Alias get_client directly instead of via a function

Summary
get_client is the main entrypoint to getting a Client instance. Currently, it
is merely a wrapper for create_client, taking only **kwargs. Due to the
wrapping and use of **kwargs, all type hints are lost.
To improve the situation without breaking existing code, get_client is
redefined as a simple alias of create_client. Additionally, create_client is
altered to force the use of keyword arguments according to the PEP 3102 [0]
asterisk. This combination of changes improves the usability of the get_client
function while preserving all existing functionality.
[0] - https://peps.python.org/pep-3102/
Checklist
Delete items not relevant to your PR:

[x] Unit and integration tests covering the common scenarios were ~added~ already included
[x] A human-readable description of the changes was provided to include in CHANGELOG

Thanks for the usability improvement!


Blynk ioT style button

The node has two Button ON property's
The first one works correctly by indicating "ON" in the debug.
The second one also indicates "ON" in the debug even though it is set to be "OFF".
Can you check it out?
Thanks, Joe
<EMAIL_ADDRESS>

I finally got it to work.
I re loaded None Red and started over with my project.
I made sure that the "topic" info from my ESP 8266 consided with the Node Red Node.
I kept researching the available documentation.
The html screen looks to be miss labeled though.
Thanks, Joe


Update topology-considerations.md

Added SQL AoAG supported configuration notice to section likely to referenced by individuals designed a new solution; existing notice under "Deploy and Use" --> "First Time Deployment" --> "Server Setup: SQL" is routinely overlooked.

@RKauf00 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Admin note: If the PR is approved, the Markdown syntax for the custom alert needs to be fixed before merging. The PR review team can do this.

@billmath Could you review this proposed update to your article?
Thank you!

@billmath Could you let us know whether this pull request from last October being reviewed?
Thanks.

@billmath  - nudge

Closing per the PR per Eugene's comment above.


Manage columns

Great job with the design, it is exactly what I was looking for.
I'd like to ask if it would be possible to add a feature to manage the columns dynamically?
Or at least provide instruction to customize the names or number of columns.
I am thinking about using it for more than one folder, with different sets of columns.
If you allow me to, I would probably spend some time trying to implement this feature.

While the number of columns is hardcoded to 6 right now, you can already control the names of the columns. Check out the js\config.js for the description of the folders. The name attribute is what you want to edit.

I would also love to see the feature to configure the columns individually ;)

Hi @evrenvarol ,
thank you very much for providing this cool project. :+1:
@FireFighter1017, @salomonderossi , @GrimmiMeloni ;
Hi guys, I have been able to manage the number of columns programmaticaly, with little manipulation of the HTML/CSS and JS-Code.
My use case: Remove the Focus column for the Kanban View!
Basically, you have to follow the 5 steps:

Delete the Focus folder in Outlook Tasks view
Open to the config.js file and comment the FOCUS_FOLDER ... ( line 17)
Open to the app.js file and comment the $scope.focusTasks ... ( line 30) Result: You should be able to drag&drop items in the Kanban view. But you should still see the former Focus column.
Open to the kanban.html file and comment the complete lane 4 ( line 148 - 180). Result: This will remove column from the Kanban view.
Open to the bootstrap.min.css file and search for the css class .col-lg-2 and increase the width from 16.666667% to 20%

@devsoccercode Thank you. Works for me

@salomonderossi I have updated my comment above and added a new point 4.
Dropping task did not work for me to 100%, so I have removed the line  which checks whether the number of task items exceeds the predefined limit for the non-existing FOCUS folder

Hi @evrenvarol , thank you very much for providing this cool project. 👍
@FireFighter1017, @salomonderossi , @GrimmiMeloni ;

Exactly what I was looking for!
Thanks a lot.


TempFile Cleanup using Tkinter

TempFile Cleanup using Tkinter
This Pull Request resolves Issue #<000>
Use GUI to clean Temp Files with Tkinter in Python.

Are there any updates or should we close the PR?


Wrong/No urls module for user.api

user.api.urls is actually a duplicate test module of user.tests.test_drf_urls

@dipen30 Everything is OK it seems, just the test for the api (test_drf_urls, test_drf_views) fails as they need the url file for the api.


Develop merge release/v1.1.0

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully


Pin babel-preset-react-app to a minor core-js version as per core-js readme

Is your proposal related to a problem?
I've been trying to polyfill Promise.allSettled for Edge by using react-app-polyfill/stable but failing. My expectation was that it should work since<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>and Promise.allSettled was moved into core-js/stable on v3.2.0.
I've dug a bit deeper to find that babel-preset-react-app has corejs set to major version 3 (https://github.com/facebook/create-react-app/blob/v3.4.1/packages/babel-preset-react-app/dependencies.js#L91)
Looking at the core-js readme I see this:

Warning! Recommended to specify used minor core-js version, like corejs: '3.6', instead of corejs: 3, since with corejs: 3 will not be injected modules which were added in minor core-js releases.

Locally I've set corejs in babel-preset-react-app to 3.2 (just a proof this is the issue) and I can see Promise.allSettled is now polyfilled correctly.
It's not clear to me why babel-preset-react-app does not follow the advice of core-js and pin to a minor version?
Describe the solution you'd like
Update babel-preset-react-app to pin to a minor version of corejs in it's configuration.
Describe alternatives you've considered
Eject and manage babel-preset-env myself but I'm very reluctant to go down this route.
I look forward to being told why things aren't as simple as changing babel-preset-react-app configuration :)

I had the same problem four months ago.
At that time, I solved it by importing the specific polyfill instead of just corejs
import 'core-js/modules/esnext.string.match-all';

I had the same problem four months ago.
At that time, I solved it by importing the specific polyfill instead of just corejs
import 'core-js/modules/esnext.string.match-all';

Thanks @pakaponk, I'm doing the same as you for as a workaround knowing the CRA is specifically targetting v3 of core-js.
This issue is really to explore what's stopping CRA from targetting a more recent version of core-js. 3.0.0 was released over a year ago now (19 Mar 2019).

