[WIP] feat: records create/update bulk endpoints with fully support

Description
This adds endpoints:
POST /api/v1/datasets/:dataset_id/records/bulk
PUT /api/v1/datasets/:dataset_id/records/bulk
to support related entities as responses, suggestions and vectors, based on work developed in https://github.com/argilla-io/argilla-server/pull/88.
There is still some work to do:

[ ] Test integration with the argilla-python module. This will help to validate the proposal
[ ] Adding tests for upsersing relationships

Closes #<issue_number>
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)

[ ] New feature (non-breaking change which adds functionality)
[ ] Refactor (change restructuring the codebase without changing functionality)
[ ] Improvement (change adding some improvement to an existing functionality)

How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

[ ] Test A
[ ] Test B

Checklist

[ ] I added relevant documentation
[ ] I followed the style guidelines of this project
[ ] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

Duplicated https://github.com/argilla-io/argilla-server/pull/100


Any plans to support OpenLayers 4?

Was looking to use react-openlayers but my coworkers (who have much more OpenLayers experience than I) were encouraging me to use OL4...
(they said OL4 had some features to better limit the resulting webpack javascript bundle size?)

It's already OL4
https://github.com/allenhwkim/react-openlayers/blob/master/package.json#L47

Oh awesome!!
(just fyi/fwiw I'm new to OpenLayers so maybe I read it differently than others would have but it was the description "A minimal React wrapper of OpenLayer 3+ written in TypeScript" that I misread as "OpenLayers 3" I didn't even notice the "+" part until your message)


Error 'Asked for index.html but it was not precompiled' after editing exe manifest to require admin privileges in a packaged app

