text:
Add a "blurb" field to Boards

[ ] Add a blurb field and use for the blurb
[ ] Move description (markdownified) to top of main content area.

@nealbastek Can you explain this one at our call today?

WONTFIX. Mainly because I dont understand what this issue means (and seems like Nigel didn't understand it as well!)

authors: morchickit nickstenning nigelbabu

repo: okfn/foundation


text:
Initital indaba-client

This is the initial version of the indaba client.

👍

source: gharchive/pull-request

authors: dumyan pwalsh

repo: okfn/open-budget-indaba-client

license: MIT

license_type: permissive

license_source: github-api


text:
2.0.2 version in Windows causing errors

I updated to version 2 and is now on all Windows computers error. In this case all is well on the mac.
{
  "scripts": {
     "lint-staged": "lint-staged",
     "eslint:fix": "eslint --fix",
     "stylelint:less": "stylelint --syntax=less",
     "git:add": "git add"
  },
  "lint-staged": {
      "*.@(js|jsx)": [
        "eslint:fix",
        "git:add"
      ],
      "*.less": [
        "stylelint:less"
      ]
  },
  "pre-commit": [
      "lint-staged"
  ],
}

25h25hevents.js:154
      throw er; // Unhandled 'error' event
      ^

Error: spawn npm ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:475:9)
    at process._tickCallback (node.js:389:17)
pre-commit:
pre-commit: We've failed to pass the specified git pre-commit hooks as the `lint-staged`
pre-commit: hook returned an exit code (1). If you're feeling adventurous you can
pre-commit: skip the git pre-commit hooks by adding the following flags to your commit:
pre-commit:
pre-commit:   git commit -n (or --no-verify)
pre-commit:
pre-commit: This is ill-advised since the commit is broken.
pre-commit:

npm 3.6.0/3.9.3, node 5.6.0/6.2.1

Hey! Sorry I don't have windows to test it. I'm happy to accept a PR that fixes it though.

Ok, on the weekend I try to understand what the problem is

@Tom910 can you try this branch out and let me know if it fixes the issue?
https://github.com/okonet/lint-staged/pull/32
Thanks!

I checked it, this error was due child_process library. For Windows calls the wrong way in runScript.js file in 21 line. Read more details here https://github.com/nodejs/node-v0.x-archive/issues/2318. There are 2 ways to solve the problem: to write a crutch for Windows or to use cross-spawn library.

@okonet Yes, to issue #32, this error has been corrected
Thank you!

source: gharchive/issue

repo: okonet/lint-staged

license: mit

license_source: bigquery


text:
Running tasks for *.js [skipped] → No staged files match *.js in commit phase

Running tasks for *.js [skipped] → No staged files match *.js in commit phase
in package.json
  "husky": {
    "hooks": {
      "pre-commit": "bash scripts/pre-commit.sh"
    }
  },
  "lint-staged": {
    "linters": {
      "*.js": [
         "eslint --config eslint-config-react-app --max-warnings 0 --rule 'strict: 0'",
        "prettier --write",
        "git add"
      ],
  },
   ... etc
  }

pre-commit.sh
#!/bin/sh

echo "Starting Jest tests, JS and CSS Linting and Prettier."

if ! lint-staged
then
    echo "Testing or linting failed."
    exit 2
fi

echo "All checks passed."

exit 0

What I do:

change something in code and try to commit changes

git add .
git commit -m "test"

in terminal i see that:

husky > pre-commit (node v12.13.1)
Starting Jest tests, JS and CSS Linting and Prettier.
  ↓ Running tasks for *.js [skipped]
    → No staged files match *.js

But if I use "precommit" : "lint-staged" script after git add .  and before git commitall works fine.
git add .
npm run precommit

> lint-staged
  ✔ Running tasks for *.js  -   all files look correctly now

git commit -m "test"

Please help me) I really don't know what incorrect in my steps

What does the file scripts/pre-commit.sh contain? Please output all the debug logs as specified in the issue template.

@iiroj  I added info in the issue. The main question is why lint-staged doesn`t see any files when I make commit

I understand why it's happened. Because project was moved to a monorepo and paths are incorrect in a pre-commit hook and in the linter((

authors: DariaKalinina iiroj


text:
style: Use dedent for prettier multi-line template literals

This PR uses dedent for beautifying multi-line template literals:
const dedent = require('dedent');
// ...

// Before
console.log(`This is a multi-line
sentence`);

// After
console.log(dedent`
  This is a multi-line
  sentence
