Sw 6261 add logging to workflow

Codecov Report
Base: 51.47% // Head: 50.44% // Decreases project coverage by -1.02% :warning:

Coverage data is based on head (a386e67) compared to base (3ebca8d).
Patch coverage: 44.64% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #252      +/-   ##
==========================================
- Coverage   51.47%   50.44%   -1.03%
==========================================
  Files          13       13
  Lines         509      559      +50
==========================================
+ Hits          262      282      +20
- Misses        217      245      +28
- Partials       30       32       +2

Impacted Files
Coverage Δ

internal/sirius/get_task_list.go
46.83% <0.00%> (-1.22%)
:arrow_down:

internal/sirius/get_teams_for_selection.go
18.18% <0.00%> (-0.87%)
:arrow_down:

main.go
0.00% <0.00%> (ø)

internal/server/workflow.go
59.37% <26.66%> (-11.50%)
:arrow_down:

internal/sirius/client.go
65.62% <50.00%> (-5.21%)
:arrow_down:

internal/sirius/assign_tasks_to_casemanager.go
66.66% <100.00%> (+3.50%)
:arrow_up:

internal/sirius/get_applied_filters.go
100.00% <100.00%> (ø)

internal/sirius/get_assignees_for_filter.go
68.57% <100.00%> (+1.90%)
:arrow_up:

internal/sirius/get_current_user_details.go
50.00% <100.00%> (+7.14%)
:arrow_up:

internal/sirius/get_page_details.go
92.85% <100.00%> (+0.26%)
:arrow_up:

... and 1 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Incompatible with 2.2.0

Your requirements could not be resolved to an installable set of packages.
--

Problem 1
- Installation request for iazel/module-regen-product-url dev-master -> satisfiable by iazel/module-regen-product-url[dev-master].
- Conclusion: remove magento/framework 101.0.0
- magento/product-community-edition 2.2.0 requires magento/framework 101.0.0 -> satisfiable by magento/framework[101.0.0].
- magento/product-community-edition 2.2.0 requires magento/framework 101.0.0 -> satisfiable by magento/framework[101.0.0].
- Conclusion: don't install magento/framework 101.0.0
- Installation request for magento/product-community-edition 2.2.0 -> satisfiable by magento/product-community-edition[2.2.0].

Please fix this issue.

@AlterWeb
I created a fork which you could use. (version <IP_ADDRESS>)
https://github.com/SpikeSpade/magento2-regenurl

This is fixed in my fork, amongst other issues https://github.com/peterjaap/magento2-regenurl


Do you consider adding a source map feature

Do you consider adding a source map feature, as it is difficult to locate large files

Yes. We can consider to support it.


Rewrite Authelia client using React

This work will make Authelia visually more attractive and professional and will help develop a management interface required by application passwords or JWT tokens issuance and revocation.

This will enable the implementation of https://github.com/clems4ever/authelia/issues/303.


Process about rel path

⬆ Condition
$ incoming -i "vidoe.mkv" -o "video.mp4"
# or
$ incoming -i "vidoe.mkv" -o "../output"

Possible? or just abs path?

Pull and test it


PCIe x1 compatibility

Hi,
Can Vercolib be used with a PCIe 1x Gen2 FPGA ?
Regards!

Hi,
currenly we only have a ready-to-use endpoint configuration for 7 Series FPGAs with 8 lanes.
However, as long as you're using an FPGA that is compatible with Xilinx' Gen2 IP-Core, it's probably fairly straightforward to adapt the endpoint module for single lane setups.

Thank you for the answer !


[MINOR][PYTHON][DOC] Setting toggle-prompt button in docs to user-select:none

What changes were proposed in this pull request?
Added a css tag for the button that toggles the python '>>>' interpreter prefix on and off.
This tag is called 'user-select' and was set to 'none'
Why are the changes needed?

This prevents the user to highlight the button, a small enhancement to the user experience.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Building the docs on local.

Merged to master.

Can one of the admins verify this patch?


Dockerfile: update base image

What is changed and how it works?

Issue Number: Close #16032
What's Changed:
Use rocklinux:9 as base image. Because it has fewer security issues than ubi 8.6.
Check List
Tests

No code

Release note
None

/merge


Do I have to use client-only?

I notice in the example you use <client-only>. Is there any way this works with SSR? When I try to I get a hydration mismatch...

Hey @aonghas
unfortunately since Vue 3.4^ there's no way other than wrapping the component in ClientOnly with some loading state while it's hydrating.

<template>

Universal Render

Calendar

    <ClientOnly>
      <VCalendar v-model="date" />

      <template #fallback> loading... </template>
    </ClientOnly>

Date Picker

    <ClientOnly>
      <VDatePicker v-model="date" :attributes="attrs" />

      <template #fallback> loading... </template>
    </ClientOnly>

</template>

it's an issue from vcalendar itself as it uses vue-screen-utils package and it doesn't work in ssr.
If you're using the DatePicker component with Popper like in this example where the component is hidden initially I guess it won't be an issue.
I have looked for alternatives and in terms of features the only one that comes close is radix-vue calendar component but it is still in alpha.
Another solutions that looked appealing at first glance but one the bundle size is huge and the other is still in beta

Schedule-X calendar also needs to be wrapped in ClientOnly
qcalendar it's from Quasar

Fair, thanks for replying! Didn't know about client-only fallback so that's handy. I'll keep an eye on radix Vue in the meantime!


feat(progress bar, notification): colour token updates

Summary
Updated colour tokens as per the UX.
ADO Story or GitHub Issue Link
TASK 2003578
TASK 2003583
Figma Link
Progress bar
Notification
Inline notification
Toast notification
Notes
Updated the colour tokens for the following components

Progress bar
Notification

Checklist

[x] Used Conventional Commit messages as outlined in the contributing guide.

[ ] Noted breaking changes (if any).

[ ] Documented/updated all props, events, slots, parts, etc with JSDoc.

[ ] Ran the analyze command to update Storybook docs.

[ ] Added/updated Stories with controls to cover all variants.
[ ] Ran test locally to address any failures.
[ ] Added/updated the Figma link for the Story's Design tab.
[ ] Added any new component exports to the src/index.ts file

In the Notifications, the X buttons look wrong. I don't think we can use the button component there anymore with the new styles. Maybe we should copy the Modal/Side Drawer X button? @wbarbee created a mixin for the styles for that yesterday.
In the progressBar files, it seems like all of your indentation has changed from 2 spaces to 4 spaces. Might want to see what's causing that, as it creates fake changes that make it hard to review.

Will make the required changes.
The indentation was changed to 2 spaces as part of this PR: https://github.com/kyndryl-design-system/shidoka-applications/pull/268/files#diff-555b2eb8ccd2cc20430cf10227122ea0e8a12c674ae00ce7d0a62dbe80b383f4. So, will first fix the indentation, merge it to next and then make changes to that, so that the colour token changes are easily visible.

@brian-patrick-3, I've fixed the indentation issue.

Hi @jaideep08,
Inline notification - Link text is not visible on click
Notification - Figma has some light green background, but UI has white different background - is this expected?

Figma:

The boarder of close is not clearly visible for 2 toast messages

Hi @jaideep08, Inline notification - Link text is not visible on click Notification - Figma has some light green background, but UI has white different background - is this expected?  Figma:

The link issue, I'll have to check with the UX team.
Yes, the background colour of the notification depends on the tagStatus prop value. The one seen on Figma is the success variant while the one in the storybook screenshot is info.

The boarder of close is not clearly visible for 2 toast messages

I'll check with the UX team


Can't run an oak server simultaneously with webview

I'm having a strange issue where calling webview.run() prevents my oak server from working.
import { Application } from 'https://deno.land/x/oak/mod.ts';
import { WebView } from 'https://deno.land/x/webview/mod.ts';
import router from './routes.ts';

const app = new Application();
app.use(router.routes());
app.use(router.allowedMethods());

const webview = new WebView(...);
webview.run();  //THIS LINE

await app.listen({ port: 8080 });

I'm using Postman to test the API on port 8080 on a simple /api/test endpoint that returns a string.
With webview.run(),  the API hangs and eventually times out.
Commenting out webview.run() and suddenly the API works.
I also tried calling webview.run() in oak's "listen" event handler.
I also tried await Promise.all([webview.run(), app.listen(...)])
Not sure what one has to do with the other. Am I missing something very basic here?

Closing as duplicate https://github.com/eliassjogreen/deno_webview/issues/5


Redirect (301) aren't followed

