UX/UI: align "Send" screens

Is your feature request related to a problem?
Currently all "Send" screens look similar but different. This is partly related to different info that is available to be displayed and partly to code-inconsistencies.
Describe the solution you'd like
A general solution which can be used for all these screens.
This will hopefully:

align the UI/UX
reduce code because we can re-use the same "component" for all screens

Are you working on this?
No
Screenshots

Keysend (payment directly to a node)

Start (non-prompt)

Success (non-prompt only)

Withdraw

Start (prompt)

Start (non-prompt)

Success (non-prompt only)

Channel

Start (prompt)

Start (non-prompt)

Success (non-prompt only)

- nodeId can be rather long
- k1 is "random or non-random string to identify the user's LN WALLET when using the callback URL"

Auth

Start (prompt)

Start (non-prompt)

Success (non-prompt only)

Confirm payment

Start (prompt)

Start (non-prompt)

Success (non-prompt only)

LNURLPay

Start (prompt)

Start (non-prompt)
-
-
Success (non-prompt only)

Relates to #1197

Current draft ideas

No image for actions pasted directly via "Send"
Header same size but with no image
Keysend "long" key will get cut off via "..."


Mentioning IOS Press as a data publisher that uses YASGUI

Hi,
We just launched our linked data portal LD Connect at http://ld.iospress.nl and we are using YASGUI as our Query interface at http://ld.iospress.nl/query-interface/.
We would like to attribute YASGUI, and would like to ask if there is any particular format we should follow?
If possible, it would be great to be included in your list of data publishers in your "Used by many" section in your README.md as well.
Thanks!
Stephanie

Hi @s-delbecque,
Thanks for using YASGUI!  I'll add it to the list of publishers in the README file.
If you want to attribute YASGUI on your site, its best to refer to the main YASGUI paper, which was published by IOS Press (Semantic Web Journal): Rietveld, Laurens, and Rinke Hoekstra. "The YASGUI family of SPARQL clients 1." Semantic Web 8.3 (2017): 373-383.

PS: When I download the N-Quads datadump, the file seems to end in the middle of a triple/IRI.  Could it be that the file is only partially uploaded?

Hi @wouterbeek
Thanks!!
Ok, great, we'll refer to the SWJ paper!
Thanks for the feedback of the N-Quads datadump. I tested it on several browsers and devices, without any problem. Could you give me some context of where it went wrong with your download, so we can have a closer look?
Thanks!

@wouterbeek
Both file sizes and lines are correct and last bit got fixed. Will have a look at the macOS files as well!
Thanks for your feedback!


Loading icon or greyed save button when saving a record in show all data screen

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
Loading icon or greyed save button when saving a record in show all data screen
Describe alternatives you've considered
Additional context

Hi @CamilleGuillory ,
How about that ?

Hi @tprouvot
Yes that's good
Even better if the blue button can become grey / disable once you click on it :)

Hi @tprouvot Yes that's good Even better if the blue button can become grey / disable once you click on it :)

Oh @tprouvot, thank you. The greyed icon and the disabled button are perfect. I couldn't have asked for more... Or could I? 😈


Mutation productImageCreate doesn't validate file extension

The mutation productImageCreate which is used to upload product images from the dashboard doesn't validate file extensions. Now it is possible to upload e.g. an audio file.

I think we should be validating MIME types and not just file extensions?

Yes, that would be a more reliable way.


Typescript support

I'm going to install victory-native module in typescript. I'm not able to find @types/victory-native when I try npm install @types/victory-native.
What should I do for typescript?

https://github.com/FormidableLabs/victory/issues/1033 helped me out. That issue was opened after this one, but it seemed to get more attention.

To use the victory types as victory-native types, you can write
declare module "victory-native" { export * from "victory" }

in the file victory-native.d.ts under local_types.

@pvinis you can hack it like so:
declare module "victory-native" {
  export const VictoryThemeDefinition: any;
  export * from "victory";
}

Hi,
Obviously, At the moment they do not support the library for ts, but you can ignore ts-list when you put
this line: //@ts-ignore before including the library.
Example:
//@ts-ignore
import { VictoryPie, VictoryLabel, VictoryGroup } from 'victory-native';

Best,
D. Hristov

Hi,
Obviously, At the moment they do not support the library for ts, but you can ignore ts-list when you put
this line: //@ts-ignore before including the library.
Example:
//@ts-ignore
import { VictoryPie, VictoryLabel, VictoryGroup } from 'victory-native';

Best,
D. Hristov

Using @mrded suggestion I've written out a full example/comment.

@emarx Where is local_types? And from where does the victory-native.d.ts come from, iiuc we have to add @types/victory?