The similar issue, babel-plugin-polyfill-corejs3 removes my side-effect import because of babel-preset-react-app provides old version of core-js and there is no way to specify a correct version at least 3.17.
So I just wanted to use the latest stable ES with nice stuff like Array.prototype.at, Object.hasOwn and so on and
importing it like a polyfill import "core-js/es/array/at"; with only side effect does not work :(
The sole solution I've found so far is to use export * from "core-js/es/array/at"; instead of side effect import, but I don't like it.
It would be much better to add an option for corejs version, or at least update it to the latest 3.20

I have a similar issue when polyfilling Array.prototype.at

If you are using craco to override CRA config - you can override corejs version by using the following code
// craco.config.js

const path = require("path");

const fixCoreJsVersion = (babelConfig) => {
  babelConfig.presets.forEach((preset) => {
    if (preset?.[1]?.corejs)
      preset[1].corejs = require("core-js/package.json").version;
  });
};

const fixPresetReactAppLoaderOptions = (babelLoaderOptions) => {
  const babelPresetReactAppDependencies =
    require("babel-preset-react-app/dependencies")(null, {
      helpers: true,
    });

  const babelPresetReactApp = require("babel-preset-react-app")(null, {
    runtime: "automatic",
  });

  fixCoreJsVersion(babelPresetReactAppDependencies);
  fixCoreJsVersion(babelPresetReactApp);

  return {
    ...babelLoaderOptions,
    presets: babelLoaderOptions.presets?.map((preset) => {
      if (
        typeof preset?.[0] === "string" &&
        preset[0].includes("babel-preset-react-app/dependencies")
      ) {
        return babelPresetReactAppDependencies;
      }
      if (
        typeof preset?.[0] === "string" &&
        preset[0].includes("babel-preset-react-app/index")
      ) {
        return babelPresetReactApp;
      }
      return preset;
    }),
  };
};

module.exports = {
  // ...
  babel: {
     // ...
    loaderOptions: fixPresetReactAppLoaderOptions,
  },
};

As soon as CRA will be updated to automatically use current node_modules core-js version (same as in the snippet above) – you will be able to remove this code snippet from you craco config 🙌


Add salary field and associated tests

Currently, InTrack does not have a field for Salary. As a user looking for internships, I would want to be able to track the salary that each internships offer so that I can make an informed decision on which internship offer to choose or prioritize. Let's add a ```Salary`` field to accommodate this, and add the associated tests to improve coverage.

Codecov Report
Base: 70.04% // Head: 69.88% // Decreases project coverage by -0.15% :warning:

Coverage data is based on head (883c3f4) compared to base (9a1036c).
Patch coverage: 70.42% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #111      +/-   ##
============================================
- Coverage     70.04%   69.88%   -0.16%
- Complexity      523      524       +1
============================================
  Files            94       94
  Lines          1679     1687       +8
  Branches        177      177
============================================
+ Hits           1176     1179       +3
- Misses          453      459       +6
+ Partials         50       49       -1

Impacted Files
Coverage Δ

.../java/seedu/intrack/logic/commands/AddCommand.java
100.00% <ø> (ø)

...a/seedu/intrack/logic/commands/AddTaskCommand.java
0.00% <0.00%> (ø)

...eedu/intrack/logic/commands/DeleteTaskCommand.java
28.57% <0.00%> (ø)

.../java/seedu/intrack/model/util/SampleDataUtil.java
37.93% <0.00%> (-9.90%)
:arrow_down:

src/main/java/seedu/intrack/ui/InternshipCard.java
0.00% <0.00%> (ø)

.../java/seedu/intrack/ui/SelectedInternshipCard.java
0.00% <0.00%> (ø)

...in/java/seedu/intrack/model/internship/Salary.java
80.00% <80.00%> (ø)

...ava/seedu/intrack/model/internship/Internship.java
93.93% <88.88%> (ø)

...java/seedu/intrack/logic/commands/EditCommand.java
97.36% <100.00%> (ø)

...va/seedu/intrack/logic/commands/RemarkCommand.java
100.00% <100.00%> (ø)

... and 7 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add data for Signify LWA005

This is another version of the Hue Filament E27. Measurements taken with the Sonoff S31.

You are sure this is a E27 bulb? Because when I search around it looks like a E26 fitting.

We cannot fully trust the Blakkader database, it is also user generated (so model names taken from this database may be incorrect or ambiguous).
Slight variations in thread dimensions are a thing of the past, but it is actually possible to screw an E26 bulb into an E27 socket and vice versa. The same situation is with the E12 and E14.
So, I can suggest the description as "E26 / E27".
https://www.waveformlighting.com/home-residential/e26-vs-e27-bulbs-are-they-interchangeable

@bramstroker / @nepozs, my mistake. I corrected the model.json to reflect E26.

@scottrhoyt thanks.
@nepozs also thanks for input. All references I found referred to E26, not only zigbee blackadder. Anyway it's not that important, it's only informative for the supported models list.

There are also European version of this bulb, but I don't know their real model names
https://www.amazon.de/-/pl/dp/B099NQQGGX/
https://www.amazon.de/-/pl/dp/B07V38RXFL


Minor changes to accept string in definition file

just one line changes - you may want to do it yourself or drop if you disagree.
headerClass?: string | string[] | ((params: any) => any);
note: last line ending was from my vscode IDE; you may ignore.

this isn't exactly right:
headerClass?: string | string[] | ((params: any) => any);
should be:
headerClass?: string | string[] | ((params: any) => string | string[]);
doing the second required some cleanup in the core code, so i've fixed it up and checked it in outside of this PR.
thanks for the suggestion.

:thumbsup:


Add Chinese (simplified) translations

Add Chinese (Traditional) language translation file
Tests:

Add test for outdated compiled QM file, seems to be deterministic for the same input .ts file
More reliable test by creating a temp directory so as not to change the translation files in the git repo after running test
Fix creating new translation files from scratch and not updating the current files

Title was wrong, this is simplified!

@gijskoning I don't think XML vs. JSON makes it any more difficult to edit the file, however it's recommended to use QT Linguist, and it's required as that's the format QT uses. Linguist provides a nice UI, with various warnings like leading and trailing punctuation and translation suggestions. lupdate (run ./update_translations.py) also automatically updates the source code line numbers when they're moved, which is only for Linguist


Update measurements to use invoke

[msal-browser] Updates remaining measurements to use the invoke wrappers. This will also result in a few more measurements we're not collecting today.
Will follow up with msal-common changes in a separate PR

Codecov Report

Merging #6484 (84f70a5) into dev (81d34b4) will decrease coverage by 2.30%.
Report is 319 commits behind head on dev.
The diff coverage is 60.52%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
?

msal-browser
85.34% <ø> (-1.13%)
:arrow_down:
Carriedforward from bc3840d

msal-common
83.05% <ø> (-1.49%)
:arrow_down:
Carriedforward from bc3840d

msal-core
?

msal-node
80.52% <ø> (-2.87%)
:arrow_down:
Carriedforward from bc3840d

msal-node-extensions
68.25% <60.26%> (-7.39%)
:arrow_down:
Carriedforward from bc3840d

msal-react
94.24% <ø> (-0.45%)
:arrow_down:

node-token-validation
?

*This pull request uses carry forward flags. Click here to find out more.

Files Changed
Coverage Δ

...ions/msal-node-extensions/src/utils/Environment.ts
20.51% <0.00%> (-22.08%)
:arrow_down:

...b/msal-browser/src/app/IPublicClientApplication.ts
36.66% <ø> (-7.09%)
:arrow_down:

...ib/msal-browser/src/app/PublicClientApplication.ts
65.90% <ø> (-29.42%)
:arrow_down:

...er/src/broker/nativeBroker/NativeMessageHandler.ts
86.29% <ø> (+0.33%)
:arrow_up:

lib/msal-browser/src/cache/AsyncMemoryStorage.ts
80.76% <ø> (+2.99%)
:arrow_up:

lib/msal-browser/src/cache/BrowserCacheManager.ts
89.47% <ø> (-2.25%)
:arrow_down:

lib/msal-browser/src/cache/BrowserStorage.ts
90.00% <ø> (-0.91%)
:arrow_down:

lib/msal-browser/src/cache/CryptoKeyStore.ts
80.00% <ø> (-3.34%)
:arrow_down:

lib/msal-browser/src/cache/DatabaseStorage.ts
34.00% <ø> (-4.54%)
:arrow_down:

lib/msal-browser/src/cache/MemoryStorage.ts
100.00% <ø> (ø)

... and 55 more

... and 177 files with indirect coverage changes


teach rohmu to notifiy when it writes anything [AD-756]

This allows robjecter to be informed everyime pghoard (rohmu) writes
anything. This can be controlled with the presence of extra config
passed to the constructors of each object storage driver.
The plain_key is needed as robjecter itself uses rohmu so the prefix
gets prefixed twice.
size is not strictly needed but helps make robjecter's work easier. And
here size is easily avaialble statically or dynamically (in case of
multipart-uploads). In case of multipart uploads the size could
calculated using the callback mechanisms locally however each driver
reports callback in a different manner and in some cases the callback
might not be called if a multipart upload was not necessary.
NOTE: this just replays aiven/pghoard/pull/548 here
AD-756

About this change - What it does

Resolves: #xxxxx
Why this way

(Assigned reviewers based on github's recommendations :-) )

Documenting the Slack discussion. The decision was to go with composition.
Inheritance
Extend the BaseTransfer class to include notification
Pros:

Has all the details about the upload available

Cons:

Code increases with the number of base implementations

Duplicated code, i.e. every subclass must reimplement the same logic
More error prone, i.e. forget to add it in a base class
More tests, i.e. because every subclass reimplements the same logic, they have to be tested separately

Mixes the concerns of notification with transfer

Proxy class
Write a proxy class to call notify.
Pros:

Single class implementing notify

no duplicated logic
fewer tests

Cons:

A näive implementation doesn't have all the data available, so additional calls are required. This includes OS system calls (cheap), and REST calls like store_file_object used for streaming uploads

Composition
Pass a notifier object to the base transfer
Pros:

Isolate the responsabilities
Allows the reuse of the data for streaming uploads

Cons:

Same cons as inheritance w.r.t. number of implementations

superseeded by https://github.com/aiven/rohmu/pull/67


Feature/acm integration

Issue #, if available:
Description of changes:
ACM integration
Prepared to migrate to aws-quickstart npm repo
Fixed a number of issues integrating with latest changes from the SSP quickstart.
Nginx blueprint with ACM integration works e2e (workload PR is coming)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@shapirov103 there is a CI check failing as well.

@shapirov103 there is a CI check failing as well.

Yeah, it is because I used the tar for the npm module since we have not published the quickstart yet.


Add LLBLGen Pro Info

Added Tools & Extensions section and info about LLBLGen Pro

@divega could you take a quick look over this

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

I maintain a blog post of EF Core extension libraries that are available on Nuget - would that be useful to add to the docs? http://erikej.blogspot.dk/2016/12/entity-framework-core-extensions.html

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@ErikEJ are you offering a PR to the new extensions section? 😄 Yes, I think it would be good to list them.

Sure, I will see if I can figure it out!


PackageConfig, JobConfig and Schema classes refactoring

As a result of the packit/packit#1543 epic our config is no more strictly associated with just one Package.
We should change its name from PackageConfig to something like RepoConfig and as a result a RepoConfig should have many PackageConfig(s).
At the moment a PackageConfig has many PackageConfigView(s) but we can obtain a RepoConfig with many PackageConfig(s) if we

[ ] change the config class name from PackageConfig to RepoConfig
[ ] and change the config class name from PackageConfigView to PackageConfig

The PackageConfig (later RepoConfig) can have multiple JobConfigView(s) one for every package interested by the job, probably a better name would be PackageJobConfig or something similar, and these should be initialized by the RepoConfig object itself.
Even schema classes names have to be improved: follow instructions given by packit/packit#1759

@majamassarini We've found an old related issue Can you please take a look at #1759 if there is something relevant so we can close it and preserve just one card. Thank you!

@majamassarini We've found an old related issue Can you please take a look at #1759 if there is something relevant so we can close it and preserve just one card. Thank you!

I have updated the description and linked the old card and I am going to closing it.

We discussed on today's standup that some refactoring here is still needed, as the code after the monorepo implementation has worse readability.


Configure it correctly with enzyme

Hi Guys,
I tried to use jest-puppeteer with enzyme tests but they fail with the next error: It looks like you called mount() without a global document being loaded.
So I have next questions:

Do I need to do something extra to run my tests in puppeteer with enzyme?
Do I need puppeteer at all? Does it replaces running tests via Karma in Chrome?

Thanks

Hi @deser, Puppeteer is just an API to control a Chrome Headless browser. You are at the place of the user, you can click, drag & drop, type with keyboard, etc... But as a user you are not able to run Enzyme, to do it you have to be in the page, in the JavaScript code of the website.
So the short answer is no, you can't use Puppeteer + Enzyme and it does not replace Karma. This library is designed for E2E testing.

Hey @deser , did you get any luck with the error? It happened the same to me, as soon as I add preset: 'jest-puppeteer', in my jest config, my tests with ezyme throw the same global document error...

using jest-pupeteer is a no-go for enzyme users then, bottom line ?


Tag Endpoints: max_tag_id failure (data still limited to 20 images)

The pagination section of the documentation has clearly specified the use of next_url parameter to get the next set of data.
My approach -
The next_url for GET /tags/tag-name/media/recent endpoint has a &max_tag_id= parameter to the URL. And, I believe max_tag_id = next_max_id or next_max_tag_id. Tried all combinations, I cannot get more than 20 images or 33 images if you use &count= parameter in the URL.
Here's what the pagination response is -

Question -
How can I get a more images ( greater than 33) for GET /tags/tag-name/media/recent endpoint?

So if you are paging through, the next time you run this method, how do you know the min_tag_id to start with (what is @tracker initialized with)?  I need to ensure the same image isn't received twice.   I was thinking  response.pagination would have a max_tag_id but it doesnt.

Yes, good point. As far as I know there is no way to set the starting min_tag_id to a reasonable value.
I use 0 for the first run and compare the instagram IDs I get with my own storage and ignore duplicates. Works ok for my use case.

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.


BUG: scipy.stats.vonmises_fisher.pdf() return probabilities >= 1

Describe your issue.
Hi,
When I used scipy.stats.vonmises_fisher.pdf() to calculate the probability P(X; mu, kappa) of some samples X from a certain von Mises-Fisher distribution parameterized with mu, kappa, I got probabilties values greater than 1, which is impossible from the definition.
Reproducing Code Example
import numpy as np
import scipy as sp
from scipy import stats

class RandomData:
    def __init__(self, rng, n_samples=300, n_components=3, n_features=2, scale=20):
        self.n_samples = n_samples
        self.n_components = n_components
        self.n_features = n_features

        # weights with shape=(n_components)
        self.weights = rng.rand(n_components)
        self.weights /= np.sum(self.weights)
        # mean direction with shape=(n_components, n_features)
        self.means = rng.rand(n_components, n_features)
        self.means /= np.linalg.norm(self.means, ord=2, axis=1, keepdims=True)
        # cencentration parameters with shape=(n_components)
        self.kappas = rng.rand(n_components) * scale

        self.X = []
        for _, (w, m, k) in enumerate(zip(self.weights, self.means, self.kappas)):
            vmf = stats.vonmises_fisher(m, k)
            self.X.append(vmf.rvs(int(np.round(w * n_samples)), random_state=rng))
        self.X = np.vstack(self.X)

        self.Y = np.hstack(
            [
                np.full(int(np.round(w * n_samples)), k, dtype=int)
                for k, w in enumerate(self.weights)
            ]
        )

    print(np.__version__)
    print(sp.__version__)

    rand_data = RandomData(np.random.RandomState(0))

    means = rand_data.means
    kappas = rand_data.kappas
    X = rand_data.X
    prob = stats.vonmises_fisher.pdf(X, means[0,:], kappas[0])
    print(prob[:5])
    print("Any values >1 in pdf:", np.any(prob>1))

Error message
[0.52220616 1.07532891 0.74081103 0.344824   0.62481833]
Any values >1 in pdf: True

SciPy/NumPy/Python version and system information
python=3.11
numpy=1.26.1
scipy=1.11.3

These are probabilitydensities, which can be greater than one. The PDF is the derivative of the CDF, which has a maximum value of 1.

Oh, my bad. Thanks for your explanation.


v2.3.2 High CPU/memory usage for big files

We are using excelize to write reports via the SetSheetRow interface. Which is working pretty well normally.
Today one of our processes is stuck while writing a report. I uses slowly more memory (2GB after 30m, 3GB after 1h) and uses one cpu fully. The report should have ~80k rows with 200 columns. Receiving the data from the database takes around 15s.
Looking at stack traces it is stuck at:
#	0x101412c	github.com/360EntSecGroup-Skylar/excelize/v2.glob..func1+0x4c				/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/styles.go:2042
#	0x1009c64	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).getStyleID+0x224			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/styles.go:2088
#	0x1009404	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).NewStyle+0xc4			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/styles.go:1992
#	0xfd5d14	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).setDefaultTimeStyle+0x114		/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/excelize.go:161
#	0xfae5c9	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).setCellTimeFunc+0x209		/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:150
#	0xfadc92	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).SetCellValue+0x652			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:92
#	0xfb1451	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).SetSheetRow+0x331			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:680

#	0x1009c04	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).getStyleID+0x1c4			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/styles.go:2088
#	0x1009404	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).NewStyle+0xc4			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/styles.go:1992
#	0xfd5d14	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).setDefaultTimeStyle+0x114		/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/excelize.go:161
#	0xfae5c9	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).setCellTimeFunc+0x209		/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:150
#	0xfadc92	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).SetCellValue+0x652			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:92
#	0xfb1451	github.com/360EntSecGroup-Skylar/excelize/v2.(*File).SetSheetRow+0x331			/home/vsts/go/pkg/mod/github.com/360!ent!sec!group-!skylar/excelize/v2@v2.3.2/cell.go:680

Profiling shows:

Steps to reproduce the issue:

Use File.SetSheetRow to write Data.
??
ss.CellXfs.Xf in styles.go:2087 seems to grow and is scanned for each time field completly.

Describe the results you received:
Very high resource usage and unexpected slow process
Describe the results you expected:
Data added to the File object
Output of go version:
go version go1.17.4 linux/amd64

Excelize version or commit ID:
github.com/360EntSecGroup-Skylar/excelize/v2 v2.3.2

Environment details (OS, Microsoft Excel™ version, physical, etc.):
The server is running on a recent ubuntu.

Updating to version 2.5.0 solves the issue.


Roll Flutter Engine from 1b567e80386e to<PHONE_NUMBER>95 (3 revisions)

https://github.com/flutter/engine/compare/1b567e80386e...967069056395
2024-11-08<EMAIL_ADDRESS>Roll Skia from d0ee80612f86 to 778b21720a61 (5 revisions) (flutter/engine#56457)
2024-11-08<EMAIL_ADDRESS>Manual roll Dart SDK from 50c620224f27 to cfa1826c3df1 (2 revisions) (flutter/engine#56456)
2024-11-08<EMAIL_ADDRESS>[Impeller] Switch to uniform arrays for gradient data on non-SSBO hardware (flutter/engine#56441)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Build Errors On FreeBSD

I would really like to try out Nfty but I'm solely a FreeBSD user on all servers. Getting build errors for Nfty on FreeBSD 13.1. Can you help or consider FreeBSD for your releases? You consider every other OS but not the BSDs.
$ pwd
/home/schrodinger/src/ntfy-2.4.0
$ make build
cd web && npm install
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.

added 1487 packages, and audited 1488 packages in 17s

245 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm notice
npm notice New patch version of npm available! 9.6.4 -> 9.6.5
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.5
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
cd web  && npm run build  && mv build/index.html build/app.html  && rm -rf ../server/site  && mv build ../server/site  && rm  ../server/site/config.js  ../server/site/asset-manifest.json

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  313.97 kB  build/static/js/main.80de9c45.js

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://cra.link/deployment

pip3 install -r requirements.txt
make: exec(pip3) failed (No such file or directory)
*** Error code 1

Stop.
make: stopped in /usr/home/schrodinger/src/ntfy-2.4.0

I tried the OpenBSD solution but it doesn't translate to FreeBSD. I tried to work around the python problem with a venv but I'm getting more problems related to dependencies. Unfortunately I'll consider ntfy incompatible with FreeBSD for now. Shame, I like your project. An alternative might be an Ubuntu jail (FreeBSD containers) but feels like overkill.
Just FYI the current errors:
Collecting six>=1.5 (from python-dateutil>=2.8.1->ghp-import>=1.0->mkdocs>=1.4.2->mkdocs-material->-r requirements.txt (line 2))
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Building wheels for collected packages: csscompressor, jsmin, regex, MarkupSafe, pyyaml, watchdog
  Building wheel for csscompressor (setup.py) ... done
  Created wheel for csscompressor: filename=csscompressor-0.9.5-py3-none-any.whl size=240333 sha256=982acb770d8f7377fe84221489a53350dd3e1721494abfffe373e2cb241c9c35
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/b9/97/af/2636f782de9bded12dfea15ea66cc77e01937e6b0916a3353c
  Building wheel for jsmin (setup.py) ... done
  Created wheel for jsmin: filename=jsmin-3.0.1-py3-none-any.whl size=13765 sha256=6e8503aee921da3f5930e60791f13c974cbbcc8a4229ae72f18fa3fef63eebc9
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/b1/2d/bd/fafa1f2a88e2f23e0e4eb50b0852a67268eed958096a02c03f
  Building wheel for regex (setup.py) ... done
  Created wheel for regex: filename=regex-2023.3.23-cp311-cp311-freebsd_13_1_release_p6_amd64.whl size=292711 sha256=d233a7b2f7306c9699ae5e4397b3e97343ab8f7368bf37e88b31a94348b2fd6c
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/99/ef/3a/307139e5aa4cf80c007432f70f22ecc0e5638082c5105a5fc6
  Building wheel for MarkupSafe (setup.py) ... done
  Created wheel for MarkupSafe: filename=MarkupSafe-2.1.2-cp311-cp311-freebsd_13_1_release_p6_amd64.whl size=15425 sha256=7c1ba91e80cd55adad97436874657e243db9fe47df5b88fdfa12a11467503100
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/01/81/5f/04fdc32056d8410469bd24a28bd60dfa5be60e0d12fd1bf8ea
  Building wheel for pyyaml (pyproject.toml) ... done
  Created wheel for pyyaml: filename=PyYAML-6.0-cp311-cp311-freebsd_13_1_release_p6_amd64.whl size=45344 sha256=e31b456d9d29741c71b48b60c72e2eb2cdc8fb4320ec83b1ed3212c6e78ebb17
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/3c/de/35/2cbb99955fa449eeddb2b433b4369035ee5bdf0fc121035ffe
  Building wheel for watchdog (setup.py) ... done
  Created wheel for watchdog: filename=watchdog-3.0.0-py3-none-any.whl size=82036 sha256=7150527fae069459983266dc420e1bdc90c2ad2cb716a122bfc12872e70521a0
  Stored in directory: /usr/home/schrodinger/.cache/pip/wheels/4d/58/44/2c9a2be09adb640c344be9970d37f88a4a78239b760bed8c55
Successfully built csscompressor jsmin regex MarkupSafe pyyaml watchdog
Installing collected packages: jsmin, htmlmin2, csscompressor, watchdog, urllib3, six, regex, pyyaml, pygments, mkdocs-material-extensions, mergedeep, MarkupSafe, markdown, idna, colorama, click, charset-normalizer, certifi, requests, pyyaml-env-tag, python-dateutil, pymdown-extensions, jinja2, ghp-import, mkdocs, mkdocs-simple-hooks, mkdocs-minify-plugin, mkdocs-material
Successfully installed MarkupSafe-2.1.2 certifi-2022.12.7 charset-normalizer-3.1.0 click-8.1.3 colorama-0.4.6 csscompressor-0.9.5 ghp-import-2.1.0 htmlmin2-0.1.13 idna-3.4 jinja2-3.1.2 jsmin-3.0.1 markdown-3.3.7 mergedeep-1.3.4 mkdocs-1.4.2 mkdocs-material-9.1.8 mkdocs-material-extensions-1.1.1 mkdocs-minify-plugin-0.6.4 mkdocs-simple-hooks-0.1.5 pygments-2.15.1 pymdown-extensions-9.11 python-dateutil-2.8.2 pyyaml-6.0 pyyaml-env-tag-0.1 regex-2023.3.23 requests-2.29.0 six-1.16.0 urllib3-1.26.15 watchdog-3.0.0
  File "<stdin>", line 1
    -e import sys\nif sys.version_info < (3,8):\n exit(1)
       ^^^^^^
SyntaxError: invalid syntax
/usr/local/bin/python3.8
python3.8  build
python3.8: can't open file 'build': [Errno 2] No such file or directory
*** Error code 2

Stop.
make: stopped in /usr/home/schrodinger/src/ntfy-2.4.0

You can go ahead and close the issue and thanks for getting back to me.

For what it's worth, I managed to compile 4c7dc4c1ba166c386894c4c199129d9959618319 yesterday using
goreleaser build --snapshot --clean --id ntfy_freebsd_amd64
After the following patch:
diff --git a/.goreleaser.yml b/.goreleaser.yml
index 131a302..911bbd7 100644
--- a/.goreleaser.yml
+++ b/.goreleaser.yml
@@ -3,6 +3,16 @@ before:
- go mod download
- go mod tidy
builds:

id: ntfy_freebsd_amd64
binary: ntfy
env:

 - CGO_ENABLED=1 # required for go-sqlite3

tags: [sqlite_omit_load_extension,osusergo,netgo]
ldflags:

 - "-linkmode=external -extldflags=-static -s -w -X main.version={{.Version}} -X main.commit={{.Commit}} -X main.date={{.Date}}"

goos: [freebsd]
goarch: [amd64]

id: ntfy_linux_amd64
binary: ntfy
diff --git a/Makefile b/Makefile
index 8cb7523..f72d764 100644
--- a/Makefile
+++ b/Makefile
@@ -111,7 +111,7 @@ build-deps-ubuntu:
docs: docs-deps docs-build

docs-build: .PHONY

  @if ! /bin/echo -e "import sys\nif sys.version_info < (3,8):\n exit(1)" | python3; then \

  @if ! /usr/bin/printf "import sys\nif sys.version_info < (3,8):\n exit(1)" | python3; then \
    if which python3.8; then \
          echo "python3.8 $(shell which mkdocs) build"; \
      python3.8 $(shell which mkdocs) build; \

I'll clean this up and submit a pull request when I have time, but hopefully this is enough to get you going.


Dependency Conflict with @mendable/firecrawl-js During Flowise Deployment to SAP BTP Cloud Foundry

We are currently working on deploying the Flowise AI application to SAP BTP Cloud Foundry and are facing an issue during the deployment process. I’m hoping someone here can help with insights or solutions.

Use Case: We are trying to deploy the Flowise AI application to BTP Cloud Foundry.

Source Code: The source code for Flowise AI is available on our GitHub repository:        https://github.com/FlowiseAI/Flowise.git

Local Setup:
Locally, the application builds and runs fine using the following environment:
Node.js version:  18.20.3, 18.20.4, 20.15.1, 20.16.0, 22.7.0, 22.8.0
npm version: 10.7.0
We are able to build the application locally using the following command:
commands:
- "npm install -g pnpm"
- "pnpm install"
- "pnpm run build"

Deployment to BTP Cloud Foundry:
We now aim to deploy this application to the BTP Cloud Foundry environment. For this, we created a deployment     descriptor (mta.yaml), which looks like this:
_schema-version: "3.1"
ID: flowise
version: 0.0.1
description: Flowise HTML5 Application
parameters:
keep-existing-routes: true
modules:

name: flowise
type: html5
path: Flowise
parameters:
disk-quota: 1024M
memory: 1024M
buildpack: nodejs_buildpack
stack: cflinuxfs4
instances: 1
build-parameters:
builder: custom
commands:
- "npm install -g pnpm"
- "pnpm install"
- "pnpm run build"

The .mtar file is being successfully built with the above mta.yaml file, but when we attempt to deploy the .mtar to BTP Cloud Foundry, the app staging fails with the error: BuildPackCompileFailed
Error Details:
The root cause of the failure appears to be a dependency issue. Here is a snippet of the error captured during the deployment process:
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@mendable/firecrawl-js
npm ERR!   packages/components
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/flowise-components
npm ERR!       workspace packages/components from the root project
npm ERR!   peerOptional @mendable/firecrawl-js@"*" from<EMAIL_ADDRESS>npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Troubleshooting Steps Tried
Ensured all packages were installed locally without issues using pnpm.
Attempted deploying with:
npm install --legacy-peer-deps
npm install --force
However, the error persists.
Verified the compatibility of Node.js and npm versions across local and deployment environments and checked the compatible versions available in SAP BTP cloudfoundary NodejsBuildpack and version.
Could anyone provide some pointers or steps to resolve this issue effectively? Any suggestions or insights would be greatly appreciated!

Hi Team, Any update on this?


UI report statistics - differentiate between NAT and access rules

currently all rules are counted which might cause a raised eyebrow when comparint 1482 rules in statistics report just with the 756 rules in the (standard) access rule report

consolidate into #600


Proper error message not given for a type init expr with invalid no. of args

Consider the following example:
type Person object {
    string name = "";
    int age = 0;
};

public function main() {
    Person p = new("John Doe", 20);
}

Running the above results in the following compile error on both 1.2.4 and master
error: .::test2.bal:7:16: too many arguments in call to 'null()'

This should,

not say null() in the error message
probably give an error message more suited for the type init expr

Reproducible on sl-alpha for
class Person {
    string name = "";
    int age = 0;
}

public function main() {
    Person p = new("John Doe", 20);
}

Reproducible on sl-alpha for
class Person {
    string name = "";
    int age = 0;
}

public function main() {
    Person p = new("John Doe", 20);
}


Getting spotDL's core requirements simplified

[x] Definition of major interfaces
[x] Spotify wrappers (for song search, metadata and the likes)
[ ] YouTube Song matching (getting a downloadable link for a song from YouTube)
[ ] Download, format conversion and metadata embed wrappers

@rocketinventor has agreed to work on YouTube song matching using YouTube Music.


Fix the permission for the public ecr

Description
Fix the ECR Permission policy for the public ECR repo.
Motivation and Context

Current permission policy created for public ecr repo are wrong.

Breaking Changes

No breaking changes
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This is merged in upstream https://github.com/terraform-aws-modules/terraform-aws-ecr/pull/7


two types of tokenizer?

Hi, dear author, i noticed you used two different type of tokenizer in your implementation:

BERT tokenizer

    def init_bert(self, vision_width, cross_attention_freq=2, truncation_side="right"):

        # tokenizer = BertTokenizer.from_pretrained("bert-base-uncased", truncation_side=truncation_side)
        print("loading bert-base-uncased tokenizer.")
        tokenizer = BertTokenizer.from_pretrained("pretrained/bert-base-uncased", local_files_only=True)

Vicunna tokenizer

    if 'mpt' in model_args.model_name_or_path:
        tokenizer = transformers.AutoTokenizer.from_pretrained(
            model_args.model_name_or_path,
            cache_dir=training_args.cache_dir,
            model_max_length=training_args.model_max_length,
            padding_side="right"
        )
    else: # vicunna tokenizer
        tokenizer = transformers.AutoTokenizer.from_pretrained(
            model_args.model_name_or_path,
            cache_dir=training_args.cache_dir,
            model_max_length=training_args.model_max_length,
            padding_side="right",
            use_fast=False,
        )

I wonder why use two different tokenizer for single work. is the two actually the same one? thank you .

Hi. BERT tokenizer is used to get text input for QFormer to generate context tokens, and Vicunna tokenizer is used to generate tokens for LLM input.

Hi. BERT tokenizer is used to get text input for QFormer to generate context tokens, and Vicunna tokenizer is used to generate tokens for LLM input.

Yes. But why not use same tokenizer for both?

QFormer is based on BERT, it can understand BERT tokenizer only.


plugins/base: Detect HTTP errors in myip()

Out of the box, curl reports success (via exit code) even if the
server returns an error, e.g. 429 Too Many Requests which was
sometimes the case with http://myip.dnsomatic.com. So, errors went
undetected.
There is the --fail switch which enables us to use the exit code the
way we need:

-f, --fail
(HTTP) Fail  silently  (no  output  at  all)  on  server
errors. This is mostly done to better enable scripts etc
to better deal with failed  attempts.  In  normal  cases
when  an  HTTP  server  fails  to deliver a document, it
returns an HTML document stating so  (which  often  also
describes  why  and  more).  This flag will prevent curl
from outputting that and return error 22.

Use it to make the myip() deliver results reliably.

@nwinkler looks like we have issues with Travis-CI here: https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798
I recently enabled Travis-CI for my fork and it seems this has some impact on the PRs here. I'm afraid only you can help here by migrating from Legacy integration to GitHub Apps in regard to Travis, as mentioned in that thread.

I will have to take a look at this later, sorry - don't really have time today.

FWIW you can see the PR builds here: https://travis-ci.org/github/Bash-it/bash-it/pull_requests
Looking into migrating this over to GitHub Apps now.

Migrated the Travis builds over as documented - I've retriggered the build for this PR - it should show up here now...

Merged - thanks for hanging in there!


add hooks to Migrate

add hooks to Migrate to allow filtering and mutation of the tables being created.
as per https://github.com/facebook/ent/issues/1079 this will make it possible to change or remove tables before they're created for any custom modifications needed.
	migrate, err := schema.NewMigrate(sql.OpenDB("mysql", db), schema.Hook(func(next CreateFunc) CreateFunc {
		return func(ctx context.Context, tables ...*Table) error {
			return next(ctx, tables[0], &Table{Name: "pets"})
		}
	}))

Wow! Thanks for adding this @rubensayshi. Minor style comment, please use the same patterns/naming uses in ent.Hook and entc/gen.Hook.

Wow! Thanks for adding this @rubensayshi. Minor style comment, please use the same patterns/naming uses in ent.Hook and entc/gen.Hook.

yea, you're absolutely right, made it in the same style now.

yea, you're absolutely right, made it in the same style now.


Making Default Headers configurable

I was trying to upgrade to this latest version, but the fact that the source code is now in an external npm repo restricts the configuration by using the AppConfig class.
Unfortunately, I have little knowledge of JS and React, but it seems that there is only a subset that can be configured. This works on my project:
module.exports.setupGraphiQLWorkspace = function (bootstrapOptions = {
    defaultUrl: 'https://graphql.up.welt.de/graphql',
    defaultQuery: '{ search( section: "/wissenschaft/" ) {\n    headline\n  }\n}',
}) {this.bootstrapOptions = bootstrapOptions;
    const config = new AppConfig("graphiql", bootstrapOptions);
    ReactDOM.render(<GraphiQLWorkspace config={config}/>, document.getElementById('graphiql-workspace'));
};

How would I modify the defaultHeaders? I need to replace the default Authorization header with an X-Api-Key header.

Indeed only a small subset of properties are customizable:
https://github.com/OlegIlyenko/graphiql-workspace/blob/5b5b88e6eb6079c2c313b3e7862cb454480a823f/src/config.js#L79-L83
If you would like to customize more things, I would appreciate if you can make a PR and add more AppConfig options (at least for default headers). Would be happy to merge it :)


Wrong Batch Comment

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
<IP_ADDRESS>-RC1
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-Proxy
Expected behavior
start.bat
Batch Comment @rem or rem
Actual behavior
shell comment #
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).

Thanks for your issue.💖


docs: fix tutorials list

I was needed to check notifications first :facepalm:
#506
Should we remove a tutorial file?


how to refactor code

create an array with numbers of the data you will be using ex: oldarray = [1, 9, 17, 25 ,33]
create for loop
inside for loop:
create variable to get value of one number in the array
ex: newarray = oldarray[i]
replace number 1 with newarray
still inside loop:
for the 5-day results only:

create a div with class = col-lg-3 col-md-5 col-sm-12 me-4 weathers
create div for weather icon with class "weather-icon" and put an img element with class "icon" inside "weather-icon" div / append img to "weather-icon div
create an unordelist with p elements
append "weather-icon" div to div class "col-lg-3 col-md-5 col-sm-12 me-4 weathers"
append unordered list to to div class "col-lg-3 col-md-5 col-sm-12 me-4 weathers"

append "col-lg-3 col-md-5 col-sm-12 me-4 weathers" to div class="row allweathers"

completed 12/7/22


automated benchmark tool

Benchmark requirements / matrix

Each run needs to be run 5 times

we take the mean as the result
wa calculate stddev to make sure there are no environmental issues

Workload: inserts, mixed
Tasks: 1M 10M 100M
Contenders: Rust, Gocql, This

workers: 1K, 2K, 4K, 8K

Contenders: This in async mode

workers: nr CPUs * 2^i for i=0-4
batch size: 256*2^i for i=0-4

Closed as of #241


Tool to diagnose the parallelizability of a dask graph

I have a nice computational graph with lots of mostly-numeric functions.  However I'm only getting 200-300% CPU usage on a twelve core machine.  I'd like to track down which of my functions parallelize well and which don't.  I'd also like to test the purity of these functions, ensuring that they produce the same results on each execution.  What I need is a set of valid inputs for each of these functions and then to test them in some sort of testbed.  Fortunately the dask graph gives us exactly this set of inputs.
I propose a sequential pass through the task graph where, at every task, we redundantly execute the function both sequentially and in parallel with a thread pool.  We record the speedup and verify purity.  We then pass along the arguments for the next task.
This would be a diagnostic on a graph.  The output would be a report on which functions parallelize well and are pure and which functions need work.
This may interest @eriknw and @jcrist

Hrm, this could probably just be done with the synchronous scheduler and a callback.

I'm surprised you need to verify which functions are pure. That part is usually pretty obvious (at least it should be!). I also doubt it can be diagnosed reliability, especially for functions with side effects like writing to disk.
I agree that it would be useful to diagnose the parallelizability of tasks. The diagnostic might also try running tasks in a process pool for the sake of comparison, which could couple well with #457.

I'm surprised you need to verify which functions are pure.

I'm working with a large-ish foreign codebase.  It's much easier wrap things with do than to investigate each function.

I'm currently getting by with just a decorator
from time import time
from multiprocessing.pool import ThreadPool

nthreads = 4
njobs = 12
pool = ThreadPool(nthreads)

def benchmarkme(func):
    def bench_func(*args, **kwargs):
        seq_start = time()
        result = func(*args, **kwargs)
        seq_end = time()

        if seq_end - seq_start < 0.1:
            return result

        def g(_):
            return func(*args, **kwargs)

        par_start = time()
        results = pool.map(g, [0] * njobs)
        par_end = time()

        ratio = njobs * (seq_end - seq_start) / (par_end - par_start)
        pure = all(str(result) == str(r) for r in results)

        print("Func: %s  Ratio: %f  Pure:  %s  Time: %f" %
                (func.__name__, ratio, pure, seq_end - seq_start))

        return result
    return bench_func

Closing as speculative


Bump minimist from 1.2.2 to 1.2.3 in /images/chaos-dashboard

CVE-2020-7598
high severity
Vulnerable versions: < 0.2.1
Patched version: 0.2.1
minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.

Thanks for taking care of the security problem of Chaos-mesh 😄
However, we are refactoring chaos dashboard recently. And in this pr https://github.com/pingcap/chaos-mesh/pull/419, the current chaos-dashboard component will be removed. So maybe we can close this ticket? WDYT?


[DRAFT] add working directory parameter

Allows setting the working directory from workflow yaml files.
Description
With this change, the working directory can be set in a workflow step like:
    steps:
      - name: Build
        env:
          AIO_RUNTIME_NAMESPACE: ${{ secrets.AIO_RUNTIME_NAMESPACE_PROD }}
        uses<EMAIL_ADDRESS>        with:
         working-directory: './tools'
          os: ${{ matrix.os }}
          command: build

This is useful for projects that are not primarily aio apps, so would prefer to have aio files in a sub-directory, but still want to benefit from github actions.
How Has This Been Tested?
In progress, will move from draft to open PR once completed.
Types of changes

[ ] 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 change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Testing is blocked by https://github.com/adobe/aio-apps-action/issues/28


autoload.php

hello, you have autoload.php in your sample test , but there is not autoload.php in your src
thank you

The autoload.php is generated by Composer automatically.
To use all of examples mentioned on README, it should use composer require zhuravel/php-iso-3166-1 to install this PHP package firstly.
And the vendor/ folder will be generated during above composer command running.


Improved Regex syntax highlighting

Improves semantic highlighting of regex by utilizing Roslyn data that was previously unused.
This "breaks" themes that only style the regexp token because new specialized token types were added.

Could you add some screenshots to demonstrate what this looks like?

Here are some examples within VSCode with default colors from Visual Studio 2019.
VSCode Light:

VS2022 Light:

VSCode Dark:

VS2022 Dark:

@TechnologicalPizza Thanks so much for adding these tokens. I think we are missing two things to make this complete.

For the other token types, we maintain entries in the package.json where we map each token type to a textmate scope to aid in theming.

https://github.com/OmniSharp/omnisharp-vscode/blob/675319476db5713da3e45f6879b0eda44b1863a5/package.json#L3664-L3739

We also ship semantic enabled Visual Studio 2019 themes that could be updated to better match the VS 2019/2022 regex colors. (see https://github.com/OmniSharp/omnisharp-vscode/tree/master/themes)

If you feel up to working on these two tasks, please let me know. Otherwise, I am happy to take this PR as is.

Seems like something interesting I could look at :eyes:
I'm not really sure what name should go where but I'll investigate a bit first.

I'm not really sure what name should go where but I'll investigate a bit first.

Some are already defined in the themes. Others will have to be a best guess unless you find something definitive.
https://github.com/OmniSharp/omnisharp-vscode/blob/master/themes/vs2019_light.json#L543-L583

With commit cba7893 these are the default colors that were already in vs2019_dark.json🥳

@TechnologicalPizza Sorry I haven't followed up. Were there any required changes to the Light theme?

@JoeRobich I don't think so? The images I uploaded were made with stock themes. This PR doesn't change any themes either.
I couldn't really figure out why the Light theme was brighter though. It seemed to use the same color definitions as the Dark theme but it was somehow brightened by VSCode, unless I missed some specific regex stuff in some light theme somewhere.

Thanks @TechnologicalPizza !


Add endpoint option to Builder

https://github.com/jrochkind/faster_s3_url/issues/9
Currently the Builder's initializer accepts a host param which assumes https. I like to use minio for local development and it isn't ideal to run it with https.
The normal Aws::S3::Client gem accepts an :endpoint option to by-pass this issue.
Here is a section of the docs that explains this option:
:endpoint (String, URI::HTTPS, URI::HTTP) — Normally you should not configure the :endpoint option directly. This is normally constructed from the :region option. Configuring :endpoint is normally reserved for connecting to test or custom endpoints. The endpoint should be a URI formatted like:
'http://example.com'
'https://example.com'
'http://example.com:123'

https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/S3/Client.html

Thank you for this! I'm sorry I've been very busy in other areas last week and this, but this is on my radar. I will try to look at it today, if not, know that I haven't forgotten you, but if you don't hear from me for a bit, please feel free to ping again on this issue!

OK, so host -- you are right that when I implemented/documented it I hadn't totally thought it ought and it didn't quite work in that way.
But I have ended up using it for when you have a CloudFront distribution (or any other CDN) on top of S3. For public unsigned urls, you just need to change the hostname to be your CDN hostname.  And this is a convenient tool to do it, in a speedy way (much speedier than AWS SDK), applying appropriate (a bit idiosyncratic) S3 escaping rules for keys, etc.
So I think we do need to keep the host argument there, working as it did -- at least for unsigned URLs. Perhaps host and endpoint are mutually exclusive, and if you specify both you get an ArgumentException? Or we just doc which takes priority.

OK thanks for this!
Splitting it out into a separate class is nice and readable code organization wise. (I'd probably call the class BaseURI instead of just URI).
BUT.  The whole point of this thing is performance. We need to make sure splitting it into a different class, or these changes in general, don't harm performance significanty -- especially in cases where this new feature is NOT being used.
Would you be interested in trying to run the in-repo benchmarking stuff against this new one -- maybe find a way to run the old unchanged code against the new code -- to see how it effects performance?
Thank you!

Also add a CHANGELOG.md entry in PR please, with a URL to this PR!

Thanks for getting back to me! I can get back to this early next week.
It sounds like I have the following TODOs:

[ ] Run the performance specs before and after this change.
[ ] Update the CHANGELOG.md with a link to this PR.
[ ] Rename the new class from URI to BaseURI. (Assuming performance is good with this class).

I am still a little confusing about the host feature. Does that mean when you use it you do specify the bucket name in the host string you provide? If so that makes a lot of sense, and I could update the specs to match that pattern.

Is the difference between endpoint and host just that endpoint allows you to include a port too? I am having trouble understanding what's up here -- can you give me illustrative examples of what you would pass in as endpoint and where you would get it?

Hey if I understand what endpoint is doing, I think this could and shoudl actually be a lot simpler.
Endpoint is just to allow you to specify http instead of https, and a port in addition to a host?
This code can be much simpler.  If Endpoint is specified, just use the string given to construct the url, no?
Places in the code that have "https://" + self.host + path just need to be changed to have logic like:
if self.endpoint
     self.endpoint + path
else
    "https://" + self.host + path
 end

Even better, if on initialization a host is given and not an endpoint, just SET the endpoint to "https://#{host}", and then all subsequent logic can just be in terms of endpoint -- host is just a shortcut for setting endpoint that assumes https and no port.
I think this can just be a few lines of change, and doesn't need a separate class, or instantiating a stdlib URI object -- things I was worried about their effects on performance.
My use of host.  I have an S3 Bucket.  So something in the S3 bucket might be at the public URL "https://#my-bucket.s3.amazonaws.com/somepath/something.jpg".  No signature, it's a public URL.
But i have an AWS Cloudfront CDN in front of it, so to access it through AWS Cloudfront I actually need to access it at https://d987adfa07df.cloudfront.net/somepath/something.jpg, so I set host to d987adfa07df.cloudfront.net.

I started down that expect path, and I ran into 2 problems.

When endpoint it an IP address AWS has to form the path differently by adding the bucket. Which I try and point in this spec. I might be able to make that spec clearer by adding a starts_with assertion. So the path changes as well as the host/endpoint.
The canonical_headers needs to not include the http or https. So when I have an endpoint param I need to be able to strip the scheme off of it.

Both the path and the canonical_headers are in the string_to_sign so it is important that those variables are exactly correct for the signature. So it makes it all it little more complicated than just changing the resulting url.
I do think you have a great idea about using the host to set an endpoint, which might simplify the logic! I didn't fully understand that host variable before, I can look into this next week. Thanks!

Ah, i see what you mean about additional requirements. Hm, how about this @BenKanouse:
Right now it looks like the only specs you added are to your new URI object?
Can you add some actual public API tests -- write tests where you test all the pertinent different kinds of "endpoint" params (numeric IP, http vs https), and tests that the output is correct in all the ways you mention -- the canonical headers for correct signature (you could compare the signature against what the AWS-SDK does to make sure it is right, I think some existing tests may do that?), the extra path info for numeric IP etc.
Write enough specs that if the specs pass, then we're good, regardless of inside implementation. Write specs for the behavior required, not the internal implementation. Presumably your current implementation would pass!
Then, I think I'll have some time this week to take a stab at writing the simplest possible implementation that passes your specs. Like explain to me everything it needs to do that you know about by writing the specs that will test it, and I'll see what i can do.
Make sense?  Interested?

I did try to add those specs here and here in the builder_spec.rb file in my first commit.
My hope was that file is testing the public API, so I added those specs in the first commit before any of my refactors in the second.
It sounds like we discovered some more edge cases that I should add. 👍🏻

OK even if we had the embedded URI file, I would want those specs at the top level documenting the public API, right!
Can you add them, along with all the edge cases you can think of, such that if the tests pass, as far as you know the thing will be good?
I don't want to make you do a lot of other work spinning your wheels; if you can do this, I can try my idea for the simplest possible implementation that would pass specs!

Today I did the following:

Added extra specs to builder_spec.rb
Ran the performance tasks on version 1.1 and my branch and posted the results to the description of this PR.
Added to the Changelog.

I wasn't able to do endpoint to "https://#{host}" because the specs would start failing. It turns out that host dose not act like AWS's endpoint param. I made a spec here showing that they are not equal:
https://github.com/jrochkind/faster_s3_url/pull/10/files#diff-55397705043290c57d8e318e16f642ff8250ababeaac2526eb5da8da66b0aee4R80
The host param wants to make a url like this:
"https://my.example.com/some/directory/file.jpg"

While AWS's endpoint param makes a url like this:
"https://my-bucket.s3.amazonaws.com/some/directory/file.jpg"

While still much faster than AWS the performance did drop some after adding this feature.
I'm starting to think that maybe this project shouldn't support this feature. It feels like the point of this project is to create quick make URLs and if we add all the AWSs features we might end up with complex code that gets slowed down. For instance I needed to parse this logic in order to understand how AWS deals with endpoints: https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-s3/lib/aws-sdk-s3/endpoint_provider.rb#L30 Which makes me think there are more edge-cases out there.

Hey @BenKanouse !
I have been pretty busy with other stuff recently!  I see what you mean.
Yes, the host param is completely separate, my further suggestion may have been infeasible, just ignore current host entirely for now I think!
If you think you can capture the top-level  public API interacton specs fully, such that an I am happy to spend some time doing the implementation to match the specs. But if you don't think it seems feasible for you to do this, then that would be a signal that it's not feasible to implement right now.
I don't entirely understand what is going on myself though, I haven't had time to look more in depth into it!

That sounds correct to me!
I do have those specs in the spec/builder_spec.rb file on this branch.

You think the specs in there now are sufficient to spec correct behavior? They include the header stuff you mentioned and anything else required?  If so, I'll take a look!

OK, I'm sorry, I'm still getting confused. Why do you have a spec that says does NOT match the AWS logic for the endpoint param, why is the correct desired behavior to not match AWS logic in this case?
I haven't looked at this code in a while and at this point you probably have a fresher understanding of than me. Can you do me a favor and make it easier for me, can you help me identify exactly what specs we are talking about that specify the desired behavior at the top-level API? And then I would love to take a stab at writing an implementation to meet them.

OK wait sorry should have rubber-ducked it, I think I figured it out thanks!

The ones that are NOT match are for the existing host behavior. Those specs might be pointing out that we are doing something with host that AWS's gem can't do.
The new behavior specs are under the endpoint sections.

Closed for #14


extension Suggest

Layout, is a declarative layout library. You can set the layout in the xml file. Write like android. TangramKit this library I first saw very cordial (there are a lot of layout and the layout of the android like), and then I was thinking, the author can TangramKit and layout together, and then really can be written android layout as Write ios layout.

@geGao123 I'm not sure exactly what is being suggested here?


Fix the compilation error

Try cargo run --verbose after copying the code into a separate project. This example snippet does not compile and requires serde create to be present in the main.rs. So including the serde crate will fix the compilation error.
fixes #ISSUE_ID
:tada: Hi and welcome! Please read the text below and remove it - Thank you! :tada:
No worries if anything in these lists is unclear. Just submit the PR and ask away! :+1:

Things to check before submitting a PR

[x] the tests are passing locally with cargo test
[ ] cookbook renders correctly in mdbook serve -o
[ ] commits are squashed into one and rebased to latest master
[ ] PR contains correct "fixes #ISSUE_ID" clause to autoclose the issue on PR merge

if issue does not exist consider creating it or remove the clause

[ ] spell check runs without errors ./ci/spellchecker.sh
[ ] link check runs without errors link-checker ./book
[ ] non rendered items are in sorted order (links, reference, identifiers, Cargo.toml)
[ ] links to docs.rs have wildcard version https://docs.rs/tar/*/tar/struct.Entry.html
[ ] example has standard error handling
[ ] code identifiers in description are in hyperlinked backticks

[`Entry::unpack`]: https://docs.rs/tar/*/tar/struct.Entry.html#method.unpack

Things to do after submitting PR

[ ] check if CI is happy with your PR

Thank you for reading, you may now delete this text! Thank you! :smile:

Hey thanks good catch.  Appreciate you letting us know.


pypi shows old package version number

Hi all, I'm author/maintainer of the package pylmnn. I updated my package and uploaded the new versions to pypi. When I search for the package on pypi.org, I see an old release number next to the package name (1.5.2), but after clicking I can see the new versions. Same with pip, when I search, I see the old version number, but when I install, the latest version is installed. This also results in this confusing message from pip:
PyLMNN (1.5.2)  - Large Margin Nearest Neighbor implementation in python
INSTALLED: 1.6.2
LATEST:    1.5.2

Seems to be fixed now for my package.

Closing as it seems to be fixed.


usr_mcu_version.cpp: Implement usr_mcu_version

Apart from the funny comment typos, looks good to me! I started wondering whether it is needed to add separate messages for guid and and hw_info or would those have fit logically into some existing messages. But if you feel that it is logically nicer to have separate messages (or there just isn't any suitable ones), it is fine!

Apart from the funny comment typos, looks good to me! I started wondering whether it is needed to add separate messages for guid and and hw_info or would those have fit logically into some existing messages. But if you feel that it is logically nicer to have separate messages (or there just isn't any suitable ones), it is fine!

I could not find any candidate messages to append these to, also, I think it is cleaner to have separate messages for separate things rather than trying to put unrelated (or even vaguely related) things together. I assume the messages / message types / identifiers / whatever are not some kind of precious resource ?


When PySDL2 is not installed, error about package "sdl2" appears confusing

The cross-platform solution is to run:
pip3 install pysdl2

But the message that's printed does not clearly describe this is how to resolve the issue.
https://github.com/Driftwood2D/Driftwood/blob/5ed4b90d42a165a72bb6885b2404f151537e4a26/src/__main__.py#L52

Alright, I can add extra messages for import failures.


fix: Bring back DefaultVerify

Jump Start Solutions (JSS) use Blueprints/Terraform in the following way:

terraform apply ... - to deploy the JSS
terraform destroy ... - to delete the JSS deployment

We haven't had a need to test that a second terraform apply ... would work.
But now, with MiM, users will need to run terraform apply a second time.
So I'm bringing back the DefaultVerify test.

Failures seen in integration tests:
# module.simple.module.filestore.google_filestore_instance.xwiki must be replaced
resource "google_filestore_instance" "xwiki" {
...
    ~ networks {
...
        ~ network           = "xwiki-gce" -> "projects/ci-migrate-gce-a471/global/networks/projects/ci-migrate-gce-a471/global/networks/xwiki-gce" # forces replacement
...
# module.simple.module.vm.module.instance_template.google_compute_instance_template.tpl must be replaced
resource "google_compute_instance_template" "tpl" {
    ...
    ~ metadata_startup_script = (sensitive value) # forces replacement


Apply MD5 impmplementation with public-domain version to branch 1.6.x?

Should we apply the commit 9b9a310118a9523c72db939939a326dd9e60fa4b to branch-1.6.x and so move the entry in ChangeLog from 1.8.1 to 1.6.22?

Yes, seems fair.

OK done by 3d16c35d37fd649a498eb57a573bda0b7d7b1e5f and 438c80db99749d51a216a3b6c9ed244b74614ce4


Update build pack to v1.6.11

Issue number: N/A
Description of change
Updates the build pack to v1.6.11. I've done a test deployment to UAT.
Changes: https://github.com/cloudfoundry/python-buildpack/releases
Checklist

[x] Have any relevant search models been updated?
[x] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[x] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[x] Has the admin site been updated (for new models, fields etc.)?
[x] Has the README been updated (if needed)?

Codecov Report

Merging #878 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #878   +/-   ##
========================================
  Coverage    96.68%   96.68%
========================================
  Files          162      162
  Lines         4773     4773
  Branches       460      460
========================================
  Hits          4615     4615
  Misses          98       98
  Partials        60       60

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 c145036...f639f82. Read the comment docs.


Forbid unsafe

Pending a benchmark, this removes the last unsafe blocks. Those were cause by borrowing checking that only the next generation could fix. Instead, we internally return an owned descriptor and borrow only where necessary.

sad noises
[Benchmark]              	[Change] 	[Base]  	[Head]  	[Significance]
gif/note.gif/727554      	regressed	9.598513	9.728900	0.050000
gif/photo.gif/10130100   	regressed	111.857520	113.430000	0.050000
gif/sample_1.gif/69      	regressed	1.459887	1.484500	0.050000
gif/sample_big.gif/751774	improved 	345.864613	338.790000	0.050000
gif/extract-metadata-note	regressed	362.200198	445.730000	0.050000

sad noises
[Benchmark]              	[Change] 	[Base]  	[Head]  	[Significance]
gif/note.gif/727554      	regressed	9.598513	9.728900	0.050000
gif/photo.gif/10130100   	regressed	111.857520	113.430000	0.050000
gif/sample_1.gif/69      	regressed	1.459887	1.484500	0.050000
gif/sample_big.gif/751774	improved 	345.864613	338.790000	0.050000
gif/extract-metadata-note	regressed	362.200198	445.730000	0.050000

Unless we find some really cute way to express this, I guess we just wait on the next version of the borrow checker or on a general rework of the decoder. Although the performance changes aren't too crazy the unsafe code has been vetted by a few people now and the new code is more complicated.

Unless we find some really cute way to express this, I guess we just wait on the next version of the borrow checker or on a general rework of the decoder. Although the performance changes aren't too crazy the unsafe code has been vetted by a few people now and the new code is more complicated.


chore: update next-spec branch with latest changes from master

/rtm

Recent comments about the release from the bot were added by mistake. More details in https://github.com/asyncapi/spec/issues/899


packaged-as-an-iexpress-installer

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your rule idea isn't already filed: search

Summary
It'd be cool to have a rule that detects EXEs created with iexpress.exe
Examples
52e25bdd600695cfed0d4ee3aca4f121bfebf0de889593e6ba06282845cf39ea
Features
Is it possible to match on the EXE manifest with capa?
<!-- Copyright (c) Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

  <assemblyIdentity version="<IP_ADDRESS>"
     processorArchitecture="amd64"
     name="wextract"
     type="win32"/>

  <description>IExpress extraction tool</description>
...

Otherwise, matching on the two strings shown below in the same function scope should be a good indicator:

From: https://analyze.intezer.com/analyses/6e1d2029-a4ac-477a-8187-03670732b745/families/0a29c6e3-2b86-4e82-b034-57a08b011ad6
Additional context
N/A
Rule details
Namespace
executable/installer/iexpress
References
https://en.wikipedia.org/wiki/IExpress
Other rule meta information
T1207 - Obfuscated Files or Information

Nice, we can match on the manifest strings and the other (w)extract related strings.

@recvfrom  you've had some great rules in the past, and we really appreciate the documentation you put together in these issues! please also feel free to directly open PRs (if you want to draft the rules, too). minor benefit is that there'd be less latency in you waiting for us to say "good idea go ahead!"

@williballenthin thank you! I recently discovered that my work wants us to track work-related contributions to open source projects through a new system they created, and I haven't had a chance to figure out what the full process for that is.  I figured I'd open tickets in the meantime, though, so I don't move on to other things and forget about it. I do plan to circle back to these at some point, though, unless someone else gets to it first.

that process sounds familiar to me ;-)
please let me know if there's anything we can do to ease the project and ensure you can continue contributing here!


Think about ways to define items and recipes as an asset

We should have a textual format to define items and recipes which can be loaded as an asset.
This would enable us to iterate on the concrete numbers in a faster way.
For example, each recipe should define the input items and their counts, the time to craft the recipe, the structure to craft the recipe in and the number of output items.
For the items and structures it's probably enough to define a unique identifier (to use in the recipes) and maybe the textures/models needed to render them ingame

Closing as duplicate of #338 which is more actionable.

I think #368 is the replacement issue here

Oops, absolutely. Triage on mobile is hard.


Update code to improve code quality

Also fixed bug where description sorting is not case sensitive. This contradicts the UG that says sorting is case sensitive. This is thus a bug that must be fixed.
Made code match UG description.
Fixes #264

Codecov Report

Merging #265 (909ea28) into master (33b22e9) will increase coverage by 0.07%.
The diff coverage is 59.25%.

@@             Coverage Diff              @@
##             master     #265      +/-   ##
============================================
+ Coverage     70.48%   70.56%   +0.07%
- Complexity      885      894       +9
============================================
  Files           127      127
  Lines          2704     2714      +10
  Branches        352      349       -3
============================================
+ Hits           1906     1915       +9
- Misses          607      608       +1
  Partials        191      191

Impacted Files
Coverage Δ

...mands/tasks/TaskSortAddedChronologicalCommand.java
100.00% <ø> (ø)

src/main/java/taskbook/model/Model.java
100.00% <ø> (ø)

src/main/java/taskbook/model/ModelManager.java
94.44% <0.00%> (-1.07%)
:arrow_down:

src/main/java/taskbook/ui/TaskListCard.java
0.00% <0.00%> (ø)

...taskbook/logic/commands/tasks/TaskFindCommand.java
72.22% <58.33%> (+2.52%)
:arrow_up:

...book/logic/parser/tasks/TaskFindCommandParser.java
73.33% <60.00%> (+2.87%)
:arrow_up:

src/main/java/taskbook/model/task/Description.java
76.92% <100.00%> (ø)

src/main/java/taskbook/model/task/Task.java
58.42% <100.00%> (+1.95%)
:arrow_up:

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


updated project list link

Not sure where the project list link should go to, but the current location results in a 404.

Thanks!

Thanks!


Gemini by sample not cohort

My gemini directory (joint calling n=24) has vcf's and db's for each sample. In past runs it only contained the multisample vcf and db.  Also, each of these db's was put into the final directory. Does that seem expected?  I tried to reproduce this with the test case (./run_tests.sh joint) but couldn't. Is it possible you have joint calling specified but don't have the samples in a shared batch within the metadata? I'll try to think more on possible issues but that's the first that comes to mind. Hope this explains it.

Ugh, I sure am good at doing everything wrong.
I put batch in the sample.csv file but forgot to add it to the template
config yaml. It needs to be in both to end up in the final sample yaml,
correct?
On Thu, Mar 19, 2015 at 6:05 PM, Brad Chapman<EMAIL_ADDRESS>wrote:

Daryl;
Sorry about the issue. I tried to reproduce this with the test case (./run_tests.sh
joint) but couldn't. Is it possible you have joint calling specified but
don't have the samples in a shared batch within the metadata? I'll try to
think more on possible issues but that's the first that comes to mind. Hope
this explains it.
—
Reply to this email directly or view it on GitHub
https://github.com/chapmanb/bcbio-nextgen/issues/794#issuecomment-83834774
.

Where does batch come into play for the joint pipeline. If it didn't make
it into the final yaml, could I start the pipeline at the gemini time
point?
On Fri, Mar 20, 2015 at 2:55 PM, Daryl Waggott<EMAIL_ADDRESS>wrote:

Ugh, I sure am good at doing everything wrong.
I put batch in the sample.csv file but forgot to add it to the template
config yaml. It needs to be in both to end up in the final sample yaml,
correct?
On Thu, Mar 19, 2015 at 6:05 PM, Brad Chapman<EMAIL_ADDRESS>wrote:

Daryl;
Sorry about the issue. I tried to reproduce this with the test case (./run_tests.sh
joint) but couldn't. Is it possible you have joint calling specified but
don't have the samples in a shared batch within the metadata? I'll try
to think more on possible issues but that's the first that comes to mind.
Hope this explains it.
—
Reply to this email directly or view it on GitHub
https://github.com/chapmanb/bcbio-nextgen/issues/794#issuecomment-83834774
.

Daryl;
Putting the batch in the sample.csv should be all you need to do, and it'll end up in the final sample YAML. I couldn't reproduce an issue with it being left out running the unit test (./run_tests.sh template) but please let me know if I'm missing anything.
Regarding re-running, you'll need to re-do the joint and GEMINI analysis, so remove both of those directories and checkpoints/multicores2.done and you should be able to re-run. Hope this fixes it for you.


Request: Compatibility between Cow in a jar and EnderIO Conduits

They suggested to put this request over on your end rather on theirs.
I'd like you to add compatibility for the EnderIO conduits so I can use the ENDERIO Drums to store more milk from the Cow in a Jar then later use it.
Current version used 1.10.2 but I'd like it through all versions

This is dealt with by #231 (for upcoming Minecraft 1.12 update)


how to use custom order filed instead of the default order field id , when use First、Take、Last?

when i use under sql，
db.First(&user)
the final sql  is:
SELECT * FROM users ORDER BY id LIMIT 1;
but when i use myself order,
db.Order("name desc").First(&user)
the final sql  is:
SELECT * FROM users ORDER BY name desc, id LIMIT 1;
but, the order field id that not what  i want , and it will make the query more slow.

sorry,i now find the answer from the docs.
// Get one record, no specified order
db.Take(&user)
// SELECT * FROM users LIMIT 1;


Fixing size

Is your feature request related to a problem? Please describe.
Some of the book tiles doesn't clearly show up the details as all the book tile have the same size while some of the book description and book name are large. Thus description gets hidden behind buttons.
Describe the solution you'd like
It can be done by:

Making the image of the book small
Increasing the size of that particular tile
Reducing the spacing between description
Decreasing the padding of the content inside tile

Are you willing to contribute to this issue? [Yes/No]
Yes
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context

@Sonaljain6431  We don't want the card design to be changed for the genre page. If you could suggest other alternatives like one could be fixing the no of lines to be displayed for book name and author name.

The padding or font-size of the text can be decreased.

@Sonaljain6431 adding bottom padding to author name would work what you say?

It can increase the size of the card design if card is not set to box-sizing

Also fixing the line to be displayed for the book title will work

It indirectly involves changing the font size

Can I work on this issue?

It can increase the size of the card design if card is not set to box-sizing

True
So go for fixing lines to be displayed for book title or book author would work check this for same

Can I work on this issue?

Go ahed

Ok

Go through starter guide it will help.

@Sonaljain6431 you need to do this to explore and genre-wise book displayed page.

Go through starter guide it will help.

Okay mam!

Is it ok if work on this issue?
I can also improve UI of the tile.

Is it ok if I work on this issue?
I can also improve UI of the book tile.


Roadmap to 1.0

This is a mind dump of what I'd like to see in for 1.0, API wise, functionality wise, and algorithmic wise.

[ ] The big goals for 1.0 are:

[x] API for Word algorithms.
[ ] API for SWAR algorithms.
[ ] API for algorithms on Word slices.
[ ] i128/u128 support.
[ ] Support stable Rust.

[ ] The word algorithms I would like to see in the library for 1.0 are:

[x] Basic algorithms from N3864 / stdcxx-bitops.
[ ] Morton indices algorithms:

[x] BMI2.0
[x] Magicbits
[x] LUT
[ ] sLUT

[x] Greatest common divisor: #11.
[x] Hamming distance: #2 .
[ ] Swap by primitives.
[ ] parallel_bits_deposit/extract-right and extract_bits_right (see compress and expand.
[ ] Butterfly network.
[ ] sheep-and-goats
[ ] deposit/extract flip variants (left and right).
[ ] omega-flip network.
[ ] sign extend
[ ] gray code (and inverse)
[ ] is x a contiguous sequence of 1 bits ?

[ ] The subword algorithms (SWAR) I would like to see in the library for 1.0 are:

[ ] broadcast/deposit all: fill every subword with value
[ ] gather/extract: extract the value of a subword
[ ] broadcast/deposit: fill subword i with value
[ ] count_ones/count_zeros/ leading ones/ leading zeros / trailing ones / trailing zeros in subword i
[ ] does one subword contain the value zero ?
[ ] parity of the subword i
[ ] binary operations for the i-th subword values (and for all values) of the words x and y, with/without wrapping/saturation, signed/unsigned, etc: : : add/sub/mul/div/mod ...
[ ] unary operations for the i-th subword values (and for all values) of the word x: neg, increment, decrement, abs, ..
[ ] logical operations for the i-th subword values (and for all values) of the words x and y: eq, neq, leq,geq, le, ge,
[ ] bitwise operations for the i-th subword values (and for all values) of the word x: shifts, and/or/xor/rotation...
[ ] "horizontal" binary operations (for adjacent subwords in a word): add/sub/mul/...

[ ] The word slices algorithms I would like to see in the library for 1.0 are:

[ ] count non-zero/zero bytes (use the byteorder crate for this?)
[ ] bit matrices: inversion, transposition

a "clear leading one" would be nice


Script is moving the downloaded file then converting

Should the script not be converting the file and then moving it?
I am using default settings.

This behaviour is normal.  The script can be set to move the file to a directory manually using move to =  after the conversion.

Actually I need more information, the behavior may be due to an incomplete installation
Did you set up all components of the script or just part of it? Without setting up the post downloader scripts (Sonarr/SAB/Torrent) you will not get conversion before moving file. If you do set those up then converting before the file is moved is easily possible

I have setup settings for Sonarr, Radarr, Deluge, SABnzb and PLEX

So then the Deluge and SAB scripts if set up properly and if conversion is enabled in their respective sections of autoProcess.ini should convert the files before they are moved to their final destination
Tagging however is done after moving
From: Smalfinn
Sent: Wednesday, August 2, 2017 7:31 AM
To: mdhiggins/sickbeard_mp4_automator
Cc: Michael Higgins; Comment
Subject: Re: [mdhiggins/sickbeard_mp4_automator] Script is moving thedownloaded file then converting (#775)
I have setup settings for Sonarr, Radarr, Deluge, SABnzb and PLEX
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

autoProcess.ini: https://pastebin.com/ajc7dprv
Conversion was enabled on both but still moves the file and then converts

Removed "output_directory =" from Deluge and SAB in autoProcess.ini and it now works the way I expected... weird

But now re-converts the .mp4 when it is moved to it's final location?!

Turn off convert-MP4 in options
Sent from my iPhone

On Aug 2, 2017, at 11:37, Smalfinn<EMAIL_ADDRESS>wrote:
But now re-converts the .mp4 when it is moved to it's final location?!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Perfect!


Design a logo

I have no artistic ability whatsoever - so any offers of help are most welcome!
(Related to #61 and others with the non-coding tag)


Signatures with RSA

We should support signatures with RSA key pairs (256, 384 and 512), as they are commonly used with json web tokens.

@vigoo This should probably be closed  as it was fixed by https://github.com/zio/zio-crypto/commit/1ab0c15ac72954ff8575d7c66a87ac3b67386f13.


Devtoberfest - Week 6 - Fun Friday

Tutorials: https://developers.sap.com/tutorials/devtoberfest-week-6-fun-friday.html
Hello folks, I attended week 6 devtoberfest trivia night on November 12th, 17:00 CET (Berlin). But I do not see a points I marked there at gameboard. I use some nickname at menti.com while submitting my answers. The nickname is different from my SCN's ID.
Was I supposed to use SCN's ID at menti.com?
Is there any chance for me to get those points I scored to the gameboard?
thanks

The user that you used on menti.com shouldn't matter. It only matters that you use the same SCN ID to complete the tutorials as what you registered with Devtoberfest for.


lost var definition

Doh, thanks - though looking at the code it's not doing things quite right anyway - as there's a possibility for multiple parents there...


Update const.py

I have, as a newbie, tried to do the change I think is needed to support the extra WirelessHD source input, and also the moved PC source input (I just added 20 so that 10 is untouched). Please feel free to correct any misstake I might have done - I am not used to either GitHub or Python - newbie on thin ice.
According to the documentation this is the list of sources that should be returned if one asks the projector (no I have not tested this part): 20 PC
30 HDMI1
53 LAN
A0 HDMI2
D0 WirelessHD

I have tested this direct into /homeassistant/custom_components/epson_projector_link/projector/const.py and it works perfectly.


ScrollScene breakpoints with gsap.timeline.from

Hi, i use ScrollScene with breakpoints and a gsap timeline with only "from" tweens :
new ScrollScene({
  breakpoints: { 0: false, 768: true },
  triggerElement: '.trigger',
  gsap: { timeline: gsap.timeline({ paused: true }).from('.anim', { y: '100%' }) }
})

My issue is on viewport width < 768px (mobile), where my .anim node gets it initial style from Gsap :
transform: translate(0px, 100%)

where i do not want to : for me the breakpoint is supposed to remove the timeline and all it styles.
From my tests, timeline with only 'to' animation are not concerned by this issue obviously.
The problem is that the timeline stay in "paused state" even if the breakpoints doesn't match.
Should Scrollscene calls the timeline.progress(0).pause() method instead ? like in the ScrollMagic gsap plugin removeTween method ?
Or do you have a better idea how to resolve this problem ?

Hmm. It's already doing this with pause(0) which is the same as progress(0).pause().
What about changing the immediateRender options within gsap?

Hmm. It's already doing this with pause(0) which is the same as progress(0).pause().
What about changing the immediateRender options within gsap?

Interesting option. For me it implies other problems in my animations and i had to refactor it for making it really responsive, but maybe for someone else it could be fine.
Thanks 4 ur help.

I can't tell whether this got resolved. If you have more troubles, just let me know and I'll try and work the kinks out. This library is still fresh.


FinalInternalClassFixer - fix for annotation with space after "@"

Reference: https://github.com/wikimedia/composer-merge-plugin/blob/v2.0.1/src/NestedArray.php#L16

Coverage increased (+0.0004%) to 91.53% when pulling 9de186136c030d092ce28a167a1cc1b2821d0a5d on kubawerlos:fix_FinalInternalClassFixer into 714e1922c6c598c8d032f166fdfbe86217e43bfd on FriendsOfPHP:2.19.

Thank you @kubawerlos.


Look for categories that map against AI genomics

in patent, openalex, crunchbase taxonomies

Has been split into #42 and #39


[Discussion] Versioning

Since the only release of cineast is v2.0.0, I suggest to state the versioning scheme in the README.

I personally would suggest to use semver.

All components of the vitrivr stack have been using semver since v1.0. Due to the low number of actual releases, this is however not obvious.


Center a view

How can I center an UIView?
This is what I'm doing:
class CenterView: UIView {
    let squareView = UIView()

    init() {
        super.init(frame: .zero)

        self.backgroundColor = .lightGray
        self.squareView.backgroundColor = UIColor.gray
        self.addSubview(self.squareView)
    }

    required init(coder aDecoder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }

    override func layoutSubviews() {
        super.layoutSubviews()

        self.squareView.pin.vCenter().hCenter().width(60).height(50)
    }
}

class ViewController: UIViewController {
      override func loadView() {
          self.view = CenterView()
     }
}

And this is what I get:

You're right, sorry for that. I've implemented this method few days ago, and I didn't have the time to unit test it. Thanks for the report. This will be fixed today!

Thanks for the report @pableiros, the fix is completed and is available in the release 1.0.7. Unit test will be added today to ensure that this issue won't appear again 😄

@lucmirego Thank you !!

Also @pableiros, I've forgot, you can also do squareView.pin.center() to center the view

I have tried, but what I have to do is to have a square view positioned at the left and center vertically


Implement CreateFileFromTemplateAction

It'll allow creating a Makefile from the File | New_ menu.

The plugin has been moved to https://github.com/JetBrains/intellij-plugins and is now bundled in CLion and GoLand.
This repository is no longer maintained, please submit all feature requests and bug reports to https://youtrack.jetbrains.com/issues/CPP


Documentation links are broken

Describe the bug
When following a Google link to the documentation, I got redirected to On https://dynatrace-oss.github.io/dynatrace-monitoring-as-code/next/configuration/configuration_structure/. Please not the slash at the end.
This causes all links, e.g. to Supported configuration types, to break as they point to https://dynatrace-oss.github.io/dynatrace-monitoring-as-code/next/configuration/configuration/configTypes_tokenPermissions in this case. Please note the /configuration/configuration.

Thanks for bringing this up @dzoech!
I've opened a PR to fix this (and likely a few more links)


Update documentation about fetcher.load()

fetcher.load() has to be called from within a useEffect or a callback. I added an explanation of this to the documentation.

thanks, I was wondering why heck so many folks were trying to call load as they rendered 😆 I already updated the doc elsewhere though, thanks for the error message PR though!


Allow PEP 508 URL requirements in requires_dist

What's the problem this feature will solve?

I want to put a package on PyPi which uses the new direct url syntaxpkg@git-repo-url from PEP 508. Uploading to PyPi yields
HTTPError: 400 Client Error: Invalid value for requires_dist. Error: Can't have direct dependency:
I have a package which depends on another package which I don't want to go through the trouble of uploading to PyPi as well. This dependency then breaks installing my package from PyPi.

Describe the solution you'd like

Allow PEP 508 URL requirements in requires_dist.
Additional context

Originally reported by @themightyoarfish at https://github.com/pypa/pip/issues/6301

PEP 440 says:

Public index servers SHOULD NOT allow the use of direct references in uploaded distributions.

PEP 508 says:

Firstly, PEP-440 direct references haven't actually been deployed in the wild, but they were designed to be compatibly added, and there are no known obstacles to adding them to pip or other tools that consume the existing dependency metadata in distributions - particularly since they won't be permitted to be present in PyPI uploaded distributions anyway.

As such, I'm going to close this issue as we have no plans to deviate from these PEPs, but thanks for the report.


Index gets confused by Quickfix

If I run Popup with a Quickfix panel open, all sorts of weird behaviors happen, from "buffer number 9 not found in index" to simply opening the wrong buffer when I select one.
At one point it opened a copy of the Quickfix buffer itself.
I suspect you should just ignore Quickfix buffers.
Probably the same for Location boxes.
(Thanks for the plugin!)

Sorry for stalls.
Now the bug should be fixed with this commit:
https://github.com/bsdelf/bufferhint/commit/6aabcde82f5238ce0578763e74890c19a481046a


Prealloc msgs in multierr.Error

"msgs"'s length is known, preallocate it can save memories.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.