Why do I need full SSL certificate if I only want SPKI (Subject Public Key Info) pinning?

I am a bit of a security novice but I'd like to add SSL pinning to my Starscream implementation. Everything I've read suggests using SPKI and standard public key pinning at the least. I see there is an option for using public key pinning in the library but it needs a full cert for extracting it. Is there no way to simply provide that public key info without packagaing a full cert file (that will frequently expire) in the app bundle?
Thanks for any help/wisdom!

The docs could definitely use love. We are working on some updates around the Networking and SSL Pinning currently, so stay tuned for those updates. In the meantime, you should be able to currently provide just the public key like so:
let publicKey = SecTrustCopyPublicKey(trust) // or wherever you obtain your SecKey from.
let cert = SSLCert(key: publicKey)
socket.security = SSLSecurity(certs: [cert], usePublicKeys: true)

Ah wonderful. Thanks for the update!


Delay in response when using  Magic TrackPad 2

When using the Magic TrackPad 2 to slide up and down, there is a delay in response.
I use the mac mini 2020, and the macos is Monterey

same as issue #51


feat: divider control

GitHub Issue: #
PR Type
What kind of change does this PR introduce?

Feature

Description
I've implemented the material divider control.
PR Checklist
Please check if your PR fulfills the following requirements:

Commits must be following the Conventional Commits specification
[x] Tested UWP
[x] Tested iOS
[x] Tested Android
[x] Tested WASM
[ ] Tested MacOS
[x] Contains No breaking changes

If the pull request contains breaking changes, commit message must contain a detailed description of the action to take for the consumer of this library. As explained by the Conventional Commits specification

Other information

Internal Issue (If applicable):

test macos

Adjust the margin/padding on the item a bit, so they appear centered:

Add an example for ListView?

Adjust the margin/padding on the item a bit, so they appear centered:

Yes please and leave also some padding on the right side of the icon  :)

Add it to README.md please :)

Material's spec says not to use dividers for every item.
I would just adapt the sample a little bit to be sure not to guide a wrong guidance :)


Forms

Forms functionality complete with http requests

Should we add the forms to the contact page? Right now I think they're on separate pages, not in the nav bar

I think we'll eventually add the forms to the contact page, but for now we'll try and ship a Minimum viable product!


Switched to submodules with prototypal inheritance

Also added a mocked aws-sdk to allow for easier end-user testing (see README)

Nice work! Really sets us up for growth.


Minor: re-order optimizer and scheduler steps

This PR swaps the order of optimizer and learning rate scheduler steps (addressing the warning pointed out by @HaokunLiu):
Warning message pre-change:

UserWarning: Detected call of lr_scheduler.step() before optimizer.step(). In PyTorch 1.1.0 and later, you should call them in the opposite order: optimizer.step() before lr_scheduler.step(). Failure to do this will result in PyTorch skipping the first value of the learning rate schedule. See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate

Can we double check when/how Transformers fixed this?

Changed for SQuAD here: https://github.com/huggingface/transformers/pull/1136/files

Can we double check when/how Transformers fixed this?

A few re-orders were done in 8/19, with "One last reorder of {scheduler,optimizer}.step()" in 3/20.


[FEATURE] Allow flagd debug flag to be set through environment variable

Background
flagd debug flag is defined at the root level and available as a persistent flag. However persistent flags are not modifiable through environment variables.
Requirement
Given flagd support environment variable-based configurations, we should add support to define debug flag through environment variable (ex:- FLAG_DEBUG or DEBUG)
Also consider the following,

Given we haven't visited cobra and viper configurations, it could be good opportunity to refactor flagd startup setup
Document FLAGD prefix based environment variable resolving capability

I'm taking this issue


Add CI

Particularly to check that go test ./... is happy, including vet. If we want this to be more than a one-man project, CI will be useful.
Happy to enable the repo on Travis and send a PR with the yaml file if @rogpeppe agrees. We can use go1.11beta3 for now.

Seems like an excellent idea to me.

Fixed by #26


Clear incorrectly reported errors in cms_io

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

This pull request is ready to merge

Merged to master and 3.0 branches. Thank you.


Placeholder for MWPhotoBrowser

Is there a method implemented already for custom placeholder?
custom placeholder means before loading "full size" image, I want it to display thumbnail images first until full size image loaded

@steve21124 you can use https://github.com/mwaterfall/MWPhotoBrowser/pull/479


Flag for reasoned or not

Address issue :
https://github.com/EBISPOT/OLS/issues/274

Not relevant for MOD as this is specific to a portal. We shall look into this in AgroPortal.


Support for Version 4

Hi
Is it safe to upgrade the Veeam Server to version 4?
Is this panel still running on the new version?

Version 4 is supported and has some new things included. The release is available via https://github.com/nielsengelen/vbo365-rest/releases/tag/v4.


BUG postgresql field get error

pullOrderTime := model.PullOrderTime{}
g.DB("vivipos").Model("public.pull_order_time").Where("id = ?", "cratedb").Struct(&pullOrderTime)

The sql fields are constructed using the struct fields of the model and do not use the orm tag field names in the tag
SELECT "Id","PullTime","Params","SuppTime" FROM "public"."pull_order_time" WHERE id = 'cratedb' LIMIT 1
database/gdb/gdb_model_utility.go

@651016236 请使用最新master分支再试试

切换到master分支还是有问题
orders := ([]model.ViviposVivitrendOrders)(nil)
db.Model("pos.vivitrend_orders").Limit(1).Scan(&orders)
2021-07-09 17:42:53.288 [DEBU] [455 ms] [default] SELECT a.attname AS field, t.typname AS type FROM pg_class c, pg_attribute a LEFT OUTER JOIN pg_description b ON a.attrelid=b.objoid AND a.attnum = b.objsubid,pg_type t WHERE c.relname = 'vivitrend_orders' and a.attnum > 0 and a.attrelid = c.oid and a.atttypid = t.oid ORDER BY a.attnum  2021-07-09 17:42:53.310 [ERRO] [ 17 ms] [default] SELECT "Id","Sequence","ItemsCount","Total","Change","TaxSubtotal","SurchargeSubtotal","DiscountSubtotal","PaymentSubtotal","RoundingPrices","PrecisionPrices","RoundingTaxes","PrecisionTaxes","Status","ServiceClerk","ServiceClerkDisplayname","ProceedsClerk","ProceedsClerkDisplayname","Member","MemberDisplayname","MemberEmail","MemberCellphone","InvoiceType","InvoiceTitle","InvoiceNo","InvoiceCount","Destination","TableNo","CheckNo","NoOfCustomers","TerminalNo","TransactionCreated","TransactionSubmitted","Created","Modified","IncludedTaxSubtotal","ItemSubtotal","SalePeriod","ShiftNumber","BranchId","Branch","TransactionVoided","PromotionSubtotal","VoidClerk","VoidClerkDisplayname","VoidSalePeriod","VoidShiftNumber","RevalueSubtotal","QtySubtotal","InheritedOrderId","InheritedDesc","ItemSurchargeSubtotal","TransSurchargeSubtotal","ItemDiscountSubtotal","TransDiscountSubtotal","ServiceChargeSubtotal","IncludedServiceChargeSubtotal","Zone","CompanyCode","HardwareId","OverAmt","OrderSourceId","DiningStyle","ChannelNo","PrnInvQrcode","BackupId","IsValid" FROM "pos"."vivitrend_orders" LIMIT 1
默认字段并未获取model中的orm tag 字段值

@651016236 请使用最新master分支再试试
切换到master分支还是有问题
orders := ([]model.ViviposVivitrendOrders)(nil)
db.Model("pos.vivitrend_orders").Limit(1).Scan(&orders)

2021-07-09 17:42:53.288 [DEBU] [455 ms] [default] SELECT a.attname AS field, t.typname AS type FROM pg_class c, pg_attribute a LEFT OUTER JOIN pg_description b ON a.attrelid=b.objoid AND a.attnum = b.objsubid,pg_type t WHERE c.relname = 'vivitrend_orders' and a.attnum > 0 and a.attrelid = c.oid and a.atttypid = t.oid ORDER BY a.attnum 2021-07-09 17:42:53.310 [ERRO] [ 17 ms] [default] SELECT "Id","Sequence","ItemsCount","Total","Change","TaxSubtotal","SurchargeSubtotal","DiscountSubtotal","PaymentSubtotal","RoundingPrices","PrecisionPrices","RoundingTaxes","PrecisionTaxes","Status","ServiceClerk","ServiceClerkDisplayname","ProceedsClerk","ProceedsClerkDisplayname","Member","MemberDisplayname","MemberEmail","MemberCellphone","InvoiceType","InvoiceTitle","InvoiceNo","InvoiceCount","Destination","TableNo","CheckNo","NoOfCustomers","TerminalNo","TransactionCreated","TransactionSubmitted","Created","Modified","IncludedTaxSubtotal","ItemSubtotal","SalePeriod","ShiftNumber","BranchId","Branch","TransactionVoided","PromotionSubtotal","VoidClerk","VoidClerkDisplayname","VoidSalePeriod","VoidShiftNumber","RevalueSubtotal","QtySubtotal","InheritedOrderId","InheritedDesc","ItemSurchargeSubtotal","TransSurchargeSubtotal","ItemDiscountSubtotal","TransDiscountSubtotal","ServiceChargeSubtotal","IncludedServiceChargeSubtotal","Zone","CompanyCode","HardwareId","OverAmt","OrderSourceId","DiningStyle","ChannelNo","PrnInvQrcode","BackupId","IsValid" FROM "pos"."vivitrend_orders" LIMIT 1
默认字段并未获取model中的orm tag 字段值

@651016236 再试试master


Release 20.03

Motivation for this change
DisplayCal version 3.5 as released with NixOS 20.03 could not perform a calibration, but did compile. Updating to the latest stable release and fixing the packaging allows for a successful calibration.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Wow, not what I wanted to do...


Support a clickable label for Slider

I would like to add a label element for a slider component. Clicking the label should focus the slider.
At the moment I cannot find a way to do this with Radix Themes directly.
I can do this with Radix Primitives by making the Slider.Thumb a input[type="range"] using the asChild prop.
As Radix Themes does not expose the Thumb part, in order to do this with Radix Themes I would need to build my own Slider using the Radix Themes classes and Radix Primitives parts.
This is fine - but perhaps this technique is useful for others or perhaps you want to incorporate this in to Radix Themes. I am not sure if there is a drawback to making the Thumb part an input[type=range], I haven't found one yet, but if there is not perhaps this should be done as standard?
Check out this stackblitz - it shows the issue and how I have solved it:
https://stackblitz.com/edit/vitejs-vite-5ikew3
Note that the Thumb already has role="slider" and, as far as I can see, input[type=range] is a sensible default when using role=slider:

When not using the HTML  element to create your slider
...
It is recommended to use a native  of type range, , rather than the slider role.

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/slider_role

@benoitgrelard check this out

changing the Slider.Thumb to a button by default wld also fix this. the current slider supports multiple thumbs so unstyled ranges might look a bit weird here. they would allow Radix to remove some internal BubbleInput logic though which could be nice!


ADBC driver for DataFusion

What feature or improvement would you like to see?
I started an adbc driver for datafusion in adbc-datafusion repo based on the rust dummy driver in this repo. It's mostly functional with support for get_objects, sql and substrait execution.
I'm not sure what's the most appropriate home for the driver though. Should it go here in arrow-adbc repo, the main datafusion repository or maybe as an independent repository as a datafusion-contrib?

fyi @alamb, curious what you think

I think we would like projects to maintain their drivers (as DuckDB does), but the Rust target is also shifting. It's possible we should maintain it in -contrib or in tree until the Rust APIs have settled a bit before trying to upstream it so there is a reasonably stable target to follow.

@mbrobbel maybe something to explore is versioning the Rust API definitions separately as well so there is a very stable target instead of churning the version number every 2 months for no reason

in tree until the Rust APIs have settled a bit

I agree with this. Keeping it in tree helps to understand how changes to core traits impact existing drivers, and drivers must be updated as part of PRs that change these traits.

maybe something to explore is versioning the Rust API definitions separately as well so there is a very stable target instead of churning the version number every 2 months for no reason

I agree it would be better to track this separately. There are a few things to consider:

I guess this complicates the release process a little bit?
As long as we're still using 0.x.y versions, applying non-breaking minor bumps is trivial for dependents, especially when they are using something like Dependabot.
We are going to have to release whenever arrow-rs releases a new major version (we are using arrow-rs types in our public API). Dependents using both arrow-rs and adbc crates are blocked from updating their arrow related dependencies until we release with the latest arrow-rs major version.

thanks, I'll open a PR here then.

Only just now realized I was linking to a private repo in the description :man_facepalming: anyway.. PR is up at #2267


Array conditions

Bug or feature request?
Feature request
Description:
Would be neat if cond could accept array of guards, without this I have to make multiple transient states when my logic is more complex.
(Feature) Potential implementation:
It's not a breaking change and the API would be something like this:
'': [
    { target: 'foo', cond: ['isOnline', 'hasForm'] }
]

This seems like it would work well with custom guards 📘 - the tricky thing with "just allowing arrays" is that it's ambiguous whether it means isOnline && hasForm or isOnline || hasForm. But you can easily do this:
const every = (...guards) => ({
  type: 'every',
  guards
});

const guards = {
  isOnline: ctx => ctx.status === 'online',
  hasForm: ctx => ctx.user.hasForm === true
};

// ...
'': [
  {
    target: 'foo',
    cond: every('isOnline', 'hasForm')
    // => { type: 'every', guards: ['isOnline', 'hasForm'] }
  }
]

// ...
// machine options
{
  guards: {
    ...guards,
    every: (ctx, event, { guard }) => {
      const { guards } = guard;
      return guards.every(guardKey => guards[guardKey](ctx, event));
    }
  }
}

What do you think about that for a solution? Much more flexible than having XState be opinionated (and potentially too magical/black-box like) about custom guards.

I don't have much problem with the proposed solution, I've tackled the problem at hand in a similar fashion at the moment. My reasoning behind requesting this was that basically OR might be already represented by:
'': [ { target: 'foo', guard: 'a' }, { target: 'foo', guard: 'b' } ]

and that custom guards are harder to serialize.

I'll consider it. Good to look at prior art too: https://states-language.net/spec.html#choice-state

This feature would be really nice. An array of two strings (e.g. cond: ['isOnline', 'hasForm']) would be much easier to read and write than custom guards are.
I think an array would work as an assumed && since the || alternative can already be implemented using an array of transitions (as @Andarist mentioned) and the pattern already exists with the actions arrays (i.e. every function in the array is fired).
🤞

Good point. I'll implement it - it's on the roadmap.

Good point. I'll implement it - it's on the roadmap.

Thank you!

Good point. I'll implement it - it's on the roadmap.
Any chance this would also show up for the choose action?

@cybervaldez That will most likely look like:
choose([
  { cond: and('cond1', 'cond2') }
])

Or something similar.

But you can easily do this

If anyone stumbles across this workaround, I had to make a few changes to the every guard to make it work:
- every: (ctx, event, { guard }) => {
- 	const { guards } = guard;
- 	return guards.every(guardKey => guards[guardKey](ctx, event));
  }
+ every: (ctx, event, { cond }) => {
+ 	const { keys } = cond;
+ 	return keys.every(guardKey => guards[guardKey](ctx, event));
  }

If anyone stumbles across this workaround, I had to make a few changes to the every guard to make it work:

This helped me, thanks!

@davidkpiano
I just implemented this following the namespace.utility convention of actions (actions.choose, actions.pure, etc.).
export namespace guards{
  export function every(...guards:string[]){
    return function guard(context:any, event:any, meta:any)
      {return guards.every(key => meta.state.machine.options.guards[key](context, event, meta))}
  }
  export function some(...guards:string[]){
    return function guard(context:any, event:any, meta:any)
      {return guards.some(key => meta.state.machine.options.guards[key](context, event, meta))}
  }
}

This implementation allows me to reuse guards in any machine, without the boilerplate of the previously proposed solution (target guards defined externally to MachineOptions, every guard defined in MachineOptions).
Two questions:

Are you aware of any potential pitfalls with this approach ?
What do you think of using this approach for the Array conditions target of the roadmap?
(the namespace.utility shape, not the exact implementation)

@Enteleform That actually seems like a great idea. Can you add it as an idea to a new discussion? I don't see much danger in exposing the machine configuration directly (which it already is, for state.machine) but we can support that more directly.

@davidkpiano When this feature will be released? 🥺

@davidkpiano When this feature will be released? 🥺

It is already in V5 alpha, although it looks slightly different to make guards much more flexible:
guard: and(['isOnline', 'hasSomething'])


New tutorial for using Azure Key Vault from a Web Application

I noticed that there wasn't a tutorial for this use case and thought it will be a common one.

Hi @adamhurwitz, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

I work at Microsoft

Working with @adamhurwitz and @bruceper to redirect to private repo

Hi Bryan,
I'm totally new to this process, the PR receiving side. How do I know if I've permissions and what do the next steps look like.
Thanks,
Bruce

Merging per conversations with @BrucePerlerMS

Excellent.


Restrict LDAP authentication to users in a group

Hi,
This is sort of a duplicate of #378 but since that has been closed by the author i created a new issue. Our issue is the same as the issue #378. We need to restrict the authentication to a certain group in our AD. Something like this:
userbase: “CN=testgroup,OU=Sites,OU=company,DC=company,DC=company”
Is there no way to achieve this today?
More information in this thread: https://discuss.opendistrocommunity.dev/t/authentication-via-ldap-only-allow-certain-security-groups/4540

I am also looking for this. Ideally users that don't fall into any authorization role cannot login at all.

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


Screenshots 404 error

Hello,
Could you reupload the demo screenshots ?
Thank you very much

Fixed on the latest!


Migrate IndexerSQLMetadataStorageCoordinator.getUnusedSegmentsForInterval to streaming

Affects Archive task

Missed query from #2859

@xvrl please peek when you have a chance.

👍

travis failure - https://travis-ci.org/druid-io/druid/jobs/134358186

👍 after travis


scan4all won't get updates anymore?

scan4all I really use this program a lot. It was a very useful program. But I haven't been using it for a long time since it hasn't received updates. Has the development of this program ended?

I hope more people can participate and contribute to open source together


Add missing permissions to kafka-instances script

statefulset and pod permissions were absent, this caused the commands that query kafka state to fail.

nod to last time the checks were made
https://github.com/openshift/managed-scripts/pull/41
what was missing there that you caught now?

yes, indeed, sorry for the churn on this.
For this mistake to have slipped through there must have been some mistake made with the application of the testing procedure when rachel did the original work.    She was using https://source.redhat.com/groups/public/openshiftplatformsre/wiki/backplane_scripts    "How to test the script before creating the PR." .  I'm unsure why she didn't see these errors.
In addition we are still having problems running ocm backplane testjobs which we are still working through separately. (@StevenTobin )

Hopefully the last
But I think I found a permission issue I notes
After that I'll lgtm

/lgtm
/approve


meld segfault on yosemite (10.10.4)

Related to https://github.com/Homebrew/homebrew/issues/36980, I see the following after running meld
Couldn't bind the translation domain. Some translations won't work.
'module' object has no attribute 'bindtextdomain'
2015-07-30 10:48:48.193 Python[28065:262485] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.

And then when I close meld, python crashes.
Segmentation fault: 11

The problem report states:
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

I installed meld by:
brew tap homebrew/x11
brew install meld

Interestingly enough, this is 100% reproducible by clicking the red "x" on the window, but if I use CMD-Q, there is no segfault.

Looks like an upstream issue.
Could you file a bug over this at Gnome bugzilla?
Thanks

I've been seeing this problem since moving to the 10.11 beta in July, and I see the same thing just running upstream meld (with homebrew's libgtk).  I finally posted my output and stack trace to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=756225

I had the same issue and a similar stack trace to bprodoehl. Running brew reinstall gtk+3 --with-quartz-relocation fixed the problem.

Works! Fixes file diffs. Still get a segfault on close (if I click the red X), but this is a major improvement.

The delete-event segfault may be something that should be passed up to the creators of meld. A simple way of solving it is to patch meldwindow.py. Add import sys to the top, and then sys.exit(1) to the end of on_delete_event at about line 303, it will remove the segfault, although the memory may not be properly cleaned.

@dabeale this solved the issue for me. Thanks. Do you think this is an upstream issue with meld and that they should make that change in the main repo?

Yes. There is always the possibility that if you issue a patch it will not be fixed. Since the leak is only caused on exit of the main window it could be worse. It may also be a bug in pygobject, or gtk.

Looks like this is the same issue as https://github.com/Homebrew/homebrew/issues/44722.

As far as I am concerned, this issue is not fixed. Although the manual change in meld's source by @dabeale fixes the issue.
Could this issue be reopened?

