(BKR-1009) Don't fail when ip is unavailable in Vagrantfile

I was running into an issue when using the vagrant_custom hypervisor and not using any private_network with a known ip address (only the NAT interface, no hostonly). In all examples, I am using the virtualbox provider.
The first run with provisioning worked perfectly. If I ran it a second time without reprovisioning I would get an exception stating "Unable to determine ip for vagrant box #{hostname}". This was because only on reprovisioning does beaker attempt to parse out an ip address from the Vagrantfile.
I propose that instead of raising an exception, we just return nil for the ip address. As far as I can tell, beaker connects to the machines using the ssh config file generated from the set_ssh_config method. I compared the host.host_hash from a fresh run and a run without provisioning and they seem functionally equivalent (the ip address was undefined vs nil, respectively). Testing so far doesn't seem to have any negative impact (I've tried with the vagrant_custom and vagrant hypervisor).

Can one of the admins verify this patch?

Closing this and reopening a new one so I follow the standards outlined in CONTRIBUTING.md.


Run on scratch image in docker

Describe the bug
When using scratch as a docker container the framework can't extract file and gives a really weird error message.
This is a bug but also a question as i don't understand scratch very well, i thought that if i built my code statically linked and with musl, i will be able to run in scratch base image in docker as all i need is inside the binary
Bad request 400
"Parse http data failed"
To Reproduce
Steps to reproduce the behavior:

Create a handler that will parse formdata/multipart
In the handler, extract a file
Run the program in a dockerfile with scratch as runner

Expected behavior
Better error message or a way to run in scratch
Screenshots
Desktop (please complete the following information):

OS: Linux
Browser chrome
Version [22

Additional context
Scratch is the base image of docker.

Can you provide a repository that contains the Dockerfile and the code you tested?


Integrate the new filter format

Checklist

[x] Manual verification
[ ] Unit test coverage
[ ] E2E test coverage
[x] Needs manual QA?

Summary
Issue addressed:
To standardise where and having filters we introduced a new format for filters similar to ASTs.
Details:

Updating the UI to integrate this new format.
Moving the code to match the selectors/actions format.

Steps to Verify
Play around with filters. There shouldnt be any regressions from main.

Thanks for the review. There is an issue right now with us assuming dimension values are string. This resulted in a few issues. But the type declarations for dimension value params and other places were not updated. We should go through and get a consistent typing for it. Hence, I have left in the any in the filter utils for now.
Regarding E2E, there is a test that changes the filters. There were some failures around it while developing so it catches issues there I believe.

@bcolloran The protobuf type is google.protobuf.Value which can be any value that serializes to JSON. The value is propagated more or less directly to a DuckDB query arg (so e.g. a nested object might be valid if the underlying DuckDB type is a struct).

@AdityaHegde please go ahead and merge this when you are ready. I'm sorry, I should have made more clear: I think this PR is ready to go and it's great! I wanted to dig more into the typing, but I didn't mean to hold you up

@bcolloran The protobuf type is google.protobuf.Value which can be any value that can serialize to JSON. The value is propagated more or less directly to a DuckDB query arg (so e.g. a nested object might be valid if the underlying DuckDB type is a struct).

@begelundmuller ok awesome, thanks that's super helpful! Would it be possible to add a comment that explains why this needs be unknown (i.e. that it could represent any supported DuckDB expression value, including possibly things like nested structs etc)? I think you said it's easy to add comments in the API code that are passed through the codegen to the TS types, right?


Fix device allocation for MSE observer

This PR fixes the pre-allocation of a few tensors used in the MSE observer. The original allocation did not specify the device, which ended up leading to failures due to computation with tensors in different devices.

@dsikka given this is a minimal change, can we land this as is and then overwrite the changes once he other pieces are in place? The benefit is we'll have a quick fix to unblock MLR and ideally a dev version with minimal risk and required overhead for testing to see if it is functioning fully

@dsikka given this is a minimal change, can we land this as is and then overwrite the changes once he other pieces are in place? The benefit is we'll have a quick fix to unblock MLR and ideally a dev version with minimal risk and required overhead for testing to see if it is functioning fully

Yes but we need the tests to pass first


Clarifying scenarios in which the remove transform could/should be used

Purpose
Clarifying scenarios in which the remove transform could/should be used
Changes
Described that the remove transform should also be used when settings are only used in the view.
Caveats
Additional helpful information

I'm done making tweaks for reals now.


Microsoft.PowerToys.Settings.UnitTest does not seem to run correctly on CI

From #5118 bringing all the CI online, this is currently not running unit tests for settings.  Error being thrown is it can't detect tests in the file.

@ryanbodrug-microsoft shouldn't this be a p0 for invest for 20.10?

https://github.com/microsoft/PowerToys/blob/master/.pipelines/ci/templates/build-powertoys-steps.yml seems like it is running but would love to verify this

This is working in ci now


Package request: camilladsp

Project description
A cross-platform tool to create audio processing pipelines for applications such as active crossovers or room correction. (A flexible cross-platform IIR and FIR engine for crossovers, room correction etc.)
Metadata

homepage URL: https://henquist.github.io
source URL: https://github.com/HEnquist/camilladsp
license: gpl-3.0
platforms: linux, darwin

See #337272


Contribute Waterfall to Vizro visual vocabulary

Thank you for contributing to our visual-vocabulary! 🎨
Our visual-vocabulary is a dashboard, that serves a a comprehensive guide for selecting and creating various types of charts. It helps you decide when to use each chart type, and offers sample Python code using Plotly, and instructions for embedding these charts into a Vizro dashboard.
Take a look at the dashboard here: https://huggingface.co/spaces/vizro/demo-visual-vocabulary
The source code for the dashboard is here: https://github.com/mckinsey/vizro/tree/main/vizro-core/examples/visual-vocabulary
Instructions

Get familiar with the dev set-up (this should be done already as part of the initial intro sessions)

Read through the README of the visual vocabulary

Follow the steps to contribute a chart. Take a look at other examples. This commit might be helpful as a reference to see which changes are required to add a chart.

Ensure the app is running without any issues via hatch run example visual-vocabulary

List out the resources you've used in the README

Raise a PR

Useful resources:

Waterfall: https://plotly.com/python/waterfall-charts/
Data chart mastery: https://www.atlassian.com/data/charts/how-to-choose-data-visualization

Hi @huong-li-nguyen, can I work on this one?

Yes, @sammitako! That would be great 👍

PR: https://github.com/mckinsey/vizro/pull/786


[Proposal] GridView::headOptions

I propose to add a property yii\grid\GridView::headOptions. This will allow us to use this bootstrap4 opportunities.
What steps will reproduce the problem?
<?= yii\grid\GridView::widget([
    'dataProvider' => new yii\data\ArrayDataProvider([
        'allModels' => [
            ['col1' => 'val1-1', 'col2' => 'val1-2'],
            ['col1' => 'val2-1', 'col2' => 'val2-2'],
        ],
    ]),
    'headOptions' => ['class' => 'thead-light'],
]); ?>

What is the expected result?
<table>
    <thead class="thead-light">
        ...
    </thead>
    ...
</table>

What do you get instead?
Error: Setting unknown property yii\grid\GridView::headOptions
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.1.27

Operating system
Ubuntu

The idea is great, but Yii2 is in feature-freeze mode
FR needs to be migrated to https://github.com/yiisoft/yii-dataview


Review and merge codal-microbit-nrf5sdk PRs

As they are in the micro:bit Foundation org they cannot be added to the CODAL project board, so creating this issue to be able to track them:

https://github.com/microbit-foundation/codal-microbit-nrf5sdk/pull/12
https://github.com/microbit-foundation/codal-microbit-nrf5sdk/pull/13

When I tried the ble_test() sample just now the services and characteristics don't all fit. The UART characteristics are missing.
The first PR above was intended to fix that, but some caution is needed now because the build has changed since I made that PR.

@microbit-carlos @JohnVidler I think the effect of not having https://github.com/microbit-foundation/codal-microbit-nrf5sdk/pull/13 is that when MakeCode is set to no pairing required, the build uses open security for everything except the Nordic DFU characteristic. The iOS app first writes to an open security characteristic, then fails to flash with the error authentication is insufficient for the Nordic DFU. A workaround is to use MakeCode Edit Settings As Text to define "security_level": "SECURITY_MODE_ENCRYPTION_OPEN_LINK" instead if the default null.

So does that mean that when this option is set in MakeCode the micro:bit cannot be flashed via the apps?

@microbit-carlos I believe an open link hex from MakeCode can be flashed but can't be flashed over. Only tested in iOS. I dragged the the open link hex to the MICROBIT drive, then tried to pair with and BLE flash over it with the iOS app.
It may be that if you have paired with another hex, then BLE flashed an open link hex, the pairing will allow another hex to be flashed. I'm not sure exactly what MakeCode creates, but I think this is a likely explanation for the authentication is insufficient error.

Is it safe to assume this was also a problem in MakeCode v5? The issue is not something introduced between v5 and v6?

Compare
https://github.com/microbit-foundation/codal-microbit-nrf5sdk/blob/master/sdk_config/sdk_config.h#L102
with
https://github.com/lancaster-university/codal-microbit-v2/blob/master/inc/MicroBitConfig.h#L178
The latter is correct because it doesn't redefine MICROBIT_BLE_SECURITY_MODE when MICROBIT_BLE_OPEN has already defined it.
If I build microbit-v2-samples ble-test() with the codal.json below I can go through the pairing process with it in the app, then flash over it. MICROBIT open good.zip
If I remove the last line from codal.json or change the value to null and rebuild, there are lots of warnings (warning: "MICROBIT_BLE_SECURITY_MODE" redefined) but it does build. Pairing with the result fails with Authentication Insufficient.
MICROBIT open bad.zip
I also get Authentication Insufficient pairing with this, saved from MakeCode v5  microbit-openlink-v5 (8).zip https://makecode.microbit.org/_UMt84d9Cuiut
If I pair with a normal, MakeCode just works hex, and BLE flash an open hex over it,  sending another hex initially fails. If it was a "good" open hex, it's possible to recover by pairing again, but pairing with a "bad" open hex fails with Authentication Insufficient.
{
    "target": {
        "name": "codal-microbit-v2",
        "url": "https://github.com/lancaster-university/codal-microbit-v2",
        "branch": "master",
        "type": "git"
    } ,
    "config":{
        "DEVICE_BLE": 1,
        "MICROBIT_BLE_ENABLED" : 1,
        "MICROBIT_BLE_PAIRING_MODE": 1,
        "MICROBIT_BLE_DFU_SERVICE": 1,
        "MICROBIT_BLE_DEVICE_INFORMATION_SERVICE": 1,
        "MICROBIT_BLE_EVENT_SERVICE" : 1,
        "MICROBIT_BLE_PARTIAL_FLASHING" : 0,
        "MICROBIT_BLE_OPEN" : 1,
        "MICROBIT_BLE_SECURITY_LEVEL": "SECURITY_MODE_ENCRYPTION_OPEN_LINK"
    }
}


stop the redirect to the root URL

Hi, thanks for a fascinating project!
I just installed all the code and samples on my own server, and its all working fine: https://wikischool.org/gfm.html
The only thing I can't seem to figure out (perhaps because I'm not that knowledgeable about service-workers), is that when one visits the URL, there is a redirect to the root URL. Where can I prevent that from happening?
Thanks.

