Silently rescuing exception

It seems like osc-ruby is silently rescuing exception inside the message handlers.
 My most base example was to take the example code and add raise my own exception:
require 'rubygems'
require 'osc-ruby'
require 'osc-ruby/em_server'

@server = OSC::EMServer.new( 3333 )
@client = OSC::Client.new( 'localhost', 3333 )

@server.add_method '/greeting' do | message |
  puts "#{message.ip_address}:#{message.ip_port} -- #{message.address} -- #{message.to_a}"
  raise Exception.new "This is an exception"
end

Thread.new do
  @server.run
end

@client.send( OSC::Message.new( "/greeting" , "hullo!" ))

sleep( 3 )```

And I get nothing.

Since there's no rescue blocks in the em_server file, I'm wondering if there's something in event machine or how I'm using event machine that's responsible for this.
I'll check into that in my next free block of time.

I can confirm I'm seeing this.  There's something in eventmachine channel that's swallowing the exceptions.  I'll update when I figure something out.

Yeah, eventmachine is swallowing the exceptions.  There is some way to get the error messages out.  I'll first work on exposing those error messages, and then maybe see if i can reconstitute them back into "real" exceptions.

I've fixed this in the 1.1.4 version of the gem


Stuck on "Writing your app name in the sand" when generating a new app

What's going on?
When I try to generate a new app the ignite command gets stuck at the last step ("Writing your app name in the sand") - I never get back to the bash prompt.

Steps to reproduce

npx ignite-cli new PizzaApp
Wait until your patience runs out (in my case around 25 minutes).

No patch files found

✔ Solidarity checks valid
Jetifier found 1263 file(s) to forward-jetify. Using 16 workers...
Installing unimodules:
<EMAIL_ADDRESS>from ../node_modules/expo-constants/ios
<EMAIL_ADDRESS>from ../node_modules/expo-file-system/ios
<EMAIL_ADDRESS>from ../node_modules/expo-image-loader/ios
<EMAIL_ADDRESS>from ../node_modules/expo-localization/ios
<EMAIL_ADDRESS>from ../node_modules/expo-permissions/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-app-loader/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-barcode-scanner-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-camera-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-constants-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/core/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-face-detector-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-file-system-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-font-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-image-loader-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-permissions-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/react-native-adapter/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-sensors-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-task-manager-interface/ios

Auto-linking React Native modules for target `PizzaApp`: RNCAsyncStorage, RNCMaskedView, RNGestureHandler, RNKeychain, RNScreens, and react-native-safe-area-context
Analyzing dependencies
Downloading dependencies
Generating Pods project
Integrating client project
Pod installation complete! There are 73 dependencies from the Podfile and 64 total pods installed.

[!] Your project does not explicitly specify the CocoaPods master specs repo. Since CDN is now used as the default, you may safely remove it from your repos directory via `pod repo remove master`. To suppress this warning please add `warn_for_unused_master_specs_repo => false` to your Podfile.
✨  Done in 14.78s.

ignite doctor results:
System
  platform           darwin

  arch               x64
  cpu                16 cores                                  Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  directory          /Users/daniel/projects/_test/IgniteExpo

JavaScript
  node               12.13.0      /Users/daniel/.nvm/versions/node/v12.13.0/bin/node
  npm                7.15.1       /Users/daniel/.nvm/versions/node/v12.13.0/bin/npm
  yarn               1.22.10      /usr/local/bin/yarn

React Native
  react-native-cli   2.0.1
  app rn version     0.63.2

Ignite
  ignite-cli         3.1.6        /usr/local/bin/ignite

Android
  java               12.0.2       /usr/bin/java
  android home       -            /Users/daniel/Library/Android/sdk

iOS
  xcode              12.5.1

@daniel First off, congrats on getting daniel as your Github username. Secondly, can you run it with --debug and post the results? (it'll be pretty verbose, but the primary thing I'm looking for is any errors toward the end of the output).

@jamonholmgren Thanks, I was a beta tester 😄.
 Using 16 workers...

    ⠹ Unboxing NPM dependencies Installing unimodules:
<EMAIL_ADDRESS>from ../node_modules/expo-constants/ios
<EMAIL_ADDRESS>from ../node_modules/expo-file-system/ios
<EMAIL_ADDRESS>from ../node_modules/expo-image-loader/ios
<EMAIL_ADDRESS>from ../node_modules/expo-localization/ios
<EMAIL_ADDRESS>from ../node_modules/expo-permissions/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-app-loader/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-barcode-scanner-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-camera-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-constants-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/core/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-face-detector-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-file-system-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-font-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-image-loader-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-permissions-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/react-native-adapter/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-sensors-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-task-manager-interface/ios

    ⠧ Unboxing NPM dependencies Auto-linking React Native modules for target `HelloWorld`: RNCAsyncStorage, RNCMaskedView, RNGestureHandler, RNKeychain, RNScreens, and react-native-safe-area-context
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`

    ⠇ Unboxing NPM dependencies Fetching podspec for `RCT-Folly` from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`

    ⠋ Unboxing NPM dependencies Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`

    ⠦ Unboxing NPM dependencies Downloading dependencies
Installing CocoaAsyncSocket (7.6.5)
Installing DoubleConversion (1.1.6)
Installing EXConstants (9.3.5)
Installing EXFileSystem (9.3.0)
Installing EXImageLoader (1.3.0)
Installing EXLocalization (9.1.0)
Installing EXPermissions (10.0.0)
Installing FBLazyVector (0.64.2)
Installing FBReactNativeSpec (0.64.2)

    ⠹ Unboxing NPM dependencies Installing Flipper (0.75.1)
Installing Flipper-DoubleConversion (1.1.7)
Installing Flipper-Folly (2.5.3)
Installing Flipper-Glog (0.3.6)
Installing Flipper-PeerTalk (0.0.4)
Installing Flipper-RSocket (1.3.1)
Installing FlipperKit (0.75.1)
Installing OpenSSL-Universal (1.1.180)
Installing RCT-Folly (2<IP_ADDRESS>)
Installing RCTRequired (0.64.2)
Installing RCTTypeSafety (0.64.2)
Installing RNCAsyncStorage (1.15.5)
Installing RNCMaskedView (0.1.10)
Installing RNGestureHandler (1.10.3)
Installing RNKeychain (6.2.0)
Installing RNScreens (2.18.1)
Installing React (0.64.2)
Installing React-Core (0.64.2)
Installing React-CoreModules (0.64.2)
Installing React-RCTActionSheet (0.64.2)
Installing React-RCTAnimation (0.64.2)
Installing React-RCTBlob (0.64.2)
Installing React-RCTImage (0.64.2)
Installing React-RCTLinking (0.64.2)
Installing React-RCTNetwork (0.64.2)
Installing React-RCTSettings (0.64.2)
Installing React-RCTText (0.64.2)
Installing React-RCTVibration (0.64.2)
Installing React-callinvoker (0.64.2)
Installing React-cxxreact (0.64.2)
Installing React-jsi (0.64.2)
Installing React-jsiexecutor (0.64.2)
Installing React-jsinspector (0.64.2)
Installing React-perflogger (0.64.2)
Installing React-runtimeexecutor (0.64.2)
Installing ReactCommon (0.64.2)
Installing UMAppLoader (1.4.0)
Installing UMBarCodeScannerInterface (5.4.0)
Installing UMCameraInterface (5.4.0)
Installing UMConstantsInterface (5.4.0)
Installing UMCore (6.0.0)
Installing UMFaceDetectorInterface (5.4.0)
Installing UMFileSystemInterface (5.4.0)
Installing UMFontInterface (5.4.0)
Installing UMImageLoaderInterface (5.4.0)
Installing UMPermissionsInterface (5.4.0)
Installing UMReactNativeAdapter (5.7.0)
Installing UMSensorsInterface (5.4.0)
Installing UMTaskManagerInterface (5.4.0)
Installing Yoga (1.14.0)
Installing YogaKit (1.18.1)
Installing boost-for-react-native (1.63.0)
Installing glog (0.3.5)
Installing libevent (2.1.12)
Installing react-native-safe-area-context (3.1.8)
Generating Pods project

    ⠋ Unboxing NPM dependencies Integrating client project

 Pod installation complete! There are 73 dependencies from the Podfile and 64 total pods installed.

    🧶 Unboxing NPM dependencies
    ⠴ Baking CocoaPods Scanning for pods...

    ⠦ Baking CocoaPods 1.10.1

 > pod install

    ⠦ Baking CocoaPods Installing unimodules:
<EMAIL_ADDRESS>from ../node_modules/expo-constants/ios
<EMAIL_ADDRESS>from ../node_modules/expo-file-system/ios
<EMAIL_ADDRESS>from ../node_modules/expo-image-loader/ios
<EMAIL_ADDRESS>from ../node_modules/expo-localization/ios
<EMAIL_ADDRESS>from ../node_modules/expo-permissions/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-app-loader/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-barcode-scanner-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-camera-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-constants-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/core/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-face-detector-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-file-system-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-font-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-image-loader-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-permissions-interface/ios
<EMAIL_ADDRESS>from ../node_modules/@unimodules/react-native-adapter/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-sensors-interface/ios
<EMAIL_ADDRESS>from ../node_modules/unimodules-task-manager-interface/ios

    ⠏ Baking CocoaPods Auto-linking React Native modules for target `HelloWorld`: RNCAsyncStorage, RNCMaskedView, RNGestureHandler, RNKeychain, RNScreens, and react-native-safe-area-context
