translating 'grad_h[h<0] = 0'

I am trying to translate https://pytorch.org/tutorials/beginner/examples_tensor/two_layer_net_tensor.html#sphx-glr-beginner-examples-tensor-two-layer-net-tensor-py to tch-rs.
It's not clear to me how to translate the following line:
grad_h[h<0] = 0

My understanding is that h<0 is supposed to return a vec of bool, which we use as a mask for which elements of grad_h to modify.
It's not clear to me how to do this in a 'parallel' (i.e. not a single for loop) in tch-rs.

I haven't tested but maybe you can do something like the following ?
let grad_h = grad_h * h.ge(0.).to_kind(Kind::Float)
This would compute h >= 0 as a boolean, then convert int to a float which should be 0 or 1 and do a pointwise multiplication. Probably worth checking the output on a couple examples but hopefully that would do the trick.

To the extent I have the legal rights to do, I'd like to offer the following (a translation / derivative work of https://pytorch.org/tutorials/beginner/examples_tensor/two_layer_net_tensor.html#sphx-glr-beginner-examples-tensor-two-layer-net-tensor-py ) as additional sample code:
Besides the let grad_h = grad_h * h.ge(0.).to_kind(Kind::Float) trick, it's a direct translation.
fn main(opts: (tch::Kind, tch::Device)) {
    println!("main test");
    let (d_n, d_in, d_h, d_out) = (64, 1000, 100, 10);

    let x = tch::Tensor::randn(&[d_n, d_in], opts);
    let y = tch::Tensor::randn(&[d_n, d_out], opts);

    let mut w1 = tch::Tensor::randn(&[d_in, d_h], opts);
    let mut w2 = tch::Tensor::randn(&[d_h, d_out], opts);

    let learning_rate = 1e-6;

    for i in 0..500 {
        let h = x.mm(&w1);
        let h_relu = h.clamp_min(0);
        let y_pred = h_relu.mm(&w2);
        let loss = (&y_pred - &y).pow(2).sum();
        println!("{}: {:?}", i, loss);

        let grad_y_pred = 2.0 * (&y_pred - &y);
        let grad_w2 = h_relu.transpose(0, 1).mm(&grad_y_pred);
        let grad_h_relu = grad_y_pred.mm(&w2.transpose(0, 1));
        let grad_h = grad_h_relu * h.ge(0.).to_kind(tch::Kind::Float);
        let grad_w1 = x.transpose(0, 1).mm(&grad_h);

        w1 -= learning_rate * grad_w1;
        w2 -= learning_rate * grad_w2;
    }
}

#[test]
fn test_00() {
    let opts = (tch::Kind::Float, tch::Device::Cpu);
    main(opts)
}

Code appears to work: output:
main test
0: [34260284]
1: [32717616]
2: [35069400]
3: [34915180]
4: [29025518]
5: [19116674]
6: [10442851]
7: [5215584]
8: [2716956.5]
9: [1597051]
10: [1077723.5]
11: [806905.6875]
12: [643919.9375]
13: [532315.875]
14: [448856.5625]
15: [383128.1875]
16: [329637.0625]
17: [285379.1875]
18: [248298.359375]
19: [216973.46875]
20: [190334.21875]
21: [167557.953125]
22: [148002.375]
23: [131113.96875]
24: [116475.3671875]
25: [103731.03125]
26: [92597.359375]
27: [82841.921875]
28: [74268.0703125]
29: [66709]
30: [60016.53125]
31: [54088.41015625]
32: [48823.796875]
33: [44134.609375]
34: [39949.82421875]
35: [36208.046875]
36: [32862.96484375]
37: [29861.57421875]
38: [27163.69921875]
39: [24734.12109375]
40: [22543.10546875]
41: [20565.583984375]
42: [18777.408203125]
43: [17159.69921875]
44: [15693.8330078125]
45: [14364.0234375]
46: [13156.2861328125]
47: [12058.017578125]
48: [11058.720703125]
49: [10148.5263671875]
50: [9319.212890625]
51: [8562.736328125]
52: [7871.6298828125]
53: [7240.029296875]
54: [6662.66552734375]
55: [6134.64892578125]
56: [5650.7060546875]
57: [5207.15234375]
58: [4800.38525390625]
59: [4427.21630859375]
60: [4084.65625]
61: [3770.163818359375]
62: [3481.187255859375]
63: [3215.48095703125]
64: [2971.60302734375]
65: [2747.099853515625]
66: [2540.377197265625]
67: [2349.89306640625]
68: [2174.292236328125]
69: [2012.3524169921875]
70: [1862.973388671875]
71: [1725.17919921875]
72: [1597.97509765625]
73: [1480.51025390625]
74: [1372.021484375]
75: [1271.76953125]
76: [1179.1275634765625]
77: [1093.469970703125]
78: [1014.2444458007813]
79: [940.973876953125]
80: [873.1773071289063]
81: [810.4569702148438]
82: [752.4011840820313]
83: [698.6286010742188]
84: [648.8204345703125]
85: [602.6876831054688]
86: [559.94140625]
87: [520.3128662109375]
88: [483.5766296386719]
89: [449.5108947753906]
90: [417.94464111328125]
91: [388.6556396484375]
92: [361.4674987792969]
93: [336.24249267578125]
94: [312.8373718261719]
95: [291.1053161621094]
96: [270.9220886230469]
97: [252.18289184570313]
98: [234.78280639648438]
99: [218.61538696289063]
100: [203.5952911376953]
101: [189.63330078125]
102: [176.65658569335938]
103: [164.59197998046875]
104: [153.37435913085938]
105: [142.94175720214844]
106: [133.24234008789063]
107: [124.21937561035156]
108: [115.82464599609375]
109: [108.01161193847656]
110: [100.74175262451172]
111: [93.97444915771484]
112: [87.67327880859375]
113: [81.80506896972656]
114: [76.3422622680664]
115: [71.25404357910156]
116: [66.51329803466797]
117: [62.09667205810547]
118: [57.98186492919922]
119: [54.14569091796875]
120: [50.57160949707031]
121: [47.237030029296875]
122: [44.12919616699219]
123: [41.23194122314453]
124: [38.53001022338867]
125: [36.009193420410156]
126: [33.65830993652344]
127: [31.464611053466797]
128: [29.418720245361328]
129: [27.50872230529785]
130: [25.725427627563477]
131: [24.061630249023438]
132: [22.508499145507813]
133: [21.058027267456055]
134: [19.703481674194336]
135: [18.439287185668945]
136: [17.257568359375]
137: [16.15477180480957]
138: [15.123416900634766]
139: [14.160041809082031]
140: [13.259425163269043]
141: [12.417962074279785]
142: [11.631413459777832]
143: [10.895730018615723]
144: [10.208312034606934]
145: [9.565279960632324]
146: [8.963581085205078]
147: [8.401830673217773]
148: [7.875828742980957]
149: [7.382791519165039]
150: [6.922338962554932]
151: [6.491796970367432]
152: [6.088073253631592]
153: [5.7103657722473145]
154: [5.356616020202637]
155: [5.0256452560424805]
156: [4.715524673461914]
157: [4.425028324127197]
158: [4.152915000915527]
159: [3.8980093002319336]
160: [3.6594557762145996]
161: [3.435666084289551]
162: [3.225914478302002]
163: [3.0295639038085938]
164: [2.845404624938965]
165: [2.6725549697875977]
166: [2.510826826095581]
167: [2.3589487075805664]
168: [2.2165966033935547]
169: [2.0831785202026367]
170: [1.9577014446258545]
171: [1.8404662609100342]
172: [1.7301545143127441]
173: [1.6266480684280396]
174: [1.5297385454177856]
175: [1.4386940002441406]
176: [1.352889895439148]
177: [1.272759199142456]
178: [1.197373390197754]
179: [1.1265606880187988]
180: [1.0600446462631226]
181: [0.9974740743637085]
182: [0.9388630986213684]
183: [0.8838181495666504]
184: [0.8320485353469849]
185: [0.7833105325698853]
186: [0.7375422716140747]
187: [0.6944899559020996]
188: [0.6540900468826294]
189: [0.6161644458770752]
190: [0.5804455876350403]
191: [0.5468751788139343]
192: [0.5151917934417725]
193: [0.485488623380661]
194: [0.457588791847229]
195: [0.4313516318798065]
196: [0.406649112701416]
197: [0.3833242952823639]
198: [0.36140576004981995]
199: [0.3407328128814697]
200: [0.32142406702041626]
201: [0.303079754114151]
202: [0.2858888804912567]
203: [0.26974642276763916]
204: [0.25449246168136597]
205: [0.24014046788215637]
206: [0.22659197449684143]
207: [0.21385924518108368]
208: [0.2018306404352188]
209: [0.1904999315738678]
210: [0.17985865473747253]
211: [0.16983194649219513]
212: [0.1603270024061203]
213: [0.15140242874622345]
214: [0.1429554522037506]
215: [0.13500405848026276]
216: [0.12753276526927948]
217: [0.12046453356742859]
218: [0.11384101957082748]
219: [0.10755111277103424]
220: [0.101639524102211]

Here's a translation of https://pytorch.org/tutorials/beginner/examples_autograd/two_layer_net_autograd.html#sphx-glr-beginner-examples-autograd-two-layer-net-autograd-py
use super::*;

fn main(opts: (tch::Kind, tch::Device)) {
    println!("main test");
    let (d_n, d_in, d_h, d_out) = (64, 1000, 100, 10);

    let x = tch::Tensor::randn(&[d_n, d_in], opts);
    let y = tch::Tensor::randn(&[d_n, d_out], opts);

    let mut w1 = tch::Tensor::randn(&[d_in, d_h], opts);
    let mut w2 = tch::Tensor::randn(&[d_h, d_out], opts);

    w1.set_requires_grad(true);
    w2.set_requires_grad(true);

    let learning_rate = 1e-6;
    for i in 0..500 {
        let y_pred = x.mm(&w1).clamp_min(0).mm(&w2);
        let loss = (&y_pred - &y).pow(2).sum();
        println!("{}: {:?}", i, loss);

        loss.backward();

        tch::no_grad(|| {
            w1 -= learning_rate * w1.grad();
            w2 -= learning_rate * w2.grad();
            w1.zero_grad();
            w2.zero_grad();
        });
    }
}

#[test]
fn test_00() {
    let opts = (tch::Kind::Float, tch::Device::Cpu);
    main(opts)
}

