Adds fine-tune example

resolves #31

Hello @64bit, been having some issues with the string format.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ApiError(ApiError { message: "Expected file to have
JSONL format, where every line is a valid JSON dictionary. Line 1 is not a dictionary
(HINT: line starts with: \"{\"pr...\").", type: "invalid_request_error", param: None, code: None })'

Hi @Doordashcon,
I believe its probably malformed jsonl in code. I'd recommend to separate data from code and put .jsonl file in examples/fine-tune/data so you can read that in code via file_path_train = "./data/train.jsonl".
Putting data out of code is good for many reasons: lets you edit/change data easily, validate the file format, don't need to escape quotes etc.
Hope this helps!

Nice.
For model:  After printing (good UX) fine tuning events until end of stream, retrive the model using fine tune job id using https://docs.rs/async-openai/latest/async_openai/struct.FineTunes.html#method.retrieve

seems like data is not a field in the response stream?
JSONDeserialize(Error("missing field `data`", line: 1, column: 133))
StreamError("request or response body error: error reading a body from connection: stream error received: unexpected internal error encountered")
JSONDeserialize(Error("missing field `data`", line: 1, column: 133))

My current match statement

let fine_tune = CreateFineTuneRequestArgs::default().training_file(training_id).validation_file(validation_id).build().unwrap();

let job = client.fine_tunes().create(fine_tune).await.unwrap();

match client.fine_tunes().list_events_stream(&job.id).await {
    Ok(mut stream) => {
        while let Some(item) = stream.next().await {
            match item {
                Ok(response) => println!("{:?}", response.object),
                Err(error) => println!("-// {:?}", error),
            }
        }
    },
    Err(e) => {
        println!("-/ {:?}", e)
    }
}

Looks like a bug. If you add tracing subscriber you should see the whole payload in logs too (see example/rate-limit-completions for setting up logs).
In generate my observation with OpenAI's streaming APIs is that they usually have a different response format than their non-streaming counterparts - where some of the fields are optional.
To handle that requires two separate struct types for each of streaming and non streaming, similar to chat API (see examples/chat and examples/chat-stream #75).
In this example for ListFineTuneEventsResponse we need ListFineTuneEventsStreamResponse maybe?

Hello @64bit
Created
#[derive(Debug, Deserialize, Clone, PartialEq, Serialize)]
pub struct ListFineTuneEventsStreamResponse {
    pub object: String,
}

which I then replaced here:
pub type FineTuneEventsResponseStream =
    Pin<Box<dyn Stream<Item = Result<ListFineTuneEventsStreamResponse, OpenAIError>> + Send>>;

I tried retrieving but returns None , this might have to do with time factor, regarding how long it takes to fine-tune a model

I think you might need data: Option<FineTuneEvent> too, right?
Does fine tunning on small data set still happen in reasonable time frame, like few minutes?
Does stream block untill all events are available, if not then polling for fine tunning completion is the last resort?

I think you might need data: Option too, right?

returns None
I reduced the n_epoch to 1, maybe a quick look at the recent commit would better clarify things.

It seems like possible path forward is having multiple binaries(cli) for this example each doing specific step:

Submit data for fine tunning, and print ft id
Query ft api for completion using ft id from step (1) may be bin takes cli arg for ft id
Once ft model is ready make use it through this cli with arg taking input

What do you think and recommend?

Hello @64bit
We query OpenAI fine-tune api directly using this cli?
What libraries would you recommend for the request response cycle?
I'm happy to implement

On cases where the ft id produced returns a failure, how would this be handled?

I'm not sure I completely follow your comments.
May be user can retry in case of failures?

Hi @Doordashcon ,
I received your message on Twitter, I'd appreciate if we continue discussion here.
Will you be independently compelting this?  I'm sorry but I'm not available for 1:1 support for this.
You're welcome to indepedently continue and once ready open this PR for review if you'd like me to review and accept contributions. In fact you have made progress and you know more about the subject in this PR, and I do not have futher inputs on this PR.
Thank you for volutanterring and offering contributions on this.

Yes, doesn't seem like much work...should open for review soon enough.
Was thinking of making additional contributions in the form of a tutorial video(specifically for embedding and fine-tune examples), that was the main reason of going through Twitter. My apologies if it was in poor taste.

Hello @64bit, please review

Thank you @Doordashcon . I'll review this in upcoming week.
In the meantime, because this example is unusual than the others - can you add a README for someone new to Rust to be able to run this example without looking at code, please?

Hello @64bit, will add a README
For the additional contributions I suggested, what are your thoughts on it?


add support for hard forks to private ethereum env builder

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

Project coverage is 17.02%. Comparing base (cedf21d) to head (86255ab).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #839   +/-   ##
=======================================
  Coverage   17.02%   17.02%
=======================================
  Files          37       37
  Lines        4435     4435
=======================================
  Hits          755      755
  Misses       3597     3597
  Partials       83       83

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


Win32 and Desktop Bridge app ADMX policy Ingestion - registry locations no longer correct

Hi,
I don't believe the following article is correct: https://docs.microsoft.com/en-us/windows/client-management/mdm/win32-and-centennial-app-policy-configuration
With release of July 26 2022 CU (https://support.microsoft.com/topic/july-26-2022-kb5015878-os-builds-19042-1865-19043-1865-and-19044-1865-preview-549f5551-fcc5-4fee-8811-c5df12e04d40) known Issue rollback (KIR) ADMX can now be ingested and targeted.
KIR ADMX references the following registry path HKLM:\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Override
While the article mentions that ingested policies are not allowed to write to locations within System
Can this article please be updated?
Article on KIR ADMX injection: https://docs.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback#deploy-a-kir-activation-using-microsoft-intune-admx-policy-ingestion-to-the-managed-devices

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

ID: 7f5ed380-12c6-ad56-3f3b-1a0fe190acc9
Version Independent ID: ecdc3e8c-21e4-0a4c-6208-67905a4e57d4
Content: Win32 and Desktop Bridge app ADMX policy Ingestion - Windows Client Management
Content Source: windows/client-management/mdm/win32-and-centennial-app-policy-configuration.md
Product: w10
Technology: windows
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


⚠ Bofrost.at has degraded performance

In deb5731, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1467 ms

Resolved: Bofrost.at performance has improved in 3c9d6af.


Use the latest manageiq-api-common gem

Removed all the RBAC code since now they are in common gem
Changed specs to get error message from array of errors
Modified the Gemfile to use the common gem from github till
they update the rubygems

@syncrou If the lib/rbac/tools can be deleted the code climate issues will be resolved. Since the tools directory files are only used by rake tasks to help in seeding.


:star: except GEOS exception when adding contour

@SanderHulst thank you for your suggested modifications. If you have the time please see if the suggested changes make sense. In any case it would be great if you could reproduce the issue using a handwritten raster with a few tens of cells (there's a raster creation function you can use):
https://github.com/noaa-ocs-modeling/OCSMesh/blob/6d472482019634b870cacdb428622b9b49e4bfdc/ocsmesh/utils.py#L2132-L2137
This should make sure issues like this are resolved and always checked for.

@SorooshMani-NOAA
I tried to add a regression test but the test bed won't work on my setup. I tries to download and install .tif files in places where it may not write.
May I ask you to run the tests as is, with the commented test on the number of vertices, and run it again with the check?

May I ask you to run the tests as is, with the commented test on the number of vertices, and run it again with the check?

Sure, thank you, I'll try it.

@SanderHulst, the test raster array dimensions don't match with what you're trying to set. Based on your description, I think the issue you're running into for locally testing, is due to the code in tests/api/__init__. You can comment that code on your local machine and the run:
python tests/api/hfun.py SizeFunctionCollector.test_add_contour_single_vertex

from your repo root directory. This should only run the new test you're adding. I think it's easier if you could complete the test on your machine, because (after removing typos) when I tried it it doesn't fail (Since you commented the check you added, I'm expecting the test to be something that should fail before you uncomment) and I'm not sure how/why it's supposed to fail.

Hi @SorooshMani-NOAA ,
Life got easier after commenting the code in init. The test now results in a one point contour line.

Just for the sake of documentation:
If I uncomment the check:
if len(path.vertices) < 2:
    continue

I still don't get a failed test. The contour from path.vertices is [[-1.  -0.7] [-1.  -0.7]] for me for the test_add_contour_single_vertex test.
I'm using matplotlib 3.7.1 and noticed @SanderHulst has 3.5.1. I switched to 3.5.1 and now I see the error! So I think moving forward maybe the test wouldn't be doing anything (due to updated matplotlib), but it's useful to have it for now.
Still the fact that the test becomes irrelevant has nothing to do with the actual check for number of vertices which catches the error and is needed.


fix: release.yml workflow failing because the cli is not found

Attempt to fix the release.yml workflow that failed:
https://github.com/accesimpot/graphql-lookahead/actions/runs/10387100789/job/28759843259

What

Enforce installing devDependencies with --prod=false in ci.yml and release.yml workflows

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

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Sign

For use with potentially several Places presets in superclass=information; class=sign:

Directional Sign
Gateway Sign
Mile Marker
Regulatory Sign
Trail Marker
Trail Sign

There no existing HFC symbol for a generic sign, but it would be a very useful catch-all for us to use with POI's. Here's my idea:

@jakecoolidge: What do you think of this?

Looks good to me! You'll probably have to modify or remove the linework inside the sign at smaller sizes, but I like the direction.

After more discussion, we've settled on a simpler design that's more NPS-ish:

Standalone symbol designs:

32
24
16


The training results on the self-built dataset are zero.

@Jingkang50 ，Hi, according to the work you have done, I have created a small dataset specifically for railway scenarios. It only includes two classes of objects: pedestrians and railways. It also includes two types of relationships: "on" and "beside." After training for 100 epochs multiple times, I noticed that the results are consistently zero. I obtained this result when using the predict file to infer an image. As you can see, the PSGTR model I trained predicted the entire image as "person."Can you give me some advice?

+1


Please help add --form dialog

As title.
Please help add --form dialog. Thank you very much.

--form means multiple input entries.
Thank you again.

I was once trying to work on it but adding forms is quite complicated and right now I'm working on other projects, so I can't promice anything.


lazyloading - prev and next on initialization

Being able to preload the next slide on initialization. Currently it will only load the first slide; then subsequent slides on click of prev/next.
Ideally you would want the option to load the next (and or prev) slides on initialization also.
Awesome job btw, really nice library.

Thanks. There will no be slides lazy loading feature, but there is in plans to realise something like virtual slides to keep DOM small. Related to #1154

Sorry I think you misunderstood. I meant lazyloading of the slide images. This functionality already exists. However it doesn't preload the next/prev images on swiper initalization. Only when you click prev/next nav buttons.

Oh, you mean this. Then you need to also enable lazyLoadingInPrevNext - as docs states:

Set to "true" to enable lazy loading for the closest slides images (for previous and next slide images)


asImageWidthSrcSet does not accept ImageField

asImageWidthSrcSet expects an ImageFieldImage, but in the docs it appears to be accepting an ImageField.
Reproduction
import { asImageWidthSrcSet } from "@prismicio/helpers"
import * as prismicT from "@prismicio/types"

const image = {} as prismicT.ImageField
asImageWidthSrcSet(image) // Argument of type 'ImageField<never, FieldState>' is not assignable to parameter of type 'EmptyImageFieldImage | FilledImageFieldImage'.

Hey there, thank you so much for the report again!
We're facing some TypeScript limitations with this type indeed... We'll attempt at fixing it without introducing further regression again!

Fixed in 0.1.27 🎉
Updating @prismicio/types should fix the issue, let us know if you still encounter issues 🙏


Missing redis cache related information on dns

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @mblanco77
Microsoft Alias: allensu

Thanks for leveraging Azure docs feedback channel to raise this question. Could you please share the information you are looking for ?

Hello VIjay,
this table in that article is missing information about redis cache
[image: image.png]
when i created a private endpoint for redis in my tenant, it is showing
custom dns setting suffixed as
redis.cache.windows.net
instead of
privatelink.redis.cache.windows.net
which makes me depend on this documentation on if that is correct or could
be a mistake since this feature is in preview mode.
On Sat, Oct 24, 2020 at 7:48 AM Svijay-msft<EMAIL_ADDRESS>wrote:

Thanks for leveraging Azure docs feedback channel to raise this question.
Could you please share the information you are looking for ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/64956#issuecomment-715910229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPMMID6MMQNE5ILL2RLUE3SMLELBANCNFSM4S5IC57Q
.

--
Ganesh Phani Majeti.

@mganeshphani , thank you for your feedback.
Azure Cache for Redis with Azure Private Link went Public Preview on 22 September, 2020.
All information is available in the below article:
https://docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-private-link
The Redis cache instance's host name will be .redis.cache.windows.net.

This information will be updated in the DNS article soon.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Feature/#49 add unit tests for x unit generator

close #49 issue

Codecov Report

Merging #55 (076dd4b) into main (eb90784) will decrease coverage by 0.61%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
- Coverage   90.74%   90.14%   -0.61%
==========================================
  Files          21       20       -1
  Lines         227      213      -14
  Branches       37       37
==========================================
- Hits          206      192      -14
  Misses          9        9
  Partials       12       12

Impacted Files
Coverage Δ

...Extensions/Generators/SignatureWrapperGenerator.cs
100.00% <ø> (ø)

.../Analyzers/TheoryAttributeOverJsonDataAttribute.cs
94.73% <100.00%> (ø)

...ers/TheoryAttributeOverJsonDataAttributeCodeFix.cs
92.59% <100.00%> (ø)

...sExtensions/Analyzers/TextExtensionsDescriptors.cs

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


run_model_bpa Running Forever and Not Completing for Certain Datasets

Tried multiple times, this particular dataset never gets completed.
Tried with both function run_model_bpa and run_model_bpa_bulk
published dadatset to diffrent workspace, same result
Dataset is very simple
I tried 7-8 times on different days same result.
It doesn't throw any error, just keeps running.
Same function in the same connection instance running fine.
I can download dataset, it looks fine. I published it to different workspace with different name, but same issue.
Model Size: 113 MB
It is happening with many datasets. Like 2 out of 10 datasets.

Also, one more unusual error after lates version of release as below.  multiple repeat at position 42

For the 'multiple repeat at position 42' error, run this model against the run_model_bpa function and provide the full error message.
For the unending issue - do you have some sort of circular dependency in your DAX? For example, Measure A depends on Measure B and Measure B depends on Measure A.

For the 42 error, I will likely need to see the .bim file as this error message is not proving useful.
Regarding the dependencies issue, does the labs.get_measure_dependencies() function work for that semantic model?

labs.get_measure_dependencies() function works fine

As it is getting stuck, and I am not able to use it in an automation. Could you please introduce a timeout optional parameter so I can pass it like 300 seconds or 6000 seconds for workspace to timeout for now. So it will jump to next workspace if it or getting stuck at any workspace or dataset.
i am trying externally to terminate it with some timeout but function is blocking, and timeout termination is not getting executed.

Do you have an issue when running model calc dependencies when using semantic link labs version 0.8.3?
I don’t plan to put a timeout. I plan to solve the root cause. To do that, I need to figure out what about this model is causing the model calc dependencies function to go on an infinite loop.

I need some more time to get the exact case when it stuck. I will update here.

Just an update a dataset was running for forever for below function in 8.3. Now that dataset is working fine in 8.8
get_model_calc_dependencies
run_model_bpa
But still some dataset getting stuck in 8.8 and some throwing error like below
Process Process-1:
Traceback (most recent call last):
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/tmp/ipykernel_11250/911325610.py", line 80, in run_bpa_for_workspace
labs.run_model_bpa(dataset=Dataset_Name, workspace=Workspace_Name, export=True)
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/site-packages/sempy/_utils/_log.py", line 348, in log_decorator_wrapper
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/site-packages/sempy_labs/_model_bpa.py", line 314, in run_model_bpa
x = [nm(obj) for obj in tom.model.Tables if expr(obj, tom)]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/site-packages/sempy_labs/_model_bpa.py", line 314, in
x = [nm(obj) for obj in tom.model.Tables if expr(obj, tom)]
^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/site-packages/sempy_labs/_model_bpa_rules.py", line 416, in
lambda obj, tom: any(
^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/site-packages/sempy_labs/_model_bpa_rules.py", line 417, in
re.search(
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/init.py", line 176, in search
return _compile(pattern, flags).search(string)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/init.py", line 294, in _compile
p = _compiler.compile(pattern, flags)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/_compiler.py", line 745, in compile
p = _parser.parse(p, flags)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/_parser.py", line 989, in parse
p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/_parser.py", line 464, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/trusted-service-user/cluster-env/clonedenv/lib/python3.11/re/_parser.py", line 694, in _parse
raise source.error("multiple repeat",
re.error: multiple repeat at position 42

This is fixed in 0.8.8


Feat: set current part as next

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature

What is the current behavior? (You can also link to an open issue here)

Sofie does not allowing setting the current part as next.

What is the new behavior (if this is a feature change)?

This removes that limitation as the backend can now handle is appropriately

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #375 (eace7dd) into master (c86bd91) will increase coverage by 0.19%.
The diff coverage is 64.49%.

@@            Coverage Diff             @@
##           master     #375      +/-   ##
==========================================
+ Coverage   66.79%   66.99%   +0.19%
==========================================
  Files         192      192
  Lines       12951    13041      +90
  Branches     3045     2920     -125
==========================================
+ Hits         8651     8737      +86
- Misses       4229     4231       +2
- Partials       71       73       +2

Impacted Files
Coverage Δ

meteor/lib/collections/PeripheralDevices.ts
47.36% <ø> (ø)

meteor/lib/collections/Timeline.ts
40.90% <ø> (ø)

meteor/server/api/asRunLog.ts
68.04% <ø> (ø)

meteor/server/api/playout/adlib.ts
44.12% <ø> (ø)

meteor/server/api/playout/lib.ts
78.76% <ø> (ø)

meteor/server/api/playout/pieces.ts
16.89% <0.00%> (ø)

meteor/server/api/playout/lookahead.ts
8.73% <9.30%> (+0.04%)
:arrow_up:

meteor/lib/rundown/infinites.ts
63.41% <50.00%> (-0.09%)
:arrow_down:

meteor/server/api/playout/take.ts
62.33% <50.00%> (-0.41%)
:arrow_down:

meteor/server/api/playout/timeline.ts
73.91% <50.00%> (+0.21%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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


Connect (m,n,k) game + a few minor changes

Hi Paul !
I hope things go well for you.
Being in the doubt ( either 1) you are busy with other stuff and that's fine or 2) you are expecting me to rework my branch) I have reworked my branch "LucasBorboleta" in the form of a new branch "LucasBorboleta2" by taking into account (I hope so) your feedback from my former branch.
Lucas

Hi Lucas, sorry for the delay in getting to these, I've been super busy the past couple of months I'm afraid. Thanks for sticking with this, I'll get to reviewing this once life is slightly less crazy.

Hi Paul !
Good to hear you. I hope that the important things in life are going right for you.
Don’t mind for my pull request ; it is hobby.
Cheers,
Lucas
De : Paul Sinclair @.>
Envoyé : mercredi 17 mars 2021 21:24
À : pbsinclair42/MCTS @.>
Cc : Lucas Borboleta @.>; Author @.>
Objet : Re: [pbsinclair42/MCTS] Connect (m,n,k) game + a few minor changes (#16)
Hi Lucas, sorry for the delay in getting to these, I've been super busy the past couple of months I'm afraid. Thanks for sticking with this, I'll get to reviewing this once life is slightly less crazy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/pbsinclair42/MCTS/pull/16#issuecomment-801418315 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AFHTG5QE6UEVN4BPA4PYZTDTEEFWBANCNFSM4YAZCK5Q .  https://github.com/notifications/beacon/AFHTG5XDNEKFYGGQSXCOYPTTEEFWBA5CNFSM4YAZCK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF7CKYSY.gif

Hey :) Just wanted to check in and see if you have plans to merge these changes? Briefly looking them over they seem very reasonable 👍

Konstantin,
I am happy that you appreciate my contribution. The intent was to provide a simple, but complete, example of a usage of Paul's MCTS library, which sounds good for discovering the Monte Carlo Tree Search approach.
Unfortunaltey, Paul seems to be busy with other stuff in his life.
Cheers, Lucas

@LucasBorboleta since this repo seems to be inactive I decided to fork it and keep working there. I did add this PR as a patch to my code base. I am using this package in another project so it will be nice if it follows conventions...
I plan on making a couple of changes like renaming the function / classes so that they follow the Python Naming Convention, structuring the codebase to multiple packages and add abstract classes  for State and Action so that they can be extended more easily by users of the package and also ad a CI/CD pipeline (GitHub Actions).

I did get started on my endeavour in this repo and published v2.0.0 pypi package in case anyone is interested :)

Konstantin,
Good to know that you are making this MCTS projet alive. Applying common Python naming convention might also help.
In a way of you choice, could you mention, my name "Lucas Borboleta" as associated to the  example "Connect(m,n,k)"  ? Well, unless it appears automatically from Git historical mechanims. Thanks.

Sure :) I added a patch of this PR to the repo so your account is linked with the corresponding commit, but I will mention you in the readme as well next the example :)

All right !


fix(@angular-devkit/build-angular): remove deprecated i18nLocale and i18nFormat options

BREAKING CHANGE: Removal of deprecated extract-i18n command options
The deprecated i18nLocale option has been removed and the i18n.sourceLocale within a project's configuration should be used instead.
The deprecated i18nFormat option has been removed and the format option should be used instead.

@clydin please fix the conflict.


Add/agent specific knowledge

testing

Disclaimer: This review was made by a crew of AI Agents.
Code Review Comment for PR #1672 - Added Knowledge to Agent Level
Overview
This pull request fundamentally enhances the agent-level knowledge management system. It introduces capabilities for agents to maintain their own knowledge bases independent of the crew's knowledge, effectively decentralizing informational resources.
Key Findings

Knowledge Configuration Simplification

Issue: The initial dictionary configuration for knowledge sources was unnecessarily complex.
Improvement: Transitioning to a direct list configuration streamlines the process and enhances clarity.

Change:knowledge_sources=[string_source]

This change improves readability and aligns more closely with typical configuration patterns.

Error Handling Improvements

Issue: The original code lacked robust error handling, particularly in the context of embedding operations.
Improvement: Introducing specific error handling enhances the robustness of knowledge operations, significantly reducing potential runtime errors.

Change:except chromadb.errors.InvalidDimensionException as e:
    # Logging and raising ValueError with detailed message

Ensuring that users receive clear feedback when errors occur is crucial for debugging.

Code Deduplication through Utility Functions

Issue: The context extraction logic was duplicated across multiple locations.
Improvement: Centralizing this logic into a utility function improves maintainability and reduces future code repetition.

Change:def extract_knowledge_context(knowledge_snippets: List[Dict[str, Any]]) -> str:
    ...

Utility functions not only reduce duplicated code but also enhance clarity by encapsulating common logic.

Separation of Concerns in Agent Implementation

Issue: The agent class's knowledge initialization was overly complex and mixed multiple concerns.
Improvement: Simplifying the initialization process allows for clearer responsibility segregation within the class.

Change:def _set_knowledge(self):
    ...

This change encourages cleaner and more testable code structures.

Historical Context and Related Insights
While this PR stands as a significant enhancement to the agent's knowledge framework, it is important to recognize that previous PRs have set the groundwork for this structure. PRs focusing on general error handling, configuration management, and knowledge query optimizations have shaped a more comprehensive and robust knowledge management system.
Suggested Enhancements

Input Validation: Implement a validation function for embedding configurations to enforce required fields and configurations.
Performance Improvements: Consider caching frequently accessed knowledge to enhance performance, especially as the knowledge base grows.
Logging for Knowledge Operations: Introduce a more detailed logging mechanism around knowledge additions and removals to improve traceability.

Conclusion
This PR positively contributes to a well-structured agent-level knowledge management system, enhancing maintainability, robustness, and user experience. The proposed recommendations aim to further strengthen the codebase, ensuring it sustains further growth and adaptability.
Thank you for your hard work on enhancing our knowledge management capabilities! I look forward to seeing these changes integrated.


[SoundcloudBridge] Improves Author, Date, Description

Author Name now doesn't include Episode Title
It now fetches Episode Creation Timestamp, to allow correct sorting in podcatchers
Description is now the actual show notes, and not an <audio> tag

Not implemented yet: fetch enclosure length, fetch enclosure mimetype, fetch artwork

It's not clear to me why the test fails.

Thanks for the PR!

It's not clear to me why the test fails.

This is not your fault. Travis changed some internal specifics that currently break our checks:

https://changelog.travis-ci.com/deprecation-container-based-linux-build-environment-82037
https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration

I'm working on a solution...

Master is fixed, please rebase.

I am seeing "This branch has no conflicts with the base branch" on my side, do I still have to rebase?
I was working from GitHub's web editor so far so I don't see how I can do a rebase.

Ah I see, then I'll merge and fix if anything breaks. Looks good to me anyway :+1:

Merged.

Cheers. I'll see how else I can improve this bridge soon.


Auto Re-login?

Anyway to do an automatic relogin once google times you out after 30mins? Cuz otherwise the map is hard to use if you can only go outside for 30mins with it, have to go back home and login/out and toogle mobile hosting again.

It probably would be way faster to make a trainer club account for this than to wait for update.

even with the PTC Account it logs out

I am running 0.1.0 and it has been running for about 6 hours now on PTC account. Are you using the new version  ?

yes i do - do you an account that you only use for the map? mine is also botting in this area i am scanning ^^

It is a throwaway account for live map client.

ok - i use a "maponly" account now too .. hope it helps, thx

Well.. if only I can signin for PTC account..

works now for me with my extra account, thx

The problem is registering PTC accounts is blocked since days due to "maintenance".

The site comes back up once a while. I was able to make a few for the past two days during different time. Check often


Please add an explanation that defines External Access options more thoroughly

What is the difference between 'External Access' and 'Users can communicate with external Skype for Business Users'?
Also, it appears that this screen shot and its explanation needs to be updated. My admin portal now says 'Users can communicate with Skype for Business Users and Teams users'; it no longer offers 'External Users'

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

ID: 31588a25-f3ee-e888-aa67-203be3d34489
Version Independent ID: 3b498bcf-69a9-01ac-973a-4d5dbeea587c
Content: Manage external access (federation) in Microsoft Teams
Content Source: Teams/manage-external-access.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@officedocsbot assign @scanum

Hello @LisaJo48
Thanks for your feedback! I created a PR to improve the article based on your comments.
Thank you

@LisaJo48  Thank you for submitting this feedback.
From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.

@officedocsbot close


Refactor Project

The idea is refactor the project and the api to include better solutions and create a open source project to help people create a complete and easy e-commerce.
The e-commerce project it will be changed to:

[X] Monorepo
[X] Design System
[X] Storybook
[ ] React with hooks
[ ] Redux Hooks
[ ] Redux-Saga
[ ] Unit/Integration Tests

The Api will be changed to:

Elixir
Phoenix

Future Features

[ ] Home (List products)
[ ] Detail products
[ ] Recommended products
[ ] Cart
[ ] Checkout
[ ] Login / Register
[ ] Admin (Seller)
[ ] Profile (Buyer)
[ ] Contact Us
[ ] Message between Seller and Buyer
[ ] Ratings about the Seller
[ ] Dashboard for Sellers
[ ] Notifications
[ ] Favorites
[ ] Pwa
[ ] Firebase or storage
[ ] Socket.io
[ ] App
[ ] SSR

Using reselector for redux would be a great addition. I think that on some cases, we will need to save a lot of info at the store or make complex calculations, etc.

Using reslect for redux would be a great addition. I think that on some cases, we will need to save a lot of info at the store or make complex calculations, etc.

Yes, I agree. Is very simple for create a selector for cart functions using reselect

What about Context instead of Redux? Would save you from having to use Redux.

What about Context instead of Redux? Would save you from having to use Redux.

Only context is very bad, because don't have a largest perfomance, but using Context + Hooks, is a good thing, because is very similar to redux implementation. I have a example here: https://github.com/viniarruda/spotify-project
My idea is use redux with hooks, and redux-saga to test the idea in a "largest" project, focusing in perfomance and tests, but we can use Context + hooks in native app, is a good idea too.

What about Context instead of Redux? Would save you from having to use Redux.

Only context is very bad, because don't have a largest performance, but using Context + Hooks, is a good thing, because is very similar to redux implementation. I have a example here: https://github.com/viniarruda/spotify-project
My idea is use redux with hooks, and redux-saga to test the idea in a "largest" project, focusing in perfomance and tests, but we can use Context + hooks in native app, is a good idea too.

I had some previous problems with the scalability of context with ReactNative. It seems that the slight lower performance of context API really shows up in low spec mobile devices.
Maybe context works well with simple applications with low traffic in the global state, at least that's what I got from my previous experiences.

What about Context instead of Redux? Would save you from having to use Redux.

Only context is very bad, because don't have a largest performance, but using Context + Hooks, is a good thing, because is very similar to redux implementation. I have a example here: https://github.com/viniarruda/spotify-project
My idea is use redux with hooks, and redux-saga to test the idea in a "largest" project, focusing in perfomance and tests, but we can use Context + hooks in native app, is a good idea too.

I had some previous problems with the scalability of context with ReactNative. It seems that the slight lower performance of context API really shows up in low spec mobile devices.
Maybe context works well with simple applications with low traffic in the global state, at least that's what I got from my previous experiences.

Hmm... how is a application for much users, I think the better option is use redux, but we can use context + hooks to test in web package. Don't have problem to change after too, is a open source project to test and feel free to open pr's after.
The idea is create a lot of components for design system first, after designer complet the design system. We have time to think before start the project.


SigningStargateClient.connectWithSigner endpoint Error

const network = {   url: 'http://localhost:8080/rest',   headers: {     'Content-Type': 'application/json'   } } const chainId = 'osmosis-1' const offlineSigner = window.keplr.getOfflineSignerOnlyAmino(chainId); const client = await SigningStargateClient.connectWithSigner(   network,   offlineSigner, );
Error：
"TypeError: url.startsWith is not a function"  at Function.connectWithSigner (signingstargateclient.js?172a:66:1)
Version 0.28.3 source code：
public static async connectWithSigner(     endpoint: string | HttpEndpoint,     signer: OfflineSigner,     options: SigningStargateClientOptions = {},   ): Promise<SigningStargateClient> {     const tmClient = await Tendermint34Client.connect(endpoint);     return new SigningStargateClient(tmClient, signer, options);   }
builded code signingstargateclient.d.ts：
static connectWithSigner(endpoint: string, signer: OfflineSigner, options?: SigningStargateClientOptions): Promise<SigningStargateClient>;
Why is there no HttpEndpoint？

This change is unreleased. If you need it, you should consider to build it by yourself instead of waiting for a release. The 0.28.3 version of this code is:
  public static async connectWithSigner(
    endpoint: string,
    signer: OfflineSigner,
    options: SigningStargateClientOptions = {},
  ): Promise<SigningStargateClient> {
    const tmClient = await Tendermint34Client.connect(endpoint);
    return new SigningStargateClient(tmClient, signer, options);
  }

(https://github.com/cosmos/cosmjs/blob/v0.28.3/packages/stargate/src/signingstargateclient.ts)
Got commited yesterday: https://github.com/cosmos/cosmjs/commit/7d62e8fc0d1c79e2ff5268d77584153256d4f769
Also in changelog "unreleased": https://github.com/cosmos/cosmjs/blob/main/CHANGELOG.md

If I use it like this, I get a cross domain error
`const network = 'https://lcd-osmosis.keplr.app';
const chainId = 'osmosis-1'
const offlineSigner = window.keplr.getOfflineSignerOnlyAmino(this.chainId);
const client = await SigningStargateClient.connectWithSigner(
network,
offlineSigner,
);
`
Access to fetch at 'https://lcd-osmosis.keplr.app/' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

If I set the proxy, an error will be reported：
 proxy: {       // 配置跨域       '/rest': {         target: 'https://lcd-cosmoshub.keplr.app',//后端接口地址         ws: true,         changOrigin: true,         pathRewrite: {           '^/rest': ''         }       }     }
asyncToGenerator.js?1da1:6 Uncaught (in promise) Error: Bad status on response: 404

This change is unreleased. If you need it, you should consider to build it by yourself instead of waiting for a release. The 0.28.3 version of this code is:
  public static async connectWithSigner(
    endpoint: string,
    signer: OfflineSigner,
    options: SigningStargateClientOptions = {},
  ): Promise<SigningStargateClient> {
    const tmClient = await Tendermint34Client.connect(endpoint);
    return new SigningStargateClient(tmClient, signer, options);
  }

(_https://github.com/cosmos/cosmjs/blob/v0.28.3/packages/stargate/src/signingstargateclient.ts_)
Got commited yesterday: 7d62e8f Also in changelog "unreleased": https://github.com/cosmos/cosmjs/blob/main/CHANGELOG.md

build error：https://github.com/cosmos/cosmjs/issues/1117

Yes I understand the problem too, that's why you can also use the change from https://github.com/cosmos/cosmjs/issues/1117 once the next release is released.
Regarding your build issues - can you list ALL the steps you take?

npm run build
➤ YN0000: [@cosmjs/utils]:     at Function.moduleExports.runMain (/Users/weizhao/zw/projects/bigData/cosmos/cosmjs/.pnp.cjs:23600:31)
➤ YN0000: [@cosmjs/utils]:     at internal/main/run_main_module.js:17:47
➤ YN0000: [@cosmjs/utils]: Process exited (exit code 1), completed in 4s 255ms
➤ YN0000: The command failed for workspaces that are depended upon by other workspaces; can't satisfy the dependency graph
➤ YN0000: Failed with errors in 16s 636ms

是的，我也理解这个问题，这就是为什么你也可以在下一个版本发布后使用7d62e8f的更改。
关于您的问题 - 您可以提出您的所有步骤吗？

When will the version be released?

Yes I understand the problem too, that's why you can also use the change from 7d62e8f once the next release is released.
Regarding your build issues - can you list ALL the steps you take?

When will the version be released?

If I set the proxy, an error will be reported： proxy: { // 配置跨域 '/rest': { target: 'https://lcd-cosmoshub.keplr.app',//后端接口地址 ws: true, changOrigin: true, pathRewrite: { '^/rest': '' } } } asyncToGenerator.js?1da1:6 Uncaught (in promise) Error: Bad status on response: 404

This is intended for everyone, there should be no cross-domain issues, hopefully this will be resolved

``

@zwht You can simple fix the building problem by:

Install yarn
cd your/path/cosmjs
rm -R node_modules/
yarn
yarn build

Hi @zwht, the same error occurred for me, can you help me solve ?

To sum this issue up (and keep it closed):

If you have building issues, re-clone the project and use yarn instead of npm. npm isn't supporting the workspaces like we set it up here. (at least I don't know how)
In the initial issue the author described how he wanted to connect to a LCD/"Rest"-Server. This isn't supported by CosmJS. You always have to connect to a RPC Host.

If you have any further issues please keep this one closed and consider to open a new one.


Work responsibly

In the Readme.md file, the section heading "Work responsible" should probably be "Work responsibly".
Background: "responsible" is an adjective modifying a noun (analogous to "happy", but then it should precede and not follow the noun), "responsibly" is an adverb modifying a verb (analogous to "happily"), which seems to be intended here.

Thank you for the feedback, i will change it!


Migrate to AndroidX and updates to build.gradle

Updates the Kotlin Gradle Plugin, the Gradle Build Plugin, and the compileSdkVersion

@nsamala , Could you please update example folder to AndroidX
Thank you very much.

Thanks for your contribution but this issue is now resolved in version 0.1.0 released yesterday. Closing issue.


Hybrid W2V pad token is hardcoded

The pad token for the wav2vec hybrid segmentation method is hardcoded to the token "<pad>".
https://github.com/mt-upc/SHAS/blob/a64a70f8571f7b154dadf205203a04d151448d5b/src/segmentation_methods/utils.py#L333
This causes problems if we load a model that used a different pad token. For example, PereLluis13/Wav2Vec2-Large-XLSR-53-catalan uses "<PAD>" instead. In this case, then the prediction will always be "0".
This can be fixed in 1 line by doing the comparison against processor.tokenizer.pad_token.
Before the fix:
[{duration: 10.06, offset: 0.0, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
  {duration: 10.06, offset: 9.94, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
  {duration: 10.06, offset: 19.94, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
...

After the fix:
[{duration: 2.82, offset: 0.0, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
  {duration: 9.74, offset: 3.5, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
  {duration: 2.44, offset: 13.76, rW: 0, speaker_id: NA, uW: 0, wav: Debate24_726.13_2273.72.wav},
...

Fixed in #3

Hi Javier, true, thanks for pointing this out :)


LaTeX rendering is broken

It seems like most all of the LaTeX math rendering for these pages is broken, see on this page \ket in the first line.

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

ID: 139b4939-525f-d0b4-40e4-c912f5fcff48
Version Independent ID: b00ec85c-4a1f-9706-3ea6-921e4f463d6c
Content: R1 operation (Microsoft.Quantum.Intrinsic) - Q# reference - Microsoft Quantum
Content Source: api/qsharp/microsoft.quantum.intrinsic.r1.yml
Product: quantum
GitHub Login: @anpaz-msft

bra-ket notation renders on this page but not on the page cited in this issue.
Looking at the source, there is MathJax.Hub.Config that includes definitions of TeX macros for ket/bra/braket/etc. Maybe the mathjax braket extension should be loaded instead?


docs: Addressing Typos in Architecture and Metrics Sections

This pull request focuses on enhancing the documentation by correcting typographical and grammatical errors found in key sections.
Summary of Updates
1. architecture.mdx

Improved the explanation of vote extension requirements by removing redundancy.

Previous: "comprise the required minimum stake required for a price update."
Revised: "comprise the minimum stake required for a price update."

2. application-reference.mdx

Resolved a grammatical issue in the oracle_response_latency description.

Previous: "time in nanoseconds between request/response of from the Application to Oracle."
Revised: "time in nanoseconds between request/response from the Application to Oracle."

we're winding down maintenance of Connect right now so we won't be merging this - apologies!


NTR: tRNA folding

I just read a new paper, PMID 27849601, that shows tRNA chaperone activity for an E. coli enzyme, TruB.  Given the clear importance of proper tRNA folding, I think it would be useful to have a GO term for it.  Proposed parent: GO:0034337.  Proposed definition: The process of assisting in the folding of tRNAs into the correct tertiary structure.
Thanks,
Ingrid

[Term]
+id: GO:0061818
+name: tRNA folding
+namespace: biological_process
+def: "The process of assisting in the folding of tRNAs into the correct tertiary structure." [GOC:dph, PMID:27849601]
+is_a: GO:0034337 ! RNA folding
+intersection_of: GO:0034337 ! RNA folding
+intersection_of: has_input CHEBI:17843 ! transfer RNA
+created_by: dph
+creation_date: 2016-12-13T15:54:40Z


Add pixi support

I would like to add a pixi project file to enable an easy way to install and run simulations in comodo in a way that is:

reproducible across different machines
easy to use
that allows to only install the simulator one wants to use (mujoco, drake, JaxSim)

Blocked by:

#20
https://github.com/ami-iit/jaxsim/pull/260

How to use pixi in comodo
The pixi.toml file, also called project manifest, is where we specify all the project configurations, environments along with their dependencies.
In this case, I've created a default environment containing all the dependencies Comodo needs (taken from its README). Then I specified an environment for each simulator supported today on comodo: mujoco, JaxSim and Drake (in future we can add all the other simulators comodo will support in an extensible way).
These environment have the name of the simulator (i.e. they are called mujoco, jaxsim, drake), and there is also an all environment that include all of them. These environments build upon the default one and add just the dependencies they need to work properly.
The it is possible to activate one of the environments with:
pixi shell -e <environment-name>

just like one will activate a conda environment.
It is also possible to run directly a command in one of these environment using:
pixi run -e <environment-name> python <script-filename.py>

or
pixi run -e <environment-name> jupyter notebook

and then run the jupyter notebooks in the examples folder.
Visual Studio Code
For the folks using vscode, remember to select the appropriate pixi environment when developing and running python scripts by:

Clicking on the python environment button on the bottom right corner of the IDE:

and selecting the pixi environment from the dropdown list (among the available ones):

And when running Jupyter notebooks from vscode, it is possible to select as kernel one of the pixi environments bu clicking on the top right corner of the notebook:

Issue installing packages containing git-lfs files
There is an ongoing issue that can happen when with pixi we try to install packages containing LFS files. This is due to an issue in the package manager used by pixi, uv:

https://github.com/prefix-dev/pixi/issues/2000
https://github.com/astral-sh/uv/issues/3312

This is manifesting in our setup for the jaxsim package. At the moment, to overcome this issue the first time we attempt to use pixi you have to setup the GIT_LFS_SKIP_SMUDGE=1 environment variable. So for example we can run:
GIT_LFS_SKIP_SMUDGE=1 pixi shell

Issue installing Drake package
I'm getting an error when trying to add drake package, available from pypi as:
 pixi add -f drake --pypi drake
  × failed to solve the pypi requirements of 'all' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because only drake>=0.35.0 is available and drake>=0.35.0,<=1.11.0 has no wheels with a matching Python ABI tag, we can conclude that drake<0.36.0 cannot be used.
      And because drake>=1.12.0 has no wheels with a matching Python implementation tag and you require drake, we can conclude that your requirements are unsatisfiable.

      hint: Pre-releases are available for drake in the requested range (e.g., 0.35.0b1), but pre-releases weren't enabled (try: `--prerelease=allow`)

Issue installing Drake package
I'm getting an error when trying to add drake package, available from pypi as:
 pixi add -f drake --pypi drake
  × failed to solve the pypi requirements of 'all' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because only drake>=0.35.0 is available and drake>=0.35.0,<=1.11.0 has no wheels with a matching Python ABI tag, we can conclude that drake<0.36.0 cannot be used.
      And because drake>=1.12.0 has no wheels with a matching Python implementation tag and you require drake, we can conclude that your requirements are unsatisfiable.

      hint: Pre-releases are available for drake in the requested range (e.g., 0.35.0b1), but pre-releases weren't enabled (try: `--prerelease=allow`)

So, how pixi solve works is that it first solves the conda dependencies, then given the installed version of conda dependencies it solves the python one. Which version of python are you using (or is pixi selecting?) I guess there is no drake version compatible with the required python version.

So, how pixi solve works is that it first solves the conda dependencies, then given the installed version of conda dependencies it solves the python one. Which version of python are you using (or is pixi selecting?) I guess there is no drake version compatible with the required python version.

In my case pixi is selecting python version 3.10.15. Checking on the drake pypi page it says it supports python >= 3.10.

Why? If we are installing jaxsim as a conda package, I don't think uv may complain about the git lfs files, or I am missing something? What error do you get if you try to install jaxsim without GIT_LFS_SKIP_SMUDGE ?

You're right @traversaro , my message was a regression when I was installing it from git source. Installing the onda package works fine. I tried multiple times, by cleaning the cache and existing environments and it worked fine. I will mark my message as obsolete.

So, how pixi solve works is that it first solves the conda dependencies, then given the installed version of conda dependencies it solves the python one. Which version of python are you using (or is pixi selecting?) I guess there is no drake version compatible with the required python version.

Looking in Drake documentation, from the "Supported configurations" table reported here, it shows that for Ubuntu 24 LTS is supported only python 3.12, but the footnote says that in theory also python 3.10 should be supported via pip.

BTW when I install this environment I get the following warning:
 WARN The package `etils==1.9.4` does not have an extra named `epy`

@traversaro I've seen you're one of the maintainers of the etils feedstock. Have you ever encountered this?
From a quick look at the etils package I've seen that there exist and epy extra: https://github.com/google/etils/blob/08f2c4767761240550d7040c7a9f11a7d1d83e75/pyproject.toml#L76-L78, but maybe is not included in the conda package recipe?

BTW when I install this environment I get the following warning:
 WARN The package `etils==1.9.4` does not have an extra named `epy`

@traversaro I've seen you're one of the maintainers of the etils feedstock. Have you ever encountered this?
From a quick look at the etils package I've seen that there exist and epy extra: https://github.com/google/etils/blob/08f2c4767761240550d7040c7a9f11a7d1d83e75/pyproject.toml#L76-L78, but maybe is not included in the conda package recipe?

I am unable to reproduce the warning, what command are you executing?

Issue installing Drake package
I'm getting an error when trying to add drake package, available from pypi as:
 pixi add -f drake --pypi drake
  × failed to solve the pypi requirements of 'all' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because only drake>=0.35.0 is available and drake>=0.35.0,<=1.11.0 has no wheels with a matching Python ABI tag, we can conclude that drake<0.36.0 cannot be used.
      And because drake>=1.12.0 has no wheels with a matching Python implementation tag and you require drake, we can conclude that your requirements are unsatisfiable.

      hint: Pre-releases are available for drake in the requested range (e.g., 0.35.0b1), but pre-releases weren't enabled (try: `--prerelease=allow`)

Can you add python = "*" among the dependencies ? Doing that solves the problem for me:
index c078c78..a98a258 100644
--- a/pixi.toml
+++ b/pixi.toml
@@ -23,6 +23,7 @@ mesalib = ">=24.2.4,<25"
 notebook = ">=7.2.2,<8"
 ipykernel = ">=6.29.5,<7"
 resolve-robotics-uri-py = ">=0.3.0,<0.4"
+python = "*"

 [pypi-dependencies]
 # TODO: move adam-robotics package to conda dependencies as soon as PR https://github.com/ami-iit/adam/pull/100 is merged

However, the confusing error is indeed a pixi problem, if you do it in a simple case you get the clear error that a python is missing from dependencies.

Can you add python = "*" among the dependencies ? Doing that solves the problem for me:
index c078c78..a98a258 100644
--- a/pixi.toml
+++ b/pixi.toml
@@ -23,6 +23,7 @@ mesalib = ">=24.2.4,<25"
 notebook = ">=7.2.2,<8"
 ipykernel = ">=6.29.5,<7"
 resolve-robotics-uri-py = ">=0.3.0,<0.4"
+python = "*"

 [pypi-dependencies]
 # TODO: move adam-robotics package to conda dependencies as soon as PR https://github.com/ami-iit/adam/pull/100 is merged

However, the confusing error is indeed a pixi problem, if you do it in a simple case you get the clear error that a python is missing from dependencies.

Strange, even doing this I continue to get the same error (I also removed the pixi.lock and cleaned previous environments).
I tried in an empty project to do:
pixi init

pixi add drake --pypi

and got:   × missing python interpreter from environment   help: Use pixi add python to install the latest python interpreter.
But doing
pixi add python
pixi add drake --pypi

Then gives the same:
  × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because only drake>=0.35.0 is available and drake>=0.35.0 has no wheels with a matching Python ABI tag, we can conclude that drake<0.36.0 cannot be used.
      And because you require drake, we can conclude that your requirements are unsatisfiable.

      hint: Pre-releases are available for drake in the requested range (e.g., 0.35.0b1), but pre-releases weren't enabled (try: `--prerelease=allow`)

I am unable to reproduce the warning, what command are you executing?

I remember it was logged with pretty much every pixi command on this environment, but I also cannot reproduce this now, strange.. I will let you know when if this happens again.

I am unable to reproduce the warning, what command are you executing?

I remember it was logged with pretty much every pixi command on this environment, but I also cannot reproduce this now, strange.. I will let you know when if this happens again.

Today, running pixi run test in for the Jaxsim repo I obtained the warnings:
$ pixi run test                                                                                 ✔  12:01:40 
 WARN The feature 'style' is defined but not used in any environment
 WARN The feature 'testing' is defined but not used in any environment
 WARN The feature 'viz' is defined but not used in any environment
 WARN The feature 'all' is defined but not used in any environment
 WARN The package `etils==1.9.4` does not have an extra named `epy`
 WARN The package `etils==1.9.4` does not have an extra named `epy`
 WARN The package `etils==1.9.4` does not have an extra named `epy`
 WARN The package `etils==1.9.4` does not have an extra named `epy`

@CarlottaSartore I think this issue is ready for review. To install pixi you can follow https://pixi.sh/latest/ and to use the pixi environment(s) of comodo you can follow the instructions in https://github.com/ami-iit/comodo/pull/23#issuecomment-2414421345.
Let me know if that works for you :) we can also add instructions on the README if you want

Unfortunately is still not possible to install Drake automatically through pixi, we can address this in a future PR.

I reported the issue in https://github.com/prefix-dev/pixi/issues/771 . I think that Ruben is as ROSCon so I do not think he will able to reply shortly, but at least we reported it somewhere.

I reported the issue in prefix-dev/pixi#771 . I think that Ruben is as ROSCon so I do not think he will able to reply shortly, but at least we reported it somewhere.

Thanks a lot @traversaro !!

Updated adam-robotics package since https://github.com/ami-iit/adam/pull/100 has been merged.

With the suggestion from https://github.com/prefix-dev/pixi/issues/771#issuecomment-2446340546 I was able to install drake through pixi.
Now the drake example notebook runs, but still I'm getting an unrelated error while running the simulation:
[ERROR] [2024-10-30 11:20:36.872] [thread: 548825] [blf] [QPTSID::advance] osqp was not able to find a feasible solution.
[ERROR] [2024-10-30 11:20:38.349] [thread: 548825] [blf] [QPTSID::advance] osqp was not able to find a feasible solution.
ERROR:root:MultibodyPlant's discrete update solver failed to converge at simulation time = 4.391 with discrete update period = 0.001. This usually means that the plant's discrete update period is too large to resolve the system's dynamics for the given simulation conditions. This is often the case during abrupt collisions or during complex and fast changing contact configurations. Another common cause is the use of high gains in the simulation of closed loop systems. These might cause numerical instabilities given our discrete solver uses an explicit treatment of actuation inputs. Possible solutions include:
  1. reduce the discrete update period set at construction,
  2. decrease the high gains in your controller whenever possible,
  3. switch to a continuous model (discrete update period is zero),      though this might affect the simulation run time.

I don't know if that notebook worked successfully before @CarlottaSartore

It may be a problem of drake version? @akhilsathuluri may know more about this. By checking on his lock files, I guess he used drake 1.23.0 .

It may be a problem of drake version? @akhilsathuluri may know more about this. By checking on his lock files, I guess he used drake 1.23.0 .

I tried just by pinning that version but still the I get the failed controller error, I have to try to run it with the same conda environment he used to check if it's a problem with dependencies or if the code the notebook uses has changed, breaking its functionality.

If everything else is working except for drake perhaps we can merge as it is so people that anyhow use drake for the rest of the backends, and open a different issue to track solving the drake problems? fyi @xela-95 @CarlottaSartore

Opened #27 since I'm getting the same error also from the main branch with a conda environment.

@CarlottaSartore this is ready to be reviewed :)

While testing I got the following error

but was due to my setup

LGTM @xela-95 thanks! could you please add some documentation also in the main readme ?

Sure! I will add it ASAP

While testing I got the following error
but was due to my setup

This is an issue with file descriptors, it happened seldomly also on my setup. I circumvented the problem by temporarily increasing the number of file descriptors in the terminal by executing: ulimit -n 65535. The reason why the file descriptors are exhausted is unknown to me, maybe is due to the high parallel number of download requests during the first installation of the environment.

Interestingly, it would be worth reporting this problems and its workaround somehow, for example in https://github.com/prefix-dev/pixi/discussions (as I do not know if this is a issue that can be addressed).


Release tags

https://github.com/pydata/xarray/releases marks v0.11.2 as the latest release, rather than v0.12.1. Is this intended?

Good spot @TomekTrzeciak
That's not intended. 0.12.1 is at least tagged. Anyone know why GH doesn't treat it as a release?

@max-sixty, you can see 0.12.1 under releases section by clicking 'show newer tags', but 0.11.2 is still marked as the latest. I suspect it's down to annotated vs. lightweight tags and how github interprets them. It seems like annotated tags are preferred for releases.

It appears that you can mark a tag as "release" on this page: https://github.com/pydata/xarray/tags . Since we missed a few tags, I don't know if we should move directly to 0.12.1 or mark the intermediate tags as releases too.

I'll do it for 0.12.1 so at least the latest is correct - any objections? (will do it this eve EST)

I think we need to ensure we do this step in future: https://github.com/pydata/xarray/blob/master/HOW_TO_RELEASE#L40
Closing the issue for now; thanks posting it @TomekTrzeciak

FYI I just did this for 0.12.3, which didn't show a 'release' on GH

Hmm.. I wonder if we can just tell GitHub somehow to automatically treat tags as releases.

I do wince a bit reading the full checklist - could we write a script to do most of this? I'm happy to help.
Are there any projects that do this well? e.g. a script with release_script.py --version=0.12.4
Someone mentioned Hypothesis, which releases on every merge to master - though I wonder whether it makes merging to master more 'expensive'.


Also can not import macros

Using 2.6.31 I am not able to to consistently import macros and some that are already active become inactive?
I find completely shutting down the game and opening back up will allow me to import and create icon and use the macro. but that's it. you cant import any after even tho the debugger IS seeing the requested macro it never displays in my available macros loaded is GSE. please help as this is really annoying!

Update:
On a fresh start of the game everything works great (i went ahead and disabled ALL other addons to rule out conflicts).
However simply /reload ui once breaks the program. the debug is showing its trying to work but the macros that just worked no longer work.

Try a /gse forceclean
Followed by a logout and a logon.
This needs to be a logout/login and not a /reload as there are logout actions that are not occurring the first time

I will try that
On Thu, Dec 3, 2020, 2:52 PM Timothy Minahan<EMAIL_ADDRESS>wrote:

Try a /gse forceclean
Followed by a logout and a logon.
This needs to be a logout/login and not a /reload as there are logout
actions that are not occurring the first time
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/760#issuecomment-738299738,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR7UUOHMDKQRZD54RIOK7GLSS727DANCNFSM4UMQGUDQ
.

closing as no further information


Batch update

As the title says, just a simple method to update records in batch :)
And line ending should be ok this time :)

Sorry I forgot about this... just fixed the docstring

Hey @gtalarico do you plan on doing a new release to include this? Would be great to have it as part of the pypi library!

Thanks for the bump @DylanScotney
released as .15.12
https://pypi.org/project/airtable-python-wrapper/#history


Improve integration with fastlane

Hi,
it would be nice to be able to get the code coverage from a Fastlane lane. A quick'n'dirty way to do it can be seen in this gist
But this is just the unfolding of the gem inside the action. It could break at any update. A simple way to do it would be for the gem to have the option to be called fastlane style so that it returns all the infos needed in a result object.
I'm sorry I won't have time to propose any PR for this. But maybe someone is interested or already working on a similar case.

Hi @teriiehina 👋
As you have said one of the good things about building the gem of top of fastlane-core is that we don't need to update the fastlane action when a change is made onto our gem. However, we can share information thorough other mechanisms like environment variables, do you think it'd do the job or just in a very limited way?
Thanks!

oh yeah, environment variables would be totally fine. In fact, that's what I used (gist):
Actions.lane_context[SharedValues::SUPER_XCOV_CODE_COVERAGE] = coverage

I opened an issue instead of a PR as I don't know what are the preferred coding/architecture style for xcov. If you can give me general directions, no problem to open a PR.

Hi again @teriiehina 👋
Please take a look at this contribution by @hds: #29 with that you could read the json and therefore have access to the entire report. What do you think? would that resolve your issue?


Incorrect Username / Password handle.

https://github.com/Undeadkillz/node-steam-bot-manager/blob/5c42e0520ff03b3c7741931b23000f329e26d4f9/lib/index.js#L442
^ Analytics message
https://github.com/Undeadkillz/node-steam-bot-manager/blob/5c42e0520ff03b3c7741931b23000f329e26d4f9/gui/GUI_Handler.js#L147
^ One of two instances where incorrect un/password being sent.
Is there a reason you are tracking incorrect passwords and usernames, Curious?
Regards
Duffyboyo

Not really, I was excited to try and track usage of different functions. But kinda gave up on it since it's useless and time-consuming. You can simply disable stats tracking if you do not wish to send me usage info (it's all anonymous and doesn't include any info other than the function being run btw).

Alright, please update to the latest version using 'npm update', it addresses this issue. If you notice any more slip-ups, please post them here. Thank you for reporting the issue.
I will keep the issue open for the next few days in case you have any further issues/questions.
Regards,
Samer A.


SSDP Incorrectly Identifies Hue Bridge as Roku Device

When allowing SSDP to search for Rokus on my network, it incorrectly identifies my Philips Hue Bridge (Generation 1) as a Roku device.

Hmm, interesting. I wonder if node-ssdp isn't correctly filtering for the "roku:ecp" identifier or if possibly the hub is responding incorrectly to the broadcast.
I don't have the time to investigate right now, but if you come up with a solution submit a PR and I'll merge it in.

I have this same issue. I ended up adding an extra check to the ssdp response call.
//handle the ssdp response when the roku is found
ssdp.on('response', function (headers, statusCode, rinfo) {
    if ( headers.ST === 'roku:ecp' ) {
        rokuAddress = headers.LOCATION;
        console.log("Found Roku: ", rokuAddress);
    }
});

It's a little redundant, but the ssdp.search() doesn't appear to be reliable.

Hey @mikehobi, that looks good! Would you mind submitting a pull request for that change?

Thanks @mikehobi

No problem!


*_locator logs leak URL password

url parse 'em out
no reason to ever log them, even at RUST_LOG=debug

Yeah, this requires fixing some Display and Debug methods on Locator implementations. It's on the list.
But in the meantime, please don't run in production with logging turned up.

@emk this happens even at RUST_LOG=warn
remember, it's added to the log context
        // Build a logging context.
        let ctx = ctx.child(o!(
            "from_locator" => opt.from_locator.to_string(),
            "to_locator" => opt.to_locator.to_string(),
        ));

fixed by https://github.com/faradayio/dbcrossbar/commit/84358c5e6b68d75d1a83c7dc3092f492005b07b6


[Question] Any plans to support morph animations between svg's?

I really would like to have a chance to use that feature

There are other libraries available for this. Closing.


No logo in docs on mobile

Hey @iansu , Here's the fix for the issue #7521 .  Docusaurus by default hides the logo for resolution less than 1200px. Hence, I have made the logo to be displayed for all devices. Sample screenshot here

Fixed by #7521


email webmaster question

Modifies form to request details of bug
Adds User id, name, and login to email if email is created by a logged-in user
Fixes #2267

coverage: 94.372% (+0.001%) from 94.371%
when pulling 133ade56425af562e306981d4ba6729ed1ac55a5 on 2267-email-webmaster-question
into cc39660763652cd238ffcad12ab708bce5fea5d4 on main.


(project): upgrade wecross stub to 1.3.0.

Codecov Report
Patch coverage: 53.77% and project coverage change: +0.15 :tada:

Comparison is base (76c4d26) 53.80% compared to head (850dd97) 53.95%.

:exclamation: Current head 850dd97 differs from pull request most recent head 523ac1e. Consider uploading reports for the commit 523ac1e to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #147      +/-   ##
============================================
+ Coverage     53.80%   53.95%   +0.15%
- Complexity      385      416      +31
============================================
  Files            42       44       +2
  Lines          3390     3675     +285
  Branches        263      298      +35
============================================
+ Hits           1824     1983     +159
- Misses         1380     1479      +99
- Partials        186      213      +27

Impacted Files
Coverage Δ

...ain/java/com/webank/wecross/common/FabricType.java
6.25% <0.00%> (-0.42%)
:arrow_down:

.../wecross/stub/fabric/ChaincodeResourceManager.java
77.00% <ø> (ø)

...ebank/wecross/account/ExtendedIdentityFactory.java
28.57% <28.57%> (ø)

...ain/java/com/webank/wecross/utils/FabricUtils.java
53.52% <32.00%> (-11.70%)
:arrow_down:

...m/webank/wecross/account/FabricAccountFactory.java
45.31% <33.33%> (+7.21%)
:arrow_up:

...a/com/webank/wecross/stub/fabric/FabricDriver.java
57.43% <37.50%> (-0.94%)
:arrow_down:

...va/com/webank/wecross/stub/fabric/FabricBlock.java
61.61% <56.03%> (-17.46%)
:arrow_down:

...k/wecross/account/X509ExtendedSigningIdentity.java
78.57% <78.57%> (ø)

...m/webank/wecross/stub/fabric/FabricConnection.java
58.80% <90.00%> (+0.58%)
:arrow_up:

...java/com/webank/wecross/account/FabricAccount.java
70.00% <100.00%> (+3.33%)
:arrow_up:

... and 1 more

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Getting "ESLint server shut down itself" message. Linting not working

Hi,
after the latest update of VS Code, ESLint seems to be not working.

I'm not sure how can I restart it and make it working again.

@sunpietro Which version of ESLint extension are you on?

THis works for me using VS Code 1.30 and ESLint 1.7.2


[integration_test] Enable sharding of integration test suites

Use case
When running integration tests normally, the tests are executed sequentially on the connected device.
This is fine if the integration test suite is small. But it does not scale well when the suite grows.
This is an impediment for CI/CD pipelines containing integration tests because the integration tests will become the bottleneck.
For example, I have a test suite containing 10 integration tests. Running those alone already takes about 12 minutes (only running the tests on the device, excluding the time it takes to build the tests).
Sharding the integration test suite means to split the whole integration test suite into n shards which can be run in parallel on n devices to speed up running the whole integration test suite.
Firebase Test Lab provides an option num-uniform-shards to do this. See the documentation here and note that this is only available on the beta channel of the gcloud sdk.
However, this option currently does not work with Flutter tests. When using the option, one shard contains all the tests and the other shards are empty. This causes the whole test suite to fail because shards should not be empty.
The flank team has documented this quite nicely here with an example project containing integration tests.

Excerpt from flank's documentation
--num-uniform-shards
Test:
gcloud alpha firebase test android run \
  --project flank-open-source \
  --type instrumentation \
  --app build/app/outputs/apk/debug/app-debug.apk \
  --test build/app/outputs/apk/androidTest/debug/app-debug-androidTest.apk \
  --num-uniform-shards=3 \
  --timeout 5m

Result:
┌─────────┬────────────────────────┬───────────────────────────────┐
│ OUTCOME │    TEST_AXIS_VALUE     │          TEST_DETAILS         │
├─────────┼────────────────────────┼───────────────────────────────┤
│ Failed  │ walleye-27-en-portrait │ 1 test cases failed, 5 passed │
└─────────┴────────────────────────┴───────────────────────────────┘

Expected behaviour
The Flutter example app contains 6 test methods, so according to doc, the gcloud should create 3 shards, each shard should contain 2 methods.
Investigation results

One shard contains all test's
Two other shards are being empty.

Conclusions
The result is different from expected behaviour.

Proposal

I would like to be able to shard an integration test suite so it can be run faster by executing the shards in parallel on multiple devices.
More specifically, I would like to be able to use the --num-uniform-shards option of Firebase Test Lab.

Really wish for this feature to be implemented. +1

@danagbemava-nc @goderbauer any clues on timeline about getting this one in a near release?

Another +1 for this proposal. Running instrumentation tests in parallel would help massively with our CI times!

any updates on it?

Running the tests in profile mode could also speed them up, but flutter test command runs only in debug mode for some reason.

I don't understand why it's P5.

I investigated this problem and drafted a solution that'd solve it (and a few other issues).
Firebase Test Lab can work only on native test cases, written using native test frameworks (Java/Kotlin on Android, Objective-C/Swift on iOS). Flutter's integration_test package does integrate with these tools, but in a basic way. For example, native test cases are created only after all Dart tests execute, so there's no way for FTL (or any other platform) to shard them, because they don't exist yet.
Flutter's integration_test is not compatible with Android Test Orchestrator, which is the recommended way to run UI test on Android. My draft solves that as well.
Basically, the current bridge between Flutter <---> iOS/Android testing tools is very rudimentary and for sharding to work, it needs to be improved.

I'm happy to share that we have solved this problem in Patrol - a new custom testing framework for Flutter. It's not stable yet, but it will be, soon :)
See yourself:
https://github.com/flutter/flutter/assets/40357511/dd78f00d-2455-4b93-8d06-245817c00d63

Just a quick update: we released Patrol 2.0 yesterday, which has support for test sharding :) See the changelog entry for 2.0.

is there update on this sharding of integration test feature?

If there was an update, it'd be posted here.
Your best option is to use Patrol (if you want this feature).

Is there any update on this feature implementation for flutter integration tests?

@vcgupta-indihood If there was an update, it would surely be posted here. And as far as I know, no work is being done in this area.


"Steer" P2S traffic to an NVA

Hello,
Can I please ask for another scenario to be added to this doc?
What happens if we want to route all P2S traffic to a Network Virtual Appliance that sits in our VNET? Is this possible? If yes, how do we have to use the UDR to achieve this? Do we apply it on the Gatewasubnet?
We have a support ticket open for this exact same scenario (Ticket #<PHONE_NUMBER>00039) but I thought this would be something that other folks would be interested in so I decided to post here.
Thanks,
t

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

ID: 6860efb1-ddab-04a1-bf34-4e0a41844102
Version Independent ID: 2321ec49-4cb8-d477-3430-44af3790bcdd
Content: About Azure Point-to-Site routing
Content Source: articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: anzaman

@tFable Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@cherylmc Hi, can you please check this issue, the customer is asking adding another scenario. Thanks.

@tFable - I've sent this on to the PM to document. Great idea! Thanks! #please-close

@anzaman - can you please comment?

I have some additional info from my testing (can also be found on ticket<PHONE_NUMBER>00039.)
When a UDR ,mapped to the Gatewaysubnet, mentions IP subnets that are part of the VNET or peered VNET's address space and it designed to "steers" traffic to an NVA, the UDR is honored and P2S traffic is routed via the NVA. However, if the UDR references on-premises destinations, then the UDR is not honored and P2S traffic destined for on-premises subnets is not routed to the NVA and the traffic dies as soon as it enters Azure.
On the other hand, as mentioned in this article, if P2S client is trying to send traffic to a subnet that is included in the S2S VPN BGP table of the VNET, then the P2S client CAN reach on-premises destinations by going to Azure and then exiting out of the S2S VPN.

Thank you for the feedback, we will add this scenario to the documentation.
-Ali

Thank you @anzaman
Can you please let me know if "steering" P2S traffic destined for on-premises via a Network Virtual Appliance is supported?
Thanks,
Tony

Yes, but you have to be careful with applying UDR to the gateway subnets.

Hey @anzaman
Can you please clarify? I have tried using a UDR that references on-premises subnets and applied it to the Gatewaysubnet, however, P2S traffic destined for those on-premises subnets never hits the NVA. I have ensured that the correct routes were manually added on the P2S client.
Please take a look at ticket<PHONE_NUMBER>00039 for some detailed testing results.
It would be fantastic if we can achieve this scenario and any advise on what I'm doing wrong would be greatly appreciated.

Hey I'm the SE on the case he is referring to.
In my testing a UDR on the GatewaySubnet does not affect P2S clients at all.
@tFable I think he is just referring to the fact that UDRs that include certain internal Azure IPs can break the VNG.

I'm going to go ahead and close this PR. Thanks for the doc scenario! #please-close


Update titlebar customization doc for Microsoft.UI.Windowing.AppWindowTitleBar

Since the release of Windows App SDK 1.2, title bar customization using AppWindowTitleBar is supported downlevel on Windows 10. The release note page for WinAppSDK has a summary for this under "Windowing" section.
This PR is to update the MSDN doc to capture the latest changes.

Resubmitting through private repo.


Override host/target for src/docs if Qt >= 6.7.0

Fixes https://github.com/miurahr/aqtinstall/issues/775

@rectalogic Thanks!


Multipart upload blocks EventChannel with file reading IO

I believe the code for uploading multipart files blocks the EventLoop with IO.
If I understand it right, this closure is reading data in a blocking way: https://github.com/swift-aws/aws-sdk-swift/blob/624305c09f4098431a20421c1e5243704fa6fc25/Sources/AWSSDKSwift/Extensions/S3/S3%2Bmultipart_API.swift#L204
I see there is a task already to use NIO.NonBlockingFileIO for the upload: https://github.com/swift-aws/aws-sdk-swift/issues/222 There are a couple other options that could fix the issue as well

Move the file reading to a different thread. Not ideal, but better than blocking an EventLoop.
Support sending a FileRegion, which can be sent on a Channel without loading it into memory at all.

#271 fixes this.
I have also added https://github.com/swift-server/async-http-client/pull/202 so we can supply AsyncHTTPClient with FileRegions


[Feature] FR - IP address

Description of the feature
If possible, could dash. show the IP of the device (WAN and or LAN) under the new NETWORKING section?
Additional context
No response

It would definitely be possible, but why would you want this?

because I don't know what ip my servers are using and it would be nice to quickly check. I normally access them through a vpn (tailscale).

I am not sure, if that is something that fits in this project. I think I will make all the labels more configurable, then I can add it as an optional label.


Override issue with component

Hi everyone,
my team and me are currently using styled-components for our project and we love it!
We are currently creating an icon component and wondering why we can't override this icon component style.
Component
/**
*
* Icon
*
*/

import React from 'react';
import styled from 'styled-components';

import '!!style-loader!css-loader!assets/fonts/font.css';

const IconStyled = styled.i`
  font-size: inherit;
  color: black;
  color: ${(props) => props.white ? 'white' : 'inherit'};
  margin-right: 0px;
`;

function Icon(props) {
  return (
    <IconStyled className={`bc-${props.iconName}`} />
  );
}

Icon.propTypes = {
  iconName: React.PropTypes.string.isRequired,
};

export default Icon;

Styling + Usage
const Icons = styled(Icon)`
  font-size: 50px; <-- This is not working
  margin-right: 5px; <-- This is not working
`;

Did someone already had this issue?
Thank you!

Version
1.4.3

Does it work with !important?

You're not passing through the className prop to IconStyled, so styled-components can't do its job. ;)
If you pass it through, for example like this, it should work:
<IconStyled className={`${props.className ? props.className : ''} bc-${props.iconName}`} />

Thanks @diondiondion I totally missed that 😊

@diondiondion @mxstbr Thank you a lot! Works perfectly!


Update self-service-sign-up.md

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


Implement Threshold SHA256 fullfilment

I need a description here @adrianhopebailie .

We need to implement the THRESHOLD-SHA-256 type of fulfillment.
See the spec: https://github.com/interledger/rfcs/blob/master/0002-crypto-conditions/0002-crypto-conditions.md#threshold-sha-256-threshold-sha-256-condition-type
The current code only implements the other types.


Error last build of TRFP

While testing quantms, we found https://github.com/bigbio/quantms/issues/432 an error in some of the raw files:
Progress of 'loading mzML':
  Progress of 'loading spectra list':
  -- done [took 14.11 s (CPU), 14.10 s (Wall)] --
  Progress of 'loading chromatogram list':
  -- done [took 0.00 s (CPU), 0.00 s (Wall)] --
-- done [took 14.12 s (CPU), 14.11 s (Wall) @ 48.98 MiB/s] --
Memory usage (loading MS data): 853 MB (working set delta), 855 MB (peak working set delta)
-- General information --
File name: UPS1_125amol_R2.mzML
File type: mzML
Instrument: LTQ Orbitrap Velos
  Mass Analyzer: Fourier transform ion cyclotron resonance mass spectrometer (resolution: 0)
MS levels: 1, 2
Total number of peaks: 49814125
Number of spectra: 44115
Ranges:
  retention time: 0.33 .. 9299.35 sec (155.0 min)
  mass-to-charge: 0.00 .. 1999.96
    ion mobility: <none>
       intensity: 1.00 .. 137152720.00
Number of spectra per MS level:
  level 1: 7302
  level 2: 36813
Peak type from metadata (or estimated from data)
  level 1: Centroid (Centroid)
  level 2: Centroid (Centroid)
Activation methods
    MS-Level 2 & CID (Collision-induced dissociation): 36813
Precursor charge distribution:
  charge 2: 20840x
  charge 3: 13151x
  charge 4: 2427x
  charge 5: 347x
  charge 6: 48x
Number of chromatograms: 1
Number of chromatographic peaks: 44115
Number of chromatograms per type:
  base peak chromatogram:                         1
FileInfo took 14.59 s (wall), 28.19 s (CPU), 0.59 s (system), 27.60 s (user); Peak Memory Usage: 891 MB.

[8:27](https://bigbioworkspace.slack.com/archives/D046E5YGFHS/p1729664854778759)
latest version:
Progress of 'loading mzML':
  Progress of 'loading spectra list':
  -- done [took 13.72 s (CPU), 13.73 s (Wall)] --
  Progress of 'loading chromatogram list':
  -- done [took 0.00 s (CPU), 0.00 s (Wall)] --
-- done [took 13.73 s (CPU), 13.75 s (Wall) @ 50.78 MiB/s] --
Memory usage (loading MS data): 853 MB (working set delta), 855 MB (peak working set delta)
-- General information --
File name: UPS1_125amol_R2.mzML
File type: mzML
Instrument: LTQ Orbitrap Velos
  Mass Analyzer: Fourier transform ion cyclotron resonance mass spectrometer (resolution: 0)
MS levels: 1, 2
Total number of peaks: 49837600
Number of spectra: 44115
Ranges:
  retention time: 0.33 .. 9299.35 sec (155.0 min)
  mass-to-charge: 0.00 ..<PHONE_NUMBER>9127773984755715932160.00
    ion mobility: <none>
       intensity: 0.00 ..<PHONE_NUMBER>41549913785241933185024.00
Number of spectra per MS level:
  level 1: 7302
  level 2: 36813
Peak type from metadata (or estimated from data)
  level 1: Centroid (Centroid)
  level 2: Centroid (Centroid)
Activation methods
    MS-Level 2 & CID (Collision-induced dissociation): 36813
Precursor charge distribution:
  charge 2: 20840x
  charge 3: 13151x
  charge 4: 2427x
  charge 5: 347x
  charge 6: 48x
Number of chromatograms: 1
Number of chromatographic peaks: 44115
Number of chromatograms per type:
  base peak chromatogram:                         1
FileInfo took 14.24 s (wall), 27.46 s (CPU), 0.62 s (system), 26.84 s (user); Peak Memory Usage: 891 MB.

Yes @caetera . Thanks a lot for looking into this.

Thanks! Just to clarify:
It affects only the second file.
And the problem is that if you look at the output that yasset posted, the OpenMS mzml parser parses at least one spectrum that has an incredibly high m/z value.
So high in fact that it is probably the result of an uninitialized random memory location. It could be that the annotated length of the mzarray does not match the actual length of the spectrum to be decoded anymore. Or something even more strange.

Note the different number of peaks that are parsed (while the number of spectra stayed the same)

Interesting, that happens in two different machines, in two different places.

@ypriverol did we really try two different downloads of the file though? I only know of the one file that Dai shared.

I tested 2 different Windows (10 + 11) systems, and two Linux (Ubuntu 20.04 LTS and 24.04 LTS, both running latest version of Mono), i.e. 4 downloads in total - SHA-1 checksums (calculated by TRFP and by sha1sum) are consistent between the downloads, and differ to the one in the shared mzML. Conversion is successful in all cases.
Could you provide more information on the platform you are running on? Is it containerized?

I have been trying to reproduce the error without success. We can leave it for now. Im adding checksum to SDRF, and also to our pipeline for the future, to trace this better.


sublime package

looking forward to trying this via sublime package install. Thanks for your efforts.

You can install the development version by following the instruction in README now 😄 .

awesome, thanks!

Could be installed from Package Control now.


Added browser field in package.json for bundlers

Just for bundlers like rollupjs where we can decide to build for browser.

That file provides the polyfill right away on the global, not a ponyfill.
Is that what you are looking for? (it's fine to me)

Yes, and it's just to get my config file clean ;)

1.6.2 has this field in


[ZEPPELIN-4526] Consistent with old version output path

What is this PR for?
Consistent with old version output path
What type of PR is it?
[Refactoring]
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4526
How should this be tested?
N/A
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

will this impact the work that I created?

@fred521 Don’t worry this is not required, I will close this PR temporary.