system probe error: failed to delete mountpoint from cache  unknown mount id

Describe what happened:
I've recently enabled sysprobe on an estate and get regular errors for files stating:
(pkg/security/probe/probe_bpf.go:343 in handleMountEvent) | failed to delete mount point 1394 from cache: unknown mount ID

Describe what you expected:
I would expect the mount event to be picked up and inserted into the cache, and no errors to occur when getting a umount event.
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc):
latest version 6.24.1

Did you ever get around to figuring this out? I'm running into the same issue and it's causing my system-probe container to restart hundreds of times due to OOMKills. I'm running datadog-agent version 7.25.0 and kube version 1.14.8.

Did you ever get around to figuring this out? I'm running into the same issue and it's causing my system-probe container to restart hundreds of times due to OOMKills. I'm running datadog-agent version 7.25.0 and kube version 1.14.8.

@cp-jennifer I didn't. I am presuming that either the cache doesn't have a file in it because it was there before datadog started and the cache isn't hydrated on startup, or the caching logic is flawed. I didn't have a chance to dig into the code and make a fix. I presumed it would get fixed in later versions as this feature is pretty beta. Instead, I am ignoring these errors and using the exporter.

@cp-jennifer I didn't. I am presuming that either the cache doesn't have a file in it because it was there before datadog started and the cache isn't hydrated on startup, or the caching logic is flawed. I didn't have a chance to dig into the code and make a fix. I presumed it would get fixed in later versions as this feature is pretty beta. Instead, I am ignoring these errors and using the exporter.

@william-salt-cko Gotcha, thanks for letting me know! FWIW, I tested the latest version of the agent (7.25.0) and although it solved my other system-probe issues (container restarting hundreds of times from OOMKills), this issue still remains. Hopefully, Datadog will have a fix for this soon.

@william-salt-cko Gotcha, thanks for letting me know! FWIW, I tested the latest version of the agent (7.25.0) and although it solved my other system-probe issues (container restarting hundreds of times from OOMKills), this issue still remains. Hopefully, Datadog will have a fix for this soon.

We changed the log level from Error to Warn in the 7.26 version. The log level was incorrect regarding the severity of this.

Closing it for now, feel free to re-open if you still see the error with more recent versions.


Update README usage Section

The usage output seems to have drifted and was causes confusion when
attempting to use as a reference.

Thanks for pointing it out and fixing! :+1:


Wrong documentation

fabOptions.setButtonsMenu requires context. It must be changed to (I can't send You pull request)::
fabOptions.setButtonsMenu(yourActivity.this, R.menu.your_fab_buttons);

Thanks for reporting, this will be correct in the next release (It should be available soon), thanks!

No problem:)


ci: Add health check for docker-compose minio

CI failed for minio start too slow, we should wait for it's startup: https://github.com/apache/incubator-opendal/actions/runs/5928223116/job/16073366018
mc: <ERROR> Unable to initialize new alias from the provided credentials. Server not initialized, please try again.
Error: Process completed with exit code 1.

@gongyisheng Would you be interested in helping with this?

@Xuanwo I just get up, do you think @oowl 's PR looks good? I can help if you need.

@Xuanwo I just get up, do you think @oowl 's PR looks good? I can help if you need.

Sorry, I took over this before you reply   😆


Allow walkthrough to re-open after opening a folder from a step

We've heard from extensions that they'd like to a step in their getting started to either open a folder or create a project. The downside with the walkthroughs right now is that opening a folder does not re-open the walkthrough where the user last left off. It would be great to have a flag to allow the walkthrough to re-open. A few examples of other extensions doing something similar:

This would be a huge value add for us over on the Azure extensions (specifically Static Web Apps). https://github.com/microsoft/vscode-azurestaticwebapps/issues/397

Here's a demo of how this could become a streamlined experience:
https://user-images.githubusercontent.com/35271042/142695638-b4e646c8-c6f2-4089-8b52-b9e2cd94ea24.mov

This seems to have worked before as it landed and was verified in #123525.

@digitarald  It's slightly different from #123525 .  In this issue, when you open a folder (e.g. which is not opened in vscode before) from walkthrough, the walkthrough will not open automatically, so users cannot resume and follow rest steps.
Demo in https://github.com/microsoft/vscode/issues/137544#issuecomment-974494107 is exactly the experience we want.
Technically, what I can imagine now include:

Option A. provide a command like workbench.action.files.openFolder accepting args like id of walkthrough to open.
Option B. For command workbench.action.files.openFolder, if it's triggered from a walkthrough step (but not the last step), it auto opens current walkthrough after opening the folder.
...

Hello folks, any update for this issue ? We are currently optimizing our walkthrough and this issue is a blocker in our overall walkthrough flow - Would be great if we can have an ETA of some sort :)
thanks!

@digitarald so is this issue targeting to be resolved by the January milestone?
TeamsFx team is also having the same trouble and would like to leverage this in GA scope if possible.

Checking with @JacksonKearl if it's on his radar. Afaik this is a regression as it worked before, so the scope shouldn't be a concern.

Added new API for telling vscode that after running a given command via getting started, a provided folder URI should be opened. VSCode core will handle opening the URI with the current walkthrough&step selected. Please LMK if this works for your use cases.
Sample: https://github.com/microsoft/vscode-extension-samples/blob/main/getting-started-sample/src/extension.ts#L28-L30

@alexweininger, @jaeyonglee8687, @nickzhums, etc. if possible it'd be helpful if you could text this new functionality in Insiders and verify that it suits your indented use cases.

@Eskibear would you mind doing a test of this?

I just tested the example provided in https://github.com/microsoft/vscode/issues/137544#issuecomment-1005282329 , and it works. However it simply hardcoded the target folder to open.
Our user case is to let users specify their Java project folder to open. But hopefully we can implement some logic with "open dialog" to let user specify the folder to open.

I simply tried below sample code, the API works well, and the walkthrough page is opened automatically.
But there's a small problem for us to tweak. From the demo you can find that, there is a re-rendering of walkthrough after we grant workspace trust. That's because some java extensions are activated, changing some context value, leading to the update of the steps.
  context.subscriptions.push(vscode.commands.registerCommand('java.pack.openFolder', async () => {
    const target = await vscode.window.showOpenDialog({
      canSelectFolders: true,
      canSelectFiles: false,
      canSelectMany: false,
    })
    return target && { openFolder: target[0] };
  }));

Demo:
https://user-images.githubusercontent.com/2351748/150911647-2dccbbf8-8e48-40f9-acb4-c8151f32a1b5.mp4

We need to reload the window upon granting trust, so there's no avoiding the re-render. I'm not exactly sure what you mean regarding the context keys, is the final displayed walkthough incorrect?

See 0:08 ~ 0:10 in my demo. There's no problem after granting trust, re-rendering of walkthrough. And the active step is still "explore your projects" at that moment.
For "explore your projects" step, we actually provide two different steps, depending on whether there's a valid Java project recognized by Java LS. So you'll see 1s after granting trust, the walkthrough refreshed and it changed to focus on the first step.
I guess that's as expected behavior. It just makes the workflow less smooth, but is not a blocking problem.

Before granting trust, it was focusing on java.showProjectExplorer.inactive. And after, the step is replaced by a different step java.showProjectExplorer (though same title), and I guess that's the reason why it's not focused.
{
            "id": "java.showProjectExplorer",
            "title": "Explore your projects",
            "description": "%walkthrough.java.projects%",
            "media": {
              "svg": "walkthrough/projects.svg",
              "altText": "Project Explorer"
            },
            "when": "java:projectManagerActivated && workspaceFolderCount > 0"
          },
          {
            "id": "java.showProjectExplorer.inactive",
            "title": "Explore your project",
            "description": "%walkthrough.java.projects.inactive%",
            "media": {
              "svg": "walkthrough/projects.svg",
              "altText": "Project Explorer"
            },
            "when": "!java:projectManagerActivated || workspaceFolderCount == 0"
          },

@JacksonKearl , I know this issue was closed, but I still got one question when I try to implement this cool feature. Can you help to address it.
In your shared example: https://github.com/microsoft/vscode-extension-samples/blob/4e9b69f212d4544f8ad933b473c84db87b34c78f/getting-started-sample/src/extension.ts#L28-L30
context.subscriptions.push(vscode.commands.registerCommand('getting-started-sample.viewSources', () => {
return { openFolder: vscode.Uri.joinPath(context.extensionUri, 'src') };
}));
it will open folder in same windows, is there any way to open folder in a new windows? Such as:
return { openFolder: vscode.Uri.joinPath(context.extensionUri, 'src'), forceNewWindow: true };


[KARAF-4107] Upgrade Json to version 20150729

Hi all,
This PR is related to:
https://issues.apache.org/jira/browse/KARAF-4107
Andrea

In order to verify the feature, we have to use 1.8.
As now master depends to Java8 (Karaf 4.1.x), I will do the change there.


lld 14.0.6: rebuild against libxml2 2.13

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_3cgvhahxhq/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:30: should_use_compilers: The recipe requires a compiler directly
clone/recipe/meta.yaml:41: missing_tests: No tests were found.
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f6q_5103lf/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:41: missing_tests: No tests were found.
clone/recipe/meta.yaml:30: should_use_compilers: The recipe requires a compiler directly
===== Final Report: =====
2 Errors and 0 Warnings were found

An error on win-64:
WARNING: failed to get package records, retrying.  exception was: Unsatisfiable dependencies for platform win-64: {MatchSpec("llvm-tools==14.0.6=h4157e71_2"), MatchSpec("llvmdev==14.0.6=h4157e71_2")}
untered problems while solving:

  - package llvmdev-14.0.6-h4157e71_2 requires llvm-tools 14.0.6 h4157e71_2, but none of the providers can be installed

Could not solve for environment specs

The following packages are incompatible

\u251c\u2500 libxml2 2.13.*  is requested and can be installed;

\u2514\u2500 llvmdev 14.0.6.*  is not installable because there are no viable options

   \u251c\u2500 llvmdev 14.0.6 would require

   \u2502  \u2514\u2500 llvm-tools [14.0.6 hbc40eef_0|14.0.6 hbc40eef_1], which requires

   \u2502     \u2514\u2500 libxml2 >=2.9.14,<2.10.0a0 , which conflicts with any installable versions previously reported;

   \u2514\u2500 llvmdev 14.0.6 would require

      \u2514\u2500 llvm-tools [14.0.6 h4157e71_2|14.0.6 h4157e71_3], which requires

         \u2514\u2500 libxml2 >=2.10.3,<2.11.0a0 , which conflicts with any installable versions previously reported.

We need to rebuild llvmdev 14.0.6 because its llvm-tools 14.0.6 requires libxml2


