Basic stream post

Most functionality added. UI may be janky but haven't really gone to lengths with it yet.
Some things in this branch are strictly related to displaying a post, please ignore those.
Still need to handle source and origin, having an actual profile picture in the modal, and application/base64, and possibly some other stuff that I'm forgetting.
Using store crashes the page so...login before trying to create a post.

Some things in this branch are strictly related to displaying a post, please ignore those.

instead of ignoring them, do not pull request the unrelated files

Still need to handle source and origin, having an actual profile picture in the modal, and application/base64, and possibly some other stuff that I'm forgetting.

add todo's to the mark down what needs to be done in the future

Some things in this branch are strictly related to displaying a post, please ignore those.

instead of ignoring them, do not pull request the unrelated files

No they make me feel the good and are harmless.


How to custom path prefix with router base

Hello!
I have website using default locale indonesia and that is also available in english.
What is Expected?
http://mywebsite.com/id/landing/about/
What is actually happening?
http://mywebsite.com/landing/id/about/
Version
nuxt-i18n: 6.15.1
nuxt: 2.14.0
Nuxt configuration
mode: universal
nuxt.config.js
router: {
    base: '/landing/'
},
////
modules: [
    'bootstrap-vue/nuxt',
    ['nuxt-i18n'],
],
i18n: {
    strategy: 'prefix',
    locales: ['id', 'en'],
    defaultLocale: 'id',
    paths: {
      en: '/landing/',
      id: '/landing/'
    },
  }

You can't as far as I can tell. The router.base is considered the root of the site and you can't control anything above that.


+50% Improve performance of address parsing

It turns out that we were de serializing twice in the address parsing logic.
 It is 1 000 000 operations per second for bech32.


Remove CrossPlatformSupport trait

This internal test fixture class isn't needed as Groovy has a built-in method to handle this.

Merged.


Alternative Feature Directory

I like to look at acceptance testing from the customer’s point of view.  One issue that has been brought up a few times is that cucumber tests tend to be kept in the developer’s environment and so they are not easily available/viewable by the customer/tester.
The wiki version of Fit (FitNesse) overcomes this by having all tests in a wiki which is searchable.  Tests are executed from within that environment and the results easily seeable.   But some have technical issues with the environment in which FitNesse executes its tests.
What I propose is something a cross between these two and somewhat how some current requirement/test tools work.   And there may already be something in the works on this.  if that's the cases, please send me a link to it.
Tests (e.g. feature files) would be kept in a separate requirements directory hierarchy, which may or may not parallel the source code hierarchy.    Non-developers would be able to view and possibly alter these tests (under revision control).
At test time, the feature files would be either individually, as a group, or as a composition be submitted to cucumber.   The program could examine the files for tags (ala how cucumber currently works). and create one of more feature files based on the requested tags   The program would keep track of the source path of the feature files submitted.   As cucumber produces results, the output would be placed back into a parallel directory structure. For example, the html result of
customertests/login/mylogin.feature
would be put into
customertestresults/login/mylogin.html
Appropriate links could be added so that results are accessible via the hierarchy structure (to keep everything linked in a browser).   The non-developer would be able to browse the results to see current status of tests that have be run.

Hi, have you looked at www.relishapp.com?
Also https://cucumber.pro is coming...


fix coverage upload

oopsie

:tada: This PR is included in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Accelerated Gradient Boosting

I just read a cool paper on arxiv and thought it might be of interest to the LightGBM team: https://arxiv.org/pdf/1803.02042.pdf

Hmm I am not sure wether this optimization makes sense for non-standard gradient boosting algorithms (such as LightGBM and XGBoost), where you already compute the Hessian in adition to the Gradient...
Theoretically, the added benefit of computing the Hessian of the loss function should be essentialy equivalent to a method such as Nesterov's accelerated gradient (since it is just a way to provide further information to the optimization technique, in order to make de descent more efficient)...
It looks like it is really an improvement over the original Friedman's gradient boosting, but with "Hessian/Newtonian boosting" that just might not be the case.
It would be really cool to try it out and see if it makes learning faster, but a lot should have to be changed in LightGBM's source code in order to implement this.

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.

See also Lu et. al. (2020) and specifically their discussion in section 6, which seems cognizant of some of the observations here by @julioasotodv.


Add global button style btn-loklak-blue

This PR adds a global button style that can be reused : btn-loklak-blue, and changes several buttons in different pages to use this style.
Two styles vars are introduced that can be configured anytime :
$btn-loklak-blue: #55acee;
$btn-loklak-blue-hover: #0084B4;

Fixes Issue #420

@sudheesh001 I think there is not so much to review here. Could you check and merge this, please?


allow for folders for file caching

Each pull request should address a single issue and have a meaningful title.
Description
Fix the previous breaking change that prevents folders from being created for file based caching allow folders for file caching increases performance and organization when there are significant numbers of cached files.
Checklist:

[ ] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

---------Remove from here down in your description----------
Notes

Pull requests must be in English
If the PR solves an issue, reference it with a suitable verb and the issue number
(e.g. fixes 12345)
Unsolicited pull requests will be considered, but there is no guarantee of acceptance
Pull requests should be from a feature branch in the contributor's fork of the repository
to the develop branch of the project repository

You also can't just remove a feature/bug/whatever you want to call it that production applications are relying on without a proper deprecation cycle, and without a proper solution to the problem that subdirectories fix. i.e. it could just be built to automatically subdirectory based on the first x characters in the string or something similar.

You also can't just remove ... that production applications are relying

Agreed. Like I said this was totally unintentional, but I believe that is because the feature was unintentional to begin with (or at least entirely undocumented/commented). We can make this a priority but I'm not comfortable making this call by myself. If you have time and capacity to flesh out this PR to be a proper "allow subdirectories" emendation it would save time if we go that route.

I’m not suggesting you put it back permenantly but by implementing this hotfix solves the problem short term so people can upgrade without breaking entire systems (the other functionality would have always been broken for them anyways) and then working on a long term solution that solves the problem would be secondary.
On Wed, Jun 2, 2021 at 8:50 AM, MGatner @.***> wrote:
You also can't just remove ... that production applications are relying
Agreed. Like I said this was totally unintentional, but I believe that is because the feature was unintentional to begin with (or at least entirely undocumented/commented). We can make this a priority but I'm not comfortable making this call by myself. If you have time and capacity to flesh out this PR to be a proper "allow subdirectories" emendation it would save time if we go that route.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/codeigniter4/CodeIgniter4/pull/4765#issuecomment-853142123] , or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAHKIMWLQU4MMB5CTP4HPK3TQZHMRANCNFSM455PCAJA] .

We for sure won't be hotfixing (i.e. pushing to master and re-releasing). If you mean providing this solution in the repo you can do this with the content you already made by pointing at your branch. Update composer.json as follows:
	"require": {
		"php": "^7.3 || ^8.0",
		"codeigniter4/codeigniter4": "dev-feature/fix-file-cache",
	},
	"repositories": [
		{
			"type": "vcs",
			"url": "https://github.com/colethorsen/codeigniter4"
		}
	]

The forums are back up. If you PM me your Slack email I will invite you directly.

Superseded by #5008


SyncError- when installing ocs using gitops.

I get this error message installing Openshift storage cluster(ocs) on OCP in Azure.
SyncError
Failed sync attempt to 346f5eb3d256ff1b04d1130b2d39d99670f07cf8: one or more objects failed to apply, reason: StorageCluster.ocs.openshift.io "ocs-storagecluster" is invalid: spec.storageDeviceSets.dataPVCTemplate.spec.resources.requests.storage: Invalid value: "Gi": spec.storageDeviceSets.dataPVCTemplate.spec.resources.requests.storage in body should match '^(+|-)?(([0-9]+(.[0-9])?)|(.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|(eE?(([0-9]+(.[0-9])?)|(.[0-9]+))))?$'