You need to install the definitions for vicrtory by doing yarn add --dev @types/victory, then create a new def file,  under /typing/victory-native.d.tsthen you add the line that @emarx suggested:declare module "victory-native" { export * from "victory" }`


Return 404 response when Rules and/or key is unknown

Looks like it is failing on oracle now :(

Looks like it is failing on oracle now :(

More fun with column cases :roll_eyes:. I've fixed by forcing lower-case with quotes so that we don't need to modify the tests themselves.

Integrated into main, thanks @ryanemerson !


Pin the buildpack versions in heroku/buildpacks:18

Since the heroku/buildpacks:18 CNB builder image is based upon the Heroku-18 stack, which has reached end-of-life, and as such support will soon be removed from the stack from our various buildpacks.
We will soon be stopping the publishing of heroku/buildpacks:18 image updates entirely, however, we expect a few more upstream security updates to Ubuntu 18.04 (until 31st May, Canonical's revised EOL date) which we wish to pick up in the meantime.
By pinning the buildpack versions of our shimmed buildpacks, it unblocks removing Heroku-18 support from them in the meantime.
To pin the version, we rely on the fact that the buildpack registry stores versioned archives of each buildpack release, with a vNNN suffix.
The latest version numbers of each shimmed buildpack were generated using:
$ for lang in scala gradle ruby python php go; do echo "${lang}-v$(h buildpacks:versions heroku/${lang} | head -n3 | tail -n1 | cut -d ' ' -f 2)"; done
scala-v96
gradle-v39
ruby-v271
python-v232
php-v230
go-v173

GUS-W-13143718.

CI is failing with:
ERROR: failed to add buildpacks to builder: invalid buildpack: buildpack from URI 'https://cnb-shim.herokuapp.com/v1/heroku/scala-v96?version=0.0.0&name=Scala' has ID 'heroku/scala-v96' which does not match ID 'heroku/scala' from builder config

This is because cnb-shim infers the buildpack ID from the registry URL, and it's (understandably, given we're trying to trick the URLs) treating the -v96 in the URL as part of the buildpack name and not the version.
To resolve the error we would have to either:

Switch the IDs that we call the buildpacks - which is potentially a breaking change (given people may be using eg --buildpack builder:heroku/scala or whatever that syntax is) plus kinda meh for UX in build logs.
Or, update cnb-shim so that it allows overriding the ID via a URL parameter (the same way it allows overriding other attributes), or else so that it knows to strip off any -vNNN suffix.

Option (2) seems marginally better, however, I'm not sure it's worth the effort given that we could also just stop publishing new updates to heroku/buildpacks:18, given that when builds occur a fresh run image will be pulled in. (So any updates to the run image itself will still be picked up, even if we're not updating the builder image.)

I've decided to go with option (2) after all:
https://github.com/heroku/cnb-shim/pull/71


How to clear diagnostic when the file is closed.

How can i clear the diagnostic info when the file is closed with LanguageClient? I can get the didClose info with middleware, but how can i remove the diagnostic in IDE? Hope for your help. Thanks a lot.
const clientOptions: LanguageClientOptions = {
  diagnosticCollectionName: 'test',
  middleware:{
    didClose:{xxx}
  }
}

You can do that from the server as  well. Simply push diagnostics using an empty array.

You can do that from the server as well. Simply push diagnostics using an empty array.

Is there any methods used in LanguageClient to realize this function? The editor can get the didClose info and clear will be implied on the client side. After the file is closed, there is no need to send the request on the server side

didClose is a notification rather than requests.

Yes, that is correct. You can still push an empty diagnostic array using the same notification you used to push the initial diagnostics.


Use a fixed maximum for the Y scale of the elevation profile, based on a

map's max height. This helps compare elevation profiles before/after map
edits.
Example of a comparison now:

Dividing the max value by 3 is still quite unfortunate...

I'm going to try a few more changes for the x axis and # buckets, so just a draft

Alright, this now attempts to scale the X axis as well, with more rounding behavior to cover miles.
I like the idea of showing the before/after profile in one plot, but we can leave that as future work. It's also worth noting Yuwen has a design for integrating the elevation data even more:

So the question becomes: is this PR at least an incremental improvement? Is the rounding behavior for Distance sane?

I like the idea of showing the before/after profile in one plot, but we can leave that as future work. It's also worth noting Yuwen has a design for integrating the elevation data even more:

Yuwen's design looks good!
I'd be interested to see if it can be tweaked to accommodate a before vs. after aspect, or if the elevation comparison should remain a separate widget.

Thanks for the review!

I'd be interested to see if it can be tweaked to accommodate a before vs. after aspect

I could imagine it gets hard, since it's more integrated with the trip timeline. Comparing timelines could also be useful, but overlaying two of those probably wouldn't work.


Feature: support kexts

We can list kernel extensions too.

Fixed in https://github.com/hazcod/maclaunch/commit/d9379df0a6845c25ec7b8420e390b98686162481


Add size badge

Hi (salut),
A small PR to advertise the size of you library using https://github.com/ngryman/badge-size.
I can change it to display the gzip version if you want.

Sure why not, thanks for the PR!


Add option to reset value on operator change

I was running into an issue as seen below:
Let's say we have a field named hobbies, which can be ["Football", "Soccor", "Fishing", "Programming", "Filmmaking"]
Now, I want there to be two operators possible on this field:
{name: '=', label: 'is'} and {name: 'beginsWith', label: 'begins with'}
I have set the is operator to return a "select" valueEditor, and the beginsWith to return a "text" valueEditor.
Here is the bug that would occur:
Let's say I type "F" while the beginsWith operator is set, then change the operator back to is (which will display a select element now). The rule's value would still remain as "F" in the query, until the user changes the select dropdown's value.
The option I have added in this PR allows you to specify that the rule's value should be reset after changing an operator.
Looking forward to hearing your thoughts! Thanks

Codecov Report

Merging #126 into master will decrease coverage by 0.78%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #126      +/-   ##
==========================================
- Coverage     100%   99.21%   -0.79%
==========================================
  Files          13       13
  Lines         252      254       +2
  Branches       23       24       +1
==========================================
  Hits          252      252
- Misses          0        1       +1
- Partials        0        1       +1

Impacted Files
Coverage Δ

src/QueryBuilder.jsx
97.93% <0%> (-2.07%)
:arrow_down:

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 69270ef...9711c38. Read the comment docs.

I could also update the demo app to reflect such a use case, if you'd think it would be helpful!


Fix counter_wb test & Makefile cocotb-verify-* regex

This PR fixes 3 things:

Test example "counter_wb" fails due to timeout: Timeout increased, and test tidied a little.
Minor error in regex for cocotb-verify-* in Makefile prevents running any test that ends in the letter c
.gitignore updated to exclude venv-cocotb (per #373 ).

I'm not authorized to merge, Anton.
I looked over the changes and don't see anything obvious, but asked Marwan to review, too.


Add BT only note to regional

Proposed changes

Merge timing

Related issues (optional)
Closes #4448

@markzegarelli is this gtg?


ebitenutil: DebugPrint ignoring image origin

Ebitengine Version
v2.7.2
Operating System

[ ] Windows
[ ] macOS
[ ] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] PlayStation 5
[ ] Xbox
[ ] Web Browsers

Go Version (go version)
go1.22.2
What steps will reproduce the problem?
Using ebitenutil.DebugPrint() on an image with non-zero origin.
What is the expected result?
Text drawing on the top left.
What happens instead?
Text being cut or not visible.
Anything else you feel useful to add?
E.g., see https://github.com/hajimehoshi/ebiten/blob/v2.7.2/ebitenutil/debugprint.go#L48C3-L48C32 trivially replace with:
bounds := image.Bounds()
DebugPrintAt(image, str, bounds.Min.X, bounds.Min.Y)

I mean, I'm unsure of the exact desired behaviors, in some cases DebugPrintAt() might also need some changes, in which case the fix would be more involved?

I feel like this is an expected behavior.

I feel like this is an expected behavior.

Yes, I think it's for the same reason that if you do DrawImage to a sub-image, you also have to translate the origin of the destination sub-image explicitely.

I mean, the documentation says:

DebugPrint draws the string str on the image on left top corner.

There are two possible interpretations of this:

"[...] draws the string on image's top-left corner", in which case, top-left corner is the image's origin, and the function description doesn't match its current behavior, as an image origin is image.Bounds().Min.
"[...] draws the string on image, at coordinates (0, 0)", in which case, the current documentation is very ambiguous and easy to misinterpret. Notice that (0, 0) is not even the top-left corner of the screen, but technically, the top-left corner of the parent of image. So even trying to rewrite as "[...] draws the string on image, on the top-left corner of the screen" wouldn't be technically correct. An alternative description would be "with no translation".

I'm fine with current behavior being the desired one, but I don't think the most reasonable interpretation of the function description matches the current behavior. DrawImage doesn't have this problem, and in fact, you depend on GeoM, which has this explicit documentation:
// The default (zero) value is identity, which draws the image at (0, 0).

So, I think there is no parallel with DrawImage here, this is purely on DebugPrint's description.

Ok so I'd like to update the documentation side.


Automated cherry pick of #6726: fix: keystone event list fail to find user

Cherry pick of #6726 on release/3.2.
#6726: fix: keystone event list fail to find user

Codecov Report

Merging #6727 into release/3.2 will decrease coverage by 0.00%.
The diff coverage is 0.43%.

@@               Coverage Diff               @@
##           release/3.2    #6727      +/-   ##
===============================================
- Coverage         7.03%    7.03%   -0.01%
===============================================
  Files              650      650
  Lines           111812   111837      +25
===============================================
- Hits              7869     7868       -1
- Misses          103334   103361      +27
+ Partials           609      608       -1

Flag
Coverage Δ

#aFlag
7.03% <0.43%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/baremetal/tasks/bm_register.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/ipmiprobe.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/fetch.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/namevalidator.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/opslog.go
1.49% <0.00%> (-0.02%)
:arrow_down:

pkg/cloudcommon/db/scoperesource.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/tenantcache.go
2.96% <0.00%> (-0.32%)
:arrow_down:

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/cloudprovider.go
1.53% <0.00%> (ø)

pkg/cloudprovider/instance.go
0.00% <ø> (ø)

... and 32 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 728494b...6358277. Read the comment docs.


fix: new css added to fix header overlap issues on website

Description
Added CSS to fix the issues with the navigation links not showing the headers when clicking on them (as seen in #631).
Added support for mobile, tablet, and desktop using media queries.
Fix from : https://stackoverflow.com/a/69535686/4018461
Related issue(s)
Fixes #631

@boyney123 When I saw the preview of this PR, I see no changes on every docs page. The navbar still overlaps the heading during scroll. I think what is the major issue is that even adding the classes in style.css is not reflected on the website. I will better recommend you to ask @fmvilas related to this.

@akshatnema Do you mean https://github.com/asyncapi/website/blob/master/pages/_app.js#L23 is not working and CSS file is ignored? I think there are some similar changes already introduced there in style.css

@akshatnema Do you mean https://github.com/asyncapi/website/blob/master/pages/_app.js#L23 is not working and CSS file is ignored? I think there are some similar changes already introduced there in style.css

You can see the changes because I made PR #731 to target this issue. You can see in the PR that it also makes a change in the postcss.config.js to safelist the particular CSS added in the style.css.

Closing as it is fixed already with https://github.com/asyncapi/website/pull/731


Fix broken examples & add a NuxtJS code sample

I presume you can do something similar to [vuex-persistedstate#nuxtjs](https://github.com/robinvdvleuten/vuex-persistedstate#nuxtjs], but I haven't been able to pull it off.

There is an example for Nuxt in examples/nuxt/.
It was added in February 2019, I think you can close this issue.


change the way to get projectId

When I use gitlab and drone, sometimes I cannot activate repository through drone.
I found that specification of repository failed in 'Activate' function.
I added new method below and modify this project.
https://github.com/Bugagazavr/go-gitlab-client/blob/master/projects.go
I really want to use GitLab and drone.

closing this in favor of 0.4 changes that were just merged

@bradrydzewski
Thank you for replying, and merge 0.4.


Conflicts with OhMyZsh macos plugin

I love this kind of thing. Good work.
However, the music function already exists in the macos plugin for Zssh at https://github.com/ohmyzsh/ohmyzsh/tree/master/plugins/macos
I was able to simply change music to amusic in zshMusic.zsh to get it to work.
I would recommend either renaming the music function so it does not conflict with a popular OhMyZsh plugin or contributing your work to the macos plugin as it looks like yours has more functionality.
Also, there is a typo in tthe README - source ~/add-to-your-.zshrc/zshMusic/zshmusic.zsh should be source ~/add-to-your-.zshrc/zshMusic/zshMusic.zsh (capitalize the M).
Thanks for this cool tool!

Yea thats a really good idea, I'll change it to zmusic. Would that work?


ref(installing-workflow): rename workflow-dev to workflow-beta1

closes #129

s/beta1/beta2/g??

Yep. Lemme do that real quick

This has already been updated in master so closing this


Update Public Roadmap with FY25 OKRs & Q1 updates - Content Draft

User story
As a user, I want to know how ReportStream is planning on improving so I can know if it is going to continue to meet my needs.
Background & context
With new FY25 OKRs finalized, we can update our website's roadmap page with the new annual goals and Q1 plans/progress.
Link: Product doc with ReportStream FY25 OKRs
Link: Working content doc
Acceptance criteria
Content draft

[ ] Update "Objectives" section with FY25 Annual Goals and OKRs
[ ] Update "Roadmap" section with Q1 progress & what's up next

Draft approval

[ ] Draft approved, or ticket for approval is created
[ ] If applicable, eng implementation ticket created

Link to the working content doc.

Refined first draft, shared with Chris for feedback before populating quarter-specific updates.

Chris and Brandon provided feedback + approval. Shared link with Tim for awareness.

Eng ticket created: Implement updates to the ReportStream public roadmap #16293.
Closing this ticket.


Djoser "Password Changed Confirmation" Email Not Sending

Good day,
I have been overwriting the default Djoser email templates with success, but I can't get the "Password Changed Confirmation" email to send.
According to djoser/conf.py, djoser/email.py, and djoser/templates/email it appears I am doing everything correctly. But it's not obvious why this one isn't sending as there are no errors being raised.
The project directory has these relevant files and paths:
project
  - core
    - email.py
    - settings.py
  - templates
    - email
      - activation.html                    # works
      - confirmation.html                  # works
      - password_changed_confirmation.html # does not work
      - password_reset.html                # works

settings.py was set as per the Djoser docs.
DJOSER = {
    'LOGIN_FIELD': 'email',
    'USER_CREATE_PASSWORD_RETYPE': True,
    'SET_PASSWORD_RETYPE': True,
    'SEND_ACTIVATION_EMAIL': True,
    'ACTIVATION_URL': 'activate/{uid}/{token}',
    'SEND_CONFIRMATION_EMAIL': True,
    'PASSWORD_RESET_CONFIRM_URL': 'password/reset/confirm/{uid}/{token}',
    # I set this to True as per the docs:
    'PASSWORD_CHANGED_EMAIL_CONFIRMATION:': True,
    'USERNAME_RESET_SHOW_EMAIL_NOT_FOUND': True,
    'PASSWORD_RESET_SHOW_EMAIL_NOT_FOUND': True,
    'SERIALIZERS': {
        'user_create': 'users.serializers.UserCreateSerializer',
        'user': 'users.serializers.UserCreateSerializer',
    },
    'EMAIL': {
        # These 3 templates send:
        'activation': 'core.email.ActivationEmail',
        'confirmation': 'core.email.ConfirmationEmail',
        'password_reset': 'core.email.PasswordResetEmail',
        # This one does not:
        'password_changed_confirmation': 'core.email.PasswordChangedConfirmationEmail',
    }
}

In email.py I create my custom class to reference the template. The print statements don't even fire so I don't think this is even getting called.
from djoser import email

# Override the default Djoser confirmation email.
class PasswordChangedConfirmationEmail(email.PasswordChangedConfirmationEmail):
    template_name = 'email/password_changed_confirmation.html'

    def send(self, to, *args, **kwargs):
        print(f"Sending password changed mail to {to}")
        try:
            super().send(to, *args, **kwargs)
        except:
            print(f"Couldn't send mail to {to}")
            raise
        print(f"Password changed mail sent successfully to {to}")

Sending a reset password POST request yields the following (expected) messages in the console:
Sending password reset mail to<EMAIL_ADDRESS>Password reset mail sent successfully to<EMAIL_ADDRESS>[25/Apr/2022 13:53:56] "POST /api/v1/users/reset_password/ HTTP/1.1" 204 0

I then go to the URL it provides and send a POST request with the provided uid and token to the reset_password_confirm end-point and it resolves successfully.
[25/Apr/2022 14:13:33] "POST /api/v1/users/reset_password_confirm/ HTTP/1.1" 204 0

I can successfully change the password, but there aren't any print statements from my PasswordChangedConfirmationEmail class and no email received.
What am I doing wrong here?
Any help would be appreciated, thank you.

`from djoser import email
Override the default Djoser confirmation email.
class PasswordChangedConfirmationEmail(email.PasswordChangedConfirmationEmail):
template_name = 'email/password_changed_confirmation.html'`

Have you tried this...
It should work for you.
from djoser import email

# Override the default Djoser confirmation email.
class PasswordChangedConfirmationEmail(email.PasswordChangedConfirmationEmail):
    template_name = 'email/password_changed_confirmation.html'


Investigate SDK-type binding support for OOP workers

[x] Proposal for OOP support for sdk-type bindings
[x] Prototype with Blob storage

This work has been completed. @liliankasem will be opening additional issues for the work we're tracking for sprint 130

Proposal for OOP support for sdk-type bindings

Is that a publicly available document?


Validation Error while creating Texture Geometry -> Grid

While creating a surface plot for an image with dimensions (3,3344,5822), a GPUValidationError is thrown.
The limits seems to be set at 2048, could this be changed dynamically?
Code Snippet:
        geometry = gfx.Geometry(grid=arr.astype(np.float32))
        material = gfx.VolumeIsoMaterial(clim=(0, 2000), threshold=1000)

        vol1 = gfx.Volume(geometry, material)
        self._scene.add(vol1)

Traceback:
Device::create_texture error: Dimension X value 5822 exceeds the limit of 2048
Draw error
Traceback (most recent call last):
  File "C:\Py312\Lib\site-packages\wgpu\gui\_gui_utils.py", line 77, in log_exception
    yield
  File "C:\Py312\Lib\site-packages\wgpu\gui\base.py", line 135, in _draw_frame_and_present
    self.draw_frame()
  File "c:\projekte\tutorial\stars_extract.py", line 69, in animate
    self._renderer.render(self._scene, self._camera)
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\renderer.py", line 511, in render
    container_group = get_pipeline_container_group(wobject, environment)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 159, in get_pipeline_container_group
    pipeline_container_group.update(wobject, environment, changed_labels)
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 239, in update
    container.update(wobject, environment, env_hash, changed)
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 314, in update
    raise err
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 311, in update
    self.update_shader_data(wobject, changed)
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 347, in update_shader_data
    self.update_bind_groups()
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\pipeline.py", line 442, in update_bind_groups
    binding_des, binding_layout_des = binding.get_bind_group_descriptors(
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\binding.py", line 134, in get_bind_group_descriptors
    "resource": ensure_wgpu_object(resource),
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\update.py", line 153, in ensure_wgpu_object
    wgpu_texture = ensure_wgpu_object(resource.texture)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\pygfx\renderers\wgpu\engine\update.py", line 141, in ensure_wgpu_object
    resource._wgpu_object = device.create_texture(
                            ^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\wgpu\backends\wgpu_native\_api.py", line 1149, in create_texture
    id = libf.wgpuDeviceCreateTexture(self._internal, struct)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Py312\Lib\site-packages\wgpu\backends\wgpu_native\_helpers.py", line 329, in proxy_func
    raise wgpu_error  # the frame above is more interesting ↑↑
    ^^^^^^^^^^^^^^^^
wgpu._classes.GPUValidationError: Validation Error

Caused by:
  In wgpuDeviceCreateTexture
    Dimension X value 5822 exceeds the limit of 2048

Wgpu applies some limits (of which the max texture sizes are probably the most impactful) https://gpuweb.github.io/gpuweb/#limit-default
In pygfx you can set these limits (before creating the first renderer) using e.g.
gfx.renderers.wgpu.set_wgpu_limits(maxTextureDimension3D=3000)

You cannot set limits higher than those of the adapter. From what I've seen, these adapter limits are usually not higher than the default limits. I may have to dive into this deeper, because it seems like a reasonable use-case to ask for larger textures?

Note that a 3D texture has a much lower limit than a 2D texture. What's the purpose of the 3d dimension in your code?

What's the purpose of the 3d dimension in your code?

I am trying to create a surface plot for an astro image that I took. The third dimension is the magnitude (normalized brightness  [0-1]) of the stars, later I want to switch the third dimension to the distance from earth in light years. Later, I want to save this as a 3D Object.
The X and Y dimensions are just the size of the camera sensor in pixels, so typically 4k*6.5k pixels

You can try creating a Texture that represents a stack of 2D images, so that the 2D texture limit applies.
In wgpu, this works:
>>> d.create_texture(size=(3000, 3000, 3), format=wgpu.TextureFormat.r16float, dimension="2d", usage=wgpu.TextureUsage.RENDER_ATTACHMENT)
<wgpu.backends.wgpu_native.GPUTexture object '' at 0x108cf9010>

I have not tried this in pygfx, but I think using Texture(..., dim=2) should do the trick.


6 July 2021 problem

just got a problem from now, been used these pretty long but for now 5 Jul the SAM won't display any game. Only Spacewar game from my library (Displaying 1game Total 1 game) pls help!

nvm


Handling of // protocol resolving

Hi
Seems that similar to #13 error appeared again in 0.4.0 and higher versions:
###
Uncss
https://github.com/addyosmani/grunt-uncss
Remove unused CSS
###
module.exports = ->
  @config 'uncss',
    build:
      options:
        htmlroot: 'build'
      files: [
        src: 'build/{,**/}*.html'
        dest: build/assets/styles/style.tidy.css'
      ]

	<!-- Fonts -->
	<link rel="stylesheet" href="//fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,400,300,600,700&subset=latin,cyrillic">

results in:

Please note that there is nowhere can be found path build\css in project or microtemplate's variables, while actuals project's css stored in build\assets\styles
Using of full protocol name http://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,400,300,600,700&subset=latin,cyrillic fixes that issue, but it should work with // too I guess
In 0.3.8 all works fine

Upstream issue; report it there.

Sure.
Ref: https://github.com/giakki/uncss/issues/164


Sourcing a session file may generate a "No buffers were wiped out" error

Only happens if the session contains more than threshold buffers. The error looks like:
vim/_editor.lua:0: nvim_exec2()../Users/cam/.local/share/nvim/sessions/test.vim, line 210: Vim(bwipeout):
E517: No buffers were wiped out: bwipe 3

The error may not be surfaced to the user (depending on how the session was sourced) but even if it's not shown to the user, the session will not fully restore as a result of the error.
The error happens because nvim may create an empty buffer while restoring the session. It keeps track of that buffer and expects to close it later in the session loading process:
...
" empty buffer may be created here
if expand('%') == '' && !&modified && line('$') <= 1 && getline(1) == ''
  let s:wipebuf = bufnr('%')
endif
...
<add a bunch of buffers here>
...
" empty buffer, if exists, is cleaned up here
if exists('s:wipebuf') && len(win_findbuf(s:wipebuf)) == 0 && getbufvar(s:wipebuf, '&buftype') isnot# 'terminal'
  silent exe 'bwipe ' . s:wipebuf
endif

Loading a session sets g:SessionLoad so you could check for that before checking the buffers. I'll throw together a PR if that's helpful.

If you want to repro, you can either install a session plugin (e.g. (auto-session)[https://github.com/rmagatti/auto-session]) or you can manually create a session:

disable hbac (so you can get more than threshold buffers
open more than threshold buffers
save the session: :mksession ~/test.vim
enable hbac
clear all of your buffers: :%bw so you have just a blank buffer
load the session :source ~/test.vim


[Bug] [task dependency] dependency task can't retry

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The workflow definition contains a task of a dependency type. Set Retry Times to 3 and Retry Interval to 1 minute. Enable Timeout Alarm, enable Wait for Dependency Completion, set Timeout to 1 minute, and select Timeout Policy to Timeout Failure, as shown in the following figure:

I then manually execute the workflow and select "Failure Policy" as "Continue" and execute the workflow as shown below:

During execution, it was found that the dependent task did fail after a 1 minute timeout, but after another 1 minute, it was not retried (3 failed retries have been set up above), and the workflow instance was always running. After manually stopping a workflow instance, the workflow instance remains in the ready to stop state.
I also tried to change the number of failed retries to 0 and then run it again manually, and found that the workflow instance was still running after the dependent task failed to time out the first time.
What you expected to happen

A workflow has a dependency task. If the dependency task fails to time out during workflow execution, you can retry the workflow based on the set retry times and interval.
If a dependent task fails to run eventually, the entire workflow can continue to run subsequent tasks or stop running directly according to the set running policy.

How to reproduce
Create a workflow definition where the first task type is a dependent task, which is dependent on any task that is not executed today, so that when the dependent task runs, it can time out and fail. Then enable the timeout alarm for the dependent task and wait for the dependency to complete, and set the timeout failure to the timeout policy.
Followed by any other type of task, such as a shell.
After saving the work definition and executing the workflow manually, you should see that the dependency failed to time out, but was not retried, and the corresponding workflow instance was always running. Manually stopping a workflow instance does not stop the workflow completely, but is always in a state of ready to stop.
Anything else
No response
Version
3.1.4
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Is anyone interested in this issue? can try to fix

@ziqiang-wang I see that your final results are the same. Is your log the same as this issue? #13956

@ziqiang-wang I see that your final results are the same. Is your log the same as this issue? #13956

I don't understand what you're asking


Long Press M (Lock/Unlock)

Is there a way to enable long Press to use Lock/unlock?

Hi, look there:
https://github.com/iMicknl/LoctekMotion_IoT/issues/35


ci: purge fastly path during manifest creation

The Habitat API has at least 2 layers of caching for the /latest
endpoint in use in create-manifest.rb. 1 layer of caching is in the
service itself. This cache should be invalidated on write.
The second layer of cache is via Fastly.
We have created incorrect manifests on multiple occasions and we
currently believe it is the result of this caching.
In the long-run, we would like to use the expeditor workload directly;
however, a bug in expeditor currently prevents that.
This PR purges fastly for expeditor-based builds in the hopes that it
is the fastly cache that is the cause of our inconsistent manifests.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

Fastly should not be caching any of the latest responses as we are setting cache-control to include private.  Is there a trace showing that Fastly is indeed serving the response from a cache hit?

Gonna close for now as we don't think fastly should be caching this at all.


Fix wrong React translation and exporting keyword

There was a mistake in the translation that translated the React word itself to English, making it to be Reagir (React in Portuguese). Additionally, the exports word was translated in a way that does not make much sense in this context.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


label is breaking renaming with lsp in dressing.nvim

👎 Problem
the label if is activated showing in input in dressing.nvim file rename ui and blocking some characters.

🔢 Steps to reproduce
Install neododeium alongside dressing.nvim and enable label.
👍 Expected behavior
No label visible.
Neovim version (nvim -v)
0.10.1
Operating system (uname -om)
macOS arm64
:checkhealth neocodeium
OK
Relevant log output
No response

Disable neocodeium for such windows.

I don't know your neovim expertise, so if something is unclear, feel free to continue asking in this issue.

I consider myself a noob but I thought that maybe the plugin was not meant to run in such places.

Places like what? Everything in neovim is windows and buffers.

Thants an vim.ui.input and I has no file type. It returns either a string that user has put in or nil. So haw do i disable neocodeium there?

Thats an vim.ui.input

Not this is not. It is custom implementation made with floating window and buffer.
https://github.com/stevearc/dressing.nvim/blob/c5775a888adbc50652cb370073fcfec963eca93e/lua/dressing/input.lua#L438

Yea I saw it too in the source. I have to learn more about Neovim.
Whats important is that it is in fact working as I want it. Tanks again.

@monkoose It would be helpful to make this default:
      neocodeium.setup {
        filetypes = {
          DressingInput = false,
        },
      }

It can save people from one extra google search :)

"DressingInput" is not neovim default filetype. I suppose it is some external plugin. Not all the users use it. So my answer is no.
Example how to use filetypes option is documented. User can add any additional plugin's filetypes they want.


CORE-2377: PostgreSQL supports CREATE OR REPLACE VIEW

Thanks!

@nvoxland I faced the same issue: upgraded from liquibase:3.5.3 to the latest version and got lots of errors like "cannot drop columns from view" and "cannot rename columns in view". I can't change my old changelogs due to checksums change, so is there any workaround?


Mapping to insert plain timestamps

Does this feature exist in Emacs orgmode core?
Yes
Orgmode link
https://orgmode.org/manual/Creating-Timestamps.html
Feature value
No response
Additional context
I think extending #65 to include mappings for inserting plain and inactive timestamps (without SCHEDULED: or DEADLINE:) would bring feature parity with time-stamping in org-mode. Default mappings could be <Leader>oi. for plain timestamp and <Leader>oi! for inactive timestamp similar to Emacs' bindings

:+1:  this would solve #84 - I've not used Emacs so I'm not sure what is the org way to keep track of time spent on tasks :slightly_smiling_face:

I added it, it's mapped to <Leader>oi. and <Leader>oi!. Let me know if there are any issues with it.

Thanks for the quick work on this! One issue is that the timestamp is inserted at cursor position so it breaks up the text i.e.
* TODO My task -> * TODO My tas<2021-09-17>k
Could it be changed so that the timestamp is inserted on a newline?

Emacs does the same thing:

So if you have this happening often I suggest to create a custom mapping that will first append a new line below and then trigger the org mapping.

The problem though is that Vim bindings require that you enter normal mode before you can use the keybinding to insert date.  When you hit escape, the cursor moves one character before where you were typing, so when you insert a date it always breaks up the last character of the line. Even if you leave an extra whitespace before exiting insert mode, inserting date will leave the trailing whitespace. Emacs (at least without Evil bindings) can be inserted inline with the same spacing.

I could use a instead of i when adding a date, but that would potentially cause a different kind of issues.
If you want to have a one liner, something like this work. I think it's a bit trickier because modes are switched in a single mapping
nnoremap <silent><my-keys> o<Esc>:exe "norm \<Leader>oi."<CR>

or this:
:nnoremap <silent><my-keys> o<Esc>:call feedkeys("\<Leader>oi.")<CR>

The mapping is hacky but works okay. Thanks!

Is it possible for this to give the current time as well? :thinking:


NuGet package fix for support of win32 projects

Removing Condition="'$(TargetPlatformIdentifier)' == 'UAP'" for Issue #294 and Proposal #494, for Win32 projects support.
Without this change, attempting to compile repro project
\UWPCompositionDemos\HelloVectors\HelloVectors_win32_cpp\HelloVectors_win32_cpp.vcxproj
from https://github.com/clarkezone/UWPCompositionDemos/tree/vectors would result in the WinUI nuget not being found, even though it was properly installed.
That error went away when using the experimental nuget build https://dev.azure.com/ms/microsoft-ui-xaml/_build/results?buildId=11145 instead.
Fixes #294, fixes #494

We still need a similar change for DotNetCore projects.
DotNetCore projects do NOT include the targets file in the native folder, only the parent folder.
Without this, a dotnetcore project will fail to compile.

@ocalvo, thanks for the info. This PR has already been closed. Please file a new Issue for this problem.


Template specializations

Summary
Wrappers are created for methods in template specializations that may not have been implemented. In the example below, the Foo(unsigned u) constructor is not implemented in the specialization.
Foo.hpp
template<unsigned DIM_A, unsigned DIM_B>
class Foo : public AbstractFoo<DIM_A, DIM_B>
{
public:
  Foo(unsigned u);
  Foo(unsigned u, double d);
};

// Specialization
template<unsigned DIM_B>
class Foo<1, DIM_B> : public AbstractFoo<1,DIM_B>
{
public:
  Foo(unsigned u, double d);
  Foo(unsigned u);
};

Foo.cpp
template<unsigned DIM_A, unsigned DIM_B>
Foo<DIM_A, DIM_B>::Foo(unsigned u) : AbstractFoo<DIM_A, DIM_B>(u)
{
  // implementation
}

template<unsigned DIM_A, unsigned DIM_B>
Foo<DIM_A, DIM_B>::Foo(unsigned u, double d) : AbstractFoo<DIM_A, DIM_B>(u, d)
{
  // implementation
}

// Specialization
template<unsigned DIM_B>
Foo<1, DIM_B>::Foo(unsigned u, double d) : AbstractFoo<1, DIM_B>(u, d)
{
  // implementation
}

The wrapper below is generated for Foo<1,2>:
py::class_<Foo1_2, Foo1_2_Overloads>, AbstractFoo<1,2> >(m, "Foo1_2")
  .def(py::init<unsigned int>(), py::arg("u"))
  .def(py::init<unsigned int, double>(), py::arg("u"), py::arg("d"))

This results in a linker error:
undefined reference to `Foo<1u, 2u>::Foo(unsigned int)'