Fixed in meld 3.14.2 (#162)


Updated 'Spanish Argentina' translation.

Updated 'Spanish Argentina' translation.

Thanks once again @leomartinez, Will merge in for the next patch release.

We are heavly using Bookstack at work. Having little time to collaborate with the code, I can at least keep the translation up to date.


⚠ Bofrost.be has degraded performance

In 23a80b8, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 938 ms

Resolved: Bofrost.be performance has improved in eeb1320.


Deployment

User Story
AS AN employee with access to sensitive data
I WANT to randomly generate a password that meets certain criteria
SO THAT I can create a strong password that provides greater security
Acceptance Criteria
GIVEN I need a new, secure password
WHEN I visit the website using the URL
THEN I can access my website with no errors

completed


Thed docs link seems to be broken?

The link to the docs seems to be broken, any one else having the same issue?

Seems like all of gitbook is down 😬

https://twitter.com/GitBookStatus


tab component

@keybase/react-hackers implements the tab nav (for inside components)
https://zpl.io/2hBKb7
Zeplin:

tnx @MarcoPolo , keep forgetting the class thing

:+1: not sure about the tab width instead of just having it expand

(but we can change later)

in the current design they're fixed width and don't actually take the whole container. but we could limit the size based on the container. i say we move this in and fix up the component as we need it


Add organisation member as collaborator

Hi!
I want to know why we can't add an organisation member as a collaborator on a repo that is not on his organisation.
E.g. :

User X is in Org X
Repo Y is in Org Y
I can't add User X as collaborator to Repo Y

My use case :
I have :

A <brandname> organisation that contain

all my developers users
applications repositories

An infrastructure organisation that contain

my sysadmin users
2 repos :

Saltstack formulas : server deployment code
Saltstack pillars : parameters for the deployment code

Pillars contains sensitive data and I don't want developers to be able to access it, So  I can't add them to infrastructure organisation, I just want them to be able to access with read-only permissions the  repo Saltstack formulas

All Repos under an Organization have to be managed by Teams.
You create a Team in infrastructure-organization, give it Read-only access. Add all devs to that Team, and give that Team access to Saltstack formulas. Done :smiley:

I didn't clicked on the repo list :)
I've found the setting now


Github Actions workflow requires Jenkins access

Do you have a CI build flow that does not require access to your Jenkins setup?

Hi, sorry for the late reply. We are in the process of removing Jenkins. What is it that you are looking for wrt to the CI build flow?


[Proposal] ActiveRecordCollection

It would be nice if ActiveQuery returns ActiveRecordCollection instead of Array. Example:
/* Order has many OrderItems */
/* OrderItems has many Items */
$order->items->add($item);
/*OR*/
$order->items->build($post);

foreach($order->items->each() as $item) { /*do some with collection item*/ }

UPD: by customizing  the collection class, developers will have opportunity to create own collection methods
UPD2: we can achive that without breaking compatibility by asCollection method in the ActiveQuery class. Example:
return $this->hasMany(Product::className(), ['catalog_id' => 'id'])
                  ->asCollection(ActiveRecordCollection $optionalCollectionClassThere);
/* OR */
Product::find()->asCollection()->all();

https://github.com/yiisoft/yii2/blob/master/framework/data/BaseDataProvider.php#L101

@lynicidn
This is not the same.
Collection class can help avoid code like this:
$catalog = Catalog::findOne($catalogId);
$product = new Product;
$product->load($post);
$product->link('catalog', $catalog);

instead of:
$catalog = Catalog::findOne($id);
$catalog->products->build($post);

like in Rails.

https://github.com/yiisoft/yii2/issues/2423

https://github.com/mdmsoft/yii2-ar-behaviors/blob/master/RelationBehavior.php
$catalog = Catalog::findOne($catalogId);
$catalog->product = $post;

@mdmunir , it's almost the same but only for one use case - adding new elements.
Collections provide more flexible solution. One more example:
$product->images->deleteAll();
$product->images->buildMultiple($post);
$catalog->products->updateMultiple($post);
$cart->lineItems->remove($lineItemId);

it's Repository Pattern, not just behavior of Strategy.
Also we can use ArrayAccess with collections.
@Ragazzo thx, but this is not really the same proposal.
I'm still waiting for @qiangxue or @samdark to discuss.

What would be the benefits?

@Sammaye
I'm already provide examples.
Purpose is to encapsulate relations inside of domain logic and provide simpler the relations interaction interface.
Also this can help with database interaction, improve speed of application, and show how to do right.

Just the ability to add multiple functions? Most of this is handled by DB queries that are custom to the PHP logic

No, look at Rails.

// delete all items
$order->items = [];

// build multiple
$order->items = [$item1, $item2, $item3];

// add new item
$items = $order->items;
$items[] = $item4;
$order->items = $items;

// remove 1 item
$items = $order->items;
unset($items[1]);
$order->items = $items;

@mdmunir thx for examples, but i still can't add some custom logic, because this is not OOP. Also i can't incapsulate logic.

Closing since there's #10806 w/ active discussion.


Can’t update on RPI ZeroW

Describe The Bug:
Can’t update Homebridge-config-ui-x
Getting command failed error
To Reproduce:
Press update
Expected behavior:
It updates
Logs:

USER: pi
Homebridg DIR:
/usr/local
homebridae-confio
CMD:
endo
-E -n pm install
-g homebridge-config-ui-x@latest
SETTINGS
pm WARN deprecated<EMAIL_ADDRESS>This release contains a breaking change fr
Up om 0.3.1 but otherwise functions properly. Please read the changelog on Github to learn
more.
pm ERR! process terminated
pm ERR! signal SIGTERM
© Uodate Availa pm ERR! A complete log of this run can be found in:
npm ERRI
Homebridg
/home/pi/.npm/_logs/2022-01-17T20_27_57_8467-debug-0.log

Cleaning up pm cache, please wait..
pm cache cleared, please try updating homebridge-config-ui-x again.

Show the Homebridge / Homebridge Config UI X logs here.

¡17/01/2022, 15:42:05] (Homebridge VI] pm cache clear command executed with exit code 0
[17/01/2022, 15:42:06] (Homebridge UI] Command failed. Please review log for details.

Homebridge Config:

{
    "bridge": {
        "name": "Homebridge DE1E",
        "username": "0E:8C:79:57:DE:1E",
        "port": 51887,
        "pin": "571-83-259"
    },
    "accessories": [
        {
            "name": "showerDummy",
            "stateful": false,
            "reverse": false,
            "time": 180000,
            "resettable": false,
            "accessory": "DummySwitch"
        },
        {
            "name": "OfficeDummy",
            "stateful": false,
            "reverse": false,
            "time": 7200000,
            "resettable": false,
            "accessory": "DummySwitch"
        },
        {
            "name": "WashroomDummy",
            "stateful": true,
            "reverse": false,
            "time": 1000,
            "resettable": false,
            "accessory": "DummySwitch"
        }
    ],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "auth": "form",
            "theme": "dark-mode",
            "tempUnits": "c",
            "lang": "auto",
            "platform": "config"
        },
        {
            "options": {
                "username": "”,
                "password": "",
                "accessId": "",
                "accessKey": "",
                "lang": "en",
                "projectType": "2",
                "appSchema": "smartlife",
                "countryCode": 1,
                "debug": true
            },
            "name": "TuyaPlatform",
            "platform": "TuyaPlatform"
        },
        {
            "name": "TplinkSmarthome",
            "addCustomCharacteristics": true,
            "deviceTypes": [
                "plug",
                "bulb"
            ],
            "platform": "TplinkSmarthome"
        },
        {
            "name": "SwitchBot",
            "credentials": {
                "openToken": "",
                "notice": "Keep your token a secret!"
            },
            "options": {
                "devices": [
                    {
                        "deviceId": "d3:BC:54:0E:BE:68",
                        "configDeviceType": "Bot",
                        "ble": false,
                        "bot": {
                            "mode": "press",
                            "deviceType": "switch"
                        }
                    }
                ],
                "refreshRate": 30,
                "pushRate": 1
            },
            "platform": "SwitchBot"
        },
        {
            "name": "Govee",
            "username": "",
            "password": "",
            "apiKey": "9aa7c1a4-27e0-4518-8d3d-42fc96386802",
            "platform": "Govee"
        },
        {
            "devices": [
                {
                    "name": "My LG TV",
                    "ip": "<IP_ADDRESS>",
                    "mac": "ec:6c:9a:51:73:f5",
                    "pollingInterval": 5,
                    "volumeLimit": 50,
                    "volumeControl": "both",
                    "channelControl": true
                }
            ],
            "platform": "webostv"
        },
        {
            "email": "",
            "password": "",
            "countryCode": "CA",
            "deebotNames": [
                "Shamu"
            ],
            "refreshTimer": 0,
            "publishBipSwitch": true,
            "publishSwitch": true,
            "publishFan": true,
            "publishMotionDetector": true,
            "publishAutoSwitch": true,
            "publishEdgeSwitch": true,
            "publishSpotSwitch": true,
            "publishSpotAreaSwitches": [
                "2",
                "0",
                "3,4,5",
                "7,8",
                "11,13"
            ],
            "publishAreaSwitchesAsSeparateDevices": false,
            "showInfoLogs": true,
            "platform": "DeebotEcovacs"
        }
    ]
}

Screenshots:

Environment:

Node.js Version: 16.13.1
NPM Version: 8.1.2
Homebridge Version: 1.3.9
Homebridge Config UI X Version: 4.41.2
Operating System: Raspbian
Process Supervisor: hb-service

Same behavior here! Waiting for some solution ASAP!

Same behavior here also on my Pi Zero. Updating the plugins through homebridge-ui-x also fails as well as updating homebridge itself!
However updating using ssh works well.


Document the Word doc generation caveats

The Word doc format produced by Metanorma is called Word MHT, which is not a typical Word file.
Caveats:

The Table of Contents must be updated using real Microsoft Word to have correct page numbers
The Metanorma generated Word document cannot be read by OpenOffice / LibreOffice.

In order to convert the .doc file into a typical Word file (.doc or .docx), you need to follow these steps:
https://github.com/riboseinc/html2doc#converting-document-output-to-native-word-docx
This information should be put on metanorma.com.

There's information in https://github.com/riboseinc/metanorma-iso/blob/master/docs/outputs.adoc that presumably needs to go to metanorma.com as well.

Has been addressed: https://www.metanorma.com/author/topics/building/output-formats/


Automatically use available fieldmaps if IntendedFor is missing

The BIDS spec lists that the IntendedFor field is optional:
"The IntendedFor field is optional and in case the fieldmaps do not correspond to any particular scans it does not have to be filled."
Whenever I don't include it in the fmap's .json files, I get "No fieldmaps found or they were ignored".  It would seem as if any found fmap's should, by default, be applied to anything in the func folder.  Or, am I misreading that in the spec?
Craig

