text:
React Native Vector Icons causing build error

I created a React Native Project and Worked on it, It works perfect on debug build. But when I run ./gradlew assembleRelease inside android directory, It leads me to an error.

Task :app:copyReactNativeVectorIconFonts FAILED

FAILURE: Build failed with an exception.

What went wrong:
A problem was found with the configuration of task ':app:copyReactNativeVectorIconFonts' (type 'Copy').

Gradle detected a problem with the following location: '/Projects/AppName/android/app/build/intermediates/ReactNativeVectorIcons/fonts'.
Reason: Task ':app:lintVitalAnalyzeRelease' uses this output of task ':app:copyReactNativeVectorIconFonts' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':app:copyReactNativeVectorIconFonts' as an input of ':app:lintVitalAnalyzeRelease'.
Declare an explicit dependency on ':app:copyReactNativeVectorIconFonts' from ':app:lintVitalAnalyzeRelease' using Task#dependsOn.
Declare an explicit dependency on ':app:copyReactNativeVectorIconFonts' from ':app:lintVitalAnalyzeRelease' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/8.0.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 4s
214 actionable tasks: 7 executed, 207 up-to-date
Here's package.json
{
"name": "App Name",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"lint": "eslint .",
"start": "react-native start",
"test": "jest"
},
"dependencies": {
"@react-native-async-storage/async-storage": "^1.19.0",
"@react-navigation/bottom-tabs": "^6.5.8",
"@react-navigation/native": "^6.1.7",
"@react-navigation/native-stack": "^6.9.13",
"@reduxjs/toolkit": "^1.9.5",
"axios": "^1.4.0",
"react": "18.2.0",
"react-native": "0.72.1",
"react-native-linear-gradient": "^2.7.3",
"react-native-safe-area-context": "^4.6.3",
"react-native-screens": "^3.22.0",
"react-native-splash-screen": "^3.3.0",
"react-native-vector-icons": "^9.2.0",
"react-redux": "^8.1.1"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/preset-env": "^7.20.0",
"@babel/runtime": "^7.20.0",
"@react-native/eslint-config": "^0.72.2",
"@react-native/metro-config": "^0.72.7",
"@tsconfig/react-native": "^3.0.0",
"@types/metro-config": "^0.76.3",
"@types/react": "^18.0.24",
"@types/react-test-renderer": "^18.0.0",
"babel-jest": "^29.2.1",
"eslint": "^8.19.0",
"jest": "^29.2.1",
"metro-react-native-babel-preset": "0.76.5",
"prettier": "^2.4.1",
"react-native-dotenv": "^3.4.9",
"react-test-renderer": "18.2.0",
"typescript": "4.8.4"
},
"engines": {
"node": ">=16"
}
}

for me to after upgrading RN to 0.72.1 i get a build error

Hi! See https://github.com/oblador/react-native-vector-icons/issues/1508 thread

Same issue please patch it
This worked for me :) please patch the package

Hi! See #1508 thread

Thanks a lot!! it worked for me too :)

I also have the same problem, is there a solution?

I also have the same problem, is there a solution?

try this https://github.com/oblador/react-native-vector-icons/issues/1508#issuecomment-1604115239 it worked for me.

Fixed in 10.0.0

我也有同样的问题，有解决办法吗？

试试这个#1508（评论）它对我有用。

Thank you, I have successfully fixed it by this method, and the author has updated to 10.0.0, which also made the fix

authors: billel-boudchicha caixingyue nehaTrank oblador pavelustenko sehrish30

repo: oblador/react-native-vector-icons


text:
Cannot build for Android due to gradle config issue

Description
Newly installed dependency, cannot build with debug variant
Error Message
run npx react-native run-android
> Configure project :react-native-vector-icons
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html

FAILURE: Build failed with an exception.

* Where:
Script '/Users/PhilLui/projects/TestApp/node_modules/react-native-vector-image/strip_svgs.gradle' line: 10

* What went wrong:
Cannot get property 'name' on null object

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Expectation
Can build normally with debug variant
Further information
I think the issue is due to the following row in this repo gradle file
def bundleTasks = tasks.findAll { task -> task.name.startsWith("bundle") && task.name.endsWith("JsAndAssets") && !task.name.contains("Debug") && task.enabled }

As all debug tasks has been removed in this filter closure, this repo is not possible to build with debug variant.
What are the concerns of excluding debug tasks?
I don't know if this can help or not, my tasks list attached
task ':app:androidDependencies'
task ':app:assemble'
task ':app:assembleAndroidTest'
task ':app:assembleDebug'
task ':app:assembleDebugAndroidTest'
task ':app:assembleDebugUnitTest'
task ':app:assembleRelease'
task ':app:assembleReleaseUnitTest'
task ':app:build'
task ':app:buildDebugPreBundle'
task ':app:buildDependents'
task ':app:buildEnvironment'
task ':app:buildNeeded'
task ':app:buildReleasePreBundle'
task ':app:bundle'
task ':app:bundleDebug'
task ':app:bundleDebugAndroidTestClasses'
task ':app:bundleDebugAndroidTestResources'
task ':app:bundleDebugClasses'
task ':app:bundleDebugResources'
task ':app:bundleDebugUnitTestClasses'
task ':app:bundleRelease'
task ':app:bundleReleaseClasses'
task ':app:bundleReleaseResources'
task ':app:bundleReleaseUnitTestClasses'
task ':app:check'
task ':app:checkDebugAndroidTestDuplicateClasses'
task ':app:checkDebugDuplicateClasses'
task ':app:checkDebugManifest'
task ':app:checkReleaseDuplicateClasses'
task ':app:checkReleaseManifest'
task ':app:clean'
task ':app:cleanBuildCache'
task ':app:collectDebugDependencies'
task ':app:collectReleaseDependencies'
task ':app:compileDebugAidl'
task ':app:compileDebugAndroidTestAidl'
task ':app:compileDebugAndroidTestJavaWithJavac'
task ':app:compileDebugAndroidTestKotlin'
task ':app:compileDebugAndroidTestRenderscript'
task ':app:compileDebugAndroidTestShaders'
task ':app:compileDebugAndroidTestSources'
task ':app:compileDebugJavaWithJavac'
task ':app:compileDebugKotlin'
task ':app:compileDebugRenderscript'
task ':app:compileDebugShaders'
task ':app:compileDebugSources'
task ':app:compileDebugUnitTestJavaWithJavac'
task ':app:compileDebugUnitTestKotlin'
task ':app:compileDebugUnitTestSources'
task ':app:compileLint'
task ':app:compileReleaseAidl'
task ':app:compileReleaseJavaWithJavac'
task ':app:compileReleaseKotlin'
task ':app:compileReleaseRenderscript'
task ':app:compileReleaseShaders'
task ':app:compileReleaseSources'
task ':app:compileReleaseUnitTestJavaWithJavac'
task ':app:compileReleaseUnitTestKotlin'
task ':app:compileReleaseUnitTestSources'
task ':app:components'
task ':app:configureDebugDependencies'
task ':app:configureReleaseDependencies'
task ':app:connectedAndroidTest'
task ':app:connectedCheck'
task ':app:connectedDebugAndroidTest'
task ':app:consumeConfigAttr'
task ':app:copyDownloadableDepsToLibs'
task ':app:crashlyticsUploadDistributionDebug'
task ':app:crashlyticsUploadDistributionRelease'
task ':app:createDebugCompatibleScreenManifests'
task ':app:createMockableJar'
task ':app:createReleaseCompatibleScreenManifests'
task ':app:dependencies'
task ':app:dependencyInsight'
task ':app:dependentComponents'
task ':app:deviceAndroidTest'
task ':app:deviceCheck'
task ':app:extractApksForDebug'
task ':app:extractApksForRelease'
task ':app:extractProguardFiles'
task ':app:fabricGenerateResourcesDebug'
task ':app:fabricGenerateResourcesRelease'
task ':app:generateDebugAndroidTestAssets'
task ':app:generateDebugAndroidTestBuildConfig'
task ':app:generateDebugAndroidTestResValues'
task ':app:generateDebugAndroidTestResources'
task ':app:generateDebugAndroidTestSources'
task ':app:generateDebugAssets'
task ':app:generateDebugBuildConfig'
task ':app:generateDebugFeatureMetadata'
task ':app:generateDebugFeatureTransitiveDeps'
task ':app:generateDebugResValues'
task ':app:generateDebugResources'
task ':app:generateDebugSources'
task ':app:generateDebugUnitTestAssets'
task ':app:generateDebugUnitTestResources'
task ':app:generateDebugUnitTestSources'
task ':app:generatePackageList'
task ':app:generateReleaseAssets'
task ':app:generateReleaseBuildConfig'
task ':app:generateReleaseFeatureMetadata'
task ':app:generateReleaseFeatureTransitiveDeps'
task ':app:generateReleaseResValues'
task ':app:generateReleaseResources'
task ':app:generateReleaseSources'
task ':app:generateReleaseUnitTestAssets'
task ':app:generateReleaseUnitTestResources'
task ':app:generateReleaseUnitTestSources'
task ':app:help'
task ':app:installDebug'
task ':app:installDebugAndroidTest'
task ':app:installRelease'
task ':app:javaPreCompileDebug'
task ':app:javaPreCompileDebugAndroidTest'
task ':app:javaPreCompileDebugUnitTest'
task ':app:javaPreCompileRelease'
task ':app:javaPreCompileReleaseUnitTest'
task ':app:kaptDebugAndroidTestKotlin'
task ':app:kaptDebugKotlin'
task ':app:kaptDebugUnitTestKotlin'
task ':app:kaptGenerateStubsDebugAndroidTestKotlin'
task ':app:kaptGenerateStubsDebugKotlin'
task ':app:kaptGenerateStubsDebugUnitTestKotlin'
task ':app:kaptGenerateStubsReleaseKotlin'
task ':app:kaptGenerateStubsReleaseUnitTestKotlin'
task ':app:kaptReleaseKotlin'
task ':app:kaptReleaseUnitTestKotlin'
task ':app:lint'
task ':app:lintDebug'
task ':app:lintFix'
task ':app:lintRelease'
task ':app:lintVitalRelease'
task ':app:mainApkListPersistenceDebug'
task ':app:mainApkListPersistenceDebugAndroidTest'
task ':app:mainApkListPersistenceRelease'
task ':app:makeApkFromBundleForDebug'
task ':app:makeApkFromBundleForRelease'
task ':app:mergeDebugAndroidTestAssets'
task ':app:mergeDebugAndroidTestJniLibFolders'
task ':app:mergeDebugAndroidTestResources'
task ':app:mergeDebugAndroidTestShaders'
task ':app:mergeDebugAssets'
task ':app:mergeDebugJniLibFolders'
task ':app:mergeDebugResources'
task ':app:mergeDebugShaders'
task ':app:mergeReleaseAssets'
task ':app:mergeReleaseJniLibFolders'
task ':app:mergeReleaseResources'
task ':app:mergeReleaseShaders'
task ':app:model'
task ':app:packageDebug'
task ':app:packageDebugAndroidTest'
task ':app:packageDebugBundle'
task ':app:packageDebugUniversalApk'
task ':app:packageRelease'
task ':app:packageReleaseBundle'
task ':app:packageReleaseUniversalApk'
task ':app:preBuild'
task ':app:preDebugAndroidTestBuild'
task ':app:preDebugBuild'
task ':app:preDebugUnitTestBuild'
task ':app:preReleaseBuild'
task ':app:preReleaseUnitTestBuild'
task ':app:prepareKotlinBuildScriptModel'
task ':app:prepareLintJar'
task ':app:prepareLintJarForPublish'
task ':app:processDebugAndroidTestJavaRes'
task ':app:processDebugAndroidTestManifest'
task ':app:processDebugAndroidTestResources'
task ':app:processDebugGoogleServices'
task ':app:processDebugJavaRes'
task ':app:processDebugManifest'
task ':app:processDebugResources'
task ':app:processDebugUnitTestJavaRes'
task ':app:processReleaseGoogleServices'
task ':app:processReleaseJavaRes'
task ':app:processReleaseManifest'
task ':app:processReleaseResources'
task ':app:processReleaseUnitTestJavaRes'
task ':app:projects'
task ':app:properties'
task ':app:reportBuildArtifactsDebug'
task ':app:reportBuildArtifactsRelease'
task ':app:reportSourceSetTransformAndroidTest'
task ':app:reportSourceSetTransformAndroidTestDebug'
task ':app:reportSourceSetTransformDebug'
task ':app:reportSourceSetTransformMain'
task ':app:reportSourceSetTransformRelease'
task ':app:reportSourceSetTransformTest'
task ':app:reportSourceSetTransformTestDebug'
task ':app:reportSourceSetTransformTestRelease'
task ':app:resolveConfigAttr'
task ':app:signDebugBundle'
task ':app:signReleaseBundle'
task ':app:signingConfigWriterDebug'
task ':app:signingConfigWriterDebugAndroidTest'
task ':app:signingConfigWriterRelease'
task ':app:signingReport'
task ':app:sourceSets'
task ':app:tasks'
task ':app:test'
task ':app:testDebugUnitTest'
task ':app:testReleaseUnitTest'
task ':app:transformClassesWithDexBuilderForDebug'
task ':app:transformClassesWithDexBuilderForDebugAndroidTest'
task ':app:transformClassesWithDexBuilderForRelease'
task ':app:transformDexArchiveWithDexMergerForDebug'
task ':app:transformDexArchiveWithDexMergerForDebugAndroidTest'
task ':app:transformDexArchiveWithDexMergerForRelease'
task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'
task ':app:transformDexArchiveWithExternalLibsDexMergerForDebugAndroidTest'
task ':app:transformDexArchiveWithExternalLibsDexMergerForRelease'
task ':app:transformNativeLibsWithMergeJniLibsForDebug'
task ':app:transformNativeLibsWithMergeJniLibsForDebugAndroidTest'
task ':app:transformNativeLibsWithMergeJniLibsForRelease'
task ':app:transformResourcesWithMergeJavaResForDebug'
task ':app:transformResourcesWithMergeJavaResForDebugAndroidTest'
task ':app:transformResourcesWithMergeJavaResForDebugUnitTest'
task ':app:transformResourcesWithMergeJavaResForRelease'
task ':app:transformResourcesWithMergeJavaResForReleaseUnitTest'
task ':app:uninstallAll'
task ':app:uninstallDebug'
task ':app:uninstallDebugAndroidTest'
task ':app:uninstallRelease'
task ':app:validateSigningDebug'
task ':app:validateSigningDebugAndroidTest'
task ':app:validateSigningRelease'
task ':app:writeDebugApplicationId'
task ':app:writeDebugModuleMetadata'
task ':app:writeReleaseApplicationId'
task ':app:writeReleaseModuleMetadata'