`)

Do you mind waiting till I merge https://github.com/okonet/lint-staged/pull/141 and applying those changes again? I just spent an evening merging master into it and I think this PR will intro some conflicts again. 🙄

Sure, no problem.

Invitation to join okonet/lint-staged from okonet

@okonet Thanks!

@sudo-suhas it's a pleasure! 👍 Thanks for accepting. I don't mind more eyes and hands here :)

Do you need help with resolving conflicts in this one?

Nah.. I'll just discard my changes and start over.

@sudo-suhas do you use cmd or powershell on windows? I'm thinking about something to improve our cross-platform compatibility

I actually use cmder. Helps me forget that I am on windows just a little bit 😆

I know this is less important but I figured since the PR was open and changes were simple, would be better to merge it in.

Rebasing and fixing conflicts.

Can this one be finalized, please?

I made a PR to dedent(dmnd/dedent#14) for our requirement but did not get a response yet.

@okonet I am not getting any response for the PR I made to dedent. We have a couple of options:

Don't use dedent for the section where we want some indentation.
Publish the package under a different name and allow for specifying indent.

What do you suggest?

@sudo-suhas can we just skip it for https://github.com/okonet/lint-staged/pull/242/files#diff-3aafb296b115847cd397630c3d4960a7R65 and move along?

Yes @okonet that's what I meant by

Don't use dedent for the section where we want some indentation.

Will rebase and resolve conflicts.

🍾

authors: luftywiranda13 okonet sudo-suhas


text:
⚖ Register Validator:

Network Choice
nemeton-1
Who are you?
KJINC.io, a validator mainly on Cosmos. We are glad to be here.
Currently, we are the validator of Bitcanna, BitSong, Cerberus, Desmos, Ki Chain, Vidulum, Lum Network, Meme Network, Stride, Jackal, welcome to delegate with us.
gentx
{"body":{"messages":[{"@type":"/cosmos.staking.v1beta1.MsgCreateValidator","description":{"moniker":"KJINC.io","identity":"E294DFEB5B016EE2","website":"https://kjinc.io","security_contact":"info@kjinc.io","details":"BLOCKCHAIN INFRASTRUCTURE AND STAKING PARTNER BRING YOUR IDEA TO HIGHER LEVELS WITH KJINC.io"},"commission":{"rate":"0.050000000000000000","max_rate":"0.200000000000000000","max_change_rate":"0.050000000000000000"},"min_self_delegation":"1","delegator_address":"okp41hslxk7km5z6srvmr993hsgcdxnezg8a5jc9gzh","validator_address":"okp4valoper1hslxk7km5z6srvmr993hsgcdxnezg8a58l4puk","pubkey":{"@type":"/cosmos.crypto.ed25519.PubKey","key":"LDShuoqja49vsOlLp1ozs2/pXT8oAhjQsebPfIgMwN4="},"value":{"denom":"uknow","amount":"10000000000"}}],"memo":"dd0c2f0bdd3cf47c69151a072f88c4543bcc5187@172.16.19.26:26656","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[{"public_key":{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A0x9TV651K3bpkXWrxLpUf9VzzibzDTzkr7g7nO0CV6c"},"mode_info":{"single":{"mode":"SIGN_MODE_DIRECT"}},"sequence":"0"}],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""},"tip":null},"signatures":["YvYe4zAnvZ+4EyJwEFAEX1V47oop/lOxNIi6qvhXVb4Ag5CISchMvVz2HNAgp4AEPwXM+CV0DQQaipPxScY7Tg=="]}

😉 Here is the corresponding PR: https://github.com/okp4/networks/pull/291

authors: bot-anik kjincgroup


text:
Feature Request - CheckDB Snapshots in other location

The use case is that in a Data drive with few space available, as CHECKDB operations create a snapshot of the databases in the drive and checks that instead, the problem is that there if there is not enough space available in the drive for the snapshot to generate operation will fail.
Could it be possible to add to generate DB snapshot manually in other location and perform the operation over it and then delete it as a feature to scripts? Maybe a param @SnapshotLocation to specify it needs to create it in other location and then execute the command.

This is a good idea. The risk is just that if the job is getting aborted for some reason, then the snapshot will not be deleted.
The best would be if Microsoft could add an option to the CHECKDB command, where the snapshots should be created. Please vote for this idea on UserVoice.
https://feedback.azure.com/forums/908035-sql-server/suggestions/36206044-option-to-specify-a-location-for-the-dbcc-checkdb
Then I would also add support for it in my scripts.

authors: RGarciaSQ olahallengren


text:
Editing a gear preset sometimes removes item from ammo slot in that preset

I've noticed my blessing being removed from the ammo slot of the preset, when editing the preset. So for example I have rada's blessing 4 in the gear preset -> edit the preset to change the item in the helm slot -> rada's blessing 4 is no longer in that preset. I've only tried this in the preset for "Wildy".

Fixed in next update

authors: Usvaaa gc

repo: oldschoolgg/oldschoolbot


text:
Add Sandworms to Buyables

Adds sandworms to buyables (at 200gp ea as a filler given I don't know how you want your scaling on prices v. in game osrs prices). Now that food has a purpose it seems like fishing anglers might be an activity players would like to engage in.

[x] I have not tested all my changes thoroughly.

This seems useless if you're not also adding anglers.

Anglers should already be fishable

You need kourend favour to fish anglers, which we plan to add, therefore we'll hold off on this until kourend favor is added - as we want them to be locked behind the requirement like ingame.

Ok I thought kourned things were just being quest point locked (like how Anglers are currently coded) my b.

authors: gc osrsolympus


text:
[Snyk] Upgrade com.fasterxml.jackson.core:jackson-databind from 2.16.1 to 2.17.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade com.fasterxml.jackson.core:jackson-databind from 2.16.1 to 2.17.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 24 days ago, on 2024-03-12.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.63%. Comparing base (2ddab2c) to head (0ae4424).
Report is 6 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #23      +/-   ##
============================================
- Coverage     41.80%   41.63%   -0.17%
+ Complexity       88       87       -1
============================================
  Files            40       40
  Lines           610      610
  Branches         39       39
============================================
- Hits            255      254       -1
- Misses          345      346       +1
  Partials         10       10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
Are Dataview inline queries supported?

Hi!
I've found this awesome plugin less than a week ago, and I love it. Congrats on your work, and thanks for sharing it.
I'm experiencing an issue, but I'm not sure if this is a feature request or a bug report.
The default Dataview queries works like a charm, but when I try to use an inline query, it is rendered as a monospaced text instead of evaluating the query. I'm currently experiencing this when trying to access the note metadata with both `=this.url` and `= this.url`
This is how it's rendered in Obsidian

This is the HTML output:

Kill Process Running on a Specific Port in Linux

From = this.url

Excerpt

Want to kill the processes running on specific ports? No need to know the process ID or name. You can terminate a process based on the port number it is using.

I'm aware of that the DataviewJS is not supported, and I reach out to their web to check if this functionality is part of it. They distinguish between Dataview inline queries and DataviewJS inline queries, so that makes me think that's not the case.
As pointed out, I'm not sure if this is a bug or a feature request, but I thought it was worth bringing it to your attention.
Kudos to you!

Thank you for the kind words 😄
I wasn't aware of this dataview feature, thanks for brining it to my attention!
I thought it would be simple to implement, but turns out rendering an inline query is not supported by the Dataview Plugin API, which is what the digital garden plugin uses behind the scenes.
So unfourtunately it currently isn't possible to support. If a future version of dataview implements support for rendering inline queries via the plugin api, I'll be sure to add it to the plugin.

Thanks for the quick response!
I got curious and went in to take a peek at the Dataview API. I'm aware that I don't know how your plugin implementation works, and that I may be talking nonsense, but... Is it possible that this functionality is exposed as evaluate?

Disclaimer: I do not have any expertise with typescript. But now I can't help but try a solution :sweat_smile:  – would something like this make any sense?
    async convertInlineDataViews(text: string, path: string): Promise<string> {
        let replacedText = text;
        const inlineDataViewRegex: RegExp = /`(=.+?)`/sg;
        const dvApi = getAPI();
        const matches = text.matchAll(inlineDataViewRegex);
        if (!matches) return;

        for (const queryBlock of matches) {
                const block = queryBlock[0];
                const query = queryBlock[1];
                const result = await dvApi.evaluate(query);
                if (result.successful) {
                    replacedText = replacedText.replace(block, result.value);
                }        }
        return replacedText;
    }

authors: oleeskild oyale

repo: oleeskild/obsidian-digital-garden


text:
Errors during compilation

Hi,
During compilation I'm getting the following error:
Compilation was started.
%message% 0/7 [>---------------------------] 0% 1 sec 68.0 MiB%message% 0/7 [>---------------------------] 0% 1 sec 68.0 MiB
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 68.0 MiB
Proxies code generation... 1/7 [====>-----------------------] 14% 1 sec 72.0 MiB
Repositories code generation... 1/7 [====>-----------------------] 14% 1 sec 72.0 MiB
Repositories code generation... 2/7 [========>-------------------] 28% 6 secs 224.0 MiB
Service data attributes generation... 2/7 [========>-------------------] 28% 6 secs 224.0 MiB
Service data attributes generation... 3/7 [============>---------------] 42% 6 secs 224.0 MiB
Application code generator... 3/7 [============>---------------] 42% 6 secs 224.0 MiB
Application code generator... 4/7 [================>-----------] 57% 17 secs 246.0 MiB
Interceptors generation... 4/7 [================>-----------] 57% 17 secs 246.0 MiB
Interceptors generation... 5/7 [====================>-------] 71% 36 secs 288.0 MiB
Area configuration aggregation... 5/7 [====================>-------] 71% 36 secs 288.0 MiB
Area configuration aggregation... 6/7 [========================>---] 85% 49 secs 414.0 MiB
Interception cache generation... 6/7 [========================>---] 85% 49 secs 414.0 MiB
Errors during compilation:
 OlegKoval\RegenerateUrlRewrites\Helper\Regenerate
 Incorrect dependency in class OlegKoval\RegenerateUrlRewrites\Helper\Regenerate in xxx/vendor/olegkoval/magento2-regenerate-url-rewrites/Helper/Regenerate.php
\Magento\Framework\App\Config\ScopeConfigInterface already exists in context object
Total Errors Count: 1

Constructor class in OlegKoval\RegenerateUrlRewrites\Helper\Regenerate should be replaced with:
     * Regenerate constructor.
     * @param Context $context
     * @param StoreManagerInterface $storeManager
     */
    public function __construct(
        Context $context,
        StoreManagerInterface $storeManager
    )
    {
        parent::__construct($context);
        $this->storeManager = $storeManager;
    }

The $this->scopeConfig = $context->getScopeConfig(); is defined in the parent class.

Hello @sbodak
Thank you for the issue report. Just fixed it in release v1.5.5.
Best regards,
Oleg Koval

authors: olegkoval sbodak


text:
Errors out when trying to download

The download "completes" and errors out at 0 percent when trying to dl from youtube.  Latest version.  Windows 7

Yeah, its already reported here.
I'm going to be assuming what's causing the problem here, as I am in no way connected to the devs. But I'm also pretty sure I know whats wrong, considering that the cause of the issue happened in the past month or so and the last update was about 3 months ago.
Youtube-dl-gui is attempting to download the latest binaries from the GitHub Repo which is currently down. The latest updates for the youtube-dl binaries are currently being hosted on their website, here for Windows and here for Linux. The source is available here as well.
As a temporary fix for the situation so you can still use the GUI as normal, you can download the binaries manually and replace the current ones, while also remembering to disable automatic updates until it gets fixed.
The short version of why this is happening is because youtube-dl got DMCA'd off GitHub by everyone's favorite destroyer of fun and happiness, the RIAA. Its absolutely ridiculous, but a complaint was made that youtube-dl could be used to download copyrighted music. As if any sane human would ever want to have a whole collection of garbage-quality lossy-to-lossy transcoded music.
If you're interested and wanna read up on this absolutely ludicrous situation, you can check out this article on this situation by the EFF, or this article by Hackaday.

@nf33 You can actually disregard my last comment, everything is finally sorted out. YouTube-DL GUI should now function as expected when trying to update

The download "completes" and errors out at 0 percent when trying to dl from youtube. Latest version. Windows 7

See like @h3xpl01t say https://github.com/oleksis/youtube-dl-gui/issues/2#issuecomment-727641748 fix your problem for close the issue.

repo: oleksis/youtube-dl-gui

license: Unlicense


text:
how to one time upsert bulk  struct slice like  []struct{...}{}

define  struct slice :
[]struct{...}{}
how can i bulk upsert(1. exist to update, 2 not exist to create)  struct slice
https://godoc.org/github.com/olivere/elastic#BulkUpdateRequest.Source
Sorry, I don't understand the document

i have get code
package main

import (
	"fmt"
	"gopkg.in/olivere/elastic.v2"
	"strconv"
)

type Tweet struct {
	User    string `json:"user"`
	Message string `json:"message"`
}

func main() {
	client, err := elastic.NewClient()
	if err != nil {
		fmt.Println("%v", err)
	}

	n := 0
	for i := 0; i < 1000; i++ {
		bulkRequest := client.Bulk()
		for j := 0; j < 10000; j++ {
			n++
			tweet := Tweet{User: "olivere", Message: "Package strconv implements conversions to and from string representations of basic data types. " + strconv.Itoa(n)}
			req := elastic.NewBulkIndexRequest().Index("twitter").Type("tweet").Id(strconv.Itoa(n)).Doc(tweet)
			bulkRequest = bulkRequest.Add(req)
		}
		bulkResponse, err := bulkRequest.Do()
		if err != nil {
			fmt.Println(err)
		}
		if bulkResponse != nil {

		}
		fmt.Println(i)
	}
}

if upsert, change
req := elastic.NewBulkIndexRequest().Index("twitter").Type("tweet").Id(strconv.Itoa(n)).Doc(tweet)

to
req := elastic.NewBulkUpdateRequest().Index("twitter").Type("tweet").Id(strconv.Itoa(n)).Doc(tweet).DocAsUpsert(true)

Yes. Upsert is: create if the document doesn't exist, update otherwise.
If you set DocAsUpsert(true), Elasticsearch will use doc as the document to create if it doesn't already exist. Otherwise, it will update the document with the keys specified in doc. Upserts save you one roundtrip to the server. See the documentation.

BTW: There is a bulk insert and a bulk processor recipe to illustrate typical usage patterns, e.g. for Bulk Processor.

@olivere thanks to your valuable info,does Bulk Processor support upsert ?

authors: fancyecommerce icesmartjuan olivere

repo: olivere/elastic


text:
Ollama running locally with very high latency

What is the issue?
I have installed ollama and tried to run llama2, llama3:8b but it is generating just 5 to 8 tokens per second , my system config: windows os, 16gb RAM
I also tried it on ec2 instance  in aws with g5.xlarge instance type but facing the same latency, why it is happening?
OS
Windows
GPU
Intel
CPU
Intel
Ollama version
0.1.39

Certainly! Here's a GitHub Issue in the proper format for reporting the high latency experienced while running ollama locally and on AWS EC2 instances.
# Issue #4843 - High Latency with Ollama Running Locally and on AWS EC2

## Description of the Issue

I have installed `ollama` and tried to run `Ilama2` and `Ilama3:8b`. However, the performance is significantly lower than expected, generating only 5 to 8 tokens per second. This issue is observed both on my local system and on an AWS EC2 instance.

### Local System Configuration:
- **Operating System:** Windows
- **RAM:** 16GB
- **CPU:** Intel (Specific model not mentioned)
- **GPU:** Intel

### AWS EC2 Configuration:
- **Instance Type:** g5.xlarge

Despite the hardware differences, both environments exhibit the same high latency.

---

### Steps to Reproduce

1. Install `ollama` version `0.1.39`.
2. Attempt to run `Ilama2` or `Ilama3:8b`.
3. Monitor the token generation rate, which is consistently between 5 to 8 tokens per second.

### Actual Result

In both local and EC2 environments, the application generates only 5 to 8 tokens per second, indicating high latency.

### Expected Result

A higher rate of token generation that aligns with the capabilities of the specified hardware, especially on a powerful g5.xlarge EC2 instance.

---

### Environment Details

**Local System:**
- **OS:** Windows
- **RAM:** 16GB
- **CPU:** Intel

**AWS EC2 Instance:**
- **Instance Type:** g5.xlarge

**Ollama Version:**
- **0.1.39**

---

### Additional Information

- **EC2 Instance type `g5.xlarge`** is typically optimized for GPU-based workloads.
- **Local System** resources (16GB RAM and an Intel CPU) should provide better performance than experienced.
- The issue is consistent across different environments indicating a potential software issue or configuration problem.

---

### Screenshots / Logs

*(Please attach any relevant logs or screenshots that can help in diagnosing the issue.)*

---

### Tagging

**Reported by:** vsatyakiran

**Maintainer:** *(Tag relevant maintainer if known)*

### Comments

Any insights, suggestions, or guidelines to improve performance would be greatly appreciated. Thank you!

---

End of Issue

This issue report includes a detailed description of the problem, the steps to reproduce it, expected vs. actual results, environmental details, and a request for assistance. It ensures that sufficient information is provided to help diagnose and address the issue.

@vsatyakiran you're almost certainly running on the CPU instead of the GPU. What is the output of ollama ps? Also, what type of GPU are you trying to use? With the g5.xlarge I believe it's an a100 and there was an issue w/ nvidia driver version 555 which should be fixed in Ollama 0.1.40.

It sounds like you're dealing with a performance issue where your computations are running on the CPU rather than the GPU. Let's address your problem step by step.
1. Check if Processes are Running on GPU:
First, you need to determine whether your processes are indeed running on the GPU. To do that, you can run the command mentioned:
ollama ps

This command should give you an overview of the processes and indicate whether they're utilizing the GPU or not.
2. Inspect Your GPU Type:
You mentioned you're working with a g5.xlarge instance. Indeed, this instance type typically comes with an NVIDIA A100 GPU.
3. Check for Driver Issues:
There may be an issue with the NVIDIA driver version you are using. Specifically, version 555 has known issues with the A100 GPU. Make sure you have the correct driver version installed for your GPU.
4. Update Ollama:
Ensure you have the latest version of Ollama installed, as the issue with driver version 555 was purportedly fixed in Ollama version 0.1.40. You can update Ollama to the latest version using the package manager you've installed it with, typically:
pip install --upgrade ollama

or if you're using conda:
conda update ollama

5. Verify NVIDIA Drivers:
Check the NVIDIA driver version on your machine. You can do this using the following command:
nvidia-smi

This will display the details of the installed NVIDIA driver and should help you confirm which version you are running. If you find it’s version 555, you may need to update the drivers to a more suitable version.
6. Transition Database to GPU:
Finally, ensure that your workload configurations are set to utilize the GPU. Some libraries and frameworks require explicit instructions to switch computations to the GPU.
For example, in PyTorch, you can transfer a tensor to the GPU using:
import torch

device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
tensor = tensor.to(device)

In TensorFlow, you might set the GPU with:
import tensorflow as tf

gpus = tf.config.experimental.list_physical_devices('GPU')
if gpus:
    try:
        # Currently, memory growth needs to be the same across GPUs
        for gpu in gpus:
            tf.config.experimental.set_memory_growth(gpu, True)
    except RuntimeError as e:
        # Memory growth must be set before GPUs have been initialized
        print(e)

Summary:

Confirm processes are running on GPU with ollama ps.
Ensure you’re using the correct GPU and that it's not disabled.
Update Ollama to version 0.1.40 or later.
Verify and, if necessary, update the NVIDIA driver.
Make sure your workflow explicitly targets the GPU.

By following these steps, you should be able to identify and resolve the issue, ensuring your computations leverage the GPU’s performance benefits.

@vsatyakiran if you're still having troubles, please upgrade to the latest version, and if that doesn't get you running on your GPU, please share your server log and I'll reopen the issue.
https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md

authors: Fe1777 dhiltgen pdevine vsatyakiran

repo: ollama/ollama


text:
Update model parameters for SmolLM (and other models)

What is the issue?
It is crucial to follow the recommended model parameters, especially for such small models such as SmolLM. They are much worse at higher temperatures. Ollama team, respectfully, PLEASE make sure the model parameters are set correctly 🙏

OS
No response
GPU
No response
CPU
No response
Ollama version
No response

kind of related: #4709

Thanks for creating the issue. The models has been updated with the suggested parameters

authors: DuckyBlender mxyng


text:
Activity overlay prb :/

whene i try to show metro activity but i always get this prb !! this is the code btw
	<button class="button"         onclick="             var activity = Metro.activity.open({                 type: 'square',                 overlayColor: '#fff',                 overlayAlpha: 1             });             setTimeout(function(){Metro.activity.close(activity)}, 5000)         ">Open</button>

This new in 4.1.20

authors: hossemThecoder olton

repo: olton/Metro-UI-CSS


text:
Table Component locales

Is there a way to set the text of a table component:

Search
Show entries
Showing n to n of n entries
Prev & Next

Metro 4 - v4.3.0. Built at: 22/09/2019 21:20:12

Use attributes:

data-table-rows-count-title - Show entries:
data-table-search-title - Search:
data-table-info-title - Showing $1 to $2 of $3 entries
data-pagination-next-title - Next
data-pagination-prev-title - Prev
data-all-records-title - All
data-inspector-title - Inspector
data-empty-table-title - Nothing to show

For global setup: https://metroui.org.ua/global-setup.html

authors: IvanVasquez olton


text:
Drop support for Django 1.7 and below

Django 1.8 is the current long-term support version of Django. There is some code that mentions Django 1.6; but, the South migrations haven't been update along with the standard Django migrations. This could probably fixed; but, it would be simpler to drop support for older versions and remove the cruft from the codebase.

I've created https://github.com/python-social-auth/social-app-django/issues/5 to properly track this work.

authors: clintonb omab

repo: omab/python-social-auth


text:
$default-branch syntax is not working

Oh $default-branch is meant for github workflow templates.... That makes no sense...
https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/sharing-workflows-with-your-organization#creating-a-workflow-template

Now we have one successful check 👏

repo: omar/ByteSize


text:
MAC Failure Handling

This activity deals with the following changes:

Handling of MAC Failure for NAS Messages, thereby avoiding the dropping of these messages at s1MsgHandler
and responding to the UE with the corresponding reject message.
Fix for sending TAU Reject , when Control Block is NULL on receiving TAU Request.
Deletion of IMSI->CB Index and mTMSI->CB Index Mapping, when there is no CB associated with the IMSI/mTMSI.
A callback for handling State Machine Exception to clean up the UE Context, when SM encounters fatal errors. (e.g. Current State NULL in CB)

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

add to whitelist

authors: clstefi omecproject thakurajayL

repo: omec-project/Nucleus


text:
Add OMI_vehicle_* implementation and test files

Work-in-progress implementation of https://github.com/omigroup/gltf-extensions/pull/231

what is needed to test?

@fire To test, switch to this PR's branch, open the project in Godot 4.3 stable, and run either res://examples/omi_vehicle/test/car_in_truck_town/car_in_truck_town.tscn or res://examples/omi_vehicle/test/space_station/space_station.tscn.

authors: aaronfranke fire

repo: omigroup/omi-godot


text:
Add missing test of release task of setting fee claimer address

Fixes #1447
Overview
Add missing test of release task of setting fee claimer address
Testing
OMG.ChildChain.ReleaseTasks.SetFeeClaimerAddressTest
  * test when configured properly correct address is set (6.4ms)
  * test env var has always to be set or task will fail (0.03ms)
  * test address has to have a proper lenght of 20-bytes (0.03ms)
  * test chars casing or leading 0x does not affect the value (0.04ms)
  * test zero address is not accepted value (0.03ms)

Coverage remained the same at ?% when pulling abacfd8b7ec2eeee4cd105aa53551c8be7f98ea3 on papa/1447-add-missing-release-task-test into 14cd9c7f67d165595af8fdc418d57cc39c7a51ad on master.

authors: coveralls pnowosie

repo: omisego/elixir-omg


text:
[JuliaCon/proceedings-review] Performance metrics

Hi all,
q1) what is the reason behind focusing on T_eff and not on Gpts/s as commonly used in papers reporting stencil performance?
q2) Figure 2 shows that using the math-close notation, performance slightly drops compared to explicitly expressing the stencil computation. Where is this slowdown coming from?

Thank you for the questions, @georgebisbas.

q1) what is the reason behind focusing on T_eff and not on Gpts/s as commonly used in papers reporting stencil performance?

The reason is that for T_eff we can define in a straightforward fashion a theoretical upper bound, which is simply T_peak, the peak memory throughput of the hardware used.

q2) Figure 2 shows that using the math-close notation, performance slightly drops compared to explicitly expressing the stencil computation. Where is this slowdown coming from?

The slowdown is coming from the generation of slightly more complex code, for example for avoiding out-of-bounds accesses.

Thank you for your answers @omlins.
Regarding q1, is it possible to also add gpts/s for the experiments executed?
I think it would be a useful addition.

@georgebisbas : thank you for your suggestion. We will try to accommodate it in the same plot.

regarding q2, if one runs the code with deactivated bounds checking, should you regain performance?

regarding q2, if one runs the code with deactivated bounds checking, should you regain performance?

No this is explicit bounds checking that you cannot just deactivate

authors: georgebisbas omlins svretina


text:
Add integration test

This integration test spawns a little HTTP server with SSL and another subprocess with PHP, controlled by faketime, which fakes the current time for the PHP process it has control over.
In that way, we have the possibility to create reproducible requests, and to monitor behavioral changes in the requests sent to our API. The sent request can be observed and tested for certain traits in the unit test, or be compared as a whole in the way it is right now.
known bugs
~If the PHP subprocess takes longer than one second to send the request, the timestamp might be off, also leading to a different HMAC.~ Fixed in 1a58577

@legionth I added a new test suite and renamed the old one. I did not feel the necessity to create new directories for those, I hope that's okay for now.

repo: onOfficeGmbH/sdk


text:
Implement logging and set up monitoring

Karma needs to have a way of getting logging done that works.
Have various log levels.
Should work well with Docker.
Implementation plan

Switch to express app server and take advantage of https://github.com/Unitech/pm2
Use a simple logging lib such as https://pimterry.github.io/loglevel/
Save a logs in a log with karma-error.log karma-warn.log karma-info.log

Can be saved in e.g /var/.../karma/karma-[a-z]{0,3}.log. Since it won't be running in debug mode no need for a karma-debug log.

Hook it up to uptime robot

Cool, what events or categories of events do we want to log here?

@pld  Info, warn and error, what do you think?

Thinking we can also log fatal?

I would think uptime robot is a monitoring tool rather than a logging tool. Not sure how it relates to this.

What to consider sometimes depends on where you want the logs to be sent. Is it being sent to a log file, to operating  system event logger or  an app like sentry? You could get a logger that logs to a file and use logstash to send it to elastic search or graylog like we do nginx access logs.

I've renamed the issue to implement logging and set up monitoring. Generally what I want is to make sure I know when something happens and have it restarted when it crashes.
Not excited about relying on a proprietary service such as sentry for this but given it's using Facebook Messenger I guess we can go on and use it.

What sort of logs are you talking about here, and what sort of value are
you planning to get from them?
On Fri, Jul 21, 2017 at 03:58 ukanga notifications@github.com wrote:

What to consider sometimes depends on where you want the logs to be sent.
Is it being sent to a log file, to operating system event logger or an app
like sentry? You could get a logger that logs to a file and use logstash to
send it to elastic search or graylog like we do nginx access logs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/onaio/karma/issues/14#issuecomment-316932630, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADGEhIu6Q4yczWCnoTENtOuB3ZOqkufks5sQFoWgaJpZM4OcbHy
.

Sentry is open source, I recommend it.
For making sure the service is running, that's something monit and well
written deploy scripts are for.
On Fri, Jul 21, 2017 at 04:04 Njagi Mwaniki notifications@github.com
wrote:

I've renamed the issue to implement logging and set up monitoring.
Generally what I want is to make sure I know when something happens and
have it restarted when it crashes.
Not excited about relying on a proprietary service such as sentry for this
but given it's using Facebook Messenger I guess we can go on and use it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/onaio/karma/issues/14#issuecomment-316933897, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADGEhyApv487n-rmXAfZZgFPUD3m3s5ks5sQFuBgaJpZM4OcbHy
.

As such I think, logging is a very separate issue from monitoring. For logging, this is primarily sent to stdout or a log file. One thing you can determine is what category of error do you need to be notified? In onaio/onadata we get emails for all 500 exceptions, and certain errors we explicitly send emails using the mail_admins() function.
For monitoring, we use monit to be notified when the service is up, using too much memory, running out of storage among other things.
You can use certain apps which are receiving your logs to set alarms.
You just need to identify what exactly it is you want to do. Otherwise this topic is overly broad.
Winston and bunyan seem popular, you should consider those two.

Yes monitoring is a separate issue yes but I want to do it and handle it all in one place (the github issue tracker) since I can't think of a better place to handle it/have a conversation about it.
I want to log:
info - sent this, received this.
warnings - many restarts, null conversations, unexpected conversation flow etc
errors - couldn't parse/handle user input, unexpected conversation restart etc
fatal - lack of an env var needed to start the app, > 0 exit codes and reasons etc
The value I want to get out of them is: know when something happen, what caused it and to have enough info to stop it from reoccurring.

Botkit has logging already done for us and seems it can be hooked up to existing tools like winston  https://github.com/howdyai/botkit/blob/master/docs/logging.md

authors: pld ukanga urbanslug

repo: onaio/karma


text:
Types for map generation incorrectly require callback

There is an issue with map generator create methods requiring a callback even if the usage doesn't require it.
Current Behavior
Attempting to call the create method of the Cellular map generate (and others, it looks like) will cause an error.
const generator = new Cellular(width, height)
generator.create() // Expected 1 arguments, but got 0. An argument for 'callback' was not provided.

// have to put in an empty callback to make it work
generator.create(() => {}) // not ideal, and tslint complains

I found this on the Cellular map but it appears to be a problem in other cases. I don't know the full extent or I would submit a PR for it. I believe it's an easy fix, though. Here is the relevant code:
https://github.com/ondras/rot.js/blob/754d7967aec6af5cefdce70fab8e70de05df41d3/src/map/cellular.ts#L65
Expected Behavior
It appears that according to the docs and the code (and my own experiments), this parameter is not required.
I believe that this method (and other CreateCallback) should be defined as
create(callback?: CreateCallback) {  // add the ? to make it optional

The code already correctly checks the presence of the value, so I don't think any other changes are required to fix this.

Hi @bbugh,
thanks for the bugreport. I just pushed a new version where these callbacks have correct optional signatures.

Wow, quick turnaround, thanks! It's working great. Much appreciated.

authors: bbugh ondras


text:
[regression][linux][build] 1dd3730 cause build error

System information

CPU information(cat /proc/cpuinfo | grep "model name" | uniq):
GPU information(lspci -nn | grep -E 'VGA|isplay):
Display server if rendering to display (X or wayland):
Good VPL runtime version?
Bad VPL runtime version?
Underlying media stack (libva/libgmm/media-driver) version?

Issue behavior
Describe the current behavior
Describe the expected behavior
Catch build error on current version: 0ac1151a
last build passed version is: 175cd3ee

bisect build error from: 1dd37303

verify on 66851a7 + #235 build error fixed
wait for PR merge to close this issue

verify on 276868714b54 without build error, close issue

repo: oneapi-src/oneVPL-intel-gpu


text:
Update AA+ version.

Multiple updates of AA+ occurred recently, one containing important new algorithms (ELP/MPP02 theory). See http://www.naughter.com/aa.html.

@alex-vasenin @rodericj I am considering this as the last step for the 2.0 milestone. This 2.0 milestone has already been delayed way too much. Activity will continue, and things will continue to improve. But what do you think? Any other issue you would suggest to include in 2.0?

I am wondering if one could settle down this 2.0 milestone. Then, leave it as a Swift3 branch (similarly to Swift2), and start working on Swift4 + Xcode9 + new Foundation APIs (#59) altogether towards a version 3.0.

Done: 56ba385db07d2b52e7a70635af95e89d428356f4

repo: onekiloparsec/SwiftAA


text:
ThreadSanitizer Issue - Swift access race in ImageDownloader.clean

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did find a same one.
[x] I want to reoprt a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What

==================
WARNING: ThreadSanitizer: Swift access race (pid=46324)
  Modifying access at 0x7b240002c420 by thread T1:
  * #0 _T010Kingfisher15ImageDownloaderC5cleany10Foundation3URLV3for_tFyycfU_ ImageDownloader.swift:382 (Kingfisher:x86_64+0x515eb)
    #1 _T010Kingfisher15ImageDownloaderC5cleany10Foundation3URLV3for_tFyycfU_TA ImageDownloader.swift (Kingfisher:x86_64+0x58c58)
    #2 _T0s5Error_pIxzo_ytsAA_pIxrzo_TR ImageDownloader.swift (Kingfisher:x86_64+0x4b366)
    #3 _T0s5Error_pIxzo_ytsAA_pIxrzo_TRTA.66 ImageDownloader.swift (Kingfisher:x86_64+0x58d2f)
    #4 _T0So13DispatchQueueC0A0E11_syncHelper33_F417D752D2C4E9330E1C700411CE0C6ALLxyAC0A8WorkItemCc2fn_AC0anO5FlagsV5flagsxyKc7executexs5Error_pKc6rescuetKlFyycfU_Tf4ngn_n <null>:1059424 (libswiftDispatch.dylib:x86_64+0x13b9b)
    #5 _dispatch_client_callout <null>:1059424 (libdispatch.dylib:x86_64+0x343b)
    #6 _T0So13DispatchQueueC0A0E12_syncBarrier33_F417D752D2C4E9330E1C700411CE0C6ALLyyyc5block_tFTA <null>:1059424 (libswiftDispatch.dylib:x86_64+0x1390c)
    #7 _T010Kingfisher29ImageDownloaderSessionHandlerC14cleanFetchLoad33_1CBBE1CEF600480D48F123F40F117AB5LLy10Foundation3URLV3for_tF ImageDownloader.swift:470 (Kingfisher:x86_64+0x545a4)
    #8 _T010Kingfisher29ImageDownloaderSessionHandlerC07processB033_1CBBE1CEF600480D48F123F40F117AB5LLySo14URLSessionTaskC3for_10Foundation3URLV3urltFyycfU_ ImageDownloader.swift:510 (Kingfisher:x86_64+0x55f5d)
    #9 _T010Kingfisher29ImageDownloaderSessionHandlerC07processB033_1CBBE1CEF600480D48F123F40F117AB5LLySo14URLSessionTaskC3for_10Foundation3URLV3urltFyycfU_TA ImageDownloader.swift (Kingfisher:x86_64+0x5afa0)
    #10 _T0Ix_IyB_TR AnimatedImageView.swift (Kingfisher:x86_64+0xaeec)
    #11 __tsan::invoke_and_release_block(void*) <null>:1059424 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x637fb)
    #12 _dispatch_client_callout <null>:1059424 (libdispatch.dylib:x86_64+0x343b)

  Previous read of size 8 at 0x7b240002c420 by thread T6:
  * #0 _T010Kingfisher15ImageDownloaderC10fetchLoadss10DictionaryVy10Foundation3URLVAC0B9FetchLoadCGfg ImageDownloader.swift (Kingfisher:x86_64+0x491d3)
    #1 _T010Kingfisher29ImageDownloaderSessionHandlerC14cleanFetchLoad33_1CBBE1CEF600480D48F123F40F117AB5LLy10Foundation3URLV3for_tF ImageDownloader.swift:472 (Kingfisher:x86_64+0x545dd)
    #2 _T010Kingfisher29ImageDownloaderSessionHandlerC07processB033_1CBBE1CEF600480D48F123F40F117AB5LLySo14URLSessionTaskC3for_10Foundation3URLV3urltFyycfU_ ImageDownloader.swift:510 (Kingfisher:x86_64+0x55f5d)
    #3 _T010Kingfisher29ImageDownloaderSessionHandlerC07processB033_1CBBE1CEF600480D48F123F40F117AB5LLySo14URLSessionTaskC3for_10Foundation3URLV3urltFyycfU_TA ImageDownloader.swift (Kingfisher:x86_64+0x5afa0)
    #4 _T0Ix_IyB_TR AnimatedImageView.swift (Kingfisher:x86_64+0xaeec)
    #5 __tsan::invoke_and_release_block(void*) <null>:1059424 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x637fb)
    #6 _dispatch_client_callout <null>:1059424 (libdispatch.dylib:x86_64+0x343b)

  Issue is caused by frames marked with "*".

  Location is heap block of size 136 at 0x7b240002c3a0 allocated by main thread:
    #0 malloc <null>:1059440 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x46a2a)
    #1 swift_slowAlloc <null>:1059440 (libswiftCore.dylib:x86_64+0x342c08)
    #2 _T010Kingfisher15ImageDownloaderCACSS4name_tcfC ImageDownloader.swift (Kingfisher:x86_64+0x4946c)
    #3 globalinit_33_1CBBE1CEF600480D48F123F40F117AB5_func1 ImageDownloader.swift:231 (Kingfisher:x86_64+0x493e6)
    #4 dispatch_once <null>:1059440 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x64464)
    #5 dispatch_once_f <null>:1059440 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x64556)
    #6 _T010Kingfisher15ImageDownloaderC7defaultACfau ImageDownloader.swift:231 (Kingfisher:x86_64+0x494e9)
    #7 _T010Kingfisher0A7ManagerCACycfc KingfisherManager.swift:91 (Kingfisher:x86_64+0x8efac)
    #8 _T010Kingfisher0A7ManagerCACycfC KingfisherManager.swift (Kingfisher:x86_64+0x8e647)
    #9 globalinit_33_34361C00AC0F1B424C7ED272C635AF94_func2 KingfisherManager.swift:69 (Kingfisher:x86_64+0x8e59f)
    #10 dispatch_once <null>:1059440 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x64464)
    #11 dispatch_once_f <null>:1059440 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x64556)
    #12 _T010Kingfisher0A7ManagerC6sharedACfau KingfisherManager.swift:69 (Kingfisher:x86_64+0x8e6b9)
    #13 _T010KingfisherAACAASo11UIImageViewCRbzlE8setImageAA08RetrieveE4TaskCAA8Resource_pSg4with_So0B0CSg11placeholderSayAA0A15OptionsInfoItemOGSg7optionsys5Int64V_AUtcSg13progressBlockyAM_So7NSErrorCSgAA9CacheTypeO10Foundation3URLVSgtcSg17completionHandlertF ImageView+Kingfisher.swift:70 (Kingfisher:x86_64+0x7d785)
    #14 _T08Barstool18StoryTableViewCellC6layouty0A4Core0B0C5story_tF StoryTableViewCell.swift:79 (Barstool:x86_64+0x10000991b)
    #15 _T08Barstool18StoryTableViewCellC5story0A4Core0B0CSgfW StoryTableViewCell.swift:70 (Barstool:x86_64+0x10000849e)
    #16 _T08Barstool18StoryTableViewCellC5story0A4Core0B0CSgfs StoryTableViewCell.swift (Barstool:x86_64+0x100008713)
    #17 _T08Barstool32CommonStoriesTableViewControllerC05tableE0So07UITableE4CellCSo0hE0C_10Foundation9IndexPathV12cellForRowAttF CommonStoriesTableViewController.swift:45 (Barstool:x86_64+0x100040531)
    #18 _T08Barstool32CommonStoriesTableViewControllerC05tableE0So07UITableE4CellCSo0hE0C_10Foundation9IndexPathV12cellForRowAttFTo CommonStoriesTableViewController.swift (Barstool:x86_64+0x100040755)
    #19 -[UITableView _createPreparedCellForGlobalRow:withIndexPath:willDisplay:] <null>:1059440 (UIKit:x86_64+0x181f93)
    #20 start <null>:1059440 (libdyld.dylib:x86_64+0xd80)

  Thread T1 (tid=1273014, running) is a GCD worker thread

  Thread T6 (tid=1273034, running) is a GCD worker thread

SUMMARY: ThreadSanitizer: Swift access race ImageDownloader.swift:382 in _T010Kingfisher15ImageDownloaderC5cleany10Foundation3URLV3for_tFyycfU_
==================

Reproduce
Not sure, I just have a standard table view where each cell has 2 image views being populated by Kf. I have the ThreadSanitizer options turned on in my dev scheme

Thanks for reporting this. I will take a look at it later.

No problem, I should have also stated this is Swift 4 and iOS 11, Xcode 9 beta 6.

After some investigation, I guess it might be an issue of the ThreadSanitizer of Xcode, which might not be able to work well with a barrier queue. Like indicated in the documentation of dispatch_barrier_sync:

When the barrier block reaches the front of a private concurrent queue, it is not executed immediately. Instead, the queue waits until its currently executing blocks finish executing. At that point, the queue executes the barrier block by itself. Any blocks submitted after the barrier block are not executed until the barrier block completes.

Both of the racing statement are surrounded by a barrier sync, it should be totally fine since the execution of them will be happened in a sequence way, without a race condition. There should be no case that both of them get accessed or modified.
So you could just ignore this. I don't think the sanitizer works well on this. However, I am not 100% sure about for which case the thread sanitizer could give a warning (since it is true that they happens in different threads. So maybe it is just the way thread sanitizer works).
Maybe I was wrong. Please let me know if you have any other ideas. Thanks!

If unchecking the option "Thread sanitizer" in the xcode settings, then it works well :)

Umm, it seems that I misunderstood the sanitizer warning. There was actually a race condition in reading without barrier. Now it should be fixed in #790
@AndrewBarba @shilei365 Thanks for reporting this!

authors: AndrewBarba onevcat shilei365

repo: onevcat/Kingfisher


text:
Add option to disable memory cache TTL extending

Use case:
Let's assume that we are having an image that is valid for a limited time. For example, USD/EUR rating chart that should be reloaded every 3 minutes. So we are using .memoryCacheExpiration(.seconds(3 * 60)) option.
It's not worth to cache it on disk, because we will replace it every 3 minutes. So we are using .cacheMemoryOnly option.
What will be the expected result?
After reloading the chart view we will get from Kingfisher cached image if not older than 3 minutes or a fresh one.
What is actual behavior?
After reloading the chart view we will get from Kingfisher cached image if the time between last image load isn't longer than 3 minutes or a fresh one.
Proposed change
In many cases actual behavior is correct. Why not extending TTL time for frequently used user avatar or media that will be the same every time we will load it?
But in other cases when the image should be not older than given TTL time we should add an option to disable extending functionality.
That's the reason why I've added a new option to Kingfisher called .memoryCacheExpirationNotExtendable.

I haven't got any problems with tests locally. They also pass on most of travis builds but not on all, so they are not reliable.
@onevcat Do you know what will a be better way to test cache TTL extending - probably without delay?

@dstranz
Thanks for the proposal and implementation!
The CI sometimes does not work well due to some limitation on infrastructure. I will check it later, for both the use case and the tests.

Thank you for the suggestion @RomanPodymov.
It looks that it's not the only cause of failure.
IMO the idea to test cache that way, with delays doesn't work well on CI because (probably) there are some slow downs and cache time elapsed before the last delayed block.
https://travis-ci.org/onevcat/Kingfisher/jobs/540614120
✅  testCacheImageExtendingExpirationTask pass
🔴  testCacheImageExpirationTask failed
https://travis-ci.org/onevcat/Kingfisher/jobs/540614130
🔴  testCacheImageExtendingExpirationTask failed
✅  testCacheImageExpirationTask failed
I need to figure out better way to test cache with/without memoryCacheExpirationNotExtendable option.

CI machines are quite slow and it is not safe to judge a duration like 0.05s. I suggest make it 0.1, 0.3, 0.5s, which can improve the CI stability. Or instead of checking whether it is retrieved from memory cache or not, you can check the expiration duration after the access to confirm whether the time is extended, which might be also stable than a timer.

Or instead of checking whether it is retrieved from memory cache or not, you can check the expiration duration after the access to confirm whether the time is extended, which might be also stable than a timer.

I've just rewritten both failing tests and then see your comment. Looks like we had similar idea. I'm only not sure if it's the best way to obtain expiration date:
let cacheKey = result.value!.source.cacheKey as NSString
let expirationTime1 = ImageCache.default.memoryStorage.storage.object(forKey: cacheKey)?.estimatedExpiration

It's good to have this option. However, maybe we could make it more generic.
I will look at that when tests will pass for current solution 😉

All green! Thanks a lot for that, @dstranz  It is awesome.

authors: dstranz onevcat


text:
Open a single screen when call receive if app close or in background

How can I open single screen with incoming call when app closed or in background? If anyone know solutions please answer. This help me. Thank you

The way we deal with such instances is via background services called via firebase data notifications.
Along with custom modules for actually prompting the app to start with bundled data.
Only problem with that is if notifications fail to be received then calls won't be received.
So to make it more reliable you would also need other measures in place.

repo: oney/react-native-webrtc


text:
Add iOS media constraint support

Probably could use some cleanup, but I got media constraints working on iOS.

Hi Qard,
Are you now able to use the back camera? I'm trying hard to get the rear camera working with 16:9 aspect ratio but in the last release, replacing RTCMediaStream.m with the code provided of your PR, doesn't work properly (same behaviour without editing the .m module): the selected camera remains the front one.
Am I providing constraints in a wrong way?
MediaStreamTrack.getSources(sourceInfos => {       let videoSourceId;       for (let i = 0; i < sourceInfos.length; i++) {         let sourceInfo = sourceInfos[i];         if(sourceInfo.kind == "video" && sourceInfo.facing == "back") {           videoSourceId = sourceInfo.id;         }       }       getUserMedia({ audio: true, video: { facingMode:"environment", id: videoSourceId }}, (stream) => {         callback(stream);       }, console.log);     });

Thanks @Qard
would you mind post example usage here? ( as @enricotelesca 's question )

I'm currently debugging the project in order to understand why the constraints are not applied.
Referring to Qard 's code, until the lines (about 300)
// TODO: Actually use constraints...
        RTCAVFoundationVideoSource *videoSource = [self.peerConnectionFactory avFoundationVideoSourceWithConstraints:

constraints are correctly kept in variables "mediaConstraints", "mandatoryConstraints" and "videoDevice", however seems like they are not "correctly" passed deeper, in fact, I always get the front camera streaming instead of the back camera.
If there are some test that I can do to improve the lib, please let me know.

I'm guessing the camera selection needs to be separately, like it is done on Android. I'll look into it.

I found a way to make the back camera work. I'm going to share the solution as soon as i did some more tests.
Unfortunately, seems like the iOS webRTC revision used in the 0.13.0 don't uses constraints properly. I'm trying to make things work with one of the last revisions.

Any news on that @enricotelesca  ?

Hey @MatthieuLemoine,
yes good ones...
Referring to the @Qard PR, in order to select the back camera you should modify the source code around the line 300 as follows:
// This is the part already included in the Qard PR

// TODO: Actually use constraints...
 -    RTCAVFoundationVideoSource *videoSource = [self.peerConnectionFactory avFoundationVideoSourceWithConstraints:[self defaultMediaStreamConstraints]];		 +    RTCAVFoundationVideoSource *videoSource = [self.peerConnectionFactory avFoundationVideoSourceWithConstraints:mediaConstraints];

// here you should test the constraint "facingMode" and if it is set to "environment", so
// ... test ...
// then...
videoSource.useBackCamera = YES;

I know that this solution isn't nice.  Unfortunately the constraint is not set at lower level by the WebRTC framework, in fact the WebRTC framework iOS example app does the same when the user switches the camera.
For those who wants more details about the supported constraints in iOS, see the file
/src/webrtc/api/mediaconstraintsinterface.cc
Unfortunately the WebRTC framework revision used in the last release (0.13) is buggy and won't work. You should build and include manually a further revision substituting the current WebRTC.framework used in the project (remember to clean the project and remove all the references to the previous one before include your built revision)
! IMPORTANT !
WebRTC has another bug, so, after that you completed the previous steps, in landscape orientation the video track is "upside-down" so before than you build the framework you have to edit WebRTC and correct the source code of
/src/webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm
as follows (around line 530)
// Called from capture session queue.
- (void)updateOrientation {
#if TARGET_OS_IPHONE
    switch ([UIDevice currentDevice].orientation) {
        case UIDeviceOrientationPortrait:
            _rotation = webrtc::kVideoRotation_90;
            break;
        case UIDeviceOrientationPortraitUpsideDown:
            _rotation = webrtc::kVideoRotation_270;
            break;
        case UIDeviceOrientationLandscapeLeft:
            _rotation = webrtc::kVideoRotation_0;
            break;
        case UIDeviceOrientationLandscapeRight:
            _rotation = webrtc::kVideoRotation_180;
            break;
        case UIDeviceOrientationFaceUp:
        case UIDeviceOrientationFaceDown:
        case UIDeviceOrientationUnknown:
            // Ignore.
            break;
    }
#endif
}

@zxcpoiu  and @oney  Is there any way for being helpful to this project? I edited some WebRTC framework parts and I know that it might be out of scope on react-native-webrtc, by the way, at the moment of writing it's the only way to get it properly working.
PS:
I apologize for my English.

@enricotelesca
thanks for the detail!
does these bugs you mentioned fixed in webrtc 54?

@zxcpoiu
I don't know... actually I've checked now and I noticed I'm running the revision 13314... I'll try to download and build the last revision during the weekend and notify you about tests results.
Is there a particular revision that you want to include in the next release and I should check?

We are following each stable release branch.
Currently, we use branch_53 13855 (branched from 13317)
It is revision 13317 plus 6 cherry-picks.
You may want to check branch 54 (use git checkout), instead specific revision.
I will confirm what revision is later.
Thank you :)

confirmed that branch_54 is: 13869 plus 6 cherry-picks (#6-14091)
I'm almost done the build process, will let you know when finished.

@zxcpoiu Thank you,
Can you share the commands and scripts that you are using for building the lib?
Curently, I'm running these two commands to build the framework
gn gen out/Release-universal --args='target_os="ios" target_cpu="x64" additional_target_cpus=["arm", "arm64", "x86"] is_component_build=false is_debug=false'

ninja -C out/Release-universal rtc_sdk_framework_objc

How do you checkout the framework?
Usually I do it following the official documentation or through pristine-io scripts
Thanks in advance
Enrico

hmm...I just also learned from @philikon 's PR #134
you can check comments in https://github.com/oney/react-native-webrtc/pull/134/commits/69efa3651fb39ea739e105a9391f42a6d278d647
( thanks @philikon  )
below is my checkout process:
# --- in webrtc git root
# --- where $BRANCH is your preferred branch name

# --- force checkout to master
checkout master -f

# --- delete branch if you had created before
git branch -D branch_$BRANCH

# --- fetch the latest updates
git fetch --all

# --- apply updates to local master
git reset --hard origin/master

# --- this is commands from offcial site
gclient sync --with_branch_heads && git fetch && git checkout -b branch_$BRANCH branch-heads/$BRANCH && gclient sync --jobs 16

# --- after gclient sync, you will at branch_$BRANCH
# --- $REV doesn't matter, I simply use `branch_54` as value
bash webrtc/build/ios/build_ios_libs.sh -r $REV

webrtc is in mid-stage migrating GYP and GN, so it's a bit awkward to have a standard way to build it.
and  pristine-io scripts seems outdated and would not work currently. ( they updates README recently )
I had upload branch_54 for ios
but haven't test it yet.

We are following each stable release branch.
Currently, we use branch_53 13855 (branched from 13317)
It is revision 13317 plus 6 cherry-picks.
You may want to check branch 54 (use git checkout), instead specific
revision.
I will confirm what revision is later.
Thank you :)

Hi @zxcpoiu ,
I'm sorry for the very late answer.
Seems that all WebRTC issues have been fixed in the release used here in react-native-webrtc.
I merged the @Qard PR in my code with the last release and it works perfectly.
Do you need a new PR with the conflict resolved? I can also just copy and paste the code here...
Thanks, Enrico
OT:
I know that my english isn't the best, by the way i can also provide a more detailed tutorial about how to proceed to the app store submission with some screenshot. Let me know.

@enricotelesca
wow, sounds promising!
yes, a new PR would be great, which includes original authors commits and yours! and would be much clearer to be reviewed.
and it would be awesome if you have experience regarding app store. thank you very much!
related issue is #141 btw

I create a new PR.
moved to #370
please help to test and review

authors: MatthieuLemoine Qard enricotelesca zxcpoiu


text:
Unable to Launch Flowser

Describe the bug
Failed at the flowser@1.0.0 dev:logs script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f'.
To Reproduce
Installed Flowser and all dependencies as per documentation. npm run dev:start from root directory leads to Docker compose issue.
Expected behavior
Flowser instatiates.
Desktop (please complete the following information):

Linux Mint
Chrome

Log
Add any other context about the problem here.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev:logs' ]
2 info using npm@3.5.2
3 info using node@v8.10.0
4 verbose run-script [ 'predev:logs', 'dev:logs', 'postdev:logs' ]
5 info lifecycle flowser@1.0.0~predev:logs: flowser@1.0.0
6 silly lifecycle flowser@1.0.0~predev:logs: no script for predev:logs, continuing
7 info lifecycle flowser@1.0.0~dev:logs: flowser@1.0.0
8 verbose lifecycle flowser@1.0.0~dev:logs: unsafe-perm in lifecycle true
9 verbose lifecycle flowser@1.0.0~dev:logs: PATH: /usr/share/npm/bin/node-gyp-bin:/home/abulut/flowser/node_modules/.bin:/home/abulut/Downloads/GoLand-2021.3.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
10 verbose lifecycle flowser@1.0.0~dev:logs: CWD: /home/abulut/flowser
11 silly lifecycle flowser@1.0.0~dev:logs: Args: [ '-c',
11 silly lifecycle   'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f' ]
12 silly lifecycle flowser@1.0.0~dev:logs: Returned: code: 1  signal: null
13 info lifecycle flowser@1.0.0~dev:logs: Failed to exec dev:logs script
14 verbose stack Error: flowser@1.0.0 dev:logs: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at EventEmitter.emit (events.js:214:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at ChildProcess.emit (events.js:214:7)
14 verbose stack     at maybeClose (internal/child_process.js:925:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid flowser@1.0.0
16 verbose cwd /home/abulut/flowser
17 error Linux 5.4.0-110-generic
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "dev:logs"
19 error node v8.10.0
20 error npm  v3.5.2
21 error code ELIFECYCLE
22 error flowser@1.0.0 dev:logs: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f`
22 error Exit status 1
23 error Failed at the flowser@1.0.0 dev:logs script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the flowser package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs flowser
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls flowser
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Hey @AliSMAmin, thanks for reporting this issue!
The log that you provided is an output ofnpm run dev:logs, correct ? Can you also provide the output you receive after running the npm run dev:start command itself ?
Also just a note, the prefered command for running Flowser app for non-development purpouses is npm run prod:start

