.list() bug ?

Expected Behaviour
".list()" should list elements.
Actual Behaviour
".list()" does not list every elements but ".get" display it if I have the key.
Reproduce Scenario (including but not limited to)
Run the following code several time.
Steps to Reproduce
Run the following code several time.
Platform and Version

@adobe/aio-lib-state: 5.0.2

Sample Code that illustrates the problem
import { init } from '@adobe/aio-lib-state';

export async function main() {

    try {
        const as = await init()

        //await as.deleteAll({match: "test1.*"}) // To cleanup if necessary
        const id = "test1."+Math.random()
        await as.put(id, "ID IS : " + id)

        const one = await as.get("test1.0.3514122052590529") // Use a previous inserted record

        const res = []
        for await (const { keys } of as.list({
            match: 'test1.*',
            countHint: 1000,
        })) {
            for (const key of keys) {
                res.push(key)
            }
        }
        return {
            statusCode: 200,
            body: { res, one }
        }
    } catch (error) {

        return {
            statusCode: 500,
            body: error
        }
    }
}

Logs taken while reproducing problem
Execution 1
{
    "one": {
        "expiration": "2024-10-04T13:00:45.891Z",
        "value": "ID IS : **test1.0.6753679853643251**"
    },
    "res": [
        "**test1.0.6753679853643251**"
    ]
}

Execution X (Error)
{
    "one": {
        "expiration": "2024-10-04T13:00:45.891Z",
        "value": "ID IS : **test1.0.3514122052590529**"
    },
    "res": [
        **[... NO test1.0.3514122052590529]**
        "test1.0.6753679853643251"
    ]
}

Execution X + 1 (I hoped it appears this time)
{
    "one": {
        "expiration": "2024-10-04T13:00:58.458Z",
        "value": "ID IS : _test1.0.6975951631977719_"
    },
    "res": [
        **[... NO test1.0.3514122052590529]**
        "test1.0.6753679853643251",
        "_test1.0.6975951631977719_"
    ]
}

More details
I create a lot of records in state. Sometimes, a new records does not appears with .list() method, and it won't never appear. If I use .get() to retrieve a specific record wich DOES NOT appears with .list(), I successful get it.
Patrick said to me you can not reproduce it. I am running it on a huge db (I can send you the environment if nested), maybe it's a volumetry issue ?

Hi @syno-dlr thanks for reporting this, I will investigate, could you give me more details about the number of keys you are writing?
Yes please also send me the environment and every additional information you can think of. Thanks!

this is what I tried so far and could not reproduce the issue doing so:

put 10k key-values that start with test1.*. From a local node process, with a state instance initialized to my credentials, I ran:

const KEYS_PER_ITERATION=1000;
const ITERATIONS=10;
for (let i = 0; i<ITERATIONS; ++i) {
  await Promise.all((new Array(KEYS_PER_ITERATION).fill(0)).map(async (_,idx) => {
    const id = "test1." + Math.random();
    await state.put(id, "ID IS : " + id, { ttl: 3600 });
  }));
  console.log(`${(i + 1) * 1000}/${ITERATIONS*KEYS_PER_ITERATION}`);
}

deployed the following action

export async function main() {
    try {
        const as = await init()
        // put two new keys in the two bags
        const id1 = "test1."+Math.random()
        await as.put(id1, "ID IS : " + id1)
        const id2 = "test2."+Math.random()
        await as.put(id2, "ID IS : " + id2)

        // test1.* is preloaded with many keys
        const res = []
        for await (const { keys } of as.list({
            match: 'test1.*',
            countHint: 134, // some random value to make it "harder", not a multiple of 10k
        })) {
              res.push(...keys)
        }

        const res2 = []
        for await (const { keys } of as.list({
            match: 'test2.*',
            countHint: 173,  // some other random value
        })) {
          res2.push(...keys)
        }
        return {
            statusCode: 200,
            body: {reslength: res.length, res2: res2, res2length: res2.length, one }
        }
    } catch (error) {
        return {
            statusCode: 500,
            body: error
        }
    }
}

At every invocation the action adds a key in test1.* and a key in a new bag test2.*. Then we return the length of each bag returned from listing all keys with those prefixes. The expected result must be the prevsize_of_the_bag + 1

Results (as expected)
// first invocation
{
  "res2": ["test2.0.3062791872061441""],
  "res2length": 1,
  "reslength": 10001
}
// 2nd
{
  "res2": ["test2.0.3062791872061441", "test2.0.9354860568075689"],
  "res2length": 2,
  "reslength": 10002
}
// 4th
{
  "res2": ["test2.0.3062791872061441", "test2.0.8683097928544137", "test2.0.6549568204353067", "test2.0.9354860568075689"],
  "res2length": 4,
  "reslength": 10004
}
//16th invocation
{
  "res2": ["test2.0.3702616045240217", "test2.0.8452456159763329", "test2.0.3062791872061441", "test2.0.568154399449698", "test2.0.41394382037542443", "test2.0.9946958458315607", "test2.0.8683097928544137", "test2.0.3330606626483712", "test2.0.7210368977674697", "test2.0.6549568204353067", "test2.0.39067038816595123", "test2.0.7398105862683666", "test2.0.9166607285572936", "test2.0.8826057412687409", "test2.0.9354860568075689", "test2.0.6802973389356854"],
  "res2length": 16,
  "reslength": 10016
}
// and so on..

I can also try with more keys if necessary (depending on your environment)

Hello again !
Thank you for your answer.
Here are my ".stats()" results, if it helps :
    "stats": {
        "bytesKeys": 12372560,
        "bytesValues": 91335241,
        "keys": 163587
    }

I tried your code and I have... no results. So I investigated : The lower is  the countHint, the higher is the chance to NOT retrieve my items. With countHint = 134, I have no result. With countHint = 1000 I have... some results XD.
Could you try with the same volumetry ? If it helps, I can give you (maybe in PM) the concerned environment ?
Thank you.
Damien.

Ok indeed those are way more keys, will give it a try, yes please share your environmental details with me too

@syno-dlr I may have reproduced the issue and may have found a way to fix this. I keep you updated.
Thanks again for raising the issue and sharing details!

a fix is on the way :)

@syno-dlr the fix has been deployed! could you kindly double check?

Hello !
It seems to work using your branch : chore/e2e-tests-list-improvements .
What do you mean by "fix has been deployed" ? It seems version of state is still 5.0.2.
When will it be available using a regular tag ?
Anyway, thank you so much.
Damien.

Hi @syno-dlr, sorry for the confusion. The fix has been deployed server-side, and no changes were needed in the library. So you should be able to use your current 5.0.2 version

Hey Damien can we close this? 🙏

Closing please re-open if the issue arises again

Hello. Sorry for being late to answer : I had to make a lot of tests.
It seems to work ! THANK YOU !!!


STONEBLD-857 Fix Kaml build

/test jvm-build-service-in-repo-apicurio-e2e

/test jvm-build-service-in-repo-apicurio-e2e

Kaml is fixed but graphql failed to resolve its contamination. Need to see if it was intermittent.

I feel this could be related to the checker-framework issue as well.


Roadmap Suggestions for 2.0.0

@pivovarit
For the near long term, I think the following would be (some of the) good goals (IMO) for a 1.0.0 release:

Minimum JDK 17
Take advantage of sealed classes in Java 17. Make Try and Option (and possibly others) sealed classes.
Take advantage of records. Make Try and Option implementations records. This could pave the way in the future of parameter matching on Some, Success, etc.

Others should feel free to chime in and add their thoughts on a roadmap to 1.0.0.

Personally, I would release v0.10.4 as v1.0.0 after a few rounds of bug fixing and improvements to seal the deal and signal that this is feature-complete. However, the next major release should definitely be JDK17-based if not JDK21.
However, I'm afraid you pinged the wrong person

Hey @EarthCitizen, thanks! Jumping on an actual long term release makes sense, that was also on my mind.
@pivovarit creating a 1.0.0 based on an actual version is a good suggestion and an important signal to the community.
I will elaborate on the roadmap along with a plan to have more project sponsors.
Regarding sponsorship, I will need to find companies and persons who are relying on Vavr in a long term manner.

@pivovarit Sorry. Based on your comments on another issue, I interpreted that as you would be one of the main people taking over :-)
After the current code base is released as 1.0.0, looking toward what's after that, I think it is too early to have a minimum JDK of 21. Spring Boot, for example, just switched to JDK 17 as the minimum.

Please, please with much sugar on the top ... release 1.0.0
I used vavr for many projects, but sadly the 0.10.4 version since having an -alpha in the version would be a huge downer in an code review. v1 is long overdue and would make acceptance in an project much easier. You can always release v1.0.1 if anything is missing. Nobody would be sad. The -alpha version has been out so long I would be confident that it's fine and could be released as -final.
Having java17 as an prerequisite would be an candidate for v1.1.x or v2.0.x imho.
And yes, j21 is too early.

Suggest triaging the open issues making sure they are labeled correctly as bug or not, and label the ones that should be fixed for a 1.0.0 release. I may be able to fix bugs that are prioritized.
It would be helpful to have at least one final release that works with JDK 8 since there are still a lot of projects that are stuck on that.

I agree with @pivovarit and @pertl and @ezoerner. Current code base should be released as 1.0.0, and my original suggestion of going to JDK 17 should be 2.0.0. My original thought was that 1.0.0 would be the new start, but it makes a lot of sense to release what exists as 1.0.0.

Renamed this issue to suggestions for 2.0.0.

I would not even bother with current open issues but just release v1.0.0 right now and release bug fixes in subsequent v1.0.x releases. The -alpha has been tested for so long it really can't be that wild.

v1.0.0 would probably be the right time to remove deprecations, e.g. "class $"


saved_models/bert-base-uncased-vocab.txt was not found

Hi, I have a problem like this when I run the command "bash run/train.bash". I have upgraded the transformers module to the latest version.
Does anyone help me with this problem?

because the transformers has been updated, you have to adjust the code in L-170 of model.py

Do you mean this line?
model_class, tokenizer_class, pretrained_weights = (ppb.BertModel, ppb.BertTokenizer, 'bert-base-uncased')
Do you have any advice? I have no idea about it. Thank you very much.