sorry this issue is not valid, it cannot be built due to i commented apply from: "../../node_modules/react-native/react.gradle" in my gradle file to prevent duplicate resource issue, after i uncommented this row, the project can be built now

source: gharchive/issue

repo: oblador/react-native-vector-image

license: MIT

license_type: permissive

license_source: github-api


text:
Getting angulaj digest cycle errors with groupSort: true

Hi, I'm getting the following with grid 1.3.2 & angular 1.4.7
TypeError: Cannot read property '$$nextSibling' of null
    at Scope.$digest (angular.js:15854)
    at Scope.$apply (angular.js:16097)
    at angular.js:17864
    at completeOutstandingRequest (angular.js:5507)
    at angular.js:5784

The error is not constant. Sometimes it works. Sometimes toggleSort should be called twice. I can make a repo with the example I'm using if required.
p.s. https://github.com/bronzovik/grid-sort-example

This should be fixed with 1.4.1.
Thanks.

Still having the same issue with 1.4.2

Update to 1.4.3.
The grid flow and the $digest from angular were not always in sync and this caused a conflict.
The grid is now respectful of a digest being in progress and will render after.
However, one part that is seen here is that in your project you are missing this part of the css so it makes the rows show their "{{code}}" briefly before it completes. Adding this css which should be default for the datagrid will make those rows not show until they are done. However, you can change the fade out of this css if you don't want them to fade.
.datagrid-row > * {
   -webkit-transition: opacity 0.5s ease-out;
   -moz-transition: opacity 0.5s ease-out;
   -ms-transition: opacity 0.5s ease-out;
   -o-transition: opacity 0.5s ease-out;
   transition: opacity 0.5s ease-out;
}

.uncompiled > * {
   visibility: hidden;
   opacity: 0;
}

.compiled > * {
   opacity: 1;
}

.datagrid-chunk {
   opacity: 0;
   -webkit-transition: opacity 0.5s ease-out;
   -moz-transition: opacity 0.5s ease-out;
   -ms-transition: opacity 0.5s ease-out;
   -o-transition: opacity 0.5s ease-out;
   transition: opacity 0.5s ease-out;
}

.datagrid-chunk-ready {
   opacity: 1;
}

Hi Wes,
it looks like 1.4.3 has fixed it. Thanks a lot and thank you for the heads up with the CSS!
Still gotta check variable row height feature.

Awesome! Your git example for me to work with was SO helpful because I had seen the error before, but was not sure how to reproduce it, Thanks for your help!

authors: bronzovik wesjones

repo: obogo/ux-angularjs-datagrid

license: mit

license_source: bigquery


text:
aging versus ageing

Related to #2691
Any MP term that contains the word aging in it should have a synonym that replaces aging with ageing.
slow aging
mortality/aging
premature aging
early reproductive senescence (accelerated reproductive aging)

Done!


text:
Improve ingestion limit rules

Right now, we have a limit of 250 pages when scraping a page. Let's separate scraping from ingestion and have two different limits. You should be able to scrape a much higher number of pages so that you can select which pages to ingest.
Also, make these fields configurable as env vars instead of hard coded.

This is configurable through an Env variable, but yes we should be able to raise the limit to a higher number due to the various improvement we have made. I will do some scaling test and raise the number accordingly.

authors: StrongMonkey cjellick

repo: obot-platform/obot


text:
Bug: app.setting is not included in Type Definitions

app.setting is not included in the latest Type Definitions available on npm despite widespread use and awareness.

Private APIs are not documented because they are private.
There are loads of methods and fields that exists at runtime but aren't in the API because we have not committed to supporting them through the API.
If you decide to use a private API you can do so by adding it in your own local .d.ts file in your plugin repo.

Understood, thanks for the information. Just voicing an opinion here that an eventual public API opening settings would be useful to many plugins 🙂.
For those that land here in the future, consider using / contributing to these unofficial but thorough types.

authors: Cutaiar joethei

repo: obsidianmd/obsidian-api


text:
Support for Huggingface Serverless Inference API

I think it would be helpful to have support for the Huggingface Serverless Inference API given that is supports a range of models and includes a limited number of free calls.
I'm a novice here, but from my understanding of the documentation, the API endpoints vary by model, so the URL may need special configuration  for each one. Right now I've added a new provider for each model that I want to use and I've also had trouble with the interpreter updating the contents within my template.

Excited for this! Any idea when 0.10.6 will drop?

authors: andrew-m-j datavistics

repo: obsidianmd/obsidian-clipper


text:
Replace HTML interlinks

Requires #33. Comparison when #33 is merged: 6b88a4859651a803abe887164ecf44be416bf259...6c61e0b91762f54c7d1b2a9b8e1584175419a952 Rebased.
This makes the importer convert valid  links linking other HTML files into wikilinks or Markdown links linking the imported Markdown files depending on Files & Links > Use [[Wikilinks]]. Example:

a.html -> a.md
b.html -> b.md:

abc

becomes
[[a]]

