text:
moor_generator >=2.0.1 is incompatible with json_serializable ^3.2.5

Please help, I can't start using moor because I got this error when I added moor_generator to pubspec.yaml. thanks

Running "flutter pub get" in do_not...
Because analyzer_plugin >=0.2.1 depends on analyzer >=0.35.3 <0.39.0 and analyzer_plugin >=0.1.0 <0.2.1 depends on analyzer >=0.35.3 <0.38.0, analyzer_plugin >=0.1.0 requires analyzer >=0.35.3 <0.39.0.
And because moor_generator >=2.0.1 depends on analyzer_plugin >=0.1.0 <0.3.0, moor_generator >=2.0.1 requires analyzer >=0.35.3 <0.39.0.
And because json_serializable 3.2.5 depends on analyzer ^0.39.0 and no versions of json_serializable match >3.2.5 <4.0.0, moor_generator >=2.0.1 is incompatible with json_serializable ^3.2.5.
So, because do_not depends on both json_serializable ^3.2.5 and moor_generator ^2.3.1, version solving failed.
pub get failed (1; So, because do_not depends on both json_serializable ^3.2.5 and moor_generator ^2.3.1, version solving failed.)

You can use   json_serializable: ^3.2.3 until next version if is not important to use 3.2.5

I just released moor and moor_generator version 2.4.0, which support the latest analyzer. You can remove the dependency_overrides section and just depend on ^2.4.0. Let me know if you run into any problems, thanks!


text:
Support binding user-defined values to statements

StatementImplementation.execute() requires that all parameters are provided, but only understands a fixed set of types. It would be nice to add a Bindable interface that makes this extensible, e.g.:
+abstract class Bindable {
+  // Binds this value to a statement as parameter `i`.
+  void Bind(CommonPreparedStatement stmt, int i);
+}

