Cannot find module 'json-schema-faker'

when i run
prism mock https://raw.githack.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore-expanded.yaml

show me
Error: Cannot find module 'json-schema-faker'
    at Object.<anonymous> (~/.nvm/versions/node/v8.9.3/lib/node_modules/@stoplight/prism-cli/node_modules/@stoplight/prism-http/lib/mocker/generator/JSONSchemaExampleGenerator.js:5:11)

Hey, let’s get this sorted! What was your installation method and which version are you running, and are we on windows, OS X or Linux here?

I get the same error when I do:
➜  Stoplight npm install -g @stoplight/prism-cli@alpha
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/bourne. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
/Users/taylorbarnett/.nvm/versions/node/v10.15.3/bin/prism -> /Users/taylorbarnett/.nvm/versions/node/v10.15.3/lib/node_modules/@stoplight/prism-cli/bin/run
+<EMAIL_ADDRESS>added 288 packages from 276 contributors in 44.784s
➜  Stoplight prism mock https://raw.githack.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore-expanded.yaml

Error: Cannot find module 'json-schema-faker'
    at Object.<anonymous> (~/.nvm/versions/node/v10.15.3/lib/node_modules/@stoplight/prism-cli/node_modules/@stoplight/prism-http/lib/mocker/generator/JSONSchemaExampleGenerator.js:5:11)

This is happening because we're using the resolutions property in the package.json which is working  exclusively with yarn. We'll figure out a way to get rid of this.
In meantime, @xieyx, can you try to install Spectral using the binaries or yarn?
yarn global add @stoplight/prism-cli

@xieyx This should now be fixed in the latest alpha. Just upgrade your local installation with the same command you ran:
npm i -g @stoplight/prism-cli@alpha or also npm i -g @stoplight/prism-cli

@XVincentX Thanks. It's ok now.


[ENH] Make bids_participant_id and bids_session_id mandatory

Is there an existing issue for this?

[X] I have searched the existing issues

New feature
These columns will be expected & used by the Neurobagel CLI to parse subject-session level processing info and attempt to match subject-sessions from the processing status TSV with a BIDS dataset.
Unclear documentation
No response

Closed by #354


Ruby Capstone

Link to the kanban board:
https://github.com/bill7pearl/Ruby-kanban/projects/1
Team members:
This is a Ruby capstone project contributed by two partners @bill7pearl & @Salwa99.
Tasks assigned:

Team Member # 1: @bill7pearl
Team Member # 2: @Salwa99

Hi Team,
Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!
Highlights 💯

Descriptive info✔
Tasks distributed equally ✔

Required Changes ♻

Kindly add a description of the following tasks:

[ ] https://github.com/bill7pearl/Ruby-kanban/issues/14
[ ] https://github.com/bill7pearl/Ruby-kanban/issues/13
[ ] https://github.com/bill7pearl/Ruby-kanban/issues/15

as per this requirement all tasks should have description.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

STATUS: APPROVED ✔ ✔
Hi @bill7pearl and @Salwa99,
✔ Tasks are properly assigned
Your project is complete!  There is nothing else to say other than... it's time to go ahead with the project :shipit:
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear. And please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Support for virtual documents?

Not sure if I missed this anywhere in the docs. Does the LSP provide support for virtual documents? I'm thinking of something akin to how IntelliJ treats decompiled sources; you can open them in your editor, but they are read-only and don't necessarily exist in the user's workspace.

This would be very useful for the haskell lsp server too. It seems like vscode already supports this to some extent, but not via LSP: https://code.visualstudio.com/api/extension-guides/virtual-documents

Dups https://github.com/microsoft/language-server-protocol/issues/336


[WIP] Koalas Series.str functions

As discussed in #281, this PR creates Series.str functions for manipulating strings in Koalas Series.

Any mypy experts? I think str might be a special attribute name, and I'm getting this failure with the linter.
mypy checks failed:
databricks/koalas/series.py: note: In member "__getattr__" of class "Series":
databricks/koalas/series.py:1089: error: Invalid type "databricks.koalas.series.Series.str"
databricks/koalas/series.py:1090: error: str? has no attribute "startswith"

I don't know what the right way is ... but this worked:
str_type = str # in the beginning of the file

...
    def __getattr__(self, item: str_type) -> Any:

Codecov Report

Merging #292 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #292      +/-   ##
==========================================
+ Coverage   93.57%   93.63%   +0.05%
==========================================
  Files          33       34       +1
  Lines        3286     3331      +45
==========================================
+ Hits         3075     3119      +44
- Misses        211      212       +1

Impacted Files
Coverage Δ

databricks/koalas/series.py
92.46% <100%> (+0.29%)
:arrow_up:

databricks/koalas/tests/test_series_string.py
100% <100%> (ø)
:arrow_up:

databricks/koalas/strings.py
100% <100%> (ø)

databricks/koalas/__init__.py
88.88% <0%> (-3.71%)
:arrow_down:

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 397f76f...5e210ac. Read the comment docs.

Argh, seems it's wrongly merged. Can you rebase or make another pr after closing this?

Ah yes, I'll try making another pr after closing this one.
Just a heads up, I'm going to be gone on vacation for a week and a half, but will revisit this when I get back!


.NET: Add package type for Windows Readme.

Description
Improvement
Added additional column for .NET 4.8,4.72 package type.
Related issue:
https://github.com/actions/virtual-environments/issues/953
Check list

[+] Related issue / work item is attached
[+] Documentation is updated (if applicable)
[-] Changes are tested and related VM images are successfully generated

/azp run windows2016, windows2019


Thread 1: signal SIGABRT build ios

when I executed the project with lottie installed I have the following error

more details:

Environment:
OS: macOS High Sierra 10.13.4
Node: 9.11.1
Yarn: Not Found
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.3.1 Build version 9E501
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4

Package.json
{
"name": "easypay",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"firebase": "^5.0.3",
"lottie-react-native": "^2.3.2",
"react": "16.3.1",
"react-native": "0.55.4",
"react-native-elements": "^0.19.1",
"react-native-loading-spinner-overlay": "^0.5.2",
"react-native-router-flux": "^4.0.0-beta.31",
"react-native-vector-icons": "^4.6.0",
"react-navigation": "^2.0.4",
"react-redux": "^5.0.7",
"redux": "^4.0.0",
"redux-thunk": "^2.2.0"
},
"devDependencies": {
"babel-jest": "22.4.4",
"babel-preset-react-native": "4.0.0",
"jest": "22.4.4",
"react-test-renderer": "16.3.1"
},
"jest": {
"preset": "react-native"
}
}
other image

Why is this happening? I think there is a configuration in xcode that I am forgetting
Thank you very much for your time

In the Embedded Binaries section above click the + icon and add the Lottie.framework.iOS from Lottie.xcodeproj
https://medium.com/react-native-training/lottie-react-native-tutorial-162d91840720

if you are using firebase, this works for me.
https://github.com/invertase/react-native-firebase/issues/1633#issuecomment-432801902

I added lottie.framework in embedded binaries and it worked ...

where is embedded binaries? theres no such thing on my xcode

Hello Guys,
I was having the same issue on RN 0.60.4
The error was actually caused by this:
libswiftCore.dylib requires an OS version prior to 12.2.0
And the easy fix for this issue in my case was to create an empty swift file on my project.
I hope this can help anyone facing the same issue.

Hi Mate,
I got the same issue on RN 0.60.5. Can you please provide screenshot of your blank swift file? what's the name of the file? and where to put it? Thank you before.
Regards,


ipam: Ensure the package builds on macOS

~Change constant to use a cross-platform version, as it turns out netlink constant is only an alias to unix.AF_INET.~

test-me-please

@tgraf @glibsm per conversation last week, I gathered this doesn't have to be moved to datapath package and just a simple change to constant is sufficient.

Coverage decreased (-0.03%) to 45.508% when pulling 0cd4c426faf4b173f5357a1b4bed70c933ca829e on pr/errordeveloper/operator-macos-build into d22fd6911757231df29d37cefa658c81260269f9 on master.

test-me-please

known flake https://github.com/cilium/cilium/issues/10231 merging


NodePool container.gcp.upbound.io should not LateInitialize node_count

What happened?
When creating a NodePool MR, the subsequent reconciliation of this resource updates spec.forProvider.nodeCount. This can sometimes cause the node to be wrongly resized as it conflicts or lags behind the value set by the GKE cluster autoscaler
How can we reproduce it?
Create a Cluster and NodePool with autoscaling enabled.
What environment did it happen in?

Crossplane Version: 1.12.2
Provider Version: 0.28.0
Kubernetes Version: 1.24.12
Kubernetes Distribution: GKE

@sengjea could you please provide us full MRs and steps to reproduce the issue?

@sengjea thank you for the quick reply, I can reproduce the issue. It makes sense not to LateInitialize the node_count parameter.
Feel free to contribute, this guide will help you.

I can reproduce this bug as well. It happens for me on a composition that creates a Cluster and 2 NodePools. Each Node Pool has a nodeCount of 1, set by Crossplane in forProvider: after the first Refresh. Once the node pools scale up,  Crossplane requests a scaledown, based on nodeCount:1.
The following errors also happen on the NodePool:
 Normal   UpdatedExternalResource        21m (x6 over 74m)       managed/container.gcp.upbound.io/v1beta1, kind=nodepool  Successfully re │
│ quested update of external resource                                                                                │
│   Warning  CannotObserveExternalResource  18m                     managed/container.gcp.upbound.io/v1beta1, kind=nodepool  cannot run refr │
│ esh: refresh failed:                                                                                │
│   Warning  CannotObserveExternalResource  2m19s (x22 over 8m20s)  managed/container.gcp.upbound.io/v1beta1, kind=nodepool  cannot schedule │
│  a native provider during observe: 2a8e58e4-be07-4bb5-8128-cad4325e730c: cannot schedule native Terraform provider process, please conside │
│ r increasing its TTL with the --provider-ttl command-line option: native provider reuse budget has been exceeded: invocationCount: 112, tt │
│ l: 100