(It's not [[a|abc]] because apparently ReferenceCache.displayText is always the empty string if the link is a Markdown link even if the Markdown link has a display like [abc](./a.html). As the intermediate form uses Markdown links, this causes [[a]] instead of [[a|abc]] to be outputted. Maybe this needs to be fixed on your side? A temporary fix would be to parse the displayText out from ReferenceCache.original, but I am not exactly wanting to parse Markdown links myself yet...)

(It's not [[a|abc]] because apparently ReferenceCache.displayText is always the empty string

When I tested this on the files in test/html I was seeing that the link became [[HTML import/embeds|embeds.html]] as expected.

Presumably, it is fixed.

source: gharchive/pull-request

repo: obsidianmd/obsidian-importer


text:
Cannot link an object file

It's probably something I don't get right, but I can't compile a very simple program in which I try to link together a piece of OCaml and a piece of C code. The code is here:
https://gist.github.com/pdonadeo/bbc4a1ea176110ab93dd/
The program compiles but ctypes seems to ignore the linked symbols... or the command line for ocamlopt is wrong.
$ ./foo_ml_linked_a
Fatal error: exception Dl.DL_error("./foo_ml_linked_a: undefined symbol: my_foo_function")

@pdonadeo, did the suggestions above solve your problem?

@yallop sorry for the delay, I just came back from holidays. Yes, your suggestion works, I'm closing this "issue" which is more a documentation issue than a problem with ctypes itself.

authors: pdonadeo yallop

repo: ocamllabs/ocaml-ctypes


text:
Bound integrals entirely broken

I cannot do integrals with bounds in Obsidian Math Plus.
\int_{a}^{b} changes to \in t_{a}^{b}.

Unfortunately I have the same issue and I didn't find a workaround.

Thanks for your patience, this should be fixed in the latest release!

authors: arrow501 duckfromdiscord ocapraro

repo: ocapraro/obsidian-math-plus


text:
[Bug]: The partition plan execution cycle has cached values

ODC version
ODC 4.2.3
OB version

What happened?

Create a partition plan, and the data displayed in the execution cycle is the cycle of the previous task
What did you expect to happen?
Clear execution cycle data
How can we reproduce it (as minimally and precisely as possible)?
After issuing a partition planning task, issue another one again.
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 1928d46a5a4a27e1e71111a51d67191949b4edb7
------
咏和
Tue Dec 19 19:06:12 2023 +0800

pass

authors: HSunboy sl01388797 tonghan-gsh

repo: oceanbase/odc


text:
Add unit tests and improve code coverage.

Fixes #214 #273  .
Changes proposed in this PR:

add unit tests for the unused/untested functions;
code coverage above 90% for each file;
resolve generate_hash bug in the web3 unit tests.

I just tested to see that it solves #273 in this branch. And, it does. Good job:)
I briefly reviewed the other code. Looks good, but I defer to Calina and David for a more thorough review.

I chatted with Calina. Result:
It's to change the private keys in the READMEs.
However do be sure that you can run through the quickstart.

closes #256 as well

authors: alexcos20 mariacarmina trentmc


text:
Fix asyncio version by downgrading to 21.1 again for CI warnings.

Echoes #531. Closes #790.
Apparently pytest-asyncio did not fix their issue with subsequent versions. Downgrading back to 21.1 and adding instructions in setup.py to be mindful of the changelog before approving dependabot upgrades.

I see, I reviewed the outline of #531 and #790. Since you've been iterating on this and seem to be narrowing down the issue, let's approve the downgrade to 21.1 and see if it stabilizes tests/warnings.

Reviewed the 0.21.1 changelog and the previously reported issues. Hopefully this stabilizes the tests/skips/warnings/isuses. Approving.

It does. The test run for this branch is clean from those warnings, and the pytest-asyncio maintainers have specified these problems in the changelog, suggesting for 21.1 to be used until they fix those issues.

authors: calina-c idiom-bytes

repo: oceanprotocol/pdr-backend


text:
Warnings of deprecated libraries upon Docker build vue_apps

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

Unfortunately this is not a result of this repo.  These warnings are coming from npm install itself.  Please see the issue below:
https://github.com/11ty/eleventy/issues/1178
I'm certain they will correct this quickly.  However, you can specify an earlier version of npm in the dockerfile if you wish.
Thank you for your support and bringing this to my attention.

These warnings unfortunately do not originate with my code.  They appear to come from the npm install of vue/cli.  Hopefully it is remedied soon.

Upgraded project to use Vue 3.  I am no longer seeing any issues.

authors: dorian-yeager hickst

repo: oci-labs/rapid-stack


text:
ability to provide VPC region info

Signed-off-by: Prajyot Parab Prajyot.Parab1@ibm.com

@mkumatag @Karthik-K-N
Let me know if we are good to merge these changes post your validation checks.

Changes lgtm. I feel the caption should be changed as this pr is providing a way to pass classic region info and not fixing the auth.
Also an issue link with the explanation why we are doing the change will help others.

as far as I know there is nothing like region for the classic infra

as far as I know there is nothing like region for the classic infra

@Prajyot-Parab Right we are dealing with VPC region and not classic. Please update the information and variable names.

@yussufsh @cs-zhang : Can you please help with review?

@Prajyot-Parab : Please let me know if we are good to close / anything is blocked?

@Prajyot-Parab : Please let me know if we are good to close / anything is blocked?

Updated branch to be inline with upstream repo - Good to merge now

/approve

/backport release-4.8

/cherry-pick release-4.8

/cherry-pick release-4.7

/cherry-pick release-4.6

authors: Prajyot-Parab mkumatag ssinha20 yussufsh


text:
无法自动播放视频

环境描述
系统: win11
浏览器：brave
OCS版本：4.8.8
页面链接: https://example.com/xxxxxxxxxxxxxxx
BUG 描述
无法自动播放视频
推测是学习通增强了调用play()函数的检测
12:39 [错误]:播放视频时发生未知错误：NotAllowedError: play() can only be initiated by a user gesture.
...
重现方法

进入任意一个视频

预期行为
应该自动开始播放视频。
屏幕截图

如果可以请附带截图。
解决方案
如果可以，请提供您的解决思路

尝试更新到 4.8.30

authors: Nippaku-Zanmu enncy

repo: ocsjs/ocsjs


text:
Process releases in the server

What feature would you like to have?
The current version is processing the selected range of releases in the browser. We should move this process to the server with Next.js API Routes.
What problem will this feature solve?
By moving this logic to the server, we would benefit from:

sending less code to the browser (lighter bundle)
processing the releases in a more powerful environment (faster processing)
caching responses (saving processing time)

Do you want to help make the feature?
Yes
Is there anything else we need to know?

All the existing E2E should work in the same way
We need to cache the responses based on repo slug, from version and to version
If "latest" option is found in either from or to version, we can't cache the response

caching responses (saving processing time)

That sounds like a big improvement! Fetching the changelogs takes a long time right now...
I'm wondering does the cache update when people "refresh" the query?
For example:

current cache contains renovatebot/renovate changelogs from 1.0.0 to 31.0.0
User runs query from 1.0.0 to latest
Program fetches results and updates cache
Cache code understands that latest points to 31.56.0???
Cache now contains renovatebot/renovate changelogs from 1.0.0 to 31.56.0???
If user runs query from 1.0.0 to 31.56.0 fetch directly from cache, no waiting???

I still need to check how much granular control I have for caching requests at Vercel for Serverless Functions.
From what I've seen so far, I think that your example would work in the following way:

That's a request with a repo slug, from version and to version, so it's cached with no problems indeed.
Since one of the versions is latest, I want to use stale-while-revalidate strategy there
That's correct.
No: cache doesn't understand that latest points to 31.56.0 per se. We have two options here:
a. Use the stale-while-revalidate strategy. In this case, we would return the previously processed data cached for 1.0.0 --> latest, which could be 1.0.0 --> 31.55.4 for example. This strategy would recalculate the cache in the background so it returns processed releases for 1.0.0 --> 31.56.0 the next time that 1.0.0 --> latest is requested
b. In the browser we convert latest to the actual last version at that point in time, so we request 1.0.0 --> 31.56.0 to the server, which will cache the response properly
No matter what strategy we pick on the previous step, both 1.0.0 --> 31.0.0 and 1.0.0 --> 31.56.0 would be cached at this point
Next user requesting (could be the same user, or another one) 1.0.0 --> 31.56.0 would get it directly from cache, so would be an almost instant response.

repo: octoclairvoyant/octoclairvoyant-webapp


text:
Make schematic connections of "8relay8led" board

Make schematic connections of "8relay8led" board in EasyEDA.

https://oshwlab.com/octopos-em/i2c8relay8ledd

authors: ecehzrc krmlp

repo: octoposprime/op-pcb


text:
🛑 OSRA App (app.osperyhra.org.ar) is down

In e0d0cc2, OSRA App (app.osperyhra.org.ar) (https://app.osperyhra.org.ar/api/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OSRA App (app.osperyhra.org.ar) is back up in f8895c9.

repo: octubre-softlab/octubre-upptime


text:
🛑 Mi Web App (miweb.umet.edu.ar) is down

In ca21cc0, Mi Web App (miweb.umet.edu.ar) (https://miweb.umet.edu.ar/api/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mi Web App (miweb.umet.edu.ar) is back up in 4f0185b.


text:
minor typo error

Hi,
Just a minor typo in OddBird's Accourement modules are individual Sass toolkits (t missing in accoutrement !)
Cheers

Thanks! Closed by 23e848d

repo: oddbird/accoutrement-color


text:
Set positions via CSS custom properties instead of directly on target elements.

Description
Before, we were calculating positions and then setting them directly via targetElement.style.setProperty(...). This isn't ideal for two reasons:

It ignores the cascade. What if the anchor() call from the stylesheet is overridden by a different set of styles?
It doesn't allow any math outside of the anchor function, e.g. top: calc(anchor(--my-anchor 100%) - 50px);.

With the changes in this PR, we are now replacing uses of anchor() with a unique generated CSS custom property directly in the stylesheet, and then after we calculate the position value we simply assign that pixel value to the relevant CSS custom property. This way we can allow CSS itself to handle the cascade, and any relevant math.
Steps to test/reproduce
Please explain how to best reproduce the issue and/or test the changes locally (including the pages/URLs/views/states to review).
View the demo and confirm that the examples still work (including the new "used in math function" example).

 Allow CSS to apply positioning by updating stylesheets instead of applying styles directly.

 transformCSS() - anchor() function in math functions

@mirisuzanne @jerivas Since Sana and Olu are out, would the two of you be willing to review this PR sometime? Not urgent, of course.

I remember some discussion about shorter UUIDs in the custom props? That's not urgent, but it would look nicer.

Yep! That's coming in the next PR... #52

repo: oddbird/css-anchor-positioning


text:
Purify Event Dispatching and Handling

In an effort to make state management teste, I've realized that directly modifying global state may be somewhat problematic in the long term.
This issue is to "purify" each function into pure logic, then apply a vector of modification events returned from each event handling function.
This makes Odilia much easier to test and extend.
Related to: https://github.com/odilia-app/odilia/issues/117, https://github.com/odilia-app/odilia/issues/108, and depends on https://github.com/odilia-app/atspi/pull/82 being merged.

Here is an example of how this should work:
Instead of a function like update_string_insert(start_pos, update_length, updated_text) -> impl Fn(&mut CacheItem) + '_ this would become: update_string_insert(text_caret_moved_event) -> OdiliaEvent.
enum OdiliaEvent {
    ...
    Cache(OdiliaCacheEvent),
}
struct OdiliaCacheEvent {
    InsertAt(usize, String),
    RemoveFrom(usize, usize),
}
...

This creates a well-defined, easily testable surface area for the screen reader. We can know instantly if we've covered a certain case in our testing, how extensively it's been tested, and we don't have to check state directly (for example: checking each field in the state structure, checking that each item is changed as expected, and that no other changes were made.
Yes, we will also need to test functions which apply these effects to the state structure, but, importantly, we have already tested that the functions return the right results separately from testing that the effects are applied correctly. This separates the responsibility of the various tests, and makes it so we don't have to do the work of spinning up atspi and SSIP connections, etc. for a test of the internal functionality of a function.
Hopefully this makes sense. It'll be a ton of work, but I am absolutely convinced of this for the long-term.

repo: odilia-app/odilia


text:
Default server URL updated

fixes: https://github.com/odk-x/tool-suite-X/issues/244

runtests

authors: pawanharariya wbrunette

repo: odk-x/androidlibrary


text:
hero pages

Improve the hero pages (currently we only display rankings and benchmarks).
Things we might want to add:

Best against/worst against heroes
Recent (pro?) matches with this hero
graphs for winrate against time

I can try to do this, but where take data for it?

The endpoints need to be implemented on odota/core.  You can check the table schema and test SQL queries using the Explorer.
I can also help with this, but I'll probably be implementing the team endpoints first.

Proposed API endpoints to add:
/heroes/{heroId}/matchups: returns games played and wins against all other heroes (for pro matches)
/heroes/{heroId}/matches: return most recent games played with this hero
/heroes/{heroId}/durations: return games played and wins for each bucket of 5 minutes

see this PR for an example:
https://github.com/odota/core/pull/1539
I might do this tomorrow if I have some time

Endpoints implemented in:
https://github.com/odota/core/pull/1542

authors: Luchanso howardchung

repo: odota/ui


text:
🛑 urbamonde.org is down

In c133b42, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 909 ms

Resolved: urbamonde.org is back up in 9a65b22.

repo: odqo/upptime


text:
🛑 oec-static.sgu.ru is down

In 5493171, oec-static.sgu.ru (https://oec-static.sgu.ru/favicon.ico) was down:

HTTP code: 0
Response time: 0 ms

Resolved: oec-static.sgu.ru is back up in 45dc838.

repo: oec-ssu/status


text:
Fix unit test and add unit test for ImJoy web app

Currently, the unit test based on Karma does not work. We will need unit test for longer term development.

This commit (https://github.com/oeway/ImJoy/commit/343ef7dfa16c67c210c0b194cb56a60bb94bbe98) allows unit test with karma.

repo: oeway/ImJoy


text:
Change the colour of comments in the pseudocode

To visually distinguish them from the pseudocode, and make it look just a little bit more like an editor.

Fixed in https://github.com/ofZach/dayForNightSFPC/commit/da4572dfabffa1a42dbfd9e6fef5e1af6e5d2c98

repo: ofZach/dayForNightSFPC


text:
ofdsign报错：no such algorithm: 1.2.156.10197.1.401.2 for provider BC

使用EC或SM2，exeSign 写入签名正常；exeValidate 验签报错 no such algorithm: 1.2.156.10197.1.401.2 for provider BC。很是奇怪，请问如何解决

OFDRW的几个验签容器仅供仓考，若需要个性化的验签需求，请实现 SignedDataValidateContainer接口。

repo: ofdrw/ofdrw


text:
[Bug Fix] Ember.String.htmlSafe throws exception

Resolves #198
ping @blimmer

perfect - thank you!

authors: blimmer offirgolan

repo: offirgolan/ember-cp-validations


text:
Recalculate scrollbar when viewport dimensions change

When a dom element is removed or inserted, we dont recalculate the scrollable container. @taras this solution works but I believe can be improved.

@offirgolan which DOM element is removed or inserted?

@taras lets say you have a flexbox container with flex-direction: row. You initially have a single item in that container (i.e. the table) then some event gets triggered and a new item is added to the container. Now, the table's width has been reduced by 50% but the scrollable container does not trigger its recalculate method due to the fact that a resize event hasnt been triggered

oh, I see. I think the solution that I linked to ember-scrollable should do it. It adds a brief animation to the height of the element. When the height changes, the animations' callback is triggered which triggers an event similar to resize event.
That's likely the better solution to this problem.

Perfect. Lets prioritize that since I believe this is currently a blocker (especially in my current apps)

authors: offirgolan taras

repo: offirgolan/ember-light-table


text:
Firefox

I followed the instructions on the GitHub, however i have a binary not found error. I have Firefox installed in the default location.
here is the error massage
  File "C:\Users\User\Downloads\twitchtube - Copy (2)\main.py", line 80, in <module>
    make_video(**parameters)
  File "C:\Users\User\Downloads\twitchtube - Copy (2)\twitchtube\video.py", line 191, in make_video
    upload = Upload(profile_path, executable_path, sleep, headless, debug)
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\opplast\upload.py", line 34, in __init__
    self.driver = webdriver.Firefox(
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\firefox\webdriver.py", line 170, in __init__
    RemoteWebDriver.__init__(
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 157, in __init__
    self.start_session(capabilities, browser_profile)
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 252, in start_session
    response = self.execute(Command.NEW_SESSION, parameters)
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "C:\Users\User\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.SessionNotCreatedException: Message: Expected browser binary location, but unable to find binary in default location, no 'moz:firefoxOptions.binary' capability provided, and no binary flag set on the command line

Fixed in #99. You can specify Firefox path in config if it isn't detected automatically by geckodriver.

authors: Luphaestus OwOHamper

repo: offish/twitchtube


text:
能否导入sm18的文件

如题

看下这篇文章 https://zhuanlan.zhihu.com/p/555893660 的【（十一）与SuperMemo互动】

看下这篇文章 https://zhuanlan.zhihu.com/p/555893660 的【（十一）与SuperMemo互动】

感谢

repo: oflg/fishing


text:
EnumCorpus

感谢无私分享，我有一个小小的提议，
EnumCorpus在line数量特别大时非常的慢，是不是可以通过counter计行数的方式读取，这样也能保证每一行数据都会用来生成图片，下面的方式我试了一下还是蛮快的。
import random
from multiprocessing import Lock, Value
    random.shuffle(self.texts)
    self.index = Value('i', 0)
    self.total_line = len(self.texts)
    self.lock = Lock()

def get_text(self):
    with self.lock:
        if self.index.value >= self.total_line:
            self.index.value = 0
        else:
            self.index.value += 1
    return self.texts[self.index.value]

主要是因为 numpy 的 random.choice 很慢，已经修复了，见这个 commit

authors: Sanster kingwpf


text:
Closing socket connection

I think the readme is misleading, because the code below only unsubscribes but does not close the socket connection.
messagesSubscription.unsubscribe()
hence, how can I close the socket connection ?
(I use Angular)

This should close the connection, but it would depend exactly on how you are using the Observable (e.g. whether you are using share, publish etc.)
Could you paste more of your code sample?
The code looks fine to me but I may have missed something, there may be a bug. I can test it out when I have some more time.

Angular > Service
import { Injectable } from '@angular/core'
import { QueueingSubject } from 'queueing-subject'
import { Observable } from 'rxjs/Observable'
import websocketConnect, { Connection } from 'rxjs-websockets'
import { Config } from "../common/config";

@Injectable()
export class WebSocketService {

  private inputStream: QueueingSubject<any>
  public messages: Observable<any>

  public connect(path: string) {
    if (this.messages)
      return

    // Using share() causes a single websocket to be created when the first
    // observer subscribes. This socket is shared with subsequent observers
    // and closed when the observer count falls to zero.
    //this.messages =

    this.messages = websocketConnect(
      Config.getEnv("wsRoot") + path,
      this.inputStream = new QueueingSubject<any>()
    ).messages.share()
  }

  public send(message: any): void {
    // If the websocket is not connected then the QueueingSubject will ensure
    // that messages are queued and delivered when the websocket reconnects.
    // A regular Subject can be used to discard messages sent when the websocket
    // is disconnected.
    this.inputStream.next(message)
  }

  public disconnect(){
    //???
  }

}

Angular > Component
import { ActivatedRoute } from '@angular/router';
import { EventClientFetchAction } from "./../store/reducer/event-client.reducer";
import { AppState } from '../store/state/app-state';
import { Store } from '@ngrx/store';
import { Component, OnInit } from '@angular/core';
import { Observable } from "rxjs/Observable";
import { EventClient } from "../../shared/model/event-client";
import { WebSocketService } from "../../websocket/websocket.service";
import { Subscription } from "rxjs/Subscription";

@Component({
    templateUrl: 'connect-event.component.html'
})

export class ConnectEventComponent implements OnInit {

    private code: string;

    loading$: Observable<boolean>;
    eventClient$: Observable<EventClient>;
    reTry: boolean;

    private socketSubscription: Subscription
    private ponger: Subscription;

    constructor(
        private route: ActivatedRoute
        , private store: Store<AppState>
        , private webSocketService: WebSocketService
    ) {
        this.loading$ = store.select(state => state.eventClient.loading);
        this.eventClient$ = this.store.select(state => state.eventClient.item)

        this.store.select(state => state.eventClient).subscribe(eventClientContainer => {
            this.reTry = (eventClientContainer.httpResponseCode != 200 || !eventClientContainer.serverResponse.isOk()) ? true : false;
        })
    }

    ngOnInit() {
        this.route.params.subscribe(params => {
            this.code = params['code'];
            this.fetchEventClient();
        });
    }

    fetchEventClient() {
        this.store.dispatch(new EventClientFetchAction(this.code));
    }

    connect() {
        this.webSocketService.connect("ws/v1")
        this.socketSubscription = this.webSocketService.messages.subscribe((message: any) => {
            console.log('received message from server: ', message);
            console.log(message.action === 'ping');
            console.log(message.action);
        })

        this.ponger = this.webSocketService.messages.filter(msg => msg.action === 'ping').subscribe(
            (msg) => {
                console.log("I AM HERE TO PONG!");
                this.webSocketService.send({action: "pong"})
            }
        );
    }

    send() {
        // send message to server, if the socket is not connected it will be sent
        // as soon as the connection becomes available thanks to QueueingSubject
        this.webSocketService.send({ type: 'helloServer' })
    }

    disconnect() {
        this.socketSubscription.unsubscribe();

    }

}

When the number of subscribers to a share()d observable drops to 0 it should run the disposal routine which in the rxjs-websockets code closes the web socket connection. If not it's a bug, I'll have to verify myself.

OK, I could not observe that. Maybe that I should wait for a while?
What is the right pattern of closing the socket connection when the user clicks on a button on the webpage?
a) controller closes the socket connection through the websocket service's method
b) controller only unsubscribe and if no subscriber left, the connection is closed automatically
c) controller sends a new action to the server and the server closes the connection
(I think the library should support all options)

It does support all of these options, you would handle it via rxjs operators like publish(), share() etc.
It's important to have a good understanding of cold observables to understand how to use this library effectively, when you get that you'll see how to do (a-c).

I'd advise checking this out: https://blog.thoughtram.io/angular/2016/06/16/cold-vs-hot-observables.html
It's liked in the README. TBH you'll need that understanding to do anything slightly advanced with rxjs.

Hi, thanks for the resource, I've checked it, it was very useful.
I've found the mistake, thanks for your support. Actually I have two different subscriptions but I close only one of them. I fixed it like that:
    disconnect() {
        if (this.socketSubscription){
            this.socketSubscription.unsubscribe();
        }
        if(this.ponger){
            this.ponger.unsubscribe();
        }
    }

Cool, I'm writing some unit tests, hopefully those will lead to more understanding.

At least your mistake demonstrated how the share() operator works to you, it's pretty cool no? Rxjs is great!

I have to look into Rxjs more deeply :)

It looks like if I subscribe to the connectionStatus, even if I unsubscribe, the socket is not closed :)
do you think that can be true?

Oh, I put the share() and it worked. It seems like I didnt get the idea :))
    let con: Connection = websocketConnect(
      Config.getEnv("wsRoot") + path,
      this.inputStream = new QueueingSubject<any>()
    );

    this.messages = con.messages.share();
    this.status = con.connectionStatus.share();

There's no point sharing the connection status, it's a hot observable. Doing so is a minor performance hit for nothing.

OK, however without share, it does not close the socket connection even after unsubscription

That should be impossible, I suspect you've made a mistake elsewhere.

See here in the code:
https://github.com/ohjames/rxjs-websockets/blob/master/src/index.ts#L28
connection status is a BehaviorSubject, a hot observable.

yes u r right (again) thanks!

authors: mustafaekim ohjames

repo: ohjames/rxjs-websockets

license: ISC


text:
build: use external release notes builder

closes #520

How do you feel about making the value of the -stop-at flag a Makefile variable as you are doing with the version in #575?

How do you feel about making the value of the -stop-at flag a Makefile variable as you are doing with the version in #575?

Sure, that's a good idea.

authors: adamstruck buchanae

repo: ohsu-comp-bio/funnel


text:
iOS popover cancel button event

Hi @okadan
first of all great work!
I am using your package in a project where I read a NfcTag and later use the tag id to call some server logic. Overall I am using the BLoC-pattern and I am wondering if there is an option to catch the "on cancel"-event when you tap the button on the Nfc-Popover in iOS. I differentiate between two states IsReadyToReadNfc and ReadingNfc. Depending on the state I have a button and want to display either "Start Scanning" or "Scanning..."

Hi @eddiesTime
Currently, this plugin does not support handling "cancel / error" events.

Hi @eddiesTime
Currently, this plugin does not support catching "cancel / error" events.
But we can probably do this by handling didInvalidateWithError on iOS and specifying the callback when starting a session.
NfcManager.instance.startTagSession(
  didInvalidateWithErrorIOS: (e) {
    // handling error
  },
);

Hi @okadan
thank you for your fast response!
I can't wait to see what your next update will bring. In my opinion your plugin is the easiest to use and will be the best one at pub.dev yet with the addition of error handling.

@eddiesTime
Added a callback parameter for handling errors from the session. #10
And, published to pub.dev as v1.3.0.

Hi @okadan
Excuse me for my delayed response. Thank you for updating the package with the new enhancement.
I've tried it out today but unfortunately did not receive any result. Do you mind to take a look at my approach and give me some feedback?
Down below is my implementation of the startTagSession and my approach to test the onSessionError-Callback.
NfcManager.instance.startTagSession(
        onDiscovered: (NfcTag tag) async {
      // discover logic
    }, onSessionError: (NfcSessionError error) async {
      print('error');
      print(error.message);
     // error logic
    });

When I hit the "Cancel"-Button on iOS nothing happens. I don't receive any print statements in my debug console.
I've taken a loot in your adaptation of nfc_manager.dart. The callback should respond with a NfcSessionError with the NfcSessionErrorType userCanceled when I select the cancel button.

@eddiesTime
Sorry, this is a bug.
Fixed and published to pub.dev as v1.3.1.

Thank you.
I've tested it and it works as intended. Keep the good work up! :)
Closing the issue now.

authors: eddiesTime okadan


text:
ODE does not ingest a public Google Sheets

Problem description
This is a problem reported by one of the organizations conducting the pilot. They tried to ingest this Google Sheets and the ODE displays a message saying the URL is not valid or that the data is not publicly available.

I checked the file, and data is effectively online (see file here).
Can you please check what could be going on?

Hi @roll! I'm adding more context here. I asked ACIJ to share the Datos tenencia censo 2022 (1).xlsx. I tried to ingest it and got this error:

We discussed this issue during our stand-up meeting. The problem here is that the user is adding a public Google Sheets ending in html. This is the reason why the ODE is not ingesting the file. I'll add a clarification to the ODE user guide.

@roll can you add this to the ODE documentation?
Section:  Uploading data
Link: https://opendataeditor.okfn.org/documentation/uploading-data/
Please, add this to the Note box as the second bullet point
👉🏼 For Google Sheets, please make sure you are adding the public version of your file without the HTML term at the end. For example:
✅https://docs.google.com/spreadsheets/d/1dFVoF6f9VU5pjaGhyyvQaBN0n6ae-iLCtlvsO1N2jhA/edit?gid=0#gid=0
❌https://docs.google.com/spreadsheets/d/e/2PACX-1vQ8w9yb7D-iYEbImb0WD4Kh53_Yp7H1VOi1bIMcicphWbkrrH9PobXCJhXt9frqyQ/pubhtml

repo: okfn/opendataeditor


text:
Remove unnecessary markdownify calls

Is this a BUG REPORT or FEATURE REQUEST?:
Refactor Suggestion
Explanation:
We changed markdown configuration within exampleSite's config.toml file to add support for Hugo v0.60 and the new GoldMark markdown compiler but the solution is not really good. It's much better to remove any unnecessary markdownify calls which causes problems for rendering with the unsafe html errors.

Hi, this is what I have tested using syna/layouts/partials/fragments/footer.html
This is the code used right now (with a bit of DEBUG):

  {{- with .self.Content }}

DEBUG.self.Content
      {{- . | markdownify -}}

  {{- end }}
  DEBUG.self.Content
  {{- .self.Content -}}

With Goldmark gives:

DEBUG.self.Content

  DEBUG.self.Content

Syna Theme

Highly customizable open source theme for Hugo based static websites

With blackfriday gives what you expect:

DEBUG.self.Content

Syna Theme

Highly customizable open source theme for Hugo based static websites

  DEBUG.self.Content

Syna Theme

Highly customizable open source theme for Hugo based static websites

Using markdownify only gives one change, we lose the closing
, and it doesn't work with Goldmark by default

Now if we change self.Content to self.RawContent when we are using markdownify:

  {{- with .self.RawContent }}

DEBUG.self.RawContent
      {{- . | markdownify -}}

  {{- end }}
  DEBUG.self.Content
  {{- .self.Content -}}

With Goldmark gives:

DEBUG.self.RawContent

Syna Theme

Highly customizable open source theme for Hugo based static websites

  DEBUG.self.Content

Syna Theme

Highly customizable open source theme for Hugo based static websites

With blackfriday gives the same result

DEBUG.self.RawContent

Syna Theme

Highly customizable open source theme for Hugo based static websites

  DEBUG.self.Content

Syna Theme

Highly customizable open source theme for Hugo based static websites

So I think it is safe to assume that self.Content has already the markdown processed to html and that's why Goldmark fail with markdownify.
It seems like markdownify is redundant, no need to convert again the html code in self.Content, and not allowed by Goldmark by default. Also without markdownify you have the closing

I can't test this with an older version of Hugo (0.60.1 right now) to see if self.Content was always already rendered making markdownify redundant.
But I'm going to try  to get the full Public folder with the code as it is, then remove all | markdonify with sed to get a new Public and compare both. Using blackfriday and goldmark (with unsafe = true).

Awesome analysis and debugging. Seems like "markdownify" might be a left-over artifact from early versions, which isn't necessary anymore. Much appreciated. Looking forward to the PR resolving compatibility for 0.60.1 \o/

@Marzal Thanks again for your help.

authors: Marzal mpourismaiel stp-ip

repo: okkur/syna


text:
fix: search all configs regardless of staged files

This PR searches for all configurations inside the git repo, instead of only those matching the staged files. It's currently only used for the hasMultipleConfigs check, but in the future it will also be used to fix "parent directory" globs, which are currently not working.
Without this fix, hasMultipleConfigs would be false if you only staged files matching a single config, and thus the CWD would be wrong.

Need to add some more tests:
--------------------|---------|----------|---------|---------|-------------------
File                | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------------|---------|----------|---------|---------|-------------------
All files           |     100 |    99.68 |     100 |     100 |
 searchConfigs.js   |     100 |       80 |     100 |     100 | 26

What do you think about this, @okonet ?

Ping @okonet, do you think you'd have time for checking this out? I haven't really had time to take it further either, but merging this would fix the most clear issue we have currently in monorepo setups.

I hope you are well @okonet.
In the meantime, if someone from the community wants to open this exact same pull request, I am able to approve and release it. Unfortunately with the current repo settings, I'm not able to self-approve my own changes.

Thanks, @okonet! I'll try to migrate the config grouping to the new logic next.

repo: okonet/lint-staged


text:
docs: fix github workflow badges 🤖

This PR fixes github workflow badges after a breaking change on github platform. Everything is explained there : https://github.com/badges/shields/issues/8671
I took advantage of this PR to make the workflow status badges target only the main branch.
🤖 This PR is generated by this script.

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


text:
Ci/linter improvements

Continue the work on linters initiated by @faddat: https://github.com/okp4/okp4d/pull/175 & https://github.com/okp4/okp4d/pull/174. Thank you by the way! 🙏

Enforce gofumpt code formatting by adding the linter to the Lint workflow.
Add a target to the makefile to format go source code using gofmpt
Improve documentation (a bit)

@amimart i've added a target to the makefile to format the go source files using gofmpt. It's not essential (especially if the developers wire correctly their IDE) but it completes the supported features, as a general principle.

@amimart i've added a target to the makefile to format the go source files using gofmpt. It's not essential (especially if the developers wire correctly their IDE) but it completes the supported features, as a general principle.

Nice thanks!

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

authors: amimart bot-anik ccamel


text:
OKTA_CREDENTIALS_SUFFIX ignored when writing AWS configuration

The fix for #161 still unconditionally uses _source in the AWS configuration file.
It should honor the environment setting OKTA_CREDENTIALS_SUFFIX (or its default value if not set) instead of always using _source.

Good catch. My test "worked" only because I had the _source named credentials profile from before.
I like your fix. Can you open a PR with it?

#164

authors: AlainODea jimlawton

repo: oktadeveloper/okta-aws-cli-assume-role


text:
tabPress listener doesn't fire if screen is currently active

This would allow for a common pattern in iOS to focus a search bar when a tab is pressed if the screen is already active.

Will be fixed by #116 🚀

Should be fixed in 0.3.1

authors: gunnartorfis okwasniewski

repo: okwasniewski/react-native-bottom-tabs


text:
Release Issue Cannot Find File

https://travis-ci.com/ChristopherDavenport/unique/jobs/232709673#L325
On 1.3.1 my code in unique failed to deploy saying it could not find the bundle.

Ok, I believe its an issue with having a publishTo that didn't get removed from the build.

repo: olafurpg/sbt-ci-release


text:
optional axi signal record

Make it optional to combine the axi interface signals in a record. Avoiding to use a record will enable Vivado to detect the port as an axi interface, and simplifies connecting in block design GUI.

It seems that there are 3 things that need to be updated to simplify integration with Vivado block designer:

[ ] Avoid using record for the AXI interface signals
[ ] Avoid combining the register signals in records
[ ] Avoid using VHDL 2008 (This is particularly infuriating...)

repo: olagrottvik/uart


text:
What's the difference beween OnlineMatch and OfflineMatch?

It seems that the codes of OnlineMatch and OfflineMatch in HelloWorldApp are the same. Both two functions match trajectory samples by the following codes:
foreach (var sample in samples)
{
var vector = matcher.Execute(kstate.Vector(), kstate.Sample, sample);
kstate.Update(vector, sample);
}
Is there any differences between OnlineMatch function and OfflineMatch function?

Hello:
the original Barefoot project has an explanation:

Offline map matching: Most map matching applications rely on the matching of a sequence of position measurements recorded in the past (traces) for reconstruction of the object's path on the map. Offline map matching finds the best matching on the map and exploits availability of the full trace.
Online map matching: In many other applications, objects send position updates to some monitoring system periodically. An online map matching system matches each position update right away and, hence, keeps track of the objects' movements on the map in (near) real-time.

发现您的地址在昆明，我还是用中文沟通吧。我原来的意思是例子里的OnlineMatch函数和OfflineMatch函数执行的匹配过程好像差不多，都是先matcher.Execute，然后kstate.Update。这两个函数（OnlineMatch和OfflineMatch）有什么区别吗？后来仔细比对之后，发现OnlineMatch里还有个kstate.Estimate。

Online 的是喂一个经纬度就能估计出这个经纬度所处的路网图的边，类似于驾车使用的导航。
Offline 是一次给一堆经纬度，整体计算出途经的边。

authors: applefl oldrev

repo: oldrev/mapmatchingkit


text:
No vasa option in =monster

🐛 Bug Report
Currently with =monster , vasa does not have a option (vasa, vasa magus) like all the others to be able to look up boosts & times.

Found out this also applies to nex, and tempoross, not sure what others might be affected by it.

repo: oldschoolgg/oldschoolbot


text:
Unable to generate curve data

I am just testing audicurve on 'windows 7'. Apparently it doesn't find sox.exe, if i am right : 'Unable to generate curve data'.

sox.exe is in same folder?
Den 2015-07-23 17:43, skrev rcspam:

I am just testing audicurve on 'windows 7'. Apparently it doesn't find
sox.exe, if i am right : 'Unable to generate curve data'.
--
Reply to this email directly or view it on GitHub [1].

Links:
[1] https://github.com/olear/audiocurve/issues/9

yes installed with you setup

"unable to generate curve data"  happens when sox gives no output/data, maybe wrong params (input/output)?

just input a file in audiocurve plugin then generate curve so...

I've try on another host, all is ok !
Don't know why i doesn't works on the other one.
Surely the secret ghosts of the compinting !?

In Fact, sox for win32 doesn't support mp3 files. It is not compiled, i hope to have well understood, with liblame....

https://github.com/mxe/mxe/blob/master/src/sox.mk#L11
Should support mp3 (untested).

Just an info for users who want use AudioCurve.exe...

If you want sox read mp3 files, you have just to include libmad.dll and libmp3lame.dll in sox.exe directory

So, it is the same directory as Plugins !

authors: hafuz olear rcspam

repo: olear/audiocurve


text:
Add build.gradle for ppconsul

as well as other supporting gradle stuff.
This is a preliminary change that adds the foundation for ppconsul to be accessible as a third party library from fds-src. The OM team does not plan to begin utilizing this library right away, but forsee usage in the future. Additions that will include support for this in the iso etc will be done when we begin to use this.

@meena-m  why was it closed? :)

