buy kit wopr

Good evening,
do you have any wopr kits for sale at the moment.
Sincerely.

I should have more in stock in a week or 2.

Good morning,
ok, keep me informed, what are the options to take so that the kit is complete.
Sincerely.
----- Mail original -----
De: "Unexpected Maker" @.>
À: "UnexpectedMaker/wopr" @.>
Cc: "alalal80" @.>, "Author" @.>
Envoyé: Jeudi 20 Juin 2024 01:16:11
Objet: Re: [UnexpectedMaker/wopr] buy kit wopr (Issue #9)
I should have more in stock in a week or 2.
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you authored the thread. Message ID: <UnexpectedMaker/wopr/issues/9/2179556153 @ github . com>

It’s only available as a kit.
If you want to be notified when I have more in stock, please sign up to the “back in stock” notification on my website:
https://unexpectedmaker.com/shop.html#!/W-O-P-R-Display-Kit/p/578899083/category=154491532

Ok, but what type of dev board should we take tinypico, or tinys2 or s3?
Sincerely.
----- Mail original -----
De: "Unexpected Maker" @.>
À: "UnexpectedMaker/wopr" @.>
Cc: "alalal80" @.>, "Author" @.>
Envoyé: Jeudi 20 Juin 2024 07:56:42
Objet: Re: [UnexpectedMaker/wopr] buy kit wopr (Issue #9)
It’s only available as a kit.
If you want to be notified when I have more in stock, please sign up to the “back in stock” notification on my website:
https://unexpectedmaker.com/shop.html#!/W-O-P-R-Display-Kit/p/578899083/category=154491532
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you authored the thread. Message ID: <UnexpectedMaker/wopr/issues/9/2179875659 @ github . com>

Is there a new version of the firmware or other developments to come?
----- Mail original -----
De: "Unexpected Maker" @.>
À: "UnexpectedMaker/wopr" @.>
Cc: "alalal80" @.>, "Author" @.>
Envoyé: Jeudi 20 Juin 2024 07:56:42
Objet: Re: [UnexpectedMaker/wopr] buy kit wopr (Issue #9)
It’s only available as a kit.
If you want to be notified when I have more in stock, please sign up to the “back in stock” notification on my website:
https://unexpectedmaker.com/shop.html#!/W-O-P-R-Display-Kit/p/578899083/category=154491532
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you authored the thread. Message ID: <UnexpectedMaker/wopr/issues/9/2179875659 @ github . com>


Change data capture support

Hello
I was wondering if there are any plans for adding change data capture support? I'm looking for something that listens to changes made to a graph collection so that I can consume these events and do something with them.
I came across this project but it is dead: https://github.com/baslr/arangochair.

Hi @michielhub,
Unfortunately the short answer would be no. Exposing the replication API (which arangochair seems to use under the hood)  is in the roadmap but building the actual poller is out of the scope of this client.

But it shouldn't be too hard to build yourself. All it seems to do is query the two endpoints (which you will be able to do using python-arango in its next release) in a while loop.

Hi @michielhub,
Replication API is now available in the latest version of python-arango. Building a checker on top of these should not too much work.


Dev

This change is

Coverage increased (+1.4%) to 74.697% when pulling<PHONE_NUMBER>503d86b4e90684c93f09a57a0389ea on dev into 21ccade54a0ede416b357263d39f6b1bbec47982 on master.

Codecov Report

Merging #787 into master will increase coverage by 1.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #787      +/-   ##
==========================================
+ Coverage   79.02%   80.06%   +1.04%
==========================================
  Files          25       25
  Lines        7188     7323     +135
==========================================
+ Hits         5680     5863     +183
+ Misses       1508     1460      -48

Impacted Files
Coverage Δ

...rojects/php/x86/php-7.1.16-src/ext/sqlsrv/util.cpp

...php/x86/php-7.1.16-src/ext/pdo_sqlsrv/pdo_util.cpp

...x86/php-7.1.16-src/ext/pdo_sqlsrv/php_pdo_sqlsrv.h

...x86/php-7.1.16-src/ext/sqlsrv/shared/core_conn.cpp

...php-7.1.16-src/ext/pdo_sqlsrv/shared/core_conn.cpp

...cts/php/x86/php-7.1.16-src/ext/sqlsrv/php_sqlsrv.h

...php-7.1.16-src/ext/pdo_sqlsrv/shared/core_init.cpp

...php-7.1.16-src/ext/pdo_sqlsrv/shared/core_util.cpp

...-7.1.16-src/ext/pdo_sqlsrv/shared/core_results.cpp

...rojects/php/x86/php-7.1.16-src/ext/sqlsrv/conn.cpp

... and 40 more

Continue to review full report at Codecov.

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


How to get modcharts and tricky expurgation notes?

yeah.. the title says it all

Modcharts don't work on BR due to complications with the lua library not working. Expurgation, Hellclown, and all other charts that use Tricky's style of hurt notes should work by default, however no other notetypes are implemented

Closing due to inactivity


Supporting Bool while saving

While saving a resource with Bool value, it returns error(data type mismatch, my server expects bool value)from server.

let newObject = Person.init()
newObject.is_american = true
newObject.name = "King"
spine.save(newObject)

the debug follows

{"data":{"type":"persons","attributes":{"name":"King","is_american =":"1"}}}

my server throws error due to this.
thanks in advance

Do you use an NSNumber variable and a BooleanAttribute?


Add encoder calibration documentation

@anirudhupadhyaya requests that I review this PR in terms of direction of content

@anirudhupadhyaya this is on the right track and seems to be written to the right audience, i.e., a user of the AMDC who is trying to interface an encoder to their control system.
There are a few typos and awkward sentences which should be resolved.
However, my main feedback would be to add a "master" block diagram which shows all the possible steps in processing the encoder integer feedback value into something useful for the control system. Then, replace your C code blocks with a single block of C code which implements the block diagram for "all cases" i.e., CW or CCW, etc.
I am not sure about your while() loop for performing the mod(x, 2*pi) operation. Probably better to just use mod() here unless you have a good reason not to use it.
Also, add a section about validating the encoder offset via the d-axis voltage during operation.
I am also curious to see your section on converting position to speed.

I am yet to update the block diagram, but I have addressed rest of the comments.

Block diagram updated.

@elsevers I have addressed your review comments.

Oh.. I guess it went away when I accepted the suggestions?

@elsevers I added a line on the bandwidth recommendation for low pass filter.

Simulink PLL Block for Encoder Feedback Filtering

Zip file of the .slx file for Simulink:
pll_encoder.zip

@elsevers to my understanding, we should not have -1 in the second equation, i.e.,

if CCW = 1,
$\theta_\text{CCW} =2\pi \frac{\text{position} - \text{offset}}{\text{ENCODER COUNT PER REV}}$
else if CCW = 0
$\theta_\text{CW} =2\pi \frac{\text{ENCODER COUNT PER REV} - \text{position} + \text{offset}}{\text{ENCODER COUNT PER REV}} = 2\pi \frac{\text{ENCODER COUNT PER REV}}{\text{ENCODER COUNT PER REV}}-2\pi \frac{\text{position}-\text{offset}}{\text{ENCODER COUNT PER REV}}=2\pi-\theta_\text{CCW}$

Your proposed changes works too.
I noticed that this exists from ARL codebase to operate the BP4:
https://github.com/Severson-Group/ARL-eturbo/blob/c1cfcf5c685953966a533b32e2c0184f8654331f/Embedded/My-C-Code/usr/bm_4dof/task_bm_4dof.c#L187

Thanks @noguchi-takahiro. Further confirmation from @anirudhupadhyaya:

@elsevers I have temporarily added these pll_test.m and pll_encoder.slx to this branch. To simplify the process to create FRF, I made minor adjustments for me to the blocks for continuous-time domain. If you run pll_test.m, the following plot is generated:

The blue circles in the plot represents the FRF of $\theta_{\text{out}}/\theta_{\text{in}}$ by injecting the chirp signal to $\theta_{\text{in}}$ of the PLL. From my understanding, this PLL is consist of PI and an integrator. The closed-loop (CL) transfer function is as follows:
$$
\frac{\theta_{\text{out}}}{\theta_{\text{in}}} = \frac{K_p s + K_i}{s^2 + K_p s + K_i}
$$
The red line in the plot (PLL) represents this function, which seems to behave like a filter.
Based on this block pll_encoder.slx, PI gains are determined by $K_p = -2\pi \text{Pole1}- 2\pi \text{Pole2}=-\omega_1-\omega_2$ and $K_i = 2\pi \text{Pole1} \times 2\pi \text{Pole2}=\omega_1\omega_2$, where Pole1 = -10 Hz and Pole2 = -100 Hz. Therefore,
$$
\frac{\theta_{\text{out}}}{\theta_{\text{in}}} = \frac{K_p s + K_i}{s^2 + K_p s + K_i} = \frac{(-\omega_1-\omega_2) s + \omega_1\omega_2}{s^2 + (-\omega_1-\omega_2) s +  \omega_1\omega_2} = \frac{(-\omega_1-\omega_2) s + \omega_1\omega_2}{(s-\omega_1)(s-\omega_2)}
$$
This indicates for sure these Pole1 and Pole2 are poles of CL. But I am still thinking about the relationship between the desired pole locations and the roll off frequency of the filter. I am not sure if this is correct approaches but assuming the natural frequency and damping of this CL:
$$
\omega_n = \sqrt{K_i} = \sqrt{\omega_1 \omega_2} = 198 (\text{rad/s}) = 31 (\text{Hz})
$$
$$
\zeta = \frac{K_p}{2\sqrt{K_i}} = \frac{-\omega_1-\omega_2}{2\sqrt{\omega_1\omega_2}} = 1.74
$$
probably the poles are actually determined based on these parameters?


Example Okta config? Getting 404

It might be helpful to see an example Okta configuration. I'm setting up an app on my dev instance and got the client id and secret and terraformed with those. However, when I try to access my CloudFront url, it's redirecting to Okta, but I'm getting a 404 from Okta.
i.e. it redirects to a url like this:
https://dev-XXXXXX-admin.okta.com/error/404?fromURI=%2Foauth2%2Fv1%2Fauthorize%3Fclient_id%3DXXXXXXXX%26nonce%3DXXXXXXXXXXXX%26redirect_uri%3Dhttps%3A%2F%2FXXXXXXXX.cloudfront.net%2Flogin%26response_type%3Dcode%26response_mode%3Dquery%26scope%3Dopenid%26state%3Dnone

I needed dev-XXXXXX.okta.com instead of dev-XXXXXX-admin.okta.com 🤦


Generate kubelet specific kubeconfig and enable node authorization

Signed-off-by: Suraj Deshmukh<EMAIL_ADDRESS>

How can we articulate this with adding/removing nodes to an already created cluster? Specially with autoscaling. Is there any easy way? thinking

Sorry I don't understand what you mean here? This PR is just solving the issue where the nodes were not named differently and now this PR tries to achieve that.

@surajssd I mean, if are using different certificates and names for kubelets (IIUC, from a quick view of the PR), then how can we generate these certificates when we add nodes after bootkube run? For example, when we manually add nodes in terraform or when autoscaler needs to add nodes. How will those certificates for the kubelet be generated?

@surajssd I mean, if we are using different certificates and names for kubelets (IIUC, from a quick view of the PR), then how can we generate these certificates when we add nodes after bootkube run?

For example, when we manually add nodes in terraform or when autoscaler needs to add nodes. How will those certificates for the kubelet be generated? Doesn't seem trivial, or am I missing something?

@surajssd I didn't review the PR, but in general, I believe the approach should be following for that:

generate bootstrap kubeconfig for controller node
Enable TLS bootstrapping
all remaining kubelets should get it's certificates with bootstrap method

I don't think we should generate multiple certificates with Terraform, so I would not merge this PR.

@surajssd I'm trying to follow up with review, but don't have enough context. Please can you update the description?

@kosyfrances note that the commit messages have a more expanded description now :)

tl;dr when node count is changed/increased all the nodes are recreated, since certs are regenerated.

@surajssd I mean, if we are using different certificates and names for kubelets (IIUC, from a quick view of the PR), then how can we generate these certificates when we add nodes after bootkube run?

Every time we run the bootkube module will be called.

For example, when we manually add nodes in terraform or when autoscaler needs to add nodes. How will those certificates for the kubelet be generated? Doesn't seem trivial, or am I missing something?

So right now when we increase the node count, since the total nodes' count has changed the bootkube module is invoked and new set of certs are generated all over again and I think it is causing all the nodes to be recreated.

@invidian

@surajssd I didn't review the PR, but in general, I believe the approach should be following for that:

generate bootstrap kubeconfig for controller node
Enable TLS bootstrapping
all remaining kubelets should get it's certificates with bootstrap method
I don't think we should generate multiple certificates with Terraform, so I would not merge this PR.

I need to check how this can be made to work with bootkube. But I have never tried with bootkube, but I have tried it with k8s setup where the control plane components were running as systemd. But I will give it a try and change the approach taken in this PR. I also think the approach isn't suitable because every time you add a new node i.e. increase/decrease the total node count all the certs are regenerated and nodes are reprovisioned, which is the last thing you want in our setup; since it's breaking what already works.

tl;dr when node count is changed/increased all the nodes are recreated, since certs are regenerated.

@surajssd I mean, if we are using different certificates and names for kubelets (IIUC, from a quick view of the PR), then how can we generate these certificates when we add nodes after bootkube run?

Every time we run the bootkube module will be called.

Oh, and that is intended? The autoscaler won't have access to bootkube, it will just set a cloud-config file for the new instance (you can replace some variables, like tokens or master IP) and that is all.
If bootkube is a requirement to add a node with this PR, then it seems like it won't be easily, at least, to implement autoscaling after this. Am I missing something?

Oh, and that is intended? The autoscaler won't have access to bootkube, it will just set a cloud-config file for the new instance (you can replace some variables, like tokens or master IP) and that is all.
If bootkube is a requirement to add a node with this PR, then it seems like it won't be easily, at least, to implement autoscaling after this. Am I missing something?

Nope that is not intended. I think in the long run for things to just work fine, we need more automation on the part where certs are provisioned for nodes and nodes join the cluster. I am investigating the TLS bootstrapping for that.


Fix typos and comments' style

You don't have to merge this pull request now, I will probably add more typo fixes here.

You can probably merge it now. I most likely won't have time to touch anything in the following weeks.


BebasDNS DoH is breaking imdb.com?

This is what it looks like when opening imdb.com with BebasDNS DoH on Firefox. I think the filters are too potent.

Fixed, removed Tiarapp from the list


S2 negative-subdued semantic background color aliases

Description
Added new semantic color aliases to Tokens Studio, in the S2 color tokens, alias sets for both light and dark themes.
They include:

negative-subdued-background-color-default
negative-subdued-background-color-hover
negative-subdued-background-color-down
negative-subdued-background-color-key-focus

Variables were also created in S2/Variables before creating this PR.

Motivation and context

New negative-subdued background tokens were needed for negative and not selected tag components. See Jira ticket
Related issue
This issue is related to the new non-color tokens for the S2 Tag component in this PR https://github.com/adobe/spectrum-tokens-studio-data/pull/56

Types of changes

 [ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [X] Minor (add a new token, changing a value; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)
Checklist:

 [X] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [X] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
TOKENS STUDIO DATA IS COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.default
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.hover
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.down
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.key-focus

SPECTRUM SYNC SUMMARY
NEW TOKENS: (4) negative-subdued-background-color-default, negative-subdued-background-color-hover, negative-subdued-background-color-down, negative-subdued-background-color-key-focus

TEST COMPLETE

SYNCING spectrum2-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/
TOKENS STUDIO DATA IS COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.default
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.hover
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.down
UPDATED METADATA - SPECTRUM UUID: spectrum2/alias.Alias.background.semantic.negative-subdued.key-focus

SPECTRUM SYNC SUMMARY
NEW TOKENS: (4) negative-subdued-background-color-default, negative-subdued-background-color-hover, negative-subdued-background-color-down, negative-subdued-background-color-key-focus

WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/spectrum2/alias/dark.json
WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-colors/spectrum2/alias/light.json
WROTE: /spectrum-tokens/packages/tokens/src/semantic-color-palette.json
SYNC COMPLETE
Spectrum Tokens Pull Request
Tokens Studio Pull Request


Adds support for devs to recreate VCR cassettes

This commit includes a giant set of conceptual changes that were needed
as part of this effort.

dotenv gem has been added and .env file is used to store
credentials needed to run the test suite
Implementing DELETE support
Disambiguating the client model from the Harvest client.
Instances of HarvestingClient have been renamed to harvest_client
in places where it would be ambiguous.
#path methods were added to Harvesting::Models::Client
Additional model classes, Harvesting::Models::Invoice and
Harvesting::Models::TaskAssignment, were added
README has been updated with a note about how to correctly delete all
of a type of entity
README has been updated with a warning about the specs destroying data
in the referenced Harvest accounts
#client accessor has been added to Harvesting::Models::Contact
User-Agent header updated to reference gem name
An RSpec shared context has been added to contain all of the setup
required to run the specs. This setup is wrapped in vcr_cassette
calls.

@mscottford Did you get a chance to see my comments?

@mscottford Just fixed the conflicts and the failing build. Thanks! 👍

I just noticed that I never responded to your comments! I need to figure out what blackhole my GitHub notifications are going in to.


Updated CI_INTEGRATION.md

We need to create a ticket (probably for Jean) that requests he update the fastlane docs in the prod to match these changes. CI_INTEGRATION.md is the source of truth.


performance issues with accessing bgzipped ancestral fastas

Accessing later regions of a fasta via a mutyper.Ancestor object (child class of pyfaidx.Fasta) is not performant, likely stemming from this issue in pyfaidx: mdshw5/pyfaidx#153.
This is particularly problematic for the mutyper targets subcommand, since it scans through all sites in a fasta record, or a sequence of bed regions.
The current workaround is to work with decompressed fasta data. A bgzipped fasta, e.g. named ancestor.fa.gz can be decompressed with bgzip -d ancestor.fa.gz to produce an uncompressed fasta ancestor.fa.

I ran into this issue using mutyper variants, good to know there's a workaround! Thanks to Luke for helping me troubleshoot!

Running into this again with a new dataset, and it's wild the difference in performance this makes. Ran the job with the bgzipped fasta for >2 days and only got 400MB through a vcf file, and now with the unzipped fasta am already at 1.5GB after an hour. Maybe consider throwing a warning or error if someone tries to input a compressed ancestral fasta? it's virtually unusable when it's that slow


Lightstrip always "on" in iOS Home App

What issue do you have? Please be as thorough and explicit as possible.
Although the lightstrip is physically off, the home app still shows it "on". To toggle the lightstrip on physically, I first have to turn off the in home app, the click it once more to turn on. After turning it off in the home app, after a few minutes it shows as on again (even though its off physically).
You can see in the log that after I turn off the lightstrip using the home app, a few seconds later it turns itself back on. The lightstrip itself does not turn on, but the home app thinks it does.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI v4.41.5

Which version of Homebridge/HOOBS do you have?
v4.41.5

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi Zero W
Node v16.13.1

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
v4.23.1

Which Govee devices do you have that are causing issues? Please include product models if applicable.

Lightstrip H6199
Please paste any relevant logs below.

[07/01/2022, 00:52:05] Homebridge v1.3.9 (HAP v0.9.8) (Homebridge 1282) is running on port 51858.
[07/01/2022, 00:52:14] [Govee] Bluetooth hardware and packages found successfully.
[07/01/2022, 00:52:17] [Govee] [H6199_1468] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"disableAWS":"no","enableBT":"yes","logging":"standard"}.
[07/01/2022, 00:52:17] [Govee] [H6199_1468] initialised with id [xxxx].
[07/01/2022, 00:52:20] [Govee] ✓ Setup complete. Have time to give this plugin a review? http://bit.ly/hb-govee-review
[07/01/2022, 00:52:22] [Govee] [H6199_1468] has been reported [offline].
[07/01/2022, 00:52:27] [Govee] [H6199_1468] current state [off].
[07/01/2022, 00:52:34] [Govee] [H6199_1468] current state [on].
[07/01/2022, 00:52:40] [Govee] [H6199_1468] current state [off].
[07/01/2022, 00:52:50] [Govee] [noble] Peripheral already connected at Peripheral.connect (/usr/local/lib/node_modules/homebridge-govee/node_modules/@abandonware/noble/lib/peripheral.js:47:26).
[07/01/2022, 00:53:47] [Govee] [H6199_1468] current state [on].

Thanks for coming on here.
Have you obtained an API key and configured this in the plugin?
https://github.com/bwp91/homebridge-govee/wiki/Configuration#obtaining-your-api-key
Also please verify that the lights are connected to wifi - if may be worth trying to unplug and plug back in the light strip if you can. In your logs you can see that they are being reported offline by Govee, this may be why they are always showing as ON (as this is the last data reported by Govee before the device went offline).

Hey Ben,
Yup I have the API key in and wifi enabled.

Hey Ben,
I have the API inserted, power cycled the lightstrip, made sure it was on wifi, still seems to have the problem.

Can you show me a screenshot of your devices tab in the govee app please?

Seems like my wifi setting were mixed up. After a few tries it (really) connected via Wifi and now the plugin is working correctly with my home app. Thanks for your help Ben, appreciate it!


Fix main in zstd-sys build.rs: Use var_os for CARGO_MANIFEST_DIR

Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

Thanks for the PR!


Use EEx templates for mails

As suggested by @jxs, we should use EEx templates for mails.

[ ] How should configuration look like? (multipart-mails, CC/BCC/header fields in general)
[ ] I18N? (see also #13)
[ ] Support for mail attachments / inline images?
[ ] Support for non-mailgun mailers?

Opinions and PRs are welcome!

imho

configuration should have a couple of defaults, and be extendable
I18N yes, definitely if possible
unnecessary if templates are extendable
yes definitely

what do you think @trenpixster ?

Nice one guys, Eex templates is definitely the way to go :+1:
Here are some thoughts:
1 - I'm thinking in turning everything regarding e-mail configurations into a hash, with sensible defaults, so we'd be able to have people configure e-mails - maybe even all configurations - like:
%{
  register: {
    template: Foo.Bar,
    from: "FooBar<EMAIL_ADDRESS>    bcc<EMAIL_ADDRESS>    html: true
  },
  password_recover: {
    template: Foo.Baz,
    from: "FooBar<EMAIL_ADDRESS>    html: true
  }
}

What do you think?
2 - This would be a great plus, just not sure the best way to implement it, still haven't looked at Linguist.
3 - I'm not foreseeing a case where an attachment is required?
4 - Yup, presentation layer should be agnostic of the underlying e-mail gateway.

agree with all :+1:

Maybe we do not need to reinvent the wheel, as there is already a very promising Elixir library available:
https://github.com/kamilc/mailman
Unfortunately, it seems that is a little bit outdated. I will try to contact the author.

That's a nice library there. I wouldn't use it instead of the current solution, though:

We could include the mail sending capability by defining it as a new mailer, Addict.Mailers.SMTP.
Re-using the way it populates context data into the eex template on the Addict.EmailGateway would also be nice.

What do you think?

yeah, agree with you @trenpixster

Quick update: thanks to @kamilc, mailman is now available as hex package:
https://hex.pm/packages/mailman

#68


FR: Allow theme colors

If i use theme variables in the configuration.
theme.yaml
  # My colors
  my-blue: "#55acee"
  my-green: "#9bc53d"
  my-yellow: "#fde74c"
  my-red: "#c3423f"

config
    - type: line
      entities:
        - entity: sensor.ds18b20_01
          name: Temp one
          color: var(--my-green)
          #color: "#55acee"
        - entity: sensor.ds18b20_02
          name: Temp two
          color: var(--my-yellow)
          #color: "#55acee"

it shows this:

Thanks for this wonderfull card!

CSS variables aren't supported at this time, only normal html colors. But I can see how having them would be useful for streamlining the theme. It's only a few lines of code to add, so I'll schedule that for the next release.

Added to V1.0.13. You'll have to specify the CSS var without the var() keyword, see Readme.

Thank you! :heart:


UAEPass Outbound Authenticator with WSO2 Identity Server

Purpose

UAEPass Authenticator is developed as an outbound OIDC federated authentication connector for UAEPass Identity Provider. This connector supports WSO2 IS from version 5.11.0 and later. The following figure shows the overall view of the federated login scenario.

Goals

Support federated authentication with UAEPass and WSO2 IS as a dedicated authenticator.
Ability to dive into both Staging and Production.
An alternative solution to support common-auth logout from UAEPass.

Approach

Release note

Can redirect back to the SP screen after common-auth logout is triggered.

Documentation

Click here to browse the documentation

Automation tests

Unit tests

51%

Integration tests

Not done

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran the FindSecurityBugs plugin and verified the report? Not done
Ran sonar scanner plugin and verified the report? - Yes, Zero bugs and vulnerabilities.
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes (Only included sample data in test cases class.)

Related PRs

https://github.com/wso2-cs/client-etisalat-iam/pull/2

Test environment

JDK 8
JDK 11
UAEPass Staging
WSO2 IS 5.11.0 vanilla to onwards

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Wrong behavior in RTL mode

When the APP is in RTL mode, everything is reverse but can ignore,
The time picker will shows . wrong labels and selects wrong values in RTL mode.

I have this issue too. If I could I would do a pr and add isRTL boolean so that it reverse the rows and columns

Fix this issue in 1.0.0-beta.7 version . (and add reverse props for more customize)


Allow for more structured package mapping rule attributes

This change modifies the attributes attribute of pkg_files and pkg_mkdirs
to allow for more structured inputs than a list of strings.
For the lack of a better option, the solution for this right now is to serialize
the data in terms of JSON strings, which will be assembled using the new
pkg_attributes macro.  Users should always use pkg_attributes for this
purpose.
The JSON is decoded within the mapping rules and passed out through their
providers.
A better option would be to pass Providers full of structured data directly into
rules, but, unfortunately Bazel does not support this at this time.

A potential issue with this is that buildifier may want to sort named arguments in the order of (group, mode, user).  The most readable ordering for these is (mode, user, group).
We may be able to override it with additions to buildifier's tables, but that may not be sufficient.

Latest force-push updates documentation and cleaned up some noticed whitespace issues.

Github review is too painful to try incremental things. Let's get #273 in and then look at this.

Github review is too painful to try incremental things. Let's get #273 in and then look at this.

Done!

If you think you got the 'non surprising' behavior, go ahead and try to merge. Can you? If not, I will.

If you think you got the 'non surprising' behavior, go ahead and try to merge. Can you? If not, I will.

Yeah, I can.  Got sidetracked with a few internal things.


Extension Methods - Remove namespaces add docs

Remove name spaces from Extension classes and add top level documentation where missing.
Extension classes shouldn't have namespaces so that they are easier for developers to discover (source: #2). Anvil didn't consistently apply this rule until now.
What is the current behaviour?
Some extension method classes have namespaces that require the developer to import before using.
What is the new behaviour?
All extension method classes exist at the root namespace.
What issues does this resolve?
Developer discover ability of namespaces
What PRs does this depend on?

None

Does this introduce a breaking change?

[ ] Yes
[x] No - You may have unused import statements code now.

Instead of adding to the namespace that the extension is intended for, could you use your own for all extension classes? namespace Anvil.CSharp.Extensions?
Just out of curiosity, why does putting them in a namespace hinder discoverability? Do the extensions just not appear in autocomplete?

Instead of adding to the namespace that the extension is intended for, could you use your own for all extension classes? namespace Anvil.CSharp.Extensions?
Just out of curiosity, why does putting them in a namespace hinder discoverability? Do the extensions just not appear in autocomplete?

Some IDE configurations don't show intellisense for options in namespaces that haven't been imported into the current context. Others require a different key combination than the standard one used to bring up intellisense.
While it's pretty normal to press the extra key combo when writing a type it's less common to think to do so when writing the method portion of a statement. Having extension methods outside of a namespace allows the method to always appear when working with an instance of the target type.

Are name conflicts not a concern then? I know Anvil only has a couple of users today, but even if you tried to include some third-party library one day that defines its own TypeExtension class with no namespace, you'd have compile errors until someone changes the name right?

I would vote for a single .Extensions namespace for all static extension classes, easier to maintain and include. Speaking personally, I tend to have a template file for C# or Unity projects, and would just include said extensions namespace by default.
This isn't worth changing at this point, but out of curiosity, was there a reason to use Anvil.CSharp.<Area> over Anvil.<Area> in namespaces and similar?

Alright, you guys make good arguments. I went and tested VSCode and Visual Studio for Mac. Either by default or after changing some preferences both behave the same way as rider with regard to discoverability of extension methods in an un-imported namespace.
My mind was stuck in the past, we live in the future now and IDEs are better.
With that in mind we should just put the extension methods in the same namespace as their siblings in the same directory.
Will close this PR and adjust the approach.

This isn't worth changing at this point, but out of curiosity, was there a reason to use Anvil.CSharp. over Anvil. in namespaces and similar?

It's been a while but I think the rationale was that this was the Pure C#/.NET variant of Anvil. C#/.NET was the platform while anvil-unity-core is Anvil.Unity.*
Maybe we should have instead built onto the Anvil.CSharp. prefix in the Unity module to make it Anvil.CSharp.Unity...
That way you could say
What library is this? -> Anvil
What language is it implemented in? -> Csharp
What is the specific platform that's required -> Unity.
That way in the future, let's say Boo in Unity took off again. You could have an Anvil.Boo.Unity that would be separate from Anvil.Csharp.Unity`.
...but we didn't and, like you said, I'm not sure it's worth changing at this point.


Language recognition in evaluation process with NEDCorpusEvaluation class

With the current version, the evaluation with NEDCorpusEvaluation class only possible with English language. In order to do the evaluation with several languages, it is needed the process of language recognition as a prerequisite prior to the evaluation step.

If the language is specified in the filename of the txt file is better to take it from there first.


🐛 fixes #188

This addresses the deprecation warning below.
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, 16px) or calc($value / 16px)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷
28 │     @return $value / 16px * 1em;
   │             ^^^^^^^^^^^^^
   ╵
    node_modules/breakpoint-sass/stylesheets/breakpoint/_helpers.scss 28:13                 base-conversion()
    node_modules/breakpoint-sass/stylesheets/breakpoint/_helpers.scss 20:13                 breakpoint-to-base-em()
    node_modules/breakpoint-sass/stylesheets/breakpoint/parsers/double/_default.scss 18:13  breakpoint-parse-double-default()
    node_modules/breakpoint-sass/stylesheets/breakpoint/parsers/_double.scss 29:14          breakpoint-parse-double()
    node_modules/breakpoint-sass/stylesheets/breakpoint/_parsers.scss 178:20                breakpoint-parse()
    node_modules/breakpoint-sass/stylesheets/breakpoint/_parsers.scss 48:22                 breakpoint()
    node_modules/breakpoint-sass/stylesheets/_breakpoint.scss 46:16                         breakpoint()

@Snugug Just checking to see if you've had a chance to review this PR yet.

Thanks for taking a look at this! I really appreciate it!
While this is an elegant fix, I'd prefer this be resolved by upgrading to the new math.div as returning the result of a calc will change the browser support for Breakpoint (calc vs media queries).
Thanks!

@Snugug Thanks. I've updated the PR to make use of the built-in sass:math module instead of the calc function.


Classifier counts are off

DCL count is 1, although there are 4 examples
LCL count is 2, although there are 3 examples

Hi Carol are both of these considered classifiers (One has a semi colon and the other does not)?
DCL"opening can"
DCL:crvd-L"bagel"

Hi -
Yes - both are classifiers.
Classifiers very often (but not always) have a colon followed by handshape
preceding the “description of the meaning”.
Thanks,
Carol

On Oct 14, 2017, at 10:50 AM, kwasiopoku<EMAIL_ADDRESS>wrote:
Hi Carol are both of these considered classifiers (One has a semi colon and the other does not)?
DCL"opening can"
DCL:crvd-L"bagel"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/DCS-LCSR/ASL-DAI/issues/27#issuecomment-336639757, or mute the thread https://github.com/notifications/unsubscribe-auth/AM_2wnOTPXnnMiwr8BbN7ly3DI2DKDIkks5ssMpAgaJpZM4P4hD1.

Fixed


Unable to debug application when using library version 0.7.0

First, I'am able to successfully flash the STM32F303x and run the application.
The issue I'm facing is attempting to debug the application with GDB/OpenOCD.
When issuing a cargo run I see the following messages (emphasis mine):

Reading symbols from target/thumbv7em-none-eabihf/debug/app...
DW_FORM_strp pointing outside of .debug_str section [in module /Users/Me/Projects/embedded_template/target/thumbv7em-none-eabihf/debug/app]

(No debugging symbols found in target/thumbv7em-none-eabihf/debug/app)

As a result I'am unable to set break points or use layout src in GDB.
This only occurs when using cortex-m version 0.7.0.
If I use version 0.6.4 I'am able to successfully debug the application.
Aside from the memory.x file is there additional configuration needed for the newest version of the library?
Are specific versions of the library only compatible with specific MCU's?
Does the version of the cortex-m library require a specific version of GDB?
Below is my memory.x file if it helps:
MEMORY
{
    CCRAM : ORIGIN = 0x10000000, LENGTH = 8K
    FLASH : ORIGIN = 0x08000000, LENGTH = 256K
    RAM : ORIGIN = 0x20000000, LENGTH = 40K
}
_stack_start = ORIGIN(CCRAM) + LENGTH(CCRAM);

This seems to be an upstream issue, it is fixed on nightly Rust versions.

This seems to be an upstream issue, it is fixed on nightly Rust versions.

OK great, thanks @jonas-schievink

OK great, thanks @jonas-schievink

@jonas-schievink so to be clear if I pass -Clinker-plugin-lto to the compiler I should be able to use version 0.7?

@jonas-schievink so to be clear if I pass -Clinker-plugin-lto to the compiler I should be able to use version 0.7?

This is now fixed by the new 0.7.1 release (containing #318).

This is now fixed by the new 0.7.1 release (containing #318).

@jonas-schievink so to be clear if I pass -Clinker-plugin-lto to the compiler I should be able to use version 0.7? Or should I wait for version 0.7.1 to be released?

Hopefully 0.7.1 solves the issue! Thanks for reporting the bug, sorry we couldn't get it fixed sooner.

@jonas-schievink so to be clear if I pass -Clinker-plugin-lto to the compiler I should be able to use version 0.7? Or should I wait for version 0.7.1 to be released?

Hopefully 0.7.1 solves the issue! Thanks for reporting the bug, sorry we couldn't get it fixed sooner.


Deprecation error with syntax blocker for Chef13

Bumping: https://github.com/sethvargo/chef-sugar/issues/146
Deprecation errors still present and will break cookbook in Chef13.
         method access to node attributes (node.foo.bar) is deprecated and will be removed in Chef 13, please use bracket syntax (node["foo"]["bar"]) at 1 location:
           - /opt/chef/embedded/lib/ruby/gems/2.3.0/gems/chef-sugar-3.5.0/lib/chef/sugar/node.rb:162:in `method_missing'
          See https://docs.chef.io/deprecations_attributes.html for further details.

This is definitely an issue. Any chance it will be fixed soon?


Simplify job evaluation avoiding a double-loop

In before there was a for-loop and after that a call to "all". Instead
we can just move the body of the for-loop into the evaluation called by
"all". This is cleaner, avoids the double-loop and also helps to
unindent code preventing more annoying log-message line-wrapping.
Motivated by #168 . @michaelgrifalconi if we accept this PR before #168 then you would need to only change https://github.com/openSUSE/qem-bot/pull/168/files#diff-d44cab80bf43c62865043529f6e9883cc12ab37d49f5fb5af9e1bdc7c012dcaaR195 and additionally pass "api" to the method "job_acceptable"

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.98%. Comparing base (97005ee) to head (aa6d62b).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #169   +/-   ##
=======================================
  Coverage   66.98%   66.98%
=======================================
  Files          25       25
  Lines        1663     1663
=======================================
  Hits         1114     1114
  Misses        549      549

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Actually, while working on my PR, I did change that in a different way that sounded better and simpler and then come back to the original to avoid refactoring unrelated stuff.
I am not a big fan of your proposal, while it makes it a bit cleaner, fees a touch more difficult to follow/debug/understand.
How about getting rid of the all() call, and instead return "acceptable" bool variable which starts as true and become false if there is a failure?
I can provide the change if I did not mange to explain what I mean :)

Actually, while working on my PR, I did change that in a different way that sounded better and simpler and then come back to the original to avoid refactoring unrelated stuff.
I am not a big fan of your proposal, while it makes it a bit cleaner, fees a touch more difficult to follow/debug/understand.
How about getting rid of the all() call, and instead return "acceptable" bool variable which starts as true and become false if there is a failure? I can provide the change if I did not mange to explain what I mean :)

Hm, I quite like the functional approach with "all" which is akin to the list comprehension in python. Many people use too much procedural code. I doubt you will convince me with an extended for-loop here :)


Wavy background on main menu

Describe your problem here.
Im trying to fix this error, but im getting this error:

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
For testing only

okay, is the first one really not that obvious? you're missing arguments for the function

I know, but im trying to fix it lol

Now i got this lol.
Second error showing this:

if statements can't be used in a function @Stefan2008Git

UGH
What i need to do? Im still learning Haxe damn

add the proper arguments

this is how


Support more endpoints

The current support for Discord API REST endpoints is sufficient to begin with, but it still misses support for a lot of endpoints that one might need someday.
Luckily adding new endpoints is usually easy, but it's still sub-optimal that users need to add these endpoints themselves.
(PRs are appreciated)
Checklist

[x] Application Commands
[ ] Application Role Connection Metadata
[x] Audit Logs
[ ] Auto Moderation
[ ] Channels

[x] Reactions
[x] Threads
[x] Manage Channels
[ ] Messages (Partial support)
[ ]  Others (Invites, Permissions, etc...)

[ ] Emoji
[ ] Guilds

[x] Manage Guilds
[ ] Roles (Partial support)
[ ] Members (Partial support)
[ ] Others (Bans, Widgets, Voice, etc...)

[ ] Guild Scheduled Event
[ ] Guild Template
[ ] Invite
[ ] Stage Instance
[ ] Sticker
[ ] User
[ ] Voice
[x] Webhook
[x] CDN Resources

All endpoints have been added to the Endpoint enums using Discord's own alpha Postman collection and with the help of a Command plugin, but not all Endpoints have a function in DiscordClient.

Hi, thank you so much for the library, I've so far been using Sword and thus stuck on Swift 4. DiscordBM is such a nice breath of fresh air, I can finally use async/await in my bot \o/ (or even just Swift's own Result type lol).
I was just looking for a way to send a typing notification which I find to be great for showing loading states, e.g. the bot making slow network requests. I found the endpoint in DiscordBM, but not much else. Am I correct in assuming this is one of the not yet integrated endpoints?

@kiliankoe are you talking about this endpoint?
https://discord.com/developers/docs/resources/channel#trigger-typing-indicator
Generally you can just search the link url in DiscordBM. If something exists, it's link is near it so you'll find out.
This endpoint is not supported but it's a one those pretty simple endpoints so i can just put add it to DiscordBM in a few minutes.
If you are using slash commands, you won't need this endpoint since slash commands have "native" support for showing a "loading" indicator.

Oh that's awesome, thanks!! That works well :)


Improve Device definitions

Each device now also reports the number of rows and colums for each
button. This could be used by GUI applications to easily display the
layout.
New devices.go file containing functions shared by each device's go
file.
Dynamically determine the Reset and Brightness packets

Fixes:

Ensure the Mini's brightness packet contains all the header bytes

Thanks for this; I'm just tweaking it a little to move the device-specific bits out of "shared" and back into the device files, and then I'll merge it.

Thanks for this; I'm just tweaking it a little to move the device-specific bits out of "shared" and back into the device files, and then I'll merge it.


setTimeout -> setImmediate

If you run webpack not directly but through a wrapper (like grunt-webpack) then using setTimeout generates race conditions: sometimes grunt is killing webpack thinking that everything went good and bundle-analyze is not firing at all.
Changing that to setImmediate fixes the problem and still placing all the logs to the bottom

Thanks!

In v1.5.4


Animated webP support

add animated webP support
add example for animated webP

Animated webP is a more cool than gif and more and more people need it
I add some code for support animated webP and add an example for it。it works well

line 18 should be #import "libwebp/webp/mux_types.h", change it and works

sorry, it's my mistake, i have fix it

Merged via 88b025a in 4.x branch

we found that animated webp play fast than normal gif


Server Sync

Adding support to allow ReliableCommunication instances to find each other through a server at a known address. That server only provides the port and IPs of other devices and doesn't route traffic. This only works on a local network.
A sample server can be found at Comms/webserver.
The server hosts 'rooms' which are created by ReliableCommunication servers.
Each room has a passkey to enter which is set by the ReliableCommunication server. ReliableCommunication clients must know this passkey to enter.
Here is what the update GUI looks like for this method

@danilogr I'm going to merge this so I can use it for ARTEMIS. Tagging you because I imagine you want to take a look at it.


Accept optional plugin options

when plugin is an Array of the form [PluginName, {}], then accept the second param as options to the plugin
hecs-plugin-three accepts the following options:

renderer: a THREE.WebGLRenderer instance
scene: a THREE.Scene instance, possibly with lights
camera: a THREE.PerspectiveCamera instance

Fixes #23, #20
Relates to #25

I'm not sure I like the syntax of using every 2nd array item for options to the previous item. Feels hacky.
A cleaner approach might be to make plugins require instantiation with options, eg:
import { World } from 'hecs'
import ThreePlugin from 'hecs-plugin-three'

const world = new World({
  plugins: [new ThreePlugin({ /* options */ })]
})

What do you think?

That would work fine for me. Wouldn't that mean switching all plugins from an object (via createPlugin) each to a class?

Could even be a plain old function for simplicity?

I spent a bit trying to build the above solution and just realised it's probably a lot simpler to just let you do that at the plugin level.
As an example, for non-configurable plugins you just export this:
export default function BasicPlugin = createPlugin({
  name: 'basic-plugin',
  decorate(world) {
    world.basicPlugin = true
  }
})

And use it like this:
const world = new World({
  plugins: [BasicPlugin],
})

But if you want a configurable plugin you can just do this:
export default function ConfigurablePlugin(options) {
  return createPlugin({
    name: 'configurable-plugin',
    decorate(world) {
      world.apiKey = options.apiKey
    }
  })
}

And use it like this:
const apiKey = 'ABC123'
const world = new World({
  plugins: [ConfigurablePlugin({ apiKey })],
})

@canadaduane this should resolve the issue, what do you think?

Oh, fun. Closures FTW. I see what you mean now. Let me try this and see if it does what I need.

Yup, that's all I need. Nice solution!


Fixing SQLi Vulnerability

As mentioned in https://github.com/hypertrace/document-store/issues/14, for the existing Postgres Implementation, while building where clause, we were appending strings that are prone to SQL Injections.
In this PR, we are building a parameterized where clause. While building the String query, we will add ? instead of the actual value. Also, in parallel, we will build a Map<Integer, Object> which will consist of the index and the actual param value.
Both of the above will be used while building the PreparedStatement.

https://github.com/hypertrace/document-store/issues/14

great job @jainnidhi703 could you please describe in this PR how is this issue being fixed?

closing this as taken care as part of - https://github.com/hypertrace/document-store/pull/30


Frontend Homework 7

Drift Video Link:- https://video.drift.com/v/abzyP4T9aXMLCPogiNFF5rwJyayH2CcaYIZ3ZvTHZV2P4/
Screenshots:-

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
0

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


refactor: dynamic support for hash algs

This PR refactors the crate to support hash algorithms determined at runtime.
Issue #39
TODO

Fix doctests

How do I use this PR with the doctests removed temporarily? I was going to fork this to add blake3 support as well...


Memory Leak in PatchBufferFixed when using boost::serialization

Contrary to its name the fixed buffer in PatchBufferFixed is never cleared. This occurs possibly only when using boost::serialization. This leads to a steadily growing memory usage during MPI calculations as this buffer is used to store kernel and rim during ghost zone calculations.
Patch diff:
libgeodecomp/storage/patchbufferfixed.h
77d76
<             buffer[indexRead].clear();

After deliberation, a better patch would be
57d56
< buffer[indexRead].clear()


All axe heads exept for the base one don't show reinforcements

That is wierd, I didn't find anything obvious in the configs, so I'll have another look later.

Lol, all of the axe models had the wrong order.


Send thank you email from hello@:collectiveSlug.opencollective.com

Also fixes unsubscribe and adds the address in the ticket confirmation email.

Coverage decreased (-0.005%) to 81.204% when pulling 6b8c8d9ce3406e27edaf8a74c6fa80c34fbb73e1 on hello into a6dcf10925ab437ea9515f171c8abf2c7cd17b39 on master.


Add scrolling to the list

Currently, the list is pushing down the footer when too many tasks are added.

You can start working on this issue


[SPARK-49576][INFRA] Upload Python logs in CI

What changes were proposed in this pull request?
This PR proposes to upload Python logs as well after test execution.
Why are the changes needed?
We should be able to debug Python test failures, e.g. https://github.com/apache/spark/actions/runs/10726544359/job/29763316706
/_w/spark/spark/python/target/28a23950-46c7-45c5-a9b7-42e7d9b21518/python3.12pyspark.sql.tests.connect.test_connect_session_ah_ug0xu.log)

Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Manually.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.


Can't have webhook working in multiple namespaces

We're installing the spark op to multiple namespaces. Our trick for now is to installCRDs only for the first install. The problem is that a second install breaks the first install's webhook.
Any idea on how to support this, i.e., deploy the spark op to multiple k8s ns?
Thanks

What you meant by breaks the first install's webhook?

Sorry, secrets and confimaps stopped being mounted in first install.

Got it. Do you have the flag webhook-namespace-selector set? The selector field in the MutatingWebhookConfiguration is set based on the value of webhook-namespace-selector. Since MutatingWebhookConfiguration is global (non-namespaced),  the webhook running in one namespace overrides the MutatingWebhookConfiguration created by the webhook in another namespace, and effectively changes the namespace selector.

Searching around the code and docs, I don't see it documented.  It seems that wanting to have multiple spark operators installed in a development cluster is something others want to do be able to do as well.  It would be great to have a recipe for doing that.  And/or a pointer into the pattern as used in Kubernetes itself.

Completely agree with @jkleckner . Currently, we have a hack for only installing the CRDs on first install and removing them on last install. We're still testing out the webhook part (thanks @liyinan926!).

A good way to make the webhook work for multiple namespaces is to add some custom label to each of the namespaces, e.g., spark-operator-webhook-applicable=true, and then set the label selector spark-operator-webhook-applicable=true when starting the operator.

Hi, we tried many alternatives and all fail. Once we install the second spark op it prevents secrets/configmaps from being mounted in the first spark op.
Here's what we ran:
`
kubectl label --overwrite ns ns1 ns1-webhook-applicable=true
helm install spark-operator ./charts/sparkoperator
--namespace ns1
--set installCrds=true
--set operatorVersion=v1beta2-1.1.1-2.4.5
--set sparkJobNamespace=ns1
--set imagePullPolicy=Always
--set enable-metrics=true
--set enableWebhook=true
--set webhookPort=443
--set webhookServiceNamespace=ns1
--set webhookNamespaceSelector=ns1-webhook-applicable=true
kubectl label --overwrite ns ns2 ns2-webhook-applicable=true
helm install spark-operator ./charts/sparkoperator
--namespace ns2
--set installCrds=false
--set operatorVersion=v1beta2-1.1.1-2.4.5
--set sparkJobNamespace=ns2
--set imagePullPolicy=Always
--set enable-metrics=true
--set enableWebhook=true
--set webhookPort=443
--set webhookServiceNamespace=ns2
--set webhookNamespaceSelector=ns2-webhook-applicable=true
`
We also tried with and without the webhookServiceNamespace which also failed.
Any idea what's wrong?
Thanks

I have a problem which I think is related to this: #892
Turns out the chart is helm's incubator repo does not support this settings yet. After I added this flag myself it seems to work properly.

Hey @doctapp great to hear that! Can you create a PR for the instructions above?

Glad it worked out for you. I have a few questions around your approach:

I did a similar change in the helm chart but with a different namespace label convension: sparkoperator.webhook.selector={{ .Values.sparkJobNamespace }}. This saves one variable in the value file, I can't think of a case where the webhook should listens to a different namespace than {{ .Values.sparkJobNamespace }} ?
The webhook configname in the chart has {{ include "sparkoperator.fullname" . }} as prefix, so installing with helm would result this to be different in each install? I'm not sure if it's necessary to add a suffix {{ .Release.Namespace }} to difficiate it as well.
I'm not sure what's your usecase for two installs of SparkOperator but I'm not sure if set --set installCrds=true for both SparkOperator is an issue? Unless one of them gets deleted at some point.

@liyinan926 Would do a PR on a consolidated repo between this one and https://github.com/helm/charts/tree/master/incubator/sparkoperator as I have no idea which one is supposed to be the master. Thanks :)
@andizzle:

Makes sense, can't see why you would listen do a different namespace
Yes, that's what we need for running multiple spark ops. Config name is cluster wide, therefore, you need to have multiple configs for deploying Spark Op to multiple namespaces
Use case for installing is running Spark jobs in isolation in different namespaces. If you set installCrds=true beyond the first install, you'll have problems when deleting the operators. Our use case requires different life cycles for each spark op instance, e.g., create ns1, create ns2, delete ns1, create ns1...

Hi @doctapp  we are trying to accomplish the same on Openshift cluster but facing same issue. Do you have any document or detailed steps to follow to overcome this issue. I am not sure downside of resolution not included in chart yet.
I tried steps given by you above but looks like something missing or got updated in helmchart till time.

Will close this issue, starting from version 2.0.0, the webhook will work as expected  when multiple Spark operator instances are deployed, each watching different namespaces with proper namespace selector and object selector configured automatically.


Feature Request: Allow custom fields inside commit message

For our purpose, we need to add a custom field into the commit message.
In our case, we have a string field with a Jira Ticket Nr. that needs to be added to the commit message.

The is available in v4.2.0.


HOTFIX : assignments should only show forms filtered on the posible f…

…orms of the org unit
Explain what problem this PR is resolving
Related JIRA tickets : IA-XXX, WC2-XXX, POLIO-XXX
Self proofreading checklist

[ ] Did I use eslint and black formatters
[ ] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] New translations have been added or updated if new strings have been introduced in the frontend
[ ] My migrations file are included
[ ] Are there enough tests
[ ] Documentation has been included (for new feature)

Changes
Explain the changes that were made. The idea is not to list exhaustively all the changes made (GitHub already provides a full diff), but to help the reviewers better understand:

which specific file changes go together, e.g: when creating a table in the front-end, there usually is a config file that goes with it
the reasoning behind some changes, e.g: deleted files because they are now redundant
the behaviour to expect, e.g: tooltip has purple background color because the client likes it so, changed a key in the API response to be consistent with other endpoints

How to test
Explain how to test your PR.
If a specific config is required explain it here (dataset, account, profile, ...)
Print screen / video
Upload here print screens or videos showing the changes
Notes
Things that the reviewers should know: known bugs that are out of the scope of the PR, other trade-offs that were made.
If the PR depends on a PR in bluesquare-components, or merges into another PR (i.o. main), it should also be mentioned here

Non, non, c'était un bug, ceci. La feature flag, c'est pour autre chose.


Protecting from stack overflow in recursive functions.

Suppose you have some recursive function:
fn recursee(n: i64) -> Result<i64, ()> {
    if n > 0 {
        Ok(1+ try!(recursee(n-1)))
    } else {
        Ok(0)
    }
}

fn main() {
    println!("{:?}", recursee(3));
    println!("{:?}", recursee(100));
    println!("{:?}", recursee(999999999));
    println!("{:?}", recursee(5000));
}

It works for small values (that you need). But attacker can supply special unbalanced bad data that cause stack overflow. Getting rid of recursion requires big redesign and regretting about committing the "Let's use clever recursion here" idea. What if we can just add a direct protection against stack overlow?
#![feature(asm)]

fn sp() -> usize {
    let sp : usize;
    unsafe {
        asm!("":"={esp}"(sp):::"volatile");
    }
    sp
}

static mut near_stack_top : usize = 0;

fn get_stack_gauge() -> f64 {

    let stack_size = if cfg!(target_env="musl") { 0x18000 } else { 0x800000 };

    let (s, st, ss) = (sp() as f64, unsafe { near_stack_top } as f64, stack_size as f64);

    (st - s) / ss
}

fn recursee(n: i64) -> Result<i64, ()> {
    if get_stack_gauge() > 0.95 {
        // stack overflow is nearing
        return Err(());
    }

    if n > 0 {
        Ok(1+ try!(recursee(n-1)))
    } else {
        Ok(0)
    }
}

fn main() {
    unsafe { near_stack_top = sp(); }

    println!("{:?}", recursee(3));
    println!("{:?}", recursee(100));
    println!("{:?}", recursee(999999999));
    println!("{:?}", recursee(5000));
}

Ok(3)
Ok(100)
Err(())
Ok(5000)

Maybe functions for being aware of how much stack is still available should be a bit closer to language, so there can be
fn get_stack_gauge() -> f64 {
    (::std::stack:remaining() as f64) / (::std::stack::size() as f64)
}

?
Alternative ideas:

Special macro like try_recurse!(recursee(n)) that tries to check if there enough stack for calling and throws othewise;

https://crates.io/crates/stacker/ looks like something similar to what you're describing

Shall I move the issue to stacker? Maybe it can provide more than one function to allow checking for stack without growing it.

Yeah I agree with @jonas-schievink in that I think this should probably grow outside the standard library (perhaps on crates.io), and I think that the stacker crate provides a good way in for now!

Late bloomer here.
Is this an issue when you write a tail call optimised function?

Neither rustc nor llvm currently guarantee any tail optimization, so writing a function that you think should be TCO often isn't
See https://github.com/rust-lang/rfcs/issues/271
To answer your question, though, this should not happen if the function is tail call optimized

Thank you, @tupshin

Another late bloomer here. Is stacker the advised solution for now? Is TCO coming at some point?

Not sure a separate crate is what you want here, because you could argue rust is memory unsafe if this is not protected against.

Stack probes ensure that stack overflows do not ensure in memory safety
holes.
On Mon, Oct 29, 2018, 06:40 Julian Ospald<EMAIL_ADDRESS>wrote:

Not sure a separate crate is what you want here, because you could argue
rust is memory unsafe if this is not protected against.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/rfcs/issues/1488#issuecomment-433786600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApc0svArTGXoELtv9P6Uel2t94RcLuBks5upobagaJpZM4HShTE
.

I found several DoS attacks due to recursive functions in the past, so that's something I'm really interested in


repokitteh: Print docs link

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:

in response to /docs command
for any PR that has a prefix of docs:

Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/rk-bless

/docs

/docs

/docs

cc @alyssawilk @RyanTheOptimist as i know you update READMEs quite a bit
one consequence of this PR is that you probably dont want to make a PR that is not going to change the rendered docs docs: ... - perhaps use something like readme: ...


Crash adjusting "Fee: Priority" option

Tested on windows wallet on windows 7, windows 2012 r2, windows 2008 r2
When using "send max amount" option to send coins. on the next screen if you then try and adjust the "Fee: Priority" option the wallet crashes irrecoverably and a restart is required.

disabling the fee as its not necessary to use a custom fee for our blockchain.


Add Tests and documentation for Spark types

Terms

THIS SOFTWARE IS CONTRIBUTED SUBJECT TO THE TERMS OF THE TERMS OF THE CCLA DATED 2017-11-07 WITH FINOS/LINUX FOUNDATION (FORMERLY THE SYMPHONY SOFTWARE FOUNDATION CCLA).
  THIS SOFTWARE MAY BE REDISTRIBUTED TO OTHERS ONLY BY EFFECTIVELY USING THIS OR ANOTHER EQUIVALENT DISCLAIMER IN ADDITION TO ANY OTHER REQUIRED LICENSE TERMS.

the CI is currently failing because of Error: tests-integration/generated/refModel/src/typescript/Morphir.ts(191,7): error TS2440: Import declaration conflicts with local declaration of 'SparkTests'., I suspect this is a combination of a breaking change in typescript (https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#local-and-imported-type-declarations-now-conflict), and possibly caused by typescript generating code where a source file and a directory have the same name, but am currently trying to confirm that.


CANVAS-94 - Connect LTI app to MongoDB Atlas

@maxpluez @chern Needed to change the DB connect string to just be the URL since I wasn't able to get the code to connect to MongoDB Atlas with the connection string separated in parts. So adopting this code you would need to change your .env to have this set:
DB_URL=mongodb://localhost:27017/lti-media-resources?replicaSet=rs0
For MongoDB Atlas this would be:
DB_URL=mongodb+srv://:@/lti-media-resources

@rlorenzo Looks good, just tested locally


mraa fix for dev branch

This was resolved via https://github.com/openaps/oref0/pull/504 - thanks to everyone for driving this while we were traveling!  :-)


SpatialEditor Gridlines are almost invisible (e611ff5)

Operating system or device, Godot version, GPU Model and driver (if graphics related):
e611ff5; OpenGL ES 3.0 Renderer: GeForce 800M/PCIe/SSE2
Issue description:

Regression from e611ff5
Steps to reproduce:
Run the editor

It can be fixed by #10990 so this might be the duplicate of #10987.


Add special tag javascript-obfuscator:string-array-threshold: <number>

I need some part code more obfluscated than other parts, but still I want smaller result.
So is possible add changing string-array-threshold for some part source?
Thanks

Very unique and rare case. Right now i don't see any reason to add this.


Create Grasshopper examples

Create examples for user to get started (and explore possibilites) with the API.
To start with, all the examples should be made for Grasshopper. Preferably all examples should have an equivalent in C#, Dynamo as well, but for now only the most basic examples should be created.
Instructions on getting started

[x] (Maybe) Update README.md installation section, if something is unclear.

Basic examples to implement (Scripts)

[x] Example 1: Creating a simply supported beam with supports, loads, loadcases - prio 1
[x] Example 2: Analyse a simple model - prio 1
[x]  #253
[x] #202
[ ] #257
[ ] #258
[ ] #266
[ ] To be added

Practical examples to implement (Scripts)

[x] Creating a parametric bridge model similar to this - prio 1 See attached specification below

http://blog.rhino3d.com/2021/10/parametric-bridge-design-online.html
https://sofistikforyou.com/challenges-of-bridge-design-and-detailing-in-autodesk-revit/
Exempel Bro Specifikation.docx
[ ] Bridge with complex load combinations and load groups. Crack analysis.
[ ] Reading and writing data to excel. Piling. Read piling report with actual pile coordinates (in SweRef) and update the supports to actual positions.
[ ] Create an example generating a simple plate (balcony?) and loads, running analysis and deciding reinforcement (iterative analysis)
[ ] Mapping between Revit/FEM Design (already started)
[ ] Example with iterative analysis in Grasshopper, using maybe Anemone or similar (for users who don't know C#)

Wishes from customers

[ ] Reading results
[ ] Adding elements to an existing model
[ ] Railway noise barriers
[ ] Basic piling situation

Possible examples (to be considered)

[ ] Approximating the functions of the FEM-Design load macros (wind, snow, moving load etc)
[ ] High rise building with varying wind load

I think we need to have

Basic examples for understanding and learning how to use the API
Practical examples on what you actually want to do with the API, "real world problems"

Some (relatively simple) real world problems should be prioritized as they explain why you should even use the API

@xRadne and @samnyb , I guess we should update examples to FD 21 version. Because they were made for FD 20 right?

I agree! However it is not required since the API is backward compatible, meaning all grasshopper scripts made in v20 can be used with API v21.
The same goes for Dynamo.
But not C#, but it will give clear hints on what needs to be fixed,

I agree! However it is not required since the API is backward compatible, meaning all grasshopper scripts made in v20 can be used with API v21.
The same goes for Dynamo.
But not C#, but it will give clear hints on what needs to be fixed,

Include this in documentation #35. Ping @andosca

@samnyb I think the About component #189 should be added to all scripts as well.

@xRadne and @samnyb , I guess we should update examples to FD 21 version. Because they were made for FD 20 right?

@samnyb I think the About component #189 should be added to all scripts as well.

I'll put both these things on my to-do-list!

I agree! However it is not required since the API is backward compatible, meaning all grasshopper scripts made in v20 can be used with API v21.
The same goes for Dynamo.
But not C#, but it will give clear hints on what needs to be fixed,

Include this in documentation #35. Ping @andosca

There is not any clear distinction between FD21 and FD20. For now it is backwards compatible as no xml-schema changes were introduced.

Is it really backwards compatible all the way? I thought some components may have a changed number of inputs or have some changes, making it necessary to replace them.  I think it would be nice at least to check that they work in FD 21

Is it really backwards compatible all the way? I thought some components may have a changed number of inputs or have some changes, making it necessary to replace them. I think it would be nice at least to check that they work in FD 21

If the grasshopper plugin is not backwards compatible. It's a bug. The components we have changed should be functioning but marked as OLD.

@xRadne and @samnyb , I guess we should update examples to FD 21 version. Because they were made for FD 20 right?

@samnyb I think the About component #189 should be added to all scripts as well.

I'll put both these things on my to-do-list!

[ ] Checked all examples for OLD components
[ ] Added About component to all examples

Possible improvement of bridge example: using the Perp Frames component instead of orienting planes along axis. Cuts 7-8 components per flange. I haven't tested if it's a complete match in functionality though, so I'll have to get back to it at a later point.

22/03/16: Add Python filepath component to all existing examples

[ ] Example 1
[ ] Example 2
[ ] Example 3
[ ] Example 4
[ ] Example 5
[ ] Example 6 (in progress)
[ ] Potentially the Bridge example

2022-03-24: Load combination factors apparently in wrong order in example 2.

[ ] Check example 2
[ ] Check other examples for similar error

We should create these examples in C# as well. These examples should be equivalent so that a user familiar with one framework could easily compare c# to grasshopper (and eventually python and/or dynamo)

We have initiated the process of migrating examples form FemDesign.Samples to a future directory called FemDesign.Examples. Progress on this is mapped in #203.

@xRadne when you have time, I would like to merge branch 34 to master to set Example 7 in the right folder, and also rebase (?) branch 34 so the new structure is applied there as well, and all duplicate files removed. I still feel a little unsure around merging, so I would like your support, as well as a green light of the whole process, of course.

@xRadne when you have time, I would like to merge branch 34 to master to set Example 7 in the right folder, and also rebase (?) branch 34 so the new structure is applied there as well, and all duplicate files removed. I still feel a little unsure around merging, so I would like your support, as well as a green light of the whole process, of course.

Example 7 added to master branch


Bug Report: 'Reload NRCS Data' results in an error

About me
This bug report is posted on behalf of the BBC
Observed Behavior
Clicking 'Reload NRCS Data' from the Sofie timings bar results in an error message appearing and an error being logged in Core.
Doesn't matter if the rundown is active or inactive in Sofie.
This is with MOS Gateway, unknown if this affects other ingest methods.
{"level":"info","message":"UserAction \"resyncRundownPlaylist\" failed: UserError: {\"rawError\":\"errorClass: Error: Rundown \\\"kneAzthqifY_ezDsJvNosujBCcY_\\\" does not have a peripheralDeviceId [500], Error: Rundown \\\"kneAzthqifY_ezDsJvNosujBCcY_\\\" does not have a peripheralDeviceId [500]\\n    at server/api/ingest/lib.ts:120:9\\n    at /opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\\n => awaited here:\\n    at Function.Promise.await (/opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\\n    at server/api/ingest/actions.ts:19:15\\n    at /opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\\n => awaited here:\\n    at Function.Promise.await (/opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\\n    at server/api/rundown.ts:46:14\\n    at /opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\\n => awaited here:\\n    at Function.Promise.await (/opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\\n    at server/api/rundown.ts:42:18\\n    at /opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\\n => awaited here:\\n    at Function.Promise.await (/opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\\n    at server/api/client.ts:242:18\\n    at /opt/core/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\",\"message\":{\"key\":\"An internal error occured!\"},\"key\":0,\"errorCode\":500}"}

Expected Behavior
A suitable MOS message should be sent (E.G. roReq) to re-request the RO.
Version
release51
Severity / Impact
Not a significant issue at this time

After discussions on Slack it appears that running: Meteor.call('debug_playlistRunBlueprints', 'kneAzthqifY_ezDsJvNosujBCcY_') breaks the reload process.
I'll leave this issue open for NRK to decide if this is something that should be fixed or not...

We had a quick chat about this one in the Sofie Team.
Since debug_playlistRunBlueprints is an internal debugging function we won't spend time on fixing it, but if anyone else would open a PR with a fix, we'd be happy to accept it.


Support common documentation formats

[ ] #141
[ ] #918
[ ] #919
[x] #920
[ ] #921
[ ] #922

Examples of the different formats: https://realpython.com/documenting-python-code/#google-docstrings-example

pyment can detect the used documentation format: https://github.com/dadadel/pyment/blob/2c10b1c64093adbce8db369a3db4321e6c3c7c32/pyment/docstring.py#L647

pdoc might also be helpful for this.


Implement a log collection service

Need to implement a service which is responsible for collecting logs from a Rancher Environment.

closing in favor of #8939


rest token enhancement

Jacopo: nice work!
I'd like to see your authorization system integrated with laravel-auth-token https://github.com/tappleby/laravel-auth-token for ReST support.
The next version is working on JWT support, which is part of the OpenID Connect standard, and plays well with OAuth 2.
There are some Open Source dashboards in JavaScript, if & when you get to that point.

Not planning that for now.


windows: panic on sign-out

Describe the bug
tun_windows.rs panics on sign-out sometimes
To Reproduce
Sign out
Expected behavior
Shouldn't panic
Screenshots / Logs

Platform (please complete the following information):

Firezone Version 606ab3ff3
OS: Windows 11

Additional context
None

I see the fix was merged. This bug doesn't always replicate depending on where that worker thread is, but I'm pretty sure I had the right root cause, so I'll close this. I tested it once and it signed out cleanly:


Update to Smack 4.5.0-beta2

The new Smack beta has dropped some old API. This commit adjusts our code accordingly.
Sadly, one of the tests that ship with Smack now fail (see https://github.com/igniterealtime/Smack/pull/630 ). That test has been disabled in the CI for this project.

Asking for forgiveness instead of permission: Merging this to be able to rebase https://github.com/XMPP-Interop-Testing/smack-sint-server-extensions/pull/41 onto this


full data request

Hi! When could you offer the full 11000 datasets?

Additional data releases are expected mid this year (due to the removal of sensitive information).

Any updates on this? Thanks in advance!

Same here. It would be great to have full dataset.

any updates on this?

It has been than an year and the complete dataset has still not been released. Can you please share the link for the complete dataset.

@him1411  Can you help me how can I use datasets on my Node project?
I need to scan France receipts. So many types of document are there.


How to give opacity to child route page so?

How to give opacity to child route page so that previous page shows transparently.
I've tried giving Opacity() widget at the top and won't work as expected.

Above screen should be transparent.

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v0.5.7, on Mac OS X 10.13.6 17G65, locale en-KR)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[!] VS Code (version 1.25.1)
[✓] Connected devices (3 available)

You have to create your own PageRoute/MaterialPageRoute subclass with the following override:
class _TransparentPageRoute<T> extends MaterialPageRoute<T> {
  ...
  @override
  bool get opaque => false;
}

Now push this route to the navigator:
Navigator.push(context, _TransparentPageRoute(builder: ...));

@sir-boformer builder isn't defined in _TransparentPageRoute

Well, implement it ;)
class _TransparentPageRoute<T> extends MaterialPageRoute<T> {
  _TransparentPageRoute({
    @required WidgetBuilder builder,
    RouteSettings settings,
    bool maintainState,
    bool fullscreenDialog,
  }) : super(
          builder: builder,
          settings: settings,
          maintainState: maintainState,
          fullscreenDialog: fullscreenDialog,
        );

  @override
  bool get opaque => false;
}

@sir-boformer Hi. Thank you for help. However, I am facing assertion error trying your code.
'package:flutter/src/material/page.dart': Failed assertion: line 87 pos 12: 'opaque': is not true.
#0      _AssertionError._doThrowNew (dart:core/runtime/liberrors_patch.dart:37:39)
#1      _AssertionError._throwNew (dart:core/runtime/liberrors_patch.dart:33:5)
#2      new MaterialPageRoute (package:flutter/src/material/page.dart)
#3      new _TransparentPageRoute (file:///Users/hyochan/Documents/SourceCode/FlutterProjects/foodieon/lib/screens/profile.dart)
#4      ProfileState._switchToHost (file:///Users/hyochan/Documents/SourceCode/FlutterProjects/foodieon/lib/screens/profile.dart:247:29)
<asynchronous suspension>

Below is where I see assertion.
class MaterialPageRoute<T> extends PageRoute<T> {
  /// Creates a page route for use in a material design app.
  MaterialPageRoute({
    @required this.builder,
    RouteSettings settings,
    this.maintainState = true,
    bool fullscreenDialog = false,
  }) : assert(builder != null),
       super(settings: settings, fullscreenDialog: fullscreenDialog) {
    // ignore: prefer_asserts_in_initializer_lists , https://github.com/dart-lang/sdk/issues/31223
    assert(opaque);
  }

Maybe try to extend PageRoute or ModalRoute. Or remove the assertion manually and see what happens.

Support questions like this are probably better asked on StackOverflow.

@hyochan Have a look here, I have answered the question on Stack Overflow: https://stackoverflow.com/questions/54572107/transparent-pageroute-in-flutter-for-displaying-a-semi-transparent-page 😉


generic stub implementation

And a command line tool using generic stub to talk to rpc server (only for unary call).

The code looks good, and it's nice to have a CLI tool. Can you test it? I know it's not as easy to test as some of the other tools, but it would be nice to have an actual automated test here.

Excellent.


Adding C++/WinRT Wrapper Name Change to Release Branch

Related Issue
Moving the name changes to release branch for the bookkeeping purposes.
How Verified
Verified manually by integrating it via nuget.org feed.

Is this a Cherry-pick? If so, can you link to the original pull request?

Is this a Cherry-pick? If so, can you link to the original pull request?

Added CP


Updated height provider code to be a closure,

Allows for more flexibility in specifying a custom height. Also happens to fix a potential memory leak.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fa2d3ad). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #191   +/-   ##
=========================================
  Coverage          ?   93.41%
=========================================
  Files             ?       40
  Lines             ?     4392
  Branches          ?      359
=========================================
  Hits              ?     4103
  Misses            ?      288
  Partials          ?        1

Impacted Files
Coverage Δ

Source/Bricks/Generic/GenericBrick.swift
99.32% <100%> (ø)

Continue to review full report at Codecov.

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


OrdinalRange vs UnitRange

https://github.com/control-toolbox/CTBase.jl/blob/d9b6cd6c27dd125c60f9e8e9f57eeb7eb9e9aa92/src/model.jl#L179
OrdinalRange seems more adapted because it contains both StepRange and UnitRange

With OrdinalRange we can have things like 1:2:5.

@BaptisteCbl nice idea. Please fork this taking into account side effects, e.g. additional matches needed in constraint-type](xxxxx):
constraint_type(e, t, t0, tf, x, u) =
    @match [ has(e, x, t0), has(e, x, tf), has(e, u, t), has(e, x, t), has(e, u, t0), has(e, u, tf) ] begin
        [ true , false, false, false, false, false ] => @match e begin
            :( $y[$i:$j]($s) ) => (y == x && s == t0) ? (:initial, i:j     ) : :other
            :( $y[$i   ]($s) ) => (y == x && s == t0) ? (:initial, Index(i)) : :other
            _                  => (:boundary, replace_call(e, x, t0, Symbol(x, "#0"))) end

@BaptisteCbl Hi, what about this issue?

Hello, I made the changes in a new branch unit-to-ordinal, I will make sure I did not forget any side effects and make a pull request in the next days.


Prevent duplicate variant and option names

closes #632

Coverage decreased (-0.02%) to 27.537% when pulling<PHONE_NUMBER>fddf4671e36e0751ff36f5a38b6f35 on variants into 3ee63695e65f844a41b0a9b07a3cade0ff033b02 on master.


envdir not working with virtualenvs properly? daemontools behaves correctly

hi @jezdez, it seems envdir is modifying the PATH in some unexpected way when using virtualenv. daemontools seems to be working as expected.
I have a pretty vanilla set up using pyenv and virtualenvwrapper. Nothing fancy.
setup:
$ deactivate
$ mkvirtualenv test
$ deactivate

with jezdez/envdir:
$ workon test
$ which python
/Users/johria/.virtualenvs/test/bin/python
$ envdir envs/prod which python
/Users/johria/.pyenv/versions/3.6.1/bin/python

^^^^ error is here ^^^^
uninstall jezdez/envdir, install daemontools:
$ deactivate
$ pip uninstall envdir
$ brew install daemontools

with daemontools:
$ workon test
$ which python
/Users/johria/.virtualenvs/test/bin/python
$ /usr/local/bin/envdir envs/prod which python
/Users/johria/.virtualenvs/test/bin/python

Thanks for the repost.
NOTE: you are using pyenv apparently, and maybe even pyenv-virtualenvwrapper.  So two additional failure points.

If you're using pyenv, why does which python not point at ~/.pyenv/shims/python?

I'm using pyenv and vanilla virtualenvwrapper. @blueyed it does point to the shim python before I go into the virtualenv. The virtualenv adds it's own python to the beginning of the path.

I'll add some more debug output I can think of when I get to my laptop.

@blueyed I uninstalled pyenv and tried again. It seems to be a pyenv issue. Here is more specifically what's happening:
no subshell
$ echo "$PATH"
bin:/Users/johria/.nodenv/shims:/Users/johria/.rbenv/shims:/Users/johria/.pyenv/shims:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

in subshell, same path
$ sh -c 'echo "$PATH"'
bin:/Users/johria/.nodenv/shims:/Users/johria/.rbenv/shims:/Users/johria/.pyenv/shims:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

in subshell with envdir, changed $PATH
$ envdir envs/prod sh -c 'echo "$PATH"'
/Users/johria/.pyenv/versions/3.6.1/bin:/usr/local/Cellar/pyenv/1.1.1/libexec:bin:/Users/johria/.nodenv/shims:/Users/johria/.rbenv/shims:/Users/johria/.pyenv/shims:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

pyenv is somehow adding two more folders on to the PATH when interacting with envdir. probably out of scope here but I'd appreciate any ideas for debugging further.

Another note: if envdir is installed inside the virtualenv, there are no issues.

I think the issue can be simplified down to:
$ which python
/Users/johria/.pyenv/shims/python
$ envdir envs/prod which python
/Users/johria/.pyenv/versions/3.6.1/bin/python

Still perplexing. I don't think any of my startup shell scripts are a culprit because if pyenv init ran properly it would go right back to the shims path.

It seems like I found the issue. Python itself is modifying the path when the python executable gets run.
$ echo "$PATH"
/Users/johria/.pyenv/shims:bin:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

$ python -c "import os; print(os.environ['PATH'])"
/Users/johria/.pyenv/versions/3.6.1/bin:/usr/local/Cellar/pyenv/1.1.1/libexec:/Users/johria/.pyenv/shims:bin:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

This only occurs with pyenv. With homebrew python:
$ echo "$PATH"
bin:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

$ python -c "import os; print(os.environ['PATH'])"
bin:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin

No changes to the PATH. The pyenv wrapper shim is doing the addition to the PATH!
SO. In conclusion, when envdir is installed globally via pyenv, the pyenv shim is injecting variables on to the PATH. When inside a virtualenv, the shimmed envdir ends up changing the PATH so its no longer using the virtualenv but instead its using the global python.

@AlJohri yeah, overall virtualenvs barely "exist," they are mostly about the modification to $PATH (see here for a good post about this). I recently learned more about this dealing with the interaction between pyenv and the wonderful (newish) Python package manager, poetry.

Anyways the envdir code of interest is https://github.com/jezdez/envdir/blob/master/envdir/runner.py#L79
To find a universal solution could be hard; for some people shell=True may be appropriate, others not. Judgment calls...

Tangential:
I'm beginning to think about writing a new utility, envdir in pure shell with just a dependency on env. It would have disadvantage vs Python envdir in not being compatible with non-sh/bash/zsh-like shells (like fish), but would possibly have the advantage of guaranteed consistency with the shell you call it from.

@hangtwenty
Just a quick side offtopic note, I am using the following shell function to export envdirs (zsh):
envdir-export () {
	setopt extendedglob
	local envdir=$1
	if ! [ -d "$envdir" ]
	then
		echo "$envdir is not a dir."
		return 1
	fi
	for i in $envdir/*(.)
	do
		if [[ "${i:t}" == *.* ]]
		then
			continue
		fi
		echo "Exporting $i:t"
		eval "export ${i:t}='$(<$i)'"
	done
}

I call this for example via autoenv (https://github.com/Tarrasch/zsh-autoenv) for projects, or manually on certain dirs to get extra parts of some config.


Skip frontend build where unnecessary

The testing pipelines and build-backend steps do not depend on frontend files, skip their build for them.

looking at CI it do not realy short time a lot but it's still a good idear

You'll notice build steps in the integration pipelines gone down from 3-4m to around 1-2m.

We could also create an docker image go-nodejs to speed up ci.

Such a image would not gain much, Node.js installation is like 40s currently including curl. The bulk of the CI time is spent in the go linter, integration tests and various cross builds.

@lunny Creating a docker image should solve our tmpfs problem!

@guillep2k https://gitea.com/gitea/build

@guillep2k https://gitea.com/gitea/build

Superb! I'll try to play with this when I get some free time.

My only worry about such a image is that it needs to be constantly be updated/rebuild to track upstream changes. Do you plan on having any automation for that?


Fix iot-installer build via the cloud API

8fdd1587997dbf091dd69a426bb44ef1c9abcfd1 modified the Cloud API to resolve
ostree commits using a separate job. This change caused the API handler
to call PackageSets without any ostree options (because they are not resolved
yet).
Unfortunately, the new implementation of PackageSets initializes the manifest.
The initialization checks the options and if the type is iot-installer and
it doesn't have the fetch checksum for IoT, it just returns an error.
To work around this (we need an initialized manifest to create the chains),
this commit just gives the initialization method a dummy checksum. The ostree
options currently don't have any effect on the package sets, so this should
be fine.
In order to make this workaround at least slightly sane, a warning is printed,
there's a new test just for this behaviour and a long comment to remember to
delete these lines.
Fixes #3125
This pull request includes:

[x] adequate testing for the new functionality or fixed issue

Your typo concerns were fixed. :)


Splitting dataapi into separate components

It would make it easier to deploy on another platform the ooni data api together with the measurement API if the components that need read only access to the DB were separated.
This issue is about splitting those out into separate components to work towards a better isolation of the mission critical vs essential components.
This is about taking all the public endpoints related to read only access to measurements and putting them on their own API.

This has been done and a more detailed plan for the next steps can be found here: https://github.com/ooni/backend/issues/807


Add tsc linting

Codecov Report

Merging #31 (0638b72) into master (dd3f051) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #31   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           49        49
  Lines          971       971
  Branches       215       215
=========================================
  Hits           971       971

Flag
Coverage Δ

root
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Installing dependencies for a node.js project

Hello,
I'm trying to install node dependencies for a node.js project. I don't want to install them globally, I just want them to be available in the project directory.
I have this:
  include nodejs::v0_10
  exec { 'update npm deps':
    command => "${nodejs::nodenv_root}/bin/nodenv exec npm install .",
    cwd => $repo,
    provider => 'shell'
  }

But when I try to update, I get an error:
Notice: /Stage[main]/Projects::Drbot/Exec[update npm deps]/returns: nodenv: no versions of NodeJS are currently installed

How do I configure a particular node version to be active so that I can execute node commands during a puppet configuration?

Closing due to inactivity. Please mention me if this is still an issue.


Line height of suggestion details pane is too small when font size is large.

VSCode Version: 1.51.0
OS Version: Arch Linux (kernel 5.9.6)

Line height of suggestion details pane is too small when font size is large. If font size is medium or small, this looks OK.
When font size is "15":

When font size is "19":

VS Code 1.50.0 doesn't has this problem.
Steps to Reproduce:

Set the "font size" to a large value, e.g. "19".
Edit a file which supports suggestion, then type something which will trigger the suggestion details pane.

Does this issue occur when all extensions are disabled?: Yes

@g-plane What font are you using?

I can reproduce with editor.fontSize being 19 or above. Is that what you are doing? This isn't with having the suggest font size configured, right?

What font are you using?

I'm using Jetbrains Mono.

This isn't with having the suggest font size configured, right?

Yes. I don't configure that.

/verified


Out-of-date links to online Vim documentation

According to these commits:
https://github.com/c4rlo/vimhelp/commit/565fe830fa62e2760cfb28975617e469631fb32f
https://github.com/c4rlo/vimhelp/commit/115ce1c1b802ed7a825e032f3a38831730959df2
https://github.com/c4rlo/vimhelp/commit/54bc151a06e231190e7f670d856128ed0296679e
The current URL for the online Vim documentation is https://vimhelp.org
The old links are present in these pages:

https://www.vim.org/docs.php
https://github.com/vim/vim/blob/12ee7ff00b91d852e060bb24951d1c94239863eb/runtime/doc/intro.txt#L68
https://github.com/vim/vim/blob/12ee7ff00b91d852e060bb24951d1c94239863eb/runtime/doc/syntax.txt#L3143

The appspot links still work, but linking to vimhelp.org is nicer, thus I'll use that.

Oh, I didn't know that there exists a vimhelp.org domain. I only knew about vimhelp.appsport.com (which still works). Good to know.

this seems fixed, so closing.


Building a standalone parser

I'm sorry if this is covered somewhere in the docs, I honestly tried hard to find the answer online... but is it possible to build an Ohm parser into a zero-deps JS module like what you get if you do "Download parser" at https://pegjs.org/online?

Hi - sorry for not replying sooner. No, this is not something that Ohm directly supports. However, you could do it yourself by using a bundler like Rollup or esbuild.


[WIP] Inline inventory

Fix for #201

Thank you for your PR. They're always welcome. I did however want to check I'm thinking of the same use case. Are you intending to have a user provide a per-job inventory by manually entering the information, or are you setting the inventory in the job configuration?
In either case, this PR seems to address the case when the Rundeck inventory is not used at all to determine which nodes to target. The file copier, node executor, inline workflow node and workflow node plugins all rely on the Rundeck inventory. I don't think it wise to provide a separate inventory to these plugins. The module workflow, inline workflow and workflow plugins do make some sense here.

The idea is to provide an Ansible inventory, independent of the Rundeck inventory, inline (so per job, in the job configuration) for use cases where you want the user to modify the inventory by having access to the Rundeck instance, but not to the underlying file system.
I agree that it is not very useful for file copier, node executor, inline workflow node and workflow node; I'll rework the PR.

May we considder beeing able to also overlay the inventories ?
Usecase:
As a Job developer, i want to group my Servers for use in an Ansible Playbook but the specific groups used are only needed for this single Job. I want to group my Servers or define them for this job, without changing the global Inventory definition which would introduce unnececary groups to all Playbooks while only needed by one. But i also want to keep variables/information defined in the global inventory.
CLI Equivalent:
ansible-playbook -i localinventory -i /etc/ansible/hosts myplaybook.yml
Ansible supports overlaying Inventorys. It will automatically merge them.
https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html
I am not sure if that would be possibe with the current WIP implementation.
In the Code of the AnibleRunnerBuilder the Inventory gets returned once so i think it is either inline or global. We could merge both files ourself depending on a checkbox state.

replaced by  #318