I've changed the provider and ignored nodeCount in lateInitialization.

Autoscaling ON: works as expected: nodeCount is no longer written in forProvider; atProvider.nodeCount is correct. After create, no requests are made to resize the nodepool
Autoscaling OFF: works, nodeCount is respected on both create and update from Crossplane

If I switch from autoscaling on->off, or off->on, I get a Terraform error. It wants to destroy and recreate (but the resource has prevent delete - this is expected GCP behaviour, you cannot change autoscaling behaviour without a recreate)

Exact error: cannot run plan: plan failed: Instance cannot be destroyed: Resource google_container_node_pool.nodepool has lifecycle .prevent_destroy set

Update on tf error. Even after I rollback my change to autoscaling, the error persists. If I want to increase nodeCount from 2 to 3 I get an error. After some local debugging, I removed the prevent_destroy. I found that:
Terraform will perform the following actions:

  # google_container_node_pool.nodepool-static must be replaced
-/+ resource "google_container_node_pool" "nodepool-static" {
      ~ id                          = "projects/upsidr-staging-argus/locations/asia-northeast1-a/clusters/nodepool/nodePools/nodepool-static" -> (known after apply)
      ~ initial_node_count          = 2 -> 3 # forces replacement

This is true for both Autoscaling on -> off  and off -> on. So ignoring changes seems to work for nodeCount but I believe initialNodeCount needs to be treated as well.


Inheritance Issues, Generic Typing and the FileReader

Take the following example:
const fileReader: FileReader = new FileReader();
fileReader.addEventListener('load', handleFileLoad);
fileReader.readAsDataURL(file);

const handleFileLoad = (event: ProgressEvent) => {

        const fileReader: FileReader = event.target;
        console.log(fileReader.result);
};

This actually breaks when checked by flow as ProgressEvent.target must be of the type EventTarget.
However, FileReader extends EventTarget, but an error is still thrown when trying to assume this. It is possible to access the event.target as if its a FileReader by wrapping the access as such;
if(event.target instanceof FileReader) { }

But in this implementation, any object could be checked for, there seems to be no correlation between checking for objects that extend the intended EventTarget type.
Is there a reason why it isn't possible to use class inheritance to satisfy the type? Since FileReader extends the EventTarget, is there a way it could be accepted as well as other possible EventTarget extensions?
Additionally, would it instead be better to type-hint ProgressEvents or other Event types less generically to better handle cases like this?
For example if the file reader returned a FileReaderProgressEvent instead of a generic ProgressEvent, it could then expect it's event.target to be a FileReader instead of a generic EventTarget.

This is a pretty frustrating issue. I feel it a lot because even for regular html events like click, the event.target is just an EventTarget and has to be cast to an HTMLElement.
The reason things don't work in this case is that ProgressEvents can have different types of targets. In your use-case, it's a FileReader, but there are also DOM progress events where the target might be a DOM element. So at the type level, just because Flow knows it's a progress event doesn't mean it can assume the target will be any more specific. And there are tons of possible combinations of event names, event targets, and types of thing that the target should maybe be.
So, when you try to type your handler function with a more specific type, saying that it demands to be given an event with a more specific target, Flow (correctly!) says that that doesn't type check, because the code calling the function will possibly provide a target of a different type.
On the browser side, I'm pretty used to just doing the cast to HTMLElement inside the event handler and then not worrying about it. I suspect the right solution is the same here, too.


Router service name should be configurable

If the router service name was configurable, we wouldn't have to re-implement this factory when the router you want to use is not aliased to RouterInterface::class
https://github.com/mezzio/mezzio-cors/blob/a61a344246be20667478821b05f5081fc526eb04/src/Service/ConfigurationLocatorFactory.php#L22

WHY would the router not properly aliased to? if that is the case, the application would not pick that router up for routing either and thus would not match?
thats the whole point of how routing works in mezzio:
https://github.com/mezzio/mezzio-router/blob/4.0.x/src/RouteCollectorFactory.php
Everything basically uses that service, so the cors component should do that as well.
I would suggest to streamline those projects you have issues with rather than adding workarounds in components.

We have existing form for this:
https://github.com/mezzio/mezzio-helpers/blob/5.17.x/src/UrlHelperFactory.php
In my case, I have 2 applications running out of the same code-base, each with a different router instance in the container along with a different set of routes.

Interesting. I'd rather ensure having proper configuration when bootstrapping but as there is already this kind of magic, go ahead. 🤷🏼♂

I don't think I'd call it magic though - it's just configuration for "what service id gives me a router?", defaulting to the accepted norm.


[Question] About debugging on 3090 and the pretrained adapter in finetuning script

Question
Firstly, I want to appreciate the tremendous work you have put into this project. It has been quite insightful and enlightening for me.
I am having a bit of trouble regarding fine-tuning pre-trained models and I'm hoping you can provide some assistance.

While perusing your code, I noticed an argument named pretrain_mm_mlp_adapter in the finetune.sh script. However, I could not find the corresponding location in the codebase that details how to generate this adapter. Could you please provide some guidance or refer me to the relevant section where I can understand more about this pre-trained adapter?
I'm considering debugging the fine-tuning code on my personal workstation, which has 3 RTX3090 GPUs and 128GB of CPU memory. For this, I would like to clarify that I'm not specifically looking to achieve similar performance as your setup. I am primarily interested in ensuring the code can run on my workstation. Can you confirm if this setup would be adequate for running and debugging the fine-tuning code?

Any assistance you can provide would be greatly appreciated. Thank you again for your time and dedication to this project!

Hi @haotian-liu , I just noticed that the scripts/extract_mm_projector.py was removed at commit eae9369. Would you mind provide us with some suggestions to extract the mm_projector from pretrained model? Or can we just use the removed script?

Hi @xiaobaishu0097
In our latest code base (llava>=1.0.0), you do not need to extract the projectors anymore, as we now only save the projector during the pretraining stage, and do not save frozen LLM weights during the pretraining stage (which was a waste of the disk space).
If you are interested in using our pretrained projectors, you can check out our model zoo.
Regarding debugging on RTX 3090. You can use --tune_mm_mlp_adapter or --freeze_backbone to save memory. I just tried that this works for tuning vicuna-7b v1.3 on 2x 3090s.
Thanks.

Hi @haotian-liu
Thanks for all your help!
I am trying to fine-tune the 13B vicuna on 2 A100-80G. However, I noticed that the GPU memory consumption keeps increasing during training. I just want to know, is that a normal situation? And what is the normal batch size when we fine-tune the model on A100-80G?


Docker ARM support

I've looked into building ARM based Docker Images and this is the solution that worked on my private repo.
I tried the Docker image on my Raspberry Pi and it worked fine there.
This solves issue https://github.com/bagetter/BaGetter/issues/134

Can the current image be used on windows containers too? Would be nice to add windows to the build targets too then to keep those users happy. With docker desktop I could just switch to windows containers, but I'm not sure how to do that with podman yet so I can't test it right now.

I don't know. Do you mean Windows Docker Container? I am not sure how to do this the correct way. Would need to figure this out and test this.
I would suggest to do this in another release.

Can the current image be used on windows containers too? Would be nice to add windows to the build targets too then to keep those users happy. With docker desktop I could just switch to windows containers, but I'm not sure how to do that with podman yet so I can't test it right now.

I don't know. Do you mean Windows Docker Container? I am not sure how to do this the correct way. Would need to figure this out and test this. I would suggest to do this in another release.

If you have docker for windows, you can just right-click the symbol and "Switch to Windows containers". Then run the image to see if everything works.


Blazor state management topic

Fixes #13259
Internal Review Topic

HOLD merge until package is on NuGet. I'll keep an :eye: on it.
I recommend the generic title that I use here (sans "server-side") so that the article can address client-side state further later. "Server-side" is in the article description, and there are ample remarks to explain that this topic applies to server-side only. This is just a recommendation, of course. I'll react to your feedback, including if you prefer the title be more specific about "server-side" application. Just have a feel'in that it will change soon enough to say something more about Blazor client-side state management ... even if it's only to mention and cross-link some 3rd party options (here are a few).
Let's withhold a common sample app demo for now. The 🧀 could move on this one.
The "circuits" concept is new to docs. We have an issue now for engineering to flesh that out, perhaps in the hosting models topic :point_right: Document "circuits" for Blazor server-side (aspnet/AspNetCore.Docs #13360).

@SteveSandersonMS Updates made. Do you want to say anything further about ...

"The server can't retain disconnected circuits forever. ... The timeout and retention limits are configurable."

:point_up: Idk the limits/timeouts exactly ... doesn't seem like it refers to SignalR limits. How are these timeouts+limits configurable? I can see about cross-linking this remark to the appropriate place(s). If the content doesn't exist, I can open an issue, but let me know if the new content should be documented along with the concept of "circuits," as we already have an issue for that at https://github.com/aspnet/AspNetCore.Docs/issues/13360.

let me know if the new content should be documented along with the concept of "circuits," as we already have an issue for that at #13360.

Yes, that sounds ideal.

... and Microsoft.AspNetCore.ProtectedBrowserStorage on NuGet ... still on the way? 🎁

Yes, I'll follow up on this today.

Let's make sure that we HOLD this until the package goes live ...
https://www.nuget.org/packages?q=Microsoft.AspNetCore.ProtectedBrowserStorage

@SteveSandersonMS The package is still in-progress for NuGet.org? We can publish this as soon as the package goes live.

The package is still in-progress for NuGet.org? We can publish this as soon as the package goes live.

Yes, and we have the final build of it now. Just waiting for it to be uploaded to NuGet.org.

Thanks @SteveSandersonMS ... I'll keep an :eye: out for it.
@Rick-Anderson Do u want to go ahead and look? I'll merge after reacting to your feedback and after I confirm that the package is there.

OK, it's published now: https://www.nuget.org/packages/Microsoft.AspNetCore.ProtectedBrowserStorage/0.1.0-alpha.19406.1
May have to give it a few minutes to update its caches before that page starts to return valid content.

@guardrex  lets S&M now and possibly merge to live. I'll do a PR tonight or tomorrow to shorten any long sentences.

No long sentences here. I already squashed four or five long ones after the last PR.
I'll make a final quick pass on this and then shoot it in. I'll take master to live after that.

@SteveSandersonMS We never discussed the end of this passage (emphasis added here) :point_right:

The server can't retain a disconnected circuit forever. The server must release a disconnected circuit after a timeout or when the server is under memory pressure. The timeout and retention limits are configurable.

How are the timeout and retention limits configurable? I'd like to cross-link ... are the timeouts/limits confugurable via SignalR? ... or do you want to leave this as it is for now? ... or chop this remark out for now?

@guardrex I'd recommend cross-linking to the relevant section of https://github.com/aspnet/AspNetCore.Docs/issues/13360 when that's written. Until maybe leave it without further explanation.

Thanks, I'll track that by making a note on that issue. For now, I'll strike it here.


Hero Variant

As shown in Figma, we will use Hero component in details page.
We need to extend Hero component variant with 300px height.

You can give prop isFullHeight with an initial value true. If isFullHeight={false}than we will have 300px height hero.

#55


Return stellar-core and horizon versions

This PR adds HorizonVersion and StellarCoreVersion to root resource.
Close #73.

Looks like there are some formatting issues on this PR.  Could you run the changed files through gofmt?

Other than choosing a better default for overridable version string:  :+1:

Fixed.


Tweak diff output

Thanks.
I wonder why coveralls is stuck and didn't report back on the PR

Coverage decreased (-0.16%) to 86.0% when pulling fdcc7f2a15713fbffc7b80987d1121f8a85d8424 on papandreou:tweakDiffOutput into 19b11bab69c6819c74fa7341ea4ca293b0b4c756 on Munter:master.


Clarify Expo support in documentation

From what I'm seeing browsing through the code this seems like it should be perfectly compatible with Expo (managed workflow) projects. However, it would certainly be nice to have this explicitly stated in the documentation as this is the kind of library many newcomers to React Native (who are quite likely to be using Expo) would be looking for.

Thanks for pointing this out. Yes, the package is perfectly compatible with both Expo-managed and bare workflows. There are zero 3rd party dependencies and no native packages required. I'll see where in the documentation I'll add a note about this.

Fixed in 0678f705d155cf3b284772b241581d05cd1091a3


Fix parsing of timeseries data when metadata is stored in CSV.

@claytonpbarrows @jd-lara Sorry for this, but my earlier PR introduced a regression.  You'll hit a bug if you try to parse time series data from timeseries_pointers.csv instead of timeseries_pointers.json.  All of our test data uses JSON but the RTS_GMLC repo uses CSV.  We need a test to cover CSV; I'll add one to PowerSystems.

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   67.21%   67.21%
=======================================
  Files          30       30
  Lines        1409     1409
=======================================
  Hits          947      947
  Misses        462      462

Impacted Files
Coverage Δ

src/forecast_parser.jl
72.22% <ø> (ø)
:arrow_up:

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 65276ee...f31ac9b. Read the comment docs.


(2.2.11) Growing zones will not trigger boulder hauling

IMPORTANT: Please first search existing bugs to ensure you are not creating a duplicate bug report!
Describe the bug
when creating a growing zone, and the area of the zone includes boulders, the game will not trigger hauling orders automatically to move the boulders out of the way for sowing the growing zone.
Steps to reproduce the behavior (VERY IMPORTANT)

Open the attached save
hit 4

Recreating without the save:

Create a sowing/growing zone on top of boulders
when the colonists start sowing, they will ignore the boulders and not move them (in vanilla, the colonists will move the boulders to the edge of the growing zone)

Error Log
!!! Link to contents of Player.log or Error.log (MUST BE LINK) !!!
!!! Link to HugsLib log. (MUST BE LINK) !!!
No errors triggered
Save file
!!! Please add a save file where the issue occurs to speed up testing and fixing of the issue !!!
growin zones boulder hauling.zip
Screenshots
!!! Add screenshots to help explain your problem here !!!
Mod list (For vanilla report, it has to be same as below list.)

Harmony
Core
Royalty (optional)
HugsLib
RimThreaded

Tested in 2.2.13. On a new save I created a few growing zones over boulders and bushes, and the pawns moved the boulders and cut the bushes.


Azure DevOps Self Hosted

Hello, I was wondering is Azure DevOps self hosted supported? I see several shields for Azure DevOps are there but is it possible to use a self hosted version of shields to work with a self hosted version of Azure DevOps? I was trying to do it through the custom badge method but I couldn't figure out how to enter my personal auth token.

Hi @eberkund - to clarify, are you asking if you can use the Shields.io service for badges from TFS/Azure DevOps Server?

Not exactly, I am currently using the built in DevOps badges:

However I would like to add a new custom badge for code coverage. DevOps server provides a JSON API with this information so I believe it is possible.

We provide native badges for code coverage from Azure Pipelines already:
https://img.shields.io/azure-devops/coverage/swellaby/opensource/49.svg

https://shields.io/

Isn't that only for the cloud hosted one?

I didn't see a way to customize the URL to use my self-hosted server.

Okay, as I had asked before, you are using a self-hosted TFS/Azure DevOps Server?

Yep, that is what I am using

Thank you for confirming. The short answer is that no it's not possible today to use Shields to create badges for a self-hosted TFS/Azure DevOps Server instance. We'd be more than happy to review a PR if anyone is interested in adding this! There's two key points to consider:

the main Shields.io service can only be used to interface with internet-accessible services/tools that do not require user/account specific authentication. That's why Shields.io can work with AzDO accounts, including coverage and test results badges for public projects. If your target tool/service does not meet both of those criteria (for example the tool/service runs on your private intranet, etc.) then you have to run your own self-hosted Shields instance. I suspect that anyone using the self-hosted AzDO Server/TFS will almost certainly be running it within a private network.
The Azure DevOps badges we have today are based off the URL pattern and APIs explicitly for the SaaS Azure DevOps (formerly known as VSTS), which may or may not be compatible with the self-hosted Azure DevOps Server (formerly known as TFS).

If the latest version of the self-hosted AzDO Server has identical APIs as the main SaaS service, then a relatively simply solution would be to add an optional server query parameter that folks (again probably using their own self-hosted Shields server) can use to specify there self-hosted AzDO Server endpoint to override the default dev.azure.com base that's currently always used (something similar was done for the Bitbucket badges not too long ago).
However, if the API sets are completely different then we'd have to discuss whether support for self-hosted AzDO servers is something we want to incorporate, as we do not really add badges to Shields that only work for private/self-hosted services.

Okay, thanks for the response.


Add improvements to the readme.

Add improvements to the readme.

@jmtsuji Any other changes?

@jmtsuji I have addressed your feedback. I'm looking forward to your final approval.


Update getPrestigeByIcon

Adding more ranks into getPrestigeByIcon for you

Silly me I kept on forgetting the // on the comments


Error events not automatically reported to Sentry when running on device or emulator

Environment
Capacitor SDK v0.18.0
Framework: React/Remix in SPA mode
Steps to Reproduce
Initialise the SDK as the following:
import { RemixBrowser } from '@remix-run/react'
import { startTransition, StrictMode } from 'react'
import { hydrateRoot } from 'react-dom/client'
import * as Sentry from '@sentry/capacitor'
import * as SentryReact from '@sentry/react'
Sentry.init(
  {
    enabled: import.meta.env.PROD,
    dsn: '__MY_DSN__',
    integrations: [
      SentryReact.browserTracingIntegration({
        tracePropagationTargets: ['localhost'],
      }),
      SentryReact.replayIntegration({
        maskAllInputs: true,
        maskAllText: false,
        blockAllMedia: false,
        networkDetailAllowUrls: ['[redacted]'],
        // networkRequestHeaders: ['Cookie', 'X-Fallback-Cookies'],
      }),
      SentryReact.captureConsoleIntegration({
        levels: ['log', 'warn'],
      }),
    ],
    // Performance Monitoring
    tracesSampleRate: 1.0,
    // Session Replay
    replaysSessionSampleRate: 0.1,
    replaysOnErrorSampleRate: 1.0,
  },
  // Forward the init method from @sentry/react
  SentryReact.init,
)

startTransition(() => {
  hydrateRoot(
    document,
    <StrictMode>
      <RemixBrowser />
    </StrictMode>,
  )
})

After initialisation, the app will try to execute an undefined function and run into an error. This happens automatically after initialisation.
Expected Result
Events are reported to Sentry on all environments.
Actual Result
Events are correctly reported when running in a browser, but are not captured by the SDK when running the app on an ios device or emulator.
Logs: https://gist.github.com/devo-devo/0a6090c08dc880db3a87410197ce8475
The workaround was to add captureException method in the errorBoundary component:
https://gist.github.com/devo-devo/e4e6b37511c8453b70f41afaaff9b197
https://gist.github.com/devo-devo/780c62fabc6f7fb0dbfb150811634926
Removing the errorBoundary has no effect on the final result, the errors are not captured on the device.
Original report

Since the project is using Remix, it is recommended to use Sentry Remix instead of React (using version 7.114.0).
The setup for Remix is different, so I recommend using the following documentation to set up Sentry with it: Sentry Remix Manual Setup.
Sentry Capacitor is currently not officially supported by Remix. Ideally, you should use the Sentry Remix SDK by itself. However, you can also use Sentry Capacitor with it. The difference is that in entry.client.tsx, you initialize Sentry Capacitor along with the Remix SDK. On the server side, you only initialize the Remix SDK.

I'm using Remix in SPA mode, which essentially builds everything into a client side app of only html and js - so I won't need to initialize on the server side.
Is it confirmed that deploying to a simulator or device using sentry/remix & sentry/capacitor on the client side captures the exceptions w/o the manual workarounds? Is there en example Sentry.init for the client side that you've found works in this scenario?

I would recommend following this setup for using Remix with Capacitor for the time being

Closed as not supported


DAE solver for non-smooth currents

Fix (at least one of the) DAE solvers to work when the input current is not smooth.
Hacky approach is to do step-by-step and match up discontinuities with steps, or try stepping the differential and algebraic equations separately

could we augment model.events to take 2 types of events: "termination" and "discontinuity". The solver would then make sure to integrate up to just before a discontinuity, and restart integration just after the discontinuity.

Good idea, so would the discontinuities be a list of variables for which to look out for discontinuities? Or do we analyse the input current (a parameter) before solving to identify discontinuities and then tell the model/solver about them before solving?

I'm thinking that the user would manually specify where the discontinuities occur in time, based on the parameters of the model. Therefore discontinuities would be an expression that evaluates to the time when the discontinuity takes place.
So, given a model that has parameter a and which exhibits a discontinuity at 2*a, the user would set model.events = [(pybamm.DISCONTINUITY, 2*a)]
Then it would be easy for the solver to get the list of where discontinuities occur in time, and make sure that the integration is restarted at each discontinuous time-point

Each event now needs 3 pieces of info, its name, expression and type (DISCONTINUITY or TERMINATION). I think this needs a separate class to encapsulate this (and provide some documentation). Implemented this as Event, so that to create some events you might do something like this:
        model.events = [
            pybamm.Event("var1 = 1.5", pybamm.min(var1 - 1.5)),
            pybamm.Event("var2 = 2.5", pybamm.min(var2 - 2.5)),
            pybamm.Event("nonsmooth rate",
                         pybamm.Scalar(2.5),
                         pybamm.EventType.DISCONTINUITY
                         )
        ]


[Bug]: error cndy.state.goLiveDate.toNumber

Feature
The problem is when you do yarn install, then set your .env file and do  yarn start the mint button appears but it is not clickable and in console the following message appears:
TypeError: cndy.state.goLiveDate.toNumber is not a function
Ideal solution or implementation
Fix the issue related to latest release of candy-machine-ui
Alternative solutions or implementations
No response
Other context
No response

I made the modification suggested in #3 and it worked for me. Thanks MarkSackerberg 🎉
For those who don't want to wait until the PR is merged:
in src/candy-machine.ts, just go l. 210 and change goLiveDate by goLiveDate: state.goLiveDate

I did that - it worked at least now i can see how many nft still -- and i can see the price too --
but I got a new err  !!
i have enough sol - and i can mint using the terminal -- but the mint button still clickable ---

I did that - it worked at least now i can see how many nft still -- and i can see the price too --
but I got a new err !! i have enough sol - and i can mint using the terminal -- but the mint button still clickable ---

Works if you do this.
goLiveDate: state.data.goLiveDate,

Thank you Very much it works !!!


Webpack loader for external CSS files

[x] This is a v1.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Just want to start by saying I'm not a huge contributor to open source, so if this is a bad place to put this feel free to shout and I'll take it down.
I was struggling with JSS for a number of reasons, so I decided to write a Webpack loader for loading external CSS files into JSS, specifically for use with Material UI. I really just want to share it in case it can be helpful to someone else who wants to keep their CSS in CSS but still use the Material UI theme. I doubt it has any room in the official Material UI repo, but who knows if it will spark any ideas.
Link to loader: https://www.npmjs.com/package/css-to-mui-loader
Examples
Basically, you can do things like this in your CSS:
:root {
  --xs-color: blue;
}

.button {
  background: $(theme.palette.primary.main);
  padding: 2su; /* Material UI spacing units */
}

.button:hover {
  background: $(theme.palette.primary.light);
}

@media $(theme.breakpoints.only('xs')) {
  .button {
    background: var(--xs-color);
    -mui-mixins: theme.mixins.button;
  }
}

...and then load it as you would an external JS file:
import Button from '@material-ui/core/Button';
import { withStyles } from '@material-ui/core/styles';
import styles from './styles.css';

const MyComponent = withStyles(styles)(({ classes }) => (
  <Button className={classes.button}>
    Click Me
  </Button>
));

Under the hood it converts to something like this:
export default (theme) => {
  const xsColor = `blue`;
  return {
    button: {
      background: `${theme.palette.primary.main}`,
      padding: `${theme.spacing.unit * 2}px`,
      '&:hover': {
        background: `${theme.palette.primary.light}`,
      }
    },
    [theme.breakpoints.only('xs')]: {
      button: {
        ...theme.mixins.button,
        background: `${xsColor}`,
      }
    }
  };
};

Context
I hoped to solve the following problems with this loader:

copy/paste CSS directly from Chrome inspector
make it easier for designers on the team to not have to work with JS
reduce verbosity of my style files
but still leverage the MUI theme and the power of scoped JSS

Again, happy to remove or move this issue if it's not helping anything, but also open to suggestions of where else to post this for others who may find it useful.

@mcdougal Thank you for sharing this webpack loader, it's slick! ❤
JavaScript theme object into SCSS
I have been suggesting people to load the JavaScript object theme into SCSS in #12699. This approach has already been pioneered by people like @planetflash in https://itnext.io/sharing-variables-between-js-and-sass-using-webpack-sass-loader-713f51fa7fa0.
MyComponent.scss
.root {
  font-family: get('typography.fontFamily');
  &:hover {
    background: get('palette.primary.main');
  }
}

MyComponent.js
import Button from '@material-ui/core/Button';
import styles from './MyComponent.scss';

// The direct mapping between `classes` and `styles` is possible because
// we follow the CSS API of Material-UI.
const MyComponent = props => <Button classes={styles} {...props} />;

export default MyComponent;

This works best when your theme is a static object. The CSS output is generated at build time.
Now, when you have to deal with a dynamic theme, you are out of luck. Here is where I think your approach comes it 💃.
CSS to JavaScript
Generating the CSS at runtime requires more ressources but allow much more flexibiltiy. It's a different tradeoff, it's great to have it!
We have a documentation section on this topic https://material-ui.com/guides/interoperability/. It would be great to document how people can leverage the theme in the CSS/LESS/SCSS/PostCSS approaches.

This is great.

@oliviertassinari Per your suggestion, I opened a PR to add documentation for css-to-mui-loader to the https://material-ui.com/guides/interoperability/ section: https://github.com/mui-org/material-ui/pull/12841. Let me know if there is anything you think I should change.


PEStudio install fails due to  wrong checksum

I have try to reinstall PEStudio but the checksum is not correct. Any help?

same

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM has just been released and will make the project more open and maintainable.
Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:

new tools or tool-related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.


fix makecode simulator + screen reader?

There is a bug in NVDA where it steals focus and moves it to the next element. This breaks keyboard support for the makecode arcade simulator.

fixed.


Measure and output installing and downloading durations

Description
Improving output for "Install-Binary" and "Start-DownloadWithRetry" functions with additional measuring and logging of installing and downloading durations.
Test run:
https://github.visualstudio.com/virtual-environments/_build/results?buildId=116599&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=5431112d-2b61-5a5f-7042-ef698f761043&l=5552
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[x] Changes are tested and related VM images are successfully generated

/azp run windows2016, windows2019, windows2022


Add 'mark thread as done' functionality

Fixes https://github.com/google/go-github/issues/3264.

Thank you, @tomfeigin!
Merging.


Baselines: finetuning

There are missing baseline results for some tasks/models we want to compare our models with. Potential baselines could be BERTurk, mBERT, mT5, or mBART, depending on whether the task type is classification or conditional generation. We should also consider the model size when choosing a baseline for a fair comparison. Our model has 1.1 billion parameters.

Outdated.


Use the Microsoft.Storage resource provider for Azure file share management operations

Resource Provider
Microsoft.Storage
Description of Feature or Work Requested
Today, the Azure Files CLI commands for file share management (az storage share) go through the Azure storage data plane. This causes a number of issues for customers, most notably it means customers are unable to manage their file shares if their Azure storage account is in a vnet and the client where they are running the Azure CLI (such as their laptop) isn't - this is a very common management scenario for Azure Files. Therefore, we would like to add a new command path, az storage share-rm, that sends the file share management requests through the Storage Resource Provider (SRP) instead of through the Azure storage data plane.
We need to add a new command path for several reasons. First and most importantly, not all operations are available on the file share proxy resource object offered by SRP, by design. For example, operations to create and manage SAS tokens are not planned and are unlikely to be ever added to the file share object. Secondly, SRP is being a middle-man for file share requests - the requests they get to manage a file share are passed through to the data plane APIs (SRP has a way through customer vnets). SRP is generally believed to have less performance than the underlying data plane API. Therefore, it is strongly recommended that customers needing to do many calls against the Azure file share at once should use the data plane. Although this is not the primary thing that customers use Azure Files for today, we have to maintain this path for compatibility reasons. Finally, adopting SRP will require some significant changes to the command interface, and we would like to avoid a breaking change. Note, this change has already been done in the Azure PowerShell package - we maintain (verb-Aznoun, which goes through the data plane, and verb-AzRmnoun, which goes through SRP).
Minimum API Version Required
Microsoft.Storage 2019-06-01
Swagger Link
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/storage/resource-manager/Microsoft.Storage/stable/2019-06-01/file.json
Target Date
1/13
Here's the link to the OneNote describing the change.

@Juliehzl  add to S164.

@wmgries, in your description, you mentioned that "Minimum API Version Required
Microsoft.Storage 2019-06-01", is this feature only supported in 2019-06-01 as I checked https://github.com/Azure/azure-rest-api-specs/blob/master/specification/storage/resource-manager/Microsoft.Storage/stable/2019-04-01/blob.json and found the API spec of 2019-04-01 is very similar with 2019-06-01?

@wmgries, could you please help to confirm the question mentioned above?

Hey, sorry I missed this. I don't see why you cannot use 2019-04-01, however, the control plane is missing several features currently, in both API versions, that are in plan to be added in January. Several examples: snapshot support and share stats. These will presumably use 2019-06-01 as I do not think they require breaking changes to the API.
The spec I gave does not assume this missing features are there.

@wmgries , thanks for your confirmation. We'll use 2019-04-01 for this feature and in the future, when we support features only in 2019-06-01, we'll use 2019-06-01.
Also this time for each command, CLI will not support the following options as PowerShell didn't support them yet. If we do need support them, we can support them in the future.

We only support using "account-name", but not support "account-id".
We will not support "ids" for the commands in spec, such as "az storage share-rm show --ids string[]>"

I would argue the equivalent to account-id for PowerShell is taking in an object. For example:
$storAcct = Get-AzStorageAccount -ResourceGroupName "myRG" -Name "mysa"
New-AzRmStorageShare -StorageAccount $storAcct -Name "myshare"

CLI does let you get storage accounts by the ID of the storage account, (az storage account show --ids), so if you're in the position where you have the ID of a storage account, I don't see why you shouldn't be able to create a proxy resource with it instead of having to independently lookup the name and resource group of the resource.

@wmgries, thanks for your comments. We'll support account-id as well.
But for the commands (exists, delete, show, update), we'll not support option "--ids" to keep consistent with PowerShell and data plane file share commands as neither PowerShell nor data plane file share support "--ids", does this decision make sense to you?

This feature was already released in Azure CLI 2.0.81.


Keyboard Navigation?

Hi @oliviertassinari! While I know that this is intended mostly towards mobile use-cases, I was wondering if you plan to support keyboard navigation and ARIA attributes given that it works for browsers?
Thanks!

Hi,
I don't think that we should build the keyboard navigation in the core of the lib.
But we could do something like the autoPlay HOC using react-event-listener 👍 .
Regarding the ARIA, I don't have any expertise on this field. What do you have in mind?


gfold: 4.0.0 -> 4.0.1

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gfold/versions.
meta.description for gfold is: "CLI tool to help keep track of your Git repositories, written in Rust"
meta.homepage for gfold is: "https://github.com/nickgerace/gfold"
meta.changelog for gfold is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.0.1 with grep in /nix/store/k985c4ss3i9j8v3qvg58a65w1d2madra-gfold-4.0.1
found 4.0.1 in filename of file in /nix/store/k985c4ss3i9j8v3qvg58a65w1d2madra-gfold-4.0.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gfold

Instructions to test this update (click to expand)

Build yourself:
nix-build -A gfold https://github.com/r-ryantm/nixpkgs/archive/d74cd24a03ad1e9318ce101750bc9652802ba426.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k985c4ss3i9j8v3qvg58a65w1d2madra-gfold-4.0.1
ls -la /nix/store/k985c4ss3i9j8v3qvg58a65w1d2madra-gfold-4.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gfold

Maintainer pings
cc @shanesveller for testing.

FWIW I didn't get to it in time but I would've been happy to approve the PR as of d74cd24a03ad1e9318ce101750bc9652802ba426 instead.

FWIW I didn't get to it in time but I would've been happy to approve the PR as of d74cd24 instead.

Please check: https://github.com/NixOS/nixpkgs/pull/180746
I didn't know how to remove the commit in GitHub GUI. =(

Botched the nixpkgs-review command, sorry. Will repeat with the correct replacement PR.


New Icons

Credit goes to @iwazaru

Hey @neynah can you also updates the images in public/icons (I personnaly use Favomatic) or includes a high-res version so I can do it myself? Thanks!

Let me know if these are OK! I used favomatic, it was super fast. ;)


GetArg should explicitly be case insensitive

It's currently not clear whether arguments are case insensitive or not, see ambiguity when storing and reading the config file. This is possibly an issue when checking if the current private and public keys are valid, see https://github.com/gridcoin/Gridcoin-Research/blob/master/src/rpcblockchain.cpp#L1319.
Improvements:

See if we can use boost::program_options for writing config values.
Use case insensitivity in GetArg.
Try to unit test this.
Move the many config file and argument handling functions to an args.cpp/h.

Thanks to @Foggyx420 for noticing.

has this generally been addresses since the beacon advertising issues are fixed.?
if not we coudl boost:to_lower but some keys like 'PrimaryCPID' and UpdatingLeaderBoard would be affected?


tests: smp: correct the inappropriate testcase

Update testcase test_fatal_on_smp(), and refine it and correct some
inappropriate usage such as unnecessary irq_lock(). This prevents
the error propagation to the later executing testcase.
Fixes #35200
Fixes #35202
Signed-off-by: Enjia Mai<EMAIL_ADDRESS>

@IRISZZW could you please help to verify that in your hsdk board, I did not have it. I think these two testcase-related issues can be solved by this PR, thank you!

@yingmingx could you please help to review this, I made some changes to it. thanks!


Error on search for bluetooth devices: failed to load assembly

Hello,
I am trying to create an app for Android to connect to a bluetooth device. I am using InTheHand.Net, but get the following error message whenever I try to search for devices.
error message:
[monodroid-assembly] open_from_bundles: failed to load assembly InTheHand.Net.Bluetooth.dll Loaded assembly: /data/data/com.companyname.shuntapp2/files/.__override__/InTheHand.Net.Bluetooth.dll [External] [monodroid-assembly] open_from_bundles: failed to load assembly InTheHand.AndroidActivity.dll Loaded assembly: /data/data/com.companyname.shuntapp2/files/.__override__/InTheHand.AndroidActivity.dll [External] [monodroid-assembly] open_from_bundles: failed to load assembly Uno.dll [monodroid-assembly] open_from_bundles: failed to load assembly Uno.dll
My code that gives me troubles is as:
public async void InitialBluetoothScan(object sender, EventArgs e)
        {
            // new bluetooth client
            BluetoothClient client = new BluetoothClient();
            BluetoothDeviceInfo[] devices = (BluetoothDeviceInfo[])client.DiscoverDevices();

            foreach (var i in devices)
            {
                Console.WriteLine($"Name: {i.DeviceName}. Address: {i.DeviceAddress}");
            }
        }

I am trying to follow along this guide: https://medium.com/the-pragmatic-tech-review/how-to-transfer-data-via-bluetooth-in-net-a23a9d6a77f6
I have tried running the code on two separate computers and get the same error on both.

How is linking configured in your project - select none or SDK Assemblies only to avoid the linker stripping out assemblies which are not referenced directly.

Thank you for replying so quickly.
Based on peterfoot's suggestion i looked up linking and I think adding the following to my .csproj file in the <ItemGroup> section solved my problem:
<TrimmerRootAssembly Include="InTheHand.BluetoothLE" />
<TrimmerRootAssembly Include="InTheHand.Net.Bluetooth" />

However, it only lead me to another problem: Now i get the following error (though only after IntheHand has been correctly loaded):
Loaded assembly: InTheHand.AndroidActivity.dll [External]
[monodroid-assembly] open_from_bundles: failed to load assembly Uno.dll
[monodroid-assembly] open_from_bundles: failed to load assembly Uno.dll

I suspect this is not directly related to IntheHand, so I will probably post another issue somewhere else.

I just found this post by you, @peterfoot , commenting on the issue I am now facing with the Uno.dll assembly.
You end the post by saying that the nuget package InTheHand.BluetoothLE no longer depends on either xamarin or maui (and Uno??).
Would you recommend I switch to using the InTheHand.BluetoothLE package rather than InTheHand.Net? Or is that depended on which type of application I aim to make?

On Android, whether you use InTheHand.BluetoothLE (Bluetooth LE) or InTheHand.Net.Bluetooth (Bluetooth Classic) you should add the following to your MainActivity to setup the activity reference which is required by some APIs particularly using pickers:-
InTheHand.AndroidActivity.CurrentActivity = this;


how to set max time and min time for any date

I have to set minTime and maxTime in date selection irrespective of the date.
So that I can select any date in 10AM - 10PM.
Is this possible in react native datetimepicker

I just had the same problem, do you know if there is any solution to it?

@dtaborda  I tried to make it this way.https://gist.github.com/anandp926/c7ab0498b8b80724325a5cf481a06fff

Hey @dtaborda I tried to make it this way. https://gist.github.com/anandp926/c7ab0498b8b80724325a5cf481a06fff

@anandp926 Does it work for android?


About Enjoy_Husky_Gibson_Flagrun_ppo1

Hello everyone,
I am studying on flagrun with ppo1 algorithm nowadays. Unfortunately, I have a problem while I am trying to run enjoy_husky_gibson_flagrun_ppo1.py.
The error is:
TypeError: __init__() missing 2 required positional arguments: 'hid_size' and 'num_hid_layers'
I realized that, model which consists information of size and layers is lost. How can I set these parameters?
A second question: I see a line in the same file  as reload_name = '/home/berk/GibsonEnv/gibson/examples/train/models/flagrun_RGBD2_50.model'. There is not any file in this location as '.model' . How can I import the model to the code and create .model file?
Thank you in advance.

Up

Did you use train_husky_gibson_flagrun_ppo1.py script to train the model? You need to run that script first. Also hid_size and num_hid_layers can be recovered from that script as well.

Yes I did, but I haven't realized that the file and some trials are terminated due to size of resolution. I will try again with slight changes and inform you.
Thank you

Hello again,
I tried to apply training the husky but I am still at same point. I couldn't the create model file. When I tried to run train_husky_gibson_flagrun_ppo1.py, I got the error which is given followings:

I couldn't see the problem in shuffle(). How can I handle with this error?
Thank you.

Different issue continues on flagrun_ppo1 with:
Connot feed value of shape (64,128,4) for Tensor 'pi/ob:0', which has shape '(?,128,128,4)
I've changed all parameters but it doesn't match. Thanks for your helping.
Sincerely,
Berk

I fixed problem. It causes due to 'ob' variable. It is also discussed in issue of #55.


Menus: Stitch together back end services and UI components to get menu contributions working end-to-end

As a Platform.Bible extension developer, I want to be able to add menus to my webviews and contribute to extensible points in platform-provided menus.

Depends on #418, #419, #420, #421, #424, #707, #722
Once we have code in place that reads in menu contribution JSON documents, transforms those into "final" JSON documents on a per web app and overall application basis, and renders those JSON documents in the UI as "proper" menus, we need to stitch all these things together so they provide an end-to-end benefit to developers and users.
The menu contribution design document has more details.
Additional note from TJ:

We might have to do a bit of rework in the extension service as I think it only actually does much of anything with extensions that contain a main file right now. We need to make sure extensions that don't have a main file still get their menus added.

Additional note from Tom (with help from Matt):
create parallel types to MultiColumnMenu and SingleColumnMenu (that should be used in the React components and MultiColumnMenuProvider) that do not expect the ReferencedItem keys, but rather plain strings. This will make it possible to remove some type casts.

Testing Steps:
In my test extension.

I updated the menus.json to include a pointer for the P.B main menu to include under projects.
manus.json

{
  "mainMenu": {
    "columns": {},
    "groups": {},
    "items": [
      {
        "label": "%mainMenu_openPAPIMenuTestScreen%",
        "localizeNotes": "Application main menu > Project > Open PAPI Menu TestScreen",
        "group": "platform.projectResources",
        "order": -1000,
        "command": "paratextExtensionTest.openPAPIMenuTestScreen"
      }
    ]
  },
  "defaultWebViewTopMenu": {
    "columns": {},
    "groups": {},
    "items": []
  },
  "defaultWebViewContextMenu": {
    "groups": {},
    "items": []
  },
  "webViewMenus": {}
}

Updated the localizedStrings.json to have localisation

{
  "metadata": {},
  "localizedStrings": {
    "en": {
      "%mainMenu_openPAPIMenuTestScreen%": "Open PAPI Menu TestScreen"
    }
  }
}

Updated the type file to include the command that is triggered on menu click on 'Open PAPI Menu TestScreen'

 export interface CommandHandlers {
    'paratextExtensionTest.testingComponents': () => Promise<string>;
    'paratextExtensionTest.randomNumGen': (num: number) => number;
    'paratextExtensionTest.openPAPIMenuTestScreen': () => void;
  }

5.Updated main.ts to register the command and to open 'PAPI Menu Test' web-view on command.
const openPapiMenuWebView = async () => {
  logger.debug(`Entered here in the openPapiMenuWebView command`);
  papi.webViews.getWebView(papiMenuWebViewProvider.webViewType, undefined, { existingId: '?' });
};
const openPapiMenuWebViewPromise = papi.commands.registerCommand(
    'paratextExtensionTest.openPAPIMenuTestScreen',
    openPapiMenuWebView,
  );

Hi @roopa0222 - That looks like a good test of the menu functionality.


Information security management practices, includes secret rotation playbook

Describe the task
Document procedures related to FAM
Acceptance Criteria

[x] reviewed by Pete
[ ] walkthrough with our team

Additional context

document will capture operational security
content is updated on our confluence page: https://apps.nrs.gov.bc.ca/int/confluence/x/RxE9Cg

Walkthrough tentatively set for Sept 06 internal demo


Add citation section in README

Perhaps we should add something in the Docs as well?

I guess so, probably just the exact same on the home page?

I think there is a mention about citing it on that page that can just be updated actually

Yes, true. I’ll do that ;)


