Search text on Autocomplete now reflects initialValues and values cor…

…rectly.
Autocomplete values are saved as strings in redux-form, so the search text should rely on the value's type (which should almost always be a string) instead of just on whether datasourceConfig is set or not. This should fix #86.

Codecov Report

Merging #140 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #140   +/-   ##
=======================================
  Coverage   78.37%   78.37%
=======================================
  Files          11       11
  Lines          37       37
=======================================
  Hits           29       29
  Misses          8        8

Impacted Files
Coverage Δ

src/AutoComplete.js
50% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

I need to be able to populate my AutoComplete field with an initial value (display it as string in the component, but store value as it's set in the dataSource).
It seems this is the PR that would solve this.  What is preventing this from being merged in? I'd be happy to help if needed.

I need this too, do you need any help getting this merged?  It seems like a big oversight for the component in the first place.

Any updates on this??

Can someone merge this or offer a branch with beta-alpha-next features ?

This has been worked out with latest release of RFMUI.


Passing argument to the success callback

Thanks for putting this extension together!
I want to use it in conjunction with the cordova-plugin-save-image plugin to write a photo that I take in my app to a gallery. The natural way to do this seems to be
  pictureTakenHandler(function(photoData){
    glPhotoData = photoData;
    permissions.hasPermission(permissions.WRITE_EXTERNAL_STORAGE, storageAllowedHandler, null);
  });

and then use storageAllowedHandler to write the photo. But it seems that the prototype to the success callback takes only one argument, the status value arising from permissions.hasPermission. How can I pass photoData to the success callback? Or is there a different approach you recommend?

Use closures, for example using classes:
var app = {

    takePhoto: function (){
        // ...
    },

    glPhotoData: null,

    pictureTakenHandler: function (photo) {
        app.glPhotoData = photo;
        permissions.hasPermission( permissions.WRITE_EXTERNAL_STORAGE, app.storageAllowedHandler, null);
    },

    storageAllowedHandler: function(status) {

        if ( status.hasPermission ) {
            show(app.glPhotoData);
        }
    }
}
app.takePhoto();


Error fetching log event: Query timeout exceeded. Consider reducing your block range

Error
Error:
   0: Error fetching log event: (code: -32000, message: Query timeout exceeded. Consider reducing your block range., data: None)
   1: (code: -32000, message: Query timeout exceeded. Consider reducing your block range., data: None)

Metadata

key
value

version
signup-sequencer 0.1.0

c7bef90822ba4e783c88b11c4a0c0e2ea48235de 2022-11-10

x86_64-unknown-linux-musl 2022-11-10

Remco Bloemen remco@worldcoin.org:Lucas Ege<EMAIL_ADDRESS>

https://github.com/worldcoin/signup-sequencer

Template for a Rust CLI tool

SpanTrace

SpanTrace:
   0: signup_sequencer::app::process_events
             at src/app.rs:303
   1: signup_sequencer::app::App::new
           with options=Options { ethereum: Options { ethereum_provider: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("polygon-mainnet.g.alchemy.com")), port: None, path: "/v2/ZBjU5pzlBWQQPftvl26hJ4cP1VaBrOGq", query: None, fragment: None }, signing_key: 0x5f6aa37e247a09852d2b1c1b74d797cd01f83a99d4c3be3692257916947c5c4b, max_log_blocks: 10000, min_max_fee: 1250.0, min_priority_fee: 31.0, priority_fee_multiplier_percentage: 200, send_timeout: 30, mine_timeout: 300 }, contracts: Options { semaphore_address: 0xd81de4bcef43840a2883e5730d014630ea6b7c4a, group_id: 1, create_group_depth: None, initial_leaf: 0x0000000000000000000000000000000000000000000000000000000000000000_U256 }, starting_block: 27829300, lock_timeout: 120 }
             at src/app.rs:96

This happens with some frequency.
https://app.datadoghq.com/logs?query=env%3Aprod service%3Asignup-sequencer "Error fetching log event"&cols=host%2Cservice&index=&messageDisplay=inline&saved-view-id=1320295&stream_sort=time%2Cdesc&viz=stream&from_ts=1668050255358&to_ts=1668136655358&live=true
We have already lowered it several times https://github.com/worldcoin/signup-sequencer/blob/c7bef90822ba4e783c88b11c4a0c0e2ea48235de/.github/workflows/build-test-deploy.yml#L405

Lowering it to 2k in #275 . Alchemy uses 2k as a no-limits doc minimum for reposnse size. Our problem is query time. Let's hope this works.

This can result in many more requests. The fixes for that are #240 and #243

#275 mitigated the issue.


Improve KLM docs with findings/questions from recent onboarding

Description

Architecture

maybe rework the diagram

align the multiples, e.g.: (for me, the multiples where a bit confusing and I assumed there is one super big KymaCR in KCP that describes all SKR clusters)

SKRs being multiples
KymaCR in KCP being multiple whereas in SKR being single
ManifestCRs in KCP being multiples

consider using TAM block diagram notation

it is heavily used and understood within SAP, and should also be rather clear to the outside

add the "outside" access to KCP

e.g., actor access to KymaCR in KCP (for me, it was for instance not clear from the document how a Kyma installation is removed again)

phrase "manages operators free of dependency trees" may need further explanation
phrase "rendered module" may need further explanation

ModuleTemplate Custom Resource

starts with "contains 3 main parts that are used to initialize and resolve modules", but then lists all spec attributes without further reference of what the 3 main parts are

Kyma Custom Resource

phrase "contains 3 fields that are together used to declare the desired state of a cluster" with the following 2 points list (even though 3 fields are mentioned) is a bit confusing

Controllers

section on Remote Synchronization may be outdated

understood from Jay that by now, KCP KymaCR only includes the "initial spec" and up to date status; for module installation, the source of through is spec from SKR KymaCR
mentioned ReplaceWithVirtualKyma doesn't seem to exist in sync handlers any more

Control Plane Quick Start

step 3 in provisioning uses outdated link

new location seems to be https://raw.githubusercontent.com/prometheus-community/helm-charts/main/charts/kube-prometheus-stack/charts/crds/crds/crd-servicemonitors.yaml

link to kustomization in Deploy Lifecycle Manager goes to 404 when called directly, but still seems to work

browser accessible link seems to be https://github.com/kyma-project/lifecycle-manager/tree/main/config/control-plane, but specifying that one fails
it may justify a small note/explanation

Reasons

keep the docs nice and shiny

Assignees
@kyma-project/technical-writers
Attachments

Please align with THE @jeremyharisch and THE @c-pius on the diagram. 🙂


Add French locales

Hi,
This PR adds French translations.
Thanks for you package.
Karel

Thank you @shaffe-fr!
Will create a release for this asap.


How to use jetty.server.Server

Hi, I'm new to Java and Gradle. I need to use org.eclipse.jetty.server.Server to write a web package like Flask in python, as there seems to be no counterpart for Python's HTTPServer in the Java built-in library.
I noticed that the jetty plugin is deprecated and I used Gretty instead as suggested. However, I failed to import the org.eclipse.jetty module with error: package org.eclipse.jetty.server does not exist.
I tried to add the jetty plugin in build.gradle but it was not found.
How could I set up the jetty.server.Server? Is downgrading the Gradle version the only choice? Is there any workaround or alternative for jetty.server.Server?

I found that I might mix up Gradle dependency and plugins. The jetty plugin is deprecated and replaced by gretty, while the jetty package could still be used by java code through the gradle dependency setting.
Please correct me if I am wrong.

Thank you for your interest in Gradle!
Please ask such a usage question on discuss.gradle.org or stackoverflow.com where to get answers by the community of Gradle users.
If, after investigation, it turns out to be a Gradle bug or missing feature, please file another issue describing the problem or use case and add a reproducer.


loader: gh971 Fix double free on physical devices

I'm getting a crash on Windows 7 x64 when running dEQP-VK.api.info.instance.physical_devices test.
The pointer is not reset to NULL after a free, which makes it possible to take that branch again on the next call and free again.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

LGTM :+1:

Committed: 0387853c4e919ff9ea53a62df378f91036dbfe9c


Implement generic function type syntax in the VM.

This is the VM-implementation issue for #27527.
At the moment we only really need the new syntax in typedefs. Eventually, we want to make this syntax usable for fields and locals, but it's not yet as high a priority. If you find the time to make it work there too, please guard it behind a (different) flag.

Moving to 1.22 for implementation, informal spec i linked from the meta-issue https://github.com/dart-lang/sdk/issues/27527

@a-siva FYI for assignment