[ x] I have read the contribution documentation for this project.
[ x] I agree to follow the code of conduct that this project follows, as appropriate.
[ x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
Running into compilation issues in packaged app on Windows 10, when requested execution level of the exe is changed to requireAdministrator
Steps to reproduce:

Set up and build a new project electron-forge init forge && cd forge && npm run package
Everything runs fine
Change requestedExecutionLevel from asInvoker to requireAdministrator in /out/forge-win32-x64/forge.exe manifest
I used mt.exe to extract and edit the manifest since node-rcedit doesn't seem to be working properly right now. Editing manifest using rcedit results in this issue and adding "win32metadata": { "requested-execution-level": "requireAdministrator" } to forge config results in 'side by side configuration error' when running the exe
When you run the exe, you get the following error in the window: Failed to compile C:/.../app/src/index.html. Asked for C:/.../app/src/index.html but it was not precompiled
When you run the exe from an admin cmd, it actually works fine again

I imagine this is probably electron-compile or electron-prebuild-compile issue, but let me know what you think and I'll open the issue with the correct project if needed.

I don't know how requireAdministrator is supposed to work but regardless of the strange error, if it can't access the app unless you run it from an admin command, that seems to fit what the config option sounds like it is?

No, that's not the case. <requestedExecutionLevel level="requireAdministrator"> in exe manifest means that the app will ask for their privileges to be elevated to administrator level when it's launched and Windows will give you a little popup asking you if you're ok with that.
Basically you end up running the app under your user, but in an elevated privilege context.
When you run the app from administrator cmd, you launch it under administrator. I guess that's the difference.
I should have made it clearer, but the application launches normally, BrowserWindow opens up, code in index.js runs, however index.html doesn't load and you get the electron-compile error in the window.

In a non-admin cmd window, try running:
SET DEBUG="electron-compile:*"
electonAppName.exe

There should be some debug info from electron-compile (in the cmd window? Not sure, I don't develop on Windows).

Fri, 23 Feb 2018 16:24:13 GMT electron-compile:sanitize-paths Cache miss for cachedRealpath: 'c:\code\forge-test\out\forge-test-win32-x64\resources\app' => 'c:\code\forge-test\out\forge-test-win32-x64\resources\app'
Fri, 23 Feb 2018 16:24:13 GMT electron-compile:sanitize-paths Cache miss for cachedRealpath: 'c:\code\forge-test\out\forge-test-win32-x64\resources\app\src\index.js' => 'c:\code\forge-test\out\forge-test-win32-x64\resources\app\src\index.js'
Fri, 23 Feb 2018 16:24:13 GMT electron-compile:compile-cache Fetching c:\code\forge-test\out\forge-test-win32-x64\resources\app\src\index.js from cache
Fri, 23 Feb 2018 16:24:13 GMT electron-compile:compile-cache Path for BabelCompiler: c:\code\forge-test\out\forge-test-win32-x64\resources\app\.cache\318fbe29173eac8b3c9c5a28df9dce3dd22e379a
Fri, 23 Feb 2018 16:24:13 GMT electron-compile:compile-cache Set up with parameters: {"name":"BabelCompiler","version":"6.26.0","options":{"presets":[["env",{"targets":{"electron":"1.8"}}],"react"],"plugins":["transform-async-to-generator"],"sourceMaps":"inline"}}
Fri, 23 Feb 2018 16:24:15 GMT electron-compile:protocol-hook Intercepting url file:///C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html
Fri, 23 Feb 2018 16:24:15 GMT electron-compile:sanitize-paths Cache miss for cachedRealpath: 'C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html' => 'C:\code\forge-test\out\forge-test-win32-x64\resources\app\src\index.html'
Fri, 23 Feb 2018 16:24:15 GMT electron-compile:file-change-cache Tried to read file cache entry for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html
Fri, 23 Feb 2018 16:24:15 GMT electron-compile:file-change-cache cacheKey: C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html, appRoot: c:/code/forge-test/out/forge-test-win32-x64/resources/app, originalAppRoot: C:/Users/TOMASG~1/AppData/Local/Temp/electron-packager/win32-x64/forge-test-win32-x64/resources/app
Fri, 23 Feb 2018 16:24:15 GMT electron-compile:protocol-hook Failed to compile C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html: Asked for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html but it was not precompiled!
Error: Asked for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html but it was not precompiled!
    at FileChangedCache.getCacheEntryForPath (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:218:15)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:127:41
    at Generator.next (<anonymous>)
    at step (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:191)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:437
    at Promise (<anonymous>)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:99
    at FileChangedCache.getHashForPath (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:177:7)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\compiler-host.js:298:51
    at Generator.next (<anonymous>)
Fri, 23 Feb 2018 16:24:16 GMT electron-compile:protocol-hook Intercepting url file:///C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html
Fri, 23 Feb 2018 16:24:16 GMT electron-compile:file-change-cache Tried to read file cache entry for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html
Fri, 23 Feb 2018 16:24:16 GMT electron-compile:file-change-cache cacheKey: C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html, appRoot: c:/code/forge-test/out/forge-test-win32-x64/resources/app, originalAppRoot: C:/Users/TOMASG~1/AppData/Local/Temp/electron-packager/win32-x64/forge-test-win32-x64/resources/app
Fri, 23 Feb 2018 16:24:16 GMT electron-compile:protocol-hook Failed to compile C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html: Asked for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html but it was not precompiled!
Error: Asked for C:/code/forge-test/out/forge-test-win32-x64/resources/app/src/index.html but it was not precompiled!
    at FileChangedCache.getCacheEntryForPath (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:218:15)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:127:41
    at Generator.next (<anonymous>)
    at step (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:191)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:437
    at Promise (<anonymous>)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:27:99
    at FileChangedCache.getHashForPath (c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\file-change-cache.js:177:7)
    at c:\code\forge-test\out\forge-test-win32-x64\resources\app\node_modules\electron-compile\lib\compiler-host.js:298:51
    at Generator.next (<anonymous>)na

The last thing I would check is the permissions/ownership on the files/folders in resources\app. If those look OK, it seems like it's a strange interaction between electron-compile and that Windows exe directive. I don't know why else it would work for admin but not for non-admin.

Thanks. The permissions look OK - my user is the owner and has full access. I guess this warrants opening an issue directly in electron-compile

As of<EMAIL_ADDRESS>we don't use electron-compile by default.  If you still experience this issue in a post-6.0.0 world you should raise an issue on electron-compile.

For anyone else running into this issue:

Make sure you put your HTML and any static files inside a sub-folder i.e. dist, or src, and recompile, that seems to resolve my issue.


typo

Thank you :+1:
@samsonasik Feel free to merge this kind of PR as well. It's pretty clear

Thank you :+1:
@samsonasik Feel free to merge this kind of PR as well. It's pretty clear


Trait method newEloquentBuilder has not been applied, because there are collisions with other trait methods

Issue
Trait method newEloquentBuilder has not been applied, because there are collisions with other trait methods on App\Models\Flight.
I found out that i'm also  using \Grimzy\LaravelMysqlSpatial Trait in this model.
and reading this issue it looks like it has to do with this package.
https://github.com/grimzy/laravel-mysql-spatial/issues/17
I'm not sure if it's possible to implement a method to fix this issue in this package or that i do have to create my own custom "Illuminate\Database\Eloquent\Builder".
Environment
Laravel Version: 5.5.40
Laravel Model Caching Package Version: 0.2.62
PHP Version: PHP 7.1.8
Operating System & Version: Mac OS X
Stack Trace

(1/1) FatalErrorExceptionTrait method newEloquentBuilder has not been applied, because there are collisions with other trait methods on App\Models\Flight
--

Hi @eelco2k, off the top of my head, I believe this is something you will have to resolve locally in your app. Please let me know if you do find a solution, so I can take a look and see if it would be possible to implement in the package.

as @grimzy commented out in this issue: https://github.com/grimzy/laravel-mysql-spatial/issues/17 he wrote a custom Illuminate\Database\Eloquent\Builder and extending own packages classes with a Trait.
Perhaps this would be a good method to do as well for laravel-model-caching.

i've tried to move the functions in CachedBuilder.php into a Trait but this didn't work sadly.
I've also tried this in conjuction with the dev-builder-as-trait branch of the grimzy/laravel-mysql-spatial but i'm still getting the same errors.
So no solution yet.

Yea, I don't think there is an easy solution for this at this time. I'm closing this for now. Please re-open if you have further information that may help out. Thanks for looking into it!

I had this problem with \Kalnoy\Nestedset\NodeTrait
I think this is working as a simple solution in my case, the node trait ran
public function newEloquentBuilder($query) {
    return new QueryBuilder($query);
}

Looking at the code in the model caching, it was ok to simply override in my model
use \GeneaLabs\LaravelModelCaching\Traits\Cachable {
        \GeneaLabs\LaravelModelCaching\Traits\Cachable::newEloquentBuilder insteadof \Kalnoy\Nestedset\NodeTrait;
}

I would imagine providing the trait that's causing issues doesn't do anything that would cause issues overriding might solve it. Otherwise you'll need to write your own trait to handle the conflict cases I would think.
I'm still testing for any side effects...

I had this problem with \Kalnoy\Nestedset\NodeTrait
I think this is working as a simple solution in my case, the node trait ran
public function newEloquentBuilder($query) {
    return new QueryBuilder($query);
}

Looking at the code in the model caching, it was ok to simply override in my model
use \GeneaLabs\LaravelModelCaching\Traits\Cachable {
        \GeneaLabs\LaravelModelCaching\Traits\Cachable::newEloquentBuilder insteadof \Kalnoy\Nestedset\NodeTrait;
}

I would imagine providing the trait that's causing issues doesn't do anything that would cause issues overriding might solve it. Otherwise you'll need to write your own trait to handle the conflict cases I would think.
I'm still testing for any side effects...

@Spodnet Have you found any side effects?

No issues so far :)

This is still an issue - is there any workaround, now nearly two years later?

@LiamAird Please open a new issue with full stack trace and query and all the version information.

@Spodnet @indowebdeveloper @Daniyal-Javani @eelco2k Could you give release 0.10.2 a try and let me know if that fixes the issue? Please see the readme section towards the top regarding conflicting packages as how to implement it. Thanks!

I tried implementing the fix, but get the error:
Call to undefined method GeneaLabs\LaravelModelCaching\ModelCaching::useBuilder()
use GeneaLabs\LaravelModelCaching\ModelCaching;
use Kalnoy\Nestedset\QueryBuilder;

class AppServiceProvider extends ServiceProvider
{

    public function register()
    {
        //
    }

    public function boot()
    {
         ModelCaching::useBuilder(QueryBuilder::class);
    }

Can you make sure you got the latest update, change your composer json to
"genealabs/laravel-model-caching":"^0.10.2",

then run composer update again.

@mikebronner Its already at that version.

Hmmm, ok. Leave it at release 0.10.1 for now, I'm working on an update to this functionality and hope to release it in the next day or so.


Expose Model classes to Schema methods

Related to #397

Pull Request Test Coverage Report for Build 593

4 of 6 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 84.204%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/Model.js
4
6
66.67%

Totals

Change from base Build 586:
0.1%

Covered Lines:
1853

Relevant Lines:
2130

💛  - Coveralls

My bad, I pushed a new commit to the same branch by mistake today, it got added to the pull request. It's all good now.


Add Rails/OutputSafety Cop

This adds a new cop tighten security around Rails output safety helpers like .html_safe and raw. While you may need .html_safe in a handful of cases, it was too easy to casually use without careful review. Instead of just using content_tag(:div, something) in a safe way in a helper method, "<div>#{something}</div>".html_safe would be used instead. In instances .html_safe were is necessary, we use an inline # rubocop:disable Rails/OutputSafety comment after security review.

You might want to add some rule about this in the Rails style guide document as well. Such changes require a changelog entry.

You might want to add some rule about this in the Rails style guide document as well

Wheres that at?

Such changes require a changelog entry.

👍

@bbatsov pushed some changes based on your suggestions.

Wheres that at?

https://github.com/bbatsov/rails-style-guide
Apart from the failing build, the cops looks OK to me. You'll have to rebase, though. What's the reason why this is disabled by default? I'm guessing it produces some false positives, right?

Apart from the failing build, the cops looks OK to me. You'll have to rebase, though.

👍 I'm on it.

What's the reason why this is disabled by default? I'm guessing it produces some false positives, right?

I'll just move it to enabled by default.

@bbatsov updated with changes.

👍 Thanks!

Hi @josh,
Any suggestions for the following case?
= f.submit '▶'.html_safe

Cheers.

How about using the decoded character?
= f.submit '▶'

Thanks @mikegee, but I was wondering if using a non-ASCII character wouldn't be a bad practice.

If you really need encoded entities, consider something like = f.submit html_encode('▶'). Others reading your views have no idea what ▶ means.

Thanks @josh!
Did you mean html_escape? Because either html_escape or h compiles to the following HTML:
<input type="submit" name="commit" value="▶" />

While = f.submit '▶'.html_safe generates a non-ASCII character (which is considered a good practice afaik):
<input type="submit" name="commit" value="▶" />

Cheers.

I think the cop should allow raw() for uninterpolated strings.

Butting heads against this cop with ' '.html_safe. There's no Rails helper for HTML entities. Uninterpolated strings should not be a violation, as there's no risk of code injection.
safe_join(words, ' '.html_safe)


A C++ Program

A C++ Program to show the simulation of the Solar System.hacktober2019

Hi! Looks pretty cool, but I'm not actually really actively maintaining this repository or anything any more, sooo.. I'll merge the PR to help you with hacktoberfest anyway lol :)


[usecase-wrt] Update test steps for ApplicationlocalStorage

Impacted TCs num(approved): New 0, Update 1, Delete 0
Unit test Platform: Android
Android test result summary: Pass 1, Fail 0, Block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-4901

LGTM


Adding REGION parameter to UNLOAD

The region parameter is necessary for the unload function. If it's not there, S3 raises an error:
"S3ServiceException:The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.,Status 301,Error PermanentRedirect".
Please keep in mind that my pull request is just an example. "us-east-1" should not be hard coded. It should be asked as a parameter beforehand.

why would you hardcode the region ?
It could be a default which is assumed when no other input is given.

why would you hardcode the region ?
It could be a default which is assumed when no other input is given.

Your suggestion is perfect. I just hard-coded it to clarify what the problem is. I'm not actually interested in changing the code myself. It's just an issue that I'm facing when trying to use this library.
Maybe I should have posted this as an issue instead.

Closing for now since it’s been a while (let me know if you’re still working on this)


[BUG] Timestamp fields will not recognized in usage with Cross Cluster Search

What is the bug?
Anomaly detection cannot determine timestamp fields in usage of cross cluster search. Error message is "Timestamp field: (@timestamp) is not found in index mapping". See Screenshot:

Even other existing timestamp field are not recognized.

How can one reproduce the bug?
Steps to reproduce the behavior:

Create an Remote Cluster for Cross Cluster Search
Index Remote Cluster in Opensearch Dashboard
Open Anomaly Detector Plugin and create a new Detector with the Remote Cluster as Datasource

Add "@timestamp" or other valid datefield as timestamp field

What is the expected behavior?
Even with Cross Cluster Search and manually entried Datasource/Timestamp Fields should the anomaly detection find my Documents.
What is your host/environment?
Azure AKS Kubernetes v.1.25
Opensearch2.6
Opensearch-Dashboard2.6

Crazyigor1987@, thanks for reporting the issue. We don't support remote index now. Will add the issue to our backlog.

@kaituo we do support remote indices - see https://github.com/opendistro-for-elasticsearch/anomaly-detection-kibana-plugin/pull/244
The difference is, then the configured timestamps and feature fields have to be manually input. On first glance, this looks to be some issue with the validation API, where it is unable to pull details from the remote indices. Is this a missed use case @amitgalitz ?

@ohltyler yes, we supported it partially when fgac is not enabled. I guess validation does not consider that case.


Cookie Editor Extension add Helpful to handle Cookies on websites

Description
Cookie Editor helps you to get all cookies add cookies fetch cookies from particular website remove cookies
I would like the Cookie Editor extension to offer a user-friendly interface that allows for easy searching, filtering, and batch-editing of cookies. The extension should support advanced filtering by domain, expiration date, and other attributes. Additionally, a feature to export and import cookies in various formats (JSON, CSV) would be highly beneficial.
Fixes:  #1172

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@Sulagna-Dutta-Roy Please review this PR, added a chrome extension useful for cookie setting .
And add the suitable level labels


Feature request : add a setting to filter the tasks from a note

For the moment, we can only filter with the status of the task. This can be a problem, especially if you have a lot of tasks and don't want all of them to yield rewards.
Would it be possible to add an option where we would put a path to a note, to only retrieve the tasks on this note?
If not, will there be more advanced ways to filter tasks in the future?
Thanks in advance,

I would also like to second this feature request.
Currently I have way too many checkboxes in my vault and filter out the important ones that are actual tasks with #task using the tasks plugin.
I think having the ability to filter by hashtag would be essential for me to move forward with using this plugin.
It's an awesome plugin and I really want to use it but for me I think this would be necessary to move forward

@rchaklashiya Hi! Thanks for your suggestion, I think to add filter by hashtag in version 1.1.0 on 1 May or early.
Currently I focus my work on fixing bugs till middle of this month. After I will implement more features.

I added this feature d1f890dae8e5b91703570b2ebea9fc6e27024c85 it will be available from 1.1.0 (Release 15 April 2024). So I close this issue. Thanks for suggestion!


Release v0.4.0

Codecov Report

Merging #80 (2c125a5) into master (0589dc3) will not change coverage.
The diff coverage is n/a.

 Everything else is non-breaking.


Integrations spec

#Changes made:

Set up capybara and other gems in the repository.
Wrote tests for the following views:

login
user index
user show
post index
post show

Hello, @AshakaE 🙌
Thank you for reviewing my work. I will proceed to merge these changes into the dev branch. 🚀
Happy coding to you too! 💻


why default is not a semver?

AFAIK
distance = "{version}.post{distance}+{vcs}{rev}"

is not a semver.

The default version formats are meant to produce PEP 440-compliant versions, not semver versions.  While the two have some overlap, they are not the same, and it appears that the only form for a non-final release that is compatible with both forms is "<version>+<build>".  I see no advantage to strictly sticking to semver in the Python world, but I do see an advantage to incorporating the tag distance into a ".post" or ".dev" component instead of a local component.


Overriding a style

Hello,
I've implemented a component button but I'd like to override the style; for instance moving the text to center it properly. I can't find how to do so.
Any thoughts ?

also with override object, the textColor, backgroundColor, and rippleColor can't be changed. Please solve the issue

@DavitVosk actually, it can, but you must choose specific color variables (those from the library itself). I managed to do it eventually


bug:  ERR_MODULE_NOT_FOUND on drizzle nextauth option

Provide environment information
System:
OS: Windows 11 10.0.22631
CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900KF
Memory: 45.12 GB / 63.83 GB
Binaries:
Node: 18.18.2 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
npm: 9.8.1 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
pnpm: 8.13.1 - ~\AppData\Local\pnpm\pnpm.CMD
bun: 1.0.21 - ~.bun\bin\bun.EXE
Describe the bug
⨯ Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'C:\Users\hitech\code\nomad_competition\node_modules.pnpm@auth+drizzle-adapter@0.4.0\node_modules@auth\drizzle-adapter\lib\utils' imported from C:\Users
\hitech\code\nomad_competition\node_modules.pnpm@auth+drizzle-adapter<EMAIL_ADDRESS>at new NodeError (node:internal/errors:405:5)
at finalizeResolution (node:internal/modules/esm/resolve:327:11)
at moduleResolve (node:internal/modules/esm/resolve:946:10)
at defaultResolve (node:internal/modules/esm/resolve:1132:11)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ModuleWrap. (node:internal/modules/esm/module_job:77:40)
at link (node:internal/modules/esm/module_job:76:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
Reproduction repo
https://github.com/xkalf/nomad_competition
To reproduce
pnpm dev and go to the localhost:3000 in server console is getting error calling db request is also not woking for this bug
Additional information
No response

i got fix by auth js team
link


Choosing covariates

Try models with combinations of the following variables:

Ruggedness - need to try a few different resolutions (9, 25, 49) - can do AIC-based model selection to identify best ruggedness value
Viewshed
Distance to road - should predict when they switch from walking to driving
Vegetation type
Area of chaparral within 120 meters
Distance to vegetation type boundary
Distance to headquarters - would expect them to move from driving --> stopping

Testing all univariate models https://github.com/kaitlyngaynor/hopland-hunting/commit/a1bab961d4086eed86134e51d699c29747b92cb1


Third party assemblies do not load every time after idling

I'm experiencing an issue with a blobtriggered function, in which I utilize multiple third party dlls. After running succesfully for a while, it will fail to load the assemblies in the bin folder after idling. But not every time.
Provide the steps required to reproduce the problem

Listen to a blobtrigger (might be every trigger, I don't know), and call a function in a third party DLL.
Watch it fail to load the assembly after going idle, but only sometimes. This means it sometimes recovers the next time it idles.

Expected behavior

Should continue to run and start up after idling.

Actual behavior

Fails to load 3rd party dll's in the bin folder.

Related information
Function is written in C#, simply does this:
#r "Lasso.Content.dll"
#r "Lasso.Data.dll"
#r "Lasso.Functions.dll"
#r "Lasso.Domain.dll"

using System;

public static async Task Run(Stream blob, string name, TraceWriter log)
{
    try {

        await new Lasso.Functions.EventHandlerFunction().Run(name);
    } catch (Exception e)
    {
        log.Error(e.Message);
    }
}

The specific exception:
Exception while executing function: Functions.EventHandlerFunction
Microsoft.Azure.WebJobs.Host.FunctionInvocationException : Exception while executing function: Functions.EventHandlerFunction ---> System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation. ---> System.TypeLoadException : Could not load type 'Lasso.Functions.EventHandlerFunction' from assembly 'Lasso.Functions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
   at async Submission#0.Run(Stream blob,String name,TraceWriter log) at  : 17
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Submission#0.Run(Stream blob,String name,TraceWriter log)
   End of inner exception
   at System.RuntimeMethodHandle.InvokeMethod(Object target,Object[] arguments,Signature sig,Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj,Object[] parameters,Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj,BindingFlags invokeAttr,Binder binder,Object[] parameters,CultureInfo culture)
   at async Microsoft.Azure.WebJobs.Script.Description.DotNetFunctionInvoker.InvokeCore(Object[] parameters,FunctionInvocationContext context)
   at async Microsoft.Azure.WebJobs.Script.Description.FunctionInvokerBase.Invoke(Object[] parameters)
   at async Microsoft.Azure.WebJobs.Host.Executors.FunctionInvoker`1.InvokeAsync[TReflected](Object[] arguments)
   at async Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.InvokeAsync(IFunctionInvoker invoker,Object[] invokeParameters,CancellationTokenSource timeoutTokenSource,CancellationTokenSource functionCancellationTokenSource,Boolean throwOnTimeout,TimeSpan timerInterval,IFunctionInstance instance)
   at async Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.ExecuteWithWatchersAsync(IFunctionInstance instance,IReadOnlyDictionary`2 parameters,TraceWriter traceWriter,CancellationToken…

This is the same issue reported here, correct?
When did you first notice this issue? Can you share your function app name directly or indirectly so we can take a closer look?

Hi. Yep, that's me aswell.
My function app name is called Lasso-Services, the function called EventHandlerFunction. EU West.

@EmilBechMadsen looking at some logs and execution information, there are a couple of things we can do to resolve this issue:

Looks like multiple functions are using the same set of assemblies with multiple copies deployed. While this alone is not an issue, it often leads to mismatched deployments if you're dealing with multiple versions. I'd recommend deploying those assemblies to a common folder and referencing them with a relative path (e.g. #r "..\shared\myassembly.dll")
We noticed some assembly resolution subscriptions pulling from the current domain, which may also cause issues since private assemblies are loaded into a different context and you may end up with an incorrect version or interfering with the runtime logic. Those were also accumulating
Only the direct assembly reference needs to be added to your function. So you only need to #r the assembly that implements your function method and the indirect references will be automatically resolved. While this alone wouldn't cause the issue, it is the recommended practice so you don't have unnecessary metadata references

I'm still inspecting some of the data, but wanted to share those findings.

Hi Fabio. Thanks for investigating.

I'll take a swing at the shared assemblies.
Are you referring to AppDomain.CurrentDomain.AssemblyResolve in regards to resolutionsubscriptions? If so, that was just an attempt at mitigation, so I suppose we can ignore that.
Will remove second-degree #r's :)

I've now implemented above suggestions and will report back in a day or two whether that solved my problem.
If it does indeed work, I think it's because I had another version of the assembly with the same version number, but without the missing EventHandlerFunction class in another function's bin folder. I was not aware that this was a problem, and that they would sometimes run using the assembly of another function.
Something not related to this issue:
The NuGet package management really is dodgy at best. Sometimes a package will install correctly, othertimes it won't. During these changes, some packages would just refuse to install no matter what I did (even if it said it was installed and in the file system), so I ended up resorting to manually putting my otherwise NuGet-referenced dll's in the shared folder as well. This worked fine (Even with WindowsAzure.Storage v. 8.1.1).

Yes, what you've described with the mismatch could indeed cause issues.
About the NuGet, if you have more information you can share (error messages, details about the behavior, etc.) that would help. The restore process uses the same NuGet restore logic (same actual client) as what you'd see locally, the key difference (and what sometimes causes some of the issues with it) is the remote file system, but without more information, we can't really pinpoint that as the cause.

Preliminary results after 24 hours of running: It worked.
About the NuGet: I didn't really intend on you to fix it, as we all know NuGet is kind of odd sometimes. I can't really say much other than it wouldn't run because it was missing files that I had included in my project.json. When I forced a restore (by changing project.json), it would even say "Installed XXXX" (the exact missing assembly). It still wouldn't run properly. Not even after a restart of the Function app, deleting all NuGet caches or changing the version numbers back and forth.

Good to hear the original issue was resolved.
How often are you running into the NuGet issues?
It would be good to track it separately, so I'll close this issue for now, and if you run into this again, would you mind opening a new issue and sharing both, the project.json AND the project.lock.json files (as well as the errors you see)?
Thanks!


react-native link broken for iOS: links libBackgroundGeolocation.a instead of libRCTBackgroundGeolocation.a

Your Environment

Plugin version: 0.5.0-alpha.35
Platform: iOS
OS version: 11.0
Device manufacturer and model: Apple Simulator
React Native version: 0.50.4
Plugin configuration options: {debug: true}
Link to your project: not public

Context
After linking the native dependencies through react-native link the native dependencies are not available in iOS.
Expected Behavior
react-native link  should create the links to native dependencies correctly so that the plugin works out of the box without further manual intervention
Actual Behavior
react-native link links libBackgroundGeolocation.a instead of libRCTBackgroundGeolocation.a. This results in the native dependencies not being available
Possible Fix

Steps to Reproduce

create a react-native app
install react-native-background-geolocation
run react-native link
try to use the module in the javascript code, for example

import BackgroundGeolocation from 'react-native-mauron85-background-geolocation';

....

BackgroundGeolocation.configure({debug: true})

Context

Debug logs
TypeError: Cannot read property 'configure' of undefined

Couldn't reproduce your issue. I've just tried:

react-native init myapp && cd myapp
yarn add react-native-mauron85-background-geolocation
react-native link react-native-mauron85-background-geolocation
import module and call configure and start in App.js
react-native run-ios

Env:
Plugin version: 0.5.0-alpha.35
React Native: 0.56
XCode: 9.3
I had to run react-native run-ios twice, because on first attempt it didn't build app correctly, but it was react-native or xcode issue.

@mauron85 Thanks for your feedback. Which library is it linking in your case? libRCTBackgroundGeolocation.a or libBackgroundGeolocation.a.


How can I keep the original video quality?

The question

I'd like to create an exact copy from a given audio or video file, keeping the quality, format, codec, framrate, bitrate, etc... (I just get bigger or smaller files, but can't get to get a file with the same attributes and size)

What you have tried

I'm trying to remove settings hoping it takes the original file values.
I also tried:
.setConstantRateFactor(0)

Solution: (In case someone has the same issue)
FFmpegBuilder builder = new FFmpegBuilder()
...
.setAudioCodec("copy")
.setVideoCodec("copy")

Thank you for the issue and answer! I'll go ahead and close this issue, as you have answered it yourself.
Feel free to reopen or create a new issue.


New Rule: no-id-selector

Rule details
Flag any CSS selector that uses the ID selector
What type of rule is this?
Warns about a potential problem
Example code
#one { /* lint error */
  background-color: yellow;
}

h1#heading { /* lint error */
  color: rebeccapurple;
}

The #id selector has very high specificity and doesn't always play well with other rules. An alternative is to use a .class selector instead.
When using a component-based UI framework, id selectors are often not very useful. You can hardcode an id into a component, but this makes the component non-reusable. The framework-generated unique ids cannot be referenced in CSS. Therefore, using id selectors in these cases is likely a mistake.
Participation

[x] I am willing to submit a pull request to implement this rule.

Additional comments
From MDN:

The ID selector has high specificity. This means styles applied based on matching an ID selector will overrule styles applied based on other selector, including class and type selectors. Because an ID can only occur once on a page and because of the high specificity of ID selectors, it is preferable to add a class to an element instead of an ID. If using the ID is the only way to target the element — perhaps because you do not have access to the markup and cannot edit it — consider using the ID within an attribute selector, such as p[id="header"].

A CSS equivalent to JavaScript's no-restricted-syntax rule would cover this use case and more.
We couldn't take this approach in Stylelint because the general parser we use is limited to a few node types. We ended up with many separate rules, including selector-max-id, that disallow or limit things. We turn on only a handful of these in our standard config because we found restricting CSS syntax is rarely universal. There is also the stylelint-no-restricted-syntax plugin that can target these few node types.
The CSSTree parser is far more granular and id selectors are a node type (IdSelector):
{
    "rules": {
        "no-restricted-syntax": [
            "error",
            {
                "selector": "IdSelector",
                "message": "Id selectors are not allowed."
            },
        ]
    }
}

(Mixing AST Selectors and CSS Selectors could be a little confusing, though.)

The ID selector has high specificity... If using the ID is the only way to target the element — perhaps because you do not have access to the markup and cannot edit it — consider using the ID within an attribute selector, such as p[id="header"].

A rule to limit specificity would be complementary to a no-restricted-syntax one. In Stylelint, we have selector-max-specificity, and people use it when they want to limit the specificity of selectors.

A rule to limit specificity would complement the no-restricted-syntax one. In Stylelint, we have selector-max-specificity, and people use it when they want to limit the specificity of selectors.

Ah interesting, that may be a better way to go than just limited blocking of ID selectors.

Looking into this right now. Would it make sense to ever set a minimum specificity? For instance, would a rule like this have any value?
specificity: ["error". {
    max: [0, 3, 5],
    min: [0, 1, 0]
}

Rough draft: https://github.com/eslint/css/pull/24

or they get abused by developers instead of using classes
dialog > div > span:nth-child(1) > img {}

I agree. Classes are always better than tag selectors and less prone to breakage

I think it's worth noting that there is a diverse set of CSS methodologies, and type selectors are sometimes a good fit, especially when the CSS is scoped.
For example, with the @scope at-rule:
@scope (.component) to (.content) {
  a {
    color: red;
  }
}

Or within the Shadow Dom using (Lit) Web Components:
import {LitElement, html, css} from 'lit';
import {customElement} from 'lit/decorators.js';

@customElement('my-element')
export class MyElement extends LitElement {
  static styles = css`
    p {
      color: green;
    }
  `;
  protected render() {
    return html`<p>I am green!</p>`;
  }
}

The nice thing about a no-restricted-syntax rule is that people can configure it for their preferred approach. For example, if they use something like CSS modules, they'd probably want to disallow:

id selectors
type selectors
top-level combinators

{
    "rules": {
        "no-restricted-syntax": [
            "error",
            {
                "selector": "IdSelector",
                "message": "Id selectors are not allowed."
            },
            {
                "selector": "TypeSelector",
                "message": "Type selectors are not allowed."
            },
            {
                "selector": "Rule > SelectorList > Selector > Combinator",
                "message": "Top-level combinators are not allowed."
            },
        ]
    }
}

By only disallowing top-level combinators, you'll still be able to use them in powerful pseudo-classes like :has(). It would allow things like this:
.component {
  &:hover {}
}

.child {
  &:has(+ .alt) {}
}

While disallowing things like:
#id {
 & > div
    & > div {}
  }
}