Hi,
the server is configured to redirect all traffic from http to https.
Example:
[http://v22017084844652188.powersrv.de/schemas/test.json](HTTP address).
Calling this
parser.dereference("http://v22017084844652188.powersrv.de/schemas/test.json")
      .then((value) => {
        console.log("Schema fetched...");
        this.parserSchema = value;
      })
      .catch(error => {
        console.log("Schema not fetched...");
        console.log(error);
        this.parserError = error;
      });

I'm getting the following error (running into a CORS problem):
Failed to load http://v22017084844652188.powersrv.de/schemas/test.json: Redirect from 'http://v22017084844652188.powersrv.de/schemas/test.json' to 'https://v22017084844652188.powersrv.de/schemas/test.json' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8100' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

A redirect has to be detected and the the ressource should be dereferenced!
@BigstickCarpet Should the redirects handled in http.js?

@big-r81 - Thanks for opening this issue.
Yes, the redirects should be handled in http.js.  Is this only happening in Node, or also in web browsers?  I'm pretty sure that web browsers automatically follow redirects, so we only need to fix this for Node.  If that's the case, then we can just use follow-redirects as a drop-in replacement for the default http and https modules.

Hi,
if i open the url in the browser, i get redirected to https.
I use your library in an ionic/angular project and there i running into the problem...

@BigstickCarpet
I'm not a node guru, so i tried the following:

clone this repo
changed http.js

var http = require('follow-redirects').http,
    https = require('follow-redirects').https,
    ...

run npm run build (FYI: it will break the redirect tests...)
npm link (in the json-schema-ref-parser directory)
in my own project dir npm link json-schema-ref-parser
starting my app, but the same result...

@big-r81 - ok, thanks for the analysis.  Looks like this isn't going to be as straightforward as I had hoped.  :-/


Provision Workflow should use the correct values for numvcpus

Currently, through serendipity, the values for :number_of_cpus and the value for :number_of_sockets are correct for miq_provision_infra_workflow.rb and miq_provision_vmware_workflow.rb.
But, this assignment should really be changed to:
:number_of_cpus => vm.hardware.logical_cpus,
:number_of_sockets => vm.hardware.numvcpus,

The reason is still works right now is that we assume that all VMWare vms have one socket.  So, the calculation that happens later is an identity operation and has no effect.
If VMWare starts reporting socket information, this could change and we might start showing the wrong values.

@blomquisg is this still relevant?
https://github.com/ManageIQ/manageiq-providers-vmware/blob/774c48510e06c093b9366cd848d9bcecf4a885d1/app/models/manageiq/providers/vmware/infra_manager/vm/reconfigure.rb#L57-L58

@blomquisg can you close this issue.


Implement a Screen1 AutoscaleImages property

Describe the desired feature
Due to possible resource limitations of the device, App Inventor has always scaled images down. This is done by computing a scaling factor in MediaUtil. As devices have increased the amount of RAM available to apps, it seems reasonable to allow people to disable this "feature" in order to use high resolution images in their apps. I propose that we add a AutoscaleImages property to Screen1, defaulting to true for compatibility reasons, that developers can use to turn off scaling of images to take advantage of higher resolution displays.
Give an example of how this feature would be used
Anyone showing camera images, etc. could use this to show the full resolution image rather than a scaled version.
Why doesn't the current App Inventor system address this use case?
App Inventor gives no option to control this behavior, but people expect that if they provide a high res image it will show accordingly. Instead, it is scaled down and may become "fuzzy".
Why is this feature beneficial to App Inventor's educational mission?
While there isn't a direct benefit, students may appreciate having the ability to show higher quality images and not have their apps look "scaled down" compared to other apps.

@ewpatton I would like to work on this issue.

Great. Let us know if you have any questions.
Sent from my iPhone

On Feb 5, 2020, at 05:17, Suyash Jain<EMAIL_ADDRESS>wrote:
@ewpatton I would like to work on this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ewpatton I've added the required property to the form component.
Here's the link to my changes - link
But, during runtime, I'm getting the following error whenever I try to disable the autoscale feature.

Can you please help me out?
Thank you in advance.

@jsuyash1514 After you've compiled the system, make sure to install the companion from build/buildserver/ onto your device, otherwise you won't have the new functionality.

Hi all,
i 'm having an issue as i upload a FHD (1080x1920) images to be (Screen BackgroundImage) for a multiple screen app in app inventor but their quality get lowered automatically ,whether the sizing was Fixed or Responsive .is there a way or even a work around to get the original quality of the background?
note:
tested on AppInventor release nb186


activationEvents onLanguage doesn't work with custom language

VSCode Version: Version 1.7.2
OS Version: OSX 10.9.5

Steps to Reproduce:

I've downloaded client+server extension example from https://github.com/Microsoft/vscode-languageserver-node-example
After this I've added Gherkin language support via:

"languages": [
			{
				"id": "feature",
				"aliases": [
					"feature",
					"gherkin",
					"Gherkin",
					"cucumber"
				],
				"extensions": [
					".feature"
				],
				"configuration": "./language-configuration.json"
			}
		]

and
"grammars": [
			{
				"language": "feature",
				"scopeName": "text.gherkin.feature",
				"path": "./syntaxes/feature.tmLanguage"
			}
		]

Current Result:
After these steps, syntax highlighting working properly. Also, extension looks good for the plain text file type ('typescript' word is highlighting with error). But, it doesn't work for the 'feature' ("activationEvents": ["onLanguage:feature"]) - see screens.

Was unable to find solution on this. Looks like an issue. Please assist. Thank you.

Issue was related to wrong documentselector during new LanguageClient creation.


Cannot read property STATE_NONE of undefined

Configuration
Run react-native info in your project and share the content.
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Memory: 3.55 GB / 11.92 GB
Binaries:
Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-183.6<IP_ADDRESS>22156
What react-native-track-player version are you using?
1.1.8
Issue
I have tried to link automatically and I have tried to link manually as well but in both cases i get "Cannot read property STATE_NONE of undefined".
Using:
"react": "16.8.6",
"react-native": "0.60.5",

Pretty sure i gave up and started using nativescript.
On Fri, Sep 4, 2020, 3:57 PM musangowope<EMAIL_ADDRESS>wrote:

@c0bra https://github.com/c0bra did you ever find a solution for the
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-kit/react-native-track-player/issues/804#issuecomment-687379768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZULZ6Z5KFVZX3FWZF7I3SEFICJANCNFSM4JWR7CSQ
.


Refreshing solution explorer

Have you found a way to have the generated .sql file included in the project so it is immediately visible in Solution Explorer without manually right-clicking / include in project every time?
This approach gets close but still requires a refresh of the explorer:
<ItemGroup>
    <Content Include="Definitions\**\*.sql" />
</ItemGroup>

Actually, just saw in your video how this is intentional. Maybe this is something we can add as a switch to the  Start-Migrations cmd?

Actually, I am totally open to having these included in the project by default.  I would surely welcome a PR that does it.


Upgrade to Terraform 1.0.x

Summary
As an engineer
I want to use up-to-date version of tools
So that I can take advantage of the latest improvements
Context
The latest stable Terraform version is v1.0.5 (as of 2021-08-19). However, the component still defaults to Terraform v0.14.8. We should update the component to default to v1.0.5 after verifying that the OCP4 modules (https://github.com/appuio/terraform-openshift4-cloudscale and https://github.com/appuio/terraform-openshift4-exoscale) work with v1.0.5.
I'd propose that we switch to the registry.gitlab.com/gitlab-org/terraform-images/releases/terraform, which has tags that actually correspond to a Terraform version in contrast to the registry.gitlab.com/gitlab-org/terraform-images/releases/0.14 image which we currently use, where tag v0.10.0 doesn't correspond to the Terraform 0.14 patch version (actual Terraform version in registry.gitlab.com/gitlab-org/terraform-images/releases/0.14:v0.10.0 is v0.14.8).
Out of Scope

Large-scale refactoring of Terraform modules

Further links

Current latest Terraform version can be seen on https://www.terraform.io/downloads.html
Available GitLab Terraform image versions can be checked on https://gitlab.com/gitlab-org/terraform-images/container_registry/1803074

Acceptance criteria

Given that I include this component for my cluster, I'm using Terraform v1.0.x unless I override the Terraform image.

Implementation Ideas

Update default image version

Currently (2022-05-25) the latest Terraform version is v1.2.1. Please check whether it's feasible to directly migrate to v1.2


More issue template updates

Fast follow to #39354.
Also renames to use numbers to order templates instead of letters.

@gewarren
I like what's here, but you also need to change the name of the issue template in our docfx.json here
Otherwise, the feedback control won't work.

@gewarren
I like what's here, but you also need to change the name of the issue template in our docfx.json here
Otherwise, the feedback control won't work.

@BillWagner What do I need to update there?

@BillWagner What do I need to update there? I didn't change the name of the z-customer-feedback.yml template.

You're right. I looked at the comment, but didn't notice that the first and last weren't renamed.
Approving.


Propagate retries parameter to the client

retries is never passed to the client.send
should be retries instead of retires (typo)

verified statically  typo is now fixed


Start on the Github rewrite, with [GithubPullRequestCheckState]

The GitHub service family is the largest, and as yet untouched by our service rewrite. I thought I would start the process by tackling one service.
This pull request has a few things going on:

Rename pull-request-status to pull-request-check-state. We have another badge called pull request status. It seems like the checks are called one thing in the UI and another thing in the API, which is unfortunate. If other folks have strong feelings about the name, I’ll defer.
Move its tests and tighten up the syntax.
Move its badge examples including the doc string.
Add a new helper errorMessagesFor to use in the new services in place of githubCheckErrorResponse. It seems like we didn’t really use the errorMessages parameter to githubCheckErrorResponse, so I pared this down. I’m not sure if this is the function we’ll ultimately want, but it seems like a good place to start.
Pull fetch code I know we use in other places into github-common-fetch. As in the PR I just opened for azure-devops, this takes a functional approach to the shared code, which is more direct, nimble, and easy to reason about than inheritance.
Create GithubAuthService which functions identically to BaseJsonService, except for one thing, which is that it uses the token pool. I accomplished this by adding a _requestFetcher property to BaseService, which is initialized to sendAndCacheRequest in the constructor, and can be overridden in subclasses. Since we weren’t using _sendAndCacheRequest directly except in BaseService and tests, I removed that property. I like this approach to patching in the GitHub auth because it’s very simple and creates no new API exposure. However, the way we’re doing the dependency injection feels a bit odd. Maybe the eventual refactor of request-handler would be a godo time to revisit this.

The GitHub requests go through many, many layers of indirection at this point. Later on it would be good to shave some of these off, perhaps once the legacy GitHub services have been converted, or when all the services are done and we can take another look at the base service hierarchy. The work in #2021 and #1205 is also related.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

this is.. really strange. The change in 3173c2e looks like it should work but it seems to have not worked and somehow broken the other example:

I am very confused by this

Ah… that was a regression in #2240. It's unrelated. I'll open a new PR with a fix.


Release Google.Cloud.Speech.V1 version 3.4.0

Changes in this release:
New features

Voice Activity Detection: adding speech event time and speech event type (commit dda7fc9)

Documentation improvements

Clarified boost usage (commit 195e99a)

Created release for Google.Cloud.Speech.V1-3.4.0


Make the messaging around contribution in GitHub and the website consistent

This issue is now a dupe of serveral other issues including:
#265 #264 #74


How to connect ESP-32

Thank you for working on such an important project,
I am very new to displays and ESP-32, Could you please help me to connect my display and run a simple test

and my board :

Thank you so much

Wireing

TFT

ESP32
ESP32S2/S3

LDC_RST
--
GPIO32
GPIO45
*1

LDC_CS
--
GPIO33
GPIO42
*1

LDC_RS
--
GPIO15
GPIO41
*1

LDC_WR
--
GPIO4
GPIO40
*1

LDC_RD
--
GPIO2
GPIO39
*1

LDC_D0
--
GPIO12
GPIO1
*1 *2

LDC_D1
--
GPIO13
GPIO2
*1 *2

LDC_D2
--
GPIO26
GPIO3
*1 *2

LDC_D3
--
GPIO25
GPIO4
*1 *2

LDC_D4
--
GPIO17
GPIO5
*1 *2

LDC_D5
--
GPIO16
GPIO6
*1 *2

LDC_D6
--
GPIO27
GPIO7
*1 *2

LDC_D7
--
GPIO14
GPIO8
*1 *2

5V
--
5V
5V
*3

3.3V
--
3.3V
3.3V
*3

GND
--
GND
GND

(*1)
You can change any GPIO using menuconfig.

(*2)
When using REGISTER I/O parallel, GPIO from D0 to D7 is 1 to 31.(GPIO0 is boot mode pin)
(*3)
With a regulator (mostly AMS1117) is on the back, the supply voltage is 5V.
With a regulator is NOT on the back, the supply voltage is 3.3V.

Since I don’t have any other external devices attached, I would be happy with the default one.
Could you kindly share some example for text and some animations ( like fire or wind )
really appreciate it

There is no animations.
There is example for text.
Wireing

TFT

ESP32
ESP32S2/S3

LDC_RST
--
GPIO32
GPIO45
*1

LDC_CS
--
GPIO33
GPIO42
*1

LDC_RS
--
GPIO15
GPIO41
*1

LDC_WR
--
GPIO4
GPIO40
*1

LDC_RD
--
GPIO2
GPIO39
*1

LDC_D0
--
GPIO12
GPIO1
*1 *2

LDC_D1
--
GPIO13
GPIO2
*1 *2

LDC_D2
--
GPIO26
GPIO3
*1 *2

LDC_D3
--
GPIO25
GPIO4
*1 *2

LDC_D4
--
GPIO17
GPIO5
*1 *2

LDC_D5
--
GPIO16
GPIO6
*1 *2

LDC_D6
--
GPIO27
GPIO7
*1 *2

LDC_D7
--
GPIO14
GPIO8
*1 *2

5V
--
5V
5V
*3

3.3V
--
3.3V
3.3V
*3

GND
--
GND
GND

(*1)
You can change any GPIO using menuconfig.

(*2)
When using REGISTER I/O parallel, GPIO from D0 to D7 is 1 to 31.(GPIO0 is boot mode pin)
(*3)
With a regulator (mostly AMS1117) is on the back, the supply voltage is 5V.
With a regulator is NOT on the back, the supply voltage is 3.3V.

Thank you so much .


Alternate visualization for TDD

This PR adds a chart builder and provides a template for given sets of field.
The chart builder is used in TDD to provide alternate visualizations
P0

[x] Fix type errors and tests
[x] Add tabs and update icons for chart selection
[ ] Match the color for dimensions and charts
[ ] Add support for comparisons

P1

[ ] Add interactions for stacked area charts
[ ] Custom tooltip on hover for all charts
[ ] Bidirectional hover highlighting between charts and table

@ericpgreen2 Marking this as ready for review. Some P0 items are still remaining but for the sake of reviewability, will be making those changes in a separated PR branched from this.


Analyze and categorize attack on PyPI package ctx

https://blog.sonatype.com/pypi-package-ctx-compromised-are-you-at-risk

Attack vector Distribute as Maintainer fits for the attack on PyPI package ctx, however, little information is given to identify any subvector. Similarly, attack vector Contribute as Maintainer fits for the attack on PHP package phpass.
At the end of the blog, there are more examples provided than can also be categorized:

PyPI package pymafka
npm package colors-2.0
Rust package rustdecimal


fixed the issue

Description

Fixes issue number <#Issue number>

Checklist:

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Yes, it's participating.
I'm adding the "hacktoberfest accepted" label to it so that it can count for your contribution and show up on your profile on Hacktoberfest website, but we can only merge it after you fix the responsiveness issue.

Ok cool😊

I made the required changes. Pls see and do let me know if there is still any problem. Thank you!

Good job @a-muk 👏👏. Thanks for contributing 😊


[SMALLFIX] Deserialize entries in masters other than FileSystemMaster

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4636/
Test PASSed.

LGTM


Update collectd plugin to write values under the field "value"

This is a fix for #2412.  I'm a golang newb, so I'll describe my testing procedure to make sure it's sufficient.

Forked repo
Used go get x to install each dependency
Ran go test and received PASS
Made fix
Ran go test and received PASS

Simple change, but this was holding us up.  Thanks.

I would think that this test should be failing now:
https://github.com/josh-padnick/influxdb/blob/master/collectd/collectd_test.go#L186
The fact it was passing, and that this change didn't make it fail means the test likely needs to be fixed as well.
I'm not sure what tools the bug is referencing that expects it to always be value but I'm open to it.  It feels like this should probably be a configuration option though, unless this is 100% always a true case regardless of tools being used.
I would expect the following to be the norm unless in the config someone were to specify it differently.  However, I'm not a collectd expert, so I could be wrong. @otoolep @jwilder do either of you know?
fields[data.Values[i].Name] = data.Values[i].Value

Let me know if you want to take another pass at this or need any help.
This does appear to be a bug.  Good catch and thanks for your efforts!

@corylanou I've updated the test to include a case that now fails.  See latest commit.  This isn't yet ready for merging, though, because this test is failing now.
Regarding what's motivating this change in the first place, for our team, it came down to what Grafana is expecting, which I assume will be the overwhelmingly popular choice for dashboard.  Grafana assumes that every metric name's value is stored in a field called value, rather than a field like disk_read.  This means that you have to manually edit the query to get it working.
Certainly, Grafana could change its behavior, but since a measured named disk_read that has a field named disk_read seems redundant, I'm inclined to change the collectd plugin, not Grafana.
I'm not sure how to proceed from here, and am happy to pass this PR on to @kimor79 or someone else w/ more experience w/ the InfluxDB code base.

Thanks @josh-padnick -- this is definitely an issue in the code. It should be using value. I'll take a look at this.

Closing in favour of https://github.com/influxdb/influxdb/pull/2460


Asset url

Hi futhr,
Nice work on this gem! I was trying to add the following to your _print.pdf.prawn template:
image asset_url 'logo.svg' , :at => [0,720], :scale => logo_scale
But i get a "image not found", while the url (http://localhost:3000/assets/logo.svg) actually exist.
Do you know how to add this image?

Try assets/images
Sent from my iPhone

On 02 Mar 2015, at 11:35, Paul Huisman<EMAIL_ADDRESS>wrote:
Hi futhr,
Nice work on this gem! I was trying to add the following to your _print.pdf.prawn template:
im = asset_url 'logo.svg'
image im , :at => [0,720], :scale => logo_scale
But i get a "image not found", while the url (http://localhost:3000/assets/logo.svg) actually exist.
—
Reply to this email directly or view it on GitHub.

Thanks for your swift response. I think it might have something to do with http://stackoverflow.com/questions/11560455/prawn-import-image-from-url.
I do not think the solution applies to my _print.pdf.prawn template though.

Solved it with using the correct method name:
Spree::PrintInvoice::Config.set(print_invoice_logo_path: 'logo.jpg' )
In the documentation it shows the wrong method name, 'logo_path'

ah, that makes sense! Thanks. Will update the readme.

Not sure how that should actually work? What branch are you using? It's logo_path on 3-0-stable

Ah, my bad.. was looking at the wrong README. I'm on 2-3-stable. Sorry!


Can't reach server running inside Docker container

Hi! I'm wrapping my sphinx dev environment inside a Docker container to make it portable and easier to use for other users and I'm interested on adding sphinx-autobuild into it.
Up to now, I was able to run a python -m http.server inside the container and access it from my host machine, no problem.
I've made some tries with sphinx-autobuild and the building part works great but I can't access the web server, even though I've EXPOSEd the port I'm using in my Dockerfile and I'm binding a host port to it, as with the http.server module.
It seems that the server the sphinx-autobuild module is starting isn't getting my hosts requests.
Any idea on how to run it on debug mode, or have some logs to look further into this issue?

@ggalmazor I have the same problem and while --host <IP_ADDRESS> solves it, the page no longer auto-refreshes when rebuilt. I am using a Windows host and Windows docker container. I don't see a --poll option as you have listed. Did auto-refreshing work for you?


question: in napari Python console, how can I (programmatically) stream the newly acquired images to the viewer?

Hello,
After launching napari-MM and verifying that MM configuration and camera etc. worked, I opened its Python console and obtained a reference mmc to the same core object using the CMMCorePlus.instance call (verified with mmc.getFocusDevice for example). However, when I then ran mmc.snapImage or mmc.run_mda, I didn't see the default image viewer updating with the newly acquired images. What other steps are needed? Thanks!
-lin

mmc.snapImage

This one doesn't immediately show anything is because (perhaps surprisingly) it doesn't emit any event that napari is listening to;  mmc.snap() will however (it's a combination of snapImage() and getImage(), added in pymmcore-plus)
this confusion is also discussed in: https://github.com/pymmcore-plus/pymmcore-plus/issues/144

mmc.run_mda

This one doesn't work at the moment because, currently, napari-micromanager only pays attention to MDAs that it started itself.  This is a bit of an arbitrary decision, and probably overly "cautious".
It's caused by this line right here:
https://github.com/pymmcore-plus/napari-micromanager/blob/ebddc0aee75d85011ac07ff3365d513c9abd28e4/src/napari_micromanager/_mda_handler.py#L194C1-L196C30
it would be very easy to change that behavior.  If you want to "hack" it to just work for you, all you need to do is add a little metadata to the MDASequence:
from useq import MDASequence
from napari_micromanager._mda_meta import SequenceMeta

fake_meta = {'napari_mm_sequence_meta': SequenceMeta()}
core.run_mda(MDASequence(time_plan={'loops': 5, 'interval': 0.1}, metadata= fake_meta))

what do we think, lin and @fdrgsp, should napari-micromanager just show all running mdas? regardless of how they were started?

I edited the title here to say "programmatically"... note that if you hit the snap or live buttons:

or press the MDA button to open the MDA widget:

and then run an MDA with

it will populate the viewer with the images

Thank you! The suggested hack kind of works. I had to call the fake_meta = ... line every time before run_mda(...) though for the viewer to update with incoming images. If I run_mda(...) consecutively, the viewer's z slide moves, but the display remains black.
I vote for napari showing all MDAs regardless of the origin.


Fix /userinfo token expiration

Apparently the token used by /userinfo now expires after one day and it's not refreshed. What we can do is:

Fix the refresh mechanism
Replace the id_token with a call to the Auth0 /userinfo endpoint (the recommended way)

Update: tweaking token expiration (in particular, setting id_token's expiration to be greater than the access_token expiration) should fix the issue already.
We might still want to do 2 since I think it's a better way and will be required if we move the tokens from the cookie to the Authorization header.  I should have a PR ready for it soon, the team can decide which solution we prefer to adopt for now.


Add telemetry on reminder and broadcast features

Summary
Add missing information in the telemetry data.
@Adovenmuehle, one of the fields I just added to the incident structure (ReminderTimerSeconds) is only present in a specific event, as it does not make much sense to send it with the others that relate to incidents. Is that ok for your data processing, or do you guys need us to always add the same fields for the events that refer to the same data type?
Ticket Link
https://mattermost.atlassian.net/browse/MM-32051

@agarciamontoro, can you plan to update the documentation to reflect the new telemetry additions?

@agarciamontoro, can you plan to update the documentation to reflect the new telemetry additions?

@agarciamontoro it's fine to have fields that are specific to only one event. 👍

@agarciamontoro it's fine to have fields that are specific to only one event. 👍

@agarciamontoro, can you plan to update the documentation to reflect the new telemetry additions?

@lieut-data, heads-up that I created https://mattermost.atlassian.net/browse/MM-32353 for this sprint.

@agarciamontoro, can you plan to update the documentation to reflect the new telemetry additions?

@lieut-data, heads-up that I created https://mattermost.atlassian.net/browse/MM-32353 for this sprint.


NTR dolichol phosphate mannose

Request  for
dolichol phosphate mannose
dolichol-P-mannose
Dol-P-Man
required for logical definition of dolichol phosphate mannose biosynthetic process
https://github.com/geneontology/go-ontology/issues/28929
reference e
PMID: 18387370
and others

@ValWood The name given is pretty vague and most likely refers to CHEBI:17624 based on evidence found in PMID:28743912. Its major microspecies at pH 7.3 is CHEBI:58211


Update office-365-worldwide-endpoints.md

added *.svc.ms, -files.sharepoint.com, -myfiles.sharepoint.com to line 31

@JoeDavies-MSFT - Can you please assist to check, approve and merge the content of this PR based on issue #420?
Thank you.

@JoeDavies-MSFT - We would like to follow up. Can you please assist to check, approve and merge the content of this PR based on issue #420?
Thank you.


music/sfx provided by feep is a hack and needs a new system

My RubyGem, feep, is currently providing (in debug/test) some music/sfx for a couple triggers, but even when using threads, it's still slow and is way behind the action. It's a hack, and needs improvement, but nothing comes to mind.

I added win32-sound back in as the main sound system for Windows machines, with feep as a fallback. The former is superior in playback, but lacks in compatibility cross-platform. Compromise for now.

Found a new sound system I can use, bloopsaphone, that will work for the Mac as a default. Added in version 0.14.5. Feep is still around for fun, but it is no longer recommended.


Missing CORS headers in some of the endpoints calls

Some of the endpoints are missing the CORS headers and the call is denied on preflight. This is really strange, and I can't understand why other endpoints with absolutely the same configuration work and others don't.
Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The only difference is that in front-end we are passing extra headers using axios.
Example:
const getSomething = (type) => axios.get(`/my/endpoint`, {
  headers: {
    type: type
  }
})

The above code is getting denied because of missing CORS, but the following code is working:
const getSomething = () => axios.get('/my/endpoint')

    "github_com/devopsfaith/krakend-cors": {
      "allow_origins": ["http*"],
      "expose_headers": [
        "Content-Length",
        "Content-Type"
      ],
      "max_age": "12h",
      "allow_methods": [
        "OPTIONS",
        "GET",
        "POST",
        "PUT",
        "DELETE"
      ],
      "allow_headers": [
        "Origin",
        "Authorization",
        "Content-Type",
        "Cache-Control",
        "Pragma",
        "Accept-Language"
      ],
      "allow_credentials": true
    }

@kpacha I am not sure if this is a bug or I am missing any configuration. Please help!

I found the solution. It seems that we need to add the extra headers in the allow_headers list in the krakend-cors configuration.
In my case here I need to add the "type":
      "allow_headers": [
        "Origin",
        "Authorization",
        "Content-Type",
        "Cache-Control",
        "Pragma",
        "Accept-Language",
        "type"
      ],


All KameletBindings reporting "Integration X does not have a readiness condition" error message

When deploying a KameletBinding in an OpenShift cluster, we're getting the following error message:
Integration "integration-name" does not have a readiness condition

Steps to reproduce:

Go to Administrator > Operators > Installed Operators > Camel K Operator > KameletBinding
Click Create KameletBinding then click Save (without edits)
After a few minutes, the integration fails to deploy with Status Phase: Error and the following YAML

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  creationTimestamp: '2023-03-13T13:34:06Z'
  generation: 1
  managedFields:
    - apiVersion: camel.apache.org/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:spec':
          .: {}
          'f:sink':
            .: {}
            'f:ref':
              .: {}
              'f:apiVersion': {}
              'f:kind': {}
              'f:name': {}
          'f:source':
            .: {}
            'f:properties':
              .: {}
              'f:message': {}
            'f:ref':
              .: {}
              'f:apiVersion': {}
              'f:kind': {}
              'f:name': {}
      manager: Mozilla
      operation: Update
      time: '2023-03-13T13:34:06Z'
    - apiVersion: camel.apache.org/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          .: {}
          'f:conditions': {}
          'f:observedGeneration': {}
          'f:phase': {}
      manager: kamel
      operation: Update
      subresource: status
      time: '2023-03-13T13:36:58Z'
  name: example-v2
  namespace: openshift-operators
  resourceVersion: '6623300'
  uid: df236b47-3841-45ea-8bf1-c87d7b51be4e
spec:
  sink:
    ref:
      apiVersion: messaging.knative.dev/v1
      kind: InMemoryChannel
      name: example
  source:
    properties:
      message: Hello world
    ref:
      apiVersion: camel.apache.org/v1alpha1
      kind: Kamelet
      name: example
status:
  conditions:
    - lastTransitionTime: '2023-03-13T13:36:58Z'
      lastUpdateTime: '2023-03-13T13:36:58Z'
      message: Integration "example-v2" does not have a readiness condition
      status: Unknown
      type: Ready
  observedGeneration: 1
  phase: Error

Kubernetes Cluster:
OpenShift 4.12.5
Operator::
Camel K Operator and the Red Hat Integration - Camel K Operator (tried both, and they both fail with the same message.
CLI Version:
Camel K Client 1.12.0

The KameletBinding is not able to run because the referenced Kamelet source(example) does not exist. You need to reference a Kamelet that is available from one of the Kamelet catalogs (e.g. https://camel.apache.org/camel-kamelets/3.20.x/). Also the binding uses a Knative InMemoryChannel example as a sink so you would have to make sure to create this channel before running the binding.
Here is a KameletBinding I just verified on OCP 4.12 with Camel K 1.12.0
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  labels:
    app: camel-k
  name: timer-to-log
spec:
  source:
    ref:
      apiVersion: camel.apache.org/v1alpha1
      name: timer-source
      kind: Kamelet
    properties:
      message: Hello world
  sink:
    ref:
      apiVersion: camel.apache.org/v1alpha1
      name: log-sink
      kind: Kamelet

The binding log output:
2023-03-13 15:09:30,848 INFO [org.apa.cam.k.Runtime] (main) Apache Camel K Runtime 1.17.0
2023-03-13 15:09:30,874 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
2023-03-13 15:09:30,877 INFO [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 3.20.1 is starting
2023-03-13 15:09:31,034 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='camel-k-embedded-flow', language='yaml', type='source', location='file:/etc/camel/sources/camel-k-embedded-flow.yaml', }
2023-03-13 15:09:31,130 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='log-sink', language='yaml', type='source', location='file:/etc/camel/sources/log-sink.yaml', }
2023-03-13 15:09:31,134 INFO [org.apa.cam.k.lis.SourcesConfigurer] (main) Loading routes from: SourceDefinition{name='timer-source', language='yaml', type='source', location='file:/etc/camel/sources/timer-source.yaml', }
2023-03-13 15:09:31,643 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 3.20.1 (camel-1) is starting
2023-03-13 15:09:31,660 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:3)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started binding (kamelet://timer-source/source)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started source (timer://tick)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Started sink (kamelet://source)
2023-03-13 15:09:31,661 INFO [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 3.20.1 (camel-1) started in 221ms (build:0ms init:203ms start:18ms)
2023-03-13 15:09:31,666 INFO [io.quarkus] (main) camel-k-integration 1.12.0 on JVM (powered by Quarkus 2.16.0.Final) started in 4.319s.
2023-03-13 15:09:31,667 INFO [io.quarkus] (main) Profile prod activated.
2023-03-13 15:09:31,667 INFO [io.quarkus] (main) Installed features: [camel-bean, camel-core, camel-k-core, camel-k-runtime, camel-kamelet, camel-kubernetes, camel-log, camel-timer, camel-yaml-dsl, cdi, kubernetes-client, security]
2023-03-13 15:09:32,671 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:33,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:34,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:35,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:36,659 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:37,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:38,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]
2023-03-13 15:09:39,660 INFO [log-sink] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello world]

It's strange because I am getting a completely different behaviour when I try to deploy the example YAML you provided.
Basically, I am getting the same error message shown in my original issue description. And, the following logs are showing up under the operator container:
{"level":"info","ts":1678721314.489918,"logger":"camel-k.controller.kameletbinding","msg":"Invoking action monitor","request-namespace":"openshift-operators","request-name":"timer-to-log","api-version":"camel.apache.org/v1alpha1","kind":"KameletBinding","ns":"openshift-operators","name":"timer-to-log"}
{"level":"info","ts":1678721314.4919193,"logger":"camel-k","msg":"could not find any knative type in namespace openshift-operators, last error was: the server could not find the requested resource"}

{"level":"info","ts":1678721314.489918,"logger":"camel-k.controller.kameletbinding","msg":"Invoking action monitor","request-namespace":"openshift-operators","request-name":"timer-to-log","api-version":"camel.apache.org/v1alpha1","kind":"KameletBinding","ns":"openshift-operators","name":"timer-to-log"}
{"level":"info","ts":1678721314.4919193,"logger":"camel-k","msg":"could not find any knative type in namespace openshift-operators, last error was: the server could not find the requested resource"}

Not a bug, some misleading information: https://github.com/apache/camel-k/issues/2397

Hi @squakez
I also saw #2397 so started to rule it out as a culprit. What's left to troubleshoot?
In case this helps, below is the Event stream from the KameletBinding:
13 Mar 2023, 10:21 Condition "Ready" is "False" for KameletBinding timer-to-log: Integration "timer-to-log" is in "Creating" phase
13 Mar 2023, 10:21 KameletBinding "timer-to-log" in phase "Creating"
13 Mar 2023, 10:24 KameletBinding "timer-to-log" in phase "Error"
13 Mar 2023, 10:24 Condition "Ready" is "Unknown" for KameletBinding timer-to-log: Integration "timer-to-log" does not have a readiness condition

can you see any IntegrationKit resources in the operator namespace?
oc get ik

What does it say? Same for Build resources. You can have a look at these resources to also get some error information.
Maybe it is good idea to remove all IntegrationKit and Build resources that you can see in order to start fresh

Figured out the issue. I'm embarrassed to admit that the OpenShift internal registry was not configured.
I think it would be useful to introduce logic in Camel-K during deployment/installation to check for the image registry and throw an error if it isn't configured. Shall I create a separate Issue for this?


icon width resize

how can resize icon width ?
I want to use facebook icon and I use this line of code
Facebook
but icon doesnt seem like in demo. It's bigger than demo one

It's hard to know without a reproducible code sample. Some other CSS might have been interfering.
The best way to detect what is interfering is to inspect the item using the web inspector. Then look at the CSS properties that set by other stylesheets and try to toggle them until it works.


how to set Each service module individually configured option?

when i used this,i need to set some diff option,and i've no idea ,plz help

@fionagithub I missed your message until just now.  If you switch to the 1.0 branch, you'll be able to customize the vuex modules quite easily.  Check out https://github.com/feathers-plus/feathers-vuex/issues/40 for more info.

Version 1.x has shipped!  npm install feathers-vuex@latest  It's very easy to customize, now.  See the docs in the Readme.md.

great！i saw it in readme.md.i can easy to set  specify custom options per service.thx!


Appending current data sources by scraping symptoms from Wikipedia

Appending current data sources by scraping symptoms from Wikipedia
Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes/features) (Or not needed)
[x] Labels, reviewers and assignees have been added to the pull request
[x] Docs have been added / updated (for bug fixes / features) (Or not needed)

Motivation and Context

Create more useful data by matching symptoms to ICD 10 codes
Does this PR introduce a breaking change?

No
Other information
To run the code do the following:

Update environment with: conda env update --file environment.yml
Run: python src/data/make_dataset.py -a -c 5 -s (The -i stands for the function and the -c stands for the size. Depending on the number after, this is how many sources will be scraped)
I have implemented a caching system which allows the scraper to become faster everytime you run it

maybe edit pull request information on how to run python file


applyConversationReference issue

Versions
What package version of the SDK are you using. V4.6.1
What nodejs version are you using : v11.5
What browser version are you using : na
What os are you using : windows 10
Describe the bug
Describe the bug

let ref = TurnContext.getConversationReference(context.activity)
let newActivity = TurnContext.applyConversationReference({type: 'message'}, ref)
let newRef =  TurnContext.getConversationReference(newActivity)

// expect newRef to be same as ref

The newRef and ref have interchanged bot and user properties.

@ubreddy - I'm assuming your context.activity contains an incoming activity. You can see in the SDK reference that isIncoming is false by default because applyConversationReference is mostly meant to be used on outgoing activities, and this is supposed to switch the from and recipient properties so that the activity can be sent to the user. If you want to apply a conversation reference to an incoming activity then you should set isIncoming to true.
Does this resolve your issue?

yes. Thank you.
Uday
On Saturday, 30 November, 2019, 02:17:34 am IST, Kyle Delaney<EMAIL_ADDRESS>wrote:

@ubreddy - I'm assuming your context.activity contains an incoming activity. You can see in the SDK reference that isIncoming is false by default because applyConversationReference is mostly meant to be used on outgoing activities, and this is supposed to switch the from and recipient properties so that the activity can be sent to the user. If you want to apply a conversation reference to an incoming activity then you should set isIncoming to true.
Does this resolve your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


[WebView] Backport to Accompanist 0.23

Please backport WebView to Accompanist 0.23. WebView is currently only available in 0.24, which is based on Compose 1.2.0-alpha.
PS: What happened to GitHub Discussions? It seems they have been disabled for this project 😢

WebView was not put in to the Compose 1.1 branch as it's under active development and the API is changing which means it doesn't meet the criteria for a stable release unfortunately. As a workaround you could look how it is implemented and wrap WebView with AndroidView yourself to meet your requirements. Sorry I don't have a better option for you.
As for GitHub discussions, we decided to turn them off as they were going neglected and to focus our efforts on the issues for when people need support.


ResponsiveMasonry

i can't understand, what is the problem?

Same here

This happens because using defineProperty with only a getter makes it immutable. I think this is an issue with the build system.
I tried to build the code using v21.7.1 and it produces a different output. I am not sure which version the code authors used.

I had to build it myself using latest node version. hope this gets fixed soon

My team had this issue after regenerating the package-lock.json file during updating unrelated dependecy
Our workaround is to downgrade to v2.2.0 and make it strict in package.json file
terminal:
npm i<EMAIL_ADDRESS>
package.json:
-"react-responsive-masonry": "^2.2.0",
+"react-responsive-masonry": "2.2.0",

same issue, v2.2.1 works without issues

After running this command on node version v20.18.0 solved the issue in my case
npm i<EMAIL_ADDRESS>my next version is

"next": "13.4.7",


Make OrderedMap.Has distinguish KeyNotFoundError

Closes #213
Description
Modify OrderedMap.Has to distinguish KeyNotFoundError from other errors.

[x] Targeted PR against main branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Maybe we can tag a new build after this has been merged?

Maybe we can tag a new build after this has been merged?

Great timing!  I opened issue #214 today that includes tagging a new build as a task.  I'll open separate PR to add doc.go and tag a new build after it is merged.


[Vue warn]: The computed property "fields" is already defined as a prop. in vue cli 3

[Vue warn]: The computed property "fields" is already defined as a prop in vue cli 3

How I can fix this problem.

Hi there. I am having the same issue.
Vuejs 2.5.17
vuetable 1.7.5
vee-validate 2.1.0-beta.9

in my case, vue-bootstrap and VeeValidate3 is making conflictions


[Bug][projects] Can't select different page sizes on projects page

Search before asking

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

What happened
We have a lot of projects and we can't change the page size. It's always stuck at 20, so it's hard to find projects that we are looking for.

What do you expect to happen
We would like to be able to change the page size on projects page.
How to reproduce
Trying to change the page size will always set it to 20.
Anything else
No response
Version
v1.0.0-beta3
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

this issue is present in the Blueprints section as well.
DevLake version: 1.0.1-beta3

+1. I think it should be resolved ASAP. @Startrekzky


Remove reference capabilities from the design time target.

Remove reference capabilities from the design time target. They will now be coming from the targets in the SDK (see https://github.com/dotnet/sdk/pull/406)
Related to #400, #399

Closing this as the solution we're going with is an opt out model instead of opt in.


add rename file

as the title said it would be nice to add a way to add a middleware to rename uploaded files before saving to local storage , i think this feature is a must when working with files !

Could you guide me with a callback function to the configuration of FormDataInterceptorConfig to get the filename?

Hi @AmineHouari98 @chhonhourseng
If you are using DTO, you can achieve this with @Transform decorator (class-transformer package):
@Transform(({ value }: { value: MemoryStoredFile }) => {
    value.originalName = 'new name';
    return value;
  })
file: MemoryStoredFile;

Hi, maybe add a callback function to the configuration of FormDataInterceptorConfig to get the filename before saving it to local storage?

can you give us the example? please.


Sitemap Broken

Sitemaps have been broken since the subdomain switch. We'll need to fix it to get sites properly indexed.

closed by https://github.com/manawiki/mana/commit/605cbe9616e3eb9fac81f6fe863ebb7466d416e8


Enabling os x

Can you also make a new version 1.1.1 so these changes are accessible as a released version?

I can merge this, but I don't know who owns the Pod anymore :( Can somebody at @mindsnacks help with that? :)


Restore putting unread at top in All Feeds

In previous iterations of this plug-in (using Firefox on Linux), the All Feeds section would show unread articles only. The advantage of this was that an unread article was put towards the top of the screen, and was easily accessible even if quite old. Now that All Feeds shows both unread and read articles, unread articles aren't as easily accessible. Would it be possible to set All Feeds to automatically list unread items before read items once again, or enable an option for this feature?

clicking on the unread counter or with alt key depressed shows unread only for any source on the list, there was no special treatment for All feeds


Mouse wheel scroll pans map (Chrome)

URL
No response
How to reproduce the issue?
Is it me or did something change in iD that makes it that scrolling does not zoom anymore?
I think that I alway scrolled right after clicking edit to zoom in. Now I pan the map. I think that changed. Maybe something with how browsers send trackpad and mouse wheel scrolls?
There is https://github.com/facebook/Rapid/issues/867 which might be related.
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
No response
Which browsers are you seeing this problem on?
Chrome

facebook/Rapid#680 hasn’t been incorporated into iD as far as I know. (Otherwise it might be possible to close #8649, which is about the reverse problem in Firefox.)

Hi there - can you provide more information on your browser/platform (browser version, operating system and version)? I can't reproduce this behavior on my end - I expect nothing has changed, but there could still be a bug affecting specific browsers.

Also, can you confirm that this issue occurs both after a reboot of your computer and in a clean copy of your browser (e.g. addons disabled, new profile) or at least in a private window without addons?

Closing this as stale - feel free to reopen this as a new issue if you are still experiencing the problem. Thanks!

@nickrsan please reopen. The issue is well described. The linked Rapid issue gives more details. I will update the title.

Well, it looks like I can close, but not reopen issues. Maybe @1ec5 can reopen since he's in this thread.
In the meantime, could you answer the questions I provided above so that we can better try to reproduce the behavior? Is the issue still occurring, what browser version are you on, etc. Without that, this issue will be challenging to respond to as I can't reproduce it on my end (but did see the behavior in RapiD at the time that other issue was logged)


Switch to using ROCDL directly, as opposed to via HC. Add missing bits.

This makes HIP use ROCDL directly, which is highly preferable. Function definitions are provided inline in the relevant header. Certain functions which were previously unimplemented are added.

@AlexVlx @b-sumner This PR is causing performance drop in rocrand (SWDEV-157382 or SWDEV-157378). Can we do something for performance improvement?

@gargrahul this is due to the more conservative implementation of the float intrinsics; at least the normal_distribution test is likely to be affected by __sincosf no longer relying on AMDGCN native sin + cos. That being said, unless there are even cursory targeted performance tests in place to measure this and present it outside of "this dense codebase seems to suffer between two HIP commits; I had to go and grok rocRAND to deduce what may be happening), which can drive optimisation here, it would be extremely unwise to do anything. So this is a chance for CQE to shine and present a nice thorough analysis.


[sbt 1.0] Scala 2.12.2

Fixes #3111

Merging this since @dwijnand and I talked about this change before, and he's tested it on Travis CI as well.


Fix for increasing number of network connections

Description:
Updated pymyq version to 1.2.0. The aiohttp client session is now setup within the pymyq library instead with tested socket options to prevent continuous increase in sockets on certain platforms.
Related issue (if applicable): fixes #9193
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

[X] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Can you elaborate what changes in your session fixed the leak socket issue? enable_cleanup_closed=True?
If so, maybe we should change aiohttp_client to default turn on this option.

So this is what I have found out so far. This is experience and testing with aiohttp for 2 components that were having issues on certain deployments of HassIO.
Harmony component (through library aioharmony) is using websockets from aiohttp. People were having regular disconnects and then re-connections failing. Sometimes also with errors like "Network unreachable" etc...
In that one a solution was to set the connection to be socket.AF_INET and verify_ssl=False. This is based on some info I found for aiohttp with others running into similar issues:
https://github.com/aio-libs/aiohttp/issues/2522
https://github.com/aio-libs/aiohttp/issues/3171
The whole conversation related to aioharmony is here: https://community.home-assistant.io/t/harmony-hub-problems-after-update/98460
Next issue with myq. Somewhat similar but they would just see the number of connections keep on increasing even although it's supposed to keep the connection open and using pooling (all managed through aiohttp).
Hence I started off with same settings. Issue was still there only now happening every 30 seconds or so instead of every 10 seconds (every 10 seconds a request is sent).
I then set limit_per_host to 5 and added enable_cleanup_closed=True.
After that change is was reported back to overall it only had 1 connection open, with a maximum of 2 connections.
That is still below the limit_per_host of 5.
What I currently do now know however is what if it is only enable_cleanup_closed=True and family is not set. I know with the issue on websockets I had to set it to resolve that issue.

I believe  enable_cleanup_closed=True is the key, can you try to only set it?
It seems happened in particular website, which didn't handle the SSL connection close gracefully.

You can create a new websession with same connector pool with the helper. I would prefere that one because it need less resource and home assistant is care that this session will be closed: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/helpers/aiohttp_client.py#L49

You can create a new websession with same connector pool with the helper. I would prefere that one because it need less resource and home assistant is care that this session will be closed: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/helpers/aiohttp_client.py#L49

It's not about creating new sessions. It's about aiohttp "leaking" connections. Same connection pool is being used but and idea is same connection is used all the time. Yet on certain platforms they were seeing a constant increase in number of connections.
Was using the HA aiohttp client before to create the web session.

Just checking

Can you elaborate what changes in your session fixed the leak socket issue? enable_cleanup_closed=True?

If so, maybe we should change aiohttp_client to default turn on this option.
They confirmed this indeed helps.

Not sure what needs to be done further to get this approved. I see a number of new checks sitting there though.

I think it has been confirmed that enable_cleanup_closed=True works, can you change the pull request to change aiohttp_client add this option instead of maintenance your own session.

I think it has been confirmed that enable_cleanup_closed=True works, can you change the pull request to change aiohttp_client add this option instead of maintenance your own session.

Changed it back to use aiohttp helper client from HA and updated aiohttp helper client to include this option.

@pvizeli
Per aiohttp document

enable_cleanup_closed (bool) – some SSL servers do not properly complete SSL shutdown process, in that case asyncio leaks ssl connections. If this parameter is set to True, aiohttp additionally aborts underlining transport after 2 seconds. It is off by default.

However add this option will apply to all clients, would you mind take a look into it?

I think that it's fine.


Allow user to set default LaTeX header

For me personally, I often need to change the color of formulas or add Unicode encoded characters to them. Of course, I can open the LaTeX2AI_header.tex file after each new project and modify its contents, but always remember those macros and commands are not very user-friendly.
So would it be possible to provide an option in the configuration screen to allow the user to edit the default LaTeX2AI_header.tex file contents once and for all.

This is an interesting feature request. However, I am not sure if this is easily doable within LaTeX2AI. Two (not perfect) workarounds:

What you can always do, is put the Illustrator documents that should use the same header in the same directory
Use the \input command in to point to a global file (this still requires to edit the header after creation)

Greetings @isteinbrecher,
This feature is what I saw in other software's latex plugin, I think it is very user friendly, so I share it with you, hope to provide a little inspiration to improve latex2AI.
Of course, not every software uses the same implementation logic, and it doesn't matter if the same operation can't be realized in LaTeX2AI. As you said, LaTeX2AI is capable of realizing the same effect, it just requires a little more effort from the user.
BTW, I have another idea besides the two options you provided. In fact, it is entirely possible to add enough rich latex packages, such as "color", "ctex", and corresponding setup commands, such as "\xeCJKsetup{CJKmath=true}", to the tex file of the source code. Subsequently recompile to get the plugin. In this way, most of their needs can already be met, even if the user does not have the flexibility to customize the contents of the default header file.


wbits parameter ignored for compression level 1 on 2.0.x branch

Hi, I maintain python bindings for zlib-ng (https://github.com/pycompression/python-zlib-ng). I run a lot of compatibility tests with Python's zlib module to ensure smooth interoperability.
It turns out that using zng_deflate with compression level 1 overrides  the wbits setting in deflateInit in some way. This results in files that are always compressed with wbits 13 it seems. When I use wbits=-9 , I should also be able to inflate again with wbits=-9, however this is not possible and will throw an invalid window size error.
This problem does not occur on the develop branch.

That sounds like it was fixed in this commit: https://github.com/zlib-ng/zlib-ng/commit/ce6789c7e093e8e6bb6fc591bbdf0f805999bdb9. But it is already included in latest zlib-ng release.

The problem still occurs on the zlib 2.0.6 branch and the coming zlib-ng 2.0.x branch.

Maybe we should add a test for this, and have it run it once per algorithm.
I have tried to track down where this problem occurs, but my hunches have been wrong so far. @nmoinvaz any ideas?

I think we need more information in order to be able to track it back to a commit. @rhpvorderman can you provide instructions on how to run the tests, in your tests folder? Which test would trigger the error? It seems requirements-docs.txt might be missing pytest. Each time I install python-zlib-ng does it rebuild zlib-ng?

@rhpvorderman can you provide instructions on how to run the tests, in your tests folder?

git clone --recursive https://github.com/pycompression/python-zlib-ng.git
cd python-zlib-ng
virtualenv .venv  # python3-virtualenv needs to be installed or do pip install virtualenv first
source .venv/bin/activate
pip install . pytest
pytest tests/test_compat.py::test_compress

Last statement will yield 108 xfailed (expected failure) those are the tests that are failing.
It is maybe easier to recreate the test in this repo:

Take a reasonably large chunk of data (128Kb should suffice)
compress it with all possible wbits, memlevel and compresslevel options
For each options, check if it can be decompressed with the same options.
Currently for level 1 any thing with a window size below 13 (regardless of header/trailer) fails. All other levels are OK.

Yes! Got it!
https://github.com/zlib-ng/zlib-ng/blob/2.0.x/deflate.c#L302-L305
#if !defined(NO_QUICK_STRATEGY) && !defined(S390_DFLTCC_DEFLATE)
    if (level == 1)
        windowBits = 13;
#endif

This happens in deflateInit2. This should be extremely easy to fix.
I will make a patch immediately.

Done https://github.com/zlib-ng/zlib-ng/pull/1431

FYI in the zlib-ng integration thread for cpython (https://github.com/python/cpython/issues/91349) they reckoned this commit fixed the problem https://github.com/zlib-ng/zlib-ng/commit/ce6789c7e093e8e6bb6fc591bbdf0f805999bdb9 .
That commit removes  the WindowBits cap entirely and does some rebalancing. As a result the bug is also gone.
So you could also integrate that commit into 2.0.x.

It looks like that was the right commit. However, I was wrong, I assumed it was merged into 2.0.x and stable branches based on the date of the commit and date of the release - it never got into any 2.0.x release.

Fixed


Install on Ubuntu 22.04 (jammy) fails, unmet dependencies

[x] I confirm that this is an issue rather than a question.

Bug report
This is more of a tracking ticket.
When following the official installation guide and isntalling hyperion via apt repo, there are some unmet dependencies in Ubuntu 22.04 (jammy).
https://docs.hyperion-project.org/en/user/Installation.html
Steps to reproduce

install Ubuntu 22.04 (jammy)
follow the installation instructions: https://docs.hyperion-project.org/en/user/Installation.html

What is expected?
Hyperion should use available dependencies/find the correct dependiences and install correctly.
What is actually happening?
Hyperion cannot be isntalled, because some dependencies are missing in the offical ubuntu repos:
The following packages have unmet dependencies:
 hyperion : Depends: libpython3.9 but it is not installable
            Depends: libmbedtls12 but it is not installable

These depencies can be manually solved by the following:
libpython3.9: https://launchpad.net/~deadsnakes
libmbedtls12: build from source: https://launchpad.net/ubuntu/jammy/+source/mbedtls
System

Standard Ubuntu x64 trying to install  Hyperion 2.0.13

Alternatively to manually solving the dependencies, hyperion could switch to libmbedtls14 and libpython3.10.
But I am not sure how much work is needed for this.

@fightforlife Thanks for reporting. I updated the builds accordingly.
The next nightly build should have the corrected packages for Jammy (22.04) and Kinetic (22.10) for the amd64 platform.
Details on installing nightly builds you find here:
https://apt.hyperion-project.org/#nightly
Hoping everything works again....
Maybe you can test and report back,

Yes, Installation went without any problems. Thank you!


Fix/small sync and udev devlink priority

2 small fixes here:

Support reading devlink priority 'L:' from udevadm info output..
Sync() on the filehandle in addPartitionSet and delPartitions.

Code coverage is silly :)


TextFormField validator return String doesn't expands to more than one line when running in a real IOS, works the right way in a simulator!

Steps to reproduce

run the app on a real iPhone [tested only in IOS 17.5 on both]

Expected results
the expected result should be as it happens in a simulator running IOS 17.5,
the return text of validation should be expanded let's say for two lines if the text is big enough!
Actual results
what happens is that the text is shrunk to one line only and at the end of the line I find ...
three dots!
Code sample
Code sample
                Form(
                  child: Builder(
                    builder: (context) {
                      return TextFormField(
                        controller: passwordCont,
                        obscureText: _viewPassword,
                        // textAlign: TextAlign.left,
                        validator: (passCurrentValue){
                          RegExp regex=RegExp(r'^(?=.*?[A-Z])(?=.*?[a-z])(?=.*?[0-9])(?=.*?[!#$%^&*.]).{8,}$');
                          var passNonNullValue=passCurrentValue??"";
                          if(passNonNullValue.isEmpty){
                            return (Languages.of(newContext)!.text616);
                          }
                          else if(passNonNullValue.length<7){
                            return (Languages.of(newContext)!.text617);
                          }
                          else if(passNonNullValue.contains("123")||passNonNullValue.contains("456")||passNonNullValue.contains("789")){
                            return (Languages.of(newContext)!.text618);
                          }
                          else if(!regex.hasMatch(passNonNullValue)){
                            return (Languages.of(newContext)!.text619);
                          }
                          return null;
                        },
                        onChanged: (value) {
                          password = value.trim();
                          Form.of(context).validate();
                        },
                        decoration: kTextStyleDecoration.copyWith(
                            suffixIcon: GestureDetector(
                              onTap: () {
                                setState(() {
                                  _viewPassword = !_viewPassword;
                                });
                              },
                              child: Icon(
                                _viewPassword
                                    ? Icons.visibility
                                    : Icons.visibility_off,
                                color: Colors.grey,
                              ),
                            ),
                            hintText: Languages.of(context)!.text366),
                        inputFormatters: [passwordAllowed],
                      );
                    }
                  ),
                ),

Screenshots or Video

Screenshots / Video demonstration
this is a real iPhone ios 17.5

this is a Simulator ios 17.5

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.0, on macOS 14.6.1 23G93 darwin-arm64, locale en-EG)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.92.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Hi @EgHubs, can you provide a complete sample without third party packages that reproduces this issue? With just a textfield and long text, the error lines wraps on the simulator. See the screenshot below

sample used
import 'package:flutter/material.dart';

void main() => runApp(const MaterialBannerExampleApp());

class MaterialBannerExampleApp extends StatelessWidget {
  const MaterialBannerExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MaterialBannerExample(),
    );
  }
}

class MaterialBannerExample extends StatelessWidget {
  const MaterialBannerExample({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('The MaterialBanner is below'),
      ),
      body: Center(
        child: TextFormField(
          autovalidateMode: AutovalidateMode.always,
          validator: (passCurrentValue) {
            return 'something somthein taskdhjasdnaskdajsdhaskda skdajsdhaskdajsd asdkajdansd askdajs aksdjadaskdajsdhaskdajsdaskdaj';
          },
          onChanged: (value) {},
        ),
      ),
    );
  }
}

Hi @EgHubs, I think this is because you have a line break in your message. If you remove the line break, it will fit one line and if you add it, it will split the text on both lines. I get the same behavior with the simulator on my iPhone XS

Hi @EgHubs, what iPhone are you testing on? On my iPhone XS, the display is the same as the simulator. See the screenshot below

Hi @EgHubs, with the code sample in https://github.com/flutter/flutter/issues/153665#issuecomment-2304555591 do you still get the issue with your iPhone 11 or is it only in your actual project?


Error at Determination

As I select "Update Status" I receive this red error immediately. Happened twice, but not sure how to recreate it.

@frjo Are you working on the fix?

I will look at this.

No longer an issue on the live and test sites.


Facebook oauth token format change causes error (suspected)

It appears as though FB logins updated the oauth token format
https://www.facebook.com/v2.3/oauth/access_token returned when you exchange a code for an access_token now return valid JSON instead of being URL encoded. The new format of this response is {"access_token": {TOKEN}, "token_type":{TYPE}, "expires_in":{TIME}}. We made this update to be compliant with section 5.1 of RFC 6749.
https://developers.facebook.com/docs/apps/changelog#v2_3
This has broken the (very old) version of securesocial we're running 2.1.4
I'm new to scala having recently taken over this project and am at a pretty big loss as to what I can do to get logins working again.
Any suggestions?
The error I'm getting locally is (I think this is the issue)...
[error] application - Unable to log user in. An exception was thrown
securesocial.core.AuthenticationException: null
	at securesocial.core.OAuth2Provider.doAuth(OAuth2Provider.scala:117) ~[securesocial_2.10-2.1.4.jar:2.1.4]
	at securesocial.core.IdentityProvider.authenticate(IdentityProvider.scala:75) ~[securesocial_2.10-2.1.4.jar:2.1.4]
	at securesocial.controllers.ProviderController$$anonfun$handleAuth$1.apply(ProviderController.scala:92) [securesocial_2.10-2.1.4.jar:2.1.4]
	at securesocial.controllers.ProviderController$$anonfun$handleAuth$1.apply(ProviderController.scala:88) [securesocial_2.10-2.1.4.jar:2.1.4]
	at play.api.mvc.ActionBuilder$$anonfun$apply$10.apply(Action.scala:221) [play_2.10-2.2.4.jar:2.2.4]
	at play.api.mvc.ActionBuilder$$anonfun$apply$10.apply(Action.scala:220) [play_2.10-2.2.4.jar:2.2.4]

The user class has
authMethod: securesocial.core.AuthenticationMethod = securesocial.core.AuthenticationMethod(""),
  identityId: securesocial.core.IdentityId = securesocial.core.IdentityId("", ""),
  oAuth1Info: Option[securesocial.core.OAuth1Info] = None,
  oAuth2Info: Option[securesocial.core.OAuth2Info] = None,
  passwordInfo: Option[securesocial.core.PasswordInfo] = None,
  notifications: List[Notification] = Nil
  ) extends securesocial.core.Identity {
  def isAdmin: Boolean = is_admin == 1 || id == 500
  def getAvatarUrl(sz: Int = 80): String = s"https://www.gravatar.com/avatar/${Codecs.md5(email.getOrElse("").getBytes)}.png?d=${shared.controllers.RemoteAssets.getUrl("images/avatar-default.png")}&s="+sz
}

@pedalpete I just fixed this in master and released a new milestone with the fix.  Since you are using 2.1.4 I suggest you create a new Facebook provider that does not override buildInfo and register that instead of the build in one.
The code in OAuth2Provider parses the json as expected but we had a custom logic for Facebook because they were not following the spec.

Thanks for that jaliss, I appreciate the speedy response. I've got this working now.

you're welcome @pedalpete


Documentation

I'm currently migrating a bot from python-telegram-bot to kotlin, I'll try to collaborate with this while I'm on that


[Flux v2] Pipeline links are NOT FOUND

Hey,
I have noticed that the links that lead to the definitions of the different pipelines (ci, cd and pr) are not valid links.
The links are found in the "Import the CI/CD pipelines" section.
I've noticed that the pipeline links for the Flux v1 tutorial are valid. I believe that they are the same links? The same pipelines for both Flux versions?
Thank you in advance.

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

ID: 72579f7e-b040-d514-cf8f-422a66ceb0b0
Version Independent ID: 22d40926-4a12-7387-61b5-04805b1d5c83
Content: Tutorial: Implement CI/CD with GitOps (Flux v2) - Azure Arc
Content Source: articles/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
Service: azure-arc
Sub-service: azure-arc-kubernetes
GitHub Login: @eedorenko
Microsoft Alias: iefedore

Fixed in #200189

Fixed in #200189](https://github.com/MicrosoftDocs/azure-docs-pr/pull/200189)

The link provided is longer available.


[Dialog] Open state bug

Problem description
I created a Dialog component and control its open state with this.state.openState which is connected to this.props.open. Another component which contains this Dialog component, also include a button which sets the open prop to true for Dialog when clicked.
After the first button click the Dialog open prop was set to true, but it's openState state still false. It only changes to true after the second click on the button.
Any idea why this is happening? It should change the state on the first click because of the shouldComponentUpdate.
Subsequent clicks on the button works properly, only the first click on the button after the render has this bug.
Steps to reproduce
import React from 'react';
import Dialog from 'material-ui/Dialog';
import FlatButton from 'material-ui/FlatButton';

class DialogExample extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      openState: props.open
    };
  }
  // ... handleClose, handleSubmit
  shouldComponentUpdate(nextProps) {
    this.setState({ openState: nextProps.open });
    return true;
  }
  render() {
    const {openState} = this.state;
    const actions = [
      <FlatButton
        className="button"
        label="No"
        onTouchTap={this.handleClose}
        />,
      <FlatButton
        className="button"
        label="Yes"
        primary={true}
        onTouchTap={this.handleSubmit}
        />,
    ];
    return (
      <Dialog
        title="example"
        actions={actions}
        modal={true}
        open={openState}
        >
        Text?
      </Dialog>
    );
  }
}

