fix(#798): Async callback was not invoked within the 5000ms timeout

Closes: #798

Which test is this for? Many tests explicitly set 5000ms timeouts.

NPM directory listing
https://github.com/denoland/deno_website2/blob/ba67b17b653aaf5bfaeb485586c3cb3c52f481c5/util/registries/npm.test.ts#L67


chore(deps): update tinyglobby and use isDynamicPattern

Description

follow up to https://github.com/vitest-dev/vitest/pull/6502#issuecomment-2383502911

Replaced isDynamicPattern with the one from tinyglobby. It also fixes a symlink issue reported by storybook https://github.com/vitest-dev/vitest/pull/6274#issuecomment-2375380966
Thanks @SuperchupuDev for the new release!

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[ ] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

FYI I've just released a 0.2.8 hotfix 😅 you might want to update to that instead

@SuperchupuDev It looks like this exotic case https://github.com/vitest-dev/vitest/pull/6274#issuecomment-2274472142 came back as failing/timeout? I ran it locally on my Linux PC and this indeed gets stack.
pnpm -C test/reporters test custom-reporter -- -t 'load no base'

interesting, i'll take a look tomorrow. meanwhile, can you try to tell me the exact glob usage that makes it get stuck?

@SuperchupuDev I tried a repro but it looks quite puzzling. It's likely that this is related to the scenario like https://github.com/SuperchupuDev/tinyglobby/issues/53, but behavior-wise, it's same as v0.2.6, so maybe something happened internally which is affecting performance of large node_modules crawling.
I can only reproduce the difference between v0.2.6 and v0.2.8 on Vitest repo's node_modules. I added test/reporters/repro.mjs, which should stuck only on v0.2.8. I hope it would help the investigation.

i think i know what's going on, node_modules are linked to each other when using pnpm, making fdir recursively crawl those. if two packages use each other it probably enters an infinite loop. i wonder how fast-glob handles that

@hi-ogawa can you tell me if it works using "tinyglobby": "https://pkg.pr.new/tinyglobby@1f1fa12" in the package.json? let me know if it does then i'll do a new release

@SuperchupuDev Thanks for quick follow up. I confirmed https://pkg.pr.new/tinyglobby@1f1fa12 is working locally. I'll push it here to check CI now.

i think i know what's going on, node_modules are linked to each other when using pnpm, making fdir recursively crawl those. if two packages use each other it probably enters an infinite loop. i wonder how fast-glob handles that

Good spot. That might be it since we have a cyclic workspace warning by pnpm like this:
$ pnpm i
Scope: all 47 workspace projects
 WARN  There are cyclic workspace dependencies: /home/hiroshi/code/others/vitest/packages/browser, /home/hiroshi/code/others/vitest/packages/vitest
...

great, glad that it works. i've just released 0.2.9 that reverts the symlinks resolution support

@hi-ogawa fyi i've just released 0.2.10 which adds back symlinks resolution, without a critical bug this time 😅

Closing as per https://github.com/vitest-dev/vitest/pull/6688


adding isNewSerializerAPI: true sets embedded relational data JsonAPI format

I was getting an error in my tests that said need to set isNewSerializerAPI to true on my serializer.
when I do it changes the data format from what should be this:
{"name":"name one",
"sent_at":"Wed Jan 06 2016 17:49:47 GMT-0800 (PST)",
"template":"template1",
"filter": {
            "has-donated":"yes",
            "any-all":"all"
    }
  }
}

to this:
{"name":"name one",
"sent_at":"Wed Jan 06 2016 17:49:47 GMT-0800 (PST)",
"template":"template1",
"filter": {"data":{
             "attributes":{"has-donated":"yes",
                                 "any-all":"all"
             },
             "relationships":{"campaign-email":
                {"data":{"type":"campaign-emails","id":null}}},"type":"filters"
             }
   }
}

this is my serializer:
import DS from 'ember-data';
import ApplicationSerializer from './application';
export default ApplicationSerializer.extend(DS.EmbeddedRecordsMixin, {
  attrs: {
    users: {
      serialize: 'id'
    },
    filter: {
      embedded: 'always'
    }
  }
});

What version of Ember Data, Ember, and Active model Adapter are you using?
What code is calling this?
Can you reproduce in a jsbin at all, and/or post your model definitions?

Active-model-adapter  : 1.13.6
Ember                          : 1.13.11
Ember Data                 : 1.13.15
ill try and get the rest to you soon.

I would suggest trying the latest version of ActiveModelAdapter which is currently in the 2.x series. I think it is still compatible with 1.13.

I got the same error when updating to AMS 2.0.3 and reproduced it with a sample app here: https://github.com/koryteg/ams-sample

