.Net supported version missing

If I have to update so I have to see which .Net version is required for this control.

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

ID: 79395f69-e1fe-02ce-9687-923b42b96326
Version Independent ID: de462407-3129-4299-6892-8106bf4823a7
Content: Differences Between the Windows Forms DataGridView and DataGrid Controls
Content Source: docs/framework/winforms/controls/differences-between-the-windows-forms-datagridview-and-datagrid-controls.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Hi, @AizazAZ, You can click on the DataGridView link in the article, which will take you to the API page. On the right-hand side, click on the Applies To link, which will show you the applicable versions.  I've also included the link here. Closing this item as I believe it is resolved. If this isn't the case, please reopen.


Payment gateway

Working on the Payment Gateway for the Traveldiction Project

Payment Gateway is Working well for the Traveldiction


Wrong link on contact page: Privacy Policy

Update wrong Privacy Policy link on the contact page.

Changed to StopModReposts Privacy Policy Link.


[WIP] Feature/remove contributors multiple components

Purpose
Give users the choice to remove a user from either the current node or from the current node and all its children.
Current:

Proposed:

Changes:

Delete the user from the given node as a default with a modal.
If the Admin wants to remove the Contributor from the node AND its children, Open a second modal view, and use the API V2 to list of every component associated with the Contributor to remove.
If the Admin clicks "Remove" on the second view, use the API v2 to delete those contributors from all child nodes previously listed.

Currently blocked by #4600

After talking with @sloria and @brianjgeiger, I am going to temporarily use API v1 until the API v2 features of a request for a node tree and a contributor endpoint are implemented.  This PR is no longer blocked.

@billyhunt Please resend this to develop if it is still relevant.


Add laravel package in Readme.

I have created a laravel supported package on top of this client it will be great if we can add this in the readme as an unofficial framework client.
https://packagist.org/packages/pushpak1300/laravel-phpkiteconnect

@vividvilla


Issue with /docs/concepts/services-networking/service/

This is a...

[ ] Feature Request
[ ] Bug Report
[x] Documentation Changerequest