Hi @oliora, I forked your repo (perhaps I should be cloning instead), and these changes were intended to go against that fork, and don't really belong in master; I fat-fingered the base when creating the PR :) Hence the immediate close.

Ah, ok :) If you mind you're welcome to merge your changes back to the master.

authors: meena-m oliora

repo: oliora/ppconsul


text:
Why is it slow

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v7 (for Elasticsearch 7.x)
Please describe the expected behavior
I just used two ways to search the same index data. The first way is elastic V7 search, and the second way is HTTP request search. The premise is that there are no search conditions in both ways. The first way is 3S, and the second way is 200ms
Please describe the actual behavior
Any steps to reproduce the behavior?

I have no idea. It's very much an educated guess. It could as well be just a cache being warmed up after the first request. Notice that this is just the repository of a Go driver for Elasticsearch, not the Elasticsearch repository. But if you can isolate the effect and are able to construct a reproducible test case, I'm eager to learn what I can do about it.

@olivere I have a similar issue. Two exactly the same queries - one is ran from curl and one is ran from the golang client.
Curl query
~ time curl -X GET "http://localhost:9200/case/_search" -H 'Content-Type: application/json' -d '{"query":{"constant_score":{"filter":{"bool":{"filter":[{"bool":{}},{"geo_bounding_box":{"location":{"bottom_right":[14.0625,54.1624339680678],"top_left":[11.25,55.77657301866769]}}}]}}}},"size":10000,"sort":[{"_id":{"order":"asc"}}]}' &> /dev/null
curl -X GET "http://localhost:9200/case/_search" -H  -d  &> /dev/null  0.01s user 0.04s system 2% cpu 1.745 total

