text:
Grid does not work as expected (small != 12)

The grid does not work as expected. If I use a less number then 12 for small view, the columns still collapse as 12. The following example is from the offical foundation for emails/inky templates. (https://github.com/zurb/foundation-emails/tree/v2.0/test/visual/pages)
Example HTML:
<container>
    <row>
        <columns small="12" large="2">

(small="12" large="2") One Word

        </columns>
        <columns small="4" large="4">

(small="4" large="4") Lorem ipsum dolor sit amet, consectetur adipisicing elit. Fuga repellendus velit aut perferendis, eveniet delectus maxime quisquam recusandae assumenda culpa tenetur dolorem error voluptatibus. Animi accusamus molestiae placeat, sequi beatae.

        </columns>
        <columns small="8" large="6">

(small="8" large="6") Lorem ipsum dolor sit amet, consectetur adipisicing elit. Veritatis quis obcaecati facere dolore laborum officia rem praesentium cumque culpa delectus alias ullam ad, doloremque, ipsa asperiores ex sit necessitatibus minima!

        </columns>
    </row>
</container>

Desktop view (large):

Desktop view (small):

Hmmm, we can't replicate this behavior

To make sure you are using the latest build, you can update you package.json file to grab the latest code on v2.0
"foundation-emails": "zurb/foundation-emails#v2.0"
And make sure you have inky set to
"inky": "^1.2.3",
and run npm update
Let us know how that works for you!

I'm up to date. ;)
I found out that the behavior only occurs if I dont inline the css "npm start" instead of "npm run build".
I don't know if this is a use case for someone or for you.
Thanks for the fast reply.

That's weird, seems to work both inlined and not. Since this grid has been through some extensive testing, we can't treat it as framework bug. Thanks for the report!

authors: nwerr rafibomb

repo: zurb/foundation-emails


text:
large-pull not working anymore?

Hi!
I am not an expert at zurb foundation, so please bear with me.
I was using Zurb foundation 6.3.1 but has updated to 6.4.0.
Successfully converted from "row" to "grid-container". But I cannot seem to find where large-pull and push went?
Old html looks like this:

On large the sidebar comes on the right side and the maincontent on the left.
On medium the sidebar take upp full width, and comes first, maincontent below.
It is more or less a copy-paste from the zurb example pages.
My question is: How do I acheive this with the new grid-container ?
I posted my question here as well: (Feel free to give the answer at stackoverflow as well)
https://stackoverflow.com/questions/44846865/zurb-6-4-0-where-did-the-large-pull-3-go

As far as I'm aware, the new XY Grid doesn't utilize the large-pull- classes, but it does use the large-offset- classes.

@codetheorist is exactly correct. Push and pull are a bit of a hack solution necessary for Float based grids, but the XY grid is a flexbox based grid which allows you to explicitly order things by breakpoint. Check out the offset classes here: http://foundation.zurb.com/sites/docs/xy-grid.html#offsets

@Snorvarg Seems like what you are looking for sits right here
http://foundation.zurb.com/sites/docs/flexbox-utilities.html#source-ordering

@IamManchanda, I cannot find "medium-order-" when I search among the css-files.. I use 6.4.0, but downloaded and searched the files for version 6.4.1, nowhere to be found..?

@Snorvarg No its in there
If you are talking about this line
Its in here => https://cdnjs.cloudflare.com/ajax/libs/foundation/6.4.1/css/foundation.css
[ Line 5401 ]
If talking about repo, it's here in sass stuff https://github.com/zurb/foundation-sites/blob/develop/scss/components/_flex.scss#L107-L113

@codetheorist, could I use a negative offset with large-offset- ? Maybe I don't get your point, how would I make the two columns switch place with large-offset ?

@Snorvarg @codetheorist @kball I have used these classes
Offset is not the right classes for this
Source ordering is the right classes for this!

@Snorvarg Just to confirm, the correct markup based on your example would be:

Yes exactly
@brettsmason Do we need some docs copy here ??

@IamManchanda Maybe we need a small section with a demo then point to the flexbox utilities listing for it for more details. Something along the lines of you need to include the flexbox utilities in order to do this etc etc.

Ohk let me dig in :smile:
Reopening

@IamManchanda, you are right, it's there! I think I somehow got v6.4.0, and there it is not. I did a file compare, it is added in 4.6.1.
Now it is working.
Thanks for the great work guys, zurb is great to work with! (Fully aware of the tremendous work with keeping the docs up to date)

@IamManchanda, you are right, it's there! I think I somehow got v6.4.0, and there it is not. I did a file compare, it is added in 4.6.1 6.4.1.

Yeah we added in 6.4.1 ... me only did that so i remember... :smile:
The problem was that those were situated in this file https://github.com/zurb/foundation-sites/blob/develop/scss/grid/_flex-grid.scss
which basically was only adding this in legacy flex grid ... :smile:
But now its working ... sigh !

Thanks for the great work guys, zurb is great to work with! (Fully aware of the tremendous work with keeping the docs up to date)

:+1:

Ohk added PR on docs update => #10318

source: gharchive/issue

authors: IamManchanda Snorvarg brettsmason codetheorist kball

repo: zurb/foundation-sites

license: mit

license_type: permissive

license_source: bigquery


text:
F6 block grid and sass promblems

hello, i need help with new grid system:
i need to use custom classes in foundation 6.
Example:
.gl{@include grid-row(3); border: 1px solid green;}
.wp{@include grid-column; border: 1px solid orange;}
it looks like: http://awesomescreenshot.com/0225fm6u1e
at the bottom i show a example from docs. so where is the problem?

The column needs to be nested inside to define
.gl {
@include grid-row(3) {
.wp {
@include grid-column(1);
}
}
}
I'll close this as it should solve your issue, but feel free to reopne if it hasn't

authors: sashafokin zurbrandon


text:
Input[type="search"] has incorrect box-sizing property (a.k.a Update normalize).

How can we reproduce this bug?

Create <input type="search" />
See that box-sizing: content-box is set
See that normalize.css is out of date

What did you expect to happen?
Expected normalize.css NOT to be embedded in foundation (Seems like its hard to upgrade—maybe there is a better way of handling this [see below for context]?).
7 days after release of 3.0.3, https://github.com/necolas/normalize.css/commit/fe567632afcf8afcf17925ab2a507ed87504cce8 was introduced. Also, normalize is currently at 4.1.0 (https://github.com/necolas/normalize.css/releases/tag/4.1.0).
TLDR, just recommendation, overall extreme limited context of this repo.
What happened instead?
See that @include foundation-global-styles, added in https://github.com/zurb/foundation-sites/issues/7159, is on version v3.0.3.
Test case:
http://codepen.io/chemoish/pen/NNYWEw

I'm all for making this change:

But I don't know the reasons why Normalize is hardcoded.

+1 for updating Normalize.

+1 for updating Normalize

normalize-scss is a fork of normalize and does not provide the latest changes from normalize. Imo we should switch to a pure normalize implementation.

Closing as https://github.com/zurb/foundation-sites/pull/11086 is merged now.
Feel free to reopen if the error still exists.

authors: DanielRuf Lynda333 andycochran chemoish rgalus


text:
chore: improve "tree shaking" support and documentation

Description

This pull request change some Foundation entries so they better follow the recommended practices and should be better analyzed by bundlers in order to enable tree-shaking. Also, it adds a section in the "Javascript" documentation with advices to reduce the final bundler size.
Changes

Add a simpler export file js/foundation.js
Use js/foundation.js instead of js/entries/foundation.js
Add default export as it may be sometimes required for tree-shaking
Add "Tree Shaking" section in javascript documentation

Others changes

Add missing export of Move in "foundation-plugins" entry

Related to https://github.com/zurb/foundation-sites/issues/11401

Types of changes

[x] Documentation
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to change)

Checklist (all required):

