Centos Linux 7.9: 7.9.2009: Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found

Prerequisites

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

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
$atom
$ cat ~/.atom/nohup.out
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/share/atom/resources/app.asar.unpacked/node_modules/nslog/build/Release/nslog.node)
at process.func (electron/js2c/asar.js:138:31)
at process.func [as dlopen] (electron/js2c/asar.js:138:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
at Object.func (electron/js2c/asar.js:138:31)
at Object.func [as .node] (electron/js2c/asar.js:147:18)
at Module.load (internal/modules/cjs/loader.js:645:32)
at Function.Module._load (internal/modules/cjs/loader.js:560:12)
at Module.require (internal/modules/cjs/loader.js:685:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (/usr/share/atom/resources/app.asar/node_modules/nslog/lib/nslog.js:5:11)
Steps to Reproduce
Run atom from terminal or try to open any file with atom
Expected behavior:
Open atom
Actual behavior:
Nothing open and throw error in log as below :
$ cat ~/.atom/nohup.out
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/share/atom/resources/app.asar.unpacked/node_modules/nslog/build/Release/nslog.node)
at process.func (electron/js2c/asar.js:138:31)
at process.func [as dlopen] (electron/js2c/asar.js:138:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
at Object.func (electron/js2c/asar.js:138:31)
at Object.func [as .node] (electron/js2c/asar.js:147:18)
at Module.load (internal/modules/cjs/loader.js:645:32)
at Function.Module._load (internal/modules/cjs/loader.js:560:12)
at Module.require (internal/modules/cjs/loader.js:685:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (/usr/share/atom/resources/app.asar/node_modules/nslog/lib/nslog.js:5:11)
Reproduces how often:
always!
Versions

$ atom --version
Atom    : 1.53.0
Electron: 6.1.12
Chrome  : 76.0.3809.146
Node    : 12.4.0
$ apm --version
internal/modules/cjs/loader.js:815
return process.dlopen(module, path.toNamespacedPath(filename));
^
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/share/atom/resources/app/apm/node_modules/git-utils/build/Release/git.node)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:815:18)
at Module.load (internal/modules/cjs/loader.js:641:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Module.require (internal/modules/cjs/loader.js:681:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (/usr/share/atom/resources/app/apm/node_modules/git-utils/src/git.js:3:22)
at Module._compile (internal/modules/cjs/loader.js:774:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:785:10)
at Module.load (internal/modules/cjs/loader.js:641:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
Additional Information
None

Confirmed, latest atom fails for me too.
I had to reverd back to version 1.46 before atom could start.

I'm seeing this issue as well.
Atom    : 1.56.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1

Still broken in 1.57.0.
Atom    : 1.57.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1
$ cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)
$ cat .atom/nohup.out
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/share/atom/resources/app.asar.unpacked/node_modules/nslog/build/Release/nslog.node)
at process.func [as dlopen] (electron/js2c/asar.js:140:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1034:18)
at Object.func [as .node] (electron/js2c/asar.js:149:18)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Module._load (internal/modules/cjs/loader.js:727:14)
at Function.Module._load (electron/js2c/asar.js:769:28)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/share/atom/resources/app.asar/node_modules/nslog/lib/nslog.js:5:11)
at Object. (/usr/share/atom/resources/app.asar/node_modules/nslog/lib/nslog.js:15:4)

I have run into this as well using RHEL7.
The only work around I've found so far is to  downgrade to Atom 1.51.0.

I'm still seeing this same issue on CentOS 7.9 with Atom versions 1.49.0 and 1.51.0. Is there any resolution or workaround for this issue?

1.58.0 also has this issue.  Tried setting LD_LIBRARY_PATH to a locally installed libstdc++.so.6.0.25 (no sudo) and no version of atom will start.  Workaround is use 1.51.0 and keep closing the bug window.


Invalid prop: type check failed for prop "customButtons". Expected Function, got Array

Hello.
I faced with this warning if I pass custom buttons this way:
{
hide:false,
icon:"settings",
onclick: function () {
console.log('btn pressed')
}
}
I got prop warning "Expected Function, got Array "
As far as know in vuejs-way to pass some state from child to parent is emit\v-on. How can I pass some emit from these custom buttons via the 'onclick' function in buttons array?
Thank you.

Please provide more code, preferably in a codesandbox.


Web Chat speaks text value instead of speak property in channel data

Version
Web Chat v4.5.0 (Full) CDN
Description
Adding the speak property to an activity's channel data should make Web Chat speak the corresponding value; however, Web Chat is speaking the text value instead.
To Reproduce
await context.sendActivity({
    text: 'Web Chat should not speak this',
    channelData: {
        speak : 'Web Chat should speak this'
    }
});

Steps to reproduce the behavior:

Pass the webSpeechPonyfillFactory as a prop to Web Chat.
Send an activity to the Web Chat conversation that has the speak property set in the activity's channel data.
Web Chat will speak the text value and not the speak value.

Expected behavior
Web Chat should speak the value in the activity's channel data and not the text value.
Additional context
We should also investigate how Web Chat handles the speak attribute being added to the activity and the activity's channel data.
await context.sendActivity({
    text: 'Web Chat should not speak this',
    speak: 'Web Chat is speaking this',
    channelData: {
        speak : 'but maybe it should speak this instead'
    }
});

[Bug]

After testing older versions of Web Chat, I appear to be wrong. The speak property in the channel data acts as a boolean value and has no effect on what is actually spoken. If the developer wants Web Chat to speak without the user having to speak to it first, they should set the speak attribute to true. Not sure if this is documented anywhere.
await context.sendActivity({
    text: 'Web Chat should speak this',
    channelData: {
        speak : true
    }
});

This also appears to work correctly when the speak attribute in the activity is set - Web Chat is speaking the activity's speak attribute instead of the  text attribute.
await context.sendActivity({
    text: 'Web Chat should not speak this',
    speak: 'Web Chat should speak this',
    channelData: {
        speak : true
    }
});
}


Disable email notifications

I get a lot of email notifications from Travis that are just noise. This disables email notifications. If you like getting emails we can enable them selectively: https://docs.travis-ci.com/user/notifications#Configuring-email-notifications
Talked to @helfer who is for this change.

Agreed!


Line 101 and Line 111 should be conditional

Line 101 should be
The Conditional AND operator && also computes the logical AND of its operands, but always evaluates both operands.
instead of
The Logical AND operator & also computes the logical AND of its operands, but always evaluates both operands.
Line 111 should be
The Conditional OR operator || also computes the logical OR of its operands, but always evaluates both operands.
instead of
The Logical OR operator | also computes the logical OR of its operands, but always evaluates both operands.
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Line 101 should be The Conditional AND operator && also computes the logical AND of its operands, but always evaluates both operands. instead of The Logical AND operator & also computes the logical AND of its operands, but always evaluates both operands. Line 111 should be The Conditional OR operator || also computes the logical OR of its operands, but always evaluates both operands. instead of The Logical OR operator | also computes the logical OR of its operands, but always evaluates both operands.
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Please ignored. I guess I am confused.

Just ignore my pull request. I bet I was confused.

Thanks for adding the additional comments @chanmmn
I'll close this, as the current article is correct.


Roadmap to v1.0 — Silicon Beach 🏝

Silicon Beach 🏝
If you want to see our whole v1.0 roadmap, including the actionable items, check out the projects here.
The Stacks Toolkit
Buddy, the Stacks CLI, is designed to help navigate you. The following commands are your helper & guide to the framework.
buddy --version # get the Stacks version
buddy --help # view help menu
# please note: you may suffix any command with the
# `command --help` flag to review the help menu

buddy install # installs your dependencies
buddy fresh # fresh reinstall of all deps
buddy clean # removes all your deps

buddy update # auto-update deps & the Stacks framework
buddy update:dependencies # auto-update deps & the Stacks framework
buddy update:framework # auto-update deps & the Stacks framework
buddy update:package-manager # auto-update deps & the Stacks framework
buddy update:search-engine # auto-updates Meilisearch
buddy update:node # update to latest project-defined node version
buddy update:all # update Node, package manager, framework, dependencies

# if you need any more info on any command listed here, you may suffix
# any of them via the "help option", i.e. `buddy ... --help`

buddy dev # start one of the dev servers (components, functions, pages, or docs)
buddy dev:components # start local playground dev server
buddy dev:desktop # starts the Desktop playground
buddy dev:pages # start local playground pages dev server
buddy dev:functions # stub local the functions
buddy dev:docs # start local docs dev server
buddy development # `buddy dev` alias

# for Laravel users, `serve` may be a more familiar command. Hence, we aliased it:
buddy serve
buddy serve:components
buddy serve:pages
buddy serve:functions
buddy serve:docs

# building for production (e.g. AWS, Google Cloud, npm, Vercel, Netlify, et al.)
buddy build # select a specific build (follow CLI prompts)
buddy build:desktop # build Desktop app
buddy build:components # build Vue component library & Web Component library
buddy build:vue-components # build Vue 2 & 3-ready Component library
buddy build:web-components # build framework agnostic Web Component library (i.e. Custom Elements)
buddy build:functions # build function library
buddy build:pages # build SSG pages
buddy build:all # build all your code

# `buddy build` aliases
buddy prod
buddy prod:components
buddy prod:vue-components
buddy prod:web-components
buddy prod:functions
buddy prod:pages
buddy prod:all
buddy production # `buddy prod` alias

# sets your application key
buddy key:generate

buddy make:stack project
buddy make:component HelloWorld
buddy make:function hello-world
buddy make:page hello-world
buddy make:lang de
buddy make:notification welcome-email
buddy make:database cars
buddy make:table brands
buddy make:migration create_cars_table
buddy make:factory cars
buddy make:seed cars

buddy lint # runs linter
buddy lint:fix # runs linter and fixes issues

buddy commit # follow CLI prompts for committing staged changes
buddy release # creates the releases for the stack & triggers the Release Action (workflow)
buddy changelog # generates CHANGELOG.md

