Unable to build after installing package

Hello am getting the following error after i  installing the package
error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:
  - react-native-admob (to unlink run: "react-native unlink react-native-admob")
This is likely happening when upgrading React Native from below 0.60 to 0.60 or above. Going forward, you can unlink this dependency via "react-native unlink <dependency>" and it will be included in your app automatically. If a library isn't compatible with autolinking, disregard this message and notify the library maintainers.
Read more about autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md

Since i got the error, my application is unable to build, i tried to unlink but here what i get when i try that
info Unlinking "react-native-admob" iOS dependency error Something went wrong while unlinking. Reason Cannot read property 'find' of undefined. Run CLI with --verbose flag for more details. TypeError: Cannot read property 'find' of undefined
please can someone help me? it's been a day now that  am having this problem

I got the same problem with v1.
A installed the V2 (in beta) and now it works

@arochedy  hello please can you tell me how you got it working ? i mean i install the beta but i can't even build the application keeps showing the following errors

> Task :app:transformDexArchiveWithExternalLibsDexMergerForDebug FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.5/userguide/command_line_interface.html#sec:command_line_warnings
234 actionable tasks: 218 executed, 16 up-to-date
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-fs/android/src/main/java/com/rnfs/RNFSManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerButtonViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-reanimated/android/src/main/java/com/swmansion/reanimated/NodesManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-reanimated/android/src/main/java/com/swmansion/reanimated/NodesManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-svg/android/src/main/java/com/horcrux/svg/TSpanView.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Note: /home/stanly/Desktop/kawlo/node_modules/rn-fetch-blob/android/src/main/java/com/RNFetchBlob/RNFetchBlobUtils.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
D8: Cannot fit requested classes in a single dex file (# methods: 75542 > 65536)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  The number of method references in a .dex file cannot exceed 64K.
  Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html

* 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

BUILD FAILED in 22s

error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-fs/android/src/main/java/com/rnfs/RNFSManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerButtonViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-reanimated/android/src/main/java/com/swmansion/reanimated/NodesManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-reanimated/android/src/main/java/com/swmansion/reanimated/NodesManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-svg/android/src/main/java/com/horcrux/svg/TSpanView.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/stanly/Desktop/kawlo/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Note: /home/stanly/Desktop/kawlo/node_modules/rn-fetch-blob/android/src/main/java/com/RNFetchBlob/RNFetchBlobUtils.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
D8: Cannot fit requested classes in a single dex file (# methods: 75542 > 65536)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  The number of method references in a .dex file cannot exceed 64K.
  Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html

* 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

BUILD FAILED in 22s

    at checkExecSyncError (child_process.js:629:11)
    at execFileSync (child_process.js:647:13)
    at runOnAllDevices (/home/stanly/Desktop/kawlo/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:39)
    at buildAndRun (/home/stanly/Desktop/kawlo/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:158:41)
    at then.result (/home/stanly/Desktop/kawlo/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:125:12)
    at process._tickCallback (internal/process/next_tick.js:68:7)

app crashed after installing.
yarn add react-native-admob@next
react-native link

@lmavaiya  having the same error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  The number of method references in a .dex file cannot exceed 64K.
  Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html

* 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.

I got a problem like this.
I try a lot of things but the only thing which work was to support Android version 21 (android 5.0) which support multidex by default.
If you want to know more :
https://developer.android.com/studio/build/multidex

@arochedy Thanks for the respond, the  problem is that  i live in a country where 4.4 is highly used, can't give up the support please can you suggest me another package or solution  ?

Ok. If you read the doc they explain you how to use multidex in Android
before version 5.0
Good luck
El sáb., 14 dic. 2019 11:35, lewatt23<EMAIL_ADDRESS>escribió:

@arochedy https://github.com/arochedy Thanks for the respond, the
problem is that i live in a country where 4.4 is highly used, can't give up
the support please can you suggest me another package or solution ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sbugert/react-native-admob/issues/488?email_source=notifications&email_token=AARIDZQPCR56B2L22U2OTQTQYSZFTA5CNFSM4JTRZ432YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG37VLI#issuecomment-565705389,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARIDZTGYF64HMAPQH3LVV3QYSZFTANCNFSM4JTRZ43Q
.

hi @lewatt23. I ran into the exact same issue. Were you able to resolve the issue?

hello @t08-apporio  all you need to do is enable multidex on android rn [https://rnfirebase.io/enabling-multidex](https://rnfirebase.io/enabling-multidex)

hi @lewatt23. Fixed it without multidex. The gradle and sdk versions were incompatible. Thanks for your input!


Server returns 200 when file paths are wrong

I tried uploading files when the $resumable->tempFolder and $resumable->uploadFolder were pointing to folders/files that didn't exist, and the server was still returning 200 for every call (regardless of testChunks on/off)

Actually, this issue is too specific, I'll just open a new one


Appending/Linking objects with textures causing a black render and freeze

I think this is TxManager related. If appending/linking an object from an external .blend scene, TxManager doesn't add the textures "attached" to said object automatically, the user has to parse the scene manually, which is prone to human error.  Is it possible to run "parse scene" on import/append/linking of objects to the scene?
Here's a capture to better show what's happening. I append an object with textures in the material, and TxManager isn't finding them automatically. * Please disregard the diffuse texture in the TxManger, I have a hidden object in the scene this belongs to.
https://user-images.githubusercontent.com/10125645/136289097-17cc1cc0-b22f-401e-9d6a-472554d3d93d.mp4
And this is the log:
src\liboslexec\instance.cpp:480: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instops.empty() && m_instargs.empty()' failed.
src\liboslexec\instance.cpp:489: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instsymbols.size() == 0 && "should not have copied m_instsymbols yet"' failed.
src\liboslexec\instance.cpp:494: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instoverrides.size() == (size_t)std::max(0,lastparam())' failed.
src\liboslexec\instance.cpp:480: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instops.empty() && m_instargs.empty()' failed.
src\liboslexec\instance.cpp:489: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instsymbols.size() == 0 && "should not have copied m_instsymbols yet"' failed.
src\liboslexec\instance.cpp:494: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instoverrides.size() == (size_t)std::max(0,lastparam())' failed.
src\liboslexec\instance.cpp:480: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instops.empty() && m_instargs.empty()' failed.
src\liboslexec\instance.cpp:489: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instsymbols.size() == 0 && "should not have copied m_instsymbols yet"' failed.
src\liboslexec\instance.cpp:494: RMAN_1697a56_OSL::pvt::ShaderInstance::copy_code_from_master: Assertion 'm_instoverrides.size() == (size_t)std::max(0,lastparam())' failed.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.
S31020 {ERROR}   Inf/NaN detected in bounding of |walls_001|walls_001-MESH after displacement. Displacement will not be applied.

@TzurH  I'll have to think about this. Blender doesn't seem to have a callback for when you link to an object, so we can't add the textures to the texture manager.

I did some more tests and I've noticed this crash only occurs when I open scenes I had previously set up with materials, etc. which is probably why you aren't experiencing it?  If I start a new scene and then build the material from scratch it doesn't crash.

I have shared a test scene with you on Goggle Drive. I've packaged this test scene using the new tool you've added. This scene is running fine on this commit:
https://github.com/prman-pixar/RenderManForBlender/tree/88c8b2ac3ef8f9f09811845585ec643c69d58184
Try to open it using the commits addressing this issue, it should crash.  Let me know if you need anything else to help test/debug.

Can confirm works now. I'm also able to link collections which I was unable to do previously. Amazing! Thanks for the fix 💯


cmake: add proper target exporting

This pull request adds proper cmake target exporting, making it possible to build and install mbed TLS in a location from which it can be effortlessly imported by a separate cmake project. As a bonus, I added some cmake code to automatically extract the version number from version.h and therefore avoid potential issues where one can forget to manually update it in cmake. This was necessary because cmake exporting makes use of the version number.
Here is how it works. First, build and install mbed TLS to an installation prefix:
cmake -DCMAKE_INSTALL_PREFIX=/tmp/mbedtls .
make install

In a separate cmake project, importing looks like this:
find_package(mbedtls CONFIG REQUIRED)
add_executable(mbedtls-sample main.c)
target_link_libraries(mbedtls-sample mbedtls)

For the exported cmake package to be found, it needs to be added to CMAKE_PREFIX_PATH like this:
cmake -DCMAKE_PREFIX_PATH=/tmp/mbedtls .
That's it! the sample project will automatically link to the proper mbed TLS libraries and add the required include directories.
We have been using this method for Windows, macOS, Linux, Android and iOS for a while now and it works quite well.
This is my first pull request, I have read the contribution guidelines. I created an mbed account with the same email used for the commits in this PR and I accepted the contribution agreement.
Thank you!

@awakecoding Thank you for your contribution!
As I mentioned in #2091 we cannot accept any contribution before a CLA has been accepted.
Thank you for your cooperation, and for your interest in Mbed TLS.

@RonEld now that the CLA has been signed, who would be a good person to review and discuss improvements to the cmake build system? Thanks!

could this be addressed now?

@gocarlos If @awakecoding or you rebases this pull request on top of the current development and it passes the CI, we'll give it a look. Please note that most of us on the Mbed TLS team don't know much about CMake, so we need explanations if you use non-obvious features. Also anything that you rely on should be tested via all.sh, otherwise it's likely to break without us noticing.

Note that crypto was, but no no longer is a separate repository, so the reason for postponing is no longer relevant and no change of structure is necessary.

Superseded by https://github.com/ARMmbed/mbedtls/pull/3465


Change URL references from pdsimg.jpl.nasa.gov to pds-imaging.jpl.nasa.gov

Brief Description
The Planetary Data System Imaging Node (PDS-IMG) is deprecating the URL pdsimg.jpl.nasa.gov, in place of the more utilized pds-imaging.jpl.nasa.gov. References should be updated to ensure links to PDS-IMG continue to work.
Expected Behavior

Update all code, README, etc., references of pdsimg.jpl.nasa.gov to pds-imaging.jpl.nasa.gov

Current Behavior

References to pdsimg.jpl.nasa.gov exist within repository

@thareUSGS Did you see this come across?

@riverma Thanks for the warning. Those are simple find/replace URL code snippets. What needs to change first are the Geoscience-node create "ODE" shapefile footprints for MOC (which this script uses).
https://ode.rsl.wustl.edu/mars/coverage/ODE_Mars_shapefile.html
Their footprint pipeline will need to be updated with your URL change. Looks like CTX footprints are updated (not sure about others). I would email their ODE support or forum and you can point to this issue to maybe help them explain or ask for more information. https://pds-geosciences.wustl.edu/contact/default.htm
Once those are update I will update this script too.


PoC version of chimney for scala 3

Attempting to provide as much functionality of chimney as possible, initial state:

transformers of case classes and co-products are supported, no support planned in nearest future for java beans (implementation depends on Mirror's, java beans would probably require totally different approach)
patchers have all the functionality of the ones from scala2 and some (multiple patches applied at one time for runtime performance gains)
configuration is cleaned-up (minimal macro usage in configuration, with well typed config tuples), scoped configuration not considered right now

Special care must be taken regarding performance, we might observe both compile-time and run-time regression in performance, which can be mitigated with replacing mirrors with tasty-reflect based construction of classes (to avoid intermediate representation, and transformation from-into tuples and excessive inline depth)
Once scalafmt has support for scala 3.0 it needs to be configured to clean-up the code, formatted manually for now
Tests need to be rewritten almost from scratch, some of the API was changed, in some cases implicit/given resolution is not working as expected

Hi @wookievx,
this is brilliant!
Have you already published your version somewhere? I'd be keen to try it out. (Otherwise I'll build locally.)
Unfortunately, the core maintainers of Chimney are not very active anymore. Do you aim to get your fork merged into their repository or would you also be willing to have this as a standalone project?
Thanks!

Well It is by not any means stable version, I would really try to test it in real world, but there are significant differences to original library, I was learning scala 3 meta programming and needed to cut some corners (or did not agree with design choices made before).
One biggest disparity is lack of support for java beans, they can be added, given time, but would require deeper dive into Tasty reflect.

Great! I'm interested in moving forward your work. Is there anything I can help?

Well, I have a lot of things on my head right now. There are two problems with the new version right now:

I was learning scala 3 metaprogramming so implementation is not perfect, it probably can be simplified quite a bit (for example instead of deriving transformers in different methods I should directly inline transformer/patcher body for performance reasons, so auto-derived transformer is as performant as possible, avoiding virtual dispatch for fields)
There is feature disparity between chimney for scala 2 and my version (I enriched patcher API with recursive derivation, map patching etc. and applying multiple patches in one go, while I did not implement some features of transformers)
There is very little common code that can be extracted, but if implementation goes in the direction of feature parity it has to be decided what sources should be shared between scala 3 and 2.13 (probably transformer and patcher traits, rest is platform dependent)

Thanks for clarification. As neither I am familiar with metaprogramming in Scala 3, (not even in Scala 2) I'd try make it feature parity first with test cases to let more users be able to try it in their codebase.
Regarding code sharing, it will be ideal if we can cross-build the existing chimney subproject in Scala 2 and 3, exposing the same API with version specific macro implementations.

https://github.com/guersam/chimney/commit/3f2d68599d57e1ebcf7c9fd3f79d5e8f4ff82d60
Here's a quick sketch enabling cross compilation. Upon this setup, we can provide the same API that can be tested with the shared test suites.


PermissionEx Sponge - Group ladder not working correctly

I created a group Trainer (pex group Trainer def false)
I set it as default ( pex default user parent add group Trainer )
I created a child group GymLeader ( pex group GymLeader parent add group Trainer )
I wrote this command: pex rank Trainer add group GymLeader
Then I have assigned to deluxe rank Trainer ( pex user deluxe parent add group Trainer )
promote user deluxe -> ... was already at the top of ladder default
What did I do wrong?
Thanks for help!

I'm wondering the same thing. However I cannot find a response anywhere on the internet pertaining to this issue?

None of the commands used in the Original Post are actual PEX Commands.

These are commands for PEX 2.0, which has different commands.

Ahhh, ok.  I saw that August 2016 stamp and thought this was old potatoes.

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


Issue homepage icon

Fixed issue that appeared on the homepage where the fontawesome icon pushed against the text.
Also home component was refactored into a container component


[PE-D][Tester C] Help Page Direction

Address of help page directed is inaccurate. If I copy the URL and open it. It leads me to the user guide of AB3

Labels: severity.High type.FeatureFlaw
original: mamayuan/ped#1

Consolidated into #175


A good description of how to retain RSEs and the career path

From the discussion two weeks ago, @tobyhodges had an idea on how to formulate sth. that sounds convincing of how to retain RSEs in academia and what would be good arguments to actually do this. I feel this should be part of the call for action paper and the organization paper.
related issues:
#78 #84
pinging some contributors:
@mschwarzmeier @Bisaloo @jngrad @jlinx

There are useful elements on this topic here: https://zenodo.org/record/8264153


[Saitej Kuralla]AB#1179754 Migrated Nancy contect with Httpcontext to support .net core projects

Updated NancyContext with HTTPContext
Update Unit tests that supports the HTTPContext
Added a Example project to use this package

In hindsight, we should probably create 3 projects -
AspnetCore.Hal
This should hold the core components for building the hal responses.
AspnetCore.Hal.SystemTextHalJsonFormatter
Registers an output formatter built on top of SystemTextJsonFormatter.
AspnetCore.Hal.NewtonsoftHalJsonFormatter
Registers an output formatter built on top of NewtonsoftJsonFormatter.


Report abuse: new users are created with spamming purposes (dedewalker9, cfsxflsf, rhdkfk, ... sblvp7249, ... others)

I just opened a request to GitHub for checking dedewalker9 user which looks nasty.
I case I'm wrong let me know!

Good idea, I've done the same. It's obvious is spam so no, you're not wrong.

Me too

Opening  this issue wasn't a good idea. Trolls are only searching for attention, don't feed them. Reporting them to github is the only right thing to do.

@LeaVerou Also, block that user for now, it will prevent him from opening issues I believe.

Wow, that has never happened before. I reported him and blocked him, and closed all his issues, but I don’t think Github lets you delete issues (or am I missing it?). Odd.

Also, I don’t think there’s an issue of “feeding the troll” here, it’s clearly a spambot.

don’t think Github lets you delete issues (or am I missing it?). Odd.

No, you can't delete issues, tho normally GitHub support does that.

This cfsxflsfuser is somehow related to my request of yesterday to block dedewalker9 user too. Just signaled to GitHub but we/github should find a more structured way to block that behaviour before it generate 135 spamming issues!
Any idea ?

The next one is bada999 :(

rhdkfk is the latest offender. I've reported the account and will update if GitHub support responds with useful information.
https://github.com/LeaVerou/awesomplete/issues/created_by/rhdkfk

Github support deleted all issues :)

There's so much spam, it's extremely annoying. I had 548 Github emails of which only around 20 were non-spam. WTF.

How does big repos prevent that?

I suggest everyone is going to Report new abuses to GitHub for this repository to link this thread in the Body issue #70.
GitHub should improve user creation process with "spamming filter kind of" mechanism.
Here my Report abuse: sblvp7249 :

Body
[LeaVerou/awesomplete](https://github.com/LeaVerou/awesomplete) has been targeted by abusive and reiterate users creation with the only pourpose to spam his watcher user list.

This should be stoped as soon as possible to evoid compromising the usability of GitHub `Whatch` button (service/function).

@viktorstrate    I guess they simply have not been targeted yet but not sure

:(

How does big repos prevent that?

I don't know of any repos I work on (some quite big ones) that have been spammed out this hard. Mostly github's anti-spam system works like a charm :(

Six or seven notifications per minute is more than my inbox should handle.
I've just unwatched this repo.

I watch many big repos, and it's the only and first one that has such problem with spam. Weird that github is not able to stop it somehow.

I think it might be related to the fact that it was trending in Github Explore. i.e. there are many big repos, but this one grew too fast and attracted the attention of spammers :(
I’ve never seen this before either.  Thankfully, I have Github emails going to a separate folder.
I don’t understand people like @Mithgol though, talking as if it’s somehow the fault of someone here. It’s not something we can control, no need to sound so disgruntled.

I marked all those emails as spam, and then gmail started marking every incoming github email as spam :smile:
I think @Mithgol was being practical. I thought of it too, but went for the adventure.

We need an answer by GitHub ,,,,
unless they want to loose watch button functionality (and relative "social network data" ) !
Does anybody get more then the following email ?

Hello Luca,

Thanks for the report! Our team is investigating.

Cheers,
Matt

... tons of that actually, but I'll go on reporting and mentioning this thread in the report: issue #70. !

@LeaVerou
don't worry too much about what's happening here.
Filtering a mailbox ourself or going back here by hand without receiving an email notification, is not a big deal and I'm doing it without any effort!
Moreover, this nice toy (- could be a bot-toy a digital version of a boy-toy !?! :-)
... its just rising LeaVerou/awesomplete visibility ... and adoption at the end of the day !
The only failing here is social network credibility of GitHub (sorry to underline that but I care, really).

... hey,
do you see what is happening here ? The pattern is changing on both side !
... I guess @GitHub "is filtering" quicker some how ...
and bot-toy is getting "smarter" ... :-)

@arthurvr       ... I start thinking u were right in this case too, as it ws for old BBS :(

... Trolls are only searching for attention, don't feed them ...

Another spammer - http://whatsappcalling.github.io/whatsappcalling/
He's using github pages for sh!tty surveys.


gohugo can't start

Describe the bug
The hugo tool does not work anymore:
$ nix run nixpkgs#hugo server
Error: failed to download modules: binary with name "go" not found

(same for a nix shell)
Steps To Reproduce
Steps to reproduce the behavior:

nix run nixpkgs#hugo server

Expected behavior
I expect hugo to work directly
Notify maintainers
@schneefux @Br1ght0ne @Frostman

Note that if I install both go and hugo, then it's fine… but I guess go should be added as a dependency in that case no?

It does work for me with the version from master on x86_64-linux and there weren't any recent changes. May you provide more information about what version of nixpkgs you're using?

So my system is based on 1ffba9f2f68 (also x86_64), but in the above tests I was running nix run nixpkgs#hugo server that should download the latest nixpkgs version I guess. When I try with nix-shell, I'm not sure which channel is actually chosen by nix-shell, but in case it helps:

system: "x86_64-linux"
host os: Linux 5.15.34, NixOS, 22.05 (Quokka)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.8.0pre20220411_f7276bc
channels(me): "home-manager, local-nixos-unstable, local-nixpkgs-unstable, nixgl, nixos-20-03-20.03, nixos-unstable, test"
channels(root): "nixos-21.11pre325514.a4bf4434570"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos


searxng: 0-unstable-2024-05-31 -> 0-unstable-2024-06-19

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Was that really so important to merge that you cannot wait a day for a review by me or @9999years ?

Also because of the reformatting we now got a messy history for no good reason...


Analytics - Scroll depth tracking for key stories

We'd like to know how far down a user scrolls before leaving page, with "how far down" pegged to which key story or text section is the last one visible

Did we ever come to a conclusion on whether this is doable without parallax like on the fish viz?

yes, it does seems doable as the fish viz didn't take advantage of parallax features to do this. Instead if was checking for certain elements being above or within the window view. It made these checks 4 times a second.

Looks like we need to add hashes for the sections below the map

fish viz implementation is here: https://github.com/USGS-VIZLAB/climate-fish-habitat/blob/fedab7226d889bb0bac202da36a3b0c42986a95e/layout/js/app.js#L51

☝ would that be very hard to implement? We already have some hashes, and could add some more to wu_story.mustache as needed. We've already got #wu-story, #national-pie, #national-static-pie, #rank-states-interactive, #data-collection, and a few in the footer.

I'm going to give it a shot, hopefully we can just reuse the code used ☝ .  But I really don't know, this is kinda beyond my javscript skillz.

Seems this involves adding jquery, is that a problem?

yeah, I think jquery is a little hefty to bring in for this alone. We might want to ping a js expert to see if this is doable easily w/ vanilla js


fix tlsConfig for csi proxy and install script

This fixes an issue where the install script was over-riding existing wins config as well as sets the default csiProxy http transport to be insecure.
Summary
Fixes a new bug found while testing https://github.com/rancher/rancher/issues/36732 and https://github.com/rancher/rancher/issues/36574
Occurred changes and/or fixed issues

do not override the wins config when using the wins install script
ensure that the default certFilePath in wins config is empty for non-rancher users
set certFilePath as part of the wins install script
call ValidateTLSConfig as part of wins config validation
default to using an insecure http transport to match system-agent functionality

Technical notes summary
in csi.go, we are now specifying an http.Transport struct as it is the only way to mimic a --insecure that is used in the system-agent scripts.
Areas or cases that should be tested
I tested the install script on a windows machine
Areas which could experience regressions
I don't see any areas of possible regressions.
Screenshot/Video

https://github.com/rancher/windows/issues/161


[Synapse] - Build track 2 data plane SDK

This change aims to add the following 3 client libraries for Synapse:

Azure.Analytics.Synapse.Spark
Azure.Analytics.Synapse.AccessControl
Azure.Analytics.Synapse.Development

Most code is generated based on track 2 code generator. While we are still working on board review, we would like to build and release SDK packages in order to unblock our customers.

/azp run

/azp run net - synapse - tests

/azp run net - synapse - ci

/check-enforcer reset

/check-enforcer evaluate

/check-enforcer reset

/check-enforcer evaluate

/check-enforcer override

/azp run net - synapse - ci


Restructure GGIR vignettes

In the past couple of months Jairo and I have been preparing a restructuring of the vignette documentation.
We now have a github-pages framework that we will fill with narrative chapters to describe everything there is to say about GGIR in an accessible way. As a result, the CRAN pages can be be refocused to have a more practical focus with output and parameters dictionaries, as well as reference tables for cut-points.
I am creating this issue to keep track of outstanding tasks:
Chapters 1-7:

[x] Draft and peer-review among ourselves (offline)
[x] Add to branch
[x] Check all looks good locally
[x] Merge with master branch and check all look good online

Chapters 8-12:

[ ] Draft and peer-review among ourselves (offline)
[ ] Add to branch
[ ] Check all looks good locally
[ ] Merge with master branch and check all look good online
[ ] Add hyperlinks in between chapters and republish.

Update rest of GGIR:

[ ] Add reference from GGIR-package.Rd to github pages.
[ ] Revise main CRAN vignette to become more complementary to the github pages, e.g. structured as a demo(s) with a strong focus on discussing GGIR output and all its variables.
[ ] CRAN displays all vignettes https://cran.r-project.org/web/packages/GGIR/. Can this be turned off to skip vignettes to avoid redundancy?

As this grows we can ask users and collaborators to peer-review.

In https://wadpac.github.io/GGIR/articles/chapter3_QualityAssessment.html#auto-calibration-algorithm
there seems to be a problem with the link backup.cal.coef, see specific documentation on this parameter [here](https://cran.r-project.org/package=GGIR/vignettes/GGIRParameters.html#:~:text=setting%20is%20TRUE.-,backup.cal.coef,-Character%20(default%20%3D%20%E2%80%9Cretrieve).


[C2SIM Issue Title]: LOX Schema: Side and Superior mandatory in EntityDescriptor

Issue Type
Change Request
Percieved Urgency
Very urgent
Submitter Name
Hein Kluiver
Contact Email
<EMAIL_ADDRESS>Submitter Organization
TNO
Date of Submission
1 mei 2024
Product
LOX
Description
Should an actor not always have a side and superior? And if there is no superior the value 00000000-0000-0000-0000-000000000000

Consent

[X] I agree to be contacted regarding this issue

Sorry

not very urgent (cannot change it anymore in edit mode)

Need to follow-up on this comment. Seems like having Superior be a mandatory entry, with a default "zero" string when there is no Superior, is more of a usage convention to be documented in a C2SIM coalition agreement than to have as a requirement in the C2SIM standard.


Nginx Ingress Controller performance

Hey Guys -
Observed significant difference in performance when we access the service from nginx-ingress-controller.
Accessing service via NodePort is faster than accessing via nginx-ingress-controller
nginx-ingress-controller:0.8.2
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.4", GitCommit:"dd6b458ef8dbf24aff55795baa68f83383c9b3a9", GitTreeState:"clean", BuildDate:"2016-08-01T16:45:16Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.5", GitCommit:"b0deb2eb8f4037421077f77cb163dbb4c0a2a9f5", GitTreeState:"clean", BuildDate:"2016-08-11T20:21:58Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Ubuntu 14.04
Any pointer to look into ?

@asifhj can you provide more information about your cluster and how you are testing the controller? (like #1482)

@aledbf  I am hitting nginx-ingress-controller through which it send pass the request to kubernetes service. My setup kubernetes setup is not cloud. I tried
I tried this link too to change the proc values. I did't help

I tried this link too to change the proc values. It did't help

@asifhj if you are not running in the cloud the performance of the ingress controller can be affected by the configuration of the nodes (distribution version, updated, kernel version, docker/rkt version, sysctl tuning, fs, etc.).
(most of this things are outside the scope of the ingress controller)
Please post more information about the performance you see in the nginx ingress controller using tools like wrk or vegeta from inside (another pod) and outside the cluster

Please report with the requested information and I'll reopen


Tab subtitles

Support for tab subtitles would be nice, like demonstrated here:

Could probably be easily accomplished if HTML is allowed in the title. The subtitle can then be wrapped in a div (or whatever) and styled via CSS.

You can pretty much achieve this look by using the step slot
<wizard-step
                slot-scope="props"
                slot="step"
                :tab="props.tab"
                :transition="props.transition"
                :index="props.index">

                    {{props.tab.title}}

                  Subtitle

            </wizard-step>

Example https://jsfiddle.net/bt5dhqtf/1564/
However the approach is pretty limited since you would basically have to do some checks.
If you iterate through the tabs to display them, then this could be quite easy with a method
https://jsfiddle.net/bzfb4p8u/19/

    {{getSubTitle(props.index)}}

getSubTitle(index){
    return this.tabs[index].subtitle
}

If you need something more flexible, feel free to open a PR and add a prop on this component https://github.com/cristijora/vue-form-wizard/blob/master/src/components/TabContent.vue
which could be an object with additionalInfo where you could pass the subTitle or other information which you might need. Then, the declaration of the step could be better like this
<wizard-step
                slot-scope="props"
                slot="step"
                :tab="props.tab"
                :transition="props.transition"
                :index="props.index">

                    {{props.tab.title}}

                  {{props.tab.additionalInfo.subTitle}}

 </wizard-step>


Yatin: Watch gamee.com

Yatin requests the watch of the watch_keyword gamee\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

gamee\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


What to do when the model's id has to be String

I have multiple DTOs to parse data from my application's backend API. In this API all objects ids are String. However Ollie's Model class id property is Long, so it conflicts with my API.
In ActiveAndroid Model's id was private and there was an getId method that suited very well in this situation. The application is already working with ActviveAndroid and the API can't be changed.
Have you any clues?
Btw, I'm using Retrofit and Gson on the API side.

Have a look at this answer. https://github.com/pardom/Ollie/issues/38#issuecomment-70501843


Change edit links and de-clutter summary page

-Moved some of the css to the styles.js, should perhaps start thinking of indexing/de-cluttering the styles.js page since it is beginning to get a tad large.
-Set up a better abstraction for the table in the summary page. A lot less clutter.
-Added the links according to the design doc for the 'Edit' and 'Change' links in the summary page.
Todo:
-wait until @pcraig3's merge for the calendar to go through and add the calendar data to the availability row.
-add tests for the new components I added.

rebased and ready for liftoff! 🚀


Drop distincts on product filters

I want to merge this change because it drop usages of qs.distinct() on product filters.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4372 Some product filters generate SQL queries with distinct


Force RAII to solve leaks on ubuntu - fixes #924

For some obscure reason, the Ubuntu platform that was leaking requires this.

It looks like build is failing because the curl dmd 2.067 download fails with error code 22

Hm, two questions:

Do you know why the FreeListRef failed? After all, it also uses RAII to free the memory.
I kept VibeNoSSL as it is, so that no existing projects get broken. If we want to switch to VibeNoTLS, VibeNoSSL should still be recognized as version(VibeNoSSL) version = VibeNoTLS;. May be then later there can also be a deprecation warning, before finally removing it.

Ok yes, a compatibility deprecation would do. I couldn't investigate further for lack of time, it looks like an edge case.
I'm currently writing some high level tests to check new client/server features
Both http/2 and botan are done now, but dmd32 goes out of memory on win64 :/

Yeah, 2.067 got a lot worse wrt memory use :(

Wasn't there a flag or an option in dub to compile each file individually?

Yes, --build-mode=singleFile, possibly with --parallel if the machine has enough RAM.

Yes, --build-mode=singleFile, possibly with --parallel if the machine has enough RAM.

Just tried that, looks like it's not an option. I get errors in every file regarding the static if I'm using to add/remove features. I think Win64 & DMD will be off the table, I'll probably look towards LDC for the near future.
Well now since openssl and botan don't go together, the dub json is going to be a little big:
https://github.com/etcimon/vibe.d/blob/a5f43cfb2fb2db4fbc6a7007f1d8a8cf2b63f59e/dub.json
The 32mscoff is necessary for windows, but the libs aren't included with the compiler. The DMD64 doesn't exist on windows. I won't know what to do with this branch after I'm done testing it

Someone should write a little DEP to add "features" in addition to "configurations". But why do you need all of these? Couldn't you use platform suffixes instead?:
		{
			"name": "libasync_botan_posix64",
			"dependencies": {
				"botan": {"version": "~>1.11.11" },
				"libasync": {"version": "~>0.7.2" }
			},
			"versions": ["Botan", "VibeUseNativeDriverType", "VibeLibasyncDriver"]
		},
		{
			"name": "libasync_botan_posix32",
			"dependencies": {
				"botan": {"version": "~>1.11.11" },
				"libasync": {"version": "~>0.7.2" }
			},
			"versions": ["Botan", "VibeUseNativeDriverType", "VibeLibasyncDriver"],
			"subConfigurations": { "botan": "full_x86" }
		},
		{
			"name": "libasync_botan_win32",
			"dependencies": {
				"botan": {"version": "~>1.11.11" },
				"libasync": {"version": "~>0.7.2" }
			},
			"versions": ["Botan", "VibeUseNativeDriverType", "VibeLibasyncDriver"],
			"dflags-windows-x86": ["-m32mscoff"],
			"subConfigurations": { "memutils": "32mscoff", "libasync": "32mscoff", "botan": "full_win32", "libhttp2": "32mscoff" }
		},

Also, why is 32-bit COFF needed? If there is no technical requirement, I'd leave that as a user decision. Same goes for VibeUseNativeDriverType, that should also be a user option.

I tried subConfigurations-windows-x86 but it's not implemented.

Also, why is 32-bit COFF needed? If there is no technical requirement, I'd leave that as a user decision. Same goes for VibeUseNativeDriverType, that should also be a user option.

There's more than 32k symbols if you count in the botan library, so unfortunately OMF isn't an option

Sorry, you are right about subConfigurations. Forgot about that. But can't you structure the botan package description in a way that it doesn't require explicit configuration selections?
More than 32k symbols in botan alone? Shoudn't the individual packages each more or less have their own share of available symbols (except for template instantiations)?

More than 32k symbols in botan alone? Shoudn't the individual packages each more or less have their own share of available symbols (except for template instantiations)?

D doesn't have a pre-processor, so I ended up replacing all the ASM and SIMD code generation macros into CTFE functions. That stuff takes up so much symbol space it's hard not to cringe.
e.g. https://github.com/etcimon/botan/blob/master/source/botan/hash/sha1_x86_64.d#L268

But can't you structure the botan package description in a way that it doesn't require explicit configuration selections?

Yes, I just realized I can use version-x86_64 and version-x86, so the only thing is the coff. If it had a version-x86-coff it would be possible not to split configurations.
However, for openssl/botan combinations I can't do much.

Right, OpenSSL and Botan should both be handled by "features" rather than "configurations", but for now that should be ok.
About Botan, would separating the library into multiple sub packages be an option or do the modules have too many interdependencies?

About Botan, would separating the library into multiple sub packages be an option or do the modules have too many interdependencies?

I haven't looked into subpackages yet, but there's a lot of "version" tags that allows to start with a very light bare bone (sha256 gives me a 800kb exec), and you can add algorithms selectively. You can see the dub file here. I'm not sure if defaulting to a lower setting is easily do-able, the factory finds algorithms with string matching so the compiler can't give any warnings. If the algorithm isn't versioned in when it's requested by a user application, it will crash with a segfault, and most of the unit tests aren't designed for this selective use case.
This is probably alright for the TLS general purpose, so I'd have to give that a try.

@s-ludwig Could you explain what you meant when you said that 2.067 got worse with memory?

I have a few projects that don't compile on Windows anymore due to out of memory errors. DMD 2.066.1 still works, though.

I've managed to make a dmd x64 build on windows thanks to this:
http://forum.dlang.org/thread/mghqlf$10l2$1@digitalmars.com#post-ybrtcxrcmrrsoaaksdbj:40forum.dlang.org

All issues with FreeListRef have been fixed, so this can be closed safely.


Fix #335: Remove the need for the  Gradle capsule plugin.

Packaging should now work with Gradle 7.

I tested with Gradle 7.4.2.

OK, there were three packaging tests. I've commented one out (it was looking to execute a non-existent jar file, and we don't do that now, anyway - we execute scripts that contain jars inside them). The other two tests pass after some minor changes.

Hi! Your code works wonderfully 👍 I think that we should apply it to the branch kscript_4.1 as there is a new development. In this branch, I have added OS independent paths, so testing multi-OS behavior should be easier. There are only a few changes that may affect your patch:

All occurrences of Path were changed to OsPath. Generally, all common functionality should be covered in OsPathExt.kt
In parsed script fileName is just a file name without extension - you don't have to use dropExtension in your code
test_suite.sh -> linux_suite.sh
Unit test for CommandResolver still fails - I was working on Windows cmd support, but it is really deeply screwed up, so it takes a lot of time

So please rebase this patch to kscript_4.1. I will add also some comments to your code.

OK, I've addressed most of the comments and added questions where things are unclear. Please take a look, and I will then look at merging with 4.1 in a separate PR.

Please rebase on 4.1 branch - I think we shouldn't introduce any more breaking changes in 4.0

Done, see #370. Note that --package was already broken, hence this issue.

From my point of view, I would rather not copy files to the current directory, but in all cases (cached/not cached) communicate to user where is package located.

Sure, but that's a change to existing behavior, isn't it? For example, the packaging tests expect the executable to be placed in the current directory. Of course, they could be changed, but the cache package location for the executable could change every time because of hash changes. So I'm not the current simplistic Bash-based tests will cope ...

I think it is not worth adding an additional indentation function

OK, I'll see about removing it.


Indicate possibility to update if new update available

Description
Prompts only in a selection of views as to not interrupt users during work.
Closes: #414
The easiest way to test things is to change this line to something like:
        return {"version": "v2020.01.1"}

This should trigger the update dialog.
Checklist

[X] The PR branch is set up to merge into dev instead of master.

For future reference, this was the line to change to test this feature:
https://github.com/orchest/orchest/blob/354481ff355313b922f1f23a1614a95a5d539326/services/orchest-webserver/app/app/views/views.py#L239


Exception Handling

Currently, exception handling policy will be considered only on yield $curl. It means the following code causes Uncaught Exception.
Co::wait(function () {
    yield Co::SAFE => function () {
        throw new \RuntimeException;
        yield 1;
    };
});

I'm fixing it, but that feature requires me very complicated codes...

Working branch: https://github.com/mpyw/co/tree/scoped-exception-handling-support


Poll-wait when installing (but not necessarily when 'busy')

If another tile is in the process of being installed, the pipeline needs to wait. But it shouldn't wait anytime there's a staged change-- it should only wait when the Opsman is in the process of "installing".

Much more interested in using some kind of locking system rather than constantly polling the opsman & parsing out it's status. Closed in favor of #13


Update sdfstudio_dataparser.py

Explicitly split training set and validation set, when there is no split provided. The default validation split will be the indices that can be divided exactly by an integer, i.e. self.config.skip_every_for_val_split.
Current implementation might cause confusion as validation set is contained by the training set.
Thanks for your wonderful project and your effort.

@qsun1 Thanks for the PR. We use all the images for training to make it consistent with previous work. For example, NeuS and VolSDF use all DTU images for training. Could you add it as an option so we could exclude testing images when it's specified from the training command.

@niujinshuchong Thanks for your advise. I've add the train_val_no_overlap option for the training command.
I test the code in my device:
MODEL="neus"
INDOOR="True"
DATASET="replica-scan1"
PATH_DATA="../Replica/scan1"
train_val_no_overlap="True" # options

ns-train ${MODEL} --pipeline.model.sdf-field.inside-outside ${INDOOR} --vis tensorboard --experiment-name ${MODEL}-${DATASET} sdfstudio-data --data ${PATH_DATA} --skip_every_for_val_split 10 --train_val_no_overlap ${train_val_no_overlap}

The size of training set would be 90 instead of 100 (number of all images in the dataset).
Setting up training dataset...
Caching all 90 images.
Setting up evaluation dataset...
Caching all 10 images.


Multiple translations could possibly write to the same output CR

Spawned from the discussion on https://github.com/fusor/cpma/pull/113#discussion_r282676836
Quoting from that comment:

Have we considered the fact that more than one ocp4 feature may need to provide their configuration on the same CR, which means they'd need to edit a shared output file? Perhaps we need to share a data structure between transforms that represents the total file output so that more than one Translator can mutate the same individual output file.

The model we have in place allows to treat several components "working" on the same CR.
Please create a new issue if needed.


Daikin integration no longer works correctly when set up using configuration.yaml

Home Assistant release with the issue:
0.94.3 (worked fine with 0.83.1)
Frontend JavaScript version: latest
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker, official raspberrypi3-homeassistant container.
Component/platform:
https://www.home-assistant.io/components/daikin/
Description of problem:
After upgrading to 0.94.3 from 0.83.1 my daikin climate control integration stopped working.
I saw others facing the same issue, and a proposed workaround was to remove it from config and manually click it using the frontend, but this is not useful for me, as I'm relying on configuration.yaml whenever possible to have everything versioned with git. It makes it easier for me to automate deployment from staging to the production instance.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
daikin:
  hosts:
    - !secret salon_ac_ip

climate:
  - platform: daikin
	host: !secret salon_ac_ip

secrets.yaml:
salon_ac_ip: <IP_ADDRESS>

Traceback (if applicable):
Log Details (ERROR)
Tue Jun 18 2019 11:24:27 GMT+0200 (Central European Summer Time)
ClientError
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 495, in _request
    resp = await req.send(conn)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 626, in send
    await writer.write_headers(status_line, self.headers)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 112, in write_headers
    self._write(buf)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 67, in _write
    raise ConnectionResetError('Cannot write to closing transport')
ConnectionResetError: Cannot write to closing transport

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/daikin/config_flow.py", line 47, in _create_device
    await device.init()
  File "/usr/local/lib/python3.7/site-packages/pydaikin/appliance.py", line 188, in init
    await self.update_status(HTTP_RESOURCES[:1])
  File "/usr/local/lib/python3.7/site-packages/pydaikin/appliance.py", line 254, in update_status
    self.values.update(await self.get_resource(resource))
  File "/usr/local/lib/python3.7/site-packages/pydaikin/appliance.py", line 230, in get_resource
    return await self._get_resource(resource)
  File "/usr/local/lib/python3.7/site-packages/pydaikin/appliance.py", line 245, in _get_resource
    'http://%s/%s' % (self.ip, resource)) as resp:
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1005, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 507, in _request
    raise ClientOSError(*exc.args) from exc
aiohttp.client_exceptions.ClientOSError: Cannot write to closing transport

Additional information:
I thought that climate config section might be redundant, but removing it also did not fix the problem. Again, it was working fine with the previous HA version.

The issue you linked to is not related to your issue.
Start with removing everything related to Daikin in your config, the device will be auto-discovered and configured in most cases.
Your issue is due to something happening on the socket that is used to communicate with the AC. Perhaps there is multiple connections on the same socket..

Thanks for the tip @fredrike, but I have already removed both climate and daikin components from configuration.yaml file, but the component did not appear on the frontend. Also services related to any of these was unavailable.
I had no problem with this in 0.83.1. I wanted to downgrade HA but there are several incompatibilities which prevents me from doing that (different onboarding file structure, etc).

Did you get the same issues when trying to add Daikin via Configuration -> Integrations?
The configuration is still backable (but via .storage/core.config_entries)..
Let's hookup on discord (I'm fredrike#1724) and we'll see if we can fix it..

proposed workaround was to remove it from config and manually click it using the frontend, but this is not useful for me, as I'm relying on configuration.yaml whenever possible to have everything versioned with git

I should actually add there that this workaround is working, but no luck if I want use configuration.yaml. I'll check discord in few mins.

@MartinHjelmare Is this an error that should be handled by the pydaikin lib?

Probably, but I'm not sure what's going on.

@MartinHjelmare Is this an error that should be handled by the pydaikin lib?

Probably, but I'm not sure what's going on.

The issue should be cached here https://github.com/home-assistant/home-assistant/blob/d22c3f13b2262a2a8fa4d4ef02ebfc709c3a5620/homeassistant/components/daikin/config_flow.py#L47


mc_pos_control: different LPF cutoffs for XY and Z

We want to be able to have different LPF cutoffs for XY velocity and Z velocity, so we can tune XY tracking without affecting descend speed.

Will squash before merging, leaving commits now for easier review


fix environment for symlinked Python package which have their sources in a subdirectory

#219 introduced a regression for Python packages which don't store their first level Python package in a direct subdirectory below the setup.py file (it passes something like this in the setup() function: package_dir={'': 'somewhere'}).
When building with --symlink-install the easy-install.pth file (which was removed by the referenced PR) made sure that the Python package was found in the source directory of the package. With it being removed the fallback was used which is the build directory being part of the PYTHONPATH.
For packages as described above that PYTHONPATH entry pointing to the packages build directory is incorrect. It needs to point to the subdirectory from where the Python packages can be found - in the above example that would be <pkg-build>/somewhere.

A package where I ran into this: ros-visualization/rqt_robot_steering#7


Split up core in smaller sub modules

Changes
Split up core in smaller sub modules, e.g. generic_series and mathematical_expression and so forth.

In my opinion the code is better maintainable, if modules are kept smaller.
The complains of static analysis are not new, but now show up as being newly introduced.
Regarding the RTD issues, I'm not able to reproduce these locally. But I think they are also not related to the changes made here.


MWPW-159560

Resolves : MWPW-159560

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 88.62%. Comparing base (a36877e) to head (2485637).
Report is 8 commits behind head on stage.

Files with missing lines
Patch %
Lines

acrobat/scripts/alloy/verb-widget.js
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #845   +/-   ##
=======================================
  Coverage   88.62%   88.62%
=======================================
  Files          51       51
  Lines        7814     7814
=======================================
  Hits         6925     6925
  Misses        889      889

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


Less aggressive browserslist

Is your feature request related to a problem? Please describe.
Currently the default browserslist is set to "last 4 versions, > 1%, IE 11." This evaluates to the following browsers:
and_chr 85
and_ff 79
and_qq 10.4
and_uc 12.12
android 81
baidu 7.12
bb 10
bb 7
chrome 85
chrome 84
chrome 83
chrome 81
edge 85
edge 84
edge 83
edge 81
firefox 80
firefox 79
firefox 78
firefox 77
ie 11
ie 10
ie 9
ie 8
ie_mob 11
ie_mob 10
ios_saf 13.4-13.7
ios_saf 13.3
ios_saf 13.2
ios_saf 13.0-13.1
ios_saf 12.2-12.4
kaios 2.5
op_mini all
op_mob 46
op_mob 12.1
op_mob 12
op_mob 11.5
opera 70
opera 69
opera 68
opera 67
safari 13.1
safari 13
safari 12.1
safari 12
samsung 12.0
samsung 11.1-11.2
samsung 10.1
samsung 9.2

This is way more browsers than we need to support. We do not support IE mobile, IE 8-10, or Opera, for instance. This bloats our build by including unnecessary CSS prefixes.
As a test, I removed the "last 4 versions" from the auro-button browserslist and ran a build. The output (non-minified) CSS was 26 lines less and over 1KB smaller when minified (7.47KB vs 8.61KB). This is due to removing unused prefixes like -webkit-box-shadow, -webkit-transform, -ms-transform, -o-text-overflow, -moz-user-select, -webkit-transition, -o-transition, -webkit-animation, and -webkit-box-sizing.
Describe the solution you'd like
We should identify the browsers we need to support and set the browserslist accordingly instead of including the last 4 versions of every browser. This should first be done in the generator and then all other components updated.
Additional context
This doesn't appear to affect the transpiled Webpack output at all.

I 100% agree @geoffrich. Although part of the problem is the lack of real browser support specification, so with this we went with the catch-all as not to make waves. As well, it is a common template.
What is interesting to note is that Alaska has released a new official browser support page https://www.alaskaair.com/content/about-us/site-info/browser-info and this clearly states the following:

We support recent versions of the browsers listed below. Newer versions are more secure, load faster and display better-looking pages.

Also, notice the lack of IE.
I think what you are going for would be
  "browserslist": [
    "last 2 version",
    "> 5% in US",
    "not IE 10",
    "not IE_Mob 10",
    "not IE_Mob 11"
  ],

Which outputs
and_chr 85
and_ff 79
and_qq 10.4
and_uc 12.12
android 81
baidu 7.12
bb 10
bb 7
chrome 85
chrome 84
edge 85
edge 84
firefox 80
firefox 79
ie 11
ios_saf 14.0
ios_saf 13.4-13.7
ios_saf 13.3
ios_saf 12.2-12.4
kaios 2.5
op_mini all
op_mob 59
op_mob 12.1
opera 70
opera 69
safari 14
safari 13.1
samsung 12.0
samsung 11.1-11.2

That browserslist looks like it still has a lot of browsers we don't plan on supporting (e.g. opera mini). Could we do something like:
last 2 Chrome versions
last 2 iOS major versions
ie 11
last 2 Firefox versions
last 2 Edge versions
last 2 Safari major versions

That outputs the following, which seems much more reasonable:
chrome 83
chrome 81
edge 83
edge 81
firefox 76
firefox 75
ie 11
ios_saf 13.4
ios_saf 13.3
ios_saf 13.2
ios_saf 13.0-13.1
ios_saf 12.2-12.4
ios_saf 12.0-12.1
safari 13.1
safari 13
safari 12.1
safari 12

Working with auro-button, here are the following bundle size results.
Baseline

13248 auro-button__bundled.js

  "browserslist": [
    "last 2 version",
    "> 15% in US",
    "not IE 10",
    "not IE_Mob 10",
    "not IE_Mob 11"
  ],

13117 auro-button__bundled.js

  "browserslist": [
    "last 2 Chrome versions",
    "last 2 iOS major versions",
    "ie 11",
    "last 2 Firefox versions",
    "last 2 Edge versions",
    "last 2 Safari major versions"
  ],

12087 auro-button__bundled.js

Total savings, around 1k. Savings are good, but this feels pretty aggressive and exclusionary. Are the trade-offs correct?

I think the trade-offs are fine, since we're only using this to generate CSS prefixes. Worst case, the browser doesn't apply the CSS (which is almost always a progressive enhancement).
I diffed the auro-button CSS outputs of the 2 buttons and here's the prefixes that are being added:

-moz-user-select
-webkit-transform
-webkit-box-shadow
-webkit-box-sizing
-webkit-animation
-webkit-transition

A quick perusal of caniuse indicates that most of these are not necessary for modern browsers. Most of the savings seem to come from removing -webkit-box-shadow, which doesn't appear to need prefixes since 2011. Even if we did miss one, they wouldn't break the component. I think the 1KB savings is worth it.

moz-user-select: Firefox <= 68 (Jul 2019)
webkit-transform: Chrome <= 35, Safari <= 8, Android <= 4.4.4
webkit-box-shadow: Chrome <= 9, Safari <= 5, Android <= 3
webkit-box-sizing: Chrome <= 9, Safari <= 5, Android <= 3
webkit-animation: Chrome <= 42 (2015), Safari <= 8 (2014), Android <= 4.4.4
webkit-transition: Chrome <= 25, Safari <= 6, Android <= 4.3
(stats from caniuse)
Every prefix besides moz-user-select has had unprefixed support for at least 5 years. I think it's okay to stop adding them. Firefox is an evergreen browser and user-select is an enhancement, so we shouldn't stress about not adding it.

The browserlist is also used for the webpack config in creating the bundled files. Removing IE 11 also reduces the bundle size.

11364 auro-button__bundled.js

And agreed ... vendor prefixing is dead in the water. The vast majority of the issues there are in regards to features that webkit still release out of band with the standards group to support iOS.
In the end, I am good with this recommendation.

Reopening the issue because we need to dig a little deeper.

My issues are twofold:

We are including 1KB of prefixes we might not need (at least on auro-button, other components could be less/more)
last 2 versions includes way too many browsers. If there's browsers we want to support that require prefixes, that's fine, but we should be explicit about what those browsers are instead of including the last 2 versions of every browser in caniuse.

The biggest offender for auro-button, -webkit-box-shadow, seems to be due to the MDN data for Android webview. However, the data seems suspect to me since it also says "Support unknown" and the main caniuse entry for box-shadow doesn't mention it.
So, if you think my proposal doesn't include enough browsers? Let's add more to the list. But let's not blanket include the last two versions of every browser.
As a reminder, my proposal was
  "browserslist": [
    "last 2 Chrome versions",
    "last 2 iOS major versions",
    "ie 11",
    "last 2 Firefox versions",
    "last 2 Edge versions",
    "last 2 Safari major versions"
  ],

I'm also not opposed to leaving in some sort of percentage-based criterion to catch commonly-used browsers we missed, e.g. >1% in US.

:tada: This issue has been resolved in version 2.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated SwiftyTask lib

Changed github link to new for SwiftyTask

Project URL

Category

Description

Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          2 Warnings

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

:warning:
Found 3 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1172
301
https://github.com/MailOnline/Reactor redirects tohttps://github.com/RuiAAPeres/Reactor

2045
404
https://github.com/dereklimbus/hedwig

2369
404
https://github.com/dereklimbus/pivot-slider

  Generated by :no_entry_sign: Danger

Is there any specification on the error?

I feel like there are broken links?

@Albinzr Please move the project to the end of the category. The broken links I'll fix them.


How to run with Google Appengine?

As long as GAE Standard Environment only supports Python2, I'd say it's not possible to run a Hug app in it. Anyhow, you could run a Hug application in GAE using its Flexible Environment. You'd have to enable the billing though.

You can replace Flask in the AppEngine examples with Hug and it just works provided you are using the Flexible Environment. I use hug with gunicorn there just fine.


Question: Change terminology? (ie. Books -> Pages)

Hello, first off I would like to say I only just installed BookStack and so far I am loving the design and easy of use. It is pretty much perfect for my use-case.
However, I was wondering how the language system works exactly (would manual translations need to be made for Books?)
And also, I would like to use a different terminology, for example I would like to rename:
Books -> Pages
Chapters -> Sections
Shelves -> Categories
Is there an easy way to go about doing this? I was thinking perhaps through the language system, but I have never heard of crownedin before (or used any other translation system before really) and I am having some trouble understanding how it works.
Thank you, and a happy new year :)

Hi @aekramer,
These terms are fixed to official BookStack terms (Books,Pages,Chapters) within the project code so we wouldn't accept any such changes to the included translations files or via Crowdin.
To support this kind of use-case, The ability to locally & selectively override the translation files will be available in the next release; Details can be found here:
https://github.com/BookStackApp/BookStack/pull/1749
That said, This won't affect some areas such as the names used in URLs.

Hi @aekramer,
These terms are fixed to official BookStack terms (Books,Pages,Chapters) within the project code so we wouldn't accept any such changes to the included translations files or via Crowdin.
To support this kind of use-case, The ability to locally & selectively override the translation files will be available in the next release; Details can be found here:
#1749
That said, This won't affect some areas such as the names used in URLs.

Alright, thank you for the heads up I will be waiting for that version release.
The terminology seemed a bit weird to me, especially since the system is being described as a wiki system, for which shelves/books make little sense

Since the original question has been answered, and since the mentioned release is now available, I'll close this off.


ClimatologyConfig should use relative time for ranges

The current implementation expects a full datetime for tspan, including the year. For example:
tspan=(np.datetime64('2011-01'), np.datetime64('2011-07'))

This isn't very generic -- one would expect to be able to describe a range of possible values for a particular month or season, regardless of year.
Suggested updates:

tspan becomes a tuple of int's that represent the "day of year"

Note: we could also consider using "month of year" instead?

The code maps each observation to a climatology bucket
If a range of dates is missing from the climatology, this is a valid use case and should not fail

There might not be enough historic data to define a climatology for every month of the year. For example, a buoy that is only deployed in the summer months
We could show a warning message if the climatology doesn't cover the whole year

How to handle leap years?

If this matters to you, you're probably overfitting

@yosoyjay @reedan88 @cseaton @patcdaniel Please comment if I missed anything

This was fixed with https://github.com/ioos/ioos_qc/pull/21 and https://github.com/ioos/ioos_qc/pull/22 (thanks @kwilcox !)


Provision two linux testbeds with samsung a02

This is to support benchmark tests on low end devices for regression check.
/cc @iskakaushik

Progress:

[x] Provision a new intel nuc with ubuntu image, and get salt setup
[ ] setup dns for remote connection
[ ] setup samsung a02 device (blocked on Verizon account setup)

Two A02s devices have been setup. One connected to linux-27, and processing jobs.

This is complete.


[AutoDiff] TF-123: fix reabstraction to opaque

This fixes TF-123 by adding a new abstraction pattern that properly abstracts the derivative functions in a differentiable_function bundle that is being abstracted to AP::Opaque.
Even though this technically fixes TF-123 (all its testcases compile and run successfully), many simple operations involving opaquely differentiable functions are still broken due to TF-1122. I believe that TF-1122 is a distinct problem, so it makes sense to fix it later in a separate PR.
This also adds tests for reabstraction:

The last 3 tests in reabstraction_e2e.swift are the ones that have been fixed by this PR.
The last 3 tests include some commented-out code that currently segfaults at runtime due to TF-1122.
All the tests in reabstraction_e2e.swift except for the last 3 already pass before this PR. I just used this PR as an opportunity to test reabstraction more thoroughly.

The comment that I added in AbstractionPattern.h describes the solution in more detail:
    /// A Swift function whose parameters and results are opaque. This is
    /// like `AP::Type<T>((T) -> T)`, except that the number of parameters is
    /// unspecified.
    ///
    /// This is used to construct the abstraction pattern for the
    /// derivative function of a function with opaque abstraction pattern. See
    /// `OpaqueDerivativeFunction`.
    OpaqueFunction,
    /// A Swift function whose parameters are opaque and whose result is the
    /// tuple abstraction pattern `(AP::Opaque, AP::OpaqueFunction)`.
    ///
    /// Purpose. When we reabstract `differentiable_function` using the
    /// `AP::Opaque` pattern, we use `AP::Opaque` to reabstract the original
    /// function in the bundle and we use `AP::OpaqueDerivativeFunction` to
    /// reabstract the derivative functions in the bundle. This preserves the
    /// `differentiable_function` invariant that the derivative type
    /// (`SILFunctionType::getAutoDiffDerivativeFunctionType()`) of the original
    /// function is equal to the type of the derivative function. For example:
    ///
    ///   differentiable_function
    ///     [parameters 0]
    ///     %0 : $@callee_guaranteed (Float) -> Float
    ///     with_derivative {
    ///       %1 : $@callee_guaranteed (Float) -> (
    ///         Float,
    ///         @owned @callee_guaranteed (Float) -> Float
    ///       ),
    ///       %2 : $@callee_guaranteed (Float) -> (
    ///         Float,
    ///         @owned @callee_guaranteed (Float) -> Float
    ///       )
    ///     }
    ///
    /// The invariant-respecting abstraction of this bundle to `AP::Opaque` is:
    ///
    ///   differentiable_function
    ///     [parameters 0]
    ///     %3 : $@callee_guaranteed (@in_guaranteed Float) -> @out Float
    ///     with_derivative {
    ///       %4 : $@callee_guaranteed (@in_guaranteed Float) -> (
    ///         @out Float,
    ///         @owned @callee_guaranteed (@in_guaranteed Float) -> @out Float
    ///       ),
    ///       %5 : $@callee_guaranteed (@in_guaranteed Float) -> (
    ///         @out Float,
    ///         @owned @callee_guaranteed (@in_guaranteed Float) -> @out Float
    ///       )
    ///     }
    ///
    /// In particular:
    ///
    /// - The reabstraction %0 => %3 uses pattern `AP::Opaque`.
    /// - The reabstraction %1 => %4 uses pattern
    ///   `AP::OpaqueDerivativeFunction`, which maximally abstracts all the
    ///   parameters, and abstracts the result as the tuple
    ///   `(AP::Opaque, AP::OpaqueFunction)`.
    /// - The reabstraction %2 => %5 similarly uses pattern
    ///   `AP::OpaqueDerivativeFunction`.
    OpaqueDerivativeFunction,

Can one of the admins verify this patch?

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci please test tensorflow macos

@swift-ci Please test tensorflow is still down, so I'll help test this PR on macOS manually.

I merged apple/tensorflow and pushed some minor edits.
swift/utils/build-script --preset tensorflow_test passes on macOS. Merging now!


Determining type of JSON at runtume

I had a question about determining what type of JSON is present at runtime.
I'm trying to parse data from an exchange and right now there's two different messages I can receive
a Pong:
{"success":true,"ret_msg":"pong","conn_id":"daccac2a-c146-48ec-a069-90fd2bd7c48d","op":"ping"}
or Market Data:
{"topic":"orderbook.1.BTCUSDT","ts":1676942675027,"type":"delta","data":{"s":"BTCUSDT","b":[],"a":[["24840","0.76475"]],"u":39480281,"seq":3144408541}}
Originally I figured I could use glz::get_sv_json or variant handling, but because neither of the responses have any common keys, trying to read the value of a key results in an error being thrown. Ideally, I don't want to use errors in my control flow, so I've resorted to modifying the raw string beforehand like this:
data = data + "\"op\":\"update\""
so when I parse data, I can check for the key 'op' and since 'op' already occurs in the Pong response I get different values and parse the JSON accordingly. However, I feel like this isn't ideal and I was wondering if there was potentially a faster and more elegant way to do this.

Yeah variant type deduction support is pretty minimal right now and I could recommend some ways of handling your specific case but I prefer a more general solution and I think it is feasible in a relatively performant manner.
General solutions:

We need a better way of specifying custom type deductions
We could improve the auto deduction for the meta objects

One has been a longstanding issue that has been put off since we do not want to get locked into a bad interface and we haven't entirely decided what to do. Two can be implemented and improved later without breaking anyone using glaze since its internal so Id be more interested in tackling that issue right now.
I thought about it for alittle bit, and we have a lot of type info compile-time so we can deduce when certain combinations of keys have to result in one type with the variant. Here is a basic outline:

Create a compile time constexpr perfect hashmap of the key to uint64_t (or maybe a std::bitset or array of uint64_t to support more types in the variant but who uses more than 64 types in a variant) with each bit representing if the key belongs to the type for that type index in a variant.
Start with a uint64_t possible_types with all bits set to one
Parse the key and lookup in the map and bitwise and the result with possible_types
Use std::has_single_bit to detect if a single type matches
If a single type matches parse as that type (Use one of the std bitscan functions to get the type index), if possible_types equals zero error out, otherwise skip to the next key (skip_ws match<':'> skip_ws, skip_value), and resume step 3. If we reach the end of the object we could either error out or parse it as the first type that matches. We might also want to keep track of the key and value string_views to speed up the parsing when we know the type (We know the max keys compile-time so we can put them in a std::array since dynamic memory allocation is expensive) but I think such optimizations can wait.

This would work in your case pretty well as there is no overlap in the keys so it could immediately deduce the type and would automatically select the correct type in a std::variant without any additional code on your end if implemented.
I'll talk to @stephenberry later to see what he thinks and try to brainstorm a bit but I think it is worth implementing and should be fairly straitforward.

Amazing. After checking the response sizes for my situation I think I can deduce the type with straightforward data.size()comparison. Would be great to see those features in the future.

@themorlock lol that's hilarious, sometimes the simplest solution is the best solution.
I think it's still a good idea to implement better auto deduction and I'll try to get that in as soon as the no_except branch is ironed out.

Automatic object deduction in a std::variant based on unique key combinations was merged into the no_except branch in #175.
This also includes better tagged variant support. Still need to add some info on std::variant support and its limitations to the readme/docs.
no_except is being treated as the next major feature release branch (Some breaking changes are being made) and should be merged into main on this coming Monday so I'm closing this issue out.
Auto deduction example:
struct xy_t
{
   int x{};
   int y{};
};

template <>
struct glz::meta<xy_t>
{
   using T = xy_t;
   static constexpr auto value = object("x", &T::x, "y", &T::y);
};

struct yz_t
{
   int y{};
   int z{};
};

template <>
struct glz::meta<yz_t>
{
   using T = yz_t;
   static constexpr auto value = object("y", &T::y, "z", &T::z);
};

struct xz_t
{
   int x{};
   int z{};
};

template <>
struct glz::meta<xz_t>
{
   using T = xz_t;
   static constexpr auto value = object("x", &T::x, "z", &T::z);
};

suite metaobject_variant_auto_deduction = [] {
   "metaobject_variant_auto_deduction"_test = [] {
      std::variant<xy_t, yz_t, xz_t> var{};

      std::string b = R"({"y":1,"z":2})";
      expect(glz::read_json(var, b) == glz::error_code::none);
      expect(std::holds_alternative<yz_t>(var));
      expect(std::get<yz_t>(var).y == 1);
      expect(std::get<yz_t>(var).z == 2);

      b = R"({"x":5,"y":7})";
      expect(glz::read_json(var, b) == glz::error_code::none);
      expect(std::holds_alternative<xy_t>(var));
      expect(std::get<xy_t>(var).x == 5);
      expect(std::get<xy_t>(var).y == 7);

      b = R"({"z":3,"x":4})";
      expect(glz::read_json(var, b) == glz::error_code::none);
      expect(std::holds_alternative<xz_t>(var));
      expect(std::get<xz_t>(var).z == 3);
      expect(std::get<xz_t>(var).x == 4);
   };
};

Auto deduction works if the type can be determined by the combination of keys present. If you need to deduce the type based on the value associated with a key you can use the new tagged union support that now allows for custom tags instead of just "type" and the ids can be overridden from the default of glz::name_v of the type.
Tagged union types example:
struct put_action
{
   std::map<std::string, int> data{};
};

template <>
struct glz::meta<put_action>
{
   using T = put_action;
   static constexpr auto value = object("data", &T::data);
};

struct delete_action
{
   std::string data{};
};

template <>
struct glz::meta<delete_action>
{
   using T = delete_action;
   static constexpr auto value = object("data", &T::data);
};

using tagged_variant = std::variant<put_action, delete_action>;

template <>
struct glz::meta<tagged_variant>
{
   static constexpr std::string_view tag = "action";
   static constexpr auto ids = std::array{"PUT", "DELETE"}; //Defaults to glz::name_v of the type is ids is not supplied
};

suite tagged_variant_tests = [] {
   "tagged_variant_write_tests"_test = [] {
      // custom tagged discriminator ids
      tagged_variant var = delete_action{{"the_internet"}};
      std::string s{};
      glz::write_json(var, s);
      expect(s == R"({"action":"DELETE","data":"the_internet"})");
      s.clear();
   };

   "tagged_variant_read_tests"_test = [] {
      tagged_variant var{};
      expect(glz::read_json(var, R"({"action":"DELETE","data":"the_internet"})") == glz::error_code::none);
      expect(std::get<delete_action>(var).data == "the_internet");
   };
};

These two approaches should handle most use cases of determining the type of a json object at runtime. And they also work if the type of some item nested in a json object needs to be deduced. If someone runs into a real world case where this is insufficient they can open up a new issue and we will see what we can do.
There are some things I could've added but Id rather not bloat the options so Ill wait to see if anyone actually stuff first before implementing it. Worst case we can add an option that loops through and trys all potential types in the variant to handle more complicated cases but due to the performance of such an approach I would never enable such a thing by default. Right now we error out if there are multiple types that match but we could also add an option for reading into the first matching type in the variant. Also right now the ids are limited to strings but they could easily be any value provided we can constexpr hash them, due to std::hash not being constexpr. In the short term we will most likely keep it to strings and supporting any type would require the user to supply a constexpr hashing function so Id prefer to wait for std::hash to become constexpr so we don't have to support user supplied hashing functions (Its easy to add things but hard to remove them).


feat: make redis store injectable

Which problem is this PR solving?
Redis implementation of the BasicStore can now be used with the injection library
Short description of the changes

RedisBasicStore now implements the Starter and Stopper interface
Added configuration to RedisPeerManagementConfig and SmartWrapperOptions

The test is failing because of the lack of metadata about the new configs. We will finalize the config options once we have the end-to-end running


Add prompt for alternative library option when choosing existing planet options

As we discussed, possible scenarios including:

Use the data found in the new location
Use the data in the existing location to overwrite
Merge the data found in the existing and the new locations
Cancel, do nothing


The benchmark test encountered a problem

Issue
dirname: 2024-08-05-18-58-25--test2
test_cases: 27
model: ourModel
edit_format: whole
commit_hash: c45688c-dirty
pass_rate_1: 25.9
pass_rate_2: 33.3
percent_cases_well_formed: 100.0
error_outputs: 10
num_malformed_responses: 0
num_with_malformed_responses: 0
user_asks: 9
lazy_comments: 0
syntax_errors: 0
indentation_errors: 0
exhausted_context_windows: 0
test_timeouts: 2
command: aider --model ourModel
date: 2024-08-05
versions: 0.47.2-dev
seconds_per_case: 173.1
total_cost: 0.9951
The status will be printed all the time during the test. I found that sometimes the values error_outputs: 10 user_asks: 9 will increase. The model I use is my own local model, which is written in the form of API in imitation of the format of OpenAI GPT. Under what circumstances will these two values increase? What does it mean?
Thank you for your help, looking forward to your answer!
Version and model info
No response

Thanks for trying aider and filing this issue.
You would have to check the logs for your benchmark, and the source code for the benchmarking tool to really figure out what triggered those counters to increment. They go up if aider outputs error messages (in red) or asks the "user" a question.

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


Doc job is failing

The robotiq document job is failing, see here.  The problem appears to be due to a faulty catkin_package delcaration, see here.
python-pymodbus is not a catkin package.  It should probably moved under a regular DEPENDS.  This might fix the doc job.  I'm not sure if python-pymodbus is a standard library, so it may still cause issues.

I just run into the same problem on the new build farm. The problem is the requires entry in the setup.py file of the robotiq_modbus_rtu package: https://github.com/ros-industrial/robotiq/blob/0fc9203ff93a39880446234bcf1dfd7eaff00a0b/robotiq_modbus_rtu/setup.py#L10
I guess removing that line is the correct solution.

@dirk-thomas: removing the python- prefix should also work (see #22)?

I am not sure why to keep the require entry since the setup.py file of catkin packages is commonly not supposed to be invoked directly.
But yes, I assume removing the prefix should make it work.

Seems like all doc jobs have run to completion now. Version rocker on the wiki pages is missing only the groovy button, but since the groovy buildfarm is gone, the doc jobs aren't run anymore for that distro.

Thanks for that!
2015-05-27 2:57 GMT-04:00 G.A. vd. Hoorn<EMAIL_ADDRESS>
Seems like all doc jobs have run to completion now. Version rocker on the
wiki pages is missing only the groovy button, but since the groovy
buildfarm is gone, the doc jobs aren't run anymore for that distro.
—
Reply to this email directly or view it on GitHub
https://github.com/ros-industrial/robotiq/issues/10#issuecomment-105782539
.

--
*Nicolas Lauzier, ing., *Eng., Ph. D.
Chargé de projet / Project Manager
1-888-ROBOTIQ (762-6847) ext. 206
<EMAIL_ADDRESS>robotiq.com
blog.robotiq.com
Follow us on / Suivez-nous sur
http://www.facebook.com/pages/Robotiq/122478611152517
https://plus.google.com/u/0/b/100363269019698451101/100363269019698451101/posts
http://www.linkedin.com/company/1695451?goback=.fcs_GLHD_robotiq_false_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&trk=ncsrch_hits
https://twitter.com/?lang=en&logged_out=1#!/SamBouchard
http://www.youtube.com/user/RobotiqTV


Amplify Web App Device based Defect

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Describe the bug
1.Successful login to AWS.Amplify.Console
2.Successful Upload of all Web site files as "Archive.zip"
3.Mobile devices (phones/tablets) display all web pages including a latest new HTML page
4.Desktop/laptop displays all web pages except latest new HTML page
Expected behavior
1.Successful login to AWS.Amplify.Console
2.Successful Upload of all Web site files as "Archive.zip"
3.Mobile devices (phones/tablets) display all web pages including a latest new HTML page
4.Desktop/laptop displays all web pages except latest new HTML page
Reproduction steps

Login AWS.Amplify.Console-> Successful
Upload web files -> Successful
Test launch https://otso.com.au/rmc.html
Error:
"AccessDeniedAccess DeniedQ54A6AZR4TSGHV0AvGFeNxCJupUSGcwgQVuEXTF3YCsdlaBvxzihpOpVIKrQh90raUUxlImWKt91klSB1ADLYgHx9qo="

Build Settings
No response
Additional information
Issue relates to Amplify Mobile web display function:
Phone devices with web browser -> OK
Tablet devices with web browser -> OK
Desktop/laptop with web browser -> NOK

Yes, HTML Error occurs on Type I devices - Desktop/Laptops only
AccessDeniedAccess Denied3560W8VRWKTHTNHEPUA0zcXPqOc3ED1MtHFnursQL+3AgydAwD7FSqqjIJyZz5r8McPKu+7MddrHkWsYCxK+HE96TYg=
Type II - Mobile devices phones/tablets are ok.
Please test:
https://otso.com.au/rmc.html https://otso.com.au/rmc.html
Kind regards,
Robert Basford, CPEng
M. 0431 623 347
North Bondi  NSW  2026
About me  otso.com.au http://otso.com.au/
https://otso.com.au/card.html https://otso.com.au/card.html

On 21. Apr 2021, at 04:00, Gary Lee @.***> wrote:
Do you still have the issue? I can visit the link
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-console/issues/1760#issuecomment-823486715, or unsubscribe https://github.com/notifications/unsubscribe-auth/AODQ4L73OE7C7PDENC4K45LTJW6NTANCNFSM43G4UPPQ.

Do you still have the issue? I can visit the link

22.04.2021 Yes, please replicate issue by visiting https://otso.com.au/rmc.html using a Desktop/laptop.  Next try with mobile phone/tablet which seems to work OK.
22.04.2021 Deployed otso.com.au  again, issue displaying page on Desktops/laptops persists.  The HTML page in question is only 8009 bytes and defect free.   On Desktops/laptop other HTML pages load ok including https://otso.com.au/aus.html which is very similar to the issue page https://otso.com.au/rmc.html

Just checked Desktop/laptops now display page with no errors. Thank you for whatever was done.

Just checked Desktop/laptops now display page with no errors. Thank you for whatever was done.


Clean up Field class and KarelWorld implementations

Remove inheritance pattern in Field, favor composition instead.
Move most implementations from loops to streams in KarelWorld
Rename entities -> fields
The first dimension of fields now corresponds to the y axis, the second to the x axis.

Tested with some sample code and test cases. Seems to be working properly.


Battery Actual showing too high

My battery got to 100% today which should be 2x2.88kwh but it was showing 9.2kwh on the chart.
I've attached a few screenshots of the graph and settings to see if I'm doing anything wrong.

There's a hardcoded battery capacity variable within the apex charts yaml :)

Doh!!!!!
On Wed, 8 Mar 2023 at 20:06, Nathan Marlor @.***> wrote:

There's a hardcoded battery capacity variable within the apex charts yaml
:)
—
Reply to this email directly, view it on GitHub
https://github.com/nathanmarlor/foxess_em/issues/206#issuecomment-1460797882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5PC2HPF6L3TSC6C2HTFYTW3DRELANCNFSM6AAAAAAVUFYGSM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Make noarch: python, fix license and add myself as maintainer

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi @conda-forge/paramiko
Could some please review this PR?
Thanks!

@tschoonj , sorry for the delay.


Fix/email validation

add the validation email feature using the following posts as reference:
https://help.returnpath.com/hc/en-us/articles/220560587-What-are-the-rules-for-email-address-syntax-
https://stackoverflow.com/questions/2049502/what-characters-are-allowed-in-an-email-address

@hyanmandian @fxamauri

Sorry the delay


IA-1644: standardize grid container spacing in filters

Explain what problem this PR is resolving
Fix spacing inconsistency through the app
Self proof reading checklist

[x] Did I use eslint and black formatters
[x] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] Did I add translations
[ ] My migrations file are included
[ ] Are there enough tests

Changes

Reducing space between filters grid, switch from spacing=4 to spacing=2
Uniformize space around main components

How to test
Go through the entire app and make sure spacing between columns is set to 2 (16px)
Print screen / video

I'm closing this PR, merged it in https://github.com/BLSQ/iaso/pull/218


Docker GPU breaking VK build

Short Description of the issue
@Bianco95 test the whole make build before PR next time :) Let's try to get this fixed ASAP.

Environment

Operating System:
Other related components versions:

Steps to reproduce

Logs, stacktrace, or other symptoms

output

Summary of proposed changes

maybe it's enough to try this to go.mod:
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.19.0

Temporary fix with #194 , please take a look if docker sidecar still compiling

looks like not: https://github.com/interTwin-eu/interLink/actions/runs/8479439513/job/23233440482#step:5:61


lua_runonce: add kwargs to be passed to Lua script

This PR also addresses several points about benchmark_png.

benchmark_png: add timeout kwarg

benchmark_png: fix Lua script to use get_perf_stats

benchmark_png: use splash.args to pass in arguments

thanks!