A no-restricted-syntax rule would cover many of Stylelint's disallow and limit rules, including selector-max-id and selector-combinator-disallowed-list.

It turns out that the core no-restricted-syntax rule can already be used with CSS!
You can disallow id and type selectors with:
import css from "@eslint/css";

export default [
  {
    files: ["**/*.css"],
    language: "css/css",
    ...css.configs.recommended,
  },
  {
    rules: {
      "no-restricted-syntax": [
        "error",
        {
          selector: "IdSelector",
          message: "Id selectors are not allowed.",
        },
        {
          selector: "TypeSelector",
          message: "Type selectors are not allowed.",
        },
      ],
    },
  },
];

Thinking out loud: maybe what we're really after is a rule that limits the complexity of selectors? If that was the original intent of selector-max-specificity, then maybe a rule like selector-complexity could serve that purpose?
We could have options for:

maximum specificity
disallow ID selectors
disallow type selectors
disallow :is
disallow :where

Would that make sense?

Selector complexity in CSS is an odd one because it's:

a sliding scale of what you get for your money
multifaceted with a lot of features in play

It seems that the way people use selectors is a broad spectrum. On one side, there are people who:

only use class selectors
avoid combinators
avoid functional pseudo-classes
avoid selector lists

People at the other end lean into all the selector features. For example, using :has() with other functional pseudo-classes and combinators to move styling logic out of JavaScript into CSS:
/* selecting cards that don't have an `img` within */
.card:not(:has(img)) {}