[x] I have read and follow the CONTRIBUTING document.
[x] There are no other pull request similar to this one.
[x] The pull request title is descriptive.
[x] The template is fully and correctly filled.
[x] The pull request targets the right branch (develop or develop-v...).
[x] My commits are correctly titled and contain all relevant information.
[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly to my changes (if relevant).
I have added tests to cover my changes (if relevant).
[x] All new and existing tests passed.

Well I think using default export is bad practice, because it allows doing very creepy things and also breaks checks for instanceof.
Here are just some other ideas why default export never were a good idea
https://blog.neufund.org/why-we-have-banned-default-exports-and-you-should-do-the-same-d51fdc2cf2ad
https://basarat.gitbooks.io/typescript/docs/tips/defaultIsBad.html
Another thing to consider is, that named exports also help with not breaking the API. If you have a default export every change to this export is possibly a breaking change.
So just never ever use default exports.

@DaSchTour I'm aware of this but it seems even Twitter Bootstrap (and many others) use export default, see https://github.com/twbs/bootstrap/blob/v4-dev/js/src/carousel.js#L520

It is not recommended to use default imports. But I remember that in some environnements they may be the only possible solution, and seems to work better with tree shaking. I'll try to find back the articles explaining this.

@DaSchTour default export is not bad imo – if used correctly.
If someone misuses it to bundle several export in one default export it's of course bad practice and interferes with tree shaking. So you shouldn't do
utils.js
function triple(val) {
  return val * 3;
}
function double(val) {
  return val * 2;
}
export default {
  triple: triple,
  double: double
};

app.js
import utils from './utils';
console.log(utils.triple(10));

but instead do
utils.js
export function triple(val) {
  return val * 3;
}
export function double(val) {
  return val * 2;
}

app.js
import { triple } from './utils';
console.log(triple(10));

In contrast if you've a module that has just one export because it doesn't make sense to import partials of it then it's absolutely ok in my eyes to use export default. This happens if there's just one main function or class.
super-carousel.js
class SuperCarousel {
  constructor() {
    console.log(`I'm a super carousel!`);
  }
}
export default SuperButton;

app.js
import SuperCarousel from './super-carousel';
const carousel = new SuperCarousel();

@SassNinja I removed "grouped" named exports:

Default exports should only be used for "primary" objects or classes, not for libraries for which individual named exports should be prefered.

Also, I kept named exports at the end of the files. See https://github.com/airbnb/javascript/issues/1275#issuecomment-274367523

@DaSchTour IMHO default imports are not a good import practice, but it is not a bad export one. There is many situation where default imports is the only solution, like when trying to simply transition from ES5 to ES6 (so from CommonJS to ESM modules) or when module imports are handled and/or transpiled by the framework's CLI (like for Ember).

@ncoden I know this is a constructed scenario. But one thing that can happen with default exports, for example because of somebody making a mistake while resolving merge conflicts, you end up with code like this
import Reveal from 'foundation-sites/js/foundation.dropdown';
import Dropdown from 'foundation-sites/js/foundation.reveal';

This is not an error and with JS you might search for hours to find the reason why everything is messed up.

@DaSchTour Yes. Default imports should be avoided when possible for this reason. But we should still propose default import for the reasons given above, even if we do not encourage it.

@ncoden I don't see any reason why default imports should be possible. In general I wonder why put so much effort into making foundation 6 tree shakable or why put any effort into foundation 6 at all while everybody is waiting for 7.

why put so much effort into making foundation 6 tree shakable

Because fixing and cleaning the ESM+AMD+CJS+static imports (which is a big "feature" of the v6.5.0 release) goes with providing efficient ways to use them in each of these environnement. And IMHO this means allowing to import single plugins without importing the whole framework (which is unexpected when you have the ability to cherry-pick feature).

why put any effort into foundation 6 at all while everybody is waiting for 7

Good question. Personally, I'd like to get Foundation 6 stable before we take 6-12  months to prepare and work on Foundation 7. But I recognize that this step took way much time than expected. I am sorry about that.

Good question. Personally, I'd like to get Foundation 6 stable before we take 6-12 months to prepare and work on Foundation 7. But I recognize that this step took way much time than expected. I am sorry about that. – @ncoden

I don't think it's wrong to enable using Foundation v6 with module bundler the way users expect (import only certain plugins).
It may seem a bit waste of time regarding v7 but I think it's more important to ensure a good usability of the existing version. If users get pissed of using Foundation they may not wait until v7...

@SassNinja well I guess some users already won't be waiting for v7. It's called Osborne effect.

@DaSchTour @SassNinja Could we not enter into meta-discussions about the global Foundation roadmap and focus on the current issue ? Time matters, everyone agree on that, but we're not saving any with this kind of discussion. For now I'd like to get this PR approved/rejected to release RC3.

@SassNinja
I adapted the message so direct imports are only recommended if tree-shaking doesn't work, "depending on your build environment". Are you good with this ?
@jdalton
I added the sideEffects flag, I think this is the best I can do.

I adapted the message so direct imports are only recommended if tree-shaking doesn't work, "depending on your build environment". Are you good with this ? – @ncoden

Not really :/
But I've now set up a simple webpack config using your feature branch and tree shaking did work without problems. The only downside is all plugins still appear in the stats but the emitted JS code looks good.
// webpack.example.js

const path = require('path');

module.exports = {
    mode: 'production',
    devtool: 'none',
    entry: {
        'example': './example.js'
    },
    output: {
        path: path.resolve(__dirname, 'dist-example'),
        filename: '[name].js'
    },
    externals: {
        jquery: 'jQuery'
    },
    optimization: {
        minimize: false,
        runtimeChunk: 'single'
    }
};

// example.js

import { Abide } from './js/foundation.js';

console.log(typeof Abide);

How did your setup look where tree shaking isn't working?

@SassNinja See https://github.com/ncoden/foundation-sites-tree-shaking

@SassNinja I cannot make tree shaking work with your configuration. Could you share your dummy project in a repo ?

I cannot make tree shaking working with your webpack configuration. Could you share your dummy project in a repo ?

Here's an example repo:
https://github.com/SassNinja/example-foundation-sites-tree-shaking
I think I know what went wrong on your side because I also faced an issue when creating that example repo. To work the bundler needs to take the module field in the package.json what webpack does not do by default.
So you need to override it like this
resolve: {
    mainFields: ['module', 'browser', 'main']
}

Thank you. Too bad that the webpack documentation about tree shaking doesn't mention it.

Maybe we should adjust our package.json to fix this without the need for additional bundler config. The browser field looks promising to me.
See https://github.com/webpack/webpack/issues/4674#issuecomment-355853969
What do you think?

I've simply replaced the field name module with browser.
Afterwards it's working for me without further bundler config (tested webpack).

A radical idea: what about removing the whole entries folder?
I think if you use a module bundler (and therefore probably want tree shake) you have to include the desired plugins via
import { Abide, OffCanvas } from 'foundation-sites';

We can provide a list with all plugins imports for copy & paste.
And people who wanna import the whole framework without a module bundler (e.g. when using gulp without any bundler in the task) may use the dist file directly.
We could also cover the dist case with an export default but I don't see any useful reason to offer something like
import FoundationEverything from '../dist/js/foundation.js';
export default FoundationEverything;

I've simply replaced the field name module with browser.
Afterwards it's working for me without further bundler config (tested webpack).

Thank you, I'll test this tonigh and update the pull request.

A radical idea: what about removing the whole entries folder?

Hmmm, this would break backward compatibility so it's definitely not for this pull request. For v6.6.0, maybe if it enables anything useful. But for now I don't see any advantages for us or our users.

I removed the browser field it and it works well. According to the specs there is no reason for us to use a browser field as the package itself it only for browsers (or any environement with a DOM). With this configuration, ESM-compliant transpilers/bundlers will pick module, and the others will pick main.
There is still one problem too: the "picked" code is not only a ESM bundle, but also ES6 code. Webpack will use module because it's an ESM bundle but will not transpile the ES6 stuff...
So I think we should also provide our distribution files in the .esm.js format: a transpiled file BUT with ESM exports untouched, and use it for the module field.
See for example the Vue dist folder: vue.js (UMD), vue.common.js (commonJs) and vue.esm.js (ESM)
What do you think ?

According to the specs there is no reason for us to use a browser field as the package itself it only for browsers (or any environement with a DOM).

Alright then let's ditch browser and only use main and module

Webpack will use module because it's an ESM bundle but will not transpile the ES6 stuff...

I don't understand this – what do you mean?
The code gets picked up by the bundler which understands ES6 and resolves all dependencies. If necessary it can be transpiled to ES5 using e.g. the babel-loader.

See for example the Vue dist folder: vue.js (UMD), vue.common.js (commonJs) and vue.esm.js (ESM)

I think a transpiled ESM file is nice to speed the build process up as there's no need then to transpile node_modules yourself (while preserving tree shake support).
However we should also offer an untouched file imo (see vue.esm.browser.js) for people who don't need any pre transpilation.

However we should also offer an untouched file imo (see vue.esm.browser.js) for people who don't need any pre transpilation.

You are right. I'm going for the following: foundation.js (UMD), founcation.cjs.js (commonJs), foundation.esm.js (transpiled ESM module), foundation.es6.js (untouched ESM module).

What is the difference between transpiled ESM module and untouched ESM module? Transpiling ESM module to let's say ES5 would make it "remove" modules because ES5 doesn't have modules. And I think any kind of processing might possibly hurt treeshaking and also minification.

What is the difference between transpiled ESM module and untouched ESM module? Transpiling ESM module to let's say ES5 would make it "remove" modules because ES5 doesn't have modules. – @DaSchTour

That's why I wrote foundation.esm.js would still contain ES6 code, precisely the import/export stuff.
But compared to foundation.es6.js (@ncoden maybe we should rename it to avoid confusion?) it's compiled to ES5 except of all import/export.

And I think any kind of processing might possibly hurt treeshaking – @DaSchTour

afaik webpack requires ES6 import/export for tree shaking. If we preserve that on transpilation it shouldn't be a problem and improves the build time because users can exclude foundation from their own ES5 transpilation then.
Anyway this has to be tested of course (haven't done this yet).

Some bundlers (webpack, rollup...) supports the ES6 module format and require to use it for tree shaking but will leave the other ES6 stuff intact (they are bundlers, not transpilers). foundation.esm.js is transpiled ES5 code embeded in ESM modules for those bundlers. foundation.es6.js is untouched ES6 code and modules that can be manually transpiled by our users depending on their targets.

@SassNinja So I made (a lot of) tests:

ESM6+ bundles (es6+ in es modules) are correctly shaked by both Webpack and Rollup.
ESM5 bundles (transpilled es5 in es modules) are not shaked, despites being marked as __PURE__ by Rollup. This comes from static properties defined outside of the class like <plugin>.defaults = { ... }, and plugin initializations in entry files.

There is no other way to define static properties for now. There is a TC39 proposal for this but the Babel plugin generate code outside of the class closure, making it incompatible with tree sharking.
For now I think we can go with only an ES6+ version directly from the sources (so Webpack/Rollup users will have to transpile the code), and I'll do some refactor later to allow us to provide shakable transpiled bundles.
I removed pkg.browser, and improved the "tree shaking" section in the installation documentation to promote named imports over "manual" imports. What do you think ?

There is no other way to define static properties for now. There is a TC39 proposal for this but the Babel plugin generate code outside of the class closure, making it incompatible with tree sharking.
For now I think we can stay with the ES6 sources in pkg.modules (so Webpack/Rollup users will have to transpile the code), and I'll do some refactor later to allow us to provide shakable transpiled bundles.

Ok, then let's stay with untranspiled ES6 code in the module field.
Would be of course much better if users don't need to transpile node modules themselves but does not make sense if tree shaking doesn't work correctly anymore.

I removed pkg.browser, and improved the "tree shaking" section in the installation documentation to promote named imports over "manual" imports. What do you think ?

Docs lgtm :+1:
The only thing I still doesn't like is the usage of named and default export in the plugins that export the same.
I've only tested webpack and there it also works without default export.
But you've also tested other bundlers and noticed it's necessary to have default exports, haven't you?

@SassNinja Thank you for the review :)

But you've also tested other bundlers and noticed it's necessary to have default exports, haven't you?

I remember that yes, but I'll check again just to be sure.

I tested, and issues actually come fron side-effects in the "fully-initialized" browser entry js/entries/foundation.js. But we can't move it from there as this is how Foundation is used: import { Foundation } from "foundation-sites"; // already initialized

source: gharchive/pull-request

authors: DaSchTour DanielRuf SassNinja ncoden


text:
fix: Fixed submenu bounce if nested

Description
If you have a nested submenu where you want to have open submenus at the beginning.

Current behaviour:
The submenu will bounce up and come down again.
Desired behaviour:
The submenu will stay open and not bounce.
Types of changes

[ ] Documentation
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (anything that would change an existing functionality)
[ ] Maintenance (refactor, code cleaning, development tools...)

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] The pull request title and template are correctly filled.
[x] The pull request targets the right branch (develop or develop-v...).
[ ] My commits are correctly titled and contain all relevant information.
[ ] I have updated the documentation accordingly to my changes (if relevant).
[ ] I have added tests to cover my changes (if relevant).