This could be done within this function:
https://github.com/poldracklab/sdcflows/blob/fcc9ee0d242aaf52e460afa80b5c7c1bfa1a8c63/sdcflows/workflows/base.py#L260-L292

Maybe it would make sense to only automatically assign fieldmaps to images if the shim settings match?

How would you check that from the BIDS input?

Heudiconv/PyDicom both will write out a "ShimSetting" field with a series if values like
	"ShimSetting": [
		1716,
		-3891,
		-210,
		392,
		14,
		-78,
		161,
		4	],

In my experience, this gets configured at the scanner console. The shim settings used when acquiring the fieldmap are copied for the scans the fieldmap is intended to correct. I'm not sure if this is siemens specific, but it's been useful for sanity-checking the quality of distortion correction. Often the person scanning will forget to copy the shim settings from the fieldmap into their dwi or bold and the distortion correction is a bit off.
The other problem is that "ShimSetting" is not part of BIDS..

Quick question about this thread, has there been any updates on this feature? I saw that it got moved to pipelines, but wanted to make sure there was something I wasn't missing since this thread was initiated 2 years ago
I'm currently trying to apply gradient echo field maps (I have 1 phasediff image and 2 magnitude images) that I'm trying to apply fieldmap correction to several functional runs, without the "IntendedFor" argument in the .json files for the fieldmaps.
I've been trying to follow along with the documentation in sdcflows (https://fmriprep.readthedocs.io/en/stable/sdc.html), and tried using the --force-syn argument, but for some reason, it's still not automatically detecting my fieldmaps. I looked at the function that @oesteban posted above with the "fieldmap_wrangler" function that seems to address this, but It's not working clearly for me. Fwiw, According to my logs, the bidsvalidator does detect the fieldmaps, so I know that they are detected. However, they don't seem to be applied.
Below is a snippet of code I used to call fmriprep. Please let me know if I'm posting this in the wrong thread -- since it seems that SDC seemed to have migrated to a different workflow.
`
#!/bin/bash
#SBATCH -t 08:00:00
#SBATCH --mem=128GB
#SBATCH -N 1
#SBATCH -n 32
#SBATCH --account=carney-ashenhav-condo
#SBATCH -J TCB-fmriprep-fieldmap
#SBATCH --output slurm-logs/TCB-fmriprep-log-%J.txt
#SBATCH --error slurm-logs/TCB-fmriprep-error-%J.txt
#--------- CONFIGURE THESE VARIABLES ---------
#bids_root_dir=/gpfs/data/ashenhav/mri-data     # based on oscar path
bids_root_dir=/gpfs/data/bnc/scratch
participant_labels=("tcb2004")
investigator=shenhav                            # investigator
study_label=201226                              # study label
fmriprep_version=20.0.1                         # check /gpfs/data/bnc/simgs for the latest version
#nthreads=64 				                    # heuristic: 2x number of cores
#--------- FMRIPREP ---------
singularity run --cleanenv
--bind ${bids_root_dir}/${investigator}/study-${study_label}:/data
--bind /gpfs/scratch/dyee7:/scratch
--bind /gpfs/data/bnc/licenses:/licenses
/gpfs/data/bnc/simgs/fmriprep-${fmriprep_version}.sif
/data/bids /data/bids/derivatives/fmriprep-${fmriprep_version}-nofs
participant
--participant-label ${participant_labels}
--fs-license-file /licenses/freesurfer-license.txt
-w /scratch/fmriprep
--stop-on-first-crash
--nthreads 64
--write-graph
--force-syn
#--use-syn-sdc
#--fs-no-reconall
`

No, fMRIPrep does not use fieldmaps that don't use IntendedFor at this point.

Yep, the problem is that the heuristics to assign fieldmaps and target data without the IntendedFor are quite complex and subject to opinion (e.g. the comments about shimming above).
This will take a while to implement if ever done. I only can see a push in the context of diffusion MRI, where the BIDS specs fall short in some cases. And even there, the most straightforward path would be to extend the possible uses of IntendedFor in BIDS.

After thinking this through, and having bids-standard/bids-specification#622 in the works, I think this issue can be moved back to fMRIPrep.


Can't add it to HomeAssistant

Problem/Motivation
How do I add this add-on to HA? I can't seem to add it as repository.

Maybe it is helpful to put this in the readme: https://github.com/erik73/hassio-addons


identification Ax1 and Ax2, 2D acquisition

Hi,
In 2D scan, with two actuators I find that is difficult to remember  which we select Ax1 and Ax2 to write start, stop and step values without mistake. because of only select Ax1 and Ax2 by clicking first and second.

Is it possible to add small information link to the selection of these actuators, on "Ax1" and "Ax2" to remember during experiment who's who ?

Commit 628ed3930220feeeaa23d1ec855bf7c9d32d044f is adding a tooltip to values of each axis depending on the actuator selection:


feat: homepage update with blog page

[X] Update navbar, showing blog menu in right and about in the left side
[X] Get latest blog post and showing as banner in homepage

[X] Initial blog index

@urmauur My nitpicks:
Featured Article

Should be full width
Can we explore making it neutral tone (vs. high contrast) - see https://sfcompute.com/ as an inspiration
Goal is to highlight it, without overpowering the rest of the page

@dan-homebrew pushed new commit with changes

update banner announcement full width
using neutral tone color

will wotk with @eckartal once he back online regarding leadgen

@urmauur I'm going to merge this first, and we'll handle the Partner button later


2023-10-05 (05 Oct 2023) - Morphir Project Meeting

Date
Thursday 05 Oct 2023 - 11am ET / 3pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve previous meeting minutes - https://github.com/finos/morphir/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info

https://zoom.us/j/95452540437?pwd=TEk0bitJcVFsK3lrWVZCYmxyTm5LZz09
Meeting ID: 954 5254 0437
Passcode: 778814

Dial-in

Find your local number: https://zoom.us/u/aFGSSGV9x

Github Repo: https://github.com/finos/morphir/
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

James McLeod / FINOS

Kicki Frisch, turntabl

Richard Wagener / Cognizant

Edward Peters/Capital One

Ronald Ssebalamu / FINOS

Test suite - https://github.com/finos/morphir-scala/tree/main/examples/morphir-elm-projects/evaluator-tests

Stephen Goldbaum @ Morgan Stanley


corrected overlapping logic

Resolves #57

Can one of the admins verify this patch?

Jenkins, add to whitelist.

Merged build triggered.

Merged build started.

Merged build finished. Test PASSed.

