Fixed outdated tech redirect link.

@snazzysam933 spotless check failed on your change. I can't push to your branch to fix it. please run spotlessApply and update

@snazzysam933 DCO check is now failing - you need to add signoff to your commits

ok one more check is failing - because this class is part of the plugin-api
FAILURE: Build failed with an exception.

Where:
Build file '/home/runner/work/besu/besu/plugin-api/build.gradle' line: 59

What went wrong:
Execution failed for task ':plugin-api:checkAPIChanges'.

For the Plugin APIs the checksum of the project did not match what was expected.

If this is a deliberate change where you have thought through backwards compatibility,
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.8/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
24 actionable tasks: 24 executed
then update "Expected" for "Calculated" in the appropriate build.gradle as the knownHash for this task.
Expected   : Q6EK5By3BNKNa/JYqYjFw43VXWL0KVBUV3dGEQBjZ70=
Calculated : yH50m+z1tnzshJQPdwR86pb2EU3m6iZxwkqoy/5spcs=


[otbn] RSA signature verification for 3072-bit keys

This forks the RSA signature verification algorithm to create a dedicated variant for 3072-bit sized keys and the F4 (65537) exponent.
This implements #6566

@alphan, @cfrantz This now exposes the symbols for all buffers w/o using the index table as we discussed.

@imphil in case you're reviewing this, it makes sense to look mostly on the 2nd commit only, since the 1st is a copy of existing code

I now updated this PR to address the remaining review nits and will merge once CI passes.


No XP

I sign in with Facebook, deploy the bot, and then I don't get xp, which is the only reason I would use this bot.
Don't get me wrong, I LOVE this bot...
...but no xp and the random huge cells kind of ruin it for me.

Refer to what I said in issue #537.


Fixes issue #315 (MatAutocomplete's clear-button submits forms)

Changes the type of the MatIconButton to be "button" instead of "submit" (default) to avoid accidental submits of EditForms. This is done by changing the "type" of the MatIconButton on the MatAutocomplete component.

Hi!
Can you redo this change on the newer version using MatAutocompleteList?
Thank you!

It seems this change is also in https://github.com/SamProf/MatBlazor/pull/325

Thanks for the PR, this is now resolved in the latest develop branch.


GGIR only supports one type of file path on Windows

Describe the bug
I'm just running a couple of files to test #567 and noticed an issue with file paths.
On Windows, both C:/Users/user/folder and C:\\Users\\user\\folder are valid file paths. While the former is definitely clearer, the latter is easier if you need to copy a long folder path into R (you can copy from file explorer and use readClipboard() to get an escaped filepath). The problem is that some parts of GGIR assume that folders are always separated by /, and this causes issues. E.g., https://github.com/wadpac/GGIR/blob/536ffafee772440638fd14aee70b3f493441a65c/R/GGIR.R#L74-L75
To Reproduce
Here's an example of the problem, using that line above as an example:
# This works as expected
datadir <- "C:/Users/taren/Desktop/gene_files"
outputdir <- "C:/Users/taren/Desktop/outdir"
outputfoldername = unlist(strsplit(datadir, "/"))[length(unlist(strsplit(datadir, "/")))]
metadatadir = paste0(outputdir, "/output_", outputfoldername)
outputfoldername
#> [1] "gene_files"
metadatadir
#> [1] "C:/Users/taren/Desktop/outdir/output_gene_files"
# But could also just be replaced by:
basename(datadir)
#> [1] "gene_files"
file.path(outputdir, "output_", basename(datadir))
#> [1] "C:/Users/taren/Desktop/outdir/output_/gene_files"

# This file path is valid, but fails in GGIR
datadir <- "C:\\Users\\taren\\Desktop\\gene_files"
outputdir <- "C:\\Users\\taren\\Desktop\\gene_files"
outputfoldername = unlist(strsplit(datadir, "/"))[length(unlist(strsplit(datadir, "/")))]
metadatadir = paste0(outputdir, "/output_", outputfoldername)
outputfoldername
#> [1] "C:\\Users\\taren\\Desktop\\gene_files"
# metadatadir is not a valid file path
metadatadir
#> [1] "C:\\Users\\taren\\Desktop\\gene_files/output_C:\\Users\\taren\\Desktop\\gene_files"
# The builtin can already handle this format.
basename(datadir)
#> [1] "gene_files"
# And can make a valid file path
file.path(outputdir, "output_", basename(datadir))
#> [1] "C:\\Users\\taren\\Desktop\\gene_files/output_/gene_files"

Created on 2022-05-26 by the reprex package (v2.0.1)
You might not want to fix this, but maybe it should be noted in the vignette?
Before submitting

[x] Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
[x] Have you tried this on the latest master branch from GitHub?

Thanks Taren and sorry for the slow reply. I am now in the process of facilitating this.
User will be able to use \\ and GGIR internally converts this to / in order not to upset all downstream code that assumes /.


Windows 10 Mobile

Should the Windows 10 Mobile and Windows 10 Mobile Enterprise editions be removed from the table at the beginning of this page showing the available servicing channels for each Windows 10 edition as these editions are now out of support?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f5400f8b-2ed0-7960-4e3d-2f3444be7e6b
Version Independent ID: 81bd37f4-301b-b5ab-cda2-972a72a31ae7
Content: Assign devices to servicing channels for Windows 10 updates (Windows 10) - Windows Deployment
Content Source: windows/deployment/update/waas-servicing-channels-windows-10-updates.md
Product: w10
Technology: windows
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

Partially related to the following ticket:

Add note to show this page is about a product that has reached EOS #6672

Yep; we're working on a massive overhaul of all these articles this month.

@jaimeo Shall we suspend assignment to this issue?

The issue is going to be addressed at #6672 (via https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6672#issuecomment-707224731)

The issue is going to be addressed at #6672 (via https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6672#issuecomment-707224731)


Generated typescript migrations and seeds have type errors

Environment
Knex version: 0.15.2
Bug

Explain what kind of behaviour you are getting and how you think it should do

Getting type errors, shouldn't have any.

Error message

Type 'Bluebird<any>' is not assignable to type 'Promise<any>'.
  Property '[Symbol.toStringTag]' is missing in type 'Bluebird<any>'.

This is because the bluebird promise type is incompatible with the typescript Promise type. This can fixed by simply wrapping the function body in Promise.resolve(...) and returning that instead.
Example (seed file, needs to be fixed with migration as well)
Current generated code
import * as Knex from "knex";

exports.seed = function (knex: Knex): Promise<any> {
    // Deletes ALL existing entries
    return knex("table_name").del()
        .then(function () {
            // Inserts seed entries
            return knex("table_name").insert([
                { id: 1, colName: "rowValue1" },
                { id: 2, colName: "rowValue2" },
                { id: 3, colName: "rowValue3" }
            ]);
        });
};

Code that typechecks correctly by adding Promise.resolve(...)
import * as Knex from "knex";

exports.seed = function(knex: Knex): Promise<any> {
  // Deletes ALL existing entries
  return Promise.resolve( // <-- added line
    knex("table_name")
      .del()
      .then(function() {
        // Inserts seed entries
        return knex("table_name").insert([
          { id: 1, colName: "rowValue1" },
          { id: 2, colName: "rowValue2" },
          { id: 3, colName: "rowValue3" }
        ]);
      })
  );
};

Wouldnt it be better to declare function as async?
exports.seed = async function(knex: Knex): Promise<any> {
  //...
};

Yes that's what I started doing shortly after filing the issue, should have updated it.

Could also use PromiseLike
ie
import * as Knex from "knex";

exports.seed = function (knex: Knex): PromiseLike<any> {
    // Deletes ALL existing entries
    return knex("table_name").del()
        .then(function () {
            // Inserts seed entries
            return knex("table_name").insert([
                { id: 1, colName: "rowValue1" },
                { id: 2, colName: "rowValue2" },
                { id: 3, colName: "rowValue3" }
            ]);
        });
};

Fixed https://github.com/tgriesser/knex/pull/2816

