Skin layers are quite visible up close.

It might be worth it to add a pixel on the y axis to close individual layers.  Match it to the color of the pixel its connected to to blend it in.  Corners would be odd.  Averaging the color of both connected faces would be best.  Priority matching would probably be fine for most skins (match front before sides and sides before back).

I guess you're talking about the armor? The issue with the armor is that it doesn't have any faces on the inside, and even adding them would not give a texture there, and even the texture would break with resource packs. I only see two options to make the armor less stupid than it looks right now: 3d modeled armor(bedrock/dungeons like) or trying to apply the 3d-ification that is also done on the skin 2nd layer to make the armor have real depth(would probably break again on non 16x texture packs).

I guess you're talking about the armor? The issue with the armor is that it doesn't have any faces on the inside, and even adding them would not give a texture there, and even the texture would break with resource packs. I only see two options to make the armor less stupid than it looks right now: 3d modeled armor(bedrock/dungeons like) or trying to apply the 3d-ification that is also done on the skin 2nd layer to make the armor have real depth(would probably break again on non 16x texture packs).

As you can see in the Following Screenshot the Bottom Layers actually exist, they are just in the Ground Block and therefore not visible. I agree, that its not needed to bled in some extra layers, but maybe in the future it could be possible to set a Feet-Height.
In the Screenshot the bottom layer seems black, but thats caused by the shader and boots-enchantment.

I can't quiet follow you what you mean? that the lower part of the boots/feet clip into the ground while sneaking is a normal vanilla issue that probably doesn't have a not odd looking fix?

I mean… Offsetting the player model by half a pixel on the y axis when one wears boots could look fine and solve this part of the issue. And since the armor model is hard-coded you could perhaps optionally inject your own shrunk variation, simply making the armor model tighter on the first person model.

This basically is now related to making 3d-skin-layers work with armor. So will be tracked over there.


🐛 BUG: In non-Astro workspaces, the extension warn about not being able to find Astro abusively

Describe the Bug
Currently, when opening Astro files outside of an Astro workspace, the extension will complain about not being able to find Astro. This is valid, however it's very annoying for users. It'd be great if the following happened:

If an Astro file is opened inside a non-Astro workspace, we should warn once, and only once about not being able to find Astro and that the experience might be degraded
When multiple workspaces (folders) are opened, we should check if the folder is an Astro project before warning. Otherwise, users see the warning for every single folder, which is very annoying, especially considering those folders are not even Astro related

Those two behavior are pretty undesirable, we should make sure the extension is helpful in cases where it matters and otherwise be as invisible as possible
Steps to Reproduce

Open an Astro file in an untitled workspace

Extension warn multiple times about not being able to find Astro

Open multiple folders, with one of them being an Astro project

Extension warn that Astro couldn't be found in every opened folder

Alternatively it would be helpful to add extension setting to disable Astro extension warning altogether


I want to improve markdown editor page

Describe the bug
A clear and concise description of what the bug is.
@Bashamega I want to improve the buttons and navbar of markdown editor and also make it responsive
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

sure

done


https://[cname_domain]/hubpress doesn't work

https://[cname_domain]/hubpress for custom domain-hosted (CNAME) blogs.
The note that appears (following) isn't clear, and doesn't provide a solution. I can't enter the administration console when using a [cname domain]
"If you are using a CNAME, you might need to access your Administration console using the https://.github.io address pattern initially, so your CNAME redirect will work."

In my case it's trying to open a 404, and looks to be unig [repositoryname] where it shouldn't:
http://centroslibres.org/centroslibres/themes/casper/theme.json?dt=1475226009017
Here's my source https://github.com/somosazucar/centroslibres

This is the same as https://github.com/HubPress/hubpress.io/issues/244 I guess

I'll check this in the docs next time I'm doing a bug fix run.

Thanks! I loved hubpress but I haven't been able to make it work reliably.

I was having the same issue and discovered that you can add the CNAME to config.json and everything seems to work.
 {   "meta": {    "username": "username or organization",    "repositoryName": "blog",     "cname": "blog.example.com",     "branch": "gh-pages"   },   "theme": {     "name": "Casper"   } }

Thanks! That solved the issue for me! Would be nice to make a findable comment in documentation.

Yep, I'll look at making this more discoverable in the GitBook hosted docs.
Sent from Mobile.

Hi,
@jasonbullard @icarito did you set the CNAME in the settings of your repository?
HubPress do not work yet with this option, it still works with the CNAME file.

I can confirm that @ jasonbullard 's tip worked for me. Otherwise URLS
were not constructed correctly.
It would be ideal to only change this in one place. Or prominently
documented.
Also the program doesn't offer very friendly error messages...
El 04/10/16 a las 03:57, Anthonny Quérouil escribió:

Hi,
@jasonbullard https://github.com/jasonbullard @icarito
https://github.com/icarito did you set the CNAME in the settings of
your repository?
HubPress do not work yet with this option, it still works with the
CNAME file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HubPress/hubpress.io/issues/442#issuecomment-251332522,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMMS_9LtgWe6k3XTTCy9uhSFDt5xNe1ks5qwhT9gaJpZM4KK4QS.

FYI, actually i can't set the custom domain of a repository with the Github API
See https://twitter.com/anthonny_q/status/783771728719835140

Next action:

Update https://hubpress.gitbooks.io/hubpress-knowledgebase/content/admin/access_admin_console.html with a better admonition.
Create an article about setting the CNAME in both places.
Note that GitHub can not set CNAME.


Add code of conduct

By merging this PR, the initiators of this project hereby pledge that they will take responsibility for establishing and maintaining an inclusive and positive contribution experience to this project, as stated in the committed CODE_OF_CONDUCT.md file.
In more detail, this PR adapts the Contributor Covenant Code of Conduct in its original form, since I think it reflects our values and the environment we want to create really well.
Proposals for adaptions are highly welcome, otherwise I would go with the vanilla version for now.

Looks great!
One thing I like is if enforcement is clearly defined, but on the other hand it might highly depend on the actual case. Considering that I would leave it as is and merge it.

Yeah, I think we can still refine it later on, since I currently have no specific ideas on how to make it unambiguous. I think this all comes with more experience later on, so I suggest we will revisit it after a while to get more specific.


build: Don't require glslang if not building layers

This makes distribution packaging easier.

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

Thanks @chewi!


update tilelive-omnivore

clamping rasters at z0 (via mapnik-omnivore)

Uhh I have no idea why there are some updated tests related to logging - even copied straight from master. Perhaps my text editor is making some updates?


Adding support for channel search and autocomplete.

Just needs a rebase and good to go

For posterity, here's a loadtest run against 5.0.0 with these changes:
Loadtest Results
Score: 239.03
The score is the average of the 95th percentile, median and interquartile ranges in the routes below.
Routes
/channels/CID/members

Metric
Actual

Hits
1901

Error Rate
0.00%

Mean Response Time
3.41ms

Median Response Time
3.00ms

95th Percentile
4.00ms

/channels/CID/members/me

Metric
Actual

Hits
1450

Error Rate
0.00%

Mean Response Time
2.62ms

Median Response Time
2.00ms

95th Percentile
3.00ms

/channels/CID/posts

Metric
Actual

Hits
1450

Error Rate
0.00%

Mean Response Time
1.82ms

Median Response Time
1.00ms

95th Percentile
4.00ms

/channels/CID/stats

Metric
Actual

Hits
1450

Error Rate
0.00%

Mean Response Time
1.14ms

Median Response Time
1.00ms

95th Percentile
2.00ms

/channels/members/me/view

Metric
Actual

Hits
1450

Error Rate
0.00%

Mean Response Time
10.78ms

Median Response Time
10.00ms

95th Percentile
15.00ms

/files

Metric
Actual

Hits
6

Error Rate
0.00%

Mean Response Time
1213.67ms

Median Response Time
1239.00ms

95th Percentile
1602.50ms

/files/PID/thumbnail

Metric
Actual

Hits
149

Error Rate
0.00%

Mean Response Time
50.56ms

Median Response Time
35.00ms

95th Percentile
106.50ms

/hooks/incoming

Metric
Actual

Hits
49

Error Rate
0.00%

Mean Response Time
16.29ms

Median Response Time
16.00ms

95th Percentile
20.00ms

/posts

Metric
Actual

Hits
215

Error Rate
0.00%

Mean Response Time
31.12ms

Median Response Time
29.00ms

95th Percentile
37.50ms

/posts/PID/files/info

Metric
Actual

Hits
174

Error Rate
0.00%

Mean Response Time
0.63ms

Median Response Time
0.00ms

95th Percentile
3.00ms

/teams/TID/channels

Metric
Actual

Hits
137

Error Rate
0.00%

Mean Response Time
4.69ms

Median Response Time
4.00ms

95th Percentile
11.00ms

/teams/TID/channels/autocomplete

Metric
Actual

Hits
260

Error Rate
0.00%

Mean Response Time
6.25ms

Median Response Time
6.00ms

95th Percentile
11.00ms

/teams/TID/channels/search

Metric
Actual

Hits
2216

Error Rate
0.00%

Mean Response Time
4.93ms

Median Response Time
5.00ms

95th Percentile
9.00ms

/teams/TID/posts/search

Metric
Actual

Hits
44

Error Rate
0.00%

Mean Response Time
6.30ms

Median Response Time
5.00ms

95th Percentile
14.50ms

/users/UID/active

Metric
Actual

Hits
500

Error Rate
0.00%

Mean Response Time
110.99ms

Median Response Time
114.00ms

95th Percentile
204.00ms

/users/email/UID

Metric
Actual

Hits
500

Error Rate
0.00%

Mean Response Time
36.70ms

Median Response Time
31.00ms

95th Percentile
101.00ms

/users/status/ids

Metric
Actual

Hits
13072

Error Rate
0.00%

Mean Response Time
1.57ms

Median Response Time
1.00ms

95th Percentile
2.00ms


fix: Add missing mix.lock changes

Somehow I missed this in my commits for #42 :(

🚀 Thank you for your contribution! 🚀


IONe UI type Object fields editor

Should be an
input[key]: input[value]
Only one level!

Resolved in #81


Optionally support production style URL format http://accountname.localhost/container