Analyzing dependencies

    ⠧ Baking CocoaPods Downloading dependencies
Generating Pods project

    ⠼ Baking CocoaPods Integrating client project

 Pod installation complete! There are 73 dependencies from the Podfile and 64 total pods installed.

    ☕ Baking CocoaPods
    ⠦  Writing your app name in the sand /ios/PizzaApp RENAMED

 Ignore above error if this file doesn't exist

 Ignore above error if this file doesn't exist

 /ios/PizzaApp.xcodeproj RENAMED

 Ignore above error if this file doesn't exist

 /ios/PizzaApp.xcodeproj/xcshareddata/xcschemes/PizzaApp.xcscheme RENAMED

 /ios/PizzaAppTests RENAMED

 /ios/PizzaAppTests/PizzaAppTests.m RENAMED

 /ios/PizzaApp.xcworkspace RENAMED

 Ignore above error if this file doesn't exist

 Ignore above error if this file doesn't exist

 /android/app/src/main/res/values/strings.xml MODIFIED

 /index.js MODIFIED

 /ios/PizzaApp/Info.plist MODIFIED

 /package.json MODIFIED

 /app.json MODIFIED

    ⠸  Writing your app name in the sand /ios/PizzaApp.xcodeproj/project.pbxproj MODIFIED

    ⠦  Writing your app name in the sand /ios/PizzaApp.xcworkspace/contents.xcworkspacedata MODIFIED

    ⠙  Writing your app name in the sand /ios/PizzaApp.xcodeproj/xcshareddata/xcschemes/PizzaApp.xcscheme MODIFIED

    ⠸  Writing your app name in the sand /ios/PizzaApp/AppDelegate.m MODIFIED

    ⠦  Writing your app name in the sand /android/settings.gradle MODIFIED

    ⠇  Writing your app name in the sand /ios/PizzaAppTests/PizzaAppTests.m MODIFIED

    ⠸  Writing your app name in the sand /ios/Podfile MODIFIED

    ⠴  Writing your app name in the sand /app.json MODIFIED

 android/app/src/main/java/com/helloworld BUNDLE IDENTIFIER CHANGED

 /android/app/src/main/AndroidManifest.xml MODIFIED

 /android/app/BUCK MODIFIED

 /android/app/build.gradle MODIFIED

    ⠦  Writing your app name in the sand /android/app/src/main/java/com/helloworld/MainActivity.java MODIFIED

 /android/app/src/main/java/com/helloworld/MainApplication.java MODIFIED

 /android/app/src/main/java/com/helloworld/MainActivity.java MODIFIED

 android/app/src/debug/java/com/helloworld BUNDLE IDENTIFIER CHANGED

 /android/app/src/main/AndroidManifest.xml MODIFIED

 /android/app/BUCK MODIFIED

 /android/app/build.gradle MODIFIED

 /android/app/src/debug/java/com/helloworld/ReactNativeFlipper.java MODIFIED

 Done removing builds.

 APP SUCCESSFULLY RENAMED TO "PizzaApp"! 🎉 🎉 🎉

 Podfile has been modified, please run "pod install" inside ios directory.

 Please make sure to run "watchman watch-del-all" and "npm start --reset-cache" before running the app.

    🏝  Writing your app name in the sand

I can start the app after running yarn, so it might be that the only problem is that the process doesn't exit properly.

Hi @daniel - is this still an issue for you when using the latest version of ignite?

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.


[Feature Request] Run local strap script after installing Brewfile

Hi,
Similar to the laptop script, it would be nice to be able to run a local ~/.strap.local script or perhaps even a script in the USER/homebrew-brewfile or USER/dotfiles repo.
if [ -f "$HOME/.strap.local" ]; then
  . "$HOME/.strap.local"
fi

Essentially my entire setup at the moment is:

run strap
install Brewfile
run a script to configure the stuff installed from Brewfile (rbenv, bundler, pyenv, node, bashrc, zshrc, etc.)

This would make the 3rd step a bit easier. If its not within the scope of the project there are several other ways I can achieve this so let me know.

My main problem with this workflow: how does .strap.local get there on first system bootstrap?

My main problem with this workflow: how does .strap.local get there on first system bootstrap?

Any ideas on this? Closing this out until this is fleshed out.

@mikemcquaid revisiting this idea again. I just set up my homebrew-brewfile repository and its working swimmingly. The only thing left is to run a script to set up rbenv, bundler, heroku, etc.
I'm very much digging this separation between (boot)strapping one's laptop and setting up dotfiles, since dotfiles can be extremely custom and personal.
Similar to how you fetch the user's Brewfile from Github, I think it makes sense to fetch the user's .strap.local from Github.

Check if a Github user has a dotfiles repository. Clone the repository in ~ (and pull changes?).
Check if the dotfiles repo has a .strap.local file in it. Symlink to ~.
If ~/.strap.local exists, run the file.

Now the user can setup their dotfiles right from the ~/.strap.local script if they choose. The only assumption being made is that the user will want to clone their dotfiles into ~ which seems like a reasonable assumption. If they have their own procedure for setting up dotfiles they can still go about doing that.
Thoughts?

@AlJohri I think the problem with dotfiles is that I don't think you can assume people want Strap to clone it or where they'd want it installed. I think that's something that's better living in another way or being a default-off configurable option.

Is there a recommended way to kick off an arbitrary script from Strap? I'd like to be able to install dotfiles and take care of other config.

I could write a script and have it run strap and then do the things I want, but I haven't been able to figure out a way to avoid authenticating multiple times.
I feel like it'd be nice to have two places to hook in, once at the beginning of the strap run (to put things like .Brewfile into place) and once at the end to set up dotfiles and configure things that depend on strap already having been run (like setting the default shell).

There is not beyond the Brewfile hooks. My main design opposition to adding them is how they are run on first system install. Strap should be the first thing that's run when you open a Terminal on a new system so any hooks would need a way that's standardised per-org rather than per-user to know what to do on a new install. I'm open to ideas to doing that, though? Perhaps a strap-config repository or something on the user account?

My main design opposition to adding them is how they are run on first system install.

I totally agree with this.

Perhaps a strap-config repository or something on the user account?