yes, you have to adjust this line, because bert-base-uncased-vocab.txt has
been deprecated.   You can use the transformers and corresponding
pre-trained Bert to replace them. please refer to
https://huggingface.co/bert-base-uncased
lttkien1511 @.***> 于2023年5月19日周五 01:46写道：

Do you mean this line?
model_class, tokenizer_class, pretrained_weights = (ppb.BertModel,
ppb.BertTokenizer, 'bert-base-uncased')
Do you have any advice? I have no idea about it. Thank you very much.
—
Reply to this email directly, view it on GitHub
https://github.com/Suo-Wei/SRCF/issues/5#issuecomment-1553405110, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APEAJ7GXLEYKUJKYRSFE62LXGZN63ANCNFSM6AAAAAAYF6JPYM
.
You are receiving this because you commented.Message ID:
@.***>

Hi, I still cannot fix this problem. I found that I couldn't find the saved_models directory in this project.
Moreover, I have added the line from transformers import BertTokenizer, BertModel and fix the line 170 in model.py into model_class, tokenizer_class, pretrained_weights = (BertModel, BertTokenizer, 'bert_weight/bert-base-uncased') but it still didn't work.

OK， maybe you can pip uninstall transformers and pip
install pytorch-pretrained-bert. And keep the original code.

lttkien1511 @.***> 于2023年5月21日周日 17:38写道：

Hi, I still cannot fix this problem. I found that I couldn't find the
saved_models directory in this project.
Moreover, I have added the line from transformers import BertTokenizer,
BertModel and fix the line 170 in model.py into model_class,
tokenizer_class, pretrained_weights = (BertModel, BertTokenizer,
'bert_weight/bert-base-uncased') but it still didn't work.
—
Reply to this email directly, view it on GitHub
https://github.com/Suo-Wei/SRCF/issues/5#issuecomment-1556131727, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APEAJ7D4K6UPEZRELPVGZVDXHHPAPANCNFSM6AAAAAAYF6JPYM
.
You are receiving this because you commented.Message ID:
@.***>

I have cloned your project and do again. And the problem is okay now.


About supported plugins in README

In the README, there is a section on supported plugins: https://github.com/Mofiqul/dracula.nvim?tab=readme-ov-file#-supported-plugins.
But it does not specify what I need to do to make the supported plugins work with dracula.nvim.
Thanks in advance.

Usually, supported plugins implies that highlight groups are provided by the colorscheme, not requiring any further action on your part. See the LSP Saga highlights for instance.
--LSP Saga
LspFloatWinNormal = { fg = colors.fg, },
LspFloatWinBorder = { fg = colors.comment, },
LspSagaHoverBorder = { fg = colors.comment, },
LspSagaSignatureHelpBorder = { fg = colors.comment, },
…

Understood. Thank you very much for your reply.


Please add a directive for Scrollspy like in bootstrap

Normally bootstrap has this Scrollspy feature which keeps track of the current page hash on the navbar. A scrollspy directive would be a welcome addition.
url: http://getbootstrap.com/javascript/#scrollspy

Closing issue becuase i solved my problem using ui-router.

@anubhav7495 may I ask how you solved this with ui-router?

when route would match /home, active class would be applied to the .
Hope this helps.


ISBN scanning feature not working. Camera permissions not working.

Someone mentioned this issue:

If I can scan ISBN that would ease my job. (That doesn't work on the Android app because of missing permissions).

It should be an easy fix, so I might fix it this weekend hopefully.

Ok.
This issue is very hard to fix.
I added all the permission stuff, but still it does not work.
I am not sure what to do.

Alright. The idea for now is to implement ISBN scanning in the app on itself. This would get around the current problems and it would enable ISBN scanning for instances that do not have it yet, because it would make it work from within the app.

I needed quite a lot of hours to get this working, but it finally works!
Fixed with commit be020bdfcd5a3a4ff4e8a2c57cb973b450fd2466


Remove "strict" option from open / close operations?

I am not sure how useful these options are, and think we should just adopt the tolerant behaviour (which is the default) in all cases.
This would be consistent with Python's file-like objects which are quite happy with being closed multiple times.
fp = open('bob.txt', 'w')
fp.close()
fp.close()

@mikeboers any thoughts on this?

My initial thought is I would prefer to go the other direction, but as long as there is a closed attribute (which is also what Python does with file) and any actual operations with the thing besides hitting close() raise exceptions, then I'm very happy to drop the strict in these cases.

To be clear: remove strict, but have public read-only closed attribute.


Create aws.yml

name: Amazon ECR "Login" Action for GitHub Actions
You may pin to the exact commit or the version.
uses: aws-actions/amazon-ecr-login@aaf69d68aa3fb14c1d5a6be9ac61fe15b48453a2
uses: aws-actions/amazon-ecr-login@v1
with:
A comma-delimited list of AWS account IDs that are associated with the ECR registries. If you do not specify a registry, the default ECR registry is assumed.
registries: # optional
Whether to skip explicit logout of the registries during post-job cleanup. Exists for backward compatibility on self-hosted runners. Not recommended.
skip-logout: # optional

.github/workflows/aws.yml


Could you keep the 'v1.0.0' interface?

I like the new interface. Really, I used the semaphore to control concurrency outside the bus.
And, I hope to keeps both the old interface and the new interface.

There is the code that depends on the old interface.
The new interface has a concern as performance is degraded. https://github.com/vardius/message-bus/blob/master/README.md#benchmark

v1.0.0 https://github.com/vardius/message-bus/blob/c1f01b61c37e8992775c53d6be6b61e362adfce2/bus.go#L82
v1.1.0 https://github.com/vardius/message-bus/blob/bdb2394d9af1cf4f226490d32a6cb4e8f6d36ab7/bus.go#L93
Ref: https://github.com/vardius/message-bus/commit/dd40db9f8e8a2cfe434fdc9381202827f851c931#diff-ecf9c6bcdc8d97b7f04226e8857c1108L82

Heh. I was going to suggest the opposite, that current interface stutters quite a bit. My concern is more aesthetic tho, as Go Stockholm Syndrome kicks in.

The main goal for v1.1.0 was to reduce the amount of goroutine spawns. By spawning goroutines on subscribe once and keeping them alive. In previous versions many goroutines where spawned each time publish method was called.
Also earlier the concurrency was limited on a global level meaning one queue per all handler of all topics. in v1.1.0 it is limited per topic. Each of topics has it's own queue.
I encourage you to contribute. I am sure together we can workout best performance interface. More use cases gives more insides on actual message-bus usability and performance.

@vardius Thanks for your reply.
I will think about your suggestion.
My use case that implements with your message-bus is this.
https://github.com/michilu/boilerplate/blob/173e4736f68c188a6300f4a87f8c3de276dddce6/v/bus/bus.go
I want to use a lightweight pub/sub.
Now I implement by channel via genny, like this.
https://github.com/michilu/boilerplate/blob/master/v/topic/topic.go
If you no problem, close this issue.

Would be good to know what is the opinion of other ppl as well.
As to your request we could add new constructor something like this
// NewAsync creates new MessageBus that always spawns goroutines
func NewAsync() MessageBus {
	return &messageBus{
		handlerQueueSize: runtime.NumCPU(),
		handlers:         make(handlersMap),
	}
}

which would create new bus with preset number of concurrent calls. maybe we could set it to -1 and then not use buffered channels but call handler directly ?
ideally we create strategy interface (async, sync) and based on that we use buffered channels ?
what do you think ?

I’m closing this issue because it has been inactive for a while. Please use the https://github.com/vardius/message-bus/releases/tag/v1.0.0 for v1.0.0 interface. Keep in mind that by using older release you loose recent bug fixes and futures.
Thank you!


Branch other itinerary commands

Codecov Report

Merging #184 into master will decrease coverage by 3.35%.
The diff coverage is 0.00%.

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


hey bud

bro, which extension, plguin, software do u use??

Hi @Guiflayrom
My TIL collection is basically a set of Markdown files, served via GitHub Pages (or directly), which is okay, but not as pretty.
I use the following tools:

VScode
Markdownlint

And GitHub Action

Spellcheck GitHub Action

For the GitHub Pages, which is implemented using Jekyll I use the following additions:

"jekyll-github-metadata"
'jemoji'

See the Gemfile
Their might be better ways, but I needed something basic and it works. I would love for it to be more wiki-like, but then again, it is just my notes, written primarily for myself.


Release v1.1.1

Release Notes
Another day, another release. These are the release notes for the version v1.1.1.

Will trigger a new release...


Update dockerfile to use supported image

Created by hand-patching the onbuild commands from the previous image to match modern Docker.
Tested this by running on GCP Cloud Run, not sure if there's a better path for testing.

Looks good to me. Thanks for the contribution!


FR: Switch direction

In visual mode (and in vim-visual-multi), it is possible to switch the direction of the selection by moving back.
This behavior is not possible, with multicursor.nvim I am "blocked" from going any further until I switch anchors with o.
https://github.com/smoka7/multicursors.nvim/assets/73286100/0262c4a1-ad7a-4ec4-b36c-16b019f459fb

At first I want it to implement it like this, but i couldn't replicate the behavior nicely.
I accept a PR for this, and help in the process when needed.


Align anonymous function handling against ES6/ES7

Currently an empty string .name is set on the function instance. Check ES6/ES7 behavior.

[x] Change anonymous function .name behavior to match ES6
[x] Change .name for Function constructor result
[x] Testcase for anonymous function name in ES6
[x] Testcase for new Function() .name
[x] Migration notes
[x] Releases entry

V8 behavior seems a bit odd:
> var anon = (1, 2, function () {});  // avoid automatic name
undefined
> Object.hasOwnProperty(anon, 'name');
false
> JSON.stringify(anon.name);
'""'
> Object.getPrototypeOf(anon) === Function.prototype
true
> JSON.stringify(Function.prototype.name);
'""'

So far so good: anon inherits from Function.prototype, doesn't have an own .name property, and the property lookup comes out as the empty string (same as for Function.prototype).
But then:
> Object.defineProperty(Function.prototype, 'name', { value: 'aiee' });
[Function: aiee]
> Function.prototype.name
'aiee'
> JSON.stringify(anon.name);
'""'

Setting the Function.prototype.name succeeds - but anon.name is still empty, even if it has no such own property and inherits directly from Function.prototype.

It's get a bit more weird:
> Object.hasOwnProperty(anon, 'name');
false
> Object.getOwnPropertyDescriptor(anon, 'name')
{ value: '',
  writable: false,
  enumerable: false,
  configurable: true }

Maybe there's a typo somewhere :)

If my test above is correct, this is probably V8 somehow "caching" the name so that a change to Function.prototype isn't effective, but the function instance still pretends it inherits the value from Function.prototype. But then, it returns a descriptor for Object.getOwnPropertyDescriptor() so maybe this approach is "leaking" a bit. Or maybe there's a bug in my test.

Deleted a few comments on weirdness I though I found in V8, but it actually seems anonymous function .name is a concrete own property in V8:
> var anon = (1, 2, function () {});
undefined
> anon.hasOwnProperty('name')
true

So, need to check if this is ES6/ES7 behavior. If so, current behavior is OK.

ES6 has this to say, right under the section for .name:

Anonymous functions objects that do not have a contextual name associated with them by this specification do not have a name own property but inherit the name property of %FunctionPrototype%.

Either this was changed in a later edition, or V8 is out of spec here.

That's how I quickly read it too, I'll re-read the relevant parts tonight. Function .name is operated from quite a few places.

Firefox also has an own .name property for anonymous functions. Time to check the ES2017 draft.

There's also this:
> x = new Function('')
[Function: anonymous]
> x.name
'anonymous'

That last one is backed up by ES6, at least:
ES6 Section <IP_ADDRESS>.1, step 29:
Perform SetFunctionName(F, "anonymous").

Yeah, that new Function(...) behavior is quite clearly specified in ES6 (also checked draft ES2017).
Just wanted to note it has been explicitly defined; it didn't use to be, and Duktape currently creates anonymous functions (with empty string name) in this case.

At work now, so just putting this here:
http://www.ecma-international.org/ecma-262/6.0/#sec-function-definitions-runtime-semantics-evaluation

That's the place where the actual steps indicating an anonymous function is supposed to miss a .name is apparent: for the case with a BindingIdentifier the SetFunctionName() specification function is called. For the anonymous case it's not called so it should remain unset.
The .length property is in both cases handled via FunctionCreate() -> FunctionInitialize() -> step 3 sets .length with attribute C (configurable, other flags unset).
Behavior in this pull should now match that outcome.

@fatcerberus I'll merge this tomorrow unless you come up with shortcomings :)

I checked the ES8 draft to be sure, and it has the same note as ES6:

Anonymous functions objects that do not have a contextual name associated with them by this specification do not have a name own property but inherit the name property of %FunctionPrototype%.

Runtime semantics for anonymous function expressions likewise do not seem to invoke SetFunctionName() (but those with a binding name of course do):
https://tc39.github.io/ecma262/#sec-function-definitions-runtime-semantics-evaluation
So it looks like the behavior in this pull is correct w.r.t. Ecmascript requirements.  So no complaints from me, merge away. :)