⚠ TorrentLeech has degraded performance

In 8107b4e, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 5876 ms

Resolved: TorrentLeech performance has improved in f5dd215 after 7 minutes.


Enhancement in Azure API and RHEL/SUSE adaption of kill switch

This document is very dated. Could you please update the latest developments with Azure API and how RHEL and SUSE adapting to the kill switch feature for faster failure detection.
Also, how to get SAP Certification for HANA and SCS Pacemaker cluster to use Azure API as fencing agent?
Thanks,
Shajith
SAP & Azure Architect

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

ID: a20453e6-5273-2119-69f7-85b5108a8f7d
Version Independent ID: 4ac93e53-6969-4c8d-5b5c-0db47a8976ce
Content: Setting up Pacemaker on SUSE Linux Enterprise Server in Azure
Content Source: articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md
Service: virtual-machines-windows
GitHub Login: @MSSedusch
Microsoft Alias: sedusch

@smithashajith Thanks for the feedback!
I am assigning the issue to the content author for adding comments on this document enhancement.

@smithashajith, SUSE has not released yet the changes to dependent components(Azure Python  SDK), required to benefit from fast failover times when using the Azure fence agent.  We are in touch with SUSE and the articles will be updated as soon as we get confirmation that the changes are completed.

@rdeltcheva Thanks for providing the details and confirming on the document update timelines.