export default DialogExample;

Versions

Material-UI: 0.15.1
React: 15.1.0
Browser: Chrome, FF, IE

@valentinvichnal does your application require the calling button to be in another component and not with the dialog? It would not happen if it is a part of the same component the dialog is.

@nehalbhanushali yes, because I have a list of item each has a related icon button for the Dialog.
When dialogs were in the same components it worked, but there is too much Dialog related code so I moved them to their own module.
Now I use only the props to check if the Dialog is open, pass a callback to the Dialog which can call it and it will change the open prop to false. It works but not a nice solution.

@valentinvichnal Looks like we can close this issue then


QGLWidget not found when compiling project

When I tried to compile the project, it couldn't finish.
Looks like it needs QGLWidget and can't find it nor does it exist in the CMakeLists.txt file.
It gave me the following error:

In file included from /path/GSLAM/GSLAM/gslam/GUI/QGLViewer/vec.h:32:0,
from /path/GSLAM/GSLAM/gslam/GUI/QGLViewer/quaternion.h:26,
from /path/GSLAM/GSLAM/gslam/GUI/QGLViewer/keyFrameInterpolator.h:29,
from /path/GSLAM/GSLAM/gslam/GUI/QGLViewer/camera.h:26,
from /path/GSLAM/GSLAM/gslam/GUI/QGLViewer/qglviewer.h:26,
from /path/GSLAM/GSLAM/gslam/GUI/MainWindow.h:20,
from /path/GSLAM/GSLAM/gslam/GUI/MainWindow.cpp:14:
/path/GSLAM/GSLAM/gslam/GUI/QGLViewer/config.h:78:11: fatal error: QGLWidget: No such file or directory
# include <QGLWidget>
compilation terminated.
CMakeFiles/gslam.dir/build.make:86: recipe for target 'CMakeFiles/gslam.dir/GSLAM/gslam/GUI/MainWindow.cpp.o' failed
make[2]: *** [CMakeFiles/gslam.dir/GSLAM/gslam/GUI/MainWindow.cpp.o] Error 1
CMakeFiles/Makefile2:141: recipe for target 'CMakeFiles/gslam.dir/all' failed
make[1]: *** [CMakeFiles/gslam.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

Please update your gslam version and try again.


Build regression in GN from recent commit

Example failing builds:
https://chromium-review.googlesource.com/c/angle/angle/+/1978600
https://chromium-review.googlesource.com/c/chromium/src/+/1978604
Error message:

ERROR at //third_party/spirv-tools/src/BUILD.gn:177:7: Undefined identifier
      debug_insts_file,
      ^---------------
See //third_party/spirv-tools/src/BUILD.gn:260:1: whence it was called.
spvtools_language_header("debuginfo") {
^--------------------------------------
See //third_party/glslang/src/BUILD.gn:196:5: which caused the file to be included.
    "${spirv_tools_dir}:spvtools_opt",
    ^--------------------------------

Regression range:
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/e70b009b0f1e..64f36ea5296e
Suspecting 64f36ea5296ec023f65f75d7 "Support OpenCL.DebugInfo.100 extended instruction set (#3080)" by<EMAIL_ADDRESS>since that's the only one that changed the GN.
@dneto0 can you investigate?

This is blocking rolling DEPS in Dawn.


Feature request: possibility to create exclusive consumer

We would like to use consumer in exclusive mode and although com.rabbitmq.client.Channel.basicConsume() allows it, would it be possible to add relevant support to Consumer actor (by adding relevant argument or even ConsumerParameters, where to bundle (autoAck, noLocal, exclusive) arguments?
Or is there any reason why it wouldn't be good idea?
Thanks!

Can you please have a look at branch wip-issue61 and tell me if that is what you are looking for ?
Just out of curiosity, what is your use case ? (I've seen people use exclusive queues but not exclusive consumers yet)
Thanks!

Thank you, wip-issue61 seems to have the improvement I was looking for.
We are building data processing pipeline, where each step is coordinated by a cluster singleton actor (each of which distributes workload to workers across Akka cluster). Step coordinators are communicating with each other over RabbitMQ (persistent) queues. The motivation to use exclusive consumers is to have (additional) guarantee, that every step has only one coordinating actor running at a time (as theoretically there could be 2 cluster singleton running in case of cluster partitioning).

Ok. If wip-issue61 works for you then I'll merge with master and close the issue. I'll probably release a new version to maven central very soon.
Thanks


Lakeshore Model 372: include heater submodules into snapshot, don't snapshot blocking_t parameter, add output parameter to heaters

include heater submodules into snapshot
Also add parameter to get the heater output level from the instrument.
don't snapshot blocking_t parameter

This has been tested on a Model 372. I have not looked into if similar problems with snapshot of output channels are present in drivers for other models.
Ping @astafan8 as you most recently committed to this driver.
( original description was edited )

@ThorvaldLarsen is there a particular reason for the heaters to be in a list as opposed to JUST be submodules of the instrument added via add_submodule(...) call?

@ThorvaldLarsen I pushed some edits. Could you perform the test again?

Yes, will test it again next week.
One thing: The get_parser in set_blocking_t really needs to be removed otherwise the snapshot thing gives warnings (the parameter does not have a get_cmd). I can of course test as is but that was my experience when testing last time for initial version of this PR.

ok, will remove the get_parser and investigate the thing separately

@astafan8 I just tested the current version of this driver and all the changes worked:
Tested reading out heater range. setting temperature, and reading snapshot.
Two things to comment on:
First: The heater will return 0.005 even when the heater is off. Seems 0.005 is the lowest value in can return even if it should be zero. Values in normal operation mode works fine. To me it is fine as is but might be good to add a comment about it?
Second: I found a different bug in wait_until_set_point_reached. When the measured temperature is outside the calibrated range the lakeshore will return 0 kelvin as the value. This means abs(t_reading - t_setpoint) / t_reading > tolerance will throw an error due to zero division. There should be a check that t_reading is not equal to zero. Dont know if this should be fixed in a separate PR.

@ThorvaldLarsen Thanks a lot! Then I merge this PR.

The heater will return 0.005 even when the heater is off.

For now, I'll add this as a note in the description of the parameter in this PR. If needed, we can implement something smarter in the driver.

I found a different bug in wait_until_set_point_reached ...... Dont know if this should be fixed in a separate PR.

Thanks! But it is to be fixed, for sure, in a separate PR :) This PR already contains 3 subtly related changes.


[SPO] Trial statuses outline and rules

Latest update: Once "Cancelled", cannot be back to "Active" or "On Hold".

@Mastaleru These are clarifications regarding trial statuses added/modified by SPONSOR.

@paiusCatalin avoid setting redundant statuses. e.g if the status is Active it should not be changed to Active again.

@Mastaleru I share your vision. Let me clarify with the business for such a modification (and to align on the reason if not). I will keep you updated and in the loop.

@Mastaleru It was confirmed by Achal that once the trial is cancelled, there is no need to place it on hold or make it active again. Thanks for raising this point! So, once the trial is cancelled, the TP can get into another trial. Regarding the "On Hold", the details are coming.

@Mastaleru Baldwin did a fantastic job by clarifying the details. I am just citing below.
"For our pilot and for simplicity, I would recommend the following:
“On Hold”= stop recruitment of new TPs.  Collection of data from all TPs enrolled in the trial to continue [Comment from Kristina: collection of data = continue visits & procedures]. TPs remain active in the trial. Status can be reverted to “Active” or moved to “Cancelled”
“Cancelled”= Stop recruitment of new TPs and stop collection of data from all TPs enrolled in the trial [Comment from Kristina: stop collection of data = stop visits & procedures]. TPs to be discontinued. Status cannot be reverted to “Active”"
In reality, the situation will be more complex with the "Cancelled", but Baldwin suggested to simplify it (above is a simplified version) at this stage of the development.

completed in https://github.com/PharmaLedger-IMI/eco-sponsor-ssapp/commit/0792479d6012c5770c6ae03a74c20a0e16ed8437


Added the Publisher apply method to the SFlux object

@zackman0010 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@zackman0010 Thank you for signing the Contributor License Agreement!


Integration spec functionality completed with partners

In this PR: I have created the mentioned functionality in the specs.
Multiple files are modified and created.

HI @BilalLiaquat7, @binyamolango and @anyars-encarta, Please fix the Rubocop  linter  error that was added by the last commit, please when you submit for review please avoid making commits 👍🏿

STATUS: INVALID CODE REVIEW 🛑
Hi @BilalLiaquat7 ,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
Hello @BilalLiaquat7, kindly note that this PR cannot be used for this block, you have a new partner, kindly submit changes on the PR for this block
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
Invalid Code Review Request does not count into the code reviews limit.

Hi @zeff96
I'm repeating the module and I have previously finished this thing can we add a commit for my new partner and then can we able to submit this again??
Please do let me know.
Thanks


Bug: picrew.me

URL
https://picrew.me/ja
FILTERS

Adguard
base, mobile, tracking, URL tracking, social, annoyances, Japanese

other
Legitimate URL Shortener, AdGuard Japanese filter Plus

Browser
Google Chrome 125.0.6396.3
Operating System
Microsoft Windows 11
Ad-Blocker
AdGuard Browser Extension 4.3.44
Userscript Manager
Violentmonkey 2.18.0
USERSCRIPT
AdGuard Popup Blocker (Beta)
Always on focus
Google Search English Filter
microShield
Select text inside a link like Opera
Comment
Enabled

Disabled

I don't understand why a breakage occurs when microShield is enabled and Twitter SDK and Ad-Shield script are filtered using a HTML filtering rule.

Ads with this website may have returned.

@Am4hisa Please tell me what microShield version is.

I can't reproduce it now...
It may have been temporary or on my side issue ;(
script ver 4.4.7


multi-cluster e2e tests in GHA

What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

I branched off of #50 for this PR. I am going to recreate it to avoid having to work through merge conflicts again.


requestAnimationFrame error in safari v5.1.7 (and possibly chrome and safari on ios)

I am currently getting this error with the commit 4f40ddb44db197276f37f22fe11b7db6a9c7e1d4
I only have a windows machine and that is the latest version of safari I can get on windows. It also isn't loading my hls stream on ios in safari or chrome, so this might be the same issue, but I have no good way of testing this at the moment so it might not be.

Looking in the source it looks like a shim should be being provided for browsers that don't support requestAnimationFrame so I'm guessing this is a bug?

I'm looking into it.

Proposed fix: https://github.com/clappr/clappr/pull/458

I now get this error which I'm looking in to

Tested on Safari for iOS and it's fixed. Thanks @tjenkinson!


Should we include a sh script in RCA source code to execute it in batch?

What would a run script look like?  How do we pass the directory to be analyzed?  Just would be helpful for new users that want to run locally.
java -jar "\Run-Control-Apps\RCApps\target\rcapps-1.1.0_RC4-jar-with-dependencies.jar"

Add a comment in the script suggesting:
"Required inputs from analysis include: (1) WBXMLI directory contain workbench xml to be analyzed, OR a VDPXMLI directory containing VDP xml to be analyzed and (2) RCAPARM with execution parameters"