Probably this line:
                <Route render={() => <Redirect to="/" />} />

This redirects all routes that don't match the defined routes to /.
https://github.com/generative-music/generative.fm/blob/master/src/components/app/index.jsx#L35

Thanks, I tried changing those routing lines, but the same redirection behavior persists.


How to swipe only one and turn off another

This document wrote  https://github.com/jemise111/react-native-swipe-list-view/blob/master/docs/manually-closing-rows.md

If you are using'SwipeRow', please define a'ref' for him and use'ref' to call'closeRow()'

SwipeListView  not work closeOnRowBeginSwipe and closeOnRowOpen

Please check if your 'data' contains' key '

Please check if your 'data' contains' key '

This helped. closeOnRowBeginSwipe prop works for me.

I meet this problem too when I create a SwipeListView, and use SwipeRow in the renderItem funciton. I found my data not contains the 'key', so I add a keyExtractor property in the SwipeListView element and solved this problem.
_keyExtractor = (item, index) => {         return index.toString();     }
   <SwipeListView                         useFlatList                         keyExtractor={this._keyExtractor}                         data={data}                         renderItem={(data, rowMap) => (                             <SwipeRow> ....</SwipteRow>    />

Hey @methineeinkan I agree with @luojiong , this is almost always solved by ensuring you either have a key for your data or pass a keyExtractor prop.
Looks like that is working for people in this thread, so I will close this, but reopen if you still have issues, thanks!


Action doesn't fail on failed uploading

Hei,
I've just played with your action. I noticed that a error while uploading still results in a green pipeline.
Server logs HTTP-401:
webdav.fieldtracks.org:80 <IP_ADDRESS> - fieldtracks [22/Jan/2023:17:18:52 +0000] "PUT /JellingStone/JellingStone-b22b81a7be65a0341758024bcc8aef3b8f03975e%2Bgh3980720524.zip HTTP/1.0" 401 704 "-" "axios/0.27.2"

Action output is:
Run bxb100/action-upload-webdav@d19f1edf785abf4b0b7f818ba46b6dba9b0334c6
  with:
    webdav_address: https://webdav.***.org
    webdav_username: ***
    webdav_password: ***
    webdav_upload_path: /JellingStone
    files: JellingStone*.zip
    keep_structure: false
    fail_on_unmatched_files: false
  env:
    AUTOMATIC_RELEASES_TAG: current-main
Current directory: /home/runner/work/JellingStone/JellingStone
📦 Uploading /home/runner/work/JellingStone/JellingStone/JellingStone-b22b81a7be65a0341758024bcc8aef3b8f03975e+gh3980720524.zip to /JellingStone/JellingStone-b22b81a7be65a0341758024bcc8aef3b8f03975e+gh3980720524.zip

I'd expect the action to fail if the server responds with HTTP-401.

fixed in the latest commit


希望支持路由缓存功能

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>

What is expected?
希望支持路由&页面缓存功能，诸如从列表页进入详情页再返回列表页时可缓存之前的列表数据这种场景，有计划支持么

+1

自己写一个


Fixed duplicate view_render_event for product descriptions

The following view render event was declared twice, both before and after the product description:
{!! view_render_event('bagisto.shop.products.view.description.before', ['product' => $product]) !!}
I fixed the second instance to be bagisto.shop.products.view.description.after

@MattApril thanks


Add functionality to pass context while rendering

Hi,
First of all, Thanks a lot for the package 🚀. It is very nice to have this kind of DSL for GraphQL.
Currently I am working on a project where I need to have one optional argument according to the logic. We need to decide to render the argument only the time when we are rending the whole query.
So it would be nice to pass some context while rendering. Therefore, we can extend the Argument overwrite the template to not render the argument if flag is True in the context.
So it can be like following
In jinja template:
// optional_argument.jinja2
{% if ctx.render_foo_field %}
{{ name }}: {
  {{ value }}
}
{% endif %}

class OptionalArgument(Argument):
    template = "optional_argument.jinja2"
    def render(self, context=None):
        template = template_env.get_template(self.template)
        return template.render(name=self.name, value=self.value, ctx=context)

query = Query(name="bar", arguments=OptionalArgument(name="foo", value="bar")

print(query.render(context={"render_foo_field": True}))
# This query is with the foo field argument

print(query.render(context={"render_foo_field": False}))
# This one will not have foo field as argument

What do you think? If you are interested, I can make a PR

Hello, thanks for using graphql-query. I'm glad the library is useful.
i think that this is a nice idea. Can you create a PR with general context for each render method?

@denisart Thanks! I will create a PR for passing context to each render method!


Gentx Indonode

Hello , Indonode Validator is eager to participate in the gentx ceremony , our validator is 100% secured with 24/7 Monitoring, and we provide some services too!
Indonode Services Included :
🔥API/REST Endpoint
🔥RPC Endpoint
🔥Genesis mirror
🔥IBC Relayers
🔥Live Peers
🔥Addrbook file
🔥State Sync
🔥Snapshot
🔥Installation Guide
🔥CLI Cheatsheet Command
For more info about us : https://indonode.net/
Email us at<EMAIL_ADDRESS>Discord : Indonode#5255
Telegram : t.me/elangrr
Twitter : @indonodev

Fixed the folder from PR 29

Genesis phase is over, if you want to become a validator - follow our docs and get enough NLS allocation to get into the active set of validators
https://docs-nolus-protocol.notion.site/Run-a-Mainnet-Validator-f64624c3423c4c41922c3a1d0d342e17


API shows unexpected PR for a commit

Description
The API endpoint GET /repos/{owner}/{repo}/commits/{sha}/pull returns a pull request in more cases than I would expect:
I created the example repo https://demo.gitea.com/betanummeric/pr-test1 as an example:
* 2e0af5a76e4e02ff9ee4d52949d25fd229683754  (HEAD -> yetanother, origin/yetanother)
| * a8a7c696d7de8abd600798966caa4a47a6c420ca  (origin/other, other)
| * 827ed730869e32856e56da7be2a294dbf89a1b93  (origin/mergeme, mergeme)
|/
* bd0050a443969356bf847bed330aa34a53be00cf  (origin/main, main)

I created a PR from branch mergeme to main: https://demo.gitea.com/betanummeric/pr-test1/pulls/1
The API returns that PR for every commit hash of the repo. I would have expected this to return the PR only for commit 827ed730869e32856e56da7be2a294dbf89a1b93, because only that will be applied to the target branch in the PR.
I'm using this endpoint to determine if a push event relates to some PR. I work around by checking if the PR head matches the head of the push event.
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
tested with gitea 1.22.1 and https://demo.gitea.com/ at 1.23.0+dev-464-g19af534462
Database
None

The /repos/{owner}/{repo}/commits/{sha}/pull API was added by #29243. According to its description, this API is used to get the merged PR associated to a commit. If the PR is not merged, the API should return 404.
However, now the API can return a PR even if it has not been merged yet. This is caused by a bug.
Here we try to get the SHA by the sha path param.
https://github.com/go-gitea/gitea/blob/2fc347bcb362af533d0e99b3a34788128ac97010/routers/api/v1/repo/commits.go#L357
But there is not a sha param in the path. The correct param should be ref.
https://github.com/go-gitea/gitea/blob/2fc347bcb362af533d0e99b3a34788128ac97010/routers/api/v1/api.go#L1286-L1289

Thanks for the quick fix. :)
For the record, I wanted to use the API endpoint to get the PR (if any) by commit sha regardless of whether the PR is merged or not. I want to check in a push webhook if the push belongs to a PR. I guess I need to find a different solution for that now.


Templating child component file paths is relative to the child which could be confusing

Is your feature request related to a problem? Please describe.
We should take a look at PKG_TMPL for ways that we can improve usability issues like file paths being relative to a child package on import.

This has been resolved


Website down (https://dlcdevkit.com/)

Connection timeout

thanks, tracked down DNS issues working now,
https://dlcdevkit.com


Fix RTS / RSI stream packaging when AES encryption is involved

As a user  I want to have the same good user experience with RSI TV series or RTS documentaries as with other kinds of contents (news, e.g.).
Currently seeking does not work as smoothly with these contents. Moreover the Apple TV standard playback UI shows an empty thumbnail while seeking, which is useless.
Context
RTS / RSI stream packaging delivers EXT-X-I-FRAME-STREAM-INF playlists but those are broken because of the AES encryption. When fast forwarding the player cannot read these frames and therefore remains stuck. This explains why the Apple TV does not present thumbnails and why the player in general remains stuck at the seek start time instead of smoothly coping with seek requests.
We should get rid of these I-frame playlists. They are not useful anyway and just make the user experience worse.
Acceptance criteria

The player is able to smoothly cope with seek requests when playing RSI TV series or RTS documentaries, for example.

Tasks

[ ] Discuss the matter with @bgaudaen.
[ ] Update stream packaging to remove I-frame playlists.
[ ] Deploy the update for RSI as well.
[ ] Check in players.

As discussed with @bgaudaen:

Short-term fix: Remove I-frame playlist with vod_hls_output_iframes_playlist parameter set to off in the corresponding configuration.
Mid-term solution: Use same fmp4 configuration for CH content as well.

Must notify RSI so that they can do the fix as well.

We must notify Ivan at RSI so that he can forward the information further. We can provide the corresponding change as information.

RSI has been contacted. Done.


Kochiku-worker assumes Kochiku server is on HTTPS

lib/kochiku/jobs/build_attempt_job.rb has https hardcoded. It's not going to take long before someone is going to run into this because I assume that most people will serve Kochiku over http.
I assume the best solution is to add a configuration option for this?

This was fixed a long time ago in #18


category and sub-categories

**What changed? **
Added category:defi and subcategories: for stablecoin, lending/borrowing and liquidity management
Notes to reviewers
@wbnns I created this new branch containing the category and subcategories, per the new standard.
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/2

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2

@iafhurtado
Hi there! Thanks for the updates! Could you please rebase to fix the merge conflict?

I think it should be clean now @wbnns or?

Ok, I apologize @wbnns , I will scrap this PR and have created a new one that has no conflicts that I can see: https://github.com/base-org/web/pull/1441


Promblems concerning Mixtral evaluation

When testing Mixtral 8x7b with 2xA100-80G GPUs, I employed the model vllm with its most recent package (vllm 0.2.6). However, I encountered a CUDA Out Of Memory (OOM) error, even when setting the batch size to 1. I came across https://github.com/QwenLM/Qwen/issues/819 which suggests that the error might stem from the latest update of vllm. Subsequently, downgrading vllm to version 0.2.5 resolved the issue, allowing for error-free inference. You may update your code to support the updated version of vllm.

Thanks for the report!

Thanks ！ help a lot ！ So, why there's error? is the issue with vllm?

When I ran MMLU with vLLM 0.2.7, I found the it leads to OOM even for a 7B model when I set batch_size='auto'. Either adjusting batch_size to 1 or using a small gpu_memory_utilization value such as 0.6 could solve this OOM problem, but it tends to be slower.
After some debugging, I found it is related to the generation parameters prompt_logprobs=2. Whenever we enable this feature, we have a higher chance of OOM. For a normal generation task without prompt_logprobs, I can even run a llama2-70b without issues.


on Awards view add a third button "Awards view" navigating to newly created "awards list" view

done, pull request merged https://github.com/zetonteam/zeton_react/pull/89


Error: Invalid display: fullscreen

Why does gulp-real-favicon throw an error when display in manifest is set to 'fullscreen'? It is a perfectly valid value according to the specs: https://w3c.github.io/manifest/

This is because of the service itself, not the Gulp plugin.
The service was updated a minute ago. Could you retry?


[BrokenLinksH2] Fix path in link

Fixing the link path in line 58

Docs Build status updates of commit 0e15fcc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/apis/syntex/syntex-model-rest-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@tfosmark - Please can you review and merge this PR!

Global effort to fix broken links
@andrewconnell
The Content & Learning team is fixing broken links on docs.microsoft.com for the rest of H2. This effort will eliminate potential accessibility, security, and usability issues. This PR includes only link fixes and does not change other content. Please review within five business days and merge, or comment in the PR with any changes you'd like to see. Thanks!

Docs Build status updates of commit 866dfd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/apis/syntex/syntex-model-rest-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 43889e2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/apis/syntex/syntex-model-rest-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add initial azavea.opentripplanner role, with an example

I don't see anything for the nginx config in here; we'll probably want to serve OTP behind it.

@flibbertigibbet I'm not sure that is something we will always want to do. What if our backend app is using the API as opposed to a frontend? We may not always want nginx on the same machine as well.

@flibbertigibbet no, theres nothing for that here. I assumed that would be more of a project level thing, since each project would potentially have multiple nginx routes. OTP is served to localhost on 8080 for now.

Yeah, got it, this is just an OTP role.

@hcastro updated PR with feedback, left @sharph 's recommendation to load the gtfs data for a followup PR, otherwise everything should be taken care of.

Re-provisioning from scratch locally right now to confirm everything still works.
Otherwise, this PR is pointed at master. I made all of the Ansible role repositories follow git-flow with a develop branch because it helped formalize the version release process. Would you mind pointing this at a develop?

Of course. Was going to do that after getting the ok and rebasing this down. But I'll just do it now.

:+1:

Superseded by #2


Prepend module name to TestItem IDs

It is possible to have two identically named suites in two different test targets. These were being erroniously rolled up in to the same parent TestItem.
Disambiguate these TestItems by prepending the module name. This has the added benefit of making the TestItem IDs a fully qualified name that can be passed to swift test.
The module name is pulled from the compiler arguments for the target. If no module name can be found we fall back to the targetID for the ConfiguredTarget.

@swift-ci Please test

@plemarquand Could you also create a cherry-pick PR for this change to release/6.0? https://github.com/swiftlang/sourcekit-lsp/blob/main/CONTRIBUTING.md#opening-a-pr-for-release-branch

@swift-ci Please test

@swift-ci Please test Windows


Candlestick chart not supported on desktop

This is known - unfortunately flutter doesn't support webviews on desktop.

This is known (see #2123 (comment)) - unfortunately flutter doesn't support webviews on desktop.

Fair enough. Probably low priority to fix, but I thought it would be good to document it. We have at least some users on desktop.

We have at least some users on desktop.

Ah, interesting - I was not aware of this... we could fall back to the old implementation, but it was quite complex by comparison

Afaik "Desktop" should be supported because we only support desktop for M1s which is iOS no?
Eitherway, we are now using a library which supports it. Here is a short how-to: https://inappwebview.dev/docs/intro#setup-macos

From what I can tell, inappwebview does not support desktop in general:

It does seem to support MacOS though


feat: introduce AnnotationDependentResourceConfigurator concept

The idea is to be able to configure dependents using annotations
directly so that we can remove the special handling of
KubernetesDependentResource from AnnotationControllerConfiguration. This
results in dependent resources being instantiated and configured
directly when processed from the annotations in the managed case, thus
rendering the DependentResourceFactory concept obsolete. This should
also lead to further simplification later.

Made some comments, nothing serious, I still think this could be done using an annotation instead of the interface, but we can experiment with that later. There are some parts what is not clear to me, we should clarify document those.

Otherwise looks very good :)


Fix delta role error when using custom LLM

This addresses a delta chunk issue that happens when you use a custom baseURL on the openai chat model. Some models like llama 2 on openrouter may have a empty delta and result in a undefined error.
Example error:
Cannot read properties of undefined (reading 'role')",
  "error.stack": "TypeError: Cannot read properties of undefined (reading 'role')\n    at _convertDeltaToMessageChunk (/home/ubuntu/node_modules/langchain/dist/chat_models/openai.cjs:72:24)\n    at ChatOpenAI._streamResponseChunks (/home/ubuntu/node_modules/langchain/dist/chat_models/openai.cjs:409:27)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async ChatOpenAI._streamIterator (/home/ubuntu/node_modules/langchain/dist/chat_models/base.cjs:77:34)\n    at async RunnableSequence._streamIterator (/home/ubuntu/node_modules/langchain/dist/schema/runnable/base.cjs:780:30)\n    at async Object.pull (/home/ubuntu/node_modules/langchain/dist/util/stream.cjs:73:41)

on _convertDeltaToMessageChunk, openai works fine but when you start using models from openrouter or other baseURL llms, it doesnt take in account for empty deltas and assumes theres always a value.
I was able to test with a custom baseURL and normal openai that this works with no errors on streaming after this tweak.

Fixes # (issue)

I think this is probably a simpler fix? Can you test?

Thanks!


Bug: [Fzf-lua] invalid previewer 'bat  --paging=never --style=plain --theme=base16'

RTFM Checklist

[X] I have searched exisiting issues / discussions
[ ] I have read the Wiki including the Advanced section
[ ] I have read man fzf / I am well versed in shell fzf

Operating system
Mac
Shell
fish
Neovim version (nvim --version)
NVIM v0.10.1 Build type: Release LuaJIT 2.1.1723675123 Run "nvim -V1 -v" for more info
Fzf version (fzf --version)
0.54.3 (brew)
Output of :lua print(os.getenv('FZF_DEFAULT_OPTS'))
--bind 'ctrl-p:up,ctrl-n:down'
Is the problem reproducible with mini.sh?

[X] My issue is reproducible with mini.sh
[ ] My issue IS NOT reproducible with mini.sh
[X] I have not tested with mini.sh (not relevant, requires LSP, Windows, etc)

Fzf-lua configuration
require('fzf-lua').setup({
				files = {
					fd_opts = "--type f " .. vim.fn.getenv("FD_DEFAULT_COMMAND"):gsub("^fd%s*", ""),
				},
				git = {
					files = {
						cmd = "git status --porcelain | awk '{print $2}'",
					},
				},
				fzf_bin = "fzf-tmux",
				fzf_opts = {
					["--border"] = "sharp",
					["--no-separator"] = "",
				},
				fzf_colors = {
					["bg"] = { "bg", "Normal" },
					["fg"] = { "fg", "Normal" },
					["border"] = { "fg", "Normal" },
				},
				fzf_tmux_opts = { ["-p"] = "80%,90%" },
				winopts = { preview = { default = "bat  --paging=never --style=plain --theme=base16" } },
				manpages = { previewer = "man_native" },
				helptags = { previewer = "help_native" },
				tags = { previewer = "bat_async" },
				btags = { previewer = "bat_async" },
			})

Describe the bug / steps to reproduce
invalid previewer

This isn't a bug, bat is the name of the previewer table, if you want to define a different command use previewers.bat:
require("fzf-lua").setup({
  previewers = {
    bat = {
      cmd   = "bat",
      args  = "--paging=never --style=plain",
      theme = "base16"',
    },
  }
})


Sphero bolt set_matrix_pixel error on bad pixel value

I accidentally tried to use set_matrix_pixel on a negative pixel value, which crashes the program in the following way:
"spherov2\controls\v2.py", line 157, in new_packet
    packet = Packet(flags, did, cid, self.__seq, tid, sid, bytearray(data or []))
                                                           ^^^^^^^^^^^^^^^^^^^^^
ValueError: byte must be in range(0, 256)

While it makes sense that calling set_matrix_pixel on a negative pixel location wouldn't work, it should ideally be handled gracefully and at the very least return a specific error rather than crashing the program.

That's fine, but having a specific exception that lets you know that the issue was that the pixel coordinate was not valid (outside of the 0-7 range) rather than getting an error from an internal function with an amiguous relationship to set_matrix_pixel would be more understandable.


Using vueuse but npm requires me to npm install --save @vue/composition-api/dist/vue-composition-api.esm.js

Versions

nuxt: 2.15.7
node: v14.17.3

Reproduction
repo: https://gitlab.com/tonypythoneer/nuxt-bug
When I try to use Vueuse in my code and npm run dev, it will give this error log:
https://gitlab.com/tonypythoneer/nuxt-bug/-/blob/main/pages/index.vue#L27
✖ Client
  Compiled with some errors in 9.32s

 ERROR  Failed to compile with 1 errors

This dependency was not found:

* @vue/composition-api/dist/vue-composition-api.esm.js in ./node_modules/vue-demi/lib/index.mjs

To install it, you can run: npm install --save @vue/composition-api/dist/vue-composition-api.esm.js

When I don't use any function from vueuse, nuxt won't shoot errors.
https://gitlab.com/tonypythoneer/nuxt-bug/-/blob/main/pages/index.vue#L57-L59
onMounted(()=> {
  set(domReady, true);
});

I feel confused about why using vueuse  will cause nuxt to break.

Additional Details

Steps to reproduce
What is Expected?
What is actually happening?

Related https://github.com/vueuse/vue-demi/issues/76


Messages sent to market participants contains Xml Schema namespace and location causing it to fail schema validation

Incident owner: SME Irene, ticket: INC0286645
A market participant has reported failing schema validation on a message received from metering point domain.
Issue: XmlSchemaNamespace and XmlSchemaLocation are provided in the message sent to market participant, see yellow marks below. Those shall be removed.

Please ensure no outbound messages contain XmlSchemaNamespace and XmlSchemaLocation.
Issue was also present in Charges domain (see original issue), but was fixed by this PR.

Deployed and tested that it works in U-001 and B-002.

Note for Batman. Story had a 1 in complexity.


Enable completion of variables across scriptblock scopes

PR Summary
Enables completion of variables assigned in other scriptblocks like:
ls | foreach -Begin {$MyVar = "Hello"} -Process {$MyV<Tab>}
Scriptblocks that are executed as commands with ampersand are explicitly excluded because variables assigned in those are not available outside the scope.

PR Context

PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[X] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[X] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[X] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[X] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

The change enables completion on some commands that are not appliable to the assumption, such as Invoke-Command, New-Module, and Register-ArgumentCompleter.
Quick search in a default session shows the following cmdlets that have parameter with the type ScriptBlock, some of them do not run the script block in the calling scope. So, it's better to restrict when this completion should be enabled.
PS:1> gcm -ParameterType ([scriptblock])

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          ForEach-Object                                     <IP_ADDRESS>0 Microsoft.PowerShell.Core
Cmdlet          Invoke-Command                                     <IP_ADDRESS>0 Microsoft.PowerShell.Core
Cmdlet          Measure-Command                                    <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          New-Module                                         <IP_ADDRESS>0 Microsoft.PowerShell.Core
Cmdlet          Register-ArgumentCompleter                         <IP_ADDRESS>0 Microsoft.PowerShell.Core
Cmdlet          Register-EngineEvent                               <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Register-ObjectEvent                               <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Set-PSBreakpoint                                   <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Set-PSReadLineKeyHandler                           2.3.1      PSReadLine
Cmdlet          Set-PSReadLineOption                               2.3.1      PSReadLine
Cmdlet          Start-Job                                          <IP_ADDRESS>0 Microsoft.PowerShell.Core
Cmdlet          Trace-Command                                      <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Where-Object                                       <IP_ADDRESS>0 Microsoft.PowerShell.Core

@daxian-dbw Good point. I've changed it to only work for dot sourced scriptblocks, and arguments to Foreach/Where-Object. What prompted this change was me writing a pester test and being annoyed that a var in BeforeAll was not completable. Can I add third party commands like "BeforeAll" and "BeforeEach" to the whitelist?

Can I add third party commands like "BeforeAll" and "BeforeEach" to the whitelist?

Sure, I think they should be in the whitelist. You are really solving a pain point here 👍


prepare signage for onsite

Preparing signage for onsite use: directional, program related (what sessions are where, daily schedule for each room to be displayed outside of the room). Other?

This worked fine.


fix: ignore notifications received offline

- What I did

Add a new preference to the AtClientPreferences to optionally ignore the notifications received when offline upon the subsequent restarts.

- How I did it

In AtClientPreferences add a boolean variable fetchOfflineNotifications which defaults to true (the existing behaviour). Optionally can be set to false to ignore the notification received when offline.

- How to verify it
- Description for the changelog

Tests ran in local with changes:
**Monitor first run**
----------------------
/home/sitaram/DevTools/flutter-sdk/flutter/bin/cache/dart-sdk/bin/dart run test -r json /home/sitaram/IdeaProjects/atsign/core/at_client_sdk/at_client/test/samples/monitor/monitor_single_subscription_regex.dart
Testing started at 10:19 am ...
INFO|2022-09-15 10:19:55.039054|HiveBase|commit_log_225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:19:55.059807|HiveBase|225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:19:55.254544|Monitor|monitor started for @murali with last notification time: null
alice notification received: AtNotification{id: 5485a80e-9a27-446e-b2b6-57d6d7298bee, key: @murali:text-0, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>396, value: null, operation: update}
alice notification received: AtNotification{id: 542f1448-e585-417e-8b0a-d090a43def1b, key: @murali:text-1, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>389, value: null, operation: update}
alice notification received: AtNotification{id: 80f2f235-b2a9-42d0-8c52-373121921570, key: @murali:text-2, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>925, value: null, operation: update}
alice notification received: AtNotification{id: 69bc8b64-ab1d-4775-b074-3acd0055d0b5, key: @murali:text-3, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>501, value: null, operation: update}
alice notification received: AtNotification{id: -1, key: statsNotification.@murali, from: @murali, to: @murali, epochMillis:<PHONE_NUMBER>798, value: 2, operation: update}
alice notification received: AtNotification{id: 91171f82-27e5-4dd8-8a33-2819d5596ada, key: @murali:text-4, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>986, value: null, operation: update}

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)

**Monitor second run - client restarted with setting 'fetchOfflineNotifications' to false. So notifications from text-5 to text-15 are ignored.**
------------------------------------------------------------------------------------------------------------------------------------------------------
/home/sitaram/DevTools/flutter-sdk/flutter/bin/cache/dart-sdk/bin/dart run test -r json /home/sitaram/IdeaProjects/atsign/core/at_client_sdk/at_client/test/samples/monitor/monitor_single_subscription_regex.dart
Testing started at 10:20 am ...
INFO|2022-09-15 10:20:27.298624|HiveBase|commit_log_225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:20:27.318969|HiveBase|225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:20:27.513581|Monitor|monitor started for @murali with last notification time: null
alice notification received: AtNotification{id: 643c2773-83a8-4d81-941e-024918dfcd44, key: @murali:text-16, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>296, value: null, operation: update}
alice notification received: AtNotification{id: cd5f9ae2-9105-4b5c-970b-64da4509c81f, key: @murali:text-17, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>830, value: null, operation: update}
alice notification received: AtNotification{id: 18847725-47c6-4601-abad-763bc1f8f8d9, key: @murali:text-18, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>350, value: null, operation: update}
alice notification received: AtNotification{id: 5db81c95-d1fc-4d8d-a230-ceaaa1f95cd9, key: @murali:text-19, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>928, value: null, operation: update}
alice notification received: AtNotification{id: e920ccb8-35b5-48f8-b63d-3362a0d2b9f4, key: @murali:text-20, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>454, value: null, operation: update}

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)

**Monitor second run - client restarted with setting 'fetchOfflineNotifications' to true. So lastNotificationTime is sent to secondary and notification received are fetched.**
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/home/sitaram/DevTools/flutter-sdk/flutter/bin/cache/dart-sdk/bin/dart run test -r json /home/sitaram/IdeaProjects/atsign/core/at_client_sdk/at_client/test/samples/monitor/monitor_single_subscription_regex.dart
Testing started at 10:20 am ...
INFO|2022-09-15 10:20:54.252507|HiveBase|commit_log_225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:20:54.273253|HiveBase|225ec42f3539301ac4076ab97420deb3f2727fab2343674c777eda4885419c79 initialized successfully
INFO|2022-09-15 10:20:54.364573|Monitor|starting monitor for @murali with lastNotificationTime:<PHONE_NUMBER>454
INFO|2022-09-15 10:20:54.509759|Monitor|monitor started for @murali with last notification time:<PHONE_NUMBER>454
alice notification received: AtNotification{id: 28d9e138-39ce-4d35-8809-d9526dbbb1cc, key: @murali:text-21, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>981, value: null, operation: update}
alice notification received: AtNotification{id: 5201c294-d158-4dad-a6f5-2d8164234b24, key: @murali:text-22, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>499, value: null, operation: update}
alice notification received: AtNotification{id: a6e5bdaf-d2f5-4b64-ba47-47272ff639a1, key: @murali:text-23, from: @sitaram, to: @murali, epochMillis:<PHONE_NUMBER>032, value: null, operation: update}

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)