@smithashajith Hope the response for the content team helps clarify your query on the updating the document.
We will close this issue now. If there are further questions on this, please tag my name in a comment. I will reopen the issue and we will be glad to assist you further on this.


Fixed a typo in the README.md file at the options variable binding

This gave me a lot of hassle till I found out that this was the problem. I hope this fix avoids hassle for future users of the repo.

I don't think this makes a lot of sense. opts and options is user defined variable.

True, it is user defined, but in the README.md file the example is given with the variable defined as opts in the .ts file and used as options in the html file. As I copied the example exactly as it is from the README file it took me a while to realise why the options where not working properly.


fs_scandir iterator causes memory leak with early break

Using fs_scandir and fs_scandir_next as an iterator results in a memory leak if the iterator is not fully drained. Example:
local luv = require 'luv'

local function dir(d)
  return function(fs)
    return luv.fs_scandir_next(fs)
  end, luv.fs_scandir(d)
end

for name in dir('.') do
  print(name)
  break
end

This results in a memory leak. This happens because the uv_fs_req is only cleaned up when the iterator reaches a UV_EOF:
https://github.com/luvit/luv/blob/c51e7052ec4f0a25058f70c1b4ee99dd36180e59/src/fs.c#L600-L605
However, when the iteration loop breaks early this condition is never hit and uv_fs_req_cleanup is never called.
It does not seem possible to manually cleanup the fs handles either: fs:close() does not exist.