Hi @pascalknecht 👋,
Thank you for your pull request. The next time, please open an issue too, with an easy way to reproduce the bug. I took care of this this time: https://codepen.io/ncoden/pen/BGrwQE.

Hi @ncoden . Thanks for the feedback.
Glad my first pull request for foundation has been approved. How long does it usually takes for bugfixes like these to land in a release?

It depends. v6.5.0 took 1 year to release, and v6.5.1 took 2 weeks 😉.

authors: ncoden pascalknecht


text:
Minify breaks even button-group

I'm experiencing trouble with my even-4 button-group. It turns out the even-part breaks after you minify it, but I wouldn't know why. See the picture below for an illustration. The first one is the original code, the second one is the minified one.

The example above has the following code, which is working fine as you can see in the above image:

As soon as it get's minified, it breaks the 'even' part. In my case it's automatically minfied, but I found out it doesn't matter if it's minified automatically or just by hand. If I put the code on one line like in the example below, it breaks in the same way.

In my eyes, it's strange that this happens. Why wouldn't it be possible to put this code on just one line? Works for every other kind of list.

This is happening because the items within a button group use the property display: inline-block. So it looks slightly different if the list items do or don't have a whitespace character between them. (HTML counts a line break as a whitespace character.) Here's an explanation of why inline-block elements generate extra whitespace.
The ideal way to fix this is to use floats instead of inline-block. It wouldn't be hard to implement, I'm just not sure if it constitutes a breaking change or not. Visually it would look identical, but structurally it would be slightly different.
We've already fixed this in Foundation 6, and since 5 has been out for quite a while right now, we might want to leave this as-is. As for a fix, if you know that your HTML will always be compressed, you can add back in the spacing by hand:
.button-group li:not(:last-child) {
  margin-right: 1px;
}

@gakimball Good point, thanks for explaining. I should have thought about this solution myself haha. It works quite good. I will wait for F6 for the definitive solution.

authors: Tralapo gakimball

repo: zurb/foundation


text:
2022.2 Version is Launched

Any chance to get a new version for 2022.2, released yesterday? 👍🙏

Thanks for reminding 😊 Will do later today!

Published. Should appear soon once moderation will be done.
BTW still decided to not opt-in into floating version, so I can quickly re-test it for each version of R#. For most of the updates I actually had to tweak the code to fix the complication, so do not see huge win from that anyway 😉
So thanks for doing a good service and keep reminding me of updates 😊

Happy to help!
🙏🙏🙏

authors: Mike-E-angelo zvirja

repo: zvirja/ReSharperHelpers

license: MIT

license_source: github-api


text:
NeoVim: Messing up cursor shape for normal/insert

I have my neovim setup to show a block cursor in normal mode and a beam cursor in insert mode. I just installed TabNine and nothing else new. Now, I only have the beam cursor. I'm running the SpaceVim configuration as well (I'm still actually learning Vim after switching from Emacs/SpaceMacs configuration). Also, indentLine isn't loading anymore and when I go into insert mode, it asks me to install indentLine plugin. I no longer have my lines for the indention showing, but they were before installing TabNine.

I found my problem. I had a setup error in my working folder calling vim instead of neovim. So, neovim seems to be working fine, but vim 8.0 doesn't. But, since I don't use vim, it doesn't matter.

repo: zxqfl/TabNine


text:
移动端不能进入编辑界面，在文件目录页面下点开任意一个文件就会显示页面错误

这部分功能还未实现，哈哈。
最近忙于秋招，没时间写了。等秋招结束会进行完整实现。感谢关注。

这部分功能还未实现，哈哈。 最近忙于秋招，没时间写了。等秋招结束会进行完整实现。感谢关注。

学长太强了吧，准大三的菜鸟给学长递烟😂。祝学长拿到心仪的offer，明年可以有机会去找你内推 哈哈哈 （暑假才开始自学vue，之前自己看过一点nodejs，参照着学长的项目学到了很多。现在仍在摸索研究中，希望开学之后能帮学长完善项目的文档说明啥的吧 respect🫡）

authors: seasnakes zyascend

repo: zyascend/ZMindMap-Mobile


text:
Removes REQUIRE file and updates Project.toml

Removes upper bound on Images package

I think you could just delete Manifest.toml; it'll be generated if not existed.

@JuliaRegistrator register()

Pull request comments will not trigger Registrator as it is disabled. Please trying using a commit or issue comment.


text:
Super Tabs orientation bug @ Android

Hello,
Super Tabs by default has a scss tag that is 'min-width' that is placed to 50px but it's causing an orientation problem on my project. As I remove it, it solves but it's not a worth kind to do, so how do I fix it?
Preview:
https://i.imgur.com/AOWXUFk.png

By p-sebastian:
for anybody having this issue adding that, fixes it.
page-home {
super-tabs {
super-tab-button {
flex: 0 0 auto !important;
}
}
}

By p-sebastian:
for anybody having this issue adding that, fixes it.
page-home {
super-tabs {
super-tab-button {
flex: 0 0 auto !important;
}
}
}


text:
use new .get_probability() from zyte-common-items==0.12.0

Following the 0.12.0 release of zyte-common-items which contains this new feature: https://github.com/zytedata/zyte-common-items/pull/65

Codecov Report

Merging #7 (9114917) into main (755dbd8) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head 9114917 differs from pull request most recent head 0c97bee. Consider uploading reports for the commit 0c97bee to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
- Coverage   99.10%   99.09%   -0.02%
==========================================
  Files           8        8
  Lines         449      444       -5
==========================================
- Hits          445      440       -5
  Misses          4        4

Files
Coverage Δ

zyte_spider_templates/spiders/base.py
97.61% <100.00%> (-0.16%)
:arrow_down:

zyte_spider_templates/spiders/ecommerce.py
94.23% <100.00%> (-0.22%)
:arrow_down:

authors: BurnzZ codecov-commenter

repo: zytedata/zyte-spider-templates


text:
No module named utils

O running run_timit.sh I am getting following error
saurabh@saurabh-Inspiron-5559:~/saurabh/asr_new/main$ sudo pip install utilsThe directory '/home/saurabh/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/saurabh/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Requirement already satisfied: utils in /usr/local/lib/python2.7/dist-packages
saurabh@saurabh-Inspiron-5559:~/saurabh/asr_new/main$ ./run_timit.sh
loop index: 2
Traceback (most recent call last):
  File "timit_train.py", line 27, in <module>
    from utils.utils import load_batched_data
ImportError: No module named utils
saurabh@saurabh-Inspiron-5559:~/saurabh/asr_new/main$

Hi @saurabhvyas ,
utils is not a package which you have to install via pip. It is supplied with this repository. Are you using the latest version of the code from the master branch? As this error should not exist as we have added this line to the code in timit_train.py:
sys.path.append('../')

Best,
Hitesh

Yes, I cloned latest master branch , I recloned and followed the steps and I get the same error

@saurabhvyas Utils is a directory, have you fixed this error?