One possible solution is to allow specifying exclusions for specific template arg values.

This can be done by excluding the unimplemented method from wrapping for the whole class, and then adding it back in for the appropriate template args using a custom wrapper generator.

The example above can be fixed in this manner:
package_info.yaml
classes:
  - name: Foo
    constructor_signature_excludes:
      - [unsigned]

FooCustomTemplate.py
class FooCustomTemplate(cppwg.templates.custom.Custom):

    def get_class_cpp_def_code(self, class_name):
        DIM_A =  # Extract DIM_A from class_name here

        if DIM_A != "1":
            return ".def(py::init<unsigned int>(), py::arg("u"))"

        return ""


updated sources so they now return a redshift list, and updated Confi…

…gHandler to also include z_source, z_source_convention, and multi_plane.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.005%) to 94.612%

Files with Coverage Reduction
New Missed Lines
%

../../../../../opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/paltas/Sources/cosmos.py
1
99.17%

../../../../../opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/paltas/Configs/config_handler.py
5
97.8%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
2037

Relevant Lines:
2153

💛  - Coveralls


Clarification needed in article abstract "High availability for Azure SQL Database and SQL Managed Instance"

Hi all,
in the abstract of this article [https://learn.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla?view=azuresql&tabs=azure-powershell]  there's a statement about "Zone-redundant configuration":

In the following chapters I found that this configuration is available also for Premium SKU:

...and also for Hyperscale SKU:

Can you please clarify and update the abstract statement accordingly to the content in the whole page?
Thanks for your cooperation and I take this opportunity to tell you that you are doing a great job with this documentation, which is very rich and detailed.
Luca Bovo - beanTech

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

ID: e2d07885-d3f0-11d9-0a1f-aa9025d60d49
Version Independent ID: 551bdeb1-fc7c-5d7f-4e58-a558d3a39df7
Content: High availability - Azure SQL Database and SQL Managed Instance
Content Source: azure-sql/database/high-availability-sla.md
Service: sql-db-mi
Sub-service: high-availability
GitHub Login: @AbdullahMSFT
Microsoft Alias: amamun

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

@rajeshsetlem for awareness.

#assign:rajeshsetlem

Hi @lucabovo , thanks for contacting Microsoft! Our apologies for the confusion, the introduction sentence is meant to imply that for Azure SQL Managed Instance, zone redundancy is currently in preview and only available in the Business Critical service tier, whereas for Azure SQL Database, it's available in the Premium service tier for DTU databases, and in both the General Purpose and Business Critical service tiers for vCore databases.
We're currently in the process of refreshing this content for better clarity so please stay tuned.
I'll go ahead and close out this Git Issue but please feel free to comment should you need anything further.
Thanks again for reaching out and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close
#assign:MashaMSFT


Assist is translating my request, and then failing to comply

Hey there,
When using Piper as source for translation of my Assist within Home Assistant, I'm using Portuguese as the language.
Although, for it translates my sentence to English which then seem to make the Assist to be able to recognize the command.

Did I misconfigure something? I don't think so, as it was working in the past, and if I run the text pipeline, it does work as expected.

Cheers

Assist doesn't translate anything, so it looks to me like everything is working correctly. A Portuguese pipeline should fail with an English sentence, no?

What you are saying does make sense, but I have everything set to Portuguese 😅 Could I be missing something else?

Just to confirm, the voice command was spoken to Piper in Portuguese, which then translated to English, and that is what you are seeing on the first screenshot.
That’s whisper not piper. Piper is the output which is in Portuguese.
Are you on HA 2024.3.0 ?

Just to confirm, the voice command was spoken to Piper in Portuguese, which then translated to English, and that is what you are seeing on the first screenshot.

That’s whisper not piper. Piper is the output which is in Portuguese.
Are you on HA 2024.3.0 ?

Ohhh that’s right 🤦♂
Yes, I’m. But this was already happening in the previous version.

This screenshot says PT:

But this EN:

Something seem wrong.

This screenshot says PT:

But this EN:

Something seem wrong.

Yes, that was what I wanted to understand. Because, I did created the container as English at first, but then noticed that you can select other languages within the configurations. I thought that it could be default vs actuals. Nevertheless, I might need to create a new portuguese container, and see if that solves the issue.

In theory you are correct, the Assist pipeline config shall be able to use the settings different from the container. But I'm still intrigued how the Portuguese speech got translated to English. :D
I'm also using voice in Portuguese and this never happened.

In theory you are correct, the Assist pipeline config shall be able to use the settings different from the container. But I'm still intrigued how the Portuguese speech got translated to English. :D
I'm also using voice in Portuguese and this never happened.

If you don't mind, can you share your Container configs?
The odd thing is, I didn't change anything, as far as I can recall of course, and it was working in the past.

Did create a new whisper container with PT as default, and that sorted out.
Although, I don't understand how in the past this worked, but now is failing. 🤷♂
whisper-portuguese:
container_name: whisper-portuguese
image: rhasspy/wyoming-whisper:latest
command: --model base-int8 --language pt
volumes:
- /volume1/docker/whisper-portuguese:/data
environment:
- TZ=Europe/Lisbon
restart: unless-stopped
network_mode: "host"
ports:
- 10300:10300

Closing this, and moving it to rhasspy/wyoming-faster-whisper.


'nonce' parameter validation is done at the endpoint

Background

According to the  OIDC spec, 'nonce' parameter validation is done once all the request parameters are assembled from both OAuth request and the request object.

Issue

'nonce' parameter validation is done at the endpoint once all the parameters are assembled. This validation needs to be moved to a proper validator class.

Reference

nonce validation

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Drop chowlk support

At the moment, generating method graphs via Chowlk is supported by data2rdf. However, dropping this functionality would simplify the package and is therefore desiderable.

Has been solved in the #54 release.


For #15: EO badge.

For #15: EO badge.

Codecov Report

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

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

@rultor merge

@rultor merge

@paulodamaso OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@paulodamaso Done! FYI, the full log is here (took me 2min)


Visual Studio Solution Explorer README.md Addition

There is an unresolved comment from https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/pull/91 about working with Visual Studio's Solution Explorer that wasn't addressed. I plan to address it in a coming PR.

@brettrowberry Do you still plan on creating a PR for this? If not that's fine, just looking for a status update here.

@brettrowberry Do you still plan on creating a PR for this? If not that's fine, just looking for a status update here.

Closing this as inactive, feel free to re-open if desired.


Wrong exclude rectangle on phantomjs/ explorer

Running mochaon this test with phantomJS or with BroserStack on ie11 produces excludes that don't cover the entire element.

@christian-bromann how about using CSS for the exclusion, instead of getting the absolute. We could set:
color: transparent;
background: black;

(as remove for example is already "playing" with the dom)

I will try to mimic this behavior with the above example using execute, and lets see how it turns out...

You wouldn't be able to do polygonal exclude regions using CSS. But if IE isn't calculating the right size and offset of elements then that is going to be a larger problem than just for exclude regions and should definitely be fixed.

@TheSavior
Sorry, indeed I forgot to mention it will not work for polygonal.

But if IE isn't calculating the right size and offset of elements then that is going to be a larger problem

It seems we are using getBoundingClientRect to get the values - which seems to be the right way, although in the end result many times I see IE not excluding properly.

On the other hand, if there's a way to "fix" getBoundingClientRect, I'd be happy to continue with the good old shot.drawRectangle() way ;)