Thanks for the report, I'll look into it.

Here's an even simpler reproduction:
local uv = require('luv')
local req = uv.fs_scandir('.')

As pointed out in the OP, we currently only handle cleanup when we fully iterate with scandir_next.


Refactor Algolia search box

What is it?
Right now the Algolia search box is a self-contained modal.
Instead, I want to refactor the search+list component out and just use the default modal in Plasmic.
This way, we can use the search+list component in the terminal navigation as well.
We should be able to pass in index names and display options

Renaming modal component here
https://github.com/opensource-observer/oso/pull/1980

https://github.com/ankeetmaini/react-infinite-scroll-component?tab=readme-ov-file

Just got rid of the modal while I'm trying to refactor to a generic search list
https://github.com/opensource-observer/oso/pull/1983

Adding infinite scroll here
https://github.com/opensource-observer/oso/pull/1984

Pushing projects index page here
https://github.com/opensource-observer/oso/pull/1985

With the latest changes, the AlgoliaSearchList is both used in a modal in the navbar, as well as as a left pane in the projects/ page


higher number of creation failures

https://cmsweb.cern.ch/reqmgr2/fetch?rid=fabozzi_Run2016B-v2-ZeroBias6-17Jan2017_8020_170117_170800_2500
https://cmsweb.cern.ch/reqmgr2/fetch?rid=fabozzi_Run2016B-v2-ZeroBias6-25Nov2016_8020_161125_152646_3953
have basically identical settings and yet, the 17Jan has had way more creationg failures. which is counter intuitive, has the code that generate that failure been changed much ?

