Add option to never remember email account password.

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
5.806
Problem you are trying to solve
With the rise in demand for more security in mobile applications (as evidenced by requests like https://github.com/k9mail/k-9/issues/753, https://github.com/k9mail/k-9/issues/1352, https://github.com/k9mail/k-9/issues/3318, https://github.com/k9mail/k-9/issues/3377, https://github.com/k9mail/k-9/issues/3920, https://github.com/k9mail/k-9/issues/4796, https://github.com/k9mail/k-9/issues/5260, https://github.com/k9mail/k-9/issues/5740) a lot of users are trying to seek solutions for common security risks such as unauthorized device access and network sniffing for credentials.  I understand K9 isn't an advanced security application, nor should it be, but I think this can give some users a much wanted peace of mind.
Suggested solution
I'd like to have an option for K9 to NOT remember my email account password and just prompt the user to enter it if and when needed.
This way the user can rely on a third party application for encrypting their credentials or they can remember their password manually.  While this won't prevent unauthorized access to existing data on the device, it will prevent new data from being sent to the device and give protection against unauthorized users sending data using the saved account.
It can also help the user to be more aware of the network they're connected to in the event they're connected to a rouge network or otherwise at risk for a man in the middle type of attack.
Screenshots / Drawings / Technical details
If implemented, it'd probably be good to have an option in the per account settings, probably under general settings.  It could just be a simple checkbox for "Remember password" that's checked by default.
Another checkbox could be added when adding a new account to "remember" the password that would have to be unchecked.
There could also be a global setting in the main General Settings under Privacy that unchecks it for all existing accounts (perhaps with a warning that any existing stored passwords will be removed) and keeps the creation checkbox unchecked by default.
The effects could cause the app to prompt the user for the password for a given account when the app is opened, when a manual or automatic update is triggered, or when sending an email or other server request.
When entered, the password would be used for that connection attempt and "forgotten" when finished.  It would be similar to how Thunderbird operates if you decline to have it remember account passwords.

What you're suggesting would require large changes to the way the app works. The user experience would also not be something most users expect or want. Making this an optional feature would just add even more complexity.
I wrote down numerous times why such a feature doesn't improve security in a meaningful way if you use the security features Android already offers. Since you've linked the relevant issues, I assume you already know this.
If you need this feature, K-9 Mail is not the app for you.


Kube apiserver  fails to get deployed if issuer URL has fragment

How to categorize this issue?

/area control-plane
/kind bug
What happened:
  kubernetes:
      oidcConfig:
        issuerURL: 'https://test.html# '

If issuerURL has fragment then KAPI fails to get deployed and throw following error -
E1115 03:29:46.930763       1 run.go:74] "command failed" err="jwt[0].issuer.url: Invalid value: \"https://test.html# \": URL must not contain a fragment"

What you expected to happen:
KAPIs should be deployed successfully.
How to reproduce it (as minimally and precisely as possible):
Create a shoot cluster with the issuerURL having #<text> at the end. The KAPIs pod will in error state.
Anything else we need to know?:
Environment:

Gardener version: 1.107
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

We can add validation to improve this.
/assign


Runelite keeps closing itself every few minutes.

Seen some posts about this in the past and tried some "fixes" with no success.
Currently doing Mahog homes and whenever I enter a home and sometimes when I tele to a new area, the client just spontaneously closes.
Was working fine yesterday and throughout the weekend with no issues, had no driver updates in a good week, problem continues before and after a Java update, and cant find anything in any log folders.
Any advice / help is appreciated, thank you :)

Hey,
I've encountered the same issue, but I was in the Catacombs of Kourend and when I teleported using the Xeric's talisman it crashed my client and auto-closed. I experienced this last night as well. I think there is a deeper issue.

There is currently an instability with 64-bit Java. Using the 32-bit RuneLite client  should resolve this issue for the meantime.

I recommend following ThePharros's advice. If you have further issues, please reach out in our Discord server's #support channel.


[BUG]  video doesn’t want to change by clicking