@ncolon, do you know if this issue has already been addressed in this PR (https://github.com/cloud-native-toolkit/multi-tenancy-gitops/pull/256)?


request daemon mode support

English Only (except for bug reporting).
This program needs to run permanently on the server

There are plenty ways to run any program as background. For example: screen/tmux/nohup.

None of these methods are convenient, and they are even less convenient in an embedded environment


Bug overlapper modal in case perform transaction successfully with Polkadot vault account

Describe the bug
Bug overlaped modal in case perform transaction successfully with Polkadot vault account
To reproduce the bug
Steps:

Perform transaction successfully with Polkadot vault account
Observe the displayed screen

Actual: Overlaped modal

This error cannot be reproduced anymore because SendFund has undergone some changes.

All modals have been improved to avoid modal overlap issues.
TransactionDone is no longer a modal but a separate screen.

@ThaoNguyen998 please re-check and close this issue

I can't reproduce the bug on the newest version
-> Close issue.


About function wrfpywind

Hi sir, can you tell me whar's your function wrfpywind . I can't find it. Thank you!

Hey, that actually a package I wrote, which you can find here (sorry for the misnomer), but if you're not looking to get data from your own WRF forecasts, you can probably just disable anything from wrfpywind.

Thank you for your reply. I will change my data to test .


feat: add lance image type handling in pydantic

See #600

what's the status here?

@changhiskhan sorry this stalled on my side. I can finalize it first week of January or hand it over.

The Windows failure is probably bad luck but the pydantic1x failure looks legitimate (complaining about pydantic_core and this PR does add a pydantic_core import)


Not able to connect to cluster when using Azure CLI

This is autogenerated. Please review and update as needed.
Describe the bug
When am trying to connect to an AKS cluster using Azure CLI, its getting this error.
Command Name
az aks get-credentials
Errors:
The command failed with an unexpected error. Here is the traceback:
API version 2022-06-01 does not have operation group 'managed_clusters'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", line 112, in handler
    client = self.client_factory(self.cli_ctx, command_args) if self.client_factory else None
  File "/usr/lib/python3/dist-packages/azure/cli/command_modules/acs/_client_factory.py", line 27, in cf_managed_clusters
    return get_container_service_client(cli_ctx).managed_clusters
  File "/usr/lib/python3/dist-packages/azure/mgmt/containerservice/_container_service_client.py", line 492, in managed_clusters
    raise ValueError("API version {} does not have operation group 'managed_clusters'".format(api_version))
ValueError: API version 2022-06-01 does not have operation group 'managed_clusters'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az aks get-credentials --resource-group {} --name {}

Expected Behavior
Environment Summary
Linux-5.19.0-1-amd64-x86_64-with-glibc2.34, Debian GNU/Linux bookworm/sid
Python 3.10.7
Installer: DEB

azure-cli 2.40.0

Extensions:
azure-devops 0.24.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.0.0

Additional Context

route to CXP team

@yonzhan Will it be routed automatically or should I be doing some steps to route to CXP team?

automatically with CXP Attention label

@strange2x Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@strange2x I wasn't able to reproduce this issue at my end. I had a look at the below details from your environment:
Linux-5.19.0-1-amd64-x86_64-with-glibc2.34, Debian GNU/Linux bookworm/sid
Python 3.10.7
Installer: DEB

This is not the official Azure CLI published by Microsoft. Please see https://github.com/Azure/azure-cli/issues/19640.
Action Plan:
For now, please follow https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt to install Azure CLI on stable/GA versions of Debian, like 11 Bullseye, instead of sid.
https://wiki.debian.org/DebianUnstable

Sid is forever doomed to being unstable.

Hope this helps.

@strange2x I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you had any updates on this. Awaiting your reply.

@strange2x The action is currently pending on you see the above suggestion. Please feel free to reopen this thread, if you need any further assistance on this. We would be happy to help.

I used 'install script (any)' option. but still cannot get auto-completion sorted

I had changed the version to a lower one and it worked then and now I have changed the machine and its working perfectly


🐛 Bug Report: Github event on delete won't generate the right location for deletion

📜 Description
When a new project is registered by the scaffolder a subsequent delete event won't delete the resources registered.
👍 Expected behavior
The location should be deleted, and the orphan cleanup should kick in.
👎 Actual Behavior with Screenshots
On the log it says that 0 entities were removed
backstage-7c7d5f4677-bqnv5 backstage-production {"level":"debug","message":"Received event for topic github.repository","plugin":"catalog","service":"backstage","span_id":"4e117962f485e043","target":"github-provider:audibene","trace_flags":"01","trace_id":"adff3f5641efa8dff5dac519e0dbf89e"}
backstage-7c7d5f4677-bqnv5 backstage-production {"level":"debug","message":"removed, 0 entities: [\"location:default/generated-4e435bcea65ba7568ff7590efc06f2a6cfc44af4\"]","plugin":"catalog","service":"backstage","span_id":"4e117962f485e043","trace_flags":"01","trace_id":"adff3f5641efa8dff5dac519e0dbf89e"}
backstage-7c7d5f4677-bqnv5 backstage-production {"level":"debug","message":"Removed entities for deleted repository platform.test-backstage","plugin":"catalog","service":"backstage","span_id":"4e117962f485e043","target":"github-provider:audibene","trace_flags":"01","trace_id":"adff3f5641efa8dff5dac519e0dbf89e"}
backstage-7c7d5f4677-bqnv5 backstage-production {"level":"info","message":"[06/Sep/2024:09:13:49 +0000] \"POST /api/events/http/github.repository HTTP/1.1\" 202 21 \"-\" \"GitHub-Hookshot/1a50080\"","service":"rootHttpRouter","span_id":"4e117962f485e043","trace_flags":"01","trace_id":"adff3f5641efa8dff5dac519e0dbf89e","type":"incomingRequest"}

👟 Reproduction steps
Register a project with the scaffolder using this config:
- id: publish
  name: Create Github repository
  action: publish:github
  input:
    allowedHosts: ['github.com']
    description: This is ${{ parameters.projectName }}
    repoUrl: ${{ parameters.repoUrl }}
    defaultBranch: 'develop'
    repoVisibility: 'private'
- id: register
  name: Register app on backstage's catalog
  action: catalog:register
  input:
    repoContentsUrl: ${{ steps.publish.output.repoContentsUrl }}
    catalogInfoPath: '/catalog-info.yaml'

then on github side (assuming webhook is already configured) trigger a deletion
📃 Provide the context for the Bug.
It seems that the code generate a location with the blob url https://github.com/Bonial-International-GmbH/backstage/blob/9112efc364d24f134881e9c09db1323fdfcc4165/plugins/catalog-backend-module-github/src/providers/GithubEntityProvider.ts#L284 but the location created by the scaffolder, uses the tree url https://github.com/Audibene-GMBH/platform.test-backstage/tree/develop/catalog-info.yaml
should the location method return a list with both urls or should tree always be used?
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Sorry to hear that you're having issues. Are you running a recent version of backstage?
I believe @pjungermann made some recent fixes to events in #26016

I just came back from vacation and will have a look at which end there might be an issue.
Seeing the register step at your template, though, it seems like you don't use the entity provider to discover and add/register your entities/catalog files.
The entity provider and its event-driven updates are for entities that belong to it and are not meant for otherwise registered entities like static locations are (manual) registrations.

Regardless of that, I will have a look at blob vs tree. At some places, we seem to support both. Might be the right action here. I'm not sure yet.

I came to this thread because I just finished a debugging session of tree vs blob.
I could register my entity using blob 1 time. Then immediately (or after a few minutes) it would throw the Warning: entity not found. When trying to register again it said it existed already and only allowed me to refresh. But then the /refresh threw a 404. And searching in the catalog showed no results.
In the DB, the final_entity was created with the component and the appropriate location existed as well. After manually deleting each I could register the component again and reproduce the issue several times.
I experienced this with 4 repos and one was successful after 1 DB deletion. Checking the final_entities, there were 2, one with /blob and one with /tree. I then modified all register links to /tree and it worked as it should from the beginning.
I have been, however, able to add multiple entities in the past with /blob.
Will research more on the why, but wanted to echo on this issue. We're running Backstage 1.25.x

bump


Add Jan-Ken-Puzzle

Title:
Jan-Ken-Puzzle (Python)
Body:
Jan-Ken-Puzzle solver using Dynamic Programming (memoization and BT cut).
Are you working on this? - Yes

Working on it


KCC closes at start - Windows 10 - 5.1.2

I don't know what can cause this, but KCC doesn't even start on my HP Laptop, as soon as it opens, the programs closes itself.

@retardBoy the latest binary works, which is version 5.5.2.  The download link through the KCC website and also on the KCC GitHub readme is pointing to the 5.1.2 binary.  If you change the URL to https://kcc.iosphe.re/Windows/KindleComicConverter_win_5.5.2.exe this will work.

I can't believe it, it worked, thank you very much bro.

seems OK, closing the issue


Skip migration test when transactions not avalible

Addresses #43
Not every developer will have mongodb setup using mongos or as a replica set. This skips the failing test when the functionality is not available. I could not test whether it does run the test when it is available as I had to go of documentation, so please check this.

Good point, thank you.
I'll merge this guy in the evening.

Also, just to share how I do this, it is very comfortable to create a free atlas instance to do development things there
https://www.mongodb.com/cloud/atlas
You don't need mongodb (even dockers) on your own system n that case. I like it :-)


fix: use IdsId as type for connector ID

What this PR changes/adds
It changes the type of the connectorId field from String/URI to IdsId in all IDS classes. Whenever the ID is mapped to Infomodel classes, IdsId.toUri() is used.
Why it does that
To have a consistent handling of the connector's ID in IDS classes, as currently the connector uses different ID formats for its own ID (id-value and urn:connector:id-value).
Further notes
Uses ConnectorIdUtil.resolveConnectorId() to set the connector's ID in ConnectorServiceSettings, as I missed this when removing the code duplications.
Linked Issue(s)
Closes #2022
Checklist

[ ] added appropriate tests?
[x] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report
Base: 63.87% // Head: 64.34% // Increases project coverage by +0.46% :tada:

Coverage data is based on head (623198b) compared to base (820a034).
Patch coverage: 68.57% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2031      +/-   ##
==========================================
+ Coverage   63.87%   64.34%   +0.46%
==========================================
  Files         781      780       -1
  Lines       16514    16521       +7
  Branches     1076     1073       -3
==========================================
+ Hits        10548    10630      +82
+ Misses       5518     5441      -77
- Partials      448      450       +2

Impacted Files
Coverage Δ

...ipart/dispatcher/sender/SenderDelegateContext.java
100.00% <ø> (ø)

...type/MultipartCatalogDescriptionRequestSender.java
7.69% <0.00%> (ø)

.../api/multipart/controller/MultipartController.java
57.14% <ø> (ø)

...pi/multipart/handler/ContractAgreementHandler.java
70.58% <ø> (ø)

...pi/multipart/handler/ContractRejectionHandler.java
78.94% <ø> (ø)

.../api/multipart/handler/ContractRequestHandler.java
58.33% <ø> (ø)

...i/multipart/handler/DescriptionRequestHandler.java
72.54% <ø> (ø)

...ultipart/handler/EndpointDataReferenceHandler.java
100.00% <ø> (ø)

...tor/ids/core/service/ConnectorServiceSettings.java
1.17% <0.00%> (+0.10%)
:arrow_up:

...aspaceconnector/ids/core/util/ConnectorIdUtil.java
0.00% <0.00%> (ø)

... and 25 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Tag description from piwebapi

Hello,
Is there any way to retrieve the tag description and use it in a graph?
Greetings,
Casper

Any update for this question/ features ideas? thanks

Can you provide more details on the request?

Is it possible to get the description value of a Pi Tag ?

But where do you want to use that?

Maybe in tooltip when you search for a tag, like PiVision, or concat with tag name, and the description dissapear when you select the tag.

Fixed in #107


updated package.json

Task linked: RND-2930 NPM update and test all active themes

Task linked: RND-2930 NPM update and test all active themes


Make the %%spark magic support proxy

Enterprise Spark clusters are typically behind a firewall which is not accessible directly. It helps a lot if %%spark supports proxy.

Can you be a little more specific about what kind of network configurations you have in mind?

It looks like Spark has no special support for proxies, so the JVM runtime proxy support (using the http.proxyHost, https.proxyHost, http.proxyPort, and https.proxyPort properties) should work.  That also means there is no way to apply a proxy only to Spark—it will apply to the entire kernel, so it may be necessary to use http.nonProxyHosts for access to other addresses if the proxy doesn't pass them through.
If the environment needs two different proxies, one for accessing the Spark cluster and one for accessing external sites, I don't think the JVM runtime will support that.

The Spark UI embeds links in a way that requires URL rewriting. Here's a (forked) plugin that adds basic Spark UI access from within JupyterLab.
https://github.com/s22s/jupyterlab-spark-ui-tab
I suspect another common use case for needing a proxy is running notebooks launched from JupyterHub. We're running into the same problem where all the super cool %%spark links aren't accessible due to assumptions about hostname, context path etc.


Update readme

📋 Description
Updating readme

Summary by CodeRabbit

New Features

Introduced a new "AMRIT" health technology platform in the README.
Added a new "Credits" page to acknowledge contributors.
Enhanced footer with a link to the credits section.

Bug Fixes

Corrected spelling of "gallery" in the about page comments.

Documentation

Updated README to reflect changes and provide clearer instructions for running the project locally.
Added detailed contributor information in the new credits markdown file.

We can also consider adding credits for original theme


Where to get example data

In the example it is using PTC_ged dataset (data/PTC_ged/). Where is that located?
From the code it seems like these should be json files with a 'ged' field.

Mainly, I want to get my data into the correct format that this code can ingest, so an example json file would be helpful.

Also how is batching actually used? The collate function is never called https://github.com/khoadoan/GraphOTSim/blob/e92bec19ce85347054d01a209c864ed92d14b88c/python/train.py#L346
Additionally in all the similarity computations torch.mm is used rather than torch.bmm...
It seems like this code would work for batch size = 1, but would mix graph pairs if batch size > 1

I have the same problem. Could you please upload a link of the datasets?

RSP, I never got a response but I think all their datasets are standard in pytorch geometric: https://pytorch-geometric.readthedocs.io/en/latest/modules/datasets.html# under GEDDataset
Also, LAPJV is called 1-by-1 on each graph pair in the batch - it is not a parallelized operation:
https://github.com/khoadoan/GraphOTSim/blob/e92bec19ce85347054d01a209c864ed92d14b88c/python/models.py#L638

This library used DGL but it can be easily converted to PyTorch Geometric


Failed to connect to Jupyter notebook

This is likely a bug in your jupyter install. I've seen this when a dll load failure occurs (Python 3.8 can have this problem)
You might have the new Output tab that shows the Jupyter server output. Can you check and see what it says? If not can you post your console log? Thanks.

Thanks for reporting this issue.
To help you better, please could you fill in the issue template to help us help you better.
E.g. python version, OS, etc.
Also, please could you try installing the following version and letting us know how it goes https://github.com/microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build

When I input show python interactive window after pressing F1, it pops up what is shown above
However, when I input some code on the bottom of interactive window where type code... is and press shift enter, the interactive window disappears
After that, when I press shift enter on the editor tab, the Jupyter can run normal.

The interactive window is supposed to close itself when an error occurs (it looks like it's waiting till the next execute to do so, that's a separate issue).
Can you include your console log? I can't tell you what the problem is without seeing what Jupyter output.

The interactive window is supposed to close itself when an error occurs (it looks like it's waiting till the next execute to do so, that's a separate issue).
Can you include your console log? I can't tell you what the problem is without seeing what Jupyter output.

How can I check the console log.?  The terminal and output don't show anything.

Help | Toggle Developer Tools, right click, save as and upload here.
There should also be a new 'Output' tab for 'Jupyter' (depending upon which build you're using).

Is that one?

Yes but we need the entire console. That's just the error being thrown (essentially the thing we put into the message that pops up).

How about this?

Still not enough. Can you just upload the entire file? Just drag it onto github should be sufficient.

-1576717226470.log

You must have a filter enabled. The log doesn't show anything except what your picture shows.

Can you turn off filtering in the Console tab? There should be 100s of messages in the log.

But how? I cannot find any pressing button related to uploading file.

Here's what mine looks like:

On the left you can filter by type, make sure you pick the top most item
Then right click and you should get this to show up:

Click on Save As and then upload that file here.

This is what mine looks like after reopen the vscode. But I didn't know which ones I shall upload.

If you right click it and save save as, it will upload them all.

No, just one column. I have tried

-15767182460832.log
Is this one?
By the way, I want to update python extension mannually, but the azure pipelines shows Build no Found

Yes that log was correct, but it looks like you didn't repro the problem. It would be best if you restarted VS code, repro'd the problem, then uploaded the log.
This would be the page for the latest CI that I can find:
https://dev.azure.com/ms/vscode-python/_build/results?buildId=55442&view=artifacts&type=publishedArtifacts
Not sure what Azure page you're looking at. Maybe we restricted access for some reason.

Yes that log was correct, but it looks like you didn't repro the problem. It would be best if you restarted VS code, repro'd the problem, then uploaded the log.
This would be the page for the latest CI that I can find:
https://dev.azure.com/ms/vscode-python/_build/results?buildId=55442&view=artifacts&type=publishedArtifacts
Not sure what Azure page you're looking at. Maybe we restricted access for some reason.

I will try the latest version and check if the problem can be fixed.
Shall I clear the history console log?
This is where I used to download insider extensions.
https://dev.azure.com/ms/vscode-python/_release?view=mine&definitionId=3&_a=releases

Don't clear the console log, but rather restart VS code (or run the 'Reload Window' command). Then repro the problem, and then upload the log.

This is where I used to download insider extensions.
https://dev.azure.com/ms/vscode-python/_release?view=mine&definitionId=3&_a=releases

That location would be the spot where the latest insider's is dropped. There's newer bits in the spot I linked to.

-1576718877669.log
The latest version cannot fix the problem

Thanks that gives at least a clue as to what is going on. It looks like your default kernel we created on a previous run is not valid for some reason.
This error here:
[W 09:27:42.955 NotebookApp] Kernel not found: python37464bit8a84406a13554133b698d173d8217538
Is what is causing the 501 error I believe.
You might be able to get this to work if you go to a command prompt where you can run 'jupyter kernelspec list' and remove the bad kernel.

On my machine I can do this by simply going to C:\Users\rchiodo.REDMOND\AppData\Roaming\jupyter\kernels

delete them?

Just the second one, The first one is installed by something else.

It may still not work though. We might not be installing the kernel correctly for some reason.

If it doesn't work again, there should be an 'Output' tab in VS code that says 'Jupyter'. Maybe that will give us more information as to what happened with that kernel.

-1576719559352.log
This one? I filtered Jupyter  log and saved them

-1576756340554.log

No sorry, it looks like this:

Did you change something? That latest error is you have specified a server URI in this setting:
    "python.dataScience.jupyterServerURI": "local",

It looks like you have it set to "https://hostname:8080"

We've been discussing possible reasons for your initial 501 error, and we think we might need to wrap kernel creation, and when it fails ask the user to pick a different one.
Internal notes:

Change the JupyterSession createSession calls to wrap error and throw a new exception specifying kernel invalid
In the interactiveBase, handle this error for both change kernel and start server and ask the user to pick a different kernel.

We've been discussing possible reasons for your initial 501 error, and we think we might need to wrap kernel creation, and when it fails ask the user to pick a different one.
Internal notes:

Change the JupyterSession createSession calls to wrap error and throw a new exception specifying kernel invalid
In the interactiveBase, handle this error for both change kernel and start server and ask the user to pick a different kernel.

No, it didn't make any difference.

Did you change something? That latest error is you have specified a server URI in this setting:
    "python.dataScience.jupyterServerURI": "local",

It looks like you have it set to "https://hostname:8080"

No, I didn't make any change like what you said.

Shall I remove vscode and python completely and reinstall them again?

What is the value of python.dataScience.jupyterServerUri
Or more simply, run the command 'Open Settings UI' and see what this value is:

You shouldn't have to reinstall python or VS code.

default value

What does the settings UI show?

Shall I roll back to Nov stable Release?

@AeneasZhu That won't be necessary.
We have applied a fix #9227. Pleas wait for another 1/2 hour for the CI/CD run its course and update the insiders build with the latest.
Please feel free to retry the latest insiders build within 1/2 hour or so.
The fix is, we'll prompt the user to select another kernel.
So, if it fails you'll be notified immediately and you'll have the ability to select a different kernel.
Please do let us know how this goes. And thanks for being patient and helping us get to the bottom of this issue.

@DonJayamanne

Is this one? I have installed that, but it didn't make any sense.

Thanks for getting back, looks like you are having some other problem. I'll create another build tomorrow with additional logging and fixes.
Apologies once again

@DonJayamanne  It can work on the latest version(55700), but it also pops  up select another kernel and I have to select python interactive

@AeneasZhu apologies for the bug.
@rchiodo had already fixed this and it will be in the next build, some time in the next few hours

@DonJayamanne
It works as before after installing 55725 version

@AeneasZhu Thanks for the confirmation.
I'm going to close this issue for now.
If you come across any additional issues, please feel free to create a new issue.


added a solution to resolve the workflow error

failed to run git: fatal: not a git repository (or any of the parent directories): .git

solve the issue in another pull request


Be consistent with SMILES, InChI(Keys) standardized from Wikidata

Until https://github.com/lotusnprod/lotus-search/commit/ffcd80bd3363568aa8d779f57fa878f835cb0251 we were using the original SMILES and not the standardized one. But descriptors, InChI(Keys), etc are generated on the standardized one, leading the new tests failing.
@bjonnh We need to decide how to proceed, probably keeping the original SMILES somewhere but not as it is right now

Fixed but worth a check


Stuck after python install

No error message.

That's because the BuildTools_Full.exe is really slow to install. Go take a coffee... it will take a long time...

Yeah, I should probably indicate somewhere that it'll take a really long time.

+1, I cancelled the install 4 times assuming it hung before coming here are realizing it's just silent

Alright, I added a spinner 👍  Thanks everyone for reporting!

Spinner that is spining for an hour means nothing if there is no percentage when downloading is involved...

It's been more than 5 hours... should i still wait?

More than a day. Gosh...

[Resolved] Once you failed for some reason, go to Task manager and kill the BuildTools... process and try installing again.

Same issue, no BuildTools process during job execution on Windows Server 2016 in Jenkins BATCH command.  On the server, this takes < 1-2 minutes.  Hangs on Python installation Successfully.  Something is amiss.

also got the same issue...
[09BC:1DA4][2018-06-12T16:17:40]e000: MUX:  Stack:    在 System.Xml.XmlTextReaderImpl.Throw(Exception e)
在 System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res, String arg)
在 System.Xml.XmlTextReaderImpl.ParseDoctypeDecl()
在 System.Xml.XmlTextReaderImpl.ParseDocumentContent()
在 System.Xml.XmlTextReaderImpl.Read()
在 System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
在 System.Xml.XmlDocument.Load(XmlReader reader)
在 Microsoft.Devdiv.Bootstrapper.DownloadManager.DownloadXml(String url, Int32& returnCode)
[09BC:1DA4][2018-06-12T16:17:40]i000: MUX:  Failed to download the update xml file from http://go.microsoft.com/fwlink/?LinkID=659005 Setup will not be updated.
[09BC:1DA4][2018-06-12T16:17:40]i052: Condition '( (CommunityCheck_DetectKey = 1) ) AND (CurrentOperation = "Install") ' evaluates to false.
[09BC:1DA4][2018-06-12T16:17:40]i052: Condition '((WDExpress_DetectKey = 1) ) AND (CurrentOperation = "Install")' evaluates to false.
[09BC:1DA4][2018-06-12T16:17:40]i052: Condition '( (VSWinExpress_DetectKey = 1) ) AND (CurrentOperation = "Install")' evaluates to false.
[09BC:1DA4][2018-06-12T16:17:40]i052: Condition '(VersionNT < v6.3) and ((not netfxfullredist_43_DetectKey_Exists) or (netfxfullredist_43_DetectKey_Version < v4.5.50709) or (netfxfullredist_43_DetectKey_Release < 378758))' evaluates to false.
[09BC:1DA4][2018-06-12T16:17:40]i052: Condition '(VersionNT = v6.3) AND (netfxfullredist_43_DetectKey < v4.5.25000)' evaluates to false.

it's copied from the build_tool _log.txt.   killing BuildTools in taskmgr as suggested by bluemind didn't make it.


cypress: 9.6.0 -> 9.6.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 9.6.1 with grep in /nix/store/2whklz9zzby0p2l99c5q72j07079i41q-cypress-9.6.1
found 9.6.1 in filename of file in /nix/store/2whklz9zzby0p2l99c5q72j07079i41q-cypress-9.6.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
cypress

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2whklz9zzby0p2l99c5q72j07079i41q-cypress-9.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/e45180fda2c96d7cf15bc45997fbd9d84f5b6625.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2whklz9zzby0p2l99c5q72j07079i41q-cypress-9.6.1
ls -la /nix/store/2whklz9zzby0p2l99c5q72j07079i41q-cypress-9.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cypress

Maintainer pings
cc @thorstenweber83 @mmahut for testing.

Closing as this is updated to 10.0.3 in #176933


Follow XDG Base directory specs

Hi!
On Linux, elan stores files in ~/.elan.
It may be better to follow the XDG desktop specification.
In particular,
Configuration files should go under $XDG_CONFIG_HOME (if empty, $HOME/.config/)
Data files should go under $XDG_DATA_HOME (if empty, $HOME/.local/share/)

I agree, that the XDG standard should probably be the default, but it is already possible to set ELAN_HOME.


Fix: Date field in mediaviewer needs to be more specific

What is the date field here supposed to indicate? Is it the upload date? The date the photo/video/document was created? The date the file was last modified? The field needs to be more specific what the date is telling the user. Consider the need for more date fields.

No date is provided with the file, so the date field will be removed.


fix: Correct link in quick-start-guide-and-build.md

Need to correct link in quick-start-guide-and-build.md related to the API Documentation.
Pull Request
Description
Please include a summary of the change and which issue is fixed. Also, provide relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Correct typo in link address related to the API Documentation file.
Type of change
Please delete options that are not relevant.

[ X] Bug fix (non-breaking change which fixes an issue)
[ X] Documentation update

Testing
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Test Configuration:

Java: v17
LPVS Release: v1.4.2
fix related to link in documentation file

Checklist:

[x] My code follows the style guidelines of this project
[x] My code meets the required code coverage for lines (90% and above)
[x] My code meets the required code coverage for branches (80% and above)
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@o-konoval  please sign the commit

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.91%. Comparing base (f649078) to head (6ba9960).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #469   +/-   ##
=========================================
  Coverage     90.91%   90.91%
  Complexity      491      491
=========================================
  Files            47       47
  Lines          1750     1750
  Branches        210      210
=========================================
  Hits           1591     1591
  Misses           93       93
  Partials         66       66

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@o-konoval please sign the commit

Added sign-off in the commit. Please review again.


add actions also on VM details screen

The following scenario is not too user friendly:

pick a VM
a detail is shown
check if it is the one I wanted to start (e.g. check the disks or description or something)
yes, I want to start it, press esc, find the VM again and press run

It would be good to have this actions on the details as well.

Done


Watching files

Hi, thanks for your work. I'm trying to use mdast-lint, and am thinking it'd be wonderful to have something like a --watch option built into mdast.

It’s certainly a goal. I think it can be useful. Currently, you can use markdown-linter for atom with live hinting, and Schiba which is a markdown previewer but also with mdast-lint.

Thanks. Yeah, I don't want to need Atom or Schiba to do my linting...
Maybe I could help with a PR? My idea is that all plugins attached to the current session of mdast get executed every time the target file saves. How correct is this?

Pretty correct :) You’ll probably want to watch (e.g., with mikael/watch), and intercept here

