API v2 resource_types endpoint must return the count property

The current resource_types endpoint only returns an array of strings, but for the purposes of the faceted search we also need the number of resources for each resource type.
The following response would be enough
{
   "resource_types":[
	{
		"name": "layer",
		"count": <number of layers>
	},
    {
		"name": "map",
		"count": <number of maps>
	},
    {
		"name": "document",
		"count": <number of documents>
	},
    {
		"name": "geostory",
		"count": <number of geostories>
	}
   ]
}

@allyoucanmap the client will have to be updates as soon as this willbe done...

@giohappy I assigned this points.

@giohappy  Should the count on resource_types depend on resources visible to the current user?

@giohappy Should the count on resource_types depend on resources visible to the current user?

yes @marthamareal


Added - PS generator

Added a deployed user-friendly PS generator that is live and attracting over 1,000 monthly visitors.

live link can be checked here  - randompasswordgenerator.bio


Features page: fix typo

Just a teeny typo on the Features page. Though I'm not sure how I got here because I don't see a link to the Features page on the top navigation bar of https://stratumprotocol.org. Must have been from a blog post.

Thanks for contribution @satsie!
I think we decided to remove this one from navigation since it's an old page, and we outlined features more concisely on the index.md page. I'll merge this one regardless, but I guess we should see if we want to remove this page entirely due to it being a leftover. Neverthless congrats on your first contribution! 🥳


[11.x] Support soft deleted models when using explicit route model binding.

This PR allows the resolution of soft-deleted models when using Laravel's explicit route-model binding feature.
It allows developers to use explicit route-model binding without having to customise the resolution logic when dealing with soft-deleted models. To do so it uses the same withTrashed() method as implicit binding.
Before:
Route::get('/users/{user}', ...);

Route::bind('user', function (string $value) {
    return User::where('id', $value)->withTrashed()->firstOrFail();
});

After:
Route::get('/users/{user}', ...)->withTrashed();

Route::model('user', User::class);

This introduces no breaking changes, as resolveSoftDeletableRouteBinding is only being called when the route explicitly requests withTrashed() and the corresponding model uses the SoftDeletes trait.

https://laravel-code.tips/you-can-call-withtrashed-on-a-route-to-accept-soft-deleted-models/
What's wrong with this one?

@Rizky92 That example is using implicit binding. Currently, withTrashed doesn’t work with explicit binding; this PR makes the behaviour consistent.


crash when recovering from unsafe state

Hyprland Version
3b657257ecb7628a12a4fe72e733a60f031bfec2
Bug or Regression?
Regression
Description
Recovering from unsafe state leads to crash.
The regression was introduced in 46d66f4bcc95d9fb7fede18ad5c2c043796b9071. Issue doesn't happen before that commit.

FYI this is due to you calling hyprctl activeworkspace in unsafe state

I wasn't directly calling hyprctl activeworkspace, but it was being done by waybar for its workspaces module. The patch does solve the problem.
I found another issue though, Xwayland apps crash, presumably because the X connection is killed. Here's an example output:
❯ , xeyes
X connection to :0 broken (explicit kill or server shutdown).

interesting. Will look into, can you make another issue for that? I'll close this one by committing the patch


[hi] Localize Infrastructure as Code in Hindi

https://glossary.cncf.io/infrastructure-as-code/

done in #1173


Handling App links

Does the library support App Links?
These are how i'm using it now

<intent-filter>
    <action android:name="android.intent.action.VIEW" />

    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />

    <data android:scheme="uz.uzinfocom.myid" />
</intent-filter>

<intent-filter android:autoVerify="true">
    <action android:name="android.intent.action.VIEW" />

    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />

    <data
        android:host="myid.uz"
        android:pathPattern="/api/v.*/oauth2/authorization"
        android:scheme="https" />
</intent-filter>

@Destination(
    deepLinks = [
        DeepLink(
            uriPattern = "https://myid.uz/$FULL_ROUTE_PLACEHOLDER"
        )
    ]
)
@Composable
fun AppLinkScreen() {
}

But it doesn't work. I logged the data from the intent through the onNewIntent() method and got this result.
uz.uzinfocom.myid://authorization?client_id=test&auth_method=simple&status=0&state=None&method=simple&scope=address,contacts,doc_data,common_data

Clicked url
https://myid.uz/api/v1/oauth2/authorization?client_id=test&response_type=code&scope=address%2Ccontacts%2Cdoc_data%2Ccommon_data&method=simple

But I can't navigate the required screen.
Please help.

All I did related to deep linking was exposing the same APIs we have with official compose navigation with our annotations.
If this is possible with official library than it should be possible with compose destinations because the APIs are one to one. But I don’t know much past this , sorry 😬
My suggestion is try googling or asking on Kotlin slack about this from the perspective of the official compose navigation library, then it should be fairly simple to use the solution with compose destinations.


Refactoring Task Configurations and Adding Tests

Refactor the Task Configurations from Yaml to OO objects
Add test cases for the refactor in tests folder
Test have passed

@chenhuims / @namisan - rebased to the new development branch and all tests have passed.  Feel free to review and comment.


Add an instruction to link to profile.html from index.html

In the last exercise, we should instruct the student to add a link to profile.html, from index.html

@mikesjewett @stanidesis Which choice do you like better:

At the end of 007-profile-page.md tell them the exact code with the caveat that they'll learn what the <a> tag does later
Move 010-links.md before 007-profile-page.md

I like the second option a little better but I'm not sure if it will interfere with any students currently going through the program (who might need a refresh or something)

Yeah, let's go with 1.


Multi choice.

Fixes #5.
Example meta.json
{
  "schema": {
    "name": {
      "type": "string",
      "required": true,
      "label": "Project name"
    },
    "description": {
      "type": "string",
      "required": true,
      "label": "Project description",
      "default": "A Vue.js project"
    },
    "author": {
      "type": "string",
      "label": "Author"
    },
    "private": {
      "type": "boolean",
      "default": true
    },
    "preprocessor": {
      "label": "CSS Preprocessor",
      "type": "checkbox",
      "choices": [
        "less",
        "sass"
      ]
    }
  }
}

