Doc: Mask clarification

In the Masking section, it was stated, "though it is also possible to flip the convention around" but no further clarification is given on how that is possible (keyword option? using ~mask manually?).
Also, since this is an Astropy affiliated package, I'm curious on why the mask definition is the opposite of what is adopted by masking in astropy.table.

The instructions should specifically mention InvertedMasks, which are described later in http://spectral-cube.readthedocs.io/en/latest/masking.html#inclusion-and-exclusion.  I agree there should be a link between these sections.
AFAICT, the convention is arbitrary, and I wasn't aware of the astropy.table convention.  The numpy convention is consistent with the astropy one, though.  I've always thought of masking as a multiplicative operation, i.e. result = data * mask, which is an inclusion mask.
However, we should avoid arbitrary conventions if possible.  I'll regard this issue as a TODO to replace BooleanArrayMask with BooleanIncludeArrayMask and BooleanExcludeArrayMask and similar; these should all be straightforward and low-overhead to implement and easier to understand / less subject to arbitrary convention.
Anyone else, please chime in if you feel differently.

I think astropy.table uses the same convention as Numpy masked arrays.
@keflavich - changing the name of the classes might not help with cases like
cube2 = cube1.with_mask(cube1 > 3)

since this still requires the user to know what convention the mask is using?

@astrofrog that's true.  I have a lot that depends on this convention being as it is, but maybe we should add with_include_mask and with_exclude_mask methods too?  Though these would not interact in obvious ways with IncludeMask/ExcludeMask objects.

I also prefer the status quo for masking, namely the mask being an include mask.  This plays very well with scipy.ndimage and the morphology operators for mask manipulation and casts well to arithmetic operations.  It also operates well with calls to return operations valid values: np.sum(image[mask])  I know it's just a convention, but much of my layering on top of spectral cube also relies on the convention operating this way.  I'm not sure why astropy chose such a counterintuitive approach 😉 .

I think with Astropy, it stemmed from Numpy. And it does make sense when your mask is created from DQ arrays, where 0 (False) means a good pixel.


Split Relation.players into 2 methods: one filtered by roles, and one that isn't

What is the goal of this PR?
To fix Relation.players() always returning an empty collection.
What are the changes implemented in this PR?
In https://github.com/graknlabs/grakn-2.0/pull/13, we updated the Grakn RPC to take in two different kinds of messages for retrieving roleplayers from a relation; one filtered by roles, and one that isn't.
Then we aligned client-java's Relation and RelationImpl with the new message format.

Depends on protocol: see graknlabs/protocol#44

Note: test-behaviour is currently failing - this is intentional and will be fixed with further, upcoming changes to client-java, protocol and grakn-2.0.

We'll need to address the change request in here first before we proceed with this PR.


Needs updating!

The project is a bit out of date.
Please do this:

update the openai usage to use the new chatgpt API instead of text davinci 3
mark lib as ignored folder
test it in replit and make sure it still works
use node_modules with yarn config
use pm2 - see https://github.com/firtoz/GPT-Shell/pull/15/files

I had a start at this branch, but didn't have a chance to test it, so, feel free to base your code on it:
https://github.com/firtoz/GPT-Shell/compare/update-project?expand=1

Bounty: $50!  What do you recommend as the alternative?

Sorry, I don't have any experience with alternatives. My comment was just a warning to not post any further bounties at Bountysource because they are not paying hunters anymore.

I guess I will withdraw it if possible and post on an alternative

Bountysource is a shell company by now, pretty sure your funds are stuck. They no longer respond to anyone including their biggest backer. IBM is engaging its legals now.

 Should have done more research. Thanks for letting me know at least!

I will see if PayPal can help with refund

Note to bounty claimers: if you complete it, let me know here, I will send the bounty to you directly

There aren't a lot of breaking changes as the libraries still work
#18

Fixed via #19 - bounty resolved off platform

@mamonet a little success :D

I'm really glad to hear that. Apparently, PayPal was able to discern their scam business.
$50 not that much but at least Bountysource doesn't seize your funds as they don't seem to get enough after embezzling thousands of dollars from other backers and bounty hunters.

@firtoz Do you mind if I referred this issue to other backers so they can do the same within 180 days of their PayPal transition?

All good, go ahead @mamonet


Try out cypress

For end to end testing.
Other potential tools include puppeteer or RobotFramework, but cypress seems like the simplest to get up and running.

Closing in favor of #96

Closing in favor of #96


Hide progress view for students in ITSI theme.

