Upgrade Next.js to 9.3

Custome routes da kaldirabilir miyiz? Artik gerek yok.

Hello @BatuhanW ,
May be required in some cases. I think there is no problem.


Website Opens at the Bottom of the Page Upon Load

When opening the website, the page automatically scrolls to the bottom instead of starting at the top. This behavior occurs consistently across all pages and affects the user experience. The expected behavior is for the page to open at the top by default. The issue can be observed in the attached video, which demonstrates the page automatically scrolling to the end upon load.
Steps to reproduce:

Open the website.
Observe that the page scrolls to the bottom instead of remaining at the top.

Expected behavior: The website should load at the top of the page by default, providing a better user experience.
https://github.com/user-attachments/assets/ee8130c0-093a-40f1-80d0-096d9a44b412
I would like to work on the issue. Can you assign it to me under gssoc-ext and hacktoberfest-accepted

When opening the website, the page automatically scrolls to the bottom instead of starting at the top. This behavior occurs consistently across all pages and affects the user experience. The expected behavior is for the page to open at the top by default. The issue can be observed in the attached video, which demonstrates the page automatically scrolling to the end upon load.
Steps to reproduce:

Open the website.
Observe that the page scrolls to the bottom instead of remaining at the top.

Expected behavior: The website should load at the top of the page by default, providing a better user experience.
Counter.App.and.2.more.pages.-.Personal.-.Microsoft.Edge.2024-10-06.18-11-24.mp4
I would like to work on the issue. Can you assign it to me under gssoc-ext and hacktoberfest-accepted

Sure.All the Best!!


Wrong error message if x:expect has assert and test

If you have
<x:expect assert="true()" label="Expect-1" test="true()" />

The latest master XSpec complains
Creating Test Stylesheet...
ERROR in scenario "Expect-1": can't have both @context and @test at the same time

In the message, context and test attributes are blamed. But actually x:expect has no context attribute.

Thanks for reporting this issue, it may be a mismatch between the test conditions and the error message in the XSpec code. I'll have a look and keep you posted. Please allow me 7-10 days to get back to you as it is Christmas time.

As confirmed by @AirQuick in https://github.com/xspec/xspec/issues/30#issuecomment-269759116, #38 made this issue obsolete so I close it.

As confirmed by @AirQuick in https://github.com/xspec/xspec/issues/30#issuecomment-269759116, #38 made this issue obsolete so I close it.


Getting 404 errors related to .properties files

I'm running the latest docker build (2.4.5) and getting 404 errors as well as console errors related to a few .properties files. This causes the UI to have nothing in it for ~20 seconds and then finally renders.
Looks like these files don't exist in source control either. What's the fix for this?
nav_en.properties
nav_en_US.properties
traces_en.properties
traces_en_US.properties

The i18n library is just looking for refined data right? (Ex american
dialect). 404 is not an error per se, just not finding something better

The UI has nothing in it for ~20 seconds and only renders after the uncaught error in jquery.il8n.properties displays.

maybe look at this related commit? 54f66a72389b854ae6ba734cf9ddd6b9cc1a8cc1 It is possible that what needs to change is upstream in https://github.com/jquery-i18n-properties but maybe it is configurable cc @igorwwwwwwwwwwwwwwwwwwww

i believe the slowness in rendering may be due to #1914. it may not be related to the i18n stuff at all.
also, the 404s on language files were already happening in previous versions of the zipkin-ui, this is inherent in how the i18n plugin operates. so as far as i know, this is pre-existing and "expected" behaviour.
the length error on the other hand doesn't look good. it looks like it might be due to a missing key in the language file (based on the code here https://github.com/jquery-i18n-properties/jquery-i18n-properties/blob/master/jquery.i18n.properties.js#L150). this is a bit hard to tell without a reproduce case and the ability to dig deeper. though if the error does not cause the UI to be unusable, I don't think it is absolutely critical.

