How to play online streams from http://torrent-tv.ru/

Hi folks,
I am a one of that lucky who have installed and configured this powerful feature on my own Wi-Fi router and now I want to continue in my tests and I'm gonna to play online torrent streams from http://torrent-tv.ru/ (or similar). What do you think, is it possible?

peerflix supports playback of all regular torrent files and magnet links

Great question, even though it's off-topic.
Look at torrent-tv.ru's guide on how to use on Mac, they have a HTTP proxy software you can download and run. They use Ace Stream, who have extended the bittorrent protocol to support live playing.
As I said, Ace Stream have a HTTP proxy, so this can be used on other platforms / through other software, but unfortunately it will remain proprietary until someone reverse engineers it.

They software are virus, and works unstable, it's hardcoded to some specific hardware, and there are a lots of other issues, but I need only open their torrent streams in peerflix. I've tried to do it, but I see only
fetching torrent metadata from 0 peers


[FEA] Multi-gpu dataloader

 Issue by jperez999
Wednesday May 27, 2020 at 16:31 GMT
Originally opened as https://github.com/rapidsai/recsys/issues/176

trying to get a multi_gpu dataloader setup up for the JoC release in june/july. Should coincide with our 0.2 release.

We should work with distributed pytorch training using apex: https://github.com/nvidia/apex


View/Edit visit details

Visit Details:
Things to remember:
Edit visit should give possibility to doctor to add several detail regarding the upcoming visit.

Details will be visible on the trial participant page:

no longer required / waiting for business clarifications


Renew all garden access secrets on seed when triggered by annotation

How to categorize this PR?

/area security usability
/kind enhancement
What this PR does / why we need it:
This PR adds a mechanism for renewing all garden access secrets on a given seed by annotating it with gardener.cloud/operation=renew-garden-access-secrets.
ref https://github.com/gardener/gardener/pull/8032#discussion_r1224445056
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/8001
Special notes for your reviewer:
/cc @oliver-goetz @rfranzke
Release note:

NONE

/assign

@rfranzke @oliver-goetz thanks for your reviews, PTAL :)

/lgtm

/lgtm
/approve
/retest


QA 02/26

[ ] capitalization on kube platform readme
[ ] comma separation of lists in intros of getting started
[ ] infer default package name during npm init @dxos
[ ] npm init @dxos shouldn't print files saved
[ ] plate rename saved to wrote (during TemplatingResult.save())

├─┬ @dxos/react-appkit 0.1.26
│ └── ✕ missing peer<EMAIL_ADDRESS>├─┬ @vitejs/plugin-react 3.1.0
│ └── ✕ unmet peer<EMAIL_ADDRESS>found 4.0.4
└─┬ @storybook/addon-actions 6.5.16
  └─┬ react-inspector 5.1.1
    └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17.0.0": found 18.2.0
Peer dependencies that should be installed:
<EMAIL_ADDRESS>


Observability task: Improve RPC request exception indicator buried points:

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Describe the proposal

EN: Improve RPC request exception indicator buried points:
timeout、no_ provider、network、codec、biz、thread_ Pool exception, etc
中文：完善RPC请求异常指标：timeout、no_provider、network、codec、biz、thread_pool异常等

assign

assign


feat: Added context switching for pages pane

Description
Fixed the context switching issues for pages pane JS, Query and UI tabs.
PR fixes following issue(s)
Fixes https://github.com/appsmithorg/appsmith/issues/29069
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/build-deploy-preview

/ok-to-test

/build-deploy-preview

/ok-to-test

/build-deploy-preview skip-test=true

/ok-to-test

/ok-to-test

/ok-to-test

/build-deploy-preivew skip-tests=true

/build-deploy-preivew skip-tests=true

/build-deploy-preview

/ok-to-test


Cleanup pixel aliases

Remove pixel package alias leftover from an intermediate name change. With the final naming scheme that we settled on it is not needed.

also noticed that we're still referencing github.com/faiface/mainthread and github.com/faiface/glhf, are we ready to switch those over?

Not yet. Let me cut a release and I'll update this pr when it's good to go.to not delay this pr. Let's move ahead with this pr. Create another one with changing the aliases for mainthread and glhf and we can merge when the two other projects are ready.

Approved


Lit HTML Server: Create key from array string

Problem
The problem is that for every new request on the server we end up having different array objects for the same template literal. Since its a new object it has the same shape but is not the same reference. Therefore we do not find a value in the lookup map for the object, which in turn makes the cache grow forever until it crashes since map can't be garbage collected like WeakMaps.
e.g.:

Here both x and y arrays, contain the same literals but they are different objects and therefore have different id when looking up from the map cache ☝🏽, which is what happens on the server side we get a new array object for every request, for the same template literals that we lookup but since they are different objects the map will not be able to find an entry for them.
Whats done
Since the result.string is an Array type, we therefore do key = strings.toString() and by default join all the values in the array by the , separator.
Example
We modified the compiled code with the following e.g.:
var templateCache = /* @__PURE__ */ new Map();
var templateCache2 = new Map();
var id = 0;
function getTemplateInstance(result) {
  const strings = result.strings;
  let template = templateCache.get(strings);
  if (template === void 0) {
    //
    template = getTemplate(strings);
    templateCache.set(strings, template);
    templateCache2.set(strings.toString(), template);
  } else {
    console.log(`cached (templateCache.size: ${templateCache.size}) (templateCache2.size: ${templateCache2.size})`)
  }

  return new TemplateInstance3(template, result.values);
}

We got the following output:

As you can see the templateCache grows until we crash.
However templateCache2 were we use a string always has 9 elements which equals to the amount of templates we have on the server.

@popeindustries ☝🏽

This is very strange. From MDN docs:

For any particular tagged template literal expression, the tag function will always be called with the exact same literal array, no matter how many times the literal is evaluated.

The strings array should preserve identity equality.

This is very strange. From MDN docs:

For any particular tagged template literal expression, the tag function will always be called with the exact same literal array, no matter how many times the literal is evaluated.

The strings array should preserve identity equality.

Two arrays even If they contain the same objects are not the same as far the JS semantics dictate to my knowledge.
I guess what they say here is that for a tagged template literal itself this will be the case. But here we have an array. We did an Array.isArray check when we tested the code before ending with the proposed solution.

Tagged templates are special, and the first array is supposed to be static and frozen for every call, that's part of what makes them so performant:
(From MDN)
const callHistory = [];

function tag(strings, ...values) {
  callHistory.push(strings);
  // Return a freshly made object
  return {};
}

function evaluateLiteral() {
  return tag`Hello, ${"world"}!`;
}

console.log(evaluateLiteral() === evaluateLiteral()); // false; each time `tag` is called, it returns a new object
console.log(callHistory[0] === callHistory[1]); // true; all evaluations of the same tagged literal would pass in the same strings array

Running the benchmark doesn't reproduce this cache-miss behaviour, and lit-html does the same in the browser:
  _$getTemplate(result: TemplateResult) {
    let template = templateCache.get(result.strings);
    if (template === undefined) {
      templateCache.set(result.strings, (template = new Template(result)));
    }
    return template;
  }

Are you able to determine if all subsequent calls result in a miss, or only some?

I may have missed something here – but the strings property of TemplateResult is as far I can tell a TemplateStringsArray, which seems to be the template itself split on the different values it should insert into the template: https://lit.dev/docs/api/templates/#TemplateResult
Additionally, I've come to understand that a Map never gets garbage collected, while a WeakMap does. If that's the case, should the Map used here as a templateCache instead have been a WeakMap?

@janerikbr the result.strings is just the first argument to the tagged template function (html/svg), and is of special type TemplateStringsArray representing the static parts of the template. It is special in that it's frozen, and will always be the exact same Array every time the template is processed.
I don't think a WeakMap is necessary unless it's likely that the templates themselves can be GC'd. Does it change the outcome when testing?

My concern here is that this fix goes against spec and prior expectations (lit-html-server has done this for 4+ yrs), and will have a significant performance impact since this check is on the hot path (7227 req/s vs 5765 req/s). I would like to find out if this is in fact a result of something else, but it's hard for me to investigate if I'm unable to reproduce the problem.

My concern here is that this fix goes against spec and prior expectations (lit-html-server has done this for 4+ yrs), and will have a significant performance impact since this check is on the hot path (7227 req/s vs 5765 req/s). I would like to find out if this is in fact a result of something else, but it's hard for me to investigate if I'm unable to reproduce the problem.

We are using the transpiled js code that is shipped when installed in the node modules with node 18.10.0.
Can try to create a reproducable branch when i find some time but most probably on monday 😅👋

@popeindustries Thanks for clarifying. We may do something wrong on our side and one thing we could try is to run the tests again while at the same time commenting out templates or parts of templates one by one.
And no, WeakMap won't fix the underlying problem here – was thinking more in terms of enabling garabage collection – to prevent the Map from growing and growing? But that may have other implications I don't know of.
God helg! 👋

@popeindustries where can i find the benchmark code which refer to here?

$ node ./benchmark/perf.js

After a lot of debugging and test/failing 😂  like e.g.:

Is it typescript?
is it Esbuild and template literals conversion
...

I managed to find out what is causing the issue and i created an example code here.
You can checkout the code and run:
npm i
npm run perf:unsafe

It should crash in about 10-15s e.g.:

The problem
The main issue is that using unsafeHTML directives, in our html directive is the reason why renderToString(...) is not able to cache the template literal, when it contains such directives, and the templateCache keeps on growing.
My thought then was well lets extract the unsafeHTML() and render them directly from our code, before sending them into the template literal like these e.g.:
async function LiteralTag(someValue) {
  const safeHTML = await renderToString(unsafeHTML(unsafeHTMLValue)); // this is still not cacheable and leaks
  return html`<div>someValue<div>${safeHTML}`;
}

But the problem still remains here,  and it leaks 🤷🏽
Thoughts?
Perhaps we should have e.g.:

An option to renderToString() which indicates that it should not be cached. Or implicitely infer it it has been called with unsafe directives and ther
An renderUnsafeHtmlToString(..) that bypasses the cache mechanisms

Perhaps there is a better solution, all ears here 👋🏽

Great work @cristobal! I'm pretty sure I can fix this without changing the API or caching behaviour.