... and in StatementImplementation._bindParam():
+    } else if (param is Bindable) {
+      param.Bind(this, i);

This requires that Bind() downcast to PreparedStatement, so maybe Bind() would instead take Pointer but you get the rough idea.

I'm not entirely opposed to this, but I'm not super convinced this feature should be part of the sqlite3 package either. In my mind, that package provides a direct wrapper around sqlite3 that looks like Dart. So we have an OOP API based on sound types, but we don't have stuff that sqlite3 doesn't support either (like creating CRUD statements automatically or a direct transaction API). Adding Bindable isn't much, but it also feels a lot like something that a higher-level package should do.
Do you have an example where it's considerably more convenient to use Bindable instead of just doing the translation manually? The way I see it, Bindable.Bind would just recursively call stmt.bind to set the translated value at the same index? Are you using a sqlite3 library for another language that has that feature?

Ah yeah, that's fair. I wasn't aware of that functionality in sqlite3, but I think we can add basic support for it. (Basic in the sense that it's going to be really low-level, I think even exposing the type pointer as a Dart string would be wrong given how much the document talks about how types must not be dynamic values)
Do you also need an API to read pointer values as arguments from user-defined Dart functions?

My use case is just to use an extension written in C from Dart, but I guess for completeness you would want to be able to consume/return such values from Dart extensions.
In my case there is a C API that knows how to generate such values, so all I need is to get a sqlite_stmt* to pass into that API.

My use case is just to use an extension written in C from Dart, but I guess for completeness you would want to be able to consume/return such values from Dart extensions.

I agree that a complete solution should have that. But given how rarely the feature is used and how poorly it translates to Dart with dynamic strings, I think it might be better to not have support for pointer passing interfaces at all.

From what I can tell, there is no way to bind a user-defined value to a statement at all: you must pass all parameters

Yes, the intention here is to avoid bugs caused by parameters that haven't been bound.
To support your use case, I've followed a different approach in d3382c5310b63dd70ed7882301607581104279d5. It adds a StatementParameters class which explicitly controls the way parameters are bound. This validation can be completely bypassed by using StatementParameters.bindCustom:
stmt.executeWith(StatementParameters.bindCustom((stmt) {
  stmt as PreparedStatement;

  callMyNativeFunction(stmt.handle); // stmt.handle is a sqlite_stmt*
}));

Thanks! I expect many users of this feature would commonly pass a mix of standard and custom types, but this certainly works and is easiest to implement.
Appreciate the quick turnaround. :)

Just noticed this was committed to the v2 branch and not main, is v2 considered suitable for production use?

Right, I've pushed the change on the v2 branch which will become the next stable release but has some features that are still in development.
I might have to make breaking changes before the final release. But apart from that, the FFI implementation on the v2 branch is working and I consider it suitable for production if you depend on a fixed version (e.g. sqlite3: 2.0.0-dev.0). If breaking changes happen you'd have to migrate eventually, but so do users who are currently on 1.x of this package.
The WASM implementation on the v2 branch is not stable yet.

Just as a single point of feedback:
I've tried working with this a little bit and think the original proposal may be slightly more usable -- otherwise to bind both custom and standard types in the same statement, you need to obtain a RawSqliteStatement in order to call sqlite3_bind_*.

I've added a CustomStatementParameter class in 5ddbf8c7bc7cc0fb21b2c580c9fceb5d8da7127a. It can be used to mix the two modes. So you can do something like execute([123, MyCustomValue()]) where MyCustomValue implements CustomStatementParameter and calls the C function with the statement handle. But there's no need to manually call sqlite3_bind for 123 anymore.

source: gharchive/issue

license: mit

license_type: permissive

license_source: bigquery


text:
🛑 Victoris Webby is down

In 0f96bf3, Victoris Webby (https://$VW_SITE1/) was down:

HTTP code: 500
Response time: 7200 ms

Resolved: Victoris Webby is back up in d64a87e.

license: MIT

license_source: github-api


text:
🛑 Victoris Webby is down

In 09054c0, Victoris Webby (https://$VW_SITE1/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Victoris Webby is back up in 3501193 after 3 minutes.


text:
8 Report task file not found

changed folder for search

Fixed with 'Build break task failing #10'

source: gharchive/pull-request

repo: simondel/sonar-buildbreaker-vsts


text:
replicable clusters based on k-means

Thanks for providing such user-friendly package!  The results of feature clusters are not repeatable when I use k-means through fluff heatmap  although the results are almost the same each time I run the same command. I guess it's because of k-means method. Is there a way to initialize the basic random number generator ?

There is not at the moment, but it's a good point. Essential to have a replicable analysis. I'll add it.

Once version 3.0.3 is available, you can use the -S option to set the random seed for K-means clustering.

authors: JMing-Li simonvh

repo: simonvh/fluff


text:
After 1.0a9, datasette-edit-schema to use alter-table permission

See:

https://github.com/simonw/datasette-edit-schema/issues/56

This is done.

repo: simonw/datasette


text:
03 - Create Initial JS

This is where most of the work will be focused. Throughout this step, I will be updated the html and css to match the js. This is still just an initial version. The goal is for most of the file to be working, however, it's fine if everything does not work at this stage.

Everything is not working yet. This initial push was much more basic than I had planned. The next JS issue has more code.

repo: sinclairems/JavaScript-Quiz


text:
Change window title to Preference Pane title

Found this advice in the HIG today: https://developer.apple.com/design/human-interface-guidelines/macos/app-architecture/preferences/
So maybe after #6 is merged,

[ ] rename PreferencePane.toolbarTitle to simply title or preferencePaneTitle
[ ] use the title for the window title

This also makes #12 obsolete.

I have seen it, but I have intentionally ignored it. I personally don't think it makes much sense to repeat the tab title in the window title. It's already clear which tab it's on. I was kinda hoping no one would notice 😝 Also, a lot of Apple's apps and even macOS don't follow the HIG entirely.
But I guess we should do this to follow the HIG...

Update the window's title to reflect the currently visible preference pane. For example, if your preferences window has a General preference pane, the window’s title should be General when that pane is active.

This makes the window title unusably generic in the window list. It will just show "General", which does not make it clear that the window is a preference window...

We also need to take into account this:

If your window doesn’t have multiple preference panes, then its title should be App Name Preferences.

Some observations:

Finder.app shows "Finder Preferences" as the window title for all the panes.
Which is a violation of:

Update the window's title to reflect the currently visible preference pane.

Messages.app has the minimize button enabled.
Which is a violation of:

Disable the Minimize and Zoom buttons.

Mail.app has the minimize button enabled.
Which is a violation of:

Disable the Minimize and Zoom buttons.

iTunes.app doesn't apply the changes immediately.
Which is a violation of:

Apply preference changes immediately.

Dictionary.app has the zoom button enabled.
Which is a violation of:

Disable the Minimize and Zoom buttons.

Books.app uses the tab title and the word "Preferences" as the window title, for example, "General Preferences".
Which is a violation of:

For example, if your preferences window has a General preference pane, the window’s title should be General when that pane is active.

TextEdit.app uses the window title "Preferences".
Which is a violation of:

If your window doesn’t have multiple preference panes, then its title should be App Name Preferences.

FaceTime.app uses the window title "Preferences".
Which is a violation of:

If your window doesn’t have multiple preference panes, then its title should be App Name Preferences.

Keychain Access.app uses the window title "Preferences".
Which is a violation of:

If your window doesn’t have multiple preference panes, then its title should be App Name Preferences.

Script Editor.app has the minimize button enabled.
Which is a violation of:

Disable the Minimize and Zoom buttons.

Audio MIDI Setup.app has the minimize and zoom button enabled.
Which is a violation of:

Disable the Minimize and Zoom buttons.

Xcode.app shows the tab as the window title, but then modifies the "Window" menu to show "Preferences - General", admitting that the tab title is not clear enough of a window title.
Apple, as usual, has such a double standard. They expect third-party apps to follow their HIG, but they couldn't care less to follow it themselves.
I have filed a Radar: https://openradar.appspot.com/radar?id=5029274855669760

Wow, good detective work :) I wonder what their response is going to be.
I actually like how Xcode prepends "Preferences - " to  the window title list best, just to add my 2¢.

I actually like how Xcode prepends "Preferences - " to the window title list best, just to add my 2¢.

Me too.

Should we rename toolbarItemTitle to preferencePaneTitle now that we'll use it for both the toolbar item and the window title? Kinda makes sense, since it's not really a "toolbar item" when using the segmented controls.

I didn't find a way to implement the nice addition of Preferences --  to the window list title. I am afraid this is a menu customization. We could offer a drop-in controller/service object that people tie to their window menu and that (1) removes the preference window from the regular window list, and (2) adds it as a custom entry above the regular list.
After all, Xcode's window list does look different from e.g. Finder's:

That's a strong indicator for me that they replaced the system default functionality.

Or we set the window title to "Preferences -- (preferencePaneTitle)" and replace the titlebar's label with a custom one that drops the prefix.

That actually makes more sense, as you would want to improved title in the window list and mission control too. But I think we should think about the problem a little bit more before implementing this, and it should obviously be opt-in.

Inspecting Xcode windows, it actually does not use the Preferences -- prefix in the actual window title. Folks in a Slack proposed changes during menu validations.

authors: DivineDominion sindresorhus

repo: sindresorhus/Preferences


text:
Add Scientific Writing

By @writing-resources @ashwinvis and @maehr
Discussion can be found here https://github.com/sindresorhus/awesome/pull/1700

https://github.com/writing-resources/awesome-scientific-writing
Open source tools for painless academic writing.
This should be included, because academic writing is a hassle.
PRs:

https://github.com/sindresorhus/awesome/pull/1735
https://github.com/sindresorhus/awesome/pull/1635
https://github.com/sindresorhus/awesome/pull/1644

By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.

Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.

thank you @sindresorhus we fixed it accordingly

The default branch should be named main, not master.

This is a very recent adition to the guidelines, so I don't know how strict @sindresorhus wants to be about it when it comes to previously opened PRs.
Doesn't hurt to change though 😃

@mourarthur Done

Tweet: https://twitter.com/awesome__re/status/1274373790714048513

authors: ashwinvis maehr mourarthur sindresorhus

repo: sindresorhus/awesome


text:
Add Outsourcing

https://github.com/morenoh149/awesome-outsourcing
The business practice of hiring a party outside a company to perform services and create goods. It should be added because it provides valuable information if you are thinking about outsourcing software development. Where do you start, how does this process work, etc.
I reviewed #1817 , #1816 and #1813 .
I confirm I've read and complied with the awesome requirements
(I made a new pr because I accidentally deleted the first fork, re https://github.com/sindresorhus/awesome/pull/1825)

unicorn


text:
New Yarn global directory on Windows

With the release of Yarn 1.5.1, Yarn's global installation directory on Windows has changed.  The global module storage path now includes "Data" such as AppData/Local/Yarn/Data/global/node_modules
Reference:
https://github.com/yarnpkg/yarn/pull/5336
This results in global-dirs reporting the incorrect global directory with Yarn 1.5.1 on Windows.  Subsequently, is-installed-globally fails to report global installations with Yarn 1.5.1 on Windows.

@issuehunt has funded $30.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

@sindresorhus has rewarded $27.00 to @tiagodanin. See it on IssueHunt

:moneybag: Total deposit: $30.00
:tada: Repository reward(0%): $0.00
:wrench: Service fee(10%): $3.00

authors: IssuehuntBot ttamj

repo: sindresorhus/global-dirs


text:
use travis-ci container-based infrastructure

Allows for faster builds. See docs for details.

No longer needed:

For repos we recognize on or after 2015-01-01, linux builds are sent to our container-based infrastructure.

authors: Zertz sindresorhus

repo: sindresorhus/node-module-boilerplate


text:
TypeError: URLParser is not a constructor in Node 6.12.2

The normalization function (version 3.1.0) does not work with node 6.12.2
The problem seems to be at the line:
const URLParser = typeof URL === 'undefined' ? require('url').URL : URL;

My guess is that it needs to be:
const URLParser = typeof URL === 'undefined' ? require('url').parse : URL;

Here's a sample how to reproduce the issues:
$ nvm install 6.12.2

$ nvm exec 6.12.2 node
Running node v6.12.2 (npm v3.10.10)

> norm = require('normalize-url')
[Function]

> norm('http://example.com/some/path')
TypeError: URLParser is not a constructor
    at module.exports (/Users/jdoe/workspace/node_modules/normalize-url/index.js:32:17)
    at repl:1:1
    at sigintHandlersWrap (vm.js:22:35)
    at sigintHandlersWrap (vm.js:73:12)
    at ContextifyScript.Script.runInThisContext (vm.js:21:12)
    at REPLServer.defaultEval (repl.js:340:29)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:539:10)
    at emitOne (events.js:101:20)

> require('./node_modules/normalize-url/package').version
'3.1.0'

You need the latest Node.js 6 version (Node.js 6.14).

repo: sindresorhus/normalize-url


text:
fix contribution graph's time interval selection

Visiting a profile on github and selecting a contribution year for the contribution graph sets the interval in the url query to the current month, or the last month of the given year.
e.g. https://github.com/kiprasmel
2020: selects https://github.com/kiprasmel?tab=overview&from=2020-12-01&to=2020-12-31 - last month of 2020
2021 (current year): selects https://github.com/kiprasmel?tab=overview&from=2021-07-01&to=2021-07-02 - current month
It seems the expected UX would be to select the whole year?
One would need to change the year selection's <a href attribute and replace the given start date's month to the first month 01. I can try creating a PR if we agree on this fix.

It seems the expected UX would be to select the whole year?

Then it will need to load a year's worth of contributions, which can be very long.
I don't think there is anything to "fix", but rather, you are asking for a "expand" button.
Maybe we can extend infinite-scroll to support profile page.

Or maybe we can extend infinite-scroll to support profile page.

We can't it changes the URL on every load

I tried, it doesn't work. If I set the requested dates it just loads January:
https://github.com/fregante?tab=overview&from=2019-01-01&to=2019-12-31
In short, GitHub expects you to click the year and then go backwards, starting from the "latest month" of that year ("December" for past years or "the current month" for this year).

authors: fregante kidonng kiprasmel yakov116

repo: sindresorhus/refined-github


text:
UI Frameworks Not Working Due to useExternalStore hook being undefined.

Hi,
I am attempting to use ChakraUI with Single-SPA, but I am unable to load ChakraUI, as the useExternalStore hook seems to be undefined.

Issue was with the Single SPA playground using an older version of React and overriding the import.

repo: single-spa/single-spa-react


text:
[Feature Request]: Add Hover Effect on Chatbot Icon

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Requesting the addition of a hover effect on the chatbot icon to enhance user experience and provide visual feedback when the icon is interacted with.
Use Case
Adding a hover effect will make the chatbot icon more interactive and engaging, providing users with a clear indication that the icon is clickable and interactive.
Benefits
Benefits:

Improved user engagement and interaction with the chatbot.
Enhanced visual feedback indicating the icon's interactivity.
A more polished and professional look for the chatbot feature.

Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I'm a SSOC'24 contributor
[X] I want to work on this issue

This can be done in #464 only, no need for a separate issue to add a hover effect.


text:
TadGan multivariate => ValueError: Axis 2 is outside the dimensions of X (1)

Orion version: 0.4.1
Python version: 3.7.16
Operating System: windows

Description
I am writing to seek your assistance with an issue I have been encountering while using the orion-ml package. I am trying to use the package to perform multi-variable anomaly detection on my dataset, which contains data sampled at a frequency of 20 Hz for a period of 1 month, resulting in 72000 data points per second. The dataset consists of 30 variables, and I would like to perform anomaly detection on 1-hour windows of the data.
data format:
timestamp,0,1,2,3
1220000000,0.001714,-0.000164,0.002266,0.000921
1220000003,0.001731,-0.00018,0.002233,0.000516
1220000006,0.001731,-0.000213,0.002266,0.001423
1220000009,0.001714,-0.000213,0.00225,0.000872
.
.
.
What I Did
To do this, I am using the following code:

from orion import Orion

hyperparameters = {

    "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1": {
        'window_size': 72000,
    },
    'orion.primitives.tadgan.TadGAN#1': {
        'epochs': 5,
        'verbose': True,
        'input_shape': [72000, 30],
    }
}
orion = Orion(
    pipeline='tadgan',
    hyperparameters=hyperparameters
)
orion.fit(data)

However, when I run this code, I receive the following error message:
"ValueError: Axis 2 is outside the dimensions of X (1)."
I have tried to troubleshoot this error on my own, but I have been unable to identify the cause of the issue. I was hoping that you could help me understand what is causing this error and how I can resolve it.
Additionally, I have a few questions regarding the functionality of the orion-ml package that I hope you could help me with.

Hi @mohammadx0098! Thank you for using Orion!
The issue that you are seeing is because we need to adjust the interval hyperparameter. I noticed that time between one timestamp and another is 3 seconds so I would set interval=3.
hyperparameters = {
    "mlprimitives.custom.timeseries_preprocessing.time_segments_aggregate#1": {
        'interval': 3
    },
    "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1": {
        'window_size': 72000,
    },
    'orion.primitives.tadgan.TadGAN#1': {
        'epochs': 5,
        'verbose': True,
        'input_shape': [72000, 30],
    }
}

Let me know if this solves your issue

@sarahmish
thanks.
my problem is solved .
I wonder to know if your framework could support multivariate signals?
like this dataset with 30  variables.
you have mentioned before that your framework can just do it for one target column output.
it means that I should run my code for each target column or not?

Great! Yes, precisely. Orion currently only supports detecting anomalies in one target column, therefore, if you would like to detect anomalies in multiple columns, you need run a pipeline for each target column.

Great! Yes, precisely. Orion currently only supports detecting anomalies in one target column, therefore, if you would like to detect anomalies in multiple columns, you need run a pipeline for each target column.

so I should add these lines for that?
target_column and target_shape
"mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1": {         **'target_column': 0**      }, 'orion.primitives.tadgan.TadGAN#1': {         'epochs': 5,         'verbose': True,         'input_shape': [100, 25],         **'target_shape': [100, 1],**     }

Almost. You will need to go through the columns you have.
So in the first run
"mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1": {
    'target_column': 0
}

In the second run, you will change it to the second column
"mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1": {
    'target_column': 1
}

and so forth

thanks :)

repo: sintel-dev/Orion


text:
Please update changelog for v0.11

https://github.com/Sirupsen/logrus/blob/master/CHANGELOG.md wasn't updated.

Done!

authors: AlekSi sirupsen

repo: sirupsen/logrus


text:
missing training file while running TestCases scripts

File "CartPole_MCTSRS.py", line 61, in
data = joblib.load("Data/Train/itr_50.pkl")
File "/usr/local/anaconda3/lib/python3.6/site-packages/joblib/numpy_pickle.py", line 590, in load
with open(filename, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'Data/Train/itr_50.pkl'

Fixed.

repo: sisl/AdaptiveStressTestingToolbox


text:
"Hosted by"-string printed as b'Hosted by...'

So I was speedtesting my connection when I noticed something weird
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Ziggo (ip here)...
Selecting best server based on latency...
b'Hosted by SoftLayer Technologies, Inc. (Amsterdam) [32.92 km]: 15.53 ms'
Testing download speed........................................
Download: 68.76 Mbit/s
Testing upload speed..................................................
Upload: 12.13 Mbit/s

The "Hosted by"-string is printed as b'Hosted by...'.
 b'Hosted by SoftLayer Technologies, Inc. (Amsterdam) [32.92 km]: 15.53 ms'

This has to do with the UTF-8 encoding as shown in this snippet:
 >>> print(("test".encode('UTF-8')))
 b'test'

I'm seeing this consistently too (Python 3.4.3 in Alpine Linux).
@maride any reason you didn't make 81fa7c5 into a PR? :smile:  (does it not appropriately fix the issue?)
I also see the issue when I do --list:
$ speedtest-cli --list
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
b'6412) T-Mobile (North Las Vegas, NV, United States) [7.52 km]\n1431) Switch (Las Vegas, NV, United States) [12.67 km]\n....'

A little less esoteric place I can reproduce easily is Python 3.5.1 from Debian Unstable (installing python3-pip and then doing pip3 install speedtest-cli).

Sorry if this is already obvious (I'll admit openly that my Python-fu is subpar), but it appears that this is caused by the fact that in Python 2, str.encode returns a "string" (https://docs.python.org/2/howto/unicode.html - "which returns an 8-bit string version of the Unicode string") vs Python3 str.encode which returns a "bytes object" (https://docs.python.org/3/library/stdtypes.html#str.encode - "Return an encoded version of the string as a bytes object")

Found more info on the topic: https://docs.python.org/3/howto/pyporting.html#text-versus-binary-data
I will try to make a patch for it.

I just wonder @sivel, why is it even encoded like that?

It will be fixed in a future version. It is already solved in another branch that I have.

Allright, thanks!

authors: sivel tianon tomvanderlee

repo: sivel/speedtest-cli


text:
Handle multiple failures in aggregate_failures block

RSpec 3.3 allows to group multiple failures using aggregrate_failures, but formatter doesn't not handle it. It just puts
<testcase classname="spec.sample_test" name="test with aggregate_failures with multiple failures" file="./spec/sample_test.rb" time="0.037076"><failure message="RSpec::Expectations::MultipleExpectationsNotMetError" type="RSpec::Expectations::MultipleExpectationsNotMetError">
./spec/sample_test.rb:4:in `block (2 levels) in <top (required)>'</failure></testcase>

when RSpec output is
Failures:

  1) test with aggregate_failures with multiple failures
     Got 3 failures from failure aggregation block "multiple failures".
     # ./spec/sample_test.rb:4:in `block (2 levels) in <top (required)>'

     1.1) Failure/Error: expect(0).to eq 1

            expected: 1
                 got: 0

            (compared using ==)
          # ./spec/sample_test.rb:5:in `block (3 levels) in <top (required)>'

     1.2) Failure/Error: expect(2).to eq 3

            expected: 3
                 got: 2

            (compared using ==)
          # ./spec/sample_test.rb:6:in `block (3 levels) in <top (required)>'

     1.3) Failure/Error: expect(4).to eq 5

            expected: 5
                 got: 4

            (compared using ==)
          # ./spec/sample_test.rb:7:in `block (3 levels) in <top (required)>'

