[Java][Suggestion] Add Enum with all Operations

Currently it is hard for beginners to start with the Java API of TF. Mostly because the function names staed in the python tutorial do not apply to the Operation names used in Java. It would be nice if we had an Enum Containing all standart possible Operations.
grapth.opBuilder(type, name)
I am currently struggling to find out what the correct name of "Multiply" is.
I have digged my way thorgh the code and most of the operations are registered trought REGISTER_OP and I could trace down the java methods to  TF_OperationDescription(TF_Graph* g, const char* op_type, const char* node_name) in c_api_internal.h. But I absolutly dont know were the operations are storred.
Also nice would be a table "python function name" to "internal operation name"

Given that attribute names may also generally differ, the only "principled" way to do this would be to either automatically generate code for constructing ops (which can be ugly) or manually add functions that create all supported ops. The Python API currently uses a mixed approach. If you can be a little patient, I have been working on a Scala API that does that and adds a lot more of the Python API functionality (e.g., gradients). It's not ready to be released yet, but I will have a usable version soon. It is written Scala though and uses some "Scala-specific" features, but it shouldn't be hard to create a Java compatibility layer then.

ohh that would be great. It is currently realy annoing to not know what op names are. for example I could not find anything what "tf.global_variables_initializer" would be in java.

@asimshankar for Java.
The variables etc are registered in the graph. You'd need access to the collections from the Graph class, I believe.

As @eaplatanios pointed out, I don't think that an enum would be appropriate and code generation for all the operations (which happens for Python, C++ and Go right now) is the right way to go.
I believe @karllessard and @kbsriram are looking into this as part of resolving #7149, so I'm going to close this issue out and recommend comments/follow ups on #7149 instead.
Thanks!

But the method solution is much more complex and enums are the right way to do it, like OpenGL does it.

An enum might describe the list if operations, but we'd still need to describe all the inputs, their types, any attributes, default values - essentially all the contents of the OpDef protocol buffer that is created with the REGISTER_OP macro calls, so merely listing out the operations without describing how to use them seems insufficient, no?

well enum cann do this in java do (we can give them an input definition as DataType array) and the Exceptions are helpfull so the hardest thing currently is guessing the name, if you have the name the excpetiuons tell you what you need.

I do believe that the code generation is the appropriate thing to do regardless, but yes, it will take time.
I'm not fully convinced about the value of the enum. Yes, it may help with discovery of operations, but once the code generation is in place, then that would be a better means of discovery? Note that operations can also be added at runtime (e.g., Adding a New Op), so the enum will not be sufficient.
That said, one minor change seems to be a pre-requisite for discovery whether using code generation or an enum. That would be to make  TF_GetAllOpList available in the Java API, the output of which can be parsed into an OpList Java object.
I'd be happy to add that. With it you should be able to generate your own enum if you want and if after using it you still feel convinced that it is appropriate, we could discuss the possibility of merging it in.
Sound fair?

Ok if you will add all this stuff then yeah the enum is pretty out of place and not needed. With alot of bloddy magic it is possible to add enum at runtime but a solution wiht methods is by far better.


Remove "symptoms" column

Background
We've consistently heard from users that the symptoms column is not valuable to them. The symptoms column as it stands creates data clutter and should be removed.
Action requested
Remove the symptoms column.
Acceptance Criteria
What needs to happen for this ticket to be complete?

A/C: Symptoms column should be gone from the results table.


[ViewModelWidget] [Mockito] | widget is not rebuilt after tester.pump()

Hi,
I have a small issue trying to test ViewModelWidget with mocked ViewModel via mockito. Unfortunately, build is not called on every pump.
setup:
widget:
class EmailSection extends ViewModelWidget<AuthViewModel> {
  EmailSection() {
    print('ctor');
  }

  @override
  Widget build(BuildContext context, AuthViewModel model) {
    print('build');
    return Container();
}
}

test file:
Future<void> createWidget(WidgetTester tester, AuthViewModel model) async {
  await tester.pumpWidget(ViewModelBuilder<AuthViewModel>.nonReactive(
    viewModelBuilder: () => model,
    builder: (context, model, _) => MaterialApp(
      home: EmailSection(),
    ),
  ));

  await tester.pump();
}
@GenerateMocks([AuthViewModel])
void main() {
  var authViewModel = MockAuthViewModel();

  setUp(() {
    resetMockitoState();
    authViewModel = MockAuthViewModel();

    when(authViewModel.isBusy).thenReturn(false);
    when(authViewModel.isLogin).thenReturn(true);
    when(authViewModel.username).thenReturn('username');
    when(authViewModel.email).thenReturn('test@test.com');
    when(authViewModel.password).thenReturn('12345678');
  });

  testWidgets('test', (WidgetTester tester) async {
    await createWidget(tester, authViewModel);
    await createWidget(tester, authViewModel);
    await createWidget(tester, authViewModel);
    await createWidget(tester, authViewModel);
    await createWidget(tester, authViewModel);

    final widgetFinder = find.byType(EmailSection);

    expect(widgetFinder, findsOneWidget);
  });
}

In this case, I'll have only one 'build' in the console, but several 'ctor'.
if I'll add a unique ValueKey to createWidget, it will work:
var q = 0;
Future<void> createWidget(WidgetTester tester, AuthViewModel model) async {
  await tester.pumpWidget(ViewModelBuilder<AuthViewModel>.nonReactive(
    viewModelBuilder: () => model,
    key: ValueKey(q++),
    builder: (context, model, _) => MaterialApp(
      home: EmailSection(),
    ),
  ));

  await tester.pump();
}

After this change, I have 5 'build' in the console. But I feel that I'm doing something wrong. Could you please suggest how to omit adding ValueKey during test?

@Kp0c you're not doing something wrong. Sometimes flutter cannot determine if a widget has changed and doesn't swap it out in the element tree. The way to fix that is to supply unique keys. You'll see this in development as well when you have a list view that you update dynamically. The list item won't update regardless of calling setstate because the list view builder determines it hasn't changed. The way we fix that is by adding a unique key for each item.
So what you're doing is fine. I don't have any UI tests (like this) but I don't see anything wrong with your implementation.

Thank you for the response. I thought that this elements-optimization thing is a root cause, but felt weird doing that ValueKey hack. But if someone much more experienced in Flutter says that it is fine, then I'll close that 😸


chttp cannot be compiled under arch linux.

I have openssl installed and both libssl.so.1.1 and libssl.so.1.0.0 under /usr/lib folder
here is the demo project to replicate the problem.
When i compile this in a docker container with ubuntu it compiles however in arch linux which is my only os installed i cannot compile it

Hmm, I have been hearing about various issues compiling with OpenSSL under some distros. Since the error message references the psl crate, try compiling again with the psl feature disabled and let me know if you get any farther. I'll get a Docker image based on Arch set up as a test case.
If this is somehow caused by the psl crate, then you might be glad to hear that this will no longer be a dependency in the next chttp version. (This wouldn't be the first problem it has caused.)

could you please guide me through how to disable the psl feature @sagebind ?

I have not been able to reproduce this so far. I spun up a Docker container using the archlinux/base image, installed both openssl and openssl-1.0 packages, and compiled the linked example with no trouble (other than fixing a missing semicolon in main.rs).

psl is no longer a dependency, so I am assuming that this is no longer a problem.


Add option to toggle theme style (dark/light)

Implemented #113, using the theme toggler functionality from bootstrap 5.3 (https://github.com/search?q=repo%3Atwbs%2Fbootstrap bd-theme&type=code).
Video:
https://github.com/user-attachments/assets/8bc89ae3-6647-4094-8e2e-9e7b3a662090
Image:

Moved also the implementation of the language picker to the same style

Additionally:

removed some unused files
added translations

Pending adjustments:

[x] add theme configuration
[x] improve mobile spacing
[x] add upgrading steps (as I combined some CSS files)
[x] review impact on theme size/performance
– potential followup: load only some bootstrap files instead of the whole thing: https://getbootstrap.com/docs/5.3/customize/sass/#variable-defaults
[x] feedback

Looks awesome @zetxek :)

In terms of performance it seems there's no impact. We're good:
Mobile:

Desktop:

The SEO decline is just because we're using the preview URLs in vercel to test (https://adritian-demo-git-theme-update-update-theme-7a59da-adrianmoreno.vercel.app/?vercelToolbarCode=A1_o93MWTpyHAW0#, from https://github.com/zetxek/adritian-demo/pull/115)
So it seems we're quite good. I'll test a bit more in mobile tomorrow (in a real device), and if it goes well we can ship this to a new release :)

I have tested in my local site and works great, good job! I left some comments in the PR in specific files just for let you know ;)
Great work @zetxek

I have tested in my local site and works great, good job! I left some comments in the PR in specific files just for let you know ;)
Great work @zetxek

I love the comments! Ideally the theme is both usable "as-is" and extensible for other usages - many times when I'm implementing things i think "would anyone else use it like this?". So the feedback is super appreciated 🙌

I found a bug: the icon for the theme switcher should switch to the active one. It stays always in the ☀ one.

I found a bug: the icon for the theme switcher should switch to the active one. It stays always in the ☀ one.

Ah, of course. When I tested it, it seemed to be working as it should.

I got this one right now :)

It switches properly, it changes color if the theme is changed, and the language and theme selectors are consistent in styling.


Your app is having trouble loading the st_aggrid.agGrid component.