The curl query takes 1.745 seconds
golang query
		start := time.Now()
		search := s.ES.Search().Index(s.CasesIndex).
			Query(
				elastic.NewConstantScoreQuery(
					elastic.NewBoolQuery().Filter(
						params.ToQuery(),
						tile.GetBBoxGeoQuery(),
					)),
			).
			Sort("_id", true).
			Size(esMaxFetchDocs)

		searchResult, err := search.Do(ctx)
		elapsed := time.Since(start)
		fmt.Printf("Search took %s\n", elapsed)

Search took 2.269884083s
this is 0.5 seconds of difference, and this is before the json is deserialized. This seems like a lot.
The client is created like so:
	s.ES, err = elastic.NewClient(
		elastic.SetURL(strings.Split(s.addresses, ",")...),
		elastic.SetSniff(false),
		elastic.SetRetrier(newRetrier()),
	)

I'm testing on local, there is no network latency issue and I'm running the queries a lot of times so it's not related to any caching.
What could potentially cause this? This is just a simple http call, it shouldn't have any overhead really?

I figured out my problem. It was related to the JSON decoding at the query level. I had some documents with very long fields and the JSON decoding was taking .5 seconds itself. So I've configured
FetchSourceContext(elastic.NewFetchSourceContext(true).Include("field1", "field2")). to my query so that only the needed fields are returned