No ,  not been able to fix it .

authors: hiteshpaul saurabhvyas zzw922cn


text:
support agent revocation status; refactring resolve opts

@ilya-korotya skip revocation option is supported on sdk level and allows not to include revocation info into the circuits, so zkp will be generated without checks for non-revocation of credentials.
At this moment JS SDK will not generate proof on revoked credential despite the option skip revocation

authors: ilya-korotya vmidyllic


text:
Created Solution of Leetcode - Stock sell and buy

@1dharode I have given the solution of stock sell and buy question..please check it and merge it


text:
Add view to command summary

Codecov Report

Merging #387 (5f9f9f1) into master (23bee1c) will increase coverage by 0.47%.
The diff coverage is n/a.

:exclamation: Current head 5f9f9f1 differs from pull request most recent head 49170b5. Consider uploading reports for the commit 49170b5 to get more accurate results

@@             Coverage Diff              @@
##             master     #387      +/-   ##
============================================
+ Coverage     68.41%   68.89%   +0.47%
- Complexity     1131     1141      +10
============================================
  Files           135      136       +1
  Lines          3866     3864       -2
  Branches        521      521
============================================
+ Hits           2645     2662      +17
+ Misses          996      977      -19
  Partials        225      225

Impacted Files
Coverage Δ

.../seedu/address/model/lesson/CalendarEntryList.java
85.20% <0.00%> (-0.09%)
:arrow_down:

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/CenterPanel.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/ui/PersonGridPanel.java
0.00% <0.00%> (ø)

.../java/seedu/address/logic/commands/TagCommand.java
100.00% <0.00%> (ø)

...java/seedu/address/logic/commands/FindCommand.java
100.00% <0.00%> (ø)

...ss/model/person/NameContainsKeywordsPredicate.java
100.00% <0.00%> (ø)

...s/model/person/PersonMatchesKeywordsPredicate.java
53.80% <0.00%> (+0.29%)
:arrow_up:

.../main/java/seedu/address/logic/FeesCalculator.java
74.41% <0.00%> (+3.48%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

authors: codecov-commenter eeliana


text:
Fix minor formatting issues

Codecov Report

Merging #177 (cc5251e) into master (91316de) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #177   +/-   ##
=========================================
  Coverage     52.67%   52.67%
  Complexity      630      630
=========================================
  Files           119      119
  Lines          2863     2863
  Branches        350      350
=========================================
  Hits           1508     1508
  Misses         1266     1266
  Partials         89       89

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

.../java/seedu/address/logic/commands/AddCommand.java
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

authors: adam-ky codecov-commenter


text:
Docs: Trim User Stories

Codecov Report

Merging #244 (9bad695) into master (4638175) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #244   +/-   ##
=========================================
  Coverage     38.44%   38.44%
  Complexity      556      556
=========================================
  Files           178      178
  Lines          3283     3283
  Branches        389      389
=========================================
  Hits           1262     1262
  Misses         1883     1883
  Partials        138      138

Continue to review full report at Codecov.

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


text:
[v1.3] Implement Event Tag class

completed

authors: peienlim peterXGD


text:
Debug user guide

LGTM


text:
Update react-build.yml

LGTM!!! 🤩

[heart]         Mahmoud Mohamed Abdgelil reacted to your message:

From: AbdelRahman @.>
Sent: Saturday, December 28, 2024 9:39:49 AM
To: AbdelRahmanRahal/GradeA @.>
Cc: Mahmoud Mohamed Abdgelil @.>; Author @.>
Subject: Re: [AbdelRahmanRahal/GradeA] Update react-build.yml (PR #56)
LGTM!!! 🤩
—
Reply to this email directly, view it on GitHubhttps://github.com/AbdelRahmanRahal/GradeA/pull/56#issuecomment-2564281875, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCFAQUBX42DAVXGNFLPUMZT2HZWWLAVCNFSM6AAAAABUJEKYCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGI4DCOBXGU.
You are receiving this because you authored the thread.Message ID: @.***>

repo: AbdelRahmanRahal/GradeA


text:
Call out that by default, all the tooling uses public instances of fulcio and rekor

Addressed in a new slide (67)


text:
Create README.md

Readme güncellendi

repo: Acikgozens/C-Sharp-Project


text:
LSP Find all references does not find references in assembly

Would be also nice to implement Go to definition and Go to type definition for inline assembly external references

Fixed in #102.

repo: Ackee-Blockchain/woke

license: ISC


text:
update packages

:white_check_mark: Build TheIdServer 7.4.7-fix-dependencies1-0230 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/bd1a05c4b5 by @invalid-email-address)

authors: AppVeyorBot aguacongas

repo: Aguafrommars/TheIdServer


text:
feat(vm) : description syntax added

Please only make substantial changes - preferably in response to issues.

authors: cryptoryda vicsn

repo: AleoHQ/snarkVM


text:
Fix lints

I see, now you will be able to finally compile (somewhat) 😝

Just removing the annoyances one by one ✂

repo: AmbientRun/Ambient


text:
Rebuild libspatialite 4.3.0a for libxml2 2.10

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:18: http_url: http://archive.ubuntu.com/ubuntu/pool/universe/s/spatialite/spatialite_4.3.0a.orig.tar.gz is not https
ERROR: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:75: missing_description: The recipe is missing a description
WARNING: /tmp/abs_52ud3z8wd7/clone/recipe/meta.yaml:76: missing_description: The recipe is missing a description
Errors were found

authors: anaconda-pkg-build skupr-anaconda

repo: AnacondaRecipes/libspatialite-feedstock


text:
feat(ci): move to mc-modpack-kit

@Aninuscsalas You have to set the Modrinth ID and TOKEN in the settings
Also allow "Allow PR's to be managed with actions"

@Aninuscsalas Can't maybe yet merge cause https://github.com/jh-devv/mc-modpack-kit/issues/49

@Aninuscsalas This should be pretty much complete (still have to add some stuff) but I want to ask something:
Does the version of the pack need to be different for the Forge and Quilt version?
Because for that, we would need https://github.com/jh-devv/mc-modpack-kit/issues/49

Does the version of the pack need to be different for the Forge and Quilt version? Because for that, we would need jh-devv/mc-modpack-kit#49

I'm still not sure what to do. I think its better to wait because in my test repos modrinth publishing/builing often fails, or skips everything. Im going to some testing with other packs before this one gets merged

Hmm, weird? Have you read the README?

Does the version of the pack need to be different for the Forge and Quilt version? Because for that, we would need jh-devv/mc-modpack-kit#49

I'm still not sure what to do. I think its better to wait because in my test repos modrinth publishing/builing often fails, or skips everything. Im going to some testing with other packs before this one gets merged

Could you share a test repo of yours?

This theorically should be now working (the release please things just means you can bump one part of the monorepo)
Shoudl work!

This theorically should be now working (the release please things just means you can bump one part of the monorepo) Shoudl work!

Should we try merging it? I have added the secrets to the repo. I guess the versioning can restart from 0.1.0... Im still not sure how should i style commit names, chore(quilt):,  and feat(forge): can work fine but im not sure that listing all the updated mods separately or just saying "Updated mods" is a better idea.

Should we try merging it? I have added the secrets to the repo. I guess the versioning can restart from 0.1.0... Im still not sure how should i style commit names, chore(quilt):, and feat(forge): can work fine but im not sure that listing all the updated mods separately or just saying "Updated mods" is a better idea.

@Aninuscsalas Yea, but you could just try to run the version workflow right away and set it to just some value (e.g. fabric, it does not support currentry different versions for different components) and for the version set 0.1.0 if you want that!
And for the mod commits, I would use it like:
For updates:
chore(fabric): Update mods
For bigger mod changes (e.g. adding or removing)
feat(fabric): Added mods or feat(fabric): Added Fabric API
Its pretty much how'd you like it!
Hope this helps
jh-devv

@Aninuscsalas Now my project uses commits like

feat(modpack/<mod>): <description> for adding new features, configs or content.
chore(modpack/<mod>): <description> for routine maintenance tasks or cleanups.
update(modpack/<mod>): update <mod> for updating mods to newer versions.
mod(modpack/<mod>): add <mod> for introducing new mods to the modpack.

I'm gonna probably try to merge this this in the next few days 🙃

@Aninuscsalas now just run the set version workflow ;3

@Aninuscsalas now just run the set version workflow ;3

can i do that before merging? (im new to github)

@Aninuscsalas now just run the set version workflow ;3

can i do that before merging? (im new to github)

You can do right after or I can do it :3

https://github.com/orgs/community/discussions/25488 @Aninuscsalas

authors: Aninuscsalas jh-devv


text:
Add generic document type

Hey, so sorry it took me so long to get around to this PR.
I like the overall idea and I think we should move towards this model!
My three comments are:

This change should be fully transparent and not break anything -- I think you've made sure of that in the returned Result format, thanks!
In the same vein, I don't think we should be forcing user to use our Document type, I think it makes more sense for the user to be able to pass just text and it be auto-constructed from it.
I can add this myself, but I think Document should also come with a "metadata" attribute which is just a dict where the user can pass in whatever!

I might take a stab at this myself later this afternoon, but thanks again for your contribution, and so sorry for the how long it took me to review this1

Hey, I've made a number of changes. There was a lot of API breaking change, which is something that will never happen with rerankers (I'm intending to keep everything compatible with the release version for as long as humanly possible). The key result of my updates are basically:

Result objects are now transparent to their Document object
Users can freely pass in pre-constructed Documents, string+doc_ids+meta_data, or any combination thereof, and the results will be the same.

I think this is ready to merge now, thank you for getting this started!

repo: AnswerDotAI/rerankers


text:
Add TicTacToe Game

Thanks for your Contribution


text:
Merge all open branches

Closed by #230, #231

authors: OnnoEbbens dbrakenhoff

repo: ArtesiaWater/nlmod


text:
BUG FIX: Return value of Evaluate method

Consider using again the evaluation method in the examples

repo: AtrejuArtax/aironsuit


text:
Spike: can tests enforce that structs include all members in to_ct/nt, read, write, operators?

Not without some ugly macro magic


text:
[pyamqp] branch with changes

/azp run python - eventhub - perf

/azp run python - eventhub - perf

repo: Azure/azure-sdk-for-python


text:
[DO NOT MERGE] testing check enforcer status

/check-enforcer evaluate

repo: Azure/azure-sdk-tools


text:
resolve where in expression throw internal error

approve

repo: BKBASE-Plugin/trino


text:
Avoid "dirtyfication" of the defines when not required

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14918/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14918/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14918/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14918/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14918/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14918/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14918/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14918/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14918/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14918/merge/testResults/webgl2playwright/index.html

authors: bjsplat deltakosh


text:
Added Czech translation

Hi @BenPru
I've converted the special characters in the file to UTF16.
However, on my Home Assistant it works even without that.

Hi @BenPru,
Is there anything I could improve to make the pull request accepted?

Hi @BenPru ,
I can confirm the translation file is compatible with the 2024.9.23-Beta release 👍.
I use it on my HASS instance.

repo: BenPru/luxtronik


text:
[feat/IaC-5] Add security groups

All good via aws output


text:
(201) Definir qual sistema gerenciador de banco de dados utilizar para armazenamento dos comentários

MongoDB escolhido

repo: BugaM/Sentzer


text:
34 ajout page admin

wrong branch boloss


text:
Master

更新的系统架构，暂时删除。

更新的系统架构，暂时删除。

更新的系统架构，暂时删除。

更新的系统架构，暂时删除。

repo: CaiNiaoLab/MicroRTOS


text:
Fix typo

thanks!

authors: CalebEverett easeev

repo: CalebEverett/arloader


text:
各部品の説明・整理

@MayaAbe ファイル1つ1つに1行程度の説明を加えるマークダウンファイルを作成。


text:
Missing language features

#59 will be fixed by e410677413680344b4b111008aab54605cfaf349

repo: CertainLach/jrsonnet


text:
Fix flaky test for ChainGetPath RPC method

Don't think this has flaked in a while

repo: ChainSafe/forest


text:
game

ez

repo: Champita/skills-code-with-codespaces


text:
Page design/styling

as a user i'd like to have a page that works not only on web but that is also responsive


text:
throw Error('No Connection URl provided.')

Udah diisi .env nya belum buat link database mongodb nya? Isi di example.env trus ganti nama file jdi .env

Udah ku tambahin juga dah ini dotenv nya biar ke baca di beberapa hosting, clone ulang

Udah ku tambahin juga dah ini dotenv nya biar ke baca di beberapa hosting, clone ulang

Udah diisi .env nya belum buat link database mongodb nya? Isi di example.env trus ganti nama file jdi .env

Udah

Udah ku tambahin juga dah ini dotenv nya biar ke baca di beberapa hosting, clone ulang

Oke

Wkwkwk dev

authors: JastinXyz ThisMe124 ZeroChanBot


text:
use signature and public key from primitives and crypto

doesn't work on wasm :(

repo: ComposableFi/near-rs

license: Unlicense


text:
GEOJSON overlay on top of tiff file.

Reviewed.

repo: CyberComplex/Space-tica


text:
Support for Slime

Closing this as we are using Polar instead, See #47

repo: CytonicMC/Cytosis


text:
If chant switches segments, should "

Whoops! Don't know how this happened... this issue is actually #1478

repo: DDMAL/CantusDB


text:
Add Build Support for windows

All left is to pull this on linux and see if there are any problems.

Works On Linux As Well

repo: DEVLOPRR/CSprite


text:
Search Page

Converted into a search bar visible at the top of every page

Completed in v0.2.0

repo: DNYLA/Melodiy


text:
Fix commitlint usage in git hook

Complete, Thanks!

authors: NoopDog hunterckx

repo: DataBiosphere/data-browser


text:
MoonDAO typo

Thanks for your contribution @ryand2d :)

repo: DeSciWorldDAO/awesome-desci


text:
added my profile README

Hey, @Prathamkrishna please add some more content in the readme and maybe add some dynamic widgets which will make it look good.

Yes please add some more content in the readme than either me or one of the maintainers will merge it!

authors: DevrajDC Prathamkrishna Shridhar-dev

repo: Design-and-Code/Dope-Github-Readmes


text:
SQL sources added

Teşekkürler

authors: enesmanan selincildam


text:
Added Table of contents to readme

@ROBERT-MCDOWELL
I'll be merging this as you accepted it before just had to update it again 👍


text:
create new world on enter

done

repo: Entkenntnis/robot-karol-web


text:
Okay, some stuff really messed up

look, if you really need to, you can make your PRS a draft if you ever need to

Alright.

i already fixed it, no need to make this pr

i already fixed it, no need to make this pr

I'm glad.

hi

authors: DaviIsBad Erizur Gabriel2019r

repo: Erizur/FNF-DaveEngine


text:
Bneukom/ue51 update

LGTM, quickly tested example scene. Did not go through the updated projects yet

repo: Esri/vitruvio


text:
Add Vitarum resume tool

add new tool which gets the resumes from vitarum.

repo: Euricom/euricom-gpt


text:
회원가입 서비스 개발

브랜치 이동

repo: FISA-on-Top/wooriSec


text:
tag scanning

https://pyimagesearch.com/2020/12/21/detecting-aruco-markers-with-opencv-and-python/

tag scanning works with QReader works but has two main problems:

Extremely slow start up times on script startup (multiple seconds)
It only supports QR Codes and not Aruco Markers (implications: (a) more difficult to scan (smaller details and doesn't do well with distorsion); (b) can't use the aruco marker maker inside CoppeliaSim (have to use a separate website to create 3d qrcodes)

Closing for now as it's working and if it ain't broke don't fix it but it's a possible area of improvement in the longer run to implement tag scanning with barebones opencv like on the tutorial above.


text:
investigate "sub" repos for publications

Added manuscripts as sub-modules to the job market survey 2019-2020 repo.


text:
add get query string, return orderedIdx

의견 전달이 잘 안된거 같아서요..!
제가 생각했던 내용으로 수정해서 풀리 올렸습니다!
검토 후 의견 주시고, 이상 없으면 그 때 마지 하겠습니다

충돌 해결버전은 Merge branch 'main' into woong@220730 커밋을 확인하면 됩니다


text:
Dev

cool

repo: Fauzanmhr/zannime


text:
Chat GraphQL & WS Backend

TODO: clean up messages in delete Account & delete Group

repo: Filan-glitch/StudiConnect-API


text:
Fix network type with gfx

checked with mstsc 10.0.19041 on windows 10 22h2 19045.4291  against freerdp-shadow-cli with WITH_DEBUG_CAPABILITIES :
all Experience/Performance options send the same EarlyCapability flags.

repo: FreeRDP/FreeRDP


text:
feat(anda-config): add extra_repos in rpm {}

manual testing on my machine, seems to work

repo: FyraLabs/anda


text:
Lookout Update package-lock.json to lockfileversion v2

LGTM.  I'll approve once I see if the circle ci integration tests pass.

repo: G-Research/armada


text:
Refactor syncQueues() to utilize data from the state dump.

Closing in favor of #288

repo: G-Research/unicorn-history-server


text:
Support for rabbitmq dead letter exchanges

@FlorianHockmann thank you for your feedback. I addressed your suggestions with the latest update.

repo: GDATASoftwareAG/motornet


text:
[Test] Improved code coverage

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.70%. Comparing base (184d271) to head (2116187).

Files
Patch %
Lines

src/range/range_iterator.rs
0.00%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #56      +/-   ##
==========================================
+ Coverage   64.80%   74.70%   +9.90%
==========================================
  Files          22       22
  Lines        2250     2155      -95
==========================================
+ Hits         1458     1610     +152
+ Misses        792      545     -247

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

authors: Gifted-s codecov-commenter

repo: Gifted-s/velarixdb


text:
Support unknown in match parameter

could you add a new test for an invalid org id? for example organizations/whatever
otherwise LGTM

Done

repo: GoogleCloudPlatform/config-validator


text:
Changed CD directory

Thanks @kristijansoldo

authors: artf kristijansoldo

repo: GrapesJS/preset-webpage


text:
docs: add SemanticMask and InstanceMask example in quick_start/examples

Pull Request Test Coverage Report for Build 1207873426

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.756%

Totals

Change from base Build 1197285733:
0.0%

Covered Lines:
6105

Relevant Lines:
7037

💛  - Coveralls

authors: coveralls marshallmallows

repo: Graviti-AI/tensorbay-python-sdk


text:
chore: merge influxdb1-client v0.1.4

 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.

authors: CLAassistant coanor

repo: GuanceCloud/cliutils


text:
Improve simplify commands logic

Better Error


text:
Add multi line comment syntax

Closes #595

I slightly would prefer #{ ... #} over #{ ... }#, what do you think?

Every language does this differently, there isn't any common way to do it other than /* */.
If i were to choose, I'd go with #= =# like in julia, even if it doesn't look like it's opening a block, or with #[ ]# like in nim, even if we don't really use [ ] with this kind of meaning elsewhere.
Relevant: https://en.wikipedia.org/wiki/Comparison_of_programming_languages_(syntax)#Comment_comparison
Do you have any preference or reason for any of the options? If not, we'll keep #{ }#

I slightly would prefer #{ ... #} over #{ ... }#, what do you think?

I like it

Does this also fix https://github.com/HigherOrderCO/Bend/issues/623 ?

Yes, it does fix the issue

authors: developedby imaqtkatt

repo: HigherOrderCO/Bend


text:
Add feature to use server cache instead of local storage

Hey @Ercogx, thanks for your work on this!
This was deployed in the new v2.0.0 version.
I did some changes in the PR, as I was not satisfied with the multi-persisters inside the HasTogglelabe trait : now it feels way easier to add persisters.
Feel free to upgrade (guide here) and tell me if it works correctly for you.

Amazingly, I also thought about redoing it but wouldn't dare to release a new version. Great work!
I will try to check everything today 🙌

@tgeorgel work like a charm, thank you for your work!

Thanks for yours @Ercogx !

authors: Ercogx tgeorgel


text:
CFEE-1631:As a customer I want establish container-to-container functionality in the plugin (Git-338)

LGTM

repo: IBM/cf-migration-runtime


text:
ziya-llama效果很棒，我想问一下增量训练时，是全量参数训练，还是LoRA微调？

全量参数训练。

全量参数训练。
您好，目前有开源ziya SFT代码吗

authors: ganzhiruyi lulia0228 yuemengrui

repo: IDEA-CCNL/Fengshenbang-LM


text:
Provide system temperature

Best wait for https://github.com/IRL2/nanover-protocol/pull/245 which changes the ase simulations around

Need to make sure that we calculate the instantaneous temperature of the system (NOT the temperature of the thermostat) for the programs we support:

[ ] Calculate instantaneous temperature in OpenMM via kinetic energy for runners without inbuilt methods
[ ] Calculate instantaneous temperature in OpenMM via inbuilt methods for runners with this functionality (perhaps we don't want to support this?)
[ ] Calculate instantaneous temperature in ASE (i.e. cannot just take the temperature of the thermostat)

First draft for OpenMM based on existing StateDataReporter code -- untested

We should also add this field for MDAnalysis converter

We should also add this field for MDAnalysis converter

After testing, I think this data field can already be retrieved via the converter, so no need!

Added tests for both OpenMM and ASE implementations:

OpenMM implementation checks that the correct temperature is delivered when there are no iMD interactions, and that the temperature delivered is within 1% of the true temperature when there are iMD interactions
ASE implementation checks that the temperature delivered in the frame matches that calculated internally by ASE

authors: Ragzouken hjstroud


text:
Add repository and unitary tests

El trabajo parece bueno, pero el test debe ir sobre una DB-inmemory, no sobre la BBDD real. No veo fichero de configuración de test. El test intenta ejecutarse sobre BBDD real.

authors: GabrielMino jonatanvicente


text:
Update queue model closes #108

Codecov Report

Merging #158 (38351ac) into main (bb2a1ba) will decrease coverage by 1.86%.
The diff coverage is 61.90%.

@@             Coverage Diff              @@
##               main     #158      +/-   ##
============================================
- Coverage     83.38%   81.52%   -1.87%
+ Complexity      334      327       -7
============================================
  Files            43       41       -2
  Lines           939      931       -8
  Branches        141      137       -4
============================================
- Hits            783      759      -24
- Misses           63       81      +18
+ Partials         93       91       -2

Flag
Coverage Δ

unittests
81.52% <61.90%> (-1.87%)
:arrow_down:

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

Impacted Files
Coverage Δ

...nopolis/innoqueue/domain/queue/dto/EditQueueDTO.kt
100.00% <ø> (ø)

...nnopolis/innoqueue/domain/queue/dto/NewQueueDTO.kt
100.00% <ø> (ø)

...m/innopolis/innoqueue/domain/queue/dto/QueueDTO.kt
100.00% <ø> (ø)

...s/innoqueue/domain/queue/dto/QueueInviteCodeDTO.kt
100.00% <ø> (ø)

...opolis/innoqueue/domain/queue/dto/QueueShortDTO.kt
88.88% <ø> (ø)

...opolis/innoqueue/domain/queue/dto/QueuesListDTO.kt
100.00% <ø> (ø)

...lis/innoqueue/domain/queue/util/UsersQueueLogic.kt
60.00% <ø> (ø)

.../com/innopolis/innoqueue/domain/user/model/User.kt
100.00% <ø> (ø)

...polis/innoqueue/domain/user/service/UserService.kt
86.36% <ø> (ø)

...tlin/com/innopolis/innoqueue/model/Notification.kt
100.00% <ø> (ø)

... and 17 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: SMore-Napi codecov-commenter

repo: InnoQueue/Backend


text:
200/update homepage ui

Summary

Includes WhyBlock from la previa layout into home page.

Media
Screenshot

Close
Closes #200


text:
Add favorites date option in nav add JS to check local storage

Completed. PR ready for review


text:
Add-CSS-File

css file added


text:
Bump up Gradle plugin dependencies

Thanks! However, GE integration shouldn't even be committed. 🙃

authors: hsz jprinet

repo: JetBrains/gradle-changelog-plugin


text:
Add WSB Merito Bydgoszcz to school list

@mibac138 Thank you for your patience while waiting for a review and processing your request. Pull request merged.

repo: JetBrains/swot


text:
Create incois.txt

@lakshmitharun First stage of verification passed, official domain for Indian National Centre for Ocean Information Services is incois.gov.in as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@lakshmitharun I am sorry, this domain seems to represent a purely research institution, not a specific single university or a college. I have to close this request without merging.
If you are a student, please enroll to GitHub Student Developer Program at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).
If you are a researcher, please send an email to sales@jetbrains.com to get an academic discount for your paid license.
Thank you for your understanding!

authors: lakshmitharun philipto


text:
add simec institute domain

Please kindly provide the full name of your school on the first line of the file in your request

Removed first line white space, Please Proceed with my PR.

Please kindly provide the full name of your school on the first line of the file in your request

Removed first line white space, Please Proceed with my PR.

@itsmohiful Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.

authors: itsmohiful philipto


text:
How to get your project dataset? about gta5_train.txt.

Hi there,
GTA5_train.txt is indeed the GTA5 image file list.
gta5_list.txt
Cheers,
Zixin

authors: Jo-wang csliuchang

repo: Jo-wang/Cal-SFDA


text:
Prevent ifelse from returning zero-bit DistInt

Thanks. Can you perhaps add a unit test that checks for this bug?

Thanks. Can you perhaps add a unit test that checks for this bug?

Added in 84b9d68!

Thanks. I am wondering whether it makes more sense to make the bit width a type parameter and require the same bit width in the then and else branches? @PoorvaGarg ?

merging this for now but still confused why bit width would ever reduce. seems to me like the returned bit width should be the max of the two arguments of the iften

merging this for now but still confused why bit width would ever reduce. seems to me like the returned bit width should be the max of the two arguments of the ifthen

My understanding is that if the most significant k bits are unsatisfiable, then they are "chopped off" the returned DistInt. Here is the relevant code with some additional comments:
function ifelse(cond::DistBool, then::DistInt, elze::DistInt)
    if isvalid(cond)
        then
    elseif !issat(cond)
        elze
    else
        last_sat_bit = 1 # The fix sets this to 1 instead of 0, so we keep the LSB regardless of its satisfiability
        mbthen, mbelze = max_bits(then), max_bits(elze)
        mb = max(mbthen, mbelze)
        # As many DistBools as the wider argument has
        z = Vector{DistBool}(undef, mb)
        for i=1:mb
            z[i] = if i > mbthen  # If we are beyond the `then` DistInt's width
                !cond & elze.bits[i]
            elseif i > mbelze  # If we are beyond the `else` DistInt's width
                 cond & then.bits[i]
            else  # Common case
                ifelse(cond, then.bits[i], elze.bits[i])
            end
            # Is this bit is satisfiable, then ensure it is included it the returned DistInt
            if issat(z[i])
                last_sat_bit = i
            end
        end
        DistInt(cond.mgr, z[1:last_sat_bit])  # Chop off upper unsatisfiable bits
    end
end

This is why the unit test I added fails before the fix: as no bits of DistInt([DistBool(dicecontext(), false)]) are satisfiable, then the width shrinks to 0.

Thanks. I am wondering whether it makes more sense to make the bit width a type parameter and require the same bit width in the then and else branches? @PoorvaGarg ?

I think if we shrink implicitly (as above), then we should also not require the user to explicitly add bits (e.g. to avoid overflow for DistInt addition).
Reasons to automatically grow/shrink ("arbitrary precision" DistInts):

Ergonomics: user does not have to manage widths
No overflow (it could be worth discussing behavior for div by 0 & NaN values at the same time)

Reasons to bake width into type

If user does not care about execution paths where overflow occurs, this might be able to improve performance beyond what is possible with arbitrary precision DistInts.

To investigate

Effect on performance of automatic shrinking vs. having extra constants in the upper bits. Based on a few tiny experiments, extra constants don't seem to hurt.

I am not sure what discussion has already been had on this topic - are there more reasons for either side that I am missing? I currently feel like the argument for automatically-sized DistInts is stronger - are there motivating examples to include the width in the type?

The issue with the "prune width if unsat" approach is that it only works with bottom-up BDD compilation in program order. If we want to do any other form of inference or analysis, it will be impossible to determine sat halfway through the program.

I left this in the issue tracker to discuss the redesign or the integer types: https://github.com/Juice-jl/Dice.jl/issues/10

authors: guyvdbroeck rtjoa


text:
Release 1.0

Closes #26

repo: Julia-Chekulaeva/YouTubeGifAndSoundBot


text:
chore(gha): add a name to CI step

Codecov Report

Merging #17 (99598f2) into main (8af2ad5) will decrease coverage by 36.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #17       +/-   ##
===========================================
- Coverage   76.63%   40.54%   -36.09%
===========================================
  Files          16       16
  Lines        2191     2163       -28
===========================================
- Hits         1679      877      -802
- Misses        512     1286      +774

see 14 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter mortenpi


text:
download: add verbose option (print debug info to stderr)

Codecov Report

Merging #41 into master will decrease coverage by 2.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
- Coverage   93.95%   91.84%   -2.11%
==========================================
  Files           5        5
  Lines         281      282       +1
==========================================
- Hits          264      259       -5
- Misses         17       23       +6

Impacted Files
Coverage Δ

src/Curl/Curl.jl
100.00% <ø> (ø)

src/Curl/Easy.jl
94.93% <100.00%> (+0.06%)
:arrow_up:

src/Downloads.jl
94.91% <100.00%> (+0.08%)
:arrow_up:

src/Curl/utils.jl
78.12% <0.00%> (-18.75%)
:arrow_down:

src/Curl/Multi.jl
91.66% <0.00%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: StefanKarpinski codecov-io


text:
Suggest an impressive APP ICON

Have a look at this one.

this one is good but search for other options as well
On Mon, Jan 31, 2022 at 11:12 AM Girija Nandan Kar @.***>
wrote:

https://user-images.githubusercontent.com/42700980/151744347-a46e7a5a-a51f-48f9-b762-018a46abb9d2.png
Have a look at this one.
—
Reply to this email directly, view it on GitHub
https://github.com/Kajal13081/Gallery-Application/issues/19#issuecomment-1025399958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUD4U5QJISYBXL7B7YYRWDLUYYOOHANCNFSM5NFIVVJA
.
You are receiving this because you authored the thread.Message ID:
@.***>

hey guys,
i can understand your enthusiasm for open source contribution and thanks
for selecting our project but we will appreciate a lot if you guys can also
chat with us on the JWOC discord channel rather than on comments because
the comment section will be filled with the discussion which is not good
for others who visits the issue for JWOC ,so comment on the issue that you
wanna work on it and want us to assign it to you and if there is any doubt
related to issue or project we can easily clear it on discord. Bonding
with the mentors and other mentees are also important thats why the discord
channel is created
I hope you guys understand it
Here is the discord link JWOC Discord
https://discord.com/invite/ve6ad4jfEP
this is my discord id: Vilgad#0291
Happy Coding ;)
On Mon, Jan 31, 2022 at 11:28 AM Rohit @.***> wrote:

this one is good but search for other options as well
On Mon, Jan 31, 2022 at 11:12 AM Girija Nandan Kar <
@.***> wrote:

https://user-images.githubusercontent.com/42700980/151744347-a46e7a5a-a51f-48f9-b762-018a46abb9d2.png
Have a look at this one.
—
Reply to this email directly, view it on GitHub
https://github.com/Kajal13081/Gallery-Application/issues/19#issuecomment-1025399958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUD4U5QJISYBXL7B7YYRWDLUYYOOHANCNFSM5NFIVVJA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi there, I'm interested to suggest app icon. Well, I'm a graphics designer too, so if needed I can design myself one too.
Can you please explain more about this issue?
I'm interested to work on this issue and get assigned.

can you please comment on this issue actually i am unable to see your
comment on that issue in  github
On Tue, Feb 1, 2022 at 1:22 AM Binay Shaw @.***> wrote:

Hi there, I'm interested to suggest app icon. Well, I'm a graphics
designer too, so if needed I can design myself one too.
Can you please explain more about this issue?
I'm interested to work on this issue and get assigned.
—
Reply to this email directly, view it on GitHub
https://github.com/Kajal13081/Gallery-Application/issues/19#issuecomment-1026148944,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUD4U5WNDKKTBWXGN6XPZRTUY3R75ANCNFSM5NFIVVJA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey, I'm Interested to design and suggest App Icon for you!
@vilgad

Hey, I'm Interested to design and suggest App Icon for you! @vilgad
All the best

@vilgad  Hey, Can you tell me like what type of app logo you like or want? So that I can figure out your requirements and work on it.

Does this looks okay? or shall I change the design?

@binayshaw7777 please have this discussion on discord

authors: binayshaw7777 girijakar vilgad


text:
Cannot run on the wasmJs platform

Hello, I would like to ask when the wasmJs platform will be supported. I encountered an error when running on the wasmJs platform. The error message indicates that it cannot find the library for the js platform. Here is the error message:
Could not determine the dependencies of task ':kotlinNpmInstall'.

Could not resolve all dependencies for configuration ':composeApp:wasmJsNpmAggregated'.
Could not resolve io.github.kevinnzou:compose-webview-multiplatform:1.9.20.
Required by:
project :composeApp
No matching variant of io.github.kevinnzou:compose-webview-multiplatform:1.9.20 was found. The consumer was configured to find a library for use during 'kotlin-runtime', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.js.public.package.json' with value 'public-package-json', attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm', attribute 'org.jetbrains.kotlin.wasm.target' with value 'js' but:
- Variant 'desktopApiElements-published' declares a library:
- Incompatible because this component declares a component for use during compile-time, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'desktopRuntimeElements-published' declares a library for use during runtime:
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'desktopSourcesElements-published' declares a component for use during runtime:
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosArm64ApiElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosArm64MetadataElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosArm64SourcesElements-published' declares a component for use during 'kotlin-runtime':
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosSimulatorArm64ApiElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosSimulatorArm64MetadataElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosSimulatorArm64SourcesElements-published' declares a component for use during 'kotlin-runtime':
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosX64ApiElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosX64MetadataElements-published' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'iosX64SourcesElements-published' declares a component for use during 'kotlin-runtime':
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'metadataApiElements' declares a library:
- Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'metadataSourcesElements' declares a component for use during 'kotlin-runtime':
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'releaseApiElements-published' declares a library:
- Incompatible because this component declares a component for use during compile-time, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'releaseRuntimeElements-published' declares a library for use during runtime:
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
- Variant 'releaseSourcesElements-published' declares a component for use during runtime:
- Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
- Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')

Try:

Review the variant matching algorithm at https://docs.gradle.org/8.7/userguide/variant_attributes.html#sec:abm_algorithm.
No matching variant errors are explained in more detail at https://docs.gradle.org/8.7/userguide/variant_model.html#sub:variant-no-match.
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 7s

Translated by ChatGPT, it might not be perfect. Please forgive any mistakes.

@MoYeRanqianzhi Thanks for your feedback. Currently, we only have a PR that has empty support for WasmJs. It just makes this lib build successfully on the WasmJs platform. However, the web content will not display properly on it. Since I am not an expert on the WasmJs side, I am afraid that we can only wait for someone to create the real implementation for it. I am sorry for that. You are welcome to build upon the PR above to support WasmJs. Thanks!

@KevinnZou Thank you, this way at least it won't cause the wasmJs platform to fail to run. For the implementation method on the wasmJs platform, I think maybe using the IFrame tag might work.

@KevinnZou I think this method can work. Just display the WebView at the top layer and adjust its position and size to make it appear at the specified location.
style.css
html, body {
    width: 100%;
    height: 100%;
    margin: 0;
    padding: 0;
    overflow: hidden;

    .over {
        position: fixed;
        top: 0;
        left: 0;
        width: 100%;
        height: 100%;
        display: flex;
        z-index: 9999;
    }
    .over .component {
        pointer-events: auto;
    }
}

index.html
<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>TinySoftware</title>
    <link type="text/css" rel="stylesheet" href="styles.css">

main.kt
@OptIn(ExperimentalComposeUiApi::class)
fun main() {
    document.getElementById("webview")!!.appendChild(
        document.createElement("web").apply {
            innerHTML = ""
        }
    )
    ComposeViewport(document.body!!) {
        App()
    }
}

authors: KevinnZou MoYeRanqianzhi

repo: KevinnZou/compose-webview-multiplatform


text:
Setup CI & CD, primary branches & Contributor guides

where's the PR for this? @alofeoluwafemi

authors: alofeoluwafemi pauloladimeji

repo: KlayOracle/klayoracle-monorepo


text:
Updates to produce new, better phenotype comparisons

This currently will generate the IC maps but won't yet pass them to the call to runoak similarity

On the Jenkins run, the line for building the custom IC map fails due to an SQL error, as below:
09:33:34  + runoak -g hpoa.tsv -G hpoa -i sqlite:obo:phenio information-content -p i --use-associations .all
12:32:40  sqlite3.OperationalError: too many SQL variables
12:32:40
12:32:40  The above exception was the direct cause of the following exception:
12:32:40
12:32:40  sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) too many SQL variables
12:32:40  [SQL: SELECT term_association.id AS term_association_id, term_association.subject AS term_association_subject, term_association.predicate AS term_association_predicate, term_association.object AS term_association_object, term_association.evidence_type AS term_association_evidence_type, term_association.publication AS term_association_publication, term_association.source AS term_association_source
12:32:40  FROM term_association
12:32:40  WHERE term_association.object IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,

This may require sqlite to be updated on the build environment.
See also https://github.com/deepset-ai/haystack/issues/588

With changes in https://github.com/INCATools/ontology-access-kit/pull/764 I expect this to work better - will just need to pin OAK version to github

Will test after merging https://github.com/INCATools/ontology-access-kit/pull/759

Getting Jenkins errors on test - unclear why:
Error when executing always post condition:
Also:   org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 7c6506e2-fc79-47e8-b60a-bfd6d52143dd
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node
	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:89)
	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:70)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

