NodePort Not Working in Conjunction with Network Policies

I need to isolate the network traffic for each individual namespace in a v1.18 K8 cluster.  I have created a deny all ingress traffic network policy and an allow all ingress traffic from the Ingress Controller namespace network policy for each application namespace.  This allows all application ingress traffic external to the cluster to reach applications internal to the cluster via Layer 7 but restricts and internal namespace to namespace traffic and it works like a champ.  The issue is with external cluster traffic attempting to reach internal cluster applications via TCP Layer 4 - NodePort.  Adding the network policies breaks NodePort.  I created a GlobalNetworkPolicy to allow the ingress host NodePort traffic (https://docs.projectcalico.org/security/kubernetes-node-ports) but it still does not work.  Any ideas?
Expected Behavior
curl http://myapp1.example.com:30000  - will reach the application behind the NodePort service (30000-->80).  This works prior to applying the network policies but not after.
Current Behavior
curl http://myapp1.example.com:30000  - cannot reach the application behind the NodePort service (30000-->80)
Steps to Reproduce (for bugs)

Create namespace app1
Deploy a simple webapp with a NodePort service NodePort

apiVersion: v1
kind: Service
  name: app1
  namespace: app1
spec:
  ports:
  - nodePort: 30000
    port: 80
    protocol: TCP
    targetPort: 80
  selector:
    app: app1
  type: NodePort

Verify you can reach the application
curl http://myapp1.example.com:30000
Apply the deny-from-other-namespaces network policy to the app1 namespace

    kind: NetworkPolicy
    apiVersion: networking.k8s.io/v1
    metadata:
      namespace: app1
      name: deny-from-other-namespaces
    spec:
      podSelector:
        matchLabels:
      ingress:
      - from:
        - podSelector: {}

Apply the allow-from-ingress-namespace

    kind: NetworkPolicy
    apiVersion: networking.k8s.io/v1
    metadata:
      namespace: app1
      name: allow-from-ingress-namespace
    spec:
      podSelector:
        matchLabels:
      ingress:
      - from:
        - namespaceSelector:
            matchLabels:
              app: ingress-controller

Apply the allow-cluster-np-internal-ingress-only GlobalNetworkPolicy

apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
  name: allow-cluster-np-internal-ingress-only
spec:
  order: 20
  preDNAT: true
  applyOnForward: true
  ingress:
    - action: Allow
      source:
        nets: [<IP_ADDRESS>/23, <IP_ADDRESS>/16]
    - action: Deny
  selector: has(kubernetes-host)

Verify you can reach the application - you will not be able to.
curl http://myapp1.example.com:30000

Context
Isolating internal namespace to namespace network traffic with network policies breaks ingress using NodePort.  We need external ingress into the cluster for non-Layer 7 traffic.
Your Environment

Calico version: Calico v3.11.2
Kubernetes version: v1.18 (baremetal cluster)
Operating System and version: VMware Photon OS 3.0
CRI and version: containerd  v1.3.4

  ingress:
    - action: Allow
      source:
        nets: [<IP_ADDRESS>/23, <IP_ADDRESS>/16]
    - action: Deny
  selector: has(kubernetes-host)

In policy rule example, what are those nets? Are they your node IP ranges or something else?

Hey @caseydavenport,  The <IP_ADDRESS>/23 is the IP range for our nodes and the <IP_ADDRESS>/16 is for our pods.  I initially tried it with just the IP range for our nodes (<IP_ADDRESS>/23) but once that didn't worked I added the pod IP range to see if that helped.

Hm, so the traffic that will be hitting your NodePort services pre-DNAT will have a source IP address of whatever originated the traffic - in your case is that a pod and/or node? Or is it something outside the cluster?

@caseydavenport - the traffic hitting the NodePort is ingress traffic coming from applications with source IP addresses outside of our cluster.   The goal is to prevent any east/west traffic between namespaces within the cluster but allow all external ingress via Layer 7 through the Ingress Controller and Layer 4 via Nodeport.

So I think for that you'd want something like this:

Policy in namespace X which allows only from namespace X ("allow from same namespace")
Policy in namespace X which allows from ingress namespace (assumes that your ingress pods are NOT host networked)

^ This is what you already have, and will get you the prevent east/west between namespaces except for the ingress namespace behavior. But of course, as you discovered, doesn't allow traffic that enters via a NodePort, since that traffic is SNAT'd before it reaches the pod.
I think you might be looking for a policy like this one in order to allow traffic to your NodePort:
apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
  name: allow-cluster-np-internal-ingress-only
spec:
  order: 20
  preDNAT: true
  applyOnForward: true
  ingress
    - action: Allow
      protocol: TCP
      destination:
        selector: has(kubernetes-host)
        ports: [30000]
  selector: has(kubernetes-host)

This of course assumes you have host endpoints for each of your kubernetes nodes. It should allow all traffic to your service that uses the node port 30000. If you want to restrict who is able to access the nodeport, you can add a source section to limit to certain selectors or IP addresses.
Give that a shot and let me know if it works - I might have missed something in your set up :)

@caseydavenport - Thank you for the suggestion.  I removed my entire previous setup and started from scratch.

Deployed two test applications:  App1 using L7 Ingress and App2 using NodePort on 30000
Verified both applications were reachable - success
Applied your suggested deny all Network Policy

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  namespace: vcs
  name: deny-from-other-namespaces
spec:
  podSelector:
    matchLabels:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          asi: vcs

Tested both applications - both unreachable as expected.
Applied the Allow Ingress from the Ingress Controller namespace Network Policy

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  namespace: vcs
  name: allow-from-ingress-namespace
spec:
  podSelector:
    matchLabels:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          app: tanzu-system-ingress

Tested both applications - App1 using L7 Ingress worked as expected and App2 using NodePort on 30000 unreachable as expected.
Created a host endpoint for each of my worker nodes

apiVersion: projectcalico.org/v3
kind: HostEndpoint
metadata:
  name: k8-tkg-prod-md-0-948f59b86-pbb4s-eth0
  labels:
    kubernetes-host: ingress
spec:
  interfaceName: eth0
  node: k8-tkg-prod-md-0-948f59b86-pbb4s

Created the GlobalNetworkPolicy

apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
  name: allow-cluster-np-internal-ingress-only
spec:
  order: 20
  preDNAT: true
  applyOnForward: true
  ingress:
    - action: Allow
      protocol: TCP
      destination:
        selector: has(kubernetes-host)
        ports: [30000]
  selector: has(kubernetes-host)

Tested App2 - App2 using NodePort on 30000 is still unreachable :-(

I really had high hopes this was going to work.

@reddog335 I think I know what is going on, and, I believe it is a bug in the example in our docs.
Specifically, the issue is that the destination.selector field needs to resolve to a set of IP addresses in order to be enforced. However, the HostEndpoints you've created (and the one in the docs) do not have the expectedIPs field set.
You can test this by modifying your host endpoints to have the expectedIPs field set with the addresses of eth0 that you intend for nodeport traffic to hit. If that gets traffic flowing, which I expect it will, then I think we've found the culprit.
Once that is working, you can either ensure your HEPs have the right addresses, or you might want to look at enabling automatic host endpoints so that you don't need to create them by hand: https://docs.projectcalico.org/archive/v3.16/security/kubernetes-nodes#automatic-host-endpoints

@caseydavenport - Thank you for the update.  I added the expectedIps to my HEPs and it still did not work.
apiVersion: projectcalico.org/v3
kind: HostEndpoint
metadata:
  name: k8-tkg-cya-lab2-md-0-8d88f59d6-rzxvg-eth0
  labels:
    kubernetes-host: ingress
spec:
  interfaceName: eth0
  node: k8-tkg-cya-lab2-md-0-8d88f59d6-rzxvg
  expectedIPs:
  - 10.<redacted>
---
apiVersion: projectcalico.org/v3
kind: HostEndpoint
metadata:
  name: k8-tkg-cya-lab2-md-0-8d88f59d6-t5drm-eth0
  labels:
    kubernetes-host: ingress
spec:
  interfaceName: eth0
  node: k8-tkg-cya-lab2-md-0-8d88f59d6-t5drm
  expectedIPs:
  - 10.<redacted>
---
apiVersion: projectcalico.org/v3
kind: HostEndpoint
metadata:
  name: k8-tkg-cya-lab2-md-0-8d88f59d6-xzvf6-eth0
  labels:
    kubernetes-host: ingress
spec:
  interfaceName: eth0
  node: k8-tkg-cya-lab2-md-0-8d88f59d6-xzvf6
  expectedIPs:
  - 10.<redacted>

After investigating further, the source IP address of the ingress traffic shows up as a Pod network address (100.111.191.###), not the worker node address.  I was able to get around this by changing ipipMode from Always to Never in the default-ipv4-ippool ippool.  After making this change, I was able to get nodePort working with a native K8 Network Policy so I no longer required the GlobalNetworkPolicy and HEPs.
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  namespace: vcs
  name: allow-from-node-port
spec:
  podSelector: {}
  ingress:
  - from:
    - ipBlock:
        cidr: <IP_ADDRESS>/8
    ports:
    - protocol: TCP
      port: 80
    - protocol: TCP
      port: 8080

I added the expectedIps to my HEPs and it still did not work.

Drat.

the source IP address of the ingress traffic shows up as a Pod network address (100.111.191.###),

Ah, yes. If you're using encapsualtion then host->pod traffic will use the IPIP tunnel so that traffic is symmetrical. The IPIP tunnel device on each node is given an address from the pod range in order to enable this.


MGMT-14464 - Break Cluster network host prefix field description text into help and description text

https://issues.redhat.com/browse/MGMT-14464
Before:

After:

Looking great!
/approve


Pluggable Scheduler/Provider backends

While writing tests I came across the fact that we don't only have to check with mesos to see if an incoming request for a token is valid.
If possible we could add:

A testing backend that fails/grants requests based on some test requirements
k8s?
nomad?
swarm?

Would there be an interest in maybe cooperating on adding support for ECS or a plain Docker?


Output doesn't match with the data in the ledger

Thank you Balaji for share the resource. I have a query regarding the output I got.
Everything worked as said in the read me, but the output data is not the same as the ledger data. Am I doing anything wrong?
Output I got by running this chaincode "java -cp blockchain-client.jar org.app.chaincode.invocation.QueryChaincode" is
INFO: {"make":"Chevy","model":"Volt","colour":"Red","owner":"Nick"}
But I couldn't find the same in the init part of the .go code in the fabcar sample.
Do i need to persist the same into the ledger first? If yes, is there any API in the code sample to do that?
Thank you

Hope previous response helped you. Hence closing this issue, plz reopen or open a new issue if you have any question.

Hi Mahesh,
Sorry for the delay in responding. Yes, I'm clear now.
Can I know in which chaincode you are running the invoke transaction, I couldn't locate it exactly.


influxdb database stores only the latest message with the same timestamp always.

@chombium - Moving forward the influxdb database stores only the latest message with the same timestamp always. No matter what. Even more, Grafana doesn`t show even the only latest message that is written to influxdb

Am i missing a trick here?
Originally posted by @howdyharry in https://github.com/mainflux/mainflux/issues/759#issuecomment-501734060

I solved it by removing the "bt" field from postman, but still the data is not visible in grafana.

It is now visible on Grafana as well.


CDE-14 Repository selection step

Issue #CDE-14
Problem:  Repository selection step
Solution: Created UI for repository selection step

thanks @vidhya-metacell


AKV to AKS integration needs clarification and testing

[Hi, I was following the AKV to AKS integration and it seems as though it contains a couple of errors.  Midway down the page where there are instructions to Install AAD pod identity and you create role assignments.  It makes it look as though the NODE_RESOURCE_GROUP is a regular group, but should indicate that this can be found with by running "az aks show -g $RESOURCE_GROUP -n $AKS_CLUSTER --query nodeResourceGroup -o tsv"   And I'm not positive but shouldn't the assignee be the Object ID rather than client ID for the cluster?

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

ID: eee999c1-32dd-d014-40df-8027adee1258
Version Independent ID: 19a29c09-79f8-580a-841f-873e2801da56
Content: Integrate Azure Key Vault with Kubernetes
Content Source: articles/key-vault/general/key-vault-integrate-kubernetes.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@carmodyquinn
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@carmodyquinn  AKS implemented new version of CSI driver with Azure Support. We deprecated old key vault tutorial, please check new guide provided by AKS team here:
https://docs.microsoft.com/en-us/azure/aks/azure-disk-csi
If there are any issues, please create item on their documentation.
#please-close


Feature Request: Add a Notes input

Could you add another input for the Notes URL?
Use case: I don't use a static changelog file, I use the link to the Github release page instead, so my links are dynamic.

f2111092e5f3b2e740e1aaa1b71c6047e4c645fa

Now available in v1.0.2.  If you are just using the @v1 tag, then you should pick up the change automatically


[main] SRVLOGIC-390: update the prod templates to include the operator memory increase and adjust the SonataFlow-Builder.containerfile

Description of the change:
Motivation for the change:
Checklist

[ ] Add or Modify a unit test for your change
[ ] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

ignore for now the check headers failure, I fixed it in upstream already and when I sync the midstream main branch with upstream main it will be fixed.


Submission [Question]

Hello,
@Jetski5822 Do you have in plan to make Submissions for Plugins?

At some point - we take contributions and ports from the old codebase, but right now we are focused on how the V2 stuff will look - early days :)


Support Go to definition for defined constants

In one file, I have a define like so:
define('someConstant', "Foo");

In another file, (after calling require_once for the above file), I call it like
echo 'My name is ' . someConstant;

Go to definition doesn't work on someConstant

resolved in v0.8.0


Fix behaviour of CreateDataset in case of an timeout creating the image

Old code did not return an error in the timeout case
Delete dataset in case of a timeout
Write test to ensure that timeouts are handled correctly
fixes #11

Thanks @simonswine
I'd be interested to know whether Kubernetes dynamic volume provisioning fails unless we make this change.
In any case, please address or answer the comments above.

Thanks for reviewing @wallrj
The biggest problem/bug right now for k8s dynamic provisioning is that if CreateDataset runs into a timeout, it will return nil, nil which crashes Kubernetes Controller Manager. This behaviour has to be fixed as soon as possible to move the dyn prov PR forward..


Feature Flag Composition

When loading feature flags, if multiple feature flags have the same name, then they should be last one wins.

[ ] DotNet Feature Management Library, local file
[ ] Python Provider
[ ] Python Feature Management library
[ ] Verify Spring Feature Management Library
[ ] Verify JavaScript Feature Management Library
[ ] Add Validation Test

Is there any reason to break the current design (the first one win) which is more efficient)?


Issue presenting large ancient change numbers

Hi again, @Beskhue.
I'm not sure if I introduced it or not, but it seems the presentation of ancient change levels for copying isn't working so well for very large numbers:

At roughly 1e12 it starts formatting them in a way that can't be interpreted by the ClickerHeroes game. I'll have a go at solving it when I get back home to a tolerable computer, but it won't be for a few days.

Thanks for the report. This output format should be understood by Clicker Heroes. For example, 123e2 would be interpreted (correctly) as 1.23e4. If you are having issues, please include screenshots from Clicker Heroes and please send me your save file.

Oh, that's actually really cool. I was quite certain I'd tried and failed pasting that format into the game client, but I'll double check at next ascension. You're probably right.

I just tried pasting in 1e12 and that definitely works. There's apparently no issue beyond my strange previous inability to make it work.

Thanks for the update!


Manage timezone when a live is scheduled

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
When a live is scheduled we don't save any timezone, we save it in UTC. But When we want to display the scheduled date in a mail for example we have no other solution than displaying it in UTC. We would like to display the date and time at a given timezone
Describe the solution you'd like
When an instructor schedule a webinar, it should specify the timezone and we should save this information. Once we have it we always display the date and time with the configured timezone.

So you will also need to record the timezone when a user registers to the live so you know what timezone to use in the email you will send him?


error: could not find native static library MySwiftLib, perhaps an -L flag is missing? When using Cargo workspaces

Problem
When linking a native static library using a build.rs file doesn't work when using Cargo workspaces.
Steps
I have a build.rs file in a Cargo project that something looks like this:
const MACOS_TARGET_VERSION: &str = "10.15";

#[derive(Debug, Deserialize)]
#[serde(rename_all = "camelCase")]
struct SwiftPaths {
    runtime_library_paths: Vec<String>
}

#[derive(Debug, Deserialize)]
struct SwiftTarget {
    paths: SwiftPaths
}

fn main() {
    let profile = env::var("PROFILE").unwrap(); // release / debug
    let arch = env::var("CARGO_CFG_TARGET_ARCH").unwrap();
    let target = format!("{}-apple-macosx{}", arch, MACOS_TARGET_VERSION);

    let swift_target_info_str = Command::new("swift")
        .args(&["-target", &target, "-print-target-info"])
        .output()
        .unwrap()
        .stdout;
    let swift_target_info: SwiftTarget = serde_json::from_slice(&swift_target_info_str).unwrap();
    swift_target_info.paths.runtime_library_paths.iter().for_each(|path| {
        // path = /usr/lib/swift
        println!("cargo:rustc-link-search=native={}", path);
    });

    if !Command::new("swift")
        .args(&["build", "-c", &profile])
        .current_dir("./MySwiftLib")
        .status()
        .unwrap()
        .success() {
        panic!("Swift library MySwiftLib compilation failed");
    }

    println!("cargo:rustc-link-search=./MySwiftLib/.build/{}-apple-macosx/{}", arch, profile);
    println!("cargo:rustc-link-lib=static=MySwiftLib");
    println!("cargo:rerun-if-changed=MySwiftLib/src/*.swift");
}

The project structure looks like this:
MyRustProject
├── Cargo.toml
├── build.rs
├── MySwiftLib
│   └── ...
├── src
│   └── ...
└── target
    └── ...

When I run cargo build, it all compiles without problems.
However, when I include the project in a workspace:
# Cargo.toml

[workspace]
members = [
    "MyRustProject",
    "MyOtherRustProject"
]

.
├── Cargo.toml
├── MyRustProject
│   └── ...
└── MyOtherRustProject
    └── ...

and try to run cargo build again, I get the following error:
error: could not find native static library `MySwiftLib`, perhaps an -L flag is missing?

The stripped down version of the rustc call when invoking cargo build --verbose is:
rustc --crate-name MyRustProject --edition=2021 MyRustProject/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C split-debuginfo=unpacked -C debuginfo=2 -C metadata=93ef0ef370adc8fd -C extra-filename=-93ef0ef370adc8fd --out-dir /..root/target/debug/deps -C incremental=/..root/target/debug/incremental -L dependency=/..root/target/debug/deps -L native=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -L native=/usr/lib/swift -L ./MySwiftLib/.build/x86_64-apple-macosx/debug -l static= MySwiftLib

Possible Solution(s)
No response
Notes
I'm not sure if this is a bug, or if I'm doing something wrong.
Version
cargo 1.58.0 (7f08ace4f 2021-11-24)
release: 1.58.0
commit-hash: 7f08ace4f1305de7f3b1b0e2f765911957226bd4
commit-date: 2021-11-24
host: x86_64-apple-darwin
libgit2: 1.3.0 (sys:0.13.23 vendored)
libcurl: 7.77.0 (sys:0.4.51+curl-7.80.0 system ssl:(SecureTransport) LibreSSL/2.8.3)
os: Mac OS 12.1.0 [64-bit]

This is a consequence of rustc being run from the workspace root, but the link search paths are passed as-is. A workaround is for your build script to always pass absolute paths.
Cargo could perhaps have better handling of relative search paths. It may be tricky due to backwards compatibility, but it could maybe check both locations to resolve it.  It could also provide warnings if the (resolved) search path doesn't exist, which could help diagnose issues, though I'm not sure if it is common to include non-existent paths.


Allow import of nn assigned statuses

I actually think due to some other logic, this might be dead code, but it is more logical and less misleading this way

maybe add a comment?


Help with vcd-cli failure

I am trying to build vcd-cli with mach-nix.
  vcd-cli = mach-nix.buildPythonApplication {
    src = "https://github.com/vmware/vcd-cli/archive/24.0.0.tar.gz";
    name = "vcd-cli";
    version = "24.0.0";
    requirements = ''
      pbr >=1.9
      click >= 7.0
      colorama >= 0.3.9
      keyring >= 10.6.0, <= 12.0.0
      pycryptodome == 3.6.6
      pypiwin32 >= 223;platform_system=="Windows"
      pyvcloud >= 23.0.0, < 24.0.0
      tabulate >= 0.7.5
      unittest-xml-reporting >= 2.2.1
    '';

    providers = {
      _default = "nixpkgs,wheel,sdist";
    };
  };

is giving me this error:
  File "/nix/store/9y059s1mdyipln8nwzgv1q2gwnqzz033-python3.8-pbr-5.4.5/lib/python3.8/site-packages/pbr/hooks/metadata.py", line 25, in hook
    self.config['version'] = packaging.get_version(
  File "/nix/store/9y059s1mdyipln8nwzgv1q2gwnqzz033-python3.8-pbr-5.4.5/lib/python3.8/site-packages/pbr/packaging.py", line 870, in get_version
    raise Exception("Versioning for this project requires either an sdist"
Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name vcd-cli was given, but was not able to be found.
error in setup command: Error parsing /build/source/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name vcd-cli was given, but was not able to be found.
builder for '/nix/store/bbry5mbg5vl2j68jdwd55ga5gypk2mv7-python3.8-vcd-cli.drv' failed with exit code 1

Some packages cannot be installed from github taball, since some metadata is missing there.
In this case you either need the git repository (including the .git directory) or you fetch the tarball from pypi.
You could use for example:
src = mach-nix.fetchPypiSdist "vcd-cli" "24.0.0";

Or you just install it by using mkPython:
let
  mach-nix = import (builtins.fetchGit {
    url = "https://github.com/DavHau/mach-nix/";
    ref = "refs/tags/3.0.2";
  }) {};
in
mach-nix.mkPython {
  requirements = ''
    vcd-cli==24.0.0
    setuptools
  '';
}

I needed to add setuptools. This dependency is missing from the install_requires of vcd-cli. You might want to report that upstream.

@DavHau  it works like a charm. Many many thanks for your help !


Make abstract SceneObject + Entity class

The SceneObject class should be a super class for all objects in the scene, such as jumpmen.
It should expose some common behavior, such as a position and scale.
The Entity class should be a subclass of SceneObject, but should also have a visible component (for now).
Estimated time: 15 m.

Fixed by b3badac.


[feature request] ability to change size of bit placement and removal

this mod is basically unusable for anything that's more complex than making stairs.
it's missing necessary features like drag-to-place, the only way to place bits is to place them one by one, which makes even medium constructions a nightmare. i don't understand why such an important feature is lacking, technically this mod is the best version of a chisel&bits sort of thing, it's just a shame it's missing a core feature like this.
even the chiseling itself is hard, because the iron chisel can't chisel faster than holding left mouse button places blocks, and it removes 1/64th of a block per use and you can't change that. the diamond chisel removes 1/4096ths of a block per use (and is also slow to use), the smart chisel is drag-to-remove though, so you can remove big chunks at once.
but still, if you want to make a block a slab you either have to slowly remove 32 parts, or you have to have walk around the block to precisely remove the part you want to remove with the smart chisel, and you don't always have space to go around an entire block. on top of that if you want to make that slab a double slab from 2 different materials you're stuck there for hours placing 2048 bits one at a time.

and while i'm at it, the ability to remove bits using the bits in your hand, so you don't have to switch tools every time you misplace, would also be a very welcome feature!


Introducing new UIFramework attribute in VS 16.7 Preview 3 above

Docs Build status updates of commit d1de7ed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guides/Create-UI-Controls.md
:white_check_mark:Succeeded
View

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


Confirm Text is PlainTextField not AnyTextField

https://github.com/seratch/slack-web-api-client/blob/e25971057cdc429fbbab50e2070b73c7ef0752d7/src/block-kit/confirm.ts#L5
should be
export interface Confirm {
    title?: PlainTextField;
    text: PlainTextField;
    confirm?: PlainTextField;
    deny?: PlainTextField;
    style?: "primary" | "danger";
}

@zhawtof You're right. This needs to be improved


Update controller dependency graph to the latest

Description

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

See updated graph at: https://github.com/hjiawei/operator/tree/readme-dep-graph#controller-dependency-graph.


Build fails with custom js file

Short description of the problem:
I have a JavaScript file which exports a function init(). I have defined d.ts file for the same and using the function in a ts file.
ionic serve runs fine.
But ionic build fails:
bundle failed: Could not resolve './demo' from /Users/..../app/.tmp/pages/books/demo/demo.component.js
I checked the .tmp/ folder. It doesn't have the JavaScript file copied here.
Steps to reproduce:

Create 3 files:

demo.js
function init() {}
module.exports = init;

demo.d.ts
declare function init(): void;
export = init;

demo.component.ts
import { Component, AfterViewInit } from '@angular/core';

import init from './demo';

@Component({
  templateUrl: 'demo.html'
})
export class DemoBookComponent implements AfterViewInit {
  public show: boolean = false;
  ngAfterViewInit() {
    init();
  }
}

On the CLI:
ionic build gives error whereas ionic serve succeeds.

Which @ionic/app-scripts version are you using?
Ionic 2 after Max's 14th Oct blog update.

I tried moving the JS and .d.ts file to assets/ folder. Again, ionic serve runs fine but ionic build fails with same error. I checked the .tmp/ directory - it does not have assets/ folder, so build is expected to fail. So I believe we should be copying the assets/ folder as well?

Thanks @jgw96 for the mail. So this is the flow:
I have a 3rd party software which outputs the following HTML:
<head>
<script>....</script>
<script>....</script>
</head>
<body>
<div ...>...</div>
</body>

I tried making this HTML as component template, but then realized that Ionic 2 RC removes all <script> tags from the template (BTW, I wish I could control this...).
So what I know do is take the JS inside <script> tags and put in JS file. And export methods to use in TS component file.
It is not possible to convert the JS file to TS as this is 3rd party generated and is fairly complex. Also changing it is not scalable as we move forward. We want that to remain as black box.

@jgw96 Is there any alternative work around as of now? I am not very familiar with webpacks, but would that solve this issue when that CL is merged?

Thanks for the info @shikharls ! So just to be clear, you are trying to put <script /> tags in your component templates?

@jgw96 Sorry for being ambiguous. What I have from a 3rd party is a self-sufficient HTML file which script tags. Now there are two ways to integrate this:

Take the entire HTML file and make it as templateUrl of a @Component. The problem here: Ionic removes script tags from the template.

Separate the script tags from the HTML and make 2 files: 1 pure HTML which would be templateUrl of a @Component, second, a JS file which would have JS from the script tags and expose the methods using exports and .d.ts file. The problem here: This JS files is not copied over when building and build fails. Also, I would not like to put these JS files in index.html as this is not scalable for us.

I think Ionic should address both of these. As of now, any workaround would be great.

@shikharls Does this work in a normal Angular app? Such as one generated by the angular cli

@jgw96 To be very frank, I have never used angular cli. These work well with Ionic 1. But given Angular does not remove the script tags, and also has no custom script like @app-scripts, I think it should work fine.

Hello! After further review I am going to be closing this issue for now. Angular 2 components are not designed to have script tags in the templates. Also, not only are they not designed to have script tags in them, but this will also cause other issues with things like AoT compile. While this may have worked in Ionic 1 / Angular 1, Ionic 2 is built on Angular 2 which is an entirely different architecture.


Create Organization with avatar fails

Describe the bug
As a vendor, creating organizations fails when an optional 'profile picture' is uploaded/chosen. Choosing an image at the time of 'Create Organization' prevents the organization from being created. A workaround is to leave the image out (optional) and create the organization without an avatar. Adding an image after the organization is created also fails.
To Reproduce
Steps to reproduce the behaviour:

Sign in as a vendor (via GitHub)
Go to 'My Profile -> Organizations -> Create Organization'
Choose Image in Profile Picture, upload an image from local machine
Fill out required fields in the form
Click 'Create Organization'
see error 'Please select a different avatar' and "502 Bad Gateway" on inspection.

Expected behaviour
Uploading an image should be possible. It should not block the creation of an organization.
Screenshots

Additional context
Problem can not be re-created locally, but has been verified on test and prod.

resolved in #298


feat: add 'proper' argument parsing

use clap crate and enum for arg parsing.

parsing to usize and then usize to back to String seems unnecessary / redundant.

Closes #26

here is a good reference: https://github.com/mosure/bevy_args


master build is failing

Trying to build the master branch locally results in:
[INFO]
[INFO] --------------------< org.glassfish.jaxb:jaxb-core >--------------------
[INFO] Building JAXB Core 4.0.0-SNAPSHOT                                [14/38]
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for jakarta.xml.bind:jakarta.xml.bind-api:jar:4.0.0-RC3 is missing, no dependency information available
[WARNING] The POM for jakarta.activation:jakarta.activation-api:jar:2.1.0 is missing, no dependency information available
[WARNING] The POM for org.eclipse.angus:angus-activation:jar:1.0.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Jakarta XML Binding Implementation 4.0.0-SNAPSHOT:
[INFO]
[INFO] JAXB BOM ........................................... SUCCESS [  0.153 s]
[INFO] JAXB BOM with ALL dependencies ..................... SUCCESS [  0.005 s]
[INFO] JAXB External parent ............................... SUCCESS [  3.290 s]
[INFO] RelaxNG Datatype ................................... SUCCESS [  0.827 s]
[INFO] RNGOM .............................................. SUCCESS [  2.159 s]
[INFO] XSOM ............................................... SUCCESS [  9.716 s]
[INFO] Jakarta XML Binding Implementation ................. SUCCESS [  0.216 s]
[INFO] JAXB TXW parent .................................... SUCCESS [  0.009 s]
[INFO] TXW2 Runtime ....................................... SUCCESS [  0.250 s]
[INFO] Codemodel .......................................... SUCCESS [  0.015 s]
[INFO] Codemodel Core ..................................... SUCCESS [  0.651 s]
[INFO] TXW2 Compiler ...................................... SUCCESS [  0.183 s]
[INFO] Codemodel Annotation Compiler ...................... SUCCESS [  0.103 s]
[INFO] JAXB Core .......................................... FAILURE [  0.005 s]
[INFO] JAXB Runtime parent ................................ SKIPPED
[INFO] JAXB Runtime ....................................... SKIPPED
[INFO] JAXB XJC ........................................... SKIPPED
[INFO] JAXB JXC ........................................... SKIPPED
[INFO] Parent for osgi testing modules. ................... SKIPPED
[INFO] osgi-test-parent ................................... SKIPPED
[INFO] osgi-test-core ..................................... SKIPPED
[INFO] JAXB bundles ....................................... SKIPPED
[INFO] Old JAXB Core ...................................... SKIPPED
[INFO] osgi-test-runtime .................................. SKIPPED
[INFO] Old JAXB Runtime ................................... SKIPPED
[INFO] osgi-test-xjc ...................................... SKIPPED
[INFO] Old JAXB XJC ....................................... SKIPPED
[INFO] osgi-test-jxc ...................................... SKIPPED
[INFO] Old JAXB JXC ....................................... SKIPPED
[INFO] JAXB Documentation parent .......................... SKIPPED
[INFO] JAXB Release Documentation ......................... SKIPPED
[INFO] JAXB samples ....................................... SKIPPED
[INFO] JAXB RI ............................................ SKIPPED
[INFO] JAXB OSGI parent ................................... SKIPPED
[INFO] JAXB OSGI .......................................... SKIPPED
[INFO] osgi-test-osgi ..................................... SKIPPED
[INFO] JAXB OSGi Tests .................................... SKIPPED
[INFO] JAXB WWW Help files ................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17.784 s
[INFO] Finished at: 2022-01-14T11:27:16+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jaxb-core: Could not resolve dependencies for project org.glassfish.jaxb:jaxb-core:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: jakarta.xml.bind:jakarta.xml.bind-api:jar:4.0.0-RC3, jakarta.activation:jakarta.activation-api:jar:2.1.0, org.eclipse.angus:angus-activation:jar:1.0.0: Failure to find jakarta.xml.bind:jakarta.xml.bind-api:jar:4.0.0-RC3 in http://localhost:8081/repository/maven-public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1]
[ERROR]

E.g. the last published version of jakarta.xml.bind-api is 4.0.0-RC2
https://search.maven.org/artifact/jakarta.xml.bind/jakarta.xml.bind-api

pass -Pstaging to the build and you're good to go. Currently missing dependencies cannot be published to maven central yet; they should be published shortly after Jan 25.

Running 'mvn clean install -Pstaging' results in the same error.

try with clean repo and mvn -U -C clean install -Pstaging; that is what CI does and I can see binaries at https://jakarta.oss.sonatype.org/content/repositories/staging/ (that's the repo -Pstaging uses)

or as per resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced use -U

Thanks for the repository link. This was the missing piece. Once I configured a proxy repository for it in my Nexus instance and added it to the maven group, the build worked.


Bump Dependencies #5967845158

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5967845158

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


Add parameter preserve_index to from_pandas

Added optional parameter, so that user can get rid of useless index preserving. Issue

I did make style and it affected over 500 files

Nvm I was using wrong black version


Revert "[GLUTEN-4660][CH]Asynchronous shuffle read (#4664)"

This reverts commit bf528b30ceb5393b2bab6b81c30a53c5284b93d6.
What changes were proposed in this pull request?
Revert #4664, due to performance issue
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_master_02_24_2024_time.csv
log/native_master_02_23_2024_b82359286_time.csv
difference
percentage

q1
34.34
33.31
-1.021
97.03%

q2
24.77
22.67
-2.103
91.51%

q3
38.78
39.20
0.420
101.08%

q4
37.81
37.79
-0.019
99.95%

q5
71.67
70.31
-1.364
98.10%

q6
5.66
7.14
1.483
126.23%

q7
83.96
84.33
0.373
100.44%

q8
86.74
86.39
-0.345
99.60%

q9
125.66
124.14
-1.513
98.80%

q10
42.79
42.39
-0.395
99.08%

q11
20.56
21.03
0.467
102.27%

q12
28.79
26.45
-2.346
91.85%

q13
45.21
45.22
0.006
100.01%

q14
20.63
16.73
-3.907
81.06%

q15
28.31
27.23
-1.081
96.18%

q16
13.32
14.68
1.360
110.21%

q17
102.37
101.39
-0.980
99.04%

q18
149.07
148.35
-0.722
99.52%

q19
12.59
13.42
0.838
106.66%

q20
26.67
26.61
-0.053
99.80%

q21
226.20
226.57
0.372
100.16%

q22
13.50
13.69
0.197
101.46%

total
1239.39
1229.06
-10.334
99.17%


Bug 2247748: A storage-client CronJob create too many jobs and pods causing maxPod limit to be reached

Fixes the issue created where consecutive CronJobs iterations create pods unnecessarily and caused maxPod limit to be reached thus resulting in future pods scheduling to be stuck in a pending state.

Added a ConcurrencyPolicy field to the CronJob for reconcileClientStatusReporterJob in StorageClientReconciler
ConcurrencyPolicy chosen in this case to be Forbid

The Forbid option specifies waiting for the current job to finish before starting a new one and the Replace option starts a new job no matter what is the current one's status is (which can also create a new pod while the previous job’s pod is still terminating and increase pod count unnecessarily).
Since the created pod for this cronJob purpose is a heartbeat to the provider server i don't see the point in choosing to replace the current job with another, therefore forbid made more sense.

@bernerhat could you pls add controllers as the prefix to commit msg to pass github actions?

Firstly addressing the issue at hand, simulated and tested the options to either Forbid or Replace the current running Job locally using minikube and kubernetes version 1.27.4
Secondly, Concerns brought up to me by Ohad were:

Setting a proper deadline for the pod to finish it's operation to prevent an infinite loop scenario.
Keeping last run objects to investigate such option

In order to address these concerns i've added a few new specs to the crafted CR:

TTLSecondsAfterFinished - keep iteration objects (job and pod). set the ttl to 10 minutes, can be changed.
ActiveDeadlineSeconds - deadline before killing the objects. Pod 2 minutes after consultation, Job 2 minutes 35 seconds.
SuccessfulJobsHistoryLimit - set to 1. default value is 3, reduced to prevent unnecessary object clutter.

ActiveDeadlineSeconds on the job level was set to 2 minutes and 35 seconds in order to keep the pod. for some reason the pod was not kept after the deadline reached, after many testing i've managed to find that the pod was only kept after moving into error status 30 seconds after the deadline is reached and the kill order was issued (extra 5 seconds to be sure).

@bernerhat could you pls add controllers as the prefix to commit msg to pass github actions?

missed, GH action is still failing.

@bernerhat could you pls add controllers as the prefix to commit msg to pass github actions?

missed, GH action is still failing.

did not miss, its failing for the first commit still.. is there a way to fix or should i re-create the pr?

/approve


Arch sniffer - Allow custom factories

Because our arch sniffer checks not only Spryker infrastructure factories but everything with *Factory pattern, it leads to the changes like that (allowing magic methods in custom factories) https://github.com/spryker/architecture-sniffer/compare/0.4.0...master#diff-62ac95b02f69918a5851de9eeae1063dR44
At the same time in Spryker infrastructure factories, magic methods and any other methods are not allowed.
To prevent the mess we need to distinguish spryker infrastructure and custom factories by a proper definition of the constant or splitting it: \ArchitectureSniffer\Common\Factory\AbstractFactoryRule::PATTERN_ZED_FACTORY

:+1:


Add option to pass dataCallback from the ember config

This enables you to modify the stack-payload before passing it to Sentry.
Work in progress - cant verify success yet.

Hi @hussfelt, thanks for the PR.
This would indeed be a nice addition, though I'm not a huge fan of the function definition inside the config file.
May be we could instead try to use a sentry-data-callback service that would have to be registered before the sentry-setup one.
Doing this would leave the config as clean as possible, and may be allow the use of other services.
What do you think?

Sounds like a plan!
I am pretty lost on how to accomplish that though :)
Are you talking about shipping another initializer with some kind of hook with the ember-cli-sentry package or are you talking about enabling raven-setup initializer to read from another initializer and have a "before" statement in those initializers?
Gosh. :)
I'd love to hack this stuff, I need it asap :) But I need some direction...

ping @damiencaselli

@damiencaselli And for the record, I hated the solution above as well - but it was the only way I could pass it down without fiddling too much with the core parts. I just want to get a PoC at this point :)

Are you talking about shipping another initializer with some kind of hook with the ember-cli-sentry package or are you talking about enabling raven-setup initializer to read from another initializer and have a "before" statement in those initializers?

The latter one hehe
I'll try to POC this as an separate repository to ensure it works and that it doesn't generate ghetto code :smiling_imp:

@damiencaselli So I'm done? :) It seems you know what you want to do - I just hope that I can get this stuff together! :-)
Tell me if there is anything you need, besides a tester!
Closing this then!

For the record, I could not get the above solution to work. :)


[Fixes #109] Implement edit

Implement edit buyer and edit seller
To allow for easy editing of existing entries rather than deletion and recreation by the user.
Uses Java's Optional class so that user can choose to leave out fields in the edit command

As mentioned, adding tests would be helpful. When either this or #127 is added, we need to integrate the two together as well (Pass a CommandWarnings to the edit parsers so that they can display warnings). Other than that, LGTM.


fix(chat): Chatbar + edit focus and style

What this PR does 📖

This PR does 2 things: First it addressed #1564 and changes the edit box areas style.
Next it fixes the focus problem and makes it so the chatbar is autofocused. As well as when trying to edit a message autofocusing that message

Which issue(s) this PR fixes 🔨

Resolve #1564

my bad. i linked the wrong issue. it addresses #1564 (second point)

i've noticed if you cancel the edit the auto focus doesn't go automatically go the chat bar again
the same happens if you upload and cancel as well
https://github.com/Satellite-im/Uplink/assets/29093946/156aca96-3a6b-4cfa-b4cf-fc076a3f09d2
but merging, can be improved later
macOS, m1


Add utility that scales legend markers after legend creation

In matplotlib and seaborn, it's possible to adjust the size of legend markers at the time of legend creation, but it's not super clear how to make that transformation after a legend has already been created. It would be nice to be able to give users a utility that lets them scale markers after a legend already exists, rather than having to remember the multiple ways of achieving that before plotting.

via @keithchev : It would also be nice to be able to use a different marker shape in the legend


ci: Add commitlint GitHub action  [citest skip]

Ensure that commits follow conventional commits format
Ensure that the PR title follows conventional commits format
Ensure that only one commit exists in the PR

Adding this in https://github.com/linux-system-roles/.github/pull/24 it will be applied globally to all roles with automation.


Updates for new Firebase projects

This PR replaces the legacy token generations with support for the new Firebase projects. The implementation closely follows the documentation.

When will this be merged in?

I rebased my commits with the latest master and even removed an unrelated commit just now. Anyone on the team, please tell me if there's anything wrong with this.

This no longer seems relevant as the Python Admin SDK is out there.


the released 4.0.0 version can not download dependency from maven repo, back to 3.1.0 runs ok

[kscript] Resolving wu.seal:kscript-tool:1.0.13...
[kscript] Resolving com.google.code.gson:gson:2.8.9...
[kscript] [ERROR] Failed while connecting to the server. Check the connection (http/https, port, proxy, credentials, etc.) of your maven dependency locators. If you suspect this is a bug, you can create an issue on https://github.com/holgerbrandl/kscriptFile 'wu.seal:kscript-tool:1.0.13' not found
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for wu.seal:kscript-tool:jar:1.0.13
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for wu.seal:kscript-tool:jar:1.0.13

Sorry for the inconvenience. Could you share an example to reproduce the problem?

The same is happening on my CI starting from today:
[kscript] Resolving com.squareup.okhttp3:okhttp:4.9.3...
[kscript] [ERROR] Failed while connecting to the server. Check the connection (http/https, port, proxy, credentials, etc.) of your maven dependency locators. If you suspect this is a bug, you can create an issue on https://github.com/holgerbrandl/kscriptFile 'com.squareup.okhttp3:okhttp:4.9.3' not found
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for com.squareup.okhttp3:okhttp:jar:4.9.3
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for com.squareup.okhttp3:okhttp:jar:4.9.3

As far as I can say it is a problem with a Kotlin Scripting artifact resolver: whenever the artifact is in the local artifacts cache it works correctly, but for remote resolution, it doesn't work.
This resolver was working correctly in Kotlin 1.4, but after upgrading to the latest version of Kotlin it has started to fail. During my tests of the kscript4 branch, I was able to make it work by using the most dependencies for Kotlin at version 1.5, but only keeping kotling-scripting dependency at version 1.4.
Here is the ticket at JetBrains:
https://youtrack.jetbrains.com/issue/KT-50069
The above ticket did not get much traction, most probably because no one else has reported that problem. It would be great if someone can repeat my tests by changing the version of Kotlin dependencies and once again analyze the KScript dependency resolution code. The new dependency resolution code in KScript is in fact very similar to the previous KScript version resolver, so seems like updating KScript dependency to the new kotlin-scripting artifact version broke KScript.

I noticed same issue below are snippets from my kscript:
#!/usr/bin/env kscript
import DependsOn
import kotlin.system.exitProcess

@file:Include("../utils/secrets/build/generated/source/nytsecrets/release/com/nytimes/android/secrets/Secrets.kt")
@file:Include("base.kt")
@file:DependsOn("com.offbytwo:docopt:<IP_ADDRESS>50202")

import org.docopt.Docopt

On new instance using kscript 4.0.0 I get the below error:
[kscript] Resolving com.offbytwo:docopt:<IP_ADDRESS>50202...
[kscript] [ERROR] Failed while connecting to the server. Check the connection (http/https, port, proxy, credentials, etc.) of your maven dependency locators. If you suspect this is a bug, you can create an issue on https://github.com/holgerbrandl/kscriptFile 'com.offbytwo:docopt:<IP_ADDRESS>50202' not found
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for com.offbytwo:docopt:jar:<IP_ADDRESS>50202
[kscript] [ERROR] org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for com.offbytwo:docopt:jar:<IP_ADDRESS>50202

Under 3.1.0 on new instance
[kscript] Detected missing dependencies in cache.
[kscript] Resolving dependencies...
[kscript] Resolving com.offbytwo:docopt:<IP_ADDRESS>50202...
[kscript] Resolving com.github.holgerbrandl:kscript-annotations:1.4...
[kscript] Dependencies resolved

If the dependency is already present in .m2/repository on the instance then it appears to resolve without issue

If you can do the additional tests and confirm my hypothesis - we can upvote Jetbrains ticket. Please see my comment: https://github.com/holgerbrandl/kscript/issues/345#issuecomment-1112428775

I guess we then need to roll back the scripting dependencies to the version initially suggested by @aartiPl . I was hoping that the problem would have been resolved upstream.
@aartiPl We should also add some tests that intentionally prune some subtree of the local .m2 cache to ensure that the resolver is tested correctly.  With the cached .m2 copies of the dependencies I completly missed this major regression.

I've added more tests and I struggle to reproduce the problem. Here's a basic protocol
brandl@ubuntu:kscript$ rm -rf .m2/repository/log4j/log4j/1.2.14/; kscript --clear-cache
Cleaning up cache...
brandl@ubuntu:kscript$ kscript --version
kscript - Enhanced scripting support for Kotlin on *nix-based systems.

Usage:
 kscript [options] <script> [<script_args>]...
 kscript --clear-cache

The <script> can be a script file (*kts), a script URL, - for stdin, a *.kt source file with a main method, or some kotlin code.

Use '--clear-cache' to wipe cached script jars and urls

Options:
 -i --interactive        Create interactive shell with dependencies as declared in script
 -t --text               Enable stdin support API for more streamlined text processing
 --idea                  Open script in temporary Intellij session
 -s --silent             Suppress status logging
 -d --development        Enable logging of exception stack trace and additional log messages
 --package               Package script and dependencies into self-dependent binary
 --add-bootstrap-header  Prepend bash header that installs kscript if necessary

Copyright : 2021 Holger Brandl
License   : MIT
Version   : v4.0.0
Website   : https://github.com/holgerbrandl/kscript
Kotlin    : 1.6.21-release-334
Java      : JRE 11.0.15+10
brandl@ubuntu:kscript$ cat ticket_345.kts
#!/usr/bin/env kscript

@file:DependsOn("log4j:log4j:1.2.14", "com.offbytwo:docopt:<IP_ADDRESS>50202")

//import DependsOn
import kotlin.system.exitProcess

import org.docopt.Docopt

org.apache.log4j.Logger.getRootLogger()
brandl@ubuntu:kscript$ kscript ticket_345.kts
[kscript] Resolving log4j:log4j:1.2.14...
[kscript] Resolving com.offbytwo:docopt:<IP_ADDRESS>50202...
brandl@ubuntu:kscript$

So at least the resolver part seems fine. Could you help me to reproduce this issue?

There is test case in main repository for this issue: "IntegrationTest345.main.kts". It fails for me every time, even before resolving "com.beust:klaxon:5.5". Below the screenshot from session with enabled development mode "-d".
kscript -d IntegrationTest345.main.kts

As you can see it throws from "org.eclipse.aether.resolution.DependencyResolutionException" (DependencyResolver.kt:51).
Does anyone know how to access Aether source code? The project is already archived in Eclipse, and I couldn't find any trace of its source code.

I had added this test (which should be moved to tests later I think) to assess if the resolver would generally work when bypassing kscript (which seems to be the case).
Since aether is coming in as a transitive dependency, I do not know where the sources are maintained now. It was indeed archived away a while ago.

I have a few new findings in regards to this issue:

'aether' project is deprecated, but the direct successor of this library is 'maven-resolver' project (it even keeps the package naming); Link: https://github.com/apache/maven-resolver
'kotlin-scripting-dependencies-maven' imports old 'aether' artifacts instead of 'maven-resolver' artifacts (it should be fixed in 'kotlin-scripting-dependencies-maven' as 'maven-resolver' artifacts are also imported as a dependency)
I have added IntegrationTest345 also to the test directory in kscript; I have implemented 'fun main()' there and I have started it by using that function. That way IntegrationTest345 has passed, while when started using kscript it fails.

Because of that, I suspect that there are differences in classpath between IntelliJ (where resolver works) and Kscript. Cannot pinpoint specific dependencies though.

In the past the classloader in the kotlin binary worked differently compared to the java classloader (which is also used in the IDE). Maybe this points to the root cause?
@ligee Is (2) Intentionally or a bug?

DependencyResolutionException usually has a cause. Is it possible for you to look at the full chain of causes in debugger?

@holgerbrandl, seems like a bug on our side, @ileasile is taking care about it.

@ligee , @ileasile - How can we test changes? Can you create temporary artifacts e.g. SNAPSHOT, so that I can apply in kscript and recheck?

@aartiPl https://youtrack.jetbrains.com/issue/KT-50069/Maven-artefacts-resolving-doesn-t-work#focus=Comments-27-6053576.0-0

We kinda found out a reason and fixed the issue. Debugging helped me a lot. Just in case, I'll share how I've done it.
There is a bin/kotlinc file in kotlin compiler distribution. It's a shell script, and there is a place where JAVA_OPTS are set up. Add this argument there:
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5006

(or you may just export JAVA_OPTS env variable with this value)
Then, setup Remote JVM debug configuration in IDEA:

Then run your kscript command, like kscript script.kts. Execution should suspend. Setup breakpoints in kscript code.  Execution should stop on breakpoint.

/\
|   Good stuff!
Thanks for helping with this issue!

So cool, thanks a ton to both of you @ileasile  and @aartiPl for this great analysis and fix.
So @aartiPl, shall we apply your PR for a hotfix release and then wait until the fixed version of kotlin has been released before reollin it back to its current state?

I need some more time to do additional testing and cleanup of the branch with fixes (I hope it will be ready at the latest on Saturday afternoon).
We will not have to wait for a new version of Kotlin. The problem was with the incorrect merging of resources by Gradle shadow plugin. We can either change 'kotlin-scripting-dependencies-maven' artifact to 'kotlin-scripting-dependencies-maven-all' (preferred) or add an additional transformation step during the shadow jar building.
It seems that this change works correctly also with Kotlin 1.6.21, so I will use this version of Kotlin.

BTW, I was not able to execute the reproducer script even after the fix. It successfully resolves dependencies and compiles but fails on execution with different exceptions

@ileasile - yes that's a bit strange, but taking into consideration that tests are passing without problems and in Kotlin 1.6.21 not every problem is fixed (still a dependency on aether artifacts) I would leave it for further testing in real-life conditions. There is huge improvement anyway. I have applied both solutions to make sure that the problem won't break kscript in any way.
@holgerbrandl - I think we can release a fixed version and see if there is an improvement.

@here - there is a new version of kscript available: 4.0.2 - please retest with the new version.

4.0.2 solves the issue for me. Thanks!

Seems to be solved now. If anyone still experiences problems with resolving artifacts, please reopen this ticket.


update tensorboard function config for torch_profiling example

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-4430832.modal.run


Update protractor version.

Updating protractor version to be able to pass selenium standalone params in protractor configuration file.

Thank you!


nixos/chromium: add cursor metadata patch for wayland screen-sharing

Signed-off-by: Anthony Rabbito<EMAIL_ADDRESS>Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg build chromium

@ofborg build chromium

closed in favor of: https://github.com/NixOS/nixpkgs/pull/169365


Simple usemappedstate

This PR is based on https://github.com/facebookincubator/redux-react-hook/pull/38 (let's merge it!).
This is more of a suggestion rather than a final pull request. The idea is to return not the state value from the hook but an actual mappedState from the global state so it's not stale even while the component is rebasing its state. Right now I don't see why calling mapState directly on store.getState would be a problem but I'm not 100% sure. We can also avoid extra renders to if the mapState function is changed but the actual mappedState remains the same and synchronous state updates are handled correctly. A problem I see is that calling a mapState on every render might be a problem if the mapState is expensive and not memoized so I decided to add a development-only warning that the function should be memoized.
I've also added a test for a state/props mismatch.
If the approach is fine a can try some benchmarking mentioned in https://github.com/facebookincubator/redux-react-hook/issues/39.

Thanks for the PR and opening the discussion! I'm really hesitant on this one. I know in our app, the mapState function being called so much contributes significantly to the time taken to process an action (we can have > 2000 connected components). If you have a fast changing prop or state, for example, you'd then need to isolate it to a different component to avoid performance issues. This may not be the worst thing, of course. This is very simple, and really isn't that much different than the proposal in #49.

Yes, this is basically what was discussed in #49 but extracted to the library level so we can try to optimise (or recommend to memoize).
I'm not sure I understand what you mean by "isolate it to a different component". You would do this if you want to utilise React.memo and skip children rendering. It might be helpful for the current implementation because a new mappedState causes a component to render at least twice even if the mappedState is unchanged. If the component is actually big it can become a problem and you might want to split it into multiple components and use React.memo. But returning fresh mappedState right away will not cause a second render (there is not setState in hook body) so I don't see what to extract. Moreover, unchanged state won't trigger a render.
To avoid calling mappedState too often I've also added a useMemo to calculate derivedState. I think It is even slightly better than it is now as mappedState will only be invoked if the state actually changes rather than on every action which does not necessary result in a new state.

To avoid calling mappedState too often I've also added a useMemo to calculate derivedState

That is a pretty nice idea. I'm liking this overall. Need to dive in a bit more to the code first, as the forced update still feels a little dirty.

One potential downside of this approach is that it will always re-render the component when the store changes. If we want to go this route, we might as well just grab the entire state instead of having a force update.

I appreciate not calling mapState too often, but because there is a separate mapState call in checkForUpdates, every time the store changes mapState will be called twice. Can you take a shot at that one?

Here is my suggestion. We can memoize mapState (this can be omitted by passing false as a second arg) in the hook so mapState won't be invoked in useEffect if the state hasn't changed since render. Same goes for mapState and store changes that trigger useEffect. I've updated tests to reflected the behaviour and added a new one for the second arg in useMappedState

@ianobermiller What's your opinion on this?

I think I fixed the things you asked. I've been thinking of adding a comment on why we don't rely on React internal bailout mechanism but use a ref for it but I'm not sure it's worth it. What do you think?

Yes, it is always worth adding more comments. Especially since we have a
commit not to long ago using the bailout.
On Sat, Mar 30, 2019 at 4:08 AM Turanchoks<EMAIL_ADDRESS>wrote:

I think I fixed the things you asked. I've been thinking of adding a
comment on why we don't rely on React internal bailout mechanism but use a
ref for it but I'm not sure it's worth it. What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/redux-react-hook/pull/40#issuecomment-478235685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2zi2vVzYmd1CumWYx2ramZCMZPA4ibks5vb0W6gaJpZM4bhmqx
.

Is there anything left before merging?


Brackets can't run on Debian 7 (Wheezy)

Update from @jasonsanjose:
A fix for this issue requires an update to CEF https://code.google.com/p/chromiumembedded/ to fix the glib dependency. A story for this issue is logged here https://trello.com/c/CySUsuf4.
Original Message

Hi,
I get the following error when run Brackets sprint 29 on my Debian 64bit:
/opt/brackets/Brackets: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/brackets/Brackets).
I have tried to applied the solutions in #4720 ln -s libudev.so.1 libudev.so.0, however libudev.so.0 has already existed in my system.
$ ls -al libudev.*
lrwxrwxrwx 1 root root    17 Jul 20 11:38 libudev.so.0 -> libudev.so.0.13.0
-rw-r--r-- 1 root root 59992 Apr 29 05:36 libudev.so.0.13.0

Thanks antivanov... that's worked just fine... brackets working now.

@antivanov
i'm new to debian
could you please explain and detail the steps for me
like to add the the line "deb http://ftp.debian.org/debian jessie main to /etc/apt/sources.list
"??

Download
libc6 :http://packages.ubuntu.com/precise-updates/libc6
libc6-dev : http://packages.ubuntu.com/precise/libc6-dev
then create a folder anywhere (ex:/home/newlib)
**Not :i386 is 32 -bit your system maybe is 64 bit **
$sudo dpkg -x libc6-dev_2.15-0ubuntu10.11_i386.deb /home/newlib
$sudo  dpkg -x libc6_2.15-0ubuntu10.11_i386.deb /home/newlib
Then
vim /home/.bashrc
if LD_LIBRARY_PATH value already written add  :/home/newlib/lib/i386-linux-gnu end of sentence.
else add fallowing value
LD_LIBRARY_PATH=/home/newlib/lib/i386-linux-gnu
save/close.
update
source /home/.bashrc
start Brackets without problem.

this worked on my wheezy 64 bits
https://oscartux.wordpress.com/2014/05/21/como-solucionar-el-problema-de-glibc_2-14-not-found-en-spotify/

Thanks antivanov , That's work

Thank you antivanov : )

Thank you @antivanov  : )
Happy Back To The Future / Flux Capacitor Day!
eric@flux-capacitor:Desktop $ cat /etc/issue
Debian GNU/Linux 7 \n \l
eric@flux-capacitor:Desktop $ uname -a
Linux flux-capacitor 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.68-1+deb7u5 x86_64 GNU/Linux

Is there a way to run Brackets on centos6.5? I am getting the following errors when i run it:
/usr/bin/brackets: /lib64/libc.so.6: version GLIBC_2.14′ not found (required by /usr/bin/brackets)
/usr/bin/brackets: /lib64/libc.so.6: version GLIBC_2.14? not found (required by /opt/brackets/lib/libcef.so)
/usr/bin/brackets: /lib64/libc.so.6: version GLIBC_2.15′ not found (required by /opt/brackets/lib/libcef.so)
/usr/bin/brackets: /usr/lib64/libstdc++.so.6: version GLIBCXX_3.4.15? not found (required by /opt/brackets/lib/libcef.so)

@thefirstofthe300 the trick with the symbolic links works like a charm 🥇 tnx a lot! Brackets finally working on Wheezy!


Fix for random test failures

Fix for the randomic failures on SidechainStateTest and CertificateSubmitterTest.

Duplicates https://github.com/HorizenOfficial/Sidechains-SDK/pull/555


redesigned test page

Description

Redesigned the bloodtest page
Related Issues

Closes #1170

Type of PR

[x] (Feature Enhancement)

Screenshots / videos (if applicable)

Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:

Please review my pull request @varshith257

THANKYOU FOR YOUR CONTRIBUTION


⚠ Bofrost.be has degraded performance

In 924262d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1492 ms

Resolved: Bofrost.be performance has improved in 8c8b9da.


log files are not opened inside the chroot

Got gmid going today on my FBSD server with the chroot configuation. Wanted to use a text logfile. At first I created the path within the chroot but server couldn't open it. Realized it may be an exception to chroot, created in the main filesystem and it worked.
The documentation for the chroot option currently reads "All the paths in the configuration file are relative to the chroot directory, except for the cert, key and ocsp paths." Also the log access option says "The path is relative to the chroot."
My experience is that this is misleading, and a change to the documentation may be warranted. Alternatively, if the plan is to open the logfile within the chroot, this is not my experience.

Oops, I got confused for a moment, please ignore 9f1cce3d0e53209180eabbcd48878c1e989101e7, I just reverted it.  The real fix is in 248fb833f9883b714c48cd3edac2b212cbcd565f.
I actually wanted to follow OpenBSD' httpd behaviour and open the log files inside the chroot; in this case the documentation was right and the code had a bug.
Thanks for the report!

I'm about to close this issues since 2.0.2 was released and includes this bugfix.  Thanks!


dev: Gas metering

Add a GH action that will print a gas report and szhould fail if that gas report isn't up to date
This will allow to compare the effect a PR has over the code base in terms of gas

Ping

Pong

.

@gaetbout can you elaborate gas report isn't up to date? we will have a latest gas_report, and we will compare the PRs gas report with pre-existing one. If the gas is equal or less consumed, then the PR passes, otherwise, if the gas increases, then the PR should fail. am I right?


Add email address

Email address should be on the page. Preferably somehow obfuscated to avoid spam bots.

b57c2fa438d7448c7871e0fca2fa55286947a483


why is the firebase web app necessary here

In the read-me section, I see:

Create a web app in Firebase console of your project.

Q1) why do I need a web app while I am developing a Flutter mobile app ? Is this because files will be stored in web ?

Create a firebase-config.js file in the example/web folder and put there only js part like this

Q2) Where will I find the example/web folder ?

It is not needed, it is just an example for web :) you don't need to do it if you have only a mobile application.


Using Juice on the client-side

This is the error I get when I try to use juice.inlineContent(html, css):
/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:445
            throw moduleError('Cannot find module');
                  ^
Error: Cannot find module: "canvas" from directory "/Users/holmes/Code/foobar/app/node_modules/juice/node_modules/jsdom/lib/jsdom/level2" while processing file /Users/holmes/Code/foobar/app/node_modules/juice/node_modules/jsdom/lib/jsdom/level2/html.js
    at moduleError (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:406:16)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:445:19)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:537:14)
    at Array.forEach (native)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:519:27)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:537:14)
    at Array.forEach (native)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:519:27)
    at Wrap.require (/Users/holmes/Code/foobar/app/node_modules/browserify/lib/wrap.js:537:14)
    at Array.forEach (native)

I'm using Juice client-side via browserify 1.15.
Can Juice work on the client-side? I don't see why it couldn't.

Any progress on this?

jsdom was removed for 1.x, which was a major blocker since it was a native module, but I'm not sure off hand what other blockers there are to in-browser use. Probably the most useful thing at this stage would be to assess what problems currently exist so we can make a roadmap to fixing them.

Even if there are some remaining node/native modules, they can be replaced at browserification time.

My quick attempts failed miserably with obscure errors (it was my first use of browserify).
We have reconsider approach so the front-end packaging won't be necessary for us.

My co-worker and I had some luck the other day by removing web-resource-inliner and fs dependancies. I know this isn't feasible for everyone but it worked well in webpack, V8 and Chrome. I made a basic example in a fork of what we did https://github.com/barretts/juice


Site: tests for basic validation of page add/edit

Marking as won't fix (yet). It's only a couple of required fields so we  would mainly be testing Django Forms.


How to decode the naked stream of camera directly

Thanks for sharing.
I have a problem. I get the naked video stream from the webcam SDK and cache it in a buf space. How can I decode it directly instead of reading the file or address

Hi @ou525, I don't have GStreamer setup for that scenario.  You may want to look to the Jetson Multimedia API which is a lower-level API that you can access the encoder/decoder hardware through:  https://docs.nvidia.com/jetson/l4t-multimedia/index.html


use different star for all day completions younger than one hour

Using :star2: instead of :star: on any day where the solution to part 2 is younger than one hour makes the Leaderboard not only more beautiful but also shows the small achievements of each and every player better.
Example Image

Love the update!

btw. for everyone wondering: the screenshot was taken during development, many of those having a :star2: actually made it more than an hour ago, - that's why there are so many. This is fixed now but I think for an example screenshot it looks pretty better


Use this model on tensorflow

Hello, I would like to use this model in tensorflow, in order to integrate it into a web application. Is it possible to convert it to Tensorflow?  Thanks in advance

Hello, yes it is possible to convert it to tensorflow Lite. Here's a video showing the various steps
How to convert your ML model to TensorFlow Lite (TensorFlow Tip of the Week)
In addition, this tensorflow org website may answer your question
Convertisseur TensorFlow Lite
If you have any further questions, please don't hesitate to contact me.


LFS: missing line feed after message

Hi @bk2204,
I've been working on a pure-SSH implementation and following scutiger-lfs and the specs. I noticed that scutiger-lfs does not add a line feed LF after error messages. The specs describe error-message = *PKT-LINE(data LF) however, scutiger-lfs doesn't add a LF after messages. I've also noticed some inconsistencies in the proposal https://github.com/git-lfs/git-lfs/pull/5560

Hey,
Thanks for the report.  I've got #13 up to fix that and I'll plan to do a release this weekend assuming I haven't broken the Git LFS testsuite, which I'll check tomorrow.

Hey,
Thanks for the report.  I've got #13 up to fix that and I'll plan to do a release this weekend assuming I haven't broken the Git LFS testsuite, which I'll check tomorrow.

Welp, I didn't see that one. Thanks for the quick response, I will close this one 🙂


Can I propose my minimalistic browser written in pyqt

https://github.com/o6n/Ayumi

i can add Print
cookie technology will soon be abandoned
you can use my minimalist browser i'm big fan of AppImage and i'm testing HelloSystem thank you for your work

No response


Harbor cluster lcm controller running context canceled error.

What can we help you?
After make run and create harborcluster cr, then controller log:
ERROR harbor-operator.controller error when reconcile cache component. {"controller": "harborcluster", "error": "context canceled"}

The PR for fixing the issue has been merged, close it


Fix the shell_quoting test

r? @alexcrichton
add-on to #5666

Added mod shell_quoting; to testsuite/main.rs, so it actually runs
fixed bugs in the test

@bors: r+

:pushpin: Commit d1cb78acc642b57e36f8b68ee01fdf0d282deb50 has been approved by alexcrichton

:hourglass: Testing commit d1cb78acc642b57e36f8b68ee01fdf0d282deb50 with merge<PHONE_NUMBER>93056c5584002c019d8705c4c138d9...

:broken_heart: Test failed - status-appveyor

The test is failing on windows because shell-escape uses backslashes on windows, and single-quotes on unix. I'm not sure what the best thing is to do here. We could

use #[cfg] attributes to use one version on windows, and a different one on unix, or
check that the command is runnable. That's really the important thing here. One way to do that could be to figure out which part of the cargo output is from rustc, and then run the rustc command and make sure the output and exit code is the same.

What do you think?

I think env vars can be used to trick it into always doing unix escaping, so perhaps that could be used?

Sure, I'll try that. Should be the easiest fix.

@bors: r+

:pushpin: Commit 2e17235d9b9907bac25b4e70d8eeb386cc226268 has been approved by alexcrichton

:hourglass: Testing commit 2e17235d9b9907bac25b4e70d8eeb386cc226268 with merge 2a39e6c5376f8f7becdc0d80a49fda6c4f77dd93...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 2a39e6c5376f8f7becdc0d80a49fda6c4f77dd93 to master...


status of subscription NOK

Date:2016/06/29
[Steps to reproduce]

As marketplace owner, choose "Marketplace/Manage access", define "Authorized customers only"
Unclick an organization that has a subscription that was published to this marketplace
This results in a warning stating that there is at least one subscription that will be suspended.
Press ok.
As customer (that has another marketplace where he can still login), login to another marketplace
Look at status of subscrptions that were on restricted access marketplace

[Expected result]
status: suspended (as stated in RQ)
(even though I do not think it should be possible to unclick the organization that has active subscriptions)
[Observed result]
status: suspended, update payment types.
[Details]
This is confusing because normally subscriptions only become suspended if payment types are missing. If I now update payment types, then I can reactivate subscription. Do we want this?
Of course this is only possible if the customer has the possibility to login to another marketplace,
and if "HIDE_PAYMENT_TYPES" is not set to true.
As suggested by Lorenz, it may be better to not allow restricting access to organizations that have active subscriptions on the marketplace. (org cannot be unclicked). These customers should terminate their subscriptions, before this is possible.

With current design, active subscriptions will be suspended when restricting the customer access to the marketplaces where they are hosted. This is first of all, to prevent in any case, that customers are continued to be be charged for subscriptions they can't access anymore.
However, after all, we concluded that suspending the customer subscription is not the appropriate measure to achieve this. Despite of the here mentioned interference with the payment type handling, there is deeper concept lack, concerning the question of how to resume them in this use case.
Idea: KISS. If the marketplace manger attempts to remove access for a customer C to a marketplace M:

if C doesn't have any active subscriptions on M, the operation succeeds and C cannot access M anymore
if C has active subscriptions on M, the operation fails with a respective error message and access to M remains for C.

@mdehn
Would this be an accepted solution for you?

yes, that is ok.

As just discussed, there is an easier solution.
Currently, when the marketplace owner selects to provide access to his marketplace for authorized customers only, he gets the list of all customers, where those customers are preselected, who have at least one active subscription on that marketplace. This is already implemented.
Proposed Enhancement: Access cannot be removed for customers with active subscriptions on the selected marketplace. The check-boxes for those customers will be disabled in the list.
If such customers with active subscriptions exist, a respective note will be displayed on the manage access page, that the access cannot be removed for these customers, because they have active subscriptions. These subscriptions have to be terminated first.
Developers have to take care with the "select all" function in this table, in order that these disabled check-boxes are excluded for the "all" checkbox handling.

Adapted the documentation (en/de) for this proposal. Will be included in next doc build (>2016-07-13)

Verified by FNST
[Verified-build] BES_MASTER_DELIVERY-744 2016/07/22
[Verified-details]The customer with active subscription cannot be disable from a marketplace, so verified.


Fix #3 Remove deprecations, bump to ember-cli 1.13.1, ember 1.13.3

fixes #3

:+1: Thanks a lot for taking care of that!

Just published v0.2.0. Thanks again @wswidzinski!


DOMNodeRemoved never disposed

this.dialog_.addEventListener('DOMNodeRemoved') is never disposed, causing a huge stack of listeners for every opening of a new dialog:
https://github.com/GoogleChrome/dialog-polyfill/blob/0.4.4/dialog-polyfill.js#L236

Thanks, this was something from testing that slipped in. I've removed it and published 0.4.5 both in git and npm.


global env overrides local with

Describe the bug
Hi, I had the following code in my action file:
name: "CI"
on:
  push:
    branches: "*"
  pull_request:
env:
  php-version: 7.4
  cache-version: 1
jobs:
  platform-check:
    name: "PHP 5.6 compatibility"
    runs-on: ubuntu-latest
    steps:
      - name: "Checkout"
        uses: actions/checkout@v2

      - name: "Setup PHP"
        uses: shivammathur/setup-php@v2
        with:
          php-version: 5.6
          coverage: none

      - name: "Check dependency compatibility"
        run: |
          composer check-platform-reqs --no-dev

The env variable was then used for all the jobs except the one described in the snippet. However, with this config, the global env overrode the local with and I got version 7.4 for the job! Now, I agree that it was probably stupid of me to choose the same name, however, I would really expect this to use 5.6 for this job...
Version

[x] I have checked releases and the bug exists in the latest patch version of v1 or v2.
[x] v2
[ ] v1

Runners

[x] GitHub Hosted
[ ] Self Hosted

Operating systems
ubuntu
Additional context
See skaut/skaut-google-drive-gallery#671 for full run/patch.
Are you willing to submit a PR?
No, I have no idea how to fix this.

@marekdedic This should be fixed now after 2.6.0 release.
with will be preferred over env.

Hi,
thanks for the fix, it works :)


some history command stuck on the latest command by having "0s ago" timestamp

I encounted this problem this month i think. I don't know if it is a bug or ...feature, its' annoying.

I got the same issue on Ubuntu 23.04 running atuin 12.0.0 (installed most recent version from Ubuntu package repository). A few commands stuck with 0s at the bottom.
To keep using atuin I had to remove the database .local/share/atuin and rerun an atuin import bash.
It does import the commands in a rather strange order, at first sight it seems to be alphabetically.
And I am aware that there is a more recent version, and especially one which offers a way to delete commands from history. But I'd like to keep using the version offered by distribution vendor for being able to update it with apt, like all other packages.
@KUD-00 With what distribution and version did you run into this issue? Is it for you an option to install >= 14.0.0 and try to delete those stuck commands with something like atuin search --delete ... See https://atuin.sh/blog/release-v14 for more details.

We mark items as "0s" ago if they somehow occurred in the future. We had issues with DST before but I'll take another look through later to see how were recording datetimes

@conradludgate Thanks, that figures. I was developing a time-based feature in my companies product and needed to set my date into the future for testing. Guess I have run a few commands and forgot to switch the time back. The workaround I assume should then be an update to at least 14.0.0 and remove those stuck commands from history.

that make sense. I got dual boot on my pc and the hardware time in Linux appears weird. that caused this 0s ago problem.
thank you for your responses.


Query builder feature - postgresql FOR, NOWAIT and SKIP LOCKED

What steps will reproduce the problem?
Creating an SQL query with a FOR, NOWAIT or SKIP LOCKED using a Query Builder.
https://www.postgresql.org/docs/9.5/static/sql-select.html
What is the expected result?
Pass a SKIP LOCKED to an SQL query using query builder.
What do you get instead?
I have to use createCommand and write whole sql query by hand.
Additional info

Q
A

Yii version
2.0.10

Can't be implemented since it is DBMS specific feature and Yii's query interface supports many engines.


how to share the parameters in nngraph

Thanks for your attention
I want to share the parameters in some layers when using the nngraph to construct a net.please help me

you use the :share method. See this documentation: https://github.com/torch/nn/blob/master/doc/module.md#sharemlps1s2sn

I know this method, but in nngraph, if I want to share the parameter between layer1 and layer2，it would say "no share method"

Have you considered sharing the layer parameters beforehand prior to building your network with nngraph?

@soumith  I know this method, but in nngraph, if I want to share the parameter between layer1 and layer2，it would say "no share method"

@RuiShu I considered, but if are many gmodules ,I do not know how to assemble them together

@duanLH I recommend posting a more detailed question on https://groups.google.com/forum/#!forum/torch7; you'll likely find help there.

@RuiShu thanks~

@duanLH I was trying to find a solution for another problem I have and I hit your thread. I suggest you take a look at this post regarding my issues with parameter sharing in Torch using nngraph. Hope this helps!


Add last of type class

The :last-of-type pseudo selector isn't supported by ie8 so add last-of-type class in macro.  Last-of-type css class is being added within checkbox scss for now as this seems specific to this case rather than a general reset.
The new margin now means that when the focus is on a checkbox, the yellow focus border extends beyond the grey connection border.  However when there is no focus the checkboxes are now aligned with grey border, matching service manual patterns.
Before:

After:

Still gets cut a bit short on mobile.

😦

Yeah was fixing that as you wrote that, doesn't anymore!

I think these are both fixed now and ready to review.

OT but what do we think of polyfills for this kind of thing? Suppose it only works with js enabled...

@risicle I think you answered your own question there :P

Hey, I only properly reviewed this at end of day today.
I have a few comments and I'm not sure if this is the best place for them but it seemed like it would be fine.

Probably a bit late :s  Want to talk about it tomorrow?

These are just changes that I noticed doing a manual visual diff, not looked at any of the CSS changes in particular.  Wraith just turned the whole screen red for me (because all the spacing is changed), so it wasn't really that useful.
i. There's a new gap in the border when we have textareas with wordcounts

Before
After

ii. Questions are generally more squished together
This is probably down to a matter of preference, but I think it was better before having them more clearly separated.

Before
After

iii. More space between the question and hint_underneath fields
The hint_underneath is further from the question it's related to and closer to the next one.

Before
After

iv. There's a lot of extra spacing when radio buttons/checkboxes have extended descriptions
To be clear, this isn't a new problem.  It's been like this for a while.
The difference now is that the fields are more compressed though.

After

  The different coloured lines are the distances between the bottom of the field above and the top of the bolded text about the next question.

v. Border extends further under vertical radios/checkboxes
We already knew about this.

Before
After

I think probably i, ii, and iii are specific to this pull requests.  It also doesn't seem like any of them are showstopping bugs.

I think i. is a bug worth fixing and putting in the backlog.  The other ones seems pretty negligible.  v isn't nice, but there are other problems with the vertical lines that are probably a separate thing.


fix(index): Fix index.css line 1 syntax

To get through webpack css loaders parsing errors.
 You're either doing something wrong with your Webpack config or it's a Webpack/plugin bug. Either way, not something to work around here.


when in lifecycle created commit mutation not be logger

Version
2.4.1
Reproduction link
https://jsfiddle.net/a1wqbmy9/
Steps to reproduce
when in lifecycle created commit mutation not be logger in vue-devtool
What is expected?
logger when first init
What is actually happening?
when in lifecycle created commit mutation not be logger

https://jsfiddle.net/a1wqbmy9/
This is not a runnable reproduction. Please provide a small repository or similar that demonstrates the issue.

when in lifecycle created commit mutation not be logger in vue-devtool

I don't understand this sentence, sorry :(

As I asked you in the other issue, please, use the forums or chats to ask questions


low benchmark scores

from looking at your benchmark scores, they seem really low (by a factor of 10-100x) for reading/writing contiguous memory, even if your doing some other stuff too...did you remember to benchmark with optimizations enabled? you never mentioned the commands you used in the blog entry so I couldn't tell.

I don't do anything special, according to my understanding of bench/criterion it already runs with optimizations enabled?

hmm... maybe allocator stuff? i would have tested with much bigger trees, from reading your code, the trees appear to only have 10-20 elements, so the vast majority of the time would be allocating/freeing the arena/vec's memory. anyway, i'll close this issue since it does appear as though optimizations are enabled.


[Bug]: access to $tags fixture in non-bdd project

I also implemented the approach using tags, which caused an issue unfortunately, and stumbled across this question.
In my current setup, as mentioned in another thread, I am using a project for BDD test cases and another project using "plain" playwright tests: https://github.com/vitalets/playwright-bdd/issues/166.
The issue arises when executing the non-BDD tests and is related to following storageState fixture:
storageState: async ({ storageState, $tags, loggingService }, use) => {
    for (const tag of $tags) {
      if (tag.includes("@user:")) {
        const user = tag.split(":")[1];
        loggingService.logMessage(`detected annotation ${tag} => using storage state ${user}`);
        storageState = `${process.env["AUTH_FILE_DIR"]}/${user}.json`;
      }
    }
    await use(storageState);
  },

The error message then is similar to one already seen in the other context with parallel execution of BDD and non-BDD:
Error: Can't find testMeta for key ""
Is there an issue in initialization of the $tags fixture when not using BDD style, or are there some expected limitations known.
Originally posted by @helmutchecker in https://github.com/vitalets/playwright-bdd/issues/184#issuecomment-2249559602

Released in v7.1.0.
@helmutchecker could you re-check on your side?
Feel free to re-open in case of any issues.


Vite plugin gives release/sourcemap warnings in developer mode

Environment
"@sentry/vite-plugin": "^2.22.6"
Steps to Reproduce
vite dev
Expected Result
Should not attempt to upload sourcemaps and create release in dev mode.
Actual Result
> vite dev

[sentry-vite-plugin] Warning: No auth token provided. Will not create release. Please set the `authToken` option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
[sentry-vite-plugin] Warning: No auth token provided. Will not upload source maps. Please set the `authToken` option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/

Dev mode is actually not reliable to detect sometimes. As a workaround you can either set disable: true in devmode or not add the plugin at all.

Closing this issue for cleanup, if you find this didn't help don't hesitate to re-open @memcorrupt.

Duplicate of https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/344


update travis configuration

http://docs.travis-ci.com/user/migrating-from-legacy/?utm_source=legacy-notice&utm_medium=banner&utm_campaign=legacy-upgrade
This job is running on our legacy infrastructure. Please read our docs on how to upgrade

setting sudo as false fixed this warning, closed by https://github.com/caelum/vraptor4/commit/7ddbed943af415f59633d41211d2409b91dabf9b


Automated Package Upgrade

:tada: This PR is included in version 25.3.149 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Prevents text in Select to overlay

fixes https://github.com/keboola/indigo-ui/issues/347

Netreba.


paper

Can you share the address of the paper?

Thank you for your kind attention. We are pleased to announce that the paper has been uploaded and is now available for review.

Thank you so much for uploading your article and code, both are great! Hope to have the opportunity to communicate more in the future!
------------------ 原始邮件 ------------------
发件人:                                                                                "keviner1/FFMEF"                                                                                @.>;
发送时间: 2023年5月17日(星期三) 下午2:49
@.>;
<EMAIL_ADDRESS>主题: Re: [keviner1/FFMEF] paper (Issue #1)
Thank you for your kind attention. We are pleased to announce that the paper has been uploaded and is now available for review.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


How keep alive a client?

I'm building a service that (crons) that could take hours/day before activate a client. So for the majority of the time, the client(s) will be waiting for a job.
How can I keep alive the client, and still get new task for a server when ready?
Think in something like pubnub.com

I think I'm facing the same issue. Could you shine any more light on it?

@Carbaz @mauricioabreu  gevent will not switch greenlet in long loop(no i/o wait) before you use 'gevent.sleep(0)'.
Mybay you can use code below instead.
def slowmethod(self):
    for x in range(20000):#This is, aprox, the time in ms (on my old I7)
        if x%100 == 0:
            print ("x: {}".format(x))
        for n in range(10000):
            y = x*x
        gevent.sleep(0)
    return 'Slow Done'

Hi @fordoo, I can not change code of executed methods as they are arbitrary and not have direct control over them. I saw greenlets can not handle that kind of concurrence (arbitrary code) so
Is there a version of zeroRPC with threads instead of greenlets?

Nope, there is no version with threads. Also, to solve this problem and also make it easier to support more IO style and more languages, I do have plans to move the core of zerorpc to its own compiled lib, with threads in order to be independent. Very much like how zmq does it.