/* selecting boxes that have 3 or more items */
.box:has(.item:nth-last-child(n + 3)) {}

/* selecting boxes that preceded a circle */
.box:has(~ .circle) {}

Or, using :is() to remove duplication in selector lists:
/* this */
header :is(h1, h2) a {}

/* instead of this */
header h1 a,
header h2 a {}

Or, using type selectors within @scope:
@scope (.component) to (.content) {
  a {
    color: red;
  }
}

And then there's everyone in between those ends of the spectrum.
Realising that there isn't a one-size-fits-all when it comes to selector use, we added a bunch of rules to Stylelint that people can use to enforce their conventions based on their ideas of complexity and consistency. They can use these rules to limit the:

number of id, class, attribute, type, pseudo-class and universal selectors
number of compound selectors
number of combinators
types of combinators, pseudo-class selectors, pseudo-element selectors, attribute selectors and attribute operators

And a rule to disallow qualifying, and a general one to disallow patterns in selectors.
We also added allowed versions of many of the list rules, e.g. allowing a subset of combinators, but, in hindsight, this is a less common use case which you can probably avoid.
Some may see complexity as the number of compound selectors or combinators, whereas for someone else, it may be the number of different types of selectors used (id, class, universal and so on). It'd be great to accommodate both with this rule. Rather than single out id and type selectors and the :is() and :where() pseudo-classes, can it provide options to limit the number and types of the different selectors and combinators?

Rather than single out id and type selectors and the :is() and :where() pseudo-classes, can it provide options to limit the number and types of the different selectors and combinators?

Yes, that was actually my intent. I just included some examples off the top of my head in my previous comment.
It seems like a rule that allows everything to start and you have to configure it to disallow something might make sense? So maybe you'd have a "max" option for each part of a selector (i.e., maxIds, maxClasses, etc.)?


Inlined content schema in RequestBody missing type

In the Pet Store specification (https://petstore.swagger.io/v2/swagger.json) the only 2 inlined request body content schemas (i.e., POST of"/pet/{petId}/uploadImage" and POST of "/pet/{petId}") have type: object.
However, when parsing it with this library and priting the OpenAPI object, i noticed that type: null. This is not true for $ref 'ed request body content schemas which also have type: object and swagger-parser correctly detects their type.
It may be worth noting that this specification is Swagger v2 rather than OpenAPI v3, so swagger-parser still performs a conversion while parsing (which may or may not influence the outcome).

can you raise a PR with a failing test case.


No output torch 2.3.0, python 3.10.12

Very excited to try out Depyf, hoping you can point me in right direction for the following
import torch
from torch import _dynamo as torchdynamo
from efficient_kan import KAN
from torch.profiler import profile, record_function, ProfilerActivity
import depyf

torch.set_float32_matmul_precision("high")

model = KAN([28 * 28, 64, 10])
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
model.to(device)
model = torch.compile(model)

# Warmup
for _ in range(10):
    model(torch.randn(64, 28 * 28).to(device))

def main():
    for _ in range(100):
        model(torch.randn(64, 28 * 28).to(device))

if __name__ == "__main__":
    with depyf.prepare_debug("./depyf_debug"):
        main()

Running the previous with TORCH_COMPILE_DEBUG gives the expected torchinductor output, but depyf does not write anything to the depyf_debug directory.
I also get UserWarning: You are trying to debug torch.compile. Please make sure the code runs multiple times to cover all the possible branches., but I believe I am running it several times
Testing it in this repo if model will help.
Thanks for your help :)

Hi, can you try to move the warmup code into main? I think your code is already compiled before you use depyf.prepare_debug , so it cannot capture anything for you.
e.g.
def main():
	# Warmup
	for _ in range(10):
	    model(torch.randn(64, 28 * 28).to(device))

    for _ in range(100):
        model(torch.randn(64, 28 * 28).to(device))

Ahh facepalm, thanks

@jturner116 does it help then?

@youkaichao Yeah works great, thank you sir!


Database prefix in config

Is there anyway to define database prefix in config.php?

IIRC, we don't support that. That would be a massive (and breaking) change. Making such a big change would also deprecate most of the extensions, and they won't work in the new versions unless developers update them.
However, this might be a nice feature, if you ignore the circumstances somehow.

IIRC, we don't support that. That would be a massive (and breaking) change. Making such a big change would also deprecate most of the extensions, and they won't work in the new versions unless developers update them.
However, this might be a nice feature, if you ignore the circumstances somehow.