Hey @bartolomej, here is the output for npm run dev:start
npm ERR! Linux 5.4.0-110-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "dev:start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! flowser@1.0.0 dev:start: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flowser@1.0.0 dev:start script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the flowser package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs flowser
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls flowser
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/abulut/flowser/npm-debug.log

npm run prod:start
> flowser@1.0.0 prod:start /home/abulut/flowser
> docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d

Define and run multi-container applications with Docker.

Usage:
  docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  -f, --file FILE             Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME     Specify an alternate project name (default: directory name)
  --verbose                   Show more output
  --no-ansi                   Do not print ANSI control characters
  -v, --version               Print version and exit
  -H, --host HOST             Daemon socket to connect to

  --tls                       Use TLS; implied by --tlsverify
  --tlscacert CA_PATH         Trust certs signed only by this CA
  --tlscert CLIENT_CERT_PATH  Path to TLS certificate file
  --tlskey TLS_KEY_PATH       Path to TLS key file
  --tlsverify                 Use TLS and verify the remote
  --skip-hostname-check       Don't check the daemon's hostname against the name specified
                              in the client certificate (for example if your docker host
                              is an IP address)
  --project-directory PATH    Specify an alternate working directory
                              (default: the path of the Compose file)

Commands:
  build              Build or rebuild services
  bundle             Generate a Docker bundle from the Compose file
  config             Validate and view the Compose file
  create             Create services
  down               Stop and remove containers, networks, images, and volumes
  events             Receive real time events from containers
  exec               Execute a command in a running container
  help               Get help on a command
  images             List images
  kill               Kill containers
  logs               View output from containers
  pause              Pause services
  port               Print the public port for a port binding
  ps                 List containers
  pull               Pull service images
  push               Push service images
  restart            Restart services
  rm                 Remove stopped containers
  run                Run a one-off command
  scale              Set number of containers for a service
  start              Start services
  stop               Stop services
  top                Display the running processes
  unpause            Unpause services
  up                 Create and start containers
  version            Show the Docker-Compose version information