also, is max_events_per_lumi calculated at all ? why not adjusting it automatically to 48h/TimePerEvent internally ? (maybe because then we cannot fool request manager to still create the jobs ... questions and answers)

eventually : how does one set that max_events_per_lumi at assignment time ?
I think the default should be a godzillion, 20k does not make any default sense.

@amaltaro @ticoann  any indications ?
FYI @areinsvo

Sorry i missed this. I will investigate.

Code hasn't been changed long time (at least which code affect this)
Here is condition  which make creation fail
As you said both split setting seems to be identical, I am not sure how there will be number of failure difference. (I can't see the earlier workflows failure number since that workflow is archived already)
As far as logic goes, following is the logic for not creating the job.
I am not sure the logic behind it and why eventLimit is set to 20K by default.
@vlimant, @amaltaro, Could you explain if you know the logic behind it.
#If the number of events per lumi is higher than the limit
#and it's only one lumi then ditch that lumi
if f['avgEvtsPerLumi'] > eventLimit and f['lumiCount'] == 1:

Is max_events_per_lumi only parameter that one sets ?
How does one change that value via api ? is this just passing max_events_per_lumi in the json ?

Interesting, I thought this algo was failing any jobs that were supposed to process more events than the limit (default 20k), but it only fails if the file has a single lumit section (such that avgEvtsPerLumi is the exact number of events per lumi, instead of an average).
I was looking at the splitting rest api and I came up with a working example that you can use to update this max_events_per_lumi (and in theory any other splitting parameters), see:
https://github.com/amaltaro/scripts/blob/master/ReqMgr2/changeSplitting.py#L20
As you can see in the script, we only post the task arguments that were really changed, not everything. It seems there are algos (in my case it was "MinFileBased") that we cannot really update.
@vlimant 20k used to be a quite good number, but if you think there is a better default value to be put in place, please let us know. Ideally we should base it on TimePerEvent + some safe margin.

Can the value be create from 48h and the timeperevent ?

Maybe for March deployment.

in the context of data reprocessing, I think we need to solve this max_events_per_lumi issue, and have it automatically adjusted so that it never gets in our way in ACDC or recoveries

ping on that one. for data reprocessing, we have to have this parameter auto-adjusted in the agent.
I'd rather not have this in unified

ping ping https://its.cern.ch/jira/browse/CMSCOMPPR-1911

@ticoann @amaltaro could we put the default value up to 200k so that it does not bother us until we get the value properly adapted to the max pilot lifetime (46-48h) and the time/event provided.

Hi let me check whether there will be any side effect on 200k default value.  I move to a high priority and I will take the look at the problem too.

It seems increasing default value will add the risk of creating long running jobs.
With EventAwareLumiBased algorithm, the minimal lumi per jobs is 1 and and increasing max_events_per_lumi  to 200k might cause some long running jobs to be created.
I can create the patch which only fails the job in creation if estimated jobs  (number of events per job * time per events) is exceeded the 48h. I don't think we can automatically adjust the job size in that case since the minimum lumi size is 1.


Script to execute all notebooks inside the func-mooc.fr docker container

It would be nice to have a script part of the jupyterhub user docker image to be able to check that it's possible to execute all the cells of all the notebooks of the MOOC without raising exceptions and to log such exceptions otherwise.
We already do this check when we run the jupyter book command as part of the this github actions CI but this does not check that all the dependencies with the same versions are installed in the docker image used on the fun-mooc platform.

This would be nice to have in an ideal world I agree. One thing I am wondering is whether this test should be in the same repo as where the docker image is defined (the gitlab mooc-apps repo) or in this repo here (github scikit-learn-mooc).
I am also wondering whether this is premature over-engineering but maybe we can use the first session of the MOOC and see how often the problem happens in practice ...
I created a "infra" tag for this kind of things 😉 so I am going to use it here.

Some notes I had lying around on this:
Not sure what is the easiest way to do that maybe via a terminal inside JupyterHub ... although not really continuous integration this would be a start:
This would run:

all the notebooks from the github repo
convert full quizzes (from gitlab) to python file with jupytext, and run them

Maybe there is actually a way run the JupyterBook inside the container?


Custom dropdown filters

I am not quite sure if we can add some custom dropdown filters?
User selects an item from dropdown it just filters based on given dropdown item.  Then when a user searches items it searches among filtered items like given in the example below. Below is implemented in jQuery datatable. Tutorial examples would be great.

Thank you again for vuetable. It is very useful!

@cosecantt Yes, you can.
Think about it, the dropdown itself is a predefined set of filters. That means it's just another type of filter that your backend API has to deal with. You just need to make Vuetable sent this filter to your backend via append-params.
You should first think about the query string that your backend API will receive and work with.
  http://example.com/api/products?group=drink&subgroup=all&filter=co

These can be used to program into apppend-params prop.

Ok @ratiw thank you. I definately look into that. Thank you again.

Hello how did you manage to add these filters please ?


Issues when updating git dependencies in PNPM

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
npm
Package manager version
PNPM
Language version
No response
Manifest location and content before the Dependabot update
I don't have a repro for this yet, but we're seeing issues in private repositories related to upgrading dependencies coming from git sources.
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
Updates should happen correctly without errors.
In particular, we see errors like the following:
 ERROR  Command failed with exit code 128: git ls-remote<EMAIL_ADDRESS>HEAD
error: cannot run ssh: No such file or directory
fatal: unable to fork

This error happened while installing the dependencies of <name>@<version>

pnpm: Command failed with exit code 128: git ls-remote<EMAIL_ADDRESS>HEAD
error: cannot run ssh: No such file or directory
fatal: unable to fork
    at makeError (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:24230:17)
    at handlePromise (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:24801:33)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async getRepoRefs (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110651:23)
    at async resolveRef (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110663:20)
    at async resolveGit (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110614:24)
    at async Object.resolve (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:113185:173)
    at async run (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:124970:23)
/home/dependabot/common/lib/dependabot/shared_helpers.rb:329:in `run_shell_command'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:58:in `run_pnpm_updater'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:42:in `block (2 levels) in run_pnpm_update'
/home/dependabot/common/lib/dependabot/shared_helpers.rb:181:in `with_git_configured'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:41:in `block in run_pnpm_update'
/home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `block in in_a_temporary_repo_directory'
/home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `chdir'
/home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `in_a_temporary_repo_directory'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:40:in `run_pnpm_update'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:25:in `updated_pnpm_lock_content'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:245:in `updated_pnpm_lock_content'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:174:in `pnpm_lock_changed?'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:207:in `block in updated_lockfiles'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:206:in `each'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:206:in `updated_lockfiles'
/home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:42:in `updated_dependency_files'
/home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:85:in `generate_dependency_files'
/home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:36:in `run'
/home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:25:in `create_from'
/home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:122:in `check_and_create_pull_request'
/home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:59:in `check_and_create_pr_with_error_handling'
/home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `block in perform'
/home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `each'
/home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `perform'
/home/dependabot/dependabot-updater/lib/dependabot/updater.rb:72:in `run'
/home/dependabot/dependabot-updater/lib/dependabot/update_files_command.rb:38:in `perform_job'
/home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:52:in `run'
bin/update_files.rb:23:in `<main>'

I have not been able to reproduce this locally. Everytime I specify git+ssh on a package.json file, pnpm ignores it and uses https. However, that's not happening in these repositories for some reason.
Yarn & NPM have specific code to replace git+ssh with https in package.json before trying to update a lockfile, and then replacing back the updated https references with git+ssh again. So I guess this is a common problem in other package manager, so I will try to "blindly" fix it by applying the same fix.
Some preparatory work for that is at #7245.
In general, we should also review how updates behave with git dependencies, since I have not done any explicit testing with that.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Same situation here.
Dependabot Update logs
updater | 2023/05/08 21:05:15 INFO <job_659665566> Sending event ebfebc63e7474a61bf8fd59e9369a3eb to Sentry
  proxy | 2023/05/08 21:05:16 [546] POST https://sentry.io:443/api/1451818/store/
  proxy | 2023/05/08 21:05:16 [546] 200 https://sentry.io:443/api/1451818/store/
updater | 2023/05/08 21:05:16 ERROR <job_659665566> Error processing eslint-plugin-yml (Dependabot::SharedHelpers::HelperSubprocessFailed)
updater | 2023/05/08 21:05:16 ERROR <job_659665566> ╭─────────────────────────────────────────────────────────────────╮
updater |    │                                                                 │
updater |    │                Update available! 8.3.1 → 8.4.0.                 │
updater |    │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v8.4.0   │
updater |    │     Run "corepack prepare<EMAIL_ADDRESS>--activate" to update.     │
updater |    │                                                                 │
updater |    │     Follow @pnpmjs for updates: https://twitter.com/pnpmjs      │
updater |    │                                                                 │
updater |    ╰─────────────────────────────────────────────────────────────────╯
updater |
updater | Progress: resolved 1, reused 0, downloaded 0, added 0
updater | Progress: resolved 51, reused 50, downloaded 0, added 0
updater | Progress: resolved 91, reused 91, downloaded 0, added 0
updater | Progress: resolved 92, reused 91, downloaded 0, added 0
updater | Progress: resolved 122, reused 112, downloaded 2, added 0
updater | Progress: resolved 145, reused 114, downloaded 21, added 0
updater |  ERROR  Command failed with exit code 128: git ls-remote<EMAIL_ADDRESS>HEAD
updater | error: cannot run ssh: No such file or directory
updater | fatal: unable to fork
updater |
updater | This error happened while installing the dependencies of<EMAIL_ADDRESS>updater |
updater | pnpm: Command failed with exit code 128: git ls-remote<EMAIL_ADDRESS>HEAD
updater | error: cannot run ssh: No such file or directory
updater | fatal: unable to fork
updater |     at makeError (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:24230:17)
updater |     at handlePromise (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:24801:33)
updater |     at runMicrotasks (<anonymous>)
updater |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
updater |     at async getRepoRefs (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110651:23)
updater |     at async resolveRef (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110663:20)
updater |     at async resolveGit (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:110614:24)
updater |     at async Object.resolve (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:113185:173)
updater |     at async run (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:124970:23)
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/common/lib/dependabot/shared_helpers.rb:329:in `run_shell_command'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:58:in `run_pnpm_updater'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:42:in `block (2 levels) in run_pnpm_update'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/common/lib/dependabot/shared_helpers.rb:181:in `with_git_configured'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:41:in `block in run_pnpm_update'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `block in in_a_temporary_repo_directory'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `chdir'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/common/lib/dependabot/shared_helpers.rb:36:in `in_a_temporary_repo_directory'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:40:in `run_pnpm_update'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:25:in `updated_pnpm_lock_content'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:245:in `updated_pnpm_lock_content'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:174:in `pnpm_lock_changed?'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:207:in `block in updated_lockfiles'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:206:in `each'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:206:in `updated_lockfiles'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:42:in `updated_dependency_files'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:85:in `generate_dependency_files'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:36:in `run'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/dependency_change_builder.rb:25:in `create_from'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:122:in `check_and_create_pull_request'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:59:in `check_and_create_pr_with_error_handling'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `block in perform'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `each'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:34:in `perform'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:72:in `run'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/update_files_command.rb:38:in `perform_job'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> /home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:52:in `run'
updater | 2023/05/08 21:05:16 ERROR <job_659665566> bin/update_files.rb:23:in `<main>'

Here is a live repo for repro.
The dependency that cause the same issue here is @postlight/parser
https://github.com/postlight/parser/blob/e8ba7ece291efa4d915d50dd4deeec17d54359f2/package.json#L116-L134

Thanks for that example, will make this much easier to fix confidently!

@deivid-rodriguez We might be able to fix it with a small change to the Git shim. It's currently restricted to which commands to run here, and the protocols to rewrite here.

Yep, I was just looking at that!

We'd need to allow ls-remotes command and git+ssh protocol, right?

@deivid-rodriguez Yep, I think that would do it!

Awesome, I'll look into it. This is reproducible with the CLI only, so I'll add a smoke tests since I'm at it!

I wasn't lucky with the git-shim changes, but this other tweak seems to do the trick!
diff --git a/common/lib/dependabot/shared_helpers.rb b/common/lib/dependabot/shared_helpers.rb
index 80294552d..9870c1ac9 100644
--- a/common/lib/dependabot/shared_helpers.rb
+++ b/common/lib/dependabot/shared_helpers.rb
@@ -274,6 +274,10 @@ module Dependabot
         "git config --global --add url.https://#{host}/." \
         "insteadOf git://#{host}/"
       )
