Verify that the regenerated ledger represents the merkle root of the network it was replayed from

#6256 adds the target ledger hash to the replayer input. The replayer will fail (exit 1) if the final ledger hash doesn't match that hash.
Still need to add a CI job to run the replayer with a particular archive db and input.

We're checking ledger hashes for each block in the replayer, not sure what else this issue contemplates.


Hearts / Wires by Deftones unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> Deftones-Hearts-/-Wires

added, song name wrong on genius https://genius.com/Deftones-hearts-and-wires-lyrics


[file_selector] openFile crashes upon selecting the same file again

Steps to reproduce

Open a selector:

const images = XTypeGroup(
  label: 'Images',
  extensions: <String>['jpg', 'jpeg', 'bmp', 'gif', 'webp', 'png'],
);

final file = await openFile(acceptedTypeGroups: <XTypeGroup>[images]);

Pick an image from Google Drive.
Observe that NO error happens.
Open the selector again.
Pick the same image.
Crash happens. You can never select the image again. Even after restarting the app.

Expected results
I expect it to not throw the below exception, but this error seems so unfathomably strange, that I suspect it is hardware related. The test was done on a Samsung T510.
Actual results

Crash details
I/flutter (19371): ══╡ EXCEPTION CAUGHT BY FLUTTER FRAMEWORK ╞═════════════════════════════════════════════════════════
I/flutter (19371): The following PlatformException was thrown:
I/flutter (19371): PlatformException(java.lang.Exception: Failed to read file:
I/flutter (19371): content://com.google.android.apps.docs.storage/document/acc%3D5%3Bdoc%3Dencoded%3Dgoo3xDz35V9BK23ARmM3o5zSTbWIhv3VLJVFeqiB84udV4c%3D,
I/flutter (19371): Exception, Cause: null, Stacktrace: java.lang.Exception: Failed to read file:
I/flutter (19371): content://com.google.android.apps.docs.storage/document/acc%3D5%3Bdoc%3Dencoded%3Dgoo3xDz35V9BK23ARmM3o5zSTbWIhv3VLJVFeqiB84udV4c%3D
I/flutter (19371): 	at
I/flutter (19371): dev.flutter.packages.file_selector_android.FileSelectorApiImpl$1.onResult(FileSelectorApiImpl.java:113)
I/flutter (19371): 	at
I/flutter (19371): dev.flutter.packages.file_selector_android.FileSelectorApiImpl$4.onActivityResult(FileSelectorApiImpl.java:280)
I/flutter (19371): 	at
I/flutter (19371): io.flutter.embedding.engine.FlutterEngineConnectionRegistry$FlutterEngineActivityPluginBinding.onActivityResult(FlutterEngineConnectionRegistry.java:807)
I/flutter (19371): 	at
I/flutter (19371): io.flutter.embedding.engine.FlutterEngineConnectionRegistry.onActivityResult(FlutterEngineConnectionRegistry.java:430)
I/flutter (19371): 	at
I/flutter (19371): io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onActivityResult(FlutterActivityAndFragmentDelegate.java:811)
I/flutter (19371): 	at io.flutter.embedding.android.FlutterActivity.onActivityResult(FlutterActivity.java:771)
I/flutter (19371): 	at android.app.Activity.dispatchActivityResult(Activity.java:8550)
I/flutter (19371): 	at android.app.ActivityThread.deliverResults(ActivityThread.java:5583)
I/flutter (19371): 	at android.app.ActivityThread.handleSendResult(ActivityThread.java:5631)
I/flutter (19371): 	at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:51)
I/flutter (19371): 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
I/flutter (19371): 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
I/flutter (19371): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2336)
I/flutter (19371): 	at android.os.Handler.dispatchMessage(Handler.java:106)
I/flutter (19371): 	at android.os.Looper.loop(Looper.java:246)
I/flutter (19371): 	at android.app.ActivityThread.main(ActivityThread.java:8653)
I/flutter (19371): 	at java.lang.reflect.Method.invoke(Native Method)
I/flutter (19371): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
I/flutter (19371): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
I/flutter (19371): , null)
I/flutter (19371):
I/flutter (19371): When the exception was thrown, this was the stack:
I/flutter (19371): #0      FileSelectorApi.openFile
I/flutter (19371): <asynchronous suspension>
I/flutter (19371): #1      FileSelectorAndroid.openFile
I/flutter (19371): <asynchronous suspension>
I/flutter (19371): #2      ImageSelector.pickImage
I/flutter (19371): <asynchronous suspension>
I/flutter (19371): #3      ImagePickerButton.build.<anonymous closure>
I/flutter (19371): <asynchronous suspension>
I/flutter (19371):
════════════════════════════════════════════════════════════════════════════════════════════════════

Code sample
Code sample
[Paste your code here]

