Fix incorrect check for the “ok” status

Please provide a description of this PR:
Fix incorrect check for the “ok” status

Hi @JinVei. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@JinVei: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
df6b178619c008c5f80d3337282a614afe529a90
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Kwxm/plutus papers/add doi info

Add DOI info for the papers, as suggested by @jmchapman.

I'm confused: I thought the discussion we had was bout what to do with the drafts in the plutus-papers repository? James already added DOI information in this repository.

But that was in a different place, I think it's useful to have more information.

I'm confused: I thought the discussion we had was bout what to do with the drafts in the plutus-papers repository? James already added DOI information in this repository.

Sorry, I missed that: it's buried in the middle of the big README file.  I don't think it'll do any harm having the DOIs here as well though.  I already added the same info in the plutus-papers repository, together with pointers to the directories here.

Okay, seems fine.


Reach time limit

Browser Version
Edge
Exension Version
1.5.2
Actual behaviour
reach limit after first use
I've tried multiple times reinstall the extension however it doesn't work
here's the textbook I'm trying to gain access
https://quizlet.com/explanations/textbook-solutions/advanced-engineering-mathematics-10th-edition-9780470458365/chapter-1-exercises-7-9d2f77a9-e8f7-447d-a035-3a7abade458d
Reproduction steps
No response
Expected behaviour
No response

sorry for the disturbance, IT FIXED after I delete cookies


Checking Base network results in Error: Invalid API Key

This is the error when attempting check for permissions on base
Checking Base network results in Error: Invalid API Key

It looks like this was a transient error with Basescan that seems to be resolved now.


Provide functions to record and manage TS streams

Port functions from EPGStation or newly implement similar functions.
mirakc doesn't provide any UI, just provides functions as Web API.  UI has to be implemented separately.  However, a function to provide static files for UI may be implemented if many users request it.

The timeshift recording feature has been implemented in 69f699c9901bf848e4d8bada6c77d3fcd7f9d938.


Github Actions And Dockerfiles Failing To Build

Centsos 7 based elements are failing due to mirrorlist.centos.org no longer being valid..
Loaded plugins: fastestmirror, ovl
14Determining fastest mirrors
15Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was
1614: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
17
18
19 One of the configured repositories failed (Unknown),
20 and yum doesn't have enough cached data to continue. At this point the only
21 safe thing yum can do is fail. There are a few ways to work "fix" this:
22
23 1. Contact the upstream for the repository and get them to fix the problem.
24
25 2. Reconfigure the baseurl/etc. for the repository, to point to a working
26 upstream. This is most often useful if you are using a newer
27 distribution release than is supported by the repository (and the
28 packages for the previous distribution release still work).
29
30 3. Run the command with the repository temporarily disabled
31 yum --disablerepo=<repoid> ...

FYI @andrew-m-leonard

Part of https://github.com/adoptium/temurin-build/issues/3795


Potential Score Increase Percentage

[Enter feedback here]

The Defender for cloud Portal page, shows the Potential Score Increase in Percentage. It is not clear how this percentage is calculated. Please explain how Potential score increase is calculated.
Screenshots used in this page https://learn.microsoft.com/en-us/azure/defender-for-cloud/secure-score-security-controls#calculations---understanding-your-score  does not match the Portal currently.
If you have questions, please ping alias moravind

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

ID: b9d7741b-cd5a-29b0-c360-e054f7686c87
Version Independent ID: f03434f5-504a-d87f-b9ce-3ed695db9227
Content: Secure score
Content Source: articles/defender-for-cloud/secure-score-security-controls.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: elkrieger

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

@ElazarK
Could you Please review this and update as appropriate.

@moravindMSFT
I'm going to assign this to the document author so they can take a look at it accordingly

@moravindMSFT Thank you for bringing this our attention. I will have the screenshot replaced within the next few publishing cycles.
As for how the potential score increase is calculated, it is referred to on the page here:

Where the Potential score increase - The remaining points available to you within the control. If you remediate all the recommendations in this control, your score will increase by 9%.
Potential score increase = [Score per resource] * [Number of unhealthy resources]