I think the correct interpretation should be "overlaps partially"
So it should be
((viewRegion.start <= LongColumn("start")) && (viewRegion.end > LongColumn("start"))) || ((viewRegion.start < LongColumn("end") && (viewRegion.end >= LongColumn("end"))

@erictu  I don't think above one works in all cases. But again the change I made does handle partial overlaps.
anyways i wrote a small test case - https://gist.github.com/nikhilRP/91b762ebac8795f8fb05

@nikhilRP ah, yes, good catch. We didn't consider the case where B fully contains A.

@nikhilRP Before we merge this, can you add in this overlapping logic for the other file loads we do as well?

@erictu  will do

Merged build triggered.

Merged build started.

Merged build finished. Test PASSed.

@erictu updated the overlapping logic for variants, features and alignments

Thanks @nikhilRP! I have manually committed this as https://github.com/bigdatagenomics/mango/commit/369164878f058384523ceddad93606f103ac6ef0.


Command ID for moving cursor to next line?

Hi,
I want to be able move my cursor up, down, left, right without using the arrow keys. Is there a command id for that?  If not, do you have any example of how to achieve that?
Thanks

Editor.prototype.setCursorPos in /src/editor/Editor.js is the API you need.

Thank you very much for the quick response.
I believe there's no key binding for this, right?
What would be the approach if I want to use this API? Should I create my own extension?

You need to create your own extension to start with.
First get the editor instance.
var EditorManager = brackets.getModule("editor/EditorManager"),
      editor = EditorManager.getCurrentFullEditor();

then set cursor position.
editor.setCursorPos(1, 4);

Thank you!


SqlFacet missing?

I'm looking for the SqlFacet class. It appears to be in the old System.Data.SqlClient package for the full .Net framework and in .Net Core but was not available when referencing System.Data.SqlClient from a Net Standard library.
Similarly, it appears SqlFacet is missing from this repository.
Can someone explain why it has not been accessible from Net Standard when referencing System.Data.SqlClient and why it is not in this repository now?
Is there a plan to add SqlFacet to this repository and to make it accessible when referencing Microsoft.Data.SqlClient from a Net Standard library?
Thanks!

Hi @agilenut
From initial research, I think we should be able to support it, it's probably missed out here.
We will acknowledge this as an enhancement and plan to support it soon.
I'm not sure why it was not available in .NET Standard for S.D.S, but will look more into it and update again.

Hi @cheenamalhotra. Thanks for marking that as an enhancement. I'll keep an eye on this.
For now, we will likely multi-target netstandard2.0 and net48 and will include a definition of the attribute class in our project wrapped in #if / #endif to get netstandard to compile.

The missing attribute is also mentioned here, way back in 2017, where it is one of many missing things flagged as "TypesMustExist".
https://github.com/dotnet/SqlClient/issues/17

Conjectire. SqlFacet is used in SQLCLR and the netcore version of this library can't be used in SQLCLR so it was removed in porting netfx to netcore. Because netstandard was union of netcore and netfx it being missing in netcore probably caused it to be omitted from netstandard. While the type can be added it won't have any use in this library as far as I know. What are you intending to do with it?

Conjecture. SqlFacet is used in SQLCLR and the netcore version of this library can't be used in SQLCLR so it was removed in porting netfx to netcore. Because netstandard was union of netcore and netfx it being missing in netcore probably caused it to be omitted from netstandard. While the type can be added it won't have any use in this library as far as I know. What are you intending to do with it?

We have a library of lookup types that act similar to enums which need to available to SQLCLR as well as logic in various nuget libraries and other business logic. Having the attribute in netstandard would allow us to target our types library to netstandard, thus allowing the other libraries and business logic that references it to be in netstandard. The actual attribute will not be used in netstandard but having it available allows us to multi-target both uses cases (4.8 for SQLCLR and netstandard for our calling libraries).

The type won't be added to netstandard, there will be no further versions of netstandard now that .net5 and later are unifying the bcl for netcore and mono. It's trivial to add it to this library's netstandard build but it'll never be usable. If that is enough then I'm fine with adding it I just want you to be aware it's not going to be usable for anything but satisfying type presence, which sounds like it might be all you need.

@Wraith2 - Yes, that is all that I need. And, yes, I'm not expecting the type to become a part of the netstandard definition. I just need it in a package that targets netstandard so that I can reference it from a netstandard project.


[FEATURE] Add "RepectSafeArea" option on Banner Tab

Is your feature request related to a problem? Please describe.
https://github.com/Poing-Studios/godot-admob-ios/issues/22
https://github.com/Poing-Studios/godot-admob-android/issues/115
Describe the solution you'd like
Add an option to respect the Android and iOS Safe Area for both platforms, it is recommended to always leave this option true, as AdMob recommends this: https://developers.google.com/admob/ios/x-ad-rendering
Banner ads must be placed in the "Safe Area" to avoid being obscured by rounded corners, sensor housing, and the Home indicator.

There is a small detail to point out: While working on this implementation, I noticed that Android's Safe Area is different from iOS, for example, Android's bottom Safe Area is usually 0 pixels, while iOS's is approximately 45 pixels. Same thing with the top, on Android it's 76 pixels and on iOS it's 100 pixels this can cause a difference in UI on devices.


chore(master): release 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-12-23)
Features

gcm_crack: magic poly repr (dde8b1c)
gcm_crack: works but wrong (aad1e21)

Bug Fixes

gcm_crack: fix magic_p (5f4387d)
gcm_crack: IT WORKS (0d983be)
superpoly: edf is now sorted (8d1170c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.4.0
:sunflower:


Teamwork integration not working

OS version: macOS 12.6
Browser version: 106.0.5249.119 Chrome
Extension version: 2.0.17

Relevant integration (if any):
Teamwork - teamwork.com
🐛 Describe the bug
Teamwork updated their UI and the button is no longer there. Our "Where can I find the button" page shows the following screenshot:

I just created a Teamwork account to test and the UI is completely different with the button not visible:

Expected behaviour
We should show the button in the new UI of Teamwork
Steps to reproduce

Steps to reproduce the behaviour:

Go to extension settings > Integrations
Enable the Teamwork integration
Go to the Teamwork web app
Check if you can find the button

Other details or context
Related to a user complaining, intercom case 🔗

Also not working for me. Any updates?

I'm seeing the issue as well, I'm assuming it's because of Teamwork updating their UI, but I really do not like using their time tracking app as I have automations setup for billing via Toggl Track.

OS version: Windows 10
Browser version: 112.0.5615.50 Chrome
Extension version: 3.0.2


Updated Open File Snippet to use OpenFileDialog.OpenFile()

Summary
The current snippet uses File,ReadAllText which is wrong since the documentation is for OpenFileDialog.OpenFile()
Fixes dotnet/docs#7500

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


Move tlogserver logic to client (i.e. : remove tlogserver)

I propose to remove tlogserver and moves the logic to client
I'm  thinking of this because there are many changes since the original tlog server at https://github.com/g8os/tlog:

In Go : the initial implementation was in C++ and Nim. Being in Go, make it possible to implement it entirely in nbd
using 0-stor : 0-stor reduces some complexities in the tlog server code
no dpdk : i never heard plan toward dpdk anymore, CMIIW. Even dpdk would be slower than direct func call or Go channel
one tlog server for one nbdserver setup.

PROS
The advantages to move the logic to client:

faster, as there is no communication overhead between tlog client and server
reduces point of failure
simpler communication : golang channel  vs async TCP / dpdk. No need to handle for unordered, lost, and  corrupted logs.
current server is only an entity that buffer the log and send it to 0-stor
no need to create redundancy

In short: the logic and thus the code will be simpler, performance will be better. Simpler logic tend to more reliable
CONS

additional loads on capnp aggregation creation. notes that it is only the aggregation, the client itself already creates capnp block when sending the block to server
additional loads on aggregation processing : encrypt, compress, erasure encoding
load spike when doing aggregation processing

I think the additional load can be solved by giving more resource (CPU, RAM) which can be taken from resource for tlog servers.
NOTES
While tlogserver logic itself will give extra loads to nbdserver, we need to take into account that tlog client also not a simple entity which send data to server, it needs to:
- buffers the logs and retry it if needed
- encoded capnp block

interesting proposition indeed. I think it make sense if we consider then now the tlog server is really doing nothing more then receiving data from nbdserver and most of the logic belong the in the 0-stor client.
although I don't think we should focus on this at the moment, I'll move to milestone beta-1 see if we have time to there and it gives us more time to really understand the impact of such a decisions.
On more cons I see is that if we remove the tlog server, we can't then spread the load anymore. In the future when zero-os will be used in real distributed scheme. we could imagine to have the tlog server running on a completely different location then the nbdserver.

On more cons I see is that if we remove the tlog server, we can't then spread the load anymore. In the future when zero-os will be used in real distributed scheme. we could imagine to have the tlog server running on a completely different location then the nbdserver.

This argument is enough to close this issue :)
As one of the motivation is :

one tlog server for one nbdserver setup.

There is no real reason why you would limit it to one tlogserver for one nbdserver forever. What I mean is that sure things might get more complex, but it should definitely be possible to have multiple tlogservers working concurrent, as all they do is process blocks and form aggregations. I know this will only be possible once problems X and Y are solved, but if I remember correct all problems ever mentioned with it, they all were solvable.


My COCO dataset JSON file contains empty list of segmentations...

          My COCO dataset JSON file contains empty list of segmentations...

WARNING:root:Segmentation in COCO is experimental
Traceback (most recent call last):
  File "/home/frta/.local/bin/label-studio-converter", line 33, in <module>
    sys.exit(load_entry_point('label-studio-converter', 'console_scripts', 'label-studio-converter')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/frta/projects/***-pose-estimation/label-studio-converter/label_studio_converter/main.py", line 189, in main
    imports(args)
  File "/home/frta/projects/***-pose-estimation/label-studio-converter/label_studio_converter/main.py", line 171, in imports
    import_coco.convert_coco_to_ls(
  File "/home/frta/projects/***-pose-estimation/label-studio-converter/label_studio_converter/imports/coco.py", line 219, in convert_coco_to_ls
    item = create_segmentation(
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/frta/projects/***-pose-estimation/label-studio-converter/label_studio_converter/imports/coco.py", line 54, in create_segmentation
    segmentation = annotation['segmentation'][0]
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range

Originally posted by @frippe75 in https://github.com/HumanSignal/label-studio/issues/2806#issuecomment-1792769373

If you still have this problem, take a look at this commit:  https://github.com/HumanSignal/label-studio-converter/commit/dec9c58c983b1f0ff2efd49af37e05aa600f4480
Check your coco.py file and apply the change yourself, this solved the issue for me.
Cheers

hey @ajmalrasi thanks for making this issue, I'm moving to close this because it's a duplicate as you pointed out but I've reopened the other issue. It would be good to have a single thread of discussion for all issues relating to the same or similar COCO json issues


Suggestion: for pipe:: write the signal number to the pipe

It would be nice to have a version of the pipe:: module which indicates which signal was triggered by writing the corresponding i32 constant to the pipe, giving users an elegant way to identify which signal was sent and only use one pipe for all signals.

This is not supported for the reason it is an obvious solution that is subtly wrong.
As the signal handler can't block, it needs to simply give up when the read end does not keep up and it is full. So imagine you receive SIGUSR1 8 million times which fills the pipe. Then you receive SIGUSR2, but that doesn't fit. The other end wakes up and sees the 8 million SIGUSR1s, but the SIGUSR2 is lost forever. If you use separate pipes, or if you use out of atomic bound flags, you lose the information of how many times each signal was received, but not a whole kind of signal. That is fine, as even kernel can coerce multiple same signals together.
Furthermore, as i32 is 4 bytes long, you could get a partial write ‒ get only eg. 3 bytes written and 1 thrown away. That would confuse the reader end furthermore.
Therefore, I don't like exposing an interface that is basically a footgun.


Node downgrade to what's supported by appveyor

Description
Downgrading node minor version to align with appveyor. Also set the max memory for the nodejs process.
Motivation and Context
Trying to see what can fix the nightly builds in appveyor.
Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

@kytwb - this PR is also required (to fix the appveyor side of the CI process)


CF-checker warnings when following example H.11 (Atmospheric sounding profiles)

In the example H.11 (version 1.7) the variable profile is given with
variables:
      int profile(profile) ;
          profile:cf_role = "profile_id";

which is fine with me, but the checker produces warnings - could this be changed in next checker versions to INFO?
Using CF Checker Version 3.1.1
Checking against CF Version CF-1.7
Using Standard Name Table Version 69 (2019-10-15T14:39:18Z)
Using Area Type Table Version 9 (07 August 2018)
Using Standardized Region Name Table Version 4 (18 December 2018)
------------------
Checking variable: profile
------------------
WARN: (3): No standard_name or long_name attribute specified
WARN: (3.1): units attribute should be present

Not entirely sure what's happened here as there appears to be no section 9 in the conformance document to cover checking of discrete geometries although the checker does implement checks.  I am happy to take an action to sort this out.

Specific to the warnings above as far as I can see the current recommendation is that all variables except boundary, climatology and grid mapping variables specify a long_name or standard_name.  So I think that warning is correct.  Warnings are just there to flag recommendations, they don't mean that the file fails CF compliance.

Chapter 9.5 of the CF Conventions document states:

Where feasible a variable with the attribute cf_role should be included.  The only acceptable values of cf_role for Discrete Geometry CF data sets are timeseries_id, profile_id, and trajectory_id.   The variable carrying the cf_role attribute may have any data type.

It does not explicitly state that the variable should have no standard_name but I would interprete these sentences in the way that the mentioned variable should have only the attribute cf_role.
However, the variable with attribute cf_role is not mentioned in conformance document chapter 3 (http://cfconventions.org/Data/cf-documents/requirements-recommendations/requirements-recommendations-1.7.html):

Recommendations:

All variables should use either the long_name or the standard_name attributes to describe their contents. Exceptions are boundary and climatology variables.

Thus, it should be explicitly stated in chapter 9.5 of the CF conventions document that standard_name and long_name are not needed for the cf_role-variable. Additionally, chapter 3 of the CF conformance document should be extended by this case.
@RosalynHatcher Is explicitly mentioned that the grid mapping variable does not have a standard_name or long_name? I mean: the grid mapping variable should not have these attributes but I cannot find it in the text (neither CF Conventions nor CF conformance). Actually, this information should also be in chapter 3 of the conformance document -- shouldn't it?
Should I submit a new issue on this topic?

Dear all
Daniel @neumannd's comment reveals some inconsistency in the CF standard and conformance document. Section 3 of the conformance document has the recommendation, which he quoted,

All variables should use either the long_name or the standard_name attributes to describe their contents. Exceptions are boundary and climatology variables.

but that recommendation isn't made in the preamble to Section 3 of the conventions, which says only that CF supports long_name and introduces standard_name. The conformance statement should belong instead Section 3.2, which says

it is highly recommended that either [the long_name] or the standard_name attribute ... be provided to make the file self-describing

Unfortunately this text doesn't say what kinds of variable the statement applies to! To clarify this, I suggest that

We delete the existing recommendation at the start of Section 3 of the conformance document.

We insert instead a recommendation for Section 3.2: "All data variables and variables containing coordinate data should use either the long_name or the standard_name attributes to describe their contents."

We amend the third sentence of Section 3.2 of the conventions document to read "But it is highly recommended that either this or the standard_name attribute defined in the next section be provided for all data variables and variables containing coordinate data, in order to make the file self-describing," where the bold is new.

This is consistent with Appendix A. The long_name and standard_name can also be used for boundary variables, so long as the attribute value is identical to the one on the parent coordinate variable. That's shown by "BI'' in Appendix A, and was clarified in the latest version of CF.
Those statements also answer @neumannd's question about the grid mapping variable. That kind of variable does not have these attributes, according to Appendix A. Hence the checker would not give a warning if they are absent.
Section 9.5, about coordinates and metadata for discrete sampling geometries, says "one of the coordinate or auxiliary coordinate variables of a discrete sampling geometry should have an attribute named cf_role." That is, the cf_role variable is a variable containing coordinate data, so according to Appendix A and Section 3 the cf_role variable is recommended to have either a standard_name or a long_name. That's consistent with what @RosalynHatcher said.
In summary, I don't think there's a problem with the warnings that @GeyerB reported. The checker is correct. But there are some defects in the documents, as outlined above. Therefore I am going to close this issue now, since it was raised as a question and nothing has been said for over four years, with thanks to the contributors, and I will open a new defect ticket. Please reopen this issue or begin a new one if you think the question hasn't been answered.
Jonathan


JFX: Menu entries are not correctly found

In JavaFx apps, "clicking" on a menu entry works but clicking on the resulting sub-menu items doesn't.
JRE 8 - u 51

Which selector did you try when selecting the sub-menu items? text:, type: or some complex selector?

It was "text:" but I'll double check to see if it wasn't more than one component with that text on the screen at that moment.

Please make sure to use a good "narrowing" selector, something like matchingAll( "type:MenuItem", "text:My Text" ). If this does not work right, I'll have a look, it's possible the search algorithm missed something.

We've tried it with the id selection fxer.clickOn("#aboutMenuItem") and it DOES move the mouse near the element but not on the element. It also could be clicking outside it.
We've also tried with a selector: fxer.clickOn(matchingAll("type:MenuItem", "text:About")) and it does not work because we get an exception like this:
com.athaydes.automaton.GuiItemNotFound: Could not locate ComplexSelector(matchType:ALL,queries:[type:MenuItem, text:About])
Doing fxer.getAt("#aboutMenuItem") to get a reference of the element works but fxer.getAt(matchingAll("type:MenuItem", "text:About")) throws the same exception:
com.athaydes.automaton.GuiItemNotFound: Could not locate ComplexSelector(matchType:ALL,queries:[type:MenuItem, text:About])

Ok, thank you for all the details. I will fix this as soon as I can. Should release a fix in a few days.

Confirmed the bug. The y-coordinate of the menuItem is incorrect. Affects Java 7 and Java 8.

This bug was caused by a workaround for a JavaFX bug in which the Scene's position was reported incorrectly.
You can remove that workaround by running the following Groovy code in the same JVM where your tests will run:
com.athaydes.automaton.FXAutomaton.metaClass.static.getScenePosition = { Node node ->
    new Point( node.scene.x as int, node.scene.y as int )
}

I will publish a fix for this soon, if you prefer to wait.

Hi, we will wait for a proper release because we've already implemented a quite fragile workaround: clicking based on relative coordinates.
Thank you for your effort!

Released the fix. Change your Automaton version to 1.2.2.

Fix confirmed.


test: add curl features check

Add a test ensuring curl was built with the expected features.
Signed-off-by: Taras Roshko<EMAIL_ADDRESS>Description: Add a test ensuring curl was built with the expected features.
Risk Level: Low.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.

A way to automatically verify #8154.


hourglass-RuntimeError: The size of tensor a (13) must match the size of tensor b (14) at non-singleton dimension 3

Hi,
I got the same issue than  #3654 when i use hourglass backbone for cornetnet and centripetalnet:
RuntimeError: The size of tensor a (13) must match the size of tensor b (14) at non-singleton dimension 3
I tried different input sizes without succes.
Thanks!

This might because the image is not correctly padded, e.g., padded to be divisible by 16 but the image is downsampled by stride 32 in the backbone. You may check that.

I tried 1024x1024 and 512x512 images but it still doesn't work

I alse meet the same issure at HRNet   the size of tensor a(47) must match the size of tensor b(48) at non-singleton dimension @ZwwWayne  use your model to test

Please use the error template to report the issue in detail. The current information does not provide much useful information to reproduce or debug the bug.


Science Isn’t Broken

Hey!
I am curious if you have the data you used for the Science Isn't Broken article (https://fivethirtyeight.com/features/science-isnt-broken/). Particularly, the datasets you used for Hack Your Way To Scientific Glory figure. I know you mention where you got it, but do you have the "organized" form you used for it available?
It really is an excellent article.

You may be able to find the data you're looking for in this file.


Using ACE when Bicep modules are stored within a private container registry

Bicep has the potensial to store modules within a private module registry.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/modules#private-module-registry
However, in order for ACE to restore, authentication is needed with suffcient permission.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-cli#restore
How could we make this work?

Hey @BenjaminEngeset!
If I understand that correctly, to restore modules from private module registry, the principal used in ACE needs to have sufficient permissions to do that. That should be a matter of using proper RBAC role for it and is outside of ACE's scope (one thing that could be added is support for passing Bicep config file).
However, what ACE doesn't support today, is running bicep restore <bicep-file> before compiling Bicep to ARM Templates, so remote modules are downloaded. That's something I can plan for 1.3, so most likely would be available in 1.3-beta1 version within two weeks.

I checked docs one more time, and they state, that:

Typically, you don't need to run restore because it's called automatically by build.

That leads me to a question - have you tried to run described scenario or is it a generic question? :)

@kamil-mrzyglod Let me try to explain further, it was a rather bad description from me.
The contexts created and the context used for authentication does not work for the container, as it is running isolated. It is not inherited.
There must be a way we can perhaps use environment variables and get the running container to authenticate with the security principal that will make the bicep build work as expected.
Example that does not work since the container is running fully isolated:
- task: AzureCLI@2
    displayName: Cost forecasting
    inputs:
      azureSubscription: spn
      scriptType: bash
      scriptLocation: inlineScript
      inlineScript: |
        docker run -e AZURE_CLIENT_ID=$(ClientId) -e AZURE_TENANT_ID=$(TenantId) -e AZURE_CLIENT_SECRET=$(Secret) -v $(pwd)/modules:/app/modules thecloudtheory/azure-cost-estimator:latest $(TestFilePath) $(SubscriptionId) $(ResourceGroupName)

I think I get it. When containerized, ACE is not running in authenticated environment, hence restoring is not working as Bicep commands are not run inside context of authenticated principal. Makes sense.
I see two options:

Dockerfile needs to be changed, so it runs az login before executing ACE's executable
Before compiling Bicep, ACE runs az login, which will guarantee, that the context of authenticated user is available

I'll think about which solution would work the best and come back to you shortly.

@kamil-mrzyglod Great, thanks for your swift responses!

@BenjaminEngeset I'll give a try new Docker image first, if that's not working as expected, I'll go for the second solution. Most likely it'll available in the upcoming week.

@BenjaminEngeset I'll give a try new Docker image first, if that's not working as expected, I'll go for the second solution. Most likely it'll available in the upcoming week.

Great! I'll test it for GH and ADO soon as it is available.

@BenjaminEngeset for complete bug report, could you please add output you're getting from the pipeline, when ACE is running?

@BenjaminEngeset for complete bug report, could you please add output you're getting from the pipeline, when ACE is running?

2023-04-30T16:34:54.6001437Z Unable to find image 'thecloudtheory/azure-cost-estimator:latest' locally
2023-04-30T16:34:55.7865203Z latest: Pulling from thecloudtheory/azure-cost-estimator
2023-04-30T16:34:55.7868114Z 26c5c85e47da: Pulling fs layer
2023-04-30T16:34:55.7868303Z 6df469f23ae1: Pulling fs layer
2023-04-30T16:34:55.7868489Z 7e979fe76393: Pulling fs layer
2023-04-30T16:34:55.7868656Z 6c9b5f8b63cb: Pulling fs layer
2023-04-30T16:34:55.7868808Z 9081d6669561: Pulling fs layer
2023-04-30T16:34:55.7868971Z 6b86c97df054: Pulling fs layer
2023-04-30T16:34:55.7869140Z 95270bef9dd1: Pulling fs layer
2023-04-30T16:34:55.7869304Z 86f60e6f4545: Pulling fs layer
2023-04-30T16:34:55.7869469Z 9e129b2dea2a: Pulling fs layer
2023-04-30T16:34:55.7869629Z 03f2beeb33ff: Pulling fs layer
2023-04-30T16:34:55.7869792Z 95270bef9dd1: Waiting
2023-04-30T16:34:55.7869945Z 86f60e6f4545: Waiting
2023-04-30T16:34:55.7870099Z 9e129b2dea2a: Waiting
2023-04-30T16:34:55.7870248Z 03f2beeb33ff: Waiting
2023-04-30T16:34:55.7870386Z 6c9b5f8b63cb: Waiting
2023-04-30T16:34:55.7870537Z 9081d6669561: Waiting
2023-04-30T16:34:55.7870686Z 6b86c97df054: Waiting
2023-04-30T16:34:56.1810749Z 6df469f23ae1: Verifying Checksum
2023-04-30T16:34:56.1811092Z 6df469f23ae1: Download complete
2023-04-30T16:34:56.2986125Z 26c5c85e47da: Verifying Checksum
2023-04-30T16:34:56.3015784Z 26c5c85e47da: Download complete
2023-04-30T16:34:56.4789076Z 6c9b5f8b63cb: Download complete
2023-04-30T16:34:56.5068803Z 7e979fe76393: Verifying Checksum
2023-04-30T16:34:56.5072605Z 7e979fe76393: Download complete
2023-04-30T16:34:56.6809702Z 9081d6669561: Verifying Checksum
2023-04-30T16:34:56.6819384Z 9081d6669561: Download complete
2023-04-30T16:34:56.9004637Z 95270bef9dd1: Verifying Checksum
2023-04-30T16:34:56.9005267Z 95270bef9dd1: Download complete
2023-04-30T16:34:57.2038824Z 86f60e6f4545: Verifying Checksum
2023-04-30T16:34:57.2039753Z 86f60e6f4545: Download complete
2023-04-30T16:34:57.4929702Z 6b86c97df054: Verifying Checksum
2023-04-30T16:34:57.5011436Z 6b86c97df054: Download complete
2023-04-30T16:34:57.6944439Z 26c5c85e47da: Pull complete
2023-04-30T16:34:57.7501502Z 9e129b2dea2a: Verifying Checksum
2023-04-30T16:34:57.7501781Z 9e129b2dea2a: Download complete
2023-04-30T16:34:58.0298477Z 03f2beeb33ff: Verifying Checksum
2023-04-30T16:34:58.0298706Z 03f2beeb33ff: Download complete
2023-04-30T16:34:59.1846857Z 6df469f23ae1: Pull complete
2023-04-30T16:34:59.9826161Z 7e979fe76393: Pull complete
2023-04-30T16:35:00.0355830Z 6c9b5f8b63cb: Pull complete
2023-04-30T16:35:00.0884279Z 9081d6669561: Pull complete
2023-04-30T16:35:00.4060934Z 6b86c97df054: Pull complete
2023-04-30T16:35:00.7103396Z 95270bef9dd1: Pull complete
2023-04-30T16:35:01.2555444Z 86f60e6f4545: Pull complete
2023-04-30T16:35:01.9160329Z 9e129b2dea2a: Pull complete
2023-04-30T16:35:02.4602007Z 03f2beeb33ff: Pull complete
2023-04-30T16:35:02.4645113Z Digest: sha256:d97e91d639a1fefa8b1c8caa52c3eda0080e645605d84871f0d737585c6bf885
2023-04-30T16:35:02.4663068Z Status: Downloaded newer image for thecloudtheory/azure-cost-estimator:latest
2023-04-30T16:35:02.9671886Z
2023-04-30T16:35:02.9672213Z                                               .***      ***
2023-04-30T16:35:02.9672635Z                                    ,    ***.********,****
2023-04-30T16:35:02.9672967Z                                      **********************
2023-04-30T16:35:02.9673209Z                                *    ************. ***********  *
2023-04-30T16:35:02.9673513Z                              ///   *******, ****  ////////////******
2023-04-30T16:35:02.9674146Z                                .//************ ///// /////////********
2023-04-30T16:35:02.9674446Z                            ///////// ********///////// //////.********    (,
2023-04-30T16:35:02.9674744Z                      .   ///////////// **** ////////////,////******* ( (/
2023-04-30T16:35:02.9674968Z                        *////////////////   ////////////////  ** ((((((((((((
2023-04-30T16:35:02.9675184Z                         ///,  */////////.   **************,    ((((((((((((((
2023-04-30T16:35:02.9675400Z                        ///////////////.(((((((,******** ///// (((((( (((((((((
2023-04-30T16:35:02.9675704Z                        ///////////// ((((((((((((   ////////// ((((((((((*((((
2023-04-30T16:35:02.9675947Z                         ////////// ((((((((((( ((    //////////(((((((((((((((
2023-04-30T16:35:02.9676256Z                     //   /////// (((((( (((((((((((((((( ///////(((((((((((((
2023-04-30T16:35:02.9676774Z                        //   /  ( ((((((((((((((((,((((((((((.////(((((((((  ((
2023-04-30T16:35:02.9677071Z
2023-04-30T16:35:02.9677292Z                                   ACE (Azure Cost Estimator) [1.2.0]
2023-04-30T16:35:02.9677467Z
2023-04-30T16:35:02.9678050Z General help: https://github.com/TheCloudTheory/arm-estimator/discussions
2023-04-30T16:35:02.9678530Z Bugs & issues: https://github.com/TheCloudTheory/arm-estimator/issues
2023-04-30T16:35:02.9678734Z
2023-04-30T16:35:02.9678997Z ------------------------------
2023-04-30T16:35:02.9679085Z
2023-04-30T16:35:02.9689722Z Run configuration:
2023-04-30T16:35:02.9689861Z
2023-04-30T16:35:02.9690177Z -> Scope: ResourceGroup
2023-04-30T16:35:02.9690725Z -> Susbcription Id: xxx
2023-04-30T16:35:02.9691160Z -> Resource group: xxx
2023-04-30T16:35:02.9691642Z -> Template file: modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep
2023-04-30T16:35:02.9692050Z -> Deployment mode: Incremental
2023-04-30T16:35:02.9692377Z -> Threshold: Not Set
2023-04-30T16:35:02.9692719Z -> Parameters file: Not Set
2023-04-30T16:35:02.9693049Z -> Currency: USD
2023-04-30T16:35:02.9693389Z -> Generate JSON output: False
2023-04-30T16:35:02.9693965Z -> Silent mode: False
2023-04-30T16:35:02.9694305Z -> Redirect stdout: False
2023-04-30T16:35:02.9694665Z -> Disabled detailed metrics: False
2023-04-30T16:35:02.9695009Z -> Generate HTML output: False
2023-04-30T16:35:02.9695366Z -> HTML output filename: Not Set
2023-04-30T16:35:02.9695711Z -> Dry run enabled: False
2023-04-30T16:35:02.9696046Z -> Cache disabled: False
2023-04-30T16:35:02.9696223Z
2023-04-30T16:35:02.9696483Z ------------------------------
2023-04-30T16:35:02.9696667Z
2023-04-30T16:35:02.9704056Z -> Attempting to compile Bicep file using Bicep CLI.
2023-04-30T16:35:05.5480895Z [Error] /app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(25,43) : Error BCP192: Unable to restore the module with reference "br:xxx.azurecr.io/operationalinsights/la-workspace:1.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:05 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: 91892e23-3412-4986-80f2-f7ca753c8f77x-ms-ratelimit-remaining-calls-per-second: 333.266667Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(34,29) : Error BCP192: Unable to restore the module with reference "br:xxx.azurecr.io/storage/storageaccounts:3.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:04 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: a31b6a66-a8cd-4f83-b427-39733fc40333x-ms-ratelimit-remaining-calls-per-second: 333.316667Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(52,38) : Error BCP192: Unable to restore the module with reference "br:nomgtpbicepacrcr.azurecr.io/dbforpostgresql/servers:1.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:04 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: d3afa785-66ff-4be7-b072-be5f58e9c663x-ms-ratelimit-remaining-calls-per-second: 333.3Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(65,40) : Error BCP192: Unable to restore the module with reference "br:nomgtpbicepacrcr.azurecr.io/dbforpostgresql/servers-database:1.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:04 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: 796f8c68-f1d0-4ea9-826b-a19bcf396552x-ms-ratelimit-remaining-calls-per-second: 333.283333Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(81,5) : Error BCP062: The referenced declaration with name "modDependencyPostGreSqlDatabase" is not valid./app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(84,30) : Error BCP062: The referenced declaration with name "modDependencyPostGreSqlServer" is not valid./app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(85,28) : Error BCP062: The referenced declaration with name "modDependencyStorage" is not valid./app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(100,39) : Error BCP192: Unable to restore the module with reference "br:nomgtpbicepacrcr.azurecr.io/dbforpostgresql/servers:1.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:04 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: d3afa785-66ff-4be7-b072-be5f58e9c663x-ms-ratelimit-remaining-calls-per-second: 333.3Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(113,41) : Error BCP192: Unable to restore the module with reference "br:xxx.azurecr.io/dbforpostgresql/servers-database:1.0.1": Service request failed.Status: 401 (Unauthorized)Content:{"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}Headers:Server: openrestyDate: Sun, 30 Apr 2023 16:35:04 GMTConnection: keep-aliveX-Ms-Correlation-Request-Id: 796f8c68-f1d0-4ea9-826b-a19bcf396552x-ms-ratelimit-remaining-calls-per-second: 333.283333Strict-Transport-Security: REDACTEDContent-Type: text/plain; charset=utf-8Content-Length: 134/app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(124,5) : Error BCP062: The referenced declaration with name "modDependencyPostGreSqlDatabase1" is not valid./app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(127,30) : Error BCP062: The referenced declaration with name "modDependencyPostGreSqlServer1" is not valid./app/modules/dbforpostgresql/servers-securitypolicies/test/main.test.bicep(128,28) : Error BCP062: The referenced declaration with name "modDependencyStorage" is not valid.
2023-04-30T16:35:05.5529766Z [Error] There was a problem with processing template.
2023-04-30T16:35:05.5626840Z Unhandled exception: System.Exception: Exception of type 'System.Exception' was thrown.
2023-04-30T16:35:05.5627159Z    at ACE.Program.<>c.<<Main>b__1_15>d.MoveNext() in /src/ace/Program.cs:line 67
2023-04-30T16:35:05.5627464Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5627708Z    at System.CommandLine.Invocation.AnonymousCommandHandler.InvokeAsync(InvocationContext context)
2023-04-30T16:35:05.5627989Z    at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
2023-04-30T16:35:05.5628294Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5628544Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
2023-04-30T16:35:05.5628858Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5629095Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
2023-04-30T16:35:05.5629404Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5629648Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
2023-04-30T16:35:05.5629948Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5630196Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
2023-04-30T16:35:05.5630505Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5630740Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
2023-04-30T16:35:05.5631046Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5631293Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
2023-04-30T16:35:05.5631586Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5631828Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
2023-04-30T16:35:05.5632132Z --- End of stack trace from previous location ---
2023-04-30T16:35:05.5632533Z    at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()
2023-04-30T16:35:05.7011283Z ##[error]Script failed with exit code: 1
2023-04-30T16:35:05.7022854Z [command]/usr/bin/az account clear
2023-04-30T16:35:06.2043503Z ##[section]Finishing: Cost forecasting

Hey @BenjaminEngeset, I believe it can be solved without much of changes needed on ACE's side. In fact, that's not a bug at all :)
Private modules for Bicep should be correctly restored when ACE runs estimation as you need to provide environment variables, which are used by Azure.Identity to authenticate the principal you're using. The problems comes from the default credential precedence Bicep is using - it only looks for credentials stored via Azure CLI / Azure PowerShell.
To allow your pipeline to restore your modules, make sure, that you put bicepconfig.json file in the same directory as your Bicep files. Here's an example of such file:
{
  "cloud": {
    "currentProfile": "AzureCloud",
    "profiles": {
      "AzureCloud": {
        "resourceManagerEndpoint": "https://management.azure.com",
        "activeDirectoryAuthority": "https://login.microsoftonline.com"
      }
    },
    "credentialPrecedence": [
      "Environment"
    ]
  }
}