(function (exports, require, module, __filename, __dirname) { import ...
getting error - on import statement.


Install local react-native package in e2e

Summary

Following 6df2edeb2a33d529e4b13a5b6767f300d08aeb0a, the template for a new app no longer refers to a specific version of React Native, as the React Native CLI will set the correct version when react-native init is run. As it happens, the CLI cannot find a local react-native@1000 version when run as part of the JavaScript e2e tests. Therefore, I am working around using the CLI directly, and instead we're copying the contents of template/ into a temporary directory for e2e tests. This is not dissimilar to what we already test internally at Facebook.
Changelog

[General] [Fixed] - Fixed JavaScript e2e tests
Test Plan
Local:
node ./scripts/run-ci-e2e-tests.js --js --retries 3 --skip-cli-install
echo $?
0

Circle CI: ✅ test_javascript

The fix in this PR is not specific to JS e2e but rather any test that uses the run-ci-e2e-tests.js file. I just noticed that test_ios has been broken for the same reason<EMAIL_ADDRESS>does not exist on npm), but this PR surfaces another failure further down the line when test_ios runs its e2e tests.
It looks like it's related to the renaming of the test app performed in this PR, so I'll make sure to fix that before landing this PR. Please do not merge until then.

test_ios is legit broken due to 094f221a0c2d24f16a9540e4f176783843ec4fd9 having moved jsi around. Landing, with the intent to fix forward later.


engineering: add tests infra

[x] unit test with https://github.com/MrPowers/chispa
[x] function test, integration test with docker-compose
[x] linter on build and PR
[ ] tox for multiple py versions

closing it as completed, decided to not use tox.


Cancel snippet expansion

Is there a way to cancel the snippet expansion ?
Use cases:

I have an automatic snippet that is correctly triggered in 99% of cases but sometimes I just want to cancel the expansion.
I triggered snippet expansion by accident using my mapping and want to cancel it and retrieve the trigger text.

Just found https://github.com/L3MON4D3/LuaSnip/issues/797 FR which seem to be the same request.


before writing tests

a few things:

added a docs folder. let's see how much we like this.
refactored the tests a bit.
added a first model for sklearn. needs usage to figure out if we really like this.


Fix docFreq in score calculation after rewrite of boolean query consisting of blended query and boosted term query

Description
When there is a boolean query consisting of a fuzzy query and a boosted term query during rewrite:

fuzzy query is replaced by BlendedTermQuery with a series of term queries with a matching edit distance
BlendedTermQuery is replaced by a series of boosted term queries with a non-null termStates that have one common docFreq value that is false for some terms (see BlendedTermQuery::adjustFrequencies).
Because TermQuery::equals implementation was not taking into account termStates, both the generated term query with non-null termStates and original boosted term query were merged together. Resulting TermQuery termStates depended on hash code that is based on Solr startup time (can be changed using tests.seed property). Because of that similarities that use docFreq can return wrong score.

This PR changes equals and hashCode implementation in TermQuery so one generated from fuzzy query and original one are not merged together anymore. Also added a test making sure it works as intended. Test was failing for tests.seed=1.
Fixes #10309

Thank you @rafalh!  Query scores depending on HashMap iteration order is really awful.  And thank you @stefanvodita for reviewing.  @rafalh do you want to fold in the feedback maybe?  Thanks!


 One of them found an old grave of his, but instead of breaking, his inventory got entirely deleted and the grave refused to break. I put grave robbing on to see if this could help, but it only made it so that it also deleted my inventory???
forgottengraves-mc1.18.2-v2.5.0.jar

Found this in the log multiple times:
[14:05:46] [Server thread/ERROR]: Failed to handle packet net.minecraft.class_2885@57339178, suppressing error
java.lang.IndexOutOfBoundsException: toIndex = 53
at Not Enough Crashes deobfuscated stack trace.(1.18.2+build.2) ~[?:?]
at java.util.AbstractList.subListRangeCheck(AbstractList.java:507) ~[?:?]
at java.util.AbstractList.subList(AbstractList.java:497) ~[?:?]
at me.mgin.graves.block.GraveBase.useGrave(GraveBase.java:258) ~[forgottengraves-mc1.18.2-v2.5.0.jar:?]
at me.mgin.graves.block.GraveBase.onUse(GraveBase.java:107) ~[forgottengraves-mc1.18.2-v2.5.0.jar:?]
at net.minecraft.block.AbstractBlock$AbstractBlockState.onUse(AbstractBlock:939) ~[?:?]
at net.minecraft.server.network.ServerPlayerInteractionManager.interactBlock(ServerPlayerInteractionManager:336) ~[?:?]
at net.minecraft.server.network.ServerPlayNetworkHandler.onPlayerInteractBlock(ServerPlayNetworkHandler:1081) ~[?:?]
at net.minecraft.network.packet.c2s.play.PlayerInteractBlockC2SPacket.apply(PlayerInteractBlockC2SPacket:30) ~[?:?]
at net.minecraft.network.packet.c2s.play.PlayerInteractBlockC2SPacket.apply(PlayerInteractBlockC2SPacket:8) ~[?:?]
at net.minecraft.network.NetworkThreadUtils.method_11072(NetworkThreadUtils:22) ~[?:?]
at net.minecraft.server.ServerTask.run(ServerTask:18) ~[?:?]
at net.minecraft.util.thread.ThreadExecutor.executeTask(ThreadExecutor:157) ~[?:?]
at net.minecraft.util.thread.ReentrantThreadExecutor.executeTask(ReentrantThreadExecutor:23) ~[?:?]
at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:808) ~[client-intermediary.jar:?]
at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:165) ~[client-intermediary.jar:?]
at net.minecraft.util.thread.ThreadExecutor.runTask(ThreadExecutor:131) ~[?:?]
at net.minecraft.server.MinecraftServer.runOneTask(MinecraftServer:790) ~[client-intermediary.jar:?]
at net.minecraft.server.MinecraftServer.runTask(MinecraftServer:784) ~[client-intermediary.jar:?]
at net.minecraft.util.thread.ThreadExecutor.runTasks(ThreadExecutor:140) ~[?:?]
at net.minecraft.server.MinecraftServer.runTasksTillTickEnd(MinecraftServer:769) ~[client-intermediary.jar:?]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer:701) ~[client-intermediary.jar:?]
at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer:273) ~[client-intermediary.jar:?]
at java.lang.Thread.run(Thread.java:833) [?:?]

Hey there, that sounds like a nasty one.
I'm going to do some testing & mess around with the code and see if I can't resolve the issue. I believe it has to do with adding or removing a mod that adds extra slots after the particular grave has been placed.
Thanks for the report!

Hey there, just an update: I've fixed the bug but I'm just doing some code clean up, working on resolving #40, etc.. but the fix should be released in the next couple days. Thanks again for the report!

Thank u so much! Final questions: will my friend get the "deleted" items back from the grave or are they lost forever?

They should be able to retrieve the items that were already in the grave originally. Unfortunately, the items they had whilst trying to retrieve the grave are lost.

Hello! Did a new issue come up or have ya just been busy? The new version wasn't released in "the next couple of days" so that's why wondering lol :3 I hope this doesn't come off as rude...all the respect in the world for you!

Howdy, I've been pretty busy at work lately so I haven't had the time to release it. That and I wanted to finish #40 before releasing (which more or less is now finished since last night).
I'm gonna go ahead and do my standard testing & then release it before I head to bed.

Released a 1.18.1 and 1.18.2 version that should fix this -- let me know if you have any other issues, thanks!


Support blink.cmp

Blink.cmp is a new completion engine that's meant to be very fast.
While it's only been around for just under 2 months at time of writing, it's already proving to be quite popular.
I'd gladly submit a PR if I can find the time to do so and you'd be willing to accept one for it.

@RVxLab go for it


Make website compatible with a "reader view"

Summary
It would be useful for users of AutSPACEs to be able to view stories in a reader view to eliminate distractions and make it more comfortable and easier to focus. Currently there is no reader view compatibility. This is important for accessibility as it helps people with sensory overwhelm.
What needs to be done?

[ ] Adapt "view stories" so that they can be put into a reader view and clicked through without having to close the reader view.

I've started to look into this a bit and it seems that at least some of our pages are already compatible with the reader view as implemented in Safari & Firefox:
For example, on all the "about", "help" etc pages the reader view is being offered. Similarly, the "single story" view offers the reader view as well. Our front page is a bit more tricky, Safari will show the reader view option, but only with very limited details, while Firefox doesn't offer it at all.
Also, the "view all stories" page does not offer the reader view, probably due to the collapse etc. nature of the page.
This SO answer provides some details on how to improve the reader view rendering (which in turn might also imrpove accessibility by screen readers).

Okay, I looked into this more and it seems like it won't be as easy to adapt as I had hoped: The collapsing "cards" for each story mean that the content is nested in a way that makes it inaccessible/invisible to the 'readability' libraries that browsers ship with.
This means we'd have to rewrite this whole page from scratch – to make the default a list of expanded text and then use JS magic to make it hidden (which is basically the opposite of how it works now).
Given this I'd say for now we put this one into the backburner and instead give the RSS feeds a try, which allows people to subscribe to the content to to have it displayed in the way they prefer in their clients?

RSS feeds were implemented in #654


Support plaintext .sdb files

Identify when the .sdb file is k=v in plaintext instead of a disk hashtable in cdb format
This format should be defined somehow in the Sdb instance and saved in the same format when dumping.

Requirements for the text format:

Correctly handle (escape) all valid strings as keys and values, including '=', '\n', '\', etc.
Support namespaces somehow