+      run_shell_command(
+        "git config --global --add url.https://#{host}/." \
+        "insteadOf git+ssh://git@#{host}/"
+      )
     end

     def self.reset_git_repo(path)

Just to post today's debugging of this issue, I found the culprit is here:
https://github.com/pnpm/pnpm/blob/1de07a4af3941b01fac991fae51be8b0d994c8ef/resolving/git-resolver/src/parsePref.ts#L64-L120
In that method PNPM tries to do a manual HEAD request to https://github.com/postlight/difflib.js, but since that does not succeed, it assumes it's a private repo and uses<EMAIL_ADDRESS>instead.
Some debugging prints on the failing HEAD request shows this error:
FetchError: request to https://github.com/postlight/difflib.js failed, reason: getaddrinfo EAI_AGAIN github.com
    at ClientRequest.<anonymous> (/home/dependabot/.cache/node/corepack/pnpm/8.3.1/dist/pnpm.cjs:61067:18)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:494:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN',
  erroredSysCall: 'getaddrinfo'
}

It seems like some DNS issue/misconfiguration specific to our CLI/production environment 😬.
One potential solution would be to change PNPM to use git ls-remotes with GIT_TERMINAL_PROMPT like I'm doing at https://github.com/dependabot/dependabot-core/pull/7241, instead of a manual request, but I think it'd be best to figure out how to make this request succeed in our environment so that this works consistently across PNPM versions.