Problem:
The linked page (also here) describes external access to internal services via NodePort. But when I talk to people who really know Kubernetes well they always suggest to externalize services via Ingress. Without this info at the NodePort spot newcomers stop after reading about NodePorts and don't even get to the Ingress page. I mean, who reads the whole manual when one's questions are already (seemingly) answered, right?
Proposed Solution:
The page should mention Ingress, and probably how the Kubernetes stands to the NodePort vs Ingress question. My guess would be that more and more people want Ingresses instead of NodePorts, because they seem to also support other features that is required with externalization like Loadbalancing (which you don't have automatically in bare metal installations).
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/service/

/remove-lifecycle stale
/lifecycle frozen

@sftim Will #14526 address this? If not, can I work on this?

PR #14526 will help, I hope. There's yet more to do afterwards. I think the main page about the Service concept should talk less about implementation details like AWS load balancers, and more about different ways of handling ingress (eg Ingress, Istio, Gloo).
Because #14526 is a big set of changes, I think it makes sense to build on it once merged.
@palnabarun you could sketch out (in your mind, on paper, using Git, whatever) what that documentation might look like in the future, even before #14526 is ready to merge. Does that sound alright?

/language en

@sftim Sure. I would make a note of it.
What I felt is, right now as a temporary measure we can add the reference to Ingress and Ingress Controller in the Service documentation so that readers get pointed to the right direction and learn more about it.

How about closing this in favor of #14770?

Sure. We can track about refactoring the Service documentation on #14770

/assign
/close


Updated createStore.ts

name: "\U0001F4DD Documentation Fix"
about: Fixing a problem in an existing docs page
Checklist

[ ] Is there an existing issue for this PR?

_https://github.com/reduxjs/redux/issues/3725_

[ ] Have the files been linted and formatted?
Yes

What docs page needs to be fixed?

Section: NA
Page: NA

What is the problem?
A broken link is being displayed in the error message.
What changes does this PR make to fix the problem?
The PR changes the broken link to the correct one.

Thanks!


"container.v1.ClusterManagerClient" methods returns an "Operation" which is not resolvable to a promise, contradicting the docs.

Environment details

OS: macOS 10.15.7
Node.js version: v12.18.4
npm version: 6.14.6
@google-cloud/container version: 2.2.0

Steps to reproduce

Given this async function:

const container = require('@google-cloud/container');
const client = new container.v1.ClusterManagerClient();
const {
  PROJECT, ZONE, CLUSTER, POOL,
} = process.env;
const config = {
  projectId: PROJECT,
  clusterId: CLUSTER,
  zone: ZONE,
  nodePoolId: POOL,
};
const turnOffCluster = async () => {
  const [operation] = await client.setNodePoolAutoscaling(
    { ...config, autoscaling: { enabled: false } },
  );
  await operation.promise();
  await client.setNodePoolSize({ ...config, nodeCount: 0 });
};
turnOffCluster();

When the function is executed an error is thrown:

(node:58270) UnhandledPromiseRejectionWarning: TypeError: operation.promise is not a function
Expected behaviour
The operation.promise() should return a promise as it is specified in the documentation https://googleapis.dev/nodejs/container/latest/v1.ClusterManagerClient.html#setNodePoolAutoscaling
We need that in order to be able to wait until the autoscaling is completely applied to later be able to resize the pool to 0.

@miguepintor thanks for the bug report, we'll need to dig into this.

Hi @bcoe
typeof operation
'object'
operation.constructor.name
'Object'

clusterConditions:(0) []
detail:''
endTime:''
location:''
name:'operation-1624954448276-0351e3b8'
nodepoolConditions:(0) []
operationType:'UPDATE_CLUSTER'
progress:null
selfLink:'https://container.googleapis.com/v1/projects/000000000000/zones/europe-west1-b/operations/operation-1624954448276-0351e3b8'
startTime:'2021-06-29T08:14:08.276695698Z'
status:'RUNNING'
statusMessage:''
targetLink:'https://container.googleapis.com/v1/projects/000000000000/zones/europe-west1-b/clusters/cluster-name/nodePools/preemptible-pool'
zone:'europe-west1-b'
__proto__:Object

Regards

Hi @miguepintor,
Thanks for submitting this bug. After investigating, it turns out that this library was created before we implemented the proto annotations for long-running operations. The documentation you cited does not apply to this library given its age. Implementing these standards would require a breaking change, so instead we're going to update the samples appropriately to use these operations.
We have an internal bug filed for this, this should be fulfilled by September.
See https://github.com/googleapis/python-container/issues/3 for more details.


#14817 fix parameters not being deleted

The reason why they were not deleted is that dialog acted preserved previous values in its static variable and rewrote them every time OK was pressed

Please double check with named parameters (:name), anonymous parameters (?) and variables (${name}).
Variables must be visible across all scripts and must be visible in dialog. Editor reopen or DBeaver restart mustn't break this behavior.


CanvasItem.draw_line() width depends on display resolution

When drawing lines in Node2D using draw_line() function, the line width seems to be in display pixels instead of node coordinates.
Line drawn with same width looks a lot wider on low DPI desktop than on high DPI Android device. Positions of lines work as expected.
I can fix this by multiplying the line width by get_viewport_transform().get_scale().x, but shouldn't the function take the line width in same units as the positions?

I tried this in the current master branch and it seems to behave fine as far as I understand (I don't have a HiDPI display to test, but I used a tool script to draw in the editor directly and changed the editor DPI scaling).
Test project:
draw_line_width.zip
Closing as it's an old issue and might no longer be relevant now, but please comment if I misunderstood the issue and you can still reproduce it.


about deepspeed

I have question about deepspeed. Assuming that we did not use DeepSpeed in our code initially, if we now want to use it in our fine-tuning process, do we just need to call it in the run_finetune_with_lora.sh script? Are there any other files that need to be modified? Thanks~

Thanks for your interest in LMFlow! You may run ./run_finetune_with_lora.sh first, which uses alpaca dataset and galactica-1.3b by default. To use your own dataset, you may provide your own dataset in {path-to-your-dataset}/*.json, with "text_only" typed format for those json files. Then changing
--dataset_path {path-to-your-dataset}

in this line will specify the dataset.
If you would like to change model, you may change the base model with
--model_name_or_path {a-huggingface-model-or-path-to-your-own-model}

where a model name provided by huggingface models or a local path to a model (can be a previously pretrained model) is specified here.
Hope that answers your question. Thanks 😄

This issue has been marked as stale because it has not had recent activity. If you think this still needs to be addressed please feel free to reopen this issue. Thanks

deepspeed: error: unrecognized arguments: --dataset_path


:seedling: add querying options to list and watch

Summary
Related issue(s)
Fixes #

/assign @qiujian16

/hold

/unhold


How to install pluralize in production environment?

Also, Is it free?

It’s in the README and LICENSE, standard for software practices.


Data races

Commander has races in ensureDockerClient and around the workerChans map.

will be fixed in PR #250


test: add cases for hedge-price usage

Discussion
This PR is to start adding a set of test cases to ensure our use-cases are configured properly with the dealer conversion functions they use for different pathways.

not sure if worth it but we can add a helper file for diff and amount to earn/spend functions

I would usually only do this if the functions were going to be used in more than 1 file. Do you think it makes sense here since we're using only in these tests?


Number of boxes

Dear author, thanks for your excellent work. May I ask how many boxes are in RF100? Thanks!

Hello @yhcao6! We have not calculated the total number of boxes in the benchmark, however, there was over 11,170 hours of labeling involved in the user creation of these datasets.


Add /donate page and DAF integration

WIP
Build preview: https://os-website-git-donate-daf-open-sats.vercel.app/donate

This still needs quite a bit of work, let's make sure the content is top-notch before we update & finalize this PR.
The text can be improved by quite a bit, and there's some typos too, e.g:

Make sure to use Grammarly or similar to catch those little things @Arvin21M

Google Doc version of the Navigating Donations article/page here: https://drive.google.com/drive/u/1/folders/1OyYMmSSWK6Fg0PcJnFkLCFJeztB0bzIt?ths=true

@dergigi sharing a quick relevant note from group chat today with @cfunk7777:
Look into having a direct link to the donation form for each respective fund/project to make a shorter path from click to donate for users.

I've implemented @cfunk7777's suggestion just now, defaulting to the General Fund.
I'll do my best to have another go at this, i.e. review & edit the blog post and write the rest of the /donate page so we can push all of this live. (Have to get payouts done first, though.)

I've decided to move the blog post to its own pull-request, see:

https://github.com/OpenSats/website/pull/198

This way we can merge the other changes quicker, potentially.

I will merge this now as-is, because I need the /donate page for https://github.com/OpenSats/website/pull/203


Update code completion sorting priority so that Silk components appear before compose components

One user mentioned that the Compose ones always show up before the SIlk ones which they usually don't want. If it's possible to influence the ordering / scoring of the code completion list, we might want to bump of stuff under the com.varabyte.kobweb package

No idea if this is possible yet. It is a reasonable first step to investigate the IJ APIs and close this as not possible if, well, it's not possible.


Update librdkafka to 1.5.2 and kafkacat to 1.6.0

What's this PR about
I've updated librdkafka to 1.5.2 and kafkacat to 1.6.0.
TODO's:

[x] Run perfecto check on your spec file
[x] Write bibop tests
[x] Enable "Allow edits from maintainers" for this PR
[x] Update the messages below

Did you try to build the package with this spec?: Yes
Is this ready for review?: Yes

Looks good, merged. Thanks!

Packages were built and added to kaos-testing repository.


Build server can't build with tests at net6.0

Currently, the build server fails if the tests use net6.0, likely because its Docker image uses Mono, which imitates net4.7.2.
We should figure out a way to fix this, maybe:

Add a step to fetch net6.0 and build using that?
Figure out why the tests need to be on net6.0, and find a way to go back to net4.7.2
Something else?

@JimOfLeisure had mentioned some interest in this

This wound up being a semi-blocker to copying all the assets at once.  So, I'm looking at it now, with TheOrioli's solution.  Seems to be working.  Now trying to DRY out the configuration.


PC Tokens Indistinguishable

Assign any distinct token art for each Actor's default Token.  Alternatively (think both makes most sense) configure PC Tokens to display name.

done


BAZEL CI TESTS ON ORIG

Do not merge, I just want to run CI with our credentials

Tests are done. Bazel CI + Docker + Bats has been merged in main in #295


impove name, def for G2 cell size control checkpoint

G2 cell size control checkpoint
current
Definition	A cell cycle checkpoint that monitors cell size, and negatively regulates cell cycle progression between G2 and M phase until a critical size is reached.
rename to
mitotic G2 cell size control checkpoint
(currently exact synonym)
Def
A mitotic cell cycle checkpoint (signaling network) that monitors cell size, and negatively regulates cell cycle progression between G2 and M phase until a critical size is reached.
A DYRK family protein kinase (Pom1  in pombe) forms a spatial gradient and acts as an inhibitor of mitotic entry. As cells increase in size, DYRK kinase levels decrease at the cell division site, leading to mitotic entry. The DYRK spatial gradient and the medial cortical nodes generate information about cell size and coordinate this with mitotic entry by regulating Cdk1 through other mitotic inducer kinases and Wee1.
(I made this def as generic as possible, but so far there is no annotation from other species, I presume the mechanism is conserved when a G2 cell size control checkpoint exists, can be revised if not, but should prevent inappropriate use)
Original papers for the mechanism co published in Nature back in 2009:
PMID:19474789 A spatial gradient coordinates cell size and mitotic entry in fission yeast.
Moseley JB, Mayeux A, Paoletti A, Nurse P
PMID:19474792 Polar gradients of the DYRK-family kinase Pom1 couple cell length with the cell cycle.
Martin SG, Berthelot-Grosjean M

Since it is defined between G2 and M, isn't it necessarily mitotic? I don't think it occurs before meiosis does it?

It is necessarily mitotic from the position,
but meiosis has G2 and M (http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0051327)
can mean meiotic phase as well as "mitotic phase" it seems?
I have no idea yet if there is a cell size checkpoint in during meiotic  G2 before meiotic M-phase
but if there is, this would also fit the term name G2 cell size control checkpoint. I think it would be better to clarify ...


Bugfix/bgid push sigchld race

I made a new PR with name better matchign what this does (add logs): https://github.com/pantavisor/pantavisor/pull/385


Vet python code

Minimum vetting process has occurred, enough to merge changes since an end-to-end test currently works.


Add http scheme

grpc exporter  and receivers not required http scheme.
exporters:
  otlp:
    endpoint: otelcol2:4317

but,http exporter
required URL scheme.
exporters:
  otlphttp:
    endpoint: https://example.com:4318

why did I see any telemetry before?

why did I see any telemetry before?

tried it myself


POSTing to the root (Transaction/Bundle)

Do you want to request a feature, improve documentation, or ask a question?
Ask a question
Are you reporting a bug?
No
What is the current behavior?
Trying to POST a transaction Bundle to the root, keep getting a OperationOutcome - > "Invalid URL : /"
Question is simply, does this implementation have the capacity to POST transaction Bundles to the root url? Is this something I need to enable somehow? If so, is there documentation on how to do so?
What is the expected behavior?
What are the steps to reproduce?
What OS are you using and what version of node.js, @asymmetrik/node-fhir-server-core, and @asymmetrik/node-fhir-server-mongo are you running?

Hi Isaac,
The short answer is that batch/transaction behavior is not currently supported in this implementation.
The reason that you're getting an "Invalid URL" is that there is no express route for the root location in the current release of node-fhir-server-core, which this implementation is built upon.
According to the FHIR spec, batch and transaction operations are 2 different things, where batch is treated as a bunch of independent operations that succeed/fail independently and a transaction is one big bulk operation that either completely succeeds/fails. Supporting transactions on mongo may be a bit trickier, as it will involve using replica sets. However, supporting batches is more straightforward.
To add support for batch operations, we would need to add base/root routes and controllers to node-fhir-server-core and then a batch service here in node-fhir-server-mongo. We'll add it to our backlog, but feel free to add it in yourself if time is of the essence!
Thanks,
Sumeet

Hi Isaac,
Just an update on this, I've done some work on supporting batch operations. While I still need to write out the unit tests and whatnot before merging in, the support for batch operations has been added to node-fhir-server-core. Changes to node-fhir-server-mongo are not actually necessary to support batch operations.
These changes will propagate into master and the main branch once they have been fully tested and reviewed. Until then, the changes can be seen in the PR at https://github.com/Asymmetrik/node-fhir-server-core/pull/184.
Thanks,
Sumeet

Closing stale request. Please comment if this is still relevant


feature: allow searching by ISO code

I was missing a way to quickly search a country by ISO code, e.g. "US" for United States, or "DK" for "Denmark".
This PR enables that functionality.
And oh, thanks for a super sweet library. Well done! I've been wasting too much time today trying 3-4 different libraries and trying to customize them to my needs, only to find this is by far the best library for Flutter out there.

Thanks a lot for the kind words. ⭐


Framework 16 Support

Now that the Framework 16 is shipping, it makes sense to add a profile for it as well :3

I have my FW16 and would be happy to contribute. If there are submission guidelines that I can review please point them out to me.

I have my FW16 and would be happy to contribute. If there are submission guidelines that I can review please point them out to me.

I recommend just looking at the Framework folder and copy the style/semantics of that and if you have any other question ask it in the Matrix chat :)

@nyabinary ^^


Slots without blocks will be missing from the dataset

Due to the underlying data structure slots without blocks will not appear in the current query result sets. Initially this was implemented but presented a significant performance tax when joining objects to a view already derived from a recursive CTE.
This is an important domain-specific query relating to Stake Pool performance, so while a natural query expression of:
{
  Slot(where: {block: {id: {_is_null: true}}}) {
    number
  }
}

...will return no results, a specific query for stakePoolPerformance can be implemented without compromising performance, and provide greater value to the consumer

No longer relevant


Consul ACL custom resource

Not sure where an ACL custom resource is at this point.  Looks like there were some PRs to add ACL resources, but they were closed for various reasons.  Is there currently work in progress?

+1, we might need this shortly, would love to know either way.

I'm open to accepting custom resource for ACL.

The previous attempt in #220 seems to have halted due to a gem?


API Calls and more

Added spotify token and sign in values to local storage, and retrieval
Added a search form on the popup-signed-in to allow for quick search
Added an API call to the spotify server asynchronously, and added a message callback on the frontend
Parsed JSON into a table format. Beautification need
Added some documentation
Formatting of various JS and HTML files

Aligned theme with Spotify, and add search bar animations (Trust me, they're impressive)
Remove unnecessary code referenced in the previous commit
Moved css to dedicated stylesheet folder
Added Font: Gotham, as used by Spotify

Love what you've done with it! Thanks Saif 🥳


Android does not load image from albumart

Great library. I just have one problem i cant use the library to show album art from android media store.
A uri like this
content://media/external/audio/albumart/58

I tried your example using this uri
import FastImage from 'react-native-fast-image'

const YourImage = () =>
  <FastImage
    style={styles.image}
    source={{
      uri: 'content://media/external/audio/albumart/58',
      headers:{ Authorization: 'someAuthToken' },
      priority: FastImage.priority.normal,
    }}
    resizeMode={FastImage.resizeMode.contain}
  />

An solution?

Content urls are now handled in the latest version.

@DylanVann ^4.0.6?


Implement saving of the best model after each iteration of composier

Now, the final chain only is saving is JSON. However, the intermediate output during composer execution can be useful for the analysis of the results.
The temp folder can be used for storage.

Implemented


fix: Fix TypeScript errors in CLI (CDMD-2584)

lets close this stale draft.... @r4zendev

@alexbit-codemod i'll keep it for reference, this is on my radar for current/next sprint (CLI refactoring), could help getting started.


Replace EnergyDervativeModel by function transformation

both the energy dervative and shallow ensemble class do not add extra state to the model. They could thus be replaced with function transformations. This would make the parameter handling easier (make canonicalize_energy_model_parameters obsolete) and make the code more "jaxonic".

on second thought, this might make a few things more challenging


Wrong storage hash key for storage value

In our generated code we have this:
  final _i1.StorageValue<int> _endorsementTicketsPerBootstrapper = const _i1.StorageValue<int>(
    prefix: 'EncointerCeremonies',
    storage: 'EndorsementTicketsPerBootstrapper',
    valueCodec: _i4.U8Codec.codec,
  );

The generated key hash:
    final hashedKey = _endorsementTicketsPerBootstrapper.hashedKey();

    // hashedKey: 0xa7d291a8132b2cc65c41da45f4de76796ae3d97cb4a9938c6ebddc6491b5bc06
    print("hashedKey: 0x${hex.encode(hashedKey)}");

Is wrong, the correct key hash according to polkadot-js/apps is:

So the method is wrong in this case, whereas the prefix is correct. The method has 33 characters, so my guess is that some magic happens on substrate side for prefixes > 32 bytes.

Ok, found the issue it is in the xxh64 algorithm actually (that is used by twox). cc @justkawal

Fixed on version 0.2.4

I can confirm that it is fixed on our end. Thanks for the blazingly fast fix!

I have to correct my statement, the hash seems to be wrong in other cases now, example:
  final _i1.StorageValue<_i3.CeremonyPhaseType> _currentPhase = const _i1.StorageValue<_i3.CeremonyPhaseType>(
    prefix: 'EncointerScheduler',
    storage: 'CurrentPhase',
    valueCodec: _i3.CeremonyPhaseType.codec,
  );

// wrong result:
// 26dc3fa0a77526a8494180a4789f6883d9764401941df7f77a47ba7db64a6e0a
// actual value:
// 26dc3fa0a77526a8494180a4789f6883d9764401941df7f707a47ba7db64a6ea

Actual value:

It only seems to affect the last bytes.

It seems I can't reopen the issue unfortunately. Shall I create a new one?

They are pretty close though haha. Seems people are not really good at making hashing algorithms. I wish dart itself had them. I will check it later.

Totally my fault this one. When converting to hex it did not use signed 2's complement. It should be fixed now, also added this string to the tests.

Released under version:
polkadart: ^0.2.5

Nice, our integration tests work again, seems to be fine, thanks a lot for this quick reaction again! 👍


some minor fixes

change from js to diff code blocks in migration docs
readability English docs
add some links to references

⚠ That workflow shouldn't attempt to deploy the docs built for testing. It naturally fails due to me not being authorized to push to your repo.

⚠ That workflow shouldn't attempt to deploy the docs built for testing. It naturally fails due to me not being authorized to push to your repo.

thanks, I also found this problem.

if you need help, let me know

Welcome PR
Maybe:
PR -› test the build
push master -› build and deploy

Ok, I am busy now. Will give it a try later today.


Customize border rounding on tooltips separately from windows

Description
At the moment, decoration:rounding affects both tooltip's and window's borders. However, there are cases where tooltips are intended to be rectangle-shaped, with borders being drawn inside of tooltip area.
I think there should be a way to set border rounding on tooltips separately. Even though tooltips aren't windows, I think a windowrule-like approach would suit them.

Okay, I may also need to clarify that it affects vscode's tooltips, GTK ones seem to be unaffected

It's running wayland. Reopen the issue.

Here are the screenshots demonstrating the issue. You either get all windows with rounded borders or none

I did break it then, but it's your fault

can you git bisect this

I'm sure this is a really old bug, pretty sure it was happening all the way back during v0.26

I'll try bisecting though

nah no way, I just noticed this.

Earliest release I could compile is v0.29, still happens there. v0.28 wont build

Nvm, something was wrong on my side. v0.28 builds, but the issue is still there

I swear, it happened in v0.26 too. I may not be able to test it now, but going that far back is impossible with git bisect, as I cannot build past v0.27.

You could try the binary releases, it wouldn't be able to point to a specific commit, but can give you a range.

fixe d 3b1e09e5a18bd1cf137f8f50394aa0c1eaac1e30


Update overview-data-governance.md

cleaned up grammar

@kjpoulton : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@WendyRing: I'm sorry - only the author of this article, @mboswell, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Calculating the angle

in the gestures state attributes, I didn't find an attribute that gives the current angle of the component from its initial position, so is there a way to get the angle that I am missing? and if not, are there plans to add it in the future?
I am willing to make a PR adding the angle attribute if it's not already implemented.

angle sounds very interesting! if @dbismut didn't add it already please make a PR!

What's the typical use-case for this? With initial and movement it should be pretty straightforward to implement it in user land? Unless you want to also count the number of full 360 turns?

The use case that I had in mind is when dragging a component I want it to rotate based on the angle it has from the origin.
something that is similar to this codepen: https://codepen.io/aaroniker/pen/mNWQyM

so is this a valid use case so I can start on the PR or should we leave it for the user to calculate it?

Sorry @hazem3500 I'm currently on holidays and should be able to reach out to a proper wifi tonight. Will let you know by then. Thanks for your patience.

@dbismut no problem, enjoy the holiday 😄.

Hey @hazem3500 just had a look at the codepen, which is a bit different that calculating angle from the origin right? If just the angle matters then I think it's just a one liner and I wouldn't make the API more complex for a use case that is a) uncommon b) simple to address in user land. Happy to discuss this further though, maybe this is less trivial than I think!

Closing because of inactivity. Feel free to continue the discussion here if needed.


High-Order function helper

I find myself wanting to write functions of the form f -> g -> * -> f(g(*)). This is helpful when you want a high-order function to wrap a function and alter the result when its called. Much like a high-order compose function. Kind of like the opposite of the way memoize works because this function only alters the result.
R.hof = R.curry (f, g) -> (args...) -> f(R.apply(g, args))

# for example
wrapValue = R.hof (value) -> {value}
a = wrapValue -> 1
a()
# => {value: 1}

High-order function might not be the proper term here either.... what do you think?

The type of S.compose is (b -> c) -> (a -> b) -> a -> c, which vaguely resembles your f -> g -> * -> f(g(*)). I'm not clear as to what you're trying to achieve, though. Could you elaborate?

I just realized R.map does precisely this:

Map treats also treats functions as functors and will compose them together.

This was the goal:
coffee> a = -> 10
[Function]
coffee> b = (value) -> {value}
[Function]
coffee> R.map(b, a)
[Function]
coffee> R.map(b, a)()
{ value: 10 }


Make Evaluators plugin work with ESM

Fixes Issue #130
Also fix minor bug in maliciousness.

Can you please double check that it still works properly with CJS?

Yup, I tested it using the DevUI. Works!


Slim syntax highlighting not working?

Hi, syntax highlighting doesn't work for my Vundle set up. Does it only happen for me or everyone? Thanks in advance.
Here is my vimrc
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()

" let Vundle manage Vundle, required
Plugin 'gmarik/Vundle.vim'
Plugin 'kana/vim-textobj-user'
Plugin 'nelstrom/vim-textobj-rubyblock'
Plugin 'kien/ctrlp.vim' "Ctrl + p to find your file
Plugin 'tpope/vim-repeat'
Plugin 'tpope/vim-dispatch'
Plugin 'tpope/vim-surround'
Plugin 'vim-scripts/tComment'
Plugin 'ervandew/supertab'
Plugin 'jiangmiao/auto-pairs'
Plugin 'mileszs/ack.vim'
Plugin 'ngmy/vim-rubocop'
Plugin 'slim-template/vim-slim'

" Auto-save
Plugin 'vim-scripts/vim-auto-save'
let g:auto_save = 1
let g:auto_save_in_insert_mode = 0
" Disable auto-save in Python
autocmd FileType python let g:auto_save=0

" For polygloting programming
" Plugin 'sheerun/vim-polyglot'

" Ruby Plugins
Plugin 'tpope/vim-rails'
Plugin 'vim-ruby/vim-ruby'
Plugin 'tpope/vim-endwise'
Plugin 'jgdavey/vim-blockle'
Bundle 'thoughtbot/vim-rspec'

" Multiple Cursors
Plugin 'terryma/vim-multiple-cursors'

" File Browser Plugin
Plugin 'scrooloose/nerdtree'
let g:NERDTreeShowHidden = 1
let g:NERDTreeMinimalUI = 1
let g:NERDTreeAutoDeleteBuffer = 1

call vundle#end()            " required

syntax enable
filetype plugin indent on

However adding this line makes it work.
autocmd BufNewFile,BufRead *.slim set ft=slim

May I know if it's a bug or because of my set-up? Thanks.

also had to add ´´´autocmd BufNewFile,BufRead *.slim set ft=slim´´´ to get it working

ditto on: autocmd BufNewFile,BufRead *.slim set ft=slim


Reuse reconstruction columns slice to reduce allocations

Create an internal method on Schema to reconstruct a value, passing in a [][]Value to use as columns. Use this internal method, rather than Reconstruct, when reading rows in GenericReader.
Calling Reconstruct on every row being read, and constructing a new [][]Value, in aggregate, accounts for the majority of allocations while reading parquet files and induces an unnecessarily large GC overhead.

Test code used to identify issues
test.parquet is a 768MB parquet file with 32M records.
type TestStruct struct {
	Field1 int64
	Field2 int64
	Field3 int64
}

func main() {
	entries := make([]TestStruct, 1024)
	inFile, err := os.Open("test.parquet")
	if err != nil {
		log.Fatalf("failed to open parquet file: %v", err)
	}
	pr := parquet.NewGenericReader[TestStruct](inFile)
	for {
		_, err := pr.Read(entries)
		if err == io.EOF {
			break
		} else if err != nil {
			log.Fatalf("failed to read parquet entries: %v\n", err)
		}
	}

	f, err := os.Create("mem.pprof")
	if err != nil {
		log.Fatalf("failed to open file: %v", err)
	}
	defer f.Close()
	if err := pprof.Lookup("allocs").WriteTo(f, 0); err != nil {
		log.Fatalf("failed to write heap profile: %v", err)
	}
}

Profile output (before change)

Profile output (after change)

Apologies to make more work for you, but we've decided to move development on this project to a new organization at https://github.com/parquet-go/parquet-go to ensure its long term success. We appreciate your contribution and would appreciate if you could reopen this PR there if it is still relevant.


Timer related custom alerts

I was thinking it would be neat to be able to add custom alerts related to different timer effects that are being tracked.  Perhaps there could be a button on the alert that if you select
could lead you into creation of a custom alert for it where you could also enter a time value such that the visual/audio custom values you put in for it go off the time value you enter prior to the expiration of that timer.  Possibly also having input option against it for just yourself or to include others.
e.g.
You Levitation 1 minute offset warns me a minute prior to expiration.
You mod rod consumed no time offset just tells me my mod rod is ready.
Some random respawn timer i'm interested in have it tell me audio alert 30 seconds prior to respawn.

This is something that I'd like to do, I just have to figure out how the hell I'm going to accomplish it.
I'd like the timers to feel more useful than just as a timer. Things like having a voiceover for when something hits 30 seconds remaining, etc, are definitely on the docket.
It'll likely be after June, however.
The Great Hatching™ approaches, and I have a Lizard to level!


Calenar Localization

Hi I am trying to Setting localization.
In the calendar weekdays options &  monthPickerFormat work. But how can i change the localization on the actual month shown for the month picker ?
i.e FEB 2018
You have the option to set the format but how do you set the localization?
monthFormat | string | 'MMM YYYY' | month title format
Thanks
Dimitri

Yes. Same problem here.
I put the following code in my app.module.ts:
import {registerLocaleData} from '@angular/common';
import localeCa from '@angular/common/locales/ca';
import localeEs from '@angular/common/locales/es';
import localeEn from '@angular/common/locales/en';
import localeFr from '@angular/common/locales/fr';

registerLocaleData(localeCa);
registerLocaleData(localeEs);
registerLocaleData(localeEn);
registerLocaleData(localeFr);

@NgModule({
    declarations: [...],
    imports: [
        ...
        CalendarModule,
        ...
    ],
    bootstrap: [...],
    entryComponents: [...],
    providers: [
        {provide: LOCALE_ID, useValue: "es"} // could be 'es', 'en', 'fr' or 'ca'
    ]
})

Then, if I test with simple localized Angular Pipe...
<p>{{today | date:'fullDate'}}</p>
... the output appeaers localized in spanish (es), BUT MY CALENDAR PICKER IS STILL IN ENGLISH =>  "February 2018".

I think the problem is that you are not using angular date pipe to localize month names. You are using moment format function.

This works for me to localize months @dmpour23 :
import {Component} from '@angular/core';
import {Platform} from 'ionic-angular';
import {StatusBar} from '@ionic-native/status-bar';
import {SplashScreen} from '@ionic-native/splash-screen';

import moment from 'moment';
import 'moment/locale/es';

@Component({
    templateUrl: 'app.html'
})
export class TaxApp {

    rootPage: string = "HomePage";

    constructor(platform: Platform, statusBar: StatusBar, splashScreen: SplashScreen) {
        platform.ready().then(() => {
            statusBar.styleDefault();
            splashScreen.hide();

            moment.locale("es");
        });
    }

}


Integrate bit-banged i2c for BNO08x IMU

The built-in Raspberry Pi i2c controller does not support clock stretching, which is required by the BNO085.  v2 and v2_1 code used the built-in controller.  The IMU reports successfully most of the time, but there are occasional bad data points which are clear outliers in the quaternion stream.  Our working theory is that these bad data points result from an i2c comm error associated with the lack of clock stretching.
As a fix, we are looking at the pigpio library bit-banged i2c API.  Peter N. has written code to utilize this API, but it needs to be integrated and tested with the main Tag recording application (cetiTagApp).

Peter N's implementation was integrated and tested.  IMU behavior on the bench is as expected.  Closing the issue.


Review the results once more

Making small touches to the text to make sure we don't miss anything.

Has the commits from #161 for now. Will rebase once that is merged.

@santisoler finished the results but couldn't get to the discussion in time, sorry.
I made some tweaks to the figures and the text but again nothing major. Feel free to make any changes you see fit and merge when ready!
I'll finish this off as soon as I get back from vacation (or sooner if I get bored 🙂).

@santisoler finished the results but couldn't get to the discussion in time, sorry.

Thanks! Don't worry for the discussion, we can do that later.

I made some tweaks to the figures and the text but again nothing major. Feel free to make any changes you see fit and merge when ready!

:+1:

I'll finish revising as soon as I get back from vacation (or sooner if I get bored slightly_smiling_face).

I forbid you. I won't merge any PR you make until you come back from the vacations. And I'll be watching commit datetimes on any PR you open later on :eyes:

TODO:

[ ] Change back to viridis
[ ] Crop colorbar in random vs sequential figure

@santisoler I reverted the cmap back to viridis, made the cmap of the random vs sequential figure the same as the difference figures, and made the Australia CV figure into a single column instead of full width. See what you think and if you're happy, then please merge away. I'll look at the discussion in another PR.

Awesome! I'm merging this! Thanks a lot!


Action_msgs not findable, because of relocation from /ros_ws/install/action_msgs/share/action_msgs/rust to /ros_ws/install/share/action_msgs/rust/

Since this error is relatively new, I wanted to show it. So colcon tries to find the action_msgs when building my package and searches incorrectly.
--- stderr: simple_ros_rs
error: failed to load source for dependency `action_msgs`

Caused by:
  Unable to update /ros_ws/install/action_msgs/share/action_msgs/rust

Caused by:
  failed to read `/ros_ws/install/action_msgs/share/action_msgs/rust/Cargo.toml`

Caused by:
  No such file or directory (os error 2)
---

As you can see, it looks for the library in the /ros_ws/install/action_msgs/share/action_msgs/rust path, where it can't find it. Actually, the library is in the path /ros_ws/install/share/action_msgs/rust/.
The comand, with whicht I'm building my packages is colcon build --continue-on-error --build-base /ros_ws/build --install-base /ros_ws/install --base-paths /ros_default /ros_ws /microros_ws --merge-install

So actually the colcon flag --merge-install makes the dependencies appear in install/share/ folder instead of directly in /install folder, which leads to confusion when building. If I see this correctly, the whole thing is rather a bug of cargo-ament-build than of colcon directly.

This is intended, Rust source files are installed into the share directory. Did you run this on a clean workspace or did you reuse an existing one?

That was a clean installation. I know now how the --merge-install flag works. I just didn't realise that -cargo-ament-build couldn't handle it.


Performance fixes - SynchronizedMap work with read-write lock, decrease partition table copy cost

Decrease partition table copy cost. Make SynchronizedMap work with read-write lock.
Decrease partition table copy cost.

Linux test FAILed.

Windows test PASSed.

verify-linux

Linux test FAILed.

closing for now. To be done in the future.


[Bug] the value returned from PlutoCell().value is different than the original value

Steps to reproduce the bug:
1.Create a pluto grid with a date column using format PlutoColumnType.date(format: 'dd/MM/yyyy')
2.Select the row
3.if you try to use the value from event.row!.cells['column']!.value it will be a string, not a date
Expected results
A DateTime instead of a String (this probably will happen with money and number)
Actual results
A string is returned:
row value
09/02/2022
is String?
true
is Datetime?
false
---------------------------------------------------------
true value
2022-02-09 00:00:00.000
is String?
false
is Datetime?
true

Code sample
value.zip
Execution Environment
Flutter version
Channel stable, 3.3.9
PlutoGrid version
PlutoGrid - v5.4.6
OS
Web

As this seems like intended behavior, it would be nice if row!.cells['column'] had two getters:
one for the original value and one for the value presented on the grid (formatted or with custom render)

@bosskmk any updates?

@bosskmk any updates?

Resurrecting

👀

💀

.

.


Location of klujax and grad-able solves with KLU

Sax looks like a very interesting and useful package!
I was wondering where the code for klujax is located, since it doesn't seem to be part of sax.
Additionally, as I was reading the docs on the KLU backend, I was surprised to learn that the backend does not support gradients. If I understand the approach correctly, the calculation is a combination of matrix multiplications and a linear solve (using klujax). The gradient for the linear solve operation should just involve another linear solve, meaning that you should be able to define the gradient rule for JAX to make another call to klujax. Am I missing something?

Thanks @ianwilliamson ,
klujax is not yet open source, but will be very soon! (I just started the internal review process within my company)
I agree... It should be fairly easy to implement autograd on a linear solver. In fact, I have done this before for my PyTorch solver. The main reason why I haven't done this yet for klujax is basically laziness: I didn't really need it yet so far... for many of the optimization problems I'm using a smaller circuit anyway which can easily be modeled with the default backend.

Hi @ianwilliamson ,
klujax is now open source. Feel free to open an issue (or PR 😉) for autograd there!
closing this here as the discussion can be continued on the klujax repository.


Wait for correctly labelled pods to be ready

Type of change

Bugfix

Description
Check for application-monitoring pods wasn't working because only pods labelled app:enmasse are checked. This PR allows the labels to be passed as a parameter instead of being hardcoded
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=acceptance testcase=MonitoringTest ocp4

:x: Test Summary :x:
TEST_PROFILE: acceptance
TEST_CASE: MonitoringTest
TOTAL: 14
PASS: 11
FAIL: 3
SKIP: 0
BUILD_NUMBER: 1402
BUILD_ENV: crc
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testAddressSpaceRules in io.enmasse.systemtest.isolated.monitoring.MonitoringTest
testAddressQueries in io.enmasse.systemtest.isolated.monitoring.MonitoringTest
testMonitoringCommonQueries in io.enmasse.systemtest.isolated.monitoring.MonitoringTest


Remove library copy in csproj

resolves #393

@NemrudDemir
Hello!  I just wanted to let you know that the code changes themselves are just fine but there are other things that need to be done. 😃
So first thing is to give you some resources.  If you go to the main project page here, you will see the main README on this page.  If you scroll down to the contribution section, you will see some basic steps on how to contribute.
Here are some resources:

README
Branching Docs

Scroll down to the Feature Branches and Preview Feature Branches sections.  These are the only branches that outside contributors need to worry about.  Currently, we are in preview so you only have to worry about the Preview Feature Branches section for this PR.

Join and become a member of the discord server.

This is also a great place to contact me and get questions and clear things up.  I am very available since I do this full time.

Things That Need Changing:
Due to the CICD requirements and standards put onto the project, there are some things that need to be done if you could please.

The branch name needs to be a preview feature branch.

A branch name with the correct syntax is required.  Preview feature branches look like this 👉🏼 preview/feature/-

Good example 👉🏼 preview/feature/393-remove-lib-copy

The branch needs to be created from the latest preview branch.

Currently, we are in v1.0.0-preview.11
The name of the branch is preview/v1.0.0-preview.11

Use a PR template for preview features

These can be found here
There are 5 different kinds.  For your PR you need to use the content of the file named preview-feature-pr-template.md.  Just copy the content of this file into the main section of the PR when you are creating it.
Unfortunately, though, since your branch name is incorrect, you have to recreate the PR.  This is where you can put the PR template content when you create it.  (If you forget, I can add it after)

Please make a comment on the issue so I can assign it to you.

Quick Note:

Please make sure that when you are wanting to possibly contribute to an OS project, make sure you leave a comment asking if the issue is something you can work on.

This is a good idea for any project.  The GitHub system is designed to not even allow a maintainer to assign the issue to outside contributors unless you make at least one or more comments on the issue.
This is also a good idea because when you comment on issues, the maintainers get notifications.  This is why it took me a while to respond.  I did not even know that there was a pull request out there for this because I did not get a notification and I did not get a notification because you did not comment.

Make sure you take the time to read the project's README files.  This is where projects will always start you off so you can know how to contribute and what the project's special needs are as well as how it is maintained and run.

I hope that helps!!
If you need anything else, don't hesitate to contact me and we can get you started so we can get the PR done in time for the end of hacktoberfest!!
Cheers!!


Update README.md

Old multi-machine link: Page not found.

This PR has been merged into master. Thank you for the contribution!


wget https://huggingface.co/kuleshov/llama-7b-4bit/resolve/main/llama-7b-4bit.pt 404 error

--2023-06-29 21:50:16--  https://huggingface.co/kuleshov/llama-7b-4bit/resolve/main/llama-7b-4bit.pt
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving huggingface.co (huggingface.co)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to huggingface.co (huggingface.co)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-06-29 21:50:17 ERROR 404: Not Found.

Indeed the link https://huggingface.co/kuleshov/llama-7b-4bit/resolve/main/llama-7b-4bit.pt yields "Entry not found". Even checking the repository shows that the .pt file does not exist: https://huggingface.co/kuleshov/llama-7b-4bit/tree/main. I personally had to resort to using the other weights such as https://huggingface.co/kuleshov/llama-65b-4bit/resolve/main/llama-65b-4bit.pt


[BUG] Logs are not displayed in the web ui

Rancher Server Setup

Rancher version: 2.7.4
Installation option (Docker install/Helm Chart):

Helm, RKE2 v1.24.11+rke2r1

Proxy/Cert Details: N/A

Information about the Cluster

Kubernetes version: v1.25.9+rke2r1
Cluster Type (Local/Downstream):

Custom

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:
Admin

Describe the bug

Logs are not displayed in the web ui.
To Reproduce

Go to a pod, select the hamburger menu and 'View Logs'.
Result
Log section pops up and is empty.
Expected Result

Logs are displayed.
Screenshots

Additional context

Clicking 'Download' downloads the logs that I would expect should be displayed in the web ui.

The log display defaults to the last 30 minutes. If the pod has crashed / not logged anything nothing will be displayed.
In the bottom right, you can select the time range to 'Everything'


Added 'exist' param to the 'zadd' method as ability setup NX or XX argument

Added exist parameter to the zadd method as ability setup NX or XX argument.

@mastak pls, merge it, to make green: https://github.com/mastak/aioredis/pull/2

@mastak if you have time try to update from master

@pcinkh
have updated. thanks for the help with tests!

Thanks,


Evaluation Related; Meanings of Metrics in the Output Text File Related;

seq_Smeasure:0.135;seq_wFmeasure:0.095;seq_adpFmeasure:0.041;seq_maxF:0.185;seq_meanF:0.121;seq_adpEmeasure:0.249;seq_maxE:0.627;seq_meanE:0.202;seq_MAE:0.819
Above is one of the lines in the output file, and some pairs have been found in the paper:
Smeasure  ——  4.2.2 5. structure measure
wFmeasure  ——
adpFmeasure  ——
maxF  ——  maximum F-measure
meanF  ——
adpEmeasure  ——
maxE  ——  4.2.2 4. Maximum Enhanced-Alignment Measure
meanE  ——
seq_MAE  ——  4.2.2 mae
However, the meanings of the variables not found are still not clear, could you please help me about this? Thank you sincerely!

Kindly suggest you read original paper carefully. Please see Section 4.2 in https://link.springer.com/article/10.1007/s41095-021-0262-4


codemirror: mustache template

made changes in the codemirror parser to comply with this request in https://github.com/CartoDB/cartodb/pull/11939#issuecomment-292559200

Change the text color to difference the text inside {{}} and the text outside. Maybe we can use the white for the text outside like a “{“

it's much less sophisticated now, so I'm not sure about it, what's your opinion @nobuti ?

/cc @urbanphes

the simpler, the better. I think to show parsing errors is a nice thing though.

yeah, actually there's an ongoing discussion about syntax validation https://github.com/CartoDB/cartodb/pull/11939#issuecomment-293290750
I need to talk to @rochoa about that when he has a minute

Hey guys, what about this PR? can we close it? Should we keep pushing?

it's done, pending feedback and/or acceptance as it changes a bit how moustache strings are validated. They slightly change the color for better represent the template (see attached)

this is prod ^^^


Key Vault keys API: Add OKP key type and EdDSA digital signature

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.

The feature is already deployed to public regions.

When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.

Expectation is to release with the next preview version of the Key Vault data plane APIs.

If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[x] SDK of Js
[x] SDK of Go
[x] PowerShell
[x] CLI
[x] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

@docschmidt can you update your branch with the latest content from main?  I believe that will fix the hanging CI problem.

@docschmidt can you update your branch with the latest content from main? I believe that will fix the hanging CI problem.

Will do.

@docschmidt can you update your branch with the latest content from main? I believe that will fix the hanging CI problem.

@jhendrixMSFT, looks like merging main brought in other issues. Are you aware of a more specific update I should merge? Otherwise does it make sense to merge?

It's going to have to merge with main eventually so it's best to go through the issues and fix what you can. The breaking change policy can be ignored, and will have to. But things like PrettierCheck are typically pretty straight-forward to resolve.

@heaths and @jhendrixMSFT,
I reviewed the failed checks and none of them are under specification/keyvault. Is the expectation still to try to fix those? Wouldn't this trigger reviews from those teams?

When you do, please rebase - not merge - main:
git fetch upstream main
git rebase upstream/main

As I understand it, the problem might be that the target branch (Azure:dev-keyvault-Microsoft.KeyVault-7.4-preview) is too far behind. If that is the case, then rebasing my feature branch will bring in again all these changes from main that may or may not work.
Wouldn't it make sense to rebase Azure:dev-keyvault-Microsoft.KeyVault-7.4-preview first?

From: Heath Stewart @.>
Sent: Tuesday, November 2, 2021 3:18 PM
To: Azure/azure-rest-api-specs @.>
Cc: Alex Schmidt (AZKV) @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Key Vault keys API: Add OKP key type and EdDSA digital signature (#15989)
When you do, please rebase - not merge - main:
git fetch upstream main
git rebase upstream/main
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F15989%23issuecomment-958263603&data=04|01|Alexander.Schmidt%40microsoft.com|c5b9e637e2a143555f0a08d99e4ea218|72f988bf86f141af91ab2d7cd011db47|1|0|637714882907934150|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=In19dhjULNu3mZjtUAH0ikHYi6EpKgW2zY9KW9veRNs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD6QYYKNM4L7XAPTC3XWL2DUKBWSTANCNFSM5DYD3DIQ&data=04|01|Alexander.Schmidt%40microsoft.com|c5b9e637e2a143555f0a08d99e4ea218|72f988bf86f141af91ab2d7cd011db47|1|0|637714882907944102|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3E9Jkl1PFxpGQu09U6PCHy48OKQZPLLu7nz7PizpISE%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Alexander.Schmidt%40microsoft.com|c5b9e637e2a143555f0a08d99e4ea218|72f988bf86f141af91ab2d7cd011db47|1|0|637714882907944102|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2B2fVa0MA0yj2P7OQPQI6zqdXDjpsA9hEZSAOoG7U3nw%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Alexander.Schmidt%40microsoft.com|c5b9e637e2a143555f0a08d99e4ea218|72f988bf86f141af91ab2d7cd011db47|1|0|637714882907954057|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=HkADri5O17iQJJh3c4%2BYeHBO5MX5xgF0W%2B58Oj45GEA%3D&reserved=0.

Actually, I missed this was targeting a release branch. Don't rebase until we're done and ready to merge, or anyone else with outstanding work will be adversely affected.
Looking at the checks, this pipeline did pass but didn't report back status: https://github.com/Azure/azure-rest-api-specs/pull/15989/checks?check_run_id=4002543967
Given that, @lmazuel can you help us merge this?

@lmazuel, gentle ping on @heaths' ask.
Could you please help merge the change into the feature branch?


Workday CloudQuery Plugin

Hi Team, hopefully this is right place to ask, if not, I'd appreciate if you can direct me.
I'm the founder of cloudquery.io, a high performance open source ELT framework.
Our users are interested in a Workday plugin, but as we cannot maintain all the plugins ourselves, I was curious if this would be an interesting collaboration, where we would help implement an initial source plugin, and you will help maintain it.
This will give your users the ability to sync Workday data to any of their datalakes/data-warehouses/databases easily using any of the growing list of CQ destination plugins.
Best,
Yevgeny

Thanks for reaching out.  This is the only repo I'm interested in maintaining at this point.


Basic calendar

The pull request includes a working calendar which is linked to the Eventbrite account. It displays the upcoming live events and the user can click on the event card to have another tab on the browser open with event page.
There are still some features to be added to it, though I wanted to get a working model for the site:

Right now, error handling could be more descriptive as any error-outs will display that it didn't work
There is no loading overlay while the site makes a request out to Eventbrite, and would aid in user experience
The design of the event cards is basic and could be re-design for user experience.

Deploy preview processing.
Built with commit 5e67b87c36a015f25893e53c209eba93a5467d1e
https://app.netlify.com/sites/fcccolumbus/deploys/59e129dcdf995346a8c9daa5

Coverage remained the same at 100.0% when pulling 5e67b87c36a015f25893e53c209eba93a5467d1e on DanStockham:master into 1492fedfdb3878e2b071222a999d08817c924ab3 on FCCColumbus:dev.

Coverage remained the same at 100.0% when pulling 2f444469db24ec9c29cad49667465d9d0bf2e14f on DanStockham:master into 1492fedfdb3878e2b071222a999d08817c924ab3 on FCCColumbus:dev.

I am not sure if this is a good way to go as the secret may become exposed. What are your thoughts on navigating the calendar events logic over to a micro-service on Heroku and then fetching the data from it for the calendar page @DanStockham?

I didn't think about building a micro service for just the calendar. Though
I'm down with building one.
On Oct 18, 2017 7:50 PM, "Justin Woodward"<EMAIL_ADDRESS>wrote:

I am not sure if this is a good way to go as the secret may become
exposed. What are your thoughts on navigating the calendar events logic
over to a micro-service on Heroku and then fetching the data from it for
the calendar page @DanStockham https://github.com/danstockham?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FCCColumbus/F3C_Website/pull/25#issuecomment-337759960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR3bl6ZeX41m9f_fR4yAIc6uEX0byTFks5sto7egaJpZM4P5DMs
.

I would be up for pairing on that idea if you wanted.

Im down. When is the best time for you?
On Oct 19, 2017 12:37 PM, "Justin Woodward"<EMAIL_ADDRESS>wrote:

I would be up for pairing on that idea if you wanted.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FCCColumbus/F3C_Website/pull/25#issuecomment-337965475,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR3btwlpjiJME67dJa4rB1wtR-uuYpRks5st3qxgaJpZM4P5DMs
.

Coverage remained the same at 100.0% when pulling 8cb93a94a176a73fa59972d2b7ac01e75325042f on DanStockham:master into 3eec80f0dcb06afb4ade4ebc39ae8ea70127bca4 on FCCColumbus:dev.

In the deploy preview, you may notice at times that when viewing the calendar page, it seems as if it is taking a little while to fetch the data. This is due to the API being hosted on the Heroku free tier. Since it is so, sometimes it takes a few setups for the api to ramp up due to options that are in the hands of Heroku. It may not be a bad idea to explore next, and I will see if I can ramp up an API on it for a better experience.

Coverage remained the same at 100.0% when pulling 60cf78470928d4491cd29990a78aa2220ceb0421 on DanStockham:master into 3eec80f0dcb06afb4ade4ebc39ae8ea70127bca4 on FCCColumbus:dev.

Changes Unknown when pulling 55d50dda42546a243df9e1b8cf852221a361b040 on DanStockham:master into ** on FCCColumbus:dev**.

Coverage remained the same at 100.0% when pulling cf0aef5c6672ff205551ff4eb39b76e26c8338b3 on DanStockham:master into bf643d07ab643f2e020145b3a82c9fc6bc8288f1 on FCCColumbus:dev.


BUG Server fails to start and crashes in Helix editor

Describe the bug
LSP exits a couple seconds after launching in the Helix editor
To Reproduce
Use the below languages.toml in global or workspace (.helix/) helix folder, change command path if needed, launch helix
Expected behavior
The LSP to launch and respond to requests made by the editor.
Please complete the following information:
OS NAME: GNU/Linux
YARN VERSION: 1.22.22
NODE VERSION: v21.7.1
FISH VERSION: fish, version 3.7.1
FISH-LSP VERSION: 1.0.8

Additional context
I have the install at /home/cat/reference_repos/typescript_fish-lsp/bin/ which includes the fish-lsp binary and is added to PATH
Logs

Helix
Languages.toml

# /home/cat/reference_repos/typescript_fish-lsp/bin/fish-lsp
fish-lsp = { command = "fish-lsp", args = [
  "start",
] }

# Copied from default languages.toml
[[language]]
name = "fish"
scope = "source.fish"
injection-regex = "fish"
file-types = [ "fish" ]
shebangs = [ "fish" ]
comment-token = "#"
indent = { tab-width = 4, unit = "    " }
auto-format = true
# formatter = { command = "fish_indent" }
language-servers = [
  "fish-lsp",
]

Log:
2024-10-01T01:27:09.006 helix_term::application [ERROR] Language Server: Method window/showMessageRequest not found in request 0
2024-10-01T01:27:09.026 helix_lsp::transport [ERROR] fish-lsp err <- "/home/cat/reference_repos/typescript_fish-lsp/node_modules/vscode-jsonrpc/lib/common/connection.js:565\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "                        responsePromise.reject(new messages_1.ResponseError(error.code, error.message, error.data));\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "                                               ^\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "ResponseError: Method not found: window/showMessageRequest\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "    at handleResponse (/home/cat/reference_repos/typescript_fish-lsp/node_modules/vscode-jsonrpc/lib/common/connection.js:565:48)\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "    at handleMessage (/home/cat/reference_repos/typescript_fish-lsp/node_modules/vscode-jsonrpc/lib/common/connection.js:345:13)\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "    at processMessageQueue (/home/cat/reference_repos/typescript_fish-lsp/node_modules/vscode-jsonrpc/lib/common/connection.js:362:17)\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "    at Immediate.<anonymous> (/home/cat/reference_repos/typescript_fish-lsp/node_modules/vscode-jsonrpc/lib/common/connection.js:334:13)\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "    at process.processImmediate (node:internal/timers:478:21) {\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "  code: -32601,\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "  data: undefined\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "}\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "\n"
2024-10-01T01:27:09.027 helix_lsp::transport [ERROR] fish-lsp err <- "Node.js v21.7.1\n"
2024-10-01T01:27:09.037 helix_lsp::transport [ERROR] fish-lsp err: <- StreamClosed

Hm, haven't seen an issue in helix for a while. The log messages seem to indicate that the problem is due to helix not implementing the window/showMessage method of the lsp spec.
Testing locally, the issue seemed to be resolved by using the fish env variable: $fish_lsp_show_client_popups
# in ~/.config/fish/config.fish or somewhere else
# that your fish-shell autoloads during startup/usage

set -gx fish_lsp_show_client_popups false

don't forget to source your fish config afterwards
source ~/.config/fish/config.fish

Here are two other alternative methods of providing the environment variable to your shell environment:

1. set environment variable during interactive session
>_ # note: setting to true causes error again
>_ set -x fish_lsp_show_client_popups false; helix /tmp/foo.fish

2. set fish_lsp environment variables in shell function
# ~/.config/fish/config.fish
fish_lsp_config

# ~/.config/fish/functions/fish_lsp_config.fish
function fish_lsp_config --description 'fish-lsp env --create'
    set -gx fish_lsp_show_client_popups false
end

This solution stopped the server from crashing after indexing completed on my machine. If you're still experiencing issues though, feel free to use the $fish_lsp_logfile to provide more logs.

Disabling this feature suppresses the client's ability to display "popup" notifications, containing messages about the status of a language-server request. Other language servers that use 'window/showMessage' include: sumneko-lua/lua_ls, ts-server, pyright, etc...

 SCREENSHOT - notification displayed once background indexing completes

(in BOTTOM RIGHT, colored BLACK w/ GREEN border)

fish-lsp's command provider also uses this feature.
These are currently the only places where disabling $fish_lsp_show_client_popups will silence the notifications.
I'd assume that this particular issue will go away as helix development continues. Keep an eye out in the future for window notification support in helix, so that you can enable the popup variable and access all features provided by this language-server.

Hope this helped! If you come across your own workaround, feel free to fork and contribute to the fish-lsp :)
Thanks for the thorough bug report!

Thank you for the quick reply and additional info.
Setting set -gx fish_lsp_show_client_popups false did the trick, it's working perfectly as expected now.
Will close this issue since the issue is more on the Helix side

Relevant Issue and possible PR for anyone that may stumble upon this in the future
https://github.com/helix-editor/helix/issues/4699
https://github.com/helix-editor/helix/pull/11081


problem to creat-react-app

i had some problem to download react app ..i already install it but i faced problem and i deleted it and try to re install but i can't

Please refer to documentation here :- https://create-react-app.dev/docs/getting-started


No example for Python Functions v2

There is only a tutorial for Python functions V1. It would be very helpful to have a v2 example as well like most of the other function docs
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1ecc7d98-61b9-4042-2ed7-a0c1a67ef88e
Version Independent ID: 21ec0fc8-0c2f-6649-cec6-dc07d0721ab9
Content: Tutorial: Trigger Azure Functions on blob containers using an event subscription
Content Source: articles/azure-functions/functions-event-grid-blob-trigger.md
Service: azure-functions
GitHub Login: @cachai2
Microsoft Alias: cachai

@jjgriff93
Thanks for your feedback! We will investigate and update as appropriate.


Visual Descriptions

请问,Visual Descriptions是怎么通过GPT生成的,如果对于国内用户来说可以用其他的代替吗?
如果想要生成关于OV-COCO数据集相关的视觉描述,应该怎么做?

Sorry for the late reply.

You can refer to this script; Deepseek can achieve similar result with GPT3.5. I will try to release my visual desc generation script and deepseek checkpoint this week.
Change the categories with ov-coco categories in the script

I did not try ov-coco, you can add the dataset and try it
just set find_unused_parameters=True in configs/common/train.py, this would not affect the result

It is an interesting and worth-exploring result. First of all, thank you very much for your experiments, which has given us a more comprehensive understanding of this work.

All my experiments were all conducted on 8 V100/A100, and the final results have been verified through repeated experiments, but I haven't tried the result on 2 GPUs.

LaMI-DETR during training will sample easy negative classes for positive classes. If the total batch size is too small, the sampled negative classes will be too easy to distinguish different classes, especially base categories, which may help explain why your results of APf and APc are so weird. Since you use 2 GPUs for training, you may only have relatively too simple categories sampled in each iteration.

Therefore, to reproduce the results in our paper, I suggest using 8 GPUs with bs=32, or maybe at least 4 GPUs for training.


Regression test to run on hpc (NOAA/NASA/?)

Add optional ctest at hi-res that will serve as regression tests
(while we figure out something cleaner)

To be moved to soca-science


Added app to handle fullscreen notifications

Added an application that can be triggered by other Bangle.js apps to display fullscreen notifications and allows the wearer to look back at previous notifications (configurable).
Screenshots:

think  about adding g.reset() to save.

@MaBecker Not sure what you mean by "to save". Doesn't g.reset() put all the graphics settings back to the default as on load?

just update my first comment

This looks like a really neat solution - thanks!
Please could you just tweak the changelog into the text-only format used for the other logs though? The loader looks for a ChangeLog file and loads it when the version is clicked on and I'd rather not have to check for a bunch of different styles :)

Updated. Is this the right format @gfwilliams?

Yes, that's perfect - thanks!

Hey, greetings from germany.
Can we change the font to Dennis8 http://www.espruino.com/Fonts?
This would help to display notfication messages with special characters like äöüß

Hey, greetings from germany.
Can we change the font to Dennis8 http://www.espruino.com/Fonts?
This would help to display notfication messages with special characters like äöüß

Well, the 6x8 font has all you need.
https://github.com/espruino/Espruino/issues/1770

Awesome.
I've haven't tested the gadgebridge releated PRs.
I just can state that the current available packages in app loaders have problems with special characters. Maybe the cause is gadgetbridge on my phone. I don't know.

Sorry it's taken so long to sort this, it seemed tricky to integrate this nicely.
I'm afraid I haven't merged this, but have added a simple notify (top of screen as before) and notifyfs app, which create something that allows you to require("notify").show(...). Apps can also set a dependency so that a notification library gets loaded automatically if one doesn't exist.
There's no stored notification list but hopefully the new one can run at the same time as most other apps. The issue with this PR (as far as I could see) was once it's fired it doesn't load widgets, so you wouldn't actually get a second notification if one came in?
If you'd like to PR the new notifyfs with any changes that'd be great though!


Not possible to delete payloads from web interface

When using the web interface, it's impossible to delete payloads.
On MacOS, this means saving via USB creates hidden files which take up all the slots and can't be deleted via the web interface.

We added this feature to the latest update!  Download v1.0.4 here.


Actions failed

Seems all recent actions on updating the problem set failed.
https://github.com/Bishalsarang/Leetcode-Questions/actions/runs/5958046723/job/16161714482

Yeah seems so. Maybe they changed the HTML.


Connect a node to itself

can we make a connection with the node itself?

Yes, just set target and source to the same nodeId in the edge element; you may need a custom edge to achieve the look and feel you are looking for.


Cooldown timer part I

What's New?

Avoid log data loss when hardware / farmware malfunctions via cooldown timeouts.

What's Next?

User notifications need a little extra work.

Coverage remained the same at 91.337% when pulling 6075b1125b8f99fb40f977ec0f68a9b0609352b6 on RickCarlino:log_throttle into 7f48937fc849a4a4411a6c567bd084bb0c85dac9 on FarmBot:staging.


neo_nav2_bringup: 1.3.0-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository neo_nav2_bringup to 1.3.0-1:

upstream repository: https://github.com/neobotix/neo_nav2_bringup.git
release repository: https://github.com/ros2-gbp/neo_nav2_bringup-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.12.0
previous version for package: null

Holding for Jazzy sync


Master version more aggresive than dev in search monster

Why with master version I've got much more pokemon than dev version? Master version more aggresive in detect monster spawn.

Ive noticed that the dev version detects way less pokemon spawned by lures


update (npm): add v0.2 with command param support

npm task's behavior defaults to using the npm command. Users
would like to use the same task with yarn or some other package manager
as their node env based package manager if npm is not their choice of
pkg manager. To enable this, this commit allows the user to specify the
COMMAND param (which default to npm) where the user can specify some
other package manager available in the nodejs environment.

Changes

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Follows the authoring recommendations
[ ] Includes docs (if user facing)
[ ] Includes tests (if functionality of task changed or new task added)
[ ] Commit messages follow commit message best practices
[ ] Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation

[ ] File path follows  <kind>/<name>/<version>/name.yaml

[ ] Has README.md at <kind>/<name>/<version>/README.md

[ ] Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource

[ ] Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

[ ] mandatory spec.description follows the convention
  ```

  spec:
    description: >-
      one line summary of the resource

      Paragraph(s) to describe the resource.
  ```

See the contribution guide
for more details.

/diff-task

/diff-task

/diff-task

/diff-tree

/diff-tree

/diff-task

/diff-task

/diff-task

/diff-task

/diff-task

Diff between version 0.1 and 0.2
diff --git a/task/npm/0.1/README.md b/task/npm/0.2/README.md
index 77e9b31..27f4767 100644
--- a/task/npm/0.1/README.md
+++ b/task/npm/0.2/README.md
@@ -12,6 +12,8 @@ kubectl apply -f https://raw.githubusercontent.com/tektoncd/catalog/main/task/np

 - **PATH_CONTEXT**: The path where `package.json` of the project is defined. (_Default: `"."`_)

+- **COMMAND**: The package manager you want to run from the nodejs env. (_Default: `npm`_)
+
 - **ARGS**: The npm goals you want to run. (_Default: `version`_)

 - **IMAGE**: The node image you want to use. (_Default: docker.io/library/node:12-alpine@sha256:12048cdfd75d944df35f3144132d9bdeee78015fbd6df765edad1be46599b110_)
diff --git a/task/npm/0.1/npm.yaml b/task/npm/0.2/npm.yaml
index 7b2ced8..328fcbf 100644
--- a/task/npm/0.1/npm.yaml
+++ b/task/npm/0.2/npm.yaml
@@ -3,7 +3,7 @@ kind: Task
 metadata:
   name: npm
   labels:
-    app.kubernetes.io/version: "0.1"
+    app.kubernetes.io/version: "0.2"
   annotations:
     tekton.dev/pipelines.minVersion: "0.17.0"
     tekton.dev/categories: Build Tools
@@ -23,10 +23,14 @@ spec:
       type: string
       default: "."
       description: The path where package.json of the project is defined.
+    - name: COMMAND
+      type: string
+      default: "npm"
+      description: The package manager you want to run from the nodejs env.
     - name: ARGS
       type: array
       default: ["version"]
-      description: The npm goals you want to run.
+      description: The goals you want to run for the given command.
     - name: IMAGE
       type: string
       default: "docker.io/library/node:12-alpine@sha256:dfbebf17bfb014e1e7068e76325a117bccf8679c68aec6a28514184a209c8bae"
@@ -35,7 +39,7 @@ spec:
     - name: npm-run
       image: $(params.IMAGE)
       command:
-        - "npm"
+        - $(params.COMMAND)
       args:
         - $(params.ARGS)
       workingDir: $(workspaces.source.path)/$(params.PATH_CONTEXT)
diff --git a/task/npm/0.1/tests/run.yaml b/task/npm/0.2/tests/npm-run.yaml
similarity index 100%
rename from task/npm/0.1/tests/run.yaml
rename to task/npm/0.2/tests/npm-run.yaml
diff --git a/task/npm/0.2/tests/yarn-run.yaml b/task/npm/0.2/tests/yarn-run.yaml
new file mode 100644
index 0000000..18145b2
--- /dev/null
+++ b/task/npm/0.2/tests/yarn-run.yaml
@@ -0,0 +1,64 @@
+apiVersion: tekton.dev/v1beta1
+kind: PipelineRun
+metadata:
+  name: npm-run
+spec:
+  workspaces:
+    - name: shared-workspace
+      volumeClaimTemplate:
+        spec:
+          accessModes:
+            - ReadWriteOnce
+          resources:
+            requests:
+              storage: 10Gi
+  pipelineSpec:
+    workspaces:
+      - name: shared-workspace
+    tasks:
+      - name: fetch-repository
+        taskRef:
+          name: git-clone
+        workspaces:
+          - name: output
+            workspace: shared-workspace
+        params:
+          - name: url
+            value: https://github.com/vinamra28/sonartest
+          - name: subdirectory
+            value: ""
+          - name: deleteExisting
+            value: "true"
+      - name: install-dependencies
+        taskRef:
+          name: npm
+        workspaces:
+          - name: source
+            workspace: shared-workspace
+        params:
+          - name: PATH_CONTEXT
+            value: "app"
+          - name: COMMAND
+            value: "yarn"
+          - name: ARGS
+            value:
+              - install
+        runAfter:
+          - fetch-repository
+      - name: run-test
+        taskRef:
+          name: npm
+        workspaces:
+          - name: source
+            workspace: shared-workspace
+        params:
+          - name: PATH_CONTEXT
+            value: "app"
+          - name: COMMAND
+            value: "yarn"
+          - name: ARGS
+            value:
+              - run
+              - test
+        runAfter:
+          - install-dependencies

/diff-task

Diff between version 0.1 and 0.2
diff --git a/task/npm/0.1/README.md b/task/npm/0.2/README.md
index 77e9b31..27f4767 100644
--- a/task/npm/0.1/README.md
+++ b/task/npm/0.2/README.md
@@ -12,6 +12,8 @@ kubectl apply -f https://raw.githubusercontent.com/tektoncd/catalog/main/task/np

 - **PATH_CONTEXT**: The path where `package.json` of the project is defined. (_Default: `"."`_)

+- **COMMAND**: The package manager you want to run from the nodejs env. (_Default: `npm`_)
+
 - **ARGS**: The npm goals you want to run. (_Default: `version`_)

 - **IMAGE**: The node image you want to use. (_Default: docker.io/library/node:12-alpine@sha256:12048cdfd75d944df35f3144132d9bdeee78015fbd6df765edad1be46599b110_)
diff --git a/task/npm/0.1/npm.yaml b/task/npm/0.2/npm.yaml
index 7b2ced8..328fcbf 100644
--- a/task/npm/0.1/npm.yaml
+++ b/task/npm/0.2/npm.yaml
@@ -3,7 +3,7 @@ kind: Task
 metadata:
   name: npm
   labels:
-    app.kubernetes.io/version: "0.1"
+    app.kubernetes.io/version: "0.2"
   annotations:
     tekton.dev/pipelines.minVersion: "0.17.0"
     tekton.dev/categories: Build Tools
@@ -23,10 +23,14 @@ spec:
       type: string
       default: "."
       description: The path where package.json of the project is defined.
+    - name: COMMAND
+      type: string
+      default: "npm"
+      description: The package manager you want to run from the nodejs env.
     - name: ARGS
       type: array
       default: ["version"]
-      description: The npm goals you want to run.
+      description: The goals you want to run for the given command.
     - name: IMAGE
       type: string
       default: "docker.io/library/node:12-alpine@sha256:dfbebf17bfb014e1e7068e76325a117bccf8679c68aec6a28514184a209c8bae"
@@ -35,7 +39,7 @@ spec:
     - name: npm-run
       image: $(params.IMAGE)
       command:
-        - "npm"
+        - $(params.COMMAND)
       args:
         - $(params.ARGS)
       workingDir: $(workspaces.source.path)/$(params.PATH_CONTEXT)
diff --git a/task/npm/0.1/tests/run.yaml b/task/npm/0.2/tests/npm-run.yaml
similarity index 100%
rename from task/npm/0.1/tests/run.yaml
rename to task/npm/0.2/tests/npm-run.yaml
diff --git a/task/npm/0.2/tests/yarn-run.yaml b/task/npm/0.2/tests/yarn-run.yaml
new file mode 100644
index 0000000..18145b2
--- /dev/null
+++ b/task/npm/0.2/tests/yarn-run.yaml
@@ -0,0 +1,64 @@
+apiVersion: tekton.dev/v1beta1
+kind: PipelineRun
+metadata:
+  name: npm-run
+spec:
+  workspaces:
+    - name: shared-workspace
+      volumeClaimTemplate:
+        spec:
+          accessModes:
+            - ReadWriteOnce
+          resources:
+            requests:
+              storage: 10Gi
+  pipelineSpec:
+    workspaces:
+      - name: shared-workspace
+    tasks:
+      - name: fetch-repository
+        taskRef:
+          name: git-clone
+        workspaces:
+          - name: output
+            workspace: shared-workspace
+        params:
+          - name: url
+            value: https://github.com/vinamra28/sonartest
+          - name: subdirectory
+            value: ""
+          - name: deleteExisting
+            value: "true"
+      - name: install-dependencies
+        taskRef:
+          name: npm
+        workspaces:
+          - name: source
+            workspace: shared-workspace
+        params:
+          - name: PATH_CONTEXT
+            value: "app"
+          - name: COMMAND
+            value: "yarn"
+          - name: ARGS
+            value:
+              - install
+        runAfter:
+          - fetch-repository
+      - name: run-test
+        taskRef:
+          name: npm
+        workspaces:
+          - name: source
+            workspace: shared-workspace
+        params:
+          - name: PATH_CONTEXT
+            value: "app"
+          - name: COMMAND
+            value: "yarn"
+          - name: ARGS
+            value:
+              - run
+              - test
+        runAfter:
+          - install-dependencies

/test .*

Catlin Output
Diff between version 0.1 and 0.2
FILE: task/npm/0.2/npm.yaml
HINT : Task: tekton.dev/v1beta1 - name: "npm" is missing a readable display name annotation("tekton.dev/displayName")
WARN : Step "npm-run" uses image "$(params.IMAGE)" that contains variables; skipping validation

/test .*

Catlin Output
FILE: task/npm/0.2/npm.yaml
HINT : Task: tekton.dev/v1beta1 - name: "npm" is missing a readable display name annotation("tekton.dev/displayName")
WARN : Step "npm-run" uses image "$(params.IMAGE)" that contains variables; skipping validation


3.5.1 support?

Latest release appears to support up to 3.4.0
https://github.com/IBM/spark-s3-shuffle/releases
Possible to do a new release for 3.5.1? If you give me some pointers I'd be happy to try it.

It works with 3.5.0 for me.

Ah will try it! Did you use the 3.4.0 release?
On Sun, Mar 17, 2024, 11:05 AM Leo @.***> wrote:

It works with 3.5.0 for me.
—
Reply to this email directly, view it on GitHub
https://github.com/IBM/spark-s3-shuffle/issues/83#issuecomment-2002558790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHZJMD5BEKL22CV3RW3FLLYYXLOZAVCNFSM6AAAAABEZ56SMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGU2TQNZZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry, somehow I have issues getting public github notifications.
The 3.4.0 build should work: The Spark API did not change. I'll add a 3.5.x build for consistency.

Builds should be available in a couple minutes: https://github.com/IBM/spark-s3-shuffle/releases/tag/v0.9.6


Inconsistent behavior in URLEncoding.encode() for GET and POST calls

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?

I added a RequestAdapter that I use to inject common API parameters into my HTTP calls when a certain HTTP Header is present (backstory: all my calls to this particular API require that I send a device_guid and client_bundle_id in the body or query string, depending on the verb used GET/POST/PUT).
In the adapter I populate a dictionary with these values and call:

urlRequest = try URLEncoding.default.encode(urlRequest, with: parameters)
completion(.success(urlRequest))

What did you expect to happen?
I expected the HTTP body to be updated with the new parameters in the resulting urlRequest in case of POST calls and the query string to be updated with the new parameters in case of GET calls.
What happened instead?
In case of GET calls, the query string has the existing parameters + the two parameters above.
For example, https://example.com/user?user_id=1 becomes https://example.com/user?user_id=1&device_guid=12345&bundle_id=com.example.bundle_id
In case of POST calls, the HTTP body is completely replaced with the two parameters above.
This is a source of confusion as my expectation would have been that URLEncoding.encode() behaves in the same manner regardless of the verb used.
(More applied to my particular issue, maybe using a RequestAdapter here is the wrong approach?)
Alamofire Environment
Alamofire Version: 5.6.4
Dependency Manager: Cocoapods
Xcode Version: 14.2
Swift Version: 5.7.2
Platform(s) Running Alamofire: iOS
macOS Version Running Xcode: Ventura 13.2.1
Demo Project
A sample adapter is below:

private let deviceGUID: String = "12345"

public class APICommonParametersInjector: RequestAdapter {

    /// Magic header name
    public static var headerName: String = "__xxx_inject_common_parameters"

    public func adapt(_ urlRequest: URLRequest, for session: Session, completion: @escaping (Result<URLRequest, Error>) -> Void) {
        var urlRequest = urlRequest

        if urlRequest.value(forHTTPHeaderField: APICommonParametersInjector.headerName) != nil {
            urlRequest.setValue(nil, forHTTPHeaderField: APICommonParametersInjector.headerName)

            var parameters: [String: String] = [:]
            parameters["device_guid"] = deviceGUID
            parameters["client_bundle_id"] = Bundle.main.infoDictionary?["CFBundleIdentifier"] as? String

            do {
                urlRequest = try URLEncoding.default.encode(urlRequest, with: parameters)
            }
            catch {
                // do nothing, the request will probably fail
            }
        }

        completion(.success(urlRequest))
    }
}

Yes, this is expected behavior, as URLEncoding encodes to the body by default for POST requests, as that's what 99% of servers expect. You can encode these particular parameters into the query by using URLEncoding.queryString.
There are several other ways to improve your code.

When using any of the other Foundation networking types like URLRequest with headers, you can use Alamofire's .headers extension property to set and get them using our HTTPHeaders type. I suggest you write some extensions to that type to ensure you're setting the headers in only one way with a nicer API.
Call completion(.failure(<Errror>)) when you know the request will fail. The error will be passed through to your completion handler.
Move to an Encodable type for your parameters and use URLEncodedFormParameterEncoder. That API is the future of Alamofire and already has more powerful tools for dealing with customized encodings.

Wait, I feel like either I wasn't clear enough in my explanation or you misread my notes.
The problem is not that the POST parameters go in the body. That's where they're supposed to be 😅
The problem is that in case of GET requests, the parameters are appended to the existing set of parameters, while for  POST requests, the parameters sent to URLEncoding.default.encode completely replace the existing HTTP body.

Yes, that's expected behavior, and that aspect of it is not customizable. For the body encoding we'd need to parse an existing body in order to append, which is a lot of work for little reward. If you need to change that behavior you can duplicate URLEncoding and have it do what you need.

I suppose we could hack it and make URLComponents parse the body for us by setting it as the query of new components, appending, and then putting it back into the body. I'll think about it for URLEncodedFormParameterEncoder, but this is definitely one of those things I probably won't port back to URLEncoding.

Thanks for your thoughts on this. It feels like this is opening a nasty can of worms, what happens if it's a multipart POST call? It can quickly get overly complicated.
I think everyone's better off working around it and just putting up a warning of sorts in the doc block that explains the particularities of URLEncoding's behavior.

Yes, that's the issue with each customizability axis in things like this. Each one needs its own error path and proper testing.
I'll look at the docs. Probably just need to update the inline docs to specific "append" for the query setting and "replace" for the body setting. I may get to that or I'd accept a PR.


Why this solution when a "proper" solution is planned?

Hi,
This is not the first automation solution from Microsoft to schedule stop/start of VMs.
While I appreciate the effort what we need is a simple solution build in to the platform not a complex automation solution.
It looks like this planned https://feedback.azure.com/forums/320373-devtest-labs/suggestions/17509267-support-auto-start-from-vm-blade.
But it has been a couple of years. It would be nice to know what the  plan is for a build in solution vs. the automation solutions?
Regards Peter

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

ID: 225c9d05-83dd-b006-0025-3753f5ab25bf
Version Independent ID: 9eecef0c-b1cb-1136-faf7-542214492096
Content: Start/Stop VMs during off-hours solution (preview)
Content Source: articles/automation/automation-solution-vm-management.md
Service: automation
Product: unspecified
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@theheatDK Thanks for the feedback. We are actively investigating and will get back to you soon.

@theheatDK We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add section on block storage encryption

Summary
translated from https://grand-est.fr/support-utilisateurs/documentation-en-ligne/guide-dutilisation-dopenstack/#disk-encryption

Related issue :

I'm a bit concerned by reading "translated from" :)
Have we their authorisation for reusing their content? Have you any info about licence used for their content and so on?

I'm a bit concerned by reading "translated from" :) Have we their authorisation for reusing their content? Have you any info about licence used for their content and so on?

i got the link from Jerome as that is the SCIGNE documentation, should i check with him?

i got the link from Jerome as that is the SCIGNE documentation, should i check with him?

Yes please, you could even propose him to comment here that he is fine :)

Just to log that we got the confirmation from @Pansanel that it's fine to reuse/adapt this content.

The user documentation got reorganised via #414, can you please resolve the conflicts in your PR?

@gwarf rebase done


Roadmap

[x] refactor uf2 support into a standard IOSteam? reader that works just like open() on a bin file
[ ] make this work on MicroPython?
[x] refactor to a class/library (half way done, kinda)
[ ] add support for pins and such
[ ] add tests, CI and packaging

TO make this work on MicroPython, it just needs a new reader:
class FlashReader():
    def __init__(self):
        self.mem = machine.mem8
        self.offset = 0
        self.buf_len = 16
        self.buf = bytearray(self.buf_len)

    def seek(self, offset):
        self.offset = offset

    def read(self, length):
        buf = bytearray(length) if length > self.buf_len else self.buf
        for i in range(length):
            buf[i] = self.mem[FLASH_START_ADDR + self.offset]
            self.offset += 1
        return bytes(buf[:length])

Revised version now added to py_decl:
class MemoryReader():
    def __init__(self, mem, global_offset=FLASH_START_ADDR):
        self.mem = mem
        self.offset = 0
        self.buf_len = 16
        self.global_offset = global_offset
        self.buf = bytearray(self.buf_len)

    def seek(self, offset):
        self.offset = offset

    def read(self, length):
        buf = bytearray(length) if length > self.buf_len else self.buf
        for i in range(length):
            buf[i] = self.mem[self.global_offset + self.offset]
            self.offset += 1
        return bytes(buf[:length])

Note: UF2Reader does not work on MicroPython because you can't subclass BytesIO (call to BytesIO.__init__ fails).


passing "ies" to natural::stem::get panics

I get the message:
thread 'main' panicked at 'index out of bounds: the len is 3 but the index is<PHONE_NUMBER>3709551615', /c
heckout/src/libcore/slice/mod.rs:2041:10

The value seems to indicate an unsigned value dropping below zero.

There are a few edge cases in the stemmer. I'd like to implement a few other stemmers, but for now I'm just going to try to manage these edge cases. I'll patch this hopefully for the next release.

I did some passes on refactoring and decided that the stemmer module is very old and not very idiomatic rust. The overhead to refactor is high, and implementing my own stemmer seems like reinventing the wheel when there are some great crates out there for this, and I didn't want to redistribute another crate within this one. My current solution to this problem is removing the stemming functionality from this crate entirely and let the user decide which stemmer crate to use, for things like TF-IDF and the classifier I'm using rust-stemmers crate to handle stemming those.


Add Koin template

Currently pending in a branch, but need an update for Koin as it doesn't support the latest ktor version.


Cannot install in Laravel 8.20

Is there any update for laravel 8.20?

Hi @timslash it seems @reshadman is not able to access github, so I've forked the project and published an updated version on packagist.org as xint0/laravel-optimistic-locking. Please try it and let me know if it works.

I just published an improvement over this package at https://github.com/qtsolv/laravel-locking please see and report any issues/feddback you may have.


[TIR] Introduce BufferLoad/Store

Co-authored-by: Siyuan Feng<EMAIL_ADDRESS>This PR introduces BufferLoad/Store to TIR. The new nodes will replace
Provide and Call with Tensor arguments in the subsequent refactors.

cc @Hzfengsy @yzhliu @ZihengJiang @spectrometerHBH

Did you push the wrong code to this branch? The codes are same as another PR

@Hzfengsy sorry, just fixed