Bound PVs are selectable when creating volume for deployment

On master-head - commit id: 8d9cedd

On Dashboard --> Create Deployment --> Storage section --> Select Create PVC
Select Use an existing PV
In the dropdown you get a list of both "Bound" and "Available" persistent volumes.
Whereas in Ember UI, the dropdown will have the list of "Bound" PVs disabled.
When a user selects a bound PV and creates a PVC from it, PVC will be stuck in "Pending" state and the deployment/workload will error out.

Dashboard UI:

Ember UI:

On master-head - commit id: 33f755f180

Issue is not fixed

Ember UI

Dashboard UI

This issue should have been fixed when this issue was https://github.com/rancher/dashboard/issues/1460

On 2.5.0

On Dashboard --> Create Deployment --> Storage section --> Select Create PVC
Select Use an existing PV
The dropdown shows users ONLY list of PVs which are NOT bound.


terminology: adopt CMake, python, and Kconfig code to use qualifiers

Followup: #69905
Adopting new board terminology for CMake, python, and Kconfig code to use qualifiers instead of identifiers.
Also adjusted to board target where applicable.

samples/drivers/counter/maxim_ds3231/README.rst has boot banner, board identifier which can be updated also

doc/hardware/porting/board_porting.rst needs updating too

Missing update in scripts/snippets.py
samples/drivers/counter/maxim_ds3231/README.rst has boot banner, board identifier which can be updated also
doc/hardware/porting/board_porting.rst needs updating too

All updated.


Add GitHub CI

I'm putting this on hold because it's too complex to do right now because of our dependencies. This package depends on the mobipick and mobipick_labs repos, which bring in a slew of other dependencies, so we cannot efficiently test grasplan in CI right now.

Update: After #23 is merged, grasplan will no longer depend on mobipick_labs, only mobipick.

#23 is merged!


Suggestion: Start using semantic versions

It seem a that versoning doesn't follow semantic versoning as the versions go from 1.3.9 - > 1.4.0.
Please have a look at https://semver.org/ an use that so one knows what type of changes have happened by looking at the version number. It is totally ok to have version 1.1.34 if there have not been any breaking changes but looking at the change log for https://github.com/leeyuentuen/polestar_api/releases/tag/1.3.4 it seem that this should have a  bump in minor at it states:

note: some entities has been renames/removed

Really love the effort, keep up the good work!

i'll try to follow that rules on next release

i've done a different logic. 1.x was using to public release and the 1.1.x was using for beta patching that was not for public release.


Rewrite VMobject fill shaders

Changelog / Overview

Rewrite VMobject fill shaders to be compatible with projection matrices

Motivation

Rewrites VMobject fill shaders to be compatible with projection matrices, which makes it much easier to control their positioning.
Explanation for Changes

Adds a file vectorized_mobject_rendering.py, which contains functions to render vectorized mobjects using the algorithm described here. Also adds a --use_projection_fill_shaders flag to control when the new shaders are used.

Documentation Reference

Testing Status

Tested with the following scene using the --use_projection_fill_shaders flag:
class TextTest(Scene):
    def construct(self):
        import string
        text = OpenGLText(string.ascii_lowercase)
        text2 = OpenGLText(string.ascii_uppercase).next_to(text, DOWN)
        self.add(text, text2)
        self.interactive_embed()

Further Comments

The fill shaders may stop working if several (>5) mobjects overlap with each other. Fixing this will require dynamically generating the shader code (I think).
Checklist

[x] I have read the Contributing Guidelines
[x] I have written a descriptive PR title (see top of PR template for examples)
[x] I have written a changelog entry for the PR or deem it unnecessary
[x] My new functions/classes either have a docstring or are private
[ ] My new functions/classes have tests added and (optional) examples in the docs
[x] My new documentation builds, looks correctly formatted, and adds no additional build warnings

Reviewer Checklist

[ ] The PR title is descriptive enough
[ ] The PR is labeled correctly
[ ] The changelog entry is completed if necessary
[ ] Newly added functions/classes either have a docstring or are private
[ ] Newly added functions/classes have tests added and (optional) examples in the docs
[ ] Newly added documentation builds, looks correctly formatted, and adds no additional build warnings

The letters are not smooth especially on the edges and the proportions are also changed. Is that supposed to happen with this shader ?

Normal Render for reference

Yes, the sharper edges are because there's no antialiasing and the different proportions are because it's using a different method for projection.

FWIW, this is the output I get from your example scene:

on a MacBook Air with the M1 chip. Also, no need to use OpenGLText, Text produces the same output (and has been made compatible with OpenGL recently).
Given that the usage of the new shaders is optional, I'm fine with merging this whenever you'd like; I'm happy to supply further information for debugging as well.


Can't use SvelteKit $app stores in Stories

I'm trying to get a basic story working using SvelteKit + Storybook using the Vite builder. This story uses the  page store from$app/stores which is imported into the Nav.svelte file as below:
import { page } from "$app/stores";

In my .storybook/main.js file, I have this config including the alias for the $app
const preprocess = require("svelte-preprocess");
const autoprefixer = require("autoprefixer");
const path = require("path");
const { mergeConfig } = require("vite");

module.exports = {
  stories: [
    "../src/**/*.stories.mdx",
    "../src/**/*.stories.@(js|jsx|ts|tsx|svelte)",
  ],
  addons: [
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@storybook/addon-svelte-csf",
  ],
  framework: "@storybook/svelte",
  svelteOptions: {
    preprocess: preprocess({
      sourceMap: true,
      scss: {
        includePaths: ["src"],
        prependData: `@import 'src/styles/variables.scss';`,
      },
      postcss: {
        plugins: [autoprefixer()],
      },
      aliases: [["ts", "typescript"]],
    }),
  },
  core: {
    builder: "@storybook/builder-vite",
  },
  async viteFinal(config, { configType }) {
    config.resolve.alias = {
      $app: path.resolve("./.svelte-kit/runtime/app"),
    };
    console.log(config);
    return config;
  },
};