Is there a way to handle it?

We got exactly the same issue, what's the Issue/PR status?

This had been a minor annoyance for us for a while and as it happens I finally got around to looking into and implementing a fix yesterday. See PR #74 for my patch. I ended up leveraging the same fully_formatted_lines method as in PR #58.

authors: TimAle jasoncodes xuantuan58


text:
Bilateral filtering on depth map is missing w.r.t Original Kinect Fusion paper

Hi,
Is there any particular reason you aren't using bilateral filtering on depth maps before processing them?
In every other paper and even the original Kinect Fusion paper uses bilateral filtering before passing on depth maps for further processing.

I checked the spatial consistency for single frame and found it is promising so that I skipped the filter directly. Still, you can apply the filter to see if there is any gain or not.

I checked the spatial consistency for single frame and found it is promising so that I skipped the filter directly. Still, you can apply the filter to see if there is any gain or not.

It didn't help noticably.


text:
Add to Favorites enhancement

Hi I'm the one requested the enhancement on sf.
Thank you for the update, it's working great, but there is something I hope you can add.
Previous in favorite window I can double click these options to add to my favorite, the script does not do it.

I added a event for it. Should be okay now.


text:
Thank You message added after submit detail

Description
Added script and for show message prevent to reload page and reset form.
Added thank you message div.
Fixes:  #366

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@sk66641 Please check it and merge !
Thank You !


text:
[Feature]: ui enhancement

Description
changed the ui of the warning modals
all the 3 warning modals ui has been changed
Fixes:  #406

Type of change

[ ] 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 not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
Before

After

@sk66641 please review this pull request


text:
Allow more PopupSettings events

Describe the feature in detail (code, mocks, or screenshots encouraged)
Currently, the popup setting is a bit limited in the case of what events it offers. Would it be possible to add a event to PopupSettings such that the popup stays visible when the user hovers over the popup.
This can open up opportunities like creating a topbar navmenu where when you hover over one of the elements, a popup is shown with the subroutes. You wouldn't really want the popup to go away when you try hovering over it and clicking one of the subroutes. You would instead, want it to go away when the user hovers away from the popup and the element that triggered the popup.
What type of pull request would this be?
New Feature
Provide relevant links or additional information.
No response

We've currently put a hold on new features for the popups.
After v2 there'll be a standalone skeleton-popup library that's going to improve ease of use and setup.
Should also allow for more options and configurability.

Was looking for these options as well (the one where the popup stays open when hovered).
@royce-mathew if you find a way to have the popup stay visible when hovered please let me know!

this is mainly just a simple workaround until we actually reach Skeleton V3

Just to clarify, the popup update will be between v2 and v3. We have a plan for introducing the new standalone features alongside the core features between major releases so folks can slowly migrate over. Then when v3 drops it'll remove the original feature from the core library - that'll be the breaking change it implements. Just so everyone is on the same page!

FYI, as we begin prepping for the new standalone popup package, we're consolidating all known issues for popups into this new thread:

https://github.com/skeletonlabs/skeleton/issues/1916

Your post will now be closed, but has been referenced in the post linked above. Please note that by doing this, your request is being folded into this larger effort. Please feel free to monitor the linked issue if you wish to track progress on this going forward.

authors: LickABrick Sarenor endigo9740 royce-mathew

repo: skeletonlabs/skeleton


text:
Update scalafmt-core to 2.5.2

Updates org.scalameta:scalafmt-core from 2.5.1 to 2.5.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #361 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #361   +/-   ##
=======================================
  Coverage   86.49%   86.49%
=======================================
  Files         135      135
  Lines        1474     1474
  Branches       36       36