Very simple PR.
[#112926811]
https://www.pivotaltracker.com/story/show/112926811

Looks good :+1:


gif supporti,

Hi,
thanks for this very useful gem. And it would be even more wonderful if you could support gif with gifsicle for instance

Sure, shouldn't be too difficult to add another optimizer to https://github.com/jtescher/image_optimizer/tree/master/lib/image_optimizer
If you wanted to submit a PR there I'd be happy to review it

Fixed via https://github.com/jtescher/image_optimizer/pull/10


Need to handle refs/branches

And ref directories.
These should be made updatable and should auto-refresh.

Refs are implemented (without additional functionality).


[nit] .sh is not .js updating billboard script

the docs for billboard app
https://docs.hiro.so/example-apps/billboard#updating-the-billboard-value
refer to using a shell script

you can use the update-message.sh script in the root

but in fact it's a js script
https://github.com/pgray-hiro/stacks-billboard/blob/main/update-message.js
also might be good to link to it directly (tho it might move :( )

thanks so much for tall the issues @dcsan!


Started writing readme for proper info about the project

updated a typo

updated a typo

will do that by tonight . Thanks

Also, closing an issue/PR means its done. You only close them when:

The commits have been merged OR issue has been resolved.
The commits have been rejected OR issue has been marked as wont-fix.

Didn't know that.Thanks

Made the changes proposed.


[POC] - Add support to run moqui jobs from the app

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

Currently, we only need to identify the requirements and challenges for this approach.

We will pass the moqui instance url to the app after login and then use the same approach for login in moqui as done in moqui apps. As we have stored ofbiz specific token and oms in omsRedirectionInfo for moqui specific apps, in this case we will store moqui specific token and oms in omsRedirectionInfo.
We need to run specific moqui job from ofbiz app, for this case we will create a ProductStore setting and store the jobId in the setting that needs to be run from the app. Discussed the approach of pProductStore setting with Deepak Sir.
Currently after login we identify that whether the app supports moqui login or not in launchpad, in the similar manner we will create another method and an env config that will help in identifying whether the ofbiz app requires moqui login or not and then pass the moqui url conditionally in url.


TypeScript and Webpack import errors

This is related to #649
I'm trying to use Raven in a Typescript project and I can't get the import to work correctly - I think there is something strange in the typings setup.
In my app I have the following:
import Raven from 'raven-js'
Raven.config('my dsn).install()

This code compiles correctly, but fails at runtime:
Uncaught TypeError: Cannot read property 'config' of undefined(anonymous function) @ index.tsx:12

My first thought was I was including the type definitions for raven-js, but not the code, but if I inspect the compiled JavasScript file I can verify that the raven-js is present.
If I try to import like this:
import * as Raven from 'raven-js'
Raven.config('my dsn').install()

I get a syntax error: error TS2339: Property 'config' does not exist on type 'typeof 'raven-js''., but this does install Raven into the page (it's not null):
import * as Raven from 'raven-js'
console.log(Raven)

produces:
raven Raven {_hasJSON: true, _hasDocument: true, _lastCapturedException: null, _lastEventId: null, _globalServer: null…}

So when I import Raven one way the type definitions work, but runtime fails, and if I import the other way the type definitions work but runtime fails.
Versions

typescript: 2.0.3
webpack: 1.13.2
npm: 3.9.3
node: v6.2.1

tsconfig
{
  "compileOnSave": true,
  "compilerOptions": {
    "target": "es5",
    "jsx": "react",
    "noImplicitAny": true,
    "noImplicitThis": true,
    "sourceMap": true,
    "allowJs": true,
    "strictNullChecks": false // TODO - enable this
  },
  "exclude": [
    "custom_typings", "node_modules"
  ]
}

typings
{
  "globalDependencies": {
    ...
    "ravenjs": "registry:dt/ravenjs#0.0.0+20160907111239",
    ...
}

OK, something really odd is up - if I don't use typing, but instead include a copy of raven.d.ts directly in my project everything works as expected, using import * as Raven from 'raven-js'.

I've just integrated raven-js in my Ionic 2 project. I didn't really have any problems installing it and configuring. I've followed the instruction from https://docs.sentry.io/clients/javascript/integrations/angular2/  and the only change is to skip SystemJS configuration and to import Raven like this:
import Raven from 'raven-js';
Other than that the magic just happened and it works.

I've removed typings  from my project and started using npm directly for @types imports. It seems to all be working now without the documented setup. Strange, but it works.
Thanks @vintage

Hi @vintage , can you share a little bit about your ionic2 setup? I just updated my project to RC1, imported raven as you mentioned, but can't get to build with 'ionic serve', I get this error
bundle failed: 'default' is not exported by node_modules/raven-js/src/singleton.js (imported by src/app/app.module.ts).

I even tried to define manually Raven and default in namedExports (rollup.config.js) but with no luck :(
thanks

Hey @davorpeic I'm also using RC1 currently. Here is my full config from app.module.ts. I didn't do any changes in any other file in the project to make the Raven works. Let me know if it doesn't solve your problem!
import { NgModule, ErrorHandler } from '@angular/core';
import { Http, HttpModule } from '@angular/http';
import { IonicApp, IonicModule } from 'ionic-angular';
import { Storage } from '@ionic/storage';
import { TranslateModule, TranslateLoader, TranslateStaticLoader } from 'ng2-translate/ng2-translate';
import Raven from 'raven-js';

import { MyApp } from './app.component';

// Pages
import { AboutPage } from '../pages/about/about';
import { AchievementListPage } from '../pages/achievement-list/achievement-list';
import { CountryListPage } from '../pages/country-list/country-list';
import { HighscorePage } from '../pages/highscore/highscore';
import { HighscoreGeneralPage } from '../pages/highscore/highscore-general/highscore-general';
import { HighscoreMonthlyPage } from '../pages/highscore/highscore-monthly/highscore-monthly';
import { HighscoreDailyPage } from '../pages/highscore/highscore-daily/highscore-daily';
import { HighscoreHardcorePage } from '../pages/highscore/highscore-hardcore/highscore-hardcore';
import { MainMenuPage } from '../pages/main-menu/main-menu';
import { ScoreSubmitPage } from '../pages/score-submit/score-submit';
import { SettingsPage } from '../pages/settings/settings';
import { ShopPage } from '../pages/shop/shop';
import { TutorialPage } from '../pages/tutorial/tutorial';
import { GamePage } from '../pages/game/game';
import { GameHardcorePage } from '../pages/game-hardcore/game-hardcore';

// Components
import { AnswerButton } from '../components/answer-button/answer-button';
import { GameSlot } from '../components/game-slot/game-slot';
import { GameStats } from '../components/game-stats/game-stats';

// Components (game types)
import { ItemRecipeGame } from "../components/game-types/item-recipe/item-recipe";
import { ItemPriceGame } from "../components/game-types/item-price/item-price";
import { ChampionSkillsGame } from "../components/game-types/champion-skills/champion-skills";
import { ChampionAttackTypeGame } from "../components/game-types/champion-attack-type/champion-attack-type";
import { SkillChampionGame } from "../components/game-types/skill-champion/skill-champion";
import { ChampionNameGame } from "../components/game-types/champion-name/champion-name";
import { ChampionTitleGame } from "../components/game-types/champion-title/champion-title";
import { ChampionNationGame } from "../components/game-types/champion-nation/champion-nation";

// Pipes
import { PointsPipe } from '../pipes/points';
import { TimeLeftPipe } from '../pipes/time-left';

// Services
import { AchievementService } from '../providers/achievement/service';
import { AdService } from '../providers/ads/service';
import { ChampionService, SkillService } from '../providers/champion/service';
import { CountryService } from '../providers/country/service';
import { GameplayService } from '../providers/gameplay/service';
import { ItemService } from '../providers/item/service';
import { MusicService } from '../providers/music/service';
import { ScoreService } from '../providers/score/service';
import { SettingsService } from '../providers/settings/service';
import { ShopService } from '../providers/shop/service';
import { GameTypeService } from '../providers/game-type/service';

Raven
<EMAIL_ADDRESS>  .install();

export class RavenErrorHandler implements ErrorHandler {
  handleError(err:any) : void {
    Raven.captureException(err.originalError);
  }
}

let appConfig = {
  statusbarPadding: false,
  backButtonText: '',
  prodMode: true
};

export function createTranslateLoader(http: Http) {
  return new TranslateStaticLoader(http, './assets/i18n', '.json');
};

@NgModule({
  declarations: [
    MyApp,

    // Pages
    AboutPage,
    AchievementListPage,
    CountryListPage,
    HighscorePage,
    HighscoreGeneralPage,
    HighscoreMonthlyPage,
    HighscoreDailyPage,
    HighscoreHardcorePage,
    MainMenuPage,
    ScoreSubmitPage,
    SettingsPage,
    ShopPage,
    TutorialPage,
    GamePage,
    GameHardcorePage,

    // Pipes
    PointsPipe,
    TimeLeftPipe,

    // Components
    AnswerButton,
    GameSlot,
    GameStats,

    // Components (game types)
    ItemRecipeGame,
    ItemPriceGame,
    ChampionSkillsGame,
    ChampionAttackTypeGame,
    SkillChampionGame,
    ChampionNameGame,
    ChampionTitleGame,
    ChampionNationGame
  ],
  imports: [
    IonicModule.forRoot(MyApp, appConfig),
    HttpModule,
    TranslateModule.forRoot({
      provide: TranslateLoader,
      useFactory: (createTranslateLoader),
      deps: [Http]
    })
  ],
  bootstrap: [IonicApp],
  entryComponents: [
    MyApp,
    AboutPage,
    AchievementListPage,
    CountryListPage,
    HighscorePage,
    HighscoreGeneralPage,
    HighscoreMonthlyPage,
    HighscoreDailyPage,
    HighscoreHardcorePage,
    MainMenuPage,
    ScoreSubmitPage,
    SettingsPage,
    ShopPage,
    TutorialPage,
    GamePage,
    GameHardcorePage,

    // Game types
    ItemRecipeGame,
    ItemPriceGame,
    ChampionSkillsGame,
    ChampionAttackTypeGame,
    SkillChampionGame,
    ChampionNameGame,
    ChampionTitleGame,
    ChampionNationGame
  ],
  providers: [
    { provide: ErrorHandler, useClass: RavenErrorHandler },
    Storage,
    AchievementService,
    AdService,
    ChampionService,
    SkillService,
    CountryService,
    GameplayService,
    ItemService,
    MusicService,
    ScoreService,
    SettingsService,
    ShopService,
    GameTypeService
  ]
})
export class AppModule {}

Hey @vintage this is awesome, really appreciate the effort, but, I have the same setup, so that took me to next level :D, I decided to update to RC2 recently published, so I updated all needed modules in package.json, deleted local node_modules (I think this did it), and run npm install again. Now I'm working on getting actual error to get logged in sentry, but at least no js errors related to raven :D
thanks!

anyone tried integrating with rollupJS?

@kleeb delayed but just FYI I got this working with rollup - I was having that error when it wasn't being pulled through the commonjs plugin.
Once I had:
commonjs({
  include: "node_modules/raven-js/**"
})

In my plugins in my gulpfile, it built and imported just fine with import Raven from "raven-js";.
I'm using rollup-plugin-commonjs 8.0.2.

Thanks Chris.
I am doing it slightly different in the Ionic project:
in copy.config.js I added copy job
  copyRaven: {
    src: ['{{ROOT}}/node_modules/raven-js/dist/raven.min.js', '{{ROOT}}/node_modules/raven-js/dist/raven.min.js.map'],
    dest: '{{BUILD}}'
  }

and simply added raven.min.js to the index.html.


Add Battery Discrete IO States

Add battery discrete IO states from sonnen API endpoint: http://<ip>:8080/api/ios.

Full JSON string is available under info.ios
Some relevant discrete IOs, including self consumption relay and pv reduction states are available under ios.DO12, ios.DO13 and ios.DO14

Thanks, LGTM


left navbar component missing in the last version ?

Problem description
Where is the left nafbar in version 0.15.0
Steps to reproduce
Versions

Material-UI: 0.15.0

https://github.com/callemall/material-ui#material-ui

Recently Updated? Please read the changelog, this README and the documentation before posting an issue.

https://github.com/callemall/material-ui/blob/master/CONTRIBUTING.md#asking-questions


Upgrade to go 1.9.3

semaphore and appveyor will update automatically once the distribution is available


Adding plugin via revision.yaml

Added a revision.yaml file to the list of plugins

@vinzscam Thanks - fixed the sign-off commit. Hope it looks ok now 😊


Custom Signed Extensions Example

User description
Solves: #359

Added example for Custom Signed Extensions.
With Custom Signed Extensions have the Codecs mapped to it.

Type
enhancement

Description

Added an example demonstrating the retrieval of signed extensions from runtime metadata in extrinsic_demo.dart.
Fixed type casting issues in extrinsic_payload.dart and signing_payload.dart to ensure dynamic types are correctly cast to String.

Changes walkthrough
Relevant filesEnhancement

extrinsic_demo.dartAdd Signed Extensions Retrieval in Extrinsic Demo

examples/bin/extrinsic_demo.dart
Imported polkadart_scale_codec as scale_codec.  Added code to retrieve and print signed extensions keys from the runtime metadata.

+14/-0

Bug fix

extrinsic_payload.dartFix Type Casting in Extrinsic Payload

packages/polkadart/lib/extrinsic/extrinsic_payload.dart
Modified type casting for keys to support dynamic to String casting.

+2/-1

signing_payload.dartAdjust Type Casting in Signing Payload

packages/polkadart/lib/extrinsic/signing_payload.dart
Adjusted type casting for typeKeys and extraKeys to ensure correct String casting.

+4/-2

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Inline File Walkthrough 💎
For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
true: A collapsable file comment with changes title and a changes summary for each file in the PR.
false (default): File changes walkthrough will be added only to the "Conversation" tab.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

@leonardocustodio PR updated


onDidChangeModelContent issue

monaco-editor npm version: 0.8.1
Browser: Chrome
OS: Mac
this.editor.onDidChangeModelContent((e) => {
  const {
    startLineNumber,
    startColumn,
    endLineNumber,
    endColumn
  } = e.range;

  console.log(endLineNumber);
});

There are 50 lines texts on editor. If you want to clear all texts and try to type 's' text, then you will type 's' after using cmd + a on the editor. That's what I was doing.
But when typing 's' text, onDidChangeModelContent callback gave to me 50 of endLineNumber. There is no text except 's'. Is it bug or not?

This is not a bug. The model content changed event gives the replaced range and the text the range was replaced with.


optimize did fetching in tables

Fixes #395 .
Changes proposed in this PR:

Use endpoint to get only the asset name

this can be marked as ready for review, right? Already tested a bit and could not find any issues

Yes, I was also looking into the refreshing transactions table issue, thought it would be easier to find the problem but I didn't managed to do it yet. I saw that there was an issue opened related to this, so that bug can be done over there and we can close this.

yup, I also secretly hoped by doing this PR we solve #414 but its cause remains a mystery. Now we know it's not caused by the DDO fetching I guess


Restore previous interrupt handler after run

I was running puma's test suite, where rubocop is run before the test suite. One of the tests was hanging, and when pressing Ctrl-C to abort it, I would get rubocop's Ctrl-C handler run.
That seemed unexpected, I think rubocop should probably restore the previously installed handler after it's run?

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[ ] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

Seems like a good change to me, but it requires a changelog entry.

@bbatsov Changelog entry added!

The code looks good to me. Is it possible to write a test for this?

Of course it is, but I don't really feel very excited about it. If this is not good to go without a test I'll just leave this opened so anyone willing to do it (including myself) can pick it up! :)

OK, ping us when ready.

@deivid-rodriguez ping :-)

Hei @bbatsov, I don't think I'll get to this any time soon. I'll close this and reopen when I get time to complete it! :)

Ended up open some separate PRs with a different approach to fix this, also with some testing!


Add tests for PostgreSQL output - v1

Related to redmine ticket: https://redmine.openinfosecfoundation.org/issues/4241
Previous Suricata PR: https://github.com/OISF/suricata/pull/6376
Current Suricata PR: https://github.com/OISF/suricata/pull/6396
Tests for:

SSL Handshake accepted, PGSQL upgraded to TLS, PGSQL connection fails, backend responds with ErrorResponse.
SSL Handshake rejected, connection established, simple query, data results, connection terminated by the frontend.

Followed by: https://github.com/OISF/suricata-verify/pull/550


DataFrame.itertuples

Implement DataFrame.itertuples.
https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.itertuples.html

I don't think we will support this kind of APIs. cc @HyukjinKwon

are you planning to implement it?

Sorry I missed the cc, @ueshin. Yeah, I don't think so too in general. One possibility I was thinking of was toLocalIterator, though ..

@dmitrypol not yet sure. maybe we could map it to toLocalIterator but this kind of API is discouraged by design in general in Koalas. Needs some discussion.

Let me close this since we added this API at https://github.com/databricks/koalas/pull/1960
cc @dmitrypol FYI


Web interface not accessible if host matching is enabled

If my app uses host matching,
app.url_map.host_matching = True

then the flask-profiler web interface cannot be accessed as the URL will always return 404 since it isn't mapped to a host. I would like to suggest an optional config option to set the host to use for the web interface.

I am facing a similar issue after using uwsgi and Nginx. It was working fine with the app running using port 8000 but returns 404 after using Nginx.

Hello @hadeelsharaf, could you please explain more about how you fixed it? I am having the same issue with uwsgi and nginx.

I actually figured out the problem with my application before fixing this
issue.
I had to simulate everything on my local machine.
On Wed, Mar 25, 2020, 11:01 AM ntanhhus<EMAIL_ADDRESS>wrote:

Hello @hadeelsharaf https://github.com/hadeelsharaf, could you please
explain more about how you fixed it? I am having the same issue with uwsgi
and nginx.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/muatik/flask-profiler/issues/65#issuecomment-603723682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLBFFHXPHDIPVFDRFH5BHTRJHB6XANCNFSM4DMGR7LQ
.


🐞 Bug : modes not working with screenshot method.

Thank you for new features discuss in the previous issue.
I just identified a bug, with "mode", they are not working when user want to get a screenshot of only one tweet using the screenshot( ) method ( python usage, not CLI ).
Tweet used for test : https://twitter.com/JagoeCapital/status/1598454780355026945
The issue is probably related to this condition, by but variables are not explicit, I will let you check : ( never seems to be true)
https://github.com/Xacnio/tweetcapture/blob/790ca13b322c4ac7454de999d2a78150f95ef34d/tweetcapture/screenshot.py#L73

Thanks. I'll fix it as soon.


[Bug] BDV2 Javascript Error on Discord Canary

[x] Used appropriate template for the issue type
[x] Searched both open and closed issues for duplicates of this issue
[x] Title adequately and concisely reflects the feature or the bug

Describe the bug
When Discord Canary is started after installing BDV2, an uncaught exception error occurs and then Discord closes.
To Reproduce

Install BDv2 to latest Discord Canary
Launch Discord Canary
Uncaught exception error should occur and clicking okay will close Discord

Expected behavior
Discord loads up like BBD
Screenshots

System information
Windows 10 Pro 64x Insider Preview Skip Ahead 20H1 Build 18865
Discord Canary whatever the latest version is as of 12:08 AM EST 4/10/2019
BDv2 Beta 6
Additional context
Are you willing and able to fix this?
I am not able to fix this, but I will try my best to help the devs solve this issue.

It's a known thing, just build node-sass bindings yourself or use Stable/PTB

On stable i have the same prob


Support request for knowledgekids.ca

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.12.23. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.12.23

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl -v http://www.knowledgekids.ca/videos/shutterbugs/bugathon-wind-blows-s1-e1
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'http://www.knowledgekids.ca/videos/shutterbugs/bugathon-wind-blows-s1-e1']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.12.23
[debug] Python version 3.4.4 - Windows-10-10.0.16299
[debug] exe versions: ffmpeg 3.3.4, ffprobe 3.3.4, rtmpdump 2.4
[debug] Proxy map: {}
[generic] bugathon-wind-blows-s1-e1: Requesting header
WARNING: Falling back on generic information extractor.
[generic] bugathon-wind-blows-s1-e1: Downloading webpage
[generic] bugathon-wind-blows-s1-e1: Extracting information
ERROR: Unsupported URL: http://www.knowledgekids.ca/videos/shutterbugs/bugathon-wind-blows-s1-e1
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp27__tkx0\build\youtube_dl\YoutubeDL.py", line 784, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp27__tkx0\build\youtube_dl\extractor\common.py", line 438, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp27__tkx0\build\youtube_dl\extractor\generic.py", line 3063, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: http://www.knowledgekids.ca/videos/shutterbugs/bugathon-wind-blows-s1-e1
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://www.knowledgekids.ca/videos/shutterbugs/bugathon-wind-blows-s1-e1

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

@dstftw Are you still working on this? The video players are powered by JW Player.
And it's also easy to get m3u8 links: http://videos-f.jwpsrv.com/content/conversions/D6IiMaB8/videos/CCWa8rsI-23509834.mp4.m3u8?token=0_5a90d2e6_0x7a08479bd393cfc7d9d7c2bfac94c0c13bbdaf68

Not working on this.


Updates

Coverage increased (+0.3%) to 75.065% when pulling e18004f893026729ce1a469e7ac8d71e7aa45d2a on updates into 0030a607d7775e4965011e40acdfea28e3047161 on master.


⚠ Samsung has degraded performance

In 8e1c8a7, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3045 ms

Resolved: Samsung performance has improved in fa6d4b9.


sets the ethereum window object

This may have been causing issues on multiple dapp sites.

Related to: #1225


Support for custom not found handler

You can now set a custom not found handler on the muxer

Merged, thanks. (Accidentally rebased the commit so it won't auto-close.)
I made some small adjustments in b9a994a8f6a5945800427435c904865e76dd6d42:

Added a test
Made the NotFound handler be called always if the pattern doesn't match. (Previously, the convenience behavior of 405 Method Not Allowed + setting the Allow header would kick in, instead of NotFound, if there is a matching pattern with a different associated method. It seems clear that NotFound should override that.)
Fleshed out the docs more, including mentioning that NotFound should be set before serving requests.


Added Coffee support

First step to support coffeescript. It doesn't support sourcemap yet

Lovely! Thanks!


This is cool, how did you know to use this?

https://github.com/salt-die/Advent-of-Code/blob/acad2aed95106f5ac3bcf786bbfdd0612d5a1a3a/2021/day_11.py#L17

Convolutions can be used to count the number of non-zero neighbors a cell has. Let's say we have a random binary array, a:
[[1 1 1 1 0]
 [1 0 1 0 0]
 [1 0 1 1 0]
 [0 1 0 0 0]
 [1 0 0 0 0]]

If we convolve it with the kernel [[1, 1, 1], [1, 0, 1], [1, 1, ]] (convolve(a, kernel, mode="constant")) we get:
[[2 4 3 2 1]
 [3 7 5 5 2]
 [2 5 3 2 1]
 [3 3 3 2 1]
 [1 2 1 0 0]]

Note that these numbers are exactly the number of non-zero neighbors that the cells in the original array had. You can change the type of neighborhoods you care about by modifying the kernel. If you only want to count neighbors in the four cardinal directions use kernel = [[0, 1, 0], [1, 0, 1], [0, 1, 0]]:
[[2 2 3 1 1]
 [2 3 2 3 0]
 [1 3 2 1 1]
 [3 0 2 1 0]
 [0 2 0 0 0]]

As the convolution in our problem was over the flashing octopuses and it did not matter if they counted themselves as neighbors, I simplified the KERNEL to just be all ones.
Here's an image from Convolutional Neural Networks (CNNs) in TensorFlow to help illustrate:

The kernel is being centered over each cell in the array and we take the sum of the element-wise multiplication.
Here's a better introduction to convolutions by 3Blue1Brown youtuber, Grant Sanderson: Convolutions in image processing

Thanks.  This was a great idea 💯 to use this


Website Down

It looks like the website is down. Any way you can get it back up?

The code of coloration-web needs to be updated to run on newer Ruby version and Heroku.
I'd happily accept a PR if someone figured out the needed changes.


Bump Slimmer

This commit does two things:

Support for the proposition header was removed from slimmer v8.0.0 so remove it from the codebase and remove the test for it.
Bump gem version.

This work needs to be done in advance of another PR which will make use of further changes to slimmer in this PR:  https://github.com/alphagov/slimmer/pull/121

This gem bump has a dependency on https://github.com/alphagov/static/pull/558 and shouldn't be merged until that PR has been deployed.

Hello, I've addressed all changes (thanks @fofr and @fatbusinessman) and http://github.com/alphagov/static#558 has been merged now so this is good to go I think.

Ah, already merged. I was going to suggest bumping to 8.1.0


Preview images of post should provide link on click

🆕🐥 First Timers Only
This issue is reserved for people who have never contributed to this project or any open source software (OSS) in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution.
👾 Description of the issue
The website contains a blog that is not shown in the main menu today since the work on the blog feature still needs to be fully done. Anyway, the blog is already part of the page and can be found here: https://open-elements.com/posts/
On that page, you see a list of blog post previews. To show the blog post, you need to click on the text of the blog. When clicking on the preview image of a post, nothing happens. Here, we want to have the full blog post preview as a link to the post. So, when clicking on the preview image of a post, the user should be forwarded to the blog post.

📋 Step by step guide to do a contribution
If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow.
A more detailed general documentation of the GitHub PR workflow can be found here.

[ ] Claim this issue: Comment below that you are interested in working on the issue
[ ] Wait for assignment: A community member with the given rights will add you as an assignee of the issue
[ ] Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button)
[ ] Check out the forked repository on your local machine
[ ] Create a feature branch for the issue
[ ] Solve the issue in your branch
[ ] Commit your changes: to your branch
[ ] Start a Pull Request (PR): in our repository
[ ] Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error, do not hesitate to add a comment to the PR and ask the community for support.
[ ] Wait for reviews: Members of the community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will discuss it with you and describe the next steps for solving it.
[ ] You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of our community as an open-source contributor ❤

🎉 Contribute to Hacktoberfest
Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

hey assign me this issue ,, i want to solve this and have potential skils to solve this

@shbhmexe sorry for the delay. Are you still interested in working on the issue?

Hey @hendrikebbers I want to work on this plz assign me this

Hey @hendrikebbers  i am unable to clone the repo it shows this error

I try multiple time and also try using SSH but this doesnt work

Hey @hendrikebbers  Where is your Public folder in which index.html file is present i am unable to find index file which is located in public folder

YOu can find it here: https://github.com/OpenElements/open-elements-website/blob/main/layouts/index.html
The website is based on Hugo (https://gohugo.io) and you need to use hugo to build it

This is not the mian file of page . Where is main index.html of website ?
Previously i see this in public folder but now there is no public filder in code

Hey @hendrikebbers can you help today is last date of hacktober fest


test(manage): events unit tests

Unit testing of "onEvent" methods under Manage CPP SDK

test logs:
manage-sdk-unit-test-logs.txt

Please update branch so it is not out-of-date with next.

:tada: This PR is included in version 1.5.0-next.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ZFP broken with current PGI / NVHPCSDK with > 1d arrays

Using the current NVIDIA HPC SDK (what was previously the PGI compiler), all tests fail for arrays > 1D:
$ cmake ../../source/master
-- The C compiler identification is PGI 20.9.0
-- The CXX compiler identification is PGI 20.9.0
-- Check for working C compiler: /opt/nvidia/hpc_sdk/Linux_x86_64/20.9/compilers/bin/nvc
-- Check for working C compiler: /opt/nvidia/hpc_sdk/Linux_x86_64/20.9/compilers/bin/nvc -- works
...
-- Build files have been written to: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master
$ make
...
[ 97%] Linking C executable ../bin/zfp
[ 97%] Built target zfpcmd
[100%] Linking CXX executable ../bin/testzfp
[100%] Built target testzfp
$ ctest
Test project /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master
    Start 1: small-arrays-1d-fp32
1/8 Test #1: small-arrays-1d-fp32 .............   Passed    0.02 sec
    Start 2: small-arrays-1d-fp64
2/8 Test #2: small-arrays-1d-fp64 .............   Passed    0.02 sec
    Start 3: small-arrays-2d-fp32
3/8 Test #3: small-arrays-2d-fp32 .............***Failed    0.01 sec
    Start 4: small-arrays-2d-fp64
4/8 Test #4: small-arrays-2d-fp64 .............***Failed    0.02 sec
    Start 5: small-arrays-3d-fp32
5/8 Test #5: small-arrays-3d-fp32 .............***Failed    0.02 sec
    Start 6: small-arrays-3d-fp64
6/8 Test #6: small-arrays-3d-fp64 .............***Failed    0.03 sec
    Start 7: small-arrays-4d-fp32
7/8 Test #7: small-arrays-4d-fp32 .............***Failed    0.01 sec
    Start 8: small-arrays-4d-fp64
8/8 Test #8: small-arrays-4d-fp64 .............***Failed    0.01 sec

25% tests passed, 6 tests failed out of 8

Total Test time (real) =   0.15 sec

The following tests FAILED:
	  3 - small-arrays-2d-fp32 (Failed)
	  4 - small-arrays-2d-fp64 (Failed)
	  5 - small-arrays-3d-fp32 (Failed)
	  6 - small-arrays-3d-fp64 (Failed)
	  7 - small-arrays-4d-fp32 (Failed)
	  8 - small-arrays-4d-fp64 (Failed)
Errors while running CTest
[chuck.atkins@deepthought master]$

This came up when I was updating the CI builds for https://github.com/ornladios/adios2 to use the new NVHPCSDK instead of the older PGI compiler and after addressing all other issues the only remaining test failures were when using ZFP and only with 2d arrays.  Rebuilding zfp with gcc and adios with PGI, the adios tests pasts.  This is reflective in the zfp build itself failing multidimensional array tests when built with PGI.

I experimented with PGI a few years ago but could never get it to work.  It wasn't obvious then what the issue was.  I think testzfp ensures that the compiler adheres to any implementation-dependent assumptions, such as right shifts of signed integers being arithmetic shifts, that signed integers use two's complement representation, and that integer types are of the proper length.  The issue could, perhaps, be differences in floating-point rounding mode or similar that prevents testzfp from generating the exact same floating-point test data.
It might be instructive to compress a 2D data set using the zfp command-line tool to see if you get the same compressed output as with other compilers.
Can you run ctest -V -I 1,8 to give us a better idea of which tests are failing?

When our CI was running the previous 19.10 PGI release the ZFP tests were passing so I assume it's a recent change.
$ ctest -V -I 1,8
UpdateCTestConfiguration  from :/home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/DartConfiguration.tcl
Parse Config file:/home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/DartConfiguration.tcl
UpdateCTestConfiguration  from :/home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/DartConfiguration.tcl
Parse Config file:/home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/DartConfiguration.tcl
Test project /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
    Start 1: small-arrays-1d-fp32

1: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "1d" "fp32"
1: Test timeout computed to be: 1500
1: zfp version 0.5.5 (May 5, 2019)
1: library version 85
1: CODEC version 5
1: data model LP64
1:
1: testing 1D array of floats
1:   compress:   rate= 2                                                    OK
1:   decompress: rate= 2 1.626e+01 <= 1.627e+01                             OK
1:   compress:   rate= 8                                                    OK
1:   decompress: rate= 8 8.276e-02 <= 8.277e-02                             OK
1:   compress:   rate=32                                                    OK
1:   decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
1:   compress:   precision= 4 ratio=  7.474                                 OK
1:   decompress: precision= 4                                               OK
1:   compress:   precision= 8 ratio=  4.995                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  2.589                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  2.589                          OK
1:   decompress: tolerance=9.766e-04 3.662e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=2.384e-07 ratio=  1.372                          OK
1:   decompress: tolerance=2.384e-07 0.000e+00 <= 2.384e-07                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.194                          OK
1:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
1:   compress:   reversible ratio=  2.253                                   OK
1:   decompress: reversible                                                 OK
1:   construct:  4.578e-05 <= 4.578e-05                                     OK
1:   update:     2.155e-02 ~ 2.155e-02                                      OK
1:
1: all tests passed
1/8 Test #1: small-arrays-1d-fp32 .............   Passed    0.02 sec
test 2
    Start 2: small-arrays-1d-fp64

2: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "1d" "fp64"
2: Test timeout computed to be: 1500
2: zfp version 0.5.5 (May 5, 2019)
2: library version 85
2: CODEC version 5
2: data model LP64
2:
2: testing 1D array of doubles
2:   compress:   rate= 3                                                    OK
2:   decompress: rate= 3 1.626e+01 <= 1.627e+01                             OK
2:   compress:   rate= 4                                                    OK
2:   decompress: rate= 4 1.600e+01 <= 1.601e+01                             OK
2:   compress:   rate=16                                                    OK
2:   decompress: rate=16 1.831e-04 <= 1.832e-04                             OK
2:   compress:   rate=64                                                    OK
2:   decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
2:   compress:   precision= 8 ratio=  8.943                                 OK
2:   decompress: precision= 8                                               OK
2:   compress:   precision=16 ratio=  4.882                                 OK
2:   decompress: precision=16                                               OK
2:   compress:   precision=32 ratio=  2.323                                 OK
2:   decompress: precision=32                                               OK
2:   compress:   tolerance=9.766e-04 ratio=  4.882                          OK
2:   decompress: tolerance=9.766e-04 3.662e-04 <= 9.766e-04                 OK
2:   compress:   tolerance=4.441e-16 ratio=  1.266                          OK
2:   decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
2:   compress:   tolerance=0.000e+00 ratio=  1.127                          OK
2:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
2:   compress:   reversible ratio=  4.210                                   OK
2:   decompress: reversible                                                 OK
2:   construct:  1.831e-04 <= 1.832e-04                                     OK
2:   update:     2.155e-02 ~ 2.155e-02                                      OK
2:
2: all tests passed
2/8 Test #2: small-arrays-1d-fp64 .............   Passed    0.02 sec
test 3
    Start 3: small-arrays-2d-fp32

3: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "2d" "fp32"
3: Test timeout computed to be: 1500
3: zfp version 0.5.5 (May 5, 2019)
3: library version 85
3: CODEC version 5
3: data model LP64
3:
3: testing 2D array of floats
3:   compress:   rate= 2                                                    OK
3:   decompress: rate= 2 [7.646e+01 > 1.500e+00]                           FAIL
3:   compress:   rate= 8                                                    OK
3:   decompress: rate= 8 [7.998e+01 > 3.663e-03]                           FAIL
3:   compress:   rate=32                                                    OK
3:   decompress: rate=32 [7.700e+01 > 0.000e+00]                           FAIL
3:   compress:   precision= 4 ratio=  9.526 [1720 != 592]                  FAIL
3:   decompress: precision= 4                                               OK
3:   compress:   precision= 8 ratio=  4.348 [3768 != 1328]                 FAIL
3:   decompress: precision= 8                                               OK
3:   compress:   precision=16 ratio=  2.083 [7864 != 4384]                 FAIL
3:   decompress: precision=16                                               OK
3:   compress:   tolerance=9.766e-04 ratio=  1.932 [8480 != 4936]          FAIL
3:   decompress: tolerance=9.766e-04 [7.639e+01 > 9.766e-04]               FAIL
3:   compress:   tolerance=2.384e-07 ratio=  1.122 [14600 != 11064]        FAIL
3:   decompress: tolerance=2.384e-07 [7.678e+01 > 2.384e-07]               FAIL
3:   compress:   tolerance=0.000e+00 ratio=  1.020 [16056 != 12520]        FAIL
3:   decompress: tolerance=0.000e+00 (7.518e+01 > 0)                        OK
3:   compress:   reversible ratio=  2.626 [6240 != 5104]                   FAIL
3:   decompress: reversible [reconstruction differs]                       FAIL
3:   construct:  [7.833e+01 > 7.630e-06]                                   FAIL
3:   update:     [3.126e+01 != 3.755e-01]                                  FAIL
3:
3: 15 test(s) failed
3/8 Test #3: small-arrays-2d-fp32 .............***Failed    0.01 sec
test 4
    Start 4: small-arrays-2d-fp64

4: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "2d" "fp64"
4: Test timeout computed to be: 1500
4: zfp version 0.5.5 (May 5, 2019)
4: library version 85
4: CODEC version 5
4: data model LP64
4:
4: testing 2D array of doubles
4:   compress:   rate= 1                                                    OK
4:   decompress: rate= 1 [7.737e+01 > 2.376e+01]                           FAIL
4:   compress:   rate= 4                                                    OK
4:   decompress: rate= 4 [7.901e+01 > 1.797e-01]                           FAIL
4:   compress:   rate=16                                                    OK
4:   decompress: rate=16 [7.956e+01 > 8.584e-06]                           FAIL
4:   compress:   rate=64                                                    OK
4:   decompress: rate=64 [7.397e+01 > 0.000e+00]                           FAIL
4:   compress:   precision= 8 ratio=  8.480 [3864 != 1424]                 FAIL
4:   decompress: precision= 8                                               OK
4:   compress:   precision=16 ratio=  4.117 [7960 != 4480]                 FAIL
4:   decompress: precision=16                                               OK
4:   compress:   precision=32 ratio=  2.029 [16152 != 12616]               FAIL
4:   decompress: precision=32                                               OK
4:   compress:   tolerance=9.766e-04 ratio=  3.821 [8576 != 5032]          FAIL
4:   decompress: tolerance=9.766e-04 [7.948e+01 > 9.766e-04]               FAIL
4:   compress:   tolerance=4.441e-16 ratio=  1.108 [29568 != 26016]        FAIL
4:   decompress: tolerance=4.441e-16 [7.643e+01 > 4.441e-16]               FAIL
4:   compress:   tolerance=0.000e+00 ratio=  1.007 [32536 != 28984]        FAIL
4:   decompress: tolerance=0.000e+00 (7.888e+01 > 0)                        OK
4:   compress:   reversible ratio=  5.146 [6368 != 5232]                   FAIL
4:   decompress: reversible [reconstruction differs]                       FAIL
4:   construct:  [7.934e+01 > 8.584e-06]                                   FAIL
4:   update:     [2.390e+74 != 3.755e-01]                                  FAIL
4:
4: 16 test(s) failed
4/8 Test #4: small-arrays-2d-fp64 .............***Failed    0.02 sec
test 5
    Start 5: small-arrays-3d-fp32

5: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "3d" "fp32"
5: Test timeout computed to be: 1500
5: zfp version 0.5.5 (May 5, 2019)
5: library version 85
5: CODEC version 5
5: data model LP64
5:
5: testing 3D array of floats
5:   compress:   rate= 2                                                    OK
5:   decompress: rate= 2 [7.361e+01 > 1.500e+00]                           FAIL
5:   compress:   rate= 8                                                    OK
5:   decompress: rate= 8 [7.304e+01 > 9.583e-03]                           FAIL
5:   compress:   rate=32                                                    OK
5:   decompress: rate=32 [7.716e+01 > 0.000e+00]                           FAIL
5:   compress:   precision= 4 ratio= 60.235 [272 != 152]                   FAIL
5:   decompress: precision= 4                                               OK
5:   compress:   precision= 8 ratio=  8.258 [1984 != 1040]                 FAIL
5:   decompress: precision= 8                                               OK
5:   compress:   precision=16 ratio=  2.805 [5840 != 4600]                 FAIL
5:   decompress: precision=16                                               OK
5:   compress:   tolerance=9.766e-04 ratio=  2.233 [7336 != 6104]          FAIL
5:   decompress: tolerance=9.766e-04 [7.148e+01 > 9.766e-04]               FAIL
5:   compress:   tolerance=2.384e-07 ratio=  1.295 [12648 != 11752]        FAIL
5:   decompress: tolerance=2.384e-07 [7.380e+01 > 2.384e-07]               FAIL
5:   compress:   tolerance=0.000e+00 ratio=  1.206 [13584 != 12784]        FAIL
5:   decompress: tolerance=0.000e+00 (7.841e+01 > 0)                        OK
5:   compress:   reversible ratio=  2.731 [6000 != 6096]                   FAIL
5:   decompress: reversible [reconstruction differs]                       FAIL
5:   construct:  [7.620e+01 > 3.148e-05]                                   FAIL
5:   update:     [1.979e+26 != 1.846e+00]                                  FAIL
5:
5: 15 test(s) failed
5/8 Test #5: small-arrays-3d-fp32 .............***Failed    0.02 sec
test 6
    Start 6: small-arrays-3d-fp64

6: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "3d" "fp64"
6: Test timeout computed to be: 1500
6: zfp version 0.5.5 (May 5, 2019)
6: library version 85
6: CODEC version 5
6: data model LP64
6:
6: testing 3D array of doubles
6:   compress:   rate= 1                                                    OK
6:   decompress: rate= 1 [7.549e+01 > 5.210e+00]                           FAIL
6:   compress:   rate= 4                                                    OK
6:   decompress: rate= 4 [7.152e+01 > 2.002e-01]                           FAIL
6:   compress:   rate=16                                                    OK
6:   decompress: rate=16 [7.321e+01 > 3.338e-05]                           FAIL
6:   compress:   rate=64                                                    OK
6:   decompress: rate=64 [7.632e+01 > 0.000e+00]                           FAIL
6:   compress:   precision= 8 ratio= 16.319 [2008 != 1064]                 FAIL
6:   decompress: precision= 8                                               OK
6:   compress:   precision=16 ratio=  5.588 [5864 != 4624]                 FAIL
6:   decompress: precision=16                                               OK
6:   compress:   precision=32 ratio=  2.408 [13608 != 12808]               FAIL
6:   decompress: precision=32                                               OK
6:   compress:   tolerance=9.766e-04 ratio=  4.452 [7360 != 6128]          FAIL
6:   decompress: tolerance=9.766e-04 [7.552e+01 > 9.766e-04]               FAIL
6:   compress:   tolerance=4.441e-16 ratio=  1.204 [27216 != 27120]        FAIL
6:   decompress: tolerance=4.441e-16 [7.775e+01 > 4.441e-16]               FAIL
6:   compress:   tolerance=0.000e+00 ratio=  1.126 [29104 != 29192]        FAIL
6:   decompress: tolerance=0.000e+00 (7.347e+01 > 0)                        OK
6:   compress:   reversible ratio=  5.432 [6032 != 6128]                   FAIL
6:   decompress: reversible [reconstruction differs]                       FAIL
6:   construct:  [7.536e+01 > 3.338e-05]                                   FAIL
6:   update:     [7.915e+06 != 1.846e+00]                                  FAIL
6:
6: 16 test(s) failed
6/8 Test #6: small-arrays-3d-fp64 .............***Failed    0.02 sec
test 7
    Start 7: small-arrays-4d-fp32

7: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "4d" "fp32"
7: Test timeout computed to be: 1500
7: zfp version 0.5.5 (May 5, 2019)
7: library version 85
7: CODEC version 5
7: data model LP64
7:
7: testing 4D array of floats
7:   compress:   rate= 2                                                    OK
7:   decompress: rate= 2 [2.199e+01 > 1.373e+01]                           FAIL
7:   compress:   rate= 8                                                    OK
7:   decompress: rate= 8 [2.166e+01 > 6.633e-01]                           FAIL
7:   compress:   rate=32                                                    OK
7:   decompress: rate=32 [2.218e+01 > 0.000e+00]                           FAIL
7:   compress:   precision= 4 ratio=512.000 [32 != 64]                     FAIL
7:   decompress: precision= 4                                               OK
7:   compress:   precision= 8 ratio= 14.322 [1144 != 1760]                 FAIL
7:   decompress: precision= 8                                               OK
7:   compress:   precision=16 ratio=  3.127 [5240 != 5856]                 FAIL
7:   decompress: precision=16                                               OK
7:   compress:   tolerance=9.766e-04 ratio=  1.857 [8824 != 9440]          FAIL
7:   decompress: tolerance=9.766e-04 [2.223e+01 > 9.766e-04]               FAIL
7:   compress:   tolerance=2.384e-07 ratio=  1.220 [13432 != 14048]        FAIL
7:   decompress: tolerance=2.384e-07 [2.198e+01 > 2.384e-07]               FAIL
7:   compress:   tolerance=0.000e+00 ratio=  1.220 [13432 != 14048]        FAIL
7:   decompress: tolerance=0.000e+00 (2.191e+01 > 0)                        OK
7:   compress:   reversible ratio=  2.522 [6496 != 6864]                   FAIL
7:   decompress: reversible [reconstruction differs]                       FAIL
7:
7: 13 test(s) failed
7/8 Test #7: small-arrays-4d-fp32 .............***Failed    0.01 sec
test 8
    Start 8: small-arrays-4d-fp64

8: Test command: /home/khq.kitware.com/chuck.atkins/Code/zfp/build/master/bin/testzfp "small" "4d" "fp64"
8: Test timeout computed to be: 1500
8: zfp version 0.5.5 (May 5, 2019)
8: library version 85
8: CODEC version 5
8: data model LP64
8:
8: testing 4D array of doubles
8:   compress:   rate= 1                                                    OK
8:   decompress: rate= 1 [2.196e+01 > 1.016e+01]                           FAIL
8:   compress:   rate= 4                                                    OK
8:   decompress: rate= 4 [2.222e+01 > 8.985e+00]                           FAIL
8:   compress:   rate=16                                                    OK
8:   decompress: rate=16 [2.171e+01 > 3.312e-03]                           FAIL
8:   compress:   rate=64                                                    OK
8:   decompress: rate=64 [2.192e+01 > 0.000e+00]                           FAIL
8:   compress:   precision= 8 ratio= 28.643 [1144 != 1768]                 FAIL
8:   decompress: precision= 8                                               OK
8:   compress:   precision=16 ratio=  6.253 [5240 != 5864]                 FAIL
8:   decompress: precision=16                                               OK
8:   compress:   precision=32 ratio=  2.440 [13432 != 14056]               FAIL
8:   decompress: precision=32                                               OK
8:   compress:   tolerance=9.766e-04 ratio=  3.714 [8824 != 9448]          FAIL
8:   decompress: tolerance=9.766e-04 [2.217e+01 > 9.766e-04]               FAIL
8:   compress:   tolerance=4.441e-16 ratio=  1.099 [29816 != 30440]        FAIL
8:   decompress: tolerance=4.441e-16 [2.216e+01 > 4.441e-16]               FAIL
8:   compress:   tolerance=0.000e+00 ratio=  1.099 [29816 != 30440]        FAIL
8:   decompress: tolerance=0.000e+00 (2.216e+01 > 0)                        OK
8:   compress:   reversible ratio=  5.038 [6504 != 6872]                   FAIL
8:   decompress: reversible [reconstruction differs]                       FAIL
8:
8: 14 test(s) failed
8/8 Test #8: small-arrays-4d-fp64 .............***Failed    0.01 sec

25% tests passed, 6 tests failed out of 8

Total Test time (real) =   0.15 sec

The following tests FAILED:
	  3 - small-arrays-2d-fp32 (Failed)
	  4 - small-arrays-2d-fp64 (Failed)
	  5 - small-arrays-3d-fp32 (Failed)
	  6 - small-arrays-3d-fp64 (Failed)
	  7 - small-arrays-4d-fp32 (Failed)
	  8 - small-arrays-4d-fp64 (Failed)
Errors while running CTest
$

This also happens in both debug and release so you can safely assume it's not an optimization issue.

These seem to indicate significant failures beyond minor rounding errors.  For example, the compressed size differs by as much as a factor of two in fixed-precision mode.
Using PGI 20.1 I'm able to essentially reproduce these results (the floating-point errors are slightly different but compressed sizes are the same).  I'm also seeing a lot of valgrind errors that appear only in 2D and higher, which suggest to me a potential issue with strides (we've seen such issues before with incorrect sign extension).  I'll see if I can figure out what's going on.  We're really strapped for time right now as we're working on releasing 0.5.6, so unless I can figure this out quickly, it may be some time before I can dig deeper.

I've narrowed down the (a) bug to zfp's constant permutation tables getting corrupted.  These tables are 4^d entries long in d dimensions, so 4, 16, 64, and 256 for 1D-4D, and they store a permutation of [0, ..., 4^d-1] as unsigned characters.  See the 3D table, for instance.
Here's a printout of the actual (corrupted) table for 3D:
0 1 4 16 20 17 5 2 8 0 0 0 0 0 0 0 0 32 21 6 18 24 9 33 36 0 0 0 0 0 0 0 0 3 12 48 22 25 37 40 34 0 0 0 0 0 0 0 0 10 7 19 28 13 49 52 41 0 0 0 0 0 0 0

Only the first zero should be zero.  The other zeros occur in entries 9-16, 25-32, ..., 57-63.  The pattern is similar in 2D and 4D.  This table is initialized here: .

Some more info: the issue is caused by aligning these tables via __attribute__((aligned(256))).  Here's a code example that illustrates the bug.  Compile with -DALIGN to expose the bug.
#include <stdio.h>

#if ALIGN
  /* results in bug */
  #undef ALIGN
  #define ALIGN __attribute__((aligned(256)))
#else
  /* no bug */
  #define ALIGN
#endif

static const unsigned char perm_3[64] ALIGN = {
  0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07,
  0x08, 0x09, 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f,
  0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17,
  0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f,
  0x20, 0x21, 0x22, 0x23, 0x24, 0x25, 0x26, 0x27,
  0x28, 0x29, 0x2a, 0x2b, 0x2c, 0x2d, 0x2e, 0x2f,
  0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37,
  0x38, 0x39, 0x3a, 0x3b, 0x3c, 0x3d, 0x3e, 0x3f,
};

int main()
{
  int i;
  for (i = 0; i < 64; i++)
    printf("%d%c", (int)perm_3[i], i == 63 ? '\n' : ' ');
  return 0;
}

We have as output:
% pgcc-20.1 pgi-bug.c -o pgi-bug; ./pgi-bug
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
% pgcc-20.1 -DALIGN pgi-bug.c -o pgi-bug ; ./pgi-bug
0 1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 9 10 11 12 13 14 15 16 0 0 0 0 0 0 0 0 17 18 19 20 21 22 23 24 0 0 0 0 0 0 0 0 25 26 27 28 29 30 31 32 0 0 0 0 0 0 0

This works fine with PGI 18.5:
pgcc-18.5 -DALIGN pgi-bug.c -o pgi-bug ; ./pgi-bug
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

Chuck, we could "fix" this with appropriate ifdefs, but it would be better to get the compiler bug fixed.  Would you mind filing a bug report?

An alternative interim solution would be to compile zfp with ZFP_CACHE_LINE_SIZE=1, which should fix the problem.  We don't have a CMake macro for this, however, but we probably should.

FYI, LLNL has submitted a PGI bug report with tracking number SR1000947.
If you prefer, we can leave this issue open until we have added an option to build zfp with a given ZFP_CACHE_LINE_SIZE.  I'm not a big fan of writing conditional code to circumvent compiler bugs, so this is probably the best we can offer at the moment.

I don't like it either but the alternative is "doesn't work with the compiler you want" or every downstream project has to manually patch it.  Even with the cache line size option the build system should probably implement the workaround, something like:
# Workaround for PGI compiler bug
if(CMAKE_C_COMPILER_ID MATCHES "PGI|NVHPC")
  add_compile_definitions(zfp PRIVATE ZFP_CACHE_LINE_SIZE=1)
endif()

Note the addition of NVHPC, support for the newer nvidia based compilers as distinct from PGI is currently being added in upstream CMake.
Up to you how you want to deal with it, but yeah, it'd be nice to at least leave the issue open until it's resolved either in the build system or in the compiler.

I'm fine with addressing this in the build system.  I'll see if I can take care of this over the next few days on the develop branch.
By the way, tests 1-8 pass with ZFP_CACHE_LINE_SIZE=1, so hopefully this is the only bug.

I've pushed a fix on develop.  Tests are passing on AppVeyor but seem stuck in the queue on Travis.  @chuckatkins can you please test on your side and close this issue if it fixes your build problems?

Since PGI is working on our end and I've not heard any further complaints, I'm closing this issue.

Since PGI is working on our end and I've not heard any further complaints, I'm closing this issue.

In addition to the fix we made on develop, this compiler bug has been fixed in PGI 21.1.


Latitude and Longitude are reversed on return of getIntersection

The return values are reversed in utils.dart.

Forget it.  I figured out my problem.  DAMN turf.Position taking Longitude first!!

Hi, thanks for using the library. The library is still very new, so there might be some issues still.
If you encounter other bugs, please report them 😄
lat/lng/alt order is defined by the RFC standard for Geojson.


Fixed some CI bugs

Add errexit flag to test script to enable exit function when testing occurs an error.
Fixed some CI bugs.
Some typo errors.
Some syntax error that the variable name and the package name are repeated.

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage decreased (-0.03%) to 56.842% when pulling d7a291b329c116fb05d01656789c08e98b964722 on xxwjj:CI_bugs into fa8ba2a81ae60475ee403647868c3f8eb8f1c370 on opensds:development.


fix csv parser

Until now node-tmx-parser parse tmx that has csv with faulty process.
For example, If csv is "1, 1, 2, 2, 3, 3", node-tmx-parser create [1, 1, 2, 2, 3].

Thanks.


Adding a GoTrue example

I wanted to throw this out there, but should we add a GoTrue example that is separate from the Netlify one? It's a similar backend but doesn't have the Identity widget.
I wasn't sure if this was just too redundant or if it should be added as well.

This might be difficult - but a great idea. Both Netlify and Supabase use their own flavors of GoTrue (server and client) under the hood. But this is for a straight go-true client w/ some "other" goTrue based backed API.
One might have to implement a serverless function that issues a JWT. I'll have to think about how one might accomplish this.

Sounds good! I knew that they both used it, so definitely not a priority. But I saw it listed on the authentication docs and the cookbook, so it might be good to have an example. It might not actually provide extra value because it would look pretty plain.


[WIP] initial work on IIIF presentation API serilaizer

closes https://github.com/inveniosoftware/invenio-rdm-records/issues/603

closing for new PR.


add non-blocking operation, power management, transmit power control and more

This is a multi-feature commit. I am aware that this is not good style, but I had to combine most of the changes to make my use case work at all. The existing examples can still be build but I don't have a setup to test if if they still work.
Here is the list of the new features:

support floating point values for frequency (MHz) and baud rate (kbps)
support modulation type OOK
support disabling of the packet handling
support Manchester encoding
added function to select transmit power
support non-blocking transmit
support power management (idle mode)
added config callback for individual chip settings (e.g. antenna switch)
support MCU SAMD21
support pin 0
removed delay in turnOn() to allow non-blocking wakeup

In spite of all these changes the project defaults are unchanged. I "only" had to add several overloaded versions for setFrequency() and setBaudRate() make the examples build without error for the SAMD21.
Some  code issues remain:

Arduino library name may not have "Arduino" at beginning of name -> changed to class name Si4432
file name (si4432) does not match class name (Si4432) -> should be changed to Si4432 (or Si443x?)
definitions in header file not ordered by accessibility (public, protected, private) -> should be reordered
TX example does not directly build for SAMD21 as sprintf (line 24) requires txBuf to be signed char and sendPacket (line 27) requires txBuf to be unsigned char -> add explicit cast

A working use case for the new features can be found in the project Solar DHT, method SolarDHT::setupRadio.

👍


[BEAM-12419] Deadline should be reset for each gRPC call.

getState() in waitForTerminalState() is invoked multiple times and deadline should be reset each time since it is an absolute number.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@apilloud Can you help take a look ?

Run Java Spark PortableValidatesRunner Batch

Run XVR_Spark PostCommit

Run XVR_Spark3 PostCommit

Run Java Spark PortableValidatesRunner Batch

I did notice that Spark PVR Streaming tests have been broken into two tests in https://github.com/apache/beam/pull/14483 but not for Batch tests, are we going to apply the same improvement for batch mode tests ?

I'm not sure. That is probably a question for @ibzib

LGTM, thanks for fixing this.

I did notice that Spark PVR Streaming tests have been broken into two tests in #14483 but not for Batch tests, are we going to apply the same improvement for batch mode tests ?

I don't think there's much of a reason to separate them, since unlike the streaming tests both Spark versions consistently pass tests (while in streaming, Spark 3 is much less flaky than Spark 2, for unknown reasons).


MiqProductFeature.count spec that won't require contant updating

Purpose or Intent
expected_feature_count is constant source of rebasing, merge conflicts and silent wrong merging (when 2 people increment by same #).
Last I heard on gitter, many [weasel words] dislike it, nobody knows [citation needed] what exactly it's testing, but it was suggested that it's useful to catch a hypotetical [non-neutral POV] seeding breakdown that would load 0 or very few features.  This PR still tests that.
Today I had to mergetool it twice again and figured maybe I someone with merge powers will tempted to press that green merge button before others notice :trollface:
(Imagine it being green more often from this day forward.  Quicker, easier, more seductive...  ↴  :tada:)
@miq-bot label developer, enhancement, darga/yes
It must be darga/yes, otherwise all future feature-adding commits will fail tests once backported.
(Ironically, this PR doesn't merge cleanly into darga but only because 1034 != 1075.)

@miq-bot add-label developer, enhancement, darga/yes

nobody knows [citation needed] what exactly it's testing

I do... it's testing that...

the structure of the deployment file is correct (not just good yaml, but that the feature itself was added correctly)

If you add 2 features, you should expect that this went up by 2, not 1 or 0

the change does not add a new key that duplicates an existing key
reseeding doesn't duplicate records

(These are all things that have happened)

I prefer the direction that @imtayadeway is going in #9924.  At the very least it verifies that each section is structured correctly, which should be sufficient to know that the feature that was added was correct.  I think the duplicate test would handle if someone added a key with the same thing twice, otherwise we will need that in #9924 .

Closing in favor of #9924


Bug with minOrderQty + Prices

Description
We have prices (rules) not beginning with 50.
This result in an error in storefront:

Problem: the prices is still collected with quantity of 1, no matter what MinOrderQuantity is definied or where the prices are starting.
Possible Solution
Additional context

This might be the same as this issue https://github.com/shopware/platform/issues/562 , Please vote the shopware issue to get it fixed :)

Duplicate of #562


Don't write signal for zero valued timeline semaphores

The Vulkan spec says in VkSemaphoreSignalInfo:
value must have a value greater than the current value of the semaphore.
The initial value is zero, so don't signal zero-valued semaphores.

Author ishitatsuyuki not on autobuild list. Waiting for curator authorization before starting CI build.

CI gfxreconstruct build queued with queue ID 36933.

CI gfxreconstruct build # 2233 running.

CI gfxreconstruct build # 2233 passed.

Author ishitatsuyuki not on autobuild list. Waiting for curator authorization before starting CI build.

I figure after this PR every Vulkan capture will likely be shorter.

Violating the signal "greater" constraint results in an immediate device loss on Mesa so this probably hasn't been encountered before. As with other PRs of mine, this is a case that commonly happens with vkd3d though.


Lokalise: Translations update

This pull request was initiated by Lokalise (user Justin Bassett) at 2019-12-18 23:34:16

Hello @balloob,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

eff5d0bd564f4ecdf014e672eb3b3d4f3055f9b6 - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.
b8f1828432cf1c331e1dfd81ff23bc83910b517b - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.
2d27ef6ad0300d97e08f43fd2f18e024659e302e - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.
06240f5a2a7b5b4ff09c3531db052c926c53d1ac - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.
f9eff42b63c42dc0b77e0ef8523f2468fb06ee30 - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.
7e6358e521374daa9b441b920d89a303a58db309 - This commit has something that looks like an email address (support@lokalise.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Please Close


Add otlphttp to the traces pipeline

Add the missing otlphttp exporter to the traces pipeline

/lgtm

/lgtm


Clean up all integration tests and standardize the creation of schema, table config and segments

Create schema and table config based on the settings in the BaseClusterIntegrationTest
Remove the methods with huge arguments list
Always use the schema and table config in the cluster to create the segments
Simplify the cluster setup methods

The following integration tests are removed:

DefaultCommitterRealtimeIntegrationTest: Merged into LLCRealtimeClusterIntegrationTest
PinotURIUploadIntegrationTest: Already covered in the module-level FileUploadDownloadClientTest

ControllerPeriodicTasksIntegrationTest is refactored (was not running before because the wrong test name '*Tests')
RealtimeStressTest is removed as it is the same as BenchmarkRealtimeConsumptionSpeed

Codecov Report

Merging #5385 into master will increase coverage by 0.16%.
The diff coverage is 73.49%.

@@            Coverage Diff             @@
##           master    #5385      +/-   ##
==========================================
+ Coverage   66.44%   66.61%   +0.16%
==========================================
  Files        1075     1083       +8
  Lines       54773    55319     +546
  Branches     8168     8306     +138
==========================================
+ Hits        36396    36851     +455
- Misses      15700    15740      +40
- Partials     2677     2728      +51

Impacted Files
Coverage Δ

...er/api/resources/LLCSegmentCompletionHandlers.java
35.17% <0.00%> (-26.64%)
:arrow_down:

...apache/pinot/controller/api/upload/ZKOperator.java
75.82% <0.00%> (-1.10%)
:arrow_down:

...data/manager/realtime/DefaultSegmentCommitter.java
80.00% <ø> (ø)

...e/data/manager/realtime/SplitSegmentCommitter.java
0.00% <ø> (-63.64%)
:arrow_down:

...ation/function/AggregationFunctionVisitorBase.java
0.00% <0.00%> (ø)

...ot/core/query/reduce/DistinctDataTableReducer.java
71.64% <0.00%> (-1.09%)
:arrow_down:

.../org/apache/pinot/core/startree/StarTreeUtils.java
80.76% <ø> (-0.32%)
:arrow_down:

...he/pinot/spi/config/table/StarTreeIndexConfig.java
0.00% <ø> (ø)

...main/java/org/apache/pinot/spi/data/FieldSpec.java
85.60% <0.00%> (-0.66%)
:arrow_down:

.../java/org/apache/pinot/spi/data/TimeFieldSpec.java
90.69% <ø> (+1.80%)
:arrow_up:

... and 190 more

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 04e70da...c218dfc. Read the comment docs.


[2.0-wip] Gradient

@markdotto : as you mentioned in an earlier topic the previous days, i'm setting a new topic now for the styling of the accordion. Since pure gray (the way it currently is) is nowhere else found in the main bootstrap's theme, could the accordion take the css style of breadcrumbs? Or maybe some other solid one.
Plz close this when done.
Thanks

I've removed the background color and replaced it with border instead. That's all I'll do on this one for now—the goal is to provide base styles for components like these, not the final product. If you want a gradient, feel free to add one yourself.


Wrong navbar text and link colors

🐞 Problem
After releasing v0.3.0, the documentation got updated. Although the process succeeded, it looks like the navigation bar is showing different colors for the text and links on it:

Link highlight is showing a blue or purple color instead of the Ansys Gold one.

Pinging here @Revathyvenugopal162.


[WIP] Example file for docker compose and k8s

Motivation
More convenience to start with docker.
Modification

Add compose.yml for serving as service.
Add k8s example file.
Update README.md for corresponding changes.

Could you revert your changes to the entry points?

@LucienShui May you rebase the latest main branch? Thanks. ref https://github.com/sgl-project/sglang/pull/1033

cc @LucienShui
ref cmd
# first sync fork's main

# next
git checkout main
git pull
git checkout  chore/docker_entrypoint
git rebase main
git push -f

Hi @LucienShui I noticed that you updated your PR. Have the compose and k8s conf been locally verified?

Hi @LucienShui I noticed that you updated your PR. Have the compose and k8s conf been locally verified?

Yes, both compose and k8s have been verified locally, but I want to simplify these files as much as possible to make them more beginner-friendly so I added [WIP] in PR's title.
Feel free to merge it now but it would be better after I make more changes.
BTW, I need to work during the day so I only have time in the evening, my timezone is UTC+8.

Got it. Thanks!

This PR is ready to merge, thanks for your time and patience!

@LucienShui Thanks for the contribution!


[Doc Improvement] [Feedback URL update]

Docs Build status updates of commit 1fa3dba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6bc4dd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/docfx.json
:white_check_mark:Succeeded

msteams-platform/toolkit/accounts.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/accounts.md
91
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/accounts.md
91
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Design FeedBack in Generate Branch Threads page.

Any feedback would be great! 🔥

Change like this.


support tapping background to dismiss

Hey @gh123man, this project works great in my app.
One thing I was looking for is to support tapping on the background to dismiss the view. Basically, if you tap outside of the image, I'd like to be able to dismiss the view.

Hey!
Glad you like it 😄
You should be able to implement this with the subview.
I just tried this and it looks like it works:

struct SimpleExample: View {

    @State var data = [
        ...
    ]

    @State var show = false

    var body: some View {
        VStack {
            Button("Show") {
                show.toggle()
            }
        }
        .fullScreenCover(isPresented: $show) {
            LazyPager(data: data) { element in
                VStack {
                    Image(element)
                        .resizable()
                        .aspectRatio(contentMode: .fit)
                        .onTapGesture {
                            print("tap image")
                        }
                }
                .frame(maxWidth: .infinity, maxHeight: .infinity)
                .contentShape(Rectangle())
                .onTapGesture {
                    show.toggle()
                    print("tap background")
                }
            }
        }
    }
}

Let me know if this works.
Also - Hello from Boston!

Amazing! This works great, thanks so much for the help!


Add Protien, Fats , Carbs and Fiber Consumption, Similar to Daily Calorie, Remove Excercise part

Also Updated the firebase firestore database to capture all the meal and save it
Also to get from the database code.
Also changed the UI to add meal and calculate protien, carbs and fats.

Homepage

View history

While adding food to a particular meal


CIS Scan - Schedule scan report is seen in "Creating" state when a schedule scan is run on cluster with k8s version less than 1.15

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Bring up a cluster with k8s 1.13 in rancher:v2.2.10
Upgrade rancher to master-head latest
Edit cluster --> Advanced options --> Enable Schedule CIS scan --> Set it to True.
Set an appropriate cron time.
Click on Save.

Actual Result:

Schedule scan is started on the cluster. Report is stuck in "Creating" State

But error is seen in the logs . Logs:

2020/03/23 22:30:30 [DEBUG] cisScanHandler: checking if cluster version v1.13.0 is less than min version: 1.15
2020/03/23 22:30:30 [ERROR] ClusterScanController c-pdbvf/ss-cis-1585002120000225789 [cisScanHandler] failed with : minimum k8s version 1.15 needed for running cis scan

Expected Result:
User should NOT be allowed to enable a schedule scan OR when user enables schedule scan, it should not be taken into consideration for a cluster with k8s version < 1.13
Other details that may be helpful:
Related to issue: https://github.com/rancher/rancher/issues/25996
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head commit id: 07f6b9a33
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke
Kubernetes version (use kubectl version):

1.13

Verified on master-head commit id: 759736e81

Upgrade cluster setup from 2.2.10 to master-head
User is not able to Edit cluster and enabled Schedule CIS scan

Edit cluster through API: Give in value for scheduledClusterScan

"scheduledClusterScan": {
"enabled": true,
"scanConfig": {
"cisScanConfig": {
"debugMaster": false,
"debugWorker": false,
"overrideBenchmarkVersion": "rke-cis-1.4",
"profile": "permissive",
"type": "/v3/schemas/cisScanConfig"
},
"type": "/v3/schemas/clusterScanConfig"
},
"scheduleConfig": {
"cronSchedule": "0 0 * * *",
"retention": 24,
"type": "/v3/schemas/scheduledClusterScanConfig"
},
"type": "/v3/schemas/scheduledClusterScan"
},

Error seen:
{
"baseType": "error",
"code": "InvalidBodyContent",
"message": "minimum k8s version 1.15 needed for running cis scan",
"status": 422,
"type": "error"
}


dask==2024.12 tests hang on CI

https://github.com/data-apis/array-api-compat/actions/runs/12174770255/job/33957310078?pr=208 runs for 3 hrs already, stuck at
array_api_tests/test_creation_functions.py::test_empty_like PASSED       [  3%]

gh-211 added a skip for an offending test, so no need to track this separately.


Use java.time.Instant to get micros accurate timestamps

fall back to System.currentTimeMillis() for Java 7

Codecov Report

Merging #261 into master will increase coverage by <.01%.
The diff coverage is 77.27%.

@@             Coverage Diff              @@
##             master     #261      +/-   ##
============================================
+ Coverage     72.96%   72.97%   +<.01%
  Complexity     1134     1134
============================================
  Files           121      122       +1
  Lines          4221     4240      +19
  Branches        422      422
============================================
+ Hits           3080     3094      +14
- Misses          943      948       +5
  Partials        198      198

Impacted Files
Coverage Δ
Complexity Δ

...o/elastic/apm/impl/transaction/EpochTickClock.java
100% <100%> (ø)
7 <2> (ø)
:arrow_down:

...a/co/elastic/apm/impl/transaction/SystemClock.java
73.68% <73.68%> (ø)
0 <0> (?)

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 7da2e91...053911f. Read the comment docs.

Sorry for not laying out the motivation of this change. With the current approach, the timestamp can be up to 1ms off, as it just uses System.currentTimeMillis() * 1_000 for the transaction timestamp.
This can lead to misaligned spans in the UI:

Go is using an accurate epoch micros timestamp but the Java agent sort of truncates the timestamp to milliseconds. When making calls across different hosts, the clocks can be misaligned by serveral milliseconds and the UI has to do compensating actions anyway, but at least when making calls on the same host, the timestamps should be consistent.

Yeah, only read through the conversation today, so removed the comment on "thinking it is too early to use Java 8 stuff" :)


UTF-8 support

Snowman currently sets the charset to utf-8, but adventures does not.  The one-liner is here:
https://github.com/videlais/snowman/blob/master/src/index.ejs

+1


C++ helloworld greeter_server too slow

Hello.
I'm working with C++ examples helloworld, behchmarking it using ghz.
Server responds only about 13k requests per second.
It's not enought, how can I achieve move performance out of servers, thank you.

Please take a look at https://grpc.io/docs/guides/performance/


fix(healthcheck) start a single timer for all workers

Before creating a new timer, check if this Nginx instance is already running an active health check in any worker.
Fixes: Kong/kong#6788

This change seems ok to me, but the tests are red.

I do not think this is correct. We need to bring back the get_periodic_lock function that dissapeared from the code (haven't checked when and where). But each HC needs one for healthy and one for unhealthy. Please check history.
The lock is an SHM key created with TTL == interval time, every worker tries to get /set that key, on success, they run the HC, on failure (already exists) another worker is already running the HC, and this worker should skip.

Supersededby #67