In all fairness. this should be marked as a security feature and should not be written off as to difficult. as the purpose of this is to make table names less likly to be guesed by an attacker. The software is opensource so any attacker would already know the table names in the database... taking that advantage away reduces the risk.
As for mods, This software is going though alot of changes and updates..... no reason why mods should not also go through the same updates and changes as long as it is justified as being reasonable

Well, if we're ready to deploy a breaking change like this, custom database prefixes would be a nice feature.

Well, if we're ready to deploy a breaking change like this, custom database prefixes would be a nice feature.

It doesn't have to be a breaking change. If the prefix is set to be empty, wouldn't it still read from an old DB?

Well, if we're ready to deploy a breaking change like this, custom database prefixes would be a nice feature.

It doesn't have to be a breaking change. If the prefix is set to be empty, wouldn't it still read from an old DB?

Well, if it breaks existing extensions, it is a breaking change. Extensions that are old will still look for the default prefix, instead the ones with customized prefixes. We'll have to update existing extensions and components indeed.

I think that if you are going to bring something that was essentially abandoned for years back to life and meet new best practices, security standards, etc. then breaking changes are just inevitable, and are something that need to be lived with.
There could always be a disclaimer on the installer at the point of being able to enter a custom prefix that this is an advanced option and may break extensions that have not been updated since .
Then, if people want to use old extensions or are not sure then they could just use the default.
Ultimately, what we need is a system where all extensions clearly show the latest version of BoxBilling that they have been tested to work with.

I suspect that the vast majority of our current integrations and extensions don't even fully work right, so I guess at the end of the day it's not all that important

There could always be a disclaimer on the installer at the point of being able to enter a custom prefix that this is an advanced option and may break extensions that have not been updated since .
Ultimately, what we need is a system where all extensions clearly show the latest version of BoxBilling that they have been tested to work with.

I liked these ideas.


fix: Input background should be white

Fixes #23.

Already fixed in https://github.com/containous/faency/pull/27


Small Bug: Atlas of Mutual Heritage

The link associated with dataset Atlas of Mutual Heritage is broken - https://dev.whgazetteer.org/datasets/819/places
Perhaps something I can fix once I have access to admin page
This is also a test for my first issue!

Tried the webpage link, to https://www.atlasofmutualheritage.nl/, came up for me. Is that the one you mean?

That's the one I mean. It won't open on my computer - tried Chrome and Microsoft Edge. And it also won't open on my colleagues computer either. Doesn't seem like an whg problem then.

That's the one I mean. It won't open on my computer - tried Chrome and Microsoft Edge. And it also won't open on my colleagues computer either. Doesn't seem like an whg problem then.

I will keep poking at it

Fixed in production -- looks ok now


Sorting in an array in place

Challenge Sort Arrays with sort has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

var array = [1, 12, 21, 2];

// Only change code below this line.

array.sort(function(a,b) {
  return a - b; });

Hey, currently your code is sorting the elements from smallest to largest. If you want to sort them from largest to smallest then you should to return b - a;

Thank you friend!


Chore: Typos fixed in files of doc/source/api/executors/ folder

[X] I have added the tests to cover my changes.
[X] I have updated the documentation and CHANGELOG accordingly.
[X] I have read the CONTRIBUTING document.

 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.


generated repository should return concrete type instead of interface

Is your feature request related to a problem? Please describe.
generated repository should return concrete type instead of interface
currently NewUserRepository in example is returning interface.
However as suggestion in go codereview

Go interfaces generally belong in the package that uses values of the interface type, not the package that implements those values. The implementing package should return concrete (usually pointer or struct) types ^1

*UserRepositoryMongo should be returned.
btw you can assert the implementation in test file
// user_repo_test.go
var _ UserRepository  = (*UserRepositoryMongo)(nil)

Describe the solution you'd like
return concrete type

I see. I will work on it.

Fixed by https://github.com/sunboyy/repogen/pull/44


Taxon constraint: GO:0009089 | lysine biosynthetic process via diaminopimelate

Please provide as much information as you can:

GO term ID label:

GO:0009089 | lysine biosynthetic process via diaminopimelate #

Request to add a taxon constraint:

**never in taxon: **

pombe/cerevisaie

Supporting evidence if available (e.g PMID):

This pathway operates in some fungi, but pombe and cerevisiae only operate the AAA pathway

duplicate https://github.com/geneontology/go-ontology/issues/28877


Privacy Manifest

Doesn't Fastis need a Privacy Manifest?

Hi, Fastis is not on the list, so we don't need a a Privacy Manifest.
https://developer.apple.com/support/third-party-SDK-requirements/

Hi, Fastis is not on the list, so we don't need a a Privacy Manifest.
https://developer.apple.com/support/third-party-SDK-requirements/

Thank you for your response.🤩


Refactored macrotypes and turnstile into separate packages

Both macrotypes and turnstile are now separately installable packages, to
minimize what you need to depend on.
Now, the -lib packages do not require rackunit or racket-docs, which are only
needed by the test (-test) or documentation (-doc) packages.
In the process, some test code has been refactored
Now macrotypes comes as

macrotypes, the meta-package that installs of the following
macrotypes-lib, the implementation
macrotypes-example, the example languages
macrotypes-test, the tests which test both -lib and -example

The testing additional infrastructure now exists in

macrotypesunit-lib
However, there is some poor abstract between this and some of the tests.
Particularly:
rackunit-kindchecking is not abstracted out into this packaage
there are stub files in the tests that simply import macrotypesunit-lib
the hierarchy in macrotypesunit-lib is bad

Now turnstile comes as

turnstile, the meta-package
turnstile-lib, the implementation
turnstile-doc, the docs
turnstile-example, the example languages
turnstile-test, which tests both -lib and -example

Closes #67 and closes #52.

Before merging, @stchang, please look at the two failing tests. One was disabled previously, and I think the failure is a problem in the test file ("trivial-test.rkt"). One I'm not sure about ("stlc+effect-tests.rkt")


Fix eol checking for read array in ExtendedBufferedReader

Characters in buffer before offset are unspecified

Can you please explain some more what problems you're running into without this fix? A test case that fails without your change but is successful with this change would help me to understand this proposal.

Placeholder JIRA ticket is https://issues.apache.org/jira/browse/CSV-158

You may not be sure buffer in call same as for previously read call. So you can just create new buffer without any initialization and call read method with non-zero offset. In this case character at position i-1 has undefined value. So you should check against offset for lastChar instead of zero.

Can you provide a unit test patch that shows the main code failing and then passing with this fix?

Without the fix getLineNumber method returns 3.

@mirasrael thank you for the test. Things are getting clearer now. How would a CSV file look like which the parser fails to parse because of this bug?

Sorry. Its hard to remember where I face this bug, because I posted it year ago.

@mirasrael yes I understand this and I'm very thankful that you reported it in the first case. I'm just trying to find out what the implications of applying this patch is. :-)