# when deploying your app/s to a remote server or cloud provider
buddy deploy
buddy deploy:docs
buddy deploy:functions
buddy deploy:pages
buddy deploy:all

# select the example to run (follow CLI prompts)
buddy example
buddy example:vue
buddy example:web-components

# you likely won't need to run these commands as they are auto-triggered, but they are available
buddy generate
buddy generate:entries
buddy generate:vue-compat
buddy generate:web-types
buddy generate:vscode-custom-data
buddy generate:ide-helpers
buddy generate:component-meta
buddy generate:all

# generates your application key
buddy key:generate

# generate your TypeScript declarations
buddy types:generate
buddy types:fix

# test your stack
buddy test # runs test suite
buddy test:unit # runs unit tests
buddy test:e2e # runs e2e tests
buddy test:coverage # runs test coverage
buddy test:types # runs typecheck

# optional: the CLI may be triggered in any
# of the following syntax:
stx fresh
buddy fresh
bud fresh
buddy fresh
pnpm stx fresh
pnpm buddy fresh
pnpm buddy fresh
pnpm fresh
pnpm run fresh
pnpm run buddy fresh

Buddy is friendly but he may bark with notes
In a few releases, Stacks will be beta-ready. Before then, Stacks will have official documentation launched.
Much more to come/to be documented!
Stay tuned.

A more detailed breakdown of what specific development chunks need to get accomplished:
# npx artisan make:component HelloWorld # bootstraps HelloWorld component
# npx artisan make:function hello-world # bootstraps hello-world.ts function
# npx artisan make:stack hello-world # bootstraps component & function

# npx artisan install # installs all deps
# npx artisan fresh # cleans & reinstalls all deps

# npx artisan dev # stubs everything & and starts smart dev server
# npx artisan dev:components # stubs components
# npx artisan dev:functions # stubs functions
# npx artisan dev:elements # stubs components
# npx artisan dev:playground # starts dev server & opens Stacks playground
# npx artisan dev:docs # starts docs dev server & opens docs in browser
# npx artisan dev:stacks # stubs the framework
# npx artisan stubs # stubs everything

# npx artisan build # runs typecheck & builds the project
# npx artisan build:components # builds component library
# npx artisan build:functions # builds function library
# npx artisan build:elements # builds web components/custom elements library
# npx artisan build:playground # builds the playground
# npx artisan build:docs # builds the docs
# npx artisan build:stacks # builds the framework

# npx artisan deploy:functions # zero-config: Netlify, Vercel, AWS, Cloudflare (and more)
# npx artisan deploy:docs # zero-config: Netlify & Vercel
# npx artisan deploy:playground # zero-config: Netlify & Vercel

# npx artisan commit # GUI for git commit
# npx artisan release # GUI for releasing the libraries
# npx artisan changelog # automatically generate changelog

# npx artisan lint # lints the codebase
# npx artisan lint:fix # auto-fixes lint errors
# npx artisan typecheck # runs typecheck
# npx artisan types:fix # wip

# npx artisan test # runs whole test suite
# npx artisan test:e2e # runs e2e tests
# npx artisan test:unit # runs unit tests
# npx artisan test:coverage # runs test coverage

# npx artisan example # run an example script (follow prompts)
# npx artisan size # wip
# npx artisan preinstall # the preinstall hook that ensures proper node & pnpm versions are installed
# npx artisan postinstall # the postinstall hook that ensures git hooks are configured after initial install

Lol I forgot to update the above. Most is done, but slowly wrapping it up now for the initial official release & will get this post updated as well shortly.

not ganna lie i think long term its ganna be bad to use artisan as there is already another big project using it. this project definitely has a good start and potential however i think the cli should probably use stacks at the command. how is anyone going to debug commands or arguments on the cli when another project already uses this namespace?

https://github.com/stacksjs/stacks/milestone/1


Add missing commas, fix typos

I did not try to correct English - as I'm not a good writer myself.
The commas seem to be necessary, however, to comprehend the sentences.

This change is

Hey there, can you rebase?  Otherwise, LGTM

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

docs/user-guide/horizontal-pod-autoscaling/index.md, line 123 [r1] (raw file):

In this case, if there are 4 pods running and each of them reports qps metric to be equal to 15, HPA will start 2 additional pods so there will be 6 pods in total. If there are multiple metrics passed in the annotation or CPU is configured as well then HPA will use the biggest

"In this case, if there are four pods running and each pods reports a QPS metric of 15 or higher, horizontal pod autoscaling will start two additional pods (for a total of six pods running).
If you specify multiple metrics in your annotation or if you set a target CPU utilization, horizontal pod autoscaling will scale to according to the metric that requires the highest number of replicas.

docs/user-guide/horizontal-pod-autoscaling/index.md, line 126 [r1] (raw file):

number of replicas that comes from the calculations.

At this moment, even if CPU utilization target is not specified, a default of 80% will be used.

If you do not specify a target for CPU utilization, Kubernetes defaults to an 80% utilization threshold for horizontal pod autoscaling.

docs/user-guide/horizontal-pod-autoscaling/index.md, line 127 [r1] (raw file):

At this moment, even if CPU utilization target is not specified, a default of 80% will be used.
To calculate number of desired replicas based only on custom metrics, CPU utilization

If you want to ensure that horizontal pod autoscaling calculates the number of required replicas based only on custom metrics, you should set the CPU utilization target to a very large value (such as 100000%). As this level of CPU utilization isn't possible, horizontal pod autoscaling will calculate based only on the custom metrics (and min/max limits).

Comments from Reviewable

Thanks for the review!
I rebased this branch on master, added a commit to update the sentences, and force pushed this branch.

Thanks! I accidentally had a typo in one of my suggested edits, though; I'll leave a review comment. Sorry about that! As soon as it's fixed we can merge.

Review status: 0 of 1 files reviewed at latest revision, 4 unresolved discussions.

docs/user-guide/horizontal-pod-autoscaling/index.md, line 123 [r2] (raw file):

In this case, if there are four pods running and each pods reports a QPS metric of 15 or higher, horizontal pod autoscaling will start two additional pods (for a total of six pods running).

each pods -> each pod

Comments from Reviewable

No you are good! I should have done more than copy & paste.
The typo is fixed. Please review this one more time 🙇

Docs LGTM! Thanks; I'll go ahead and merge this in.


Introduce JobMixins

This will introduce JobMixins module for mixins with MixinInOutPaths for Job classes.
ONE-vscode-DCO-1.0-Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

From draft #14


Please push the reset password fix to NPM.

The issue where the password reset requires the 'passwordCurrent' field is fixed in the repo but I belive the changes haven't been pushed to npm.

Hey @IrtazaSafi, sorry for the delayed response. I just downloaded the latest package from npm and it contains the ? in question 😄 . Could you check again? Maybe I'm doing something wrong. Thanks!

Hey. The current code has that block however, the backend still fails when I try to reset the password with the user 'logged out'. It works with the user 'logged in'. This is the frontend error that I get:

On the backend I get
Processing by DeviseTokenAuth::RegistrationsController#update as JSON
Parameters: {"password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "reset_password_token"=>"[FILTERED]", "registration"=>{"password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "reset_password_token"=>"[FILTERED]"}}
Unpermitted parameters: reset_password_token, registration
Completed 404 Not Found in 1ms (Views: 0.2ms | ActiveRecord: 0.0ms)
Do you have any ideas why this happening?

I'm also getting same error. Checked my package and passwordCurrent is not required. @IrtazaSafi did you find any solution for this?

Did anybody find a way to fix this? I'm having this error now.

Also getting exact same error. Reset password flow only works if the user is logged in, exactly as @IrtazaSafi reported above.

This is how I managed to reset when the user is logged out:
https://paste.ofcode.org/RgZYFBZunbKUJMFi5u3AFL

@IrtazaSafi Thanks for posting that, which is almost identical to the code I already have, which only works if the user is logged in.
resetData does not look correct - the updatePassword method of the library accepts type UpdatePasswordData which looks like this:
export interface UpdatePasswordData {
    password: string;
    passwordConfirmation: string;
    passwordCurrent?: string;
    userType?: string;
    resetPasswordToken?: string;
}

It seems odd to me that you also have 'token' as another property, with the same params['token'] in it. I am betting that Rails is just ignoring that parameter entirely.
Also I noticed in the documentation for this method it specifically says 'logged in user':
.updatePassword() Updates the password for the logged in user. updatePassword({password: string, passwordConfirmation: string, passwordCurrent: string, userType?: string, resetPasswordToken?: string}): Observable
Are you 100% certain that users who are logged out can reset their password in your app? If you manually delete localStorage (so the current valid token is gone) and then call this, you should get the same result you reported before and that I still get - user not found.

As an example here is my code after I've called reset.
This is the form - email field is disabled so user cannot change it and resetPasswordToken is hidden.
  private buildForm(): void {
    this.form = this.fb.group({
      'email': [{ value: this._activatedRoute.snapshot.queryParams['uid'], disabled: true }],
      'password': ['', Validators.required],
      'passwordConfirmation': ['', Validators.required],
      'resetPasswordToken': [this._activatedRoute.snapshot.queryParams['token']]
    });
  }

And this is what happens when the user clicks submit:

  public onSubmit(data: UpdatePasswordData): void {
    if (this.form.valid) {
      this._authService.updatePassword(data).subscribe(
        result => {
          if (result.status === 200) {
            this._userService.user = result.json().data;
            this._toastrService.success('Your password was reset!', 'Success');
            this.slowNavigate('pages/dashboard');
          };
        },
        error => {
          this._apiErrorService.notifyErrors(error.json());
        }
      );
    };
  }

I think (but am not sure) that previously my resetPasswordCallback may have been wrong. I've just been through everything again and the only code I changed was that (so that the the redirect_url sent to the api is correct):
export const environment = {
  production: false,
  token_auth_config: {
    apiHost: 'http://localhost:3000',
    apiBase: 'http://localhost:3000/api',
    registerAccountCallback: 'http://localhost:4200/login',
    signInRedirect: 'login',
    resetPasswordCallback: 'http://localhost:4200/reset'
  }
};