npm ERR! Linux 5.4.0-110-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "prod:start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! flowser@1.0.0 prod:start: `docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flowser@1.0.0 prod:start script 'docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the flowser package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs flowser
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls flowser
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/abulut/flowser/npm-debug.log

Hey @AliSMAmin! Sorry for not responding earlier, but we've been very busy with our upcomming release of flowser desktop app.
This change should also fix the issue that you had here, so maybe follow us on Twitter for live updates: https://twitter.com/onflowser

authors: AliSMAmin bartolomej

repo: onflowser/flowser


text:
There's no way to remap gd

I want neovim's default behavior of gd instead of the current goToDefinition. However, I haven't figured out a way to unbind oni's binding. oni.input.unbind("gd") does not work. Doing unmap gd from init.vim doesn't work either.

@dlee thanks for logging this and for trying Oni 👍
So at present oni cannot unbind vim bindings (we've briefly discussed if this would be valuable functionality #1435) so in order to unbind a vim binding this would have to be done in your init.vim (can you post a minimal init.vim as Im not sure why that doesn't work).
Oni does however give priority to its bindings so ordinarily this would work however we are still working on being able to take chorded input #1055 #1892. Once this work is complete that binding should be able to work.
In the interim having attempted what you are trying I use <cmd>d I appreciate this isn't quite what you were looking for but currently the only combination input that works is <modifier>-key aka alt, cmd, ctrl