Watch library tip: mikeal/watch wraps the old fs.watchFile, which inefficiently polls the filesystem. The newer fs.watch uses platform-specific notification systems when possible, and is usually better every way.

Is it possible/easy to implement, to use either fs.watch when available and fall back to fs.watchFile?

I searched a bit: looks like bevry/watchr does that.

Nice!

I took a look at what babel uses, and it looks like it uses chokidar, which seems well-prepared for production use. Can I go ahead with a PR?

I have no experience with it, but judging the list of implementations, I’d say yes :)

Awesome, I'll submit a PR within the next few days.

So I started working on the PR.  A naive implementation of --watch would cause an infinite loop because of this.
My question is: which part of the .mdastrc is causing this?

Oh, it's "output": true, duh. I'll continue to work on the PR.

:+1: good luck

I think I'm close to being done, I need to figure out how to avoid the infinite loop caused by "output": true.
As far as I know, there are two ways to define this "output" property: via .mdastrc and via CLI's --output option. What is the best way to get a single final verdict for "output" that covers both possibilities?

After hours of fighting race conditions pertaining to the "infinite loop" problem, I'm starting to question whether we should even allow the user to watch a file that mdast will rewrite over.
Because, think about it - wouldn't it be awkward to see your file change soon after you save it? The user should instead really be storing the post-rewrite content into a different file.
Instead of fighting the race conditions, I'm thinking it could be a better idea to just avoid them entirely.
Other than that, I think I'm pretty much done. @wooorm What do you think?