but when I try to view the Nav story, I get the below error
Cannot read properties of undefined (reading 'page')
TypeError: Cannot read properties of undefined (reading 'page')
    at getStores (http://localhost:6006/.svelte-kit/runtime/app/stores.js:23:22)
    at Object.subscribe (http://localhost:6006/.svelte-kit/runtime/app/stores.js:45:17)
    at subscribe (http://localhost:6006/node_modules/.vite-storybook/chunk-R7OMEHAZ.js?v=3466fb57:61:23)
    at component_subscribe (http://localhost:6006/node_modules/.vite-storybook/chunk-R7OMEHAZ.js?v=3466fb57:70:32)
    at instance (http://localhost:6006/src/components/Nav/Nav.svelte:121:2)
    at init (http://localhost:6006/node_modules/.vite-storybook/chunk-R7OMEHAZ.js?v=3466fb57:1686:23)
    at new Nav (http://localhost:6006/src/components/Nav/Nav.svelte:137:3)
    at createProxiedComponent (http://localhost:6006/node_modules/svelte-hmr/runtime/svelte-hooks.js:266:9)
    at new ProxyComponent (http://localhost:6006/node_modules/svelte-hmr/runtime/proxy.js:239:20)
    at new Proxy<Nav> (http://localhost:6006/node_modules/svelte-hmr/runtime/proxy.js:346:11)

Has anyone been able to successfully set an alias to the $app/stores?

Here you go https://github.com/kyleshepherd/svelte-kit-storybook, any issues lemme know!

Thanks @kyleshepherd.  I'm trying it out, but when I run npm run storybook after installing deps, I'm seeing this in the browser console:
:6006/.svelte-kit/runtime/app/stores:1          Failed to load resource: the server responded with a status of 404 (Not Found)

Am I missing a step?

Oh, it seems I need to also be running npm run dev, I guess.

So, it seems the import resolution itself is working fine, because if I remove the uses of $page in the component, and just log out the import, it resolves correctly.  However, and this is where my svelte (and especially svelteKit) knowledge fails me, The $page is failing.  I'm not sure exactly what that's doing, but it seems to be trying to take the Readable page, and I guess read from it, and that part is failing.  Does that give you anything to go off of?
Another thing to try, does this work correctly when using webpack?  I wasn't able to with poking at it for a few minutes, but that would be interesting to narrow down where the error is happening.
One more small tip, you can use svelteOptions: import("../svelte.config.js").preprocess,, rather than re-creating the config in the main.js.

I did try it with Webpack but was getting a similar error.
I'll try and do some more digging now knowing that the alias is working itself and see if I can figure anything out. Thank you for looking into it!

The problem is neither storybook nor vite/webpack directly. Sveltekit is simply prefilling some vars per request and that step is missing on those simple aliasing-setups. One solution can be adapted from this: https://github.com/nickbreaton/vitest-svelte-kit/blob/master/packages/vitest-svelte-kit/src/plugins/kit-module-emulator.ts

I'm going to close this out since it doesn't sound like a builder-vite bug, but please report back @kyleshepherd if you think it is, or if you find a good solution that you think might be useful to others.

The problem is neither storybook nor vite/webpack directly. Sveltekit is simply prefilling some vars per request and that step is missing on those simple aliasing-setups. One solution can be adapted from this: https://github.com/nickbreaton/vitest-svelte-kit/blob/master/packages/vitest-svelte-kit/src/plugins/kit-module-emulator.ts

Hey @benbender, thanks for this. Do you happen to know any way to implement that? I can't find how to connect the dots between sveltekit, storybook and vite

Cc @JReinhold

@hugotox have you checked out https://github.com/storybookjs/storybook/blob/next/code%2Fframeworks%2Fsveltekit%2FREADME.md ?
Note that it requires Storybook 7.0, and we even recently made more improvements to the SvelteKit integration so I'd suggest you upgrade to the latest Storybook version 7.6.6 before moving forward. npx storybook@latest upgrade
Do you need anything else not covered in the current functionality?

@JReinhold yes I have! The upgrade to storybook 7.6.6 worked, but it broke my main.js file
SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: ./.storybook/main.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset<EMAIL_ADDRESS>
Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

/Users/hugo/Projects/stickmonkey/node_modules/@storybook/addon-svelte-csf/dist/components/Meta.svelte:1
<script>
^

SyntaxError: Unexpected token '<'
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1178:20)
    at Module._compile (node:internal/modules/cjs/loader:1220:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Object.newLoader (/Users/hugo/Projects/stickmonkey/node_modules/esbuild-register/dist/node.js:2262:9)
    at extensions..js (/Users/hugo/Projects/stickmonkey/node_modules/esbuild-register/dist/node.js:4838:24)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:119:18)
    at loadPreset (/Users/hugo/Projects/stickmonkey/node_modules/@storybook/core-common/dist/index.js:15:82)

If I revert the main.js back, storybook works again, but still the $page store is undefined.
For reference, the main.js was changed to
import { dirname, join } from "path";
/** @type { import('@storybook/svelte-vite').StorybookConfig } */
const config = {
  stories: ['../src/**/*.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx|svelte)'],
  addons: [
    getAbsolutePath("@storybook/addon-svelte-csf"),
    getAbsolutePath("@storybook/addon-links"),
    getAbsolutePath("@storybook/addon-essentials"),
    getAbsolutePath("@storybook/addon-interactions"),
    getAbsolutePath("@storybook/addon-styling"),
    getAbsolutePath("@storybook/addon-storysource"),
  ],
  framework: {
    name: getAbsolutePath("@storybook/sveltekit"),
    options: {},
  },
  docs: {
    autodocs: 'tag',
  },
}
export default config

function getAbsolutePath(value) {
  return dirname(require.resolve(join(value, "package.json")));
}

And to make it work, I reverted it back to:
/** @type { import('@storybook/svelte-vite').StorybookConfig } */
const config = {
  stories: ['../src/**/*.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx|svelte)'],
  addons: [
    '@storybook/addon-svelte-csf',
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/addon-interactions',
    '@storybook/addon-styling',
    '@storybook/addon-storysource',
  ],
  framework: {
    name: '@storybook/sveltekit',
    options: {},
  },
  docs: {
    autodocs: 'tag',
  },
}
export default config

@hugotox your issue sounds related to https://github.com/storybookjs/addon-svelte-csf/issues/160#issue-2008996585 . Resolving dependencies in monorepos is hard, thanks for reporting the workaround - I don't think there's any wrong with your solution.
Sounds like your issue is resolved then. FYI if you need to, you should also be able to mock the stores on a per-story basis by setting the parameters on the Story component directly.

Yes, it seems to work. I tested it here.
It seems to work now that you just have to remove getAbsolutePath. The workspace can stay.


feat: use branch_route_id for headways metrics

We updated the vehicle_trips table to have branch_route_id but were not using the field to calculate headways.
This change updates the metrics calculation business logic to use branch_route_id for headways calculations.
Asana Task: https://app.asana.com/0/1204517240145658/1204572061960311

this all checks out.
🍰 LGTM


Can't connect to coinbase

Hi, I'm new to this and not able to retrieve data from coinbase. I did all the steps and was able to build the project but when I ran the demoTradingCore it shows "++ ATENTION: COINBASE DISCONNECTED or NO DATA...". I can't find where to change the api keys if that's the issue. Please let me know what I'm doing wrong.

You will need to debug and see what's the real reason.


allow single precision operation in the cupyx.scipy.ndimage module

allow single-precision computations in cupyx.scipy.ndimage
I opened this PR to discuss the potential for performing computations in single precision in cupyx.scipy.ndimage functions when the input is single precision. Currently, the internal weights arrays used in the convolution function, etc. are always np.float64, which does match the internal use of double precision in scipy.ndimage. However, to improve performance and reduce memory usage, it would be preferable to use single precision for the computations when possible.
A similar exception was made previously for cupy.fft where inputs are NOT automatically promoted to double precision as in NumPy.
I see three ways this can potentially be done (I am willing to make the necessary changes, but need to know what approach would be preferred).

automatically promote types to at least float32 via: cp.promote_types(image, cupy.float32) instead of just using cupy.float64 everywhere  (e.g. for the weights arrays in convolution)
leave the default internal floating point type float64, unless a boolean keyword-only argument (e.g. allow_float32) is specified
add a global cupy configuration variable to control whether single-precision computation is allowed within the cupyx.scipy.ndimage module

related issue: complex dtype support
A separate consideration is adding support for complex-valued inputs. I have open PRs for this in SciPy for the filtering and interpolation functions (scipy/scipy#12725 and scipy/scipy#12812). Hopefully those will be merged for SciPy 1.6.0 and then we can revisit adding complex support here.
cc: @jakirkham, @quasiben

There was some related previous discussion during the review of #2483.

I just realized that I had actually implemented the allow_float32 keyword-only argument in #4145 which was just merged. If one of the other approaches above is preferred instead then we should change that prior to making a new release that includes this.

If we are able to use the dtypes of the array(s) provided, that would be good.
Do you know if there's an equivalent issue raised for SciPy?

I don't think there is an equivalent issue related to single-precision open on SciPy. For SciPy itself, I think the argument is less compelling because the amount of work required would be substantial and the performance benefits of single precision may not be substantial.
As an example, many C functions copy lines to buffers that are double precision and the temporary variable holding the convolution result is double, etc. Adding templating would make the source C code harder to read and a rewrite to templated C++ would be a lot of work.
On the CuPy side the kernel C++ code is generated on the fly, so it is minimal effort to support single and/or complex dtypes as well.

If we are able to use the dtypes of the array(s) provided, that would be good.

I think I am leaning toward that as well and that is what cupy.fft currently does

I don't think there is an equivalent issue related to single-precision open on SciPy. For SciPy itself, I think the argument is less compelling because the amount of work required would be substantial and the performance benefits of single precision may not be substantial.

Ah right. Sorry forgot this.
It may still be worth adding an issue even if it is closed out as unfeasible or lingerings for time. At least that will make this issue more visible to others who may care about the performance improvement.

I believe whenever there's opportunity to use fewer bits for speedup, we should try to allow it!

Can we close this as #4314 got merged?

Can we close this as #4314 got merged?


[QUESTION] Interface name has changed after removal of NIC

I removed a NIC from the server and the other NIC's interface name have changed, leading to me losing connection to the UI since the Harvester Bond now points to an interface that does not exist anymore. How can I change the interface of the bond, since no modifications I do to the system persist after reboot?

To make the config persist across reboots, you have to update /oem/99_custom.yaml. Look for the following content in the file:
    ...
    - path: /etc/sysconfig/network/ifcfg-harvester-mgmt
      permissions: 384
      owner: 0
      group: 0
      content: |+
        STARTMODE='onboot'
        BONDING_MASTER='yes'
        BOOTPROTO='dhcp'
        BONDING_SLAVE_0='enp9s0'
        BONDING_MODULE_OPTS='miimon=100 mode=balance-tlb '
        DHCLIENT_SET_DEFAULT_ROUTE='yes'
      encoding: ""
      ownerstring: ""
    - path: /etc/sysconfig/network/ifcfg-enp9s0
      permissions: 384
      owner: 0
      group: 0
      content: |
        STARTMODE='hotplug'
        BOOTPROTO='none'
      encoding: ""
      ownerstring: ""
    ...

The content here will create the ifcfg files for interfaces harvester-mgmt and enp9s0. Let's say your NIC has been renamed to enp7s0, then you would have to replace the two enp9s0 here with enp7s0.


Add Meetup

Description
Adds icon for Meetup

Type of change

:x: Bug fix (non-breaking change which fixes an issue)
:white_check_mark: Icon addition (non-breaking change that adds/modifies Lawnicons's icons)
:x: General change (non-breaking change that doesn't fit the above categories like copyediting)

Icons addition information

Icons added

App Name (com.meetup)

Hm I thought I accepted incoming changes... Don't know why there are so many changes


9.9.0 SQL Console throws 404-Not Found console error

Description of bug
Provide a clear and concise description of the bug.
SQL Console does not display data entry field and produces console error
Steps to reproduce
List the precise steps to reproduce the bug:

Configure IIS with DNN files located in C:\DotNetNuke\Website
Login as Host
Go to 'Settings, SQL Console'
Notice there is no number 1 displayed and no place to start typing in the SQL code.
See error in browser console.

Current behavior
Explain the current behavior.
Cannot type into SQL Console
Expected behavior
Provide a clear and concise description of the expected behavior.
Should be able to type into SQL Console
Screenshots
If applicable, provide screenshots to help explain the bug.

Error information
Provide any error information (console errors, error logs, etc.) related to this bug.
Please see console errors in first image, above. Also see next section.
Additional context
Provide any additional context that may be helpful in understanding and/or resolving the bug.
URLs are wrong. This is what is being used:
Requested URL	   http://localhost:80/Resources/Shared/components/MonacoEditor/loader.js
Physical Path	   C:\inetpub\wwwroot\Resources\Shared\components\MonacoEditor\loader.js

Should be:
Requested URL	   http://localhost:80/DotNetNuke/Resources/Shared/components/MonacoEditor/loader.js
Physical Path	   C:\DotNetNuke\Website\Resources\Shared\components\MonacoEditor\loader.js

Second error produced by this wrong URL:
Requested URL	   http://localhost:80/Resources/Shared/components/MonacoEditor/editor/editor.main.js?cdv=1574
Physical Path	   C:\inetpub\wwwroot\Resources\Shared\components\MonacoEditor\editor\editor.main.js

Should be:
Requested URL	   http://localhost:80/DotNetNuke/Resources/Shared/components/MonacoEditor/editor/editor.main.js?cdv=1574
Physical Path	   C:\DotNetNuke\Website\Resources\Shared\components\MonacoEditor\editor\editor.main.js

Affected version

[ ] 10.00.00 alpha build
[X] 09.09.00 latest supported release

Affected browser

[X] Chrome
[X] Firefox
[ ] Safari
[ ] Internet Explorer 11
[ ] Microsoft Edge (Classic)
[ ] Microsoft Edge Chromium

Thanks for this bug report!
This issue is a duplicate of #4411 (the current integration of the Monaco editor does not support DNN when deployed to a folder).

Whoops, I missed that one. Sorry for the duplicate.

Closing this one in favor of #4411


removed left shift of raw data

Changing to right allignment was not a good idea: saturation detection does not work anymore. It seems there is nothing in FITS that tells how many bits are used and what the maximum pixel value is.
Reverting these changes!


util(ticdc): remove capture addr from context

What problem does this PR solve?

Issue Number: close #9157
What is changed and how it works?
remove capture addr from context, ref the capture addr from global configuration
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/merge

/retest-required

/retest-required

/test verify

/test verify


Cannot connect to remote (docker) kernel using SSH

I guess you figured it out that you need to match the Spyder and Spyder-kernels versions for a successful connection to take place. But just in case, I wanted to let you know that.

I guess you figured it out that you need to match the Spyder and Spyder-kernels versions for a successful connection to take place. But just in case, I wanted to let you know that.

HI, I'm also trying to use Spyder in a Docker container. When you say "match the Spyder and Spyder-kernels versions", do you mean all four packages (2 on remote, 2 on local) need to be the same version? Or is there a specific pair?


BUG: CountByHashAndRangeKeyQuery and CountByHashKeyQuery

DynamoDBMapper don't support: dynamoDBMapper.load(Long.class, hashKey,rangeKey) or dynamoDBMapper.load(Long.class, hashKey)
If we call CountByHashKeyQuery.getSingleResult() or CountByHashAndRangeKeyQuery.getSingleResult(), we will meet error:
Exception in thread "main" com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMappingException: Failed to instantiate class
at com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapper.createKeyObject(DynamoDBMapper.java:495)
at com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapper.load(DynamoDBMapper.java:483)
at jp.recochoku.push.common.aws.dynamodb.MultiServiceDynamoDBTemplate.load(MultiServiceDynamoDBTemplate.java:339)
at org.socialsignin.spring.data.dynamodb.query.CountByHashAndRangeKeyQuery.getSingleResult(CountByHashAndRangeKeyQuery.java:36)
at org.socialsignin.spring.data.dynamodb.query.CountByHashAndRangeKeyQuery.getSingleResult(CountByHashAndRangeKeyQuery.java:23)

I'm afraid I don't have enough information to look into this - I can't tell from this stack trace what your use case is.
Looks like a problem instantiate your hash key class - could you provide details of your hash key class?
What is the use case here? - when does this error occur?
Also, I see a class in the stack trace I don't recognise - what is the MultiServiceDynamoDBTemplate class?
Thanks,
Michael

@michaellavelle I'm sorry that I didn't provide enough information about this bug.
Thank you very much because create great project!
It help me very much in real product!
I create a project to describe this bug.
Link: https://drive.google.com/file/d/0B_CjEBcszSIBd2RmczJOeXZKeTA/view?usp=sharing
To see this bug, just modify some fields relate with DynamoD AWS in class:  org.spring.data.dynamodb.bug.main.Main
Thanks,
Minh Quan

Hi - could you please share the project on GitHub instead of a link to a zip file.?
Thanks,
Michael

I'm sorry to bother you!
This is project on GitHub: https://github.com/wanmifam/springdata-dynamoDB-bug
Thank you for your kind patience and understanding! :)

Thank you for raising this - there was a bug with this use case - really appreciate you bringing it to my attention.
I've fixed the issue in the latest snapshot build (1.0.2-SNAPSHOT) - this build requires a later version of aws-sdk (1.9.25) than you are using.
The issue happened when counting resultsets for PagedQueries when the primary key is specified, such as threadRepository.findByForumNameAndSubject.
I see in your example that you are calling this method, and you have this annotated with @EnableScan.
Just wanted to say that if you are specifying both ForumName and Subject ( both parts of the primary key), you would be able to change this to
threadRepository.findOne(threadId);
where threadId has the forumName and subject set.
This way you would not need to @EnableScan for this query, as you are searching by primary key.
Hope this helps - thanks again.
Michael

Thank you for your help!
It help me a lot of! :+1:
Some time we use reflection to mapping attribute name with method name, so the method findOne(primaryKey) don't use in this case. Whatever I love your project, It help me a lot of (about DynamoDB and Spring Data technology)!
We applied Spring Data DynamoDB in our real product, and our customer's very satisfy!
Again Thank you so much for your beautiful project!
Best regards,
Minh Quan.

You're welcome - thanks for your interest in the project - glad it's helped you.
Cheers,
Michael


Refactor T2HahnBackend to use qiskit-aer

Summary
This commit refactors T2HahnBackend to use qiskit-aer for improved performance.
Details and comments
The T2 tests were quite slow, taking around 149 seconds of run time in testing. T2HahnBackend was doing a form of simple Monte Carlo simulation, stepping through each circuit and flipping the qubit based on error probabilities. This behavior scales linearly with number of shots which is not good when running 1000 shots on around 100 circuits for each test. This commit switches T2HahnBackend to use AerSimulator which simulates each circuit only one time to determine the final output probability. It can then produce as many shot results as needed quickly by sampling from this distribution.
With the switch to AerSimulator, the run time of the T2 tests dropped from 149 seconds to 12 seconds. The simulation speed up was more significant than that because the test time is now not limited by simulation (simulation is around 0.5 seconds now).

Waiting for #1042. If that one won't be reviewed quickly, we could ignore the issues pylint is flagging.

Comment moved out of the PR description since it shouldn't end up in the commit message:
Since T2HahnBackend is used in a tutorial, I tried to maintain its previous API (otherwise, the class could be a bit simpler by being less flexible about the arguments it accepts). I did make slight changes which I put in a release note (you can't pass a single element list for a parameter when simulating multiple qubits, only a bare float or a list matching the number of qubits; if you pass only float parameters, you must pass the number of qubits; we could relax these conditions at the expense of more code checking and reformatting the inputs but it didn't seem worth it to me).
I have not done that much with qiskit-aer. There might be a different way to set up the simulator without adding the extra transpiler passes for preparation error and qubit frequency drift.

@yaelbh Your comments were straightforward, but I went a little further. Do you want to check my new changes?


Fix #985

It fixes #985

Thank you for your PR! I fixed the issue in https://github.com/vuejs/vue-devtools/commit/173a5088f0cb78f15f808a1571ab1c50cf41ec10


Change nomenclature of processing steps

Until now, every public endpoint (ie /splits) was associated with one job and one type of cache entry. But that’s no more the case:

the response can be computed using two concurrent methods (streaming vs normal, for example), and the first successful response is returned
the response can be computed at config level (/split-names) then aggregated at dataset level

It’s the occasion to rethink a bit the name of the steps, job types and cache kinds.
For now, every processing step has only one associated job type and cache kind, so we use the same for these three. But it’s no more related to the public API endpoint.

First change: remove the initial slash (/step → step)
Second change: to make it easier to think about, we can include the “level” at which the response is computed in the name of the step (step → dataset-step)

With these rules, after renaming and implementing some pending issues (https://github.com/huggingface/datasets-server/issues/735) we would end with the following set of processing steps and public endpoints:

Public endpoint
Dataset-level steps
Config-level steps
Split-level steps

dataset-config-names

/splits
dataset-split-names
config-split-names-from-streaming, config-split-names-from-dataset-info

/first-rows

split-first-rows-from-streaming, split-first-rows-from-parquet

config-parquet-and-dataset-info

/parquet
dataset-parquet
config-parquet

/dataset-info
dataset-dataset-info
config-dataset-info

/sizes
dataset-sizes
config-sizes

Also: every cached response would be accessible through: /admin/cache/[step name], e.g. /admin/cache/config-parquet-and-dataset-info?dataset=x&config=y

As discussed in #926 we didn't use the -- convention

While implementing config-level dataset-info we named the steps config-info and dataset-info (instead of config-dataset-info and dataset-dataset-info). As @severo suggested here we should also rename parquet-and-dataset-info to parquet-and-info. Should we do the same for split-names-from-dataset-info? @severo @AndreaFrancis @lhoestq
Also for future reference - runners steps are now places under directories of their levels, like:
config/
   info.py
   parquet.py
   size.py
   ...
dataset/
   info.py
   parquet.py
   size.py
   ...
split/
   ...

Yes.
For parquet-and-dataset-info, it's still only dataset-level, and converting it to config level is still a pending task (the last one, I think).
For split-names-from-dataset-info, yes, we should move it to the directories

what's left here:

[ ] remove /parquet-and-dataset-info step
[ ] convert /config-names step to dataset-config-names
[ ] remove /parquet-and-dataset-info endpoint

I can work on these

and maybe rename /dataset-info endpoint to /info?

yes, why not

still work remaining

I think we're done, thanks to @AndreaFrancis and @polinaeterna!!!!


dropdown-menu caret positioning calculations are off

When using this plugin in my app, the menu with suggestions end up in random places on the screen, so it seems like the caret calculations are off. I was able to do it on the demo page too.

Maybe Caret.js could help? (http://ichord.github.io/Caret.js/)

Got the same error on my pages.. But when i go to the Demo page, the problem seems to not be present on the demo page.. Can you explain us why ?

@p4d It strongly depends on your project, I cannot explain why it happens.

Ok, it seems you are right.. I did not found any common point between your demo and my code on my example.. I'm gonna try to integrate caretjs and then use it inside your plugin in order to make it find size clean wether the conditions are different or not. I'll try to update it if it works.

@p4d I'm writing v2. The version uses external core module: yuku-t/textcomplete [demo]. It already using caretjs.
If you don't care lack of IE8 support, you can use it.

Now v1.2.2 is released, which uses textarea-caret npm package. please use the new version.


Update http4s-client, http4s-dsl, ... to 0.21.2

Updates

org.http4s:http4s-client
org.http4s:http4s-dsl
org.http4s:http4s-okhttp-client

from 0.21.0 to 0.21.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Codecov Report

Merging #81 into master will not change coverage by %.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #81   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          24      24
  Lines         229     229
  Branches        7       7
======================================
  Misses        229     229

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 087542a...d79c1fe. Read the comment docs.

Waiting on a fix for http4s/http4s#3293 to be released before updating this.


Update readme for installation option

This PR aims at changing the Readme to provide links to install via docker as reported in the wiki and to replace the VM install with the windows subsystem for linux one.

@lrouhier any update on this?

Sorry it feel through the crack. I just checked it out I should be able to ask for a review in an hour or so (just confirming something with the install process). It still needs a few modifications. I am on it.

I think its good. I modify the order because I suspect most users having 'unsupported OS' are windows users.

I think it's good if you want to merge.


Vc-1.3.3 with GCC 7.3.0 fails SSE/AVX abi tests

Vc version / revision
Operating System
Compiler & Version
Compiler Flags
Assembler & Version
CPU

1.3.3
Gentoo Linux
GCC 7.3.0

Hi Matthias,
I package Vc for Gentoo Linux, and the CI system there has identified some test failures with Vc-1.3.3 when compiling with GCC 7.3.0. The bug report is at https://bugs.gentoo.org/647988, and the log file with the errors can be seen at https://647988.bugs.gentoo.org/attachment.cgi?id=519982. Here is a summary of the system:
=================================================================
                         System Settings
=================================================================
System uname<EMAIL_ADDRESS>KiB Mem:    65383088 total,  18105392 free
KiB Swap:   67108860 total,  67090172 free
Timestamp of repository gentoo: Sun, 18 Feb 2018 02:06:27 +0000
sh bash 4.4_p19
ld GNU ld (Gentoo 2.29.1 p3) 2.29.1
app-shells/bash:          4.4_p19::gentoo
dev-java/java-config:     2.2.0-r3::gentoo
dev-lang/perl:            5.26.1-r1::gentoo
dev-lang/python:          2.7.14-r1::gentoo, 3.5.4-r1::gentoo
dev-util/cmake:           3.10.2::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.4.1-r2::gentoo
sys-apps/openrc:          0.34.11::gentoo
sys-apps/sandbox:         2.12::gentoo
sys-devel/autoconf:       2.69-r4::gentoo
sys-devel/automake:       1.9.6-r4::gentoo, 1.15.1-r1::gentoo
sys-devel/binutils:       2.29.1-r1::gentoo, 2.30::gentoo
sys-devel/gcc:            7.3.0::gentoo
sys-devel/gcc-config:     1.9.1::gentoo
sys-devel/libtool:        2.4.6-r4::gentoo
sys-devel/make:           4.2.1-r1::gentoo
sys-kernel/linux-headers: 4.15::gentoo (virtual/os-headers)
sys-libs/glibc:           2.27-r1::gentoo

and the list of tests that failed:
96% tests passed, 4 tests failed out of 109

Label Time Summary:
AVX       =  18.62 sec*proc (37 tests)
AVX2      =   0.02 sec*proc (1 test)
SSE       =  18.97 sec*proc (40 tests)
Scalar    =  21.83 sec*proc (28 tests)
other     =   0.01 sec*proc (3 tests)

Total Test time (real) =  59.55 sec

The following tests FAILED:
	101 - test_abi_SSE (Failed)
	102 - test_abi_SSE_AVX (Failed)
	103 - test_abi_AVX (Failed)
	104 - test_abi_AVX2 (Failed)
Errors while running CTest

Cheers,
—Guilherme

I have not been able to reproduce it locally, though I've seen failures on Travis. This is bad (unless the test itself fails and the codegen is fine).

Does your system compiler imply additional compiler flags that may change code gen (e.g. stack protection)?

Hi Matthias, the Gentoo bug should have all this information. If anything is missing, please ask there and Toralf can clarify. I am not in control of the tinderbox system. Thanks.

According to https://647988.bugs.gentoo.org/attachment.cgi?id=519990, the (normally one instruction) function has an active stack protector. I.e. GCC compiles as if -fstack-protector-all were specified (it isn't). That's just crazy and I'm not sure how to support it. In any case, Vc works fine on the system (false positive). The code that inspects the generated assembly isn't able to cope with stack protector code.

See here: https://godbolt.org/g/vj3FYb

-fstack-protector-all should not lead to false negatives anymore now. I rewrote the test completely and found a minor performance issue that way.


Implement processing of all-age data

currently only the option exclude_age1=True is implemented
did Chu implement the option to include all ages?
consider changing the option name to allow selecting adult and/or age-1

See #91 for some previous info from @b-reyes.
@emiliom : Do you know if all-age processing was implemented in Matlab? (this is why I "assigned" this to you, not to ask you to implement the functions).

I know we absolutely need processing of age-1 data, but I'm not exactly sure what kind of processing Chu was doing with the age-1 in his latest version.   I know his code produces different numbers with age-1 =TRUE and not true.  I also know Chu was working on a few different implementations of age-1, and I'm not sure what is in his latest code.

Notes from 2024/01/29 meeting:
Age binning:

include age-1 in strata, but kick them out before kriging
should not include age-0
current estimate is age-2 only, trying to move to include age-1
age-1 has very different net selectivity

Temp decision:

age-0 and age-1 should be in their own bins
so have age-0 / age-1 / age-2+
But what do we include for the total number of fish? TBD

@brandynlucca -- could you comment on what the implemented handling is at the moment and point to the code section? to help us get back to this context quickly when we circle back to this, in the hopefully not very distant future!

This issue is now resolved. In the 2024/01/29 meeting we also discussed this along with the bug in #42.

I accidentally closed the wrong issue! Re-opening this.

The argument exclude_age1 has been added to transect_analysis(...) that selects the correct NASC data source depending on if exclude_age1 = True (i.e. adult-only while accounting for leaked age-1 contributions) and exclude_age1 = False (i.e. everything gets accounted for). This argument then propagates into other parts of the analysis without requiring any additional input (i.e. stratified_analysis(...) and kriging_analysis(...)).
The apportionment step is independent of this decision and is determined based on the original biological data. The primary change induced by exclude_age1 is 1) which NASC data to use and 2) whether kriged population estimates (e.g. biomass) apportioned by age and length need to be further reapportioned to remove contributions of age-1 fish.
This can be closed once PR #241 is merged.


Hierarchical SLDS not implemented

Hi! I just noticed that the SLDS class doesn't seem to support hierarchical parameters anymore. Is this on purpose?
If yes, I think __init__ taking the arguments hierarchical_transition_tags, hierarchical_dynamics_tags, hierarchical_emission_tags is a bit misleading and could be removed. I thought I was fitting a hierarchical model by specifying them but then saw that they're not actually used.
If not, could this functionality be restored by borrowing code from HMM.__init__ or would it be much more complex than that?

Hi @bagibence, thanks for pointing this out. We're not really supporting hierarchical LDS and SLDS at the moment, and should strip out those arguments. I think implementing them in a way that is reasonably well-performing (in terms of speed) would be fairly involved, since it would likely require writing custom M-steps. For now, I'm going to take out those arguments so things aren't so confusing!

Removed unused args in e487a65. Moving to "enhancement" since this would be a nice feature.

Hello! Is there any follow-up on this topic? I'm currently working with a LDS that has Bernoulli emissions and AR dynamics and I'm very interested to implement a hierarchical extension for both levels. I found some code in one of the branches for a hierarchical AR: https://github.com/lindermanlab/ssm/blob/e97ea4f0904cd204f392c2cfc4528ef860d71f9d/ssm/hierarchical.py
Is it possible to apply the same structure to implement a hierarchical version for Bernoulli emissions? Or does this require additional custom code for eg the M-steps?


fix: updated Readme.md

Going through the Readme was a bit ambitious, I have added few details which will make reading less ambitious

Thanks for the proposal, but I am planing to leave it as is right now.


[WIP] Add support for generating README.md data

This adds support for generating a readme.json file which will be consumed by Fern's remote generation service. Right now, the readme.json file will only be produced when the configured output is a GitHub repository and has a valid NPM package configuration (i.e. a significant portion of the README.md references the NPM package identifier).

Still a WIP - I need to resolve the rootClientClassName and pass it into the readme generator and actually verify the readme.json takes on the form we want.

Will need to refactor this a bit - the remaining functionality we need is found in the SdkRootClientClassDeclarationReferencer (via getExportedName) defined in the @fern-typescript/sdk-generator module.
The readme.json generation should only take place with GitHhub+NPM publish targets, so it usually makes sense to place it alongside the .github/workflows/... generation, which exists in the AbstractGeneratorCli.ts, but importing the @fern-typescript/sdk-generator from the @fern-typescript/abstract-generator-cli module doesn't feel right.
Few options:

Move the implementation to the {Simple,Bundled}TypescriptProject classes (alongside .gitignore, etc.)
Reproduce some of the logic required to resolve the rootClientClassName from AbstractGeneratorCli.ts.
Move this feature into the SdkGenerator

It probably makes most sense to move this into the {Simple,Bundled}TypescriptProject classes - we'll just need to add in some more conditional behavior there.

This is far out-of-date - we'll follow-up with this feature in another PR later on!


useSimplebar return type is wrong

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[ x] bug report

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
The useSimplebar hook definition is wrong

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?
the return type of the useSimplebar hook should be Ref<Simplebar> not just Simplebar as per https://github.com/wopehq/simplebar-vue3/blob/main/src/lib.d.ts#L26 file

What is the motivation / use case for changing the behavior?

Please tell us about your environment:
it shouldn't matter

Thanks, I will update it soon.

Fixed https://github.com/wopehq/simplebar-vue3/pull/5


Count RUSTC_BOOTSTRAP as nightly for tests

Rustdoc will count this as nightly, so cargo should too. This allows
running nightly-only tests without having to rebuild all 175
dependencies.

r? @Eh2406
(rust_highfive has picked a reviewer for you, use r? to override)

I would personally prefer to not do this. I don't think we should be encouraging usage of RUSTC_BOOTSTRAP really

The alternative is that people are forced to rebuild all the dependencies :/ that takes like 3 minutes on my laptop, which is really frustrating when I just want to run the tests.
Maybe cargo could introduce a new variable that forces running nightly tests as stable? Then it would be CARGO_FORCE_NIGHTLY=1 RUSTC_BOOTSTRAP=1 which seems a little silly to me but at least doesn't encourage RUSTC_BOOTSTRAP.

RUSTC_BOOTSTRAP implies you're running the nightly-only tests on a beta or stable toolchain which isn't guaranteed to work anyway (AFAIK), e.g., the feature may have changed since then. Is there a reason you're trying to do that?

I was using this because rustdoc-map is nightly-only, but hasn't changed in the last two release cycles.

I understand that nothing with RUSTC_BOOTSTRAP is supported, and I don't expect all the tests to pass with that. But it would be nice to at least test my own changes without having to rebuild. The alternative is that I personally keep applying this patch when I need it and then cutting it out before sending a PR, which I guess works but is really easy to mix in and send with an unrelated PR by accident.

If you're working on a nightly-only feature, why would you be using a non-nightly toolchain? It seems like that's my confusion -- I would expect Cargo developers to basically always develop on nightly.

I forgot I was on stable :(

I guess that is sort of a one time thing - but it's something I'd expect people to run into when they work on a nightly feature for the first time.

I don't imagine that this use case encompasses too many people, and like I mentioned before I do not want to encourage usage of the RUSTC_BOOTSTRAP env var. I'm also not really convinced that everyone who does hit this use case would immediately think to use RUSTC_BOOTSTRAP and save a recompile on nightly.

Ok, if you don't think it's useful we don't have to add it.


Warn and Exception when checkValidityOfAssociation don't name relation

when you get error (or warn) from checkValidityOfAssociation function, you get last word, but not the name of the relation or both source and dest class where the error is located.
For ONE_TO_MANY and MANY_TO_ONE you can just name tested var, but for ONE_TO_ONE and MANY_TO_MANY, you must get Class name you don't have in function param.

I'll see what can be done about it tonight. If a simple fix is enough, I'll include the improvement in v1.6.1, if not then it would be v1.6.2.

It's done and will be available in v1.6.2.


add :sftp_client to "application" in the mix.exs file ?

For Elixir noobs (like me ;) ):
Mentionning to also add :
def application do
[
   applications: [:sftp_client, ...]
  ...
]
end

in the readme.md ?

Were you having issues when not adding sftp_client to the applications option?
As SFTPClient officially runs only on Elixir > 1.8, specifying child applications should (generally) not be necessary.  Additionally, SFTPClient does not provide a supervision tree of its own. Thus, you can simply omit that option.

I just remember that I add some kind of errors and I just added that and then, no more error.
I don't remember what was the error but I'll give it a (re)try on thursday as I'm not in my office until then.
BTW my Elixir version is 1.9.0.

My bad: I removed the :sftp_client from my application options and everything is OK.
The error surely came from one of my own bugs ! :)
Issue closed... Sorry !

Found it !
That happens when I make and run a release:
set MIX_ENV=prod mix release
then myprogram start
then when I try a command (myprogram rpc "mycommand(args)":
=> crash and
** (UndefinedFunctionError) function SFTPClient.connect/1 is undefined (module SFTPClient is not available)
When I had :sftp_client to applications or extra_applications options in mix.exs, everything is OK.
Did I forget something when I made the release ?


Outlined textfield broken with most current builds of @material/textfield

What vue-mdc-adapter Version are you using?
2.5.21
What browser(s) is this bug affecting?
All browsers, all operating systems
What are the steps to reproduce the bug?

git clone git@github.com:maiorano84/vue-mdc-bug.git mdc && cd mdc && npm install
npm run serve
Navigate to http://localhost:8080
Click on the text field and observe what happens

What is the expected behavior?
An outline should be visible, and all textfields and notch components should respond on focus
What is the actual behavior?
A solid black SVG obscures the component
Any other information you believe would be useful?
The latest version of @material/textfield and @material/notched-outline switched from an SVG path to three separate divs. All styles associated with this path have been removed in the latest source SCSS files.
Removal of the SVG element in the components/textfield/mdc-textfield.vue file and replacing it with the updated format outlined here should resolve the root of the issue.
Because the label element now appears within the notched divs, an extra boolean check will have to be made on the first label element:

        {{ label }}

The notched outline block may then use something like the following (untested):

        {{ label }}

It is also likely that the current instance of the MDCNotchedOutlineFoundation class will need to be updated.

same here +1, I have spent the whole day to fix it...

@kieryk123 It looks like this project has been abandoned and is almost completely broken with the latest versions of MDC Web. If you value your time, I would highly recommend finding a different package or forking this one.

I forked this package and have made vue-material-adapter that uses the current material-components-web (v1.1.0) framework. There are a number of breaking changes, primarily because of the changes in material-components-web, but it is fairly compatible otherwise. The biggest thing that is missing is up to date documentation as until recently this was just me keeping up to date for my own use and I haven't had the cycles to get to updating the docs.
The other visible change is in how the project is structured - it now is a "monorepo" along the lines of the material-components-web-react project (as this seems more common nowadays and allows me to reuse their scripts and processes to some extent).


Internal Python Language Server error

Description
What steps will reproduce the problem?

DataFrame (a) with datetime Index. a.index.to - Then button press of "o" will create this error.
Traceback
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 266, in m_text_document__completion
    return self.completions(textDocument['uri'], position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 191, in completions
    completions = self._hook('pyls_completions', doc_uri, position=position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 122, in _hook
    return hook_handlers(config=self.config, workspace=self.workspace, document=doc, **kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/hooks.py", line 289, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 87, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 80, in __call__
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 52, in from_call
    result = func()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 78, in <lambda>
    outcome = _Result.from_call(lambda: self.oldcall(hook, hook_impls, kwargs))
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 81, in <lambda>
    firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 208, in _multicall
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/plugins/jedi_completion.py", line 44, in pyls_completions
    definitions = document.jedi_script(position).completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/__init__.py", line 179, in completions
    completions = completion.completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/completion.py", line 103, in completions
    return sorted(completions, key=lambda x: (x.name.startswith('__'),

RuntimeError: generator raised StopIteration  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 266, in m_text_document__completion
    return self.completions(textDocument['uri'], position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 191, in completions
    completions = self._hook('pyls_completions', doc_uri, position=position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 122, in _hook
    return hook_handlers(config=self.config, workspace=self.workspace, document=doc, **kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/hooks.py", line 289, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 87, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 80, in __call__
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 52, in from_call
    result = func()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 78, in <lambda>
    outcome = _Result.from_call(lambda: self.oldcall(hook, hook_impls, kwargs))
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 81, in <lambda>
    firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 208, in _multicall
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/plugins/jedi_completion.py", line 44, in pyls_completions
    definitions = document.jedi_script(position).completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/__init__.py", line 179, in completions
    completions = completion.completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/completion.py", line 103, in completions
    return sorted(completions, key=lambda x: (x.name.startswith('__'),

RuntimeError: generator raised StopIteration  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/home/work/venv/lib/python3.7/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 266, in m_text_document__completion
    return self.completions(textDocument['uri'], position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 191, in completions
    completions = self._hook('pyls_completions', doc_uri, position=position)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/python_ls.py", line 122, in _hook
    return hook_handlers(config=self.config, workspace=self.workspace, document=doc, **kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/hooks.py", line 289, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 87, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 80, in __call__
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 52, in from_call
    result = func()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/_tracing.py", line 78, in <lambda>
    outcome = _Result.from_call(lambda: self.oldcall(hook, hook_impls, kwargs))
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/manager.py", line 81, in <lambda>
    firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 208, in _multicall
    return outcome.get_result()
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/home/work/venv/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/work/venv/lib/python3.7/site-packages/pyls/plugins/jedi_completion.py", line 44, in pyls_completions
    definitions = document.jedi_script(position).completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/__init__.py", line 179, in completions
    completions = completion.completions()
  File "/home/work/venv/lib/python3.7/site-packages/jedi/api/completion.py", line 103, in completions
    return sorted(completions, key=lambda x: (x.name.startswith('__'),
RuntimeError: generator raised StopIteratio

Versions

Spyder version: 4.0.0b4
Python version: 3.7.3
Qt version: 5.12.4
PyQt5 version: 5.12.3
Operating System: Linux 5.0.0-23-generic

Dependencies
pygments >=2.0    :  2.4.2 (OK)
qdarkstyle >=2.6.4:  2.7 (OK)
sphinx >=0.6.6    :  2.1.2 (OK)
psutil >=0.3      :  5.6.3 (OK)
pyls >=0.27.0     :  0.27.0 (OK)
nbconvert >=4.0   :  5.5.0 (OK)
pandas >=0.13.1   :  0.25.0 (OK)
numpy >=1.7       :  1.16.4 (OK)
sympy >=0.7.3     :  None (NOK)
cython >=0.21     :  None (NOK)
qtconsole >=4.5.2 :  4.5.2 (OK)
IPython >=4.0     :  7.6.1 (OK)
matplotlib >=2.0.0:  3.1.1 (OK)
pylint >=0.25     :  2.3.1 (OK)

Please run the command below in a terminal and try again
pip install -U python-language-server jedi

That did it. Thanks very much.


How to install on nvim v0.5?

Hi, as the question suggests I'm pretty new to vim/nvim world. I'm using LunarVim which uses nvim v0.5 and want to install the version of this packages that's on lua branch but don't know how. Can you help?

looks like LunarVim uses https://github.com/wbthomason/packer.nvim
You can set the branch like so use {"lukas-reineke/indent-blankline.nvim", branch = "lua"}


Someone needs to write about Integers in chapters/integer.md

No one? I'll try to it until April 15.

Thanks @dakeshi for writing this content. It's great. There are a few sections remaining like "Converting" and "Operators". I'll keep this issue open until we have managed to fill the current sections. Thoughts?

It's a good idea. @vandadnp.  I'll try to fill extra section as soon as possible. ✈


templates: openSUSE: fall back to provo-mirror.opensuse.org

download.opensuse.org is inaccessible from Japan (500 Internal Server Error) https://bugzilla.opensuse.org/show_bug.cgi?id=1210240

I do however have problems creating an opensuse-tumbleweed VM

Could you open an issue


feat(connectors): expose search results to transformItems when available

Summary
This PR adds a secondary parameter to transformItems on all connectors that support it. It currently exposes the search results from Algolia.
Result
Search results can now be used in transformItems for various applications. For example, you can show the number of hits in the last segment of a breadcrumb widget:
// ...

instantsearch.widgets.breadcrumb({
  container: breadcrumbDiv,
  attributes: [
    'hierarchicalCategories.lvl0',
    'hierarchicalCategories.lvl1',
    'hierarchicalCategories.lvl2',
  ],
  transformItems: (items, { results }) => {
    const lastCrumb = items.pop();
    return [
      ...items,
      {
        ...lastCrumb,
        label: `${lastCrumb.label} (${results.nbHits} hits)`,
      },
    ];
  },
}),

// ...

Now that we have an object, it might be interesting to remove items as the first parameter in the next major and move it to the metadata object. Should we deprecate it now?

I don't think that is needed. In most cases you want do do something like items => items.map, changing that to ({items}) => items.map doesn't seem more friendly. Also I'm not sure how putting it in the second argument would help deprecation, as code would still need to change if we remove the first argument in a major

I created a follow-up task for documentation, after updating IS.js in all flavours. For the second note, I tend to agree with @Haroenv, as the method directly deals with items, it makes sense to separate it from other arguments.

I agree with Haroen too, that's a common pattern in functional programming, which also supports the identity function, and easy manipulation with Ramda for example.

@Haroenv @francoischalifour I meant have a single object argument, not keeping two arguments.
({ items, results }) => items.map(fn).concat(results.nbHits)


Documentation clarity

Received feedback on documentation - missing the problem statement this platform trying to address.

Need to add steps/ reference for ansible setup

Documentation added


Use blob content

Hi, I'm trying to implement the component on my platform but I get the documents (pdf, docx, xlsx,...) from the server as a blob object. I am having many problems to be able to visualize the documents.
Is there a way to deal with blob objects in this component? Thanks.

Instead of passing the blob url, pass the API url to the component and make him do the fetch. Let me know

Instead of passing the blob url, pass the API url to the component and make him do the fetch. Let me know

I have contemplated this form but when making the API call I need to pass some headers because I have a session token which I use so that only users who are on the platform can query the backend.

Instead of passing the blob url, pass the API url to the component and make him do the fetch. Let me know

I have contemplated this form but when making the API call I need to pass some headers because I have a session token which I use so that only users who are on the platform can query the backend.

You can do it.
const headers = useMemo(() => ({
    "Authorization": `Bearer ${accessToken}`,
  }), [accessToken]);

Save the accessToken in the context and pass the header in the jsx like that
<DocViewer requestHeaders={headers} ... />

Instead of passing the blob url, pass the API url to the component and make him do the fetch. Let me know

I have contemplated this form but when making the API call I need to pass some headers because I have a session token which I use so that only users who are on the platform can query the backend.

You can do it.
const headers = useMemo(() => ({
    "Authorization": `Bearer ${accessToken}`,
  }), [accessToken]);

Save the accessToken in the context and pass the header in the jsx like that <DocViewer requestHeaders={headers} ... />

Perfect it has worked for me.
Now I have another problem, the PDF is displayed perfectly but the .docx and .xlxs documents show me an error.
When I click on more information it shows me this.

Can't find this web address https://www.office.com/redir.aspx?assetid=HA102724036.

The problem here is that the docx and xlsx are trying to use the office live preview server, but your file isn't public so the office server can't access to it.
This problem can't be resolved actually

Ok, so I'll have to look for another alternative to be able to view .docx and .xlsx files.
Many thanks.

In the future we probably need to switch to a different display method .doc and .xls.


add larvae to track list

Thanks but I'd rather not do that. Use Auto-Grab since you'd want to pick them up anyways.


Refactor E2E tests for Dashboard; add E2E tests for User and Organization settings pages

Pull Request Description

PARTIALLY implements https://github.com/enso-org/cloud-v2/issues/1232

Partially refactor E2E test actions into a state machine.

The main goal of this is to disallow invalid actions - for example going from a page to itself, which will fail at runtime, or trying to create a new Data Link on a page where that button is not accessible.
An auxiliary goal is to have better namespacing of actions and better clarity:

Previously, everything was a locator at the top level of a single module. This makes it very difficult to comprehend what kinds of actions are available.

Note: There is also older namespace-based namespacing for the User and Organization settings pages, which were added before this refactor. They SHOULD be refactored to the new API, but I'm not sure whether it's worth spending the time right now.

Add E2E tests for every input on the "user" settings page and the "organization" settings page.
A skeletal E2E test for the Datalink modal has also been added - it does not actually test anything currently but should be sufficient for building upon.

Important Notes
None
Quality Assurance Recommendations

Just look at a few tests and make sure they're actually checking things as they were previously.

Code Review Recommendations

The new API is in e2e/actions/*. Of note is the base class in e2e/actions/BaseActions.ts. It may also be worth checking one each of:

The subclasses (any PascalCased file)
Non-subclass groups of actions (any camelCased file ending in Actions)
And the one file that exports just a single action. (openUserGroupAction)

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] Unit tests have been written where possible.

@MrFlashAccount @somebody1234 where are we with this PR? can we / do we want to merge this?


Xrange usage

Firstly, hi and thank you for reading this.
I do not have much exprerience with Redis Streams. The thing is that I'm trying to create a little consumer and get from message X to Y from a queue. I saw on official documentation the usage of Xrange (https://redis.io/topics/streams-intro) but, I do not know which params does ioredis.xrange fuction need.
Can anyone help me out with this?

@nbonbon Added an example for XRANGE: https://github.com/luin/ioredis/blob/main/examples/stream.js#L41


BlsSigner JsonRpcSigner & Signer Methods

We are adding a BlsSigner to bls-wallet-clients. This issue is concerned with ensuring the JsonRpcSigner & Signer Methods work with the BlsSigner. This will include overriding methods with BLS logic if needed and testing the other methods work as expected.
Some of the operations include connecting to an unchecked signer, getting the account address and checking if an object is a signer.
Note 1: The term Signer Methods here does not mean every method on the ethers Signer class. This refers to the following section in their docs that group these methods under no specific heading. Other Signer methods are included in other issues.
Note 2: There is one method called getUncheckedSigner() that returns a JsonRpcUncheckedSigner. If we were to implement this method, we would have to ensure the new BlsJsonRpcUncheckedSigner works as expected. If this is easy to implement, we should do it as part of this issue. If not, we should raise a separate issue to address this. Using an unchecked signer is also quite a niche requirement so we may also want to decide whether it is worth implementing and testing a BlsJsonRpcUncheckedSigner.
JsonRpcSigner Methods to test/override:
// The provider this signer was established from.
signer.provider ⇒ JsonRpcProvider

// Returns a new Signer object which does not perform additional checks when sending
// a transaction. See getUncheckedSigner for more details.
signer.connectUnchecked( ) ⇒ JsonRpcUncheckedSignersource

// Sends the transaction and returns a Promise which resolves to the opaque transaction hash.
signer.sendUncheckedTransaction( transaction ) ⇒ Promise< string< DataHexString< 32 > > >source

// Request the node unlock the account (if locked) using password.
signer.unlock( password ) ⇒ Promise< boolean >source

Signer Methods to test/override:
// Sub-classes must implement this, however they may simply throw an error if
// changing providers is not supported.
signer.connect( provider ) ⇒ Signer

// Returns a Promise that resolves to the account address.
signer.getAddress( ) ⇒ Promise< string< Address > >

// Returns true if and only if object is a Signer.
Signer.isSigner( object ) ⇒ boolean

Completed in https://github.com/web3well/bls-wallet/pull/439


Add result_error to simplify function

The meshopt_simplify function has an optional result_error out param that meshopt-rs ignores. I added them as an Option<&mut f32>, I know this is a breaking change, but we should follow the original API as much as we can in my opinion.

I agree, it's good to follow the same API! And the fix is quite simple usually: just add None at the end if you don't care.
This PR currently has conflict so I'll do the commit myself with the same idea so I can publish everything today