Feat index list slot

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow DiDi's contributing guide.
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

update indexList to support pulldown and pullup solt
update indexList group tittle to support v-html

Codecov Report

Merging #211 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #211   +/-   ##
=======================================
  Coverage   92.18%   92.18%
=======================================
  Files         113      113
  Lines        2367     2367
  Branches      343      343
=======================================
  Hits         2182     2182
  Misses         93       93
  Partials       92       92

Impacted Files
Coverage Δ

src/components/index-list/index-list-group.vue
100% <ø> (ø)
:arrow_up:

src/components/index-list/index-list.vue
93.82% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Supabase + Sveltekit Auth

Supabase has finally begun to thoroughly document and maintain their Sveltekit-related docs, as the Sveltekit+Supabase stack is growing rapidly in popularity. The setup is pretty straight-forward, but involves a good deal of work that could be skipped.
Being able to plop all the stuff documented here directly into your new project using Svelte Add would be fantastic.

+1 !!

Please!


LLibrary crash

When I try to use this mod with mod library LLibrary, the game crashes on load.
Chiseled Me and LLibrary are the only mods in use.
Both of them individually work fine, but fail in combination.
crash-2020-09-03_22.50.02-client.txt

This exact error is fixed in the current discord beta

This exact error is fixed in the current discord beta

Fixed in ede2651


Added option for maxExpiration in verify

Adds the option to specify maxExpiration in the verify function.
It will require the token to include exp and iat in the payload, and exp has to be less than what is specified in maxExpiration.

@Sherex thank you for taking the time to open a good looking PR. I'm wondering tho - isn't this new option to the same end as the maxAge option? The only difference is when one of these throws.
Yours looks more like content validation to make sure it follows policy, where maxAge just throws when the policy is over reached regardless of the actual exp?

@panva Yeah that was the point, I felt it fitted more for an API solution, because the user has to know about the limit (or get an error message). That may avoid an unexpected time-out.
But it may also create more problems than it's worth. For example, if the server sets maxExpiration down 1 minute, then it may break other clients using that API...
And the user can't use a token which lasts forever, I feel like it's a tad more secure(?), but it might just be overcomplicating things.
I also didn't want to use the maxAge, because it was marked as deprecated in the .ts file.
Do you know if that's a bug?
DefinitelyTyped/jsonwebtoken
Npm module:
@types/jsonwebtoken

And the user can't use a token which lasts forever

maxAge is perfectly suited for that as well
Since the only thing that changes is WHEN an error is thrown i don't think this PR is needed, it would introduce just another way of doing what's already possible. Unlike the other options exp is a sliding target.

I also didn't want to use the maxAge, because it was marked as deprecated in the .ts file.
Do you know if that's a bug?

I don't know why the types say this is deprecated. We're not the maintainers of those types and it does look like a bug with the types, nothing in the code seems to suggest the option is deprecated.

Yups, I agree, probably best to leave it as is. :)
Thanks for the review!

thanks @Sherex


Cannot find js-controller

Describe the bug
On console after run this command node main

Cannot find js-controller

On console after run this command iobroker -v

bash: iobroker: command not found

Versions:

Adapter version:   ??
JS-Controller version:??
Node version: v21.6.1
Operating system: Debian GNU/Linux 12 (docker)

Screenshot

I don't see where this is an adapter problem.
Please use iobroker to install and run this adapter.

thank you for your reply
i run my docker-compose

after that enter into container iobrocker
run install

npm i iobroker.senec

go to browser

add adpter
Go to home
run senec

but after :

File index.html not found
where I go wrong?


Column alias with same name as column causes pinot to hang

If you have a function on a column and then alias that to the same column name pinot hangs.
To reproduce start the quick start batch and run the following query:
select cast(runs as long) as runs from baseballStats limit 10

This query works:
select cast(runs as long) as runs2 from baseballStats limit 10

working on it

this issue is fixed as part of this PR https://github.com/apache/pinot/pull/7576/, just verified it.

@xiangfu0 @elonazoulay Can you please verify the fix and close the issue if the issue is fixed?

Apologies for the delay. This is fixed! Thanks @SandishKumarHN , @Jackie-Jiang @xiangfu0 !


Do not emit 'up' on 'drop'

Closes #66
@williamngan here you go, I fixed it not at the UIDragger level but at the Space level since space events "suffered the same fate" 😄.
Hope it looks good to you. One "major" change is some click event are not emitted anymore. Is there any other place I might not know about that relies on them?

Hi @tibotiber , thanks for you help on this! I tested this in various case. It seems to work well except in this case --
Try the following in the ui.track demo

Click on the red dot (without moving)
The dragging state is active, so when you move the pointer (without dragging), it acts as if dragging
Click again and the drop is ignored. Which means you cannot release the dragged item.

Any suggestions on how to fix this?
Unrelated, but I also found and fixed another bug. In unhold(), the javascript splice function actually would return the deleted items (javascript still caught me off guard sometimes! 😅), so I was wrong to assign it back to the array. It's now fixed in https://github.com/williamngan/pts/commit/fed4d1e3d189aa00c850f06dabf2c82034e29d7b so please pull the latest from master first.
Thank you!

Hi @williamngan, good catch! I've fixed it by starting the drag logic on drag instead of down, mirroring the stop on drop instead of up. Seems to work from my tests but will see if you catch anything else.
I've rebased on top of master as well, thanks for the heads up.

Thanks @tibotiber for the fixes. This should be good to go!


Enhancement: support DTO config inheritance

When inheriting a DTO factory class, there is no way to merge the config of the inherited type with a config defined on the new class.
One idea is to have a callback method on AbstractDTO that handles the case where a 2nd config object is found in the mro of the DTO type.. something like:
class AbstractDTO:
    ...

    @staticmethod
    def merge_configs(old: DTOConfig, new: DTOConfig) -> DTOConfig:
        return new

Default would just return the latest one, which would preserve current overwrite behavior, but then you could do something like:
class MyDTO(PydanticDTO[...]):
    ...

    @staticmethod
    def merge_configs(old: DTOConfig, new: DTOConfig) -> DTOConfig:
        new.rename.update(old.rename)
        return new

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh Litestar dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

Other approaches I can think of:
class MyDTO(PydanticDTO[...]):
    default_configs = [
        DefaultConfig(name="exclude", value={"id"}, strategy="merge"),
    ]

Or, have the config object itself receive a merge callback that is called whenever we detect a config object is about to be overwritten by another config object in the MRO.
def merge_callback(self: DTOConfig, new: DTOConfig) -> DTOConfig:
    return new.replace(exclude=self.exclude | new.exclude)

class BaseDTO(SQLAlchemyDTO[T]):
    config = DTOConfig(exclude={"id"}, merge_callback=merge_callback)

Other approaches I can think of:
class MyDTO(PydanticDTO[...]):
    default_configs = [
        DefaultConfig(name="exclude", value={"id"}, strategy="merge"),
    ]

What other strategies than merge would be useful to have as a default?

Or, have the config object itself receive a merge callback that is called whenever we detect a config object is about to be overwritten by another config object in the MRO.
def merge_callback(self: DTOConfig, new: DTOConfig) -> DTOConfig:
    return new.replace(exclude=self.exclude | new.exclude)

class BaseDTO(SQLAlchemyDTO[T]):
    config = DTOConfig(exclude={"id"}, merge_callback=merge_callback)

I like the idea of being able to supply a callable somehow, but I'm not sure if a method on the DTO or a callback is better :shrug:
The callback would allow a mixed approach though:
DTOConfig(..., merge_configs="merge")
DTOConfig(..., merge_configs="update")

def merge_configs(self: DTOConfig, other: DTOConfig) -> DTOConfig:
  return other.replace(exclude=self.exclude | other.exclude)

DTOConfig(..., merge_configs=merge_configs)