BUG
I have a component where I use HoverVideoPlayer. When I click to another component, I want to change the video by clicking , but the video stays the same. I dont know why is happend? My data changes but the video stays the same :(
@Gyanreyer

MY COMPONENT:

console in the devtools:

This is expected behavior because browsers implement the <video> element so that once it has loaded a source you have to either fully unmount/remount the element or go through a more complicated process of properly unloading the previous source first.
To get what you want, I think you would probably be best off using the key prop to make the component remount every time the source changes.
It would probably look like this:
  const videoSrc = activeItem.video.replace(...);

  <HoverVideoPlayer
    key={videoSrc}
    videoSrc={videoSrc}
  />

Hopefully that will work!

Hi @Gyanreyer! Thank you it solved my problem!


get_file_age function will not work on MacOS

https://github.com/aaronpowell/tmux-weather/blob/a954fe15c152d6be600bca4458dd4190c8b611b5/scripts/helpers.sh#L24
get_file_age uses stat -c to get file age, however, the BSD stat does not support -c argument:

stat: illegal option -- c

Maybe add a short paragraph on README.md to instruct MacOS users to have GNU stat installed to make this plugin work?

There was an outsanding PR that changed this: https://github.com/aaronpowell/tmux-weather/blob/master/scripts/helpers.sh#L25-L29
Does that fix the problem? Otherwise feel free to send a PR to fix it


Matthew Helmke final project

It looks like the container node server image has had some updates since the course was written. It has far fewer vulns than in the example.

Oh, good to know! We should update the example vuln count in the course. Thanks!


feat: add Qovery/Replibyte

Qovery/Replibyte: Seed your development database with real data
$ aqua g -i Qovery/Replibyte

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ replibyte --help
replibyte 0.10.0
Replibyte is a tool to seed your databases with your production data while keeping sensitive data
safe, just pass `-h`

USAGE:
    replibyte [OPTIONS] --config <configuration file> <SUBCOMMAND>

OPTIONS:
    -c, --config <configuration file>    Replibyte configuration file
    -h, --help                           Print help information
    -n, --no-telemetry                   disable telemetry
    -V, --version                        Print version information

SUBCOMMANDS:
    dump           all dump commands
    help           Print this message or the help of the given subcommand(s)
    source         all source commands
    transformer    all transformer commands

Thank you!

v4.120.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.120.0


iPhone

You mentioned that this works with an Android phone; is there any way to get the localKey with an iPhone and Mac?

Mac, yes (using Blue Stacks emulator).  iPhone, no.
You can get both pieces of information by using logcat to "sniff" the data on an android phone OR emulator (like BlueStacks.
This is known to work on Eufy Home v2.3.2 (click the link to download the apk)

More detailed steps on using logcat:

Close the app on your mobile device
Connect the device to your laptop and enable USB debugging
Run adb logcat -e 'tuya.m.my.group.device.list' (assumes you have already installed the Android debug tools)
Launch the Eufy Home app
The output lines contain JSON, you're looking for the values of localKey (16 character hex string) and devId (20 character hex string).

You can use Charles on your PC / Mac as an SSL proxy to log the data traffic when opening the EufyApp. Here you can read out both parameters.


Generator: Update SDK /services/iaasalpha

Generated from GitHub run<PHONE_NUMBER>0

There is a newer PR with the same changes https://github.com/stackitcloud/stackit-sdk-go/pull/992


Error: "Device "tun0" does not exist."

Context
I have pihole set up already and running in a Docker Container on a Apple silicon Mac.
Everything is working well.
But I want to make it work with OpenVPN(to allow iPhone to access even outdoor to block ADs),
but I didn't use "tun0"(but eth0) at the very beginning and I don't know where to config it.
Is there a way to change eth0 to tun0 or add tun0 to make it work with OpenVPN?
Thank you very much😃
more details:
Pihole running in a container. Config command to pihole I used:
docker run --name=pihole1 -e TZ=Taiwan -e jq-UbajZ=password -e SERVERIP=<IP_ADDRESS> -v pihole_app:/etc/pihole -v dns_config:/etc/dnsmasq.d -p 81:80 -p 53:53/tcp -p 53:53/udp --restart=unless-stopped pihole/pihole
pihole version
Pi-hole version is v5.11.4 (Latest: v5.11.4)
AdminLTE version is v5.13 (Latest: v5.13)
FTL version is v5.16.3 (Latest: v5.16.3)

Thank you for your answers :)


header: dead link

The 'How to Write Docs' link in the header appears to be dead.  It is pointing here:
https://github.com/documentationjs/documentation/blob/master/GETTTING_STARTED.md
I'm not sure where it is supposed to point.

:+1: thanks, fixed


Fix ClassCastException in TextInput

ClassCastException happening if getText() is not Spanned
Fatal Exception: java.lang.ClassCastException: java.lang.String cannot be cast to android.text.Spanned
at com.facebook.react.views.text.ReactTextView.reactTagForTouch(ReactTextView.java:52)
at com.facebook.react.uimanager.TouchTargetHelper.getTouchTargetForView(TouchTargetHelper.java:257)
at com.facebook.react.uimanager.TouchTargetHelper.findTargetTagAndCoordinatesForTouch(TouchTargetHelper.java:101)
at com.facebook.react.uimanager.JSTouchDispatcher.handleTouchEvent(JSTouchDispatcher.java:76)
Test plan: Manual code inspection, Circle CI.

Signed it

@mkonicek for review

The fix looks good. Any idea why it's not an instance of Spanned?

@mkonicek We are not able to reproduce it from our side ( we tested on 100 devices ), but we are seeing the crash happening on very random devices in our Fabric dashboard.

@mkonicek Can you please review it. As this fix will help us to reduce the number if crashes happening in app due to react native

@mkonicek Can you please review it. As this fix will help us to reduce the number if crashes happening in app due to react native


Myntra Customize - Add active links #136

https://github.com/DhanushNehru/Ultimate-Web-Development-Resources/issues/136

Added Links in navigation bar

On clicking a link in nav bar

Hi @epicadidash
For Hacktoberfest 2023 the PR needs to be Approved status with hacktoberfest-accepted label. Would you please mark this approved and add label?


”Chiochiș” is listed in the drop-down menu

Description:
"Chiochiș" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Chiochiș" in the search bar.

Expected results
The location is listed in the drop-down menu as "Chiochiș, Bistrița-Năsăud".


Check checklist completion deadline with CPC

Goal is for graduation by OpenJS Collaborator’s Summit. The CPC will need to have time to look at the work done and actually vote on allowing AMP to graduate, so we need to clarify when that will be.
Additionally, it's unclear whether the CPC will have all of its blocking issues fixed by then.

@brianwarner do you know by when the CPC needs to have the checklist completed to be able to move out of graduation?

Filed in https://github.com/openjs-foundation/project-onboarding/issues/30.


Form submitted automatically

I have a form consists of multiple steps, "Back" and "Next" buttons are provided for navigation between the steps. And in the last step, "Next" button becomes a submit button: <Button type="submit">Submit</Button>.
The problem is, whenever I go to the last step, the form is automatically submitted, without clicking the submit button.
If I replace the submit button with <input type="submit" value="Submit" /> or <button type="submit">Submit</button>, the form is not automatically submitted as expected.

@linlycode Your issue has been closed because it does not conform to our issue requirements.
Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

@linlycode Your issue has been closed because it does not conform to our issue requirements.
Please provide a full reproduction test case. This would help a lot  .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

What's the issue requirement specifically? I can't find it in README.md.

@linlycode When you open an issue you should be presented with an issue template. Try to fill out as much as possible with an emphasis on a minimal example that showcases the issue.

@linlycode When you open an issue you should be presented with an issue template. Try to fill out as much as possible with an emphasis on a minimal example that showcases the issue.

Sorry, I didn't see the templates when I create the issue. Now I find it. #13660


[BUG] Publish pipeline fails on push_changes_to_Dev_APIM when APIM configured with App Insights

Release version
APIOPS v5.0.0
Describe the bug
Publish pipeline fails with error message below when publishing artifacts to Dev environment before applying settings to Prod. When skipping publishing to Dev stage, publishing to Prod works fine.
System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/UK-Infrastructure/providers/Microsoft.ApiManagement/service/dev-apim-uk-01/diagnostics/applicationinsights?api-version=2022-04-01-preview failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"loggerId","message":"LoggerId must be specified."}]}}'.
2023-12-17T17:16:08.6694390Z          at common.HttpPipelineExtensions.Validate(Response response, Uri requestUri)
2023-12-17T17:16:08.6694832Z          at common.HttpPipelineExtensions.PutResource(HttpPipeline pipeline, Uri uri, JsonObject resource, CancellationToken cancellationToken)
2023-12-17T17:16:08.6695292Z          at publisher.Program.<>c__DisplayClass13_0.<b__0>d.MoveNext()
2023-12-17T17:16:08.6696593Z       --- End of stack trace from previous location ---
2023-12-17T17:16:08.6697127Z          at publisher.Diagnostic.PutDiagnostic(DiagnosticName diagnosticName, JsonObject json, ServiceUri serviceUri, PutRestResource putRestResource, ILogger logger, CancellationToken cancellationToken)
2023-12-17T17:16:08.6697753Z          at publisher.Diagnostic.<>c__DisplayClass8_0.<b__0>d.MoveNext()
2023-12-17T17:16:08.6699484Z       --- End of stack trace from previous location ---
2023-12-17T17:16:08.6699767Z          at System.Threading.Tasks.Parallel.<>c__501.<<ForEachAsync>b__50_0>d.MoveNext() 2023-12-17T17:16:08.6700045Z       --- End of stack trace from previous location --- 2023-12-17T17:16:08.6730667Z          at common.IEnumerableExtensions.ForEachParallel[T](IEnumerable1 enumerable, Func2 action, CancellationToken cancellationToken) 2023-12-17T17:16:08.6731064Z          at publisher.Diagnostic.ProcessArtifactsToPut(IReadOnlyCollection1 files, JsonObject configurationJson, ServiceDirectory serviceDirectory, ServiceUri serviceUri, PutRestResource putRestResource, ILogger logger, CancellationToken cancellationToken)
2023-12-17T17:16:08.6731641Z          at publisher.Service.ProcessArtifactsToPut(IReadOnlyCollection`1 files, JsonObject configurationJson, ServiceDirectory serviceDirectory, ServiceUri serviceUri, ListRestResources listRestResources, GetRestResource getRestResource, PutRestResource putRestResource, DeleteRestResource deleteRestResource, ILogger logger, CancellationToken cancellationToken)
2023-12-17T17:16:08.6732078Z          at publisher.Publisher.RunWithoutCommitId(CancellationToken cancellationToken)
2023-12-17T17:16:08.6732301Z          at publisher.Publisher.Run(CancellationToken cancellationToken)
2023-12-17T17:16:08.6732511Z          at publisher.Publisher.ExecuteAsync(CancellationToken cancellationToken)
2023-12-17T17:16:08.6732697Z info: Microsoft.Hosting.Lifetime[0]
2023-12-17T17:16:08.6732851Z       Application is shutting down...
2023-12-17T17:16:08.6733105Z fail: Microsoft.Extensions.Hosting.Internal.Host[9]
2023-12-17T17:16:08.6733268Z       BackgroundService failed
Expected behavior
Publish pipeline shouldn't fail when pushing changes to lower-level environment.
Actual behavior
Adjustments of pipeline required in order to get it to work
Reproduction Steps

Extract all API's.
Run publishing pipeline.
Publishing pipeline fails on stage push_changes_to_Dev_APIM

Is the logger artifact being extracted? For some reason it's not being included when publishing which is throwing a 400. Also make sure you are not trying publish against a logger that doesn't exist.

Logger artifact are getting created in repository:
{
"properties": {
"credentials": {
"instrumentationKey": "{{Logger-Credentials--6566f39dfb426808c40853a6}}"
},
"isBuffered": true,
"loggerType": "applicationInsights",
"resourceId": "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX/resourceGroups/XXXXXXXXX/providers/microsoft.insights/components/APIM-UK-Dev-AppInsights"
}
}
I've added config file with following settings and after that publish pipeline also worked successfully for Dev environment. Looks like publisher fails to parse some settings from logger artifact.
apimServiceName: dev-apim-uk-01
loggers:
- name: apim-uk-appinsights
properties:
loggerType: applicationInsights
description: prod application insights
resourceId: "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX/resourceGroups/XXXXXXXXX/providers/microsoft.insights/components/APIM-UK-Dev-AppInsights"
credentials:
instrumentationKey: "{{Logger-Credentials--6566f39dfb426808c40853a6}}"
isBuffered: true
diagnostics:

name: applicationinsights
properties:
verbosity: information
loggerId: "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX/resourceGroups/XXXXXXXXX/providers/Microsoft.ApiManagement/service/dev-apim-uk-01/loggers/apim-uk-appinsights"
apis:
name: demo-conference-api
diagnostics:

name: applicationinsights
properties:
verbosity: information
loggerId: "/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX/resourceGroups/UK-Infrastructure/providers/Microsoft.ApiManagement/service/dev-apim-uk-01/loggers/apim-uk-appinsights"

Yeah the behavior you are experiencing is odd. Usually you only need congifuruation.[env].yaml files for higher environments as you promote your changes and not for the lower environment (typically dev). In your case it seems like you are having to provide a configuration file for the lower environment that has configurations that match what you have already extracted which is unnecessary.
@guythetechie any idea what could be causing this behavior?

Can you show the contents of your DEV diagnosticInformation.json file? Should be in a path like /artifacts/diagnostics/applicationinsights/diagnosticInformation.json.

{
"properties": {
"alwaysLog": "allErrors",
"httpCorrelationProtocol": "Legacy",
"logClientIp": true,
"sampling": {
"percentage": 100,
"samplingType": "Fixed"
}
}
}

I've tried to enable Trace logging and re-run pipeline again to get more details regarding error when there is no config file for Dev environment, but eventually it worked.
I will try to do one more test with fresh API.

Please remember to close the issue once you are ready.


Second derivative of reduce_prod returns NaN

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
TensorFlow installed from (source or binary): binary (pip)
TensorFlow version (use command below): v2.3.0-54-gfcc4b966f1 2.3.1
Python version: 3.8.5
CUDA/cuDNN version: executing on CPU
GPU model and memory: executing on CPU

Describe the current behavior
Computing the second derivative of a function containing tf.reduce_prod, where one of the arguments is zero, returns NaN.
Describe the expected behavior
The second derivative should be finite in those cases.
Standalone code to reproduce the issue
def grad(f):
    x = tf.Variable([0.])
    with tf.GradientTape() as t:
        y = f(x)
    g = t.gradient(y, x)
    return g

def grad2(f):
    x = tf.Variable([0.])
    with tf.GradientTape() as t2:
        with tf.GradientTape() as t1:
             y = f(x)
        g = t1.gradient(y, x)
    g2 = t2.jacobian(g, x)
    return g2

grad(lambda x: tf.reduce_prod(tf.constant([2.,0.])*x*x)) # returns 0 as expected
grad2(lambda x: tf.reduce_prod(tf.constant([2.,0.])*x*x)) # returns NaN
grad2(lambda x: 2.*x*x) # returns 4 as expected

@swertz
I ran the code shared and face a different issue, please find the gist here. Please share a colab gist with the error reported.

I could reproduce in colab with v2.3.0, please find it here.

@swertz
I do not have access to the above link.

@swertz
I do not have access to the above link.

Sorry! Should be fine now...

@swertz
I ran the code and this had been fixed in nightly version, please find the gist here.

Great, thanks!


Remove dashboard?

As highlighted in https://discourse.pangeo.io/t/pangeo-forge-bakeries/3630, the presence of the dashboard on pangeo-forge.org is probably misleading to folks who are just starting to learn about Pangeo Forge, given that we are not currently operating a public bakery instance. Perhaps we should remove the dashboard?

presence of the dashboard on pangeo-forge.org is probably misleading to folks who are just starting to learn about Pangeo Forge, given that we are not currently operating a public bakery instance. Perhaps we should remove the dashboard?

Although I'm not directly involved here, I thought I'd share that I've seen some confusion around the number of datasets produced by Pangeo Forge as well which could be another good reason to remove the dashboard.

Thanks for chiming in @maxrjones. A possible deprecation cycle for the unmaintained dashboard/catalog could be:

Migrate all currently active/openable pangeo-forge.org catalog entries to the LEAP Catalog  as described in https://github.com/leap-stc/data-management/blob/main/catalog/README.md - anyone can open PRs for this on linked LEAP repo
Once 1 is complete, replace the current dynamic catalog page with a static page linking to the LEAP Catalog and an explanatory note. - this will be easy
Write + publish blog on “lessons in scoping” about what we've learned about how hard it is to run production services vs. develop tools, providing the context for why we don't maintain the dynamic site anymore. - I can/should do this
Once 3 is complete, remove the dashboard page and link
Once 1 & 4 are complete the zombie 🧟 heroku backend serving data to the dashboard and catalog can be shutdown and associated repo archived.

Thoughts? Also, @rabernat does this seem sensible?

The dashboard currently errors:
"Application error: a client-side exception has occurred (see the browser console for more information)."
https://pangeo-forge.org/dashboard/feedstocks

Thanks @rbavery! Yes I noticed that this morning as well.
I will put in a PR either later today or early next week to remove the dashboard.

Thanks @cisaacstern !

Once 1 is complete, replace the current dynamic catalog page with a static page linking to the LEAP Catalog and an explanatory note. - this will be easy

Interested to read the blog post and about any efforts to make and maintain static or dynamic catalogs.


Kernel Runs cells indefinitely

Applies To

[x] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
The cells run on a loop forever. I constantly have to restart the kernel and lose all my data/variables. It happens repeatedly. I have restarted the kernel. Uninstalled and reinstalled the jupyter extension, restarted my mac, quit and re-opened VS code. No clue why this is happening.
VS Code Version
1.68.0
Jupyter Extension Version
v2022.5.1001601848
Jupyter logs
info 10:29:49.355: Cell 7 executed with state Success
info 10:29:49.407: Executing silently Code (idle) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
info 10:29:49.426: Executing silently Code (completed) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
info 10:29:49.452: Executing silently Code (idle) = import builtins\nbuiltins.print(_VSCODE_getVariableInfo(batch_predictions))
info 10:29:49.467: Executing silently Code (completed) = import builtins\nbuiltins.print(_VSCODE_getVariableInfo(batch_predictions))
info 10:29:50.33: Executing silently Code (idle) = import builtins\nbuiltins.print(_VSCODE_getVariableInfo(scaled_data))
info 10:29:50.50: Executing silently Code (completed) = import builtins\nbuiltins.print(_VSCODE_getVariableInfo(scaled_data))
[I 10:29:51.195 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 10:29:51.197 NotebookApp] Starting buffering for dbba2645-934c-47c5-bc12-bed53c5c8575:b9467747-eecb-488e-851f-240b2f42c09d
[I 10:29:51.201 NotebookApp] Restoring connection for dbba2645-934c-47c5-bc12-bed53c5c8575:b9467747-eecb-488e-851f-240b2f42c09d

Coding Language and Runtime Version
Python 3.11.4
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Sorry I never got back to you on this.
Please note, you seem to be using a very old version of VS Code and Jupyter extesnion
Plese update to the latest versions and if it still occurs, please do file a new issue and we'll look into it.


Update dependencies

Update dependencies

Codecov Report

Merging #69 (df5786c) into dev (17269c2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               dev       #69   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         4    +3
  Lines          170       179    +9
=========================================
+ Hits           170       179    +9

Impacted Files
Coverage Δ

named_enum/__init__.py
100.00% <100.00%> (ø)

named_enum/enum.py
100.00% <100.00%> (ø)

named_enum/meta.py
100.00% <100.00%> (ø)

named_enum/version.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Reproduce private pulling issue + poc a fix

Follow-up to https://github.com/bazel-contrib/rules_oci/issues/126#issuecomment-1534052373
I spent some time exploring to understand if something was wrong on my side or if there was an issue and managed to pull private images with the crude fix that'll find here.
The code that handles the authentication seems to make assumptions about ~/.docker/config.json that do not match the structure of that file.
# ~/.docker/config.json
{
  "auths": {
    "https://index.docker.io/v1/": {}
  },
  "credHelpers": {
    "asia.gcr.io": "gcloud",
    "eu.gcr.io": "gcloud",
    "gcr.io": "gcloud",
    "marketplace.gcr.io": "gcloud",
    "staging-k8s.gcr.io": "gcloud",
    "us-central1-docker.pkg.dev": "gcloud",
    "us.gcr.io": "gcloud"
  },
  "credsStore": "desktop"
}

But the original code tries to look for us.gcr.io if that's what I set to the registry attr on the oci_pull. It then takes a look at the credsStore which will is set to desktop and doesn't know how to find my private image.
The fix is to instead iterate on the credHelpers if we don't find a matching entry under "auths", which I very crudely implemented.
I have included in my commit the modifications I did to test the code locally, which allowed me to successfully pull the image.
At this stage, I think it's best for me to reach out, as I don't know what would be the best solution to write a proper e2e test for such a patch. With some guidance, I could implement the fix properly, though I'm totally okay if you want to take over.

closing in favor of #237


[RFC 0089] Buildpack Authors' Tooling Sub-Team

Add Buildpack Authors' Tooling Sub-Team from buildpacks/rfcs#159.

Resolved by https://github.com/buildpacks/community/pull/104


.Net Core installer task: Don't install if version already present on the machine

Copied issue from vsts-docs=> https://github.com/MicrosoftDocs/vsts-docs/issues/4153
Users want to ensure a version is present on the agent machine, while not reinstalling it, if it is already globally installed on the machine.

Possible solutions:

Update azure-pipelines-image-generation to create the markup file for each version installed on agent image.
Provide a checkbox for not installing the version if already present on the machine.
Provide a path to search for if version is installed at that location. (like /home/dotnet/)

Complications with each:

Users will have to global install locations as the installation path. This might lead to problems on the agents.
The global install location in linux machines is not set.
& 3. Enable Multi-Level lookup needs be ignore if any of the two cases are being used.

Is there an ETA for this? We have an issue where cisco has blacklisted the IP address <IP_ADDRESS> and all of our pipelines are failing now because of this. If this issue was fixed, at least we could have fetched it from the cache until the cisco issue is resolved.
Here is what we get:
Failed to download or parse release-index.json with error: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"<IP_ADDRESS>","port":443}

Even the multi level lookup as documented here Dotnet core installer doc does not work as described. We are using the Windows-2019 hosted agent where according to this Hosted agent installed software readme the used runtime should already be installed and not be re-installed.

Any update on this?

This seems like it would remove a lot of unnecessary queue time in pipelines and download traffic from sdk sources if applied.
What is the progress on this?

Any news on that?

Any eta on this please? For me every pipeline run takes 30s to download any sdk which is waste of time.

Not only a waste of time. It also uses maybe precious seconds from your free time per month.

@aaronhallberg can you have someone have a look at this ?

Still nothing, huh?

Just saying. I'm also eagerly waiting for this fix. The pipelines are such a timesink currently. It takes more time to download the sdk (30s) than it does to run all the other steps combined (<30s). An update is really appreciated.

How can this still be open after all these years? Downloading .NET 5.x takes 30 seconds while it's already on the windows-latest image. This costs us time, and it costs Microsoft precious server resources.

How can this still be open after all these years? Downloading .NET 5.x takes 30 seconds while it's already on the windows-latest image. This costs us time, and it costs Microsoft precious server resources. It works fine for the NodeTool task, why can't this just work as well?

Agreed, number of builds times 30 seconds should be an absolutely insane amount of server capacity freed up if this is fixed.

I have spent the entire day today trying to figure this out.
It's pretty interesting.
When you create a new pipeline and use the task:
- task: UseDotNet@2     displayName: 'Install .NET'     inputs:       version: '6.0.x'       includePreviewVersions: true
Then it will not find anything in cache.
When you rerun it, it will not find anything in cache.
It will however install .NET in the version 6.0.301
However, when I ran a simple script to display the dotnet version, it turns out that the dotnet version is 6.0.301.
So, to summarize - UseDotnet doesn't see that the .NET 6 is installed by default.
This bug has been opened for 2 years and each .NET install consumes 250MB and 30s of time.
I wonder how many builds have been executed with this command...
I wrote a simple workaround to cache the .NET installation.
`# Starter pipeline
Start with a minimal pipeline that you can customize to build and deploy your code.
Add steps that build, run tests, deploy, and more:
https://aka.ms/yaml
variables:
DOTNET_CACHE_FOLDER: $(System.DefaultWorkingDirectory)/dotnet
INSTALL_DOTNET: true
dotnet: '6.0.x'
trigger:

master

pool:
vmImage: ubuntu-latest
jobs:

job: 'test'
steps:

task: PowerShell@2
displayName: Get dotnet version
inputs:
targetType: inline
script: |
try {
$version = (dotnet --version)
Write-Host "Found version: $version"
$expectedVersion = '$(dotnet)'
Write-Host "Expected version: $expectedVersion"
if ($version) {
if ($version -like $expectedVersion.Replace('x', '*'))
{
Write-Host "The installed version $version matches the expected dotnet version $expectedVersion"
Write-Host "##vso[task.setVariable variable=INSTALL_DOTNET;]$false"
}
else {
Write-Host "The installed version $version doesnt match the expected dotnet version $expectedVersion"
}
}
else {
Write-Host "Dotnet not found"
}
}
catch {
Write-Host "Dotnet not found"
}

task: Cache@2
inputs:
key: '"dotnet" | "$(Agent.OS)" | "$(dotnet)"'
path: $(Agent.ToolsDirectory)/dotnet
cacheHitVar: CACHE_RESTORED
displayName: Cache Dotnet packages
condition: eq(variables['INSTALL_DOTNET'], 'True')

task: UseDotNet@2
displayName: 'Install .NET'
inputs:
version: $(dotnet)
includePreviewVersions: true
installationPath: $(Agent.ToolsDirectory)/dotnet
condition: eq(variables['INSTALL_DOTNET'], 'True')
`

@pulkitaggarwl Any update on this please? Quite a few people, including me, are waiting on this. It's confusing in the current state, as either the doc should be fixed, or the bug acknowledged and fixed. I read this thread, and can't tell if this is a bug or expected behavior. Please clarify.

It is really mind-boggling, that there has not been any fix for this. I mean I could understand it if it would only be affecting and annoying users, but this must be a pretty big resource hog for Microsoft's infrastructure, assuming that there must be thousands of pipelines running with this task each and every day...

@bishal-pdMSFT are there any plans to add this support? It is definitely an issue that lots of folks have to deal with and potentially make workarounds for.

I have a workaround for this issue.
Don't use the UseDotNet@2 task, just create a global.json file before your dotnet build by using Command Line (CMD or Bash).

Don't use dotnet new globaljson --sdk-version 6.0.100 --roll-forward latestFeature for this!

Here is an example:
Command Prompt
echo {"sdk":{"version":"6.0.100","rollForward":"latestFeature","allowPrerelease":false}} > global.json

Bash
echo '{"sdk":{"version":"6.0.100","rollForward":"latestFeature","allowPrerelease":false}}' > global.json

Setting a global.json works if the version you want is definitely installed, but it will break when not installed, this workaround fixes the task's cacheing:
There is a workaround here: https://github.com/actions/runner-images/issues/4884#issuecomment-1013047819

It is still the same for us.
Agent info:
Operating System
Ubuntu
22.04.3
LTS
Runner Image
Image: ubuntu-22.04
Version: 20240107.1.0
Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240107.1/images/ubuntu/Ubuntu2204-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240107.1
Runner Image Provisioner
2.0.321.1
Current image version: '20240107.1.0'

Task
          - task: UseDotNet@2
            inputs:
              packageType: sdk
              version: 8.0.x
              displayName: dotnet install

Logs
##[section]Starting: UseDotNet
==============================================================================
Task         : Use .NET Core
Description  : Acquires a specific version of the .NET Core SDK from the internet or the local cache and adds it to the PATH. Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support.
Version      : 2.232.0
Author       : Microsoft Corporation
Help         : https://aka.ms/AA4xgy0
==============================================================================
Tool to install: .NET Core sdk version 8.0.x.
Found version 8.0.100 in channel 8.0 for user specified version spec: 8.0.x
get-os-distro: Error: Distribution specific OS name and version could not be detected: UName = Linux
Version 8.0.100 was not found in cache.
Getting URL to download .NET Core sdk version: 8.0.100.
Detecting OS platform to find correct download package for the OS.
[command]/home/vsts/work/_tasks/UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6/2.232.0/externals/get-os-distro.sh
Primary:linux-x64
Legacy:-x64
Detected platform (Primary): linux-x64
Detected platform (Legacy): -x64
Downloading: https://download.visualstudio.microsoft.com/download/pr/5226a5fa-8c0b-474f-b79a-8984ad7c5beb/3113ccbf789c9fd29972835f0f334b7a/dotnet-sdk-8.0.100-linux-x64.tar.gz
Extracting downloaded package /home/vsts/work/_temp/7e80ed41-c353-4e64-873e-f580fa4c8360.
Extracting archive
[command]/usr/bin/tar xC /home/vsts/work/_temp/cea2d5f9-0ff5-46c5-86b6-7da4a5a77cd3 -f /home/vsts/work/_temp/7e80ed41-c353-4e64-873e-f580fa4c8360
Successfully installed .NET Core sdk version 8.0.100.
Creating global tool path and pre-pending to PATH.
##[section]Finishing: UseDotNet

Oh right, I just deleted the install step but then obviously that introduces the uncertainty of not guaranteeing the sdk version being installed, makes sense.

Still nothing? This is now nearly 5 years old and could have saved a lot of time and resources...

Still nothing? Wasting time, space and energy...


expose nmslib HNSW method parameters for recall fine-tuning

I have build a hnsw index ( cosine distance ) with about 6M points. Using the same 6M points as test dataset, the 1st neighbor recall is about  0.979 which is high but not sufficient for my application. Setting M,post,efConstruction and efSearch parameters (https://github.com/nmslib/nmslib/blob/master/manual/methods.md) in tensorflow_similarity/search/nmslib_search.py
self._search_index.setQueryTimeParams({'efSearch': 2000})
self._search_index.createIndex({'post': 2,'efConstruction':'2000','M':64},print_progress=show)
results to a 1st neighbor recall of 0.999. These parameters provide a trade off between recall and indexing_time/memory_usage and would be very useful in production systems for recall fine-tuning.

Thanks for sharing the results. We're looking at making the storage and indexing layer more flexible and I'll be sure to include this in the changes.


[bug] Error: Module not found: Can't resolve 'fs' in './node_modules/node-gyp-build'

Is there an existing issue for this?

[x] I have searched the existing issues

RainbowKit Version
1.0.0
wagmi Version
1.0.2
Current Behavior
I encountered an error when running my Next.js project using npm run dev. The error message is as follows:
error - ./node_modules/node-gyp-build/node-gyp-build.js:1:0
Module not found: Can't resolve 'fs'
This error occurs during the execution of the npm run dev command and prevents the successful execution of the Next.js development server.
Expected Behavior
I expected the Next.js project to run smoothly without any errors related to the 'fs' module. I followed the installation guide provided in the documentation, and I anticipated that the development server would start without any issues related to module resolution.
Steps To Reproduce

Create a new Next.js app using the command: npm init @rainbow-me/rainbowkit@latest my-nextjs-app
Navigate to the project directory: cd my-nextjs-app
Start the Next.js development server: npm run dev
Observe the error message mentioned above during the execution of the development server

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

@markkucler Thanks for spotting this. This looks to be a hiccup with the v1 rollout. ethers previously bundled these polyfills, but the new alternative viem that Wagmi v1 has adopted does not. Opened a PR to fix our create-rainbowkit templates so that you won't bump into this in the future. #1236
In the meantime, you can amend your next.config.js like this to polyfill fs and other required Node modules
const nextConfig = {
  reactStrictMode: true,
  webpack: config => {
    config.resolve.fallback = { fs: false, net: false, tls: false };
    return config;
  },
};

✅


Crandall - Include new entries that were QC'd in ngs and assembly datasets + all current FDA BioProject entries into BiosampleMeta (automated process)

All FDA Biosample Entries: https://www.ncbi.nlm.nih.gov/biosample?Db=biosample&DbFrom=bioproject&Cmd=Link&LinkName=bioproject_biosample&LinkReadableName=BioSample&ordinalpos=1&IdsFromResult=231221

This ticket it now irrelevant given that we absorbed your dataset. will close and mark complete.


Delete CompatHelper.yml

This same file exists somewhere else (https://github.com/bcbi/CompatHelper.jl/blob/master/.github/workflows/CompatHelper.yml). No need to have duplicate copies.

bors merge


Add basics to README

Installing
Hello world

if anyone is willing to explain installing and running process in a few words, i can write this
Also I think a installing process for contributors is interesting.


Wiki refactor / cleanup

Changes

Renamed project start pages to 'Overview'
Added new tutorial sections: WSL2, using the terminal, x-forwarding
Refactored ROS tutorials to a single tutorial using docker and snake game

Needs review
There may be typos / broken links, if everyone could take a brief glance that would be awesome.
Testing
Can run locally using docker with docker-compose. Commands in README.
Going forward

Need to expand x-forwarding section to include Mac instructions.
If we don't like the start pages being named 'Overview', then drop a comment and we can revert that.
Need to update arc_tutorials repo to point to wiki

Assuming Docker doesn't work, can we still link the Construct version?

@raghavauppuluri13 Added changes also added another page


Highscore Feature

Assuming the timer is implemented, create a high score feature that allows users to see the high scores of everyone who has locally played the game. Consider game difficulty and user time as potential factors for creating high scores.
Estimated ~250 points

M16 Okay

F16 OK (250 pts)

Fixed in this pull request.


No install target in the project

Please add an install target that installs the headers under include/uWebSockets.

I saw something about a FreeBSD port. You maintain this for FreeBSD?
I have little insights in how FreeBSD does things

I saw something about a FreeBSD port. You maintain this for FreeBSD?

Yes.

I have little insights in how FreeBSD does things

You just need to add a cmake's install target to install the headers into include/uWebSockets.

@yurivict @alexhultman
Please look at #1042
It tries to address this problem
Also companion to PR on usockets: https://github.com/uNetworking/uSockets/pull/100
Possible change as mentioned by @yurivict, current install locations are adhering to unix header standards by not capitalizing the words, should the install locations really be changed to uWebSockets and uSockets?

It works fine. The only difference is that I installed it into include/uWebSocket and you now install it into include/usockets.
Do you think that matching the project name and calling the directory include/uWebSocket would be better?

@yurivict lol, i totally messed that up! It was a remnant from something I copied.
Thanks a lot for mentioning it, I fixed it.
Still not sure if uwebsockets or uWebSockets is the better one.
Currently going without camelcase because header files almost always avoid it.
Strange the the project has most header files with capital letters.

I actually changed it to uWebSockets, it fits with the whole project.

Fixed on master


Added a flag for reversing the QR code color

Added -reverse for make is suitable for terminals with a lighter background and darker foreground.
Wishlist item #12

Thanks @hellozee, it works, I just tested on a white terminal. Do you think you could find a way to generate a halfblock QR as the original code? That would be really great

Actually, it's not even needed to have the reverse flag at all. I think that we can default to the white-border version

@claudiodangelis doing half-blocks distorts the qr code, probably I am doing something wrong or haven't understood the library properly.

Hi @hellozee, I had a look at the original repository and it seems that @mattn, which is also contributor of this repository, has fixed an issue that might be related to the one you are reporting: https://github.com/mdp/qrterminal/pull/6

@claudiodangelis cool, will check then

It doesn't looks like the issue got solved,

Also I dont think making this behaviour default will work

@hellozee what branch or commit did you try?

@mattn I just updated the library by go get -u -v github.com/mdp/qrterminal

Could you please try this?
$ wget https://raw.githubusercontent.com/mattn/qrterminal/76a746e3c8000367e222c87d89204e2f2785ddef/cmd/qr/main.go
$ go run main.go "hello, world"

@mattn okay it looks fine if I run go run main.go "hello, world" but when I do HalfBlocks: true the qr-code gets distorted.

For half blocks the qrConfig should be:
qrConfig := qrterminal.Config{
        HalfBlocks:     true,
        Level:          qrterminal.L,
        Writer:         os.Stdout,
        BlackWhiteChar: qrterminal.BLACK_WHITE,
        BlackChar:      qrterminal.BLACK_BLACK,
        WhiteBlackChar: qrterminal.WHITE_BLACK,
        WhiteChar:      qrterminal.WHITE_WHITE,
}

and for reverse:
qrConfig := qrterminal.Config{
        HalfBlocks:     true,
        Level:          qrterminal.L,
        Writer:         os.Stdout,
        BlackWhiteChar: qrterminal.WHITE_BLACK,
        BlackChar:      qrterminal.WHITE_WHITE,
        WhiteBlackChar: qrterminal.BLACK_WHITE,
        WhiteChar:      qrterminal.BLACK_BLACK,
}

Even with these changes the ability to read the revered half block qr code depends upon the font being used and the qr app. The popular ZXing app has particular difficulty depending upon which font is in use. I have also not had much success with the ZXing app and the reverse on a terminal with a dark background.
What has been much more successful has been changing to using the unicode block characters instead of the ascii ones.
qrConfig := qrterminal.Config{
    HalfBlocks:     true,
    Level:          qrterminal.L,
    Writer:         os.Stdout,
    BlackWhiteChar: "\u001b[37m\u001b[40m\u2584\u001b[0m",
    BlackChar:      "\u001b[30m\u001b[40m\u2588\u001b[0m",
    WhiteBlackChar: "\u001b[30m\u001b[47m\u2585\u001b[0m",
    WhiteChar:      "\u001b[37m\u001b[47m\u2588\u001b[0m",
}

Making this change I have been able to successfully read halfblock qr codes in terminals with dark and light backgrounds without issue or using a reverse mode. If there is a decision to still switch to a reversed color the ZXing app doesn't have an issue recognizing the reversed code on a dark background.
Changing to the unicode characters also allows the qr code to work across a greater number of fonts. Unlike the ascii characters the unicode block characters should be a fixed width on any font that supports them.

Done @claudiodangelis , it will now use half blocks, also the default config is suitable for terminals with lighter background and -reverse when you are using a darker background.

Thanks @tssva for helping me out.

I'm just playing with a suggestion by @tssva, and came up with this solution which probably works on both darker and lighter backgrounds without even using a flag. Can you please try scanning the codes?

It basically uses:

	qrterminal.GenerateWithConfig(fmt.Sprintf("http://%s", listener.Addr().String()),
		qrterminal.Config{
			HalfBlocks:     true,
			Level:          qrterminal.M,
			Writer:         os.Stdout,
			BlackWhiteChar: "\u001b[37m\u001b[40m\u2584\u001b[0m",
			BlackChar:      "\u001b[30m\u001b[40m\u2588\u001b[0m",
			WhiteBlackChar: "\u001b[30m\u001b[47m\u2585\u001b[0m",
			WhiteChar:      "\u001b[37m\u001b[47m\u2588\u001b[0m",
		})

I had to change the level from L (low) to M (medium) to make it work. I tested with my phone camera's built in QR reader, "QR Code Reader" and "ZXing"

Update: I also successfully used it in a terminal whose background color matched the that dark white color used in the second screenshot above, and it worked:
uxterm -bg '#E6E6E6' -fg black

Solution by @hellozee works as well (as per this PR), but I had to explicitly add the -reverse flag to make it work on a darker background.

@claudiodangelis cool, I am also trying that now

I pushed it to a temporary branch, you can test it out with:
git fetch -a
git checkout fixed-color

@claudiodangelis done, implemented that, the approach is kinda awesome, now it should work the same irrespective of terminal backgrounds.

Well what a coincidence

Kudos to @tssva for that! Now there is a minor glitch, the black bar right above the QR, but it's not blocking us.


.NET 8 Upgrade Silenced Errors Fix

Summary of the Pull Request
Silenced bugs in #28655   have been fixed and necessary changes have been made.

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

For CA1863 error in commit https://github.com/microsoft/PowerToys/commit/b23b1279f90c6836748d45c2d54fcb965d2f17e5
https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1863
The method in the example given for the error in this link was applied. Multiple uses in the same file were reduced to one in the last commit

Validation Steps Performed updated.


Add xml response body support

I can help please let me know what are the plans or spec for this, we have our own version of pact-net and we added  some features we can discuss if are aligned to the spec

Hi @zezelazo
Currently we don't really have any plans or spec for supporting XML.
@mefellows @uglyog What are your thoughts on this?

Both the JVM and Rust implementations support XML, so it would be good for the .NET one to support it too.

@uglyog Does that include support for v2/3 with matching rules? If so, I'm assuming that is xpath based?

Why was this closed (something I don't know about :) ?)

@mefellows Nope, still nothing done on this front. Realistically I don't see this happening any time soon and it's not something I really have a need for. Can re-evaluate later if the ruby core gets support for xml.


Fix both logs commands to correctly handle errors

~NB: This PR is a work-in-progress and does not contain unit tests; it has been submitted for a design and high-level code review, so I don't waste a bunch of time if this fix is barking up the wrong tree~
This PR is ready for full review and merging if there are no errors.
- What I did
docker logs is broken, I think, and has been for a long time.  Specifically, it's programmed to multiplex many output streams (stdout and stderr) through one http response, and then demux the HTTP response in the CLI. This multiplexing and demultiplexing is done by docker/docker/pkg/stdcopy, which uses a stdWriter to write and StdCopy to copy to the output streams. StdCopy adds a byte header to the message which describes which stream the log message belongs to (stdout or stderr).
In api/server/router/container/container_routes.go line 108
        select {
        case <-chStarted:
            // The client may be expecting all of the data we're sending to
            // be multiplexed, so send it through OutStream, which will
            // have been set up to handle that if needed.
            fmt.Fprintf(logsConfig.OutStream, "Error running logs job: %v\n", err)
        default:
            return err
        }
    }

But outstream is not a stdWriter, which can handled muxed streams, it's just an https.ResponseWriter, so the error message gets inserted verbatim into the response from the server; no byte header is ever inserted. Then, when the response is demuxed by StdCopy it looks at the first byte of that error that was inserted verbatim and sees that it doesn't match any known output stream (stdout or stderr), and so it returns an error which gets bubbled up to the user and displayed as Unrecognized input header: and the numerical representation of the first byte (69, usually, which is E as in Error: something bad happened)
We haven't caught this until now because errors in logging at that stage are very rare, but they do happen, as evidenced by this google search: https://www.google.com/search?q=unrecognized+input+header
It has become an issue now, however, because docker service logs used the same error-handling code verbatim, and errors in docker service logs are relatively common.
This PR fixes both docker logs and docker service logs to correctly handle errors that occur while logs are streaming.
- How I did it
StdCopy has been modified to accept another stream header, Systemerr, which, when demuxed, causes StdCopy to return an error with whatever was packed into that stream. The container router and service router have both been modified to write to the output stream with a stdwriter muxed to Systemerr.
- How to verify it
Before applying patch, do docker service create --name test whatever && docker service logs test and note the Unrecognized input header: 69 error.
After applying patch, repeat and note that a real error is displayed.
- Description for the changelog

Fixed rare and esoteric docker logs error, and fixed related common (but still esoteric) docker service logs error.
- A picture of a cute animal (not mandatory but encouraged)

Added a test for the new behavior.

This PR is ready for a full review and merge, if there are no deficiencies.

Thank you for the detailed PR description. It would have been difficult to understand the fix without it.

Design LGTM

ping @cpuguy83

Don't forget to squash the commits.

@cpuguy83 @aaronlehmann added changes y'all requested, rebased, and squashed.

LGTM


negative margin on grid .row not flexible enough.

Say I want to have a bottom border on a row that contains two grid columns. You'd think that I could put a style on the row or even wrap the row in a div that has the border on it but it always sticks out 20px to the left due to the negative margin on the .row class.

As it is, it is near impossible to  add top/bottom borders or a background color on an element that wraps both the columns.
Ideally you'd revert to using :first-child to remove the left margin on the span and only use the row for clearing. I'd much prefer a slightly larger css for the added flexibility that this would provide.

Wrapping the .row in another div should work fine.
The reason it uses the negative margin is that using :first-child complicates things quite a lot. It's more specific than the .offset-* classes and thus overrides them. It's not worth the hassle I think, but I'll check it out again.

You are absolutely right. Wrapping the row in another div works fine. I don't know what I was thinking.
nothing to see here, move along


Unable to parse published date

Unable to parse publish dates on following articles:
https://www.chelseafc.com/en/news/2021/06/04/contract-extension-for-thomas-tuchel
https://ameyawdebrah.com/chelsea-star-callum-hudson-odoi-arrives-in-ghana-in-hangs-with-the-stars/
https://www.thehindu.com/entertainment/reviews/vakeel-saab-review-pawan-kalyan-amplifies-no-means-no/article34279888.ece?

@jasmedia we only get data time via meta tag  article:published_time. The sites you mentioned don't provide that value. The thehindu.com uses meta tag publish-date which is not standard.


The Connect dialog doesn't auto display after reopening Storage Explorer without account added

Storage Explorer Version: 1.4.0
Platform/OS Version:  Linux Ubuntu 16.04
Architecture: x64
Build Number: 20180704.1
Commit: 865aab62
Regression From: Not a regression
Steps to Reproduce:

Launch Storage Explorer and sign in with your account.
Remove the added account -> Close Storage Explorer.
Reopen Storage Explorer and check whether the Connect dialog auto displays or not.

Expected Experience:
The Connect dialog auto displays after reopening Storage Explorer.
Actual Experience:
The Connect dialog doesn't auto display after reopening Storage Explorer.

Do you have anything attached? For the dialog to appear you have to have:

No attached accounts or resources
Not be signed in

I tried this again according to the provided states. The Connect dialog appears. Could you help to resolve this issue. Thanks~

Yep!


Control: onChange not working in deep composition Components

I'm having some trouble with getting Control working.
I'm trying to build custom Input controls, that are composed from basic components:
* Input
* Checkbox
* Radio

I have the following setup of a composed component
Component 1:
Boolean
- Select
- - SelectList
- - - Radio (multiple)

Component 2:
Select
- SelectList
- - Radio (multiple)

The Boolean is just a wrapper around Select with some props applied/overridden.
Component 2 works as expected, but Component 1 does not. the rrf/change has no value
I'm using <Control.select> for both.
I've tried manually triggering the supplied onChange in the Boolean Component, ensuring that its sending the right value, but no value comes out in rrf/change
It's really weird, and i've been stuck solving the issue for a while, so if you guys have any input, please let me know.
Update
I think it could have something to do with which component the <Control> actually binds to.
I've console.logged the args and context of handleChange in control-component.js, and i both instances it looks like its bound to Select, and not Boolean.
Update 2
Found the culprit! I've been utilizing a type prop on my elements to choose which underlying component is should render i.e. <Boolean type='radio'> renders a  boolean in radio list form.
That conflicted with the controlProps, as radio and checkbox are read-only as per the isReadOnlyValue method in control-component.js.
So nothing wrong with rff, thankfully, but damn, that was some hard debugging.. :)

That conflicted with the controlProps, as radio and checkbox are read-only as per the isReadOnlyValue method in control-component.js.

Yeah, I need to refactor that to not use "duck-typing" to figure out if a component is an actual input/radio button. Thanks for debugging, though!

No problem.. :)
I've really enjoying this library, it makes form composition a breeze..
Keep up the good work..! 😃


Dynamicly add tab

Hey,
is possible to add dynamicly tab with javascript ?
like
$('#mytab').append('');
Thanks

Hi,
It is possible, you need to append a div to a container, and a LI block
to UL navigation block after plugin initialization.
19.06.2015 15:59, Burak пишет:

Hey,
is possible to add dynamicly tab with javascript ?
like
$('#mytab').append('
');
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/alexchizhovcom/pwstabs/issues/6.

Thanks for fast reply, can you make a example ? It will be very useful if you explain it on your demo part

Im at work so dont have much time now, but you can try this:
// UL - contolls block
var ul = $('ul.pws_tabs_controll');
// Controll block tab
var li = '';
// Add tab to controll block
ul.append(li);
// Our container with tabs
var container = $('.pws_tabs_list');
// Count how many tabs are in the container
var counter = container.find('.pws_tab_single').length;
// Code for new tab
var newTab = 'YOUR CONTENT FOR THE TAB';
// Add tab to container
container.append(newTab);
DO NOT FORGET TO:
change pws_tabs_scale_hide class to the class of the effect you are
using <pws_tabs_EFFECT_hide>
This should work, place this code after you initialize PWSTabs
19.06.2015 16:42, Burak пишет:

Thanks for fast reply, can you make a example ? It will be very useful
if you explain it on your demo part
—
Reply to this email directly or view it on GitHub
https://github.com/alexchizhovcom/pwstabs/issues/6#issuecomment-113485819.

Added method addTab, will be available in the upcoming update


Chan open try

Closes: #543
Description
Main changes:

handler/chan_open_try.rs contains the handler and a few tests for its
handler/verify.rs builds the verification problem for the counter-party chain.
context.rs it adds the processing of a chan_open_try message to the keeper

Other changes:

added a basic validation for the message chan_open_try for the counterparty port_id and channel_id
prototype for verify_channel_state in client_def
one test in ics26_routing/handler.rs

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #545 (b7b41e1) into master (b1b37f5) will increase coverage by 29.1%.
The diff coverage is 68.9%.

@@            Coverage Diff            @@
##           master    #545      +/-   ##
=========================================
+ Coverage    13.6%   42.8%   +29.1%
=========================================
  Files          69     136      +67
  Lines        3752    8704    +4952
  Branches     1374       0    -1374
=========================================
+ Hits          513    3729    +3216
- Misses       2618    4975    +2357
+ Partials      621       0     -621

Impacted Files
Coverage Δ

...application/ics20_fungible_token_transfer/error.rs
0.0% <0.0%> (ø)

...pplication/ics20_fungible_token_transfer/events.rs
0.0% <ø> (ø)

...ion/ics20_fungible_token_transfer/msgs/transfer.rs
0.0% <0.0%> (ø)

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/error.rs
100.0% <ø> (ø)

modules/src/ics02_client/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
100.0% <ø> (+66.6%)
:arrow_up:

modules/src/ics03_connection/events.rs
0.0% <0.0%> (ø)

modules/src/ics04_channel/error.rs
100.0% <ø> (+75.0%)
:arrow_up:

... and 235 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #545 (b7b41e1) into master (b1b37f5) will increase coverage by 29.1%.
The diff coverage is 68.9%.

@@            Coverage Diff            @@
##           master    #545      +/-   ##
=========================================
+ Coverage    13.6%   42.8%   +29.1%
=========================================
  Files          69     136      +67
  Lines        3752    8704    +4952
  Branches     1374       0    -1374
=========================================
+ Hits          513    3729    +3216
- Misses       2618    4975    +2357
+ Partials      621       0     -621

Impacted Files
Coverage Δ

...application/ics20_fungible_token_transfer/error.rs
0.0% <0.0%> (ø)

...pplication/ics20_fungible_token_transfer/events.rs
0.0% <ø> (ø)

...ion/ics20_fungible_token_transfer/msgs/transfer.rs
0.0% <0.0%> (ø)

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/error.rs
100.0% <ø> (ø)

modules/src/ics02_client/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
100.0% <ø> (+66.6%)
:arrow_up:

modules/src/ics03_connection/events.rs
0.0% <0.0%> (ø)

modules/src/ics04_channel/error.rs
100.0% <ø> (+75.0%)
:arrow_up:

... and 235 more

Continue to review full report at Codecov.

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


Update completed endpoint with new job group format

The latest change #324 (upstream from head) introduced a stronger job group concept which included a fairly sizeable migration, this new structure broke our /completed endpoint which we use for Hail / Seqr aggregation.
Rewrite the function to align back with the original function it was modelled off:
https://github.com/populationgenomics/hail/blob/01714cc51f092304eb7b4de47bdc2c7c192b13cd/batch/batch/front_end/front_end.py#L1714-L1739
I haven't tested the endpoint, but I've tested the query and it works.
Columns selected:

id
userdata
user
billing_project
attributes
callback
deleted
n_jobs
time_created
time_completed
msec_mcpu
token
state
format_version
time_closed
cancel_after_n_failures
migrated_batch
cancelled
n_completed
n_succeeded
n_failed
n_cancelled
cost
cost_breakdown

Yeah definitely haha, I want to keep it as close to the referenced code in this case so I can find it next time I break it :)


STOR-1170: Rebase to upstream v1.5.1

Upstream diff:
https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/compare/v1.5.1...tsmetana:rebase-v1.5.1

/lgtm
/approve

@tsmetana can you please add some highlights from changelog for QE and us in general? Like https://github.com/openshift/aws-ebs-csi-driver/pull/222

/retitle OCPBUGS-12605: STOR-1170: Rebase to upstream v1.5.1


Code.json - Update code.json to include required fields

Issue Report
Code.json - Update code.json to include required fields
Description
Update code.json to include both required fields and our optional object fields

Duplicate, #124


Using train, val data

Hi ,
I read your tutorials and I don't understand the relation between x, y, x_train, y_train, x_val and y_val in your framework.
For example, here:
https://nbviewer.jupyter.org/github/autonomio/talos/blob/master/examples/A Very Short Introduction to Hyperparameter Optimization of Keras Models with Talos.ipynb
The function:
def diabetes(x_train, y_train, x_val, y_val, params):
get the arguments : x_train, y_train, x_val, y_val
But uses x,y in the .fit method within it.
Moreover, in the line
t = talos.Scan(x=x, y=y, params=p, model=diabetes, experiment_name='diabetes')
What are x,y?
Are they x_train, y_train?

You should not mix two different concepts. One concept is the input mode def diabetes(...) which is an input to Scan(). x and y in Scan() are automatically handled to become x_train, y_train and so on in the input model.
Closing here. Feel free to open new issue if anything.


Feature Request: Better Hiding of plugin queries and task ids

So this was something that always bothered me about taskwiki as well. While i get that queries for lists and task ids are the core of the plugin, and legitimately the thing that makes a plugin like this useful. I think it would be absolutely amazing if these could get hidden in the rendered document instead of fussing up the page with all the code. Thankfully markdown has a comment feature, and all the data could be wrapped in a comment tag!
So what I'm envisioning, instead of this:
##Header $query{+PENDING}

##Header <!-- $query{+PENDING} -->

Ideally this would be for any custom tag that this plugin implements.

Hey @fullstopslash, absolutely love this. It also bothers me when I tried to read them in Obsidian but I didn't think of using comment :'(. This is likely to be the next feature.

That's so exciting! Thank you! So for instance, markdownlint handles it like this:
Some text <!-- markdownlint-disable-line MD003 -->

You could do it any number of ways, but perhaps it'd be nice if the comment also gave an indication as to what tool was acting upon it!

My current plan is to add something like https://github.com/huantrinh1802/m_taskwarrior_d.nvim/pull/64
We will have:

comment_prefix = "<!--"
comment_suffix = "-->"

I also plan to extend the pattern for concealing to support the comment_*

so it will look nice on Neovim and markdown preview


Add alt text to images

Unlabeled graphic on homepage. Just says "home page graphic." Add proper alt text to the image.
Verify other images have alt text as well.
From old pivotal ticket: https://www.pivotaltracker.com/story/show/131334291

Just focus on non org-admin/super-admin pages for this first pass

added alt text to the few images throughout the site.
Also added Aria tags to all of the fontawesome icons per the instructions found here: http://fontawesome.io/accessibility/

Closing this issue for now pending next round of accessibility testing.


Enable chat adapter with env variable

slack.coffee and hipchat.coffee are unused and burried in the docs folder. They could be useful just as they are.
With this new HUBOT_DEPLOY_ADAPTER env var, it is easier to leverage them

So this will only enable provided adapters for slack and hipchat, and there is no way to add custom adapters via this env var. I think this should be stated clearly.
Maybe using HUBOT_DEPLOY_BUILTIN_ADAPTER?

It would actually work with whatever xyz adapter, provided you implement a xyz.coffee file in /src/adapters

But in src/adapters of this package only, right?

Correct

any update on this ?


[11.x] Unserialize collection with relations

I am not sure if this is like this for purpose or not, but collection is serialized with relations, but the relations are not retrieved when collection is restored.

But what if your relationship had clauses attached when passed in...
User::with(['posts' => fn($query) => $query->where('approved', true))->get();

Then, in your queue, with this proposed change, you would end up loading all posts, approved or not.


Remove DMFile after upload S3

What problem does this PR solve?
Issue Number: ref #6827
What is changed and how it works?

DMFile switching to S3 and removing local DMFile after upload S3 successfully.
If S3 enabled, restore from S3.

Check List
Tests

[x] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)

./tiflash dtworkload --testing_type=daily_perf --verify_round=10 --s3_bucket=dtw --s3_endpoint=<IP_ADDRESS>:9000 --s3_access_key_id=minioadmin --s3_secret_access_key=minioadmin --ps_run_mode=4 --log_level=debug

[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/rebuild

/run-integration-test

/run-integration-test


Update Drupal.gitignore

Reasons for making this change:
This template is also valid for Drupal 9. As a matter of fact, when starting new projects you should use Drupal 9. And 8 is only supported until November 2021.
Links to documentation supporting these rule changes:
https://www.drupal.org/project/drupal

Would it be preferred to remove the version number altogether? https://github.com/github/gitignore#versioned-templates

Drupal 7 and earlier versions has different needs for the .gitignore than Drupal 8 and later. So maybe it should say
gitignore template for Drupal 8 and later
or
gitignore template for version 8 and later of the Drupal 8 project
or similar.

gitignore template for Drupal 8 and later

This is preferred. Is it also safe to assume that new Drupal projects will be Drupal 8 or later?

Linking other Drupal PRs https://github.com/github/gitignore/pull/3386

the structure is expected to be roughly the same in 8 vs 9, so the comment change should suffice
but perhaps #3914 should be reworked to consider #3914 and update paths is there are any official changes


Add micro service to do metadata ingestion

I would like to create a micro service that runs in Spring Boot but can be used with both HAF and Tempus Cloud. Work with Akshay and Jay on how best to design this. However, the micro service will take the configuration information that was created during the data source creation process and connect to an external data store and push the metadata To the tempus Metadata controller API with System level access.

Merged in Master of HAF.


Turn on linspace and arange tests.

PR #115 with the tests broken so nothing was actually tested. This turns the tests on and fixes bugs that the tests uncovered. However there are issues with dask.array.arange matching numpy.arange in edge cases that are not specified or supported by NumPy. Tests where these edge cases come up were marked as expected failures.
The edge cases come up when arange is passed a floating point step argument. The step argument is added repeatedly, which might result in points near the end of the interval being included when they should not.

Seems fine to me.  Merging soon if no comment.


[mtv] Extract duration from each playlist item

RSS used instead of manifest files because it's exact to the millisecond
with the video I tested while in manifest it's only exact to the second.

OK, I assume it's instead of the float since if either .find or ´.attrib` fail it'd error out. Now it just outputs null.


Markdown formatting fix

Running at this here - https://dart-review.googlesource.com/c/sdk/+/60080 CC @MichaelRFairhurst


Retry policies implementation

This PR introduces retry policies.
Retry Policies can have following attributes:

First Retry Interval
Max Number Of Attempts
Backoff Coefficient
Max Retry Interval
Retry Timeout

Once this PR is merged, would need to incorporate Docs also for Retry Policy and attach the Design approach taken for it.

One thing I'm concerned about with this PR is whether it correctly handles cases where retry policies are mixed with when_all and when_any use cases. Can we add some test cases that cover these scenarios?

now, I have added tests for when_any and when_all with retryable task.

@cgillum Please review this PR. It has been a quite stretched PR time-wise.
I have incorporated review comments.


Random least loaded provisioning strategy

When Jenkins is configured with more than 10 DockerCloud clouds, yet-another-docker-plugin tends to struggle to provision agents.  Additionally, the first configured cloud is always heavily utilized and the other clouds are not so much.
This proposed change is meant to randomize the selected list of docker clouds and to provision from the least loaded clouds first.  I have thoroughly tested this behavior.
Scenario
Let's say you have two DockerCloud clouds configured (cloud-01 and cloud-02).  Each cloud has a maximum capacity of 2 for the same DockerSlaveTemplate.
Now to describe the behavior when two builds populate the Jenkins Queue.
Old behavior
The old behavior will fill up cloud-01 with both builds.  cloud-02 will remain unused.  cloud-01 will always be exercised and cloud-02 will process fewer builds.
New behavior
The new behavior proposed in this change will fill up both cloud-01 and cloud-02.  That's because after the first build is addressed the least loaded cloud is selected.
The selection of least loaded cloud will be random across cloud-01 and cloud-02 so over time the serviced build load will be distributed across both clouds more evenly.
Test this in your own environment
See pre-merge build: https://github.com/samrocketman/yet-another-docker-plugin/releases/tag/0.1.0-rc38-samrocketman-rc1

The build "error" is not descriptive enough.  I don't know how to fix the build because findbugs is not describing the issue.

Codecov Report

Merging #167 into master will decrease coverage by 0.19%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master     #167     +/-   ##
===========================================
- Coverage     20.51%   20.32%   -0.2%
  Complexity      205      205
===========================================
  Files            56       57      +1
  Lines          2345     2367     +22
  Branches        207      211      +4
===========================================
  Hits            481      481
- Misses         1809     1831     +22
  Partials         55       55

Impacted Files
Coverage Δ
Complexity Δ

...thub/kostyasha/yad/DockerProvisioningStrategy.java
27.14% <0%> (-5.07%)
7 <0> (ø)

...kostyasha/yad/utils/DockerCloudLoadComparator.java
0% <0%> (ø)
0 <0> (?)

...om/github/kostyasha/yad/utils/DockerFunctions.java
30% <0%> (-12.86%)
3 <0> (ø)

Continue to review full report at Codecov.

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

What i'm thinking is that DockerProvisioningStrategy may really have configurable strategies i.e. it can roundrobin clouds by calling provisioning with excessWorkload = 1 (even do parallel start-up with multithreading and synchronisations because now jenkins gets the list of future nodes only at once). Also it would be good to have old strategy...

Also it would be good to have old strategy...

Does this mean you likely won't accept this PR because it is changing the old strategy?  From my experience the old strategy is generally a problem when large amounts of clouds are configured.
In general, round robin is not very good performance because what if one of the DockerClouds becomes unhealthy?  Round robin will still try to provision nodes on it.  Additionally, the old strategy will continue try to provision nodes on an unhealthy DockerCloud so it's also not good.
I created this least loaded/random provisioning strategy as a compromise.  A compromise between wanting something like round robin but better utilizing available infrastructure based on load.  The random shuffle ensures that your last configured DockerCloud has an equal chance of being used as your first DockerCloud.  With the old strategy only the first DockerCloud would always be used.

even do parallel start-up with multithreading and synchronisations because now jenkins gets the list of future nodes only at once

I agree, this is definitely possible.
I consider the old strategy a bug which is why I opened this PR to improve yet-another-docker-plugin.

For what its worth I agree that he current strategy of fill up the first cloud until the max number before moving to the second cloud is a bug... It does not work well for sporadic spikes (due to low level code commits)  If too many builds get triggered at once the amount of nodes being requested can overwhelm my dockerhost and I find myself having to adjust the order of my clouds when one is spinning up nodes as fast as it can yet none of the nodes get used.  I haven't been able to figure out why I sometimes see that nodes are spun up then thrown away before having a job run on them, I suspect some sort of race condition (since I only see it during sudden spikes in demand) but my hope is that if the sudden burst of jobs is spread across my docker hosts that no one node would be overwhelmed as easily.

@dsmorse I've uploaded a pre-release build which you can use to test this in your own environment.  Having more people test this is a good thing.  Download the HPI from https://github.com/samrocketman/yet-another-docker-plugin/releases/tag/0.1.0-SNAPSHOT-samrocketman-rc1
I'm working up adding more unit tests to satisfy the codecov requirements.

For what its worth I agree that he current strategy of fill up the first cloud until the max number before moving to the second cloud is a bug... It

Jenkins is bug by design. If something doesn't fit to you it doesn't mean it bug. Strategy should be strategy and have ability to choose strategies. Changing behaviours for already working solutions is bad.
We need find the place that should extract old and new logic with ability to choose it.

Does this mean you likely won't accept this PR because it is changing the old strategy? From my experience the old strategy is a problem when large amounts of clouds are configured.

I would better spend time on ending tests for classic swarm in docker-java branch (few tests need to be addressed). But if it could be choosable, then why not.
@samrocketman would like to hear idea of calling .provision() with 1 as load request. That may allow in future tune This strategy place. With right parallelisation and synchronisation for i.e. load 3 request it should be possible to speed-up build time.
One more idea is that provisioning choosing logic could be placed in "proxy" Cloud class that could contain other Cloud classes.

Changing behaviours for already working solutions is bad.

For the record, I changed the strategy because it doesn't work.  Configure more than 10 clouds and view the logs.  It iterates through full clouds causing severe delay in provisioning.  This patch alone speeds it up by causing no such delay.
Why would you want to choose the old strategy?  I see no benefit in keeping it.  There's no need to add yet another option.

Will try to look at weekend how to make it as choosable extension.

Swarm in docker-java may become available soon also, afair classic swarm has some strategies also.

We've tested this plugin internally and it is a much needed feature.
@KostyaSha what would it take to get this merged?
I also agree with @samrocketman the current strategy does seem to be "broken". If I have two clouds that both offer a template with the same label the second cloud will never provision a slave. I cant see a circumstance where that would ever be preferred

I rebased my PR on the latest master.

@KostyaSha to be clear; my strategy doesn't change much about how nodes are provisioned with the current strategy.  It simply shuffles up for (DockerCloud dockerCloud : getDockerClouds()) to order the clouds so that certain clouds are chosen first before others.

@KostyaSha to be clear; my strategy doesn't change much about how nodes are provisioned with the current strategy. It simply shuffles up for (DockerCloud dockerCloud : getDockerClouds()) to order the clouds so that certain clouds are chosen first before others.

I see, one of suggestions was create GlobalConfiguration option with strategy switch for DockerProvisioningStrategy class because it "global" class for all DockerClouds. I really use current strategy so i need some switch.

for what it's worth we have been running this in production for 2 weeks now. It works wonderfully. @KostyaSha what do you need to merge this in? A toggle to choose between random and the old behavior? Proper round robin rather than random?
My java is a bit rusty but i can certainly give it a go

I can also give @cpoole write access to my project for collaboration.

@KostyaSha what do you need to merge this in? A toggle to choose between random and the old behavior? Proper round robin rather than random?

Just make it as extension/enum or switch between two. Existing and new. That's all. Because it global setting feel free to add global setting.

@cpoole I have invited you to collaborate on my branch.  Please accept the invite -> https://github.com/samrocketman/yet-another-docker-plugin/invitations

thanks @samrocketman I'll take a stab at it this weekend

I've enabled branch protection so just add on to it with new commits.  I'm also willing to test your changes as well.

Rebased on latest master so it's ready for you to work.

@cpoole I have invited you to collaborate on my branch. Please accept the invite -> https://github.com/samrocketman/yet-another-docker-plugin/invitations

You may just base on Sam's branch and PR your variant, in the nearest time i will be fixing redundant Queue lock that come from durable-task-plugin that i predicted in 2016 :(

Hi All,
Is there an ETA on this? We have exactly the same issues and the RC addresses and resolves them well. I would be keen to implement YADP and this is functionality that raises it above other implementation options

I believe #209 addresses all concerns and when that is merged this issue will automatically close. @KostyaSha

@ShaunDAdams sorry, lost notifications.

Thanks this is working a treat. One question - how do you set the cloudOrder via a Groovy script in the Jenkins Console? (I'm not a Java developer - sorry for a potential obvious question)

If you're using the random strategy then it doesn't matter the could order.  They'll get shuffled and chosen from the shuffled list of least loaded clouds.

@ShaunDAdams Taking my script at https://github.com/samrocketman/jenkins-bootstrap-shared/blob/afac8b113bd8876cae35a462ac846938ab91fb16/scripts/configure-yadocker-cloud.groovy#L403-L411
import com.github.kostyasha.yad.DockerGlobalConfiguration
import com.github.kostyasha.yad.other.cloudorder.RandomLeastLoadedDockerCloudOrder

//configure global docker settings
DockerGlobalConfiguration docker_global = Jenkins.instance.getExtensionList(DockerGlobalConfiguration)[0]
if(!docker_global.cloudOrder || docker_global.cloudOrder.class.simpleName != 'RandomLeastLoadedDockerCloudOrder') {
    docker_global.cloudOrder = new RandomLeastLoadedDockerCloudOrder()
    docker_global.save()
    println 'Configured random least loaded cloud provisioning strategy for docker.'
} else {
    println 'Nothing changed.  Already using random least loaded provisioning strategy for docker.'
}

I just created it tonight and haven't had the chance to contribute it back to this plugin.


Update OpenFaaS app to the latest version

This issue is a:

[ ] Bug Report
[x] Enhancement suggestion
[ ] Feature request

If the issue concerns an existing Marketplace application, please tag the maintainer of the application (found in manifest.yaml) below:
Enhancement suggestions / feature requests
Currently, we have OpenFaaS version 0.18.0 installed by Civo marketplace as a newer version 0.27.0 is available, so it needs to be updated to the newer version. We kindly request an update to the latest version of OpenFaaS on the Civo marketplace to ensure that we have access to the most recent features and improvements.
@alexellis I request you to please take a look into this.

Hi @aakashnagpal4567 thanks for the ping. Civo manage these apps so I'd suggest pinging someone over there like @kaihoffman who may be in a better place to take a look and fully test the change.
Alex


Integrate boostrap-validator with chosen jQuery plugin

Hello,
I'am using your library with different forms. In parallel I also employ chosen jQuery plugin v1.1.0 for my selects, there is a way to validate fields like this with your library ?

also with the bootstrap-select plugin it is not working...

Ok, no solution until now ?

Would also like to use with Selectize.js I found an example of using a different validation script with Selectize but I'd like to use this bootstrap validator.

Hi, anyone can solve it? i want to use a multiple select but i can not validate, thanks.

Adding this just after loading the validator script worked for me:
$.fn.validator.Constructor.INPUT_SELECTOR = ':input:not([type="submit"], button):enabled';

Same problem with selectize...

invisible elements are no longer ignored by the validator in v0.11.0

This still isn't perfect. For some reason it works on an initial pageload, but then subsequently refreshing the page causes validation errors to not populate. The validation itself still works, just the errors fail to appear. I'm having to put a 500ms setTimeout around all my chosen elements in order to get validation to work.


Example for idiomatic menu bar ?

Hi, Since GTK4 has changed the way that menu bars should be created I'm quite lost on how it's supposed to work on gtk4-rs, is it PopoverMenuBar ? Could someone make an example on how to do it?

More examples are always appreciated, if someone wants to send a PR adding one for how to use PopoverMenu or whatever other APIs feel free to do so.


As I designer I need a date picker as part of EDS.

[x] Create component in Figma
[x] Add to component status (under construction)
[x] QA Figma component
[x] Create documentation
[x] QA documentation
[x] Update component status
[x] Create issue for development #476

@BeckyBrekke Do you have time to do QA of this?

Sure!

Done


Better material assignment for compound objects (IfcWindow)

First of all, thanks for the absolut amazing work. Is there any way to sperate an object like a window? So that afterwards we have a frame and the window glas als separate objects?

Thanks for sharing your work. Have you continued this work (I presume related to your PhD) ?
Is there some way to share your wrapping project. I'm involved in BIM research too and it would be very useful form me.
BN

@tom2drake: only if it's defined like that in the IFC file. I'm currently assigning the material to the whole IfcWindow. It would be possible with IfcBuildingProxyElements.
@berry4u:
The library uses IfcEngine which is commercial. I have to rework this to XBim in the near future. So this project is not dead, I'm just occupied with my new job at the moment ;)

Hi, thank you for your amazing work. I just wanted to know what the status is of the issues and tasks that are yet to be completed?

Well, XBim and Unity together seems to be a trainwreck. I've tested and it had several issues.
Unity Reflect should bring support for Autodesk Revit:  https://blogs.unity3d.com/2019/06/05/unity-reflect-bim-to-real-time-3d-in-one-click-for-better-design-decisions/
For IFC files, I'll write a webservice parser. That way XBim's .NET stuff and unity's won't get confused by each other.

Aah, so will you be implementing XBim library for the Unity-IFCEngine Project such that you can create a web-application of the build using a .NET application correct? Or am I slight mistaken?

Nah, it will be two applications. XBim .NET with a webservice and Unity-IFCEngine calling the webservice for geometry and metadata.


[RFC] Rotating backups

This is a possible solution for #4. I tried to keep it as simple as possible.
There is a new Destination wrapper called RotatedDestinaion. This destination extends the push() method to first delete any existing backups found via a RotateStrategy.
ping @kachkaev

Hi @kbond!
This looks very promising! I'd be keen to test this at some point after you share the config example!

Do you think it would work for your scenario? I don't personally use rotation and don't really have a need for it.
For the config, I'm thinking something like this:
zenstruck_backup:
    destinations:
        s3:
            s3cmd:
                bucket: "s3://foobar/backups"
            rotate:
                max_size: '1G'
                max_count: 10

FYI - you can test this without waiting for the bundle's config to be updated by manually configuring the destination:
services:
    my_destination:
        class: Zenstruck\Backup\Destination\RotatedDestination
        arguments: [@my_destination_child, @my_destination_strategy]
        tags:
            - { name: zenstruck_backup.destination }

    my_destination_child:
        class: Zenstruck\Backup\Destination\StreamDestination
        arguments: [sample_destination, '/home/kbond/backups'] # note the first argument

    my_destination_strategy:
        class: Zenstruck\Backup\RotateStrategy\MaxCountRotateStrategy
        arguments: [5]

zenstruck_backup:
    sources: # ...
    namers: # ...
    processors: # ...
    profiles:
        my_profile:
            destinations: [sample_destination] # this matches the first argument of my_destination_child

I just gave it a test and it worked as expected for me.

Makes perfect sense, I also like the max_size option.
My scenario is a bit different though: the count is not limited, and the rotating files are not necessary deleted starting from the oldest. The config would look somewhat like this:
zenstruck_backup:
    destinations:
        s3:
            s3cmd:
                bucket: "s3://foobar/backups"
            rotate:
                retain:
                    -
                        frequency: "all"
                        max_age: "5 minutes"
                    -
                        frequency: "10 minutes"
                        max_age: "1 hour"
                    -
                        frequency: "1 hour"
                        max_age: "1 day"
                    -
                        frequency: "1 day"
                        max_age: "7 days"
                    -
                        frequency: "1 week"
                        max_age: "6 weeks"
                    -
                        frequency: "1 month"
                        # no max_age = for ever

Both max_size and max_count can work perfectly with retain. They will just work as additional caps. By default retain is
-
    frequency: "all"

(all backups are retained forever until max_size or max_count are hit. then the oldest backups are removed)

In your above example, are all the files in the same directory?

The .zip archives are in one directory, yes. The cool thing about applying the uneven retain strategy is that you never end up with an extremely large list of files. Backing up turns into a "set up a forget" thing. If something has totally screwed up, let's say, 5 days ago without me noticing it, I'll never end up having just 10 corrupt archives, because all of them were generated today :–)

I'm probably going to need some sample code. Can what you want be done within the constraints of the RotateStrategy interface?

Yeah, I'm pretty sure that's possible! retain can be passed to the constructor and parsed. So if values are malformed or missing, an exception will be thrown right away. When you call getBackupsToRemove(), backups will be grouped into bins according to getCreatedAt() and the config, then the bins will be filtered, and thus it will be possible to know what files should remain. Then it's just a matter of getting a diff of two arrays.
You chaining mechanism will make it really easy to combine retain with two other params, it's just important to execute this filtering before the remaining ones. This is because when we reach the count or the size limit, it may be more beneficial to remove a backup that's 1.1 days old rather the one that's been in the folder for 6 months.
I'm too tired right now, but I'll have a look at all this next week if you don't lose patience and manage to write some code before then :–)

Cool! No worries, I'm not in any kind of rush for this.

@kachkaev any update on your RetainRotateStrategy? As long as it is possible to add your logic within the constraints of the current implementation I can merge this and we can add later. I just want to make sure it is possible before "locking in" this logic.

Hi @kbond. Sorry, none yet. Is it OK if I try this weekend? I can let you know what's up closer to it.

Sure, no problem!

Hi @kbond,
Have a look at #8. The name of the strategy is progressive instead of retain. I haven't implemented any phpunit tests unfortunately – won't have any time on these I'm afraid.
Let me know what you think of the functionality. Hope it makes sense.

I am going to merge this unless there are any objections. Your strategy can certainly be achieved within the confines of this implementation.

Great!


allow selection of database name

I close this ticket because I am not quite sure if the MongoDB solution will be the final one ;)