Sections restructuring

The current links can be organized in a better way
Solution:
A roadmap-style list from beginner to advanced

Would love to work on this. Please assign it to me.

done @yash251

hey! seems fun to work on! could I please be assigned to this issue ?

Currently working on it @issa-me-sush

Let me know if you need help with it!


re-sync

thanks a lot @alexrudy. All works as expected now when I build locally. I have some issue when trying to build on readthedocs, I will describe in a new ticket.


Single tech/databricks 145 iac basic

Purpose

Simple infrastructure templates for storage account, key vault and ADB workspace.
Script for creating/destroying the infrastructure.

Does this introduce a breaking change?

[ ] Yes
[x] No

Validation

create the following environment variables:
export DEPLOYMENT_PREFIX=<PREFIX FOR RESOURCE NAMES>
export AZURE_SUBSCRIPTION_ID=<SUBSCRIPTION ID TO USE>
export AZURE_RESOURCE_GROUP_NAME=<RG NAME>
export AZURE_RESOURCE_GROUP_LOCATION=eastus
export DELETE_RESOURCE_GRUP=false

cd Cluster_Deployment
./deploy.sh

cd Cluster_Deployment
./destroy.sh

Author pre-publish checklist:

[ ] Added test to prove my fix is effective or new feature works
[ ] No PII in logs
[ ] Made corresponding changes to the documentation

Issues Closed or Referenced

Closes #145

Documentation will come as part of story #160


Ensure that an OTP's issuer and label values are escaped correctly

Summary

This PR fixes/implements the following bugs/features:

[x] Creating an OTP with an issuer/label that contains a space or other restricted characters does not properly escape the issuer/label

What existing problem does the pull request solve?**

Currently, if you create an OTP with an issuer that contains a space, for example:
var oneTimePassword = new OneTimePassword {
	Issuer = "Google Google",
	Label =<EMAIL_ADDRESS>	Secret = "pwq6 5q55"
};

and then call ToString on that oneTimePassword, that will return:
otpauth://totp/Google Google:test@google.com?secret=pwq65q55&issuer=Google%20Google
(note the first "Google Google" is not escaped, like the second one in the issuer parameter)
which then looks like this in Google Authenticator after scanning the resulting QR code:

This PR resolves this issue by correctly escaping both instances of the issuer in the URL, which then appears correctly in Google Authenticator:
otpauth://totp/Google%20Google:test@google.com?secret=pwq65q55&issuer=Google%20Google
Test plan

Test cases have been added.
Closing issues

N/A

I discovered the same problem yesterday, thank you for the fix!

Thanks for this fix, it addresses issue #375.
I suggest also escaping the Label value, since an email address can contain / and ? characters.

Thanks for this fix, it addresses issue #375.
I suggest also escaping the Label value, since an email address can contain / and ? characters.

Thanks @tom-156842, done 👍

@codebude Do you any update on when this fix will be released?

All changes here look good.  Generated QR codes scan properly with Google Authenticator.  Tests have already been added :+1:


human-like figure detection and pose estimation model

I would like to use the dataset you provided to train the human body detection model and pose estimation model used in the code. Can you provide code for these two models？

Hello @LongJi12. The models were trained using the OpenMMLab framework. If you download the .mar files and unzip them, you will find the config files OpenMMLab uses to specify model architecture.

I have successfully extracted the. mar file and reviewed the relevant model content, but I still have difficulties during training. The downloaded dataset does not include the 2500 manually selected image materials mentioned in the paper and similar training materials_ Size-180000_ Dev.json, train_ Size-180000_ Can you provide ?
At 2023-10-13 00:21:50, "hjessmith" @.***> wrote:
Hello @LongJi12. The models were trained using the OpenMMLab framework. If you download the .mar files and unzip them, you will find the config files OpenMMLab uses to specify model architecture.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Let me look around for them. I no longer have access to the environment I used to train, so I'll have to look around for it. Are you attempting to compare against it as a baseline or benchmark?

Let me look around for them. I no longer have access to the environment I used to train, so I'll have to look around for it. Are you attempting to compare against it as a baseline or benchmark?

I want to use it as a benchmark for comparison

@hjessmith Did you manage to get these datasets used by the demo? I'm getting way worse outcomes using just dataset given in this repo.

After several unsuccessful searches, I've concluded that the list of 2500 manually selected images used to generate the smaller dataset didn't survive the environment transfer. I was able to find an incomplete list of the manually selected images, however, which I'll link here. Hopefully that can be of some use: https://drive.google.com/file/d/17fXv9NithNiFmmn_UmbMvWvJNZYL8zXv/view?usp=sharing


[Enhancement] Named snapshots

When working in a team it would be helpful to:

Intentionally create a snapshot in document history
Name that snapshot to ease identification

This would require an  Create Snapshot button and a "Rename Snapshot" Entry in the context menu of the snapshots.

Hi @Vinschni, it is a good idea, and Grist does internally have the ability to put labels on snapshots. All that is really missing is a UI for it.

Hello @paulfitz I have a requirement for this feature, too. I am trying to develop renamed snapshot myself. I got some point but I am trying to understand that is there a way how to update this metadata label on the model.

Hi @softwareguru90, you can set it while creating a snapshot, see: https://github.com/gristlabs/grist-core/blob/3e0045db4580f1bce49dec59afb8496024358b58/app/server/lib/ExternalStorage.ts#L28-L29. With existing code, that save happens in HostedStorageManager.ts, in the _pushToS3 method https://github.com/gristlabs/grist-core/blob/3e0045db4580f1bce49dec59afb8496024358b58/app/server/lib/HostedStorageManager.ts#L750. But that doesn't really help you. I can see how setting it after the snapshot already exists would be preferable. One way to go about it would be to add a method to ExternalStorage (and its implementations), and to DocSnapshotInventory, then an API endpoint to actually call them.

Hi @paulfitz. Thanks four your response.Snapshot section is quite complex. I am having trouble understanding exactly where to update the label field. Could you briefly explain the steps I need to follow?


Bug? There's an unexpected behaviour when reading frames sequentially.

Hello @RomanArzumanyan!
I might have found an issue with VALI, but there's also some chance that I'm just doing something totally wrong. When I read the attached video file with VALI, using the following code, I get a weird behaviour where the frames are read in an unexpected order (I get frame 0, 1, 0, 2). I'm attaching the output of the code below as well.
(Please note that the video starts until second 2... not sure if that's causing the issue).
from IPython.display import display

import PyNvCodec as nvc
import numpy as np

url = "/data/jose/test-video-overdub/example_6/bug-video.mp4"

class StopExecution(Exception):
    def _render_traceback_(self):
        return []

# GPU-accelerated decoder
pyDec = nvc.PyDecoder(
    url,
    {},
    gpu_id=0)

# GPU-accelerated converter
pyCvt = nvc.PySurfaceConverter(
    pyDec.Format(),
    nvc.PixelFormat.RGB,
    gpu_id=0)

# Colorspace conversion context. Here a dummy set of parameters is used
# just for illustration purposes.
cc_ctx = nvc.ColorspaceConversionContext(
    nvc.ColorSpace.BT_709,
    nvc.ColorRange.MPEG)

# GPU-accelerated Surface downloader
pyDwn = nvc.PySurfaceDownloader(gpu_id=0)

# Raw decoded Surface
surf_src = nvc.Surface.Make(
    format=pyDec.Format(),
    width=pyDec.Width(),
    height=pyDec.Height(),
    gpu_id=0)

# Raw Surface, converted to RGB
surf_dst = nvc.Surface.Make(
    format=nvc.PixelFormat.RGB,
    width=pyDec.Width(),
    height=pyDec.Height(),
    gpu_id=0)

# Numpy array which contains decoded RGB Surface
frame = np.ndarray(
    dtype=np.uint8,
    shape=surf_dst.HostSize())

def save_image_from_tensor(f, path):
    image = Image.fromarray(f)
    image.save(path)

for idx in range(4):
    # Decode single Surface
    success, details = pyDec.DecodeSingleSurface(surf_src)
    if not success:
        print(details)
        raise StopExecution

    # Convert tot RGB
    success, details = pyCvt.Run(surf_src, surf_dst, cc_ctx)
    if not success:
        print(details)
        raise StopExecution

    # Copy pixels to numpy ndarray
    if not pyDwn.Run(surf_dst, frame):
        print("Failed to download surface")
        raise StopExecution

    # Reshape to proper dimensions.
    # Some video formats like NV12 require to reshape to 'raw' dimensions.
    # Others like RGB24 require to reshape to 'final' dimensions. Hence this
    # feature isn't yet supported by VALI out of the box. Have to do that by
    # hand. Sic !
    res_frame = np.reshape(
        frame,
        (pyDec.Height(), pyDec.Width(), 3))

    # Display in notebook

    image_f = Image.fromarray(res_frame)
    image_f.save(f"raw{idx}.png")

https://github.com/user-attachments/assets/047729de-5f2c-446a-a125-b6e5539c1f18
Output files:

Hi @sotelo
I’ll take a look tomorrow and will come back as I find something.
Meanwhile I recommend you to decode this video with ffmpeg using cuvid decoder and see if this behaviour reproduces.

Thank you for the blazing fast response! I tried to decode it with VPF and it seems that that worked fine. Will also try with ffmpeg.

Jus to mention that I have the same issue (out of order first frames with VALI but not with vpf). Did not explore much more

@Yves33 @sotelo
Looks like I've found the culprit. Please check v.3.2.6.
After I changed CUDA stream used to memcpy ffmpeg frame to VALI to default CUDA stream, the issue no longer persists.
I've tested it locally on the video attached.


Added Github Action Workflow for Build.

We could move to Github Actions to handle Build and Release process for MicroProfile Config. Some of the main motivations to move are:

Run the build in forks. You don't need to do the PR to check the status of the build
Change the Build / Release configuration by just submitting a PR
Committers have control over the CI
Flexible to execute actions on Github Events

I've detailed some of the work done over SmallRye to use Github Actions here:
https://github.com/smallrye/smallrye-parent/wiki/SmallRye-Release-Process
The idea is not to pull the plug on Jenkins yet. We can run both in parallel. We can start with just the build part, which is easy to implement and go from there.

This requires https://github.com/eclipse/microprofile-jwt-auth/pull/171 for the JDK 11 build.

Hey @radcortez, I wonder if we should create out MP JWT specific forum and post this proposal there.
And give it a few weeks. I'll open an issue to do it anyway...
Right now I'd rather deal with it post 1.2 as there is still a lot of work to do for it so I'd be happy with the existing process for now.

Yes.
Actually, I plan to propose this as a wide process change to all MicroProfile projects.
Maybe this description was a little off. This is the final goal, but this PR is just for the Build part. I see no harm in adding it right now, and could help us catch some issues. For instance, when I broke the build with the TCK suite files move :)

@radcortez Was there a broken build in that PR ?

Hmm, I was naively assuming the PRs were triggering a build :-), but the only checks are signature checks :-). So the only way to catch the failure early before the merge is to build locally ?

I think there is a Jenkins server at Eclipse (isn't it how you do releases?), but the build result is not being reported to Github. With the GH Action we would get it for free, plus it also works on forks.
With, right now you need to build locally. It was my mistake, you should do that anyway and not rely that the project is going to report that for you, but still I think it is convenient.

@radcortez FYI, MP JWT 1.2 will be the 1st release I'll be doing. That Jenkins server does report the issues if any but after we merge the PRs, when we had a PR which was causing the build failure after I merged it, I got the notification.
So what we really want to is when someone opens a PR a CI is started and checks it immediately. GH Actions will give it to us, this is something I get :-), lets do it

Ah, so Jenkins is probably only setup to build on push to master and not on PR's.
Yes, this will build when someone opens a PR, so we get the feedback before merging :)


[feature req]parameter n support

Great lib, Thanks, Max!
Btw, I find it don't support parameter n:
https://github.com/minimaxir/simpleaichat/blob/main/simpleaichat/chatgpt.py#L111
https://platform.openai.com/docs/api-reference/chat/create#chat/create-n
n Defaults to 1
How many chat completion choices to generate for each input message.

This parameter can improve diversity and make it easier for users to observe multiple results at once, and I think this parameter is somewhat underestimated.
LLMs tend to answer questions in an expert tone, will be very easy to give a single authoritative answer, and this parameter adds variety, and it would be great if it had this parameter. But it's not clear how to add this feature so as not to break the existing structure...

This is probably a good idea to support at some point, however there are usability concerns with it, especially around conversation persistence.
However, since async sessions/calls allow both multiple conversations and handles multiple conversation persistence correctly, that's the more recommended workflow currently to handle it.

LLMs tend to answer questions in an expert tone, will be very easy to give a single authoritative answer, and this parameter adds variety, and it would be great if it had this parameter.

The intended way resolve that is through system prompt engineering, and with latest ChatGPT it does a good job of it.

That makes sense, thanks for your input.

however there are usability concerns with it, especially around conversation persistence.


🐛 AmbiguosMatchFound Exception

Describe the Bug
I am using AutoFixture to generate content for my protobuf responses.
Added ReadonlyCollectionPropertiesBehavior in order to generate RepeatedField data
Scenario
RepeatedField class has overloaded Add method which throws exception in AutoFixture.Kernel.InstanceMethodQuery
when executing the code:
public IEnumerable<IMethod> SelectMethods(Type type = default)
{
    var method = this.Owner.GetType().GetTypeInfo().GetMethod(this.MethodName);

    return method == null
        ? new IMethod[0]
        : new IMethod[] { new InstanceMethod(method, this.Owner) };
}

Expected Behavior
No Exception should be thrown.
Tasks

[ ] Updated all AutoFixture and related libraries
[ ] Confirmed in support forums if behavior is expected

More Information
I have already added a comment in the PR https://github.com/AutoFixture/AutoFixture/pull/1177
The fix that I am currently using is:
public IEnumerable<IMethod> SelectMethods()
{
    if(Owner == null) return Array.Empty<IMethod>();
    var methods = this.Owner.GetType().GetMethods();
    foreach (var methodInfo in methods)
    {
        if (methodInfo.Name == MethodName && methodInfo.GetParameters().Length == 1)
        {
            return new IMethod[]
            {
                new InstanceMethod(methodInfo, this.Owner)
            };
        }
    }

    return Array.Empty<IMethod>();
}

Would like to use it, but sadly SpecimentFactory.CreateMany requires a type and the method which does not is internal, so... have to wait :)
Screenshots
Thanks!

Duplicate of https://github.com/AutoFixture/AutoFixture/issues/1341


Removed goal type CPE from campaign and strategy

@jitendra-xoriant Can you review this PR and also run tests to make sure nothing breaks?


Change logo in title bar

I want to contribute in this issue. Please assign it to me.

I'll assign you this issue when the contribution period starts from 10th June, then you can start working on this issue.

Thank you!

Can you please tell that what should be the logo image after changing the default one?

@Khushi-sharma07 logo of this application is yet to be designed, see issue number https://github.com/QAZIMAAZARSHAD/Income-Tax-Calcultor/issues/7.
Wait till that issue gets soved.

Okay

@QAZIMAAZARSHAD can you assign this to me as well. I am interested in this

@QAZIMAAZARSHAD can you assign this to me as well. I am interested in this

@techabhi08 since this is a very basic issue I cannot assign it to more than one contributor.
Look for any other issues or open new issues.

ok

I will like to work on it please assign it to me

I will like to work on it please assign it to me

Already assigned to @Khushi-sharma07.

Now I think that "create the logo" pr is merged so I can also create the pr for this issue can you please tell me that which logo is finalised.

Actually I can see 3 pr merged for the issue.

Use this logo -> https://github.com/QAZIMAAZARSHAD/Income-Tax-Calcultor/blob/main/Logo/Income Tax calculator.png

Okay


BTRFS instructions possibly incomplete?

preface: I'm running linux-zen, if that changes anything
I have a BTRFS root partition and selected the BTRFS option at install time, I also have an empty subvolume at /snapshots.
I also tried symlinking /snapshots to /.snapshots (which is what snapper uses), but nothing changed. This is the output I get when I boot with any of the oroot options:
![booterror](https://cloud.githubusercontent.com/assets/8085052/21185313/101b4a00-c208-11e6-90e4-a4b50efc9e0b.png
(the btrfs thing before it only appeared once so far)
So, I'm not sure what I'm doing wrong, I can boot without issues if I leave the oroot option out, my fstab is correct and I have run mkinitcpio again just for safety.

closing because it may have been my own fault after all


Delete IndexedDbInterface; just use the class instead

Currently, when making updates to the IndexedDb class, we also have to make updates to IndexedDbInterface. This results in extra effort that doesn't seem to have any benefit: every place where IndexedDbInterface is used (except for this test suite) could just as easily use the class as its type instead.
This ticket is to delete the interface and just use the class.

there are many split class/interface definitions like this

I recall there was a potential issue with circular dependencies 🤔  and that the interface served as an indepedent dep. But perhaps this is no longer the case! Worth investigating.

@turbocrime:

there are many split class/interface definitions like this

Yeah, I've noticed that. I imagine that in some cases, it's to allow consumers to provide their own implementations but keep the same API contract. But in the case of IndexedDB, the interface is so tied to our own implementation that I can't imagine someone finding it useful.
@grod220:

I recall there was a potential issue with circular dependencies

Interesting... I'll look into that if/when we pull this ticket into a sprint!


Write log lines from Noso console to StdOut and/or log file

As a Noso node operator
I would like to have the log lines found in the Noso console also logged to StdOut and/or a log file
So that I can monitor the logs without needing to view the Noso GUI

I plan to run a Noso node (and eventually a master node) in a headless kubernetes cluster where I will not have access to the GUI. It would be very helpful if the log lines found in the Noso wallet console could also be directed to StdOut, and logged to a file.

Currently there is a file called /nosodata/errorlog.txt that stores all the log lines.


feat: add less loader and babel-import-plugin to support dynamic js and stylsheet imports for antd

Add babel-import-plugin and relevant setup on webpack for antd
Add less, less-loader and relevant setup in webpack to allow babel to parse antd component stylesheets.
Update package.json params


[Bug]Fork Application test is failing for a xhr call related to datasource

Intermittently when fork application is initiated
/api/v1/datasources?organizationId=* this call is returning 401

Closing since the problem was found to be in the test itself.


Could the output json include the parameters on modules?

Steps to reproduce the issue
module inner (i, o);
	input wire i;
	output wire o;

	parameter A = 1;
endmodule

module top (i, o);
	input wire i;
	output wire o;

	parameter A = 1;
	inner #(.A(A)) n (.i(i), .o(o));
endmodule

yosys -p "read_verilog test.v; chparam -list; write_json out.json"

Actual behavior
The chparam -list part will produce the following;
top:
  A
inner:
  A

Which I believe means that Yosys seems to understand that there are parameters associated with these modules. (BTW -- Any chance chparam -list could also include the default value?)
In the output JSON, the cell n will have;
      "cells": {
        "n": {
          "hide_name": 0,
          "type": "inner",
          "parameters": {
            "A": 1
          },
          "attributes": {
            "module_not_derived": 1,

Which I think means that Yosys understands that 1 value was used for the A parameter in the n cell.
However, there is no parameter property on modules output or any indication that the modules have parameters in any way.
Expected behavior
It would be nice if Yosys included a list of parameters (and even better if that list included the default values).
Version Info
Yosys 0.8+319 (git sha1 2c7e2541)

Due to the current architecture and flow of synthesis it doesn't seem possible to properly associate parameters with modules unfortunately.


Different images for different wears

Is it somehow possible to get an image for every possible wear? Currently every skin in skins.json only has one image.

hmm without scapping I don't thing so. The game files have 3 images per skin:

light
medium
heavy

This is the most I can try to do.
If this solutions is enough for you, you can take any skin image and change the substring _light_ for one of the words in the table.
{
    "id": "skin-65604",
    "name": "Desert Eagle | Urban DDPAT",
    "image": "https://raw.githubusercontent.com/ByMykel/counter-strike-image-tracker/main/static/panorama/images/econ/default_generated/weapon_deagle_aa_flames_light_png.png"
}

I have made some changes in skins_not_grouped.json to use also de medium and heavy image for skins.
You can check it live here

Is this selection of images approximate or exact?

hmm without scapping I don't thing so. The game files have 3 images per skin:
light	medium	heavy

This is the most I can try to do.
If this solutions is enough for you, you can take any skin image and change the substring _light_ for one of the words in the table.
{
    "id": "skin-65604",
    "name": "Desert Eagle | Urban DDPAT",
    "image": "https://raw.githubusercontent.com/ByMykel/counter-strike-image-tracker/main/static/panorama/images/econ/default_generated/weapon_deagle_aa_flames_light_png.png"
}

Thank you for the fast reply. Good to know that with the substring but its not quite what im looking for. Best thing would be something where I can put in a float and it gives me the appropriate image. Like the screenshot tools some marketplaces have. I would even build an API like that by myself but I dont know how to start.

hmm without scapping I don't thing so. The game files have 3 images per skin:
light	medium	heavy

This is the most I can try to do.
If this solutions is enough for you, you can take any skin image and change the substring _light_ for one of the words in the table.
{
    "id": "skin-65604",
    "name": "Desert Eagle | Urban DDPAT",
    "image": "https://raw.githubusercontent.com/ByMykel/counter-strike-image-tracker/main/static/panorama/images/econ/default_generated/weapon_deagle_aa_flames_light_png.png"
}

Thank you for the fast reply. Good to know that with the substring but its not quite what im looking for. Best thing would be something where I can put in a float and it gives me the appropriate image. Like the screenshot tools some marketplaces have. I would even build an API like that by myself but I dont know how to start.

ah got it. Yeah that is a little bit harder to do and I don't know how to do that. The only thing I know about screenshot tool for skins is this repo that I saw a time ago, maybe it can help you to start.

Is this selection of images approximate or exact?

I just set FN and MW to light, FT and WW to medium and BS to heavy. Not really sure if this is correct, let me know if you know the correct version.


wamr: Generate libc binding from NuttX

Summary
Bypass libc and other system calls into NuttX directly, similar to WAMR's builtin libc but cover more interface, must works with --bounds-checks=0 now, so it's more like  an alternative to ELF (with addition XIP support from WAMR).
Compared to ELF, this solution has better footprint (don't need to load entire ELF into RAM), and can take safety feature from Wasm in future (support boundary checks).
Impact
New feature
Testing
Vela

can take safety feature from Wasm in future (support boundary checks).

how?

can take safety feature from Wasm in future (support boundary checks).

how?

Just as WAMR's builtin libc does, do mapping or copy on need (only possible for partial interfaces ).

can take safety feature from Wasm in future (support boundary checks).

how?

Just as WAMR's builtin libc does, do mapping or copy on need (only possible for partial interfaces ).

are you going to write wrappers on many of API functions manually?

can take safety feature from Wasm in future (support boundary checks).

how?

Just as WAMR's builtin libc does, do mapping or copy on need (only possible for partial interfaces ).

are you going to write wrappers on many of API functions manually?

I prefer to do it by script except some corner case if possible.

https://github.com/arjunr2/WALI


Item - Sapros The Corrupter - Wrong Statistics

Hello o/
The following are wrong:

180 Reduced Resistances over 3.0 Seconds
180 Reduced Armor over 3.0 Seconds

They should be both

60 Reduced ... over 3.0 Seconds

TQVault
https://cdn.discordapp.com/attachments/347282491192639489/900775994670063686/unknown.png
ArtManager
https://cdn.discordapp.com/attachments/672458358673899541/900778031969349712/unknown.png
https://cdn.discordapp.com/attachments/672458358673899541/900778084519776346/unknown.png
Wagi

This is the same as #222


Remove old stuff

Refs https://github.com/AliSoftware/SwiftGen/issues/244

colors:

default: rename to swift2
swift3: no changes
rawvalues: update to swift 3 syntax, rename to swift3-rawvalues

fonts:

default: rename to swift2
swift3: no changes

images:

default: delete, deprecated by dot-syntax
dot-syntax-swift3: rename to swift3
dot-syntax: rename to swift2
structured: delete, deprecated by dot-syntax
swift3: delete, deprecated by dot-syntax
all-values: add the all values option to both options?

storyboards:

default: rename to swift2
swift3: no changes
osx-default: rename to osx-swift2
osx-swift3: no changes
lowercase: update to swift 3 syntax, rename to swift3-lowercase
uppercase: update to swift 3 syntax, rename to swift3-uppercase
osx-lowercase: update to swift 3 syntax, rename to osx-swift3-lowercase

strings:

default: delete, deprecated by dot-syntax
dot-syntax-swift3: rename to swift3
dot-syntax: rename to swift2
genstrings: no idea
no-comments-swift3: add as parameter option to other templates
structured: delete, deprecated by dot-syntax
swift3: delete, deprecated by dot-syntax

To avoid this rename dance in the future, each template will explicitly name the swift version it's for.

Should we also remove the logic of falling back to a default name in the CLI (in Commander's config)?
Or should we keep it falling back to -t default, even if we won't embed any template named "default.stencil in SwiftGen itself, so that people could still use a default template in their Application Support directory?

As this will be for 5.0 and thus a breaking change, I'd say remove the default behaviour. Because once swift 4 is made the default, people will expect that to be the default, and we might not be able to quickly release a version that supports that.

While documenting the templates, I was wondering what the use case is for the colors-rawvalue template? It's not like it adds much, the default template already provides an rgbaValue property.

It's historical, was the first template for colors (before someone pointed out that it wouldn't allow multiple color names having same value). We might as well remove it indeed as it doesn't add any real value

As we decided to keep the flat strings template, I think it'd be better if we have structured-swift2/3 and flat-swift2/3 templates. Structured in this case being the current dot-syntax templates. I've already applied this in the PR if you want to check it out.

Side note: maybe we should start a MigrationGuide.md, and enrich it on every PR removing old stuff. Like for this PR we could have a paragraph "old name / new name" for the templates so that people know what to replace their -t parameter with. Or do that doc in the Wiki, but don't forget to update it every time a breaking PR is merged.

Had the same thought. Will see about making one for this to get started.


[BUG]: failed to solve: process "/bin/bash -c source activate base     && conda install setuptools==70.0.0" did not complete successfully: exit code: 1

Version
main branch
Which installation method(s) does this occur on?
Docker
Describe the bug.
Hello , I am trying to use nv-ingest for extracting PDF data (images, tables and charts). I am following the instructions in the README file for installing docker, but when I try to run the command docker compose build , I face the following issue failed to solve: process "/bin/bash -c source activate base     && conda install setuptools==70.0.0" did not complete successfully: exit code: 1
Please see attached logs for more information.
Minimum reproducible example
No response
Relevant log output
[+] Building 15.8s (31/36)
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 5.27kB                                                                                0.0s
=> [internal] load metadata for nvcr.io/nvidia/cuda:12.2.2-base-ubuntu22.04                                                                                1.6s
=> [auth] nvidia/cuda:pull token for nvcr.io                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 26.82kB                                                                                0.0s
=> [base  1/11] FROM nvcr.io/nvidia/cuda:12.2.2-base-ubuntu22.04@sha256:1a8a738e81d4adbef0c709241f5238cec5bb77186dcb5b2103db293315ed42d1                                                                                0.0s
=> CACHED [base  2/11] RUN apt-get update && apt-get install -y       wget       bzip2       ca-certificates       curl     && apt-get clean                                                                                0.0s
=> CACHED [base  3/11] RUN wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O /tmp/miniconda.sh     && bash /tmp/miniconda.sh -b -p /opt/conda     && rm /tmp/miniconda.sh                                          0.0s
=> CACHED [base  4/11] RUN conda install -y mamba -n base -c conda-forge                                                                                0.0s
=> CACHED [base  5/11] RUN conda create -y --name nv_ingest python=3.10.15                                                                                0.0s
=> CACHED [base  6/11] RUN echo "source activate nv_ingest" >> ~/.bashrc                                                                                0.0s
=> CACHED [base  7/11] RUN source activate nv_ingest     && mamba install -y -c conda-forge tini                                                                                0.0s
=> CACHED [base  8/11] RUN source activate nv_ingest     && mamba install -y      nvidia/label/dev::morpheus-core      nvidia/label/dev::morpheus-llm      -c rapidsai -c pytorch -c nvidia -c conda-forge                                     0.0s
=> CACHED [base  9/11] RUN apt-get update && apt-get install -y     libgl1-mesa-glx     && apt-get clean                                                                                0.0s
=> CACHED [base 10/11] WORKDIR /workspace                                                                                0.0s
=> CACHED [base 11/11] COPY ./docker/scripts/entrypoint.sh /workspace/docker/entrypoint.sh                                                                                0.0s
=> CACHED [nv_ingest_install  1/17] COPY setup.py setup.py                                                                                0.0s
=> CACHED [nv_ingest_install  2/17] COPY ci ci                                                                                0.0s
=> CACHED [nv_ingest_install  3/17] COPY requirements.txt extra-requirements.txt test-requirements.txt util-requirements.txt ./                                                                                0.0s
=> CACHED [nv_ingest_install  4/17] RUN if [ -z "" ]; then     export VERSION="$(date +'%Y.%m.%d')";     fi;     if [ "dev" = "dev" ]; then     export NV_INGEST_VERSION_OVERRIDE=".dev0";     elif [ "dev" = "release" ]; then     export NV  0.0s
=> CACHED [nv_ingest_install  5/17] RUN source activate nv_ingest     && pip install -r requirements.txt                                                                                0.0s
=> CACHED [nv_ingest_install  6/17] COPY tests tests                                                                                0.0s
=> CACHED [nv_ingest_install  7/17] COPY data data                                                                                0.0s
=> CACHED [nv_ingest_install  8/17] COPY client client                                                                                0.0s
=> CACHED [nv_ingest_install  9/17] COPY src/nv_ingest src/nv_ingest                                                                                0.0s
=> CACHED [nv_ingest_install 10/17] RUN rm -rf ./src/nv_ingest/dist ./client/dist                                                                                0.0s
=> CACHED [nv_ingest_install 11/17] RUN source activate nv_ingest     && pip install -e client     && pip install -r extra-requirements.txt                                                                                0.0s
=> CACHED [nv_ingest_install 12/17] RUN chmod +x ./ci/scripts/build_pip_packages.sh     && ./ci/scripts/build_pip_packages.sh --type dev --lib client     && ./ci/scripts/build_pip_packages.sh --type dev --lib service                       0.0s
=> CACHED [nv_ingest_install 13/17] RUN source activate nv_ingest     && pip install ./dist/*.whl                                                                                0.0s
=> CACHED [nv_ingest_install 14/17] RUN source activate nv_ingest     && rm -rf src requirements.txt test-requirements.txt util-requirements.txt                                                                                0.0s
=> ERROR [nv_ingest_install 15/17] RUN source activate base     && conda install setuptools==70.0.0                                                                                14.1s

[nv_ingest_install 15/17] RUN source activate base     && conda install setuptools==70.0.0:
#0 0.928 /opt/conda/lib/python3.12/site-packages/conda/base/context.py:198: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.3.
#0 0.928
#0 0.928 To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels:
#0 0.928
#0 0.928   conda config --add channels defaults
#0 0.928
#0 0.928 For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html
#0 0.928
#0 0.928   deprecated.topic(
#0 1.270 /opt/conda/lib/python3.12/site-packages/conda/base/context.py:198: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.3.
#0 1.270
#0 1.270 To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels:
#0 1.270
#0 1.270   conda config --add channels defaults
#0 1.270
#0 1.270 For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html
#0 1.270
#0 1.270   deprecated.topic(
#0 6.289 Channels:
#0 6.289  - defaults
#0 6.289 Platform: linux-64
#0 6.289 Collecting package metadata (repodata.json): ...working... done
#0 13.78 Solving environment: ...working... failed
#0 13.94
#0 13.94 PackagesNotFoundError: The following packages are not available from current channels:
#0 13.94
#0 13.94   - setuptools==70.0.0
#0 13.94
#0 13.94 Current channels:
#0 13.94
#0 13.94   - defaults
#0 13.94
#0 13.94 To search for alternate channels that may provide the conda package you're
#0 13.94 looking for, navigate to
#0 13.94
#0 13.94     https://anaconda.org
#0 13.94
#0 13.94 and use the search bar at the top of the page.
#0 13.94
#0 13.94

failed to solve: process "/bin/bash -c source activate base     && conda install setuptools==70.0.0" did not complete successfully: exit code: 1
Other/Misc.
No response

Due to anaconda licensing issues, NVIDIA can no longer pull from the anaconda defaults channel

Solution:

Update the dockerfile to define the conda-forge channel (update the dockerfile's line 122 to && conda install -c conda-forge setuptools==70.0.0)

This is fixed, should have been closed by a previous pr.


Add URL validation for image upload by URL input

Version
Write the version that you are currently using.
@toast-ui/vue-editor: 3.2.3
Development Environment
Write the browser type, OS and so on.
Mas OS Sonoma14.0
Current Behavior
When we add image by URL input, it's fine to add image by URL such as "https" or "http". However, we can add an image by this URL input with data URL format such as data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAB3oAAAK1CAYAAAAuQ+8vAAABX2lDQ1...

This is unexpected action but this URL input not covered by addImageBlobHook so it's difficult to validate it.
Expected Behavior
Write a description of the future action.
I propose this URL input validation by "https" and "http" to filter unexpected embedding dataURI.
It's not difficult and it's probably more secure.

Although I fixed this issue in my local and I tried to push, it occured below error. Do I need to have any permission to push and create a PR for this repository?
Permission to nhn/tui.editor.git denied to aujourdui. fatal: unable to access 'https://github.com/nhn/tui.editor.git/': The requested URL returned error: 403


cleanup is_federated check in django_irods view function

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case
This is cleanup work to address issue #3562.

@sblack-usu @alvacouch I requested code review from both of you to address the issue #3562 of cleaning up django_irods view download method since you both have worked on this method which has become more and more complicated over time. @alvacouch I removed the download code from mounted iRODS user zone vault via nginx directly since all resources are now stored in data zone and there is no need to move resources from data zone to user zone since both zones are calculated in storage quota. When third party federated iRODS zone use case potentially came into existence in HydroShare, we could revisit our code base to add support for this as needed.

@sblack-usu @alvacouch This PR has been sitting there for review for a while.

I'm looking at this today @hyi, sorry I didn't get to it earlier.

@sblack-usu @pkdash I have done some further cleanup to address your comments. See if everything looks good now.


Campaign does not advance an act after completing an investigation

Bug: the campaign doesn't advance if there's an investigation is complete

Turns out it was a bad highlander build on my end. The code:       class'XComGameState_Investigation'.static.StartInvestigation(NewGameState, InvestigationTemplate, Settings.bTutorialEnabled ? 0 : 1);inXComGameStateContext_NewCampaignSetup` was edited to only start at the zeroth act, which would end up deadlocking the campaign when incrementing the act to 1 instead of 2.


[Documentation] Update button component documentation

I think we need to improve the descriptions e.g. link to certain files (like svg icon, theme colors), i also think we should add 'default' column and list default values of the non-required props.

display description -> you might want to change the display value when using linkTo prop
add description to severity prop
children -> contents inside button element, it should be plain text


Possible to extend to data vault 2.0 with Spark and/or BigQuery as target?

Seems like I am the first one to post an issue here :smile:. Very interested in diepvries, looking into it for one of my Dutch clients. We are considering the data vault 2.0 pattern for the datalake.
As described in this article there are a couple of issues that need solving for using data vault for datalake technologies like Databricks/Delta Lake or Google BigQuery. Most fundamental one is limited or non-existent functionality for constraints and foreign keys.
The article proposes to use deterministic hashkeys, which I can see working. So my question is, do you think it is doable to extend diepvries such that it can generate DDL for the target schema of the Raw Vault (that's our current scope, so not full DV2.0) for different target engines, most notably Databricks / Delta Lake and BigQuery.
Any suggestions are welcome, and if this is a workable solution we would be willing and able to contribute to diepvries.

Hey @dkapitan, thanks for your interest in diepvries!
Correct me if I'm wrong, but what you'd like to have is the ability for diepvries to generate SQL loading statement for other dialects than Snowflake, e.g. BigQuery and Databricks? Do you also have other architectural changes in mind, e.g. some structures in the raw vault that can't be loaded by diepvries?
To keep you up-to-date with our vision for the future of this framework, we are currently experimenting with using SQLalchemy for all generated SQL statements, in order to have other SQL dialects. Using SQLalchemy doesn't automatically solve all problems, as some SQL statements can differ between dialects and are not always 100% supported (e.g. MERGE statements), but we believe it would be a good first step in that direction.
Once we're there, generating DDL statements (on top of DML statements for loading data) for target structures should be possible, as SQLalchemy allows that.

Hi @matthieucan, thanks for your response. Regarding your questions:

Correct me if I'm wrong, but what you'd like to have is the ability for diepvries to generate SQL loading statement for other dialects than Snowflake, e.g. BigQuery and Databricks?

That is indeed what I am looking for.

Do you also have other architectural changes in mind, e.g. some structures in the raw vault that can't be loaded by diepvries?

For now, I just want to follow along with diepvries's existing architecture. As far as I understand it follows the current Data Vault 2.0 specification. Once we have a generic SQL back-end interface, we can start thinking about other features.
Going with SQL Alchemy makes perfect sense to me. Please let me know if there is any way I could help. For example, generating an overview with the key differences between dialects seems useful for refining our needs. I have worked a lot with BigQuery, and getting into Apache Spark more and more, so I could help with those.

Correct me if I'm wrong, but what you'd like to have is the ability for diepvries to generate SQL loading statement for other dialects than Snowflake, e.g. BigQuery and Databricks?

That is indeed what I am looking for.

Understood!

Going with SQL Alchemy makes perfect sense to me. Please let me know if there is any way I could help. For example, generating an overview with the key differences between dialects seems useful for refining our needs. I have worked a lot with BigQuery, and getting into Apache Spark more and more, so I could help with those.

While we can't commit to any timeline for this implementation, you might get inspired by this file in a proof-of-concept branch: https://github.com/PicnicSupermarket/diepvries/blob/matthieucan/sqlalchemy/src/diepvries/test_sqlalchemy.py
We intend to implement this for Snowflake as a first step. I think playing with those queries to estimate the efforts to make them compatible with BigQuery and Spark will be very valuable!

Hello all one question how is the porting to SQL Alchemy - I wanted to test it PostgreSQL database.

Hello all one question how is the porting to SQL Alchemy - I wanted to test it PostgreSQL database.

Hi, unfortunately this has not been implemented


Add Authentication Support for Dagster Pipeline Ingest

Thank you @NiharDoshi99  for adding Dagster support through the GraphQL endpoint!
This issue is a follow on for auth support, which is being driven by a mutual prospect.
Is your feature request related to a problem? Please describe.
The current dagster ingest only accepts a HostPort which is insufficient for accessing the GraphQL endpoint in Dagster Cloud which requires an API token.
Code: https://github.com/open-metadata/OpenMetadata/blob/cbcb910f06541876e3964e0aa59b73e19f89b27c/ingestion/src/metadata/utils/connections.py#L952-L967
FWIW the Dagster integration docs suggest this idea was considered but not implemented, as they refer to an API token.
https://github.com/open-metadata/OpenMetadata/blob/3d3dcff910301bd3a4a6eea50dcc510f2f75103f/openmetadata-docs/content/connectors/pipeline/dagster/index.md?plain=1#L138-L139
Describe the solution you'd like
Adding an optional parameter for an API key then using it as:
client = DagsterGraphQLClient(url, transport=RequestsHTTPTransport(url=url+"/graphql", headers={"Dagster-Cloud-Api-Token": token}))

Ref: https://github.com/dagster-io/dagster/discussions/7772
Describe alternatives you've considered
We could add a Dagster Cloud specific connector, but this adds a lot of duplication in what could be an optional parameter.

Hi @slopp , already working on integrating dagster with cloud and local just by changing dagster.yaml file .
Please find the issue for the same #7934

Awesome @NiharDoshi99  thanks!

this is already working / the issue can be closed


rework transaction EffectHash

Closes #2808
Stacked PR on #2931 which should be reviewed and merged first, then this will be rebased onto main
Adds a section of documentation on transaction signing which describe the changes made in this PR

CI is failing here due to unrelated proto changes, but this is ready for review


feat: Enable testResultsProcessor to be async

Summary
Fixes https://github.com/facebook/jest/issues/11683

Test plan
Added test

https://github.com/facebook/jest/releases/tag/v29.2.0


Removed terminology of Dead Letter Queue

Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>Across our codebase, we use quite often the term dead letter queue, while the correct term should be dead letter sink, because we don't send specifically to a queue but to a generic sink. This creates some confusion also in the logs, eg https://github.com/knative-sandbox/eventing-kafka-broker/issues/1011#issuecomment-863288386

Proposed Changes

:broom: Cleanup the term dead letter queue and use instead DLS or dead letter sink. No changes except aesthetics

Looks good!
NIT: perhaps we should skip all DLS mentions on method names? And instead have all (even the test ones) be like: doSomethingDeadLetterSink ?

NIT: perhaps we should skip all DLS mentions on method names? And instead have all (even the test ones) be like: doSomethingDeadLetterSink ?

Yeah I was wondering the same, let me do that


Reserved ip

Adds support for assigning/unassigning reserved IP with annotation: kubernetes.civo.com/ipv4-address

LGTM


NodePort 只有pod 所在的物理机节点能通，其他节点不通。sealer 部署的k8s 1.22.15版本

What happen?
svc 的流量策略都是：Cluster 模式
externalTrafficPolicy: Cluster
internalTrafficPolicy: Cluster
请求pod 所在的物理机，返回200
[root@master1 test]# curl -iv <IP_ADDRESS>:30013

About to connect() to <IP_ADDRESS> port 30013 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 30013 (#0)

GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: <IP_ADDRESS>:30013
Accept: /

< HTTP/1.1 200 OK
HTTP/1.1 200 OK
其他节点没响应
[root@master1 test]# curl <IP_ADDRESS>:30013
curl: (7) Failed connect to <IP_ADDRESS>:30013; Connection timed out
Relevant log output?
No response
What you expected to happen?
No response
How to reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
No response
What is the version of Sealer you using?
sealer 0.9
No response
What is your OS environment?
centos 7.9
What is the Kernel version?
No response
Other environment you want to tell us?

Cloud provider or hardware configuration:
Install tools:
Others:

这和sealos有关系嘛👀
检查一下 Kubernetes 的 service 信息。
在其他节点上用 nc -zv master1 30013 校验一下。不可用的话可能是防火墙的原因，或者是网络配置原因

防火墙sealer 部署的时候会设置关闭的，看过防火墙，都没有启用

把pod 调度到别的节点，别的节点的ip + NodePort 端口就能访问了，不知道为啥，没有思路，这样的话应该可以排除节点之间的防火墙问题的

@710210668 Can you show the contents of this file? /var/lib/sealer/data/my-cluster/rootfs/applications/custom-resources.yaml

改成ipip可以了，谢谢

This issue has been resolved i will close it.


Check for Play Services availability (android)

Check game services availability to be able to show the user a propper error dialog and also be able to handle when is not available from the code.
https://developers.google.com/android/guides/setup#add_google_play_services_to_your_project

@kafeg I've tackled some of the bugs, wait for the pull request.


"NotExecuted" is counted as a failed test in the "ALL Failed Tests" section

"NotExecuted" is counted as a failed test in the "ALL Failed Tests" section
so Test run outcome is considered "failed" if one test is labeled as "NotExecuted"
"NotExecuted" is an Ignored/skipped test.

yup. getting the same issue.


chapter 11 freeze,can't play the AVMutableComposition!

I selected 3 videos in Chapter 11/FifteenSeconds_Final,when run the app,and select 3 videos in app,the pointer show at the end,and THPlayerViewController show nothing!

Yes, I found that problem, too. Have you solved it yet ?

我是一个废物


Polish translation

I have a question, I need to translate something into Polish, because e.g. in Krarilotus-aggressiveAI (AIC) there is no Polish translation, I will gladly complement it or something as it used to be. :)

The aic's are contributed content, so they are handled by their respective creators. If you would like to add a translation, you can feel free to send the translated text to the creator on the ucp discord, or create a pull request with the translated text included.
I think lolasik is translating for the main patcher, but I'm sure he'd appreciate assistance when we start asking for translations before the next release, whenever that might be.

if any, I am available. I am not asking because some (AIC) lack Polish description. Therefore, in case of what, I can also help in translating :)

Whut? Thats news to me. Where is the polish translation missing exactly?
In the patcher the description is showing, so i am not sure what you are refering to?


[FX-4853] Add major-dependency-update-jira-label parameter

FX-4853
Description
This pull request adds major-dependency-update-jira-label parameter to notify-jira-about-contribution action, so the label that is added to created Jira ticket can be configured for dependabot major updates.
https://toptal-core.atlassian.net/jira/software/c/projects/FX/settings/automate#/rule/3021227/403457150 automation was updated to take label into account

How to test

check out https://toptal-core.atlassian.net/browse/FX-4920 (result of https://github.com/toptal/staff-portal/pull/11734), it has ready-for-refinement label and it was not moved in To Do automatically due to changes in automation

Development checks

[x] Add changeset according to guidelines (if needed)

PR commands

List of available commands:

@toptal-anvil ping reviewers - Ping FX team for review

@toptal-anvil ping reviewers


Cookie example for unauthenticated use?

Before submitting an issue, make sure you have:

[x] Updated to the lastest version v1.6.0
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones
[x] Reviewed the sample code in tests and examples

Which client are you using?

[ ] app (instagram_private_api/)
[x] web (instagram_web_api/)

Describe your Question/Issue:
I'm trying to save and reuse cookies for non authenticated sessions.
After reading and using the examples for an authenticated session, and also noticing that the example requires login details, I'm confused about how to do it without login details.
FYI, I'm not familiar with how to use cookies at all for anything else.

Have you found solution?


LSP workspace folder

Hi @David-Kunz ,
Would you be interested into adding  the workspace folder automatically by adding lsp dependency to the package ? I was struggling to setup up the path correctly for running the commands while now lsp can get the workspace folder automatically.
I have the code ready on my local copy just wondering if you are intersted into adding it into yours

Hi @izifortune ,
Thanks a lot for this suggestion, I'd be happy to look into your code.
Where is the workspace used? Wouldn't npx jest automatically determine the right path?
Best regards,
David


Update .travis.yml

Use travis's new container-based infrastructure for better performance.

I think they've changed their approach now. You run container based by default unless you explicitly say
sudo: required

Oops, update it later.

Packers and Movers India

Thanks for Nice and Informative Post. This article is really contains lot more information about This Topic.  -
Packers and Movers Chennai
Packers and Movers Hyderabad
Packers and Movers Mumbai
Packers and Movers Noida

This article is really fantastic and thanks for sharing the valuable post.
Packers and Movers Pune
Packers and Movers Bangalore
Packers and Movers Delhi
Packers and Movers Gurgaon

Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write
Packers and Movers Faridabad
Packers and Movers Thane
Packers and Movers Navi Mumbai
Packers and Movers Ghaziabad

Thanks for post this helpful post - Please visit for More information about -
Packers and Movers Gurgaon
Packers and Movers Bangalore
Packers and Movers Hyderabad
Packers and Movers Pune

@Munter any reference?
These doc only show that we should use sudo: false to use the new infrastructure, and the default is legacy.
http://docs.travis-ci.com/user/migrating-from-legacy/
http://docs.travis-ci.com/user/workers/container-based-infrastructure/
http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments

Judging by recent builds (e.g. https://travis-ci.org/auchenberg/volkswagen/jobs/84349911), travis uses the container based infrastructure by default
$ git clone --depth=50 --branch=v1.3.1 https://github.com/auchenberg/volkswagen.git auchenberg/volkswagen
This job is running on container-based infrastructure, which does not allow use of 'sudo', setuid and setguid executables.

Yeah it's a little weird - some of my jobs does use the new container system, others seem not to... I think they are slowly migrating over, so it's kind of a lottery which machine you get assigned

I've started using a travis config like this one to get things built on docker infrastructure and with an updated compiler that lets node 3 and 4 run node-gyp without breaking badly:
services:
  - docker
language: node_js
cache:
  directories:
  - node_modules
node_js:
  - "0.10"
  - "0.12"
  - "1"
  - "2"
  - "3"
  - "4"

addons:
  apt:
    packages:
      - gcc-4.8
      - g++-4.8
env: CXX="g++-4.8" CC="gcc-4.8"

script: "npm run-script travis"
after_success: "<coverage/lcov.info ./node_modules/coveralls/bin/coveralls.js"

Let's see what Travis says: https://twitter.com/wa7son/status/652826780676554752

Got an answer from Travis - so aparently the activation time of the repo is the thing that determine if a project by default gets routed to the new container infrastructure. And since this repo was activated on Travis after February 14th, 2015, then all builds by default run on the new container infrastructure.

A little bit strange, I got a This job ran on our legacy infrastructure. Please read our docs on how to upgrade string from a whole new repo's travis-ci. ha ... just FYI.


Correctness: Remove JsonUtils and IconConverter's 2-phase lookup bugs

Our templates were declared in the wrong order in JsonUtils, so all we needed to do was reorder them. The tests bear this out.
This allows us to disable two-phase template name lookup. I also fixed a minor issue that resulted in the inclusion of too many copies of expandIconPath.

I've only run this with Clang, so I'll come back and fix MSVC's complaints.

These tests do not run in CI, so I'm going to follow up with output from running these directly.

oh nevermind they absolutely do run in CI


What does "Invalid pages configuration: could not find a workspace named "xxx"" means?

Plugin
@knodes/typedoc-plugin-pages
Typedoc plugin(s) version(s)
0.23.1
Typedoc version
0.23.21
Describe the problem
I set up everything as documented, but kept getting this cryptic error message and couldn't figure out what it means nor did any search got something up
What did you expected ?
better error

Hi,
It means your configuration is somehow, invalid: you've set the moduleRoot flag on a page whose name is none of the name of your monorepo packages, or your project's name.
Please post your configuration so that I can help you.

Closing for housekeeping purposes


StackedHGEncoder import error

Hi
Looks like there no StackedHGEncoder in pytorch_toolbelt.modules.encoders.
I tried to find it in a previous version of the toolbelt but not succeed.
inria/models/hg.py
from pytorch_toolbelt.modules.encoders import EncoderModule, StackedHGEncoder

ImportError: cannot import name 'StackedHGEncoder'

This should be fixed since https://github.com/BloodAxe/Catalyst-Inria-Segmentation-Example/commit/6e1d47ad2d7699587de9432a56a12d4f9b327702
StackedHGEncoder has been added in pytorch-toolbelt==0.3.2 (Requirements file is also updated).


[FLOC-3227] Map public and private addresses to node UUID

Design for: https://clusterhq.atlassian.net/browse/FLOC-3227
I'm stuck with this.

@tomprince suggested an alternative approach which I'll attempt in another branch.


this is undefined, @Root seems to be workaround

Given the following setup:
Schema with RootQuery: { public: Public }
The Public ObjectType : { person(id: string): Person }
The Person ObjectType has a constructor (private data: PersonData) => data comes from a DB
The person ObjectType has a field { name(): string }
To access the data in the name() method I tried to use this, however this is undefined, even though the constructor is being properly executed. So I figured the data must be available via another way, indeed via the @Root annotation the actual instance of Person gets injected in the method's arguments.
Why do we need the @Root annotation? this is undefined in @Field methods, couldn't we simply point this to the correct value - as clearly it's available via @Root ?
Am I missing the point of what @Root does? I failed to find some docs on it other than the source.
Kind regards
Ben

@Root gives you access to the rootValue available through the graphql-js . You can see some information about it here: https://github.com/graphql/graphql-js/issues/735
Regarding the problem you're facing while trying to access this. We have a very similar use case, where we have to access DB data on a @Field method, and we are able to access this.
Maybe you could build an example where that happens, just so we could investigate and maybe find out what is happening.

Also, you root from the decorator is not specifically your  Type object, you can send any value to be resolved and in this case, this would not be strongly typed and later access to thiscan become be very misleading and confusing.


Text selection in the editor will be copied to clipboard automatically

code-server version: top of tree
OS Version: ubuntu 18.04 / and mac

I often make a copy of a text (ctrl+c) and then I high-light a piece of another text I want to replace (by selection), and then hit ctrl-v to replace it.
but this doesn't work with code-server, because code-server automatically copy the text being highlighted into clipboard. This is annoying and I don't find a way to turn it off.

@shi-yan Is the server Ubuntu and the client is running macOS?

Duplicated of #292

I run tested it on both ubuntu and mac

Closing this one to reduce duplicates. We can discuss in #292


vue warn and error in electron project

[Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.

found in

---> <Barcode>
       <Modal>
         <Card>

and this:
TypeError: this.$el.querySelector is not a function
    at VueComponent.render (/Users/Fauny/Work/WoodManager/source/epacial-vid/node_modules/vue-barcode/index.js:72:22)
    at VueComponent.Vue.$watch (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:3606:10)
    at VueComponent.mounted (/Users/Fauny/Work/WoodManager/source/epacial-vid/node_modules/vue-barcode/index.js:35:10)
    at callHook (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:2916:21)
    at Object.insert (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:4149:7)
    at invokeInsertHook (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:5944:28)
    at Vue.patch [as __patch__] (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:6163:5)
    at Vue._update (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:2665:19)
    at Vue.updateComponent (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:2783:10)
    at Watcher.get (webpack-internal:///./node_modules/vue/dist/vue.runtime.esm.js:3137:25)

sorry, this is a vue~electron~webpack issue, pls close it

@Fauny Do you have a link/resolution? I'm experiencing this issue too.

@duckbrain : (
I had to use jsbarcode instead. and embed vue-barcode code in my project


Reference Error on TinyFaceDetectorOptions (and other options)

I'm attempting to implement your new changes, but when I try to use:
const img1Description = await faceapi.detectSingleFace("s1", new TinyFaceDetectorOptions()).withFaceLandmarks().withFaceDescriptor()
I get the following error:
ReferenceError: TinyFaceDetectorOptions is not defined
I've confirmed I've got the latest JavaScript files and have tried it across all browsers with the same result. I also get the same error for MtcnnOptions and SsdMobilenetv1Options.
When I don't provide the options, the call is successful. What am I missing?

I think it should be clear, that everything is accessible via faceapi and not on the global scope:
new faceapi.TinyFaceDetectorOptions().
Sorry if the readme was confusing, I will adjust the snippets.

I figured it was something simple. That should have occurred to me. Thanks!


Define CCM multi-part API

Description
Define CCM multi-part API along the lines of the GCM multi-part API. The two APIs are not exactly the same as, contrary to GCM, CCM needs the size of the additional data and plaintext/ciphertext from the start.
Fixes #4352
Status
READY
Requires Backporting
NO
Todos

[x] Documentation
[x] Changelog updated

@mpg I believe I have addressed your comments. Thanks for having another look.

@mpg @gilles-peskine-arm I believe I have addressed all comments but https://github.com/ARMmbed/mbedtls/pull/4555#discussion_r640364749 for which I am not sure what to do yet.

@mpg @gilles-peskine-arm  Migration guide added, I believe I've addressed all comments now.

I've amended commit "Improve expected context state for some APIs" to address https://github.com/ARMmbed/mbedtls/pull/4555#discussion_r642341945 and added a new commit to address https://github.com/ARMmbed/mbedtls/pull/4555#discussion_r642365747.


irmin-pack: extract GC logic from ext

This PR is a part of #2039. It moves the core GC logic out of ext.ml and into its own set of files, gc.ml and gc_worker.ml. It also does a few cleanups in this area of the code. I recommend reviewing commit-by-commit to see the changes more easily.

Codecov Report

Merging #2063 (af53b9b) into main (5374885) will decrease coverage by 0.02%.
The diff coverage is 41.63%.

@@            Coverage Diff             @@
##             main    #2063      +/-   ##
==========================================
- Coverage   64.34%   64.32%   -0.03%
==========================================
  Files         131      133       +2
  Lines       15584    15580       -4
==========================================
- Hits        10028    10022       -6
- Misses       5556     5558       +2

Impacted Files
Coverage Δ

src/irmin-pack/unix/gc_worker.ml
8.59% <8.59%> (ø)

src/irmin-pack/unix/ext.ml
61.15% <70.00%> (-5.51%)
:arrow_down:

src/irmin-pack/unix/gc.ml
75.72% <75.25%> (+67.13%)
:arrow_up:

src/irmin-pack/unix/gc_intf.ml
100.00% <100.00%> (ø)

src/irmin/watch.ml
78.87% <0.00%> (-2.12%)
:arrow_down:

src/irmin-fs/unix/irmin_fs_unix.ml
68.38% <0.00%> (+0.64%)
:arrow_up:

src/irmin-fs/irmin_fs.ml
82.42% <0.00%> (+1.21%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Okay, I pushed the change that does not create a new gc_worker.ml but rather has the worker as a private module for gc.ml. It feels much better to me to have this all in one module. Args is now shared and the call into Worker from the main gc module doesn't feel as bad since it is internal (still probably needs more consideration  for if there is a better design).
@icristescu @Ngoguey42 can I get a final review?

thanks LGTM!


Sometime may block

Look this Dispatch thead, 5 thread is waiting:

I just looked through codes:
this wait IO will wait forever.
  /**
   * Removes and returns the stream's received response headers, blocking if necessary until headers
   * have been received. If the returned list contains multiple blocks of headers the blocks will be
   * delimited by 'null'.
   */
  public synchronized List<Header> takeResponseHeaders() throws IOException {
    if (!isLocallyInitiated()) {
      throw new IllegalStateException("servers cannot read response headers");
    }
    readTimeout.enter();
    try {
      while (responseHeaders == null && errorCode == null) {
        waitForIo();
      }
    } finally {
      readTimeout.exitAndThrowIfTimedOut();
    }
    List<Header> result = responseHeaders;
    if (result != null) {
      responseHeaders = null;
      return result;
    }
    throw new StreamResetException(errorCode);
  }

It will take my server blocked, to wait for these 5 thread. And this had occoured several times. So I don't know how did timeout work in okhttp3.
My version is 3.11.0

@yschimke yes, I think it's the problem, you said. We used it to call Apns Service, sometime may occoured this block phenomenon. And I tested it in local, timeout is worked. So now I planned to use EventLinstener to count timeout, and cancel it if it had been timeout.

And I hope you will fix it rapidly. Thanks.

Same here, pretty critical bug, do you able to fix it?
What is the workaround?

Could you please provide an executable test case to demonstrate the problem? As is a blocking thread is pretty normal.

Actually I think I understand the problem: headers aren't subject to the read timeout.

@swankjesse Actually I don't have an example on my hands, it was detected in commercial project, so I can't share the code. Also this problem is not "always reproducible".
However "forever lock" happens in this code: https://github.com/square/okhttp/blob/d51fd3ba6abcf3790bc0269fe108910848d234b0/okhttp/src/main/java/okhttp3/internal/http2/Http2Stream.java#L597

You could use https://github.com/CleverTap/apns-http2, it's the same as my
project. My project is a business project, so I couldn't provide this test
case to you.
And I can't test it for some simple test, I found it on our product server,
and comfirm this problem by log.
On Sun, Sep 16, 2018 at 10:30 PM Jesse Wilson<EMAIL_ADDRESS>wrote:

Could you please provide an executable test case to demonstrate the
problem? As is a blocking thread is pretty normal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/4241#issuecomment-421774319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACaZL5NN7EpDqag5yqTfWT5k4Coh-mlpks5ubmCJgaJpZM4WOxvA
.

--
山中无老虎猴子称大王，你好，我是猴子。

Executable test case? Not clear how we reproduce this.

No clear action to take here.

@swankjesse @yschimke has anyone ever came back to it later? It seems that I'm observing the same symptoms as in the ticket, but I feel like it can be actually related to how jvm handles blocking threads on the sockets. What would you need from the reproducible case? Creating an application that reproduces issues or eg an integration test case?


[svengbr] README - Instructions for running cypress on Windows

Where to find the issue
https://github.com/corona-warn-app/cwa-website/blob/master/README.md
Instructions npm run test:prepare to prepare testing a copy of the website using cypress.
Describe the issue
$ npm run test:prepare
may cause an error on Microsoft Windows.
><EMAIL_ADDRESS>test:prepare <path to repository>
> ./cypress/prepare.sh

'.' is not recognized as an internal or external command, operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:prepare: `./cypress/prepare.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      %USERPROFILE%\AppData\Roaming\npm-cache\_logs\<timestamp>-debug.log

Suggested change
Add a note to README.md
If executing $ npm run test:prepare causes an error on Microsoft Windows
'.' is not recognized as an internal or external command,
ensure that git is installed and execute the following command:
npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe".
PS I would be happy to submit a PR for this topic. I wanted to get feedback first though if the above is correct and if an addition to the README.md text on this topic would be welcome.

PR #1493 now submitted to close this issue.
The issue was never assigned and there was no feedback, however I am confident that the information is the PR is correct and useful.


Issue with get_push_certificate Command on Ruby 3.2 and 3.3

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
When using the get_push_certificate command in Fastlane, the generated .p12 certificate does not accept the given password when running with Ruby 3.2 or 3.3. The issue does not occur when running the command with Ruby 3.0.0.
Command executed
I ran bundle exec fastlane generate_certificate <options> it completed successfully and generated p12, pem and pkey files. But when I try to open p12 and give the password provided when generating it keychain rejects the password.

Steps to Reproduce:

Set up a Fastlane environment with Ruby 3.2 or 3.3.(add .ruby-version file in the project directory and run bundle install)
Add get_push_certificate lane. ( as given in fastlane environment section)
Run the Fastlane command: bundle exec fastlane get_push_certificate
Attempt to use the generated .p12 certificate with the given password.
See that the password is not accepted.

From my investigation, what I see is there is an upgrade in OpenSSL version from ruby 3.0 to 3.3. In 3.0 the version is OpenSSL 1.1.1q  5 Jul 2022 but in 3.3 it is OpenSSL 3.3.1 4 Jun 2024. Is there any workaround for using an old version of OpenSSL?
Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
14.3.1

Ruby
3.3.1

Bundler?
true

Git
git version 2.43.0

Installation Source
~/Documents/PersonalDocs/Rep/JK_Notification/vendor/bundle/ruby/3.3.0/bin/fastlane

Host
macOS 14.3.1 (23D60)

Ruby Lib Dir
~/.rbenv/versions/3.3.1/lib

OpenSSL Version
OpenSSL 3.3.1 4 Jun 2024

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
15.1

Swift Version
5.9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  lane :generate_certificate do |options|
    get_push_certificate(
      force: options[:force],
      development: options[:development],
      active_days_limit: 300,
      app_identifier: options[:bundle_id],
      save_private_key: true,
      username: ENV['ITC_USERNAME'], # do not commit
      team_id: options[:team_id],
      p12_password: options[:cert_password],
      output_path: options[:output_path]
    )
  end
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.221.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.6.0

did_you_mean
1.6.3

syntax_suggest
2.0.0

bundler
2.5.9

pathname
0.3.0

rake
13.2.1

base64
0.2.0

nkf
0.2.0

strscan
3.1.0

rexml
3.2.9

CFPropertyList
3.0.7

public_suffix
6.0.0

addressable
2.8.7

artifactory
3.0.17

atomos
0.1.3

aws-eventstream
1.3.0

aws-partitions
1.947.0

aws-sigv4
1.8.0

jmespath
1.6.2

aws-sdk-core
3.199.0

aws-sdk-kms
1.87.0

aws-sdk-s3
1.154.0

babosa
1.0.4

claide
1.1.0

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.5

domain_name
0.6.20240107

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.110.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.4.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.6

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.3.1

gh_inspector
1.1.3

jwt
2.8.2

multi_json
1.15.0

os
1.1.4

signet
0.19.0

googleauth
1.8.1

httpclient
2.8.3

mini_mime
1.1.5

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

google-apis-core
0.11.3

google-apis-androidpublisher_v3
0.54.0

google-apis-playcustomapp_v1
0.13.0

google-cloud-env
1.6.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.31.0

google-cloud-errors
1.4.0

google-cloud-core
1.7.0

google-cloud-storage
1.47.0

json
2.7.2

mini_magick
4.13.1

naturally
2.2.1

optparse
0.5.0

plist
3.7.1

rubyzip
2.3.2

security
0.1.5

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
2.5.0

terminal-table
3.0.2

tty-screen
0.8.2

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.24.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2024-06-26

Helo,
When using the get_push_certificate command in Fastlane with Ruby 3.2 or 3.3, the generated .p12 certificate was not accept the provided password while this works with Ruby 3.0.0. This issue is likely due to an upgrade in OpenSSL from version 1.1.1q in Ruby 3.0 to 3.3.1 in Ruby 3.3. A workaround is to use Ruby 3.0.0 by setting it in your project with a .ruby-version file and running bundle install it before generating the certificate.

I think I got the same issue. Any news on this?

Try OpenSSL::Provider.load('legacy').

How to fix it? I have the same problem.


Add Poetry specification [strict]

This change maintains the strict specification from the pip requirements file but allows the use of Poetry for virtual environments. A small addition is made to the README.md file to explain the usage.

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

@0xdabbad00 Apologies - is it appropriate to tag a maintainer? Sorry, I didn't find anything re contributor's guide

?

Closing due to lack of interest and other updates to the dependencies.


BEAM-2578 DebuggingWordCountTest Fails on Windows

[INFO] --- maven-failsafe-plugin:2.20:integration-test (default) @ beam-examples-java ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:analyze-only (default) @ beam-examples-java ---
[INFO] No dependency problems found
[INFO]
[INFO] --- maven-failsafe-plugin:2.20:verify (default) @ beam-examples-java ---
[INFO] Tests are skipped.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:41 min
[INFO] Finished at: 2017-07-10T23:18:01+05:30
[INFO] Final Memory: 45M/129M
[INFO] ------------------------------------------------------------------------

Coverage decreased (-0.02%) to 70.955% when pulling c0eec0de3f7bc1a059660c9aefec6279ce4d1202 on eralmas7:BEAM-2578 into 9f904dc00552349b535752e751ce82a7e484b471 on apache:master.

Coverage decreased (-0.2%) to 70.727% when pulling 26240bbe3a885de8fe6807c669cb40dac4f8f498 on eralmas7:BEAM-2578 into 9f904dc00552349b535752e751ce82a7e484b471 on apache:master.

R: @jbonofre


can not pull postgres

Can't pull postgres with docker

Correct, there is no postgres image for Windows.  You need to pull it from a Linux machine.  There is discussion of supporting windows based images in https://github.com/docker-library/postgres/issues/324.


Missing documentation for before() callback

for a project I'm on I need to open a dropdown before proceeding to the next step in the tour, I found that the before() callback was added for this specific use case in 1.5.0 but I could not find any documentation about how it works.

found it on the npm page, it would be great to have it on the wiki page too

Hi @Ragnar-Oock,
Thanks for noticing this, it's done: https://github.com/pulsardev/vue-tour/wiki/Features.


Pop up an incorrect browser window automatically when debugging a Reactsite project on Windows OS

OS: Linux/Windows
Build Version: 20211105.14
Regression: Not a regression
Repro Steps:

Open a Reactsite project in VS Code.
Type cd app in TERMINAL window -> Type npm install.
Navigate to "Run and Debug" view -> Select "Azure Static Web Apps…" in the dropdown list -> Select "SWA: Run app"
-> Start Debugging.
Check whether pop up a correct browser window automatically.

Expect:
Pop up a correct browser window automatically.
Actual:
Pop up an incorrect browser window automatically.

More Info:
On Linux, the browser window doesn't pop up automatically, need to type the address in browser manually.

Thanks for the issue report.
Unfortunately, the Chrome window needed for debugging with VS Code must be launched separate from any currently running Chrome window. This would definitely be nice, but currently it isn't possible.

More Info:
On Linux, the browser window doesn't pop up automatically, need to type the address in browser manually.

What about this?

@v-xinda Could you try the test on Linux again using this repo? https://github.com/alexweininger/ReactSite
Thanks!

@nturinski The browser window doesn't pop up automatically when debugging the project on Linux. The above browser window opens after typing the address "http://localhost:4280" in the Chrome browser.

@alexweininger This issue also reproduces on Linux when debugging the ReacSite project which cloned from https://github.com/alexweininger/ReactSite.

OS: All
For vue-baisc-api / angular-basic-api repo (Clone https://github.com/alexweininger/vue-basic-api / https://github.com/alexweininger/angular-basic-api):
The browser window doesn't pop up automatically when debugging it. Display hello world in the page after typing the address in browser manually.

For nextjs-basic-api repo (Clone https://github.com/alexweininger/nextjs-basic-api):
The browser window doesn't pop up automatically when debugging it. Display What Can I Deploy to Static Apps? in the page after typing the address in browser manually.

For svelte-basic-api repo (Clone https://github.com/alexweininger/svelte-basic-api):
The browser window doesn't pop up automatically when debugging it. The page is blank after typing the address in browser manually.

@v-xinda When you run npx swa --version, what is the output? And also func --version?
And could you try running npm start in the root of this workspace with a cloned staticwebdev/angular-basic repo and report the output and behavior?

@alexweininger This issue also reproduces on Linux when debugging the ReacSite project which cloned from alexweininger/ReactSite.

Thanks for the information. This now leads me to believe that there's an issue with the pwa-chrome debug type launching Chrome on Linux. But I have yet to be able to reproduce this on my own.

@alexweininger
func version: 4.0.3928
SWA CLI version: 0.8.0
The result of running npm start as below:
PS C:\Users\AzureTest\Desktop\angular-basic> npm start

><EMAIL_ADDRESS>start C:\Users\AzureTest\Desktop\angular-basic
> ng serve

Compiling @angular/core : es2015 as esm2015
Compiling @angular/common : es2015 as esm2015
Compiling @angular/platform-browser : es2015 as esm2015
Compiling @angular/platform-browser-dynamic : es2015 as esm2015
√ Browser application bundle generation complete.

Initial Chunk Files   | Names         |      Size
vendor.js             | vendor        |   2.43 MB
polyfills.js          | polyfills     | 485.71 kB
styles.css, styles.js | styles        | 346.78 kB
main.js               | main          |   7.51 kB
runtime.js            | runtime       |   6.15 kB

                      | Initial Total |   3.26 MB

Build at: 2021-11-11T03:00:47.224Z - Hash: 9adaff48e91098578d2d - Time: 55055ms

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

√ Compiled successfully.
√ Browser application bundle generation complete.

Initial Chunk Files   | Names  |      Size
styles.css, styles.js | styles | 346.78 kB

4 unchanged chunks

Build at: 2021-11-11T03:00:52.906Z - Hash: 0bafedaf87216d457228 - Time: 3919ms

√ Compiled successfully.

@v-xinda We've added a fix for #574 that we think might also fix this issue. Could you retry this on the most recent build?
Build: 20211110.10
Thanks! 🤠

Verified this issue on the build 20211110.10, it doesn't reproduce on Windows and Mac. But it still reproduces on Linux. Serene gives you a Linux machine which reproduced this issue


github_fetcher arguments error

kruug@kruugdeb:~ $ go get github.com/pengwynn/flint
# github.com/pengwynn/flint/flint
dev/go/src/github.com/pengwynn/flint/flint/github_fetcher.go:27: too many arguments in call to g.Client.Repositories
dev/go/src/github.com/pengwynn/flint/flint/github_fetcher.go:27: not enough arguments in call to g.Client.Repositories(url).One
kruug@kruugdeb:~ $ flint --version
-bash: flint: command not found
Not sure how to fix.

I am also having this issue with a fresh install of Go on OS X Yosemite.

I was really hoping to integrate this into Atom tonight too!

Should be fixed by c3a5d8d.


Cleanup doc issues

In create_component_from_scratch.md,  ComponentExample has additional field "spec.name" (with value "helloworld-python"). Need to remove it.

Add link at the end of create_component_from_scratch.md to "ApplicationConfiguration".

In install.md, update KEDA install instructions. The repo to install KEDA through Helm 3 has changed. "helm repo add kedacore https://kedacore.github.io/charts"

I'll send a PR for this.

here's the link to the helm3 keda install: https://keda.sh/deploy/

Keda install instruction is already fixed. We need to clean up the remaining issues. Zed will take care of it.


Multiple backticks for inline code

When mapping a code element to AsciiDoc, the converted content is often enclosed in multiple backticks, instead of just one (as it should be).

Not a bug! There are certain cases where multiple backticks are really required, e.g. if the code is not surrounded by whitespace. For more details, see the topic "unconstrained quotes" in the AsciiDoctor Manual.


Fix Invalid_flowconfig error

The .flowconfig file had an empty line at the start which causes the following issue when running the "npm test:flow" command:
{"code":8,"reason":"Invalid_flowconfig","msg":".flowconfig:1 Unexpected config line not in any section"}
Removing the first line fixed the error on my system:
Microsoft Windows 10 Pro Build 15063
Node v8.6.0
Flow 0.55.0

Oh, that's strange. I've never seen that. I'll merge this in anyway, though. Thanks!