Screenshots or Video
No response
Logs
No response
Flutter Doctor output
Doctor output
[!] Flutter (Channel stable, 3.7.12, on macOS 14.2.1 23C71 darwin-arm64, locale en-US)
    • Flutter version 3.7.12 on channel stable at /Users/me/fvm/versions/3.7.12
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.1.5/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/me/fvm/versions/3.7.12. Consider adding /Users/me/fvm/versions/3.7.12/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (9 months ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/me/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/me/Library/Android/sdk
    • Java binary at: /Users/me/Library/Java/JavaVirtualMachines/corretto-1.8.0_362/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Corretto-8.362.08.1 (build 1.8.0_362-b08)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.85.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (3 available)
    • SM T510 (mobile) • R52N70RYCGL • android-arm    • Android 11 (API 30)
    • macOS (desktop)  • macos       • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 120.0.6099.199

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 3 categories.

Thanks for filing this @larssn.
Please can you provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code?
Thank you

A completely unrelated plugin (file_picker), exhibits the exact same problem, which points to an issue with the overall Google Drive implementation on this particular device.
So I'm closing because I'm guessing this will never be fixed.


feat: multiple fonts fallbacks

Adds the possibility to specify an array of base URLs in EXCALIDRAW_ASSET_PATH, so that we could register font faces for our bundled fonts with multiple fallbacks, in case of unreachable resources due to:

network restrictions (vpns, corporate policies, firewalls etc.)
ad blocker #8290 (only solves first-party if an appropriate filter is set to allow such fonts)
offline mode
unknowns

Excalidraw-app now has three font URLs for our bundled fonts:

DO CDN
Root domain excalidraw.com [fallback]
UNPKG CDN [fallback]

Fonts are fetched in the order specified above (with automatic fallbacks), for both:

window.document.fonts.load API

out-of-the-box fallbacks due to multiple sources specified as part of the FontFace object in a CSS familiar @font-face#source manner

fetch for SVG fonts inlining

added custom fallback mechanism
in case none of the URLs is reached (i.e. when working offline), we will just inline the last specified URL (unpkg for our bundled fonts or whatever URL we have for other fonts)

Additional improvements:

setting CORS for excalidraw.com as the only origin for all the new fonts
treating DO CDN as SSOT with a build-step

👍

If Helvetica is used in the scene I get this error

It's probably because I've let it register Helvetica font face (line changed below), since I did not observe any impact. Is this thrown for some reason just in Electron? I cannot repro on the PR deployment.
https://github.com/excalidraw/excalidraw/pull/8286/files#diff-f5ccf5aca114071dcadadf871453d462f106971c70d3face46b3a855664e13bfL127

@zsviczian could you perhaps confirm #8303 solves this?

I confirm #8303 solves the issue.
The screenshot above is from Excalidraw web: https://excalidraw-7vmwury8n-excalidraw.vercel.app/#json=t11M0HM6UHAPuCgd97kcC,BjJyC9R4u_fj73hS_U5QJQ
I used the preview from the most recently merged PR: https://github.com/excalidraw/excalidraw/pull/8302


onClose() is automatically called while the controller is still in use.

I am developing a front-end chat application, I have a controller named ChatRoomController Put with the ChatRoomID tag, in this ChatRoom screen, I want when I click on Notification, it will replace this screen with a new controller Put with the new tag, everything works fine until I focus on the Textfield, the onClose function is called while the controller is still in use, the Controller still has the functions in the Controller still working normally, only the onClose is called Dispose all the controllers like TextEditingController, ScrollController, animationController, ... have been disposed. Any suggestions from everyone will help me a little
Thanks!
handle when clicking on notification
I use parameter as tag

Example
https://github.com/user-attachments/assets/7d48e2fb-4518-4226-bcdb-a5d7c87b6649
Log

Flutter Version 3.24.3
Get Version 4.6.6

I'm so sorry, because I didn't pass in the tag in GetBuilder, that's why TextEditController got this error.

I'm so sorry, because I didn't pass in the tag in GetBuilder, that's why TextEditController got this error.


0.29 _typeconv import issue

Traceback (most recent call last):
File "lib\testapp\testapp.py", line 2311, in
import numba
File "C:\p\testapp\lib\numba_init_.py", line 12, in
from .special import typeof
File "C:\p\testapp\lib\numba\special.py", line 3, in
from .typing.typeof import typeof
File "C:\p\testapp\lib\numba\typing_init_.py", line 2, in
from .context import BaseContext, Context
File "C:\p\testapp\lib\numba\typing\context.py", line 10, in
from numba.typeconv import Conversion, rules
File "C:\p\testapp\lib\numba\typeconv\rules.py", line 3, in
from .typeconv import TypeManager, TypeCastingRules
File "C:\p\testapp\lib\numba\typeconv\typeconv.py", line 3, in
from . import _typeconv, castgraph, Conversion
ImportError: cannot import name '_typeconv'

Is this an installation from source?  This looks like the C extensions were not built.

Windows, no not from source

http://www.lfd.uci.edu/~gohlke/pythonlibs/#numba
On Thu, Oct 20, 2016 at 9:42 AM, Stan Seibert<EMAIL_ADDRESS>wrote:

Is this an installation from source? This looks like the C extensions were
not built.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/numba/numba/issues/2158#issuecomment-255109000, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABXVTZMct1Frul3LuGf0ttc0MeOOZ_Evks5q12-vgaJpZM4Kbuhq
.

Hmm, this sounds like this might be an issue with the Gohlke package build.  We are not involved with these builds, and it sounds like Gohlke isn't providing any support for these packages.  You could report the issue to him, but I don't know if he will have any time to fix it.
We build and test binary packages for Anaconda on Windows/Mac/Linux, so that's the only other suggestion we can offer.

Can't reproduce.

With our conda packages, we've sometimes seen a strange error like this if the binary package is installed while package files are open (due to how windows handles file locks).  You could try forcing a reinstallation when you are sure no other python instances are running.

While I can't reproduce this error, I get a LLVM IR parsing error in production code with llvmlite-0.14.0. Had to revert to previous numba/llvmlite for now.
X:\Python35\lib\site-packages\numba\targets\codegen.py in add_ir_module(self, ir_module)
    147         assert isinstance(ir_module, llvmir.Module)
    148         ir = cgutils.normalize_ir_text(str(ir_module))
--> 149         ll_module = ll.parse_assembly(ir)
    150         ll_module.name = ir_module.name
    151         ll_module.verify()

X:\Python35\lib\site-packages\llvmlite\binding\module.py in parse_assembly(llvmir)
     20         if errmsg:
     21             mod.close()
---> 22             raise RuntimeError("LLVM IR parsing error\n{0}".format(errmsg))
     23     return mod
     24

RuntimeError: Failed at object (object mode frontend)
Failed at object (object mode backend)
LLVM IR parsing error
<string>:767:55: error: expected type
  %".600" = call i8* (i64) @"PyLong_FromSsize_t"(i64 (0, 0))

This looks very strange.  I'm going to open a new issue in the llvmlite repo to track the parser error.

This was an easy one, I download python 3.6 and needed 3.5. No issue.
On Thu, Oct 20, 2016 at 12:20 PM, Stan Seibert<EMAIL_ADDRESS>wrote:

Hmm, this sounds like this might be an issue with the Gohlke package
build. We are not involved with these builds, and it sounds like Gohlke
isn't providing any support for these packages. You could report the issue
to him, but I don't know if he will have any time to fix it.
We build and test binary packages for Anaconda on Windows/Mac/Linux, so
that's the only other suggestion we can offer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/numba/numba/issues/2158#issuecomment-255154758, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABXVTeRjQGHHlYjS_d9Q933SUBrYYJZXks5q15S1gaJpZM4Kbuhq
.

OK, glad you figured it out.  The IR parse error will be tracked in the llvmlite repo.


Unbound value error when running "dune build"

When I try to run dune build I get the following error:
File "src/colors.ml", line 5, characters 8-26:
Error: Unbound value Color.of_hexstring
Hint: Did you mean to_hexstring?

I tried following the hint and got a type error.

Thanks for reporting!
I cannot reproduce. Just to make sure, you've set up opam like this?
$ opam init
$ opam switch 4.07.0
$ opam install dune core lwt re color sexp_pretty

During opam init, did you let it add the opam config hook to your shell init? Like this in your .bashrc or .zshrc:
# OPAM configuration
. /home/alex/.opam/opam-init/init.zsh > /dev/null 2> /dev/null || true

You might need to reload your terminal

The reason I ask is because I suspect an old version of the Color library is being pulled in without this commit: https://github.com/anuragsoni/color/commit/3449ab9f8c44b87ef8b2d0019d564ffceb0211f2#diff-3b911a16cb75f078b7c3ccd2682c5e09
So if you aren't on OCaml 4.07.0 that might explain why.


Cookbook fails to use reload for restarting dovecot on SLE 12

The dovecot cookbook states, that the reload command is supported for all installations of dovecot:
service 'dovecot' do
    supports restart: true, reload: true, status: true
    ....
end

This is not true at least for dovecot on SLE 12 with systemd. There it fails with the following error message:
       - restart service service[postfix]
   Recipe: dovecot::service

       ================================================================================
       Error executing action `reload` on resource 'service[dovecot]'
       ================================================================================

       Mixlib::ShellOut::ShellCommandFailed
       ------------------------------------
       Expected process to exit with [0], but received '3'
       ---- Begin output of /usr/bin/systemctl reload dovecot ----
       STDOUT:
       STDERR: Failed to reload dovecot.service: Job type reload is not applicable for unit dovecot.service.
       ---- End output of /usr/bin/systemctl reload dovecot ----
       Ran /usr/bin/systemctl reload dovecot returned 3

       Resource Declaration:
       ---------------------
       # In /tmp/kitchen/cookbooks/dovecot/recipes/service.rb

        22: service 'dovecot' do
        23:   supports restart: true, reload: true, status: true
        24:   if node['platform'] == 'ubuntu' &&
        25:      Gem::Version.new(node['platform_version']) >= Gem::Version.new('13.10')
        26:     provider Chef::Provider::Service::Upstart
        27:   elsif node['platform'] == 'debian' &&
        28:         node['platform_version'].to_i >= 8
        29:     provider Chef::Provider::Service::Debian
        30:   end
        31:   action [:enable, :start]

       Compiled Resource:
       ------------------
       # Declared in /tmp/kitchen/cookbooks/dovecot/recipes/service.rb:22:in `from_file'

       service("dovecot") do
         action [:enable, :start]
         updated true
         supports {:restart=>true, :reload=>true, :status=>true}
         retries 0
         retry_delay 2
         default_guard_interpreter :default
         service_name "dovecot"
         enabled true
         running true
         pattern "dovecot"
         declared_type :service
         cookbook_name :dovecot
         recipe_name "service"
       end

   Running handlers:
   [2015-09-10T15:14:14+03:00] ERROR: Running exception handlers
   Running handlers complete
   [2015-09-10T15:14:14+03:00] ERROR: Exception handlers complete
   Chef Client failed. 255 resources updated in<PHONE_NUMBER>95 seconds
   [2015-09-10T15:14:14+03:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
   [2015-09-10T15:14:14+03:00] ERROR: service[dovecot] (dovecot::service line 22) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '3'
   ---- Begin output of /usr/bin/systemctl reload dovecot ----
   STDOUT:
   STDERR: Failed to reload dovecot.service: Job type reload is not applicable for unit dovecot.service.
   ---- End output of /usr/bin/systemctl reload dovecot ----
   Ran /usr/bin/systemctl reload dovecot returned 3
   [2015-09-10T15:14:14+03:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Hi @kleini,
Thanks for reporting the issue.
I do not have any machine with SUSE. But trying to run the cookbook on an openSUSE platform gives me a different error:
================================================================================
Error executing action `install` on resource 'zypper_package[(core) dovecot-core]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '104'
---- Begin output of zypper --non-interactive --no-gpg-checks install --auto-agree-with-licenses dovecot-core ----
STDOUT: Loading repository data...
Reading installed packages...
STDERR: Package 'dovecot-core' not found.
---- End output of zypper --non-interactive --no-gpg-checks install --auto-agree-with-licenses dovecot-core ----
Ran zypper --non-interactive --no-gpg-checks install --auto-agree-with-licenses dovecot-core returned 104

Resource Declaration:
---------------------
# In /tmp/kitchen/cookbooks/dovecot/recipes/from_package.rb

 34:     package "(#{type}) #{pkg}" do
 35:       package_name pkg
 36:       only_if { Dovecot::Conf.require?(type, node['dovecot']) }
 37:       if type == 'core' || node['dovecot']['ohai_plugin']['build-options']
 38:         notifies :reload, 'ohai[reload_dovecot]', :immediately
 39:       end
 40:     end # package

Compiled Resource:
       ------------------
# Declared in /tmp/kitchen/cookbooks/dovecot/recipes/from_package.rb:34:in `block (2 levels) in from_file'

zypper_package("(core) dovecot-core") do
  action [:install]
  retries 0
  retry_delay 2
  default_guard_interpreter :default
  package_name "dovecot-core"
  declared_type :package
  cookbook_name :dovecot
  recipe_name "from_package"
  only_if { #code block }
end

Please, can you try if disabling the reload fixes the problem on SLE?

Obviously they do not have any dovecot-core package:
singlenode:~ # zypper search dovecot
Loading repository data...
Reading installed packages...

S | Name                      | Summary                                                      | Type
--+---------------------------+--------------------------------------------------------------+-----------
i | dovecot                   | IMAP and POP3 Server Written Primarily with Security in Mind | package
i | dovecot22                 | IMAP and POP3 Server Written Primarily with Security in Mind | package
i | dovecot22-backend-mysql   | MySQL support for Dovecot                                    | package
i | dovecot22-backend-pgsql   | PostgreSQL support for Dovecot                               | package
i | dovecot22-backend-sqlite  | SQLite support for Dovecot                                   | package
singlenode:~ #

When I look into the cookbook code I see:
case node['platform']
when 'redhat', 'centos', 'scientific', 'fedora', 'suse', 'amazon', 'oracle'
  default['dovecot']['packages']['core'] = %w(dovecot)
  default['dovecot']['packages']['imap'] = [] # included inside core
  default['dovecot']['packages']['pop3'] = [] # included inside core
  default['dovecot']['packages']['lmtp'] = [] # included inside core
  default['dovecot']['packages']['sieve'] = %w(dovecot-pigeonhole)
  default['dovecot']['packages']['ldap'] = [] # included inside core
  default['dovecot']['packages']['sqlite'] = [] # included inside core
  default['dovecot']['packages']['mysql'] = %w(dovecot-mysql)
  default['dovecot']['packages']['pgsql'] = %w(dovecot-pgsql)

which is correct except the sieve package. I don't see a dovecot-core package for platform suse.

OK, thanks. I'm going to fix openSUSE support and see if that fixes SUSE support.

Is there any chance to workaround the problem by changing attributes in the dovecot service resource to not call the reload function and use instead the restart function?

You can try disabling the reload in the service after including the cookbook:
include_recipe 'dovecot'

r = resources(service: 'dovecot')
r.supports restart: true, reload: false, status: true

Unfortunately the systemd provider does not respect the supports attribute. And we are again here: https://github.com/chef/chef/issues/3678

I'm on it. Meanwhile try this:
include_recipe 'dovecot'

r = resources(service: 'dovecot')
r.provider(Chef::Provider::Service::Redhat)

Fixed in 668f266.

Released in 2.4.0.

Works like a charm!

I am glad it has been fixed :wink:


Support rename initiated from the end of an identifier 🚥 #1163

Depends on https://github.com/apple/sourcekit-lsp/pull/1163

rdar://124727045

@swift-ci Please test


ads shows only when i resume the app not at the launching

this's my main function
void main() async{
  WidgetsFlutterBinding.ensureInitialized();
  MobileAds.instance.initialize();
  /// Replace your admob app ID
  final admobAppId =  FlutterAdmobAppOpen.testAppId;

  /// Replace your admob app open ad unit id
  final appAppOpenAdUnitId =FlutterAdmobAppOpen.testAppOpenAdId;

   AdRequestAppOpen targetingInfo = AdRequestAppOpen(
      keywords: <String>['flutterio', 'beautiful apps'],
      contentUrl: 'https://flutter.io',
      //testDevices: <String>[], // Android emulators are considered test devices
      nonPersonalizedAds: true,
    );

  await FlutterAdmobAppOpen.instance.initialize(
    appId: admobAppId,
    appAppOpenAdUnitId: appAppOpenAdUnitId,
    targetingInfo: targetingInfo,

  );
  runApp(myApp());
}

the ads only show when I pause the app and the resume but the I launch the app its not showing Is in my code or this is how this package is works ??
I will be glad to add any required information if any is need

same issue here!

I have the same issue with Android and in iOS the app crashes.


Report what tests have been run on a resource

Reporting of tests done
It would be really nice if the GUI would report what tests have been run on a resource, similar to what YummyData does, so that we can learn how resources can be made more FAIR.

Interesting, I already have a reporting system in place to report which files I failed to parse (mainly for unvalid RDF files)
It commits the reports in markdown of each run to a blank report branch:
https://github.com/vemonet/shapes-of-you/tree/report
I currently disabled the commits, because the reports where changing at each run an some could get quite big, there are so many unvalid RDF file out there! But the system works well
This could be easily updated to report other metadata
Ideally we would reuse an existing library that would generate this report (python would be perfect, Java or any other language would work if we can make it an executable).
If you have some direct pointers to existing tools, or even just direct link to the code files where some services implemented it (e.g. YummyData) I could take a look
Otherwise we would need to implement one.
The problem is that there are already multiple "FAIR validator" tools, but, as far as I know, most of them are not reusable, or even accessible (disclaimer: I host one of them, but cannot reuse it.).
Which is ironic as the core of the FAIR ecosystem does not seems FAIR itself, and cannot even be peer reviewed.
Honestly in my opinion it could be implemented as a simple python script/library (1 file, less than 500 lines most probably), and be easily improvable incrementally by the community to make the process of validating FAIRness more FAIR.

For SPARQL endpoints YummyData clearly describe it's methodology and queries used here: http://yummydata.org/umaka-score.html
It could be reimplemented, especially that I don't take into consideration the endpoints that do not support graphs when I try to generate metadata


Readme.md - add windows passing and linux passing to CI badges.

Given that this lib has gone to great efforts to ensure full support for both Windows + Unix-like systems, I believe that it should be clearer to users that this is the case.
Unless they are using app veyor themselves, the vast majority of your users will be none the wiser in regards to OS support as the app veyor logo will mean nothing to them.
This change is a simple one, but will make it crystal clear to all users that you take Windows support seriously.
Preview:
http://f.cl.ly/items/2U151G0q3q2H0B3v253n/Screen Shot 2015-03-22 at 15.58.41.png

Thanks for the PR and the supportive comments. For this lib, Mac is actually a totally distinct case from Linux as well. Any idea how to distinguish between them from the Travis tests for separate badges on those?

Badges on travis are per-build - so you couldn't have separate badges.
Nothing stopping something like ...

... though :)

or even this looks nice I think
https://img.shields.io/travis/paulmillr/chokidar/master.svg?label=Mac%20OSX%20%26%20Linux

Updated, preview https://github.com/shakyShane/chokidar

Yup, looks great. Thanks.

:+1: - thanks to you for the great lib - I'm in the process of using it to replace Gaze in BrowserSync :)

Cool. Let me know when that's published and we can mention it in the chokidar readme.

Will do, reliant on https://github.com/paulmillr/chokidar/issues/264 however.


Modify ESM protocol for STAGING_PROJECT

Use new proposed ESM protocol for CNS sites, testing in STAGING_PROJECT project:
6 days, 6 ESMs per day, every 12 weeks
Increase completion window to 15 minutes from default 10 minutes

Can we maybe change the interval to every 12 weeks anyway?
We get a lot of unnecessary notifications every day all the time. If this is just for testing, we can add it as a clinical task too so it's always there?

Sure, I can change it to 12 weeks. I was just worried that if we miss the 6 day period, we would have to change the phone's date or enroll with a new subject. Is that fine?

Can we maybe change the interval to every 12 weeks anyway?
We get a lot of unnecessary notifications every day all the time. If this is just for testing, we can add it as a clinical task too so it's always there?

Made the changes

Can we merge this?


Revert "chore(release): 1.0.0-alpha.1 [skip ci]"

This reverts commit 164441919aabed97d6748ccb6cb76a9b4655e5f7.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


fix: cwd not escaping when running wt.exe externally

We actually already set the cwd when spawning wt.exe, so we can use just
. to reference it and avoid dealing with escaping entirely.

Yes, this follows up on https://github.com/microsoft/vscode/issues/204039


Makefile does not always use DOCKER_COMPOSE_ENV var

Changes
Let say that you add a /src/adservice/Dockerfile.elastic to the project to build a specific version of the image. So you add the following line to the .env.override file:
AD_SERVICE_DOCKERFILE=./src/adservice/Dockerfile.elastic

If you run:
make redeploy

The /src/adservice/Dockerfile.elastic should be used instead of the default one.
This commit adds DOCKER_COMPOSE_ENV variable anywhere it's needed.
Closes #1758.

There's still an error with markdownlinkcheck but I did not change anything ;)

There's still an error with markdownlinkcheck but I did not change anything ;)

I think that was a fluke error: the link checker got a 502 for a particular GitHub repo URL during that check. Perhaps @rogercoll could re-run the test (I don't have access to re-run the workflow).

There's still an error with markdownlinkcheck but I did not change anything ;)

I think that was a fluke error: the link checker got a 502 for a particular GitHub repo URL during that check. Perhaps @rogercoll could re-run the test (I don't have access to re-run the workflow).

Correct, rerunning it fixed the issue.


Adds a liquid-animating class while an animation is occuring

Allows for customization of liquid-container's CSS whilst it's children are animating. Can be used to control the element's overflow properties as described in issue #208.

Thanks for this PR.
This doesn't quite solve the problem in all cases, because animate is an optional helper. People are free to implement transitions in other ways.
Instead, take a look at willTransition and afterTransition in liquid-container.js. I think if you set and clear the class from there it will work in every case.

I moved the changes into liquid-container.js, and it seems to be working as intended.

Thanks. I merged and then refactored a bit to take advantage of ember's built-in classNameBindings.

Any chances getting this class on the entire html as well? Would be nice to set overflow: hidden to body when using toUp / toDown to prevent scrollbar appearing on OS X.

I'm missing how this solves #208. Is the idea that you override/disable overflow:hidden on the liquid-outlet then only have overflow:hidden on the liquid-animating class?


screenshot highlight area offset

Great that the module is now working on Angular6. However, I'm facing an issue on Google Chrome and Safari with the Overlay for highlighting parts of the image. While it displays everything correctly while drawing the yellow rect and also it shows the right image in the preview, the final image is widely offset and the covering layer seems way too small:

What are possible reasons for this ?

Hi @hakkurishian , actually current way to draw rectangle is not the best. The project is being updated for using a new way to draw rectangle. Once it done, the issue you met should be fixed. I reckon the update will be completed around two weeks.

Hi @RickonChen - is there any update on this? I'd be willing to help if that makes sense at this stage.

Hi @hakkurishian , yes. The update should could be finished before next Tuesday.

Hi @RickonChen  thank you ! Now the last problem I'm facing regarding the screenshot is that the little toolbar is not draggable if it is below the highlighted rect( which can be resolved by moving it away before highlighting)

Hi @hakkurishian , the issue seems could be solved by adjusting the z-index of rectangles and toolbar. I will see if I can fixed duing this week.

Hi @hakkurishian, latest version 1.1.5 or newer has solve the issue.


Txt2Al conversion error - CONST('') in property converted to const('') in AL

Dear AL team,
A little backstory: I had developed a page object (a list page) in an extension where I tried to apply a filter to only show records for which the Code field is equal to ''. So what I tried to do is setting the SourceTableView property to the following:
SourceTableView = sorting (Tag, Code) where (Code = const (''));

However, I noticed that no filter was applied to the page, instead it showed all records.
I didn't see any particular problem with the propery-setting directly, but after some time I noticed that the property should instead be set to:
SourceTableView = sorting (Tag, Code) where (Code = const (''''''));

(i.e., using '' to escape each single quote in the string; if you know an easier way, please feel free to share!)
For developing my extension I made use of the output of the Txt2Al conversion tool as a starting base for multiple new object definitions in AL.
I noticed that the Txt2Al tool suggests to convert CONST('') from the 'classic' object to const ('') in the AL object definition. This seems to be a bug in the Txt2Al conversion tool.
This also applies to other object types and similar properties, for example the DataItemTableView property for a dataitem in a report object. This applies to the Txt2Al tool that ships with W1 13.0 (24285).
Hope you can look into this! Thank you in advance for any responses!

Another related error:
When you have the DataItemTableView property in a report dataitem set to CONST(), then the Txt2Al tool will convert this to const('').

Hi @rvanbekkum, can you try reproducing it on the latest developer preview from the version 14.x? If it still reproduces, can you share with us some C/AL code that would reproduce this issue after being converted to AL?

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.


Cannot provide decimals in daily energy mode

Also have a look into values < 1. Also add a test for this case.

Fixed with #985

was this supposed to be fixed with the PR?:
Logger: homeassistant.components.sensor
Source: custom_components/powercalc/sensors/daily_energy.py:196
Integration: Sensor (documentation, issues)
First occurred: August 18, 2022, 22:47:12 (2 occurrences)
Last logged: August 18, 2022, 22:47:12

Error adding entities for domain sensor with platform powercalc
Error while setting up powercalc platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 428, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 673, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 775, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/powercalc/sensors/daily_energy.py", line 196, in async_added_to_hass
    self._state = Decimal(state.state)
decimal.InvalidOperation: [<class 'decimal.ConversionSyntax'>]

Yes was supposed to be fixed. However comparing your stack trace with https://github.com/bramstroker/homeassistant-powercalc/issues/980. The issue arrises on another place, so definitely need to fix some other occurence as well.

Issue added https://github.com/bramstroker/homeassistant-powercalc/issues/1010

@Mariusthvdb  Fixed with #1046


Ability to turn on the green health bar over your character out of combat even at 100%

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've
considered.
Additional context
Add any other context or screenshots about the feature request here.

@powersubzero - can you fill out the issue text in your top post for clarity? I understand what you're asking but it may be helpful for others to have more information.


Influencing markdown rendering

Hey, i am currently writing a theme and integrating Bulma.
Now im asking myself if it is also possible to influence how single content blocks look or are structured, for example a notice (wihich you currently only style using your css classes) as in how it is rendered in html?
Im not too far into Symfony or Slim so i couldn't look into the Markdown-Render Logic yet.
Sincerely
Josef

so i see, that there is some rendering happening. in my case influencing the css-classes helps alot already.
I'd rather do it with javascript now, which is no problem for me, but serverside-rendering would be more bullet proof.
As an example using bulma for notifications
https://bulma.io/documentation/elements/notification/
doing it influencing your core system:
            $Block = [                 'element' => [                     'name' => 'div',                     'handler' => array(                         'function' => 'linesElements',                         'argument' => (array) $text,}                         'destination' => 'elements',                     ),                     'attributes' => [                         'class' => "notification is-primary",                     ],                 ],             ];
doing it with JavaScript:
window.addEventListener("DomContentLoaded", ()=>{ document.querySelectorAll('.notice1').forEach(el=>{ el.classList.add('notification', 'is-primary'); el.classList.remove('notice1'); }) document.querySelectorAll('.notice2').forEach(el=>{ el.classList.add('notification', 'is-secondary'); el.classList.remove('notice2'); }) })

Yes, you are right, you have to change the markdown renderer to add classes to elements. I use parsedown and some own extensions for non-standard stuff like notice elements. Right now you cannot hack into the renderer directly. I did not work with Bulma yet (I use Tachyons), but if something is not accessible with a framework, I usually write some custom css to style things.
The only way to change the classes right now is with a plugin, but I doubt that it makes sense because your theme depends on a plugin then. Next problem is the performance: With a plugin you can hack into the content-array before it is transformed into html (see https://typemill.net/plugin-developers/event-overview event "oncontentArrayLoaded"), but then you have to loop over the whole content array, check for notice elements and change the class in the array. It is possible, but maybe the JavaScript solution is smarter.
I wouldn't change the core code for a specific frontend framework, there are too many of them. But maybe it is a solution in future to add another configuration in yaml where you can add css-classes for html elements in your theme and use them in parsedown. I have to think about it a bit, but I won't have time to implement it in next weeks because of other tasks on the roadmap...

Well, that totally contradicts the way how the markdown parsers work.
But it is a nice idea, let me think about it :D

i actually thing that this feature is kind of in the new typemill version with shortcode plugins!

Still a very nice idea. I will try to allow limited html-elements in markdown soon, maybe with shortcode logic, so you have some more flexibility. Changing the rendering in parsedown is too complicated right now. I will close this for now because I want to focus on bugs-reports in issues, for everything else the github-questions/answers is the best place


Query Loads Forever "Config is not defined"

When clicking on a link that requires login I login and then it just loads forever. Even with non login required links the same thing can happen sometimes.

Still a Problem!


fixing video for reals

Hello @ksigler7,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Unique column in kundera mongodb

I want restaurant_item_name must be Unique
My class is below
@Entity
@Table(name = "restaurant_item", schema = "xxx@xxx")
public class RestaurantItem implements Serializable {
	@Id
	@GeneratedValue(strategy = GenerationType.AUTO)
	private String restaurant_item_id;

	@Column(name = "restaurant_item_name")
	private String restaurant_item_name;
//setter and getters
}

Help me.

@sreekanth0041
Currently you cannot specify this using using Kundera, however you can ensure unique names in  MongoDB  by creating a unique index over it in the following manner :
db.restaurant_item.ensureIndex( { restaurant_item_name: 1 }, { unique: true } )

Hope this Helps!
Chhavi

Thank you for giving the replay chhavigangwal,We need to do it manually right?

Yes
Chhavi

Ok thank you

@sreekanth0041
http://docs.mongodb.org/manual/tutorial/create-a-unique-index/
Better to use
db.restaurant_item.ensureIndex( { restaurant_item_name: 1 }, { unique: true, sparse: true } )

Also, IMHO it should be invoked during application bootstrap.  With Kundera, i guess you should be able to execute it in native way. So while instantiating EMF, get a handle of Mongo DB client and just invoke it.
Kundera Team, can enable this support by extending @Index and @IndexCollection for index uniqueness.
HTH,
-Vivek

Fixed with Kundera 3.0 release.


[ISSUE-301][Subtask][Improvement][AQE] Merge continuous ShuffleDataSegment into single one

What changes were proposed in this pull request?

Merge continuous ShuffleDataSegment into single one
Throw exception when reading the discontinuous blocks into segments directly

Why are the changes needed?

Currently, the LocalOrderSegmentSplitter will split the index file into
multiple shuffleDataSegments. But the split scope is limited in the range of local order.
For example:
The blocks are as follow
block-a (taskId-1)
block-b (taskId-2)
block-c (taskId-1)
block-d (taskId-2)

When the reader want to get  the range of taskIds: [1, 3), the strategy will return
two shuffleDataSegments. But we'd better to merge them into single one to
reduce the network interaction times, because they are continuous.
Does this PR introduce any user-facing change?

No
How was this patch tested?

UTs

Codecov Report

Merging #303 (d05e086) into master (74949f5) will decrease coverage by 1.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #303      +/-   ##
============================================
- Coverage     60.76%   59.73%   -1.03%
+ Complexity     1454     1380      -74
============================================
  Files           179      170       -9
  Lines          9201     8693     -508
  Branches        882      850      -32
============================================
- Hits           5591     5193     -398
+ Misses         3316     3217      -99
+ Partials        294      283      -11

Impacted Files
Coverage Δ

...ffle/common/segment/LocalOrderSegmentSplitter.java
88.23% <100.00%> (+1.56%)
:arrow_up:

.../org/apache/spark/shuffle/writer/WriterBuffer.java

...org/apache/spark/shuffle/RssSparkShuffleUtils.java

...ava/org/apache/spark/shuffle/RssShuffleHandle.java

...k/shuffle/writer/WrappedByteArrayOutputStream.java

...e/spark/shuffle/reader/RssShuffleDataIterator.java

.../java/org/apache/spark/shuffle/RssSparkConfig.java

...che/spark/shuffle/writer/BufferManagerOptions.java

...pache/spark/shuffle/writer/WriteBufferManager.java

...org/apache/spark/shuffle/writer/AddBlockEvent.java

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

@jerqi PTAL


Build pipeline

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kchri-nets sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


css modules + purifycss plugin = no css

Hey :)
I've been trying to use css modules and the purifycss plugin but with no luck :(
I am using webpack2 and extract-text-webpack-plugin.
webpack config:
{
        test: /\.css$/,
        loader: ExtractTextPlugin.extract({loader:"css-loader?minimize&modules&importLoaders=1"}),
},
...
plugins: [
  new ExtractTextPlugin({
      filename: "style.css",
      allChunks: true
    }),
  new purifyCSS({
     basePath: path.resolve(__dirname, 'static')
})

result:
   style.css  0 bytes          [emitted]

Can somebody help me with this?
All that I want is that style.css to have just the classes I use, not all of them.
Thank you!

@andreiconstantinescu
the following works fine for me:
 new ExtractTextPlugin(`style.${versionHash}.css`, {
      allChunks: true
    }),
    new PurifyCSSPlugin({
      basePath: buildPath,
      paths: [
        '*.html'
      ]
    }),

i believe its not working on your end because you are not passing it a glob in paths.

You didn't pass any paths to purifycss-webpack-plugin so I can imagine that purify doesn't find any used classes.
I have been trying to do the same with CSS modules and even passing a paths does not help. I suspect the issue is that with CSS modules the actual classnames are only written to disk after the JS bundle has been emitted. It looks like purifycss-webpack-plugin is running before that happens and only considering what it can find on disk. So it will never find the classnames of your css modules.

Running purify-css manually after webpack does work.
However I can imagine that if you're doing longterm caching using the file contents as a hash can result in issues if you run purify after the hash has been determined. For example if you run purify with different options or with a different version the resulting css will be different, but clients won't see this when the hash of the file remains the same. This would be especially bad if running purify resulted in a css issue. You can't fix the issue because the client will keep using the cached file with the error.
So I would probably have to recalculate the hash of the css file and replace it in JS bundle just to be safe.

Closing as this was answered. Feel free to re-open if relevant still.

Is it possible to allow it to work together with Webpack for css modules? 0xR's solution would work in theory but running purify manually would be especially inconvenient with hashes. And, if someone uses another plugin like html webpack plugin, which automatically injects hashed files into index.html, you would need to adjust not only hashes in css files, but also their references in index.html.
I think it is very important issue because CSS modules are really the future :)

@klis87 Given purify relies on heuristics that check whether or not some class is used or not and CSS Modules hides that information, I don't see how it could work out within the current logic.
It feels like CSS Modules would require a specific solution and that goes beyond what this plugin can provide.

Thank you @bebraw for clarifications, it definitely makes sense. So let's hope in the near future we will have this option somehow, maybe I will raise this issue on PurifyCSS plugin itself :)

The best workaround I found is to add some kind of a static string to localIdentName in css-loader and then whitelist that string in PurifyCSS. Ex:
// css loader
{
  loader: 'css-loader',
  query: {
    importLoaders: 1,
    localIdentName: 'MODULES_[hash:base64:5]',
    minimize: true,
    modules
  }
}

// purify
new PurifyCSSPlugin({
  ...
  purifyOptions: {
    whitelist: ['*MODULES*']
  }
}),

That seems to work fine for me. One funny interesting thing I thought of would be to use an emoji as your unique identifier. Just prefix all your CSS Modules classes with 🔥  or anything else you could think of. Unfortunately, the CSS parser complains when you use an emoji in the name of an animation, since the regex only checks against \w. I opened up a PR to allow this, but it seems like the project is pretty abandoned so the likelihood of it getting merged is probably slim.

@Vpr99 Could you open a documentation PR (add to readme) for that? Too good info to be lost in a comment. 👍

Will do when I have a sec later today :)


Expose ModifySettings Support in HcsShim.

This is required for Hot Add/Remove of Network Endpoints
Signed-off-by<EMAIL_ADDRESS>

Hi.
if (Model.IsMSEmployee && !Model.IsMSVendor) {
@madhanrm
thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
} else if (Model.HasCLA) {
@madhanrm
Thanks for having already signing the Contribution License Agreement.
We will now review your pull request.
} else if (!Model.IsSignificant) {
This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
}
else {
if (Model.IsMSEmployee && Model.IsMSVendor) {
@madhanrm,
    Thanks for your contribution.
    To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com
    The agreement will cover your contributions to all Microsoft-managed open source projects.

} else {
    @__madhanrm__,

    Thanks for your contribution.

    To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com
    It will cover your contributions to all Microsoft-managed open source projects.
}

}
Thanks, Microsoft Pull Request Bot

ping @dineshgovindasamy @jhowardmsft

ping @jhowardmsft

Am moving one of the error check "ErrComputeSystemDoesNotExist" to libNetwork and not eat the exception here.

I am adding few more helpers for HNS

Ping @jhowardmsft  . I need to vendor in these changes to libnetwork and docker. Can you merge this PR?

I'm generally OK with this now. @msabansal can you confirm?
Also @jstarks - are you OK with this approach? Thinking generic modify in the future (change memory etc) on a running container.

@jhowardmsft  Ping.

LGTM

Needs a rebase

Resolved conflicts, tested and updated the PR

@darrenstahlmsft , @jhowardmsft  took care of the review comments, tested and pushed the latest changes.

@madhanrm Thanks. This looks good to me, except that one comment left. I don't think that
func ModifyContainer(id string, request *ResourceModificationRequestResponse) error

fits with the rest of the functions here, and with the above changes, it only calls public methods in hcsshim so it should just be a simple lift and shift to the consumer.

@jhowardmsft  I moved the method out. Let me know how it looks now.
Thanks for the review.

Added one more comment to fix, but as soon as that is fixed LGTM 👍

Done.


feat: widget release

The historical tx port does not seem to work

Maybe wait for the widget discussion before the merge?


Adjust Personas to integrate knowledge about date and season

see Wrong answer when asking about season and date #9

Will add a variable DATUM (date) and JAHRESZEIT (season) in weather.py to be used in the prompt as seasonal and date related information.

done with https://github.com/ClemensGruber/climart-gptree/commit/40a28b43cd172e35e84be35635e60ce156466274


Semicolon's missing in a chapter of useState in React Docs(Beta).

I think that a semicolon should be added an example of syntax of useState in the tutorial.
now
const [state, setState] = useState(initialState)

toBe
const [state, setState] = useState(initialState);

or is there any intention of removing semicolon?
I just found that all examples are missing a semicolon in Beta version Docs.
Actually, examples of previous version documents have a semicolon, so.

I think semicolons are avoided intentionally as semicolons are primarily optional in React.

These are not meant to be runnable snippets of code, but and overview of the API definition.
This was actually fixed here: https://github.com/reactjs/react.dev/pull/5823 but I'm reverting it here: https://github.com/reactjs/react.dev/pull/6543


Is there open api spec for duffel apis?

It should be accessible via an authenticated GET call to /schemas/v1 yes 👍


Feature/ssl param mapi

This PR adds the SSL parameter to the constructor of the MAPI and it fixes an error caused by the inconsistency of the args of the responseHandler function of the MAPI with the one declared in the parent class. This solves #40 and #39.
How to test it
Since we don't have any test in place for the MAPI, you can manually test this in a standalone PHP script. You can create a new space for testing and use one of the examples from the MAPI:
$client = new \Storyblok\ManagementClient('YOUR_OAUTH_TOKEN');
$spaceId = 'SPACE_ID'; // The space id
$storyId = 'STORY_ID'; // The id of the Home story created by default in the test space
$payload = [
  "story" =>  [
    "name" =>  "Story Name",
    "slug" =>  "story-name",
    "id" =>  $storyId ,
    "content" =>  [
      "component" =>  "page",
      "body" =>  []
    ]
  ],
  "force_update" =>  1,
  "publish" =>  1
];

echo $client->put("spaces/{$spaceId}/stories/{$storyId}", $payload)->getCode();

If the code is 200 and the story has now the new name and slug assigned via API, it's ok.

Thanks, @thiagosaife! 🙏🏻


"Open file in editor" from terminal opens a new split, instead of changing focus to a different one

VSCode Version: 1.49.2
OS Version: Windows 10 Enterprise

Steps to Reproduce:

Have multiple "splits" (I think this is what VS Code calls them, like different files open at the same time. Basically different tabs)
Have some file left.cpp open on the left split and right.cpp open on the right split.
In the terminal, run echo "left.cpp:4" (some string that VS Code recognizes as a path to a file that it allows you to control-click to open file in editor)
With focus on right.cpp, ctrl-click on that link.

The result is that we open a new tab in the right split to refer to left.cpp. Even though left.cpp is already open and visible in the left split.
This is mildly annoying, and would be much nicer if the editor first checked if left.cpp was visible in any of the splits -- and if it was, navigate in that split (regardless of which split currently has focus).
I wouldn't call this a bug per se, since left.cpp does successfully get opened. More of a improvement request.

Does this issue occur when all extensions are disabled?: When I tried to check this:
$ code --disable-extensions .
Ignoring option disable-extensions: not supported for code.

I think this is by design since you can open a file in multiple panes and the right one was focused.

I think this is by design since you can open a file in multiple panes and the right one was focused.

Would it be possible to at least get a configuration option to get the different behavior? This may be by design but it is a design I find fairly annoying -- it is never the behavior I want and always results in momentary confusion.

We have a setting.

We have a setting.

Could you tell me what that setting is?


drop down

(Not an issue) Sorry, noob question. Is there an option to choose an element contained in a drop down menu?

You can choose just about anything with a css selector. However, you'd want to attach an onShow handler to the dropdown step that emulates a hovering over it so that the step appears correctly.

Thanks! Here's what I did for anyone Googling this:
onShow: function(tour) { $("#selector").show();}


[Legacy] template for static link: BuildMain.xml

Similar to static link in "non-legacy". Sorry. I will try to merge the pull requests with Main.cpp and include.xml.

Sorry, I couldn't find how to merge the 3 edits on a single edit in github.com. Next time I will check out the project. I have tested this for Windows, but it is similar to non-legacy, thus I think it will be similar in the other targets. Thanks

These solve this http://community.openfl.org/t/is-it-possible-to-statically-link-the-standard-hxcpp-dlls/1710/5

Awesome!


Initial commit

Hi @gillesvink,
I made a bunch of changes according to your review, so MVC should be properly separated now and all the tuple returns are gone! Much much cleaner like this already. The only thing I haven't done yet is split the classes up into functions (with the lru_cache you mentioned for the ShotGrid connection). I'm not entirely sure how to go about this yet so let's discuss this on a call or irl sometime soon! Thanks for the review :)


Kernel size can only be set as integers

When kernel size is set to a float for the newest version, a bug was reported.

you really need to say a bit more here.   am guessing that you are commenting on something that is neither a bug nor new, nor related to float / integer.

Sorry.
What is causing a bug is the radius that's set, e.g. using CC[fixedImage,movingImage,weight,radius]
When I used a float (0.75 here), it was fine but since I updated to the newest version, it causes a bug as:
Exception caught in ANTS:
/tools/devel/linux/ANTS/ANTs_git/Utilities/antsCommandLineParser.h:126:
itk::ERROR: CommandLineParser(0x22274b0): ERROR: Parse error occured during command line argument processing
ERROR: Unable to convert '0.75' to type 'j' as unsigned int
When I tried the same command using an older version of ANTS, it's still working.

the bug was in the older version - i.e. allowing you to set a float.  the CC radius is a voxel measurement.  you can thank @hjmjohnson for correcting this previous bug.

Is it possible to add in the help file, which values are set in mm and which values are in "voxel"

yes - feel free to make the additions yourself and create a pull request.
brian
On Tue, Jun 23, 2015 at 9:53 AM, Yundi Shi<EMAIL_ADDRESS>wrote:

Is it possible to add in the help file, which values are set in mm and
which values are in "voxel"
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/197#issuecomment-114513390.

cool. thanks for clearing the issue for me


#30 Update fetching content widht/height in updateMetrics

Hello! Very interesting bug, however I could not reproduce it
What are conditions to reproduce it? If I just scroll and then call updateMetics, content width and height are correct in my case
Also, why clientWidth and not offsetWidth? It does take into account borders
Thanks!

Yeah, sorry, it looks like it was my mistake. Btw, I don't why replacing on clientWidth solves the problem. I'm still investigating


Silly npm error keeps popping up every time I do something.

Error message was: npm WARN package.json<EMAIL_ADDRESS>'repositories' (plural) Not supported. Please pick one as the 'repository' field

Oh, I can't actually take that out.  It's for the CDN that I use.


BUG: As a developer, I want to understand why tests are failing in Spring '15

Test methods from 4 test classes are failing in my spring '15 managed package test org.

Which 4?

ACCT_HHAccounts_TEST: changeContactOwners
ERR_Handler_TEST: errorHandlingDisabled, errorsStoredInDbTdtmCustomConfigEmailErrors, testInactiveUserEmailBehavior
RLLP_OppRollup_TEST: testGivingRollupBatchHHAccount testGivingRollupBatchOne2One testOrgSoftCreditsHHAccount, testOrgSoftCreditsOne2One, testSoftCreditsHHAccount, testSoftCreditsOne2One
STG_SettingsManager_TEST (testPanelOppBatch)

I verified that the change that decreases the limit has been removed, for now:

@davidhabib ~ regarding the hardcoded value of 5, I must have done that because there was no other way to get this value from the platform, per https://salesforce.stackexchange.com/questions/62845/concurrent-batch-job-limit-of-2:
"[...]and hopefully there will be someway to identify this limit in Apex as there is not today."

wait, so are you saying that all test pass now in spring '15 without us doing any code change?

The jenkins build I kicked off yesterday against our gs0 test org to test the beta package failed with the same error:
http://ci.salesforcefoundation.org/view/uat/job/Cumulus_uat_managed_test_gs0/76/consoleFull#151252163474022756-574a-4673-bd0d-e114a2a1fd70

@ceiroa what org did you test in?

This is with a brand new dev org I created from https://www.salesforce.com/form/signup/prerelease-spring15.jsp.
This would match the stackoverflow post, where they said the limit change would be reverted.

To clarify, I'm investigating flex queue anyway, since we'll need it shortly. We might as well move to it in advance.


Bump version to 0.2.104

I'd like to get https://github.com/rust-lang/libc/pull/2415 into a release so I can use the new API in a change I'm working on for the nix crate, please.

r? @JohnTitor

Hey thanks for the PR! I'll r+ this once I clean-up the PR queue.

:pushpin: Commit c6ad015d15f2b87dc84d6b83db6abc77c0d19722 has been approved by JohnTitor


feat(archive): Add default name for artifact repository ref.

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[x] My builds are green. Try syncing with master if they are not.
[x] My organization is added to USERS.md.

@Ark-kun could I please request your feedback on this?


increase feed front size

Found that the feed font size at 15px was just not working well.
Here making it 18 which is in line with what you are using in the post textbox
im sure 17 is fine too/

See feedback here from community:
https://diamondapp.com/posts/7de6dad5a6158b244d7dce699e4ebdd525c4862d93f6ca442e3e1b6e887c2b22?tab=posts

agreed with Tijn. font size in feed was being too small imo


refactor seqs.get_translation and add method to rename seqs in a collection

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

42 of 52 (80.77%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.09%) to 91.231%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cogent3/core/new_sequence.py
10
12
83.33%

src/cogent3/core/profile.py
11
14
78.57%

src/cogent3/core/new_alignment.py
20
25
80.0%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/core/new_sequence.py
1
65.1%

src/cogent3/core/new_genetic_code.py
2
94.74%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
32479

Relevant Lines:
35601

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

42 of 52 (80.77%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.09%) to 91.287%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cogent3/core/new_sequence.py
10
12
83.33%

src/cogent3/core/profile.py
11
14
78.57%

src/cogent3/core/new_alignment.py
20
25
80.0%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/core/new_sequence.py
1
67.31%

src/cogent3/core/new_genetic_code.py
2
94.74%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
32500

Relevant Lines:
35602

💛  - Coveralls


Analyze projects and extract info

Python script to automate cloning and info extraction from 1k repos on GitHub

Nice, thanks @Deee92 !


{! foo }syntax is deprecated. Use@foo` syntax instead

Please undo this change or this warning ...
The basic {} and {! } syntax flow and are visually easy.  While the @ syntax makes it harder to differentiate words. Maybe its a dyslexia issue but this syntax is just harder to read and is a step back.
Example:
@Option()
{! Option() }
@Component
{! Component )
Or remove the warning about it being deprecated and leave it for the folks that want to use the old syntax.

This check is also bugged...
templ something(action string) {
{! Component }
}
Will give a warning on {! Component }
templ something(action string) {
if 1 == 1 {
{! Component }
}
}
Zero warning because there is no check done ...

I have raised a new issue for the diagnostic not working in if statements:
https://github.com/a-h/templ/issues/478
Closing this as the new syntax is a foundation for features that have already been developed.


Rewrite of model-adapter guide

Rewrite the guide on how to create a model-adapter

Closing due to github no longer assoication my fork/branch with this pr


Keyboard fixes for WK

Just tested for some days, feels soooo much better =)
any reason you are waiting with merging?

@mnewmedia stay tuned! this will never be merged but we will release the new keyboard architecture soon!

Hi,
Any ETA on the new keyboard release date? Chatting on ionic feels a bit horrible

@manucorporat
Any ETA on the new keyboard release date?

Waiting for the new keyboard release!!!

With the branch ngx-translate for IOS devices does not work properly.
Strings are not loaded, app shows the keys. WIth the native branch:
translation work as expected, however the UI screen on Keyboard show moves the entire screen up even the top bar.


Replacement for equinox.internal.if_mapped?

Hi, I noticed that equinox.internal.if_mapped has been removed in a recent version of equinox rather than added to the main package. What is the reason for this / what would a reasonable replacement be to replicate its behavior?
I have highly nested pytrees in my package, so if_mapped turns out to be very useful for saving memory when moving across vmap boundaries.

So this hooked into some JAX internals that are getting removed in a future version of JAX. You could maybe replicate the same behavior by arranging for something updated and similar yourself, but I'm not sure exactly what.
The fact that this used such internals is why it was undocumented in equinox.internal instead of the main namespace, as I knew this might need to happen at some point!
FWIW I never really found a use-case for this in my own work as it meant that the output shape was hard to track.
Sorry that I can't give you better news!

This is okay, makes sense! It is probably best practice to be explicit about the out_axes anyway. The best replacement for the behavior is probably to just create an out_axes pytree explicitly from a filter_spec, like the following
out_axes = jax.tree.map(lambda x: 0 if x else None, filter_spec)


RP scaffolder should not decorate model with  [BindProperty]  in delete

[BindProperty] in not needed in the delete page. There is nothing to bind on the delete page - it uses ID to get the model.
To repo, follow RP tutorial.

Content issue. Can you please have some one on your side take care of this?

https://github.com/aspnet/AspNetCore.Docs/issues/15616 tracks documenting that.


docs: simplify import map generation

Hopefully this is easier to understand and maintain
Depends on #1307
What I did

clean up importMap code, replacing several truly awful hacks with a smaller number of merely gross hacks.

Testing Instructions

pages, demos, playgrounds

When loading a playground demos:
index.html:1 Uncaught TypeError: Failed to resolve module specifier<EMAIL_ADDRESS>Relative references must start with either "/", "./", or "../".

index.html:1 Uncaught TypeError: Failed to resolve module specifier<EMAIL_ADDRESS>Relative references must start with either "/", "./", or "../".

This seems to be an issue on main right now too

yeah the playgrounds don't work in localhost right now. check the dp


Error while running protractor tests

Steps to reproduce and a minimal demo of the problem
npm run webdriver-update
npm run webdriver-start
npm run serve.e2e
npm run e2e
Current behavior
[23:33:01] I/direct - Using ChromeDriver directly...
[23:33:01] I/launcher - Running 1 instances of WebDriver
[23:33:02] E/launcher - Error: ReferenceError: Zone is not defined
    at Object.<anonymous> (/Users/jakepartusch/Documents/angular/angular2-seed-advanced/modules/@angular/core/testing/fake_async.ts:8:34)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)
    at Module.require (module.js:466:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/jakepartusch/Documents/angular/angular2-seed-advanced/modules/@angular/core/testing.ts:5:3)
    at Module._compile (module.js:541:32)
[23:33:02] E/launcher - Process exited with error code 100

Other information
Related?
https://github.com/angular/protractor/issues/3181

Thanks @JakePartusch! not sure, I'll see what I can find out.

Found it, protractor needed this: require("zone.js/dist/zone-node");
Thanks again for the report 👍

@NathanWalker What's your thought on this? https://github.com/angular/protractor/issues/4364


Adapt flyway to manage Registry database migrations

Describe the issue
As a developer, i'd like to adapt flyway to manage Registry database migrations.
Additional context
Have it integrated with the existing workflow.
Definition of done
Flyway is integrated with the existing workflow.

#192 can leverage this deliverable.

Document a plan to have this integrated to registry prod with zero downtime:

set up a new set of patroni db
set up a new registry api service using the updated deployment config with pre-hook migration container

ensure to pass the right params so dc will rollout on image change from IS platsrv-registry-flyway:prod

set up necessary nsp rules so the pre-hook migration container can run against new patroni master db
check inside new patroni master db to see if there is a schema table and schemas are up-to-date
migrate prod data to new patroni master db
if everything is running well, do a cutover to the new registry api from the oc route


CI for Node

✕ Contains the compiled JavaScript (7 ms)
✕ Initializes with two players (4 ms)
✕ Starts the game with a random player (1 ms)
✕ Sets the current player to be whoever it is not (1 ms)


Introduce teleport validation data provider

XRTK - Mixed Reality Toolkit Pull Request
Overview
Please see https://github.com/XRTK/XRTK-Core/pull/727

/azp run

Probably won't pass until the package target is updated to the latest preview release

@FejZa just pointed that out to me @StephenHodgson  :D
Thought it had already been done, but fixed now


Synchronization for settings

VSCode Version:1.7.1
OS Version:win10 14959

Steps to Reproduce:

Add synchronization for both settings and extensions

For settings, there is already an extension out there, try ext install EditorConfig in command palette.

@MuNaiYi520 Can you add more details? Sync across workspaces? Machines ?

@ramya-rao-a I hope to be able to synchronize the settings on different computers, work is a computer, home to continue to work is another computer.

There are quite a few issues logged for this purpose.
#10114
#9999
#2743
Please add your thoughts/upvotes there


applying plugin for url without /intel?

https://intel.ingress.com/?ll=43.412921,3.696964&z=15&pll=43.412921,3.696964 plugin doesn't start for URL like that because of missing intel between / and ?
fix makes it work

This repo is unmaintained.
Better switch to IITC-CE


Generated sidebar.js doesn't load

Describe the bug
sidebar.js generated file does not load on docusaurus start
Expected behavior
The sidebar.js file that is generated should load and correctly render the sidebar.
Current behavior
$ yarn start
yarn run v1.22.19
$ docusaurus start --host <IP_ADDRESS>
[INFO] Starting the development server...
[ERROR] Sidebars file at "/home/garth/projects/saascrud/phasetwo-docs/api/sidebar.js" failed to be loaded.
[ERROR] Loading of version failed for version current
[ERROR] Error: Invalid sidebar items collection `{"type":"doc","id":"phase-two-admin-rest-api"}` in sidebar 0: it must either be an array of sidebar items or a shorthand notation (which doesn't contain a `type` property). See https://docusaurus.io/docs/sidebar/items for all valid syntaxes.
    at normalizeSidebar (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:49:15)
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:57:66
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:13469:38
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:4967:15
    at baseForOwn (/home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:3032:24)
    at Function.mapValues (/home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:13468:7)
    at normalizeSidebars (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:57:29)
    at loadSidebars (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/index.js:81:74)
    at async doLoadVersion (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:91:34)
    at async loadVersion (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:113:28)

Possible solution

Steps to reproduce

See code here: https://github.com/p2-inc/phasetwo-docs/tree/xgp/panetworks-openapi

Start with an existing docusaurus 2.3.1 repo
run yarn add docusaurus-plugin-openapi-docs
run yarn add docusaurus-theme-openapi-docs
update the docusaurus.config.js file with the docusaurus-plugin-openapi-docs and @docusaurus/plugin-content-docs plugins, configured like this: https://github.com/p2-inc/phasetwo-docs/blob/xgp/panetworks-openapi/docusaurus.config.js#L250
run yarn docusaurus gen-api-docs all
run yarn start
see error above

Context
I'm unable to render the generated API documentation in docusaurus.
Your Environment

Version used: 1.7.0
Environment name and version: Node.js v19.1.0. Yarn 1.22.19.
Operating System and version (desktop or mobile): Ubuntu 20.04
Link to your project: https://github.com/p2-inc/phasetwo-docs/tree/xgp/panetworks-openapi

Hi @xgp, the versions you referenced are incompatible as documented on the doc site and README:
Compatibility Matrix

Docusaurus OpenAPI Docs
Docusaurus

1.x.x
>=2.0.1 <2.3.0

2.x.x (beta)
>=2.3.0

Thanks @sserrata . I updated to docusaurus 2.2.0 and the plugin version 1.7.0. I am still encountering problems with my configuration. Now the generate task fails:
$ yarn docusaurus gen-api-docs all
yarn run v1.22.19
$ /home/garth/projects/saascrud/phasetwo-docs/node_modules/.bin/docusaurus gen-api-docs all

   ╭──────────────────────────────────────────────────────────────────────────────────────────╮
   │                                                                                │
   │                              Update available 2.2.0 → 2.4.0                              │
   │                                                                                │
   │    To upgrade Docusaurus packages with the latest version, run the following command:    │
   │     `yarn upgrade @docusaurus/core@latest @docusaurus/plugin-google-analytics@latest     │
   │        @docusaurus/preset-classic@latest @docusaurus/theme-live-codeblock@latest`        │
   │                                                                                │
   ╰──────────────────────────────────────────────────────────────────────────────────────────╯

/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/versions/files.js:123
        throw new Error(`The docs folder does not exist for version "${versionName}". A docs folder is expected to be found at ${path_1.default.relative(context.siteDir, contentPath)}.`);
              ^

Error: The docs folder does not exist for version "current". A docs folder is expected to be found at api.
    at getVersionMetadataPaths (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/versions/files.js:123:15)
    at async createVersionMetadata (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/versions/index.js:97:68)
    at async Promise.all (index 0)
    at async readVersionsMetadata (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/versions/index.js:150:30)
    at async Object.pluginContentDocs [as plugin] (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:32:30)
    at async initializePlugin (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/core/lib/server/plugins/init.js:83:32)
    at async Promise.all (index 7)
    at async initPlugins (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/core/lib/server/plugins/init.js:91:21)
    at async externalCommand (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/core/lib/commands/external.js:17:21)
    at async file:///home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/core/bin/docusaurus.mjs:213:3

Node.js v19.1.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Is this a flaw in my configuration? https://github.com/p2-inc/phasetwo-docs/blob/xgp/panetworks-openapi/docusaurus.config.js#L252 I have read through the docs and examples, and I'm unable to find the problem
  ...
  plugins: [
    [
      'docusaurus-plugin-openapi-docs',
      {
        id: "openapi",
        docsPluginId: "api",
        config: {
          phasetwo: { // Note: petstore key is treated as the <id> and can be used to specify an API doc instance when using CLI commands
            specPath: "openapi.yaml", // Path to designated spec file
            outputDir: "api", // Output directory for generated .mdx docs
            baseUrl: "/api",
            sidebarOptions: {
              groupPathsBy: "tag",
            },
          }
        }
      },
    ],
    [
      "@docusaurus/plugin-content-docs",
      {
        id: "api",
        path: "api",
        breadcrumbs: true,
        routeBasePath: "api",
        include: ["**/*.md", "**/*.mdx"],
        sidebarPath: "api/sidebar.js",
        docLayoutComponent: "@theme/DocPage",
        docItemComponent: "@theme/ApiItem", // add @theme/ApiItem here
      },
    ],
  ],
  themes: ["@docusaurus/theme-live-codeblock","docusaurus-theme-openapi-docs"],
  ...

Removing the plugin-content-docs and running generate works to create the api dir and generate the .mdx files, but then I'm back to the same spot when I add it back and try to run yarn start.
$ yarn start
yarn run v1.22.19
$ docusaurus start --host <IP_ADDRESS>

   ╭──────────────────────────────────────────────────────────────────────────────────────────╮
   │                                                                                │
   │                              Update available 2.2.0 → 2.4.0                              │
   │                                                                                │
   │    To upgrade Docusaurus packages with the latest version, run the following command:    │
   │     `yarn upgrade @docusaurus/core@latest @docusaurus/plugin-google-analytics@latest     │
   │        @docusaurus/preset-classic@latest @docusaurus/theme-live-codeblock@latest`        │
   │                                                                                │
   ╰──────────────────────────────────────────────────────────────────────────────────────────╯

[INFO] Starting the development server...
[ERROR] Sidebars file at "/home/garth/projects/saascrud/phasetwo-docs/api/sidebar.js" failed to be loaded.
[ERROR] Loading of version failed for version current
[ERROR] Error: Invalid sidebar items collection `{"type":"doc","id":"i/phase-two-admin-rest-api"}` in sidebar 0: it must either be an array of sidebar items or a shorthand notation (which doesn't contain a `type` property). See https://docusaurus.io/docs/sidebar/items for all valid syntaxes.
    at normalizeSidebar (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:49:15)
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:57:66
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:13469:38
    at /home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:4967:15
    at baseForOwn (/home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:3032:24)
    at Function.mapValues (/home/garth/projects/saascrud/phasetwo-docs/node_modules/lodash/lodash.js:13468:7)
    at normalizeSidebars (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/normalization.js:57:29)
    at loadSidebars (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/sidebars/index.js:81:74)
    at async doLoadVersion (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:91:34)
    at async loadVersion (/home/garth/projects/saascrud/phasetwo-docs/node_modules/@docusaurus/plugin-content-docs/lib/index.js:113:28)
[INFO] Docusaurus version: 2.2.0
Node version: v19.1.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It does appear that the generated sidebar.js isn't valid against the docusaurus spec https://github.com/p2-inc/phasetwo-docs/blob/xgp/panetworks-openapi/api/sidebar.js

@sserrata Thanks for the help!


Support forward slash in Windows paths

Windows accepts forward slashes as path component separators in most of their API's (and in explorer.exe as well as cmd.exe). It would be nice if neo-tree.nvim did the same.
This does not work on Windows:
require("neo-tree.command").execute({ toggle = true, dir = "foo/bar" })

Looks like it tries to open a non-existant path.
This does work:
require("neo-tree.command").execute({ toggle = true, dir = "foo\\bar" })

And the contents of bar is shown.

Hey @miversen33
Is there any change this issue can be solved with (or something similar to) #1023 ?

So the gist of this request is basically, whatever function actually resolves the path, it should accept this kind of pathing as well (though do we make it only accept this path if the os is windows? Idk).
As an alternative, we could cheese it and have the filesystem.navigate function just convert all foo/bar references to foo\\bar references (basically convert / -> \\ behind the scenes). I don't imagine it would be tough to do either. Just adding the following line
state.path = state.path:gsub('\', '//')

to lua/neo-tree/sources/filesystem.init#L137
Thinking about it, I don't actually hate that idea. @cseickel thoughts on this?

So the gist of this request is basically, whatever function actually resolves the path, it should accept this kind of pathing as well (though do we make it only accept this path if the os is windows? Idk).
As an alternative, we could cheese it and have the filesystem.navigate function just convert all foo/bar references to foo\\bar references (basically convert / -> \\ behind the scenes). I don't imagine it would be tough to do either. Just adding the following
state.path = state.path:gsub('\', '//')
path_to_reveal = path_to_reveal:gsub('\', '//')
path = path:gsub('\', '//')

to lua/neo-tree/sources/filesystem.init#L120
Thinking about it, I don't actually hate that idea. @cseickel thoughts on this?

I think you have your slashes reversed. The request is to support forward slashes, unix style. Your suggestion is about escaping backslashes.
I'm guessing there is a branch of code somewhere that interprets a path based on windows conventions if the os is windows which is not recognizing the use of a unix style path separator. I'd need more details on where the problem is before I can make any suggestions.
I honestly never knew that windows would accept both unix style and windows style separators. It seems completely insane to me. What happens if you use both? Does backslash become an escape character or an alternate path separator?

I think you have your slashes reversed. The request is to support forward slashes, unix style. Your suggestion is about escaping backslashes.

Not quite. I am replacing forward slashes with escaped backslashes. This means a user can request directory foo/bar and the filesystem source will see it as foo\\bar (which is what it expects currently I believe). It seems a bit hacky, but unless I am mistaken, it shouldn't cause any issues with vim.loop (btw this is now vim.uv) or plenary. It is essentially forcing consistent paths before we start messing about with the path string

I honestly never knew that windows would accept both unix style and windows style separators. It seems completely insane to me. What happens if you use both? Does backslash become an escape character or an alternate path separator?

So fun fact, apparently windows treats / and \ the same. I can (for example) navigate to C:/Users\miver and it works just the same as C:\Users\miver and C:/Users/miver. Tested quick in powershell, command prompt and the file explorer. It seems NTFS doesn't care.
Because who needs consistency right? :upside_down_face:

If I understand correctly, in cmd the escape char is ^ and in powershell, it's <backtick> (damn how do I put a backtick in markdown lol)
Both cases, \ does not mean to escape something and is used for path separator.
Neovim's core team seems to prefer using / in Windows: https://github.com/neovim/neovim/issues/15220 (link is broken in that issue, see this commit for details).
But old vim functions prefer backslashes. :=vim.fn.getcwd() => C:\... so now it's a complete mess.

Because who needs consistency right? 🙃

so now it's a complete mess.

100%
@miversen33 I think you are on the right track, but the place to enforce that consistency is probably where the user input is first taken in, in the command module. Maybe in this function?
https://github.com/nvim-neo-tree/neo-tree.nvim/blob/7f6fa04dbd8e8c79d1af33bc90e856b65d8641da/lua/neo-tree/command/parser.lua#L81

I noticed this inconsistency when digging into #1026 and I'm still not sure why there hasn't been much problem in neo-tree's code yet.
1. Opening file.
Let's try to open C:/Users/User/AppData/Local/nvim/lua/target{1..5}.lua while CWD = C:/Users/User/AppData/Local/nvim.
There's a lot of ways to do it.

:e lua/target1.lua or :e lua\target1.lua
:e C:/Users/User/AppData/Local/nvim/lua/target2.lua (Neotree uses this I think?)
:e C:\Users\User\AppData\Local\nvim\lua\target3.lua
:e ~/AppData/Local/nvim/lua/target4.lua
:e ~\AppData\Local\nvim\lua\target5.lua

2. Look at :ls
The results of files opened with each command correspondes to below.

lua\target1.lua
~/AppData/Local/nvim/lua/target2.lua
~\AppData\Local\nvim\lua\target3.lua
~/AppData/Local/nvim/lua/target4.lua
~\AppData\Local\nvim\lua\target5.lua

So, as you can see, C:/Users/User is always substituted by ~ but the type of slashes does matter.
3. Look at vim.fn.expand("%:p")

C:\Users\User\AppData\Local\nvim\lua\target1.lua
C:\Users\User/AppData/Local/nvim/lua/target2.lua !!!
C:\Users\User\AppData\Local\nvim\lua\target3.lua
C:\Users\User/AppData/Local/nvim/lua/target4.lua !!!
C:\Users\User\AppData\Local\nvim\lua\target5.lua

Now, here's where it starts to get weird.
The result of 2 and 4 have / and \\ mixed up because of the :p.
4. mksession!
Let's save the current session with :mks! which results in a file named Session.vim right inside $CWD.
When you peek inside this file, you'll see lines that prints as below, which has all backslashes replaced with /,
and uses ~.
badd +1 `lua\target1.lua`
badd +1 `~/AppData/Local/nvim/lua/target2.lua`
badd +1 `~/AppData/Local/nvim/lua/target3.lua`
badd +1 `~/AppData/Local/nvim/lua/target4.lua`
badd +1 `~/AppData/Local/nvim/lua/target5.lua`

This behavior is however different from vim which does not substitute backslashes by default.
Introduced in this commit,
related issue.
(Use :h sessionoptions to change the behavior. nvim deletes this option and make / the default.)
vim.fn.getcwd()
This however returns path with all backslashes.
The biggest issue that should be caused by this inconsistency is is_subpath where string.sub(path, 1, string.len(base)) == base might not be true due to difference in slashes.
However neo-tree is surprisingly working as expected in most cases probably thanks to windowize_path but there are certain places where this is not used but should be critical. Like here. I'm quite confused now lol.
@cseickel Maybe we should wrap all calls to vim.fn.expand, getcwd, etc and vim.api.nvim_buf_get_name and substitute backslashes to / and force to use forwardslash throughout the project? Or shall we simply keep it as-is?

I think you are on the right track, but the place to enforce that consistency is probably where the user input is first taken in, in the command module. Maybe in this function?

Maybe we should wrap all calls to vim.fn.expand, getcwd, etc and vim.api.nvim_buf_get_name and substitute backslashes to / and force to use forwardslash throughout the project? Or shall we simply keep it as-is?

By doing this, we (as Neo-tree) are making the active decision that we will sanitize paths before passing them to the underlying source to handle. Not to say that's a bad thing, just a decision that I didn't feel comfortable making (which is why I moved the suggestion into the filesystem source instead of above in the command resolution, which is where I was initially looking).
IMO, while taking this approach may be the best decision, it might be wise to take it as a 2 step approach. Resolving this direct issue (allowing forward slashes in the path), and then targeting path sanitation/fixing for 3.x
My biggest concern is that one of these approaches is much smaller and easier to validate/verify than the other :)

By doing this, we (as Neo-tree) are making the active decision that we will sanitize paths before passing them to the underlying source to handle.

That's a good point. I didn't consider that someone could be on windows but still be passing an argument to a source that interacts with a *nix host such as a docker container or remote host.
Given that, your suggestion of handling within the filesystem source is a good fix for this specific issue.
Longer term we should handle paths in a consistent manner throughout the plugin and external sources. As @pysan3 pointed out, the issue is complicated and there are likely many edge cases waiting to be found within our codebase. I think we should drop all representations of paths as strings and replace them with plenary Path objects or come up with our own abstraction that can handle the windows/nix differences properly. Hopefully Plenary's implementation works or we can get fixes in where needed. This might be a v4.x change.

That's a good point. I didn't consider that someone could be on windows but still be passing an argument to a source that interacts with a *nix host such as a docker container or remote host.

I appreciate you :)
I'll slap together a PR for this this evening, the change is really small so it shouldn't take me too long to do and test.

I think we should drop all representations of paths as strings and replace them with plenary Path objects or come up with our own abstraction that can handle the windows/nix differences properly. Hopefully Plenary's implementation works or we can get fixes in where needed

IIRC Plenary Path's are a touch buggy but I haven't touched them since I was playing around with Telescope back in the day. I do think letting pathing be someone else's problem is a great solution. Properly handling paths is hard.

 I'm totally for the sanitizing everything with the vim.fs.normalize approach, though IIRC there's some interesting problems and discussion around that subject in neovim recently..
ok here's the pr..
it looks like using this to sanitize might be ok now? https://github.com/neovim/neovim/commit/8a7e3353eb5bffb10015254917361266b4b20511

Quick test with vim.fs.normalize nets the below results
:lua print(vim.fs.normalize("C:\\Users/miver"))
C:/Users/miver

I think we might be able to get away with using normalize in yes. It will take more testing to be sure it works as expected generally though :)

Could you also stress test non ascii chars as well as emojis included in the path?
We might also have to check how the git related codes work since Windows Git uses a weird encoding for non-ascii characters.
This just came to my mind but would it be fixed if we execute chcp 65001 every time before the git command? I don't have a Windows PC right now so I'm sorry to bother you.

Could you also stress test non ascii chars as well as emojis included in the path?
We might also have to check how the git related codes work since Windows Git uses a weird encoding for non-ascii characters.

I think we are probably safe. I made a truly horrendous discovery in that NTFS allows emojis in your path

Using vim.fn.normalize seems to be the best way to handle this whole path escaping thing IMO

This just came to my mind but would it be fixed if we execute chcp 65001 every time before the git command? I don't have a Windows PC right now so I'm sorry to bother you.

I have no idea what this is so I can't really speak to it unfortunately

On my linux machine (where the path C:\ is nonsensical) and the function still cleaned it up to something that is "standard". So it is most likely (speculating as I don't feel like digging into the vim source to verify) just running some string regex replaces to make the path "normal" (hence the function name).

I will fetch dis.
copy-la-pasta, here's the code fasta!
from https://github.com/neovim/neovim/blob/a3f4598226c4d01e4fbc41181a1ad21793862fe3/runtime/lua/vim/fs.lua#L331

--- Normalize a path to a standard format. A tilde (~) character at the
--- beginning of the path is expanded to the user's home directory and any
--- backslash (\\) characters are converted to forward slashes (/). Environment
--- variables are also expanded.
---
--- Examples:
--- <pre>lua
---   vim.fs.normalize('C:\\\\Users\\\\jdoe')
---   --> 'C:/Users/jdoe'
---
---   vim.fs.normalize('~/src/neovim')
---   --> '/home/jdoe/src/neovim'
---
---   vim.fs.normalize('$XDG_CONFIG_HOME/nvim/init.vim')
---   --> '/Users/jdoe/.config/nvim/init.vim'
--- </pre>
---
---@param path (string) Path to normalize
---@param opts table|nil Options:
---             - expand_env: boolean Expand environment variables (default: true)
---@return (string) Normalized path
function M.normalize(path, opts)
  opts = opts or {}

  vim.validate({
    path = { path, { 'string' } },
    expand_env = { opts.expand_env, { 'boolean' }, true },
  })

  if path:sub(1, 1) == '~' then
    local home = vim.uv.os_homedir() or '~'
    if home:sub(-1) == '\\' or home:sub(-1) == '/' then
      home = home:sub(1, -2)
    end
    path = home .. path:sub(2)
  end

  if opts.expand_env == nil or opts.expand_env then
    path = path:gsub('%$([%w_]+)', vim.uv.os_getenv)
  end

  return (path:gsub('\\', '/'):gsub('/+', '/'):gsub('(.)/$', '%1'))
end

yeah, it's simply transforming it, not making sure it exists. It does do some expansion of env vars though, so that's cool. I don't know if that helps, but it's cool.
shocking about the emoji thing.. 🤷♂
I'm envisioning a dystopian future full of filesystems that look like
C:/🎁/👻/😆/🐱👤/🏎/🥳/(╯°□°）╯︵ ┻━┻/Q2 fiscal year 1323/straightLaced_biznassREPORTZ.🦅
we will soon have to support the .🦅 file extension.. you have been warned.

I've submitted PR #1051 that should resolve this.  I am going to close this issue out, though if my resolution did not fix this, please either tag me on this so it can be reopened, or open a new issue :)


ROWAN_PROJECTS_HOME ... env var pointing to shared clone directory ...

Change installation scripts and docs to use ROWAN_PROJECTS_HOME instead of ROWAN_HOME ...
This env var will be used by Jadeite as well ...

will need to coordinate with @ericwinger so that Jadeite release and PR #112 done together.

This is not complete until I get my code checked into master

merged to master (PR #112)


Changes in Capitalize methods in WordUtils class.

Some minor changes in capitalize and uncapitalize methods. I annotated useless methods as depreciated, do some refactorization and duplication elimination in delimeters varargs. This is second pull request after some useful advices from community.

Your changes introduce the conversion of the char array into a HashSet and back again into an array. This is way too expensive. Keep the original array and iterate through it. If you want to check for duplicates, you may create a 2nd array and add each processed character. Then you can check any new delimieter character for the index in the 2nd array first.

Yes...You have right. I completely removed duplication elimination as too much overhead even with an Array.


Remove grammatical error from first line

Error in the first paragraph of whitepaper in API Documentation.
Whitepaper title: A Pragmatic Approach to Rock Your API Strategy
present at : https://wso2.com/whitepapers/a-pragmatic-approach-to-rock-your-api-strategy/
under heading "1. API First Concepts":
"A very easy analogy might be: .... Most people have no clue about how a car works under the hood, but knows that...
knows should be changed to know as people is a plural word.

@tharikaGitHub Can you please update on this issue?

@arshita-kakkar Thank you for pointing this out. We will correct it and let you know.

This is fixed now


Add missing "+" on SV flags.

Without the "+", Verilator interprets the argument as a module name -- this PR fixes the CLI arg.
Manually verified with a small SystemVerilog example. :)

Thanks for the fix!