Great work @cristobal! I'm pretty sure I can fix this without changing the API or caching behaviour.

Cool ping me If there’s something, need input our just help. I can dedicate some work time to this also 👋

Fixed in #21


Docker run: Passthrough environment variables do not get passed through

Problem description

Passthrough environment variables do not get passed through; the documentation says they do.
Problem location

I saw a problem on the following URL: https://github.com/docker/docker/blob/master/docs/reference/commandline/run.md

# pass through this variable from the caller
TEST_PASSTHROUGH
$ TEST_PASSTHROUGH=howdy docker run --env-file ./env.list busybox env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=5198e0745561
TEST_FOO=BAR
TEST_APP_DEST_HOST=<IP_ADDRESS>
TEST_APP_DEST_PORT=8888
_TEST_BAR=FOO
TEST_APP_42=magic
helloWorld=true
TEST_PASSTHROUGH=howdy
HOME=/root
123qwe=bar
org.spring.config=something

Project version(s) affected

Observed in Ubuntu Xenial
$ docker --version
Docker version 17.03.0-ce, build 60ccb22

and macOS
Version 17.03.0-ce-mac2 (15654)
Channel: stable
1d7d97bbbd

The TEST_PASSTHROUGH environment variable does not seem to be passed through:
$  TEST_PASSTHROUGH=howdy docker run busybox env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=2566c262240f
HOME=/root

My reading of the docs suggested it would get passed through.  I am not sure if this is a documentation error, a bug, or my misunderstanding.

I think the example is outdated or confusing.
You can set environment variables like
# option 1, set the value in the command
docker run -e TEST_VAR=value --env-file env.list  alpine env

# option 2.1, use an existing variable
TEST_VAR=value docker run -e TEST_VAR --env-file env.list  alpine env

# option 2.2, use an existing variable
export TEST_VAR=value
docker run -e TEST_VAR --env-file env.list  alpine env

# option 3, use an existing file
cat <<EOL > env.list
TEST_VAR=value
EOL

docker run -e TEST_VAR --env-file env.list  alpine env

You can also mix it all together, and use --env-file and -e at the same time. If the same environment variable is defined both in a file and the environment, the container will be set with the value from the environment.

Hi @joaofnfernandes - Thanks for the workarounds, that may be useful for others who read this issue.
The specific issue is that the PASSTHROUGH method is documented as working, and doesn't in the the versions I tested.
I think this documentation just needs to be updated from the upstream version.

Fixed by @joaofnfernandes back in March. Thanks!

I'm sorry but I can't seem to get this to work either.
A simple test of docker run -e TEST_VAR=1234 --env TEST_VAR2=1234 alpine env reveals the variables in the guest, but docker build -t stockwebservice . && docker run --env JDBC_USERNAME=user --env JDBC_PASSWORD=1234 --env API_PASSWORD=1234 --name stockwebservice stockwebservice refuses to set the environment correctly!
Even changing the Dockerfile to run env instead of my app doesn't work so I'm thinking that the Dockerfile must be the problem.
# We select the base image from. Locally available or from https://hub.docker.com/
FROM openjdk:8-jre-alpine

# Expose TCP port
EXPOSE 8080:8080

# We define the user we will use in this instance to prevent using root that even in a container, can be a security risk.
ARG APPLICATION_USER=ktor

# We define a distribution name as created by gradle's application plugin.
# This distribution will be added to the container.
ARG DISTRIBUTION=stockwebservice-0.1

# Then we add the user, create the /app folder and give permissions to our user.
RUN adduser -D -g '' $APPLICATION_USER
RUN mkdir /app
RUN chown -R $APPLICATION_USER /app

# Marks this container to use the specified $APPLICATION_USER
USER $APPLICATION_USER

# We copy the FAT Jar we built into the /app folder and sets that folder as the working directory.
ADD "./build/distributions/$DISTRIBUTION.tar" /app
WORKDIR /app

RUN env
RUN "./$DISTRIBUTION/bin/stockwebservice"

Use .env file instead?


Downloading binaries fails with wrong sha256 checksum

Bug description
npm ERR! code 1
npm ERR! path /home/d2766cb87e42ac78b6cf6400f1e52be457744eee/node/node_modules/@prisma/engines
npm ERR! command failed
npm ERR! command sh -c -- node scripts/postinstall.js
npm ERR! /home/d2766cb87e42ac78b6cf6400f1e52be457744eee/node/node_modules/@prisma/engines/dist/scripts/postinstall.js:22677
npm ERR!             throw new Error(`sha256 of ${url} (zipped) should be ${zippedSha256} but is ${zippedHash}`);
npm ERR!                   ^
npm ERR!
npm ERR! Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz (zipped) should be b8137868e4dc45f6cb384173fbfc7606b4cb0641328720f2fad95c5e74e6971c but is fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354

How to reproduce
$ wget https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
--2022-11-11 10:04:38--  https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
Resolving binaries.prisma.sh (binaries.prisma.sh)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to binaries.prisma.sh (binaries.prisma.sh)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13665486 (13M) [binary/octet-stream]
Saving to: 'migration-engine.gz'

migration-engine.gz                                        100%[========================================================================================================================================>]  13.03M  30.3KB/s    in 1m 46s

2022-11-11 10:06:25 (126 KB/s) - 'migration-engine.gz' saved [13665486/13665486]

$ sha256sum migration-engine.gz
fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354  migration-engine.gz

Expected behavior
Correct sha256 checksum when downloading the binary.
Prisma information
Not needed, installation of prisma fails even without a schema.
Environment & setup
OS: CentOS 7.5
Database: MySQL
Node.js version: 18.12.1
Prisma Version
4.6.0

Got the same error with prisma 4.5.0 in docker on ubuntu

Does anyony have a solution?
That's funny, because we have a demo today but now we cannot rebuild our containers
I thought it depends on prisma version, but it looks like it doesn't

Hey everyone who reported this @87brandonn @1Vlod @Trainxy, some things you can do to help us understand this:

Where are you or your server that is doing the downloading located?
What operating system are you running and which binary type (rhel-openssl-1.1.x in the example above) is your Prisma CLI trying to download?
Can you test with another internet connection, e.g. mobile tethering via mobile phone and see if the problem persists?
If you have not, please include the full error message (as @Trainxy did, with the URLs and checksums and so on) in a comment here so we can really look deep at what is going on.
Can you please upload the gz file that is causing the problem (by clicking the link in the error message) here in a comment so we can compare them to what should be returned?

Thanks.

Thanks for the information you included in your initial descriptoin @Trainxy. I get a different checksum after downloading:
janpio@Surface-Studio:~$ wget https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
--2022-11-11 10:04:54--  https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
Resolving binaries.prisma.sh (binaries.prisma.sh)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to binaries.prisma.sh (binaries.prisma.sh)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13665931 (13M) [binary/octet-stream]
Saving to: ‘migration-engine.gz’

migration-engine.gz         100%[===========================================>]  13.03M  27.2MB/s    in 0.5s

2022-11-11 10:04:55 (27.2 MB/s) - ‘migration-engine.gz’ saved [13665931/13665931]

janpio@Surface-Studio:~$ sha256sum migration-engine.gz
b8137868e4dc45f6cb384173fbfc7606b4cb0641328720f2fad95c5e74e6971c  migration-engine.gz

And that is indeed the one our tool expects, and talks about in the error message:
npm ERR! Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz (zipped) should be b8137868e4dc45f6cb384173fbfc7606b4cb0641328720f2fad95c5e74e6971c but is fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354

@dev-isemo:

#8 34.42 npm ERR! Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/linux-musl/migration-engine.gz (zipped) should be fef9a669cb5a4a866b0c3f54c87b19fa23b34029770e156ff65af0086b8cfb47 but is a8c0f25dba718250a33974276a0dacbcc8e8d9ac754ef2f60c40fbc011b772fd

When I download that file and checksum it, I get the correct one:
janpio@Surface-Studio:~$ wget https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/linux-musl/migration-engine.gz
--2022-11-11 19:58:21--  https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/linux-musl/migration-engine.gz
Resolving binaries.prisma.sh (binaries.prisma.sh)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to binaries.prisma.sh (binaries.prisma.sh)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15090616 (14M) [binary/octet-stream]
Saving to: ‘migration-engine.gz.1’

migration-engine.gz.1       100%[===========================================>]  14.39M  27.5MB/s    in 0.5s

2022-11-11 19:58:22 (27.5 MB/s) - ‘migration-engine.gz.1’ saved [15090616/15090616]

janpio@Surface-Studio:~$ sha256sum migration-engine.gz.1
fef9a669cb5a4a866b0c3f54c87b19fa23b34029770e156ff65af0086b8cfb47  migration-engine.gz

@eliliam had posted in a separate issue:

While trying to install prisma via npm install prisma, the installation fails in the step where it installs @prisma/engines and tries to download the migration-engine.gz binary. When it compares the hash with what it's "supposed" to be, the comparison fails causing the whole installation to fail.

Here is the file that was downloaded for me, as well as the link in question. Link: binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/debian-openssl-1.1.x/migration-engine.gz
My version: migration-engine.gz

What would be causing different users to retrieve different files entirely when they should be the same?

CDN or network issues.
For now we have 3 reports from differnet people, but all with different operating systems: rhel-openssl-1.1.x from @Trainxy, linux-musl by @dev-isemo and debian-openssl-1.1.x by you @eliliam. When I download most of these, I get the same hashes that the CLI seems to expect.

So to list all the cases and error messages:

Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz (zipped) should be b8137868e4dc45f6cb384173fbfc7606b4cb0641328720f2fad95c5e74e6971c but is fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354
Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/linux-musl/migration-engine.gz (zipped) should be fef9a669cb5a4a866b0c3f54c87b19fa23b34029770e156ff65af0086b8cfb47 but is a8c0f25dba718250a33974276a0dacbcc8e8d9ac754ef2f60c40fbc011b772fd
Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/debian-openssl-1.1.x/migration-engine.gz (unzipped) should be 003a64e669a41cbedc77eceddbcaa857e8e5d86a0f7e258dccc88cd3273b1c3 but is 6a14286c51fbc005ab193eac8dcca740275fd9716dd226e1f857fab2dc00d778