Skipping the notify test because the test is failing due to timezone issue:
Attaching the log below
Epoch Mills from client :<PHONE_NUMBER>123 /// /// Thu Sep 15 2022 16:58:16

ce2e2_secondary.1.cuthczzaiu9e@cicd2x64    | INFO|2022-09-15 11:28:22.817005|InboundListener|RCVD: [_3cc94e4a-c969-44a7-9279-3f1ea909f86e] monitor:1663233673909 /// Thu Sep 15 2022 14:51:13
ce2e2_secondary.1.cuthczzaiu9e@cicd2x64    |

/// Notification time stamp on receiver secondary - Thu Sep 15 2022 15:45:24
ce2e2_secondary.1.cuthczzaiu9e@cicd2x64    | INFO|2022-09-15 11:28:22.817914|InboundConnectionImpl|SENT: [_3cc94e4a-c969-44a7-9279-3f1ea909f86e] notification: {"id":"
af7e1999-6e10-4a80-8dc6-c6d0b2b88cc7","from":"@ce2e1","to":"@ce2e2","key":"@ce2e2:t3XmJmqbd19cJUsHx6gkh/3+FDPsEtEsTu5kRMWq2zk=","value":null,"operation":"update","epo
chMillis":1663236924114,"messageType":"MessageType.text","isEncrypted":true} /// Thu Sep 15 2022 15:45:24

ce2e2_secondary.1.cuthczzaiu9e@cicd2x64    | INFO|2022-09-15 11:28:24.425341|InboundListener|RCVD: [_073cf68a-3b5c-4707-90eb-86b8869a4290] monitor:1663241296123 /// Thu Sep 15 2022 16:58:16


suggestion: add conditional autocollapse options

Is it possible to add extra conditions to the autocollapse option besides resolution?
I've found in certain situations(when watching someone's stream) I would like my channels collapsed while in other situations(when going through text channels) I would rather have them open. Toggleing this with the hotkeys is pretty tedious and the autocollapse option seems to be perfect for this.