leaving this open a bit longer as I don't know the strategies available to avoid 404's. Maybe we can help upstream.. possibly by keeping a config file of known properties files? (ex the server can compute this so there's no maintenance)

we won't address this i18n library in classic #2487 will likely use a different library in lens


Cannot read language file

Hi. I got this notice after upgrading to YOURLS 1.7.1 today (although it might've existed before, upgrading was the last thing I did with YOURLS in ages):
Notice: Cannot read file user/plugins/redirect-index/languages/redirindex-.mo. Make sure there is a language file installed. More info: http://yourls.org/translations in /Applications/MAMP/htdocs/yourls/includes/functions-l10n.php on line 458
I was under the impression that if no language is specified (my config.php contains define( 'YOURLS_LANG', '' );), then YOURLS shouldn't need to look for any language files. In fact, it makes absolutely no sense to look for a redirindex-.mo file since the is no sane situation in which this file would exist.
I know it's just a notice, but I thought it's best reporting this just in case, since I think YOURLS shouldn't need to be checking for language files at all.

Thanks for the heads up, I'll look into this


Not able to download dataset via Google Drive

The google drive link (https://drive.google.com/drive/folders/1w8imCXWYn2LxajmGeGH_g5DaL2rabHev) is not working. Showing 404 not found error.

The link has been fixed. The data is avaialble at https://drive.google.com/drive/folders/16kuhXdM-MOhYcFIyRj91WvnDnjnF-xHw?usp=sharing now.


support for clair 4.x.y

Does the adapter support newer releases of Clair? i.e. 4.x.y

IIRC Clair v4 has changed the API. Currently this adapter officially supports version v2. Some more tests have to be done to confirm that it works with the newest Clair scanner. (I did a very quick test with Clair v4 some time back but it failed.)
I think we'd appreciate any help on that. The first step could be just to deploy Clair v4 and configure this adapter to use it, and report any issues that may occur during such test. After that we could plan for changes in code.

Yes, in v4 both the Clair API and database relations have changed. Let me see if i can try out the adapter with changes.


Added foo channel

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I don't think this addition will make it. Foo doesn't seem to be a real channel 😉


ci: fix multi arch release process

What problem does this PR solve?:
Which issue(s) does this PR fix?:

https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

created https://github.com/mesosphere/konvoy-image-builder/pull/614 based on this PR. This PR has more refactoring to enable building the multi arch binaries and docker images.


Use a simple heuristic to determine if a git_tag is actually a git rev

If it's 40 characters long hexadecimal string it's very likely a rev

Could you give some information on what this PR is trying to solve/improve?

It solves the following issues that were reported during edm init when a dependencies.yaml contains a git rev in the git_tag field, it would occasionally output warnings like this:
[edm]:    Error while cloning git repository during local dependency checkout:
[edm]:       Cloning into 'workspace/libocpp'...
[edm]:       fatal: Remote branch 169573382e4d790103ce008027bb753d5ebd124a not found in upstream origin

I'll have another look about making it a bit prettier though, was just a relatively quick fix :)


got an error in objective c

[handler getTokenWithRequest:request successHandler:^(AcceptSDKTokenResponse * _Nonnull token) {
NSLog(@"success %@", token.getOpaqueData.getDataValue);
} failureHandler:^(AcceptSDKErrorResponse * _Nonnull error) {
<EMAIL_ADDRESS>);
}];
I got error here "EXC_BAD_ACCESS"

@RakeshVisa can you provide an example Objective-C implementation?
https://gist.github.com/davidolesch/266a4553897386a800e7e5e00113cf8b
My implementation crashes on line 25 with a EXC_BAD_ACCESS exception. I think it might be an issue with the bridging because I don't have any problems using the SDK in Swift. Unfortunately I need to use it in a Objective-C.

Hi @davidolesch  did you solve this problem?
I also got EXC_BAD_ACCESS exception with Objective-C implementation.

No. Instead I just implemented the validation and API requests the SDK does in Objective-C. The Swift code is open source so you can see how they do it.

@davidolesch
Thanks for your suggestion.

@davidolesch May I know which swift code did you reference?

@sprewell20051116 https://github.com/AuthorizeNet/accept-sdk-ios/tree/master/AcceptSDK

@davidolesch thank you !!!

Will include the Objective-C demo app. Closing the issue for now.


error about inference.py

Hello author, I encountered an error while running the inference script conference.py. May I ask for the reason? If you could answer my question, I would be happy. Best wishes!
The error : from models import GeneratorUNet ModuleNotFoundError: No module named 'models'

yep,I find the reason,is that
from models import GeneratorUNet should be from lib import GeneratorUNet
a little mistake,best wishes!


Create more generic  and  elements

This is a first step in clarifying the role of <annot>.  These elements will make it possible to encode relationship info outside the context of an annotation.

Closed by ca15fe7


dropRepeats of state on every level (isolation)

When not dropped in StateSource then every isolated child gets "update" as well regardless of his isolated state.

Nice catch! Thanks!


It is opaque to me which version of Docker is in a given Docker Bosh Release

Can this be included in the release notes and/or exposed in a file easier to find in the repo than https://github.com/cloudfoundry-incubator/docker-boshrelease/blob/f1871e87376c2ae174983b548beb5ac877d75433/packages/docker/spec#L8 ?

Yep will ensure it's in the releases when we bump to 19.x


Optimize textContent

Reference: http://esbench.com/bench/56a042be45df6895002e01e6

Eyo, turns out this was already optimized :)


Geo index is not used when GEO_DISTANCE is compared with a stored value

My Environment

ArangoDB Version:        3.7.3
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:    systemd
Configuration:               optimizer-rules = -splice-subqueries in arangod.conf
Infrastructure:               own
Operating System:        Ubuntu 18.04
Total RAM in your machine:        126Gb
Disks in use:        HDD
Used Package:              Debian or Ubuntu .deb

Component, Query & Data
Affected feature:
AQL query using web interface (index not used)
AQL query (if applicable):
Query 1
for m in z_monitoring
    for c in m.polygons
    	 for o in z_obs
    	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < c.radius
    	       collect with count into c return c

Query 2
for m in z_monitoring
    for c in m.polygons
    	 for o in z_obs
    	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < 100000
    	       collect with count into c return c

AQL explain and/or profile (if applicable):
Query 1
Query String (199 chars, cacheable: true):
 for m in z_monitoring
     for c in m.polygons
     	 for o in z_obs
     	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < c.radius
     	       collect with count into c return c

Execution plan:
 Id   NodeType                       Est.   Comment
  1   SingletonNode                     1   * ROOT
  2   EnumerateCollectionNode           1     - FOR m IN z_monitoring   /* full collection scan, projections: `polygons` */
  3   CalculationNode                   1       - LET #4 = m.`polygons`   /* attribute expression */   /* collections used: m : z_monitoring */
  4   EnumerateListNode               100       - FOR c IN #4   /* list iteration */
  5   EnumerateCollectionNode   297818200         - FOR o IN z_obs   /* full collection scan, projections: `geoloc` */
  6   CalculationNode           297818200           - LET #6 = (c.`radius` > GEO_DISTANCE([ c.`lon`, c.`lat` ], [ o.`geoloc`.`lon`, o.`geoloc`.`lat` ]))   /* simple expression */   /* collections used: o : z_obs */
  7   FilterNode                297818200           - FILTER #6
  8   CollectNode                       1           - COLLECT  WITH COUNT INTO c   /* count */
  9   ReturnNode                        1           - RETURN c

Indexes used:
 none

Functions used:
 Name           Deterministic   Cacheable   Uses V8
 GEO_DISTANCE   true            true        false

Optimization rules applied:
 Id   RuleName
  1   reduce-extraction-to-projection

Query 2
Query String (197 chars, cacheable: true):
 for m in z_monitoring
     for c in m.polygons
     	 for o in z_obs
     	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < 100000
     	       collect with count into c return c

Execution plan:
 Id   NodeType                       Est.   Comment
  1   SingletonNode                     1   * ROOT
  2   EnumerateCollectionNode           1     - FOR m IN z_monitoring   /* full collection scan, projections: `polygons` */
  3   CalculationNode                   1       - LET #4 = m.`polygons`   /* attribute expression */   /* collections used: m : z_monitoring */
  4   EnumerateListNode               100       - FOR c IN #4   /* list iteration */
 10   IndexNode                 297818200         - FOR o IN z_obs   /* geo index scan, scan only */
  8   CollectNode                       1           - COLLECT  WITH COUNT INTO c   /* count */
  9   ReturnNode                        1           - RETURN c

Indexes used:
 By   Name              Type   Collection   Unique   Sparse   Selectivity   Fields                           Ranges
 10   idx_11016982078   geo    z_obs        false    true             n/a   [ `geoloc.lat`, `geoloc.lon` ]   (GEO_DISTANCE([ c.`lon`, c.`lat` ], [ o.`geoloc`.`lon`, o.`geoloc`.`lat` ]) < 100000)

Optimization rules applied:
 Id   RuleName
  1   geo-index-optimizer
  2   remove-unnecessary-calculations-2
  3   reduce-extraction-to-projection

Dataset:
Example documents (45,000,000 documents, 18,000,000 with lat/lon):
{
	"geoloc": {
		"lat": 43.6517076,
		"lon": 3.8620017,
		"altitude": 92,
		"accuracy": null
	},
	...
},
{
	"geoloc": null,
	...
}
{
	"geoloc": {
		"lat": null,
		"lon": null,
		"altitude": null,
		"accuracy": null,
		"locality": "at home"
	},
	...
}

Steps to reproduce

Explain Query1 (using GEO_DISTANCE() < c.radius)
Explain Query2 (using GEO_DISTANCE() < 100000)

Problem: the geo index is not used in Query1. I tried to cast the radius with TO_NUMBER, the index is still not used.
Expected result: the geo index is used

Hello ArangoDB team,
Sorry to have closed and then reopened the issue.
During the tests, it worked again (because I set the comparison value as an integer), but at the end it doesn't work with a variable.
Best regards,

If it helps:
for m in z_monitoring
	for c in m.polygons
		let radius = ROUND(TO_NUMBER(c.radius))
		return radius

[
	70247,
	76355
]

In the next example, the index is used, but the request returns 0:
for m in z_monitoring
	for c in m.polygons
		let radius = ROUND(TO_NUMBER(c.radius))
		for o in z_obs
			filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < radius
			collect with count into c return c

If I use the greatest radius value 76355, it returns 9414:
for m in z_monitoring
	for c in m.polygons
		let radius = ROUND(TO_NUMBER(c.radius))
		for o in z_obs
			filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < 76355
			collect with count into c return c

If you use a stored value as radius, then a full collection scan will be required to retrieve that value before the distance can be calculated. I assume that the geo index will not be eligible if the radius is dynamic. FILTER GEO_DISTANCE(...) < NOOPT(76355) will probably not return the expected number anymore too. If no index can be used, I would still expect the query to arrive at the correct result, albeit slower. So this might actually be a bug.

Not sure to understand. Do you mean that it's not possible to use geo index with this query? :
for m in z_monitoring
    for c in m.polygons
    	 for o in z_obs
    	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < c.radius
    	       collect with count into c return c

The value of c.radius is not known at query compile time but only at run time, because it comes from storage (it is dynamic). The optimizer doesn't recognize that it could still use the geo index, as long as the document reference is from an outer loop. I consider this a feature request.
What's the result of this query?
for m in z_monitoring
	for c in m.polygons
		for o in z_obs
			filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < NOEVAL(76355)
			collect with count into c return c

Does it return the same value as without NOEVAL() or not? If it returns a different number, then I would consider that a potential bug.

for m in z_monitoring
	for c in m.polygons
		for o in z_obs
			filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < NOEVAL(76355)
			collect with count into c return c

Indexes use: none
Result:
Warnings:

[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'
[10], 'in function 'GEO_DISTANCE()': Invalid coordinate pair'

Result:

[
  2794402
]

If I add filter o.geoloc.lon and o.geoloc.lat:
Indexes used: none and 9414 as result

Thanks, with the additional filter it matches the number that you mentioned in https://github.com/arangodb/arangodb/issues/13185#issuecomment-741873567, which seems like a good sign. I guess the warnings are raised because GEO_DISTANCE() receives null for documents without geoloc.lon and geoloc.lat. It's a bit strange though that this doesn't appear to be the case for your original query.
@goedderz was so kind to check the optimizer code and found out that the geo index rule only supports expressions that are values or variable references. It does not support attribute accesses like c.radius so far. A workaround could be to assign the attribute to a variable:
for m in z_monitoring
    for c in m.polygons
        let radius = c.radius
        let tmp = NOOPT(radius) // prevent optimizer from substituting radius with r.radius if it's only used once
    	 for o in z_obs
    	    filter GEO_DISTANCE([c.lon, c.lat], [o.geoloc.lon, o.geoloc.lat]) < radius
    	       collect with count into c return c

However, it doesn't return anything in 3.7 when a geo index is present. It does return something if there is no index. In a 3.8.devel maintainers build, I found an assertion failure: max->type == aql::NODE_TYPE_VALUE. Looks like the geo index doesn't support/resolve variable references to values.

@AntoineAA We confirmed that the optimizer only supports numbers. It also accepts references (variables), but this isn't actually implemented. #13196 restricts it to numbers. In a future step, we would like to add support for references and attribute access and enable the geo index optimization for your example query, but this will take some time.

Ok, thank you!

Ok, thank you!


Error when borrowing more than thousand units

Running a local fork and getting the following error when borrowing anything above 4 or 5 units.
ERROR: Error: invalid BigNumber string (argument="value", value="1e+21", code=INVALID_ARGUMENT, version=bignumber/5.4.2)
reason: 'invalid BigNumber string',
code: 'INVALID_ARGUMENT',
argument: 'value',
value: '1e+21'
Tested the following:
examples-js > web3-js > borrow-erc20-with-eth-collateral.js
examples-js > ethers-js > borrow-erc20-with-eth-collateral.js

Hi there. Discord #development channel is the best place to ask for help with questions like this (https://compound.finance/discord). Perhaps try passing a string with the full fidelity of the integer? like this: "1000000000000000000000"

Thank you Adam, will join the discord and ask there again. FYI tried I tried your suggestion, unfortunately it didn't work for me.


DF: add min_samples_split, min_weight_fraction_leaf, min_impurity_decrease, max_leaf_nodes parameters

Decision forest: several parameters were added:

minObservationsInSplitNode ("min_samples_split" is similar parameter from Sklearn);
minWeightFractionInLeafNode ("min_weight_fraction_leaf" is similar parameter from Sklearn);
minImpurityDecreaseInSplitNode ("min_impurity_decrease" is similar parameter from Sklearn);
maxLeafNodes ("max_leaf_nodes" is similar parameter from Sklearn)

/intelci: run

Some tests were created in daal4py side. Scikit-learn like interface is used for it, it does not integrate in daal4py test system. PR: https://github.com/IntelPython/daal4py/pull/204/files

/intelci: restart
set infra_branch=dev/agorshk-update_df_tests_master

/intelci: restart
set infra_branch=dev/agorshk-update_df_tests_master

/intelci: restart
set infra_branch=dev/agorshk-update_df_tests_master compatibility_branch=dev/agorshk-update_df_tests_compatible

/intelci: restart
set infra_branch=dev/agorshk-update_df_tests_master compatibility_branch=dev/agorshk-update_df_tests_compatible

/intelci: restart
set infra_branch=dev/agorshk-update_df_tests_master
set compatibility_branch=dev/agorshk-update_df_tests_compatible

http://intel-ci.intel.com/eaa0c4db-9858-f171-a13b-8cdcd4b723a1

http://intel-ci.intel.com/eaa18485-840c-f198-a734-8cdcd4b723a1


Enhance e2e suite

Summary
Currently our suite of e2e tests is extremely minimalistic. Meanwhile we had a fair dose of arguably app breaking bugs. We want to catch the most critical errors with our e2e suite.
Tasks
Create more tests.
In the spike https://github.com/stoplightio/elements/issues/1141 we created following test ideas:

each page type - article, service, operation, model, etc. - should have a test if this page type is correctly displayed.
send a request with TryIt
check generated RequestSample content
validate that JSV is working
basic test if ref resolving works in Docs, examples etc.
test if mocking in stoplight project works

You can of course add more tests, if you come up with something.
Remember that e2e tests should be highly general. Preferably each aspect of application (for example TryIt) gets no more than 1, max 2 tests.

There also appeared issues with props not being passed correctly to web components.
Therefore perhaps it would be valuable to make e2e tests for props like hideTryIt, hideSchemas`?
Up to debate.


GEODE-4791: Upgrading gradle from 3.5.1 to 4.5.1

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x]  Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@jdeppe-pivotal I'm running the failing test category locally to confirm if this is a platform issue rather than a real error
@scmbuildguy I've adjusted for a 2-space indent. Should be fixed now.

@jdeppe-pivotal seems the build was a temporal anomaly ... latest precheckin is all green


docs: Fix untitled protos in API docs.

Description: Fix untitled protos in API docs. Standardize on title casing.
Fixes: https://github.com/envoyproxy/envoy/issues/8525
Risk Level: Low
Testing: bazel --nohome_rc test --config=libc++ //test/...
Docs Changes: fix up some links to deprecated.rst to refer to internal links vs. Github
Release Notes: none required.
Signed-off-by: Michael P<EMAIL_ADDRESS>

@moderation thank you so much for continuing my change! I can help you on Monday if there are formatting, etc. issues.


Fix video wrapper

The goal is to correcly render the videos produced by the RenderImageInfoWrapper. Currently only sequences of black images are produced

rebased all commits to a new branch called "integrate-imitation"


question: mount/umount concurrency

podman mount always mounts to the same place.  I'm concerned if I'm running two scripts in parallel this can be error prone.  The mount, cp, umount flow in parallel can result in a umount before you'd like.  For safety it would be nice if you could specify the target dir which I'd expect would mount to the common location then bind mount to the target.

I don't know how the container's read/write layer would react to being mounted in multiple places, but if that can be addressed in containers/storage, I think this would definitely be a neat addition (unmount has always worried me a little with its potential interactions with running containers. We have checks in place to make sure you don't unmount a running container, but it'd be a lot cleaner if it was a completely separate mount).

Sadly this is not something you can do with overlay, I believe you could do this with devicemapper.  We could add a bind mount from the actual mount point to the specified location.
@nalind WDYT?

I was thinking about this more, and I wonder if having some sort of session scheme would also work. podman mount would generate a session ID, and podman unmount would optionally accept an ID to unmount. If more than one mount session is active, podman unmount won't actually unmount, but will instead remove the mount session in question from the active sessions list. This would ensure unmount doesn't squash other active copy operations.
This would need a bit of work, especially if we want to do it in a backwards-compatible fashion, but it would solve the issue without further work on the storage side.

Sure we could do that, although we would probably need a --force  umount.  The datastore counting mounts should be done in /run. so that it will not exists on reboot.  We would also need to notice if someone umounts mount point outside of the podman command.

This should be fixed now via #1104 - we use a mount counter to ensure that we don't unmount until every active mount is done.


Linux support

I want my flutter app (that uses supabase) to have linux support.
When can we expect linux support or will it never come?
Additional context
I searched around and couldn't find anything regarding the timeline of when Linux support will happen and the level of effort it takes to get to it. I also noticed in the chart on pub dev that Linux doesn't have null safety for the Provider Auth.

The issue is missing deep link support for Linux. There is an open issue in the package: https://github.com/llfbandit/app_links/issues/20

@matthewwong525
You can use most of the features on Linux today actually. All that is missing is the deep link feature to bring back the user to the app once someone clicks on the confirmation email as @Vinzent03 has pointed out. Everything else from database, realtime, storage and auth persistence will work just fine on Linux! Give it a try and let us know how it goes!

@matthewwong525 Sorry for the confusion, but you can use most of the features on Linux today actually. All that is missing is the deep link feature to bring back the user to the app once someone clicks on the confirmation email as @Vinzent03 has pointed out. Everything else from database, realtime, storage and auth persistence will work just fine on Linux! Give it a try and let us know how it goes!

I've just made a comment on that issue here:
https://github.com/llfbandit/app_links/issues/20#issuecomment-1368711249
I've recently published Desktop Entry which includes an example Flutter project that might be helpful. As I mention in that comment, the configuration will be different depending on how the application developer is distributing their application.

@dshukertjr app_links: ^3.5.0 published 22 days ago included a new feature: Linux support, which was standing in the way of supabase_flutter supporting Linux platform.
Last month I've migrated from Firebase, due to the limited platform support, and Supabase is awesome! 🚀🚀🚀 Adding Linux support is just an icing on the cake 🍥
Can we get an updated version of supabase_flutter next week?

@predragcvetkovski Sure, we can include it in the next update on Monday.
BTW, if app_link already supports Linux, you should already be able to use supabase_flutter in Linux as well! Make sure your app is using app_link v3.5.0, and follow the deep link set up instruction on app_link for Linux, and everything should be good!

@dshukertjr thanks, I look forward to trying it out on Monday! 🚀
The app builds and runs on Linux, however when the user taps on the magiclink it opens Chrome, instead of routing back to the app to complete the auth. I will check the deep link set up instruction on app_link for Linux to make sure I haven't missed anything. 👀

@predragcvetkovski 👍
Smash double check that you have app_link v3.5.0 it later in your pubspec.lock file!

Hello everyone,
I wanted to ask a question as there is indeed Linux support but it is not stated here: https://github.com/supabase/supabase-flutter/blob/9b91ce8491a6aec35d3d59767cdff45827212fa3/packages/supabase_flutter/pubspec.yaml#L33-L38
Thanks


More docs for the URL part of path_or_url

[ ] Have an example
[ ] Clearly describe what it means & does

It seems like this is not needed, no one is complaning, let's close then.


chore: jsonfmt profile

Ran jsonfmt -w "profile/*.json"

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?


No HELP in package

Hi, please add Help file with options. I have 19 gpus and I can't figure it out how to mine on all of them.
I tried with -d0 / -d01234 / -d0,1,2,3,4 and so on...many combinations, but the miner starts to mine always on gpu #0
I tried the .exe with -h -help and /h for any help.

Thanks a lot!

same problem

I noticed that d1 starts on the next device.
start PascalCoinCUDA_ProxyMiner_sm30.exe d0
start PascalCoinCUDA_ProxyMiner_sm35.exe d1
but my system crashes after some time. not sure why

sm30, sm35 and so on is for the architecture of the gpu. Mines are 1070 and 1080 and they are sm61.
So, I run xxx_sm61.exe


External library not excluded from build despite being defined in browser field

Command
build, serve
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
16
Description
External library that is marked with false in package.json (browser field) is still added to final bundle. It seems that issue is only present when using esbuild (with webpack it works as expected - library is not included when building). This behavior is pretty easy to reproduce, just add browser field to package.json with chosen library and check that is still being added to final bundle.

Based on some simple debbuging it seems to me that the problem is either with esbuild itself or angular-complier plugin. Despite library is excluded, it still is proceseed by angular-compiler plugin and because it returns some contents (https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/build_angular/src/tools/esbuild/angular/compiler-plugin.ts#L391 ) it ends up being added to bundle. I'm not sure if it is correct that esbuild invokes plugins for disabled libraries or maybe angular-plugin should filter disabled entries.
Similar simple setup (esbuild + excluded library in browser field) but without angular works as expected.

Hi @piozygmunt, thanks for opening this issue. It appears to be an esbuild issue https://github.com/evanw/esbuild/issues/3629


Provide documentation on how to setup iOS Privacy Manifest for Flutter Modules

As per the new guidelines for iOS Privacy Manifest need to be added in the iOS apps being submitted from May 1, 2024. Flutter community is active working on the changes required for apps and packages.
However, there does not seem to be much resources about adding the Privacy Manifests for Flutter Modules and how to go about these for Module specific code.
Needed help with defining manifests for the Flutter Modules

Out of curiosity, what is your module doing that would a privacy manifest?  Trying to figure out if it's because you're using ffi and calling one of the "required reason API"s, or if it's about privacy data use, for example your module collects email addresses (for this case, our understanding from Apple is that only SDKs in this list are required to declare data use).

Hello @jmagman , in our module we are not using ffi and any required reason APIs. As you correctly mentioned it is about privacy data use, and that too only for the "Linked to User" case. We do not use any such data for tracking purposes.
To be specific, out of the list specified on the Describing data use in privacy manifests page, we only consume the following data from the user only for the "Linked to User" case -
Contact info
Name - NSPrivacyCollectedDataTypeName
Email address - NSPrivacyCollectedDataTypeEmailAddress
Phone number - NSPrivacyCollectedDataTypePhoneNumber
Physical address - NSPrivacyCollectedDataTypePhysicalAddress
Financial info
Payment info - NSPrivacyCollectedDataTypePaymentInfo
Other financial info - NSPrivacyCollectedDataTypeOtherFinancialInfo
User content
Photos or videos - NSPrivacyCollectedDataTypePhotosorVideos
Identifiers
Device ID - NSPrivacyCollectedDataTypeDeviceID
Report the reasons your app or third-party SDK collects data
App functionality - NSPrivacyCollectedDataTypePurposeAppFunctionality
In this case, do we need to add the Privacy Manifest? In case we do, how can this be added?
Sincerely appreciate your time on this.


Clearer Custom Task Reference Interface

Feature Request
Request to have an additive dedicated field for referencing Custom Task, instead of using generally named fields apiVersion + kind + name under taskRef for it.
- name: sample-custom-task-new
  taskRef:
    customTask: "wait.testing.tekton.dev/v1beta1/Wait"
    name: "wait-task" # optional, depends on how custom tasks are implemented.

In this way, we create a new field customTask under taskRef for referencing Custom Task (just like we have a dedicated field resolver for Remote Resources).
- name: custom-task
 taskRef:
   customTask: "wait.testing.tekton.dev/v1beta1/Wait"
   name: "wait-task"

- taskRef:
   resolver: git
   params:
   - name: url
     value: https://github.com/tektoncd/catalog.git
   - name: revision
     value: main
   - name: pathInRepo
     value: task/git-clone/0.6/git-clone.yaml

- name: regular-task
 taskRef:
   name: "sample-task"

Use Case
Say I'm a new comer to Tekton, the first thing I knew about taskRef is it refers to a Task and will be scheduled as a TaskRun.
When I want to use the powerful Custom Task, I realized I need to use the following genaric syntax under taskRef to specify a CustomTask reference.
What's even more weird is, I'm not allowed to use taskRef.apiVersion when specifying a regular Task, which seems like an inconsistent API design.
# the current way of referencing a custom task
- name: custom-task
  taskRef:
    apiVersion: "wait.testing.tekton.dev/v1beta1"
    kind: "Wait"
    name: "wait-task"
# illegal usage
- name: regular-task
  taskRef:
    apiVersion: "tekton.dev/v1beta1"  # illegal, PipelineRun controller ceates a CustomRun/Run for this taskRef instead of a TaskRun.
    kind: Task # optional
    name: "regular-task"

It would be clearer if we have a dedicated field to refer to CustomTasks under taskRef.

@XinruZhang I am not sure I completely agree with this statement. The apiVersion + kind + name is a very well known construct in Kubernetes types

Thank you for the comment @vdemeester. Sorry for the confusion that I might have introduced here 🙃
My main point is it is confusing for a new Tekton user that using taskRef.apiVersion + taskRef.kind + taskRef.name to refer to a Custom Task. I updated the issue description, added the Use Case section to describe where the confusion is for a Tekton User, and why it is inconsistent, hope this helps with clarifying my idea.
Since I'm proposing a new field here, we can consider makeing this API field more generic (remove the implied Kubernetes-ism) as suggested in this conformance design principle to improve our API abstraction.

@tektoncd/core-collaborators  PTAL :)

Even though apiVersion and kind are technically kubernetes-isms, I think the spirit of the design principle on conformance is to not introduce fields that are only be able to run on k8s as opposed to other platforms. I'm not convinced that apiVersion and kind detract from conformance goals because it's extremely likely that custom task users would need to specify this info regardless of platform (I'm assuming that's why it's encoded in the "customTask" syntax in the example above).
Also, we can make this an additive change, but it introduces redundancy into the API. I'd imagine we'd consider deprecating the existing syntax at some point. I'm not sure there's a strong enough reason to do this.
Maybe to lessen confusion, we could allow the "illegal usage" example above? i.e.
apiVersion: tekton.dev/v1beta1
kind: TaskRun
spec:
- name: regular-task
  taskRef:
    apiVersion: "tekton.dev/v1"  # Create a v1 TaskRun instead of a v1beta1 TaskRun (the current behavior)
    kind: Task # optional
    name: "regular-task"

Thank you for the comment @lbernick!

It's extremely likely that custom task users would need to specify this info regardless of platform

An interesting idea emerged when I discussed this with @vdemeester offline, APIVersion + Kind is not necessarily required when referring to a Custom Task, the two fields are often used for two purposes:
1. Filtering Events for CustomRun/Run:
https://github.com/tektoncd/experimental/blob/f60e1cd8ce22ed745e335f6f547bb9a44580dc7c/cel/pkg/reconciler/cel/controller.go#L53
https://github.com/tektoncd/experimental/blob/f60e1cd8ce22ed745e335f6f547bb9a44580dc7c/task-loops/pkg/reconciler/tasklooprun/tasklooprun.go#L102-L107
https://github.com/tektoncd/experimental/blob/f60e1cd8ce22ed745e335f6f547bb9a44580dc7c/pipeline-loops/pkg/reconciler/pipelinelooprun/pipelinelooprun.go#L86-L91
https://github.com/tektoncd/experimental/blob/f60e1cd8ce22ed745e335f6f547bb9a44580dc7c/pipelines-in-pipelines/pkg/reconciler/pip/piprun.go#L67-L71
For the filtering purpose, we actually don't have to use APIVersion + Kind, for example using "pipelineLoop" to filter all the Kubernetes Event on v1alpha.Run has the same effect.
2. Get the target CRD resource back and make modifications:
https://github.com/tektoncd/experimental/blob/f60e1cd8ce22ed745e335f6f547bb9a44580dc7c/pipeline-in-pod/pkg/reconciler/pipelineinpod/pipelineinpod.go#L136-L142
For this purpose, the info "APIVersion" and "Kind" is important for those custom task controllers who take care of those CRDs defined within CustomRun/Run. But they don't have to be specified by end users by using the pipeline.spec.tasks[].taskRef or run.spec.refor customRun.spec.customRef. Instead, each individual custom task controller can decide what CRD they want to manage within the controller, as long as end users specify which Custom Task Controller they want to use.
For example, a custom task user can specify:
taskRef:
  customTask: "PipelineLoop"
  name: "my-pipeline-loop"

And in the PipelineLoop controller, it can only reconcile resources where their

apiVersion=="pipelineloop.dev/v1beta1"
kind=="PipelineLoop"
name=="taskRef.name"

I think the spirit of the design principle on conformance is to not introduce fields that are only able to run on k8s as opposed to other platforms

I partially agree with this statement, for the conformance policy, the functional capability of being platform-ignorant is indeed important, but the naming itself is also important.

Moving the discussion with @pritidesai here in the issue: the main idea that @pritidesai  brings is:

The pipeline author decided to choose the Tekton Task specifications as Custom Task. I do not think we should restrict or try to interpret the values specified in those fields. It's very well documented that those specifications (taskRef.apiVersion and taskRef.kind) creates customRun/Run.
A pipeline author could also decide to specify apiVersion: "tekton.dev/v1beta1" and kind: Pipeline. It's user's decision to specify any kind of resource as a customRun/Run.

Chatted offline with @XinruZhang and we agreed that it's not necessarily the fact that "apiVersion" and "kind" are "kubernetes-isms" that makes them confusing-- what's actually confusing is that custom run controllers reconcile custom run objects, and whether they reconcile objects with the specified api version and kind is entirely up to the controller. We're overloading "kind" to mean both the custom run controller that should reconcile the object and the type of object that the custom run controller can optionally reconcile. Similarly, we're overloading "apiVersion" to mean both the version of the custom spec (where api group is not clearly meaningful) and the api group + version of the object that the controller can optionally reconcile.
It's also confusing that name is required for Tasks but optional for custom Tasks. If the custom task controller supports reconciling objects of the same name and api version, it's supposed to look up the object with that name and use its spec, and if the user doesn't specify a name, the custom task controller may support reconciling w/ an empty spec.
Imagine a custom run controller must continue to reconcile CustomRuns, but can do so however it wants to (i.e. it's not necessarily required to reconcile objects of the same api version and kind as it filters for). The following syntax would be clearer IMO. (I'm not proposing this syntax, I'm just trying to brainstorm what it would look like if we didn't overload apiversion/kind in this way.)
taskRef:
  customRunController: "PipelineLoopFancyController"
  customSpecAPIVersion: "v1"
  customSpec:  # Anything in here is entirely up to the controller.
     pipelineLoopNameToFetchFromCluster: "my-pipeline-loop-crd"

This signifies that the custom run would be reconciled by the "PipelineLoopFancyController", using its v1 version of the custom spec. This specific custom run controller can either accept a custom spec inline, or it can look up whatever type of objects it reconciles. In this example, it would look up whatever type of object it reconciles, named "my-pipeline-loop-crd", and use that object's spec.
I'm not sure what syntax I'd want for a reference to a custom task in an ideal world, but wanted to hear others' thoughts on this (maybe nobody else finds this confusing?)

I haven't gotten chance to review the entire thread here, pinging @tomcli so that Tommy can chime in, thanks!

I think @XinruZhang's proposal on the customTask can work for us on the pipelineloop because the custom task just need to be aware where the custom apiVersion and kind are defined to filter all the customRuns/Runs events and to get the pipelineloop template when it's used as a taskRef. In this case we can get the ApiVersion and Kind from the customTask string by splitting the last slash and have some regular expression validation to make sure both ApiVersion and Kind are defined in the  customTask field.


Fix character encoding issue of template rendering

@mmoayyed  Fix encoding issue which mentioned in #1731.

Before pressing merge, could I ask you to:

Reverse the change
Find your application.properties file and set spring.thymeleaf.encoding=UTF-8.
See what happens

@mmoayyed

I just tried exactly same as what you said.
But still NOT work.
Please reopen this issue. That closed is a mistaken

OK, thanks. What you want to do then is:

Add a field to the class of type ThymeleafProperties and autowire it.
Use that field to do: setCharacterEncoding(thymeleafProperties.getCharacterEncoding())

That should work, rather than hardcoding the encoding.


Only way to drop you a message, just a thank you note

I just want to say thank you so much for making this repo public. It feels like years have passed since I started looking to the Dirichlet Process and how to freaken do it. I just could not grasp the literature on this topic, yet you made the concept so simple with your examples and code snippets 🥇

Thanks @bobfourie!


Documentation Update - Generate macOSInstaller

Anytime someone clones it they'll have to adjust the IF statement in the generate-installer.yml file.
Line 37 does a check if the repo is == to your repo name not the destination. A quick fix is to just modify it with the cloned name.

This job was skipped

@theonlytruebigmac I added that if statement because there is a limit of running github actions on repos. And if someone forks it and runs it then it counts the run in my account so that it why. you can do the "Use template" option instead of forking.


Feature Request - Multiple .CSV per chart/report

Would be great if we could have multiple .CSV per chart
IE, Income and expenses, could be separate .CSV
filename: ./Items/Income.csv, ./Items/Expenses.csv
model: all
type: chart

Thanks !
Yes ! It will help a lot when having a lot of data to ingest and manage,
I will regroup a couple of Feature requests and try to release soon

Hello
I released v0.5.3 and 0.5.4 that includes this feature, and started to work on v0.6.0 and tested the feature successfully.
Note, Each file must have the header (I skip the first line to join all files together)
You can update the plugin in Obsidian,
I will close this ticket, do not hesitate to reopen if you have comments


Brainstorm ways to improve our testing process

We want to improve our test process to be more efficient, comprehensive, and representative of our customers' use cases. This probably involves changes to our testing process, the use of automation, and/or new frameworks and tools.
Please propose a system we could implement to achieve these goals.

We should consider CI pipelines (e.g. GitHub Actions) as the primary interface for Uffizzi. The Uffizzi Dashboard should be secondary. Instead of just testing our CLI, our tests should start from PRs that trigger a pipeline. For an example GitHub Actions workflow that uses our reusable workflow, see this example:
https://github.com/UffizziCloud/example-voting-app/blob/main/.github/workflows/uffizzi-previews.yml

Idea 1
We could configure our test process such that when a developer opens a PR for a Uffizzi feature branch, it triggers a pipeline that deploys a Uffizzi-on-Uffizzi preview. After the preview URL is ready, another job runs that deploys a test app (e.g. example-vote-app) into the new preview environment. After the test app is deployed we can run a series of additional tests on both the test app and on Uffizzi-on-Uffizzi itself.

Test cases for dev-team for smoke testing after releasing a new feature.
For platform:

Check if the pipeline was passed for your feature branch.
Make smoke testing of your feature (your feature appeared in the environment and the main functionality of your feature works as expected e.g. login passed, button appeared, deployment was created etc.)
Connect your GitHub account
If your feature impacts the deployment process, follow the next steps:
Add compose file https://github.com/NealArw/example-voting-app-monorepo/blob/master/docker-compose.uffizzi.yml (firstly you need to make fork of necessary repos and create necessary secrets inside the uffizzi)
Create deployment from this compose file (We also need to prepare some compose files for other cases e.g. volumes, anchor, etc)
Check if the preview was successfully deployed and you can open the preview using URL
Crate pull request in repo https://github.com/NealArw/example-voting-app-monorepo from  branch double-dogs to master
Check if the new preview was automatically created, successfully deployed and you can open the preview using URL
Delete all created deployments

For CLI with open source app:

Check if the pipeline was passed for your feature branch.
Pull the latest version qa branches of cli and uffizzi_app
Run uffizzi_app and cli
Connect from cli to uffizzi_app
Make smoke testing of your feature (your feature appeared in the environment and the main functionality of your feature works as expected e.g. login passed, button appeared, deployment was created etc.)
Connect Docker Hub account
If your feature impacts the deployment process, follow the next steps:
Save locally compose file https://github.com/NealArw/hello-world-1/blob/compose-test/uffizzi-vote-app-docker.yml
Create necessary secrets
Create deployment from this compose file (We also need to prepare some compose files for other cases e.g. volumes, anchor, etc)
Check if the preview was successfully deployed and you can open the preview using URL
Delete all created deployments


MSID: 98634 Version: 1 DOI: 10.1101/2<IP_ADDRESS>8285

MSID: 98634
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>8285
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98634
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>8285

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98634v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>8285
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98634/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c22) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c67) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c68) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c71) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c72) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c73) has a publication-type='other'. Is that correct?
warn: [title-lower-case] Content of  element is entirely in lower-case case: Is that correct? 'gal expression correlates with whole-brain activity'
warn: [title-lower-case] Content of  element is entirely in lower-case case: Is that correct? 'gal controls whole-brain activity'
warn: [title-lower-case] Content of  element is entirely in lower-case case: Is that correct? 'gal exerts only a modest effect on seizure activity in eaat2a mutants'


flatpak: 1.12.4 → 1.12.5

Motivation for this change
Picked from https://github.com/NixOS/nixpkgs/pull/160343
Untested.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Flatpak tests failing:
-SUMMARY: total=49; passed=47; skipped=0; failed=2; user=1136.0s; system=641.7s; maxrss=439060
+SUMMARY: total=50; passed=47; skipped=0; failed=3; user=1138.7s; system=584.6s; maxrss=439120
+FAIL: flatpak/test-history.sh.test (Child process exited with code 1)
 FAIL: flatpak/test-prune.sh.test (Child process exited with code 1)
 FAIL: flatpak/test-seccomp.sh.test (Child process exited with code 1)


Exits as soon as I start typing in the first test

@@@@@@@@@@@@@@@@@@@ controlTextDidChange
operation count: 0
query string:
 ;; simple query

(define (parse-ans-simple) (run 1 (q)
 (let ((g1 (gensym "g1")) (g2 (gensym "g2")) (g3 (gensym "g3")) (g4 (gensym "g4")) (g5 (gensym "g5")) (g6 (gensym "g6")) (g7 (gensym "g7")) (g8 (gensym "g8")) (g9 (gensym "g9")) (g10 (gensym "g10")) (g11 (gensym "g11")) (g12 (gensym "g12")) (g13 (gensym "g13")) (g14 (gensym "g14")) (g15 (gensym "g15")) (g16 (gensym "g16")) (g17 (gensym "g17")) (g18 (gensym "g18")) (g19 (gensym "g19")) (g20 (gensym "g20")))
(fresh (A B C D E F G H I J K L M N O P Q R S T U V W X Y Z _) (parseo `(begin (define ,A
  (lambda ,B
    ,C)) ,_))))))