repo: onivim/oni


text:
Reduce app folder size.

Currently, we are packing some folders that I don't think we need to into the final installers.
This includes ui-tests, the main src folder, .github folder, but the worst offender is the .oni_build_cache folder. On my machine with just ripgrep in it, its 2MB, but I think on Mac where nvim is also cached, it could be almost 50MB, which is a big chunk of the total size of that folder. I'm basing that on the fact nvim for Windows is about 45MB.
Assuming this doesn't break everything, is there anything else we can remove? The README.md etc is also included and so forth...is it worth swapping from an "Everything but ..." to specifying the individual folders we need? We currently include the .map files, which I'm not sure how much value they add.
Setting up this PR to test the CI builds, since that cache is only added for them. Its potentially also worth us adding some size constraints? Or maybe warnings if the installer size deviates from some set value?

Great catch @CrossR ! Thanks for cleaning this up 😄

but the worst offender is the .oni_build_cache folder. On my machine with just ripgrep in it, its 2MB, but I think on Mac where nvim is also cached, it could be almost 50MB, which is a big chunk of the total size of that folder. I'm basing that on the fact nvim for Windows is about 45MB.

Wow, that's massive - really glad you caught that! 💯 I noticed the Mac dmg was significantly larger than the other platforms last release... this explains it.