I'll admit that this would be a useful feature, but to implement it in a way that would be usable for enough users would require me to abstract a ton of properties of the Discord UI, which would be tedious and likely to break. Due to this, if I implement this feature, it won't be in a way that will just work at the click of a button in the settings panel.
I could implement custom conditionals for autocollapsing but the user would have to have a knowledge of programming and Discord's DOM structure to effectively use it, so at best it would be a feature for advanced users only. For instance, if you wanted it to collapse the channels list while in a call, you would put document.querySelector('.wrapper-1gVUIN') in the channels list conditional input.
If you think what I suggested is a feature you would use, feel free to respond to this message and I'll look into implementing it.

I wouldn't mind looking into the backend stuff to get this to work, it would be a huge QoL feature to me as the streams would be very small otherwise on my vertical monitor. Would be worth the effort to me.

Added in db0434d.
For your specific use case, if you only want it to collapse while in a call, put document.querySelector('.wrapper-1gVUIN') in the channel list box like this:


Added Safe link double protect

A blind safe-link PROTECT_PTR bypass I came across a while ago.
It requires a strong primitive, namely control of the t-cache metadata.
It references another technique called "House of Water" which I will open a PR asap.
It is a technique for getting t-cache control leakless and also indexing a libc pointer leakless.
A sample of these two techniques can be found in the CTF challenge I wrote specifically with them in mind here: Tamagoyaki

This looks good. Thank you for the contribution!


Tests for poseidon2

This change is

#688  👈
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shaharsamocha7 and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.95%. Comparing base (2506932) to head (39f360a).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #688   +/-   ##
=======================================
  Coverage   89.95%   89.95%
=======================================
  Files          75       75
  Lines        9657     9657
  Branches     9657     9657
=======================================
  Hits         8687     8687
  Misses        889      889
  Partials       81       81

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


WS-Fed Endpoint usernamemixed