I set credentialPrecedence to use environment variables only, but for most cases you should have other methods available here as well. See https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config-modules#configure-profiles-and-credentials.
Once that file is available, Bicep CLI embedded in ACE's image will fetch correct credentials and restore modules. Let me know if it doesn't work for you.

@kamil-mrzyglod Gotcha.
I tried this now, having the configuration file at the root of the repository with environment variables having the precedence.
Same issue occurs, have you tried this out?
I'll definitely try to troubleshoot more as I'm super keen to make this work.
Is there a way we can ensure that ACE's Bicep CLI is taking advantage over the configuration file? I'm really unsure if the embedded Bicep CLI ACE is using has access to the configuration file.

@BenjaminEngeset Yeah, I tested that using my own pipeline. But that file is not supposed to be at the root of your repo - it must be in the same directory as the Bicep file you want to estimate.
I could add a log message though, which would be displayed if the config file is found.

@BenjaminEngeset Yeah, I tested that using my own pipeline. But that file is not supposed to be at the root of your repo - it must be in the same directory as the Bicep file you want to estimate.
I could add a log message though, which would be displayed if the config file is found.

@kamil-mrzyglod Thanks, it works well now! You were right, tip of the repository is a no go.
To customize values, create this file in the directory where you store Bicep files. You can add bicepconfig.json files in multiple directories. The configuration file closest to the Bicep file in the directory hierarchy is used.
Again thanks for identifying this configuration mistake such swiftly. Now it's rock on :shipit:

Great, happy I was able to help!


Fresh Google Oauth2 and 401 error.

Hello,
I got an acces_token from my android Application like
{"email":_@gmail.com","userId":"****************","displayName":"__","gender":"male","imageUrl":"https://lh3.googleusercontent.com/-**********************/x4oPC0_/photo.jpg?sz=50","givenName":"_","familyName":"__","ageRangeMin":21,"oauthToken":"_*******************************"}
And I created an Oauth2 account on google :

Unfortunately when I declare the
clientID: GOOGLE_CLIENT_ID,
clientSecret: GOOGLE_CLIENT_SECRET
and add the "oauthToken" I have a 401 error
Would you tell me if this behavior is normal and tell me what I missed ?
Thank you very much.

What was the solution?

I didn't find a solution

I found a solution, not sure if its the same problem.
You're getting a 401 when you're sending your token to the backend?

@oreporan  would've been nice to actually post your solution here even if it wasn't the same problem


Decoding multiple times a message raising SchemaParseException

Class : https://github.com/Azure/azure-sdk-for-java/blob/8f60b758143ce86e3c3e494ccba61676766ecb1e/sdk/schemaregistry/azure-data-schemaregistry-apacheavro/src/main/java/com/azure/data/schemaregistry/apacheavro/AvroSerializer.java#L165
Scenario: when AvroSerializer.decode() is called more than once for same message type, it is raising following exception since Schema.Paser keeps names already parsed.
org.apache.avro.SchemaParseException: Can't redefine: com.azure.data.schemaregistry.apacheavro.generatedtestsources.PlayingCard

	at org.apache.avro@1.10.1/org.apache.avro.Schema$Names.put(Schema.java:1542)
	at org.apache.avro@1.10.1/org.apache.avro.Schema$Names.add(Schema.java:1536)
	at org.apache.avro@1.10.1/org.apache.avro.Schema.parse(Schema.java:1655)
	at org.apache.avro@1.10.1/org.apache.avro.Schema$Parser.parse(Schema.java:1425)
	at org.apache.avro@1.10.1/org.apache.avro.Schema$Parser.parse(Schema.java:1413)
	at com.azure.data.schemaregistry.apacheavro/com.azure.data.schemaregistry.apacheavro.AvroSerializer.parseSchemaString(AvroSerializer.java:115)
	at com.azure.data.schemaregistry.apacheavro/com.azure.data.schemaregistry.apacheavro.AvroSerializer.decode(AvroSerializer.java:165)

Reproduction:
Edit AvroSerializerTest class for following test:
@Test
    public void encodesAndDecodesObject() {
        // Arrange
        final AvroSerializer registryUtils = new AvroSerializer(false, parser,
            encoderFactory, decoderFactory);

        final PlayingCard expected = PlayingCard.newBuilder()
            .setPlayingCardSuit(PlayingCardSuit.DIAMONDS)
            .setIsFaceCard(true)
            .setCardValue(13)
            .build();

        // Using the raw message encoder because the default card.getByteBuffer() uses BinaryMessageEncoder which adds
        // a header.
        final byte[] encoded = registryUtils.encode(expected);
        final byte[] schemaBytes = expected.getSchema().toString().getBytes(StandardCharsets.UTF_8);

        // Act
        final PlayingCard actual = registryUtils.decode(ByteBuffer.wrap(encoded), schemaBytes,
            TypeReference.createInstance(PlayingCard.class));

        **final PlayingCard thisWillBeFailed = registryUtils.decode(ByteBuffer.wrap(encoded), schemaBytes,
            TypeReference.createInstance(PlayingCard.class));**

        // Assert
        assertCardEquals(expected, actual);
    }

@srnagar could you please take a look?

@ankursaini2006 Could you please let us know what is the scenario where you would need to decode a named schema multiple times? Also, note that AvroSerializer is an internal type that is not for public use. The decode method is an implementation that shouldn't be called outside of this library.
Regarding the change in unit test noted above, the exception is coming from the underlying Apache Avro package. This is working as expected and is according to the Avro spec where you cannot register named schemas multiple times. See Avro spec that states that the schema with the same name cannot be registered twice.
Quoting the spec:

A schema or protocol may not contain multiple definitions of a fullname.

Given that the Apache Avro library doesn't allow parsing the named schema string multiple times, this exception is an expected behavior and isn't considered an issue that needs to be fixed. If you still have further questions regarding the unit test, please let us know.

@srnagar In our scenario, we are sending events from an application using avro serializer. When consuming these events, each event is being deserialised using spring bean SchemaRegistryApacheAvroSerializer. The first message is correctly deserialised since it is the first time Schema.Parser is called and names are created. While deserialising the second message the exception is raised since the both messages are received with same schemaId and Schema.Parser is static & keeps all the names in its state.
In the unit test, I tried to show the same scenario using same instance of AvroSerializer and decoding more than one message

@ankursaini2006 thanks for clarifying that you are deserializing through SchemaRegistryApacheAvroSerializer. This type is public and shouldn't throw this error when multiple events with the same schema are deserialized. I have created a PR to fix this bug and will be released in our next release cycle in April.


[add]allow list value for source option

Codecov Report

Merging #14 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   51.91%   51.91%
=======================================
  Files          26       26
  Lines         495      495
  Branches       38       38
=======================================
  Hits          257      257
  Misses        236      236
  Partials        2        2

Impacted Files
Coverage Δ

rplugin/python3/curstr/info.py
49.35% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Dashboard hangs when refreshing screen with F5

When you refresh the dashboard (or in some instances) change the dates, the data gets really weird and/or the browser hangs.

The appears to be caused by the fact that responses from the first query still come back to the browser and are treated as being part of the new query (caused by the refresh)

@torinfo @FayCross just been testing this with our page types demonstrator and not sure I can replicate although noticed a few things:
For me F5 closes the dashboard (with and without the browser console open) so not sure about the reference to F5 here.
Changing the date with this example, even by a day or week, does seem to take a long time to update but that may be a problem with this large project with a lot of data?
So will leave you @torinfo to check if what you reported here is still an issue.


REQUEST: @joshvanl as approver in dapr/dapr

GitHub Username
@joshvanl  as approver in dapr/dapr
PRs:
https://github.com/dapr/dapr/pulls?q=author%3Ajoshvanl+ (Total: 43 Merged)
Highlights:

Identity overhaul (though not merged due to test coverage)

https://github.com/dapr/dapr/pull/6171
https://github.com/dapr/dapr/pull/6179
https://github.com/dapr/dapr/pull/6193

Integration tests/API bug fixes

https://github.com/dapr/dapr/pull/6327
https://github.com/dapr/dapr/pull/6340
https://github.com/dapr/dapr/pull/6463
https://github.com/dapr/dapr/pull/6573

1.11.1, 1.10.8 patch releases

https://github.com/dapr/dapr/pull/6555
https://github.com/dapr/dapr/pull/6556

runtime/control plane refactoring for hotrloading/graceful shutdown

https://github.com/dapr/dapr/pull/6584
https://github.com/dapr/dapr/pull/6382
https://github.com/dapr/dapr/pull/6232
https://github.com/dapr/dapr/pull/6323
https://github.com/dapr/dapr/pull/5831
https://github.com/dapr/dapr/pull/5860
https://github.com/dapr/dapr/pull/5859
https://github.com/dapr/dapr/pull/6037

SDK test jobs

https://github.com/dapr/dapr/pull/6310
https://github.com/dapr/dapr/pull/6309
https://github.com/dapr/dapr/pull/6304

Placement unit test improvement

https://github.com/dapr/dapr/pull/6308
https://github.com/dapr/dapr/pull/6079
https://github.com/dapr/dapr/pull/6026
https://github.com/dapr/dapr/pull/6037

PRs reviewed: https://github.com/dapr/dapr/pulls?q=-author%3Ajoshvanl+involves%3Ajoshvanl+ (Total: 25)
Issues created: https://github.com/dapr/dapr/issues?q=is%3Aissue+author%3Ajoshvanl+ (Total: 7)
Issues from others contributed to: https://github.com/dapr/dapr/issues?q=is%3Aissue+-author%3Ajoshvanl+involves%3Ajoshvanl (Total: 19)
Sponsor: @artursouza

+1 binding

+1 binding

We have enough approving votes. Closing


Better node install documentation

Many system package managers install node in a way that breaks npm install -g for wrangler due to permissions errors. Using sudo to get past this is currently broken since npm will run our post-install script as nobody, and even if it ran as root users couldn't access root's home directory.
This PR provides better documentation on how to install node (using a version manager) so users aren't confused by this issue.
I would appreciate feedback on the exact language used here.

Closes https://github.com/cloudflare/wrangler/issues/242

bonus points if you instruct the user as to how to learn where their install is and what it was installed with...

merge at will!