"Bad file descriptor" error in  9f4fc91

Building 9f4fc91 from source, I encounter a "bad file descriptor" error in the client. A commit from earlier this morning worked OK. (This also affected the crusader remote - same error message.)
√ release % ./crusader test rpi4.lan
[2024-08-03 09:45:47] Client version 0.0.12 running
[2024-08-03 09:45:47] Client failed: Bad file descriptor (os error 9)
Update: Server said:
[2024-08-03 09:44:09] Error from client <IP_ADDRESS>:63677: Expected object
What other troubleshooting info can I provide?

What's the latest commit which works ok?

You can try the latest master with RUST_BACKTRACE=1 on the client side.

√ release % RUST_BACKTRACE=1 ./crusader test rpi4.lan
[2024-08-03 13:42:17] Client version 0.0.12 running
[2024-08-03 13:42:17] Client failed
Error: Failed to connect to server

Caused by:
    Bad file descriptor (os error 9)

Stack backtrace:
   0: __mh_execute_header
   1: __mh_execute_header
   2: __mh_execute_header
   3: __mh_execute_header
   4: __mh_execute_header

[2024-08-03 13:42:17] Error from client <IP_ADDRESS>:65073: Expected object

I will also try an earlier commit to see where it stopped working

I forgot to mention you should use a debug build (cargo build and src/target/debug).

Here's a recent commit that worked: 2b678a0
I haven't narrowed it further. I will re-test with the latest commit and src/target/debug, but probably not today. Thanks again.

I had a couple spare minutes, and had a successful test with a1b41fc. Does that seem likely? Thanks again.

My guess would be that it's non-deterministic. There haven't been any interesting changes to the client in the ranges you've mentioned.

No issue here with latest git commit a1b41fcbdeaed3d62e791384efa63ed10a81007e.
Server: Ubuntu 22.04 with up to date rust installation, build crusade from source
Client: Windows 11 with up to date rust installation, build crusade from source
PS C:\work\speedtest\crusader\src\target\release> .\crusader test  <IP_ADDRESS>
[2024-08-04 21:19:13] Client version 0.0.12 running
[2024-08-04 21:19:13] Connected to server <IP_ADDRESS>:35481
[2024-08-04 21:19:14] Latency to server 1.98 ms
[2024-08-04 21:19:15] Testing download...
[2024-08-04 21:19:22] Testing upload...
[2024-08-04 21:19:33] Testing both download and upload...
[2024-08-04 21:19:40] Warning: Load termination timed out. There may be residual untracked traffic in the background.
[2024-08-04 21:19:40] Writing data...
[2024-08-04 21:19:40] Saved raw data as data 2024.08.04 21-19-40.crr
[2024-08-04 21:19:40] Saved plot as plot 2024.08.04 21-19-40.png

Have you been able to reproduce this with a debug build?

@Zoxc Disappointing news: Using ecc6628 (with updates to the new README), I cannot run the "release" build, but the "debug" build works fine. (I used cargo build to build both the release and debug builds)
What other troubleshooting info could I collect? Thanks.
?1 release % git rev-parse --short master
ecc6628

√ release % ./crusader test <IP_ADDRESS>
[2024-08-08 21:58:13] Client version 0.1.0 running
[2024-08-08 21:58:13] Connected to server <IP_ADDRESS>:35481
[2024-08-08 21:58:13] Client failed
Error: Socket is not connected (os error 57)

?130 release % cd ../debug

# debug build
√ debug % ./crusader test <IP_ADDRESS>
[2024-08-08 21:58:25] Client version 0.1.0 running
[2024-08-08 21:58:25] Connected to server <IP_ADDRESS>:35481
[2024-08-08 21:58:27] Idle latency to server 2.03 ms
[2024-08-08 21:58:28] Testing download...
[2024-08-08 21:58:34] Testing upload...
[2024-08-08 21:58:41] Testing both download and upload...
[2024-08-08 21:58:48] Writing data...
[2024-08-08 21:58:48] Saved raw data as crusader-results/data 2024-08-08 21.58.48.crr
[2024-08-08 21:58:49] Saved plot as crusader-results/plot 2024-08-08 21.58.48.png

# I subsequently tried a release build with RUST_BACKTRACE
√ release % RUST_BACKTRACE=1 ./crusader test <IP_ADDRESS>
[2024-08-08 22:05:48] Client version 0.1.0 running
[2024-08-08 22:05:48] Connected to server <IP_ADDRESS>:35481
[2024-08-08 22:05:48] Client failed
Error: Socket is not connected (os error 57)

Stack backtrace:
   0: __mh_execute_header
   1: __mh_execute_header

Both were tested against a server running 5b607c4 (from earlier this evening):
[2024-08-08 21:58:13] Error from client <IP_ADDRESS>:63250: Expected object
[2024-08-08 21:58:25] Serving <IP_ADDRESS>:63251, version 3
[2024-08-08 21:58:48] Serving complete for <IP_ADDRESS>:63251
[2024-08-08 22:05:48] Error from client <IP_ADDRESS>:63427: Expected object

Try setting
strip = "none"
debug = 2

under [profile.release] in the file src/Cargo.toml

A more juicy report... What other info could I provide? Thanks
?1 release % RUST_BACKTRACE=1 ./crusader test <IP_ADDRESS>
[2024-08-08 22:53:20] Client version 0.1.0 running
[2024-08-08 22:53:21] Client failed
Error: Failed to connect to server

Caused by:
    Connection refused (os error 61)

Stack backtrace:
   0: std::backtrace_rs::backtrace::libunwind::trace
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
   1: std::backtrace_rs::backtrace::trace_unsynchronized
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2: std::backtrace::Backtrace::create
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/backtrace.rs:331:13
   3: std::backtrace::Backtrace::capture
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/backtrace.rs:296:9
   4: <E as anyhow::context::ext::StdError>::ext_context
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.86/src/backtrace.rs:27:14
   5: anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::with_context
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.86/src/context.rs:65:31
   6: crusader_lib::test::test_async::{{closure}}
             at /Users/richb/github/crusader/src/crusader-lib/src/test.rs:94:19
   7: tokio::runtime::park::CachedParkThread::block_on::{{closure}}
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/park.rs:281:63
   8: tokio::runtime::coop::with_budget
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/coop.rs:107:5
   9: tokio::runtime::coop::budget
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/coop.rs:73:5
  10: tokio::runtime::park::CachedParkThread::block_on
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/park.rs:281:31
  11: tokio::runtime::context::blocking::BlockingRegionGuard::block_on
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/context/blocking.rs:66:9
  12: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::{{closure}}
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/scheduler/multi_thread/mod.rs:87:22
  13: tokio::runtime::context::runtime::enter_runtime
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/context/runtime.rs:65:16
  14: tokio::runtime::scheduler::multi_thread::MultiThread::block_on
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/scheduler/multi_thread/mod.rs:86:9
  15: tokio::runtime::runtime::Runtime::block_on_inner
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/runtime.rs:363:50
  16: tokio::runtime::runtime::Runtime::block_on
             at /Users/richb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/runtime.rs:335:13
  17: crusader_lib::test::test
             at /Users/richb/github/crusader/src/crusader-lib/src/test.rs:884:21
  18: crusader::run
             at /Users/richb/github/crusader/src/crusader/src/main.rs:191:13
  19: crusader::main
             at /Users/richb/github/crusader/src/crusader/src/main.rs:225:25
  20: core::ops::function::FnOnce::call_once
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
  21: std::sys_common::backtrace::__rust_begin_short_backtrace
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:155:18
  22: std::rt::lang_start::{{closure}}
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/rt.rs:159:18
  23: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:284:13
  24: std::panicking::try::do_call
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:559:40
  25: std::panicking::try
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:523:19
  26: std::panic::catch_unwind
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panic.rs:149:14
  27: std::rt::lang_start_internal::{{closure}}
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/rt.rs:141:48
  28: std::panicking::try::do_call
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:559:40
  29: std::panicking::try
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:523:19
  30: std::panic::catch_unwind
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panic.rs:149:14
  31: std::rt::lang_start_internal
             at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/rt.rs:141:20
  32: _main
?1 release %

This'll have to wait 'til tomorrow. I'm on the east coast of US (New Hampshire) so it's late here... Thanks!

I'm closing this in favor of #38


Extend entity (relation) without custom fields

Description
I need to alter the product_category relation table with custom columns. I only see documantions on how to extend entities via "extensions" (which is not the way if i'm getting it right) or with custom fields (In my case, the product_category relation does not have the possibility to add custom field data).

how can i add fields to entity relations (like product_category)
how can i add this field to all relevant Shopware sections?

Possible Solution
Additional context

Hi @NiklasTeich
sadly, there is no way to extend mapping tables in Shopware6.
Maybe you can explain what you want to achive here :)
Sunny Regards
Pantrtxp

Hi @pantrtxp
Thanks for your response!
My current use case is to code a custom listing sort.
This sort needs product data depending on the category.
My idea was to alter the relation table to save exactly this.
Other ideads to achieve something like that are more than welcome!
Greetings,
Niklas

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


⚠ Bofrost.de has degraded performance

In ae0cb94, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2255 ms

Resolved: Bofrost.de performance has improved in f60c8b9 after 6 minutes.


Verify NTVS functions properly with latest VS2015 bits

In particular, most concerned with Salsa functionality

verified all is well with VSUML 25324.00


SPA and WebForms Applications

Hello,
I would like to put at the same canvas, many web applications with many different tecnologies and my main concern is about how can I manage the fragment assets.
Whether Tailor uses AMD to get the fragment content, my fragment can start some script before their dependency to be loaded. For exemple if I have Some script and link tags inside of the fragment.
How can I control this flux?
Best Regards,

The best way is to do the dependency management in your fragment since you know which scripts are dependent on each other.
define("react", function() {});

require(["react", /** extra libs **/], () => {
   // fragment app code goes here
})

You can send this JS via fragment link header or put in script tag. It should not matter.
Incase if you want this behaviour for every fragment in the page, the best way is to put the libs on HTML templates and send the scripts through fragment link tags.