I am using AgGrid 0.0.7 , streamlit v0.73
Your app is having trouble loading the st_aggrid.agGrid component.
(The app is attempting to load the component from , and hasn't received its "streamlit:componentReady" message.)
If this is a development build, have you started the dev server?
If this is a release build, have you compiled the frontend?
For more troubleshooting help, please see the Streamlit Component docs or visit our forums.
this happen when i use call the aggrid function:
gb = GridOptionsBuilder(min_column_width=100, editable_columns=False, side_panel=False)
    gb.build_columnsDefs_from_dataframe(input_df) #take df as parameters
    gridOptions = gb.build()

    st.markdown("""
    ## Details#
    """)

    grid_response = AgGrid(input_df, gridOptions=gridOptions, height=500)

    input_df = grid_response['data']

and it seems i continously call the function but i cannot find the
"streamlit:componentReady"** message location. can you givve an hints>

update to latest version with pip install streamlit-aggrid --upgrade.

update to latest version with pip install streamlit-aggrid --upgrade.

I am facing the same issue:
Your app is having trouble loading the st_aggrid.agGrid component.
(The app is attempting to load the component from , and hasn't received its "streamlit:componentReady" message.)
If this is a development build, have you started the dev server?
If this is a release build, have you compiled the frontend?
Upgrading via "pip install streamlit-aggrid --upgrade" to streamlit-aggrid 0.1.7 didn't help. Please suggest.

I am facing the same issue:
Your app is having trouble loading the st_aggrid.agGrid component.
(The app is attempting to load the component from , and hasn't received its "streamlit:componentReady" message.)
If this is a development build, have you started the dev server?
If this is a release build, have you compiled the frontend?
Upgrading via "pip install streamlit-aggrid --upgrade" to streamlit-aggrid 0.1.7 didn't help. Please suggest.

I am facing the same issue.
streamlit           0.76.0
streamlit-aggrid    0.1.9

Same issue also here with
streamlit==0.82.0
streamlit-aggrid==0.2.1

I still face this issue
streamlit==1.7.0
streamlit-aggrid==0.2.3.post2

Did anyone manage to resolve this issue?

I had this issue when deploying on Google Cloud Run also.
Upgrading the machine with more RAM solved the issue for me.
with 512 mb memory I was experiencing this issue. No longer seeing this issue with the container memory set to 2Gb

I had this issue when deploying on Google Cloud Run also.
Upgrading the machine with more RAM solved the issue for me.
with 512 mb memory I was experiencing this issue. No longer seeing this issue with the container memory set to 2Gb

It seems more like a connection speed issue. With good WIFI, I don't have the issue. This is discussed here.


How to configure with SystemJS?

Getting this error when importing using SystemJS:

This is my SystemJS:
(function (global) {
    System.config({
        paths: {
            'npm:': 'libs/'
        },
        map: {
            ....
            'ngx-popper': 'npm:ngx-popper'
        },
        packages: {
            ....
            'ngx-popper': {
                main: 'index.js',
                defaultExtension: 'js'
            }
        }
    });
})(this);

I've also used Gulp to copy index.js, popper.js, popper-content.js, popper.model., and popper.module.js from node_modules directory to my project's libs folder.
My Gulp file:
gulp.task('restore:ngx-popper', function () {
    gulp.src([
        'node_modules/ngx-popper/src/*.js'
    ]).pipe(gulp.dest(libs + 'ngx-popper'));
});

What's wrong I'm doing?

Okay, I solved it by importing Popper.JS too in the similar way as above.
But now I'm getting another error while importing NgxPopperModule in my module file.

import { NgModule } from '@angular/core';
import { NgxPopperModule } from 'ngx-popper';

@NgModule({
    imports: [
...
        NgxPopperModule
    ],
    declarations: [
...
    ],
    exports: [
...
        NgxPopperModule
    ],
    providers: [
...
    ]
})

export class CoreModule { }

I have no experience working with SystemJs, from the error it seems the NgxPopperModule is not getting imported properly hence the "undefined".
if you can supply a demo page I can try looking into it.

Hey, Thanks for the reply.
See the issue was that index.ts file was not importing popper.module file and popper.js file. So to solve this I needed to explicitly tell SystemJS to load these two files, which usually does not happen.
(function (global) {
    System.config({
        paths: {
            // paths serve as alias
            'npm:': 'libs/'
        },
        // map tells the System loader where to look for things
        map: {
            ... ,
            'ngx-popper': 'npm:ngx-popper',
            'popper.js': 'npm:ngx-popper',
            'popper.module': 'npm:ngx-popper',
        },
        // packages tells the System loader how to load when no filename and/or no extension
        packages: {
            ... ,
            'ngx-popper': {
                main: 'index.js',
                defaultExtension: 'js'
            },
            'popper.js': {
                main: 'popper.js',
                defaultExtension: 'js'
            },
            'popper.module': {
                main: './popper.module.js',
                defaultExtension: 'js'
            }
        }
    });
})(this);

Its better if you just figure it out how to do it directly, i.e. without the users of library to do it explicitly.
This solved this issue.. Thanks.
I'm having some other issue too.. I'm trying to solve it.. Will as for your help if needed. :)

Let me know if you need anything else,
Ill add this to the docs.
Thanks1


Fix repository links in package.json

URLs for the repository referred to https://github.com/sharedstreets/sharedstreets.js/, which resulted in broken links when trying to reach the repository from the npm package page at https://www.npmjs.com/package/sharedstreets. This will hopefully fix this problem on your next publish.

Thanks @louh!


Shouldn't we rewrite API so that value is returned in first resolve?

If we're using async/await, it's not so clean to implement this.

For example, if the value is cancelled, we would need to wrap in a try/catch, but you don't reject the promise it seems.


Extension needs to listen to LS telemetry

It appears that all the LSP message telemetry/event does is to fire event back on the extension which then should be submitting telemetry to the VS Code API.

FWIW it'd be good to know if there's some specific schema that this event needs to be providing to mesh with the telemetry that the extension is already sending. The LSP spec defines the telemetry event to just include an arbitrary object, so if there's a specific format needed in practice that'd be great to know.

@jakebailey - AFAIK it is
        /**
         * Sends a telemetry event
         * @param {string} eventName The event name
         * @param {object} properties An associative array of strings
         * @param {object} measures An associative array of numbers
         */
        // tslint:disable-next-line:member-access
        public sendTelemetryEvent(eventName: string, properties?: {
            [key: string]: string;
        }, measures?: {
            [key: string]: number;
            // tslint:disable-next-line:no-empty
        }): void;

Event name will be 'Microsoft Python Language Server'. Data then can be either string or dictionary.

The event name might need to be more specific. Take the bit that actually starts the language server:
https://github.com/Microsoft/vscode-python/blob/a14db37b4375cbbd109cb40b8e0c91652cfbf8f9/src/client/activation/languageServer/languageServer.ts#L164-L173
and the constants:
https://github.com/Microsoft/vscode-python/blob/a14db37b4375cbbd109cb40b8e0c91652cfbf8f9/src/client/telemetry/constants.ts#L35-L41
But we can definitely upgrade from object to something like this (not final):
[Serializable]
struct TelemetryEvent {
	public string eventName;
	public HashMap<string, string> properties;
	public HashMap<string, int> measures; // TS "number" is more than just int, though.
}


Prevent user input that is not divisible by the step value (modulus 0)

If we let users enter typed input and there is a step, should we be validating their typed input?
Not doing so allows them to circumvent the step.
If component is stepped:
    Valid typed user input is:
        Numbers that are a result of X increments/decrements of step (from initial value) / modulus 0
        e.g. Typed Input: 2.25, Initial Value: 1, Step: 0.25, Increments: 5 / (2.25 % 0.25 === 0)

This is probably app layer stuff. And should be handled by downstream consumers own validation. Closing.


[html / javascript] Create a dynamic view for employee availabilities

In src/restaurant.html it would be nice to view a week at a time, similar to Google calendar, showing hours and color coded sections showing when they would like to work, could work, prefer not to work, and not available to work.
Then have controls that would allow you to go forward and backwards a week at a time.
The javascript logic can be stored in src/ui.
The data right now is just dumped raw. Instead it can be dumped into a javascript section in src/restaurant.html

I'm thinking the javascript may also come in handy when we are visualizing the shifts for GMs

The current data being dumped looks like this:
day_of_week: 0 start: 2021-12-31 00:00:00 end: 2022-12-31 00:00:00 earliest: 540 latest: 1020 priority: 1.0 note: None
day_of_week: 1 start: 2021-12-31 00:00:00 end: 2022-12-31 00:00:00 earliest: 540 latest: 1020 priority: 1.0 note: None
day_of_week: 2 start: 2021-12-31 00:00:00 end: 2022-12-31 00:00:00 earliest: 540 latest: 1020 priority: 2.0 note: None
day_of_week: 4 start: 2021-12-31 00:00:00 end: 2022-12-31 00:00:00 earliest: 540 latest: 1020 priority: 3.0 note: None```

Where day_of_week 0=Monday, earliest and latest are the number of minutes since midnight, and priority 1=want to work, 2=could work, 3=prefer not to work, 4=cannot work. Note may be None or may be notes the the scheduler for more information.

So basically what functionality want to add?

Take the data shown in the comment above and use javascript to create a table showing days of the week and hours of each day and showing what times people can work, cannot work, etc. Kind of like week-view in Google Calendar.

To have more of a visual, something like this

:

It doesn't have to be exactly like the above, but I would like to map the data to a visual presentation something like the above

Sir I wanted to ask you one thing that how can I be good at coding the
logic because I think I am lacking something?
Please help me out.
On Mon, Jan 3, 2022, 3:26 AM Marc Page @.***> wrote:

It doesn't have to be exactly like the above, but I would like to map the
data to a visual presentation something like the above
—
Reply to this email directly, view it on GitHub
https://github.com/marcpage/scheduling/issues/53#issuecomment-1003781503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT7PRYYQ6OBFTPJ6JCJNBV3UUDCZZANCNFSM5LBWRL5A
.
You are receiving this because you commented.Message ID:
@.***>

Is there any way we can connect it directly with Google Calendar?
On Mon, Jan 3, 2022, 3:07 AM Marc Page @.***> wrote:

Take the data shown in the comment above and use javascript to create a
table showing days of the week and hours of each day and showing what times
people can work, cannot work, etc. Kind of like week-view in Google
Calendar.
—
Reply to this email directly, view it on GitHub
https://github.com/marcpage/scheduling/issues/53#issuecomment-1003779233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT7PRYZPPC72LHXW3VTICH3UUDARLANCNFSM5LBWRL5A
.
You are receiving this because you commented.Message ID:
@.***>

Not in an easy way. This is availability, which we would not want to clutter their personal calendar. For shift scheduling we can have a calendar they can add to Google calendar. We also don't want to require them to have a Google account.


"Are you sure you want to leave?" is asked even for search queries

Gitea version (or commit ref): 43fc430

Description
Gitea uses jquery.are-you-sure to help users not lose data when they have edited a form. This is currently done on every form, see here. On inputs such as search queries, popping up this dialog seems both annoying and may cause needless what-did-I-do-wrong stress.
Reproduce
Go to any page with a search bar. Type some letters in the search query. Navigate to another page (without searching). You'll get a prompt asking if you are really sure about leaving this page.
Possible solutions
Either:

tell jquery.are-you-sure to ignore the search query inputs (and possibly other unimportant fields) by adding class="ays-ignore"
or the other way around, add a class to all forms that do need to be warned about when modified, and enable areYouSure only for forms of that class.

Any preference for either solution?

Best solution would probably be to add ignore, that would be more error prone also in future

@lafriks PR #3707 implements the solution that makes ignoring explicit.
Slightly different from what I proposed, I ended up adding a class ignore-dirty to the forms, instead of adding ays-ignore to every input.


File Sharing: Initial changes for showing uploaded files in sendbox

What
Initial changes for showing uploaded files in sendbox
Why
https://skype.visualstudio.com/SPOOL/_workitems/edit/2671570
How Tested
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

@prabhjot-msft  Could you also add a couple of screenshots in the PR description to show how this implementation looks in the chat composite?

Failed to pass the UI Test. If this PR is for UI change and the error is snapshot mismatch, please add "ui change" label to the PR for updating the snapshot.

Since this PR changes the chat composite UI, you will need to add the ui change label to this PR. @prabhjot-msft

UI Snapshots show that unneeded height is being added to the sendbox

We should not add extra height to the sendbox unless files have been attached


[WIP] Migration for the sendTiming events for package:unified_analytics

Related to tracker issue:

https://github.com/flutter/flutter/issues/128251

Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I believe this analysis error is unrelated to your change and fixed upstream:
Analyzing Á flutter sdk...

  error • 'FakeView.render' ('void Function(Scene)') isn't a valid override of 'TestFlutterView.render' ('void Function(Scene, {Size? size})') • packages/flutter/test/widgets/multi_view_testing.dart:20:8 • invalid_override
  error • 'FakeView.render' ('void Function(Scene)') isn't a valid override of 'TestFlutterView.render' ('void Function(Scene, {Size? size})') • packages/flutter_test/test/multi_view_testing.dart:20:8 • invalid_override
   info • Place 'package:' imports before relative imports • packages/flutter_tools/lib/src/commands/packages.dart:22:1 • directives_ordering

@christopherfujino ah i see, thanks, i was wondering why it kept coming up

This PR was reverted due to Google3 updates that need to be made:

#139278


⚠ AsianCinema has degraded performance

In 3d4b574, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 3100 ms

Resolved: AsianCinema performance has improved in b0c167d after 13 minutes.


types updated

RegExpExecArray | null
string[]

Why is this necessary?

Because my compiler generates errors like:

Type 'RegExpExecArray | null' is not assignable to type 'RegExpExecArray'.
Argument of type 'string' is not assignable to parameter of type 'never'.

The changes should not break the existing code and will rather make the code more understable.
I think it would be good to add this additional type-information :)


Extract config parsing out of PAL

This commit updates the Bolt::PAL class to take the whole Bolt::Config object
as a single parameter rather than taking options from config as seperate
parameters.
As part of the change, the functionality of munging the modulepath to include
BOLTLIB and built-in content has moved to a read-only function in the Config
class.
All of the inputs to PAL came from config already, and this distinction -that
PAL just takes config as one object- helps define how tools that use bolt as a
library (like PE) should use and extend bolt for their needs. Specifically
this change helps other tools use Bolt without needing to redefine PAL, but
instead those tools can redefine or update the config class for their needs
and have the config sent to PAL.

CLA signed by all contributors.


Import Editor Linter Registry from NG

A work-in-progress.

Passing tests, working locally. Ready for a review.
/cc @atom-community/linter-contributors

Already merged into the next branch.


feat: Compatibility with leap.nvim

When using leap.nvim, hints are not highlighted as expected which negatively affects the usability of the plugin with this color scheme.
Example:

Using darkvoid:

It's a bit hard to tell just from the screenshot, but vis and vif were both vim originally, and the s and f are the hints. As you can see, it's basically impossible to tell that they're hints without actually reading the whole word and seeing that the letter is wrong.

Using kanagawa theme, here's how it should look:

I will take a look at implementing leap.nvim compatibility this weekend when I have some time. Another thing I'd like to see is an option to have string literals be also highlighted in a subtle color -- really it's the last thing that's missing for me. I'll probably open a separate issue for that later.
Love the theme otherwise! I've always wanted to work on a theme but I was never sure where to start. Now that I see this foundation you've laid out, I'm bursting with ideas. Super excited to be on board, cheers!
EDIT: Just saw that there is an easy way to set the string color in the config. My bad!

Yes sure take care of the leap.nvim support for darkvoid.nvim.
Files you will have to change:

Make a new file leap.lua in plugins folder in which you will define the highlights and color to apply to those highlights from colors.lua.
config.lua : add name leap in plugins table
colors.lua: leap = true in plugins table
config.md: leap = true in plugins table


add dart grpc

Would you be open to adding dart grpc ?
Its now quite mature, and also gettign grpc-web soon.
I typically use it to do grpc between golang servers and dart clients in flutter.
REPO: https://github.com/grpc/grpc-dart
Tutorial: https://grpc.io/docs/tutorials/basic/dart.html
Here is the tutorial using a Makefile for golang and dart talking over grpc.
 On  Dart client and Dart server sides.


Pytorch version

Could you develop a Pytorch version？The CPU version depending on the gensim is too slow.

Thank you for answering


Update to use public_folder

Sinatra public config item was renamed to public_folder. I noticed
after bundle installing Serious from git source for my site that a new
version of Sinatra was installed 1.3.0. When running app was warned
that this item has changed to public_folder.

Hmm I'm not sure how I came across this. Since I've had the project locally I was able to get the tests working after running bundle install and it is using Serious 1.2.6. Not sure how I had it install 1.3.0. Either way while you can ignore this just keep it open for now as I'll leave my branch so if you do move to support newer versions of Sinatra you'll run into this issue and can just accept the fix then. It's a minor change.


Be smarter about when we render notebook output in monaco editors

Peng and I were talking about https://github.com/microsoft/vscode/issues/120219 by @firelizzard18.
Currently, in notebooks we special case the application/json mimetype to be rendered with syntax highlighting in an editor. In the issue, Ethan requested a way to render code in the same way within the renderer, but this is hard for a number of reasons. Instead, it would be nice if there was a way to render other languages in the same way we special-case application/json.
Currently, language contributions already list their mimetypes
https://github.com/microsoft/vscode/blob/cdab314713b80fef92c2f9593d4a3d2dd8b9cf27/extensions/json/package.json#L38-L41
so instead of special casing JSON, we could have generic logic that can render mimetypes for any installed language in an editor.
Another way would be an optional property on the cell output...
export class NotebookCellOutputItem {

-  constructor(mime: string, value: unknown, metadata?: Record<string, any>);
+  constructor(mime: string, value: unknown, metadata?: Record<string, any>, languageId?: string);

but I think this is overkill where the mime type mapping could 'just work'.
@jrieken @rebornix @roblourens

@rebornix in what way is this out of scope?


YARN-8990. Fix fair scheduler race condition in app submit and queue …

…cleanup.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.2 Compile Tests _

+1 :green_heart:
mvninstall
32m 28s

branch-3.2 passed

+1 :green_heart:
compile
0m 50s

branch-3.2 passed

+1 :green_heart:
checkstyle
0m 39s

branch-3.2 passed

+1 :green_heart:
mvnsite
0m 54s

branch-3.2 passed

+1 :green_heart:
javadoc
0m 37s

branch-3.2 passed

+1 :green_heart:
spotbugs
1m 59s

branch-3.2 passed

+1 :green_heart:
shadedclient
17m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 59s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 37s

the patch passed

+1 :green_heart:
mvnsite
0m 55s

the patch passed

+1 :green_heart:
javadoc
0m 35s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager generated 0 new + 353 unchanged - 6 fixed = 353 total (was 359)

+1 :green_heart:
spotbugs
2m 13s

the patch passed

+1 :green_heart:
shadedclient
17m 58s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
87m  1s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

179m 21s

Reason
Tests

Failed junit tests
hadoop.yarn.server.resourcemanager.metrics.TestSystemMetricsPublisherForV2

hadoop.yarn.server.resourcemanager.metrics.TestCombinedSystemMetricsPublisher

hadoop.yarn.server.resourcemanager.scheduler.capacity.conf.TestFSSchedulerConfigurationStore

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3254/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3254

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 08e081a1e9a3 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.2 / ee520484f0ddf1f268f97fbd985444d2bf3a09ce

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~18.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3254/1/testReport/

Max. process+thread count
799 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3254/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

I ran the following three failed tests in branch-3.2 and all of them failed without modification.

TestSystemMetricsPublisherForV2
TestCombinedSystemMetricsPublisher
TestFSSchedulerConfigurationStore

Note: Backported YARN-9338 to branch-3.2 to fix TestSystemMetricsPublisherForV2


Fix s3 streaming

To make working s3 we also need https://github.com/openshift-pipelines/tektoncd-results/pull/33

This pr is confliction with https://github.com/openshift-pipelines/pipeline-service/pull/511 ...

Can you please rebase and clean up the commit history?


signalbackup-tools: 20230429 -> 20230508

Description of changes
Update to latest version. No changes that effect build (diff: https://github.com/bepaald/signalbackup-tools/compare/20230429...20230508)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.


timeout rollback may have a bug

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
flush undo_log pending before committing until the server notifies the branch to roll back when it finds that the global transaction has timed out.
finally undolog inserted and business sql executed。
it is wrong。
Ⅱ. Describe what happened
rollback may make data dirty
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

debug point on
com.alibaba.fescar.rm.datasource.ConnectionProxy#
if (context.hasUndoLog())//line

until the server notifies the branch to roll back when it finds that the global transaction has timed out

branch rollback(has no undo_log)   return succ

finally release debug point

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
OS :
Others:

please use the latest version . If you have other questions, please reopen it.


refactor!: declarative api

Description
This PR refactors the API to use a more declarative approach, as described in #14.
It includes a version bump to 0.4.0.
TODO

[x] Add more tests.
[x] Ensure 100% code coverage.
[x] Update documentation.
[x] Improve/otherwise update example project.
[ ] Upload to pub.

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[x] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Do you need some support with finishing the PR?

@felangel As discussed offline, this refactor looks ready to get reviewed, merged and released! 😄


Missing empty constructor for xscalar

Hi, it would be nice to have an empty constructor for xscalar so that we can have an homogeneous behavior with xarray, xtensor; i.e. a constructor that initializes the scalar to 0 for numeric types.

Fixed in #795


last.fm autocorrect before TTS

Resolved in https://github.com/tb0hdan/voiceplay/commit/0de2d9c3a674d97685ce200109cff4cf8afb211e


Add query to search for Issues & associated PRs/Issues

This query will provide a 'paper trail' of Issues and PRs pertaining to a particular Issue when passing in a GitHub Search string. It's useful when trying to determine what requests may still be outstanding vs what requests are actively being worked on.

Thanks

Thanks I appreciate it thanks

Can you help me
On Thu, Apr 22, 2564 BE at 1:19 PM akiragg @.***> wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/platform-samples/pull/378#issuecomment-824986041,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATOTKEVXMMINRZQRNYA2G2DTKBEADANCNFSM4WTRFFTA
.


Siad has exited unexpectedly    Loading... (0/6) Loading siad... listen tcp <IP_ADDRESS>:9980: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Loading...
(0/6) Loading siad...
listen tcp <IP_ADDRESS>:9980: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

This means you're running another program on that port -- most likely another instance of siad. Kill those other instances and try again.

Recommendation to devs: Close


Error with Google Script

Hey, Love the script! When I try to run it Google gives me the error of

TypeError: Cannot call method "slice" of undefined. (line 60, file"Code")

Lines 59 - 60
function paginate(posts, page) {    var postsCopy = posts.slice();    var postsChunked = [];   var postsPaginated = {     posts: [],     pages: {       previous: null,       next: null     }   };
If you could help me out that would be great.

I had this issue until I published the Sheet. You must make it public using the "Share" button, but also from the File menu: "Publish to the web..."


[BUG] The text format of startup.sh and shutdown.sh is incorrect

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The text format of startup.sh and shutdown.sh is incorrect。
both this is need to set unix format。

Expected Behavior
No response
Steps To Reproduce
No response
Environment
HertzBeat version(s):V1.6.1.RC4

Debug logs
No response
Anything else?
No response

restart.sh  is also incorrect

Hi, this is a pre-release version. You are welcome to provide feedback via the mailing list.

We will fix it.


[BUG] -  @ikun-ui/utils npm 版本低，无法install

Describe the bug
pnpm add @ikun-ui/core && pnpm add -D unocss && pnpm add -D @ikun-ui/preset

ERR_PNPM_NO_MATCHING_VERSION  No matching version found for<EMAIL_ADDRESS>This error happened while installing the dependencies of<EMAIL_ADDRESS>The latest release of @ikun-ui/utils is "0.0.9-beta.1".
If you need the full list of all 7 published versions run "$ pnpm view @ikun-ui/utils versions".
Progress: resolved 214, reused 213, downloaded 0, added 0

@ikun-ui/utils
坤坤坤，已经迫不及待的想体验一下哥哥的UI了
Reproduction
No response
System Info
No response
Used Package Manager
pnpm
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a ikun-ui issue and not a framework-specific issue. For example, if it's a Svelte SFC related bug, it should likely be reported to https://github.com/sveltejs/svelte instead.
[X] The provided reproduction is a minimal reproducible example of the bug.

Try with latest version


Effectful values were not longer being shared in MonadInterleave

@Ericson2314 @ryantrinkle @tgiannak When we had the previous, IORef-based Thunk implementation, the following program only imported hello.nix once:
let x = import ./tests/files/hello.nix; in [ x x ]

With the recent change to using MonadInterleave, we lost this sharing of effects, as can be seen by a trace of the evaluation:
Let..1
Let..2: s = fromList [("x",())]
NList
NSym: var = "x"
NApp
NSym: var = "import"
evalApp:NVBuiltin import
NLiteralPath
No known current directory
Importing file /Users/johnw/src/hnix/tests/files/hello.nix
NStr
NSym: var = "x"
evalApp:NVBuiltin import
No known current directory
Importing file /Users/johnw/src/hnix/tests/files/hello.nix
[ "Hello, world!" "Hello, world!" ]

Since we kept the interface the same, I'm going to revert the contents of Thunk.hs back to the IORef version until we can resolve this sharing issue.

I think we'll stay with the explicit now, which is at least easier to understand and allows us to discriminate between pure and effectful-bearing thunks.


ngRoute: Resolve properties not immediately available on the $scope object

Resolved properties of a route are added to the $scope object under the name $resolve (unless otherwise changed by the resolveAs setting), however, the $resolve object is not present when the controller function is first executed (it is added a few milliseconds after).
Here is a plunker of the problem (an edited version of the route example in the docs).
When BookController loads, it immediately tries to access properties from $scope.$resolve but it is undefined.
One of my routes is used for both creating a new resource and editing an existing one as they both use the exact same form. The only difference is that when you are editing an existing object, it is fetched from the server in the resolve section of the route definition. In the route controller, I cannot inject it like a normal resolve property because it is not present all the time. So I wanted to access it via the $scope, so I can fill the form with existing data.

The aim of the $resolve property is to help with simple scenarios where a controller is not needed.
It is added as part of the ngView directive: https://github.com/angular/angular.js/blob/master/src/ngRoute/directive/ngView.js#L278
If you want to have access to these values in your controller then you can either:

have them injected directly into your controller
access them via $route.current.locals (which is the same object as $resolve`

That being said, it might be possible to move the attachment to before the controller is instantiated. What do you think @shahata?

I agree $resolve is not the right way to go in this use case, I would just inject the values in controller constructor.

I can't inject them in the controller because the values are given as locals to the injector when the controller function is run.
I think $route.current.locals might work for my situation, but I still think the attachment of $resolve to the scope should be moved to before the controller is instantiated because its not really possible to use it as it stands now. Although I understand how low priority this fix is.

After having a look at the source it looks like $resolve is set at the same time as the controller is added to the scope using the $controllerAs property. This makes sense to me and seems like the intended behaviour. Maybe just close this issue then.


chore: rs-sdk minor fixes and docs improvements

Issue being fixed or feature implemented
cargo doc shows warnings
What was done?

fixed docs
removed some unnecessary dependencies
tested rs-sdk with various features enabled/disabled
fix: Sdk::prove() uses value set in SdkBuilder (but only true supported so far)
rs-sdk online-testing replaced by  offline-testing (enabled by default) so that cargo test --all-features uses offline test vectors

How Has This Been Tested?
Running cargo doc and cargo clippy manually
Breaking Changes
None
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
[ ] I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Love moar docs!


chore(main): release 0.2.22

:robot: I have created a release beep boop
0.2.22 (2023-10-05)
Miscellaneous

deps: Bump Gradle Wrapper to 8.4 (c7e7fe4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/paulschuberth/mdgen/releases/tag/v0.2.22 :sunflower:


doc(readme): add redis registry

What type of PR is this?

docs: Documentation only changes
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
添加redis服务注册拓展
(Optional) More detail description for this PR(en: English/zh: Chinese).

en: add redis registry for readme
zh(optional): 添加redis服务注册拓展
Which issue(s) this PR fixes:

null

Can you also update the README of registry repo?


fix(ckb-contracts): add ckb contracts tests

Codecov Report

Merging #191 (82451a3) into main (81e1f6d) will increase coverage by 1.94%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #191      +/-   ##
==========================================
+ Coverage   31.13%   33.07%   +1.94%
==========================================
  Files          56       33      -23
  Lines        6148     5091    -1057
  Branches      185        0     -185
==========================================
- Hits         1914     1684     -230
+ Misses       4234     3407     -827

Impacted Files
Coverage Δ

...racts/lib/eth-recipient-typescript-lib/src/test.rs
100.00% <100.00%> (ø)

eth-contracts/contracts/libraries/TypedMemView.sol

eth-contracts/contracts/proxy/Base.sol

eth-contracts/contracts/CKBChainV2.sol

eth-contracts/contracts/proxy/EnhancedMap.sol

eth-contracts/contracts/libraries/ViewSpv.sol

eth-contracts/contracts/Eaglesong.sol

eth-contracts/contracts/libraries/Blake2b.sol

eth-contracts/contracts/CKBChain.sol

...th-contracts/contracts/CKBChainV2-openzeppelin.sol

... and 14 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #191 (82451a3) into main (81e1f6d) will increase coverage by 1.94%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #191      +/-   ##
==========================================
+ Coverage   31.13%   33.07%   +1.94%
==========================================
  Files          56       33      -23
  Lines        6148     5091    -1057
  Branches      185        0     -185
==========================================
- Hits         1914     1684     -230
+ Misses       4234     3407     -827

Impacted Files
Coverage Δ

...racts/lib/eth-recipient-typescript-lib/src/test.rs
100.00% <100.00%> (ø)

eth-contracts/contracts/libraries/TypedMemView.sol

eth-contracts/contracts/proxy/Base.sol

eth-contracts/contracts/CKBChainV2.sol

eth-contracts/contracts/proxy/EnhancedMap.sol

eth-contracts/contracts/libraries/ViewSpv.sol

eth-contracts/contracts/Eaglesong.sol

eth-contracts/contracts/libraries/Blake2b.sol

eth-contracts/contracts/CKBChain.sol

...th-contracts/contracts/CKBChainV2-openzeppelin.sol

... and 14 more

Continue to review full report at Codecov.

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


package.json

added package.json so we can install via npm.

The "author", "bug" and "homepage" fields are incorrect
The "directories" field is useless
The "dependencies" field is missing


How do I hide an entire clr-stepper-panel based on a toggle switch from another clr-stepper-panel?

I am unable to hide a stepper panel after I toggle a checkbox in another stepper panel. I tried with both [hidden] as well as *ngIf, I do not get the expected results.

When I use [hidden], I get an error while loading the page saying:

core.js:4799 ERROR TypeError: Cannot read property 'id' of undefined     at StepperModel.openFirstPanel (clr-angular.js:17866)

When I use *ngIf and toggle the checkbox in another stepper panel, the stepper panel changes focus and expands the first stepper panel again. I would like the new stepper panel to be added or removed silently.

This is the condition I have put in my *ngIf or [hidden]:
form.get('checkboxName').value
How to reproduce
Steps to reproduce the behavior:

Create a stepper with more than one stepper panels. One of the stepper panels must contain a checkbox inside it.
Add a *ngIf or hidden in other stepper panel such that it is shown only when the checkbox is selected.
Check the checkbox

Versions
App

Angular: [e.g. 8]
Clarity: [e.g. 2.1.0]

Device:

Type: Mac
OS: [e.g. iOS]
Browser [chrome]

Additional notes
Add any other notes about the problem here.

Can you please help us by creating a demo using StackBlitz? We request this of all reports so we can triage your issue. We have some starters at https://stackblitz.com/@clr-team


dual_clock fifo and bsvpreprocess.py

Please take a look at first two commits.

Can I merge this?

With the new UI for "review" I missed the merge step somehow.

now that I've merged it, I should see if there is a way to merge in github now without a merge commit


Index prefetch attemtps to prefetch invalid blocks

Initially, I discovered this issue when running several test_pg_regress instances in a loop. Then I reproduced it with a reduced schedule, like this:
parallel group (6 tests):  hash_part partition_info partition_aggregate partition_prune partition_join indexing
     partition_join               ... ok         4112 ms
     partition_prune              ... ok         4036 ms
     hash_part                    ... ok          267 ms
     indexing                     ... ok         4462 ms
     partition_aggregate          ... ok         3980 ms
     partition_info               ... ok          684 ms
test oidjoins                     ... FAILED (test process exited with exit code 2)     2568 ms

(Later I found out that only indexing (repeated) is enough to trigger the issue.)
PG:TRAP: FailedAssertion("BlockNumberIsValid(blockNum)", File: ".../neon//vendor/postgres-v14/src/backend/storage/buffer/bufmgr.c", Line: 594, PID: 1075005)
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(ExceptionalCondition+0xd6)[0x5569a9d6e86e]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(PrefetchBuffer+0x73)[0x5569a9b55509]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(_bt_first+0xf5c)[0x5569a96f254a]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(btgettuple+0x19b)[0x5569a96ec878]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(index_getnext_tid+0x18b)[0x5569a96d6958]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(+0x7a1854)[0x5569a9cfa854]
postgres: cloud_admin regression <IP_ADDRESS>(50626) DO(+0x7a136f)[0x5569a9cfa36f]
...
PG:2024-11-21 06:49:52.430 GMT [1063326] DETAIL:  Failed process was running: DO $doblock$
    declare
     fk record;
    nkeys integer;
...
Core was generated by `postgres: cloud_admin regression <IP_ADDRESS>(50626) DO                          '.
Program terminated with signal SIGABRT, Aborted.
...
#5  0x00005569a9d6e8a1 in ExceptionalCondition (conditionName=0x5569a9f436fa "BlockNumberIsValid(blockNum)", errorType=0x5569a9f435d9 "FailedAssertion", fileName=0x5569a9f43598 ".../neon//vendor/postgres-v14/src/backend/storage/buffer/bufmgr.c", lineNumber=594) at .../neon//vendor/postgres-v14/src/backend/utils/error/assert.c:69
#6  0x00005569a9b55509 in PrefetchBuffer (reln=0x7f2ce1636b88, forkNum=MAIN_FORKNUM, blockNum=4294967295) at .../neon//vendor/postgres-v14/src/backend/storage/buffer/bufmgr.c:594
#7  0x00005569a96f254a in _bt_first (scan=0x5569abb51518, dir=BackwardScanDirection) at .../neon//vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c:1484
#8  0x00005569a96ec878 in btgettuple (scan=0x5569abb51518, dir=BackwardScanDirection) at .../neon//vendor/postgres-v14/src/backend/access/nbtree/nbtree.c:242
#9  0x00005569a96d6958 in index_getnext_tid (scan=0x5569abb51518, direction=BackwardScanDirection) at .../neon//vendor/postgres-v14/src/backend/access/index/indexam.c:575
#10 0x00005569a9cfa854 in get_actual_variable_endpoint (heapRel=0x7f2cddc74e90, indexRel=0x7f2ce1636b88, indexscandir=BackwardScanDirection, scankeys=0x7ffc407fde80, typLen=4, typByVal=true, tableslot=0x5569abb51300, outercontext=0x5569aba97ad0, endpointDatum=0x5569abbcd5b0) at .../neon//vendor/postgres-v14/src/backend/utils/adt/selfuncs.c:6229
#11 0x00005569a9cfa36f in get_actual_variable_range (root=0x5569abbb90e8, vardata=0x7ffc407fe220, sortop=609, collation=0, min=0x0, max=0x5569abbcd5b0) at .../neon//vendor/postgres-v14/src/backend/utils/adt/selfuncs.c:6108
#12 0x00005569a9cf09b7 in ineq_histogram_selectivity (root=0x5569abbb90e8, vardata=0x7ffc407fe220, opoid=611, opproc=0x7ffc407fe100, isgt=false, iseq=true, collation=0, constval=26439, consttype=26) at .../neon//vendor/postgres-v14/src/backend/utils/adt/selfuncs.c:1126
#13 0x00005569a9cefd28 in scalarineqsel (root=0x5569abbb90e8, operator=611, isgt=false, iseq=true, collation=0, vardata=0x7ffc407fe220, constval=26439, consttype=26) at .../neon//vendor/postgres-v14/src/backend/utils/adt/selfuncs.c:685
#14 0x00005569a9cf4ab9 in mergejoinscansel (root=0x5569abbb90e8, clause=0x5569abbbba88, opfamily=1989, strategy=1, nulls_first=false, leftstart=0x7ffc407fe2e0, leftend=0x7ffc407fe2e8, rightstart=0x7ffc407fe2f0, rightend=0x7ffc407fe310) at .../neon//vendor/postgres-v14/src/backend/utils/adt/selfuncs.c:3099
#15 0x00005569a9a2252f in cached_scansel (root=0x5569abbb90e8, rinfo=0x5569abbbd5e0, pathkey=0x5569abbcda68) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/costsize.c:3687
#16 0x00005569a9a2168d in initial_cost_mergejoin (root=0x5569abbb90e8, workspace=0x7ffc407fe510, jointype=JOIN_ANTI, mergeclauses=0x5569abbcdad8, outer_path=0x5569abbcabb8, inner_path=0x5569abbcad00, outersortkeys=0x5569abbcd970, innersortkeys=0x5569abbcdb88, extra=0x7ffc407fe6e0) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/costsize.c:3249
#17 0x00005569a9a34e0c in try_mergejoin_path (root=0x5569abbb90e8, joinrel=0x5569abbcb888, outer_path=0x5569abbcabb8, inner_path=0x5569abbcad00, pathkeys=0x0, mergeclauses=0x5569abbcdad8, outersortkeys=0x5569abbcd970, innersortkeys=0x5569abbcdb88, jointype=JOIN_ANTI, extra=0x7ffc407fe6e0, is_partial=false) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinpath.c:910
#18 0x00005569a9a359a4 in sort_inner_and_outer (root=0x5569abbb90e8, joinrel=0x5569abbcb888, outerrel=0x5569abb94bd8, innerrel=0x5569abbbbf28, jointype=JOIN_ANTI, extra=0x7ffc407fe6e0) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinpath.c:1333
#19 0x00005569a9a33dc6 in add_paths_to_joinrel (root=0x5569abbb90e8, joinrel=0x5569abbcb888, outerrel=0x5569abb94bd8, innerrel=0x5569abbbbf28, jointype=JOIN_ANTI, sjinfo=0x5569abbbd498, restrictlist=0x5569abbccf78) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinpath.c:282
#20 0x00005569a9a38e5f in populate_joinrel_with_paths (root=0x5569abbb90e8, rel1=0x5569abb94bd8, rel2=0x5569abbbbf28, joinrel=0x5569abbcb888, sjinfo=0x5569abbbd498, restrictlist=0x5569abbccf78) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinrels.c:915
#21 0x00005569a9a388cc in make_join_rel (root=0x5569abbb90e8, rel1=0x5569abb94bd8, rel2=0x5569abbbbf28) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinrels.c:760
#22 0x00005569a9a37dfc in make_rels_by_clause_joins (root=0x5569abbb90e8, old_rel=0x5569abb94bd8, other_rels_list=0x5569abbcce20, other_rels=0x5569abbcce40) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinrels.c:312
#23 0x00005569a9a37917 in join_search_one_level (root=0x5569abbb90e8, level=2) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/joinrels.c:123
#24 0x00005569a9a185c1 in standard_join_search (root=0x5569abbb90e8, levels_needed=2, initial_rels=0x5569abbcce20) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/allpaths.c:3021
#25 0x00005569a9a18527 in make_rel_from_joinlist (root=0x5569abbb90e8, joinlist=0x5569abbbe580) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/allpaths.c:2952
#26 0x00005569a9a13d53 in make_one_rel (root=0x5569abbb90e8, joinlist=0x5569abbbe580) at .../neon//vendor/postgres-v14/src/backend/optimizer/path/allpaths.c:228
#27 0x00005569a9a5408d in query_planner (root=0x5569abbb90e8, qp_callback=0x5569a9a59dfb <standard_qp_callback>, qp_extra=0x7ffc407febc0) at .../neon//vendor/postgres-v14/src/backend/optimizer/plan/planmain.c:276
#28 0x00005569a9a568b7 in grouping_planner (root=0x5569abbb90e8, tuple_fraction=0) at .../neon//vendor/postgres-v14/src/backend/optimizer/plan/planner.c:1442
#29 0x00005569a9a55f50 in subquery_planner (glob=0x5569abbc4130, parse=0x5569abb934f0, parent_root=0x0, hasRecursion=false, tuple_fraction=0) at .../neon//vendor/postgres-v14/src/backend/optimizer/plan/planner.c:1019
...

Notice the blockNum value passed to PrefetchBuffer().
With some logging added inside the "Start prefetching" code block, I got the following diagnostics:
PG:2024-11-21 18:09:54.280 GMT [3461271] LOG:  !!!_bt_first| forward: 0, first_offset: 1, so->n_prefetch_blocks: 5, stack->bts_offset: 7
PG:2024-11-21 18:09:54.280 GMT [3461271] LOG:  !!!_bt_first| skip: -2

So, we can see negative i here:
    /* Start prefetching for index only scan */
    if (so->prefetch_maximum > 0 && stack != NULL && scan->xs_want_itup) /* index only scan */
    {
        int first_offset = _bt_read_parent_for_prefetch(scan, stack->bts_blkno, dir);
        int skip = ScanDirectionIsForward(dir)
            ? stack->bts_offset - first_offset
            : first_offset + so->n_prefetch_blocks - 1 - stack->bts_offset;
        Assert(so->n_prefetch_blocks >= skip);
        so->current_prefetch_distance = INCREASE_PREFETCH_DISTANCE_STEP;
        so->n_prefetch_requests = Min(so->current_prefetch_distance, so->n_prefetch_blocks - skip);
        so->last_prefetch_index = skip + so->n_prefetch_requests;
        for (int i = skip; i < so->last_prefetch_index; i++)
            PrefetchBuffer(rel, MAIN_FORKNUM, so->prefetch_blocks[i]);
    }

But the BlockNumberIsValid() assert fails only when so->prefetch_blocks[i] contains -1, so it happens not every time when i is negative.
While testing, I also saw another assertion failure:
PG:TRAP: FailedAssertion("so->n_prefetch_blocks >= skip", File: ".../neon/vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c", Line: 1479, PID: 814781)

I could not find a good clean way to reproduce this yet, except for running multiple test instances in a loop for an hour/two, though with the following "forced ios" modification (which makes test_pg_regress fail due to unexpected outputs, but it doesn't matter here):
--- a/src/backend/access/index/genam.c
+++ b/src/backend/access/index/genam.c
@@ -107 +107 @@ RelationGetIndexScan(Relation indexRelation, int nkeys, int norderbys)
-    scan->xs_want_itup = false; /* may be set later */
+    scan->xs_want_itup = true;

and sed 's/polygon //' -i src/test/regress/parallel_schedule # needed to avoid an unrelated failure
running multiple test instances simultaneously and looking for FailedAssertion in test_output/, I can quickly get failures as below:
7       ======================== 1 failed in 395.79s (0:06:35) =========================
4       ======================== 1 failed in 399.26s (0:06:39) =========================
6       ======================== 1 failed in 436.25s (0:07:16) =========================
9       ======================== 1 failed in 820.90s (0:13:40) =========================
3       ======================== 1 failed in 822.12s (0:13:42) =========================
8       ======================== 1 failed in 823.63s (0:13:43) =========================
5       ======================== 1 failed in 825.26s (0:13:45) =========================
2       ======================== 1 failed in 826.89s (0:13:46) =========================
1       ======================== 1 failed in 828.05s (0:13:48) =========================
10      ======================== 1 failed in 836.52s (0:13:56) =========================

test_output/test_pg_regress_7[debug-pg14-None]/repo/endpoints/ep-1/compute.log
PG:TRAP: FailedAssertion("so->n_prefetch_blocks >= skip", File: ".../neon//vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c", Line: 1479, PID: 2270161)
...
PG:2024-11-24 16:42:25.638 GMT [2262658] DETAIL:  Failed process was running: INSERT INTO itest1 DEFAULT VALUES;

test_output/test_pg_regress_4[debug-pg14-None]/repo/endpoints/ep-1/compute.log
PG:TRAP: FailedAssertion("so->n_prefetch_blocks >= skip", File: ".../neon//vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c", Line: 1479, PID: 2270863)
...
PG:2024-11-24 16:42:31.958 GMT [2262430] DETAIL:  Failed process was running: CREATE INDEX test_replica_identity_hash ON test_replica_identity USING hash (nonkey);

test_output/test_pg_regress_6[debug-pg14-None]/repo/endpoints/ep-1/compute.log
PG:TRAP: FailedAssertion("so->n_prefetch_blocks >= skip", File: ".../neon//vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c", Line: 1479, PID: 2269994)
...
PG:2024-11-24 16:43:12.463 GMT [2262483] DETAIL:  Failed process was running: DROP POLICY p2 ON t1;

Good find @alexanderlaw!
That should be fixed by https://github.com/neondatabase/neon/pull/9867

@bayandin , unfortunately, with the patch https://github.com/neondatabase/postgres/compare/284ae56be2397fd3eaf20777fa220b2d0ad968f5...7af94013de364fbe0c47a389cb4c0575d4992c60 applied, I'm still getting:
PG:TRAP: FailedAssertion("so->n_prefetch_blocks >= skip", File: "...//vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c",
...
PG:2024-11-25 03:52:13.123 GMT [3654398] DETAIL:  Failed process was running: update people set fn.first = 'Jack';

using the same "forced ios" testing method.

With an auxiliary Assert added to the latest patch:
+        if (so->n_prefetch_blocks >= skip)
+        {
+            so->current_prefetch_distance = INCREASE_PREFETCH_DISTANCE_STEP;
+            so->n_prefetch_requests = Min(so->current_prefetch_distance, so->n_prefetch_blocks - skip);
+            so->last_prefetch_index = skip + so->n_prefetch_requests;
+            for (int i = skip; i < so->last_prefetch_index; i++)
+{
+Assert(i >= 0);
+                PrefetchBuffer(rel, MAIN_FORKNUM, so->prefetch_blocks[i]);
+}
+        }

I can see it triggered like this:
8       ======================== 1 failed in 378.53s (0:06:18) =========================
7       ======================== 1 passed in 977.77s (0:16:17) =========================
9       ======================== 1 passed in 981.50s (0:16:21) =========================
5       ======================== 1 passed in 983.19s (0:16:23) =========================
4       ======================== 1 passed in 984.47s (0:16:24) =========================
10      ======================== 1 passed in 993.43s (0:16:33) =========================
6       ======================== 1 passed in 997.41s (0:16:37) =========================
3       ======================== 1 passed in 998.07s (0:16:38) =========================
2       ======================== 1 passed in 999.05s (0:16:39) =========================
1       ======================== 1 passed in 1000.31s (0:16:40) ========================

test_output/test_pg_regress_8[debug-pg14-None]/repo/endpoints/ep-1/compute.log
PG:TRAP: FailedAssertion("i >= 0", File: ".../vendor/postgres-v14/src/backend/access/nbtree/nbtsearch.c", Line: 1489,
...
PG:2024-11-25 07:56:52.578 GMT [3917163] DETAIL:  Failed process was running: SELECT table_name, column_name, column_default, is_nullable, is_identity, identity_generation, identity_start, identity_increment, identity_maximum, identity_minimum, identity_cycle FROM information_schema.columns WHERE table_name LIKE 'itest_' ORDER BY 1, 2;

(I've disabled the troublesome polygon's query more granularly for 'make check' to pass cleanly with the "forced ios" mod: fix-polygon.sql-for-forced-ios.patch.txt.)


Sanity-check that an archetype has a component

What
We're starting to build in a lot of assumptions in our code about what archetypes has what components.
This happens here and there where we query for components directly.
At first I added the checks at runtime using reflection, before I realized we can do it at compile-time instead:
    fn _check_encoded_image_has_blob(image: &archetypes::EncodedImage) {
        let _: components::Blob = image.blob;
    }

This means we will be reminded to update the code if we ever change the archetype to e.g. use a EncodedImageBuffer component or similar in the future!
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

A macro is a good idea 🤔


Extend from Parser

Extending from Parser adds some convenience methods to the Parser out of the box, such as decodeAccumulating.
The parser package object already matches the Parser interface.
Relates to #199

@zmccoy @jeffmay Would you have time to take a look? Thanks!

(As an aside, I see that readme in this repo still names Travis as a maintainer.)

@TimoMeijer A preemptive approval when I thought I saw it green on my part.  So it looks like things run fine on 2.11, and 2.12.  On 2.13 however, when extending Parser on the package object it compiles, but ends up acting as if the  def parse(yaml: Reader): Either[ParsingFailure, Json] definition doesn't exist and that the method that takes a string is the only one.  Changing names would break bincompat, and I'm honestly not sure if this is a bug in the 2.13 compiler or an expected change.

I can see if I can reproduce this locally tomorrow, and if so, investigate further

The compile error actually occurs in both 2,12 and 2.13, but not in 3.
If I change the package object into a regular object, the error disappears.
I have not yet figured out why this is the case, but I'll do some more research.

That looks to track with what we found when we were looking at things, I missed the 2.12 failure though but that makes sense.

Sorry, I know I don't maintain this anymore. But I want to ask:
Do you want to extends Parser so that this package can be substituted for a Parser? Or is it just to inherit the < 20 lines of code that Parser gives you?
I'd hope it's not the former, because you can't substitute a JSON parser for a YAML parser (nor vice versa, necessarily).
I'd hope it's not the latter, because those methods aren't special enough to couple these.
Just my opinion as an ex-maintainer.

Thanks for your thoughts @jeremyrsmith!
My original case was that I wanted to use decodeAccumulating with yaml files. On looking into it further, I noticed it was implemented on the Parser trait in circe core, which the circe builtin jawn parser module implements. It seemed logical that the yaml parser should be implemented similarly, and inherit the same functionality and convenience methods.
You're of course completely right that simply copying over decode and decodeAccumulating would add the same
convenience methods. Personally, I would argue that extending Parser would be a more future-proof implementation, over duplicating the convenience methods. Although this compiler bug makes that choice less straightforward.
@jeremyrsmith, is your point that we should add these convenience methods, but not through extending from Parser, or that we shouldn't add these conveniences at all?

@TimoMeijer I guess my point is that, in Parser, the desired method decodeAccumulating is just composing parse and then the decoder's decode. The details of composing an Either[E, T] with a T => ValidatedNel[E, T] are not likely to change, so extending an interface just to inherit that well-defined method might not be worth the trouble it's causing.
Another solution would be to pull out the implementation in question to a function. Would that seem silly for the method in question?
Again, sorry to butt in here. Not trying to imply I have answers.
But extending Parser might be an XY problem @zmccoy 😉

Whops, sorry, was working on an alternative and accidentally pushed into master... I've fixed that, this isn't really merged in.. :disappointed:

@TimoMeijer Thoughts on https://github.com/circe/circe-yaml/pull/338?

Seems like a clean workaround! On 4 Nov 2022 22:58, Darren Gibson @.***> wrote:
@TimoMeijer Thoughts on #338?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Bump ames version for breach

Also removes trailing whitespace from ames, something we really should do for the whole repo sometime.

Sent from my iPhone

On Feb 22, 2018, at 10:13 AM, Fang<EMAIL_ADDRESS>wrote:
Also removes trailing whitespace from ames, something we really should do for the whole repo sometime.
You can view, comment on, or merge this pull request online at:
https://github.com/urbit/arvo/pull/639
Commit Summary
Bump ames protocol version. Now set in a single constant.
Remove trailing whitespace from ames.
File Changes
M sys/vane/ames.hoon (31)
Patch Links:
https://github.com/urbit/arvo/pull/639.patch
https://github.com/urbit/arvo/pull/639.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Rendering efficiency of list comparisons of columns or rows.

A problem in which the list of columns or rows is re-rendered even if it has not been changed.
I'm struggling with this for rendering efficiency.

I've started working on this this week.
The main problem is using a change notifier. there are a lot of widgets and they're all getting notified of all events, most of the widgets don't care about most of the events (for example, a cell shouldn't get a notification when resizing a column). and that's causing the whole grid to be rebuilt, re-layouted, and re-painted unnecessarily.  I'm working on separating these events and their subscribers. It'll be a hard task, but I'll see what I can do.
For now I've seen that the rendering performance when resizing a column is too bad for using a Row widget. I've changed it to another widget, I'm still doing tests, but we can't do this without separating the layout process.
Another thing we may do is to cache cell widgets whenever possible.
I'll share my progress when I get some work done on the topic


Add support for Linux x86_64

Opening this PR a bit early as I need some help with it.
Changes required:

[x] Update rust/makefile to support linux builds
[x] Update rust/copy.sh to have binaries copied over from target folder
[ ] Update dart code to support Linux as a platform.

A few other issues I have been facing which is preventing me from working on the dart codebase:

[ ] Type errors in dart code. lib/src/root.dart has type errors for the return values of several functions called from loaderApi. Most of them return an Int Pointer but their definition returns different types.

  Future<bool> isExplicitlyRbf() async {
    try {
      final res = await loaderApi.isExplicitlyRbfStaticMethodApi(tx: _tx!);
      return res; // this returns a Future<int> while the definition is bool
    } on FfiException catch (e) {
      throw configException(e.message);
    }
  }

Update also required in lib/src/utils/loader.dart
Unable to test for this due to the Type Errors mentioned above.
DynamicLibrary _open() {
  if (Platform.isIOS) {
    return DynamicLibrary.process();
  } else if (Platform.isAndroid) {
    return DynamicLibrary.open("librust_bdk_ffi.so");
  } else if (Platform.isLinux) {
    return DynamicLibrary.open("librust_bdk_ffi.so"); // linux/x86_64/librust_bdk_ffi.so ? or is the linux subpath implied?
  } else {
    return DynamicLibrary.executable();
  }
}

Also noticed that the binaries are being checked into git.
Better to .gitignore them?

Also noticed some changes in root.dart that I do not recognizing.
Replicating this PR through another account to find the source of those changes.

Also noticed some changes in root.dart that I did not recognize.
Replicated the changes I made through another repo and also finding the same result. I only change 2 files yet there are changes reflecting in the files in lib/src/generated/*

Also noticed that the binaries are being checked into git.
Better to .gitignore them?

If pub.dev requires binaries in the repo; then having release branches might be a good solution where the binaries are checked in.

I'm also trying to work through this and Windows trackin

Also noticed that the binaries are being checked into git.
Better to .gitignore them?

at least remove them :+1:

[ ]  Type errors in dart code. lib/src/root.dart has type errors for the return values of several functions called from loaderApi. Most of them return an Int Pointer but their definition returns different types.

  Future<bool> isExplicitlyRbf() async {
    try {
      final res = await loaderApi.isExplicitlyRbfStaticMethodApi(tx: _tx!);
      return res; // this returns a Future<int> while the definition is bool
    } on FfiException catch (e) {
      throw configException(e.message);
    }
  }

The definition for the functions that can be called using the DynamicLibrary loaderApi is available in lib/src/generated/bindings.dart. For the function isExplicitlyRbfStaticMethodApi, the return type is Future<bool>.
https://github.com/i5hi/bdk-flutter/blob/56f9feff3e9d22f5256965926e03fb8bc370ac1f/lib/src/generated/bindings.dart#L260.
You can cross-check, with bindings. dart file to confirm that the return types are the correct ones.

Unable to test for this due to the Type Errors mentioned above.
DynamicLibrary _open() {
  if (Platform.isIOS) {
    return DynamicLibrary.process();
  } else if (Platform.isAndroid) {
    return DynamicLibrary.open("librust_bdk_ffi.so");
  } else if (Platform.isLinux) {
    return DynamicLibrary.open("librust_bdk_ffi.so"); // linux/x86_64/librust_bdk_ffi.so ? or is the linux subpath implied?
  } else {
    return DynamicLibrary.executable();
  }
}

Adding a target and adding the condition for Linux is not the only thing required to add Linux support.
Please refer to the Linux integration part on this page: https://cjycode.com/flutter_rust_bridge/library/platform_setup/windows_and_linux.html to get a better idea on how to go about adding Linux support.

Also noticed that the binaries are being checked into git.
Better to .gitignore them?

at least remove them 👍

The binaries are in Github so that anyone who wants to use the Github repository can directly use them.
Without the binaries developers will have to build there own binaries which can be a non trivial task for some developers. This would add additional friction hence binaries are readily available.

Also noticed that the binaries are being checked into git.
Better to .gitignore them?

If pub.dev requires binaries in the repo; then having release branches might be a good solution where the binaries are checked in.

Thanks, yes this is one possible option. When this turns out to be a problem we can consider a suitable option.

Yes flutter rust bridge auto generates these files

Also noticed some changes in root.dart that I did not recognize.
Replicated the changes I made through another repo and also finding the same result. I only change 2 files yet there are changes reflecting in the files in lib/src/generated/*

Yes, Flutter Rust Bridge auto generates these files.


编译失败

One or more issues found when checking AAR metadata values:
 The minCompileSdk (31) specified in a
 dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
 is greater than this module's compileSdkVersion (android-29).
 Dependency: androidx.window:window-java:1.0.0-beta04.
 AAR metadata file: /Users/xiaobao/.gradle/caches/transforms-3/5cdc6ff012c2642ae0b17cac4608bd36/transformed/jetified-window-java-1.0.0-beta04/META-INF/com/android/build/gradle/aar-metadata.properties.

 The minCompileSdk (31) specified in a
 dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
 is greater than this module's compileSdkVersion (android-29).
 Dependency: androidx.window:window:1.0.0-beta04.
 AAR metadata file: /Users/xiaobao/.gradle/caches/transforms-3/e3fb8849fda8212e93ddc75a93e65816/transformed/jetified-window-1.0.0-beta04/META-INF/com/android/build/gradle/aar-metadata.properties.

 The minCompileSdk (32) specified in a
 dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
 is greater than this module's compileSdkVersion (android-29).
 Dependency: androidx.webkit:webkit:1.5.0.
 AAR metadata file: /Users/xiaobao/.gradle/caches/transforms-3/e6ad915c58ea43049220ff4368b6515a/transformed/webkit-1.5.0/META-INF/com/android/build/gradle/aar-metadata.properties.

 The minCompileSdk (33) specified in a
 dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
 is greater than this module's compileSdkVersion (android-29).
 Dependency: androidx.core:core:1.10.1.
 AAR metadata file: /Users/xiaobao/.gradle/caches/transforms-3/e6c7144b059ce69ee04d1632ecbb731a/transformed/core-1.10.1/META-INF/com/android/build/gradle/aar-metadata.properties.

 The minCompileSdk (33) specified in a
 dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
 is greater than this module's compileSdkVersion (android-29).
 Dependency: androidx.annotation:annotation-experimental:1.3.0.
 AAR metadata file: /Users/xiaobao/.gradle/caches/transforms-3/b0f7cc7fb17f410187f6f2d5921c535b/transformed/jetified-annotation-experimental-1.3.0/META-INF/com/android/build/gradle/aar-metadata.properties.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3/userguide/command_line_interface.html#sec:command_line_warnings

麻烦提供一下你的 pubspec.lock 的内容我对比下

可以更新下最新代码尝试，刚好升级了一批依赖


slow transition from page with large number of  elements

Hi,
I have a page with a large number of Link elements (around 6000, it's a large table). When I navigate away from this page by clicking one of the links, react-router5 directly results in a 6 minute delay in rendering. Is there a way to work around or otherwise disable this behaviour?
Thanks
[edit]
I initially thought this was caused by the unsubscribe functionality, but that's not quite right. For additional information, the delay seems to be caused by the logic in withRoute.js:
                    this.routeState = {
                        route,
                        previousRoute
                    }
                    if (this.mounted) {
                        this.forceUpdate()
                    }

It appears that on TRANSITION_SUCCESS, this function is called for every Link, forcing an update (and thus, presumably, a re-render). I'm not very familiar with the internals of router5 but this seems to be the source of the slowdown.
As an experiment I commented out this.mounted = true in componentDidMount and the navigation time went from 6 minutes to about a second.

You can use BaseLink instead, which isn't connected to route changes, or implement your own custom link component.

that's worked, thank you!


Custom backend support

For now, Candle only has a fixed set of backends (CPU, CUDA and Metal). Some other frameworks like PyTorch or Burn supports custom backends.
This PR contains changes enabling to create and use custom backend.
This can be useful when user wants to use a different GPGPU framework (like OpenCL) or some specific hardware.
The PR consists of two parts:

Refactoring of BackendDevice and BackendStorage traits (removed new method, made location an associated type, renamed some methods to avoid ambiguity and other minor changes) and implementing them also for Device and Storage.
Creating CustomDevice and CustomStorage that encapsulate a custom BackendDevice and BackendStorage implementation (which is relatively tricky because these traits contain associated types and generic methods, but Tesnor doesn't have generic parameters, so implementation should go through dynamic dispatch, but this isn't exposed to user) and making types used by these traits public.

Has it a chance to be merged?
If it is undesirable to stabilize backend API, then custom backends may be enabled by feature with a note that it is unstable.

+1 to be able to implement and running another backend without needing to fork would be very useful.

I don't think this would be in the immediate priorities of the project. The diff is pretty large and it would be quite tricky to review it and assess that it doesn't break anything, we would have to brainstorm about how to make it in a way that the changes are less invasive than this. Before making such changes, I would suggest asking in the discord server if there are some thoughts about it just to avoid putting a lot of effort in such PRs.

+1 on supporting custom backends in some way. This also allows wrapping an existing backend to modify some of its operations without needing to fork.


Tc mz python webserver

Add Python webserver sources, etc. for the MicroZed BSP

Agreed.  I will do this.
--Tom
From: tnizan-witekio @.>
Sent: Friday, November 12, 2021 9:57 AM
To: Avnet/meta-avnet @.>
Cc: Curran, Tom (EM) @.>; Author @.>
Subject: [External] Re: [Avnet/meta-avnet] Tc mz python webserver (PR #41)
@tnizan-witekio requested changes on this pull request.

In recipes-core/images/avnet-image-full.inchttps://github.com/Avnet/meta-avnet/pull/41#discussion_r748352017:

@@ -110,6 +110,15 @@ IMAGE_INSTALL_append_minized-sbc = "\

     wpa-supplicant \

"
+IMAGE_INSTALL_append_mz = "\
If you rebase your changes on top of the new 2021.1 branch, you will see that we use the python webserver for minized, mz and pz = all zynq platforms.
So we can remove those packages from IMAGE_INSTALL_append_{minized/mz/pz}, and add them in IMAGE_INSTALL_append_zynq
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Avnet/meta-avnet/pull/41#pullrequestreview-804892529, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADCNSOHQN7TJ2VAJFNDASL3ULUTM5ANCNFSM5H43MIRA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Expose console port, add debug image flag

Thinking a little more, this alone isn't quite enough. We as a client need to know where the loghash_dict for the prompt is too.


Flaky counts a skipped unittest test as a failure

If a test is skipped via unittest.skip(), it's counted as a failure and rerun. (If it's skipped via pytest.mark.skipif, it seems to work fine.)
This causes the test to get reported multiple times (it's correctly reported as skipped each time in the xml), which causes problems with xdist again (trying to remove tests from the queue multiple times).

It seems like this is the same as issue #43.


feat: move pkg syncmap

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

Move pkg syncmap path.

Related Issue

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #859 (d024e84) into main (3f6e672) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #859      +/-   ##
==========================================
+ Coverage   41.40%   41.41%   +0.01%
==========================================
  Files         103      103
  Lines        8047     8047
==========================================
+ Hits         3332     3333       +1
+ Misses       4304     4303       -1
  Partials      411      411

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
41.41% <ø> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

cdn/supervisor/task/manager.go
10.09% <ø> (ø)

client/daemon/peer/peertask_stream.go
53.82% <0.00%> (-1.53%)
:arrow_down:

client/daemon/peer/peertask_base.go
47.87% <0.00%> (+1.21%)
:arrow_up:


[Codegen] Remove depreciated vector distribution transform codegen path

Removes iree_vector_ext.layout attribute for VectorExt and other related passes which were required for the vector distribution transform dialect path. This path is now depreciated.

Nice! Does this mean that this code can now also be removed from this header:
https://github.com/iree-org/iree/blob/1654ce6dd4cb36061b453e37892d40da2f493bcf/compiler/src/iree/compiler/Codegen/Dialect/GPU/IR/IREEGPUAttrs.h#L71-L85
Meaning, that struct OpaqueMmaLayout can move into IREEGPUAttrs.cpp, and the getOpaqueMMALayout function becomes static in IREEGPUAttrs.cpp?

Nice! Does this mean that this code can now also be removed from this header:
https://github.com/iree-org/iree/blob/1654ce6dd4cb36061b453e37892d40da2f493bcf/compiler/src/iree/compiler/Codegen/Dialect/GPU/IR/IREEGPUAttrs.h#L71-L85
Meaning, that struct OpaqueMmaLayout can move into IREEGPUAttrs.cpp, and the getOpaqueMMALayout function becomes static in IREEGPUAttrs.cpp?

Yes! Do you want me to do it in this patch or a seperate patch?

Yes! Do you want me to do it in this patch or a seperate patch?

Up to you!

Yes! Do you want me to do it in this patch or a seperate patch?

Up to you!

I'll do it in a follow up patch then :)


About the training set

Hi, may I ask how large the training set is and when will it be released?

Hello! NAVSIM uses the OpenScene dataset. The full trainval split of this data is currently available on the OpenScene repository:
https://github.com/OpenDriveLab/OpenScene/blob/main/docs/getting_started.md#trainval-set
Its size is approximately 2TB. We are working on preparing a download script as well as a subsampled version of this data for training (around 300GB). These are expected to be released by the end of March.

Thanks for your prompt reply!!


[CIT-577] Update postinst script of tedge-agent

Proposed changes
By this change, tedge-agent user can run sudo /etc/tedge/sm-plugins/[plugin].
Restriction:

Due to security issue, we force a plugin name must start with [a-z]. If we use wildcard like /etc/tedge/sm-plugins/*, hacker can execute /etc/tedge/sm-plugins/../../anything.
sudoers doesn't accept regrex. See man page: https://www.sudo.ws/man/sudoers.man.html#Wildcards

Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Hackers could aso use /etc/tedge/sm-plugins/a/../../anything afterwards, right?

I tested, actually in this case, you are asked to input the password of tedge-agent. So, seems it's safe.
No password is asked in this case: /etc/tedge/sm-plugins/**a**/../apt.

Codecov Report

Merging #436 (19fb0ad) into main (b8950d2) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #436      +/-   ##
==========================================
- Coverage   62.62%   62.57%   -0.05%
==========================================
  Files         107      107
  Lines        6745     6731      -14
==========================================
- Hits         4224     4212      -12
+ Misses       2521     2519       -2

Impacted Files
Coverage Δ

mapper/thin_edge_json/tests/test_suite.rs
88.88% <0.00%> (-0.59%)
:arrow_down:

common/certificate/src/lib.rs
95.34% <0.00%> (-0.18%)
:arrow_down:

common/mqtt_client/src/lib.rs
25.91% <0.00%> (-0.10%)
:arrow_down:

...mapper/src/sm_c8y_mapper/smartrest_deserializer.rs
96.66% <0.00%> (-0.04%)
:arrow_down:

sm/tedge_agent/src/agent.rs
0.00% <0.00%> (ø)

sm/plugin_sm/src/plugin_manager.rs
50.60% <0.00%> (ø)

sm/plugins/tedge_apt_plugin/src/main.rs
0.00% <0.00%> (ø)

tedge/src/system_services/managers/bsd.rs
0.00% <0.00%> (ø)

tedge/src/system_services/managers/openrc.rs
0.00% <0.00%> (ø)

common/batcher/src/batcher.rs
93.15% <0.00%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


Normalization not working on Windows

@BeatPlus moved your comment to a new issue:
If your development environment is run in Windows, there is a bug in Nextjs path rendering. #4 fixes this

This project actively supports Linux and WSL (Windows Subsystem for Linux), so I am not yet sure how much effort I can put into Windows. I'd be surprised if #4 is the only change needed to make things work on native Windows. There might be other places in the code, where fore-slashes are used (there are also calls to the file-system).
Therefore, before merging this PR I'd like to get a better overview what is needed here to fully support Windows. If you could identify the places that need to be changed/checked: that would be great. I also welcome any proposals on how this repo can sustainably support Windows, maybe we need to implement some automatic tests for that?

Thanks @styxlab , I  managed to get my development environment running but your guess that something else must be broken is valid. I will migrate to WSL but I will commit in this PR additional bug fixes that I spot

@BeatPlus Super that you can give WSL a try - it's a much better experience when working with this repo but also with other nodejs driven applications. I will close the PR, but you can always open a new issue (or PR) for your upcoming findings.


Missing R4 constant + profile?

Noticed that some R4 resources, for example ServiceRequest is missing from the file src/constants.js and doesn't have a profile inside src/server/profiles/ , is that something you might have missed, is it planned for further patches or am I missing something?

Hi @mihaixyx, thanks for pointing this out. We have support for this in our 2.0 branch which we hope to release soon, but we can probably add it back here as well fairly soon.
This version has a lot of manual updates and our 2.0 has a lot more automated updates, so this was just a case of us developing both versions side by side and not getting to backport some of the new R4 capabilities yet.

2.0.0 is released now and this is supported.  If you cannot upgrade, we can retro fit it but it may not happen til after dev days (June 10 -12) unless someone else can contribute. We have a few things we are trying to wrap up before then and will be a little busy until after that.


Feature - ImageDownloaderDelegate

This PR adds the ability to provide different auth credentials on a per-request basis. All public APIs have docstrings, tests have been update and a new section has been added to the migration guide.

cc @kcharwood

Based on an offline conversation with @kcharwood, I'm going to decline this PR and switch over to adding a custom instance property on UIImageView to allow users to override the class ImageDownloader with a different instance.


detached or non-detached execution should be controled by a switch

to choose from detached or non-detached run should not be done by choosing different execution method but by the command line / test plan switch
Imagine the situation where the execute type is set in L1. One could want to run the test while seeing the console output in real-time while executing it by an automation might want to use detached regime. The execution type should be e.g. beakerlib for both cases but handled differently in different situations.

So the plan with #302 is to completely move the framework selection to L1 metadata (with some backward compatibility handling to prevent regressions with the old configs) which should result into what, I believe, is your described scenario. You select on the commandline or in the plan which executor should be used. Pipeline would have some default. You can override from the command line as needed and you can specify it in the plan as well.

I believe this has been covered by #302. Feel free to reopen if not.

I believe this has been covered by #302. Feel free to reopen if not.