The Jenkins error was due to string interpolation in environment variable names not working as expected.

Getting a ModuleNotFoundError: No module named 'semsimian' because semsimian is optional dependency - fixing

Good news: IC map is produced quickly and without errors!
Bad news: Something (OAK or Semsimian) is raising an error:
10:13:21  + runoak -i semsimian:sqlite:obo:phenio similarity --no-autolabel --information-content-file hpoa_ic.tsv -p i --set1-file HPO_terms.txt --set2-file HPO_terms.txt -O csv -o HP_vs_HP_semsimian_-20240516.tsv --min-ancestor-information-content 4.0
10:13:39  Loading custom IC map from: "hpoa_ic.tsv"
10:13:39  Failed to import custom IC map: Error parsing IC value: invalid float literal

That error may be a false positive - when I run a single pair locally and pass the IC map, I don't get that error:
$ runoak -vvv -i semsimian:sqlite:obo:phenio similarity --no-autolabel --information-content-file hpoa_ic.tsv -p i  -O csv -o test.tsv --min-ancestor-information-content 4.0 HP:
0007166 @ HP:0007153
INFO:root:Setting other_languages=()
INFO:root:Settings = Settings(impl=None, autosave=False, associations_type=None, preferred_language=None, other_languages=())
INFO:root:Wrapping an existing OAK implementation to fetch sqlite:obo:phenio
INFO:root:Locator: obo:phenio
INFO:root:Ensuring gunzipped for https://s3.amazonaws.com/bbop-sqlite/phenio.db.gz
INFO:root:Locator, post-processed: sqlite:////home/harry/.data/oaklib/phenio.db
DEBUG:root:Paths to search: [PurePosixPath('model/schema'), PurePosixPath('schema'), PurePosixPath('linkml'), PurePosixPath('src/linkml'), PurePosixPath('src/model'), PurePosixPath('src/model/schema'), PurePosixPath('src/schema'), PurePosixPath('.')]
DEBUG:root:candidate model/schema not found
DEBUG:root:candidate schema not found
DEBUG:root:candidate linkml not found
DEBUG:root:candidate src/linkml not found
DEBUG:root:candidate src/model not found
DEBUG:root:candidate src/model/schema not found
DEBUG:root:candidate src/schema not found
INFO:root:out=test.tsv <class 'str'>
INFO:root:file=<_io.TextIOWrapper name='test.tsv' mode='w' encoding='UTF-8'> <class 'str'>
INFO:root:Splitting terms ['HP:0007166', '@', 'HP:0007153'] on 1
INFO:root:Calculating all-by-all pairwise similarity for 1 objects
[00:00:09] Building closure and IC map: ████████████████████████████████████████ 100%                                                                                INFO:root:Post-processing results from semsimian