Hi
We currently use ADFS 3.0 as a «protocol Gateway» to authenticate SharePoint 2013 against our SAML2-based Identity Provider (Shibboleth). We are investigating if we can replace the ADFS Server with a solution based on IdentityServer3 with the WS-Federation plugin together with Kentor Authentication Services (https://github.com/KentorIT/authservices).
In our Proof of Concept Environment 95% woks like a charm, but there is one simple part missing so that we can replace ADFS definitely.
We use a special endpoint from ADFS (/adfs/services/trust/13/usernamemixed) to get a SAML Token based on Username and Password from the Identity Provider "Active Directory". We need this in SharePoint to be able to get the current user context in a web service, because with ADFS and SharePoint by default the impersonation will be done with the IUSER and not with the current logged in user.
Do you know if this can also be implemented in IdentityServer3?
Many Thanks for your help.
Cheers, Joël

That's a WS-Trust endpoint. We don't support that - and it cannot easily be added.

thanks you very much for the fast answer! But it is possible to add the functionality, it is just a question of time, priority and of course money?

Everything is a question of money ;)


Add more sub-interfaces to Events for easier handling in custom EventListener implementations

General Troubleshooting

[x] I have checked for similar issues.
[x] I have updated to the [latest JDA version][download].
[x] I have checked the branches or the maintainers' PRs for upcoming features.

Feature Request
Breakdown big event interfaces into smaller ones, and make them implement multiple smaller interfaces
Example:
GenericSnowflakeEvent -> implements the getId() and getIdLong()
GenericUserEvent -> implements the getUser()/getAuthor()
and more
Example Use-Case
In custom event listeners, this would allow for way shorter code
Personally, I'm writing an annotation based EventListener which also has FilterAnnotations, and the only way i can filter events by user now, is checking if it extends any event which has the getUser or getAuthor methods, which makes it horribly long, and it would require a lot of maintenance in order to keep it up to date with JDA

I myself think this is a pretty rare use-case to justify such an implementation.
There are currently things like the ListenerAdabter which already extends the GenericEvent or other more casual event types.
If you didn't check already, you might wanna take a look at the list of events on the wiki.

I don't see how this would be possible without breaking changes.

Nevertheless, I think the trade-off for shorter code is not as great. We would introduce a lot more complexity to the event system for little gain. You can already capture very generic event types such as GenericEvent and GenericMessageEvent etc. This would introduce more complexity in the code and make things harder to understand for user and maintainer. Another issue is naming, I don't wanna make 300 interfaces that have a single method like "GetUserInterface" which adds "getUser()". There really is no benefit there since you can already check if a method exists using reflections. Making an interface for individual methods of the events is a non-goal and I have to decline.

you can already check if a method exists using reflections

Yeah, this is also what I'd recommend to simplify your code and make it forwards compatible for new events in the future.

i have only one issue with that, in some events to get the user who triggered the event its getAuthor() and in other its getUser()

That's a valid concern, however, that should be easily handleable by checking for both getUser and getAuthor


Loosing attributes with .chunk and .pad

Hello,
Attributes disappear after calling the following DataTree method: .chunk, .pad
datatree version:  '0.0.13'
import numpy as np
import pandas as pd
import xarray as xr
from datatree import DataTree

np.random.seed(0)

temperature = 15 + 8 * np.random.randn(2, 3, 4)

precipitation = 10 * np.random.rand(2, 3, 4)

lon = [-99.83, -99.32]

lat = [42.25, 42.21]

instruments = ["manufac1", "manufac2", "manufac3"]

time = pd.date_range("2014-09-06", periods=4)

reference_time = pd.Timestamp("2014-09-05")

ds = xr.Dataset(

    data_vars=dict(

        temperature=(["loc", "instrument", "time"], temperature),

        precipitation=(["loc", "instrument", "time"], precipitation),

    ),

    coords=dict(

        lon=("loc", lon),

        lat=("loc", lat),

        instrument=instruments,

        time=time,

        reference_time=reference_time,

    ),

    attrs=dict(description="Weather related data."),

)
dt = DataTree.from_dict({"simulation/one": ds, "simulation/two": ds})
dt.attrs = {"a": 0, "b":1}
dt.pad({"loc": 1}).attrs  # returns {}, expected  {"a": 0, "b":1}
dt.chunk({"loc": 1}).attrs  # returns {}, expected  {"a": 0, "b":1}

I tried to replicate the behavior with datatree version's on the xarray repo. The .pad issue disappear:
xarray version '2024.6.0'
from xarray.core.datatree import DataTree
# same operations as above
dt.pad({"loc": 1}).attrs  # OK

but the following operation raises an error
dt.chunk({"loc": 1}).attrs

ValueError: unrecognized chunk manager dask - must be one of: []
Raised whilst mapping function over node with path /simulation/one

Hi @louisletoumelin , thanks for raising this.

I tried to replicate the behavior with datatree version's on the xarray repo. The .pad issue disappear

In that case then unless you want to contribute a fix to this repo, I don't think there is anything to do here, because we're trying to archive this repo very soon.

ValueError: unrecognized chunk manager dask - must be one of: []
Raised whilst mapping function over node with path /simulation/one

Do you have dask installed? If so then this is a separate bug.

The attributes issue should either be fixed or behave the same way as the rest of xarray upstream, and should be re-raised upstream if it's still not working.
The ChunkManger not found issue is independent of DataTree, and again should be re-raised upstream if it's still not working.


Split uBAMs before alignment

Experimental branch to split uBAMs before alignment.

moved scripts/extract_read_length_and_qual.py to this image
added scripts/split_bam.py to this image

splits a uBAM into chunks of max size chunksize

sha256:7c793937b5c0472c34b820b413decef1b74ce02767eafa65627da7e6e5028bf9

Suppress the missing index error in pysam à la https://github.com/pysam-developers/pysam/issues/939#issuecomment-669016051
sha256:795cfb8852b6dc705754ebc4d87d7c170e2388eeb2491f18481e23211294aa6b

sha256:d815a20224f08db414609d931ac1cc2f186f18e50555add5350f6909e15f800e


Change endpoints to be compatible with stellate

Makes the endpoints compatible with the impending Stellate implementation.

.deploy to development

.deploy to development

Closing and opening a new one due to cloudflare pages check blocking.


Some PDFs don't look good

Attach (recommended) or Link to PDF file here:
7157997.pdf
Configuration:

Web browser and its version: Chrome 97.0.4692.71 (Build oficial) (64 bits)
Operating system and its version: Windows 10
PDF.js version: unknown
Is a browser extension: PDF Viewer 2.3.164

Steps to reproduce the problem:

Open attached PDF with PDF Viewer extension

What is the expected behavior? (add screenshot) open with internal Chrome PDF Viewer:

What went wrong? (add screenshot) open with PDF Viewer extension (based on PDF.js)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Duplicate of #3351


Broken link in readme

Registering the Ledger device with the node
...
Currently there are two other ways to do this:
If you have the Nix package manager, use the Tezos baking platform.
Build tezos from the tezos repo with [these instructions]

"these instructions" links to broken link.

@songproducer the link has been fixed in the README.md. This is the updated link: http://tezos.gitlab.io/introduction/howtoget.html#build-from-sources
Thank you


Get pos/line numbers in language

In the language you use goyacc which is wonderful: https://github.com/martian-lang/martian/blob/9a44a92ae0f7de22e61753a2afcd00f32ec34c54/martian/syntax/grammar.y
I was wondering if you knew of how to get useful position and line numbers into the AST, so that each member there could know where an error was for example.
Thanks!

Ast nodes have that information but it isn't currently exported through the public API.  Internally, that's used for error reporting e.g. by AstError: https://github.com/martian-lang/martian/blob/master/martian/syntax/errors.go.  There's a few weird edge cases where positioning information isn't exactly correct, but it's been getting much better...
If there's a good use case for exposing that information publicly then that's an easy change to make.

@adam-azarchs Do you know how goyacc populates this information? I'm having trouble finding it in your source.

goyacc doesn't do it on its own.  The logic for tracking position is in the lexer.  There might be a better way to do things out there.

Since there do not appear to be any further questions here, I'm going to close this issue.


[Validation] - Validate Individual Fields

Would be nice to invoke validate on a single field.
i.e
var result = $('.ui.form').form('validate field[email]');
Where email is the key of the validation property:
            email: {
                identifier: 'Email',
                rules: [{
                    type: 'empty',
                    prompt: 'Please enter an email'
                }, {
                    type: 'email',
                    prompt: 'Invalid email'
                }]
            },

Also would be nice to be able to mark a field as invalid manually:
$('.ui.form').form('get[email]').setInvalid('Email already in use');
$('.ui.form').form('get[email]').setValid();
For when custom validation is written outside of Semantic.

@jlukic up

+1

+1


Implement find time based on schedule + favored time

From ScheduleBot created by lyonva: lyonva/ScheduleBot#34
Currently the bot only checks one or the other. We need to check for all available times, the intersection of both.

Implemented the find time based on schedule + favored time. The bot is able to find the intersection of the available time and the favored time for a event type.


Add CSV export

Nice work!  Two more small comments:

Is it possible that you forgot to add the changes to the cabal file?  In particular, I would expect that cassava is added as dependency, and that we add Zureg.Model.Csv to the exposed-modules array of the library.