I think I figured it out! node-fetch, used by PNPM here, does not respect proxy environment variables. I'm working on a patch for PNPM.

@deivid-rodriguez That makes sense. Since the Updater container is on a network where only HTTP(S) is allowed to the proxy, if it were to ignore the proxy setting the first thing it would do is make a DNS request, which will fail. When using the proxy the DNS request happens on the Proxy container.

I opened an issue and a raw patch to PNPM!


Simplify code to calculate working dir of kernel & add tests

Part of #11552

Codecov Report

Merging #11560 (567cc28) into main (c06b44d) will increase coverage by 0%.
The diff coverage is 90%.

:exclamation: Current head 567cc28 differs from pull request most recent head 4f6d44a. Consider uploading reports for the commit 4f6d44a to get more accurate results

@@          Coverage Diff           @@
##            main   #11560   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        477      478    +1
  Lines      34059    34071   +12
  Branches    5527     5530    +3
======================================
+ Hits       21507    21554   +47
+ Misses     10497    10472   -25
+ Partials    2055     2045   -10

Impacted Files
Coverage Δ

src/platform/common/utils.node.ts
70% <ø> (+14%)
:arrow_up:

src/kernels/kernelStartupCodeProvider.node.ts
91% <81%> (+10%)
:arrow_up:

src/platform/common/application/workspace.node.ts
92% <87%> (-2%)
:arrow_down:

src/kernels/kernelWorkingFolder.node.ts
93% <93%> (ø)

src/kernels/serviceRegistry.node.ts
100% <100%> (ø)

src/platform/common/cancellation.ts
64% <0%> (-4%)
:arrow_down:

src/kernels/jupyter/jupyterKernelService.node.ts
72% <0%> (-2%)
:arrow_down:

src/platform/common/utils/localize.ts
76% <0%> (+<1%)
:arrow_up:

src/notebooks/controllers/kernelRanking/helpers.ts
58% <0%> (+<1%)
:arrow_up:

.../notebooks/controllers/vscodeNotebookController.ts
82% <0%> (+<1%)
:arrow_up:

... and 10 more


refactor SignatureUtils and related usage

What is the purpose of the change

refactor SignatureUtils and related usage
split the big try-catch into pieces, make code more easy to understand
using try-with-resource clause

Codecov Report

Merging #10291 (0cb3fdb) into 3.0 (90cef36) will decrease coverage by 0.30%.
The diff coverage is 61.76%.

@@             Coverage Diff              @@
##                3.0   #10291      +/-   ##
============================================
- Coverage     65.70%   65.39%   -0.31%
- Complexity      297      318      +21
============================================
  Files          1233     1233
  Lines         53712    53682      -30
  Branches       8107     8081      -26
============================================
- Hits          35294    35108     -186
- Misses        14587    14721     +134
- Partials       3831     3853      +22

Impacted Files
Coverage Δ

.../org/apache/dubbo/auth/AccessKeyAuthenticator.java
92.30% <57.14%> (+1.19%)
:arrow_up:

...va/org/apache/dubbo/auth/utils/SignatureUtils.java
66.66% <62.96%> (+0.95%)
:arrow_up:

...dubbo/remoting/zookeeper/ZookeeperTransporter.java
50.00% <0.00%> (-38.89%)
:arrow_down:

...ng/zookeeper/curator5/Curator5ZookeeperClient.java
43.47% <0.00%> (-27.06%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...he/dubbo/rpc/listener/ListenerExporterWrapper.java
58.82% <0.00%> (-14.71%)
:arrow_down:

...mmon/threadpool/support/AbortPolicyWithReport.java
70.17% <0.00%> (-14.04%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...che/dubbo/registry/client/NopServiceDiscovery.java
44.44% <0.00%> (-11.12%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
41.66% <0.00%> (-8.34%)
:arrow_down:

... and 62 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 90cef36...0cb3fdb. Read the comment docs.


fixed osde2e image url in e2e template

What is being added?
Is this a fix for a bug?  What's the bug?  Is this a new feature? Please describe it. Is this just a small typo fix?  That's fine too!
fix

IT fixes the path to osde2e image https://quay.io/repository/app-sre/osde2e in test harness template

sdcicd-1075
Checklist before requesting review

[ ] I have tested this locally
[ ] I have included unit tests
[ ] I have updated any corresponding documentation

Steps To Manually Test
Please provide us steps to reproduce the scenarios needed to test this.  If an integration test is provided, let us know how to run it. If not, enumerate the steps to validate this does what it's supposed to.
1.
Ref sdcicd-1075

/lgtm


react-graph-reports solution has been added

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

What's in this Pull Request?

This sample describe a SPFX application which reterive an office 365 usage reports using Microsoft Graph API. This application also use chartjs library to generate graph.

Thanks a lot for your contribution, Ejaz! The web part looks awesome! :)
I modified the README slightly: added the missing telemetry image, and added a couple of steps on how to approve Graph permissions just in case someone doesn't know how to do it.
Thanks again and keep up the good work!
Laura

Thanks a lot for your contribution, Ejaz! The web part looks awesome! :)
I modified the README slightly: added the missing telemetry image, and added a couple of steps on how to approve Graph permissions just in case someone doesn't know how to do it.
Thanks again and keep up the good work!
Laura

Thanks Laura for adding missing information to the README file.

Hi Laura,
Just checking when does samples move from Dev branch to master branch?
Seems like this sample still sits under dev branch.
Regards
Ejaz
Get Outlook for Androidhttps://aka.ms/ghei36

From: Laura Kokkarinen<EMAIL_ADDRESS>Sent: Sunday, April 14, 2019 1:21:57 PM
To: SharePoint/sp-dev-fx-webparts
Cc: Ejaz Hussain; Author
Subject: Re: [SharePoint/sp-dev-fx-webparts] react-graph-reports solution has been added (#834)
Thanks a lot for your contribution, Ejaz! The web part looks awesome! :)
I modified the README slightly: added the missing telemetry image, and added a couple of steps on how to approve Graph permissions just in case someone doesn't know how to do it.
Thanks again and keep up the good work!
Laura
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-fx-webparts/pull/834#issuecomment-482962830, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASX9-ViVH_hp3QjEB4QVDIN8KFMBxViPks5vgx1lgaJpZM4ckcG_.

Hi Ejaz,
Vesa did the master merge at the end of last week, so your sample can now be found under the master branch. Sorry about the delay and the late reply!
Laura

Hi @ejazhussain, would you be interested on doing a live demo of this in upcoming SPFx calls? This is really nice sample which demonstrates the Graph usage pattern and also how to use external library - this case the chart.js. We would have a spot still next week SPFx call on 23rd of May or then next one on 6th of June, depending on your availability.

Hi @Vesa<EMAIL_ADDRESS>Happy to do the live demo. I can do 23rd May.
Regards
Ejaz Hussain

From: Vesa Juvonen<EMAIL_ADDRESS>Sent: 14 May 2019 09:37
To: SharePoint/sp-dev-fx-webparts
Cc: Ejaz Hussain; Mention
Subject: Re: [SharePoint/sp-dev-fx-webparts] react-graph-reports solution has been added (#834)
Hi @ejazhussainhttps://github.com/ejazhussain, would you be interested on doing a live demo of this in upcoming SPFx calls? This is really nice sample which demonstrates the Graph usage pattern and also how to use external library - this case the chart.js. We would have a spot still next week SPFx call on 23rd of May or then next one on 6th of June, depending on your availability.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-fx-webparts/pull/834?email_source=notifications&email_token=AES736ISTY2NS4WZPI3ZKO3PVJ25VA5CNFSM4HERYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKYLCY#issuecomment-492144011, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AES736JQVPX4TA25GB6GOELPVJ25VANCNFSM4HERYG7Q.

Sounds good, I'll add you for the agenda for the 23rd of May. Thanks for volunteering.


IMPROVEMENTS sprint 02-toolsurvey

https://nfdi4microbiota.github.io/nfdi4microbiota-knowledge-base/Software-Development/02-toolsurvey

link to license
format nicely (header size)

added links to licence definitions

@nighthog80 @pmjklemm This has been realized, right? Can we close the issue?

yes


With v2.11.2 of traefik doesn't work

With v2.11.2 of traefik version doesn't work
Please could you verify this?

https://github.com/BetterCorp/cloudflarewarp/actions/runs/8587415216/job/23531025468#step:13:41
https://github.com/BetterCorp/cloudflarewarp/actions/runs/8806669105/job/24171994305#step:13:37
Seems to work fine with the latest traefik hey
Maybe post your config and what you are issues you have and we can go from there

The Traefik image hadn't downloaded properly, which was causing issues. It wasn't a problem with the plugin


Update fetchdata script

ThronesDB no longer hosts their own images, so it should no longer be
used as an image source.

Sad 😢