I'd rather not have another repository, maybe a recommended way to call strap from another script? Here's what I'm currently doing (source):
bash <(curl -s https://raw.githubusercontent.com/johndbritton/dotfiles/master/script/setup)

The only thing I'm not able to accomplish with this setup right now is prompting for the sudo password up front. If I pre-auth in my script like strap does and then call strap, I'm still prompted for my password a second time.
What do you think about my approach of wrapping strap? Any recommendation to get around the need to enter my password multiple times?

I'd rather not have another repository, maybe a recommended way to call strap from another script? Here's what I'm currently doing (source):
bash <(curl -s https://raw.githubusercontent.com/johndbritton/dotfiles/master/script/setup)

That approach makes me uneasy without any sort of checksum validation. I'm wondering if dotfiles is a sufficiently standard name to use? If so, maybe we just clone it somewhere?

If I pre-auth in my script like strap does and then call strap, I'm still prompted for my password a second time.

You probably need to remove sudo -k which forces sudo to re-ask for the password.

I'm wondering if dotfiles is a sufficiently standard name to use?

What about having a default repository name (dotfiles) with a default command to run script/setup and accepting an argument or ENV variable in strap to override?
bin/strap.sh would run strap and then, if the user has a dotfiles repo it will clone it and run script/setup
DOTFILES_REPO=foo/bar DOTFILES_SETUP=bin/setup.sh bin/strap.sh would configure the entry point via env.
bin/strap.sh --dotfiles-repo=foo/bar --dotfiles/setup=bin/setup.sh would do the same via command line arguments.
This gives the user the ability to set up any repo they want and run a script in that repo after strap finishes.


Prices are not updating on Europe

I am currently trying to retreive prices from https://europe.albion-online-data.com/api/v2/stats/prices and update them using the albion data client, but the prices are not updating despite the logs indicating that the prices were sent.
Here is a screenshot of the game screen and logs

Response from https://europe.albion-online-data.com/api/v2/stats/prices/T4_METALBAR.xml?locations=Thetford
<MarketResponse>
<ItemTypeId>T4_METALBAR</ItemTypeId>
<City>Thetford</City>
<QualityLevel>1</QualityLevel>
<SellPriceMin>0</SellPriceMin>
<SellPriceMinDate>0001-01-01T00:00:00</SellPriceMinDate>
<SellPriceMax>0</SellPriceMax>
<SellPriceMaxDate>0001-01-01T00:00:00</SellPriceMaxDate>
<BuyPriceMin>0</BuyPriceMin>
<BuyPriceMinDate>0001-01-01T00:00:00</BuyPriceMinDate>
<BuyPriceMax>0</BuyPriceMax>
<BuyPriceMaxDate>0001-01-01T00:00:00</BuyPriceMaxDate>
</MarketResponse>
</ArrayOfMarketResponse>

Am I doing something wrong?

You're hitting the wrong API. In the screenshot, it says it's updating average stats, which is history. If you goto https://europe.albion-online-data.com/api/v2/stats/history/T4_METALBAR.xml, there's data there. Right now, it seems most people are blocked/encrypted for the prices api which shows "Sending X market offers to ingest" (picture attached).

As far as I understand, the problem is known and will be fixed?

No, there's no problem and nothing to be fixed. Blocked/encrypted data is something SBI did a few months back. There's nothing we can do to fix that.
There's some magic combination of data points about your account/toon that disables encryption and allows live prices to flow again. Not sure if you're on the AODP Discord or not, but there's explanations there. The AODP website needs to be updated to have some of that data, but most people end up asking about it in Discord.


resource.id evaluates wrong in the FHIRpath-Engine

Describe the bug
After getting a resource from a (hapi) FHIR Server: Resource.getId() returns the fullUrl of a Resource instead of the id.
This leads to an error in fhirpath expressions like: "id = '123'" as id in the Fhirpathengine evaluates to the fullUrl.
To Reproduce
    FhirContext fhirContext = FhirContext.forR4();
    IFhirPath fhirPath = new FhirPathR4(fhirContext);

    IGenericClient client = fhirContext.newRestfulGenericClient("http://hapi.fhir.org/baseR4");
    String id = "1683059";

    Patient patient = client.read().resource(Patient.class).withId(id).execute();

    Optional<Base> evaluate = fhirPath.evaluateFirst(patient, "id = '" + id + "'", Base.class);
    System.out.println(evaluate.get());

Expected behavior
FhirPath evaluates to true & Resource.getId() only returns a ID value.
Environment:

HAPI FHIR Version 5.4.1

Did some further analysis. It seems that the hapi client ignores the returned id, and replaces this with the content of the Content-Location header.


Extend bpf verifier tests to test socket programs

This PR makes various cleanups in the test/bpf/verifier-test.sh script, adds a new tool tools/maptool for creating sockmap and eppolicymap map times from a simple CLI, and finally adds support for loading the socket-level BPF programs into the verifier test script.
The PR is spread out across several commits to allow review commit-by-commit.

This change is

test-me-please

Coverage decreased (-0.06%) to 45.468% when pulling ad51487ed3ae6671e7160816ec2ec49cffefdaf1 on joestringer:submit/verify-cg-progs into 8d290d31e187ca83d3acfbc8ac237527225c914c on cilium:master.

test-me-please

test-me-please

test-me-please


Default Task name does not match the installer default

The installer asks for a task name and by default uses “Manually triggered reload of Metrics Library”   However in the QMC, when you go to create a task the default is "Reload task of Metrics Library".  We should change the installer to match the QMC default or at least update the installation docs to have a note in case a user runs through the installer quickly.

This has been updated in the documentation to reflect the new auto naming of tasks.  Reload Metrics Library.


Replay Observer Documentation

Further documentation for the replay observation example.
Includes IgnoreReplay usage with examples on how to filter replays based on the map, the mrr of the players as well as the match up. General comments were added, and goes through how to process multiple replays simultaneously.

I'm going to close this since there has been no update for a couple months now.


Could not connect to elasticsearch

Using the example in the README gives a 500:
curl "http://npmsearch.com/query?q=dom&fields=name"
> Could not connect to elasticsearch

Hey, sorry for the delay! This has been fixed (76176e8032931b6998e79656eaa649ec69ace475) and deployed.
Feel free to re-open this if the problem persists.


Copy Suggestion

There is a typo in the Server-Side Projection section

The following example is retrieves just the Email property ...

appears to have been intended to read

The following example retrieves just the Email property ...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cbd87ab1-9a5b-4d23-05ce-d9d5f5bb74a0
Version Independent ID: 0bf2b20a-1830-02e5-67bd-a05074a7236b
Content: Azure storage table design patterns
Content Source: articles/storage/tables/table-storage-design-patterns.md
Service: storage
Sub-service: tables
GitHub Login: @tamram
Microsoft Alias: tamram

@hobozero Thank you for catching this . We will review this and update the thread.

@hobozero We have updated the document and it will be live once the pull request is reviewed and approved by the team.


This change is

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@regedit32 Thansk for reviewing! i will just close and reopen this to kick of the tests again since it was a while since this PR was sent in (want to know if dev branch will fail so we can resolve it).

Test passing perfectly today too! Awesome. Merging this.


Can't configure vulture min_confidence in pyproject.toml

Vulture option under [tool.pylama.linter.vulture] as min_confidence
The following pyproject.toml that has the min-confidence configuration option specified with hyphens as underscores:
[tool.pylama.linter.vulture]
min_confidence = 80

causes the following output/error when pylama is run:
usage: vulture [options] [PATH ...]
vulture: error: unrecognized arguments: --min_confidence=80

Vulture option under [tool.pylama.linter.vulture] as min-confidence
Running instead with with min-confidence as-is appears to show the correct output but is not shown in VSCode (not sure why):
[tool.pylama.linter.vulture]
min-confidence = 80

output:
src/main/helpers.py:10:1 V104 unused import 'Min' (90% confidence) [vulture]
src/main/helpers.py:10:1 V104 unused import 'Q' (90% confidence) [vulture]
src/main/helpers.py:11:1 C0411 standard import "from typing import Union" should be placed before "from django.db.models import Q, Min" [pylint]
src/main/helpers.py:12:1 W0611 'datetime.date' imported but unused [pyflakes]
src/main/helpers.py:12:1 C0411 standard import "from datetime import date, datetime" should be placed before "from django.db.models import Q, Min" [pylint]
src/main/helpers.py:12:1 V104 unused import 'date' (90% confidence) [vulture]
src/main/helpers.py:12:1 V104 unused import 'datetime' (90% confidence) [vulture]
...

Vulture option specified under [tool.vulture] as min_confidence
Running under [tool.vulture] with underscores half works as above, producing output but not registering in VSCode
[tool.vulture]
min_confidence = 80

Vulture option specified under [tool.vulture] as min-confidence
Running under [tool.vulture] with hyphen produces an error
[tool.vulture]
min_confidence = 80

output:
Unknown configuration key: min-confidence

I'm not sure if I'm doing something wrong or have missed some trick, any advice appreciated.

Interestingly adjusting the Pylama args in VSCode to include --vulture-min-confidence 80 doesn't stop pylama from working correctly but also doesn't change the output (i.e. I still have warnings with confidence under 80%).
The full command that is run during this is: ~/.virtualenvs/<project-name>/bin/python ~/.vscode-server/extensions/ms-python.python-2023.8.0/pythonFiles/linter.py -m pylama "--vulture-min-confidence 80" ./src/main/helpers.py


support group_concat aggregation

I have two tables Cards and CardLabels, I want to select all cards and labels associated to it.
The SQL query will be like this:
SELECT card.*,  GROUP_CONCAT(label.title , ',') AS labels   FROM Cards card JOIN CardLabels label  ON card.number = label.number  GROUP BY card.number
I wonder how to do  GROUP_CONCAT and write this query with Swift.

Did you ever find a solution to this?

https://sqlite.org/lang_aggfunc.html#group_concat


other: databuilder support neo4j v4.x

Signed-off-by: JacobSMoller<EMAIL_ADDRESS>Summary of Changes
changes:

env var to signal setup that we would like neo4j v4 package.
conditional import of v3 or v4 neoj4 package in neo4j extractor, publisher and stale data task.

Tests
No tests yet. I think these changes might need a bit of discussion/input from someone with more experience in this project, before they are fully ready.
tests are passing, but they also only install v3 neo4j, so theres work to do here,  but would love some input on how to do it :)
Documentation
No docs yet. I think these changes might need a bit of discussion/input from someone with more experience in this project, before they are fully ready.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test

This a first try at some neo4j v4.x compatibility, based of: https://github.com/amundsen-io/amundsendatabuilder/compare/master...brexhq:minsu--test-for-4 and https://amundsenworkspace.slack.com/archives/CGFBVT23V/p1609896995239100.
This can potentially also be a wont fix kind of thing, and just be here as a reference to others that would like to use neo4j v4.
But i think looking at this https://neo4j.com/developer/kb/neo4j-supported-versions/ it would be good to get a head start on upgrading.
the frontendlib comes with version 3.3 which is quite old, and even the latest v3(3.5) has end of support in 2021.
@allisonsuarez @feng-tao any input from you, or others from lyft who might have some ideas on this :) ? Would like to hear what your thoughts are.

I am +1 on the change if we could make it v3/v4 compatible.

I am +1 on the change if we could make it v3/v4 compatible.

The changes i've made should be compat. with both v3 and v4. Defaulting to v3.
I am not super happy about the env var in setup.py, but I can't seem to find a better way to make v4 dependency optional.

@feng-tao would it be possible to deprecate support for neo4j<v3.5? That would make a neo4j 3.5 and 4.x compatible version of Amundsen data builder a lot cleaner.
The current version of the neo4j 4 driver is backwards compatible with neo4j 3.5. And dropping support for neo4j 3.3 and 3.4 seems to be a reasonable idea as they has both passed their end of support date.

we have quite a few deployments (lyft including) are in neo4j 3.3. will let @allisonsuarez from Lyft to chime in as I am no longer with Lyft.

I think we should push forward to deprecate neo4j 3.3, it was released 4 years ago and isn't supported. 3.5 should be a drop-in upgrade for 3.3 users.
That said, I don't think this will land soon enough for the monorepo transition, so I've created a ticket to track https://github.com/amundsen-io/amundsen/issues/1008


Add numerical support for other real types (traffic_flow)

Continue #1909.
Tasks:

[x] traffic_flow_lwr 1d
[x] unit tests for above

Ready for review ^^


formState.isSubmitSuccessful does not behave like react-hook-form