=======================================
  Hits         1275     1275
  Misses        199      199

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 eb7041e...667d0f3. Read the comment docs.

authors: codecov-io scala-steward

repo: sksamuel/scapegoat


text:
Improvements

Python's method resolution order makes it difficult to use the SniperLinkAccountAdapter with another adapter.
Instead, I split it out into a SniperLinkAccountAdapterMixin that only defines the add_message method, and refactored SniperLinkAccountAdapter for backwards compatibility.
I also used a real project in the example when I updated the README.
And then while I was updating the documentation, I made a few more tweaks to the Markdown.
Thank you for this project, sniper links are cool! If you can publish a new release once these changes are merged, I'd appreciate it.

@skulegirl Do you have any feedback on this?

repo: skulegirl/django-allauth-sniperlinks


text:
Type of intersection of two object types A and B is not equal to A & B

I am trying to build a generic type with @skunkteam/types that takes an existing (object) type and extends it with a number of fields (id in this example):
import { BaseObjectLikeTypeImpl, intersection, object, string, The, TypeImpl } from '@skunkteam/types';

export type ObjectType<ResultType> = TypeImpl<BaseObjectLikeTypeImpl<ResultType>>;

export type Person = The<typeof Person>;
export const Person = object('Person', { name: string });

export type RestDocument<T> = T & { id: string };
export function RestDocument<T>(type: ObjectType<T>): ObjectType<RestDocument<T>> {
    return intersection(`RestDocument<${type.name}>`, [object({ id: string }), type]);
}

Unfortunately this throws a typescript error:
error TS2322: Type 'TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>' is not assignable to type 'TypeImpl<BaseObjectLikeTypeImpl<RestDocument<T>>>'.
  Type 'TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>' is not assignable to type 'BaseObjectLikeTypeImpl<RestDocument<T>>'.
    The types returned by 'and(...)' are incompatible between these types.
      Type 'TypeImpl<IntersectionType<[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]>>' is not assignable to type 'TypeImpl<IntersectionType<[BaseObjectLikeTypeImpl<RestDocument<T>>, any]>>'.
        Type 'TypeImpl<IntersectionType<[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]>>' is not assignable to type 'IntersectionType<[BaseObjectLikeTypeImpl<RestDocument<T>>, any]>'.
          Types of property 'types' are incompatible.
            Type '[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]' is not assignable to type '[BaseObjectLikeTypeImpl<RestDocument<T>>, any]'.
              Type 'TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>' is not assignable to type 'BaseObjectLikeTypeImpl<RestDocument<T>>'.
                The types returned by 'and(...)' are incompatible between these types.
                  Type 'TypeImpl<IntersectionType<[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]>>' is not assignable to type 'TypeImpl<IntersectionType<[BaseObjectLikeTypeImpl<RestDocument<T>>, any]>>'.
                    Type 'TypeImpl<IntersectionType<[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]>>' is not assignable to type 'IntersectionType<[BaseObjectLikeTypeImpl<RestDocument<T>>, any]>'.
                      Types of property 'types' are incompatible.
                        Type '[TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>, any]' is not assignable to type '[BaseObjectLikeTypeImpl<RestDocument<T>>, any]'.
                          Type 'TypeImpl<IntersectionType<[TypeImpl<InterfaceType<{ id: TypeImpl<BaseTypeImpl<string>>; }, TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>, TypeImpl<...>]>>' is not assignable to type 'BaseObjectLikeTypeImpl<RestDocument<T>>'.
                            The types returned by 'typeValidator(...)' are incompatible between these types.
                              Type 'Result<MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>' is not assignable to type 'Result<RestDocument<T>>'.
                                Type 'Success<MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>' is not assignable to type 'Result<RestDocument<T>>'.
                                  Type 'Success<MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>>' is not assignable to type 'Success<RestDocument<T>>'.
                                    Type 'MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>' is not assignable to type 'RestDocument<T>'.
                                      Type '(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>) | { [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<...>; }' is not assignable to type 'RestDocument<T>'.
                                        Type '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>; }' is not assignable to type 'RestDocument<T>'.
                                          Type '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>; }' is not assignable to type 'T'.
                                            'T' could be instantiated with an arbitrary type which could be unrelated to '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>; }'.
                                              Type 'MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>' is not assignable to type 'T[P]'.
                                                Type '{ id: string; }' is not assignable to type 'RestDocument<T>'.
                                                  Type '{ id: string; }' is not assignable to type 'T'.
                                                    'T' could be instantiated with an arbitrary type which could be unrelated to '{ id: string; }'.
                                                      Type 'MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>' is not assignable to type 'T'.
                                                        'T' could be instantiated with an arbitrary type which could be unrelated to 'MergeIntersection<T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>>'.
                                                          Type '(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>) | { [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<...>; }' is not assignable to type 'T'.
                                                            'T' could be instantiated with an arbitrary type which could be unrelated to '(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>) | { [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<...>; }'.
                                                              Type '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>; }' is not assignable to type 'T'.
                                                                'T' could be instantiated with an arbitrary type which could be unrelated to '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>; }'.
                                                                  Type 'MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]>' is not assignable to type 'T[P]'.
                                                                    Type '(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P] | { [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]]: MergeIntersection<...>; }' is not assignable to type 'T[P]'.
                                                                      Type '{ [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P]]: MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[P][P]>; }' is not assignable to type 'T[P]'.
                                                                        Type 'MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)["id" | keyof T]>' is not assignable to type 'T[P]'.
                                                                          Type '(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)["id" | keyof T] | { [P in keyof (T & TypeOfProperties<Writable<{ id: TypeImpl<...>; }>>)["id" | keyof T]]: MergeIntersection<...>; }' is not assignable to type 'T[P]'.
                                                                            Type '(T["id"] & string) | (T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[keyof T]' is not assignable to type 'T[P]'.
                                                                              Type 'T["id"] & string' is not assignable to type 'T[P]'.
                                                                                Type 'MergeIntersection<T["id"] & string> | MergeIntersection<(T & TypeOfProperties<Writable<{ id: TypeImpl<BaseTypeImpl<string>>; }>>)[keyof T]>' is not assignable to type 'T[P]'.
                                                                                Type 'MergeIntersection<T["id"] & string>' is not assignable to type 'T[P]'.
                                                                                Type '(T["id"] & string) | { [P in keyof (Record<string | number | symbol, unknown> & T["id"] & string)]: MergeIntersection<(Record<string | number | symbol, unknown> & T["id"] & string)[P]>; }' is not assignable to type 'T[P]'.
                                                                                Type 'T["id"] & string' is not assignable to type 'T[P]'.
                                                                                Type 'string' is not assignable to type 'T[P]'.
                                                                                Type '{ id: string; }' is not assignable to type 'T'.
                                                                                'T' could be instantiated with an arbitrary type which could be unrelated to '{ id: string; }'.

The following should work:
export type Person = The<typeof Person>;
export const Person = object('Person', { name: string });

// This is the trick here:    vvvvvvvv
export type RestDocument<T> = Writable<T> & { id: string };
export function RestDocument<T>(type: ObjectType<T>): ObjectType<RestDocument<T>> {
    return intersection(`RestDocument<${type.name}>`, [object({ id: string }), type]);
}

Objects that are passed into object to configure the validator are converted to TypeScript types on the fly (during compile time). During this conversion we ensure that any readonly annotation of the properties is removed (using the Writable type that is exported from the @skunkteam/types lib). If we wouldn't do that, a readonly property in the config-object would result in a readonly property in the resulting type and that would be unreasonable I think.
You have to forgive TypeScript for the error-message inception, we are stretching the limits here. Please try the suggested solution above and let me know.

Just came out of a call with @wvanderdeijl and we figured that this needs to be documented in the README. Maybe in the future we can think of a way to remove the mandatory use of Writable.

authors: pavadeli wvanderdeijl

repo: skunkteam/types


text:
Simplify adding new probes

Would be nice to have a more straighforward approach to add new probes.
Maybe is it possible to copy how Telegraf handles it.
They add a new folder with the "plugin" plus an import in a file with all the plugins: https://github.com/influxdata/telegraf/pull/7418/files
They relay in the "init()" function of each folder to register the plugin.