example package.json
{
  "name": "{{ name }}",
  "description": "{{ description }}",
  "author": "{{ author }}",
  {{#private}}
  "private": true,
  {{/private}}
  "scripts": {
    "watchify": "watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js",
    "serve": "http-server -c 1 -a localhost",
    "dev": "npm-run-all --parallel watchify serve",
    "build": "cross-env NODE_ENV=production browserify src/main.js | uglifyjs -c warnings=false -m > dist/build.js"
  },
  "dependencies": {
    "vue": "^1.0.0"
  },
  "devDependencies": {
    {{#preprocessor.less}}
    "less": "^2.6.1",
    {{/preprocessor.less}}
    {{#preprocessor.sass}}
    "node-sass": "^3.4.2",
    {{/preprocessor.sass}}
    "babel-core": "^6.0.0",
    "babel-plugin-transform-runtime": "^6.0.0",
    "babel-preset-es2015": "^6.0.0",
    "babel-preset-stage-2": "^6.0.0",
    "babel-runtime": "^5.8.0",
    "cross-env": "^1.0.6",
    "babelify": "^7.2.0",
    "browserify": "^12.0.1",
    "browserify-hmr": "^0.3.1",
    "http-server": "^0.9.0",
    "npm-run-all": "^1.6.0",
    "uglify-js": "^2.5.0",
    "vue-hot-reload-api": "^1.2.2",
    "vueify": "^8.0.0",
    "vueify-insert-css": "^1.0.0",
    "watchify": "^3.4.0"
  },
  "browserify": {
    "transform": [
      "vueify",
      "babelify"
    ]
  }
}

It would probably make sense to document this feature a bit more in readme.

Sweet!, thanks a lot!

@zigomir btw, really appreciate your contributions - interested in joining the vuejs team? I can add you as a maintainer of vue-cli. We also have a slack for collaborators :)

Yes, totally. I'd love to do that. I also wanted to start working on tests
as next thing that vue-cli needs. I see we already have an issue for that
:) Where can I join slack?
On Mon, Apr 4, 2016 at 9:54 AM Evan You<EMAIL_ADDRESS>wrote:

@zigomir https://github.com/zigomir btw, really appreciate your
contributions - interested in joining the vuejs team? I can add you as a
maintainer of vue-cli. We also have a slack for collaborators :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue-cli/pull/68#issuecomment-205390638

Awesome, just sent you invite.


Introduce Valkyrie before missions

It think it is better to introduce Valkyrie and the problems it solves before giving an overview of the missions.  For example...
Why Valkyrie
In 2003, NASA launched the Ice, Cloud and Land Elevation Satellite (ICESat) mission.  Over the following six years, ICESat collected valuable data about ice thickness in the Polar Regions.  Unfortunately, the ICESat mission ended before a follow-on mission could be launched.  To fill the gap, an airborne campaign called Operation IceBridge was started.  Between 2009 and 2019, Operation IceBridge flew numerous campaigns over the Greenland and Antarctic icesheets, as well as over sea ice in the Arctic and Southern Oceans.  The last campaign was fill in date here.  In September 2018, ICESat-2 was launched to continue NASA's collecting ice, cloud and land elevation data.
The wealth of data from these three missions, as well as from earlier missions, presents an opportunity to measure the evolution of ice thickness over several decades.  However, combining data from these missions is a challenge.  Data from the Airborne Topographic Mapper (ATM) flown during IceBridge campaigns is store in N different formats.  ICESat and ICESat-2 data are also in different file formats.  Data needs to be harmonized (put into similar formats) before comparisons can be made.  A further complication is that the coordinate reference systems used to locate measurements have changed.  The Earth's surface is not static and changes shape.  To account for these changes, terrestrial reference frames that relate latitude and longitude to points on the Earth are updated on a regular basis.  Since the launch of ICESat, the International Terrestrial Reference Frame has been updated three times.  The geolocation accuracy of instruments means that a point measured at the beginning of the record is not the same point as that measured at the end of the record.  Even though the latitude and longitude is the same.  These changes in geolocation need to be reconciled if meaningful comparisons of measurements are to be made.
Valkyrie solves this problem...
This needs some work
Brief overview of ICESat
Brief Overview of Operation IceBridge
Brief Overview of ICESat-2

This was updated prior to our advertisement of Iceflow last year.


zabbix graffana database with mariadb

Describe the bug
i  connected zabbix databaze with graffana, i configurated Data Sources but i have this message when i share dashboard

Grafana
Zabbix
Grafana-Zabbix Plugin

5.2.4
4.0
3.9.7

Unauthorized error probably related to https://github.com/grafana/grafana/issues/11006
At the second screen you should set proper datasource for the panel.


Create user via API "The password confirmation does not match."

Laravel Version: 5.5.39
Voyager Version: 1.0
PHP Version: 7.2.3
Database Driver & Version: mysql

Description:
I tried to create API, and when testing register function, I used this information:
curl -X POST http://localhost:8000/api/register \  -H "Accept: application/json" \  -H "Content-Type: application/json" \  -d '{"name": "Thanh", "email"<EMAIL_ADDRESS>"password": "123456", "password_confirmation": "123456"}'
but I received error:
{     "message": "The given data was invalid.",     "errors": {         "password": [             "The password confirmation does not match."         ]     } }
How to create users via my API?
Steps To Reproduce:

I used Postman and wrote wrong "password_confimation" instead "password_confirmation"


🌱 Leave BMO and Ironic configmaps alone

What this PR does / why we need it:
These configmaps are created/edited from metal3-dev-env when setting up
the environment. It is better to let them stay as they are to avoid
conflicts and mistakes. They are cleaned/reset every time the bootstrap
cluster is lanuched anyway.
Wait for https://github.com/metal3-io/metal3-dev-env/pull/975 before merging this.

/test-v1b1-centos-e2e-parallel

/test-v1b1-ubuntu-e2e-parallel

/test-v1b1-ubuntu-integration

/test-v1b1-upgrade-e2e


Refactoring: event stream based agent history

Memory component: short overview
This PR works with the short term history. It proposes an implementation of the event-stream based architecture for agent history, which:

uses directly the event stream for history

it doesn't save its own copies of events (in state.history)
event stream is the source of truth

filters and otherwise processes the events, for insertion in the prompt
the stream is not pairs of (action, observation), and neither is history

when the agent returns an action, the runtime/backend returns an observation that has the field cause set to the action id

a compatibility method with (action, observation) pairs is used for evals output.

Pre-requisite for #2021

@xingyaoww Totally agree, I think it will be better to get this one in, sooner rather than later, because we need this architecture to continue building on.
Merge conflicts fixed, and it's ready for review.


Tips on debugging CUDA kernel

I'm writing bidirectionality support into the CUDA kernel. Should be able to get high L1 and L2 cache hit rates as portions of our sequence should still be in memory. I am curious if you have any recommendations to go about debugging. Compile time is the roughest, so I have removed some architectures while I test it. Any other suggestions or tips would be greatly appreciated. Thanks for such a great project, really does get me excited about this field.

You can comment out most of the options (e.g. only keep fp16 real length 128) so that it compiles faster.
I usually use printf to debug, sth like if (threadIdx.x == 0 && blockIdx.x == 0 && blockIdx.y == 0 && blockIdx.z == 0) printf(blah);

Thanks for the quick response!

I'll also mention that an "official" (endorsed by me at least) version of bidirectionality will appear on arXiv in the next two weeks :) would be cool to get lower-level implementation support for that!

I'm looking forward to it! At least for me, the way people did bidirectionality for Mamba with flipping and adding doesn't make any sense from a mathematical standpoint. I am working on a better extension of mamba to nd sequences and have a basic implementation for bidirectionality that is more mathematically sound. I look forward to the paper and would be more than happy to share the bidirectional code/change it to have low-level support for this paper.

Could you please provide the command that you use in order to recompile the kernel? Because i run
python3 setup.py install but i do not think this is the proper way to do it

pip install -e . is what I use, you need to edit the setup.py if you want to customize the install.

Do you add the selective_scan_fwd{bwd}_kernel.cuh in your setup.py? Because it seems to be ignored when i use python3 setup.py install command (which is relatively fast, but I also think this is why).
The only way it seems to work is when I first delete the build folder and then run python3 setup.py install in order to recompile the .cuh file.
Thanks for your help

I see what you are saying. Yes, you have to delete the build and then just rerun. The compiler doesn't know that header files have changed, and thus it won't do anything unless you delete the build folder. Deleting build is what I did and it worked fine. The best thing to reduce compile time was to remove the number of templates and also only compile to sm architecture on my machine. Np, and gl


Add a figure to notebook

The figure and the notebook can be found in
https://github.com/microsoft/FLAML/pull/1216/files

Assigned me I will add

Can explain more what actually does

Hi i will like to fix the issue , can you assign this to me

The figure is not in the notebook in the autogen repo.

Pls assign this issue to me i can fix this issue

Also can you send the image because its not loading properly


make uninstall deletes too much

The uninstall target in Makefile has a line:
$(REMOVE) $(DESTDIR)$(bindir)/infer*

Which results in non-infer binaries being deleted from my system.  I suggest we tighten that up using an explicit list of binaries installed by infer.

It isn't that DESTDIR is incorrect, assuming "correct" is /usr/local/bin.  I can give you a concrete example:
tommd@ubuntu1604-xenial tommd/infer% sudo touch /usr/local/bin/infer-thing
[sudo] password for tommd:
tommd@ubuntu1604-xenial tommd/infer% sudo make uninstall
rm -rf /usr/local/lib/infer/
rm -f /usr/local/bin/infer*
rm -f /usr/local/bin/infer-analyze /usr/local/bin/infer-capture /usr/local/bin/infer-compile /usr/local/bin/infer-explore /usr/local/bin/infer-report /usr/local/bin/infer-reportdiff /usr/local/bin/infer-run
rm -f  /usr/local/share/man/man1/infer-analyze.1.gz  /usr/local/share/man/man1/infer-capture.1.gz  /usr/local/share/man/man1/infer-compile.1.gz  /usr/local/share/man/man1/infer-explore.1.gz  /usr/local/share/man/man1/infer-report.1.gz  /usr/local/share/man/man1/infer-reportdiff.1.gz  /usr/local/share/man/man1/infer-run.1.gz  /usr/local/share/man/man1/infer.1.gz
tommd@ubuntu1604-xenial tommd/infer% ls -l /usr/local/bin/infer-thing
ls: cannot access '/usr/local/bin/infer-thing': No such file or directory

I have a binary with a name prefixed with infer, much as the infer-thing appears above.  It wasn't much of an issue for me either when I discovered it or moving forward now that I'm aware of this quirk, but I expect it could cause someone else a headache.

Yes, this isn't safe. We should store the list of binaries created and only remove the binaries from this list.

FYI that list exists already: https://github.com/facebook/infer/blob/cac08598a027e689580705df97f85ef61c912c6b/Makefile.config#L58-L66
We should definitely fix this instance, but more generally I wonder how we can ensure that make uninstall never deletes too much, and doesn't leave files around either.


[NNPA] Enable splitting zdnn div

I forgot to add zdnn div into the list of supported ops for splitting in #2690. Added it here.

Jenkins Linux ppc64le Build #12980 [push] Enable splitting zdnn di... started at 02:26

Jenkins Linux s390x Build #13983 [push] Enable splitting zdnn di... started at 02:17

Jenkins Linux amd64 Build #13956 [push] Enable splitting zdnn di... started at 01:17

Jenkins Linux amd64 Build #13956 [push] Enable splitting zdnn di... passed after 1 hr 4 min

Jenkins Linux s390x Build #13983 [push] Enable splitting zdnn di... passed after 1 hr 23 min

Jenkins Linux ppc64le Build #12980 [push] Enable splitting zdnn di... passed after 1 hr 49 min


propose if let guard

View
I find myself wanting this often (the latest use case being parsing terminal escape codes).

The Lang Team discussed this RFC today, with the following take-aways:

This seems like a natural syntactic extension, under the guise of "if you can use if as a guard, it's reasonable to expect if let to work as well".
At least some members of the team expressed running into situations where such syntax would've been useful, and they instead used something like matching against a pair.
Generally there were no real objections. However, there's a concern of "syntax creep": we've been getting (and accepting) a number of such RFCs to "complete" various parts of our grammar, and we need to make sure that at the end we're left with something that sits together well.

Overall, the consensus was that we should move forward with this RFC, but with a clearly provisional flavor (as with other recent syntactic additions): when it comes time to stabilize, we want to take a holistic look at the way the syntax is evolving across these RFCs.
@rfcbot fcp merge

I have 2 concerns:

(category: "formatting") This encourages rightward drift in arms and the tokens = and => are hard to distinguish at glance.
We can mitigate this with rustfmt by formatting as:

match x {
    'C' if let &[n] = parms =>
        self.screen.move_x( n as _),  // note the linebreak!
    ...
}

or if the bit before if let is very long:
match ui.wait_event() {
    KeyPress(mod_, key, datum)
        if let Some(action) = intercept(mod_, key) => act(action, datum),
    ev => accept!(ev),
}

(category: "syntax creep") match and if let (and while let) become more inconsistent; It seems to me that the natural extension of this RFC is to permit:

if let A(x) = foo()
if let B(y) = bar()
if cond(x, y) {
    ...
}

This ^ particular syntax was not (iirc) very intelligible in the survey done at #2260.
The RFC does write that you can't chain if let and if in match, so maybe if let chaining isn't the logical conclusion, but it is something to consider.

@Centril What consistency between match and if let would this break?

@strake you would not be permitted to chain an if let with an if let, but you are allowed to chain a match with an if let. That is not necessarily a problem; I'd just like us to be aware of it =)

I see a majority of boxes checked — what is holding back FCP?

@rfcbot concern borrowck
We are currently working through how to rationalize our existing patterns in MIR borrowck, and in particular addressing a number of soundness complications. It's not entirely obvious to me how this RFC is going to interact with that -- for example, the current treatment that we are moving towards is that -- in a guard expression -- the bindings from the pattern are compiled into refrences into the value being matched, with an implicit deref. So e.g. in a match like this:
match foo {
    Some(x) if x > 5 => {..}
}

although the type of x in the binding is i32, the type of the value representing x in the MIR is an &i32, and the x > 5 becomes *x > 5. (This is similar to what we do for closures.) The goal here is to prevent arms from mutating through x (e.g., if it is a ref mut binding) or from moving out of x.
I feel like before we accept this RFC, we ought to talk through what its MIR desugaring will be and how it will interact with the borrow check.
(cc @pnkfelix)

@nikomatsakis and @pnkfelix need to discuss more.
But the executive summary is: @pnkfelix currently believes that there is a relatively straight-forward semantics under the match changes that are proposed (see https://github.com/rust-lang/rust/pull/50783) as part of the NLL work.
It might be a good idea to try to work through those semantics, perhaps via a series of examples, within this RFC text.
Or it might be a good idea to just accept this RFC, with the understanding that we will need to work out the exact semantics (in terms of when the various bindings occur in the MIR desugaring) as part of the implementation effort.

@rfcbot resolve borrowck
OK, so it seems I killed the conversation with my comment. I apologize that the comment didn't make it particularly clearly what sort of follow-up would satisfy me. After some consideration, I've decided to withdraw my concern. It's not that I'm not still worried, it's that I think it's ok to merge this RFC basically as our "stated intention" to specify this more clearly.

I think that this sounds good:
match keyinfo {
  /* Separate 'if let' with 'if' using '&&'
  note: && is parsed regularly after initial && separator */
  Some(keyinfo) if let Some(key) = get_key(keyinfo) && key == K_ENTER && key == K_UP || key == K_DOWN => {
    // stuff
  },
  _ => {
    // other stuff
  }
}


Handle ACLs stored in database

Added support for "ACLs in database" feature and filtering ES by ACLs
Group identifiers in RAML must now be full and complete. E.g. g:admin instead of just admin

created separate branch: acls_in_db


fix: use value instead of missing template

@mvisonneau there was a small problem with your latest change: https://github.com/mvisonneau/helm-charts/commit/effddc6dd9c2e7db5a251705e251377102ba4593#r119644504

thanks @salzig, I need some coffee..! 🙌


image feature is 2-Dimensional, what is ids for one picture ?

i extract feature from image. every picture have 2-Dimensional feature, like [[0.32, 0.52 ...], [0.32, 0.52 ...], [0.32, 0.52 ...]].
when i index for one picture. it like this
xb = # xb extract from one image
index = faiss.IndexFlatL2(xb.shape[1])
index_with_ids = faiss.IndexIDMap(index)
index_with_ids.add_with_ids(xb, ids)
then, what is ids for one picture ?
and, what is xb and ids for many images ? (image feature is 2-Dimensional)

does all the id for one picture xb is the same?
xb = # xb extract from one image
ids = [image_id] * xb.shape[0]   # all the id for this image is same
index = faiss.IndexFlatL2(xb.shape[1])
index_with_ids = faiss.IndexIDMap(index)
index_with_ids.add_with_ids(xb, ids)

These questions are related to faiss, not this project. Please read their documentation:

https://github.com/facebookresearch/faiss/wiki/Pre--and-post-processing#faiss-id-mapping


Question about 3D environment data

I was wondering how the data for 3D environments that aren't in the .mdl format are stored. Stuff like walls and streets and buildings. I found a way to extract the textures for those environments in 2 and 3 but I'm interested in how the games handle the 3D data for them. As far as I can tell the data is stored in either .map files, .cam files, .cld files, or .kg2 files. What are these file types for?

Actually I have another question as well. The character models don't have any face bones aside from the jaw and eyes, so how are the faces animated in-game? The same thing is true of SH3 models so it can't just be FMVs.

hi @many-bees !
yep, 3d environments are stored in map files -- i recommend checking out pmttavara's ph2 for an absolutely amazing map viewer/editor :)
cld is collision data; checkout bigmanjapan's explanation here
cam is for cutscenes, which my friend quaker has done some work on, but hasn't been fully reversed afaik?
kg2 is for map shadows, while kg1 is for character shadows. it has been reversed, see murugo's documentation here
i plan on supporting maps in the museum soon, but haven't gotten there yet! i'm working hard to finish my model editor -- expect a big update next weekend!

The character models don't have any face bones aside from the jaw and eyes, so how are the faces animated in-game? The same thing is true of SH3 models so it can't just be FMVs.

you're right! this is the purpose of the cluster_nodes section in the mdl files, which is blendshapes/morph targets. basically it just blends between different shapes to get different facial expressions. murugo has reversed this for ps2 (and pc, although he hasn't uploaded it to github): https://github.com/Murugo/Misc-Game-Research/blob/main/PS2/Silent Hill 2%2B3/Blender/addons/io_sh2_sh3/import_mdl.py
this is also planned to be ported over into the museum.

Damn now I'm really excited

When you say Murugo hasn't uploaded his reverse engineering of PC .mdl files but hasn't uploaded it to github, is there any place where he has uploaded it? And do you know of anyone who's working on the same for Silent Hill 4?


Fix T1/T2 Charstring inheritance

See #1932. Tracking reminder for me to get onto it.

Is it worth touching?


Fix Mapdl import

Closes: https://github.com/ansys/pymaterials-manager/issues/203

Codecov Report
Attention: Patch coverage is 66.66667% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 82.93%.  Consider uploading reports for the commit f8ea3f4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #204      +/-   ##
==========================================
+ Coverage   82.88%   82.93%   +0.05%
==========================================
  Files          23       23
  Lines         964      967       +3
==========================================
+ Hits          799      802       +3
  Misses        165      165


Display names of endorsing communities in list of search results

Context
As a reader, I want to know if an article has been endorsed or not before I read it, so that I can be more informed when deciding if an article is worth my time.
We hypothesise that endorsements from trusted editorial communities are an important trust indicator for readers and that articles with one or more endorsements will command greater levels of trust.
DoD

[ ] A clear indication of the names of communities that have endorsed an article in the list of returned results

[ ] If an article has not been endorsed by a community, return nothing.

Will be testing on http://localhost:8080/articles?query=Marine+cyanolichens+from+different+littoral+zones as the first article being endorsed by PeerJ.

To see both endorsed and not endorsed articles: http://localhost:8080/articles?query=distinct bacterial


ActiveStorage::FixtureSet.blob incompatible with rspec

What Ruby, Rails and RSpec versions are you using?
Ruby version: 3.1.1
Rails version: 7.0.4
RSpec version:
rspec-core (3.12.0)
rspec-rails (5.0.3)
rspec-support (3.12.0)
Observed behaviour
When setting up file fixtures, and calling e.g. fixtures/active_storage/blobs.yml
my_blob: <%= ActiveStorage::FixtureSet.blob(
   filename: "test.jpg",
) %>

This will call ActiveSupport::Testing::FileFixtures.file_fixture_path, which is nil. This then fails.
The rspec config should be set up correctly.
RSpec.configure do |config||
  config.fixture_path = "#{::Rails.root}/spec/fixtures"
  config.file_fixture_path = "#{::Rails.root}/spec/fixtures/files"
end

Expected behaviour
Expect rspec to find file_fixture_path

We have a default
Can you please help to pinpoint the issue by setting a breakpoint here? What is the difference if you configure it vs use the default?

Can you provide a reproduction snippet? (Preferably not an entire app, see our snippets for examples (https://github.com/rspec/rspec-rails/tree/main/snippets)

I ran into the same problem today. Here's what I've figured out. And sorry I couldn't get a snippet to work. I tried but ran into ActiveStorage initialization issues.
TL;DR.
Rails expects ActiveStorage::FixtureSet.file_fixture_path to be set, but rspec-rails sets RSpec::ExampleGroups::FooExample.file_fixture_path instead.  ActiveStorage::FixtureSet.file_fixture_path is nil and blows up a File.join call.

This is the line that is blowing up.
path = Pathname.new(File.join(file_fixture_path, fixture_name))

https://github.com/rails/rails/blob/f95c0b7e96eb36bc3efc0c5beffbb9e84ea664e4/activesupport/lib/active_support/testing/file_fixtures.rb#L27
The line errors because file_fixture_path is nil and blows up the File.join call. On that line, self is ActiveStorage::FixtureSet, so Rails expects the ActiveStorage::FixtureSet.file_fixture_path class attribute to be defined.
How Rails and minitest do it
Rails and minitest set up the class attribute in active_storage/engine.rb on line 204.
ActiveSupport.on_load(:active_support_test_case) do
  ActiveStorage::FixtureSet.file_fixture_path = ActiveSupport::TestCase.file_fixture_path
end

rspec-rails
rspec-rails sets the file_fixture_path class attribute on the wrong class. It should set it on ActiveStorage::FixtureSet, but instead sets it on  the current example group.
https://github.com/rspec/rspec-rails/blob/fe95eacb376f7fa558d3ffeeaa9afa6d3110a540/lib/rspec/rails/file_fixture_support.rb#L11
Fix?
If I change that line to the code below, the error goes away.
ActiveStorage::FixtureSet.file_fixture_path = RSpec.configuration.file_fixture_path

I don't know if that is a good fix, or if I'm 100% on the write track, maybe I'm missing something. I could send a pull request.

file_fixture is getting the path uses it with no explicit receiver. And file_fixture_path is defined with class_attribute that allows overriding the global setting per instance of a test.
Such usage is confirmed by e.g. this test.
As for blob usage inside fixtures, yes, it appears that we're missing setting the default file fixture path.
But the suggested fix would break non-active storage specs, wouldn't it?

If I set a breakpoint on the line you mentioned, when it runs, self will be ActiveSupport::TestCase. The user can override that value by calling self.file_fixture_path in their test case because they inherit from ActiveSupport::TestCase.

But the suggested fix would break non-active storage specs, wouldn't it?

Yes, you're right. Good catch. I just tested it. It breaks regular file fixtures with the same error I was getting with blobs.
But, you don't have to replace the line. This makes more sense.
included do
  self.file_fixture_path = RSpec.configuration.file_fixture_path
  if defined? ActiveStorage::FixtureSet
    ActiveStorage::FixtureSet.file_fixture_path = RSpec.configuration.file_fixture_path
  end
end

I don't think  Rails < 7.0 has the ActiveStorage::FixtureSet class. So, the if statement is needed.
Oh and a quick note. If anyone comes across this and wants an easy solution, I'm currently setting the ActiveStorage::FixtureSet.file_fixture_path in my rails_helper.rb file. This fixes the problem.

Nice! A PR is welcome, @jaywhy.


savepoint-timestamp fix to correct invalid dates to current date and time

Invalid dates can mean either a date in the future, or a date with invalid format.

issue https://github.com/opendatakit/tool-suite-X/issues/99

runtests

Closed by https://github.com/opendatakit/androidlibrary/pull/130


Feat/docs generator

:tada: This PR is included in version 2.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Show package dependencies on package details

This is a request to show all packages that a package depends on under package details. I.e., something like this:
Uploader
<EMAIL_ADDRESS><EMAIL_ADDRESS>License
unknown (LICENSE)
Dependencies
flutter, url_launcher
More

Yup, only the direct ones.

It'll be tough to pick "good ones" here. I'd like to avoid too much noise in the sidebar.

I don't think we should be "picking", we should be showing them all. If there are too many and it becomes noise, just show the first x characters and then add a 'more' link to expand the list.

@mit-mit – what's wrong w/ the details in the analysis tab?
I'd like to keep the sidebar ~clean.

The way I think of it, the sidebar is a nicely formatted pubspec.yaml, and the direct dependencies may have place there. The analysis has much more (dev and transitive deps, constraint, resolution)...

@kevmoo I think knowing the dependencies is a key piece of information to a consumer of a package. A consumer needs to understand the license, health, completeness, etc. not just of the package they are consuming directly, but also those same characteristics of it's dependencies. That's why I think it's important to put them "front and center"


Trouble Using This in November of 2023

I'm trying to use this but finding myself unable to do so, I'm getting login errors but I believe thats only because I have steam guard and I do not see a place in which to put a code for either account. Is there any chance of this working? My goal is to get to the strange limit of 2.49 billion. No worries if you dont want to come back to this problem after so long. Slight bummer but I'd understand.

When you log into an account with Steam Guard it should ask you for the code in the same window. Its possible this is now broken due to Steam having changed the way logins work a while ago. Can you try running npm update and then node index.js and see if that solves the issue for now?

Upon running the npm update I received
"added 17 packages, removed 199 packages, changed 16 packages, and audited 90 packages in 4s"
After running "node index.js" I was met with:
"Error: InvalidPassword
at Steamuser._handleLogOnResponse (C:\Users\123|Desktop\fake-stattrak-master\node_modules\steam-user\componets\0-9logon.js:775:17)
at C:\Users\123\Desktop\fake-stattrak-master\node_modules\steam-user\componets\o9-logon.js:400:10 {
eresult: 5
}
I did not receive any prompt to enter a steam code.

In my test it appears that I can login fine after upgrading all dependencies but my strange weapon doesn't appear to gain any kills. Not sure why and I am not really gonna bother looking into it.

That's fine, thanks for responding at all :)


[google_maps_flutter] Removes setZoomControlsEnabled from GoogleMapController.h

Description
As outlined in https://github.com/flutter/plugins/commit/821a5c4e761e55347452960a5b0568b6d5a915c5#r38618278, GoogleMapController shipped with an invalid method definition.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@lidongze91 I do not understand yet why this issue wouldn't be reported by either Xcode or the build server / CI. Could you please outline the steps you took (e.g. compilation instructions), and perhaps we can extend CI scripts for all plugins in a future PR?


Chem | Similarity,Diversity searches: add the ability to perform the search for the filtered data

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-15155

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16171


Star Citizen lighting issues

The lighting is black for most of the screen.

System information

GPU: GTX 1080
Driver: 391.35
Wine version: Native Windows 10
DXVK version: f71f527

Apitrace file(s)
trace
Log files
StarCitizen_d3d11.log
StarCitizen_dxgi.log
vulkanlog.txt

That a regression or did that never work to begin with?

Never worked to begin with.

For more background; the same issue is present with plain Wine, even without DXVK.

As of f4a92a6 the lighting issues seems to be fixed. However, I am now receiving a crash in some places.
This error looks to be the cause of the crash
err:   D3D11: Incompatible UAV formats
  Base format: 27
  View format: 42

Commit fb3dbd8
fixed the crash. Thank you.


pythonPackages.django: 1.11.24 -> 1.11.26

See

https://docs.djangoproject.com/en/1.11/releases/1.11.26/
https://docs.djangoproject.com/en/1.11/releases/1.11.25/

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

I’ll port it to release-19.09 once merged.

a lot of the packages have dropped support for python2

Yes, python2 is close to retirement (less than 1 month from now https://pythonclock.org/). Having projects dropping its support is a good thing if you ask me.
From what I can see, all the 26 failed dependent derivations also fails on master, this is not linked to this PR.

still, touching the django ecosystem doesn't happen too often, it would be nice to get the nix-review to reflect the current state of dependent packages

could mark django at python 2.7 as broken

This will be done soon.
django-1.11 is the last LTR branch supporting python2, and it reach EOL by april 2020. So before release-20.03, I plan to turn django-2.2 the main django branch supported in nixpkgs, turning off python2 support in the same time.

looks like the django ecosystem could use some love

FYI: This PR fixes the sentry-sdk build: https://github.com/NixOS/nixpkgs/pull/75039


Update events

Codecov Report

Merging #13 (03e6dfd) into main (9e5ab04) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          105       105
  Branches         4         4
=========================================
  Hits           105       105

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 6ac2393...03e6dfd. Read the comment docs.


Add Inertia v2 Support

Please merge https://github.com/lepikhinb/momentum-modal/pull/76 and publish this Vue3 plugin. It has been extensively tested from our side in a larger app and works flawlessly with Inertia v2.0.0

@lepikhinb are you still planning to maintain Momentum Modal? It's a great project and it works absolutely flawlessly on Inertia v2, so we would all greatly appreciate if you could merge and publish it. 🙏

momentum-modal (npm)
For those who can't wait and don't want to use npm i --force (as now all other packages seem to be compatible with Inertia v2), you can install directly from my other inertia-v2-build branch like this:
$ npm i onlime/momentum-modal-plugin\#inertia-v2-build --save-dev

... which will put the following in your package.json:
    "devDependencies": {
        "momentum-modal": "github:onlime/momentum-modal-plugin#inertia-v2-build",
    }

I have bumped all deps and added a prepare script there, so momentum-modal-plugin will be automagically built upon install.

[!IMPORTANT]
Make sure you have prettier installed globally (e.g. brew install prettier) to get the build running.

based/momentum-modal (Composer)
For PHP based/momentum-modal package (https://github.com/lepikhinb/momentum-modal/pull/76), just add this to your composer.json:
    "require": {
        "based/momentum-modal": "dev-inertia-v2",
    },
    "repositories": [
        {
            "type": "git",
            "url": "https://github.com/onlime/momentum-modal.git"
        }
    ],

I've asked @lepikhinb a couple of times if this could be merged and he's said he would, Inertia 2.0 has been in beta for a while and has been released now for a week. There's been plenty of time to merge this in.
However, we've moved onto using Inertia UI's Modal plugin instead as we're already using the Inertia UI Table and it's compatible with Inertia 2.0.

another alternative


Transition User Endpoints from WebSockets to HTTP Requests

Hello Team,
We need to update the implementation of our user endpoints, specifically for login, registration, and password recovery functionalities. Currently, these are handled through WebSockets via a beyond-js bridge. However, for consistency with our current API standards, we should transition these endpoints to use HTTP requests.
Action Items:

Modify the login endpoint to use HTTP requests.
Update the registration endpoint to follow the HTTP request model.
Change the password recovery functionality to utilize HTTP requests.

This change will align these endpoints with our existing API infrastructure and ensure uniformity across our platform. Please ensure that the transition is smooth and does not affect the existing user experience.

@ftovar8 did you finish it ?

As finished, there is only the login point with Google.
There are no ws calls for password recovery or user registration, at the API level no functionalities have been developed for this.
@jircdev


Download sources from archive instead of git

also, corrected typo from e5531edcbe5cc811b8961967b1748f4fa722fb46
fixes #34

There are less errors, but it still happens some times. I will implement a retry tomorrow...

Well, the XCode travis build ran 24 times in a row without problem, it didn't even hit the download exception handling and retry...

@ericLemanissier Thanks for your PR. As mentioned in the related issue, I think it would be better to download the whole archive from the Qt's website instead of downloading the modules one by one.

migrated to https://github.com/bincrafters/conan-qt


Add tests to util

for test coverage and testing tuesday
IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #[issue number]
Checklist

[x] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

While using this convent to name test functions is more human readable, it makes it difficult to navigate to the class/function with failing tests during debugging in the IDE (especially when there are so many test cases). The alternative is to use JUNIT 5 annotation for providing human readable name however compose UI tests are still dependent on JUNIT4


Embedded capacity planning: fix whitespaces

There were some non-visual characters that caused whitespace mistakes in the text. Corrected those.

@mberdugo
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Documentation to explain request header casing

Addresses Issue #1882 Header helper and what it does to case on header names

thank you, merged


All VMS getting in cluster  reboots when we remove a control node from cluster

Describe the bug
All VMS getting in cluster  reboots when we remove a control node from cluster
To Reproduce
Steps to reproduce the behavior:

Go to '...' Hosts - Cordon the node -> Enable Maintenance --> Delete node

Expected behavior
When remove a control plane node which is in maintenance it should not restart all VMs (Virt pods)
Its happening only for control plane nodes - worker nodes are good when we remove from cluster
*Support bundle
Environment

Harvester ISO version:  V.1.1.1
Underlying Infrastructure ( Baremetal with Dell PowerEdge R6420):

Additional context
NAME                       STATUS                     ROLES                       AGE     VERSION
node01-c01   Ready                      control-plane,etcd,master   60d     v1.24.7+rke2r1
node01-c02   Ready,SchedulingDisabled   control-plane,etcd,master   60d     v1.24.7+rke2r1 - when we remove this node all VMS are restarting
node01-c05   Ready                      control-plane,etcd,master   60d     v1.24.7+rke2r1
node01-c06   Ready                                            60d     v1.24.7+rke2r1
node01-c09   Ready                                            59d     v1.24.7+rke2r1
node01-c10   Ready                                            59d     v1.24.7+rke2r1
node01-c11   Ready                                            59d     v1.24.7+rke2r1
node01-c12   Ready                                            59d     v1.24.7+rke2r1
node01-c13   Ready                                            48d     v1.24.7+rke2r1
node01-c14   Ready                                            47d     v1.24.7+rke2r1
node01-c15   Ready                                            48d     v1.24.7+rke2r1
node01-c16   Ready                                            48d     v1.24.7+rke2r1
node01-c17   Ready                                            6d18h   v1.24.7+rke2r1
node01-c18   Ready                                            6d18h   v1.24.7+rke2r1
node01-c19   Ready                                            6d17h   v1.24.7+rke2r1
node01-c20   Ready                                            6d17h   v1.24.7+rke2r1

@dseralathan
The Condorn&maintain will migrate all VMs from the specified NODE to other NODEs.  I guess not all the VMs were scheduled in node01-c02 when you Cordon and maintain it, please double check.
Even though it is a bit later, but https://docs.harvesterhci.io/v1.1/troubleshooting/harvester/#generate-a-support-bundle wich a support-bundle file we may still check if some useful information are available.
Are VLAN network, storage-network or some other none-default configuration are configured/enabled in this cluster? thanks.


Flutter analyze reports 3 issues in analysis_options.yaml

Describe the bug
Flutter analyze reports 3 issues in analysis_options.yaml
To Reproduce
Steps to reproduce the behavior:

Add very_good_analysis: ^2.3.0 to project pubspec
Run flutter pub upgrade
Run flutter pub get
Run flutter analyze
Observed 3 errors in analysis options yaml

flutter analyze
Analyzing application name...

warning - Warning in the included options file C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\very_good_analysis-2.3.0\lib\analysis_options.2.3.0.yaml(1782..1803): 'deprecated_consistency' is not a
       recognized lint rule - analysis_options.yaml:1:10 - included_file_warning
warning - Warning in the included options file C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\very_good_analysis-2.3.0\lib\analysis_options.2.3.0.yaml(4865..4895): 'use_build_context_synchronously' is not
       a recognized lint rule - analysis_options.yaml:1:10 - included_file_warning
warning - Warning in the included options file C:\src\flutter\.pub-cache\hosted\pub.dartlang.org\very_good_analysis-2.3.0\lib\analysis_options.2.3.0.yaml(5079..5097): 'use_named_constants' is not a recognized
       lint rule - analysis_options.yaml:1:10 - included_file_warning

3 issues found. (ran in 14.5s)

Expected behavior
No error reported in very_good_analysis plugin.
Screenshots

Additional context
flutter doctor output
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.19042.1110], locale en-150)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] Connected device (3 available)

• No issues found!

Reproducible on Linux and Windows machines
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.1, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✗] Linux toolchain - develop for Linux desktop
    ✗ clang++ is required for Linux development.
      It is likely available from your distribution (e.g.: apt install clang), or can be downloaded from https://releases.llvm.org/
    ✗ CMake is required for Linux development.
      It is likely available from your distribution (e.g.: apt install cmake), or can be downloaded from https://cmake.org/download/
    ✗ ninja is required for Linux development.
      It is likely available from your distribution (e.g.: apt install ninja-build), or can be downloaded from https://github.com/ninja-build/ninja/releases
    ✗ GTK 3.0 development libraries are required for Linux development.
      They are likely available from your distribution (e.g.: apt install libgtk-3-dev)
    ✗ The blkid development library is required for Linux development.
      It is likely available from your distribution (e.g.: apt install libblkid-dev)
    ✗ The lzma development library is required for Linux development.
      It is likely available from your distribution (e.g.: apt install liblzma-dev)
[✓] Android Studio
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

Hi @Yuiry-IV 👋 !
Would it be possible for you to update to the latest stable Flutter release, and try again?
I believe the latest stable is 2.2.3 https://flutter.dev/docs/development/tools/sdk/releases

Hello @jorgecoca,
Thank you, it fix an issue :tada: !


Remove 5min connection timeout when restoring

The MongoDB database connection for the restore function had a 5 minute timeout, causing restores to fail with large collections that took more than 5mins to restore.
This PR removes the timeout.

Yup, good point. I'll add a note the readme.


Executing final e = <String, String>{}; returns exception 'Null check operator used on a null value'

Executing code
final e = <String, String>{};
or any other with empty map returns
The following _TypeError was thrown building Builder:
Null check operator used on a null value

The relevant error-causing widget was:
  MaterialApp MaterialApp:file:///C:/Projects-test/eval1/lib/main.dart:15:12
When the exception was thrown, this was the stack:
#0      compileSetOrMapLiteral (package:dart_eval/src/eval/compiler/collection/set_map.dart:53:21)
#1      parseLiteral (package:dart_eval/src/eval/compiler/expression/literal.dart:46:12)
#2      compileExpression (package:dart_eval/src/eval/compiler/expression/expression.dart:32:12)
#3      compileVariableDeclarationList (package:dart_eval/src/eval/compiler/statement/variable_declaration.dart:34:17)
#4      compileVariableDeclarationStatement (package:dart_eval/src/eval/compiler/statement/variable_declaration.dart:15:3)
#5      compileStatement (package:dart_eval/src/eval/compiler/statement/statement.dart:23:12)
#6      compileBlock (package:dart_eval/src/eval/compiler/statement/block.dart:17:20)
#7      compileFunctionDeclaration (package:dart_eval/src/eval/compiler/declaration/function.dart:84:14)

dart_eval: 0.7.4

Fixed in v0.7.5

Thank you! But looks like this issue has a continuation :(


bug: When two plugins with upstream configuration are used at the same time, the request is abnormal

When using two plugins with upstream configuration at the same time, the result will not be as expected.
For example:
dynamic-upstream and params-rewrite plugins.

There is no other upstream related plugin in this repository, how do I submit pr?

can you submit a mini test case first? the test case can reproduce this issue.

Without the cooperation of another plugin, the test cases are not well covered. I think we can create a branch to test the problem.

can you submit a mini test case first? the test case can reproduce this issue.

I know how to do it.

Without the cooperation of another plugin, the test cases are not well covered. I think we can create a branch to test the problem.

I know the solution.

This is not a bug.


feat: require port bindings to include inferface ip

Intention: binding to a port often unintentionally exposes services to the local network. Often seen when developers start databases in a Container and expose it via port-exposing to the local application. Sadly this is done often without limiting the port binding to localhost. Gets even worse when no password for the database is set up.
So this will warn when no Interfaces/HostIP is specified.

@salzig Hi! Thanks for suggestion and PR, I'll look for it and let you know if something needs to be adjust

@salzig Hello again.
Sorry for the long review.
I'm trying to find articles with good workarounds for local development where you don't need to set up IP explicitly and it's only decreasing readability (for documentation).
I suppose 'expose' would work for some cases, and maybe it should be validated then also.
Maybe you can help me with some good articles and examples?
It's not a blocker, but I want documentation to be clear and friendly for beginners.

@zavoloklom sorry for not responding. Sadly there isn't anything I know of other than adding the IP to the port. By default docker will expose all published ports to your local network.

@salzig It's ok, i cherry-picked your commit to next release branch, and I'm planning to release it within a week. Thank you for your contribution!

@salzig Hi! I released new version with this rule https://github.com/zavoloklom/docker-compose-linter/releases/tag/v2.0.0


[INTEGRATION][dbt] add dbt integration test

Dbt is tested reusing existing infrastructure for airflow. Test does not use openlineage.airflow, Airflow is used only as execution engine for dbt here.
https://github.com/OpenLineage/OpenLineage/issues/236
Signed-off-by: Maciej Obuchowski<EMAIL_ADDRESS>

Codecov Report

Merging #246 (df506d4) into main (b0f5000) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #246   +/-   ##
=======================================
  Coverage   87.64%   87.64%
=======================================
  Files          31       31
  Lines        1675     1675
=======================================
  Hits         1468     1468
  Misses        207      207

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 b0f5000...df506d4. Read the comment docs.


build(deps): update sqlalchemy to 2.0.0rc1

Thanks for this @gazorby - great to see an RC through:)
Shame about the sentry error - I can't see a standing issue for it so I might raise over there and see if I can get it fixed.

BTW, just waiting for a release with https://github.com/getsentry/sentry-python/pull/1812 in it for this. Maybe the official 2.0 release will beat it :D


(spurious?) failures in 640_proxy_restart_reattaches_test

https://circleci.com/gh/weaveworks/weave/3387
https://circleci.com/gh/weaveworks/weave/3378
https://circleci.com/gh/weaveworks/weave/3375

If the systemctl error is not the cause of the failure, then I would hypothesize that it is docker taking too long to reboot, so we should poll/wait, or something for that.

Agreed.  This will make some test runs faster, assuming we poll quicker than we sleep atm.

Per discussion in #1630 we believe there was some issue in Docker restarting containers that used -net=host, so I'm going to remove this from 1.2.1 milestone and we can review whether later Docker releases make this better.

I've just run in to this and tracked down one of the causes:
INFO: 2015/11/08 10:52:55.800420 proxy listening on tcp://<IP_ADDRESS>:12375
INFO: 2015/11/08 10:52:55.803458 Attaching container 02152dcefe35aafa17a318b05a7d21a7008ddb42609afb187018f3f445d757b4 with WEAVE_CIDR "<IP_ADDRESS>/24" to weave network
WARN: 2015/11/08 10:52:55.889482 Attaching container 02152dcefe35aafa17a318b05a7d21a7008ddb42609afb187018f3f445d757b4 to weave network failed: curl: (7) Failed to connect to <IP_ADDRESS> port 6784: Connection refused

This is due to #1556 - inserting a 2 second sleep just before the call to AttachExistingContainers solves that particular problem.

I've just run in to this and tracked down one of the causes:

https://github.com/weaveworks/weave/issues/1556#issuecomment-153330840

inserting a 2 second sleep just before the call to AttachExistingContainers 'solves' that particular problem.

Fixing this race between the proxy and the router starting up was one of the motivations for #1642.

Fixed by #1561


Release v0.8.0 "New Eyes"

This release makes some key changes, adds some essential functionality, and re-wires things under the hood. I am unilaterally adopting the model of naming releases after albums, because I am releasing this in Vienna and "Mozart's House" by Clean Bandit (New Eyes, track 1) has been stuck in my head throughout WordCamp Europe.
Autodiscovery
Autodiscovery is now supported via the WP.discover method (#181)
Bootstrapping
If you already have the API response object you want to bootstrap with, the .routes property from it can now be passed in when calling WP.site or instantiating a new WP object (also #181, documented #182):
var site = WP.site( 'http://my-endpoint.com/wp-json', endpointJSON.routes );

A script to ease the process of downloading this JSON object was added in PR #175
registerRoute
Arbitrary methods for custom endpoints can now be added without auto-discovery by using the .registerRoute method, which takes the same route configuration strings as register_rest_route in the API core.
Internal Re-Architecture
In #168 the innards of the library were totally gutted and re-written to support autodiscovery, registerRoute and bootstrapping.
Human-Readable names for HTTP verbs
PUT and POST are not the most intuitive words for what they do, and POST in particular caused a lot of semantic confusion with the post object within the WordPress data model. .post has become .create, and .put has become .update.
Upgraded Dependencies
Package dependencies and developer tools have all been updated to the latest version in their respective ranges.
Props
@props to the community that submitted code, bugs, issues, questions, or comments that added to & informed this release. I am a believer in celebrating contributions beyond code commits because this project would not be going anywhere were it not for the people using (or attempting to use) this package.
For general advice & conceptual validation:
@rmccue
For assisting with the discussion about how to handle autodiscovery
and custom route endpoints:
@adamsilverstein
@aedensixty
@andreipot
@artoliukkonen
@BenHen75
@chrishutchinson
@elyobo
@gnarf
@ishaan-puniani
@jasonphillips
@joehoyle
@jupitercow
@timmyc
For opening issues and asking questions:
@aedensixty
@dasheck0
@jsteranko
@nabeards
@satish9323
@stompweb
We still owe responses to, and have not forgotten the questions of:
@MurhafSousli
@smedegaard
@tommedema
@vtripolitakis

No code in this patch but retroactive commentary on the new APIs from #181, #176, and #180 are always welcome


Added fixes for Margin, Padding and Thickness properties with UseLayo…

Added fixes to resolve issues I raised in the issue #7798.
Even though Avalonia supports UseLayoutRounding - the pixel perfect positions were incorrectly calculated when scaling was present with objects that use Margins, Padding and Borders.
Margin was previously included in the calculation but the rounding was done after doing "availableSize = size - margin" and since rounding function is not linear the relation F(a) + F(b) == F(a + b) does not hold. That means that margin rounding to pixel perfect positions sometimes resulted in one pixel offset (visible in sample images).
The same treatment was never given to Padding and BorderThickness so I included those.
The goal of this fix is to support this layout rounding for all current and future users and I'm willing to make further fixes if needed.
List of Changes:
Layoutable.ArrangeCore - added separate rounding for Margin before any calculation.
LayoutHelper - added RoundLayoutThickness method
LayoutHelper.ArrangeChild - included a calculation of the rounding for padding and thickness if the parent uses LayoutRounding.
Border and ContentPresenter - added LayoutThickness private property that's passed to the renderer instead of BorderThickness. The LayoutThickness is calculated once and then cached. It makes sure that thickness will always be pixel perfect with UseLayoutRounding rather than having blurry edges in higher scales (to avoid borders looking blurry in 4k for example).

You can test this PR using the following package version. 0.10.999-cibuild0019488-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

@AndrejBunjac this looks great! I wonder if we have any tests that we can add to check this on CI?

You can test this PR using the following package version. 0.10.999-cibuild0019609-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0019659-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Also to reply to a comment from @jmacato. I would most likely want to add a ScreenShot test but I would need a way to be able to force the scaling to certain values for the test to make sense. I don't think that other type of test would make sense as this is a very visual issue visible only on a scaling different from 1.
Maybe I can do something with the TestRoot but I have to think about it.

I would most likely want to add a ScreenShot test but I would need a way to be able to force the scaling to certain values for the test to make sense. I don't think that other type of test would make sense as this is a very visual issue visible only on a scaling different from 1.

Agreed, and the problem with render tests is that they either have to be pixel perfect, or have to do a fuzzy match. The pixel perfect checks can fail on different machines, and the fuzzy tests aren't going to pick up such issues, so I'm fine with leaving this without render tests.

@AndrejBunjac hope you don't mind - I updated and fixed a merge error and made a small change too (moved some fields to the top of the class in Border).

Great! Looking forward to seeing the changes in action!
@grokys Of course I don't mind, you are the maintainer of Avalonia after all. :)
When can we expect these changes in a stable release?
(maybe it's a dumb question but I haven't picked up how you release new versions)

You can test this PR using the following package version. 0.10.999-cibuild0020087-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Hmm this seems to have caused a problem with context menus:

When can we expect these changes in a stable release?

Probably for the release after next, 0.10.15 - I wanted to leave some time to get some testing, and indeed we've found an issue as reported above ;)

Hmmmm, I will also try to figure it out in parallel with you guys as soon as I catch a breather from my regular work.

If I had to bet on something - I think the size of the popup might not be updated correctly with these changes. I'll look into it.

Thanks @AndrejBunjac - I've opened an issue with my initial findings here https://github.com/AvaloniaUI/Avalonia/issues/8092


Why IGMP does not implement SerializeTo method like other layers

I was surprised why IGMP layer does not implement SerializeTo method like other layers. Is there some special reason to do so? Or should it be fixed?

Serialization was added to the library after a number of layers were already implemented, IGMP included.  There hasn't yet been a comprehensive effort to implement serialization in every layer... instead we tend to wait for folks to need it.  If you'd like to implement IGMP serialization, we'd love to have it!  :D

Closing this after a 3 month of idle...


fix typo

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the master branch of freeCodeCamp.
[X] None of my changes are plagiarized from another source without proper attribution.
[X] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

changed virutal to virtual

Thank you @Kosmas for your contribution and congratulations on your first PR merge to this repo! 🎉
Hope to see more contributions from you in the future.


⚠ ClamAV has degraded performance

In 879f553, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 196 ms

Resolved: ClamAV performance has improved in 878d111.


LUTECE-2177 : Add CSRF tokens to ExternalFeaturesJspBean actions

The templates and JSP do not seem to be used elsewhere

Merged, Thanks !


Instantiate chrome via launch method, instead of using Launcher class directly.

Due to the fact that handleSIGINT is set by default as expected(true), I didn't add that property explicitly.

@nicolaivadim thanks!


changing values on config file doesn't have any effect

hi! everytime i try to set a custom timer for the work and the break i always get the default 90 minutes for the work and 15 minutes for the break even though on the config file i've set 1800 seconds (30 minutes) for the work and 300 seconds (5 minutes) for the break :thinking:  did i do something wrong? same goes for the pomo counter, i've set 4 and it still stay 5 :thinking: this is my config file values:
 // Time Configuration   const workTime = 1800; // in seconds   const breakTime = 300; // in seconds   const longBreakTime = 900; // in seconds   const longBreakEvery = 4; // long break every x pomos   const defaultPomoNumber = 4;   const workTimeRemind = 25;   const sendWorkTimeRemind = true;   const startingTime = 1800;   const noLastBreak = true;   const showHours = false; // true: time in hh:mm:ss; false: time in mm:ss always   const showHoursIf00 = false; // true: will show 00:mm:ss, false: will show mm:ss when hours is 0

i've even tried to wipe the folder and the config.js replacing with the latest 1.2.2 version but it still doens't want to change the values :thinking:

Are you sure your OBS overlay is pointing to the right file? I would make sure you are starting the setup again when re-downloading

It has been sometime since i got a response so I will be closing this issue as regarding it as a human error rather than code error the timer works for many 👍


Added --quiet option to suppress debug errors in console for the CLI implementation

@roikles What's the reasoning for suppressing the output?

@napcs The 'Refresh' notifications clutter up our debugging output from sass and jslint e.t.c. As I can see the browser window refresh most of the time it may not be necessary to log every browser refresh in the terminal output.
There have been situations in the past which have required some debugging of Livereload issues which is why I propose a 'quiet' flag rather than just supressing the output all together.

@roikles Hmmm. I can see that.
I'm not comfortable with this PR though. I think there should be a message that shows initially that displays the polling interval and the port. I'm fine with suppressing the reloading messages though, and I'm actually thinking it would be best if those messages were OFF by default and you would need a debugging flag on by default.
Care to convince me I'm wrong?

@napcs I agree that the initial message is important and I would be fine if the 'Refresh' messages are off by default I think its probably the best implementation.
I'll amend the PR so it can be tested. I'll also fix the spelling :-)

I have rewritten the PR based on your suggestions. Im not very familiar with coffescript so I just tried my best to rewrite the js in what to me looks like the same syntax.
Essentially this now suppresses the logs of 'Refresh: ...' and also 'Browser URL: ...'. but it doesn't affect any other essential error logs.

Any news on this @napcs?

@roikles I promise it's on the list. There are a couple other PRs that I have to merge at the same time because of Node 4.x.
It would be super helpful if you could convert the CoffeeScript to JS though using the CoffeeScript converter. Just run
cake build

to do that.  That way we're sure everything is correct.
(I plan to convert this from CoffeeScript to JS, just not right now.

@roikles nevermind, I'll convert and merge it. :)


AttributeError: 'OSC2ScenarioConfiguration' object has no attribute 'route' 'OSC2ScenarioConfiguration' object has no attribute 'route' No more scenarios .... Exiting

Describe our question or idea
Hi everyone, i follow this guide https://github.com/carla-simulator/scenario_runner/blob/master/Docs/README_OpenSCENARIO_2.0.md to run the demo, but the terminal show "AttributeError: 'OSC2ScenarioConfiguration' object has no attribute 'route' 'OSC2ScenarioConfiguration' object has no attribute 'route' No more scenarios .... Exiting", please give me some advise, thanks.
Screenshots

Desktop (please complete the following information):

OS: [e.g. Ubuntu 20.04]
CARLA Version [e.g. CARLA 0.9.15]
Python version [e.g. 3.8.10]
Version [e.g. 0.9.15]

Ran into same issue. Noticed OSC2ScenarioConfiguration did not chain up the init with super. Declaring __init__ in the child discards supers __init__ where the route variable is declared.
Calling super().__init__() adds those variables to the child class.
This seems to fix it.
# osc2_scenario_configuration.py
class OSC2ScenarioConfiguration(ScenarioConfiguration):
    def __init__(self, filename, client):
        super().__init__()```


cluster-info-dump is not easily parseable

Summary
After running microk8s inspect a file is created called cluster-info-dump that contains the output from kubectl cluster-info dump.
The issue is this file contains a mix of json and plain text, making it very difficult to parse (by humans or programatically)
Why is this important?
We would like to be able to generate a inspection report on a microk8s system and use automated tools to analyze the inspection report. This is difficult in it's current form.
Are you interested in contributing to this feature?
yes. I will submit a PR shortly.

Hi @SeanReece, it would have been great to have a tool to automate the processing of inspection reports. Is your work public/opensource anywhere? Thanks


Finalize the Leaderboard list app by adding the styles needed

Project name: Leaderboard - final touches
Project description: In this activity, the Leaderboard list app will be finalized by adding the styles needed to make it look great.
Project requirements:

At this point, a fully working app should have been ready that uses only basic styles to make the layout work, according to the wireframe.
Now the look and feel of the application should be improved, by adding the styles of choice.
Please keep the general layout of the wireframe, this is the only mandatory requirement.
Plain CSS or any CSS framework can also be used.

Project requirements link: https://github.com/microverseinc/curriculum-javascript/blob/main/leaderboard/m3_final_touches.md

Hi @lenkon Can you go on slack ?

Hi,
Yes, I can be on Slack.
Best Regards,
Konjengbam Inoulen Shanongba
On Fri, Feb 10, 2023 at 1:56 PM Yannick-Noel AKA @.***>
wrote:

Hi @lenkon https://github.com/lenkon Can you go on slack ?
—
Reply to this email directly, view it on GitHub
https://github.com/lenkon/leaderboard/pull/4#issuecomment-1425405278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3AA2JYMAVVAVKBBTF62V3WWX3TZANCNFSM6AAAAAAUXQFZLU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Integration tests bootstrap

Create a test suite with some test cases that use local blockchain features.

Test cases suggestions:

Catch contract outside class initialization error
When contract instantiation (new Contract()) is made outside of the component class it isn't reading tasit-sdk config properly (I think that could be because of babel transpiling).

Catch react-navigation wrong screen name string
When changing a Screen name without updating this.props.navigation.navigate(ScreenName).


Stuck training in server.py

I have installed all of the prerequisites. However, when I started running python server.py hex.conf command for training models, it's stuck after the following two lines:
2019-05-18 20:47:53,750592 [INFO    ]  checking if generation data available
2019-05-18 20:47:53,750715 [INFO    ]  Not such file for generation: [Errno 2] No such file or directory: u'/root/ggpzero/galvanise_zero/data/hex/d2/gendata_hex_0.json.gz'

Could you please give me any guidance?

That's ok.  Just means no self play data exists yet for that generation.  Once train for a while will save the file in that location.  If you restart the server will pick up from last point it was saved.

I don't know if something is wrong with my installation. But there isn't any error displaying and just continually output the same sentence every ten minutes. It seems they're not training and no self-play data is stored.
2019-05-19 09:11:47,561940 [VERBOSE ]  entering checkpoint with 0 sample accumulated
2019-05-19 09:21:47,661234 [VERBOSE ]  entering checkpoint with 0 sample accumulated
2019-05-19 09:31:47,760546 [VERBOSE ]  entering checkpoint with 0 sample accumulated

Hi.  Bear with me, I am trying to write some docs to get you going.
In the meantime I pushed a revamped test in src/test/player/test_player.py.
The first thing to do after installing should be to run these tests.  (and I can use the below for docs!)
First you'll need to checkout gzero_data repo.  The test will be using breakthroughSmall, you can copy the rulesheet into ggplib/data/rulesheets.  And test with
python perftest.py breakthroughSmall in ggplib/src/ggplib/scripts
Then copy the breakthroughSmall directory in gzero_data into the data directory to the galavanise_zero repo.
Then can run the 3 tests in src/test/player/test_player.py
$ py.test test_player.py  -s -k test_random
This will test a random neural network against a simplemcts player.  It will lose!
$ py.test test_player.py  -s -k test_trained
This will test a trained neural network against a simplemcts player.  The model is very strong.  It will win easily.
$ py.test test_player.py  -s -k test_puct_v2
This will test two gzero players against each other.  They use a reasonable strong network, but one uses the puct1 player and the other is puct2 player.  puct1 player is what is used for self play, and puct2 is used for match mode and has many more (experimental) features - not least batching on the GPU, so is much faster.
Note, I aim to merge puct1/puct2 at some point.
Let me know how that goes please, and I will work on some decent instructions for training.
Feel free to play around with options etc. :)
PS a number of unit tests have rotted over time.  I will also aim to fix those.


Introduce compatibility with stimulus-reflex 3.4

The javascript for stimulus-reflex changed the parameter permanent_attribute_name to permanentAttributeName`. So this PR aims to fix this incompatibility.

Codecov Report

Merging #38 (3859456) into master (c91cd4c) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master     #38      +/-   ##
=========================================
- Coverage    2.71%   2.68%   -0.03%
=========================================
  Files          12      12
  Lines         295     298       +3
  Branches       30      31       +1
=========================================
  Hits            8       8
- Misses        287     290       +3

Impacted Files
Coverage Δ

sockpuppet/consumer.py
0.00% <0.00%> (ø)

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 c91cd4c...3859456. Read the comment docs.


[Bug]: RuntimeError: dictionary changed size during iteration

What happened?

I'm doing some batch embeddings creations and get a lot of these exceptions
Versions
0.3.22.dev17
Relevant log output
2023-04-17 11:23:45 2023-04-17 18:23:45 ERROR    chromadb.server.fastapi dictionary changed size during iteration
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 94, in receive
2023-04-17 11:23:45     return self.receive_nowait()
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 89, in receive_nowait
2023-04-17 11:23:45     raise WouldBlock
2023-04-17 11:23:45 anyio.WouldBlock
2023-04-17 11:23:45
2023-04-17 11:23:45 During handling of the above exception, another exception occurred:
2023-04-17 11:23:45
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 43, in call_next
2023-04-17 11:23:45     message = await recv_stream.receive()
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 114, in receive
2023-04-17 11:23:45     raise EndOfStream
2023-04-17 11:23:45 anyio.EndOfStream
2023-04-17 11:23:45
2023-04-17 11:23:45 During handling of the above exception, another exception occurred:
2023-04-17 11:23:45
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/chroma/./chromadb/server/fastapi/__init__.py", line 47, in catch_exceptions_middleware
2023-04-17 11:23:45     return await call_next(request)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 46, in call_next
2023-04-17 11:23:45     raise app_exc
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 36, in coro
2023-04-17 11:23:45     await self.app(scope, request.receive, send_stream.send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 75, in __call__
2023-04-17 11:23:45     raise exc
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 64, in __call__
2023-04-17 11:23:45     await self.app(scope, receive, sender)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
2023-04-17 11:23:45     raise e
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
2023-04-17 11:23:45     await self.app(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 680, in __call__
2023-04-17 11:23:45     await route.handle(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 275, in handle
2023-04-17 11:23:45     await self.app(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 65, in app
2023-04-17 11:23:45     response = await func(request)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 231, in app
2023-04-17 11:23:45     raw_response = await run_endpoint_function(
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 162, in run_endpoint_function
2023-04-17 11:23:45     return await run_in_threadpool(dependant.call, **values)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/concurrency.py", line 41, in run_in_threadpool
2023-04-17 11:23:45     return await anyio.to_thread.run_sync(func, *args)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/to_thread.py", line 31, in run_sync
2023-04-17 11:23:45     return await get_asynclib().run_sync_in_worker_thread(
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
2023-04-17 11:23:45     return await future
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 867, in run
2023-04-17 11:23:45     result = context.run(func, *args)
2023-04-17 11:23:45   File "/chroma/./chromadb/server/fastapi/__init__.py", line 158, in add
2023-04-17 11:23:45     result = self._api._add(
2023-04-17 11:23:45   File "/chroma/./chromadb/api/local.py", line 140, in _add
2023-04-17 11:23:45     self._db.add_incremental(collection_uuid, added_uuids, embeddings)
2023-04-17 11:23:45   File "/chroma/./chromadb/db/clickhouse.py", line 542, in add_incremental
2023-04-17 11:23:45     index.add(uuids, embeddings)
2023-04-17 11:23:45   File "/chroma/./chromadb/db/index/hnswlib.py", line 148, in add
2023-04-17 11:23:45     self._save()
2023-04-17 11:23:45   File "/chroma/./chromadb/db/index/hnswlib.py", line 187, in _save
2023-04-17 11:23:45     pickle.dump(self._label_to_id, f, pickle.HIGHEST_PROTOCOL)
2023-04-17 11:23:45 RuntimeError: dictionary changed size during iteration
2023-04-17 11:23:45 2023-04-17 18:23:45 INFO     uvicorn.access  <IP_ADDRESS>:48976 - "POST /api/v1/collections/mimessage-embeddings/add HTTP/1.1" 500
2023-04-17 11:23:45 2023-04-17 18:23:45 ERROR    chromadb.server.fastapi dictionary changed size during iteration
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 94, in receive
2023-04-17 11:23:45     return self.receive_nowait()
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 89, in receive_nowait
2023-04-17 11:23:45     raise WouldBlock
2023-04-17 11:23:45 anyio.WouldBlock
2023-04-17 11:23:45
2023-04-17 11:23:45 During handling of the above exception, another exception occurred:
2023-04-17 11:23:45
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 43, in call_next
2023-04-17 11:23:45     message = await recv_stream.receive()
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/streams/memory.py", line 114, in receive
2023-04-17 11:23:45     raise EndOfStream
2023-04-17 11:23:45 anyio.EndOfStream
2023-04-17 11:23:45
2023-04-17 11:23:45 During handling of the above exception, another exception occurred:
2023-04-17 11:23:45
2023-04-17 11:23:45 Traceback (most recent call last):
2023-04-17 11:23:45   File "/chroma/./chromadb/server/fastapi/__init__.py", line 47, in catch_exceptions_middleware
2023-04-17 11:23:45     return await call_next(request)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 46, in call_next
2023-04-17 11:23:45     raise app_exc
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/base.py", line 36, in coro
2023-04-17 11:23:45     await self.app(scope, request.receive, send_stream.send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 75, in __call__
2023-04-17 11:23:45     raise exc
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 64, in __call__
2023-04-17 11:23:45     await self.app(scope, receive, sender)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
2023-04-17 11:23:45     raise e
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
2023-04-17 11:23:45     await self.app(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 680, in __call__
2023-04-17 11:23:45     await route.handle(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 275, in handle
2023-04-17 11:23:45     await self.app(scope, receive, send)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 65, in app
2023-04-17 11:23:45     response = await func(request)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 231, in app
2023-04-17 11:23:45     raw_response = await run_endpoint_function(
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 162, in run_endpoint_function
2023-04-17 11:23:45     return await run_in_threadpool(dependant.call, **values)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/starlette/concurrency.py", line 41, in run_in_threadpool
2023-04-17 11:23:45     return await anyio.to_thread.run_sync(func, *args)
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/to_thread.py", line 31, in run_sync
2023-04-17 11:23:45     return await get_asynclib().run_sync_in_worker_thread(
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
2023-04-17 11:23:45     return await future
2023-04-17 11:23:45   File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 867, in run
2023-04-17 11:23:45     result = context.run(func, *args)
2023-04-17 11:23:45   File "/chroma/./chromadb/server/fastapi/__init__.py", line 158, in add
2023-04-17 11:23:45     result = self._api._add(
2023-04-17 11:23:45   File "/chroma/./chromadb/api/local.py", line 140, in _add
2023-04-17 11:23:45     self._db.add_incremental(collection_uuid, added_uuids, embeddings)
2023-04-17 11:23:45   File "/chroma/./chromadb/db/clickhouse.py", line 542, in add_incremental
2023-04-17 11:23:45     index.add(uuids, embeddings)
2023-04-17 11:23:45   File "/chroma/./chromadb/db/index/hnswlib.py", line 148, in add
2023-04-17 11:23:45     self._save()
2023-04-17 11:23:45   File "/chroma/./chromadb/db/index/hnswlib.py", line 187, in _save
2023-04-17 11:23:45     pickle.dump(self._label_to_id, f, pickle.HIGHEST_PROTOCOL)
2023-04-17 11:23:45 RuntimeError: dictionary changed size during iteration

@jonluca we are looking into this

We've improved a lot of consistency issues with 0.4+. Closing this issues but please feel free to re-open it if this comes up again.


feat: customize useHomeStorage

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@mario-mui Note the comment above about actually replacing the underlying storageApi instead; closing this for now


adding shadow to the exapanding edge

Thanks for sharing this useful lib. Is there a mechanism to style the expanding edge with shadow?

No, that is left to the system. If you set an elevation on the expandablelayout it should work - don't forget to set a background color.
Closing as this isn't an issue with the library.