When collecting these, and trying to reproduce the hashes I noticed that your case @eliliam is actually different: The error message says (unzipped) instead of (zipped) for the others - which explains why the checksum for the downloaded .gz did not match either checksum value. When I unzipped the file, the checksum indeed was 6a14286c51fbc005ab193eac8dcca740275fd9716dd226e1f857fab2dc00d778 again as expected.

The remaining task for the previous comment that now would help a lot:

Can you test with another internet connection, e.g. mobile tethering via mobile phone and see if the problem persists?

@janpio when I download it and decompress the gz file I still have a mismatched hash.

Can you upload the extracted file please and the checksum you get for that file? I think before you uploaded only the archive.

SHA256 hash: 6a14286c51fbc005ab193eac8dcca740275fd9716dd226e1f857fab2dc00d778
Github won't let me upload the unzipped file due to file extension limits, so I've uploaded it elsewhere.
Here is the unzipped file: https://paste.c-net.org/EnhancePeaked
And here is the gzipped file before decompression:
migration-engine.gz

Something is off there @eliliam. When I use the gzipped file and unpack it, I get a different file than what you uploaded to paste.c-net.org - different size, content and (logically) checksum. Are you 100% sure that this comes from https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/debian-openssl-1.1.x/migration-engine.gz?

Here is an archive with the original files from the CDN for debian-openssl-1.1.x, so https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/debian-openssl-1.1.x/migration-engine.gz:
migration-engine.zip The archive, the checksum for the archive, and the checksum for the unpacked file.

Here is another case that was raised in an old issue:

    Since this morning we encounter this issue and there is not much information out there, so that is why I open this old issue :)

The Dockerfile executes RUN npm ci
[2022-11-11T14:28:23.999Z] Step 7/161 : RUN npm ci
[2022-11-11T14:28:23.999Z]  ---> Running in a3b499d60536
--- snip ---
[2022-11-11T14:29:06.387Z] npm ERR! code 1
[2022-11-11T14:29:06.387Z] npm ERR! path /app/node_modules/@prisma/engines
[2022-11-11T14:29:06.387Z] npm ERR! command failed
[2022-11-11T14:29:06.387Z] npm ERR! command sh -c -- node scripts/postinstall.js
[2022-11-11T14:29:06.387Z] npm ERR! /app/node_modules/@prisma/engines/dist/scripts/postinstall.js:22677
[2022-11-11T14:29:06.387Z] npm ERR!             throw new Error(`sha256 of ${url} (zipped) should be ${zippedSha256} but is ${zippedHash}`);
[2022-11-11T14:29:06.387Z] npm ERR!                   ^
[2022-11-11T14:29:06.387Z] npm ERR!
[2022-11-11T14:29:06.387Z] npm ERR! Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/linux-musl/migration-engine.gz (zipped) should be fef9a669cb5a4a866b0c3f54c87b19fa23b34029770e156ff65af0086b8cfb47 but is a8c0f25dba718250a33974276a0dacbcc8e8d9ac754ef2f60c40fbc011b772fd
[2022-11-11T14:29:06.387Z] npm ERR!     at /app/node_modules/@prisma/engines/dist/scripts/postinstall.js:22677:19
[2022-11-11T14:29:06.387Z] npm ERR!     at runMicrotasks (<anonymous>)
[2022-11-11T14:29:06.387Z] npm ERR!     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2022-11-11T14:29:06.387Z]
[2022-11-11T14:29:06.387Z] npm ERR!

Originally posted by @DarkSmile92 in https://github.com/prisma/prisma/issues/10312#issuecomment-1311768404

@darksmile92 You case seems to be identical to https://github.com/prisma/prisma/issues/16233#issuecomment-1311622549 :/

Our current thoughts:

Either this is a hickup on AWS, S3 and Cloudfont that we can not influence
Or this is another case of https://github.com/prisma/prisma/issues/10328#issue-1056323219 - but we have not find a clear indication for that.

Here is an archive with the original files from the CDN for debian-openssl-1.1.x, so https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/debian-openssl-1.1.x/migration-engine.gz: migration-engine.zip The archive, the checksum for the archive, and the checksum for the unpacked file.

I have redownloaded the file and created a similar zip of the gzipped file, extracted file, and their respective sha256 sums. I still get the same bad values.
migration-engine-bad.zip
If it is indeed a CloudFront caching issue, what steps need to be taken to resolve this issue, and who is able to accomplish this?

That would be us of course.
I just triggered a minimal invalidation. Can you check if the problem is already resolved maybe?
(The problem here is always that only some CDN nodes are affected, and it seems this time I have no way to reproduce this at all)

I was receiving the same issue, found this thread and @janpio can confirm that after your comment I was able to run npm install without issue.

Works for me again! 👍

@janpio Fantastic that worked for me too!

Thanks. Sorry that took so long to connect the dots, only the second time in the last 3 years this happened.
I'll wait for confirmation from @Trainxy to close the issue, or they can do that themselves.

@janpio Thanks for the quick help yesterday! :)

Thanks. Sorry that took so long to connect the dots, only the second time in the last 3 years this happened.
I'll wait for confirmation from @Trainxy to close the issue, or they can do that themselves.

@janpio Thanks for your help. I installed node_modules successfully after you solve.

Are you trying to upgrade to 4.6.1 when this happens

Hey @janpio
we upgraded to Prisma 4.6.1 and got the following error (a few days ago):
 error: Error: Could not find prisma-fmt binary. Searched in<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
Are you familiar with this issue?

Not really, please open a new issue and provide all the information.
Especially what command output this, and what it output before and after.


fix(protobuf) minor bugfixes for protobuf

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.

LGTM - Thanks for the cleanup + additional testing :)


Variable/IndexVariable do not accept a tuple for data.

What happened?
It appears that Variable and IndexVariable do not accept a tuple for the data parameter even though the docstring suggests it should be able to accept array_like objects (tuple falls under this type of object, right?).
What did you expect to happen?
Successful instantiation of a Variable/IndexVariable object, but instead a ValueError exception is raised.
Minimal Complete Verifiable Example
import xarray as xr

xr.Variable(data=(2, 3, 45), dims="day")

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[x] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
ValueError: dimensions ('day',) must have the same length as the number of data dimensions, ndim=0

Anything else we need to know?
This error seems to be triggered by the self._parse_dimensions(dims) call inside the Variable class. This problem does not happen if I use a list. But I find it strange that the array_like data specifically needs to be a certain type of object for the call to work. Maybe if it has to be a list then the docstring should reflect that.

I've no idea what's the purpose for packing tuples into 0d arrays but as there are also tests for it in the above PR I'm assuming there is one real reason. Maybe @shoyer can chime in here to shed some light?

See  https://github.com/pydata/xarray/issues/4404 It seems like this is for MultiIndex support. A better error message  and  documentation  would be a great contribution!


Fix relative URLs in getRepoURL

This should fix #28

cc @yakov116

Works!

This means I have to release a hotfix for RG, doesn't it?

Yes

Did it only break releases-tab and recently-pushed-branches-enhancements on Releases? Doesn't feel too urgent so far. Let's see if we broke anything else first (or wait until Thursday)

As soon as I saw it broke on releases I did a mass check. I dont see any where else.

Thank you!


Imaging sonar message discussion

This is the place for discussion of SonarImage.msg.

Closing in favor of people making specific issues for more specific requested changes on the message.


[Infra] Setup a public Kubernetes cluster for demos

Setup a public Kubernetes cluster for demos under xsk.io domain

#355


Functionality to compile only OpenFPGA engine.

Is your feature request related to a problem? Please describe.
The feature will reduce compilation time when the user is not interested in yosys build.
Describe the solution you'd like
Add compile_openfpga target in the Makefile which will execute CMAKE with flags that will disable yosys build.
Describe alternatives you've considered
Alternatively a new target can be added to the Makefile which will combine checkout with the build of only OpenFPGA engine.
Additional context
Users having custom Synthesis tools will benefit from this future.

@tpagarani @coolbreeze413 Would you mind modifying our Makefile to support this feature? It will help us in testing different yosys versions from containers. Let me know what you think.

Close as PR #426 is merged


Proposal for global configuration object

I'd like to suggest making the DaLi configuration dict globally available, similar to the way LOGGER is globally available.  This will make the configuration available everywhere without passing it around as a function argument.  The code could be as simple as this:
# dali_configuration.py
CONFIG: Dict[str, Any] = copy.deepcopy(DEFAULT_CONFIGURATION)

# Everywhere else
from dali.dali_configuration import CONFIG

# Sample code in dali_main
CONFIG[section_name] = _validate_transaction_hints_configuration(ini_config, section_name)

I haven't tried this yet.  Any pitfalls I may be overlooking?

Thanks for raising this: it allows me to clarify some of DaLI and RP2 design decisions. It also made me realize this is missing from the Design Guidelines section of the documentation, so I updated it.
One of the design principles of RP2 and DaLI is that all global state is immutable: of course in Python there is no such thing as global constants, so this boils down to convention more than anything else. In other words: any global state is initialized where it is declared and then never modified again. This convention is valid throughout the code and gives us the advantages of immutability for global state, even though Python itself doesn't support the concept at the language level.
The configuration dictionary is built bit by bit at runtime as main() parses the .ini file, so in my mind it doesn't fit the above description of an immutable global. This is why I left configuration as a pass-in variable. Hope this helps.

Thanks for the clarification. I agree immutable objects have advantages over mutable objects and the configuration object is an ordinary dict which will be potentially exposed to changes wherever it is used. Those changes can happen regardless of whether the config is global or passed-in. My reason for wanting the global state is because it encourages developers to increase product flexibility by adding new configuration parameters in a low-cost way. We only need to change the code where the configuration is used, and don't need to change all the higher-level calling functions.
Is there a way we can get the best of both worlds? Can you think of a good way to construct an immutable configuration after parsing and validating the ini file?

I'm not sure I understand your point: configuration parameters and sections can still be added easily today with the existing structure. There is no need to change higher level calling functions when adding parameters to the configuration. Could you elaborate?

Maybe I'm thinking about this the wrong way, or was I unclear?  Let me try again. Consider the function calling diagram below.
We have 5 modules: main, A, B, C, and the configuration module (not shown).
We have 6 functions: main, A1, A2, B1, B2, C.
We have 6 function calls shown by the arrows.
main -> A1 -> B1
               \
                C
               /