We can now selectively add {-# OPTIONS_GHC -fno-warn-orphans #-} to the top of the Zureg.Model.Csv module to make the warnings go away.

Thanks again for implementing this!

Is it possible that you forgot to add the changes to the cabal file?  In particular, I would expect that cassava is added as dependency, and that we add Zureg.Model.Csv to the exposed-modules array of the library.

Oh yes, you are right, I forgot to commit the cabal file.

We can now selectively add {-# OPTIONS_GHC -fno-warn-orphans #-} to the top of the Zureg.Model.Csv module to make the warnings go away.

I will add that now.
Thank you for your comments!


Add notebook demonstrating regionprops

Closes #98

Work-around for plotly rendering bug: https://github.com/plotly/plotly.py/issues/2516


[WIP] Refactor maybe_log_send_result

-refactor

@whatyouhide I'm getting hung up on this -> When I move maybe_log_send_result to the Sentry.Transport.encode_and_post_envelope I get many failing test with the corn integrations:
test start event and same ref stop event have same check-in id (Sentry.Integrations.Quantum.CronTest)
     test/sentry/integrations/quantum/cron_test.exs:233
     Assertion failed, no matching message after 1000ms
     The following variables were pinned:
       ref = #Reference<0.2513758090.1975255046.33127>
     The process mailbox is empty.
     code: assert_receive {^ref, :done}
     stacktrace:
       test/sentry/integrations/quantum/cron_test.exs:253: (test)

Advice?

@savhappy inside Bypass.expect_once on the failing test, put dbg(check_in_body) for example to figure out why it's not matching. That error means something within expect_once failed and the :done message wasn't sent.


10% faster imperfect radix decoding

Using uninitialized(_:) makes perfect radix !(2, 4, 16) decoding 10% faster. This one's a bit strange, and different from (#15), because uninitialized(_:) does not change the computation. Instead, because it ends in a while !digits.isEmpty loop, you can skip this check in the last if-else and that saves 10% for some reason.

To me it seems like adding this expression at the end should make the method more expensive, but the compiler disagrees:
if !error /* digits.isEmpty */ { self = value } else { return nil }

The following yields an additional 10% improvement, but it's too dumb to commit 🥴
// ........
self.init()
let success: Void? = { ... }()
guard let _ = success else { return nil }


delete gtest_to_junit.xsl

the file is no longer needed, because reports are now done using ctest --output-junit ....

:-)


Setup initial Go repository structure

Nothing much to add here.
See Makefile for some details

Lgtm :unicorn:


BUG: interpolate: work array sizes for RectSphereBivariateSpline

Reference issue

closes gh-14591
What does this implement/fix?

Make sure that nuest parameter is large enough when s=0 and pole_continuity=(True, True). This value translates to
iopt(2) = iopt(3) = 1 in the FITPACK routine spgrid.f.
This routine contains the following comment:
  c  nuest : integer. unchanged on exit.
  c  nvest : integer. unchanged on exit.
  c          on entry, nuest and nvest must specify an upper bound for the
  c          number of knots required in the u- and v-directions respect.
  c          these numbers will also determine the storage space needed by
  c          the routine. nuest >= 8, nvest >= 8.
  c          in most practical situation nuest = mu/2, nvest=mv/2, will
  c          be sufficient. always large enough are nuest=mu+6+iopt(2)+
  c          iopt(3), nvest = mv+7, the number of knots needed for
  c          interpolation (s=0).

Therefore, we set in the f2py wrappers nuest = mu+6+2, which is the maximum needed: each iopt array element is at most 1.
Additional information

The fix is precisely what @rkern suggested in https://github.com/scipy/scipy/issues/14591#issuecomment-938762699

There are no additional comments, so let's merge it. Thanks @ev-br

I tested that the commit can be cleanly cherry-picked to the maintenance branch and this has a defect label so adding a backport label.


fix(upload): 修复进度条引起跨域导致文件上传失败问题

由于WEB后端配置CORS未处理OPTION，upload进度条效果引起跨域导致文件上传失败，故增加隐藏进度条选项来解决：回调函数onProgress() {return false} 即可

A bit confused by this solution. I think the correct solution would be to have the backend support OPTIONS method.

In CORS, a preflight request is sent with the OPTIONS method so that the server can respond if it is acceptable to send the request. In this example, we will request permission for these parameters:
The Access-Control-Request-Method header sent in the preflight request tells the server that when the actual request is sent, it will have a POST request method.
The Access-Control-Request-Headers header tells the server that when the actual request is sent, it will have the X-PINGOTHER and Content-Type headers.

ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS

@cs1707 确实应该由后端解决OPTION，但不是必须的，因为preflight可以跳过。
最初用upload组件 上传报错 ：
Access to XMLHttpRequest at 'https://dev.ex.com/api/uploadFile' from origin 'http://localhost:63342' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
而用axios可以上传成功。
网上其他解决方案是在before-upload 或 http-request 改用axios。
这个解决方案是简单的在on-progress方法里 return false 即可像axios一样上传成功。


Add jrnl

Add jrnl
A journal for the command line.

Types of Changes

[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

PR Checklist

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[x] I have added necessary documentation (if appropriate)

@Raymond-Adams
I recommend submitting your command-line tool here:
https://github.com/herrbischoff/awesome-macos-command-line#readme


Add category to challenge view title element and h1 element

For SEO purposes, we should include the challenge category (JavaScript, HTML, Node.js, etc.) both in the <title> element and in the <h1> element before the challenge's name.
For example:

I would like to try and solve this issue

@QuincyLarson, @andmckvr13: This doesn't need changed before the challenges name. I will be doing this in https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11061 😉

@atjonathan bummer, next time then. okay thanks anyways

@andmckvr13, np! You can still work on the title tag tho!

@atjonathan great!! On it :)

@QuincyLarson @atjonathan should the "get set for our basic algorithm challenges" be labeled with the JavaScript tag? I figured that it should be, but don't want to make assumptions

@QuincyLarson @atjonathan shall I also update the Spanish titles too?

@andmckvr13, yes please for other languages! Tagging @QuincyLarson for the other question

What about Portuguese? I can contribute :)

@tmpvnunes yes - we would welcome your contributions! Many of our challenges have already been translated into Portuguese. Join gitter.im/freecodecamp/contributors and ask @vtamara to help you get started :)

I'm closing this in favor of https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11061 which is very similar.


compare only dirs/files/both mode

Hi, would be fine to compare only files/dirs/both with some --option [default both]
For example i want only compare files, but not directories, but sometimes vice versa
Here is example where "dupes" occurs
138851 /data/www/ftp_data_external/exp_documents/1422569840 (0 > 138851)
138851 /data/www/ftp_data_external/exp_documents/1422569840/373446.pdf (0 > 138851)
Is it possible ? At first look to output file from ncdu im not sure tell that row is folder or file. But looks like structured json file. Im not good at this python things :)
Mark it as feature request with low prio :D
Anyway thanks and have a nice day.

What if ncdu-compare will print type of file/dir, e.g.
138851 DIR /data/www/ftp_data_external/exp_documents/1422569840 (0 > 138851)
138851 FILE /data/www/ftp_data_external/exp_documents/1422569840/373446.pdf (0 > 138851)

If you want only files, you can just add | grep FILE.
Would this solve problem?

:1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal:
:1st_place_medal: AWESOME :1st_place_medal:
:1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal: :1st_place_medal:

Done, try version v0.0.7 to see if it's working for you

It works ! Thank you so much !


Do not compile all of swc (try again)

What problem does this feature solve?
Back in

https://github.com/web-infra-dev/rspack/pull/2552

I tried to untangle swc but failed due to pulling in swc::config
What does the proposed API of configuration look like?
This time I suggest to directly copy swc::config into Rspack so we can remove the problem of "swc pulling in everything".
See https://github.com/swc-project/swc/blob/main/crates/swc/src/config/mod.rs

Current cargo build --timings

https://github.com/swc-project/swc/blob/main/crates/swc/src/config/mod.rs

After: 201s -> 172s (=29s), 15% improvement

@suxin2017 Can you take a look at this,
https://github.com/web-infra-dev/rspack/blob/ed6411c6d693ab2e313404f01647fb378bbce0e5/crates/rspack_loader_swc/Cargo.toml#L22
Is is possible to remove the base import for avoiding compiling all of swc.

We still have these two:
error[E0433]: failed to resolve: could not find `base` in `swc_core`
 --> crates/rspack_plugin_javascript/src/visitors/mod.rs:6:15
  |
6 | use swc_core::base::config::ModuleConfig;
  |               ^^^^ could not find `base` in `swc_core`

error[E0433]: failed to resolve: could not find `base` in `swc_core`
 --> crates/rspack_plugin_javascript/src/visitors/swc_visitor/build_module.rs:3:15
  |
3 | use swc_core::base::config::ModuleConfig;
  |               ^^^^ could not find `base` in `swc_core`

@suxin2017你能看看这个吗
https://github.com/web-infra-dev/rspack/blob/ed6411c6d693ab2e313404f01647fb378bbce0e5/crates/rspack_loader_swc/Cargo.toml#L22
可以删除基本导入以避免编译所有 swc。

@suxin2017 Can you take a look at this,
https://github.com/web-infra-dev/rspack/blob/ed6411c6d693ab2e313404f01647fb378bbce0e5/crates/rspack_loader_swc/Cargo.toml#L22
Is is possible to remove the base import for avoiding compiling all of swc.

This can be tricky, because the swc documentation is so sketchy that it takes a little bit of looking at the code to separate out the logic


error in running demo: Error in jointBilateral

I've completed installing "rcnn-depth" according to help on Ubuntu 16.04.4 (gcc 5.4.0) except the step that I have to run rcnn_build(); witch resulted in error and as suggested in issue #2 I run make in liblinear-1.94 and `liblinear-1.94/matlab' folders.
I've tried with both Matlab R2016b and Matlab R2012b (with editing matlab path in imagestack Makefile and liblinear-1.94/matlab Makefile), both produce this error:
result of Matlab R2012b:
runname =
release
Invalid MEX-file
'/home/hojat/Documents/application/rcnn-depth/eccv14-code/rgbdutils/imagestack/matlab/joint_bilateral_mex.mexa64':
/usr/local/MATLAB/R2012b/bin/glnxa64/../../sys/os/glnxa64/libstdc++.so.6: version ``GLIBCXX_3.4.21' not found (required by
/home/hojat/Documents/application/rcnn-depth/eccv14-code/rgbdutils/imagestack/matlab/joint_bilateral_mex.mexa64)
Error in jointBilateral (line 16)
  aa = joint_bilateral_mex(single(II), single(refII), sigma1, sigma2);
Error in computeNormals>filterItChopOffIS (line 65)
	fFilt = jointBilateral(sp, f, 1, 1000);
Error in computeNormals (line 34)
	AtA = filterItChopOffIS(cat(3, AtARaw, AtbRaw), superpixels, disparity,
        sigmaSupport, sigmaSuperpixel, sigmaDisparity);
Error in wrapperComputeNormals (line 39)
	[N b] = computeNormals(X, Y, Z, disparity, missingMask, superpixels, sigmaSupport,
        sigmaDisparity, sigmaSuperpixel);
Error in yCues (line 11)
  [N, b, pc] = wrapperComputeNormals(double(D)./100, false(size(D)), 3, s, C);
Error in getAllCues (line 12)
    [y1, y2, y3, angl1, angl2] = yCues(D, C, 1);
Error in detectEdge (line 17)
    cues = getAllCues(Iin, Din, C, colorModel, opts.rgbd3opts.vars, cacheFile);
Error in run_all (line 12)
  [E, Es, O] = detectEdge(I, D, [], C, model, sc, [], []);
Error in demo (line 6)
run_all(I, D, RD, C, out_file);
what is GLIBCXX_3.4.21? what is causing this error?

This is probably because the libraries that you used to compiled imagestack with are different from the one that matlab has loaded. You could try specifying LD_PRELOAD path (to point to the system libraries that were used to compile imagestack) while launching matlab to fix this.

hi noob here! Can you explain where I should specify LD_PRELOAD path?
thanks for the quick response!