I agree that files which would normally be regenerated, should not (initially) be output by the watch command.
However, mdast can also output to different directories and to non-markdown files, an example is mdast compiling it’s docs to man/.
We could turn off writing to the file-system, but that would prohibit the use of mdast to create files, like the aforementioned man pages.
Alternatively, we can check if the content changed instead inside the watch: mdast generates the same output as the input document, when it created the input itself.

Thanks. How about this: when a file being rewritten is also being watched, we give the following warning:
You're watching file blah.md, but mdast is configured to rewrite over the file.
To avoid race conditions, mdast will not rewrite over the file while you're watching,
but instead hold the output in memory. When you exit the watch with a SIGINT (CTRL+C),
then mdast will rewrite over the file with the latest output.

....and we do as the warning says.
I think this is a good compromise among everything. What do you think?

I’m fine with that!
Also, could you create a pull-request / branch with your work? That means I can help you with writing this, reply with comments, steer you in the right directions, &c.

Yeah of course - I was just preparing up for a PR. Coming soon

:+1:

Let's continue the discussion in #57.


Change hypothesis_jsonschema private module name

The commit https://github.com/Zac-HD/hypothesis-jsonschema/commit/1d98b386503b2291eab45d0290bf61c0a8761452 introduces a change in hypothesis_jsonschema internal structure that affects schemathesis.
It is just a patch, until something is found to avoid usage of the lib internals ?

Hello @hlobit :)
Cool, thank you for noticing this - there was no hypothesis-jsonschema release with these changes, and I'd like to use a public API if possible. Some compatibility shim should be used anyway to support hypothesis-jsonschema versions after & before these changes. Or we can pin hypothesis-jsonschema version with these changes when it will be out - not sure actually what would be the best way.
Maybe we can involve @Zac-HD into the discussion? What do you think about having such public API for registering string formats in hypothesis-jsonschema  itself?

There was no hypothesis-jsonschema release with these changes

Yes there is 0.9.13 released today and that's how I noticed this :)

It's out as of about an hour ago, since I discovered an array canonicalisation bug. So requiring >=0.9.13 would work.
What's your use-case for this? I'm keen to keep my public api as small as possible, but cam grow it if needed!

For example, we have some custom format, e.g. for payment card numbers - and we declare it in the schema + use validation for it via jsonschema + connexion:
@draft4_format_checker.checks("card_number")
def is_card_number(value):
    # Validation based on Luhn algorithm