We thought about using this approach (instead of calling the Register function manually here https://github.com/skydive-project/skydive/blob/master/agent/topology_probes.go#L48-L60). But, if I remember correctly, we thought it was more explicit to call the Register function than relying on an unnamed import like import _ "github.com/skydive-project/skydive/topology/probes/docker"

authors: adrianlzt lebauce

repo: skydive-project/skydive


text:
http : fix Basic Auth, as the server need to reply WWW-Authenticate

on 401

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

rerun scale-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

run python-tests

[ci skip skydive-compile-tests]

[ci skip] skydive-compile-tests

[ci skip]

[skip ci]

@safchain all done, you can check/merge

run python-tests

authors: nplanel safchain


text:
Custom Error Handling

Is there any way we can deserialize the json  in errorBody ?

Hi,
You can resolve it using the ApiErrorModeMapper.
The map function will receive the raw ApiResponse.Failure.Error<*> model and you can customize it to your own error response. And you can handle the customized model via the map extension.

Thanks 👍

authors: TrueKage skydoves

repo: skydoves/Sandwich


text:
Allow binding of the "Tab" key

I have muscle memory of navigating browser tabs using "Ctrl-Tab" and "Ctrl-Shift-Tab". Unfortunately, lagrange does not allow me to create this particular binding.
Version 1.3

Fixed for v1.3.2.

authors: benthor skyjake

repo: skyjake/lagrange


text:
[feature] get signatures info using CLI tool

Describe your idea:
@skylot first of all, thank you very much for Jadx. This makes the android RE experience so much easier.
About the feature request, I see that jadx-gui has APK signature view which shows the details of all versions of signatures used. However, I don't see an equivalent option for jadx CLI. It'll be nice to get signature info output in a file containing all info (say, signatures.json) with a switch like --cert-info.
Additional context: I'm working on https://github.com/Surendrajat/APKLab and I'm using Jadx CLI to decompile the apk. I'd very much like to avoid adding yet another jar file just to parse certificates because Jadx already can do that.. just not in CLI yet.

@Surendrajat this can be done.
By the way, do you going to parse that file? Because jadx use info provided by apksig library (check ApkSignature class). So maybe for you, it will be easier to just use that lib.

@Surendrajat this can be done.
By the way, do you going to parse that file? Because jadx use info provided by apksig library (check ApkSignature class). So maybe for you, it will be easier to just use that lib.

@skylot thanks for the reply.
No. I am planning to keep the json(?) file as output in the project root for interested people to see.
Yes, I see that jadx uses apksig but because I'm doing it in typescript and not java, and am potentially trying to avoid just another jar :)
But for now, I think I can parse the little info uber-apk-signer spits and save that until it's done in jadx.

@skylot thanks for the reply.
No. I am planning to keep the json(?) file as output in the project root for interested people to see.
Yes, I see that jadx uses apksig but because I'm doing it in typescript and not java, and am potentially trying to avoid just another jar :)
But for now, I think I can parse the little info uber-apk-signer spits and save that until it's done in jadx.

@skylot Hi, can jadx now have a cli cmd to get an apk's signature?
By the way, I have some questions about how jadx get the signature of one apk. I have used some tools such as apksigner.jar, keytool.jar, etc. to test some apks but their result is "No Jar Signatures". However, although jadx will also get the "No Jar Signatures" on these apks, jadx also have a valid signature info about these apks.  How this worked?

@99zikke Jadx uses apksig library Whis is also used by apksigner.
Usually "JAR signature" is the name of APK v1 signature. An APK can have an V2 and/or v3 signature with or without v1 signature. Each signature version is independent of the other versions and can be present or not. Does that solves your confusion?

@99zikke Jadx uses apksig library Whis is also used by apksigner.
Usually "JAR signature" is the name of APK v1 signature. An APK can have an V2 and/or v3 signature with or without v1 signature. Each signature version is independent of the other versions and can be present or not. Does that solves your confusion?

I got it. Thank you very much!

authors: 99zikke Surendrajat jpstotz skylot

repo: skylot/jadx


text:
Inconsistent code

source code
public int testfor() {
            int tmp = 1;
            for (int i = 10; i > -1;i--) {
                if (i > tmp) {
                    for (int j = 0; j < 54; j += 4) {
                        if (i < j) {
                            for (int k = j; k < j + 4; k++) {
                                if (tmp> k) {
                                    return 0;
                                }
                            }
                            break;
                        }
                    }
                }
                tmp++;
            }
            return tmp;
        }

decompile code
public int testfor() {
        int tmp = 1;
        for (int i = 10; i > -1; i--) {
            if (i > tmp) {
                int j = 0;
                while (j < 54) {
                    if (i < j) {
                        for (int k = j; k < j + 4; k++) {
                            if (tmp > k) {
                                return 0;
                            }
                        }
                        continue;
                    } else {
                        j += 4;
                    }
                }
                continue;
            }
            tmp++;
        }
        return tmp;
    }

another
source code
public void testswitchif(int i,int index) {
			switch (i) {
			case 0:
				if (index != 7) {
					if (index ==2) {
						System.out.println(2);
					}
					if (index ==1) {
						System.out.println(1);
						break;
					}
				}
				else
				{
					System.out.println(7);
					return;
				}
				break;
			default:
				break;
			}
			System.out.println("end");
		}

decompile code
public void testswitchif(int i, int index) {
        switch (i) {
            case 0:
                if (index != 7) {
                    if (index == 2) {
                        System.out.println(2);
                    }
                    if (index == 1) {
                        System.out.println(1);
                        break;
                    }
                }
                System.out.println(7);
                return;
                break;
        }
        System.out.println("end");
    }

In newest versions testfor() is decompiled to
    public int testfor() {
        int i = 1;
        for (int i2 = 10; i2 > -1; i2--) {
            if (i2 > i) {
                int i3 = 0;
                while (i3 < 54) {
                    if (i2 < i3) {
                        for (int i4 = i3; i4 < i3 + 4; i4++) {
                            if (i > i4) {
                                return 0;
                            }
                        }
                        continue;
                    } else {
                        i3 += 4;
                    }
                }
                continue;
            }
            i++;
        }
        return i;
    }

testswitchif is decompiled good

authors: basherone sergey-wowwow


text:
Issues installing on MacOS Sonoma, Python 3.11 and 3.12

While trying to install pymediasoup in the a.m. environment I'm appearing troubles, most likely with the AV submodule.
(ms) ~ $ pip install pymediasoup
Collecting pymediasoup
  Using cached pymediasoup-0.2.2-py3-none-any.whl (41 kB)
Collecting aiortc<2.0.0,>=1.2.0 (from pymediasoup)
  Downloading aiortc-1.5.0.tar.gz (1.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 4.0 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting h264-profile-level-id<2.0.0,>=1.0.0 (from pymediasoup)
  Using cached h264_profile_level_id-1.0.0-py2.py3-none-any.whl (5.0 kB)
Collecting pydantic<2.0.0,>=1.8.1 (from pymediasoup)
  Obtaining dependency information for pydantic<2.0.0,>=1.8.1 from https://files.pythonhosted.org/packages/39/9f/ab6d19c5d3fccc1e3e0d835ac773031388802b31d93937daf878465c2ecf/pydantic-1.10.13-py3-none-any.whl.metadata
  Downloading pydantic-1.10.13-py3-none-any.whl.metadata (149 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 149.6/149.6 kB 4.5 MB/s eta 0:00:00
Collecting pyee<9.0.0,>=8.1.0 (from pymediasoup)
  Using cached pyee-8.2.2-py2.py3-none-any.whl (12 kB)
Collecting sdp-transform<2.0.0,>=1.0.1 (from pymediasoup)
  Obtaining dependency information for sdp-transform<2.0.0,>=1.0.1 from https://files.pythonhosted.org/packages/0e/47/80a3782ebe97cddb5c91f22e736cb5270288b11b1829d6943d75b90d7d5a/sdp_transform-1.0.6-py3-none-any.whl.metadata
  Using cached sdp_transform-1.0.6-py3-none-any.whl.metadata (598 bytes)
Collecting aioice<1.0.0,>=0.9.0 (from aiortc<2.0.0,>=1.2.0->pymediasoup)
  Using cached aioice-0.9.0-py3-none-any.whl (24 kB)
Collecting av<11.0.0,>=9.0.0 (from aiortc<2.0.0,>=1.2.0->pymediasoup)
  Downloading av-10.0.0.tar.gz (2.4 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.4/2.4 MB 3.9 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [80 lines of output]
      Compiling av/plane.pyx because it changed.
      [1/1] Cythonizing av/plane.pyx
      Compiling av/dictionary.pyx because it changed.
      [1/1] Cythonizing av/dictionary.pyx
      Compiling av/stream.pyx because it changed.
      [1/1] Cythonizing av/stream.pyx
      Compiling av/option.pyx because it changed.
      [1/1] Cythonizing av/option.pyx
      Compiling av/enum.pyx because it changed.
      [1/1] Cythonizing av/enum.pyx
      Compiling av/bytesource.pyx because it changed.
      [1/1] Cythonizing av/bytesource.pyx
      Compiling av/buffer.pyx because it changed.
      [1/1] Cythonizing av/buffer.pyx
      Compiling av/packet.pyx because it changed.
      [1/1] Cythonizing av/packet.pyx
      Compiling av/error.pyx because it changed.
      [1/1] Cythonizing av/error.pyx
      Compiling av/_core.pyx because it changed.
      [1/1] Cythonizing av/_core.pyx
      Compiling av/format.pyx because it changed.
      [1/1] Cythonizing av/format.pyx
      performance hint: av/logging.pyx:232:5: Exception check on 'log_callback' will always require the GIL to be acquired.
      Possible solutions:
          1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
          2. Use an 'int' return type on the function to allow an error code to be returned.

      Error compiling Cython file:
      ------------------------------------------------------------
      ...
      cdef const char *log_context_name(void *ptr) nogil:
          cdef log_context *obj = <log_context*>ptr
          return obj.name

      cdef lib.AVClass log_class
      log_class.item_name = log_context_name
                            ^
      ------------------------------------------------------------

      av/logging.pyx:216:22: Cannot assign type 'const char *(void *) except? NULL nogil' to 'const char *(*)(void *) noexcept nogil'. Exception values are incompatible. Suggest adding 'noexcept' to type 'const char *(void *) except? NULL nogil'.

      Error compiling Cython file:
      ------------------------------------------------------------
      ...

      # Start the magic!
      # We allow the user to fully disable the logging system as it will not play
      # nicely with subinterpreters due to FFmpeg-created threads.
      if os.environ.get('PYAV_LOGGING') != 'off':
          lib.av_log_set_callback(log_callback)
                                  ^
      ------------------------------------------------------------

      av/logging.pyx:351:28: Cannot assign type 'void (void *, int, const char *, va_list) except * nogil' to 'av_log_callback'. Exception values are incompatible. Suggest adding 'noexcept' to type 'void (void *, int, const char *, va_list) except * nogil'.
      Compiling av/logging.pyx because it changed.
      [1/1] Cythonizing av/logging.pyx
      Traceback (most recent call last):
        File "/Users/decades/anaconda3/envs/ms/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/decades/anaconda3/envs/ms/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/decades/anaconda3/envs/ms/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 507, in run_setup
          super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 157, in <module>
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/Cython/Build/Dependencies.py", line 1154, in cythonize
          cythonize_one(*args)
        File "/private/var/folders/7l/rc18f0m564qgtmjlzn6b_n5m0000gn/T/pip-build-env-hqi7pcce/overlay/lib/python3.12/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
          raise CompileError(None, pyx_file)
      Cython.Compiler.Errors.CompileError: av/logging.pyx
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
WARNING: There was an error checking the latest version of pip.
(ms) ~ $

Anybody heard about? Any idea, what to do with this?

PS: It works in a 3.9 VM. It also does not install in a 3.10 VM, but there with another error.
I'm fine with 3.9

I'm seeing right now there is only support up to 3.9.

v0.2.5 now supports python3.11

authors: neilyoung skymaze

repo: skymaze/pymediasoup


text:
Feature: Add multi-threading and retry when caching Tokens and Markets during startup

Abstract
As of now, 2 getProgramAccounts RPC requests are made to a Solana RPC server on startup, first to cache the USDC markets, then the SOL markets. They are very slow, and can timeout, causing startup to fail.
Fix

Add multi-threading to the 2 RPC calls, so they are made concurrently. CompleteableFuture may be preferred, or the most modern Java concurrency pattern that is elegant.
If RPC timeout is experienced during either of the threads, retry up to 3 times.

Retry doesn't seem needed anymore, now that the majority of the Solana network is on 1.10.25, and both markets cache in ~1-3 seconds with the threading.

Resolved by 54e3351

repo: skynetcap/serum-data


text:
Would it be reasonable to get the shared_ptr from a resource_handle?

Hello, I've been using the resource management classes and they've been great, but I ran into an issue as I've started to build out my project's accompanying UI library.
I would like this UI lib to not enforce an entt dependency on the consumer (especially not a requirement that they use an entt::resource_cache), but I would like to continue using it in my own project. Unfortunately, there's no way that I can see to get the underlying shared_ptr from a resource_handle, so I don't seem to have a good way to pass lifetime responsibilities along to the UI objects that will be using the resources.
My question is: would it be reasonable to add a way to get the shared_ptr from a resource_handle? Or is there some complication that I'm not seeing?

Technically speaking, it's trivial.
On the other side, I always wanted to remove the constraint on the shared pointer and have stateless loaders that manage their own memory. In this case, your suggestion would break the design.
Since caches are defined on a per-type basis, we could make the handle sfinae-friendly and allow user customizations. This would solve your issue. Actually, it's already possible in fact.
Another approach is that your library exports its own handle type to callers rather than the EnTT one. Overall, it would also make it easier to modify your engine internals without affecting other libraries, at least as long as the API of your handle doesn't change. As a first implementation, it can just be an alias for the EnTT handle.

Good ideas, I went with the specialization approach for now and it's working just fine. Thanks!

Please, leave this issue open. It made me think and I can achieve my goal with a few changes.
Briefly, if the loader returned a handle rather than a shared pointer, I could allow for specializations that don't rely on shared pointers anymore while still offering a default that works as it does nowadays.
A breaking change in the API, but also an easy one to manage, so I don't really care about it.

repo: skypjack/entt


text:
Incorrect type definition for thread_broadcast subtype

@slack/bolt version
3.19.0
Your App and Receiver Configuration
n/a
Node.js runtime version
18.12.0
Steps to reproduce:
The type for thread_broadcast is not matching the actual type of actual callback.
Actual
{
  ...envelopedEventStuff,
  "event": {
    "app_id": "<app_id>",
    "blocks": [],
    "bot_id": "<bot_id>",
    "channel": "<channel>",
    "channel_type": "<channel_type>",
    "event_ts": "<timestamp>",
    "subtype": "thread_broadcast",
    "text": "<text>",
    "ts": "<timestamp>",
    "type": "message",
    "user": "<user>"
  }
}

Type in SDK and Docs:
{
    type: 'message';
    subtype: 'thread_broadcast';
    event_ts: string;
    text: string;
    attachments?: MessageAttachment[];
    blocks?: (KnownBlock | Block)[];
    user: string;
    ts: string;
    thread_ts?: string;
    root: (GenericMessageEvent | BotMessageEvent) & {
        thread_ts: string;
        reply_count: number;
        reply_users_count: number;
        latest_reply: string;
        reply_users: string[];
    };
    client_msg_id: string;
    channel: string;
    channel_type: channelTypes;
}

Expected result:
Types in SDK must match the actual event body.
Actual result:
There is a mismatch between the event body being posted to the callback url and type definition.

What specifically is missing for you, @arunonl ?

@filmaj root is the property that is missing and it seems to be missing when bot (seems to work fine for user) does a thread broadcast.

I am unable to reproduce that. Here are the details for my test:

I wrote a simple app that listens for a message "do the broadcast" and replies-in-thread w/ a message "broadcast" that is also broadcasted.
I have a generic message listener which logs out details for the event payload.

Here is what the test looks like in the Slack client:

The code for my two handlers are:
app.message('broadcast', async ({ message, say, client, event, payload }) => {
  console.log('event', event);
});
app.message('do the broadcast', async ({ message, say, client, event, payload }) => {
  await say({
    text: 'broadcast',
    channel: message.channel,
    thread_ts: message.ts,
    reply_broadcast: true,
  });
});

And the event payload logging for the above test is:
event {
  subtype: 'thread_broadcast',
  bot_id: 'B060TP7C3SL',
  thread_ts: '1720705130.212029',
  root: {
    user: 'U02AEHE4KG9',
    type: 'message',
    ts: '1720705130.212029',
    client_msg_id: 'bc94cc53-8e54-4542-bdd7-d3f67ed922d9',
    text: 'do the broadcast',
    team: 'T029V6468RL',
    thread_ts: '1720705130.212029',
    reply_count: 1,
    reply_users_count: 1,
    latest_reply: '1720705130.809389',
    reply_users: [ 'U0604PD417C' ],
    is_locked: false,
    blocks: [ [Object] ]
  },
  type: 'message',
  ts: '1720705130.809389',
  app_id: 'A0601REQL93',
  text: 'broadcast',
  blocks: [ { type: 'rich_text', block_id: 'vc/fN', elements: [Array] } ],
  channel: 'C029YT5KEMB',
  event_ts: '1720705130.809389',
  channel_type: 'channel'
}

@filmaj thank you for trying to reproduce this. Looks like this happens when thread_ts is a random value that does not exist, like in the code below.
index.js
const express = require('express');

const app = express();
app.use(express.json())

app.post("/callback", (req, res) => {
    console.log(req.body);
    res.json({challenge: req.body?.challenge});
});

app.listen(3000, async () => {
    console.log('Server is running on port 3000');
})

sendMessage.js
const signingSecret = ""
const token = ""
const channel = ""

const { App } = require('@slack/bolt');
const slackApp = new App({
    signingSecret,
    token
});
slackApp.client.chat.postMessage({
    channel,
    text: "broadcast message from bot",
    thread_ts: "1720709525",
    reply_broadcast:true
}).then((res) => {
    console.log('Message sent: ', res.ts);
}).catch((err) => {
    console.error(err);
});

O wow, actually you are right, and I think this is backend bug: if you send a message via chat.postMessage and provide garbage for thread_ts and reply_broadcast: true, then a regular message will be posted and your app will receive a type: message + subtype: thread_broadcast event for that message!
Going to mark that part as a backend bug. Separately, yes, we can add optional parameters for bot_id to the event.

authors: arunonl filmaj

repo: slackapi/bolt-js


text:
[BUG] Can't access CLA assistant

Describe the bug
I can't sign CLA from Contributing guidelines. I found an error.
I want to contribute but I can't now.
Requirements (place an x in each of the [ ])**

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

To Reproduce
Access to https://cla-assistant.io/slackapi/deno-slack-api
Expected behavior
A developer can begin to sign CLA.
Screenshots

Reproducible in:
deno-slack-api version:
Deno version:
OS version(s):
Additional context
Add any other context about the problem here.

@filmaj @WilliamBergamin Please check a site (CLA assistant) configuration or a contribution guide 👀

@whywaita, apologies for our delayed response here.
We've switched from the CLA assistant to the Salesforce one; however, it seems that we haven't updated the contribution guide yet 🤦 . Our team will resolve this later, so please proceed with your pull request and sign our newest CLA. Moreover, please remember that, if you plan to make significant changes, you should start a discussion before sending such code changes. Thank you for your interest!

@seratch Thank you for your quick comment!
I got it, I will open an issue and pull-request.

Thank you very much for pointing this issue out. We've resolved the issue on the contribution guide ✅

authors: seratch whywaita

repo: slackapi/deno-slack-api


text:
ModuleNotFoundError: No module named 'aiohttp'

(Filling out the following details about bugs will help us solve your issue sooner.)
Reproducible in:
pip freeze | grep slack
python --version
sw_vers && uname -v # or `ver`

The Slack SDK version
slack-sdk==3.18.1
Python runtime version
Python == 3.7
OS info
ProductName:    macOS
ProductVersion: 12.4
BuildVersion:   21F79
Steps to reproduce:
(Share the commands to run, source code, and project settings (e.g., setup.py))
1.Import both WebClient and SlackApiError from slack package  to my Apache Airflow DAG
2.Apache Airflow sends an error
3.
Expected result:
Apache Airflow DAG succesfully loaded to webserver UI
Actual result:
Broken DAG: [/opt/airflow/dags/trigger_dag.py] Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.7/site-packages/slack/__init__.py", line 7, in <module>
    from slack_sdk.rtm import RTMClient  # noqa
  File "/home/airflow/.local/lib/python3.7/site-packages/slack_sdk/rtm/__init__.py", line 16, in <module>
    import aiohttp
ModuleNotFoundError: No module named 'aiohttp'

Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @PapiG0nz0 - aiohttp is an external module used by python-slack-sdk. I'm not so familiar with the Apache Airflow DAQ environment, but you will need to make sure that module is available for the Python SDK to work.

@PapiG0nz0
I don't think that your Airflow DAG needs the RTM client. If you are developing new code, you can use slack_sdk modules instead.
This SDK provides slack modules for smooth migration from slackclient v2 package. Refer to the v3 migration guide for details. If you have existing code, you can go with either of:

Migrate to slack_sdk modules instead of importing slack
Add aiohttp to your dependencies if you need to import slack modules for some reason

I hope this helps.

authors: PapiG0nz0 seratch srajiang

repo: slackapi/python-slack-sdk


text:
Send message even when Github Action fails

Description
I noticed that no message is sent whenever the action fails to execute (see the image below). Is there a way to force the message for any action state? There are cases when error is as important as success (e.g. failing to build the app and deploying it).
Fwiw, I'm using the Slack Workflow Builder approach.

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hey @fnando, this is a pretty neat use case! It seems like this might be possible by adding if: ${{ always() }} to this step of your GitHub Action. An example with failure() can be found on these docs, but the same syntax should apply to always(). I hope this is helpful!

authors: e-zim fnando

repo: slackapi/slack-github-action


text:
Text input not following the keyboard

What is the best was to debug this behaviour for that I can send you a better issue description? I am asking because this should be fixed with Version 9.4.

Thank you for your kindness. But I can't reproduce. For me it seems that in my implementation the textinput does not recognize that it becomes firstResponder.
Maybe I miss something new in the initialization stage?
The only code I use here is
    inverted = false
    bounces = true
    shakeToClearEnabled = true
    keyboardPanningEnabled = true
    shouldScrollToBottomAfterKeyboardShows = true
    let attachmentIcon = UIImage(named: "icon_Attachment") as UIImage?
    leftButton.setImage(attachmentIcon, forState: .Normal)

    // TODO: Find better solution that does not break autoconstraints
    // ...
    leftButton.translatesAutoresizingMaskIntoConstraints = true // this breaks autolayout with constraints

    leftButton.frame = CGRectMake(8, 8, 25, 30)
    leftButton.contentMode = .ScaleAspectFill
    leftButton.imageView?.contentMode = .ScaleAspectFill
    leftButton.imageView?.clipsToBounds = false
    leftButton.tintColor = MyTheme.sbColorPaletteDarkGrey

    rightButton.setTitle("Send", forState: .Normal)

    textInputbar.autoHideRightButton = true
    textInputbar.maxCharCount = 4000;
    textInputbar.counterStyle = SLKCounterStyle.Split
    textInputbar.counterPosition = SLKCounterPosition.Top
    textInputbar.editorTitle.textColor = MyTheme.sbColorPaletteDarkGrey
    textInputbar.editorLeftButton.tintColor = MyTheme.sbColorPaletteDarkGrey
    textInputbar.editorRightButton.tintColor = MyTheme.sbColorPaletteDarkGrey

    textView.layer.borderWidth = 0
    textView.keyboardType = UIKeyboardType.Default
    textView.placeholder = "Type new message here..."
    textView.placeholderColor = MyTheme.sbColorPaletteMediumGrey

My class includes
class MessageStreamViewController: SLKTextViewController, MyCallbackDelegate, MyProtocol, UIImagePickerControllerDelegate, UINavigationControllerDelegate {

Neither the textInputbarDidMove is triggered nor the overridden didChangeKeyboardStatus does fire.

@headkit Do you by any chance override the method func target(forAction action: Selector,   withSender sender: Any?) -> Any? of SLKTextView? I modified the method to prevent "select/copy/paste menu" and screwed something up, when I removed the override it worked again. Spend my entire afternoon figuring it out...

@jpodcedensek hey, thanx for your thoughts on that - unfortunately I don't overwrite any SLKTextView methods at all. I am still diggin'...

strange - gone it is, working fine!

@headkit How to solve this problem? Could you let me know?

For anyone coming in after me: I had to disabled IQKeyboardManagerSwift using viewDidAppear and viewWillDisappear methods.

The above comment helped me.
I did the following:
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)

        IQKeyboardManager.sharedManager().enable = false
    }

    override func viewWillDisappear(_ animated: Bool) {
        super.viewWillDisappear(animated)

        IQKeyboardManager.sharedManager().enable = true
    }

authors: DanH-SyncInteractive ShawnBaek cbrandsma-cs headkit jpodcedensek

repo: slackhq/SlackTextViewController


text:
seperated -> separated

Fixes a typo

 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.Evan Jensen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR @evanpjensen! We can merge this once you signed the CLA.

Fixed by #302

authors: CLAassistant evanpjensen nbrownus wadey

repo: slackhq/nebula


text:
Added basic macOS signing

In reference to issue #24 this adds a new make target for signing macOS binaries. I didn't integrate into release because it would seem weird to only have the macOS signing there and I don't have the moment right now to figure out the linux stuff and I don't know the Windows one.
But to my knowledge this is about what it should look like, the default TEAMID is the Slack one (pulled from the signed macOS Slack app) but can be overriden for enterprises deploying their own forks of nebula (or ones with unmerged master changes) with:
make TEAMID=<Some other TEAMID> sign-darwin

 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.Mitchell Grenier seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

This probably needs to be reworked for notarization. But I might imagine there's some work there to support iOS

authors: CLAassistant directionless obelisk


text:
Allow listen.host to contain names

On some networks (like fly.io, DO) it is desirable to listen on specific address and the easiest way to discover that address is by using a known name.
Closes #817

any docs on this feature to add to https://nebula.defined.net?

authors: jasikpark nbrownus


text:
Drop support for Ruby 2.3 and 2.4

Per discussion in #1360

No need for it to go into this PR, but what is the status of building on Ruby 3.0? Are we waiting for libraries to update to be compatible?

No need for it to go into this PR, but what is the status of building on Ruby 3.0? Are we waiting for libraries to update to be compatible?

Middleman uses the deprecated URI::escape method which was removed in Ruby 3.0, so have to wait for an upstream release there before slate can support 3.0.

Middleman uses the deprecated URI::escape method which was removed in Ruby 3.0, so have to wait for an upstream release there before slate can support 3.0.

Sorry to have missed this, but does the Gemfile need updating too?
https://github.com/slatedocs/slate/blob/e546ad54c52d56089fee9c1376f18598d6408264/Gemfile#L1

Sorry to have missed this, but does the Gemfile need updating too?
https://github.com/slatedocs/slate/blob/e546ad54c52d56089fee9c1376f18598d6408264/Gemfile#L1

authors: MasterOdin MikeRalphson

repo: slatedocs/slate


text:
irrlicht 1.8 and .NET 7

Hi
Would it be possible to port your fantastic library so it supports latest irrlicht 1.8 and also .NET 7?
Thx

Hopfully it's as easy as changing the TFM from netcoreapp3.1 to net7.0-windows.
It does already target netcoreapp3.1 which you should be able to reference from a net7.0-windows assembly
https://www.nuget.org/packages/Irrlicht.NetCore.x64

Thanks i try it!
.net core will be dropped by microsoft I have read (or maybe already is).
Will you try to make .net 7 version?
Do you know if original irrlicht lime project is abandoned?

Is it possible to allow issues in the irrlicht lime fork? They are disabled.
I want to test it and report problems I find

Fixed, sorry about that, I never noticed issues were disabled!
I have made some custom changes in this fork. Mostly around setting the absolute position of scene nodes. The default behavior is unchanged.
I haven't updated the irrlicht version since forking irrlicht lime in 2020.
I don't see any activity on the original repo since 2019.

And yes, netcoreapp3.1 is out of supports since a few weeks ago

Do you want to check if there are things not included/updated yet so irrrlicht latest version is supported?

I will check, but I don't have much personally invested. I welcome your contributions!

Unfortunately I csn just use irrlicht and am not good enough to contribute to this :(

I've updated irrlicht to the latest copy from the mirror at https://gitlab.com/pgimeno/irrlicht-mirror.
Then, I updated my fork off irrlicht lime (Irrlicht.Net) to target net6.0-windows and use vs2022 cpp toolset (v143; it was v142). Everything compiled but I did not run it.
my fork of irrlicht: https://github.com/slater1/Irrlicht
used by my fork of irrlicht lime: https://github.com/slater1/Irrlicht.Net

Can confirm it works. Tested with GraphicsTemplate

A call to GUIEnvironment.AddImage(...) threw an AccessViolationException. I don't have time to look into it. I commented it out in the app.
Be sure to copy Ijwhost.dll and Irrlicht.dll from Irrlicht.NetCore\bin\x64\Release. This is done automatically with the nuget packages but net6.0-windows isn't published (yet)

Thanks, I have the same result so I did it correctly :)
Can I ask why you stay with .NET 6.0 and not use 7.0?

Maybe it's a good idea to move the examples from irrlicht lime to your repo once they all are working?

Great that it works for you too! I chose 6.0 because it it supported longer than 7.0. https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
I suppose it would be good to port some examples. I haven't because I don't need it and my fork is pretty obscure. But if it gathers interest it makes sense to.


text:
Try to cythonize when Cython is installed

Change to use

Cython to compile .pyx
GCC to compile .cpp
Pure Python

if available when running
python setup.py install

Hello
when i run python setup.py install
i get a erro or warning
building 'fastdtw._fastdtw' extension
setup.py:81: UserWarning: compilation failed. Installing pure python package
warnings.warn(reason+'compilation failed. Installing pure python package')
how can i fix it.
thanks a lot

@zhahaoqiang
Cloud you paste the entire error message?
Please also take a look at:
https://github.com/slaypni/fastdtw/issues/13

authors: slaypni zhahaoqiang

repo: slaypni/fastdtw


text:
Add configurable stream sorting

Possible options:

Order by relevance (this is the current default)
Order by download size
Order by download time
... (maybe more possibilities?)

The options are configurable here when accessing the search api:
https://github.com/sleeyax/stremio-easynews-addon/blob/726239538ccec2cc61c15d63a7f1cad8320983e3/packages/api/src/api.ts#L29-L34

One suggestion would be if it's possible to sort by HDR thing.
Like priority would be Dolby Vision > HDR > 4k > 1080p

One suggestion would be if it's possible to sort by HDR thing.
Like priority would be Dolby Vision > HDR > 4k > 1080p

Create a new issue for that.

authors: sleeyax znre

repo: sleeyax/stremio-easynews-addon


text:
Small issue with Xcode 7

I just downloaded Chipmunk from here and run example in Xcode 7, as result I see issue in cpSpatialIndex.h: - ../Chipmunk-7.0.1/include/chipmunk/cpSpatialIndex.h:57:5: Unknown command tag name.
/// @private
So, I just changed it to
// @private
and it compiles ok. Xcode 7.1.1

It's fixed in the master branch (I think). I should probably make another tag.

+1, just ran into that error :)

authors: KAMIKAZEUA gr8bit slembcke


text:
Component Wrappers

Storages like FlaggedStorage and ChangedStorage (I'm assuming most "wrapper" storages as well) could be improved if it was possible to return wrapper types instead of just components themselves:
pub trait UnprotectedStorage<T> {
    type Wrapper<'a>;
    type WrapperMut<'a>;
    ...
    fn get<'a>(&'a self) -> Self::Wrapper<'a>;
    fn get_mut<'a>(&'a mut self) -> Self::WrapperMut<'a>;
    ...
}

impl<T> UnprotectedStorage<T> for ChangedStorage {
    type Wrapper<'a> = &'a T;
    type WrapperMut<'a> = Tracked<&'a mut T>;
    ...
    fn get<'a>(&'a self) -> &'a T { ... }
    fn get_mut<'a>(&'a mut self) -> Tracked<&'a mut T> { ... }
    ...
}