Hey
I noticed that formState.isSubmitSuccessful always remains false
Likely #22 but very different..
Actual behaviour
isSubmitSuccessful is always false even after a successful submission
Expected behaviour
Upon submitting the form and it completing successfully isSubmitSuccessful remains true until a subsequent reset is called (like react-hook-form) (https://www.react-hook-form.com/api/useformstate/ and https://www.react-hook-form.com/api/useform/reset/)
Possible solution
I'm unsure how this would work given the action response is handled by the developer rather than this library. But thought i'd post the issue and see if you had any ideas!

@geemanjs hmm well the real puzzle here for me is is this needed because if the submit is successful the action will probably redirect you or something? But I guess if it was submitted via fetcher it would stay on same page, can you tell me your use-case so I can think about what would be the best approach in Remix world?

I think similar issue to https://github.com/Code-Forge-Net/remix-hook-form/issues/39


copr: Add vectorized BitAndSig

PCP #5751
What have you changed?
Add vectorized BitAndSig
What is the type of the changes?
Improvement. Non-vectorized BitAndSig already exists. Just add a vectorized version for better performance.
How is the PR tested?
Unit tested. Will run copr test later.
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No. It should not change the behavior.
Does this PR affect tidb-ansible?
No.

/run-integration-copr-test copr-test=pr/21

/run-integration-copr-test copr-test=pr/21

/test

/run-all-tests

/run-all-tests copr-test=pr/21

/test

/run-integration-copr-test copr-test=pr/21

/test

/run-all-tests copr-test=pr/21

/test

PTAL. I have fixed the conflict. Seems they conflict with each other. I will handle them one by one.

/run-integration-copr-test copr-test=pr/21

Related copr-test PR https://github.com/tikv/copr-test/pull/21

/merge


Default value is wrong

This is the log of adapter start:
solax.0 | 2022-04-03 08:51:38.893 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.893 | warn | Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
solax.0 | 2022-04-03 08:51:38.887 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.886 | warn | Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.883 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.883 | warn | Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.866 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.866 | warn | Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.863 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.862 | warn | Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.858 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.858 | warn | Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.853 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.853 | warn | Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.846 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.846 | warn | Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.837 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.837 | warn | Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.829 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.828 | warn | Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:34.791 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
solax.0 | 2022-04-03 08:51:34.790 | info | terminating
solax.0 | 2022-04-03 08:51:34.790 | info | Got terminate signal TERMINATE_YOURSELF
solax.0 | 2022-04-03 08:51:11.684 | warn | system settings cannot be called up. Please check configuration!
solax.0 | 2022-04-03 08:51:11.630 | info | starting. Version 0.3.7 in /opt/iobroker/node_modules/iobroker.solax, node: v14.19.1, js-controller: 4.0.21
solax.0 | 2022-04-03 08:51:11.608 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.608 | warn | Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
solax.0 | 2022-04-03 08:51:11.587 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.587 | warn | Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.583 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.583 | warn | Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.578 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.578 | warn | Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.574 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.574 | warn | Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.569 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.569 | warn | Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.566 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.566 | warn | Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.562 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.562 | warn | Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.559 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.559 | warn | Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.536 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.535 | warn | Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
host.iobroker | 2022-04-03 08:51:06.833 | error | iobroker  host.iobroker Object solax.0.info.success is invalid: Default value has  to be type "boolean" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.
host.iobroker | 2022-04-03 08:51:06.823 | error | iobroker  host.iobroker Object solax.0.history.yield_7_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.817 | error | iobroker  host.iobroker Object solax.0.history.yield_6_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.810 | error | iobroker  host.iobroker Object solax.0.history.yield_5_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.804 | error | iobroker  host.iobroker Object solax.0.history.yield_4_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.798 | error | iobroker  host.iobroker Object solax.0.history.yield_3_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.791 | error | iobroker  host.iobroker Object solax.0.history.yield_2_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.785 | error | iobroker  host.iobroker Object solax.0.history.yield_1_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.778 | error | iobroker  host.iobroker Object solax.0.suninfo.Azimut is invalid: Default value  has to be type "number" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.
host.iobroker | 2022-04-03 08:51:06.765 | error | iobroker  host.iobroker Object solax.0.suninfo.Altitude is invalid: Default value  has to be type "number" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.```

 - Adapter version: 0.3.7
 - JS-Controller version: 4.0.21
 - Node version: 14.19.1
 - Operating system: Debian 11

Fix in Version 0.4.5


Int8/Uint8 convolution support

Just for your information.
In the near two years, model quantization is becoming popular in deep learning, especially for mobile devices. The core of quantization is low-bits (usually in 8-bits) convolution, which can reduce the memory bandwidth and run-time of deep network significantly.  Many deep learning frameworks have implemented related features, e.g.,

tensorflow: https://arxiv.org/abs/1712.05877
pytorch: https://code.fb.com/ml-applications/qnnpack/
...

Do you have plan to add this feature into SimdLib?

Recently I spend main time to optimize the inference of neural network on the base of
Synet and Simd Library. Of course I know about model quantization and have corresponding plans. But these are medium term plans. In the nearest future I'm going to add support of NHWC data format (native data format for Tensorflow) to Synet and optimizations for ARM NEON.


BERT withheld set and stopping criteria

A document containing the proposal details and supporting data will be provided to the working group in the next meeting.

@googlebot I signed it!


Select Content is misaligned when using popper to position

Bug report
Current Behavior
I'm struggling to make the content align with the trigger.

Expected behavior
I expected that the content/dropdown would be left-justified with the trigger/button and that the width would be precisely the same.
Reproducible example
https://codesandbox.io/s/radix-select-alignment-issue-forked-4wk7cp?file=/src/App.js
Suggested solution
I feel like it is related to the react-remove-scroll package setting CSS props on the body of the document but not positive. I can work around it to a degree by applying margin and padding to the body like this:
https://codesandbox.io/s/radix-select-alignment-issue-workaround-jggdgc?file=/public/index.html
But that's not ideal because it doesn't work if I set the padding to 0. Having padding on the body is a pain for a single-page app.
Additional context

Thanks for the awesome library!

The Viewport doesn't have a box-sizing: border-box, making the placement calculation wrong.
As the content is close to the edges, the Select comes with a collisiondPadding of 10 by default, making it not touch the edges. If you move the trigger to the middle of the screen the collisionPadding is not applied.

https://codesandbox.io/s/radix-select-alignment-issue-forked-6dfgs5?file=/src/App.js

@joaom00 Thank you SO much for the quick response! Your tips solved my issue.


[RFE] Adding a way to auto assign role templates by cluster name.

Describe the solution you'd like
We are looking for a way to have rancher automatically assign role templates and groups to a cluster depending on the cluster name.
For example:
If a cluster is registered in rancher with "prod" in the name - the following assignments will take place:
dev group - custom read only dev cluster role template
infra group - custom read only infra cluster role template
But if it is registered with "dev" in the name then:
dev group - custom read/write role
infra group - custom read only infra cluster role template
etc.
Describe alternatives you've considered
We considered automating the process during the cluster registration.
But on occasion we need to create new roles.
In addition, it will be hard to keep assignment "rules" up to date and documented as it will be a part of the cluster creation pipeline which includes other services beside rancher.

@gasalomo-github Can you expand on what you think this might look like?

@gasalomo-github Can you expand on what you think this might look like?

Something like clusterCreatorDefault in roletemplate, but with the ability to specify which clusters it would apply to, as well as run it on existing clusters.
For Example:
apiVersion: management.cattle.io/v3
kind: RoleTemplate
builtin: false
context: cluster
displayName: readonly-custom
...
clusterBindingDefault:
    rules:
    - groupId: <group id>
      clusters: ["*-prod"] # regex for the cluster displayName
    - userId: <user id>
      clusters: ["*-prod"]
    - groupPrincipalId: <group principal id>
      clusters: ["*-prod"]

so if I have an existing cluster with the name "us-prod" or if I create one called "eu-prod"
rancher will create a role bindings on the clusters for each of those rules
but it will not apply to "us-dev"


SSH clone and/or HTTPS clone

Hi @raxod502 ,
When setting up a new computer, I like to clone my emacs dotfiles. However, if I don't have my .ssh keys setup with github, I'm unable to do a straight.el .emacs.d setup as it requires the ssh git for cloning git@github.com:username/project.git (other projects other than straight.el, e.g. projectile, magit, etc) . Naturally I should just setup ssh keys, but what if it's the scenario of you're spinning up a bunch of aws servers, and setting up ssh keys on the remote host is just a bother.
If I do an el-get .emacs.d setup it is able to proceed because it allows using an https git clone.  What do you think about putting a setting/parameter to allow https on initial git clone.
P.s. Here's also another thought, and I'm not sure how this would be done. Never really done this with git except manually. Can it be automated so that the git remote changes from using https to ssh. Manually I normally just do "git remote rm origin (some https remote)" and then "git remote add origin git@github.com:username/project.git" .

The relevant logic is in straight--vc-git-encode-url, which is what handles constructing a URL from :host and :repo for the git backend. As you can, it's hardcoded to generate SSH URLs at the moment. That can and should be changed to allow for generating HTTPS URLs by default, by the introduction of a straight-vc-git-default-protocol user option.
By default, whatever URL the repository is cloned from becomes the URL of the remote. When you use straight.el to perform bulk management of your repositories, it will interactively make sure that your remote URLs are set correctly, but by default it treats HTTPS and SSH URLs equivalently, using straight--vc-git-urls-compatible-p. People with strong opinions about HTTPS vs. SSH can be accommodated by the addition of a straight-vc-git-force-protocol user option, which would cause HTTPS and SSH URLs to be treated as non-equivalent, so they would be reset to the protocol that you specified.

Thanks @raxod502, I appreciate it.
Having it so that it so that one can bootstrap and clone one's emacs.d files and use purely https will be convenient (for the unprovisioned computer).
With regards to package development, I totally understand the ssh git@github.com:username/projectname.git default format -- I much prefer it vs https normally. Less bothersome logins to github/bitbucket, etc that the https remote occasionally prompt one for.

P.s. Out of curiosity, how would one automate changing remotes from using ssh remote to https? Both in the shell / bash and in elisp? Or https to git? If you've got the bash tool for this it would be perfect for git-extras.

Hmm… it shouldn't be terribly difficult. Firstly you can use git remote set-url instead of deleting and re-creating the remote, although it might be preferable to delete and then recreate since then you don't have to worry about out-of-date branch pointers. See straight--vc-git-validate-remote for how this is handled interactively in straight.el.
Obviously doing it for GitHub, GitLab, and Bitbucket repositories is not hard, but I do not know of a general way to translate from HTTPS to SSH. If you figured out a good heuristic, though, it's just a matter of using git remote get-url and git remote set-url.

P.s. Out of curiosity, how would one automate changing remotes from using ssh remote to https? Both in the shell / bash and in elisp? Or https to git? If you've got the bash tool for this it would be perfect for git-extras.

@agsdot Please let me know what you think of the latest version (https://github.com/raxod502/straight.el/commit/361eed5f439fcd6974f71aed66f4f6482f7cc798).

:+1: @raxod502, commit 361eed5 provides for what I asked for in the original issue, now I can clone my .emacs.d on a server without the public/private key files setup, and all the packages are cloned using https rather than ssh.
I tested setting the parameter
(setq straight-vc-git-default-protocol 'https)
and
(setq straight-vc-git-default-protocol 'ssh)
and they worked fine from a fresh install of straight.el (i.e. I blew out the straight/ directory and went for the fresh install).
How do you force for an already initialized .emacs.d with the repos already downloaded for the packages to switch remotes from the ssh to https format? Changing setq straight-vc-git-default from 'ssh to 'https back and forth on an already initialized repo didn't change/update the remotes.
Note, this is an entirely non-necessary request now, just asked out of curiosity and for convenience (I can just rm -rf the straight/ directory and let it download and build again), it would be convenient though if just for the sake of not having to clone all the repos again.
Thanks!

You can use M-x straight-normalize-all, which is provided for the express purpose of performing these kinds of normalization tasks. Note that if you want HTTPS and SSH URLs to be considered as incompatible (so that straight.el will prompt you to re-set remote URLs that are using the "wrong" protocol), you must (setq straight-vc-git-force-protocol t).
By design, you should never ever have to delete the entire straight directory: it contains all of your repositories and your version lockfiles!

It works! Thanks @raxod502 .


Move all sub-chart dependencies up to riff chart

this seems necessary for helm install to work with Helm 2.15

looks like dependency resolution has changed and doesn't recurse into dependencies

we can revisit this when/if we move to Helm 3

Fixes #69

I think the 2.14 behavior was a fluke. AFAIK there is no reliable support in Helm for recursing into dependent charts and resolving their dependencies. I've only found a few open issues that suggest adding this feature, like https://github.com/helm/helm/issues/2759


added linear search program in java

Sorry to inform but this repository has been excluded from hacktoberfest. So inorder to make your PR count towards hacktoberfest, request you to make your contribution in this repository -> https://github.com/SR-Sunny-Raj/Hacktoberfest2022-for-everyone


async getters discussed?

Curious if there's been any discussion about async getters?
AsyncMethod :
    get async PropertyName (StrictFormalParameters)  { FunctionBody }

I can see arguments both ways, but the spec currently allows you to await regular properties, so why not properties that are computed via a getter?
Just looking to start an open dialog if one hasn't already.
Some examples for reference...
Assuming this setup:
function fakeAjax() {
  return new Promise(resolve => {
    setTimeout(() => {
      resolve([new Comment(1, 'First comment')]);
    }, 2000);
  });
}

class Post {
  constructor(id, body) {
    this.id = id;
    this.body = body;
  }
}

class Comment extends Post {}

Currently supported by traceur:
class Article extends Post {
  constructor(id, body) {
    super(id, body);
    this._comments = null;
  }

  async fetchComments() {
    if (this._comments === null) {
      this._comments = await fakeAjax();
      this._comments[0].body += ' of the day';
    }

    return this._comments;
  }
}

async function main() {
  let article = new Article(123, 'Hello World');

  // Comments may or may not be loaded yet
  let comments = await article.fetchComments();

  console.assert(comments[0].body === 'First comment of the day');
}

Not currently supported by traceur or spec:
class Article extends Post {
  constructor(id, body) {
    super(id, body);
    this._comments = null;
  }

  get async comments() {
    if (this._comments === null) {
      this._comments = await fakeAjax();
      this._comments[0].body += ' of the day';
    }

    return this._comments;
  }
}

async function main() {
  let article = new Article(123, 'Hello World');

  // Comments may or may not be loaded yet
  let comments = await article.comments;

  console.assert(comments[0].body === 'First comment of the day');
}

But you can work around this spec omission by doing this:
class Article extends Post {
  constructor(id, body) {
    super(id, body);
    this._comments = null;
  }

  async _fetchComments() {
    this._comments = await fakeAjax();
    this._comments[0].body += ' of the day';
  }

  get comments() {
    if (this._comments === null) {
      this._fetchComments();
    }

    return this._comments;
  }
}

async function main() {
  let article = new Article(123, 'Hello World');

  // Comments may or may not be loaded yet
  let comments = await article.comments;

  console.assert(comments[0].body === 'First comment of the day');
}

I'm not sure if this restriction will continue to make sense. Decorators in particular make it possible to move concerns such as caching out of the getter code, so I think its worthwhile to revisit this for the future?


[FAB-17451] simplify TestCommSend

TestCommSend still made too many goroutines. There were two producers
and one consumer, and it could cause too many gouroutines to be
waiting to try and send.
Turned the senders and receivers into independent functions, along
with the final wait.
Change-Id: I14bc27db20c0e0de653c68c7e375b1f3d29dfee4
Signed-off-by: Morgan Bauer<EMAIL_ADDRESS>

Type of change

Bug fix
New feature
Improvement (improvement to code, performance, etc)
Test update
Documentation update

Description

Additional details

Related issues

sorry, wanted this on my fork


fix: add explicit type annotations to Interceptors

This is to make the generated code work with TS's new isolatedDeclarations config.
https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/#isolated-declarations
src/api/requests/core/OpenAPI.ts:14:3 - error TS9008: Method must have an explicit return type annotation with --isolatedDeclarations.

14   eject(fn: Middleware<T>) {
     ~~~~~

  src/api/requests/core/OpenAPI.ts:14:3
    14   eject(fn: Middleware<T>) {
         ~~~~~
    Add a return type to the method

src/api/requests/core/OpenAPI.ts:21:3 - error TS9008: Method must have an explicit return type annotation with --isolatedDeclarations.

21   use(fn: Middleware<T>) {
     ~~~

  src/api/requests/core/OpenAPI.ts:21:3
    21   use(fn: Middleware<T>) {
         ~~~
    Add a return type to the method

Note: I should add tsconfig tests because this is too easy to break and hard to see what it actually fixes

Can this land in the meantime? 🙂 I agree tests to prevent regressions is ideal, but this doesn't hurt on its own, and allows me to drop a floated patch

Merged, thanks! Is it okay if it's released on Monday/weekend?

Yeah, no rush at all 👍
Thanks!


Remove all non-modular jars

This is a long term task. The non-modular jars limit are tooling choices as they require special handling.

Look into replacing retrofit with feign.

@hohonuuli Still in progress or done?

@lonnylundsten Still in progress.


Be able to use official topology

This PR aims to support standard topology key topology.kubernetes.io/zone.
Closes #447

Could we check if [this test] is skipped or not ? And in any case, try to make a test with this support ?

@outscale-mdr I add test now

@outscale-mdr What do you think of the test and feature implementation ?


usePlural extract issue

Hi everyone,
thank you so much for this awesome package.
if you have an optional value like this:
const number = useSignal<number>()
const p = usePlural()

return
{p(number.value ?? 0,'app.someKey')}

It seems to me, you extract 0 as key here, which is wrong. This way extract is creating 0.json file for each language containing:
{
  "0": {
    "one": "",
    "other": ""
  }
}

I hope in the future I find some time to help you guys out, I really like the approach and except this small issue it works already quite fine.

Extract & Inline tools use a parser built specifically for this library. Should we extend it into a compiler to cover cases such as null coalescing?
Rather, I think it's simpler and more correct to initialize the signal, instead of adding null coalescing wherever it's used:
const number = useSignal<number>(0)
const p = usePlural()

return
{p(number.value, 'app.someKey')}

@robisim74 If your backend delivers something which can be null, you have to add a useComputed only for duplicating the same value. If it's to complex, we can work with it, but I was very confused seeing this files.

t & p closure functions are only placeholders that will be replaced with simple texts in production. They expect as first param a value or an identifier for now.
You can manage null values also in jsx (in my opinion more appropriate):
{number.value &&
{p(number.value, 'app.someKey')}
}
Note. You can't extend a library to cover every single case that occurs (because otherwise it would grow indefinitely). To implement a request you need to:

that the case is probable to occur
that there are no simple alternative solutions
that the implementation covers all analogous cases, in our example null coalescing, logical or, ternary operator and so on

Maybe I still not understand how the whole workflow is and I have to read it first.


Fix Resource::get_rid override not working in GDExtension

Since RID::from_uint64 is a static method, the original code did not work at all.
https://github.com/godotengine/godot/blob/655e93d5846b2ef8ebb7d22c8878f51b8f22b312/core/templates/rid.h#L66-L70

Thanks!


Attachment decorator ident

Allow specification of all attach-deco attributes on init; auto-generate (uuid4) ident for attachment deco by default via from_indy_dict().

Codecov Report

Merging #210 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #210      +/-   ##
==========================================
+ Coverage   72.66%   72.67%   +<.01%
==========================================
  Files         219      219
  Lines       10131    10132       +1
==========================================
+ Hits         7362     7363       +1
  Misses       2769     2769


I got this ported to my OS.

without modifying one line of codes.
https://github.com/chillancezen/ZeldaOS/tree/master/application/tinyvm
I do realize how portable the code written with ANSI C is.
much appreciated!


"Play my game" spam as comments

Like #1202, but it's potentially worse since it subverts the natural voting.

Added this as a support bottleneck since I'm the goto person when folks find this.

It could look something like this:

onChange event detects that I've entered a link to my game and it replaces the publish etc buttons with a helpful message.

It could look something like this:

The component reacts to and onChange event that sees that I've entered a link to my own page and replaces the publish etc. buttons with a helpful info box.

Neat. Does it stay there or is dismissable/go away at any time.r?
On Thu, Apr 26, 2018, 17:06 Martin Zackrisson<EMAIL_ADDRESS>wrote:

It could look something like this:
[image: ld_comment_nolinks]
https://user-images.githubusercontent.com/8041100/39331939-40835df0-49a6-11e8-8d08-eb72e4d6c4aa.png
The component reacts to and onChange event that sees that I've entered a
link to my own page and replaces the publish etc. buttons with a helpful
info box.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1636#issuecomment-384788934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf2CTPJH0VRBHETPyWqzByesVlg_JMWks5tsja-gaJpZM4TikDt
.

Couldn't there be a button to mark comments as unhelpful? Clicking it would be the opposite of the 'Love btn' and would lower the commenters coolness.
(Does the love button raise it? I'm actually not entirely sure what it does).


how to use the saved model after trained to detect new pictures

Hi all,
this might be repeated question.
I trained classifier on cats, dogs. and saved the model. Now I want to use the saved trained model to detect new pictures. How to do this? Is there a code for this?
Thanx

This is not Build/Installation or Bug/Performance issue. Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions. GitHub is mainly for addressing bugs in installation and performance. Thanks!


light gizmo doesn't show reliably

see title

Which part, the icon or the preview volume? Also does it show partially or not at all?

Further testing needed, maybe it was just a malfunction of the user


🌱 Fix go mod vulnerabilities according to different CVEs

What this PR does / why we need it:
Backport of #157
Fixes# https://github.com/advisories/GHSA-r48q-9g5r-8q2h , https://github.com/advisories/GHSA-69cg-p879-7622 and https://github.com/advisories/GHSA-hp87-p4gw-j4gq

/retest
/test-ubuntu-integration-release-1-1

Added hack/tools now
/test-ubuntu-integration-release-1-1

Timeout...
/test golangci-lint

/test unit
/hold cancel


Enable OpenCL in Debian package

I'm not sure if a PR on GitHub is the right way to get this to you, but here's a patch to build the OpenCL backend in the Debian packages. I've successfully used it to produce packages for Linux Mint.
This PR is based off your branch debian/sid on alioth. Only the last two commits are mine.

Hey Lars, thanks for showing interest in the OpenCL backend of ArrayFire. First thing to do is to file a bug in the Debian bug tracker against the source package arrayfire. Use severity wishlist and ask for a request for the OpenCL backend. That way, if someone else was also interested, then this bug will be the central point to track progress.
You will be pleased to know that I have already done some work on it and that a release in Debian unstable is to be expected soon. I cannot accept your patch however, since the content of the debian folder has changed quite significantly since the initial debianization done in this branch. You can have a look at the repository hosted on Debian science if you're curious.
On a side note, a slight variation from your proposal is that libarrayfire-dev will be a common package shared by libarrayfire-cpu-dev and libarrayfire-opencl-dev.

You can have a look at the repository hosted on Debian science if you're curious.

Do you mean this repo? That's actually where I got the code. This PR isn't really meant to apply to this repo, it just seemed like the easiest way to get the patches to you.

On a side note, a slight variation from your proposal is that libarrayfire-dev will be a common package shared by libarrayfire-cpu-dev and libarrayfire-opencl-dev.

I'm sorry, I don't understand how this is different from the way I set things up. I've put all the headers into the common -dev package and the .so into individual cpu-dev and opencl-dev.

I'm sorry, I don't understand how this is different from the way I set things up.

I meant:
Package: libarrayfire-dev
...
Depends:
 ${misc:Depends}
...

Package: libarrayfire-cpu-dev
...
Depends:
 libarrayfire-dev,
 ${misc:Depends}
...

Package: libarrayfire-opencl-dev
...
Depends:
 libarrayfire-dev,
 ${misc:Depends}
...

Plus, I will add an additional package libarrayfire-all-dev, which installs all ArrayFire backends:
Package: libarrayfire-all-dev
...
Depends:
 libarrayfire-cpu-dev,
 libarrayfire-opencl-dev,
 ${misc:Depends}
...

I actually considered that setup, but I chose against it because the libarrayfire-dev package seemed useless without either of the backend -dev packages. No client program would link, right? So I made libarrayfire-dev depend on libarrayfire-cpu-dev | libarrayfire-opencl-dev.

Feel free to correct if I am wrong here. According to your current d/control, if I apt-get install libarrayfire-opencl-dev, then neither the public includes nor the necessary ArrayFireConfig*.cmake dispatcher get installed. So the development environment would be incomplete.
Previously, doing apt-get install libarrayfire-cpu-dev provided a complete development environment, and I'd want the OpenCL, CUDA and future unified backends to remain that way.
For that to happen, the only solution I can think of is to factor the public headers and ArrayFireConfig*.cmake out to a "useless" package (libarrayfire-dev or libarrayfire-common-dev, naming convention still left to be discussed) on which all libarrayfire-$(backend)-dev would depend on.
Thoughts?

Hm, you're right there. I guess your setup is cleaner.

The only problem with your setup is that apt-get install libarrayfire-dev installs a useless package; but I guess that naming them -all-dev and -common-dev should be clear enough.

Actually, libarrayfire-dev is not technically "useless". Assuming you come up with an API-compatible alternative implementation of ArrayFire, then all you need is the public headers and the ArrayFireConfig*.cmake, which is what this package provides.
I admit this is an extremely improbable use case though.


chore(build): use just to manage build

This change is part of the following stack:

#31 ◀

Change managed by git-spice.


More refactoring changes

Following changes were done

Removed type references
Removed referring to deprecated code
Added “SafeVarargs” wherever applicable
Removed un-used imports
Removed SuppressWarnings wherever applicable
Refactored methods so that its usage is not in an
inverted fashion [ i.e., not like !isValid() type ]
Removed un-used methods (didn’t deprecate them
since they are internal package residing methods )
Use lambdas wherever applicable
Removed extraneous method arguments wherever
applicable

@juherr - I have addressed all the review comments. Please take a look.


router: Support TLS TCP routes

I should be able to define a TCP route with TLS enabled:
$ flynn -a postgres route add tcp -s postgres -p 5432 --tls-key <file> --tls-cert <file>

I could really use this. I'm happy to contribute, If anyone can point out to me what needs to be changed where.

@256dpi This would be implemented in the router: https://github.com/flynn/flynn/blob/master/router/tcp.go

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


ReferenceError: regeneratorRuntime babel-present-env error?

I think this may be a bug with babel-preset-env, just checking here first. I'm getting the error below when trying to run the tests for a new exercise I'm implementing. This error refers to this line: function* generate(A) {. Generator functions are part of the babel-preset-es2015 which should be included in babel-preset-env so I'm not sure why this is happening. Any ideas? Thanks!
 ● Test suite failed to run

    ReferenceError: regeneratorRuntime is not defined

      at Object.<anonymous> (exercises/alphametics/tmp/alphametics.js:57:15)
      at Object.<anonymous> (exercises/alphametics/tmp/temp.alphametics.spec.js:1:122)

Test Suites: 1 failed, 1 total

I have no idea :(
@exercism/javascript ?

@arthurchipdean @rchavarria I will try to investigate this later.  I think the first step is to see if I can reproduce it.  Personally, I haven't tried using generators under our current setup.

I have no idea about how to configure Babel nowadays (I did it in the past, but it has evolved a lot since then).
But just looking at the documentation, if I compare the support for arrow functions (a basic feature that makes sense to be included by default) to generators (a not so basic feature) I notice a difference:
The generators documentation shows a warning:

Runtime required
You need to use either the Babel polyfill or the regenerator runtime so that regeneratorRuntime will be defined.

It seems if we want to use generators we need a plugin.

@rchavarria You are right, after adding the babel-polyfil the error has gone away. Thanks for your help!

@arthurchipdean Can you check if this works? https://babeljs.io/docs/plugins/transform-regenerator/#usage-via-babelrc-recommended-
Since babel-plugin-transform-regenerator is already installed, I think it would be better if that can be used instead of adding a new package.

@tejasbubane  Yes that worked! I removed the babel-polyfil dependency and added the .babelrc file.


Remove post websocket search

Fixes #41
This removes the "cool" websocket post search feature and replaces it with a full page request search functionality. I think the websocket approach was fun but probably a bit overkill for that feature. If we were to do it we should probably return JSON and not rely on a kind of stubbed out conn replacement to try and render HTML views.
Pagination works and retains the query across pages.

Tomorrow afternoon will be all tilex for me so I'll be able to look at the code rather than just glance at it but yeah it seems like a solid choice. -chris

Nice! Thank you! 👍


Compilation failed when installing addon

Hi,
The editor seems broken and keeps throwing errors. Turns out some scripts fail to compile for some reason. Here are the logs:
Godot Engine v4.2.2.stable.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
  modules/gltf/register_types.cpp:63 - Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
--- Debug adapter server started ---
--- GDScript language server started on port 6005 ---
  res://addons/blockflow/commands/command.gd:234 - Parse Error: Could not resolve member "get_command".
  res://addons/blockflow/collection.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/commands/branch.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/commands/command.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/command_processor.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/core/utils.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/blockflow.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/editor/command_block/root.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/editor/displayer.gd:-1 - Compile Error:
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/editor/editor.gd:-1 - Compile Error:
  res://addons/blockflow/core/plugin_script.gd:-1 - Compile Error:
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/blockflow/core/plugin_script.gd" with error "Compilation failed". (User)
Remove Autoload
Add Autoload
  res://addons/blockflow/command_collection.gd:14 - Parse Error: The function signature doesn't match the parent. Parent signature is "get_command(int) -> Variant".
  res://addons/blockflow/commands/command_goto.gd:-1 - Compile Error:
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/blockflow/commands/command_goto.gd" with error "Compilation failed". (User)
  core/extension/gdextension.cpp:688 - GDExtension library not found:
  Failed loading resource: res://orchestrator/orchestrator.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
  core/extension/gdextension.cpp:688 - GDExtension library not found:
  Failed loading resource: res://orchestrator/orchestrator.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
  core/extension/gdextension.cpp:688 - GDExtension library not found:
  Failed loading resource: res://orchestrator/orchestrator.gdextension. Make sure resources have been imported by opening the project in the editor at least once.

Thank you for the report. Are you using the last commit in the main branch or are you using the latest release?

I'm using the latest release

Thank you, I'll debug this and make a release ASAP

1.1 version released, can you try and see if it works now, please?

Hi, sorry for the big delay, I haven't had time to look into Godot again for a while.
I still get errors:
Godot Engine v4.2.2.stable.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
  modules/gltf/register_types.cpp:63 - Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
--- Debug adapter server started ---
--- GDScript language server started on port 6005 ---
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/animation.svg-96bb5333edd4909624777a9c9d4a7760.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/bookmark.svg-82508ea2542c0fb3695c2c61eba9090b.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/branch.svg-90616a165dd595bdb39d1551185f36d2.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/comment.svg-23337e76f1842091fe042d8624d84723.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/function.svg-fb4ed8bdf43831b69d675649eea671c8.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/jump.svg-1b129eae2ba449be5d220e32ee0d8ebc.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/picture.svg-a49798352b09bf6be7d857c6d1669d55.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/play.svg-f6c1778f26a9cb162d89fb8c1abe906b.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/plugin_icon.svg-ec16cde1dc1c9a421de06d4015f22553.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/plugin_icon_flat.svg-17e1f10e7d6678eb27e8d65fd367b834.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/return.svg-3c0faf52579095e2a13ee6b9914f7c5b.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/settings.svg-7bb415dae634a28b0a8938b9be4570bc.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/sliders.svg-bdaac90bb94d8f07d99af1feb5d3af57.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/stop.svg-828b79ea27358c4b936f89091e6fdf78.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/timeline.svg-6779e58c1b1d9770a2c8d7452b569f3f.editor.meta'
  Missing required editor-specific import metadata for a texture (please reimport it using the 'Import' tab): 'res://.godot/imported/timer.svg-feea25d724a386103e92657be0689a34.editor.meta'
  res://addons/blockflow/tests/collection_test.gd:3 - Parse Error: Could not find base class "GdUnitTestSuite".
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/blockflow/tests/collection_test.gd" with error "Parse error". (User)
  res://addons/blockflow/tests/command_collection_test.gd:3 - Parse Error: Could not find base class "GdUnitTestSuite".
  modules/gdscript/gdscript.cpp:2726 - Failed to load script "res://addons/blockflow/tests/command_collection_test.gd" with error "Parse error". (User)

Why the duck are there the plugin test scripts? 😨
Please remove addons/blockflow/tests folder and try again. I'll review the release file 😅

Ok that has worked, I don't have errors anymore 👍

Thank you! I'll open a new issue related about the release


ci: add dependabot

we should consider adding Dependabot to this project. Dependabot is a tool that automates dependency updates by monitoring a project's dependencies and notifying us when updates are available. Dependabot can also create pull requests to update our dependencies automatically, saving us time and effort.
code demo
# dependabot.yml
version: 2
updates:
  # Update all npm dependencies
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "daily"
    # Update to the latest version
    version: "latest"

I would like to work on this issue.

We don't use Dependabot right now.
Why is this one the right solution? (There are alternatives)

ok

@priyankarpal would you be willing to update the issue description to outline (briefly explain) why you recommend this approach: using Dependabot?

@priyankarpal would you be willing to update the issue description to outline (briefly explain) why you recommend this approach: using Dependabot?

In this project currently we're using gh action also so in future if there are any updates needed for gh actions dependabot will automatically create a PR.


Cannot enter 'Configure FF OSD' from main menu

Title says it.  With no USB stock inserted I can enter the main menu by pushing both buttons, then scroll to the OSD setup option by moving left or right.  However, when at the OSD setup prompt nothing I do will convince it to enter that submenu.  What am I missing?  Currently using firmware 3.22.

Not using OSD extended protocol? Have you jumpered A0-A1 on the blue pill?

Not using OSD extended protocol? Have you jumpered A0-A1 on the blue pill?

Oh, bother...  My mistake!  I didn't pay attention to what I was reading and somehow thought it was configuration for the OLED display.  Sincerest apologies for the high specific gravity here.

Oh, bother...  My mistake!  I didn't pay attention to what I was reading and somehow thought it was configuration for the OLED display.  Sincerest apologies for the high specific gravity here.


Please consider changing default shortcut keys

This drove me crazy for a while until I realized it was song rating hijacking the opt1-5 keys & opt-`
Those are used to type ¡™£¢∞àèìòù characters
I personally change them all to use control instead of option

Sorry for the inconvenience. We cannot resolve this due to what matter the default key binding. The possible conflict always existing. And I'm not sure if there are some languages using the option to input the character regularly. I think most of languages using shift key.
The idea to using option is due to we binding the option + < and option + > to changes the rate up and down. The control key is not selected due to system conflict for screen navigation.  Following this pattern the option + number added for star rate.
And the key mapping supports customize to change what you want. Changing the key mapping will surprise existing users. So please select the binding best fit you should be fine.

There are plenty of available unbound key combinations, I'm simply suggesting setting the default to one that doesn't interfere with native behavior.

Changing the key mapping will surprise existing users.

I'm suggesting changing the default.  Existing users wouldn't be affected.

I'm not test that changes. Maybe this could only take effect for new users as your mentioned.
And another reason to choose the option as prefix key is make the right hand rate up and down with "<" and ">" possible. So please customize the key binding in preference panel to make it fit your best.
Maybe I could show the preference window or make a wizard to allow user set it at the first launch. But I'm not available recently. So I'm sorry that's won't fix in the near future.


Change istiod label to app=istiod

Fixes https://github.com/istio/istio/issues/21233
This should cause no upgrade issues, as the only part where the label is
immutable is in the deployment spec, and we are creating a new
deployment. This prevents issues where the new istiod service selects
the legacy deployment.

This needs to be backported to 1.5 right?

This needs to be backported to 1.5 right?

Yes

/cherrypick release-1.5

@howardjohn: once the present PR merges, I will cherry-pick it on top of release-1.5 in a new PR and assign it to you.

In response to this:

/cherrypick release-1.5

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ayj I made the change you suggested and renamed a few things that should be istiod to istiod. This is already approved but I put a hold so if its looks good to you can you remove it/comment?

/cherrypick release-1.5

@howardjohn: #21234 failed to apply on top of branch "release-1.5":
Using index info to reconstruct a base tree...

Auto-merging operator/pkg/vfs/assets.gen.go
CONFLICT (content): Merge conflict in operator/pkg/vfs/assets.gen.go
CONFLICT (modify/delete): operator/cmd/mesh/testdata/manifest-generate/output/pilot_override_values.golden.yaml deleted in HEAD and modified in Change istiod label to app=istiod. Version Change istiod label to app=istiod of operator/cmd/mesh/testdata/manifest-generate/output/pilot_override_values.golden.yaml left in tree.
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/pilot_override_kubernetes.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/pilot_k8s_settings.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/pilot_k8s_settings.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/pilot_default.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/pilot_default.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_set_values.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_set_values.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_override_values.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_override_values.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_output_set_values.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_output_set_values.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_output_set_profile.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_output_set_profile.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_output.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_output.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/flag_force.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/flag_force.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/component_hub_tag.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/component_hub_tag.yaml
Auto-merging operator/cmd/mesh/testdata/manifest-generate/output/all_on.yaml
CONFLICT (content): Merge conflict in operator/cmd/mesh/testdata/manifest-generate/output/all_on.yaml
Auto-merging manifests/istio-control/istio-discovery/templates/service.yaml
Auto-merging manifests/istio-control/istio-discovery/templates/deployment.yaml
CONFLICT (content): Merge conflict in manifests/istio-control/istio-discovery/templates/deployment.yaml
Auto-merging manifests/istio-control/istio-discovery/templates/clusterrolebinding.yaml
Auto-merging manifests/istio-control/istio-discovery/templates/clusterrole.yaml
error: Failed to merge in the changes.
Patch failed at 0001 Change istiod label to app=istiod

In response to this:

/cherrypick release-1.5

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Sync failed: please check your network connection.

I use Version 1.0.0-beta.3 (1.0.0-beta.3), and CAN connect to Github gist, but this message keep coming, DevTool console told me
Unhandled rejection TypeError: Cannot convert undefined or null to object
    at NavigationPanel.renderLangTags (file:///Applications/Lepton.app/Contents/Resources/app.asar/bundle/app.bundle.js:1962:14)
    at NavigationPanel.renderTagSection (file:///Applications/Lepton.app/Contents/Resources/app.asar/bundle/app.bundle.js:2019:16)
    at NavigationPanel.render (file:///Applications/Lepton.app/Contents/Resources/app.asar/bundle/app.bundle.js:2052:14)
    at /Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:796:21
    at measureLifeCyclePerf (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:75:12)
    at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:795:25)
    at ReactCompositeComponentWrapper._renderValidatedComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:822:32)
    at ReactCompositeComponentWrapper.performInitialMount (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:362:30)
    at ReactCompositeComponentWrapper.mountComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:258:21)
    at Object.mountComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactReconciler.js:46:35)
    at ReactCompositeComponentWrapper.performInitialMount (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:371:34)
    at ReactCompositeComponentWrapper.mountComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:258:21)
    at Object.mountComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactReconciler.js:46:35)
    at Object.updateChildren (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactChildReconciler.js:121:51)
    at ReactDOMComponent._reconcilerUpdateChildren (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactMultiChild.js:208:32)
    at ReactDOMComponent._updateChildren (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactMultiChild.js:312:31)
    at ReactDOMComponent.updateChildren (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactMultiChild.js:299:12)
    at ReactDOMComponent._updateDOMChildren (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactDOMComponent.js:936:12)
    at ReactDOMComponent.updateComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactDOMComponent.js:754:10)
    at ReactDOMComponent.receiveComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactDOMComponent.js:716:10)
    at Object.receiveComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactReconciler.js:125:22)
    at ReactCompositeComponentWrapper._updateRenderedComponent (/Applications/Lepton.app/Contents/Resources/app.asar/node_modules/react-dom/lib/ReactCompositeComponent.js:754:23)