Vincent ugdg

Pull Request Test Coverage Report for Build 465

2 of 6 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 74.586%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/planner/ui/WelcomePanel.java
2
6
33.33%

Totals

Change from base Build 464:
0.3%

Covered Lines:
2119

Relevant Lines:
2841

💛  - Coveralls


AttributeError: module 'flax.core' has no attribute 'pop'

I need "pop" to use "train_lib_deprecated/train_utils.py"
but i cant find it

Hi, I found pop by debugging flax.
Change all flax.core.pop to flax.core.FrozenDict.pop :)

Hi, I found "pop" by debugging flax. Change all flax.core.pop in "train_lib_deprecated/train_utils.py" to flax.core.FrozenDict.pop :)

thank u，this question has  been resolved


chore: replace clean transaction with sequence of promises, increased beforeEach timeout

Attempt to unlock CI.

(Now better no merges from main any more as that disables these tests)

Note: the test is skipped on main since https://github.com/prisma/prisma/pull/15565 because it was blocking the release.
After the release: We need to continue this PR here to make the test more robust and unskip it.

Sorry for the mess here, everything is back to normal.
Note I created a PR to checl that only unskip the test to see the current status and it fails in Buildkite https://github.com/prisma/prisma/pull/15575

Let’s consider that most likely increasing timeouts in those tests is just a temporary patch for a broader issue elsewhere: too many concurrent Prisma clients are competing for resources, resulting in transactions (e.g., the one used for cleaning the db tables) taking ages