authors: nacholibre olivere wanghousheng

repo: olivere/elastic


text:
defined blade_complement_type trait

Change-Id: I8e2e44f97602581cedd5a3583f65ae77b414e87c

Codecov Report
Attention: Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.

Project coverage is 69.11%. Comparing base (79ff378) to head (dbde16f).

Files with missing lines
Patch %
Lines

rigid_geometric_algebra/blade_complement_type.hpp
0.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
+ Coverage   67.72%   69.11%   +1.38%
==========================================
  Files          21       23       +2
  Lines         251      272      +21
  Branches        5        7       +2
==========================================
+ Hits          170      188      +18
- Misses         81       84       +3

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

authors: codecov-commenter oliverlee

repo: oliverlee/rigid-geometric-algebra


text:
Dutch translation work

Fix a small typo, missing 'c' in project in en.json;
Add Dutch translation files.

Thanks for that!

authors: hugolgst sexybiggetje


text:
Automatically switch parent Swipeable view

If we are at the end of the flow of a swipeable view (beginning or end), we automatically switch the parent swipeable view instead. Implemented as an option.

@zetura Thanks. Should only we have an issue when switching back?
I have found a better approach. I'm still trying to address #26 too. I will submit a PR once it's done.

authors: oliviertassinari zetura

repo: oliviertassinari/react-swipeable-views


text:
Thanks you very much!

Thanks you very much!. I spent a week implementing nested middlewares, but still couldn't cover all their use cases. You saved everyone a many of nerve cells!
p.s It is very strange that Prisma core team  did not implement this in 3 years.

I'm glad you are finding it useful! Thanks for letting me know, this made my day! 🙌
Please let me know if you have any feedback or find any issues 👍

authors: olivierwilkinson xferqr


text:
Error: Server disconnected without sending a response. Error: [WinError 10061] No connection could be made because the target machine actively refused it

when running this code

i get the error in the title. what did i do wrong or what is the issue here?

Hi, how did you solve this? any guidance pls?

Hi, how did you solve this? any guidance pls?

i think i forgot to start the ollama server but i dont really know anymore

repo: ollama/ollama-python


text:
Error: Head "http://127.0.0.1:11434/": EOF (Windows 10)

Thank you for the OLLAMA.
So far, I've been using ollama in WSL2, and when the windows version came out, I experienced it right away. But..
Microsoft Windows [Version 10.0.19045.4046]
C:\Users\Name>ollama pull nous-hermes:13b-llama2-q6_K
Error: Head "http://127.0.0.1:11434/": EOF
C:\Users\Name>ollama list
Error: Head "http://127.0.0.1:11434/": EOF
ollama help provides a normal help
from app.log:
...
time=2024-02-17T13:20:54.375+03:00 level=WARN source=server.go:109 msg="server crash 16 - exit code 1 - respawning"
time=2024-02-17T13:20:54.875+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started"
time=2024-02-17T13:21:10.884+03:00 level=WARN source=server.go:109 msg="server crash 17 - exit code 1 - respawning"
time=2024-02-17T13:21:11.385+03:00 level=ERROR source=server.go:112 msg="failed to restart server exec: already started"
from server.log:
...
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
Error: listen tcp 127.0.0.1:11434: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2.
To see if this is it, run this command in cmd:
netsh interface portproxy show all
If so, you need to remove it with this command:
netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1
or
netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0

I had this problem and I discovered that it was because I had added a portproxy to be able to access the ollama API from Windows that was running on WSL2.
To see if this is it, run this command in cmd:
netsh interface portproxy show all
If so, you need to remove it with this command:
netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=127.0.0.1
or
netsh interface portproxy delete v4tov4 listenport=11434 listenaddress=0.0.0.0

Thanks, it solved my problem.

Same error, no proxy

Hello I solved the same issue see here

authors: EdwHA Gonrizard szymonk92 tzzed

repo: ollama/ollama


text:
Silly buffer sizes may cause a2_Close() to block forever

Not entirely sure why this happens, or if it's even in A2 itself. At least it happens with the SDL driver on Linux. (PA -> JACK -> ALSA.)
It doesn't happen with the JACK driver, but that's probably just because it ignores the buffer setting and goes with the JACK buffer size instead.

It seems like this (no audio output + block forever in driver close) can also happen with perfectly reasonable parameters with the SDL driver. Is this an SDL issue and/or are we not verifying the resulting configuration properly?
Maybe we should verify that audio devices actually work before initializing the A2 engine at all, and/or set timeouts whenever we're depending on an engine round trip?

Well, one thing SDL can do, that's trivial to detect, is setting up a device with 0 samples of buffering. That will obviously be dead, but everything still looks fine - until one tries to close and get stuck waiting for an API<->engine roundtrip that will never happen.
I'm not sure what we can do in A2, other than refusing to accept 0 bytes of buffering from SDL. If SDL gives us a dead device under other circumstances, all we can do is implement a timeout, and hope no Bad Things™ happen if we just kill everything from the API context. Not cool!

Actually, we're not even waiting for a roundtrip anywhere. We just rip the callback out, and then close everything in the API context. The indefinite wait was in pthread_join() inside SDL.

license: Zlib


text:
Problema no executeRequest

Olá,
estou tentando fazer a integração e autenticação usando sua API.
Ele esta pegando o json corretamente,
Gera o link corretamente, e redireciona para eu autenticar, e consigo autenticar no site da OLX.
Então ele retorna na url corretamente, só que ao ele pegar o código para enviar via CURL e receber o token, ele retorna false.
No método executeRequest, o $response retorna
bool(false)
e o $result retorna
array(4) { ["header"]=> bool(false) ["body"]=> bool(false) ["http_code"]=> int(0) ["last_url"]=> string(35) "https://auth.olx.com.br/oauth/token" }

Olá Samuel,
Você possui conta premium e as chaves de acesso a API?

authors: samuelmiquelino vitormattos

repo: olxbr/olx-api-client


text:
VipsImage thread safety

Hi! Thank you very much for providing this very pleasant to use binding crate.
It would appear this warning is directed at me and my use case:

Be aware that the VipsImage object is not thread safe in the moment. I'll investigate what is happening and provide a solution for it in the future.

Is there an update to your thoughts on this, or your general advice on working around it?

No. I didn't figure out what is wrong.
What is your use case?

@augustocdias I am working with a type of proxy service - I basically fan out a bunch of HTTP requests in parallel process them with vips to resize and crop as they come in. Then once they are all done, I join them in to one contiguous image with arrayjoin. As such, I need to hold on to basically Vec<VipsImage> as they come in, which requires Send.
The only "hack" I could think of was serializing them to [u8] so I could move it around, and recreate a VipsImage when they are all finally ready. Obviously not very efficient..
I did try unsafe impl Send for VipsImage {} just for kicks, and saw that it indeed breaks things...
Is there maybe another approach that will let me do this in parallel? I am totally new to using vips, so I appreciate the adivce :)
Let me know if there's other details I can provide.

The problem is I'm not sure if the problem is with rust or libvips. I had a similar setup as you.
I didn't have any segfaults or anything, but the vips operations started to fail complaining the internal pointer from vips was invalid.
I didn't have time to investigate and I couldn't find any doc stating how am I supposed to handle ffi pointers in these situations.
If you find anything please share because I'm intrigued to know the reason for that.

Gotcha. IIRC the segfault happened with a particularly large image. Others, yes, would say something along those lines of the pointer being invalid, something from vips own logger.

The problem is I'm not sure if the problem is with rust or libvips.

Right. I get the impression from https://libvips.github.io/libvips/API/current/using-threads.html - which claims:

On startup, you need to call VIPS_INIT() single-threaded. After that, you can freely create images in any thread and read them in any other thread.

as I'm sure you've already read. So I'm inclined to take their word on it, and its something funny we're doing in Rust..
I have a few things to try today, among them possibly trying to reproduce an equivalent small program in C, or maybe seeing what I can find with a debugger.
If I find anything I will report back - thanks for your time!

repo: olxgroup-oss/libvips-rust-bindings


text:
(fix): Add swift-docc-plugin dependency

Add swift-docc-plugin dependency to fix the auto generated d…ocs issue (#9)

Codecov Report
Base: 96.63% // Head: 97.71% // Increases project coverage by +1.08% :tada:

Coverage data is based on head (6520b35) compared to base (c1a2e00).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
+ Coverage   96.63%   97.71%   +1.08%
==========================================
  Files          31       31
  Lines        2499     2499
==========================================
+ Hits         2415     2442      +27
+ Misses         84       57      -27

Impacted Files
Coverage Δ

...sts/UserDefaults/MultiUserDefaultsStoreTests.swift
100.00% <0.00%> (+0.49%)
:arrow_up:

Sources/UserDefaults/MultiUserDefaultsStore.swift
97.00% <0.00%> (+1.00%)
:arrow_up:

Sources/CoreData/Database.swift
94.64% <0.00%> (+1.78%)
:arrow_up:

Sources/UserDefaults/SingleUserDefaultsStore.swift
90.90% <0.00%> (+3.03%)
:arrow_up:

Sources/Blueprints/Logger.swift
100.00% <0.00%> (+4.54%)
:arrow_up:

Sources/Keychain/SingleKeychainStore.swift
90.42% <0.00%> (+5.31%)
:arrow_up:

Sources/Keychain/MultiKeychainStore.swift
86.89% <0.00%> (+5.82%)
:arrow_up:

Tests/Utils/MultiObjectStoreFake.swift
90.90% <0.00%> (+9.09%)
:arrow_up:

Tests/Utils/SingleObjectStoreFake.swift
89.47% <0.00%> (+10.52%)
:arrow_up:

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

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

Thanks @engali94! I see the overview now after #16
Looks like adding this dependency is not required anymore

UPDATE: It’s no longer necessary to add the DocC plugin to your package. If you’ve added it already, feel free to remove it. Our build system will also cope if you leave the plugin or need it for another purpose, so there’s no rush to remove it! The only change you need to make to your project is to add the manifest file.

Now that #18 is merged, lets keep and eye on the documentation for main, if it doesn't help, then we can merge this and give it a shot.

Hey @omaralbeik I compared with other packages I spotted this difference after double checking the spi.yml file
seems the platform info is missing I am updating this PR

Thanks @engali94, this is the documentation platform, we don't need doc generation in multiple platforms for this package, I don't think we need to specify it, but lets wait to see if the new changes appear here in the next 24 hr first to make sure

Documentation platform
By default, we will generate documentation using macOS. If your package requires the documentation generation to be run for a certain platform such as iOS, you can also specify a platform:

@engali94 Looks like the documentation is fixed now!
I'll close this one, feel free to open another one where you update the .gitignore file

authors: codecov-commenter engali94 omaralbeik

repo: omaralbeik/Stores


text:
Shadow don't work

Hello, Thank you for your great package :)
I want to remove the shadow in my model viewer but shadowIntensity & shadowSoftness don't work. I tried changing the value to 0.0~1.0 but nothing happens.
Can you help me to remove all the shadows in model viewer?
Thank you :)

remove this "}"

@hanshanfeihe Thx :)

authors: hanshanfeihe jamesleetu


text:
V05 dev1

Using schemas from https://github.com/ome/ngff/pull/249
And corresponding data at https://minio-dev.openmicroscopy.org/idr/v0.5-dev1/6001240.zarr
Test at https://deploy-preview-35--ome-ngff-validator.netlify.app/?source=https://minio-dev.openmicroscopy.org/idr/v0.5-dev1/6001240.zarr

@joshmoore @d-v-b
The data above at https://minio-dev.openmicroscopy.org/idr/v0.5-dev1/6001240.zarr was generated from a local v0.4 NGFF sample with this code (NB: this isn't using ome-zarr-py, just plain zarr v3):
One issue is that it doesn't preserve the chunk sizes, since it reads the data as numpy rather than with Dask, so we lose chunks info.
Also this code doesn't handle labels, plates, bioformats2raw layout etc.
import numpy as np
import zarr
import os

path = "/Users/wmoore/Desktop/ZARR/data/6001240.zarr"
# remote fails - see below
# path = "https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0062A/6001240.zarr"

rootpath = "6001240_V0.5-dev1.zarr"
if os.path.exists(rootpath):
    import shutil
    shutil.rmtree(rootpath)

store_class = zarr.store.LocalStore
if path.startswith("http"):
    # TypeError: Can't instantiate abstract class RemoteStore with abstract methods get_partial_values, list, list_dir, list_prefix, set_partial_values
    store_class = zarr.store.RemoteStore
read_store = store_class(path, mode="r")
# Needs zarr_format=2 or we get ValueError("store mode does not support writing")
read_root = zarr.open_group(store=read_store, zarr_format=2)

# Create new Image...
write_store = zarr.store.LocalStore(rootpath, mode="w")
root = zarr.Group.create(write_store)
# copy NGFF attrs
for key in read_root.attrs.keys():
    root.attrs[key] = read_root.attrs[key]
# update version
root.attrs["multiscales"][0]["version"] = "0.5-dev"

# convert arrays
multiscales = read_root.attrs.get("multiscales")
for ds in multiscales[0]["datasets"]:
    ds_path = ds["path"]
    data = zarr.load(store=read_store, path=ds_path)
    print('array', ds_path, data.shape)
    a = root.create_array(str(ds_path), shape=data.shape, chunk_shape=[64] * data.ndim, dtype=data.dtype)
    # These 2 lines are equivalent to e.g. a[:,:] = data (for any number of dimensions)
    s = [np.s_[:]] * len(data.shape)
    a[tuple(s)] = data

Updated the samples at https://minio-dev.openmicroscopy.org/idr/v0.5-dev1/6001240.zarr and https://minio-dev.openmicroscopy.org/idr/v0.5-dev1/6001240b.zarr with version 0.5-dev1 to corresponds to last commit above and fix of version in schemas at https://github.com/ome/ngff/pull/249
cc @joshmoore

repo: ome/ome-ngff-validator


text:
How to add omniauth-okta without devise ?

Hi!
I added this code with credentials
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :okta, ENV['OKTA_CLIENT_ID'], ENV['OKTA_CLIENT_SECRET'], {
    client_options: {
      site:                 'https://your-org.okta.com',
      authorization_server: '<authorization_server>',
      authorize_url:        'https://your-org.okta.com/oauth2/<authorization_server>/v1/authorize',
      token_url:            'https://your-org.okta.com/oauth2/<authorization_server>/v1/token',
      user_info_url:        'https://your-org.okta.com/oauth2/<authorization_server>/v1/userinfo',
      audience:             'api://your-audience'
    }
  }
end