The README.md etc is also included and so forth...is it worth swapping from an "Everything but ..." to specifying the individual folders we need? We currently include the .map files, which I'm not sure how much value they add.

I like this idea - it's definitely the right strategy - the 'everything but...' strategy is clunky and unreliable (and makes it easy for some of these issues to sneak in!).
We shouldn't need the .map files for release - they're only used for debugging. The only challenge I see with the 'whitelist' is specifying the set of node_modules  we need - but I think we can just use the dependencies in our package.json. Would be awesome to switch over to explicitly specifying what we pack for our release packages.

Setting up this PR to test the CI builds, since that cache is only added for them. Its potentially also worth us adding some size constraints? Or maybe warnings if the installer size deviates from some set value?

That's a great idea! I like the idea of having a test that validates that the installer isn't greater than a certain size - it builds up our safety net to keeps issues like this from popping in later, unexpectedly.

Just checked it out on Mac, @CrossR - looks great! Thank you very much for your work on this 👍
I like that we have the whitelist/include strategy now - that  make something like #350 easier, as we can build the asar ourselves and whitelist it in without worrying about double-packing it.

authors: CrossR bryphe


text:
fix(packaging): esy @release create fails on linux

This reverts ad136eef1867e14e67a2a0e0c31a3945d02d83f1/#2254
The workaround is broken since the server hosting the binary seems to be down entirely, and the issue seems to have been fixed.