I'm trying to understand how this % value is calculated. In this example 9% increase on Total points? Or with Max Score?
Display of percentage is incorrect at this stage. I checked this in many customer environments and none of them are matching to the actual value.
In both the cases, it is not matching with the actual value. Please ping via teams if you need further clarification.
Regards,
Mohan Ravindran | CISSP
CSA - Security - Engineering
+1<PHONE_NUMBER>
From: Elazar Krieger @.>
Sent: Thursday, April 20, 2023 6:25 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Mohan Ravindran @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Potential Score Increase Percentage (Issue #107722)
@moravindMSFThttps://github.com/moravindMSFT Thank you for bringing this our attention. I will have the screenshot replaced within the next few publishing cycles.
As for how the potential score increase is calculated, it is referred to on the page here:
[image]https://user-images.githubusercontent.com/58463413/233338635-731af566-b6ed-4cf5-992c-7aec3e6983e0.png
Where the Potential score increase - The remaining points available to you within the control. If you remediate all the recommendations in this control, your score will increase by 9%.
Potential score increase = [Score per resource] * [Number of unhealthy resources]

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/107722#issuecomment-1516088207, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZKOVRYA5A7BGTRNZWYKWSDXCEFJDANCNFSM6AAAAAAWULZVUM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@moravindMSFT i will reach out on team.
I will be closing this Github issue.

#please-close


Implement caching and dynamic data fetching.

Implemented ability to search across the schemas:

added caching to the /tables/<db_id>/<schema>/ endpoint
added caching to the function that fetches all the table names for the database
implemented dynamic fetching for the table / view names
added @cached_view and @cached_cls_func decorators

Implements https://github.com/airbnb/caravel/issues/1415

Testing

tested locally on presto and mysql DBs
plan to test on the caravel box using proxy

Reviewers

@mistercrunch
@ascott
@vera-liu

there is a lot of data fetching and setting state happening in SqlEditorLeftBar. we should move that to the sql lab actions file.

@ascott  - updated, thanks !

As discussed, this PR adds a lot of complexity (caching, decorators, async autocomplete, ...) and can lead to a degradation of user experience in some cases:
case 1: a user has a Postgres DB with hundreds of schemas and thousand of tables for which loading the cache takes 15 seconds, and no cron job to constantly warm up the cache has been setup, or is down for some reason. Every 2 minutes, hitting the table selection dropdown will take 15 seconds, even if they had selected a schema
case 2: that same user run a "create table as" statement and wants to work off of this summary, wants to add the new table to the workspace, hits the dropdown, tables were cached before, table is missing
I'd lean towards keeping the current working pre-schema flow untouched, and setting up caching only where needed (cross schema lookup) and maybe parameterize it (switch it on on a per-database basis).

Another thought that may invalidate some assumptions: does simplecache work across gunicorn workers? I think not.

@mistercrunch  - updated implementation. Please take a look. Async Select is enabled only if the schema is not set.

lgtm

thanks for the review!
On Tue, Feb 7, 2017 at 10:03 AM, Alanna Scott<EMAIL_ADDRESS>wrote:

lgtm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/superset/pull/1466#issuecomment-278086621, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFdmwkOD2Qr-v4zmrKe-Acjs1SuKj3Rrks5raLHkgaJpZM4Ki-zO
.

--
Best regards,
Bogdan Kyryliuk.


Function incorrectly marked as not differentiable

Description
The following code does not compile giving the following error diagnostic:
Differentiated functions in '@inlinable' functions must be marked '@differentiable' or have a public '@derivative'; this is not possible with a closure, make a top-level function instead```

This is incorrect however as the function itself is not a closure and is differentiable.

### Reproduction

```swift
import _Differentiation

public struct Solution2<Thing: Differentiable & FloatingPoint>: Differentiable where Thing.TangentVector == Thing {
    @inlinable
    public static func optimization() -> Thing {
        var initial = Thing.zero

        let (_, delta) = valueWithGradient(at: initial, of: simulationWithLoss)

        initial.move(by: delta)

        return initial
    }

    @inlinable
    @differentiable(reverse)
    static func simulationWithLoss(input: Thing) -> Thing {
        return input // implementation
    }
}

Expected behavior
Compile without error
Environment
Apple Swift version 6.0-dev (LLVM 097782ee554d9fe, Swift 60bf038ce965551)
Target: arm64-apple-macosx14.0
Additional information
No response

tagging @asl


PNG Mapping support

I found that F3D does not seem to support PNG Mapping during use?
Incorrect display colors for png mapping

Hi @bisechen
Could you share the .fbx file ? This may be an issue with assimp, VTK of F3D so we need to test it.

support PNG Mapping during use?

Could you elaborate on that ?

Looks like the colors are mapped. It can happen if the texture is 16-bits (which is possible with PNG files).
It's probably an easy fix by calling vtkTexture::SetColorModeToDirectScalars in the assimp importer.
Please @bisechen share the file.

Looks like the colors are mapped. It can happen if the texture is 16-bits (which is possible with PNG files). It's probably an easy fix by calling vtkTexture::SetColorModeToDirectScalars in the assimp importer. Please @bisechen share the file.

You are right, I tried it again, it is indeed the problem caused by 16 bit.

support PNG Mapping during use?

Could you elaborate on that ?

Is the problem caused by PNG 16bit

Still, it should work with 16-bits PNG files. Please share the file so we can fix the issue.

Because the test file has been deleted, I recreated a 16bit mapping using the original settings and steps, but the FBX file cannot be uploaded here, but this FBX is only Blender's default CUBE export

Any change to look at this @Meakk ?

Any change to look at this @Meakk ?

I downloaded version 2.0 for testing,
and the display of both 16-bit and 32-bit color depth is incorrect,
but the display of 8-bit color depth is normal.
Previously, I have been using Blender for drawing,
but in order to rule out its problems,
this time I used Krita to create files with three different color depths.
The display results of F3D in 16-bit and 32-bit are still incorrect.
I have attached my test files for reference.
Krita version 5.1.5
Blender version 3.5
https://drive.google.com/file/d/1FYAzb1pP1henVIrdvJK7JXyXPxR92PkX/view?usp=share_link

Hi @bisechen
Here's the current result for the 16-bit fbx file:

Here's with my fix:

Is it what you are expecting?

Hi @bisechen Here's the current result for the 16-bit fbx file:

Here's with my fix:

Is it what you are expecting?

Yes, this is the result I want. Thanks for your contribution.


fix: set content-carousel hero images to stretch with object-fit

Set the height and object-fit css properties/styles so that hero images scale and fill their container proportionally.

I tested these changes locally -- looks good!  :+1:

going to split this into separate branches


[Bug] Remove .idea/dictionaries

We should stop tracking the .idea/dictionaries directory, as these are personal configuration files unsuitable for the repo.

sir can i do my first contribution here ?....but i need your support

@PuneetDabral yes you can submit a PR fixing this issue. For issues labelled 'good first issue' you don't need to ask. Our handbook might be a helpful read for you as a new contributor. You can also join us on Slack (channel #openverse) or comment here if you need help with anything.

ok sir i should try it

sir i guess i need to move that directory to git ignore ...i am right?

Yes, and delete the already checked-in directory as well.


feat(#627): Print PHI Expressions

In this PR, I translate all generated XMIR files to PHI expressions in all integration tests. These changes prove that we can generate a valid XMIR that can be easily used further.
These changes leave significant technical debt related to the jeo-maven-plugin architecture. We expose many fields using getters and similar methods, this indicates poor design of the plugin. I have left several puzzles to address this issue later.
Closes: #627.

PR-Codex overview
This PR updates Maven commands and refactors code for consistency.
Detailed summary

Updated Maven commands in integration test README files
Added a new integration test for "Bytecode To Eo"
Refactored method properties in XmlMethodTest.java
Improved XML parsing in several classes
Updated Maven plugin versions in POM files

The following files were skipped due to too many changes: src/it/takes/pom.xml, src/main/java/org/eolang/jeo/representation/directives/DirectivesField.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesTypedData.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesMethodProperties.java, src/main/java/org/eolang/jeo/representation/xmir/XmlOperand.java, src/it/spring/pom.xml, src/main/java/org/eolang/jeo/representation/xmir/XmlAnnotationProperty.java, src/test/java/org/eolang/jeo/representation/xmir/XmlClassPropertiesTest.java, src/it/custom-transformations/pom.xml, src/it/bytecode-to-eo/pom.xml, src/main/java/org/eolang/jeo/representation/xmir/XmlMaxs.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesTryCatch.java, src/test/java/org/eolang/jeo/representation/xmir/XmlFrameTest.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesData.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesAnnotationsTest.java, src/main/java/org/eolang/jeo/representation/xmir/XmlAttribute.java, src/it/spring-fat/pom.xml, src/main/java/org/eolang/jeo/representation/directives/DirectivesAnnotations.java, src/test/java/org/eolang/jeo/representation/xmir/XmlFieldTest.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesMethod.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesClassPropertiesTest.java, src/main/java/org/eolang/jeo/representation/xmir/XmlTryCatchEntry.java, src/main/java/org/eolang/jeo/representation/xmir/XmlFrame.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesFrameTest.java, src/test/java/org/eolang/jeo/representation/MethodNameTest.java, src/test/java/org/eolang/jeo/representation/directives/HasMethod.java, src/main/java/org/eolang/jeo/representation/bytecode/BytecodeAnnotation.java, src/test/java/org/eolang/jeo/SameXml.java, src/main/java/org/eolang/jeo/representation/xmir/XmlClassProperties.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesClassTest.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesMethodTest.java, src/main/java/org/eolang/jeo/representation/MethodName.java, src/main/java/org/eolang/jeo/representation/directives/DirectivesAnnotationProperty.java, src/main/java/org/eolang/jeo/representation/xmir/XmlMethod.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesTryCatchTest.java, src/test/java/org/eolang/jeo/representation/directives/DirectivesAnnotationPropertyTest.java, src/test/java/org/eolang/jeo/representation/xmir/XmlTryCatchEntryTest.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

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

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 11min)

@volodya-lombrozo Thanks for the contribution! You've earned +20 points for this. Please, keep them coming. Your running balance is +20.


Random string using openssl_pseudo_random_bytes()

With fallback to /dev/urandom
Note: see https://github.com/ircmaxell/RandomLib/tree/master/lib/RandomLib

Solved in https://github.com/AngryBytes/hash/releases/tag/2.0.0


[v2] f7-pages missing?

framework7 2.0.0-beta.9
framework7-vue 2.0.0beta.1.5
v2 will remove f7-pages or new component coming?

Yes, pages is not required anymore and been removed


sam: fix ENABLE bit blocking ADC channel setup

This should close:
https://github.com/zephyrproject-rtos/zephyr/issues/59806
Thanks to @attie-argentum for helping fix this issue.

Compliance checks should pass.

@maksimdrachov please fix the compliance check

@maksimdrachov - please could you fix the compliance check? It seems you committed with a different email to the Signed-off-by line.


Debug dots appear when i click on a line of code

Issue Type: Bug
On my Windows 10 system, I debugged my code. After I was done with the debugging, whenever I clicked on the code, line corresponding to it was marked red, just like how we mark a line of code for debug. This process continues for every part of code. And during all this, when I try to copy a part of code, the red dot is pasted in its place and it doesnt copy correctly. Interesting thing is that this happened with visual studio 2019 too on the same machine.
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.88GB (1.14GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

cpptools
ms-
0.29.0

This is a sample of how its working. The corresponding red dots were created when I tried to click on that line number.

Looks like you are clicking too far to the left of the line numbers. Try clicking on the actual numbers.

Thing is, I am not working with debug mode on. I am just trying to code right now and during that when I switch line numbers by clicking on a part of code or just scrolling through it, this red dot appears on the line corresponsing to wherever my cursor goes and starts flickering. I click on it again to remove it and it gets removed but the same cycle happens when I move my cursor through mouse clicks or keyboard arrow keys.

Breakpoints can be set even when you are not actively debugging. The dark red dots in your screenshot come from when you clicked in that column. If you only want to select the line (not set a breakpoint on it), click on the number.


Update to latest PHP, Python, and Composer

Unsure of how to update the README.md that references all this.

Unsure of how to update the README.md that references all this.

No worries, I'll take of that. Thanks for the PR!


TS Error for CallbackType of EventHandlerType

Bug is related to

[x] embla-carousel (core package)
[ ] embla-carousel-react
[ ] embla-carousel-vue
[ ] embla-carousel-svelte
[ ] embla-carousel-autoplay
[ ] embla-carousel-auto-height
[ ] embla-carousel-class-names
[ ] embla-carousel-docs (documentation)
[ ] embla-carousel-docs (generator)

Embla Carousel version

v7.1.0

Describe the bug
I'm trying to use such code:
const onSelect = (emblaApi: EmblaCarouselType) => {
    // some actions with the emblaApi...
};
emblaApi.on('reInit', onSelect);

I'm getting TS error:
TS2345: Argument of type '(api: EmblaCarouselType) => void' is not assignable to parameter of type 'CallbackType'.   Types of parameters 'api' and 'evt' are incompatible.     Type 'string' is not assignable to type 'EmblaCarouselType'.       Type 'string' is not assignable to type 'EmblaCarouselType'.
on this:
emblaApi.on('reInit', onSelect);
In the file embla-carousel/components/EventHandler.d.ts the callback parameter is specified as: export type EmblaEventType = 'init' | 'pointerDown' | 'pointerUp' | 'scroll' | 'select' | 'settle' | 'destroy' | 'reInit' | 'resize';
but in fact the emblaApi object (EmblaCarouselType) gets into the function

Hi @evgencode,
Thank you for your bug report. This is not a bug. The documentation is always for the latest version which at the time of writing is v8.0.0-rc12. v7 is a major version behind the latest release and that means breaking changes.
Best,
David


Update build-microsoft-365-solutions.md

corrects misleading information, that 'Power Apps is included in your Microsoft 365 E5 developer subscription license', which is not true. With the E5 subscription, a user only gets "Power Apps for  Office 365", which only includes standard connectors.
adds information on which (free) license to choose to create and test Power Apps with the Power Apps developer Plan, that also allows for premium connectors (only for test and dev purposes)

Docs Build status updates of commit 68d2a24:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/build-microsoft-365-solutions.md
:warning:Warning
View
Details

docs/build-microsoft-365-solutions.md

Line 75, Column 284: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/connectors/connector-reference/connector-reference-premium-connectors' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 75, Column 155: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/connectors/connector-reference/connector-reference-standard-connectors' will be broken in isolated environments. Replace with a relative link.
Line 75, Column 284: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/connectors/connector-reference/connector-reference-premium-connectors' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8ddee92:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/build-microsoft-365-solutions.md
:bulb:Suggestion
View
Details

docs/build-microsoft-365-solutions.md

Line 75, Column 155: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/connectors/connector-reference/connector-reference-standard-connectors' will be broken in isolated environments. Replace with a relative link.
Line 75, Column 284: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/connectors/connector-reference/connector-reference-premium-connectors' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


The result of omitted jedi.executable.command is unexpected for README

If jedi.executable.command is omitted, coc-jedi always download jedi-language-server in venv in *unix system.
Here is the source code about this issue.
https://github.com/pappasam/coc-jedi/blob/6e178d83ed1ea2f756ae293d4aa67f1324749811/src/jlsExecutable.ts#L58-L70
I have no ability to create a PR because I have no idea about TS and I haven't developed any plugins about coc.

Updated the docs to reflect what's actually happening, resolved in 188a0f40acfd204e4eadac562d4d7f9a29dd18f6

Updated the docs to reflect what's actually happening, resolved in 188a0f40acfd204e4eadac562d4d7f9a29dd18f6


Access violation reading location

hello its me again =))
there is some things that I tested wanted to tell you as a tester
I tried your dll with the right offsets and right injector even other injectors
I didn't build anything by myself but three issues I faced with
aim bot turned on crashes the game
attached visual studio to process and got these errors :
An invalid exception handler routine has been detected (parameters: 0x00000004).
Exception thrown at 0x6482C283 in csgo.exe: 0xC0000005: Access violation reading location 0x00000000.
searched somethings in the net about these found out a warrning in aimbot.cpp at line 45 I think maybe you wanted to check but im not pro tho
in the game after using cheat some time the esp just disapears or the dll uninjected some how and i have to inject again
and it crashed without aimbot 3 times while playing too

