production fails: 1 more missing directory in repo

after manually adding the directory  /in to repo  production fails:

directory /out doesn't exist in repo out

Did you check out late changes? cannot reproduce the issue. Here is the directory: https://github.com/evshvarov/i14y-csv/blob/master/out/
and here is the setting in docker-compose:
https://github.com/evshvarov/i14y-csv/blob/b7b2997313dcd3cd7b5c9fb74d5f9af9f53ac553/docker-compose.yml
Here is the setting in production:
https://github.com/evshvarov/i14y-csv/blob/ae12783baba67cee3d2063fcde89ba0b123b8c43/src/esh/i14y/csv/F2CProduction.cls

I have of course seen and used your recent changes. (also affects issue #3)
you map your download directory is mapped to /home/irisowner/irisdev
But you refer to /home/irisowner/irisdev/in and /home/irisowner/irisdev/out
and none of these directories exists in your downloaded repo.
and the production fails with missing directory
might be your docker creates it at output (would be quite dangerous)
but I fail to imagine that it also creates it by referencing the input directory
solution:
create /in and /out in your download directory manually after download
and before the start of production.
Or more comfortable for the user add it to your repo as I did in my PR
For GitHub you need to place some empty dummy file inside as
Github doesn't allow empty directories.

Ah, I see.
i have it in dev repo locally.
but they are empty and thus not
being committed as empty to GitHub.
will solve this.
On Fri, Feb 10, 2023 at 3:40 PM rcemper @.***> wrote:

I have of course seen and used your recent changes. (also affects issue #3
https://github.com/evshvarov/i14y-csv/issues/3)
you map your download directory is mapped to /home/irisowner/irisdev
But you refer to /home/irisowner/irisdev/in and
/home/irisowner/irisdev/out
and none of these directories exists in your downloaded repo.
and the production fails with missing directory
might be your docker creates it at output (would be quite dangerous)
but I fail to imagine that it also creates it by referencing the input
directory
solution:
create /in and /out in your download directory manually after download
and before the start of production.
Or more comfortable for the user add it to your repo as I did in my PR
For GitHub you need to place some empty dummy file inside as
Github doesn't allow empty directories.
—
Reply to this email directly, view it on GitHub
https://github.com/evshvarov/i14y-csv/issues/4#issuecomment-1425321845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEP2NEA4TEX54LF6GOK3WWXWHNANCNFSM6AAAAAAUXC7KBQ
.
You are receiving this because you commented.Message ID:
@.***>

all fixed. works fine


contrib: update pg_smtp_client

Updated Dockerfile and Trunk.toml to follow same pattern as other pgrx-based extensions.
I think this will fix the extension installation problem described here: https://github.com/tembo-io/trunk/pull/724#issuecomment-2260804903

Ping @ChuckHend when you get a chance

Thanks!  It's working now


Replace https://github.com/xi2/xz due to no license

While working on #117 I discovered that the xz lib used has no license. We should replace it.
Maybe https://pkg.go.dev/github.com/ulikunitz/xz is a good fit.

SGTM!


Add support for WeakRefs

As the proposal for WeakRefs got finalized as part of ES2021, a rule should be added to disallow its usage.

I think we rather want all of es2021 to be supported, so filed https://github.com/mysticatea/eslint-plugin-es/issues/47


Financial Conduct Authority (FCA) UK (Independent Publisher)

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 doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[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 @gulshankhurana,
I have received more than 10+ emails regarding your changes in this PR.  However our pipelines are failing to validate the files.  Please close this PR and open a new PR with new fork branch.

Hello @gulshankhurana,
I have received more than 10+ emails regarding your changes in this PR. However our pipelines are failing to validate the files. Please close this PR and open a new PR with new fork branch.

Hi @vmanoharas
My apologies. Being a non-dev and a newbie at GitHub, I'm struggling with this whole fork, open and close PR thing so no wonder you received umpteen emails regarding this. Nevertheless, I will try again. Wish me luck.
Kind regards
Gulshan

Closed this pull request, as instructed by @vmanoharas


Adds type param to userCallToActionEmail payload

What's this PR do?
Includes the password reset type as a type parameter.
How should this be reviewed?
Upon https://github.com/DoSomething/blink/pull/236 deploy, test triggering a Password Reset and verify the type parameter is included in the Customer.io call_to_action_email event created.
Relevant Tickets
Per https://github.com/orgs/DoSomething/teams/team-bleed/discussions/34, this allows us to define different event triggered campaigns in Customer.io for the various call_to_action_email events created by Forgot Password or Non-Traditional Member Activations in https://github.com/DoSomething/chompy/pull/65
Checklist

[ ] Documentation added for changed endpoints.
[ ] Tests added for new features/bug fixes.

Thanks for reviewing! 🍕


Fix odd number of logging args

/kind bug
Oversight in https://github.com/gardener/gardener/pull/5268/commits/d15f5db2f27b0a123f904a3e0ca1b33273ae11cd
Fixes https://github.com/gardener/gardener/issues/5292
Thanks @BeckerMax for reporting!

/close in favor of https://github.com/gardener/gardener/pull/5293/files


Logo/icon Proposal for Raw-Dumper

Hello,
This my logo/Icon design for your project. It's free for your project.
I design this logo using adobe illustrator cc 2018. I hope you like this logo.

If you need anything change please contact me
Md Nazmul Hasan
Email<EMAIL_ADDRESS>Thank You.

Ok!
I solicited access to the Google Drive folder
I will update the icon as soon as possible :)

hi, when you use this logo??

Hi,
I solicited access to the Google Drive folder, however, it appears that BitBounce blocked it from appearing on your e-mail, so I still can't download the files.
I'm planning to use the logo when the next version is released, that should happen until the end of the month :)

please check #3

Hi,
I merged your pull request and now I'm going to replace the icon, post the license and mention your work on the about-box :)

thank you

as ur wish

Since everything went well, I'm closing this issue

@mdnazmulhasan27771 i understand a bunch of you people are going around trying to contribute to open-source projects to gain some cryptocurrency with utopian.io
unlike any other person i've found (they merely stole icons from flaticons and tried to pass it off as their own, not even caring about the potential legal action it may cause as the icons are under basic licenses), you actually made your own icons, with a professional product, acted quite professional in speech, and i really want to thank you for that. it makes me happy to see people with good values


Netlify setup

Currently the Netlify build uses my team.  I think it'd be better if we had our own separate KaTeX Netlify team.  Also, I was thinking we should apply for Netlify's open source plan: https://www.netlify.com/legal/open-source-policy/.

How should we go about changing to a separate KaTeX Netlify team?

According to https://app.netlify.com/teams/new, you are supposed to request an Open Source plan on an existing Starter account (can't make one for KaTeX); I think this might trigger the creation of a new KaTeX team.
I've gone ahead and submitted the form.

Should we turn off Netlify auto-building? We just hit 90% usage, and risk incurring $7 charge to @kevinbarabash until this gets approved. @ylemkimon

@edemaine Good idea. I've disabled the build.

@kevinbarabash Did you ever get a response about this from Netlify?

Sorry I've been away.  I have not contacted netlify.  I do think that as a first step would could create a new team and do whatever needs to be done to transfer our current configuration to the new team.

@edemaine I re-read the thread and since you submitted the form I should probably look in my inbox.

I checked my email and did receive a response from Netlify and we have a new OSS sponsored account.  I've invited the both of you. 🙂

@ylemkimon thanks for stopping the auto-builds. ❤

@kevinbarabash Thank you! Could you transfer katex.org to the new team?

@kevinbarabash Here are the instructions. I think only you can do the transfer, as owner, but it is easy:
https://docs.netlify.com/accounts-and-billing/team-management/team-owned-sites/

I've transferred the site over and removed you as members of my netlify team.  It should be safe to restart the site now, but I haven't done so yet.


Removed dots from frontpage words and added lisp

Title says it all.

Accepting seeing that quite a few people in the Slack group want them gone


New field support

Checkbox, select, and select with multi-select

Thanks for the issue! :smile:
If I understand correctly, you mean support for checkbox and select boxes. Is that correct?
If so, any more details on how that would work?

Sure, for checkboxes
{{ember-inline-edit
checked=boolean
field='checkbox'
onSave=(action "changeValue" "boolean")}}
Just need a flag for if the box should be checked or unchecked. gets its value and send it to the action
For select boxes
{{ember-inline-edit
multiple=boolean
options=options
field='select'
onSave=(action "changeValue" "selected")}}
For select it can be a little more difficult. Options should be array of options, maybe key value? Also would be nice to support multiple choice. Let me know if this helps

Thanks for the details! I'll get around to working on it this week. :smiley:

If there hasn't beeen any work done on this yet, I have an idea of how to achieve this: refactor most of the behavior into a ember-inline-control mixin, create a separate component ember-inline-checkbox and have both that and the existing component extend that. This would also facilitate an ember-inline-select component.
The main reason I'd rather have separate components is because right now overriding the template (in order to apply styles/layout) is cumbersome; adding another set of {{if}} blocks is going to make that worse (I'd even like to see an ember-inline-textarea, actually).

That's a good way to go about it. I was wondering whether it would make sense to support custom components (as opposed to just the HTML ones, like text, textarea, select, etc.). A lot of people may be using an ember addon for a select, or maybe even an ember WYSWYG editor, for certain values.
We can allow that with ember's contextual components, like this perhaps:
{{#ember-inline-edit isEditing=false as |inline-edit|}}
  {{#inline-edit.editable}}
    Click here to edit
  {{#inline-edit.editable}}

  {{#inline-edit.editor}}
    {{custom-component}}
  {{#inline-edit.editor}}
{{/ember-inline-edit}}

This makes is really flexible. It can handle most situations but it also complicates things a bit.
Thoughts?

That would be great, and it will be a much needed component as there are several inline edit or x-editable but there is no way to customize the editable component.
Ember power select does not use contextual components but the architecture design is perfect, maybe you can borrow some ideas.

@frisco82 — I'll take a look at power select! 👍

Okay, I looked at it! With a select component, the good thing is that it still is very clear with a normal block. Something like:
{{#select as |option|}}
   {{option}}
{{else}}
   No options
{{/select}}

... reads very well and is extremely clear. For this addon, I got this working:
  {{#ember-inline-edit value=value}}
    {{some-custom-component value=value}}
  {{else}}

{{value}}

  {{/ember-inline-edit}}

I'm not sure this is very clear though. What do you think?

Okay, I gave this a shot. It's on the block-components branch. Feel free to take a look.
It'll work something like:
  {{#ember-inline-edit as |inline-edit|}}
    {{#inline-edit.editable}}

{{value}}

    {{/inline-edit.editable}}

    {{#inline-edit.editor}}
      {{custom-editor-component value=value}}
    {{/inline-edit.editor}}
  {{/ember-inline-edit}}

This is a little verbose but it allows flexibility in both the editor as well as the editable. You can have a select box, for instance, when a user wants to edit, and the value could be wrapped in a heading tag.
We can also make it somewhat less verbose like this:
  {{#ember-inline-edit as |inline-edit|}}
    {{#inline-edit.editable value=value}}

    {{#inline-edit.editor}}
      {{custom-editor-component value=value}}
    {{/inline-edit.editor}}
  {{/ember-inline-edit}}

Thoughts?

That looks like the approach to take, but I think the input/text area logic should be moved to separate components that can provide blocks to ember-inline-edit. You'd have both simpler templates and an example of how to provide blocks.

@CygnusRoboticus — Can you give an example? Creating separate components for text (and related), textarea, and other custom components is fine I think.

May be you can pass a parameter with the component to use for editing as with the value but it could only be used for custom components, It will be very rare that a public component complies with any standard API for value and actions.
That would lead to 3 diferent usages to fit everyone:
Reduced inline templates
  {{#ember-inline-edit as |inline-edit| onSave=(action save)}}
    {{#inline-edit.editable value=value}}
    {{#inline-edit.editor}}
      {{input value=value onBlur=inline-edit.save}}
    {{/inline-edit.editor}}
  {{/ember-inline-edit}}

Full inline templates
  {{#ember-inline-edit as |inline-edit| onSave=(action save)}}
    {{#inline-edit.editable}}

{{value}}

    {{/inline-edit.editable}}
    {{#inline-edit.editor}}
      {{input value=value onBlur=inline-edit.save}}
    {{/inline-edit.editor}}
  {{/ember-inline-edit}}

Custom components
  {{#ember-inline-edit as |inline-edit| onSave=(action save)}}
    {{#inline-edit.editable editableComponent='displayValue'}}
    {{#inline-edit.editor editableComponente='editValue'}}
  {{/ember-inline-edit}}

In fact maybe the last one could be reduced even more:
 {{#ember-inline-edit as |inline-edit| onSave=(action save) editableComponent='displayValue' editorComponent='editValue'}}
But I am not sure if you cand handle easily optional contextual components

@frisco82  — In this case:
  {{#ember-inline-edit as |inline-edit| onSave=(action save)}}
    {{#inline-edit.editable editableComponent='displayValue'}}
    {{#inline-edit.editor editableComponente='editValue'}}
  {{/ember-inline-edit}}

The custom components will have some data of their own, so you'll end up passing a few more attrs, right? Say you want to pass in a user's email and name, for example. I don't think we can cater to those requirements very well. My thinking is that if there are complex custom components, toggling between them is better as a separate component instead of using an addon like this. It just gives you a lot more control.
For the more common cases like using a custom select box or a custom WYSWYG editor, being able to do that even through an addon like this makes sense.
I like this:
  {{#ember-inline-edit as |inline-edit| onSave=(action save)}}
    {{#inline-edit.editable value=value}}
    {{#inline-edit.editor}}
      {{input value=value onBlur=inline-edit.save}}
    {{/inline-edit.editor}}
  {{/ember-inline-edit}}

I haven't been able to figure out a way to remove the editable component (and just pass in the value) but other than that, I think it's clear enough and can handle the more common cases.
What do you think?

As I tried to say the use case for passing the components directly only makes sense when they are app specific components, but it makes sense if you have a want to reuse the editor or editable markup and not the full component.
For example you can have a editable component that it shared in fields that are checkboxes, textareas and emails.
And the editor maybe it is shared between inline editable and regular fields on different parts of the app.
In those cases you should set an atrribute 'value' on the main ember-inline-edit that is setted to the custom component along with another object with the actions (open, close, save).

@frisco82 — That makes sense. 👍
I'll try to figure out an API for it.

@swastik The example I would provide is basically what your last code block is:
{{#ember-inline-edit as |inline-edit| onSave=(action save)}}
{{#inline-edit.editable value=value}}
{{#inline-edit.editor}}
{{input value=value onBlur=inline-edit.save}}
{{/inline-edit.editor}}
{{/ember-inline-edit}}
An inline-input and inline-textarea component both need templates similar to this, then you can remove the textFields and textAreaFields logic from ember-inline-editor.
It looks like you're already taking a crack at it, but I'm more than willing to contribute if need be.

@CygnusRoboticus — Great, I think I get it now! 😄
I'll work on it on the block-components branch this week.

Sorry for the (massive) delay!
Largely fixed in #12. 😄


b2i donot need sourceurl

Signed-off-by: runzexia<EMAIL_ADDRESS>B2i will correspond to a new sourceURL each time run, so there is no need to specify sourceURL in s2ib

/lgtm


Non negligible divergence between recorded metric and original expression

What did you do?
To speed up console node list, I created a record rule:
node:cpu_iowait:cur_avg = 100 * (avg without(cpu, mode) (irate(node_cpu{mode='iowait'}[5m])))

What did you expect to see?
I expected the recorded metric to be almost identical to the original expression.
What did you see instead? Under which circumstances?
Instead, graphing
abs(100 * (avg without(cpu, mode) (irate(node_cpu{mode='iowait'}[5m]))) - node:cpu_iowait:cur_avg)

shows a divergence of more than 20% on multiple occasions:

DISCLAIMER: The server showing the highest divergence is one our most busiest.
Environment

System information:

$ uname -srm
Linux 3.19.0-61-generic x86_64`

Prometheus version:
I'm using a Docker container.

From /status:
Version 	0.20.0
Revision 	aeab25c

Prometheus configuration file:

global:
  scrape_interval:     15s # By default, scrape targets every 15 seconds.

rule_files:
   - rules/node_speedup.rules

scrape_configs:

  - job_name: 'node'

    # Override the global default and scrape targets from this job every 5 seconds.
    scrape_interval: 5s

    static_configs:
        <node_list>
        ...

Logs:

I didn't see any relevant entries.

Given the default eval interval is 1m and you're scraping every 15s, this is an expected result when using irate. Try rate instead.

Thank you Brian, I'lll close this issue as I'm not working on it anymore.


deformable_col2im invalid argument error in pytorch 1.0.0 branch

Hello,
I'm in pytorch_1.0.0 branch
I got the same error in
https://github.com/chengdazhi/Deformable-Convolution-V2-PyTorch/issues/13
but in the pytorch_1.0.0 branch, there is no src/deform_conv_cuda_kernel.cu file,
so I searched for GET_BLOCKS
which now exists in src/cuda/deform_im2col_cuda.cuh
after changing this I still get the error.
Unfortunately I'm not familiar with the cuda kernels,
could you help me out?

realized I didn't do make.sh after changing the code,
but now I see Too many resources + Jacobian mismatch error again...
https://github.com/chengdazhi/Deformable-Convolution-V2-PyTorch/issues/15
I have Titan XP w/ 12GB
tried with 1024, 512, 256

Have you solved your problem? I meet the same problem.

Hi,
I am facing the same issue. Has someone solved this?
Using GTX TITAN X 12GB


Think of the sexiest possible name

hubot-steak-podium (current)
streakbot
streak-ladder
hubot-github-streak
...?

I like hubot-streak-ladder

The sexiest name possible is obvious: hubot-streaklife
I also like the obvious and easy to search: hubot-commit-streak


[Bug]: /guidelines/typography/overview Page not displaying all content

Package
@carbon/type
Browser
No response
Package version
N/A
React version
No response
Description
I am seeing this in the carbon design type page in production

CodeSandbox example
N/A
Steps to reproduce
N/A
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

This will be fixed with our v11 release. 👍

I can confirm this has been fixed, though there's a problem with not having proper font styling applied.
I've opened a new issue https://github.com/carbon-design-system/carbon-website/issues/2900 to address.


allow objectDropdown in known.anyobj, allow changing socket in dropdownOnly mode

Allow a known function that is considered known.anyobj (starting with *.) to specify an objectDropdown - which is essentially the same as a parameter dropdown, but instead applies to the callee.object (the left side of the MemberExpression)
A little known feature allows you to specify dropdownOnly inside your dropdown object, which makes the socket non-editable. Unfortunately, the dropdown couldn't change the socket text in this case as well, so I fixed that.
PR feedback from last PR (https://github.com/droplet-editor/droplet/pull/160): use CoffeeScript existential operator

@Bjvanminnen

lgtm


Empty attribute name produces invalid XML output with using xmlParser

Fix issue #1474
In my opinion, since the value of attribute name is empty, this result of parsing seem more reasonable

Added two new variables hasIllegalAttributeName and illegalPendingAttributeName used to record the current key values are reasonable and while building the XML dom tree the illegal key value will change to empty

Thanks - agree that we can just drop attributes if they don't have a name. But I don't see that we need these extra state values in the token , and fear that they will just lead to extra complexity. Seems simpler just to check and  drop on the emit / finalize stage.


Android Basics: Fragments Navigation component

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-fragments-navigation-component?authuser=1&continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-2%3Fauthuser%3D1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-fragments-navigation-component#3
In which task and step of the codelab can this issue be found?
Unit 3
Introduction to the Navigation component
step 4
Describe the problem
In section 3, there is a code error about "Update tools:context in fragment_letter_list.xml to .LetterListFragment".
Example code does not update successfully.

@codewpf
Do you mean code snippet is not correctly updated?

Not the OP but I think it is a dupe of #33

@codewpf
Thank you so much for reporting this issue. This is fixed and will be published soon.


Consider renaming recipe to task

The word "recipe" comes from make's terminology. However, since just is not a build system that is intended to produce artifacts, the term is a bit lacking. The best alternative to is probably task.
I'm waffling over whether or not this change is a good idea, so 👍 if you prefer the name task, and 👎 if would rather that we keep the existing recipe terminology.

action?

Action is okay, although I haven't seen it used in that sense before. I like that they would be "just actions" though. It has kind of a poetic ring to it.

Since the first comment had multiple suggestions, can I 👍  "just tasks"? :)

I like term "recipe". It sounds... tasty 🍰

I like task, action, and chore better than recipe, myself. And in that order.

I would go with command. Here are some extremely subjective and personal reasons (add "for me" to every statememt :-)):

task has other connotations, e.g. compute workflows (with tasks), CI systems with build tasks, and the like
command puts the emphasis on the user of just. I see just as a way of nicely packaging and specifying commands, that I as a user am invoking. task implies some automated procedures
I use just as a kind of "command-ops", as an extension of "git-ops". "task-ops" doesn't capture the power and end user ease and UX enjoyment compared to "command-ops".
command sounds cooler (I am very scientific)
replace "task" with "action" and my above preferences stand

I can't believe I have such strong preferences but just is changing the way I organize complex mono-repos, and I have manually changed the default to "Commands:" myself. Thanks for changing my life @casey !

I think the ship has sailed on this one.


Documentation Request: mount and config storage devices

Is your feature request related to a problem? Please describe.
I'm unsure how to mount drives.
Describe the solution you'd like
A short documentation of how to mount your storage devices.
Additional context
I'm looking for best practices on how to mount your storage and what to configure about that.
I would love to see something in the documentation about that.

There are lots of docs already on ZFS - https://davidstephens.uk/ansible-nas/zfs/zfs_overview, but automating it is outside of the scope of Ansible-NAS.


Remove the shared ElastiCache instance

Since moving to using in-cluster Redis for our Apps, we need to check if the shared ElasticCache is being used and remove it.

I've checked for active client connections in prod and staging, and didn't see any. I have modified the security group rule for the cluster in staging, and will leave it for a couple of days to see if anything breaks.
If its all good next week, I'll start shutting down the clusters.


Prepare the Scala.js integration for SIP-51.

When using Scala.js 1.15.0+ together with Scala 2, we now add an explicit dependency to the scalajs-scalalib artifact. That artifact comes with Scala.js 1.15.0+, and is double-versioned with the Scala version and the Scala.js version.
As SIP-51 gets implemented and future versions of the Scala library may break forward binary compatibility, the new scalajs-scalalib will be able to bring in new APIs back to existing Scala.js versions.
This commit mimics the changes done to sbt-scalajs in https://github.com/scala-js/scala-js/pull/4913/files#diff-adc7ad642b8f89aab3d2a81ac25b23e345bbea758b1c8bbea46cc9d1f351834c

SIP-51: https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html

Thank you for opening this pull request, @sjrd . It looks reasonable.
What's the next step? Should we merge it right away or wait for some state change / announcement of SIP-51?

It can be merged right away. sbt-scalajs 1.15.0 already behaves this way.
It is already beneficial irrespective of SIP-51 (though with much smaller consequences): if there is a bugfix in a newer version of the standard library, users of the new Scala version will get the bug fix, instead of having to wait for a newer version of Scala.js that has itself upgraded to the newer Scala.


Catalog Graph overwhelmed

We have imported a number of services with their APIs and consumption, and provision information.
It makes for a very complex graph, some services have lots of consumers (~30s) , others consume a lot of services, etc.
When selecting the explore graph to render just the consumption and provide relationships, components and APIs, infinite depth we have a graph that makes sense but it is missing relationships.
We have 3 services that are called by almost everything. They should be 3 very clear nodes in the graph, but we can only see one.

That node selected has like 30 incoming lines. Other of the key services (upper right) has a fair number but the third key service has only 5 incoming links, but if I select that one then it will have 30 incoming and the previously selected service just 5.
In short, I think the library is unable or unwilling to draw so many lines and it is removing them for readability, perhaps.
The problem is that then we have low trust on the graph as we do not know when it will choose to cut corners.
Also, we can't use it to see our whole platform in one graph that was kind of the goal here.
Settings

Hey - I know that @ZubairRafiq has solved this problem already for one of our clients - I will send him the issue and I'm sure he can help here.

As you have mentioned that when the maxDepth is set to infinite, perhaps it chooses to cut down several lines. In our case we decided to set the default value of maxDepth to 2 for better readability of graphs. Simply by passing maxDepth : 2 prop to CatalogGraphPage.

Maybe worth then, to set the default depth to a smaller value right?

For sure, that will provide better readability.

I would like to work on this issue. Could I please be assigned to it?

Sure. Assigned!

Looks like this was fixed in #14884, closing. Feel free to comment if there's something we missed.

I do not think this solves the issue. I could manually look at less information already.
The whole point is to have a view that includes all the components. That view does not render well. That not being the default does not make it render better.

Hi, The graph issue is still there. Can anybody confirm if this is resolved?
Also we can see another piece of PR related to this but isn't merged yet
https://github.com/Bonial-International-GmbH/backstage/commit/da0bf25d1a893f1c0ecb19df0431c60f83874781#diff-a4de9e719f3904dc40d526d0f2f529c946f978010111879bda37a5d06b89ff0b
@pjungermann can you confirm on this issue if this was resolved and what actions steps do we need to take.

@Tushti02 not sure what you mean by "isn't merged yet". It was merged at PR #14466
Also, I think it is not really related to the issue here.


Handle npm-shrinkwrap.json with no dependencies

Fixes https://github.com/ansble/safe-shrinkwrap/issues/8

Sorry for the delay on this!


Remove duplicated laravel installer code

I did remove duplicated Laravel installer code in workspace Dockerfile
I completed the 3 steps below:

[x] I've read the Contribution Guide.
[ ] I've updated the documentation. (refer to this for how to do so).
[x] I enjoyed my time contributing and making developer's life easier :)

@lanphan Did you try to log-in with root user and run laravel new after this change?
I think your comment can broke this thing.
See also: https://github.com/laradock/laradock/issues/1717
and my pull: https://github.com/laradock/laradock/pull/2176/files


Look into removing Collation.transaction_fee_sum from

What is wrong?
The Collation object currently uses a stateful and mutation based mechanism for storing the total transaction fee.
https://github.com/jannikluhn/py-evm/blob/65d7b24d718b1aa1238ba72a385d16baa93498e7/evm/vm/forks/sharding/collations.py#L29
It would be better if we can find a way to track that value and expose it in the appropriate place(s) in a more explicit way.
How can it be fixed
Need to investigate.

deactivate


Please help!. I can not hear anything

Please help me. In the Script: UdpPacketReader.cs
Function:
public byte[] ReadBytes(int length)
{
byte[] buffer = new byte[length];
var read = _inner.Read(buffer, 0, length);
if (length != read)
return null;
return buffer;
}
Always return null. Because "read = _inner.Read(buffer, 0, length)" always return 101, with every value "length".
Thanks so much for your help.

That's interesting because I haven't experienced any issues there. Could you tell me a bit more about how you're using this asset? For instance, are you receiving audio from Mumble-Unity, or a different Mumble client?

Thanks for your reply. I use Plumble - Mumble VOIP App android to send voice, and use Mumble-Unity to listen. The audio data is transmitted, but can not be read and converted to audio, because the problem in above Scripts. Do you think the problem from Plumble - Mumble VOIP App or above Script. Thanks so much!

I use Plumble with this asset, so my guess is that there's a configuration issue somewhere.
Do you know if you're streaming Opus or Speex audio? This asset doesn't support Speex because it's a fairly outdated client. If you are able to change settings for the Murmur server, you can force it to only use Opus and not Speex anywhere.
If you are using Opus, can you tell me what the value of "size" is before ReadBytes is called?

Hi BananaHemic, now I used Plumple with this asset. And I have heard the sound, but the signal is just noise. Ex: ss..sss..ssss

Hi BananaHemic.
I'm sure using Opus, using local loopback. Do I need to configure anything?
Thanks

The asset should work out of the box without any configuring other than enforcing Opus everywhere.

Do you still only get noise if "Use synthetic source" is on?
Do you get a log message saying what frequencies the microphone supports?
If you have more than one mic available on your machine, can you try cycling through "Mic Number To Use" in Mumble Microphone?
Can you post the full logs?

Thank you very much for the great help from you. After all day adjusting, I have successfully build it. Thanks so much again!!!


Docs

Improve docs

Coverage remained the same at 81.0% when pulling a6345dc4294cecacbd00090fb2deb36868578e32 on feature/better-docs into 1bf2eb372a06f6953b29afc192666ccbbeaa4a06 on develop.


Better fix to iOS zoom bug on orientation change

I was exploring MBP the options to address the famous iOS zoom bug when you change your device to landscape when I started thinking about a different solution.
Currently, MBP suggests using the viewport width=device-width which fixes the bug. But we know the device viewport is stuck in 320px even if you rotate your device. If the user wants to solve this by setting initial-scale=1, MBP suggests an script based on @shichuan solution that fixes the bug but have several issues (if the user zooms, the script doesn't work anymore; the zooming only happens in the second gesture, ...).
I think I got a better solution that allows user zooming all the time (never disabling it), allows different viewport sizes for both portrait and landscape and doesn't seem to have any UX issues. I used a trick with CSS scale transformations to properly scale the page.
I created a small project here to showcase my solution:
https://github.com/sergiolopes/ios-zoom-bug-fix
There's a demo and the code has many comments. I did some real world demos too, applying the hack to famous mobile sites to see if it works in the wild (and apparently, it does :).
What do you think?

Nice approach, although reading your GitHub readme I think this could cause undesirable effects to the way people commonly use media queries in their sites, due to it using width=device-height? I'm sure you can work around it ok, but having to do so for a single bug on one platform kinda seems overkill in the grand scheme of things? I'm also not sure about the possible effect of applying CSS transforms to very large pages on some sites… would need more testing.

The media querie issue is the only big caveat. Maybe the script should provide a solution to automatically convert media queries to the new version.
During my research, I found a solution using width=device-width normally. But in this case I have to scale down the page on landscape (the device-height solution scales up on portrait). Scaling down has some issues on older iOS versions but works fine.
I got a pure CSS solution (no JS) based on this idea: https://gist.github.com/1935528
And do you have some big page example so I can test performance? I tested using famous sites from mediaqueri.es, including BostonGlobe.com that is huge, and everything seems pretty fast even on my old 2nd gen iPod Touch.

Another cool solution MBP could use is @scottjehl's one:
https://github.com/scottjehl/iOS-Orientationchange-Fix
As all solutions (including mine), it also has some limitations, but it seems better than the currently solution MBP adopts.

I'd like to see how older versions of iOS handle this, as well as the iPad. But even if performance was ok, I think the other side effects are perhaps just as significant as the limitations of other solutions mentioned here.


Checks&Radios: Increase the size to follow the brand

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues
NA
Description
Working on an example, I found this issue, so here is a separate PR to tackle this.
Motivation & Context
Checks and Radios are too small compared to the design.
Types of change

Bug fix (non-breaking which fixes an issues)

Live previews

https://deploy-preview-1860--boosted.netlify.app/docs/forms/checks-radios

Checklist

Contribution

[x] I have read the contributing guidelines

Accessibility

[x] My change follows accessibility good practices; I have at least run axe

Design

[x] My change respects the design guidelines defined in Orange Design System
[x] My change is compatible with responsive display

Development

[x] My change follows the developer guide
(NA) I have added JavaScript unit tests to cover my changes
(NA) I have added SCSS unit tests to cover my changes

Documentation

[x] My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

(NA) My change introduces changes to the migration guide
(NA) My new component is added in Storybook
(NA) My new component is compatible with RTL
[ ] Manually run BrowserStack tests
[ ] Manually test browser compatibility with BrowserStack (Chrome >= 60, Firefox >= 60 (+ ESR), Edge, Safari >= 12, iOS Safari, Chrome & Firefox on Android)
[ ] Code review
[ ] Design review
[ ] A11y review

After the merge

[ ] Manually launch Percy tests

Checkboxes and Radio buttons are now the correct size. All looks good to me.

in terms of size, good to me
but i glanced at this page and I saw the chapter "star rating"
What a surprise when I saw that the unchecked stars are in gray to not contrasted enough although they convey information and are activable.
We must increase contrast!

IMO this PR should also tackle a change of margins for the .form-checks.
With the new size, they are really close together by default:

Thoughts @louismaximepiton?

As far as I can see, it seems like 20px is common at Orange, should I set it to 20 or maybe only 10 ? Might be asked to a designer maybe 🤔 Or maybe change the min-height to 1.875rem that would be closer to what Bootstrap propose ?
Thinking out loud here but shouldn't we avoid small margin like .125rem ?

Designer:

I think the default vertical space between checkboxes should be 15 px.

https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/1860/commits/f30721b8b0dcfd9f829143a078258d6d11686541 takes care of it.

Should be resolved right now.
For instance checked:

dropdown page
list-group page
table page
navbar sticky example page
check&radios page
layout page
overview page
validation page


feat: Add RepositoryCollaborator resource

Description of your changes

Fixes #104
Adds the RepositoryCollaborator resource.

@asafhm Your commit is great, so you can sign-off it with ssh key. The team will verify you PR.

Thank you! 😁 Signed it.

Why is the bot unhappy? Seems to be signed now?

@steveizzle Sorry my bad. Fixed it now.

Any chance to get this looked at?

please..?

@asafhm Will get back to this. The CI runs are not triggered so that needs some investigation.

Thank you all


updates based on operator-sdk scorecard test

update operator to satisfy operator-sdk scorecard tests
Add .osdk-scorecard.yaml file for operator-sdk scorecard tests
list of tests: https://github.com/operator-framework/operator-sdk/blob/master/doc/test-framework/scorecard.md#what-each-test-does
in the current state the operator passes all scorecard tests except Writing Into CRs Has An Effect: https://github.com/operator-framework/operator-sdk/blob/master/doc/test-framework/scorecard.md#writing-into-crs-has-an-effect

operator-sdk scorecard output
Basic Tests:
        Spec Block Exists: 1/1
        Status Block Exists: 1/1
        Writing into CRs has an effect: 0/1
OLM Tests:                                                                                Provided APIs have validation: 1/1
        Owned CRDs have resources listed: 1/1                                                                                CRs have at least 1 example: 1/1
        Spec fields with descriptors: 0/0                                                                                Status fields with descriptors: 2/2

Total Score: 76%
SUGGESTION: The operator should write into objects to update state. No PUT or POST requests from the operator were recorded by the scorecard.


refactor!: Supply SignedBlock instead of SignedTransaction to peer

Description
This is first part of #4696:

Added topology field to genesis.json
Changed kagami genesis sign to generate SignedBlock
Adapted iroha_swarm to those changes

Planned changes for next PRs:

Provide hash of genesis block to all peers (#4555)
Allow multiple peers to submit genesis

Benefits
Checklist

[x] I've read CONTRIBUTING.md
[x] I've used the standard signed-off commit format (or will squash just before merging)
[ ] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

A thing that I have noticed. We don't validate genesis instructions at all anymore because there is no initial executor. This is a bug, only the 1st instruction (which is upgrade) should not be validated, all others should


Waiting for a server call to return

Hey Chris -
At one of our routes we should wait for a server call to return before the route is executed.  I wasn't sure how to tackle that?  I realize there's a wait method, but what about a "continue" ?
Cheers,
. Dirk

i dont know if this is the best solution. But i am doing this to wait on a Meteor.call response
Ready = new Blaze.ReactiveVar(false);
Router.route('feed',{
waitOn: function () {
Meteor.call('getInstagramUserFeed', function(error, result) {
if(!error) {
Ready.set(result)
}
});
return [
function () { return Ready.get(); }
];
},
action: function () {
if (this.ready())
this.render('feed')
else
this.render('LoadingMany');
}
});
what do you think?

Hey @ivan9074 - looks like a clever solution!
Interested to hear @cmather thoughts on this.

Hi @DirkStevens, As @ivan9074 shows with his example, the wait list can be populated with any function that returns a truthy or falsy value. If the function is reactive, it can reactively trigger a state change in the wait list (true to false or false to true). This affects this.ready() in your route functions. So you can just return a function that returns true or false reactively.
You could also just build your own reactive variable that a helper uses. For example, a helper might render something if the reactive variable is true, otherwise render a loading template.

@cmather I have a similar use-case to this; I need to build a complex object when a route is triggered and I do this with a Meteor.call('create-product', function (error, product) {...});. Ideally I then want to pass this product into the data for the route, but I can't seem to figure out a way to stop the route from loading until after the Meteor call is complete... Any ideas?

+1

Wow. this works thanks for this, but this feels so sloppy. Isn't there a better way? a simple promise? I have to tack on these session variables just to set defaultValue in react?
There's got to be a better way


Fix little

Fix for #16  and #17

Is there an ETA for when this fix will be available on PyPI?

I just published the version 0.7.1 with the latest fix.


Fix OrgAdmin permission

Purpose
A user with the role OrgAdmin shouldn't be able to change things from another organization.
Related issue: #825

Coverage decreased (-0.02%) to 52.465% when pulling 964e62e14ae0f15e7f2e606ff18bd0c44d2477b9 on jefmoura:fix-org-admin-permission into a2d9f6b72852584b091a177383bff864d1b728d2 on toladata:dev-v2.


create DataFrame from dict with different data type, cat't change value then.

I try to make a DataFrame from a dict, and need to change it's value then. I find when dict as different data type value, It does't work.
dict has same data type, It works.
from pandas import DataFrame
a = {'a': 1, 'b': 1}
df = DataFrame([a])
print df
rec = df.ix[0]
rec['a'] = 100
print df
out:
a  b
0  1  1
a  b
0  100  1
dict has different data type, go wrong.
from pandas import DataFrame
a = {'a': 1, 'b': '1'}
df = DataFrame([a])
print df
rec = df.ix[0]
rec['a'] = 100
print df
out:
a  b
0  1  1
a  b
0  1  1
-c:6: SettingWithCopyWarning:
A value is trying to be set on a copy of a slice from a DataFrame
See the the caveats in the documentation: http://pandas.pydata.org/pandas-docs/stable/indexing.html#indexing-view-versus-copy

That's working as expected. Have a look at the documentation in the warning message, which explains that

A multi-dtyped DataFrame (meaning it has say float and object data), will almost always yield a copy

rec = df.copy()
rec.loc[0, 'a'] = 100

or if you want to modify df:
df.loc[0, 'a'] = 100

@TomAugspurger Thank you! I got it!


Job Id pipelinebatch component deployment creation

Description
Fix job id workflow for pipeline batch  component deployments
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


feat: set Items as optional in ItemsProvider

🙋 Feature Request

The ResolveItemsRequestAsync method assumes that the Items from the ItemsProvider can be null, but the GridItemsProviderResult type forces the list. Loading indicator terminates even if no satisfactory results are received.
🤔 Expected Behavior

It is possible to specify null as Items.
😯 Current Behavior

Items must be a list.
💁 Possible Solution

🔦 Context

DataGrid with Virtualize parameter when first running ItemsProvider gives req.Count as null.

No, we are not going to change that logic. Even if the result is that no rows are being returned, the grid is then no longer in a Loading state. It is not on us to interpretate if that is a satisfactory result or not.

Do you have any other idea to bypass the problem with req.Count as null?

I think that is something that needs to be handled on 'your' side. We can't determine what is right or wrong when null is returned.

Perhaps there was a small misunderstanding.
I would like to deal with invalid input parameters on "my side" (e.g. req.Count is null) but I can't as after every ItemsProvider call the loading indicator disappears and doesn't open when ItemsProvider called again.
private GridItemsProvider<RowDto> InitialProvider => async req =>
{
    try
    {
        _grid.SetLoadingState(true);
        if (req.Count is null) throw new OperationCanceledException();
        var results = await new GridCommand(args).Execute(req.CancellationToken);
        return GridItemsProviderResult.From(
            items: results.Items,
            totalItemCount: results.TotalItemCount
        );
    }
    catch (OperationCanceledException ex) {}

    return GridItemsProviderResult.From(
        items: Array.Empty<RowDto>(),
        totalItemCount: -1
    );
};

The disappearing of the loading indicator is by design. The provider has retuned, so loading is done.

So in the case of using the Virtualize parameter, which gives req.Count as null on the first load? Should I use an external loading indicator?

No, you should anticipate on that first request returning null. You know that will always be the case.

At this moment, I have no way to handle it.
I tried with OnAfterRender, loading flags, etc., but nothing worked.

Sorry to hear that. Up until now, there has been no issues/discussions around this. You must have a pretty unique use case.

I will make a reproduced example and report the bug issue if it is not a problem.

Sure, no problem. But as this is one of the most used (and most complex) components, we will be very careful to not have any breaking changes. So no guarantee that your issue can or will be resolved.

Of course!


Vue-Cropperjs issue with 5.0.0 version

I am getting error with latest version of vue-cropperjs (5.0.0). The code is working fine with older version 4.2.0.

The error is -  Error in mounted hook: "Error: The first argument is required and must be an  or  element."
Can you please help me out for this issue.

5.x.x only use vue3
4.x.x only use vue2
vue3 and vue2 is not compatible

As @aibow said, 5.0.0 is only for vue 3.


Add Rx Design Guidelines to source control

Copied from https://rx.codeplex.com/workitem/62
(Rx Design Guidelines.pdf attachment not included)
I thought it would be good to add the Rx Design Guidelines document to source control, and maintain it on an ongoing basis. It's proved extremely useful to me on several occasions.
Current found on MSDN at:
http://go.microsoft.com/fwlink/?LinkID=205219
And attached.

Done; in a future release, we may convert this to wiki pages.


[Help] Add Buttons

Hello,
How do I add the add and remove button?
Thanks!

Solved,
How Add Icon
https://github.com/bosskmk/pluto_grid/blob/master/demo/lib/screen/feature/cell_renderer_screen.dart


Estimote IndoorLocation works on Marshmallow but not Pixel 2 or the S9

Prerequisites

[x ] Put an X between the brackets on this line if you have done all of the following:

My beacons have Estimote Location packet enabled (Check it in the Estimote Cloud, or via app)
My Android device/devices supports BLE and has Android OS version >= 5.0.0
My Android device/devices have bluetooth enabled
My app has Location Permissions granted

Basic information
Estimote SDK version: [Paste here the SDK version that you are using (like 0.1.0-alpha.6)] 'com.estimote:indoorsdk:2.5.3'
'com.estimote:sdk:1.0.12'
Android devices affected:
Pixel 2
Samsung S9 Plus
Android OS version affected: [Android OS version (ex. Oreo 8.0.0)]
Pie (Pixel 2)
Oreo (S9)
Beacon hardware version:
F3.3
Description
Using the sample code (described https://developer.estimote.com/indoor/android-tutorial/), the app worked as expected on Android Lollipop and Marshmallow. However, on phones with Android Oreo and Pie, it seems that the OnPositionUpdateListener always calls hidePosition().
Steps to reproduce:

Follow the tutorial and create an apk
Test the APK on the devices
Run the app

Expected behavior:
An avatar that represents the user moves around in between the displayed beacon as the user moves around in real life.
Actual behavior:
The beacons are displayed, but the avatar is hidden as onPositionOutsideLocation is constantly called on the OnPositionUpdateListener. However, this only appears to be happening on our newer devices.
(Optional)
I am not sure if this is an operating system issue, but I suspect it may be related as the same exact apk works on the older phone models and not the newer ones.
Add here any logs you want to attach, or any other info, like pictures for example

Same issue on OnePlus 6 and 6T with android Oreo.

I was in contact with Estimote and they told me to add the following dependency to my build.gradle:
implementation 'com.estimote:scanning-plugin:0.24.0'
this is a newer version of the scanning plugin that hasn't been updated yet in the indoor SDK, this newer dependency will overwrite the one from the indoor SDK, this solved my issue


Unexpected key(s) in state_dict

self.disp_score = torch.range(0, max_disp - 1)  # [D]
Traceback (most recent call last):
File "train.py", line 215, in
main(args)
File "train.py", line 75, in main
model.load_state_dict(state['state_dict'])
File "/home/cb/anaconda3/lib/python3.6/site-packages/torch/nn/modules/module.py", line 719, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for PSMNet:
Missing key(s) in state_dict: "cost_net.cnn.conv0.0.net.0.weight", "cost_net.cnn.conv0.0.net.1.weight", "cost_net.cnn.conv0.0.net.1.bias", "cost_net.cnn.conv0.0.net.1.running_mean", "cost_net.cnn.conv0.0.net.1.running_var", "cost_net.cnn.conv0.1.net.0.weight", "cost_net.cnn.conv0.1.net.1.weight",

Did you use one GPU?

Did you use one GPU and comment out the model = nn.DataPararell(model, device_ids)?
Hi, I have the same problem.I run train.py by one GPU, and i get errors when i try to test the model. How should I save the model in training and call my own trained model in the test to avoid such errors?Thanks!
This is my errors:
KeyError: 'unexpected key "state_dict" in state_dict'

Try to comment out this segment code.

Thanks a lot! It's helpful  for me.


Barrel Roll can be performed out of board

No "out of board" check

Temporary allowed, with ship destruction.


[PubSub][Question] DEADLINE_EXCEEDED after 60s for sending acks/modacks

We've recently added a new feature which involves a new topic and subscriptions using google-cloud-pubsub version 1.35.0.
However, we noticed warning logs for DEADLINE_EXCEEDED over a number of days all stating a 60 second deadline like the following:
3549577 [Gax-11] WARN c.g.c.p.v.StreamingSubscriberConnection - failed to send operationsio.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after<PHONE_NUMBER>3ns at
io.grpc.Status.asRuntimeException(Status.java:526) at
io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:419) at
io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:41) at
io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:684) at
io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:41) at
io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:391) at
io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:475) at
io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63) at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:557) at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:478) at
io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:590) at
io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) at
io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at
java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
java.lang.Thread.run(Thread.java:748)

We had set a 300 second Ack Deadline on topic creation but investigating the code reveals instead a default of 60 seconds is used since pubsub: re-implement periodic deadline adjustment. However, that deadline should have adjusted and we use the default Max Ack Extension setting so would expect a larger deadline than 60 seconds.
Further investigation led to discovering that the unary calls to send the acks/modacks also has a deadline of 60 seconds and it appears that the stacktrace is produced by the logging StreamObserver used during this step.
Could someone confirm whether these stacktraces actually relate to the the sending of ack/modacks timing-out?

@guess-burger  Found any solution bro :) ?

@goxr3plus, we didn't. We had all sorts of problems with high duplication of messages even though items were handled in a few seconds.
In the end we just stopped using the Async Stream Pull consumer. Even flow control setting of max 1 outstanding still produced issues. We started to synch-pull one item at a time and duplicates stopped and so did these error messages.
Although now we occasionally see deadline exceeded for a negative length of time!

I can confirm these stack traces are related to sending ack/modacks timing out.
Could you let us know how you're setting up the executor? We've seen problem in the past where all threads in executor are busy with messages that they cannot service an RPC. With flow control at 1, this seems unlikely unless you have a single-threaded executor?

We are seeing the same behaviour with v1.37.1. We are creating an executor provider with FixedExecutorProvider.create(Executors.newScheduledThreadPool(4)) and using the default FlowControlSettings.

@maros7 How long running are your tasks? Eg, does each message take 1 second of executor's time? 10 seconds? etc. I might be onto something but would like to understand this better first.

@pongad Our MessageReceiver creates a Spring Integration Message including the AckReplyConsumer as a message header and puts the message on a Spring Integration channel. This takes less than 1 second. Processing is done by the consumer of the Spring Integration Channel.

@pongad, we were using the default executor provided by the Subscription.Builder which looks like 5 * Num available Processors.

@guess-burger Can you please try with latest version? It has better configuration of channel pool and executor provider and see if it helps?

This issue is out of date.  Please retry with the latest version.  If that doesn't help, please open a new issue.


Asserts on functions defined using function statements do not work

Bug Report

🔎 Search Terms
asserts function declaration

⏯ Playground Link

Playground link with relevant code
💻 Code

function fn<T>(val: T) {
    return { val }
}

const fnLambda = function <T>(val: T) { return { val } };

const arrow = <T,>(val: T) => ({ val });

type AnyFunction = (...args: never[]) => unknown;

function enhance<Fn extends AnyFunction>(fn: Fn): asserts fn is Fn & { enhanced: true } {
    Object.assign(fn, { enhanced: true } as const);
}

(function runner1() {
    enhance(fn);
    enhance(fnLambda);
    enhance(arrow);

    console.log(fn.enhanced)
    console.log(fnLambda.enhanced)
    console.log(arrow.enhanced)
}())

🙁 Actual behavior
Assertion does not work for function declaration but it works for function expressions / arrow functions.

🙂 Expected behavior
I expect same behavior in all 3 cases.

Duplicate of #41232. Used search terms: asserts function in:title


Fix: Cannot set property of  which has only a getter

When a method of a Class makes changes in a cloned copy of a getter property wich type is an array, the property is included in the drafts, causing the TypeError: Cannot set property 'propName' of # which has only a getter. For example:
class State {
  [immerable] = true
  word1 = 'bar'
  word2 = 'foo'
  get chars() {
    return this.word1.concat(this.word2).split('')
  }
  setWord(newWord) {
    let mix = [...this.chars].slice(0,3)
    // The next line changes a cloned copy of this.chars
    mix[2] = 'z'
    this.word1 = mix.slice(0, 3).join('')
    this.word2 = newWord
  }
}

const state = new State()

test('should allow getter array', () => {
  expect(state.word1).toEqual('bar')
  expect(state.chars).toEqual(['b', 'a', 'r', 'f', 'o', 'o'])
  const newState = produce(state, d => d.setWord())  //TypeError: Cannot set property chars of #<State> which has only a getter
  expect(newState.word2).toEqual('baz')
})

This PR fixes it, checking with ownKeys if the property exists in the state.base, before creating the proxy. If the property doesn't exist, it returns the value.
https://codesandbox.io/s/great-colden-1py9k

This PR also solves #439

Thanks for the suggested fix! Could you also include a unit test that makes sure we don't regress on this and the code is covered? Thanks!

The tests were included @mweststrate. Thanks.

Hi @mweststrate. The use of getOwnPropertyDescriptor didn't work, because it always returns undefined for getters. I am proposing to use Object.keys() instead.

Ah, that is because they probably live on the prototype, not the instance. I think we should hold this a little, and think this further through or maybe even forbid it. This is a rabbit hole that might go quite deep, see #317 (and #392) for some background.
I am not sure there is an universally applicable solution to this.

@mweststrate, now that v. 5.0.0 is ready, can we think about this issue?
This problem only occurs with setUseProxies(true).  With es5 (without proxies) the getters work nicely. You can check it out at https://codesandbox.io/s/useimmer-tic-tac-ci6qq.
There is no performance or bundle size cost in the fix.
It allows the same behavior, with and without proxies.
@luncheon

Replaced by https://github.com/immerjs/immer/pull/558


added release workflows script

:tada: This PR is included in version 2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement Stream interface?

I am trying to use gulp-rev (https://www.npmjs.org/package/gulp-rev) to revision my assets. I know I could manually do this for my webpack.config stuff but it raises a more important question to me: How can I pipe the output from webpack into an arbitrary stream?
I couldnt find any examples and it doesnt look obvious to me. Any pointers? Can you show an example of piping output from webpack into gulp-rev?

https://github.com/shama/webpack-stream


Restart projects via dashboard

This is just a PoC to test how to enable restarts via the dashboard (for csprojs only).

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

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


gitmodules: Use https:// git URL

Using an HTTPS URL is a bit more accessible as it doesn't require setting up an SSH key.

I'd definitely favor this, since the current setup breaks in every containerized setup, like in github codespaces.

Until this is merged, I'm using this workaround:
# Set HTTPS URL for git submodule 'lib/distro'
git -C dotbot-ifplatform submodule set-url -- lib/distro https://github.com/python-distro/distro.git
# Ignore dirty state in git submodule
git config -f .gitmodules submodule.dotbot-ifplatform.ignore dirty

@ssbanerje - Are you available to review this PR?  Thank you

@ssbanerje any chance you could look at this?

Closing due to no inactivity from repo owner.


Expression Interpreting - operators, literals, and variables

Get expression interpretation working (except for functions):

[x] unary negation
[x] unary positive (ignored)
[x] BNOT
[x] NOT
[x] power
[x] multiplication
[x] division
[x] DIV
[x] MOD
[x] addition
[x] subtraction
[x] BAND
[x] AND
[x] BOR
[x] OR
[x] BXOR
[x] XOR
[x] equality
[x] inequality
[x] greater or equal
[x] less or equal
[x] greater
[x] less
[x] string concatenation
[x] works for Assignment
[x] works embedded in PRINT
[x] operator precedence works
[x] parentheses precedence works

AND/OR short-circuiting has to be deferred because it requires an ANY function return to even try to make it occur in a testable way.

Made the decision to remove "cram concat" -- expressions must be separated by semicolons in PRINT


I would like to contribute

Hello guys,
I have basic experience in Golang, and would like to improve it. Could I help the project with some issue?
Thank you!

Hi @rafamarts ! Sorry for the late response... !
I'm going to create an issue for you and will come back here with it.
That's so nice to also have you here. It will be of great value for the project to have contributors working on both frontend and backend.

Hi there @rafamarts !!
Do you want to take the issue #19 ? If so, please comment in the issue and I'll assign it to you.
Sorry for the late response... 🤒

Great!! Let's do it!! I can get the issue #19.

Great!! Just comment there on the issue, please, so I can assign it to you.
Welcome on board! 😃


ZKP - Predicate referent did not produce any credentials

When I use ZKP in the credential presentation request by the verifier, it results in an error in the presentation in the holder. However, if I do not include ZKP predicates, the submission is sent and verified correctly.
Environment
I have a scenario deployed in docker (with docker-compose) with several agents (frameworks and controllers). AENA (ports 8035-8036) is the holder and FNMT (ports 8045-8046) acts as issuer and verifier simultaneously.
Regarding the frameworks, I am using the public image: bcgovimages/aries-cloudagent, version py36-1.16-1-1_0.7.2.
I am using AIP 1.0.
I am not using revocation (the credential is issued without revocation).
I am using a locally deployed VON network.
Let's start from a point where:

The credential schema and the credential definition have already been published in the local VON network.
The connection between AENA and FNMT is already established.
FNMT has already issued the credential to AENA, and AENA has it stored in the wallet. The credential is as follows:

Request
The request I am using is: /present-proof/send-request.
The request's body is the following one:

Note: The response does not contain any errors.
Logs
There are no errors printed in the terminal.
No webhook is sent.
The only error that is shown is the one specified in the "log" file (the file I specified to store logs) of the AENA agent, and it is the following:
<IP_ADDRESS> [09/May/2022:14:04:19 +0000] "POST / HTTP/1.1" 200 155 "-" "Python/3.6 aiohttp/3.7.4.post0"
Received presentation request message: {"@type":"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation","@id":"40158805-4724-400a-875a-fcb16b28d5b3","request_presentations~attach":[{"@id":"libindy-request-presentation-0","mime-type":"application/json","data":{"base64":"eyJuYW1lIjogIlByb29mIHJlcXVlc3QiLCAibm9uY2UiOiAiMSIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiMF9mdWxsX25hbWVfdXVpZCI6IHsibmFtZSI6ICJmdWxsX25hbWUiLCAicmVzdHJpY3Rpb25zIjogW3siY3JlZF9kZWZfaWQiOiAiNXpTakFVVkx1dFptQVRhOTdjNWNOSzozOkNMOjEwOmNvdklEX1BvQ19JZGVudGl0eSJ9XX0sICIwX3Bob3RvX3VybF91dWlkIjogeyJuYW1lIjogInBob3RvX3VybCIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICI1elNqQVVWTHV0Wm1BVGE5N2M1Y05LOjM6Q0w6MTA6Y292SURfUG9DX0lkZW50aXR5In1dfSwgIjBfZG5pX251bWJlcl91dWlkIjogeyJuYW1lIjogImRuaV9udW1iZXIiLCAicmVzdHJpY3Rpb25zIjogW3siY3JlZF9kZWZfaWQiOiAiNXpTakFVVkx1dFptQVRhOTdjNWNOSzozOkNMOjEwOmNvdklEX1BvQ19JZGVudGl0eSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7IjBfYmlydGhkYXlfZXBvY2hfR0VfdXVpZCI6IHsibmFtZSI6ICJiaXJ0aGRheV9lcG9jaCIsICJwX3R5cGUiOiAiPj0iLCAicF92YWx1ZSI6IDEwODMxOTY4MDAsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICI1elNqQVVWTHV0Wm1BVGE5N2M1Y05LOjM6Q0w6MTA6Y292SURfUG9DX0lkZW50aXR5In1dfX0sICJ2ZXJzaW9uIjogIjEuMCJ9"}}],"comment":"Identity proof presentation to the FNMT entity"}
	src/services/anoncreds/prover.rs:445 | name: Some("photo_url"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("full_name"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("dni_number"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("birthday_epoch"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("dni_number"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("full_name"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("photo_url"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("birthday_epoch"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("full_name"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("photo_url"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("dni_number"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("birthday_epoch"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("full_name"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("photo_url"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("dni_number"), names: None
	src/services/anoncreds/prover.rs:445 | name: Some("birthday_epoch"), names: None
Could not automatically construct presentation for presentation request Proof request:1.0 because predicate referent 0_birthday_epoch_GE_uuid did not produce any credentials.

And the log of this request by the FNMT agent does not show any error, only the following:
<IP_ADDRESS> [09/May/2022:14:04:19 +0000] "POST /present-proof/send-request HTTP/1.1" 200 2678 "http://localhost:8046/api/doc" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36"

Framework configuration
FNMT framework configuration (the configuration of the holder's framework is similar, but with ACAPY_WALLET_LOCAL_DID set to true):
AGENT_PORT: "8045"
ADMIN_PORT: "8046"
ACAPY_ENDPOINT: "http://313f-90-167-203-98.ngrok.io"
ACAPY_GENESIS_URL: "http://<IP_ADDRESS>:9000/genesis"
ACAPY_WALLET_SEED: ....
ACAPY_WALLET_TYPE: "indy
ACAPY_WALLET_NAME: ...
ACAPY_WALLET_KEY: ...
ACAPY_AUTO_PROVISION: "true"
ACAPY_LOG_FILE: "/logs/acapy-FNMT-20220509T154406.log"
ACAPY_LOG_LEVEL: info
ACAPY_DEBUG_CONNECTIONS: "true"
ACAPY_DEBUG_CREDENTIALS: "true"
ACAPY_DEBUG_PRESENTATIONS: "true"
ACAPY_AUTO_ACCEPT_INVITES: "true"
ACAPY_AUTO_PING_CONNECTION: "true"
ACAPY_AUTO_RESPOND_MESSAGES: "true"
ACAPY_AUTO_STORE_CREDENTIAL: "true"
ACAPY_AUTO_RESPOND_CREDENTIAL_REQUEST: "true"
ACAPY_AUTO_VERIFY_PRESENTATION: "true"
ACAPY_AUTO_RESPOND_PRESENTATION_REQUEST: "true"
ACAPY_WEBHOOK_URL: "http://controllerFNMT:5000/webhooks"

AND
aca-py start -it http '<IP_ADDRESS>' '8045' -ot http --admin '<IP_ADDRESS>' '8046'"

Oh I see, I knew the error I had was going to be a silly mistake...
However, a question arises for me... if the predicate condition is not met, doesn't the verifier have a way to be notified about it? Because in my case, the verifier wasn't getting any response.

If the holder doesn't have any credentials they can present (which is the case here, since there are no credentials that satisfy the predicate restriction) all the holder can do is send a problem report (which basically cancels the request)
I'n not sure any of the mobile wallets implement this right now, but since you're using a bunch of aca-py agents you can call the /present-proof/problem-report endpoint (I think that's it) on the holder agent


Fix build error on Node 10

Update nan to fix build error on Node 10.
And add Node 10 for travis test.
Fix https://github.com/yanyiwu/nodejieba/issues/112

Thank you!


[V1.1]Updated about us

Coverage remained the same at 92.413% when pulling 2cce9f91a151dd11281a5398b9779733ae7ee267 on ALim95:V1.1_UpdateAboutUs into 3c64e359c1b3e9429413ced00ae253b2e0c22765 on CS2103AUG2017-T15-B4:master.


Switching to path location strategy

I'm submitting a question about the decisions made in the repository.
Currently the starter is using hash location strategy for the routing by default. Why not switch to path location strategy?
I believe most users want to be html5 compliant out of the box. Browser support for Angular 2 includes only IE9+ with more recent versions of Chrome, Firefox and Opera, so it's not an issue.

hash location strategy is easier to understand how a SPA works. Even if the goal is having html5 support

I was thinking the goal of this repository was to get people up to speed with an Angular 2 project instead of teaching them about how SPA works.
But if the intention is more towards the second I will happily close.

Does the Path Location Strategy fall back automatically to Hash Location Strategy? :)
For example on IE9

@samvloeberghs nope :)
Normally path location strategy should work on IE9 of you use a polyfill like history.js
Sadly I have not experimented with it much, but if support for hash location strategy is more IE9 friendly then it's a reason to keep it.

@samvloeberghs the bootstrap code could probably use Modernizr to detect if the history API is there or not and adapt the config based on that. IMHO IE9 shouldn't be considered anymore anyways, time to move on. Microsoft dropped support, let's not live in the past. Ask people to move to a modern Web browser :)

@spawnius @dsebastien totally up for that! But why do we still have Hash Location Strategy than.. Can't think of a case other than IE9

@samvloeberghs - while IE9 without push state support might be one of the reasons, the major one I see is when you don't want to delegate handling of deep links to the front end. Example: ngnix web server is handling / while the SPA is handling /# based routes.

I was going to open an issue relating to path location strategy, but it might be more appropriate here. Maybe @spawnius can help me out. I'm using path location strategy. On my server, nginx is handling incoming requests and sending them off to either the front-end server or the backend (api) server.  If I visit / and navigate to /about, all will be fine, but on a refresh I'll get a 404 in the server logs. With the block, however, refreshes work as expected. Also, I don't understand how dynamic uri's (e.g. /users/3) can work out between nginx and path location strategy.
Any ideas?

@louisscruz this is a question for stackoverflow as it is an implementation specific matter.

FYI I've added support for push-state in the production build of my fork (dev mode being ok with the historyApiFallback option

@spawnius I totally understand. It's just that I've already made 4 or 5 posts on SO and Serverfault about this issue over the past few months. No luck. I personally think that it would be great if someone did a wiki on this, if anyone actually understands how this implementation should work.
@dsebastien I'm going to check out your setup/superstatic later. Thanks!

I spent days wondering why back clicks weren't working.  I thought i was supposed to add the following to the app.routes.ts file like the official docs state:
export const appRouterProviders = [      provideRouter(routes)    ];
I then imported this into the bootstrap and everything appeared to work as push state except back clicks.  Took me forever before I realized that location strategy is being forced and I'm not supposed to use provideRouter I guess, even though I have no clue what it actually does.

Thanks @dsebastien for you suggestion, it's exactly what i am looking for!!!


add function to link switch to router

@vtolstov @hzhou8 could you help review? thanks!

Maybe you can add some test for your change.

closing this pr, will submit another one to link switch to router in a transaction


[FEATURE] Date Filters

Filter by dates, use the virtual date filters

https://blog.devgenius.io/a-query-in-time-introduction-to-sql-server-temporal-tables-145ddb1355d9
select *
from Person
for system_time as of '2021-02-05 18:25:00'
order by PersonId

as of
between  and
all

except SqlOxide doesn't support FOR statements like this.


random QR code

(this is an example of what pull request feedback would be like).
Thanks for the QR code, could you add some information to the README about where it points.


Flow not understanding React propTypes for ES6 classes

Background: I'm converting a smallish package to Flow, in order to sell it to the team as a general part of our codebase.
Running 0.24.2, using the following example:
// @flow

import React, {Component, PropTypes} from 'react';

export class TestComponent extends Component {

    // props: {
    //     message: string
    // };

    someMethod() {
        console.log(this.props.badField);
    }

    render() {
        return <div>{this.props.message}</div>;
    }

}

TestComponent.propTypes = {
    message: PropTypes.string
};

Flow tells me this code has no problems. If I uncomment the duplicate props type definition, it correctly flags badField as non-existent. Using a static propTypes = {...} does not solve the problem.
I understand that duplicating the propTypes as a Flow type will fix the problem in this limited example, but I'll never get the rest of my team on-board with Flow if they have to write out all their propTypes twice. We would also not get any error messages as the duplicate definitions diverged over time, which kind of defeats the purpose of the exercise.

I've been thinking on this. Perhaps TestComponent.propTypes could be generated from the Flow props type via Babel?

I am just a user like you, but I don't use PropType but flow type as here
http://flowtype.org/docs/react.html#_
props: {
    title: string,
    visited: boolean,
    onClick: () => void,
  };

or
type Props<Config> = {
  class: ReactClass<Config>,
  config: Promise<Config>,
};

then
class Button extends React.Component {
  props: Props
...
}

you will see lot of examples in the test files
I read comments from react core team that React.PropType is limited in scope and wante to get rid of in favor of flow. t may not happen still, I don't know whether you should use React.PropType if using @flow

While you can get away with not including FooComponent.propTypes, it's not ideal and you will miss out on runtime warnings in development mode, which would still be useful if a project is being migrated to using Flow a-chunk-at-a-time. But doing this would not be an option at all for some things, like FooComponent.contextTypes or FooComponent.childContextTypes as they're needed at runtime.

may or may not relate to #1908

@sophistifunk check out https://github.com/codemix/babel-plugin-typecheck for getting warnings in dev mode.
+1 for the contextTypes and childContextTypes. It feels borderline illegal to mix react.PropTypes for contextTypes and use flowtype declarations for component.PropTypes.

This is a missing feature, not a bug. It's in the documentation. Having said that, it seems strange that Flow would provide this capability to React.createClass components but not extends React.Component components. One of the great things about Flow is that you can get a lot of mileage out of it without resorting to type annotations. Unfortunately, that doesn't cover component classes. So this issue is gets +1 from me.

@steve-taylor context does not appear to be mentioned in the docs you linked to. Is there anywhere else this behavior is documented?

Nowadays Flow enforces you to type properties so there is no way around it. I don't think Flow will ever support inferring types from proptypes.
There are some libraries to help with this:

Flow libdefs for proptypes: https://github.com/flow-typed/flow-typed/blob/master/definitions/npm/prop-types_v15.x.x/flow_v0.41.x-/prop-types_v15.x.x.js
Codemod to convert proptypes to flow types: https://github.com/billyvg/codemod-proptypes-to-flow
Flow runtime type checker: https://github.com/codemix/flow-runtime


Route base permissions with OML/CML

Follow up from #230 : The routes in management-navigation.component.ts should be protected with an OML

I think, this is done by #294.


Create an SAP Cloud Platform destination pointing to an SAP Gateway

I think the ES5 destination also requires the custom property
sap-client = 002

We have found that the ES5 destination doesn't require the client number, so we didn't put it in the tutorial.
Cheers,
Jonathan


[OUI Docs] Removed the chart section that's using elastic charts

Description
Removed the chart plugin section that's using elastic charts.

Issues Resolved
#337
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[x] All tests pass

[x] yarn lint
[x] yarn test-unit

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

fixes #337


[bug] dotenv not work in production

Describe the bug
I'm using dotenv crate to save some important informations like access keys and secrets by saving them in the src-tauri/.env file. It works perfectly in dev but fail to load in release mode.
dotenv
//.env
KEY=ABC
SECRET=DEF

// main.rs
fn main() {
    dotenv::dotenv().ok();
    let key_id = dotenv::var("KEY").unwrap_or_default(); // empty in release mode
    let secret = dotenv::var("SECRET").unwrap_or_default();  // empty in release mode
    // ...
}

Reproduction
No response
Expected behavior
No response
Platform and versions
Operating System - Mac OS, version 12.2.1 X64

Node.js environment
  Node.js - 16.14.0
  @tauri-apps/cli - 1.0.0-rc.5 (outdated, latest: 1.0.0-rc.8)
  @tauri-apps/api - 1.0.0-rc.1 (outdated, latest: 1.0.0-rc.3)

Global packages
  npm - 8.3.1
  pnpm - 6.24.3
  yarn - Not installed

Rust environment
  rustup - 1.24.3
  rustc - 1.59.0
  cargo - 1.59.0
  toolchain - stable-x86_64-apple-darwin

App directory structure
/test
/dist
/node_modules
/public
/src-tauri
/.git
/.vscode
/src

App
  tauri - 1.0.0-rc.3
  tauri-build - 1.0.0-rc.3
  tao - 0.6.2
  wry - 0.13.2
  build-type - bundle
  CSP - default-src 'self'; img-src 'self' asset: https://asset.localhost; media-src 'self' asset: https://asset.localhost; connect-src *
  distDir - ../dist
  devPath - http://localhost:8080/
  framework - Vue.js (Quasar)
  bundler - Webpack

Stack trace
No response
Additional context
No response

This will not work in release mode because the released binaries does not have the folder structure you have during development (specifically there is no src-tauri folder in release mode). The dotenv crate reads the file dynamically at runtime. So it's reasonable that this does not work in production, as there is not dotenv file.
As for workarounds, you can try to include the dotenv file into the final bundle using Resources: https://tauri.studio/docs/api/config#tauri.bundle.resources but that might not work because resources are not necessarily placed in the same folder as the binary.
In general its worth noting that the dotenv crate really is meant for servers written in rust, where you deploy into a known and controllable environment and need a way to declaratively set env variables. In the context of desktop apps, anything that requires additional files at runtime to work correctly is a bit suboptimal.

Thanks for reply. Ok, let's forget about dotenv.
So, where should I save config that can be read at runtime in rust while at the same time protect these file from being access by user?

That depends, what do you need that config file for anyway? Can you just replace a config file with compile time constants? That would be the safest option.


Split Panels cannot be resized

With one of the last updates, I am no longer able to resize split panels:

I tried restarting/reinstalling the app, which didn't help.
I'm running Terminus 1.0.92 on Windows 10 version 1803.

also having the same on 1.0.98 on Windows 10 version 19041


Added proper command support

The bot now parses commands correctly, so that it can discard commands explicitly directed at other bots (i.e. /chobot@anotherbot) and support /chobot@ritalobot seed.

Derp, I accidentally pushed a new commit in the meanwhile. How do I apply the pull request only up to 41a1e56?

You could create a different branch for this feature only and propose the
merge of that feature branch.
Good job on the code BTW.
On Mon, Mar 21, 2016, 23:53 Capacitor Set<EMAIL_ADDRESS>wrote:

Derp, I accidentally pushed a new commit in the meanwhile. How do I apply
the pull request only up to 41a1e56
https://github.com/blackdev1l/ritalobot/commit/41a1e568edf998a0ba885338735465ca83d55433
?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/blackdev1l/ritalobot/pull/6#issuecomment-199523757

Revert or reset the HEAD to that commit (git commit --reset HEAD^)
Il 21 marzo 2016 23:53:00 CET, Capacitor Set<EMAIL_ADDRESS>ha scritto:

Derp, I accidentally pushed a new commit in the meanwhile. How do I
apply the pull request only up to 41a1e56?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/blackdev1l/ritalobot/pull/6#issuecomment-199523757

--
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.

Code looks good, although it lacks of command line arguments  for the new variable name and the example in README.md too.

Actually there is no need to pass the bot username as a paramenter. There is a useful API method getMe which returns info (like the username) about the bot associated with the api key


kubescape: 2.0.146 -> 2.0.147

Motivation for this change
https://github.com/armosec/kubescape/releases/tag/v2.0.147
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 159054 run on x86_64-linux 1

1 package built:

kubescape


Make: Upgrade GCC version

:tada: This PR is included in version 2.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use defined endpoint data sources from tasks

Question
Is there a way to use the defined endpoint data sources in the extension manifest from task's TypeScript code? does the task library support this?
My case is that I need to call the rest service defined in the endpoint from the task. What I've seen so far is that the data sources are mainly used to populate pick lists in the task definition screens.
Since the endpoints of the rest service can be defined in the extension manifest and I can access some of that info from the task (URL, authentication). I was wondering if there is a way to call the external rest service with a simple call in the task lib (I haven't seen anything in the task lib docs). I would be a nice feature if it is not possible now.
Can you confirm if the alternative now is, for example, to build the call to the external rest service in the task and use the node.js request to make the call?
Thanks,
J.

@jsalado Task lib currently doesn't have any such functionality though i agree it will be good to have. Currently the two options are to use Execute Service Endpoint Request rest API or to call the external rest API directly in task as you mentioned.

@omeshp Thank you for your answer. I'll try to do everything in the task code then as you suggest.
Do you think the task lib will support using the endpoint datasource definitions any time soon. How can I open a feature request fo it?
Best,
J.

@omeshp Thanks for your answer.
I'll implement the call in the task code as you say.
Is the enhancement going to be developed any time soon? How can I open a feature request for it?
Best,
J.

@GitHubSriramB Can you add this request to backlog, if not already present?

ANy news on this?


Offset drops to side clicked to avoid collision weirdness

When drops are spawned inside the block space of the frame block, they can glitch out and throw themselves everywhere. Offsetting them like this avoids that.

Alternatively, it could try to place the drop in the player's inventory directly - and failing that, drop it at their feet.


Wrong output path on Linux.

Hi there,
I tried to find a solution on the internet but haven't succeeded so far.
I've got folders structure like this:

root

MyApp.Android
MyApp.JS

In 'MyApp.JS' folder I've got a gulp task which generates java files and put them inside 'MyApp.Android' folder.
It works fine on Windows and OS X.
But on Linux it generates a lowercase folder like 'myapp.android' which is treated like a separate one. The interesting thing is that file names case is correct, the issue is in parent (target) folder only.
My current system:
- Linux Fedora 22
- Node v4.2.1
- Gulp v3.9.0
- Npm v3.3.9

Sorry, my fault.
Inside gulp task was running grunt task (legacy one).
So, probably it's a grunt's issue.


e2e: fix provisioning for Ubuntu cloud image.

Ubuntu cloud image does not need a DNS fixup.

I'm ok with it, but probably some day we would need to fix those sed with internal ansible line replacement, it would be faster in overall script runtime.

+1


Support react-native 0.63

Hi
First of: Thanks for an awesome library!
Does this library support react-native 0.63? If so, could you please update the react-native peer dependecy in package.json to ">=0.57 =<0.63"? :)
Best regards
Jens

Check this https://www.youtube.com/watch?v=Bx_gwRODtlY

this package supports all modern RN versions
fix: https://github.com/callstack/react-native-image-editor/pull/125


Added pkcs7 signed data support

Fixes #310
Fixes #232
Added ability to parse pkcs7 signed content. Same features as in the Java version.

I wonder if this also resolves issue #63

This should be pulled in with commit  2a508f3f , which will be synced eventually. Thank you!


Exposing namespace with override in helm-chart will help in sub-charts scenarios

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Instead of current

Exposing it like this with override values.yaml will enable more use cases like sub-charts.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Secrets Store CSI Driver version: (use the image tag):
Azure Key Vault provider version: (use the image tag):
Kubernetes version: (use kubectl version):
Cluster type: (e.g. AKS, aks-engine, etc):

This is no direct support in helm for this unless a chart provides override capability via values.yaml
https://github.com/helm/helm/issues/5358#issuecomment-628920908

@BlackRider97 Thank you for opening the issue!
Could you provide more information on why the subcharts would want to be deployed in different namespace than the parent chart? For this particular project, wouldn't the intent be to deploy the provider and the driver in the same namespace ?

Have a same requirement. Any update on this ask?

Have a same requirement. Any update on this ask?

@bhanuprakash-1 As @aramase mentioned above, could you elaborate why would you want driver and provider in different namespaces? It would be helpful to know more about your use case.

We have divided our application into different charts like cluster-setup chart and a application chart. In cluster-setup chart, we have multiple sub-charts as dependencies and one of it is csi-secrets-store-provider-azure. And according to security requirement, we have to install this specific sub-chart in kube-system namespace. But other charts to be in a default namespace.
Im not asking for driver and provider to be in a different namespace, just want to be able to configure namespace using values.yaml for this chart(for provider and in-turn for driver). Excuse me if Im not clear, new to Helm!

@bhanuprakash-1 Thanks for explaining. This makes sense.
Are you willing to open a PR to make this change? We update our charts in manifest_staging. You would need to update both driver and provider helm charts. Let us know if you need any help.


Teams search is calling 'business.bing.com'.

Japanese customer told us Teams search box is calling 'business.bing.com'.
Can anyone verify and add it in the list?

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

ID: 66bd8666-3566-a901-b25b-eb6baba6264a
Version Independent ID: e9f6310f-2207-8c81-d31a-3d5a80beb26b
Content: Office 365 URLs and IP address ranges - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@kelleyvice-msft Please help us in resolving this issue. Thanks


Rerun prettier

Change-type: patch

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci I self-certify!

I self-certify!


Make the change - @id present but optional

This addresses #434

@lrosenthol - can you please add to the description of this PR the issue we are solving. There are so many discussions on this topic I think it would be helpful to have it clearly articulated here.

The reason we are doing this is because it can't be done after the fact.
@id is defined in the JSON-LD spec as the way in which you refer to an node externally - basically giving that instance of that schema a unique ID.  While it may be that in Adobe's current use of a given schema, they don't ever need to refer to a specific instance - we do not know how other users of these schemas will use them.
And since you can't add @id to an instance of a schema that doesn't have it defined in the schema itself (if you assume that somewhere in the flow there may be validation) - we must define it in all schemas.
However, just because it is defined in each, doesn't mean it has to be there - which is why it may be optional.

@lrosenthol - Thank you for the reasoning. One clarification, we use the term "schema" here, but we really mean every instance of an object and maybe array too.
e.g looking at the assets/asset.schema.json we would want to add @id in both these cases which are not schema "files"
        "xdm:milestone": {
          "title": "Milestone",
          "description": "A label given to a version of the asset.",
          "type": "object",
          "properties": {
<--- Add @id here? -->
            "label": {
              "title": "Milestone Label",
              "type": "string",
              "description": "Label for the version of an asset"
            },
            "description": {
              "title": "Milestone Description",
              "type": "string",
              "description": "Description for the version of an asset"
            }
          }

And
        "xdm:aliasIDs": {
          "type": "array",
          "meta:usereditable": false,
          "title": "Alias IDs",
          "items": {
            "properties": {
<--- Add @id here? -->
              "system": {
                "title": "External System",
                "type": "string",
                "description":
                  "A string used to identify the external systems like google, facebook etc."
              },
              "id": {
                "type": "string",
                "title": "External ID",
                "description":
                  "An ID under which external systems track the asset."
              }
            }
          },

Thoughts?

Actually, when I am using it, I mean the schema definition as contained in a .schema.json file.  Perhaps that is what is confusing you?
So in your examples, you wouldn't add @id into either.  You would have it at the top of an instance of a schema.

That seems a bit arbitrary considering we do not necessarily break down schemas into sub/abstract schemas consistently across committing teams. On the XC side we tend to prefer reusability of schemas, and thus have normally got only one properties definition per schema.
I certainly read the intent of @id to mean node, not schema file. So any collection of properties that represent something, an aliasID, or a milestone may need a predictable address if we follow the thinking of the proposal.
I suppose I'm saying the proposal is still a but unclear in my mind because you are saying an "@id needs to be added if we somehow deemed it right to break out an object in a dedicated schema file." Which in itself is fairly stylistic decision, not a canonical one.... or else I'm showing my ignorance in this area....

I agree with you @cdegroot-adobe that you can use a schema either by itself or as a child of some other schema.  However, you seem to be considering properties as instances of schemas, but they are not.
On the other hand, consider something like a directory listing that has a list of assets such as:
"xdm:dirListing" : [ { xdm:asset { "@id" : "12345", .... }, { xdm:asset { "@id": "67890", .... } ]
Since xdm:asset is an actual schema, each instance of it can then have an @id associated with - even though it is inside/child of the xdm:dirListing

I want to point out that how we organize schema definitions into files is a canonical decision, in that references to those definitions from other schemas reference that filename. I worry this may be a looming issue for us, at least where we currently have done a poor job of grouping definitions into files.