vega: generate_markdown: Don't raise exception for unsupported templa…

…tes.
So a code like:
with Live(dir='dvclive', report='md') as live:
    live.log_sklearn_plot("calibration", y_true, y_score)
    live.log_sklearn_plot("confusion_matrix", y_true, y_pred)
    live.log_sklearn_plot("det", y_true, y_score)
    live.log_sklearn_plot("precision_recall", y_true, y_score)
    live.log_sklearn_plot("roc", y_true, y_score)

Still generates a valid report for the supported plots instead of failing and not generating anything.

Codecov Report
Base: 96.01% // Head: 96.02% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (75b8f6e) compared to base (5360c45).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
+ Coverage   96.01%   96.02%   +0.01%
==========================================
  Files          19       19
  Lines         677      680       +3
  Branches      100      100
==========================================
+ Hits          650      653       +3
  Misses         22       22
  Partials        5        5

Impacted Files
Coverage Δ

src/dvc_render/vega.py
97.40% <100.00%> (+0.06%)
:arrow_up:

tests/test_vega.py
100.00% <100.00%> (ø)

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

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


4 DEADLINE_EXCEEDED: Deadline exceeded on update query

Hi,
We are trying to update some records in one table, while performing this action sometimes we get this error
4 DEADLINE_EXCEEDED: Deadline exceeded
    at Object.callErrorFromStatus (/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
    at Object.onReceiveStatus (/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
    at /node_modules/@grpc/grpc-js/build/src/call-stream.js:111:35
    at Object.onReceiveStatus (/node_modules/grpc-gcp/build/src/index.js:73:29)
    at InterceptingListenerImpl.onReceiveStatus (/node_modules/@grpc/grpc-js/build/src/call-stream.js:106:23)
    at Object.onReceiveStatus (/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
    at Object.onReceiveStatus (/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
    at /node_modules/@grpc/grpc-js/build/src/call-stream.js:182:78
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  code: 4,
  details: 'Deadline exceeded',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  note: 'Exception occurred in retry method that was not classified as transient'
}

We are using this function to perform the update operation
await this.database.runPartitionedUpdate({
                ...options,
                gaxOptions: this.retryAndTimeoutSettings,
});

Hi @aayush-sib. runPartitionedUpdate are usually used for large updates. Can you share what your query is and how many rows are approximately getting updated along with your timeout settings. It is possible that it's simply getting timed out as it is a large operation and increasing the value for timeout should resolve it

Hi @asthamohta
Thanks for the reply, we are just updating one row. Can you share the function which we can use instead of this?

Assuming that you are running a query, this sample should help: https://github.com/googleapis/nodejs-spanner/blob/main/samples/dml.js

We have tried with runUpdate function also, and the same intermittent issue was there with this function also.

Can you share your query and environments details which might help replicate the issue?

@aayush-sib just want to get back to you if this is still an open issue or something I can help with?

Closing this issue due to lack of activity, feel free to reopen this if you face the same issue


File frmSimplyVBUnitRunner.log is useless and should be removed

I'm submitting a "bug" report
Library Version: <IP_ADDRESS>

Current behavior:
File VBCorLib-3.0.0.zip\VBCorLib-3.0.0\Source\Tests\frmSimplyVBUnitRunner.log is useless and should be removed.

It will be removed. Thanks!


Clean up

🚀🚀🚀 Benchmark Results
Concurrency: 256
Requests/sec: 433699.99

Codecov Report

Merging #591 (a09ebe3) into release/next (0470146) will decrease coverage by 0.12%.
The diff coverage is 60.60%.

@@               Coverage Diff                @@
##           release/next     #591      +/-   ##
================================================
- Coverage         58.52%   58.39%   -0.13%
================================================
  Files                60       60
  Lines              1379     1418      +39
  Branches             51       58       +7
================================================
+ Hits                807      828      +21
- Misses              572      590      +18

Impacted Files
Coverage Δ

zio-http/src/main/scala/zhttp/core/Util.scala
100.00% <ø> (ø)

zio-http/src/main/scala/zhttp/http/Http.scala
57.52% <0.00%> (-10.19%)
:arrow_down:

zio-http/src/main/scala/zhttp/http/Patch.scala
83.33% <ø> (ø)

zio-http/src/main/scala/zhttp/service/Server.scala
51.11% <0.00%> (-1.17%)
:arrow_down:

zio-http/src/main/scala/zhttp/http/HttpData.scala
50.00% <14.28%> (ø)

zio-http/src/main/scala/zhttp/http/Request.scala
22.72% <20.00%> (-3.59%)
:arrow_down:

zio-http/src/main/scala/zhttp/http/Header.scala
90.00% <66.66%> (-1.90%)
:arrow_down:

...io-http/src/main/scala/zhttp/http/Middleware.scala
78.57% <66.66%> (ø)

...tp/src/main/scala/zhttp/http/HeaderExtension.scala
79.71% <78.00%> (+0.60%)
:arrow_up:

...io-http/src/main/scala/zhttp/http/PathModule.scala
78.78% <80.95%> (+2.92%)
:arrow_up:

... and 9 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 0470146...a09ebe3. Read the comment docs.

🚀🚀🚀 Benchmark Results
Concurrency: 256
Requests/sec: 432452.03


Toasts not displaying on card submission

Blocked by https://github.com/GuthrieW/shl-trading-cards/issues/63

Should actually be fixed now by another ticket.


Fix outcome printer object printing

Object used to be printed as {foo: bar}, not {. foo: bar} or {.. foo: bar}. After the object syntax change a while ago I think we didn't
update the outcome printer's printing.
Whitespace-less diff: https://github.com/facebook/reason/pull/1357/files?w=1

¯_(ツ)_/¯ merging


Register provider via policy For CosmosDBForPostgreSql.

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - cosmosdbforpostgresql - ci

API change check
API changes are not detected in this pull request.

/azp run java - cosmosdbforpostgresql - mgmt - tests


Translation not showing on initial app launch

Hi,
We recently updated our project to use vite instead of webpack and also modified also our vuejs files to make it compatible, everything is working well except for one thing. Yesterday I noticed that the requested translations did not load on the first load of the project when you refresh or visit the website.
For example when I put the url in my webbrowser and visit it, the translations will be in English but if I click on 1 menu item to go to another page, everything will change to the Dutch translations (which is correct).
Our app.js is as follows:
import './bootstrap';
import '../css/app.css';

// Import modules...
import { createApp, h } from 'vue';
import { createInertiaApp } from '@inertiajs/inertia-vue3'
import { InertiaProgress } from '@inertiajs/progress'
import { FontAwesomeIcon } from "@fortawesome/vue-fontawesome";
import { library } from "@fortawesome/fontawesome-svg-core";
import { faInfoCircle } from "@fortawesome/free-solid-svg-icons";
import { faEdit } from "@fortawesome/free-solid-svg-icons";
import { faEye } from "@fortawesome/free-solid-svg-icons";
import { faSun } from "@fortawesome/free-solid-svg-icons";
import { resolvePageComponent } from 'laravel-vite-plugin/inertia-helpers';
import { i18nVue } from 'laravel-vue-i18n';

library.add(faInfoCircle);
library.add(faEdit);
library.add(faEye);
library.add(faSun);

  createInertiaApp({
      resolve: (name) => resolvePageComponent(`./Pages/${name}.vue`, import.meta.glob('./Pages/**/*.vue')),
      setup({ el, app, props, plugin }) {
          return createApp({ render: () => h(app, props) })
              .use(plugin)
              .use(i18nVue, {
                  resolve: async lang => {
                      const langs = import.meta.glob('../../lang/*.json');
                      return await langs[`../../lang/${lang}.json`]();
                  }
              })
              .mixin({ methods: { route, hasAnyPermission: function (permissions) {
                      var allPermissions = this.$page.props.auth.can;
                      var hasPermission = false;

                      permissions.forEach(function(item){
                          if(allPermissions[item]) hasPermission = true;
                      });
                      return hasPermission;
                  } } })
              .mixin({ methods: { route } })
              .component("font-awesome-icon", FontAwesomeIcon)
              .mount(el);
      },
  });

and in our vuejs files we use {{ $t('translation') }} to load the translations for a specific text, what can be the reason that the translation only load when you navigate to another page?

Hey @iMaBo, everything looks good to me, can you check a couple things for me:

What is the "lang" attribute on your HTML tag.
What version you have installed from the package.json file.
If happens with only vite command or it still happens when you run the vite build.

Thanks.

Hey @xiCO2k

What is the "lang" attribute on your HTML tag.
In the app.blade.php file it is <html lang="{{ str_replace('_', '-', app()->getLocale()) }}"> this will result in <html lang="nl"> if visited in the browser.

What version you have installed from the package.json file.
"laravel-vue-i18n": "^2.1.3",

If happens with only vite command or it still happens when you run the vite build.
It happends with both commands, with vite and vite build both will give the same result.

Just updated the package to version v2.2.1 and deployed it, and it seems to be fixed now.
The translations do get loaded on the initial launch of the app.
Much appreciated for the quick fix 😄

No problem, anytime.

iam having the same problem, on v2.2.2, vue v3.2.31, cant find why

Can you try v2.3.0. and check if there is any issue on the console?
Thanks.

Still didnt seem to work, I can workaround this by adding :key to the root component, and then, in the onMounted lifecycle, i can inside a 50ms timeout update the key to force the entire app to re-render and then it will update the ui with the correct language, but its a hack, the ui always flashes the content because of this

Hey @diego-lipinski-de-castro just checked and looks like to avoid that (since the language is being read async) you may need to change your resolve method to the SSR example like this:
resolve: lang => {
    const langs = import.meta.globEager('../../lang/*.json');
    return langs[`../../lang/${lang}.json`].default;
}

Still doesnt seem to work unfortunately, is there an working example I could test of this working? or maybe another way of testing

made that switch on your repo, then I did run vite build and that was it.

edit: I found out why it didn't work while writing this and testing on the side and thought it might be interesting for others. and still uploaded it alongside what I found at the end.

made that switch on your repo, then I did run vite build and that was it.

I tried it on my project and it still doesn't work on the first page load.
I'm sorry I can't share the full repository as it is a project I'm working on as an intern but here are some insights which might be useful.
I'm working with the jetstream/inertia preset and the specific use case where I'm having this issue is when I'm loading graphs with chartjs.
here's the abstract class I made to get the translations
import { trans, isLoaded } from 'laravel-vue-i18n'

export abstract class Lang {
    public static keys: Readonly<object>
    public static fallbacks: Readonly<object>

    public static getLang(keyName: string | number) {
        return this.keys[keyName] ?? null
    }

    public static getFallback(keyName: string | number) {
        return this.fallbacks[keyName] ?? null
    }

    public static get translations() {
        // if (isLoaded()) {
            return Object.assign({},
                ...Object.entries(this.keys)
                    .map(([index, value]) =>
                        ({ [index]: trans(value) }))
            )
        // }

        // return this.fallbacks
    }

    public static translate(keyName: string | number): string | null {
        const key: string | undefined = this.keys[keyName]

        if (key === undefined) {
            return null
        }

        if (isLoaded()) {
            return trans(key)
        }

        return this.fallbacks[keyName] ?? keyName
    }
}

The LogLevel class which extends this
import { Lang } from "../Base/Lang";

export class LogLevelLang extends Lang {
    public static keys = Object.freeze({
        1: 'activity.emergency',
        2: 'activity.alert',
        3: 'activity.critical',
        4: 'activity.error',
        5: 'activity.warning',
        6: 'activity.notice',
        7: 'activity.info',
        8: 'activity.debug',
    })
    public static fallbacks = Object.freeze({
        1: 'Emergency',
        2: 'Alert',
        3: 'Critical',
        4: 'Error',
        5: 'Warning',
        6: 'Notice',
        7: 'Info',
        8: 'Debug',
    })
}

and what I'm doing inside the setup
<script  setup>
//...
const activitiesMeta = Meta.new()
    .doughnut()
    .setLabels(LogLevelLang.translations)
    .setColors(LogLevelColor.colors)
    .title({
        display: true,
        text: 'Activity levels'
    })
    .setTooltipPercentage()

const activitiesStats = computed(() => datasetGenerator(props.stats.activities, activitiesMeta))
//...
</script>

<template>
    ...
    <Doughnut :chart-data="activitiesStats" :chart-options="activitiesMeta.options" />
    ...
</template>

I tested some things while writing this and found out why my code didn't work as intended.
When using the trans function this way
const tmp = trans('my.translation.key')

the translation would occure before the translation got loaded and I was able to fix this by using
const tmp = computed(()=>trans('my.translation.key'))

In my specific case I had to turn activitiesMeta into a computed property and pass it to the activities computed property using .value
As I'm still quite new to vue I'm not quite sure of the impact on performances from using it this way but at least it works.
I think the documentation should warn about such details when using the function from within the setup

made that switch on your repo, then I did run vite build and that was it.

U might got confused, because if any state changes, the app rerenders and then renders the translations, but if you F5 you will see that the translations arent being loaded, that might be the case, im not sure, I made that change and ran vite build but got the same results, after logging in and F5

Same issue, translations aren't available in mounted hooks or outside of hooks, but we are using webpack, not vite.
Using version: 2.3.0.
app.js
.use(i18nVue, {
  resolve: (lang) => import(`../../lang/${lang}.json`),
})

some component where we need translations in mounted hook
onMounted(() => {
  console.log("error.generic"); // Output is error.generic
});

en.json
{ "error.generic": "This is generic error!" }

https://github.com/pristavu/inertia-vue3-i18n
Throttle the network via devtools

page loaded without ssr
https://user-images.githubusercontent.com/4123729/200774971-e8824352-94b7-46fd-a748-5770bff0c260.mp4

page loaded with ssr
https://user-images.githubusercontent.com/4123729/200775383-cbcca464-8523-4c60-ae6d-fba7f72d66f6.mp4

I am experiencing same issue while using it with Inertia js

Finally, figured it out. In my case, the issue is caused by the  component of "inertiajs/inertia-vue3"
As per Inertia JS docs:
**Link** component is a light wrapper around a standard anchor <a> link that intercepts click events and prevents full page reloads from occurring.
Hence, the page is not reloading the  tag and the "lang" attribute remains unchanged. However, it works on F5/refresh because it reloads the full page and the  tag gets refreshed as well.
The solution is to use normal anchor tag or any other language switching alternatives instead of the Link component.
@iMaBo @diego-lipinski-de-castro @Mondotosz @kskrlinnorth2 @pristavu Please try this out and see if it works.


Sharktopoda 2 integration

Related to #2. Sharktopoda 2 (MBARI's new video player) supports rendering and editing of localizations via a remote protocol. Gridview should be integrated with Sharktopoda 2 to facilitate this.

From VARS meeting 2/8/2023:
Requirements

Open video(s) for selected
Show localizations in Sharktopoda
Propagate edits & deletions back to gridview → VARS
Also delete the annotation (pending user approval)

Additional requirement:

Color boxes according to concept label (consistent with GridView colors)

Opening video does not seek to the correct frame on Mac. This is likely due to a failed connection because of the forced IPv6 UDP socket -- need to investigate more.

sharktopoda-client v0.4.3 introduces handling of IPv4 and IPv6 ephemeral sockets. Need to test if this resolves the issue above.

Hoping to have completed by 11/30/2023; Appears to be mostly complete but KRW will be testing this week to see if there are any outstanding issues.

From KRW:

I spent a little time this morning troubleshooting the shark-2 issue with Gridview and VARS Anno and figured out when it is not working correctly. If I open Gridview and choose open file on an image, it seeks to the correct elapsed time in video on shark-2. Then I open VARS Annotation, open a video file, close VARS annotation, and then go back to Gridview (has been open the whole time) and try to Open Video on an image, it opens the video in shark-2 from Gridview but seeks to the beginning of the video file, elapsed time 0, not to the correct elapsed time within video. So it seems like VARS annotation is changing something with shark-2 after it has been opened and then Gridview doesn't work correctly even after closing VARS annotation.

It sounds like the following is happening:

S2 is opened and not connected to any application
VARS Gridview is opened and connects to S2; S2 is now connected to VARS Gridview
VARS Gridview is able to send commands to S2, and S2 replies since it's connected to VARS Gridview; videos can be opened, seeked, and have localizations sent over
VARS Annotation is opened and connects to S2; S2 is now connected to VARS Annotation and drops the connection to VARS Gridview
VARS Annotation is able to send commands, and S2 sends replies to VARS Annotation since it's connected. VARS Gridview is able to send commands, but does not receive replies as VARS Annotation has broken its connection, and S2 only maintains a single connection; videos can be opened, but the "open done" reply is never returned, so VARS Gridview does not send a seek/add localization command.

So, it sounds like gridview needs the ability to re-connect without restarting the application, since VARS Annotation will interrupt the connection. In that vein, a nice-to-have could be an S2 connection status indicator (e.g. red X vs. green check).

From v0.4.0, there is now a "Video Player" tab with controls for Sharktopoda 2.

This can be used to specify the host/ports for Sharktopoda 2 and re-connect as needed when VARS Annotation grabs the connection.

From discussion 12/06/2023:
First cut: load all annotations from a given video, not just the selected one.
Next version: load annotations from within a time window of the selected annotation. Will require reaching out to VARS for other annotations

Appears to be completed @kevinsbarnard. Ok to close?


Remove Java and Javascript harnesses

Now that Wycheproof is community managed (more on that later!), I’d like to propose a significant change: removing the Java and Javascript testing harnesses, and focusing entirely on the JSON test vectors.
One big reason is that we don’t have the Bazel and Java expertise to properly maintain them, and it seems they are in need of maintenance (#83), somewhat undocumented (#84), and designed to run on Google infrastructure that’s not available to us (#86).
More generally, I think the Wycheproof consumption model that established itself in the past years is that of implementations consuming the JSON vectors with harnesses maintained upstream. I want to encourage that: upstream library authors are the best equipped to test their own code.
In particular, in COVID times zero PRs and four issues were about the harness code. Three of the issues are referenced above, and suggest failure to use that code. Only #93 suggests successful use of the harnesses.
The Java and Javascript code is not really just a harness, though: it also implements tests that can’t be represented well with vectors, like timing tests. Those would be lost.
Those harnesses also probably functioned as CI for the test vectors, but I’d rather we build proper GitHub Actions to check that the tests are well-formed, match the schema, and maybe also pass against at least one implementation, just to make sure the tests are not suddenly broken (but not to test the implementation itself).
All things considered, I think the tradeoff is worth it, and we should focus resources into producing, documenting, testing, and facilitating using the vectors instead. I'm looking for feedback on this direction before making the change.
/cc @NeilMadden @jbangert @Sajjon @jvoisin @ascarpino as those involved in issues related to the code to be removed
/cc @bleichenbacher-daniel @thaidn @chuckx as previous maintainers
/cc @C2SP/stewards

A collection of canonical JSON test vector sounds like a good vision for the project!
And if we will go with only one reference implementation - there are far more suitable languages than Java for it! E.g. Rust or possibly Swift - but Rust has far better cryptography ecosystem support.

And if we will go with only one reference implementation - there are far more suitable languages than Java for it! E.g. Rust or possibly Swift - but Rust has far better cryptography ecosystem support.

 Tests for the tests, essentially. Doesn't even have to be the same language for all vectors, as long as someone is there to maintain the tests.

On Saturday, March 23, 2024 at 06:47:04 PM GMT+1, Filippo Valsorda @.***> wrote:

And if we will go with only one reference implementation - there are far more suitable languages than Java for it! E.g. Rust or possibly Swift - but Rust has far better cryptography ecosystem support.

 Tests for the tests, essentially. Doesn't even have to be the same language for all vectors, as long as someone is there to maintain the tests.
One thing I'm currently doing is to keep a small database with test results. Running a test adds an entry to the data base. This allows to generate a list of algorithms with entries such as
"x25519.json": {
    "type": "Xdh",
    "alg": {
      "type": "Xdh",
      "primitive": "X25519"
    },
    "references": ["RFC 7748"],
    "test_status": {
      "pyca": {
        "test_version": "0.29",
        "date": "2024-03-16 13:13",
        "lib_version": "41.0.7",
        "passed": 236,
        "skipped": 0,
        "failed": 0
      }
    }
  },
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

One of the options to simplify the test environment is to run tests with test vectors through
java/com/google/security/wycheproof/testcases/JsonTest.java
This class takes a file with any test vectors as input and returns a structure with the test results. It is independent of JUnit and the dependencies that are essentially required are the provider to test and a JSON parser.  The class allows to generate test files with subsets of the test vectors, so that it is for example possible to rerun just the failing tests. There is also a bit of support for detecting false positives in this class. If no valid test vector in a file passes then it is likely that the test setup is wrong or uses incorrect assumptions and one should check this first before sending out automatic notifications to third parties.
The current setup is to use long lists of test cases  like
@Test
public void testSecp160k1Sha256() throws Exception {
testVerification("ecdsa_secp160k1_sha256_test.json", true);
}
@Test
public void testSecp160r1Sha256() throws Exception {
testVerification("ecdsa_secp160r1_sha256_test.json", true);
}
...
This setup is useful if one has tools to monitor the state of test cases over time, but as pointed out makes the tests less flexible and adds more dependencies.

I'm currently testing new test vectors against pyca and Rust. That gives about 70% of coverage. When testing against Rust I often struggle with seemingly non-uniform interfaces. Otherwise Rust does indeed support quite a large range of algorithms and primitives.


Command Resolution Issue: Sibling and Related Commands Not Properly Resolved in Split Command Registrations

I encountered an issue with the command resolution when using the help command in the current framework, which can resolve similar commands through SiblingCommands, ChildrenCommands, and their combination via RelatedCommands. However, this structure has a flaw when commands are registered separately across different classes.
For example, consider the following scenario:
In Class A:
@Command("base help")

In Class B:
@Command("base reward set")
@Command("base reward get")

In this case, the /base help command does not retrieve the base reward commands, because when checking the siblingPath, the path for base help is "base", while the path for base reward get is "base reward". As a result, neither siblingPath nor relativePath returns the full command help I expect.
Temporary Solution:
To resolve this issue temporarily, I implemented my own custom Help handler, using the following code:
Lamp<BukkitCommandActor> lamp = BukkitLamp.builder(this)
        .parameterTypes((it) -> {
            it.addParameterType(CardGroup.class, injector.getInstance(GroupParameterType.class));
            it.addContextParameterFactory(ContextParameter.Factory.forType(
                    MySiblingCommands.class,
                    (parameter, context) -> new MySiblingCommandsImpl(Collections.filter(context.command().lamp().registry().commands(), (anotherCmd) -> {
                        ExecutableCommand<BukkitCommandActor> currentCommand = context.command();
                        String currentPath = Temp.getSiblingPath(currentCommand).toLowerCase();
                        String anotherPath = Temp.getSiblingPath(anotherCmd).toLowerCase();
                        return anotherCmd != currentCommand && !anotherCmd.isSecret() && anotherPath.startsWith(currentPath) && anotherCmd.permission().isExecutableBy(context.actor());
                    }))
            ));
        })
        .build();

I also used the following helper to retrieve the sibling path:
object Temp {
    @JvmStatic
    fun getSiblingPath(cmd: ExecutableCommand<*>): String {
        val field = Execution::class.java.getDeclaredField("siblingPath")
        field.trySetAccessible()
        return field.get(cmd) as String
    }
}

This solution filters commands based on the siblingPath and uses startsWith to retrieve all related commands.
Request for Enhancement:
I believe it would be highly beneficial for the Lamp framework to natively support such functionality, allowing help commands to resolve all relevant commands, even when registered separately across different classes. This enhancement could improve the flexibility and ease of organizing command registration.

Thank you for bringing this to my attention. Yeah, I'm aware that the sibling implementation is not as comprehensive as it should. I think this goes back to the fact that we may not fully agree on who is a sibling of who :P
Nonetheless, the issue you point out is valid. I'll migrate this implementation when I get a chance.
Thanks.

We can agree that in this case help is a sibling of reward set, and I already told you this issue before


Create a domain for my college

Official site: www.xujc.com

Computer Science Department intro
(sorry for the site is Chinese only, however you may use Google Translate)
Proof of students using xujc.com domain: Mail Login Portal

@walt-w Pull request merged. Thank you!


Support for backup configuration

Terraform Version
Not relevant I guess
Affected Resource(s)
Please list the resources as a list, for example:

rediscloud_subscription_database

Expected Behavior
There should be a way to configure the remote back type through terraform
Actual Behavior
Currently doesn't look possible
I checked the redis api and saw that that configuration type is supported but not included in the go library. I guess that is why that was not implemented yet.

Hi @urie-tsec, thank you for the feedback, and I'm sorry for the late response.
We are working on closing some gaps between the API and TF these days, and remote backup is one of them.
I don't have an exact ETA, but I can say it will be available in the next 2-3 months.

Hi @urie-tsec, the remote backup configuration is available in our registry


False positive with MSTEST0018: Method used in test is static but private

Describe the bug
The "data source" member referenced should be allowed to be private.

cc: @Evangelink  @engyebrahim


Open modal performance is slow for Android

Just using the following code for item selection feature. Now i am using doc provided method to open modal. The modal will be shown after 2 seconds which makes UX bad. Any suggestion ? Thanks a lot !
        <Modal
          duration={0}
          style={styles.jumpPageModal}
          ref="jumpPageModal"
          swipeToClose={false}
          swipeArea={0}
          onClosed={this._reactiveSwipeBack.bind()}
        >
          <ScrollView
            contentContainerCustomStyle={styles.jumpPageModalScrollView}
            ref="jumpPageScrollView"
            showsVerticalScrollIndicator={false}
          >
            <View style={styles.jumpPageModalContainer}>
              {this.state.jumpPageOption.map((x, i) => {
                if (this.state.currentPage != i)
                  return (<TouchableOpacity key={i} style={styles.jumpPageOption}><Text>Page {i + 1}</Text></TouchableOpacity>)
                return (<TouchableOpacity onLayout={this._getCurrentPageOptionOffset.bind(this)} key={i} style={styles.jumpPageOption}><Text style={styles.jumpPageOptionSelected}>Page {i + 1}</Text></TouchableOpacity>)
              })}
            </View>
          </ScrollView>
        </Modal>

You can stop Remote JS Debug for test

Even i have the same issue, modal opens after some time and it is very jerky.
Any solution to avoid that?

@stockcode stop js debug doesn't help.
i experience the same result :(

Same on Nexus 5x in Android simulator. Opening a modal is really slow.

I am experiencing similar issues, which is rendering this component useless for most Android devices.

+1, slow when chrome developer tools is open

+1

+1

+1

Any solution for this issue?

+1

I always find this Modal pretty slow on Android , specially if there is  more transparent background area , more it goes slow.

still facing same issue

Same issue in 2020

Same issue in 2022!

Same issue in mid-2022


UI - "MaxListenersExceededWarning" error encountered after which we UI becomes unresponsive.

Electron build from commit id - e8c58e5aca2
Steps to reproduce the problem:
PreReq - Have few assistant and chat threads

Create an assistant.
Chat this this assistant and say a thread called thread1 gets crrated.
Delete this assistant.
Now select the thread that was created from step2.
This will result in the thread not loading and being stuck which is tracked in https://github.com/gptscript-ai/gptscript/issues/736.
When "loading script" is presented , Wait for 10 - 15 secs and then click on any other thread.
Once the this is thread is loaded , go back to the thread1 from step2 .This will again result in being stuck in "loading script".
Following steps  6 and 7 couple of times , will result in even threads (that are from existing assistants) get struck in "loading script" state.

Once we reach this state, clicking on any other threads for about 10 times results in the following error seen and UI becomes completely unresponsive.
(node:34653) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 interrupt listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `Assistant Studio --trace-warnings ...` to show where the warning was created)
(node:34653) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 addTool listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(node:34653) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 removeTool listeners added to [Socket]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit

"Ideas to Enhance Daily walk" is the thread from the deleted assistant:
https://github.com/user-attachments/assets/13e274ac-bec9-4290-be8e-37630c9ab07c

PR: https://github.com/gptscript-ai/desktop/pull/61


Implement Create and List for AppProfiles.

This is part of the work for #780. It creates the functions, unit
tests, sample snippets, integration tests and changes to the
emulator.

Ping?


Add “modified_date” & “updated_by” to the User table

Add “modified_date” & “updated_by” to the User table for tracking updates made by admins
cc @gigincg

@sainak I would like to work on this issue

@sainak What behaviour do we want to implement on User object creation?
Initially SET updated_by to null
or
Initially SET updated_by equal to created_by

@sainak Could I be assigned this issue?

I've been looking through these files...

models.py
user.py
@sainak and @rithviknishad , my general approach is to add the 2 fields in both files. Then make the migrations and the migrations file, so that application logic and ORM are in sync with db. Also, should updating these fields every time someone modifies a user be in the PR as well? Right now, it seems we're just adding in 2 fields. Let me know your thoughts :)


null char at the end of string

When getting a string field from json, the result string contains a null char at the end of the string (this is in addition to the usual null terminator).
As a result, if you try to append two string field obtained from json, you will get: "string1\0string2\0"
This breaks many UI functions as they generally stop at the first \0.

Sorry, my bad, the \0 is slipped in from upstream, not in this component! :D


Why are you not using torchmeta?

https://tristandeleu.github.io/pytorch-meta/api_reference/datasets/

TorchMeta provides some excellent data loaders (great work @tristandeleu and team!), and a meta-module API that makes it easy to implement new modules in a meta-learning compatible way. AFAIK, it does introduce some restrictions, and also doesn't support existing/saved modules, whereas higher's  monkey-patching logic does. Furthermore it only supports SGD as an optimizer, whereas we cover (nearly) all optimizers from torch.optim. For these reasons, my recommendation is to use torchmeta's data loaders in conjunction with higher, as shown in this example. Both libraries work quite well together in this sense, allowing users to write compact and natural meta-learning code without writing much non-standard pytorch, and unleashing the power of existing model implementations and other libraries.


Hitting Esc does not return to Selection mode

(Ignition Citadel 3.3.0) The Manipulating Models tutorial says Esc returns to select mode from any other mode, but this does not appear to be the case.

You can always return to selection mode from any other mode by pressing Esc.

https://github.com/ignitionrobotics/docs/blame/master/citadel/Manipulating_models.md#L42
https://ignitionrobotics.org/docs/citadel/manipulating_models#select-mode
Hitting Esc in Translate mode or Rotate mode deselects entities that are being acted upon, but it never returns to Select mode. Esc as deselect feels pretty intuitive to me - maybe the line about returning to Select mode should be removed from the tutorial?

but it never returns to Select mode

It does for me if the 3D scene has focus, but not if the entity tree has focus. I think we could just make sure that works. And also mention on the documentation that esc also deselects all entities? CC @JShep1

It does for me if the 3D scene has focus, but not if the entity tree has focus.

Interesting! If I add shapes to empty.sdf then it works for me with the 3D scene in focus, but if I launch shapes.sdf and add the Transform Control plugin then I get the behavior in the issue.

Interesting! If I add shapes to empty.sdf then it works for me with the 3D scene in focus, but if I launch shapes.sdf and add the Transform Control plugin then I get the behavior in the issue.

Yeah, so just for some background, this issue is likely boiling down to how QML captures input.  Whichever section is currently focused will accept the input and the other sections will not observe this input, I suppose this is a QML way of optimizing its front-end, but it has proven to be sort of a nuisance in cases like these.  Currently, the method of the focus transitioning to the 3d scene is simply hovering your mouse over that area, so no action will occur on a button press unless the mouse has at least hovered over the 3d scene first (possibly we should add some documentation about this, I tried to fix this awhile ago and honestly couldn't find the best solution which focuses the 3d scene at all times, it may be worth re-visiting).
I see what you mean with the transform control not returning to select mode when the escape button is pressed when you load in the Transform Control via the plugin menu, I'll need to look into this some more.


It's possible to eject Mech pilots while the Mech is moving around

Description
You can be ejected from a mech while you're moving around, and you need to run like 5 tiles away from the person who initiated it to stop the ejection.
Reproduction

>make a ripley
>try to have some fun with it outside of science
>""""""funny""""" clown keeps trying to eject you
>successfully ejects you because they keep pulling you preventing you from running halfway across the station to stop the ejection
>tries to get in your mech
>you beat them to death and then gib their body with an artifact crusher
Additional Context
Any movement should prevent ejection like how any movement stops cuffing/injection/a thousand other mechanics that require you to stand still

any movement stops cuffing/injection
any movement doesn't stop them


decorate UnexpectedConnectionClosureException with IOException

Decorate akka-http exceptions with exceptionds understood by the AWS SDK so that they are automatically retried by the default retry policy. This was inspired in NettyUtils.decorateException
Since UnexpectedConnectionClosureException is private we need to use a hack...

As one can see from the build logs of 8c7a211, the test fails as expected
[info]   Cause: akka.http.impl.engine.client.OutgoingConnectionBlueprint$UnexpectedConnectionClosureException: The http server closed the connection unexpectedly before delivering responses for 1 outstanding requests


Do you support Waymo? Or how to train Waymo using Det3D?

Here is an instruction about how to extract the bin file and label file from Waymo.
https://www.jianshu.com/p/a3e8310cea32      (It is written in Chinese.)
I am a beginner about 3D detection. Could anyone give me a guide to train Waymo using Det3D?
Many thanks.

Thanks for your interest in Det3D!
It should be quite easy to add a dataset into Det3D. Here are the recommended steps:

preprocess the Waymo dataset and generate the infos (annotations) into a pkl file (you can refer to https://github.com/poodarchu/Det3D/blob/master/tools/create_data.py)
follow any of existing datasets (e.g. https://github.com/poodarchu/Det3D/blob/master/det3d/datasets/kitti/kitti.py) to create a Waymo(data.datasets) class, and implement the init (which is used to load the infos file generated in step 1) and the getitem (which is used to load the file and preprocess it).
Add corresponding evaluation func according to waymo's API and metrics.


Need scroll bar in dialog selection page for skill exporting (if this page is required)

Describe the bug
Need scroll bar in dialog selection page for exporting a bot as skill if we did not disable this page .

Version

Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[X] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

I recommend we make the select all checkbox sticky at the bottom and outside the scrollable area.
I strongly recommend against putting the select all checkbox below the fold.

@vivekkshankar close this one, and we will follow your design to fix this issue. dup with #7780


Fix mismatch in views' reductions format

This patch adds a getter for counts and user reductions
from views' states, based on tuple's element position.
That allows to remediate mismatch in state format
used in DBCore and DBNext.
BugzID: 57182

What do we do going forward? We need to get this change into ASF somehow.

@iilyak how I see it, this patch is just to elevate bigblue's pain and confirm I haven't missed anything.
I'm looking into your epi roll-forward now and once we happy with it we'll cut dbnext release with it and mrview proper. Then I'll apply this patch (refactoring rather) to it and submit to ASF. Have no idea what justification to use and how it'll go, but we'll see.

+1


[Feature] Add MonoFlex Coder

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Add monoflex coder.
Modification
add monoflex_bbox_coder.py
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

final review, can be merged after fix.


Add support for variables named "_". Fixes #420

Close #420

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


vBump

$

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6196879394

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6196879394
Status: success


Add GNU Screen bullet

This prompt should help you keep track of the current screen session you're currently working in.
For those who may don't know screen. It's a window manager developed by GNU, which makes it easy to create individual terminal sessions. Often used on servers, in case you lose your ssh connection, you can easily restore to your terminal.
http://www.gnu.org/software/screen/
This is my first pull request, in case I did anything wrong please let me know. 🙂

First of all I am sorry for getting back to you so late.
I gave it a try, the prompt showing up right expect for it's cog glyph. I am sure you are using Mac and maybe iTerm2, that has superior rendering. I am using a Linux distro with highly sophisticated terminals (fonts even) and none is able to show/render that UTF-8 glyph, not even my text editor.
Could you replace it with something from this site, please? https://unicode-table.com/en/
Also if you have found the one you like, please link it back here so I can double check for you that it renders correctly :)
Soon that is working I will merge this PR.

Now I'm really sorry that it took me so long to change this simple icon.
I have chosen this "⬗" prefix, which I have tested on Kali. Even though feel free to change it if you don't like it.


MacOS Native Tabs/Fullscreen Crash

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

VS Code Version:  1.59.0
VS Code Insiders Version:  1.60.0
OS Version: MacOS 11.4 (Big Sur)

Steps to Reproduce:

MacOS System Preferences -> General -> Prefer tabs [ALWAYS] When opening document
MacOS Finder Preferences -> Open folders in tabs instead of windows.
VS Code / Insiders Settings.json -> {  "window.nativeTabs": true,  "window.restoreFullscreen": true }
Open VS Code
Activate Full screen
CMD+Shift+N (New Window) which opens a new VS Code tab
Close VS Code
Reopen VS Code
VS Code should start opening and immediately crash.

Verbose Mode shows that this seems to be the cause:
[main 2021-08-17T15:35:58.001Z] window#validateWindowState: multi-monitor working area { x: 0, y: 25, width: 1680, height: 1025 }
[main 2021-08-17T15:35:58.002Z] window#ctor: using window state { mode: 1, x: 328, y: 141, width: 1024, height: 768 }
[main 2021-08-17T15:35:58.069Z] windowsManager#open used window count 2 (workspacesToOpen: 0, foldersToOpen: 2, emptyToRestore: 1, emptyToOpen: 0)
2021-08-17 11:35:58.070 Electron[68102:513840] *** Assertion failure in -[NSWindowStackController _enterWindow:intoFullScreenWithWindow:], NSWindowStackController.m:1009
[0817/113558.080360:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffee3f76000, 0x2000): (os/kern) invalid address (1)
[0817/113558.302621:WARNING:crash_report_exception_handler.cc(240)] UniversalExceptionRaise: (os/kern) failure (5)
[68110:0817/113558.311591:ERROR:child_thread_impl.cc(227)] Invalid PlatformChannel receive right

I've had this issue consistently for a couple of years now (across the last 3 versions of MacOS at least), but would always be able to solve it by starting VS Code with --disable-extensions from the command line.   Unfortunately that doesn't seem to be the case now, and I'm able to reproduce consistently with a fresh Insiders build.
I can also verify that the crash will happen on with a fresh Insiders build on MacOS Catalina 10.15.7, however, recovery behavior differs slightly.  On Catalina, opening from the command line with no arguments seems to partially ignore the Restore Fullscreen setting, and doesn't open both windows in Full screen.

Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks!

Not entirely sure I did that right, let me know if this isn't what you need
vs-code-crash.zip

I've got exactly the same bug and the same error log

@tybruffy thanks for the detailed repro steps, can confirm the issue.

As I've experienced this issue right now after updating, my workaround is to disable restoring to fullscreen: "window.restoreFullscreen": false.

Version: 1.62.1 (Universal)
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0

I am having the same problem. If you are unable to startup VS Code at all because of this, try doing what @davidenke said, as follows:

Open the file/Users/_yourusername_/Library/Application Support/Code/User/settings.json (you'll probably have to use textEdit to open it since VS Code won't start atm).
Search for the Setting ID: "window.restoreFullscreen" and set it to false
Save the file & VS Code should start again.

Just have to make sure that this setting stays disabled until it's fixed.
After VS Code wouldn't start anymore for a couple times, I tried starting it up through the terminal with code --verbose, which gave me the following output:
❯ ~ code --verbose
[main 2022-04-06T07:37:29.661Z] [File Watcher (node.js)] Request to start watching: /Users/floris/Library/Application Support/Code/User (excludes: <none>),/Users/floris/Library/Application Support/Code/User/settings.json (excludes: <none>)
[main 2022-04-06T07:37:29.671Z] Starting VS Code
[main 2022-04-06T07:37:29.671Z] from: /Applications/Visual Studio Code.app/Contents/Resources/app
[main 2022-04-06T07:37:29.671Z] args: {
  _: [],
  diff: 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': false,
  'disable-gpu': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: 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,
  'crash-reporter-id': '5be41840-2f8d-4ff4-8f04-3031f575c4a0',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: 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,
  logsPath: '/Users/floris/Library/Application Support/Code/logs/20220406T093729'
}
[main 2022-04-06T07:37:29.673Z] Resolving machine identifier...
[main 2022-04-06T07:37:29.673Z] Resolved machine identifier: 071f8abbcb54ae6ac989c1d50d828e5f6f2f056dc388e62a7c5f08f1087d9f80
[main 2022-04-06T07:37:29.674Z] Main->SharedProcess#connect
[main 2022-04-06T07:37:29.678Z] [File Watcher (node.js)] Started watching: '/Users/floris/Library/Application Support/Code/User'
[main 2022-04-06T07:37:29.695Z] [File Watcher (node.js)] Started watching: '/Users/floris/Library/Application Support/Code/User/settings.json'
[main 2022-04-06T07:37:29.715Z] StorageMainService: creating global storage
[main 2022-04-06T07:37:29.721Z] lifecycle (main): phase changed (value: 2)
[main 2022-04-06T07:37:29.722Z] windowsManager#open
[main 2022-04-06T07:37:29.722Z] windowsManager#open pathsToOpen [
  {
    workspace: { id: '928088975d35e4b31bc7d425c2862e06', uri: [h] },
    type: 2,
    exists: true
  },
  {
    workspace: { id: '580658b124f04dfc8bba0fb0e46b7770', uri: [h] },
    type: 2,
    exists: true
  },
  {
    workspace: { id: '928088975d35e4b31bc7d425c2862e06', uri: [h] },
    type: 2,
    exists: true
  }
]
[main 2022-04-06T07:37:29.723Z] windowsManager#doOpenFolderOrWorkspace {
  folderOrWorkspace: {
    workspace: { id: '928088975d35e4b31bc7d425c2862e06', uri: [h] },
    type: 2,
    exists: true
  },
  filesToOpen: undefined
}
[main 2022-04-06T07:37:29.723Z] IPC Object URL: Registered new channel vscode:85c5b6d5-ff1a-419b-a393-261b471e99a9.
[main 2022-04-06T07:37:29.723Z] window#validateWindowState: validating window state on 2 display(s) { mode: 3, display: 3, width: 1024, height: 768, x: 502, y: -1104 }
[main 2022-04-06T07:37:29.723Z] window#validateWindowState: restoring fullscreen to previous display
[main 2022-04-06T07:37:29.723Z] window#ctor: using window state { width: 1024, height: 768, mode: 3, x: -266, y: -1440 }
[main 2022-04-06T07:37:29.853Z] window#load: attempt to load window (id: 1)
[main 2022-04-06T07:37:29.855Z] StorageMainService: creating workspace storage (928088975d35e4b31bc7d425c2862e06)
[main 2022-04-06T07:37:29.856Z] windowsManager#doOpenFolderOrWorkspace {
  folderOrWorkspace: {
    workspace: { id: '580658b124f04dfc8bba0fb0e46b7770', uri: [h] },
    type: 2,
    exists: true
  },
  filesToOpen: undefined
}
[main 2022-04-06T07:37:29.856Z] IPC Object URL: Registered new channel vscode:22c9c417-b2ff-4c3c-80fb-1b2bc2894d30.
[main 2022-04-06T07:37:29.856Z] window#validateWindowState: validating window state on 2 display(s) { mode: 1, display: 3, width: 1024, height: 768, x: -266, y: -1440 }
[main 2022-04-06T07:37:29.856Z] window#validateWindowState: multi-monitor working area { x: -266, y: -1415, width: 2560, height: 1415 }
[main 2022-04-06T07:37:29.856Z] window#ctor: using window state { mode: 1, display: 3, width: 1024, height: 768, x: -266, y: -1440 }
[main 2022-04-06T07:37:29.899Z] window#load: attempt to load window (id: 2)
[main 2022-04-06T07:37:29.900Z] StorageMainService: creating workspace storage (580658b124f04dfc8bba0fb0e46b7770)
[main 2022-04-06T07:37:29.901Z] windowsManager#open used window count 2 (workspacesToOpen: 0, foldersToOpen: 3, emptyToRestore: 0, emptyToOpen: 0)
2022-04-06 09:37:29.901 Electron[84644:1196948] *** Assertion failure in -[NSWindowStackController _enterWindow:intoFullScreenWithWindow:], NSWindowStackController.m:1019
[0406/093730.029549:ERROR:directory_reader_posix.cc(42)] opendir /Users/floris/Library/Application Support/Code/Crashpad/attachments/66f6179c-9812-419e-9942-018b8c17e9de: No such file or directory (2)
[0406/093730.029548:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
[84652:0406/093730.031536:ERROR:child_thread_impl.cc(233)] Invalid PlatformChannel receive right
❯ ~

Version: 1.66.0
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:49:37.118Z (1 wk ago)
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.4.0

Issue does not repro with latest stable 1.74


♻ Include Contract Name in Deployment File Name

PR Checklist

[ ] Because this PR includes a bug fix, relevant tests have been included.
[ ] Because this PR includes a new feature, the change was previously discussed in an issue or in the discussions section.
[x] I didn't do anything of this.

This PR simply suggests adding the contract name defined in the config file to the name of the deployment.json file which will help if the user is deploying multiple contracts, so each file will be CONTRACTNAME_NETWORKNAME_deployment.json.

@asghaier76 Thanks for this, makes very much sense.


✨Preparing For First Initial Release ✨

[!Important]
It is intended to be only merged after the #7 as the code in this pull depends on that pull docs/security_guide.md file. So, it request to merge first that pull and then this.

TL;DR:

Prepared app for its first release by changing changelog, adding icon & enhancing a about us activity.
Also make some changes in build.gradle for better compatibility with all dev environment possible user by contributors.

Changes Made

Enhance a about screen and given info about developers and app development.
Given a warning to users (In About Us) about the application development & safety of passwords.
Update the changelog.
Add icon to app. (Which was created by @HamadaNative)

Important Changes In Build.gradle

change the code from buildFeature to Viewbinding. Coz, buildFeature is not compatible with gradle version we are using. (buildFeature on work with a specific dev environment while, Viewbinding works on both environment in desktop and also in mobile, Codeassist)

Fixes Viewbinding Compatibility with Code Assist
This pull request successful fixes the viewbinding compatibility issue that arise in codeassist.
Icon Based Changes
This pull request add the icon in the app. Which is original create by @HamadaNative but added by me.
The icon is added after a through research on google. So, that similar concept/icon doesn't exist.
Conclusion
Reviewers, Please review the code & Merge it only after #7. And also if possible, Merge it after #8.

[!Note]
With successfull merge of this pull request along with #7 & #8 it will count as the app is prepared for the initial release.

@kudanilll @HamadaNative is that ok?


Example is not completely clear

I think it would help if there would be if clause in the example. Because I would assume from "pathExists('foo').then  that it already has done the check. But instead this is correct:
// foo.js
var pathExists = require('path-exists');

pathExists('foo.js').then(function (exists) {
	if (exists) {
		console.log('foo.js exists');
	}
});

Thanks for you input, but I honestly feel the example is more than clear enough. It's even clearly spelled out in the API docs:

Returns a promise that resolves to a boolean of whether the path exists.


add option to enter custom id2label dicts in init

I can contribute if you guide me.
As far as I understood explainer base class need to pass customer dict to PretrainedConfig during init.

@lalitpagaria that would be really helpful thanks. So because this only applies to sequence classification tasks I think the best place to implement this would be in the __init__ of the SequenceClassificationExplainer.
On the API level I see it looking something like
cls_explainer = SequenceClassificationExplainer(model, tokenizer, custom_id2label = {0: "my_label1", 1: "my_label2"})

Where custom_id2label is a optional parameter that can passed and will set the new values. I don't think you even need to overwrite id2label on the HF model's config itself because the classification explainer sets these as attributes itself so changing it for the explainer should do, I try as much as possible not to interfere with HF model itself.
Some other things that would be nice to do before actually setting the new values would be to check that the length of custom_id2label.keys() matches the existing length. In a case where a user accidentally sets too few or too many labels I would see it raising some sort of value error.
Another thing that this has got me thinking is that once the new id2label is set it would be to set label2id with the inverse values.
Thanks for volunteering to help on this, let me know if you need any further guidance.


Terminal does not support ballistic scroll

#8222

Open integrated terminal with lots of output
Use the trackpad to scroll a lot
Notice how the terminal does not respect the balistic scroll - e.g it always scrolls the same not matter how strong I scrolled

This should work if a native scroll bar is added to the integrated terminal. It was mentioned in https://github.com/sourcelair/xterm.js/issues/150 to use clusterize to implement native scrolling, that may have its own set of issues. Closing in favor of https://github.com/Microsoft/vscode/issues/6602


Fix the reference of runtime_type in component catalog

Fix the reference of runtime_type in component catalog
Description
Fixes: https://github.com/opendatahub-io/notebooks/issues/114
The release image had a reference of Kubeflow pipeline under the component catalog:

With this, we have changed the reference pattern it would show as Data Science Pipeline:

How Has This Been Tested?

Spin up the image and check the component catalog
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/test notebook-base-ubi8-python-3-8-pr-image-mirror

Moving forward and merging this manually.
Taking responsibility for this PR.

Please leave a comment or open an issue if found any error while reviewing
cc: @atheo89 @VaishnaviHire


Classify Dataset UX Updates

Closes fidesplus#404
Code Changes

[x] Return only top 1 suggestion instead of top n in data table
[x] rename button to state approve classifications
[x] Update dataset classify heading text
[x] Update to only approve collection at one time vs entire dataset
[x] Update from returning the first classification to ensure returning the top 1 in the same way the dropdown does
[x] Create a common function to get the topClassification
[x] Exclude Identifiability from  rendering as part of the Dataset view (Closes fidesplus#513)

Steps to Confirm

[ ] Start up fidesplus in the background
[ ] Navigate to the admin-ui and start up the frontend using npm run dev
[ ] Classify the fides db using postgresql+psycopg2://postgres:fides@fidesplus-db:5432/fides (it's actually a bit collection-heavy so feel free to use a smaller one you can find in 1Password such as this)
[ ] Click into the dataset and run through each collection. On the last collection, validate the status is updated

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation:

[x] documentation complete, PR opened in fidesdocs
[x] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[x] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
Currently, these changes feel like a lot is left to be desired as far as the UX for classification. The approve classification button is not informative and should likely change on click or load the next collection to be completed.

As an early criticism, check out this Loom -> https://www.loom.com/share/963dbf44bd044668aa57da96875badb6
It feels like the UX doesn't seem to quite align with what we want here, some more work around the button to approve classifications is likely required. I'd love to see something around loading the next collection to be reviewed as well 🤷🏽

Not sure but I may have introduced a new issue somewhere causing an empty state seizure 🤔 found when retesting https://www.loom.com/share/5b57f5b506cb445b9fa0766b2e640409

Not sure but I may have introduced a new issue somewhere causing an empty state seizure 🤔 found when retesting

Hmm what steps did you take to get here? I've seen this once before but I think it's because my backend wasn't working properly. I'll try to repro on main

Not sure but I may have introduced a new issue somewhere causing an empty state seizure 🤔 found when retesting

Hmm what steps did you take to get here? I've seen this once before but I think it's because my backend wasn't working properly. I'll try to repro on main

It looks like it only happens when using npm run cy:start - I noticed the classify dataset button was missing as well so thinking maybe something wrong with backend too. Flipped back to npm run dev since Cypress seemed to be fine and no more stuttering / classify dataset button visible again

Not sure but I may have introduced a new issue somewhere causing an empty state seizure 🤔 found when retesting

Hmm what steps did you take to get here? I've seen this once before but I think it's because my backend wasn't working properly. I'll try to repro on main

It looks like it only happens when using npm run cy:start - I noticed the classify dataset button was missing as well so thinking maybe something wrong with backend too. Flipped back to npm run dev since Cypress seemed to be fine and no more stuttering / classify dataset button visible again

Ohhhh okay yeah npm run cy:start should only be used against cypress (which I'm only just realizing now too!). This is because we set a NODE_ENV=test there, and in our next config we don't reroute backend requests if we are in the test environment (since these cypress tests should work without a backend (they're all stubbed))
I believe to run a built js, you can npm run build and then npm run start

Ahh, interesting! Thank you once again for the detailed explainer 🙌🏽 makes sense now and I'm not afraid that I did something wonky somewhere 😂


Image for xamarin ios 16.4: unable to restore solution if it contains a Xamarin.Android project

Describe the solution you'd like
Image 16.4 (xamarin ios) does not have this issue.
Image 16.2 does not have this issue.
[command]/bin/bash -c /usr/bin/find . -name '*.sln' -type f -print0 | /usr/bin/xargs -0 grep -l 'xxxxx.iOS.csproj' | /usr/bin/xargs -I '{}' nuget restore '{}' -DisableParallelProcessing
MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/15.0/bin'.
/Users/runner/work/1/s/xxxxx/xxxxx.Droid/xxxxx.Droid.csproj(150,13): error MSB4226: The imported project "/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/xbuild/Xamarin/Android/Xamarin.Android.CSharp.targets" was not found. Also, tried to find "Xamarin/Android/Xamarin.Android.CSharp.targets" in the fallback search path(s) for $(MSBuildExtensionsPath) - "/Library/Frameworks/Mono.framework/External/xbuild/" . These search paths are defined in "/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/MSBuild.dll.config". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths.
/var/folders/lf/qycgv4fd6yjcj__vqnk_wxhm0000gn/T/NuGetScratch/py8ev7ym.9vl.nugetrestore.targets(382,5): warning MSB4181: The "MSBuild" task returned false but did not log an error. [/var/folders/lf/qycgv4fd6yjcj__vqnk_wxhm0000gn/T/NuGetScratch/z6gs83uf.j7i.nugetinputs.targets]
/var/folders/lf/qycgv4fd6yjcj__vqnk_wxhm0000gn/T/NuGetScratch/py8ev7ym.9vl.nugetrestore.targets(394,5): warning : Skipping restore for project '/Users/runner/work/1/s/xxxxx/xxxxx.Droid/xxxxx.Droid.csproj'. The project file may be invalid or missing targets required for restore. [/var/folders/lf/qycgv4fd6yjcj__vqnk_wxhm0000gn/T/NuGetScratch/z6gs83uf.j7i.nugetinputs.targets]

##[error]/bin/bash failed with return code: 1
##[error]/bin/bash failed with error: /bin/bash failed with return code: 1

Describe alternatives you've considered
Rollback to 16.2

This is incredibly painful. The best solution is to have a post-clone step that removes the Android projects from the solution at runtime, then the NuGet restore step of the entire solution will work. There's a pretty cool command called dotnet sln that will do this. I'd suggest looking into that.
Note that trying to run NuGet restore just for certain projects is inadvisable, because project dependencies don't get resolved such that it will restore the projects in the right order. You really have to NuGet restore at the solution level.

This week new issue. My customer's project does not compile anymore, with 16.4 oe 16.2, maybe because Visual Studio Mac has been removed from the images.
I switched to Azure pipelines to build the IPAs, and published them to Appcenter Distribute.
If someone is interested I can publish the yaml pipeline here. It took me 2 days to create successfully.
This is time lost before migrating to maui and codemagic.

Yes, the problem stems from Xamain.iOS and Xamarin.Android not being on the macOS-13 images that are used by AppCenter builds (via Azure DevOps). Setting the mono version back to an earlier version in an AppCenter build configuration gets around that, but causes other problems because it uses Xcode 14.2 rather than 15.x.

Just in case it helps anyone I was having the same issue and followed @brunck advice of using dotnet sln and got it to work.
I created an appcenter-post-clone.sh script file in the iOS project folder like the documentation specifies.
Inside it added the line below:
dotnet sln <path to solution> remove <path to android project>

@softlion
Hi,
I also have some problems with AppCenter since some weeks, so I would be very interested in the Azure Pipelines scripts. Can you provide them to me?
Thanks

Just in case it helps anyone I was having the same issue and followed @brunck advice of using dotnet sln and got it to work. I created an appcenter-post-clone.sh script file in the iOS project folder like the documentation specifies. Inside it added the line below: dotnet sln <path to solution> remove <path to android project>

@dinisvieira  Can you help me please with a complete sample of your appcenter-post-clone.sh
I do this script ans i have an error -> Could not find solution or directory /Users/runner/work/1/s/project/project.sln.
For an other script (appcenter-pre-build.sh) i use variable like SLN_FILE or  ANDROID_PROD_FILE to find files in project and this is ok no error
My script
#!/usr/bin/env bash
SLN_FILE=$APPCENTER_SOURCE_DIRECTORY/project/project.sln
ANDROID_PROD_FILE=$APPCENTER_SOURCE_DIRECTORY/project/project.Android/project.Android.csproj
dotnet sln $SLN_FILE remove $ANDROID_PROD_FILE

Just in case it helps anyone I was having the same issue and followed @brunck advice of using dotnet sln and got it to work. I created an appcenter-post-clone.sh script file in the iOS project folder like the documentation specifies. Inside it added the line below: dotnet sln <path to solution> remove <path to android project>

@dinisvieira Can you help me please with a complete sample of your appcenter-post-clone.sh
I do this script ans i have an error -> Could not find solution or directory /Users/runner/work/1/s/project/project.sln. For an other script (appcenter-pre-build.sh) i use variable like SLN_FILE or ANDROID_PROD_FILE to find files in project and this is ok no error
My script #!/usr/bin/env bash
SLN_FILE=$APPCENTER_SOURCE_DIRECTORY/project/project.sln ANDROID_CSPROJ_FILE=$APPCENTER_SOURCE_DIRECTORY/project/project.Android/project.Android.csproj
dotnet sln $SLN_FILE remove $ANDROID_CSPROJ_FILE
If i add in the script an echo $SLN_FILE; -> i have in the build -> /Users/runner/work/1/s/project/project.sln

It's not easy for me to help you without knowing your solution/folder structure. But the trick I used was taking into account that the "current directory" is going to be the place where you have the csproj that is being built. From there I "go back/up" into other folders.
For my scenario I'm running for the iOS project so I "go back/up" to the Solution and Android projects. (each ../ goes back/up one folder) dotnet sln ../../../SolutionName.sln remove ../Android/AndroidProject.csproj

ok thanks
the script is correctly executed , i have this line in the build process ...
[command]/bin/bash /Users/runner/work/1/s/project/project.iOS/appcenter-post-clone.sh
but just after there is the crash  Could not find solution or directory /Users/runner/work/1/s/project/project.sln.
The path seems to be ok ...i will test in your way with ../. ...etc


Update README.rst

I had the same issue as #144 and felt really dumb after :)
I think this small snippet could help others avoid the same issue
Thank you for this beautiful project!

I just saw this, and think it is in line with the rest of the readme, and you're the second person bitten by it so clearly it is an issue. Merging. Thank you!

Thanks, Fred! :-D

My pleasure! Hope you and yours are doing great!

Likewise!!


Add getFileUrl API

This PR

updates blockstack.js to 19.0.1-beta.1
add new API getFileUrl and tests for it (fixes #122 )

This PR is based on branch feature/19_0_0

Looks like the new web app at view-source:https://flamboyant-darwin-d11c17.netlify.com/redirect.html is opening blockstacksample:?authResponse=
And the manifest is still using <data android:scheme="myblockstackapp" />

Also running into a weird issue with auth after merging develop into this branch. The redirect seems to be going back to the browser instead..


bigdatagenomics/mango/#25

fixed issue for mate pair printing on same tracks and connecting matepairs

Can one of the admins verify this patch?

Jenkins, add to whitelist.

Merged build triggered.

Merged build started.

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

Merged build finished. Test PASSed.

Great work @akmorrow13! Looks good. I made a pass over and mostly pointed out some Scala nits.

Merged build triggered.

Merged build started.

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

Merged build finished. Test PASSed.


xWebAdministration: Added new helper function module

Pull Request (PR) description

Changes to xWebAdministration

Remove the file HighQualityResourceKitPlan.md which served no purpose.
Added Installation, Requirements, and Examples sections to the README.md.
Added new module to hold helper functions Modules\xWebAdministration.Common,
this module replaced the DscResources\Helper.psm1 module.

Updated Find-Certificate to correctly throw an error if the path
was not found.

Update each resource to correct import the new common helper function
module.

This Pull Request (PR) fixes the following issues
None.
Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

This PR is a prerequisites for some of the issues I submitted for the hacktoberfest, so I will merge this as soon as the tests passes.

Codecov Report

Merging #479 into dev will increase coverage by 0.51%.
The diff coverage is 96.86%.

@@            Coverage Diff             @@
##              dev     #479      +/-   ##
==========================================
+ Coverage   90.87%   91.39%   +0.51%
==========================================
  Files          17       17
  Lines        2467     2661     +194
==========================================
+ Hits         2242     2432     +190
- Misses        225      229       +4

Impacted Files
Coverage Δ

..._xIisMimeTypeMapping/MSFT_xIisMimeTypeMapping.psm1
100% <100%> (ø)
:arrow_up:

...SCResources/MSFT_xWebAppPool/MSFT_xWebAppPool.psm1
94.44% <100%> (+0.06%)
:arrow_up:

...sFeatureDelegation/MSFT_xIisFeatureDelegation.psm1
100% <100%> (ø)
:arrow_up:

...ApplicationHandler/MSFT_WebApplicationHandler.psm1
100% <100%> (ø)
:arrow_up:

...SCResources/MSFT_xIIsHandler/MSFT_xIisHandler.psm1
100% <100%> (ø)
:arrow_up:

DSCResources/MSFT_xIisModule/MSFT_xIisModule.psm1
5.66% <100%> (+2.74%)
:arrow_up:

...FT_xWebConfigProperty/MSFT_xWebConfigProperty.psm1
93.44% <100%> (+0.46%)
:arrow_up:

...yCollection/MSFT_xWebConfigPropertyCollection.psm1
98.03% <100%> (+0.08%)
:arrow_up:

...WebVirtualDirectory/MSFT_xWebVirtualDirectory.psm1
89.36% <100%> (+0.72%)
:arrow_up:

...FT_xWebConfigKeyValue/MSFT_xWebConfigKeyValue.psm1
92.85% <100%> (+0.35%)
:arrow_up:

... and 8 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 4f19e76...197b5d3. Read the comment docs.


Fix Groovy and Java joint compilation failure on Java class private dependency change

General idea: if there is Groovy/Java joined compilation, we delete/stash files only just before Groovy runs Java compiler.
Fixes #22531.

This is already reproducible with at least Gradle 7.5, so it's an older bug that surfaced. Removing 7.6 milestone.

@bot-gradle test this

CompileTransaction.java was actually renamed to AbstractCompileTransaction, here is the diff if it helps in anyway:
33a34
+ import java.io.Serializable;
54,57c55
- /**
-  * A helper class to handle incremental compilation after a failure: it makes moving files around easier and reverting state easier.
-  */
- public class CompileTransaction {
---
+ public abstract class AbstractCompileTransaction implements CompileTransaction {
67c65
-     public CompileTransaction(
---
+     public AbstractCompileTransaction(
97c95
-         StashResult stashResult = stashFilesThatShouldBeDeleted();
---
+         StashResult stashResult = collectFilesThatShouldBeStashed();
98a97
+             doStashFiles(stashResult.stashedFiles);
113a113,114
+     abstract void doStashFiles(List<StashedFile> stashedFiles);
+
187c188
-     private StashResult stashFilesThatShouldBeDeleted() {
---
+     private StashResult collectFilesThatShouldBeStashed() {
195d195
-             moveFile(sourceFile, stashedFile);
256,257c256
-     private static class StashResult {
-
---
+     private static class StashResult implements Serializable {
305c304,306
-     private static class StashedFile {
---
+     static class StashedFile implements Serializable {
+         private static final long serialVersionUID = 1L;
+
313a315,318
+         public void stash() {
+             moveFile(sourceFile, stashFile);
+         }
+
318a324
-

@bot-gradle test QFL

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test APT

OK, I've already triggered the following builds for you:

AllPerformanceTestsReadyForRelease build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle cancel

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

I am not sure this is the right way to solve the problem. It seems that in order to do the AST analysis of a class which is not part of the current compilation unit, the Groovy compiler tries to load the class using the compilation classpath. Loading the class also means loading all dependent classes, without taking any visibility into account. So it seems like the Groovy compiler cannot deal with only recompiling the classes which need to be recompiled due to ABI changes within the same source location. I wonder if recompiling all classes which are affected by a change in the same compilation unit makes sense in that case and would be another solution to the problem.
Another thing we should be doing is to raise this problem with the Groovy team. Maybe the Groovy compiler fixes this in Groovy 4 and doesn't try to load classes any more.

After my investigation into the root cause of this, I think the alternative fix is safer -- leaving the old class around seems ripe for more strange issues, whereas the alternative fix basically reverts it to a normal compilation.


Testing stuff

Dear community,
do you have any idea what https://github.com/tinymce/tinymce/commit/d0a84c0e4f5aaca7a2f795db920293b68849b3c2 and https://github.com/tinymce/tinymce/commit/8c9f1c19e0a94d39d1cbbe320b70af4d6934f2a9 are necessary for and if they should be included in HugeRTE? I don't know what's flaky about the tests and so on...

Many tests fail :(

Oh, my Jenkinsfile is like if I had applied the second commit (don't know if exactly, didn't look right now) but my Gruntfile not...it's about having applied commits from TinyMCE 7 (before the license change).

The new Jenkinsfile is from https://github.com/hugerte/hugerte/commit/dc8aeffc6e42777093426887e6c5dd497db3a378. Will try to merge 8c9f1c1.


Add suppress tag for "declaration of multiple variables with shared type information"

I don't tend to write code this way, but it would be nice to be able to suppress this warning without suppressing all warnings for the function. I don't see this particular warning (MULTIPLE_VAR_DEF) in a diagnostic group other than ALL.
E.g.
/**
 * @suppress {multipleVars}
**/
function foo () {
  var a, b, c, d, e, f, g;
  ...
}

The code in your example doesn't produce a warning. You need a type annotation for the warning to happen. Eg:
http://closure-compiler-debugger.appspot.com/#input0%3Dvar%2520a%252Cb%252Cc%253B%250A%250A%252F**%2520%2540type%2520%257Bnumber%257D%2520*%252F%250Avar%2520x%252C%2520y%252C%2520z%253B%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26MISSING_PROPERTIES%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1
We generally avoid turning off individual type checking warnings. More customization to the type checker makes it harder to understand what is actually being checked, and if suppressions hide real bugs.

I wish we'd just git rid of that warning or move it to a lint check. All it does is serve to annoy me.

@ChadKillingsworth +1

The type annotation is being ignored, shouldn't there be a warning for that?
http://closure-compiler-debugger.appspot.com/#input0%3Dvar%2520a%252Cb%252Cc%253B%250A%250A%252F**%2520%2540type%2520%257Bnumber%257D%2520*%252F%250Avar%2520x%252C%2520y%252C%2520z%253B%250A%250Afunction%2520f(%2520%252F**%2520string%2520*%252F%2520a)%2520%257B%257D%250A%250Afunction%2520g()%2520%257B%250A%250Af(x)%253B%250Af(y)%253B%250Af(z)%253B%250A%250A%257D%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26MISSING_PROPERTIES%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1

Yes - if it's ignored we should warn. The warning just leave the impression that applying one type annotation to multiple variables may not have been intended by the user. So at a minimum we should update the error message to state that.
It would be better though to support this use case. In either case it's a pretty minor issue.


Allow passing procs with variable arguments when declaring an attribute

Allows procs with variable arguments to be used in an attribute declaration, which will also allow the usage of &:proc. Instead of having to write something like:
class MovieSerializer
  attribute :released_in_year do |object|
    object.release_year
  end
end

We can instead write:
class MovieSerializer
  attribute :released_in_year, &:release_year
end

Should also address https://github.com/Netflix/fast_jsonapi/issues/250

@Erol this would be a nice thing to add to 1.3.1 so when this is done i will release that branch

@shishirmk Done rebasing from dev


integration tests failing

tests are still failing, please prioritize this so we can make a new release: https://github.com/ploomber/jupysql/actions/runs/6734436038/job/18305373346

Can we enbale the credentials for PRs temporarily so that the integration tests pass before merging? this error looks a new test that is failing (clickhouse and not redshift/ snowflake). we need to revert a change made in https://github.com/ploomber/jupysql/pull/912

when PRs are opened from forks, the credentials cannot be shared.
if you create a branch in this repository (I think you have permissions to do it), the integration tests will run. if they don't, you can change the github actions config to allow that


errors in run source code(.zip)  (or download two unitypackages)

Describe the bug
show some errors while run lastest relase v2.0.0 RC1 Refresh source without any change in unity 2018.3 remote to my hololens 1( I' m sure connecting success)。
A clear and concise description of what the bug is.
1.Failed to find a holographic camera. Is the Mixed Reality portal running?
2.Main camera does not exist!
UnityEngine.XR.WSA.HolographicSettings:get_IsDisplayOpaque()
Microsoft.MixedReality.Toolkit.MixedRealityCameraProfile:get_IsOpaque() (at
Assets/MixedRealityToolkit/Definitions/MixedRealityCameraProfile.cs:77)
3.transform.position assign attempt for 'VisualProfiler' is not valid. Input position is { NaN, NaN, Infinity }.
UnityEngine.Transform:set_position(Vector3)
Microsoft.MixedReality.Toolkit.Diagnostics.MixedRealityToolkitVisualProfiler:LateUpdate() (at Assets/MixedRealityToolkit.Services/DiagnosticsSystem/MixedRealityToolkitVisualProfiler.cs:237)
To reproduce
Steps to reproduce the behavior:

Download lastest source(.zip) and open in unity 2018.3.12f1
Click on scenes  SolverExamples  (or AudioLoFiEffectDemo, BoundaryVisualization  )
remote connect to hololens 1 and run.
See errors

Screenshots

Your Setup (please complete the following information)

Unity Version [e.g. 2018.3.12f1 , 2018.3.9f1]
MRTK Version [v2.0.0 RC1 Refresh(lastest)]

Target Platform (please complete the following information)

HoloLens (remote connect success)

I upgrade hololens 1 and it is ok. @wiwei @chrisfromwork


Update openStandardsSupported.yml

added in link to open standards guidance. this will need to be reviewed for style because the latest links in hints aren't showing up properly.

I've successfully parsed this using an online markdown editor (http://dillinger.io/) so it gets my :+1:


docs: add Blaze to list of projects

Blaze uses commitlint to ensure conventional commits are being written and it's really helped with automatically creating our change logs per package i.e. it now has some change logs!

Hi @gregorypratt. This repo is a fork of the canonical https://github.com/conventional-commits/conventionalcommits.org repo. I would suggest re-opening your pull request there.

D'oh! Sorry!


nomination pool withdraw unbonded bot

scan all pools
find their bonded account (example: https://github.com/substrate-portfolio/polkadot-portfolio/pull/16/commits/637a3889a8a98d8384833c2ce9f7eb78faab3a34#diff-17782fa0982182d57be83b90b00797e4ef1da85220c6780e23e310f272389aecR226)
find the api.query.staking.ledger entry associated with it
if ledger.unlocking == api.qeury.consts.staking.maxUnloking (16), call this transaction

Like all other transactions, we should support -c (count of the batch) -T and dryRun the transaction before sending.

This won't really be needed because we fixed it in the protocol.


Camera pose estimation from homography matrix

Hi, thanks for this fantastic library.
I was wondering if there is a way to estimate the camera pose (camera drift between two frames) from the homography matrix for SLAM.

Hi, thanks for this fantastic library.

Thank you for your comment.

I was wondering if there is a way to estimate the camera pose (camera drift between two frames) from the homography matrix for SLAM.

Even though the library doesn't provide camera routines at this time, you can estimate the pose using a planar homography if you have a calibrated camera. The following reference discusses the subject:
Marchand, E., Uchiyama, H., & Spindler, F. (2015). Pose estimation for augmented reality: a hands-on survey. IEEE transactions on visualization and computer graphics, 22(12), 2633-2651.


Check for BST

IMPORTANT: Please do not create a Pull Request without an issue.
All Submissions:

[x] I have read the CONTRIBUTING document.
[x] My code is written in Python3 and is ending with .py
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] I have checked that my submission does pass the test on LeetCode.com
[x] Does your filename follow the naming Conventions?
[x] Have you linked your PR to an Issue?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Hey @adityaarakeri, I have changed the filename to sync with the naming convention.


fix: recursive method leads to stack overflow exception.

fixes AM-3317
Issue
https://gravitee.atlassian.net/browse/AM-3317

Looks good. Thanks for your help. It highlights a contract issue for SecretProvider to fix somehow. But for this it is fine for now.

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

5.16.2
GitHub release

Your semantic-release bot :package::rocket:


Add optional field internalType to Param

Add internalType field to Param.

Closes #230

Is this OK to merge? @mattsse


Add an entropy-based recommender

acton.recommenders.EntropyRecommender should do uncertainty sampling using entropy.

Implemented in 007b03b1243399bf42fd7c187abd4b364b5e6fc2


Fix Traefik Hub documentation link

Traefik Hub's documentation has been remade with a new docs website; thus, the previous link moved.
cc @svx
Original PR for reference: https://github.com/keycloak/keycloak-web/pull/420

This DCO validation is killing me :(


[v1.1] Allow GeneratingHandlers to skip Apply if resource version didn't change

Backport of #341
Since the pkg/generic/fake does not exist in v1 (used in tests), I had to replace it by using a mock

I needed this change in v1 in order to be able to use it in Fleet (master branch already upgraded to v2, but existing release branches still use v1).

CI is consistently failing but it's unrelated to my changes. I've opened #352 to address it


Baremetal frontend

Baremetal frontend for RaspberryPI 3/4/400

Mostly working on RasberryPi3 :)
https://github.com/andreas-jonsson/virtualxt/tree/develop/front/rpi

Things are working well on RPI 3/4/5.
I will break this up in to separate issues.


Release build not showing map

Hello since the ticket has been closed and no longer be opened. Below is the bug and some root cause analysis
I can confirm that release build is not working. I deployed it to my local web server and it doesn't work. I inspected the layout and it seems that the css files are not being loaded properly, as I can see the classes are not attached to the mapbox divs.
I added the css manually in the inspector and here is before and after
Before - its blank

After - map appears

I checked the build css files that was generated and the style mgl-map-wrapper can't be found, hence not rendering...

Can you please advise? I tried building the native mapbox gl js release version and I didn't face the issue. For some reason in this library during the build process, the css is not properly attached or generated on the dist build

Welp, I just copied this css coming from this library to my main vue js file
.mgl-map-wrapper {
  height: 100%;
  position: relative;
  width: 100%;
}
.mgl-map-wrapper .mapboxgl-map {
  height: 100%;
  left: 0;
  position: absolute;
  top: 0;
  width: 100%;
}

and it worked.. Why was this not being autocopied when building my release? Other libraries/dependencies css are being copied over but not this library...
cc: @woshikie

Let me copy over from the other ticket in case @vinayakkulkarni missed it
I have updated my repo with the latest package and this is the output from my npm run build.
dist.zip
You can see for yourself that the map is not showing. It is showing, however, on debug builds, which we can see on CodeSandbox or npn run serve
If you don't have a development web server to run the files, you can use python as a web server.
Assuming you are using python 3 and you extracted the zip file to your current working directory:
python -m http.server --directory dist
You should be able to reach your python web server on http://localhost:8000 (by default)
Edit: not opening a new issue as we can simply reopen this one

It seems that "sideEffect" in package.json controls if the css will be excluded.
I have made a pull request ( #182 ) to fix this.
More information about "sideEffect" in vuejs/vue-cli#4832
I also see that @vinayakkulkarni has suggested another alternate fix in woshikie/mapbox-bug-demo#1
I think #182 fix is better, imo.

@woshikie & @vvavepacket: Kindly refer to this PR - https://github.com/woshikie/mapbox-bug-demo/pull/1, as this is a configuration issue but not an issue with v-mapbox per se

One of the commenters in the vue-cli issue quoted:

https://vue-loader.vuejs.org/guide/#manual-setup
Scroll to the bottom.

If you are developing a library or in a monorepo, please be aware that CSS imports are side effects. Make sure to remove "sideEffects": false in the package.json, otherwise CSS chunks will be dropped by webpack in production builds.

I believe we should reopen #182 or @vinayakkulkarni could author a similar patch.

That's actually an issue with your vue repo which bundles the package using vue-cli-service right? not with the library per se. The library is built using rollup & not webpack anyways

This is the artifact built on this repo's main branch
package.zip
We can see that in its package.json there is a line describing "sideEffects": false.
This line here stopped the bundle process from including the css files

This was an issue for me, importing the js via webpack. Not sure what the solution is internally, but it's still a problem.
Worked around it by manually adding the .mgl-map-wrapper css above into my project.