Hide any path not allowed in the breadcrumb

Hi, i´m using the breadcrumb and when i give a random route, like 'dsadsad' and the page is using a path like
{ path: '**', component: PagenotfoundComponent }
the breadcrumb shows dsadsad,
we want to hide any path like this.
i have use
`import { Component, OnInit } from '@angular/core';
import {BreadcrumbService} from 'ng2-breadcrumb/ng2-breadcrumb';
@Component({
selector: 'app-pagenotfound',
templateUrl: './pagenotfound.component.html',
styleUrls: ['./pagenotfound.component.css'],
providers: [BreadcrumbService]
})
export class PagenotfoundComponent implements OnInit {
constructor(
private breadcrumbService: BreadcrumbService
) { }
ngOnInit() {
this.breadcrumbService.hideRoute('/a-zA-Z09');
}
}`
in the app.modules we import the module like this
import {Ng2BreadcrumbModule} from 'ng2-breadcrumb/ng2-breadcrumb';
any ideas? the path still showing.
Thanks.

Have you tried .* as the regex? The other way might be to use ActivatedRouteSnaphot to specifically target the 404 path (so as not to pollute the breadcrumbs for subsequent navigation)

I've tried a little "dirty" solution that works:
export class AnyComponent implements OnInit {
  hideBreadcrumb = false;

  constructor(private breadcrumbService: BreadcrumbService,
              private router: Router,
              private activatedRoute: ActivatedRoute) {
  }
  ngOnInit() {
    this.router.events
      .filter(event => event instanceof NavigationEnd)
      .map((e) => this.activatedRoute)
      .map(route => {
        while (route.firstChild) {
          route = route.firstChild;
        }
        return route.component;
      })
      .subscribe((componentClass: any) => {
        this.hideBreadcrumb = ((new componentClass()) instanceof NotFoundComponent);
      });
  }
}

And in the template:
<breadcrumb [style.display]="hideBreadcrumb ? 'none' : 'block'"></breadcrumb>


Ajax Layered Navigation Filter Randomly error in Hyva theme

I have installed the module using composer with below command
composer require "shellpea/magento-advanced-elasticsuite-catalog":"^1.2.1"
It seems all good while i am doing test on product listing page with shop by filters i see following errors on random result.
Even i did checked the inspect element the component is there.
Reference error is attached.

@rahul-navigate Hi, please check new version 1.2.2

Hi @AlexDroomer
Thanks for sharing update.
As suggested, I did tried to upgrade version using composer to 1.2.2
composer require "shellpea/magento-advanced-elasticsuite-catalog":"^1.2.2"
But it seems 1.2.2 version is not available in composer
Problem 1
- Root composer.json requires shellpea/magento-advanced-elasticsuite-catalog ^1.2.2, found shellpea/magento-advanced-elasticsuite-catalog[1.2.x-dev] but it does not match your minimum-stability.
Problem 2
- Root composer.json requires hyva-themes/magento2-shellpea-advanced-elasticsuite-catalog dev-main -> satisfiable by hyva-themes/magento2-shellpea-advanced-elasticsuite-catalog[dev-main].
- hyva-themes/magento2-shellpea-advanced-elasticsuite-catalog dev-main requires shellpea/magento-advanced-elasticsuite-catalog * -> found shellpea/magento-advanced-elasticsuite-catalog[v1.0.0, v1.2.0, v1.2.1] but it conflicts with your root composer.json require (^1.2.2).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Ref :
so do i need to test with dev-main branch ?

HI @AlexDroomer , Thanks for quick update and yes now version is available on composer.
Thanks Again :)


testing: make TestConcurrentHandleRegion stable

Signed-off-by: lhy1024<EMAIL_ADDRESS>
What problem does this PR solve?
fix #1861
What is changed and how it works?
Check List
Tests

Unit test

/rebuild

@disksing @nolouch @Luffbee PTAL

So, the root of #1861 is there is too many goroutines?

@Luffbee the root should be too slow, but i have no idea to speed up it.


ETCM-8833 Update tests to run from Partner-Chains Repo

…container
Description
Add your description here, if it fixes a particular issue please provide a
link
to the issue.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages.
[x] New tests are added if needed and existing tests are updated.
[x] Relevant logging and metrics added
[x] CI passes. See note on CI.
[x] Any changes are noted in the changelog.md for affected crate
[x] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG Partner Chains developers to do this
for you.

I'm pretty sure you can replace tools_host with binary-host-service.sc.svc.cluster.local and then this will never need to be updated. Should avoid using IP addressing

I'm happy with the structure and the changes to CI, all looks good to me as long as it looks good to @chrispalaskas and @rsporny


Python: Bug: 05-using-the-planner.ipynb sample has dead links

Describe the bug
05-using-the-planner sample has a dead link in the section about the plan object model as well as right after in the sequential planner section.
To Reproduce
Steps to reproduce the behavior:

Go to 05-using-the-planner.ipynb
Click on the links in the 'The Plan Object Model' and 'Sequential Planner'
See error

Expected behavior
The links work
Platform

Language: Python

@beman9 Thanks for reporting. We are working on deprecating the planners. We will get this cleaned up when that work is handled.


Radio button content needs some editorial updates

A review of the radio button's Usage and Style pages was carried out as part of an accessibility review. Most of the consideration are to do with consistency of information provided in the Usage content, and what look like a few editorial problems as a result of pasting information from Checkbox directly into Radio button usage.
A few design and implementation considerations for the Radio button component have been flagged in the Radio button usage.pdf  document. Note that there are comments from both Jess Lin and myself (and I sometimes respond to something she said).
This document should be opened in Adobe Acrobat Reader (not in a browser) so that all the comments and replies  can be reviewed.

Website
When to use

[ ] Form: Add selectable tiles and data tables.

[ ] Selection in lists: I feel like we can omit this, we already indicate you can use radio buttons in forms and I think this is trying to say a similar thing.

When not to use

[ ] Change terminology to not mention "lists" and instead reference a radio button group in a form.

Live demo

[ ] This is a problem with code. The code example needs to be updated in the live demo. This should be resolved by #11860

Anatomy

[ ] Change first line item to beGroup label (optional).

Content
Group labels (optional)

[ ] First sentence: Omit "If necessary...".
[ ] Second sentence: Revise content to suggest being concise with wording when using it for instructional purposes.
[ ] Fourth sentence: Move and work into the first sentence about group labels.
[ ] Fifth sentence: This is a development question we need to resolve.

Radio button labels

[ ] Second sentence: Omit this sentence until we figure out if we want helper text for radio buttons.

Interactions
Keyboard

[ ] Revise paragraph to incorporate Michael Gowers feedback:

This is inaccurate. Normally, a user never needs to use the Space with a radio button, as the focus and selection state are synchronized. If a user lands on a radio button set WITHOUT a default indicator, they would press Space once to select that one. Or they could press an arrow key which would automatically select the next radio button. There is no means of unselecting a selected radio button with the spacebar. You just select a different one.

Screenreader

[ ] Omit this section.

Default selection

[ ] Omit this section.

Related
Radio button versus toggle switch

[ ] Change paragraph to read as follows:

Toggle switches are preferred when the user options are limited to two choices—on and off or true and false. By comparison, radio buttons can have many other options.


Merge pull request #91 from jflachman/kerek_branch

Merge pull request #88 from jflachman/main

Let see


Example for verify token doesn't work

Please, check the example for the console project.
The example doesn't work.
I guess Azure devops services change something in tokens and now this example outdated.

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

ID: add23736-f0a9-2cc7-8bd2-4b8720898552
Version Independent ID: 3f763c47-317d-a32a-37dd-6507d3f630b5
Content: Auth and Security - Azure DevOps
Content Source: docs/extend/develop/auth.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@titans2016 Sorry for the delay in responding. We've assigned this task to the relevant author.

+1 this doesn't work.
I did everything exactly like in the document, but end up with
WWW-Authenticate →Bearer error="invalid_token", error_description="The signature key was not found"
being returned. I have no clue how to fix this

@plitokpikin - Please consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow

I've made a topic on developercommunity on this issue.
https://developercommunity2.visualstudio.com/t/Authorization-using-JWT-token-not-workin/1391662
I've also got better understanding of it, it relates to symmetric/assymmetric encryption mismatch between client and the server.

Thanks @plitokpikin and @titans2016. I've just checked the Developer Community ticket and it looks like they're investigating. I've commented on the ticket and asked them to @mention me when there's an update, so I can update the article, too. So, I'm closing this issue and will work off of the Developer Community ticket. Please let me know if you have further questions about this article. Thank you!

@chcomley this documentation is still out-dated and doesn't work. So why is this issue "closed"?


Remove alias for docopt-go

docopt-go do not need alias

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.
Your Pull Request can earn you credit at DigitalOcean! See http://docs.deis.io/en/latest/contributing/hacking/#digitalocean-credit for details.

This change is not necessary. I'm sorry--Deis V1 is only receiving critical bug fixes and changes identified to implement our LTS release.


Schema contract testing

Description of changes:
Added sample tests for the pattern "Event-driven architecture - schema and contract testing"
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Assigning to @brnkrygs for now, feel free to re-assign


Added Bednarska Szkoła Realna

https://bsr.edu.pl/

Course link: https://www.bsr.edu.pl/service/techniczno-informatyczna/

@Cyber-Repocord Thank you for your patience while waiting for a review and processing your request. Pull request merged.

Thanks!


mangacopy.comic Broken

Extension information
mangacopy.comic
Steps to reproduce
download mangacopy.comic extension
open any comic/search any comic
throws error/No search results found.

Miru version
1.8.1
Other details
URIError: expecting hex digit
at decodeURIComponent (native)
at decodeUnicode (:26)
at detail (:73)
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

@hualiong 为什么移除了加密和解密的代码，这好像使得拷贝漫画这个插件不工作了。

额，原来会导致不工作吗？因为Miru有内置CryptoJS库，所以不需要在拓展中再次引入，我之前写的拓展都是可以正常运行😥


How many submissions from one team are allowed?

Hi @preduct0r, thanks for your question! You are free to update submissions until the deadline, but only one submission (system) per task is allowed for each team.
If you developed multiple systems as part of the track, or just want to compare across different hyperparameters/random seeds, we encourage you to report your findings in a system paper to submit to the DSTC 11 workshop!


怎么用SBR提升我已经训练好的106关键点检测模型呢？

If you are submitting a feature request, please preface the title with [feature request].
If you are submitting a bug report, please fill in the following details.
Which project are you using?
SAN or SBR or TS3 or others?
Issue description
Provide a short description.
Code example
Please try to provide a minimal example to repro the bug.
Error messages and stack traces are also helpful.
System Info
Please copy and paste the output from our
environment collection script
(or fill out the checklist below manually).
You can get the script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

You can use your pre-trained landmark detection model as the initialization for SBR.
To optimize your model with SBR, you need (1) labeled training data (which could be the training data for your pre-training) and (2) unlabeled video data (you can collect them on your own). An example is at here: https://github.com/D-X-Y/landmark-detection/tree/master/SBR#improving-the-detector-by-sbr
Please feel free to re-open the issue if you have more questions.


add support for CRD annotations and labels in kube-derive

This PR adds support for setting annotations and labels on kube-derive generated CRDs.
Motivation
Writing Cluster API providers requires setting specific labels on the CRD: https://cluster-api.sigs.k8s.io/developer/providers/contracts#api-version-labels
Solution
New annotation and label fields are added to kube-derive which can take a tuple of two strings as an argument.

I rewrote the solution so the values are now passed as a two-string tuple. Also added the annotation support.


Detach stream before serializing PSR-7 response

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
fixes #81

Documentation
-

License
MIT

This might be enough to fix https://github.com/php-http/cache-plugin/issues/81
Feel free to amend at will :)

thanks a lot! i continue this in #84 as i rebased on 1.x to get the fixes for phpspec.


How to re-pair?

Hi,
i entered the wrong pin number, then i have not been able to redo the pair. I removed the .credentials.tv file but he did not ask for a pin again.
How can i get this fixed?

Removing the .credentials.tv should be sufficient. I think it only starts the pairing process when you try to execute a command.
Try running tv.sh and then execute the command 5 for example. It should start the pairing process when it sees there's no .credentials.tv file.


Chispstack initialization status

Hi all,
Any way to know when the application has finished its initialization? I tested two different approaches: watching the logs and watching the __diesel_schema_migrations table. They work but I am not happy with those approaches.
Cheers.

I think the /health endpoint should provide you with such indication. See the configuration:
# Monitoring related configuration.
[monitoring]

  # interface:port to bind the monitoring endpoint to (optional).
  #
  # /health  - Returns 200 in case the healthchecks have passed.
  # /metrics - Returns metrics which can be scraped by Prometheus.
  #
  # If not set, this endpoint will be disabled.
  bind=""

https://www.chirpstack.io/docs/chirpstack/configuration.html


ECR: updating tags ignored

Describe the bug
Updating an existing ecr does ignore changes to the tags.
Steps to reproduce

build current image for ECR from main branch
create a ECR repo using the controller
update the ECR by changing/adding/removing tags
logs in controller show no problem, but ECR repo tags are unchanged

Expected outcome
Tags should be updated.
Environment

Kubernetes version: 1.17
Using EKS (yes/no), if so version? yes, eks.4
AWS service targeted (S3, RDS, etc.): ECR

/lifecycle frozen

tags are now supported for ECR repository custom resource
https://github.com/aws-controllers-k8s/ecr-controller/commit/81f131f6e61de5dbcf62df105a5cc1d416d77a48


README

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

Added WIP of README file into Main Branch, will conclude final edition shortly.

Added final updates to the README.md file to the remote branch.


Add restriction about the argument order.

I think the following code doesn't make sense.
def foo(x=10 , y)
  x + y
end

foo(10)

Because 1) I need to guessing which param I'm passing to when I calling the method. 2) If you think some argument is most needed, you should put it in the front.
So in Goby we need to write the code like this
def foo(y, x=10)
  x + y
end

foo(10)

And I'll try to add some mechanism to check the parameter's order according to it's type (required or optional).
BTW there is a Ruby style guide that supports my opinion on this. Thanks for @hachi8833 for finding this reference.

I agree with this: Ruby's current handling of parameters/arguments with default values are mess, and simplifying it is good for Goby.
The point is how to standardize this without getting developer's antipathy.
Possible ways to restrict the order of args with default values:

Parser level
VM level
Adding a standard lint lib to Goby
Adding a standard formatter like go fmt
etc.

FYI: Unobtrusive formatter like rufo would be a good example for standard.

@hachi8833 I'll make this a parser error first.

I already make the behavior same as Ruby, this restriction is not necessary now.


Make this an installable app

Some guides...

https://medium.com/clarityai-engineering/how-to-create-and-distribute-a-minimalist-cli-tool-with-python-poetry-click-and-pipx-c0580af4c026
https://cedaei.com/posts/python-poetry-pipx/

Done and documented at https://github.com/jmertic/lfx-landscape-tools?tab=readme-ov-file#local-install


Implement clone-censor-weight methods

[ ] add reference

[ ] See https://github.com/lpetito/SEERMedicareCEAnalysis/blob/master/10_perprotocol.R

[ ] Design document

[ ] Input data format: id, outcome, time, compliant_1, compliant_2, censored, confounders

[ ] weighting model specification

[ ] compliant_1 ~ factors influencing treatment strategy 1 compliance
[ ] compliant_2 ~ factors influencing treatment strategy 2 compliance
[ ] censored ~ factors influencing other censoring

[ ] Fit outcome model.

[ ] is g-computation needed? Maybe if we want ATT?

@gravesti I have tried to simulate some data to mimic the scenario that patients' data are compatible with multiple dynamic treatment regimes.   For example, the columns compatible, compatible1 below represent whether patients data are consistent with two regimes based on two time-varying covariates X1 (binary), X2(continuous),

Intiate treatment at the first visit with X2 >0
Intiate treatment at the first visit with X2 >0 or X1=1

However, we need to calculate weights for the observed treatments up to the last visit that the regime is  adhered. This is not the same as we do in the package because we only calculate for the always treated vs always controlled regimes.  So we will need to alter the weight calculation when applying clone-censor-weight because of the difference in how data are coded for treatments and a particular regime. I will work out an example using some generic coding in R.

@lisu-stats I guess from this data set up, we would just need to stack the data, once with compatible and then with compatible1, and modify the IDs for the 2nd copy. Then I think it could work directly in our existing functions.
Maybe we would need to change the IDs back for the sandwich estimator, so the clones have the same ID?

@gravesti In this simulation setting, the true weights should be the IPTW weights. Simply fitting a IPCW model to compatible and compatible1 may have the risk of model misspecification. Note that in these simulated data, there was more variation in the treatment process.  See the comment from Gaber et al's review paper

I will discuss this issue with Shaun.

@gravesti Shaun and I agreed that we probably want to implement IPTW and IPCW for the clone-censor-weight approach.
IPCW is straightforward： as you mentioned, we just calculate the weights separately based on created censoring indicators compatible and compatible1. Then weights are applied to the cloned data with an MSM. Then we use the fitted MSM to predict survival curves.  You are quite right, clones should have the same IDs as they come from the same patients.
For IPTW, we need to use the original treatment data before cloning and artificial censoring to estimate the treatment probability. For each uncensored observation in cloned data,  we use these treatment models to  estimate the probability of being uncensored up to visit t according to the observed treatment sequence up to t.
Because of the inference problems for weights estimated by data-adaptive methods as mentioned above, let's focus on parametric models for weight estimation.  Adapting undersmoothed HAL to longitudinal settings will be a big step and we will see if there is new work on this coming out.

@lisu-stats Thanks for the explanation. I think I will need to talk through the IPTW next week.
I have also see this pre-print manuscript https://arxiv.org/pdf/2404.15073 where they suggest to limit the patients who are included in the IPCW calculation to avoid an "impossible intervention". I'd be pleased to hear what you think about this.

@gravesti I agree it is tricky when the treatment timing is incorporated in a regimen. For such regimens, I feel like alternative approach such as longitudinal modified treatment policy might be better https://muse.jhu.edu/article/883479


App crashes the message recipients browsers.

On the decision of eventually avoiding the bloating of a project by using socket.io I came across your YouTube channel. Surprisingly if you send some 20 messages in one room on the first browser the second browser with a different user in the same room crashes  and only receives max up to twelve messages (tested with FF, Chrome, Chromium, Edge).
https://github.com/deniercounter/Realtime-Chat-Application/tree/18-08-2021/show-browser-crashing
I only changed client/containers/Messages.tsx -> handleSendMessage() in order to test it faster.
function handleSendMessage() {
    const date = new Date();
    numberOfSentMessages.current++;
    newMessageRef.current.value = `${
      numberOfSentMessages.current
    }. Message from ${username} @ ${date.getHours()}:${date.getMinutes()}:${date.getSeconds()}:${date.getMilliseconds()}`;
    const message = newMessageRef.current.value;

    if (!String(message).trim()) {
      return;
    }

    socket.emit(EVENTS.CLIENT.SEND_ROOM_MESSAGE, { roomId, message, username });

    setMessages([
      ...messages,
      {
        username: "You",
        message,
        time: `${date.getHours()}:${date.getMinutes()}`,
      },
    ]);

    newMessageRef.current.value = `Here is ${username} (This msg will be replaced onClick SEND Button...)`;
  }

Thank you for picking this up! The issue was that setting the messages needed to be in a useEffect with a dependency on socket. I've pushed my changes and supplied a patch here: https://github.com/TomDoesTech/Realtime-Chat-Application/blob/main/setMessages.patch


Automate color swatches (they are currently broken)

Make the swatches of color automatic like /generator.html

This will need some RGB magic to decide whether to have light or dark backgrounds.


Unreleased Resource: Streams

https://github.com/Meituan-Dianping/octo-rpc/blob/f451295b8c8017f7fbcd9e5093b45790f16eb803/dorado/dorado-common/src/main/java/com/meituan/dorado/common/util/VersionUtil.java#L57
The program can potentially fail to release a system resource.

+1


api-docs: Fix line break in API keys section.

See https://zulipchat.com/api/#api_keys. The two images with "Your bots" are not laid out the same way.

Automated message from Dropbox CLA bot
@rwbarton, it looks like you've already signed the Dropbox CLA. Thanks!


Cache workspace BLOBs in TF Controller in case the source gets deleted before Terraform CR

User Story
As a Terraform Controller user,
I'd like to have the workspace blobs cached in the TF Controller,
so that the deletion of Source won't cause issues in processing Terraform CRs.
Acceptance Criteria

[ ] The source blobs are cached in the TF Controller before processing the Terraform CRs.
[ ] Even when the source is deleted before the Terraform CR, the processing won't fail due to the cached blobs.
[ ] Adequate tests are added to ensure the caching mechanism works properly, and there is no regression in other functionalities.
[ ] We’ve created related user documentation.

Are we aware of users/customers currently having issues because we don't have this enhancement in place?

It's the problem we categorized as the single resource deletion problem reported by #454 and #666

Terraform BLOB caching design doc:
https://github.com/weaveworks/tf-controller/discussions/911

Sorry, I transferred a question over from notes that I made before reading those issues. 🤦 Thanks for the prompt response!


[Test-operator] Expose extraRPMs parameter

This commit exposes the extraRPMs parameter that was introduced by this PR [1]. The parameter is exposed via
cifmw_test_operator_tempest_extra_rpms.
[1] https://github.com/openstack-k8s-operators/test-operator/pull/102
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

recheck

Testing here -> https://github.com/openstack-k8s-operators/test-operator/pull/106

recheck

/approve


need spacing between mode and hamburger icon #457

Fixed spacing between mode and hamburger icon and make searchbar responsive as well

Hello @arghadipmanna101 please check this pr for issue #457


what is the function of scheduler package?

Hello:
I found the schedular usage in Matcher.java. However, it seems that it is related to something about Cocurrent. What is the meaning of it in this "for block".
for (final MatcherCandidate predecessor : predecessors.two()) {
            scheduler.spawn(new Task() {
                @Override
               //something to run.
                }
            });
        }

If I don't use the schedular,what will  happen？Does it make any different?
Looking forward to your reply.
Thanks a lot.

The scheduler package is for parallelization of route computations. Since we usually have some number, say n, of matching candidates for each position measurement, we must calculate approximagely n^2 routes. The route computation is a single-source-multiple-target step such that we still have n such computations which we can parallelize here. Note, we have here a simple work-stealing adaptation implemented, which is the scheduler package, because thread pools of the JRE are AFAIK not designed for stream workloads, i.e., there is NO guarantee on the order of processing like a FIFO order such that there is no guarantee that one job finishes if you consistently add more jobs in a stream processing fashion.


Update star_classes.cwt

stnh fix

Yeah but really?

Absolutely, yes.

Ok more to the point - why would one do that?

Well, STNH does it. Why else? Because you might want to place a planet or an entity defined as planet as the center of a system.
Anyhow, this question is merely theoretical - its possible to do in code, hence the tool should support it.


Update Powell Teams Connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello,
This validation is in error due to a change in the type of return value, which will lead to a breaking change for our customers.
However, we are aware of this change which is necessary and our customers are and will be informed of this critical breaking change in order to be able to modify their flows.
Currently, the type of this return value does not work, both functionally and technically, and this change therefore had to be made in order to correct these points and thus allow our customers to have a usable and functional connector.
Is it possible to override this validation so that the connector is updated?
Best regards,
Baptiste Beaupuy-Mouret

@Picos thank you for reaching out. It is very good that you are aware of this change now since we still in GitHub step. You can make this change here. If you make an update later during the certification process, it will reset the process.

Dear partner,
We apologize for the delay you might be experiencing while we are working on a high volume of connector requests. Rest assured that we are doing everything we can to address this volume. We are taking measures like improving our processes and hiring additional team members to guarantee resolving your connector requests in a timely manner.
Please let us know if you have any questions in the meantime.

Hi @PowellSoftware, I hope you are doing well. I am following up with you to see how thing are going with updating your connector.
Please let me know if you have any questions.
Thank you very much

Hi @PowellSoftware, I am following up to check if you need any help with updating your connector files.
Please let me know if you have any questions.
Thank you very much.

@PowellSoftware I'm just checking in to see how things are going with updating your connector artifacts as per the given feedback. Please feel free to reach out with any questions you may have, Thanks.

Hi @PowellSoftware I hope you are doing well. I am following up with you to see how things are going with updating your artifacts.
Please let us know if you have any questions.
We look forward to getting your connector certified.
Thank you very much.

Hello @PowellSoftware,
This is to follow up on the status of your connector. I would like to offer help to you if you are having any issues with your connector.
Please do not hesitate to reach out if you have any questions as we are always happy to help.
Thank you very much for working with us.

Hello @PowellSoftware,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Hello Partner,
I hope you are doing well.
I am following up in my messages above to see if you need any help with updating your connector artifacts.
Please do not hesitate to reach out to me if you have any questions as we are always here to help. 😊
I look forward to hearing from you.
Thank you very much.

@PowellSoftware  We are closing your PR since there is no response from your side. You can reopen the same PR whenever you are ready for certification of your connector, thanks.


Add Mako related files to mako_config/

Sorry missed this earlier, though I think I commented. Can we put this all under build_tools/mako/config?

Sorry I missed the comment...


Rotate SSH key for Matt Bostock

Due to CVE-0216-0778:
http://undeadly.org/cgi?action=article&sid=20160114142733

Rebased.


PEP8 compliant code.

Hi folks, this makes the code PEP8 compliant.
I am working on full blown documentation.

I cannot seem to get pycovjson to build correctly on travis, any ideas?

Yes, I do have a suggestion. I would just run it against Python 3.5. Never mind the rest. I would start there then we can work through improving the .travis.yml further.
Thanks

The build is failing due to #13


error: cannot unmarshal array into Go struct field RequestData.images of type types.ImageInfos

The latest version gives this error
2023-08-16T11:52:54.784Z        INFO    verifier/client.go:139  failed to decode {"images":["XXXXXXX.dkr.ecr.us-west-2.amazonaws.com/pause@sha256:33f19d2d8ba5fc17ac1099a840b0feac5f40bc6ac02d99891dbd13b0e204af4e"]}
: json: cannot unmarshal array into Go struct field RequestData.images of type types.ImageInfos
It used to work fine  earlier.  Also can we have a stable version release tags so we can pin to a specific version than latest?

@ajpaws - please check the sample policy in the latest version. The expected inputs have changed:
https://github.com/nirmata/kyverno-notation-aws/blob/main/configs/samples/kyverno-policy.yaml#L32C21-L32C27

@ajpaws - can you please verify the latest works for you?

@JimBugwadia thanks for the quick response. It works now.  Please note I created the workshop on the signer and using main branch https://catalog.workshops.aws/eks-security-immersionday/en-US/12-image-security/image-signing-with-aws-signer/3-signature-verification/2-verify-signature-with-kyverno-in-k8s. Please create a release / tag so we can pin to avoid any breaking in the workshop module

@ajpaws We have a v1 beta1 tag available right now and we are working towards a v1 release which will be released soon. We will be releasing a v1 release candidate in a couple of days. It would be great if you test that out and add it to the workshop.

@ajpaws - thanks for sharing the workshop; this looks awesome!

Closing as this issue was resolved.


Refactor positionmanager event implementation

Description
The package has an embedded version of the event logic that needs to be refactored to reference #263 . Also dependent on #345 being completed.
Specifics

[ ] deprecate all embedded pubsub resources
[ ] port over to Knative implementation #311
[ ] adjust/increase event trigger cadence
[ ] add "read" logic from metamodel API
[ ] include portfolio package logic
[ ] potentially read stored predictions from data layer
[ ] generate weights for ticker subset
[ ] update trades logic

[ ] conditionally reduce/liquidate positions
[ ] update trade package as needed

[ ] manually test container with local builds and runs

we can probably get rid of the explicit dependency on metamodel, in the event system we should not worry about coupling


Is there any way to use this with SWC instead of tsc?

For ref: https://github.com/swc-project/swc-node

I don't think this question makes sense? The type checking is done by tsc.


Update artist-lookup-component.yaml

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Don't think this is meant for here?


BUG: Logout probelem

Is there an existing issue raised for this?

[X] I have searched the existing issues

What happened?
problem
if we click on the logout button our session expired then a continuously a redirection happens or flickering happen.
I want to work on this bug. Could you assign me this issue?
there is image attached because screenshot is mandatory
Add ScreenShots

What browser are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

go for it @niteshtiwari52

I am so sorry sir. The reason is that for no responding, I working as an intern in another organization. I am facing some difficulty to manage college, internship and open project. I joined internship at 18 Aug. The GSSOC program has finished on 15 Aug so i thought that i can contribute upto 15 Aug or before that.

No worries you can pick this up whenever you want

Sure sir. I will do. But it will count still in GSSOC?

No it has concluded.....

Okay sir. Right now i am working on multiple from the internship and college. It gets little bit  tough to me. My internship will ends on 21 OCT  I will try to complete this after that. I am really very sorry  this small issue taking very long time  from my end.

not a big deal.......


License

Update the license

@mondus  Which licence are we intending to switch to?
I would suggest a permissive licence such as:

MIT

A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.

BSD 2-Clause

A permissive license that comes in two variants, the BSD 2-Clause and BSD 3-Clause. Both have very minute differences to the MIT license.

BSD 3-Clause

A permissive license similar to the BSD 2-Clause License, but with a 3rd clause that prohibits others from using the name of the project or its contributors to promote derived products without written consent.

Or alternatively a slightly less permissive licence (if the above are to permissive) which provides trademark / patent related things

Apache License 2.0

A permissive license whose main conditions require preservation of copyright and license notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without source code.

We will make this decision just prior to the 1.5 release.

MIT licence added and readme updated.


Fix ArcGISTiledElevationTerrainProvider TypeScript definition

https://github.com/CesiumGS/cesium/issues/9465#issuecomment-830465969
There was no new line after the WebGLConstants enum definition in the TypeScript definition file:
...
    MAX_TEXTURE_MAX_ANISOTROPY_EXT = 34047
}/**
 * A {@link TerrainProvider} that produces terrain geometry by tessellating height maps
...

This caused ArcGISTiledElevationTerrainProvider to not be completely picked up by the TypeScript compiler. There's special handling from WebGLConstants to hoist it to the top of the file, so we just needed to insert two new lines in the special handling code to fix the problem:
...
    MAX_TEXTURE_MAX_ANISOTROPY_EXT = 34047
}

/**
 * A {@link TerrainProvider} that produces terrain geometry by tessellating height maps
...

Thanks for the pull request @mramato!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

To test this, just run build-ts and compare it to master and you'll see that the new line is inserted as described above.

Self merging this so that I can start the release.


Accomodate VSCode users with the rust-analyzer extension

Add support for VSCode developers with this extension:

https://rust-analyzer.github.io/

It's the primary LSP implementation for Rust (so far as I can tell). It gives me hover hits, etc. This PR makes it work without having to change directories:

Do we need to do anything else for releases?

What if we use the cargo workspace function instead of a symlink? There is a discussion here: https://github.com/rust-lang/rust-analyzer/issues/6007#issuecomment-1295801479

Do we need to do anything else for releases?

I think that with the workspace that José suggested, we would need to create a symlink for the target dir of the root of the project. This is because cargo is going to save the files in the root directory, and we are looking to the native/explorer/target directory for the shared lib.
I'm going to check if there is another way to locate the file automatically.
BTW, I tested the workspace config with the following:
[workspace]
resolver = "2"

members = [
  "native/*"
]

[patch.crates-io]
jsonpath_lib = { version = "0.3", git = "https://github.com/ritchie46/jsonpath", branch = "improve_compiled" }

@josevalim @philss I tried the EDIT at the top of the Jose's comment and it just worked lol. (I swear I looked for such a setting but couldn't find one 😅)
The workspace thing may not be necessary if the settings.json approach works. But IDK enough about Rust to say for sure.

@billylanchantin nice! I prefer this way! :D
PS: maybe you need to change your editor config to add newlines at the end of the JSON files. Our .editorconfig file is configured to add new lines. Not sure why your VS Code is not reading that (maybe it needs an extension?).

Our .editorconfig file is configured to add new lines. Not sure why your VS Code is not reading that (maybe it needs an extension?).

@philss Yep, that was it! I added an extension and VSCode started adding newlines correctly.
To cement that, I've added an extensions.json that records which extensions we recommend, including the editconfig extension. We can add more of course, but this is probably fine for now.

I am not the biggest fan of adding editor specific configuration files. Isn't there a general configuration we could use that would work for many editors, such further modifications to editor config?

I am not the biggest fan of adding editor specific configuration files.

@josevalim yeah I feel ya. If you have N editors on your team, suddenly you've got N config files floating around.
I see two things we can do:

Add .vscode/ to my .git/info/exclude (aka "private" .gitignore) then remove it from the project.
Take another pass at the workspace thing.

I can do the .git/info/exclude thing either way. That way at least I'm unblocked personally.
Then I/we can take another stab at the workspace approach. That would possibly obviate the need for .vscode/settings.json, meaning future VSCode contributors would be unblocked too.

This works for me:

Remove .vscode/
Add @philss's Cargo.toml
Symlink in root:

native/explorer/Cargo.lock
native/explorer/target

Do we want that instead?

We may be able to configure the build directory and skip the symlinks:
https://stackoverflow.com/questions/50364390/how-can-i-specify-a-custom-cargo-output-directory
But perhaps we could move both Cargo.toml and Cargo.lock to the root directory and just keep the source directly inside "native" or inside "src".


feat: ledger did file was move in ic repo

Motivation
It seems that the NNS ledger.did file has been moved in the IC repo (in this PR).

Yep no changes in the ledger.did.


feat(#38): migrate to aspera browser naming instead of desktop

BREAKING CHANGE: old desktop-sdk-js is no longer used. Move to @ibm-aspera/browser-sdk-js

In general, make sure to change "Aspera for Browser SDK" to something like "Aspera Browser SDK"


Run OpenEBS in GCP

Use this issue to document the steps used to learn to get this working..
Created an container cluster with 3 nodes. The command listed here are run from the gcloud shell.
(a) Setup credentials to access the cluster
gcloud container clusters list
gcloud container clusters get-credentials openebs03 --zone asia-east1-a

(b) kubectl commands to get the current nodes and context.
kubectl get nodes
kubectl config current-context
kubectl config get-contexts

(c) Get the cluster credentials from the project / cluster settings page (username, password and certificate)
Store the key in ~/.kube/admin.key
kubectl config set-credentials cluster-admin --client-key=~/.kube/admin.key
kubectl config set-context openebs03_admin --cluster=gke_strong-eon-153112_asia-east1-a_openebs03 --user=cluster-admin
kubectl config use-context openebs03_admin

Run the openebs-operator.yaml
kubectl apply -f openebs-operator.yaml

Working steps look like:
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl config get-contexts
CURRENT   NAME                                           CLUSTER                                        AUTHINFO                                       NAMESPACE
*         gke_strong-eon-153112_asia-east1-a_openebs03   gke_strong-eon-153112_asia-east1-a_openebs03   gke_strong-eon-153112_asia-east1-a_openebs03
          openebs03_admin                                gke_strong-eon-153112_asia-east1-a_openebs03   cluster-admin
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl config use-context openebs03_admin
Switched to context "openebs03_admin".
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl apply -f openebs-operator.yaml
Please enter Username: admin
Please enter Password: ****************
                                       serviceaccount "openebs-maya-operator" configured
clusterrole "openebs-maya-operator" configured
clusterrolebinding "openebs-maya-operator" configured
deployment "maya-apiserver" created
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl config use-context gke_strong-eon-153112_asia-east1-a_openebs03
Switched to context "gke_strong-eon-153112_asia-east1-a_openebs03".
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl get pods
NAME                             READY     STATUS    RESTARTS   AGE
maya-apiserver-188163937-wz48m   1/1       Running   0          51s
kiran_mova@strong-eon-153112:~/openebs/k8s$ kubectl exec -it maya-apiserver-188163937-wz48m /bin/bash
root@maya-apiserver-188163937-wz48m:/# maya
usage: maya [--version] [--help] <command> [<args>]
Available commands are:
    network-install    Configure flannel network on maya-host machine (Alpha).
    omm-status         Display a list of known servers and their status
    osh-status         Display status information about nodes
    setup-omm          Configure OpenEBS Maya Master on this machine.
    setup-osh          Configure this machine as OpenEBS Host.
    version            Prints the Maya version
    vsm-create         Creates a new VSM
    vsm-list           Display status information about Vsm(s)
    vsm-stats          Display VSM Stats
    vsm-stop           Stop a running vsm
    vsm-update         Updates the vsm with the provided specs
root@maya-apiserver-188163937-wz48m:/#

Step 1: Create a Container cluster

Use Container Engine to create a container cluster. Select - "container-vm" as the node image, since OpenEBS requires iSCSI support. Select atleast 3 nodes, with 2 vCPU/7.5GB RAM. Wait for the cluster to get created.
Login/SSH into the VMs associated with the cluster (Compute Engine) and install open-iscsi

apt-get update
apt-get install open-iscsi

Setup access via the cloud shell (setting up CA certificate  in cat ~/.kube/admin.key ). Make a note of admin password.

gcloud container clusters get-credentials demo-openebs03 --zone us-central1-a
kubectl config get-contexts
kubectl config set-context demo-openebs03 --cluster=gke_strong-eon-153112_us-central1-a_demo-openebs03 --user=cluster-admin

Step 2: As a storage operator, enable OpenEBS - operator.
kubectl config use-context demo-openebs03
git clone https://github.com/openebs/openebs.git
#Note down the admin password - Container Cluster -> Show Credentials
kubectl apply -f openebs-operator.yaml
kubectl config use-context gke_strong-eon-153112_us-central1-a_demo-openebs03

Step 3: Running Jupyter with OpenEBS storage
kubectl apply -f demo-jupyter-openebs.yaml

(sample file located at github.com/openebs/openebs/k8s/demo/jupyter)
(This file uses "NodePort" for external access. So have the Firewall to enable ingress traffic for the port used by the jupyter service)

Step 4 : (Will be automated using the openebs provisioner) - Create the volume and PV expected by the PVC. The pod will remain in the pending state till the PV is created.
Step 4a : Create Volume
kubectl get pods
kubectl exec -it maya-apiserver-188163937-xzd76 /bin/bash
maya vsm-create -name=demo-vol1 -size=5G
exit

Step 4b : Create PV
kubectl get services
cat demo-vsm.pv.yaml #Modify the portal IP, with the one listed in the services command.
kubectl apply -f demo-vsm-pv.yaml

The jupyter-notebook should not start on the OpenEBS volume.
Access the UI by going to the URL
http://<node ip>:exposedport//

Node IP is any of the Container Hosts - External IP and exposed port can be obtained using "kubectl get services"


Bug: Global notification email in Admin are not recognized as toEmail in aws(ses), but as fromEmail.

Environment
Host

item
version

GROWI
4.2.13-RC

How to reproduce? (再現手順)

Create identiy of ses

Create an IAM with ses privileges.

Go to App Settings in admin.
Input Mail Setting in Admin, and select ses.
Enter the from address as verified by ses.
Enter the Access Key ID and Secret access key as obtained by  created IAM.

Press the Update button

Go to Notification Settings.
Click Global notification.
Click add new
Enter the required information

Enter the required information
What happens? (症状)

The following error occurs on the server side.

POST /_api/pages.update 200 78.062 ms - 1512
08:03:05.972Z  INFO growi:service:search-delegator:elasticsearch: Adding pages progressing: (count=1, errors=false, took=504ms)
08:03:05.972Z  INFO growi:service:search-delegator:elasticsearch: Adding pages has completed: (totalCount=1, skipped=0)
08:03:06.244Z ERROR growi:routes:page:
  Edit notification failed MessageRejected: Email address is not verified. The following identities failed the check in region US-EAST-1<EMAIL_ADDRESS>      at Request.extractError (/workspace/growi/node_modules/aws-sdk/lib/protocol/query.js:47:29)
      at Request.callListeners (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
      at Request.emit (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
      at Request.emit (/workspace/growi/node_modules/aws-sdk/lib/request.js:683:14)
      at Request.transition (/workspace/growi/node_modules/aws-sdk/lib/request.js:22:10)
      at AcceptorStateMachine.runTo (/workspace/growi/node_modules/aws-sdk/lib/state_machine.js:14:12)
      at /workspace/growi/node_modules/aws-sdk/lib/state_machine.js:26:10
      at Request.<anonymous> (/workspace/growi/node_modules/aws-sdk/lib/request.js:38:9)
      at Request.<anonymous> (/workspace/growi/node_modules/aws-sdk/lib/request.js:685:12)
      at Request.callListeners (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
      at Request.emit (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
      at Request.emit (/workspace/growi/node_modules/aws-sdk/lib/request.js:683:14)
      at Request.transition (/workspace/growi/node_modules/aws-sdk/lib/request.js:22:10)
      at AcceptorStateMachine.runTo (/workspace/growi/node_modules/aws-sdk/lib/state_machine.js:14:12)
      at /workspace/growi/node_modules/aws-sdk/lib/state_machine.js:26:10
      at Request.<anonymous> (/workspace/growi/node_modules/aws-sdk/lib/request.js:38:9)
      at Request.<anonymous> (/workspace/growi/node_modules/aws-sdk/lib/request.js:685:12)
      at Request.callListeners (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
      at callNextListener (/workspace/growi/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
      at IncomingMessage.onEnd (/workspace/growi/node_modules/aws-sdk/lib/event_listeners.js:269:13)
      at IncomingMessage.emit (events.js:327:22)
      at IncomingMessage.EventEmitter.emit (domain.js:467:12) {
    code: 'MessageRejected',
    time: 2021-03-12T08:03:06.240Z,
    requestId: '4ce30473-9123-4ea3-908b-7120b26690e9',
    statusCode: 400,
    retryable: false,
    retryDelay: 87.61044496853141
  }

What is the expected result? (期待される動作)
-　An email will be sent when the trigger is activated.
Note

This error does not happen using smtp server.
No problem if you use aws(ses) to send user invites.

Thanks for reporting the issue.
 Email address is not verified. The following identities failed the check in region US-EAST-1<EMAIL_ADDRESS>
The error you mentioned will be occured in case that SES settings is Sandbox mode.
Please check the following link to solve the error.
https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
For the above reason, this is not a bug of GROWI, I'll close this issue.
Thank you.


commands: use unconfirmed coins from self for coin selection

This is to resolve #1484.
We previously used unconfirmed change for coin selection as a best-guess way of identifying those unconfirmed coins from self, but now we have the is_from_self field we can use it directly and be sure we only select coins that are fully under our control.

Can you change value here:
https://github.com/wizardsardine/liana/blob/master/liana-gui/src/lianalite/client/backend/mod.rs#L652

Ah, that's been changed as part of #1498. But I don't think that change is required in this PR as the logic for specifying candidates for selection is in the remote backend API handler so will need to be changed there separately.

Ah right thanks, I merged it, can you rebase ?

Rebased on master.


Make Dask progress bars optional

Resolves #95
References:

Dask Diagnostics (local)
outdated SO answer about removing
PR describing new config methods

@rschwant I put this in analysis.read_control() method. Does that seem like a good place? Also are you ok with defaulting to false? Or do you want default true?

Don't understand the docs build failure. Same Sphinx version as when it was passing recently (4.5.0).

@zmoon Adding this to the analysis section seems like a good place to me. I also agree let's default to false and if people need to output these diagnostics they can set the value to true. I tested the commands in another jupyter notebook and they worked for me, so I can review this if needed too. Not sure either why the docs are failing now?

@rschwant thanks for testing the commands!

Thanks @rschwant


Update login screen image

Description
Forgot to update one of the assets from. In particular, forgot to update the reference to the login screen image.
https://github.com/edx/edx-app-ios/pull/811
How to test this PR
Reviewers
If you've been tagged for review, please "Start a review" with the Github GUI.

FYI @saeedbashir @danialzahid94

👍


Update storage tests

Add decorator to run the tests in live only.
Move create temp file/directory to base.
Update storage tests add a few variations.
Add test assertions of inspect recordings.

Codecov Report

Merging #2637 into master will increase coverage by 0.02%.
The diff coverage is 95.23%.

@@            Coverage Diff             @@
##           master    #2637      +/-   ##
==========================================
+ Coverage   71.87%   71.89%   +0.02%
==========================================
  Files         377      378       +1
  Lines       20725    20745      +20
  Branches     3048     3051       +3
==========================================
+ Hits        14896    14915      +19
- Misses       4894     4895       +1
  Partials      935      935

Impacted Files
Coverage Δ

src/azure-cli-testsdk/azure/cli/testsdk/base.py
62.57% <100%> (+3.51%)
:arrow_up:

...rc/azure-cli-testsdk/azure/cli/testsdk/__init__.py
100% <100%> (ø)
:arrow_up:

.../azure-cli-testsdk/azure/cli/testsdk/decorators.py
80% <80%> (ø)

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 767772d...23e4c30. Read the comment docs.

Ping @tjprescott @yugangw-msft @derekbekoe


form_builder_phone_field dependency issue

when trying to upgrade to flutter_form_builder6.0.0 i get the below error:
Because form_builder_phone_field 0.2.0 depends on flutter_form_builder ^5.0.0-alpha.1 and no versions of form_builder_phone_field match >0.2.0 <0.3.0, form_builder_phone_field ^0.2.0 requires flutter_form_builder ^5.0.0-alpha.1.
So, because money_pos depends on both flutter_form_builder ^6.0.0 and form_builder_phone_field ^0.2.0, version solving failed.
pub get failed (1; So, because money_pos depends on both flutter_form_builder ^6.0.0 and form_builder_phone_field ^0.2.0, version solving failed.)
exit code 1

same issue here

I created a pull request forform_builder put the maintainer isn't replying to anything right now I don't know why.
So I used my pull request until the maintainer merges it.
Done it as follows:
form_builder_phone_field:
    git:
      url: https://github.com/Faaatman/form_builder_phone_field.git
      ref: 4f1a827

I created a pull request for form_builder_phone_field but the maintainer isn't replying to anything right now I don't know why.
So I used my pull request until the maintainer merges it.
Done it as follows:
form_builder_phone_field:
    git:
      url: https://github.com/Faaatman/form_builder_phone_field.git
      ref: 4f1a827

edit: typo

I get this error here:
C:/_Dev/Flutter/.pub-cache/git/form_builder_phone_field-4f1a827daed80efd8ff762e436459e3c27c874e5/lib/src/form_builder_phone_field.dart:117:22: Error: The argument type 'void Function(String)?' can't be assigned to the parameter type 'void Function(String?)?' because 'String?' is nullable and 'String' isn't.
          onChanged: onChanged,
                     ^

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.0.6, on Microsoft Windows [Version 10.0.19042.985], locale de-DE)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] Connected device (3 available)
• No issues found!

@rainerlonau  Oh yeah, that problem happened when he upgraded flutter_form_builder to 6.0.1. I used flutter_form_builder 6.0.0 for this to work.
Use the following in your pubspec for the phone field to work.
flutter_form_builder: 6.0.0

@Faaatman wow, thanks for this fast reply! It works with your pubspec entry.

can you guy run your project ios emulator when use this package ? i got an error on xcode like this , any one got this problem too ?
Could not find module 'PhoneNumberKit' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator

i solved it by using Rosetta , lol
and in pubspec
 flutter_form_builder: 6.0.0
 form_builder_phone_field:
    git:
      url: https://github.com/Faaatman/form_builder_phone_field.git
      ref: 4f1a827

This still an issue?

Due to lack, I will close this issue.
If the bug still exists, feel free to open a new issue


Executable named spec not found on path

$ stack setup
stack will use a locally installed GHCJS
For more information on paths, see 'stack path' and 'stack exec env'
To use this GHCJS and packages outside of a project, consider using:
stack ghc, stack ghci, stack runghc, or stack exec

$ stack build
Ignoring that the GHCJS boot package "scientific" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "case-insensitive" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "hashable" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "async" has a different version, <IP_ADDRESS>, than the resolver's wanted version, 2.1.0
Ignoring that the GHCJS boot package "text" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "syb" has a different version, 0.5.1, than the resolver's wanted version, 0.6
Ignoring that the GHCJS boot package "stm" has a different version, 2.4.4, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "parallel" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "dlist" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "pretty" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "containers" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>
Ignoring that the GHCJS boot package "transformers" has a different version, <IP_ADDRESS>, than the resolver's wanted version, <IP_ADDRESS>

$ stack solver
Asking cabal to calculate a build plan, please wait
Running /Users/mchaver/.local/bin/cabal --config-file=/var/folders/_v/b38d3dx54yq7lbrqqtnpzmcc0000gn/T/cabal-solver28760/cabal.config install --enable-tests --enable-benchmarks -v --dry-run --only-dependencies --reorder-goals --max-backjumps=-1 --package-db=clear --package-db=global /Users/mchaver/Documents/work/ghcjs-hspec-json/ --ghcjs exited with ExitFailure 1
/Users/mchaver/.cabal/bin/alex --version
looking for tool c2hs near compiler in
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin
/Users/mchaver/.cabal/bin/cpphs --version
/usr/bin/gcc -dumpversion
/Applications/ghc-7.10.3.app/Contents/bin/ghc --numeric-version
/Applications/ghc-7.10.3.app/Contents/bin/ghc-pkg --version
looking for tool haddock near compiler in
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin
found haddock in
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin/haddock-ghcjs
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin/haddock-ghcjs --version
/Users/mchaver/.cabal/bin/happy --version
/Applications/ghc-7.10.3.app/Contents/bin/hpc version
looking for tool hsc2hs near compiler in
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin
found hsc2hs in
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin/hsc2hs-ghcjs
/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin/hsc2hs-ghcjs --version
/Users/mchaver/.cabal/bin/HsColour -version
/usr/local/bin/pkg-config --version
/usr/bin/tar --help
Reading available packages...
Updating the index cache file...
Choosing modular solver.
Resolving dependencies...

Warning: cannot determine version of /usr/bin/strip :
""
cabal: Could not resolve dependencies:
trying: ghcjs-hspec-json-0.1 (user goal)
next goal: base (dependency of ghcjs-hspec-json-0.1)
rejecting: base-<IP_ADDRESS>/installed-dfc..., <IP_ADDRESS> (global constraint requires
==<IP_ADDRESS>)
rejecting: base-<IP_ADDRESS> (global constraint requires installed instance)
rejecting: base-<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>,
<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>,
<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> (global constraint requires
==<IP_ADDRESS>)
Dependency tree exhaustively searched.

$ stack exec spec
Executable named spec not found on path: ["/Users/mchaver/Documents/work/ghcjs-hspec-json/.stack-work/install/x86_64-osx/lts-5.12/ghcjs-0.2.0_ghc-7.10.3/bin","/Users/mchaver/.stack/snapshots/x86_64-osx/lts-5.12/ghcjs-0.2.0_ghc-7.10.3/bin","/Users/mchaver/.stack/programs/x86_64-osx/ghcjs-<IP_ADDRESS>60414_ghc-7.10.3/bin","/Users/mchaver/.local/bin","/Users/mchaver/.cabal/bin","/Applications/ghc-7.10.3.app/Contents/bin","~/bin/ghc-ios-scripts","/usr/local/git/bin","/usr/local/bin","/usr/bin","/usr/local/sbin","/usr/local/bin","/usr/bin","/bin","/usr/sbin","/sbin","/usr/local/git/bin","/usr/texbin"]

Nevermind, I figured out how to run it stack test


Consider using multi-line form for all compound matcher failure messages

Given this expectation:
      expect(last_cmd_stdout).to include(
        "2 examples, 0 failures",
        "is selected by line", "is selected by tag"
      ).and exclude("not selected")

I'm getting a failure message like so:
       expected "Run options: include {:tag => true, :locations => {\"./tmp/aruba/spec/file_1_spec.rb\" => [2]}}\n\nFile 1\n  is selected by line\n\nFile 2\n  is not selected\n  is selected by tag\n\nFinished in 0.00059 seconds (files took 0.12448 seconds to load)\n3 examples, 0 failures\n" to include "2 examples, 0 failures", "is selected by line", and "is selected by tag" and expected "Run options: include {:tag => true, :locations => {\"./tmp/aruba/spec/file_1_spec.rb\" => [2]}}\n\nFile 1\n  is selected by line\n\nFile 2\n  is not selected\n  is selected by tag\n\nFinished in 0.00059 seconds (files took 0.12448 seconds to load)\n3 examples, 0 failures\n" not to include "not selected"

There's also a diff which helps (although that has problems of its own -- see #746) but the message itself is pretty hard to read.  I think that we should consider making compound (and/or) always use the multi-line form (where they use ...and:  and indentation) because that will be more readable.  Or perhaps we should still use the single-line form if the message is below some length threshold?  For short messages it still reads OK.
Thoughts?

:+1:


feat: introduce a new API for consumer tests

The current API is tightly coupled with mocha (and gts). introduce a
new API that can be used across various different testing frameworks.
We simply use asserts, and users can structure their tests as
appropriate. This also gets rid of tight coupling with gts. Instead
we use typescript compiler directly.
The old API is still available, but if this seems better to folks, I
would like to drop the old one in a subsequent semver major.

@JustinBeckwith added a README. PTAL.

This depends on https://github.com/google/post-install-check/pull/36.


Readme update

Updates the readme to direct people to the website

Questions on more things to be removed:

Old Install instructions
Game controls

Should we mention v2 coming?
Should we add a troubleshooting section pointing at website then discord?


Link against system rapidjson

Is there any easy way to link against the system rapidjson install path inside the build system?
A simple grep of the source code indicates no options like -D*RAPIDJSON* exist — but perhaps this is called differently?
If not, any ideas how this can best be patched? Would it suffice to turn off the downloads in Code/GraphMol/MolInterchange/CMakeLists.txt and point to the system directory — or does this have to be in the build tree?
Attempting to build =rdkit-2020.03.6

The implementation in Open Babel might be a useful reference for a patch:
https://github.com/openbabel/openbabel/blob/master/CMakeLists.txt#L603-L630
and
https://github.com/openbabel/openbabel/blob/master/cmake/modules/FindRapidJSON.cmake


Cannot use partials in layout

Expected behavior and actual behavior
I have a layout file at source/layouts/layout.erb, which includes a partial which is at source/shared/_dropdown.html.erb, and various actual pages that are rendered in the layout: for example source/tutorials/what_is_passenger/index.html.erb.
I do not use the partials_dir config, and never have (I know it's gone now anyway).
I render the partial with <%= render_partial("/shared/dropdown.html").
This worked in v3 and doesn't now in v4.
After poking around in middleman, I found that for some reason the path of the file which is being rendered in the layout (ie a specific page) is being used as the current_path of the layout, which makes it impossible to set a path to the partial. it appends the path I pass to render_partial to the end of the current path (eg tutorials/what_is_passenger/shared/dropdown.html which doesn't exist so I'd have to use ../../ in the path which would only work if every page had the same number of dirs in the path).
Steps to reproduce the problem (from a clean middleman installation)
I don't know.
Additional information

Ruby version: 2.3.7
Middleman version: 4.2.1
OS version: macOS 10.13.6 (17G65)

Nevermind the problem is I can't include extensions in partial paths.


Add RichText support to find.text

Check RichText in find.text if the direct parent element is not a Text widget. This allows users to find the text value of RichText without double-counting the RichText widget created by Text.
Fixes https://github.com/flutter/flutter/issues/21961

This seems like a good change, but it is technically a breaking change because something that findsOneWidget today could now fail. You might want to give a heads up on the relevant mailing lists.


Update producer cache after creating

Fixes issue #43.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #44   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines          24     24
=====================================
  Hits           24     24

Impacted Files
Coverage Δ

...adet/spark/kafka08/writer/KafkaProducerCache.scala
100% <ø> (ø)
:white_check_mark:

...det/spark/kafka010/writer/KafkaProducerCache.scala
100% <ø> (ø)
:white_check_mark:

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 bfaeda1...09d2c9b. Read the comment docs.

Thanks a lot merging (can't believe this passed through)!

 I'm glad I could help a little bit.

@basvandenbrink ahah just saw that it was working before thanks to https://github.com/BenFradet/spark-kafka-writer/blob/master/spark-kafka-0-10-writer/src/main/scala/com/github/benfradet/spark/kafka010/writer/KafkaProducerCache.scala#L42
However I do agree that getOrElseUpdate simplifies things a bit.

Ah, you're right. It wasn't a problem in the first place.


how to select iphone

i bought fingerprint key from bablosoft, but when i using this tags it's error, how to do that ?
const fingerprint = await plugin.fetch(mykey, {
tags: ['iPhone', 'Safari'],
});
Fingerprint error : Fingerprint with tags iPhone,Safari not found 0.

I can't reproduce the issue, do you have more filters?

there is no filter,
when i used : tags: ['Mobile', 'Chrome'] it's running well,
but when i'm using another tags like ['iPhone', 'Safari'] it's show the error.
i also try tags: ['Mobile, iPhone', 'Safari']  or ['iPhone', 'Chrome']  it's also error.
do you any suggest to use tags for iphone ?

I can't reproduce the issue, do you have more filters?

how to solve this problem, sir ?


Doesn't work

Followed the instructions on the website, installed Glide and then ran and got this
Js-iMac:alloy jmhowitt$ go install
main.go:6:2: cannot find package "github.com/olliecoleman/alloy/app/services" in any of:
/Users/jmhowitt/go/src/alloy/vendor/github.com/olliecoleman/alloy/app/services (vendor tree)
/usr/local/go/src/github.com/olliecoleman/alloy/app/services (from $GOROOT)
/Users/jmhowitt/go/src/github.com/olliecoleman/alloy/app/services (from $GOPATH)
main.go:7:2: cannot find package "github.com/olliecoleman/alloy/app/views" in any of:
/Users/jmhowitt/go/src/alloy/vendor/github.com/olliecoleman/alloy/app/views (vendor tree)
/usr/local/go/src/github.com/olliecoleman/alloy/app/views (from $GOROOT)
/Users/jmhowitt/go/src/github.com/olliecoleman/alloy/app/views (from $GOPATH)
main.go:8:2: cannot find package "github.com/olliecoleman/alloy/cmd" in any of:
/Users/jmhowitt/go/src/alloy/vendor/github.com/olliecoleman/alloy/cmd (vendor tree)
/usr/local/go/src/github.com/olliecoleman/alloy/cmd (from $GOROOT)
/Users/jmhowitt/go/src/github.com/olliecoleman/alloy/cmd (from $GOPATH)
Js-iMac:alloy jmhowitt$ alloy dev

You should use glide install to install the dependencies first.

This is what i did
n.b. i had to install glide seperately which is not in the HowTo
$ cd /Users/jmhowitt/go/src -- into my go src directory
$ git clone https://github.com/olliecoleman/alloy -- get the repo
$ cd alloy -- got into the directory
$ glide install -- run glide but it is not there
$ curl https://glide.sh/get | sh -- get glide
$ glide install -- install glide
$ npm install -- install npm
$ go install -- try to create the project and get all the errors
$ alloy dev -- falls over of course

Same go install issue for me as well. Using MacOS Sierra 10.12.6.

@sahajRe I use MacOS Sierra 10.12.6 too but not encounter this error, I think it have no relation with your OS.
Did you clone this project to $GOPATH/src/github.com/olliecoleman/alloy directory?

OK installed in "$GOPATH/src/github.com/olliecoleman/alloy" so i must have missed that instruction in the documentation.
so now it works up to "alloy dev" where it tells me there is no such command.

Have in run go install and put the binary file $GOPATH/bin/alloy to you $PATH such as /usr/local/bin?

Hmm getting complicated and all of this missing in the installation instructions, i think i will just delete it and get on with something else.

Thanks @rootsongjc. Cloning alloy in $GOPATH/src/github.com/olliecoleman/ worked.


stateful_session: encode expiry time and reject expired cookies

Commit Message:
encode expiry time and reject expired cookies
Additional Description:
Changed internal format of cookies to protobuf. Added expires field. When processing received cookie, expires timestamp is compared to the current time. Expired cookies are ignored and new upstream host is selected. Backwards compatibility is preserved, so cookies in "old" non-proto format are accepted, but support for them will be removed in the future.
Risk Level: Low
Testing: Expanded unit and integration tests.
Docs Changes: No.
Release Notes: Yes.
Platform Specific Features:
Runtime guard: envoy.reloadable_features.stateful_session_encode_ttl_in_cookie
Fixes #26347

/assign

Json is great. But would it be better to use some simple way to extended this cookie value? For example, a simple space could be used to seperate different fields in the value.
All <IP_ADDRESS>, <IP_ADDRESS> -, <IP_ADDRESS> <timestamp> could be valid values.
Although we may have more fields in the cookie value, the Json still too heavy for this simple requirement.

/wait-any

Json is great. But would it be better to use some simple way to extended this cookie value? For example, a simple space could be used to seperate different fields in the value.
All <IP_ADDRESS>, <IP_ADDRESS> -, <IP_ADDRESS>  could be valid values.
Although we may have more fields in the cookie value in the future, the Json still too heavy for this simple requirement.

That was my first approach - to separate by say ";". But then I started to think how to protect against crashing when the payload is not correct. Currently, the cookie is expected to beip:port. The stateful_session filter does not do any syntax validation, because it offloads the checks to the cluster. For example, instead of valid IP address you can send "blahlahbalah" in the cookie and stateful_session filter will ask the cluster to use "blahlahbalah" as upstream address. The cluster does syntax validation and rejects it as address. With a new timestamp field, I have to ask solid parsing, dealing with missing fields, validating that the field is indeed an integer, etc. Most of those problem are already solved by json parser.
Let me write microbenchmark to see how json compares to tokenizing a string with fields separated by ";".

For encoding the data I would strongly recommend something like a base64 encoded protobuf. This will be much easier to deal with if we add more fields in the future.

@mattklein123 Thanks for your suggestion. Let me refactor the code to use protobuf.

For encoding the data I would strongly recommend something like a base64 encoded protobuf. This will be much easier to deal with if we add more fields in the future.

SGTM.

@wbpcode Thanks for reviewing. I tried to address all your comments.

/retest

/retest

/wait

/retest

Thanks for all comments. There is still one outstanding issue of encoding:

I still think we can add a simple flag to distinguish the new proto format cookie. base64(PB ) or PB-base64() or some others way could be selected.
By this way, we can distinguish new format cookie value with once prefix comparation quickly and needn't always try to do a proto parsing. esp, considering that users with old format cookie will always use old format in a long time (because of the use_old_style_encoding_). This unnecessary parsing should be avoided.

Cookie is considered short-lived. I agree that during an upgrade, clients may keep sending cookies with old, non-proto format, but this should last only until TTL value given to a client expires. After that, a client should send a request without cookie and will be given a  cookie in a new format.
I also agree that adding "PB " prefix reduces processing for "old" cookies but also adds one operation for "new" cookies.
Currently the logic is like this:
base64decode -> decode_from_proto -> treat as PB on success, treat as "old" string on failure
If we add "PB " prefix, the logic is
                         |--> found. base64decode->decode_from_proto->treat as PB on success, reject on failure
check for "PB " prefix - |
                         |--> not found. base64decode->treat as "old" string.

Prefix will also complicate deprecating "old" cookie format. Few months from now, "old" cookie format should be deprecated, and keeping that prefix will not make sense. But code to support "transition" will have to be added, because cookies encoded as proto may arrive with "PB " prefix or without.
I may be missing something, but that is my understanding of using cookies.

Since the cookie is owned by us anyway no one should be parsing it

Then should we always generate new format cookie when requests have no cookie or old cookie is invalid? @mattklein123

Since the cookie is owned by us anyway no one should be parsing it

Then should we always generate new format cookie when requests have no cookie or old cookie is invalid?

Just to clarify the current logic:

if a request contains no cookie, then the new format is generated
if a client sends a cookie in "old", non-proto format, but a cluster selected a different upstream host than indicated in the cookie (for example if that endpoint does not exist in the cluster anymore), the new cookie is generated but in the "old" format. Not sure if it makes sense if we assume that we own the cookie and no one should be parsing it. I can change this behaviour to always reply in the new format.

Not sure if it makes sense if we assume that we own the cookie and no one should be parsing it.

Yeah, this is what I want to say. If we think no one should parse it, then seems we can always genere a new format cookie. And after a while (six month), we can remove the old format logic completely.

/retest

/retest

Could merge the main and try the CI again.

This change is not backwards compatible. TTL was optional in the raw encoding but becomes mandatory for the new proto encoding. I think a required TTL is a better security posture, but this definitely would break someone upgrading that didn't set TTL.

Is it because cookie is instantly expired when ttl is zero? I did not change API, so if you do not set ttl, the value is zero. If so, the fix should be relatively easy.

Yes, TTL set to 0 (as recommended by docs for sessions) makes it expire immediately. I'll send a patch.

OK. Thanks!


WIP: App Definition

This defines the application interface.

  1) @fabric/core/types/machine
       Machine
         provides the predicted entropy on first sip with seed:
      AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
+ expected - actual
- '6923e4e00dc073ca76ab4d96aa5eea9a'
+ 'b1ded69edb1e516fcf59be7819208f89'
      + expected - actual
      -6923e4e00dc073ca76ab4d96aa5eea9a
      +b1ded69edb1e516fcf59be7819208f89

      at Context.<anonymous> (tests/fabric.machine.js:33:14)
  2) @fabric/core/types/machine
       Machine
         provides the predicted entropy on first slurp with seed:
      AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
+ expected - actual
- '6923e4e00dc073ca76ab4d96aa5eea9aa830a9bbd2118004af8d63d9212b7373'
+ 'b1ded69edb1e516fcf59be7819208f89af35b7916cc82211cf18b2a9ff258747'
      + expected - actual
      -6923e4e00dc073ca76ab4d96aa5eea9aa830a9bbd2118004af8d63d9212b7373
      +b1ded69edb1e516fcf59be7819208f89af35b7916cc82211cf18b2a9ff258747

      at Context.<anonymous> (tests/fabric.machine.js:41:14)

@melnx — when you get a chance, your review here would be appreciated

@naterchrdsn — you might have some solid input here post-Doorman


Issue with Super Galaxy Rumble Q

If you use it just stays in a single direction when you cast it and doesn't move with you if you turn in a different direction

#1


New driver crash on odbc35

Could any one help use to take a look at this new coming crash?
tail(callstack):
[0] /usr/lib64/libclickhouseodbc.so + 0xd88ab
[1] /usr/lib64/libclickhouseodbc.so + 0xe4cad
[2] /usr/lib64/libclickhouseodbc.so + 0x120688
[3] /usr/lib64/libclickhouseodbc.so + 0x136460
[4] /opt/mstr/MicroStrategy/lib/libodbc.so + 0xedddb
[5] /opt/mstr/MicroStrategy/lib/libodbc.so + 0xb47f3
[6] /opt/mstr/MicroStrategy/lib/libM8DbOd35.so.11.3.0100.1416!MDb::Odbc35::Odbc::SQLFreeStmt(MDb::Error&, MDb::DATABASE_TYPE, MDb::ODBCDriverVendor, void*, void*, void*, unsigned short, wchar_t const*, wchar_t const*, wchar_t const*) [/var/lib/jenkins/Projects/microstrategy/Tech/Server/Common/Database/Odbc35/PrivateSource/Odbc.cpp : 747 + 0xc]
[7] /opt/mstr/MicroStrategy/lib/libM8DbOd35.so.11.3.0100.1416!MDb::Odbc35::OdbcResult::~OdbcResult() [/var/lib/jenkins/Projects/microstrategy/Tech/Server/Common/Database/Odbc35/PrivateSource/OdbcResult.cpp : 688 + 0x26]
[8] /opt/mstr/MicroStrategy/lib/libM8DbOd35.so.11.3.0100.1416!MDb::Odbc35::OdbcResult::~OdbcResult() [/var/lib/jenkins/Projects/microstrategy/Tech/Server/Common/Database/Odbc35/PrivateSource/OdbcResult.cpp : 699 + 0x5]
[9] /opt/mstr/MicroStrategy/lib/libM8PrcCo2.so.11.3.0100.1416!MMultiProcess::MultithreadedExecutor::Run() [/var/lib/jenkins/Projects/microstrategy/Tech/Server/Common/MultiProcess/ProcessCommunicator/PrivateSource/MultithreadedExecutor.cpp : 323 + 0x6]
[10] /opt/mstr/MicroStrategy/lib/libM8Synch4.so.11.3.0100.1416!MSynch::ThreadImpl::ThreadFunction(void*) [/var/lib/jenkins/Projects/microstrategy/Tech/Server/Common/Synch/Synch/PrivateSource/ThreadImpl.cpp : 185 + 0x3]
[11] /usr/lib64/libpthread-2.17.so!start_thread + 0xc5
[12] /usr/lib64/libc-2.17.so!__clone + 0x6d
tail(classifiers): segv
tail(error.message): SIGSEGV /SEGV_MAPERR
tail(hostname): tmstr01h.oebs.yandex.net
histogram(hostname):
tmstr01h.oebs.yandex.net ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 1
tail(uname.sysname): Linux
tail(uname.version): 0.0.0 Linux 4.1.12-61.1.24.el7uek.2.paysys.x86_64 #2 SMP Thu Aug 8 15:33:17 MSK 2019 x86_64
tail(customer_dsi): 126600
tail(cpu.count): 1
tail(version): 11.3.0100.18093
histogram(version):
11.3.0100.18093 ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 1
tail(application): M8MulPrc.11.3.0100.1416
tail(purpose): undefined
tail(reason): undefined
tail(slack_channel_id): undefined
tail(fingerprint;issues;ticket): undefined
tail(fingerprint;issues;tags): undefined
tail(podname): undefined
tail(upload_status_DSSErrors.log): excluded
tail(production_env): 0
Customer Release Set: 11.3.1

Could it be that your code frees the statement handler twice? Check how many times MDb::Odbc35::Odbc::SQLFreeStmt() is called in your reproducible case.


Document new optional support for ConfigMap and Secret

Corresponds to proposal https://github.com/kubernetes/community/pull/175

This change is

@fraenkel One nitpick: on line 320, can you change that sentence to "When this pod is run, the output will be:" because when you say "will include the lines:" I'm expecting there to be some sort of output. Also, it will match better with the other lines later on where you say that.

@chenopis No problem. I was struggling with some of the wording.

@fraenkel Yeah, exactly. Thx!


main: Add -version

Give callers an easy way to extract both the plugin version and the dependency versions.  With this commit:
$ ./terraform-provider-libvirt -version
./terraform-provider-libvirt 48adac309dc181faad7ccd87d52d5e004d5798ec-dirty
Compiled against library: libvirt 3.9.0
Using library: libvirt 3.9.0
Running hypervisor: QEMU 2.9.0
Running against daemon: 3.9.0

The details are very similar to:
$ virsh version --daemon
Compiled against library: libvirt 3.9.0
Using library: libvirt 3.9.0
Using API: QEMU 3.9.0
Running hypervisor: QEMU 2.9.0
Running against daemon: 3.9.0

except the Go bindings do not currently expose the API version.  I've submitted a patch to libvirt-go adding ParseVersion there.  But until then, carrying our own parseVersion shouldn't be too much trouble.
I hunted around for a way to expose this in Terraform.  Currently:
$ cat main.tf
provider "libvirt" {
  uri = "qemu:///system"
}
$ terraform version
Terraform v0.11.8
+ provider.libvirt (unversioned)

but the RPC API is not particularly clear to me, and the versions there may be extracted from plugin filenames and not from RPC calls.

You just click "Restart build" on the travis page for the build. I just did it for you.

@wiking nice thx I will look to it. You can always run also the test locally full with make testacc

i think we can retrieve all teh values with URI var.
This change will not be backward compatible with other Version of the plugins  but is imho a good thing to have ! thx

in case we provide the plugin as rpm/deb

This is even easier, since we'll get the commit information built in.  As it stands, folks who go get the provider (like this) will need to go back to the Git repo manually to retrieve this info.

in case we have a remote kvm-server and we need to take the version ( libvirt-go version and the hyperv version)

The environment variable discussed here should address this.

Mostly in case 2 would need a sort of ssh-mechanism to go to the host..

I don't think we need to go beyond an environment variable for the URI.  If someone needs to SSH to libvirtd, they can use SSH to tunnel a port and then set the URI to the local side of the tunnel.

Imho we could add an helper script not in main for retrieving the version.

This would allow for drift between the two binaries.  I'd much rather stick to a single binary.

We might also investigate how other Provider upstream do it ( AWS etc)

As I mentioned in my initial comment, I'm not aware of a way for Terraform to collect info like this over RPC.  I think it would be awesome if that existed, and it already may, but either way, this integration is beyond me ;).
I dunno if the other providers will have much guidance, since they likely link statically (so no need to wonder "what library version were we dynamically linked to?").  And there's only the one AWS, or at least "which AWS?" does not seem to be configurable, so querying libvirt doesn't seem to have an analog.  Maybe other providers have guidance, but I'm content to model virsh, as I've done here.  It will be easy enough to shift this around later if we come across an alternative approach to follow.

With the default URI resolved, I think this is good to go again.  If there are any remaining issues that I need to address, please let me know.

@wking  yop I agree with you there ! I wll check once I have time for that

I've pushed #445 with a fix for the Travis golint issue.

Yop good point, I need to check.
@wking  would be also awesome that you create a  test for this feature, ( I thing shoud be possible)

@wking would be also awesome that you create a test for this feature

Something like:
make build
test "$(./terraform-provider-libvirt -version | head -n1 | cut -c,50)" = "./terraform-provider-libvirt v"

in Travis?  (I just guessed for the cut, it probably needs work to strip off the mutable parts of the version).  I don't understand @dmacvicar's _service reference.

@wking we build here:
https://build.opensuse.org/package/show/systemsmanagement:terraform/terraform-provider-libvirt
And while the tarball is generated from git, it currently does not include the .git subdirectory

terraform-provider-libvirt.spec has:
Version: 0.0

I dunno what's going on there.  But _service:set_version:terraform-provider-libvirt.spec has:
Version: 0.5.0

It just needs to call go build with -ldflags "-X main.version=v${VERSION}".  Is that something the spec can be updated to do?

_service runs a sequence of services: checkout git, create a tarball, and then set_version service updates the version in the _service file based on the git revision/parent tag.
What we would need to do is to keep the last commit of .git inside the tarball, but I am not sure how to do that. I am sure others have done it already. Better to ask internally inside SUSE, somebody would know.

Oh no, it is even easier, we just need to do:
LDFLAGS += -X main.version=%{_version}

in the spec files.

I did some experiments and -X main.version can be set independently of the variable existing on main. So we can change the spec file to set main.version before merging this PR.

@dmacvicar  nice. imho would be safe also to add a  unit-test before merging it.
I don\t feel confortable adding features (especially command-line args) untested, especially if we depend for variables used/definitd in other files.
Awesome :+1:

and keeping the discussion further, i was thinking to put the SPEC files here in github, so contributors could modify if needed. ( we use the same mechanism @uyuni)
Could be this douable? what is your pov?

I've pushed ef77653 -> 91d0e45 rebasing onto the current master and adding a unit test for printVersion.

I am having problems updating the .spec file.
For non-SUSE we are fine, as we build with plain go build, which I updated to:
go build -ldflags "-X main.version=%{version}" .

But for SUSE we use the %gobuild macro, and I haven't figured out how to add arguments to it.

@dmacvicar we might don\t use the macro?


Upgrade NodeJS

GitHub actions has deprecated NodeJSS v16. Running the action in version 1.3.0 emits this message:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Many actions we use have released this type of change as a new major release.

Did PR https://github.com/gwatts/go-coverage-action/pull/64 help you in any way?


User can edit criteria

Via inline form

better time to resolve this issue after resolve the issue#1106


Add OpenSearch support

This makes it so when users type in package.elm-lang.org in Chrome and hit Tab, it will automatically be searching package.elm-lang.org.
It turns out this is pretty simple:
http://stackoverflow.com/questions/7630144/how-to-add-google-chrome-omnibox-search-support-for-your-site

Better to track somewhere else.

👍 Moved to https://github.com/elm-lang/package.elm-lang.org/issues/243


FEniCS conda Mac OS X questions

Hello, I've installed FEniCS via conda on Mac OS X Sierra, and am able to import dolfin. I have a few questions:

Is mshr available on the FEniCS conda package? I get the error 'no module named mshr' when I try to import mshr.

I also get an error 'name TimeSeries is not defined'. Is there anyway to fix this?

What is the best way to run a FEniCS script in Anaconda? I'm using Spyder, but am not able to obtain any plots. I don't get any errors when I try to plot, I just don't see any plots.

I installed Anaconda navigator (graphical installer), and it was working fine, but after installing FEniCS, (which downgraded Anaconda from 1.4 to 1.2), the Navigator does not work anymore.

Thank you

mshr must be installed separately: https://github.com/conda-forge/mshr-feedstock/
TimeSeries requires HDF5 but DOLFIN is built without it (issue #5)
The conda package is using matplotlib as the default plotting backend. After calling plot doimport matplotlib.pyplot as plt
plt.show()

I don't know. Maybe you can try upgrading Anaconda again?

This is not an issue so I'm closing this. For support use the FEniCS support mailing list.


Explicitly choose the most optimal, and supported tls-model.

The default without -fPIC is 'initial-exec'; with -fPIC is 'global-dynamic'.
Dynamic models are not applicable for enclaves (we don't support multi-module loading),
and therefore are not supported.
The two available models are 'initial-exec' and 'local-exec'.
We choose the most optimal model: 'local-exec'.
Without explicitly choosing the thread-local model, the linker may not always be able to optimize away the "global-exec" (default) threading-model. This could result in enclaves that cannot be loaded.

bors try

bors try

bors try

bors try

bors r+


containong -> containing

Coverage decreased (-1.7%) to 81.013% when pulling ac36def5501cff12de8e5d1c6aeb0ffd94eb9371 on nicholasbishop:patch-1 into 80a1deab58d1faf41c05a5d741d9e3f51bde3a55 on Geal:master.

Coverage decreased (-1.7%) to 81.013% when pulling ac36def5501cff12de8e5d1c6aeb0ffd94eb9371 on nicholasbishop:patch-1 into 80a1deab58d1faf41c05a5d741d9e3f51bde3a55 on Geal:master.

Hi! I'm sorry, this was already fixed in a previous PR: b149c766


Auth request is sent before each api call after update msal-browser from v3.5.0 to v3.6.0

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.10.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.13
Public or Confidential Client?
Public
Description
Access token is not used from cache, auth request is sent before each api call after update from msal-browser v3.5.0 to msal-browser v3.6.0
Error Message
No response
MSAL Logs
No response
Network Trace (Preferrably Fiddler)

[ ] Sent
[ ] Pending

MSAL Configuration
{
    auth: {
      clientId: auth.clientId,
      authority: auth.authority,
      knownAuthorities: auth.knownAuthorities,
      redirectUri: auth.redirectUri,
      navigateToLoginRequestUrl: true,
      postLogoutRedirectUri: auth.logoutUri,
    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE,
    },
    system: {
      loggerOptions: {
        loggerCallback,
        logLevel: LogLevel.Error,
        piiLoggingEnabled: false,
      },
    },
  }

Relevant Code Snippets
export function MSALGuardConfigFactory(auth: IAuthConfiguration): MsalGuardConfiguration {
  return {
    interactionType: InteractionType.Redirect,
    authRequest: {
      extraQueryParameters: auth.extraQueryParameters,
    },
  };
}

Reproduction Steps
If there are several api calls, auth request is sent to 'https://byoidpoc.b2clogin.com/...' before each of them
Expected Behavior
Auth request is sent once to 'https://byoidpoc.b2clogin.com/...' and uses cached value while access token is valid
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge
Regression
@azure/msal-browser 3.5.0
Source
External (Customer)

The cacheLocation should be set to BrowserCacheLocation.LocalStorage or BrowserCacheLocation.SessionStorage, depending on your requirements. Also, verify that the storeAuthStateInCookie option is correctly configured based on your application's needs and the browser being used

There was a known regression in 3.6/3.7, please update to the latest (3.10.0) and if the issue persists please provide trace level logs

auth: {         clientId: auth.clientId,         authority: auth.authority,         knownAuthorities: auth.knownAuthorities,         redirectUri: auth.redirectUri,         navigateToLoginRequestUrl: true,         postLogoutRedirectUri: auth.logoutUri,     },     cache: {         cacheLocation: BrowserCacheLocation.LocalStorage,         storeAuthStateInCookie: isIE,     },     system: {         loggerOptions: {             loggerCallback: (level, message, containsPii) => {                 if (containsPii) {                     return;                 }                 switch (level) {                     case LogLevel.Error:                         console.error(message);                         return;                     case LogLevel.Info:                         console.info(message);                         return;                     case LogLevel.Verbose:                         console.debug(message);                         return;                     case LogLevel.Warning:                         console.warn(message);                         return;                     case LogLevel.Trace:                         console.trace(message);                         return;                     default:                         console.log(message);                         return;                 }             },             logLevel: LogLevel.Trace, // Set to Trace for detailed logs             piiLoggingEnabled: false, // Set to true if you need to log personal identifiable information (PII)         },     },

Trace level logs:
trace-logs.txt

This only contains Trace level logs - could you please share a set of logs that includes all levels? Thanks!

Sure, all levels log is attached, thank you
console-export.txt

I see the same issue after upgrading my msal library, here are the package version I installed the detail
 "@azure/msal-angular": "^3.0.13",     "@azure/msal-browser": "^3.10.0"

Hi @tnorling we are experiencing the same issue. Could we get an update on this? This is a performance impact having to retrieve tokens before every call.

Based on the logs and when this started breaking this looks related to environment matching but I don't have enough detail to see what precisely is happening, nor does this repro with our own B2C sample/tenant. What would be really helpful is if you could check local/sessionStorage for your tokens and see what the "environment" property is. It should match the domain part of your authority url & what you pass to knownAuthorities.

@tnorling this looks correct for our "environment" property and what we're using for authority url and passing into knownAuthorities. all match

@tnorling Yes, "environment" property matches the domain part of the authority url and what we pass to knownAuthorities.

hmm ok are you able to reproduce with our sample? Or could you please share a link to a minimal reproduction?