hi @britter after review the code，I think what @mirasrael means is that when use a new char[] buf and  offset start from 5 in that way buf[0] to buf[4] are unspecified. so when i equals offset (that means i is 5)  the  expression  (i > 0 ? buf[i - 1] : lastChar return buf[4]  but what should return lastChar.

@mirasrael
Please rebase on git master to we can see new build results.

Updated for master

https://issues.apache.org/jira/browse/CSV-158


Add floodfill algorithms

This PR adds floodfill algorithms, as well as an associated LargeCostMatrix struct to allow for u16 sized values for each position.
This is dependent on unreleased updates currently merged into the main branch of screeps-game-api, and will need the dependency version bumped once those updates are released.

Note: The errors in the test runs are due to the pinned version of screeps-game-api being 0.21, which does not have the Direction::iter implementation.


Github proof failed

I know it's likely it's my fault but in case it's a bug.
Link to proof.
https://gist.github.com/Robloxxx/4cfc7a3a4d6779c8cf0e3ecb97bdaeca

I have the same issue, it just suddenly stopped working:
proof - https://gist.github.com/Ni-Knight/c065227526a258e989da1cafc46208e5

@Ni-Knight Did you recently change your GitHub username? From your gist:

I am droravr on github.

@justinmccormick My bad, totally forgot I've done that =D
Thanks

@Robloxxx not sure if this means anything but the gist show your username with lower case r instead of R


[jk] Retry block runs from specific block

Summary

For standard python pipelines, retry block runs from a selected block. The selected block and all downstream blocks will be re-ran after clicking the Retry from selected block button.
This feature is not available for other types of pipelines (e.g. streaming or integration). Streaming pipelines don't have block runs, and users can still retry from failed block runs in integration pipelines.

Tests

@dy46 Can you review the BE changes? There's only a couple files.


Firebase version removed

When the project has firebase versions defined, then when you import it to any project you must will have to use the exact firebase vversion..
So now by removing those versions, you can set up any of the firebase versions  you want to add.

Thank you!


Test ci

Hey,
this is my understanding of what whould be done to fix https://github.com/mcollina/levelgraph/issues/149.
This is following discussion on  #150

The tests are not running on saucelabs: https://travis-ci.org/mcollina/levelgraph/jobs/171782745#L391-L397

Is the  SAUCE_USERNAME env defined in Circle CI ?
When I tried to set it locally, the test web test are executed.

Let's try merging.

Looks like this works

Indeed! Thanks!!!


"target" option for links in slate

There seems to be no way at the moment to add an attribute like target="_blank" to links created with the slate "create a link" button. Or am I missing something?

That's true, feel free to PR to fix that!

@arekkas Is there documentation available on adding plugins to the slate ory component? I'm pretty sure I went through all the docs but couldn't find anything. It would be helpful.

Not yet, but I'll direct you to the pieces:

You can pass plugins to the slate factory, see here
This is what a plugin looks like

Hope that helps

Also dofollow/nofollow may be relevant for links

@AlexanderReiswich  The slate plugin has now an "open in new tab/window" option. And its now very easy to add additional properties. Stuff like dofollow/nofollow should be now very easy to do!
Feel free to send in a Pull request for further improvement or reopen an issue if you need help!


Dataset browser url is still https://huggingface.co/nlp/viewer/

Might be worth updating to https://huggingface.co/datasets/viewer/

Yes! might do it with @srush one of these days. Hopefully it won't break too many links (we can always redirect from old url to new)

This was fixed but forgot to close the issue. cc @lhoestq @yjernite
Thanks @jarednielsen!

This was fixed but forgot to close the issue. cc @lhoestq @yjernite
Thanks @jarednielsen!


Failed to install helm-unittest

Hello, I am interesting in using helm-unittest.
But I failed to install helm3, ubuntu 18.04
wj@wj:~/ws/asr/kubernetes/bin/test$ rm -rf /home/wj/.local/share/helm/plugins/helm-unittest && helm plugin install https://github.com/lrills/helm-unittest --debug
[debug] updating https://github.com/lrills/helm-unittest
[debug] symlinking /home/wj/.cache/helm/plugins/https-github.com-lrills-helm-unittest to /home/wj/.local/share/helm/plugins/helm-unittest
plugin_install.go:73: [debug] loading plugin from /home/wj/.local/share/helm/plugins/helm-unittest
plugin.go:60: [debug] running install hook: /bin/sh -c $HELM_PLUGIN_DIR/install-binary.sh
Downloading
curl: (3) <url> malformed
Failed to install helm-unittest
For support, go to https://github.com/kubernetes/helm
Error: plugin install hook for "unittest" exited with error
helm.go:76: [debug] plugin install hook for "unittest" exited with error
main.runHook
        /tmp/helm-20191206-4731-1gu6wjh/src/helm.sh/helm/cmd/helm/plugin.go:67
main.(*pluginInstallOptions).run
        /tmp/helm-20191206-4731-1gu6wjh/src/helm.sh/helm/cmd/helm/plugin_install.go:79
main.newPluginInstallCmd.func2
        /tmp/helm-20191206-4731-1gu6wjh/src/helm.sh/helm/cmd/helm/plugin_install.go:50
github.com/spf13/cobra.(*Command).execute
        /tmp/helm-20191206-4731-1gu6wjh/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
        /tmp/helm-20191206-4731-1gu6wjh/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
        /tmp/helm-20191206-4731-1gu6wjh/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
        /tmp/helm-20191206-4731-1gu6wjh/src/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
        /home/linuxbrew/.linuxbrew/Cellar/go/1.13.4/libexec/src/runtime/proc.go:203
runtime.goexit
        /home/linuxbrew/.linuxbrew/Cellar/go/1.13.4/libexec/src/runtime/asm_amd64.s:1357

Error message is as above
Do you have any idea?

Hello @hehe717,
The current version is not compatible for helm 3,
You van use this fork https://github.com/quintush/helm-unittest.
It has the same funtionality (and more) and is compatible with helm 3.
Greetings,
@quintush

Close due to archiving repository.
Sorry for not presenting so long. I've been working on another project and don't have time to for helm-unittest.
Please consider other working forks like quintush/helm-unittest.


[microNPU] Fix incorrectly calculated stride when converting NHWC to NHCWB16

Fixes an issue that causes strides to be incorrectly calculated when the number of channels in the input is less than 16 and involves a conversion from NHWC to NHCWB16. This is due to TVM being 'too smart' when analyzing generated TE and removing compute that is deemed unnecessary. Consequently, strides over data are incorrectly calculated leading to an output mismatch.
The PR uses a reduce sum operation to trick TE's data dependency analyzer into looping over a whole block (16), rather than the number of channels actually used (< 16). This causes the calculated strides to be a multiple of 16 which is required for NHCWB16 format.
cc @mbaret @ekalda @manupa-arm @NicolaLancellotti @dchauhan-arm

Thanks! @lhutton1 @mbaret .


Need some docs to import into a webpack project.

I'm new to webpack and it would be nice to have some docs to import this component into a webpack project.

Ive never used this in a webpack projects, others have done so though. But Iam going to try creating a basic project. But It should work out of the box

Hey thanks for the reply, i managed to import it without any issues.
rules: [

        /*
         * Typescript loader support for .ts
         *
         * Component Template/Style integration using `angular2-template-loader`
         * Angular 2 lazy loading (async routes) via `ng-router-loader`
         *
         * `ng-router-loader` expects vanilla JavaScript code, not TypeScript code. This is why the
         * order of the loader matter.
         *
         * See: https://github.com/s-panferov/awesome-typescript-loader
         * See: https://github.com/TheLarkInn/angular2-template-loader
         * See: https://github.com/shlomiassaf/ng-router-loader
         */
        {
          test: /\.ts$/,
          use: [
            {
              loader: '@angularclass/hmr-loader',
              options: {
                pretty: !isProd,
                prod: isProd
              }
            },
            { // MAKE SURE TO CHAIN VANILLA JS CODE, I.E. TS COMPILATION OUTPUT.
              loader: 'ng-router-loader',
              options: {
                loader: 'async-import',
                genDir: 'compiled',
                aot: AOT
              }
            },
            {
              loader: 'awesome-typescript-loader',
              options: {
                configFileName: 'tsconfig.webpack.json'
              }
            },
            {
              loader: 'angular2-template-loader'
            }
          ],
          exclude: [/\.(spec|e2e)\.ts$/]
        },

        /*
         * Json loader support for *.json files.
         *
         * See: https://github.com/webpack/json-loader
         */
        {
          test: /\.json$/,
          use: 'json-loader'
        },

        /*
         * to string and css loader support for *.css files (from Angular components)
         * Returns file content as string
         *
         */
        {
          test: /\.css$/,
          use: ['to-string-loader', 'css-loader'],
          exclude: [helpers.root('src', 'styles')]
        },

        /*
         * to string and sass loader support for *.scss files (from Angular components)
         * Returns compiled css content as string
         *
         */
        {
          test: /\.scss$/,
          use: ['to-string-loader', 'css-loader', 'sass-loader'],
          exclude: [helpers.root('src', 'styles')]
        },

        /* Raw loader support for *.html
         * Returns file content as string
         *
         * See: https://github.com/webpack/raw-loader
         */
        {
          test: /\.html$/,
          use: 'raw-loader',
          exclude: [helpers.root('src/index.html')]
        },

        /*
         * File loader for supporting images, for example, in CSS files.
         */
        {
          test: /\.(jpg|png|gif)$/,
          use: 'file-loader'
        },

        /* File loader for supporting fonts, for example, in CSS files.
        */
        {
          test: /\.(eot|woff2?|svg|ttf)([\?]?.*)$/,
          use: 'file-loader'
        }

      ],


Is this a bug or I am missing some config? Only happens on Android with Google Maps. Works fine with iOS Apple Maps.

Summary
Here's a test Snack https://snack.expo.dev/@umrashrf89/testmapmarker?platform=ios
Try zooming in and out on iOS and then on Android. See how the marker on Android doesn't move with the Map but with iOS it does. I want the marker to stay its ground :)
Reproducible sample code
import React, { Component } from 'react';
import { View, Image, Platform } from 'react-native';
import MapView, { Marker } from 'react-native-maps';

import carImage from '../assets/car.png';

export default function App() {
  return (
    <MapView
      style={{
        flex: 1,
        width: '100%',
        height: '100%',
      }}
      loadingEnabled={true}
      showsUserLocation={true}
      region={{
        latitude: 45.45665,
        longitude: -73.840248,
        latitudeDelta: 0.4,
        longitudeDelta: 0.4,
      }}>
      <Marker
        identifier={'mk1'}
        coordinate={{
          latitude: 45.45665,
          longitude: -73.840248,
          latitudeDelta: 0.4,
          longitudeDelta: 0.4,
        }}>
        <Image
          ref={(ref) => {
            this.carImageRef = ref;
          }}
          source={carImage}
          style={{ width: 24 }}
          resizeMode="contain"
          resizeMethod="resize"
        />
      </Marker>
    </MapView>
  );
}

Steps to reproduce

https://snack.expo.dev/@umrashrf89/testmapmarker?platform=ios
https://snack.expo.dev/@umrashrf89/testmapmarker?platform=android

Expected result
Marker should stay its grounds
Actual result
On iOS Marker stays its grounds so should on Android
React Native Maps Version
1.14.0
What platforms are you seeing the problem on?
Android
React Native Version
0.74.5
What version of Expo are you using?
SDK 48
Device(s)
Samsung Galaxy S9+
Additional information
No response

@salah-ghanim would you know? :)

I fixed it by adding height along with the width. I was under the impression that if I am setting only the width, then it should be calculating height accordingly but that wasn't the case.


Use shouldVisitTemplateInstantiation to see if wil::single_threaded_property's overloaded()'s auto return type can be deduced

wil's method signature requires using getter and setter templates anyways. Closing. Can revisit.


Graceful skip of unpublished packages

Hello,
I believe full stop of update if meet unpublished packages is a bit too strongly. I suggest provide warning instead and leave it unchanged.
Greetings,
$ bump
[INFO] Checking django-redis-cache
[ERROR] No published version found for django-redis-cache

It is supposed to do that but didn't due to a bug. Try out 0.1.11
Also I didn't get that error when I was testing, so likely you don't have access to https://pypi.python.org/pypi/django-redis-cache/json (that's where bump gets its version info).  You can run with --debug to get details on any failure.


Create a Dockerfile

This pull request introduces a Dockerfile, which inherits from Centos:7 image and has GnuPG installed with install_gpg_all.sh script.
GnuPG is configured with disabled support for LDAP, Readline, TLS access to keyservers and TOFU. I can reconfigure Dockerfile if needed, it's only a matter of installing four additional packages. Pinentry is configured to use ncurses only.
By default, all components are in their latest versions. Optionally, user may chose 2.2 or 2.1 suite version (as defined in install_gpg_all.sh script) instead. Unfortunately, installing from Git is not supported due to outdated version of Automake in CentOS package repository (minimum 1.14 is required whereas only 1.13 is available).
This pull request includes usage example as well. Finally, Dockerfile is tested in Travis CI.

Well, it doesn't exactly solve my problem of installing GnuPG within Docker, because I want to run something "inside" of my Dockerfile. Dockerfiles cannot be built on top of each other -- a Dockerfile cannot be run inside another Dockerfile.
Can't we just move the contents of this Dockerfile into a script that can be run within a Dockerfile?