Same issue with Version 1.0.0-beta.3 on Mac OS X.

The issue occurs during login, and Lepton hangs in the loading phase.

@aaronice Can you paste the log in ~/Library/Application Support/Lepton/logs?

@hackjutsu log result are
2017-02-03T23:04:05.834Z - info: Found user profile null
2017-02-03T23:04:07.370Z - info: [Dispatch] updateAuthWindowStatus ON
2017-02-03T23:04:32.228Z - info: [Dispatch] updateAuthWindowStatus OFF
2017-02-03T23:04:32.232Z - info: [Dispatch] updateUserSession IN_PROGRESS
2017-02-03T23:04:34.307Z - info: [Dispatch] updateUserSession IN_PROGRESS
2017-02-03T23:04:34.309Z - info: [Dispatch] updateAccessToken
2017-02-03T23:04:38.087Z - debug: The gist number on this page is 30
2017-02-03T23:04:40.033Z - debug: The gist number on this page is 30
2017-02-03T23:04:41.778Z - debug: The gist number on this page is 30
2017-02-03T23:04:42.862Z - debug: The gist number on this page is 3
2017-02-03T23:04:44.013Z - debug: The gist number on this page is 0
2017-02-03T23:04:44.022Z - error: The request has failed: TypeError: Cannot read property 'match' of null
2017-02-03T23:04:44.023Z - info: [Dispatch] updateUserSession ACTIVE
2017-02-03T23:04:59.345Z - info: Found user profile null
2017-02-03T23:05:00.771Z - info: [Dispatch] updateAuthWindowStatus ON
2017-02-03T23:05:25.349Z - info: [Dispatch] updateAuthWindowStatus OFF
2017-02-03T23:05:25.355Z - info: [Dispatch] updateUserSession IN_PROGRESS
2017-02-03T23:05:27.031Z - info: [Dispatch] updateUserSession IN_PROGRESS
2017-02-03T23:05:27.034Z - info: [Dispatch] updateAccessToken
2017-02-03T23:05:30.536Z - debug: The gist number on this page is 30
2017-02-03T23:05:32.357Z - debug: The gist number on this page is 30
2017-02-03T23:05:34.396Z - debug: The gist number on this page is 30
2017-02-03T23:05:35.626Z - debug: The gist number on this page is 3
2017-02-03T23:05:36.889Z - debug: The gist number on this page is 0
2017-02-03T23:05:36.901Z - error: The request has failed: TypeError: Cannot read property 'match' of null
2017-02-03T23:05:36.902Z - info: [Dispatch] updateUserSession ACTIVE
2017-02-04T00:53:13.418Z - info: The app window is closed