That hexadecimal value 0xbluhbluhbluh is useless regarding spotting issue.
Idk I've only used this cheat with -insecure launch optioned CSGO, and used only in bot practice mode, therefore some factors could be something unexpected in other mode. I haven't even tested much. Can you tell me about the mode u played?

I used it like that not wanna get VAC for tests.
Your source doesn't have big issues and its really nice compared to many of cheats but it can not be used to inject with every injector or every injection type
Idk what injection type does CSGHOST injector use but I used your cheat too much in every type of matches and all cheats on and it worked with zero problem with that injector if you wondered about fixing it or work on it my test results was this :)
for those errors people on the net said something like "That looks like you forgot a NULLPTR check somewhere." in the aimbot.cpp line 45 but I checked that you did that but idk what is wrong I'm noob at programming just saying my thoughts and wondering what you gonna do to fix it ^^

I don't think that error is nullptr check as well cuz, yeah as you said I did it properly. I think it's more like I somehow accessing out of range of the playreList array at line 45. However it also checked not to happen before line 45, so idk, maybe my assumption is also wrong.

I'm noob at programming

Reading someone else's code is always difficult haha.
I didn't mentioned it but CS:GO doesn't allow LoadLibrary, a injection way, by default. That's why you only could inject by ManualMapping. If you put '-insecure' flag, I think you would be able to inject with LoadLibrary method.(Or maybe not. I'm not so confidential)


BclStorageFolder.GetItemsAsync Not Async

I was looking at the BclStorageFolder code.
I notice that the async methods, particularly GetItemsAsync that can return hundreds or thousands of elements, is not async at all.
https://github.com/AvaloniaUI/Avalonia/blob/cdc7bf396c3ecdedeec630967d7deb64525c62cf/src/Avalonia.Base/Platform/Storage/FileIO/BclStorageFolder.cs#L69
This probably could be implemented better.
I'm also noting that BclStorageFile.CanOpenWrite always returns true; but there doesn't seem to be reliable way of knowing it other than opening the file and catching the error.
https://github.com/AvaloniaUI/Avalonia/blob/cdc7bf396c3ecdedeec630967d7deb64525c62cf/src/Avalonia.Base/Platform/Storage/FileIO/BclStorageFile.cs#L24
Using Avalonia11-preview5

I notice that the async methods, particularly GetItemsAsync that can return hundreds or thousands of elements, is not async at all.

There is no async API in the BCL to get items. So it can't be really implemented better.
Having async interface API not necessary means it always will start an async IO operation. Heavily depends on the platform backend.

I'm also noting that BclStorageFile.CanOpenWrite always returns true; but there doesn't seem to be reliable way of knowing it other than opening the file and catching the error.

Here I agree, that API isn't quite clear. CanOpenWrite currently indicates if platform supports open write.
Should it check permissions? Which bcl API it should use internally?

If you call EnumerateFiles, you can start processing each item as they are returned. Currently, the ToArray forces all items to be loaded in memory first before returning, making it basically useless for very large folders.
if you really want async, you can do Task.Run until the first result comes back. That would make a difference with an external hard drive that needs a few seconds to boot up on first access.
As for CanOpenWrite... I was looking at that yesterday. There is no better approach to it than trying to open the file and catching any error... which wouldn't make much sense when used like this.
if (file.CanOpenWrite)
    var write = await file.OpenWriteAsync();

To make GetItemsAsync useful, it should return IEnumerable instead of IReadOnlyList.
Use EnumerateFileSystemInfos instead of querying files and directories separately.
Then while being at it, why not offer SearchPattern and SearchOption.
Something similar to this should work.
public IEnumerable<IPathInfo> EnumeratePathInfos(string searchPattern, SearchOption searchOption) => _info.EnumerateFileSystemInfos(searchPattern, searchOption)
        .Select<FileSystemInfo, IPathInfo>(x => x is System.IO.FileInfo f ? new FileInfo(f) : new DirectoryInfo((System.IO.DirectoryInfo)x));

It's still not an async method but allows processing the data as it comes.
If we wrap EnumerateFileSystemInfos inside Task.Run, then it should be async until the first item and then allow looping through the IEnumerable.

As for CanOpenWrite... I was looking at that yesterday. There is no better approach to it than trying to open the file and catching any error... which wouldn't make much sense when used like this.

Makes sense. I think we should remove CanOpenRead and CanOpenWrite. Especially, as I just noticed, it ended up returning "true" always on all platforms.

With this API we are going from the common denominator between platforms.

People would write their own IO classes for more advanced scenarios.

That's what I would say as well. If needed, people can branch their code on desktop platforms and using .NET API directly (or even platform API directly) for the efficiency, and possibly converting paths to IStorageFile with TryGetFileFromPath (if needed). And on non-supported platforms like browsers, they can fallback to slower GetItemsAsync.

if you really want async, you can do Task.Run until the first result comes back. That would make a difference with an external hard drive that needs a few seconds to boot up on first access.

Normally, I would say that async APIs that just call Task.Run internally have a quite bad reputation. As it ends up being useless, since developers could use Task.Run by themselves if they need. Otherwise, it's just a waste to thread-pool.
But in current situation, when that's depends on interface implementation, some backends might even require UI thread, which makes Task.Run(() => folder.GetItemsAsync()) quite dangerous operation.

public Task<IEnumerable> GetItemsAsync()

I think this idea makes sense.
Alternatively, it can be IAsyncEnumerable<IDialogStorageItem> which we can even fully support on the browser backend (!). And just wrap over EnumerateFiles on desktop.

Added these two API changes to the list of this issue https://github.com/AvaloniaUI/Avalonia/issues/9876

I would say that async APIs that just call Task.Run internally have a quite bad reputation

Why? I think it's worse to have an async method that "magically" doesn't behave async. In what context does it need to be run in the UI thread and running from different thread is dangerous?

In what context does it need to be run in the UI thread and running from different thread is dangerous?

It's not about BCL implementation. On the browser you simply cannot start a new thread, for example. Some of the Android APIs require main thread as well, but I don't think it's applicable here.
I mentioned Task.Run as there is basically two ways to ensure it is async even if some implementations are not.
Either run Task.Run inside of sync backend (like BCL) in the framework code, or always run all GetItemsAsync call inside of Task.Run (regardless of the backend) in the user code.
And in this context, second option is more dangerous that the first one.

Here we're talking about the BCL implementation. I think it's fine to have async handled differently for each platform, and shouldn't be up to the calling user to figure that out per platform.

So far I am thinking about implementing IAsyncEnumerable<IStorageItem> API instead of current one.
On BCL it won't be async, but at least it won't also load all items in the memory as you said.
And on Browser it can be both async and lazy.
We can technically do pinvokes to get truly async and lazy implementation, which is supported in Windows AFAIK, but not in the .NET API. But I don't have much knowledge about low level IO on windows.


Zeeve_Parachain_deployment_zoombienet_testing_automation

Project Abstract
Zeeve will provide a command line based tool to setup of new Substrate parachain network with in-depth and flexible configurations in few clicks on the cloud of choice to distribute nodes upon (AWS, GCP, DigitalOcean and Linode) - supporting K8 and native VMs whichever fits the parachains better.
We understand the on-paper maximum for a Level 3 grant is for $100,000, but the scope of this project requires 4 FTE-months and we were told earlier in the process that we can make a case to go beyond that limit.
Grant level

[ ]   Level 1: Up to $10,000, 2 approvals
[ ]   Level 2: Up to $30,000, 3 approvals
[X]   Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[X] The application template has been copied and aptly renamed (Zeeve_Parachain_deployment_zoombienet_testing_automation.md).
[X]   I have read the application guidelines.
[X]   A BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (aUSD/USDT) address for the payment of the milestones is provided in the application.
[X]   The software delivered for this grant will be released under an open-source license specified in the application.
[x]   The initial PR contains only one commit (squash and force-push if needed).
[X]   The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[X]   I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @ghanzeeve:matrix.org

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

I’m closing this for now due to inactivity. Let me know if I should reopen it.

Hi David,No problem, will update the wire frames and details within this week and then we can reopen it. We have started preparing the UX for the same.RegardsGhanSent from my iPhoneOn 09-Jan-2023, at 12:57 PM, David Hawig @.***> wrote:
Closed #1399.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

Great. Just ping me once you are ready.

Hi @Noc2, We are ready with the Details. Please reopen it.

Sounds good. I opened the PR again.

Thanks for the update. This is a reminder that @arjunzeeve still needs to sign the terms and conditions (see CLA assistant). Also, the links to the images currently don’t work.

Hi @Noc2,  I tried to sign the CLA, it shows successful but I think it is not updating on the repository.
I am sharing the image for the reference. Just let me know what should I do next.
Thanks.

Thanks @arjun-zeeve did you try clicking the "recheck" button? What is the result?

Thanks @arjun-zeeve did you try clicking the "recheck" button? What is the result?

I am unable see the “recheck” button. But after all the things it is still one pending check.

thanks @gnv-zeeve I'm looking into the issue internally and will get back to you.

Hi @keeganquigley please let us know if there is anything is required to be done from our side.

Sorry for the delay here. Not sure why it doesn't work, but I can confirm that @arjun-zeeve signed the terms. I just double-checked the backend, see below:

So we will just ignore the above message and continue with the evaluation.

Sorry for the delay here. Not sure why it doesn't work, but I can confirm that @arjun-zeeve signed the terms. I just double-checked the backend, see below:
So we will just ignore the above message and continue with the evaluation.

Thanks @Noc2. We are looking forward.

Thanks for the application @gnv-zeeve this looks really good and a useful tool. One minor thing, you can go ahead and remove the article 0e. deliverable from the first milestone if you only plan to deliver one, as it is only mandatory for the last milestone.