But after restart rails I go to /auth/okta and receive :404
According to the docs I need to pass provider name ( https://github.com/omniauth/omniauth#integrating-omniauth-into-your-application)
Can you please describe, what cause a problem ?
Update: this fork works without devise (https://github.com/andrewvanbeek-okta/omniauth-oktaoauth)

If somebody helps: Resolved + with ability to set credentials dynamically :
module Okta
  class DynamicCredentials
    def initialize(env)
      @env = env
    end
    attr_reader :env
    def call
      request = Rack::Request.new(env)
      settings = Model.get_settings # get dynamic credentials from database
 client_options: {
          site:                 host,
          authorize_url:        "#{host}/oauth2/v1/authorize",
          token_url:            "#{host}/oauth2/v1/token",
          user_info_url:        "#{host}/oauth2/v1/userinfo"
        },
        authorize_params: {
          idp: settings['idp'] # For this param I added specific extension to overrite state param
        },
        redirect_uri: okta_redirect_uri,
        client_id: settings['client_id'],
        client_secret: settings['client_secret']
}
     end
end

OmniAuth.config.logger = Rails.logger
OmniAuth.config.request_validation_phase = false # Need because of csrf issues for auth omniauth POST request
OmniAuth.config.on_failure = Api::OktaController.action(:oauth_failure)

OKTA_SETUP = lambda do |env|
  credentials = Okta::DynamicCredentials.new(env).call
  env['omniauth.strategy'].options.merge!(credentials)
end

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :okta, nil, nil, {
    setup: OKTA_SETUP,
    strategy_class: OmniAuth::Strategies::Okta,
    provider_ignores_state: true # https://github.com/omniauth/omniauth-oauth2/issues/95
  }
end

repo: omniauth/omniauth-okta


text:
Expose the finder API over FFI

With the addition of a Finder API for the gitoid crate, we need to expose it over FFI. For the existing impls, this is pretty easy. One question is how to handle the fact that the trait involved is open-ended (i.e. not sealed), and so additional impls could be provided by third parties.
I'm of the mind that for now we don't need to worry about this, and can just provide functions for the impls we're aware of. That said, I'm open to discuss it!

This API has been removed!

repo: omnibor/omnibor-rs


text:
Allow bracketed lists as arguments to resolvers

This is needed if we want to be able to apply a resolver on a config variable which is a list (using nested interpolations).
Note that doing so is a bit cumbersome though, as we need to do something like:
my_list: [0, 1, 2]
my_function_of_list: ${my_function:${escape_commas:${my_list}},other_arg}

where escape_commas is a resolver that escapes the commas in the string representation of a list.
It may not look great but at least it works, enabling use cases that were not possible before (to the best of my knowledge).

Please explain the motivation in more details. I don't understand what this is doing.

Also, before sending pull requests, especially PRs that are adding new features please open an issue and allow for some discussion.

Closing (superseded by #321)

authors: odelalleau omry

repo: omry/omegaconf


text:
Fix/sidekiq 6.5 breaking changes

This PR is focused to adapt the project to support the changes coming from the Sidekiq 6.5.

The sidekiq/util file is not available anymore. And we don't really need it. I just changed to use the logger from the Sidekiq module;
Update the Ruby version references to 2.6 (dockerfile) and some dev dependencies;
The Poller class requires an argument when Sidekiq version is >= 6.5. I fixed it passing the Sidekiq options. Seems like the right workaround as I could see in the sidekiq repo.

Closes #330

Thanks for that @danilogco! 🙌🏼 Overall, I'm ok with the changes.
Even with this one: https://github.com/ondrejbartas/sidekiq-cron/pull/331/files#diff-bf1bc96faeb372d833380849ebf4e700be88333620eb814bdb57103a5eb6e212R9, as Ruby 2.5 is EOL for some time and we don't run tests for that specific version.
@ondrejbartas @honzasterba what do you think?

authors: danilogco markets

repo: ondrejbartas/sidekiq-cron


text:
Expose sub-device exposed by ZE_AFFINITY_MASK as devices

Moved from https://github.com/oneapi-src/level-zero/issues/86

jandres742 commented 5 days ago
From customer feedback:
Currently with a device with two sub-devices, following mask exposes the root device and bot sub-devices:
ZE_AFFINITY_MASK=0.0,0.1
Request is to have these exposed as two separate root devices. In other words, that each sub-device exposed in the mask is presented by Level Zero as a device, with no sub-devices.

@jandres742
Author
jandres742 commented 5 days ago
When you use the affinity mask, we expose the parent device when at least 2 sub-devices are selected with the mask. From https://spec.oneapi.io/level-zero/latest/core/PROG.html?highlight=affinity#affinity-mask: See here how for a 4 sub-device system, when you have 1.3 and 1.0 in the mask, then we expose the root device and two subdevices for it (see below).
The following examples demonstrate proper usage for a system configuration of two devices, each with four sub-devices:
• …
• 0.2, 1.3, 1.0, 0.3: both device 0 and 1 are reported; device 0 reports sub-devices 2 and 3 as sub-devices 0 and 1, >respectively; device 1 reports sub-devices 0 and 3 as sub-devices 0 and 1, respectively; the order is unchanged.
Now, the reason we do that, instead of exposing 1.3 and 1.0 as separate devices is threefold:
Flexibility:
a. It exposes everything to the application, letting it to decide what to use and what not. If the application wants to see each sub-device as a device, then middleware library (DPC++, OpenMP) or the application can use the sub-device handles, but if other application wants to use the hierarchy of root and sub-device handles, then it would be also available. Limiting to exposing sub-devices as devices always, would limit applications who want to see the hierarchy.
Implicit scaling:
a. By exposing the root device, we allow for implicit scaling to be supported with a sub-set of tiles. In the sample below, we would have implicit scaling with the two-out-of-four tiles 1.3, and 1.0. The application then would decide whether to use the root device with a 2T implicit scaling, or just use the tiles directly. If we exposed each sub-device as a device, then implicit scaling wouldn’t’ be possible with a sub-set of tiles.
Scalability:
a. In the future we could have further levels in the device hierarchy, with sub-devices inside sub-devices. In this case, it would become difficult to decide what a device is. Imagine the case where you have this:
1 root device
2 tiles
Each tile with 4 sub-sub-devices.
Now imagine the user pass this mask:
MASK=0.0,0.1.2,0.1.3
In this case, if we exposed each as a sub-device, then we would have each device with a different set of capabilities, which may further complicate things. However, by exposing in this case
MASK=0.0,0.1.2,0.1.3 =>
root device handle 0
sub device handle 0: representing 0.0
sub-device handle 1: representing 0.1
sub-device handle 0: representing 0.1.2
sub-device handle 1: representing 0.1.3
it is clear, and easier for the application, to traverse the device hierarchy and understand what each device handle represents.
In this case, if the application, DPC++, or OpenMP, wants to see 0.0, 0.1.2, and 0.1.3, as separate devices, can do it by just selecting the right-most leaves in the trees, and if other application wants to see the whole hierarchy, and use implicit scaling, then it would use the device handle that they need.
Now, one proposal from customers is to either change the meaning of the affinity mask, or to define a new one, like ZE_VISIBLE_DEVICES, which allows for this model.

@servesh
servesh commented 4 days ago
@jandres742 Would it make sense to be more pragmatic in the way root devices are shown to the programming layer above?
The current issue seems to stem from, "we expose the parent device when at least 2 sub-devices are selected with the mask"
My thinking here is,
MASK=0.0,0.1.2,0.1.3=>
sub device handle 0: representing 0.0 (Default device 0 from programming layer, if chosen implicitly scale across 0.1.2 and 0.1.3. Memory allocations should be split across the closest domain to these devices, i.e 0.1's global memory)
sub-device handle 0: representing 0.1.2
sub-device handle 1: representing 0.1.3
MASK=0,0.0,0.1,0.1.2,0.1.3=>
root device handle 0 (Default device 0 from programming layer, if chosen implicitly scale across 0.1 and 0.2. Memory allocations should be split across the closest domain to these devices, i.e 0's global memory)
sub device handle 0: representing 0.0
sub-device handle 1: representing 0.1 (device 2 from programming layer, if chosen implicitly scale across 0.1.2 and 0.1.3. Memory allocations should be split across the closest domain to these devices, i.e 0.1's global memory)
sub-device handle 0: representing 0.1.2
sub-device handle 1: representing 0.1.3
And if the application chooses a device handle with subdevice, then implicitly scale the workload across its subdevices.

@jandres742
Author
jandres742 commented 4 days ago
thanks @servesh . I think what you are saying is the same as me, no? The way we have the affinity mask defined allows for allowing users to programmatically select the device handle in the hierarchy that fits their needs, depending on the mask passed. The behavior you showed in your example is exactly that. We would expose several device handles in the hierarchy, and do implicit scaling and color the allocations accordingly, and as you say, the application can programmatically select the handle it wants.
MASK=0,0.0,0.1,0.1.2,0.1.3=>
root device handle 0 (Default device 0 from programming layer, if chosen implicitly scale across 0.1 and 0.2. Memory > allocations should be split across the closest domain to these devices, i.e 0's global memory)
sub device handle 0: representing 0.0
sub-device handle 1: representing 0.1 (device 2 from programming layer, if chosen implicitly scale across 0.1.2 and 0.1.3. Memory allocations should be split across the closest domain to these devices, i.e 0.1's global memory)
sub-device handle 0: representing 0.1.2
sub-device handle 1: representing 0.1.3
If instead of that, we would expose each of this comma-separated masks as a single device, then no memory coloring nor implicit scaling would be possible.
That's why I dont think we should change the meaning of the mask, and previous suggestion from your team about having a separate environment variable to say whether or not we want the comma-separated masks as devices might be more viable.

@TApplencourt
TApplencourt commented 4 days ago •
That's why I dont think we should change the meaning of the mask, and previous suggestion from your team about having a separate environment variable to say whether or not we want the comma-separated masks as devices might be more viable.
I agree. HavingZE_VISIBILE_DEVICES or another ENV, will be maybe more tractable. Look like both behaviors (the visibly and the masking) are needed.
Some users definitely want the same behavior as ROCR_VISIBLE_DEVICES. So not giving a mask, just an "expose was I pass you as a device".
So having 2 different ENV seems to be a good idea!

On oneAPI at least 2 products implemented this feature:

OpenMP via LIBOMPTARGET_DEVICES subdevice
OneDPL via some XXX_SHOW_TILE_AS_DEIVE

FYI: we have a debug key in compute-runtime that provides that functionality:
https://github.com/intel/compute-runtime/blob/0101e80b00e5884fe26fbe58acfdd71bc7814670/shared/source/debug_settings/debug_variables_base.inl#L338
DECLARE_DEBUG_VARIABLE(int32_t, ReturnSubDevicesAsApiDevices, -1, "Expose each subdevice as a separate device during clGetDeviceIDs or zeDeviceGet API call")

Can confirm this atleast enumerates correctly with L0. Needed the NEOReadDebugKeys to be set as well.

ReturnSubDevicesAsApiDevices currently works only with NEOReadDebugKeys=1.

authors: MichalMrozek TApplencourt jandres742 servesh

repo: oneapi-src/level-zero-spec


text:
Add mechanism to gather memory utilization info for all VFs

Add extension capability to current API zesMemoryGetState to gather memory utilization info for all VFs from PF (similar to zesGetEngineActivityExt)

@sanilkumar0 @jandres742 @joshuaranjan @saik-intel @wdamon-intel

@sanilkumar0 : could you take a look?

Similar to Engine activity reported perf VF, Memory usage reporting per VF is required. Create  zesMemoryGetStateExt with 'free' and 'size' fields

@aravindksg  is PR raised for this ?

Closing as we are moving to new set of VF interfaces with #248


text:
Changes in nfp fwaas plugin with monkey patched router methods, creat…

…e_firewall

@njagadish @hemanthravi @songole

Closing this, as raised another PR - https://github.com/oneconvergence/group-based-policy/pull/444

repo: oneconvergence/group-based-policy


text:
Handle error about file size, when file does not exists

Error: Unable to retrieve the file_size for file at location: .

Hi @ExsyDev
Can you please elaborate on this issue ? or give a minimal setup to reproduce this ?
The entity checks for the existence of the file in the file system before attempting to retrieve any metadata relating to it.
Thanks

Hi @ExsyDev
Can you please elaborate on this issue ? or give a minimal setup to reproduce this ? The entity checks for the existence of the file in the file system before attempting to retrieve any metadata relating to it. Thanks

When file already uplodaed, and after removed, then we can see this error on index page of resource.

Please, would you be able to provide a minimum set up to reproduce this ?
Currently we check if the file exists before doing any operations at https://github.com/oneduo/nova-file-manager/pull/175/files#diff-72f4fd3cf2a3b01ecb2cf2ca503f9333c70a64a761cdf900f101787c2df426a0R49
If the file was deleted outside of the tool, we show an error stating the file was deleted.

authors: ExsyDev Rezrazi TEstDevelo

repo: oneduo/nova-file-manager