@CatTail Got it. This is caused by a null value when parsing the description.
export function descriptionParser (rawDescription = 'AWESOME GIST') {
  const regexForTitle = rawDescription.match(/\[.*\]/)
  const rawTitle = regexForTitle && regexForTitle[0] || ''
  const title = (rawTitle.length > 0) && rawTitle.substring(1, regexForTitle[0].length - 1) || ''

  const regextForCustomTags = rawDescription.match(/#tags:.*$/)
  const customTags = regextForCustomTags && regextForCustomTags[0] || ''

  const description = rawDescription.substring(rawTitle.length, rawDescription.length - customTags.length)

  return { title, description, customTags }
}

I thought the es6 initial value in the argument list will handle the case when the arg is null. But it turns out it only works when there is no args or the arg is undefined.

Default function parameters allow formal parameters to be initialized with default values if no value or undefined is passed. ref

Good lesson learned. I'll fix it soon

Should be fixed:https://github.com/hackjutsu/Lepton/commit/6af171eaea98915f2a0ec268468f5c817179086a

Issue still is happening to me on version 1.5.0 on macos, unable to login and use app.

Hi I'm on 1.5.0 on macos 10.13.2 and am getting the "Sync failed message". The dev console does not show any message at all. Lepton was working ok until I added some gists with a [title] and tags # then I was logged out and am now getting the sync message. I tried changing the gists directly on github but Lepton is still in a limbo.

@hansjons Try delete ~/Library/Application Support/Lepton/ in v1.5.0, or try the alpha release for 1.5.1.
https://github.com/hackjutsu/Lepton/releases/tag/v1.5.1-alpha

@hackjutsu I tried both and can confirm that both methods worked for me. Cool app by the way and thanks for the prompt reply:-)