Interesting for sure that all exclude rectangles have the same padding to the desired position. I bet there is some document margin not included in that getBoundingClientRect function.
@amitaibu how about doing both? Using CSS to make background black (would not work for certain elements though) + using drawRectangle

I bet there is some document margin not included in that getBoundingClientRect function.

You mean some CSS element that messes with it? Not sure how to find it - can you spot it?

how about doing both?

Well, I'd argue that having one system that simply works should be fine ;)
I think we should try to find the cause - maybe it's something we can over come without removing shot.drawRectangle() as indeed now that you mention it, with CSS it might be tricky to do on some elements flash, svg, etc' :/

thank you guys for the quick replys ;)

With the risk of saying something stupid (won't be a first time :wink: ) - If I understand correctly getBoundingClientRect() is relative to the current view port not the absolute value.Looking at this part, could we be missing the scroll value?

So... I think I found the problem - the gap we are seeing is the scrollbar.

The webdriverCSS image doesn't include the scrollbar, thus we can see a bigger padding on the document.
I've done some careful testing to confirm this Browsing the site directly via ie11 (using browserStack):

Printing the values of excludeRect we see we got the right values:
{ x0:<PHONE_NUMBER>621094,
    y1:<PHONE_NUMBER>03125,
    x1:<PHONE_NUMBER>792969,
    y0:<PHONE_NUMBER>515625 }

Using CSS to place an element using absolute to position a rectangle on those same coords:

Ouch, I've added document.body.style.overflow = 'hidden'; to hide the scrollbar, but the exclude is still placed wrong :/

Try -ms-overflow-style: none, that will hide the scrollbar in IE.

maybe getBoundingClientRect() gets calculated on render time. :+1: for the finding @amitaibu

Ok, last info before letting this go for tonight...
On BrowserStack the resolution is set to 1024x768. However, when checking the max width we see it's 1007px with the scrollbar, and upon document.body.style.overflow = 'hidden'; it is set to 1024px. So even though it's not working, I still think it's the scrollbar ;)

yeah seems like it. Actually it would be no problem to remove the scrollbar because we scroll using css as well

So I'm able to remove the scrollbar, but the values from getBoundingClientRect() are indeed the same.
    client
      .url(baseUrl)
      .execute(function() {
        document.body.style.overflow = 'hidden';
      })
      .webdrivercss(testName, {
        name: 'homepage',
        exclude:['#community-stats .users .highlight'],
  // ...

Could you try -ms-overflow-style: none too?

I would not recommend setting overflow on the body to hidden. My guess is that if there are any scrolling elements this will be a problem so applying this to body isn't right. I'd really recommend trying
* {
  -ms-overflow-style: none;
}

@christian-bromann do you mean something like document.body.style.-ms-overflow-style='none';?

meh, too late, not thinking right ^^ ;)
jQuery('body').css('-ms-overflow-style', 'none'); didn't have an effect. But do you think there's a difference from doing document.body.style.overflow = 'hidden'; which is working fine?

Doing manually getBoundingClientRect() after hiding the scrollbar seems to return new values.

So if I'm indeed right about this, then the next thing is to figure out why getBoundingClientRect() doesn't return the updated one when running via webdriverCSS

there are the 9px :wink:

yeah, one pixel for each hour I lost on finding it :wink:

haha, so but this is not working using the execute command?

btw: thanks for figuring that out :+1:

Sure :)

so but this is not working using the execute command?

Unfortunately no. The weird thing is that the image we get from webdriverCSS doesn't have the vetical scrollbar even without the execute I've added.

@christian-bromann if you'd like I can add you to my BrowserStack account if you want to experiment.
(It's getting late, and I actually attend a conf about Shoov tomorrow :smile: )

wait I got it

waiting... :)

So here is the problem: https://github.com/webdriverio/webdrivercss/blob/master/lib/documentScreenshot.js#L101-L119
before I take the screenshot I do that overflow hidden thing already but remove it after taking the screenshot and before executing getBoundingClientRect().

I guess we need to capture these information while being in that capturing state. Doesn't look like an easy refactor though :-/

what do you mean by

but remove it after taking the screenshot and before executing getBoundingClientRect()

Remove what?

when I take the screenshot I remove the scrollbars and enable them after taking the screenshot. Then the next step ist to capture the position information (with scrollbars enabled instead of disabled)

why do you need to re-enable them?

good question..I think it might be better to leave the page as it is as much as possible. Not sure if this is necessary though

page might behave differently with scrollbars disabled. This could affect the next capturing process/screenshot.

meh, your messing with the dom anyway with remove, and possible with execute.
In fact, removing document.body.style.overflow = 'visible'; has fixed the problem!

you'r messing with the dom anyway with remove

not quite, I just set display: none and enable it after the capturing process. But yeah I guess this solves definitely some displacement issues \o/ .. glad it works now.

But you'll accept a PR to remove the re-enabling, right? :)

well, I'm out for today..

We should think of a better strategy for the capturing process instead of just removing a line of code.

ok, good night and thanks again!

:+1:

We should think of a better strategy for the capturing process instead of just removing a line of code.

What would be the implication of that removal? As far as I can see, even as a short term solution it would be preferable than having that offset almost constantly on IE.


修复 toolkit:replace 可能出现无限递归的情况

toolkit:replace 当参数 new_str包含old_str 的时候回出现无限递归
如:
string test = "m=audio 0 RTP/AVP 0\r\n";
toolkit:replace(test,"RTP/AVP","RTP/AVP/TCP");

将出现无限递归导致溢出

 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.liangzhuohua seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Multiple RHS Support

This patch changes the type of the RHS argument of ExhaustiveSynthesis::synthesize() and Solver::infer() from a Inst pointer to a vector of Inst pointers.
Exhaustive Synthesis takes a constant "MaxRHS". This constant is set to 1 for performance. Exhaustive Synthesis generates at most MaxRHS number of RHSs. The original Souper test suite on my machine runs for 282.54s while with MaxRHS set to 3, the test suite runs for 454.83s.
Call sites of infer() function takes the result vector of RHS and extract the first RHS, this preserves the behaviors of these call sites.

Note: no support for multiple RHS dump in souper-check and redis cache in this patch.


pull request for e2e test at 12/04/2016 20:45:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


docs: improve readme code formatting and grammar

Noticed while checking this library out :)