[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

Justification, Sync deps after eventing cut -slinkydeveloper
/cc knative-sandbox/source-wg-leads
/assign knative-sandbox/source-wg-leads

/assign

/assign

/lgtm
/approve

/lgtm
/approve


Update fileio.rst

added .cas.gz, .cas.h5 support

Codecov Report

Merging #601 (1a0db4c) into main (fdb2f04) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #601   +/-   ##
=======================================
  Coverage   76.08%   76.08%
=======================================
  Files          32       32
  Lines        2271     2271
=======================================
  Hits         1728     1728
  Misses        543      543


WIP: ci/cd: Migrate Tern from CircleCI to GH Actions

This commit translates the current lint/test suite from the circleci
yaml file to a new yaml file that will be run by GitHub actions.
Fixes #492
Signed-off-by: Rose Judge<EMAIL_ADDRESS>

Closing this PR as some experimentation is still needed. Will open a new one when it's ready for Tern's repository.


ERR_PACKAGE_PATH_NOT_EXPORTED when trying to use nuxt 2 module

Hi, first of all, thanks for the cool module!
I'm trying to implement it in my nuxt 2 project, I got to the point about connecting the module to buildModules: https://github.com/posva/mande?tab=readme-ov-file#nuxt-2
// nuxt.config.js
module.exports = {
  buildModules: ['mande/nuxt'],
}

But it looks like something is wrong with the exports in the package, and I can't run the build (or dev):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './nuxt' is not defined by "exports" in /home/projects/mande-nuxt/node_modules/mande/package.json

Package
Version

mande
2.0.9

nuxt
2.17.3

node
20.13.1

Here's a small reproduction: https://stackblitz.com/edit/mande-nuxt ✌

Sorry for the delay, I don't use nuxt 2 anymore and it's already reached EOL so I won't be able to give this time. I will probably remove the Nuxt 2 section from the readme in the near future.


Updates on ci and sign binaries and images with cosign

Updates on ci and sign binaries and images with cosign

rehearsal: https://github.com/cpanato/kubepug/releases/tag/v99.99.01
job: https://github.com/cpanato/kubepug/actions/runs/4649977502/jobs/8228692130 failed in the krew but that is expected running in a fork

/assign @rikatz


Range query don't work with @timestamp "now-5m", but the query string it generated works in kibana.

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[X] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
ctx := context.Backgruond()
range_query := elastic.NewRangeQuery("@timestamp").Gte("now-5m")
bool_query := elastic.NewBoolQuery().Filter(range_query)

I use the Source function from the BoolQuery struct. and get this
{"bool":{"filter":{"range":{"@timestamp":{"from":"now-5m","include_lower":true,"include_upper":true,"to":null}}}
and if I put it in Count.
client.Count(index_name).Query(bool_query).Do(ctx)

The query string just like blow:
{"query":{"bool":{"filter":{"range":{"@timestamp":{"from":"now-5m","include_lower":true,"include_upper":true,"to":null}}}}}}
Then I execute CountService's Do function.
if I use the query string in Kibana. it works.
the excepted behavior is it show return the numbers the Kibana returned.
Please describe the actual behavior
counts just keep return 0.
Any steps to reproduce the behavior?
if I use bool query with match query .it works.
if I use range query with range query with some numeric value. it works too.
but if i use range query with @timestamp. it just don't work.

I changed argument from "not-5m" to time.Time.
it still not working.

I think i found the issue. my bad. cause I defined the index. which did't contain 'now-5m' time range.


[FEATURE REQ][COSMOS] Expose the Feed Processor Lag as part of API

Is your feature request related to a problem? Please describe.
Need access to the lag per partition for the ChangeFeedProcessor worker (similar to GetEstimatedRemainingWorkPerPartitionAsync) for tracking purpose.
Describe the solution you'd like
Make the com.azure.data.cosmos.internal.changefeed.ChangeFeedObserver public along with ChangeFeedObserverContext and expose the lag stats in the context class
Describe alternatives you've considered
Currently I am relying on implementation details via logic similar to .net RemainingWorkEstimator in my implementation where I need to case the builder to ChangeFeedProcessorBuilderImpl and then register a custom observerFactory
Additional context
Such a feature is supported by .Net implementation for change feed processor
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

In addition please also expose the full ChangeFeedObserver which enables returning Mono
Mono<Void> processChanges(ChangeFeedObserverContext context, List<CosmosItemProperties> docs)

This would allow us to chain the Future returned from downstream processing of feed (in our case a write to Kafka) and avoid adding an arbitrary Await call to force waiting for actual downstream processing to complete.
See here for an example usage which currently rely on implementation details
private object ObserverBridge extends com.azure.data.cosmos.internal.changefeed.ChangeFeedObserver {
    override def open(context: ChangeFeedObserverContext): Unit = {}
    override def close(context: ChangeFeedObserverContext, reason: ChangeFeedObserverCloseReason): Unit = {}
    override def processChanges(context: ChangeFeedObserverContext,
                                docs: util.List[CosmosItemProperties]): Mono[Void] = {
      val f = observer.process(context, docs.asScala.toList).map(_ => null).toJava.toCompletableFuture
      Mono.fromFuture(f)
    }
  }

Started coding this feature request; this feature will be rolled out as part of the 4.x version of the Cosmos SDK to start with and will return an estimate for each lease document and current assigned host/worker thread.


Model compress example user experience

The model compress example directory (examples/model_compress) is very confusing.

It seems configure_example.yaml is useless.

There is no guide about how to run the examples.

I tried with python main_torch_pruner.py,  there is no any information about model compress/sparsity in the output, the output looks like this:

Processing...
Done!
Module  does not have parameter "weight"
# Epoch 0 #
 0%  Loss 2.306724786758423
11%  Loss 0.3890495002269745
21%  Loss 0.24405378103256226
32%  Loss 0.38694724440574646
43%  Loss 0.18668800592422485
9920512it [00:29, 558515.07it/s]                                                                                53%  Loss 0.22311894595623016
64%  Loss 0.20908677577972412
75%  Loss 0.1498120278120041
85%  Loss 0.075614333152771
96%  Loss 0.04789094254374504
Loss: 0.11596445617675781  Accuracy: 96.47%)
...
# Epoch 9 #
 0%  Loss 0.08927597105503082
11%  Loss 0.018723296001553535
21%  Loss 0.018285473808646202
32%  Loss 0.014593178406357765
43%  Loss 0.0168264489620924
53%  Loss 0.03268904611468315
64%  Loss 0.021244840696454048
75%  Loss 0.007444677408784628
85%  Loss 0.003078282345086336
96%  Loss 0.013677495531737804
Loss: 0.030250001430511476  Accuracy: 98.98%)

9920512it [05:47, 28560.55it/s]

Module  does not have parameter "weight"

@chicm-ms could we close this issue now?

Sure.


Dynamic Table bug

Hi, the template very good until I found a bug which layout is okay on HTML but when on PHP, it have excess long spaces after the table. (Maybe the height of table did not recalculated?).
I have tried:

Open with Mozilla Firefox and Google Chrome but return same result not working
Clear cache not working
Resize browser window (larger or smaller) the white space removed automatically 👍

Unfortunately this is a HTML template and since is ok there we're gonna close this for now but feel free to open another one whenever you want with a HTML/CSS/JS issue/help etc.


Could we have spotted the missing jvmti support in JDK19 on non-x64/aarch64 platforms?

Under some of the testing performed during the release cycle for JDK19 we discovered that the --enable-preview option resulted in jvmti support not being available on certain platforms (Notably the ones where a full Virtual Threads implementation was not available - everything except the x86-64 and aarch64 platforms).
Could we have pre-emptively caught this as part of the regular test cycles in order to avoid hitting the problem during the release cycle, and if not is there anything we could put in place to get early warning of such a problem in the future?

The answer is yes, if someone had been triaging the jdk19 pipelines, those failures were present in nightly and weekly runs.
Example:
https://trss.adoptium.net/output/test?id=63130ae993ac60470b274021
[2022-09-03T04:15:39.295Z] Exception in thread "main" java.lang.UnsupportedOperationException: Unsupported os, arch, or address size: Linux, s390x, 64
[2022-09-03T04:15:39.295Z] 	at java.base/jdk.internal.foreign.CABI.current(CABI.java:69)
[2022-09-03T04:15:39.295Z] 	at java.base/jdk.internal.foreign.abi.SharedUtils.getSystemLinker(SharedUtils.java:237)
[2022-09-03T04:15:39.295Z] 	at java.base/java.lang.foreign.Linker.nativeLinker(Linker.java:198)
[2022-09-03T04:15:39.295Z] 	at ImplicitAttach.main(ImplicitAttach.java:48)

Also if the advisement of the release checklist to run a trial release pipeline a week ahead of the release had been followed, these failures would have been spotted.

Looks like it was removed from https://github.com/adoptium/adoptium/issues/171.
Closing this issue, as the 'action' to take is to monitor the test pipelines, and follow the release checklist.
Noting that testing is still disabled, so any nightly monitoring will happen once testing is re-enabled, which likely needs to be added to the checklist to remind release champions. (see https://github.com/adoptium/adoptium/issues/177).

Those failures are in the FFI tests which is equally valid although digging into jvmti it looks like they might be excluded somewhere so we wouldn't have picked them up:
Looking at https://github.com/adoptium/aqa-tests/blob/f494e46151a96f625bfb24f12a6cc3241721405b/openjdk/playlist.xml#L189 it looks like hotspot_serviceability which contains the jvmti tests are only being run for JDK8/9 but only a subset (excluding jvmti) are in those logs and I can't see any indication of the serviceability ones being run in the 19 logs.
So I guess the questions are

Should the serviceability tests be excluded for later versions? (A trial on JDK19 shows it is a bit messy although even some of the "passing" ones in there seem to be failing when I click on them) - most are complaining about Use -nativepath to specify the location of native code but I guess that may be easy to resolve without too much of a problem - possible related issue.
What is excluding jvmti from the serviceability tests and should that be reversed? (2/4 are listed in ProblemList_openjdk9.txt) but unclear why none are run)

FYI @sophia-guo since we were discussing this earlier.
It probably makes sense to either change the title on this issue now or open a new one to cover attempting to re-enable jvmti. While the FFI tests are also failing, those are enabled and running so could have been caught, but not the jvmti ones.

Enable serviceability_jvmti tests (serviceability/jvmti) for 19+ https://github.com/adoptium/aqa-tests/pull/4035/files. Note those tests are not running with option --enable-preview, which probably should be solved by adding option tests in upstream openjdk repo.
All Loom related targets are as following, which can be gradually enabled when it's ready.
tier1_loom =
:tier1_loom_runtime
:tier1_loom_serviceability
tier1_loom_runtime =
runtime/vthread
runtime/jni/IsVirtualThread
tier1_loom_serviceability =
serviceability/jvmti/vthread
serviceability/jvmti/events
serviceability/dcmd/thread

See also: https://bugs.openjdk.org/browse/JDK-8287726 Does aquavit handle \@require tags in jtreg?

See also: https://bugs.openjdk.org/browse/JDK-8287726 Does aquavit handle @require tags in jtreg?

Yes, aqavit using jtreg running openjdk tests. All jtreg features are supported by default.


PEP8 line lengths

References #48

Thanks!

@MarkoMackic Is there any reason you add blank line before closing """?

Nope, I corrected it

Could you resolve conflicts ? I would but don't really know how


Problem when using no action bar theme across the app

When the action bar is hidden using custom theme from tiapp.xml the crop window won't show the action bar (and hence the crop button) even if you specify an action bar theme from styles in the crop method options. Following is how I am using themes:
App theme in tiapp.xml:    Theme.NoActionBar  (Action bar hidden)
theme in crop method:    Theme.BlueActionBar (Action bar exists)
Result:   Action bar (and so the top actions) not displayed in the crop window.
App theme in tiapp.xml:    Theme.BlueActionBar  (Action bar hidden)
Result:   Action bar (and so the top actions) are displayed in the crop window.
I am using Titanium SDK 7.0.2.GA.

Can you try by renaming your themes like NoActionBar and BlueActionBar as I guess its the period (.) in your theme name causing this issue?

Just trying to find out if this issue has been resolved? Would love to use the module but no way around the 'crop' button missing from no action bar showing.

@emptybox you can use an action bar enabled theme specifically for the crop window with the theme property. I ended up enabling the action bar for whole app from tiapp and hiding it on windows where I needed.

Thanks! I was hoping to do the opposite and enable the action bar on demand
but I'll try this.
On Sun, Aug 26, 2018 at 21:43 qasim90<EMAIL_ADDRESS>wrote:

@emptybox https://github.com/emptybox you can use an action bar enabled
theme specifically for the crop window with the theme property. I ended
up enabling the action bar for whole app from tiapp and hiding it on
windows where I needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prashantsaini1/android-titanium-imagecropper/issues/3#issuecomment-416112662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE5ocvMYw6MloW4P5Do6rYfL7gTESFzks5uU3jjgaJpZM4TALcK
.

--
Sent from Gmail Mobile

@emptybox you can set any action-bar enabled theme to the theme attribute in the module code. please refer the docs for more details. If no theme is provided, then only the app-wide theme will be used.


Update formStateUseEffect.ts

Removed TS specific code from JS Example

removed FormInputs type from line 11. (Since it is a TS specific code in JS)

thanks. 👍


Update with 2017 holidays

The on-demand site lists the dates when GitHub's trainers will not be available to offer assistance via Gitter. This PR updates the list to reflect the actual dates for 2017.
I also added a heading so people would know which year was reflected in the chart!
@github/services-training will merge with 1 :+1:

:heart: thank you @hectorsector


IDL Hashing does not follow upgrade spec

Describe the bug
By adding a new field to an error variant, I get back an error Cannot find field hash _2102411630_ when using a version of the generated delcarations without the new variant.
To Reproduce

Deploy canister with type

  public type CreateInvoiceErr = {
    message : ?Text;
    kind : {
      #BadSize;
      #InvalidToken;
      #InvalidAmount;
      #InvalidDestination;
      #InvalidDetails;
      #MaxInvoicesReached;
      #Other;
    };
  };

Generate declarations
Add type #NotAuthorized;
Redeploy, and make call using prior declarations

Expected behavior
Agent JS should make the call without the most up to date interface

@chenyan-dfinity would you agree that this behavior is incorrect as-is?

With the current implementation, I think we won't get the error unless you are sending the new tag #NotAuthorized as the value.
With the new spec change, the error variant should also be inside an opt value, so that when the client sees an unknown tag, we change it to null. See https://github.com/dfinity/candid/issues/295. This has not been implemented in JS yet.

I'm getting the error when receiving the new tag from the canister. Could we switch to a console.warn approach, while allowing the application logic to decide how to handle the unexpected tag?

That's the goal. The error type should be opt CreateInvoiceErr, then null indicates the unknown tag.


Feature: dark mode

Is your feature request related to a problem? Please describe.
My eyes, I go blind at night when I see the screen, this window is very bright.
Describe the solution you'd like
They could place a selection of themes to change the colors to suit one.
Describe alternatives you've considered
use the colors used by gtk / kde apps and use those colors / themes
Additional context
try to change the dependency of the use of npm for yarn, I use yarn instead of npm but well it is not so important but I must mention it since npm is not the only one.

Additional context for anyone who comes across this issue:

We'd very much like to include a dark-mode option in Web UI (and, by extension, Desktop)
Current timeline would involve including this work in a larger-scale revisiting of Web UI/Desktop, likely in Q2/3 2021
If anyone is interested in PRing something earlier, contributions are most welcome!

Additional context for anyone who comes across this issue:

We'd very much like to include a dark-mode option in Web UI (and, by extension, Desktop)
Current timeline would involve including this work in a larger-scale revisiting of Web UI/Desktop, likely in Q2/3 2021
If anyone is interested in PRing something earlier, contributions are most welcome!

If someone wants to work on this:

speed up your work by copying colors generated  by https://darkreader.org for now

we can refine and bubble up them to https://github.com/ipfs-shipyard/ipfs-css later

Hello,
Any news on this ?
Thanks

Photosensitive user here; I sadly just had to uninstall the desktop app due to the blindingly-bright screen with no dark mode option. Support for dark mode would be greatly appreciated! I'll be sticking to the CLI for now :blush:

The colors are pretty spread out in the js files. Guess a theme-switch button will really be needed -- no easy path with only changing a CSS file with @media (prefers-color-scheme). Well, I mean, you can do the same query with JS, but if you're changing the JS you might as well add a button.


ToastVisual does not allow adding image element

According to the schema, we can put <image placement="inline"> inside <visual>. However, that is not possible at the moment.

Hmm, there's supposed to be an InlineImages property on the ToastVisual class, but it's not showing up for some reason. I'm looking into it. Thanks for catching that!

So it turns out there's a bug in VS 2015 where IntelliSense doesn't expose the collection properties.
There's two ways you can add inline images. You can use the cool C# feature, but IntelliSense won't tell you that InlineImages exists (type it anyways, and it'll compile)...
ToastVisual visual = new ToastVisual()
{
    InlineImages =
    {
        new ToastImageSource("http://msn.com/image.jpg")
    }
};

Or the classic way...
ToastVisual visual = new ToastVisual();
visual.InlineImages.Add(new ToastImageSource("http://msn.com/image.jpg"));

Note that the cool C# way works with initializing StackPanel children, Grid children, etc... anything that has a collection property can be initialized using that first syntax. It's pretty neat. But I only found out now that IntelliSense doesn't properly expose those collection properties. It DOES expose it if you're referencing the project in your own solution (which is what I did, which is why from my perspective it was working fine), but when you reference the DLL, IntelliSense doesn't pick up those collection properties.


Fixed issue with Highchart's global binding of pointer up event

I had been having an issue that would only manifest itself after loading a component in my application that used a chart. I traced it back to Highchart binding on pointer up events global causing odd issues such as click events not reaching the component. I solved this issue by running the initChart call in ChartComponent.ts outside of Angular.

@gevgeny : Please review and merge this PR. lot of click events get highjacked and stop working, post including this library.


i can not use direction key when i connect bash on Windows 10?

it is really a beautiful terminal, but when i use bash on Windows, it seems the direction key don't work?

Duplicate #1127

thanks Chabu


open outline in tab, left sidebar, or right sidebar by default

enhancement: choose default behavior for opening the outline view. options: new tab, left sidebar, and right sidebar

Thank you for your suggestion.
Displaying it in the left sidebar seems not difficult. I have to look into how to display it on a tab later.
Do you know of any community plugins that can be configured like this that I could refer to?

Hi! I'm aware that the Custom Frames plugin has this functionality.

Sorry for the late reply, and thank you for the information!
I think I can implement this in the next update.

Implemented in v0.5.0. Let me know if you have any problems with it working!


Use ref mounted

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


storeName not changing when calling config

When calling config like this:
localforage.config({         driver: [localforage.INDEXEDDB],         name: 'RoadPro',         storeName: "order_50015",         description: 'RoadPro Local Storage'     });
Then I call the iterate function and it iterates on the previous loaded config.
localForage is using the previous config called on the same page.
logging localforage.config() returns this after setting config.
description: ""
driver: "asyncStorage"
name: "RoadPro"
size: 4980736
storeName: "order_500775"
version: 1

If I refresh the page and run again, the config is set correctly the first time, but doesn't change until I refresh the page.  Have you guys seen this or run into this problem?  I'm using the newest version of localforage.  I think it was working correctly a few months ago?  Thanks for your help!
Cheers!
Scott

#1028 may be related to this as I'm experiencing similar issues, I tried first to call the config function before any other calls to localforage, then that kept iterating on the previous database and split it (even after a fresh install). So I went the route of trying to change the defaults from localforage.js so that they HAD to be the ones I set and you still get a database created called "localforage"


Search Ranges

Goodnight,
I have used bitcrack a couple of times, I have never found a pkey, and I am quite new to the subject.
I was using the following code:
G:\BitCrack\clBitCrack.exe -b 42 -t 256 -p 5600 --keyspace 7cce5efdaccf6808: 1a838b13505b26867 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -o G:\BitCrack\keys.txt
Since I have read almost all the issues.
Use that code because on this website: https://privatekeys.pw/puzzles/bitcoin-puzzle-tx puzzle number 64 was not solved and is within that range.
My question is, how to know in which range of keyspace an address would be found, for example this: 1MLbqQELxgnyQLAFS1ZgaJUUhDGh5AtoRd
I have a pc with an rx460 video card that runs at 35Mkeys/s.
Thank you very much for your help.

cuBitCrack.exe --keyspace ffffffffffffffff:8000000000000000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
That is the effective range for #64, from start to end. Are you using a custom range?


replace lodash.* dependencies

This changes reduce my bundle size from 700kB to 691kB. 9kB is a small changes, but for example... if I use 10 packages with 9kB overhead... it's 90kb useless code.

Today I reduce my bundle size from 750kB to 517kB (gzipped) ~30% :smile:

Hi, this looks good. I will merge for the next release. I had not come across 'just' before, thanks for the heads up!


Feedback on Focus Area: Innovation Value

This issue is for developing Value WG focus area: Innovation Value
Goal of this focus area: Evaluating open source project development for comparing with in-house and outsourcing options
Please suggest changes, add questions, and provide feedback inside the google doc:
https://docs.google.com/document/d/1q40ljJZ93AYbaxH1jewLWzHRKe892uavD2bgSA3ybp0/edit#

Moving comments out of Google doc to here:)
Questions for companies who wish to measure "innovoation" value
If we didn’t use “this piece” of open source technology, we’d have to build it, or buy it. How much would it cost us to do so?  Calculation framework to include:

Estimated cost to build from scratch (offer a low, medium, high estimate framework and average them  Do this for BOTH dollar cost and labor time cost).

Estimated cost of licensing (offer a low, medium and high licensing price input, and average them).

Estimated Opportunity Cost calculation

Work with product owners to estimate the real dollar value of a feature being delivered (eg, how much additional revenue or savings are estimated to be delivered by a feature in a given year?)
Take time cost from A  (how many dev hours it would take to build), subtract those hours from how many dev hours your current team can provide in a given time period (for example, 160 hours = 1 dev/month).
An example:
If a given feature is going to save $120,000/year, then the opportunity cost of each month it's not implemented is $10k per month.
If that feature was going to require 160 dev hours to complete; but instead that dev has to write something else that could have been done in open source instead, then the opportunity cost to the business of NOT using an Open Source solution is $10k/month.
BTW, the opportunity cost ties directly to a companies capacity for teams to have TIME to innovate:) So we could say "innovation opportunity cost" - might be more contextual.

Thanks @mpgjon. I think a lot of these values are going to have to be local parameters used by individual companies. I know that right now, there is similar discussion on a release candidate metric around labor investment.

Thanks @germonprez  - 100% agree.  Is there some sort of web-based value calculator on the roadmap?  We could help individual companies understand what parameters might be most helpful with a guided calc of some sort (we could also use a set of web-based calcs to anonymously gather inputs as research data points - as long as we disclose the anonymous collection)

I don't think I'd call it a roadmap but here is a link to the candidate metric for Investment by Organization:
https://chaoss.community/metric-labor-investment-by-organization/
You'll see that this starts with Issues but PRs will play a role in future versions. Along with other things, I suspect.
This is a start in this area. In short, the idea is that people could download raw data (CSV) and then manipulate it locally. I think a next step would be to start building this type of manipulation into a UI so that you don't have download the data.

Thanks for the link - is that page in the chaoss/website repo?  Two of the three literature links at the bottom don't seem to resolve:) (Creating an OSPO, and OS in the Enterprise).

@mpgjon - thanks for these notes.  I expect value will be expressed in different forms depending on business context.  One context is economic cost to get the work done (like a buy vs build or inhouse/outsource evaluation).  Another context is economic value and competitive advantage of achieving a dominant market position.  For example - https://www.forbes.com/sites/jeanbaptiste/2019/07/01/bill-gates-admits-that-his-biggest-mistake-was-letting-android-win-costing-microsoft-400-billion/#17d9a9205689

Closing now that our first metrics are published.


Rate Limiting

https://sendgrid.com/docs/Glossary/rate_limiting.html
"Please visit our pricing page to see the account specific sending limits."
The pricing page does not specify any details or information about rate limiting per different accounts.

@greganth - great catch! this is for sure outdated.
I'm going to open this one up for the community.
The to do here is to remove "Please visit our pricing page to see the account specific sending limits." from https://sendgrid.com/docs/Glossary/rate_limiting.html
This would be a great first PR.

It would be even better if the rate limits per plan were listed somewhere. That information isn't available anywhere (that I can find).

Actually, after looking at this more closely, this is not an issue with the docs. The number of emails you can send per plan is on the pricing page. If you select your plan, scroll down, and it tells you how many emails included in that plan and the cost of sending more emails than your plan. Note that there is no actual limit - you can send as many as you want, you just might get overages depending on your plan.


Add check to avoid crash with dummy links

this fix  avoid crashes with dummy links

any update on this @poweic ?

any update on this @poweic ?


Extension: Timestamps

An extension that adds on top of core and lists timestamp property names for the whole lifetime of a field (boundary) seems to be important.

I'd love to moderate this and create the extension, but I'd need some input from experts about timestamps in field boundaries. Who would be interested in discussing this?

Will be developed here: https://github.com/fiboa/timestamps-extension


Redesign all Detail pages

All the detail pages will need to be redesigned.
@lvuch - will give you mocks
@vincent99 - will give you the new top menu

@tani review and provide feedback https://xd.adobe.com/view/b38835cd-fc89-4e0a-b89b-4ff9114e404c-e6db/

@lvuch Hello. Thank you for calling me. However, I guess it is not me. Have a good day!

@lvuch my only comment is events would be a tab and not a table beneath the tabs.  The labels/annotation section is between you and Vincent.

I think this issue has been ready to validate.
We refactored all the detail pages, made it stick in dashboard style.
Could you help us to check the detail pages?
@lvuch @DoNotSayYes


Unable to run db:migrate

Got the following error when run bundle exec rake db:migrate
NoMethodError: undefined method `delegate_belongs_to' for #Class:0x007fe455c5e3d8
Did you mean?  delegate_missing_to
Solidus version 2.4.2
ruby v 2.4.0
Thanks

Hi, @ahwong5, could you update and try again, please?


ImportError: No module named carla

hi,
OS: ubuntu20.04
unreal engine: 4.26.2
carla: latest, pull from github master
run make launch to run CarlaUE4 and press play button, then , run python tutorial.py
but i get the error :
Traceback (most recent call last):
File "tutorial.py", line 21, in
import carla
ImportError: No module named carla

change to python3 , it works. but unreal engine collapse very often.

I have the same problem,
OS: windows10
Carla: 0.9.11
python: 3.7
I can see carla0.9.11 package when I input pip list   in command， but I cannot import carla

To solve this issue pip3 unintsll carla
make clean
make PythonAPI
make launch

If this solves your issue would you be happy to close this issue?


feat(rich-text-editor): DLT-1601 add channel suggestions

feat(rich-text-editor): add channel suggestions

Obligatory GIF (super important!)

:hammer_and_wrench: Type Of Change

These types will increment the version number on release:

[x] Feature

:book: Jira Ticket
https://dialpad.atlassian.net/browse/DLT-1601
:book: Description
Created a new instance of the TipTap mentions plugin to support channel mentions. This can be enabled by the new channelSuggestions prop. Very similar to the existing user mentions.
:bulb: Context
Needed to support channel mentions in the new message input.
:pencil: Checklist

For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.
[x] I have added all relevant documentation.
[x] I have considered the performance impact of my change.

For all Vue changes:

[x] I have made my changes in Vue 2 and Vue 3. Note: you may sync your changes from Vue 2 to Vue 3 (or vice versa) using the ./scripts/dialtone-vue-sync.sh script.
[x] I have validated components with a screen reader.
[x] I have validated components keyboard navigation.

:camera: Screenshots / GIFs

:link: Sources
https://tiptap.dev/docs/editor/api/utilities/suggestion

Fixed the imports plus some other vue 3 specific fixes. Looks good now.


invalid memory address or nil pointer dereference

Hi. I'm trying to run telly on Ubuntu 16.04. I get an error that I dont know how to solve.
Can anyone help? :-)
username@UBUNTU-PLEX:~/go/src/telly$ ./telly -playlist=/home/username/go/src/telly/playlist.m3u
[telly] [info] booting telly v0.6
[telly] [info] Reading m3u file /home/username/go/src/telly/playlist.m3u...
[telly] [warning] telly is not attempting to strip out unneeded channels, please use the flag -filterregex if telly returns too many channels
[telly] [info] telly is currently not filtering for only uk television. if you would like it to, please use the flag -uktv
[telly] [info] found 15 channels
[telly] [info] creating discovery data
[telly] [info] creating lineup status
[telly] [info] creating device xml
[telly] [info] creating webserver routes
[telly] [info] Building lineup
[telly] [info] advertising telly service on network
[telly] [debug] Advertising telly as HDHomerun (telly) (12345678-AE2A-4E54-BBC9-33AF7D5D6A92)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x661275]

goroutine 1 [running]:
main.main()
	/home/username/go/src/telly/main.go:384 +0x1755

Did you compile from source? Or what release did you use?

I did this.. But I am not sure that is correct. :)
cd $GOPATH
git clone https://github.com/tombowditch/telly.git
cd telly
go build
./telly -playlist="/MYFOLDER/playlist.m3u"

To be sure it isn't vendor specific, can you first run go get -u all  before compiling & running?

Found the root cause of this, working on a fix


Add example app: jokes

I've put together a port of the jokes app. It's basically all there except the the optimistic UI when creating a new joke. I'm opening this PR as a draft cause I think there are a few issue that are worth figuring out before telling everyone "this is how you do it".
Type safety
You've already done some thinking about this with regards to data loading and KCD opened an issue on the Typescript repo to address some related issues. It's hard to unravel them all to separate talking points but I'll do my best!
Enforcing correct types on route module exports - Route modules have to export the correct functions of the correct types. I feel like this may just be an unavoidable issue when it comes to convention based frameworks and is the same problem that KCD opened the issue for. Rescript has *.resi files but how do you ensure that they're using the correct types?
There's an option to automatically generate the *.resi files using the js-post-build hook. That has its own issues though and feels a little heavy handed.
Enforcing correct types on loader/action return types - This is the issue you were playing with. The problem is that Remix's return type on loader/action functions is (basically) Data | Promise<Data> | Response | Promise<Response>. It would be pretty easy to declare a standard function signature that returned Promise<Data> but it turns out that the Response versions are used constantly. Within the jokes app, they're used often for redirects after form submissions and augmenting standard data responses with additional headers (Vary, for example). The reliance on web standards is a bit of a curse here as Response is clearly not typed.
Furthermore, these data types are actually used constantly in remix. For example, the meta function gives the user access to the loaderData to customise the headers. useMatches gives the user access to not only the current route's data but all parent routes as well. This is generally typed as any in the Typescript bindings, I assume due to the complexity.
I think there's a few options here:

Allow the response to be wrapped in Data() or Response() variant constructors. It makes it easier for the user to return the correct data type but doesn't force it though.
Have a loader/action signature that only allows Promise.t<Response> and provide multiple json response bindings of type data => Response. One for the loader and one for actions. Again, this doesn't force the user to do the right thing but makes it easier.
Have signatures for loader/action that only allow return types of Promise.t<Response> and create a single json binding of type Js.Json.t => Response.Basically, embrace the fact that we don't know what the actual data type is and encourage users to use something like decco to enforce types at runtime. This would mean that useLoader would return Js.Json.t and would require decoding at runtime. I actually think this may be the best option given the complexity and how many places attempt to read this data.

Server modules on the client
This is a bit of a limitation of Rescript again, similar to the convention-based routing issues we encountered previously. Basically, route modules are a single file containing isomorphic code, as well as code that will only ever run on the server. During development, I think Remix serves up the route modules as-is, meaning that DB dependencies will get bundled for the client. This is a problem when these modules rely on native code that can't get bundled (I ran into issues with bcrypt during the port, opting to use bcryptjs in its place). I'm pretty sure this isn't an issue during production builds as tree-shaking should remove methods like loader that would have interacted with the DB.
I'm pretty sure this is why Remix's naming convention of db.server.js exists. I think this ensures that the db module won't get bundled for the client under any circumstances. Unfortunately, using . in a Rescript module name makes it exotic and impossible to import from another module, making db.server.res kind of useless.
I don't think we have any other recourse here except for a change to Remix itself to allow an alternate naming strategy for client/server modules. I haven't looked at whether this is possible, let alone welcome, but it's definitely an issue.

I'm keen to hear your thoughts on this!

I've been playing with another branch (branched from this PR branch) where I've:

Simplified the loader/action functions to return Promise.t<Webapi.Fetch.Response.t>
Changed the binding of json to Js.Json.t => Webapi.Fetch.Response.t
Introduced decco for generating encode/decode functions for loader/action types
Use patch-package to allow a custom regex for detecting server modules

The ergonomics around using Js.Json.t actually feels much nicer and seems to align with Remix's goal of "use the platform". It's almost like replacing Remix's use of any with something more analogous to unknown that requires runtime checks. It also doesn't require making any custom Remix-focused bindings for the Webapi module that try and enforce type safety (such as a Remix.Response.t<'appData>). Obviously this is all at the cost of some compile-time type safety (you're not forcing that loader returns the same type that's read by useLoaderData) but the run-time safety should make sure your code will either run with good data or throw with bad data (instead of running with bad data).

@drewschrauf amazing, really appreciate your help here! Sorry I haven't got round to these yet, caught up in a bunch of things atm 😅
Will try to take a look this week 🙇

No worries! I've been tinkering a little less since the cricket season ended anyway 😂


python312Packages.qdrant-client: 1.8.0 -> 1.8.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.qdrant-client is: Python client for Qdrant vector search engine
meta.homepage for python312Packages.qdrant-client is: https://github.com/qdrant/qdrant-client
meta.changelog for python312Packages.qdrant-client is: https://github.com/qdrant/qdrant-client/releases/tag/v1.8.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.8.2 with grep in /nix/store/gib3mprhziz7bvdn5g982faqfkx5qq87-python3.12-qdrant-client-1.8.2
found 1.8.2 in filename of file in /nix/store/gib3mprhziz7bvdn5g982faqfkx5qq87-python3.12-qdrant-client-1.8.2

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
chatgpt-retrieval-plugin
python311Packages.llama-index-vector-stores-qdrant
python311Packages.qdrant-client
python312Packages.llama-index-vector-stores-qdrant
python312Packages.qdrant-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gib3mprhziz7bvdn5g982faqfkx5qq87-python3.12-qdrant-client-1.8.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/22d216036774e46ec7d6b582c9b11248f1be7859#python312Packages.qdrant-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gib3mprhziz7bvdn5g982faqfkx5qq87-python3.12-qdrant-client-1.8.2
ls -la /nix/store/gib3mprhziz7bvdn5g982faqfkx5qq87-python3.12-qdrant-client-1.8.2/bin

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

Maintainer pings
cc @happysalada for testing.

Result of nixpkgs-review pr 301644 run on x86_64-linux 1

2 packages marked as broken and skipped:

chatgpt-retrieval-plugin
chatgpt-retrieval-plugin.dist

8 packages built:

python311Packages.llama-index-vector-stores-qdrant
python311Packages.llama-index-vector-stores-qdrant.dist
python311Packages.qdrant-client
python311Packages.qdrant-client.dist
python312Packages.llama-index-vector-stores-qdrant
python312Packages.llama-index-vector-stores-qdrant.dist
python312Packages.qdrant-client
python312Packages.qdrant-client.dist


Make isVisibleFromModule accept TagDecl definitions that were demoted to declarations.

Clang AST requires to have only a single definition in a redeclaration
chain, that's why it demotes duplicate definitions from other modules to
declarations. But on the Swift side it is important to know a module
contains a full definition and not just a forward declaration, even if
it was demoted to a declaration.

Please test with following PR:
https://github.com/apple/llvm-project/pull/3872
@swift-ci Please test

I'm not sure what kind of extra testing is required as this change is supposed to preserve the existing behavior. Any feedback about that is welcome.
For now I'm testing with clang change against stable/20211026 The plan is to check that everything works as intended and then to review at https://reviews.llvm.org, land upstream, let it merge to "next", and then cherry-pick to stable/20211026. Also I plan to test this change together with the proposed flag in clang and with "Reland "[modules] Fix miscompilation when using two RecordDecl definitions with the same name."" to make sure this change is sufficient for safe relanding.

Could the test modified in https://github.com/apple/swift/pull/40091 be updated to test this?

Yep, I can totally revert the change in #40091. Just to clarify my understanding, in what cases the test should have failed? Because all PR tests succeed but I'm not sure which ones run "ClangImporter/overlay.swift".

Yep, I can totally revert the change in #40091. Just to clarify my understanding, in what cases the test should have failed? Because all PR tests succeed but I'm not sure which ones run "ClangImporter/overlay.swift".

The test uses // expected-error *, so it will accept zero or more of the specified error message. So it kind of just eats the failure. If we get rid of that line, does the test still pass?

The test uses // expected-error *, so it will accept zero or more of the specified error message. So it kind of just eats the failure. If we get rid of that line, does the test still pass?

Thanks for the explanation! Totally missed that *. Pushed the revert to PR branch, will rerun the tests.

Please test with following PR:
https://github.com/apple/llvm-project/pull/3872
@swift-ci Please test

isThisDeclarationADemotedDefinition has been added in clang, let me rerun the tests just with commits in this PR, no cross-repo testing.

@swift-ci Please test


Allow global settings on Grape::Entity (0.4.x)

This fixes a regression introduced after merging a #134.
It's something undocumented before but it worked before and I don't see
anything harmful in the presence of this feature.
Fixes #166.

Merging.
Btw, I think the convention for doing patch releases for a branch name is 0.4.x, NBD.


Some Suggestions

Hi, here are some feature suggestions

Add file and folder selection Option: select multiple files or folders to copy/cut/delete/
The language is kind of mixed up. English + Chinese (?) on many pages. Please add an option in the setting page to select a language and use that for every word in each page
Add an option to drag and drop between tabs
Add an option to remove the default pinned folders to the home screen ( Documents, Music,...)
Typo (Setting->Personalize)
The back button does not work in the setting page (disabled)
Removing the (+) Button in the QuickView Causes the app to crash

Thanks for your great app and sorry to bring up the issues and suggestions here, I could not submit my feedback within the app (Network Error)

@Mahan3340

You can use keyboard shortcuts to select multiple files/folders

Because RX is developed and maintained by individuals, there may be some problems in multilingual translation. If you find any incomplete translation, please submit it to me here, thank you

Currently, dragging between tabs is not supported yet, I will try to achieve

I will change the mechanism to allow remove the default pinned folders

Thank you for correcting the translation (Personalise->Personalize)

The settings page is a pop-up control, so it does not need to use the back button, this is not a BUG

What does this mean ?

Removing the (+) Button in the QuickView Causes the app to crash

@zhuxb711 Thank for your response. I've attached a screenshot for the plus button I mentioned earlier. By the way, I'm using a surface with a touch screen with no keyboard and the issues are when working with a touch screen. I would appreciate it if your team could test the app with a touch screen and make it a little bit more touch-friendly.

@Mahan3340
Sorry for the inconvenience.

Long-Press a file to open a menu, then try to select open-with, Edit or share with a touch screen, works well with mouse or pen but not finger

This situation is Microsoft's fault😂😂😂😂😂.
See this: How to use menuflyout in CommandBarFlyout with touch screen
Also, I don’t know how you removed the “+” button, because from a code perspective you should not be able to right-click and remove it. How did you do it?

@zhuxb711 So we have to wait for MX to fix it 😁 I guess top/bottom menus for copy/cut/selection/delete,.. shortcuts would be a good alternative, just like the win phone old apps or some other UWP apps, with the 3-dot menu.
The plus button could be deleted by a long-press menu using touch.

@Mahan3340
I have investigated the problems when using the touch screen.
The cause of this problem is that mouse events and touch events are triggered in different ways
So, I will fix the issue that may cause the right-click menu to pop up incorrectly when using the touch screen in the next version.

Close #1
Most of this recommendation has been implemented in Release-4.6.8
v4.6.8 has been released to Microsoft Store


Mod still not working as of 1.1.1; rollback to 1.0.0 still functions

as detailed in the previous issue, the customize button has disappeared and no effects of the mod are visible, even after updating from 1.1.0 to 1.1.1
the mod appears to have loaded and is visible in tacklebox with no errors given.

actually fixed in v1.1.2 my bad

it does seem to be fixed! it's an excellent mod and your work is really appreciated.


Use Crowdin to manage translations

It would be better and faster if we use crowdin to handle localization, so when you guys add a new key you don’t need to update each language JSON

We just do '''npm run i18'''
This generates the type safe translation keys along with any new keys in each translation JSON.

@HysMX Why Crowdin instead of Weblate? For any of the reasons I can think of, I draw a blank there.


feat: add data transform log

fixed https://github.com/antvis/G2/issues/5415

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 6 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 89.422%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/data/log.ts
2
5
40.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
9650

Relevant Lines:
10452

💛  - Coveralls


Correct line endings and file permissions

A few minor changes to a couple of files for consistency. git warns about the CRLF line endings:
$ git diff
warning: CRLF will be replaced by LF in Carthage/Checkouts/FeedKit/Tests/xml/Content.xml.
The file will have its original line endings in your working directory.

Hi, @Eitot. Merging this. Thank you for contributing 😄

Ok, so I closed this by mistake before merging, and for some odd reason, the reopen button is grayed out. I'm guessing maybe it's because the originating repository no longer exists 🤔 So so Sorry! I'll make sure to include theses changes in the next version, none the less.


docs(samples): updated NUMERIC samples

Added specific samples for NUMERIC instead of modifying the existing datatypes samples.

Thanks so much for the review and feedback @olavloite and @JustinBeckwith.


feat: add Resource Kind in output

It was very hard to tell the resource type of error object.
I made me hard to deep dive to diagnostic with additional kubectl or other operation .
for example :
Below errors ,I have to guess they are pods:

But for below , just guess ? a pod again ? No, it's a deployment or statefulset :-)

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

I use Hi-Yellow , correct me if better color suits.

@AlexsJones  what do you think about this idea?

@AlexsJones what do you think about this idea?

I support it


Fix invalid context cast in ReactRootView

Summary
Hi 👋
I'm one of the  Expo contributors. When upgrading the Stripe dependency in Expo for SDK48 release on Android, we noticed the following error:
java.lang.ClassCastException: android.view.ContextThemeWrapper cannot be cast to android.app.Activity
With @Kudo we narrowed it down to an underlying issue in the following cast in ReactRootView done during checking for keyboard events:
((Activity) getContext())
The getContext() is actually a ContextThemeWrapper for ExperienceActivity, so we should not cast it to an Activity directly - instead, we unwrap it using getBaseContext().
Implementing the following fix into the Expo fork fixed the crash for us:
https://github.com/expo/react-native/commit/0e2c9cada120a3709e8285ab4bcdaa1c5c446732

Changelog
[ANDROID] [FIXED] - Fixed crash occurring in certain native views when handling keyboard events.

Test Plan

Tested manually by comparing two builds before and after this change. The main branch build crashes when the Stripe 0.23.1 Card Element from the example app is mounted on screen. Applying the change fixed the issue.
Happy to make a more isolated reproduction if necessary.

Full stack trace:
         AndroidRuntime  D  Shutting down VM
                         E  FATAL EXCEPTION: main
                         E  Process: host.exp.exponent, PID: 8849
                         E  java.lang.ClassCastException: android.view.ContextThemeWrapper cannot be cast to android.app.Activity
                         E      at com.facebook.react.ReactRootView$CustomGlobalLayoutListener.checkForKeyboardEvents(ReactRootView.java:937)
                         E      at com.facebook.react.ReactRootView$CustomGlobalLayoutListener.onGlobalLayout(ReactRootView.java:913)
                         E      at android.view.ViewTreeObserver.dispatchOnGlobalLayout(ViewTreeObserver.java:1061)
                         E      at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3352)
                         E      at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2286)
                         E      at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8948)
                         E      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231)
                         E      at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239)
                         E      at android.view.Choreographer.doCallbacks(Choreographer.java:899)
                         E      at android.view.Choreographer.doFrame(Choreographer.java:832)
                         E      at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214)
                         E      at android.os.Handler.handleCallback(Handler.java:942)
                         E      at android.os.Handler.dispatchMessage(Handler.java:99)
                         E      at android.os.Looper.loopOnce(Looper.java:201)
                         E      at android.os.Looper.loop(Looper.java:288)
                         E      at android.app.ActivityThread.main(ActivityThread.java:7898)
                         E      at java.lang.reflect.Method.invoke(Native Method)
                         E      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
                         E      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Should I care about the failing macos builds?
Seems like an unrelated issue.

how to apply this patch to currnet app?

how can we use this in our app, patch-package not working ?

@cortinico facing the same issue on 0.71.3, can you please suggest how to get this fixed.

I'm encountering the same issue when using version 0.71.8.
Would it be possible to incorporate this fix also in 0.71? Thanks 🙇 !

This change is included only in 0.72. If you folks want this backported, you need to ask for such in the release workign group in the dedicated discussion:
https://github.com/reactwg/react-native-releases/

Great, thanks Nicola for sharing the info 🙇. I’ll definitely take a look at the release working group.


Release v2.2.3

@c-rack Do you agree that we should mark v2.2.2 as invalid on hex?
(There were also questions about the issue on the elixir Slack etc.)

@maennchen sure


Update CONTRIBUTING.md

@optimizely/fullstack-devs

Coverage remained the same at 100.0% when pulling ca4ea0d8657edcc8f738e73ff88e6c6cda3a170c on elliot/contributing into eb2d81e1f20b0d39dc90c39220fe66ee3c943b1c on master.


[BUG] test_floor_scale_zero fails with DATAGEN_SEED=1700009407

FAILED^[[0m ../../../../integration_tests/src/main/python/arithmetic_ops_test.py::test_floor_scale_zero[Double][DATAGEN_SEED=1700009407, INJECT_OOM]

Repro:
SPARK_RAPIDS_TEST_DATAGEN_SEED=1700009407 ./run_pyspark_from_build.sh -k test_floor_scale_zero

654798 [2023-11-15T02:31:18.513Z] ----------------------------- Captured stdout call -----------------------------
654799 [2023-11-15T02:31:18.513Z] ### CPU RUN ###
654800 [2023-11-15T02:31:18.513Z] ### GPU RUN ###
654801 [2023-11-15T02:31:18.513Z] ### COLLECT: GPU TOOK 0.10657858848571777 CPU TOOK 0.14875459671020508 ###
654802 [2023-11-15T02:31:18.513Z] --- CPU OUTPUT
654803 [2023-11-15T02:31:18.513Z] +++ GPU OUTPUT
654804 [2023-11-15T02:31:18.513Z] @@ -1944,7 +1944,7 @@
654805 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=Decimal('0'))
654806 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=None)
654807 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=Decimal('0'))
654808 [2023-11-15T02:31:18.513Z] -Row(floor(a, 0)=Decimal('-940459146980391'))
654809 [2023-11-15T02:31:18.513Z] +Row(floor(a, 0)=Decimal('-940459146980392'))
654810 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=None)
654811 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=None)
654812 [2023-11-15T02:31:18.513Z]  Row(floor(a, 0)=None)

The difference is tied to the output types and operations involved.  floor(a) produces a long, whereas floor(a, 0) produces a decimal(16,0).  The latter is computed first by casting a as a decimal(30,15) and then computing floor at scale=0 on that.  What's interesting is that we start to diverge from Spark CPU on the cast to decimal(30,15):
scala> spark.conf.set("spark.rapids.sql.enabled", "false")

scala> Seq(-9.40459146980391E14).toDF("a").repartition(1).createOrReplaceTempView("df")

scala> sql("select a, cast(a as decimal(30,15)) as c, floor(a) as f, floor(a, 0) as fa from df").collect
res22: Array[org.apache.spark.sql.Row] = Array([-9.40459146980391E14,-940459146980391.000000000000000,-940459146980391,-940459146980391])

scala> sql("select a, cast(a as decimal(30,15)) as c, floor(a) as f, floor(a, 0) as fa from df").printSchema
root
 |-- a: double (nullable = false)
 |-- c: decimal(30,15) (nullable = true)
 |-- f: long (nullable = true)
 |-- fa: decimal(16,0) (nullable = true)

scala> spark.conf.set("spark.rapids.sql.enabled", "true")

scala> Seq(-9.40459146980391E14).toDF("a").repartition(1).createOrReplaceTempView("df")

scala> sql("select a, cast(a as decimal(30,15)) as c, floor(a) as f, floor(a, 0) as fa from df").collect
23/11/28 11:07:33 WARN GpuOverrides:
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
      @Expression <AttributeReference> a#102 could run on GPU

23/11/28 11:07:33 WARN GpuOverrides:
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
      @Expression <AttributeReference> a#102 could run on GPU

23/11/28 11:07:33 WARN GpuOverrides:
  !Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
    @Partitioning <SinglePartition$> could run on GPU
    ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
      @Expression <AttributeReference> a#102 could run on GPU

23/11/28 11:07:33 WARN GpuOverrides:
!Exec <ShuffleExchangeExec> cannot run on GPU because Columnar exchange without columnar children is inefficient
  @Partitioning <SinglePartition$> could run on GPU
  ! <LocalTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.execution.LocalTableScanExec
    @Expression <AttributeReference> a#102 could run on GPU

res26: Array[org.apache.spark.sql.Row] = Array([-9.40459146980391E14,-940459146980391.021204383727616,-940459146980391,-940459146980392])

So this ends up being solely about the known imprecision when casting floating point values to decimals.  The test has to explicitly set spark.rapids.sql.castFloatToDecimal.enabled=true to keep everything on the GPU, and that leads to the difference of -940459146980391.021204383727616 vs. -940459146980391.000000000000000 when casting the double to a decimal(30,15).  Performing a floor on those values results in a difference, because floor moves to the next integral value towards negative infinity.
If the GPU matched the CPU when casting floating point to decimals, the test would pass as written.


Avoid circular dependencies without changing struct definition (for generated proto types)?

We have a self-referential Failure type defined here. The actual struct is more complicated, but it looks like the one in the below script:
package main

import (
	"github.com/brianvoe/gofakeit/v6"
)

// Failure is a generated struct from a proto definition.
type Failure struct {
	Cause *Failure // Can't add fakeit ignore tag here because this is a generated field.
}

func main() {
	var obj Failure
	_ = gofakeit.Struct(&obj) // stack overflow
}

This will cause a stack overflow due to the circular dependency. However, I can't easily ignore the field because I can't edit the struct definitions since they are generated. There may be some ways, but I'd rather avoid it if possible since it will likely add a new step to our proto generation process.
Is there a way I can state during the invocation of gofakeit.Struct that this specific field should be ignored so that I don't need to modify the struct definition itself?
Thank you!

Nope. Looks like you should probably rethink the need for a circular struct.


Index on NpgsqlRange

Would it be possible to make it so that you can easily define indexes on NpgsqlRange values (or does it already exist?)?
In §8.17.9 of the Postgres documentation regarding indexes for range types we can see this example:
CREATE INDEX reservation_idx ON reservation USING gist (during);

which says:

A GiST or SP-GiST index can accelerate queries involving these range operators: =, &&, <@, @>, <<, >>, -|-, &<, and &>

@Jefffrey That should be possible. Take a look at the docs for more information:

The Npgsql EF Core provider allows you to specify the index method to be used by specifying ForNpgsqlHasMethod() on your index in your context's OnModelCreating:
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
   modelBuilder.Entity<Blog>()
               .HasIndex(b => b.Url)
               .ForNpgsqlHasMethod("gin");
}

I'm going to close this issue, but feel free to post back if you have additional questions.

Yes, thanks. Missed this page of the documentation. Sorry.


Update extensionsGallery.json

Updated version info for Extension/Simple-Data-Scripter

Updated version info for Extension/Simple-Data-Scripter from 01.3 -> 0.1.5

That's new. But no problem. all done.

@ecirpnaes Updated the galleries - you should see the new version in insiders and stable now!


Suggestions on what to improve

The latest library release adds support for nested component and passing properties to them. A lot of functionality still has to be tested by expanding the tests.
Feel free to try out the compiler with everything you can throw at it so we can see what still has to be fixed!

Does css work now?

Yes, I think it works. It generates an app.css file that you link in your index.html and it dumps all the CSS between the style tags appended with a random string into it.

Gonna try and find what I can add or improve this weekend.


Template pytorch docker file

Issue #, if available: N/A
Description of changes: provide a template Dockerfile to create a PyTorch docker image. The Dockerfile contains optional stanzas, and expect users to read through it, understand what each stanza does, then create their own Dockerfile. This is amalgamation of a wide range of images, notably those targeted for p4, p5, and latest Parallel Cluster.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@verdimrc, we'll need to talk more about this one with the team as it's changing the naming convention. Should we move the AMI directory name to AMI + containers?

For sure, let's talk about it. For now, I move the Dockerfile to sit together with the AMI templates.

Recommended changes:
2.AMI_and_containers
|- 1.AmazonMachineImage
|- 2.DockerContainer

looks good. I'll reorganize that subdir.

@perifaws : push latest commits. PR ready for re-review.

re-org to dir. structure stated in https://github.com/aws-samples/awsome-distributed-training/pull/37#issuecomment-1810425239
add readme
bugfixes

Please address conflicts.


[suggestion] make a mod like this but instead of fabric on forge, it's forge on fabric (1.20.1)

i wanted to play gun mods on fabric, but because of 90% of the gun mods being on forge, i need a connector and patchwork are outdated for a long long time

However, due fabric being a lightweight mod loader and forge being a heavyweight mod loader. It will be much more difficult to get Forge on Fabric.

ok


Error: $compile:multidir Multiple Directive Resource Contention

This is my issue
https://docs.angularjs.org/error/$compile/multidir?p0=ionDatetimePicker&p1= (module:

Hi,
seems like your whole error link is not copied and I really can't tell what's going on. Please post whole error URL with error message as well.


rewrite code around trust proxy

rewrite code around proxy

Zipline v1 is no longer supported, please switch to the next branch.


antiegotistical, grindstones

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,g]

/trunk merge


[PPP-5046] - Code changes of Vulnerable Component: Avro.

:x: Build failed in 1m 31s
Build command:
mvn clean verify -B -e -Daudit -Djs.no.sandbox -pl \
plugins/avro-format/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message


Connectors - Async event logger

Need an async event logger to report low level error details in case of connector errors, including HTTP request/response parameters

Related to #303


refactor: upgrade logr/zerologr to stable release v1.0.0

Description
logr.Logger is changed from interface (v0.4.0) to struct (v1.0.0). Update zerologr to logr.LogSink.

@tarrencev @OrlandoCo Would you please review this PR? It doesn't change any public interface of zerologr, but logr.Logger is changed from interface to struct in the stable release, so nil check is replaced.

@hn8 Thanks.

@adwpc Do you know how can I proceed for this commit? Can't believe logger change would change test coverage so much since this package is not about logging? Lol

@adwpc Do you know how can I proceed for this commit? Can't believe logger change would change test coverage so much since this package is not about logging? Lol

seems not your fault
i met this on ion too


VS Code for ubuntu suddenly won't open

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.2
OS Version: Ubuntu 22.04

Steps to Reproduce:

Run  code --disable-gpu --disable-extensions --verbose
I've tried:

logging in as a differnt user

Re-installing vs code

Running with the GPU disabled

Running with extensions disabled

[18153:0918/064430.797424:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2023-09-18T10:44:30.910Z] [File Watcher (node.js)] Request to start watching: /home/robert/.config/Code/User (excludes: <none>, includes: <all>),/home/robert/.config/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2023-09-18T10:44:30.928Z] Starting VS Code
[main 2023-09-18T10:44:30.928Z] from: /usr/share/code/resources/app
[main 2023-09-18T10:44:30.928Z] args: {
  _: [],
  diff: false,
  merge: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  'pre-release': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': true,
  'disable-gpu': true,
  'disable-chromium-sandbox': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: false,
  'enable-smoke-test-driver': false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  'disable-gpu-sandbox': false,
  '__enable-file-policy': false,
  'enable-coi': false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  'disable-dev-shm-usage': false,
  'profile-temp': false,
  logsPath: '/home/robert/.config/Code/logs/20230918T064430'
}
[main 2023-09-18T10:44:30.931Z] Resolving machine identifier...
[main 2023-09-18T10:44:30.931Z] Resolved machine identifier: 110c81339ccdbded51be27f746ba74be7f4f0394efd32ea93cd63ed7a3593a1a
[main 2023-09-18T10:44:30.931Z] Main->SharedProcess#connect
[main 2023-09-18T10:44:30.937Z] [File Watcher (node.js)] Started watching: '/home/robert/.config/Code/User'
[main 2023-09-18T10:44:30.938Z] [File Watcher (node.js)] Started watching: '/home/robert/.config/Code/User/settings.json'
[main 2023-09-18T10:44:30.939Z] StorageMainService: creating application storage
[main 2023-09-18T10:44:30.943Z] ElectronURLListener: waiting for window to be ready to handle URLs...
[main 2023-09-18T10:44:30.943Z] lifecycle (main): phase changed (value: 2)
[main 2023-09-18T10:44:30.943Z] windowsManager#open
[main 2023-09-18T10:44:30.946Z] windowsManager#open pathsToOpen [
  {
    workspace: { id: '59fd4c9fb9d89419ece478111eb2125d', configPath: [c] },
    type: 1,
    exists: true,
    remoteAuthority: undefined,
    transient: undefined
  }
]
[main 2023-09-18T10:44:30.947Z] windowsManager#doOpenFolderOrWorkspace {
  folderOrWorkspace: {
    workspace: { id: '59fd4c9fb9d89419ece478111eb2125d', configPath: [c] },
    type: 1,
    exists: true,
    remoteAuthority: undefined,
    transient: undefined
  },
  filesToOpen: undefined
}
[main 2023-09-18T10:44:30.947Z] IPC Object URL: Registered new channel vscode:e4b24423-81bd-4e33-9b09-ebdd43648073.
[main 2023-09-18T10:44:30.948Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 158, y: 167, width: 1048, height: 735 }
[main 2023-09-18T10:44:30.948Z] window#validateWindowState: 1 monitor working area { x: 0, y: 27, width: 1536, height: 877 }
[main 2023-09-18T10:44:30.948Z] window#ctor: using window state { mode: 1, x: 158, y: 167, width: 1048, height: 735 }
[main 2023-09-18T10:44:30.996Z] window#load: attempt to load window (id: 1)
[main 2023-09-18T10:44:31.003Z] StorageMainService: creating workspace storage (59fd4c9fb9d89419ece478111eb2125d)
[main 2023-09-18T10:44:31.004Z] windowsManager#open used window count 1 (workspacesToOpen: 2, foldersToOpen: 0, emptyToRestore: 0, emptyToOpen: 0)
[main 2023-09-18T10:44:31.004Z] lifecycle (main): phase changed (value: 3)
[main 2023-09-18T10:44:31.005Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2023-09-18T10:44:31.005Z] update#setState idle
[main 2023-09-18T10:44:31.087Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2023-09-18T10:44:33.509Z] lifecycle (main): phase changed (value: 4)
[main 2023-09-18T10:44:46.190Z] CodeWindow: detected unresponsive
[main 2023-09-18T10:44:48.424Z] IPC Object URL: Removed channel vscode:e4b24423-81bd-4e33-9b09-ebdd43648073.
[main 2023-09-18T10:44:48.425Z] Lifecycle#window.on('closed') - window ID 1
[main 2023-09-18T10:44:48.425Z] Lifecycle#onWillShutdown.fire()
[main 2023-09-18T10:44:48.426Z] Lifecycle#onWillShutdown - begin 'instanceLockfile'
[main 2023-09-18T10:44:48.426Z] storageMainService#onWillShutdown()
[main 2023-09-18T10:44:48.426Z] Lifecycle#onWillShutdown - begin 'applicationStorage'
[main 2023-09-18T10:44:48.427Z] Lifecycle#onWillShutdown - begin 'workspaceStorage'
[main 2023-09-18T10:44:48.427Z] Lifecycle#onWillShutdown - begin 'extHostStarter'
[main 2023-09-18T10:44:48.427Z] Lifecycle#app.on(window-all-closed)
[main 2023-09-18T10:44:48.427Z] Lifecycle#app.on(before-quit)
[main 2023-09-18T10:44:48.427Z] Lifecycle#onBeforeShutdown.fire()
[main 2023-09-18T10:44:48.427Z] [WindowsStateHandler] onBeforeShutdown {
  lastActiveWindow: {
    workspaceIdentifier: {
      id: '59fd4c9fb9d89419ece478111eb2125d',
      configURIPath: 'file:///home/robert/.config/Code/Workspaces/1680043647063/workspace.json'
    },
    folder: undefined,
    backupPath: '/home/robert/.config/Code/Backups/59fd4c9fb9d89419ece478111eb2125d',
    remoteAuthority: undefined,
    uiState: [Object: null prototype] {
      mode: 1,
      x: 157,
      y: 167,
      width: 1050,
      height: 737
    }
  },
  lastPluginDevelopmentHostWindow: undefined,
  openedWindows: []
}
[main 2023-09-18T10:44:48.428Z] Lifecycle#app.on(will-quit) - begin
[main 2023-09-18T10:44:48.428Z] Lifecycle#onWillShutdown - end 'extHostStarter'

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Adding --disable-software-rasterizer gets it to launch

The issue remains on 1.82.2

Can you provide the output of code --verbose, the logs with --disable-gpu show a normal application lifecycle I don't see any error from the runtime.

Found the workaround, had to clear the GPU Cache of VSCode by deleting ~/.config/Code/GPUCache

Found the workaround, had to clear the GPU Cache of VSCode by deleting ~/.config/Code/GPUCache

Interesting. Mine is now opening (despite me having done nothing) so next time the issue comes up I'll try this and let you know if it works...

Found the workaround, had to clear the GPU Cache of VSCode by deleting ~/.config/Code/GPUCache

just ran into this myself on 1.83.1 - this solved it

Hey @deepak1556, this issue might need further attention.
@robertmain, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Training time

Thanks for releasing the code. How long does your method need to train?

Hi, thank you !! Training CLOUDS takes around 6h30 on 2 GPUs Nvidia A100 with a batch size of 8.


IndexError: list index out of range [Only when running with ros2]

@wangg12 @shanice-l @Rainbowend @tzsombor95  need your help.
The inference script runs successfully without any errors when executed as a standalone Python script.  By when running with ros2, ie., calling script inside ros2 node, the following error occurs. This error is happening at the pose refinement stage.
The error occurs at the line "used_program.draw("triangles", model.index_buffer)"  inside renderer.py.
I also tried changing app backends and gl backends, but same error
WARNING: OpenGL version could not be determined, which might be a sign that OpenGL is not loaded correctly.
2024-09-09 14:01:55,310 - WARNING - OpenGL version could not be determined, which might be a sign that OpenGL is not loaded correctly.
Traceback (most recent call last):
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_iris/lib/xrm_perception_iris/perception.server.v2.py", line 283, in
main()
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_iris/lib/xrm_perception_iris/perception.server.v2.py", line 273, in main
executor.spin()
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 294, in spin
self.spin_once()
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 794, in spin_once
self._spin_once_impl(timeout_sec)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 791, in _spin_once_impl
future.result()
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/task.py", line 94, in result
raise self.exception()
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/task.py", line 239, in call
self._handler.send(None)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 437, in handler
await call_coroutine(entity, arg)
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 391, in _execute_service
response = await await_or_execute(srv.callback, request, srv.srv_type.Response())
File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 107, in await_or_execute
return callback(*args)
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_iris/lib/xrm_perception_iris/perception.server.v2.py", line 239, in srv_task_callback
self.perception.inference_call(request)
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_iris/local/lib/python3.10/dist-packages/xrm_perception_iris/pipeline/pipeline_v2/init.py", line 85, in inference_call
self.pipeline.inference_call()
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_iris/local/lib/python3.10/dist-packages/xrm_perception_iris/pipeline/pipeline_v2/pipeline.py", line 139, in inference_call
self.gdrnpp1.inference(self.data.color.copy(), self.data.depth.copy(), target_obj )
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_modules/local/lib/python3.10/dist-packages/xrm_perception_modules/models/gdrnpp/get6dpose.py", line 64, in inference
poses = self.gdrn_predictor.postprocessing(data_dict, out_dict)
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_modules/local/lib/python3.10/dist-packages/xrm_perception_modules/models/gdrnpp/predictor_gdrn.py", line 216, in postprocessing
self.process_depth_refine(data_dict, out_dict)
File "/home/rack/Workspace/projects/xrm/install/xrm_perception_modules/local/lib/python3.10/dist-packages/xrm_perception_modules/models/gdrnpp/predictor_gdrn.py", line 281, in process_depth_refine
self.ren.draw_model(
File "/home/rack/Workspace/projects/3rdparty/gdrnpp_ws/gdrnpp/lib/render_vispy/renderer.py", line 407, in draw_model
used_program.draw("triangles", model.index_buffer)
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/program.py", line 543, in draw
canvas.context.flush_commands()
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/context.py", line 172, in flush_commands
self.glir.flush(self.shared.parser)
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 584, in flush
self._shared.flush(parser)
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 506, in flush
parser.parse(self._filter(self.clear(), parser))
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 824, in parse
self._parse(command)
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 798, in _parse
ob.attach(*args)
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 1803, in attach
self.deactivate()
File "/home/rack/.pyenv/versions/gdrnpp/lib/python3.10/site-packages/vispy/gloo/glir.py", line 1774, in deactivate
gl.glBindFramebuffer(gl.GL_FRAMEBUFFER, stack[-1])
IndexError: list index out of range
The following exception was never retrieved: cannot use Destroyable because destruction was requested
[ros2run]: Process exited with failure 1

@wangg12 @shanice-l @Rainbowend @tzsombor95  need your support