resetPasswordCallback defaults to window.location.href - so will almost certainly be incorrect for most people.
Now when resetPassword is called the data sent is:
{
email<EMAIL_ADDRESS>
redirect_url: "http://localhost:4200/reset"
}

It works for users that are logged out.


Add more allowable ContentTypes or make validation optional?

https://github.com/stac-utils/stac-asset/blob/20a5d5ab8669867d3e5a7601072a501cde74e89d/src/stac_asset/validate.py#L3-L5
I was just this library out with a maxar item https://api.maxar.com/discovery/v1/catalogs/imagery/collections/wv01/items/102001008EC5AC00
But hit validation errors on the mime-types trying to download assets, which are almost the same. I don't think the asset type are standardized in STAC validation, but could be wrong! I thought about adding them to ALLOWABLE_PAIRS, but maybe just skipping this check altogether would be better?
DownloadError: ContentTypeError: the actual content type does not match the expected: actual=application/json, expected=application/geo+json
ContentTypeError: the actual content type does not match the expected: actual=application/json, expected=application/geo+json
ContentTypeError: the actual content type does not match the expected: actual=image/tiff, expected=image/tiff; application=geotiff

but maybe just skipping this check altogether would be better?

Ah, sorry after digging in the code a little bit I see that is already possible via config!
httpconfig = stac_asset.Config(http_headers={'MAXAR-API-KEY':os.environ['MAXAR_API_KEY']},
                                 http_check_content_type=False)
download_item(config=httpconfig)

@scottyhq thanks for raising — since it's not uncommon for servers to have these media type mismatches, I wonder if switching to warn-by-default would be better UX?

since it's not uncommon for servers to have these media type mismatches, I wonder if switching to warn-by-default would be better UX?

Sounds good to me!


[SPARK-43473][PYTHON] Support struct type in createDataFrame from pandas DataFrame

What changes were proposed in this pull request?
Supports struct type in createDataFrame from pandas DataFrame.
With Arrow optimization, it works without the fallback:
>>> import pandas as pd
>>> from pyspark.sql.types import Row
>>>
>>> pdf = pd.DataFrame(
...     {"a": [Row(1, "a"), Row(2, "b")], "b": [{"s": 3, "t": "x"}, {"s": 4, "t": "y"}]}
... )
>>> schema = "a struct<x int, y string>, b struct<s int, t string>"
>>>
>>> df = spark.createDataFrame(pdf, schema)
>>> df.show()
+------+------+
|     a|     b|
+------+------+
|{1, a}|{3, x}|
|{2, b}|{4, y}|
+------+------+

and Spark Connect also works.
Why are the changes needed?
In vanilla PySpark without Arrow optimization, Row object or dict can be handled as struct type if the schema is provided:
>>> import pandas as pd
>>> from pyspark.sql.types import *
>>>
>>> pdf = pd.DataFrame(
...     {"a": [Row(1, "a"), Row(2, "b")], "b": [{"s": 3, "t": "x"}, {"s": 4, "t": "y"}]}
... )
>>> schema = "a struct<x int, y string>, b struct<s int, t string>"
>>>
>>> df = spark.createDataFrame(pdf, schema)
>>> df.show()
+------+------+
|     a|     b|
+------+------+
|{1, a}|{3, x}|
|{2, b}|{4, y}|
+------+------+

Whereas with Arrow, it uses a fallback to make it:
>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', True)
>>> spark.createDataFrame(pdf, schema).show()
/.../pyspark/sql/pandas/conversion.py:329: UserWarning: createDataFrame attempted Arrow optimization because 'spark.sql.execution.arrow.pyspark.enabled' is set to true; however, failed by the reason below:
  A field of type StructType expects a pandas.DataFrame, but got: <class 'pandas.core.series.Series'>
Attempting non-optimization as 'spark.sql.execution.arrow.pyspark.fallback.enabled' is set to true.
  warn(msg)
+------+------+
|     a|     b|
+------+------+
|{1, a}|{3, x}|
|{2, b}|{4, y}|
+------+------+

and Spark Connect fails:
>>> df = spark.createDataFrame(pdf, schema)
Traceback (most recent call last):
...
ValueError: A field of type StructType expects a pandas.DataFrame, but got: <class 'pandas.core.series.Series'>

Does this PR introduce any user-facing change?
Row object or dict in pandas DataFrame works as struct type when createDataFrame if the schema is provided.
How was this patch tested?
Added the related test.

Does that refactoring still conform to UNSUPPORTED_DATA_TYPE_FOR_ARROW_VERSION?

@xinrong-meng

Does that refactoring still conform to UNSUPPORTED_DATA_TYPE_FOR_ARROW_VERSION?

This PR doesn't change anything related to pyarrow version.

Sorry I meant UNSUPPORTED_DATA_TYPE_FOR_ARROW_CONVERSION. Do we have plans to remove the constraints?
@ueshin

Do we have plans to remove the constraints?

I'm not sure if it's planned, but now we can remove the constraints.

Merged to master.

This looks great, thanks for doing it @ueshin !


How to query table with database name？

We can query table in this way：
ti.tidbMapDatabase("test")
spark.sql("select * from tidb_test").show
but we can't query table with database name:
spark.sql("select * from test.tidb_test").show
this query will throw exception :
org.apache.spark.sql.AnalysisException: Table or view not found: test.tidb_test; line 1 pos 14;
'Project [*]
+- 'UnresolvedRelation test.tidb_test
If we can't query with database name , how can we join tow table in different database?

Hi, @lizhenhuan
Thanks for your feedback. If any two tables you are using don't have duplicate table names, you may simply use:
ti.tidbMapDatabase("test1")
ti.tidbMapDatabase("test2")

and query:
spark.sql("select * from table1, table2").show

where table1 and table2 originate from test1 and test2 respectively.
If there are duplicate table names, you may use:
ti.tidbMapDatabase("test1", dbNameAsPrefix = true)
ti.tidbMapDatabase("test2", dbNameAsPrefix = true)

where the corresponding table names for table1 will be test1_table1 and test2_table1.

get it. thank you very much

hi ! please tell me ,how to connect the database_name and database_name ?
I try database_name.database_name but can not.
error like this:
scala> ti.tidbMapDatabase("prod_ods",dbNameAsPrefix = true)
scala> spark.sql("select id from trade limit").show
+---------+
|       id|
+---------+
|551191467|
|551191468|
|551191469|
|551191470|
|551191471|
|551191472|
|551191473|
|551191474|
|551191475|
|551191476|
|551191477|
|551191478|
|551191479|
|551191480|
|551191481|
|551191482|
|551191483|
|551191484|
|551191485|
|551191486|
+---------+
only showing top 20 rows
scala> spark.sql("select id from prod_ods.trade limit").show
18/04/27 11:24:12 WARN ObjectStore: Failed to get database prod_ods, returning NoSuchObjectException
org.apache.spark.sql.AnalysisException: Table or view not found: prod_ods.trade; line 1 pos 15;
'Project ['id]
+- 'UnresolvedRelation prod_ods.trade, limit

@yixinGod Hi.
If you use dbNameAsPrefix = true, your table should be prod_ods_trade, i.e., database name and table name are separated by underline. That is because spark view does not support dot in view name.

get ,thanks

@yixinGod My pleasure. Feel free to address more issues if you encounter any difficulties!


Small translate issue in French

Is your feature request related to a problem? Please describe.
Just a small translation issue in French language
Describe the solution you'd like
Change the text from "Trajets" to "Disques" or "Péripheriques et lecteurs"
Change text to "Assez bon" in "Properties" to "OK" like in english
Describe alternatives you've considered
Reporting the issue ?
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?
Windows 10 Pro,latest version

@PruvostMaxime Would you like to work on this issue?

Yeah,it's would be a pleasure !
So i could even check if there is other missings translations :D

@PruvostMaxime That is great! Let us know if you have any questions.

Thanks !
And no problem,i'm gonna do it this weekend.

@PruvostMaxime Is this still an issue?

Sup,
I forgot to do the translations because i have more work than planned (moving out,exams..)
Really sorry,still need to do them

Looks like the translations are done now (wasn't running the latest version of Files)
So the issue can be closed


pi build patch

What changes were proposed in this pull request?

gcc-6.3.0 error fix for pi2 build
test Cmake fix for cross-compiling
test source code fixes

How was this patch tested?
build was tested with a cross-compiler
Quick checklist
The following checklist helps ensure your PR is complete:

[x] Eclipse Contributor Agreement signed, and signed commits - see IP Requirements page for details
[x] Reviewed the Contributing Guidelines and followed the steps within.
[x] Created tests for any significant new code additions.
[ ] Relevant tests for your changes are passing.

new one #494  is opened


Atrous convolution

Atrous convolution (also called dilated convolution) is used in quite a few works. Tensorflow has its implementation as tf.nn.atrous_conv2d. It should be nice if tensorpack/models/conv2d.py has a wrapper for tf.nn.atrous_conv2d :-)

It would be nice of course.
But you can just call tf.layers.conv2d in your model, with the dilation_rate option.

I see. Thanks! :-)

@JesseYang I just officially added it to the Tensorpack Conv2D class with #625 so now we officially support it.

Thanks!


chore: Updating import statements

Description
Updating import statements to use @appsmith/.. instead of ce/..
Fixes # (issue)
Type of change

Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

Manual
Jest
Cypress

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=b2245e6

/ok-to-test sha=ccdaf27


Upgrade MQTT to pull in some bug fixes

I saw a bunch of bug fixes in this lib and thought it might be worth upgrading it.

Disconnect hang: https://github.com/eclipse/paho.mqtt.golang/issues/501
Occasional deadlock when connections are lost: https://github.com/eclipse/paho.mqtt.golang/issues/509

Sounds good, thanks @mihaitodor!


Decorate references inside macros. [phab:D1838]

Created by zarko at 2017-08-07 20:44:34:
The indexer gives up too easily when indexing types
it's seen before, but which have macro-based locations
that can be mapped back to physical source files.
Check for this specific condition (we're emitting ranges
for types; the range we get in is valid, but in a macro;
that range is zero-length; we can follow it back to a file)
and avoid dropping out early.

fromberger accepted this revision at 2017-08-07 20:48:44

shahms wrote at 2017-08-07 20:50:41:
Do we want to support decoration all of the relevant parts for a macro resembling:
ASSIGN_OR_RETURN(ClassName var, expr());
It seems like this code (specifically, RangeForASTEntityFromSourceLocation) may only decorate single-identifier parts of that.

zarko wrote at 2017-08-07 21:51:26:

Check for multi-token types and expressions

zarko wrote at 2017-08-07 21:53:20:
Updated to better deal with multiple tokens. PTAL.

shahms wrote at 2017-08-07 21:59:36:
Thanks!

shahms accepted this revision at 2017-08-07 21:59:36

zarko closed via commit 3a33b731d7da0bdd541539fa14500d7dadfb4fa7 at 2017-08-07 22:43:13


croshair

is there a way to turn off the croshair i play on feather and i have croshair mod enabled and with this mod i have two croshairs is there a way to disable croshair in customhud?

It'll be in the next release, sometime within the next week

Fixed in v3.1


[@tests] add prod mode to labs packages

Labs packages will test with prod and dev modes
Previously TEST_PROD_MODE=true was used to flag prod mode.
This has been changed to MODE=prod

Nice! Thanks for the small scoped PR.
It's expected that the Sauce tests are still failing, so that's fine. The changesets failure is also fine, since this doesn't affect any published packaged. (We can also do npx changeset --empty to make it green).

added an empty changeset! thanks @aomarks


Adding third ppxgboost example

Issue #, if available:
new feature added.
Dependency installation updated.
Description of changes:

add the third example along with necessary dataset.
changed installation instruction in readme.md for pyope since the old way doesn't work anymore
Also, suggest removing the "third-party" folder

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Just to want to clarify, the contribution we made are based on work by Kodai Sato, me and Eric. (comment here for the record)


Fix date formatting

Questions
Answers

Description?
We were happily calling a function with a wrong argument count. This fixes it.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes tests in https://github.com/PrestaShop/PrestaShop/pull/34521, which revealed this issue when I typed displayDate method.

How to test?
See steps below.

What is wrong
The method Tools::displayDate was changed between 1.7.8 and 8.0.0, and this module was calling the old version, resulting in some errors in developer mode.
https://github.com/PrestaShop/PrestaShop/blob/1951311beb2497bb97659aded1b643905403becc/classes/Tools.php#L981
https://github.com/PrestaShop/PrestaShop/blob/f64f657366caf66e01f3b4fccaad4b77989a1257/classes/Tools.php#L923
How to test (do these steps on both versions)

Get 1.7.8 and 8.0.0
Install this module. (Make sure to uninstall distribution api.)
Go to BO > Advanced parameters > Performance and set Forced compilation and disable cache in Smarty section.
Go to settings of this module and check that you see date normally in the template list, like below. ⬇

@florine2623 Added some steps to reproduce. :-)

Yes, just the fact that you don't have any errors makes this QA ✅. :-)

Yes indeed, the date format changes on your country. I didn't think about that, sorry ^^


Disable default bitvec features to avoid std

Fix required for parent crate - see https://github.com/librasn/rasn/issues/262#issue-2353222882.

Future work: once this PR gets merged, crate must be released and rasn updated.

Thank you for your PR, and congrats on your first contribution! 🎉


dune-gen does not support non-deterministic mode

Hi,
It seems that dune-gen (used by stanza 0.2) does not support setting non-deterministic mode:
https://github.com/realworldocaml/mdx/blob/4942357cad00307d787c5d117ce4941678b39296/bin/dune_gen.ml#L35-L41
If we want MDX_RUN_NON_DETERMINISTIC=1 dune runtest to work, this needs be supported and dune to be adjusted so that it knows about the envvar dependency.

Thanks for the report and the debugging. From the MDX side this should be quite easy to fix.
Does dune pass all the environment options as-is to the binary produced by dune-gen? Or are there other adjustments that are necessary to do?


Object not updating on the UI

I have a simple object called ambassador that I retrieve from the store which should be getting the initial state - see the constructor down below.
    constructor(
        private store: Store<AppState>,
        private ambassadorActions: AmbassadorActions,
        private router: Router,
        private route: ActivatedRoute,
    ) {
        **this.ambassador = store.select('ambassador');**
    }

Let's take this very simple UI which I want to see update after the successful API call.

    {{ambassador.id}}

I then run these lines of code on the Init.  However, it does not appear my object is getting updated because the UI is not changing.   I have logging turned on and it appears that the object is updated
    ngOnInit() {
        this.paramsSub = this.route.params.subscribe(params => this.username = params['username']);
        this.getAmbassador(this.username);
    }

    getAmbassador(username) {
        this.store.dispatch(this.ambassadorActions.getAmbassador(username));
    }

What am I missing here?
Thanks!

@jrmcdona store.select('ambassador') returns an Observable, so you need to subscribe to it to get its value
 {{ambassador.id}}

should be
{{ (ambassador | async)?.id }}

Your ambassador variable is an observable, you should use async pipe:

    {{ (ambassador | async).id }}


chore(sidekiq): add sidekiq_retries_exhausted handling

Current dependencies on/for this PR:

master

PR #1   👈

This stack of pull requests is managed by Graphite.


km3d init. Decoder, head, and utils added.

This PR targets at the overall framework of KM3D with implementation of heads' over structure and userful decoders and utils. Development of the heads can be supported by the functional decoders with minor adjustments.

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

Hi @AllenLiuX ！We are grateful for your efforts in helping improve this open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) , where you can share your experiences, ideas, and build connections with like-minded peers.
To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


odo init interactive mode: Automatic port detection based on Alizer detection

/kind user-story
User Story
As an odo user, I want odo to automatically detect the port that my application is using So that I don't have to type it again if it is already defined in my project source code.
Acceptance Criteria

[ ]  odo init should automatically detect all ports that the application listens to

Notes
The detection logic should be in Alizer, odo should just use Alizer library for this.
/kind user-story

/status blocked
Currentl, Alizer can't do this, but it is work in progress

I would love to see support for manually providing a port value via odo init --port PORTNUMBER.
If more than one port is detected, we may need the user to specify which port to use anyway.

I would love to see support for manually providing a port value via odo init --port PORTNUMBER.
If more than one port is detected, we may need the user to specify which port to use anyway.

Thanks for your input, @ryanj !
As I understand it, if there are multiple ports detected in the application and returned by Alizer (when running odo init), the resulting Devfile would list them all, and odo dev would expose and port-forward each one of them. It would then be up to users to call the application on the right port forwarded.
But as you suggested, giving users the ability to explicitly specify the port (and optionally a debug port too) (at least when running odo init non-interactively) would be great.
@kadel Any comment on that?

If alizer detects single port, override the port defined in Devfile.
If alizer detects no port, use the port defined in Devfile.
Warn the user about it in both the cases.
If there are multiple container components, error out, for now.


Switch to Key/Mouse EventHandlers

Is your feature request related to a problem? Please describe.
The current implementation means at only the moment is_key_pressed or get_mouse_press are called the state of the key/mouse is checked. This is a simple solution, but also introduces delays and at low framerates entire keypresses might go unnoticed.
Describe the solution you'd like
It would be significantly better if you were to hook/unhook eventHandlers to keys/mouse events, instead of checking in an endless loop.
Implementing on_key_down(Key, Function), on_key_up(Key, Function), on_mouse_move(Function), ...

One of the first goal of the project is to have a procedural approach, I didn't intend to do events due to me being unskilled at first (I learned Rust with this project) and also due to potential variable access problems.
For example, how can I give you access to your variables in the event function ? We may need to define something in the middle to allow that. 🤔 This may require async properties to the project
Do you have by any chance any experience in it ?
By the way, we capture inputs when the engine is idling, so only on wait_frame 😉

ill check it when i get some time

Hello @razaqq !
I made a pull request that add some sort of event handling. Can you take a look at it and tell me if it's resolving your issue, please ?

The pull request has been merged! see Release 2.1.0


[Build] Fixes make clean and adds .gitignore