Looks nice! I think it would be interesting to have these as sample code indeed. Would you mind making some small PR to integrate these, e.g. in examples/basics, and pointing at the original source so that people can easily compare ? (if you don't have the time to do so I can have a look at it)

Long term it makes sense to submit pull requests. Let me translate a few more tutorials and see if I can organize this a bit better.

Closing this one now, feel free to re-open if you encounter further similar issues.


Path not working

I am trying to create a custom path animation and it doesn't seem to be animating for me. I tried the demo (heart) code here http://jsfiddle.net/xrbfw21o/1/ yet that doesn't seem to work either.
Any idea what's going on?

 Didn't call the animate function... http://jsfiddle.net/xrbfw21o/2/

On a side, note, is there a way to use a custom SVG path for a bunch of elements without copying the SVG originally? As in initialize it once in the HTML but have ProgressBar copy it for as many elements as I need it on?

progressbar.js doesn't provide the copy functionality you would need, you have to figure a way to copy the SVG element outside this library.


Development 1.1 calender

Related Issues
#265

Why do we do all these requests??

we didn't do that in the old client

The meeting link should open in another window

use target= _blank to achieve that

The current calendar doesn't display Birthdates or Publick holidays

Clicking outside the dialog and on the Exc key should close it

Screencast from 01-23-2024 11:55:58 PM.webm

Does this card need a background?

The request should be based on the chosen month, and we should show a loading indicator until the events have loaded.
Screencast from 01-23-2024 11:58:36 PM.webm

Does this need to be changed? The color I mean
Screencast from 01-24-2024 12:01:05 AM.webm

Why do we do all these requests??
we didn't do that in the old client

it's because we're retrieving every user that applied for a vacation to display his/her name in the title, this feature was discussed in the demo and approved by @xmonader

got this error when clicked on the vacation event

did you miss the birth date events?

I got this error after clicking on the Public Holiday event, maybe we need a detail card there

Does this need to be changed? The color I mean
Screencast.from.01-24-2<IP_ADDRESS>.AM.webm

@ehab-hassan Should be handling any styling issues(colors, fonts, etc..)

ll handle all styling and color when merged to development_1.1


Disable macOS CI temporarily

This makes it easier to tell when PR validation succeeds.
(It also removes the risk of someone doing a bad PR merge if a real error is mistaken for the known macOS failure, but this isn't IMO very significant for our small team vs. a repo like dotnet/runtime where it matters much more.)

@dseefeld @crummel ok to merge without full CI? macOS isn't involved in the gathering/bootstrap legs and this removal is very targeted. It would be nice to get this in ASAP to remove clutter from other PRs.


primaryData attribute in Media Type Object

Media Type Object should have an optional primaryData attribute, to specify the name of the property, where the primary data is located in the schema.
It is very common to return the response object wrapped in a top level property. This way, it is possible to provide additional metadata as well. Example:
responses:
  '200':
    description: successful operation
    content:
      application/json:
        schema:
          type: object
          properties:
            data:
              $ref: '#/components/schemas/User'
            meta:
              $ref: '#/components/schemas/Metadata'
          required: ['data']
        primaryData: data

The OpenApi tools could better understand these type of responses. It would be possible to express, that the data attribute is not really part of any schemas/objects. It is just a wrapper.
The SDK Generators could benefit from this primaryData attribute as well. At the moment, these kind of responses usually have to be manually unwrapped.

Related: #519, #555, #957, #1749

Envelopes can be implemented in OAS 3.0 using dynamic references.  The value of $dynamicAnchor could be chosen to indicate the primary-ness (or you could just use a custom annotation, since JSON Schema wouldn't need to do anything with it).
Would that address your use case?

That seems to be a really useful feature, but I'm not sure that it would solve the original issue.
Adding something like primaryData to the spec would standardise this behaviour, so SDK generators could expect it and handle these structures more conviniently.

@K-Adam I'm a bit reluctant to "standardize" something about message bodies outside of media types.  #3771 proposes an extensible registry of media type models.
Given that, you could define a vendor- or personal-tree media type (e.g. application/vnd.whoever.envelope+json) that indicates how the envelope works.  Perhaps with a media type parameter giving a JSON Pointer to the content.
I realize it's not as clean of a solution as another field, but it might be easier to get done.  If an experimental media type such as this takes off, then adding support directly to the OAS would be a lot easier to sell.  I suppose one could also experiment with an x- field that does what you're asking for and see if that gets uptake as well.


[Discussion] React to StackExchange.Redis v2.0

We are introducing two new packages to use StackExchange.Redis 2.0 with ASP.NET Core Caching and SignalR. We are also introducing support for using Redis to store DataProtection key material using StackExchange.Redis 2.0.
For ASP.NET Core 2.2 we will continue to ship our existing packages which use StackExchange.Redis 1.0, to preserve compatibility for existing users. However, we suggest you update to the new package as soon as possible. These packages are now considered deprecated and will be removed in ASP.NET Core 3.0.
Caching
We are releasing a new package "Microsoft.Extensions.Caching.StackExchangeRedis" which will depend on StackExchange.Redis 2.0. "Microsoft.Extensions.Caching.Redis" will continue to ship in ASP.NET Core 2.2 with the StackExchange.Redis 1.0 dependency and will be removed in 3.0.
To use the new package, remove your dependency on Microsoft.Extensions.Caching.Redis (if present), and add a dependency to "Microsoft.Extensions.Caching.StackExchangeRedis". Next, change your AddDistributedRedisCache invocation in ConfigureServices to AddStackExchangeRedisCache. No further changes should be necessary.
DataProtection
The "Microsoft.AspNetCore.DataProtection.Redis" package is new in ASP.NET Core 2.2 and depends on StackExchange.Redis 1.0 in Preview 2. In Preview 3, this package has been renamed to "Microsoft.AspNetCore.DataProtection.StackExchangeRedis" and has been updated to use StackExchange.Redis 2.0.
To use the new package, remove your dependency on Microsoft.AspNetCore.DataProtection.Redis (if present), and add a dependency to "Microsoft.AspNetCore.DataProtection.StackExchangeRedis". Next, change your PersistKeysToRedis invocation in ConfigureServices to PersistKeysToStackExchangeRedis. No further changes should be necessary.
SignalR
We are releasing a new package "Microsoft.AspNetCore.SignalR.StackExchangeRedis" which will depend on StackExchange.Redis 2.0. "Microsoft.AspNetCore.SignalR.Redis" will continue to ship in ASP.NET Core 2.2 with the StackExchange.Redis 1.0 dependency and will be removed in 3.0.
To use the new package, remove your dependency on Microsoft.AspNetCore.SignalR.Redis (if present), and add a dependency to "Microsoft.AspNetCore.SignalR.StackExchangeRedis". Next, change your AddRedis invocation in ConfigureServices to AddStackExchangeRedis. No further changes should be necessary.

when is this package going to be released ? Microsoft.Extensions.Caching.StackExchangeRedis
i dont see it at nuget.org

Soon. https://github.com/aspnet/Announcements/issues/307

Good changes

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Update package.json

missing dependencies

for me it was also missing "jest": "^29.5.0"

These should install with langchain.


Publish snapshots on main builds

Github CI workflow needs to be tweaked to conditionally publish snapshots if built from main

Here's a sketch of a plan

add https://github.com/qoomon/gradle-git-versioning-plugin, so the version is controlled by the git tag (if the current commit matches vX.Y.Z, then the version is X.Y.Z, else it's $branchName-SNAPSHOT.
set up the GitHub action to always try and release
because the maven-publish convention plugin is setup to point to Sonatype Snapshot if the version ends with -SNAPSHOT, this will all happen manually.

Then snapshot releasing is automatic, and manual releasing means creating a tag.

@aSemy I think semver calculations, signing keys, etc are working but there's some issue with the gradle setup. Do you have time to have a look?

Ahh the wonders of Gradle. I'll take a look now.

so the tests still work, but publishing does not
build scan of the failing linux jvm publish task https://scans.gradle.com/s/73dqhlc2nhi4s

@Kantis Are you able to run ./gradlew publishAllPublicationsToMavenProjectLocalRepository locally, with the appropriate signing properties set?

Yup.

> Task :ks3-jdk:publishJsPublicationToMavenProjectLocalRepository
[task: :ks3-jdk:publishJsPublicationToMavenProjectLocalRepository] io.ks3:ks3-jdk-js:0.0.1-SNAPSHOT

> Task :ks3-standard:publishJsPublicationToMavenProjectLocalRepository
[task: :ks3-standard:publishJsPublicationToMavenProjectLocalRepository] io.ks3:ks3-standard-js:0.0.1-SNAPSHOT

> Task :ks3-standard:publishJvmPublicationToMavenProjectLocalRepository
[task: :ks3-standard:publishJvmPublicationToMavenProjectLocalRepository] io.ks3:ks3-standard-jvm:0.0.1-SNAPSHOT

> Task :ks3-jdk:publishJvmPublicationToMavenProjectLocalRepository
[task: :ks3-jdk:publishJvmPublicationToMavenProjectLocalRepository] io.ks3:ks3-jdk-jvm:0.0.1-SNAPSHOT

> Task :ks3-standard:publishKotlinMultiplatformPublicationToMavenProjectLocalRepository
[task: :ks3-standard:publishKotlinMultiplatformPublicationToMavenProjectLocalRepository] io.ks3:ks3-standard:0.0.1-SNAPSHOT

> Task :ks3-jdk:publishKotlinMultiplatformPublicationToMavenProjectLocalRepository
[task: :ks3-jdk:publishKotlinMultiplatformPublicationToMavenProjectLocalRepository] io.ks3:ks3-jdk:0.0.1-SNAPSHOT

Possible related to the secrets not being available https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#accessing-secrets
Also I changed the Gradle property for the Sonatype user/pass to just come from a Gradle property, so they need to be set using ORG_PROGJEC_GRADLE_osshrUsername

Publishing main branch snapshots is working now, but only for JVM
https://s01.oss.sonatype.org/content/repositories/snapshots/io/ks3/ks3-standard-jvm/main-SNAPSHOT/

ok, but I would like it to work like with the GHA I added.. Snapshot should be called next-ver-SNAPSHOT, where next-ver is latest tagged version + major if there's a commit with(MAJOR) since that release, or minor if there's a (MINOR) commit, otherwise a patch version bump.

Thought I guess the current setup helps when testing different feature-branches.. 🤔 Still, I think the Major/Minor thing is nice.

Oh sorry, I didn't realise the GHA you added was doing that. I thought it was just extracting the most recent tag version.
Some amount of logic is possible with the git-versioning plugin, but maybe not to that extent...
It is possible to tell it to fetch the previous git tag on the branch, and suffix that with -SNAPSHOT.

I think it published main-SNAPSHOT because there's no tag. If there's a tag, e.g. v0.0.1, then the published version = would be 0.0.1-SNAPSHOT

Looks like main-SNAPSHOT went out even when latest commit was tagged :/

Maybe this fixes that https://github.com/Kantis/ks3/commit/58e1f191d37755486b2353b7428c55dfc042544a

Hmm, no luck https://github.com/Kantis/ks3/actions/runs/3324493107/jobs/5496116866#step:6:929

Got a couple of failures now on Sonatype
typeId | sources-staging
-- | --
failureMessage | Missing: no main jar artifact found in folder '/io/ks3/ks3-standard-jvm/0.0.1'

typeId | javadoc-staging
-- | --
failureMessage | Missing: no main jar artifact found in folder '/io/ks3/ks3-standard-jvm/0.0.1'

typeId | signature-staging
-- | --
failureMessage | Missing Signature: '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1.jar.asc' does not exist for 'ks3-jdk-0.0.1.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1-kotlin-tooling-metadata.json.asc'  does not exist for 'ks3-jdk-0.0.1-kotlin-tooling-metadata.json'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1.module.asc' does not exist for 'ks3-jdk-0.0.1.module'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1-sources.jar.asc' does not exist for 'ks3-jdk-0.0.1-sources.jar'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1.pom.asc' does not exist for 'ks3-jdk-0.0.1.pom'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk/0.0.1/ks3-jdk-0.0.1-javadoc.jar.asc' does not exist for 'ks3-jdk-0.0.1-javadoc.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1-sources.jar.asc' does not  exist for 'ks3-standard-0.0.1-sources.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1-kotlin-tooling-metadata.json.asc'  does not exist for 'ks3-standard-0.0.1-kotlin-tooling-metadata.json'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1-javadoc.jar.asc' does not  exist for 'ks3-standard-0.0.1-javadoc.jar'.
failureMessage | Missing Signature: '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1.pom.asc' does not exist for 'ks3-standard-0.0.1.pom'.
failureMessage | Missing Signature: '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1.module.asc' does not exist for 'ks3-standard-0.0.1.module'.
failureMessage | Missing Signature: '/io/ks3/ks3-standard/0.0.1/ks3-standard-0.0.1.jar.asc' does not exist for 'ks3-standard-0.0.1.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-jdk-jvm/0.0.1/ks3-jdk-jvm-0.0.1-javadoc.jar.asc' does not  exist for 'ks3-jdk-jvm-0.0.1-javadoc.jar'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk-jvm/0.0.1/ks3-jdk-jvm-0.0.1.module.asc' does not exist for 'ks3-jdk-jvm-0.0.1.module'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk-jvm/0.0.1/ks3-jdk-jvm-0.0.1.pom.asc' does not exist for 'ks3-jdk-jvm-0.0.1.pom'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-jdk-jvm/0.0.1/ks3-jdk-jvm-0.0.1-sources.jar.asc' does not  exist for 'ks3-jdk-jvm-0.0.1-sources.jar'.
failureMessage | Missing Signature: '/io/ks3/ks3-jdk-jvm/0.0.1/ks3-jdk-jvm-0.0.1.jar.asc' does not exist for 'ks3-jdk-jvm-0.0.1.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard-jvm/0.0.1/ks3-standard-jvm-0.0.1.module.asc' does  not exist for 'ks3-standard-jvm-0.0.1.module'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard-jvm/0.0.1/ks3-standard-jvm-0.0.1.pom.asc' does not  exist for 'ks3-standard-jvm-0.0.1.pom'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard-jvm/0.0.1/ks3-standard-jvm-0.0.1-sources.jar.asc'  does not exist for 'ks3-standard-jvm-0.0.1-sources.jar'.
failureMessage | Missing  Signature:  '/io/ks3/ks3-standard-jvm/0.0.1/ks3-standard-jvm-0.0.1-javadoc.jar.asc'  does not exist for 'ks3-standard-jvm-0.0.1-javadoc.jar'.

Arrow has a lot of stuff for publishing multiplatform things, if we need more sources of inspiration. https://github.com/arrow-kt/arrow-gradle-config/tree/main/arrow-gradle-config-publish/src/main/kotlin/internal

I've asked if it's possible here https://github.com/qoomon/gradle-git-versioning-plugin/issues/104

Got a couple of failures now on Sonatype

this might be because Sonatype doesn't like parallel uploads - I've disabled it for now. But it could be because the Gradle signing plugin is really old and doesn't work properly.

It looks like there's no signing tasks registered when the publishing is configured. This breakpoint is never hit.

I'll just get ks3 set up on my machine that has the signing credentials, and I'll test the signing locally to see what's up.
With regards to the automatic versioning, the git-versioning-plugin doesn't work how I expect, and I don't think it's possible to tag a commit (e.g. v1.2.3), and then make another commit which will have a version of 1.2.4-SNAPSHOT - it will always be main-SNAPSHOT (or 1.2.3-SNAPSHOT, but that doesn't really make sense). Maybe it's best to restore the GitHub Action that I removed. I'm not sure.

Nice, thanks.
I've also been thinking that the GHA might be the simplest way forward, but wanted to give you some space to experiment. It's definitely not urgent, but would be nice to get proper snapshot names at some point

I think that Sonatype just doesn't show jars...? It's really weird. It's also not showing the .asc signature files.
It's the same for some of the Kotest snapshot dependencies too? I'm very confused https://s01.oss.sonatype.org/#nexus-search;gav~io.kotest~kotest-framework-datatest-jvm~~~~kw,versionexpand


Setup of Neural Search Plugin

Description
The task involves the setting up of the Neural Search plugin for development.
Tasks:

[x] Setup the code for the repo
[x] Update the Description of the repo
[ ] Setup the Developer guide
[x] Add the merge policy like: Don't merge the code without approval, 2 person approval.
[x] Setup the labels.
[x] Setup the 2.x branches
[x] Add update version task
[x] Show Jacoco reports when Pull request is created
[x] Run CI checks periodically
[x] Add the badges to Readme.

I'm pretty sure that's done, closing


Package's ".x" is not reproducible between dependency upgrade

This is a tracking issue for https://github.com/golang/go/issues/69547
I was upgrading our external dependencies recently and these 2 GoCompilePkg actions ran on the same package between 2 consecutive commits.

https://app.buildbuddy.io/invocation/a21c41a4-d2d3-49b5-9fa2-928cb7043d1e?actionDigest=4006f4946e2d116787a3e26a3e2a677611942994ce2992e24cca9741de1f5e5f#action
https://app.buildbuddy.io/invocation/0bd82434-6213-466b-aa76-e3c68250c92a?actionDigest=bfe3f607ffd5015d1eb076045805c1d074ef71c1454a84c583df589ab1e05f31#action

Specifically, the package is server/util/db with a single source file db.go. The upgraded dependency was gorm.io/driver/{mysql,clickhouse,sqlite}. There was no code change in db.go.
The expectation is for db.x output to stay the same between the 2 compilations as no exported data was change. However, we observed that there were some bytes differences between the 2 .x files, which caused downstream compile actions to all rebuild.
~> diffoscope db{1,2}.x
--- db1.x
+++ db2.x
│┄ Command `'nm -s {}'` failed with exit code 1. Standard output:
│┄     /Library/Developer/CommandLineTools/usr/bin/nm: error: for the -s option: bad number of arguments (must be two arguments)
│┄     /Library/Developer/CommandLineTools/usr/bin/nm: error: a.out: No such file or directory
@@ -34357,15 +34357,15 @@
 00086340: 0104 0203 0405 1000 8108 0082 0803 7b03  ..............{.
 00086350: 4303 0103 0203 4103 8001 0324 034a 031b  C..... Consulting upstream Go team for more information on the 7-bytes diff.

@sluongng I discovered something related - it appears that the .x archive is not reproducible even if the interface of the package is constant.
The .x file should not change if I modify this file to return false instead of true.
package mypkg

func TestFunc() bool {
	return true
}

I do not think we are getting much/any benefit from separating the .a from the .x, as intended by https://github.com/bazelbuild/rules_go/pull/2461

@joeljeske Does this reproduce if you make the implementation more complicated? I wouldn't be surprised if the export data ensures that this function is inlined into every caller.

Yes, the x archive still changes even when the implementation is more complex. Here is a draft PR with a script to show the issue. https://github.com/bazel-contrib/rules_go/pull/4143
Does rules_go have any test case that asserts on this functionality? I'm not certain if this is a result of the rules_go implementation of extracting the pkgdef information, or something in golang native that is causing the instability.
In any case, I think this performance feature may not be working as intended, and there are potentially huge gains to be had 😄

Also, should I move this to a new issue, as its not exactly the same issue as @sluongng? But it does feel very related.

Yeah, I think you are observing the effect described in https://github.com/golang/go/issues/69547. IIUC, the Go team responds that .x not being stable is "fair" game. You can follow up in that thread or via Gophers' Slack #compilers channel.

I do not think we are getting much/any benefit from separating the .a from the .x

In a remote build setup, separating the 2 reduces the input size of GoCompilePkg actions significantly. .x is smaller and can be compressed with Zstd much better than the binary .a. So there is a benefit that our cache is more fine-grained and our actions are slimmer.
I do think though, that ultimately, a fix in upstream Go tooling would be very much desirable. If the exported "interface" in a package was not changed, the '.x' output should be stable. I did not find the time to create a follow-up with the Go team on this issue though. It would be nice if someone else could help with this.

I think there is more missing reproducibility. I've built the same target on two machines configured the same way and got different .x files, while .a files were the same.
When inspecting with diffoscope following the example above, I've observed that constants (both private and public) are included in different (random?) order. I traced two differences to validation types and cardinality. There were also other differences that looked like ordering as well, but not for constants and not as easy to trace.
005da4b0: 6564 0133 084f 7074 696f 6e61 6c01 3108  ed.3.Optional.1.
│ -005da4c0: 5265 7175 6972 6564 0132 0103 0131 0108  Required.2...1..
│ -005da4d0: 4f70 7469 6f6e 616c 0132 0108 5265 7175  Optional.2..Requ
│ -005da4e0: 6972 6564 0133 0108 5265 7065 6174 6564  ired.3..Repeated
│ +005da4c0: 5265 7175 6972 6564 0132 0103 0132 0108  Required.2...2..
│ +005da4d0: 5265 7175 6972 6564 0133 0108 5265 7065  Required.3..Repe
│ +005da4e0: 6174 6564 0131 0108 4f70 7469 6f6e 616c  ated.1..Optional
│  005da4f0: 0000 0001 2f67 6f6f 676c 652e 676f 6c61  ..../google.gola
│  005da500: 6e67 2e6f 7267 2f70 726f 746f 6275 662f  ng.org/protobuf/
│  005da510: 7265 666c 6563 742f 7072 6f74 6f72 6566  reflect/protoref
│  005da520: 6c65 6374 010e 4361 7264 696e 616c 6974  lect..Cardinalit

@annapst Could you file an issue with upstream for this? That's a pretty clean diff and the existing explanations for why there may be a difference don't apply.

with a setup like this
~/work/misc/test-go> cat importcfg
# import config
~/work/misc/test-go> cat temp.go
package lib

type mytype int

const (
    validationTypeOther mytype = iota
    validationTypeMessage
    validationTypeGroup
    validationTypeMap
    validationTypeRepeatedVarint
    validationTypeRepeatedFixed32
    validationTypeRepeatedFixed64
    validationTypeVarint
    validationTypeFixed32
    validationTypeFixed64
    validationTypeBytes
    validationTypeUTF8String
    validationTypeMessageSetItem
)
~/work/misc/test-go> cat go.mod
module github.com/foo/lib

go 1.23

I could not reproduce
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a
~/work/misc/test-go> go tool compile -o lib.x -linkobj lib.a -p github.com/foo/lib -complete -goversion go1.23.2 -c=4 -shared -nolocalimports -importcfg importcfg -pack ./temp.go && sha256sum lib.x && sha256sum lib.a && rm -f lib*
6d9a7e512c9db5b9ffbc5cfe74bf413fa0bf730fe2cd3a6b68f80154ca8b5652  lib.x
5bd6d2693bfd2176e119ed4ecbf74175ce39f9e827588f77ca35aeabef69ed52  lib.a

It would be nice to get a small reproduction from your end @annapst
And yeah, if it can be reproduced, the issue would need to be filed upstream to Go's compiler team

I also didn't reproduce it starting from a small example. After digging into differences between our repository build and a simple go example, I found that the difference in ".x" files on the same commit appears only when I run builds with nogo, so I'm not sure if this is go compiler problem or not. I'll be going after upgrading rules_go to latest and checking if that's still the case, I see nogo got separated into a separate action, will share an update then!

I'm actually able to reproduce this in rules_go's own tests now and will investigate further.


[Touches] Let only the nearest ancestor root view process touches

This is to support nested root views with independent bridges by preventing touches in the inner root view from being handled by the outer one.
Previously, touches were handled by both touch handlers. This was problematic because the outer touch handler would dispatch a JS touch event to the outer bridge with a react tag from the inner root's descendant view. So if you touched view 7 in the inner root view, then view 7 in the outer root view would also receive a touch event. Instead, we want touches in the inner root view to stay in the inner root view.
Performance-wise, I profiled this diff and didn't see an impact. On the start of each touch (when the finger goes down, not when it is dragged), the view hierarchy is traversed upwards until the first root view which is on the order of 10 property lookups for a typical view hierarchy.
Test Plan: Tapped around in an inner root view and saw that components in the outer root view like text fields, etc were no longer receiving mystery touches.

@tadeuzagallo, @nicklockwood: what do you think about this?

What's the use case for nested root views?

(Not that I need to know that in order to approve the PR - which seems reasonable to me).

This is for the Exponent component that renders a React Native bundle inside of another React Native app ^_^

Any updates on this?

What should we do with this? @ide @nicklockwood

ping!

cc: @majak, who has a better understanding of touch handling than I do.

I believe this works.
I see this as a subset of a larger problem, which is embedding RN root view in any other view, where the outer view can have its own gesture recognizers. Imagine RN rootviews in a native UIScrollView. When you touch down on the embedded RN and drag, the RN should get its touches cancelled.
So I'm thinking about a bit more generic solution, which would expose RCTTouchHandler as a property on the rootView, so anyone could set up dependency between RN and native GR as needed.
(There is some risk in this approach, since it requires a change in what states our RCTTouchHandler GR goes through, and I'm not entirely sure if there are any hidden implication of doing that yet.)
I'm hesitant to merge this fix. The main reason being is it's not unreasonable to think you could want to do the opposite thing - make the embedded RN not receive any touches, and we already internally have have the UIScrollView embed need.
@ide let me know what are you thoughts.

@majak thanks for your analysis. I agree that this diff is too inflexible and it would be much better if the RN RootView provided a way for its superview to customize how touches within the RN RootView are handled.
In our use case, we want to let a touch inside of a RootView get sent to the deepest subview that was directly touched (like the normal touch-handling behavior), and allow the touch to bubble up the view hierarchy.
The superview of the RootView wants to intercept and create a copy of the touch with some properties changed, and let the new touch bubble up.

This is interesting. Just to double check, you want the inner root view to handle the touch, but at the same time the outer one should get some transformed touch as well? (No matter if the inner root view actually did anything with the touch.)

@majak Yes, exactly.

@ide This diff would be a part of the solution for your case?
Also I'm curious what the transformation would look like if you can say.

I think this diff would not be part of the solution since we want the touch to bubble up past the inner root view, but allow its superview to intercept the touch.
The transformation of the UITouch would be just to change its view property. In our case we want the new value of touch.view to be the superview of the inner root view.

So currently even the outer root view get touches with view property set to a view from the inner root view? (If yes) That sounds wrong, since the embedded one should be treated like an opaque view by the outer one.
My guess is this is happening because of this:
https://github.com/facebook/react-native/blob/2e8eb652e10ba5d5419f277a98294faff4e46f56/React/Base/RCTTouchHandler.m#L82-L90
I think you could try modify that logic to do continue climbing up the view hierarchy up even in case we found a react view, but its root view is not the same as the one the GR was set up on.

@tadeuzagallo would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

@ide Do you plan to continue working on this? Any opinions on the comment by majak?

@mkonicek yep, I plan to look into this more eventually. Probably not super soon but I would like to build a solution!

OK sounds good! :)

Just going through all old PRs. Based on the comments above leaving this one open.

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @javache as a potential reviewer. Could you take a look please or cc someone with more context?

I support the great cause of this pull request, but at this point it is kind of just a symbol of intending to do something about this that has just been a symbol for months. I think we should close it. If you want to start working on it again then that would be awesome! - and then I think just opening a new PR would be appropriate.


[FLINK-18810][sdk] Golang remote functions SDK

Implements a remote Golang SDK for stateful functions.
Important To Reviewers
cell.go is a bit tricky because it requires both resumable reads, as well as the ability to restart from the beginning. This is the component that was causing issues in testing so please take an extra close look.
Licensing
The SDK has two dependencies which are both BSD-3 licensed. Golang libraries do not have binary releases, only source releases, so my understanding is that we do not require a NOTICE file but please correct me if I am wrong.
Releasing
The Go SDK is implicitly released when the release branch is tagged[1]. It does require the tag to be exactly the format vMAJOR.MINOR.PATCH, which is different than our current tagging model. We can discuss whether to add both tags or switch our tagging model during the release.
[1] https://blog.golang.org/publishing-go-modules

@sjwiesman We wont release any Go binaries, but the Go SDK source will be part of the source tarball release. Are the BSD-3 licensed dependencies bundled in the SDK source? If so, we need to acknowledge that here: https://github.com/apache/flink-statefun/blob/master/NOTICE. This is the NOTICE file that gets bundled with the source release.

@igalshilman thanks for your help reviewing! Thrilled to finally get this merged in :)


Sending data to a restarted peer will not return an error

Hello,
Why does the client continue to send data to the old connection without returning an error after the server restarts, and must wait until the idle timeout before returning an error？

You might interested in reading https://datatracker.ietf.org/doc/html/rfc9000#section-10.3.


Added back to home link in sidebar

Added the back to home link in the sidebar

Deployed to: http://staging.quran.com:32813

Deployed to: http://staging.quran.com:32814


Error in batch_size in PointPillarScatter

Hello,
I am trying to train a pointpillar model on custom datasets of point clouds. I'm facing an error in forward function of PointPillarScatter class (In pcdet/models/backbones_2d/map_to_bev/pointpillar_scatter.py).
batch_size is defined as batch_size = coords[:, 0].max().int().item() + 1 instead of batch_size = batch_dict['batch_size'].
Therefore every few iterationsbatch_dict['spatial_features'] is of shape torch.Size([3, 64, 214272]) instead of torch.Size([4, 64, 214272])
This results in an error when computing loss:
 File "/home/ganoufa/workSpace/deep_learning/lidar_detection/OpenPCDet/tools/../pcdet/utils/loss_utils.py", line 60, in forward     pt = target * (1.0 - pred_sigmoid) + (1.0 - target) * pred_sigmoid RuntimeError: The size of tensor a (4) must match the size of tensor b (3) at non-singleton dimension 0
What can be the cause of coords[:, 0].max().int().item() + 1 not being equal to the actual batch_size ?

I am also unable to use other models. I get different error messages that are probably linked with the first issue :
For pv_rcnn : in VoxelBackBone8x forward function
I get an error during convolutions
tensor shapes:
x_conv1:  [2, 248, 216]
x_conv2:  [1, 124, 108]
x_conv3:  [1, 62, 54]

x_conv4 computation results in an error

[Exception|implicit_gemm_pair]indices=torch.Size([2557, 4]),bs=2,ss=[1, 62, 54],algo=ConvAlgo.MaskImplicitGemm,ksize=[3, 3, 3],stride=[2, 2, 2],padding=[0, 1, 1],dilation=[1, 1, 1],subm=False,transpose=False
  File "/home/ganoufa/workSpace/deep_learning/lidar_detection/OpenPCDet/tools/../pcdet/models/detectors/pv_rcnn.py", line 11, in forward
    batch_dict = cur_module(batch_dict)
  File "/home/ganoufa/workSpace/deep_learning/AnomalyDetection/myenv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/ganoufa/workSpace/deep_learning/lidar_detection/OpenPCDet/tools/../pcdet/models/backbones_3d/spconv_backbone.py", line 157, in forward
    x_conv4 = self.conv4(x_conv3)

[.........]
  File "/home/ganoufa/workSpace/deep_learning/AnomalyDetection/myenv/lib/python3.8/site-packages/spconv/pytorch/conv.py", line 381, in forward
    res = ops.get_indice_pairs_implicit_gemm(
  File "/home/ganoufa/workSpace/deep_learning/AnomalyDetection/myenv/lib/python3.8/site-packages/spconv/pytorch/ops.py", line 280, in get_indice_pairs_implicit_gemm
    raise ValueError(
ValueError: your out spatial shape [0, 31, 27] reach zero!!! input shape: [1, 62, 54]

For pointrcnn it is another error:
 File "/home/ganoufa/workSpace/deep_learning/lidar_detection/OpenPCDet/tools/../pcdet/models/backbones_3d/pointnet2_backbone.py", line 76, in forward     assert xyz_batch_cnt.min() == xyz_batch_cnt.max() AssertionError

Anyone figure this out? I'm having the same issue

Try playing with the voxel size. It dictates the gird size and it is not big enough for the different downsamples happening in different layers!

any progress on this issue?

I just found that if the .bin file had no data, then the error might occur


angular-ui/ui-tinymce setup method in tinymceOptions breaks model binding

I want to add a custom button to the tinymce toolbar, and added a setup function to tinymceOptions as discribed in the docs:
$scope.tinymceOptions = {
setup: function (editor) {
editor.addButton('myMethod', { //myCode }
},
//more options
}

Adding the setup function breaks the binding with the model. Content added to the editor is not synced to the model and vice-versa.
Are there known issues with this approach? If so, what would be the other way to add custom buttons, without breaking binding?
Tnx;

this doesn't work for me. the attrs object isn't defined. if I remove the mode and elements items, the editor doesn't load.

this doesn't work for me. the attrs object isn't defined. if I remove the mode and elements items, the editor doesn't load.

If you do not need to handle events that occur before the 'init' event, then until the issue with setup is resolved, you could use init_instance_callback instead.
So replace
{
   // ...
   setup: function (ed) {
       ed
         .on('init', function () { alert('init!'); })
         .on('blur', function () { alert('blurred!'); });
   }
}

with
{
   // ...
   init_instance_callback: function (ed) {
       alert('init!');
       ed.on('blur', function () { alert('blurred!'); });
   }
}

This seems to work for now:
inside tinymce.js
if (expression.custom_setup) {
    scope.$eval(function () {
          expression.custom_setup(ed)
     });
     delete expression.custom_setup;
}

inside your_code.js

$scope.tinymceOptions = {
//...
custom_setup: function(editor) { /* setup */ }
}

Can confirm this is an issue for me as well.

This was resolved with ae37bb9dd9e1094b5a2379bb4a63e35209f14622, however the tagging is currently messed up and version 0.0.5 does not currently resolve to the correct version 0.0.5 tag.
Recommendation is to download the .zip of the real v.0.0.5 and use that in the interim.
https://github.com/angular-ui/ui-tinymce/archive/v0.0.5.zip

Ok @thatguyyoulove it cool, but why there is no new tag 0.0.6 tag ?
This issue is important !

Comment on #127 to get support for having it fixed please.

I believe this is now fixed - I have removed the broken 0.0.5 tag and released 0.0.6.
I do however think that the api is a little awkward for extending the setup function - I am open to any ideas on a better way to extend the logic in the existing callbacks, in the event the user wants custom behavior to happen, if it is desired. If anyone is interested, feel free to open a new issue on this.

It still happens. Using the    init_instance_callback as @helmutkian  suggested does not work if you are adding a new button . It works for the context menu surprisingly..

Just FYI - i solved the issue of not being able to add the button via creating a new plugin - and injecting that in the tinymce options. I also passed the $rootScope, $scope and other angular requirements to the plugin via this.PluginManager.$rootScope = $rootScope from within the init_instance_callback function in the $scope.tinymceOptions in the controller.

Take the @mangreen code, It fixed couple of issues for me.

Allows me to add custom button.
When inline=true two way binding not works without this fix for me.

Not only in this case. In my approach I need to do stuff in the init. And I can't setup this because the entire model binding is lost (setup function extends over the original one in the directive).

Will a new version be put out with the fix by @mangreen?

Since updating to the latest version of Tiny I had to do the following to get my angular buttons to work:
$scope.tinymceOptions = {
       external_plugins: { "custom-button": "/scripts/libraries/ui-tiny/plugin.js" }
       init_instance_callback: function (ed) {
      ed.$scope = $scope;
      },
       toolbar: "custom-plugin"
 }
In the plugin.js folder it was just a normal ed.addButton function.


fix text layouting

This came up when trying to build tables out of Labels. The alignment looked bad, which seems to be because of incorrect assumptions about glyph boundingboxes. So far, the width of a line was computed using the "ink-width" of the glyphs, but this leads to a ragged appearance when right-aligning. Also, the left origin of a line was incorrectly adjusted for bearing, which is not necessary at all, as the bearing is chosen to make the glyph look well-adjusted when left aligned.
Some test code:
f = Figure(fontsize = 30, font = "Helvetica")

words = ["Apple", "Pear", "Cherry", "Coconut", "Pineapple", "Grapes"]

for (i, word) in enumerate(words)
    Label(f[i, 1], word, halign = :left)
    Label(f[i, 2], string(i), halign = :right)
end

rowgap!(f.layout, 10)

f

Before
After

Cool! I guess the test failures are all expected... But I guess the Glyph Collections error in the unit tests still needs fixing ;)

Ok the unit test is fixed. I'm not sure how to proceed given that height_insensitive_boundingbox_with_advance is just a Makie function now, while height_insensitive_boundingbox lives in FreeTypeAbstraction as if it's somehow more basic. This was more about me learning along the way how all these glyph metrics and boundingboxes work. I'm still not 100% sure what the canonical behavior should be, but it seems that taking the full hadvance into account makes some things easier and appears to be more closely to how a browser behaves when selecting text, for example.

Compile Times benchmark


Enable building uProxy as a Cordova Chrome App for Android

Currently the getter functionality is present but nonfunctional,
so the app is titled "uProxy for Sharers".  The Google social network
is also not working, possibly due to STARTTLS issues in the TCP
socket API bindings.
This is the first part of a solution to https://github.com/uProxy/uproxy/issues/586

Looks good! Few small things.

Reviewed 8 of 9 files at r1.
Review status: 7 of 9 files reviewed at latest revision, 4 unresolved discussions, all commit checks successful.

src/cca/app/scripts/cordova_browser_api.ts, line 57 [r1] (raw file):
This comment can probably be removed (made more sense in Chrome where I had a lot more helpers in different categories).

src/cca/app/scripts/cordova_browser_api.ts, line 83 [r1] (raw file):
Quick note following our chat offline: if we were to assume that tapping the mobile app icon mimics a desktop browserAction (clicking the ext icon), then this code would not work in the case where the user has a uProxy (mobile) window open but out of focus.

src/cca/app/scripts/cordova_core_connector.ts, line 23 [r1] (raw file):
We don't need this anymore, if you could take it out. Thanks!

src/cca/app/scripts/cordova_core_connector.ts, line 64 [r1] (raw file):
So I understand, does your making uProxyAppChannel a promise get rid of the need for flushQueue?

Comments from the review on Reviewable.io

Review status: 6 of 10 files reviewed at latest revision, 4 unresolved discussions, some commit checks pending.

src/cca/app/scripts/cordova_browser_api.ts, line 57 [r1] (raw file):
Done.

src/cca/app/scripts/cordova_browser_api.ts, line 83 [r1] (raw file):
True.  I've attempted to clarify this code a little.

src/cca/app/scripts/cordova_core_connector.ts, line 22 [r1] (raw file):
Done.

src/cca/app/scripts/cordova_core_connector.ts, line 62 [r1] (raw file):
Sort of.  It means that messages will automatically be queued until the uProxyAppChannel is ready.  It's also important that the channel will never go away once it's present.

Comments from the review on Reviewable.io

Review status: 6 of 10 files reviewed at latest revision, 6 unresolved discussions, all commit checks successful.

Gruntfile.coffee, line 83 [r2] (raw file):
Why do we need to copy cca twice?

Gruntfile.coffee, line 624 [r2] (raw file):
We have icons, and _locales copied twice.

Comments from the review on Reviewable.io

Review status: 6 of 10 files reviewed at latest revision, 6 unresolved discussions, some commit checks pending.

Gruntfile.coffee, line 83 [r2] (raw file):
Removed!

Gruntfile.coffee, line 624 [r2] (raw file):
Fixed!

Comments from the review on Reviewable.io

last thing then :+1: !

Review status: 6 of 10 files reviewed at latest revision, 7 unresolved discussions, all commit checks successful.

Gruntfile.coffee, line 585 [r3] (raw file):
!**/spec also duplicated below

Comments from the review on Reviewable.io

Review status: 6 of 10 files reviewed at latest revision, 6 unresolved discussions, some commit checks pending.

Gruntfile.coffee, line 585 [r3] (raw file):
Removed

Comments from the review on Reviewable.io


Fix mainContentObserver adding links to modals

Fixes small bug where the MutationObserver would add wiki links to the pop-up modal when trying to save a snippet to your journal.
Also took the liberty of updating the README (removing implemented features from TODO; removing unessential  trailing whitespaces; and adding more visible links to other installation sources) and bumping the version number.
If you'd rather drop any of those commits, or if you want them in a separate PR, please let me know

Just cleaning up my branch, apologies if you got pinged a bunch


[CELEBORN-1061] Fix the bug if celeborn.client.spark.shuffle.writer is sort and celeborn.client.spark.push.sort.pipeline.enabled is false

What changes were proposed in this pull request?
SparkShuffleManager may throws NullPointerException if celeborn.client.spark.shuffle.writer is sort and celeborn.client.spark.push.sort.pipeline.enabled is false.
Why are the changes needed?
Currently, if celeborn.client.spark.shuffle.writer is sort and celeborn.client.spark.push.sort.pipeline.enabled is false, the SparkShuffleManager.asyncPushers will be null. When calling SparkShuffleManager. getWriter , the null pusher thread used to construct SortBasedShuffleWriter. SortBasedPusher.triggerPush causes NullPointerException.
Does this PR introduce any user-facing change?
Yes.
Fix a bug.
How was this patch tested?
Exists test cases.

spark-2 module need to change too?

There was an unrecoverable design issue identified when celeborn.client.spark.push.sort.pipeline.enabled is true, actually, the community decided to delete this feature in the next release.

There was an unresolvable design issue identified when celeborn.client.spark.push.sort.pipeline.enabled is true, actually, the community decided to delete this feature in the next release.

Do we need to solve this problem first?

@beliefer I think we can minimize the change and port this patch to branch-0.3 too. then delete the related code on the main branch

@AngersZhuuuu @pan3793 It's my fatal.
SortBasedShuffleWriter checked celeborn.client.spark.push.sort.pipeline.enabled again, please see:
https://github.com/apache/incubator-celeborn/blob/2758df713ead7fd78fdee9f8a2af2ad2ce377fa9/client-spark/spark-2/src/main/java/org/apache/spark/shuffle/celeborn/SortBasedShuffleWriter.java#L130


Diagnostics Source events for View Components

Originally we had intended to show child actions. View Components are the successor to what child actions where intended to do and we would like to have Diagnostics Source events for the "action"/component resolution and corresponding view resolution.
// @rynowak @Eilon

Would love to see more detail about what this would look like and what kinds of things you expect users to troubleshoot/understand with this experience.

As demonstrated by the various View Components in MusicStore, I think it is imagined that a good percentage of users will be doing some sort of out-of-proc work in these (probably mainly db stuff) and because of that it makes sense to show them what is causing that work to occur and what the result it. Hence shoring which View Component have executed, what happened within them and what resulted is really useful. Given this, we would like a before/after for the View Component itself and then for the "view" that results from that. Does that make sense/help?


The information about requirement of .NET Core 7.0 SDK and runtime is not valid anymore

In the page of this: https://microsoftlearning.github.io/mslearn-ai-services/Instructions/setup.html
It says about needs .NET 7.0 SDK installed:

This is problematic because as of today, 28th May 2024, .NET 7.0 is out of support:
(source: https://dotnet.microsoft.com/en-us/download/dotnet)

Could the setup.md and the actual lab instruction be updated to at least use .NET 8.0, the STS version?

The hosted labs are tested and verified against that environment, which is still on 7.0. Updating this is a bigger ask than just changing the setup file - I'll add notes in there about it for clarity, and have it on the backlog to update the .NET version on the VMs and test the code.


ImportError: libcudart.so.7.5: cannot open shared object file: No such file or directory

I'm a new user of tensorflow.I install tensorflow like this.
1.export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow-0.10.0-cp27-none-linux_x86_64.whl
2.sudo pip install --upgrade $TF_BINARY_URL
and I succeed install tensorflow ,when I import tensorflow ,It happens that "ImportError: libcudart.so.7.5: cannot open shared object file: No such file or directory".It's crazy,I find some solution ,that my shell environment variables should do like this:
1.export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64"
2.export CUDA_HOME=/usr/local/cuda
but it not works.
I find there is not libcudart.so.7.5 in "/usr/local/cuda/lib64",it's only "libcudart so.8.0"
os:ubuntu 16.04 LTS,cuda:8.0

You need to install CUDA 7.5 rather than CUDA 8.0 which is not yet
supported by pre-built binaries
On Thu, Sep 29, 2016 at 4:58 PM, lxj0276<EMAIL_ADDRESS>wrote:

I'm a new user of tensorflow.I install tensorflow like this.
1.export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/
linux/gpu/tensorflow-0.10.0-cp27-none-linux_x86_64.whl
2.sudo pip install --upgrade $TF_BINARY_URL
and I succeed install tensorflow ,when I import tensorflow ,It happens
that "ImportError: libcudart.so.7.5: cannot open shared object file: No
such file or directory".It's crazy,I find some solution ,that my shell
environment variables should do like this:
1.export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64"
2.export CUDA_HOME=/usr/local/cuda
but it not works.
I find there is not libcudart.so.7.5 in "/usr/local/cuda/lib64",it's only
"libcudart so.8.0"
os:ubuntu 16.04 LTS,cuda:8.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/4664, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHP8DQIGixnv8CEimUzlK8nKPmOazks5qvFC9gaJpZM4KKmkP
.

What @yaroslavvb said.  Feel free to re-open if CUDA 7.5 did not work for you.

If I install cuda7.5 and cuda8.0 at the same time ,they  will not clash?


Getting the same md5 regardless of Blob contents

Not sure what I'm doing wrong here, following the documentation I do something like this:
var img = document.getElementById('image');
var imgBlob = base64ToBlob(getBase64Image(img));

var spark = new SparkMD5.ArrayBuffer();
spark.append(imgBlob);
console.log('md5: ' + spark.end());

No matter which image I use as the test, I always get the md5:
d0ad09ba8fe3801ac437d06ba62740d2
From the filesystem, I get the md5:
$ md5 test_image.png
MD5 (test_image.png) = d1a87269a70cb65ed4a41d272d376052

I've also tried with:
SparkMD5.ArrayBuffer.hash(imgBlob, false);
"d41d8cd98f00b204e9800998ecf8427e"

Which always returns that md5 no matter which test image I use.
The same happens when I use a more complicated example with transferred files (non-images), I get the same md5 sum that I get here with the images.
Any idea what I'm doing wrong here?

Nevermind, this was a user error.


Setup and Test Requirements considered harmful

Currently the setup.py that pyscaffold generates contains these lines:
    setup(setup_requires=['six', 'pyscaffold>=2.4rc1,<2.5a0'] + sphinx,
          tests_require=['pytest_cov', 'pytest'],

usage of setup_requires and tests_require is unfortunately a little problematic. Setuptools/distutils will install the packages listed there into the .eggs directory upon calling python setup.py develop and python setup.py test. Since the introduction of virtualenvs in the python workflows, one is probably more interested to use one virtualenv for developing and building the tool, and another one for running the tool that does not include the dev requirements.

+1 the whole approach seems to be screwed at the moment and we need to find a way to fix it...

To be fair, setup_requires and tests_require are the way that setuptools/distutils are layed out.

Hm... but setup_requires is actually needed for the whole concept of tools like PyScaffold, setuptools_scm and pbr. Can you elaborate some more where the problem is? Is it directly connected to #70 ?

Let's separate two things, for one, what we would like to have, and then what setuptools does and how this differs from what we would like to have in an environment where we use virtualenvs:
What we want: we would like to have a way to specify dependencies that we only need for executing a setup.py and not during runtime.
What setuptools offers: Setup requirements can be specified and are installed in a .eggs directory in the project. They appear as if they were installed and interfere with the state of the virtualenv (or the system python packages if no virtual env is used). In my experience, having packages in .eggs directory is a typical cause for trouble.
Nowadays, we have virtualenvs, so what we want is, to install all packages we need during development into a development virtualenv. We build a wheel for packaging our package up and install it in another, fresh virtualenv that does not pull any setup requirements for running the software. Virtualenvs enable us to not use the .eggs directory.
My workflow involves having a dev_requirements.txt file in the repo that I just install into the environment I am developing in. This means that I have to execute one pip install -r dev_requirements.txt before I can execute the setup.py, but ensures that .eggs will not trouble me.
Example
What kind of trouble is it when packages are installed in a .eggs directory?
% putup asdf
% cd asdf
% pip install -e .
%  % python setup.py test
running test
Searching for pytest
Reading https://pypi.python.org/simple/pytest/
Best match: pytest 2.7.3
[snip]
Installed /............/asdf/.eggs/pytest-2.7.3-py2.7.egg
[snip]
% py.test
pyenv: py.test: command not found

So I will go on and install pytest in my virtualenv. No I have two pytest installations.

@holgerpeters, good explanation. So when everything is already in your virtual environment, it should be no problem. It only causes trouble if setuptools installs software into the egg folder that was not available before. The question is if setuptools allows changing from easy_install to pip. Another option would be to raise an error for at least all packages in setup_requires instead of installing them with the help of setuptools.
I am looking forward to your thoughts on that @holgerpeters and @sebastianneubauer.

After our discussion, several things will be done to avoid this issue. First of all #72 will limit those possible conflicts to PyScaffold itself. Then avoiding test_requires and using an test-requirements.txt file like in #70 should at least limit the number of eggs you'll have if you set up your venv beforehand.


Add Bonus Guide: Installation ThunderHub

I installed ThunderHub on my Raspibolt. The following Guide describes my steps and setup.

and I also updated the SCB part, which already existed. (new pictures and just some small text changes)

Will need to test this more in-depth, unless someone else can attest that everything works.

Oh nice, thank you.
I assume you used the btcexplorer guide as template because there are still some hints in your guide :)
You should correct these before merge.
Additionally you should link the original installation guide from apotdevin.
Some words about security mesures should also not avoided since the original guide dives deep into this topic by configuring quite a few things.

Yes I used btcrpcexplorer as template. Unfortunately I don't know much about the security risks that may come with thunderhub (and with the "wrong" configuration)
I linked the original guide and hopefully I removed all "btcrpcexplorer" parts out of my file.

@real-doman Would you like to open a PR again to include ThunderHub as a new bonus guide? It would be great to add to the +Lightning section of the Bonus Section!
We use a new file naming convention and formatting for v3, happy to help with this if needed.

Don't forget to add an entry on https://raspibolt.org/bonus/lightning/

Don't forget to add an entry on https://raspibolt.org/bonus/lightning/

right, good point. I added thunderhub to the index.md

I share your opinion. The login method as decribed in the guide works for me, but I don't know much about other methods, so I won't change it for now, but I am open for other recommendations.


Typo in example

Very minor typo.
In the example:
Set-ADSyncRestrictedPermissions -ADConnectorAccountDN 'CN=ADConnectorAccount,CN=Users,DC=Contoso,DC=com' -Credential $credential
It should be:
Set-ADSyncRestrictedPermissions -ADConnectorAccountDN 'CN=ADConnectorAccount,OU=Users,DC=Contoso,DC=com' -Credential $credential

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

ID: 5eab5899-ad7d-2071-6d43-50e7de4a304b
Version Independent ID: ab3eeda6-a534-af65-9fff-604fec3a0b65
Content: Azure AD Connect: Configure AD DS Connector Account Permissions - Microsoft Entra
Content Source: articles/active-directory/hybrid/how-to-connect-configure-ad-ds-connector-account.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@mav147
Thanks for your feedback! We will investigate and update as appropriate.

@mav147
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


don't automatically generate shell scripts

e.g. obi-clean-localhost.sh
I suggest a new command whose purpose is to create them.

A "dry run" option for those obi commands might suffice too (just redirect to a file to make the script).


Invalid Version Warning: Semantic version mismatch

The screenshot says it all, but for those arriving here by search terms:
"Using latest version of Electron"
"Your application is using version 1.6.3 and the latest version released is 1.3.14"

Hi,
the problem is actual not solved. Here you see the latest version is 1.6.11. But Devtron say the latest is 1.7.4.

For the devtron team... it might be enough to just change the wording on this so it says something like "Using latest Stable Electron version"


Fix tests

Looks like I'm having a bit more trouble than I expected - lots of the tests are broken although I can't reproduce myself.

@justinmk this is where my lack of experience shows - is there a better way to do 025b7e0 (#890) ?


LogReporter for unmangled TypeScript compiler output

Would it be possible to add a logReporter that outputs the TypeScript compiler output untouched?  Currently, the "error|warn" is missing and it changes a TS code from TSXXXX to XXXX.  This causes Visual Studio Code to no longer parse the output correctly to surface the errors in the editor.  I imagine this is impacting other editors/plugins that also parse the output.

Thanks for reporting. I was already thinking about changing the default reporter, so I've done that. The longReporter can also be used with VS Code if I'm not mistaken.

Thanks for the quick fix!  FYI, longReporter is not working for me in VSCode 0.1.0 (only released version) on gulp-typescript 2.7.3


External MSVC compilers 404s in staging/beta

OK! This is a beta- and staging- only issue! It's the prefix we pass, so we're trying to call "godbolt.ms/staging/api/compile/..."
Having trouble replicating locally right now, but sure enough of this to not let this block release of execution

Confirmed locally. One to fix, but not high priority right now!

The non-WINE MSVC installs seem to have disappeared entirely.  Is this related?  (I don't know where to look for news / announcements about installed-compiler changes, maybe this is already known.)

https://godbolt.ms was down and it caused some problems on the main site. We had to disable those compilers provided by Microsoft in order to fix said problems. We'll reactivate them as soon as we can confirm that everything's good.
Sorry for the incoveniences this might have caused :)

www.godbolt.ms is back up: will update the site to get them in later

@pcordes : The live site was restarted with MSVC compilers enabled last night. Sorry for the lack of information; I should have used a site notification. If you use twitter at all, we post short informational updates on https://twitter.com/CompileExplore but I appreciate that Twitter is not to everyone's taste.

No worries, thanks Matt.
I noticed that www.godbolt.ms lets you make shortlinks, but they're instantly dead.  Fortunately I still had the relevant code in a SO answer I was editing.
I don't do Twitter.  Checking email is enough of a burden (and I don't even do that regularly).  I just like computers more than using them to talk to people :P  But for some reason I like Stack Overflow, probably because of the notion of creating permanently-useful content, rather than ephemeral chatter.

Interesting re: www.godbolt.ms short links: I'm not directly responsible for that site so I can't do anything about it: I'd recommend you use godbolt.org and rely on its link service (or long URLs). But I'll raise it with MS :)
Thanks for your message; and even more so thank you for being such an amazing SO post-reply-er! :) I very often come across your answers when I'm looking for stuff!


Mismatch in prometheusRules mixin for lvmLocalPV

As per the title, the mismatch is due to case difference in "lvmLocalPV" between these two files:

jsonnet/openebs-mixin/rules/prometheus-rules.libsonnet#L26 (lowercase):
https://github.com/openebs/monitoring/blob/87b902c85429eedce78033049de9280f39e81372/jsonnet/openebs-mixin/rules/prometheus-rules.libsonnet#L26

jsonnet/openebs-mixin/rules/openebs/lvmlocalpv-rules.libsonnet#5 (mixed case):
https://github.com/openebs/monitoring/blob/87b902c85429eedce78033049de9280f39e81372/jsonnet/openebs-mixin/rules/openebs/lvmlocalpv-rules.libsonnet#L5

This prevents compilation, as showed here:
RUNTIME ERROR: Field does not exist: lvmlocalpv
        vendor/openebs-mixin/rules/prometheus-rules.libsonnet:26:113-175        object <anonymous>
        vendor/openebs-mixin/mixin.libsonnet:9:20-62    object <anonymous>
        vendor/kube-prometheus/lib/mixin.libsonnet:24:78-109
        vendor/kube-prometheus/lib/mixin.libsonnet:26:19-20     object <anonymous>
        During manifestation

Changing to mixcase in jsonnet/openebs-mixin/rules/prometheus-rules.libsonnet#L26 fixes the issue for me, i.e.
- ... + lvmLocalPV(prometheusRules._config).prometheusRules.lvmlocalpv + ...
+ ... + lvmLocalPV(prometheusRules._config).prometheusRules.lvmLocalPV + ...

Ran into same issue. Above fixed it.

Closing the issue as the changes have been merged with PR #104


Disallow READ_ONLY and EX_SH lock simultaneously

Changes proposed in this pull request
Do not allow READ_ONLY and EX_SH locks to be held simultaneously.
Patch testing
Ran all the tx dunit tests and hydra tests in the jira ticket
Other PRs
No
Earlier it was allowed thinking the conflict exception will be thrown
while commiting when lock is upgraded, however there is a scenario
where insert into child can happen violating the foreign key constraint.

Did you try running the store precheckin with this? Its possible some tests may be expecting this and need to be fixed. Which are the tx dunit tests you have mentioned as having run? 'TranDUnit.class' will cover most but I think some RR tests were added in other dunits too later. Also 'TranTest.class' and 'TXTest.class' for junits. One run of full precheckin will be good -- @kneeraj mentioned some existing failures so those can be ignored.

Ran precheckin; no surprises, the failures in store were all existing failures.

Good for merge.


Walk Abstract Syntax Tree to find imports

Rationale: Using regex means that you can only find the imports that are at the top of the page without any spaces between them. There's likely other issues, but that was the one that bit me.
Caveat: Old method would parse files with broken syntax. This one will not.

This looks quite good, I tested it locally and it works as expected. You also added comments to tests, which is also nice :)
This also fixes #36
Thanks for the PR!

In case its a concern that AST walking is slow. I've done some spot tests.
Before AST: runtime 0m0.718s. Found 40 requirements.
After AST: runtime 0m3.043s. Found 60 requirements.
Caveats
Since this reaches down into the depths of the AST; you will get all imports even conditional ones. This may result in a build that’s impossible to actually have; but this is a problem shared with the previous non-AST system.
More likely this will result in a good thing: those imports you forgot about b/c they’re buried in the depths of sites-packages; you can get them now.


Enhancement Request: Add Logging and Email Notification Features in tampering CCTV

Subject: Enhancement Proposal: Logging and Email Notification Features
Dear hashmithagunda123
I hope this message finds you well. I want to contribute on your project by adding the following enhancements.Please give me this issue.
Proposed Enhancements:
Logging Feature: Implement logging functionality to track tampering events and significant actions for better auditing and debugging purposes.
Email Notification Feature: Integrate email notifications to promptly alert users when tampering is detected by the surveillance system.

please assign me this issue as you lhave labelled but not assigned me check once and assign me this issue I surely work on it.
Thank You

assign me this issue I surely work on it

assign me I will do as I have updated the code where any motion is detected or any crime is detected or any motion detection is there it will record and saved as a file so give me issue I surely make changes and enhance the code

Please can you assign this issue to me .I would like to work on this issue .Under GSSOC'24

I have completed the work would you please assign me. Only I have to do pull request and want to merge it. Assign this issue to me

Assign me this issue I have enhanced the features which I have raised.

I would like to work on this issue ,Please assign this issue to me

Assign me this issue as I have done my work. Only thing thing is if you will assign I have to merge only in this. Review my comment and assign me this issue

Please assign me this issue.

I'm eager to contribute! Could you please assign me an issue to work on?
Thank you!

I would love to work on it.Please assign this issue to me.


A way to pull in the whole lot

When size doesn’t matter, you’d sometimes just want to save 5 lines of code and write:
import {flip, curry2, split, and, or, isTruthy} from '1-liners/module';

Here’s one way to do it – which works both for require and the ES6 import:

module.js
module/index.js

SGTM. We could add a npm task to update the module/index with all modules.

:+1:


S390x: Support ME and CRT offloading

S390x has to ability to offload modular exponentiation and CRT operations to Crypto Express Adapters.  This possible performance optimization was not yet used by OpenSSL.  Add support for offloading and implement an optimized version of RSA and DH with it.
The environment variable OPENSSL_s390xcap now recognizes the token "nocex" to prevent offloading.
Signed-off-by: Juergen Christ<EMAIL_ADDRESS>Since this is just an optimization to existing functionality, no additional tests were added.  Also note that testing requires a real s390x and cannot be done on qemu.

Fixed a bug in the new code found by @ifranzki:
Hardware-accelerated CRT only supports RSA keys with p > q.  Handling all other cases via OpenSSL software implementation.

I reviewed this from an s390x point of view, and it looks good now.

Merged to master branch after resolving trivial conflict in crypto/bn.h.
Thank you for your contribution.


Bot not working - Discord update?

Trying to use this app, I found it no longer works.
I see an attempt to connect, the bot appears in Discord, but then disconnects. Nothing shows up in TS3.
Checking the logs, I see:
2023-07-04 16:17:22.983659|INFO    |TeamCord      |   |Waiting for established connection to discord...
2023-07-04 16:17:46.302941|INFO    |TeamCord      |   |Client connected
2023-07-04 16:17:46.311950|INFO    |TeamCord      |   |Connection established to discord
2023-07-04 16:17:50.229260|INFO    |TeamCord      |   |Joining discord channel<PHONE_NUMBER>40444743
2023-07-04 16:17:50.250271|INFO    |TeamCord      |   |Channel bitrate: 64000
2023-07-04 16:18:05.285897|ERROR   |TeamCord      |   |The operation has timed out.

It would seem there was a Discord update, and this might be the cause/issue?
https://github.com/discord-net/Discord.Net/issues/2634
Thanks for the app!

A friend tried to update the plugin. Afterwards it always said in the Teamspeak log "Client disconnected".

Seems like although this project has already been ported to Discord.Net 3.x in 2022, there hasn't been a release yet. I'll try compiling the newest state using the latest version of Discord.Net and report back if I succeed.

Unfortunately newer Discord.Net versions than  3.1.0 doesn't work due to changes that Bearer tokens can't be used anymore with this library.
Therefore I no longer provide updates to TeamCord. Furthermore Discord makes it harder to use their API with bearer token in general to prevent users from using other clients than the official Discord client.


Release 1.4.8

User facing issues on the docket:

non-zip_safe pex extraction has a race on renaming #557
Execute pex archive at runtime with -m parameter #547
OSX's python 2.7.10 interpreter reports a bad local platform, bdists fail to resolve #523
pex.resolver.resolve does the wrong thing when given an interpreter and no platform #511
[Errno 13] Permission denied when executing with bdist_pex #570

The #563 fixes would just so happen to solve a big problem for me right now, we have surprising demand for 'task runners' in python that the -m or -c at runtime would gracefully solve
I'm asking 100% out of curiosity, is there an ETA until this drops? And will -m/-c at runtime work with any future pex artifacts built with 1.4.8?

I've been aiming for release the last 4 days - today should be the day and we'll support -m and -c at least until python drops or changes support - the ~whole point is to act like a hermetic python interpreter.
NB: Pex has supported (pex --help-varables) the -m behavior via environment variables for a very long time:
$ PEX_MODULE=app:main ./app.pex
$ PEX_MODULE=tool:fix ./app.pex

So the -m support just allows you to switch from the PEX_MODULE env-var to the -m option like python uses.

Released:

https://github.com/pantsbuild/pex/releases/tag/v1.4.8
https://pypi.org/project/pex/1.4.8/


Fix seqfault in emission of NVPTX due to missing DIsubprogram

Fixes #576
@wsmoses now the only question is: Why is CI passing.

So nested_codegen is breaking this:
                        cf = nested_codegen!(mod, add_one_in_place, Tuple{Any})
                        push!(function_attributes(cf), EnumAttribute("alwaysinline", 0; ctx))
                        permit_inlining!(cf)

I suspect it is due to the call not having a !dbg info.


Can't compile or install v<IP_ADDRESS>

Hi! I'd like to try out hsdev, but cabal won't build it for me. Something seems to be broken:
$ cabal install hsdev
Resolving dependencies...
Configuring hsdev-<IP_ADDRESS>...
Building hsdev-<IP_ADDRESS>...
Failed to install hsdev-<IP_ADDRESS>
Build log ( /home/max/.cabal/logs/ghc-8.0.2/hsdev-<IP_ADDRESS>-Eu13OLfadsmBHrSqhDVsuM.log ):
cabal: Entering directory '/tmp/cabal-tmp-4660/hsdev-<IP_ADDRESS>'
Configuring hsdev-<IP_ADDRESS>...
Preprocessing library for hsdev-<IP_ADDRESS>..
Building library for hsdev-<IP_ADDRESS>..
[ 1 of 76] Compiling System.Directory.Paths ( src/System/Directory/Paths.hs, dist/build/System/Directory/Paths.o )
[ 2 of 76] Compiling HsDev.Version    ( src/HsDev/Version.hs, dist/build/HsDev/Version.o )
[ 3 of 76] Compiling HsDev.Util       ( src/HsDev/Util.hs, dist/build/HsDev/Util.o )
[ 4 of 76] Compiling System.Directory.Watcher ( src/System/Directory/Watcher.hs, dist/build/System/Directory/Watcher.o )

src/System/Directory/Watcher.hs:160:17: error:
    • The constructor ‘FS.Added’ should have 3 arguments, but has been given 2
    • In the pattern: FS.Added _ _
      In a case alternative: FS.Added _ _ -> Added
      In the expression:
        case e of {
          FS.Added _ _ -> Added
          FS.Modified _ _ -> Modified
          FS.Removed _ _ -> Removed }
cabal: Leaving directory '/tmp/cabal-tmp-4660/hsdev-<IP_ADDRESS>'
cabal: Error: some packages failed to install:
hsdev-<IP_ADDRESS>-Eu13OLfadsmBHrSqhDVsuM failed during the building phase. The
exception was:
ExitFailure 1

I'm using GHC 8.0.2-10 on Ubuntu 17.10.

Cabal installs it now. Thanks!


⚠ Bofrost.lu has degraded performance

In f1dd161, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 870 ms

Resolved: Bofrost.lu performance has improved in fdb4f00 after 7 minutes.


Missing folders aren't being generated when there are other ones already present.

So when there is a folder already in the /EXILED/Configs/AutoEvent/ folder, the plugin will not generate the other folders, including their respective files (configs, events).
Here's the conversation that I brought up on the EXILED Discord server.

Plugin.cs#134 is the line where directories are created. If debug mode is enabled there may be logs. An exception for any of the folders could prevent other folders from being generated. The exception could be from file permissions.

https://github.com/RisottoMan/AutoEvent/blob/main/AutoEvent/Plugin.cs#L134

That line calls this method.
CreateDirectoryIfNotExists
https://github.com/RisottoMan/AutoEvent/blob/main/AutoEvent/Plugin.cs#L194

Closed, I no longer support AutoEvent.


Ipc support

This commit depends on #23. And introduces an approach that allowes IPC backend support.

I have rebased changes on the top.

Something is wrong with CI.

CI is still unreliable, I want to merge everything that is safe to merge and postphone other things to make some sort of refactoring in other to improve situation.


Option to change units when visualizing data

Sometimes, the user wants to adjust the units shown in plots. It may be useful to be able to adjust those manually.

As an alternative, we could show everything in SI units.

There could be also an checkbox/dropdown in order to decide whether to show everything in SI units or not.


Html text coercion

Add support for HTML text coercion.

@jonmaim Do you think this can be merged?

Might be better to do the PR upstream: https://github.com/VersoSolutions/CordovaClipboard


Use zap-cli for zap codegen instead of using third_party/zap/repo

This uses #23643 - our docker images now contain zap-cli which is usable for zap codegen:

on my machine that is up to 25% faster to run
CI results seem to indicate zap check time dropped from 14-20 minutes to 6 minutes (but only one datapoint available so far ... overall though I assume this will be quite a bit faster)

Changes:

update generate.py and convert.py to invoke zap-cli instead of npm ...
removed all zap bootstrap logic as the bootstrap is generally "Install zap"
added some documentation in BUILDING.md about how to install zap releases
fixed references inside our json files that went into zap repo: copied over manufacturers.xml from zap into CHIP and updated json to refer to it
deleted third_party/zap as a submodule
updated zap Github Actions to use zap-cli (and the new chip-build image).

Short story: the scripts people use right now should keep working.  If they require ZAP to be installed separately somehow, they need to detect if it's not and complain, ideally with a pointer to documentation for how to create the right setup.

Short story: the scripts people use right now should keep working. If they require ZAP to be installed separately somehow, they need to detect if it's not and complain, ideally with a pointer to documentation for how to create the right setup (e.g. install ZAP, set some env var to point to it, something like that).

@bzbarsky-apple
I changed the generate.py script and kept it running, but with the prerequisite of zap-cli installation (which I did make in our docker images, but in other developer machines it would need to be handled separately)
What setup would be acceptable? I do not run zap often except the regen all from the docker image, so my general flows are quite restricted.
My understanding of requests are:

have a env variable able to point to a development version of zap and be able to run that (is this true)?
if zap-cli is not found, provide a human-friendly description of please install zap release, see documentation in .....

Is the above correct? Sufficient? anything more/different?

have a env variable able to point to a development version of zap and be able to run that (is this true)?

Doesn't have to be an env var, but the specific request is: have some way to run either generate.py or zap_regen_all.py and have it run a development version of zap. Have the script raise a useful error if it can't find zap, which allows discovering how to use either a release or development version.
Similarly for run_zaptool.sh.

have a env variable able to point to a development version of zap and be able to run that (is this true)?

Doesn't have to be an env var, but the specific request is: have some way to run either generate.py or zap_regen_all.py and have it run a development version of zap. Have the script raise a useful error if it can't find zap, which allows discovering how to use either a release or development version.
Similarly for run_zaptool.sh.

Updated all scripts to support:

$ZAP_DEVELOPMENT_PATH for local zap development
$ZAP_INSTALL_PATH for install from zip (but not set in $PATH)
$PATH usage otherwise

Fast track: had several review passes and this was verified on both linux and mac. Unlikely to be able to review more next week given thanks giving.


WIP PR with hackathon changes

Checklist

[ ] Update changelog in CHANGELOG.md.

Closing. 🎉 Last of the changes are in #23


Handle excluded_pods not set in configuration file

I broke this during https://github.com/xing/XNGPodsSynchronizer/pull/6, I think it shouldn't be mandatory to have that in the configuration file.

Coverage increased (+0.1%) to 82.778% when pulling 61e5cfa9239312fa14083864ab8cfe6bf3d025a1 on Ruenzuo:fix_exclude_pods_not_set into 764b472d6ea770bcdc87d2630079ff25ceccd1ac on xing:master.

I think I had this lying around as well. 👌


update our build.gradle based on the latest AdvantageKit instructions

Our build.gradle has fallen behind the most recent AdvantageKit instructions.

Fixed in 3061-lib 2025 beta 0.


Isolated integration tests

What this PR does / why we need it:
This PR tries to introduce a concept of isolated integration tests. The basic principles of those are:

The idea of a shared kind cluster from the traditional integration tests is retained
kubernetes-sigs/e2e-framework is used for tests and Features (its own thing, more details will follow, together with a guide and TESTING.md entry) setup and teardown

Thanks to it we can inject things like ktf's cluster for the purpose of deploying addons in test.
This allows us to install kong addon - Kong Gateway installation via the helm chart - per test (or rather per feature, but that's a detail, more details will follow)
This OTOH allows to

Run tests in parallel being sure that no test conflicts with another one
Not need to "lock a mutex" for a listener port

Thanks to e2e-framework's features like test Feature's labels we're able to filter the tests not only via names but also by labels and only those tests that were filtered will have their setup run

The reason we need to use Features is https://github.com/kubernetes-sigs/e2e-framework/issues/330 which for some reason doesn't allow use to use a shared setup like tenv.BeforeEach[Test|Feature]

An extension of this new proposal could be a merge of the existing system of integration tests and the new one where based on the test Feature labels we'll be able to use a shared kong instance (installed once in kong namespace) or a dedicated one (installed per Feature in its own dedicated namespace)

Special notes for your reviewer:
Added a separate section in TESTING.md
So far the new suite is in the test/integration/isolated.

What do we gain by this change in terms of numbers?
Non scientific comparison of relevant test suites:

dbless expressions router suite before this change: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6510664946/job/17690016290

tests run: 21m52s

dbless expressions router suite after this change: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6511109860/job/17737909158

tests run: 16m16s

NOTE: this moved the tests around, from the above mentioned suite, to isolated-dbless-expression-router suite (which run for: 6m0s) but the change is that in the isolated suite tests can run in parallel without any interference so the more tests we add there the more benefits we'll see.

@mlavacca

I have one question though - we are running in isolation the UDPRoute tests only. Which other tests do you think we can run in such an isolated environment? Do we have something we should avoid?

I don't have everything written down because at the time I put up this PR I wasn't sure everyone would be on board with this approach but hey! It seems now that we're mostly OK with this we can plan ahead.
My very high level plan for this is:

merge this PR
address #4847
reconsider if we want to use kong per feature (current approach mostly due to #4847) or kong per test (as in Go test)
migrate all integration tests 1 by 1 to the new (isolated) framework

during this migrate decide if the test should be isolated (get its own kong instance and namespace) or use a shared installation of kong (installed in default namespace)

@mlavacca

I have one question though - we are running in isolation the UDPRoute tests only. Which other tests do you think we can run in such an isolated environment? Do we have something we should avoid?

I don't have everything written down because at the time I put up this PR I wasn't sure everyone would be on board with this approach but hey! It seems now that we're mostly OK with this we can plan ahead.
My very high level plan for this is:

merge this PR

address Tests: can't use e2e-framework's [After|Before]EachFeature to get conditional setup / teardown run #4847

reconsider if we want to use kong per feature (current approach mostly due to Tests: can't use e2e-framework's [After|Before]EachFeature to get conditional setup / teardown run #4847) or kong per test (as in Go test)

migrate all integration tests 1 by 1 to the new (isolated) framework

during this migrate decide if the test should be isolated (get its own kong instance and namespace) or use a shared installation of kong (installed in default namespace)

I like this plan, sounds good to me 👍

@randmonkey and @programmer04 Feel free to respond to the still opened conversations and close them if you feel they have been addressed.

https://github.com/Kong/kubernetes-ingress-controller/issues/4847 can be considered a follow up to this PR.
When this gets merged we're already going to use  a version of e2e-framework which will contain the fix.


Another feature request

Please add a button to the console output overlay to copy the contents to the clipboard.

no longer necessary


Dictation API

Added support for dictation API (#102)

Awesome, this is great, thank you for this! Let me know if you need any help or clarification. If you also don't have the time to fix it up, let me know as well and I can pick up the slack of necessary.

@Meiguro - I think I've addressed all your concerns.. take a look and let me know what you think :smile_cat:

:+1: The only concern is that the docs are grabbed from master, so you may have to separate the doc improvements in a separate PR to be merged once cloudpebble has the updated pebble.js


Update 1.19.3

Haven't had time to extensively test but seems to work properly.
For #57

my goodness.

this takes far more knowledge of minecraft's codebase than i have

The main changes are that 1.19.3 removed the Widget interface in favor of the AbstractWidget class.
They also split the registry into Registry and BuiltInRegistries.
Truth be told I didn't take the time to deep drive into the diffs and re-implement functionality against the source code, I just updated it so it worked as required and my friend could enjoy it.
Besides, this is just a minor update so it's not like the legacy code would remove new functionality from the recipe book or anything.

Everything seems to be working

Had the same issue running the forge test. Assumed it was the configs.
Compiled it both for fabric and forge and tested it on both, seemed to work fine on both.

Forge seems to work fine!


CMD in Dockerfile

The Dockerfile needs CMD entry points, relying on docker-compose proved to be bad when the image used in muilticontainer mode in other apps.

Implemented in https://github.com/Flagro/VecMetaQ/commit/4b28e6e91a78c7798e55d0b672405b62edb5d8e8


Finish documentation-related TBDs

Finish Quickstart with final catalog syntax
Fix docstrings in API docs
Implement !template_int and !template_datetime
Implement shell() and env() for catalog files
Decide on zero-length dataframe for metadata
Better description of Intake uses in overview

Closing this. Not that documentation is complete or comprehensive, but most of what is here is done, and we should have more specific docs issues.