Hey 👋  I thank you for the pr and the time spent on it.

@gkampitakis yup go for merging - there might be further improvements but I'm happy to do as many PRs as needed :)


Comments break indentation of subsequent lines

Tested with 0.24.2, this can be reproduced in the playground:
// Input
public class C {
    public void Test() {
        this
            // This is a comment
            .LongUglyMethod();
    }
}

// Playground output
// Observe that the comment and .LongUglyMethod() are not indented
public class C
{
    public void Test()
    {
        this
        // This is a comment
        .LongUglyMethod();
    }
}

// Expected output
public class C
{
    public void Test()
    {
        this
            // This is a comment
            .LongUglyMethod();
    }
}

This seems to only occur if the first line is a comment.
If the comment line follows an already indented line, everything seems ok:
// Input
public class C {
    public void Test() {
        services
        .A()
        // This is a comment
        .C();
    }
}

// Output is ok
public class C
{
    public void Test()
    {
        services
            .A()
            // This is a comment
            .C();
    }
}

Maybe related (but maybe not)?
Here's another bad case I observed involving comments messing subsequent formatting.
When you put a comment on a method parameter that has an attribute, the comment forces a line break between attribute and parameter name. This is inconsistent with the formatting without comment, and doesn't look good on short lines.
// Input and expected -> ok!
void TestALongMethodWithAttributesOnParameter(
    [FromBody] string name,
    [FromQuery] List<string> manyTags
) { }

