[HxInputDate] FocusAsync() not working + other indirect input-components might be also affected

Discussed in https://github.com/havit/Havit.Blazor/discussions/785

Originally posted by chobo2 April  4, 2024
Hi
I am trying to use "FocusAsync" but it never focuses on it.
I tried taking the default code and added a reference
<HxInputDate Label="Date" @bind-Value="@value" @ref="testInputDate" />

@code {
    public DateTime value { get; set; }
   private HxInputDate<DateTime> testInputDate;
   protected override async Task OnAfterRenderAsync(bool firstRender)
    {
        if (firstRender)
        {
              testInputDate().FocusAsync()
        }
    }
}

In my actual application I get an error telling me that it can't be done after first render or soemthing like that though it could be because the HxInputDate is in a child component but since I can't even get it working with the example code I thought I would start there.
Also on a side note, is there away to get the calendar to put when you tab into a HxInputDate?

Some input-components use indirect setup where the input-element to be focused is contained in internal component being wrapped by the HxInputBase<>-derived component itself.
The HxInputBase<>.FocusAsync() call has to be passed to the underlying internal component and the contained input-element.

Some input-components use indirect setup where the input-element to be focused is contained in internal component being wrapped by the HxInputBase<>-derived component itself.
The HxInputBase<>.FocusAsync() call has to be passed to the underlying internal component and the contained input-element.

[x]  HxInputDate
[x]  HxInputDateRange
[x]  HxAutosuggest
[x]  HxMultiSelect
[x]  HxInputTags
[x]  HxSearchBox

Thanks for checking into this, I just saw this message now.
I did try in the latest version and confirm the cursor does not start in that box.
Is it possible to set it to popup the calendar as well? I can't get the calendar to popup when I tab into those boxes or if I do this FocusAsync() which leads to having to do a secondary click.

@chobo2 Thanks for the feedback. I added the logic to show the corresponding dropdown when the input is focused with FocusAsync().


Replace multiple maps with a single map and use a follower struct.

Scope & Purpose
There were multiple maps mapping follower ids to different information. This PR creates a struct that holds all this information and reduces everything to a single map.

Sanitizer run: https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/31150/


Proposed changes for a more Pythonic code

There is a bunch of alerts throwed by peps8 validators, so this is an attempt to address those warnings.
This code should have no problems with any functionality because they are only for styling porpoises.

Thanks! :-)
When I have some spare time, I will refactor bootcamp's code
You did a great start

Thanks a lot, I hope this were helpful.


Folding not detecting DO/END blocks

Blocks aren't always getting detected for folding.  When mousing over line 668 I see the the folding indicator, but not over line 705 in the screenshot below.

[2024-12-12T13:30:17,150] [INFO] Command line arguments:
[2024-12-12T13:30:18,165] [INFO] LanguageServerInfo: 1.18.0-23783bf -- ClientInfo: Visual Studio Code 1.96.0 -- JVM: Eclipse Adoptium 17.0.13+11
[2024-12-12T13:30:18,165] [INFO] Client Capabilities: WS Config true -- WS Folder true -- Diagnotics true -- Symbol Hierarchy true -- Document Highlight true
[2024-12-12T13:30:18,165] [INFO] Semantic tokens support: true - Multiline tokens: false - Overlapping tokens: false

Will have a look, thanks for the report !

Fixed


User can reactivate his deactivated account!