Alternatively:
pub trait UnprotectedStorage<'a, T> {
    type Wrapper: 'a;
    type WrapperMut: 'a;
    ...
    fn get(&self) -> Self::Wrapper;
    fn get_mut(&mut self) -> Self::WrapperMut;
    ...
}

impl<'a, T> UnprotectedStorage<'a, T> for ChangedStorage {
    type Wrapper = &'a T;
    type WrapperMut = Tracked<'a, &'a mut T>;
    ...
    fn get<'a>(&'a self) -> &'a T { ... }
    fn get_mut<'a>(&'a mut self) -> Tracked<'a, &'a mut T> { ... }
    ...
}

Since it would eliminate the need for things like maintain methods and ease overall usage of the storages to be used similar to any other.
Sadly, I don't think it is possible in current Rust's type system until either we get lifetime ATCs or a non-'static TypeId (since this is what prevents just adding a lifetime to the UnprotectedStorage<T>.

It is possible with little boilerplate.
trait Wrapper<'a> {
  type Mut;
  type Ref;
}

trait UnprotectedStorage<T> {
  type Wrapper: for<'a> Wrapper<'a>;
  fn get<'a>(&'a self) -> <Self::Wrapper as Wrapper<'a>>::Ref;
  fn get_mut<'a>(&'a mut self) -> <Self::Wrapper as Wrapper<'a>>::Mut;
}
``|