This is the relevant function in semsimian:
https://github.com/monarch-initiative/semsimian/blob/e2cba82624dc0633092e0b299d80f3771d01659c/src/utils.rs#L579-L607
Maybe it's just trying to parse EOF? Seems unlikely as there isn't a tab in the last line.
Oh. Wait. No. It's the header.
Semsimian doesn't expect it.
Not sure why that error isn't being raised locally but I'll put a fix for it in here.

Looks like the map is now loading correctly, at least for HP.
12:14:28  + runoak -i semsimian:sqlite:obo:phenio similarity --no-autolabel --information-content-file hpoa_ic.tsv -p i --set1-file HPO_terms.txt --set2-file HPO_terms.txt -O csv -o HP_vs_HP_semsimian_-20240516.tsv --min-ancestor-information-content 4.0
12:14:46  Loading custom IC map from: "hpoa_ic.tsv"
12:14:46  Custom IC map imported successfully.
12:14:55  Warning: The following keys are present in closure_map but not in ic_map:

This is followed by a list of more than 20K CURIEs, including 5952 HP IDs.
Might be excessive to write that to stdout.

I wonder why so many CURIEs are in closure_map but not ic_map?

If the HP ID doesn't show up in the association table at all, it doesn't get an IC score.
So many of these IDs (just based on cursory checking, not exhaustive at all) are rare phenotypes, like HP:0100378 (Absent distal phalanx of the 3rd toe) or high-level terms that just aren't specific enough to get used in associations, like HP:0008008 (Reduced visual acuity) - the latter's child term of HP:0000618 (Blindness) is used 168 times in the HPOA, for example.
Is this the expected behavior, though?
Should all terms receive some sort of baseline score by virtue of existing, then have that score get adjusted proportionally by observed frequency?

Is this the expected behavior, though?

This is expected, but is going to cause problems. I think we will need IC values for everything in phenio

Should all terms receive some sort of baseline score by virtue of existing, then have that score get adjusted proportionally by observed frequency?

We could do that, but I can't think of how to convince OAK to calculate IC like that.
How about this: if a term is not observed, we set the IC to -log(1/number of total counts).
To do this, we could post-process the IC tsv file to set any term in phenio that isn't in there to min(IC score in the IC TSV file). Or, we could do this in semsimian after we read in the IC tsv file.

TODO:

Add option to semsimian + OAK to specify what to do for CURIEs in closure but not in IC map. One option should be to fail. Don't do that by default. Also provide option to infer (assign or use proportional IC.
Save other artifacts to the uploaded output, like the IC maps.

Also something odd happened to the HPvMP and HPvZP uploads. Will check on that

Aha - the issue is that the IC tables for MP and ZP aren't generating what I'd expect.
Running this:
runoak -g mpa.tsv -G hpoa_g2p -i sqlite:obo:phenio information-content -p i --use-associations .all > mpa_ic.tsv

Only outputs 137 ICs, none of them from MP! It looks like the subject_taxon column is being used as the calculation input instead of what's in the object column.
So the hpoa_g2p parser isn't working as expected.
Other parsers are listed here: https://github.com/INCATools/ontology-access-kit/blob/main/src/oaklib/parsers/init.py

authors: caufieldjh justaddcoffee


text:
fix(grpc) proto files include path

included in this PR https://github.com/Kong/kong/pull/8914

authors: Suika-Kong mayocream

repo: Kong/kong


text:
Setup Kotlin compiler server with dataframe dependency

Well, server is up and running, but we're waiting for Kotlin Playground react component to introduce a parameter to change server URL. Until the there's not much i can do about this ticket

repo: Kotlin/dataframe


text:
assemble javadocs on build

not really part of anything in git, just the IDE

repo: KrabCode/LazyGui


text:
fix: send mail on approvl/reject and more

:tada: This PR is included in version 2.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: LABIOQUIM/visualdynamics


text:
Truncate memote test output

Codecov Report
Patch coverage: 65.98% and project coverage change: -0.55 :warning:

Comparison is base (0ec9418) 78.23% compared to head (2bb61f0) 77.68%.

:exclamation: Current head 2bb61f0 differs from pull request most recent head bcd27d4. Consider uploading reports for the commit bcd27d4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   78.23%   77.68%   -0.55%
==========================================
  Files          20       20
  Lines         611      623      +12
==========================================
+ Hits          478      484       +6
- Misses        133      139       +6

Impacted Files
Coverage Δ

src/memote.jl
100.00% <ø> (ø)

src/memote/frontend.jl
69.94% <65.98%> (-1.49%)
:arrow_down:

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

authors: codecov-commenter stelmo


text:
adding sightseeing dataset to pois

add all data spots


text:
add support for wav format

fixed with #7


text:
Add and update projects

closed #462


text:
feat: Add Pufferfish tag and Configuration file

Thank you for your contribution

repo: MCSManager/MCSManager


text:
Add diffusion v1

function conv(x, w::AbstractArray{T, N}; stride = 1, pad = 0, dilation = 1, flipped = false, groups = 1) where {T, N}
Din ce vad aici x nu are tip, deci poate fi orice chestie acolo. Cred ca trebuie doar definite operatiile de inmultire, adunare, impartire pe Cell.

authors: Bogdan-Morosanu MariusDrulea


text:
Add Your Favorite, Awesome clone and contribute to Hacktoberfest-2021

Thanks for much for the fast response checkout this PR #5 here. let me know if it looks right. thanks! @MasterBrian99