Remove obsolete constants in version 1.0.0

This issue tracks constants that should be removed from libc for release 1.0.0.
The following are absent in FreeBSD 11, never had stable values across versions, and should never have been used by third party software.  They should be removed from FreeBSD.
CTL_MAXID
KERN_MAXID
HW_MAXID
USER_MAXID

The following is still present in FreeBSD 11, but like the previous four it should never have been used by third party software, and its value isn't guaranteed to be stable across versions.  It should be removed from FreeBSD
CTL_P1003_1B_MAXID

Add to the list AIO_LISTIO_MAX.  That symbol should never be used because the quantity it represents can potentially vary at runtime.  Programs should use sysconf(3) instead.

I've deprecated these on master, and they are also doc(hidden). I'd say that we'd remove them in one of the next releases.

I agree.

Feel free to open a PR removing these.


i64 in sqlite: bigint NOT NULL PRIMARY KEY AUTOINCREMENT

Description
I am define entity , this is code:
#[derive(Clone, Debug, PartialEq, DeriveEntityModel, Eq)]
#[sea_orm(table_name = "t_test")]
pub struct Model {
    #[sea_orm(primary_key)]
    pub id: i64,
    pub create_user: Option<String>,
    pub create_time: DateTime,
    pub update_user: Option<String>,
    pub update_time: DateTime,

}