@ronaldtse I guess I can write a dedicated prerequisites installer script which will provide required packages similarly to what gpg_install_all.sh previously did. Since it will be a separate program, it does not need to be much portable, and it is okay if it will only work in CentOS. That said, I still does not see much value in a script which will do nothing but yum install.

Actually @dewyatt's Automake package could be very useful as it solves biggest headaches.

I noticed this too, I have a ribose-autoamke116 SCL package that I made locally for this that I've been meaning to publish.

Originally posted by @dewyatt in https://github.com/riboseinc/gpg-build-scripts/pull/24#issuecomment-439865266

Actually @dewyatt's Automake package could be very useful as it solves biggest headaches.

I'll work on getting that published now.

@skalee The automake116 package is now available in the ribose rpm repo if you want to try it (see the package README for usage).


执行npm install 安装依赖有很多告警

执行npm install
安装依赖有很多告警
Steps to reproduce（问题复现步骤）
$ npm install
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to 'tasksfile'. Install using 'npm install tasksfile' instead.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli . Install using @pawelgalazka/cli instead
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli-args. Install using @pawelgalazka/cli-args instead
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()

您的项目是否需要更新依赖的版本号？

下一个大版本更新这些依赖。

D:\vue-element-admin-master>node -v
v8.12.0
D:\vue-element-admin-master>npm install
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to 'tasksfile'. Install using 'npm install tasksfile' instead.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli . Install using @pawelgalazka/cli instead
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli-args. Install using @pawelgalazka/cli-args instead
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()
npm ERR! Error while executing:
npm ERR! C:\Program Files (x86)\Git\cmd\git.EXE ls-remote -h -t https://github.com/nhn/raphael.git
npm ERR!
npm ERR! fatal: unable to access 'https://github.com/nhn/raphael.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol versionnpm ERR!
npm ERR! exited with error code: 128
急急急  请问你们都能启动项目么？

问题同上，安装依赖的时候，ERR
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to 'tasksfile'. Install using 'npm install tasksfile' instead.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli . Install using @pawelgalazka/cli instead
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli-args. Install using @pawelgalazka/cli-args instead
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm ERR! Unexpected end of JSON input while parsing near '...orn":"^5.5.3","acorn-'
npm ERR! A complete log of this run can be found in:

npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to 'tasksfile'. Install using 'npm install tasksfile' instead.
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli . Install using @pawelgalazka/cli instead
npm WARN deprecated<EMAIL_ADDRESS>This project has been renamed to @pawelgalazka/cli-args. Install using @pawelgalazka/cli-args instead
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()

<EMAIL_ADDRESS>install D:\coding_projects\vue.js_project\vue-element-admin\node_modules\yorkie
node bin/install.js

自己的win10和公司的win10就有问题。公司的mac没有这个问题。

部分warning暂时解决不了，要等vue-cli@4发布。

同问,目前19.10.16, npm install还是出现'tasksfile'.怎么解决 @PanJiaChen

@github-linannan https://github.com/PanJiaChen/vue-element-admin/pull/2642 该分支已修改。

@github-linannan #2642 该分支已修改。

我应该是重新下载按流程重新操作一遍吧 但是还是显示这个问题

我应该是重新下载按流程重新操作一遍吧 但是还是显示这个问题 @PanJiaChen


Ability to set download directory and disable download or open popup using Firefox

Helium really does a great job simplifying selenium interface and I like using it. However, I couln't manage to set a profile for Firefox in order to change download directory and disable download popup. I think these were essential features for me while using selenium. Are you planning to add this kind of settings to start_firefox and start_chrome just like headless=True option?

Thank you for the kind words. I'm happy to hear you like Helium.
Regarding your question: Helium lets you supply ChromeOptions to start_chrome since the last release. Maybe something similar could be added for Firefox?
Either way, I won't have time to implement this. But I will be happy to merge a PR that does it.

I implemented this feature. See PR #22 .
Usage
from selenium.webdriver import FirefoxOptions

options = FirefoxOptions()
options.set_preference("browser.download.useDownloadDir", True)
options.set_preference("browser.download.folderList", 2)
options.set_preference("browser.download.dir", "path/to/download/directory")
options.set_preference("browser.helperApps.neverAsk.saveToDisk", "text/csv")  # specify content-type
start_firefox("connpass.com/login", options=options)

ref: https://stackoverflow.com/a/36309735

Thank you again @ftnext. I've released this on PyPI as version 3.0.3.


Skip Option on Game Shelves not working

It appears that changing the value in the Skip option within the Game Shelves configuration does not actually skip anything, true at least with my current set-up. I cannot find anything obviously unusual that should be causing this and I know it worked correctly before.

Fixed in v2.10.1


Update cwltool version when released

Feature Request
Desired behaviour
Update to and test with a version newer than cwltool-1.0.20161108... in order to get https://github.com/common-workflow-language/cwltool/pull/222 (used by pcawg workflows in multiple user environments) and https://github.com/common-workflow-language/cwltool/pull/223 (used potentially for Precision FDA work)
See also #475

Confirmed on staging.dockstore.org


Calculates of dropdown position lead to scrollbar flickering

Hi,
we're using custom scrollable container and ui-select inside. It looks like calculateDropdownPos leads to flickering the scrollbar if position set to 'auto' and long select is placed at the bottom of form.
I did some quick search and change function a bit: except just dropdown[0].style.opacity = 0; ... dropdown[0].style.opacity = 1; I added dropdown[0].style.position = 'fixed'; ... dropdown[0].style.position = 'absolute'; to move dropdown out of page flow temporary.
It solves the problem. Unfortunately I can't make PR due to some reasons, but I think this is not very big change.

@lexey111 Can you use the issue template provided and provide plunkr and version numbers?
For reference: There was some attempt to fix something similar in #1557, #1123 & https://github.com/angular-ui/ui-select/pull/1557#issuecomment-210851842 maybe it would be useful for your PR.

http://plnkr.co/edit/FMUk3ZzrnDqpNJ3A9AUz here is a demo of a flicker.
The problem especially visible when we don't know direction +modal window or footer.

Fix for situation when item goes out of viewport appears flicker before changing dropdown positioning. Here is fixing PR: and plunk of a fix: http://plnkr.co/edit/QxycwbMMYUpNoTLiubEg

We are seeing this same issue. Looking forward to a fix.


Where are the configured services stored?

Expected Behavior
Look into ~/.config (Linux)  and easily find a file with the config of the configured services/accounts.
Current Behavior
Seeing a huge bunch of files, also caches - can't find the config.
Context
I wanted to add the Franz service configuration to my personal (secret) dotfiles.
Your Environment

Franz Version used: 5.0.0-beta.15
Operating System and version: Antergos Linux release 18.1 (ISO-Rolling) / GNOME

Your service configuration of Franz 5 is stored in the cloud.

Also passwords etc...?
Looks like I was fooled by...

How do you handle my personal messages & chats?
Franz does not read anything you type, send or receive. That's between you and your messenger service. His only interest is to successfully deliver your messages. No nosing – all hail postal secrecy!

and

Franz does not store your password nor does it directly access your messaging service's account!

Since there's also

If you explicitly opt in to synchronize your session data (session data usually does not contain any passwords) with your other computers, we will encrypt your credentials, using high security industry standards, and store them as long as necessary on our servers. The encryption of your data will happen on your computer. We will never have access to plain text credentials.

under https://meetfranz.com/privacy/
I am I right that there's no more opt-out for this "feature" starting from Franz 5?

@adlk If read the thread https://github.com/meetfranz/franz/issues/71#issuecomment-342815507 - actually I'd have expected that someone who closes this links me to such an important discussion.
I can understand that there needs to be some business around Franz and it's more than fair that you get something (money) back from your work.
But the way how the communication is handled is really poor and made me also look for alternatives, if you're interested you can read about the issues (statements from Franz) in this thread.


Fix review feedback from previous checkin.

@abarth doesn't like Futures that explicitly point out they're type-unsafe. :-P
TBR @abarth

Lgtm


Language.simplify regex compilation and memoization

Currently, regexes in the Language.simplify method are not compiled, and are recompiled
every time the re.sub method is called. As a result, the parsing takes a big performance hit, especially in the case where many languages have to be evaluated, for example when parsing dates from a data set with mixed languages or unparseable strings.
This pull request adds compilation and memoization of the regexes to the Language.simplify method, which improves the performance of the tests by a factor 5.
Performance of tests before:
$ make test
(...)
Ran 1628 tests in 68.507s

Performance of tests after:
$ make test
(...)
Ran 1628 tests in 14.957s

A note on the 3.6 build failure: the failed tests are unrelated to this pull request. The error message on out-of-range dates in the datetime module was changed in Python 3.6.1, causing the tests to fail.

Codecov Report

Merging #315 into master will decrease coverage by 15.57%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master     #315       +/-   ##
===========================================
- Coverage   94.42%   78.84%   -15.58%
===========================================
  Files          34       34
  Lines        2960     4000     +1040
===========================================
+ Hits         2795     3154      +359
- Misses        165      846      +681

Impacted Files
Coverage Δ

dateparser/languages/language.py
97.6% <100%> (+0.13%)
:arrow_up:

dateparser/parser.py
47.57% <0%> (-43.98%)
:arrow_down:

dateparser/languages/loader.py
50.71% <0%> (-35.65%)
:arrow_down:

dateparser/calendars/hijri.py
94.73% <0%> (-5.27%)
: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 2726c47...ea745b1. Read the comment docs.


"Taxes should be increased on the rich to provide for the poor." assumes income taxation

I believe in wealth taxation, so I don't want to increase taxation (as a percentage anyway) but I also believe that money should be removed in larger amounts from the rich for the poor. The question should be rephrased to something like "More money should be taken from the rich to provide for the poor". Unless the writer means that the amount paid should be increased, rather than the percentage, in which case in needs more clarification such as "The percentage of tax paid should be increased on the rich to provide for the poor" coupled with an additional question: "The total amount of tax paid should be increased on the rich to provide for the poor".