What is the purpose of this pull request (PR)?
Fixes issue #63
Was this PR tested and how?
./autogen.sh && ./configure && make -j4 && make clean
Does this PR resolve an open issue (reference issue #)?
Fixes issue or JIRA tasks:
#63

utACK.  Will test soon.


[TFLite] Add support for passing extra parameters to the LUTPopulate transform function

Hello,
LUTPopulate currently takes a float (*transform)(float) function pointer to generate the values of the LUT. This commit provides some overloads to allow passing extra parameters to the transform function through a type-erased void* in the form of a float (*transform)(float, const void*) function pointer. A void* is used instead of std::function to keep compatibility with TFLite Micro.
It can then be used as follows for example:
LUTPopulate<int16_t>(
    input_scale, input_zp, output_scale, output_zp,
    [](float value, const void* extra_params) {
        if (value <= 0.0f) {
            const float output_scale =
                *static_cast<const float*>(extra_params);
            return std::numeric_limits<int16>::max() * output_scale;
        }
        return 1.0f / std::sqrt(value);
    },
    static_cast<const void*>(&output_scale), lut_int16);

This extra flexibility is useful for PRs like https://github.com/tensorflow/tensorflow/pull/51785 and other PRs we would like to raise that use the LUTPopulate function.
Thibaut

Hi @Tessil Can you please resolve conflicts? Thank you!

@gbaned Thanks, I resolved the conflicts.


Conduct secure random generator on macOS

Description
MacOS provides secure random generator which allows us generating random number without calling file descriptor.
For more information see: https://developer.apple.com/documentation/security/1399291-secrandomcopybytes
Status
READY/IN DEVELOPMENT/HOLD
Yes | NO
Which branch? development
Migrations
NO
Additional comments
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog updated
[ ] Backported

Steps to test or reproduce
Outline the steps to test or reproduce the PR here.

I am closing this pull request because it makes the code less portable and harder to maintain and doesn't have a clear benefit.


@conda-forge-admin,please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/pymc3-hmm-feedstock#6.


Consider adding chainable syntax to Schema or SchemaBuilder

Example of how schema initialization might look like (see #36 for discussion on this subject):
$schema = new GraphQL\Schema();
$schema->setQueryType( $objectType)
    ->setMutationType($mutationType)
/* Other possible setters:
   ->setDirectives($directives)
   ->setTypes($types)
*/

Closing in favor of #82


Read only FileSystem

I'm attempting to run serge inside of Pterodactyl Panel to avoid issues with crashes and it successfully pulls the docker image but fails on the step: Installing collected packages: llama-cpp-python with the following error message
ERROR: Could not install packages due to an OSError: [Errno 30] Read-only file system: '/.local'
139:C 26 May 2023 00:44:33.742 # Fatal error, can't open config file '/etc/redis/redis.conf': Permission denied
Is there any way around this or must I host this directly on the machine? Pterodactyl uses redis already so I'm sure it may be conflicting.

I guessed as much. I'm just cohosting serge on my minecraft server until I can get a second server.


Use correct config option for the log path.

The cli client is using the wrong config option to infer the log path.
From ovos-utils, it's using logs.path :
https://github.com/OpenVoiceOS/ovos-utils/blob/c9b1b560dab02d13a77bd9c1f3ad788e65fb9c13/ovos_utils/log.py#L53
This PR fixes this problem.

I revisited the code. The reference to log_dir is there in the original mycroft cli client but nowhere else.
The way I understand hit is that you could point to a different location for the logs if you were running the cli client as a different user or something like that.
I've reworked the change to add a deprecated warning and still honor log_dir if it's the only variable present.

@JarbasAl anything else needed on this PR ?


import/no-internal-modules forbid option doesn't work as expected

So basically I want to create a rule that protects me from defining imports that have more than 2 levels of depth ("@app/commons/date-utils")
In one case I want to have the possibility to define 3 level imports ("@app/components/button")
For example, these imports should be invalid:
"@app/views/home"
"@app/commons/date-utils"
these imports should be valid:
"@app/components/button"
"@app/views"
"@app/commons"
I created a rule but it doesn't work. I don't know if I'm doing something wrong or it is an issue.
    "import/no-internal-modules": [
      "error",
      {
        "forbid": ["@app/!(components)/*"]
      }
    ]

plugin version:  "2.23.3"

I checked my pattern @app/!(components)/* in https://lironzluf.github.io/minimatch-playground/ and it works as I expected. So I guess that problem is with the plugin.

Can you try with v2.23.4?

I tried, it doesn't work either.

Same issue : https://github.com/benmosher/eslint-plugin-import/issues/2082

Closing as a duplicate of #2082.
I'm still confused, because our own tests pass for this.

Tests cover exactly the same situation as described in that PR?

@gk4m true, probably not the exact same. I suppose the next step is a PR that adds tests for the exact cases in this issue, as well as #2082 - if they fail, then that makes it much easier to fix.


(Windows) enableSWRendering and RDP problem

Hello,
in Windows it is essential, that a program can also run in an RDP (Remote Desktop Protocol) session.
For a javafx app the VM parameter -Dprism.order=sw must be used. (This is crazy)
If i add <enableSWRendering>true</enableSWRendering> to my client-maven-plugin configuration, the app still doesn't work with RDP.
Did i miss some additional configuration?
thx
Edit: This is only, if the first dialog is the Alert dialog ...  and i think it's an javafx issue

This helped:
PlatformImpl.startup(()->{});
and VM args:
--add-exports javafx.graphics/com.sun.javafx.application=ALL-UNNAMED


use source image storage type for Color3 case

closes #83

Actually, in Julia 1.6, we can dispatch on the functors but I'll just leave things as it is for now for backward compatibility consideration.

New language features

Types written with where syntax can now be used to define constructors, e.g. (Foo{T} where T)(x) = ....


feat(all): add openapi3 detect

:heavy_check_mark: Checklist:

[ ] Have only one commit (if not, squash them into one commit)
[ ] Tests for the changes have been added (for features / bug fixes / refactoring)

Codecov Report

Merging #262 (6ece6f3) into main (7058ab5) will increase coverage by 0.05%.
The diff coverage is 80.95%.

@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
+ Coverage   62.74%   62.80%   +0.05%
==========================================
  Files          16       16
  Lines         604      621      +17
==========================================
+ Hits          379      390      +11
- Misses        209      213       +4
- Partials       16       18       +2

Impacted Files
Coverage Δ

internal/openapi3/openapi3.go
90.00% <ø> (ø)

internal/parse/parse.go
59.18% <80.95%> (+9.18%)
:arrow_up:

internal/faker/internet.go
85.71% <0.00%> (-14.29%)
:arrow_down:

internal/faker/person.go
95.65% <0.00%> (ø)

Continue to review full report at Codecov.

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


ios uploading debug symbols

OS:

[ ]  Windows
[/ ]  MacOS
[ ]  Linux

Platform:

[ /]  iOS
[ ]  Android

I am able to upload my bundles fine to sentry.io during the build process, but one issue I am having is that for IOS build it always uploads as main.jsbundle instead of index.ios.bundle resulting in error "Source code was not found for app:///index.ios.bundle" when I a view an issue. For Android the proper bundle "index.android.bundle" is uploaded. I looked at script "react-native-xcode.sh" and it definitely has a bundle file of main.jsbundle. I am wondering whether I misconfigured react-native-sentry or is it just something on my end?

was just an issue on my end -- closing.

Can you remember how you fixed this? I'm running into the same issue.


zlib decompressor error

out file have some error data when patch by zlib decompressor.

Hi @sisong,
Can you please send your patch and original (old) files for the sample?
Also, is this produceable on single or directory patch? Or both?

Hi @sisong,
Sorry for taking too long for the reply due to some activities need to be done on my primary project and some RL stuffs.
Seems like the buffer doesn't get filled properly while reading the data from .NET's own DeflateStream.
The fix is to use ReadExactly method for reading the data to ensure that the buffer will always be filled.
I've just pushed some commits to fix this issue and also releasing a new hotfix in the release page.
Can you please confirm whether the issue is now fixed?
Anyway, thank you for creating HDiffPatch!
Your project really motivates me to learn more about C/C++

tested the new version of SharpHDiffPatch:
diffFile created by $ hdiffz -m -c-zlib ...,  SharpHDiffPatch test passed;
but diffFile created by $ hdiffz -s -c-zlib ..., SharpHDiffPatch test failed!
( the same tests, zstd,bzip2,pbzip2 & nocompressor all passed.  )

Your project really motivates me to learn more about C/C++
Your project comes with a libzstd.dll, curious why not choose to compile out and come with a libhpatchz .dll?

Hi @sisong
Sorry for my late response (again).
I see. Seems only the zlib-compressed stream diff fails in this case. Will try to investigate it later.

Your project comes with a libzstd.dll, curious why not choose to compile out and come with a libhpatchz .dll?

I used to use the native library in the first place for my other project called Collapse, which is basically a universal launcher for miHoYo's PC Games. I used it to patch all the hdiff patch files for updating the game.
But in the end, the reason why I choose to make this C# port of HPatch instead of using the native library is that, I want to make the project to be fully compatible with .NET codes and minimizing the dependencies of code interop while also makes it easier to diagnose if something went wrong with the patching process. The second is that I want to make some additional APIs including an API to get the info (mostly header related) of the patch file and the "progress event" so I can track the current patching progress in real-time.

Hi @sisong,
I just pushed another release (v1.4.3) that hopefully fix the issue you reported last time.
Can you please check if the issue still persist or not?

all cases tests passed.


DNS based discovery not configurable

Since commit https://github.com/pires/docker-elasticsearch-kubernetes/commit/d1907dad5d6985c60848b16bdd7bb8af53c78954 it's no longer possible to automatically discover the master nodes in your cluster if the service has a different name. I run multiple ES clusters with different names inside the same namespace.
You used to be able to use the following environment variable:
service: ${DISCOVERY_SERVICE}

But now the following hardcoded name is used:
ping.unicast.hosts: elasticsearch-discovery

Is it possible to either revert this change or make sure it's configurable via the same envvar again? Thx

Hm, I see you already did a commit to fix this after 5.1.2. Any chance you can push an updated 5.1.2_1 or something like it? Thx

Yes.


dateWritten element should be placed after the ‘id’ tag

dateWritten element should be placed after the ‘id’ tag
dateWritten element under MedicationOrder(contained resource)should be placed after the ‘id’ tag.
FHIR Resource used->ExplanationOfBenefit(PBS & MBS)
FHIR version -->1.4.0
HAPI version -->1.5
dateWritten element should be placed after the ‘id’ tag.txt

Hi @ganesh-athmagnanam , we have just released HAPI FHIR 2.0, would you be able to confirm whether this issue is still occurring on that version?


Implement all constraints from the mathematical formulation

Pull request details
Describe the changes made in this pull request
Changes made by @gnawin and me
List of related issues or pull requests
Collaboration confirmation
As a contributor I confirm

[ ] I read and followed the instructions in README.dev.md
[ ] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[ ] Tests are passing
[ ] Lint is passing

Looks fantastic and completely correct! ;)


indexer: replace _previous_version with _last_indexed

replace _previous_version with _last_indexed which is a db version of last indexed version of record (based on _update field)

indexer_task: move search of records to re-index before current record re-indexing.

integration_async: Update all tests which were checking _previous_version as now after re-indexing _last_indexed will show current_version (as current will be last indexed).

fixed retry_until_matched for expected_results which are logical False

INSPIR-3618

@pazembrz maybe I missed parts of your discussions, but what's the purpose of this PR? Seems to be missmatching ES with DB

This should fix problem described by me here: https://inspirehep.zulipchat.com/#narrow/stream/122202-devel/topic/indexing.20incosistencies/near/200515453
@drjova What you mean by

Seems to be missmatching ES with DB
This should actually help to keep es in sync with DB

I'm not sure this makes sense, as you'll run into atomicity issue (the version on ES changes between reading from ES and computing the records to reindex).

Still this should be less problematic than current way how we are doing this. In worst case we will re-index twice same referenced records. Currently in worst case we are not re-indexing any referenced records.


feat: initial module implementation

Description of the changes
First implementation of the new Longhorn module which will be used with SKS cluster.
Tests executed on which distribution(s)

[X] SKS (Exoscale)

@hbollon I took the liberty to commit some changes to the README.adoc -> https://github.com/camptocamp/devops-stack-module-longhorn/pull/1/commits/bcd5e8df6e840be106d9ed4813f1545aa0dcd392
We can discuss them if you want ;)


Create semaphores dynamically

This introduces dynamic creation of the semaphores used internally by the library, most noticeably in the client code (server/scan to be done). The reason for this change is each semaphore used in each attribute that uses them consumes ~180 bytes of memory.
On the client especially, this effect is dramatic when considering there are 2 semaphores per remote service, 3 per remote characteristic and 2 per remote descriptor. If the remote device has 1 service with 1 characteristic and 1 descriptor, when we connect and obtain the database it will use ~1260 bytes of heap memory before beginning any other operations.
This PR will remove that and create the semaphores on an as required basis using new macros to help implement this procedure. Using this method has reduced heap use in my testing by ~700% per connection, depending on the number of attributes on the remote device.
This is not without a cost however, it requires careful and strict adherence to properly creating and making sure the semaphores are deleted when no longer needed. In other words increased maintenance and increased risk of memory leaks and bugs.
So far I have been able to run this iteration for days with 3 threads accessing the semaphore protected resources with potentially conflicting timings in both debug and release configuration without issue.
I believe this to be overwhelmingly worth the cost, @Jeroen88 has seen a ~27k heap use reduction connecting to a peripheral with 72 attributes, that is incredible and worth the effort IMHO.
If you can find a way to break this please comment, so far so good for me!

@h2zero as I said before, I am not very experienced with semaphores. Currently my own test case is using PR #49 but PR #40 not yet, 3 peripherals, endlessly scanned, connect (once) to one and maintain that connection. Next, every 12s: reading service data from the first, reading manufacturer data from the second, reading one characteristic from the third (connected) device. Will it give you insights if I start this scenario as a test for a longer period of time, to see if it is stable?

@h2zero I think I have to compliment you on this achievement, but frankly I have got no idea of what's going on, lol!

@h2zero I am thinking a bit about this PR. I do not know for sure, but if we merge PR #40, then most of the class instances for the characteristics and most of the descriptors will never be created. In this scenario the savings of this PR are far less than you report now. If we find a solution for creating services as well dynamically then also the service class instances are sparsely created.
IMHO dynamic population of the class instances is very important!
If we go on with the dynamic object creation, is the added complexity (and the, I think, non-standard use of semaphores which creates an extra threshold for other programmers that want to add to this library) of the dynamic semaphores worth the effort?
I am aware of the fact that in the dynamic objects scenario combined with the dynamic semaphores the memory savings increase on the number of objects requested by the programmer. Still I am in doubt of this solution....

Ideally, we could achieve both. Creating semaphores dynamically is quite common actually, they just sit there taking up resources most of the time, especially in this library. The maintenance isn't that bad, just like any other resource you allocate, you need to release it properly, the macros help with this.
The complexity here comes from the use of a single static pointer to the allocated semaphore, which is a binary type wrapped in a class to make it somewhat custom and keeps track of the number of tasks trying to take it. This has been hidden in the class/macros and could probably be a bit simpler but I can see it being confusing for those who are unfamiliar with the subject. Perhaps I should explain the operation of them somewhere.
#40 Is the next step, it's also a bit of a complex problem due to how BLE spec uses "handles" and how NimBLE accesses the peripheral database. I need to do some experiments with it and see what's reasonably possible. The question I need to answer there first is "does NimBLE request the whole database when calling get_service/characteristic_uuid?". If that is what it does we will have to implement some other way to get "only" the attributes we want.

The question I need to answer there first is "does NimBLE request the whole database when calling get_service/characteristic_uuid?"

Do you mean the stack or the library? For the stack I don't know, but I can't imagine it retrieving more than needed. For the library I am sure: all services are retrieved, and next every characteristic for every service and every descriptor for each characteristic. Actually it is done with the function call here defined here.
PR #40 retrieves all services on connection, but the characteristics dynamically only on first request. It does not retrieve the descriptors (yet).

I was referring to the stack, I'm not sure how it is done there. BLE was meant that you would connect and bond with the device so you would only ever get the database once and store a copy for future reconnection. So that is (somewhat) what the library does.
Because of the way handles work you need to ask the device for the whole thing to find what you're looking for, it could be stopped once you found it but if the attribute you want is at the end of the database then you've just discovered the whole thing anyway. Also if you didn't store all those results and wanted a second attribute handle you would have to start the whole process over, wasting time and battery.

Moving the discussion to #40 ... see there

Thinking about this PR, even though it works well to my own surprise I believe there is a better option that can eliminate the semaphores completely. It’ll require a bit of work and testing but the results could be worth it.

Closing this as there is a better solution almost complete.


Close button does not appear to respect padding anymore

This is just a float issue. It's working as intended - it looks when when there is text in the header, but without it the header collapses because the button has been removed from the document flow. The real solution here is to remove the float.


Improve ListFile API docs in case null "path" field

Specifically want to make clear that ListFile on a commit does not return all files in that commit, only files at the top level

LGTM


When I move files - perform a git move and not a delete and create

This issue is not really solved ->
https://github.com/Microsoft/vscode/issues/31380
Or am I missing something

The user summarized it correctly: https://github.com/microsoft/vscode/issues/31380#issuecomment-317702582
In Git, a move is nothing but a delete and create. We show exactly what git status shows.


tests: BinaryHeapArray::heapDown()

Add tests to increase branch or path coverage.

no tests can be added, I'll choose another function

Their BinaryHeap doesn't support having two equal values in it. Because of that branch #8 could never be reached (the only uncovered branch).


php: php_proto build rule uses existing bootstrap image.

@alainjobart

This change is

LGTM thanks for fixing my mess :)


[Feature]: Implement prioritized experience replay buffer

Prerequisites

[X] I have tried updating UtilsRL to the newest version.
[X] I have checked both open and closed issues but found nothing related to my request.

UtilsRL verison when proposing this request
0.3.13
What I am expecting
Implementing PER for DQN-like algorithms.
Possible solutions
See the original paper for details.
I also implemented once in unstable baselines, here is an example. It was removed from the current version of UtilsRL, not knowing the reason.
Any additional messages which might help
No response
Urgency
Not a big problem, minor modifications on docs / annotations / codes.

Maybe related to #15.

#22 is working on this.


Configurable id property on full-text search: Lunr2 integration

As documented in https://github.com/itemsapi/itemsjs/blob/master/docs/lunr2-integration.md it is possible to use Lunr2 for full-text searching.
I want to try to use this, because I need nested/deep object search (which is possible via the extractor of a field https://lunrjs.com/docs/lunr.Builder.html#field )
But, my data set has no id property, but e.g. a unique property uuid. So it would be nice to make this property configurable in order to be more flexible on this.

It's done. More details in PR tests or integration examples in docs.


Add public_ipv6 to keyNames

Scaleway servers should be reachable through ipv6 if they don't have a
public_ip attribute.

Thanks!


[Snyk] Security upgrade @testing-library/jest-dom from 5.17.0 to 6.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Uncontrolled resource consumption SNYK-JS-BRACES-6838727
Yes
No Known Exploit

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Uncontrolled resource consumption

👷 Deploy Preview for resonant-biscochitos-ee6470 processing.

Name
Link

🔨 Latest commit
a1759fcfcfcda6a6d98c3394351b517d7213d7a4

🔍 Latest deploy log
https://app.netlify.com/sites/resonant-biscochitos-ee6470/deploys/6642f180ad902c0008c405bf


refactor: replace glu.Config with glu.PipelineBuilder

Continuing to seize on the pre release and breakable nature of this project 😂
This removes the concept of glu.Config and replaces it with an optional glu.PipelineBuilder.
The builder is where the (now optional) typed resource comes into play.
Previously, we couldn't hang a type parameter off the core system, otherwise, we tie the system to a single type parameter.
Same went for configuration and the pipeline interface at this fidelity.
This made creating a config structure that could simplify configuring a typed Git and OCI source hard to do.
Now, AddPipeline takes a func(context.Context, *config.Config) (Pipeline, error).
This is not typed and only has access to the raw config.
The new function glu.BuilderFunc returns this function type, but it does so by adapting a function which takes the new *PiplineBuilder type.
The two functions previously hung off *glu.Config, called GitRepository and OCIRepository have now morphed into:
glu.GitSource(...)
// and
glu.OCISource(...)

These two functions depend on this builder (and they continue to use it for caching previouslly built dependencies) and return the actual typed git.Source[R] and oci.Source[R].
Each of these functions and types share the core constraint of glu.Resource.
However, the Git and OCI ones further constrain it with their respective necessary requirements.
TL;DR this removes the need to know about a sources repository dependency (and removes the need for more type arguments):
https://github.com/get-glu/glu/blob/e3daa16e6d2b57608f8badc0bef1f75550d5be4f/examples/oci-and-git/experiment.go#L22-L37

Hold this thought. I think this might bork caching.

I think there is something here, but it does break the cache (caching is no longer on the single system).
I am going to take another pass at this later.
I think there is something here, just the result will be a little more invasive.


Removed the use of deprecated scipy.stats.ss function

I recently updated scipy to version 1.0.0 and found that scipy.stats.ss used in the analysis/stats.py module has been deprecated.

Looks good to me.
Did you test this change and the results are equivalent?  It looks like tests are failing because of Travis not anything you did, but it's not clear if this is covered by tests.

It's not even clear if that function is called anywhere, as the other mention of Pearson r computes it separately. I'll just go ahead and merge this then.


Feature/race

Develop the race adding feature
other than that includes a few other functions

Loout
Alert for API calls
Router Protections

Logout function

Race function

List & Create partally


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1668

Questions ?
Please refer to the Backport tool documentation


OUTDATED

Update your pages when you update your products so that the pages are relevant.

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

ID: 0dff4c66-23f7-d3d1-f60c-db15608b9f3b
Version Independent ID: cbde5db2-7471-723b-9b6b-9d055941ff36
Content: Create a branching rule for a survey
Content Source: cv-docs/create-branching-rule.md
Service: dynamics-365-customervoice
GitHub Login: @sbmjais
Microsoft Alias: shjais

Thanks for your comment, @brcox9090. This issue has been assigned to the doc author for review.

Thanks for the feedback. The document is updated. Closing this issue.


Update toll-free-dialing-restrictions-in-the-united-states-u-s.md

Moving the "Important" note from the bottom of the article to the top to increase visibility and adding references to the toll-free number rates mentioned in the note.

Learn Build status updates of commit 0bdb0c9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/toll-free-dialing-limitations-and-restrictions/toll-free-dialing-restrictions-in-the-united-states-u-s.md
: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 learn.microsoft.com contributor guidesPost your question in the Learn support channel

Closing this pull request as timing is being adjusted.


Vitamins and Minerals shows like 0

I've just added a product to the database and if I look at the Vitamins and Minerals in the app it is in 0, but if I check it through the website the values are shown correctly.
App Screenshot:

Browser Screenshot:

Product: https://world-es.openfoodfacts.org/producto/8480017371676
I downloaded the app from F-Droid, I'm logged in and my app version is: 2.9.7

Thanks a lot for the report @RiQuY
@brandenfung very much looks like a unit error (Vitamin E shows 10 time less than what it should be)

It looks like a problem on the server side.
If you go to https://fr.openfoodfacts.org/api/v0/product/8480017371676.json, you'll find the following values for sodium:
"sodium":0.133858267716535,
"sodium_serving":0.133858267716535,
"sodium_value":"0.13385826771653545",
"sodium_unit":"g",
"sodium_100g":0.446,

Which matches the values displayed in https://world-es.openfoodfacts.org/producto/8480017371676.
But having a look again at the json, but for vitamin B2:
"vitamin-b2":0.00042,
"vitamin-b2_serving":0.00042,
"vitamin-b2_value":"0.42",
"vitamin-b2_100g":0.0014,
"vitamin-b2_unit":"mg",

we find that there's some kind of undesired mg-to-g-conversion for fields "vitamin-b2", "vitamin-b2_serving" and "vitamin-b2_100g" (with an incoherence with the other field "vitamin-b2_value"), with "%_serving" and "%_100g" being the values displayed in the app by NutrimentsRecyclerViewAdapter.

@monsieurtanuki You might be right, values in vitamin-b2_100g for this product seems to be in grams and not mg.

@teolemon Please reopen, issue is still unsolved.
I just checked the same product today in the latest version and still show ups wrong.


For HyP3 jobs, also download and upload browse image

When running RAiDER independently in HyP3 on previous INSAR_ISCE HyP3 jobs, all three product files will need to be downloaded from the previous HyP3 job and re-uploaded so that when this job is ingested, all the files are available.
Previously, only the .nc and .json files were downloaded and uploaded. This downloads and uploads the remaining browse image.

Looks good to me.
So you download/upload png regardless if you are running Raider separately with failed job_id or with full workflow.
Hopefully the s3 upload function clobbers the old browser image. That would be my only conern


Feat/improve atip i18n

Summary | Résumé
Improving i18n support for the ATIP module
Related to https://github.com/cds-snc/site-reliability-engineering/issues/705


pkg_resources: UnboundLocalError: local variable 'dist' referenced before assignment

When trying to run my package's tests frozen via cx_Freeze on Windows, I just got this:
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\pkg_resources\__init__.py", line 2986, in _initialize_master_working_set
    del dist
UnboundLocalError: local variable 'dist' referenced before assignment

full traceback:
unittests-frozen runtests: commands[2] | C:\projects\qutebrowser\.tox\unittests-frozen/build/run-frozen-tests
Traceback (most recent call last):
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
    exec(code, m.__dict__)
  File "scripts/dev/run_frozen_tests.py", line 38, in <module>
    pytest_rerunfailures, pytest_warnings]))
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\config.py", line 39, in main
    config = _prepareconfig(args, plugins)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\config.py", line 118, in _prepareconfig
    pluginmanager=pluginmanager, args=args)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 724, in __call__
    return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 338, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 333, in <lambda>
    _MultiCall(methods, kwargs, hook.spec_opts).execute()
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 595, in execute
    return _wrapped_call(hook_impl.function(*args), self.execute)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 249, in _wrapped_call
    wrap_controller.send(call_outcome)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\helpconfig.py", line 28, in pytest_cmdline_parse
    config = outcome.get_result()
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 278, in get_result
    raise ex[1].with_traceback(ex[2])
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 264, in __init__
    self.result = func()
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 596, in execute
    res = hook_impl.function(*args)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\config.py", line 861, in pytest_cmdline_parse
    self.parse(args)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\config.py", line 966, in parse
    self._preparse(args, addopts=addopts)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\config.py", line 927, in _preparse
    self.pluginmanager.load_setuptools_entrypoints("pytest11")
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\_pytest\vendored_packages\pluggy.py", line 495, in load_setuptools_entrypoints
    from pkg_resources import iter_entry_points, DistributionNotFound
  File "c:\python\32-bit\3.4\lib\importlib\_bootstrap.py", line 2237, in _find_and_load
  File "c:\python\32-bit\3.4\lib\importlib\_bootstrap.py", line 2226, in _find_and_load_unlocked
  File "c:\python\32-bit\3.4\lib\importlib\_bootstrap.py", line 1191, in _load_unlocked
  File "c:\python\32-bit\3.4\lib\importlib\_bootstrap.py", line 1161, in _load_backward_compatible
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\pkg_resources\__init__.py", line 2958, in <module>
    @_call_aside
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\pkg_resources\__init__.py", line 2944, in _call_aside
    f(*args, **kwargs)
  File "C:\projects\qutebrowser\.tox\unittests-frozen\lib\site-packages\pkg_resources\__init__.py", line 2986, in _initialize_master_working_set
    del dist
UnboundLocalError: local variable 'dist' referenced before assignment

This seems to be introduced in #698 (cc @minrk) and happens when the for dist in working_set: above doesn't assign to dist because working_set is empty.

Fixed by #703. Sorry about that, and thanks for catching it!

No worries, that was a mean one, probably wouldn't have noticed it either. Thanks for the quick fix!

Thanks for fixing this, just hit it myself. I see that 25.1.2 includes this fix and is tagged on github but isn't released on pypi? If you're expecting to get that onto pypi soon I can probably avoid having to go through all my install scripts pinning the setuptools version. Any idea when that might happen?

Hmm. PyPI releases are meant to be automatic from tagged versions. Let's see what happened.
Aah, so it built and tests passed, but the upload failed because I forgot to bump the versions in the code (by running bumpversion patch) first.
I'll push out a release momentarily.

I expect the release to go out with this job.

Great, it's out, thanks!


IEXQueryError

Summary (include Python version)
Python 3.7
from iexfinance.stocks import get_historical_data
import datetime
from dateutil.relativedelta import relativedelta
start = datetime.datetime.today() - relativedelta(years=5)
end = datetime.datetime.today()
df = get_historical_data("GE", start=start, end=end, output_format="pandas", token="my_token")
Date/time of issue
12/9/2019 1300 GMT+8
Expected behavior
data loaded into df
Actual behavior
Traceback (most recent call last):
File "/home/test.py", line 12, in
df = get_historical_data("GE", start=start, end=end, output_format="pandas", token="my_token")
File "/home/venv/lib/python3.7/site-packages/iexfinance/stocks/init.py", line 44, in get_historical_data
close_only=close_only, **kwargs).fetch()
File "/home/venv/lib/python3.7/site-packages/iexfinance/base.py", line 209, in fetch
data = self._execute_iex_query(url)
File "/home/venv/lib/python3.7/site-packages/iexfinance/base.py", line 165, in _execute_iex_query
return self._handle_error(response)
File "/home/venv/lib/python3.7/site-packages/iexfinance/base.py", line 178, in _handle_error
raise IEXQueryError("The query could not be completed. "
iexfinance.utils.exceptions.IEXQueryError: An error occurred while making the query.
Edit: I am close to using up my monthly message allocation (98%) at IEXCloud, could this be the reason I'm getting the error?

Yes that is likely the error. We are working on repairing error reporting. Let me know if this continues to be an issue.


P2322R6 accumulator types for reduce

This PR addresses the following issue. I also found that we use copy assignment operator on uninitialized memory, which might lead to issues for not primitive types.

This PR should be merged after libcu++ supports device lambdas in invoke result: https://github.com/NVIDIA/libcudacxx/pull/284

:warning: Breaking changes:

AgentReduce:

now has extra template parameter representing the accumulator type.
ConsumeTile uses accumulator type for thread aggregate instead of output iterator value type.
ConsumeTile returns accumulator type instead of output iterator value type.

DeviceReduceKernel doesn't accept output iterator as a template parameter. Apart from that, it now accepts accumulator type.
DeviceReduceSingleTileKernel now accepts accumulator type.
DeviceSegmentedReduceKernel now accepts accumulator type.
DeviceReducePolicy now accepts accumulator type instead of input iterator value type. It also doesn't accept output iterator value type now.
DispatchReduce:

now accepts accumulator type as last parameter.
now accepts initializer type instead of output iterator value type.
doesn't work with device extended lambdas now.
Constructor now accepts init as initial type instead of output iterator value type.

DispatchSegmentedReduce:

accepts accumulator type as last parameter.
accepts initializer type instead of output iterator value type.

Thread operators now accept parameters using different types: Equality, Inequality, InequalityWrapper, Sum, Difference, Division, Max, ArgMax, Min, ArgMin.
ThreadReduce now accepts accumulator type and use different type for prefix
Default accumulator type is now selected by introspecting return type of the reduce operator.

Breaking changes

Thanks for writing this up! Can you edit the PR description/first comment and add this to it? I'm less likely to overlook it that way :)

Breaking changes

Thanks for writing this up! Can you edit the PR description/first comment and add this to it? I'm less likely to overlook it that way :)

Sorry, didn't think about this aspect :smile: I'll definitely update the description.


Build fail with Visual studio 2010

Hi
I'm trying to build qpdf with visual studio 2010 because of my legacy project
However, an issue related to C++14 occurred.

There will be no possibility of building a current version of qpdf with such an old compiler. qpdf's requirement for C++11 is deep as it relies on thread-safe static initialization, and lambdas and other C++11 and 14 features are pervasive throughout the code. You may be successful with qpdf 9.0.2 or older as 9.1.0 was the first version to require a modern compiler. There were some performance issues in the 9 versions that were fixed in 10, but they would only be noticeable on very large files. Supporting a non-C++-14 compiler is a non-goal for qpdf at this time.

Thanks for your answer so quickly


[format -> prettyprint] Redirect (fixes #876)

Fix extraction to use src/prettyprint instead of src/format, and remove
src/format completely, since it is redundant. (Fixes #876)
Signed-off-by: Ramkumar Ramachandra<EMAIL_ADDRESS>

The latest CI error seems to be
https://everestlogstorage.blob.core.windows.net/fstar-linux/buildlogfile_FStar-Linux-20190430-19.html

Can you access this, by the way?
https://everestlogstorage.blob.core.windows.net/fstar-linux/buildlogfile_FStar-Linux-20190430-19.html

Thanks for the build log -- yeah, I was able to access it. Fix was simple enough.

Fixed.

This CI failure has nothing to do with your PR, but more of a CI / VSTS issue:
Retrieve extra VSTS build information
Unhandled: Request error with code: '401'.

I would have expected a snapshot diff in src/ocaml-output. Did the printed output really not change?

I would have expected a snapshot diff in src/ocaml-output. Did the printed output really not change?

I thought our official policy was to not burden contributors with updates to src/ocaml-output -- that should be taken care of automatically by the CI? See CONTRIBUTIONS.md

@catalin-hritcu @artagnon: I don't think this should have been merged in its current form.
I realize that CONTRIBUTIONS.md says that we should let the CI system push a snapshot automatically. But, that's a mistake there. The CI system does not refresh snapshots automatically: it cannot, since master is locked. I think we've discussed this issue at the F* meetings, and @protz  had a suggestion to create another unlocked staging branch for snapshot refreshes.
Until we fix this issue, I think we need to explicitly kick snapshot refreshing builds on the CI system on a branch of your choice before merging to master. I've done that now on a separate branch and will merge it into master if/when I get a green.
Put another way, I don't think we should merge to master unless we have a full green from CI, unless we have a specific, good reason for why we want to temporarily introduce some partial breakage.

Let's fix CONTRIBUTIONS.md then, we both did precisely what the documentation said we should do.

Yes, see a separate PR for the update to CONTRIBUTIONS.md
Not trying to blame you for a mistake or anything. But, the workflow here just revealed a bug in our process.

The CI system does not refresh snapshots automatically: it cannot, since master is locked.

Hm, what does dzomo do then? See 24e300200434 for instance.


Adding Dark Mode Feature

This would be very helpful for users while studying for long hours. They can switch between dark and light mode as needed.

@Yashshukla11 i would like to contribute to this issue... kindly assign me

I am here as GSSOC'24 contributor. Can you please add the lable to issues like level 1.

@Yashshukla11 I would like to work on this issue under GSSOC'24. Please assign it to me.

hey! i would like to contribute to this issue...please assign this task to me.

@Yashshukla11 i would like to contribute to this issue... kindly assign me

@Yashshukla11 I have finished working on the feature, please check the pull request and let me know if I need to change anything


UI: fix unable to scroll on 'Regulatory' page

grabGesture doesn't always work in dialog's exec() in QT 5.
it seems that the only reliable way for scrolling in QDialog is to use  show() instead of exec()
resolve: https://github.com/commaai/openpilot/issues/24808#issuecomment-1172288970

After this change the main event loop wouldn't be blocked anymore to wait for the result. Is there any way we can wait for the widget to be closed and return the proper status (OK or cancel).

You can probably just call QCoreApplication::processEvents() in a loop until the dialog is done.

You can probably just call QCoreApplication::processEvents() in a loop until the dialog is done.

This will make the bug reproduce like QEventLoop::exec in QDialog::exec()

Scrolling works just fine if you remove enough elements to make the Device page non-scrollable. It seems like if your page with the button can scroll like it does now, these are the sequence of events:
obj: "MainWindowClassWindow", evt: QEvent::MouseButtonPress
"qt_scrollarea_viewport" QEvent::ScrollPrepare
obj: "MainWindowClassWindow", evt: QEvent::MouseButtonRelease
"" QEvent::MouseButtonPress
"" QEvent::MouseButtonRelease

However if the page doesn't scroll (Regulatory scrolling works fine):
obj: "MainWindowClassWindow", evt: QEvent::MouseButtonPress
"qt_scrollarea_viewport" QEvent::ScrollPrepare
"" QEvent::MouseButtonPress
obj: "MainWindowClassWindow", evt: QEvent::MouseButtonRelease
"" QEvent::MouseButtonPress
"" QEvent::MouseButtonRelease

We'll also need to block the event loop, as the new internationalization PR relies getting the result from a scroll view in a dialog box.

If you click a button on the Software page you can also see it immediately shows pressed style state, while Device takes half a second to enter pressed state.

I just realized this. It may be this problem that caused the gesture recognizer's error

It seems that setting MousePressEventDelay to a tiny value can also solve this issue https://bugreports.qt.io/browse/QTBUG-67210?focusedCommentId=464719&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-464719 :

lgtm, haven't found any side effects so far

Looks good! However I was testing out on the Network page, if you scroll around repeatedly it's somehow easier to accidentally press networks, then it seems like you need to press twice to register a touch to cancel out.

It seems that ElidedLabel should emit clicked  like QPushbutton to work correctly with QScroller, instead of simply detecting mouseReleaseEvent
https://code.woboq.org/qt5/qtbase/src/widgets/widgets/qabstractbutton.cpp.html#_ZN15QAbstractButton14mouseMoveEventEP11QMouseEvent

Horary for it being fixed!
I don't feel so bad for wasting a few hours trying to figure this issue out to try to get a commit in... turns out it was a decently hard one!


Save selected (or all) colour schemes in localstorage

That way we don't need to fetch and parse the schemes on extension load. And then we can use that when rendering the colour scheme selector.

Done 567c5b2


How to pause recording?

I'm developing an app in which user can pause recording voice and than resume the recording from same point where it was paused. Is it possible to achieve this functionality with this plugin?

I'm sorry but this plugin does not support pausing.
maybe you can perform several recordings and combine them?

I'm sorry but this plugin does not support pausing.
maybe you can perform several recordings and combine them?


CAMEL-18447 Camel-pubsub: AsyncTaskException: Asynchronous task failes

fixes: https://issues.apache.org/jira/browse/CAMEL-18447

I'm switching to the draft as I can see some warnings in IT tests (using mocked backend)

@JiriOndrusek can you please backport to 3.18.x too?

I'll do that

Backport PR: https://github.com/apache/camel/pull/8667


V2 Changelog

The v2 of react-async-states will be deeply integrated with react (even with the core part) and will include several breaking changes.
API removal
useAsyncState options

wait will be removed
events.change will be removed
fork and forkConfig will be removed
concurrent will be removed (new API will be introduced)

useAsyncState return value

all properties accessible from the source property will be removed, this includes: run, runc, replay, abort, invalidateCache and so on. These properties are all copied from the source, so please use them from there. Better for the library and your apps.

Utilities

Sources.of and Source.for will be removed, createSource and getSource remain.
useSource and useProducer will be removed, they are literally a return useAsyncState()

API rename
Hydration
The Hydration component will be renamed to Provider that would allow global configuration, hydration and suspense streaming.
useAsyncState will be shortened to useAsync
Mental model change
aborted status
After gathering several feedback internally and from the practice, we found than managing several states isn't good and mostly forgotten. Especially the aborted state which can be combined with the Error state. This will reduce a generic parameter when using typescript and less code/branches to deal with.
boolean status
useAsyncState will return isInitial, isPending, isSuccess and isError, along with data and error properties. (the state property will remain as a source of truth and allow gradual adoption).
signal
The producer will receive an AbortSignal in the props
generators
Generator support will be via a plug-in or runners system to be defined, but will stay out of the box in the library, at least in v2. Generators support remains (may be it will be removed though).
The provider
The provider will allow injecting global or scoped configuration to state instances created in its territory. Also, it would allow tunning the states to hydrate/exclude.
States GC
States will be removed
New APIs
### useData
const data= useData(config, deps) // suspends and throws, like React.use

Async component
will offer a great api to do it all at once in a declarative way: tune pending and error states, hydration ... etc

as of beta-4, everything is okey


Requirments section in vdx/README.md file

Pack (VDX)
Documentation udpate relative to the requirements of packages for the "vdx" pack install

Thanks for submitting this. We should really do a proper README, with more info about the pack purpose, and how to use it, but this is a start.