So it is triggered for all input values with format: "card_number".
And it is very nice to generate valid card numbers to get deeper in the code with generated input
It is basically our use-case :)

I've opened Zac-HD/hypothesis-jsonschema#29 to track that and discuss the design :smile:


LSTM Support

Hi, I've been trying to implement a time series prediction model using RNN, but I've been getting an Only 1 subgraph is currently supported. error despite following the example from here https://www.tensorflow.org/lite/convert/rnn and Keras LSTM Example.
My model is like this:
model = Sequential([
    LSTM(5, activation='relu', return_sequences=True,
            input_shape=(STEPS, FEATURES)),
    Flatten(),
    Dense(FEATURES, activation='relu', name='output')
])

You probably want to unroll your LSTM layer before trying to run with TFLu by setting unroll=True. I don't believe there is support for the LSTM fused op in TFLu currently.

That worked! Thanks a lot!!


composite example does not run in Windows

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
What part(s) of the article would you like to see updated?
Creating an action metadata file
 works for ubunut and mac.  For windows, / does not work.
suggest the following change:
        - run: echo "${{ github.action_path }}" >> $GITHUB_PATH
          shell: bash
        - run: goodbye.sh
          shell: bash

Additional information
No response

@robert-s-lee
Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

@robert-s-lee - Thank for raising this issue. I agree, your suggested change would avoid using the forward slash so would be usable across the OSs.
The change required is, therefore, as follows.
On lines 87-88 of the docs file content/actions/creating-actions/creating-a-composite-action.md, change:
- run: ${{ github.action_path }}/goodbye.sh
  shell: bash

to:
- run: echo "${{ github.action_path }}" >> $GITHUB_PATH
  shell: bash
- run: goodbye.sh
  shell: bash

Hi, can I get started with this issue

Ok. Patients people. I see what to do. I'm doing more than one thing. And learning everything on my own.

Ok. Patients people. I see what to do. I'm doing more than one thing. And learning everything on my own.

Can i givr some help on this?

Can y'all help me and update my
Profile

@kum9748ar

Hi, can I get started with this issue

Please do! 🙇♂

Hello, Can I please work on this?

@allprogrammers One of the writers reviewed and suggested a change for this issue in this comment. You can follow this writer's review to open a PR with a fix ✨


Continuous Deployment - buildspec error

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Next.js
Amplify APIs
Authentication, REST API, GraphQL API, Storage
Amplify Categories
auth, storage, function, api, hosting
Environment information

  System:
    OS: macOS 13.0
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 43.13 MB / 32.00 GB
    Shell: 5.8 - /usr/local/bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.4.1 - ~/.nvm/versions/node/v16.13.2/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 107.0.5304.87
    Firefox: 106.0.5
    Safari: 16.1
  npmPackages:
    @next/eslint-plugin-next: ^12.1.0 => undefined (12.1.2)
    @types/node: 17.0.23 => 17.0.23
    @typescript-eslint/parser: ^5.16.0 => undefined (5.10.1)
    eslint: 8.12.0 => 8.12.0
    eslint-config-airbnb: 19.0.4 => 19.0.4
    eslint-config-airbnb-typescript: ^16.1.4 => 16.2.0
    eslint-config-mantine: 1.1.0 => 1.1.0
    eslint-config-next: 12.1.2 => 12.1.2
    eslint-plugin-import: ^2.25.4 => undefined (2.25.2)
    eslint-plugin-jsx-a11y: ^6.5.1 => 6.5.1
    eslint-plugin-react: ^7.29.4 => undefined (7.29.1)
    eslint-plugin-react-hooks: ^4.3.0 => undefined (4.3.0)
  npmGlobalPackages:
    @aws-amplify/cli: 8.2.0
    amplify-category-video: 3.9.2
    corepack: 0.10.0
    eslint: 8.18.0
    firebase-tools: 10.2.1
    lerna: 4.0.0
    local-ssl-proxy: 1.3.0
    npm: 8.4.1
    react-native-cli: 2.0.1
    yarn: 1.22.18

Describe the bug
Since yesterday the continuous deployment fails in the build step while cloning the repository. There have been no code changes that might cause this issue.

Expected behavior
Successful deployment as it was working before.
Reproduction steps

Start deployment

Build Overrides:

Code Snippet
No response
Log output

2022-11-08T07:58:26.553Z [INFO]: Git SSH Key acquired
2022-11-08T07:58:26.639Z [INFO]: # Cloning repository: git@bitbucket.org:account/app.git
2022-11-08T07:59:25.083Z [INFO]: Agent pid 150
2022-11-08T07:59:25.276Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
                                 Cloning into 'app'...
                                 Warning: Permanently added the RSA host key for IP address 'xxx.xxx.xxx.x' to the list of known hosts.

                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at 15f6xxxxx trigger build
2022-11-08T07:59:25.338Z [INFO]: Successfully cleaned up Git credentials
2022-11-08T07:59:25.338Z [INFO]: # Checking for Git submodules at: /codebuild/output/src972127685/src/app/.gitmodules
2022-11-08T07:59:25.347Z [ERROR]: !!! CustomerError: The commands provided in the buildspec are malformed. Please ensure that you have properly escaped reserved YAML characters. If you have a ':' character in your command, encapsulate the command within quotes
2022-11-08T07:59:25.347Z [INFO]: # Starting environment caching...
2022-11-08T07:59:25.347Z [INFO]: # Environment caching completed
Terminating logging...

aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response

@mojansen Can you please share your App ID?

@mojansen Can you also please share your build spec? Also, are you using the AMPLIFY_SKIP_BACKEND_BUILD environment variable to skip your backend builds?

@Narrator the App ID is d31sui9syw3mhg.
I'm not using the mentioned env variable. Please see the amplify.yml below (the additional amplify push command was added due to issues with the deployment of the amplify-video category):
version: 1
applications:
  - backend:
      phases:
        preBuild:
          commands:
            - "# Install required dependencies "
            - "# jq is to create a proper parameters.json file"
            - # yum install jq -y
            - yum clean metadata
            - npm i amplify-category-video -g
        build:
          commands:
            - amplify -v
            - amplify video -v
            - "# Execute Amplify CLI with the helper script"
            - amplifyPush --simple
            - amplify push -y
            - echo mainvod | amplify video get-info
            - cp aws-exports.js ../shared-react/src/aws-exports.js
            - cp aws-video-exports.js ../shared-react/src/aws-video-exports.js
    frontend:
      phases:
        preBuild:
          commands:
            - yarn
            - echo "AMPLIFY_ENV=$AMPLIFY_ENV" >> .env
        build:
          commands:
            - yarn build
      artifacts:
        baseDirectory: .next
        files:
          - "**/*"
      cache:
        paths:
          - node_modules/**/*
    appRoot: apps/web

@mojansen Please remove this line from your YAML: - # yum install jq -y. If you want to comment it out from your YAML, do this:
# - yum install jq -y

Or surround it in quotes like so:
"# yum install jq -y"

We have recently made improvements to our CI/CD system to be more stringent about validating the build spec. That's why your build is failing.
Please make the suggested changes and let us know if your build continues to fail. Thank you!

@Narrator it works now. Thank you for the quick help!


Integration with Hippo

https://github.com/deislabs/hippo-cli is the command line interface for interacting with a Hippo instance.
To simplify the user experience, it would be gerat if there was a Hippo plugin for Spin which would allow the Spin CLI to interact with a Hippo instance.

This issue is marked as P0 but is 8 months old.  Is it still current?  Is the feature being discussed now covered by spin deploy?

I believe so. I'm in favor of closing it.


Use tsconfck to parse tsconfig files

This is only partially finished.  I'm seeing strange test errors where my absolute path is repeated, and I don't know why.
There may also need to be changes to handle the now-async functions within the cli, I haven't tested that part yet.
But this is at least a start I think.

Eh, not worth making everything async


Unable to modify backend auth resources

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d10f4nc5uip2ry
Region
us-west-1
Amplify Console feature
Backend builds
Describe the bug
Cannot edit Auth whatsoever.
Any attempt to edit or remove my auth ends with this error after amplify push:
Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete

I've seen many other issues suggesting to pull the repo, but this is not a sync issue in my case.  I've pulled, pushed, it doesn't matter, the issue cannot be fixed that way.
Expected behavior
amplify auth update
....change some setting...
amplify push y

should successfully update
amplify auth remove y
amplify push y

The above commands should remove my Auth.
I'm afraid that all I can do is delete my project completely and start over.  The fact that this is possible makes it maybe a little to risky to use Amplify in the first place.  Hopefully this can be resolved without that.
Reproduction steps
No Idea
Build Settings
No response
Additional information
No response

Hi @siegerts ,

amplify -v = 4.52.0
The project was created using the CLI, however certain aspects were edited in the Cognito user pool UI.
You caught me, I put the wrong command in the question.  I've edited it.  In my testing I used the correct command
amplify auth remove

Based on the issue I'm seeing in cloud formation I've tried several methods now to update my GraphQL Api, which I did find was expired.
1. I've added the line
"APIKeyExpirationEpoch": "-1"
to my amplify > api > myApi > parameters.json
2. I've edited my API key in AppSync > myApi > settings to no longer be expired.
Still no change.

logged in to mess with this to see this today:

Not sure I'm making progress here...

If you want to delete the API Key created by amplify CLI you would have to set CreateAPIKey to 0. The parameters GraphQL transformer accepts are documented here.
You could also try to extend the API Key expiration time by running amplify update api and updating auth settings for the API.
When the API Key extension done using the AppSync console does it using control plane and does not sync with Amplify CLI as it uses Cloudfomration for managing resources.

@yuth - I can't run amplify auth update.  That's the whole problem here.  My updates won't go through

Hey all, I closed this.  Though I'm quite worried about the fact this kind of lock up is possible, I've deleted the amplify project and started over.  I have to make the decision to move forward.  Thanks all for your time.


use task weaver independently + uniquely

datatonic will do well to use taskweaver only rather than all three frameworks together.

duplicate

duplicate


⚠ Bofrost.at has degraded performance

In 81547d0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1308 ms