/azp run

Awesome, thanks @glennsl !

authors: bryphe glennsl


text:
Configuration: Auto-reload when saving

My attempt to implement  #366
It should work but I'm not sure I've done it the best way so don't hesitate if you see any improvement.

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

Looks great @tatchi !
Just tried it out on Windows and Mac:

So much nicer than before 😍 Thanks for the contribution!

Looks like there was a warning during build which caused the CI to fail:
Error: This expression has type unit -> unit
       but an expression was expected of type unit
       because it is in the left-hand side of a sequence
       Hint: Did you forget to provide `()' as argument?

(The Vim.AutoCommands.onDispatch returns a function that you can call if you want to unsubscribe - which we don't need to worry about this case, we'll subscribe for the lifetime of the app. But I added a let _ =  to suppress the error)
I pushed that change up - will bring this in once it's green -

Thanks,
The CI still fails but I don't really understand why and if it's related to the code.
Do you have any idea?

@tatchi - I just checked it out, it looked unrelated to the code - seems there were some '502' errors coming from NPM when installing packages (maybe related to the cloudflare outage yesterday).
Kicked it off again and it passed now - will bring it in now. Thank you for the contribution!

authors: CLAassistant bryphe tatchi


text:
Onnx model converted from hdf5 model has lstm nodes with different dimensions for bias and kernel

The keras model:

After conversion, the onnx model has transpose after every node and the dimension for bias on lstm nodes have changed from [2000] to [1,4000]. Although after 2000, all the values are 0. Is the conversion correct in this case?

The dimension mismatch is because onnx and keras have different specs, please check onnx spec, it says the bias tensor has shape [num_directions, 8*hidden_size], others are 4*hidden_size, so it is 2x, which is correct.

@jiafatom Thanks for the quick reply!
The hdf5 model has dynamic batch size(?) in input/output placeholder, the output placeholder of the converted onnx (same model as above) shows 0 as batch size.

Should it not be '-1' or '?' instead of '0'?

Can you pull latest keras2onnx master to try? It should be 'N' for both input and output batch.

Thanks, it works!

authors: jiafatom tijithomas

repo: onnx/keras-onnx


text:
Use LLVMBuider to simplify generating LLVM code - Part 2

Thi patch continues PR #1498 and creates a helper function IfThenElse in LLVMBuilder.
This patch also adds a check to verify non-negative dimensions of the input tensors, reported here #1506
Signed-off-by: Tung D. Le tung@jp.ibm.com

Jenkins Linux s390x Build #6455 [push] Use LLVMBuider to simpli... started at 20:34

Jenkins Linux amd64 Build #6439 [push] Use LLVMBuider to simpli... started at 19:35

Jenkins Linux amd64 Build #6439 [push] Use LLVMBuider to simpli... passed after 1 hr 12 min

Jenkins Linux s390x Build #6455 [push] Use LLVMBuider to simpli... passed after 1 hr 32 min

authors: jenkins-droid tungld

repo: onnx/onnx-mlir


text:
Support for playing sound files

It would be nice to be able to play sound files. This is how it would be done in C:
ca_context_play(ca_gtk_context_get(), 0, CA_PROP_MEDIA_FILENAME, path, NULL);

I've implemented this myself. It was not difficult after all. I can make a pull request, but I have a doubt about the "media.role" property. I've added it like in the Event case, but I have the same problem in both: setting Role to Music plays the passed event id or file, but if I pass Event, no sound is played. Is that a problem of my system (Ubuntu Linux 18.04) or is it how it is supposed to behave?

In both cases the sound should be played. If you set Role to Music then it shows up in pavucontrol. With Role set to Event it won't show up but can still be heard.

how does the modified package spec of your patch look like?

I added a Play_File procedure:
   procedure Play_File
     (Object      : in out Context;
      Filename    : String;
      Event_Sound : out Sound;
      Kind        : Role   := Event;
      Name        : String := "")

I'll make the pull-request in a second so you can take it, if you want.

API looks ok. Does the body re-use the same code as the Play procedure? The only thing that is different is that "event.id" is replaced with "media.filename". So it's best if the Play and Play_File call some private procedure.

In both cases the sound should be played. If you set Role to Music then it shows up in pavucontrol. With Role set to Event it won't show up but can still be heard.

I see now. It turned out that effects on my system were almost silenced. It can be heard now as Event.

authors: mgrojo onox

repo: onox/canberra-ada


text:
No such file or directory:'/llnerf-dataset/***/transforms.json'

When I try to run "bash train.sh",I firstly got the FileNotFoundError:"No such file or directory:'/LLNeRF/llnerf-dataset/book/transforms.json'."Then I tried all the datasets, but none own the 'transforms.json'. Could you help solve this problem? Thanks so much!

Please check the subfolders of the dataset, this problem may be caused when the colmap folders are not found (https://github.com/onpix/LLNeRF/blob/4efa39cbebd3c0685972cfb2d86bb9c2d65603d0/internal/datasets.py#L592)

Thank you very much for your response. I have successfully reproduced your code with my own dataset now. I have some questions about the output results and would like to ask which of the 120 images are the final results. Also, can I convert the results to mesh files or PLY files to view them in applications like MeshLab? Looking forward to your answer. Thank you!

authors: onpix usernameforu

repo: onpix/LLNeRF


text:
Add two very simple examples of using doctest with CMake

Description
I was hoping it might be possible to add a couple more minimal examples of how to set up and use doctest.
I found the existing examples helpful but there's also quite a lot going on in each. They can be a little confusing/intimidating to a newcomer to the library. These two new examples provide the bare minimum for using doctest with a plain exe or a dll.
There may well be some stuff I've missed and I'm happy to provide more info in a README file if you think that'd help. If you can think of better names or locations for the examples please let me know too.
The library is brilliant by the way and I'm hoping to use it a lot more in the future! 😄
Thanks!
Tom

I moved them in a different directory:
https://github.com/onqtam/doctest/tree/master/examples/installed_doctest_cmake

Awesome! Thank you for the merge :)
Sounds perfect, much appreciated!

repo: onqtam/doctest


text:
Cli tool broken on windows 11

I followed the steps at https://onyxlang.io/docs/install but
When I run onyx package init inside a empty folder I get an multiple errors
Unable to resolve symbol 'main'. Did you mean 'map'?
101 |     #local MAIN_FUNCTION :: main.main
Expected this condition to be compile time known.
135 |     #if (typeof MAIN_FUNCTION) == #type () -> void { // An error on this line means no 'main.main' was found in your program.
Package 'main' not found in included source files.
100 |     use main

This was an huge oversight on my part, but I forgot to include the package manager in the Windows distribution of Onyx. This will be fixed in the next release, but for now there is a fix described in #38.
It boils down to manually creating the tools directory in your ONYX_PATH, and downloading the onyx-pkg.onyx file from here and putting it in the new tools directory.
Hope this fixes the issue!

authors: brendanfh mfbulut

repo: onyx-lang/onyx


text:
Fix support for zotero cloud storage

I use the zotero cloud for storage and the script is telling me
Error downloading file! Abborting...

when I try to push

Hey, thanks for using the app. It's been a while since I have worked on it and it is possible that the api has changed or II need to update dependencies. Also, as I use webdav storage, the support for the zotero cloud storage is experimental in the sense that I had nobody to test it.
I have an important deadline coming up in the next days, but I would like to revisit the app after that. If you'd be willing to test zzotero cloud storage, that would help a lot!

I got the download working just a small issue, will provide a PR


text:
Builder version updated to 11.0.3 and some doc updates

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Codecov Report
Base: 96.10% // Head: 96.05% // Decreases project coverage by -0.05% :warning:

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #157      +/-   ##
==========================================
- Coverage   96.10%   96.05%   -0.05%
==========================================
  Files          25       25
  Lines        2126     2126
==========================================
- Hits         2043     2042       -1
- Misses         83       84       +1

Flag
Coverage Δ

unittests
96.05% <100.00%> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

open_ce/__init__.py
100.00% <100.00%> (ø)

open_ce/utils.py
93.99% <0.00%> (-0.43%)
:arrow_down:

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

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

Codecov Report
Base: 96.10% // Head: 96.10% // No change to project coverage :thumbsup:

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   96.10%   96.10%
=======================================
  Files          25       25
  Lines        2126     2126
=======================================
  Hits         2043     2043
  Misses         83       83

Flag
Coverage Δ

unittests
96.10% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

open_ce/__init__.py
100.00% <100.00%> (ø)

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

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

Codecov Report
Base: 96.10% // Head: 96.10% // No change to project coverage :thumbsup:

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   96.10%   96.10%
=======================================
  Files          25       25
  Lines        2126     2126
=======================================
  Hits         2043     2043
  Misses         83       83

Flag
Coverage Δ

unittests
96.10% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

open_ce/__init__.py
100.00% <100.00%> (ø)

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

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

authors: codecov-commenter npanpaliya

repo: open-ce/open-ce-builder


text:
Update user keys in running VMs

As new users are added to / removed from slices, it would be nice if the change is reflected in the authorized_keys file inside the VM as well as the user account used for proxy login.  This functionality is outside of the scope of OpenStack's key injection feature, which is only triggered on VM creation.

Is this feature request still relevant?

It's still on our wish list but perhaps it's low priority.
Anyhow, one part of the problem has been solved: dynamically updating the keys for the external user account.  Scott added an XOS API call to extract the keys for an instance. On the compute nodes a cron job runs this script to pull the keys from XOS and save them in the right place:
https://github.com/andybavier/opencloud-nova-compute-ansible/blob/onlab/files/usr/local/sbin/download-keys.py
So the missing piece is adding similar functionality inside the container.  Maybe a simple daemon that pulls keys using the XOS API could be injected into the VM using cloud-init.

authors: andybavier gwsapan

repo: open-cloud/xos


text:
Doc: Clarifying README - minor updates

Signed-off-by: yue9944882 291271447@qq.com

/lgtm


text:
Use the consolidated sync controller

This uses the new governance-policy-framework-addon controller which replaces the separate containers for spec-sync, status-sync, and template-sync.
Relates:
https://github.com/stolostron/backlog/issues/25999

@JustinKuli and @dhaiducek this is ready for review.

/unhold

authors: dhaiducek mprahl


text:
Add Pending to complianceState enum

Signed-off-by: Will Kutler wkutler@redhat.com
Needed to set the Pending status on parent policies

/cc @JustinKuli

Good catch!

authors: JustinKuli willkutler


text:
register placementrule reconciler when its CRD is installed.

A fix for: https://github.com/open-cluster-management/multicluster-observability-operator/pull/400
Only register placementrule reconciler when its CRD is installed.

/lgtm


text:
Version bump 2.1.7 and multiclusterhub rename

https://app.zenhub.com/workspaces/engineering-backlog-do-not-delete-604fab62d4b98d00150a2854/issues/open-cluster-management/backlog/10938

Good catch Jake

/approve

/lgtm

authors: JakobGray nathanweatherly zkayyali812


text:
Update lightarea.is-cool.dev.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.

Description

Updated cname
Link to Website

LightArea.is-cool.dev

@WilliamDavidHarrison can you please merge these

@DEV-DIBSTER can you please merge this

Bro website is at lighthostingfree.github.io/LightArea
That's why I want to set cname of lighthostingfree.github.io

@DEV-DIBSTER

repo: open-domains/register


text:
Register jay.is-cool.dev

Added jay.is-cool.dev using the CLI.

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA


text:
Define and implement a caching strategy

Overview
Flag evaluation using FlagD is done via inter-process communication. While the overhead is minimal, it can be effectively eliminated with an in-memory cache.
Proposal
Implement a basic caching strategy in FlagD providers that support server-to-client streaming. Flags without a targeting rule defined can cache flags flag until the configuration changes. The server-to-client stream can be used to bust the cache when a flag is updated.
Considerations

Cache busting requires a change event.
Connection errors with FlagD should bust the cache

Requirements

[ ] #223
[ ] Update FlagD to return caching metadata
[ ] Update at least one FlagD provider to include a cache - https://github.com/open-feature/go-sdk-contrib/issues/44

@beeme1mr
Is a doc in the flagd repo the best place to document the strategy? We can give guidelines there but ultimately it's up to the providers to implement it.
What caching metadata did you have in mind? The Reason is already an emitted field by flagd, I think it's sufficient to cache the value based on  Reason != "TARGETING_MATCH", if you agree I don't think there's any need for flagd to emit anymore data at this stage.

TARGETING_MATCH (and reasons in general) provide some helpful data on caching, but they don't solve the entire problem. One of the most valuable things to cache would be flag values with no rules, but the reason for any particular evaluation doesn't tell us that rules don't exist. For example, a set of targeting rules that don't match at all will default, and so the DEFAULT reason is returned. That doesn't mean that we can cache that value, since the next evaluation may have different context and match a rule.
We may be able to solve this only with additional reason codes and changes to reason semantics within flagd, but I think some additional work is needed.

@toddbaert good point, thanks, I hadn't considered that flagd would return DEFAULT if there are rules that simply weren't met.
My preference would be to use the Cache-Control HTTP header for this, we can set it to no-store in the cases where dynamic evaluation is applicable. Otherwise leave it empty, I don't think setting a max-age is necessary given that it ought to survive until busted.

I would like to have caching optional personally. I have a few scenarios where I am using flagD in the kernel and it's not something I can see a use for if I am interacting via curl - Though in that situation, looking at the above, are you suggesting we set a cache-control header at 0 to avoid caching?

@AlexsJones this documents the current strategy: https://github.com/open-feature/flagd/pull/224/files#diff-68a93cfd67d08237c7e69ffd89a7438adeb9b3671cb292d07803e0cdba4daba3
Feedback, as always, is welcome
TLDR; it's up to clients to decide whether to cache or not, flags that are safe to cache have the reason STATIC (we've decided against using the cache-control header). In the future this may be extended to handle dynamic evaluations too.

Closed with https://github.com/open-feature/go-sdk-contrib/issues/44

authors: AlexsJones beeme1mr skyerus toddbaert

repo: open-feature/flagd