react/jsx-no-useless-fragment false positive

There's a false positive on the rule with forwarded children. Use cases are pretty rare but still exist. Without a fragment around the children, code breaks at runtime
const HollowComponent = ({ children }) => {
  // some logic here
  return <>{children}</>; // doesn't pass the rule
}

example: https://codesandbox.io/s/icy-lake-ri3uo
Temporary fix is to disable rule for this line but it would be nicer if this rule let this kind of Fragment use possible.

What use cases would require the fragment?

Here are 2 use cases I actually encounter in the project I'm working on.
1. Conditional rendering
Let's say we have a component augmenting its children conditionally like the following:
const Augmenter = ({ children }) => {
  // ... logic used here ...
  return renderWithAugmentations
    ? (
      <>
        {additionalNodes}
        {children}
        {otherAdditionalNodes}
      </>
    ) : (
      <>{children}</>
    );
}

2. Testing hooks (mocks)
const MockComponentUseSomeHook = ({ children }) => {
  useSomeHook();
  return <>{children}</>;
};

In the first case, why wouldn't : children work identically?
Same question in the second case; return children should work fine.

As you can see in the codesandbox I pasted in the original post ( https://codesandbox.io/s/suspicious-sunset-ly9ik ), returning the children without a fragment can throw a runtime error.
Working with typescript generates an error too as children type for a FunctionalComponent can be undefined and said functional component cannot return the undefined type.

Thanks for bearing with me.
Type errors aren't relevant, but runtime errors are.
The solution in your code, of course, is to use defaultProps, or const TestEmpty = ({ children = null }) => children;, so that if it is undefined, it becomes null, or, const TestEmpty = ({ children }) => children ?? null;, but it seems reasonable to specifically allow a prop, only, to be used with an otherwise "unnecessary" fragment, because of undefined.

Thank you for trying to understand the issue! I'll try the null workaround in my project which seems reasonable!

Hi, I think I have encountered a similar problem. My use case is like this:
<Query>
  {({data, loading})  => {
    ...
    return (
      <>
        {anArray.map(item => {
          return item.success
            ? getTypeA(item)
            : getTypeB(item);
        })}
      </>
    );
  }
}
</Query>

This is treated as an error but the render prop expects the return to be a single element so I think the Fragment is necessary here.

I have the same issue where I'm getting an error when there's a single map function inside the fragment. I can't enable this rule and use typescript at once because of this issue.

Same error as zenefits-brody and geoguide.
There's only one child in program's AST, but there may be multiple children in React tree.
https://github.com/yannickcr/eslint-plugin-react/blob/master/lib/rules/jsx-no-useless-fragment.js#L106
One should check if the only child isn't jsx expression with a call expression inside.

@ljharb @sbdchd Hi guys, thank you for your work!
Do we have any plan for when [New] jsx-no-useless-fragment: add ignoreUnsafeChildren flag Merge Request is going to be merged?

(merge request is only a gitlab idiom, it's called a "pull request" most commonly)
That PR doesn't match https://github.com/yannickcr/eslint-plugin-react/issues/2584#issuecomment-595978999, so it needs to be updated to do so. If the PR author isn't interested in doing it, anyone else is welcome to comment a link to a branch (please do NOT open a new PR) and i'll update the PR with it.

Had the same issue with conditional rendering did anyone find a solution for that?
return user ? <>{children}</> : ;

Hi, I think I have encountered a similar problem. My use case is like this:
<Query>
  {({data, loading})  => {
    ...
    return (
      <>
        {anArray.map(item => {
          return item.success
            ? getTypeA(item)
            : getTypeB(item);
        })}
      </>
    );
  }
}
</Query>

This is treated as an error but the render prop expects the return to be a single element so I think the Fragment is necessary here.

Was this fixed already? I am still having the issue.

For me the solution was to add allowExpressions option to the config:
"react/jsx-no-useless-fragment": [2, { allowExpressions: true }]

allowExpressions: true is not work for me


[SaveAction] allow to select the output destination in a HDF5 file

When saving a curve or an image, use a DataFileDialog to specify the output destination group inside a HDF5 file.

Closed by #1752 (not using a DataFileDialog)


Add WinRT API version of GetSecurityDescriptorForAppContainerNames

#188 brought up a good idea for a WinRT API equivalent of this new function, that will return the security descriptor in SDDL string form. I'll plan to do this, but don't have time to address it right now, and it wasn't part of the original plan. Creating this issue to track that part of the feature.

Since the most common use case for this function is sharing named objects between Win32 and WinRT applications, it makes sense to create a wrapper for GetAppContainerNamedObjectPath too.
https://docs.microsoft.com/en-us/windows/uwp/communication/sharing-named-objects

Since the most common use case for this function is sharing named objects between Win32 and WinRT applications, it makes sense to create a wrapper for GetAppContainerNamedObjectPath too.
https://docs.microsoft.com/en-us/windows/uwp/communication/sharing-named-objects


Does able to using on fastspeech2 and acheive better result than HifiGAN?

Does able to using on fastspeech2 and acheive better result than HifiGAN?

Sorry, but I have never tried using it with FS2.
However, I believe it would work better than the vanilla HiFiGAN in scenarios where pitch controllability or pitch robustness is required.


K8SPS-72: fix serviceTypes

https://jira.percona.com/browse/K8SPS-72
Rename serviceType to primaryServiceType
Add replicasServiceType for headless service
Use .expose.type for per-pod services

Test name
Status

config
passed

init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

scaling
passed

sidecars
passed

users
passed

We run 8 out of 8

commit: https://github.com/percona/percona-server-mysql-operator/pull/79/commits/15e76f59c437f86e6f612824ab73c8f4bb542b5e
image: perconalab/percona-server-mysql-operator:PR-79-15e76f5


Missing word

The sentence “All decomposition glyphs used for the Syriac Abbreviation Mark but must be defined as mark glyphs” seems to be missing something between “but” and “must”.

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

ID: 4d7ea0b7-0363-c4b7-a9d8-bab46dd6a80a
Version Independent ID: f64aee9e-4d52-cb98-bb88-ee482ba09995
Content: Developing OpenType Fonts for Syriac Script - Typography
Content Source: typographydocs/script-development/syriac.md
Product: typography
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

Thank you for reporting the issue. We are correcting the wording.


[FR] custom shader support

It would be nice to be able to provide custom shaders for colormap or tilemap.
I see multiple features from that:

slopes from hillshade layer like this https://i1.wp.com/geogeek.xyz/wp-content/uploads/2019/10/Raster-of-slopes-in-degrees.png?w=825&ssl=1
raster automatic dark theme by "inverting" images
raster gray mode working on every single layer

Marking this with 'idea-maybe-future' currently, but it is unlikely to be implemented anytime soon. It is not easy to design a simple yet comprehensive shader wrapper, there is a reason why GLES/Metal have such a large APIs.
I think most use cases are covered either by:

'virtual datasources' for raster tiles that can do per-pixel translation of the original tile image
custom CartoCSS styling for vector tiles.

Marking this with 'idea-maybe-future' currently, but it is unlikely to be implemented anytime soon. It is not easy to design a simple yet comprehensive shader wrapper, there is a reason why GLES/Metal have such a large APIs.
I think most use cases are covered either by:

'virtual datasources' for raster tiles that can do per-pixel translation of the original tile image
custom CartoCSS styling for vector tiles.

@mtehver i understand but what is "virtual datasource" ?

@mtehver i understand but what is "virtual datasource" ?

@farfromrefug Virtual datasources connect to primary datasources and do some processing on the data. For example, imaginary GreyscaleRasterTileDataSource would use another datasource to fetch the tile and would then decompress the image and apply 'rgbaToGrayscale' filter to the image.

@farfromrefug Virtual datasources connect to primary datasources and do some processing on the data. For example, imaginary GreyscaleRasterTileDataSource would use another datasource to fetch the tile and would then decompress the image and apply 'rgbaToGrayscale' filter to the image.

@mtehver ok i see, thought you meant something already implemented. Now i think a shader is the way to go there as it is gpu side and thus much more efficient i think.
I understand your point about it not being easy wrap . I think i ll try and create a custom version where i can just "custom set" that string for example. Not  perfect but i think i can do almost anything with this and the current shader parameters

@mtehver ok i see, thought you meant something already implemented. Now i think a shader is the way to go there as it is gpu side and thus much more efficient i think.
I understand your point about it not being easy wrap . I think i ll try and create a custom version where i can just "custom set" that string for example. Not  perfect but i think i can do almost anything with this and the current shader parameters


[Bug] getOfferings() erroring because of Date properties

When calling getOfferings against the tbdex pfi exempler (as well as any other PFI), an error occurs:

Failed to fetch offerings: Error(reason: "Error while fetching offerings: typeMismatch(Swift.String, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "data", intValue: nil), _JSONKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "metadata", intValue: nil), CodingKeys(stringValue: "createdAt", intValue: nil)], debugDescription: "Expected to decode String but found number instead.", underlyingError: nil))")

Looks like this is happening even when the PFI doesn't have any offerings.
let pfiDid = "did:dht:f9pfkh1co4d5u1h9gjpme6tmx6xu8g565omrtohicfx1cqzw79dy"

let mockURL = URL(string: "http://localhost:9000/offerings")!
Mocker.register(Mock(url: mockURL, contentType: .json, statusCode: 200, data: [.get: Data()]))

do {
    let offerings = try await tbDEXHttpClient.getOfferings(pfiDIDURI: pfiDid)
} catch {
    XCTFail("Failed to fetch offerings: \(error)")
}

Found by @blackgirlbytes 🙌🏾

Trying this out:
func test_listOffering() async throws {
    let pfiDid = "did:dht:f9pfkh1co4d5u1h9gjpme6tmx6xu8g565omrtohicfx1cqzw79dy"

    let mockDIDDocument = """
    {
        "@context": "https://www.w3.org/ns/did/v1",
        "id": "did:dht:f9pfkh1co4d5u1h9gjpme6tmx6xu8g565omrtohicfx1cqzw79dy",
        "service": [
            {
                "id": "pfi",
                "type": "PFI",
                "serviceEndpoint": "http://localhost:9000"
            }
        ]
    }
    """.data(using: .utf8)

    let mockURL = URL(string: "https://diddht.tbddev.org/f9pfkh1co4d5u1h9gjpme6tmx6xu8g565omrtohicfx1cqzw79dy")!
    let mock = Mock(url: mockURL, dataType: .json, statusCode: 200, data: [.get: mockDIDDocument!])
    mock.register()

    let response = try await URLSession.shared.data(from: mockURL)
    print("Response: \(String(data: response.0, encoding: .utf8) ?? "")")
    do {
        let offerings = try await tbDEXHttpClient.getOfferings(pfiDIDURI: pfiDid)
        // Add assertions to verify the expected behavior or values of `offerings`
        XCTAssertNotNil(offerings)
        // Add more assertions as needed
    } catch {
        XCTFail("Failed to fetch offerings: \(error)")
    }
}

I get the error: "Failed to fetch offerings: Error(reason: "DID does not have service of type PFI")" which may be hiding the issue?

ah - mocking it out and it fails:

    let resolutionResult = await DIDResolver.resolve(didURI: pfiDIDURI)
    // print out resolution result for debugging
    print(resolutionResult)

@angiejones I think in first case - there may be an offering which has a number which ideally would go into the resource field as string, in the second empty case, its probably the lack of signature that is hiding the error.

@angiejones ok I have tried this with the PFI exemplar as well as the tbdex-aud-usd example one and waas able to get offerings listed from swift.
What will not work is mocking - then it is hiding the error, so I don't think that is related, there is something else going on that stops it, I don't think it is related to swift in this case.

I added this to the test cases:
func test_listOffering() async throws {

    let pfiDid = "did:dht:w9ktfxkcez433y1wqc8wmoyhqx6hccbfc59twx9oqf7843hqa1eo"

    do {
        let offerings = try await tbDEXHttpClient.getOfferings(pfiDIDURI: pfiDid)
        print(offerings)
    } catch {
        XCTFail("Failed to fetch offerings: \(error)")
    }
}

and it did list offerings from the exemplar.

@kirahsapong

    /// The time at which the message was created
    public let createdAt: Date

Should that be string? (or is it converted to/from the ISO format that tbdex requires later?)


cordova-plugin-googleplus fails

When adding a plugin https://github.com/EddyVerbruggen/cordova-plugin-googleplus, the login dialog does not show up and error message writes "can only use lower 16 bits for requestCode". Is there some way I can use this plugin with tabris-js

Is this a runtime error or a build error?  If the latter, can you post the full build log?

Its a runtime error... app builds just fine, it seems to load the plugin but instead of prompting for accounts it goes straight to error callback.

@rasmusustav could you provide some more context of the error message?

@rasmusustav We had a problem with plugins that call cordova.getActivity().startActivityForResult(..). This has been fixed since the 1.10 release. Could you please try to build your app against nightly?

@mpost could you please tell me how to do it on a local build. Sorry, I did not mention that before.

@rasmusustav you will have to download a nightly platform eg: https://tabrisjs.com/downloads/nightly/platforms/tabris-android.zip and than follow the regular local build procedure https://tabrisjs.com/documentation/latest/local-build#local-build

Thanks @mpost, but I give up, the problem remains & unfortunately can't tell you anything else  - all seems to run okay, console does not show any errors except it just goes to googleplus login error callback

@rasmusustav Are there any errors in logcat?  You can view it over adb, through an app, or in Android Studio.

@cookieguru yes there are, though I believe it's not very useful either.
11-29 01:07:29.473: I/GooglePlugin(12676): Building Google options
11-29 01:07:29.473: I/GooglePlugin(12676): Building GoogleApiClient
11-29 01:07:29.474: I/GooglePlugin(12676): GoogleApiClient built
11-29 01:07:29.474: I/GooglePlugin(12676): Trying to Log in!
11-29 01:07:29.474: E/PluginManager(12676): Uncaught exception from plugin
11-29 01:07:29.474: E/PluginManager(12676): java.lang.IllegalArgumentException: Can only use lower 16 bits for requestCode
So basically this https://github.com/EddyVerbruggen/cordova-plugin-googleplus/blob/766570abc2c40108d28849d3693d3e95d289d38f/src/android/GooglePlus.java#L173-L176 is where the problem starts and this is what @mpost mentioned should be fixed, but it just did not work for me.

@rasmusustav could you set up a simple demo project that can reproduce this error with the build service provided on http://tabrisjs.com ? That would have the advantage of being reproducible and we can more easily switch between different Tabris.js version and build settings there. The build service also provides detailed logging output of everything that happens during the build.

@jonek So I did what you told - built an app with your service, used Tabris.js Client Version Nightly, got positive confirmation:

Put '583d7b4d634fb0e42c18c06d/io.cordova.hellocordova-debug.apk'
Put 1 files
Done, without errors.

And again when starting login procedure, it failed. https://github.com/rasmusustav/tabris-login-test.git

@rasmusustav We have solved the issue by an update to the Android cordova platform. Could you please try again with the latest nightly?
https://tabrisjs.com/downloads/nightly/platforms/tabris-android.zip

Oh, guys, you are the best. Thank you, the last nightly did the trick

@rasmusustav Glad to hear that. :)


Backend: Save organization roles to session on login

Description :sparkles:
There was a problem when DRF was fetching the organization roles from the suomi.fi eauthorizations API every time instead of using the session variable. Save the organization roles to session on login instead of the DRF session authentication class EAuthRestAuthentication.
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #287 (75298f1) into develop (ec0447d) will decrease coverage by 0.80%.
The diff coverage is 90.90%.

@@             Coverage Diff             @@
##           develop     #287      +/-   ##
===========================================
- Coverage    95.91%   95.10%   -0.81%
===========================================
  Files          160       85      -75
  Lines         5601     2777    -2824
===========================================
- Hits          5372     2641    -2731
+ Misses         229      136      -93

Impacted Files
Coverage Δ

...kend/kesaseteli/applications/api/v1/permissions.py
89.65% <84.61%> (+0.76%)
:arrow_up:

backend/kesaseteli/applications/api/v1/views.py
91.89% <100.00%> (-0.22%)
:arrow_down:

backend/shared/shared/oidc/auth.py
86.02% <100.00%> (ø)

...ckend/shared/shared/oidc/tests/test_eauth_views.py
100.00% <100.00%> (ø)

backend/shared/shared/oidc/views/eauth_views.py
79.51% <100.00%> (+0.50%)
:arrow_up:

...ications/migrations/0017_add_company_department.py

.../applications/migrations/0014_application_batch.py

...enefit/applications/tests/test_applications_api.py

backend/benefit/companies/apps.py

backend/benefit/common/debug_util.py

... and 70 more

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 ec0447d...75298f1. Read the comment docs.


Add replication support for LDAP in nightly

Coverage increased (+0.3%) to 60.198% when pulling 29bdcfe4540fa6b054582be1a276ffe759fb27ed on wy65701436:fix-nightly-ldap into c2d9f8cc564b2a68020b4a82cbfdb2b6cbe65998 on vmware:master.


Logging improvements

Some logging fixes to address PR feedback from #4089; correct error levels in a few spots and improve consistency.

@grobinson-grafana for your comment here, do you have a preference what key name we align on?

@grobinson-grafana for your comment here, do you have a preference what key name we align on?

Group key is the correct name.

Ping, any additional work needed here?


Womanium Final Assignment - Phalak Bhatnagar

PR Description
Pull Request for submission of Classiq Assignment 6.12 on Quantum Walk Operators, as a part of Womanium Quantum+AI Program 2024.

Good job!
Score: 8/10

Good job!
Score: 8/10


Import backend env made in previous version of console / cli

I have an amplify project that I first deployed over two years ago. I've not done much development on it since then, but it does have active users.
In the current version of the console the front end environments are listed but there are no backend environments. However the app has two backend environments (dev and production) and the corresponding CloudFormation stacks all exist along with their associated dynamo tables, cognito pools and so on.
Trying to user amplify push or amplify pull results in the error An error occurred during the push operation: The specified key does not exist.
I need to get the cli and console to recognise my existing environments. How can I do this?
Region: eu-west-2
AppId: d2z0aapvx3jong

Hi @tscole, it looks like you were able to successfully push changes after this issue was created. If this is still a problem, please feel free to reopen. Thanks!

This is still a problem


[SPARK-25275][K8S] require memberhip in wheel to run 'su' in dockerfiles

What changes were proposed in this pull request?
Add a PAM configuration in k8s dockerfile to require authentication into wheel to run as su
How was this patch tested?
Verify against CI that PAM config succeeds & causes no regressions

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/2699/

Test build #95475 has finished for PR 22285 at commit f29051e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95475/
Test PASSed.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/2699/

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2699/
Test FAILed.

Merged build finished. Test FAILed.

looks like alpine doesn't have PAM installed

Test build #95477 has started for PR 22285 at commit d8c8ee4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/2700/

Test build #95477 has finished for PR 22285 at commit d8c8ee4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95477/
Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/2700/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2700/
Test PASSed.


Improve display image rendering.

I will re-write huge parts of the button image rendering to be more flexible and make it easier to implement new features.
Ideas:

Allow user to choose between

Plugin's icon
Icon from Home Assistant
No icon at all

Update (download) plugin icon rendering rules on startup

Enables updates and bugfixes withour new releases

Update (download) a list of states that represent an "active/on" state for image buttons

Enables updates and bugfixes withour new releases

Work in Progress:


Champion Leader Board is Empty

Updated vrom V1.0 to V2.0. App plloads within Teams and shows all the admin icons. Champions list is populated with Champions however when I click on the Champion Leader Board icon, no Champions are displayed.
I have deleted the app from Teams and reinstalled the the package from scratch.

Hi @Sean287,
Thanks for your patience.
Can you please share a screenshot. And can you confirm if the leader board was working earlier. Can you also share a screenshot of "Site Contents" from the share point site collection.
And please confirm if you have followed all instructions as mentioned here: https://github.com/OfficeDev/microsoft-teams-apps-champion-management/wiki/Upgrade-to-latest-version
Thanks.


Flex grid columns not rendering on mobile device (tested on iphone)

Hey there,
I've been having some issues with my flexgrid columns not rendering properly when viewing from my iphone. I set up a quick demo of it here using meteor: http://flexgridtest.meteor.com
Here's the link to the repo: https://github.com/amazingBastard/flexgrid-mobile-test
I used the grid.css from this repo and the grid I made based on your code. Not sure why it's reacting this way. Checked the link on my phone with chrome and safari and the grid isn't rendering as it's supposed to. It does work when I'm looking at the site with my laptop and resizing the browser window.
Any ideas? Thanks for the help!

Looking at your repo, flexgrid.css only has the cutting edge flexbox properties, and iOS uses an older spec.
If you copy the CSS from flexgrid.css and past it into the appropriate field here (Autoprefixer online) you'll see that a lot of properties are missing.
You can copy/paste what Autoprefixer online outputs and save it in your file, and then you should be good.
I would suggest that you read up in the spec a little, here are a few articles you might find helpful:

A Complete Guide to Flexbox [CSS-Tricks]
A Visual Guide to CSS3 Flexbox Properties [scotch.io]
Can I Use - Flexbox (Browser support, notes on which browsers use old syntax or what bugs they might have)

Hope this helps,
-Elijah

What @ElijahFowler said. I'd recommend adding autoprefixer to your build step, that way you don't even have to think about this stuff (most of the time).

Thanks a lot guys, this helps a lot.


"Verse of the day" and "Last Read" doesn't change language on language selection

Let's say I first use the app in English language.
Now, I change the language to Hindi.
"Verse of the day" and "Last Read" are still in English and do not change to Hindi.

Similarly,

Let's say I first use the app in Hindi language.
Now, I change the language to English.
"Verse of the day" and "Last Read" are still in Hindi and do not change to English.

https://user-images.githubusercontent.com/32533774/139521807-3810b894-8e71-4d8d-b4ea-b890552b8aa5.mp4

Last read was managed by the locally so not able to change language when language changed.

Done.


webapp archetype is broke

The webapp archetype is not working as expected. We should get rid of it or fix it.

butvwe tested it durin ci right?

No, currently the artifact is not tested in CI, but we should definitely adjust this.

is following error message related to this issue?
mvn archetype:generate -DarchetypeCatalog=local -DarchetypeGroupId=de.terrestris -DarchetypeArtifactId=shogun2-webapp-archetype
[INFO] --- maven-archetype-plugin:3.1.2:generate (default-cli) @ shogun-core --- [INFO] Generating project in Interactive mode [WARNING] Specified archetype not found. [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype:    Your filter doesn't match any archetype (hint: enter to return to initial list) Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): :

Actually, the artifact is called differently nowadays, try
mvn archetype:generate -DarchetypeCatalog=local -DarchetypeGroupId=de.terrestris -DarchetypeArtifactId=shogun-core-webapp-archetype -DarchetypeVersion=4.0.0
Still, I'm currently unsure whether the archetype is in a working state.


⚠ Jenkins Plugins Artifactory has degraded performance

In e766af0, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1127 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 87c6f6e after 25 minutes.


Issue 1500: allows useOverlayPosition to take a prop maxHeight

Closes https://github.com/adobe/react-spectrum/issues/1500
Note

Note useOverlayPosition returns user-specified maxHeight or current available viewport height, whichever is smaller.
The change of maxHeight triggers useCallback hook and thus will update the overlay position, which can be useful for responsive design as users might want to set different maxHeights.

✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[x] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

Check out stories > useOverlayPosition > maxHeight=200. Note given the maxHeight, the dropdown won't take all viewport space now even there's more available.
Simply run yarn jest.

🧢 Your Project:
Adobe Garage Week :)

Tested locally. Also concerned about regressions.

Tested locally. Also concerned about regressions.

Hi @ktabors, is it causing any regressions?


Issues on CPFlow deployment on linux

Hello, I have encountered some issues when deploying CPFlow on Linux recently. Firstly, I am using Python 3.8, and when I directly ran pip install cpflow, the installed version of Qiskit was 1.2.4 and the version of jaxlib was higher than 0.3.5. However, the latest CPFlow-0.0.4 requires jaxlib to be in the range of 0.3.0 to 0.3.5, but this version range is no longer available on PyPI. Although I managed to install it through other methods, new issues arose. A higher version of Qiskit is causing CPFlow to not run properly. I was able to get it working with older versions (qiskit==0.46.0, qiskit-ibm-runtime==0.18.0). The version of qiskit-terra that comes with this qiskit is higher than 0.20.0, which is the version you specified for installation. Without installing the version you recommended, the program runs successfully and outputs:
7 successful. cz counts are:
[8, 8, 8, 8, 8, 9, 10]
< ccz_chain | Rational | loss: 0.0 | CZ count: 8 | CZ depth: 8 >

This result is inconsistent with what you have stated in the README, and there are no circuit prints, but the ccz_chain file is generated in the result directory. I also tried it on Colab but encountered similar issues. Could you please advise on the correct environment setup to properly run the files from your tutorial?

Hi @eeethon! Thanks for your interest in CPFlow and sorry it led you to the dependency hell.
Unfortunately, CPFlow is not currently supported or kept updated. If your goal is to find the absolute shortest possible circuit for a small unitary, it still may be worth it to try and setup everything so that it works.
However, if you are looking for a generic quantum circuit compiler you'd probably be better off using some of the more versatile and actively supported ones, such as BQSKit.
Hope that helps!

Thank you very much for your reply, @idnm. CFPlow is still very valuable for small-scale circuit optimization.  Several days ago, I noticed that you had provided the specific environment configuration at the bottom of the tutorial's Jupyter Notebook. I apologize for not seeing it earlier. With this information, I can replicate the environment. Additionally, two days ago, I learned about other circuit optimization tools from the papers, including BQSKit, and I plan to try these tools next. Thank you again for your reply!


Egdetpu.tflite Converting Error

Hi there,
When I try to convert my .tflite model to Edgetpu.tflite, I got this error:
’‘’
Edge TPU Compiler version 15.0.340273435
Invalid model: model_nasa_bearing_CNN.tflite
Model not quantized
‘’‘
Here is how I convert my tf model to tflite:
‘’‘
run_model = tf.function(lambda x: model(x))
BATCH_SIZE = 1
STEPS = 4
INPUT_SIZE = 1279
concrete_func = run_model.get_concrete_function(tf.TensorSpec([BATCH_SIZE, STEPS, INPUT_SIZE], model.inputs[0].dtype))
MODEL_DIR = "/content/gdrive/MyDrive/Colab Notebooks/tf_saved_model"
model.save(MODEL_DIR, save_format="tf", signatures=concrete_func)
converter = tf.lite.TFLiteConverter.from_saved_model(MODEL_DIR)
tflite_model = converter.convert()
‘’‘
I also tried:
’‘’
tf.lite.TFLiteConverter.from_keras_model()
and
tf.lite.TFLiteConverter.from_saved_model(MODEL_DIR)
without using concrete function
‘’‘
The error is still the same.
Do you have any idea about what happened there?
https://drive.google.com/file/d/1ivl5h0X803EsGjRLFXswRBQbjCxwRye4/view?usp=sharing   Here is my Demo LSTM tflite model.
Thank you in advance.
Ze

Hello,
I 've visualized the model using netron.app. I can see the model layers have datatype of float 32.
we need to fully quantize the model to int8 format.
please check these tutorial section convert to TF Lite
https://colab.sandbox.google.com/github/google-coral/tutorials/blob/master/retrain_classification_ptq_tf2.ipynb#scrollTo=P0_StAtZwJ5p

Hi,
I followed this instruction, but I got this error when I am converting LSTM:
ValueError: Failed to parse the model: pybind11::init(): factory function returned nullptr.
The weird thing is, when I created a CNN model, it works well. Does this mean LSTM is not supported yet?
This is how I create this demo LSTM model:
model = tf.keras.models.Sequential([
tf.keras.layers.Input(shape=(4, 1279), name='input'),
tf.keras.layers.LSTM(20, time_major=False, return_sequences=True),
tf.keras.layers.Flatten(),
tf.keras.layers.Dense(2, activation='softmax', name='output')
])
model.compile(optimizer='adam',
loss='sparse_categorical_crossentropy',
metrics=['accuracy'])
model.summary()

can you please share your quantization script and saved model?

Hi,
Here is the Colab link:
https://colab.research.google.com/drive/1_NstPsGiyZE5VqnRREDPwUvrV6Ethqma?usp=sharing

There is an open issue in tensorflow repository for this error.
https://github.com/tensorflow/tensorflow/issues/46821
please check with tensorflow team.

Hi,
Thanks a lot for your support. I will check this with tf team.
BTW, I got this edgetpu.tflite works on the google dev board now. I noticed that, to run an inference with edgetpu.tflite, the data type should be uint8. However, while creating the tf model, I normalized my data to range (0, 1). In this case, if I convert my data to uint8, all my data will be 0 or 1. Does this mean I can not normalize my data to (0, 1) anymore if I want to use edgetpu.tflite?

Hi, Normalization of inputs does not affect the quantization. As quantization would be performed on weights of the model.

Hi,
Thanks a lot for your help. I finally understand that the input data type should be pre-defined while creating the quantized model. Thank you so much!


Fix test for IE7/IE8 build

Wrapping test object keys as string to avoid IE7/IE8 error (reserved identifiers).
Tests were added with #3667 : https://travis-ci.org/jashkenas/backbone/builds/66548299.

Thanks for looking into it!

Grr oldIE.
Thanks for the quick fix.

Hmm, we should set up (actually run) linting for backbone
/cc @michaelficarra

Yes, probably. A linting step is basically free, and takes 5 minutes to set up. I suggest someone with more familiarity with the project than myself does this, though.

It's already set up. We could use eslint, like Underscore, too though.

It's already set up. We could use eslint, like Underscore, too though.
Yeah but we don't run it through CI and haven't updated it in a long time

For sure, but it would be a one line change to set it up with CI. I'd be fine just cribbing Underscore's .eslintrc here.

If the projects follow similar styles and have similar browser support, I'd say that's a good idea.


[NFC] Include implicit-unwrap bit in AST dump

There’s a bit in the AST indicating whether a ForceValueExpr is an implicitly-inserted unwrap of an IUO, but it’s not included in the AST dump. Add it.

@swift-ci please smoke test

No test changes in this PR because we don't test AST dumps.


the map is showing blank

This is how the map looks when I run it on android.
I created a totally blank project just to test the map, but no matter how hard I try, it does not display well and does not throw any error.
This is my .ts
`
import { Component, ElementRef, OnInit, ViewChild } from '@angular/core';
import { Plugins } from '@capacitor/core';
import { CapacitorGoogleMapsPlugin } from 'capacitor-googlemaps-native';
const { CapacitorGoogleMaps } = Plugins;
...
...
@ViewChild('map', {static: false}) mapView: ElementRef;
capacitorGoogleMapsPlugin: CapacitorGoogleMapsPlugin = CapacitorGoogleMaps;

constructor() {
}

async ngOnInit() {
    // await this.capacitorGoogleMapsPlugin.initialize({
    //     key: 'AIzaSyD3t5VAdEBMdICcY9FyVcgBHlkeu72OI4',
    // });
}

async ionViewDidEnter() {
    const boundingRect = this.mapView.nativeElement.getBoundingClientRect() as DOMRect;

    this.capacitorGoogleMapsPlugin.create({
        width: Math.round(boundingRect.width),
        height: Math.round(boundingRect.height),
        x: Math.round(boundingRect.x),
        y: Math.round(boundingRect.y),
        latitude: -33.86,
        longitude: 151.20,
        zoom: 12,
    });

    this.capacitorGoogleMapsPlugin.addListener('onMapReady', async () => {

        /*
          We can do all the magic here when map is ready
        */

        this.capacitorGoogleMapsPlugin.addMarker({
            latitude: -33.86,
            longitude: 151.20,
            title: 'Custom Title',
            snippet: 'Custom Snippet',
        });

        this.capacitorGoogleMapsPlugin.setMapType({
            type: 'normal',
        });
    });
}

ionViewDidLeave() {
    this.capacitorGoogleMapsPlugin.close();
}

`

The code you shared looks good. Have you configured the key in AndroidManifest ? https://github.com/hemangsk/capacitor-googlemaps-native#add-api-key-to-your-app

Yes, I do

And add plugin class in MainActivity

A few checks I can think of:

We've to ensure Maps SDK for Android is enabled for your API key in Google cloud console.
Internet access should be available on the device/emulator so that the library can fetch the map tiles.
Version of library is 0.0.3 and not an older one.
Is the below mentioned line showing typescript lint errors?

capacitorGoogleMapsPlugin: CapacitorGoogleMapsPlugin = CapacitorGoogleMaps;

I'm seeing
Type '{ [prop: string]: any; }' is missing the following properties from type 'CapacitorGoogleMapsPlugin': create, initialize, addMarker, setMapType, and 17 more.ts(2740)

But, after changing to
capacitorGoogleMapsPlugin = CapacitorGoogleMaps;

it compiles.
Let me know if that solves the issue. I will try to prep a bare bones demo tomorrow incase we aren't able to figure this out.

Sorry, my mistake, you have activated only the SDK for Javascript and not for android, now that I add it it looks perfectly, thanks for your time and sorry for the inconvenience.
And no, it does not present me with typescript  lint errors

No worries! I'm glad you got this resolved :)  closing the ticket


[GGSoC'23] Adding hamburger icon for phones

Hey,
I would like to improve the navbar, using the hamburger icon.
Thanks and regards,
Vibhuti Chandrakar

hello,
I would like to work on this issue, I can improve the NAVBAR by making it 100% responsive and as seen on the website there is OVERFLOW when in the lower width size(shrunk web-page). Please assign me this issue under GGSOC 23'
Regards Priyam Maini

Hello @akshitagupta15june
Issue: Improve Responsiveness and Overflow Issue in NAVBAR
Description:
The current NAVBAR on the website lacks responsiveness, causing overflow and layout issues when viewed on smaller screen sizes. As a GGSOC '23 contributor, I propose to enhance the NAVBAR's responsiveness and resolve the overflow problem to ensure optimal user experience across different devices.
Proposed Solution:
To address this issue effectively, I suggest the following steps:
Analyze the existing NAVBAR code and identify the areas that contribute to the lack of responsiveness and the overflow problem.
Implement responsive design techniques, such as media queries, to adjust the NAVBAR's layout and content based on different screen sizes.
Test the modified NAVBAR thoroughly on various devices, including mobile, tablet, and desktop, to ensure it adapts seamlessly and eliminates the overflow issue.
Make necessary adjustments to the NAVBAR's HTML and CSS code, optimizing it for responsiveness without sacrificing functionality or aesthetics.
Tasks:
Identify the causes of responsiveness and overflow issues in the NAVBAR.
Implement responsive design techniques to make the NAVBAR 100% responsive.
Test the modified NAVBAR on multiple devices to ensure its adaptability and resolve the overflow problem.
Optimize the NAVBAR's HTML and CSS code for improved performance and maintainability.
Request for Assignment:
As a GGSOC '23 contributor, I would like to be assigned to this issue to enhance the responsiveness and resolve the overflow problem in the NAVBAR. I have experience in implementing responsive design and ensuring optimal user experience across various devices.
I am confident in my ability to address this issue promptly and effectively. By improving the NAVBAR's responsiveness, I will contribute to enhancing the overall usability and visual appeal of the website.
Please assign me this task, and I will commence working on it to provide an improved NAVBAR experience.
Thank you for considering my contribution!

Please provide the page on which you found the issue, please share screenshots of the issue.
A responsive navbar is implemented on blog page have a look into it , the same implementation will be done on all other pages.

@ankitjt I have added the screenshot . Please have a look

some are working on the same


Vdebug closing as soon as it connects

As soon as it finds a connection, vdebug closes and the page that's loading just dies.
- [Debug] {Tue 20 2018 14:22:31} Setting buffer for DebuggerWatch: ['']
- [Debug] {Tue 20 2018 14:22:31} Setting buffer for DebuggerStack: ['']
- [Debug] {Tue 20 2018 14:22:31} Setting buffer for DebuggerStatus: ['Status: stopped', 'Listening on port', 'Not connected', '', 'Press <F5> to start debugging, <F6> to stop/close. Type :help Vdebug for more information.']
- [Info] {Tue 20 2018 14:22:32} Closing the connection
- [Debug] {Tue 20 2018 14:22:32} Command: stop -i 1
- [Debug] {Tue 20 2018 14:22:32} Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="stop" transaction_id="1" status="stopped" reason="ok"></response>
- [Debug] {Tue 20 2018 14:22:32} Closing the socket
- [Debug] {Tue 20 2018 14:22:32} Closing the socket
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: ['']
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: ['']
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: ['Status: stopped', 'Listening on port', 'Not connected', '', 'Press <F5> to start debugging, <F6> to stop/close. Type :help Vdebug for more information.']
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: [' 11000   | line        | /home/james/dev/myshopmanager/app/Http/Controllers/CampaignController.php:1072']
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: []
- [Debug] {Tue 20 2018 14:22:32} Creating hidden buffer: []
- [Debug] {Tue 20 2018 14:22:32} Closing the socket

PHP 7.2.3
Arch Linux (up to date)
Vdebug is up to date
Python 3
Let me know if I left out any important info!

@FatBoyXPC Did you add any configuration for vdebug, or just using it with the defaults?

Defaults, though I did have to use :VdebugOpt to get the debug level and debug file. I was looking for the highest level I could set it to, though I guess I could have just set it higher and higher until it stopped working.

It seems I have the same problem:
I am using latest vdebug on Mac OS X with Neovim and Python3:
- [Debug] {Wed 21 2018 21:47:49} Setting buffer for DebuggerWatch: ['']
- [Debug] {Wed 21 2018 21:47:49} Setting buffer for DebuggerStack: ['']
- [Debug] {Wed 21 2018 21:47:49} Setting buffer for DebuggerStatus: ['Status: stopped', 'Listening on :9000', 'Not connected', '', 'Press <F5> to start debugging, <F6> to stop/close. Type :help Vdebug for more information.']
- [Info] {Wed 21 2018 21:47:50} Found connection from ('<IP_ADDRESS>', 49965)
- [Debug] {Wed 21 2018 21:47:50} Command: context_names -i 1
- [Info] {Wed 21 2018 21:47:50} Closing the connection
- [Debug] {Wed 21 2018 21:47:50} Command: stop -i 2
- [Debug] {Wed 21 2018 21:47:50} Response: <?xml version="1.0" encoding="utf-8"?>
<response xmlns="urn:debugger_protocol_v1" command="context_names" transaction_id="1"><context name="Locals" id="0"/><context name="Globals" id="1"/><context name="Code Objects" id="2"/></response>
- [Debug] {Wed 21 2018 21:47:50} Closing the socket
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: ['']
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: ['']
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: ['Status: stopped', 'Listening on :9000', 'Not connected', '', 'Press <F5> to start debugging, <F6> to stop/close. Type :help Vdebug for more information.']
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: [' 11000   | line        | /Users/gf/work/nvim-tuts/python/hello_world.py:5']
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: ['- [ERROR] {Wed 21 2018 21:39:21} Tracing an expression is only possible when Vdebug is running', '', '- [ERROR] {Wed 21 2018 21:46:05} Tracing an expression is only possible when Vdebug is running', '']
- [Debug] {Wed 21 2018 21:47:50} Creating hidden buffer: []
- [Debug] {Wed 21 2018 21:47:50} Closing the socket
- [Debug] {Wed 21 2018 21:47:50} Closing the socket

@Govinda-Fichtner I have no issues testing with a dockersetup using neovim on macOS high Sierra

@BlackIkeEagle Can you describe how did this so I can test this on my machine and figure out if this a problem specific to my setup or not? Thanks.

@Govinda-Fichtner
$ brew install neovim
$ pip3 install neovim
installed my vimfiles https://github.com/BlackIkeEagle/vimfiles
I'm using docker-compose with dinghy (for example: https://github.com/dockerwest/compose-magento2)
I have a magento2 installed and start debugging, no issues.

@FatBoyXPC I have no issues on Arch so I cannot reproduce your issue.

@FatBoyXPC my PHP information:
php -v
PHP 7.2.3 (cli) (built: Mar  1 2018 16:50:09) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Xdebug v2.6.0, Copyright (c) 2002-2018, by Derick Rethans

php -m
[PHP Modules]
Core
ctype
curl
date
dom
fileinfo
filter
hash
intl
json
libxml
mbstring
mysqlnd
openssl
pcntl
pcre
PDO
Phar
posix
readline
Reflection
session
SimpleXML
SPL
standard
tokenizer
xdebug
xml
xmlreader
xmlwriter
zip
zlib

[Zend Modules]
Xdebug

@BlackIkeEagle Well that's frustrating :disappointed:  Could it be an xdebug version issue?
 I've also set debug_file_level to 8 and I don't think any new information was given in the log

@FatBoyXPC I'm sorry I still can't reproduce your issue, I've just installed laravel and tried using locally installed php on Arch:
$ composer create-project --prefer-dist laravel/laravel laravel
$ cd laravel
$ php artisan serve

browsing <IP_ADDRESS>:8000

enable debugger with browser plugin and let vdebug wait with default settings (I removed my personal default settings from my vimrc)

Is there a way I can dump the Vdebug config that is loaded or something? Are you using your development copy of Vdebug or are you at the same commit as master branch?
When looking through the commit history, it looks like somebody recently modified the whole listening/not listening part of the code (at least, according to the commit messages). I went ahead and checked out this commit just to see if any of the changes since then were the culprit, but I was still unable to connect.
Can you check your Python version and see if maybe that's the issue?

This is what I did

set parameter 'background_listener' to 0
quit Vimredebug
open vim +VdebugStart
Vdebug quit and display message below
Error starting Vdebug: <class 'UnicodeDecodeError'>

@FatBoyXPC I'm using vdebug almost daily, if it is not working I'm also affected so that would be very weird that the python3 change broke everything
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Mar 25 2018 21:47:56)
Included patches: 1-1645
Compiled by BlackEagle
Huge version without GUI.  Features included (+) or not (-):
+acl               +farsi             +mouse_sgr         -tag_any_white
+arabic            +file_in_path      -mouse_sysmouse    -tcl
+autocmd           +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
-balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
-browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           -netbeans_intg     +timers
+byte_offset       -hangul_input      +num64             +title
+channel           +iconv             +packages          -toolbar
+cindent           +insert_expand     +path_extra        +user_commands
+clientserver      +job               +perl/dyn          +vertsplit
+clipboard         +jumplist          +persistent_undo   +virtualedit
+cmdline_compl     +keymap            +postscript        +visual
+cmdline_hist      +lambda            +printer           +visualextra
+cmdline_info      +langmap           +profile           +viminfo
+comments          +libcall           +python/dyn        +vreplace
+conceal           +linebreak         +python3/dyn       +wildignore
+cryptv            +lispindent        +quickfix          +wildmenu
+cscope            +listcmds          +reltime           +windows
+cursorbind        +localmap          +rightleft         +writebackup
+cursorshape       +lua/dyn           +ruby/dyn          +X11
+dialog_con        +menu              +scrollbind        +xfontset
+diff              +mksession         +signs             -xim
+digraphs          +modify_fname      +smartindent       -xpm
-dnd               +mouse             +startuptime       +xsmp_interact
-ebcdic            -mouseshape        +statusline        +xterm_clipboard
+emacs_tags        +mouse_dec         -sun_workshop      -xterm_save
+eval              +mouse_gpm         +syntax
+ex_extra          -mouse_jsbterm     +tag_binary
+extra_search      +mouse_netterm     +tag_old_static
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_FORTIFY_SOURCE=2  -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.26/core_perl/CORE  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -L/usr/local/lib -Wl,--as-needed -o vim    -lSM -lICE -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lelf -lnsl    -lacl -lattr -lgpm -ldl   -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.26/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/perl5/5.26/core_perl/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc

Could you test with my vim version (https://repo.herecura.eu)
or neovim from the Arch repos

@azhargiri could you please open another issue for this, I would say, settings background_listener to 0 is not supported right now

@FatBoyXPC  with vim version from Arch:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb 26 2018 23:02:12)
Included patches: 1-1542
Compiled by Arch Linux
Huge version without GUI.  Features included (+) or not (-):
+acl               -clientserver      +dialog_con        +find_in_path      +keymap            +modify_fname      +multi_byte        +profile           +statusline        +textobjects       +wildignore
+arabic            -clipboard         +diff              +float             +lambda            +mouse             +multi_lang        +python/dyn        -sun_workshop      +timers            +wildmenu
+autocmd           +cmdline_compl     +digraphs          +folding           +langmap           -mouseshape        -mzscheme          +python3/dyn       +syntax            +title             +windows
-autoservername    +cmdline_hist      -dnd               -footer            +libcall           +mouse_dec         +netbeans_intg     +quickfix          +tag_binary        -toolbar           +writebackup
-balloon_eval      +cmdline_info      -ebcdic            +fork()            +linebreak         +mouse_gpm         +num64             +reltime           +tag_old_static    +user_commands     -X11
+balloon_eval_term +comments          +emacs_tags        +gettext           +lispindent        -mouse_jsbterm     +packages          +rightleft         -tag_any_white     +vertsplit         -xfontset
-browse            +conceal           +eval              -hangul_input      +listcmds          +mouse_netterm     +path_extra        +ruby/dyn          +tcl/dyn           +virtualedit       -xim
++builtin_terms    +cryptv            +ex_extra          +iconv             +localmap          +mouse_sgr         +perl/dyn          +scrollbind        +termguicolors     +visual            -xpm
+byte_offset       +cscope            +extra_search      +insert_expand     +lua/dyn           -mouse_sysmouse    +persistent_undo   +signs             +terminal          +visualextra       -xsmp
+channel           +cursorbind        +farsi             +job               +menu              +mouse_urxvt       +postscript        +smartindent       +terminfo          +viminfo           -xterm_clipboard
+cindent           +cursorshape       +file_in_path      +jumplist          +mksession         +mouse_xterm       +printer           +startuptime       +termresponse      +vreplace          -xterm_save
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_FORTIFY_SOURCE=2  -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.26/core_perl/CORE  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -L/usr/local/lib -
Wl,--as-needed -o vim        -lm -ltinfo -lelf -lnsl    -lacl -lattr -lgpm -ldl   -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.26/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/
perl5/5.26/core_perl/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc   -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lieee -lm

@FatBoyXPC @sstutz
Do you still get the issue if you are using this minimal vimrc:
" nocompatible has to be the first of all ( use the real vimpower )
set nocompatible

""""
" Plug config
""""

if (has("nvim"))
    call plug#begin('~/.local/share/nvim/plugged')
else
    call plug#begin('~/.vim/plugged')
endif
" colors
Plug 'chriskempson/base16-vim'

Plug 'joonty/vdebug'

call plug#end()

""""
" default vim settings
"""""

" vdebug settings
let g:vdebug_options = {
    \'path_maps': {'/phpapp': getcwd()}
\}

That is the result for me when using this minimal vimrc

@BlackIkeEagle it looks like @sstutz figured it out. We both has some listchars going on in our vim configs. If I comment out this line:
set listchars=tab:›\ ,trail:•,extends:#,nbsp:. " Highlight problematic whitespace
Then it works!

@BlackIkeEagle the issue is not the listchars setting itself but rather the unicode used, replacing the › and •  symbol with - works as well

@FatBoyXPC and @sstutz If you could test https://github.com/vim-vdebug/vdebug/pull/340 That fixes the issue on my machine with utf8 data in listchars

Works for me, I'll nag @sstutz and see if I can get him to confirm as well.


Update Pathology Bundle Weights

Description
Update the pathology bundle weights and metrics
Status
Ready
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.

/build

/build

/build

Hi @drbeh  , could you please help to double check the authority of the new weights? The CI test failed due to download issue. A part of logs is like below:
Cannot retrieve the public link of the file. You may need to change the permission to 'Anyone with the link', or have had many accesses.
RuntimeError: Download of file from https://drive.google.com/uc?id=1Y-kLanna3osAEqZHiLeh5nOkAKcSU0uc to models/pathology_tumor_detection/models/model.pt failed due to network issue or denied permission.

/build


Bitbucket Cloud: .tekton/ subtree support

The same way we have support for subtree on Github, we should have that same support for Bitbucket Cloud

we need to update bitbucket cloud to get subtree listing support in client cf: https://github.com/ktrysmt/go-bitbucket/commit/f3ac86cd695cd17a1ab80fd70deb60f4f44a4ad6
from a qucik try updating it, i am getting some failures :

let's postpone this feature for 0.8.x


Add option for not bump major version

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
Hi,
first of all: thanks for this tool, i love it!
I'm trying to briefly explain my needs:
in some scenario i have two version of a library (one for a language version and one for another), in this case i simply use master to advance and a branch release-1.x to keep the versioning for the old language and i want to keep 1.x.x semver.
So it could be very helpful to have an option like features_never_bump_major and breaking_never_bump_major or something else to assure that the bump is never for major
Desired solution
add some option to avoid major bumping
Alternatives considered
i could add some enforcing on ci or git hooks to avoid commit description with potential major bump, but is cumbersome and error prone
Additional context
No response

Hello, thanks for reporting this! 🐻
git-cliff uses the next_version crate for bumping the version. It might be better to ask the maintainer of that crate @MarcoIeni regarding if a new config option like that would be applicable or not :)