Resolved: Bofrost.at performance has improved in d82f42a.


Add Aqua; badges

The tests pass with Julia Version 1.11.0-beta1 so who knows what is wrong with nightly.


Updated gnubg (1.04.000-1010-x86_64)

Should this caveat be kept? (In case the user uses something else as --appdir)

Still required.


Version 1.16.1 is absent in linux repo

VSCode Version: 1.16.0
OS Version: Ubuntu 17.04

Steps to Reproduce:

sudo apt-get update
sudo apt-get upgrade
(Repository: https://packages.microsoft.com/repos/vscode stable main)

Same here.
In the application shows there is a update, but when you run the commands it shows as the latest version is the 1.16.0.
I went even further and removed the code package, and when I try to install it the version 1.16.0 is installed.

It's now uploaded https://packages.microsoft.com/repos/vscode/pool/main/c/code/, the .rpm is still in progress

Any news about rpm version?

+1 still waiting for the RPMs to update (OpenSUSE and Fedora)

This should be resolved now, we had some signing issues.


[1.3.z] Adjust release checker to special verifications for 1.3.z branch

Summary
For 1.3.z branch we need to follow old release format 1.3.z.Final
Please check the relevant options

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Release (follows conventions described in the RELEASE.md)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[ ] Example scenarios has been updated / added
[ ] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

Latest release: 1.3.1.Final
[failure] current-version: 1.3.1.Final
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028253830/job/27714955453
[failure] “Final” qualifier is missing after patch version
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028308661/job/27715072121
[failure] major and minor versions don’t match 1.3
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028335895/job/27715132547
[failure] the next-version in project.yaml is not valid. Patch version of the next release must be one upper than the latest
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028349277/job/27715163132
[failure] the next-version in project.yaml is not valid. "Final-SNAPSHOT" qualifier is missing after patch version
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028366005/job/27715200834
[success]
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/10028371614/job/27715213505


Update logstage-core, ... to 1.2.0

About this PR
📦 Updates

io.7mind.izumi:logstage-core
io.7mind.izumi:logstage-rendering-circe
io.7mind.izumi:logstage-sink-slf4j

from 1.0.10 to 1.2.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.7mind.izumi" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.7mind.izumi" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #294.


kvm/ssh: fix getcwd() error for qemu ssh

Calling any command inside QEMU VM through SSH (especially /enterexec for entering) causes following error:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
getcwd() is failing because of missing PWD enviroment variable when SSHing to the VM. Now, it's done by sshd_config. For lkvm, variable is set properly by default.
cc @coreos/rkt-kvm-maintainers

lgtm

Very, very strange as we are using same userspace in qemu as in lkvm.

@jellonek Right, it's weird. But also when I put static env binary to the stage1 and call it directly by:
ssh [options] env,
for lkvm PWD is set, for qemu - it's not

PWD should be a built in variable from bash shell, so imo this deserves for deeper study why these stages are different.

I have to agree with @jellonek, as you are probably hiding the symptoms here instead of hitting the cause.
shell-init .. error .. getcwd means that the bash that is being spawned doesn't know where it is being run. @jjlakis can you please check where /proc/self/cwd is going in your qemu enter-ssh session and compare the result with lkvm one?
Also, if at the end of the day we find out that bash is really being spawned in a weird place, the cleanest fix is probably to add a WorkingDirectory= property to its unit.

@lucab looks like nothing is here
QEMU:
lrwxrwxrwx 1 root root 0 Sep 19 14:51 cwd -> /proc/188
root       188  0.0  1.2  14096  3204 pts/0    Ss   14:51   0:00 -bash
LKVM:
lrwxrwxrwx  1 root root 0 Sep 19 14:55 cwd -> /proc/167
root       167  0.0  1.2  14096  3176 pts/0    Ss   14:54   0:00 -bash

This is by the way failing while cleaning, on semaphore.

@lucab still if we don't have a resources to investigate this - imo adding "a cure" which hides the real problem is better to leaving this issue as it already is.
@jjlakis do Intel have someone who could look on this deeper?
@sur - maybe you can help?
If there is no one who could catch the gap, I think that it would be a better choice to merge this instead waiting for real inspection what is really going on.

@jellonek I'm worried we don't have time to look on this deeper now, since this workaround is satisfies us at the moment.
I can at least fix this seamphore cleaning problem if there's a wish to merge this "cure" + add following issue.

Sounds bad, but if we don't have any other choice...

I need a bit of investigation on this, and I think it actually requires investigation on qemu side.
It looks like the error message above is coming from the bash spawned by sshd in stage1, which has a cwd the GECOS field specified in stage1 /etc/passwd for root, currently /root. This is created at login time over the 9p filesystem, and sshd/bash seems really unhappy about it. Changing this directory to some other path not backed by 9p makes the problem go away.
Your patch here just make the symptom goes away (which is fine if we don't have any better solution) but I have the feeling this will bite us again later in different context, so it needs at least a tracking issue and a description of the actual root cause (which I fear may be somewhere in bash, qemu or 9p virtio). And a rework for the tests :)

@sameo mentioned yesterday that they may have already encountered and fixed this 9p-qemu-getcwd issue, so it may be worth looking into directly integrating ClearLinux kernel+qemulite instead of working around it here.

@lucab This one may fix the root issue: https://github.com/01org/qemu-lite/commit/b621abbc642911f50b163f7129617c2814ecd9c7

@jjlakis there seems to be an upstream fix (at least in qemu-lite) available, bumping to the next release. Do you think you can tackle this?

From what I saw in /var/lib/rkt/pods/.../stage1/rootfs there's no '/root' directory, so how 9p would mount this dir, if it's not existent? I think this patch works, because dir tree is created by make file:  "/root/" and "/root/.ssh". So just adding "mkdir /root" at begginging of sshd-prep.service should work. Or I'm missing something?

@lukasredynk /root is created at some point at runtime, possibly by stage1-kvm-enter ensureKeysExistInPod(). Then it is in turn chmod/chown-ed by sshd-prep.service. As far as I understand, these two operations are happening on the two different sides of the 9p mount (creation: host, chmod/chown: guest), so I see something can get weird/race-y there.
Can you guys please check if just shipping an empty /root/.ssh/authorized_keys in stage1 rootfs is enough to fix this? Just to be clear I would be happy if we could remove more of the mkdir/chown/chmod magic from sshd-prep.service, instead of adding more.

I'm almost sure that serving empty /root/.ssh/authorized_files will ensure that /root dir will exist, but i'm not sure that it could help with this issue. chown/chmod is there because we try to ensure that rkt can be built on any system account not needing root privileges.
I can elaborate on this later (when i will be back from pl pycon where i'm right now) - i mean why this is done in exact that way at the moment.

Problem still exists in this: https://github.com/rbradford/rkt/tree/qemu-lite version containing all CC kernel and qemu patches, especially mentioned one. It's using this version of qemu-lite as a hypervisor (its commits).
@s-urbaniak Fix doesn't solve the problem but we looks like we will aim at upstreaming CC patches anyways, we just need additional performance testing.
@s-urbaniak @sameo @lucab @jellonek @lukasredynk

@chao-p do you think this issue is qemu related ? It seems that 9pfs is being involved here...

Following up with further investigation on this: I'm not excluding that this may have some root cause deep in 9p, but definitely bash is also involved here. I tried replacing the current stage1 bash with a newer bash from debian without the workaround in this PR, and I'm not seeing the getcwd problem anymore.
Assigning to myself for further narrowing down, and trying to get a newer bash in stage1.

It turned out to be a problem due to cross-compiled bash. I'm not sure why this shows up only on rkt qemu-9p, but it is definitely fixed by https://github.com/coreos/coreos-overlay/pull/2272.

Superseded by https://github.com/coreos/rkt/pull/3388, closing.


Installation fails inelegantly when GOPATH is not set

While I'm not surprised that the installation script failed because my GOPATH wasn't set, I had to read the installation script to figure out why, since it wasn't clear from the error message.
Here's a reproduction of the error.
fosterd@fosterd-a02 maintainers % make
./hack/install-maintainers.sh
go build github.com/dims/maintainers: copying /var/folders/xt/0sbwl11j167fjmjjpxjrs5fc0000gp/T/go-build3664102535/b001/exe/a.out: open /bin/maintainers: operation not permitted
make: *** [install] Error 1
fosterd@fosterd-a02 maintainers % echo $GOPATH

fosterd@fosterd-a02 maintainers % export GOPATH=$HOME/go
fosterd@fosterd-a02 maintainers % make
./hack/install-maintainers.sh
maintainers installed to /Users/fosterd/go/bin

I'm also curious why this is building from github.com/dims/maintainers, instead of kubernetes-sigs?

cc @MadhavJivrajani

I'm also curious why this is building from github.com/dims/maintainers, instead of kubernetes-sigs?

module name and paths need to be updated - https://github.com/kubernetes-sigs/maintainers/blob/main/go.mod#L1
/assign @RaghavRoy145

/assign

/remove-lifecycle stale

Closing on account of https://github.com/kubernetes-sigs/maintainers/pull/23 being merged!


Rename PersonType to Person

Looks like someone already renamed PersonType to Person, and missed a few.

Thanks, can you also rename AnimalType while you at it?


Fix/Hyprland/Workspaces: Window Rewrite on multiple non-overlapping bars

About the Problem
An issue exists when using the Window Rewrite feature on Hyprland/Workspaces. The issue manifests only when the user has all_outputs = false on their configuration and moves a window from one of monitor A's workspaces to one of monitor B's workspaces. When that happens, the window's icon vanishes, and can only be seen again if the bar is restarted.
This happens because on this setup, not all workspaces exist accross all bar instances. The way that window moving works is that it "cuts" the icon from workspace 1 and "pastes" it to workspace 2, avoiding having to re-process the window's icon. However, since the origin workspace might not exist on one of the bar's instances, the window is rendered empty.
About the Solution
This PR introduces a new map Workspacess::m_orphanWindowMap which will now hold every window that couldn't be assigned to a workspace. This is then used when moving windows around if the origin workspace is not present on that bar's instance.
Related PRs
Although #2809 also fixes the same issue, it does so by fetching the clients data on every call to Workspaces::update(). The solution being introduced here should hopefully be enough to avoid what might be a resource-intensive call.
CC: @zjeffer @khaneliman

building it now to test it out

Err... maybe not. Old behavior on reboot. Gonna have to investigate again

Err... maybe not. Old behavior on reboot.

You should be able to change the minimum catch2 version in meson.build. I had the same issue with the arch package.

Err... maybe not. Old behavior on reboot.

You should be able to change the minimum catch2 version in meson.build. I had the same issue with the arch package.

Yeah, i'm creating a branch that just lowers that version again just for testing until I can spend a little bit of time on the proper way of passing the nixpkgs-master catch2_3 package as the dependency to use.

@Syndelis so after rebooting a couple times. It looks like there's still something weird going on for the initial boot behavior. The icons might not render but I can drag them to another monitor and then back and see the icons.

As a side note, we should definitely remove catch2 as an actual build/runtime dependency, and use it only for test-runner builds. Also, it probably should be a git submodule, rather than a system lib dependency.

@Syndelis so after rebooting a couple times. It looks like there's still something weird going on for the initial boot behavior. The icons might not render but I can drag them to another monitor and then back and see the icons.

I've just installed the newly built version with ninja -C build install and rebooted my system; everything seems fine. Does launching new programs not get their icons rendered in your bar? Or have you got some programs starting before Waybar does?

I have two bars, one on each monitor. Workspace 1 is assigned to one monitor and the rest on the other. Waybar runs as a systemd service on login and other applications are launched via hyprland on login. The other applications started via hyprland on login are what don’t get rendered. With this PR they at least show after I drag them to the other monitor and render again dragging back to their workspace.

The other applications started via hyprland on login are what don’t get rendered. With this PR they at least show after I drag them to the other monitor and render again dragging back to their workspace.

I'd guess the applications are getting ophaned on both bars, but I'm unsure of what could be causing that. Could you verify that with this patch?
diff --git a/src/modules/hyprland/workspaces.cpp b/src/modules/hyprland/workspaces.cpp
index 3f85b975..b15680bd 100644
--- a/src/modules/hyprland/workspaces.cpp
+++ b/src/modules/hyprland/workspaces.cpp
@@ -222,6 +222,7 @@ void Workspaces::doUpdate() {
       if (windowPayload.incrementTimeSpentUncreated() < WINDOW_CREATION_TIMEOUT) {
         notCreated.push_back(windowPayload);
       } else {
+        spdlog::info("Orphaning window {}/{} on bar {}", windowPayload.getAddress(), windowPayload.repr(*this), m_monitorId);
         registerOrphanWindow(windowPayload);
       }
     }

The other applications started via hyprland on login are what don’t get rendered. With this PR they at least show after I drag them to the other monitor and render again dragging back to their workspace.

I'd guess the applications are getting ophaned on both bars, but I'm unsure of what could be causing that. Could you verify that with this patch?

Yeah, I see a bunch of orphaning window stuff on boot.
Jan 08 22:36:28 khanelinix systemd[3178]: Started Highly customizable Wayland bar for Sway and Wlroots based compositors..
Jan 08 22:36:28 khanelinix waybar[3396]: [2024-01-08 22:36:28.890] [info] Using configuration file /home/khaneliman/.config/waybar/config
Jan 08 22:36:28 khanelinix waybar[3396]: [2024-01-08 22:36:28.893] [info] Discovered appearance 'dark'
Jan 08 22:36:28 khanelinix waybar[3396]: [2024-01-08 22:36:28.893] [info] Using CSS file /home/khaneliman/.config/waybar/style.css
Jan 08 22:36:28 khanelinix waybar[3396]: [2024-01-08 22:36:28.900] [info] Hyprland IPC starting
Jan 08 22:36:28 khanelinix waybar[3396]: [2024-01-08 22:36:28.902] [info] Registering for Hyprland's 'windowtitle' events because a user-defined window rewrite rule uses the 'title' field.
Jan 08 22:36:29 khanelinix .waybar-wrapped[3396]: ../gobject/gsignal.c:2088: type 'GtkWindow' is already overridden for signal id '73'
Jan 08 22:36:29 khanelinix .waybar-wrapped[3396]: ../gobject/gsignal.c:2088: type 'GtkWindow' is already overridden for signal id '72'
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.010] [info] Registering for Hyprland's 'windowtitle' events because a user-defined window rewrite rule uses the 'title' field.
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.285] [info] Bar configured (width: 1880, height: 64) for output: DP-3
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.289] [info] Bar configured (width: 5080, height: 64) for output: DP-1
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.296] [info] Bar configured (width: 1880, height: 64) for output: DP-3
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.416] [info] Orphaning window 3391520/<U+F08B9> on bar 1
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.416] [info] Orphaning window 3391520/<U+F08B9> on bar 0
Jan 08 22:36:29 khanelinix .waybar-wrapped[3396]: Unable to replace properties on 0: Error getting properties for ID
Jan 08 22:36:29 khanelinix .waybar-wrapped[3396]: Unable to replace properties on 0: Error getting properties for ID
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.792] [info] Orphaning window 339c7d0/<U+F066F> on bar 1
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.792] [info] Orphaning window 339c7d0/<U+F066F> on bar 0
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.793] [info] Orphaning window 33a2220/<U+F066F> on bar 1
Jan 08 22:36:29 khanelinix waybar[3396]: [2024-01-08 22:36:29.794] [info] Orphaning window 33a2220/<U+F066F> on bar 0
Jan 08 22:36:30 khanelinix waybar[3396]: [2024-01-08 22:36:30.190] [info] Orphaning window 33a8e30/<U+EB1C> on bar 1
Jan 08 22:36:30 khanelinix waybar[3396]: [2024-01-08 22:36:30.418] [info] Orphaning window 33b5c60/<U+F269> on bar 1
Jan 08 22:36:30 khanelinix waybar[3396]: [2024-01-08 22:36:30.471] [info] Orphaning window 33a0c80/<U+F059> on bar 1
Jan 08 22:36:31 khanelinix waybar[3396]: [2024-01-08 22:36:31.010] [info] Orphaning window 33e4750/<U+F269> on bar 1
Jan 08 22:36:37 khanelinix waybar[3396]: [2024-01-08 22:36:37.499] [info] Orphaning window 33b5c60/<U+F144> on bar 0
Jan 08 22:36:40 khanelinix waybar[3396]: [2024-01-08 22:36:40.340] [info] Orphaning window 33cf640/<U+E795> on bar 1
Jan 08 22:36:40 khanelinix waybar[3396]: [2024-01-08 22:36:40.450] [info] Orphaning window 33d9820/<U+E795> on bar 1
Jan 08 22:36:59 khanelinix .waybar-wrapped[3396]: Status Notifier Item with bus name ':1.74' and object path '/org/ayatana/NotificationItem/steam' is already registered
Jan 08 22:37:17 khanelinix waybar[3396]: [2024-01-08 22:37:17.885] [info] Orphaning window 33ce150/<U+F1B6> on bar 1
Jan 08 22:37:17 khanelinix waybar[3396]: [2024-01-08 22:37:17.887] [info] Orphaning window 33ce150/<U+F1B6> on bar 0