I used instruction in here and after a clean make of imagestack and liblinear-1.94 and liblinear-1.94/matlab, executed this:
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/libstdc++.so.6" mymatlab_2016b
running demo() leads to the same error as before! :(
Can creating a symbolic link of the system libraries (like here)fix this?

Ok, creating the symbolic link seems to do the trick!
I finally managed to run the demo! YAY!


Add spawning/rearing habitat model(s)

For goal setting and prioritization, identify potential spawning (and perhaps rearing) habitat along streams.
One simple habitat potential model based on attributes already in the streams table:

Species
Gradient (spawning)
Stream Order (spawning)

Chinook
0-3% (<1% optimal)
3-5 (4-5 optimal)

Coho
0-3%
3-5 (4-5 optimal)

Steelhead
0-12% (<5% optimal)
2-5 (3-5 optimal)

Sockeye
0-2%
3-5 (4-5 optimal)

This just requires adding 4-5 new columns (one for a combination of the four species) and applying an UPDATE based on the gradient and stream order.
A better/more refined option is to model potential spawning habitat based on gradient, channel width and potentially channel confinement. Channel width would be modelled based on: upstream watershed area, mean annual precip, stream magnitude, area wetlands upstream etc. Channel confinement modelling TBD.
Potentially even better is to model potential habitat based on gradient and modelled annual discharge for the stream.

Channel width model (for streams where we have no measurement), for the Bulkley watershed group:
map = Mean Annual Precipitation
channel_width =
  1.34962 -
  20.81835*log(stream_magnitude) -
  0.67372*log(upstream_area_ha) -
  0.03514*log(map) +
  1.93418*log(stream_magnitude) * log(upstream_area_ha) +
  3.01788*log(stream_magnitude) * log(map) +
  0.13344*log(upstream_area_ha) * log(map) –
  0.25580*log(stream_magnitude) * log(upstream_area_ha) * log(map)

Channel width model (for streams where we have no measurement), for the Bulkley watershed group:
map = Mean Annual Precipitation
channel_width =
  1.34962 -
  20.81835*log(stream_magnitude) -
  0.67372*log(upstream_area_ha) -
  0.03514*log(map) +
  1.93418*log(stream_magnitude) * log(upstream_area_ha) +
  3.01788*log(stream_magnitude) * log(map) +
  0.13344*log(upstream_area_ha) * log(map) –
  0.25580*log(stream_magnitude) * log(upstream_area_ha) * log(map)

Draft habitat model definition added here.
Sockeye will need some additional logic in the code for rearing habitat but the other spp are straightforward - with the exception that rearing features must be connected to spawning features.
https://github.com/smnorris/bcfishpass/blob/main/02_model/data/spawning_rearing_habitat_model.csv

Draft habitat model definition added here.
Sockeye will need some additional logic in the code for rearing habitat but the other spp are straightforward - with the exception that rearing features must be connected to spawning features.
https://github.com/smnorris/bcfishpass/blob/main/02_model/data/spawning_rearing_habitat_model.csv

habitat model now functional with the exception of criteria that rearing habitat be connected to spawning. Relatively simple to do spatially with the linework but there must be a simple way to do this with the FWA attributes to avoid any spatial processing.

habitat model now functional with the exception of criteria that rearing habitat be connected to spawning. Relatively simple to do spatially with the linework but there must be a simple way to do this with the FWA attributes to avoid any spatial processing.

With draft model functional I'll close this general issue and open more specific issues for bugs/enhancements.

With draft model functional I'll close this general issue and open more specific issues for bugs/enhancements.


Add option to load textures on demand

Adds an option (disabled by default) to load all textures on demand rather than on startup to reduce memory usage.
This does cause a lag spike when spawning in cars, which is why it's toggleable.
If #1 gets merged I'd be happy to re-write this to be compatible as it would suit it very nicely.

Closing because the lag spike is a bit much to deal with in actual gameplay. I've instead made the same PR on mspielberg's fork with async texture loading. (mspielberg/DVCargoSwapMod/pull/1)


Use request.setTimeout() instead of socket.setTimeout()

This reverts 9c3b2e43f387800affa91db64c3a8fd30b4fc824 and replaces socket.setTimeout() with request.setTimeout() to prevent spurious timeouts when using keep-alive sockets.

@floatdrop is this wanted? If not I'll close it.

@floatdrop PTAL, will squash the commits if needed.


Compilation problem

Running a "R CMD build" yields the following problem
nanoflann.cpp:34:   instantiated from here
nanoflannBits.hpp:33: error: no matching function for call to ‘nanoflann::KDTreeSingleIndexAdaptorParams::KDTreeSingleIndexAdaptorParams(const int&, const size_t&)’
./include/nanoflann.hpp:409: note: candidates are: nanoflann::KDTreeSingleIndexAdaptorParams::KDTreeSingleIndexAdaptorParams(size_t)
./include/nanoflann.hpp:408: note:                 nanoflann::KDTreeSingleIndexAdaptorParams::KDTreeSingleIndexAdaptorParams(const nanoflann::KDTreeSingleIndexAdaptorParams&)
Probably due to a change in the how nanoflann works.

Fixed by commit 25e6b119fb


Error: Couldn't find a pages directory.

next start can not run if there is no pages folder present in the root directory. It should be able to run without a pages folder.
How to reproduce

run npx create-next-app@latest

TypeScript: Yes
ESLint: No
Tailwind: No
src directory: Yes
App Router: No
customize import alias: No

Run npm i nextra nextra-theme-docs
Run npm run build
Copy the following directories/files to another directory:

.next
public
next.config.js
package.json
package-lock.json

Run npm install
Run npm start

You should see the following error
> next start

/Documents/throwaways/nextra-pages-dir/node_modules/next/dist/lib/find-pages-dir.js:104
            throw new Error("> Couldn't find a `pages` directory. Please create one under the project root");
                  ^

Error: > Couldn't find a `pages` directory. Please create one under the project root
    at findPagesDir (/Documents/throwaways/nextra-pages-dir/node_modules/next/dist/lib/find-pages-dir.js:104:19)
    at findPagesDirectory (/Documents/throwaways/nextra-pages-dir/node_modules/nextra/dist/index.js:157:15)
    at Object.<anonymous> (/Documents/throwaways/nextra-pages-dir/node_modules/nextra/dist/index.js:161:53)
    at Module._compile (node:internal/modules/cjs/loader:1191:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10)
    at Module.load (node:internal/modules/cjs/loader:1069:32)
    at Function.Module._load (node:internal/modules/cjs/loader:904:12)
    at Module.require (node:internal/modules/cjs/loader:1093:19)
    at require (node:internal/modules/cjs/helpers:108:18)
    at Object.<anonymous> (/Documents/throwaways/nextra-pages-dir/next.config.js:1:20)

When you add an empty pages folder it works again.
I have tried running a regular Next server (so, without Nextra) and it will run without a pages folder.

It should be able to run without a pages folder.

what is the purpose of building your app without pages folder?
Nextra requires pages folder to be present
more info https://github.com/shuding/nextra/discussions/1142#discussioncomment-4552759

Well, when you run "next build" your app is compiled into the ".next" folder. That is what I presume to be the entire app. A regular Next app works with just the ".next" folder after you build it. You can leave out the "pages" folder because that is only necessary for development.
That is not the case with Nextra. I need to add an empty "pages" folder for the production server to run.

If somebody wants to improve it, feel free to contribute

what's renderer folder? provide an example


⚠ Feedaty widget has degraded performance

In 29657bb, Feedaty widget (https://widget.feedaty.com/public/js/feedaty.js?merchant=10213975&style_ver=2021&data-sku=36263) experienced degraded performance:

HTTP code: 200
Response time: 5933 ms

Resolved: Feedaty widget performance has improved in da563f2 after 14 minutes.


ERROR: Layer openamp-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with gatesgarth)

Hi,
I stay trying build yocto dunfell to imx7d-pico based on that:https://hub.mender.io/t/technexion-pico-pi-imx7/136
and I stay with this issue: ERROR: Layer openamp-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with gatesgarth)
Can u help-me ?

@neuberfran
HI
look at the layer
Add hardknott here

Now I have this issue with hardknott too:
ERROR: Layer openamp-layer is not compatible with the core layer which only supports these series: hardknott (layer is compatible with gatesgarth)

@neuberfran
HI
How about add hardknott in this line
https://github.com/OpenAMP/meta-openamp/blob/master/conf/layer.conf#L15
LAYERSERIES_COMPAT_openamp-layer = "gatesgarth hardknott "

@pino-kim No more build errors. As seen in the photo

Now, I need step by step to use this with hardknott (imx7d-pico) kernel 5.10 in A7 and Zephyr or FreeRTOS in A7

@pino-kim No more build errors. As seen in the photo

Now, I need step by step to use this with hardknott (imx7d-pico) kernel 5.10 in A7 and Zephyr or FreeRTOS in M4


ls --json output is invalid in 0.9.4

Output of restic version
restic 0.9.4 compiled with go1.11.4 on windows/amd64
OR
restic 0.9.4 compiled with go1.11.5 on linux/amd64
How did you run restic exactly?
To recreate, create a local repository, then backup any files into that repository, then run:
restic -r . ls latest --json
What backend/server/service did you use to store the repository?
Encountered on local and B2
Expected behavior
Restic outputs valid JSON, e.g. in 0.9.3, this is the output (formatted):
[
  {
    "time": "2019-02-21T16:42:04.1158143+13:00",
    "tree": "008d009b065d3fec5c74ac0d387d580d657fddd905502b8e704beff598564567",
    "paths": [
      "<Backup path>"
    ],
    "hostname": "<Hostname>",
    "username": "<Hostname>\\<Username>",
    "id": "008cfedbe3fc308e836d9dc5d64d8ce8bd44d591e2bb397d8f86880e5694de3a",
    "short_id": "008cfedb",
    "nodes": [
      {
        "name": "deps",
        "type": "dir",
        "path": "/deps",
        "uid": 0,
        "gid": 0,
        "mode":<PHONE_NUMBER>,
        "mtime": "2019-02-12T18:52:27.0460135+13:00",
        "atime": "2019-02-12T18:52:27.0460135+13:00",
        "ctime": "2018-11-12T21:26:46.5094019+13:00",
        "struct_type": "node"
      },
      {
        "name": "BackupScheduler-25c592ce882799aa.d",
        "type": "file",
        "path": "/deps/BackupScheduler-25c592ce882799aa.d",
        "uid": 0,
        "gid": 0,
        "size": 280,
        "mode": 438,
        "mtime": "2018-11-13T12:45:17.6459818+13:00",
        "atime": "2018-11-13T12:45:17.6459818+13:00",
        "ctime": "2018-11-13T12:44:37.4238018+13:00",
        "struct_type": "node"
      },
      {
        "name": "BackupScheduler-25c592ce882799aa.exe",
        "type": "file",
        "path": "/deps/BackupScheduler-25c592ce882799aa.exe",
        "uid": 0,
        "gid": 0,
        "size": 365568,
        "mode": 438,
        "mtime": "2018-11-13T12:45:20.2794522+13:00",
        "atime": "2018-11-13T12:45:20.2794522+13:00",
        "ctime": "2018-11-13T12:44:40.9248534+13:00",
        "struct_type": "node"
      },
      {
        "name": "BackupScheduler-25c592ce882799aa.pdb",
        "type": "file",
        "path": "/deps/BackupScheduler-25c592ce882799aa.pdb",
        "uid": 0,
        "gid": 0,
        "size": 1822720,
        "mode": 438,
        "mtime": "2018-11-13T12:45:20.3063802+13:00",
        "atime": "2018-11-13T12:45:20.3063802+13:00",
        "ctime": "2018-11-13T12:45:20.1388276+13:00",
        "struct_type": "node"
      },
      {
        "name": "BackupScheduler-488195fc288949b0.d",
        "type": "file",
        "path": "/deps/BackupScheduler-488195fc288949b0.d",
        "uid": 0,
        "gid": 0,
        "size": 280,
        "mode": 438,
        "mtime": "2019-02-12T18:52:24.9345818+13:00",
        "atime": "2019-02-12T18:52:24.9345818+13:00",
        "ctime": "2019-02-12T18:52:24.9345818+13:00",
        "struct_type": "node"
      },
      {
        "name": "BackupScheduler-488195fc288949b0.exe",
        "type": "file",
        "path": "/deps/BackupScheduler-488195fc288949b0.exe",
        "uid": 0,
        "gid": 0,
        "size": 3473030,
        "mode": 438,
        "mtime": "2019-02-12T18:52:26.9991369+13:00",
        "atime": "2019-02-12T18:52:26.9991369+13:00",
        "ctime": "2019-02-12T18:52:26.8146312+13:00",
        "struct_type": "node"
      },
      ...
    ],
    "struct_type": "snapshot"
  }
]