// Input and expected -> not ok
void TestALongMethodWithAttributesOnParameterAndComment(
    // This is a comment on name
    [FromBody] string name,
    [FromQuery] List<string> manyTags
) { }

// Actual playground output for 2nd method
void TestALongMethodWithAttributesOnParameterAndComment(
    // This is a comment on name
    [FromBody]
        string name,
    [FromQuery] List<string> manyTags
) { }


feat: add '.decoration-x' utility classes

This PR is intended to be compatible with the new text-decoration syntax of Tailwind v3.
Useful resources:

https://tailwindcss.com/docs/text-decoration
https://tailwindcss.com/docs/text-decoration-color
https://tailwindcss.com/docs/text-decoration-style
https://tailwindcss.com/docs/text-decoration-thickness
https://tailwindcss.com/docs/text-underline-offset

This PR is a work in progress. I will comment once all new syntax is implemented and ready to be merged.

Added Features
New default color
The default colors now support inherit just like current (currentColor) and transparent
.text-inherit {
  color: inherit;
}

.bg-inherit {
  background-color: inherit;
}

.decoration-inherit {
  text-decoration-color: inherit;
}

Text Decoration Type, see here
Now supports another variant 'overline'
.overline {
  -webkit-text-decoration-line: overline;
  text-decoration-line: overline;
}

Text Decoration Style, see here
Now supports another variant 'wavy'
.decoration-wavy {
  -webkit-text-decoration-style: wavy;
  text-decoration-style: wavy;
}

Text Decoration Length, see here
See Breaking Changes - Text Decoration Length
Breaking Changes
Text Decoration Color, see here
The current way of setting text decoration colors is:
.underline-green-500 {
  --tw-line-opacity: 1;
  -webkit-text-decoration-color: rgba(16, 185, 129, var(--tw-line-opacity));
  text-decoration-color: rgba(16, 185, 129, var(--tw-line-opacity));
}

The new way is:
.decoration-green-500 {
  --tw-text-decoration-opacity: 1;
  -webkit-text-decoration-color: rgba(16, 185, 129, var(--tw-text-decoration-opacity));
  text-decoration-color: rgba(16, 185, 129, var(--tw-text-decoration-opacity));
}

Text Decoration Opacity, see here
This is no longer available/need, as above syntax now support opacity values:
.decoration-green-500\/50 {
  --tw-text-decoration-opacity: 0.5;
  -webkit-text-decoration-color: rgba(16, 185, 129, var(--tw-text-decoration-opacity));
  text-decoration-color: rgba(16, 185, 129, var(--tw-text-decoration-opacity));
}

Text Decoration Length, see here
The current way of setting the text decoration lenght (thickness) is:
.underline-auto {
  text-decoration-thickness: auto;
}

.underline-8 {
  text-decoration-thickness: 8px;
}

The new way is:
.decoration-auto {
  text-decoration-thickness: auto;
}

.decoration-8 {
  text-decoration-thickness: 8px;
}

Now supports another variant 'from-font'
.decoration-from-font {
  text-decoration-thickness: from-font;
}

Unchanged

Text Decoration Offset is unchanged, as Tailwind v3 has the same syntax

I adjusted the test.
One issue I have is that the test are still failing and I'm not quite sure why. Maybe you can point me in the right direction as this is the first time I'm working with tests.

You might need to build first and then run the test