Migration code:
impl MigrationTrait for Migration {
    async fn up(&self, manager: &SchemaManager) -> Result<(), DbErr> {
        let backend = manager.get_database_backend();
        let schema = Schema::new(backend);

        let stmt = schema.create_table_from_entity(TestEntity);
        let r = manager.create_table(stmt).await;
        if let Err(err) = r {
            println!("{}", err);
            return Err(err);
        }

        Ok(())
    }

Steps to Reproduce

run this test code

env::set_var("RUST_LOG", "debug");
tracing_subscriber::fmt::init();
let mut opt = ConnectOptions::new("sqlite:file::memory:?cache=shared");
opt.sqlx_logging_level(log::LevelFilter::Info);
let db = Database::connect(opt.clone()).await.unwrap();
let _ = Migrator::up(&db, None).await;

will get error:

2023-08-30T04:46:55.588146Z DEBUG sea_orm::driver::sqlx_sqlite: CREATE TABLE "t_test" ( "id" bigint NOT NULL PRIMARY KEY AUTOINCREMENT, "create_user" text, "create_time" text NOT NULL, "update_user" text, "update_time" text NOT NULL)

thread 'test_create_test_server' panicked at 'called `Result::unwrap()` on an `Err` value: Exec(SqlxError(Database(SqliteError { code: 1, message: "AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY" })))'

Expected Behavior
It is success, when i use postgresql.
But use sqlite, i am get error. why?
I am read this doc https://www.sea-ql.org/SeaORM/docs/generate-entity/entity-structure/
I think the create table sql is error。
In the doc, the i64 id should be "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT but not  "id" bigint NOT NULL PRIMARY KEY AUTOINCREMENT
Actual Behavior
Different the document description
in sqlite,
i64 -> bigint, ❌，different doc
i64 ->  integet, expected，and same doc. but actual behavior is bigint
Reproduces How Often
always reproducible!
Versions
Cargo.toml
sea-orm = { version = "0.12.2", features = [
    "sqlx-postgres",
    "sqlx-sqlite",
    "runtime-tokio-rustls",
] }
sea-orm-migration = { version = "0.12.2", features = [
    "sqlx-sqlite",
    "sqlx-postgres",
] }

It appears to be a quirkiness of SQLite
Ref: https://sqlite.org/forum/info/2dfa968a702e1506e885cb06d92157d492108b22bf39459506ab9f7125bca7fd
In most cases BIGINT is synonyms with INTEGER, but not in PRIMARY KEY AUTOINCREMENT
I would suggest a workaround for now:
#[sea_orm(primary_key)]
#[cfg_attr(feature = "sqlite", sea_orm(column_type = "Integer"))]
pub id: i64,

Created issue in sea-query, as there is nothing to be done on sea-orm side.


Consider parallelizing our sdist dependency collection

Right now, our dependency collection process (via resolvelib looks like this):

Start at top, iteratively walk the dependency list
If the dependency has a wheel, grab its dependencies from the wheel metadata for the next iteration
If the dependency only has an sdist, install that sdist in a temporary venv to compute its dependencies for the next iteration

(3) is slow, since at each iterative step we might have N source distributions that each get their own virtual environment (and virtual environment setup is pretty slow). We could probably speed it up a decent amount by using a thread pool (with a reasonable cap) to create multiple environments and collect them as they complete.
Downsides: thread pools mean more complex error and interrupt (i.e. ^C) handling. We should figure out the tradeoffs for this before committing to this direction.
Related to #56, since doing this will (hopefully) make the CLI more responsive.

Thanks for the writeup!
It sounds like parallelizing dependency collection might be more complexity than its worth, which perhaps explains why pip doesn't do it 😅 .
Our end goal here is #56 and not parallelism for its own sake, so let's investigate other options.


Add command to run cargo check and show errors/warnings in the editor

Without this feature, you have to run cargo check in your terminal and go back and forth from the terminal to the editor to fix the issues in your code. It would be great to take the output of cargo check and somehow integrate the errors and warning in the editor itself (i.e. the same way we show syntax errors, for instance)

This actually works right now: there's Rust run action in VS Code which does this (a custom extension to LSP).


Blockchain regenesis

I wanted to open discussion on creating a new genesis block for Dogecoin, most likely around the 2,000,000 block. The Dogecoin blockchain has expanded significantly faster than the chains of most other coins due to its exceptionally low fees, and this makes it increasingly expensive to run full nodes, as well as this expense being disproportionate to the mining fees being paid. Further, the two intentional hard forks mean the chain changes substantially in its earlier blocks, and simplifying the chain consensus rules over time has obvious benefits in code cleanliness.
I propose that from an agreed-upon very distant block (2 million or otherwise), a hash is added into the header of every 1-millionth block, immediately after the transaction count and before any AuxPoW header. Naturally this causes a hard-fork, hence the very high block number before introduction.
That hash represents state at the time the block was generated. Future client releases can then use the latest millionth block plus a copy of the state at the time of the block being generated, while old clients can ignore the hash and continue as normal. Block trimming should provide a similar space reduction for existing clients (and I believe will be part of Dogecoin 1.10).
The state data would contain transactions which are either unspent or have OP_RETURN outputs. These would have to be structured carefully defined to ensure consistency - it is suggested that transaction ID of the transaction they're from, and index within the transaction, is used to order the data.
Thoughts?

How much time would it take to confirm such a block?

Good question... I imagine we're talking a dataset around 10% of the current blockchain in size, all nodes can start to prepare the dataset once the previous block is mined, but it could still take a fair chunk of time. I've got some ideas on how we could work around a huge confirmation time (such as using hash from 10 blocks ago), but sounds like I need to do some data extraction and see what the result looks like.

Also occurs that how we get the dataset to people isn't at all trivial, and the hash may want to be a merkle tree root for the data chunked into easier to confirm parts.

Here's an idea: at block 1000000 we start looking for UTXOs starting from the block 999999, until we reach a certain amount, say, 2^20. Then we format them appropriately and include in block 1000000, in the next block we start where we stopped in the previous block, and include another 2^20 transactions. We continue doing this way until all past transactions are included in a few 10000xx blocks. Now here's an important catch: if a transaction is supposed to be hashed in some block, is spent in that some block. A strict processing order has to be defined, whether the transaction is declared spent, and not included in the backup, or if the fact of spending is ignored, and it is included. The latter is better because then all clients, when they see block 999999, will start accumulating 2^20 transactions, and then verifying correctness of a backup is a matter of comparing a hash.

Quick update, I have a student working on this next academic year (2015/6). I'll update as we have news, but this is a long term feature so likely to be slow going.

Sounds a great project, did you look at the pchMessageStart Ghostlander did for FTC and Phoenixcoin?
https://github.com/ghostlander/Phoenixcoin/commit/7d99445399481a1bac647b6df81a56a064555505

i so wish this would have been implemented ;(
#dogecoin on irc is full of ppl asking why syncing takes forever

we can still make this happen, we just need to coordinate to do it. Who
knows how to contrib on this portion, who has data on where to start?
On Sat, Mar 10, 2018 at 9:27 AM, buZz<EMAIL_ADDRESS>wrote:

i so wish this would have been implemented ;(
#dogecoin on irc is full of ppl asking why syncing takes forever
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1185#issuecomment-372047054,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArw6amBqa8SPQ0qmdkG4Z3wAPLSpgH5ks5tdA0EgaJpZM4FLyB6
.

--
-Kendall

If anyone has time to work on this, that would be amazing. The theory seems sound, at least. Every x (10,000? 100,000?) blocks a Merkle tree is generated of the UTXO (unspent transaction output) set, and the Merkle tree is included in the block somehow (potentially immediately after AuxPoW data and before the coinbase transaction). These superblocks can be distributed along with the UTXO set in place of bootstrap files, and clients just start from there.
The biggest technical challenge is how to generate that Merkle tree within the minute interval between blocks. A shifted window (i.e. it reflects UTXO set state 60 blocks back and therefore there's an hour to generate it) might help here, although requires a second "Difference between baseline" value is included.

A possible inspiration (and what caused me to comment here aswell) is the work done on BTCP with tools like https://github.com/BTCPrivate/utxo-dump

I'd want to get this into Bitcoin Core rather than go it alone for Doge, although practically speaking state snapshots aren't as useful as I thought they would be.


Error: connecting: Unrecognized remote plugin message

After installing ignite v28.1.1 I get this error even for version command:
Path 						Config 	Status
<EMAIL_ADDRESS>global 	✘ Error: connecting: Unrecognized remote plugin message:
Failed to read any lines from plugin's stdout
This usually means
  the plugin was not compiled for this architecture,
  the plugin is missing dynamic-link libraries necessary to run,
  the plugin is not executable by this process due to file permissions, or
  the plugin failed to negotiate the initial go-plugin protocol handshake
Additional notes about plugin:
  Path: /Users/user/.ignite/apps/github.com/ignite/cli-plugin-network-v0.1.0/cli-plugin-network.ign
  Mode: -rwxrwxrwx
  Owner: 501 [user] (current: 501 [user])
  Group: 20 [staff] (current: 20 [staff])
  MachO architecture: CpuArm64 (current architecture: arm64)

error while loading apps: fail to link<EMAIL_ADDRESS>connecting: Unrecognized remote plugin message:
Failed to read any lines from plugin's stdout
This usually means
  the plugin was not compiled for this architecture,
  the plugin is missing dynamic-link libraries necessary to run,
  the plugin is not executable by this process due to file permissions, or
  the plugin failed to negotiate the initial go-plugin protocol handshake
Additional notes about plugin:
  Path: /Users/user/.ignite/apps/github.com/ignite/cli-plugin-network-v0.1.0/cli-plugin-network.ign
  Mode: -rwxrwxrwx
  Owner: 501 [user] (current: 501 [user])
  Group: 20 [staff] (current: 20 [staff])
  MachO architecture: CpuArm64 (current architecture: arm64)```

same


minor fixes across azure ml tutorial

added a ref to other Azure ML materials along with minor errors and clarifications

@msgregman : Thanks for your contribution! The author, @kgremban, has been notified to review your proposed change.

@kgremban @ebertrams

@msgregman : Thanks for your contribution! The author, @kgremban, has been notified to review your proposed change.

Looks good, @msgregman. Do you want me to wait for Emmanuel to review before merging your changes?

@kgremban if you're good with it, i think these changes are minor enough to put in for now, and we can do a bigger review with Emmanuel and Ted (or peer) when they're available

Sounds good. #sign-off

#sign-off


chore: remove eslint fix by default.

since the --fix flag was being run, we weren't getting errors on CI that linting was broken.  When i was trying to do a release, i noticed that there were some un staged files after doing the release script.

removing the --fix flag, so we don't get false positives

Pull Request Test Coverage Report for Build 990

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

Totals

Change from base Build 496:
0.0%

Covered Lines:
1258

Relevant Lines:
1308

💛  - Coveralls

Pull Request Test Coverage Report for Build 990

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

Totals

Change from base Build 496:
0.0%

Covered Lines:
1258

Relevant Lines:
1308

💛  - Coveralls


change spdy executor to websocket executor

tested using kind v0.22.0 (node k8s v1.29.2) with server-side websocket feature gate enabled:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
featureGates:
  TranslateStreamCloseWebsocketRequests: true

created due to KEP to shift from SPDY to WebSockets: https://github.com/kubernetes/enhancements/issues/4006


Fixing Demo Code - Compare Embeddings for retriever Docs

The code examples from docs/howtos/applications/compare_embeddings.md were missing important lines e.g. missing the TestsetGenerator import and assigning test_df before using it.
This pull request adressess these minor improvements.

@matheusft thank you so much for the PR and fixing the docs ❤ 🙌🏽


Empty interfaces to type parameters

Hello @ssoroka!
I like your package, but i think it would be better to replace empty interfaces with type parameters
please check my proposal

Closing as I've merged the same changes in #2


Takes a lot of CPU

After update(v2.2.0) the plugin takes too much CPU. When the live server is off, CPU stabilizes.
Mac Sierra 10.12.6, Atom 1.24.0

Same but my CPU was at like 430%


tensorflow/tensorflow/examples/ios/benchmark/ .   Calculate % in Images.

In this example How we can calculate the % of Prediction.
We are getting 1.0.978 water bottle
1.0.988 bottle
1.0.078 mug
type of result.
How we can convert in % value

I'm sorry, I don't quite understand what you're asking. It looks like you might be saying
p(water bottle) = 0.978
p(bottle) = 0.988
p(mug) = 0.078
and you'd like to convert these probabilities into percentages? Can you' just multiply by 100?
In any case, this issues section is more usually used for bugs and feature requests; perhaps Stack Overflow would be a better venue for this kind of question.


[DC-1317] Modify run_rdr_qc_report so it can be reused

Created a command line tool for executing parameterized jupyter notebooks.

Also, the unit test CircleCI check is failing because KeyError: 'inferred_type_name' do you have an idea why this is occurring or should I do some investigating?


HTTP_PORT and WS_PORT can not be configured via environment variables

Do you want to request a feature or report a bug?
feature, or bug if you read the description of the PR introducing these options, which states there's env variables to configure them. #592
What is the current behavior?
These are only configurable via cli args which are hard to do with docker container due to the complicated start script required to start graph-node inside the container
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Set HTTP_PORT and/or WS_PORT env variables, notice thegraph still only listens on default ports
What is the expected behavior?
setting HTTP_PORT and/or WS_PORT should change the listening port for these servers. In the case of WS_PORT, graphiql also needs to make calls on WS_PORT

Resolved in #2832.


Bug 2033382: Fix missing machine annotations

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/bugzilla-refresh

/bugzilla-refresh

/bugzilla-refresh

/bugzilla refresh

/bugzilla refresh

/bugzilla refresh

No idea🤷♂

/meow


Feature request: Have templater buttons that just run the template (without prepending o appending)

It would be great to have also a button that only runs a template.
Why? Because then we could run templates like the following to, for example (in the code below), replace all the checked boxes for unchecked ones, without adding any text to the note:
<%*

//get file content and replace checked boxes for unchecked
var noteContent = tp.file.content.replaceAll ("[x]","[ ]");

//select all in note
let cmEditorAct = this.app.workspace.activeLeaf.view.editor;
cmEditorAct.setSelection({ line: 0, ch: 0 }, { line: 9999, ch: 9999 });

//replace content + set cursor at the start
cursor = tp.file.cursor(0);
tR = cursor + noteContent.split("<%*")[0];

%>

Right now I do the trick of using append then removing that appended text: noteContent.split("<%*")[0]
But this works randomly depending on some speed of an internal process that appends the templater text to the note (because thats the button I am using).
This works perfectly when applying the template using templater command, but with buttons we cannot replicate because of the extra text insertion.
This feature would allow us to run any javascript to modify the current note using templater, I think it would be pretty cool :)
Thank you!

Really good idea that should be pretty easy to do. Will look into it.

+1 to this. I would like to use this to have pass Templater an argument from the current file that it uses to create a new file.

has this been implemented?

1


New logo

 This work is licensed under a Creative Commons Attribution 4.0 International License.

Awesome! Thank you so much for this!!


Fix support for version 1.1.3

Remove ['data']['devices']

Fix support for version 1.1.3

@liorfranko Yikes, sorry for missing this. If you're still interested, probably good to make sure this works with current NSoT


Exam mode: Fix the number of complaints in the exam assessment dashboard

Checklist
General

[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.
[x] I implemented the changes with a good performance and prevented too many database calls.
[x] I documented the Java code using JavaDoc style.

Client

[x] I followed the coding and design guidelines.
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.

Motivation and Context
When an exam receives a complaint, the dashboard shows this complaint as solved.

That is wrong because, without a response, the dashboard should show 0/1 (0%). Otherwise, the instructors will think that all complaints were solved.
According to the presentation of the information, some minor corrections are applied.
Description
Now, every time a complaint is submitted, the counting is correct.

If there are 2 complaints without an answer, the dashboard will show 0/2 (0%).
If one of these is answered, the dashboard will show 1/2 (50%).
If all complaints were answered -> 2/2 (100%)

Just like the exercises dashboard works.
Steps for Testing

Prerequisites:

1 Instructor
1 Student
1 Programming/Text/Modeling Exercise with Complaints enabled

Log in to Artemis
Navigate to Course Administration
Create an exam
Add a couple of exercises with enabled complaints (at least 2)
The student submits the exam
The instructor makes the assessment
The student submits a complaint to each exercise
Verify that the 2 complaints are shown in the dashboard 0/2 (0%)
Answer one complaint and verify the dashboard shows Complaints: 1/2 (50%)
Answer the second complaint and verify the dashboard shows Complaints: 2/2 (100%)

Reviewers can use the number of exercises and complaints they prefer. They just need to verify that the counting is correct.
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Class/File
Branch
Line

Screenshots

Tested on TS1. Works as expected.
Code changes also look reasonable.
👍🏻


Marathon services discovery in Kapacitor 1.6 config changed

https://github.com/influxdata/kapacitor/pull/2536/files#r613542653
The Timeout config parameter to the marathon service discovery was removed to stay in sync with the prometheus implementation we depend on.
https://github.com/prometheus/common/pull/123
This is planned for Kapacitor 1.6.0.

Hi guys, did we update for Kapa 1.6.1?

Looking at this now—

@lesam Is this the configuration parameter that needs to be removed from docs?  https://github.com/influxdata/docs-v2/blame/f134584c79d6289e5ac9283637bc8a31b926376c/content/kapacitor/v1.6/working/scraping-and-discovery.md#L74

Looks like we don't have docs specific to marathon, so this doesn't need a docs update at this time. However, the sample kapacitor.conf likely needs to be updated in the Kapacitor repo: https://github.com/influxdata/kapacitor/blob/b5af8896689fde42a883e6460a6cf76f23cfb8e6/etc/kapacitor/kapacitor.conf#L828-L838


Update/access gsuite identify provider

I have updated workflow for configuring Access for GSuite (now Google Workspaces) Identity Provider.
Google made some changes and I was unable to reproduce steps.
So I have updated text and add new images.

@fniko closing this, thanks so much for your work!


Added code style rules (Prettier, Eslint & Husky)

I see a lot of Pull requests saying things like "added a missing semicolon" (see #40), so I figured out it would be better if it was automated. This pull request adds prettier for code style, eslint for code linting (most rules are currently disabled in the client code as there seems to be a lot of temporary code) and husky to automatically execute prettier and eslint before commiting.
P.S.: English is not my main language, so please pardon any English mistakes

Ooooh, I love this! I want to develop skills for how to manage code styles better! Maybe I can learn this workflow and make a video about it.
One small nitpick is I think I like single quotes over double quotes? Should I change my thinking? It's not a dealbreaker for me!

I also prefer single quotes, but the code base currently uses double quotes and I wanted as little disruption as possible

I also prefer single quotes, but the code base currently uses double quotes and I wanted as little disruption as possible

Hah! Ok! I'll merge and can change to single later!

It's a really easy change: you just need to change singleQuotes from false to true in .prettierrc.


removed duplicated spring-boot-starter-thymeleaf

Due to the duplicate spring-boot-starter-thymeleaf dependecy, the build has a warning message below:
[WARNING]
[WARNING] Some problems were encountered while building the effective model for hu.sonrisa.gears:consultant-tool:war:0.0.1-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.springframework.boot:spring-boot-starter-thymeleaf:jar -> duplicate declaration of version ${spring-boot.version} @ io.github.jhipster:jhipster-dependencies:0.1.0, /Users/agaton/.m2/repository/io/github/jhipster/jhipster-dependencies/0.1.0/jhipster-dependencies-0.1.0.pom, line 379, column 25
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]

Thanks and congratulations for your PR.

Thanks! I was a bit confused by this, pretty sure I had checked my work carefully. But it was accidentally duplicated later, somehow, in this commit:
https://github.com/jhipster/jhipster-dependencies/commit/8dd8207159d322d822344a0375269e64c883db33


Fix Travis-related scripts

This PR does:

fix the script that updates READMEs' versions to also add and commit nested READMEs
Update github credentials used by travis (replaced "secure" should be the correct ones, they were added here)

Coverage remained the same at 86.153% when pulling 176fbc4a04a8fcbe3e5eb0c046161159d4dd1145 on mziccard:fix-travis-scripts into df3439df0295fdb2c97264a45260c07d60cd1bef on GoogleCloudPlatform:master.

Coverage remained the same at 86.153% when pulling 7d948c52665da34c188e09d16feaab78ac28a3b4 on mziccard:fix-travis-scripts into df3439df0295fdb2c97264a45260c07d60cd1bef on GoogleCloudPlatform:master.

Please @aozarov take a quick look


Fix pipelines

Close #83

:x: Build GuiStracini.HolidayAPI 3.3.254 failed (commit https://github.com/guibranco/GuiStracini.HolidayAPI/commit/37b536bf88 by @guistracini-outsurance-ie)

:white_check_mark: Build GuiStracini.HolidayAPI 3.3.256 completed (commit https://github.com/guibranco/GuiStracini.HolidayAPI/commit/9323ae53b2 by @guistracini-outsurance-ie)


feat(converter-runtime): support fixing converters

Converters with same source and target type (because you're just fixing a data type), are now supported to be part of the converter chain.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

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

Totals

Change from base Build<PHONE_NUMBER>8:
0.02%

Covered Lines:
266

Relevant Lines:
267

💛  - Coveralls


PKG -- [sdk] Create block wrapper methods

Addresses: https://github.com/onflow/fcl-js/issues/942
Creates wrapper methods for accessing block by id and by height more easily:
await sdk.block() // get latest block
await sdk.block({sealed: true}) // get latest sealed block
await sdk.block({id: 'abc'}) // get block by id
await sdk.block({height: 123}) // get block by height

Also note that we already have fcl.latestBlock() as a way to query the latest block


feat: Add IDs to user-menu-header title and subtitle

Changes proposed in this Pull Request:

Type both menuTitle and menuSbutitle as string | TemplateRef to have an easier way for customizing User menu header

You're welcome.
We could have something like this for example :
<ng-template #menuTitle>

       My awesome title

</ng-template>

<ng-template #menuSubtitle>
    <mat-icon
      fontIcon="home"
    ></mat-icon>

       My awesome subtitle

</ng-template>

<blui-user-menu
    [menuTitle]="menuTitle"
    [menuSubtitle]="menuSubtitle"
>
...
</blui-user-menu>

I noticed you changed the feature request in the middle of the PR. What is the underlying problem you are trying to solve with this PR?

I'm trying yo add IDs to both the user menu header's title and subtitle.
At first I thought about having ng-template to pass span/div/whatever with an id to the menuTitle and subTitle, but I realized there was a simpler option:
add IDs directly to the title and subtitle div in user-menu-header.component.ts.

I'm trying yo add IDs to both the user menu header's title and subtitle.
At first I thought about having ng-template to pass span/div/whatever with an id to the menuTitle and subTitle, but I realized there was a simpler option:
add IDs directly to the title and subtitle div in user-menu-header.component.ts.

I cans see from the PR that you are adding ID's but what problem are you trying to solve? Why do you need ID's on these elements? I'm trying to understand the root issue so we can solve it appropriately.

I want Ids there to run some automatic tests

Instead of adding ids directly onto each testable element, have you tried targeting elements via classname?
const header = document.getElementsByClassName('blui-user-menu-header')[0]; // Header   const title = document.getElementsByClassName('blui-user-menu-header-title')[0]; // Title   ...

I'm not the one making test in my organization. So i'm not the one targeting elements.
My role is to add IDs to the elements the validation team want to test

For testing, an id can be added to an element by running this code snippet before their tests.
document.getElementsByClassName('blui-user-menu-header-title')[0].id = 'my-id'

@RVieillard were you able to solve your issue using any of the recommendations @emclaug2 provided?

@RVieillard were you able to solve your issue using any of the recommendations @emclaug2 provided?

@RVieillard can you address this? Otherwise, I'll be closing this PR due to inactivity.

Problem has been solved, the PR can be closed


Add handling of ENTRYPOINT and CMD when "command" is not in policy

Container images may contain ENTRYPOINT and CMD directives and in
the case when "command" is missing in policy config, that information
needs to be inferred from the image itself.
Signed-off-by: Maksim An<EMAIL_ADDRESS>

@SeanTAllen @KenGordon FYI

Looks good to me


Move rill-developer to NPM workspaces

Issue
Currently, the root of rill-developer is a regular NPM project for the Svelte/Node local app with code in build-tools, scripts, src, static, test. Since we have moved to a monorepo, this is both confusing and clashes with other code in the repository. The Go and Java code mainly works anyway (except for minor things like excluding paths from Prettier), but it especially clashes with nested NPM projects like docs and web-cloud (see the notes in the PR).
Specifically, we need this to refactor components into a web-common (or web-core) folder, which both the local and cloud web applications can import from. Also see: Routes and code structure (Notion).
Solution
There are many tools available for dealing with monorepos. Some are cross-language (such as Bazel), some are language specific (such as Turborepo).
In Rill, we'll initially keep things simply by using native build tools – i.e. NPM (for Node), Maven (for Java) and Go. All these tools have very decent built-in monorepo support (through workspaces), and can all co-exist without clashes when configured correctly. In rill-developer, Maven and Go are already configured adequately.
This issue proposes to move our Node code to NPM workspaces (reference). NPM workspaces promote the same kind of project layout as other Typescript monorepo tools (like Nx and Turborepo), so this is a safe first step regardless of whether we'll need a more advanced build system in the future.
Specifically, it proposes the following workspaces:
docs/              # Docusaurus project with new Rill docs
docs-enterprise/   # Docusaurus project with legacy docs
web-cloud/         # SvelteKit project for cloud frontend
web-common/        # Code shared between cloud and local (like components, svelte-query hooks for runtime APIs, etc.)
web-local/         # SvelteKit project for local frontend

Things to do

[ ] Create folder web-local and move all the files related to the local app into it (incl. package.json, config files, Svelte frontend, Node backend, etc.)
[ ] Setup the web-common folder – initially, just put a simple "hello world" Svelte component into it.
[ ] Create a package.json file at the root of the repository that sets up NPM workspaces for web-local, web-cloud, docs and docs-enterprise. Configure the nested package.jsons accordingly. Make sure there's only one package-lock.json at the root.
[ ] Go through all the top-level config files (like tailwind.config.cjs, etc.) and determine whether or not they belong at the root. Config that stays at root should be general enough to apply to multiple folders in the repo (e.g. to all JS/TS files). (NOTE: You probably need to add a tsconfig.base.json file that nested tsconfig.json files extend).
[ ] Update any dependent scripts and tests to reflect the new paths
[ ] Update the CI steps for rill-developer to only run on pushes to relevant files (such as **.js or web-local/**). Travis doesn't have a native paths option, but Github Actions does, so it might be easier to just move to GH Actions (we allow both – with the long term goal of moving everything to GH Actions).

What does success look like?

You should be to import components across NPM workspaces. For example, in web-cloud you should be able to run: import { ... } from<EMAIL_ADDRESS>You should be able to run scripts in nested workspaces just by adding the -w workspace_name option. For example, npm run dev -w web-local should run the current local app.
CI should only run on changes to relevant files/paths
The repo root should look tidy and reflect the different components in the monorepo. For inspiration, see the Airbyte repo

Keep in mind that the next step after finishing this issue is to move the explore dashboard components to web-common and import them into web-cloud!

+cc @himadrisingh : This will have impact on build scripts and we would need your help to update the Makefile.


ListItemText CSS primary doesn't work

ListItemText CSS primary doesn't work on the MuiListItemText-primary

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I want to use the css primary to cover the MuiListItemText-primary style.
But it doesn't work.

Expected Behavior 🤔

class MuiListItemText-primary  should have my class style.
Steps to Reproduce 🕹

https://codesandbox.io/s/material-demo-shp3t
Context 🔦

I just want to change the ListItemText font-size with className.
Your Environment 🌎

Tech
Version

Material-UI
v4.4.3

React
v16.9

Browser
chrome77.0.3865.90

You either have to disabelTypography or inject the classname via primaryTypographyProps


Certificates:  fix bugs

Fix https://github.com/NuGet/NuGetGallery/issues/5868.

screenshots?

Before:

After:

@shishirx34, let's take that offline.  I didn't change the button in this PR.  The button can be dealt with in a separate PR if necessary.


WIP: Fix allas urls

Replaced object.pouta.csc.fi => a3s.fi

@Kallio pointed out that all commands need to be tested to make sure they work with  a3s too

#188 fixes the links, other changes are incorporated in this pull request.

Don't work on this, I will fix some things using reset and force push!

The links were fixed in #188 and no additional changes are done here, so  I will close this.


setup.py: Allow colorlog 4

I've packaged this up for openSUSE Tumbleweed, which is using colorlog 5, and the tests pass https://build.opensuse.org/package/show/home:jayvdb:branches:devel:languages:python/python-nox

The Appveyor breakage looks unrelated - a bug in pip/conda/etc on Python 3.5.

Hmm.  Problem is also occurring on Windows py37 https://github.com/theacodes/nox/pull/258

@dhermes , no breakage here ;-)

Rad, thanks for doing this and thank you @dhermes for taking a look. :)


Updated sound settings to store it in local storage

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #48931

Hey @naomi-lgbt please review the changes thanks

Hi @Riya267 it looks like my recent changes to the config location have broken your PR. Sorry about that! I'd be happy to fix it if you don't mind me pushing a commit onto your branch.

Hi @Riya267 it looks like my recent changes to the config location have broken your PR. Sorry about that! I'd be happy to fix it if you don't mind me pushing a commit onto your branch.

No worries, please go ahead and thanks for letting me know.


Adds highlight for march 25

Please remember to

[ ] Give the PR a meaningful title -- it will be shown in the release notes
[ ] Add (or remove) user questions associated with any updated docs

nothing from honeybadger for this week

@JosephSalisbury I added another suggestions. That's it from us. Nothing from Rainbow this week.
I'm a bit puzzled by the lack of info on apps.
@stone-z What about https://docs.giantswarm.io/changes/managed-apps/starboard-app/v0.6.0/ ?


sql.Scanner and driver.Valuer implementation strfmt types.

There are some test failure from path_test.go on my machine but it looks like some OSX-specific issue so not sure how to fix yet.
	Error Trace:	path_test.go:79

	Error:		Not equal: "/var/folders/ln/np47z2750376j3y5nqtk2wp00000gn/T/pkgpaths-2444302576/src/fuu/bir" (expected)
			        != "/private/var/folders/ln/np47z2750376j3y5nqtk2wp00000gn/T/pkgpaths-2444302576/src/fuu/bir" (actual)

FAIL
FAIL	github.com/go-swagger/go-swagger/swag	0.133s
?   	github.com/go-swagger/go-swagger/validate	[no test files]

Oh looks like all tests passed on circle and travis : )


AL Service Blueprint: Results Flow

Design or Research
Improve the AL Service Blueprint to include the results data flow.
Completion Criteria

[ ] The AL service blueprint includes results handling and accurately represents what AL PHL, Baptist, & Oracle requires.

Tasks

[x] We've updated the service blueprint to show the results flow
[x] Review current version of the blueprint
[x] Update based on ACK flow
[x] We've walked through the updated blueprint with AL PHL, Baptist, & Oracle and addressed any questions
[x] Static copy exported, uploaded to Confluence, and shared with CDC and partners
[ ] Note this as Future State in the diagram

Additional Context
Add any other context or screenshots about the work here.

Discussing during Team Collab later today


[#3297] Prevent magical bonuses from applying if the item is not magical

Closes #3297

Any situation you think that an item will have the mgc property but that property is not in the valid properties list?

Any situation you think that an item will have the mgc property but that property is not in the valid properties list?

We have support for adjusting these properties, so one could technically make it an invalid property for one of the system's item types, or a module subtype.

Any situation you think that an item will have the mgc property but that property is not in the valid properties list?

We have support for adjusting these properties, so one could technically make it an invalid property for one of the system's item types, or a module subtype.

Still not convinced it is necessary, but if you keep it then you should probably do two has checks rather than an intersection, because the monkey-patched set intersection method has to iterate over all entries in the set.
// O(1) time instead of O(n) time
const isMagical = this.validProperties.has("mgc") && this.properties.has("mgc");


Input popup draws over packer display

Describe the bug
I run :PackerSync when there is a plugin that has been removed from my config. Packer displays a notification to show what is being removed then prompts for Y|N input. Noice puts the Input prompt over Packer's display of what is being removed.
Noice disabled:

Noice enabled

Which version of Neovim are you using?
nightly NVIM v0.9.0-dev-155+g771824128
To Reproduce
Steps to reproduce the behavior:

Use packer. Remove a previously installed plugin from your configuration.
Run :PackerClean or "PackerSync inside of nvim with Noice enabled.

Expected Behavior
The display and the input prompt do not cover each other. Either noice somehow picks up Packer's display so that it handles it or it detects that it is there so as not to overlay it. Or something else that keeps displays in view.
Screenshots
See above.

Noice will now automatically move out of the way of existing floating windows


[Feature] Delete partition in the metastore when it expires.

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Currently, the partition will not be cleaned in metastore when the partition is expired. I think it should be delete to maintain the
correct view of the metadata.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

CC @JingsongLi WDYT ?

Close as duplicated with https://github.com/apache/paimon/issues/3514


Upload external libraries

I used jxl aka Jcalendar to graphically show the calendar, also I used jexcel to save the data base in xls file compatible with Excel, OpenOffice and Numbers (Mac)

Just in case it's necessary, I'll upload GSON, to import export json files and store data in the app


Any C/C++ API/interface?

Hi,
I'm interested in embedding several of your implemented wavelet transforms into a C++ code project, so I'd like to know if there's any C/C++ API/interface available for using the transforms provided in this package? Thanks.

@Meso272 there isn't a C/C++ API unfortunately. Even if that could be exposed, the implementations are in Cython which means you'd pull in CPython - probably not what you want for a C or C++ project.

Thanks!

Hi, have find any useseful c/c++ api


Addresses https://github.com/moneypenny/gulp-ruby-haml/issues/10

This patch will allow the haml() plugin to process haml without requiring it to exist on the physical disk.
Instead of supplying the haml command with the path of an input file, we supply the switch -s, and write the haml to childprocess.stdin. This lets us do the following (for instance)

gulp.src('foo/bar/**/*.haml')
  .pipe(replace('albert', 'dilbert'))
  .pipe(haml())
  .pipe(gulp.dest('baz'));

Earlier, since (the current version) plugin works by passing the absolute path of the haml source file, one would first have to write the output of replace to a temp folder.

Tests still run locally. Thanks!

:+1: Thank you for the awesome plugin!


Add snakefmt to precommit

Proposed changes
Updates pyproject.toml to remove settings for pylint. Add settings for snakefmt
Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Other (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

[ ] Changes have been tested to ensure that fix is effective or that a feature works.
[x] Changes pass the unit tests
[x] Code has been run through the poe quality task
[x] I have included necessary documentation or comments (as necessary)
[ ] Any dependent changes have been merged and published

Notes
All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

We should run pre-commit run --all-files, maybe in a separate PR. There will be a lot of changes...

We should also double check that the GH actions check align with the pre-commit hooks, maybe in the same PR. I think if the checks pass pre-commit run --all-files shouldn't want to change anything.

See #18 for issue, will merge this in.


Update docs, run gendocs in travis

@jlowdermilk
This is causing trouble in a totally unrelated PR

Not the first time this annoyance has happened. #5815 updated the pflags library which corrected how flag help is displayed. Unfortunately our build script is not smart about picking up on godep changes, so you'll need to run make clean and rebuild.

If it runs as part of travis, why is it not blocking PRs that needs docs
regenerated?
On Wed, Mar 25, 2015 at 11:49 AM, Jeff Lowdermilk<EMAIL_ADDRESS>wrote:

Not the first time this annoyance has happened. #5815
https://github.com/GoogleCloudPlatform/kubernetes/pull/5815 updated the
pflags library which corrected how flag help is displayed. Unfortunately
our build script is not smart about picking up on godep changes, so you'll
need to run make clean and rebuild.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5937#issuecomment-86169493
.

flipping make clean fixes it


Linux lies about its monotonic clock

The POSIX standard prescribes that the monotonic clock keeps running during system suspends. But Linux's clock stops.

Cannot fix.


CUDA 10 / SM 75 Cmake Target

Add SM75 to the (default) list of target architectures if none are specified at CMake time, if CUDA 10 or greater is in use.
    # If the CUDA version is >= 10.0, build for Turing
    if(CMAKE_CUDA_COMPILER_VERSION GREATER_EQUAL 10.0 )
        list(APPEND SMS "75") # CUDA >= 10.0
    endif()

should be added to the relevant position in cmake/common.cmake

Closing as now included in the current development branch


Add plugin package for Fastify server

Feature Request:
It would be awesome if there was an official plugin to support Fastify servers; specifically version 3.x where Express middleware is no longer supported out of the box.
https://www.fastify.io/

Hi @jgeschwendt - thanks for your feedback. This is something which is on our roadmap and we hope to implement in the future.

@jgeschwendt, you can use fasify hooks to integrate Bugsnag:
const Bugsnag = require('@bugsnag/js')
Bugsnag.start({ apiKey: <your api key> })

server.addHook('onError', (request, reply, error, done) => {
  // Only send Bugsnag errors when not in development
  if (process.env.NODE_ENV !== 'development') {
    Bugsnag.notify(error)
  }
  done()
})


Allow to restore original pushed message class on consume

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

This PR allows you to push your own message class and then get it back after it was consumed.
See new tests for details.

@samdark issue for the docs improvement: #215


Add blank line before heading rule

This PR adds a new rule, Heading blank lines top that adds a blank line above every # Heading.
It's a very small modification of the Heading blank lines rule. I wasn't able to get it working as an option under that rule, but I'm open to suggestions as to how to do that if you want!

Thanks for the PR! I would prefer it as an option of Heading blank lines, maybe top=true. I think you can do it by just putting the // trim blank lines before headings line in an if. Look at YAML timestamp for an example of options.
Also can you add the yarn.lock file to the .gitignore?

Alright I gave making it an option under the Heading blank lines rule. Setting bottom="false" should now ignore adding spaces below headings.
I wasn't entirely sure how to test the option with npm test, but the logic stayed the same. Let me know if you need any more changes or feel free to make any adjustments yourself!


Text Select Enable - All HTML Elements

Allows text to be selected on all HTML elements, with cross-browser support.
The * was used because  user-select: text; CSS only affect text and the select all selector will make sure it hits all of them, making sure none are missed.
*I've not got this site set up locally to test, but for anyone that has, might be worth adding this code too for a little zest 👍
/*$lbry-teal-3 = #38d9a9 ???*/
::-moz-selection {
    color: #fff;
    background: $lbry-teal-3;
}
::selection {
    color: #fff;
    background: $lbry-teal-3;
}

This isn't necessary for all elements. Only elements with informational text need to be selectable. A module I included made everything unselectable.
Thanks for the issue, I'll close this and modify the module.


Create configuration that exposes port 8086

For use on solidcommunity.net

See also https://github.com/CommunitySolidServer/Recipes/issues/31

@thhck can you have a look today?
@janschill did you have a chance to look at it yesterday in the train?

@thhck can you have a look today? @janschill did you have a chance to look at it yesterday in the train?

I had a spotty connection. I was only able to get a bit more familiar with the current NSS deployment. Nothing reportable. Continuing a bit more now

Looks like @bourgeoa got it working
https://matrix.to/#/!VAJLTawStGAyYwzTTY:gitter.im/$F2KdIjuhNKNUxdRHl7lYR2zxA_ArGHP5wB_PtBwtdxs?via=gitter.im&via=matrix.org&via=attendees.fosdem.org
We have a video call tomorrow morning 10:30am CET

Done, see https://cloud.pondersource.com:8086 and https://github.com/solid-contrib/pivot#example-usage as an example.


empty index.html is generated when build destination is specified

I'm using a grunt task to build the hugo site.
While I can correctly see the home page running hugo serve, when I run the build task specifying a destination hugo --destination=../build/dist hugo generates an empty index.html
If I build the site with the default hugo command, the build is successful and inside the public folder I can correctly see the generated index.html
The other post and list pages are all correctly generated.

update to 0.17 seems to have fixed it


Temperature sensor documentation incomplete

The datasheet for the temperature sensor says, in section 15.3.2 Temperature Sensor Sampling The temperature value is obtained according to the conversion relationship between voltage and temperature. Please refer to the evaluation board example program for details.
However, the (only) example ADC program simply reads the temperature sensor channel, without any conversion to a temperature: https://github.com/openwch/ch583/blob/main/EVT/EXAM/ADC/src/Main.c#L51-L62
Please document how we can actually use the temperature sensor.

You can find the ADC_GetCurrentTS function at the end of the ch58X_adC.c file to convert temperature values:
https://github.com/openwch/ch583/blob/main/EVT/EXAM/SRC/StdPeriphDriver/CH58x_adc.c#L214-L232

thank you! missed that!

I've been looking more at this, and I'm afraid I've just got more questions :)  I can change the temperature of my ch582m device, and see the temp sensor raw readings go up and down, so I'm confident that it works but getting a real number out of it is... not so obvious.  for ~ambient ~24°C, the linked function is giving me -36°C.  I've also tried the function at https://github.com/openwch/ch583/blob/main/Application/wristband/firmware/Demo_Firmware/StdPeriphDriver/CH58x_adc.c#L163-L172 which produces different (still "wrong") values.  (That function needs a cast to int on C25 otherwise nothing under 25°C is calculated properly anyway)
I've plotted the full range of values these functions generate, and they've giving quite different slopes, but still, it's just two linear equations.  What is the value in in ROM_CFG_TMP_25C meant to be giving us?  an offset? or a slope?  If it's a slope, we need more information, because the two formulas given are both wrong anyway.  If it's an offset, we need to be told the constant slope.
here's plotting the values generated by both functions for the ROM_CFG_TMP_25C value on my own board:

@Hikari-ky @zerosensei Would be lovely to get better support from WCH – the chips are really nice, but the (English) documentation and support is still lacking.


Directline API : 502 Bad Gateway error

I am getting the response from the Bot intermittently. While sending the request, I am getting the below error.
POST https://directline.botframework.com/v3/directline/conversations/B56KT664xddDwc9SBbL4md/activities 502 (Bad Gateway)
I am also getting error in botchat.js. Is something problem with directline api? Can anyone help me to solve this issue?

Yes, closing as this is a duplicate of https://github.com/Microsoft/BotBuilder/issues/2201


Add description about Microsoft-hosted agent.

We can use Microsoft-hosted agent to deploy applications, but sometimes there are firewall/proxy/restricted IP configuration between DevOps and destinations. In this case, users must know VMs for Microsoft-hosted agent use any of Azure datacenters IP range. This has impact for users and they may need to consider using Self-hosted agent. So this page should have the link to Microsoft-hosted agent page so that users can find the information easily.

@rikat-ms thanks for your help in this! Merging this in


Fix delete permissions on storage

Currently, deleting a survey can fail because the iam is not authorized to delete the objects.
Eg Oct 4 - 21:18 UTC

Temporary protections implemented in #281 to avoid errors


Rename project

Not a big deal, but I think why not renaming this project something unique to avoid conflict with other projects that have same name, for example:
https://sup-heliotrope.github.io/
https://sources.debian.org/src/sup/20100519-1/debian/sup.doc/

Eh. I think there'd have to be confusion about this in the first place. No one I've talked to has even heard of my project, let alone those ones.


[macos]. openresty  symbol not found in flat namespace '_luaL_prepbuffsize'

[macos]. openresty  symbol not found in flat namespace '_luaL_prepbuffsize'

openresty -c nginx-debug.conf

error  info
2022/03/25 16:54:11 [error] 34351#0: *4 lua entry thread aborted: runtime error: error loading module 'socket.core' from file '/usr/local/lib/lua/5.4/socket/core.so':
	dlopen(/usr/local/lib/lua/5.4/socket/core.so, 0x0006): symbol not found in flat namespace '_luaL_prepbuffsize'
stack traceback:
coroutine 0:
	[C]: in function 'require'
	...nresty-<IP_ADDRESS>/bin/nginx/lua-resty-access-pass/test.lua:9: in main chunk, client: <IP_ADDRESS>, server: localhost, request: "GET /test/debug HTTP/1.1", host: "localhost:1010"
2022/03/25 16:54:11 [error] 34351#0: *4 lua entry thread aborted: runtime error: error loading module 'socket.core' from file '/usr/local/lib/lua/5.4/socket/core.so':
	dlopen(/usr/local/lib/lua/5.4/socket/core.so, 0x0006): symbol not found in flat namespace '_luaL_prepbuffsize'
stack traceback:
coroutine 0:
	[C]: in function 'require'
	...nresty-<IP_ADDRESS>/bin/nginx/lua-resty-access-pass/test.lua:9: in main chunk, client: <IP_ADDRESS>, server: localhost, request: "GET /test/debug HTTP/1.1", host: "localhost:1010"
2022/03/25 16:54:11 [error] 34351#0: *4 lua entry thread aborted: runtime error: error loading module 'socket.core' from file '/usr/local/lib/lua/5.4/socket/core.so':
	dlopen(/usr/local/lib/lua/5.4/socket/core.so, 0x0006): symbol not found in flat namespace '_luaL_prepbuffsize'
stack traceback:
coroutine 0:
	[C]: in function 'require'
	...nresty-<IP_ADDRESS>/bin/nginx/lua-resty-access-pass/test.lua:9: in main chunk, client: <IP_ADDRESS>, server: localhost, request: "GET /test/debug HTTP/1.1", host: "localhost:1010"

please help me, thank you.

What version of LuaSocket are you using? How did you build & install it? Are you sure you built it against the same Lua headers as the version of Lua you are running?

Happy to look into this if there are further details and you can answer questions. It still seems like this is a miss-match between the headers you are building against and the Lua you are running. Comment back with info if there is still something that needs addressing here.

I got the same problem on my Mac too.
2024/01/25 16:23:36 [error] 30771#476790: *4 lua entry thread aborted: runtime error: error loading module 'socket.core' from file './socket/core.so': 	dlopen(./socket/core.so, 0x0006): symbol not found in flat namespace '_luaL_prepbuffsize'
I install LuaSocket 3.1.0-1 via luarocks with following command: luarocks install luasocket
Lua version: 5.4.3
Mac version:  macOS Sonoma 14.2.1

@tenpend How is your error related to OpenResty? What command or code are you running that shows that error? If it isn't OpenResty related please open a new issue report for your situation.

Yes, I'm running my code inside openresty.
Full error stack is:
2024/01/25 16:23:36 [error] 30771#476790: *4 lua entry thread aborted: runtime error: error loading module 'socket.core' from file './socket/core.so':
dlopen(./socket/core.so, 0x0006): symbol not found in flat namespace '_luaL_prepbuffsize'
stack traceback:
coroutine 0:
[C]: in function 'require'
...openenresty//lua/vendor/libs/util/common_util.lua:21: in function 'GetLocalIP'
...vendor/libs/agollo/repository/remoteApolloRepository.lua:155: in function 'AssembleURL'
...vendor/libs/agollo/repository/remoteApolloRepository.lua:51: in function 'GetConfigOriginData'
...openresty//lua/vendor/libs/agollo/config.lua:68: in function 'initialize'
...openresty//lua/vendor/libs/agollo/config.lua:23: in function 'new'
...openresty//lua/vendor/libs/agollo/configFactory.lua:19: in function 'GetConfigByNameSpace'
...openresty//lua/vendor/libs/agollo/configService.lua:28: in function 'GetConfig'
...openresty//lua/util.lua:19: in function 'get_redis_connection'
...openresty//lua/redis_notifier.lua:12: in function <... openresty/lua/redis_notifier.lua:11>, context: ngx.timer
code is:
function _M.GetLocalIP()
if localIP then
return localIP
end
local socket = require("socket")
local function GetAdd(hostname)
    local ip, resolved = socket.dns.toip(hostname)
    local ListTab = {}
    if resolved and "table" == type(resolved) then
        for k, v in ipairs(resolved.ip) do
            table.insert(ListTab, v)
        end
    end
    return ListTab
end
local ip = GetAdd(socket.dns.gethostname())
if ip and "table" == type(ip) and next(ip) and unpack(ip) then
    localIP = unpack(ip)
    return localIP
else
    localIP = "<IP_ADDRESS>"
end
return "<IP_ADDRESS>"

end

@tenpend How do you solve this issue? I have the same problem.

The problem here is mixing lua versions. @tenpend  is compiling luasocket against lua 5.4, and then loads it from openresty, which uses a (butchered) version of luajit.
Install openresty, then install luarocks, using the luajit and headers of openresty, and only then use luarocks to install luasocket.


Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges

Description
For past 1 month we have been testing difference in performance for a files getting opened with IOContext.RANDOM vs IOContext.READ specially during merges with Lucene version 9.11.1 and Opensearch version 2.17. We started this deep-dive when we saw an increase in time for our force merges.
Background
Opensearch k-NN plugin provides the vector search capabilities with Opensearch. The architecture of k-NN plugin is very similar to how Lucene implements the vector search with few small key differences. Before 2.17 version of Opensearch, opensearch was using dvd files to store the raw the vectors and graphs files are stored separately. These graphs are not built using Lucene HNSW but with some external libraries like Faiss.
In 2.17 version of Opensearch, we started using KNNFlatVectorFormat to store and read the raw vectors in place of dvd files. As reading vectors from .vec files as float[] is more efficient than reading byte[] and then converting to float[]. Ref: https://github.com/opensearch-project/k-NN/issues/1853
Observations
After doing the switch what we observed that our merge time for a 10M 768D dataset is increased by 20%. We did an extensive deep-dive/experiments on the root cause(ref1, ref2) and code difference between dvd files and .vec files format and was able to see that IOContext.RANDOM with .vec files is causing this regression.
This regression comes because during merges for every Lucene99FlatVectorsReader there are some operations happens like checkIntegrity(which does checksum of whole file), reading of all vector values to create new segment which are more of sequential reads than random reads.
I do believe that having a RANDOM madvise on .vec file is more beneficial for search and graph merges as Lucene uses this file as a way to store raw vectors for HNSW. BTW This PR added the capability: https://github.com/apache/lucene/pull/13267 for Random IOContext to .vec files.
Solutions Tried:
We have been trying multiple solution(all on Lucene version 9.11.1) and have been in touch with @uschindler and @mikemccand over
<EMAIL_ADDRESS>:

Switching the IOContext from RANDOM to READ: This actually helped in reducing the merges time so our original 20% increase in merge time was reduced to 0%. But making this change from RANDOM to READ for .vec added the extra latency for Lucene HNSW search. We saw 2x increase in latency because of this on a 10M 768D dataset. Code ref
Creating a new IndexInput in checkIntegrity function: This solution[ref] creates a new IndexInput in checkIntegrity function of Lucene99FlatVectorsReader with madvise as SEQUENTIAL. One of the biggest con it has is we are creating 2 indexinputs for same file in different threads and it not been recommended as per this.
We also tried enabling the preload functionality for .vec file, it really helped in reducing the merge time similar to #1, but suffered 2x latency increase during search.
We borrowed some code from latest version of Lucene of changing the mdvise before doing integrity checks and merging of flat vectors and applied it on 9.11.1 version. ref: https://github.com/shatejas/lucene/commit/4de387288d70b4d8aede45ef3095ae6c1e189331#diff-e0a29611df21f6d32a461e2d24db1585cdf3a8590f08d93b097f0dd84684ebc8R316, but with this we expect any search that is happening during the merges will have high latencies. This increase is a hypothesis we have not run the benchmarks around this.

What is an ideal solution?
In my mind an ideal solution will be the one which takes the advantage of different type of madvise and changes the madvise for the file based on the need(if merge of flatvectors is happening use Sequential, but if HNSW graph is building/searching then flip back to RANDOM). I am not sure what could be a consequence of this would like to know what community thinks about it. Similar to option 4.
Also, I do believe that since Lucene99FlatVectorsFormat now extends KNNVectorsFormat thanks to this PR: https://github.com/apache/lucene/pull/13469, having an ability to change the madvise from consumers of this format is needed. So that Lucene99FlatVectorsFormat can be used independently and not always tied with HNSW.
FAQ

On what machines the benchmarks were performed with 10M 768D dataset?
Since Opensearch is distributed Lucene, the setup was like this:

3 Opensearch nodes was used.
All nodes had 32GB of Heap
All nodes had 128GB of RAM and 16 vCPUs.
The 10M dataset was divided in 6 lucene indices aka primary shards. So per lucene index there was 1.6M docs.
Only vector field was indexed.

Is the benchmarks performed on Lucene library independently?
No, we have not performed any benchmarks with Lucene library independently, but I am working on having a reproducible setup. If there are some easy way to setup and reproduce, please share.

cc: @shatejas, @vamshin, @jmazanec15

Thanks for opening the issue. I already made similar suggestion in another PR and also the mailing list.
I'd go the route and temporarily change the IOContext to SEQUENTIAL. This may of course slow down random reads, but on the other hand once the whole file is merged away (and was therefor read) it should be in FS cache anyways. If not, you have too less memory, like @s1monw says: "Add more RUM" :-)
Users of the old segment which was merged away will only use it till the next IndexReader reopen, soby signaling that we read it only once it's a good idea to get rid of it from cache soon.
So my proposal is:

Add a method to Indexinput to change the IOContext, but document it in a valid way that all clones or slices opened at same time are also affected.
Before merging of segments, we should add a hook to the codec so it can call some special method on the incoming CodecReader to "make it ready for merging" and "revert to normal use". This could instruct the codec to apply different madvise advices or restore them. I am not sure what the best API for that is, was just a quick idea (haven't looked at the different codec components). In general the hooks should be available for all codecs components, not only DocValues and Vectors. Because also merging of stored fields may be improved by switching to SEQUENTIAL to to higher read-ahead and less paging requests in kernel.

@jpountz ping.

That makes sense to me.
I wonder if we actually need to revert the advice back to normal in the end, or if we can optimistically assume that it's unlikely that we'll need to reclaim that RAM for something else before the next refresh picks up this segment.
In terms of hooking into existing APIs, the getMergeInstance() method of our file formats feels like a natural place to change the read advice.

@uschindler On a high level it makes sense to me. I have a couple of questions so that I understand this better

Add a method to Indexinput to change the IOContext (without cloning it),

I am interested in understanding when its appropriate to clone. Based on the javadoc for IndexInput, for multithreaded use IndexInput must be cloned. My understanding is that merges will have a separate thread. Since the Readers are pooled and the same instance is used - I cloned it when I was trying to benchmark the solution. Would appreciate if you can give insights on why the indexInput shouldn't be cloned in this case.

Cloning a reader wont clone any input which is a fully different thing. Don't care about cloning or not for implementing this issue. The Javadocs and usage pattern (when to clone) is more about stateful use of IndexInputs (they have a read position which can't be updated from multiple threads). If you are about pure random access, you can get a view on it as RandomAccessInput (which is sometimes used for Lucene). In all cases: The cloned inputs use exactly the same MemorySegments behind scenes (in former days it was ByteBuffers, those were also duped for clones).
What I wanted to say is: When you change the read advice, it will affect all clones, too. Therefor it is not needed to create a clone of the IndexInput. So basically it simplifies thigs: The CodecReader that is used for merging (and used at same time also for searching) can just be instucted to change the read advice on its backing IndexInput. Thats relatively simple to implenment and won't affect the current behaviour how merging works.

"revert to normal use"

In the benchmarking code, I did not revert it back thinking the reader will be closed and a new reader will be opened with the intended IOContext in this case random. Would you be able to share insights on reverting it back considering there will be new reader.

As this is just an advise: When done with merging, just revert back. Opening new readers is too expensive and mostly not useful. In addition, you can't control if searchers using the index in parallel reopen the readers soon. @jpountz already discussed that. This largely depends on how often you reopen IndexReaders. So in general it would be a good idea to revert back to the original state if the IndexReader is still used for longer time. This really depends on the usage pattern.
Reverting to normal use is as simple to implement as the initial change. Just change the advice on any of the open IndexInputs, no matter if it is shared by multiple readers and revert back at end. Thats totally uncoupled from the internals of IndexReaders.
Uwe

Understood, so with not cloning we are avoiding any ambiguity whether the original and other clones are getting affected or not. Not cloning makes it clear that any thread using the reader will get affected
With regards to reverting, its restoring the previous state. Wrapper approach sounds good to me, I will try it out.
Thanks @uschindler and @jpountz for your inputs!

@uschindler and @jpountz thanks for your inputs and detailed explanation. @shatejas I think all the required details are present, so are you going to raise a PR for this?
@uschindler and @jpountz 1 more thing I would like to confirm once the PR is raised, till what version of Lucene the change can be backported to? Ideally I would like to get it backported till 9.12 version. But would like to know your inputs too.

Opening new readers is too expensive and mostly not useful.

@uschindler one question on this, the reason why you say opening new readers is expensive because readers mostly open new IndexInput on a file? Also, one more question not related to particularly to this gh issue, does doing multiple times new IndexInput(fileName) opens the underline file multiple times and maps it at different memory address(if MMapDirectory is used) or the file is still mapped at same memory address?

@shatejas I think all the required details are present, so are you going to raise a PR for this?

Yeah I am working on it, I have the changes and I am trying to figure out a good way to benchmark lucene

Opening new readers is too expensive and mostly not useful.

@uschindler one question on this, the reason why you say opening new readers is expensive because readers mostly open new IndexInput on a file? Also, one more question not related to particularly to this gh issue, does doing multiple times new IndexInput(fileName) opens the underline file multiple times and maps it at different memory address(if MMapDirectory is used) or the file is still mapped at same memory address?

When you open the same file multiple times it mmaps several times. Lucene does not do this and should not do this. For this we have "clone()". So as said before: Just change the
It is expensive to open new index inputs for the reasons mentioned before.

Please stick with the approach: Plan to implement an API to tell an existing IndexReader to switch to "merge" mode and the underlying codec then can optionally change the madvise for the already open indexinputs. When done, switch back.

So as said before: Just change the madvise on already open indexinput.

@uschindler, sorry for the confusion. The plan was never to open multiple files. The question was more of general question from my side to understand the behavior.
The implementation plan is still the same which you have recommended. I hope this clarify things.


[Feat]: GeekTable .update() function

What new feature are you looking for / expect?
struct Users {
    id: PrimaryKey<i32>,
    // ...
}

fn main() -> Result<()> {
    let user = User::new(...);
    user.update(&conn)?;

    // ...
}

Expectations
Required / Manditory Feature

Added in v0.2.1


"identical source files" failing typechecker tests

Because nobody ever runs the tests for the typechecker :-(

     [java] error [identical source files: test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon and test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-3:64 of com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon
     [java] error [identical source files: test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon and test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-5:0 of com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon
     [java] error [identical source files: test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon and test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-3:64 of com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon
     [java] error [identical source files: test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon and test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-5:0 of com/redhat/ceylon/compiler/typechecker/test/moduleb/module.ceylon
     [java] error [identical source files: test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon and test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-3:64 of com/redhat/ceylon/compiler/typechecker/test/modulec/module.ceylon
     [java] error [identical source files: test/moduledep2/com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon and test/moduledep1/com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon (a module/package descriptor should be defined only once, even in case of multiple source directories)] at 1:0-3:64 of com/redhat/ceylon/compiler/typechecker/test/moduled/module.ceylon

@gavinking I was wondering if you could take a look at those tests yourself for a moment. I think the compilation for those 3 modules (moduleb, modulec and moduled) used to pass even though they were really incorrect (because they have duplicate module.ceylon files). So after my fix the typechecker now  correctly complains about those duplicate files. But without knowing what the tests are supposed to do I don't really know the proper way to fix them.

@quintesse I did not write those tests, so I'm not sure.

However, it appears that there are different modules with the same name (but different version), being loaded into the same typechecker via different source directories. I assume that we must have used to allow this.

You didn't? Oh, that's surprising, I thought basically everything in the typechecker was written by you ^^
But you do agree then that those tests seem to be wrong? In the compilation that fails 2 source directories are used and both contain module.ceylon files for the exact same modules, which can't be right, right?

I thought basically everything in the typechecker was written by you

No, the module-loading stuff was written by @emmanuelbernard.

In the compilation that fails 2 source directories are used and both contain module.ceylon files for the exact same modules, which can't be right, right?

They have different versions. So can't is too strong of a word here.

I assume that we must have used to allow this.

It seems the typechecker did, but the backends never allowed this. From the moment we implemented multiple source folders the backends check for duplicate files before ever calling the typechecker.

So why does the typechecker not allow it anymore?

They have different versions. So can't is too strong of a word here.

Perhaps, but duplicate files have been forbidden for as long as I know...
(I actually allowed them for a short while, allowing you to override files, but I was overruled and it was made illegal)

Because there was a bug in the typechecker with the way it would assign owning modules to Units. In the case of multiple source folders the Units that were in the folder that did not contain the module.ceylon file they would get assigned to the default module. The backends then worked around that be re-assigning the correct module. But that caused other problems so I fixed the underlying problem in the typechecker. But the side-effect of that was that the typechecker now actually notices when there are duplicate module files :)

I can't imagine why someone would want to treat multiple source directories as anything but simple overlays.
And trying to support both approaches will lead to ambiguities.

Well, OK, fine, so it used to work by accident.

I can't imagine why...

Well actually you could do some pretty nifty build tricks with it. For example you could create a module but have a special "overlay" for testing purposes that would add or change imports.
But the objection that this would probably be hell to support in IDEs convinced me at the time not to pursue this any further.

Well, OK, fine, so it used to work by accident.

Which might mean that perhaps those tests could be removed... assuming that the only thing they tested was the ability to "override" certain files with others.

Well actually you could do some pretty nifty build tricks with it. For example you could create a module but have a special "overlay" for testing purposes that would add or change imports.

Ok, yeah, I guess that might be a third variation.
But I suppose with simple overlays you could have sources-main/, sources-test/, sources-mod-descriptor-prod/, and always compile with sources-main/ and one of the other two. (sources-test/ would include a module.ceylon, but sources-main/ would not.)

Ok, so this does not seem to have to do with "overlays" at all, but just the fact that from the PoV of the typechecker there is no problem in compiling several different versions of the same module in the same invocation of the typechecker!
And it uses that fact to perform some tests about (transitively) importing different versions of the same module and the conflicts that can occur.
Compiling several different versions of the same module simultaneously isn't something that is supported by the backends, som I'm not sure the typechecker should support this either... but it does mean that I have no idea how to "fix" these tests @gavinking :(

Jesus Tako, just rename the damn modules, do I have to do every tiny little thing myself?

Dude, I'm trying to fix your precious tests for you, okay. I could care less about them.
Renaming them (or removing them, like I did) just breaks the moduletestexportisolation and moduletestdiffversionexport tests.
Can I make the errors go away? Sure, but then the tests wouldn't test anymore the thing that they were written for!

@quintesse would it work to put one set of sources in a .src zip file in a modules directory the typechecker can see?

@jvasileff I thought that was a good idea, so I tried it, but unfortunately the typechecker is actually pretty smart and it still complains that the module.ceylon file in the .src file is a duplicate. I can try removing the module file and see if I can fool it that way, but I somehow doubt it...

Darn.
Well, I hope this doesn’t point to a bigger problem then, if you do indeed do what the test is trying to test for, and import conflicting versions while using the default model loader.

On Jul 12, 2016, at 3:12 PM, Tako Schotanus<EMAIL_ADDRESS>wrote:
@jvasileff https://github.com/jvasileff I thought that was a good idea, so I tried it, but unfortunately the typechecker is actually pretty smart and it still complains that the module.ceylon file in the .src file is a duplicate. I can try removing the module file and see if I can fool it that way, but I somehow doubt it...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ceylon/ceylon/issues/6332#issuecomment-232149211, or mute the thread https://github.com/notifications/unsubscribe/AAOaEoAjhMYhKXxr_rwPK0YI21KNpOEvks5qU-c5gaJpZM4I9vAf.

Oh, then I can I take back my other reply :)

On Jul 12, 2016, at 3:18 PM, Tako Schotanus<EMAIL_ADDRESS>wrote:
ha! that did work! Nice job @jvasileff https://github.com/jvasileff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ceylon/ceylon/issues/6332#issuecomment-232150615, or mute the thread https://github.com/notifications/unsubscribe/AAOaEmbjukYND2CS51ptTutRXAUYC9HVks5qU-h7gaJpZM4I9vAf.


Backport changes relating to deploy and upgrade of rancher server using custom image and env

@bmdepesa Can you review these changes?

LGTM


Device Buffer get's not cleared if a config is uploaded

After changing and uploading a new config the devive buffer gets not cleared. Added the missing function solves this issue.
Fixes #181

Please have a special look on the comments to the function void OnSaveConfig(). For me it was helpfull to test things about config "upload" w/o connected to the GUI. Debug prints from the firmware are not displayed in the terminal from the GUI, therefore I have to test it with a serial terminal.
If the comments are not desired, I will delete them and update the pull request.


Show tests

This PR demonstrates using hint (Haskell Interpreter) to verify that a Show instance will produce valid Haskell code by attempting to compile and evaluate the string returned by show as an expression.
This test fails in this manner to show that the current Show instance for MetaData does not produce valid Haskell code because the constructor MetaData' is not exported:
Show tests
  Show MetaData: FAIL (2.72s)
      ✗ Show MetaData failed at test/Test/Shelley/Spec/Ledger/MetaData/ShowSpec.hs:28:13
        after 1 test.

           ┏━━ test/Test/Shelley/Spec/Ledger/MetaData/ShowSpec.hs ━━━
        22 ┃ prop_MetaData_Show :: Property
        23 ┃ prop_MetaData_Show = property $ do
        24 ┃   expected <- forAll . pure $ MD.MetaData (M.singleton 0 (MD.List [MD.I 5, MD.S "hello"]))
           ┃   │ MetaData'
           ┃   │   { mdMap = fromList [ ( 0 , List [ I 5 , S "hello" ] ) ]
           ┃   │   , mdBytes = "\161\NUL\130\ENQehello"
           ┃   │   }
        25 ┃   result <- liftIO $ HI.runInterpreter $ do
        26 ┃     HI.setImports ["Prelude", "Shelley.Spec.Ledger.MetaData"]
        27 ┃     HI.interpret (show expected) expected
        28 ┃   actual <- evalEither result
           ┃   ^^^^^^^^^^^^^^^^^^^^^^^^^^^
           ┃   │ WontCompile
           ┃   │   [ GhcError
           ┃   │       { errMsg =
           ┃   │           "<interactive>:2:1: error:\n    Not in scope: data constructor \8216MetaData'\8217\n    Perhaps you meant \8216MetaData\8217 (imported from Shelley.Spec.Ledger.MetaData)"
           ┃   │       }
           ┃   │   , GhcError
           ┃   │       { errMsg =
           ┃   │           "<interactive>:2:12: error: Not in scope: \8216mdMap\8217"
           ┃   │       }
           ┃   │   , GhcError
           ┃   │       { errMsg =
           ┃   │           "<interactive>:2:57: error: Not in scope: \8216mdBytes\8217"
           ┃   │       }
           ┃   │   ]
        29 ┃   actual === expected

        This failure can be reproduced by running:
        > recheck (Size 0) (Seed<PHONE_NUMBER>5288852118<PHONE_NUMBER>0776736501) Show MetaData

    Use '--hedgehog-replay "Size 0 Seed<PHONE_NUMBER>5288852118<PHONE_NUMBER>0776736501"' to reproduce.

1 out of 1 tests failed (2.72s)

This seems to have been abandoned. Closing until such time as it's ready for review.


changed references from concourse.ci -> concourse-ci.org

Thanks for contributing to pcf-pipelines. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:
This change replaces references to the concourse.ci domain with the active domain concourse-ci.org

An explanation of the use cases your change solves:

Expected result after the change:

Current result before the change:

Links to any other associated PRs or issues:

[ x ] I have viewed signed and have submitted the Contributor License Agreement

[ x ] I have made this pull request to the master branch

[ x ] I have run all the unit tests
Yes, i ran the tests but they were failing before i made the changes, and as far as i can tell they are the same errors

Thank you @jama-pivotal, scheduled for engineering review.


feature support percent_rank window function

Proposed changes
Issue Number: close #30636

support percent_rank window function for doris.


Fix log message

This makes a log message function better - it was using outdated logic to get the submission information, so this PR simply moves up where the submission is retrieved and uses the id from that instead.

@guiburato because you and I paired on this and all the tests are passing up here, you can go ahead and merge this.


README section about Pug linting

Tension
As a user I'd like to have a section with description of linter code with pug
Solution
Add the plugin

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Deprecate absolute lookups for relative ref/relref

Ref. the ongoing debate. @vassudanagunta
For:
relref "sect5/page3.md"

We will now look first relative to the page it lives in, but will fall back to "/sect5/page3.md", which is commonly used. We cannot just change that overnight. People will scream.
But we can do it in smaller steps.
So, I suggest we check for the pattern above and "asks the user politely" to correct it to relref "/sect5/page3.md"

Makes sense!


Broken pipe when using | tee

I've been running a process into a | tee logfile; sending SIGINT will close everything down, but log4rs prints a bunch of this to stdout at that point:
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)

This is on macOS and a few months old version of log4rs; haven't tested a newer version or different OS.

I don't think log4rs is doing anything particularly interesting here. I'm guessing that SIGINTing the process group will sometimes kill the tee first so stdout breaks. The error logging goes to stderr which presumably wasn't redirected. I've been meaning to make the error logging configurable but haven't gotten around to it.

Are there any actions to take here?

Hey sorry for not getting back to you. I guess if this is how things usually work, then there's no action needed. My application actually does a graceful shutdown on SIGINT so it's probably trying to log after the pipe is closed.

No problem! I filed #32 to track the meta-logger stuff.


Upgrade default tool version of CodeNarc to 1.2.1

Resolves #6623.

Green Branch Build Accept (before rebase): https://builds.gradle.org/viewLog.html?buildId=15494377&buildTypeId=Gradle_Check_Stage_BranchBuildAccept_Trigger


FPS Issues when running huestacean - Lock 60fps on 90 hz monitor

I've been enjoying huestacean while gaming, but noticed an issue specifically on Rocket League PC - my monitor refresh rate is 90 (monitor 1, where the app is visualizing), but in game everything is locked to 60 and suffers what feels like judder/stutter. After exiting huestacean, the game runs at 90 locked. Tried this a few times.
As an additional side note, I noticed Far Cry 5 froze a couple of times today when also running the 2.6 update, but did not have issues running at a locked lower than monitor refresh rate.

Any more information to go off? OS, video card, driver? G-SYNC or Freesync enabled?
I've got Rocket League open right now and it's steady above 162 FPS and not stuttering, with or without G-SYNC.

Sorry-
Windows 10, latest public update available
i5 6600k / 16gb 3200 ddr4, 1080ti on 391.35
Main monitor - Predator x34 @ 90hz, Gsync on, 2nd one @ 60hz
RL capped at 88fps
I did have twitch running in monitor two - it's still chopping up a bit but not locked this time, but definitely impacting it a bit. Closed twitch in chrome and its much steadier, not pinning it at 88 though.


syslinux: Use Nixpkgs' gnu-efi

Description of changes
#316878 aimed to change how gnu-efi was fetched. My understanding (after futzing about) is that sourceforge's git endpoint now doesn't provide direct commit access.
Instead of awkwardly fetching an older gnu-efi, prefer using Nixpkgs' gnu-efi.
Note that within Nixpkgs only the "legacy bios" syslinux is used. We could also drop the EFI build instead.
Closes #316878.
Things done
 $ nix-build -A syslinux -A pkgsi686Linux.syslinux

Ran the .efi output, from before the change, and after. Same result.

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Looks great to me, I can't really judge how risky it is to use a different version of gnu-efi than is referenced by the syslinux submodule...

The main risk would be that it stops building with it due to backwards-incompatible changes.
Technically the added patch works around a backwards-incompatible change, but barely so. (A feature was split off out into its own header.)
If it causes issues down the line, I believe it should be fine to disable building the EFI outputs entirely. Anyways they are not used within Nixpkgs nor NixOS. To do so would be relatively simple, removing the references to gnu-efi, and then removing the EFI targets.
I actually hesitated and almost went with just removing the EFI outputs.

Somehow, and I genuinely have no idea how, this breaks the ISO boot: https://cache.nixos.org/log/z24ffw9730kzaaljzy18g67jjnn2ix9h-vm-test-run-boot-bios-cdrom.drv

oof, thanks for the quick revert :/

created #317158


[enhancement]: Direct install of models from civitai.com

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
The "install from a Huggingface repo" feature is awesome.  I'd love to have a similar flow for "install from a civitai.com URL", especially if it automatically converts the model into the diffusers format after downloading.
Alternatives
Download the model, manually tell Invoke about it, tell it to convert to diffusers, remove the downloaded model.  So, not the worst, but also not the simplest user experience.
Aditional Content
No response

On civitai, right click the download button and copy link, then you can paste that after !import_model

@xaroth8088 - Thanks for the suggestion. Civit.ai does not currently support diffusers, which will be our default model format. If they elect to introduce that support, and also position themselves away from the current "NSFW Hub", we could definitely consider it though. Closing for now!

@xaroth8088 - Thanks for the suggestion. Civit.ai does not currently support diffusers, which will be our default model format. If they elect to introduce that support, and also position themselves away from the current "NSFW Hub", we could definitely consider it though. Closing for now!

Hmmm.. NSFW models can be installed anyway. if any model you want for the most part can't be installed then no one will use the app. It seems manually import works fine for the most part. I don't see how adding a api key and link option makes the app suddenly NSFW. ideally an app should be for how people see fit to use it. well the good ones. as much freedom as possible. but I can also understand why they dont want to associate with the insane level of porn on civiatai and hentai.
Oh well. cool app anyway. but if it goes paid and they implement some soft of block for civtai models that would kill it. Better to just have a baked SFW filter and let tinkerers who want to unlock, unlock it.

@xaroth8088 - Thanks for the suggestion. Civit.ai does not currently support diffusers, which will be our default model format. If they elect to introduce that support, and also position themselves away from the current "NSFW Hub", we could definitely consider it though. Closing for now!

Hmmm.. NSFW models can be installed anyway. if any model you want for the most part can't be installed then no one will use the app. It seems manually import works fine for the most part. I don't see how adding a api key and link option makes the app suddenly NSFW. ideally an app should be for how people see fit to use it. well the good ones. as much freedom as possible. but I can also understand why they dont want to associate with the insane level of porn on civiatai and hentai.
Oh well. cool app anyway. but if it goes paid and they implement some soft of block for civtai models that would kill it. Better to just have a baked SFW filter and let tinkerers who want to unlock, unlock it.

You’re commenting on a nearly two year old thread. You can manually add API keys through your config - long solved.


[Problem] Installation

Hi, this looks promising in, but I'm having trouble getting it working. Django 1.8.18, Python 2.7, Bootstrap 3.3.7, django-bootstrap3 9.0
Here's the html generated, but the date button does nothing.
<!DOCTYPE html>

    <meta charset="utf-8">

    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>is this loading?
    Multidate Picker Demo
</title>
    <link href="//maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet"><link href="https://bootswatch.com/lumen/bootstrap.css" rel="stylesheet">

<link href="/static/django_bootstrap3_multidatepicker/bootstrap-datepicker3.standalone.min.css" type="text/css" media="all" rel="stylesheet" />

Multidate Picker Demo

<form class="form" method="POST">
  <input type='hidden' name='csrfmiddlewaretoken' value='j7KfDYNNHmUrNFUYALSpFTQ8kQxjBXwL' />

<input class="form-control" id="id_dates" maxlength="1024" name="dates" type="hidden"></input>

  <button class="btn btn-primary" type="submit"> Save</button>
</form>

Currently selected Dates

Hi sorry I was on vacation, do you still have a problem with it? Then I could look into it!

Hi, I finally got it, I was missing the css.  I do have a related question.  How do I initialize the calendar?  I want to set addDisabledDates.

I got this as well.  :)  I needed to add it to the fields.py widget call:
   widget = BootstrapDatepickerInput(             options={                 "format": "yyyy-mm-dd",                 "startDate": "Today",                 "todayHighlight": "True",                 "title": "Booking Availability",                 "datesDisabled": ["2017-10-18","2017-10-14","2017-10-21"]             }         )

Exactly, options should be used to change the calendar, all options should be listed here by the way (if anyone wants to know).

@FabianWe Hi, This is nice and easy to use (once I figured everything out :)...
Another question, if you don't mind.
I have 2 related models:
class Product(models.Model):
    product = models.ForeignKey('catalogue.Product')
    desc = models.charfield()

class ProductBooking(models.Model):
    product = models.ForeignKey('catalogue.Product')
    booking_date = models.DateField()

and I want to display them as a list:   desc, booking_date, but I want the booking date field to display the calendar.  Is this possible?

@FabianWe   One more question...this has the methods to disable dates, but not add dates.  So how can I initialize the calendar with the already selected dates?

Ok, I found the setDate method, but I can't get it to work :(  It doesn't work if I treat it as an option.  Any help?


Error: Execution failed for task ':library:generatePublicXml'. > A problem occurred starting process 'command 'bash''

After downloading the source and put it into Android studio i got that error.
Event Log:
13:09:40 Executing tasks: [:library:generateDebugSources, :library:generateDebugAndroidTestSources, :library:mockableAndroidJar, :library:prepareDebugUnitTestDependencies, :sample:generateDebugSources, :sample:mockableAndroidJar, :sample:prepareDebugUnitTestDependencies, :sample:generateDebugAndroidTestSources]
13:09:52 Gradle build finished with 1 error(s) in 14s 87ms
// Thank you

Oops, are you on Windows? I guess ignoreExitValue doesn't apply if the executable can't be found.

The latest commit on the dev branch should fix this, do a pull and Gradle sync, then try building again.

Thank you 😊


Changed ls -al to the more common ls -la

While they're technically the same, ls -la is more common and hence more useful as an example, IMO.

Thanks