Don't those mean more or less the same thing?

You mean income and wealth taxation?

"The percentage of tax paid should be increased on the rich to provide for the poor" and "The total amount of tax paid should be increased on the rich to provide for the poor" mean the same thing if the income of the rich doesn't change. Changing the quantity of money taxed also changes the percentage of money taxed.

sigh, that's true I guess we'll just have to find a better way of phrasing it. How about just straight up asking if people should be taxed based on income?


Dev: Change autoLaunch default behavior

- Summary
Disable auto launch of browser on netlify dev by default. Requires autoLaunch = true in config to enable. I'm introducing this change because in my experience, the feature is more annoying than it is useful in most cases.
Ref: https://github.com/netlify/cli/issues/615
Ref: https://github.com/netlify/cli/issues/608#issuecomment-573114582

- Test plan
Run netlify dev in any project

- Description for the changelog
Change the autoLaunch parameter logic, so that, it requires autoLaunch to be truthy to open the browser automatically.

- A picture of a cute animal (not mandatory but encouraged)
🐰

@RaeesBhatti we should probably have some product agreement before changing current behaviors. The point was made in #608 that CRA also does this and some consider it a positive for DX. This also is a breaking change for folks who expect it. Since we have the autoLaunch config for turning this off, let's leave as is for now.

Going to close this so it's status is clear, @RaeesBhatti please comment if you want to discuss further.


Large inline equations can overlap with other lines

Description
The square root is rendered through the vector. See HTI Dictaat Wiskunde 3.pdf.
Reproduction URL
~~https://typst.app/project/pxKIAuoZZl7hgc5cpu4nnH~~ (not shared)
https://typst.app/project/rrfl7-zYW_qh1tI8FeYwXE (read-only shared link)
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

What is the state of this isssue ? It's actually a major bug because it limits a lot doing package that user will use with math block a lot.
Is the value of bottom-edge and top-edge suppose to be the fix like mention in #1626 ?
Because those parameters doesn't fix at all the problem that I have mention in #3368.

#1626 fixed a different issues. Fixing this properly would require some smart heuristic in the paragraph layout. Note that you can work around this by using block equations instead of inline equations.

Okk thank you ! There is a fix !

Fixing this properly would require some smart heuristic in the paragraph layout.

Can you elaberate more about this? I currently don't quite understand why this happens. Which code is related?

@Enter-tainer It would be easy to just always expand lines to fit the equation. But that's also undesirable because it leads to uneven line spacing in many very common cases. Hence, we would need the paragraph layout to only expand the leading if truly necessary.

I wonder if there is any example about this. I cannot understand "It would be easy ... But that's also undesirable" well maybe because I cannot think of when will it become ugly. Is there a place I can tweak the code and see what is looks like if I want typst "always expand lines to fit the equation"?

I wonder if LaTeX does such "smart heuristic" when layouting inline equations. It seems that it always expand line height whenever it doesn't fit.
I also wonder if it is easy to fix(or implement) "always expand lines to fit the equation". It looks like typst currently tries to expand the line but for some reason(maybe there is already some heuristics?) it fails to correctly do it.

@Enter-tainer The following example demonstrates the case I'm talking about:

If the bounding boxes would be expanded fully, Typst's paragraph layout would add leading in between them and space the lines apart a lot. This case occurs quite frequently and the results would look really bad. For this reason, Typst has the naive workaround of just always pushing the bounding box of inline math somewhat inwards. A cleaner solution would be to ensure that nothing overlaps while keeping the lines spaced normally somehow.
As you can see, LaTeX also doesn't space the lines apart:

I'm not sure how it works in LaTeX, but it would only partly apply to Typst anyway because their line spacing model is very different. It's based on baselineskip rather than leading in between line bounding boxes.

@laurmaedje which files are relevant? Can you give me a list so I can learn how typst handles this at this moment.(And we can discuss how to improve it) I've discussed offline with @peng1999 and @Myriad-Dreamin about this.

I'm not sure how it works in LaTeX, but it would only partly apply to Typst anyway because their line spacing model is very different. It's based on baselineskip rather than leading in between line bounding boxes.

What do you think of this method: we calculate the baseline skip by adding the leading, along with the main text's ascender and descender. We then adhere to this baseline skip unless formulas or other elements cause the bounding box to collide with the previous line's descender.
This is basically switching from the original line spacing model (the Word model) to the LaTeX model. Hopefully at most of the time they are compatible.

Typst has the naive workaround of just always pushing the bounding box of inline math somewhat inwards

Relevant code is:
https://github.com/typst/typst/blob/a24052cb80e8a86695ac73e00281d5df0b9317c9/crates/typst/src/math/equation.rs#L236-L242

I'm trying to replicate the LaTeX behavior in a very rough way. And it looks good

Remove hacks for inline math bbox
When actually layouting lines, calculate prev.desc + curr.asc and see if they exceed the "default baseline skip"(in this case, it is default asc + default desc + default leading). If so, we set leading to 1pt.

diff --git a/crates/typst/src/layout/flow.rs b/crates/typst/src/layout/flow.rs
index 6f3b8f16..72d225de 100644
--- a/crates/typst/src/layout/flow.rs
+++ b/crates/typst/src/layout/flow.rs
@@ -279,8 +279,14 @@ impl<'a> FlowLayouter<'a> {
             }
         }

-        for (i, frame) in lines.into_iter().enumerate() {
+        for (i, frame) in lines.clone().into_iter().enumerate() {
             if i > 0 {
+                let leading =
+                    if (lines[i - 1].descent().abs() + frame.ascent()).to_pt() > 12.0 {
+                        Abs::pt(1.0)
+                    } else {
+                        leading
+                    };
                 self.layout_item(engine, FlowItem::Absolute(leading, true))?;
             }

diff --git a/crates/typst/src/math/equation.rs b/crates/typst/src/math/equation.rs
index 947f01f2..a78fd747 100644
--- a/crates/typst/src/math/equation.rs
+++ b/crates/typst/src/math/equation.rs
@@ -233,13 +233,12 @@ impl Packed<EquationElem> {
             let MathParItem::Frame(frame) = item else { continue };

             let font_size = scaled_font_size(&ctx, styles);
-            let slack = ParElem::leading_in(styles) * 0.7;
             let top_edge = TextElem::top_edge_in(styles).resolve(font_size, &font, None);
             let bottom_edge =
                 -TextElem::bottom_edge_in(styles).resolve(font_size, &font, None);

-            let ascent = top_edge.max(frame.ascent() - slack);
-            let descent = bottom_edge.max(frame.descent() - slack);
+            let ascent = top_edge.max(frame.ascent());
+            let descent = bottom_edge.max(frame.descent());
             frame.translate(Point::with_y(ascent - frame.baseline()));
             frame.size_mut().y = ascent + descent;
         }

@Enter-tainer The Image you have given is an image of the output given by Typist after your fix ? Or is it the one from Latex ?
I think the next step of this issue is to compare the behavior of :

Latex
Typst before your fix
Typist after your fix

First it has to be done visually on "edge cases". Then we have to check that other tests are fine with that change.

My pr #4236 has been abandoned for whatever reason i cannot remember.


ERR wrong number of arguments for HMSET

I keep randomly receive 	" ERR wrong number of arguments for HMSET" exception. But I have wrap all the hmset calls with try catch:
 logger.debug('redis hmset ', cacheKey);
                try {
                    cache.hmset(cacheKey, count);
                    logger.debug('redis hmset succesfully');
                } catch (e) {
                    logger.error(e + 'cacheKey is ' + cacheKey + ' count is ', count);
                }

but I still get uncaught exception as below:
stack		[15]
0	:	Error: ERR wrong number of arguments for HMSET
1	:	    at ReplyParser.<anonymous> (home/node_modules/redis/index.js:317:31)
2	:	    at ReplyParser.emit (events.js:95:17)
3	:	    at ReplyParser.send_error (/home/node_modules/redis/lib/parser/javascript.js:296:10)
4	:	    at ReplyParser.execute (/home/node_modules/redis/lib/parser/javascript.js:181:22)
5	:	    at RedisClient.on_data (/home/node_modules/redis/index.js:547:27)
6	:	    at Socket.<anonymous> (/home/node_modules/redis/index.js:102:14)
7	:	    at Socket.emit (events.js:95:17)
8	:	    at Socket.<anonymous> (_stream_readable.js:764:14)
9	:	    at Socket.emit (events.js:92:17)
10	:	    at emitReadable_ (_stream_readable.js:426:10)
11	:	    at emitReadable (_stream_readable.js:422:5)
12	:	    at readableAddChunk (_stream_readable.js:165:9)
13	:	    at Socket.Readable.push (_stream_readable.js:127:10)
14	:	    at TCP.onread (net.js:528:21)
level	:	error
message	:	uncaughtException: ERR wrong number of arguments for HMSET

Any idea?

the try/catch construct does not work on asynchronous calls like this. This error is a protocol error from your HMSET use being incorrect, but what happens in your code snippet is

the first logger.debug call
the try block begins
the outgoing HMSET call to redis is made
the logger.debug call is made
the try block finishes with no exception
the catch block is skipped because there was no exception
the javascript execution context completes and waits for an event
... ~miliseconds later
the network reply from Redis with the error returns, and is found to be an error by the parser
the parser sends the error to the client which then throws it

By the time the error is thrown in 9, the catch block is long since done. You cannot catch errors like this in node with asynchronous events.
The correct syntax for HMSET is HMSET key field value -- you're missing the field key.

I am using this function:
client.hmset(hash, obj, [callback])
so the count is actually a json object. In order to figure out which field is actually missing, can I do something like:
client.hmset(cacheKey, count,function(err, reply){
logger.error(err,cacheKey,count)
});
Thanks,

That will likely help -- most likely your object is an empty object {} e.g.
> c.hmset("foobar", {}, console.log)
true
> [Error: ERR wrong number of arguments for 'hmset' command]


Remove WPT test case with poor interop.

(This pull request depends on #22.  Please merge that first.)
This change is also being proposed upstream at:
https://chromium-review.googlesource.com/c/chromium/src/+/3003690

Part of #7.

Has conflict, probably has to be rebased