Actual behavior
As far as I can tell, it outputs the same information, but some of the structure seems to have been destroyed (i.e. the nodes array seems to have escaped the main JSON object in line 1, and is also no longer an array), resulting in an invalid JSON file:
{"time":"2019-02-21T16:42:04.1158143+13:00","tree":"008d009b065d3fec5c74ac0d387d580d657fddd905502b8e704beff598564567","paths":[<Backup path>"],"hostname":"<Hostname>","username":"<Hostname>\\<Username>","id":"008cfedbe3fc308e836d9dc5d64d8ce8bd44d591e2bb397d8f86880e5694de3a","short_id":"008cfedb","struct_type":"snapshot"}
{"name":"deps","type":"dir","path":"/deps","uid":0,"gid":0,"mode":2147484159,"mtime":"2019-02-12T18:52:27.0460135+13:00","atime":"2019-02-12T18:52:27.0460135+13:00","ctime":"2018-11-12T21:26:46.5094019+13:00","struct_type":"node"}
{"name":"BackupScheduler-25c592ce882799aa.d","type":"file","path":"/deps/BackupScheduler-25c592ce882799aa.d","uid":0,"gid":0,"size":280,"mode":438,"mtime":"2018-11-13T12:45:17.6459818+13:00","atime":"2018-11-13T12:45:17.6459818+13:00","ctime":"2018-11-13T12:44:37.4238018+13:00","struct_type":"node"}
{"name":"BackupScheduler-25c592ce882799aa.exe","type":"file","path":"/deps/BackupScheduler-25c592ce882799aa.exe","uid":0,"gid":0,"size":365568,"mode":438,"mtime":"2018-11-13T12:45:20.2794522+13:00","atime":"2018-11-13T12:45:20.2794522+13:00","ctime":"2018-11-13T12:44:40.9248534+13:00","struct_type":"node"}
{"name":"BackupScheduler-25c592ce882799aa.pdb","type":"file","path":"/deps/BackupScheduler-25c592ce882799aa.pdb","uid":0,"gid":0,"size":1822720,"mode":438,"mtime":"2018-11-13T12:45:20.3063802+13:00","atime":"2018-11-13T12:45:20.3063802+13:00","ctime":"2018-11-13T12:45:20.1388276+13:00","struct_type":"node"}
{"name":"BackupScheduler-488195fc288949b0.d","type":"file","path":"/deps/BackupScheduler-488195fc288949b0.d","uid":0,"gid":0,"size":280,"mode":438,"mtime":"2019-02-12T18:52:24.9345818+13:00","atime":"2019-02-12T18:52:24.9345818+13:00","ctime":"2019-02-12T18:52:24.9345818+13:00","struct_type":"node"}
{"name":"BackupScheduler-488195fc288949b0.exe","type":"file","path":"/deps/BackupScheduler-488195fc288949b0.exe","uid":0,"gid":0,"size":3473030,"mode":438,"mtime":"2019-02-12T18:52:26.9991369+13:00","atime":"2019-02-12T18:52:26.9991369+13:00","ctime":"2019-02-12T18:52:26.8146312+13:00","struct_type":"node"}
{"name":"BackupScheduler-488f4a897c2a05b2.d","type":"file","path":"/deps/BackupScheduler-488f4a897c2a05b2.d","uid":0,"gid":0,"size":280,"mode":438,"mtime":"2018-11-17T12:47:40.375824+13:00","atime":"2018-11-17T12:47:40.375824+13:00","ctime":"2018-11-14T18:08:40.6368122+13:00","struct_type":"node"}
{"name":"BackupScheduler-488f4a897c2a05b2.exe","type":"file","path":"/deps/BackupScheduler-488f4a897c2a05b2.exe","uid":0,"gid":0,"size":382976,"mode":438,"mtime":"2018-11-17T12:47:42.794508+13:00","atime":"2018-11-17T12:47:42.794508+13:00","ctime":"2018-11-14T19:06:21.336183+13:00","struct_type":"node"}
{"name":"BackupScheduler-488f4a897c2a05b2.pdb","type":"file","path":"/deps/BackupScheduler-488f4a897c2a05b2.pdb","uid":0,"gid":0,"size":1830912,"mode":438,"mtime":"2018-11-17T12:47:42.9145998+13:00","atime":"2018-11-17T12:47:42.9145998+13:00","ctime":"2018-11-17T12:47:42.5849329+13:00","struct_type":"node"}
{"name":"BackupScheduler-c515f26fd429a8b4.d","type":"file","path":"/deps/BackupScheduler-c515f26fd429a8b4.d","uid":0,"gid":0,"size":237,"mode":438,"mtime":"2018-11-12T21:27:27.7705817+13:00","atime":"2018-11-12T21:27:27.7705817+13:00","ctime":"2018-11-12T21:27:27.7705817+13:00","struct_type":"node"}
...

Steps to reproduce the behavior
To recreate, create a local repository, then backup any files into that repository, then run:
restic -r . ls latest --json
I originally discovered this with a B2 repository, this bug seems to be platform independent.
Do you have any idea what may have caused this?
Not really, definitely something between 0.93 and 0.94.
Do you have an idea how to solve the issue?
Nope, don't know Go sorry.
Did restic help you or made you happy in any way?
Yep, restic --> B2 is my main backup solution.

This is intentional. The output is not a single object; serializing a single object of arbitrary size runs the risk of memory exhaustion, so instead we print one JSON message at a time. --json backup works the same way with its status updates. (Otherwise you would get no updates until the backup was completed!)

Ah thanks, that's good, though this change probably should be mentioned in the patch notes.

Oh, right, I probably should have added that to the change log, sorry about that.


Recent changes can break with multiple meson.build files

Problem being the list returned by const mesonFiles = await vscode.workspace.findFiles("**/meson.build");; the first entry is taken but the order is ... well, maybe not non-deterministic, but not necessarily workspace root "down" (e.g. Windows).
Wouldn't like to say what the best solution is, but I hacked just to order by path length to check #186 at least superficially worked on Windows: https://github.com/lukester1975/vscode-meson/commit/2d3201297801f6081d35b49ac840b652f3223694
Thanks

cc @wolfpld. Could we change the commit to prioritize the workspace root meson.build if it exists?

Thanks @lukester1975.

NP.
You probably do want some sort of closest-to-workspace-root ordering though, if the idea is to cope with the root meson.build not being in the workspace root?
a/meson.build
a/b/meson.build

Wouldn't want a/b/meson.build (at least, generally, for sane layouts)...

Sorting the initial list of meson files by length sounds like a good solution to the problem at hand.
The idea is to exclude all dependent meson.build files (included with subdir) from the list, but this has not yet been done.

Should be fixed by #188.

My understanding is we only  need to know if it's a Meson project or not. We don't actually need to search for all meson.build files, we could just check if it exists at the root of the workspace?

There is no requirement to keep a single "meson project" meson.build file in the repository. In some cases, such a setup would be too restrictive.


Add contribution guide for adding an adapter to CopilotKit

#545 Guide to adding new service adapter to copilotkit, Ollama, OpenAI, Langchain, Unify, and groq.  Open to discussing changes or working on any other issues. And give the best.

@asif-reh thanks for this, planning to review in a bit.


Fix bug of Dockerfile

Fixed the path.

I think the Dockerfile has fallen out of step. Building a container throws an error:
E: Unable to locate package lib32gcc-5-dev

But I think it might be out of date in other ways? Doesn't this project now use llvm-11. Would say how to fix but I can't even figure out how to compile 🙃


need a refresh context menu item for file list view

VSCode Version:

1.4.0

OS Version:

Debian 8
Steps to Reproduce:
Sometimes, new created files outside vcs doesn't reflect info vcs editor.
I must restart the editor to see the changes.

@yaxinlx can you run "code --verbose" and open the developer tools console (from help menu) and show the output that happens when you create a file outside of VS Code?

@bpasero this case is rare, it only happens for about every several days.
I just run "code --verbose" , and everything is normal. There is no output changes in the developer tools console.

@yaxinlx you should see output for each file change in the console. That is how we can find out if a file event is missing.

@bpasero ok. There are really some outputs on file changes after switching to console tab.
But as I said above, this issue is hard to reproduce.

Ok without steps or diagnostic output this is hard to reproduce.

Closing until reproducible steps are present.


Add a function to close the issues

An added function is to close the imported issues to the target repository with the closed tag, "[CLOSED]"

See also #38.


Create new file for list of names without binary format

This would fix the python3 test error.

i'll wait to see how the build goes


New version: ARCHModels v0.5.1

Registering package: ARCHModels
Repository: https://github.com/s-broda/ARCHModels.jl
Created by: @s-broda
Version: v0.5.1
Commit: 017951d60eaa09971b616900f0693a73611892c0
Reviewed by: @s-broda
Reference: https://github.com/s-broda/ARCHModels.jl/commit/017951d60eaa09971b616900f0693a73611892c0#commitcomment-35526947

Please add compatibility bounds for the next release such that it will be automatically merged.


How to draw Line segments in one Line Chart.

I have a question about how to draw one data set which some data entry has no value, I find this answer on stackoverflow.
But, I find that if we omit the values, the line still is one line, my question here is can I draw line segments instead of one line ? or I need to do it by myself ?

I think out a solution.
I draw multiple data sets, each one have one segment for it.

But this one may have  performance problem if we have too much line segments.

It should have similar performance. In a standard line chart, if you have "segments" then they are different data sets.

@danielgindi can the rules be applied for combined chart? e.g. at a xIndex: 5, it has a bar data, but no line data, and the line should be cut.

Performance of two 50 points datasets shoul be the same as one 100 points
dataset (Add an extra CPU op or two for the for-loops)
So don't worry about it.
Unless you actually encounter or measure a performance problem, do not
worry about it.

How about In a standard line chart, if you have "segments" then they are different data sets. for comebined chart? Can it apply to combined chart?

Why not? :)
בתאריך יום רביעי, 22 ביולי 2015, Xuan<EMAIL_ADDRESS>כתב:

How about In a standard line chart, if you have "segments" then they are
different data sets. for comebined chart? Can it apply to combined chart?
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/235#issuecomment-123574703
.