Yeah, I see a bunch of orphaning window stuff on boot.

Could you check if this patch does it for you, @khaneliman ?
diff --git a/include/modules/hyprland/workspaces.hpp b/include/modules/hyprland/workspaces.hpp
index d2006fcc..ae936bdf 100644
--- a/include/modules/hyprland/workspaces.hpp
+++ b/include/modules/hyprland/workspaces.hpp
@@ -28,6 +28,7 @@ class Workspaces;

 class WindowCreationPayload {
  public:
+  WindowCreationPayload() = default;
   WindowCreationPayload(std::string workspace_name, WindowAddress window_address,
                         std::string window_repr);
   WindowCreationPayload(std::string workspace_name, WindowAddress window_address,
@@ -174,7 +175,7 @@ class Workspaces : public AModule, public EventHandler {
   // Map for windows stored in workspaces not present in the current bar.
   // This happens when the user has multiple monitors (hence, multiple bars)
   // and doesn't share windows accross bars (a.k.a `all-outputs` = false)
-  std::map<WindowAddress, std::string> m_orphanWindowMap;
+  std::map<WindowAddress, WindowCreationPayload> m_orphanWindowMap;

   enum class SortMethod { ID, NAME, NUMBER, DEFAULT };
   util::EnumParser<SortMethod> m_enumParser;
diff --git a/src/modules/hyprland/workspaces.cpp b/src/modules/hyprland/workspaces.cpp
index 3f85b975..2c54a8b0 100644
--- a/src/modules/hyprland/workspaces.cpp
+++ b/src/modules/hyprland/workspaces.cpp
@@ -130,7 +130,7 @@ auto Workspaces::parseConfig(const Json::Value &config) -> void {

 void Workspaces::registerOrphanWindow(WindowCreationPayload create_window_paylod) {
   if (!create_window_paylod.isEmpty(*this)) {
-    m_orphanWindowMap[create_window_paylod.getAddress()] = create_window_paylod.repr(*this);
+    m_orphanWindowMap[create_window_paylod.getAddress()] = create_window_paylod;
   }
 }

@@ -222,6 +222,10 @@ void Workspaces::doUpdate() {
       if (windowPayload.incrementTimeSpentUncreated() < WINDOW_CREATION_TIMEOUT) {
         notCreated.push_back(windowPayload);
       } else {
+        spdlog::info("Orphaning window {}/{} on bar {}. No workspace {} on that bar. Workspaces here:", windowPayload.getAddress(), windowPayload.repr(*this), m_monitorId, windowPayload.getWorkspaceName());
+        for (const auto& workspace : m_workspaces) {
+          spdlog::info("\t {}:{}", workspace->id(), workspace->name());
+        }
         registerOrphanWindow(windowPayload);
       }
     }
@@ -316,6 +320,15 @@ void Workspaces::onWorkspaceCreated(std::string const &workspaceName,
       }
     }
   }
+
+  for (const auto& [orphanWindowId, windowPayload] : m_orphanWindowMap) {
+    if (windowPayload.getWorkspaceName() == workspaceName) {
+      spdlog::info("De-orphaning window {} because of Workspace {} created on bar {}", orphanWindowId, workspaceName, m_monitorId);
+      m_windowsToCreate.push_back(windowPayload);
+    }
+  }
+
+  std::erase_if(m_orphanWindowMap, [workspaceName](auto pair) { return pair.second.getWorkspaceName() == workspaceName; });
 }

 void Workspaces::onWorkspaceMoved(std::string const &payload) {
@@ -376,6 +389,10 @@ void Workspaces::onWindowClosed(std::string const &addr) {
       break;
     }
   }
+
+  if (m_orphanWindowMap.contains(addr)) {
+    m_orphanWindowMap.erase(addr);
+  }
 }

 void Workspaces::onWindowMoved(std::string const &payload) {
@@ -407,7 +424,8 @@ void Workspaces::onWindowMoved(std::string const &payload) {

   // ...if it was empty, check if the window is an orphan...
   if (windowRepr.empty() && m_orphanWindowMap.contains(windowAddress)) {
-    windowRepr = m_orphanWindowMap[windowAddress];
+    windowRepr = m_orphanWindowMap[windowAddress].repr(*this);
+    m_orphanWindowMap.erase(windowAddress);
   }

   // ...and then add it to the new workspace

This sould de-orphan windows as soon as their workspaces are created

Yeah, I see a bunch of orphaning window stuff on boot.

Could you check if this patch does it for you, @khaneliman ?
This sould de-orphan windows as soon as their workspaces are created

Didn't seem to change behavior. https://gist.github.com/khaneliman/0787f1f898c3c9d4b2d641416bc8b3ae
EDIT: reading the output... is hyprland reporting the workspace with the silent command as the name? Does the getWorkspaceName just need to clean up that extra information?

Definitely seems like it. However I also got some other bugs where windows may not show and/or never disappear. I guess it's time to refactor out that m_workspacesToCreate/m_workspacesToDestroy duo and actually create/destroy them when required; it's just becoming a huge burden to develop features around.

This solved it for me.
diff --git a/include/modules/hyprland/workspaces.hpp b/include/modules/hyprland/workspaces.hpp
index ae936bd..52fb41d 100644
--- a/include/modules/hyprland/workspaces.hpp
+++ b/include/modules/hyprland/workspaces.hpp
@@ -40,7 +40,15 @@ class WindowCreationPayload {
   bool reprIsReady() const { return std::holds_alternative<Repr>(m_window); }
   std::string repr(Workspaces& workspace_manager);

-  std::string getWorkspaceName() const { return m_workspaceName; }
+  std::string getWorkspaceName() const {
+    std::string workspaceName = m_workspaceName;
+    std::string searchString = " silent";
+    std::size_t found = workspaceName.find(searchString);
+    if (found != std::string::npos) {
+      workspaceName.erase(found, searchString.length());
+    }
+    return workspaceName;
+}
   WindowAddress getAddress() const { return m_windowAddress; }

   void moveToWorksace(std::string& new_workspace_name);

This solved it for me. I just threw together something real quick to test the theory.

Can you check if 9e08512 yields the same results?

This solved it for me. I just threw together something real quick to test the theory.

Can you check if 9e08512 yields the same results?

Yep, still works after removing my test commits and using your latest commit! Thanks!

Nice work guys!


[choreo] Event marker refactor

C++, Java and Python deserialization changes have been tested. Ready for review.


cloudstorage(ticdc):  write meta file if not found and add ut for 10137

What problem does this PR solve?

Issue Number: ref #10137
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
 `None`.

/retest-required


WP1455 Add Dockerfile

@adrianclay can you provide a description of why you adding docker here?

@Davidslv updated

Moved to #254


Adapting for Music AI?

Hey @drahoslove
First of all, thank you for this project. It is really nice and looks/plays really well.
I was wondering if you would be interested in adapting your project for Music AI? Either as a front-end or stand-alone app?
Here is my Piano Music AI implementation but I desperately need help with front-end / app.
https://github.com/asigalov61/GIGA-Piano
Please let me know if this is something that may interest you.
Thank you.
Sincerely,
Alex

Hi @asigalov61,
thank you.
I tried your GIGA-piano in the Colab, and it looks nice.
I have some questions:

You used the word "desperately". Are you under some pressure? Could you tell me more about the project?
Is it some university project, part of some business idea, or something you do in your free time, just for your own enjoyment?

I see that you also reached out for help to the authors of some other piano projects.
One of them is a web app too, but one is a desktop app, and one is a VTS plugin. So it seems, that you are not really sure what kind of front-end you want. Right?
If you have at least some general idea, could you perhaps elaborate a bit, on what solution you have in mind? What basic features should the UI have?

I'm not very familiar with creating desktop apps. So I won't help with that.
I'm also not very familiar with python, but I can imagine that:

you could create a custom web service in python (by wrapping your code into a Django framework or something like that)
and implement some well-defined API, which then could be used by some front-end web app implemented by another person.

Regarding me helping you:
I'd like to keep my Pian.co simple, without adding too many new features and settings.
But I can imagine a simplistic integration to my Pian.co I might be interested in.
It could work like this:

there could be another room called AI, which would behave similarly to other rooms, but

the last few notes played by the user there would be recorded
there could be a magical button that would Let the AI continue on what you just started
clicking on this button would send the recorded notes as a MIDI to your service, it would do the generation and send back the whole piece, which would then be replayed locally.
(it could happen automatically without clicking a button, by just not playing more notes for a while)

However, if you'd like to have more features, for example, an option to upload MIDI files, a possibility to set various variables,  the ability to save the generated file, etc., then it would be better to have a stand-alone app with UI just for your needs.
Other thoughts:
I also have a concern about the performance, if it would be a remote service.
As I tried it in the Colab environment it seemed to take some time for the generating to finish. I'm not sure how well would it run on the server when used by several users at once.
A downloadable app with your python running locally on the user's device is probably(?) a more feasible solution.
Can't help you with that, however.
So yeah... I'm not sure if I'm interested until you provide me with more info.
Feel free to respond to me in an email, if you don't wish to discuss it further publicly.

@drahoslove Ohh...I am really good with python but I am a complete noob with web/app stuff so please forgive my ignorance and misunderstanding in advance :)
However, I would be willing to help however I can and do my part if you are willing to colab and if you think this is something that interests you.
Another interesting idea that was implemented in another project is a real-time accompaniment...user plays melody notes and AI plays chords...
Basically, there is a lot of cool things that can be done :)

@asigalov61
Well, that is great.
In that case, let's try the "magic button" idea.
My expectation is, that your python code would not be packaged in my app, but it would exist as a separate microservice, possibly hosted on its own, which would be called by me over http(s).
That way you would be able to utilize the same project in multiple ways. And not be dependent only on my app.
For example in the future, you could have your own landing page, (similar to https://openai.com/blog/musenet/), which could reuse the same python service of yours to present some examples.... or you could let someone create another front-end app, or implement some kind of hardware piano interface from Raspberry Pi/Arduino, or whatever - all of them could use the same service.
I would like you to try to create some 'proof of concept'.
Are you familiar with some basics of HTTP and how to create an HTTP handler in python?
Would you be able to create a simple HTTP service with this smaller model you are talking about, that could be called remotely?
It should have an endpoint that would accept the initial notes (and some additional parameters - eg. length of the result) and return the generated continuation.
Let's say the endpoint would be:
POST /midi/continuation

It could either accept and return the data as MIDI file (Standard Midi Format)
You could mimic the request you'd receive from me using the following curl command (It assumes you are running the service locally at port 8080 and you have file test_input.mid containing the initial notes in the current directory):
curl -X POST http://localhost:8080/midi/continuation
   -F<EMAIL_ADDRESS>   -F length=15000

Or we can use some custom JSON format (which would be probably a bit easier for me)
For example:
curl -X POST http://localhost:8080/midi/continuation
   -H 'Content-Type: application/json'
   -d '{"notes": [{"note": 60, "time": 0, "duration": 250}, {"note": 64, "time": 1000, "duration": 500}], "length": 15000}'

Or less verbose way:
curl -X POST http://localhost:8080/midi/continuation
-H 'Content-Type: application/json'
-d '{"notes": [[60, 0, 250],[64,1000,500]], "length": 15000}'

... that is for a discussion - I'm not sure what values from the midi file you actually use.

If you have no idea what I am talking about. I could probably help you implement that.
In that case, I'd need some time to familiarize myself with the python language and your code a bit - it's been a while since I've done something in python.
But it would be great if you could handle as much of the python part as possible by yourself, and ideally even host it somewhere by yourself (at least for now, to test it - we could later decide to move it).

@drahoslove Thank you for your response and thank you for being willing to colab :)
I absolutely agree with you (especially after talking to you and other people) that web API (similar to MuseNet is the way to go. It would be the best and most convenient for everyone and also very versatile in terms of integration.
Thank you for the basic guidance on the API... It is very helpful and I agree very much with most of the examples...I will need to think about which way is the best to go...
Now, I already started working on a prototype for the API... I will host it on paperspace.com as they offer GPU-powered instances. Any help from you would be really appreciated.
I hope you do not mind, I will email you soon with details and examples of my API prototype so that you can take a look at it and help me out if you can...
Otherwise, looking forward to doing this project with you and hopefully, we can achieve some results.
I will close the issue for now and I will email you directly shortly.
Alex

Awesome!
Looking forward to hearing from you.


Publish job condition evaluation is wrong

Description
The if condition to run the publish job still runs if you manually trigger a workflow on a branch other than main or master.
job_publish_module:
    name: 'Publish module'
    if: contains(fromJson('["refs/heads/main", "refs/heads/master"]'), github.ref) || ('${{ github.event.inputs.prerelease }}' == 'true')

Screenshots

Fixed?