@koryteg Sorry for the delay :(. Thanks for adding a test case though, it was extremely helpful in debugging.
TLDR; Add an ApplicationAdapter and import '../test-helper' in your unit tests as written below.
Ok, this was a bit of a tricky one to track down.
The bug
In the embedded records mixin, we call snapshot.serialize, this does a few things to get the JSON:
*looks up the model's adapter using store.adapterFor, then serializes the model using the found adapter's defaultSerializer
The lookup order is something like modelName, 'application', default for store (JSONAPI). I can't remember the exact order but it's in the store.js source code.
So, the workaround for now is to add an application adapter:
//app/adapters/application.js

import ActiveModelAdapter from 'active-model-adapter';

export default ActiveModelAdapter.extend({

});

Also, due to the way tests work, you'll need to import test-helper so the resolver is set correctly in unit tests. I'm not sure why that's not a default in ember-cli. Anyway:
// tests/unit/serializers/comment.js

import '../test-helper';

moduleFor('serializers:comment');

// test code...

On our side we should:

Generate an application adapter for you
Throw an exception if you don't have one define, and instruct you to do so.

thanks for hunting this down. it was really throwing me for a loop.

Closing due to inactivity. Please feel free to reopen if this issue is still presenting itself.


relax tests for old pygments

Relax our dependancy on Pygments.  To address issues like these:
Fixes https://github.com/Textualize/rich/issues/2810
Not our fault, per se. But that doesn't mean we aren't going to keep getting issues about it.

Codecov Report
Patch coverage: 81.81% and project coverage change: -3.17 :warning:

Comparison is base (c2df987) 98.38% compared to head (42e1ec9) 95.21%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2851      +/-   ##
==========================================
- Coverage   98.38%   95.21%   -3.17%
==========================================
  Files          74       74
  Lines        7930     7926       -4
==========================================
- Hits         7802     7547     -255
- Misses        128      379     +251

Flag
Coverage Δ

unittests
95.21% <81.81%> (-3.17%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

rich/syntax.py
98.48% <50.00%> (-0.91%)
:arrow_down:

rich/pretty.py
96.41% <83.33%> (-0.12%)
:arrow_down:

rich/console.py
95.15% <100.00%> (-2.88%)
:arrow_down:

rich/text.py
99.48% <100.00%> (ø)

rich/traceback.py
95.45% <100.00%> (-0.80%)
:arrow_down:

rich/_windows_renderer.py
0.00% <0.00%> (-100.00%)
:arrow_down:

rich/_win32_console.py
3.01% <0.00%> (-86.94%)
:arrow_down:

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.


Sphinx

All JUST files have been documented.

The errors are corrected.
On Mon, Sep 10, 2018 at 11:16 AM, Andy Neff<EMAIL_ADDRESS>wrote:

@andyneff commented on this pull request.
In docs/linux/index.rst
https://github.com/VisionSystemsInc/vsi_common/pull/55#discussion_r216361675
:

+===============
+Linux Utilities
+===============

+.. toctree::

:maxdepth: 2
:caption: Contents:

ask_question.auto
bin_utils.auto
colors.auto
common_source.auto
cuda_info.auto
dir_tools.auto
elements.auto
example.auto

What does this refer to? It does not appear to be found
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VisionSystemsInc/vsi_common/pull/55#pullrequestreview-153824396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnOAEQSH3XVs9G3uDrVDzui9m_l50rQoks5uZoI8gaJpZM4WhlgC
.

--
Vision Systems Inc.
10 Hemingway Drive
https://maps.google.com/?q=10+Hemingway+Drive+Riverside,+RI+02915&entry=gmail&source=g
Riverside, RI 02915
https://maps.google.com/?q=10+Hemingway+Drive+Riverside,+RI+02915&entry=gmail&source=g
401-427-0860 x 109 <401-427-0860%20x%20108>


v0.20.0 deps and belay select issue

repro:

did a clean venv + sourced it
pip install belay
belay [enter]

venv/lib/python3.11/site-packages/belay/cli/new.py", line 6, in <module>
    from packaging.utils import canonicalize_name
ModuleNotFoundError: No module named 'packaging'

then:

pip install packaging
belay [enter] all good
belay select
note: this only happens when no board is found/connected

  File "venv/lib/python3.11/site-packages/belay/cli/select.py", line 119, in select
    device_index = select_table(
                   ^^^^^^^^^^^^^
  File "venv/lib/python3.11/site-packages/belay/cli/questionary_ext.py", line 104, in select_table
    raise ValueError("A list of choices needs to be provided.")
ValueError: A list of choices needs to be provided.

Thanks for the report! For some reason I thought packaging was builtin; I'll open up a PR adding it as a dependency soon. I'll also be uncapping a lot of the dependency versions upper ends.
It appears that when no boards are found, the provided list is empty, and stuff errors out. I'll also add in logic to handle this more gracefully.

Fixed in #135, will be a part of v0.20.1, which ill be releasing very soon

sorry, I didn't notice your last comment, I'll also fix that right now; will be a part of v0.20.1 as well. That's a super simple bug that just slipped through the cracks (those have to be tested manually, not by CI).

top!


Can I use Product View without having deploy collector?

Hi team, I wonder if is there an option to show the group data on the product dashboard from MongoDB but without having deploy collector? :c

You would need deployment data. Jenkins plugin can publish deployment data from your deployment jobs on Jenkins.

@tabladrum
I have jenkins jobs but that can only populate the Build Stage.
How can I populate data for the stages DEV, QA, INT, PERF ?

Thanks in advance :D

@oshingc Closed . https://github.com/capitalone/Hygieia/issues/884

Hello Team. Need some help with product dashboard. We are not using any deployment collector. With Jenkins collector we are not getting the branches as (Dev, QA ..) in our product dashboard.
Can you please let us know is there any configuration settings  we need to do for achieving this?Thanks in advance

@HygieiaUser  - install hygieia-jenkins publisher plugin and configure post build actions in your jenkins jobs for all environments. Plugin will push deployment data to Mongo and deploy widget in you dashboard will display your job names. Follow https://github.com/capitalone/Hygieia/tree/master/hygieia-jenkins-plugin
Once deploy widget is configured, configure pipeline widget and then you should see all the information on product dashboard.


Does this library support disabling of automatic revalidation

If I disable the revalidateIfStale option then SWR does not seem to make the initial request and therefore no data is rendered/retrieved

Is this a known issue? Any advice would be appreciated.

Hi @Ol-Wood , this lib just for generating functions to retrieve data by using SWR, the functions can receive all params which SWR can receive, I think you need might be this https://swr.vercel.app/docs/revalidation


code of conduct guidelines

Welcome! Please use this template for reporting documentation issues on https://developers.google.com/web/.
For questions about Chrome DevTools, checkout the
google-chrome-devtools tag on StackOverflow.
For questions about Chrome, check the google-chrome
tag. If you think you've found a Chrome bug, check out our
feedback page for more details on how to file it.
Page Affected: https://developers.google.com/web/TODO
What needs to be done?
Please provide description of what's needs to be done here. Please be sure to include the link to the original page
and any supporting links/data.

[ ] Appropriate type-something label has been added.
[ ] Appropriate section-something label has been added.

Not sure what the issue is, maybe you can add some more information?
If you want to see the contributor guidelines, they can be found in CONTRIBUTING.md for Code of Conduct/Community Guidelines they can found in the Google repo; CODE_OF_CONDUCT.md


DRILL-6044: Fixed shutdown button in Web UI when ssl,auth are enabled

Fixed shutdown button to avoid cross domain requests since they are causing some issues when ssl and auth are enabled

@sohami Please review

+1 LGTM. Thanks for making the changes.

+1


All highlights, almost no normal text with TreeSitter highlights

When enabling tree-sitter highlights, almost all the code gets highlighted (mostly blue) and only the ; stays in the normal text color. I joined a screenshot of lua code, but it is the same with python (almost all in blue) and for .vim files it is mostly orange/yellow but still almost nothing in the normal color.

Same issue here;

I have the same issue.

Yeah for some reason this color scheme makes TypeScript look like absolute trash.
This plugin + tree-sitter:

Regular Vim's NeoSolarized on its own:

i hava the same problem

f found is "set termguicolors" in init.vim, treesitter hight is not word

@thmxv should be fixed now.

No, still wall of blue with a bit of orange and still close to nothing in the normal foreground color, for pretty much all the programming  language I use. The only thing I can see different is the variables in lua.
Maybe this is a defect of treestiter or the base solarized theme that just go overboard and cannot decide on what  to (not) highlight.

@thmxv Previously I made only the luaTSVariable as normal. Now I have made TSVariable as Normal can you now?

It is much better now.

If any more changes are needed please do tell. Closing for now.

I still have the wall of blue/green in Golang as the two top screenshots.
And imports and parenthesis are red.
If I can provide more information to fix this let me know.


Route validator redundancy

Description
Removes redundant code from routes.
Adds team and validated user to req body for route access.
Type of change
Please delete options that are not relevant.

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

Change Status

[x] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[x] Tested changes via Insomnia.
[x] Updated existing tests to match new code.

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

 Refactor GET team by id endpoint to not request team data again (it's being requested by validateTeamId middleware).


Bug[mhe]: mhe.GaloisKeyGenProtocol panic

mhe.GaloisKeyGenProtocol.GenShare panics when the auxiliary prime P is empty.

This bug highlights another issue with the absence of auxiliary primes P, namely that some functions
require implicitly their presence or their invocation will result in similar panics. E.g., rlwe.InnerSum uses
the hardcoded RingQP under the hood due to the usage of hoisted automorphisms.


Use total income as income and total-cost-b2b for main plot

Fix #199

updated the income analysis tab plot as well now

Ill Have a look later


Wallet manual tests fixes

Should be reviewed commit by commit.
These fixes bugs found during manually testing the wallet functionality.

Added commit that fixes https://github.com/stratisproject/StratisBitcoinFullNode/issues/2417


can we export more declaration file for us library?

Suggestion

⭐ Suggestion

When I was writing a library, there were three libraries under my namespace. After publishing to npm, when I used my library in the typescript project. the main namespace repository would not report an error when it was used.
import { A } from 'my-library';
...
render(){
  return (<A/>)
}

When using a sub-repository, it will report an error "Could not find a declaration file for module'my-library/libs/js/libsB'"
import { B } from 'my-library/libs/js/libsB';
...
render(){
  return (<B/>)
}

In my library's package.json，I want to set types param a object，but types param is required string.
At present, the type field is set in my package file like this：
{
  ...
  types: 'lib/types/a.d.ts'
}

I see. the following usage may be feasible, but it is not currently supported, I hope to support it in the future:
{
  ...
  types: {
     'my-library': 'lib/types/a.d.ts',
     'my-library/libs/js/libB': 'lib/types/libB/b.d.ts',
  }
}

Grateful！！！

It looks like this is a question rather than a bug report. This issue tracker is for tracking bugs and active work on TypeScript itself, rather than a general forum for programmers using TypeScript to get help or ask questions.
You can ask questions on sites like Stack Overflow. We are not able to provide one-on-one support on the issue tracker. Please read the issue template carefully - it has important information on what kinds of reports can be acted on here, as well as links to useful TypeScript resources. Thanks!

@RyanCavanaugh It looks like it's a feature request for the types field in package.json, though?

it's a question because there is already a solution for it (only for nightly builds) with exports https://nodejs.org/api/packages.html#conditional-exports
like
{
  "exports": {
    ".": {
      "types": "..",
      "import": ".."
    },
    "./libs/js/libsB": {
      "types": "..",
      "import": ".."
    }
  }
}

also he can put the .d.ts files togethers

libs
|- js
|- |- libsB.js
|- |- libsB.d.ts


Streamup.com no longer works?

livestreamer https://streamup.com/nnnnnn best
[cli][info] Found matching plugin streamupcom for URL https://streamup.com/nnnnnn
Traceback (most recent call last):
  File "/usr/local/bin/livestreamer", line 9, in <module>
    load_entry_point('livestreamer==1.12.2', 'console_scripts', 'livestreamer')()
  File "/usr/local/lib/python2.7/dist-packages/livestreamer_cli/main.py", line 897, in main
    handle_url()
  File "/usr/local/lib/python2.7/dist-packages/livestreamer_cli/main.py", line 478, in handle_url
    streams = fetch_streams(plugin)
  File "/usr/local/lib/python2.7/dist-packages/livestreamer_cli/main.py", line 391, in fetch_streams
    sorting_excludes=args.stream_sorting_excludes)
  File "/usr/local/lib/python2.7/dist-packages/livestreamer/plugin/plugin.py", line 313, in get_streams
    return self.streams(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/livestreamer/plugin/plugin.py", line 227, in streams
    ostreams = self._get_streams()
  File "/usr/local/lib/python2.7/dist-packages/livestreamer/plugins/streamupcom.py", line 20, in _get_streams
    url = match.group(1)
AttributeError: 'NoneType' object has no attribute 'group'

Few weeks ago it still worked.
Livestreamer is latest version. I'm not sure if (before the last time I updated/reinstalled it) I was using a modified plugin (streamupcom.py).

Try this version #1206

Thanks. Works.


No longer set or update usage_policy uri

This is inline with current changes to AAF metadata where we no longer want the PublicationInfo/UsagePolicy element to be published.
Requires merge of https://github.com/ausaccessfed/aaf-ansible/pull/714 in the same Ansible run.

Are these test failures legit?

@smangelsdorf what test failures?


DCOS-38544 Add mono to multi zk data migration

Address DCOS-38544

At this point, I made sure the integration tests pass the setup phase and execution phase. The teardown won't be success until https://github.com/mesosphere/dcos-commons/pull/2580 is merged in to this PR.

@jeid64 @nickbp this is ready for review

https://github.com/mesosphere/dcos-commons/pull/2573/commits/b7a31ef653d7eaf9eb20250af568e87bb05e2de6 is the latest set of changes

Thanks for detailed review @elezar Really helps me understand SDK semantics better.
Regarding your comments :

The validity checks for taskResource in TaskResourceMapper and ResourceMapperUtils seem to be executed in a loop while they are invariant. It would be good to know what the motivation for this is.

This seems to be left off code likely from a previous refactoring. I overlooked them while refactoring them from for loops to streams. Cleaned up this check in both the *Mapper classes now.

There seems to be a subtle difference between the MemPersister and CuratorPersister that may cause different behaviours between our tests and running services.

Addressed your comments in detail above but some of the behavior, although inconsistent, it is at-least consistent with the other methods. We can address this in a future clean up if needed.

The expectations around running the update function for a service in our tests.

I created a jira for passing around multi service names in our pytest tooling. https://jira.mesosphere.com/browse/DCOS-39743

Sorry @takirala. Only just saw:

I don't understand (2). Our intention in this test is to make sure there is only ONE task that is relaunched. For the tasks of the foo service, they are new and relaunched does not make sense for them.

We could continue using pop, but we would have to replace this with:
sdk_tasks.check_task_relaunched(config.SERVICE_NAME, 'hello-0-server', [hello_task_id.pop()])

to ensure that we are not comparing with a list of characters internally.


No test output file found!

Please help with this when i run it returned this error log
...l/share/nvim/lazy/neotest-pest/lua/neotest-pest/init.lua:169: No test output file found! Should have been at: storage/app/pest-20240907-230730
Here is my neotest config:
return {
"nvim-neotest/neotest",
optional = true,
dependencies = {
"nvim-neotest/nvim-nio",
"nvim-lua/plenary.nvim",
"antoinemadec/FixCursorHold.nvim",
"nvim-treesitter/nvim-treesitter",
"marilari88/neotest-vitest",
"fredrikaverpil/neotest-golang",
"theutz/neotest-pest",
"olimorris/neotest-phpunit",
},
opts = {
adapters = {
["neotest-pest"] = {},
["neotest-phpunit"] = {},
["neotest-vitest"] = {},
["neotest-golang"] = {
-- FIX: doesn't work when in subdirectory of repo (ex: "sesh/v2/namer")
args = { "-coverprofile=" .. vim.fn.getcwd() .. "/coverage.out" },
},
},
},
this is what my test run look like
test('example test', function () {
---
---
}

I am seeing the same issue when attempting to use this plugin, any assistance would be appreciated.

In my case, the issue was with the sail_enabled function. It was returning true, when it should be false.

That error log almost always means the command to perform the tests didn't actually run successfully, exiting with a non-zero code. Are you able to run your tests separately?
And, are you trying to run via sail or system PHP?


Ownership of Syntex

Now that Serde's code generation is stable and we no longer depend on Syntex, it no longer makes sense for our team to continue owning the Syntex stack.
Please let me know if you would be interested in taking over ownership. If nobody needs Syntex updates so much that they would be willing to run the stack, I think it means we can abandon Syntex and Aster and Quasi.

x-posted to u.r-l.o: https://users.rust-lang.org/t/seeking-new-maintainer-for-syntex/9288

cc owners of <1 month old dependencies on syntex and aster and quasi:

rustfmt: @steveklabnik @nrc
racer: @phildawes @jwilm
bindgen: @emilio @fitzgen @mahkoh @crabtw @nox @Yamakaky
cargo-modules: @regexident
cargo-safety: @alexkehayias
easy-plugin: @KyleMayes
extprim_literals: @kennytm
gdax-client: @KenanSulayman
hypospray_extensions: @jonysy
mockers_codegen: @kriomant
pnet_macros: @mrmonday @faern

@dtolnay can you describe what maintainership of syntex/aster/quasi looks like in practice? Is it mostly un-nightly-ifying code from rustc?
bindgen would be pretty negatively impacted by the loss of syntex.

Yes, though even though bindgen is really dependent on syntax for code generation, I think our need to update syntex is sporadic (i.e., when we need to generate code for something our current syntex version can't, which is rather unfrequent).
I think other projects that use rust code as input (rustfmt comes to mind) could be more affected by this.
I'm happy doing a syntex/aster/etc update once in a while when bindgen needs it for some reason, but I don't think bindgen has as much of a need for keeping syntex/quote/quasi constantly updated compared to other crates.

@fitzgen

can you describe what maintainership of syntex/aster/quasi looks like in practice? Is it mostly un-nightly-ifying code from rustc?

It is exclusively un-nightly-ifying code from rustc and bumping version numbers. Here are some example commits to give you an idea:

https://github.com/serde-rs/syntex/commit/8b40e6d964c25dbc1cc85c9058e9dd6a1844e0a3
https://github.com/serde-rs/syntex/commit/fbedee1569f2b6122ebdfb44be950c97f90b5067
https://github.com/serde-rs/syntex/commit/8759cfe5a61c2e922be62401fe52696a67c5422d
https://github.com/serde-rs/quasi/commit/b7acde7b29c9d7ac6c5c8d2f028a3b6004d9879f
https://github.com/serde-rs/aster/commit/1bfac817c031f309078b6b02f34420c9c9386569

@emilio the thing is, resolving these merge conflicts sporadically in big batches is MUCH harder than resolving them in real time as they happen. So even if bindgen only bumps its syntex dependency very rarely, you still want to have a version of syntex that is based on a relatively recent rustc at all times.

@emilio @dtolnay How hard would it be to migrate bindgen to syn's trees or just quotations?

@nox: I assume it's going to be hardish to migrate to just quotations, since we need something a bit more procedural (though maybe quotations have now support for that?). Mainly, I don't know off-hand (haven't looked to much arguably, aster is nice for that) into how to replace patterns like:
for field in struct.fields() {
    // ...
    builder = builder.with_field(..);
}

I'd had to try to know how hard would be to migrate to syn, but in any case all that is kind of off-topic in this issue.

@dtolnay
Why syntex was dropped at 163d8d6c24144fdd6fd6c79c24d643043f8cf206 and in version 0.59? Personaly I use syntex in my project for macros expansions.
I thought the project stop development, but it is moving according to commit history,
but for some reason drop important parts.

I updated syntex_syntax to Rust 2017-06-01 to use in rustfmt. I did not update syntex because rustfmt does not use it. Rustfmt is going to be moving into the main Rust distro and no longer using syntex_syntax, so you should consider both syntex and syntex_syntax abandoned.

You might want to post syn on the readmee as an alternative.


ci: migrate to GitHub Container Registry

Migrate the container images from DockerHub to GitHub's container
registry.
This pull request also bumps the related Docker GitHub Actions and
makes the source of Fedora's base image explicit.
fixes #60

I believe this is all correct. Note that the Flatpak Builder test can't succeed until the PR is actually merged, because the images aren't available until after.
The worflows use github.actor and github.repository in some places (rather than bilelmoussaoui), to allow contributors to have those images build/push in their forks. This shouldn't pose any problems for the distributed GitHub Actions, though.

So before we actually land this one, I think we should ship one single image that provides the basic tools to build/deploy a flatpak application without any pre-configured remotes. Then flathub could provide a set of images itself that contains the various SDKs combinations that would be built on top of the basic image provided by the actions itself.
We would still document the availabilities of such images in the readme as well as keep the current images up to date for a while, so I would add a new job instead of modifying current ones.
As we moved to the flatpak namespace, i want to keep it clear that flatpak is not tied to flathub and can be used with other remotes if desired.

So before we actually land this one, I think we should ship one single image that provides the basic tools to build/deploy a flatpak application without any pre-configured remotes.

So I guess what you mean is more or less the Dockerfile in the root directory, but basically just a baredbones ontop of fedora:latest?
FROM registry.fedoraproject.org/fedora:latest

RUN dnf update -y && \
    dnf install -y flatpak flatpak-builder python3-aiohttp python3-tenacity python3-gobject xorg-x11-server-Xvfb ccache zstd && \
    dnf clean all

ADD https://raw.githubusercontent.com/flatpak/flat-manager/master/flat-manager-client /usr/bin
RUN chmod +x /usr/bin/flat-manager-client

If so, I can open a PR with a new Dockerfile and workflow that pushes it to ghcr.io. Or did you mean the existing image as-is, just with no SDKs actually installed?

Okay, closing this one in favour of #101.


Suggest another recipe if one is misspelled

$ j instlal
Justfile does not contain recipe `instlal`
(did you mean `install`?)

Fixed by #91


screen size

it appears like i cant resize my screen size of the base designer does this come becouse i am bad or is it the program itself?
still a verry nice program <3

It's the program itself, I was thinking about changing it but I'm no longer maintaining this project because of no time. Size of the whole GUI is hardcoded. Feel free to change it and create a new pull request if you want. Thanks for the support <3


Business Partner KIT Release 23.12 Miscellaneous Acceptance Criteria

Release 23.12 Miscellaneous

[x] Version under Review

Pull request for KIT version under review must be placed minimum one week prior to your reserved Quality-Gate timeslot (to enable formal reviews by relevant BOs, BDAs, DevSecOps System Team)
Prerequisite: IP approval by all companies is available!

Artifact Repository:

Eclipse Tractus-X repo of KIT

Contacts:

Responsible: PO
Review by:

T-X Committer / Project Lead
DevSecOps System Team

[x] Approval of Acceptance Criteria

Product Manager / Business Owner confirms:

All acceptance criteria met (as defined in PI documentation). Relevant evidence is available.

Best Practice:

PO / PCA to obtain BO / BDM OR PM / SA approval prior to Gate review.

Artifact Repository:

JIRA solution Level

Contacts:

Responsible: PO/PCA
Consult: KIT-CONTACT1, KIT-CONTACT2
Review by: BO / BDM (from relevant Domain) OR PM / SA

[x] Test and Approval of Developer Journey

recommended; not mandatory
Business Owner / Product Owner should conduct a case study with at least 1 provider (ideally outside) of the consortium to test the developer journey.

Best Practice:

PO / BO to obtain feedback from case studies prior to Gate review.

Artifact Repository:

Case Study

Contacts:

Responsible: PO/BDA
Consult: KIT-CONTACT1, KIT-CONTACT2
Review by: Case Study Team

[x] Provide change log page in KIT

Each KIT team must provide a KIT-specific release note/change log for developers

Best Practice:

For good practice visit: keepachangelog

Artifact Repository:

Provide change log page in KIT - example

Contacts:

Responsible: PO/BDA
Review by: Release Management

the actual version with all acceptance criterias is available here https://eclipse-tractusx.github.io/docs-kits/next/kits/Business Partner Kit/Adoption View

BO and PO Approval Provided
all points of the Adoption View are accepted @maximilianong

BPDM KIT is approved by BO

Version [3.0.0] -2023-11-02 https://eclipse-tractusx.github.io/docs-kits/next/kits/Business Partner Kit/Changelog/


Add check: Duplicated keys

Example:
# .env

# Wrong
RAILS_ENV=development
RAILS_ENV=test

# Correct
RAILS_ENV=development
RAILS_MAX_THREADS=5

This check should display a message:

.env:2 The RAILS_ENV key is duplicated

I'll take these issue

@quicktour any news on that or are you stuck? Otherwise I would love to try it.


Merge pull request #1 from spring-cloud/master1

11

@lishuai2016 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Please use your own repo for experiments


Add formatting to query viewer data table

Currently, the data table in the query viewer does not contain any data formatting.
Formatting of the values in this table would be helpful so you can see if your formats look as expected before using your query result in a component.
The formats should line up with what is displayed in the <DataTable/> component.
The only exception to this is the column headers - these should not be formatted in the query viewer data table so that they are consistent with the column names generated from the SQL query.
Current query viewer data table vs. DataTable component

Closed by #320


fix: use octokit in getSourceInfo() to prevent "rate limit"

Octokit uses GITHUB_TOKEN to make authenticated request to github.

Thanks for the PR 🙏
I do however like to keep the module as small as possible and seeing octokit adding 6.5mb just to get at the token seems a lot in my mind.
I'd presume you could equally easy read the GITHUB_TOKEN from process.env and add the header in request.js instead.
I think that'd be a neater solution if you'd care to update the PR 😊


ChunkedEncodingError: search may be incomplete

I am getting an error when searching for aspirin in REAL, indicating that it doesn't search in the entire REAL so the code can't find Aspirin:
Python 3.8.16 | packaged by conda-forge | (default, Feb  1 2023, 16:01:55)
[GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import pandas as pd
from smallworld_api import SmallWorld
aspirin = 'O=C(C)Oc1ccccc1C(=O)O'
sw = SmallWorld()
results : pd.DataFrame = sw.search(aspirin, dist=0, db=sw.REAL_dataset)
ChunkedEncodingError: search may be incomplete
results['dist'].values
array([2, 2, 2, 2, 2, 3, 3, 3, 3, 3])

This seems to be a problem on Small World's side, you can check a previous discussion about it in the previous issue #2

The chunking error in SW (not in Arthor) is a concern.
But the aspirin in REAL is weird. And its oddity spills over to Arthor. I have never cared too much to actual enquire or dig deep into.
I first I had assumed Lipinski rules don't play well with it  and then I was told that REAL BB is allegedly not a subset of REAL DB, a misconception I held for a long time.
However, Aspirin (ZINC0053) is in Enamine REAL DB (Z104474430) and Enamine BB (EN300-19606 —$24/g 😆). The e-store link doesn't work as of July 23, but it ought to have.
So my guess is that the fingerprint heuristics struggle to find such an unremarkable compound, that is just a benzene scaffold with a just a carboxylate and a ester. Going one step further, benzoate (O=C(O)c1ccccc1) in Arthor against BB works but it shows what's going on under the hood, with a deluge of bezenyl and carboxyl compounds of diverse sizes...


Issue when downloading pdf file

When I download pdf it doesn't download and brings me to a 404 error link from musecore

Please uninstall any extensions you got from here. Instead, use Tampermonkey and follow the instructions in the new repo, as this repo is no longer updated: https://github.com/LibreScore/dl-librescore


Add sending of "default response" commands as needed

Problem
Right now chipZclSendDefaultResponse in src/app/plugin/binding-chip/chip.cpp is a no-op.  Presumably it should send a default response.
Proposed Solution
The actual sending of the response will presumably need to be handled in the relevant app code.  So I suspect we'll want to remove this no-op function and then fix any apps that stop compiling as a result (e.g. the wifi-echo server) to implement chipZclSendDefaultResponse.
Those implementations will need to do two things:

Encode the actual response into a buffer.  This should be handled by something in CHIP code, ideally.  That is, we should have an API exposed from libchip for doing this.
Send the resulting buffer.  This can use the existing CHIP infrastructure that the echo server already uses.

One issue implementations might run into is how to connect up the callback to chipZclSendDefaultResponse to the right chipZclProcessIncoming callsite.  Can we rely on any calls to chipZclSendDefaultResponse happening before chipZclProcessIncoming returns, so we can effectively handle this via pushing relevant state onto some sort of stack or something?
@tecimovic @sagar-apple @bhaskar-apple

At this point we should do this in the zigbeepro data model bits, not the dotdot ones. @bhaskar-apple @rwalker-apple
Some notes to myself:

The only difference between emberAfSendDefaultResponse and emberAfSendImmediateDefaultResponse (note the extra Immediate) is whether the EmberAfClusterCommand is passed in as an arg (for the former) or is the "current command" gotten via emberAfCurrentCommand (for the latter).  We can consider adjusting the naming accordingly.
The default response might not be sent anyway, for various reasons (e.g. not a unicast command type, the ZCL frame control byte disabled the default response, etc); not sure whether the naming should reflect that.
Need to figure out how to stuff things into a PacketBuffer when all is said and done.


add myself to the contributors.md  list

Hi Luke! Thanks for adding your name! 😄

Thanks for creating this project !  Github repos like this have definitely helped my git skills a lot ✅


Updating Product name with Azure Arc

Updating product name of Azure Arc enabled PostgreSQL Hyperscale to Azure Arc-enabled PostgreSQL Hyperscale

Pull Request Test Coverage Report for Build 948297108

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 42.977%

Totals

Change from base Build 947959889:
0.002%

Covered Lines:
26325

Relevant Lines:
55624

💛  - Coveralls

@nasc17 please remove the changes in XLF and LCL files, they will be generated when my XLF generation function is added to ADS and the changes will be included with the next XLF refresh.

Made new PR: https://github.com/microsoft/azuredatastudio/pull/15845


super-slicer-latest: <IP_ADDRESS> -> <IP_ADDRESS>

Description of changes
Note that without PR https://github.com/NixOS/nixpkgs/pull/194021
Changelog:
https://github.com/supermerill/SuperSlicer/releases/tag/<IP_ADDRESS>
https://github.com/supermerill/SuperSlicer/releases/tag/<IP_ADDRESS>
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

@Moredread Would you mind rebasing to a recent master version? I think everything should build correctly, but there are merge conflicts at the moment.

Have anyone been successful setting up a development environment for it?

@cab404 It worked fine when I tried it in a local commit. Did you have any issues?

Sorry, I've rebased the commit, but hadn't time to build it yet. If you should have success testing it please let me know. :)

@Moredread I've taken the liberty of taking over the update commit in #225817 (also adding the beta version), I hope you don't mind :)


conver yolo to onnx stop at building onnx gragh

i run
python yolo_to_onnx.py -m yolov4-416

and it stop at building onnx graph, and memory is increasing

I have never encountered such a problem.    Are you converting the pre-trained (downloaded) yolov4 model?

I have never encountered such a problem.  Are you converting the pre-trained (downloaded) yolov4 model?

i ran this on Jetson TX2, jetpack4.3
i installed protobuf3.8.0 https://github.com/jkjung-avt/jetson_nano/blob/master/install_protobuf-3.8.0.sh
installed   onnx 1.4.1
ran
./download_yolo.sh

but when i convert pre-trained model
python3 yolo_to_onnx.py -m yolov4-416

it stucked at building onnx graph

it took about 8 minute to finish building onnx model, and   used 30% memory while converting to onnx, is it normal?

As long as the program does not throw an error or exception, I think it's OK.  I have tested my tensorrt yolo code on both Jetson Nano and Xavier NX, but not TX2 yet.  I think it'd work anyway.

thx, i tested yolov3-416.trt on TX2,  about 5.5 FPS


added fwf reader

Address #837
Changes
Changed in pandas extension files
How I tested this
unit tests
Notes
Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.

look good, just pre-commit failure to fix please!

Thanks @swapdewalkar I realized I could easily update the pre-commit fix myself.


BufferableHandle in CallManager and CallBatcher

Internally, CallBatcher has to use BufferableHandle to be able to retry.
BufferableHandle now implements AbstractWriteHandle and AbstractReadHandle.
Thus, CallManager and CallBatcher should require BufferableHandle instead of AbstractWriteHandle.
OutputStreamHandle can not longer be supported, but that's only important for special cases where the data cannot be acquired as an InputStream.

Should remove regressions in the unit test except for the following test, which fails intermittently and may indicate a race condition in the implementation:
com.marklogic.client.test.dataservices.DataservicesPerForestTest#endpointReceivesForestName

Closed.


[WIP] Addition of Exception deriving

See #55 and #58 for reference.
Todo

[x] Add basic exception definition
[x] Add support for custom base exception class
[x] Add support for named constructor with args
[x] Add support for named constructor without args
[x] Add support for default exception message
[ ] Short error message syntax dumping
[ ] Add error when parent class is not throwable
[ ] Write documentation

Is this already finished for review? Tests are failing.

Sorry, nop it's WIP

See also DumpTest::it_throws_exception_when_a_marker_extends_an_exception_type

Regarding DumpTest::it_throws_exception_when_a_marker_extends_an_exception_type, I've simply removed it as there will be no exception type with this PR.

Hey @prolic, I'm thinking about implementing message conversion, aka
'User {{$user}} is not available' => sprintf('User %s is not available', $user->toString())

You mentionned here that something is already implemented and that it could be reused. Could you point me to which part of the lib you were making reference please?

@gquemener See f.e. buildToArrayBody function.

@gquemener It's been a while since you were working on this. Still on it? No hurries, just asking.

Hello,
I've taken some off time in August, I will get back on this PR in September.
I'll give you a full status report at this moment.
Cheers :wave:

Hello,
I've had some time to review the state of this PR.
Apart from the short message syntax and documentation, every else has been implemented (which, I believe, already makes the feature usable).
My suggestion, mainly because I don't have time to take care on the syntax part, would be to focus on the documentation and merge it.
However, @prolic has added a default value feature which impacts this PR.
As a matter of fact, I've extracted the data constructor arguments parsing logic in a reusable function, in order to reuse it for the exception constructor arguments parsing.
The rebasing is not trivial and makes me think about conflict around the exception's ctor $message argument which also has a default value (defined through the _ => 'foo' syntax AFAIR).
Would you mind handling/trying this rebase @prolic?

I try to rebase this branch on the weekend.
On Thu, Sep 6, 2018, 00:04 Gildas Quéméner<EMAIL_ADDRESS>wrote:

Hello,
I've had some time to review the state of this PR.
Apart from the short message syntax and documentation, every else has been
implemented (which, I believe, already makes the feature usable).
My suggestion, mainly because I don't have time to take care on the syntax
part, would be to focus on the documentation and merge it.
However, @prolic https://github.com/prolic has added a default value
feature which impacts this PR.
As a matter of fact, I've extracted the data constructor arguments parsing
logic in a reusable function, in order to reuse it for the exception
constructor arguments parsing.
The rebasing is not trivial and makes me think about conflict around the
exception's ctor $message argument which also has a default value
(defined through the _ => 'foo' syntax AFAIR).
Would you mind handling/trying this rebase @prolic
https://github.com/prolic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prolic/fpp/pull/77#issuecomment-418786743, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYEvAyBzdd-NJYTlufESRj6aQIH6sBQks5uX_YKgaJpZM4VXp7r
.


Distinct ServiceAccounts

The current ServiceAccount name for the controller is controller. This works well while in the cloud-run-events namespace. But we saw in knative/eventing that people wanted to install the controllers and webhooks into user defined namespaces, at which point the name controller is likely to collide.
I recommend cloud-run-events-controller.

This is working as intended.

@Harwayne @n3wscott Is this fixed or won't fix the issue? Is it still an open issue?

This is a design question. My view is that the ServiceAccount names should be moderately unique regardless of which namespace they are in, as I think that in the future it may be common for people to install in non-standard namespaces. @n3wscott prefers the simplicity and brevity of the 'non-qualified' name, because in his view the namespace itself gives all the necessary qualifications.

@mattmoor @vaikas-google This is more of a "best practice" question. Could you resolve this as TLs for knative and comment your decision?

This doesn't seem like a Knative question, given that this is in the "Google" repo.
Having a hard-coded ServiceAccount name seems like a bit of a smell to me. I suspect you want to make this configurable, and then ship with a sensible default with the following priorities:

Not incredibly insecure (e.g. don't ship with a shared secret in code, or permitting unauthenticated read/modify/write for internet-connected components.
Works out of the box for new users.
Easy to understand for people unfamiliar with the system.
Minimum privilege and strong compartmentalization.

You should definitely document how to set up minimum privilege and strong compartmentalization, but I'd design first for a good new-user out of box experience.


fix(TableExpandRow): pass headers value to fix a11y violation

We were experiencing the following violation in a11y testing:

The <td> element containing the expand button was missing programmatic information linking it to a corresponding <th> value in the table head. See this page for more info:
https://aat.w3ibm.mybluemix.net/token/a80a8d09-7f5a-480a-adcc-7e22f77482b0/c19cc7e4-e2e6-4475-89d7-533c2bc34979/archives/2018OctDeploy//doc/w3/help/en-US/idhi_accessibility_check_g1059.html
Changelog
A prop expandHeader in TableExpandRow.js allowing the user to pass a matching id for the corresponding <th> (It seems that the DataTable requires the user to write the <th> elements themselves via children of TableHead.js - Thus, the end-user will need to write a matching id in their table head in order to comply with a11y standards) The expandHeader prop defaults to "expand".
Updated snapshot test for TableExpandRow.js

@joshblack Did you have any further comments...? Thanks!


Code commit for RT-3.1

This Pull Request outdates https://github.com/openconfig/featureprofiles/pull/845 which was coded base_vrf_selection.
Recent PR#1107 changed objective/steps for same test case. this new Pull Request is raised to upload code for PR#1107
https://github.com/openconfig/featureprofiles/tree/main/feature/experimental/policy/policy_vrf_selection/ate_tests/base_vrf_selection
Thanks,
Abdul Zubaidhar .A

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.219%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1181

Relevant Lines:
2064

💛  - Coveralls

@azubaidhar also, if you can, please add support for  deviation ExplicitInterfaceInDefaultVRF
E.g. you can add the following snippet after L125 of your code
https://github.com/openconfig/featureprofiles/blob/57203927ebe87a2c02b4c356e93fbd2f551b4b7c/feature/experimental/policy/policy_vrf_selection/ate_tests/base_vrf_selection/base_vrf_selection_test.go#L125
	if *deviations.ExplicitInterfaceInDefaultVRF {
		fptest.AssignToNetworkInstance(t, dut, i1.GetName(), *deviations.DefaultNetworkInstance, 0)
		fptest.AssignToNetworkInstance(t, dut, i2.GetName(), *deviations.DefaultNetworkInstance, 20)
	}

@xw-g the new version looks good to us, just a few minor comments above.

@azubaidhar can u please address the comments here?

/gcbrun

/gcbrun

/gcbrun

/gcbrun


Make Mobile Nav Shorter

navbar 75px high
logo 60px
You can move the hamburger right as well
.iconHamburgerSSL {
margin-left: 4em;
}
and move up hero text
@media (max-width: 24.375em)
#homepageHeroText {
margin: 6em .5em 0;
}
end result looks like this

@luigicr18 The logo in the navigation is squished. Remove the width requirement (width: 60%;) so you don't force the aspect ratio


Basic serialization and deserialization for storages

This PR adds some basic serialization and deserialization into specs storages. I'm not sure how to go about having a single function call for multiple storages since I would like to avoid dynamic dispatch with serde. This could probably be solved with a macro of some sort, but I'm not entirely sure on how to design it.
In detail:
serde::Serialize is implemented for Storage<T, A, D> so you can just call any method that accepts a serde::Serialize like:
let serialized = serde_json::to_string(&storage);

Deserialization is a bit more complicated since there are a couple of cases where you might want to deserialize into a world:

Adding a scene to the world ontop of the other elements.
Loading the startup scene of the world from data.
Adding an entity prefab of some sort, so only partial loading into the world.

So instead of implementing serde::Deserialize on the Storage<T, A, D> (which would return a new storage and not have a way to make sure the world has the correct entities that correspond to the storage), there is a PackedData<T> struct. The PackedData struct implements serde::Deserialize and contains a list of offsets and components. Offsets correspond to the component list along with a "base".
So if you have a PackedData like so:
PackedData<Comp> {
  offsets: [1, 5, 7],
  components: [ Comp(1), Comp(5), Comp(0) ],
}

Then the offsets mean that the components[0] belongs to the entity base + offsets[0] (or base + 1) and components[1] belongs to the entity base + offsets[2] (or base + 5). By default the base is 0 and can be shifted by the rebase method for PackedData. (This just shifts all the offsets down by the base).
You use this struct to merge into an existing specs storage with the merge method implemented on storages by passing in a list of entities and the packed data.
For instance:
let entity_list = vec![1, 5, 7, 8, 9, 10, 11, 15];
let packed_data = PackedData {
  offsets: [3, 4, 6, 7],
  components: [Comp(1), Comp(2), Comp(3), Comp(4)],
};
storage.merge(&entity_list, packed_data);

This merges the Comp(....) into the entity in the entity_list using the offset as the index. So Comp(1) would be inserted into the storage under the entity 8 and Comp(3) would be inserted into the storage under the entity 11.
If you called rebase(3) on the PackedData then the entities it would merge into would be entity 1 and entity 8 since the offsets would be shifted down by 3.

Cool!
Regarding merging, I'm wondering what would be the optimal strategy to retrieve the amount of required entities to create before merging. It might be useful to add a field containing the number of entities to avoid having to iterate over all offset to find the maximum, or is it required that offsets is ordered?

@msiglreith If you deserialize from a storage the offsets should always be ordered since it just goes through the BitIter. If we want I could add an insertion-sort-esque thing to the deserialization.

Thank you! 🎆 🎆 🎆


WIP: Add gnali wrapper

Add wrapper for gnali
Add a test and necessary test data

gnali repo can be found here

Hi Xia, I think everything looks good so you can resolve the WIP status by removing it from the title.


Release process

Use a GCB build to release a new version of kagglehub both on pypi and in this repo as a GitHub release.
I ran it for 0.1.5:

pypi: https://pypi.org/project/kagglehub/0.1.5/#history
GitHub release: https://github.com/Kaggle/kagglehub/releases/tag/v0.1.5

http://b/314006079

We could add more automation by doing the hatch version $_NEW_VERSION in the build, but that means giving the build access to write to GitHub main branch, but a human would still have to deal with the CHANGELOG so not sure if it's worth it.

We could add more automation by doing the hatch version $_NEW_VERSION in the build, but that means giving the build access to write to GitHub main branch, but a human would still have to deal with the CHANGELOG so not sure if it's worth it.

Agree. Given that we manually update the CHANGELOG for now, let's keep it the way you have implemented it.


Make deployContract Method a Non-Blocking Call

The deployContract method in the ContractFactory currently submits the transaction and waits for it to be processed. This synchronous approach can lead to significant delays, as transaction processing times in a blockchain environment often take several seconds.
Having this method always act as a blocking call is impractical for real-world blockchain environments as it forces developers to wait for transaction completion before proceeding with other tasks.
The deployContract method should only wait for the TX to be processed if the user explicitly chooses to do it. This non-blocking approach should be the default behavior, as blocking the UI is not what users usually desire.

similar to https://github.com/FuelLabs/fuels-ts/issues/2492

Are we talking about adding the awaitExecution flag as a new parameter?
https://github.com/FuelLabs/fuels-ts/blob/dc17b9c454fb025cd07840e79489afe346ff6114/packages/contract/src/contract-factory.ts#L164

@arboleya Yes, we will also need to change the method's response type.
Currently, it returns an instance of the Contract class, ready to be used. This is only possible because the method waits for the transaction to be processed.
The ideal approach would be to have the deployContract method simply submit the transaction and return something that can be used to fetch the transaction, such as its ID or an instance of TransactionResponse. This way, dApp applications wouldn't get blocked when submitting the TX, and they would receive the transaction ID as a response, making it possible to attach hooks to fetch its status.


Wrong documentation in "README.md"

In the code "setOnMapScrollListener" is called "setOnScrollListener"

Can you send a little PR to fix that? The nice thing is: you can do all of it from within your browser. Just hit that edit button while the README.md is open and follow the steps 👍


Cmd-X does not delete/cut the current line

VSCode Version: Code - Insiders 1.6.0-insider (6746e53a611ecb3e0777fca6a4c8387dc392513f, 2016-09-29T06:04:54.045Z)
OS Version: Darwin x64 15.6.0
Extensions: QassimFarid.ejs-language-support-0.0.1, alefragnani.project-manager-0.10.0, bradgashler.htmltagwrap-0.0.3, donjayamanne.githistory-0.0.12, formulahendry.auto-rename-tag-0.0.7, tuxtina.json2yaml-0.1.1, waderyan.gitblame-1.3.0, wcwhitehead.bootstrap-3-snippets-0.0.7, wmaurer.join-lines-0.1.5

Steps to Reproduce:

Cmd-X does not delete (cut) the current line. You have so select the line (Shift-Down) to select and then it Cut.

It's happening from this latest build.

The same on Windows (with Ctrl+X).

https://github.com/Microsoft/vscode/issues/12988


Add a bash or shell script with tool installation commands

This script has to run all commands from README file from the installation section (currently see develop branch):

Install all requirements
Setup environment variables and download Java and Kotlin linters sources

Solved in #155


Microsoft.AspNet.Server.Kestrel.FunctionalTests failures on CoreCLR on Linux

info: Exec
info:   program: /usr/bin/env
info:   commandline: bash -c ". \"/home/cesars/src/aspnet/universe/KestrelHttpServer/packages/KoreBuild/build/dnvm.sh\"; dnvm run default -runtime coreclr test"
info:   workingdir: test/Microsoft.AspNet.Server.Kestrel.FunctionalTests
xUnit.net DNX Runner (64-bit DNXCore 5.0)
  Discovering: Microsoft.AspNet.Server.Kestrel.FunctionalTests
  Discovered:  Microsoft.AspNet.Server.Kestrel.FunctionalTests
  Starting:    Microsoft.AspNet.Server.Kestrel.FunctionalTests
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.ResponseTests.<LargeDownload>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    Microsoft.AspNet.Server.Kestrel.FunctionalTests.ThreadCountTests.ZeroToTenThreads [SKIP]
      https://github.com/aspnet/KestrelHttpServer/issues/232
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      System.Threading.Tasks.TaskCanceledException : A task was canceled.
      Stack Trace:
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      Assert.Equal() Failure
                ↓ (pos 0)
      Expected: 0
      Actual:   1048576
                ↑ (pos 0)
      Stack Trace:
           at Microsoft.AspNet.Server.Kestrel.FunctionalTests.RequestTests.<LargeUpload>d__0.MoveNext()
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
        --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
           at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  Finished:    Microsoft.AspNet.Server.Kestrel.FunctionalTests
=== TEST EXECUTION SUMMARY ===
   Microsoft.AspNet.Server.Kestrel.FunctionalTests  Total: 11, Errors: 0, Failed: 10, Skipped: 1, Time: 901.973s

This affects https://github.com/aspnet/Universe/issues/304.

@cesarbs I was actually abut to close this, since they're now passing on my machine. Are you seeing something different?

Have a look at the latest CI build. There are some Kestrel test failures there.

@halter73 this is one of the high pri fundamentals bugs that Eilon was talking about. Please look into this on Mac and Linux runs on the CI.

Both the KestrelTests and the Kestrel.FunctionalTests projects have been running on Travis over a week with both coreclr and mono. The last 5 Travis builds of the dev branch have passed.
https://travis-ci.org/aspnet/KestrelHttpServer/builds/93789119#L2317
I'm about to manually run the build on OS X.

CoreClr tests are looking good on Yosemite. I also ran the tests on a non-travis Trusty VM and things are good there.

@halter73 All pass on aspnetci as well?

Ubuntu-Universe and Mac-Universe haven't run since 11 days ago.
The last Mac run timed out before reaching the Kestrel tests. The last Ubuntu run timed out during the Kestrel tests.
We have skipped some hanging tests on Mono since the last runs, so I'm rerunning both configurations now. I'll report back once I get new results.

I ran the full Kestrel build with both CoreCLR and Mono tests on our Mac agent twice, and it passed both tests.
I did the same on our Ubuntu agent, and the build hung both times after showing the (successful) result of the Mono test run. We saw this issue a while back, but I hadn't seen it recently on travis until @cesarbs showed me the exact same type of failure happened earlier today.

Full Kestrel builds are once again passing on both the Mac and Ubuntu agents!

Cool, thanks!

At least the last two Ubuntu-Universe failures are due to it hanging in the middle of the Mono Kestrel tests.
After running Kestrel's build.sh in a loop until failure on the ubuntu agent, I am now once again seeing the Mono test hangs. Apparently I didn't catch everything. :(

https://github.com/aspnet/KestrelHttpServer/pull/473 may help with diagnosis; its helped me track down a few issues that didn't exhibit causes because some of the exceptions were getting masked in testing (though still exhibiting the symptoms of going wrong).

@halter73 I believe @cesarbs enabled CoreCLR only agents... do we have 100% in those runs?

The Kestrel repo successfully builds and all the tests pass for the CoreCLR only runs.
This test failed on the last Ubuntu CoreClr run:

Test collection for E2ETests.PublishAndRunTests_OnX86 (1): E2ETests (1)
PublishAndRunTests_OnX86.NonWindowsOS(serverType: Kestrel, runtimeFla…e: x86, applicationBaseUrl: "http://localhost:5035/", noSource: False)
System.OperationCanceledException : Failed to connect, retry canceled.

I'm not sure if this is an issue with Kestrel or publish. I can look into it if it fails again on the next run.

Sounds good, thanks.

I seems the the E2ETests.PublishAndRunTests_OnX86 failure is caused by a TargetInvocationException from ConsoleLoggerProvider.CreateLoggerImplementation. @cesarbs is tracking the fix.


Error  in build-py

CMake Error at CMakeLists.txt:50 (add_subdirectory):
The source directory
/data/llm/code/fastllm/third_party/pybind11

does not contain a CMakeLists.txt file.
-- Found Python3: /usr/bin/python3.10 (found version "3.10.6") found components: Interpreter
CMake Error at CMakeLists.txt:60 (pybind11_extension):
Unknown CMake command "pybind11_extension".
-- Configuring incomplete, errors occurred!
See also "/data/llm/code/fastllm/build-py/CMakeFiles/CMakeOutput.log".

meet with same problem, anyone could help to correct the python api build part?


Layout part should allow a user to drag a row from one grid to another

This currently doesn't seem possible but it would be very useful. Take the scenario where you want a grid in the layout to span the entire width of the page but the row to contain content in the centre of the page. You might like to have alternating colours for each grid and therefore being able to move rows between grids becomes necessary.

Would definitely be good to have. For the time being you can cut and paste elements from one container to the,other using the keyboard.


Actuator API

Actuator API has an impact on gateway performance. With the introduction of spring-boot-starter-actuator, performance has decreased a lot.

I dont see how this has anything to do with Spring Cloud Gateway.  If introducing actuator causes performance problems you should open an issue with Spring Boot.


Remove unnecessary JSON serialization

This fixes the unit tests on Trusty.

https://ocd.appscale.com:8080/job/Daily Build/4617/

Demo:
Unit tests failing without branch: https://ocd.appscale.com:8080/job/Create-Eucalyptus-Image/5731/
Successful build with branch: https://ocd.appscale.com:8080/job/Daily Build/4617/


donation without amount

Hi, is there a way to make a donation button without specifying donation amount?

Okay, we will launch it in a later version, so stay tuned.

Great, thanks.


Error rendering freesurfer regression output in the UI

Describe the bug
Freesurfer Regression output on COINSTAC has an extra (duplicate) t-value.
To Reproduce
Steps to reproduce the behavior:
Please discuss this with @spanta28
Expected behavior
There should be one t-value corresponding to each covariate.
Screenshots

Desktop (please complete the following information):

Got the error snapshot from @spanta28 and @sunithabasodi

Additional context
I tried a similar (maybe not exact data) freesurfer regression in the simulator and I don't see any extra t-value suggesting the error could be on the UI side. (see below for an example)

@spanta28 Please assign this issue to the appropriate assignee. Thanks.

Javier should be able to track it down. I will assign it to him.
On Fri, Dec 16, 2022 at 7:34 PM H Gazula @.***> wrote:

@spanta28 https://github.com/spanta28 Please assign this issue to the
appropriate assignee. Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/trendscenter/coinstac/issues/1610#issuecomment-1355941647,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJKH67TTPHM6VF6QRID5NTWNUKEBANCNFSM6AAAAAATBVE65Y
.
You are receiving this because you were mentioned.Message ID:
@.***>

@pixelsaurus please take a look at this when you get a chance


Added Gemini Pro Vision Support to Self Operating Computer

I've added support for Gemini Pro Vision to the project! To utilize this feature, simply include the command line argument -m gemini-pro-vision. Additionally, I've updated documentation.

@linusaltacc Was working on a similar PR, but there were a lot of issues getting a consistent response. Interested to see how it works with your implementation!

@michaelhhogue Great to hear you were working on the support as well! I'm eager to see your implementation and explore how we can combine insights to enhance the overall solution.

@linusaltacc thanks for the PR. I'm looking forward to checking this out! Have some HyperWrite / OthersideAI priorities to get through, but will try to take a look in a day or two.

@joshbickett  Appreciate your prompt response! Looking forward to your insights and feedback whenever you get a chance to review the PR. Cheers!

@linusaltacc had a bit of trouble getting the credentials setup, but now Gemini is working. I'll do a little more testing and let you know if I have any questions. Thanks! :)

@joshbickett sounds good!

Getting some 500 errors, but that's Google's side of things as far as I'm aware
Error parsing JSON: 500 An internal error has occurred. Please retry or report in https://developers.generativeai.google/guide/troubleshooting

I noticed you added support for -accurate to Gemini, thank you for doing this but I went ahead and removed it. -accurate isn't working as expected right now and it needs an update. I don't think we should support it with new models until it is confirmed to work

@linusaltacc thanks again for the PR. I went ahead and merged it. There was one thing missing, but I didn't think it needed to hold it up. When model is gemini there should be a condition in the summarize function to use gemini to do it. If the user doesn't have an openai key then summarize will fail. If you could make a PR for that, that'd be great.
def summarize(messages, objective):
    try:

Other than that there are a few other changes to make but this is a good start. I'll update the README.md a little to specify more detail about the different model modes.

@linusaltacc do you have a Twitter account? I am happy to mention you in a post about Gemini. Let me know if you want to share you're Twitter once the summary fix is in. You can message me at<EMAIL_ADDRESS>if you prefer

@linusaltacc thanks again for the PR. I went ahead and merged it. There was one thing missing, but I didn't think it needed to hold it up. When model is gemini there should be a condition in the summarize function to use gemini to do it. If the user doesn't have an openai key then summarize will fail. If you could make a PR for that, that'd be great.
def summarize(messages, objective):
    try:

Other than that there are a few other changes to make but this is a good start. I'll update the README.md a little to specify more detail about the different model modes.

@joshbickett Yeah you are right! I'm thinking of adding model as argument to support different models.
def summarize(model, messages, objective):


ifsc-sj-articled:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

A Typst template for articles of the Federal Institute of Santa Catarina.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Hey and thanks for the submission! Before we can get this merged, you'll have to rename the package. ifsc-sj is descriptive for whom this template is for (which is good, keep it as part of the name!) but articled is also descriptive. Template names must contain at least one non-descriptive / creative name component so discoverability is a level playing field. We recommend the naming schema <adjective>-ifsc-sj, see the README for more info.

Hi! Thanks for the heads up.
Updated the new name!

Thank you!


Address Github Security Vulnerabilities

Pull requests into this repository require the following checks to be completed by the submitter and reviewers.
Changes in this PR:
Updated all versions in go.mod files to latest release versions which also updated all dependencies in go.sum files.
Submitter:

[x] Administrative tasks are complete.

This pull request describes why these changes were made.
The JIRA ticket links to this PR.
The JIRA ticket for this PR is: Lantern 406 JIRA ticket

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

[x] Code review has been performed.

Code diff has been done and checked to ensure only expected code is being committed.
A linter for the language has been run.

Primary Reviewer:

[ ] Code works.

Code has been run locally and the basic functionality affected by the PR has been checked.
Edge cases have been checked to ensure behavior is as expected.

[x] Code review has been performed.

Code is maintainable, reusable, efficient, and correct.
Code accomplishes the tasks purpose.
Code follows style guidance appropriate for the language, including passing linter checks.
Code is well commented (which does not mean verbosely commented).

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

Merger:
Prior to merging, ensure that all checks have been completed. Delete the branch after the merge
is complete.

Once this is rebased I'll merge it in!


Multi-user setup on Ubuntu problematic due to lack of wheel group

The instructions at: https://github.com/andrewchambers/hermes/blob/master/doc/installing.md#multi-user-install mention using "wheel" as a group for the value associated with :authorized-group in cfg.jdn.
However, it appears that Ubuntu systems do not have such a group (at least not by default).
The "sudo" group seems to work, but it's not clear yet whether this is an appropriate alternative.

I think the best solution will be init checks if the default group exists, then prints a clear warning if it doesn't.

That sounds like an improvement.

For the documentation, I wonder whether it's better to suggest the creation of a dedicated group (as you mentioned elsewhere) as a default option.

Sure, I just don't want many barriers to multi user install, as I would prefer it to be what people use after they 'try it out' using hermes.

Yes, that makes sense.
It was the path I took as well.


recursive macro clone, CLONENODUP variation

Introduce recursive macro cloning, to easily DEREF imbricated macros.

0 2
<%
  'a' STORE
  <%
    DUP $a > <% $a * %> <% $a + %> IFT
  %> CLONE SWAP DROP
  {
    'a' $a
  } DEREF
%> FOR

Introduce CLONENODUP (name to discuss) to avoid CLONE SWAP DROP (new name to avoid signature variation up to type like CONTAINS)

like there is a CLONEREVERSE, maybe it would be better to introduce CLONEDEREF instead of CLONENODUP

like there is a CLONEREVERSE, maybe it would be better to introduce CLONEDEREF instead of CLONENODUP

I'll be happy to have such a function for all other types... CLONED is also a possible name (let a cloned object on the stack)

Closed because 1 SNAPSHOTN XEVAL does what was intended by this PR.


KQL Validations for Multiple data sources hunting queries

Required items, please complete
Change(s):

fixed the failing kql validations for multiple data sources and other related hunting queries

Reason for Change(s):

failing kql validations

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Hi @vakohl, please check and provide your feedback on this, thanks!

Hi @vakohl, please provide your feedback on this. Thanks

Hi @vakohl, please check and provide your feedback on this. Thanks

Hi @vakohl, please provide your feedback on this. Thanks

Hi @vakohl, please check and provide your feedback on this. @v-vdixit also check for branch conflicts. Thanks

Hi @vakohl,
please check and provide your feedback on this.
Hi @v-vdixit, can you please check for branch conflicts. Thanks

Hi @vakohl , check out the fixes from @v-vdixit. Thanks


Implement stablecoin conversion

Tested in production with the following commands, working as expected.
auth_client.convert_stablecoin(10, 'USDC', 'USD')
auth_client.convert_stablecoin(10, 'USD', 'USDC')

Added a testcase, rebased, and merged. Thank you!


Wave height needs to have half values - 1.5,2.5 etc

Background
After user testing, Charlotte mentioned having half values for wave height.
In scope

[ ] Add 0.5, 1.5, 2.5, 3.5, 4.5, 5.5 as options for wave height field

Tech tasks
Reminders

[ ] Test export script along with import into Access DB and its front end
[ ] Test the app in offline mode to make sure the story works in all scenario
Make sure the following appropriate documents are written up/updated if needed

[ ] Main readme: https://github.com/BMMRO-tech/BMMRO/blob/master/README.md
[ ] App readme: https://github.com/BMMRO-tech/BMMRO/blob/master/app/README.md
[ ] Export script readme: https://github.com/BMMRO-tech/BMMRO/blob/master/export-script/README.md
[ ] ADRs: https://github.com/BMMRO-tech/BMMRO/tree/master/architectural-decision-records
[ ] Operating manual  - https://docs.google.com/document/d/1zFzHcWEdO8jby3W6a9eV5IuKUfDRd62f9-HU9lqdm5Q/edit

Looks Done:


Compilation failure of tornado-drivers-ptx

Describe the bug
When executing steps to install TornadoVM on Windows from here, I get a compilation error from one of the TornadoVM modules.
How To Reproduce

Follow instructions 1 through 5 from here (I did look at the known issues and started with a fresh MSYS2 installation).

When compiling using the mingw64 terminal with the following command:
source etc/sources.env make graal-jdk-17-plus BACKEND=ptx
A compilation error arises (see this gist for the stack trace/log output)

Expected behavior
Successfull build of TornadoVM (step 6 in the instructions)
Computing system setup (please complete the following information):

OS: [Windows 10]
PTX:  cuda_11.7.r11.7/compiler.31294372_0
Nvidia Driver: <IP_ADDRESS>14
TornadoVM Commit ID: 9158641
JDK: 17
Maven: 3.9.4

Additional context
The full log output of the build can be found here.

hi @PolyRocketMatt, can you please also provide the JDK version that you downloaded for your JAVA_HOME?

Updated the original post with that information, as well as the version of Maven I am using.

The JDK17 binary breaks in Windows. My guess is that the link pointing to the JDK17 is not compatible with the latest Graal 23.1.0 compiler update that we performed recently. We will validate it, and report any updates here. In the mean time, the JDK21 binary seems to be working.

There is no Graal 23.1.0 for JDK 17, only for JDK 21. We will update the docs.

I just double-checked on Windows 11 and MSys64.  It works for JDK 21 and GraalVM.
Just for reference, here's my source file:
#!/bin/bash
export JAVA_HOME="C:\Users\jjfum\Documents\bin\jvms\graalvm-jdk-21_windows-x64_bin\graalvm-jdk-21+35.1"

## NEXT TWO LINES NECESSARY TO BUILD PTX (NVIDIA CUDA) BACKEND
## COMMENT THEM OUT OR JUST IGNORE IF YOU ARE NOT INTERESTED IN PTX BUILD
## OTHERWISE UPDATE 'CUDA_PATH' WITH ACTUAL VALUE (REMEMBER OF UNIX_STYLE SLASHES AND SPACES!!!)
export CUDA_PATH="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v12.1"
export PTX_LDFLAGS=-L\"$CUDA_PATH/lib/x64\"

# LEAVE THE REST OF FILE 'AS IS'
# DON'T ALTER!
export PATH=$PWD/bin/bin:$PATH               ## This directory will be automatically generated during Tornado compilation
export TORNADO_SDK=$PWD/bin/sdk              ## This directory will be automatically generated during Tornado compilation
CMAKE_FILE=$(where cmake | head -n 1)
export CMAKE_ROOT=${CMAKE_FILE%\\*\\*}

Then:
source sources.sh
make BACKEND=ptx
make graal-jdk-17-plus BACKEND=ptx

You can also build with the OpenCL backend.

@PolyRocketMatt , did you get the chance to test it again? Did this solve the issue?

I did. Building now seems to work, but even with a fresh install and all it seems like the tornado command is not recognized (even though building everything seemed to be succesful).

Hi @PolyRocketMatt . sorry I missed the last message. Did it finally work?
If it builds, then the issue could be the PATH to the TornadoVM bin folder ($TORNADO_ROOT/bin/sdk/bin)


custom param on my data

Hi authors, i want to custom param on my data, you can help me? Th

Please read the documentation and response to the Github discussion #91


Add postMessage to Programming Interface

When we want to use programming interface to auto run some command for user, we encountered issues when main site and ttyd site are host under subdomains.
for example:
we run a web site that helps show some useful debug commands, under a.com, with one ttyd iframe using sub domain: ttyd.a.com.
when one clicks debug command at a.com's page, we want to auto pate and run inside ttyd.a.com's iframe, but there shown errors:
Blocked a frame with origin "https://a.com" from accessing a cross-origin frame.
    at <anonymous>:1:68
(anonymous) @ VM202:1

So wish there have some postmessage programming interface to communicate to ttyd pages to just run some limit commands like paste&run command.

I'm OK to merge a PR for this feature, If you know how to implement it.


Query duplication

Version
3.7.0
Summary
Hello, when I click action button,  network debugger shows 50 outgoing requests are sent to our server.
I noticed existing issue that was closed long time ago, not sure if things have changed. https://github.com/apollographql/apollo-kotlin/issues/646
    @Inject
    @AuthenticatedClient
    internal lateinit var apolloClient: ApolloClient

    private fun onActionButtonClicked() {
        for (i in 1..50) {
            disposables.add(
                apolloClient.query(
                    OffsiteQuery(
                        url = "https://thesassyowlboutique.com/products/hearts-aflutter-skort?variant=39947075715150"
                    )
                ).fetchPolicy(FetchPolicy.CacheFirst).rxSingle()
                // Ignore the result since this is just a prefetch
                .subscribe(Functions.emptyConsumer(), Functions.emptyConsumer())
            )
        }
    }

Unrelated, with our REST Retrofit Repository implementation, it only fetches from server once.
@Inject
lateinit var urlInfoRepository: UrlInfoRepository

private fun onActionButtonClicked() {
    for (i in 1..50) {
        disposables.add(
            urlInfoRepository.getUrlInfo(
                "https://thesassyowlboutique" +
                    ".com/products/hearts-aflutter-skort?variant=39947075715150", "1059401512322041701", null
            )
            .subscribe(Functions.emptyConsumer(), Functions.emptyConsumer())
        )
    }
}

Hi!
There is no mechanism as of today to do this in Apollo Kotlin. Issue #646 is closed but we issue #3760 can be used to track this.
Thanks for the heads up about Retrofit, I wasn't aware that it had such a mechanism, I'll have a look.
I am assuming this only works for GET though? I can imagine scenarios where you actually want to execute several identical POSTs on the same resource even if one is already ongoing. For GraphQL I think this would only be allowed to work on queries, not mutations.

@BoD Hi Sorry for confusion, the dedup mechanism is from our own Repository implementation, not Retrofit. Basically we cache a Map<request, Observable>. If our code calls Repository.get(url) multiple times with same url, the map will retrieve the same observable.

Ooh right! Thanks for clarifying. I guess this could also work on top of Apollo?

We are using Apollo store as cache and ridding off our own repository implementation.
Sent from my iPhone
On Jan 4, 2023, at 1:48 PM, Benoit Lubek @.***> wrote:

Ooh right! Thanks for clarifying. I guess this could also work on top of Apollo?
—
Reply to this email directly, view it on GitHubhttps://github.com/apollographql/apollo-kotlin/issues/4604#issuecomment-1371293735, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AANZ66T5XFH4L57N7CDX2ZLWQXAXBANCNFSM6AAAAAATRBWFWM.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks for clarifying! Is it ok to close this ticket in favor of #3701?

For sure thank you!


This page is blank

Page: /setup/monitoring/datadog/
Feedback:
Throw me a frickin' bone here.
https://i.chzbgr.com/original/5899996672/hE10A9408/1

bone has been thrown, by datadog themselves I believe! https://www.spinnaker.io/setup/monitoring/datadog/


edit newsletter

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
i want to edit the footer section from

to

Use Case
would improve the project's functionality, making it more user-friendly and efficient for solving user needs.
Benefits
The advantage of enhancing features is that it makes the project more appealing, efficient, and better suited to meet user expectations
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

i think, no need.