main -> A2 -> B2

Imagine the code is initially designed such that the configuration object is built in main, but it is not used in any of the other functions shown, so it is not passed as a function argument to any of them.
Later, we decide to add configurable behavior to function C and nowhere else.
Regardless of whether the configuration object is global or not, we will modify the configuration module (not shown) and the main module to validate and add the new configuration parameters.
If the configuration object is global, we reference it in function C, but none of the function calls are modified because none of the function signatures are changed.
If the configuration object is not global, we will modify 4 additional functions A1, A2, B1, B2 and all 6 function calls to accept the configuration object as a function argument.  None of those functions will use the configuration object in any way other than passing it along.
Since the function signatures change, all the unit tests for all the functions will also change to construct and pass-in the configuration object.
When the PR is submitted, the reviewer will need to examine the code changes in all the functions and tests, spread across multiple modules.
This is what I meant by changing the higher-level calling functions and why I like the low-cost approach of referencing a global object where the configurable behavior is needed.
Am I misunderstanding something?

Let me use real code from the repository to explain what I mean and avoid ambiguity:

the input_loader() function creates dali_configuration: Dict[str, Any] = DEFAULT_CONFIGURATION, then
it initializes it the dictionary with info from the config file and passes it to a few functions, like for example
the transaction resolver: resolve_transactions(transactions, dali_configuration, args.read_spot_price_from_web)
the transaction resolver is now free to use any information from dali_configuration it wants (e.g. the transaction hints section)

Now let's consider two cases:

a parameter foo is added to the transaction hints section
a new section bar is added to the configuration containing new parameters

In both of these cases no code needs to change in the transaction resolver or any other function (unless of course the function needs to use the new parameters/sections). When the PR adding 1. and 2. is submitted the reviewer only has to review the actual changes to the configuration logic: function signatures are unaffected.

That's clear enough for me.  I'll continue my development efforts following the design guidelines.

Ok to close this issue?


Ticker variables are broken, showing constant values

When I use ticker as the formula for Position Rate, I get a simulation that seems accurate:

However, when I use an actual variable, like ticker.last the simulation draws the Take Position line in an incorrect position:

A similar thing happens when I use arithmetic operations on more than one of the ticker variables, such as in ticker.ask-(ticker.ask-ticker.bid)*0.2:

I did a a few tests:

I set ticker.last + 1000 as a take profit formula, just to be able to see the value of ticker.last. The variable ticker.last seems to have a fixed value for long periods of time (if not always). The value is 10357.71

I did a similar test with ticker.bid and the same thing happens. The value for ticker.bid is 10398.38, and seems to be constant, even when the market was at 13K +:

Fixed at latest release


Graph cut off if I switch stacks while service info is up

Version - v1.0.1
Steps to Reproduce:

Create two stacks
Add a service to each stack
Click on one of the stacks to get to details page
Click on Graph icon
Click on service to bring up service info
Use drop-down to switch stacks

Results: The graph view is cut off

Expected:  Graph view should not be cut off.

https://github.com/rancher/ui/pull/722

@lvuch This needs to be conditional based on whether the info popup is shown or not...

https://github.com/rancher/ui/pull/725

Version - master 6/15
Verified fixed


Why is bigvgan better than Avovodo ?

Hi,
I finetune Toucan Meta model on 1k on a reduced dataset to understand the difference between Avocodo and BigVGan.
Here are the spectrograms :

Apart from the 12kHz area which is a bit larger for the BigVGan version I can barely differences (I may not look at the right place). Where are the improvements ?
By the way why is there a dark strip around 12kHz ?
Thanks in advance for your explanations!

You cannot see the difference in the spectrogram, because a spectrogram does not contain the phase shift information, which is what the vocoder tries to reconstruct. Since the input to the vocoder is already spectrogram, the spectrogram of the output will simply be again the same as the input ideally.
The improvement lies in the generator of BigVGAN, which has mechanisms built in to avoid aliasing during the upsampling process.
The area at 12kHz is due to the signal being 24kHz. So anything above the Nyquist frequency (half the sampling rate, i.e. 12kHz in this case) in a spectrogram is due to a problem called imaging and something that we want to avoid.

Thanks for your explanations. I tried to simply filter anything above 12 kHz but it did not sound better.


Add DNS01 Challenge

Feature request
Implement ACME-DNS01 Challenge
Makes it possible to use wildcard certificates or when http challenge is not an option.
Could be achieved by using lego

We're running Headscale + Tailscale as an ingress router with ports 80 and 443 forwarded to a web-server on the same host.
There is no way to use ports 80 and 443 for the Let's Encrypt http challenge.
Please add the ACME-DNS01 challenge via LEGO.


Getting 2 comp errors

(build based on psych 0.6.3)

remove noteSplash use with modcharting tools, it is currently not working at all, about the first one, can i get a proper screenshot about that line?


chore: add CODEOWNERS file

add codeowners from Che team
https://github.com/eclipse/che/issues/22188

@mkuznyetsov signoff is missing in your commit, please check the failed GH action.


How do I listen to events?

I'm pretty confused. I'm using Rails and I've mounted the bot in my routes.rb file.
But I don't really understand how I set everything up to receive callbacks? For example, I want to receive referral callbacks.
How do I do that? I've got this Listener class in app/bot but how does that even get called?
Any thoughts/insight would be great. Thanks so much.

From the README: https://github.com/jgorset/facebook-messenger#usage
# bot.rb
require 'facebook/messenger'

include Facebook::Messenger

Bot.on :message do |message|
  message.id          # => 'mid.1457764197618:41d102a3e1ae206a38'
  message.sender      # => { 'id' => '1008372609250235' }
  message.seq         # => 73
  message.sent_at     # => 2016-04-22 21:30:36 +0200
  message.text        # => 'Hello, bot!'
  message.attachments # => [ { 'type' => 'image', 'payload' => { 'url' => 'https://www.example.com/1.jpg' } } ]

  message.reply(text: 'Hello, human!')
end

You would put the above code in some file, perhaps in lib/facebook_messenger_listener.rb and make sure that your Rails application loads that file. You would do that by calling require 'facebook_messenger_listener', probably in your application.rb file.
And you've also mounted this facebook_messenger engine in your routes file:
# config/routes.rb
Rails.application.routes.draw do
  # ...
  mount Facebook::Messenger::Server, at: 'bot'
end

With those two things setup, it will all work together. The requests coming into /bot (according to your routes.rb file) will get passed along to your listener code, lib/facebook_messenger_listener.rb.
That's it.

Events like feed webhook are redirect to the Bot.on :postback listener to? I'm a little confused about how to use the gem for page webhooks.
Thanks.

No, the feed webhook is NOT handled by this gem at all. This gem handles Facebook Messenger webhooks only. You can see the webhooks that this gem can handle by looking here: https://github.com/jgorset/facebook-messenger/blob/master/lib/facebook/messenger/incoming.rb#L23-L35
      #
      # @return [Hash] Hash containing facebook messenger events and its event
      #   handler classes.
      EVENTS = {
        'message' => Message,
        'delivery' => Delivery,
        'postback' => Postback,
        'optin' => Optin,
        'read' => Read,
        'account_linking' => AccountLinking,
        'referral' => Referral,
        'message_echo' => MessageEcho,
        'message_request' => MessageRequest,
        'payment' => Payment,
        'policy_enforcement' => PolicyEnforcement
      }.freeze

So the only way to handle this two webhooks is not using this gem or there is another way to inject a function to the bot callback for hadle the feed webhook?

@carlosfernandes I suppose you could fork this gem and add the code that may be able to handle that webhook. You can look at the other webhooks in this repository to see how you'd do that (creating the right Incoming class, etc). Or, perhaps there is another gem out there you could use.
This gem is only for facebook messenger, not all facebook page stuff. So it's not a relevant thing to add to it presently. But you can do whatever you want to a forked version of the gem, but you'd have to maintain that yourself, obviously.


OpenStack Swift SDK changed from "pkgcloud" to Trendyol's own OpenStack Swift SDK

Hey, I just made a Pull Request!
This Pull Request fixes the issue #4995. We changed the OpenStack Swift SDK from the unmaintained pkgcloud to the OpenStack Swift SDK we wrote and maintained. New mock created for this SDK and all tests are passed successfully.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Nice! You have a lockfile conflict now though; you may want to rebase on latest master, checkout that particular file again to the latest version before your changes, and then rerun yarn install again

any update @freben ?

Hi!
There's currently build failures complaining about types and the yarn.lock diff is extremely big. Perhaps some leftovers during development perhaps?

@mertcb We've been hesitant to go forward since it still doesn't build and the yarn.lock situation hasn't been solved.
I noticed that I had push rights to the remote branch, so I took the liberty of rebasing your work on latest master and resetting yarn.lock to only the changes that your specific branch wants to apply. For future reference, when you get into lockfile conflicts like this, it is near to impossible to use the "merge master into my branch" strategy. You'll need to rebase on master, then restore the lockfile entirely to its master state, and then run yarn install again. This applies your intended delta and nothing else.
Let's see what CI thinks about it now.
When running it I saw a warning that I hand't seen before:
warning workspace-aggregator-209c5c12-d4fb-4884-8cbd-8a36af668d14 > @backstage/techdocs-common > @trendyol-js/openstack-swift-sdk > axios-cached-dns-resolve > babel-polyfill ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

This may not be critical since it's a polyfill, but maybe there's something we can do about that? Maybe there's a newer version of axios-cached-dns-resolve to depend on or similar

Yeah OK, so now it builds right. Still needs a full review, let's get that going