I am logged in as a member user,
The sys admin deactivates my account
The system does not suspend me, I can stay logged in (see #199)
I can actually use all functions available and e.g. change my password
In the change password window I can even "reactivate" my account!!
see image

Screenshots

Desktop (please complete the following information):

OS: Windows 10 Pro N, 1903 - 18362.418

Browser Google Chrome, 78.0.3904.97

Version Knora App, 1.6.2

Additional context
Add any other context about the problem here.

this issue has been moved to YouTrack: DSP-344


Generate dictionary of locations to jump to on map

What's wrong

After clicking a state, the map jumps to a particular initLat and initLon regardless of the state clicked

What done looks like

Check the geographic state clicked in the global state and then look it up in a dictionary of lat longs of the state capitals, e.g. { "AL": { "lat": XXXX, "lon": XXXXX}, ...}.  I'm sure there's a googleable list that can be used.
Pass this lat and lon to initialize the second map.
Save this dictionary as a separate file instead of inlining it in the component, so we could swap it out with centroids or university locations in the future based on feedback.
ss

Examples:
https://github.com/vega/vega/blob/main/docs/data/us-state-capitals.json
https://gist.github.com/mcwhittemore/1f81416ff74dd64decc6
You'll have to look up and edit in the Canadian provinces and maybe some territories?


Newest version of Towelette(2.0.1) crashes the game

https://pastebin.com/uyc1kCpk
Error report.

Adorn has to release an update that's compatible with Towelette 2.x.x. Not fixable from my side.


Include InferSecuritySchemes in deep copy of SwaggerGeneratorOptions

#2540 -> same PR, only that one some extra fixes


dart:html.Location duplicates dart:uri.Uri

This issue was originally filed by @seaneagan

The dart:html Location interface duplicates the members of dart:Uri uri.  It would be better to kill Location, and have something like:
interface Window {
  //...
  String get location();
  void set location(String location);
  void replaceLocation(String location);
  List<String> get ancestorOrigins();
  void reload();
}
Then to access a Location-like object just do:
final uri = new Uri.fromString(window.location);
print("path: ${uri.path}");
// etc.
Note:  see also issue #2711

By design. The Location class has methods like reload and replace that don't align with the shared Uri class in dart:core


vbox: fix vbox race with unregistervm

There is a random race with VirtualBox where it will not release its internal lock in time before we issue the unregistervm command.  This adds a sleep as a workaround.
I've been hitting this more and more lately.  I think we need it in for 0.3.

@nathanleclaire PTAL

It is not guaranteed that 1 second sleep will fix the problem completely... Do we have a gameplan on detecting it more elegantly in the future?

Would utils.WaitFor a Stopped state work?

Hm, we already check it in Stop method :(
This seems to fix the issue so, for now at least until we can find a more elegant solution, LGTM


[core] Fix some errors when porting demos to TypeScript

Porting https://github.com/mui-org/material-ui/tree/master/docs/src/pages/demos to typescript arrise some errors, see my commit's comments.
Thanks for merging

@PavelPZ Thank you


Rollbacks for Unit Testing

Im using serverless-dynamodb-local to do some unit testing.
After each test I need to clear out all the db tables ready for the next test. In other framework and DBs I've been able to 'rollback' all the changes after each test, therefore starting with a clean set of tables.
Is there any way to perform rollbacks?
Im currently having to rebuild the database before every test and its really slowed up my tests.

@GazEdge Have you tried using -inMemory flag when starting DynamoDB local. This way after the test execution if you stop and start the database, the database should be cleared.

-inMemory — DynamoDB runs in memory instead of using a database file. When you stop DynamoDB, none of the data is saved. You can't specify both -dbPath and -inMemory at once.

Yeah tried that - takes way too long to start up the server again after every test. My workaround currently is to delete every table and re-create it.  Create a plugin lib/serverless-jest-dynamodb/index.js

The purpose of this file is to run jest through Serverless. So I can have the tables definition and pass them as environment variables to my tests and create the tables there.

const jest = require("jest").runCLI;

class ServerlessPlugin {
  constructor(serverless, options) {
    this.serverless = serverless;
    this.options = options;

    this.commands = {
      test: {
        usage: "Run unit tests",
        lifecycleEvents: ["run"]
      }
    };

    this.hooks = {
      "test:run": this.runTests.bind(this)
    };
  }

  get dynamodbTables() {
    const { Resources } = this.serverless.service.resources;

    return Object.values(Resources)
      .filter(resource => resource.Type === "AWS::DynamoDB::Table")
      .map(resource => resource.Properties);
  }

  async runTests() {
    const DYNAMODB_TABLES = JSON.stringify(this.dynamodbTables);

    Object.assign(process.env, {
      ...this.serverless.service.provider.environment,
      DYNAMODB_TABLES,
      NODE_ENV: "test"
    });

    return jest({ watch: this.options.watch, runInBand: true }, [
      this.serverless.config.servicePath
    ]);
  }
}

module.exports = ServerlessPlugin;

2. Create a dynamo client lib/dynamodb-client/index.js

The purpose of this file is to expose a dynamodb client which knows to connect to localhost or cloud depending on NODE_ENV

import AWS from "aws-sdk";

var isOffline =
  process.env.NODE_ENV === "development" || process.env.NODE_ENV === "test";

export const options = {
  region: "localhost",
  endpoint: "http://localhost:8000"
};

export const doc = isOffline
  ? new AWS.DynamoDB.DocumentClient(options)
  : new AWS.DynamoDB.DocumentClient();

export const raw = isOffline ? new AWS.DynamoDB(options) : new AWS.DynamoDB();

3. Create a test-utils/global-setup.js

The purpose of this file is to initialize the dynamodb local process after all tests.

const DynamoDBLocal = require("dynamodb-local");
const path = require("path");

DynamoDBLocal.configureInstaller({
  installPath: path.join(process.cwd(), ".dynamodb")
});

module.exports = () => {
  console.log("\n");
  return DynamoDBLocal.launch(8000, null, ["-inMemory"]);
};

4. Create a test-utils/global-teardown.js

The purpose of this file is to stop the dynamodb local process.

const DynamoDBLocal = require("dynamodb-local");

module.exports = () => {
  return DynamoDBLocal.stop(8000);
};

5. Create a test-utils/test-setup.js

The purpose of this file is to create tables before each test and then remove it after the test passes.

import { raw, options } from "lib/dynamodb-client";

const DYNAMODB_TABLES = JSON.parse(process.env.DYNAMODB_TABLES);

beforeEach(async () => {
  try {
    await Promise.all(
      DYNAMODB_TABLES.map(table => raw.createTable(table).promise())
    );
  } catch (error) {
    console.log("Error creating tables");
    console.log(error.message);
  }
});

afterEach(async () => {
  try {
    await Promise.all(
      DYNAMODB_TABLES.map(({ TableName }) =>
        raw.deleteTable({ TableName }).promise()
      )
    );
  } catch (error) {
    console.log("Error removing tables");
    console.log(error.message);
  }
});

6. Create functions/profile/create-profile/create-profile.test.js

The purpose of this file is to write the spec for the function

import createProfile from ".";
import event from "./event.json";

test("function:createProfile", async () => {
  const { profile } = await createProfile(event);
  expect(profile.profileId).toEqual(expect.any(String));
  expect(profile).toMatchObject(event.arguments.profile);
});

7. Create functions/profile/create-profile/index.js

The purpose of this file is to write the function code

import { doc } from "lib/dynamodb-client";
import uuid from "uuid";

const createProfile = async (event, context) => {
  const profile = {
    profileId: uuid.v1(),
    // userId: cognito...
    ...event.arguments.profile
  };

  const params = {
    TableName: process.env.PROFILES_TABLE,
    Item: profile
  };

  await doc.put(params).promise();
  return { profile };
};

export default createProfile;

Hope it helps you :)


Random fail on SEGV_MAPERR

when I run the latest release v1.0.0-38 on lambda, I get random (1 out of cca 30 - 40 runs) SEGV_MAPERR fails.
this happens with the with a bit more complex html files (so far no luck with isolating the issue, any hint very will be much appreciated)
simple
hello world
 html seems to work ok (120+ tries)
set of flags:
'--headless',
'--disable-gpu',
'--single-process',
'--no-sandbox',
'--window-size=1920,1200',
'--virtual-time-budget=100',
'--disable-extensions',
'--incognito',
'--v=99',
'--enable-logging=stderr',
'--print-to-pdf=/tmp/pdf_output.pdf',
'file:///tmp/my_html_file.html'

also tried with these additional flags (stiil the same fail)
'--no-zygote',
'--deterministic-fetch',
'--profile-directory=/tmp/profileDir',
'--user-data-dir=/tmp/userDataDir'

stacktrace:
[0225/185929.698092:WARNING:resource_bundle.cc(368)] locale_file_path.empty() for locale

prctl(PR_SET_NO_NEW_PRIVS) failed

[0225/185929.712490:ERROR:gpu_process_transport_factory.cc(1009)] Lost UI shared context.

[0225/185929.713155:VERBOSE1:webrtc_internals.cc(109)] Could not get the download directory.

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 59: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 68: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 68: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 79: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 79: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 79: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 88: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39:
Having multiple <family> in <alias> isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39:
Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple <family> in <alias> isn't supported and may not work as expected

[0225/185929.830975:WARNING:histograms.cc(40)] Started multiple compositor clients (Browser, Renderer) in one process. Some metrics will be disabled.

[0225/185930.352359:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Aviator' log
[0225/185930.352389:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Icarus' log
[0225/185930.352395:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Pilot' log
[0225/185930.352400:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Rocketeer' log
[0225/185930.352407:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Google 'Skydiver' log

[0225/185930.352412:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server
[0225/185930.352418:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: DigiCert Log Server 2
[0225/185930.352423:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec log
[0225/185930.352428:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Vega' log
[0225/185930.352433:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Symantec 'Sirius' log
[0225/185930.352438:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: WoSign log
[0225/185930.352443:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi Gen2 CT log
[0225/185930.352447:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: CNNIC CT log
[0225/185930.352452:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: StartCom log
[0225/185930.352457:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Sabre' CT log
[0225/185930.352462:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Comodo 'Mammoth' CT log
[0225/185930.352467:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Izenpe log
[0225/185930.352472:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Venafi log
[0225/185930.352477:VERBOSE1:multi_log_ct_verifier.cc(75)] Adding CT log: Certly.IO log
[0225/185930.352485:VERBOSE1:proxy_service.cc(958)] PAC support disabled because there is no system implementation

[0225/185930.371357:ERROR:instance.cc(49)] Unable to locate service manifest for metrics
[0225/185930.371379:ERROR:service_manager.cc(890)] Failed to resolve service name: metrics

[0225/185930.390918:ERROR:gl_implementation.cc(292)] Failed to load /var/task/bin/libosmesa.so: /var/task/bin/libosmesa.so: cannot open shared object file: No such file or directory
[0225/185930.390940:VERBOSE1:gpu_init.cc(307)] gl::init::InitializeGLNoExtensionsOneOff failed

[0225/185930.876534:VERBOSE1:network_delegate.cc(30)] NetworkDelegate::NotifyBeforeURLRequest: file:///tmp/tmp-1ifSXGRQl8Bnn

[0225/185930.890755:VERBOSE1:loader_util.cc(47)] To buffer: file:///tmp/tmp-1ifSXGRQl8Bnn

[0225/185930.893555:ERROR:gpu_command_buffer_stub.cc(611)] ContextResult::kFatalFailure: Failed to create default offscreen surface.

[0225/185930.911043:VERBOSE1:network_delegate.cc(30)] NetworkDelegate::NotifyBeforeURLRequest: blob:file:///214913db-6f34-4045-be40-a3bf5f8e6e92

[0225/185930.930992:VERBOSE1:network_delegate.cc(30)] NetworkDelegate::NotifyBeforeURLRequest: https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-beta.3/css/bootstrap.min.css

[0225/185930.931147:VERBOSE1:network_delegate.cc(30)] NetworkDelegate::NotifyBeforeURLRequest: https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.0.3/leaflet.css

[0225/185931.578162:VERBOSE1:LocalWindowProxy.cpp(229)] A context is created NOT from snapshot

[0225/185931.601193:VERBOSE1:LocalWindowProxy.cpp(229)] A context is created NOT from snapshot

[0225/185931.615839:VERBOSE1:LocalWindowProxy.cpp(229)] A context is created NOT from snapshot

[0225/185931.621532:VERBOSE1:LocalWindowProxy.cpp(229)] A context is created NOT from snapshot

[0225/185931.771033:INFO:headless_shell.cc(566)] Written to file /tmp/tmp-1AKZMmn5v6BvX.

 Core file will not be generated.

edit:
the pdf is safely written (last info before the SEGV_MAPERR bug) so it seems it just dies when trying to exit.

Hi @slimakovec — Does this happen with a beta or dev channel version? Or, an older npm version e.g. v1.0.0-7 or v1.0.0-28?

hi, I have tried beta, dev and stable (v1.0.0-38) and it randomly occurred no matter what version I tried. I even tried v1.0.0-29 and (not sure about this release number though) v1.0.0-34, still the same. To be honest, I haven't tried the v1.0.0-7, I wanted one of the latest releases.
sorry if I'm not very helpful, it's quite hard to isolate when exactly this happens :(
as I wrote - the pdf is safely written so that's okay for me


Pydantic 2: Make the tests run

We're looking to upgrade to pydantic 2, but are currently blocked by fastapi-hypermodel and some other libraries. I took the liberty to help you out with your branch and get it running to speed things up (saw your comment in #32).
Tests now pass and I think things are in order, but I'm not an pydantic internals expert. Please have a look and get in touch if you want to discuss anything.

This is fantastic, thank you so much! I've had a quick look and everything looks fine (better than fine to be honest).
I'll do a deeper dive into it tomorrow but I really can't see there being any issues.
NB: Tests are failing in GitHub Actions but that's a poetry issue. I'll try and get it fixed in main shortly so you can update the fork and that should kick everything into working again.

When you get chance, could you merge in the latest changes from main (see https://github.com/jtc42/fastapi-hypermodel/pull/34) and the tests should start passing in the CI.
Issue seems to have just been Poetry complaining about Python 3.7, which is EOL anyway.

I rebased from master to get your fixes in. I've also integrated the new version in the software that we're writing to get some more test coverage - which led me to find a few more issues that I've now fixed together with the pylint/black issues. Could you approve the workflow to see if the build goes through this time?

Workflow approved (I'm looking to see if there's a way I can auto-approve for this PR).
It's failing on 3.8 but I think that's just because we need to still use typing.Dict instead of dict for type hints for the time being. Should be a really quick fix.

@christoe Given how extensive these changes are, and the time you've spent on them, are you happy to be listed as a co-author in the library? It seems to me inappropriate for me to still be listed as the sole author given how much you've contributed to the code.

@jtc42: I'll let that be up to you. It's still your original idea and I've only tried to adapt the code to support our use case.
I've also tried fixing the mypy issue with dict vs. typing.Dict.


[SP-4063][PDI-16790]-Miscalculation with big number data type in calculator step

-fixed

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -f core/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/test-src/org/pentaho/di/core/row/ValueDateUtilTest.java
  engine/test-src/org/pentaho/di/core/row/ValueDataUtilTest.java

Newly Fixed Tests:
org.pentaho.di.core.row.ValueDataUtilTest.testPercent2:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<1.99> but was:<1.96>
	at org.pentaho.di.core.row.ValueDataUtilTest.testPercent2(ValueDataUtilTest.java:380)

org.pentaho.di.core.row.ValueDataUtilTest.testPercent3:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<0> but was:<-1>
	at org.pentaho.di.core.row.ValueDataUtilTest.testPercent3(ValueDataUtilTest.java:414)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.core.row.ValueDataUtil

Branch Change: -2.4% :small_red_triangle_down:
Complexity Change: -3.2% :small_red_triangle_down:
Instruction Change: -5.4% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:
Method Change: -7.9% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change: -8.7% :small_red_triangle_down:
Complexity Change: -3% :small_red_triangle_down:
Instruction Change: -0.8% :small_red_triangle_down:
Line Change: -0.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change: -1.4% :small_red_triangle_down:
Complexity Change: -1.4% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

License header violations

:heavy_exclamation_mark: Couldn't find acceptable copyright on engine/test-src/org/pentaho/di/core/row/ValueDataUtilTest.java

@denisprotopopov please fix copyright year

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -f core/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/test-src/org/pentaho/di/core/row/ValueDateUtilTest.java
  engine/test-src/org/pentaho/di/core/row/ValueDataUtilTest.java

Newly Fixed Tests:
org.pentaho.di.core.row.ValueDataUtilTest.testPercent2:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<1.99> but was:<1.96>
	at org.pentaho.di.core.row.ValueDataUtilTest.testPercent2(ValueDataUtilTest.java:380)

org.pentaho.di.core.row.ValueDataUtilTest.testPercent3:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<0> but was:<-1>
	at org.pentaho.di.core.row.ValueDataUtilTest.testPercent3(ValueDataUtilTest.java:414)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: -0.1% (click to expand)
org.pentaho.di.core.row.ValueDataUtil

Branch Change: -2.4% :small_red_triangle_down:
Complexity Change: -3.2% :small_red_triangle_down:
Instruction Change: -5.4% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:
Method Change: -7.9% :small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -4.4% :small_red_triangle_down:
Complexity Change: -5.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.4% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -9.1% :small_red_triangle_down:
Complexity Change: -6.2% :small_red_triangle_down:
Instruction Change: -10% :small_red_triangle_down:
Line Change: -10% :small_red_triangle_down:

@mchen-len-son done


Add Nvidia 4.1 inference code support

Hi, I am interested in the progress on this and I'm curious if i can help implement this.

Thank you @Oseltamivir for your interest. Currently we are blocked by this issue which is preventing us from checking Nvidia code on a custom system.


[Adds to #100] sticky nav bar feature for non-index pages.

Builds on #100 to apply to all non-index pages.

Hi @danielramirez0
Sticky navbar support added in https://github.com/gurusabarish/hugo-profile/commit/70ea254099da0239185824c04adf77af33aafa7a for all pages


Add raw airspeed differential press and temp message

This PR adds Raw Airspeed Data message for use in transmitting the differential pressure and temperature directly to Autopilot or any other consumer where it will be converted into True Airspeed.

Please align the comments and add a new line in the end of the message definition.
Calling in @EShamaev. Does this make sense to you? Any comments?

@pavel-kirienko I have fixed the issues.

Thank you. We're waiting for Eugene to approve/reject it now.

I would also advise to have static pressure and pitot temperature reported.

Makes sense. The following then should be explicitly specified in the comments then:

What exactly is understood under the plain temperature field. Perhaps it should be renamed.
How do we represent the unknown quantities, and which ones are required. Normally we use NaN to indicate that a certain quantity is unspecified.

Temperature should be OAT. Second one can be pitot_temperature.
If it is not available - NaN is OK.

Okay. Do we need error variance estimates for all of the reported parameters?

If we have 4 params, then matrix will be good as they are related to each other.

OK, thanks for your inputs Eugene.

Some flags would be nice as well. Most essential: HEATER_WORKING, HEATER_OVERCURRENT, HEATER_OPENCIRCUIT.

For reference, here is a list of ARINC429 labels usually sent from airdata computers:

@EShamaev can you specifically list out the additional messages I should add. For my purposes, I am using a simple module based on MS4525 which only reports Diff Pressure and Static Air Temperature, and no additional processing is being done before sending that data over UAVCAN. If you feel additional params should be listed, I would gladly add them to this PR. If you feel like adding them, I am fine with that as well.

When message is added to DSDL there will be no chance to change it in future. So we need to carefully think what is needed for broad range of devices that might be using it.
I propose to have following:
static_pressure [Pascal]
differential_pressure [Pascal]
OAT [K]
pitot_temperature [K]
variances [4x4]
flags [HEATER_WORKING, HEATER_OVERCURRENT, HEATER_OPENCIRCUIT]
Also correct naming should be Raw Air Data. I also have the same device developed and was going to post a PR regarding addition of such packet, but I have real external OAT sensor, pitot heater with temp and current sensors and static pressure sensor.
Basicly the proposed list is all data that is coming from a real world (big planes) pitot sensors / airdata sensors.
The pitot temperature and heater state is extremely important for determining the icing on pitot.
Also regarding MS4525 you mentioned, it is correct to say that it is reporting the sensor's temperature and not the "Static Air Temperature", however for such use case we consider this as OAT.

We need two different temperatures for static and dynamic pressure. I tend to find that the temperature compensation from the sensors doesn't work and we need the full data in the autopilot in order to post-compensate.

Then please add 2 separate temperatures. Sensor temperature is not OAT. If a device do not have OAT sensor it may broadcast sensor's temperature as OAT but there are devices with external OAT sensor.

ok will do

We need two different temperatures for static and dynamic pressure. I tend to find that the temperature compensation from the sensors doesn't work and we need the full data in the autopilot in order to post-compensate.

The sensor that is sending this message is "smart" and has it's own MCU. I am thinking now that this compensation should be in the sensor, not in AP.
Would like to hear other opinions on this.

@EShamaev There could be cases where compensation is not implemented for any reason, but AP does have Temperature based calibration feature like in the case of PX4, where user can calibrate wrt temperature on there end.

Alright, these 2 temperatures should be in message then, but I still think that calibration should be done on the sensor. (For newly developed devices)

@EShamaev @pavel-kirienko I have made the suggested changes. Please review and do the needful.

I know I don't normally comment on these things, and I could be missing the definition, but what are the expected flags for no data? NaN's or a negative number? I know some of the other files have comments that say unknown fields should be NaN but I'm not seeing that in this one?

I know some of the other files have comments that say unknown fields should be NaN but I'm not seeing that in this one?

It's a common convention in UAVCAN (it is mentioned in the specification) to use NaN as a placeholder for unspecified values. It should be stated explicitly in the definition here though in order to avoid confusion. @bugobliterator could you please add that? Thanks!

@pavel-kirienko @EShamaev made the suggested change. Please review.

@pavel-kirienko @EShamaev Made the fixes. Can you review...

@pavel-kirienko made the changes to variable.

I am happy with this

Thank you, everyone.


Inconsistency: "Dangling Comma" on multiline data structures and function calls

Description
There is a project-wide inconsistency within Sir Lancebot's code. For multiline data structures and function calls such as
foo = [
    "yeet",
    "cat",
    "lololol"
]

, some people think we should add a trailing/"dangling" comma at the last line while others don't.
In the code, there are instances where the dangling comma is used and instances where it is not. This can be misleading for new people wanting to contribute (such as me, last time I was discussing with ToxicKidz and Kronifer on this problem, I thought dangling commas were good practice).
Here are my thoughts on why these end-trailing commas are beneficial:

Some argue that such a miniscule change won't affect readability and instead simply adds extra stuff, but I think that it makes code more symmetrical and pleasant on the eyes (all lines will have the same format).
Easy extendability: if one needs to add one more entry, this will prevent them from forgetting to add a comma before newlining.
There are multiple articles on the Internet giving even more reasons, such as easy copy-paste code manipulation.

 Note that the use of NO dangling comma is more popular... however my thoughts still stand.
Possible Solutions
Vote and choose on one way: either delete all dangling commas or add them to ones without dangling commas. IMO it would also be a good idea to enforce the result - either delete or add - in the lint, and add it to our style guide.
Would you like to implement a fix?

[ ] I'd like to implement the bug fix
[x] Anyone can implement the bug fix

number 2 can just be avoided by not being stupid

copy-pasting code for an open source contribution is frowned upon unless you wrote it somewhere else

@Kronifer for number 2, everyone make mistakes. For number 3, I mean this kind of copy-paste https://medium.com/@nikgraf/why-you-should-enforce-dangling-commas-for-multiline-statements-d034c98e36f8

So there shouldn't need to be a discussion about this nor should we have to go back and update our codebase.
Dangling commas should be the standard, see PEP8. It also ensures the git blame is accurate if someone adds another option to an already existing list.
Our style guideline falls back to PEP8 for this, so there really isn't a need for a discussion about this.

@janine9vn currently it's not the standard. Should we do a project-wide refactoring?

No. Adding trailing commas isn't critical enough to warrant a project-wide refactoring. Those types of PRs are generally bad ideas and hell to review. While we try to maintain a standard this is still Sir Lancebot, which is a project designed for new people to learn how to contribute to open source projects. It's not critical that we follow the style guideline 100%, but when noticed we should try to follow it and make sure the code follows it.

@janine9vn got it. Thank you!

@janine9vn

While we try to maintain a standard this is still Sir Lancebot, which is a project designed for new people to learn how to contribute to open source projects. It's not critical that we follow the style guideline 100%

I noticed the same kind of inconsistency in our main bot project as well... would that be not worth a refactoring either? I'm sure this can be automated with some more Python Magic :tm:

No, it's not worth refactoring on any of our projects.
Minor modifications like this can be amended as and when the code is touched, if we have automated PRs with hundreds of lines changed then it just results in conflicts that someone has to work out. It's the same thing as typehints, we're not going to retroactively upgrade them to 3.9 style (dict[str, str] vs. typing.Dict[str, str]) because it doesn't bring us anything, it just adds extra labour for the poor soul who has to ensure that no conflicts crop up.

@jb3 alright. Thank you for explaining this, I didn't realize that this kind of refactoring can arise conflicts.


Show Union profiles differently than Intersection profiles

Consider making a visual cue distinguishing Intersection profiles from Union profiles.  I like the monotone interface, but maybe you can shade them differently.

I did originally have the intersect and union symbols at the front of the profile name, but it didn't look too good. Maybe just having them slightly tinted one way of the other will be a strong-enough visual cue.

As of commit c2e71b5caab9044623222934208e6b514fe7d3fb, Interesection profiles will have a slight orange-ish pastel tint applied to them, and Union profiles will have a slight green-ish pastel tint applied to them.


Check iterators

Username: kasperl
When we have code like this:
   MyClass m = ...;
   for (var x in m) {
     ...
   }
it would be useful to get a warning or a hint if m doesn't implement the 'iterator' getter. Not sure if this is covered by the spec, but it might be (in which case it should be a warning).
////////////////////////////////////////////////////////////////////////////////////
Editor: 0.1.2_r28706 (2013-10-16)
OS: Linux - i386 (3.2.5-gg1336)
JVM: 1.7.0-google-v5
projects: 1
open dart files: 11
auto-run pub: true
localhost resolves to: <IP_ADDRESS>
mem max/total/free: 1933 / 684 / 147 MB
thread count: 32
index: 408792 relationships in 86532 keys in 297 sources
SDK installed: true
Dartium installed: false

This is done as of: cb7aa02.


Don't send credentials over the wire with SSL on

Don't send credentials over the wire with SSL on. This fix does
the unenrypted check with fake credentials first, while checking
for valid exception about fake credentials.

alternative solution to https://github.com/ManageIQ/manageiq/pull/3217

https://github.com/ManageIQ/manageiq/pull/3218 wins :-)

haha, does it?  I was just asking questions :stuck_out_tongue:
@blomquisg Can you look here and at the other PR and give some thoughts?  I kind of like the other one better as I'd assume SSL first seems more appropriate anyway.


Search bar fixed

Issue #68
made the search bar visible
before

after

@Spandan-Bhattacharya plz check

Can the bar be made such that it's opacity decreases when it's selected?
The black border is not looking too good with it's surroundings, i think.

@Spandan-Bhattacharya  i can remove the border.

@Spandan-Bhattacharya

is this one better?

I think it doesn't need a border. It should span the entire Nav Bar.

@Spandan-Bhattacharya

this one?

Yeah now make the field more transparent

@Spandan-Bhattacharya

this?

No i meant for the input field, which is a rectangular box, spanning the full navbar height and some width.

@Spandan-Bhattacharya there's no recatangular box anymore. iremoved the thing

Then we have to bring it back😂

@Spandan-Bhattacharya u want the rectangular box with less opacity?

yes, when the input field is selected for input

@Spandan-Bhattacharya

this?

wait i am sending some reference

@Spandan-Bhattacharya just making the search solver a little darker that way ig it would feel good

you mean the writing?

@Spandan-Bhattacharya yeah

The search bar would be like this when it is selected for giving input.
It can stay the same in other times

@Spandan-Bhattacharya

i think this one matches

make the whole box, not just the outline have less opacity

@Spandan-Bhattacharya  i have synced the changes. hope it matches what you want.

@Spandan-Bhattacharya the whole box has transparent colour. its due to the background. the background image of the site is of that colour. the box has no extra colour. it only has an outline and nothing else. you can check. its the background colour.

Okay, I think i know the issue here.
I meant making the input field look like it is see through, like one can see behind the navbar(in a clouded manner).
I will give an actual design tomorrow.

@Spandan-Bhattacharya the whole box has transparent colour. its due to the background. the background image of the site is of that colour. the box has no extra colour. it only has an outline and nothing else. you can check. its the background colour.

Yes i understand that.

@Spandan-Bhattacharya what about this one?

@Spandan-Bhattacharya

this is how it looks when selected.

looks like this when not selected.

Okay, This is unfortunately not what i am looking for, I will send you a design tomorrow.

And thank you for not getting irritated at this

@Spandan-Bhattacharya no no its ok. :)
yeah plz send me the reference tomorrow.

@Spandan-Bhattacharya can u send me the reference picture?

@Spandan-Bhattacharya will u provide me a reference picture plz ?

Yeah sorry i got a little busy, will send it shortly

@Spandan-Bhattacharya hope the recent commit is what you were looking for

@Spandan-Bhattacharya tbh i have spent quite some time as well as my energy doing this. can u plz label me as medium?plz? :)


Request: add Apache Superset to the app marketplace

This issue is a:

[ ] Bug Report
[ ] Enhancement suggestion
[x] Feature request

If the issue concerns an existing Marketplace application, please tag the maintainer of the application (found in manifest.yaml) below:
Enhancement suggestions / feature requests
Apache Superset is a popular and open source business visualization app that is popular, has an active development community, and which also has an easily accessible valid Helm chart.
For those looking to quickly provision a Superset instance on Civo infrastructure, this would be a great addition to the Marketplace.
Links

Github repo (main project)
Helm chart

Hey I have already opened a pull request and implemented the feature .
check it here


Xander/carousel accessibility compliance

Changes

Bringing Carousel component to accessibility compliance by distributing proper roles and labels within the component.
Addresses #1148.
Testing

Evaluated using Cypress a11y tests. Unit & visual testing conducted as needed.
Docs

N/A

There's a unit test that's failing, so I'm going to work on that too.

Done, just had to update a querySelector (ul -> div) and a role (tabpanel -> group)


Create .travis.yml

TODO:

[x] Exclude migrations from pydocstyle check.
[ ] Add missing docstrings.
[x] Add .pydocstyle. See sample.
[x] Pin pydocstyle to current version.

Go ahead and merge it without second point in TODO list. I will fix it in PR#34, there is updated code. Here is old code I refactor some time ago in new PRs after this PR.


Image showing location of different types of content on the Windows TitleBar is incorrect

Type of issue
Other (describe below)
Description
The image that shows where the content is is incorrect. It shows the leading content to be after the sub title and before the content. However, when running with an icon, title and subtitle the leading content shows up before even the icon.
The order the documentation shows:
Icon|Title|Sub Title|Leading Content|Content|Trailing Content
The actual order displayed:
Leading Content|Icon|Title|Sub Title|Content|Trailing Content
I am running on an ARM M2 Mac with Windows in Parallels. I have not tried this on an Intel Windows machine.
Page URL
https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/titlebar?view=net-maui-9.0#create-a-titlebar
Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/user-interface/controls/titlebar.md
Document Version Independent Id
06c3bd5e-922d-562a-ca22-7c9b28602c24
Article author
@davidbritch
Metadata

ID: 06c3bd5e-922d-562a-ca22-7c9b28602c24
Service: dotnet-mobile
Sub-service: dotnet-maui

Related Issues

Associated WorkItem - 350512

@davidbritch Thanks for correcting that!
This link also shows the old image with the incorrect order.
https://learn.microsoft.com/en-us/dotnet/maui/whats-new/dotnet-9?view=net-maui-9.0

@Bowman74 Thanks for pointing that out. Fixed via https://github.com/dotnet/docs-maui/pull/2671

@davidbritch Thank you sir!


Enable strict

This is go on top of the travis changes to do more strict testing.

Fixes #65

+1 -- getting these errors as well

@razorsedge any eta on merging this?

@razorsedge, do you want to continue to maintain this module?

@mterzo, What I want and what my two young children demand are presently in conflict.  :-(  Needless to say, when I have the time I don't have the energy and when I have the energy, I don't have the time.
As for this PR, I see a few issues:

I use modulesync for the .travis.yml.  Edit .sync.yml for any overrides.
Please read through the DEVELOP.md file.  It will tell you to branch from develop and not master.
Fact ::operatingsystemmajrelease does not exist in all versions of Puppet that this module supports.
But mainly, params.pp is never a parameterized class.  If the world needs strict_variable support, PR #21 is going to be the way to do it.

We all have busy lives.
I honestly don't know what I was thinking.
We need to get strict support for puppet 4. I'll rework it this a bit and resubmit.

@mterzo I would probably use puppetlabs/ntp as example and not parameterize the params class.
@razorsedge thanks for the update, I don't think anything was meant by the question, also with so many modules moving over to the voxpupuli namespace, I think lately all public modules are starting to be asked this a lot. Allows for you to maintain it still but gives you help as well.

@mterzo @cdenneen No worries.  I've had a pretty horrible year with all sorts of life events.  I look at my growing mountain of PRs and issues and don't know where to start.  I did seriously consider donating to Puppet Community/voxpupuli when they were first created.

They so good work.  It would definitely help with keeping the dependencies up-to-date.  I checked out voxpupuli's msync and they have dropped support for older versions of ruby.

@cdenneen I thought I had followed ntp and others.  i think I cherry-picked the wrong commit. When making the branch.


Fix typo

I found and fixed one exception message that started with lower case letter.

Thanks for the PR! This terminator is not just a name but an argument name, so I think it should be kept as snake_case. Or we should add "`" to it. What do you think?

That makes sense.
I think it is easier for the reader to understand this message by adding "`".
I'll revise it if you agree.

@obregonia1 Thank you could you revise it?

Thank you!


Include ObviousResize plugin by default

I often find myself resizing splits, and absolutely love the talek/obvious-resize plugin for this.
I was wondering if this is something we'd wanna include in HVN by default, or just keep it minimal and let the user add it themselves?
As a side note: I typically bind this to shift-[hjkl] to resize, which goes nicely with ctrl-[hjkl] to move around.

There are plenty of non-minimal things in the config already so I'm open to adding it. The tricky part is what keys to bind it to. Shift-J is already taken for joining two lines together and I use it all the time.
Alternatively it is possible to customize your installation
https://github.com/begriffs/haskell-vim-now#customizing

Actually on second thought these capital letter bindings are already taken in standard vim and are very common (I use J every day). I'd say let's leave this as an optional customization rather than baking it in.


Edge Panel and Shortcuts Guide

Microsoft PowerToys version
"0.55.2"
Running as admin

[ ] Yes

Area(s) with issue?
Shortcut Guide
Steps to reproduce
In the Microsoft Edge browser, launch the "Edge Panel" and pin it to the edge of the screen by pressing the pin button. (The button is highlighted with a red circle)

✔ Expected Behavior

❌ Actual Behavior

Other Software
Microsoft Edge ´ Version 98.0.1108.56 (Official Build)
Windows 11 x64 (KB5008295)

Note that this is only when pinning to the left side of the screen.


Add support for seasonPass endpoint

This is a Sonarr endpoint that allows for mass changing of monitor status on a series/season/episodes
GET - Pulls all series, seasons, etc
POST - Updates a list of series
{
    "series": [
        {
            "id": 777,
            "monitored": true
        }
    ],
    "monitoringOptions": {
        "monitor": "all"
    }
}

I think you mentioned this, and I confirmed it, there is no GET endpoint here. POST is pretty easy.
Valid values for monitor are:
all, future, missing, existing, firstSeason, latestSeason, and none.


fix 2912 #2938 about save button in  vul tag and signed icon

Coverage remained the same at 54.445% when pulling cd1077fa4376881d1e4f56ed46f464abe7db48c9 on pengpengshui:master into 6f8f765358d97bcbe004bc0d88f830e2f0020c41 on vmware:master.


[ISSUE #6252] fix typos

Make sure set the target branch to develop
What is the purpose of the change
close #6252
Brief changelog
fix typos
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #6253 (64f113b) into develop (ce99a7f) will decrease coverage by 0.04%.
The diff coverage is 40.00%.

@@              Coverage Diff              @@
##             develop    #6253      +/-   ##
=============================================
- Coverage      43.21%   43.18%   -0.04%
+ Complexity      8852     8848       -4
=============================================
  Files           1094     1094
  Lines          77193    77193
  Branches       10070    10070
=============================================
- Hits           33358    33334      -24
- Misses         39672    39690      +18
- Partials        4163     4169       +6

Impacted Files
Coverage Δ

...cketmq/broker/schedule/ScheduleMessageService.java
57.85% <40.00%> (+1.13%)
:arrow_up:

...va/org/apache/rocketmq/store/FlushDiskWatcher.java
81.25% <0.00%> (-9.38%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-8.96%)
:arrow_down:

.../org/apache/rocketmq/store/ha/DefaultHAClient.java
61.22% <0.00%> (-5.62%)
:arrow_down:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
82.21% <0.00%> (-1.93%)
:arrow_down:

.../apache/rocketmq/store/ha/DefaultHAConnection.java
67.20% <0.00%> (-1.21%)
:arrow_down:

...a/org/apache/rocketmq/store/StoreStatsService.java
34.53% <0.00%> (-0.56%)
:arrow_down:

...che/rocketmq/acl/plain/PlainPermissionManager.java
78.22% <0.00%> (-0.54%)
:arrow_down:

...mq/store/ha/autoswitch/AutoSwitchHAConnection.java
70.16% <0.00%> (-0.27%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
59.82% <0.00%> (ø)

... and 5 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[UI] Snackbar Closing and Settings Btn Fixed

Signed-off-by: Nikhil Sharma<EMAIL_ADDRESS>Description
This PR fixes #3910 and #3918
Fixed X to close the snackbar
https://user-images.githubusercontent.com/58226527/129906600-4a5d0e2d-0ffd-4d9f-a2a5-5b6b5f2c32d5.mp4
Fixed Settings button
https://user-images.githubusercontent.com/58226527/129906867-cb2fcb23-ff98-4ee1-8a75-230771839d7f.mp4
Notes for Reviewers

Let me know if there are any other changes we can make.

Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3923 (c2aeb2c) into master (13a5721) will increase coverage by 1.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3923      +/-   ##
==========================================
+ Coverage   25.17%   26.30%   +1.12%
==========================================
  Files          63       63
  Lines        4787     4787
==========================================
+ Hits         1205     1259      +54
+ Misses       3221     3148      -73
- Partials      361      380      +19

Flag
Coverage Δ

e2etests
∅ <ø> (?)

gointegrationtests
9.88% <ø> (+0.91%)
:arrow_up:

unittests
18.75% <ø> (+0.60%)
:arrow_up:

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

Impacted Files
Coverage Δ

mesheryctl/pkg/utils/helpers.go
18.58% <0.00%> (ø)

mesheryctl/pkg/utils/platform.go
4.43% <0.00%> (+4.43%)
:arrow_up:

mesheryctl/pkg/utils/testing.go
14.58% <0.00%> (+14.58%)
:arrow_up:

mesheryctl/internal/cli/root/system/update.go
30.58% <0.00%> (+29.41%)
: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 8a452ee...c2aeb2c. Read the comment docs.

@sudo-NithishKarthik UI integration failing again, could you please re-run the test, i think that requires write access

Tested it out on local, works great, thanks @NikhilSharma03
@warunicorn19 Thanks for testing, did you also tested out for the performance/other UI's, everywhere also(just confirming) :P

Yup @Chadha93 , tested it out all over. It works

Oh, thanks for pointing out @warunicorn19


Disabled building tests default (like LLVM), enabled for our CIs

As mentioned in #1059, our default builds require onnx to be installed.
This PR implements the changes requested in that issue:

all extensive tests are predicated by ONNX_MLIR_BUILD_TESTS being ON
default ONNX_MLIR_BUILD_TESTS value switched to off.
Our CIs add the ONNX_MLIR_BUILD_TESTS=ON define.

That way, folks just building a default onnx-mlir will not build the tests, and thus we are not dependent on onnx third party to be installed.
For folks using their own scripts for testing, you must now add
        -DONNX_MLIR_BUILD_TESTS=ON \

to your cmake command.
To respond to issue #1059, I also pip uninstal onnx and tested that we can build a working compiler without onnx on my local Mac machine, and it worked.

From the log from linux/amd
[...]
[100%] Built target numerical
[100%] Running the ONNX-MLIR numerical regression tests
Test project /workdir/onnx-mlir/build/test/numerical
      Start  1: TestConv
      Start  2: TestMatMul2D
      Start  3: TestMatMulBroadcast
      Start  4: TestGemm
      Start  5: TestLSTM
      Start  6: TestRNN
      Start  7: TestGRU
      Start  8: TestLoop
      Start  9: TestScan
      Start 10: TestElementwise
      Start 11: TestSoftplus

[...]

[100%] Built target check-onnx-backend
bringing up nodes...
bringing up nodes...

530 passed, 2348 skipped in 103.80s (0:01:43)

So it appears to build & test the tests in the CI.

@AlexandreEichenberger I am curious to know if without building onnx, can you compile a .onnx model or not? Numerical tests do not use .onnx files as input, so it does not tell whether we can compile a .onnx model. Just to double check.

I am curious to know if without building onnx, can you compile a .onnx model or not? Numerical tests do not use .onnx files as input, so it does not tell whether we can compile a .onnx model. Just to double check.

@tungld Here is the experiment I ran. I executed a pip3 uninstall onnx until it said there were none; then I ran with the -DONNX_MLIR_BUILD_TESTS=OFF, build an onnx-mlir and tried the compiler on an mlir and onnx input, both of which worked. When I built it with ON, the make process would fail due to the lack of installed onnx.
That was on a Mac, let me retry all this on a LoZ

I ran with the -DONNX_MLIR_BUILD_TESTS=OFF, build an onnx-mlir and tried the compiler on an mlir and onnx input, both of which worked

Thank you for the confirmation! That sounds good. Let @gongsu832 give the final decision since the most changes are about CMakeFiles.


Different nr. of KV and Q tokens

Does the variable length kernel support computing variable length attention when the sequences in Q are shorter than the sequences in KV? e.g. q consists of 10 tokens and KV consists of 20. If so how would this work, especially with is_causal=True?
Would token j in Q attend to all tokens 10+j in K? And then the first Q token attends to the first 11 K tokens?

Yes it's supported. The precise attention pattern is described in the function docstring.
https://github.com/Dao-AILab/flash-attention/blob/c1d146cbd5becd9e33634b1310c2d27a49c7e862/flash_attn/flash_attn_interface.py#L1358

Thanks for the answer and the amazing work!


MINOR: updated upgrade and architecture for KIP-663, KIP-696, and KIP-671

adding docs for KIPs 663, 696 and 671
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mjsax @JimGalasyn I took a stab at updating the docs for a couple of kips. Let me know if there is anywhere I missed

@mjsax @JimGalasyn I took a stab at updating the docs for a couple of kips. Let me know if there is anywhere I missed

@cadonna and @mjsax I made changes based on Bruno's comments. Can you give it another look?

@cadonna and @mjsax I made changes based on Bruno's comments. Can you give it another look?

LGTM.

LGTM.


#1061 Java convert event package

EventManager.fireEvent() has try catch block that needs review.  Get a better exception to throw?

Cancel - will resubmit to an experimental core module.


OCPBUGS-11885: use bond members as keys instead of bond interface

with running rhel9 we have now bond XDP native support by design xdp packets will be carrying member interface index not the bond interface, while we still only
attach to bond interface

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

/test ingress-node-firewall-e2e-metal-ipi

/retest

/jira refresh


Update Facebook SDK

📲 What
Updates our Facebook SDK to 5.0.2. At the same time this PR moves the management of this dependency to Carthage and thus removes the SDK files from our repo unfortunately resulting in a large diff.
Note: Ignore/filter the deleted .h files in the diff to make reviewing easier.
🤔 Why
Our Facebook SDK was quite outdated and we've had reports of failed logins as well as friends lists not appearing in the app. Although it was also since discovered that our app was pending app review by Facebook it was also time to update this SDK and remove it from our repo.
🛠 How

Moved dependency to Cartfile.
Renamed deprecated types (Facebook dropped the FBSDK prefix in front of their types for Swift codebases).
Updated our FacebookAppDelegateProtocol for tests and conformed the new ApplicationDelegate (previously FBSDKApplicationDelegate) to this.

✅ Acceptance criteria
Note: Both of these are dependent on Facebook first completing their app review.

[ ] Facebook login works
[ ] Friends list loads correctly in the app

 Update Facebook SDK


Lin shrinking of cmd arguments

This PR adds shrinking of cmd arguments for Lin in both "non-DSL mode" and in "DSL mode".
We do so by adding an entry to the interface val shrink_cmd : cmd Shrink.t.
For non-DSL mode, this can be trivially satisfied with Shrink.nil performing no shrinking.
The PR adds shrinkers to the existing non-DSL tests - except for Lazy (where testing and shrinking is already dog-slow).
The DSL mode has me on thinner ice. It was nevertheless instructive to better understand the DSL code base.
@OlivierNicole if you have ideas to avoid the ugly "this-should-not-happen" failwiths I'm all ears! :grin:
I noticed QCheck's char arbitrary doesn't shrink so I include a work-around. I'll send a QCheck PR to fix it shortly.
This should take care of the Lin-part of #65 - the STM-part remains.
Finally here is a shrink output for show:
Messages for test Linearizable Hashtbl DSL test with Domain:

  Results incompatible with sequential execution

                                      |
                        Hashtbl.replace t 'a' 0  : ()
                                      |
                   .------------------------------------.
                   |                                    |
       Hashtbl.add t 'a' 0  : ()              Hashtbl.clear t  : ()
                                              Hashtbl.length t  : 2

just rebased


Host RPMs/SRPMs

It would be nice if the RPMs or SRPMs could be downloaded from somewhere without having to build the RPM oneself.
(I mean, I have no problem with that, but it can be a hassle for a greater user base)
We can use GitHub's releases (you can see it also in my own fork of the repo), or we can just host here the SRPM and build the different RPMs using copr for each Fedora release. Although it seems we do not depend on anything else than libdrm-devel for building, so a single RPM might suffice, but not sure about that. libdrm-devel versions are scattered between 2.4.59 and 2.4.66 for most recent Fedora/CentOS-based releases.

The best way to go about this is to use the Fedora copr service imho. I planned on doing this but never got around to it yet. My plan was actually to get the kernel driver upstream and re-implement the user space blob in mesa but I am not clear what is the story with that nsa user blob yet.. but that is another story :)

The best way to go about this is to use the Fedora copr service imho. I planned on doing this but never got around to it yet. My plan was actually to get the kernel driver upstream and re-implement the user space blob in mesa but I am not clear what is the story with that nsa user blob yet.. but that is another story :)

fyi - https://copr.fedorainfracloud.org/

My plan was actually to get the kernel driver upstream and re-implement the user space blob in mesa

That's actually the major part of the story if you want to host this on Fedora's COPR. You can only build in COPR packages that would be accepted by Fedora. Half of this package is proprietary, so no chance of getting it into Fedora proper, or COPR.

However ... that's what RPM Fusion exists for. If the blob is still redistributable then they are likely to accept.
That would be the best home for them potentially ... unless/until DisplayLink get patches submitted into the relevant upstreams for kernel etc

For someone who can't build themselves, check out this guy's blog, I've got my DL working on Fedora just because of him.
http://nothen.com.ar/en/support-for-displaylink-adapters-on-linux/

Would anyone help with getting this on RPMFusion, or building in Travis?
It seems that the license agreement may prevent us altogether from hosting the driver:

1.4. You may distribute the Software (other than the Open Source Elements) only (i) without
modification, (ii) in an unobfuscated form which allows the Software to be identified, and (iii) subject
to the terms and conditions of this EULA, a copy of which shall be included with any such
distribution. You may use, copy, modify and distribute the Open Source Elements in accordance
with the terms and conditions applicable to them.

We seem to be allowed to redistribute verbatim copies, so we can indeed host the src.rpm files, because the proprietary .zip fulfills the conditions.
However, I am not sure on whether the build process we are performing can be seen as "without modification", which would prevent us from legally hosting the files on rpmfusion, even though it seems that there is intention from DisplayLink Corp. for the community to provide support for other distros, as per http://support.displaylink.com/knowledgebase/articles/679060.
I honestly think companies should stop shooting at their feet by saying they would like this repackaging process to happen and then locking it out in their licensing terms.

Since we are just running/repackaging their installer I think it should be fine, Best way to find out would be to post on the displaylink forums and ask

We should try to get written confirmation from DisplayLink Ltd. or, even better, have them explicitly grant so in the license agreement.

I posted on the forums to see if we get any bites
http://displaylink.org/forum/showthread.php?p=81520#post81520

Here is the reply from the displaylink folks

The text of the license was written to ensure the driver can be repacked by other distros and redistribute. As long as the text of license file is replicated, and binaries are redistributed as provided in the .run package (unmodified), and it is still possible to identify what component is what and where it came from, the license terms are met IMO. Note however that the original package now has a much more sophisticated udev rules than the project you linked, so I'd recommend to stick to them, rather than rolling your own.
Cheers,
Michal

So it appears that we are good to go


Request: Add error information to responses

I'm finding that debugging many issues to be a case of trial and error. When I get an unexpected result I just have to keep changing parts of the query till I can track down the part that is causing the problem even if the problem would have been obvious on the server side.
The other day It was because I was looking for events with past dates but instead of specifying past in the status field I was passing it to the state field. However if I'm passing a date in the past via the time field but not specifying "past" in the status field, shouldn't there at least be some warning in the meta information?
Now I've got this query:
https://api.meetup.com/2/open_events?key=REDACTED&sign=true&lat=-37.8139831&lon=144.9641694&time=-1w,&status=past
This returns results but as soon as I change status from 'past' to 'past,upcoming', suddenly I get zero results back and I have no idea why. It also took a lot of trial and error just to get to the point where I knew the what part of the query was causing the issue:
https://api.meetup.com/2/open_events?key=REDACTED&sign=true&lat=-37.8139831&lon=144.9641694&time=-1w,&status=past,upcoming
While this specific issue is causing me problems, this is just one example. The main issue is that I get no feedback about what is wrong with this or other queries.

I know I sent this request through on the weekend, just wondering if it's been missed?

Closing this as I realise it's probably better to aim for more modest fixes.


(SIGBUS) Bus Error on armv8-a while creating channel in grpc_chttp2_transport::grpc_chttp2_transport

What version of gRPC and what language are you using?
GRPC Rev:(CPP)
Commit 8517f67ff6081d6024aaf6dfd3e4de1d5f1f0d7c
Merge: bbb1783 da9b036
Author: Mark D. Roth<EMAIL_ADDRESS>Date:   Fri Jul 24 17:07:06 2020 -0700
Merge pull request #23612 from markdroth/xds_v3_build_fix

Fix BUILD file for import.

What operating system (Linux, Windows,...) and version?
Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
What runtime / compiler are you using (e.g. python version or version of gcc)
arm-pokymllib32-linux-gnueabi-gcc/g++
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
Application and Client both trying to create a channel and crashes while initializing chttp2_transport constructor with SIGBUS
What did you expect to see?
Applications should not crash.
What did you see instead?
Both Client and server application are crashing with SIGBUS.  BT shows it is crashing while creating the transport object.
The Toolchain is configured  with Mulitlib support and have 64 bit platform but grpc and applications are compiled with 32bit tool chain.
We are using Yocto tool chain to compile the tools and configured as :
EXTRA_OECMAKE = "
-DBUILD_GMOCK=OFF
-DgRPC_ABSL_PROVIDER=module
-DgRPC_PROTOBUF_PROVIDER=package
-DgRPC_ZLIB_PROVIDER=package
-DgRPC_SSL_PROVIDER=package
-DgRPC_INSTALL=ON
-DCMAKE_CROSSCOMPILING=ON
-DBUILD_SHARED_LIBS=ON
-DABSL_ENABLE_INSTALL=OFF
-DgRPC_INSTALL_CMAKEDIR=${baselib}/cmake/${BPN}
"
**********************************************/
CC="arm-pokymllib32-linux-gnueabi-gcc  -mfpu=neon-fp-armv8 -mfloat-abi=hard -march=armv8-a -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security"
CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types
-mfpu=neon-fp-armv8 -mfloat-abi=hard -march=armv8-a
-fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat
-Wformat-security -Werror=format-security  "
CXX="arm-pokymllib32-linux-gnueabi-g++  -mfpu=neon-fp-armv8
-mfloat-abi=hard -march=armv8-a -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
-Werror=format-security "
CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types
-fvisibility-inlines-hidden  -mfpu=neon-fp-armv8 -mfloat-abi=hard
-march=armv8-a -fstack-protector-strong  -D_FORTIFY_SOURCE=2
-Wformat -Wformat-security -Werror=format-security  -Wl,--no-as-needed"

(gdb) bt
#0  0xf75a9804 in grpc_chttp2_transport::grpc_chttp2_transport (
this=0xf2101514, channel_args=0xf21013d0, ep=,
is_client=, resource_user=0x0)
at /usr/include/c++/8.2.0/bits/atomic_base.h:256
#1  0xf75aa87c in grpc_create_chttp2_transport (
channel_args=0xf21013d0, ep=0xf2100e78,
is_client=is_client@entry=false,
resource_user=resource_user@entry=0x0)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/ext/transport/chttp2/transport/chttp2_transport.cc:3345
#2  0xf759ad74 in grpc_core::(anonymous namespace)::Chttp2ServerListener::ConnectionState::OnHandshakeDone (arg=0xf4544d00, error=0x0)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/ext/transport/chttp2/server/chttp2_server.cc:225
#3  0xf75eff44 in exec_ctx_run (error=0x0, closure=0xf4544cdc)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/iomgr/exec_ctx.cc:40
#4  grpc_core::ExecCtx::Flush (this=0xf18fdbd0)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/iomgr/exec_ctx.cc:153
#5  0xf75eafac in pollset_work (pollset=0xf7fee8e8,
pollset@entry=0xf3608210, worker_hdl=,
deadline=)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/iomgr/exec_ctx.h:223
#6  0xf75eed68 in pollset_work (pollset=0xf3608210,
worker=, deadline=)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/iomgr/ev_posix.cc:325
#7  0xf7659c2c in cq_next (cq=0xf3608168, deadline=..., reserved=0x0,
reserved@entry=0xf7fee900 <__stack_chk_guard>)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/surface/completion_queue.cc:1274
#8  0xf7658b50 in grpc_completion_queue_next (cq=,
deadline=..., reserved=0x0)
at /usr/src/debug/lib32-grpc/1.30-r1/git/src/core/lib/surface/completion_queue.cc:1350
#9  0xf7ced464 in grpc_impl::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) () from /usr/lib/libgrpc++.so.1
#10 0xf7d0d1a8 in ?? () from /usr/lib/libgrpc++.so.1
#11 0xf7d17adc in grpc::ThreadManager::MainWorkLoop() ()
--Type  for more, q to quit, c to continue without paging--
from /usr/lib/libgrpc++.so.1
#12 0xf7d17d4c in grpc::ThreadManager::WorkerThread::Run() ()
from /usr/lib/libgrpc++.so.1
#13 0xf74571a4 in ?? () from /usr/lib/libgpr.so.11
#14 0xf7c36334 in ?? () from /lib/libpthread.so.0
*******************************************************************************************************/
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?

@nicolasnoble could you please look at this issue ?

Since this issue is from Aug 2020, it's not clear to me whether it's still a problem or not.
Also, I'm not familiar with the arm-pokymllib32-linux-gnueabi-gcc toolchain. Is that targeting 64bit or 32bit? We only have tests on our CI for ARM64, so if you're trying to build for ARM 32bit, I wouldn't be surprised if that didn't work.

Closing since it's unclear whether this is still an issue. Please create a new issue if this is still a thing.


allow iterating over a fieldpath's ShapeRefs

Adds a few utility methods to pkg/fieldpath.Path to make it easier to
inspect associated ShapeRefs at different parts of the path:

Path.At(int) returns the path part at the supplied index.
Path.CopyAt(int) returns a new Path up to the supplied index.
Path.ShapeRefAt(*shapeRef, int) returns a ShapeRef corresponding to
the path part at the supplied index.
Path.IterShapeRefs(*shapeRef) returns a slice of *ShapeRef that can
be used to iterate over the ShapeRefs associated with each of the
Path's parts.

Signed-off-by: Jay Pipes<EMAIL_ADDRESS>By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/test s3-controller-test

/lgtm


[macOS] Fix sub-windows opening in fullscreen.

Fixes https://github.com/godotengine/godot/issues/69292

Thanks!


When mask clicked (onPressMask) saves the date value

How can we validate the input when the mask is clicked?
I noticed many user wanting to validate the input by simply clicking on the mask and not on the OK button.
What do you think? How can we achieve that?

+1 to submitting on mask press (I think that's what you mean?)
My workaround for now is using the (undocumented) onPressConfirm:
class MyDatePicker {
  _onPress() {
    const {onPressMask} = this.props;
    this._datePickerRef.onPressConfirm();
    if (onPressMask) {
      onPressMask();
    }
  }

  _onDatePickerRef(ref) {
    this._datePickerRef = ref;
  }

  render() {
    <DatePicker {...this.props} ref={this._onDatePickerRef} onPress={this._onPress} />
  }
}

@izhan @rdewolff - this PR adds support for exactly this! https://github.com/xgfe/react-native-datepicker/pull/363


PO file is missing it's header

I think Yii message generator/extractor should also add a header to PO file. For example the translation service I'm using has now stopped supporting PO files without header through their API and I'm forced to find somekind of quick fix for that. But it would be nice to have this in the core functionality.
How should the header be populated? Should it be configurable through messages configuration file maybe? I have no answers for that - but I think this should be in the scope of framework.
Some information about it: http://pology.nedohodnik.net/doc/user/en_US/ch-poformat.html#sec-poheader

Setting it in config sounds OK.

I think this can be closed now as the headers were added as a fix for: #11212


sbt launcher script should honor the sbt.global.localcache property

problem
There are a handful of hardcoded ${user_home:-$HOME}/.cache/sbt references in the launcher script (e.g. https://github.com/sbt/sbt/blob/develop/sbt#L131)
When running sbt via docker with volume mounts for caches and specifying something like -D sbt.global.localcache=/cache/sbt its still possible for some artifacts to get placed in ephemeral storage $HOME/.cache/sbt
expectation
We have a few convenience launcher arguments like:
  --sbt-dir   <path>  path to global settings/plugins directory (default: ~/.sbt)
  --sbt-boot  <path>  path to shared boot directory (default: ~/.sbt/boot in 0.11 series)
  --ivy       <path>  path to local Ivy repository (default: ~/.ivy2)

I propose adding --sbt-localcache that would default to ~/.cache/sbt and update any references in the launcher script from $HOME/.cache/sbt to use that argument and/or property.

As a retronym I'd suggest --disk-cache to mean not-remote cache, which is the name Bazel also uses.


Fix file permissions on /var/lib/mysql

This fixed https://github.com/wunderkraut/alpine-mariadb/issues/1

It could be that more narrow permissions could still be used.


Module not found: Error: Can't resolve './src' in 'electron-react-webpack-typescript-2021'

Running npx webpack (https://webpack.js.org/guides/getting-started/#creating-a-bundle) I get this error:
(base) marco@pc01:~/webMatters/electronMatters/electron-react-webpack-typescript-2021$ npx webpack
Module not found: Error: Can't resolve './src' in '/home/marco/webMatters/electronMatters/electron-react-webpack-
typescript-2021'

Also modifying the webpack.main.js resolve path:
resolve: {
  extensions: ['.js', '.ts', '.jsx', '.tsx', '.css', '.json'],
 //alias: require('./webpack.aliases'),
  modules: [path.resolve(__dirname, 'src'), 'node_modules'],
},

doesn't resolve the problem: Module not found: Error: Can't resolve './src' in '/home/marco/webMatters/electronMatters/Ipfs-Webpack'

Command npx webpack requires an entry file to be present, for example ./src/index.js
In this project we aren't using index.js file as entry point, so you can give this command a try @raphael10-collab
npx webpack --entry ./src/main.ts

Not really sure if that'd work without any error, because the command npx wepback would still require whole webpack configuration file webpack.config.js to be available with required configuration, loaders, entrypoints etc to compile the assets used in this project.

(base) marco@pc01:~/webMatters/electronMatters/electron-react-webpack-typescript-2021$ npx webpack --entry ./src/main.ts
Need to install the following packages:
  webpack
Ok to proceed? (y) y
CLI for webpack must be installed.
  webpack-cli (https://github.com/webpack/webpack-cli)

We will use "yarn" to install the CLI via "yarn add -D webpack-cli".
Do you want to install 'webpack-cli' (yes/no): yes
Installing 'webpack-cli' (running 'yarn add -D webpack-cli')...
yarn add v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved 1 new dependency.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
└─<EMAIL_ADDRESS>Done in 10.63s.
Error: Cannot find module 'webpack-cli/package.json'
Require stack:
- /home/marco/.npm/_npx/89d6e678e21f2dae/node_modules/webpack/bin/webpack.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1030:15)
    at Function.resolve (internal/modules/cjs/helpers.js:81:19)
    at runCli (/home/marco/.npm/_npx/89d6e678e21f2dae/node_modules/webpack/bin/webpack.js:50:26)
    at /home/marco/.npm/_npx/89d6e678e21f2dae/node_modules/webpack/bin/webpack.js:139:5
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/marco/.npm/_npx/89d6e678e21f2dae/node_modules/webpack/bin/webpack.js'
  ]
}
npm ERR! code 1
npm ERR! path /home/marco/webMatters/electronMatters/electron-react-webpack-typescript-2021
npm ERR! command failed
npm ERR! command sh -c webpack "--entry" "./src/main.ts"

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/marco/.npm/_logs/2021-02-10T08_06_31_503Z-debug.log

Error: Cannot find module 'webpack-cli/package.json'

This is some strange output @raphael10-collab, could you explain a little about what you're trying to perform with npx webpack  in the ERWT boilerplate?

any update on how to fix this?

@JSLNO is there any Testing Repository which is related to this issue? It'd be helpful to have a testing repository for reproducing the issue mentioned in here.


npm packages census

After a quick look, we have 58 npm packages shared across 3 organisation (@celo, @celo-tools, @clabs).
We need to investigate and summarize what's up with that. Which ones are up-to-date, deprecated, abandoned, etc.

Good onboarding ticket.
Could way to get on board and learn about various SDKs.
Currently low prio assigned to @yerdua.

whats next here

@shazarre wrote a neat script that fetches NPM package metadata via an API.
He had a lovely Google Sheet with the output.
Next step is:

linking the sheet here (at minimum), copy/pasting a bullet list of the packages here for reference (at best)
reviewing packages e.g.

which do we (@celo-org/devtooling) want to maintain, which do we (@celo-org/devtooling) want to deprecate
which do we want to bring to other team's attention (so they decide on maintenance/deprecation)


More kernels

added R kernel
make bash kernel optional

Awesome, thanks for working on this. Now that we are using conda for installing the Python kernel, I wonder if that makes sense for R as well? @minrk thoughts?

Also, I think this should install a larger set of R packages by default. Maybe the same set as R Studio?

The conda R channel is not always updated, so I decided to use apt get instead.

If it were me, I would use conda for it, but I trust people who actually teach with R to make a better choice. I'm happy to merge this as-is, and we can consider conda for R at a later point.


get or else Camunda FEEL function is marked as syntax error

Describe the bug
When I choose get or else function from the suggestions, it's marked as syntax error.
https://github.com/camunda/camunda-modeler/assets/28307541/dc541efa-f69a-40b3-b21a-9cea66dfcd8d
Steps to reproduce

Start writing get or and notice the suggestion
Hit enter
now this happens

Expected behavior
The expression get or else(variable, defaultValue) should be parsed as:
Expression [0, 35]
  FunctionInvocation [0, 35]
    VariableName [0, 11]
    PositionalParameters [12, 34]
      VariableName [12, 20]
      VariableName [22, 34]

Environment

OS: [e.g. MacOS 10.2, Windows 10]
Camunda Modeler Version: [e.g. 2.0.0]
Execution Platform: [e.g. Camunda 7, Camunda 8]
Installed plug-ins: [...]

Additional context
The built-in extension function should be provided in the context because it uses keywords.
SUPPORT-19273

We could add a quick-fix and add it to the expression context, but that would not solve the underlying issue. We are currently supporting two FEEL engines with different capabilities, but use the same editor tooling for both.
Cf. @nikku comment on Slack: https://camunda.slack.com/archives/GP70M0J6M/p1699970314078889?thread_ts=1699954926.982759&cid=GP70M0J6M
We should try to solve it on the language level. In the long term, we need a decision on how to handle extensions, especially when we want to add a FEEL playground in the modeler experience at one point.

Hi,
The same problem occurs with Camunda Modeler 5.18.0 :

But, we can deploy the BPMN diagram on platform 8.3. And the process works correctly.

This has been independently reported by multiple users.

Moving to backlog.

Let's investigate if this is an easy pick.

Did not make it into the M76 milestone.

I looked into this yesterday and found that there is sensible improvements we could make in the feel-editor:

Any declared built-in shall also be available for syntax completion
We can make better use of the batteries included in code mirror for retrieving available variables and built-ins.

@barmac Assigning myself as I'll look into this post release (I have the context still).

Updating the feel-editor unfortunately does not solve the issue:

What I missed is that we'd also need to update our FEEL validation to recognize the get or else built-in.

Adding another user report so priority can be adjusted as needed: https://forum.camunda.io/t/unparsable-feel-expression-is-it-a-bug-in-modeler/53862/

Thanks. A fix is already work in progress.

Another customer has reported this: SUPPORT-23453

Another customer has reported this: SUPPORT-23592.
is there any workaround for this or an estimated date on when this will be fixed? My customer is using 8.5

Any updates?


Feat create title picker component

Fixes #2108
Notable changes: title is now a detail, details are now shown immediately instead of behind a dropdown
When testing, especially check whether searches and searchStrings still work as expected, as that part is rather hacky.

Don't merge until after CBI

closing for now as there will be more changes


Add redis vectordb

Description
This PR includes Redis as a vector database to Embedchain using the new, purpose-built redisvl python library. Given work was already started using base redis-py, I wanted to also highlight the work started here (https://github.com/embedchain/embedchain/pull/756) by @SudhanshuJoshi09. This simplifies the codebase a good bit (for redis) and also includes more explicit metadata filtering via "Tag" fields in Redis. It also updates documentation, adds an example notebook, and config examples.
FYI @deshraj I'd love to get any additional feedback here. The version of redisvl used to build this will be released later this week (so I am tied to a github branch atm). But I wanted to get a head start.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[x] Unit Test
[x] Test Script (please provide)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

Hi @deshraj @taranjeet We are interested in getting this merged soon if possible. What else is required? I've pinned to a supported version of redisvl and updated tests and contributed docs and notebook examples.

Hi @tylerhutcherson Can you please resolve the conflicts so that we can start reviewing the PR and merge it?

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

thanks for your contribution @tylerhutcherson . There are so many merge conflicts on this PR and we haven't heard back from you in a while, so closing this.


Add flag for properties to display to blue teams (something like 'hidden' or 'show_blue_team'

Add a flag to the property model to allow for certain views to hide or display certain properties for blue teams' services.

https://github.com/pwnbus/scoring_engine/pull/106