(define (query-val-simple)
  (if (null? (parse-ans-simple))
      'parse-error
      (let ((results-fast (begin (set! allow-incomplete-search?               #t) (results))))
  (if (null? results-fast)
    (begin (set! allow-incomplete-search? #f) (results))
    results-fast)))

2018-04-23 00:43:34.143476+0430 Barliman[40441:3466615] [General] An uncaught exception was raised
2018-04-23 00:43:34.143478+0430 Barliman[40441:3466588] [General] An uncaught exception was raised
2018-04-23 00:43:34.143535+0430 Barliman[40441:3466615] [General] launch path not accessible
2018-04-23 00:43:34.143542+0430 Barliman[40441:3466588] [General] launch path not accessible
2018-04-23 00:43:34.143621+0430 Barliman[40441:3466615] [General] (
	0   CoreFoundation                      0x00007fff48488fcb __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x00007fff6f13ec76 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4851a9ed +[NSException raise:format:] + 205
	3   Foundation                          0x00007fff4a6bee82 -[NSConcreteTask launchWithDictionary:error:] + 1304
	4   Barliman                            0x0000000100038160 _T08Barliman18RunSchemeOperationC03runC4CodeyyF + 1584
	5   Barliman                            0x0000000100037ae1 _T08Barliman18RunSchemeOperationC4mainyyF + 113
	6   Barliman                            0x0000000100037b14 _T08Barliman18RunSchemeOperationC4mainyyFTo + 36
	7   Foundation                          0x00007fff4a4ee5de -[__NSOperationInternal _start:] + 778
	8   Foundation                          0x00007fff4a4ea607 __NSOQSchedule_f + 369
	9   libdispatch.dylib                   0x0000000100ec3d1f _dispatch_client_callout + 8
	10  libdispatch.dylib                   0x0000000100ed83c3 _dispatch_continuation_pop + 940
	11  libdispatch.dylib                   0x0000000100ecf3ae _dispatch_async_redirect_invoke + 738
	12  libdispatch.dylib                   0x0000000100ec5b76 _dispatch_root_queue_drain + 723
	13  libdispatch.dylib                   0x0000000100ec584f _dispatch_worker_thread3 + 116
	14  libsystem_pthread.dylib             0x0000000100f401c2 _pthread_wqthread + 1387
	15  libsystem_pthread.dylib             0x0000000100f3fc45 start_wqthread + 13
)
2018-04-23 00:43:34.143623+0430 Barliman[40441:3466588] [General] (
	0   CoreFoundation                      0x00007fff48488fcb __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x00007fff6f13ec76 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4851a9ed +[NSException raise:format:] + 205
	3   Foundation                          0x00007fff4a6bee82 -[NSConcreteTask launchWithDictionary:error:] + 1304
	4   Barliman                            0x0000000100038160 _T08Barliman18RunSchemeOperationC03runC4CodeyyF + 1584
	5   Barliman                            0x0000000100037ae1 _T08Barliman18RunSchemeOperationC4mainyyF + 113
	6   Barliman                            0x0000000100037b14 _T08Barliman18RunSchemeOperationC4mainyyFTo + 36
	7   Foundation                          0x00007fff4a4ee5de -[__NSOperationInternal _start:] + 778
	8   Foundation                          0x00007fff4a4ea607 __NSOQSchedule_f + 369
	9   libdispatch.dylib                   0x0000000100ec3d1f _dispatch_client_callout + 8
	10  libdispatch.dylib                   0x0000000100ed83c3 _dispatch_continuation_pop + 940
	11  libdispatch.dylib                   0x0000000100ecf3ae _dispatch_async_redirect_invoke + 738
	12  libdispatch.dylib                   0x0000000100ec5b76 _dispatch_root_queue_drain + 723
	13  libdispatch.dylib                   0x0000000100ec584f _dispatch_worker_thread3 + 116
	14  libsystem_pthread.dylib             0x0000000100f401c2 _pthread_wqthread + 1387
	15  libsystem_pthread.dylib             0x0000000100f3fc45 start_wqthread + 13
)
2018-04-23 00:43:34.143980+0430 Barliman[40441:3466615] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff48488fcb __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x00007fff6f13ec76 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4851a9ed +[NSException raise:format:] + 205
	3   Foundation                          0x00007fff4a6bee82 -[NSConcreteTask launchWithDictionary:error:] + 1304
	4   Barliman                            0x0000000100038160 _T08Barliman18RunSchemeOperationC03runC4CodeyyF + 1584
	5   Barliman                            0x0000000100037ae1 _T08Barliman18RunSchemeOperationC4mainyyF + 113
	6   Barliman                            0x0000000100037b14 _T08Barliman18RunSchemeOperationC4mainyyFTo + 36
	7   Foundation                          0x00007fff4a4ee5de -[__NSOperationInternal _start:] + 778
	8   Foundation                          0x00007fff4a4ea607 __NSOQSchedule_f + 369
	9   libdispatch.dylib                   0x0000000100ec3d1f _dispatch_client_callout + 8
	10  libdispatch.dylib                   0x0000000100ed83c3 _dispatch_continuation_pop + 940
	11  libdispatch.dylib                   0x0000000100ecf3ae _dispatch_async_redirect_invoke + 738
	12  libdispatch.dylib                   0x0000000100ec5b76 _dispatch_root_queue_drain + 723
	13  libdispatch.dylib                   0x0000000100ec584f _dispatch_worker_thread3 + 116
	14  libsystem_pthread.dylib             0x0000000100f401c2 _pthread_wqthread + 1387
	15  libsystem_pthread.dylib             0x0000000100f3fc45 start_wqthread + 13
)
2018-04-23 00:43:34.144369+0430 Barliman[40441:3466588] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff48488fcb __exceptionPreprocess + 171
	1   libobjc.A.dylib               libc++abi.dylib: terminating with uncaught exception of type NSException
      0x00007fff6f13ec76 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4851a9ed +[NSException raise:format:] + 205
	3   Foundation                          0x00007fff4a6bee82 -[NSConcreteTask launchWithDictionary:error:] + 1304
	4   Barliman                            0x0000000100038160 _T08Barliman18RunSchemeOperationC03runC4CodeyyF + 1584
	5   Barliman                            0x0000000100037ae1 _T08Barliman18RunSchemeOperationC4mainyyF + 113
	6   Barliman                            0x0000000100037b14 _T08Barliman18RunSchemeOperationC4mainyyFTo + 36
	7   Foundation                          0x00007fff4a4ee5de -[__NSOperationInternal _start:] + 778
	8   Foundation                          0x00007fff4a4ea607 __NSOQSchedule_f + 369
	9   libdispatch.dylib                   0x0000000100ec3d1f _dispatch_client_callout + 8
	10  libdispatch.dylib                   0x0000000100ed83c3 _dispatch_continuation_pop + 940
	11  libdispatch.dylib                   0x0000000100ecf3ae _dispatch_async_redirect_invoke + 738
	12  libdispatch.dylib                   0x0000000100ec5b76 _dispatch_root_queue_drain + 723
	13  libdispatch.dylib                   0x0000000100ec584f _dispatch_worker_thread3 + 116
	14  libsystem_pthread.dylib             0x0000000100f401c2 _pthread_wqthread + 1387
	15  libsystem_pthread.dylib             0x0000000100f3fc45 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

@gregr Thanks, that solved it.


Error on npm run dev or build

When I try npm run dev I get this error:
Error: Cannot find module '/Users/ae/develop/_web/_hugo/artifacial/node_modules/vue-blu/build/dev-server.js'
I did npm install in the vue directory to load the dependencies. Obviously it is missing the whole build directory. I think I am missing something in the process?

Does the build directory exist ? There is not enough information to determine what cause the error. I think you can push the code to a repo or give more  information

The build directory is missing indeed. Do I need something to create it? I just npm installed vue-blu and did npm run dev in the vue-blu dir.

Because it's not a start kit project, it's a component library. so you need to do some other work. such as Vue, vue-cli. I think you'd better read the document of vue https://vuejs.org/v2/guide/
and install the vue-cli https://github.com/vuejs/vue-cli.
And, I will make an start kit project of vue-blu for user to use it more easier. maybe need some days

You are welcome :)  I will make vue-blu better.

Ok, got it working by directly linking to the cdn. In head <link rel="stylesheet"<EMAIL_ADDRESS>and near body bottom <script src="https://unpkg.com/vue/dist/vue.js"></script> and <script src="https://unpkg.com/vue-blu"></script>.
I would appreciate a pointer to a good tutorial on how to use this in a webpack build system, because in production I do want to strip out unneeded elements, minifying, etc.


Navigation Issue on mobile (Related to routes and sections)

Description
When you are on mobile and on home if you click on any button like books , DSA, developer tools or other then you will be redirected to that particular route. But from there if you click on any other menu items in navbar it is redirecting to sections on that particular route.
Expected Behavior
It should go to that particular route not on the section.
Video
screen-capture (1).webm

I can work on it.

good luck @saivinaygondrala

I can see everything working as expected.
https://github.com/user-attachments/assets/a6b45e2e-9e5b-4697-a2df-b64b9a898d27

Yes , It is working as expected.

Yes , It is working as expected.

So this issue can be closed


Feature/expose object to transform

Fixes #79
Also fixes a compilation error that was introduced in another PR I guess.

Any new on this PR @pleerock ?

Thanks for merging :) @pleerock Looking forward to contributing more to this project :)

Thank you for your contribution and sorry for a late response. Im quite busy with typeorm library right now and cannot afford myself to actively maintain other libraries as well (but I'll return activity back to them once majority of work on typeorm is done).
Your change was released in 0.1.8

Do not worry, I just thought you'd end up passing at some point. Keep up the good work, and thanks for releasing the change today too :) Very appreciated :)

@pleerock Just noticed that some changes from my PR were not merged :/ I updated the docs to and exposed a third argument "transformationType" in the callback, but those changes seem to have gone away :/


[FR] Check if input to model can be None by default

Is your feature request related to a problem? Please describe.
The model implementation can handle None inputs which would allow this argument being optional.
However, this could interfere with e.g. the coefficient calculation as pennylane searches for non-kwargs when looking for inputs or parameters.
Describe the solution you'd like
It would be nice to have input being None as default as in multiple cases, this would simplify calls to the model.
Describe alternatives you've considered
Keep as is.
Additional context
N/A

solved with #58


[RFC] Snark verify

Evan has provided some notes on Snark Verify. Can we ensure they are covered in our tech specs?
Thank you for contributing to Coda! Please see CONTRIBUTING.md if you haven't
yet.
Explain your changes here.
Explain how you tested your changes here.
Checklist:

[ ] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

Closes #0000
Closes #0000

Stale, closing


Recent Connections garbles first connection label in UI

Type: Bug
Starting with the latest 1.45.0 update the first connection in the Recent Connections window is garbled when it is first added.

Go to the Recent Connections list and clear it
Go to the Connections window and connect to any saved database connection
Go back to the Recent Connections list and the new connection shows up but is garbled text.

I have found that if you close ADS and open it back up then the problem is resolved. However I saw it get garbled in at least one other scenario initially but assumed it was an oddity and I don't remember what I did.
Azure Data Studio version: azuredatastudio 1.45.0 (8eff468100f02157f2219335f7a566d14451ca49, 2023-07-24T18:22:12.106Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Preview Features: Disabled
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.92GB (17.47GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

poor-sql-formatter
WSR
0.1.0

@cssuh can you help investigate the issue?

Hi @mtaylorfsmb, I'm having trouble reproducing this issue, here are the steps I took:

Clear recent connections list
Connect to a saved DB connection
Open recent connections list

This is what I see:

Are there any other details you can share to help me reproduce the issue on my end? Additionally, do you see any errors in the developer tools console when running into this issue?

This is most likely related with https://github.com/microsoft/azuredatastudio/issues/24027, let's keep an eye on it after the fix from PR #24038 arrives in insiders.

I have replicated the issue again and I think it reveals more of what the actual problem is. It might be related to the earlier mentioned issue, I don't know for sure.
It appears that the UI is overwriting the labels for one row with another row. In my case I was in the state where my groups weren't showing up, just the first connection in the default group. I typed in the name of a group to trigger the loading of the groups in the UI. But of course that filters out by connection name so I then cleared the group name from the filter box. At that point the UI shows a progress indicator below the filter box that never goes away. At this point the UI gets garbled. It is not properly refreshing the list of items as you expand and collapse nodes causing the garbled text I saw originally, I believe.

Hi @mtaylorfsmb
The fix is now available in insiders, could you give that a try?

@cheenamalhotra Just a quick test of the Insiders build shows that it appears to be fixed.

That sounds great! I will proceed to close the issue as fixed, please reopen if needed.


Add support for referencing event from data element library module.

When a data element is being retrieved from a condition or action of a rule, we should provide the rule's event object to the data element's library module. This will allow the data element to provide a value derived from the event. This can be useful when the event contains a snapshot of a user's data layer at the time the event occurred. It could also be useful if we ever want to provide rule-scoped data element types like Click Element ID.
This was requested by Stewart Schilling (Search Discovery) and corroborated by Lukas Cech.

Coverage remained the same at 97.929% when pulling 1a9143c68a4ac596b68eaa30bfe0d752b8892c0d on event-in-data-element into 2503593a16bd6b98a93bab28a090fa7793f6d60d on master.

Reviewed and approved in person by @celesterobinson.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/32810

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/34175

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/36190

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/37996

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/56287

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/71232


rolling update timeout

Type of change

Enhancement / new feature

Description
I messed up previous PR, reopening.
Checklist

[x] Write tests
[x] Make sure all tests pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[x] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging https://github.com/strimzi/strimzi/issues/127

Can I merge?


[Features] Node client support Promise

Can we support client return a Promise?
client.sayHello({name: user})
.then(res => {
  console.log('Greeting:', res.message);
})
.catch(err => throw err);

The Node API for GRPC is only callback based. But you can use promisifyAll() from bluebird library to create a promised based version of your grpc methods:
client.sayHelloAsync().then()

@sulliwane Thanks, I write a simple module that support both callback based and Promise,  grpc-promisify

I want to note that your grpc-promisify only works with single request/single response methods. With other types of methods, it will pass the wrong arguments and overwrite important information in the return value.

@murgatroid99 tks


Allow shareSingle to share attachments through emails

Overview

shareSingle on iOS does not support sharing files like Android. This PR changes the sharing logic to use allow for files to also be shared.
Note that this changes the way email sharing works with shareSingle.  That is, instead of opening the email app with an URL, it uses MFMailComposeViewController (similar to what the open call uses) to open the email view right on the app. One may consider this as a breaking change since it uses the app's UI layout tree.  For example, if share is called in a modal and the modal is closed, the share view will also close. However, it is a much smoother experience and matches the email behaviour when the open call is used.
Test Plan

Tested on iPhone 7.
Tested attaching local files (with url and type)
Tested attaching a base64 file as data:image/png;base64,${b64} with and without the filename property.

Should close https://github.com/react-native-community/react-native-share/issues/846

Any updates?

Did I miss any of the required review actions?

Any news? It has been a while already.

Any news? It has been a while already.

Sorry for the delay, I was having some problems focusing on other projects. Btw your PR looks great! We can go on merging this!
Thanks! 🚀 🚀 🚀 🚀 🚀

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

hi @cristianoccazinsp. I am trying to shareSingle a url using Email. On android it works as expected but on iOS the url is not added to the body. The url is to an external site. Any idea what could be wrong?

@t08-apporio can you share some code of what you're doing? Also iOS version, RN version, and react-native-share version.

Hi @cristianoccazinsp, here are the specifics
const shareEmail = {
 title: "title",
message: "message",
url: "https://example.com",
social: Share.social.EMAIL,
subject: "subject"
}

Share.shareSingle(shareEmail)
.then(response => handleResponse(response)
.catch(error => alert(error));

iOS: 14.0
RN: 0.63.4
react-native-share: 4.1.0

I believe you need to use email to set the email's TO address when using shareSingle instead of url.

the objective is to share a url via email. Email's "to" address needs to be added by the user after the mail app opens up. The message, subject are filled just fine. Only issue is that the url is not added to the body @cristianoccazinsp

In that case, I think you should be adding the URL manually to the email's body? Otherwise, it may be a bug, but it is not related to this PR at all. This PR just added attachments support to shareSingle.

ah shucks! thanks for your input @cristianoccazinsp. I'll open a new issue if its not already present

You should definitely pre-fill the body with the share URL, any reason not to do so? You are sharing with email specifically so it makes sense to build the body yourself. I believe the issue is the same I faced with attachments when I started this PR.

@cristianoccazinsp is it possible to pre-fill the mail body? I did not come across it in the documentation. Also I removed the message attribute and tried but that resulted in the email view not opening

Yes, setting message to some text should prefill the email body.

@cristianoccazinsp yeap. I was under the misconception that the message field will be used by other social media platforms. Anyway, thanks a lot for your help. If you don't mind, have you tried sharing on LinkedIn? On iOS it doesn't do anything, but on android it works

@t08-apporio sorry, I haven't really tested LinkedIn, but I wouldn't be surprised! The iOS side of this library is quite buggy, but should be working fine when using the generic share (when the user selects the platform).


Add recheck CLI

Codecov Report

Merging #83 (74dcf96) into main (19c0acd) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main       #83    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           43        50     +7
  Lines         2083      2340   +257
  Branches       115       119     +4
==========================================
+ Hits          2083      2340   +257

Impacted Files
Coverage Δ

...la/codes/quine/labo/recheck/cli/BatchCommand.scala
100.00% <100.00%> (ø)

...ala/codes/quine/labo/recheck/cli/InputConfig.scala
100.00% <100.00%> (ø)

...la/codes/quine/labo/recheck/cli/InputPattern.scala
100.00% <100.00%> (ø)

...main/scala/codes/quine/labo/recheck/cli/Main.scala
100.00% <100.00%> (ø)

.../main/scala/codes/quine/labo/recheck/cli/RPC.scala
100.00% <100.00%> (ø)

...scala/codes/quine/labo/recheck/cli/arguments.scala
100.00% <100.00%> (ø)

...in/scala/codes/quine/labo/recheck/cli/codecs.scala
100.00% <100.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

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


DRTRDOF

WHEN I OPEN DRTRDOF, I GET THE FOLLOWING ERROR

Dear @lk73438702,
It looks like your model is unstable after enabling DrTrDOF.
You appear to be using the IEA Wind 15-MW reference wind turbine atop the UMaine semisubmersible; is that correct?  I know that this model is not provided with the DrTrDOF enabled; is there a reason you want to enable it?  I'm not familiar with the background here, but I would guess that DTTorSpr is not set realistically for this model or that a smaller time step is needed when DrTrDOF is enabled.  This is probably a better question for the IEA Wind 15-MW reference wind turbine repository: https://github.com/IEAWindTask37/IEA-15-240-RWT/issues.
Best regards,


CAD-1407 stylish haskell

description

[x] stylish Haskell reformating of source code

checklist

[ ] compiles (cabal v2-build or stack build)
[ ] tests run successfully (cabal v2-test or stack test)
[ ] documentation added
[ ] link to an issue
[ ] add milestone (the current sprint)

bors r+


Updated media queries for Discord button

Description
Main issue fixed by updating media queries. The button now responds to all screen sizes without compromising the sizing.
Type of change
Please select everything applicable. Please, do not delete any lines.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Issue

[x] Is this related to a specific issue? Is so please specify:
#175

Checklist:

[x] I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@TreLynnnn Thanks for taking on this issue. I see the Login with Discord button is looking fancy! Great Work.

One thing I noticed though is I believe this change also impacted the logout with discord. Is there a way to keep box consistent between login and logout in terms of the box spacing?

Hey @TreLynnnn, I haven't gotten a hold of you. I hope everything is alright!
I am going to close out this PR as it's not completed, and we have someone else working on a landing page overhaul anyways.
Thank you for giving this a try!


Output all code blocks with "replace attributes" to make text replacement work

You can use the {attribute} text replacement format in code blocks too. It will by default not work and you have to add the option to allow this replacement e.g.:
[subs="attributes"]
====
<some code example>
====

We need text replacement in order to use the prompt entities for prefixing command examples. The code blocks should all be rendered with this subs option.

Can you give an example ? So it can be used as a testcase :wink:

#kommt aus den entities:
:prompt_root: root #

====
{prompt_root} <some code example>
====

vs.
#kommt aus den entities:
:prompt_root: root #

[subs="attributes"]
====
{prompt_root} <some code example>
====


WinSCP issue, Empty Editors

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:07:25.676Z)
OS Version: Windows_NT x64 10.0.10586
Extensions:

Extension
Author (truncated)
Version

google-search-ext
ade
0.1.2

jsrefactor
cms
1.4.1

jshint
dba
0.10.15

vscode-eslint
dba
1.2.11

python
don
0.7.0

xml
Dot
1.9.2

tslint
eg2
0.17.0

code-runner
for
0.6.33

macros
ged
1.2.0

gc-excelviewer
Gra
1.1.15

beautify
Hoo
1.1.1

output-colorizer
IBM
0.1.2

code-file-nav
jak
0.7.2

expand-region
let
0.0.3

sftp
lix
0.7.7

MagicPython
mag
1.0.12

Kotlin
mat
1.3.0

PowerShell
ms-
1.4.1

debugger-for-chrome
msj
3.1.8

advanced-new-file
pat
0.5.0

material-icon-theme
PKi
2.1.0

typescript-hero
rbb
1.4.0

java
red
0.8.0

vscode-icons
rob
7.12.0

vscode-dired
rru
0.0.4

code-settings-sync
Sha
2.8.2

vscode-table-formatter
shu
1.2.1

code-clip-ring
Sir
0.0.4

vscode-fileutils
sle
2.6.2

vscode-multiclip
sle
0.1.2

code-spell-checker
str
1.3.6

org-mode
too
0.1.3

vim
vsc
0.9.0

JavaScriptSnippets
xab
1.4.1

local-history
xyz
1.3.0

(6 theme extensions excluded)

Steps to Reproduce:

Open file from WinSCP
Extra empty editors show up:
'Code.exe' 'VS' 'Microsoft' 'Files'

this was not an issue before 1.15
Reproduces without extensions: Yes

@mizagog Please give more details, maybe with screenshots. Not clear how to 'Open file from WinSCP'

Sorry, wasn't sure how to add an image to my post :')
But now that i've looked more carefully at my screenshot, i realized i add some extra words in my file path, and after removing them the issue is resolved. thanks for your swift reply :)


Saving cost: 2 samples and 2 fixes for CI experiments

/gcbrun exp -n dg

/gcbrun exp -f -n dg

Report looking alright:
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-07-06-438-dg-comparison/index.html


Jetson AGX Xavier: calico-node pod failing to run: Bad return code from ipset list - Kernel error received: Invalid argument

calico fails to run on microk8s on an nvidia Jetson AGX Xavier:
ubuntu@xavier:~$ microk8s kubectl get pods,ds -n kube-system
NAME                                          READY   STATUS    RESTARTS   AGE
pod/calico-kube-controllers-847c8c99d-2g4nk   1/1     Running   0          81m
pod/calico-node-g8wvp                         0/1     Running   0          81m

NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/calico-node   1         1         0       1            0           kubernetes.io/os=linux   81m

Here's a sample of the calico-node pod logs:
goroutine 172 [running]:
github.com/sirupsen/logrus.Entry.log(0x40000d0180, 0x400040d170, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/go/pkg/mod/github.com/projectcalico/logrus@v1.0.4-calico/entry.go:128 +0x5d4
github.com/sirupsen/logrus.(*Entry).Panic(0x40003101e0, 0x40007dfbb8, 0x1, 0x1)
	/go/pkg/mod/github.com/projectcalico/logrus@v1.0.4-calico/entry.go:173 +0xb4
github.com/projectcalico/felix/ipsets.(*IPSets).ApplyUpdates(0x40002059e0)
	/go/pkg/mod/github.com/projectcalico/felix@v0.0.0-20200311115901-aa0a22d97c2d/ipsets/ipsets.go:342 +0x2bc
github.com/projectcalico/felix/dataplane/linux.(*InternalDataplane).apply.func1(0x40004ea500, 0x40005f1e70, 0x40002059e0)
	/go/pkg/mod/github.com/projectcalico/felix@v0.0.0-20200311115901-aa0a22d97c2d/dataplane/linux/int_dataplane.go:1290 +0x28
created by github.com/projectcalico/felix/dataplane/linux.(*InternalDataplane).apply
	/go/pkg/mod/github.com/projectcalico/felix@v0.0.0-20200311115901-aa0a22d97c2d/dataplane/linux/int_dataplane.go:1289 +0x310
2021-03-19 20:22:34.536 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.544 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.552 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.563 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.576 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.599 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.640 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.710 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:34.849 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:35.114 [ERROR][23453] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"
2021-03-19 20:22:35.635 [ERROR][23453] ipsets.go 916: Failed to read IP sets error=exit status 1 family="inet"
2021-03-19 20:22:35.635 [PANIC][23453] ipsets.go 342: Failed to update IP sets after multiple retries. family="inet"
panic: (*logrus.Entry) (0x16a11e0,0x40008c6140)

The Jetson AGX Xavier is an ARM architecture unit, this one runs Ubuntu 18.04.5 LTS aarch64
ubuntu@xavier:~$ uname -a
Linux xavier 4.9.201-tegra #1 SMP PREEMPT Fri Feb 19 08:42:04 PST 2021 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@xavier:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
Release:	18.04
Codename:	bionic

Is it possible that calico doesn't support the 4.9 kernel on this Jetson unit?
microk8s inspect tarball
inspection-report-20210319_213037.tar.gz

i can confirm that i am facing exactly same issue on jetson nano
2021-03-20 19:06:32.670 [ERROR][6756] ipsets.go 561: Bad return code from 'ipset list'. error=exit status 1 family="inet" stderr="ipset v6.38: Kernel error received: Invalid argument\n"

Did you try to use flannel?  In order to use flannel and etcd, you need to disable microk8s disable ha-cluster.

Did you try to use flannel? In order to use flannel and etcd, you need to disable microk8s disable ha-cluster.

yes, with flannel it works, callico apparently needs ipset module
only solution on jetson (l4t) platform is to custom compile kernel and enable modules needed for k8s

Thanks @hlacik for the info. Unfortunately I don't think there's anything MicroK8s can do here.

@davecore82 @hlacik this issue is reported to calico here https://github.com/projectcalico/felix/issues/2607.
Would upgrading the kernel be an option?

@davecore82 @hlacik this issue is reported to calico here projectcalico/felix#2607.
Would upgrading the kernel be an option?

well, nvidia-l4t linux distribution for jetson platform has custom kernel (4.9), luckily nvidia provides guide to rebuild custom kernel , so it is something i will have to do before going to production. For now, disabling ha-cluster and using flannel works .

Wrt to the gpu being enabled on arm arch, if we add it to the addon-list.yaml and rebuild the snap.
Then if you are keen, you can submit a PR. 😊

Did you try to use flannel? In order to use flannel and etcd, you need to disable microk8s disable ha-cluster.

Yes this is a good workaround for my use case, I don't need HA/clustering in this environment.

Then if you are keen, you can submit a PR.

@balchua well i have created this #2113  and it works!!

Hello,
I know this is a quite old issue but from my experience, generating the missing module is not that a big deal and clearly fixes the issue. I gave it a try today on my Jetson Nano JetPack 4.6 and it works.
I used the procedure described here (Troubleshooting/Jetson Nano): https://github.com/tekn0ir/toe
My 2 cents

Answering to myself - it seems another module is missing to have properly working calico-node on Jetson: ipip
For this one it is a bit more complicated as it is part of kernel and need to be configured as module in the source... but it is doable :-) good sources on how to do: https://developer.ridgerun.com/wiki/index.php?title=Jetson_Nano/Development/Building_the_Kernel_from_Source + https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3231/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fkernel_custom.html%23
It is recommended to get the sources from git (source_sync.sh) and sync to the correct tag (Eg: tegra-l4t-r32.6.1 for JetPack 4.6.1 = L4T 32-6-1)


fix: @Setting annotations placement

What this PR changes/adds
Puts all the @Setting annotation into classes that implements SystemExtension
Why it does that
improve autodoc and fix compilation
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Attention: Patch coverage is 96.89922% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 73.67%. Comparing base (7f20ba5) to head (aa7364d).
Report is 154 commits behind head on main.

Files
Patch %
Lines

...e/edc/connector/core/base/OkHttpClientFactory.java
83.33%
0 Missing and 1 partial :warning:

...a/org/eclipse/edc/iam/did/web/WebDidExtension.java
0.00%
1 Missing :warning:

...action/atomikos/DataSourceConfigurationParser.java
93.33%
1 Missing :warning:

...ane/TransferDataPlaneDefaultServicesExtension.java
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4024      +/-   ##
==========================================
+ Coverage   71.74%   73.67%   +1.92%
==========================================
  Files         919      985      +66
  Lines       18457    19948    +1491
  Branches     1037     1117      +80
==========================================
+ Hits        13242    14696    +1454
- Misses       4756     4776      +20
- Partials      459      476      +17

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


File lazy loading + SSR hydration issues

Describe the bug
Loading an SSR page that has a lazy file route leads to hydration errors (dev and prod) and a broken app.
Your Example Website or App
examples in this repo
Steps to Reproduce the Bug or Issue

fire up the basic-ssr-file-based example
adjust the index route to be lazy (e.g. index.lazy.tsx and adjusted lazy route export)
reload home page, see error

Additional context
The dynamic import is never invoked on the client on first load.
If you manually adjust the basic-ssr-file-based generated route tree to leverage the old style lazyRouteComponent, the index.lazy.tsx is correctly fetched on page load.
const IndexLazyRoute = createRoute({
  path: '/',
  getParentRoute: () => rootRoute,
  component: lazyRouteComponent(() => {
    console.log('LAZY!!!!')
    return import('./routes/index.lazy')
  }),
})

Compare that to the lazy file route approach and note that index.lazy.tsx is not fetched on page load (I guess the route's lazyFn is never invoked? Haven't dug deep yet), leading to hydration errors and a broken page:

Will quote my message here that I sent several days ago to discord chat
https://discord.com/channels/719702312431386674/1007702008448426065/1201778563528003584
I solved the problem by adding router.load() call before hydration as a temp fix.
Seems like current ssr recipes are not stable yet, so we will see.

Hi!
I am trying to use @tanstack/react-router with ssr + streaming based on Vinxi + SSR Streaming (file-based) example. Also worth to mention version 1.14.6
Just found out that hydration fails when router migrated to .lazy.tsx files from lazyRouteComponent + .component.tsx.
It seems like it breaks on lazy routes because hydration fails due to absence of component code during hydration.
You can find and fix it by adding await router.load() before starting react hydration, but I am not sure if it's correct because  load fn is intended to be used on a backend side.
The most common use case for this method is to call it when doing SSR to ensure that all of the critical data for the current route is loaded before attempting to stream or render the application to the client.
It worked like a charm before because of React.lazy wrapper around route.component property, but now it shifted to load component and other lazy code inside router.
I hope it will help someone.

I'm facing the same issue, really wish there was an example of this in the repository's examples folder so people could know the recommended implementation.
Even though I've used .lazy.tsx I feel like I haven't got the configuration right, sometimes having hydration problems, router infinity errors, and so on.

I solved the problem by adding router.load() call before hydration as a temp fix.

@kcoet the suggest by @ushakovfserg worked for me - no luck on your end?
Everything seems to be working in the ssr example I put together w SSRx - the load call is here -> https://github.com/TanStack/router/pull/1125/files#diff-e6355028e3797dc040644e9b512ab3da39c1da49fe9ba8af31dcc97abf331abfR13

@marbemac  It doesn't seem to be a problem in tanstack-router, but a problem in my Apollo configuration. I tried modifying it to use codesplitting https://github.com/TanStack/router/tree/main/examples/react/basic-ssr-file-based , it worked fine.
Hoping there's an example of Apollo's use.

Quick follow-up, while the router.load() call fixes the hydration issues, it also causes the client loaders to fire on initial load. Thus losing some of the benefit of hydrating server fetched data to the client since we're fetching more data than necessary.

Closing this issue since going forward, we want people to use the autoCodeSplitting flag in the vite plugin to handle the lazy loading. Therefore, no more .lazy suffixed files.

@SeanCassiere ah ok so is the intent to get rid of .lazy files altogether? Meaning an all or nothing approach for code splitting, or will autoCodeSplitting somehow allow for certain routes to be lazy and others not lazy?

@marbemac as of now, autoCodeSplitting is all or nothing.
It can be made configurable for sure. any idea how that config should look like?

Great question! I haven't looked into the plugin so I'm not sure what's realistic, but IMHO a threshold based approach would be awesome. E.g. threshold: 1024 * 10 - if a route's generated chunk is over 10kb, keep it split, otherwise ignore the route and don't split it out. Alternatively, a simple allowlist might be simpler (based on route path) but obv not as "auto" or seamless as the threshold based approach.


fix: makes apg script cross-platform

this PR makes the build script cross platform and work on windows :)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Autoscroll chat log

(at least) When in a battleroom, once the user scrolls up chat frame (log), then it's very difficult to control this log to automatically follow new messages.
You often must scroll manually with mouse to discover what anyone says at any time.

This should be fixed in https://github.com/skynet-gh/skylobby/releases/tag/0.9.5

This is not fixed as of version 0.9.8