[Feature Request]: Configure path for `.chroma/index' for DuckDB when used without persistence

Describe the problem
I'm running an app on AWS lambda with chroma and want to use DuckDB without persistence. Lambda does not allow writes to any directory other than /tmp. Failure stacktrace below.
[ERROR]	2023-05-07T14:21:19.196Z	f701e6be-197b-4134-91df-e64c75502077	Exception in 'http' protocol.
Traceback (most recent call last):
  File "/tmp/sls-py-req/mangum/protocols/http.py", line 97, in run
    await app(self.scope, self.receive, self.send)
  File "/tmp/sls-py-req/fastapi/applications.py", line 270, in __call__
    await super().__call__(scope, receive, send)
  File "/tmp/sls-py-req/starlette/applications.py", line 124, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/tmp/sls-py-req/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/tmp/sls-py-req/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/tmp/sls-py-req/starlette/middleware/exceptions.py", line 75, in __call__
    raise exc
  File "/tmp/sls-py-req/starlette/middleware/exceptions.py", line 64, in __call__
    await self.app(scope, receive, sender)
  File "/tmp/sls-py-req/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "/tmp/sls-py-req/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "/tmp/sls-py-req/starlette/routing.py", line 680, in __call__
    await route.handle(scope, receive, send)
  File "/tmp/sls-py-req/starlette/routing.py", line 275, in handle
    await self.app(scope, receive, send)
  File "/tmp/sls-py-req/starlette/routing.py", line 65, in app
    response = await func(request)
  File "/tmp/sls-py-req/fastapi/routing.py", line 231, in app
    raw_response = await run_endpoint_function(
  File "/tmp/sls-py-req/fastapi/routing.py", line 162, in run_endpoint_function
    return await run_in_threadpool(dependant.call, **values)
  File "/tmp/sls-py-req/starlette/concurrency.py", line 41, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
  File "/tmp/sls-py-req/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/tmp/sls-py-req/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/tmp/sls-py-req/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/var/task/src/main.py", line 69, in comprehendPolicy
    index = getQueryIndex(saveSiteText(policy.policy_link))
  File "/var/task/src/main.py", line 58, in getQueryIndex
    return VectorstoreIndexCreator().from_loaders([loader])
  File "/tmp/sls-py-req/langchain/indexes/vectorstore.py", line 73, in from_loaders
    return self.from_documents(docs)
  File "/tmp/sls-py-req/langchain/indexes/vectorstore.py", line 78, in from_documents
    vectorstore = self.vectorstore_cls.from_documents(
  File "/tmp/sls-py-req/langchain/vectorstores/chroma.py", line 412, in from_documents
    return cls.from_texts(
  File "/tmp/sls-py-req/langchain/vectorstores/chroma.py", line 380, in from_texts
    chroma_collection.add_texts(texts=texts, metadatas=metadatas, ids=ids)
  File "/tmp/sls-py-req/langchain/vectorstores/chroma.py", line 159, in add_texts
    self._collection.add(
  File "/tmp/sls-py-req/chromadb/api/models/Collection.py", line 111, in add
    self._client._add(ids, self.name, embeddings, metadatas, documents, increment_index)
  File "/tmp/sls-py-req/chromadb/api/local.py", line 140, in _add
    self._db.add_incremental(collection_uuid, added_uuids, embeddings)
  File "/tmp/sls-py-req/chromadb/db/clickhouse.py", line 542, in add_incremental
    index.add(uuids, embeddings)
  File "/tmp/sls-py-req/chromadb/db/index/hnswlib.py", line 124, in add
    self._init_index(dim)
  File "/tmp/sls-py-req/chromadb/db/index/hnswlib.py", line 107, in _init_index
    self._save()
  File "/tmp/sls-py-req/chromadb/db/index/hnswlib.py", line 178, in _save
    os.makedirs(f"{self._save_folder}")
  File "/var/lang/lib/python3.8/os.py", line 213, in makedirs
    makedirs(head, exist_ok=exist_ok)
  File "/var/lang/lib/python3.8/os.py", line 223, in makedirs
    mkdir(name, mode)
OSError: [Errno 30] Read-only file system: '.chroma'

Describe the proposed solution
Could we get a way to specify the base directory path to create .chroma in?
Alternatives considered
I've switched to using chroma with persistence (specifying persist_directory as /tmp) to avoid the .chroma creation. I'm able to use the lambda now. But, I don't need persistence for my case and this extra I/O might be an overhead.
Importance
would make my life easier
Additional Information
No response

Completed with Chroma 0.4 - we dropped duckdb

How did you solve this issue?

@jeffchuber  How did you solve this issue?


Lolodi/using pipes

Switching back to using pipes.
This should get rid of the XHR errors and make it easier to re-implement proper progress reporting going forward.

Could you please rebase this PR on the latest commit in this repo? It seems that multiple changes were actually taken care of in the previous PR, and seeing only the latest ones would help reviewing.

Could you please rebase this PR on the latest commit in this repo? It seems that multiple changes were actually taken care of in the previous PR, and seeing only the latest ones would help reviewing.

Fixed that :)


throw error if weights < 0 earlier

https://github.com/raybellwaves/xskillscore/blob/c611d7bd722d4f06a8426de3a533cdbc63e234c4/xskillscore/core/deterministic.py#L41L44
via https://github.com/raybellwaves/xskillscore/pull/28#discussion_r338361930
Text: Should this check happen before weights = weights / weights.max()?

Addressed in #31.


NPE in Gradle 4.0 RC2 for ./gradlew clean testRelease

Testing an Android project with ./gradlew clean testRelease works when using Gradle 4.0 milestone 1. It fails with milestone 2 and RC 2.
Expected Behavior
Tests are executed, build completes with success.
Current Behavior
The build fails with the following error message:
:BatteryGauge:testReleaseUnitTest FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':BatteryGauge:testReleaseUnitTest'.
> java.lang.NullPointerException (no error message)

Steps to Reproduce (for bugs)
This issue can be reproduced with the following sample project: https://github.com/markuspfeiffer/battery-gauge-android
Running a ./gradlew clean testRelease in the projects root directory should trigger the issue (clean is not necessary to trigger the bug). You can change commits to test with 4.0 milestone 1, milestone 2 and RC 2. The build should fail with all versions, except milestone 1.
A regular build (./gradlew assembleRelease) works as expected with all versions.
Your Environment
https://scans.gradle.com/s/5jm46bzah73tu

Great, after searching high and low for this issue I seem to have missed the obvious place. Probably a duplicate of #2266.


Import OpenAPI v2.0 command

[x] import openapi commad
[x] unittests
[x] integration tests
[x] Documentation in README.md
[x] When --service is not given, create new service
[x] OpenAPI spec can be a file or url
[x] OpenAPI spec can be read from stdin
[x] handle OpenAPI 2.0 parsing/validation errors

Fixes https://github.com/3scale/3scale_toolbox/issues/38

I think this might be the point to start thinking about a dry-run mode. Running potentially huge import with no option to roll back could have a devastating impact on someone's portal.

A couple of questions:

Dry-run mode for this command or for any command doing not read-only operations on remotes?
For the specific case of importing OpenAPI spec case, what strategy do you propose for the implementation? On dry run, mocking 3scale client?

Finished all remaining tasks, PR ready to be reviewed @mikz

@eguzki I think dry-run just for this command would be enough. Of course, it would be cool to have it in the others too, but not necessary I'd say.
Regarding mocking the client: I'm not sure if you can mock the client (or you can stub just POST/PUT/DELETE operations). I think the dry mode could be "read only mode". Just read what is the current state and print out the plan (... to be deleted, ... to be changed from .. to ...).

Thanks for the good feedback on relevant issues! The show must go on

Verified the patterns in the spec match what mapping rules can match
Update service from system_name. If it does not exist, create it first. system_name can be passed as option parameter and defaults to info.title from openapi spec.
All existing mapping rules are deleted before importing new API definition. Methods left untouched if exist.

rebased to current master, since it diverged too much from branch base


Create another channel

Hey,
I have used your staff chat and made it an admin chat.
I also would like a helpers chat, and i wonderd if there maybe was something possible with this?
To change some settings to have two of the same plugin running, (but one for helpers)

There is currently no support for multiple channels, and there probably won't be. I'm personally not a fan of staff role-specific channels because it seems counter-productive to communication.
There's also no way to run two separate instances of this plugin (that is generally not supported by any plugin).


Create alhikmah-school.txt

Mail and web domain is: alhikmah-school.com
The page which contains  information about long-term programming courses (in Arabic language):
https://alhikmah-school.com/علوم-الكمبيوتر/

@hatemdeeb I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host alhikmah-school.al not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Create a script to add blank pages to PDFs in batches

Create a script to add blank pages to PDFs in batches

I created it yesterday, just need to polish it and do a PR

Waiting for PR review


code-stylecheck: Allow whitespace in index operator

How are you using the lua-language-server?
NeoVim
Which OS are you using?
Windows WSL
What is the issue affecting?
Diagnostics/Syntax Checking, Formatting
Expected Behaviour
Don't provide warning for whitespace between arithmetic operators inside table index operators?

I think allowing the whitespace is more readable.
Actual Behaviour
Diagnostic messages provide warning for this style.
Reproduction steps
Basic snippet that contains the style error on line 4.
local list = {}
local values = { 1, 2, 3, 4, 5, 6 }
for _, n in ipairs(values) do
  list[#list + 1] = n
end

Additional Notes
I don't know if the same formatting rules are allowed by lua_language_server but Stylua adds whitespace between arithmetic operators: 1+2 -> 1 + 2. This automatically applies to an arithmetic expression inside index operators.
Log File
No response

@CppCXY

the default rule for space is keep at least one whitespace.
maybe you set this option table_append_expression_no_space=true.
if you are not using formatting function on sumneko ls, it is best not to open the format check

Formatting configuration is very close to stylua but perhaps not exact,
I use it as a last pass before CI linting.
However, I did have table_append_expression_no_space=true in .editorconfig and overlooked it.
Glad it's an easy fix, thanks for you time!


powertoy run 软件美化 |# Powertoy run software beautification

Description of the new feature / enhancement
我希望能够设置powerrun的外观，让它像wox软件的外观一样 |# I want to be able to change the appearance of the powerrun, make it like the appearance of the wox software.
Scenario when this would be used?
当前的软件外观虽然与微软的风格统一，但是不够好看，搜索框太大了，也没有透明化磨砂效果|#The appearance of the current software although the style is unified with Microsoft, but not good-looking, search box is too big, no transparent frosted effect.
Supporting information
No response

/dup #4794


Create Travis build

Active Admin uses Rspec, minitest, and cucumber for their testing (testing is done with bundle exec rake. Rspec was set up correctly, but no support/hooks.rb file was found to add hook (per https://github.com/applandinc/appmap-ruby#cucumber). No test/test_helper.rb exists to include require appmap/minitest. Overall, generates 1300~ appmaps with only 50~ empty.


Support in-database configuration

Summary
Adds a flag to support in-database configuration through the CONFIG_USE_DB environment variable. If this is true, the configuration file will not be created if it does not exist. It supports using the custom MM_SQLSETTINGS_DATASOURCE if that exists.
On new deployments with CONFIG_USE_DB enabled, none of the defaults written into the configuration file are created. Further, it assumes existing installations migrate their configuration over before enabling CONFIG_USE_DB as described in the documentation

Hello @paddatrapper,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Any update here?

@paddatrapper Sorry for missing your contribution until now.
We are in fact making some changes to the Mattermost Docker repository, and moving to a new project available at https://github.com/mattermost/docker. You can find additional context behind this move here: https://github.com/mattermost/mattermost-docker/issues/548
With that said, would you be open to contributing your changes to the new repository at mattermost/docker instead, and we can have your changes reviewed?
Sorry for additional work for you. Alternatively we can also open an issue in mattermost/docker to have your changes here migrated to the new repository.

There is no entrypoint or docker image builds in https://github.com/mattermost/docker... So this patch will not fit there. It isn't clear where those images are built from. According to Docker Hub, it is here, but that has none of the config creation logic, so it appears that the new images do not create any config?

@paddatrapper the Mattermost binary itself creates a configuration or reads in an existing one. In fact the https://github.com/mattermost/docker setup supports configuration in database. Just export MM_CONFIG=${MM_SQLSETTINGS_DATASOURCE} in the enviromnent variables. There is no need to override the entrypoint.

@mrckndt so the new images do not require this patch?

No, and this wasn't needed here too. It should have work by exporting MM_CONFIG with the datasource too.

No, and this wasn't needed here too. It should have work by exporting MM_CONFIG with the datasource too.

From experience, it did not work here. That attempted to create the config file the datasource as the filepath, inevitably failing


TextTheme not supported

Triggers an error:
file:///[...]/pdf-3.11.0/lib/src/widgets/text_style.dart:129:16
inherit || fontNormal != null```