CL being code reviewed (https://codereview.chromium.org/2643523002/)


deserializer says there's a missing colon between key and value when it exists

Sample input. This was generated by printing out the encoded yaml from a dataclass. I also ran it through a yaml linter to verify that it was correct:
recipe:
  name: foo
  author: ryan
  description: desc
  instructions:
    - this
    - that
    - then
  ingredients:
    - name: foo
      measurement:
        amount: 1.0
        unit: UNIT
pantryItems:
  - name: pantry
    nutritionInfo:
      caloriesPer: 1
      unit: UNIT

Error:
Uncaught Kotlin exception: net.mamoe.yamlkt.YamlDecodingException: There must be a COLON between class key and value but found null for 'me.rmullin.shared.RecipeFile'
./test.yaml
          ^ at line 1, column 12

Turns out it was user error with the library I was using to read the file

Just about to tell you that fact, but good to know the issue has been solved.


Pop Quiz 1/30

Reverse Proxy

In reverse proxy > server name and proxy pass
Describe the server name definition and proxy pass definition in the reverse proxy file

Server Name:
Server name in Nginx specifies the domain name associated with server block
Reverse Proxy:
Nginx is used as the reverse proxy to forward the cilent requests to backend servers
Proxy Pass:
Used to define the backend server address > requests forwarded there

Score

Security Config

explain security config rules required for access in spring boot
provide request matcher that shows permit
request matcher that shows authentication required

Security Config Rules:

necessary to control access to resources
necessary to protect sensitive information

Rules:

Authentication mechanisms > user/pass/OAuth
Auth Rules > who accesses what
Encrypt sensitive data
Secure communication protocols (HTTPS)

Examples:

ACL > access control list
RBAC > role based access

Permit
Authentication Required

Score

POJO

Explain POJO
Changes to POJO
Show in VsCode
Highlight change
Show POJO results as output via Postman

POJO: "Plain Old Java Object"

doesn't extend or implement special classes/interfaces
Java class that stays to a set of conventions to keep its structure simple
plain and standard Java object

POJO Characteristics:

has private fields
getter setter for fields
public no argument constructor

To Change POJO

Docker

describe docker and process for updating a docker application
show sequence of commands req to make docker update
show port used by Docker in application
in deployment show sequence of commands using docker to do update to web server

Luna's Questions
https://github.com/lunaiwa/student-template/issues/16#issue-2108598585
https://github.com/lunaiwa/student-template/issues/16#issuecomment-1917745438


increase Tekton Results pruner gracePeriod for Dev env

Following Konflux-bug 348, increasing the time period before Results Pruner kicks in to prune executed PipelineRuns from 10m to 2h.
There have been few instances where the PipelineRuns fail but we can't find the exact cause of failure because PipelineRun is already pruned. Konflux e2e demands to have PipelineRuns stored in the cluster for a longer period in order to proceed with tests, and further debugging by devs if needed.
Signed-off-by: Satyam Bhardwaj<EMAIL_ADDRESS>rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED

/test appstudio-upgrade-tests

/test appstudio-upgrade-tests


add option -i to save as gif

I added the option to save as gif, however the mp4 or mov file still needs to be saved as well. I'll be trying to find a workaround, but despite that it works. When using the -i option a .gif file will be saved to the output directory

It seems strange that changing the extension alone should create create a .gif. Can you link a source that confirms this?

It seems strange that changing the extension alone should create create a .gif. Can you link a source that confirms this?

Ffmpeg does exactly that. It recognises the extension and converts it into that format
I also tested that code and it worked just fine. Here is one article showing how to create .gif files with ffmpeg
https://engineering.giphy.com/how-to-make-gifs-with-ffmpeg/

Is there something still to be done for this PR to be merged?

Nope, that reminder was enough.


Added support of Oracle

Added support of Oracle

@pikhovkin This PR needs a rebase to the latest django-silk:master, can you work this?

Well, I messed up trying to work on the fork, I have opened another PR to continue discussion in #619


chore: bdd-nh-1584772750 to 0.0.1

chore: Promote bdd-nh-1584772750 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Infinite loop on circular registry

We see some registry with circular references resulting in infinite loop while trying to throw a RegistryKeyKeyNotFound exception (version https://pypi.python.org/packages/source/p/python-registry/python-registry-1.1.0a.tar.gz#md5=589311e55826174c1d50b0b177cd9d55)
    key = root.subkey("Select")
  File "/opt/python2.7/lib/python2.7/site-packages/Registry/Registry.py", line 249, in subkey
    raise RegistryKeyNotFoundException(self.path() + "\\" + name)
  File "/opt/python2.7/lib/python2.7/site-packages/Registry/Registry.py", line 209, in path
    return self._nkrecord.path()
  File "/opt/python2.7/lib/python2.7/site-packages/Registry/RegistryParse.py", line 1232, in path
    name = p.name() + "\\" + name
KeyboardInterrupt

If I add a print ('name', name) at line 1232 I see this:
name CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
name Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}\Microsoft\Windows\CMI-CreateHive{3D971F19-49AB-4000-8D39-A6D9C673D809}
....

worse and worse until I run out of memory

Should there be some kind of lookup table for offset pointing to decoded key, if any parent already contains that node what should it do?
Best way to generate an hive to reproduce this?

can you dump the flags for the key to see if that indicates any additional indicators of how to treat the nk record (SymbolicLink = 0x0010)
sbv-csis, can the hive producing this behavior be shared?

I'm afraid I can't share the hive raw but i'm currently trying to extract a workable test-case both for this issue as well as for my own tests.
I've recieved the hive via third-party and it's not mine to share. I'm a bit baffled myself as to how the hive got in that condition
How do I access the flags?

chntpw seems to see the same thing:
 chntpw -l bla/software_backup.bin
chntpw version 0.99.6 110511 , (c) Petter N Hagen
Hive <bla/software_backup.bin> name (from header): <emRoot\System32\Config\SOFTWARE>
ROOT KEY at offset: 0x001020 * Subkey indexing type is: 686c <lh>
File size 70254592 [4300000] bytes, containing 14796 pages (+ 1 headerpage)
Used for data: 1134187/67333408 blocks/bytes, unused: 8294/1411424 blocks/bytes.

Simple registry editor. ? for help.

(...)> cd ..

(...)\Microsoft\Windows> cd ..

(...)\Microsoft> cd ..

(...)> cd ..

(...)\Microsoft\Windows>

assuming you have a Windows box, try Registry Explorer which is my GUI for viewing hives. it also uses my own c# based parser under the hood, so i would be interested if your hive breaks my code as well
You can get Registry Explorer (and read a ton more about it) here.
http://binaryforay.blogspot.com/p/software.html
You will be interested in the technical view for the key you are trying to view. it will show you a Flags property with each flag decoded to its text representation
you can find out about technical details here
http://binaryforay.blogspot.com/2015/03/registry-explorer-0020-released.html
RECmd would also be useful to test with your data as you would know right away if you have a special hive or the issue is in this project.

It could very well be an issue with all tools as i do not recall ever getting a hive with a symlink in it for testing, but please let us know what my tools above give you

can you click on Flags present and then CTRL-C so I can see all the flags?
So did RE process the hive as expected without any errors? from that image it appears to have worked.
if so, the issue is in python-Registry

HiveEntryRootKey, NoDelete, CompressedName, VirtMirrored

ok cool. that should help Willi and NiKiZe out.

It seems to be working - I'm not really aware what I should be seeing. No infinite loop for sure.
I see lots of "Associated deleted records" and "Unassociated deleted records" otherwise it looks "normal" to me

my code recovers and reassociates deleted keys and values in hives. thats what you are seeing. see the user manual and/or the blog posts for all the gory details.

For now I'll work around the issue with a monkey patch like this:
  def path(self):
          """
          Return the full path of the registry key as a unicode string
          @return: unicode string containing the path
          """
          p = self

          name = [p.name()]
          offsets = set([p._offset])
          while p.has_parent_key():
              p = p.parent_key()
              if p._offset in offsets:
                  log.warn('Cyclic path - aborting at %s / %r',
                           p.name(), p._offset)
                  break
              name.append(p.name())
              offsets.add(p._offset)
          return '\\'.join(reversed(name))

  Registry.RegistryParse.NKRecord.path = path

@sbv-csis, thanks for reporting this issue! Quite a neat hive you've found :-)
@NiKiZe @EricZimmerman thanks for helping to triage :-)
I think the code in the monkey patch above is a pretty good solution. I like that you've used set and '\\'.join(reversed(name))! Do you mind if I incorporate this code into the main repository?

It's quite ok. :+1:


Is is possible to set custom executor for server?

There is a server::Builder::executor, however, the required traits ConnStreamExec and NewSvcExec are private.
So does it mean there is no way to construct a custom executor for a server?

You can, you need to implement hyper::rt::Executor. See the examples/single_threaded.rs file for an example.


Uses link to outdated nuget package

The article uses an outdated NuGet package (WindowsAzure.Storage) which as of version 9.4 has been split up into multiple NuGet packages. This page and the example code should be updated accordingly.

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

ID: 60e56e69-1c44-2056-ad5f-319535e4b525
Version Independent ID: 49fa6098-0b8e-ebf5-efe7-f50f3604e325
Content: Quickstart: Use .NET to create a blob in object storage - Azure Storage
Content Source: articles/storage/blobs/storage-quickstart-blobs-dotnet.md
Service: storage
GitHub Login: @tamram
Microsoft Alias: tamram

@ManfredLange Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
Just to highlight:

Has anyone gotten this sample to work with the new packages?

Having difficulty locating the package with the CloudStorageAccount type...

Yes, Microsoft did a pretty bad job with the transitioning from the old packages to the new packages. At some point there was no officially released nuget package targeting .NET Standard. In particular the support for table storage was bad or even non-existent. LINQ support for Azure Storage Table has been removed for the time being.
Perhaps the following info gets you started in a good direction:
Azure Storage Blobs
If you want to use Azure Storage blobs add nuget package Microsoft.Azure.Storage.Blob version 9.4.2 or later. This package targets .NET Standard 1.3, .NET Standard 2.0 and the full .NET Framework 4.5+.
In your code add these statements at the beginning of your file:
using Microsoft.WindowsAzure.Storage;
using Microsoft.WindowsAzure.Storage.Blob;

With that you should be able to write code such as:
var storageAccount = CloudStorageAccount.Parse(_connectionString);
var blobClient = storageAccount.CreateCloudBlobClient();
var container = blobClient.GetContainerReference("some container");
container.CreateIfNotExists();

Azure Storage Queues
If you want to use Azure Storage queue add nuget package Microsoft.Azure.Storage.Queue version 9.4.2 or later. This package targets .NET Standard 1.3, .NET Standard 2.0 and the full .NET Framework 4.5+.
Azure Storage Tables
If you want to use Azure Storage table: The client side API has been moved to nuget package Microsoft.Azure.Cosmos.Table version 1.0.0 or later. Note that this package support .NETStandard 2.0. I have not experimented using this nuget package with older targets such as the full .NET Framework 4.5+.
Note that even though the package name refers to Cosmos, you can also use it for Azure Storage tables. The client side APIs is mostly the same as previously for the basic stuff. The only exception is LINQ which is no longer supported (at least at the moment). I'd be happy to stand corrected but I suspect they want you to use Cosmos instead, so dropping LINQ support for table storage is probably driven by the finance guys at Microsoft. The current new implementation to query storage tables is much worse compare to using LINQ. You have to write code with strings as parameters. As a result you don't have type safety at the moment for certain code.

The sample has been updated to use .NET Core v2.1.0 and the Microsoft.Azure.Storage.Blob v10.0.1 NuGet package. It has been tested and run from VS2019. Please download the latest version of the sample and try again.
#please-close


Helm waits forever

I am using this ingress controller in a manner similar to #23. I'm using controller.hostNetwork=true and thus do not require the Service resource that this chart creates. My values config is as follows:
controller:
  hostNetwork: true
  extraArgs:
    "watch-ingress-without-class":
  kind: DaemonSet
  stats:
    enabled: true
  daemonset:
    useHostPort: true
  nodeSelector:
    role: ingress-controller

When deploying with helm, with the --wait as I need the command to block until the controller is ready, causes Helm to wait forever on a condition that will never happen:
$ helm upgrade --install haproxy-ingress haproxy-ingress/haproxy-ingress  --create-namespace --namespace ingress-controller  --version 0.14.2  -f values.yaml --debug --wait
history.go:56: [debug] getting history for release haproxy-ingress
upgrade.go:142: [debug] preparing upgrade for haproxy-ingress
upgrade.go:150: [debug] performing update for haproxy-ingress
upgrade.go:322: [debug] creating upgraded release for haproxy-ingress
client.go:396: [debug] checking 11 resources for changes
client.go:684: [debug] Patch PodDisruptionBudget "haproxy-ingress" in namespace ingress-controller
client.go:675: [debug] Looks like there are no changes for ServiceAccount "haproxy-ingress"
client.go:675: [debug] Looks like there are no changes for ConfigMap "haproxy-ingress"
client.go:675: [debug] Looks like there are no changes for ConfigMap "haproxy-ingress-tcp"
client.go:675: [debug] Looks like there are no changes for ClusterRole "haproxy-ingress"
client.go:675: [debug] Looks like there are no changes for ClusterRoleBinding "haproxy-ingress"
client.go:675: [debug] Looks like there are no changes for Role "haproxy-ingress"
client.go:675: [debug] Looks like there are no changes for RoleBinding "haproxy-ingress"
client.go:684: [debug] Patch Service "haproxy-ingress" in namespace ingress-controller
client.go:675: [debug] Looks like there are no changes for Service "haproxy-ingress-stats"
client.go:684: [debug] Patch DaemonSet "haproxy-ingress" in namespace ingress-controller
upgrade.go:394: [debug] waiting for release haproxy-ingress resources (created: 0 updated: 11  deleted: 0)
wait.go:48: [debug] beginning wait for 11 resources with timeout of 5m0s
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
... (message is repeated many times) ...
ready.go:258: [debug] Service does not have load balancer ingress IP address: ingress-controller/haproxy-ingress
upgrade.go:434: [debug] warning: Upgrade "haproxy-ingress" failed: timed out waiting for the condition
Error: UPGRADE FAILED: timed out waiting for the condition
helm.go:84: [debug] timed out waiting for the condition
UPGRADE FAILED
main.newUpgradeCmd.func2
	helm.sh/helm/v3/cmd/helm/upgrade.go:202
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.6.1/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.6.1/command.go:968
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_arm64.s:1172

This goes on for some time until Helm gives up and returns an error, despite everything working correctly.
Not using --wait is not an option here as I need to wait until the daemonset is actually up and healthy.

Hi, you can try configuring controller's service as ClusterIP, here is one of the installation tips regarding that:
The default service type is `LoadBalancer`, add `--set controller.service.type=<type>`
command-line option to change to `ClusterIP` or `NodePort`


Return created and lastUpdated for Connections

This is not a requirement at the moment, but could be useful, especially to add more details to the Connection Detail page. I don't see why we wouldn't do this automatically anyway.

done

Ty @KurtStam !


[FLINK-14689]Add catalog related commands support in SQL Parser

What is the purpose of the change
Add catalog related commands support in SQL Parser :

SHOW CATALOGS
DESCRIBE CATALOG catalogName
USE CATALOG catalogName
The PR is only about parser related changes to support catalog related commands and Hooking up with table env will come later.

Brief change log

aacc11Add show catalogs support in SQL Parser

2b472bAdd describe catalog syntax in SQL Parser

a746f79Add use catalog syntax in Sql Parser

Verifying this change
This change added tests and can be verified as follows:

FlinkSqlParserImplTest#testShowCatalogs
FlinkSqlParserImplTest#testDescribeCatalog
FlinkSqlParserImplTest#testUseCatalog

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: ( no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @xuefuz @bowenli86 @lirui-apache  to have a review

I'm not very familiar with sql parser, I wonder how the parsed command is connected to TableEnvironment?
side note on the ticket title: these are just commands, not DDLs

addressed

Thanks for the contribution. The PR looks good to me. To clarify, the PR is only about parser related changes to support catalog related commands and Hooking up with table env will come later.
It would be good to clarify this in the PR description area.

Addressed

LGTM, merging.
@zjuwangg just a friendly reminder that, please add component tag to the commit message. E.g.
this one should be [FLINK-14689][table] Add catalog related commands support in SQL Parser


client-side rendering issues with <lasso-slot> and out.global

I have a widget template that looks roughly like this:
<lasso-slot name="inline-js" />

        ...

In my index.js file (approximately):
module.exports = require('marko-widgets').defineComponent({
    template: template,

    getInitialState: function(input, out) {
        input.widgetClassName = 'widget'
        return input;
    },

    getTemplateData: function (state, input) {
        return state;
    },

    changeWidgetClassName: function () {
        this.setState('widgetClassName', 'widget2');
    }

The initial server render works fine, but I run into problems whenever I trigger a client rerender via changeWidgetClassName. It seems to choke on the lasso-tag, even though it is outside the w-bind. The .marko.js file contains something like this:
__tag(out,
      _________node_modules_lasso_taglib_slot_tag_js,
      {
        "name": "inline-js"
      });

And in the rerender it errors out:
Uncaught Error: Lasso page result not found for slot "inline-js-before-resultset".  And finally if I remove all of those, it still attempts to rerender the entire template, rather than just the w-binded part and below. So a few questions:

Does w-bind always have to be at the highest parent level of the template?
Should <lasso-slot> be kept out of client-rendered widgets?
Are there any gotchas for using out.global on the client?

Thanks

Does w-bind always have to be at the highest parent level of the template?

No, it does not

Should <lasso-slot> be kept out of client-rendered widgets?

Yes, it should only be in server-side templates.

Are there any gotchas for using out.global on the client?

Yes, when a rerender happens it manufactures a new out that will not have any user globals.

Is there any way to still use out.global? It seems like that should be available on both sides somehow.

What do you need out.global in the browser for? I want to better understand your use case

I actually don't need out.global or <lasso-tag> on the client, but just having those present in a template that gets rendered clientside (even if they're ignored via preserve or otherwise) will error and prevent the rerender. I imagine the use-case for maintaining access to out.global might come up in the future, so I was more curious on that piece.

During a rerender, the top-level widget can add additional things to out.global.
It's bad practice if Lasso.js related tags are embedded in the templates for UI components. Lasso.js tags belong at the top-level page or page layout.

Ok I'll refactor out the lasso tags. We can revisit out.global usage if it comes up in the future. Thanks!

Hey @patrick-steele-idem, this came up again recently. I have out.global.config on the server, which I would like to have available to widgets initialized on the client. Do you have a suggestion for this use case?

Hey @yomed, what I find works well is to pass configuration data from the server to the browser by adding the data to the widget config of a UI component rendered on the server. For example:
defineComponent({
    getWidgetConfig(input, out) {
        // Assuming this is rendered on the server
        return {
            serverConfig: out.global.config
        };
    },

    init: function(widgetConfig) {
        var serverConfig = widgetConfig.serverConfig;
        // You can do what you want with the server config...
        // For example, store it as part of a single module:
        var myApp = require('src/app');
        myApp.setServerConfig(serverConfig);

        // Or, you could just store it as part of this widget
        this.serverConfig = serverConfig;
    }
})

Does that work for you?

Hmm I think it's a weird use case. We have the component split into renderer/widget, so that we could do server render initially in the future. But for now, we are actually not doing any server-rendering at all of the component itself. However, I suppose I could get a similar result by modifying input to contain config.


How to recentered "All swipeable" when user press/touch outside the swipeable container?

I have a Flatlist with Swipeable Item.
When I swipe one item, how to recenter() when I click anywhere on the Flatlist?
The behavior is like "Clock" app in iOS

You can have the ref on each object that you have, and call recenter() on each one when you need it:
// Object containing and index to each ref
swipeablesRef = Object.create(null);

// Set the ref somehow, for example:
if (!swipeablesRef[index]) swipeablesRef[index] = React.createRef();
<Swipeable ref={swipeablesRef[index]}>...</Swipeable>

// Call this when you need to recenter each swipeable
recenterAll = () => {
  Object.values(swipeablesRef).forEach(s => s.current.recenter());
}

// Call this when you delete one swipeable
deleteSwipeable = index => delete swipeablesRef[index];

You can have the ref on each object that you have, and call recenter() on each one when you need it:
// Object containing an index to each ref
swipeablesRef = Object.create(null);

// Set the ref somehow, for example:
if (!swipeablesRef[index]) swipeablesRef[index] = React.createRef();
<Swipeable ref={swipeablesRef[index]}>...</Swipeable>

// Call this when you need to recenter each swipeable
recenterAll = () => {
  Object.values(swipeablesRef).filter(s => s.current).forEach(s => s.current.recenter());
}

// Call this when you delete one swipeable
deleteSwipeable = index => delete swipeablesRef[index];

It works for me. Thanks

You can have the ref on each object that you have, and call recenter() on each one when you need it:
// Object containing an index to each ref
swipeablesRef = Object.create(null);

// Set the ref somehow, for example:
if (!swipeablesRef[index]) swipeablesRef[index] = React.createRef();
<Swipeable ref={swipeablesRef[index]}>...</Swipeable>

// Call this when you need to recenter each swipeable
recenterAll = () => {
  Object.values(swipeablesRef).filter(s => s.current).forEach(s => s.current.recenter());
}

// Call this when you delete one swipeable
deleteSwipeable = index => delete swipeablesRef[index];

It works for me. Thanks

Working, nice!


use of 8092 rather than 8192 for accelleration scale

Version
?
Describe the bug
Simple one this time :).
typo in code.. 8092 rather than 8192!!!!
Reproduce
Search the code for 8092.
Expected behavior
should be 8192.
Additional context
probably does not cause any operational issues as accelleration is generally used for getting the direction of gravity.

Thank you for your suggestions. We will fix this problem in the next routine update.


Doesn't import into neo-gui wallet.

Hey guys, when i bought my first NEO i created wallet in Neon. Then I downloaded neo-gui (with all blockchain as well) and wanted to import my wallet there through WIF. Address appeared on Account page, but it shows no NEO or NeoGas on it, but actually there is (as I can see through Neon wallet)

Click the "rebuild index" button and wait for 15~30 minutes. Then your NEO and GAS will appear.


Cannot install from file resource

Hi,
I am trying to use your extension to install and manage extensions which are currently located locally on my server:
First, I was assuming I would be able to see the extensions that are listed in the extensions file path. I don't know if that is part of the extension, or if we can 'only' launch the installation of existing extensions based on the our settings.json. Could you clarify ?
There seems to be only linux examples. I am trying to use this on Windows, and I don't know if I am not correctly filling the Json files, OR if there is a bug.
This is my user settings.json file
"vsix.sources": {
        "mfs": {
            "type": "file",
            "path": "C:\\Users\\Stephane\\Documents\\script-scripttemplate\\Sources\\scw-snippets\\",
        }
    },
    "vsix.debug": true,
    "vsix.extensions": [
        "scw-snippets-0.0.1"
    ],

I tried using \ \\ / adding a slash and without at the end... My extension never showed up in the extension tab.

Nevertheless, when I do: vsix Manager: Install extensions I get the following error messages
But I do get the following message

When I copy my extension manually to C:\Users\MyUser\.vscode\extensions It shows up.

Question 2: Are 'Shares' supported ? (\\MyServer123\MyExtensions\) ?

"scw-snippets-0.0.1" needs to be "mfs:scw-snippets-0.0.1" (prefixed with mfs:) so the extension knows which source to use.

Question 2: Are 'Shares' supported ? (\MyServer123\MyExtensions) ?

It should be able but I haven't tested...

Thanks for your quick answer. I didn't manage to make it work.
I am not sure if I have missed something in the configuration, or if there is a bug somewhere, as the only message I have, is the following one:

It would be great to have little bit more information to help debug:
Something like:
Attempting installation from ${SnippetName}.
 [${vsix.SourceType}${SourceName}] Searching for ${$SnippetName} in ${$vsixSource.Path}

I don't know if it is searching it in the right location. Can he access the folder structure or not ?
Can he find the vsix file, if not, what is the string he is actually searching for ?
My Vsix file Is called scw-snippets-0.0.1.vsix and located in "C:\Users\Stephane\Documents\script-scripttemplate\Sources\scw-snippets\"
This is what my settings.json looks like:
"vsix.sources": {
        "mfs": {
            "type": "file",
            "path": "C:/Users/adm1-taavast3/Documents/script-scripttemplate/Sources/scw-snippets",
        }
    },
    "vsix.debug": true,
    "vsix.extensions": [
        "mfs:Swisscom-Common-Team.scw-snippets-0.0.1"
    ],

The version can be omitted since you can have several versions in same folder and the manager always picks the newest version.

ok, removing the version actually solve it. I could install it successfully now using the command VSIX Manager: Install extensions

Is there no way to have the extensions that we specifiy in the vsix.extensions visbile in the extension pane before we install them ?
So that the user can choose pick and choose using the GUI ?

Is there no way to have the extensions that we specifiy in the vsix.extensions visbile in the extension pane before we install them ? So that the user can choose pick and choose using the GUI ?

No, it's not possible. I've check if there was new commands available to do that.
The user can comment the line of the extensions he don't want.

ok. Great. Thanks a lot for you answers @daiyam ! :)

I've improved the doc, hopefully it will good enough ;)


Fix for lazyLoad with initialSlide option

Small change to initialize currentSlide to the initialSlide options.
Fix in change event handler to rollover array.
Update:
Merged upstream and updated babel => babel-cli

I tested this out, works great!

hey @akiran this has been open for a while and there is a definite need across the board for this feature to be put into the package.    Would be great if the community could get this merged in asap.
Thanks

I couldn't merge this because of merge of merge conflicts.
I have incorporated the fixes in this PR in #410


bin: support parse localhost

This closes #222.
Signed-off-by: tison<EMAIL_ADDRESS>

We may need an e2e test for this kind of changes though.

@Xuanwo I do think we need to investigate a better workflow now, if you make it clear in https://github.com/datafuselabs/databend/discussions/3415  :P

I did not consider that SocketAddr does not support parsing hostname.

No, it doesn't. See also the original issue #222.


⚠ Roblox Group Api has degraded performance

In 3770521, Roblox Group Api (https://groups.roblox.com) experienced degraded performance:

HTTP code: 503
Response time: 3783 ms

Resolved: Roblox Group Api performance has improved in 539328d.


Fixed typo for autocomplete validation error 'vsAutocompleteErorr' to 'vsAutocompleteError'

These changes can provide backward compatibility problems. The old property should be retained.

So you release a new version and follow semver practices?  I don't see the complication.  Any bugfix is a potential backwards compatibility problem which is why versioning exists.


cmake confgiure error

Version:
Platform:
[Mason] Downloading package https://mason-binaries.s3.amazonaws.com/linux-/libuv/1.9.1.tar.gz...
CMake Error at cmake/mason.cmake:95 (message):
[Mason] Failed to download
https://mason-binaries.s3.amazonaws.com/linux-/libuv/1.9.1.tar.gz: "HTTP
response code said error"
Call Stack (most recent call first):
cmake/mason-dependencies.cmake:8 (mason_use)
CMakeLists.txt:75 (include)

I use cmake configure project,the prompt cannot download 1.9.1.tar.gz

I think you're reporting this to the wrong project. That URL is not maintained by us. Try reporting this to the Mason project.


How to remove "Text" in Image

I got the application to work and such, I was able to remove the little dots but am having problems removing the Image name, is their a easy way of removing the "Title" of the frame?

Sorry was meant for Slider not View.


easy_install goatools: cannot import name ContextualZipFile

Hi!
I succesfully installed goatools, but I don't know where it is on the shell.
~$  l -lh go-basic.obo
-rw-rw-r-- 1 edgar edgar 30M okt  9 04:20 go-basic.obo
~$ whereis go-basic.obo
go-basic:

Thank you in advance for your help


Shorthand concern

gridlock --lockfile gridlock.json add tree-sitter/tree-sitter-rust

Why is tree-sitter/tree-sitter-rust assumed to be MS GitHub? Nix uses github:, gitlab:, sourcehut;, gitea:, etc. to not play favorites with forges. Standardizing on a US-based, for profit, proprietary forge is probably not the best thing when thinking about defaults or the future.

this is a proof of concept program. it also does the same thing as niv.


Do not allow the installer to deselect ScriptCards or the Meta Toolbox

These are required.

Addressed in pull request #63.


Gentle vacuum LA stats

What problem are we solving?
I would like to have more information about loading the system at the time of the vacuum
https://github.com/seaweedfs/seaweedfs/issues/3369
How are we solving the problem?
Since in the future, when the threshold value is exceeded, you can also slow down the vacuum
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

I0801 10:44:24.344908 topology_vacuum.go:92 1 vacuum 1539 on fast-volume-1:8080 processed 719464584 bytes, loadAvg 17%


[zoom] add support to downloading screen recording

Checklist

[X] I'm reporting a site feature request
[X] I've verified that I'm running yt-dlp version 2022.01.21. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
worldwide
Example URLs
I have access to multiple zoom recordings that are relevant to this feature, I am willing to share credentials although I plan to implement this feature by myself
Description
the current zoom extractor always download the camera recording, if a zoom meeting contains a screen share it will not be downloaded
I want to add support to download only the screen share, or both
I managed to implement this feature in youtube-dl already, but since then I learned of yt-dlp and prefer to implement this here
I'm opening this issue as described in Adding new feature or making overarching changes
the way I see it, this feature includes:

some way of choosing what to download between these three options (these are zoom's code terms)

view (the camera recording only, default value and current behavior)
share (the screen share video only)
both (this is a term I made up, its debatable)

the two videos will downloaded as a playlist, with the view as the first and share as the second

if share is selected (whether in both or share) but the meeting does not contain a share video, it will log a non fatal warning, revert to the default option and continue

Verbose log
[debug] Command-line config: ['-vU']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2022.01.21 [f20d607b0]
[debug] Python version 3.10.1 (CPython 64bit) - Windows-10-10.0.22000-SP0
[debug] exe versions: ffmpeg 4.4.1-full_build-www.gyan.dev (setts), ffprobe 4.4.1-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2022.01.21, Current version: 2022.01.21
yt-dlp is up to date (2022.01.21)

You can simply return them as different formats of the same video. Users can select what to download using -f

You can simply return them as different formats of the same video. Users can select what to download using -f

I may not understand the formats correctly, but isn't it suppose to be for different versions of the same video?
in this case, the audio stream is the same for both of them, but there are two different video streams
in what way do you suggest this will this be represented in the -f parameter?

See https://github.com/yt-dlp/yt-dlp/issues/389

Sorry I'm late to the party, is this feature available for use? How do I save both the screen recording and camera recording?

Sorry I'm late to the party, is this feature available for use? How do I save both the screen recording and camera recording?

Unless it was removed, then yes it's available
Zoom now require some proof of work for logging in, so if the recording require a password you'll need to manually enter the password in the browser and copy the session cookie and add it to the header in yt-dlp
To list all available formats use -F, then it should be listed there
My bad that the issue wasn't closed 😅
After so long I feel like I should check that it still works before closing it
I'll see when I have the time


Translate README.md into Chinese version.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.614%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5692

Relevant Lines:
5772

💛  - Coveralls


tf.keras.metrics.RootMeanSquaredError() not commutative for higher dimensional tensors

System information.

Linux Ubuntu 20.04
Python 3.7.9
tensorflow-gpu 2.5.0, installed via pip

Describe the problem, i.e. current behaviour.
The RootMeanSquaredError metric is not commutative for Tensors with >3 dimensions.
Describe the expected behavior.
The RootMeanSquaredError metric should be commutative for all Tensors despite their dimension.
Standalone code to reproduce the issue.
>>> import tensorflow as tf
>>> import numpy as np

>>> rmse = tf.keras.metrics.RootMeanSquaredError()
>>> y1 = tf.constant(np.random.random((10, 10, 10, 10)))
>>> y2 = tf.constant(np.random.random((10, 10, 10, 10)))

>>> rmse(y1, y2) == rmse(y2, y1)
<tf.Tensor: shape=(), dtype=bool, numpy=False>

Implementation that is commutative.
>>> def rmse_diy(y: tf.Tensor, y_hat: tf.Tensor):
>>>     return tf.sqrt(tf.reduce_mean(tf.square(tf.subtract(y, y_hat))))

>>> rmse_diy(y1, y2) == rmse_diy(y2, y1)
<tf.Tensor: shape=(), dtype=bool, numpy=True>

@sushreebarsa thanks for the fast reply. Your attached gists work like a charm. This is interesting, I will have another look at my Python environment tomorrow.

I have not yet been able to identify the root cause of this unfortunately, but it is definitely a bug.

I was able to reproduce the issue on tf-nightly and Kindly find the gist of it here.

Hey @MathiesW -- in your example, it looks like you're not calling reset_state on the rmse metric in between calls, which is causing it to accumulate previous results in its new result, which is likely what's leading to the small numerical discrepancy.
If you instead use the following code, you'll find the results are identical. The trick is that we need to reset the state of our metric between calls, as Keras metrics are stateful
>>> import tensorflow as tf
>>> import numpy as np

>>> rmse = tf.keras.metrics.RootMeanSquaredError()
>>> y1 = tf.constant(np.random.random((10, 10, 10, 10)))
>>> y2 = tf.constant(np.random.random((10, 10, 10, 10)))

>>> r1 = rmse(y1, y2)
>>> rmse.reset_state()
>>> r2 = rmse(y2, y1)
>>> r1 == r2
<tf.Tensor: shape=(), dtype=bool, numpy=True>

So I think this is WAI -- please let me know if I've misunderstood your question. Thanks!


Adds new config options:

DisablePointerAddresses: Specifies whether to disable the printing of
pointer addresses.
DisableCapacities specifies whether to disable the printing of capacities
for arrays, slices, maps and channels.
These are useful when diffing data structures in tests. Printing pointers
and capacities would otherwise lead to false negatives.
Needed to fix issue #317 in Testify.

Awesome, thanks.


String attr_json attributes does not get stripped using strip_attributes

Hi,
I wanted to use the strip_attributes gem to strip white spaces from a string attr_json attribute,
which surprisingly does not work.
Current behaviour:
Given a model using the strip_attributes gem for all attributes,
When a string attr_json field is changed with a string including whitespaces,
Then the string attr_json attribute is not stripped of white spaces.
My expected behaviour:
Given a model using the strip_attributes gem for all attributes,
When a string attr_json field is changed with a string including whitespaces,
Then the string attr_son attribute is stripped of white spaces.
Example of the current behaviour:
Model
# frozen_string_literal: true

# == Schema Information
#
# Table name: accounts
#
#  id                             :bigint           not null, primary key
#  full_name                      :string

class Account < ApplicationRecord
  strip_attributes

  attr_json :foo, :string
end

Testing from the console to keep is simple:
> account.full_name = ' white space '
=> " white space "
> account.foo = ' spacey attr json '
=> " spacey attr json "
> account.save
=> true
> account.full_name
=> "white space"
> account.foo
=> " spacey attr json "

I'm not sure why it does not work with attr_json attributes, the gem itself is stripping the attributes before validation.
Any thoughts?

Hi, thanks for the question.
What do you mean by "the gem itself is stripping the attributes before validation"?
Can you try setting rails_attribute: true when you define the attributes, and see if that makes any difference? (I mean to make this always on in a future 2.0 release).
Otherwise, I'm not sure, it's possible that the strip_attributes gem just works using Rails API that doesn't apply to the way attr_json works. I don't really have time to debug it myself at the moment, but would be happy to hear and respond to anything anyone else finds from more debugging, or review a PR!

Hi,
Thank you for your fast reply.
I added the rails_attribute: true, unfortunately, it did not work.
I will investigate a bit further, thank you.

Looks like the strip_attributes gem uses the []= method to set the new value...
https://github.com/rmm5t/strip_attributes/blob/37c1cb257638ea5075f970e8beb763eb3ea06bc8/lib/strip_attributes.rb#L47
I am doing some refactoring of internal attr_json things for a 2.x release, and I was wondering if this might be enough to make strip_attributes work, but I'm afraid that I still haven't managed to make AttrJson compatible with setting values with []=.
if strip_attributes were changed to use record.send("#{attr}=", value) instead, it should work compatibly with AttrJson.  (Although wouldn't help you get into things like array attributes and such).
Alternately, you could try to write your own code using strip_attributes, re-use it's code in a slightly different way. It would take writing some code.
As it is, they are not compatible, and there isn't any great path on this end to making them compatible.
I'm going to close this ticket for now! Thanks for the report!

Note that a change to strip_attributes was proposed at https://github.com/rmm5t/strip_attributes/pull/34 a few years ago that would make it work with attr_json, among other gems; but it was rejected.
I do think we need some good answer for stripping with attr_json, I'm thinking on it and hope to have something in upcoming v2 release.


Fix label for number inputs with 0 as value

For an
<Input type="number" label="label text" value={0}/>
the label would overlay the value when it was set to 0 (the integer)
since the checking logic checked for javascript "trueishness".
Now the check is explicit against null, undefined, empty string and NaN.

@javivelasco Any reaction on this?

Missed it. Totally makes sense, thanks!


Add View(Audio|Video)Playlist Intents.

Opens (instead of playing) the playlist specified by the user, including the various built-in Recently Added playlists.
German translations for the new utterances need verification.  Ping @mcl22 and @ausweider.

German utterances added with 5586681, but I just guessed.  @mcl22 and/or @ausweider should verify before merge.

Tested in English and working OK.  Going to merge -- German users should look over the translations and make a PR or comment here if something is wrong.


Missing branch/tag buttons on latest commit

I would like to branch or tag my latest commit, but I cannot see it. Shouldn't I be able to see the buttons always when selecting the latest commit?

In the picture you have selected a checked out branch, which is master.  But if you click open spaces you should be able to see the small "+" symbol that will allows you to create a tag or branch rather then move button.
Is that what you are looking for?

Yes, that is what I was looking for. I guess I was just surprised by the little plus sign disappearing when selecting the branch. I can understand why they disappear when I select a branch-because + move is displayed instead. But do you really have to hide it when I select the commit circle?

Admittedly, I have UI design skill of blind orangutan so I'm open to the UI idea.  But honestly I like what we have as different state displays different ops with context.

@codingtwinky there is certainly an issue with "+" not being shown when it should. If I hover my mouse, there is like 1 or 2 pixels, where I can click and it works as if I clicked on "+" but the + is not visible. This is some layout issue I guess.


changed behavior of "firewall-cmd --permanent --get-target --zone public" in new versions

Today I faced with idempotency issue.
if set target with % symbol
firewalld_zone { '***':
   ...
    target => '%%REJECT%%',
  }

firewall-cmd return value without %
#  firewalld version 4.3.2-8.1.el7_3
firewall-cmd --permanent --get-target --zone public
# REJECT

in previous version firewalld 3.9-14.el7
It returns correct value
firewall-cmd --permanent --get-target --zone public
%%REJECT%%

Now I use value without %
target => 'REJECT',

as in result it generate correct value
<?xml version="1.0" encoding="utf-8"?>
<zone target="%%REJECT%%">
  <short>Public</short>

but it looks like workaround.
Could you comment about this case?

Looks like firewalld have changed the responses in v4 :-(  - As you say, your workaround does work but this requires people to change their code when moving from firewalld 3 -> 4, so we should probably make the module backwardly compatible and recognize both %%REJECT%% and REJECT as the same

Tracked this down to this change...
https://github.com/t-woerner/firewalld/commit/7d7a7a974c1b520faeae2e4f4e367550b10c4a80
From what I can see from the changelogs this was introduced between 0.3.11-2 and 0.3.12-1, I really wish changes like this would be part of a major release as it breaks any tool that relies on consistent output from the firewall-cmd CLI (like this module)
The motivation seems to be hidden in a RedHat bugzilla ticket (RHBZ#1058794) that doesn't seem to be accessable publicly.
@t-woerner I'm not sure what kind of versioning system that firewalld uses, but changing the CLI output can break a lot of automation tools, it would be nice if these were better communicated in a major version release rather than just snuck in.


EPIC: Improve imperative user experience for setters

[ ] Update the documentation for create-setters function with best practices on how to use the function.
[ ] list-setters function should list the setter information per package similar to pre-v1. Currently all setters are listed as if they belong to the single root package.
[ ] Setters with same name might have same or different values based on the semantics of the setter. We should formulate a good UX to record the intent of package consumers in order to set the values. E.g. Consider cluster(rootpkg) and nodepool(subpkg). If both have project-id setter, they both mean the same and should have the same value. On the other hand, if there is a setter called name in both packages, even though the setter name is same, cluster.name and nodepool.name should NOT have same value.

cc @pitta @droot

list-setters function should list the setter information per package similar to pre-v1. Currently all setters are listed as if they belong to the single root package.

I think perhaps this should be the default output, but should have flags to produce what is currently being used. With perhaps more to adjust the output for yaml, etc.

Setters with same name might have same or different values based on the semantics of the setter. We should formulate a good UX to record the intent of package consumers in order to set the values. E.g. Consider cluster(rootpkg) and nodepool(subpkg). If both have project-id setter, they both mean the same and should have the same value. On the other hand, if there is a setter called name in both packages, even though the setter name is same, cluster.name and nodepool.name should NOT have same value.

I may be reading this incorrectly, but wanted to expand on this a bit.
There is an additional case to consider which is pulling in and having multiple copies of the same nodepool(subpkg). This will produce multiple instances of setters like nodepool.name that should all be unique in their values.

list-setters function should list the setter information per package similar to pre-v1. Currently all setters are listed as if they belong to the single root package.

I think perhaps this should be the default output, but should have flags to produce what is currently being used. With perhaps more to adjust the output for yaml, etc.

Setters with same name might have same or different values based on the semantics of the setter. We should formulate a good UX to record the intent of package consumers in order to set the values. E.g. Consider cluster(rootpkg) and nodepool(subpkg). If both have project-id setter, they both mean the same and should have the same value. On the other hand, if there is a setter called name in both packages, even though the setter name is same, cluster.name and nodepool.name should NOT have same value.

I may be reading this incorrectly, but wanted to expand on this a bit.
There is an additional case to consider which is pulling in and having multiple copies of the same nodepool(subpkg). This will produce multiple instances of setters like nodepool.name that should all be unique in their values.

Yes. In this case, the intent is to have different value even the setter name is same. The general idea is to obtain the intent of the user for knowing the semantics of setters with same name across packages.

kpt fn eval -i create-setters:v0.1 --fn-config
Tab completion for the file paths here (and in various other places too numerous to enumerate at the moment) would be very helpful.


feat: include runtime base call filter in extension call filter

The extension should not allow any calls which are explicitly prohibited by the base call filter defined on the system pallet. An example is all the force_* calls within the balances pallet which we explicitly prevent due to the nature of the token of the chain.
The PR simply calls the base call filter first before then determining whether the call is explicitly denied by the extension configuration.

Codecov Report
Attention: Patch coverage is 90.90909% with 1 line in your changes missing coverage. Please review.

Project coverage is 45.50%. Comparing base (39f16e1) to head (11ef3a5).

Files with missing lines
Patch %
Lines

runtime/devnet/src/config/api/mod.rs
90.90%
1 Missing :warning:

@@                 Coverage Diff                 @@
##           frank/extension     #264      +/-   ##
===================================================
+ Coverage            45.24%   45.50%   +0.26%
===================================================
  Files                   40       40
  Lines                 3698     3685      -13
  Branches              3698     3685      -13
===================================================
+ Hits                  1673     1677       +4
+ Misses                1971     1954      -17
  Partials                54       54

Files with missing lines
Coverage Δ

runtime/devnet/src/config/api/mod.rs
35.29% <90.90%> (+35.29%)
:arrow_up:

... and 10 files with indirect coverage changes


Does TUF handle downloading initial target file over http?

I am exploring the idea of distributing a binary file using TUF. I read that The client-side of the framework must ship with trusted root keys for each configured repository. . Does that mean I must distribute the initial version of the binary file over https?
Sorry for these naive questions as I am just getting familiar with this framework.

  We are not providing a means to bootstrap security so that arbitrary    installation of new software is secure.  In practice this means that people    still need to use other means to verify the integrity and authenticity of    files they download manually.
I guess that answers my question. The initial binary still needs to be distributed over https.


System.MissingMethodException on bot startup

When I start the debug I get this:
System.MissingMethodException: 'Method not found: 'System.Threading.Tasks.Task'1<Discord.IUserMessage> Discord.IMessageChannel.SendFileAsync(System.String, System.String, Boolean, Discord.Embed, Discord.RequestOptions)'.'

Have you installed the prerequisites?

Have you installed the prerequisites?

If you mean the dependencies, yes, I've installed them.

Have you installed the prerequisites?

If you mean the dependencies, yes, I've installed them.

Actually I'm getting an error in the Discord.Net dependency that says that it found another version.

It shouldn't honestly, as this has been fixed a while ago https://github.com/Kwoth/NadekoBot/commit/445e082d6c63f6f4b4ff598cb3dc073f5f32cbc7
Redownload the bot and try again.

Yeah, this was fixed a long time ago.


MPS should show no results in similar manner to results

Instead of a notification that disappears after a small bit, it should instead show a page like when there is results but instead just with the words "No results"

Leaving it as a toast for now, just decided to make the duration unlimited so that the user will still see the notification no matter when they return. PR that implemented this #32


rustc-link-arg validation breaks link-arg propagation from -sys crates

Problem
With #9523 the following use-case does not compile anymore with nightly. It works with current stable.

A -sys crate links against an external library using cargo:rustc-link-lib/cargo:rustc-link-lib-framework in its build.rs. The crate is to be consumed by a cdylib crate. To make consumption easy, build.rs of the -sys crate also prints out cargo:rustc-cdylib-link-arg=-Wl,-rpath,/some/path.
The cdylib crate depends on the -sys crate and the cdylib is linked in a way that the external library becomes a dependency for the dynamic linker and the rpath is set due to the propagation of rustc-cdylib-link-arg from the -sys crate to the final cdylib crate.

With stable rust this works as described, with nightly this now produces a build error when compiling the -sys crate due to the use of rustc-cdylib-link-arg in the non-cdylib -sys crate.
Concrete example:
Building the qttypes crate from https://github.com/woboq/qmetaobject-rs/tree/master/qttypes produces the error that #9523 introduced:
$ cargo +nightly build
   Compiling qttypes v0.2.1 (/Users/simon/src/qmetaobject-rs/qttypes)
error: invalid instruction `cargo:rustc-cdylib-link-arg` from build script of `qttypes v0.2.1 (/Users/simon/src/qmetaobject-rs/qttypes)`
The package qttypes v0.2.1 (/Users/simon/src/qmetaobject-rs/qttypes) does not have a cdylib target.

Possible Solution(s)

Allow rustc-cdylib-link-arg again in non-cdylib crates to avoid breaking their build with the next stable release.
Notes
Output of cargo version:
cargo 1.54.0-nightly (0cecbd673 2021-06-01)
cargo 1.52.0 (69767412a 2021-04-21)

@tronical We discussed this in the @rust-lang/cargo meeting today.
The behavior on stable wasn't intended to pass the flags to any package other than the current one. Up till 1.50, it was silently ignored. From 1.50 to 1.52, it was incorrectly propagating to the final linking package. On nightly, an error was added to indicate that the package doesn't have a cdylib. The behavior on stable wasn't known at the time.
A crate shouldn't be able to silently affect the link arguments of the crate depending on it; the crate depending on it should have to opt into that by calling a dependency-provided function from its own build script or similar. (Such a function could reference metadata provided by the dependency, just as it could currently reference such metadata to find things like C include paths.)
In general, rpath is something that a dependency can't safely set for a crate that depends on it; that might work for a specific cooperating set of crates, but not for an arbitrary dependency. Different crates may want to set rpath in different ways. (And, for that matter, different builders/distributors of executables may want to set it differently; for instance, Linux distributions typically do not want rpath set.)
So, rustc-cdylib-link-arg shouldn't affect the linker invocations of depending crates. To avoid breaking builds, we will make this a warning rather than an error for now, though we may make it an error in the future. We suggest altering your build scripts to only pass rustc-cdylib-link-arg within the package that contains the cdylib.

A crate shouldn't be able to silently affect the link arguments of the crate depending on it;

Why not?
For example, in C++ with cmake, this is quite typical to do  target_link_options with INTERFACE and the link flags are propagated to all the dependees.
I would say that this is a valid use case to add some flags from the -sys crate, so that everything is setup for any crate using it.
I wouldn't call this behavior "silent".

the crate depending on it should have to opt into that by calling a dependency-provided function from its own build script or similar.

That's quite an overkill workaround.  I've seen crates doing that (e.g, neon) but i guess it's only because it did not work with previous versions.
Asking every crate at the bottom of the tree to use a build script and depending on a build crate because one crate deep in the hierarchy might need a specific flag is quite not convenient when one could just tell cargo to do the right thing with something like rustc-cdylib-link-arg

In general, rpath is something that a dependency can't safely set for a crate that depends on it [...]. Different crates may want to set rpath in different ways.

This is off topic, but i was under the impression rpath are additive, so that different crates just append all the rpath they need.

(And, for that matter, different builders/distributors of executables may want to set it differently; for instance, Linux distributions typically do not want rpath set.)

That's true, but on the other hand, we added the rpath on our project because people filling github issues about our crate "not working" as it couldn't load shared libraries. We thought rpath was a good way to fix this problem to get a better out-of-the-box experience. Even of packagers, rpath doesn't hurt, does it?

I would say that this is a valid use case to add some flags from the -sys crate, so that everything is setup for any crate using it.

Linker options can conflict or create various issues, and may break if the depending crate is doing something non-trivial with linking, or if they have different needs than one of their dependencies might expect.
And there's no way for the depending crate to control or filter out those options, if they're propagated from a dependency. In many cases, the depending crate may not even see those options; nothing will even display them unless you verbosely display your link line or the output of dependency build scripts.
Also, where to load shared libraries from can be a very project-specific or distribution-specific problem of release engineering. Binaries may be built on one system, packaged up, and deployed to other systems, with shared libraries in a different place than they were on the build system. In general, the -sys crate can't know the right solution for many use cases.
If we were going to support this, I could imagine doing so by allowing crates to declaratively (without using a build.rs script) state that they want to use link flags from a specific dependency's metadata (DEP_THEDEPNAME_LINK_FLAGS, for instance).
But beyond that, rpath is one of many things that we should really have a standard solution to. People should be able to make a single top-level decision like "I want rpath set in this common way" or "I want rpath set in this uncommon way" or "I don't want rpath set at all", and then crates supplying shared libraries should be able to give cargo enough information that it could set that consistently with the user's preferences and those of the top-level crate.

This is off topic, but i was under the impression rpath are additive, so that different crates just append all the rpath they need.
Even of packagers, rpath doesn't hurt, does it?

It can hurt, for various reasons. https://wiki.debian.org/RpathIssue gives one explanation. An rpath may also cause libraries to be loaded from an unexpected path; that may have security implications, or may break if there are other libraries in that path. It's important for people building crates to be able to control where they load libraries from.

Perhaps the -sys crate can't know the right solution for many use-cases, but I believe that it should be in a position to make some decisions and it can take "user input" into account. If the consumers of the crate have to express that they want to use link flags from a dependency's meta-data and it also needs to be specified by the consumers of the consuming crate, then it becomes hard to use. We want the crate that we are developing to be easy to use. It's okay if the build fails, but it's bad if everything compiles but the program can't be started because the dynamic linker can't find a library that the regular linker clearly found at build time.
The feature that build systems like CMake offer is the encapsulation, that a CMake target can be used without having to know what other things it depends on. If I create a library with CMake and say that it needs this particular linker flag, then I can be sure that in a dynamic build the library will be linked with the flag and in a static build that flag will be forwarded until a shared library (or regular binary) is created. The only equivalent that I can think of from before that were lib tool archives.
I agree that built-in support for rpath in Cargo would be awesome, combined with a single top-level decision as you pointed out. It would be great to have a solution in the meantime, which is what rustc-cdylib-link-arg seems to offer - at the risk of being imperfect.
In any case, thanks for considering this issue and our input :-). It's much appreciated that you plan on making this a warning again, instead of an error.

I was about to file a new issue about this problem when I noticed this one so let me chime in here with my feedback:

The regression is affecting not just rustc-cdylib-link-arg but also rustc-link-arg
I am with @tronical that having the top-level (and most importantly - all intermediate crates) down the dependency chain having to "opt-in" into the transitive behavior (with a build.rs script!) is very, very unergonomic to put it mildly
Specifically in the embedded space - where a single SYS-type crate might be modeling all aspects of the Vendor SDK - including linking - allowing transitive custom link args is doing more good than harm

So indeed - I would very much appreciate too, if the old transitive behavior is restored (albeit with a warning), until we have an easy, one-line declarative way for the top-level binary crate to opt-in into consuming link args from a SYS crate down the dependency chain.

I guess I wasn't completely clear in my previous comment. The fix that turns back the old transitive behavior - albeit with a warning - works ONLY when the link type is cdylib. We need it for link type bin.

Given that this issue was recently closed as a duplicate of this one, let me state that the scope of the problem is not only about passing an rpath from a -SYS crate down to a 'cdylib' crate.
We would like to pass - transitively of course - ALL sorts of linker args from a -SYS crate all the way down to a binary (as opposed to cdylib) crate.
The above is very, very useful in the embedded world when the SYS crate is modelled to represent the unsafe bindings to the Vendor-provided SDK for the MCU, as well as the vendor-specific linker args (including custom linker scripts and whatnot) that have to be passed through to the binary crate.

Just to chime in: This also broke our build, in embedded context. In RIOT-rs, one crate compiles and links a static library (from C code). that crate also needs to link in newlib (-lc_nano). Previously, with "-Zextra-link-args", that worked fine. Not anymore.

Opening a poll to check consensus among the rest of the team.
Should we confirm that the current behavior is correct, and dependencies shouldn't be able to affect the linker command-line of the depending crate without some kind of explicit opt-in from the depending crate?
@rfcbot close

Opening a poll to check consensus among the rest of the team.
Should we confirm that the current behavior is correct, and dependencies shouldn't be able to affect the linker command-line of the depending crate without some kind of explicit opt-in from the depending crate?
@rfcbot close

My final comment is that this is poor for the embedded space where the API crate for a particular device, which includes the necessary linker script for said device, can't send the linker script along to binaries built for the device that depend on the API crate.

I do agree with @Lokathor that not having any form of transitive arguments passing from the API/SYS crate to the binary one is very suboptimal. At the same time, I so agree that such a scheme would ideally require an explicit opt-in from the binary crate.
My only concern is that if the current restricted scheme is stabilized in its current form, future transitive + explicit opt-in extensions might take  a lot of time to stabilize or not receive enough attention for that to happen at all in the foreseeable future.

To be clear, I'm quite amenable to proposals for opt-in linker arguments; I just wouldn't want them to happen implicitly without the explicit opt-in from the top-level crate.


travis fail on repo name

Skipping a deployment with the script provider because this repo's name does not match one specified in .travis.yml's deploy.on.repo: IBM/conversational-banking

Hi Mark, I have updated the repo-name and attached the buildcheck link of travis in Readme.md.
we do not have admin rights, so maybe you can re-trigger a build for us.

travis tests are still not implement (so currently fail) but this specific issue is closed.


STAC API not fully up to date?

hey! I'm using something like this to query the STAC API:
from pystac_client import Client

SENTINEL2_COG_API = "https://earth-search.aws.element84.com/v0"

geometry = {'type': 'Polygon',
 'coordinates': [[[-94.8202725, 46.4500799],
   [-94.8202725, 46.455147],
   [-94.8132087, 46.455147],
   [-94.8132087, 46.4500799],
   [-94.8202725, 46.4500799]]]}

start_date = "2023-05-01"
end_date = "2023-05-30"

client = Client.open(SENTINEL2_COG_API)
collection = "sentinel-s2-l2a-cogs"  # Sentinel-2, Level 2A, COGs
search = client.search(
        collections=[collection],
        intersects=geometry,
        datetime=f"{start_date}/{end_date}",
)

This doesn't yield any results. However, using another Sentinel data provider with the same geometry and dates, I get 7 results.
And if I manually search the s3 cogs bucket, I see those 7 results:
aws s3 ls s3://sentinel-cogs/sentinel-s2-l2a-cogs/15/T/UM/2023/5/

                           PRE S2A_15TUM_20230502_0_L2A/
                           PRE S2A_15TUM_20230509_0_L2A/
                           PRE S2A_15TUM_20230512_0_L2A/
                           PRE S2B_15TUM_20230504_0_L2A/
                           PRE S2B_15TUM_20230507_0_L2A/
                           PRE S2B_15TUM_20230514_0_L2A/
                           PRE S2B_15TUM_20230517_0_L2A/

Is it possible that the STAC catalog isn't entirely up to date? I get results for older dates.
Thanks

Same here. It looks like it's been happening since May. It works fine on April images.

Hi,
Are there any workaround for now?

If I understand this correctly, the v0 STAC API is no longer supported. There is now the v1 endpoint: https://earth-search.aws.element84.com/v1 . Sentinel-2 L2A COGS should now be reachable as the sentinel-2-l2a collection.

Can access it using pystac or satsearch packages in python? Have you guys tried it out? Thanks for your response.

@fmariluis, you've got the right endpoint now.  Many updates.  Notes can be found, and issues can be filed here for the new v1 endpoint: https://github.com/Element84/earth-search#readme

thank you @ircwaves!


about log directory logHome_IS_UNDEFINED

When the application attach pinpoint, there will be a logHome_IS_UNDEFINED log directory, it will write the business systems log have also come in.  as follew:

pinpoint version:1.6.0-snapshot

which WAS did you test with? WebLogic?

is linux user name,i already know  the root cause ,The problem is caused by the logback.  thanks


Iterating through the cache....

Hi...
What is the idiomatic way of iterating through the cache ?
There is no "iter()"/into_iter()" etc.
At least there should be  a "keys()" method so I can iterate through the values...
Or am I missing something ?
Thanks
JR

Hi @JRAndreassen
Are you looking for iter() method in moka cache? or moka-cht (concurrent hash table)?
If the former, which Cache are you trying to use? (moka::sync, moka::future, ...)
https://docs.rs/moka/latest/moka/#examples
As of moka cache v0.8.1, an experimental moka::dash::Cache has iter() method, but others are not.
https://docs.rs/moka/latest/moka/dash/struct.Cache.html#method.iter

Hi @tatsuya6502 ,
I'll move it to moka...


:arrow_up: Get Started UWP => RC1

We could also update the OnConfiguring example to utilize changes made in https://github.com/aspnet/Microsoft.Data.Sqlite/pull/161. Users should be able to specify options.UseSqlite("Filename=Blogging.db") which will automatically be put into the AppData.LocalFolder path.

:shipit:


GreedyIK does unnecessary work to generate the error message

While reviewing #240 I noticed that the GreedyIK planner generates collision_error anytime a call to FindIkSolution fails. This requires the expensive process of looping over all IK solutions and calling CheckCollision and CheckSelfCollision on them.
However, this isn't a terminal error. This means that we may repeat this process several times - even if the final plan is successful.
@lgw903 Can you take a look at this?

@mkoval @lgw903 I am interested to join the discussion on this.  I've noticed some similar code in PlanToEndEffectorPose() in SnapPlanner.

I took a look at PlanToEndEffectorPose in SnapPlanner and don't see an issue. It only calls FindIkSolutions to generate an error message if FindIkSolution fails. What do you see as the issue?


Epub & Html commands

Hey Dan, looks like you did all the heavily lifting for the Epub and Html commands already. Just reorganised the code a bit and implemented a cmd variable which determines whether PDF, EPUB or HTML will be output (probably best to do some refactoring there as well to pass the cmd variable as a parameter in the function calls).
Included epub-gen for the actual Epub generation. Haven't tested it yet with multiple URLs and I think due to the options object for epub-gen there may be some work still to optimise the Epub generation (i.e. one object per URL in the content array). Also would be good to suppress the epub-gen console output.
HTML is just saved using the Node.js fs module. Again, haven't tested it yet with multiple URLs.

Thank you for getting the ball rolling!
I'd actually prefer if we duplicate code for pdf / epub / html generation so that the PR is more clear-cut and doesn't interfere to much with the other PRs and work-in-progress, leaving the abstraction task of finding the common thread between the tasks to a later iteration.
(I'll add other, more specific, comments in the code)

Regarding package-lock.json, I'd like to not include it in the repository, since it interferes with yarn.lock. There's a guide about dealing with it, but the TL;DR is creating a .npmrc file that includes the line:
package-lock=false

And including package-lock.json in .gitignore.

👍 will have a look at reverting the structure changes and remove the package-lock.json.


Unit test contains bad access

JDL reports:
in .\src\mediafire_sdk\uploader\unit_tests\upload_fil e.cpp, the variable "mf::api::SessionMaintainer stm" declared at line #212 (or some other associated session-related object) appears to be referenced and used internally within the processing initiated by io_service.run() at line#271, outside of the scope in which SessionMaintainer is declared, leading to accesses on a non-existent object.

Should be fixed by 918498c.


Please optimazie search function

Issue Type: Feature Request
Hi,
Could you please add support for these demands?

searching key word for multi specific file type;
UEFI file type: .hfr,.inf, *.vfr;

thanks!
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

I don't understand what you are asking for. Please include more specific details


compatibility issue

I can't interact with rockets from Ad Astra when Advanced Genetics is installed

It also seems to mess with Immersive Aircraft, unfortunately.


Pip8

Migrate requirements to pip8 hash checking mechanism
Remove peep
Add pipstrap
Upgrade travis and docker tests
Extra: separated requiments used to test and run the app with the ones
needed for development only (i.e. building docs, debugging, etc)

@peterbe r?

I've grown quite fond of every project having a requirements.txt. I understand the hack you did with -r base.txt but all that just for the sake of requirements/docs.txt? You could just instead create docs/requirements.txt which feels more natural to me.
Also, if someone wants to add another dependency they might be templated to write hashin somepackage which will, by default, look up the latest version AND put it into ./requirements.txt.

We used to have peepin in the requirements.txt. Should we include hashin instead?

I've grown quite fond of every project having a requirements.txt. I understand the hack you did with -r base.txt but all that just for the sake of requirements/docs.txt? You could just instead create docs/requirements.txt which feels more natural to me.
Also, if someone wants to add another dependency they might be templated to write hashin somepackage which will, by default, look up the latest version AND put it into ./requirements.txt.

Makes sense. I started doing the separation trying to separate base, dev and docs but then dev is needed in the docker image to be able to run all the tests and ship the same image you've tested against. So dev ended up in base and then docs is the one left out because it's certainly not needed in the docker image and more importantly we don't need to track all the hashes for documentation builders :)
I'll switch to the one you suggest.

We used to have peepin in the requirements.txt. Should we include hashin instead?

re-added!

@peterbe updated to address your comments

What about

We used to have peepin in the requirements.txt. Should we include hashin instead?

??

What about
We used to have peepin in the requirements.txt. Should we include hashin instead?

??

See https://github.com/mozilla/sugardough/pull/114#issuecomment-178538697

Grr. My bad. I didn't read for it. I searched and I must have typo'ed. It's clearly there.
r+

woohoo!


Corrected the comment to match PEP8

In ast.py file in repository we get warning from linter: "PEP 8: E501 line too long (129 > 120 characters)" in line 32 https://github.com/yegor256/cam/blob/428b12f04de249ff8f009c2199d9b947695dbf43/metrics/ast.py#L32
I suggest to fix it

@nikzor read this please: https://www.yegor256.com/2024/04/01/ping-me-please.html


[Discussion] digital marker traits, such as digital::StronglyDriven, digital::OpenDrain, digital::OpenCollector, etc.

Many MCUs (the STM32s especially) implement a plethora of different output options for their GPIO pins. A driver generally has specific output requirements for its pins -- but enforcing these with API traits will mean there will be many traits available, all implementing similar or identical APIs -- i.e. OutputStronglyDrivenPin, OutputOpenDrainPin, OutputOpenDrainPullupPin, etc.
Advantages

One API for high-level pin mode (IoPin, InputPin, OutputPin), with additional traits providing fine-grained configurability
Unusual combinations easy to express (OutputPin + OpenDrain + PullUp)

Disadvantages

Possible huge proliferation of implementer types

The actual pin driving code will likely look similar for all, but initialization will be different. Does this force too much duplication/boilerplate?
Could this be handled by a builder-like pattern? i.e. pin init functions which consume a type with/without the marker trait, change the config, and return a type without/with the trait?

Possibility of expressing impossible bounds (i.e. OutputPin + StronglyDriven + OpenDrain).

Mostly a problem from the driver writer's standpoint, and it will become quickly clear that no available HAL provides the type needed

Example driver usage
pub struct BitBangedI2c<D, C> {
    sda: D,
    scl: C,
}

impl<D, C> BitBangedI2c<D, C> {
    pub fn new<D, C>(sda: D, scl: C) -> BitBangedI2c<D, C>
    where
        D: digital::IoPin + digital::OpenDrain,
        C: digital::IoPin + digital::OpenDrain,
    {
        BitBangedI2c { sda, scl }
    }
}

Please find a related  discssion here:
https://github.com/japaric/stm32f103xx-hal/pull/51


Build for PR 1082

Description
The build files for PR 1082, following the process described in https://github.com/facebookresearch/fairo/tree/main/droidlet/dashboard/web#checking-in-your-changes
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[X] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[X] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
These are the build files for PR 1082, in which I updated the web dashboard to a chat interface.
Checklist:

[ ] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[X] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

Codecov Report

Merging #1111 (1955e86) into main (840ac43) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1111      +/-   ##
==========================================
+ Coverage   34.05%   34.10%   +0.05%
==========================================
  Files         343      344       +1
  Lines       33534    33787     +253
==========================================
+ Hits        11419    11524     +105
- Misses      22115    22263     +148

Impacted Files
Coverage Δ

agents/droidlet_agent.py
41.50% <0.00%> (ø)


feat: use the enabled field from MarketMap

Closes BLO-1089

Adding a preview for this to see how it runs


Table not rendered in modern Outlook Client 3.1.0 > 3.11.0

There seems to be two versions of Outlook in use by Microsoft at the moment. One dependent on the WebView2 which I think is shared with their Android app.
When using this modern version my e-mail template that was working before now no longer renders the table data.
Here is an example that demonstrates the problem.
<mjml>
  <mj-head>
    <mj-title>test</mj-title>
    <mj-preview>test</mj-preview>
    <mj-attributes>
      <mj-all font-family="Calibri, Arial"></mj-all>
      <mj-table></mj-table>
      <mj-text font-weight="400" font-size="16px" color="#000000" line-height="24px"></mj-text>
    </mj-attributes>

  </mj-head>
  <mj-body background-color="#E7E7E7" width="700px">
      <mj-section  background-color="#000000" padding-bottom="15px" border-radius="10px" >
      <mj-column width="100%">
      </mj-column>
    </mj-section>
    <mj-section padding-top="15px"></mj-section>
     <mj-section background-color="#000000">
      <mj-column width="100%">
      </mj-column>
    </mj-section>
    <mj-wrapper padding-top="0" padding-bottom="0" css-class="body-section">
      <mj-section background-color="#ffffff" padding-left="15px" padding-right="15px">
        <mj-column width="100%">

  <mj-text>

Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum: 3.
       Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum <a href="mailto:bleggity.blah@dfsdsffd.com?subject=RE: lorem ipsum -<EMAIL_ADDRESS>ipsum.
</mj-text>
<mj-text color="#212b35" font-weight="bold" font-size="20px" align="center">lorem ipsum</mj-text>
<mj-table>
 <colgroup><col/><col/><col/><col/></colgroup>
loremipsum	loremipsum	loremipsum	E-loremipsum

blehy<EMAIL_ADDRESS></mj-table>

        </mj-column>
      </mj-section>
      <mj-section background-color="#ffffff" padding-left="15px" padding-right="15px" padding-top="0">
      </mj-section>
      <mj-section background-color="#ffffff" padding-left="15px" padding-right="15px" padding-top="0">
        <mj-column width="100%">
          <mj-divider border-color="#DFE3E8" border-width="1px" />
        </mj-column>
      </mj-section>
      <mj-section background-color="#ffffff" padding="0 15px 0 15px">
      </mj-section>
    </mj-wrapper>
  </mj-body>
</mjml>

When looking at the rendered html it looks like the table gets created with a 0 dimension.
It seems to work fine with the mjml "try it live" feature: https://mjml.io/try-it-live/LKFi1sfr2V
Interestingly enough, it does not happen with the older Outlook Desktop version (the one without webview)
Outlook Version Desktop:
Microsoft Outlook Version 1.2024.529.200 (Production).
Client Version is<PHONE_NUMBER>3.09 .
WebView2 Version is 125.0.2535.79
Android Outlook Version:
4.2422.0
Looks correct in old Desktop Outlook:

Table data is missing in Android or Newer Outlook Version based on WebView

I have added your example to our tests. We run the code through mjml (using Node) and then our own implementation and compare the results on a semantic level (so we ignore stuff like attribute orders and whitespaces and so on). And the test is green. So I would say, that the problem is more on the mjml level and not on our port.

Yeah, I think you're right.
Problem persists when I take generated HTML from MJML try-it-live and send with powershell's send-mailmessage.
I've logged the issue upstream on MJML's github.
#2869
Thanks for the quick response

I have subscribed to the issue, so that we can also implement the fix if they decide to solve the problem. Feel free to ping me, just in case I forget it.

I guess I can close that.

Yes, thanks for the help @SebastianStehle


Issues blocking leaving playtest

Description

[ ] #17313
[ ] #19606
[ ] #19672
[ ] #25204
[ ] #25293
[ ] #19563
[ ] #19853

Should we pin this? Just so more people see it?

oh god I sneezed and hit the X


Update ranking email to be more lenient on 2nd-10th place teams

Currently we ask the 2nd-10th place teams for official transcripts which is a lot of work considering we don't really need an official transcript from them. Instead I think we should clarify that we will accept unofficial transcripts for the 2nd-10th place teams.

Coverage remained the same at 97.333% when pulling 1e4e7b3b3cb9870efced3a82dfa96fb9dd96d0ec on rankingEmailFixes into 6bdcda7ed58a50a1d7e3185d5024ef9ef3946909 on master.

Coverage remained the same at 97.333% when pulling 9402a3d794b16e8e2d517b272548ea99821b1367 on rankingEmailFixes into e307a3af1e3f0b2f2e9b97b7c06c2d3895af8074 on master.


Jesse: Watch reclaim[\W_]+right[\W_]+recovery[\W_]*+group

Jesse requests the watch of the watch_keyword reclaim[\W_]*+right[\W_]*+recovery[\W_]*+group. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

reclaim[\W_]*+right[\W_]*+recovery[\W_]*+group has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


sidestep nullable error

After updating to Flutter 3, I started getting build errors as in issue #32.  This was because the variable used was nullable, but the method required a non-nullable.  We already had that!  so I just use it directly.

@sshipman Seems this branch has conflict, can you fix?

Yeah, but it's basically a one liner.  It'll be quicker to reproduce the
fix in a new branch.  I can't get to this for several hours (actual job)
On Tue, May 17, 2022, 12:22 PM Katekko @.***> wrote:

@sshipman https://github.com/sshipman Seems this branch has conflict,
can you fix?
—
Reply to this email directly, view it on GitHub
https://github.com/incrediblezayed/file_saver/pull/37#issuecomment-1129232930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABA6P2NX2JLVCLH3IKTVRLVKPWXVANCNFSM5VWNZDGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

merge conflicts resolved.  Please sanity check!

@incrediblezayed  @clong1995  May you can check for us?

I will, but tbh, I did fix that specific issue in my latest commit itself

I will, but tbh, I did fix that specific issue in my latest commit itself

Nice, thanks for your time.
Maybe can you publish on the pub.dev?

specific

Yes I will, as soon as possible

Hi, @incrediblezayed could you pls publish to pub.dev? This error prevents my app from building on android. Thank you for your time :)

Hi, I'm so sorry, I'll check and update today