Here is my proposal for a concrete format (# stuff are just comments for explaining but should maybe not be part of the format):
some_key=some_val                             # a record in the root namespace
something\nwith\nnewlines=val\nwith\nnewlines # newlines separate different records, so must be escaped
key\=with\=equals=val=with\=quals             # = must be escaped in the key, but in the value it's optional
key\\with\\backslash=val\\with\\backslash

# completely empty lines are ignored

/subns                                        # lines beginning with '/' and no '=' enter a new namespace (path is always absolute to the root)
key_in_subns=val_in_subns

/subns/deeper                                 # deeper nesting (again, path is absolute)
deepest_key=deepest_val

/weird\=ns\\\nwtf                             # namespace names use the same escaping as keys ...
\/justa_key=henlo                             # except that keys must always escape the first char if it is a slash


Improve Coprocessor Table Lookup Performance

What have you changed?
Introduce incremental_get interface at MVCC level, which will reuse the cursor when keys are given in ascending order. This can roughly improve about 30% overall table lookup performance.
Integration Benchmark
Before:
explain analyze select * from sbtest1 where k >= 50000 and k <= 51000
--------------

+-------------------+----------+-----------+---------------------------------------------------------------+-------------------------------------------------------------------------------+----------------------+
| id                | count    | task      | operator info                                                 | execution info                                                                | memory               |
+-------------------+----------+-----------+---------------------------------------------------------------+-------------------------------------------------------------------------------+----------------------+
| IndexLookUp_10    | 51293.64 | root      |                                                               | time:298.378704ms, loops:52, rows:51243, rpc time:61.261896ms                 | 7.823173522949219 MB |
| ├─IndexScan_8     | 51293.64 | cop[tikv] | table:sbtest1, index:k, range:[50000,51000], keep order:false | time:59ms, loops:55, rows:51243                                               | N/A                  |
| └─TableScan_9     | 51293.64 | cop[tikv] | table:sbtest1, keep order:false                               | proc max:150ms, min:30ms, p80:129ms, p95:150ms, rows:51243, iters:80, tasks:6 | N/A                  |
+-------------------+----------+-----------+---------------------------------------------------------------+-------------------------------------------------------------------------------+----------------------+

After:
explain analyze select * from sbtest1 where k >= 50000 and k <= 51000
--------------

+-------------------+----------+-----------+---------------------------------------------------------------+----------------------------------------------------------------------------+----------------------+
| id                | count    | task      | operator info                                                 | execution info                                                             | memory               |
+-------------------+----------+-----------+---------------------------------------------------------------+----------------------------------------------------------------------------+----------------------+
| IndexLookUp_10    | 51253.31 | root      |                                                               | time:204.635371ms, loops:52, rows:51243, rpc time:51.750645ms              | 7.823173522949219 MB |
| ├─IndexScan_8     | 51253.31 | cop[tikv] | table:sbtest1, index:k, range:[50000,51000], keep order:false | time:48ms, loops:55, rows:51243                                            | N/A                  |
| └─TableScan_9     | 51253.31 | cop[tikv] | table:sbtest1, keep order:false                               | proc max:84ms, min:14ms, p80:75ms, p95:84ms, rows:51243, iters:80, tasks:6 | N/A                  |
+-------------------+----------+-----------+---------------------------------------------------------------+----------------------------------------------------------------------------+----------------------+

Micro Benchmark
When get keys are not close to each other, there are roughly 64% improvement. When get keys are close to each other (so that point getter use next() instead of seek()), it becomes 176% improvement.
Get Key interval = 30

test storage::incremental_get::bench_table_lookup_mvcc_get             ... bench:   9,263,060 ns/iter (+/- 896,597)
test storage::incremental_get::bench_table_lookup_mvcc_incremental_get ... bench:   5,671,531 ns/iter (+/- 573,971)

Get Key interval = 1

test storage::incremental_get::bench_table_lookup_mvcc_get             ... bench:   9,111,466 ns/iter (+/- 849,512)
test storage::incremental_get::bench_table_lookup_mvcc_incremental_get ... bench:   3,301,115 ns/iter (+/- 249,179)

What is the type of the changes?

Improvement (a change which is an improvement to an existing feature)

good catch

Better to have micro-bench.

how about other cases? like select count(*) from sbtest1?
I also notice that we use N/A for the memory in Cop task, can we support it later?
@breeswish

/bench

@siddontang select count(*) from sbtest1 doesn't use point get. This PR only optimize the table look up case. We may support the memory usage statistics after all data types are migrated to continuous memory.

/run-all-test

/test

/run-all-tests

/bench +tpcc +sysbench

/bench +tpcc +sysbench

/bench +tpcc +sysbench

/test

/test

/run-all-tests

/run-all-tests

/merge


[BUG] - Font color in Bordered select is always gray

NextUI Version
2.4.6
Describe the bug
Just came to NextUI for a few days. I have a bordered select. I found out the font color is always gray no matter what color props

As you can see, it's still gray even I set the color="primary". It makes the font color inconsistent since the font color in Input is black while the font color in Select is gray
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
<Select
  name="role_id"
  label="Job Role"
  labelPlacement="outside"
  startContent={
      <UserCircleIcon className="w-4 h-4 text-default-400 pointer-events-none" />
  }
  variant="bordered"
  color='primary'
  placeholder="Select your role"
  onChange={(e) => setData('role_id', e.target.value)}
>
  {roles.map(role => (
      <SelectItem key={role}>
          {role}
      </SelectItem>
  ))}
</Select>

Expected behavior
The color should be consistent or is there any way to change the color in Select?
Screenshots or Videos
No response
Operating System Version
Mac
Browser
Chrome

Hi,
The color=primary will apply only to the label not the selected value and selectable values list in popover.
You can add the class: classNames: {       "listboxWrapper": "text-primary",       "value": "text-primary" }
Adding the above class might help you get:

@wingkwong Will it be helpful to add an variant for this?

Hi, The color=primary will apply only to the label not the selected value and selectable values list in popover.
You can add the class: classNames: { "popoverContent": "text-primary", "value": "text-primary" } Here, the styling in value applies to the selected value and styling in popoverContent is applied to selectable values.

Adding the above class might help you get:

If you like to have custom color for the selected value, you can add the  classNames: { "popoverContent": "text-primary", "value": "text-[#99C7FB]" } class

Hi
Thank you for your solution.
It changed the color of selected value as expected. But the cons is that the color of placeholder gets changed as well.
Because the placeholder is not a real placeholder prop in an input, but a span.  So I have to do like this: classNames= {{ "value": data ? "text-black" : "text-gray-500" }} as my temporary solution.
But personally, I can't get the point of design in this way. If the Select has no border, the selected value color is the same as other components. Why the selected value will be changed when Select is bordered, making the color inconsistent with other components?

@Rain-YuXia
You can add this {"value: "group-data-[has-value=true]:text-default-foreground"} to avoid using the conditional. This will show text as gray when placeholder is shown and black when some value is selected.

when placeholder

when value is selected

@macci001
working perfectly. Thanks
Is it an undocumented hidden feature? I can't find it anywhere in the documentation.

@macci001 working perfectly. Thanks
Is it an undocumented hidden feature? I can't find it anywhere in the documentation.

This is just a hack until this big is fixed.


Train sentiment analysis in Web Worker

The sentiment analysis is a bit slow. Perhaps using a Web Worker would allow me to offload it to a different "thread"?

The problem is now that I can't get it to run only once. Instead, it keeps loading the model over and over until it gets rate limited 🤦♂

This was a good idea in principle, but it doesn't work.
I've added some UX improvements (i.e. just letting the user know that the email is being sent).


Feature - scroll offset threshold

Only toggle visibility after some scroll offset threshold.

What was the state of this PR. Do I remember there being some doubts or bugs in it?

Yeah not the best pr. Closing for now.


Week 5 - Scheduling a Meeting TDD

Implement the basic function of a meeting scheduler
Pass all tests provided.

Here is the screenshot showing my code passes the test:


wsl: actually close the pipe handle for wsl.exe, but only one time

We were eating an exception on exit in debug mode because we were using
wil to clean up half of a named pipe we'd already handed ownership of
over to the CRT. The CRT likes to tie up all its loose ends when it gets
unloaded, so it was coming along at exit and closing the handle again.
Big no-no.

Also, this means we were leaking pipe handles every time the settings reloaded.


Not compatible with @prisma/nuxt

Environment
Nuxt project info:                                                                                7:51:21 AM

Operating System: Linux
Node Version:     v20.14.0
Nuxt Version:     3.12.2
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, runtimeConfig, modules, shadcn, auth, pinia
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
npx nuxi@latest init test-nuxt-app
cd test-nuxt-app
npx nuxi@latest module add @prisma/nuxt

npx nuxi@latest module add @sidebase/nuxt-auth

now npm run dev fails
Describe the bug
RollupError<EMAIL_ADDRESS>(2:8): Expected ';', '}' or  (Note that you need plugins to import files that are not JavaScript)
1: import { PrismaClient } from "@prisma/client";
2: declare const prismaClientSingleton: () => PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never, i...
^
3: declare const prisma: PrismaClient<import(".prisma/client").Prisma.PrismaClientOptions, never<EMAIL_ADDRESS>4: export type CustomPrismaClient = ReturnType;
Additional context
No response
Logs
No response

Hi @ankur198 👋
Why do you belive this is an issue with @sidebase/nuxt-auth? Have you checked with the team behind @prisma/nuxt where this error may be coming from?
As a quick workaround for this issue, you could install Prisma without the Nuxt module as we also do in create-sidebase (npm create sidebase@latest):
pnpm i -D prisma
pnpm i @prisma/client

// file: ~/server/middleware/0.prisma.ts

import { PrismaClient } from '@prisma/client'

let prisma: PrismaClient

declare module 'h3' {
  interface H3EventContext {
    prisma: PrismaClient
  }
}

export default eventHandler((event) => {
  if (!prisma) {
    prisma = new PrismaClient()
  }
  event.context.prisma = prisma
})

// file: ~/prisma/utils.ts
import { execSync } from 'node:child_process'

/**
 * Helper to reset the database via a programmatic prisma invocation. Helpful to add to \`beforeEach\` or \`beforeAll\` of your testing setup.
 *
 * WARNING: Never run this in production.
 *
 * Taken from https://github.com/prisma/prisma/issues/13549#issuecomment-1144883246
 *
 * @param databaseUrl Connection URL to database. Inferred from \`process.env.DATABASE_URL\` if not provided
 */
export function resetDatabase(databaseUrl?: string) {
  const url = databaseUrl || process.env.DATABASE_URL
  if (!url) {
    throw new Error('Cannot reset database - connection string could not be inferred.')
  }

  if (process.env.NODE_ENV === 'production') {
    throw new Error('This utility should not be called in production. It is meant for testing and development')
  }

  execSync(\`cd \${process.cwd()} && DATABASE_URL=\${url} npx prisma db push --force-reset\`, { stdio: 'inherit' })
}

Hi @zoey-kaiser ,
Thanks for responding and yes you are correct. I have seen @prisma/nuxt is not compatible with a lot of other libraries. My bad. Closing the issue.
Thanks for providing workaround though 🙂


u-boot-iot2050: flashing documentation update

The flashing documentation update with external flash programmers.
Add the image of the board's back side with flash chip's location.
Signed-off-by: Ivan Mikhaylov<EMAIL_ADDRESS>

I am not sure if that's a good idea to put this information here, I personally prefer to add it into the wiki and then link here.


scroll_started and scroll_ended signals don't get emitted for ScrollContainer on Windows but they do work on Android

Godot version
4.1.1.stable.official [bd6af8e0e]
System information
Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU (NVIDIA; <IP_ADDRESS>60) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 Threads)
Issue description
scroll_started and scroll_ended signals don't get emitted for ScrollContainer on Windows (haven't tested on linux or mac), but they do work on Android (haven't tested on iOS)
Steps to reproduce
You can connect scroll_started or scroll_ended signal of a ScrollContainer control to a function and you will notice that the callback is never called on windows, but when tested on android it works.
Minimal reproduction project
scroll_event_issue.zip

What ways are you scrolling? With the scroll wheel? Dragging with the mouse?

Tried scrolling with the scroll wheel, dragging the scrollbar with the mouse and also using the scrolling gesture (Two finger scroll) on the touchpad.

It only supports touch, as in screen touch, unsure if this is an oversight or by design though, if the latter it should be documented

You need to enable Emulate Touch From Mouse in the Project Settings for these signals to be emitted. These signals are only emitted for drag-based scrolling.

Note that this signal was originally added to solve a bug where buttons could be pressed while scrolling, so I'm unsure what use the signal has elsewhere


datastore: Projection KeyOnly-Query unable to select __key__ - property stay empty

Hello,
I try a really basic query, selecting the __key__ property - but it stays empty.
I searched the issues and stackoverflow, I also created a thread a SO, but it stays unanswered. I also created a ticket at the google cloud support, also no answer yet. Therefore I create this issue now.
Thread on stackoverflow:

https://stackoverflow.com/questions/44245132/property-key-is-empty-with-node

Environment details

OS: Linux (Ubuntu 16.04.1 LTS)
Node.js version: v7.3.0
npm version: 3.10.10
google-cloud-node version: 1.0.2

Steps to reproduce
const datastore = require('@google-cloud/datastore')({
  projectId: project,
  keyFilename: `key.json`
});

const query = datastore.createQuery("Projects").select('__key__');

datastore.runQuery(query, (err, entities, info) => {
  console.log('RESULTS:', {err, entities, info});
});

Result:
RESULTS: { err: null,
  entities: [ {}, {}, {}, {} ],
  info:
   { moreResults: 'NO_MORE_RESULTS',
     endCursor: 'CjwSNmoOZX5zYW0tcmVjb3JkZXJyJAsSHF9BRV9EYXRhc3RvcmVBZG1pbl9PcGVyYXRpb24YwYQ9DBgAIAA=' } }

Expected Result:
RESULTS: { err: null,
  entities: [
      {___key___:<PHONE_NUMBER>470976},
      {___key___:<PHONE_NUMBER>728832},
      {___key___:<PHONE_NUMBER>201216},
      {___key___:<PHONE_NUMBER>569216}
      ],
  info:
   { moreResults: 'NO_MORE_RESULTS',
     endCursor: 'CjwSNmoOZX5zYW0tcmVjb3JkZXJyJAsSHF9BRV9EYXRhc3RvcmVBZG1pbl9PcGVyYXRpb24YwYQ9DBgAIAA=' } }

The property __key__ stays empty and I dont know why. Selecting an other property works as expected.
It should work as it is described in the API Docs: https://cloud.google.com/datastore/docs/concepts/queries#projection_queries
Do I missing something?
Thanks!

ok, got an answer on SO - this seems to work:
datastore.runQuery(query, (err, entities, info) => {
  const keys = entities.map( entity => entity[datastore.KEY] );

  keys.forEach( key => {
    console.log(key.id);
  });

  console.log('RESULTS:', {err, entities, info, keys});
});


docs: Make it easier to find and install this plugin

When you enter "tasks" on plugins page this plugin is actually at the bottom making it hard to find...
With this link it will be easier to find and install this plugin.

Thanks @mpawelski - it's live now:
https://obsidian-tasks-group.github.io/obsidian-tasks/installation/


AdaptLLM models with Llama Index

Hello,
I am trying to use AdaptLLM/finance-LLM along with Retrieval-Augmented Generation (RAG) through Llama Index.
However, I am not able to make the template work. I have tried many things, the closest to a working solution being:
system_prompt = 'Please, check if the anwser can be inferred from the pieces of context provided. If the answer cannot be inferred from the context, just state that the question is out of scope and do not provide any answer.'

query_wrapper_prompt = PromptTemplate(
	'<s>[INST] <<SYS>>\n' + system_prompt + '\n<</SYS>>\n{query_str} [/INST]\n'
)

Every space a new line seems to be crucial. Any small difference changes everything.
With the proposed template sometimes the only output is [/INST] repeated a number of times.
Sometimes I obtain a consistent answer preceded by [/INST] but with multiple repetitions of the same couple of sentences.
Sometimes the output seems to describe the internal workings of Llama Index.
Other templates and formatting produce even worse results. For instance, in some cases the system prompt is ignored and the models answers on the basis of previous knowledge.
Has anyone managed to make this work?
Ed

Hi, thanks for your feedback🤗! The prompt template that uses system prompt and "[/INST]" is specifically designed for the chat model.
We highly recommend switching from 'AdaptLLM/finance-LLM' to 'AdaptLLM/finance-chat' for improved response quality.
Regarding your use-case, here's an example using the recommended 'finance-chat' model:
from transformers import AutoModelForCausalLM, AutoTokenizer

model = AutoModelForCausalLM.from_pretrained("AdaptLLM/finance-chat")
tokenizer = AutoTokenizer.from_pretrained("AdaptLLM/finance-chat", use_fast=False)

# Put your query here
query_str = 'xxx'

your_system_prompt = 'Please, check if the answer can be inferred from the pieces of context provided. If the answer cannot be inferred from the context, just state that the question is out of scope and do not provide any answer.'

# Please integrate 'your system prompt' into the input instruction part following 'our system prompt'.
query_prompt = f"<s>[INST] <<SYS>>\nYou are a helpful, respectful, and honest assistant. Always answer as helpfully as possible, while being safe. Your responses should not include any harmful, unethical, racist, sexist, toxic, dangerous, or illegal content. Please ensure that your responses are socially unbiased and positive in nature.\n\nIf a question does not make any sense or is not factually coherent, explain why instead of answering something not correct. If you don't know the answer to a question, please don't share false information.\n<</SYS>>\n\n{your_system_prompt}\n{query_str} [/INST]"

# NOTE: another option might be: skipping our system prompt and directly starting from your system prompt like this:
# query_prompt = f"{your_system_prompt}\n{query_str} [/INST]"

inputs = tokenizer(query_prompt, return_tensors="pt", add_special_tokens=False).input_ids.to(model.device)
outputs = model.generate(input_ids=inputs, max_length=4096)[0]

answer_start = int(inputs.shape[-1])
pred = tokenizer.decode(outputs[answer_start:], skip_special_tokens=True)

print(f'### User Query:\n{query_str}\n\n### Assistant Output:\n{pred}')

Feel free to let us know if you have any more questions🤗.

Hi,
I am trying 'AdaptLLM/finance-chat' as suggested and it seems to work fine.
However, the generation configuration does not seem to be taken into account.
First, with transformers 4.36.2, I receive the following warning twice:
/home/emoman/.local/lib/python3.11/site-packages/transformers/generation/configuration_utils.py:389: UserWarning: do_sampleis set toFalse. However, temperatureis set to0.9-- this flag is only used in sample-based generation modes. You should setdo_sample=Trueor unsettemperature. This was detected when initializing the generation config instance, which means the corresponding file may hold incorrect parameterization and should be fixed.
It seems that the generation kwargs from the script are completely ignored and that they are read directly from 'generation_config.json'.
So, if I alter that file to:
{
    "_from_model_config": true,
    "bos_token_id": 1,
    "eos_token_id": 2,
    "pad_token_id": 32000,
    "do_sample": true,
    "temperature": 0.0000001,
    "top_p": 0.0000001,
    "top_p": 1,
    "repetition_penalty": 0.1,
    "transformers_version": "4.31.0.dev0"
}

The warnings disappear, but the model keeps repeating itself, which would seem to indicate that 'repetition_penalty' is being ignored.
Some people suggest setting '_from_model_config' to false, but it does not change anything.

Hi, thanks for the feedback. I think we can resolve this warning by unsetting temperature and top_p.
Remove temperature and top_p from the generation_config.json file, making it look like this:
{
    "_from_model_config": true,
    "bos_token_id": 1,
    "eos_token_id": 2,
    "pad_token_id": 32000,
    "transformers_version": "4.31.0.dev0"
}

I've tested this with transformers version 4.36.2, and it works fine now.

Yes, thank you. It works.
But, generally speaking, I believe that the generation kwargs explicitly set on the script should override the default configuration file.
I would seem that, if they don't, it means that transformers has switched to some sort of legacy mode.
Finally, the model does respond to repetition_penalty and other generation parameters.
But it is extremely capricious and I haven't found a way to consistently avoid repetition other than post-processing.
It is a pity because the model seem very good for my purposes.
I believe that this volatility may be intrinsic to vanilla Llama-2 and it is not a consequence of the "reading comprehension" adaptation.
That being the case, perhaps the best solution would be to replace vanilla Lama with something better stabilised such as Mistral, for instance.  Tulu also shows a very steady behaviour.

Hi,
Thanks for your recommendation to switch our base models to Mistral and Tule. Mistral is indeed in our future plans.
Regarding this issue:
But, generally speaking, I believe that the generation kwargs explicitly set on the script should override the default configuration file

I completely agree that "generation kwargs explicitly set on the script should override the default configuration file".
But there might exist some conflicts in your config settings.
{
    "_from_model_config": true,
    "bos_token_id": 1,
    "eos_token_id": 2,
    "pad_token_id": 32000,
    "do_sample": true,
    "temperature": 0.0000001,
    "top_p": 0.0000001,
    "top_p": 1,
    "repetition_penalty": 0.1,
    "transformers_version": "4.31.0.dev0"
}

According to the official documentation: https://huggingface.co/docs/transformers/v4.36.1/en/main_classes/text_generation#generation
Firstly, setting the temperature to an extremely small value near 0 (0.0000001) creates a highly concentrated token distribution, behaving similarly to "do_sample"=false. This contradicts your setting of "do_sample": true.
Secondly, there are conflicting values for top_p in your configuration.
Then, the repetition_penalty value of 0.1 would make the problem even worse, and a value higher than 1 such as 1.2 is recommended to solve repetition.
The simplest setting for your config is like this, and you may refer to the official documentation for your specific usecase
{
    "_from_model_config": true,
    "bos_token_id": 1,
    "eos_token_id": 2,
    "pad_token_id": 32000,
    "repetition_penalty": 1.2,
    "transformers_version": "4.31.0.dev0"
}

Thanks for the advice, I will try that inmediately.
But that configuration has been tested with many models. I have also tried going with the defaults and many other combinations.


_InternalLinkedHashMap<dynamic, dynamic> is not a subtype of Map<String, dynamic>? in type cast

This is the error when I try to run client.query  with a GraphQLConsumer for onChanged event of a TextField
Unhandled Exception: type '_InternalLinkedHashMap<dynamic, dynamic>' is not a subtype of type 'Map<String, dynamic>?' in type cast

seems there is an issue during encoding/decoding the API result into the Hive box
(it's weird it was working as expected yesterday while I did not change the code and today it has issues)
Expected behavior
Get the result from client.query and update the view (using a Getx controller since Query was not working as expected)
device / execution context
Android simulator
The event function:
  void onInputChange(String value, GraphQLClient client, SearchController _) {
    if (value.isEmpty) {
      _.changeQuery("");
      return;
    }
    client
        .query(
      QueryOptions(document: gql(searchArtistQuery), variables: {
        'q': value,
      }),
    )
        .then((QueryResult result) {
      if (result.data == null) return;
      final artists = (result.data?['searchArtists'] ?? [])
          .map((artist) => Artist.fromJson(artist))
          .toList();
      if (artists.isEmpty) return;
      _.changeQuery(value);
      _.changeResult(artists);
    });
  }

Stacktrace:
E/flutter (23039): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: type '_InternalLinkedHashMap<dynamic, dynamic>' is not a subtype of type 'Map<String, dynamic>?' in type cast
E/flutter (23039): #0      BoxImpl.get
package:hive/…/box/box_impl.dart:44
E/flutter (23039): #1      HiveStore.get
package:graphql/…/cache/hive_store.dart:51
E/flutter (23039): #2      GraphQLCache.readNormalized
package:graphql/…/cache/cache.dart:114
E/flutter (23039): #3      NormalizingDataProxy.readQuery.<anonymous closure>
package:graphql/…/cache/_normalizing_data_proxy.dart:87
E/flutter (23039): #4      denormalizeOperation
package:normalize/src/denormalize_operation.dart:63
E/flutter (23039): #5      NormalizingDataProxy.readQuery
package:graphql/…/cache/_normalizing_data_proxy.dart:85
E/flutter (23039): #6      QueryManager.maybeRebroadcastQueries
package:graphql/…/core/query_manager.dart:473
E/flutter (23039): #7      QueryManager.query
package:graphql/…/core/query_manager.dart:164
E/flutter (23039): <asynchronous suspension>
E/flutter (23039): #8      GraphQLClient.query
package:graphql/src/graphql_client.dart:152
E/flutter (23039): <asynchronous suspension>
E/flutter (23039):

@mdmomeni Thanks for reporting this! Do you mind sharing how you're initializing the client? Specifically, how are you providing the Hive box to the client.

My main function:
void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  // Initialize Firebase
  await FCM.init();

  // Initialize Hive (from GraphQL package)
  await initHiveForFlutter();

  // Initialize UserController Hive box
  await UserController.init();

  // GraphQL
  final HttpLink httpLink = HttpLink(
    "http://<IP_ADDRESS>:8000/graphql",
  );

  final AuthLink authLink = AuthLink(
    getToken: () => UserController.token,
  );

  final Link link = authLink.concat(httpLink);

  ValueNotifier<GraphQLClient> client = ValueNotifier(
    GraphQLClient(
      link: link,
      cache: GraphQLCache(store: HiveStore()),
    ),
  );
  runApp(MyApp(client));
}

Also MyApp:
class MyApp extends StatelessWidget {
  const MyApp(this.client, {Key? key}) : super(key: key);
  final ValueNotifier<GraphQLClient> client;

  @override
  Widget build(BuildContext context) {
    return GraphQLProvider(
      client: client,
      child: GetMaterialApp(
...

Client provider:
GetBuilder<SearchController>(
              init: SearchController(),
              builder: (_) {
                return GraphQLConsumer(builder: (client) {
                  return Expanded(
                      child: Column(children: [
                    searchField(client, _),
                    const SizedBox(height: 10),
                    Expanded(
                        child: Stack(
                      alignment: Alignment.center,
                      children: [mainBody(_), submitBtn()],
                    ))
                  ]));
                });
              }),
...

  Widget searchField(GraphQLClient client, SearchController _) {
    return Padding(
      padding: const EdgeInsets.all(10),
      child: TextField(
        textDirection: TextDirection.ltr,
        decoration: CInputDecoration(hintText: "جستجو"),
        onChanged: (q) => onInputChange(q, client, _),
      ),
    );
  }

Cheers @mdmomeni! I've created a PR with a fix. If you're able to verify that it's working for you, that'd be a huge help!

Thank you, but how can I replace the updated code? and should I review the PR or something after testing it?

@mdmomeni
You should be able to add the branch as a dependency directly. I.e., update your pubspec.yaml file with
  graphql_flutter:
    git:
      url: git://github.com/zino-hofmann/graphql-flutter.git
      ref: fix-hive
      path: packages/graphql_flutter

I'm not sure if you can add a review, but a comment on the PR (or here) will be fine.

@mdmomeni
You should be able to add the branch as a dependency directly. I.e., update your pubspec.yaml file with
  graphql_flutter:
    git:
      url: git://github.com/zino-hofmann/graphql-flutter.git
      ref: fix-hive
      path: packages/graphql_flutter

I'm not sure if you can add a review, but a comment on the PR (or here) will be fine.

The exception still exists.
When I set fetchPolicy to FetchPolicy.networkOnly, this problem does not exist.
But I set it to FetchPolicy.cacheAndNetwork, and this exception occurred. I guess that the data type stored in hive does not match the Map.
This is my data structure：
[
  {
    _id: 6141e5e09fa3f5afd79e6ecb,
    type: urlLaunch,
    content:
      {
        image: image1.png,
        url: https://example1.com,
      },
    __typename: Recommend,
  },
  {
    _id: 6141e8029fa3f5afd79e6ecc,
    type: urlLaunch,
    content:
      {
        image: image.png,
        url: https://example.com,
      },
    __typename: Recommend,
  },
]

I use fast_immutable_collections  and freezed
@freezed
class Recommend with _$Recommend {
  factory Recommend({
    required String type,
    required IMap<String, String> content,
  }) = _Recommend;
  factory Recommend.fromJson(Map<String, dynamic> json) =>
      _$RecommendFromJson(json);
}

void exampleQuery () {
  final result =
      await client.query$Recommend(Options$Query$Recommend(
    operationName: 'exampleQuery',
    fetchPolicy: FetchPolicy.cacheAndNetwork,
    variables: Variables$Query$Recommend(
      memberId: memberId,
    ),
  ));

  if (result.hasException) {
    handleException(result);
    throw Exception(result.exception.toString());
  }
    final recommendList = IList.fromJson(
     ///  🔨 If I want to not report this exception, I need to do the following
     /// FIX: should work code json.decode(json.encode(result.data?["exampleQuery"]))
      result.data?["exampleQuery"],

      (dynamic item) => Recommend.fromJson(item),
    );
  return recommendList;
}

Thanks for reporting. Please check if #1167 fixes this for you! @Adherentman

@budde377
I checked the relevant code and it should solve the problem。
But I have a problem trying to use the latest code in pubspec.yaml.
graphql:
    git:
      url: https://github.com/zino-hofmann/graphql-flutter.git
      ref: main
      path: packages/graphql
  graphql_flutter:
    git:
      url: https://github.com/zino-hofmann/graphql-flutter.git
      ref: main
      path: packages/graphql_flutter

get error:
Because every version of graphql_flutter from git depends on graphql from hosted and example_app depends on graphql from git, graphql_flutter from git is forbidden.
So, because example_app depends on graphql_flutter from git, version solving failed.
pub get failed (1; So, because example_app depends on graphql_flutter from git, version solving failed.)

Or when will it be published on pub.dev

this is your error, you should put also inside the override package the graphql, this tell to pub "Hey you are using git, but there is some depenciences in common, so ignore it and use git".
It is strange, but the dependieces resolution world is more strange.
BTW I'm releasing the new beta release later in the day

I have used main branch to verify that it runs very well. Thank you.

@Adherentman the new beta is out


Fix cleanup logic

For the specialized logic previously added, keep deleting after the first limit is hit.
Add the tables that have specialized logic back to the 'other' list because the framework uses this list to check for FK constraints.

adresses https://github.com/rancher/rancher/issues/6659


[BUG] getter only cause issue when json-mapper deserialize object

Information

Version: 6.x
Packages: @tsed/json-mapper

Using @ReadOnly on a getter doesn't prevent to the following error when the class has getter property only:
Cannot set property test of #<DataSourceModel> which has only a getter
TypeError: Cannot set property test of #<DataSourceModel> which has only a getter

Example
class DataSourceModel {
  @Required()
  @Groups("!create")
  _id: string;

  @Property()
  @ReadOnly()
  get test() {
    return "test";
  }
}

const instance = new DataSourceModel();
instance._id = "id";
const obj = deserialize({ test: "hello", _id: "id" }, { type: DataSourceModel });  // throw error

Acceptance criteria

[ ] ReadOnly decorator disable the value assignment on decorated property
[ ] Mongoose should also ignore automatically the property decorated with @ReadOnly

:tada: This issue has been resolved in version 6.126.1 :tada:
The release is available on:

v6.126.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 7.0.0-beta.18 :tada:
The release is available on:

v7.0.0-beta.18
GitHub release

Your semantic-release bot :package::rocket:


chore: release main

:robot: I have created a release beep boop
finalbiome: 0.3.0
0.3.0 (2023-01-10)
Features

impl GamerAccount type #59 (a0bf808)
Impl returning of the intermediate result (db5ed53), closes #60
mechanics: added event DroppedByTimeout (d5c0cd1), closes #61
quota management impl (44607ab)
storage hasher in the mechanics changed (d15aa5c)
users: added registrar (8a20097)

Bug Fixes

deps: update actions/checkout action to v3.1.0 (28e8864)
deps: update renovatebot/github-action action to v34 (bfc79c5)
deps: update rust crate clap to 3.2.22 (63ad645)
deps: update rust crate clap to 3.2.23 (03c84a5)
deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)
deps: update rust crate serde to 1.0.145 (430df24)
deps: update rust crate serde to 1.0.150 (fcdcfe8)

finalbiome-node: 0.2.0
0.2.0 (2023-01-10)
Features

users: added registrar (8a20097)

Bug Fixes

deps: update rust crate clap to 3.2.22 (63ad645)
deps: update rust crate clap to 3.2.23 (03c84a5)

Dependencies

The following workspace dependencies were updated

dependencies

finalbiome-node-runtime bumped from 0.1.0 to 0.2.0

finalbiome-node-runtime: 0.2.0
0.2.0 (2023-01-10)
Features

quota management impl (44607ab)
users: added registrar (8a20097)

Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-template bumped from 0.1.0 to 0.1.1
pallet-users bumped from 0.1.0 to 0.2.0
pallet-organization-identity bumped from 0.1.0 to 0.1.1
pallet-fungible-assets bumped from 0.1.0 to 0.1.1
pallet-non-fungible-assets bumped from 0.1.0 to 0.2.0
pallet-mechanics bumped from 0.1.0 to 0.2.0
pallet-support bumped from 0.1.0 to 0.2.0

pallet-fungible-assets: 0.1.1
0.1.1 (2023-01-10)
Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

pallet-mechanics: 0.2.0
0.2.0 (2023-01-10)
Features

impl GamerAccount type #59 (a0bf808)
Impl returning of the intermediate result (db5ed53), closes #60
mechanics: added event DroppedByTimeout (d5c0cd1), closes #61
storage hasher in the mechanics changed (d15aa5c)

Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

pallet-non-fungible-assets: 0.2.0
0.2.0 (2023-01-10)
Features

impl GamerAccount type #59 (a0bf808)

Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

pallet-organization-identity: 0.1.1
0.1.1 (2023-01-10)
Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

pallet-support: 0.2.0
0.2.0 (2023-01-10)
Features

impl GamerAccount type #59 (a0bf808)

Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)
deps: update rust crate serde to 1.0.145 (430df24)
deps: update rust crate serde to 1.0.150 (fcdcfe8)

pallet-template: 0.1.1
0.1.1 (2023-01-10)
Bug Fixes

deps: update rust crate codec to 3.2.1 (ab129f8)
deps: update rust crate scale-info to 2.2.0 (9425939)
deps: update rust crate scale-info to 2.3.0 (830a533)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

pallet-users: 0.2.0
0.2.0 (2023-01-10)
Features

quota management impl (44607ab)
users: added registrar (8a20097)

Dependencies

The following workspace dependencies were updated

dependencies

pallet-support bumped from 0.1.0 to 0.2.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-template-v0.1.1 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-support-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-users-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-mechanics-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-non-fungible-assets-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-fungible-assets-v0.1.1 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/pallet-organization-identity-v0.1.1 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/finalbiome-node-runtime-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/finalbiome-node-v0.2.0 :sunflower:

:robot: Release is at https://github.com/finalbiome/finalbiome-node/releases/tag/finalbiome-v0.3.0 :sunflower:


File output sink?

Hi All,
Very cool project. One thing I'd find useful would be a file sink, so I can then follow files in Splunk. Would this be a much to do ? Also, if you've no time, I'd like to write it - how do I even start ?

@sokoow you can just have splunk hoover up /var/log/containers/eventrouter*. We do this with our on-premise splunk + k8s and it works just fine. We use the glog sync and it logs to stdout for the eventrouter logs.

How do you guys deal with files in var/log/containers being symlinks (to /var/log/pods and to /var/lib/docker/containers)?
@SEJeff do you mount all these directories inside your splunk container for it to hoover?

@queimadus we simply install and config splunk in the host operating system without a container. It would be trivial enough to volume mount those directories into a container if you're running on a host operating system such as Fedora CoreOS / Container Linux / RHEL Atomic Host however.

@SEJeff thanks for the comments on this. @sokoow have you gotten what you needed? Closing but feel free to reopen if not.


removed escape slashes

duplicate?

This is the RHEL 7 guide, other one was the RHEL 6 guide. Same tweak so merging this one since the other was reviewed.


Better error message if init returns value

Mirrors the behavior of normal Python.
Addresses https://github.com/numba/numba/issues/4985
>>> import numba
>>> class Test:
...     def __init__(self):
...             return 7
...
>>> Test()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: __init__() should return None, not 'int'
>>> jitTest = numba.experimental.jitclass([])(Test)
__main__:1: NumbaDeprecationWarning: The 'numba.jitclass' decorator has moved to 'numba.experimental.jitclass' to better reflect the experimental nature of the functionality. Please update your imports to accommodate this change and see http://numba.pydata.org/numba-doc/latest/reference/deprecation.html#change-of-jitclass-location for the time frame.
>>> jitTest()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/ethanpronovost/Documents/Projects/numba/numba/numba/experimental/jitclass/base.py", line 122, in __call__
    return cls._ctor(*bind.args[1:], **bind.kwargs)
  File "/Users/ethanpronovost/Documents/Projects/numba/numba/numba/core/dispatcher.py", line 401, in _compile_for_args
    error_rewrite(e, 'typing')
  File "/Users/ethanpronovost/Documents/Projects/numba/numba/numba/core/dispatcher.py", line 344, in error_rewrite
    reraise(type(e), e, None)
  File "/Users/ethanpronovost/Documents/Projects/numba/numba/numba/core/utils.py", line 79, in reraise
    raise value.with_traceback(tb)
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Internal error at <numba.core.typeinfer.CallConstraint object at 0x61ed59cf8>.
__init__() should return None, not 'Literal[int](7)'
[1] During: resolving callee type: jitclass.Test#11daf76d8<>
[2] During: typing of call at <string> (3)

Enable logging at debug level for details.

File "<string>", line 3:
<source missing, REPL/exec in use?>

Many thanks for the PR! I'll add this to the review queue.

This LGTM, but someone who is more familiar with jitclass might want to take a look.


Make fails on CentOS 8 "use of unstable library feature 'matches_macro'"

make  fails on CentOS 8 with a fresh clone of https://github.com/cloudflare/quiche/commit/fcbf789d8e7e62f3ffd4562e70e969db1f520fb9
make[1]: Entering directory '/root/quic/nginx-1.16.1'
cd ../quiche && cargo build --release --no-default-features
    Updating crates.io index
  Downloaded lazy_static v1.4.0
  Downloaded log v0.4.11
  Downloaded cmake v0.1.44
  Downloaded libc v0.2.80
  Downloaded libm v0.2.1
  Downloaded cc v1.0.61
  Downloaded cfg-if v0.1.10
  Downloaded ring v0.16.15
  Downloaded spin v0.5.2
  Downloaded untrusted v0.7.1
  Downloaded once_cell v1.4.1
   Compiling cc v1.0.61
   Compiling libc v0.2.80
   Compiling libm v0.2.1
   Compiling log v0.4.11
   Compiling spin v0.5.2
   Compiling cfg-if v0.1.10
   Compiling untrusted v0.7.1
   Compiling once_cell v1.4.1
   Compiling lazy_static v1.4.0
   Compiling cmake v0.1.44
   Compiling ring v0.16.15
   Compiling quiche v0.6.0 (/root/quic/quiche)
error[E0658]: use of unstable library feature 'matches_macro'
    --> src/lib.rs:1075:5
     |
1075 |     matches!(
     |     ^^^^^^^
     |
     = note: for more information, see https://github.com/rust-lang/rust/issues/65721

error[E0658]: use of unstable library feature 'matches_macro'
   --> src/frame.rs:709:10
    |
709 |         !matches!(self, Frame::Padding { .. } |
    |          ^^^^^^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/65721

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `quiche`.

To learn more, run the command again with --verbose.
make[1]: *** [objs/Makefile:1361: ../quiche/target/release/libquiche.a] Error 101
make[1]: Leaving directory '/root/quic/nginx-1.16.1'
make: *** [Makefile:8: build] Error 2

https://github.com/rust-lang/rust/issues/65721

I was using the default version of cargo from yum install cargo on CentOS 8 which fails to build quiche. Installing from https://rustup.rs solved the build issue I was having.


bug: the starknet_getEvents rpc method is failing

Current behavior
The starknet_getEvents method is failing when called with the associated hurl script. See the received response below:
{"jsonrpc":"2.0","error":{"code":520,"message":"Unknown error"},"id":1}

Expected behavior
Calling the starknet_getEvents should result in a successful response as described in the starknet specification.
Steps to reproduce:

Run Beerus locally: cargo run --bin beerus-rpc
Execute the associated hurl script: hurl --ignore-asserts examples/beerus-rpc/starknet/starknet_getEvents.hurl

Other information:
The error can come either from a malformed request in the hurl file or from Beerus itself.

assign this please


Incompatibility with react 19

https://github.com/framer/motion/issues/2668#issuecomment-2161555550

Thanks for the headsup 👍🏻
I'll add React 19 support once it has been released as a stable version and once Framer Motion supports it in a stable version as well.

@Temzasse  Framer Motion supported React 19. Could you guys to upgrade react-modal-sheet

Yes, @Temzasse We are really looking forward to the update

This has been fixed in v4.

[!NOTE]
The version 4 has breaking changes as it expects motion as peer dependency so you need to migrate to the new Motion package that has replaced framer-motion.


Implement ISheet.Cells collection to return a cell range

In EPPlus, it implements a string indexer for cell range selection
worksheet.Cells["B1"].Value = "This is cell B1"; // Sets the value of Cell B1
worksheet.Cells[1, 2].Value = "This is cell B1"; // Also sets the value of Cell B1

worksheet.Cells["A1:B3,D1:E57"].Style.NumberFormat.Format = "#,##0"; //Sets the number format for a range containing two addresses.
worksheet.Cells["A:B"].Style.Font.Bold = true; //Sets font-bold to true for column A & B

Reference
https://github.com/EPPlusSoftware/EPPlus/wiki/Addressing-a-worksheet

#257

ClosedXML also has a similar feature
https://github.com/closedxml/closedxml/wiki/Selecting-Cells-and-Ranges


Add CSV Backup Folder Preference Option

This PR implements a CSV Backup Folder option in preferences.
Closes #334

Suggestion: CSV export can take some time (usually small, but still), so we should prevent the app closing while backup creation is in process. Maybe a dialog:

CSV Backup is in process
The app will be closed when backup will be finished.
[Cancel]

Or we could not notify a user but simply let the app to continue running in the background.

The ExportToCSV function is not async, meaning the UI will freeze for a few milliseconds while the file is exported and the user shouldn't even notice it really. Because the UI freezes, the window can't be closed until it is done.
I'll do some testing of the feature on big accounts, 1000+ transactions, and if the export is noticeably long, I'll make the function async. If it's async and the window is closed, the export will continue running in the background until the function finishes and then the whole application will close.

I need to leave home for a couple of hours but then I can finish it.

I need to leave home for a couple of hours but then I can finish it.

No worries if I have some free time before you I'll finish it up.

@DaPigGuy Regarding the last commit (https://github.com/nlogozzo/NickvisionMoney/pull/383/commits/c68d14ea506cf81bbc8bd3033dcec48596526841), so you will know too:

The problem was we used Adw.PreferencesPage wrong. It is intended to be used with other Adw.Preferences* widgets and doesn't require anything else: it has title, overlay etc.
But we used Gtk.Box as its child, placing headerbar and Adw.PreferencesPage here. And it basically turned PreferencedWindow to a simple Window

While everything looked good, PreferencesWindow with "overwritten" layout can't show toasts, although there's no error on AddToast call in this case.


ngTagsInput autocomplete not working

Hi
I have created and ionic, angularjs mobile app and used the ngTagsInput module. It works fine for just simple tags but does not seem to work when its set to  auto complete. when i set focus on the input the list of suggestions does not show.Please see code below:
html:

controller:
$scope.standardFieldsTemp = [];
$scope.loadTags = function (query) {
var options = [{ text: "tag1" }, { text: "tag2" } ];
var deferred = $q.defer();
deferred.resolve(options);
return deferred.promise;
}

Same problem here with a copy/paste from a working plunker into my Ionic project. More specifically, it fails on :
TypeError: Cannot read property 'data' of undefined
at ng-tags-input.js:590
at processQueue (ionic.bundle.js:23394)
at ionic.bundle.js:23410
at Scope.$eval (ionic.bundle.js:24673)
at Scope.$digest (ionic.bundle.js:24484)
at Scope.$apply (ionic.bundle.js:24778)
at ionic.bundle.js:26545
at completeOutstandingRequest (ionic.bundle.js:14221)
at ionic.bundle.js:14493
Which corresponds to the handling of the promise used to get tags :
items = tiUtil.makeObjectArray(items.data || items, getTagId());

@StephJan - Did you figure out your issue? I'm having the same exact problem as you.

check this issue https://github.com/mbenford/ngTagsInput/issues/89. I have the same problem this solution worked for me.


Still towards the TODO list

Seems like we are in a spiral towards the perfect wallet. Sometimes it feels we are running in circles and sometimes we are getting closer to :p
So, the intent of this post is to propose the minimum acceptable wallet that will get all the basic functions done in a proper way so we could go to a testnet as soon as possible.
I would propose that we break it initially into 5 modules (that could be broken into more modules later):

INTERFACE AND INITIALIZATION
terminal functions, logic flow of wallet,...

KEYS AND FILES HANDLING
generate, restore, rewrite, load, store, write_watch_only_wallet, store_to,
get_keys_file_data,get_cache_file_data, encrypt_keys, decrypt_keys,
save_to_file, load_from_file

TRANSACTION CREATION
commit_tx, save_tx, sign_tx, load_unsigned_tx, load_tx, create_transactions_*,

TRANSACTION POST PROCESSING
balance, unlocked_balance, get_transfers, get_payments, get_unconfirmed,
get_tx_key,get_tx_proof,get_spend_proof, get_address_book,

RPC / ENGINE (IMPLEMENTATION) CONNECTION
update_pool_state, get_base_fee,

The idea is to create properly the most basic functions to achieve the following milestones:

-M1: terminal working with essential commands available
-M2: help
-M3: screen locker

-M1: functions to store in a file a jamtis_mock_keys struct and load it
-M2: encrypt/decrypt files properly
-M3: other functions

-M1: make a transaction to an address
-M2: add options to transactions
-M3: ...

-M1: visualize transactions made and received
-M2: get info about enotes
-M3: transaction proofs

-M1: connection to ledger to add and receive blocks and txs
-M2: estimate fees
-M3: ...

The line of thought being: when all M1 of all modules are achieved, then we would have the most basic proper functional wallet.
All of these modules have already many or most of the things done but not yet in a clean and coherent way. So I guess we are missing a bit of work coordination and consensus about the most basic milestones and acceptable code.
So, is it a good idea to organize and track the work like that? If so, we could better specify the milestones and organize who will be doing what. Would you change something?

In this case I don't think your answer differs from the intent of my approach. I was just trying to be more specific.

@rbrunner7 that does sound like what I'd do. But I think dangerousfreedom's way isn't that different...
I have some time to work on it today. Shouldn't that struct be moved out of mocks into some kind of a seraphis_common directory?

It's slowly dawning on me how difficult it will probably be to get this going, with a group of people that don't know each other well yet, and with doing everything in writing. People acting in good faith, trying their best, but difficult circumstances. It will certainly get better after managing to really get moving, but now I feel it's very hard.
I will gladly try to answer questions like here, but please keep in mind that I will be less and less able to provide any answers as time and work progresses. With quite some restraint I do not go into detailed designing and programming of the Seraphis wallet. It's very tempting, but I will directly walk into overwork and burnout if I do. "Managing" the whole venture already eats almost all of my time.
So it happens that unfortunately I don't have much to offer regarding the design and the implementation of the key container.
But well, we have a number of design questions on the table, and seems to me the only sensible way is to methodically and thoroughly study them one by one until good answers can be found, right? I have a personal saying here: "Sometimes only really understanding something helps".
 Just honestly trying to be helpful and also giving people some hints about the way how I "tick" to make future communication a bit less hard.)
There are in the current library two structs with key material already. @DangerousFreedom1984 used them in the code he linked. Is that the right approach? I don't know. How to find out? Reading the library, checking where and how these structs are used, how important and fundamental they are.
I see two possible outcomes of such an investigation right now, but maybe there are more: They really are only closely connected to mocking, in which case we probably should define our own, or they are quite fundamental and important, in which case we should probably use them but on the same time open a discussion with @UkoeHB whether names with "mock" in it are still appropriate in this particular case or whether we should rename them.
About serializing. In the Monero codebase we have two kinds of serialization that are widely used and with broad support, binary_archive and that "KV" stuff. Which do we take? Good question. I always wondered why for things that go into the wallet .keys files currently KV (or even RapidJason) and not binary is used. Binary is faster, more compact, as far as I know almost universally used over the Monero codebase if one has to write into files, but maybe wallet files are in some way special? Or KV is as an exception a good idea here for some other reason? Interesting research job.
Certainly feel free to reach beyond our little group into the "broader" Monero dev community and for example throw any specific questions about wallet serialization approaches into the dev IRC channel or Matrix room.


Fix issue of testgtpv1 not being generated when gtpv1 build.

Unresolved issue that testgtpv1 is not generated when gtpv1 is built.
(This has been resolved in stage 3.)

LGTM


GD-363: Parameterized test stopped working due to test_case names having invalid size

The used GdUnit4 version
4.2.2 (Pre Release/Master branch)
The used Godot version
v4.2.1.stable.official [b09f793f5]
Operating System
Windows 10
Describe the bug
I know this is not a bug on an official release, but I wanted to warn you that after replacing my local gdUnit4 that was installed from the AssetLib, with the version from the master branch bearing the changes to solve the issue GD-359, one of my tests stopped working, showing the following error:
line 12: Internal Error:
	The resolved test_case names has invalid size!
	Please report this issue as a bug!

Steps to Reproduce
This is my test that stopped working, unfortunately it references other code unique for my game, and therefore it would be difficult to provide generic steps 😅
class_name LogServiceTest
extends GdUnitTestSuite

class TestClass:
	pass

@warning_ignore("unused_parameter")
func test_register(
	test: String,
	type,
	log_level,
	expected_logs,
	test_parameters = [
		["level not registered if type is NOT valid", null, LogService.LogLevel.LOG, {}],
		[
			"level registered if log_level not provided",
			TestClass,
			null,
			{TestClass: LogService.LogLevel.ERROR}
		],
		[
			"level registered if type is valid",
			TestClass,
			LogService.LogLevel.LOG,
			{TestClass: LogService.LogLevel.LOG}
		]
	]
):
	var log_service = LogService.new()
	if log_level == null:
		log_service.register(type)
	else:
		log_service.register(type, log_level)
	assert_dict(log_service._logs).is_equal(expected_logs).override_failure_message(test)

Minimal reproduction project
No response

Oh! This is related to my latest changes, thanks for reporting this issue.
I was afraid that I might break something and had already installed this error message as a precaution.

Glad to have been of help.
Very cautious of you to add that comment 👍


fix(protobuf) use correct Protobuf icon, adds Buf

Fixes #IssueNumber
Changes proposed:

[x] Add
[ ] Delete
[x] Fix
[ ] Prepare

I noticed that the icon for protobuf files (e.g. api.proto) was actually for a protobuf implementation library, protobuf.js, and not the one used for protobuf itself.  I updated that in the first commit.
While I was here I noticed that there was no icon for Buf (a protobuf tool) configs, so I added those.

@dimitropoulos thanks for this PR. I think we chose that one because we didn't find any official protobuf icon. I've looked into the official website and there's not any logo. In any case, given that the icon you propose is being used in several places, I guess it makes sense.

thanks for taking a look @robertohuertasm.  Indeed, that's the closest thing to a "protobuf logo" that exists.
I'm not quite clear on why the CI is failing now after merging from master.  any suggestions?

There's a typo in the buf filename. It should be icons/file_type.buf.svg instead of icons/file_type.buf.svg

@robertohuertasm I updated the file name

thanks @robertohuertasm!


MSID: 96535 Version: 2 DOI: 10.1101/2<IP_ADDRESS>02626

MSID: 96535
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>02626
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96535
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>02626

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96535v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>02626
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96535/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [title-upper-case] Content of  element is entirely in upper case: Is that correct? 'CD300LG'
warn: [title-upper-case] Content of  element is entirely in upper case: Is that correct? 'CD300LG.'


Support Environment Variables

AWS Lambda now support environment variables, which is much better way of providing environment specific configuration then bundling json files.
https://aws.amazon.com/about-aws/whats-new/2016/11/aws-lambda-supports-environment-variables/
http://docs.aws.amazon.com/lambda/latest/dg/env_variables.html
Could it be supported by kappa?

oh, there is already pull request for that. Any chance for marge and release?

Link?

https://github.com/garnaat/kappa/pull/98

It was merged.


Shut down PC

Hello and thank you for the best software! Could you maybe add a feature to shut down the PC once all downloads are done? Thank you again! 👍

and what if some of the queued downloads did not succeed? then the log is gone and you even don't know which downloads failed. before such a feature can be implemented, others have to be refined (download manager, persistent logs and so on). low priority...

I mean there can be for example filled logs in TwitchID.txt of that failed download before it shuts down? I don't know, it was just an idea that would help me but still it's not a big deal :)

I have wrapped my head around this issue and there is a lot more involved than a simple shutdown command. Even user rights come into play in combination with UAC. This feature has such a low gain of usability for TL that it is simply not worth investing the required amount of time to design, implement and test it.


Add "auto generated" comment on top of generated files

Hi @ReallyLiri this is not something I would like to add to fabrikt.
I suggest you instead add this comment to the generated classes via your build script, after the generate task has run. With gradle, this can be accomplished by adding a doLast section to your task


feat(chart-explore): add select all functionality to table viz type

SUMMARY

The select all functionality was removed previously, but our users rely on this useful feature in the chart explorer, so this PR is for bringing back that feature.
With the way things currently are, the user must manually select columns one by one by clicking or dragging and dropping into the columns field when building a query in the explore view.  When the user is initially creating a chart, it is often the case that they want to query all the possible fields to identify what is relevant and narrow it down. This becomes tedious when dealing with data-sets that have many columns (100+).
We have had to create a temporary solution in our fork just to allow our users who rely on it to use the chart explorer. This design aims to reintroduce the select all functionality in a non disruptive way while keeping the UX clean. It is only shown in the columns select when in the raw records query mode in the explore view on the 'table plugin', since this is the place where it is needed by our users.
Thoughts and feedback are appreciated!
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Drag and Drop Feature Enabled:
SELECT ALL
When the columns field is empty, the select all button can be clicked to populate the columns field with all available options.

DESELECT ALL
Once any option(s) have been selected, the button text changes to deselect all. If it is clicked in this state, it empties the columns field (and the button text changes back to 'SELECT ALL').

Drag and Drop Feature Disabled:
* the columns field is "full" when all options are currently selected (list of selected values equals list of options)
SELECT ALL
When the columns field is not full*, the select all button can be clicked to add all remaining options. Since there is already a 'clear' button built in to select control when the Drag and Drop Feature is disabled, the select all button does not turn into a deselect all button when an item is added. This allows a user to select all options without first clearing the values and then selecting all. The user can still clear the values at any time with the 'clear' button.

SELECT ALL Disabled
When the columns field is full*, the select all button is disabled because all options are currently selected.

TESTING INSTRUCTIONS

Drag and Drop Feature enabled

Explore a chart that uses the 'Table' viz type.
In the 'Data' tab, under the 'Query' drop down, select 'Raw Records' as the 'Query Mode'.
For the 'Columns' selector, you should see a 'Select All' or 'Deselect All' button.
Clicking it should select all options when the button is in select all mode, and should deselect all buttons when in deselect mode.

Drag and Drop Feature disabled

Explore a chart that uses the 'Table' viz type.
In the 'Data' tab, under the 'Query' drop down, select 'Raw Records' as the 'Query Mode'.
For the 'Columns' selector, you should see a 'SELECT ALL' button.
If all options are selected, the button should be disabled.
Otherwise, the button should be enabled and should select all remaining options.
The clear button in the selector component should still clear all selected values.

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/discussions/18247
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

Hi @cccs-RyanK! Wanted to let you know that we are currently working on adding "select all" feature to all of the multiple choice select fields (besides dnd) which should be available soon (probably 2-3 weeks). Drag&drop select all is something that I hope we will tackle in the upcoming weeks so there will be a better solution provided from our side.
Thank you for helping an developing this solution 🙏

Hi @kasiazjc! Thanks for the info! Is there anywhere we can track what features are being actively worked on from your end? We'd like to avoid duplicating effort if we can!

Hi @cccs-RyanK! Wanted to let you know that we are currently working on adding "select all" feature to all of the multiple choice select fields (besides dnd) which should be available soon (probably 2-3 weeks). Drag&drop select all is something that I hope we will tackle in the upcoming weeks so there will be a better solution provided from our side.
Thank you for helping an developing this solution 🙏

Hi @kasiazjc! Thanks for the info! Is there anywhere we can track what features are being actively worked on from your end? We'd like to avoid duplicating effort if we can!

Unfortunately there is no way to track it right now 😢 we're trying to find a way to sort it out, but it may not happen anytime soon. I will try my best to keep you updated for now about this one 🤞


Eliminate test/CI dependency on Boost.Random

CI and testing have a remaining dependency on Boost.Random. Write a simple local wide-integer random bit stream to eliminate this dependency and further streamline cloning in CI.

If/when done and now that both Multiprecision as well as Math have gone standalone in Boost, this should leave dependencies on just:
          git submodule update --init libs/config
          git submodule update --init libs/math
          git submodule update --init libs/multiprecision

Let's give it a try in CI and see how it goes...


chore: add repository url to package.json

This will add a url on the npm site and allow to use relative links in the readme. (they are now broken on npm)

Codecov Report

Merging #310 (2a62953) into main (8693c49) will increase coverage by 0.17%.
The diff coverage is 92.45%.

@@            Coverage Diff             @@
##             main     #310      +/-   ##
==========================================
+ Coverage   88.07%   88.25%   +0.17%
==========================================
  Files         218      221       +3
  Lines        3926     4001      +75
  Branches      452      464      +12
==========================================
+ Hits         3458     3531      +73
- Misses        468      470       +2

Impacted Files
Coverage Δ

src/agent/AgentConfig.ts
100.00% <ø> (+4.25%)
:arrow_up:

src/decorators/attachment/Attachment.ts
100.00% <ø> (ø)

src/modules/credentials/CredentialsModule.ts
86.66% <0.00%> (ø)

src/modules/credentials/models/Credential.ts
75.00% <0.00%> (ø)

...c/modules/credentials/models/IndyCredentialInfo.ts
60.00% <0.00%> (ø)

src/modules/proofs/ProofsModule.ts
88.00% <0.00%> (ø)

src/types.ts
100.00% <ø> (ø)

src/utils/BufferEncoder.ts
84.61% <50.00%> (-15.39%)
:arrow_down:

src/modules/connections/ConnectionsModule.ts
67.60% <100.00%> (ø)

...modules/credentials/repository/CredentialRecord.ts
93.61% <100.00%> (-4.26%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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


docs: getting started with branch planner

Tried to explain most of the steps, but intentionally did not add docs about how to configure the tf-controller itself and set it as a pre-requirement.
I'm not sure it satisfies #783 or not, but it's related to that issue.
Related to #783
References:

https://github.com/weaveworks/tf-controller/issues/783

Based on this document we can add the entry with refined (more user friendly) wording to the docs website under Terraform.


Add test for CoW AMM commitment

With enabling phase 2 of CoW AMM, solvers can execute CoW AMM orders with custom amounts. This requires commiting and uncommiting the order in the CoW AMM smart contract. Not uncommiting the order is a violation of social consensus rules since it prevents the default order from getting executed.
This PR implements a test where after every settlement which contains a precommit interaction from the CoW AMM address the commited order for that address is checked.
Since there seem to be no commits so far, the code is a bit difficult to test. I added a test with tailored call data.

Looks good overall. It's hard to be very confident this works but we can merge and see I guess...
Will wait for you to fix the comments before approving.

I fixed to doc strings. If you approve I would merge and see how it goes.


Ark manager keep updateing to the same version of the server over and over again

Hi, I have a cron script that checks for update every 30 mins, and I looked at the logs today and I am seeing this
2016-11-28 03:54:32: No update needed.
2016-11-28 03:59:27: No update needed.
2016-11-28 04:19:16: No update needed.
2016-11-28 05:04:32: No update needed.
2016-11-28 05:34:37: No update needed.
2016-11-28 06:04:32: No update needed.
2016-11-28 06:34:30: No update needed.
2016-11-28 07:04:32: No update needed.
2016-11-28 07:34:29: No update needed.
2016-11-28 08:04:26: No update needed.
2016-11-28 08:34:31: No update needed.
2016-11-28 09:04:28: No update needed.
2016-11-28 09:34:31: No update needed.
2016-11-28 10:04:27: No update needed.
2016-11-28 10:34:29: No update needed.
2016-11-28 11:04:27: No update needed.
2016-11-28 11:34:28: No update needed.
2016-11-28 12:04:18: No update needed.
2016-11-28 12:34:14: No update needed.
2016-11-28 13:04:18: No update needed.
2016-11-28 13:35:16: No update needed.
2016-11-28 14:05:26: update to 1483845 complete
2016-11-28 14:34:18: No update needed.
2016-11-28 15:04:18: No update needed.
2016-11-28 15:34:14: No update needed.
2016-11-28 17:16:49: update to 1484033 complete
2016-11-28 17:34:11: No update needed.
2016-11-28 18:15:29: update to 1484033 complete
2016-11-28 18:34:27: update to 1484033 complete
2016-11-28 19:04:22: update to 1484033 complete
2016-11-28 19:45:27: update to 1484033 complete
2016-11-28 20:15:22: update to 1484033 complete
2016-11-28 20:44:41: update to 1484033 complete
2016-11-28 21:15:03: update to 1484033 complete
2016-11-28 21:34:24: update to 1484033 complete
2016-11-28 22:04:20: update to 1484033 complete
2016-11-28 22:34:24: update to 1484033 complete
2016-11-28 23:04:26: update to 1484033 complete
2016-11-28 23:34:31: update to 1484033 complete
2016-11-29 02:15:22: update to 1484033 complete
2016-11-29 02:20:52: update to 1484033 complete
2016-11-29 02:25:27: update to 1484033 complete
2016-11-29 02:30:53: update to 1484033 complete
2016-11-29 02:35:25: update to 1484033 complete
2016-11-29 02:40:53: update to 1484033 complete
2016-11-29 02:45:25: update to 1484033 complete
2016-11-29 02:50:55: update to 1484033 complete
2016-11-29 02:55:29: update to 1484033 complete
2016-11-29 03:00:23: update to 1484033 complete
2016-11-29 03:05:49: update to 1484033 complete
2016-11-29 03:10:26: update to 1484033 complete
2016-11-29 03:15:52: update to 1484033 complete
2016-11-29 03:20:26: update to 1484033 complete
2016-11-29 03:25:55: update to 1484033 complete
2016-11-29 03:30:23: update to 1484033 complete
2016-11-29 03:35:54: update to 1484033 complete
2016-11-29 03:40:27: update to 1484033 complete
2016-11-29 03:45:50: update to 1484033 complete
2016-11-29 03:50:24: update to 1484033 complete
2016-11-29 03:55:55: update to 1484033 complete
2016-11-29 04:00:26: update to 1484033 complete
2016-11-29 04:15:14: update to 1484033 complete
2016-11-29 05:04:23: update to 1484033 complete
2016-11-29 05:34:23: update to 1484033 complete
2016-11-29 06:04:25: update to 1484033 complete
2016-11-29 06:34:25: update to 1484033 complete
2016-11-29 07:15:26: update to 1484033 complete
2016-11-29 07:34:22: update to 1484033 complete
2016-11-29 08:04:28: update to 1484033 complete
2016-11-29 08:34:25: update to 1484033 complete
2016-11-29 09:04:24: update to 1484033 complete
2016-11-29 09:40:35: update to 1484033 complete
2016-11-29 09:40:42: Mod 661564024 updated
2016-11-29 10:15:24: update to 1484033 complete
2016-11-29 10:34:24: update to 1484033 complete
2016-11-29 11:05:22: update to 1484033 complete
2016-11-29 11:34:24: update to 1484033 complete
2016-11-29 12:13:26: update to 1484033 complete
2016-11-29 12:45:22: update to 1484033 complete
2016-11-29 13:04:24: update to 1484033 complete
2016-11-29 13:45:27: update to 1484033 complete

This is the same issue in a previous thread. so closing this one.


When using Swarmkit, secrets are NOT getting passed to service running in container.

Description
When using Swarmkit, secrets are NOT getting passed to service running in container.
Using swarmkit and trying to use secrets feature. Used swarmctl command, to create new secret. When service is created, assigned secret to that service. But secret is not being sent to that service.
Steps to reproduce the issue:
Using the latest changes in swarmkit repo:
https://github.com/docker/swarmkit
BUILD_COMMAND:
make binaries
START THE DAEMON(SWARM MODE):
swarmd -d /tmp/node-1 --listen-control-api /tmp/node-1/swarm.sock --hostname node-1 &
export SWARM_SOCKET=/tmp/node-1/swarm.sock
swarmctl node ls (And nodes status looks good, ACTIVE and READY)
CREATE_SECRET:
swarmctl secret create secret1 -f test_file
na94sp0r9bppg3q8bdxg5c2jl
START SERVICE, THAT HAS ACCESS TO SECRET:
swarmctl service create --name redis_2 --secret secret1 --image redis:3.0.5
5amksnt73frtjiy7q62la3bou
(ISSUE-> NOT SEEING THE SECRETS MAPPED IN THE REDIS CONTAINER..)
Describe the results you received:
(ISSUE-> NOT SEEING THE SECRETS MAPPED IN THE REDIS CONTAINER..)
Describe the results you expected:
Expected the secret to be mapped to the container's filesystem, but it was not there.
Checked under /var/run/secrets/ as well as /run/secrets, there was NO secrets folder.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Docker version 17.06.2-ce, build cec0b72
Output of docker info:(CAPTURED OUTPUT, WHEN SWARM DAEMON WAS NO LONGER RUNNING)
sudo docker info
Containers: 58
Running: 2
Paused: 0
Stopped: 56
Images: 67
Server Version: 17.06.2-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 220
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170
runc version: 810190ceaa507aa2727d7ae6f4790c76ec150bd2
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-97-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.922GiB
Name: skris14-ubuntu16.04-VM1
ID: RPPE:SGCR:KOWR:6NEM:JBJF:XB2D:XDWP:OGIM:PGFU:467K:3QTR:B4GZ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: (MANUALLY EDITED) USING PROXY SERVER
Https Proxy: (MANUALLY EDITED) USING PROXY SERVER
No Proxy: localhost,<IP_ADDRESS>
Username: skris14
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
WARNING: No swap limit support
Additional environment details (AWS, VirtualBox, physical, etc.):
I am running inside a VM(ubuntu 16.04), host machine runs Ubuntu as well.

@sudharkrish are you only using swarmctl? It is possible that swarmctl is behind swarmd. Do you also see this issue when you use Docker Swarm Mode and create secrets using the Docker CLI?