Sadly building first does not solve the issue. But I noticed some strange behaviour while looking through the test results. This gets generated by the Tools / text decoration color & opacity & length & offset / css / 0 processor (utilities.test.ts and utilities.test.ts.yml):
.decoration-double {
  -webkit-text-decoration-style: double;
  text-decoration-style: double;
.decoration-dashed {
  -webkit-text-decoration-style: dashed;
  text-decoration-style: dashed;
}
.decoration-dotted {
  -webkit-text-decoration-style: dotted;
  text-decoration-style: dotted;
}
.decoration-dashed {
  -webkit-text-decoration-style: dashed;
  text-decoration-style: dashed;
.decoration-double {
  -webkit-text-decoration-style: double;
  text-decoration-style: double;
}

Somehow there are missing brackets and the output is doubled.

Today I learned that the order of test results is very important 👀

Awesome, thanks a lot!


(SERVER-781) Add hiera as submodule

I chose version 1.3.4 as that was the version in the latest PE 3.8.1.  We can bump this up to newer versions for master branch, etc., as we do the merge-up from here.

:+1:
Also did a "functional" test of this by starting up a server from lein run on the branch using a "puppetserver.conf" which referenced the hiera submodule directory from the ruby-load-path and with some code loaded on the server that would perform a parameter lookup from hiera.  I didn't get any errors so seems reasonable to me.

:+1: This looks good to me.


Saving yaml does not resolve 409 errors

Setup

Rancher version: 2.9
Rancher UI Extensions: N/A
Browser type & version: N/A

Describe the bug

Saving yaml does not resolve 409 errors the way CreateEdit mixin does, making editing fail. This happens when editing CAPI provider but can happen in other areas of the product, so it should be fixed globally.
To Reproduce

This issue became noticeable when editing CAPi provider but it can occur in other parts of the product

Enable editing yaml for CAPI provider
Try editing existing provider

Result
"Operation cannot be fulfilled on capiproviders.turtles-capi.cattle.io "x": the object has been modified; please apply your changes to the latest version and try again" error is shown. Trying to save again returns the same error.
Expected Result

Saving yaml should retry saving if 409 error similar to the way Create edit mixin does. ie https://github.com/rancher/dashboard/blob/820374c0f04d11999b12bb2ec6d40936b682c03e/shell/mixins/create-edit-view/impl.js#L121
Screenshots

Additional context

I'm not 100% sure, but i think the conflict resolution part used when we do a normal safe will only work with json. Not sure we can convert yaml to json and then back again to save without content getting borked

@richard-cox do you think it will be feasible to have some alternative way to resolve conflicts when parsed from yaml or should we not allow editing as yaml in cases where conflict might occur?


Explains why there is no need for fixtures

Thanks Michael. Adding this comment will make things easier to understand when looking at this for the first time. We reworded the message a bit while merging to make it more concise, but your contribution was great! Thanks.


How to purge all files before deployment

** Please describe which feature you have a question about? **
Hi we have implemented two new Custom headers we want to apply these headers to all the files,
However files which are changed are only being deployed and files which are untouched are being skipped while deploying
we need to purge all the previous files and re deploy every thing
Please let us know the workaround
** Provide additional details**

Custom headers are automatically added to all files that you have deployed, you don't have to purge all files anymore. I'm closing this issue as fixed.


Update workflows.

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

Comparison is base (a706b35) 97.57% compared to head (e66d614) 97.57%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #289   +/-   ##
=======================================
  Coverage   97.57%   97.57%
=======================================
  Files          35       35
  Lines        2265     2265
  Branches      217      217
=======================================
  Hits         2210     2210
  Misses         54       54
  Partials        1        1

Flag
Coverage Δ

unittests
97.57% <ø> (ø)

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

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


Support for Python 3.8 in infinity

Feature request
I am currently working on a project that has strict environmental requirements and dependencies which necessitate the use of Python 3.8. However, I have encountered issues when trying to use the infinity package in this Python version. Both installation methods via pip and building from source have been unsuccessful.
Motivation
The inability to install infinity on Python 3.8 is posing a significant impediment to the progress of our project. Given that Python 3.8 is still widely used and that other project dependencies are not compatible with newer Python versions, it is crucial for our project to have infinity package support for Python 3.8.
Your contribution
None

Hey, I made some efforts when merging rhe AWS inferentia packages. As this packages relies on e.g. strong type checking.
Python 3.8 reaches end-of-life in 5 months as of this comments date (10/24). I have not seen any compelling reasons for downgrading to 3.8, the minimum is 3.9.
If your project has a high relevancy, Id be happy to work on a 3.8 compatible version as special release. Feel free to reach out via email for me for that.


Windows support via msys2

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [15, 19, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35]

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [15, 19]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@basnijholt I think this is ready for your review

It would be good to review this soon so we can merge https://github.com/conda-forge/ipopt-feedstock/pull/18, which might fix some issues users have been having ( https://github.com/conda-forge/ipopt-feedstock/issues/19 )

I am going ahead and merged this, I've asked for help with reviewing on Gitter several times, but no response.
I am sorry that it took so incredibly long! Thanks a lot for your contribution 😄

@conda-forge-admin, please rerender

I will merge as soon as the tests succeed.

@richardotis, after re-rendering some test seems to fail: https://ci.appveyor.com/project/conda-forge/mumps-feedstock/build/1.0.10

@basnijholt Looks like a hiccup on the CI. I restarted the job and now it seems to pass.

I want to note for the record that if someone finds this PR and is having an issue getting something besides double floating point arithmetic to work in MUMPS on Windows, here we are only building support for doubles in MUMPS on Windows (libdmumps.dll).

here we are only building support for doubles in MUMPS on Windows (libdmumps.dll).

Once #28 is merged we will have support for all datatypes.


case insensitivity feature

This adds case insensitivity to the feature counter by making all input strings uppercase

Misread instructions, need new feature


0.0.10

Release Notes for v0.0.10
New Features

Unit Tests and Examples

Added comprehensive unit tests and examples for the following modules:

parser.rs
util.rs
path.rs
safe_cstr.rs
tag.rs
de.rs
index.rs
emitter.rs

These additions significantly improve the test coverage and provide clear examples for better understanding and usage of the library.

Fixes

Bug Fixes

Destructuring in match Statements: Fixed an issue where match was used for destructuring a single pattern. This has been corrected to use if let for cleaner and more efficient code.

Documentation

Documentation Updates

Updated the documentation to reflect the latest changes.
Improved the clarity of existing documentation.
Prepared the documentation for the upcoming v0.0.10 release.

Refactoring

Code Refactoring

error.rs: Ongoing refactoring to improve the code structure and readability.
Examples and Tests: Made minor tweaks to existing examples and added new unit tests to ensure robustness and accuracy.
Library Dependencies: Updated dependencies for libyml to maintain compatibility and leverage the latest features.

Hi @sebastienrousseau . Sorry for writing this here, but you does not have enabled Issues page in this repository. Could you enable them? Thanks!


[Bug]: Do not open contributors page in new page

What bug you encountered?
when we click on our contributor button it will redirect to the contributors page and open that link in a new page, but we want to open that link in the same page.
FOR GSSOC : LEVEL1
Show us the trouble with screenshots
.
Which browsers are affected?
No response
Record

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

@PiyushKalyanpy, Would like to work on this issue under gssoc23. Please assign this to me.


Switch over to semantic-release

Refactor Request
We need to switch over to semantic-release to improve and simplify the package and release process.
Currently we manually create the release bundle and publish it locally to npm.
Description of the proposed solution
See README in above linked project repo.

closed by #535


autocomplete inflected forms in the search box

While the user is searching, show autocompletions of possible inflected forms.
From our discussions, it sounds like this could be difficult / undesirable to implement. Opening this issue as documentation that this was considered, and so that we can record our eventual decision about it.

Yes, we can consider what this would require, and why that wouldn't potentially work (well) now.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1886

Questions ?
Please refer to the Backport tool documentation


IPv6 addresses are always in big endian order

No matter what the architecture is, IPv6 addresses are always in big endian order in the C structure.
Parsing IPv6 addresses used to be broken in Nix on little-endian architectures. For example, [::1] resulted in address [::100] being effectively stored.

I suggest adding a comment that refers to RFC 1700.

@fiveop what's the relevant section?

If I understand it correctly, it specifies that all IP related RFCs are to picture data in big endian order, which results big endian becoming the 'network byte order'. See for example the linux man page on ipv6. I'll add a corresponding comment and commit this.

:+1:

Merged as 7502db05f562daac1e353fd51d9072b81571f8fb...645c48f2890cd5ef993f6a73970a693e26ca5f91.


Expose OIDC audience of KafkaSink in its status

Proposed Changes

Provision a KafkaSinks .status.address.audience and .status.addresses[*].audience field

/cherry-pick release-1.15
/cherry-pick release-1.14

/cc @matzew @pierDipi
Seems I missed the OIDC integration into the KafkaSink (exposure of its audience) :disappointed:

/test integration-tests

/retest

/retest

{Failed  === RUN   TestKafkaChannelOIDC/KafkaChannel_handles_requests_with_OIDC_tokens_correctly/KafkaChannel_handles_event_with_valid_OIDC_token/Assert/KafkaChannel_get_202_on_response

        - Match errors -
        0 - event status code don't match. Expected: '202', Actual: '0'
        1 - event status code don't match. Expected: '202', Actual: '0'
        2 - event status code don't match. Expected: '202', Actual: '0'
        3 - event status code don't match. Expected: '202', Actual: '401'

/retest-required

/retest-required

/test upgrade-tests


Change in Wiki

There's something that should be changed under installation.

Packages
WARNING: I do not maintain any packages. If they are broken, try building from source first.
Arch (AUR)
yay -S hyprland-git

Underneath this blurb, something I recently learned that could be useful can be mentioned by adding the following:

Given this project is under development and constantly changing, if you want to keep up to date with the latest commits, please consider updating your packages with yay -Syu --devel.

done


Drop "bindgen" from libthemis-sys dependencies

TL;DR: drop 40 dependencies we don't need to get x10 build speedup
Why we used Bindgen in the first place
Initially Bindgen was used to dynamically generate Rust bindings to C code. I have thought that this is the most idiomatic way to it. It is also more robust as Bindgen will be working with the actual Themis version installed on the user system.
What's wrong with using it
However, Bindgen has a lot of transitive dependencies, they take quite a while to compile, and they need to be compiled by our users too. This is a constant source of irritation for developers. Users are not really happy with that as well.
Why we don't really need to be using it
While we try our best to maintain backwards compatibility when it comes to symbols and dependencies, we generally do not bother with forward compatibility. And we effectively pin wrappers to the core library. That is, RustThemis 0.N is guaranteed to work with Themis Core 0.N, it is also guaranteed to work with Themis Core 0.N+1, and will most likely work with Themis Core 0.N+2 (unless there is deprecated API removed). However, the converse is not the case. RustThemis 0.N+1 may work with Themis 0.N if no new features were added, but otherwise it might fail to compile.
Thus, RustThemis is effectively pinned to Themis Core version, meaning that their versions must match. If that's the case, we do not need to generate FFI bindings on the user machine because we know which version we are shipping with and what symbols are available there. Thankfully, we also write portable C code so Themis API does not depend on the target architecture – which allows us to ship the bindings verbatim. Otherwise we'd have no choice other that generate them on the fly.
How we can avoid using it
With that in mind, start generating src/lib.rs manually with the help of bindgen.sh script. The developers are expected to run it on their machine to regenerate bindings somewhere before release. The users now do not need to generate these bindings on their machine, meaning that
we can drop bindgen crate dependency and all supporting code.
What we get by not using it
In the end, this gives significant improvements in transitive dependency count (down to 3, from 43) as well as ENORMOUS improvements in build times (in seconds):

Before
After

Debug
Linux
28.43
2.68

macOS
52.80
8.47

Release
Linux
52.08
5.35

macOS
127.21
8.71

CI builds were a source of pain since they build RustThemis in both debug and release versions, possibly several times, and in the worst case they are running with only one virtual CPU so the absolute time to run the test suite might be several minutes.
What do we do when this is merged
Now the maintainers need to run bindgen.sh when something has changed that may affect the content of libthemis-sys.
There is a new GitHub Action step to verify that the output of the ./bindgen.sh script does not change and src/lib.rs does not need an update. This will break the build once changes are necessary. Typically this means that some new API is exported by Themis or there are some changes in Bindgen's behavior. Either way we would like to be notified.
This is not ideal since ‘unrelated’ changes in Core may trigger the failure as well as some updates in Bindgen without code changes on our side. But this is probably fine since we don’t change API that often.
Checklist

[X] Change is covered by automated tests
[X] Benchmark results are attached (see CI logs)
[X] The coding guidelines are followed
[X] Public API has proper documentation
[X] Changelog is updated

Hm... 🤔
I tried to run make test_rust locally and found out that libthemis-src fails to build due to missing ./configure (see #611). I had forgotten to symlink it or something. I wonder why CircleCI has been fine all this time...

The issue with symlinks has been resolved by #628. I'll merge latest master into this branch to see if it still builds fine and will merge if the build is green.


Fix Typographical errors

This PR addresses typos

thanks @tmsagarofficial I had to modify some edits, so I made a new PR since I can't push to your fork


Unable to run tests in private network

Pleaseeeeee help me fix this blocking issue. I have deployed a sample contract to a private blockchain. Embark deploy privatenet works perfectly fine. when i run test, it fails with the following message. I guess, it is not able to find the blockchain and the account. I am running the command embark spec and embark spec privatenet.
error output
D:\aaa\xxx\BLockchain\installed\embark\FirstContract>embark spec
Secp256k1 bindings are not compiled. Pure JS implementation will be used.
Secp256k1 bindings are not compiled. Pure JS implementation will be used.
Conference
primary account address is : null
trying to obtain Conference address...
1) "before all" hook
0 passing (3s)
1 failing

Conference "before all" hook:
Error: the string "invalid address" was thrown, throw an Error :)
at Runner.fail (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runner.js:226:11)
at Runner.failHook (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runner.js:262:8)
at D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runner.js:307:16
at done (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runnable.js:287:5)
at Hook.Runnable.run (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runnable.js:322:5)
at next (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runner.js:298:10)
at Immediate._onImmediate (D:\aaa\xxx\BLockchain\installed\embark\FirstContract\node_modules\mocha\lib\runner.js:320:5)

hi @talktoav , embark spec by default actually runs on a simulator (Ethersim) not on a private net, are you connecting the test directly to an ethereum node? could you post part of the test? also what version of Embark are you using?

Hi Iuri thanks for the respone,
I am using Embark - 1.2.0 version. I am indeed connecting Embark directly to a Ethereum node. While deploy works, test does not.
To give more context, here is my local private network set up.

The private network, named privatenet, on my laptop has 2 nodes. Each node has one account created. I use node #1 to deploy contracts to and node #2 for mining.  The contract gets deployed and I receive the deployed contract’s address. Updated blockchain.yml with
privatenet:
testnet: true
rpc_host: localhost
rpc_port: 8545
rpc_whitelist: "*"
datadir: default
network_id: 321
deploy_timeout: 45
console: true
account:
init: false
address:

Now I run embark spec or embark spec privatenet, which gives me the error I reported. The test spec is simple
var assert = require('assert');
var Embark = require('embark-framework');
var Embark = require('embark-framework');

describe('Conference', function() {
// Deploy all contrats using the development config
before(function(done) {
EmbarkSpec.deployAll(done);
});
      it("should assert equal", function(done) {
	Conference.organizer(function(err, result){
		return result;
                assert.equal("0x8ff277f696fd4199b9b8b149da114ce12e49e45r",result.toString());
	          done();
	});
  });

});
May be the test case is incorrect but it does not move beyond deployAll(). Incase the deployAll(done) is commented, the error i get is Conference is undefined. Please help me move forward or advise and suggest a way to fire transactions deployed on my private blockchain.

for the simulator, you need to create the accounts and set the balance before deploying
  before(function(done) {
    EmbarkSpec.sim.createAccounts(10, function() {
      EmbarkSpec.sim.setBalance(web3.eth.accounts[0],<PHONE_NUMBER>000000000000, function() {
        EmbarkSpec.deployAll(done);

Note this is a simulate environment as intended, each time you run the tests it will be a brand new chain. You can change it to run the tests on a "real" chain, but you might encounter some issues in regards to state.

an example here https://github.com/iurimatias/embark-framework/blob/develop/demo/test/simple_storage_spec.js

Thanks a ton!!!!. I am unblocked and the simulator scenario works!!!!. I will fix my test cases now.
I have one more issue on which in need your help. I really want to connect to the node that runs my contract (not the simulator) on the private network. The accounts there have enough Ether. What changes do i need to make?

you mean you want to run the tests against the privatenet node?
you could run something like this, which overrides the web3 object to connect to the node instead of the sim, it was not designed for that, but should work:
var assert = require('assert');
Var Web3 = web3;
var Embark = require('embark-framework');
var EmbarkSpec = Embark.initTests();
var web3 = new Web3();
web3.setProvider(new web3.providers.HttpProvider("http://<node_host>:<node_port>"));
EmbarkSpec.web3 = web3;

describe("SimpleStorage", function() {
  before(function(done) {
        EmbarkSpec.deployAll(done);

note you need to replace "http://<node_host>:<node_port>"

thank you!! It is working, i am able to test against the privatenet node. I would continue to use the simulator to test. It's a great tool.


PWM

https://github.com/STMicroelectronics/STM32CubeF3/tree/master/Projects/STM32F303K8-Nucleo/Examples/TIM/TIM_PWMOutput

https://moons.link/post-632/#outline__2

https://note.com/aglio26/n/n6f67b780ed82


TCP Fast-Open.   Now that Linux kernels enable this by default (and web servers likely won't be ...

TCP Fast-Open.
Now that Linux kernels enable this by default (and web servers likely won't be far behind in requesting it). Lets see what browsers will get the ~5% performance improvement by requesting using TFO.

This issue was imported from Google Moderator
Moderator votes: +3
Issue added by snadrus on 2014-01-21
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

+1

+1

was this ever tracked ?


Improve Machine Learning learning plan

-reorganize resources
-pair down existing resources that are redundant
-add video(s)
-add additional relevant content

Hi Lauren -- good ideas!  Do you have specific changes in mind or are you able to make any required changes/additions?  Any contributions would be appreciated!

Hey Brian! My team is working on this now, and we'll submit a PR probably next week!

That's great, your expertise is appreciated!  We're happy to help any way we can, just reach out.


Changelog

I like to read more about webpack and how it's internal works.
But because the docs are in heavy development I never know if some new docs are added.
Is there a way to make some notes in a changelog file or so some bigger changes?

You could read the commits? I don't think we'll ever have time to make a changelog for docs...

Yeah sure I can read the commits on every repo ;) but okey, I understand it that this would be to much extra work than

Is there a tagging structure or minimum required amount of updates that would involve a full change log? Perhaps chunking issues into block of 10 or so that are tagged as 'major' or 'significant' updates or possible even just a 'last updated' auto block that goes under the title block and for sections that involve loaders || modules || plugin with a 'last updated' comparison next to one another?
For example:
css-loader
Latest Updates:

This Page
loader

[date]
[date]

Although, I do see how this could become quite a mess to maintain but just throwing it out there...

Yea idk about this one, @rouzbeh84 something like that might not be bad but, as @SpaceK33z mentioned, there's a ton of other work to be done that I would say is much higher priority than this. To get "high-level" overview of the most recent stuff going on in the docs I would say options include:

Watching this repository
Subscribing to issues that concern some piece of documentation you're waiting on
Checking the most recent commits

You can also use the github/git history of an individual file such as this one to get an idea of what's changed in any particular place.
Personally, I also wouldn't be opposed to standardizing my commits to this repository and using some tool to auto-generate a changelog but that might be fairly hard to manage as we have many different contributors opening all different kinds of PRs.
I'm going to close this for now but maybe it's something we can loop back to down the road.


Simple query stream doesn't EOF properly

Description
https://github.com/glaredb/glaredb/blob/bd684254b29fcff0e4bcafd8f4deab1ae1a61d59/crates/rpcsrv/src/handler.rs#L378-L416
Causes context deadline exceeded on cloud.

@scsmithr I wonder if it'd be easier to just use the go flightsql driver for cloud?
The following works on this branch
package main

import (
	"database/sql"
	_ "github.com/apache/arrow-adbc/go/adbc/sqldriver/flightsql"
)

func main() {
	db, err := sql.Open("flightsql", "uri=grpc://<IP_ADDRESS>:6789")
	if err != nil {
		panic(err)
	}
	defer db.Close()

	if err = db.Ping(); err != nil {
		panic(err)
	}

	rows, err := db.Query("SELECT registration_dttm from './testdata/csv/userdata1.csv' limit 1")
	if err != nil {
		panic(err)
	}
	columns, err := rows.Columns()
	if err != nil {
		panic(err)
	}

	println(columns[0])

}

This fix here is actually super easy.
We can switch to flight sql once it's ready. The code being written in https://github.com/GlareDB/cloud/pull/2527 would still be needed--it would be easy to swap the client out whenever.


md-on-deselect and md-on-select called multiple times

When clicking the select all checkbox, the md-on-select function is called for every row in the table. Should the behaviour be just once? The reason being for my example, I trigger and graph update based on selected items. So each time a user selects an item it updates the graph, but when you select all it gets triggered multiple times, there are some promises that a used to get relevant data for the graphs and it causes double counting on some items.
I noticed that a simple  $watchCollection could be used and that only gets triggered once for when an item is selected and deselected or when you select all or deselect.
$scope.$watchCollection('selectedItems', function (newNames, oldNames) {
      console.log('items selected');
    });

When you select all items, every item that is not already selected or disabled will be selected. Therefore md-on-select will be called for every item that is not already selected or is disabled. I think this is the expected behavior for most people. If you are "doubt counting" items, that seems like a fault in your logic because md-on-select should never be called for an item that is already selected.
If you just want to know when there is a change in selected items then $watchCollection could work.

Thanks, yeah I think for my situation $watchCollection works better. Just wanted to confirm this was the expected behaviour.
You are right it will most likely be something in my logic. It's calling multiple promises based on selected items each time items are selected, I need to update my logic to cancel in current promises each time it's called.


[cluster-test] More debug information in txn emitter

@bors-libra delegate+

:v: @andll can now approve this pull request

@bors-libra r=ankushagarwal

:pushpin: Commit b756cc8 has been approved by ankushagarwal

:hourglass: Testing commit b756cc88d541e7e4ea3bca5ebae7144a0df4bdcc with merge 380470e48b804f35c58f875dfdea125a0ca44e7a...


[LIVY-979][Dev] A helm-based integration environment for Livy

This helps deploy Livy on Kubernetes on a local machine. For debugging Livy on Kubernetes as a standalone setup, we need Apache Spark and Apache Livy deployed within the Kubernetes environment.
What changes were proposed in this pull request?
JIRA: LIVY-979
How was this patch tested?
Tested by deploying the Helm chart on a standalone machine.

Thank you for the submission and reviews! However some of the newly added files are missing the Apache license headers and I am not sure if this is OK to be merged in its current form. The policy I am referring to is https://apache.org/legal/src-headers.html


Fix example app and upgrade packages

Issue: https://mxcom.atlassian.net/browse/CT-917
This MR does the following:

Upgrade react-native from 0.70.3 to 0.75.3(The most recent stable version) using the the React native upgrade helper

Upgrade @mxenabled/widget-post-message-definitions to 1.4.0(the latest version)

Fix the example app

Testing instructions

Note: Follow this setup guide if you don't have xcode or android studio setup

Step 1: Run the setup command
npx mx-widget-sdk-setup

Step 2: Start the Proxy Server
In order to make API calls from the widget, you will need to set up a proxy server.
Open a new terminal from the root of the react-native-widget-sdk project and run the following command to start the  the proxy server:
npm run example:server

Enter Int or Prod credentials as prompted and keep the proxy server running as you run the react-native app.
Step 3: Start the Metro Server
You will need to start Metro, the JavaScript bundler that ships with React Native.
To start Metro, run the following command from the root of react-native-widget-sdk project:
npm example:start

Step 4: Start your Application
Let Metro Bundler run in its own terminal. Open a new terminal from the root of the react-native-widget-sdk project. Run the following command to start the  Android or iOS app:
For Android
cd example
npm run android

For iOS
cd example
npm run ios

If everything is set up correctly, you should see the example app running in your Android Emulator or iOS Simulator shortly provided you have set up your emulator/simulator correctly.
This is one way to run your app — you can also run it directly from within Android Studio and Xcode respectively.

do you know if there is a way to create custom widgets. That is to say to be able to change the interface without the need to implement everything through api @emilysallstrom @mwclemy

I'm not sure how you would create a custom widget without implementing our api. Clients that create their own widget experiences rely on our api to connect to an end user's account and fetch data and I don't see how you would get access to those data without using our api. Unless maybe I'm misunderstanding your question.