I'm seeing this issue on Ubuntu 18.04.1 LTS on my desktop.
Still work on 16.0.4 LTS on my laptop.
The upgrade to the latest LTS version of Ubuntu on my desktop somehow broke Lepton

Can confirm same issue still persist in Ubuntu 18.04 LTS

A dedicated issue was raised here.


New Features List

Here, I list the features that are considered to be added in the future.
Features must have

[ ] display as a HTML file
[ ] add text
[ ] high order bond

Features nice to have

[ ] isosurface cap to seal the surface on the boundary.
[ ] molecular surface
[ ] show cavity for porous materials
[ ] export 3D model, e.g., obj format
[x] show fixed atoms
[x] hydrogen bond
[x] bond setting

Please feel free to suggest any additional features you would like to see implemented.

In the add_text feature, if we have math support, that would be outstanding. With that we can show vectors as $\vec{a}$ instead of a for lattice vectors.
When you export image, the resolution stops increasing at some value, may be around 5. You get same file size at 5 or 20. Similarly exported image can be automatically cropped by removing a relatively large white space around cell.
In case of large supercells or even smaller, having atoms as legend would be nicer.
I personally want to have some freedom over cell box, like tweaking  color or line thickness.


Wrong Information in Torque Calculator

In the inertia tab , description has enter force applied in Newtons(kg-m/s2) but Inertia is the Moment of inertia of the body that is measured in kg-m2.
There can be two ways to resolve this issue :

Add a choose the object form label, where we will have some standard objects/shapes(like disc,ring,cylinder,sphere,etc) whose
MOI will be automatically fetched by the website without having the user to enter it. And in case its not some standard shape but
the user knows the MOI, add a custom MOI tab for the user to enter.

Simply,just change the description of Inertia form label.

I am a GSSoC Contributor.Please assign me this issue and inform me about which option to consider.

@BabyElias just change the label as the MOI is calculated in other calculator

Ok. Will do it.

The Labels are fine now but please change the sign of torque(Tau), now the sign is:

Earlier it was: