Highlight context provider is not showing up

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: MACOSX
- Continue: .47
- IDE: Jetbrains

Description

As in the screenshot attached after adding context provider highlights is not showing. Rest of the options are coming up. Add more context provider button also not working.
Below is the configuration
"contextProviders": [
{
"name": "highlights"
},
{
"name": "open",
"params": {}
},
{
"name": "code"
},
{
"name": "diff"
},
{
"name": "codebase"
},
{
"name": "folder"
}
],
To reproduce

Goto continue chat.
Enter @
Highlights options not showing up

Log output
No response

https://github.com/continuedev/continue/blob/eba3aba1fd49c51a565d0d5e4948b65f23a2b188/core/context/providers/index.ts#L39-L44
Both the outline and highlight context provider are currently commented out.

I have the same problem on Linux.

@rezaalavi @majuansari @jasonwang178 - We've left these commented out since there's a few bugs with both the outline and highlights context providers. Right now it isn't a high priority for us to get them fixed, but we'd welcome a PR if anyone is interested in fixing them!
In the meantime, we've updated the docs to remove those context providers from the list of built-ins.
https://github.com/continuedev/continue/pull/1561


Make code snippets of classes

There are many cases where user funcs are implemented or the such

This is what I get:

This is what I would need:


Apparent Bug in 06-deferred-steps.ts

I'm sorry I can't post the entire stack trace - I work on a closed system...
Running 06-deferred-steps.ts in VS Code:
   Error: the number of constructor arguments in in the derived class bodyClass must be >= than [sic] the number of constructor arguments of its base class.
   at /....../node_modules/inversify/lib/planning/planner.js:111:27
    :

02-hello-world.ts  also fails with same error.
But all the rest of the samples worked for me.
(I'm only looking at TypeScript ones)

I can't reproduce this... what versions of Node.js and Typescript are you using?
Also, if you're just running the samples... surely the stack trace should not contain anything sensitive?

I'm running on Node 10.13, TS ^3.4.1.
It's not a sensitivity issue, it runs on an air-gapped system.  I can't just cut and paste it - I'd literally have to retype the whole thing.  (Makes working with open source projects a hassle, believe me, I know).
Let me try to provide more detail, but be aware this is rekeyed from the real stack trace so....
as posted before, the stack trace begins with:
Error: the number of constructor arguments in in the derived class bodyClass must be >= than [sic] the number of constructor arguments of its base class.
at /....../node_modules/inversify/lib/planning/planner.js:111:27
Followed by (abbreviated):
at Array.forEach
at _createSubRequests ... inversify/lib/planning/planner.js:94:20
at Object.plan .... inversify/lib/planning/planner.js:136:9
at  inversify/lib/container/container.js:317:37
... more lines from Container
at  .... workflow-executor.js:92:65
at ....several more lines from executor (step, Object, step, Object..)
at NewPromise ()
at __awaiter
...
at workflow-queue-worker.js:117:60
... more queue worker lines...  WorkflowQueueWorker, step, Object.next, fulfilled)
It looks like at the node_modules level, the version of inversify that got installed looks to be 4.14.0
Hope this helps.  --jfk

Any news on this issue? I am facing the same error within pure JS (without TS).
The problem is related to thenRun method (inline step) - when it is removed, workflow has finished successfully.
Thanks,
Jan

Same issue when trying with Node 18 and typescript 4.8.4. Perhaps related to https://github.com/inversify/InversifyJS/issues/522


AutoLayout crash

"NSLayoutConstraint for (null): Constraint must contain a first layout item"
line 222:  UITableView *tableView = self.brc_context.fakeTableView; is nil

I got same issue when i used in a UITableViewController, as a UISearchController's results controller.
I think, because a UITableViewController's tableView doesn't have a superView, so [self brc_insertFakeTableView]; (L305) were not called.

I use these with uicollectionView. I created two kind of app, with and without storyboard. Without storyboard works fine.
ok thx for advice

Moving my code to
- (void)viewDidAppear:(BOOL)animated
fixed it for me. I thought viewDidLoad would be sufficient but apparently it was not haha

Setting bottomRefreshControl after you added tableView to view and set the layout constraint of the tableView:
self.view.addSubview(tableView)
tableView.snp.makeConstraints { (make) in
    make.top.equalTo(headerView.snp.bottom)
    make.left.bottom.right.equalToSuperview()
}

tableView.addBottomRefreshControl(target: self, selector: #selector(loadMoreAction))

Update:
In UITableViewController, it's still crash, move to UIViewController or using another framework, like: MJRefresh


WiP - XCLI, WaitForDevice, InstanceFormat, AttFilter

This patch introduces the Executor CLI, the wait command for the Executor binaries, instance format expectations, and attachment filtering.

[X] Executor CLI Interface
[X] Instance Format Expectation

[X] Instance Format Expectation Tests

[ ] Attachment Filtering

(cc: @clintonskitson)

[Current coverage][cc-pull] is 43.76%

Merging [#89][cc-pull] into [master][cc-base-branch] will decrease coverage by -0.66%

@@             master        #89   diff @@
==========================================
  Files            17         17
  Lines          1357       1378    +21
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            603        603
- Misses          716        737    +21
  Partials         38         38

Powered by Codecov. Last updated by [fff734d...bf17e6d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/emccode/libstorage/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/emccode/libstorage/compare/fff734d06b13efaf122450e7962777b590ac197c...bf17e6d0be2b8cb5a4af45d95e6ba10c27417537
[cc-pull]: https://codecov.io/gh/emccode/libstorage/pull/89?src=pr


Feature: config hideFromIndex for all fields inside ResourceNavigationTab

It will be very useful to have options at ResourceNavigationTab to hide from index all the fields listed in it.

You can use the fieldsForDetail.


Low Fantasy Gaming changes for luck attribute

Changes / Comments
Luck is a special attribute that functions a little differently from the rest. I've taken away a few fields that are not associated with Luck, modified the roll template to account for these changes, and added a dropdown for luck (attribute) saves. New column width style associated with luck added to css as well.

Still not a github expert; not sure what is up with the first two commits. One is old, and the other has no diffs? I'm trying to commit the changes to Luck Attribute diffs.

Is the end result what you want? Of so, doesn't matter much. The commits looks differently bc you submit them directly from your master branch.

Yes, I think the end result will be the same. Thanks for taking a look; appreciate what you do!

Added solution as requested per:
[Low Fantasy Gaming] Initiative: suggested changes. #4986
Initiative now has a checkbox toggle for Classic vs Deluxe roll method. Deluxe is checked by default.
In regards to:
[Low Fantasy Gaming] Crit damage: Has to be filled manually. #4985
Without a way to evaluate the maximum result of a roll expression I don't know how to parse and evaluate it myself. Suggest closing this request as I will not be able to fulfill it.

added default value for hidden init toggle attribute

@dedurrett Thanks for the detailed comments and following up on those Issues.


MaterialState.pressed is missing when pressing button with keyboard

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Run following application on Web or Desktop:

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Bug',
      home: Center(
        child: FilledButton(
          autofocus: true,
          onPressed: () {},
          style: ButtonStyle(
            backgroundColor: MaterialStateProperty.resolveWith(
              (states) {
                print(states);
              },
            ),
          ),
          child: const Text('button'),
        ),
      ),
    );
  }
}

Press Space or Enter on keyboard and see what is printed in the console.

Click on the button with mouse and see what is printed in the console.

Expected results
Pressing Space or Enter should cause MaterialState.pressed to be included in set of states. See more in specs According to https://m2.material.io/design/interaction/states.html#pressed.
Actual results
MaterialState.pressed state is missing when pressing button with keyboard. It works properly when clicking button with mouse
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.6, on Ubuntu 23.04 6.2.0-27-generic, locale en_US.UTF-8)
    • Flutter version 3.10.6 on channel stable at /home/kernel/work/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (4 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 15.0.7
    • cmake version 3.25.1
    • ninja version 1.11.1
    • pkg-config version 1.8.1

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /home/kernel/work/common/idea
    • Flutter plugin version 75.1.3
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 23.04 6.2.0-27-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Hi @radzish. Thanks for filing this issue. I am able to reproduce this on the latest master and stable channels. When Space or Enter is pressed on the keyboard, only {MaterialState.focused} state is seen while onPressed occurs. Otherwise, clicking on the button we have {MaterialState.focused, MaterialState.hovered, MaterialState.pressed}.
stable, master flutter doctor -v

[✓] Flutter (Channel stable, 3.10.6, on macOS 13.0 22A380 darwin-arm64, locale
    en-NG)
    • Flutter version 3.10.6 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (4 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

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

[✓] Android Studio (version 2022.2)
    • 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
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        •
      android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 14 (mobile)          • 1A122DE2-0CAB-4C3E-A395-691BF27D626F • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                •
      darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)                • chrome                               •
      web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[✓] Flutter (Channel master, 3.14.0-3.0.pre.35, on macOS 13.0 22A380 darwin-arm64, locale en-NG)
    • Flutter version 3.14.0-3.0.pre.35 on channel master at /Users/damilolaalimi/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a491089acc (3 hours ago), 2023-08-11 02:37:32 -0400
    • Engine revision 25afdb9b69
    • Dart version 3.2.0 (build 3.2.0-60.0.dev)
    • DevTools version 2.26.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

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

[✓] Android Studio (version 2022.2)
    • 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
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 14 (mobile)          • 1A122DE2-0CAB-4C3E-A395-691BF27D626F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 115.0.5790.170

[✓] Network resources
    • All expected network resources are available.

• No issues found!


update github docs CI

should now be similar to RTD setup

docs build should run a few minutes faster now and the setup should be the same as on RTD
I have removed uploading the build artifacts here to save some time. Or should we keep them @vhirtham @marscher ?


feat: add configuration options to set the SSL root of trust

This change is

If you have access to a Linux workstation with Docker installed, consider running:
./ci/kokoro/docker/build.sh clang-tidy

to fix the formatting issues.  It will be slow the first time as it builds a Docker image with the development tools and compiles all the dependencies.

Sigh, sorry, you need to rebase and push the new .abi.dump.gz files.

Done. I think: that was pushing the limits of my git-fu :-(
On Tue, Mar 10, 2020 at 4:11 PM coryan<EMAIL_ADDRESS>wrote:

Sigh, sorry, you need to rebase and push the new .abi.dump.gz files.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/google-cloud-cpp/pull/3455?email_source=notifications&email_token=AC3MQF2YA5GOE2G5XHGJUCLRGZRDTA5CNFSM4LEMEV7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOMCFYY#issuecomment-597172963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3MQF72NZEDFMLG3OMLJADRGZRDTANCNFSM4LEMEV7A
.

Thanks, assuming it all goes well I will merge your changes before some other changes that would conflict with these.


[App Config] Expose retryOptions from app-config to make it configurable

TODO:

Add retryOptions to the client options to make it configurable

Things to keep in mind:

custom throttling policy is different from what the core-http offers
throttling policy should play well with the retryOptions

Ask from Maryanne Gichohi (internal customer - App config team)

Had a chat with @jeremymeng.
In conclusion, I'm going with the following approach,

I'll extend the AppConfig client options with retry options with only maxRetries and the maxRetryDelay instead of all the four options of the RetryOptions interface in core-http
Update the custom throttling policy in app-config to not retry forever - and to honour maxRetries

reference https://github.com/Azure/azure-sdk-for-js/commit/c8126befe3aa90b7f6239ca0d7d7b0137ec6d61f

More thoughts

core-http and core-rest-pipeline should also follow the similar patterns

/cc @xirzec @ramya-rao-a

Can we treat #6484 and #9569 as pre-requisites before we invest further in the specific retry logic for App Config?

@ramya-rao-a
Internal customer(app-config team) is waiting on it.
We do have a clear idea of what to do for App Config, which is in sync with what we have duplicated in core-http.
Coming to the differences, app-config should ideally only differ with core-http's implementation w.r.t the header we pick for the retry-after-ms.
TODO in app-config

Update the throttling policy to not retry forever
Update the throttling policy to use maxRetries
Update the throttling policy to use maxRetryDelay

TODO in core-http

throttling policy uses hard-coded retries instead of user-configured maxRetries, this needs to be changed to use maxRetries
Update the throttling policy to use maxRetryDelay

TODO in core-rest-pipeline

Update the throttling policy to use maxRetries
Update the throttling policy to use maxRetryDelay
Update the delay to use abortSignal

Whatever we do in app-config should also be done in core-http and core-rest-pipeline.
All three libraries would have to be in the same state for unification.
I would like to unblock the app-config team asap.

Ok, sounds good.
I'll assign the retry tasks in core to you @HarshaNalluru as at this point you are most familiar with all the different requirements here :)


Dataset Viewer issue for wmt16

Link
https://huggingface.co/datasets/wmt16
Description
Reported by a user of AutoTrain Evaluate. AFAIK this dataset was working 1-2 weeks ago, and I'm not sure how to interpret this error.
Status code:   400
Exception:     NotImplementedError
Message:       This is a abstract method

Thanks!
Owner
No

Recently, there was a merged PR related to this dataset:

#4554

We are looking at this...

Indeed, the above mentioned PR fixed the loading script (it was not working before).
I'm forcing the refresh of the Viewer.

Please note that the above mentioned PR also made an enhancement in the datasets library, required by this loading script. This enhancement will only be available to the Viewer once we make our next release.

OK, it's working now.
https://huggingface.co/datasets/wmt16/viewer/ro-en/test

Thank you @severo !!


region-dump now requires a chunks directory for output instead of stdout?

I used to use region-dump to output a region to stdout (for various analysis purposes) but that seems to have changed (somewhere around 2021-07-05?) and it now dumps the region into a bunch of files in a chunks folder?
Any chance we can have the old stdout behaviour back?  I can't revert to the old version because my worlds are now 1.18 but the new chunks folder approach doesn't really work for analysis.

Hey there, this can definitely be done. The region-dump executable is pretty simple.
Was the behaviour you wanted just dumping out the chunks one after the other in Rust's debug format? Is there a better format you'd rather it spit out to? Converting it to json should be possible for example.

Yeah, just all the chunks in the region like it used to do.
JSON would be perfect - I did have a stab at converting the Rust debug format into JSON but my Rust is non-existent and trying to convert it post-hoc turned into a nightmare.
Thanks!

Latest fasnbt-tools should have you covered:
region-dump <file> # all chunks to stdout in Rust debug format
region-dump -f json <file> # all chunks to stdout in JSON, one line per chunk.
region-dump -f json -o chunks <file> # chunk per file in JSON
region-dump -f nbt -o chunks <file> # chunk per file in original NBT

You can also specify json-pretty and rust-pretty to get pretty-print versions. The exact format might have changed since you last tried since I had to change how the deserialiser works prior to 1.0.
Let me know if this works or not!


Can Drag?

I want drag this button, how can I do this ?

Hi luckerbai.
Thank you for using ActionButton library.
There are few ways of moving ActionButton depending on what you need to implement.
In general, ActionButton extends an Android View class, so it is a simple view, which supports all of the available View class actions.
Answering your question, using an Android Dragging and Scaling way, you can simply override onTouchEvent(MotionEvent) method as follows:
@Override
public boolean onTouchEvent(MotionEvent ev) {
    super.onTouchEvent(ev);
    // your code goes here
}

or move the ActionButton using any of the move methods.


Support on macOS Monterey and Ventura

Hi @cansik and thank you very much for your work, this is the only solution I have managed to get working for the realsense cameras on a Mac.
I have managed to get pyrealsense2-macosx working after downgrading to macOS Big-Sur and I have no issues with the installation on Monterey. However when on Monterey, the camera doesn't seem to connect:
    pipeline.start(config)
RuntimeError: No device connected

Would it be possible to expand this package to newer versions of Mac?
Thanks again for your consideration and hard work in sharing and maintaining this package, it is greatly appreciated!

the same issue ,I ran into this problem while writing my thesis and it disturbed me.

I am getting this error on Monterey as well.  Is there a way to do this for M1?

Apart from power state issues it works fine when running under sudo. E.g. sudo jupyter notebook --allow-root fixes the issues with not finding a device (this ofc raises security concerns but is apparantly due to MacOS ventura locking down usb)

Sadly it seems that Sonoma breaks realsense yet again, in a different way.  Now even with sudo we get:
Job 1, 'sudo realsense-viewer' terminated by signal SIGSEGV (Address boundary error)

I was able to build version 2.54.2 and run the test scripts using sudo to display RGB and depth streams. The current framework works, not stable (sometimes you have to run it twice), but when using sudo it seems to work.

It worked for me, sequoia 15.1.1. I have to run it multiple times typically (occasionally up to ~30). Something to watch out for is it also sometimes creates a hanging process that I had to manually kill before it would work again. Once it works, it usually works for a while though.
Interestingly, I tried putting many of the various errors I was getting into try except blocks e.g. the power issue, frames not arriving in time but found that if it didn't work the first time it wouldn't work until I tried running the application again


Publish to Live, October

The important commit here is the documentation for the new algorithm.
cc @aortiz-msft @jeffkl


[TACHYON-539] Update the worker general UI according to the worker changes

https://tachyon.atlassian.net/browse/TACHYON-539

+1 LGTM
One other approach could be to pass the startTime, blockDataManager, and workerNetAddress to the Servlet instead of passing the BlockWorker and having the additional accessor methods.

+1 LGTM

+1 LGTM. Thanks for the patch!


fix Fix be check quorum load err

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

be should not check quorum,  it's not accurate.
close this pr,   open another pr to delete be quorum check


plug in will not work in some browsers

At my work the company standard browsers are IE 11 and Firefox 45.0.2.  I have access to Chrome browser but it is not considered a company standard browser and the applications I develop need to be able to run on IE and Firefox.
The drag/drop and file upload feature work, but the paste does not work in IE 11 and Firefox 45.0.2.  It does work on Chrome.  On my personal PC's that run Microsoft Edge and Firefox 50.0.2 it works like a charm.  This plug in is perfect for a project I am currently working on.  I would like to work with my company to find a way to be able to use this functionality but wanted to find out from you if we need to be on Edge/latest Firefox, or is there a setting in the IE 11/Firefox 45.0.2 browsers that I need to have changed?

Unfortunately this behavior is normal, because only a few modern browsers support the clipboard API with files & DataUrls.
In the time developing this plugin only Chrome supported that feature. As of today I can say I only was successful on Chrome and Firefox >= 50...
(Safari & Safari Technology Preview, IE11, Edge 25.10586.672.0, Firefox < 50 was not successful).
Which is good, 1 Browser more that supports that feature, maybe 2 if you say you was successful with Edge, too...
As in the description of the plugin said, only a few very modern browsers support that feature, hopefully more to come...

Thank you for confirming this for me so I will know what to ask the desktop services team for!  Love the plug in!
Regards,
Melinda E. Forrester
Sr. Systems Developer, TIP Governance, EPO
Technology, Innovation and Performance (TIP)
PPD
<EMAIL_ADDRESS>mailto:Melinda.Forrester@ppdi.comwww.ppdi.comhttp://www.ppdi.com/
PPD LSS Yellow Belt
<EMAIL_ADDRESS>From: Daniel Hochleitner<EMAIL_ADDRESS>Sent: Friday, December 09, 2016 2:50 AM
To: Dani3lSun/apex-plugin-dropzone<EMAIL_ADDRESS>Cc: Melinda Forrester<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Dani3lSun/apex-plugin-dropzone] plug in will not work in some browsers (#10)
Unfortunately this behavior is normal, because only a few modern browsers support the clipboard API with files & DataUrls.
In the time developing this plugin only Chrome supported that feature. As of today I can say I only was successful on Chrome and Firefox >= 50...
(Safari & Safari Technology Preview, IE11, Edge 25.10586.672.0, Firefox < 50 was not successful).
Which is good, 1 Browser more that supports that feature, maybe 2 if you say you was successful with Edge, too...
As in the description of the plugin said, only a few very modern browsers support that feature, hopefully more to come...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Dani3lSun/apex-plugin-dropzone/issues/10#issuecomment-265963554, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXUyresTVaNsliL-YTNsnUttoOVLmj6Bks5rGRY2gaJpZM4LH8zi.
This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged.
If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified
that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited.
If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.


Aggressive Autosaving Causes File Reformat

This plugin causes auto-save to trigger immediately after I stop typing when a proto file is open but not in focus
Example:
Have a .go file open, open a .proto file -> split and move right
Add a new line to the .go file, auto-save is triggered and go fmt runs removing the newline
Similar to this issue, but I confirmed it is specifically the buf plugin causing it for me: https://youtrack.jetbrains.com/issue/WEB-54949/auto-save-as-soon-as-stop-typing

Unchecking these two settings seems to fix the undesired behavior

We'll check this out, thanks for the bug report.

buf plugin: 0.1.5
GoLand 2023.2 - Build #GO-232.8660.185, built on July 25, 202
It seems to happen within specific contexts, for example inside a function body or struct definition. I took a short video to demonstrate the behavior
https://github.com/bufbuild/intellij-buf/assets/18740821/56f4aa40-5587-4ad5-9ce8-a7ae2f17f27f


Brightness suddenly drops

I am using a Lenovo ThinkPad X1 Yoga OLED, and sometimes, the brightness suddenly drops, and the screen becomes very dark. Using the keys (Fn + F6) it gets brighter again, but not every keypress is registered. That results in that when the brightness indicator is full, the brightness of the screen is still not at the max brightness. I then have to reduce the brightness again and try several times to increase the brightness to max.

I'm experiencing the same, just as you describe.

same with me

Using ubuntu 19.10 with "night light on" feature, touring off night light solves issue for me.

Until the actual bug is fixed, I've been able to resolve this with icc-brightness clear and icc-brightness apply on my Thinkpad Extreme (gen 2) in Arch Linux.

Looks like disabling Auto Brightness in the settings solved the issue for me 🤦.


Problems: automatically expand file nodes similar to search results

In search we have this logic to automatically expand a file node when it has less than 10 results within. Maybe we apply the same logic to problems?

@bpasero I am doing same in error-lists as in search. It auto expands when a file has less than 10 markers.. on top of it added some smartness to not to open a file it is collapsed.. I see there are some cases which this is not as expected while applying filters.. I will check and make it more user friendly.
Thanks


Two licenses?

Just curious as to why there's two different licenses for this repo (I'm assuming the intended license is LICENSE.txt which contains the OER license).
Or does the OER license not apply to the code used in this repo (in which case, I can see why the MIT license might be present)?

@FlashDaggerX I have been told by those in the OER community that both should be used for a project such as this.  The MIT license is the one most appropriate for the code demos, whereas the Creative Commons Attribution-ShareAlike license is more appropriate for the lecture/content slides.


It doesn't work KR server.

The icon changes to green, but the UI is not visible. (there was a patch today)

I'm about to release update in few minutes.

Oh, thanks!


Drop Python 3.6

What was wrong?
Python 3.6 is no longer supported, so dropping here.
How was it fixed?
Removed CI runs, and updated any runs using 3.6 to use Python 3.9 now.
Todo:

[x] Clean up commit history

[x] Add entry to the release notes

Cute Animal Picture

@kclowes I found a few more things we can probably remove or change in this branch:

We can remove this (I don't believe it's being used anywhere) https://github.com/kclowes/py-evm/blob/drop-py36//tests/core/helpers.py#L13-L16

3.6 -> 3.9 here https://github.com/kclowes/py-evm/blob/drop-py36//.readthedocs.yml#L5 and here https://github.com/kclowes/py-evm/blob/drop-py36//docs/conf.py#L190

Remove this line https://github.com/kclowes/py-evm/blob/drop-py36/tox.ini#L49

and we might as well update the example here ? https://github.com/kclowes/py-evm/blob/drop-py36//eth/_utils/version.py#L10


Documentation: online execution of sample apps

Now that we have a few samples included in the documentation, I had the idea to implement online execution of these samples.
I found the JDoodle Java online compiler and liked it. Embedding the online executable code sample inside the quick guide was a matter of adding two lines (see patch attached).
I now want to hear your opinion on this feature, I'm curious what you think.
Side note: it may not be possible to take over the current samples as is:

Checkum.java calculates the checksum of a file, which makes it difficult/impossible to run the sampe in JDoodle,
ASCIIArt.java calls an external server for generation of ASCII art and it seems like JDoodle prevents calls to external servers.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0003630). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1188   +/-   ##
=========================================
  Coverage          ?   94.32%
  Complexity        ?      455
=========================================
  Files             ?        2
  Lines             ?     6660
  Branches          ?     1791
=========================================
  Hits              ?     6282
  Misses            ?      101
  Partials          ?      277

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/picocli/AutoComplete.java
97.01% <0.00%> (ø)
141.00% <0.00%> (?%)

src/main/java/picocli/CommandLine.java
94.16% <0.00%> (ø)
314.00% <0.00%> (?%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0003630...088d2f6. Read the comment docs.

Very interesting! I was not aware of this.
It is a good idea to have an additional example that can be executed online, like you did in this PR.
At work, my internet access is severely limited (as in many financial institutions), and I am guessing the JDoodle example will not be visible from my work PC. I will check remotely on Monday.
My point is that this should be supplimentary, while the main code examples should be embedded in the documentation.
This is exactly what your PR is doing, so that is great! I will merge this soon.

Very interesting! I was not aware of this.
It is a good idea to have an additional example that can be executed online, like you did in this PR.

Glad to see that you like the idea.

At work, my internet access is severely limited (as in many financial institutions), and I am guessing the JDoodle example will not be visible from my work PC. I will check remotely on Monday.

JDoodle offers two kind of links that can be shared:
URL: https://www.jdoodle.com/a/2mxo
Embed URL: https://www.jdoodle.com/embed/v0/2mxo
I tend to use/link to the embed URL.

My point is that this should be supplimentary, while the main code examples should be embedded in the documentation.

I fully agree.

This is exactly what your PR is doing, so that is great! I will merge this soon.

Please note that my PR is work in progress. Stay tuned, I plan to work on this soon. I will back back to you once its ready for merging. In the meantime, comments are very welcome.

I see.
I will push some changes related to your previous PR soon, you may need to rebase.

I pushed my changes; please go ahead and rebase at your leisure.

Superseded by #1196.


update knex dependency

Using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>i get this warning at yarn:
warning<EMAIL_ADDRESS>has incorrect peer dependency "knex@>= 0.8.0 <= 0.12.5".

Yeah, I'll update it in the next rc. Is there something you actually need in 0.12.6?

thanks for the fast response! nothing in particular, but was using it before and would prefer not to downgrade it

bump on this one, and to give more context on our issue: we use knex in multiple modules and if each module specifically requires an old version without the possibility for minors being upgraded we end up with a messy node_modules (e.g. knex 0.12.5, 0.12.6 and 0.127 installed)
thank you!

@rodrigopivi @xcapt The knex peerdep is for 0.x in objection 0.7.0.


"Object level storage tiers aren't yet available"

The pricing page quotes pricing for Cool/Archive on ADLS Gen 2.
So, are they now supported at object level?

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

ID: 46d15a48-4780-edbb-4485-121f901cbac9
Version Independent ID: fc65764c-2d2a-4901-5c31-82b4566bf3bc
Content: Known issues with Azure Data Lake Storage Gen2
Content Source: articles/storage/blobs/data-lake-storage-known-issues.md
Service: storage
GitHub Login: @normesta
Microsoft Alias: normesta

@ishepherd, Thanks for the Comment. We are actively investigating and will get back to you soon.

Cool tier is currently available for ADLS Gen2.  Archive tier is not yet available.
Regarding service general availability, I would suggest to keep an eye on  Azure Updates.
Azure updates provide information about important Azure product updates, roadmap, and announcements.
I will now proceed to close this issue. However feel free to comment and tag me if you have any other queries.

OK @ChiragMishra-MSFT thanks for explaining
The pricing page I linked above does quote prices for Archive, and doesn't say that it's unsupported. So please consider modifying that page.

@ishepherd Sure we will review and make appropriate changes. Thanks again for bringing this to our notice.


Ajax POST data in the OpenSeadragon.

Since OSD supports custom TileSource creation, it should also support the POST version of the HTTP protocol.
Why POST?

image protocol support: let's say your protocol for getting image tiles for some reason uses HTTP POST. Goodbye, OSD. Or not?
URL length limit: your protocol might use too large identifiers or too many parameters to fit into GET
security: it is not a good practice to put sensitive data into the URL itself

How?

ajax use must be enabled, obviously
simply extend your URL, use # sign to define where POST data starts, values after hash are not sent to server by default: we cut them out and use as the POST data

e.g. https://myserver.com/iipsrv.fcgi?Deepzoom=path/to/image.tif.dzi#myparam=1&otherparam=false
or simply https://myserver.com/iipsrv.fcgi?#Deepzoom=path/to/image.tif.dzi to not to use GET, but POST only

implement your TileSource version that

can work with the value of your url after # in configure( data, url = [string value before #], postData = [string value after #] )
returns custom post data for each tile using getTilePostData: function( level, x, y )  - analogy to getTileUrl(...)

default implementation returns null which makes OSD use HTTP GET and other TileSource implementations remain untouched

Some notes I thought can be useful

no automated tests provided
tested within an operational visualization system
existing tests not broken
documentation properly updated

I will try to add some tests when the season gets less busy, this was something I had to implement anyway and sharing was just a matter of few checkups before submitting.
I will look into # sign more, whether AJAX can actually send a request with this character, since browsers do not. I am not sure about how this works in more detail and I did not read any specification. Good point. My wild guess was that it will get eventually cut anyway so no harm done. Some quick lookup told me my guess actually might not be wrong.

Ah, I see... ? will turn on the parameters part and hash gets treated as a simple character..

@iangilman what about escapes? # is cut off, \# treated as hash, \\# treated as \ and # characters...

My concern with the # is if someone is already using it in their tile source URLs and we change the way that behaves (even if we provide an option to fix it like adding an escape), it's a breaking change for them and we'll have to communicate to them why their code is broken and they'll have to fix it. Ideally each new version doesn't break the previous version. One way to make that happen would be to only use the # for post params if a flag is set in the viewer.
Thank you for planning on writing some tests... no rush, but let me know if you end up deciding you can't do that after all.

I've now added tests, URL is correctly split, allowPost flag makes the use of # character explicit (with no escape possible, the first found is used - unfortunately not possible to have both GET, POST params and use # in GET)..

Oh, I noticed npm made some changes to json configs, should I remove that?


protonhax is no longer in the AUR

the protonhax package is no longer in the AUR, only the protonhax-git is available.

i'll close the issue then


Request: GIF integration (via Giphy, Imgur, etc.)

Description
This request is https://github.com/refined-github/refined-github/issues/72, but 7-years later and not specific to Giphy.
Can Refined GitHub support GIF integration (via Giphy, Imgur, etc.)? 🤓
This would make Refined GitHub a vehicle for better PR culture :)
Example URLs
https://github.com/DrewML/GifHub#gifhub
Seems pretty close, just a button to paste in GIFs.

Indeed that feature already exists as a standalone extension, so we don't add it to Refined GitHub, as specified  in
https://github.com/refined-github/refined-github/wiki/"Can-you-add-this-feature%3F"


[Logstash-output-opensearch] Add 1.1.0 version of rubygems links to website

Is your feature request related to a problem? Please describe.
[Logstash-output-opensearch] Add 1.1.0 version of rubygems links to website
https://rubygems.org/gems/logstash-output-opensearch/versions/1.1.0-java
1.1.0 version if out current with only the gem, no tar, no docker.
We need to have a way add it to the website.
Describe the solution you'd like
See above.
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.

I'd prefer starting with docs and the project README. @aetter for the docs, do is there already a link to the GEM URL for the Logstash output plugin?

We don't, no. Is the goal here "if you have an OSS Logstash install and want to add the opensearch output plugin to it, do the following"?
If so, pretty easy addition to the documentation -- it looks like the the command is just ./bin/logstash-plugin install logstash-output-opensearch, and we can link to the gem page while we're at it.

@aetter I also believe we need to provide documentation for upgrade logstash-output-opensearch as well.


OPCT-11: fix counters on plugin report progress

https://issues.redhat.com/browse/OPCT-11
Bump to v0.3.0-alpha1 after plugin fix https://github.com/redhat-openshift-ecosystem/provider-certification-plugins/pull/34
This PR will improve the counters when running OPCT, fixing a bug on openshift-tests on 4.12+ clusters.
We don't need to create a alpha release for CLI, but having this change on the master will get newer results from OpenShift CI, running weekly for 4.12.

/assign @rvanderp3

we'll go ahead and merge this, a quick discussion indicates that the digest might not be the best way to go with this.
/lgtm
/approve


feat(ethers): Refactor wallet management, add shared KeychainAccountManager, add Ethers wallet

Description
This PR contains a pretty big refactor of how we handle wallets and accounts in the app. The relevant classes/interfaces are organized as follows:

The ValoraWallet interface is a generic interface that encapsulates wallet functionality (i.e., signing stuff) independent of the underlying wallet library. Throughout the app, rather than expected to use a KeychainWallet (which is contractkit-specific), we expect to use a ValoraWallet. To clear up the nomenclature, I'm considering a wallet to mean "a collection of accounts, tied to a single blockchain", and account to mean a single address/private key. This means that ValoraWallet is able to perform signing on behalf of multiple addresses. This was a side-effect of this already being the case for KeychainWallet, which contains multiple signers.
ValoraCeloWallet and ValoraEthersWallet are implementations of ValoraWallet using Celo libraries and Ethers, respectively. ValoraCeloWallet is a thin wrapper over the existing KeychainWallet.
WalletManager manages initializing and retrieving ValoraWallet instances, and is initialized as a singleton.
KeychainAccountManager is a new class (initialized as a singleton within WalletManager), which manages saving, retrieving, and updating accounts from the keychain, as well as locking and unlocking them. This single KeychainAccountManager is shared between all ValoraWallet implementations. As a result of this, account lock status is shared amongst all wallets (which I'm pretty sure is desirable). Similarly, KeychainAccountManager allows wallets to register callbacks to run when an account is added to the keychain; this means that adding an account to wallet A will automatically add it to wallet B as well.

The high level structure of these classes is:

WalletManager

ValoraCeloWallet (implements ValoraWallet)

KeychainWallet

KeychainSigners (many of these, one per account)

KeychainAccountManager (singleton, passed in via DI)

ValoraEthersWallets (implements ValoraWallet) (many of these, one per chain)

ethers.Wallet (many of these, one per account)
KeychainAccountManager (singleton, passed in via DI)

ValoraCeloWallet is unfortunately quite nested; I didn't want to mess around with the existing KeychainWallet implementation too much. KeychainWallet and KeychainSigner are functionally not very different than before, except a good deal of their logic has been pulled out into KeychainAccountManager to be reused among other ValoraWallet implementation; this should hopefully simplify KeychainWallet and KeychainSigner a little bit.
Further, since the app now expects the interface of ValoraWallet in place of KeychainWallet, certain callers have needed to be modified somewhat to suit this new interface. This was largely straightforward, except for KeychainWallet's signTransaction function, whose parameters/return value are non-trivial to coerce from a Celo-specific structure to something more general. As a result, ValoraWallet.signTransaction retains the Celo-specific typing for the time being.
Test plan
Testing in progress...
Related issues

Fixes ACT-796, ACT-783.

Backwards compatibility
Yes... pending testing :)

ValoraWallet.signTransaction retains the Celo-specific typing for the time being

what are the implications of this? are we going to need to update consumers of it incrementally as we switch to using ethers in more areas of the app?


MediaWiki redirects to the homepage after editing the post (with many external links)

Describe the bug
Hi, I don't have anything to do with security, I updated it as WHM sent it to "OWASP CRS v3.x for ModSec 2.9 (via RPM)"
It turns out that now I can't put many external links in a publication in MEDIAWIKI, would that have any solution besides disabling security?
Thanks!
Logs and dumps
https://imgur.com/a/mca3e7m
The interesting thing is that this is not my IP, so why does another IP appear?
Thank you for helping lay people like me.

Hi @ofmarconi,
I think you are facing some issues with the rules. The best place to ask such question is on the OWASP CRS project.

THX 👍


Fix link in CONTRIBUTORS.md

The last person to add their name to the file had a space between the
link text and URL. Removing the space should get the link to display properly.
I'm not sure who's best to tag here. @hpinkos, this was related to a PR you merged recently so I'm tagging you.

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks


Dependency Bot warning about vulnerable dependencies: ssri and is-svg

Version
4.5.9
Reproduction link
https://github.com/upstage-org/mobilise
Environment info
Environment Info:

  System:
    OS: macOS 11.2.1
    CPU: (8) x64 Intel(R) Core(TM) i5-1030NG7 CPU @ 1.10GHz
  Binaries:
    Node: 15.6.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.4.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 89.0.4389.90
    Edge: Not Found
    Firefox: 86.0.1
    Safari: 14.0.3
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.0-rc.2
    @vue/babel-plugin-jsx:  1.0.0-rc.5
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.9
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.9
    @vue/cli-plugin-babel: ~4.5.0 => 4.5.9
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.9
    @vue/cli-plugin-pwa: ~4.5.0 => 4.5.10
    @vue/cli-plugin-router: ~4.5.0 => 4.5.9
    @vue/cli-plugin-vuex: ~4.5.0 => 4.5.9
    @vue/cli-service: ~4.5.0 => 4.5.9
    @vue/cli-shared-utils:  4.5.9 (4.5.10)
    @vue/compiler-core:  3.0.4 (3.0.7)
    @vue/compiler-dom:  3.0.4 (3.0.7)
    @vue/compiler-sfc: ^3.0.0 => 3.0.4
    @vue/compiler-ssr:  3.0.4
    @vue/component-compiler-utils:  3.2.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/reactivity:  3.0.7
    @vue/runtime-core:  3.0.7
    @vue/runtime-dom:  3.0.7
    @vue/shared:  3.0.7 (3.0.4)
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^7.7.0 => 7.7.0
    vue: ^3.0.7 => 3.0.7
    vue-eslint-parser:  7.6.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.6 (16.1.2)
    vue-router: ^4.0.0-0 => 4.0.1
    vue-style-loader:  4.1.2
    vue-template-es2015-compiler:  1.9.1
    vue3-draggable-resizable: ^1.6.0 => 1.6.0
    vuex: ^4.0.0-0 => 4.0.0-rc.2
    vuex-persistedstate: ^4.0.0-beta.1 => 4.0.0-beta.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
There is no step at all, everything was fine until Github dependency bot discover these vulnerable a few days ago, see attachment below:

What is expected?
No warning from Github's dependency bot
What is actually happening?
Dependency bot is warning about vulnerable inside these indirect dependency: ssri and is-svg

ssri and is-svg is not our direct dependency, after inspecting the yarn.lock we discover that it was peer dependency of @vue/cli-service

ssri: requires a cacache v12 patch, see: https://github.com/npm/cacache/issues/42#issuecomment-756316569
is-svg: requires a postcss-svgo patch, see https://github.com/cssnano/cssnano/pull/1023#issuecomment-806397809

Hello everyone, thank you for the great works!
What is the current status of this issue? It's now considered high severity by Dependency Bot

As said earlier, they are upstream issues, there's nothing we can do here.
Besides, they do not expose the users of Vue CLI to any real threats, it's safe to ignore them.
They're considered vulnerabilities because if you use these package versions in your Node.js web server, and process user inputs with them, your server might be compromised.
But that's not the use case of Vue CLI, which is a developer tool.

Thank you for the helpful information @sodatea 👍 We've turned off the vulnerable warning alerts for now

@sodatea The @vue/cli-service package directly depends on version 7 of ssri. For version 5 (which is currently in beta) it was bumped to version 8, per https://github.com/vuejs/vue-cli/commit/473eab2d786aa54b7ab816003df6fbfee79852e9.
It looks like the update did not have that much impact, so maybe it can be backported to version 4 of the cli-service?


added modulus and exponent support

adds modulus % and exponent ^ support

Pull Request Test Coverage Report for Build 19

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 16:
0.0%

Covered Lines:
121

Relevant Lines:
121

💛  - Coveralls


Unable to load script from path!

Godot 4.2 with gd and mono versions. Throwing an error.

Hi! That versions only supports mono, and be sure that you've created a solution with Project -> Tools -> C# -> Create C# Solution (If remeber correctly default solution is alredy creating a project with .NET 8, but if there is any errors on build try to change it manually). After you've created it, just try to build the project (it will generate .NET binaries), reload Godot and enable the addon - it should now read the scripts correctly.
I've not included that info in the main repo as those steps affects all the .NET addons and it's expected to be known, but it seems might be useful to include it anyway.
Let me know if those steps are not fixing your issues, hope it helps.

Thank you, worked for me!


[Bug] Unclear how to create mlc-ai/demo-vicuna-v1-7b-int4 manually

🐛 Bug

To Reproduce
Steps to reproduce the behavior:

Follow instructions for compiling vicuna https://mlc.ai/mlc-llm/docs/compilation/get-vicuna-weight.html
Follow instruction for compiling models https://mlc.ai/mlc-llm/docs/compilation/compile_models.html
End result is a vicuna-7b-v1.1-q4f16_0
This result is incompatible with https://huggingface.co/mlc-ai/demo-vicuna-v1-7b-int4

I've been making it work by manually push the vicuna weights to my device.
I also pushed them here https://huggingface.co/kmadsen/vicuna-7b-v1.1-q4f16_0 so our app can download them from something instead of requiring adb.

Was reading more of the documentation and noticed --reuse-lib.. Maybe that is the way? I'll give a try later
https://mlc.ai/mlc-llm/docs/compilation/distribute_compiled_models.html

mlc-ai/demo-vicuna-v1-7b-int4 is deprecated, we are now moving to vicuna-7b-v1.1-q4f16_0 instead

Thanks @Hzfengsy! Is it a work in progress or am I missing the update somewhere?
It's still in use here https://github.com/mlc-ai/mlc-llm/blob/9c3f12c89474d38366d91d61658be615f509654a/android/MLCChat/app/src/main/assets/app-config.json#L8
I published one earlier today (thinking it's temporary) because I couldn't find it anywhere else https://huggingface.co/kmadsen/vicuna-7b-v1.1-q4f16_0

The prebuilt libs are here: https://mlc.ai/mlc-llm/docs/prebuilt_models.html, which contains vicuna-v1-7b-q3f16_0.

@Hzfengsy actually another issue is building the android libraries introduced here https://github.com/mlc-ai/mlc-llm/pull/478
Android it seems you still need to build the prebuild_models in order to create the android libraries. Is there a command to build the android libraries from existing mlc weights like vicuna-v1-7b-q3f16_0?


feat(incidents): create downloadable incidents csv report

Added a button for the download reported incidents to CSV
Currently active incidents filter also applies to the downloaded CSV records

re #2292
Newly added dependencies with Bundlephobia links:
<EMAIL_ADDRESS>

@jackcmeyer @tehKapa @fox1t , I've made the requested changes and am awaiting further review to have this merged.

On it.

Ready to be re-reviewed @fox1t .

LGTM


Make $or use the parseQuery function

This part: https://github.com/feathersjs/feathers-rethinkdb/blob/master/src/index.js#L112
Can be rewritten to use this function: https://github.com/feathersjs/feathers-rethinkdb/blob/master/src/index.js#L298

Closed via #53


Replace the docker lib with regclient

What would you like to be added:
A continuation of https://github.com/open-component-model/ocm-project/issues/106.
Turns out ORAS was not a good choice. It handled some parts of the image layering choices based on MediaType incorrectly.
regclient has a much better support, an easier API ( no layering, just plain push blob or push manifest ) and a larger community actually.
Why is this needed:

Needs at least 2 assignees due to complexity of issue

Tests
Most important test is making sure that all blobs behind a manifest are actually available and downloadable.
Reproducing steps:
Description


add circe support

Hi!
I want to close #22
Thank you :)

To avoid including circe dependencies in core, maybe it is a good idea to move circe support to it own module, so it could be included on demand. What do you think?
I have done domething similar in PR #18 to add support for http4s as path extractor

Yeap, ty :)


Faillible Queryable - Non-generic Queryable version experiment

One approach to fixing #2523

Just to drop a note here: I'm currently busy with other work related stuff, so I will likely not be able to look at this for the next week or so.

So the test fails there seems to highlight a compatibility break with type inference where the compiler cannot infer "oh there's a single type I know for deserializing BigInt, that's i64, let me just use that" anymore, though I'm not sure why it has this impact.
If going for this approach, readmes and diesel_cli would still have to be updated.

Another important change here is that we cannot anymore write different impls depending on the type returned by some query or the backend. Doing that is basically required to port diesel_cli. As consequence I would like to see how that could be solved before looking any further into this.

Another important change here is that we cannot anymore write different impls depending on the type returned by some query or the backend. Doing that is basically required to port diesel_cli. As consequence I would like to see how that could be solved before looking any further into this.

From https://github.com/diesel-rs/diesel/issues/2523#issuecomment-703781510:

it would probably always be implemented without an additional layer of genericity, so it could probably use FromSqlRow instead of Queryable, as the conflicting impl error wouldn't trigger.

As it turns out, we're actually using a bit of genericity here:
https://github.com/diesel-rs/diesel/blob/a312528c7cce6b25ae6f1f5987f784b635b18ed6/diesel_cli/src/infer_schema_internals/data_structures.rs#L78-L82
but for some reason it still works. (Maybe thanks to the local UsesInformationSchema trait.)

One more issue: rust error messages suggest less correct approaches to fixing FromSqlRow<ST, DB> is not implemented for T:
https://github.com/diesel-rs/diesel/pull/2559/checks?check_run_id=1617158750#step:6:258

Closed as I would like to go with #2599

Closed as I would like to go with #2599


Server main script (.js)

Description
Required features:

Audio mixing console
Mixer lanes name viewing (input from client's packet header)

Server will not supply any UI

[ ] Web audio client UI supply
[ ] Audio receiving -> mixing -> responding
[ ] Web mixer client UI supply
[ ] Audio client's volume modification accept
[ ] Audio client's loudness monitoring

Server script language changed because of #159


i can't install

[x] I have reset Atom to defaults prior to submitting report.
[x] I have not reset Atom to defaults prior to submitting report.

Description

Steps to reproduce

Expected behavior:
Actual behavior:
Reproduces how often:
Versions

> atom --version

> apm --version

OS name and version:
Platformio-ide-terminal version:
Additional Information

Platform-ide-terminal not working

Fixed in https://github.com/platformio/platformio-atom-ide-terminal/releases/tag/v2.10.1
Please update platformio-ide-terminal to the latest version.


Load xacro instead of urdf

Hello, is it possible to load xacro file directly to the parser without manually converting the file format? Thanks.

Hi, the python library uses urdf_parser_py to parse the URDF, and it can therefore not load xacro files directly. Xacro files can easily be converted to URDF with the command xacro if you have ROS installed on your system. So one way you can do it in your scripts is to call xacro from python and use the output with urdf2casadi.


after graph worker runs, check to make sure schedules are valid

Some schedules may depend on particular assets that could be removed by a graph worker

closed by e1b7541a2


Inplace operations produce different result for jitted and pure functions.

Although the title speaks for itself, I gave below a minimal example with subtraction, but everything is also true for other operations (__imul__, __iadd__, ...).
import numpy as np
import numpy.random as random
import numba

random.seed(111)
points = 10*random.rand(10, 2)

def sub(pts):
    points = pts.copy()
    points -= points[3]
    return points

@numba.njit('f8[:,::1](f8[:,::1])')
def sub_njit(pts):
    points = pts.copy()
    points -= points[3]
    return points

assert np.all(sub(points) == sub_njit(points))

I'm not familiar with the innards of the numpy and the numba, but it looks like that numpy passes rhs as a copy and numba passes rhs as a view. I'm not sure which option is right, but in any case the result is not agreed.
sub(points) == sub_njit(points)

array([[ True,  True],
       [ True,  True],
       [ True,  True],
       [ True,  True],
       [False, False],
       [False, False],
       [False, False],
       [False, False],
       [False, False],
       [False, False]], dtype=bool)

Python 3.6.3
numpy 1.13.3
numba 0.35
Windows 10

I found this bug still exists in 0.54.1:
import numpy as np
from numba import njit

x = np.array([[2], [1]])

def imul(a):
    a = a.copy()
    a *= a[0]
    return a

imul_numba = njit(imul)

assert (imul(x) == imul_numba(x)).all()


Add License

@medhatdawoud
Hi, thank you for publishing this code.
I want to use this, but I noticed that it is unlicensed.
Can you please add a license, so I would be able to use this code?
Thank you!

Thanks for mentioning that, I've added a licence file


Add an autofix to the meta bug

here, we should add an autofix.
https://github.com/mozilla/relman-auto-nag/blob/master/auto_nag/scripts/meta_summary_missing.py#L43
I am not sure how to do it
Should be something like
return {'summary': '[meta]' + summary

Fixed in:
https://github.com/mozilla/relman-auto-nag/commit/056da5f25e7f0afaaa747a60827513800d0dce79


Only build, test and support still supported Node.js versions

I think we should update the CI configuration and package.json to just include versions that are currently still supported.
Right now this project supports everything until back to 0.10.

Correct, the generator supports the same versions of Node.js as the related Express versions it generates for. When Express launches with updated Node.js versions the generator will also match it.


Enable full AWS SDK credential chain

The 1.x AWS SDK for go does not enable the full credential chain by default (see Sessions options from Shared Config here: https://docs.aws.amazon.com/sdk-for-go/api/aws/session/). Most AWS SDKs do this by default -- the 2.x go SDK does.
This allows usage of credential helpers and ~/.aws/config profiles without setting additional environment variables.

Couple failures for sig-network cases, not sure if that's a known issue or not @dims ?

@cartermckinnon we can get to flakes later!
/approve
/lgtm

/retest


SAA-1820: Ignore removed prisoners from waitlist

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

Project coverage is 84.18%. Comparing base (9a62541) to head (aea83a1).

Files
Patch %
Lines

...ivitiesmanagementapi/service/WaitingListService.kt
90.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #936   +/-   ##
=========================================
  Coverage     84.18%   84.18%
- Complexity     3648     3649    +1
=========================================
  Files           377      377
  Lines         12062    12062
  Branches       1050     1051    +1
=========================================
  Hits          10154    10154
  Misses         1435     1435
  Partials        473      473

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


BayPI Interface Files

These files don't actually run on this server; They're added here for reference - The physical API runs on an separate isolated server as it needs a python backend.

This needs improvement before finalizing


[COMPILER] Incorrect instructions with kwsplat causes failed assertion

Minimal repro:
[**{}]
Causes Assertion Failed: ../vm_core.h:1375:VM_ENV_FLAGS:FIXNUM_P(flags)

Duplicate of #2155 and should be fixed by ruby/ruby#9540.


maintainers: remove superherointj

maintainers: remove superherointj

Not sure what happens but still thank you for all your contributions and best of luck to you for all your future endeavors.


Starter guide docs WIP

Describe changes
I implemented/fixed _ to achieve _.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@htahir1 Does WIP mean you do or don't want a review on this now?

@strickvl @schustmi id like a review on the stuff I have for now just to get initial feedback


Fix overeager scrolling in TreeMap/Grid combo.  Related TreeMap cleanups

Related and Unrelated tweaks

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[X] Caught up with develop branch as of last change.
[X] Added CHANGELOG entry, or determined not required.
[X] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[X] Updated doc comments / prop-types, or determined not required.
[X] Reviewed and tested on Mobile, or determined not required.
[X] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

I built it in to the dependency for  the model's data itself
intentionally.  Thought that was more straightforward, and that it is
unlikely to change.
On Fri, Mar 12, 2021 at 10:21 AM Tom Tirapani @.***>
wrote:

@TomTirapani commented on this pull request.
In desktop/cmp/treemap/TreeMap.js
https://github.com/xh/hoist-react/pull/2342#discussion_r593246724:

@@ -103,24 +104,23 @@ class LocalModel extends HoistModel {
this.clickCount = 0;
this.debouncedClickHandler = debounce(this.clickHandler, 500);

   // Render HighChart when chartElem container ready in DOM, a relevant observable on the

   // model API changes, and/or the source data array itself changes.

   // Render HighChart when chartElem container ready in DOM, or dependencies updated

   const chartDependencies = () => ([

       this.chartRef.current,

       model.highChartsConfig,

       model.data,

       XH.darkTheme

   ]);

We're missing the dependency on the model.algorithm here. The chart needs
to be redrawn when the layout algorithm changes
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xh/hoist-react/pull/2342#pullrequestreview-610881884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARTL2KQZWXSAETLDO3V6TDTDIWPFANCNFSM4ZCMP44Q
.

But, it has nothing to do with how we process the data? It's essentially part of the highcharts config that we've lifted to be a bindable. Don't see how its more straightforward to rebuild the data in order to redraw the chart, when we can just redraw the chart?


Missing '"experimental": true' in daemon.json listing in docerd.md

File: engine/reference/commandline/dockerd.md
"experimental" option missing on /etc/docker/daemon.json

The file in question is in the docker/docker/ repo under docs/reference/commandline/dockerd.md so the pull request needs to be made there, not in this repo.

@johndmulhausen Happy to take this on if it's still an issue, but as far as I can tell, this has been previously resolved.

Thanks @jadametz


evaluator: two level comprehension loses keys

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20221001181137-79d80efc2882

      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
             vcs git
    vcs.revision 79d80efc288208410f77d47ae9aedd37e106d84b
        vcs.time 2022-10-01T18:11:37Z
    vcs.modified false

Does this issue reproduce with the latest release?
No, it's on tip only.
What did you do?
exec cue export test.cue
cmp stdout expect.json

-- test.cue --
in: {
	foo: {
		bar: ""
		baz: ""
	}
}
out: {
	for k, v in in for vk, vv in v {
		"\(k)": "\(vk)": vv
	}
}
-- expect.json --
{
    "in": {
        "foo": {
            "bar": "",
            "baz": ""
        }
    },
    "out": {
        "foo": {
            "bar": "",
            "baz": ""
        }
    }
}

What did you expect to see?
A passing testscript run.
What did you see instead?
> exec cue export test.cue
[stdout]
{
    "in": {
        "foo": {
            "bar": "",
            "baz": ""
        }
    },
    "out": {
        "foo": {
            "bar": ""
        }
    }
}
> cmp stdout expect.json
--- stdout
+++ expect.json
@@ -7,7 +7,8 @@
     },
     "out": {
         "foo": {
-            "bar": ""
+            "bar": "",
+            "baz": ""
         }
     }
 }

FAIL: /tmp/testscript382054878/x.txtar/script.txtar:2: stdout and expect.json differ

Thanks to @Fionera on the CUE Slack for reporting this issue.
Bisected to 6b3fd657900412db28bc4270aa0bd31d12fa3c48

This is caused by an overaggressive performance optimization which was a bit overzealous removing duplicates.


Only read 32 bytes from /dev/urandom for a seed.

The problem is you're using the standard I/O functions to read this Unix device; that is not a good idea.
The stdio read functions are buffered so the fread() call will always read a full block from the input. For files and terminals this isn't a problem; the former will just read the data the latter will just return whatever's available.
The problem with /dev/urandom is that a full block of data will be available so a whole block will be read, however, this over a hundred times as much randomness as we actually need. This takes quite a while to generate as the kernel tries very hard to give good results. As the extra data is never used this doesn't actually deplete the theoretical entropy that the kernel has, but it doesn't know that. So this can cause problems too, especially if other applications use the blocking version of the device or you have a daemon that hunts for more randomness.
The Unix functions open(), read() and close() will treat the device nicely.

Added another commit to the repo, this one is an extension of the test program so that all the pieces of the library can be exercised (or even actually USED) from the command line or a shell script.
The Sha512 output is the same strings as the standard sha512sum program, the Ed25519 hex inputs and outputs are in standard hex forms as searchable on the web.

Thanks for identifying the problem and writing a solution @rdebath ! I agree that defaulting to buffered IO on /dev/urandom is a pretty bad outcome.
Rather than switching from <stdio.h> to <unistd.h> IO, I think we can ask libc to avoid buffering by doing setbuf(f, NULL). Does that seem right to you?

Just double checked with strace and that works just as well, good call!

I'm willing to use unbuffered IO, however I have no interest in the command line interface test program or the makefile that comes with it. That's a bunch more code for me to maintain that's outside the scope of this project. Feel free to host it as your own project though.


Improve handling of potential keychain errors

On iOS, the seed is split across 2 locations:

the JSON file (which contains encrypted seed, wrapped in ChaCha20)
the keychain entry (which contains key to decrypt JSON file)

If we encounter an unexpected error when reading the keychain error, and the JSON file exists on disk, then we should react appropriately.
What happens currently: we ignore the error, and display the standard welcome screen.
Possible alternatives:

display a warning to the user, prompting them to kill Phoenix, and try launching it again
ensure there is a backup of the JSON file and the keychain entry

We're still unable to reliably reproduce this bug. But an analysis of the code leads to the following possibilities:

an error reading the "security.json" file
an error reading the value from the keychain

I believe it's a temporary error from the keychain. The one time I was able to reproduce the issue (unfortunately not in the debugger), I was able to restore my wallet by simply relaunching the app. So our goal with this fix is to:

prevent the user from overwriting their seed (and potentially losing their funds)
make it possible for the user to report helpful information to the engineering team

So here's what happens now if we encounter this scenario:


Unusual elm-version

Hi, I noticed in your elm.json you have "elm-version": "0.18.0 <= v < 0.20.0". I don't think that's a valid dependency range. It should probably be "elm-version": "0.19.0 <= v < 0.20.0" instead.

Right. I will fix that.

Fix that and published.


How to identify 404 with Angular

How to identify 404 with Angular?
similar issues

https://github.com/angular/quickstart/issues/406#issuecomment-288394851
https://github.com/aspnet/Templating/issues/546

For me, it doesn't work fine, the followed example returns status code 200, but I want to return error code 404 (for analytics) (not 200 as in https://github.com/angular/quickstart/issues/406#issuecomment-288394851)
Here is an example for Node.js (https://blog.thecodecampus.de/angular-universal-handle-404-set-status-codes/), but I can't use it with this template, Do we have something similar?

@SteveSandersonMS, can you please answer this question? Thanks!

@vasyliv I assume you're asking about making the SSR response return a 404. In that case, please see https://github.com/aspnet/Templating/issues/587#issuecomment-413601497

@SteveSandersonMS thanks a lot.


Now Playing

New feature
Some sort of "now playing" display, so that we can see what's going on.

Done and deployed.


Support main in package.json lookup

Final work on https://github.com/Microsoft/TypeScript/issues/2338 Works great. One minor issue, main isn't supported, that means that one needs to do import * as root from "ts-npm-module/js"; example instead of a simpler (and more common in js) import * as root from "ts-npm-module";
Creating a separate issue for tracking :rose: + possible PR.

so why not set typings to js\index.d.ts instead?

As it prevents deep reaching e.g. "ts-npm-module/js/deep/foo";

It is used quite commonly e.g. "react" and "react/addons"

so why not set typings to js\index.d.ts instead

Setting it to js/index does indeed work. Basically typings is just an alias for main, the rest of the lookups don't even use typings :+1: :) Thanks :rose:
Complete example :
// Use from main
import * as root from "ts-npm-module";

var foo = root.foo;
var Bar = root.Bar;
var bas = root.bas;

// Or any of the other files within the module
import {foo as deepFoo} from "ts-npm-module/js/deep/foo";
import {Bar as deepBar} from "ts-npm-module/js/deep/deeper/bar";

foo = deepFoo;
Bar = deepBar;

Closing

Setting it to js/index does indeed work. Basically typings is just an alias for main,

correct. and in fact @vladima had an earlier iteration that had look up for both main and typings but that felt redundant. so we removed main checking. We would be interested to know if this will block some scenarios that typings would not be sufficient in.


Handling service and resource not found errors

This pull request sets the HTTP status codes of service and resource not found scenarios to 404 and implements integration tests to verify those.

We've improved error handling for these scenarios during the last release. These changes are no long applicable. Thanks for your contribution.


add post-aggregation for parallel-loops

Feature-request
Description
To get items out of parallel-loops, there should be a post aggregation after all parallel tasks are finished.

documentation will be updated with #136


equal( com.parent_permlink, o.parent_permlink ): The permlink of a comment cannot change.

Keep getting this error when updating a post, even though the permlink has not been changed. What's wrong?

Sorry was my mistake

Would to know how you edit a post because am getting the same error

Well, I am also getting the same error when trying to update posts. Can someone please explain this to me?


Bugfix - Huge stream parse

Fixes #109 where lib hangs when streaming big CSV from remote location.
Now trying to read the stream twice will fail (test that used to care for that was removed) but when reading large streams (which is one of the main reasons to use a stream instead of having the data in memory) will work.

I guess this is a behavior breaking change as multiple Table.read executions when the source is a stream will not work anymore. As stream factories are supported, they it can be used instead to overcome this limitation, should I add something to the docs regarding this change?

@felipesabino
Thanks!
Could you please eloborate with @anuveyatsu here because I'm not sure will it break their software or not.
We could work iteratively on this PR to make it work for everyone.

Hey @roll, sure! I will wait for @anuveyatsu input, then.
I really need this fix to be merged/released as my software is currently broken, but I guess can release on the side meanwhile if merging takes too long.

FYI for anyone also needing a temporary fix, I released this PR as tableschema-pr-118 package for now.

@felipesabino
Great, thanks! Sorry we're unable to resolve this for now on the main package. Hopefully after the holidays we'll achieve it.

Hey, @felipesabino and @roll sorry for not getting back to you before. I will take care of this by tomorrow evening.
Re why we needed multiple Table.read executions, we originally had this discussion here https://github.com/frictionlessdata/tableschema-js/issues/92 and I don't think it was required for us. So probably this PR should be fine - just need to double check tomorrow.

Cool fix, @felipesabino !
I've met the same bug and was trying to fix it by passing tableschema.infer(PATH) instead of tableschema.infer(stream) , but then pushing a huge files breaks because of buffer overflow. Just tested your fix - works great both with very wide tables (10000 columns) and with very long ones :smile:

@felipesabino @roll @AcckiyGerman let's merge it then :)

Thanks!
We're experiencing some problem with karma on CI - that's the reason of the failing build.

@roll @anuveyatsu Awesome 🎉  thanks for merging!
It seems there was an issue with karma when running the tests in the commit merge with an error related to Connected on socket.
I can't replay any builds to see if it was an intermittent thing related to an internet connection issue or something similar, can you guys take a look?

Released https://github.com/frictionlessdata/tableschema-js/releases/tag/v1.6.0


Log rotation divolte-collector.log

Hi,
My divolte instance is running for like 6 month now, with some restart but my log file is growing indefinitely. Currently my file is 3GB.
Can you add a way to rotate log everyday and only keep like 7 days log files ?

https://github.com/divolte/divolte-collector/blob/master/rpm/SOURCES/divolte-collector.logback.xml
Is configured to do the rolling file magic.
Not sure if you use the rpm based install though.
If not you can put this file on your filesystem and use the following extra option to the starting of divolte-collector to use it:
-Dlogback.configurationFile=/etc/divolte/logback.xml
Let me know if this helps you

No I didn't use rpm, just the tar.
I will test that thanks.

Thanks it seems to be working well now. Sorry for the delay.