Upon checking a few styles they return null values

This error originates from the underlying pdf package.
Do you have a minimal way of reproducing the issue, e.g. a Text Widget configuration that will always produce the error?
Also could you please add your flutter doctor -v output here :)

I just stumbled upon this error as well when fixing another issue related to fonts.  In my specific use case, setting inherit to true solved the issue for me and didn't introduce any side effects (at least not that I'm aware of).
To resolve this issue it would be crucial that you add a concrete example of how you initialize your TextTheme and how you pass it into your Text widget.

thank you, this seems to have worked as far as the original error above is concerned!
The specific project I am working on then hit a new error which I'm not investigating:
RangeError: Offset is outside the bounds of the DataView
dart-sdk/lib/_internal/js_dev_runtime/private/native_typed_data.dart 453:53  [_getInt16]


Issue keras.utils.split_dataset

The keras.utils.split_dataset returns _PrefetchDataset, thus unable to pass to torch.utils.data.TensorDataset API.
!pip install keras-core -q
import os
os.environ["KERAS_BACKEND"] = "torch"

import keras_core as keras
(x_train, y_train), held_out = keras.datasets.cifar10.load_data()
test_set, val_set = keras.utils.split_dataset(held_out, left_size=0.2)
test_set

<_PrefetchDataset element_spec=(TensorSpec(shape=(32, 32, 3), dtype=tf.uint8, name=None), TensorSpec(shape=(1,), dtype=tf.uint8, name=None))>

thus unable to pass to torch.utils.data.TensorDataset API.

Can you expand on this? What's this API and why can it not use a prefetched dataset?
The reason we are prefetching the datasets is that it represents a huge potential performance issue, and most users forget to do it themselves after getting the dataset.

Thanks for the prompt response.

Can you expand on this?

I need to build a torch data loader, that's why I need to use torch.utils.data.TensorDataset API.

The reason we are prefetching the datasets is that it represents a huge potential performance issue, and most users forget to do it themselves after getting the dataset.

Agreed. But what if I don't have Tensorflow installed or not using it (using torch or jax backend instead)? This split API has used tf functions.

8ackground:  I am translating a starter code written in a torch, source. The provider will host a Kaggle competition. But for some reason, they informed that the submission will be valid if the data loader and model are written in torch code, source. Now, I am trying to translate their starter torch code the same as possible with Keras-core (previously done with tf. keras) with torch backed.

I need to build a torch data loader

The simplest way to get a torch data loader from a tf.data dataset is likely to write a torch Dataset subclass that yields samples from the tf.data dataset in __getitem__.
Only accepting submissions in PyTorch seems odd to me -- tf.data is significantly faster and safer (no Python multiprocessing, no random segfaults), as well as portable (you can run in a Python-less environment). Plus, all production-grade LLMs are written in JAX these days (e.g. those from Google, DeepMind, Cohere, Anthropic, Apple -- meanwhile OpenAI uses its own custom CUDA stack). This is unserious.

The simplest way to get a torch data loader from a tf.data dataset is likely to write a torch Dataset subclass that yields samples from the tf.data dataset in getitem

My goal was to use same-level API if possible across the reimplementation notebook. For example,
in torch: torch.utils.data.random_split and
use tf.keras : tf.keras.utils.split_dataset

Only accepting submissions in PyTorch seems odd to me

This is uncommon in Kaggle competition. Only a few competitions make such requirements. For example, this google-asl competition asks to submit in tflite format regardless of the framework people use.
But now I have reimplemented the official torch starter with Keras-core with torch backend. Here is that updated notebook. Their main concern (unlearning method) is considered in this notebook.

The competition is LLM related

I think this competition is CV related. Details.

Any thoughts on the following cases? Now, I think, if I use the torch backend, I can use torch.random_split and keras.split_dataset for the tf backend. Not sure if there's anything in jax API. But keras.utils.split_dataset API could be general, like model_selection.train_test_split

what if I don't have Tensorflow installed or not using it (using torch or jax backend instead)? This split API has used tf functions.

Any thoughts on the following cases? Now, I think, if I use the torch backend, I can use torch.random_split and keras.split_dataset for the tf backend. Not sure if there's anything in jax API.

For simplicity, perhaps you can stick to using torch data APIs only -- a torch DataLoader should work with a Keras model with any backend.
JAX does not have its own data loading API (JAX users canonically use tf.data). And Keras is intended to be agnostic to what data loading API you use.

But keras.utils.split_dataset API could be general, like model_selection.train_test_split

General as is, able to return either a tf.data Dataset or a torch DataLoader? I think we could do, that by adding a return type argument (defaulting to tf.data).

I think we could do that, by adding a return type argument (defaulting to tf.data).

That would be fantastic.

General as is, able to return either a tf.data Dataset or a torch DataLoader? I think we could do that, by adding a return type argument (defaulting to tf.data).

@fchollet This is I actually added in my last PR for split dataset, If needed I can add it again. What do you think ?


Move from Travis to Github actions

Travis recently changed plans pricing which makes it impossible to continue Open Source on travis. We're moving to github actions, and also adding windows support !

#10


navigate to source for Octokit.net not working

I'm testing out the latest build which has the Navigate to Source feature.
https://ci.appveyor.com/project/dungpa/visualfsharppowertools/build/1.8.0-a1503071249/artifacts
I created a new project with this NuGet packages.config:
<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Octokit" version="0.7.2" targetFramework="net45" />
  <package id="SourceLink.Core" version="0.5.0-ci1411242108" targetFramework="net45" />
</packages>

The Library1.fs:
module Test

let md5 = SourceLink.Crypto.hashMD5 "a.txt"

// https://github.com/octokit/octokit.net/
let dt = Octokit.Helpers.UnixTimestampExtensions.FromUnixTime<PHONE_NUMBER>L
let github = Octokit.GitHubClient(Octokit.ProductHeaderValue "MyAmazingApp")
let a = github.Activity.Events.GetAll()
()

It correctly navigates to hashMD5 implementation which is awesome to see!
It does not work when I try to navigate to FromUnixTime or GitHubClient constructor or GetAll. It doesn't seem to be working for the Octokit.net library. It is source indexed.

Is there any error message being shown on the status bar? Or does VS just silently do nothing?

If the metadata option is enabled, it goes to the metadata. If the metadata option is disabled, the status bar shows:

I am able to start debugging and step into FromUnixTime so I know it is source indexed correctly.

This issue is not worth fixing unless SourceLink has better support for symbols at design time.


Computational fluid dynamics (CFD)

Applications

Ansys Fluent
STAR-CCM+
OpenFoam
OpenVSP
SOLIDWORKS Flow Simulation
SimScale

Running CFD on AWS ParallelCluster at Scale

https://catalog.us-east-1.prod.workshops.aws/workshops/21c996a7-8ec9-42a5-9fd6-00949d151bc2/en-US/06-openfoam

Computational fluid dynamics (CFD) with Machine Learning

https://www.amazon.com/dp/B0CZF4YN31

Added by

https://github.com/hongbo-miao/hongbomiao.com/pull/16624
https://github.com/hongbo-miao/hongbomiao.com/pull/16637


Fix /etc/mtab symlink

fixes https://github.com/gotoz/runq/issues/24

damn I thought it worked - but I was wrong.


Accesss to WiFi client (MEGH-2237)

It would be useful to have easy access to the wifi client so that other protocols might be used such as UDP or even another MQTT client.

Sorry Piyush,
I envisage using the wifi connection (once the device has completed provisioning) to provide, for example an additional MQTT client so that a device can continue to log and report data locally while still maintaining a Rainmaker node for remote monitoring and control. So rather than replacing the existing RM MQTT and wifi client connection, I would look fo a safe way of adding an additional MQTT client.


Add level and XP difference fields in skill calculator

I often have to calculate the difference in XP manually when trying to perform more complex, situational calculations myself. I noticed there were similar PR's a while back such as this one: #9283
which was a response to #9260 but from reading the replies it was never merged and didn't have functionality to edit the fields as you can the other fields.
Difference changes update the target, and vice versa. Maybe a more appropriate name is due rather than 'Level difference' and 'Experience difference' but I just called it as is. Others I've seen were 'Remaining levels' and 'Remaining Experience' which may also be suitable.

I've never understood why this is useful. If you know you want +x levels or +y experience, just add it to the current experience? It doesn't seem to me like it would be worth the loss in screen space since the panel is already fairly packed as it is.

For me it's more to do with the automatic difference calculation that happens between the current and target XP. Which I sometimes do need for other manual calculations, and for me personally just feels like one of those things I should have automatically. I've asked a few others in my cc about it, and there are some in similar scenarios and of course some who would never have had use for this. Also the only reason it's possible to input into the difference fields is to complement how the other fields work, so it feels more 'complete'.
All in all I can understand why some perceive it as a useless feature, and I am open to opinions. It's a small feature in the end that could maybe be implemented another way or not at all.
Thanks for the response.

If we are to merge it (which I don't know that we're interested in adding this feature--some discussion may be needed to get a consensus on this?) we would want the remaining XP/level fields to be disabled per discussion in #9283.

Remaining XP was added in #11509


Question Regarding door/Window Sensors

I have a home server running ubuntu and homebridge. It works flawlessly! I currently have homebridge linked to my nests, and my harmony hub and my smarthings hub V2. (homebridge-legacy-plugins....homebridge-nest....homebridge-harmonyhub) also running ("hello homebridge" and "JSON api"  smart apps on smarthings) I am currently able to use siri to control my nests, harmony hub and wave lights. I was wondering if there was a way to support my Z-wave Door/Window Sensors in homekit? I do not see them pop up as a device. I understand there are three options in home kit for these sensors ("door" "window" and "contact sensor") Is there any homebridge-plugin that will allow home kit to see my door/window sensors in homekit?

I just uploaded the change for that to my platform plugin: https://github.com/pdlove/homebridge-smartthings/
It still needs more testing before I make a release of it, but I'm expanding all of the smartthings types I can.

pdlove, you are a god! I will test this out as soon as I get home. Good luck to your upcoming npm release! If you need help beta testing anything definitely PM me and I can help!

Quick warning... You MUST install my JSON smart app as opposed to the old one. Mine is much more complete and is not compatible.

That makes complete sense! (Looking at the old JSON API code it only supports switches and hues) I'll be testing you JSON-COMPLETE-API tonight...Thanks again!

That makes complete sense! (Looking at the old JSON API code it only supports switches and hues) I'll be testing your JSON-COMPLETE-API tonight...Thanks again!

Any updates on this? I am in the same situation- want to monitor and get status updates on zwave door sensors that I have running with Openremote controller.
Lights and switches seems to work great with homebridge and Home app


how to install additional apps?

how can I install additional apps? Like (mc)mindnight commander?

That is a hypervisor for docker. So everything needs run inside a container.

how can I do that?

The easiest way to do that is install Portainer via the Hass.io community add-ons and get yourself familiar with Docker. (https://training.play-with-docker.com/ops-stage1/)
Maybe there is already a Docker image for your app, otherwise you can create your own.


Installing docker on openshift worker node makes the drivers unusable

On worker01, Openshift 4 node, running podman, I installed docker for testing purposes. Now I cannot run the CSI driver on  this node:
[root@worker01 ibm-spectrum-scale-csi-driver]# oc get pods
NAME                               READY   STATUS             RESTARTS   AGE
csi-spectrum-scale-attacher-0      1/1     Running            0          8m5s
csi-spectrum-scale-m4rfr           2/2     Running            0          8m4s
csi-spectrum-scale-nfhrm           0/2     ImagePullBackOff   4          8m4s
csi-spectrum-scale-provisioner-0   1/1     Running            0          8m4s
jenkins-1-6xrvl                    1/1     Running            2          9d
jupyter-f7779d9-8m2pf              1/1     Running            2          9d

Failed to pull image "localhost/csi-spectrum-scale:v0.9.0": rpc error: code = Unknown desc = pinging docker registry returned: error pinging registry localhost, response code 503 (Service Unavailable)

I think this is because I have docker now on the node. You should ignore docker as it is not a default container utility on openshift 4 (it's podman).
Anyway, I removed the docker.
yum remove docker

But the pod is not being updated anymore.
[root@worker01 ibm-spectrum-scale-csi-driver]# oc get pods
NAME                               READY   STATUS             RESTARTS   AGE
csi-spectrum-scale-attacher-0      1/1     Running            0          11m
csi-spectrum-scale-m4rfr           2/2     Running            0          11m
csi-spectrum-scale-nfhrm           0/2     ImagePullBackOff   5          11m
csi-spectrum-scale-provisioner-0   1/1     Running            0          11m
jenkins-1-6xrvl                    1/1     Running            2          9d
jupyter-f7779d9-8m2pf              1/1     Running            2          9d

I destroyed (and waited a couple of seconds till pods disappear) and deployed the driver again.
[root@worker01 ibm-spectrum-scale-csi-driver]# deploy/destroy.sh
[root@worker01 ibm-spectrum-scale-csi-driver]# deploy/create.sh

[root@worker01 ibm-spectrum-scale-csi-driver]# oc get pods -owide
NAME                               READY   STATUS             RESTARTS   AGE     IP             NODE                      NOMINATED NODE   READINESS GATES
csi-spectrum-scale-attacher-0      1/1     Running            1          7m22s   <IP_ADDRESS>   worker01.ocp4.scale.com   <none>           <none>
csi-spectrum-scale-d9w8p           0/2     ImagePullBackOff   4          7m21s   <IP_ADDRESS>   worker01.ocp4.scale.com   <none>           <none>
csi-spectrum-scale-mgplh           2/2     Running            0          7m21s   <IP_ADDRESS>   worker02.ocp4.scale.com   <none>           <none>
csi-spectrum-scale-provisioner-0   1/1     Running            0          7m21s   <IP_ADDRESS>   worker01.ocp4.scale.com   <none>           <none>
jenkins-1-6xrvl                    1/1     Running            2          9d      <IP_ADDRESS>   worker01.ocp4.scale.com   <none>           <none>
jupyter-f7779d9-8m2pf              1/1     Running            2          9d      <IP_ADDRESS>   worker01.ocp4.scale.com   <none>           <none>

Still, no change. I cannot use the driver anymore on my worker01. How to fix it?

What does "podman images | grep spectrum-scale" show?
Was it running on this node before installing docker? Did you have to upload the driver image again after installing docker?

Thanks, Smita. I had missing image in the podman registry on that node. Added it again and the CSI could run properly.


why is ubntu18.4 a requirement as of tf_cc v1.8 ?

hello,
I would like to install the latest versions of tf_cc on ubuntu 16.04,
but have noticed that as of v1.8 the ubuntu 18.04 is required.
( while this is not required by the save versions of tensorflow_"python".
also noticed that the cuda requirement is just 9.2 , which is supported on ubuntu 16.04.
can you please share why ubuntu 18 is required as of tf_cc 1.8 ?
is this a "hard" requirement ?
or simply that tf_cc v1.8 and above were not tested on 16.04 ?
thanks,
Omer.

Only Ubuntu 18.04 is tested. If you manage to get the right versions of required packages and compiler, it may work on Ubuntu 16.04 as well.


cacheDir clears the directory

I use a shared folder for caching, and cacheDir removes all files in the directory!

The cachedDir, is not really supposed to cache the outputted between sessions, its main purpose, is to reduce duplicate processing for common include files. So anytime you rerun the grunt task, it will clear out the cache directory.


Fixes #34 : Shifts more options to bottom sheet

This will be continued in #179. Thanks for this patch.


Async methods aren't really asyncronous

How are the getAsync() methods of the various Request classes supposed to be asynchronous, if they don't return until the http request has finished? The "Async" keyword is quite misleading in such methods.
Wouldn't it be better off to actually make them asynchronous (maybe using ListeningExecutorService)?

Version 2.0.0-RC1 was just released.


Day 449

Good morning! Here's your coding interview problem for today.
This problem was asked by Alibaba.
Given an even number (greater than 2), return two prime numbers whose sum will be equal to the given number.
A solution will always exist. See Goldbach’s conjecture.
Example:
Input: 4
Output: 2 + 2 = 4

If there are more than one solution possible, return the lexicographically smaller solution.
If [a, b] is one solution with a <= b, and [c, d] is another solution with c <= d, then
[a, b] < [c, d]
If a < c OR a==c AND b < d.

Identical to Day 101: https://github.com/vaskoz/dailycodingproblem-go/issues/212


libs/arch_libc:Add kasan protection for memset and other mm api

Summary

libc/machine:Add prefixes to libc functions implemented by arch
kasan does not instrument the assembly function,
so it is checked in advance before calling.
If Kasan is not turned on, the speed and space will
be almost unchanged under compiler optimization.
libs/machine:strnlen need check return
arch_lib.c: close kasan readcheck no return
libc: Modify the check length

Impact
After enabling archlibc, kasan checks will be performed when calling mm api
Testing
None

Sorry @W-M-R: Could you take a look at the build for nucleo-f072rb:nsh, is it failing because of this PR? Thanks!
Configuration/Tool: nucleo-f072rb/nsh,CONFIG_ARM_TOOLCHAIN_CLANG
/tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: sched/libsched.a(sem_destroy.c.obj): in function `nxsem_destroy':
sem_destroy.c:(.text.nxsem_destroy+0x24): undefined reference to `__atomic_compare_exchange_2'

https://github.com/NuttX/nuttx/actions/runs/11632461378/job/32395707420#step:7:132

Sorry @W-M-R: Could you take a look at the build for nucleo-f072rb:nsh, is it failing because of this PR? Thanks!
Configuration/Tool: nucleo-f072rb/nsh,CONFIG_ARM_TOOLCHAIN_CLANG
/tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: sched/libsched.a(sem_destroy.c.obj): in function `nxsem_destroy':
sem_destroy.c:(.text.nxsem_destroy+0x24): undefined reference to `__atomic_compare_exchange_2'

https://github.com/NuttX/nuttx/actions/runs/11632461378/job/32395707420#step:7:132

ok，i  will deal with this patch latter

Sorry @W-M-R: Could you take a look at the build for nucleo-f072rb:nsh, is it failing because of this PR? Thanks!
Configuration/Tool: nucleo-f072rb/nsh,CONFIG_ARM_TOOLCHAIN_CLANG
/tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: sched/libsched.a(sem_destroy.c.obj): in function `nxsem_destroy':
sem_destroy.c:(.text.nxsem_destroy+0x24): undefined reference to `__atomic_compare_exchange_2'

https://github.com/NuttX/nuttx/actions/runs/11632461378/job/32395707420#step:7:132

Hi, I have submitted a fix to resolve this issue https://github.com/apache/nuttx/pull/14605.
The problem is that the previously removed macros are brought back, causing arch_atomic.c to fail to compile.

Cool thank you so much! :-)


A simple replacement for "thirst"

Context
Just in case anyone doesn't know, Thirst is a stat that is shown along other stats (only) when a enemy is moused over. It is calculated like this:
int thirst;
if(deaths == 0){
   thirst = kills*100;
}else{
   thirst = (kills*100)/deaths;
}

The stat is formatted like a percentage. (e.g a thirst of 100 is 100%)
Problems with thirst
I think that it might be useful to have stats like thirst to more easily spot cheaters,
but it right now fails at that (probably because it was intended as a joke).

The name "thirst" is not particularly descriptive and quite confusing.
It isn't really a percentage, despite being formatted as such, adding to the confusion.
Because of the condition, a player with 0 deaths is treated the same as one with 1 death.
Limiting the stat to only display for enemies is kind of pointless.

Kills per Life
My idea for a replacement is kills per life, defined like this:
  float kills_per_life = kills/(float)(deaths + 1);

If displayed on both teams, i think it would solve these problems.
Other stats
I know very little about statistics, but i think that if a good enough metric was found, it might make it even faster to find
cheaters in the list. A variant on something like kills/time could make cheaters quickly float to the top of the playerlist. Another idea is player KpL - average KpL, or something like that, which shows outliers over more time, but im just spitballing now.
(Sorry if this was wordy, i tried to follow the template a bit too much i think)

kills per life
This number is the most tangible to users. However, KPL weighs too heavily "against" engineers, snipers, and risk-averse players that take forever to kill.
headshots per life
Cheating snipers may headshot more than legit snipers, but HPL ignores the other classes (such as heavy bots).
player KPL - average KPL
Too complicated and variable. Users can just check the other KPLs to spot the outliers.
kills per minute
Probably the best metric for discovering blatant hackers.

Also, KPM shouldn't be calculated until the player has a certain number of kills (e.g. 6 kills) and a certain amount of server time (e.g. 60 seconds). This keeps the value useful and stable.

characters said per minute / chattiness
Calculated after 1 minute, CSpM would make chatspamming bots obvious, but would also highlight bind users.
I think that theres not much of a problem if these stats are used to order the playerlist rather than mark players as suspicious or as a ruleset feature. My problem is usually finding the newly joined cheater among pepole i know are innocent, so some filters and sorting would go a long way. I might close this one and make a new one for this suggestion (or change this one), because that sounds much more useful than just adding some stats.

Thirst exists as a joke feature. It is not meant to be useful and I do not think it should be replaced or removed since I like the joke.
That being said, additional stats were considered. Stuff like #267. Logs.tf with ss (supplemental stats) should serve as a starting point for determining what should be useful. Overall this will likely have to wait until demo parsing is a thing.

@ClusterConsultant. Here are a few takes on some of the logs.tf stats:

kills,assists/death has the problems when deaths is 0, assists might also be just noise
in this situation. A high KpL would be a better indication of cheating (if they actually are)
than this stat, i'd assume.
damage/minute sounds promising, but might just be the same thing as KpM.
airshots is an intresting idea and might work to find pepole who are using aim assist.

The rest of the stats does not seem that helpful for cheater/bot detection. stats.tf seems to have alot of stats that are great for tracking how different players affect the game but not really for finding cheaters. I think it's important to exclude as many stats unhelpful as possible in order to not make them overwhelming. Maybe less used stats could be hidden, but i doubt that feature would be needed if the right stats are picked in the first place.


Add import implementation into DG

Codecov Report

Merging #269 (48ae475) into master (66fe62b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #269   +/-   ##
=========================================
  Coverage     76.97%   76.97%
  Complexity      944      944
=========================================
  Files           131      131
  Lines          2658     2658
  Branches        334      334
=========================================
  Hits           2046     2046
  Misses          507      507
  Partials        105      105

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Generator should use updated eslintrc

https://gist.github.com/cjus/c01bffb715e6bc4fba1f995c87fae0c0

If above eslintrc is used then the generator will need to add this to package.json
    "eslint-plugin-jasmine": "2.2.0",

This is still missing from package.json
 "eslint-plugin-jasmine": "2.2.0",

So Atom give me errors.


Fix order in which privileges are dropped

See: POS36-C. Observe correct revocation order while relinquishing privileges

Thank you!


Provisioner should persist shoots under a feature flag and not manage runtimes

To consider - could be either done under feature flags
Then consider creating a follow-up for label based approach

part of the implementation #3433
(still missing is flag is not managing)
To consider - could be either done under the labels or feature flags

Duplicate of #250


Errors with CSS grid properties

The older version of libsass reports errors with CSS grid properties

Message:
source/css/scss/modules/_layout.scss
Error: Invalid CSS after "...   \[row1-start": expected expression (e.g. 1px, bold), was '] "fourth fourth fo'
on line 47 of source/css/scss/modules/_layout.scss
>>     [row1-start] "fourth fourth fourth"       [row1-end]
----^

Node-sass has already been updated to newer version of libsass, which now support grid. I confirmed locally that bumping node-sass to ^4.5.0 in gulp-sass fixes this issue.

Remove node_modules and npm install to get the latest node-sass.


3.4.1 Seems to require Java 15, becomes incompatible with lower Java versions

I don't see what in the diff caused the incompatibility https://github.com/jeremymailen/kotlinter-gradle/compare/3.4.0...3.4.1, but when trying to use recent plugin version in an environment with lower java version, it fails with a message similar to:
> Could not resolve all artifacts for configuration ':buildSrc:classpath'.
   > Could not resolve org.jmailen.gradle:kotlinter-gradle:3.4.1.
     Required by:
         project :buildSrc > org.jmailen.kotlinter:org.jmailen.kotlinter.gradle.plugin:3.4.1
      > No matching variant of org.jmailen.gradle:kotlinter-gradle:3.4.1 was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.0' but:
          - Variant 'apiElements' capability org.jmailen.gradle:kotlinter-gradle:3.4.1 declares a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component compatible with Java 15 and the consumer needed a runtime of a component compatible with Java 11
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.0')
          - Variant 'runtimeElements' capability org.jmailen.gradle:kotlinter-gradle:3.4.1 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 15 and the consumer needed a component compatible with Java 11
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '7.0')

The build passes on Java 15. Sample failed run
I'm quite sure that's not an expected behavior change so I'm reporting an issue here.
btw. the new Gradle Toolchains feature might be helpful here https://docs.gradle.org/current/userguide/toolchains.html

Good catch. Definitely not intentional. Bytecode target should be 8. It may indeed be a side effect of upgrading to gradle 7 and not declaring the toolchain?

It may indeed be a side effect of upgrading to gradle 7 and not declaring the toolchain?

I don't think so, there is no default toolchain which would change the compatibility (or at least I'm not aware of such behavior). and btw. they were introduced in Gradle 6.8
My guess would be local environment of the machine which created the release artifact. If I'm not mistaken, by default the jar compatibility depends on the java version that builds it, and Gradle Toolchains only simplify managing that.
I couldn't find the CI run that triggered the release, but I'd first make sure it didn't have Java 15 installed and set as a default.
I don't understand that part of Gradle well enough to understand what precisely happened here and unfortunately I don't have time right now to investigate it more thoroughly, but I can share my config that produces a Java 8 compatible artifact, built with Java 15: https://github.com/usefulness/issuechecker/blob/master/build.gradle#L12

Thank you, this is helpful. I guess now jar compatibility requires more than just bytecode -- declaring which JDK apis are required by the component. Will try to fix tomorrow.

Ok, should be fixed now, give 3.4.2 a try.

Thanks! I can confirm 3.4.2 works on Java 11, and fails on Java 8 👍
You wrote:

1.8 is pretty old and unsupported now.

😬
I'll share that Java 8 seems to be still a standard in Android world 😞 Google announced Android Gradle Plugin 7.0 will require Java 11, but that's still in a distant future (at least half a year before it reaches stable version).
Despite it is possible to build an Android project with latest Java version, I'm quite sure at least half of the Android community still uses Java 8 (I think I saw a poll on reddit, but still, citation needed).
Requiring Java 11, at this moment of AGP release cycle, may be problematic for large number of Android Project which aren't ready for Java update.
(It doesn't affect me personally, but I thought it might be worth sharing)

Yes, you are right of course. I need to be more in tune with Android since most Kotlin users are there -- I'm a server dev!
Let me do another incremental bump back to 8.

Ok, 3.4.3 it is!

Thanks!
I can confirm it works, even on Java 8 🚀


Pandas compat

xref https://github.com/dask/dask/issues/6148

The many partd-related failures are handled in https://github.com/pandas-dev/pandas/pull/33892. I'll push another commit on Monday which should fetch a wheel with the fixes in pandas.

BTW, I think we should maybe rather consider reverting that freq-related change in pandas: https://github.com/pandas-dev/pandas/pull/33815#issuecomment-620820134

FYI: pandas nightly builds have been failing for ~6 days now, so we're still getting the wheel that broke Partd. Fixing that in https://github.com/MacPython/pandas-wheels/pull/84 and in pandas. Once we get a fresh wheel this should be good.

Thanks for the update

Is this good to merge? 🙂

No, n the pandas nightly wheel still isn't building correctly.

Ah ok. Sorry I misread then. Thought the merged PR xref’d above meant this was already fixed.

No worries. https://github.com/pandas-dev/pandas/issues/34114 is the issue to watch on the pandas side.

(partially) fixed the build issue on the pandas side. Lots off new failures though :/

Thanks for always doing this Tom.  I've learned to not think at all about
Pandas/Dask compatibility over the last few years (which has been
glorious), and I realize that that's not an easy task.
On Wed, May 27, 2020 at 12:23 PM Tom Augspurger<EMAIL_ADDRESS>wrote:

(partially) fixed the build issue on the pandas side. Lots off new
failures though :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/6156#issuecomment-634888524, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTD4CXTCC6XVKCPJFC3RTVSDHANCNFSM4MWU3PRQ
.

https://github.com/dask/dask/pull/6429 instead.