We have extensive and multi-layered code base which assumes production style URL format
https://accountname.core.windows.net/container
We have looked what would it take to support emulated format
http://localhost/accountname/container and due to code layout and assumptions of which part of URL means what in various layers, it would be extensive and error-prone.
This ask is to optionally support production style URL format
http://accountname.localhost/container
We will take care of name resolution, say via hosts file, or via local DNS server so that accountname.localhost resolves to <IP_ADDRESS>
But we need help in routing layers so that URL parts are properly recognized if some flag is set (e.g. set AZURITE_URL_STYLE=PRODUCTION, or set AZURITE_USE_PRODUCTION_URL_STYLE=1)
Can you please send some code pointers of which places we'd need to change so that we can prototype this change?
Thanks!

Hi @ayeltsov Personally like the idea to have a flag for switch!
Please refer to this where Azurite parser account, container, and blob names from request.
https://github.com/Azure/Azurite/blob/be4dc2c9d44e3ba643e616795c26cb48dedd5c8e/src/blob/middlewares/blobStorageContext.middleware.ts#L54
queue service has a similar queueStorageContext.middleware.ts too.

There are some further updates after PR https://github.com/Azure/Azurite/pull/416 @ayeltsov likes to have following updates.
tests
documentation
Some configuration options:
add custom domain name (for example, if someone wants to mock .blob.core.windows.net, they should be able to do this)
also considering to add option to any domain suffix (e.g. http[s]://account.*/container


Tables: Cannot color an entire row in v3

Framework Version: v3

Flavor used: default

Browser: Firefox 60 and Chromium 66

Code to reproduce: https://gist.github.com/SkewedZeppelin/11928804db4172b9eb84a8243b2d70cc

Bug description: Coloring an entire row of a table by applying an inline color style to a
 element does not work, but previously worked in v2.3.7.

Screenshots:
v2.3.7

v3

Due to the way Gluon is coded, inline styles will not work exactly like that. But you have two other options:

Use a class on the tr that applies a style to children (not preferred):

tr.my-class > td {
  color: red;
}

Alter the CSS variable in the parent element, children will inherit it (best practice):

  Data here
  More data

Sorry for the long wait, but I hope this will help you resolve your issue.

The second method worked perfectly. Congratulations on the release :tada:!


Ability to set the current angle or progress instead of just start

I was able to work around the limitation by using a synthesized MoutionEvent.

@AddictArts Sorry, what do you mean?

For example a seek bar has setProgress. Currently you can indicate a start, but not externally set it programatically. I worked around this by using a synthetic onTouch event like so:
private fun setVolumeControlViewProgress(v: VolumeControlView, progress: Int) {
    val w: Int = v.width
    val h: Int = v.height
    val controllerCenter = PointF().apply {
        x = w / 2f
        y = h / 2f
    }
    val controllerRadius = if (w > h) h / CONTROLLER_SPACE else w / CONTROLLER_SPACE
    val restoreTouchPoint = getPointOnBorderLineOfCircle(controllerCenter, controllerRadius, (progress *  360) / 100)
    val motionEvent = MotionEvent.obtain(0, 0, MotionEvent.ACTION_DOWN, restoreTouchPoint.x, restoreTouchPoint.y, 0)

    v.onTouch(contentView!!, motionEvent)
}


Document the Nix code and make it more maintainable

@balsoft Is this already ini progress? I thought you mentioned you'd been working on this?

Also, this might be a duplicate of #10003?

Implemented and merged here: https://github.com/MinaProtocol/mina/pull/12287

@michal0mina This issue is in the Done column, but still not closed. What is the correct status, in your opinion? Can we close this issue?

@robinbb yes, we can close.


Tag/Release when extension is updated on martketplace?

Would it be possible to tag/release the repository when the extension is updated on marketplace?

Yeah, I need to automate the release process so that this all done in a GH action (haven't had time to do that yet)

I did not test it, but assuming, you stick with the "release vX.X.X" commit message.
Something like below should do the trick (I can do a PR):
n:
  push:
    branches: main

name: Release

jobs:
  create_release:
    runs-on: ubuntu-latest
    if: startsWith(github.event.head_commit.message, 'release')
    steps:
      - uses: actions/checkout@v3
      - name: Set version from commit message
        id: tag_id
        run: |
          VAR="${{ github.event.head_commit.message }}"
          TAG="${VAR#* }"
          echo ::set-output name=tag::"${TAG}"
          echo "${TAG}"
      - name: Set release name
        id: release_id
        run: |
          echo ::set-output name=releasename::"${{ steps.tag_id.outputs.tag }}"
      - name: Bump version and push tag
        id: tag_version
        uses<EMAIL_ADDRESS>        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          default_bump: false
          custom_tag: ${{ steps.tag_id.outputs.tag }}
          tag_prefix: ""
      - name: Create Release
        uses: ncipollo/release-action@v1
        with:
          tag: ${{ steps.tag_version.outputs.new_tag }}
          name: ${{ steps.release_id.outputs.releasename }}
          generateReleaseNotes: true
          allowUpdates: false
          token: ${{ secrets.GITHUB_TOKEN }}

Just tested the GHA I wrote above in https://github.com/mcanouil/test-release-gha


UI text cut off unnecessarily

Describe the bug
A lot of the UI text is cut off unnecessarily, resulting in a lot of usability issues. Usually the last character is missing, so units are missing from post ages, the last digit is missing from follower/following counts, etc.
To Reproduce
Steps to reproduce the behavior:

Open essentially any screen in the app
Look for incomplete text

Expected behavior
All text should be shown completely, where space is available.
Screenshots
Feed:

Compose:

Details

Platform: Android
Platform version: Android 10, OxygenOS 10.0.1
App version: 1.37.0 (23) production

Additional context
Note that this is with no changes to default fonts, text size, etc. Using accessibility features to make the font smaller doesn't resolve this issue.

Thanks, yep - I had this on my nearterm todos. I have no idea why android is acting like this! Hope I can figure it out

I switched my phone from its default font (OnePlus Slate) to Noto Sans (the only other option available), and it seems to resolve the issue for me.

Hi! This still happens to me on my Galaxy S22 on the default font. Changing fonts fixes the issue but it's odd that it's happening in the first place.
Build version: <IP_ADDRESS>7; Bundle info: 5f2c81ca6 (prod); Bundle date: 24090211; Platform: android


(BKR-840) Added a new file test_run.md and deleted Overview.md

@Sukanyade2014 there are a number of places where we link to the overview doc. Please delete or change those links as necessary.
Also, for doc commits, you can make the commit message multiline and make one of the lines this text to make sure that CI doesn't run on the PR:
[skip ci]

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2599/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2597/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2612/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2613/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2618/

since this is all .md files, I'm fine with merging it without testing.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2625/


[Request] Port luci-app-rtorrent

Source code can be found here.
https://github.com/wolandmaster/luci-app-rtorrent

I'd appreciate if the author himself, @wolandmaster, decides to upstream it. I'm not going to simply copy his package, especially as I am unable to actually maintain it.


Add numpy-to-VTK conversion and instructions for VTK-enabled 3D rendering

Are "instructions" a "demo"?

Yeah, pretty much

-- Gabe, just now

As discussed recently: https://github.com/Kitware/VTK/blob/master/Wrapping/Python/vtk/util/numpy_support.py


Do not resolve apparent type of mapped types with a tuple constraint

fixes https://github.com/microsoft/TypeScript/issues/52650

@typescript-bot test this
@typescript-bot test top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot test tsserver top100
@typescript-bot run dt
@typescript-bot perf test this

@typescript-bot run dt but new and improved with more response post-backs

How can I see those failures?

It's nothing you did; just a timeout.
@typescript-bot run dt


[Bug]: Fail to run with a local LLM (Ollama)

Do you need to file an issue?

[X] I have searched the existing issues and this bug is not already filed.
[ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[X] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the bug
Fail to run with locally installed Ollama ...
Steps to reproduce
Ollama
ollama list
NAME                         ID              SIZE      MODIFIED
llama3.1:latest              42182419e950    4.7 GB    31 seconds ago
nomic-embed-text:latest      0a109f422b47    274 MB    3 days ago

Input
mkdir -p ./t2/input
cp the-heart-sutra.txt ./t2/input/

the-heart-sutra.txt
Init
python -m graphrag.index --init --root t2

Initializing project at t2

Modify settings.yaml to use local llama2:latest and nomic-embed-text:
llm:
  model: llama3.1:latest
  model_supports_json: true # recommended if this is available for your model.
  api_base: http://localhost:11434/v1

embeddings:
  llm:
    model: nomic-embed-text
    api_base: http://localhost:11434/api

Index
python -m graphrag.index --root t2

Expected Behavior
GraphRAG should index the text file ...
GraphRAG Config Used

encoding_model: cl100k_base
skip_workflows: []
llm:
  api_key: ${GRAPHRAG_API_KEY}
  type: openai_chat # or azure_openai_chat
  model: llama3.1:latest
  model_supports_json: true # recommended if this is available for your model.
  # max_tokens: 4000
  # request_timeout: 180.0
  api_base: http://localhost:11434/v1
  # api_version: 2024-02-15-preview
  # organization: <organization_id>
  # deployment_name: <azure_model_deployment_name>
  # tokens_per_minute: 150_000 # set a leaky bucket throttle
  # requests_per_minute: 10_000 # set a leaky bucket throttle
  # max_retries: 10
  # max_retry_wait: 10.0
  # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
  # concurrent_requests: 25 # the number of parallel inflight requests that may be made
  # temperature: 0 # temperature for sampling
  # top_p: 1 # top-p sampling
  # n: 1 # Number of completions to generate

parallelization:
  stagger: 0.3
  # num_threads: 50 # the number of threads to use for parallel processing

async_mode: threaded # or asyncio

embeddings:
  ## parallelization: override the global parallelization settings for embeddings
  async_mode: threaded # or asyncio
  # target: required # or all
  # batch_size: 16 # the number of documents to send in a single request
  # batch_max_tokens: 8191 # the maximum number of tokens to send in a single request
  llm:
    api_key: ${GRAPHRAG_API_KEY}
    type: openai_embedding # or azure_openai_embedding
    model: nomic-embed-text
    api_base: http://localhost:11434/api
    # api_version: 2024-02-15-preview
    # organization: <organization_id>
    # deployment_name: <azure_model_deployment_name>
    # tokens_per_minute: 150_000 # set a leaky bucket throttle
    # requests_per_minute: 10_000 # set a leaky bucket throttle
    # max_retries: 10
    # max_retry_wait: 10.0
    # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
    # concurrent_requests: 25 # the number of parallel inflight requests that may be made

chunks:
  size: 1200
  overlap: 100
  group_by_columns: [id] # by default, we don't allow chunks to cross documents

input:
  type: file # or blob
  file_type: text # or csv
  base_dir: "input"
  file_encoding: utf-8
  file_pattern: ".*\\.txt$"

cache:
  type: file # or blob
  base_dir: "cache"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

storage:
  type: file # or blob
  base_dir: "output/${timestamp}/artifacts"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

reporting:
  type: file # or console, blob
  base_dir: "output/${timestamp}/reports"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

entity_extraction:
  ## strategy: fully override the entity extraction strategy.
  ##   type: one of graph_intelligence, graph_intelligence_json and nltk
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/entity_extraction.txt"
  entity_types: [organization,person,geo,event]
  max_gleanings: 1

summarize_descriptions:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/summarize_descriptions.txt"
  max_length: 500

claim_extraction:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  # enabled: true
  prompt: "prompts/claim_extraction.txt"
  description: "Any claims or facts that could be relevant to information discovery."
  max_gleanings: 1

community_reports:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/community_report.txt"
  max_length: 2000
  max_input_length: 8000

cluster_graph:
  max_cluster_size: 10

embed_graph:
  enabled: false # if true, will generate node2vec embeddings for nodes
  # num_walks: 10
  # walk_length: 40
  # window_size: 2
  # iterations: 3
  # random_seed: 597832

umap:
  enabled: false # if true, will generate UMAP embeddings for nodes

snapshots:
  graphml: false
  raw_entities: false
  top_level_nodes: false

local_search:
  # text_unit_prop: 0.5
  # community_prop: 0.1
  # conversation_history_max_turns: 5
  # top_k_mapped_entities: 10
  # top_k_relationships: 10
  # llm_temperature: 0 # temperature for sampling
  # llm_top_p: 1 # top-p sampling
  # llm_n: 1 # Number of completions to generate
  # max_tokens: 12000

global_search:
  # llm_temperature: 0 # temperature for sampling
  # llm_top_p: 1 # top-p sampling
  # llm_n: 1 # Number of completions to generate
  # max_tokens: 12000
  # data_max_tokens: 12000
  # map_max_tokens: 1000
  # reduce_max_tokens: 2000
  # concurrency: 32

Logs and screenshots
Logging enabled at /home/ohho/codes/python/try/graphrag/t2/output/indexing-engine.log
/home/ohho/conda/envs/graphrag/lib/python3.10/site-packages/numpy/core/fromnumeric.py:59: FutureWarning:
'DataFrame.swapaxes' is deprecated and will be removed in a future version. Please use 'DataFrame.transpose' instead.
  return bound(*args, **kwds)
🚀 create_base_text_units
                                 id  ... n_tokens
0  6d2823d11f18b1dbb3e9c4d3a1a7b3bf  ...      401

[1 rows x 5 columns]
🚀 create_base_extracted_entities
                                        entity_graph
0  <graphml xmlns="http://graphml.graphdrawing.or...
🚀 create_summarized_entities
                                        entity_graph
0  <graphml xmlns="http://graphml.graphdrawing.or...
❌ create_base_entity_graph
None
⠇ GraphRAG Indexer
├── Loading Input (text) - 1 files loaded (0 filtered) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00 0:00:00
├── create_base_text_units
├── create_base_extracted_entities
├── create_summarized_entities
└── create_base_entity_graph
❌ Errors occurred during the pipeline run, see logs for more details.

Additional Information

GraphRAG Version: v0.3.6
Operating System: Ubuntu 22.04.4 LTS
Python Version: 3.10
Related Issues:

"Error Invoking LLM"

Embeddings API
curl http://localhost:11434/api/embeddings -d '{
>  "model": "nomic-embed-text",
>  "prompt": "Good morning"
> }'

{"embedding":[-0.9532470703125,-0.457611083984375,-3.6005859375,-0.163177490234375,-0.8304443359375,0.8436279296875,0.058013916015625,-0.48779296875,-0.018356800079345703,-1.24462890625,1.359619140625,1.21435546875,1.44140625,1.5159912109375,0.13267135620117188,0.0018310546875,0.4750518798828125,-0.78692626953125,-0.859893798828125,0.2451019287109375,-0.203155517578125,-0.639617919921875,-0.5706787109375,-0.975341796875,2.3072509765625,0.2158203125,-0.3594932556152344,1.658447265625,-0.6072998046875,0.0201263427734375,1.76953125,-0.388092041015625,-0.047771453857421875,-1.15771484375,-0.362335205078125,-0.082794189453125,-0.5257110595703125,-0.2566070556640625,0.230804443359375,-0.51434326171875,1.450927734375,-0.13272857666015625,0.38324737548828125,-0.6046142578125,0.47967529296875,0.0544891357421875,-0.19964599609375,0.7012939453125,1.388916015625,-1.66015625,-0.407958984375,-1.40576171875,0.1427450180053711,-1.119873046875,0.919525146484375,0.8438720703125,2.2939453125,0.01105499267578125,-0.0741424560546875,0.39068603515625,2.30322265625,0.45452880859375,-0.5588779449462891,1.159912109375,0.37579345703125,-0.43837738037109375,0.300567626953125,1.1546630859375,-0.21026611328125,1.07537841796875,1.288818359375,-0.04261016845703125,-0.405517578125,0.039306640625,0.047607421875,0.24953460693359375,0.0952911376953125,-0.57061767578125,-0.583740234375,-0.73150634765625,0.85992431640625,-0.638427734375,1.0047607421875,-0.3076629638671875,0.88616943359375,-0.3418426513671875,0.357086181640625,-0.35013866424560547,-0.408721923828125,-0.09002685546875,1.9013671875,-0.043849945068359375,0.14818572998046875,0.440948486328125,-0.85498046875,-0.02426910400390625,0.22553253173828125,1.5166015625,-0.9599609375,-1.1292724609375,1.220458984375,-0.5972900390625,-0.664215087890625,0.23602294921875,1.3953857421875,0.85760498046875,-1.29296875,-0.50775146484375,-1.97509765625,-0.72607421875,-1.34619140625,-0.31353759765625,-0.15783309936523438,-1.147705078125,0.07466888427734375,-0.51458740234375,2.057861328125,-1.994384765625,1.1192626953125,0.42047119140625,-0.9381103515625,-0.417510986328125,0.282257080078125,-0.1992340087890625,0.64166259765625,0.65594482421875,-1.835693359375,-1.1243896484375,-0.118255615234375,0.526153564453125,1.30615234375,-1.1182861328125,-0.32598876953125,0.3839569091796875,-0.7340087890625,1.238525390625,0.78912353515625,-0.3046722412109375,1.561279296875,0.4564208984375,0.79547119140625,0.978515625,-0.19110107421875,-1.196533203125,-0.0543060302734375,-0.211273193359375,0.9215087890625,-1.163330078125,-0.22772216796875,0.54144287109375,-0.539581298828125,0.367156982421875,-0.2320098876953125,0.84912109375,0.48486328125,-1.0509033203125,-0.4037933349609375,-0.13262939453125,1.3302001953125,0.40692138671875,1.545654296875,-0.30770111083984375,-1.563232421875,0.3138427734375,0.066162109375,-1.21490478515625,-1.26806640625,0.32611083984375,0.06850433349609375,1.70068359375,-0.43174171447753906,-0.07520866394042969,-1.11328125,-1.3681640625,0.8704833984375,-0.48931884765625,-0.57098388671875,-0.7716064453125,0.7298583984375,-0.59808349609375,-0.33929443359375,-0.414581298828125,0.1025390625,1.2266845703125,0.42816162109375,-0.807861328125,0.361602783203125,-0.8507080078125,-2.0341796875,-0.703857421875,0.12890625,0.47442626953125,-1.19384765625,-0.588134765625,0.01586151123046875,0.256378173828125,0.36114501953125,0.2126922607421875,2.204833984375,0.22434234619140625,0.09332275390625,-0.6929931640625,0.1107177734375,0.598876953125,0.54254150390625,2.134521484375,0.1041412353515625,1.48681640625,-0.1275634765625,0.292236328125,0.7822265625,0.2671966552734375,0.09737205505371094,-0.46954345703125,0.1925201416015625,0.02885150909423828,0.045196533203125,0.33062744140625,-1.032958984375,0.9552001953125,0.102752685546875,0.927734375,0.0724029541015625,-0.7486572265625,1.1007080078125,-0.3365478515625,-0.419708251953125,-1.0091552734375,-1.1881103515625,0.3725128173828125,-0.55859375,-0.7355880737304688,0.3479156494140625,0.101043701171875,0.66864013671875,0.633544921875,1.222900390625,1.385986328125,0.6439208984375,-0.8426513671875,-0.30462646484375,0.97802734375,0.3501625061035156,-0.454193115234375,-1.751708984375,0.363800048828125,0.08476495742797852,-0.432220458984375,-0.9049072265625,0.341552734375,0.42474365234375,-0.383758544921875,0.1580333709716797,-0.30384063720703125,0.488037109375,-1.6123046875,-0.09548091888427734,1.3516845703125,0.05536651611328125,-0.27874755859375,0.1202392578125,-2.123779296875,-0.3704833984375,-0.88446044921875,1.1922607421875,0.38851165771484375,0.23211669921875,0.4566650390625,-0.078399658203125,-1.5205078125,0.53070068359375,0.0497589111328125,1.372802734375,0.9677734375,-1.189208984375,-0.6856689453125,-1.2099609375,0.261993408203125,-1.925537109375,0.79150390625,-0.405059814453125,0.17988014221191406,-0.8179931640625,-0.14848709106445312,-0.506866455078125,0.9002685546875,0.9677734375,0.05352783203125,0.07342720031738281,0.22979736328125,1.627685546875,1.1768798828125,0.544219970703125,0.9749755859375,-0.406402587890625,-0.03668212890625,1.7470703125,0.003173828125,0.46917724609375,-0.552886962890625,-0.2722930908203125,0.82598876953125,1.02117919921875,-0.50787353515625,-0.3562650680541992,0.5240449905395508,0.4923095703125,0.383941650390625,-0.025167465209960938,-0.5028076171875,-0.6953353881835938,0.5027313232421875,-0.8018798828125,0.2240619659423828,-0.63861083984375,1.348876953125,0.35028076171875,0.68743896484375,1.239501953125,0.794921875,-0.1614227294921875,-0.371307373046875,-0.1471710205078125,-1.0521240234375,-0.31060791015625,0.06662368774414062,0.1534900665283203,1.951416015625,1.0489501953125,-0.404144287109375,0.0746612548828125,0.50347900390625,-0.639251708984375,-0.03094482421875,-0.86328125,0.802001953125,0.32769203186035156,-0.71337890625,-1.05181884765625,0.988037109375,-0.546051025390625,-0.65692138671875,0.4254798889160156,-1.20751953125,-1.111083984375,-0.21834754943847656,-0.4756431579589844,-0.6209716796875,0.2401123046875,-0.285430908203125,-1.0523681640625,0.9193115234375,-0.221282958984375,-0.11413383483886719,-0.08739852905273438,-0.175201416015625,0.113983154296875,1.1822509765625,0.9268798828125,-0.55474853515625,-0.49102783203125,-0.6048583984375,0.051971435546875,0.09192276000976562,-0.8843994140625,0.2191162109375,0.170654296875,0.38893890380859375,0.11091995239257812,0.0906524658203125,0.92236328125,0.246551513671875,0.26116943359375,0.570587158203125,1.381103515625,0.936767578125,-0.8555908203125,0.032196044921875,-0.4095458984375,0.2176055908203125,-0.8021240234375,-0.62060546875,0.268707275390625,-0.21563720703125,-1.05340576171875,1.1646728515625,0.433837890625,0.1472930908203125,-1.6845703125,-0.3991875648498535,0.517425537109375,-1.2269287109375,-1.0855712890625,0.659423828125,0.21179580688476562,-0.2398681640625,0.934661865234375,-0.3683624267578125,-0.755615234375,0.355560302734375,-0.3685150146484375,-0.38604736328125,0.04891301691532135,-0.72802734375,-0.62030029296875,0.1968536376953125,-1.19775390625,0.34820556640625,1.59375,-0.7813720703125,0.647125244140625,-0.22021484375,0.388458251953125,-0.9110107421875,-0.4603118896484375,0.7662353515625,0.360321044921875,-0.2811431884765625,-0.084381103515625,0.74566650390625,0.126922607421875,1.301513671875,-0.0454864501953125,0.13364797830581665,0.17798423767089844,1.440673828125,1.289306640625,-0.52252197265625,-1.49658203125,-2.004638671875,0.10943603515625,0.543701171875,0.40240478515625,-0.04791259765625,-0.556060791015625,0.06923675537109375,-0.083465576171875,0.8189697265625,-0.2060699462890625,0.57965087890625,1.29345703125,-0.1748046875,-0.69873046875,0.208160400390625,0.99072265625,3.18505859375,1.74853515625,-0.8223876953125,-1.000244140625,0.8284912109375,-0.053436279296875,0.81634521484375,0.4374542236328125,-0.059441566467285156,1.89599609375,-0.2098541259765625,0.48358154296875,0.91162109375,1.1109619140625,0.687744140625,1.1767578125,0.31285858154296875,-0.511505126953125,0.126983642578125,-0.818603515625,-1.1549072265625,-1.33642578125,0.8125,0.8345947265625,1.671142578125,-1.0694580078125,0.422515869140625,-0.61669921875,-0.854736328125,-0.392303466796875,-0.21673583984375,-0.490386962890625,-0.2745819091796875,0.338348388671875,1.769775390625,0.7159423828125,0.1293487548828125,-0.32505035400390625,-0.96978759765625,0.48663330078125,1.55810546875,1.42333984375,1.26806640625,-0.10715484619140625,-1.707275390625,0.732666015625,0.4626274108886719,0.8072509765625,-0.18320846557617188,0.900634765625,0.205902099609375,-1.2447509765625,0.5501375198364258,-0.067626953125,-0.30220794677734375,-1.546630859375,-0.3255805969238281,-0.28021240234375,-0.236236572265625,0.10071563720703125,-0.062450408935546875,-1.40185546875,-0.48760986328125,-0.7615966796875,0.1539459228515625,-0.463836669921875,-0.39532470703125,0.3518218994140625,1.224609375,0.9971923828125,-0.95458984375,0.25048828125,0.412689208984375,-0.8297214508056641,0.9842529296875,0.6094970703125,0.315765380859375,-0.3290557861328125,0.22796630859375,-0.34637451171875,0.7667236328125,-1.164306640625,-1.226318359375,0.36822509765625,-1.044677734375,0.197113037109375,0.621978759765625,0.59222412109375,0.2056427001953125,0.86346435546875,-0.60626220703125,-0.4264373779296875,0.67510986328125,0.09618759155273438,0.20380306243896484,-0.39398193359375,0.339813232421875,0.20688247680664062,0.17503929138183594,-0.3899383544921875,0.5027618408203125,-2.31494140625,0.0726776123046875,0.025909423828125,-0.476226806640625,0.15985107421875,-2.36962890625,0.056758880615234375,0.23986053466796875,-0.0033742189407348633,-0.983154296875,-0.5360374450683594,-0.4186553955078125,0.16510009765625,-0.3431129455566406,0.37799072265625,-0.05168914794921875,0.1660003662109375,0.1323089599609375,0.98681640625,0.21869373321533203,0.14003372192382812,-0.153839111328125,-0.7457275390625,-0.603759765625,-1.2054443359375,-0.0327606201171875,0.57861328125,0.71240234375,-0.8106689453125,-0.43511199951171875,-0.5113525390625,0.47777557373046875,-1.657470703125,-0.55712890625,0.9425048828125,-0.756103515625,0.9146728515625,0.98291015625,-0.29189300537109375,-0.7532958984375,-0.99072265625,-0.638763427734375,1.184814453125,0.184173583984375,0.39361572265625,1.0731201171875,0.047576904296875,-0.9503173828125,0.0052642822265625,0.224365234375,-0.20470428466796875,-1.67767333984375,-1.4921875,-1.287109375,-0.3265228271484375,-0.6295166015625,1.491455078125,-0.75732421875,-0.559326171875,1.3270263671875,0.350982666015625,0.53851318359375,-0.054534912109375,0.172088623046875,-0.40252685546875,1.511474609375,0.226959228515625,0.3145751953125,0.9840087890625,-0.9000244140625,0.71026611328125,0.0608062744140625,0.3066864013671875,-0.8043212890625,-0.41606903076171875,-0.3103790283203125,1.13836669921875,0.1932373046875,0.55682373046875,0.7596435546875,-0.6771240234375,-0.8277587890625,-0.77105712890625,0.957275390625,0.1772594451904297,-1.32958984375,-1.6732177734375,-0.9344482421875,0.1116943359375,-0.0357666015625,0.9981689453125,0.000148773193359375,-1.005615234375,0.66485595703125,0.49478912353515625,-0.3583221435546875,-0.16078567504882812,0.420166015625,0.277557373046875,-0.373138427734375,1.063720703125,0.20745849609375,1.492919921875,-0.130462646484375,1.55908203125,-0.173583984375,0.849365234375,0.0257568359375,-0.13447237014770508,-1.0125732421875,0.685302734375,-0.65789794921875,-0.1214752197265625,-2.06298828125,0.13034439086914062,-1.44873046875,-0.92822265625,0.026153564453125,0.3846435546875,-0.3443145751953125,-0.7200927734375,1.0894775390625,-1.86572265625,-0.173095703125,0.3957347869873047,0.778076171875,-0.5191192626953125,0.237274169921875,-0.492462158203125,0.44078826904296875,-0.162872314453125,-0.2239990234375,0.394622802734375,-0.7061767578125,-0.04705810546875,0.297607421875,-0.5181884765625,0.57061767578125,0.11334228515625,-0.00984954833984375,0.06342697143554688,0.1662750244140625,-0.292388916015625,-1.330078125,0.43804931640625,-0.547882080078125,-0.3859710693359375,-0.46136474609375,-0.742431640625,0.304351806640625,0.222320556640625,-0.219635009765625,-0.57855224609375,0.197998046875,-0.807861328125,0.1013031005859375,-0.43292236328125,0.8463134765625,-1.099365234375,-0.3472747802734375,0.1977081298828125,-0.5777587890625,-0.1681976318359375,-0.2085113525390625,-0.59197998046875,-0.3203125,0.70428466796875,0.474609375,1.1611328125,-0.890380859375,-0.55572509765625,0.3564605712890625,-0.12945556640625,1.803466796875,2.36376953125,0.398681640625,-1.327392578125,0.1839599609375,-0.612030029296875,-0.6049652099609375,-0.17806053161621094,-1.82421875,0.56988525390625,-1.214111328125,0.77215576171875,-1.1741943359375,0.057903289794921875,2.065185546875,0.21588134765625,0.31290435791015625,-1.765625,0.16321945190429688,-0.61279296875,0.15477752685546875,-0.53448486328125,-1.2510986328125,0.0748138427734375,0.1174468994140625,0.4141845703125,-0.22984695434570312,0.7135009765625,1.0921630859375,-0.14450454711914062,-1.000732421875,-0.235260009765625,0.74200439453125,-1.0675048828125,-0.763214111328125,-0.713134765625,0.8084716796875,0.72296142578125,0.315704345703125,1.3758544921875,-0.157318115234375,1.0859375,-0.30115509033203125,0.72015380859375,0.2470703125,-0.65179443359375,-0.1112213134765625,-1.846923828125,0.64300537109375]}

Hello,
Can you provide us  your logs ?
Anyway, you can check those threads it helped me a lot when I had problems with Ollama #619, #650.

Logs
indexing-engine.log
logs.json

Verify the name of your models, seems like llama3.1 isn't pulled on your Ollama instance.
user@VRH035941:~/.venv/graphrag$ ollama list
NAME                            ID              SIZE    MODIFIED
mxbai-embed-large:latest        468836162de7    669 MB  6 days ago
nomic-embed-text:latest         0a109f422b47    274 MB  10 days ago
mistral:latest                  f974a74358d6    4.1 GB  10 days ago
llama3.1:latest                 42182419e950    4.7 GB  10 days ago

@balezeauquentin sorry for the outdated info (I switched to a different model):
$ ollama list
NAME                         ID              SIZE      MODIFIED
llama3.1:latest              42182419e950    4.7 GB    3 minutes ago
llama3.1-32k-q8:latest       ec0697ee6936    8.5 GB    6 hours ago
mistral:latest               f974a74358d6    4.1 GB    9 hours ago
llama2:latest                78e26419b446    3.8 GB    10 hours ago
nomic-embed-text:latest      0a109f422b47    274 MB    4 days ago
llama3.1:8b-instruct-q8_0    b158ded76fa0    8.5 GB    4 days ago

$ python -m graphrag.index --root t2
Logging enabled at /home/ohho/codes/python/try/graphrag/t2/output/indexing-engine.log
/home/ohho/conda/envs/graphrag/lib/python3.10/site-packages/numpy/core/fromnumeric.py:59: FutureWarning:
'DataFrame.swapaxes' is deprecated and will be removed in a future version. Please use 'DataFrame.transpose' instead.
  return bound(*args, **kwds)
🚀 create_base_text_units
                                 id  ... n_tokens
0  6d2823d11f18b1dbb3e9c4d3a1a7b3bf  ...      401

[1 rows x 5 columns]
🚀 create_base_extracted_entities
                                        entity_graph
0  <graphml xmlns="http://graphml.graphdrawing.or...
🚀 create_summarized_entities
                                        entity_graph
0  <graphml xmlns="http://graphml.graphdrawing.or...
❌ create_base_entity_graph
None
⠇ GraphRAG Indexer
├── Loading Input (text) - 1 files loaded (0 filtered) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00 0:00:00
├── create_base_text_units
├── create_base_extracted_entities
├── create_summarized_entities
└── create_base_entity_graph
❌ Errors occurred during the pipeline run, see logs for more details.

这个问题特别恶心,困扰我好几天了

This should resolve the embedding issue you encountered. I faced a similar problem due to the different embedding format used by OpenAI.
After installing the required dependencies, you can run the file as follows:
# repo: https://github.com/9prodhi/EmbedAdapter/blob/main/ollama_serv.py
python ollama_serv.py

Also do not forget to change embedding llm api_base  setting.

File "/home/zhangyj/anaconda3/envs/graphrag/lib/python3.12/site-packages/graphrag/llm/openai/openai_chat_llm.py", line 56, in _execute_llm
return completion.choices[0].message.content
~~~~~~~~~~~~~~~~~~^^^
TypeError: 'NoneType' object is not subscriptable
seems no response generated from LLM (Ollama model), but don't know how to debug

My index process has completed,but query shows
`See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy
entity_df["community"] = entity_df["community"].astype(int)
creating llm client with {'api_key': 'REDACTED,len=19', 'type': "openai_chat", 'model': 'llama3.1', 'max_tokens': 4000, 'temperature': 0.0, 'top_p': 1.0, 'request_timeout': 180.0, 'api_base': 'http://localhost:11434/v1', 'api_version': None, 'organization': None, 'proxy': None, 'cognitive_services_endpoint': None, 'deployment_name': None, 'model_supports_json': None, 'tokens_per_minute': 0, 'requests_per_minute': 0, 'max_retries': 10, 'max_retry_wait': 10.0, 'sleep_on_rate_limit_recommendation': True, 'concurrent_requests': 25}
Error parsing search response json
Traceback (most recent call last):
File "/mnt/codes/graphrag/graphrag-local-ollama/graphrag/query/structured_search/global_search/search.py", line 194, in _map_response_single_batch
processed_response = self.parse_search_response(search_response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/codes/graphrag/graphrag-local-ollama/graphrag/query/structured_search/global_search/search.py", line 232, in parse_search_response
parsed_elements = json.loads(search_response)["points"]
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/anaconda3_install/envs/graphrag-ollama-local/lib/python3.11/json/init.py", line 346, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/anaconda3_install/envs/graphrag-ollama-local/lib/python3.11/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/anaconda3_install/envs/graphrag-ollama-local/lib/python3.11/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
SUCCESS: Global Search Response: I am sorry but I am unable to answer this question given the provided data.
`

最近问题都是这个问题,就是官方的bug吧

Routing to #657


Should we get rid of the random_state argument in get_pipeline?

Currently, the best_pipeline property in AutoMLSearch will always return a pipeline with random_state=0 because that's the default value for random_state in the get_pipeline method.
I think this is confusing because if I create an AutoMLSearch object with random_state=5, for example, I expect all of the pipelines created and returned by AutoMLSearch to have random_state=5.
I think we should remove the random_state argument from get_pipeline and instead make sure that the random state is set to whatever it was when the pipeline was fit.

Agreed.  I think that's the right move @freddyaboulton.  This one doesn't seem like a huge lift.  I'll dev backlog it.  @dsherry @tyler3991

Agreed.  I think that's the right move @freddyaboulton.  This one doesn't seem like a huge lift.  I'll dev backlog it.  @dsherry @tyler3991

@freddyaboulton @chukarsten @dsherry after looking at this one for a little, I think this issue might be a not be as straightforward as expected. In our pipeline_base.py class, we set the random_state to be an np.RandomState object, which we generate through our utils, get_random_state, which uses sklearn.utils.check_random_state. While this state is the same for the same seed, we can't get the original seed we passed in. This means that even if we passed in random_state=4 for AutoMLSearch, the pipelines and internal random_state values are np.RandomState objects seeded with '4'.
I can think of three possible solutions for this issue:

We can continue to remove random_state argument, but the random_state associated with the pipeline continues to be a np.RandomState object. This might be confusing for the user, but currently, the random_state value for AutoMLSearch is also an np.RandomState object

We can introduce a random_seed value like we did with AutoMLSearch, but I'm not sure this would help much
We can try to override np.RandomState with the int provided instead, and keep the random_state value as an int instead of an np.RandomState object. This makes the values consistent with what the user expects, but might be a lot of work, since we'll likely have to refactor both pipelines and components.

I think the big issue is determining why we decided to use np.RandomState objects to hold the random state of our objects. Was there a reason we chose to pass this around versus an int?
What do you all think? I think option 1 would be the best, even if it introduces some potential inconsistency with what the user expects.

@freddyaboulton I think the largest issue is that in our pipeline_base, we set the random_state to be an np.RandomState object, as seen here

If we remove the np.RandomState object, then we can preserve the random state that the user could pass in, but we would also need to change the default random_state behavior for component_base as well. This issue does seem to be tied with a discussion about support for np.RandomState. What do you think?

@freddyaboulton I think the largest issue is that in our pipeline_base, we set the random_state to be an np.RandomState object, as seen here

If we remove the np.RandomState object, then we can preserve the random state that the user could pass in, but we would also need to change the default random_state behavior for component_base as well. This issue does seem to be tied with a discussion about support for np.RandomState. What do you think?

Through discussion with @freddyaboulton, we decided it's fine to have the pipeline random_state be a np.RandomState object, but we want to make sure it's seeded with the random_state int that a user passes in, OR with the np.RandomState object that a user passes in, depending on the input.
This means that if a user passes in random_state=4 to AutoMLSearch, we create the pipeline random_state with '4' as the seed, and if a user passes in random_state=np.RandomState(), we pass that to create the pipeline instead.

Through discussion with @freddyaboulton, we decided it's fine to have the pipeline random_state be a np.RandomState object, but we want to make sure it's seeded with the random_state int that a user passes in, OR with the np.RandomState object that a user passes in, depending on the input.
This means that if a user passes in random_state=4 to AutoMLSearch, we create the pipeline random_state with '4' as the seed, and if a user passes in random_state=np.RandomState(), we pass that to create the pipeline instead.


Removed dependency on nette/nette.

Oh cool :+1:
I'm just thinking if it woudn't be better to require ^2.2 instead of ^2.3. There can be people using this version

You're right, I'll change it.

Thanks, and can you now also squash all commits together please?

Yes, I can.

cool, thank you :beers:


Support for RE270K?

I'm wondering if this Wi-FI Range Extender + SmartPlug is supported? Using setPowerState doesn't work. Also ._type property is device and alot of stuff differs from standard plug or bulb.

Can you run the hs100-api details <ip>(the device's IP) and paste the output? If I keep some example data I can add support.

Will do it tomorrow. Also, what's the minimal version of node required for this library to work?

6.5, as specified in the package.json

Is there something in the lib that requires 6.5 or? Since NAS devices don't support node v6. Also, my colleague took the Wi-Fi Range Extender home so I'll tell him to send the details tonight and I'll put them here.

Now that I'm using babel on this project I may be able to support v4 with minimal changes. I'll see what I can do.

{ sysInfo:     { plug:        { feature: 'TIM',         relay_status: 'ON',         on_time: 285025,         next_action: { type: -1 } },      err_code: 0,      'rangeextender.wireless':        { w5g_client_count: 0,         w2g_uplink_time: 128975,         w5g_uplink_enabled: true,         w5g_rssi: -256,         w5g_uplink_time: 0,         w2g_mac: '50:C7:BF:C8:5E:DE',         w2g_uplink_enabled: true,         w2g_downlink_enabled: true,         w5g_downlink_enabled: true,         w2g_client_count: 0,         w5g_uplink_connected: false,         w2g_rssi: -73,         w5g_mac: '50:C7:BF:C8:5E:DD',         w2g_uplink_connected: true },      system:        { ethernet_mac: '50:C7:BF:C8:5E:DE',         type: 'IOT.RANGEEXTENDER.SMARTPLUG',         oemId: 'A4551BD7CF274B28C532A79E87B9FFB5',         icon_hash: '',         system_time:<PHONE_NUMBER>,         updating: false,         deviceId: '801773997DCEC2F8134A9673D74C296318C860BA',         sw_ver: '1.1.8 Build 20170317 rel.37472',         hwId: '5AC4CF9E3183C16825EB28BC3C27059C',         longitude: 17.79082,         led_status: 'ON',         model: 'RE270K(EU)',         hw_ver: '1.0.0',         latitude: 43.351783,         alias: 'Hi-fi',         dev_name: 'AC750 Wi-Fi Range Extender with Smart Plug' } },   cloudInfo: { err_msg: 'method not support', err_code: -1 },   consumption: { err_msg: 'method not support', err_code: -1 },   scheduleNextAction: { err_msg: 'method not support', err_code: -1 } }
There's the data for RE270K

I was able to configure babel and get this working on node 4.8 (will release a version of hs100-api soon). It looks like TPLINK keeps slightly tweaking the API for each device, I would need to know the commands that are sent to control it.
This is how to control HS* devices:
{"system":{"set_relay_state":{"state":1)}}}}
I noticed that RE270K they have moved sys_info.system.relay_state to sys_info.plug.relay_status. Without having a dump of the network traffic its hard for me to know which commands to send to control it.
You could try running different versions of the command to see if any work:
hs100-api send <ip> '{"system":{"set_relay_status":{"state":1)}}}}'
hs100-api send <ip> '{"system":{"plug":{"set_relay_state":{"state":1)}}}}}'
hs100-api send <ip> '{"system":{"plug":{"set_relay_status":{"state":1)}}}}}'
hs100-api send <ip> '{"system":{"plug":{"set_relay_status":{"status":1)}}}}}'
hs100-api send <ip> '{"system":{"plug":{"set_relay_status":{"status":"ON")}}}}}'
If you find anything let me know!
If you or anyone else with access to that model could dump the traffic I can add updates to support it. Here's an example: https://github.com/softScheck/tplink-smartplug

I used your sysinfo and my simulator to try to mimic your device and spy on the Kasa app traffic. One thing this device does different is Kasa tries to login to the router. That is where I hit a roadblock.

Kasa sends out a discovery message UDP broadcast port 9999
RE270k responds with sysinfo (same as other devices)
In Kasa I see the device, when I try to add it asks for the "admin password" (other devices don't require this)
I type in a password and submit.
Kasa connects to RE270k HTTPS port 10433 and POSTs to /data/LINKIE.json with {"smartlife.common.system":{"get_sysinfo":{}}} (but "tplink" encrypted), this is not something done with the other plugs/bulbs.
Kasa shows "Your admin password is incorrect"

So this is where I'm stuck. I'm not sure what Kasa is expecting when it sends that POST. If I knew whatever authorization its doing I could maybe replicate.
If anyone has any more info please let know!

My colleague (who owns this model) is out of country until Wednesday, so nothing until then.

I tried also to reach it, but in another way.
Assume <IP_ADDRESS> is the ip address of your RE270K

I first configured the plug via the Kasa app with particular password. Afterwards I logged in via /data/json.htmland observed the developer console's network log of chrome, where I found the provided formdata and my password but somehow encrypted.

POST http://<IP_ADDRESS>/data/login.json
with following Header:
Content-Type:application/x-www-form-urlencoded
and following Form-Data:

operation:login
encoded: admin:<pw-somehow-encrypted>
nonce:

In the response you get a Cookie, which may help you contact the endpoint anew, but this time to get the specs or turn the plug on/off.

Unfortunately, I have not more information than that. Maybe someone else has an idea how to contact the smartplug endpoint (different from the webinterface for configuring the wifi extender).

The only way I could get it to work in SmartThings was to use IFTTT to turn on / off and the standard commands to get the status.  Better than just using IFTTT (since you get a return status).  I am still looking for a full solution (I want it for the Hubitat Enviroment UDP control.)


Backward-facing Step not Controllable

cc @cl126162
to be closed by deprecating the backward-facing step

@ludgerpaehler Hello:) Could u elaborate on this?

Fixed by updated backward-facing step.


Support Tabs component

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Currently, Toolpad supports Tabs. Tabs are basically sub-pages. This issue is about Tabbed containers.

https://mui.com/material-ui/react-tabs/
One of: https://github.com/mui/mui-toolpad/issues/78

@prakhargupta1 can you confirm if I understand correctly that we want something ala Tabbed container that retool offers?

There is also Tabs component which allows controlling other components via special configuration

Should we implement one, the other or both?

We should do Tabbed containers.
Example from appsmith here

@Janpot
Today I doved into this issue.
Tabs can only receive only one children property.
my suggestion is change children into a type of array.

@Janpot
Today I doved into this issue. Tabs can only receive only one children property. my suggestion is change children into a type of array.

An array of layoutSlot props might work? But not sure if there would be any obstacles that could be complicated to deal with.


General: Move creators plugin getter

Brief description
Moved get_creator_by_name function into openpype.pipeline.create.creator_plugins.
Testing notes:
Creation during loading in Blender and Maya should work as before.

Could you show me how I could get the non legacy creators by name? (Or basically what the new equivalent is of this functionality)

Could you show me how I could get the non legacy creators by name? (Or basically what the new equivalent is of this functionality)

Creator plugins are wrapped into CreateContext. Creators can be accessed by their identifier from there. So there is not direct equivalent of this functionality.
Programmatically creation is not "ideal" now but ready to be added. The development focus was and still is elsewhere.
from openpype.pipeline import registered_host
from openpype.pipeline.create import CreateContext

context = CreateContext(registered_host())
render_creator = context.creators["render"]
...
# Do some stuff
...
context.save_changes()

Creator plugins are wrapped into CreateContext. Creators can be accessed by their identifier from there. So there is not direct equivalent of this functionality.
Programmatically creation is not "ideal" now but ready to be added. The development focus was and still is elsewhere.

Thanks - that helps. That still looks painful, yes. Moving to legacy seem fine - we'll just need to make sure not to mark it deprecated until the new system is at the same ease of use.


fix: error checking inheritance when using PEP585 and PEP604 type hints

Change Summary
Created convert_generics function, which searches for str types inside of type hints and replaces them with ForwardRef.
Used this function in ModelField.

Related issue number
fix #2798
fix #3297

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

hi, when this fix is planned to be released please?

hi, when this fix is planned to be released please?

No idea actually. It first must be reviewed by maintainers. Until then, you can install this bugfix using the command below.
pip install git+https://github.com/aleksul/pydantic.git@c421630a9da2d98602e7fca4b555c5f390311774

It should be ok, I've tested it on CI in my repo.

please update.

This PR will also fix this issue - #2803

please review

Any updates to this PR?

I've removed the 1.9.1 milestone as, on reflection, I don't think this is a regression in v1.9.

I've removed the 1.9.1 milestone as, on reflection, I don't think this is a regression in v1.9.

I believe this is a regression indirectly because since Python 3.9 introduced PEP585, all of the type hints (such as List, Dict, Tuple, etc.) in the typing module were marked as deprecated, and it leads to a weird situation: on the one side - you don't want to write new code with deprecated stuff, on the other - you can't because of this annoying bug. Also, PEP604 was introduced in Python 3.10, and (as far as I understood from the release note) pydantic 1.9.0 should bring support for it, so if not a regression, this is at least an overlooked use case, I believe.
It's especially bad when using an ORM (because they heavily rely on relation checks inside of pydantic which is what this bug is all about). So, with or without the milestone, I hope this PR (or possibly another one fixing the same issue with a different approach) will be merged ASAP.

Makes sense, I've re-added the milestone and will try to include this.

please update. Also, please could you resolve conflicts - should be trivial.

please review

thanks so much.


do_connect problem

This is not a problem when I connect to the wifi that have the sql server, but when I switch to my mobile hotspot this function will still return success as it will return 0 (Success code) even if cr is 0 which crash the code. So i added if(cr == 0) return 1; to prevent the problem
template <typename T>
        TDSL_SYMBOL_VISIBLE int do_connect(T target, tdsl::uint16_t port) {
            // Disconnect if already connected
            do_disconnect();

            int cr      = 0;
            int retries = 5;

            // There may be residue data in network buffer
            // Reset it to ensure a clean start
            this->network_buffer.get_writer()->reset();

            tdsl::char_view destination_host{};

            // Given that @p target can be a progmem string,
            // we need to ensure that it is in SRAM before passing
            // it to `connect` function. For that, instead of allocating
            // a new buffer, we use the network buffer since it's sufficiently
            // large free space not yet in use for anything.

            if (target.size_bytes() <= this->network_buffer.get_writer()->remaining_bytes()) {

                auto w = this->network_buffer.get_writer();
                for (auto c : target) {
                    auto wr = w->write(c);
                    (void) wr;
                }
                destination_host = w->inuse_span().template rebind_cast<const char>();
            }
            else {
                return -99; // FIXME: proper error code
            }

            // Retry up to MAX_CONNECT_ATTEMPTS times.
            while (retries--) {
                TDSL_DEBUG_PRINTLN("... attempting to connect to %s:%d, %d retries remaining ...",
                                   destination_host.data(), port, retries);
                cr = client.connect(destination_host.data(), port);
                if (cr == 1) {
                    TDSL_DEBUG_PRINTLN("... connected, %d --> %d.%d.%d.%d:%d ...",
                                       client.localPort(), client.remoteIP() [0],
                                       client.remoteIP() [1], client.remoteIP() [2],
                                       client.remoteIP() [3], client.remotePort());
                    break;
                }

                TDSL_DEBUG_PRINTLN("... connection attempt failed (%d) ...", cr);
                delay(1000);
            }

            // Reset the network buffer so it's ready to
            // use by its real purpose
            this->network_buffer.get_writer()->reset();

            if (cr == 1) {
                return 0;
            }
            if(cr == 0) return 1; // Added this then good
            return cr;
        }

Hello @kangyite,
Thanks for reporting this, the do_connect function needs to handle the connect's return values better. I'll try address this in the next update.

Fixed with 0.4.0 release.


Output for X-shift standalone

Hello,
I have recently been looking into using the x-shift standalone to bypass the need for a GUI. I have run a sample dataset and the output was an FCS file and a .gmp. When using Vortex the output is different. We have been taking the raw clustering data (calculate group statstic for specific K value) and plugging that into an excel file. Is there a way to extract that same data from the FCS/gmp files that are generated through x-shift standalone?
Thanks,
Don

My apologies it's FCS and .gml that's generated.

Is there a way of importing the clusters from x-shift standalone into the GUI? If so, users can save time by running the computation extensive tasks on a server.


TC Login 02

Description: Valid email in the "Email box" field is introduced
Preconditions: Conection/Log In is opened

Steps.1 Chrome page is opened

Steps.2 The user clicks on the search bar the admin URL

Step.3:The user writes a valid email address in the email field  and presses on "Conecatre" button
Expected Result: The user receives on the email address an administrator link to connect on the validator main page


Remove last link header when include total option is false

When you set the include_total option to false, the total number of records is still needed for the last link header. This pr 'fixes' that by not including the last link header when you disable the include_total option. When using Kaminari, this prevents the count call which can speed up the pagination process by a lot when using big datasets.
In addition I found that when you write the test
expect(links).not_to include('rel="prev"')

that it check if that string has an exact match to the links array. This will thus always be false! Therefore I added the link helper which is just the raw header and use that in the specs so it makes a string comparison.
This pr Closes #85

Thank you!


Provide QAOA solver via qiskit

Will be adding comments in the future...
I've recreated the ConstraintConversionError from ocean.py, as it starts out the same way and has the same potential for issues. It works fine with them, but they're identical so perhaps could be moved somewhere else.

Found significant errors


Windows Builds Not Working For Most Subsystems

I tried four builds from gobuild on Win8.1 x64. All of them failed with virtually the same error messages (quoted in full). The error messages only differ in their Hex-IDs, so i only included the x64 build of 0.5.
I can get sysinfo_influxdb --help, so the binary works partly.
0.5 x64
λ sysinfo_influxdb.exe
panic: Not Implemented

goroutine 20 [running]:
runtime.panic(0x640560, 0xc082000ab0)
        c:/go/src/pkg/runtime/panic.c:279 +0x11f
github.com/cloudfoundry/gosigar.notImplemented(0x0, 0x0)
        /gopath/src/github.com/cloudfoundry/gosigar/sigar_windows.go:98 +0x7a
github.com/cloudfoundry/gosigar.(*Cpu).Get(0x3c3e88, 0x0, 0x0)
        /gopath/src/github.com/cloudfoundry/gosigar/sigar_windows.go:44 +0x37
main.cpu(0xc082000972, 0x7, 0xc08203e0a0, 0x0, 0x0)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:341 +0x1b0
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 16 [chan receive]:
main.main()
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:191 +0xa86

goroutine 17 [syscall]:
runtime.goexit()
        c:/go/src/pkg/runtime/proc.c:1445

goroutine 19 [finalizer wait]:
runtime.park(0x41e8e0, 0x8a38c0, 0x8a19a9)
        c:/go/src/pkg/runtime/proc.c:1369 +0xac
runtime.parkunlock(0x8a38c0, 0x8a19a9)
        c:/go/src/pkg/runtime/proc.c:1385 +0x42
runfinq()
        c:/go/src/pkg/runtime/mgc0.c:2644 +0xdd
runtime.goexit()
        c:/go/src/pkg/runtime/proc.c:1445

goroutine 21 [runnable]:
main.cpus(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:351
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 22 [runnable]:
main.mem(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:368
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 23 [runnable]:
main.swap(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:386
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 24 [runnable]:
main.uptime(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:404
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 25 [runnable]:
main.load(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:422
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 26 [runnable]:
main.network(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:440
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09

goroutine 27 [runnable]:
main.disks(0xc082000972, 0x7, 0xc08203e0a0, 0x1, 0xc082000972)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:497
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09
panic during panic

goroutine 21 [running]:
runtime.panic(0x640560, 0xc082000ad0)
        c:/go/src/pkg/runtime/panic.c:276 +0xf6
github.com/cloudfoundry/gosigar.notImplemented(0x0, 0x0)
        /gopath/src/github.com/cloudfoundry/gosigar/sigar_windows.go:98 +0x7a
github.com/cloudfoundry/gosigar.(*CpuList).Get(0x3f3ec8, 0x0, 0x0)
        /gopath/src/github.com/cloudfoundry/gosigar/sigar_windows.go:48 +0x37
main.cpus(0xc082000972, 0x7, 0xc08203e0a0, 0x0, 0x0)
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:359 +0x1b7
created by main.main
        /gopath/src/github.com/novaquark/sysinfo_influxdb/main.go:187 +0xa09
stack trace unavailable

After that, i tried querying only some subsystems:
λ sysinfo_influxdb.exe -c="cpu"
panic: Not Implemented
[...]

λ sysinfo_influxdb.exe -c="cpus"
panic: Not Implemented
[...]

λ sysinfo_influxdb.exe -c="mem"
#0: PC.mem
| free  | used  | actualfree    | actualused    | total |
| 0     | 0     | 0     | 0     |<PHONE_NUMBER>    |
(total is correct, at least something :) )

λ sysinfo_influxdb.exe -c="swap"
panic: Not Implemented
[...]

λ sysinfo_influxdb.exe -c="uptime"
#0: PC.uptime
| length        |
| 0     |
(errr.... no.)

λ sysinfo_influxdb.exe -c="load"
#0: PC.load
| one   | five  | fifteen       |
| 0     | 0     | 0     |
(well, that was kind-of expected)

λ sysinfo_influxdb.exe -c="network"
(did not return, had to Ctrl+C kill it)

λ sysinfo_influxdb.exe -c="disks"
(did not return, had to Ctrl+C kill it)

There was no difference, whether i ran sysinfo_influxdb with or without administrator privileges. The verbose flag did not return anything for the last two commands.

Hi,
I read from https://github.com/cloudfoundry/gosigar#supported-platforms that Windows is not supported yet :(
I'll indicate that in the README file.


Show min and max values.

Does the library support showing max and min values from a given data set onto the sparkView? Something similar to what the Coinbase android app does?
I am attaching an image below:

In the image we can see two bubbles which denote the high and lows for the selected day.
Any recommendation on how to achieve it?
Thanks!

I think you could use the getScaledX() and getScaledY() APIs on SparkView to determine where to draw your min/max labels. By default SparkAdapter.getDataBounds() gives you back the min and max data points in your adapter.

I did find those methods..However even after getting the floating value point how i can actually add an UI element to the exisiting sparkView graph? For example: is there a method such a sparkView.setTextView(string value, float x) or something along those lines? I am lost at how to update the sparkView class with a new label.

Awesome! Now you'll want to instantiate a TextView programmatically and position it using the scaled x and y values returned from your SparkView. SparkView is just a Sparkline so it doesn't provide the ability to add labels.

I tried the approach that you suggested. However from the documentation it seems like the SparkView doesn't really use the x-axis co-ordinates. It divides the x-axis equally and simply draws a Path along the y-axis. That being said, wouldn't the getScaledX() return me a pixel which is not actually used by the SparkView. If i try the aforementioned approach, the text is not visible at all, however if i only use the getScaledY() and then use text.setY(float y) i see can see the text on the top left corner since that is the highest value.
Apologies if this is getting out of hand.

Hi @pkhivesara,
@naturalwarren is right, we don't support this out of the box, but you should be able to roll-your-own here.
The x-axis behavior you mentioned can be changed. If you want spark to use the x values from your data, you can override getX() in your SparkAdapter.
So after doing that, you can getScaledX/Y to find the spark-local coordinates of the min and max points in your data. You should be able to use those to position a TextView however you'd like. Or you could even subclass SparkView itself and draw text directly to the canvas in onDraw().
This is a fair amount of work, though, and I believe MpAndroidChart likely supports this out of the box: https://github.com/PhilJay/MPAndroidChart

I am not sure but whenever i try to use the approach mentioned above, the text is always displayed either on top left or top right. It seems like the layout is being added against the screen width and height. Not the SparkView itself. Either ways i understand since this requirement is not part of SparkView, i will be closing the ticket. Thanks for all the help.!


lisa.target: Run adb_root() if possible on Android targets by default

Using username=None default allows making the difference between a user
explicitly asking to be connected as root or non-root, and a user not specifying
anything. When no username is asked in particular on android targets, try to
root adb but only warn if that fails.

The code looks good to me, I'll test it tomorrow


Update master_integration_fields.sql to add migration script for adding masterIntegrationFields for dclKey integration

https://github.com/Shippable/pm/issues/9371

verified on rc


Add new rule no-method-signature

As described in #30.

Coverage decreased (-0.4%) to 87.427% when pulling 690ed64502e5bae755b4859e85e469362f94e62d on feature/30-no-method-signature into 3fa6d625f0165b59e4c3bab0dffab23608aa6831 on master.

Coverage decreased (-0.4%) to 87.427% when pulling dad99948e7b7a6ccc02c6b8b747d3e4b014448f0 on feature/30-no-method-signature into 3fa6d625f0165b59e4c3bab0dffab23608aa6831 on master.

Coverage decreased (-0.4%) to 87.427% when pulling c0094809a032177e9d33724767431cc3d7261fbe on feature/30-no-method-signature into 3fa6d625f0165b59e4c3bab0dffab23608aa6831 on master.

Coverage increased (+10.0%) to 97.842% when pulling fef39bd505939ad84ee444131d2c3e7e0b084039 on feature/30-no-method-signature into 3fa6d625f0165b59e4c3bab0dffab23608aa6831 on master.

Coverage increased (+10.0%) to 97.842% when pulling fe64a33546fc0f834f829a10366a774838e4843f on feature/30-no-method-signature into 3fa6d625f0165b59e4c3bab0dffab23608aa6831 on master.

Closes #30


Did the baselines use the same (CLIP + SlowFast) feature extractors as Moment-DETR?

Hi @jayleicn, many thanks for sharing this great work! I was wondering whether your baseline models (e.g., MCN, XML, XML+) in Table 3 used the same feature extractors as Moment-DETR? Thanks!

Yes, we used the same features to these models to ensure fair comparisons.

On Nov 5, 2023, at 11:46 PM, Ye Liu @.***> wrote:
Hi @jayleicn https://github.com/jayleicn, many thanks for sharing this great work! I was wondering whether your baseline models (e.g., MCN, XML, XML+) in Table 3 used the same feature extractors as Moment-DETR? Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/jayleicn/moment_detr/issues/46, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYJWVL3IW2SLDCTBX3SBFLYDCIVHAVCNFSM6AAAAAA67B3XMOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3TQNJQGIYTCMA.
You are receiving this because you were mentioned.

I see. Thanks for your reply!


Theta forecaster and prediction intervals

Reference Issues/PRs

#67 #97
What does this implement/fix? Explain your changes.

Includes:

ThetaForecaster which implements the Theta method.
Unit tests for ThetaForecaster.
A new dataset in datasets.load_airline - the Box/Jenkins airline passengers dataset. I thought this provided a clearer example of simple, univariate, seasonal data than some of the other datasets currently in sktime.
New interface in BaseForecaster to enable prediction intervals to be calculated: prediction_errors. Currently this has only been implemented for ThetaForecaster. Running this method for any other forecaster will raise a NotImplementedError.
Alternatively, prediction intervals may also be obtained by calling predict() and providing one or many confidence levels. This will cause the method to return a tuple of predictions and errors, instead of just predictions.
A plot() convenience method for forecasters. As well as plotting the forecasts (optionally alongside any training/test data), it will also plot prediction intervals if available for that forecaster.
A new notebook, simple_forecasting.ipynb, to demonstrate all of the above.

Any other comments?

Other projects I looked at like as pmdarima and R's forecast library return upper and lower bounds for prediction intervals. I've opted for a different approach though, of just doing the bare minimum and calculating the forecast point errors and returning this as a single series. It's then trivial to apply this to your forecasts to obtain the intervals. This is what the new plot() method does under the hood. I think it should still be fairly easy to interface with some of these other packages even with this different approach but please let me know if you disagree.
FYI, prediction_errors supports the calculation of producing PIs at different confidence levels, something that was discussed in #97. It also allows each forecaster to define its own methods for PI calculations. I didn't attempt to implement this for any of the other forecasters as this could be quite a lot of code for some of them (in the case of ETS forecasting, I believe some models don't even have a known formula - for this reason I implemented the interface in a way that makes it optional).
I thought about merging in the new notebook with the existing forecasting notebook, but wasn't sure how to best make them fit together. I'm happy to take a steer on this if you'd prefer me to put all the forecasting stuff in a single notebook before merging the PR.
PR checklist

[x] I have added unit tests and made sure they pass locally.
[x] I have updated the existing example notebooks or provided a new one to showcase how my algorithm works.
[x] I have updated sktime's estimator overview and I'm committed to maintain my contribution and provide bug fixes if necessary.

Nice, great work!


Fix the Pages in Automotive Security Suppliers

The pagination for the directories is not professional.  Need to check what the problem is.

@heldyboy  This is fixed :


Blazor preview 8 client crashes with target framework .netstandard 2.1

Describe the bug
The Blazor preview 8 (version 3.0.0-preview8.19405.7) client crashes with target framework .netstandard 2.1 with a System.TypeLoadException: VTable setup of type System.Text.Json.Utf8JsonWriter failed. See the screenshot for additional details from the stacktrace logged by WASM.
I discovered this while updating my Blazor project from preview 6 to preview 8 and then trying to reproduce the crash from a clean Blazor solution.
To Reproduce
Steps to reproduce the behavior:

Create a new 'Blazor app' project
Choose template 'Blazor WebAssembly App' and check 'ASP.NET Core hosted'
Edit the solution's client project's .csproj file and set the target framework .netstandard 2.1
Rebuild the solution
Run the app and open the console to see the error

Expected behavior
No crash. Same behavior as when target framework .netstandard 2.0 is selected.
Screenshots

Mono's WASM implementation only supports netstandard2.0

Was it just fortuitous that it used to work on netstandard 2.1 with preview 6?

See #12568 dotnet/corefx#39767

This is now in PR: https://github.com/aspnet/AspNetCore/pull/16808


Improving CONTRIBUTING document

Proposed changes
In this PR I proposed to update the CONTRIBUTING.md doc. Here's the list I updated:

improving ToC
updating labels section
mention convention commit format in PR guide
removed translations section (we don't have any other languages in the docs)

I'm not sure about labels section. We haven't formally (?) arrange the labels that we created and used? Like which labels used on PR only, or issue only? Or what guideline for the good first issue label?
Please let me know if there's something wrong/missing. Edits are also welcome to improve this document and/or PR. 😉
Thanks,

Are there any translators working on this project? Any tranlsations planned? If there are no doubts that the framework will grow and be maintained, I would like to contribute as an English-Russian and English-Ukrainian translator

Are there any translators working on this project? Any translations planned? If there are no doubts that the framework will grow and be maintained, I would like to contribute as an English-Russian and English-Ukrainian translator

hmm from the original maintainers I don't see any translation actions beside of putting an email in the contributing doc. As of myself, I don't have that plan. IMO I think Google Translate is already enough. 😄
Btw @DanielRuf, What do you think?

Btw @DanielRuf, What do you think?

If we would have requests for translations (keeping them synced is extra work) and have a small team for this, then it could be a benefit for users.
But so far I see not many reasons to manage translations ourself.

Hmm so how do we proceed with translation section in CONTRIBUTING doc? How do we implement translation across the docs?

Personally I find it complicated to keep translations in sync, especially on websites where every PR which changes or adds new texts requires extra work from some translation team.
There are services like phrase, poedit and more which allow people to translate the texts, manage them and keep everything in sync.
Otherwise it will become cumbersome like in phpMussel where we had to check and update every translated docs after sonething has changed in the original version or they would differ too much after some time:
https://github.com/phpMussel/Docs/commits/master
I would say: let's replace the section with a text that we are looking for translators, an efficient solution so translators are independent of Git, GitHub and PRs and keep the files so far for reference.

Hmm alright, let's discuss the translation on https://github.com/materializecss/materialize/discussions/182
Btw... how about the labels?

Btw... how about the labels?

The labels are fine. Let's move on with this here. I will merge this now =)


[Bootstrapper] ensure owner and permissions of the uuid path.

this should fix #110

Already implemented this myself


[V2.0.0_CFG-04] Support Output Formats (Markdown and Plaintext)

[V2.0.0_CFG-04] Support Output Formats (Markdown and Plaintext)
Description: Enhance the tree output functionality to support multiple formats like plaintext and Markdown.
Tasks:

Add outputFormat setting to tree-meh configuration.
Implement logic to wrap output in Markdown formatting if specified.
Default to plaintext if no format is selected.

Acceptance Criteria:

Output is correctly formatted based on user configuration.
Markdown output includes proper code block wrapping.

Need to groom/develop this idea more. Moving to next release.


support set upstream host

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

Project coverage is 79.47%. Comparing base (a252e90) to head (7637d52).

Files
Patch %
Lines

pkg/filters/proxies/httpproxy/pool.go
37.50%
3 Missing and 2 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1245      +/-   ##
==========================================
- Coverage   79.50%   79.47%   -0.04%
==========================================
  Files         152      152
  Lines       17289    17295       +6
==========================================
- Hits        13746    13745       -1
- Misses       2876     2881       +5
- Partials      667      669       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Improve findWallDistance()'s returned normal

The normal returned by findWallDistance() isn't really a normal, it's just a normalized vector from the hit point to the source point. The hit point is already returned by this function, and the source point was passed in, so it's easy for users to calculate this themselves if they want.
So, instead, return the bitangent to the actual wall itself, as it's more useful.

I'm actually not sure if this is correct or not... I made this change on my fork originally because I seemed to be having problems with the normal vector used to steer agents away from walls. But now that I think about it, the nearest wall point always should have a normal that points directly towards the source point, I think? So maybe this is unnecessary... but I'm not sure....

Perhaps this is useful for when the nearest point is a corner?

The nearest wall will not necessarily always have a perpendicular normal to the source point. That would perhaps be the case if you are looking for the nearest edge from within a convex polygon but walls are boundary edges of the broader navmesh structure, and will often be edges that your source point isn't projected directly onto.
The normal shouldn't be simply the direction to the hit point or it shouldn't be called normal. That should be the interior perpendicular direction of the edge if it's going to use the term.

If you hit a vertex then there are multiple normals. I chose to call it
normal, as in "outward facing unit vector". It indeed can be derived from
the hit point and current position.
On Wed, Nov 18, 2015 at 2:12 PM, jswigart<EMAIL_ADDRESS>wrote:

The nearest wall will not necessarily always have a perpendicular normal
to the source point. That would perhaps be the case if you are looking for
the nearest edge from within a convex polygon but walls are boundary edges
of the broader navmesh structure, and will often be edges that your source
point isn't projected directly onto.
The normal shouldn't be simply the direction to the hit point or it
shouldn't be called normal. That should be the interior perpendicular
direction of the edge if it's going to use the term.
—
Reply to this email directly or view it on GitHub
https://github.com/memononen/recastnavigation/pull/120#issuecomment-157692166
.

The wall normal is very useful to have. For example, in many cases the points returned by findStraightPath is directly on top of the wall segment, in which case the normal returned by this function would be useless (as the direction cannot properly be computed).
I'm all for this change, however it is breaking. I'm not sure how we should deal with making breaking changes like this. @hymerman @grahamboree, what do you think?

For this case in particular, if people think both the new and old behaviour is useful (which is what it sounds like), then the new behaviour should be added as a new parameter to the function.
More generally, we shouldn't be afraid to make breaking changes where we feel they're strictly better than the previous behaviour, and where it won't be too disruptive - as long as this is communicated to users, preferably via the code itself (i.e. let's not change the meaning of a parameter without also changing its type or at least its name!).
We'll eventually get round to sorting out official releases which we can tag using good ol' http://semver.org/ and release notes, to flag up non-backwards-compatible changes. Then we can treat the master branch as an unstable, "might change radically at any moment" branch, and encourage users to stick to tagged releases.
Does that sound reasonable?

Yes, that sounds completely reasonable and like a very good way to do it.
However, in this case I would prefer to change the behavior, not add new behavior; the old method of computation can easily be done by the user (simply compute the unit vector in the same way as the code used to do it). The new method is a lot more involved (it requires finding the nearest polygon side that actually constitutes a wall, and then computing its normal).
I think we should merge this change once we have the versioning set up.

I'm with @Janiels on this one.  I'd rather return the more useful vector and let the user do the vector sub and normalize to get what we're already giving them (if they really want it in the first place).
Re: versioning, I think what's been said is a smart way of approaching breaking changes.  I also agree that we shouldn't be afraid to break things in the name of progress, so long as its clearly communicated to the users.  Semantic versioning seems like a good way of communicating this.

I have merged this into the 2.0 branch as we talked about waaaaay back when.


Export to PDF - using MPDF

I got this error when export to PDF
local.ERROR: unlink(C:\Users\user\AppData\Local\Temp\qtsingleapp-lineex-3e70-1-lockfile): Resource temporarily unavailable

I was install mpdf package
Publish excel config
Change config temp_path to another folder (not system temp folder)

---- To fix this issue as my temporary solution ----

Open file ...\vendor\mpdf\mpdf\src\Cache.php

Add this code to __construct
`
public function __construct($basePath, $cleanupInterval = 3600)
{
if (!$this->createBasePath($basePath)) {
throw new \Mpdf\MpdfException(sprintf('Temporary files directory "%s" is not writable', $basePath));
}
 $this->basePath = config('excel.exports.temp_path', $basePath); // <-- I add this code

 $this->cleanupInterval = $cleanupInterval;

}
`
with this code, I can export as PDF file.

How to fix this issue and not hardcoded core source?
Thank you...

Haven't tested it, but I think you should use: PhpOffice\PhpSpreadsheet\Shared\File::setUseUploadTempDirectory(your_path)

@patrickbrouwers Where I should use that code?

@muswanto you can put it anywhere you want, e.g. in a service provider.