Hi, I'm truly sorry, but I'm not keen to add this option. It seems like a very unique use case, and I don't want to complicate the codebase to add it. Again, sorry!
I hope you find a workaround.

Orhun, if you want to implement this feature in git-cliff, I'm happy to help. E.g. if git-cliff has the features_never_bump_major set, and the library next_version returns a major bump, you could instead bump the minor version yourself.

I think the best way would be to have this functionality in next_version not to segregate things. But it's fine, I guess we can do it here too.

next_version returns a major bump, you could instead bump the minor version yourself.

How can we check if the returned version is major bump etc?

I think it would make the most sense if the default behavior would be according to: https://doc.rust-lang.org/cargo/reference/semver.html

Initial development releases starting with “0.y.z” can treat changes in “y” as a major release, and “z” as a minor release. “0.0.z” releases are always major changes. This is because Cargo uses the convention that only changes in the left-most non-zero component are considered incompatible.

The option breaking_always_bump_major is still ok and can be respected when set, alternatively it's default value could be auto

Could we maybe reuse the mechanism of https://github.com/MarcoIeni/release-plz/commit/0a97ba40c8600190d0150239ffeed2eea900c53a
Eg we specify feat to as a patch bump. So that it doesn't bump minor. 🤔
For breaking changes there could be something similar 🤔🤔
Btw Orhun, I'm on mobile, so I'm not sure how you invoke next_version. But to check if a major has been updated, you could simply compare the two major versions (before and after the bump). The next_version crate exposes some functionalities to do the bump manually.
Have a look at:

https://docs.rs/next_version/latest/next_version/trait.NextVersion.html#tymethod.increment_minor
https://docs.rs/next_version/latest/next_version/enum.VersionIncrement.html#method.bump

Could we maybe reuse the mechanism of MarcoIeni/release-plz@0a97ba4
Eg we specify feat to as a patch bump. So that it doesn't bump minor. 🤔
For breaking changes there could be something similar 🤔🤔 (I know it's very similar to what was proposed in this issue 😅).
Btw Orhun, I'm on mobile, so I'm not sure how you invoke next_version. But to check if a major has been updated, you could simply compare the two major versions (before and after the bump). The next_version crate exposes some functionalities to do the bump manually.
Have a look at:

https://docs.rs/next_version/latest/next_version/trait.NextVersion.html#tymethod.increment_minor
https://docs.rs/next_version/latest/next_version/enum.VersionIncrement.html#method.bump

mbodmer, the behavior you described is already the default 👍

do you think adding a flag to specify the bump version type to use increment_xxx api in the next_version can be considered?
i come from standard-version and wonder if there is anything equivalent to --release-as in that

You can already do this without adding another option. Check out the links I posted above.

Sorry. Do you mean there is already a way to specify  bump type in git-cliff? I saw your link to next_version and release-plz. I must be missing something here.

No, I'm talking about the next_version library. I didn't get your request was for git cliff 👍

thanks, i made use of the api and make a pr in https://github.com/orhun/git-cliff/pull/744


"ValueError: Reused local directory" How should I reuse local file with streaming?

However, I've encountered an issue when trying to reuse a dataset that's saved locally in MDS format.
I keep getting the error: "ValueError: Reused local directory." How can I properly reuse the dataset? Is there a function to reinitialize the streaming process?
Thanks!

Can you open this in https://github.com/mosaicml/streaming instead please? It makes it easier for us to triage


test: disable check_broadcast_log test

Motivation
ignores the check_broadcast_log that's currently failing on a couple of open PRs (#1946, #1945, #1926)
unfortunately, it's not obvious why this fails, updating the file also did not help, #1941
but looks like this is perhaps due to some regex issues #1938, no idea what this even does, sorry @joshieDo :)

Solution

ignore test until test improved

@joshieDo FWIW, I've seen effectiveGasPrice also change in between runs. I'm not sure if that's just when I run the test alone or if the gas price can really change in the test somehow. If so, it might be a quick fix to also add it to the regex replacer.


adding direction cosines in beam pack

also JROread

Erhan, I agree with the changes.. .Lets merge it.

Erhan, I agree with the changes.. .Lets merge it.

OK, i'll do it

OK, i'll do it


100% cpu for projects with symlink loops

The setup was a (large and old) project that contains symlink loops, like this:
$ ls -l some/dir/
...  some-sub-dir -> ../..
...

This caused the emacs_erlang_yaemep_support.erl helper to go into infinite loop and consume 100% cpu for the update_etags_project_dir and update_completion_cache commands.
I investigated the update_etags_project_dir a bit, and it is actually the call to filelib:wildcard(filename:join(Directory, SearchPattern)) in update_etags/4 that never returns, traversing .../some/dir/some-sub-dir/some/dir/some-sub-dir/some/dir/some-sub-dir/... indefinitely. I found this using strace -e trace=file -ff -p <pid-of-beam-consuming-cpu>.
Maybe this is a problem for fileilb:wildcard/1,2 rather than for yaemep, but on the other hand, the file pattern it uses in this case, **/*.{erl,hrl} is so simple it would be possible to work around the filelib:wildcard/1 loop. I took brief look at using filelib:fold_files/5 instead, but it seems to follow symlinks indefinitely too, which leads me to think it would be necessary to write some file traversal code of ones own. Do you have any opinion about this?
(Why the project contains symlink loops? Can they be removed?  It has even survived a change of version control system, and I think some of the symlink loops may have been adaptations to get some tools to work correctly. In this particular case, removal of symlinks causing loops would not be an option, but it would still be good to be able to use yaemep.)

Thanks for reporting this issue. At least it does not seem like a very useful behavior that fileilb:wildcard goes into an infinite loop when there are symlink loops so I think it would be good to report this as a bug in the Erlang issue tracker. @tomas-abrahamsson can you file such a bug?

Do you have any opinion about this?

I agree that it would be nice to have a work around for this issue that at least covers the common case with the file pattern **/*.{erl,hrl} . One could also use a simple regular expression to make a work around cover file patterns of the form **/*.{ext1,ext2,ext3,...,extN}. One idea I have is to wrap the fileilb:wildcard call inside a separate process and only use the workaround if the filelib:wildcard-runner has not completed within a fixeed amount of time, but I'm not sure if that will be worth the extra effort and added complexity. I would be happy to accept a pull-request with a good workaround. Please let me know if you have any additional questions or anything you want to discuss.
Note that the filelib:wildcard function is used in several places in emacs_erlang_yaemep_support.erl not only used in update_etags.  A work around would need to update all places where filelib:wildcard are used.

I had forgotten about the ELOOP error.
$ mkdir /tmp/symlink-loops
$ cd /tmp/symlink-loops
$ ln -s . l
$ touch x.txt
$ ls /tmp/symlink-loops/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/x.txt
/tmp/symlink-loops/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/x.txt
$ ls /tmp/symlink-loops/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/x.txt
ls: cannot access '/tmp/symlink-loops/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/l/x.txt': Too many levels of symbolic links

So the cpu consumed is indeed finite. (will try to change the title of this ticket.) But if the directory tree is large and a symlink points back many levels towards the root, the time can be very long, which is what happened in our use-case. The escript helper had consumed several gigabytes of memory after many hours and was still running when I killed it.
Given eloop, whether it is still a bug in filelib:wildcard, I'm not so sure any more, but I'll try to make a PR for yaemep anyway. I've been considering whether to follow symlinks to outside the project directory tree, and a possible valid use-case could be if some files are under git annex or git lfs in conjuction with multiple git worktrees: Like Git LFS, git-annex takes large files out of Git's history. The way it handles this is by storing a symbolic link to the file in .git/annex. Maybe this case is not too common, but on the other hand there may be non-git use-cases too.
I, too, think it is wise to avoid a timeout for filelib:wildcard, with a fallback, mostly because what is a suitable timeout? Even if there are no symlink loops, it can still take long for a large project on a slow nfs disk.

I've been considering whether to follow symlinks to outside the project directory tree, and a possible valid use-case could be if some files are under git annex or git lfs in conjuction with multiple git worktrees...

I think it should be possible to avoid loops and still follow symlinks by keeping a set of already visited folders (to avoid visiting the same folder twice) while searching the file system. The 'file:read_link_info/1' and file:read_link/1 functions can be used to check if something is a symlink and what folder the symlink is pointing to. Do you see any problems with this approach?

Yes, that should be doable.

Closing as this has been fixed (see https://github.com/kjellwinblad/yaemep/pull/4)


Basic scaffolding for proxying content from s3/local filesystem

What

a functioning service to render interactive resources - sample manually saved from: https://www.ons.gov.uk/businessindustryandtrade/internationaltrade/articles/internationalimportsofservicestosubnationalareasoftheuk/2017#service-imports-into-the-english-regions-and-three-devolved-nations
includes boilerplate from repo generator - in hindsight should have merged this first 🙈
test coverage - needs some additional work

To Run Locally:

set env var: SERVE_FROM_LOCAL_DIR=internal/sample_data
run make debug
point browser to: http://localhost:27300/interactives/an_interactives_id/index.html

Will also serve from S3 - via minio for localhost.

initial plumbing all looks good


Make "Validation" Faster

Previously, publishing on NuGet was easy-peasy and fast.
Now I have to wait over an hour for my "nuget" package to publish. The consequence is now others, and I, have to stop working on an issue for at least a few hours until my NuGet package is published.

Why does it take so long?
Can you please make this faster?

This new validation is annoying and irritably getting in the way of being productive.
Also, this new janky "validation" gets worse, sometimes validation doesn't complete. I unlisted v21.0.1 few days ago because it took too long and never completed in a timely manner. I thought maybe something got stuck in your validation pipeline. So I had to republish the same exact package with a different version number 21.0.2.
Again, the overall goal should be to make NuGet more accessible, not less.
My NuGet package is Bogus listed here: https://www.nuget.org/packages/Bogus/

Thanks,
Brian

4 hours 13 minutes and counting here :(

This is causing us significant pain.
We've just published over 100 Google.Apis.* packages at v1.32.0 (e.g. Google.Apis.Storage.v1), but they all depend on Google.Apis v1.32.0, Google.Apis.Auth v1.32.0 and Google.Apis.Core v1.32.0, all three of which are still validating.
Please resolve this as soon as possible.

We are currently experiencing high latency in validating and indexing new packages pushed to NuGet.org. We will post an update to https://status.nuget.org when the issue has been resolved. Thank you for your patience.

The issue causing the high latency has been resolved, and an update posted to https://status.nuget.org.

Thanks for the update :)

Fantastic. Published Bogus v21.0.5 and only took 10 minutes for validation. Feels like 10 minutes is a good maximum threshold. :ok_hand:
Also, the Bogus v21.0.1 validation from 6 days ago finally validated. :checkered_flag: :turtle:
Thanks a bunch @chenriksson for fixing the problem and making NuGet work again. :+1:

Over 3 hours for a few packages :( Might as well go to bed.

Just found this thread, cause I was wondering how long it would take. Took 8 Minutes for my small package.
Maybe the size of the package has influence on the duration, too.

@UweKeim That issue you ran into is after validation has completed. There's some lag between NuGet's v2 and v3 pipelines, it sounds like you searched for your package using v2 but then tried to restore the package using v3 before it had been indexed.
 We're working on improving our validation pipeline's speed.

What is the issue with Validating that it is taking so long?

@mwpowellhtx We are working on making the validation faster. You can read up about what happens during validations and work that we are doing in this regard in this blog post  published earlier this year. We have already made some progress to reduce the validation time.
Which packages did you see long validation times for and what was the duration for the validation delays roughly?

@anangaur You're missing the point; validation is hanging up to the point of failure. This never used to happen before.

@mwpowellhtx We understand the pain. The key change from the times this was not a problem is that we have made the essential validations like malware scanning a blocking operation to publish a package. We are trying to make this step as fast as possible.
What is an acceptable delay beyond which you term it a failure, according to you?

@anangaur I'm not sure you do understand; whatever was pushed into production broke validation to the point of failure. If you are going to experiment, then kindly do so offline in a test server. Now my packages are not publishing, validation is timing out, and for no fault of my own.

I just checked with the team and it seems we had a live site incident causing the validation delays leading to validation failures. We have fixed the problem now and also initiated re-flow for all the packages to validate again. Expect this to get fixed soon.
/cc: @skofman1

@anangaur @skofman1 Appreciate y'all looking into that; or if it was a different specific issue.
Incidentally, at least as far as I was concern, if the "time" can be improved great, but the time wasn't that big a deal for me before, really and truly. It didn't take hours, and it didn't stop due to failure, etc, to be clear.

I have a really small library (https://www.nuget.org/packages/PolishVehicleRegistrationCertificateDecoder) and I encountered the same problem. There is still "Validating" status for 3 days now for v1.0.1. For the other versions v1.0.2 / v1.0.3 validation time was less than 5 minutes. Now I just uploaded v1.0.4 which still is "Validating" for half an hour now. Why is it taking so much time sometimes and is my v1.0.1 will be finally validated?

/cc: @skofman1 1.0.1 is still Validating.

@anangaur @skofman1 I see that after your response v1.0.1 was finally published. Can you do the same for the newest one (v1.0.5)?

not fixed for me, all my build depend on this the VersionConverter package :(


Banner for question changes

User Story
As an applicant
I want to be notified if questions have changed between intakes
so that I don't make mistakes while entering information.
Acceptance Criteria

[ ] Questions changed alert
Given that applicant is viewing or editing a draft application started during a previous intake
when the current date & time are in a time period of a subsequent intake
AND the form changed since the previous intake
then an alert will appear saying, "Questions have been changed since the previous intake. Please review the form carefully."

Duplicate of #400


Symmetrization to operate on polar coordinate images?

PyAbel currently operates on coordinate images, as input. abel.Transform() then has a complex process of dividing the image into quadrants, reorienting, (inverse) Abel transform, and then reassembling the image.  This cutting, slicing, and averaging (when symmetric) would be much easier with the image in polar coordinates, where the orientation of all quadrants is correct:

Thoughts?

Interesting idea!
As I understand it, since the transform methods expect cartesian coordinates, you are proposing to just complete the symmetrization step in polar coordinates, right? (I edited the title of the Issue to reflect this, but please change it back if your intent was indeed that the transform methods themselves should be re-formulated to operate in polar coordinates).
While the actual implementation of the "quadrant" symmetrization is a bit complicated (it's hard not to be off by one pixel!), it's fairly simple on a conceptual/mathematical level.
Is the advantage of operating on the polar image simply that we don't need to re-orient the images? Given that we already have the re-orientation code mostly figured out, I'm not sure if this is a huge advantage.
I suppose operating on the polar image would allow you to apply whatever complicated averaging scheme that you wanted, leaving out thin-slices containing artifacts and using whatever symmetry condition you wanted. However, I would think that the decisions of "left+right" and "top+bottom" would cover 99.999% of cases.
Fundamentally, our Abel transform methods are operating on cartesian images, and we are assuming that the input to the software is a cartesian image, typically from a CCD camera (or similar array detector). The coordinate transform completely distorts the image content of the image: pixels at large radius in the cartesian image get squished into single pixels in the polar image, while pixels in the center of the cartesian image get stretched across many pixels in the polar image. One would need to think very carefully about "preservation of pixels" as they transformed from cartesian to polar and back.
Now, if you have Abel transform methods formulated in polar coordinates, and/or a detector that collects data in polar coordinates, then I think that you may want to complete your image symmetrization in polar coordinates.

Arrgh!  I did not think this through.
The Abel transform does follow cartesian coordinates. Each row corresponds to a constant angle (theta), but the radial coordinate, in a polar coordinate image, would be useless for the transform.
I blame lack of sleep due to the summer heatwave in Oz.
Closing this non-issue, polar coordinate images are of no use for the PyAbel Abel transform computation.

I can see the headlines now: "Record temperatures transform Australian man into polar coordinates" :)

;-)


Template With Data

Has anyone been able to get this to work?
This is the example in the plunker demo but it's not actually passing in any values to the template. What do I need to do to pass in an object into my template? I've tried a long list of things so far.
toaster.pop('warning', "Hi ", "{template: 'myTemplateWithData.html', data: 'MyData'}", 15000, 'templateWithData');

Actually just figured it out would be worth updating the demo:
$scope.MyData = {name:'my name'};
toaster.pop('warning', "Hi ", "{template: 'myTemplateWithData.html', data: MyData}", 15000, 'templateWithData');

Hi Jaggi,
sorry that I haven't replied earlier. You could find it in the latest plunk: http://plnkr.co/edit/HKTC1a
Jiri.


[onNodesChange] select: false event is not sent when dragging

Describe the Bug
When using onNodesChange you receive an event when clicking on a node:
{ id, select: true}
When clicking elsewhere you receive an event:
{ id, select: false}
However when you drag nodes, it show them as unselected but it won't send the { select: false } to onNodesChange while the Nodes themselves are correctly updated.
Incidentally when you start dragging directly (not clicking first the node) it shortly set the node to selected but no event { select: true } is sent.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Click a node
Receive an event { select: true }
Start dragging
Do not receive an { select: false }

Expected behavior
Events should reflect what is displayed and computed internally.

Receive an event { select: true } when click/dragging directly
Receive an event { select: false } when dragging start (or end)

OR
Dragging should not unselect
Screenshots or Videos
No response
Platform

OS:macOs
Browser: Chrome
Version: 11.7.4

Additional context
Temporary solution
useOnSelectionChange does not suffer the same issue but it triggers very often (~on hover too which I don't get~ nvm it was my setup)

When you drag a node it should not get de-selected. Where did you see this?

Please re-open if it's still an issue.


Create basic bzlmod setup for rules_pkg.

Adds MODULE.bazel

Has only runtime deps, not build time ones, so we can not to tests yet.
Shows --enable_bzlmod working for one of the examples

rpm and git toolchains not done yet.

They need module extensions
still not clear if that is sufficient, because they are optional for each user

Still not sure how to get the external repo test working.

I think the macos failures are broken infrastructure.


Timestamps say 'Yesterday' when it is today

I'm the proxy for this bug report.
Version: 0.3.13 master #63
Screenshot (emphasis/highlight is mine):

It appears as though the app uses UTC. We're in -6 right now, and at around 6pm (18:00) it flipped to 'Yesterday'.

This is worse when someone posts a message in a room and they are expecting it to be 'Today'. I had a very confused user come up to me and ask why their message was posted "Yesterday" and not "Today". They were concerned that people reading their message would also see 'Yesterday', making their message irrelevant (as the message was time sensitive).

Original post updated to include a bounty.

@pixlwave Please submit a claim on bountysource if you're interested in receiving the bounty for this issue. Thanks!

No worries. I didn’t really fix it for the bounty @turt2live so feel free to move it over to another issue 🙂


Fix broken links in PATRONS.md

I should have double checked! I forgot to check for https when fixing people that had failed to leave http://, even though I explicitly told myself to in my head. Sigh :)

Wow, that was quick!
I'm hoping to make some more meaningful contributions to this project in the future 👍


Discuss Tech Stack

There are a few project layout decisions that need to be made by the website team. Here are some choices:

Do we want to use a frontend styling library like Bootstrap, Tailwind, or something else?
Do we want to use a CSS Preprocessor like Sass, Less, or something else?
How should we organize our file structure?

There are probably other design decisions that I'm forgetting, so make sure to list them out if you think of anything else!

We decided this during today's meeting:

Structure the website as an NPM package or a vanilla website?

Vanilla setup (since we aren’t going to use a CSS preprocessor)

An assets/ folder or separate fonts/, images/, scripts/, etc…?

assets/ folder is the way to go

Vue.js for the schedule?

Tentative yes so far

Frontend library?

Bootstrap

We decided this during today's meeting:

Structure the website as an NPM package or a vanilla website?

Vanilla setup (since we aren’t going to use a CSS preprocessor)

An assets/ folder or separate fonts/, images/, scripts/, etc…?

assets/ folder is the way to go

Vue.js for the schedule?

Tentative yes so far

Frontend library?

Bootstrap


Registering Lifecycle hooks without mixins

I'm trying to register a hook similar to the Lifecycle mixin within my /widgets route component:
  componentWillMount() {
    const route = this.props.route;
    this.props.history.registerRouteHook(route, (location) => {
      console.log('This log is executed.');
      return true; // This should allow transitioning..
    });
  }

However, when I navigate to /widgets and then attempt to navigate elsewhere, the location state is updated via popState, but the route does not change. As commented, the log is executed.
Any tips on how to accomplish this? I'm working on code related to #2006, so that transitions may preload their data asynchronously before the route transition occurs.

Additionally, when I put this code on the root component, all transitions are still blocked, but the console log statement is not executed.

@quicksnap I think what you look for is listenBefore. See History's documentation on Confirming Navigation.


Kosher token pull request

Kosher token first pull request.

I can help stop wasting your time refer this zakimzf/profile#1

close for re-pull request


Repo consolidation

This PR represents an initial attempt at restructuring the eventing-kafka repository to make room for the Kafka related implementations (channel, source, webhook) from the eventing-contrib repository.  It is a proposal only and feedback is welcome.
There are lot of changes in the PR, but mostly it's just changing imports to align with the new structure.  The following image gives an overview of the directory organization / naming...
~/Workspace/GO/src/knative.dev/eventing-kafka> tree -d -L 3 cmd config pkg
cmd
├── channel
│   ├── consolidated
│   └── distributed
│       ├── controller
│       ├── dispatcher
│       └── receiver
├── source
└── webhook

config
├── channel
│   ├── consolidated
│   └── distributed
├── source
└── webhook

pkg
├── channel
│   ├── apis
│   ├── client
│   ├── consolidated
│   └── distributed
│       ├── build
│       ├── common
│       ├── controller
│       ├── dispatcher
│       ├── hack
│       └── receiver
└── source

Specifically, the following questions should be considered...

Channel Naming - The eventing-contrib channel implementation is re-named consolidated, and the eventing-kafka implementation is re-named distributed.  Admittedly these aren't the best descriptors but the intent is to provide something to describe the difference in the architectural approach between the two implementations.  We shouldn't rely on their origin or history when naming them here, as that will be meaningless for new/future users of the implementations.
config/ Location - Confirm that we want to keep the config at the top as is shown or to bury it down next to the pkg/channel/distributed directory?
apis/ & client/ Location - Confirm that we want to keep these dirs under pkg/channel instead of just at pkg/?

/hold

@travis-minke-sap this reorg sounds good to me, waiting for @matzew @lberk and @aliok opinion :smile:
/lgtm

Channel Naming

I don't have a strong opinion. It is hard to name things... In the long run, are we going to merge these 2 channels? If not, what happens if we want to have eventing-contrib kafka channel as a distributed one too?

config/ Location - Confirm that we want to keep the config at the top as is shown or to bury it down next to the pkg/channel/distributed directory?

IMO better keeping this way instead of burying. Easier to do ko apply :)

apis/ & client/ Location - Confirm that we want to keep these dirs under pkg/channel instead of just at pkg/?

Sounds good to me.
/lgtm

I would suggest changing from
pkg
├── channel
│   ├── apis
│   ├── client
│   ├── consolidated
│   └── distributed
│       ├── build
│       ├── common
│       ├── controller
│       ├── dispatcher
│       ├── hack
│       └── receiver
└── source

to
pkg
├── apis
     ├── messaging
     ├── sources
├── client
├── channel (impl)
│   ├── consolidated
│   └── distributed
│       ├── build
│       ├── common
│       ├── controller
│       ├── dispatcher
│       ├── hack
│       └── receiver
└── source (impl)

Since the injection thing is documented in pkg: https://github.com/knative/pkg/tree/master/injection and it uses pkg/apis and pkg/client.

Thanks everyone for their feedback - I'll reply to it all inline here...
@aliok - Agreed naming is hard ; ).  I've heard differing opinions as to whether the long term plan will be to merge the two implementations, or to have them live on side-by-side offering different runtime characteristics.  We'll have to see where that road leads.  I would think, though, that if the eventing-contrib/kafka (consolidated) were to become "distributed", then we'd be merging them since that is the primary architectural difference.  I'm not 100% sold on the naming but don't have anything better so for now (to get started) we'll go with that ; )
@pierDipi - Thanks for the information, I'd not been involved in generating the apis/ or client/ on the knative side as of yet - so I'm happy to move them up under pkg/ if that's where they belong.
@matzew - (from slack thread) Yeah, the new common/ dirs aren't shown and can be created at whatever level we need/want when we start integrating.  For now I'd kept our sandbox/eventing-kafka common/ under distributed to get started and we can move/share things as makes sense going forward.  Also, we can move config/webhook under config/channel/webhook if that is preferable.
I'm working through the quality gates on this PR which flagged a bunch of new stuff since it's treating every file as "new" and found a couple unit-test gaps (the hard-to-test controller construction ; )  and should have the PR ready/passing in the next couple days depending on other commitments.
Once it's passable we can merge and then it will be ready to start migrating eventing-contrib/kafka components in as makes sense.  Thanks again everyone!

I like the pkg/api and pkg/client folder suggestion

I don't have a strong opinion. It is hard to name things... In the long run, are we going to merge these 2 channels? If not, what
happens if we want to have eventing-contrib kafka channel as a distributed one too?

the short story is: both get into this repo.  we than start seeing to share (common) code, like API shape for the channels.
Over time, the goal is - I guess - to have one solid channel w/ concepts from both worlds - if feasable / or configurable

I think to make migration easier, I can start to "flatten" the contrib repo to a structure like:
kafka
  cmd
     channel
     source
     webhook
  config/
     channel
     source
  pkg

Any comments?

Hey everyone - I've finished creating the necessary unit tests and merging in master/ changes, etc...  Last chance to review - tomorrow morning (Thursday US Mountain time) I'll remove the "/ hold" flag and let this move forward.   Thanks again to everyone for their input!

/hold cancel


how to detect change in query param and rerender the page

Version
"react": "^16.2.0",
"react-dom": "^16.2.0",
"react-router": "^4.2.0",
"react-router-dom": "^4.2.2",
Test Case
https://codepen.io/adamchenwei/pen/YeJBxY?editors=0011
Steps to reproduce
Click on Home -> Step 1
Expected Behavior
Go to Step 1 as well as Step 2 render correct dom
Actual Behavior
Empty, nothing renders on the page

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

use this.forceUpdate() after history.push(...)


ContextModule dependency errors manifest as warnings

Bug report

What is the current behavior?
If an error occurs while processing a ContextElementDependency then that error manifests as a warning.
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/gusvargas/webpack-contextmodule-dep-warning-bug
git clone git@github.com:gusvargas/webpack-contextmodule-dep-warning-bug.git
cd webpack-contextmodule-dep-warning-bug
yarn
yarn build
yarn run v1.6.0
$ webpack --mode development
Hash: 84ea86465d90efc8f434
Version: webpack 4.32.0
Time: 69ms
Built at: 2019-05-21 12:58:48
  Asset      Size  Chunks             Chunk Names
main.js  5.31 KiB    main  [emitted]  main
Entrypoint main = main.js
[./src/components sync recursive ^\.\/.*$] ./src/components sync ^\.\/.*$ 183 bytes {main} [built]
[./src/index.js] 33 bytes {main} [built]
    + 1 hidden module

WARNING in ./src/components/foo.js 1:1
Module parse failed: Unterminated regular expression (1:1)
You may need an appropriate loader to handle this file type.
> /invalid js
|
 @ ./src/components sync ^\.\/.*$ ./foo.js
 @ ./src/index.js
✨  Done in 0.94s.

I also included a plugin in the repo that fixes the bug.
yarn build-w-fix
yarn run v1.6.0
$ webpack --mode development --plugin ./FixContextModuleDepWarningsPlugin.js
Hash: 84ea86465d90efc8f434
Version: webpack 4.32.0
Time: 67ms
Built at: 2019-05-21 13:03:39
  Asset      Size  Chunks             Chunk Names
main.js  5.31 KiB    main  [emitted]  main
Entrypoint main = main.js
[./src/components sync recursive ^\.\/.*$] ./src/components sync ^\.\/.*$ 183 bytes {main} [built]
[./src/index.js] 33 bytes {main} [built]
    + 1 hidden module

ERROR in ./src/components/foo.js 1:1
Module parse failed: Unterminated regular expression (1:1)
You may need an appropriate loader to handle this file type.
> /invalid js
|
 @ ./src/components sync ^\.\/.*$ ./foo.js
 @ ./src/index.js
error Command failed with exit code 2.

Notice that when you build with the fix the module's build error fails the build, as expected.

What is the expected behavior?
I would expect the build to fail with the error that occurred while building the ContextElementDependency.
This code determines how the error should manifest:
https://github.com/webpack/webpack/blob/1dc561865ad57d9e862832ccf3579f67a8bbba2d/lib/Compilation.js#L157-L160
The ContextModuleFactory sets dep.optional to true for all ContextElementDependencys:
https://github.com/webpack/webpack/blob/1dc561865ad57d9e862832ccf3579f67a8bbba2d/lib/ContextModuleFactory.js#L144-L146
I think that dep.optional should be set to false. I'm happy to PR the change if that makes sense.

Other relevant information:
webpack version:  4.32.0
Node.js version: v8.9.1
Operating System: macOS 10.12.5
Additional tools:

bump


Investigate special casing FFT size 4. Does this make CompositeFFT faster?

Are there any other sizes that it's worth combining in CompositeFFT? Even if we just delegate to NaiveFFT?


Update to cats 0.9.0

would be nice because it is currently blocking us.

I already did some preliminary work, but we need a monix 2.2.0 release, which should support Cats 0.9.0.
Then we need to update sbt-catalysts-extras to the latest Cats, Monix and ScalaJS versions.

thanks for the update!

https://github.com/monix/monix/releases/tag/v2.2.0 :tada:

https://github.com/47deg/sbt-catalysts-extras/pull/6

@peterneyens I think we're good to go!

sbt-catalyst-extras is updated but not sure the artifacts have propagated or built for central. @juanpedromoreno is that automated on master merges or do we have to manually release it?

sbt-catalyst-extras 0.1.3 is now in maven-central.
CC @peterneyens


Upgrade node

Closes
Notes for after merging:
Everyone will need to make clean_all, switch to node 18, then yarn so that all packages are rebuilt against the new node.
Why this has webpack patches:
Held off on SB7 update until https://github.com/parcel-bundler/parcel/issues/8668 is resolved.
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

export NODE_OPTIONS=--openssl-legacy-provider does not get this working
nor does putting it into the script targets, nor making a make target and putting it in that
Using the patch-package I've come up with here, does work
I suspect we'll need something similar in our examples which use webpack4

For other reviewers, here are the webpack 4 example app links:
https://reactspectrum.blob.core.windows.net/reactspectrum/305000df465b136b5852f6160f9b4a1f3e080d72/verdaccio/publish-stats/webpack-4-build-stats.txt
https://reactspectrum.blob.core.windows.net/reactspectrum/305000df465b136b5852f6160f9b4a1f3e080d72/verdaccio/webpack-4/bundle.js


Cross Compilation for Android Fails With:  error: stack frame size of 4791280 bytes in function 'cmdlineParse' [-Werror,-Wframe-larger-than=]

Few lines of output below:
make[1]: Leaving directory `/home/tj/development/honggfuzz'
[*] 'arm64' libBlocksRuntime available at 'third_party/android/libBlocksRuntime/arm64'
ndk-build NDK_PROJECT_PATH=. APP_BUILD_SCRIPT=./android/Android.mk \
    APP_PLATFORM=android-26  APP_ABI=arm64-v8a \
    NDK_TOOLCHAIN=aarch64-linux-android-clang NDK_TOOLCHAIN_VERSION=clang \
     APP_MODULES='honggfuzz hfuzz hfnetdriver'
********************************************************************
Android PTRACE build: Will prevent debuggerd from processing crashes
********************************************************************
Android NDK: WARNING:android/Android.mk:honggfuzz: non-system libraries in linker flags: -latomic
Android NDK:     This is likely to result in incorrect builds. Try using LOCAL_STATIC_LIBRARIES
Android NDK:     or LOCAL_SHARED_LIBRARIES instead to list the library dependencies of the
Android NDK:     current module
make[1]: Entering directory `/home/tj/development/honggfuzz'
[arm64-v8a] Compile        : honggfuzz <= cmdline.c
/home/tj/development/honggfuzz/cmdline.c:298:6: error: stack frame size of 4791280 bytes in function 'cmdlineParse' [-Werror,-Wframe-larger-than=]
bool cmdlineParse(int argc, char* argv[], honggfuzz_t* hfuzz) {
     ^
1 error generated.
make[1]: *** [obj/local/arm64-v8a/objs/honggfuzz/cmdline.o] Error 1
make[1]: Leaving directory `/home/tj/development/honggfuzz'
make: *** [Makefile:325: android] Error 2
[tj@tj-laptop honggfuzz (master)]$

I am using the latest r20 ndk.

Hi,
Can you post the cmd-line and ndk version you're using to compile it. I've compile honggfuzz for Android more than a year ago, and even I have currently problems with making it to compile.

In any case, I think this clang error is bogus. The code doesn't instantiate a struct on a stack, merely it initializes another struct. We can add proper -Wno-error to the Android makefile if it fixes the compilation for you. Or increase the value for Wframe-larger-than=

Please try with https://github.com/google/honggfuzz/commit/0ba36e7b98db0ed999610f14a87d3179b7eb7f7b - I don't see the Wframe-larger-than problem myself, but I fixed the build for newer NDKs

Sorry just seeing now, I managed to fix by removing the compiler flag, and also saw those issues as well. Now it compiles and I am able to get it running :)
Software code coverage I seem to be struggling with on Android but that may just be my fault.
Thanks!


Can't use typeset-js on OS X 10.10.5

I executed this:
$ npm install -g typeset
And I got
<EMAIL_ADDRESS>/usr/local/lib/node_modules/typeset
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
But I don't have typeset-js when I tried to run it:
zsh: command not found: typeset-js
OS X 10.10.5, iTerm 2, with Oh-My-Zsh.

I've just pushed the latest version to NPM – it should work now. Let me know if not

@davidmerfield It is working now. Thanks for your contribution.

:+1:


Ensure schema cache gets cleaned up and generally re-envision caching

Currently aSource can be given a cache_dir in the yaml spec:
    cache_dir: ./cache

this enables caching of the data and the computed JSON schema describing the data. Both are stored in the directory and then are used to reload the data (if either --dev or --autoreload are set). It seems in certain cases the data may be refreshed but the schema file is not, which can result in mismatches between the two which can make it appear like certain filter fields are not available (because filters are created from the schema).
It's not entirely clear to me under which condition this can happen, since generally the entire cache_dir is deleted in one go so we'd have to some experimenting here.

When I run lumen serve examples/bikes/dashboard.yaml --show for the first time in the repo I get these warnings:
WARNING:param.occupancy: Could not cache 'occupancy' to parquetfile. Error during saving process: [Errno 21] Failed to open local file '/Users/mliquet/work/dev/lumen/examples/bikes/cache/occupancy.parq'. Detail: [errno 21] Is a directory
2021-09-20 10:22:00,409 Could not cache 'occupancy' to parquetfile. Error during saving process: [Errno 21] Failed to open local file '/Users/mliquet/work/dev/lumen/examples/bikes/cache/occupancy.parq'. Detail: [errno 21] Is a directory

@maximlt the problem you are seeing should be fixed by #305

Cannot reproduce these issues anymore.