Add missing conditional headers to blob and container operations

Overview
Fix https://github.com/Azure/azure-sdk-for-rust/issues/1276 and add the remaining conditional headers missing from blob and container operations as per the REST API documentation.
Testing
I tested the use case I care about, support for preventing duplicate blob writes, with the following code.
use azure_core::request_options::IfMatchCondition;
use azure_storage::prelude::StorageCredentials;
use azure_storage_blobs::prelude::BlobServiceClient;

#[tokio::main]
async fn main() {
    let token_credential = azure_identity::AzureCliCredential::default();
    let storage_credentials =
        StorageCredentials::token_credential(std::sync::Arc::new(token_credential));

    let blob_client = BlobServiceClient::new("<redacted>".to_string(), storage_credentials)
        .container_client("<redacted>")
        .blob_client("<redacted>");

    // Write blob
    let file = "Message One".as_bytes();
    blob_client
        .put_block_blob(file)
        .if_match(IfMatchCondition::NotMatch("*".into()))
        .await
        .expect("Failed to write message one");

    // Try to overwrite blob
    let file = "Message Two".as_bytes();
    blob_client
        .put_block_blob(file)
        .if_match(IfMatchCondition::NotMatch("*".into()))
        .await
        .expect("Failed to write message two");
}

The output was as expected:
thread 'main' panicked at 'Failed to write message two: Error { context: Full(Custom { kind: HttpResponse { status: Conflict, error_code: Some("BlobAlreadyExists") }, error: HttpError { status: Conflict, details: ErrorDetails { code: Some("BlobAlreadyExists"), message: None }...

@microsoft-github-policy-service agree

Thank you for the contributions!


adds svg heart animation

I want to highlight the liking feature better and improve the liked state. Please check this out and let me know what you think about the visual aspect.

Super cool concept but I feel like the animation is a bit too much :x Can we simplify it to a single heart that expands from the center of the button?

@canterberrie Thanks! I'll take another pass on it.


Create login view

[x] Call the login method on the User class
[x] Send HTTP-only cookie with encrypted JWT token
[x] Send JSON response with encrypted JWT token
[ ] Write unit tests

@Zuiluj please write unit tests for this issue.

Viewable in /pfunk/tests/test_web_login.py in branch feature/api_tests


Package with file license gives incorrect link in the package manager

Summary
I published a package with the following nuspec:
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
  <metadata>
    <id>Gregnk.Duality.Plugins.DualityTools</id>
    <version>1.0.0</version>
    <description>A collection of useful components for the Duality game engine</description>
    <authors>Gregory Karastergios</authors>
    <owners>greg_nk</owners>
    <tags>Duality Plugin Tools</tags>

    <projectUrl>http://gregnk.com/projects/DualityTools.html</projectUrl>
    <repository type="git" url="https://github.com/gregnk/DualityTools.git" />
    <license type="file">LICENSE.md</license>
    <copyright>(C) 2019 Gregory Karastergios</copyright>
    <requireLicenseAcceptance>true</requireLicenseAcceptance>
    <dependencies>
      <dependency id="AdamsLair.Duality" version="3.0.0" />
    </dependencies>
  </metadata>

  <files>
    <file src="DualityTools\bin\Debug\Gregnk.Plugins.DualityTools.core.dll" target="lib\" />
    <file src="DualityTools\bin\Debug\Gregnk.Plugins.DualityTools.core.pdb" target="lib\" />
    <file src="DualityTools\bin\Debug\Gregnk.Plugins.DualityTools.core.xml" target="lib\" />
    <file src="LICENSE.md" target="\" />
  </files>
</package>

The license is defined as a file within the nupkg, however in the package manager it gives a link to an MS article where the license should be.
How to reproduce

Upload a nuspec with the license defined as a file

Attachments

Labeled it as bug due to counter intuitive / incorrect behavior - internally it's clear that this can't work yet, as no support for embedded licenses has been implemented so far.
To add this, we need to check first whether issue #711 is a prerequisite, then figure out how to present this case to the user. The license link could simply open the file from the local package folder instead of a web URL for example.

Ok, as a workaround I will have it point to a link (https://raw.githubusercontent.com/gregnk/DualityTools/master/LICENSE.md) instead of an embedded license.


Ignore hidden and fixed elements

This fixes an issue that https://github.com/brainly/html-sketchapp/commit/6fa6f7f5c4f769b40892b93215e4a6429dab67ca introduced with my style guide.
I narrowed it to this commit by rolling forward commit-by-commit from the last known working version.
Elements that were correctly hidden were suddenly being rendered, and it actually had a knock-on effect where the symbol itself would seemingly become invalid and get ignored by Sketch, leading to a bunch of missing symbols.
The only contentious part of this PR, from what I can tell, is that fixed elements will no longer be rendered, but this seems sensible given we're rendering to Sketch. Happy to alter this PR and check for fixed position if you disagree with this change.

Thank you for contributing!!
I'd keep the fixed layers. I agree that in case of style guides it might not be useful, but since html-sketchapp tries to be generic we shouldn't make any assumptions about how it will be used.

@kdzwinel Updated and renamed based on feedback.

👌 perfect


ironhouse.py allows default NULL connects

I was under the impression that when setting  server.curve_server = True all default NULL sessions would not be allowed to connect. In the example code below, I am using curve_server, but I am still able to inject unauthenticated data.
To reproduce:

Generate keys using generate_certificates.py
Start the modified ironshouse script below
inject data using  cat /dev/random |nc localhost 9000

Versions used:

libzmq-4.0.5
pyzmq-14.5.0
Python-2.7.9

#!/usr/bin/env python
'''
Modified version of ironhouse.
'''

import logging
import os
import sys

import zmq
import zmq.auth
from zmq.auth.thread import ThreadAuthenticator

def run():
    ''' Run Ironhouse example '''

    # These direcotries are generated by the generate_certificates script
    base_dir = os.path.dirname(__file__)
    keys_dir = os.path.join(base_dir, 'certificates')
    public_keys_dir = os.path.join(base_dir, 'public_keys')
    secret_keys_dir = os.path.join(base_dir, 'private_keys')

    if not (os.path.exists(keys_dir) and
            os.path.exists(public_keys_dir) and
            os.path.exists(secret_keys_dir)):
        logging.critical("Certificates are missing - run generate_certificates.py script first")
        sys.exit(1)

    ctx = zmq.Context().instance()

    # Start an authenticator for this context.
    auth = ThreadAuthenticator(ctx)
    auth.start()
    auth.allow('<IP_ADDRESS>')
    # Tell authenticator to use the certificate in a directory
    auth.configure_curve(domain='*', location=public_keys_dir)

    server = ctx.socket(zmq.PULL)

    server_secret_file = os.path.join(secret_keys_dir, "server.key_secret")
    server_public, server_secret = zmq.auth.load_certificate(server_secret_file)
    server.curve_secretkey = server_secret
    server.curve_publickey = server_public
    server.curve_server = True  # must come before bind
    server.bind('tcp://*:9000')

    while True:
        msg = server.recv()
        print msg

    # stop auth thread
    auth.stop()

if __name__ == '__main__':
    if zmq.zmq_version_info() < (4,0):
        raise RuntimeError("Security is not supported in libzmq version < 4.0. libzmq version {0}".format(zmq.zmq_version()))

    if '-v' in sys.argv:
        level = logging.DEBUG
    else:
        level = logging.INFO

    logging.basicConfig(level=level, format="[%(levelname)s] %(message)s")

    run()

I believe this is a known problem, and fixed in libzmq master and 4.1-dev, and I think 4.0.6. I don't believe there has been a release since the fix.


BGE: Quick fix for reference field bug in config wizard

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-033670

Tracking W-033670

@melissabarber - Updated with issues closed and initial description.


Remove version: SmartSoft.SmartFTP version 10.0.3210.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://static.smartftp.com/static/Products/Client/10.0.3210.0/x64/SmartFTP.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


The override_web_audio_api.rs

Changes
"Fixes #2167"
Checklist

[x] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
[ ] ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
[ ] If this PR adds/changes features, documentations (in the ./website folder) are updated.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

Btw it would be great to make the CI pass.
For lints, a quick auto fix command is cargo clippy --fix --allow-dirty --allow-staged -- -D warnings && cargo +nightly fmt
For "Command Generate", a quick command is enter the frb_example/integrate_third_party folder, and then run just codegen generate

@all-contributors please add @Larpoux for code

I will look to that tomorrow.
I appreciate that you give me some help, like that, because you are helping me to learn a little bit better frb, and rust. This is better than doing it yourself.
Thanks for your patience.

Take your time and you are welcome!

Looks great! Now we only need to make ci pass

For lints, a quick auto fix command is cargo clippy --fix --allow-dirty --allow-staged -- -D warnings && cargo +nightly fmt, or alternatively manually check the CI error and change code
For "Command Generate", can run cargo run --manifest-path /path/to/flutter_rust_bridge/frb_codegen/Cargo.toml -- generate on frb_example/integrate_third_party folder

👀 What happened

Good morning my friend. 😃
I just submitted a new Pull Request. I hope that everything good (I did my best).


cla:accepted by utkarsh CONTRIBUTORS.csv

Current behavior

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

@utkarsh1042005 you've already accepted the CLA, please don't spam our repo with new CLA PRs
https://github.com/build-trust/ockam/pulls/utkarsh1042005
Instead, consider contributing to one of our many open issues.


Feature/hendriks/higher level parsers

Hi there, how about some minor refactoring and an update for free?

slight rebase mishap


[TEST] Automating manual regression test cases

What's the test to develop? Please describe
To reduce manual test case execution load, we should have a roadmap plan to increase e2e testing converted from manual regression test cases.
Additional context
cc @longhorn/qa

All new cases should be based on the new framework @yangchiu is working on. Please cooperate with @khushboo-rancher and @yangchiu .

We are tracking this task categories wise in various ticket. This ticket is no longer needed.


React-Native - Calling flagmisth.init on a device without internet connection breaks with  'Cannot read property 'flags' of undefined'

How to reproduce
Using a iOS simulator turn off the internet and call flagmisth.init.
The onError method will be called with the following message: 'Cannot read property 'flags' of undefined'
It seems that the code is not prepare to handle lack of internet connection
Version: 3.10.2

I'll try and replicate this - but from what I can see the only references to flags are from this.flags, indicating that this is undefined.
If I can't replicate it I may ask for an example repro.

Ok, yep could replicate this, the problem is that this was overwriting storage rather than ignoring failed network requests.
I've updated this in 3.11.0, you can run the example react-native app that caches for offline. You can now go offline in this example and it'll revert successfully to cache.

Thanks very much for reporting this!


A11y_Azure Tools Storage Explorer_Properties_Blob Container Properties tab_Usability:The user is able to tab through non interactive text element associated with 'Properties' tab.

GitHubTags: #A11yUsable;#A11yTCS;#A11ySev2;#BM_AzureToolsStorageExplorer_May2022;#Azure Tools Storage Explorer;#MAC;#FTP;#DesktopApp;#Keyboard;#AINotInScope;
Environment Details:
Application Name: Azure Tools Storage Explorer
Application Version: 1.24.0
Mac Version: macOS Monterey 12.3.1
Repro Steps:

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix.
Launch Azure Tools Storage Explorer.
Sign in to Azure.
Tab to 'Explorer' pane tree view.
Navigate to any of the file inside "Blob Containers"
Tab to 'properties' tab.
Turn on voiceover and observe.

Actual:
The user is able to tab through non interactive text element associated with 'Properties' tab.
Expected:
The user should not be able to tab through non interactive text element associated with 'Properties' tab.
User Impact:
Screen reader users will face difficulty in perceiving user interface component.
Attachment:

@bbarik06 If we don't tab through non interactive text element, how would you expect the user to get to know all the available properties?  Some properties can be customized, some just can't be customized, but all info could be important to the users.  Am I missing something to understand this bug?

@jinglouMSFT for keyboard users they would be able to see the content and get all the information and for the screen reader users they can use the (Control + Option + Right/Left Arrow keys) to read next/previous text.
Tab or shift+Tab is used to go to next/previous focusable item (link, button, input, etc.)
Is the 'Properties' tab customizable. I could not find anything which I can change for this tab.


Publishing maven package GitHub action is failing

Description
The update-release-assets GitHub action failed in the last 6.0.0 release. It looks like the 1password key was changed and its reference is not invalid.
https://github.com/MobilityData/gtfs-validator/actions/runs/11521874673/job/32076491158
As a recommendation, we should add the 1password reference as a GitHub environment variable to avoid changing the action code when keys are re-generated/updated.

I believe the entry to use from 1password is:

Vault: TECH: Keys & Tokens
Entry: GPG Key - Maven/Sonatype

And here are the new values of the variables in publish_assets.yml:

MAVEN_GPG_PRIVATE_KEY: "op://rbiv7rvkkrsdlpcrz3bmv7nmcu/dkkfywvsr3xq6eyeubq6cldaxi/Private Key"
MAVEN_GPG_PASSPHRASE: "op://rbiv7rvkkrsdlpcrz3bmv7nmcu/dkkfywvsr3xq6eyeubq6cldaxi/password"

To be confirmed.

I tried publishing from the command line following this , but I got this error:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':core:publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
   > Could not PUT 'https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/org/mobilitydata/gtfs-validator/gtfs-validator-core/6.0.0/gtfs-validator-core-6.0.0.jar'. Received status code 401 from server: Content access is protected by token

It seems sonatype will not accept username/password any more. It will require tokens. See this


Typo in title

Title: Azure Kubernetes Service (OSM)
[Enter feedback here]

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

ID: 762cd89e-4478-f58d-cf76-ab024c1cef61
Version Independent ID: 8dec3455-ec48-b3eb-16d0-cca01ccf8728
Content: Open Service Mesh in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/open-service-mesh-about.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: pgibson

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

@jorisaeles
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Using JSON with JSIL

Is it possible to use a json deserializer with JSIL? I've tried using DataContractJsonSerializer, but it seems there's no implementation for it yet. I've also tried JSON.net and TinyJSON, but those each seem to have snags that cause them to fail.
I'm wondering if it's possible to implement this (perhaps even backed by JSON.stringify/parse)  and if it's something that would be feasible for me to attempt.
Cheers,
Michael

I was successful with running translated JSON,Net (Portable for .Net 4.0 version with some patches).
Before my JSIL fixes will be merged in trunk, you can use JSIL version (https://github.com/iskiselev/JSIL).
I use translated BCL with Expression interpreter for it and some custom class implementation/proxies (not in my repo yet), so I may provide additional instructions on Monday.

A simpler/stripped down JSON parser will definitely work, too. The caveat is that most .NET JSON/XML serializers lean really heavily on reflection.
On the other hand, the built in XmlSerializer works great as long as you do the offline compile first so there's a serializer assembly. You can translate the generated serializer assembly to JS, load it, and be off to the races. So something similar is possible with JSON, if you can find a serialization lib that can do it.


Webmail: Authentication Failed

I've debugged this error for a while, it happens all the time once I try to use webmail interface, something like 'Password mismatch' or 'auth: Debug: client passdb out: FAIL' in my log file. But after I refreshed my webmail page by a couple of times the authentication come back to normal, and Modoboa works fine. It might be tiny configuration mistake, but pretty annoying. Maybe somewhere in Dovecot has a configuration item like 'xxx_timeout'?

Maybe an issue with your dovecot configuration?

Thanks for replying! I've check all my dovecot configuration, since the problem happens occasionally, it can be some kind of "Timeout", I changed my local VPS to another which provide more stable web connection, then everything works fine after re-deploy modoboa.

Great. So I close this issue.

Hey Tonioo,
Sorry to bump this issue up but we are facing exactly the same problem.
The webmail fails completely randomly (maybe one in 5 requests...)
Also, when it fails, I can see this in the logs:
Jun 19 03:15:15 modoboa dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, secured, session=<JuUhM9wY+gB/AAAB>

I'm using the latest version of modoboa (1.3.3) that I tried to migrate from the virtual image provided.
I'm pretty sure this must be a configuration issue, but I have no clue on how to pinpoint it. Also, I tried to enable SASL on postfix, I don't know if this can be related. My /etc/dovecot/conf.d/10-master.conf file looks like this:
service auth {
  unix_listener auth-userdb {
    #mode = 0666
    #user =
    #group =
  }

  # Postfix smtp-auth
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
    user = postfix
    group = postfix
  }

  # Auth process is run as this user.
  user = $default_internal_user
}

Any clue how I could try to pinpoint the problem?

Hi,
the demo VM is pretty outdated now and I've not enough time to work on it. I suggest you install install a fresh server using newer versions.
Don't hesitate to contact me in private in you need help/more information.

Hello. I have this issue after fresh install on ubuntu 14.04 with modoboa-installer. Modoboa version is 1.4.5.
Apr  2 22:22:17 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<admin>, method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, secured, session=<wjxXQIYvMgB/AAAB>

What can I do to fix this?


Browser compatibility?

Hi, thanks for the great library! I've been using it and wonder if it's compatible with all browsers? It seems that occasionally form.valid remains false even when all inputs have been entered. I really appreciate any help anyone can provide. Thanks!

Hey
Well normally it should work for all browsers but I can only confirm it for the ones I actually use (Chrome, Firefox and Safari). Are you also using one of those?
And could you maybe share a repro to this problem so that I can look at it?

I haven't been able to reproduce it myself, but dozens of users who visited my site have said the button remains disabled no matter what they do. I don't know what browsers they use, but if I can reproduce the bug myself, I'll definitely let you know. Thanks!

That sounds kinda urgent 😬
If you want I can also take a look at your site, of course only for debugging purposes. You can use this email<EMAIL_ADDRESS>if you don't want to share the site publicly.

You can check an example here. Upon clicking next, I also called console.log($form) in case that helps a bit with debugging. My hunch is it's some combination of browser and system (maybe mobile?).

It's probably Android since I can confirm that it works on MacOS and Windows for Safari, Chrome, Firefox and Edge and on iOS Safari and Chrome.
I'll try to test it with different devices when I get a chance 👍

Perfect. Thanks! I've tested on a few Android devices and haven't been able to reproduce the issue either. Will update if I have more info.

I've managed to retrieve the browser info from a few users. In fact, it's not Android. I think this one might be a tough one to debug, so don't worry if you don't have time to work on it (it could be a problem with my site, though I've tested on about 1k people now and the overwhelming majority didn't run into any issues).
          browser      version        os resolution
1:    Chrome iPad 97.0.4692.84      iPad  1024x1366
2:  Chrome iPhone 92.0.4515.90    iPhone    414x896
3:  Chrome iPhone 97.0.4692.84    iPhone    428x926
4: Firefox iPhone         40.2    iPhone    414x896
5:         Safari         15.1 Macintosh  1024x1366
6:  Safari iPhone         15.1    iPhone    390x844
7:  Safari iPhone         15.2    iPhone    390x844
8:  Safari iPhone       15.2.1    iPhone    375x812
9:  Safari iPhone      Unknown    iPhone    390x844

That sounds like it could be it!
Probably also cases like 10'000.


Breakage with latest cJSON

The latest cJSON build in the ESP-IDF has changed its API which resulted in a breakage to the cpp_utils.  This issue resolves that problem.
See also:
https://github.com/espressif/esp-idf/issues/1363

Changes made in code.


DAQ parameterization

I believe that I have learned enough about how to address the DAQ for our purposes. The question now becomes how exactly we:

record samples from the DAQ
process those raw samples into numbers that we record to data files
allow the user to make choices about how the above happens

It is important that we create a system that minimizes 'cross talk' and allows for digital background subtraction with more than one chopper. I personally want to create a system with the most transparent parameters as possible.
I have more thoughts but not much time at the moment. Just want to create a place for this discussion to happen right now.

Prescript: I don't really know what the vision for the format of data files is at this point. Do the data files contain a header that describes each of the columns and/or includes scan parameters, maybe instrument data like the monochromator used, etc.? I think we are going to need something like this, I'll assume it for this post.

For future reference, there are DAQ cards that can do simultaneous sampling (http://www.ni.com/datasheet/pdf/en/ds-151). I'm kicking myself for not getting one of those cards. :/

I'm a big fan of having a start and duration time for each channel, maybe with a text warning about how many points should be collected to minimize cross talk. A checkbox option for round robin sampling wouldn't be bad if it is desired. A graphic to show how the shots are allocated might be nice too. I liked the thing that Kent did where he showed all the collected data points over the sampling time and color coded them by channel. I'd consider that a nice bonus feature.

2&3) Normalization: I think we should include the ability to do shot-by-shot normalization. I don't really know how the DAQ works right now, how the data is transferred and manipulated by the computer, etc. It seems like since we can display every shot point on the screen that we can take those shot arrays and manipulate them directly in a aio0/(aio1*aio2) kind of way. As for user control, a simple "Normalize by" checklist could do the trick, something like this:

Photon counting for PMTs: This should include a sorting function. In addition to returning the average voltage over the specified number of shots, the program should, given two voltages, return the number of shots below the bottom voltage, between the two voltages, and above the top voltage. A cute fish (Poisson) distribution calculator determining the average number of photons per shot from this data would be great (and very very simple). Additional ability to normalize this to other inputs (like pyros) should also be possible.
PMT & Boxcar overvoltage warning: PMTs can short if they get too much light, but individual shots doing that isn't reflected in the average. It should be very clear to the user if this is happening. Flashing lights and sounds are appropriate. Also, if the voltage coming out of the boxcar is at the max for the boxcar, there should be similar warnings.
Very Simple Chopping: If there is only one chopper and the sign of the data isn't informative, then no output from the chopper is needed. The user could perhaps select from a checklist which aio channels are chopped and just return the absolute value of the difference of those channels.
Complicated Chopping: The phase of each chopper is selected from a carefully chosen point from the output of the chopper. Recognize the channels with the chopper inputs as choppers, allow the user to select an OPA beam line or omega number or other light source to associate with the chopper.  The raw (category averaged) data should be saved in columns with an appropriate binary header using a drop down menu (e.g. 011 for beam 0 off and beams 1 and 2 on or whatever). These categories can also be used as math (111 - 100 - 000 = data column) and saved as separate columns in the data file. This system hangs on to all the data, gives the user something to look at immediately, saves the processed data so it doesn't have to be re-calculated, etc. Again, it would be good to do shot-by-shot normalization with each of these additional "sub-channels." The nice thing about all of this is that the software doesn't need to know anything about the frequencies of the choppers or anything else, it uses only what it needs and gives the user everything they could want. Maybe the programmatic solution is to make virtual channel objects that can be treated like channels for data processing purposes but that are separate from the DAQ itself. Maybe there should be a chopper hardware object and these settings could be set up in the advanced tab of that hardware.
That is what I've thought of so far. What do you think?

Just remembered something else. Having a baseline corrected signal for time dependant signals like pyros and photodiodes would be nice. This would probably require a separate acquisition start time and duration. Maybe the way to do that would be to have two different virtual channel objects that take data from the same aio, but then math happens to give an output that the user wants, etc. Not committed to that idea at all, just throwing stuff out there.

I think we've agreed on how the DAQ should work in broad strokes. We can create individual issues if there are fine tuning features or bugs.


Add createListSignal to SignalsAutoDisposeMixin

SignalsAutoDisposeMixin is awesome, but it lacks createListSignal.

That's what bindSignal is for!


chore: change user/event count computing method

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
cherry pick #1415
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :exclamation: Error
Triggered by @llmin on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:exclamation: Error
73.50
< 80

Duplicated lines density
:white_check_mark: OK
5.20
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/5/2024, 12:11:26 (UTC+0)

SonarQube Quality Gate Result

Result: :exclamation: Error
Triggered by @llmin on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:exclamation: Error
73.60
< 80

Duplicated lines density
:white_check_mark: OK
5.20
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/5/2024, 13:23:52 (UTC+0)

SonarQube Quality Gate Result

Result: :exclamation: Error
Triggered by @llmin on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:exclamation: Error
73.60
< 80

Duplicated lines density
:white_check_mark: OK
5.20
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/5/2024, 15:06:51 (UTC+0)


Problem with LSDI option on BMTI density estimation

Subject of the issue
When using delta_F_inv_cov="LSDI" while calling compute_density_BMTI, an error appears and the call crashes.
Your environment
colab notebook, python 3.10, direct installation of dadapy with !pip install dadapy provides "Successfully installed dadapy-0.3.1"
Steps to reproduce
X = np.genfromtxt(fname="./Fig1.dat")
data = Data(coordinates=X)
data.compute_distances(maxk=1000, metric="euclidean")
_ = data.compute_id_2NN(algorithm="base", mu_fraction=0.9, data_fraction=1)
data.compute_kstar()
data.compute_density_BMTI(delta_F_inv_cov="LSDI", comp_log_den_err=True, alpha=0.7)
Expected behaviour
Compute densities as in the case "delta_F_inv_cov=uncorr".
Actual behaviour
Crashes with the error:
/usr/local/lib/python3.10/dist-packages/dadapy/density_advanced.py in compute_density_BMTI(self, delta_F_inv_cov, comp_log_den_err, mem_efficient, alpha, log_den, log_den_err)
338
339         # define the likelihood covarince matrix
--> 340         A, deltaFcum = self._get_BMTI_reg_linear_system(delta_F_inv_cov, alpha)
341
342         sec2 = time.time()
/usr/local/lib/python3.10/dist-packages/dadapy/density_advanced.py in _get_BMTI_reg_linear_system(self, delta_F_inv_cov, alpha)
381             )
382         elif delta_F_inv_cov == "LSDI":
--> 383             self.compute_deltaFs_inv_cross_covariance()
384             tmpvec = self.inv_deltaFs_cov
385
/usr/local/lib/python3.10/dist-packages/dadapy/density_advanced.py in compute_deltaFs_inv_cross_covariance(self, pearson_method)
251         sec = time.time()
252         # compute a diagonal approximation of the inverse of the cross-covariance matrix
--> 253         self.inv_deltaFs_cov = cgr.return_deltaFs_inv_cross_covariance(
254             self.grads_var,
255             self.neigh_vector_diffs,
cython_grads.pyx in dadapy._cython.cython_grads.return_deltaFs_inv_cross_covariance()
ValueError: Buffer has wrong number of dimensions (expected 3, got 2)

I found the bug. It was a remainder of when we used only one name, "grads_var" and a flag to check whether grads_var was an array of vectors (variance per gradient component for each point i) or of matrices (autocovariance matrix of the gradient at each point i). Then we changed to grads_var and grads_covmat, two separate attributes of the class, but I forgot to change it in the specific function.
If you want, you can mark the issue as solved.
The numerics of the matrix inversion need to be checked I feel, but this is another issue :)


[master] Auto-update dependencies

Produced via:
./hack/update-deps.sh --upgrade && ./hack/update-codegen.sh
/assign n3wscott shashwathi tanzeeb
/cc n3wscott shashwathi tanzeeb

/lgtm

/test pull-knative-sandbox-net-contour-integration-tests
On Tue, Aug 11, 2020 at 10:34 AM Knative Prow Robot <
<EMAIL_ADDRESS>wrote:

@mattmoor https://github.com/mattmoor: The following test failed, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-knative-sandbox-net-contour-integration-tests 16803d9
https://github.com/knative-sandbox/net-contour/commit/16803d985938d9a549d25902ea0afe8bc7dc31cf
link
https://prow.knative.dev/view/gs/knative-prow/pr-logs/pull/knative-sandbox_net-contour/192/pull-knative-sandbox-net-contour-integration-tests/1293187031618293761 /test
pull-knative-sandbox-net-contour-integration-tests
Full PR test history
https://gubernator.knative.dev/pr/knative-sandbox_net-contour/192. Your
PR dashboard https://gubernator.knative.dev/pr/mattmoor.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/knative-sandbox/net-contour/pull/192#issuecomment-671983705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAERAUFB6YVPNQDJG3RERDSAFJGTANCNFSM4PZ74OWA
.

/lgtm
/approve


MDC-103(103-starter) Error: The prefix "tools" for attribute "tools:targetApi" associated with an element type "item" is not bound

Describe the bug
Could not build when implement code as instruction. shows error,
Error: The prefix "tools" for attribute "tools:targetApi" associated with an element type "item" is not bound

To Reproduce
Steps to reproduce the behavior:

Download repo
Checkout 103-starter branch
Edit colors.xml and styles.xml from example
See error

Expected behavior
build should be successful, but it didn't
Codelab details (please complete the following information about the codelab):

Level MDC-103
Language Java
Link https://codelabs.developers.google.com/codelabs/mdc-103-java/index.html#2

update the resources tag in styles.xml as follows
<resources xmlns:tools="http://schemas.android.com/tools">
It will fix the issue.

To fix the bug, I needed to replace the resources tag as follows:


[feature] parse all JSON credential content into plain secret

When playing with Cloud object storage service,   its credential looks like:
{
  "apikey": "xxxxx",
  "cos_hmac_keys": {
    "access_key_id": "xxxx",
    "secret_access_key": "xxxx"
  },
  "endpoints": "https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints",
  "iam_apikey_description": "xxxx",
  "iam_apikey_name": "test-cos-crendentail",
  "iam_role_crn": "xxxx",
  "iam_serviceid_crn": "xxxx",
  "resource_instance_id": "xxxx"
}

In current implementation,  the cos_hmac_keys are saved as the JSON format in kube secret.
apiVersion: v1
data:
  apikey: xxx
  cos_hmac_keys: xxx
  ....
kind: Secret

Is that possible to parse the inner JSON as well  to create secret as below format ?
apiVersion: v1
data:
  apikey: xxx
  cos_hmac_keys.access_key_id: xxx
 cos_hmac_keys.secret_access_key: xxx
  ....
kind: Secret

Discussion in https://ibm-cloudplatform.slack.com/archives/CU3795MNE/p1587454501008000

From Mandana Vaziri  and @pdettori
The user will be able to specify what they want in the secret explicitly (optionally) by having the following in the spec of the binding resource:
secret-content:
- name: cos-hmac-keys-access-key-id
  value: <path-to-value-in-credentials>
- name: cos-hmac-keys-secret-access-key
  value: <path-to-value-in-credentials>

where the paths will be given using go templates.
This would be accomodate other use cases we’ve seen where the credentials are very complicated and that also need some data transformation.
Our Binding controller will take this spec and produce the correct data in the secret

My response:
Thinking from end user perspective, ICO used for Coligo project, Coligo will expose the CLI to create binding CR to get credential from cloud to create secret in kube. The CLI will be like coligo create binding --service-instance service1 --credential-name credential1 From CLI perspective, it is hard to know how to create secret-content , to do that it will need to parser the credential json to see if it has 2 levels json, then create the template. I think it is not the responsiblity for CLI, but for ICO. Because ICO is special for IBM Cloud service integration it should service credential parser, and ICO already parser the service credential json (first level). So suggest to add new field in binding CR spec or annotation to indicate to parser all json levels to generate plain secret, like recursive-parser: true  It will help to keep back compatible, and also support service credential which has >2 json levels.

@Zhuang The coligo CLI will surely have to accept payloads for parameters. The above command works for simple cases, but in general bindings have parameters (to set the level of permissions for example). The shape of the secret created can be passed in the CLI in the same way.
A 2-level json unwinding is not enough for credentials of e.g. postgresql, which is many levels deep, and has arrays.

@vazirim Thank you for your response. And you provided an example for postgres which has multiple json levels of credential as below.
{
  "connection": {
    "cli": {
      "arguments": [
        [
          "host=95346614-149f-408a-afe8-<...>.databases.appdomain.cloud port=30361 dbname=ibmclouddb user=ibm_cloud_<...> sslmode=verify-full"
        ]
      ],
      "bin": "psql",
      "certificate": {
        "certificate_base64": "<...>"
      },
      "composed": [
        "PGPASSWORD=<...> PGSSLROOTCERT=<...>  psql 'host=95346614-149f-408a-afe8-<...>.databases.appdomain.cloud port=30361 dbname=ibmclouddb user=ibm_cloud_<...> sslmode=verify-full'"
      ],
      "environment": {
        "PGPASSWORD": "<...>",
        "PGSSLROOTCERT": "<...>"
      },
      "type": "cli"
    },
    "postgres": {
      "authentication": {
        "method": "direct",
        "password": "<...>",
        "username": "ibm_cloud_<...>"
      },
      "certificate": {
        "certificate_base64": "<...> f"
      },
      "composed": [
        "postgres://ibm_cloud_393ebef5_1225_4834_8785_<...>@95346614-149f-408a-afe8-<...>.databases.appdomain.cloud:30361/ibmclouddb?sslmode=verify-full"
      ],
      "database": "ibmclouddb",
      "hosts": [
        {
          "hostname": "95346614-149f-408a-afe8-<...>.databases.appdomain.cloud",
          "port": 30361
        }
      ],
      "path": "/ibmclouddb",
      "query_options": {
        "sslmode": "verify-full"
      },
      "scheme": "postgres",
      "type": "uri"
    }
  },
  "instance_administration_api": {
    "deployment_id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/<...>:95346614-149f-408a-afe8-00099dd89082::",
    "instance_id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/<...>:95346614-149f-408a-afe8-00099dd89082::",
    "root": "https://api.us-south.databases.cloud.ibm.com/v4/ibm"
  }
}

I agree that it is hard to do plane format conversion. So I think your proposal above is good to help end user to parser these multiple level json format as end user may only care of several parameters but not all of them.
Thank you.


Add LUA Token and TOMOE to popular tokens list

Can you take a look our pull request @nishadsingh1 ?
We need it to listing TOMOE and LUA on Serum.
Thank you.

@nishadsingh1 Can you help me to review this pull request, thanks in advance.

Closing as these were added in 4c45341e3139b2f9764811fdbb1def2ec39d4f8f

Icon was added here 604fa4b2937e6b1742f826c69a4ca4db3aa4b8e5 Thanks!


Preview for .cjs file doesn't have formatting

Microsoft PowerToys version
0.70.1
Installation method
GitHub
Running as admin
No
Area(s) with issue?
File Explorer: Preview Pane
Steps to reproduce

Open the file explorer with the preview pane (Alt + P)
Click on a .cjs file

✔ Expected Behavior
The preview to be formatted like .js or .mjs files as shown above. (extension changed to .js)

❌ Actual Behavior
The preview pane has a white background with black text

Other Software
No response

Seems related to #22945


[DNM] Just for toolchain

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.


French translation

@Vertylo thank you so much for translating this. I'm sure to have more to translate as I continue to implement i18n across the app. If you would be interested in continuing to help, I'll add more entries into those translation files over the next week. You can also poke me on Discord if you have any questions.


feat(sse): add support for server side events

This commit adds support for http server side event streaming by setting the axios responseType to 'stream' when the Accept header is 'text/event-stream'

 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.

Thanks for the PR @apaparazzi0329 !
As discussed offline, this may be better suited to a change in the SDK itself. I'm going to close this for now.


Bot failed to start

Describe the bug
The Bot status is "Failed"

I am trying to start the weather bot (of the tutorials) .. .it was working fine till the section of reading the weather via and HTTP request to "openweather".
The return of the request was correct.
Then after doing the steps to install Cancel and Help, and then add an "Attachment" to report the output of the HTTP request to get the weather, then the Bot would not start.

Version

I am using version 2
Browser

[ ] Electron distribution
[x ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[x ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

Thank you Steven,
I was able to resolve the problem, I think it was an oversight on my part.
On Wed, May 31, 2023 at 4:20 PM Steven Kanberg @.***>
wrote:

@frgregb https://github.com/frgregb - Can you provide exact steps that
repro'ing the issue? To that end:

Is it only with both an HTTP request and installing the Cancel and
Help package (with the attachment) that causes the problem?
Have you tried the same with a new bot and does the issue persist
then?
If you create a new bot for each, does each run if you only make the
HTTP request or if you only install the Cancel and Help package?
Are you able to include a copy of your bot (in a zip file) that I
can use to repro the issue with? Or can you include exact steps

—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/BotFramework-Composer/issues/9586#issuecomment-1571087848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJTE4R7UDIKHC5CKIFWSPPLXI7G3RANCNFSM6AAAAAAYLFLDHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing as resolved.


Improved Random Colour Generator

Improve the Whole UI of Random Colour Generator as the website was empty ! Also ADDED A COPY TO CLIPBOARD SECTION which will enable the user to copy the colour codes which will be generated !
Issue No = #380

@Priyanshi662 Please review this PR !!

@Priyanshi662 Please review this PR !!


enables search for unknown operators- fixes #1849 #1743

enables URL search

Automated message from Dropbox CLA bot
@reyha, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@reyha, thanks for signing the CLA!

I think I knew why you are getting Travis CI failed tests, when you double quote every search string that contains a colon we are losing a very important functionality here which is the ability to narrow to a stream and viewing private messages with someone because these functionalities use special search strings with colons inside them and here you are quoting these strings so they are used as string literals when searching. I think the problem lies somewhere else in the code.

I am auto-quoting the URL only and not all the strings containing a colon as per my last commit but still some tests fail on Travis CI.

The current specific failure is a nondeterministic test failure (i.e. it fails occasionally) in an existing test that we've been trying to track down; you can ignore it.

Also, what do you think of the approach in #1849?  That seems potentially better since it would handle other strings that contain a : but are not URLs...

@timabbott  Thanks a lot for your suggestions about the improving the code style. All the Travis CI tests seem to work fine now. The approach used in #1849 definitely seems to be more rational as it covers all the different search items containing a colon (:).

@reyha Thanks for referencing the issue number of the issue this pull request addresses!
I want to point you to our guidelines for how to format your commit messages. (This is of course less immediately crucial than the code review that Tim's given you, but I figure it's never too early for you to start getting into the right habits. A more descriptive name in the commit message makes it easier for developers to see what you changed. Similarly, aa more descriptive name for the pull request -- check out other pull request titles for an example -- makes it easier for other Zulip developers to skim the list of pull requests and see what their peers are doing.)
For help with changing commit messages, git rebase --interactive is the tool I use, but you should be careful with it since it can rewrite history and you can lose work -- feel free to ask us for help in livechat at https://zulip.tabbott.net/# .

@brainwane  Thanks a lot! This is really very helpful. I will surely try to name the commit messages more vividly.

@timabbott I think this is ready for re-review, if I'm not mistaken.

As discussed in both this thread and https://github.com/zulip/zulip/pull/1849, I think the code for this will be a lot cleaner if we take the approach of modifying Filter.parse()  used in that PR, since that will preserve the current property that we're doing all the parsing of the user input in one place.

@reyha if you'd like you can try reworking your changes to instead be improvements to Filter.parse.  The discussion in #1849 is likely helpful, even though the implementation in that PR is not working.

@timabbott I am on it. I will try to implement it that way.

@reyha this code looks correct!  However, you have some test failures in Travis CI.  The frontend test failure was the result of an unrelated bug in master, which I just fixed; if you rebase on top of upstream/master and squash your branch, you should pass the frontend tests.
(Also, you have some trailing whitespace; run tools/lint-all to see it; you'll need to fix that before we can merge your code).
Can you add a couple tests for the new functionality in frontend_tests/node_tests/filter.js, specifically in the test_parse method?

@timabbott  I am trying to squash my commits but I am unable to do so as I committed those files from another system, so I do not have them in my git log. Should I open a new PR for this?
Moreover, I am currently learning as to how to we add tests in zulip as I am relatively new to this. I will soon  be adding some tests for the new functionalities in the frontend_tests/node_tests/filter.js.

You can use the reset-to-pull-request tool to fetch the commits from one system to another -- no need to create a new PR.

@timabbott  I have rebased on top of upstream/master and have squash my branch, still one frontend test is failing. All other tests seem to work fine.

@reyha Thanks for the update!
You can take out "remvoing trailing white space" from your commit message -- I figure that got into the commit message when you squashed together two commits, one of which included that as its commit message, but since the unified commit does not remove any trailing whitespace from the Zulip codebase, you can take it out. :)

@brainwane Thanks for pointing this out. I just updated the commit message.

@reyha the casper test failure that you were getting was because of an issue with the operator_to_prefix function that you were trying to use; I fixed that issue via 8f71d3702b209040229d2b74177c9e69cb575b83.
For the Node test, adding something like this to the parse tests in frontend_tests/node_tests/filter.js should work pretty well:
+    string = 'https://www.google.com';
+    operators = [
+        {operator: 'search', operand: 'https://www.google.com'}
+    ];
+    _test();

I added that test and merged this as 537c9755bf6a666ef394506409f8fcc571f703ac.
The one remaining issue with this is that I tested this in the Zulip development environment, and found some unfortunate highlighting issues with actually searching for a URL doesn't work so well.  I'll open a follow-up issue for that.

See https://github.com/zulip/zulip/issues/2038 for the follow-up issue.


doing in two lines what can do in one

the second line here is nonsense (comparing the interrupt register with the thread pointer) and suppose to be alwais branch:
https://github.com/azure-rtos/threadx/blob/609c75a2e51735fa3ad894e0caef595ab71ba6c9/ports/arc_em/metaware/src/tx_thread_context_restore.s#L165-L166
I think you can replace it with:
breq    r2, 0, __tx_thread_preempt_restore       ; If not set, preempt executing thread

oops, you are right, my mistake


Bootstrap navbar fix is not needed anymore

Description
since Hyas uses bootstrap 5
/** Bootstrap navbar fix (https://git.io/fADqW) */
is not needed anymore.
Steps to reproduce
Create a hyas site
add bootstrap js to script-footer.html
{{ $bootstrap := resources.Get "js/vendor/bootstrap/dist/js/bootstrap.bundle.min.js" -}}
{{ $js := slice $bootstrap $lazysizes $app | resources.Concat "main.js" -}}

heeder.html

    Navbar
    <button
      class="navbar-toggler"
      type="button"
      data-bs-toggle="collapse"
      data-bs-target="#navbarNavDropdown"
    >

    </button>

          First

          Second

Expected result
There must be a hamburger menu icon on the mobile version of the menu
Actual result
background image removed by _variables.scss file
Solution
I have sent a pull request.
following lines must be removed from the _variables.scss file.

/** Bootstrap navbar fix (https://git.io/fADqW) */
$navbar-dark-toggler-icon-bg: none;
$navbar-light-toggler-icon-bg: none;

@kaanguru, thanks for indicating this! However, your PR is from your master branch (and not from a fork) — resulting in errors /file changes that are not relevant. To speed things up, I've added the fix myself: 2031c4ebcd9b8405cf9f488b6f6d67049a08c2b5


Processor unit tests

@ymatsuda
"./gradlew streaming:jar" succeeds again, finally.

Fix the StreamTaskTest.
Fix ProcessorJob example code.

@ymatsuda
Now "./gradlew stream:test" works, but 10 out of 29 tests fails.. Could we work in parallel to fix them after checking this in?

OK. Let's merge your PR.

@ymatsuda do you have other comments for this one?


Storing responses

Hi, thank you for a great library. I'm using this to build a questionnaire app. Is there a way to store the responses to all of the steps?

Hi, thank you for a great library. I'm using this to build a questionnaire app. Is there a way to store the responses to all of the steps?

Hi, sorry for the delay in getting back. I'm not sure it is in scope of this library. If you have a repo, I'd be happy to give any tips!

Closed due to inactivity.


fix: Remve aspx from DotNet link

@nschonni : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/debugger/project-settings-for-a-visual-basic-debug-configuration.md
:white_check_mark:Succeeded

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

#sign-off


Feature/gitlab fix

Fixes the issue where we were grouping workflows on my workflows by only the org, and not by the source control and org.
Also started merging code for the my tools and my workflows, there is a lot of overlap now. Still lots more to be done though.

Codecov Report

Merging #279 into develop will increase coverage by 0.67%.
The diff coverage is 48.95%.

@@             Coverage Diff             @@
##           develop     #279      +/-   ##
===========================================
+ Coverage     62.8%   63.47%   +0.67%
===========================================
  Files          118      121       +3
  Lines         3611     3628      +17
  Branches       402      398       -4
===========================================
+ Hits          2268     2303      +35
+ Misses        1242     1236       -6
+ Partials       101       89      -12

Impacted Files
Coverage Δ

src/app/myworkflows/myworkflows.service.ts
53.33% <100%> (+1.6%)
:arrow_up:

src/app/mytools/mytools.service.ts
100% <100%> (+38.29%)
:arrow_up:

...p/myworkflows/my-workflow/my-workflow.component.ts
48.67% <15.38%> (+3.95%)
:arrow_up:

src/app/shared/my-entry.ts
69.44% <28.57%> (-26.21%)
:arrow_down:

src/app/shared/myentries.service.ts
63.04% <63.04%> (ø)

src/app/shared/toaster/toaster.component.ts
100% <0%> (ø)

src/app/shared/toaster/toaster.module.ts
100% <0%> (ø)

...pp/workflow/version-modal/version-modal.service.ts
79.48% <0%> (+0.17%)
:arrow_up:

src/app/shared/refresh.service.ts
87.65% <0%> (+4.6%)
:arrow_up:

Continue to review full report at Codecov.

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

Pending builds

@garyluu


Restore default request service feature after middleware completes

Issue describing the changes in this PR
During a review of a problem one of my client faces I dug deeper into the middleware and was wondering why the request service feature is not restored after the pipeline executed. This implementation seems to be more correct and avoids the context scope to leak into other middlewares
Pull request checklist

[x] My changes do not require documentation changes

[x] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[ ] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[x] I have added all required tests (Unit tests, E2E tests)

Additional information
Additional PR information

@danielmarbach do you mind rebasing main so we can run the CI? Thanks!

Done
FYI I have previously already set

Allow edits by maintainers

/azp run dotnet-worker.public

@danielmarbach have you validated what was stated above? The scope here should not lead to middleware outside of this context. If you've observed that, can you share a repro?
The disposal here doesn't hurt, but will also be a no-op, as the feature is initialized with an externally provided service provider.

Like I mentioned above, I reviewed the function code to troubleshoot an issue we saw with a client code. During that review, I stumbled over this code and was thinking that the way this is structured it could lead to the context scope leaking. I wrote a quick test to verify that, which failed, and then added a potential fix for it. I'm not attached to this code. If you feel it is not worth pulling this in that's totally fine for me but I'm also not investing more time into it either ;)


Get service URL on demand

Does not fix #23, but it allows users to force the service url if needed.

Update: instead of the env var, I just moved the service url inference to where the auth envelope is handled.

The getServiceBaseURL() is is just a best-effort attempt and it will fail if the server is behind a proxy and the proxy isn't setting the expected headers correctly, so I don't think we can rely on it 100%, we should leave open the option for relay.ServiceURL to be hardcoded or specified in some other way by the relay developer/runner.

Sure, brought back the env var

Honestly this is the ugliest PR I've ever received.


Support PrimeNg version 17

The current template did not support PrimeNg version 17

@pctimhk just curious, I just tried applying the Sakai-ng layout to my Angular 17.1.0 / PrimeNg 17.11.0 app and am now seeing errors about "Providers from the BrowserModule have already been loaded."  Is this what others are seeing or is it something different?
The demo app that comes with the template seems to be based on Angular 17.0.5 / PrimeNg 17.2.

@pctimhk This template works fine with primeng v.17+. Please specify what exactly doesn't work in your case.
@dgashby This error means that the application is trying to load the BrowserModule again even though it is already loaded. In this template, the BrowserModule template is loaded in app.layout.module.ts. You probably also added this module in your existing application, make sure that it will be loaded only once (via a shared module etc.)


Error net.dll+0x56a8

When I start Minecraft, my Minecraft does not start and that's the problem in the logs
Problematic frame:
C [net.dll + 0x56a8]

Looks like you're using an unsupported launcher.  You'll have to likely report this issue to them.


Question: How to load Socket.io-client and other libraries that only support require?

Sorry in advance for opening this as an issue but trying to get my head around all the new changes that are happening within vue 3 and their libraries within vite.
For 2-3 days now I've been struggling to import a 'smarter' library (like socket.io-client) than a simple ws wrapper or native web-sockets and whatever I try throw errors of 'default' is not been exported by these libraries.
I realised that any library without support of ES6 import is not supported.
Also tried vue & vue-next implementations of web-socket libraries but without any luck.
Can someone please explain with a few words how and if possible to overpass this problem within vite?
I have a simple vite codesandbox; if you can use it please to explain:
https://codesandbox.io/s/vite-tailwind-starter-04mrv?file=/src/main.js
Many Thanks

Vite only support es module. You can ask libraries provider an es module package.
Other, maybe you can have a try with blew config in vite.config.js.(This not recommend)
 optimizeDeps: {
    include: [//libraries ]
  }

Thank you @underfin.
In snowpack I found this solution: https://github.com/pikapkg/snowpack/issues/62#issuecomment-518291535
Is there an equivalent way within vite to convert unsupported libraries and integrate this solution?

Yeah.Have a try with blew config in vite.config.js.(This not recommend)
 optimizeDeps: {
    include: [//libraries ]
  }

@underfin unfortunately this doesn't work for socket.io-client.

@gianniskarmas .I fix it and wait this reslove.

Hi just to be sure, is it normal that I get this error on my end ?
[vite] Dep optimization failed with error:
Dependency debug is attempting to import Node built-in module tty.
This will not work in a browser environment.
Imported by: node_modules/socket.io-client/node_modules/debug/src/node.js

I did add it to my vite.config.js file
optimizeDeps: {
        include: [
            'socket.io-client',
        ],
},

Thanks in advance

import socket from "socket.io-client/dist/socket.io.js"; worked for me. Sadly this breaks IntelliSense.

Thanks @derappelt, live safer 👍

As @derappelt mentions, you can use
import socketio from 'socket.io-client/dist/socket.io.js'

In order to fix intellisense, create a TypeScript definition file and put in your project. The name is not important, but I named it socketio-client.d.ts
declare module "socket.io-client/dist/socket.io.js" {
    export * from 'socket.io-client'
}

This fixed intellisense issues for me.

I fixed it with:
  resolve: {
    alias: {
      "socket.io-client": "socket.io-client/dist/socket.io.js",
    },
  },

in vite.config.js
Still not ideal, but better than having to import from a different path in code.


Add new 'ACKEE_AUTO_FQDN_ORIGIN' method of adding CORS Headers

Previously there were two builtin methods of adding CORS headers to ACKEE:

Set a wildcard header (ACKEE_ALLOW_ORIGIN=*); or
Set a concrete list of domains (ACKEE_ALLOW_ORIGIN=domain1.example.com,domain2.example.com)
However these become very annoying (either insecure or tedious) to configure when working with more than a couple of domains.

This commit proposes adding a new method 'ACKEE_AUTO_FQDN_ORIGIN' to figure out which domains to add CORS Headers for.
Instead of hard-coding the domains, this mode instead determines them from the list of tracking domains.
Concretely, each domain in the domain list that has a fully qualified domain name as a title is treated as a valid domain to add a CORS header for.
The implementation is achieved by means of a new 'domainFqNames.js' utility, which uses the 'is-valid-domain' npm package to filter the list of domains.
Additionally the 'findMatchingOrigin.js' utility is modified to make use of the above.
A second equivalent implementation is added to 'serverless.js'.
This commit also adds a test for the new functionality, although this does not test the serverless implementation.

As I already mentioned in #159 I would appreciate such a feature as it's very cumbersome to manually ssh into my server and add the domain to the env variable ACKEE_ALLOW_ORIGIN every time I want to add a new site.
I also think the way this PR implements it is great as it works around the limitation mentioned in https://github.com/electerious/Ackee/issues/159#issuecomment-693226854.

This looks great! I just don't have the time to review and test the PR, but I will keep it on my list when I'm back working on Ackee. Thanks for the work!

Any updates on merging or not merging this?

This would be very nice to have, currently I'm entering all the cors domains by hand, which is really annoying

Same, @electerious  anything I can do to help get this merged?

Merged! Thanks a lot for your work. The option is now called ACKEE_AUTO_ORIGIN and a part of the develop branch. There's however a blocker for serverless installations which is why I can't completely test the implementation: https://github.com/electerious/Ackee/issues/307 Help is welcome!


fix argo deploy

please make sure to define your merge request to rookout/microservices-demo:master instead of the default GoogleCloudPlatform/microservices-demo:master

/jira open task


Latest version and the version right before it is stuck on Preloading

Hey I ran into a bit of a problem today. I tried download by using username until it kept getting stuck on Preloading. It was working last night but now is having troubles. I tried using a vpn, a previous version, and also testing different usernames. Thanks and hope you can fix it.
P.S sorry this is sort of a duplicate issue but It was working perfectly yesterday and now it doesn't, was just wondering if something is wrong.

Same problem here just says preloading..... until it gives:
Preloading...Failed to get user uploads: context deadline exceeded

the tool is working fine for me right now.
if you hammer the tiktok servers with too many requests in a short amount of time, the tool will start to give this error. wait some hours or a day, and it will start working again.

Is it possible to have a delay between searches then? That would be useful.

Same issue .. its simply stuck at preloading

the tool is working fine for me right now.
if you hammer the tiktok servers with too many requests in a short amount of time, the tool will start to give this error. wait some hours or a day, and it will start working again.

Dude i used this thing for first time today still got stuck at preloading , it think it may have something to do with the executable itself

You can continue discussions on https://github.com/pikami/tiktok-dl/issues/32


Standardise empty lines at the beginning and end of a class

Currently, adding a space at the start/end of a class is not standardised.
class Example {

    // ^ empty line at start of class

    // fields, methods, nested classes, ...

    // v empty line at end of class

}

We should remove all instances of these empty lines, which can be enforced in checkstyle.xml. See https://github.com/checkstyle/checkstyle/issues/3379

Not very important as of now.

Closing as unimportant


feat: Add new ptn modules avm/ptn/azd/container-app

Description
Fixes https://github.com/Azure/Azure-Verified-Modules/issues/1221

Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] I have run Set-AVMModule locally to generate the supporting module files.
[x] My corresponding pipelines / checks run clean and green without any errors or warnings

@jongio for notification.

@AlexanderSehr I have updated based on your comments, please re-review.

@NanaXiong00
We have added examples for Bicep parameter files to the Readme. This has been applied to all published modules but needs to be done for PRs as well. Can you please run the Set-AVMModule utility as detailed here. It is required for the validation pipeline to succeed and the contribution to be published.
Please reach out if any support is needed.

@AlexanderSehr and @ReneHezser I have updated based on rename comments, please re-review.

@ReneHezser I have updated branch and run the Set-AVMModule utility, please review.


Language Pack Icon

Can we get an icon for language packs?

FYI @chryw. I'll work with you to get this new icon in the queue.

This is already updated on the marketplace, attaching here for reference.
Icon

Gallery view

Extension page

Market_LanguagePack_128x.zip


how to sort entries as AaBaCc , instead of ABCabc?

where to modify?

got it,ez……
just replace line 228 "items.sort(key=operator.itemgetter(0))" in writemdict.py
with:
items.sort(key=lambda l:l[0].lower())


Can't play audio from internal memory on IOS

When I pull an audio from firebase, it plays normally, it is the same audio I recorded, but when I try to play this audio when it is in the internal memory of the phone, the play does not work, but I get a log of the correct duration the sound and also says it’s loaded, but it doesn’t play, and after I try to play an audio from the internal memory, the ones that come from firebase don’t play anymore
the filename from memory(_filename: '/var/mobile/Containers/Data/Application/438A07E6-8D46-4C5B-9533-B0778A74989D/Documents/audio.aac',)
this.sound = new Sound(filepath, ``, (error) => {
    if (error) {
           this.setState({ playState: 'paused' });
    } else {
           global.alert.alert(`duration ${this.sound.getDuration()}`)
           this.setState({ playState: 'playing', duration: this.sound.getDuration(), durState: 'playing' });
           this.sound.play(this.playComplete);
    }
 });

Is your issue with...

[X] iOS
[ ] Android
[ ] Windows

Are you using...

[X] React Native CLI (e.g. react-native run-android)
[ ] Expo
[ ] Other: (please specify)

Which versions are you using?

React Native Sound: last
React Native:0.60.6
iOS:13.3
Android:
Windows:

Does the problem occur on...

[ ] Simulator
[X] Device

If your problem is happening on a device, which device?

Device: Iphone 6s

maybe this pr can help you

I really was not able to run the audio from the internal memory only on IOS using this plugin, so I made a workaround using the 'react-native-audio-toolkit' just to reproduce this type of audio, and for this to work I need to concatenate the prefix ' file: // 'before the IOS internal memory path


Fix breadcrumb hierarchy rendering issues

Problem Description:
The breadcrumb hierarchy is not rendering correctly when navigating through it.
Expected Behavior/Solution:
The breadcrumb hierarchy should render the correct hierarchy.
Requirements:

[x] Add a key property with the value of the current entity's id to all instances of the breadcrumb hierarchy component

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Wireframe/Mockup - Kam
[x] ~Committee discussions - Sarah~
[x] ~Feasibility/Team discussion - Sarah~
[x] ~Backend requirements - TBD~
[x] Frontend requirements - Kam
[ ] Are new regression tests required for QA - Amy
[x] ~Questions~

UAT/LUX Examples:

Go to Catocala | PRD Catacola
In its breadcrumb hierarchy, select Endopterygota
The breadcrumb hierarchy for Endopterygota should be correct

Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:

Bugherd: https://www.bugherd.com/projects/284041/tasks/2447 & https://www.bugherd.com/projects/284041/tasks/2448

Wireframe/Mockup:
Current:

Expected:

Looks good in prod. Closing.


Faster Index Building using a single-pass approach.

Only parsing the KnowledgeBase file once.

While parsing the file (nt/ttl/tsv) we write a Vector of temporary ids which correspond to the
order of appearance in the partial vocabulary.

Merging the partial vocabularies now creates a
mapping from temporary to global ids.

In a second pass, use this mapping to convert
temporary to global ids. This is much faster
than parsing the input file for a second time

in Addition, the parser is run in parallel (using std::async) during the first pass.
This gives us another speedup.

I have changed the requested places. I also ran end-to-end builds for Wikidata Truthy without any trouble.
The single passing part was also used for Wikidata Full, but there I had some issues with the permutations which were bugfixed here (STXXL with OpenMP can be made to compile, but behaves strangely etc.)


[Event Request] Page 9203 "Budget Matrix".LookUpCode

Please add new event
local procedure LookUpCode(DimType: Enum "G/L Budget Matrix Dimensions"; DimCode: Text[30]; "Code": Text[30])
var
    GLAcc: Record "G/L Account";
    BusUnit: Record "Business Unit";
    DimVal: Record "Dimension Value";
begin
    case DimType of
        DimType::"G/L Account":
            begin
                GLAcc.Get(Code);
                PAGE.RunModal(PAGE::"G/L Account List", GLAcc);
            end;
        DimType::Period:
            ;
        DimType::"Business Unit":
            begin
                BusUnit.Get(Code);
                PAGE.RunModal(PAGE::"Business Unit List", BusUnit);
            end;
        DimType::"Global Dimension 1", DimType::"Global Dimension 2",
        DimType::"Budget Dimension 1", DimType::"Budget Dimension 2",
        DimType::"Budget Dimension 3", DimType::"Budget Dimension 4":
            begin
                DimVal.SetRange("Dimension Code", DimCode);
                DimVal.Get(DimCode, Code);

                PAGE.RunModal(PAGE::"Dimension Value List", DimVal);
            end;
    end;

    //-------------------------------OnAfterLookUpCode:BEGIN
    OnAfterLookUpCode(DimType, DimCode, Code);
    //-------------------------------OnAfterLookUpCode:END
end;

[IntegrationEvent(false, false)]
local procedure OnAfterLookUpCode(DimType: Enum "G/L Budget Matrix Dimensions"; DimCode: Text[30]; FieldCode : Text[30])
begin
end

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Added question on general-cs-quiz

Summary of changes
I have added two new questions in general-cs-quiz.
Question 1:What is the acceptable range of Balance Factor for an AVL tree?
Question 2:What method copies the actual value of an argument into the formal parameter of the function?
Checklist

[x ] I have read and followed the contribution guidelines.
[ x] I have read through the Code of Conduct and agree to abide by the rules.
[ x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[ x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[ x] I have provided a summary of my changes.

closes #XXXXX

I have commited the changes as per suggestion. kindly review it.


call replaceState not pushState based on flag

This closes #7
We now call build_page(exhibit, true) to start the application in an "embedded" mode. In this mode, we never call history.pushState, only history.replaceState.

Updated to call
build_page(exhibit, {
  embedded: true
})

merged into #16


Return empty string mappings, so rollup autogenerates them

mappings as an empty string get processed into the mappings of the output code. Since I have no idea how to generate a source map to a GraphQL query, and it's probably more useful to see the generated js, adding this code in (and normalizing how the plugin resolves) is better than rollup complaining about no source map and screwing up upstream source maps

It's kinda weird, because there's no semantic to throw a debugger expression into graphql code, so you'd have to find the generated code and mark it in the browser as a breakpoint, but since graphql isn't really executed like sequentially written stanzas of code, it'd just get super weird to map between the two. This just allows for a source map to be generated for the js code, so I think it's ok?


Using extended styles with styled-components breaks types

Steps to reproduce
Link to live example: https://stackblitz.com/edit/vitejs-vite-afbuyz?file=src%2FApp.tsx&view=editor
Steps:

Use MUI with styled-components (https://mui.com/material-ui/integrations/styled-components)
Use extended styles with styled (https://styled-components.com/docs/basics#extending-styles)

Current behavior

No Intellisense is displayed.

No warning if the wrong property is assigned.

It should be "outlined"

Expected behavior
The types are correct even if extended styles are used.
Context

There is no problem using styled-components directly.
There is no problem with styled when using emotion.

The types change when using extended styles.
styled

extended

Your environment

npx @mui/envinfo
I used Chrome: 130.0.6723.70
  System:
    OS: Linux 5.0 undefined
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  Browsers:
    Chrome: Not Found
  npmPackages:
    @mui/core-downloads-tracker:  6.1.5
    @mui/material: latest => 6.1.5
    @mui/private-theming:  6.1.5
    @mui/styled-engine:  6.1.5
    @mui/styled-engine-sc: latest => 6.1.5
    @mui/system:  6.1.5
    @mui/types:  7.2.18
    @mui/utils:  6.1.5
    @types/react: ^18.3.11 => 18.3.12
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    styled-components: latest => 6.1.13
    typescript: ~5.6.2 => 5.6.3

tsc --showConfig
{
    "compilerOptions": {
        "paths": {
            "@mui/styled-engine": [
                "./node_modules/@mui/styled-engine-sc"
            ]
        },
        "target": "es5",
        "module": "esnext",
        "jsx": "react-jsx",
        "noEmit": true,
        "strict": true,
        "esModuleInterop": true,
        "forceConsistentCasingInFileNames": true,
        "lib": [
            "dom",
            "dom.iterable",
            "esnext"
        ],
        "allowSyntheticDefaultImports": true,
        "noFallthroughCasesInSwitch": true,
        "moduleResolution": "node10",
        "resolveJsonModule": true,
        "isolatedModules": true,
        "skipLibCheck": false,
        "preserveConstEnums": true,
        "noImplicitAny": true,
        "noImplicitThis": true,
        "strictNullChecks": true,
        "strictFunctionTypes": true,
        "strictBindCallApply": true,
        "strictPropertyInitialization": true,
        "strictBuiltinIteratorReturn": true,
        "alwaysStrict": true,
        "useUnknownInCatchVariables": true
    },
    "files": [
        "./src/App.tsx",
        "./src/main.tsx",
        "./src/vite-env.d.ts"
    ],
    "include": [
        "src/**/*"
    ]
}

Search keywords: styled-engine-sc styled-components TypeScript

I wonder if it is related to https://github.com/mui/material-ui/issues/44127 at all

I wonder if it is related to https://github.com/mui/material-ui/issues/44127 at all

It's not related, looks like a bug to me. I can take a look at this next week.


Add a v-version tag for golang module

When running the publish+release action, the changesets publish command will automatically create a github tag for each package within the monorepo. The format for this is<EMAIL_ADDRESS>Which arguably makes a lot of sense for monorepos, but because we also want to use the git tags for golang module package releases we need a git tag with the format vX.X.X.
This PR creates that additional v version tag manually whenever the changeset action has created another release tag.

Please note that the latest tagged version in the repo is now v1.11.0, while all automated tags were v1.10.x.  I think before merging it we should at adjust version numbers to match. Otherwise we'll have to do ugly tricks if it publishes current main as Go package version v1.10.x.

thanks for calling that out, that makes sense! I'll add a minor changeset to this PR so that the next release will be v1.11.0

But it must be either v1.12.0 or v1.11.1. If we retag v1.11.0 this will also be a mess. Go monitors all packages for changes. If hash of a previous release changes, it would error out.

I don't think it will retag with v1.11.0. It will just skip it for now as the tag is already present.

for reference: https://github.com/rickstaa/action-create-tag?tab=readme-ov-file#tag_exists_error


Problematic method overload in derived class (from JS)

Bug Report
🔎 Search Terms

jsdoc
overload
return type
inheritance

🕗 Version & Regression Information

This changed between versions 4.5 and 4.6

⏯ Playground Link
Playground link with relevant code
💻 Code
NOTE: This is JS, not TS.

export class Controller {
	constructor() {
	}

	/**
	 * @returns {this}
	 */
	updateDisplay() {
		return this;
	}
}

export class BooleanControllerNoExtraMember extends Controller {
	constructor() {
		super();
	}

	updateDisplay() {
		console.log('test');
		return this;
	}
}

export class BooleanControllerWithExtraMember extends Controller {
	constructor() {
		super();
		this.test = 5;
	}

	updateDisplay() {
		console.log('test');
		return this;
	}
}

🙁 Actual behavior
The resulting declaration file includes updateDisplay() in BooleanControllerWithExtraMember with a return type of BooleanControllerWithExtraMember. This is problematic and causes type errors because the return type for BooleanControllerWithExtraMember.updateDisplay() needs to be assignable to this. Duplicating the JSDoc to specify that it returns this is undesirable since we don't want to have to duplicate the JSDoc for all derived classes.
I included BooleanControllerNoExtraMember as well to highlight the inconsistency that it sometimes doesn't specify the method overload due to seemingly unrelated changes to the class.
export class Controller {
    /**
     * @returns {this}
     */
    updateDisplay(): this;
}
export class BooleanControllerNoExtraMember extends Controller {
}
export class BooleanControllerWithExtraMember extends Controller {
    test: number;
    updateDisplay(): BooleanControllerWithExtraMember;
}

🙂 Expected behavior
BooleanControllerWithExtraMember doesn't specify updateDisplay() because it doesn't need to. This is how TypeScript 4.5 behaves.
export class Controller {
    /**
     * @returns {this}
     */
    updateDisplay(): this;
}
export class BooleanControllerNoExtraMember extends Controller {
}
export class BooleanControllerWithExtraMember extends Controller {
    test: number;
}

The TypeScript example includes updateDisplay() for each class. Or am I wrong?
export declare class Controller {
    constructor();
    updateDisplay(): this;
}
export declare class BooleanControllerNoExtraMember extends Controller {
    constructor();
    updateDisplay(): this;
}
export declare class BooleanControllerWithExtraMember extends Controller {
    test: number;
    constructor();
    updateDisplay(): this;
}

This when creating type declarations from JavaScript (you can change language in the TSConfig > Lang option).

Here's a repro that's the same code in JS and TS, but generates different .d.ts files:
export class C {
    cdata = 2
    constructor() {
    }

    updateDisplay() {
        return this;
    }
}

export class B extends C {
    bdata = 1
    constructor() {
        super();
    }

    updateDisplay() {
        return this;
    }
}

export class D extends C {
    ddate = 3
    constructor() {
        super();
    }

    updateDisplay() {
        return this;
    }
}

In all 3 classes, updateDisplay: () => this but the generated d.ts file for JS has updateDisplay(): D (using D as an example).

Here's a repro for the overrride part of the bug (though this should perhaps be a separate bug):
export class C {
    updateDisplay() {
    }
}

export class D extends C {
    updateDisplay() {
    }
}

The generated d.ts for JS has export class D extends C {} whereas for TS, D includes updateDisplay(): void.

Filed #54061 to track the missing-identical-override bug


TileMap and Parallaxbackground don't work in HTML5

Godot version: 3.2
OS/device including version: Windows 10
Issue description: TileMap and ParallaxBackground nodes don't work in HTML5 version of the game. It seems these nodes don't exist in a level. However, in Windows version of the game, everything works well. It doesn't matter if I use GLES2 or GLES3. I've tested in Brave, Firefox and Edge
Steps to reproduce:

Start HTML5 from the editor
Or make a build and upload somewhere, e.g. www.itch.io

Minimal reproduction project:

Project on git
Fresh HTML5 build on itch.io

It's not loading the resources because in other platforms apart from Windows the path to the resource is case sensitive (webgl being one of them) and, for example, bg_layer1.png is inside res://assets/sprites/Background/bg_layer1.png but in your scenes it tries to load res://assets/sprites/background/bg_layer1.png (notice the Background folder case). Godot should have given you a warning about this at some point.

@mrcdk oh, it's started working, thank you! However, there were no warnings at all, as well as answers on the Internet. It's very hard to figure out what went wrong.

In this case, this is a duplicate of #24107. Thanks @mrcdk for the answer :slightly_smiling_face:


Go linter fix

Changelog

Fixes some Go Linting Errors
Adds a bit more testing

/label bug

Codecov Report

Merging #43 into main will decrease coverage by 2.20%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
- Coverage   81.21%   79.00%   -2.21%
==========================================
  Files           9       10       +1
  Lines         394      424      +30
==========================================
+ Hits          320      335      +15
- Misses         53       68      +15
  Partials       21       21

Flag
Coverage Δ

#unittests
79.00% <0.00%> (-2.21%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/animals/animals.go
83.33% <ø> (ø)

pkg/router/router.go
50.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

/merge


Get version from monorepo sub project's package.json.

How can i get version from monorepo sub project's package.json.
{
apps: {
A: {
...
packages.json
...
},
B: {
...
packages.json
...
},
}
}

I'm actually a bit surprised we don't already support this natively. Many of our badges already support this, including the ability to get a dependency version from a nested package.json manifest in a subdirectory of a monorepo.
e.g.
https://img.shields.io/github/package-json/dependency-version/metabolize/anafanafo/puppeteer?filename=packages%2Fchar-width-table-builder%2Fpackage.json

In the interim, your best bet is to use the Dynamic Json badge to point to the package.json file in source and use a simple jsonpath query to grab the version from the manifest.
Adding support for the ability to specify a path to the package.json file would be pretty straightforward for anyone interested in working on this, as we'd just need to incorporate the same filename query parameter on the GithubPackageJsonVersion class and route that already exists on the GithubPackageJsonDependencyVersion class and route
https://github.com/badges/shields/blob/master/services/github/github-package-json.service.js


[backport] Fix Travis with macOS

Backport of #6754

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 823f8beabdfc127e7e561e4ee74ea1821b31df2a, target branch v6) failed with status FAILURE.


icons test 2 pr with 250 limit

feat(assets): Asset Automation 2024-07-20T10:11:18.533Z

The original file is referenced here is https://github.com/momentum-design/momentum-design/pull/686


DatabasePracticeAssets

The above two files are provided by our college lecture of database management system that is DBMS. This is a demo record that can be used to practice the problems of database management system.

This is demo database that can be used to practice database quries.


Bootstrap

Create a bootstrap library

cant use bootstrap build to use because bootstrap build dosn't support oklch,.
just setup bootstrap library


Knife supermarket don't upload "test" directory

Description
Knife supermarket don't upload "test" directory to private supermarket, even removing it of the Chefignore file
ChefDK Version
0.17.17
Platform Version
MacOS 10.11 - El Captain
Replication Case
1- Create and craft a cookbook
2- upload it using knife supermarket share  -m
3- Download it using berks or manually
4- Test and spec dirs missing.
This affects some operations with Berkshelf (like running berkshelf under fresh Berksfile from a recently downloaded cookbook, if this cookbook have some fixtures, for example).
I know this is something done by design by Chef (and it's from the cookbook dev pattern, but it's something good to have available sometimes)
NOTE: CHEFDK BUGS ONLY

While I think this is desired behavior and you should be cloning from source control to get the full repo especially if you plan to upload to supermarket, chef-dk is not really the propper home for this issue since that command lives in chef.


Re-implementation of Task Workflow

The Task workflow was structured around a hierarchy of classes, starting with a base Task class, then a GitHubTask class inheriting from Task, and finally an AutomataTask class inheriting from GitHubTask.
The Task class was a generic task object, primarily characterized by attributes like task_id, priority, max_retries, status, and retry_count.
The GitHubTask class extended Task by including elements specifically designed for tasks that need to interact with a GitHub repository, like github_manager (now removed) and task_dir, and methods such as setup_task_env() and commit_task().
The AutomataTask class further extended GitHubTask to represent tasks to be executed by the AutomataAgent via the TaskExecutor. It introduced additional attributes like rel_py_path, agent, result, and error.
Finally, a TaskExecutor class was implemented for managing and executing tasks using different behaviors specified by the IExecuteBehavior interface.
Considerations for Re-implementation
When we re-implement the Task workflow, there are some crucial points we need to take from the previous implementation:

Class Hierarchy: The class hierarchy of Task, GitHubTask, and AutomataTask was a well-structured way of breaking down task complexities. We should retain this structure but ensure that each class and method is thoroughly documented and serves a clear purpose.
TaskExecutor: The TaskExecutor is a crucial component. It separates the execution logic from the task definition, providing flexibility in executing different types of tasks. When re-implementing, we need to consider whether the current design still serves our needs or if it requires adjustments.
Error Handling and Retries: The error handling and retrying mechanisms should be robust and clear. We need to ensure that the new implementation adequately handles task failures, with an appropriate retry policy and clear visibility into what caused the failure.
GitHub Interaction: The integration with GitHub was a unique feature. However, we need to ensure that the tasks are properly encapsulated, and interaction with GitHub should not leak into every aspect of the tasks. We might want to consider how best to isolate this functionality.

The logic for this can be seen here.
Requested Action
The goal of this issue is to reintroduce the Task workflow into our codebase, taking the positives from the previous implementation, addressing its weaknesses, and ensuring it suits our current and future needs. We encourage contributions to this effort and welcome discussion on the best ways to go about it.
As always, don't hesitate to ask if you have any questions or need further clarification. Your contributions to this project are highly valued!

The PR for this is here - https://github.com/emrgnt-cmplxty/Automata/pull/51


Disable Post button when empty

This in preparation for the threaded composer. It doesn't quite make sense to treat this as an error — we should just prevent you from posting, same as we do in other invalid cases (like too long post or missing ALT).
In the second commit, I'm also replacing ad-hoc grey disabled styling with our normal disabled button. We've already been using the disabled button for the case when you pressed post so let's use it here too.
Test Plan
Observe the initial state.

Verify that typing makes the button enabled.

Verify existing flows (adding image, filling alt, adding video, posting before it's uploaded) work like before.

Found a case where it's not disabled while empty - video errors

I think we should probably disable posting if there's an error in general? Empty or not. Clear/ack the error, then post.

Pushed.


Xcode12, 'ALUserService' has different definitions in different modules; first difference is definition in module 'Applozic.ALUserService' found return type is 'ALUserService *'

Goals

We use ApplozicSwift, the Applozic SDK.
An error occurs when building after Xcode12 update.
Error : " 'ALUserService' has different definitions in different modules; first difference is definition in module 'Applozic.ALUserService' found return type is 'ALUserService *' "
'ALUserService' Interface is declared in other Framework.
Built normally in Xcode 11.7.
Please check.
Expected Results

Build success.
Actual Results

Steps to Reproduce

Code Sample

Applozic SDK version: 7.9.1
ApplozicSwift SDK version: 5.10.0
Xcode version: 12.0
iOS version: All version
Dependency manager + version: Cocoapods 1.9.3+

@djlim0527 We are able to run the project in Xcode 12 this is the sample project we tried with above configration https://github.com/AppLozic/ApplozicSwift
Can you please share any sample project?

@Sunilkumarr sample project (https://github.com/djlim0527/ApplozicSwift)
Please check in the demo project.

Hello @djlim0527,
There is an ongoing issue regarding the same issue this in Developer Forums for Xcode 12 https://developer.apple.com/forums/thread/658012

@Sunilkumarr
I also checked the article on the developer forum.
Is this an Xcode12 bug? Are there any other solutions?

Ya, it looks like an Xcode 12 bug.
One way is until the Xcode bug is fixed you can point to the Applozic pod and ApplozicSwift pod spec.

Make sure to point to the master branch  in your forked repo   and change the Applozic version in pod spec file and commit it in your forked repo
complete.dependency 'Applozic', '~> 7.9.1'

Change it to 7.10.0 :
 complete.dependency 'Applozic', '~> 7.10.0'

In your pod file you can point to below Apploizc pod :
pod 'Applozic', :git => 'https://github.com/AppLozic/Applozic-Chat-iOS-Framework.git', :branch => 'xcode-12-rename'

You will have to rename the occurs of the class name ALUserService  to  ALApplozicUserService in the ApplozicSwift   https://github.com/AppLozic/ApplozicSwift and commit in your forked repo in the different branch it in your account.

Add this in your pod file to point pod spec
Change the git URL and branch name to  Point to your forked repo and branch

pod 'ApplozicSwift', :git => 'git-url-to-your-forked-repo', :branch => 'name-of-the-branch-where-you-have-commited-the-change-from-step-3'

Thank you for answering this issue.
Today I updated to Xcode 12.0.1 (12A7300) version and it was build success.
The Xcode bug seems to be fixed.
Thank you very much for your answer.


Fix OptiX + clang14 issue with duplicate symbols

We had been using clang/llvm 12 and when trying out 14 I started
getting test failures with OptiX compliaining about duplicate
symbols. They all seemed to be the things we declared as
OSL_CONSTANT_DATA. It looks like there's a difference in llvm 12 vs 14
in how the generated PTX marks its symbol visibility.
The solution (thanks to a clever suggestion by Alex Conty) was just to
enclose those declarations in anonymous namespaces. Works like a
charm!
Signed-off-by: Larry Gritz<EMAIL_ADDRESS>

static should have the same effect, don't know if it is being drop for a legitimate reason (bad device declaration) or a bug in the front/backend. Anyway I'm glad it helped.


legal: remove licenses of dependencies

Align with other Open Telemetry projects and remove the license texts of dependencies from this project.
Also remove vendor specific tooling to manage these third party licenses.

AFAIK we still need to abide by the CNCF allowed 3rd party license policy. I

Yes - this is without question. Following the CNCF policy for allowed 3rd party licenses should continue without change.
With https://github.com/open-telemetry/community/issues/2294 I have opened a request for guidance. At the moment the majority of OTel repositories does not store and provide the licence text for dependencies, like this project.