I think this would unnecessarily complicate the API. If you need such a special solution you can just as well create your own component storages (which is quite easy as can be seen in specs-static).

authors: Aceeri omni-viral torkleyy

repo: slide-rs/specs


text:
Sli.dev and twoslash cause strange behavior

Describe the bug
When I use twoslash, they statically appear on 1 slide as shown in the screenshot below.... (tested on my custom and default theme)
Presentation repo

Desktop (please complete the following information):

OS: Windows 11
Browser: 122.0.6261.69
Slidev version: ^0.47.5

Can you help narrow it down to a minimal reproduction? Thank you.

Can you help narrow it down to a minimal reproduction? Thank you.

https://stackblitz.com/edit/slidev-btd8ya?file=slides.md
❯ npm list
slidev-btd8ya@ /home/projects/slidev-btd8ya
+-- @slidev/cli@0.48.0-beta.19
+-- @slidev/theme-default@0.25.0
`-- @slidev/theme-seriph@0.25.0

Can you help narrow it down to a minimal reproduction? Thank you.

any updates?

Can you help narrow it down to a minimal reproduction? Thank you.

By the way, your presentations are very cool! Don't you share their source code?

@kravetsone 👉 here

Can you help narrow it down to a minimal reproduction? Thank you.

twoslash turned white on beta.... By the way, everything is in place when exporting to PDF

Can you help narrow it down to a minimal reproduction? Thank you.

Can you fix it today? It's important to me)

Can you fix it today? It's important to me)

I will try to fix this later. But it seems a little bit hard.

Can you fix it today? It's important to me)

I will try to fix this later. But it seems a little bit hard.

Thank you! Slidev is awesome...

I spent 1 hour on this but made no actual progress. However, there is a workaround which hides all the popovers when the current slide has no popover:

add the following to your <root>/styles.css:

.v-popper__popper.v-popper--theme-twoslash {
  display: none;
}

add the following to your <root>/components/ShowTwoslash.vue:

<template>

</template>

if you want to enable twoslash popovers on a slide, add the following to that slide:

<ShowTwoslash />

I spent 1 hour on this but made no actual progress. (It's really hard!) However, there is a workaround that can hide all the popovers when the current slide doesn't need them.

add the following to your <root>/styles.css:

.v-popper__popper.v-popper--theme-twoslash {
  display: none;
}

add the following to your <root>/components/ShowTwoslash.vue:

<template>

</template>

if you want to enable Twoslash popovers on a specific slide, add the following code to that slide:

<ShowTwoslash />

It hides these elements on other slides but they are still on the edge))
well, I'll wait! Thanks for the work!

authors: KermanX antfu kovsu kravetsone

repo: slidevjs/slidev


text:
Can't build Embedded example

Run ./build.sh, got error in screenshot. Need some help.

If I run it again, the first error gone. But last one remain.

can you verify that you are running it with a recent developer toolchain?
swift --version
should be something like Apple Swift version 6.1-dev (LLVM 89ccf4b8a46135a, Swift 6a5ae8d5df144dd)

@sliemeobn I'm using a swift 6.0 from https://github.com/swiftwasm/swift/releases.
So where I can find a 6.1 dev snapshot?

you don‘t need a wasm/wasi SDK or toolchain, just a plain Swift toolchain from swift.org.

Change to swift 6.1 snapshot and run swift package update make it work. Just need some guide in the readme.

authors: bestwnh sliemeobn

repo: sliemeobn/elementary-dom


text:
Add text/plain to known content types

Add text/plain to known content types in AbstractHandler.php.

Coverage remained the same at 97.106% when pulling fcea184d2813e33cc8eb1235c8c0c9b01df199ff on filips123:patch-1 into 1ca78596de8f1b0e2389b812a6ce64d1ccd9e49f on slimphp:3.x.

What is the use-case that this change is for?

It could be for some text based or CLI websites and applications.

Do you have an actual app in production that needs this change? I'm struggling to imagine a text/plain website and haven't seen one in the wild.

No. This is just an idea, but it may be usable for someone.

I think we'll wait for someone to have a production use-case for this one.

authors: akrabat coveralls filips123

repo: slimphp/Slim