PurchaseManager does not support consumables and subscriptions at the same time.

List offers = new ArrayList<>();
offers.add(new Offer().setType(OfferType.CONSUMABLE).setIdentifier(BuyCoinType.coins1.produceId));
offers.add(new Offer().setType(OfferType.CONSUMABLE).setIdentifier(BuyCoinType.coins2.produceId));
offers.add(new Offer().setType(OfferType.CONSUMABLE).setIdentifier(BuyCoinType.coins3.produceId));
offers.add(new Offer().setType(OfferType.SUBSCRIPTION).setIdentifier(BuyCoinType.weekly.produceId));
offers.add(new Offer().setType(OfferType.SUBSCRIPTION).setIdentifier(BuyCoinType.monthly.produceId));
offers.add(new Offer().setType(OfferType.SUBSCRIPTION).setIdentifier(BuyCoinType.yearly.produceId));
//
throw new IllegalStateException("Cannot support OfferType Subscription and other types in the same app");
What should I do if there are both "consumables" and "subscriptions" in the game?

Either use two purchase managers, or for the repo, enhance the framework and open a PR contributing your changes.

Its relatively easy to use two Purchase managers. I tried it with one of my apps last year and it works fine (and people on mobile seems to like subscriptions).
Anyway I think it should be reflected in the readme and wiki that you can not have both pay models with one Purchase Manager because here the readme suggestst the oposite:

PurchaseManagerConfig pmc = new PurchaseManagerConfig();
pmc.addOffer(new Offer().setType(OfferType.ENTITLEMENT).setIdentifier(YOUR_ITEM_SKU));
pmc.addOffer(new Offer().setType(OfferType.CONSUMABLE).setIdentifier(YOUR_ITEM_SKU));
pmc.addOffer(new Offer().setType(OfferType.SUBSCRIPTION).setIdentifier(YOUR_ITEM_SKU));
// some payment services might need special parameters, see documentation
pmc.addStoreParam(storename, param)

If you have a good suggestion what to add where to the wiki, I'll be happy to add it!


How to train on a custom dataset ?

Hello and thank for releasing the code.
I have created a plugin under gazebo simulator, which can provide me artificial pointcloud dataset of various  objects. Now I would like to use PointRCNN to train model for an specific object. I can write a dataset similar to KITTI but I am a little confused about how the place the labels. in Original KITTI the 3D box labels are in camera frame however I do not want to use labels in camera frame, I want to directly use frame of point cloud source(x:forward, y:left, z:upright), at which part of code are you transfroming the labels from cam frame to velodyne frame ?
Also is there any tips or recommendations from you for this task ?
Thank you for your help

Any update on this issue? I would also like to use another dataset.

Hello and thank for releasing the code.
I have created a plugin under gazebo simulator, which can provide me artificial pointcloud dataset of various objects. Now I would like to use PointRCNN to train model for an specific object. I can write a dataset similar to KITTI but I am a little confused about how the place the labels. in Original KITTI the 3D box labels are in camera frame however I do not want to use labels in camera frame, I want to directly use frame of point cloud source(x:forward, y:left, z:upright), at which part of code are you transfroming the labels from cam frame to velodyne frame ?
Also is there any tips or recommendations from you for this task ?
Thank you for your help

我想向您请教一些问题，不知道可不可以加以下您的联系方式


[Network] Private IP Address Allocation wrong with LB Frontend IP create/update

Describe the bug
private_ip_allocation_method is defaulted to dynamic for lb frontend-ip create.  It should switch to 'static' if a private IP address value is provided.
Update needs to expose the ability to switch the value to dynamic.
https://icm.ad.msft.net/imp/v3/incidents/details/81867050/home

The logic in LB create is not applied to LB frontend-ip create/update.  The workaround is to create the frontend IP and then update it using generic update:
az network lb frontend-ip update -g LB_test01 --lb-name ilb -n test02_fip --set privateIpAddress=<IP_ADDRESS> --set privateIpAllocationMethod=Static

This fix will be features in the next release.


Fixes for new functions in decompiler and Blockly compiler

Fixes https://github.com/Microsoft/pxt-microbit/issues/1880
Fixes https://github.com/Microsoft/pxt-microbit/issues/1879
Fixes https://github.com/Microsoft/pxt-microbit/issues/1878
This PR adds a check to ensure only arguments with types that can be declared from blocks are allowed to be decompiled. In other words, just "number", "string", "boolean", and the types listed in pxtarget.json (just "Sprite" in arcade). This only affects user-declared functions.
I also fixed two other new function bugs I found along the way:

Array types no longer get mangled by the Blockly compiler's escaping logic
Fixed the output checks on custom arg blocks so that they handle our array and type-inheritance logic. I had to do this via a monkey-patch because it doesn't make sense to port that logic into pxt-blockly

Not in this PR


Mozilla Firefox Error: Permission denied to access property "nodeType"

Hi,
Mozilla firefox gives that error.
Error: Permission denied to access property "nodeType"
https://gallery.mailchimp.com/7beaa7cd3a83d97913970c882/images/e06f8b32-6bf6-4e11-95c8-7a5e077e123d.png
How can i fix.

Okey my bad, I solved

@hakanozkaptan I'm also seeing this issue and couldn't find an easy solution to fix this in Firefox short of disabling the type="date" that was on the same page. Did you have a better solution?

@cfuller94 I am so sorry, I don't really remember how to fix it.

@hakanozkaptan https://xkcd.com/979/

I don't remember how to fix it.

why in this hell world you thought it was a good idea to write "my bad, fixed" and close your own issue, but not report how you did it?
 I'm sorry, don't take it personal @hakanozkaptan, but I hate "fixed now" replies without any explanation...

I don't remember how to fix it.

why in this hell world you thought it was a good idea to write "my bad, fixed" and close your own issue, but not report how you did it?
 I'm sorry, don't take it personal @hakanozkaptan, but I hate "fixed now" replies without any explanation...

I feel this. I''m now running into this error. I gotta love the "nvm fixed" response. 🤦♂


“Shared with you” functions work, but “You Shared” doesn’t work

As described in the title, the "You Shared" tab is not functional. Per @karnsab , this appears to be a artifact from a previous release that is no longer supported, and should be removed from the front end.

resolved in v0.6.0


Fix Please upgrade zod package #4545

Fixes #4545
Description
Updated zod to  3.22.4 to mitigate https://security.snyk.io/vuln/SNYK-JS-ZOD-5925617
Specific Changes

Changed check(item) to safeParse(item).success per zod's new version
Modified tests to match the new zod's error messages

Testing

@ceciliaavila @sw-joelmut For comparison with yours.


Adding rule for forgotten '-r' when grepping folders

I guess it's straightforward to understand what it does :)
igor:~$ grep "is a directory" .
grep: .:  Nice job!

Thanks!

Hahaha thanks!
I'm a Python newbie and had issues to actually run thefuck locally, so
the test was useful to make sure I was not commiting BS :)
PS: code was based on copy paste from other files. As I said, noob here.
Haha
On 15 May 2015 21:07, "Pablo Aguiar"<EMAIL_ADDRESS>wrote:

One of the few pull requests with test! Nice job!
—
Reply to this email directly or view it on GitHub
https://github.com/nvbn/thefuck/pull/199#issuecomment-102552085.


ODPI-86. Test [ODPi_JRE]

Test to validate class' bytecode version.
In all fairness, this test should be fixed to accept any bytecode version less than...

The second commit basically changes the test to check if hadoop classes weren't compiled for target later than JRE8 (ie has bytecode version <=52.0)


Make it more ergonomic to make external types serializable

Today, if you have an external type (that you obviously can't annotate with [MemoryPackable]) that you want to serialize using MemoryPack, you fall off cliff where you basically have to resort to using a wrapper type + a custom formatter + register that formatter + annotate every property of that type with [MemoryPackAllowSerialize] wherever it appears.
This is clearly not the best developer experience, especially as contrasted with a simple [MemoryPackable] attribute.
I'd propose introducing an assembly-level attribute that allows users to instruct MemoryPack to generate a serializer for an external type + automatically register that in some static context using [ModuleInitializer] + have it be recognized as a memory-packable type everywhere (meaning no need for a gazillion [MemoryPackAllowSerialize]s everywhere — you can then use cutting-edge features like [UnsafeAccessor] (if necessary, to write to/invoke private properties/constructors) to source-generate serializers with no perf overhead.
Example:
[assembly: MemoryPackable<SomeExternalType>]

@neuecc Hello, would you accept a PR for a feature like this?

Update: Could potentially be closed in favor of #347, which I think is a simpler/less controversial alternative


[wip] github actions to build the backend packages

This addresses this issue. It's an implementation of some simple GitHub actions that try to go build the backend packages. go build on packages discards any binaries immediately after, only giving feedback IF there was an issue while trying to build.

TODO add win and macos
   runs-on: ubuntu-latest

/halt

backends will mostly be OS-specific, so I think the matrix approach will not work for this test. But building kpng  should, as backends will simply be added in their os-specific storecmd_xxx.go.

backends will mostly be OS-specific, so I think the matrix approach will not work for this test. But building kpng should, as backends will simply be added in their os-specific storecmd_xxx.go.

I am not sure if I get this right. Do you say: don't try to build it on all OS'. Or is just this matrix approach not working?

Because it is a little confusing to find the gh action results between different commits and branches: this is the result of the test of the last commit

lets get these passing and then merge !

for now we can ignore windows, merge and iterate ! thank you friedrich !

as a FOLLOW ON can you or neha break the code out into a Makefile?

Ok thanks for prototypeing now we know what to do #96

This PR was made obsolete by @nehaLohia27 's PR thus I will close it.


Karpenter provisioned nodes become "NotReady"

Description
Observed Behavior:
We are running EKS 1.24 dev cluster consisting of 6 nodes:

3x m5.4xlarge aimed for dev deployment workloads
3x r6i.large tainted for sts

The environment is moderately volatile, consisting of CI jobs and other CronJob as well as ~20-30 dev environments (using namespaces), each consisting of ~10 Deployment(scale=1) and 1 DaemonSet k8s objects. Totalling in ~15 pods.
We've introduced Karpenter 0.28.1 to assist with dynamic load, so that we can provision additional capacity.
The problem we are seeing is that while the "EKS Node Group" based nodes remain stable, the Karpenter nodes tend to get to:
Taints:             node.kubernetes.io/unreachable:NoExecute
                    node.kubernetes.io/unreachable:NoSchedule

Which than turns into node.kubernetes.io/unschedulable:NoSchedule
Which than gets killed by the Karpenter controller.
Expected Behavior:
Karpenter provisioned nodes should not become Unschedulable.
Reproduction Steps (Please include YAML):
I have managed to catch a snapshot of the a node going through this cycle. Please see a gist of kubectl describe node here taking 2 snapshots: 1st when node is marked as NoSchedule and the 2nd when it's already in the process of being terminated by Karpenter https://gist.github.com/maximveksler/48e303dc5782c90d7c6d4b5b167351f2
Provider spec:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: dev-capacity
spec:
  requirements:
    - key: "karpenter.sh/capacity-type" # If not included, the webhook for the AWS cloud provider will default to on-demand
      operator: In
      values: ["spot", "on-demand"]
    - key: kubernetes.io/arch
      operator: In
      values: ["amd64"]
    - key: kubernetes.io/os
      operator: In
      values:
        - linux
    - key: karpenter.k8s.aws/instance-category
      operator: In
      values:
        - c
        - m
        - r
        - t
    - key: "karpenter.k8s.aws/instance-cpu"
      operator: Gt
      values:
        - '10'
  consolidation:
    enabled: true
  providerRef:
    name: default
  kubeletConfiguration:
    systemReserved:
      cpu: 100m
      memory: 100Mi
      ephemeral-storage: 1Gi
    kubeReserved:
      cpu: 200m
      memory: 100Mi
      ephemeral-storage: 5Gi
    evictionHard:
      memory.available: 2%
      nodefs.available: 2%
      nodefs.inodesFree: 2%
    evictionSoft:
      memory.available: 200Mi
      nodefs.available: 5%
      nodefs.inodesFree: 5%
    evictionSoftGracePeriod:
      memory.available: 1m
      nodefs.available: 1m30s
      nodefs.inodesFree: 2m
    podsPerCore: 8
  limits:
    resources:
      cpu: 100
      memory: 3000Gi

---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: default
spec:
  subnetSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  securityGroupSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  blockDeviceMappings:
    - deviceName: /dev/xvda
      ebs:
        volumeSize: 384Gi

Full the complete installation steps, please see https://gist.github.com/maximveksler/38ec0cefa0ca2acccab748e71e5aebc0
Versions:

Chart Version: 0.28.1
Kubernetes Version (kubectl version):

kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-14T09:47:38Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.14-eks-c12679a", GitCommit:"05d192f0de17608d98e17761ad3cffa9a6407f2f", GitTreeState:"clean", BuildDate:"2023-05-22T23:41:27Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.27) and server (1.24) exceeds the supported minor version skew of +/-1

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

discussion context (cross referencing) https://kubernetes.slack.com/archives/C02SFFZSA2K/p1688048847670199

Is the node going NotReady by itself, pods are evicted and then Karpenter removes the node?
-or-
Does Karpenter start to deprovision the node and then cordon/drain it?
Trying to determine if its the node going bad, or just standard consolidation.

@tzneal I'm not sure.
We're currently not logging kubectl / node level logs so LMK if that's relevant and i'll make sure to catch it the next time, as this issue is a recurring problem for us, or if there's a different source for retrieving this information? In which case I'd  appreciate  guides for how to fetch.

Yes, when the node goes NotReady can you capture the logs with this log collector tool and supply them?  It may contain sensitive data, so you can submit it as a support ticket.
https://github.com/awslabs/amazon-eks-ami/tree/master/log-collector-script/linux

We've analyzed this issue internally. I don't think it's karpenter related directly.
The nodes have been terminating due resource over utilization, both memory and CPU. In both cases the kubelet process would become non responsive, which would eventually lead to not being marked unhealthy and than recycled by karpenter.
The problem is this being a dev rnd environments, with various experiments running side-by-side it's difficult to properly size pods resources. It's a matter of tolerance, for how much you over provision the requests & limit as sometimes the kernel cgroups allow to break ceiling temporary to allow the process to run when there is enough resources on the node. The problem is that for us at least, in various cases several environments decide to break budget which in turns generated the compounding effect.
To explain why it only started to appear with the introduction of karpenter - the 3x m5.4xlarge node group based nodes provided a healthy balance between number of pods, to amount of resources available. Thus, even if pods over utilized limits or in some cases didn't defined requests and limits at all, the environment would still be able to cope with that, and continue running normally. This is obviously not the case for karpenter ATM which mandates a strict node selection based on defined requests of k8s objects.
This turned it practically unusable for us in default mode, to work around it we've results to hard coding the lower bound of the node selection for the provisioner which works for us (for now).
cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: dev-capacity
spec:
  requirements:
    - key: "karpenter.sh/capacity-type" # If not included, the webhook for the AWS cloud provider will default to on-demand
      operator: In
      values: ["spot", "on-demand"]
    - key: kubernetes.io/arch
      operator: In
      values: ["amd64"]
    - key: kubernetes.io/os
      operator: In
      values:
        - linux
    - key: "karpenter.k8s.aws/instance-hypervisor"
      operator: In
      values: ["nitro"]
    - key: karpenter.k8s.aws/instance-category
      operator: In
      values:
        - c
        - m
    - key: "karpenter.k8s.aws/instance-cpu"
      operator: Gt
      values:
        - '16'
    - key: "karpenter.k8s.aws/instance-memory"
      operator: Gt
      values:
        - '50000'
    - key: "topology.kubernetes.io/zone"
      operator: In
      values: ["eu-west-3c"]
  consolidation:
    enabled: true
  providerRef:
    name: default
  kubeletConfiguration:
    systemReserved:
      cpu: 100m
      memory: 100Mi
      ephemeral-storage: 1Gi
    kubeReserved:
      cpu: 200m
      memory: 100Mi
      ephemeral-storage: 5Gi
    evictionHard:
      memory.available: 2%
      nodefs.available: 2%
      nodefs.inodesFree: 2%
    evictionSoft:
      memory.available: 200Mi
      nodefs.available: 5%
      nodefs.inodesFree: 5%
    evictionSoftGracePeriod:
      memory.available: 1m
      nodefs.available: 1m30s
      nodefs.inodesFree: 2m
  limits:
    resources:
      cpu: 100
      memory: 3000Gi

---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: default
spec:
  subnetSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  securityGroupSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  blockDeviceMappings:
    - deviceName: /dev/xvda
      ebs:
        volumeSize: 384Gi
EOF

The long term solution I believe should be ability to affect the provisioner resource calculation via a "profile", so that you will have as an example:

Economic Profile (attempts to pick the most economical node, given the resource.requests value. This should be the default)
Sparse Profile (takes as value how much "extra" resources to allocate during the node sizing calculation, per pod. Thus allowing it to respond dynamically based on cluster load)
Fixed Capacity profile (allows to define "hard coded" memory, cpu & co requests. Which will be appended to the total resource sizing performed by karpenter during node sizing).

@tzneal what's your take on this? (btw, cool script. ty!)

Generally, you should be setting request and limits as Kubelet will allow workloads to burst up to the limits value that is configured. The case were users don't define limits workloads will consume as much resource as they need. The KubeReserved and systemReserved are maintained when calculating how much resource can fit on a node, not maximum resource that can be use by a pod: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits This can result in some workloads consuming more resource then scheduler is expecting. The request and limits of the node would suggest that the pods could have been bursting beyond the capacity of what is available. The provisioning nodes Karpenter considers the resource requests and not the resources limits. Setting systemReserved may help, however the customer should consider adjusting their resources request and limits for their pods. If a container exceeds its memory request and the node that it runs on becomes short of memory overall, it is likely that the Pod the container belongs to will be evicted. A container might or might not be allowed to exceed its CPU limit for extended periods of time. However, container runtimes don't terminate Pods or containers for excessive CPU usage. If these pods were bursting and using more memory then requested, we can see this behaviors describe by the customer.


Support for text sizing, text zoom in/out

We need support for setting the size of text in the terminal and also for handling zoom in and out.
This issue depends first on the theme CSS/SCSS stuff being applied to all of the custom elements which make up the UI.

Recently fixed. The font size can be set in the Settings tab.


Hi team we were  using helm export earlier but now with 3.7.1 its removed can you let us know what is the substitute for helm export

Output of helm version:
Output of kubectl version:
Cloud Provider/Platform (AKS, GKE, Minikube etc.):

helm chart export reponame/chartname -destination 'path'

Without knowing your workflow, this is a little difficult. But, here are some ideas...
If you have pushed the chart to a repository you can then pull the chart from that repository. In that case, helm pull.
If you have the chart on the local file system you can work with it there.
The need for helm chart export was because you had put the chart/version into Helm and had it there. The current functionality doesn't have a place where you've built but not pushed the chart.

Closing this issue as answered. Please feel free to comment here and let us know if you have further questions. Thanks!


[TUZ-163] Support for data-dependent reshape and constant folding

This PR brings two features:

Data-dependent reshape
Constant folding with data-dependent reshape

cc. @zxybazh @jwfromm @gigiblender @mbaret

will send to tvm/unity


Can't build file exe

I used pyinstaller but couldn't create the exe file. I tried opening python files, only the test file showed the text.

Sorry.I can't understand english

我使用了 pyinstaller 但无法创建 exe 文件。我尝试打开 python 文件，只有测试文件显示文本。

我想将工具的显示语言更改为英语以供使用，但无法重新创建 exe 文件

程序的入口文件为editor.py，应该安装好所有pip包后编译这个文件
The entry file for the program is editor.py, and it should be compiled after installing all pip packages

Thanks, I can run now

editor.py will ask you to install additional modules, in cmd it will notify you which modules are missing, you must "pip install + ..." each module name

can you tell me what to type exactly because I always have this problem "'pyinstaller' is not recognized as an internal or external command, operable program or batch file." But I have pyinstaller in "pip list" and i tried everything : I added python to path I asked chatgpt watched a lot of videos reinstalled python and nothing changed

您能告诉我具体输入什么吗，因为我总是遇到这个问题“'pyinstaller'无法识别为内部或外部命令、可操作程序或批处理文件。但是我在“pip list”中有 pyinstaller，我尝试了所有方法：我将 python 添加到路径中，我问 chatgpt 看了很多视频重新安装 python，什么都没有改变

try it
Pyinstaller -w -i .\res\icon\editor.ico --add-data "res\icon*;res\icon" --add-data "res\support*;res\support"--add-data "res\cards\pvzhe_plants*;res\cards\pvzhe_plants"--add-data "res\cards\pvzhe_zombies*;res\cards\pvzhe_zombies"   editor.py

Thnks a lot @EFrostBlade but I always have the problem with pyinstaller  is not recognized as the name of a cmdlet can you please upload zip file of the extracted version of the pvz hybrid editor


Relocations create data in the middle of disassembly in relocatable objects

Describe the bug
Relocated instructions in relocatable objects will call applyComponentOffsetPointer. This will create data where a relocated instruction will be. That data will prevent the correct disassembly of that instruction and subsequent instructions within the function. This call was added in https://github.com/NationalSecurityAgency/ghidra/commit/2bced1cd434f7714e88a078f5ae70fa6d7c11ada. It's not entirely clear to me what the intention is here with creating a pointer offset data type template at all relocations with a non-zero addend.
To Reproduce
Open the attached object file "globals-x86.o" with default analyses and browse to the function foo
Expected behavior
The entire function should be disassembled including the return instruction.
Screenshots
The current buggy disassembly of foo:

The expected disassembly is:

Environment (please complete the following information):

OS: macOS 13.3.1
Java Version: 17
Ghidra Version: 10.3-Dev but 10.2.3 is affected
Ghidra Origin: Ghidra github

Additional context
An additional interesting thing here is these added are not subcomponents of quux, each addend is from the .bss symbol. The relocation logic as written creates offsets to subcomponents of quux rather than pointing to quuux for .bss+0x4
ReproBuggyDisassemblyRelocs.zip

Regarding your other comment about the reference representation relative to  the quux label.  This is based purely on the base reference address and the primary symbol that resides there.  In this case that is quux.  This frequently happens for an address which has ambiguous meaning (e.g., start of section, start of structure, unions, etc.).


Updated IIoT for Makers doc for IDL workflow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add topic details for legal requirements for accessibility

Resolved conflicts
Added "The Legal Aspect of Accessibility" topic
Added learningMaterial functionality
Bug fixes and code cleanup

Is there a reason you use relative paths in .html but explicit in .js? Just curious!

Can you show me exactly what you mean?
Sometimes you cannot use relative paths and sometimes you shouldn't, but if there are real inconsistencies we should fix that.

It just noticed it in the rollback pages file structure commit (https://github.com/rt2-group4/UOH-AWA/pull/11/commits/7b2b9a61dc11f351d21d6709183d4e29cb98e94c)


AttributeError: Metric 'custommetric' has no attribute [metric_need].

Hi, thank you for your work. Now I tried to run your project in a new conda env. I installed the latest recbole. But the error occurs. Do I need to correct any recbole versions?

It is recommended to try the version 1.0.1

Thanks for your quick reply.

However, when I set the recbole as 1.0.1. The error occures.

The content of error msg is as follows.
Traceback (most recent call last):
File "run_recbole_debias.py", line 7, in
from recbole_debias.quick_start import run_recbole_debias
File "/Users/Ary/dev/lab/Recbole-Debias/recbole_debias/quick_start/init.py", line 1, in
from recbole_debias.quick_start.quick_start import *
File "/Users/Ary/dev/lab/Recbole-Debias/recbole_debias/quick_start/quick_start.py", line 9, in
from recbole.data import construct_transform
ImportError: cannot import name 'construct_transform' from 'recbole.data' (/Users/Ary/anaconda3/envs/bias/lib/python3.8/site-packages/recbole/data/init.py)

I also faced the same issue and solve by adding these two line.
"/PATHTOANACONDA/anaconda3/envs/lightgcl/lib/python3.9/site-packages/recbole/evaluator/register.py"

Thanks for your contribution, I'll fix it soon.

I also faced the same issue and solve by adding these two lines. "/PATHTOANACONDA/anaconda3/envs/lightgcl/lib/python3.9/site-packages/recbole/evaluator/register.py"

Hello, @dain5832 . I follow the code change in the figure you provided and it works. But i want to know does this change safe and will not change the correctness of the project? Do you meet any problem in the future usage of this project with the code change?
Looking forward to your reply. Thank you.


Update Sysinternals forum link

It's my first pull request ever, so I hope I did well :blush:

OPS Build status updates of commit a95ac16:
:clock10: Preparing: average preparing time is 42 sec(s)

OPS Build status updates of commit a95ac16:
:clock10: Incremental building: average incremental building time is 20 sec(s)

OPS Build status updates of commit a95ac16:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 892f4d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/index.md
:white_check_mark:Succeeded
View

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

Thanks!


Add definition for "deployJava" and "FileSaver.js".

@caryhaynie thank you your contributions.
please rename fileSaver/fileSaver.d.ts to FileSaver/FileSaver.d.ts.
http://definitelytyped.org/guides/contributing.html#naming-the-file
It's exists in bower package.

Sorry for the mistake. I corrected.

@cyrilschumacher thanks mate!


Error: Could not link phinze/cask manpages to

When I run brew cask update
I get the following error: ==> Error: Could not link phinze/cask manpages to: ==>   /usr/local/share/man/man1/brew-cask.1
I've tried to rm that file. I've navigated to the dir and checked if it was gone, it was. I run brew tap --repair as instructed. No dice.
Anyone have any experience with this error?

Please always follow the guidelines for reporting bugs. If the problem persists, use the linked template to open a new issue.

phinze/cask. Wow, how long have you been without updating homebrew-cask? Or did you tap the wrong repo? Run brew uninstall --force brew-cask; brew update once.

I have meet the same problem. Do you have found any solutions?

@CSerxy
To fix the issue, please run:
brew update; brew cleanup; brew cask cleanup
brew uninstall --force brew-cask; brew update

If you are still having problems, open an issue with the appropriate template

Thanks for your help, but it seems useless for my situation.
Wind:~ cserxy$ brew update; brew cleanup; brew cask cleanup
Already up-to-date.
Error: Could not link phinze/cask manpages to:
/usr/local/share/man/man1/brew-cask.1
Please delete these files and run brew tap --repair.
==> Removing dead symlinks
Nothing to do
==> Removing cached downloads
Nothing to do
Wind:~ cserxy$ brew uninstall --force brew-cask; brew update
Already up-to-date.
Error: Could not link phinze/cask manpages to:
/usr/local/share/man/man1/brew-cask.1
Please delete these files and run brew tap --repair.
And I delete these files, it still prompts:
Wind:~ cserxy$ rm /usr/local/share/man/man1/brew-cask.1
Wind:~ cserxy$ brew tap --repair
Error: Could not link phinze/cask manpages to:
/usr/local/share/man/man1/brew-cask.1
Please delete these files and run brew tap --repair.

@CSerxy https://github.com/caskroom/homebrew-cask/issues/16094


Unexpected StartObject token (or String token etc...)

Hi,
I've been trying to find heads/tails on this problem for a good couple of hours now, and have written a number of failing tests and tried many permutations of the code, without any luck, so I'm starting to think it might actually be a bug in Newtonsoft.
I'm trying to make Newtonsoft accept a token after a custom serialiser (using 6.0.8), that reads an array into a tuple.
I have these tests, that are both failing and not failing:

  type ThisFails =
    { a : string * string
      m : Map<string, string> }

  type ThisWorks =
    { y : Map<string, string>
      z : string * string }

    testCase "failing test - array before object" <| fun _ ->
      let res = deserialise<ThisFails> Serialisation.converters
                                       """{"a":["xyz","zyx"],"m":{}}"""
      Assert.Equal("should be eq to res", { a = "xyz", "zyx"; m = Map.empty }, res)

    testCase "passing test - array after object" <| fun _ ->
      let res = deserialise<ThisWorks> Serialisation.converters
                                       """{"y":{},"z":["xyz","zyx"]}"""
      Assert.Equal("should be eq to res", { y = Map.empty; z = "xyz", "zyx" }, res)

The JsonConverter in question looks like this:
  override x.ReadJson(reader, t, _, serialiser) =
    let read, readProp, req = (read, readProp, require) $ reader

    Logger.debug logger (fun _ -> LogLine.sprintf ["type", box t] "reading json")

    let itemTypes = FSharpType.GetTupleElements t

    let readElements () =
      let rec iter index acc =
        match reader.TokenType with
        | JsonToken.EndArray ->
          // NOTE: consuming the end of the array here
          read JsonToken.EndArray |> req |> ignore

          Logger.debug logger <| fun _ ->
            LogLine.sprintf
              [ "path", reader.Path |> box
                "token_type", reader.TokenType |> box ]
              "after EndArray token, returning"

          acc

        | JsonToken.StartObject ->
          Logger.debug logger <| fun _ ->
            LogLine.sprintf
              [ "path",       reader.Path |> box
                "token_type", reader.TokenType |> box ]
              "pre-deserialise"

          let value = serialiser.Deserialize (reader, itemTypes.[index])
          read JsonToken.EndObject |> req |> ignore

          Logger.debug logger <| fun _ ->
            LogLine.sprintf
              [ "path", reader.Path |> box
                "token_type", reader.TokenType |> box ]
              "post-deserialise"

          iter (index + 1) (acc @ [value])

        | JsonToken.Boolean
        | JsonToken.Bytes
        | JsonToken.Date
        | JsonToken.Float
        | JsonToken.Integer
        | JsonToken.String ->

          Logger.debug logger <| fun _ ->
            LogLine.sprintf
              [ "path", reader.Path |> box
                "token_type", reader.TokenType |> box ]
              "value token, pre-deserialise"

          let value = serialiser.Deserialize(reader, itemTypes.[index])
          reader.Read () |> ignore

          Logger.debug logger <| fun _ ->
            LogLine.sprintf
              [ "path", reader.Path |> box
                "token_type", reader.TokenType |> box ]
              "value token, post-deserialise"

          iter (index + 1) (acc @ [value])

        | JsonToken.Null ->
          failwithf "While JS tolerates nulls, F# services don't - null found at '%s'"
                    reader.Path

        | _ as token ->
          failwithf "TupleArray: Unknown intermediate token '%A' at path '%s'"
                    token
                    reader.Path

      reader.Read () |> ignore
      iter 0 List.empty

    match reader.TokenType with
    | JsonToken.StartArray ->
      let values = readElements()
      FSharpValue.MakeTuple (values |> List.toArray, t)

    | _ ->
      failwithf "TupleArray: invalid END token '%A' at path: '%s'"
                reader.TokenType
                reader.Path

And for this failing test case, its trace is this:
checking for union type [Newtonsoft.Json.FSharp.UnionConverter]
  can_convert => false
  is_generic_type => false
  is_list => false
  type => Newtonsoft.Json.FSharp.Tests.MapConverter+NestedModule+ThisFails

reading json [Newtonsoft.Json.FSharp.TupleArrayConverter]
  type => System.Tuple`2[System.String,System.String]

value token, pre-deserialise [Newtonsoft.Json.FSharp.TupleArrayConverter]
  path => "a[0]"
  token_type => String

checking for union type [Newtonsoft.Json.FSharp.UnionConverter]
  can_convert => false
  is_generic_type => false
  is_list => false
  type => System.String

value token, post-deserialise [Newtonsoft.Json.FSharp.TupleArrayConverter]
  path => "a[1]"
  token_type => String

value token, pre-deserialise [Newtonsoft.Json.FSharp.TupleArrayConverter]
  path => "a[1]"
  token_type => String

checking for union type [Newtonsoft.Json.FSharp.UnionConverter]
  can_convert => false
  is_generic_type => false
  is_list => false
  type => System.String

value token, post-deserialise [Newtonsoft.Json.FSharp.TupleArrayConverter]
  path => "a"
  token_type => EndArray

after EndArray token, returning [Newtonsoft.Json.FSharp.TupleArrayConverter]
  path => "m"
  token_type => PropertyName

As you can see, I consume the EndArray token (not doing so make JsonNet say there's extra text), but I get no calls into MapConverter. It seems to crash before that.
Expected behaviour: don't crash on the next token after a valid deserialisation with a custom JsonConverter.
All code to debug with is here: https://github.com/haf/Newtonsoft.Json.FSharp/blob/master/src/JsonNet.Tests/MapConverter.fs#L62-L75 but I hope I've given you enough logs etc, to spot the bug/problem. Tell me if you need changes done to the repro.

I barely know F#, and I can't easily add it to the unit test project because it is C#
I and many others have used the serializer inside ReadJson and WriteJson many times without any problem.

No worries, I'll help you understand it; and since we're deserialising to F#-specific structures, writing C# wouldn't make much sense anyway - it would require a lot of wrapping at least. I'm also using the serialiser successfully in other code: https://github.com/haf/Newtonsoft.Json.FSharp/blob/master/src/JsonNet/Converters/ListConverter.fs#L35
https://github.com/haf/Newtonsoft.Json.FSharp/blob/master/src/JsonNet/Converters/ListConverter.fs#L35
match reader.TokenType with | JsonToken.StartObject -> ... is like switch (reader.TokenType) { case JsonToken.StartObject:  ...
let rec iter index acc = is like List<obj> Iter(int index, List<obj> acc) which also says it's recursive.
read JsonToken.EndArray |> req |> ignore is like:
if (!reader.Read())
  throw new Exception();

var tt =  reader.TokenType;
if (tt != JsonToken.EndArray)
  throw new Exception();

return;

acc @ [value] is like:
var accNext = acc.Clone();
accNext.Add(value);
return accNext;

This code 'bootstraps' the loop:
    match reader.TokenType with
    | JsonToken.StartArray ->
      let values = readElements()
      FSharpValue.MakeTuple (values |> List.toArray, t)

It verifies that the first token is a StartArray (because it expects JSON [ 1, 2, "hi" ] to turn into a F# tuple: 1, 2, "hi".
readElements() reads until it reaches the EndArray token and then returns the accumulated list. So from that call, we get the array. Then we create a F# tuple instance from it with FSharpValue.MakeTuple (values |> List.toArray, t) where t is the type of the tuple (a n-types-parametised generic type).
Does this make sense?

Sorry I don't know. I recommend asking on Stackoverflow. Hopefully someone with experience in both F# and Json.NET can help you.

It's alright, I've moved all my projects away from Newtonsoft.


refactor MergeGateway to cleanup Servers field

Attempt to fix https://github.com/istio/istio/issues/24118
Fixes https://github.com/istio/istio/issues/24118
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X ] Does not have any changes that may affect Istio users.

@howardjohn PTAL if this refactoring makes sense

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
fa4bb4b3c9de1033101e24051fd9be6c9134839e
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
267c6de3b54aee6e350ac5414c6a766a5cad4982
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
267c6de3b54aee6e350ac5414c6a766a5cad4982
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
267c6de3b54aee6e350ac5414c6a766a5cad4982
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
267c6de3b54aee6e350ac5414c6a766a5cad4982
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
267c6de3b54aee6e350ac5414c6a766a5cad4982
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
d2bc07538293eab29f5f26f5af7e9abdc54e064c
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

We can further refactor it to eliminate RouteNamesByServer[servers[0]] - But if you are good with this, let us get this in. I will do a follow-up

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
421a6a6481e7b5dd3c1090d84798f0ad7372160c
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
421a6a6481e7b5dd3c1090d84798f0ad7372160c
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
421a6a6481e7b5dd3c1090d84798f0ad7372160c
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
eb7dab434f8ea7e84e87228a76f3c367f6c6aa38
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
eb7dab434f8ea7e84e87228a76f3c367f6c6aa38
link
/test unit-tests_istio

lint_istio
eb7dab434f8ea7e84e87228a76f3c367f6c6aa38
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0cb01c2dfe1865a989f257c4d76d33a49ca00a29
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0cb01c2dfe1865a989f257c4d76d33a49ca00a29
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

/test integ-pilot-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0cb01c2dfe1865a989f257c4d76d33a49ca00a29
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
0cb01c2dfe1865a989f257c4d76d33a49ca00a29
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
2fa611c355e2e6a47eb6a045c5133c4a601a0ee8
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
2fa611c355e2e6a47eb6a045c5133c4a601a0ee8
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
2fa611c355e2e6a47eb6a045c5133c4a601a0ee8
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio


Have to rerun npm run build on server side code change

Unless I'm missing something, I'm under the impression that npm run build needs to be run everytime there is a change in a server-side file (eg. server.jsx or routes.js) Would be great if to have a watch flag or something on this task, since it takes quite a while to run.

Good point! Thanks for raising this as an issue, it's been bugging me for a
while as well. Would you like to take a stab at it?
On Tue, 9 Feb 2016 00:37 Charlie Clark<EMAIL_ADDRESS>wrote:

Unless I'm missing something, I'm under the impression that npm run build
needs to be run everytime there is a change in a server-side file (eg.
server.jsx or routes.js) Would be great if to have a watch flag or
something on this task, since it takes quite a while to run.
—
Reply to this email directly or view it on GitHub
https://github.com/choonkending/react-webpack-node/issues/133.

Yeah I'll take a look! Awesome work with this repo btw.

I'd just like to +1 this.

Agreed. Will take a look at this next in queue - after I have a bit of a poke around postcss :D

+1

Will fix this after I have a bit of postcss fun :)

Writing my thoughts down as I'm thinking of a good solution for this.
What we want
On npm run dev, any changes to code should trigger a change and automatically reload.
Problem
react-transform-hmr only works for any files from the entry point client.jsx. webpack-dev-middleware and webpack-hot-middleware currently only gets the webpack.config.dev.js and is compiled.
If you make changes to server.jsx or any files within the server/ folder, nothing will happen, and you will have to re-run npm run build again for a new bundle.
Potential solutions
Nodemon - nodemon will watch the files in the directory in which nodemon was started, and if any files change, nodemon will automatically restart your node application.
@psimyn suggested this to me aaages ago.
Here's a potential PR that still needs some work: https://github.com/choonkending/react-webpack-node/pull/162
Couple of considerations

Not a fan of having to npm run build for anything that involves server.jsx. Might have to have a dev version of the server bundle, to eliminate the uglifying.
Also I'm not sure I like the idea of referencing a file that could potentially not exist (due to building), from this line.

@psimyn Any ideas?

@choonkending https://www.npmjs.com/package/hot-reload ?

@psimyn What's the difference between that and nodemon? Not really sure how
this hot reloading is expected to work :(
On Sun, 6 Mar 2016 22:39 Simon Knox<EMAIL_ADDRESS>wrote:

@choonkending https://github.com/choonkending
https://www.npmjs.com/package/hot-reload ?
—
Reply to this email directly or view it on GitHub
https://github.com/choonkending/react-webpack-node/issues/133#issuecomment-192878446
.

@charlieclark @dzotokan @psimyn @caranicas
The PR will go out by the end of today - unless we find any :bug: (s).
I'm going with the nodemon approach because it's simpler. (Nodemon watches for the files/folders you wish it to watch in nodemon.json and restarts the server, you will still have to refresh your page)
I think this is a good enough change and will significantly reduce developer frustration. Now you only need to run npm run dev without EVER running npm run build. #whatatimetobealive

Unrelated stuff
In the process, I considered not doing having separate bundles for client and server side webpack, i.e. by using webpack-isomorphic-tools, like this.
That should be a separate PR if we find that we don't like our webpack config.

Merged! Please re-open if you find an issue related to nodemon (or create a new issue).

I'm in the midst of my own project for today, but I will spend tomorrow pulling this new base and moving my code over. Ill let you know how I like it.

So i was trying to use this new version, and using nodemon it is still very slow when making a change to server code. I explored the webpack docs and found the--watch command. I added to the build:webpack script in the package.json
"build:webpack": "NODE_ENV=production webpack --progress --colors --watch --config ./webpack/webpack.config.prod.js",
the only downside is i dont seem to be able to watch and  serve from the same process, so I have to open another terminal tab to run dev. But that seems like a small price to pay for a more quickly rebuilt app.

@caranicas Might have not documented it well enough, but the recent change allows you to run just npm run dev without running npm run build any longer.
It have a separate server-side rendering webpack config that does not uglify the code so it should be relatively faster.
If you run
"dev": "NODE_ENV=development nodemon",

This in turn runs
"npm run build:dev && node server/index.js"

within the nodemon.json file. Only downside to this is if you make a change to server.jsx or any of the files watched by nodemon, you would still have to refresh the page.

the only downside is i dont seem to be able to watch and serve from the same process, so I have to open another terminal tab to run dev

When in development mode, you shouldn't ever have to run npm run build:webpack any longer. I've been doing this locally, but let me know if you find any problems. Happy to hop on a channel to chat if there's still something wrong with the config. Haven't tried using dischord yet haha, but we have gitter.


How to use round up formula

I can't use round up formula in excel. Thanks for your help.

Take a look here : https://github.com/myliang/x-spreadsheet/issues/696


Add test cases for PersonIsInModulePredicate

Currently there exists no test cases for PersonIsInModulePredicate.
Thus, this pull request aims to

Add test cases for PersonIsInModulePredicate

Codecov Report
Base: 75.40% // Head: 75.47% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (efc1082) compared to base (ef91148).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #93      +/-   ##
============================================
+ Coverage     75.40%   75.47%   +0.06%
- Complexity      645      651       +6
============================================
  Files           106      106
  Lines          1952     1949       -3
  Branches        220      220
============================================
- Hits           1472     1471       -1
+ Misses          401      399       -2
  Partials         79       79

Impacted Files
Coverage Δ

...c/main/java/seedu/address/model/module/Module.java
92.72% <100.00%> (-0.38%)
:arrow_down:

...ddress/model/person/PersonIsInModulePredicate.java
100.00% <0.00%> (+33.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Setup CI using GH Actions' default Rust workflow

CI allows us to make sure that the crate builds and that the tests aren't broken on every PR.

"No news is good news", I'm merging this. :-)


Fix for missing RTC Mask file

Purpose

This branch fixes an issue where the shadow mask output file (ending in "_mask.tif") was being excluded mistakenly from RTC-S1 datasets uploaded to S3 (and subsequently published via CNM).

Proposed Changes

The regex for RTC-S1 output products in pge_outputs.yaml has been corrected to include files ending in "_mask.tif"
The regex for RTC-S1 datasets in datasets.json has been cleaned up to remove an unnecessary sub-pattern.

Issues

Fixes #671

Testing

Branch was tested on a dev cluster by submitting a SLC download job to trigger an RTC-S1 SCIFLO job (not simulated). The mask file was confirmed to be present in datasets uploaded to S3 after job completion, as well as being included in the list of files sent in the CNM notify messages.

I don't see any updates/changes to tests with this issue.  How does this functionality get tested in the PCM?

Executed a RTC-S1 PGE with S1A_IW_SLC__1SDV_20220501T015035_20220501T015102_043011_0522A4_42CC-SLC.

Verified that the sciflo job produced the mask tif file as outputs and copied into the RS S3 bucket.
Verified the mask file was included in the CNM-S msg.


mistralai dependency causes dependency conflicts when used in projects with weaviate-client due to httpx >4 (using poetry)

Hi.
We are using semantic-router and also wanted to start using Weaviate. Trying to intall weaviate-client >4 gives the following error:
Because no versions of weaviate-client match >4.5.0,<5.0.0
 and weaviate-client (4.5.0) depends on httpx (0.27.0), weaviate-client (>=4.5.0,<5.0.0) requires httpx (0.27.0).
Because mistralai (0.0.12) depends on httpx (>=0.25.2,<0.26.0)
 and no versions of mistralai match >0.0.12,<0.0.13, mistralai (>=0.0.12,<0.0.13) requires httpx (>=0.25.2,<0.26.0).
Thus, weaviate-client (>=4.5.0,<5.0.0) is incompatible with mistralai (>=0.0.12,<0.0.13).
And because semantic-router (0.0.26) depends on mistralai (>=0.0.12,<0.0.13)
 and no versions of semantic-router match >0.0.26,<0.0.27, weaviate-client (>=4.5.0,<5.0.0) is incompatible with semantic-router (>=0.0.26,<0.0.27).
So, because my-project depends on both semantic-router (^0.0.26) and weaviate-client (^4.5.0), version solving failed.

Looking at pyproject.toml, it seems there are several dependencies in the same vein as mistralai that are marked as optional. Perhaps it could be as well?
Side note: In reality, poetry should allow us to manually override dependency resolution as so many other package managers in other ecosystems, but it doesn't, and we might consider pdm for this reason.

Hi @saevarb , this requirement set currently passes constraints validation.
>> poetry show
...
semantic-router    0.0.27     Super fast semantic router for AI decision making
...
weaviate-client    4.3b2      A python native Weaviate client

Fixed by #190, closing


examples/gameexample.py raises AttributeError

gameexample.py raises AttributeError on turn 20. Here is the traceback:
Traceback (most recent call last):
  File "gameexample.py", line 103, in <module>
    main()
  File "gameexample.py", line 96, in main
    msg = world.process_event(c)
  File "gameexample.py", line 55, in process_event
    return self.tick()
  File "gameexample.py", line 73, in tick
    self.player.display = on_blue(green(bold(str(self.player.speed).decode('utf8'))))
AttributeError: 'str' object has no attribute 'decode'

I think the call to decode() is not needed.

@taotao54321 But removing decode() will break the compatibility with python2.

Good catch, I just fixed in an ugly way with https://github.com/thomasballinger/curtsies/commit/c84f717720447f44377d2ff6b41766c542600fc1
I wonder if there's something more standard, maybe in six or something. Since it's not a dependency yet I'll go with this for now.


.env file support

The package should support reading & writing to .env files.
This would likely involve writing a custom parser for it, which shouldn't be too difficult considering the syntax is simple.
Furthermore, it is worth considering whether or not the environment variables should be updated to what is in the .env file we have read in when a ConfigFile object is constructed with a .env file passed in.

Closing for now as stale


Stage parallelism does not seem to function with stage templates?

Hi,
According to the documentation, I should be able to specify parallelism by using
- stage: AcceptanceTest
  dependsOn: []    # this removes the implicit dependency on previous stage and causes this to run in parallel

This does not seem to function when the stage is a template from another file:
stages:
- template: build-api.yaml
  parameters:
    buildPlatform: $(buildPlatform)
    dependsOn: [] #tried with and without this on the first stage

- template: build-react.yaml
  parameters:
    buildPlatform: $(buildPlatform)
    dependsOn: []

- template: build-arm.yaml
  parameters:
    buildPlatform: $(buildPlatform)
    azureSubscription: $(azureSubscription)
    dependsOn: []

It also does not seem to work when specifying the two last stages to depend on the first one (so fan out).
- template: build-api.yaml
  parameters:
    buildPlatform: $(buildPlatform)

- template: build-react.yaml
  parameters:
    buildPlatform: $(buildPlatform)
    dependsOn: build-api.yaml

- template: build-arm.yaml
  parameters:
    buildPlatform: $(buildPlatform)
    azureSubscription: $(azureSubscription)
    dependsOn: build-api.yaml

Result in both cases is that they run one by one.

I have three microsoft hosted agents in the organization, and doing similar things with classic pipelines works just fine.
Am I missing something here or does it plain not work with stage templates?

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

ID: 4266f72c-c774-0046-4593-d01eb775d3c3
Version Independent ID: f20827aa-a6c5-96a8-5969-e576ffbc2e38
Content: Stages in Azure Pipelines - Azure Pipelines
Content Source: docs/pipelines/process/stages.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

Turns out I had actually misunderstood the functionality under the hood.
My stage templates did not have the dependsOn parameter in them, and in my initial example I was just giving the empty array as a parameter to the template from where nothing was done with it. And also it turns out that this is not valid syntax:
- template: build-react.yaml
  parameters:
    buildPlatform: $(buildPlatform)
  dependsOn: []

So the way I got it working was just adding
stages:
- stage: build_api
  dependsOn: []

in all of the templates individually.
One thing that might be worth documenting though, is how would one give the "empty array" dependson value into a template as a parameter correctly? Is that currently doable?

Is it possible to use same agent for every stage in the pipeline? Currently every stage picks any available agent from pool.

@C123R  You can force it to pick a particular agent with demands, like below
pool:
name: default
demands:
- 'Agent.Name -equals my-preferred-agent'

I apologize for the delay in responding.
Setting dependsOn to an empty array ([]) removes the implicit dependency on previous stage and leads to stages to running in parallel.
I think that it would be easier to accomplish what you want with the new parameters feature. I'm closing this issue for now. For implementation questions, you best bet is to ask in the Developer Community, which is monitored by the engineering team.


Pairwise velocity dispersion

Include radial and projected PVD.
CC @duncandc

@aphearin is the projected pairwise velocity distribution a thing?
radial is done.  to be included with next pull request.

yes.  dispersion.  right now i have a function for the mean and the dispersion (radial).

As far as 2D vs 3D goes, here's my opinion on the order of priority:

 vs 3D separation r
 vs 2D separation rp
sigma^2(Vz) vs. 2D separation rp
sigma^2(Vr) vs. 3D separation r

Now the remaining cases are interesting only for a much more targeted set of questions:
5. sigma^2(Vz) vs. 3D separation r
6. sigma^2(Vr) vs. 2D separation rp
7.  vs 2D separation rp
8.  vs 3D separation r
I don't think there are any other cases of interest for now. The first set is vastly more important than the second set. At some point we can add in tangential, but that can be deferred to a future PR.
@surhudm - if I have forgotten something obvious, please chime in.


I'm using Windows 11. When adding good_lp to dependencies in Cargo.toml, I'm getting compilation errors related to 'CbcSolver.lib'.

[package]
name = "jgsm-rs"
version = "0.1.0"
description = "A Tauri App"
authors = ["you"]
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[lib]
# The `_lib` suffix may seem redundant but it is necessary
# to make the lib name unique and wouldn't conflict with the bin name.
# This seems to be only an issue on Windows, see https://github.com/rust-lang/cargo/issues/8519
name = "jgsm_rs_lib"
crate-type = ["staticlib", "cdylib", "rlib"]

[build-dependencies]
tauri-build = { version = "2", features = [] }

[dependencies]
tauri = { version = "2", features = [] }
tauri-plugin-shell = "2"
serde = { version = "1", features = ["derive"] }
serde_json = "1"
scraper = "0.21.0"
reqwest = { version = "0.12.9", features = ["blocking"] }
tokio = "1.41.1"
chrono = "0.4.38"
regex = "1.11.1"
once_cell = "1.20.2"
parking_lot = "0.12.3"
rayon = "1.10.0"
rand = "0.8.5"
good_lp = "1.10.0"

error: linking with link.exe failed: exit code: 1181
(various paths...)
= note: LINK : fatal error LNK1181: 'CbcSolver.lib'
I'm having trouble finding information about this online, and even after installing cbc, I can't locate where the CbcSolver.lib file should be. It's difficult to find relevant documentation about this issue.

MRE:

Cargo.toml

[package]
name = "scratch"
version = "0.1.0"
edition = "2021"

[lib]
name = "scratch_lib"
crate-type = ["cdylib"]

[dependencies]
good_lp = "1.10.0"

lib.rs (I had to code something that uses good_lp to trigger the error, so here is a simple LP problem)

use good_lp::{default_solver, variable, Expression, ProblemVariables, Solution, SolverModel};

pub fn example(n: usize) {
    let mut vars = vec![];
    let mut pvars = ProblemVariables::new();
    let mut sum = Expression::from_other_affine(0.);
    for i in 0..n {
        vars.push(pvars.add(variable().min(0).max(1)));
        sum += vars[i];
    }
    let mut solver = pvars.maximise(sum).using(default_solver);
    for w in vars.windows(3) {
        solver.add_constraint(w[0] + w[1] + w[2] << 1);
    }
    let solution = solver.solve().unwrap();
    for var in vars {
        println!("{}", solution.value(var));
    }
}

The error is only triggered when crate_type is cdylib. It builds fine with rlib and staticlib.


fix: add react hooks eslint plugin & fix dependencies

This is an alternative to the changes proposed by @hwbllmnn without the breaking change.
Instead of allowing null as a parameter to be passed in, I would rather check it before if needed. The less null, the better :)

This is the diff to the changes of @hwbllmnn:
diff --git a/src/Hooks/useMeasure/useMeasure.ts b/src/Hooks/useMeasure/useMeasure.ts
index 1fd450b..6131d37 100644
--- a/src/Hooks/useMeasure/useMeasure.ts
+++ b/src/Hooks/useMeasure/useMeasure.ts
@@ -1,5 +1,4 @@
import MeasureUtil from '@terrestris/ol-util/dist/MeasureUtil/MeasureUtil';
-import _isNil from 'lodash/isNil';
import OlCollection from 'ol/Collection';
import { Coordinate as OlCoordinate } from 'ol/coordinate';
import OlFeature from 'ol/Feature';
diff --git a/src/Hooks/useModify/useModify.ts b/src/Hooks/useModify/useModify.ts
index 62892f4..a2f61ae 100644
--- a/src/Hooks/useModify/useModify.ts
+++ b/src/Hooks/useModify/useModify.ts
@@ -95,7 +95,7 @@ export const useModify = ({
const layer = usePropOrDefault(
digitizeLayer,

() => DigitizeUtil.getDigitizeLayer(map),

() => map ? DigitizeUtil.getDigitizeLayer(map) : null,
[map]
);

diff --git a/src/Util/DigitizeUtil.ts b/src/Util/DigitizeUtil.ts
index 4acfc5b..f8bc021 100644
--- a/src/Util/DigitizeUtil.ts
+++ b/src/Util/DigitizeUtil.ts
@@ -94,10 +94,7 @@ export class DigitizeUtil {
*
* @param map
*/

static getDigitizeLayer(map: OlMap | null): OlVectorLayer | null {
if (!map) {

 return null;

}

static getDigitizeLayer(map: OlMap): OlVectorLayer {
let digitizeLayer = MapUtil.getLayerByName(map, DigitizeUtil.DIGITIZE_LAYER_NAME) as OlVectorLayer;
if (!digitizeLayer) {

And I just noticed that the defaultFunc should not be part of the dependencies of usePropOrDefault - this will cause to many reevaluations


Add support for other jetbrains applications

This project is great. Can we support more jetbrains applications? For example, IDEA, Pycharm, clion, Android studio

one singular lookup for all of them?
it's doable but it will break because the folders keep changing on every release.
i havent been using windows recently, but if you want to implement this all you need to do is find the recentProjects.xml file locations for the other applications like in PluginQuery.fs
https://github.com/aciq/PowerToys-WebStormWorkspaces/blob/5d4a52713efcacd998c4fc9513b28674fc41da1a/PluginQuery.fs


Have holding Ctrl+P mimic holding down the power button

This would rock!

I implemented it on master :wink:


pop'ing and pushing the first route leads to black screen when back is pressed

When you have two routes, A and B, and you pop and push to Route B, pressing back on Route B should close the app, rather it takes you to a black screen, and then it doesn't respond to the back button anymore and I have to kill the app.
Navigator.of(context)..pop()..pushNamed("/home");
Video here https://www.dropbox.com/s/7vv90ddge9panrk/overflow2.mp4?dl=0

I don't understand why the app wouldn't close when you do the first pop.

Not sure, I'm just trying to make sure the SplashPage route is poped from the back stack

You probably actually want to be using pushReplacement or pushReplacementNamed.

Yes! thats what I was looking for!

The workaround for this bug is calling SystemNavigator.pop() if Navigator.pop() returns false.

One issue might be that SystemNavigator.pop() does nothing on iOS, because the human interface guidelines prohibit exiting the app. There shouldn't be a hardware back button on iOS, so this would only happen when pressing on screen buttons that pop the navigator. I think this is an argument for why on iOS putting a / route onto the stack below the deep-link if there's already is a good idea.

The specific action we want to take on this bug is that calling Navigator.pop() should imply a SystemNavigator.pop() (via a callback installed by the WidgetsApp maybe) when appropriate (when there's only one route). On iOS this may need to assert or otherwise fail in some way, maybe just not popping the route at all.

Specifically, this is to handle the case where the app was launched as a "subactivity" of another, and so there's a BackButton on the screen (or equivalent), and tapping that should pop the app off entirely (quitting it). On iOS this can't happen as I understand it.

This will probably be addressed via https://github.com/flutter/flutter/issues/11490.

My current ETA on this is that I expect to work on it in a couple of months, I'm working on RTL first. Please let us know if that time-frame isn't sufficient; we can work on more narrowly-scoped work sooner if it is urgent.

Leaving in current milestone as it is a current priority (deep linking improvements).

facing same issue.

I'm going to close this in favour of https://github.com/flutter/flutter/issues/11490 which is basically the same thing. That bug itself will probably get closed as part of my Router work.

Now it's all 2019, so how do we fix this, urgently?

Is there any solution for this problem ?

Now it's all 2019, so how do we fix this, urgently?

FYI see the comment above about this issue being closed in favour of #11490.  Thumbs up and comments on this issue probably aren't being followed by the flutter team, so won't help - go to issue #11490 instead and add a thumbs up to the first post, the more reactions there are the higher up an issue gets prioritised by the flutter devs.
PS I managed to work around the issue by using Navigator.pushReplacement instead of Navigator.popAndPush - it might help in your case too?

any solution ?

my workaround with WillPopScope widget
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

class SomeScreen extends StatefulWidget {
  final Widget child;

  SomeScreen({
    @required this.child,
  });

  @override
  State<StatefulWidget> createState() => _SomeScreenState();
}

class _SomeScreenState extends State<SomeScreen> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: WillPopScope(
        onWillPop: () {
          if (Navigator.of(context).canPop()) {
            Navigator.of(context).pop();
          } else {
            // Android back button hack
            SystemNavigator.pop();
          }
          return Future.value(true);
        },
        child: widget.child,
      ),
    );
  }
}

WillPopScope worked for me also:
return WillPopScope(       onWillPop: () async => false,       child: Scaffold(         body: Container(             child: TextButton(                 onPressed: () {                   Navigator.of(context).pop();                 },                 child: Text('Go back'),                 ),               ),       ),     );


make a shared / multisig admin account for the contracts

i.e. shared, but private, mnemonic

just needs put on github

Is this not done? I'm moving to needs refinement because I don't know


Need support for importing and exporting markdown in a custom node editor

Hello @petyosi,
I have created a custom plugin for the editor using the lexical decorator node, and I need to import and export markdown in the editor component. But I see that you haven't exported the following cells in the package. Could you please look into that and export those? The custom plugin is similar to the built-in table plugin, but the editor(TableEditor) is a bit different.
`
// import configuration
/** @internal /
export const importVisitors$ = Cell<MdastImportVisitor<Mdast.Nodes>[]>([])
/* @internal /
export const syntaxExtensions$ = Cell<MarkdownParseOptions['syntaxExtensions']>([])
/* @internal /
export const mdastExtensions$ = Cell<NonNullable<MarkdownParseOptions['mdastExtensions']>>([])
/* @internal */
export const usedLexicalNodes$ = Cell<Klass[]>([])
// export configuration
/** @internal /
export const exportVisitors$ = Cell<NonNullable<LexicalConvertOptions['visitors']>>([])
/* @internal /
export const toMarkdownExtensions$ = Cell<NonNullable<LexicalConvertOptions['toMarkdownExtensions']>>([])
/* @internal */
export const toMarkdownOptions$ = Cell<NonNullable<LexicalConvertOptions['toMarkdownOptions']>>({})
`

Here's the PR


Camera.positionWC incorrect for 2D and CV

Related to this post in the forum: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/Qc2Vvu26lBI
In this example, hit Save, then move the camera, then hit Load.  The loaded position will not be the same as the saved position.  However, if you save a position in 3D and load it in 2D, it will be correct.  That's what makes me think the positionWC in 2D is incorrect.  Unless there's a different way you're supposed to save/load the camera in 2D.
var viewer = new Cesium.Viewer('cesiumContainer', {sceneMode: Cesium.SceneMode.SCENE2D});
var camera = viewer.scene.camera;
var position;

Sandcastle.addToolbarButton('Save', function() {
    position = camera.positionWC.clone();
});

Sandcastle.addToolbarButton('Load', function() {
    viewer.scene.camera.setView({
        destination:  position.clone()
    });
});

Brought up in the forum again: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/9WG9SEAgT0s

Workaround for CV
var viewer = new Cesium.Viewer('cesiumContainer', {sceneMode: Cesium.SceneMode.COLUMBUS_VIEW});
var camera = viewer.scene.camera;
var position;

Sandcastle.addToolbarButton('Save', function() {
    var cartographic = viewer.scene.mapProjection.unproject(camera.position);
    position = viewer.scene.mapProjection.ellipsoid.cartographicToCartesian(cartographic);
});

Sandcastle.addToolbarButton('Load', function() {
    viewer.scene.camera.setView({
        destination:  position.clone()
    });
});

Related: https://groups.google.com/d/msg/cesium-dev/Q9-C5tmImIc/YXY2lSFmBQAJ

Brought up on the forum, I think this is causing issues with zooming in orthographic mode: https://groups.google.com/forum/#!topic/cesium-dev/hBNRZ69Tx20

directionWC (and I'm assuming rightWC/upWC but I haven't checked) also seem incorrect in CV

positionWC is working as expected after all.  "World coordinates" means using the world coordinate system, which is different between 3D, 2D and CV.  For example, in 3D Z is north and Y is east.  In CV, X is up.  I opened #6864 to add a helper function for users who want to get the camera position and orientation in the 3D coordinate system regardless of the current scene mode.

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/?hl=en#!topic/cesium-dev/Qc2Vvu26lBI
https://groups.google.com/forum/?hl=en#!topic/cesium-dev/9WG9SEAgT0s
https://groups.google.com/d/msg/cesium-dev/Q9-C5tmImIc/YXY2lSFmBQAJ
https://groups.google.com/forum/#!topic/cesium-dev/hBNRZ69Tx20
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/issues/3845 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:


Add bower.json file

Could you add the project to bower?
Thanks in advance

I've added bower.json.
Can you check to see if everything is working?

I have tested. I can install the package, but ./libs folder is missing.
Maybe you just haven't pushed the git tag.
Check this out

I have just realized that int the bower.json file the version detailed is "1.3.5" and the current one is "1.3.6"

Do I have to re-register after modifying the json ?

There, I fixed it.

Excellent, thanks!


[glslang] Export CMake package files

I've added a file to patch glslang's CMake files so that glslang can be used as a CMake package and can be used in a project with the find_package command

 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.:x: DethRaid sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Alright, just confirming that this PR is all ready to go. It now properly adds targets on all platforms that can be easily consumed by anyone using vcpkg. I also trimmed down the patch file to make it as small as possible for the changes we needed.

Can this patch be upstreamed?

I can certainly try, I have no idea what KhronosGroup's opinion on mucking with their build system is.

On closer inspection, they use cmake 2.8.13 minimum and I don't know if the export command even existed way back then.


Update to 13 Nov 2016 version

The demo version in gh-pages uses an old version (see #10) so update it from commit 49549a7f1b79dc9c6730ac0775bf89b0c52e7afc from master.

Closing in favour of PR https://github.com/stml/welcomejs/pull/12.


Add jazzy

let sphinx-multiversion create a page for Jazzy Jalisco, pointing to all rolling/master subrepos.
fyi: There is already one at https://docs.ros.org/

@saikishor there is no hurry for merging it, but there won't be any changes necessary unless we branch the subrepos for jazzy

@saikishor there is no hurry for merging it, but there won't be any changes necessary unless we branch the subrepos for jazzy

Ofcourse, I agree. If that's the case, we can then merge it.

Let's wait until Jazzy is included in index.ros.org and docs.ros.org/api

The changes seem correct to me though I haven't fully understood the multiversion build, yet.

The core setting is the smv_branch_whitelist: Every branch matching this regex will be built as multiversion. The other stuff is only for auto-replacement of macros in the docs, as well as checkout the correct branches of the subrepos.

After merging this, I'll rename the default branch of this repo from master to rolling (similar to https://github.com/ros2/ros2_documentation) to make sphinx-multiversion write "Rolling" instead of "Master"


Difference between addJob and updateJob?

There is currently no difference between addJob and updateJob, see:
https://github.com/doowb/firebase-cron/blob/master/index.js#L65
https://github.com/doowb/firebase-cron/blob/master/index.js#L86
I would have expected updateJob to execute the job if it is pending before recomputing _getNextDateFrom. Currently it does not, is this intentional?
Scenario where it would be useful:

daily job A is created by these commands:cron = new Cron()
cron.updateJob(job A)

the server is stopped
the nextRun date for job A (00h00) passes
the server is restarted and executes the same commands as in the first step
the job A is executed by updateJob() because the 00h00 deadline was missed
updateJob updates nextRun and we're back to normal without missing a task

You're correct that there are no differences between addJob and updateJob. I had stubbed out the methods for the api before implementing them and didn't really see how they could differ.
I like your suggestion of not overwriting the current record, but I'm not sure if executing the job first, then updating is the correct approach.
I usually have 2 scripts, one for initializing my jobs (if they aren't added dynamically) and another for starting the cron server that executes the jobs. This lets me start the cron server and it will pick up any jobs that were missed while the server was stopped.
I think what you can do is check to see which jobs have already been registered, then register any that are missing (this should provide the affect your looking for).
var each = require('async-each');
var jobs = {
 'job-1': {
   pattern: '00 00 00 * * *',
   data: {foo: 'bar'}
 },
 'job-2': {
   pattern: '00 00 02 * * *',
   data: {baz: 'qux'}
 }
};

cron.getJobs(function(err, existing) {
 if (err) return console.error(err);
 each(Object.keys(jobs), function(name, next) {
   if (existing.hasOwnProperty(name)) {
     return next();
   }
   var job = jobs[name];
   cron.addJob(name, job.pattern, job.data, next);
 }, function(err) {
   if (err) return console.error(err);
   console.log('finished adding jobs');
 });
});

I'm adding this here just as an example and show anyone else seeing this might find it useful.
I think more options or other api methods could be useful for handling some of these scenarios. Like a flag to specify that addJob should only add the job if it doesn't already exist. Or maybe that should be the default and updateJob should always add/update a job.


IRegistrationconvention Process (v. 3) vs. ScanTypes (v. 4)

Hi Matt,
The latest version of StructureMap implements Process in the ControllerConvention class.
How do I implement Scantypes(TypeSet types, Registry registry) with the newest version of StructureMap?
Thanks in advance.

Something like this...
public void ScanTypes(TypeSet types, Registry registry)
{
// Only work on concrete types
types.FindTypes(TypeClassification.Concretes | TypeClassification.Closed).Each(type =>
{
// Register against all the interfaces implemented
// by this concrete class
type.GetInterfaces().Each(@interface => registry.For(@interface).Use(type));
});
}


Alternate way of setting enter / leave support

Great library. Yet I'm having a problem enabling enter / leave support. There are frameworks out there that do not allow you to place static JS code before embedding a library, like Meteor (at least, they don't allow it without some hacking). So it would be great if enter / leave support would either be enabled by default, or if there were an explicit function call to trigger that support.

This seems like a reasonable request.
Making this configurable post-load would require a bit of architectural changes, but could be done.
I like enabling these events by default more though. It's an easy change and I have it turned on for all my projects anyway. Based on the various bug reports that I've seen, people seem to use this functionality more than not, so it makes sense to make it the default in that sense as well. In addition, the rewrite branch already has it on by default.
@timruffles Do you see a problem with changing the default behavior as if enableEnterLeave: true?

Nope that seems fine. Let's bump the major version number, and maybe add a
CHANGELOG.md so we're done our best to let people know.
On Mon, Oct 5, 2015 at 9:05 AM, Kaur Kuut<EMAIL_ADDRESS>wrote:

This seems like a reasonable request.
Making this configurable post-load would require a bit of architectural
changes, but could be done.
I like enabling these events by default more though. It's an easy change
and I have it turned on for all my projects anyway. Based on the various
bug reports that I've seen, people seem to use this functionality more than
not, so it makes sense to make it the default in that sense as well. In
addition, the rewrite branch already has it on by default.
@timruffles https://github.com/timruffles Do you see a problem with
changing the default behavior as if enableEnterLeave: true?
—
Reply to this email directly or view it on GitHub
https://github.com/timruffles/ios-html5-drag-drop-shim/issues/49#issuecomment-145458280
.

Great!


pull request for e2e test at 11/27/2016 05:56:04

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