Thanks for the application @gnv-zeeve this looks really good and a useful tool. One minor thing, you can go ahead and remove the article 0e. deliverable from the first milestone if you only plan to deliver one, as it is only mandatory for the last milestone.

HI @keeganquigley thanks for mentioning that it was duplicate, have removed from M1 and keep in M2.


Is there way to cache the models?

I am not sure if it's already possible, but I noticed it will reload the model from url every time.

@lodisy you can do own download the model & save to document of device. Hence, you can load it from local


Support new React Apollo API

Related #2112
I think we should wait for stable release.
@apollo/* libraries can be used with the version;
 - @graphql-codegen/typescript-react-apollo => 1.4.1-alpha-3b1e744b.8+3b1e744b

@apollo/* libraries have been bumped to v.3 🎊

Did this drop support for react-apollo-hooks entirely?

You are right, it is a breaking change and we are sorry about that.
With a bit more context, the maintainer of react-apollo-hooks said that his package would be deprecated in favor of the stable release of @apollo/react-hooks, so we’ve moved to the new package after the stable release of it.
The name and the signature of generated hooks should be almost same in both packages, so the only thing changed is the package name.
But if you want to go with the old package, you can use older version for react-apollo plugin of codegen.
I understand it is still a breaking change but we believe it is a relatively small and manageable one


ChartExtents rework

ChartExtents should be refactored, currently not allowing any Y/X values to be reset.

Will be released with next major release. Date TBD

Fixed with 1.0.0 release


Multi-address support (variable HD path)

The HD path used is hard-coded to 44'/714'/0'/0/0. This change would allow it to be supplied as an arg and changed as needed to get multiple addresses from the same seed.

@notatestuser I guess we close this one now?


implement quota/capacity on nodes

Each node will have a quota of "available" containers. Whenever the cluster runs out of containers, it should fail to create new containers.

@fsouza i think this project was done?

look at kubernetes, kubernetes implement with cgroup using cpuset

@derit not sure if this is completely done, it's certainly in maintenance mode, but I no longer work on it.
This issue is 7 years old though, so I'm not sure what you mean. Are you asking to close it?

yes sure


Build Error on Windows Machine: Failed to run custom build command for openssl-sys v0.9.61

@rajatha-ravish could you paste the full console error here?

error: failed to run custom build command for openssl-sys v0.9.61
Caused by:
process didn't exit successfully: C:\kafka-delta-ingest\target\debug\build\openssl-sys-6186f04521601717\build-script-main (exit code: 101)
--- stdout
cargo:rustc-cfg=const_fn
cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR
X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR unset
cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
OPENSSL_NO_VENDOR unset
running "perl" "./Configure" "--prefix=C:\kafka-delta-ingest\target\debug\build\openssl-sys-0796760039d4b93b\out\openssl-build\install" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-asm" "VC-WIN64A"
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }', C:\Users\Rajatha Ravish\scoop\persist\rustup.cargo\registry\src\github.com-1ecc6299db9ec823\openssl-src-111.15.0+1.1.1k\src\lib.rs:469:39
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

have you tried following the instructions in https://docs.rs/crate/openssl-sys/0.9.19? Alternatively, you can try rustls flag to avoid linking against openssl, see: https://github.com/delta-io/delta-rs/blob/main/rust/Cargo.toml#L60.

I have tried installing the SSl certificate as instructed in the first link and with other third-party. It did not help.
Trying alternative -
Lines I added :
[features]
rustls = ["rusoto_core/rustls", "rusoto_credential", "rusoto_s3/rustls", "rusoto_sts/rustls", "rusoto_dynamodb/rustls", "maplit"]
error: failed to parse manifest at C:\workspace\kafka-delta-ingest\Cargo.toml
Caused by:
feature rustls includes rusoto_credential, but rusoto_credential is not an optional dependency
A non-optional dependency of the same name is defined; consider adding optional = true to its definition.

You need to add optional = true to all the dependencies mentioned in that list. For example: https://github.com/delta-io/delta-rs/blob/main/rust/Cargo.toml#L36.
You also need to add "deltalake/s3-rustls" to the list.

@rajatha-ravish I recommend going through https://doc.rust-lang.org/cargo/reference/features.html to get a better understanding of how feature flag works in cargo.

I have made the recommended changes, cargo build fails again.
Changes made :
maplit = { version = "1", optional = true }
rusoto_core = { version = "0.46", optional = true }
rusoto_credential = { version = "0.46" , optional = true }
rusoto_s3 = { version = "0.46", optional = true }
deltalake = { version = "0.4.0", git = "https://github.com/delta-io/delta-rs.git", rev = "ddc123c0be9def306edafbb972f773baaefc40ad", features = ["s3"], optional =true }
[features]
s3-rustls = ["rusoto_core/rustls", "rusoto_credential", "rusoto_s3/rustls", "deltalake/s3-rustls", "maplit"]
error: failed to run custom build command for openssl-sys v0.9.61
Caused by:
process didn't exit successfully: C:\demo\kafka-delta-ingest\target\debug\build\openssl-sys-6186f04521601717\build-script-main (exit code: 101)
--- stdout
cargo:rustc-cfg=const_fn
cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR
X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR unset
cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
OPENSSL_NO_VENDOR unset
running "perl" "./Configure" "--prefix=C:\demo\kafka-delta-ingest\target\debug\build\openssl-sys-0796760039d4b93b\out\openssl-build\install" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-asm" "VC-WIN64A"

what command did you run to build the project? did you pass in s3-rustls feature flag to the build command? looks like it's still trying to build openssl. I would remove the s3 feature from deltalake as well to make sure it's only using rustls.


Creating splash screen in the app

Creating splash screen for the ovuli app

Hey @sarthology can I work on this?

Once you are done with #24

I want to work on this.

Can I work on this issue?

Go on @Major2001

Hey can i work on this issue??

Let's see who submit's first.

@Rits1272 im sending it to you


Clean99/feat/add activity apis: add unit testing env and test create feature of activity

fix CI testing.
finished activity service testing.


Add doc for TS_VERIFY_CTX_set_certs()

This addition is based on PR #9472
This will definitely fail the test (doc-nits check) since #9472 has not been merged yet.

Checklist

[x] documentation is added or updated

Not sure if the document of this function (or other TS related ones) should be back ported to 1.1.1. It might be worth doing so from my perspective, since 1.1.1 is a LTS release.

Adding missing documentation for existing functions qualifies for backporting just like fixing a bug.

All fixed in the latest commit

Ping @openssl/committers

Ahh, if this is back ported to 1.1.1, the function name should be changed back to the typo version...

I didn’t follow all details, but could‘nt the corrected function be added in 1.1.1 without deprecation, and the pod file (with correct file name) would contain both functions in the NAME section?

Depends on if the newly added function is considered as a new API or a bugfix

Anyway, if we finally do this to 1.1.1, the man page would look like a little hilarious ;-)

Ah, but an idea just occurred to me. I will post it on #9838 in a few minutes...

I will post it on #9838

I meant #9472 of course.

Please document also the compatibility macro Please TS_VERIFY_CTS_set_certs() and its deprecation, see #9472.

OK, will do that later

TS_VERIFY_CTS_set_certs() has been documented to a NOTES sections, but I think it's also acceptable if documented in HISTORY section.

Which one would you guys consider better?

This will definitely fail the test (doc-nits check) since #9472 has not been merged yet.

Note: You could rebase your pull request on top of #9472 for the moment.

TS_VERIFY_CTS_set_certs() has been documented to a NOTES sections, but I think it's also acceptable if documented in HISTORY section.

I think a note will not be sufficient to satisfy find-doc-nits (after removing the entries from missingcrypo.txt and missingmacro.txt) you need a full blown documentation for the mispelled macro, with a NAME  and SYNOPSIS entry. And finally in the HISTORY comes the usual deprecation note. In order to try it out properly, you could rebase onto #9472, or you just wait until its merged. No hurry.

you need a full blown documentation for the mispelled macro,

In other words: the NAME section contains both the correct and the misspelled name, and the SYNOPSIS contains the prototype twice, misspelled and correct.

#9472 has been merged now, you can rebase on master to pick it up.
Please be so kind to remove

TS_VERIFY_CTX_set_certs from util/missingcrypto.txt and
TS_VERIFY_CTS_set_certs from util/missingmacro.txt

after rebasing.

Sorry for the huge delay, too many meetings these days...
Rebased to #9472 . And the misspelled version TS_VERIFY_CTS_set_certs should also needed to be added into util/other.syms to satisfy make doc-nits

Ping?

It seems #9472 is not merged to 1.1.1, so this should not as well.

It seems #9472 is not merged to 1.1.1, so this should not as well.

Agreed.

Any other suggestions on this?

... and achieves exactly the same.

or simply:  ... and returns the same result.

Haha, interesting

Patched your patch in the latest commit

fixed

Ping @openssl/omc

This PR is stalled... Ping @openssl/omc again.

Ping @openssl/omc this one is very stall.
Should it be rebased to fix  util/missingcrypto.txt and  util/missingmacro.txt  conflict ?

@InfoHunter can you rebase please? Then I'll reconfirm.

@InfoHunter can you rebase please? Then I'll reconfirm.

ping?

Ups. I made a mistake when rebasing your pr. Hang on for a moment...

Ups. I made a mistake when rebasing your pr. Hang on for a moment...

I forgot to solve the conflicts in `util/missing*.txt' before pushing. Now it's done.


Explicitly set PTS server

GitHub actions for contributor PRs uses public build scan instance,
in this case we still want to enable PTS, so we need to configure
the server explicitly.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Question: Using assets (js,css,img) directly form module asset folders

Hi,
is it possible to uses files (js, css, images) directly from module asset folders without publishing to "public" ?

Hello,
That's not possible due how laravel works.
You can, however, make a symlink, or front controller to access them this way.

Hi,
thank you for the quick reply! I was thinking about symlink myself. What do You mean by front controller ?

It means having to go through a route + controller, which servers the proper assets.
This is usually done when files need to be protected by roles/passwords etc.


chore: Add missed method to changelog for 2.1.0 release

Minor correction to changelog

Good catch, thanks.
(next time you can just add [ci skip] to your commit message if there's no code change)


Plugin-Update does not work when Shell is set to Fish

[x] I am on the latest Hyper.app version

[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: macOS 10.12.1

Hyper.app version: <IP_ADDRESS>3

Link of a Gist with the contents of your .hyper.js: My .hyper.js

Relevent information from devtools (CMD+SHIFT+I on Mac OS, CTRL+SHIFT+I elsewhere): None

The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue
When i configure fish as my shell in .hyper.js the plugin update always fails.
The problem is this line which executes npm prune && npm install --production in the configured shell. When i change this to npm prune; and npm install --production it works for me.
Maybe the best would be to not run it directly on the configured shell and use something like for the preferences: bash -c "exec env npm prune && npm install --production"

I can confirm executing a bash then editing the settings works.

#1065


Checking

@kaocher82 I'm not sure what you're trying to fix but please don't use PRs for experiments.


This is the right package to convert html to react?

Say I have this piece of HTML :

<link rel='stylesheet' href='css/addons/mg_line_brushing.css' />

d3.json('data/fake_users2.json', function(data) {
    for (var i = 0; i < data.length; i++) {
        data[i] = MG.convert.date(data[i], 'date');
    }

    MG.data_graphic({
        title: "Brushing Addon by Dan De Havilland",
        description: "Drag the crosshair over the chart to zoom. For further details about this addon, take a look at its GitHub repo.",
        data: data,
        top: 70,
        width: 600,
        height: 240,
        right: 40,
        missing_is_hidden: true,
        target: '#brushing'
    });
});

and I need to merge into my React.js:
import React from 'react';
import DocumentTitle from 'react-document-title';

export default class DashboardPage extends React.Component {
    render() {

        return (
            <DocumentTitle title={'Dashboard'}>

Dashboard for data visualization

            </DocumentTitle>
    );

    }
    }

Do I need to use componentDidMount() or use your package to do the conversion?

Not sure what you want tbh. This library converts (single root) textual HTML markup into a React component which you can typically insert as a child of another React component in your code.


schedule not working due to undefined variable data

In the file parser.js function toRoom() fails to work if a room is not assigned in a schedule "slot".
This happens because in the function async schedule(data) the following snippet assumes HuoneInfo has some data in it.
rooms: this.toRoom(entry.HuoneInfo["0"]["0"])
    toRoom(data){         return {             id: data.kortti,             shortName: data.lyhenne,             name: data.nimi         }     }
Especially now as we are in distance learning most classes dont actually have classrooms assigned to them.

In our parsing guide we encourage to always check if item exists before proceeding to parse, often Visma's JSON is not reliable and items just disappear and re-appear randomly.
But thanks anyways, we'll try to fix that.

Thanks for the issue, I'll get on fixing that as soon as possible. Please note that the current version of OpenWilma in the main branch is going to be deprecated soon, when the 1.0 version catches up to it. 1.0 will provide much better usability and stability.

@Nikedi Your issue has been resolved. If you encounter any further problems regarding the patch, please don't hesitate to leave a message in this issue about it. If you encounter any other problems or have any more off-topic questions about OpenWilma, please make a new issue as usual.

The problem was that data was undefined and thus data.kortti returns an error and thus checking for data.kortti == undefined doesnt return true.
Instead it should check for data == undefined

Ah. That should be fixed now. Thanks for the clarification 👍
Please verify that the issue was fixed so I can close this issue.

Looks like it's working now.

Perfect! I'll close this issue then.


ng build lib --watch output css not changes sometimes

Hi! If I change scss file in library, app refreshes, but style not changes sometimes.
Angular CLI: 9.0.0-rc.3
Node: 12.13.1
OS: win32 x64
Angular: 9.0.0-rc.3
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.900.0-rc.3
@angular-devkit/build-angular      0.900.0-rc.3
@angular-devkit/build-ng-packagr   0.900.0-rc.3
@angular-devkit/build-optimizer    0.900.0-rc.3
@angular-devkit/build-webpack      0.900.0-rc.3
@angular-devkit/core               9.0.0-rc.3
@angular-devkit/schematics         9.0.0-rc.3
@ngtools/webpack                   9.0.0-rc.3
@schematics/angular                9.0.0-rc.3
@schematics/update                 0.900.0-rc.3
ng-packagr                         9.0.0-rc.1
rxjs                               6.5.3
typescript                         3.6.4
webpack                            4.41.2

But if I remove or add some character, this workes with refresh.

Hi @kolkov, can you please clarify if correct css is not reflected in the consuming application or at a library level in the dist folder?

@alan-agius4 If I understand correctly lib compiles properly. And I can't debug my lib. I can't see debug info in chrome dev tools.

I remove !important; from host, but I still see:

and in lib folder I see:

Mostly likely this is a duplicate of https://github.com/angular/angular-cli/issues/13588
Will take a look in the coming days

I had a look at it, and it seems not related to the issue above, also as mentioned above by the reported it doesn't happen consistently.
The problem seems to be related and webpack notifications to the browser. This is being the changes are in the served bundle it's just not reflected in the browser, as when a user does hit CTRL + F5 the style change is visible.

This fixed in rc.4. thanks!

In that case I am going to close the issue.
If the problem persists, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


feat(design-system): Add product image to XDS

EX-7689
Figma

This is a link to Empathy Platform Docs Portal preview in a development environment.
⚠ Only for Empathy members. We’re sorry for the inconvenience!
Check out EPDocs preview

This is a link to Empathy Platform Docs Portal preview in a development environment.
⚠ Only for Empathy members. We’re sorry for the inconvenience!
Check out EPDocs preview


mplus-outline-fonts is broken

Describe the bug
Adding mplus-outline-fonts to system fonts.fonts results in a bad type error:
Steps To Reproduce
Steps to reproduce the behavior:

Add

  fonts.fonts = with pkgs; [
    mplus-outline-fonts
  ];

to configuration.nix
2. build system:
$ sudo nixos-rebuild build
building the system configuration...

error: A definition for option `fonts.fonts.[definition 1-entry 7]' is not of type `path'. Definition values:
       - In `/nix/store/mqkma522w1g3pfk9fr6llyvyg2dalnhv-source/configuration.nix':
           {
             githubRelease = <derivation /nix/store/fhaliawkzgb6r6dmysavhsr4mngx1c10-mplus-outline-fonts-github.drv>;
             osdnRelease = <derivation /nix/store/9lv5h4ss87aqizr9y46f7x2dxvl5q6wp-mplus-outline-fonts-osdn.drv>;
             override = <function, args: {fetchFromGitHub, fetchzip, lib}>;
             overrideDerivation = <function>;
           ...
(use '--show-trace' to show detailed location information)

Expected behavior
A successful build, and addition of mplus-outline-fonts
Additional context
This has been a recent change, and is occurring two systems which use flakes on an OS level (as well as an erase-your-darlings setup).
Notify maintainers

@uakci (sorry, but given the recency of the issue, I can't help but wonder if it's tied to https://github.com/NixOS/nixpkgs/pull/151705 ?),
@henrytill
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.17.1, NixOS, 22.05 (Quokka), 22.05.20220330.710fed5`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

It's not broken, it was split into two variants, mplus-outline-fonts.osdnRelease and mplus-outline-fonts.githubRelease with the big redesign upstream. The osdn variant is t he old one and github is the redesign.

Ah- unfortunate that this results in a misleading type error, rather than a notice that the package has been removed/replaced by one of the two options.
Changing from mplus-outline-fonts to mplus-outline-fonts.githubRelease worked for for me.

It would certainly be nice to have the original name throw a clear error pointing people in the right direction.

It is broken. Anyone using the old package name gets an error that fails the evaluation. The PR at #151705 removed a package and introduced two new ones. In practice it forces every user of the old package to pick a new one amongst the two new. In this situation it would be better to default to the old osdnRelease, as the new one is not backward compatible. (I have just tested). If it ever becomes backward compatible, we could redirect the default there. In the meantime, there is no point in breaking the evaluation for that new package. A deprecation warning would be better.

But then, there is not proper mechanism in nixpkgs for renames and deprecation. That's a shame.

Would you be okay with this fix ? https://github.com/NixOS/nixpkgs/pull/169420


[useResponseCache] Ensure calls to cache are awaited

Description
This change ensures that the calls to the supplied cache implementation are awaited and returned, in the case that the methods are async and return promises. This prevents "floating promises" from being created which will crash the Node process if they are rejected.
I believe this is not a breaking change since all supported Node versions have the behaviour of terminating on unhandled promise rejections, and that the behaviour without this change is not intentional or desired.
Fixes #2240.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Unit tests added for set and invalidate calls to the cache implementation, ensuring that sync errors and promise rejections don't result in process termination.
Test Environment:

OS: macOS 14.4.1
@envelop/response-cache: 6.1.2
NodeJS: v20.11.0

Checklist:

[x] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Thank you for you contribution! Very appreciated!
I agree that we should not have floating promises without any error handling here, but I'm not sure that awaiting it is the right approach about this.
My concern is that if there is a set failure, the entire request handling will fail. You probably don't want to fail responding a valid request just because the cache is down, and you probably don't want to add the latency of the cache network travel.
For this reasons, perhaps just adding a .catch(err => logger.warn('Failed to cache response', err)) instead ?
Do you think it would suite your needs ?
The drawback is that it opens the possibility to have hanging open handles when shuting down the server, which can prevent server for gracefully exit. That being said, it's already the case with the current implementation. We should probably better add an abort signal to allow canceling these promises on shutdown, but not sure it is worth the added complexity for a case that is probably very rare.

After some discussion with a colleague, it appears that we actually already have a way to handle floating promises like this.
There is an undocumented waitUntil function in the yoga context.
It's provided by whatwg-node/server, and it's signature is waitUntil(f: Promise<void> | void): void.

Adding a catch handler works for us too. I also agree that the case for aborting floating promises is not worth the complexity since I'd imagine it's very rare to have a promise that never resolves.
As far as logging goes, I'm not sure where logger would come from in your example as I can't see where it gets passed in from. Maybe we can add an empty .catch and leave the logging to the implementation of Cache, or add a console.error?

Sorry, I was not very clear.
In fact, there is a function in the context called waitUntil that is already doing exactly this :-) And it allows for a better compatibility in ephemeral environment like cloud functions. You can use it instead of manually adding a .catch.
Under the wood, if an implementation is not provided by the environment, it calls .allSettled on every promises passed to it as argument.

Thanks, could you point us to some documentation for this once it's ready and we'll give it a go?


[Bazel] batch 6, of 11 files (m, except for mina_base)

Batch of 11 files starting with m, except for mina_base, which will be submitted separately, and mina_metrics, which has already been submitted.

!ci-build-me


az datafactory pipeline list issue

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az datafactory pipeline list Extension Name: datafactory. Version: 0.2.0.
Errors:
Cannot deserialize as [object] an object of type <class 'dict'>
Traceback (most recent call last):
Temp\pip-unpacked-wheel-lhx4371t\knack\cli.py, ln 215, in invoke
cli\core\commands\__init__.py, ln 654, in execute
cli\core\commands\__init__.py, ln 718, in _run_jobs_serially
cli\core\commands\__init__.py, ln 711, in _run_job
Local\Temp\pip-unpacked-wheel-7avbl0u7\six.py, ln 703, in reraise
cli\core\commands\__init__.py, ln 701, in _run_job
...
Temp\pip-unpacked-wheel-laos76cl\msrest\serialization.py, ln 1586, in deserialize_data
Temp\pip-unpacked-wheel-laos76cl\msrest\serialization.py, ln 1615, in deserialize_iter
msrest.exceptions.DeserializationError: Cannot deserialize as [object] an object of type <class 'dict'>

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az datafactory pipeline list --resource-group {} --factory-name {}

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.13.0 *

Extensions:
datafactory 0.2.0

Additional Context

datafactory

hi @houk-ms could you pls have a look? thanks


Needs a control for transparency/opacity.

I tried to manually change it but regardless what I set the opacity to I was ignored.

Please edit formOpacity in LatentCoupleHelper.json

As I said, it did nothing (which is the manual change I attempted).  0.1 all the way to 1.0 it remained the same.

You need to rewrite LatentCoupleHelper.json instead of LatentCoupleHelper.ps1.
If that does not work, try deleting the following lines.
LatentCoupleHelper.ps1:65
$frm.Opacity = $cfg.formOpacity;

I never found the above, but I was changing this:

in the .ps1 file when I needed to change the json.  Changing the json worked though I do not understand why the need to save that file out each time I close the program?

That code will be the initial value if the JSON configuration file does not exist.
The user can customise it in the JSON file and if there is any trouble, it can be reset by deleting the JSON file.

Yep.  The entire json stuff is new to me, but I guess it is like the old .cfg config files.


is possible to add audio and subtitle track changing in the future?

is possible to add audio and subtitle track changing in the future?

do you have some sample videos having multiple audio tracks?

It might be possible to do the audio track changing if the media item has multiple audio tracks. I will look into it. Subtitles as far as I can see are not likely.
For subtitle support, as far as I can see I dont think the MFPlay API supports subtitles. Later versions for win10/11 using The IMFMediaEngineEx objects might support SAMI. But I am not currently looking at the newer Media Foundation APIs - which wont work on older windows operating system anyhow.
I spent a good amount of time trying to come up with a workaround, but the video player window when rendering doesn't allow any other drawing inside of it, either by subclassing it or directly drawing onto the dc of the video window. From what I could gather, it is using the DWM and DirectX to do the rendering. The only partial success I had was to create a popup window that wasnt a child of the MediaPlayer (displays over the whole desktop), with that I could place this popup over the video window with some test text. But if the user moves/resizes or changes focus the popup would remain on the desktop - so not ideal.
Even then I would have to write a library of functions to parse the srt file, build an index of entries with the times and then handle displaying the text at certain times to sync with the position in the media file, and I couldn't be sure it wouldn't go out of sync or lag somehow.
So I dont think my basic MediaPlayer example application will ever support srt/subtitles unfortunately.

This player is the smallest and fastest player I have ever used.
Is it possible to add plug-in functionality for subtitle support?

Thanks. Unfortunately the MFPlay API doesn't support subtitles, so there is no way to add plug-in functionality for that.

I can now list the audio streams, as shown in the tooltip over the 'i' button. Tested it with a few multi audio language files and it does show, for example a video stream, an english audio and an italian audio stream. I will look into being able to switch over/select a particular audio stream.

I have audio stream switching working for media items that have multiple audio streams. The next release will have this in it.

Closing this as complete for the audio stream switching part.


Fix Kubernetes watch SSL & empty schema

This PR fixes Kubernetes watch SSL, and Kubernetes empty schema.
The new schema rule is:

if port.Name is not empty, use it as protocol
else if port = 443, schema is https
else schema is http

Fixes #332
Fixes #333
Signed-off-by: Emile Vauge<EMAIL_ADDRESS>

LGTM

LGTM :sun_with_face:


oAuth invalid_grant

Have an error while trying to authorize
Error: invalid_grant
    at Request._callback (/Users/noise/Sites/bandlab-desktop-client/app/node_modules/google-auth-library/lib/transporters.js:81:15)
    at Request.self.callback (/Users/noise/Sites/bandlab-desktop-client/app/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/Users/noise/Sites/bandlab-desktop-client/app/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/Users/noise/Sites/bandlab-desktop-client/app/node_modules/request/request.js:1091:12)
    at IncomingMessage.g (events.js:286:16)
    at emitNone (events.js:91:20)

const rawCode = /(code=.+)/.exec(event.newURL) || null;
     const code = rawCode[0] ? rawCode[0].split('=')[1] : null;
     if (code) {
       oauth2Client.getToken(code, function(err, tokens) {
         if (err) {
           throw new Error(err);
         }

         oauth2Client.setCredentials(tokens);
       });
     }

When I'm trying to getToken I have this error.
But what is strange only for first time, if i'll try one more time with same google acc, everything is working.
Thanks!

/cc @jonparrott

Hi @ruid0 - did you ever resolve this issue? I'm facing exactly the same problem. I receive an authorizationCode but the first time I call getToken with said code I get an invalid_grant error.
Repeating the login process with the same user a second time returns a valid token and I can call oauth2.userinfo.v2.me.get() successfully. It is always the first attempt which returns an invalid_grant error.
Any pointers would be much appreciated.

Hi @ruid0 / @ace-n I think I've found the cause of this issue. Whilst debugging the issue I used the "Save as HAR" option in Chrome network inspector and diffed the initial failing getToken request against the second successful request.
What I found is that for some reason the authorizationCode in the first request is URL encoded. The second character in the string is a forward slash and gets URL encoded to %2F. If I make a second request immediately after, the authorizationCode is not URL encoded, hence it works fine.
Since I'm using Javascript I just called the decodeURIComponent function on the authorizationCode. This seems to work as the function has no effect on an already decoded string.
Hope this helps someone!

I believe this was introduced in a recent version of this package, as was #803.

If this is still an issue, please let us know!

I am still getting this issue on specific Google Accounts

Specifically an aliased domain on a personal g-suite account.

@ajmwagar could you open a new bug and share:

what version of the library you're using
the code you're trying to use

Thanks!

Will do, on mobile currently. I will when I get home.

I ran node watch.js got the authorisation code and made a GET call GET /oauthcallback?code={authorizationCode}
But still I am getting Error: invalid_grant.No matter how many times I do it.Same error.

@dman777 this has nothing to do with TypeScript.  As I've mentioned above, please please open a new issue with:

the version of nodejs you are using
the code that reproduces the issue

Thanks!


Clarify test notifications UI

Notes:

I'm not sure if the notification needs to say that it's from Zulip -- we do have the URL just above.

Looks great, marked to merge assuming CI passes.


[libpq] build failure x86-windows x64-windows with features core,icu,nls,openssl,xml,zlib

Host Environment

OS: [Microsoft Windows [Version 10.0.19042.630]]
Compiler:

Visual Studio 2017 Version: 15.9.29  VS Tools Version: 14.16.27023
Visual Studio 2019 Version: 16.8.1  VS Tools Version: 14.28.29333

To Reproduce
Steps to reproduce the behavior:

git clone git@github.com:microsoft/vcpkg.git includes PR #11776 with commit https://github.com/microsoft/vcpkg/commit/3a26eb3dc4d684ca6c1748dccc7a15684b9e8d0a [intl/gettext/fontconfig] update to native build system #11776 - it may be relevant, but not sure
.\bootstrap-vcpkg.bat -verbose -disableMetrics -win64
set VCPKG_DEFAULT_TRIPLET=x64-windows
.\vcpkg.exe  install --x-use-aria2 --recurse --keep-going --editable gettext[core] icu[core] libiconv[core] liblzma[core] libpq[core,icu,nls,openssl,xml,zlib] libxml2[core] openssl[core] zlib[core]

Failure logs

Cut and past the appropriate build messages from the console output.

Computing installation plan...
The following packages will be built and installed:
gettext[core]:x64-windows
icu[core]:x64-windows
libiconv[core]:x64-windows
liblzma[core]:x64-windows
libpq[core,icu,nls,openssl,xml,zlib]:x64-windows
libxml2[core]:x64-windows
openssl[core]:x64-windows
zlib[core]:x64-windows
Starting package 1/8: libiconv:x64-windows
Building package libiconv[core]:x64-windows...
...
Elapsed time for package openssl:x64-windows: 1.308 min
Starting package 8/8: libpq:x64-windows
Building package libpq[core,icu,nls,openssl,xml,zlib]:x64-windows...
-- Downloading postgresql-12.2.tar.bz2...
-- Extracting source D:/Git/vcpkg_x64/downloads/postgresql-12.2.tar.bz2
-- Applying patch patches/windows/install.patch
-- Applying patch patches/windows/win_bison_flex.patch
-- Applying patch patches/windows/openssl_exe_path.patch
-- Applying patch patches/windows/Solution.patch
-- Applying patch patches/windows/MSBuildProject_fix_gendef_perl.patch
-- Applying patch patches/windows/msgfmt.patch
-- Applying patch patches/windows/python_lib.patch
-- Applying patch patches/linux/configure.patch
-- Applying patch patches/windows/minimize_install.patch
-- Using source at D:/Git/vcpkg_x64/buildtrees/libpq/src/tgresql-12-3dcd887135
-- Copying libpq source files to D:/Git/vcpkg_x64/buildtrees/libpq/x64-windows-rel...
-- Copying libpq source files... done
-- Applying patch patches/windows/Solution_RELEASE.patch
-- Applying patch patches/windows/python3_build_RELEASE.patch
-- Patches applied!
-- Downloading msys-gettext-<IP_ADDRESS>-1-x86_64.pkg.tar.xz...
-- Downloading msys-libgettextpo-<IP_ADDRESS>-1-x86_64.pkg.tar.xz...
-- Downloading msys-libasprintf-<IP_ADDRESS>-1-x86_64.pkg.tar.xz...
-- Using msys root at D:/Git/vcpkg_x64/downloads/tools/msys2/91955029573d0bcc
-- Building libpq x64-windows-RELEASE...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:106 (message):
Command failed: D:/Git/vcpkg_x64/downloads/tools/perl/<IP_ADDRESS>/perl/bin/perl.exe build.pl RELEASE libpq
Working Directory: D:/Git/vcpkg_x64/buildtrees/libpq/x64-windows-rel/src/tools/msvc
Error code: 1
See logs for more information:
D:\Git\vcpkg_x64\buildtrees\libpq\build-libpq-x64-windows-RELEASE-out.log
Call Stack (most recent call first):
ports/libpq/portfile.cmake:215 (vcpkg_execute_required_process)
scripts/ports.cmake:136 (include)
Error: Building package libpq:x64-windows failed with: BUILD_FAILED
Elapsed time for package libpq:x64-windows: 35.99 s
Total elapsed time: 12.87 min
...

Please attach any additional failure logs mentioned in the console output.
build-libpq-x64-windows-RELEASE-out.log

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
build-libpq-x64-windows-RELEASE-out.log Contains the follow error:

1>LINK : fatal error LNK1181: cannot open input file 'D:\vcpkg_x64\vs2019\prod\installed\x64-windows\lib\libintl.lib' [D:\vcpkg_x64\vs2019\prod\buildtrees\libpq\x64-windows-rel\libpq.vcxproj]

Note: x86-windows-static and x64-windows-static build fine

cc @Neumann-A

After some further research

The CI pipeline shows libpq passed with the PR #11776 with features core, openssl and zlib features (which I could duplicate)
Adding any of the features icu, nls, xml the port build fails - something with of those ports may be incorrect for dynamic windows builds now?
The libpq dependencies are as follows:

->vcpkg depend-info libpq[core,icu,nls,openssl,xml,zlib]
libiconv:
liblzma:
zlib:
gettext: libiconv
icu:
libxml2: libiconv, liblzma, zlib
openssl:
libpq[xml, icu, zlib, nls, openssl]: gettext, icu, libxml2, openssl, zlib

Just the library names are wrong since the PR changed the names to the correct upstream names for windows. Just needs adjustment of the patches.


Add Merge PDF feature to MediaManip Page

Sample Reference

@smaranjitghose please assign this issue to me

@smaranjitghose please help when i click this button i cannot select any pdf files to test my pdf merger

Could you please share the snapshots of your code?
CC: @anushbhatia

@smaranjitghose the existing cause which helps select files to convert only image files can be selected but not the pdf files..so please tell me how should I do

@smaranjitghose please reply on above

@smaranjitghose the existing cause which helps select files to convert only image files can be selected but not the pdf files..so please tell me how should I do

Can you please attach a clip/screenshot and explain elaborately. I am unable to understand your query.

@smaranjitghose ok I will attach the ss of code I was saying that it is not selecting the files in pdf format

@smaranjitghose @anushbhatia I'd like to try adding this feature!


Group Toggle issue

Running the latest dev branch -
The group card with device trackers (Family) has a toggle switch on it.

I have some questionable things like this as well. I have some that feel like maybe they shouldn't exist and some that should but are missing. Maybe sensors support on/off and I just didn't know?
I'll list them:
System Sensors

Custom Sensors

Automatically Created Media Player group (doesn't show)
These media players do support on/off

Fixed now for non toggle entities.
Media player is a different story, the group state is not detected correctly in the core as being able to turn on/off so the group state = unknown.


Rate limit exceeded / Gdax

Hi guys,
I'm running a live bot from console and I believe my configuration is requesting too much data from GDAX, as I am receiving this error :
[gdax.js] (getTrades) returned an error, retrying: Rate limit exceeded.
The same strategy runs fine from the UI, and it also runs fine live, in console, using paper trader.
I think I have some wrong settings. Does anyone have any ideas
I am sorry in advance if this is a noob question.

Are you running multiple gekkos / other bots from the same account & ip?

Just one instance from the command line. No backtests, no importing, nothing. Just the one

Can you try the new 0.6 release? I've been trading a lot on gdax without any problems. If that does not fix it please comment here, assuming this has been fixed.


'ifconfig' does not work when run arm64 docker from x64 host

Is this a bug report, feature (enhancement) request or question? (leave only one on its own line)
/kind question
Description:
i am running an arm64 docker on x64 host, it is straightforward with qemu-user-static, but inside the arm64 docker, ifconfig does seems good while other binaries are fine.

Steps to reproduce the issue:

docker run --rm -it -v /usr/bin/qemu-aarch64-static:/usr/bin/qemu-aarch64-static arm64v8/ubuntu:18.04 bash
apt update && apt install -y net-tools iputils-ping iproute2
ping <IP_ADDRESS>
# result is fine
ifconfig

Describe the results you received:
: error fetching interface information: Device not found

Describe the results you expected:
# show device details

Environment:

QEMU version: (if you can know it):
qemu-aarch64-static: qemu-aarch64 version 5.0.0 (qemu-5.0.0-2.fc33)
Container application: Docker

Output of docker version, podman version or singularity version
Docker version 19.03.12, build 48a66213fe

Additional information optionally:

Can you use ip? This works for me.

Can you use ip? This works for me.

yes, for this single command, ip works.
i am trying to communicate an arm64 software stack in docker using multicast, but does not come to any solution.
when i try to debug with tcpdump, it says:
tcpdump: Can't get Bluetooth device list via ioctl: Function not implemented

i am not sure if network layer is fully supported.

Maybe this helps you https://github.com/moby/moby/issues/16208#issuecomment-268378445

Maybe this helps you moby/moby#16208 (comment)

finally i am not able to figure it out in my case: multicast + docker + qemu user static + arm64 binary stack
also i cannot apply a full simulation in my target environment.
i pick up a workaround to use x64 peer for my arm64 binary stack.


Add data input and output directories

This cleans up the internal file structure
Fixes #24

Weird character error, closing PR


notification switch

hi
so i really like the extension
but notification every time i log in into my account is kinda annoying
any chance to throw in a toggle to disable it?
thanks

I'll make it an opt-in so that by default no notifications?

@LukIsHere: I just committed something to main that should do the trick if you could try it, that'd be great!

i updated the extension
switched extension off and on, got notification (might have to look into that)
then went to settings toggles notification switch twice (so it was still off)
logged out and in, no notification
so yep it did the trick
thank you very much <3

o yeah also you might also want to update the dconf thingy in the readme

https://github.com/dsheeler/gnome-shell-extensions-gravatar/pull/2#issue-2293185343
should do the trick

@LukIsHere, Thanks!!!


Use new smaller images in processes

Before testing as part of #746, we should substitute in the smaller docker images for the full scpcatools image for each process as appropriate.
This means looking at the script(s) for each step and assessing which of the slimmed images will be most appropriate for that process.
Following this, we will do some additional testing to be sure we made the right choices!

closed by #762


Proposal: New Repo Creation

Proposal
Create a new repo under TODO Group GH Org to allow people to contribute to this, and define a process and roadmap.
Asking for approval from @todogroup/steering-committee
Related discussion: https://github.com/todogroup/ospology/discussions/75

I left a comment on #75 suggesting that we do this in a directory within an existing repo, instead of creating a new repo.

Thanks for the review @geekygirldawn. Based on your comment, final resolution is:

Don't create a new repo, but use existing one to host this. Most likely at 'ospology' repo

Closed with https://github.com/todogroup/ospology/discussions/75#discussioncomment-2461834 / https://github.com/todogroup/ospology/tree/main/ospo-mindmap.


robust close codes

This puts us in position to easily add support for additional codes once we have a complete plan of action for how to handle multiple sockets
Note: commented-out code blocks are intentional; the NotFound close code doesn't quite work as intended, but the rest of these changes are still helpful without it.

@tran2 do you see anything in here that'll impact board?


Use Case: compatible with BagIt

As a repository manager, I want a well-defined way of to creating a BagIt bag from an RO-Crate so that I can leverage existing tooling to track fixity the object payload and metadata over time
See, for example, bagit-ro (https://github.com/ResearchObject/bagit-ro), BDBags and the way in which DataCrate distinguishes Working DataCrates from Bagged DataCrates
@stain, is this what you mean by the "json-in-Github" scenario?

See my comment on #16 - Bagit support is pretty easy to specify but we should also consider other use-cases As a repository manager I want a way to create X packging form from an RO-Crate
where X = OCFL Object | Frictionless Data Package | SWORD wrapper | etc.

Just to add to this use case.
Our service is exporting BagIt archives and it seems that we have a few possibilities when it comes to integrating RO-Crate, shown below.
The data exported as a bag looks like the following
zip_name/
   bag-info.txt
   bagit.txt
   fetch.txt
   manifest-md5.txt
   manifest-sha256.txt
   tagmanifest-md5.txt
   tagmanifest-sha256.txt
   data/
      workspace/
         analysis.R

Adding support for RO-Crate can be done by specifying the RO-Crate Root as the root of the bag, shown below. In this case, the artifacts from our system are placed in data/.
zip_name/
   bag-info.txt
   bagit.txt
   fetch.txt
   manifest-md5.txt
   manifest-sha256.txt
   tagmanifest-md5.txt
   tagmanifest-sha256.txt
   ro-crate-metadata.jsonld
   data/
      workspace/
         analysis.R

We can also place the RO-Crate metadata file in the bag payload, shown below.
zip_name/
   bag-info.txt
   bagit.txt
   fetch.txt
   manifest-md5.txt
   manifest-sha256.txt
   tagmanifest-md5.txt
   tagmanifest-sha256.txt
   data/
      ro-crate-metadata.jsonld
      data/
         workspace/
            analysis.R

Are there any recommendations on which method is preferred?

The DataCrate format which informed RO-Crate explicitly stated that the
metadata should be in the root directory, but RO-Crate is agnostic on this
point - you can do either.
The first approach means that:
Metadata (including the ro-crate-preview.html file you have not shown) is
more discoverable when someone opens the bagit archive
You can change the metadata without changing the payload / checksums
The second gives you more assurance that the files are as expected as the
metadata and preview files have checksums.
We should write this up in an implementation note.
On Wed, 30 Oct 2019 at 07:26, Thomas Thelen<EMAIL_ADDRESS>wrote:

Just to add to this use case.
Our service is exporting BagIt archives and it seems that we have a few
possibilities when it comes to integrating RO-Crate, shown below.
The data exported as a bag looks like the following
zip_name/
bag-info.txt
bagit.txt
fetch.txt
manifest-md5.txt
manifest-sha256.txt
tagmanifest-md5.txt
tagmanifest-sha256.txt
data/
workspace/
analysis.R
Adding support for RO-Crate can be done by specifying the RO-Crate Root as
the root of the bag, shown below. In this case, the artifacts from our
system are placed in data/.
zip_name/
bag-info.txt
bagit.txt
fetch.txt
manifest-md5.txt
manifest-sha256.txt
tagmanifest-md5.txt
tagmanifest-sha256.txt
ro-crate-metadata.jsonld
data/
workspace/
analysis.R
We can also place the RO-Crate metadata file in the bag payload, shown
below.
zip_name/
bag-info.txt
bagit.txt
fetch.txt
manifest-md5.txt
manifest-sha256.txt
tagmanifest-md5.txt
tagmanifest-sha256.txt
data/
ro-crate-metadata.jsonld
data/
workspace/
analysis.R
Are there any recommendations on which method is preferred?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ResearchObject/ro-crate/issues/13?email_source=notifications&email_token=AAFYTWD62DFN2NMRRW3LP4LQRCL7BA5CNFSM4HLXVD72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECR6YZY#issuecomment-547613799,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFYTWFC4FF6YB7GOMJIXUDQRCL7BANCNFSM4HLXVD7Q
.

--
Peter Sefton +61410326955<EMAIL_ADDRESS>http://ptsefton.com
Gmail, Twitter & Skype name: ptsefton

Just to clarify,

You can change the metadata without changing the payload / checksums

I think that ro-crate-metadata.jsonld would be defined as a BagIt tag-file so you'll see changes in the tagmanifest-md5.txt and tagmanifest-sha256.txt files.

Closing this as https://www.researchobject.org/ro-crate/1.1/appendix/implementation-notes.html#adding-ro-crate-to-bagit has been part of the specification  -- it does however have ro-crate-metadata.json inside data/ (which becomes RO-Crate Root) rather than in metadata/ -- see also #78 .


e-directive link update, closes dwyl/learn-json-web-tokens#57

@indieforger well spotted. thanks for updating it. :+1:


Always get error first time I try to create RKE cluster

Rancher versions: 2.0 master 2/4
Steps to Reproduce:

Go to Add RKE cluster
Add 3 DO nodes
First node click all three checkboxes
Second and Third node click worker
Click Create

Results:  Three errors.  They say I haven't chosen any roles for my nodes.  To get past this point I have to click on the "Pick roles" link

Version - 2.0 master 2/5
Verified fixed


Reorder Annotations - User Annotations now above Previous Annotations

PR Overview

This PR reorganises the order of the annotations so...

New (currently in progress) Annotations appear above...
User's (completed) Annottations, which appear above...
Previous (collaborative) Annotations.

This is a visual workaround that essentually fixes #97 .

The core of issue #97 is that when you Agree to a Previous Annotation on page 1, then switch to page 2 then back to page 1, the Previous Annotation now appears overlaid on top of your Agreement Annotation.
This change essentially obscures the Previous Annotation behind the Agreement Annotation instead of simply not rendering the former.
Note: if this is the 'proper' solution going forward, it may also make the ("Reenable Previous Annotation"](https://github.com/zooniverse/liberating-the-liberator/pull/92/commits/8aa9ea56367b4c435deb336f971224f2957d9f03#diff-5815a1d65dcdd68154122cd603a23d9fR41) function introduced in commit 8aa9ea5 mildly redundant.

Status
Ready for review, @wgranger 👍

Thanks for this fix. LGTM.


Add logic to actually save the dashboardwidget.

This is untested but it is code almmost copied from my links module. You should try it out before merge and also check if there already exists a label named Statistics.

Thanks man!


[CogBoard] Add repos and install cogs straight from CogBoard cog

Anyone can try to take this, but I advice to ask about specifics here before taking too much work on this, I have certain requirements about how this should be done.

Resolved by https://github.com/jack1142/JackCogs/commit/954312a5d9004f95f76f036b55fd318ab1455c64


[Button][material-next] Fix some event handlers being ignored

[X] I have followed (at least) the PR section of the contributing guide.

Fixes: https://github.com/mui/material-ui/issues/37645
Four event handlers were not being handled in getRippleHandlers, so those were lost:

onClick
onFocus
onKeyUp
onKeyDown

I also added tests for those events.

Let me know if you think we should add other events to the test.

Hey @mnajdova! Thanks for the feedback. I refactored the fix to use useSlotProps
The test_static test is failing because yarn proptypes wants to remove the four event handlers (onClick, onFocus, onKeyUp, onKeyDown) from the Button's proptypes 🤔 I think that's incorrect, they shouldn't be removed, but I'm not sure, what do you think? Should the inherited props from button be included in the Button component proptypes?

The test_static test is failing because yarn proptypes wants to remove the four event handlers (onClick, onFocus, onKeyUp, onKeyDown) from the Button component's proptypes 🤔 I think that's incorrect, they shouldn't be removed, but I'm not sure, what do you think? Should the inherited props from button be included in the Button component proptypes?

Well this is somewhat expected as we are not handling them in the component, but they are handled in the hook. @michaldudak what are we doing with these use-cases in Base UI?

These event handlers are common to all HTML elements, so they are not explicitly listed in Button or useButton. Also, they are not directly used by the hook (or the component), so essentially, they are not needed (although it does feel weird that onClick isn't defined on a button).

although it does feel weird that onClick isn't defined on a button

We can discuss this separately


[Bug] Build Docker Image CI continuously fails

Search before asking

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

Java Version
CI version.
Scala Version
2.11.x
StreamPark Version
CI version. It should be the master.
Flink Version
Unrelated
deploy mode
None
What happened
https://github.com/apache/incubator-streampark/actions/runs/5865931176/job/15903800600 fails to build
Error Exception
[INFO] ><EMAIL_ADDRESS>build
[INFO] > cross-env NODE_ENV=production NODE_OPTIONS=--max-old-space-size=8192 pnpm vite build
[INFO]
[INFO] node:events:505
[INFO]       throw er; // Unhandled 'error' event
[INFO]       ^
[INFO]
[INFO] Error: spawn pnpm ENOENT
[INFO]     at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
[INFO]     at onErrorNT (node:internal/child_process:478:16)
[INFO]     at processTicksAndRejections (node:internal/process/task_queues:83:21)
[INFO] Emitted 'error' event on ChildProcess instance at:
[INFO]     at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
[INFO]     at onErrorNT (node:internal/child_process:478:16)
[INFO]     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
[INFO]   errno: -2,
[INFO]   code: 'ENOENT',
[INFO]   syscall: 'spawn pnpm',
[INFO]   path: 'pnpm',
[INFO]   spawnargs: [ 'vite', 'build' ]
[INFO] }
[INFO]  ELIFECYCLE  Command failed with exit code 1.

Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?)

Code of Conduct

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

cc @wangsizhu0504 this seems a build failure relates to pnpm setups


Ability to delete attachments in chat

When testing I attached the wrong file (PDF) to the chat and then realised there was no way for me to remove it again.
Priority: Low

Hey @NickThackray, closing this for a few reasons. First, it doesn't have much to do with HedgeHog, our design system. This is more for our API and our frontend.
Secondly, we haven't planned to allow deleting of posts, because doing so would allow you to manipulate the history of a conversation, change its meaning, and create havoc. This is also why systems like WhatsApp or Messenger don't allow you to delete messages (once they've been seen by at least one other person - the seen-by is another can of worms that we haven't looked at just yet ;)).


Parental control

We should define a way to define some access controls in the protocol so that inappropriate rooms and content cannot be viewed.
The public room directory(/publicRooms) could be filtered and /join could check that conditions are right before joining a room.
I have no idea how to implement that in the protocol but this will allow to create safe matrix clients for <17+.

Related: #548

i have thoughts here in the context of general reputation work. i'm not sure whether we should burn time doing particular content tagging (nsfw etc) versus general reputation categorisation.

also related to https://github.com/vector-im/riot-web/issues/4683

In order to add some client constraints, note that, at least on iOS, this is not possible for an app to get the current parental control level. The system parental control is applied from the app store.

A generic tagging mechanism could be used for other filtering, such as for finding rooms in a certain language.

How about just a simple option to disable the browsing of public rooms? Thanks for considering this.

Duplicate of/related to https://github.com/matrix-org/matrix-doc/issues/3107
https://github.com/matrix-org/matrix-doc/issues/3107 has a bunch of thoughts about how could this work and how it should/shouldn't work

FluffyChat request for something like this.