How to differentiate static methods from instance methods

Original GitHub issue https://github.com/dotnet/dotnet-api-docs/issues/1787 from @slear
It seems that we have lost this information in the new docs. Process.Start(StartInfo) is static but it is really hard to understand this fact from the current documentation. In the previous msdn we had that "nice" icon.

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

ID: 4f838bcf-d93c-65a7-b629-e6027d267dbb
Version Independent ID: 25676ecc-5687-b317-e275-4b79e96c69c1
Content: Process.Start Method (System.Diagnostics)
Content Source: xml/System.Diagnostics/Process.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

And this is what we had on MSDN before:

vs. docs

YES! @BillWagner  This needs fixing!

ping @dend More customer feedback on this issue.

He's using @dendeli-msft now for work stuff

@mimisasouvanh this should be tracked internally as part of .NET API improvements

Will be very happy when this is improved

#log-suggestion


Next Link is named correctly and no longer duplicated

Fixes https://github.com/Azure/autorest/issues/2219
PTAL
@jhendrixMSFT @marstr

@mcardosos,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

consider this as passing
Retriggered locally, went through. Sorry about the servers failing, we're fine tuning auto-publishing on PR merge right now...

publish job


MIEngine: Fix multi-breakpoint gdb/mi information parsing

This PR fixes gdb/mi breakpoint information parsing for breakpoints that bind to multiple locations, which have a "<MULTIPLE>" in the addr field. According to https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Breakpoint-Information.html#GDB_002fMI-Breakpoint-Information the locations field contains the list of locations for this breakpoint type. This list of locations is used then to create the bound breakpoints for the specific breakpoint.
Signed-off-by: Andria Pazarloglou<EMAIL_ADDRESS>

@apazarlo Thank you for your contribution!


chore: add protos to gen-check and regenerate protos

What this PR does / why we need it:
Generate also protos as part of make gen-check. This will prevent from merging non updated pb files when updating google.golang.org/protobuf or google.golang.org/grpc/cmd/protoc-gen-go-grpc versions like here.
Which issue(s) this PR fixes:

Fixes #

/retest


Istio is giving 503 error with no healthy upstream error message when pods get evicted and comes back up.

Bug description
Ideally pods goes down and come up when there are lack of resources on individual nodes to other nodes. During this time when it happens across multiple times and incase if it is taking a while for pod to come up, istio is still giving “no healthy upstream” error on browser when the external url for the pod is hit. Can anyone help me with this. Do I need to add any external flag or do I need to do any application level change. One solution I found is virtualService have retry strategies like attempts and perTryTimeout. But I don’t feel this is the right way to be implemented in production, either it should be something can be implemented in istio-proxy or istio-ingressgateway to get ride of this.
Affected product area
Production
Istio ingressgateway and virtualservice
Expected behavior
When pods go to evicted state and comes back up istio should be able to route the traffic seamlessly.
Steps to reproduce the bug
When pods get evicted due to memory hike and new pod comes up. The istio shows an error "no healthy upstream" even though pod comes up successfully and application is running fine.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
1.4.2
How was Istio installed?
Istio is installed using helmchart
Environment where bug was observed (cloud vendor, OS, etc)
Cloud

@istio-policy-bot can you please provide an update regarding this issue. Our production systems are getting affected with on daily basis and we are holding them up with some temporary work arounds. Kindly do the needful at the earliest possible.

Team, Any update on this ?

@chandra210893 did you fix this issue, I have the exactly same problem.


Split binding.gyp into smaller .gypi files.

We need a modulization for binding.gyp.
Reference: https://gyp.gsrc.io/index.md

Fixed by #21


docs: in getting-started.md, "locally perhaps should be "globally" instead?

Describe the bug
https://github.com/netlify/cli/blob/82e60e4f0d3cdc7efad5065276ae01650bd154b1/docs/getting-started.md?plain=1#L13-L19
In the snippet above, the bullet point says that we should install netlify-cli locally, but immediately in the snippet after, we are asked to install it globally (with -g). I was confused when I first read it, and I think it can be improved.
To Reproduce
N/A
Configuration
N/A
Expected behavior
Perhaps, either change it to "globally", or remove the "locally"? Not sure. I think both can work, especially given the fact that we already do a disclaimer after for CI environments.
CLI Output
N/A
Additional context
N/A

Great catch @imballinst, would you like to submit a PR for it?

@erezrokah sure! I have prepared a branch. I'll submit a PR in a bit. Thanks for the response!


Adding cellular automata

Adding cellular automata to automata sections.

Could you add some test cases?

We don't plan on adding any dependencies (like PIL). Closing this PR. Feel free to open PR if the algorithm can be rewritten minimally, with tests. Thanks.


Change helix order, Add additional grantees, and update Ethereum projects

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[X] You have updated the .github/CODEOWNERS file according to your changes.
[X] You have registered new documents to /sidebars.js if any.

@jennifertrin The Gitcoin Client logo seems to be missing.

@jennifertrin The Gitcoin Client logo seems to be missing.

Apologies, can you please take a look now?


Undo performing wrong change

This is a very obscure bug. I've been working for many hours over the course of multiple days without restarting the program.
I pressed undo and for some reason it removed some earlier change instead a recent one. This has never happened before and restarting the program fixed the issue.
I don't have a consistent replication procedure, but maybe the data structure that you use to store the sequence of changes filled up (if thats even possible)?

Should be resolved in 0.1.6. Re-open if something goes wrong!


Update README

Add instructions for building on Windows

WSL installation
Downloading runtime dependencies
Building and deploying

Consider creating a release and using it in the instructions.


socket.io https://github.com/socketio/socket.io/

socket.io
https://github.com/socketio/socket.io/
Realtime application framework (Node.JS server)

move to https://github.com/seanmars/notes/issues/30


rangify readLink and symlink

Removing @safe from the signatures so that attribute inference takes
care of things. There are @safe unittests already, ensuring that the
functions themselves don't do anything unsafe.
Replacing @trusted declarations with @trusted function literals. This
way it's more clear that the specific call is @trusted, not the called
function.

The differences were just because I had done the two separately and squashed the commits later. Now using ElementEncodingType and one overload + static if for both. Also added those spaces.

Last activity was a week ago. Can I get some more review on this?

Please rebase

Please rebase

done

done

And rebase again ...

And rebase again ...

Done again.

LGTM

Done again.

Ehm.. rebase again

Ehm.. rebase again

Done again. The conflicts have only been in changelog.dd so far.

Auto-merge toggled on

The conflicts have only been in changelog.dd so far.

-> hopefully soon fixed by #4228


Filter to just BDC for create new controller action

Coverage remained the same at 35.857% when pulling a4d50b47bdd59921f61b18b0ea00cf16e19ae5e3 on chgagnon/filterBDC into 399bac33f41255b00916918581dbbbfbc5879465 on main.


Removed some language

Preview is available here:http://developers-pr46.previews.kube001.services.stellar-ops.com/docs


[docs] Add Cryptoverview to the showcase

This adds Cryptoverview, our latest Material-UI project, to the showcase.

Cryptoverview is a responsive webapp that displays a user's Bittrex portfolio, trending currencies and market caps. It provides some fancy charts, news related to cryptocurrencies, and more.

If you want, I can provide some demo credentials. It uses (or will use) almost everything I contributed to Material-UI 1.0 (e.g. table pagination was implemented for Cryptoverview's order tables), so there will be a lot to see and there is still a lot yet to come. :sunglasses:

demo/demo are demo credentials btw., if someone wants to give it a shot :wink:


Print times as benchmarks are being run.

Before this change, the console reporter would tell you that it was
running a benchmark, but wouldn't tell you when it finished a given
benchmark, and it also wouldn't tell you how long it took to run
the benchmark. It's useful to know which benchmarks are taking a long
time so that you can tune the number of iterations to maintain rapid
development cycles.
This change adds the support for recorders to maintain state, by
marking the protocol as having mutating func's. Additionally, it
upgrades the console reporter to print out these stats as it goes.
Note: I had to import libc in order to call fflush. (print
apparently flushes when you include the trailing newline, but doesn't
flush if you don't!) While we'll need to upgrade support when we want
to add Windows support, we'll also need to add CMakeLists.txt (among
other files), so I figured this was okay for now.
Example output with this change:
saeta-macbookpro2:penguinoss saeta$ time swift run -c release Benchmarks --filter "(join|Condition)"
[1/1] Compiling Benchmark Benchmark.swift
running NonBlockingCondition: notify one, no waiters... done! (11.14 ms)
running NonBlockingCondition: notify all, no waiters... done! (10.74 ms)
running NonBlockingCondition: preWait, cancelWait... done! (11.60 ms)
running NonBlockingCondition: preWait, notify, cancelWait... done! (15.43 ms)
running NonBlockingCondition: preWait, notify, commitWait... done! (23.53 ms)
running NonBlockingThreadPool: join, one level... done! (1342.32 ms)
running NonBlockingThreadPool: join, two levels... done! (8510.32 ms)
running NonBlockingThreadPool: join, three levels... done! (18988.01 ms)
running NonBlockingThreadPool: join, four levels, three on thread pool thread... done! (12.31 ms)

name                                                                   time       std                   iterations
------------------------------------------------------------------------------------------------------------------
NonBlockingCondition: notify one, no waiters                           69.0 ns    ± 64.08242553225121   100000
NonBlockingCondition: notify all, no waiters                           67.0 ns    ±<PHONE_NUMBER>0821058  100000
NonBlockingCondition: preWait, cancelWait                              79.0 ns    ± 75.57583948250084   100000
NonBlockingCondition: preWait, notify, cancelWait                      119.0 ns   ± 63.243341556531554  100000
NonBlockingCondition: preWait, notify, commitWait                      205.0 ns   ±<PHONE_NUMBER>4833453  100000
NonBlockingThreadPool: join, one level                                 677.0 ns   ±<PHONE_NUMBER>2686554  100000
NonBlockingThreadPool: join, two levels                                2088.0 ns  ±<PHONE_NUMBER>328494   100000
NonBlockingThreadPool: join, three levels                              6583.0 ns  ±<PHONE_NUMBER>996729   100000
NonBlockingThreadPool: join, four levels, three on thread pool thread  6349.0 ns  ±<PHONE_NUMBER>2243387  100

real	0m31.657s
user	0m55.243s
sys	0m1.270s

I must say, with the new adaptive iterations, printing out the times taken for each test is pretty sweet. :-)
saeta-macbookpro2:penguinoss saeta$ time swift run -c release Benchmarks --filter "(join|Condition)"
[3/3] Linking Benchmarks
running NonBlockingCondition: notify one, no waiters... done! (3149.87 ms)
running NonBlockingCondition: notify all, no waiters... done! (3195.64 ms)
running NonBlockingCondition: preWait, cancelWait... done! (3194.05 ms)
running NonBlockingCondition: preWait, notify, cancelWait... done! (1438.78 ms)
running NonBlockingCondition: preWait, notify, commitWait... done! (1979.75 ms)
running NonBlockingThreadPool: join, one level... done! (1651.06 ms)
running NonBlockingThreadPool: join, two levels... done! (2335.93 ms)
running NonBlockingThreadPool: join, three levels... done! (1575.93 ms)
running NonBlockingThreadPool: join, four levels, three on thread pool thread... done! (21.33 ms)

name                                                                   time        std                   iterations
-------------------------------------------------------------------------------------------------------------------
NonBlockingCondition: notify one, no waiters                           47.0 ns     ±<PHONE_NUMBER>1042615  28866097
NonBlockingCondition: notify all, no waiters                           49.0 ns     ±<PHONE_NUMBER>7666368  28938849
NonBlockingCondition: preWait, cancelWait                              65.0 ns     ±<PHONE_NUMBER>2241449  21986719
NonBlockingCondition: preWait, notify, cancelWait                      99.0 ns     ±<PHONE_NUMBER>5520546  10000000
NonBlockingCondition: preWait, notify, commitWait                      198.0 ns    ±<PHONE_NUMBER>5831212  7498818
NonBlockingThreadPool: join, one level                                 722.0 ns    ±<PHONE_NUMBER>4126587  84967
NonBlockingThreadPool: join, two levels                                2270.0 ns   ±<PHONE_NUMBER>738517   15801
NonBlockingThreadPool: join, three levels                              5310.0 ns   ±<PHONE_NUMBER>3195727  11258
NonBlockingThreadPool: join, four levels, three on thread pool thread  10408.5 ns  ±<PHONE_NUMBER>4109795  100

real	0m29.232s
user	0m33.171s
sys	0m1.663s

I'll send a separate PR to reduce the default max iterations setting down from 1 billion down to 1 million, as that seems sufficient. :-)

@saeta The new output you provided as an example looks great!


[WIP] GCC2019 CoFest Generic Introduction to Galaxy

Introduction -slides modification
Galaxy 101 for every one (new tutorial based on "Journals for pubs" list)

From Issue #1465

The slides "Introduction to Galaxy" are ready for review.

I think the answer is no, but is there a way to see the "compiled" version somewhere ?

Great job! Seems ok for me (noly based on the content, not the rendering ;) )

+1000Le 6 juil. 2019 13:53, Michele Maroni<EMAIL_ADDRESS>a écrit :@michelemaroni89 commented on this pull request.
In topics/introduction/slides/introduction.html:

???

The Galaxy Team is composed by bioinformaticians and software engineers
OHSU = Oregon Health & Science University
+- Customize the number of public resources

The idea is to explain a workflow by comparing it with cooking recipes.
The reason is that we want to prepare an explanation for users researchers, citizens and hobbyists that are not familiar with data intensive research.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.

Thank you for initiating the Galaxy 101 for everyone. Will have a look ASAP. A question coming to my mind is that tools using regular expressions or things similar (like the awk tool ) are very powerful and maybe the more "it" oriented thing we can ask a generic user to understand and use. For sure we have to create a dedicated training but maybe it is relevant to introduce these powerful things here.... or on a advanced 101 for everyone ?

@yvanlebras Great idea! We just did not know this tool was available in Galaxy!!!
We could for instance select rows where  Val1 > sepal length > Val2
What do you think?

Why not ;) One problem can be that the awk usegalaxy.eu tool is not working properly for now... Maybe an occasion to look at this ?

What does it mean : doesn't work properly ? Is there an issue somewhere ?

I don't know, we just saw that this week with @sbenateau for our tuto. The tool don't submit a job, but this is maybe "just" a transient .eu instance issue? Maybe exchange with @erasche directly to look at this

It has some security issues that we need to address ...

Thank you! So maybe we can, at least for now, taking another tool like filter data on any column or slect line that match an expression, something like that ? What do you think @annefou ?

Sure. I suggest we first finalize a very simple workflow and then work on improving it.

the website after this PR is deployed here: https://training-material-prev-pr-1473.herokuapp.com/

@martenson Is it always true or do we need to do something on our side to deploy at https://training-material-prev-pr-1473.herokuapp.com/
We are getting ready with our tutorial and it would be nice to review from https://training-material-prev-pr-1473.herokuapp.com/
Thanks.

Let me know when you need it. I can trigger the deployment again but then it will last only few hours (we will need to see how to make it longer on the long run)
So better to tell me when you need it

Ok! It makes sense. No urgency.  Le's look at it next week (if you have time). This afternoon, I am taking part of "Fridays for Future global climate strike". #ClimateStrike
Thanks.

@erasche @martenson @nsoranzo '101 for everyone' is ready ! Thank you for reviewing !!

What a wonderful job! Thank you!!!! I just look at it and see a very little typo. Another comment is related to the "Changing the datatype" section -> it appears to me potentially of interest to add a warning as using the "pencil" space is a manual operation and here the user can force associating a bad datatype so this is better to use convertion tool if existing to be sure.

Another comment is related to the "Changing the datatype" section -> it appears to me potentially of interest to add a warning as using the "pencil" space is a manual operation and here the user can force associating a bad datatype so this is better to use convertion tool if existing to be sure.

Another (the maybe better) choice is to use the pencil icon > Edit Attributes > Datatype > "Detect Datatype" function. Format validations are applied, the same as the Upload tool's "autodetect datatype" function. This was a new feature added in release 19.05. Extremely useful to include in an intro tuto, IMO.

Another comment is related to the "Changing the datatype" section -> it appears to me potentially of interest to add a warning as using the "pencil" space is a manual operation and here the user can force associating a bad datatype so this is better to use convertion tool if existing to be sure.

Another (the maybe better) choice is to use the pencil icon > Edit Attributes > Datatype > "Detect Datatype" function. Format validations are applied, the same as the Upload tool's "autodetect datatype" function. This was a new feature added in release 19.05. Extremely useful to include in an intro tuto, IMO.

I am not sure to fully understand the requested changes; in the tutorial, we used the pencil to convert from CSV to tabular: is it what one should do?
For adding a note/warning: Would it be OK to add a note (after the conversion from CSV to tabular) on how to use the pencil icon to detect/validate the data format?

Another comment is related to the "Changing the datatype" section -> it appears to me potentially of interest to add a warning as using the "pencil" space is a manual operation and here the user can force associating a bad datatype so this is better to use convertion tool if existing to be sure.

Another (the maybe better) choice is to use the pencil icon > Edit Attributes > Datatype > "Detect Datatype" function. Format validations are applied, the same as the Upload tool's "autodetect datatype" function. This was a new feature added in release 19.05. Extremely useful to include in an intro tuto, IMO.

I am not sure to fully understand the requested changes; in the tutorial, we used the pencil to convert from CSV to tabular: is it what one should do?
For adding a note/warning: Would it be OK to add a note (after the conversion from CSV to tabular) on how to use the pencil icon to detect/validate the data format?

Converting is ok for me. Just If I'm not wrong there was a section where "manual" modification of datatype is proposed.
'''
Check the datatype. The datatype of the iris dataset is csv. Change datatype if it is different then csv.
'''
But answer proposed by @jennaj is really perfect! Cool to have this ""new"" feature!

Converting is ok for me. Just If I'm not wrong there was a section where "manual" modification of datatype is proposed.
'''
Check the datatype. The datatype of the iris dataset is csv. Change datatype if it is different then csv.
'''
But answer proposed by @jennaj is really perfect! Cool to have this ""new"" feature!

Yes! I got it now! I will change the section where we check the datatype (and use this new feature instead of "Change datatype" button.)

@abretaud Would you have time for reviewing ?

Thanks a lot @nagoue! I pushed some tweaks to the first half of the tutorial (let me know if it looks ok to you) will get to the second half soon :)
I was thinking, we could create a workflow as a final step and maybe rerun on the cars dataset from R? instead of species we'd have country of origin. Could really reemphasize the utility of Galaxy also outside of biology, what do you think?

@shiltemann  @abretaud thanks a lot for your feedback !!

Thanks everyone for this awesome contribution! :tada::tada:


Fix deprecation warnings for our use of set-output in GHAs

E.g. https://github.com/hpcflow/matflow-new/actions/runs/5033938296

Looks like there is still one leftover in matflow: https://github.com/hpcflow/matflow-new/actions/runs/5406858390

Sorry, forgot to update workflows in matflow... this PR should fix it.


How to enable ape?

I want to train EfficientNet. it need large cuda memery.  APE can reduce memory requirements.
it is easy to enable ape in pytorch:
with autocast():
output = model(images)
loss = criterion(output, target)
scaler.scale(loss).backward()
scaler.step(optimizer)
scaler.update()
so Where should I add it.

If you want to enable amp training, just add fp16 = dict(loss_scale='dynamic') in your config.
Otherwise, if you want to modify the training procedure by yourself, maybe you need to dive into mmcv, for example, the model forward is called in EpochBasedRunner.run_iter, and the optimizer backward is call in OptimizerHook.after_train_iter


[CT-2801] [Feature] add Macros to Lineage Graph (DAG)

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
DAGs are great for many reasons. Currently the DAG in the generated docs does not include macros, making it difficult to navigate through a maze of macros, which are often called by other macros, models, and other resources. Maybe we start with just the custom macros in the macros folder and go from there.
Existing resources in the lineage graph (1.5.1)

Mock-up of the feature... :)

Describe alternatives you've considered
Jump from file to file and read the code for each macro to determine the dependencies.
Who will this benefit?
Anyone who deals with macros :)
Are you interested in contributing this feature?
No response
Anything else?
No response

@ym-onprem Neat idea! Are you thinking that this would help with digging through complex webs of macros-calling-macros? Seeing all downstream resources which depend on a given macro — and, if that macro were to change, would be selected by state:modified?
Everything that's needed here should already be present in the manifest — every resource has a depends_on.macros attribute, including macros (if they call other macros). Note that there can be some subtle differences based on when a manifest is produced (https://github.com/dbt-labs/dbt-core/issues/5079): a post-parse/compile manifest will include only the macros called within a model's raw_code, whereas a post-run/build manifest will also include macros called within the materialization.
In my view, it's still appropriate for macro dependencies to be hidden from the standard DAG visualization. But perhaps as an additional layer, or another DAG viz...?
I'm going to transfer this over to the dbt-docs repo, since that's where the changes would need to happen. Candidly, our team isn't able to prioritize new feature development in dbt-docs, so this isn't something we'd be picking up ourselves.


TypeError: no implicit conversion of Hash into String

Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command /var/www/.rbenv/versions/2.3.0/bin/bundle install

What did you expect to happen?
I expected Bundler to...

What happened instead?
Instead, what happened was...

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried...

Have you read our issues document, https://github.com/bundler/bundler/blob/master/doc/contributing/ISSUES.md?
...

Backtrace
TypeError: no implicit conversion of Hash into String
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli/install.rb:75:in `expand_path'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli/install.rb:75:in `run'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli.rb:191:in `block in install'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/settings.rb:92:in `temporary'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli.rb:190:in `install'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor.rb:369:in `dispatch'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli.rb:22:in `dispatch'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/vendor/thor/lib/thor/base.rb:444:in `start'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/cli.rb:13:in `start'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/exe/bundle:30:in `block in <top (required)>'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  /var/www/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/bundler-1.15.3/exe/bundle:22:in `<top (required)>'
  /var/www/.rbenv/versions/2.3.0/bin/bundle:23:in `load'
  /var/www/.rbenv/versions/2.3.0/bin/bundle:23:in `<main>'
  /var/www/.rbenv/versions/2.3.0/bin/ruby_executable_hooks:15:in `eval'
  /var/www/.rbenv/versions/2.3.0/bin/ruby_executable_hooks:15:in `<main>'

Environment
Bundler   1.15.3
Rubygems  2.6.12
Ruby      2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux]
GEM_HOME  /var/www/konsys/{}/ruby/2.3.0
GEM_PATH
Git       <IP_ADDRESS>
Platform  x86_64-linux
OpenSSL   OpenSSL 1.0.1 14 Mar 2012

Bundler settings
build.nokogiri
  Set for the current user (/tmp/bundler/home/tuser/.bundle/config): "--use-system-libraries"
frozen
  Set for your local app (/var/www/konsys/.bundle/config): true
path
  Set for your local app (/var/www/konsys/.bundle/config): {}
disable_shared_gems
  Set for your local app (/var/www/konsys/.bundle/config): true
bin
  Set for your local app (/var/www/konsys/.bundle/config): "bin"

Gemfile
Gemfile
source 'https://rubygems.org'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '5.1.2'
gem 'activesupport'
# Use sqlite3 as the database for Active Record
#gem 'sqlite3'
gem 'pg'
# Use SCSS for stylesheets
gem 'sass-rails'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier'
# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.2.1'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'therubyracer', platforms: :ruby

# Use jquery as the JavaScript library
gem 'jquery-rails'
# Turbolinks makes following links in your web application faster. Read more: https://github.com/rails/turbolinks
gem 'turbolinks'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder'
# bundle exec rake doc:rails generates the API under doc/api.
gem 'sdoc', '~> 0.4.0', group: :doc

#gem 'protected_attributes'    # no longer supported in Rails 5
gem 'ancestry'
gem 'paranoia', "~> 2.2"
gem "cocoon"

# Gems for Devise & CanCan
gem 'devise'
gem 'cancancan'
gem 'net-ldap'

gem 'jquery-turbolinks'
gem 'jquery-ui-rails'
gem 'jquery-hotkeys-rails'
#gem 'jquery-validation-rails'
#gem "jstree-rails-4"

gem 'bootstrap-sass'
#gem 'bootstrap_form'
#gem 'bootstrap-typeahead-rails'
gem 'font-awesome-sass'
gem 'rails-i18n'

gem 'sparql-client'
gem 'sru'
gem 'sunspot_rails'
gem 'rsolr'
gem 'progress_bar'
gem 'kaminari'
#gem 'handlebars_assets'

#gem 'momentjs-rails', '>= 2.9.0'
#gem 'bootstrap3-datetimepicker-rails', '~> 4.17.47'
gem 'bootstrap-datepicker-rails'
gem 'bootstrap-timepicker-rails-addon'
#gem 'validates_timeliness'
#gem 'date_validator'

# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'

# Use Unicorn as the app server
# gem 'unicorn'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug'
end

group :development do
  # Access an IRB console on exception pages or by using <%= console %> in views
  gem 'web-console'

  # Spring speeds up development by keeping your application running in the background.

Can you share the contents of /var/www/konsys/.bundle/config? Thanks!

As requested, here the contents of /var/www/konsys/.bundle/config:
---
BUNDLE_FROZEN: "1"
BUNDLE_PATH:
BUNDLE_DISABLE_SHARED_GEMS: "true"
BUNDLE_BIN: "bin"

If you change the third line to BUNDLE_PATH: "", it should fix the issue, and future versions of Bundler will properly serialize the YAML

After changing the third line as indicated, 'bundler install' the error "TypeError: no implicit conversion of Hash into String" occured again and surprisely BUNDLE_PATH was replaced as originally.
It seems the config file is updated/rewrite during 'bundler install':
$ ls -lrt /var/www/konsys/.bundle/config
-rwxr-xr-x 1 www-data www-data 89 Aug 25 19:28 /var/www/konsys/.bundle/config
$ cat /var/www/konsys/.bundle/config
---
BUNDLE_FROZEN: "1"
BUNDLE_PATH:
BUNDLE_DISABLE_SHARED_GEMS: "true"
BUNDLE_BIN: "bin"

And that was with Bundler 1.15.4?

No, it was 1.15.3... But after update to 1.15.4 nothing changed, the error reoccured and the BUNDLE_PATH was again overwritten.

Damn, ok, thanks! I'll do my best to look into this

How had you originally set the path config setting?

I am not sure about which config setting are you asking for, could you be more specific please?
This issue occurs on a productive server with the intention to deploy a Rails app with Passenger.

The path setting

PATH=/var/www/.rbenv/shims:/var/www/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games`

I mean Bundler's path setting, the BUNDLE_PATH on in the config problem that is causing problems

Initially I haven't explicity set BUNDLE_PATH, just when you asked to change it to "" for test purposes. This attempt failed (see above).
Now I've repeated the test and I set BUNDLE_PATH: "~/.bundle", then I ran bundle install and Bundle completed without errors(!).

But it must have been set to something to have gotten into the config in the first place

You're right, but I don't know how and what have been set.
In any case I usually do not touch this file, actually I did know about its existence until you asked me to edit it.

In that case, I'm sorry, but I don't really know how to move forward. Without a way for me to reproduce the bug locally (the generation of the invalid config file), I don't know I can fix it

Yes, I understand you perfectly and I guess you can close this ticket, the error could be avoided by editing the config file.
Thank you for your time and energy!


Use different binary names for Firefox and Chrome

Rename the binary files of curl-impersonate so that the Firefox and
Chrome versions can co-exist on the same system. The Firefox version is
now named 'curl-impersonate-ff' and 'libcurl-impersonate-ff' and the
Chrome version is named 'curl-impersonate-chrome' and
'libcurl-impersonate-chrome'. The wrapper scripts look for these names
as well. Symbolic names with the old names are still created inside the
Docker images to keep compatibility as much as possible.

@matheusfillipe
This PR might affect the AUR packages, you might want to check and/or modify them. Alternatively you can link to a previous fixed numbered version. Anyway I'll not merge yet to wait for feedback.


Move querydsl-root to root directory

Part of #1132
I'll backport it if this looks good.

It looks good now in my opinion.

I am still looking. One moment.

It looks good in my opinion as wel.


A space was added after the comma

A space was added after the comma: ...импорт', если...
What problem have you solved?
There was no space after the comma in the translation.
How did you solve the problem?
Added a space
Have you written tests? Have you included screenshots of your changes if applicable?
Did you document your changes?
Just added a space after the comma in the translation

coverage: 100.0%. remained the same when pulling 44d069059d9097cfcfbb7825cd2b184d1f54d66e on bgelov:main into 042eec44d41c43eb57fe4b831336754b0d81b109 on django-import-export:main.


KVM2: getting URL, could not get IP: host is not running

Please help me.
essh@kubernetes-master:~$ docker-machine -v
docker-machine version 0.16.0, build 702c267f
essh@kubernetes-master:~$ docker -v
Docker version 18.09.6, build 481bc77
essh@kubernetes-master:~$ cat /etc/os-release |grep VERSION
VERSION="18.04.2 LTS (Bionic Beaver)"
VERSION_ID="18.04"
VERSION_CODENAME=bionic
Running pre-create checks...
Creating machine...
(vm1) Creating KVM machine...
(vm1) Setting up store path in /home/essh/.docker/machine/machines/vm1 ...
(vm1) Building disk image from https://storage.googleapis.com/minikube/iso/minikube-v0.0.0-unset.iso
(vm1) Downloading /home/essh/.docker/machine/cache/boot2docker.iso from https://storage.googleapis.com/minikube/iso/minikube-v0.0.0-unset.iso...
(vm1) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(vm1) Setting executable bit set on /home/essh/.docker/machine/machines/vm1 (perms=drwx------)
(vm1) Setting executable bit set on /home/essh/.docker/machine/machines (perms=drwx--x--x)
(vm1) Setting executable bit set on /home (perms=drwxr-xr-x)
(vm1) Creating domain...
(vm1) Creating network...
(vm1) Ensuring networks are active...
(vm1) Ensuring network default is active
(vm1) Ensuring network minikube-net is active
(vm1) Getting domain xml...
(vm1) Creating domain...
(vm1) Waiting to get IP...
(vm1) Found IP for machine: <IP_ADDRESS>
(vm1) Waiting for SSH to be available...
(vm1) KVM machine creation complete!
Error creating machine: Error in driver during machine creation: SSH not available after waiting: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
essh@kubernetes-master:~$
essh@kubernetes-master:~$ sudo docker-machine create --driver kvm2 vm3
Running pre-create checks...
Creating machine...
(vm3) Creating KVM machine...
(vm3) Setting up store path in /home/essh/.docker/machine/machines/vm3 ...
(vm3) Building disk image from https://storage.googleapis.com/minikube/iso/minikube-v0.0.0-unset.iso
(vm3) Downloading /home/essh/.docker/machine/cache/boot2docker.iso from https://storage.googleapis.com/minikube/iso/minikube-v0.0.0-unset.iso...
(vm3) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(vm3) Setting executable bit set on /home/essh/.docker/machine/machines/vm3 (perms=drwx------)
(vm3) Setting executable bit set on /home/essh/.docker/machine/machines (perms=drwx--x--x)
(vm3) Setting executable bit set on /home (perms=drwxr-xr-x)
(vm3) Creating domain...
(vm3) Creating network...
(vm3) Ensuring networks are active...
(vm3) Ensuring network default is active
(vm3) Ensuring network minikube-net is active
(vm3) Getting domain xml...
(vm3) Creating domain...
(vm3) KVM machine creation complete!
Error creating machine: Error in driver during machine creation: Error creating VM: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2019-06-10T04:14:28.228276Z qemu-system-x86_64: -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2: Failed to get "write" lock
Is another process using the image?')
essh@kubernetes-master:~$ sudo docker-machine ls
NAME           ACTIVE   DRIVER    STATE     URL   SWARM   DOCKER    ERRORS
swarm-node-0            generic   Timeout
vm1            *        kvm2      Running                 Unknown
vm2            -        kvm2      Stopped                 Unknown   getting URL, could not get IP: host is not running
vm3            -        kvm2      Stopped                 Unknown   getting URL, could not get IP: host is not running
essh@kubernetes-master:~$ sudo virsh list --all
 Id    Name                           State
----------------------------------------------------
 3     vm1                            running
 -     centos7                        shut off
 -     minikube                       shut off
 -     node-1                         shut off
 -     vm2                            shut off
 -     vm3                            shut off

Hello. This problem in virsh. Thanks anybody.


Does this work across application insight instances?

I assume it doesn't, I just would like clarification on this. Say my team logs our services to an application insights with instrumentation key "XYZ" and we provided the telemetry Id to another team and they tried to correlate their telemetry to that id and log it to their application insights at instrumentation key "ABC", would that even work? I assume it wouldn't, since the logs are in separate locations.

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

ID: 95aa5722-ec96-40fb-b03a-0c9e73c7a18c
Version Independent ID: 28259d9c-5174-f138-c0aa-bc2125c3be1a
Content: Azure Application Insights telemetry correlation
Content Source: articles/azure-monitor/app/correlation.md
Service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

@ththiem Thank you for the question!  We are investigating this and will get back to you shortly.

@ththiem You may have to expand on your scenario, but hopefully this answers your question.
I currently have two Application Insights instances set up (one for .NET and one for .NET Core).  If I use a query with an operation_Id from my .NET Application Insights resource, my .NET Core Application resource will return 0 results.  Your instrumentation key determines what telemetry gets linked:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/create-new-resource
"After you have created the resource, you get its instrumentation key and use that to configure the SDK in the application. The resource key links the telemetry to the resource."
You can, however, look at data from multiple resources at the same time if you want:
https://docs.microsoft.com/en-us/azure/azure-monitor/log-query/unify-app-resource-data
"This article describes how to query and view all your Application Insights application log data in one place, even when they are in different Azure subscriptions, as a replacement for the deprecation of the Application Insights Connector. The number of resources Application Insights resources that you can include in a single query is limited to 100."
Does that answer your question?

@ththiem We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


CARDS-2243: Improve the performance of the clinic dashboard tables

To test:

on the CARDS-2243-test branch
build with mvn clean install -Pdocker
in compose-cluster/mssql run python3 generate_test_proms_sql.py -n 1000 proms_sample.sql
in compose-cluster run python3 generate_compose_yaml.py --mssql --cards_project cards4proms --oak_filesystem --dev_docker_image --smtps --smtps_test_container --smtps_test_mail_path ~/cardsmail --composum --adminer --timezone America/Toronto
run docker-compose build ; docker-compose up
at http://localhost:1435/?mssql=mssql&username=sa&db=master&ns=path&import= import the generated proms_sample.sql file
open http://localhost:8080/Subjects.importClarity
wait for about 30 minutes for the import to finish and all the Survey events to be generated
log in as one or two of the patients and fill in and submit the surveys
log in as another one of the patients and fill in, but DON'T submit the surveys
as admin, open the clinic dashboard and check that the tables load in just a few seconds, showing around 900 visits for today and the submitted forms
create a new user and add it to the trusted users group
log in as the new user, open the clinic dashboard and check that it loads and looks just like for admin

Everything works well except for one thing. I created 2 users; added only one to the Trusted users group, however both users see all that dashboard displays for admin.


fix table test

and re-enable it.

https://github.com/twosigma/beaker-notebook/commit/56f956c97815f7186bfe2b1386d8b3022485656b


EventCollectionNftTransferred field of callback response is not correct in the official Japanese docs.

I found some wrong information about the field of EventCollectionNftTransferred in the Japanese official docs only. tokenId in EventCollectionNftTransferred is needed to change to tokenIds. In docs of English/한국어 it seems correct.
GET /v1/item-tokens/{contractId}/fungibles/thumbnail/{request-id}/status

Oops, sorry that mistake. I will fix it soon.

Sorry late fix, but we have patched the issue.
https://docs-blockchain.line.biz/ja/api-guide/Callback-Response#eventcollectionnfttransferred


Adding Spanish language (Español)

Description
Adding a new languaje for the docs.

Testing

Checklist
Things need to be done before this Pull Request can be merged.

[ ] Code is well-formatted and adheres to project style guidelines: cargo fmt
[ ] Code does not produce any clippy warnings: cargo clippy
[ ] All unit tests pass: cargo test
[ ] I added new unit tests, so other people don't accidentally break my code by changing other parts of the codebase. How?

The Website/Docs moved to https://github.com/Snowiiii/Pumpkin-Website


BranchSDK doesn't open links with "auth" in path

Hi,
I have an url in this form https://my-app.app.link/?path=auth.
When I open on device and in func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([Any]?) -> Void) -> Bool
I call Branch.getInstance().continue(userActivity) it returns false.
Changing auth in path to anything else(e.g. auth2, 'aut') Branch.getInstance().continue(userActivity) returns true.

That is due to a URL blacklist we have to prevent Branch from trying to open a URL with login credentials in it.
The blacklist is hosted on the Branch servers and we will update it today to fix this.

In the mean time, can you use a different value for the key, or pass the key in deep-link data?


bpf: implement creating and opening existing bpf.Maps using cilium/ebpf

This PR puts cilium/ebpf.Map at the core of Cilium's bpf.Map type, see #22513 for more context. Best reviewed per commit given its size. If you've been tagged for review and don't feel comfortable, please let me know so we can reassign. Don't hesitate to ping me offline for discussion or more context.
Part of: #22513.
Perform map creation and opening using cilium/ebpf API

/test

@ti-mo Sorry never got around to reviewing this,  are you planning to reopen?

@ti-mo Sorry never got around to reviewing this,  are you planning to reopen?

No worries, it's a draft. :) Will pick this up again in a few weeks.

/test

/test

@YutaroHayakawa I've had to make some changes to the way per-cluster CT maps are loaded from a pin, PTAL.
I think pinning inner maps there is not strictly necessary and creates quite some accidental complexity around managing pins. Also, 4 * 256 syscalls to attempt opening all possible pins on every single GC cycle. Map-in-map reads need RCU, but surely a few BPF_MAP_GET_NEXT_KEY calls on the outer map aren't that problematic? At least the latter would just block instead of hammering BPF_OBJ_GETs, leading to lower CPU usage?

/test

/test

Wrt the pinned maps, I totally agree that it introduces the complexity, but the time takes to iterate over the outer maps is significantly longer when we don't pin the inner map. For example, measurement in my local machine shows 5s for iterating single per-cluster map without pin and 600us with pin. Thus, with pin, 20s per GC.

Thanks for taking a look! Did you run a profile to check what these 5s were being spent on? Since this is an ARRAY_OF_MAPS, a lot of unnecessary work will be done to scan all keys. (4 * 256 syscalls) Have you considered making this a HASH_OF_MAPS instead? That would only result in entries + 1 syscalls for a full iteration.

/test-1.26-net-next

/ci-e2e

/test

/test

Have you considered making this a HASH_OF_MAPS instead? That would only result in entries + 1 syscalls for a full iteration.

No. That sounds like a good solution. I blindly used ARRAY_OF_MAPS because the max entries are 256 so far, and it gives a maximum lookup/update performance to datapath, but given the cost of map iteration, it's worth considering that. I'll put this into the task list.

/test-1.24-5.4

Runtime tests for pkg/bgpv1/test failing due to https://github.com/cilium/cilium/pull/25625.

/test-1.26-net-next

net-next is hitting https://github.com/cilium/cilium/issues/25524

Broadly I think the direction that this PR is pushing the codebase is the right path, reducing Cilium-specific syscall related code and relying more on the cilium/ebpf library :tada:
From a quick glance, the OpenOrCreate() replacement seems to retain the semantics we want, and I welcome the improvement on OpenParallel() to more accurately reflect the reality of what it does.

/test

Marked ready-to-merge as Travis' arm64 job is stalling on go vet (maybe due to many files touched, missing cache?) and net-next is currently kernel panicking. Nothing changed here that would cause a failure on net-next only. Not much point in re-running, this PR would otherwise remain blocked and in perpetual rebase hell.

/test


Added hossted as partner

Description
Adds hossted as a partner (after onboarding discussion with Kyle Davis
Issues Resolved
none
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Hello @liorkesos - wanted to follow up on this one

@liorkesos - wanted to follow up on this

@pajuric - wondered if you'd heard anything back from them - let me know, if not, I guess we'll close this out.

Hi guys, sorry for bkt being responsive.
I'll try to submit an altered logo ...

Hello @liorkesos - wanted to follow up on this.

Signed-off and trying to submit with the proper dimensions....

@krisfreedain - I tried to resubmit in the original PR - I hope i didn't make a mess...

Hello @liorkesos - looks good. Appears there is still a DCO issue though. I'll go ahead and see if I can redo it on your behalf.

hello @liorkesos - I've resolve the issues - welcome to the OpenSearch partner page!
https://github.com/opensearch-project/project-website/pull/1254


Add Custom Lun address Feature to add volume functions

Add additional parameters to functions to support this.

Added in next release


YAMS decodes empty string as nil

https://github.com/jpsim/Yams/issues/253
When YAMS encounters an empty string when decoding a YAML string to Swift objects, it decodes it as nil rather than as an empty string. This results in discrepancies between the original file and the round-tripped file.
As a workaround, replace all empty strings in the code model file with a space '' -> ' '

Workaround has been implemented. Leaving this issue open for tracking.


Convert all the existing folds to sliding folds

Make all the folds of type ... -> Fold m (a, Maybe a) b. Users can then use the slidingWindow combinator to use these folds on a finite window and use a map to (a, Nothing) to use these on infinite window.
The finite/infinite distinction would go away.
cc @adithyaov

This is fixed now.


Fixes https://github.com/kevmoo/git.dart/issues/3

this works for me but don't know if it's 100% correct. I'm just skipping those lines that doesn't match.

@dam0vm3nt – just seeing this.
Could you add a test?

Please rebase and add a test!


updated description in readme.md

There's also docs/README.md which is the landing page for the Github pages site.

@jbarrick-mesosphere I updated the docs/readme.md as well.  Can you take a look? If all looks good, please merge.

Thanks!


Dynamic Per Resource Timeouts

To prevent k8s resource types that take a long time to sync from prematurely crashing agent Pods upon init.  Adding per resource timeouts that do not timeout sync unless the watcher has exceeded the timeout period after the last informer event of that type to be received.
That is, each watcher records the time of the last event, per API resource type. If the K8s-Synced-Timeout is reached, only timeout if event of that type was not received during the timeout period.
As well, to facilitate diagnosing such issues, adding more labels to EventsTS metrics and refactoring all uses of this metric into a single GaugeVec.
Fixes: #18776
daemon,metrics: fix issue where long running initial k8s resource syncs where causing Cilium to terminate prematurely. Caches will now wait to timeout after the last resource event.

/test

/test

Trying to break PR down into multiple commits due to large number of changes. Will squash down later.

test failure seems like a flake: https://github.com/cilium/cilium/issues/12756

/test

@christarazi sounds good, I combined some of the metrics commits. I got myself into a bit of a mess with the commit history. Just trying to squash them in a way that makes sense now.

/test

I recently discovered the below handy git tricks, which might help for addressing review comments
# commit changes linked to original commit
git commit --fixup <the original commit>

# rebase with autosquash linked commits for clean commit history.
git rebase master -i --autosquash

GKE test failure seems real.

/test

/test

nm about the GKE tests - missed the memo about those not working. Everything else seems to be ok test wise.

/test

I recently discovered the below handy git tricks, which might help for addressing review comments
# commit changes linked to original commit, auto complete can be used for easier selection
git commit --fixup <the original commit>

# rebase with autosquash linked commits for clean commit history.
git rebase master -i --autosquash

Thanks yeah, I've been doing a lot of interactive rebasing. I just ended up mixing changes into commits which made reintegrating them back into the original commit tricky.
Definitely need to try to keep my commits smaller and more self contained.

@christarazi I squash down the last commit once you're done reviewing.

/test

/test

/test

1.23-kernel-net-next failing seems unrelated to branch

/retry

/test

/test-1.23-net-next


Automated Package Upgrade

:tada: This PR is included in version 25.6.62 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Orientation.lockToPortrait() throw a error

I was write it at componentDidMount(), but it throw a red error like this:
undefined is not an object(evaluating ‘Orientation.lockToportrait’)

I'm having a very similar issue on Android.
Cannot read property of 'lockToLandscapeLeft' of undefined.
import Orientation from 'react-native-orientation'
...
componentDidMount () {
  Orientation.lockToLandscapeLeft()
}

putting in a console.log on Orientation produces:
addOrientationListener: addOrientationListener(cb)
addSpecificOrientationListener: addSpecificOrientationListener(cb)
getInitialOrientation: getInitialOrientation()
getOrientation: getOrientation(cb)
getSpecificOrientation: getSpecificOrientation(cb)
lockToLandscape: lockToLandscape()
lockToLandscapeLeft: lockToLandscapeLeft()
lockToLandscapeRight: lockToLandscapeRight()
lockToPortrait: lockToPortrait()
removeOrientationListener: removeOrientationListener(cb)
removeSpecificOrientationListener: removeSpecificOrientationListener(cb)
unlockAllOrientations: unlockAllOrientations()
__proto__: Object

so the object is clearly loaded, but the function call is failing

Im also having the same issue as @ostigley

sup @puresamari .  I'm not sure @yamill has much free time to support this anymore.  But after doing some reading, I figured out you you can make it work with  the following:
var Orientation = require('react-native').NativeModules.Orientation
...
Orientation. lockToLandscapeLeft()

and it worked.   Winner Winner Chicken Dinner

Tried both options,

import Orientation from 'react-native-orientation';
As suggested by @ostigley , var Orientation = require('react-native').NativeModules.Orientation

But still gives error undefined is not an object(evaluating ‘Orientation.lockToportrait’)

You most likely don't have the latest version, when I did npm install, it didn't actually get the latest files (it downloaded the version that used OrientationPackage(this)), so I had the same error. The correct version should be OrientationPackage() in MainApplication.
Here's what I did to fix it and get it working.
Try to remove the react-native-orientation from your project with:
npm remove react-native-orientation
Then download the zip, rename it to react-native-orientation and copy/move it to your npm_modules folder. Then link it again.
react-native link react-native-orientation
Note you may have to remove all references of react-native-orientation from the Android project first before you can re-link it.

Just fork this repository and use npm install yourgitlogin/react-native-orientation. It works for me.

@danilvalov could you explain me why did it work?

@andfs the current version of the React Native Orientation package in NPM is not up to date. For now, just fetch the code directly from the repo like npm install --save react-native-orientation@git+https://github.com/yamill/react-native-orientation.git. The current version at master should have lockToPortrait() working on Android and iOS granted native linking/installing is correct. If error persist, please open another issue with an example code for us to look at and debug.

var Orientation = require('react-native').NativeModules.Orientation

thanks this works perfectly.

TypeError: null is not an object (evaluating 'Orientation.lockToPortrait')
Please provide me its solution


Scanning recalled serial numbers shows batch recalled

Step 1:
Create a batch with serial numbers updated in valid, recalled and decomissioned.
Step2.
Scan the recalled serial number
The mobile app show "Batch recalled"
Whereas it must show "Serial Number Recalled"


Workaround ansible.builtin.apt_key module bug in ansible 4.0.0

ansible.builtin.apt_key module has a know bug in ansible v4.0.0 https://github.com/ansible/ansible/issues/74424 which is fixed in the version 4.0.1 that will be released on May 24. Until that use ansible.builtin.get_url module instead

@dmitryax How about creating conditional task that can handle the version with something like when: ansible_version.full is version('4.0.0, '==')?

@dmitryax How about creating conditional task that can handle the version with something like when: ansible_version.full is version('4.0.0, '==')?

Thanks Jeffrey! Good point.


Add: Pug.js (ex: Jade)

Add LSP for Pug.js
LSP: https://github.com/opa-oz/pug-lsp
LspConfig: https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/server_configurations/pug.lua

^^^ PR for your convenience 🙇


[$250] Web - Dependent tag choices are cleared and actions are repeated when coming online

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.18-3
Reproducible in staging?: Y
Reproducible in production?: Y
The issue was found when executing this PR https://github.com/Expensify/App/issues/44995#issue-2396295781
Issue reported by: Applause Internal Team
Action Performed:

ND: Navigate to https://staging.new.expensify.com/
ND: Log in with a New Gmail account
ND: Create a workspace
ND: Switch to OD by navigating to Account settings - Cards & Domains
OD: Navigate to Settings - Workspaces - Group - Created workspace - Tags
OD: Enable "Use multiple levels of tags"
OD: Click on the "Import from Spreadsheet" button
OD: Uncheck "Are these independent tags?"
OD: Upload the attached CSV file
ND: Navigate to the workspace chat
ND: Go offline
ND: Navigate to Composers "+" button - Submit expense - Manual
ND: Input any amount and click on "Next"
ND: Set any value for "Merchant" and submit the expense
ND: Click on the created expense
ND: Click on "State" and select any value
ND: Click on "Region" and select any value
ND: Click on "City" and select any value
ND: Click on "City" again and click on the set value to clear it
ND: Go online

Expected Result:
Changes made while offline should be displayed instantly when coming online.
Actual Result:
Dependent tag choices are cleared and actions taken while offline are slowly repeated when coming online.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Bug6565973_1723145169511!Dependent_tags_tags.csv
https://github.com/user-attachments/assets/31709e85-62a4-4b7c-82aa-8ee846db6e4a

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0100368f8944905925
Upwork Job ID:<PHONE_NUMBER>785640856
Last Price Increase: 2024-08-12

Issue OwnerCurrent Issue Owner: @Pujan92

We think that this bug might be related to #wave-collect - Release 1

@miljakljajic  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

This looks like a legit issue related to offline handling of requests, but not related to https://github.com/Expensify/App/pull/45760 or https://github.com/Expensify/App/issues/44995

Waiting for proposals

@cead22 am I wrong thinking this could be handled externally?

I thought the same, but I could see how this might be a tricky issue to fix. Should we close it?


Consider dropping invoke and just using fabric for everything (or stop using SSH).

Invoke is just Yet Another Moving Part, and maybe causes confuses on where you should look for tasks. We could merge all the invoke tasks into the basic fabfile.py and get rid of tasks.py from the directory layout altogether. (suggested by @dan-blanchard)

Alternatives: use paramiko directly instead, or stop using SSH altogether.
@dan-blanchard says:

I'd rather see us ditch trying to SSH into machines at all and rely on Storm's hook support to run a little JVM code that sets up the virtualenv. See our discussion here: https://github.com/Parsely/streamparse/issues/99#issuecomment-94007564 #99

@dan-blanchard says:

SSH is entirely optional at this point. You can set use_ssh_for_nimbus and use_virtualenv to False in config.json and you won't need to SSH into anything. This is described here http://streamparse.readthedocs.org/en/stable/quickstart.html?highlight=use_virtualenv#disabling-virtualenv-creation
We rely on the REST API for getting stats, and sparse list/kill will only use ssh if use_ssh_for_nimbus is set. The only commands we have that definitely would use SSH right now are remove_logs, tail, and update_virtualenv. We could likely hook into the REST API's newly provided access to logs to handle tail for us (and not worry about remove_logs), which would only leave update_virtualenv, which should be replaced by the hook approach I mentioned before.

I dropped invoke from the requirements, now that fabric3 is Python 3 compatible


Edit: One TV Cinema 2

Channel ID (required)
OneTVCinema2.kh
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
http://<IP_ADDRESS>:5080/LiveApp/streams/topmusic.m3u8
Languages
No response
Categories
No response
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
No response
Notes
No response

Please update your request:

broadcast area code is incorrect

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Links are in iptv-org/iptv, not in here.


Improve google identity token get

Add check for internal google link + better Attribute error catch
Changes the configuration template which generates into useful code

Codecov Report

Merging #224 (2824d5e) into dev (3cddc9a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #224   +/-   ##
=======================================
  Coverage   54.99%   54.99%
=======================================
  Files          59       59
  Lines        4224     4224
=======================================
  Hits         2323     2323
  Misses       1901     1901

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 3cddc9a...2824d5e. Read the comment docs.


[sui-execution] Move compatibility check impl into execution layer

Description
This change allows us to clean-up protocol config use in the later versions of the execution layer (to follow).
Test Plan
All existing tests
Stack

#12740
#12741

Landed via #12785


Use the main branch of Transformers in CI

What does this PR do?

This PR enables to perform slow tests and to detect example differences with the Transformers' main branch as opposed to the last release.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


gmrender-resurrect: mark as broken

Motivation for this change
The build fails on master.
CC @k0ral
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1


extend jwk cert store

upstream https://github.com/square/go-jose/issues/95

Without support from go-jose, the library needs to be forked and the functionality added. the specification for x509 certificates is available at https://tools.ietf.org/html/rfc7517
Until that is implemented, the HTTPS TLS certificate is gob encoded and stored as a PSK in the JWK store. It should be documented that the JWK store does not support the x509 claims as of now.
This approach is okay because:

There is no security impact. PSKs are encrypted using AES-GCM as well
It is not trivial to add a new TLS certificate using the HTTP REST API. this could be documented somewhere. importing TLS certificates still works!
One draw back is that clients need to be able to decode gob streams. As the certificate will be used only internally in hydra, this is not an issue.

ecdsa uses a private struct as interface value (elliptic.p256Curve) so it's not possible to use gob encoding without a lot of workarounds. darn.

HTTP/2 does not support weak-ciphers like RSA.

There's not field for it in the struct right now, but it should be fairly simple to add. I can take a look at adding this next week maybe. Or if you want to take a shot at it, pull requests are welcome!

https://github.com/square/go-jose/issues/95#issuecomment-223764077


ImageCapture API available?

A search for "image capture" doesn't show any results.
https://www.w3.org/TR/image-capture/
Regards.

Duplicate of #2887


Script to test few selected packages

This is a hacky script which does the job now. I will improve on this further tomorrow. We need a proper way of storing the ported packages in some configuration file now. I will open the relevant proposals as issues tomorrow.

Great start to the script. I agree that there should be files in ghcvm-hackage that indicate the packages that should be tested.
Before merging this, I'll need you to do a couple things:

Create all the files you need in ghcvm-hackage and submit a PR to that repository.
Update the Test.hs script to read from the files instead.
Note that ghcvm-hackage is essentially cloned to ~/.cabalvm/patches/ after running cabalvm update so you can look there for the files you created in step 1.
Make the Travis build pass. If any of the packages fail, let me know and I'll update the patches to fix the build.


Error when importing a module created by wasm-pack

Describe the bug
I'm getting the following error when using Vitest and importing a module created by wasm-pack:
 FAIL  web/test.ts [ web/test.ts ]
 FAIL  web/main.ts [ web/main.ts ]
Error: Failed to resolve entry for package "/Users/alex/programming/rust/vitest-wasm-pack-error-repro/math-lib/pkg". The package may have incorrect main/module/exports specified in its package.json.
 ❯ packageEntryFailure node_modules/vite/dist/node/chunks/dep-5605cfa4.js:34107:11
 ❯ resolvePackageEntry node_modules/vite/dist/node/chunks/dep-5605cfa4.js:34104:5
 ❯ tryResolveFile node_modules/vite/dist/node/chunks/dep-5605cfa4.js:33717:38
 ❯ tryFsResolve node_modules/vite/dist/node/chunks/dep-5605cfa4.js:33699:16
 ❯ Context.resolveId node_modules/vite/dist/node/chunks/dep-5605cfa4.js:33544:28
 ❯ Object.resolveId node_modules/vite/dist/node/chunks/dep-5605cfa4.js:40462:46
 ❯ TransformContext.resolve node_modules/vite/dist/node/chunks/dep-5605cfa4.js:40227:23
 ❯ normalizeUrl node_modules/vite/dist/node/chunks/dep-5605cfa4.js:37137:34
 ❯ TransformContext.transform node_modules/vite/dist/node/chunks/dep-5605cfa4.js:37278:47

I have spent a few hours reading through documentation and trying various workarounds and configuration options but I haven't been able to resolve the issue.
I'm using the vite-plugin-wasm-pack plugin. Note that the application builds and runs fine; this appears to be only a problem with the tests. I would expect that if Vite is able to build the application then Vitest should also work, but maybe I'm missing something?
Reproduction
I created this repository with what I believe is a minimal reproduction: https://github.com/albrow/vitest-wasm-pack-error-repro. Just follow the instructions in the README.
In case it is relevant, here is a link to the actual repository where I originally encountered this issue: https://github.com/albrow/elara/tree/vitest-error-example. I created a new branch called vitest-error-example which showcases the issue.
System Info
System:
    OS: macOS 13.0.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 146.94 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
    npm: 8.18.0 - ~/.nvm/versions/node/v16.17.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 110.0.5481.100
    Firefox: 109.0.1
    Safari: 16.1
  npmPackages:
    @vitejs/plugin-react: ^2.1.0 => 2.2.0
    vite: ^3.1.7 => 3.2.5
    vitest: ^0.26.3 => 0.26.3

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi, thanks for providing a concise reproduction. This issue is quite old one and you might have already figured it out, but I think such usage of wasm-bindgen/wasm-pack is a reasonably common setup but with some pitfalls, so let me answer this.
First of all, I don't think this is a bug in Vitest. I have a few wasm-bindgen based projects on my own also with Vitest and I haven't hit this issue. For example, my usual vitest setup looks like this https://github.com/hi-ogawa/argon2-wasm-bindgen/blob/main/test/basic.test.ts#L11
I provided a concrete code with a few comments to explain the issue in your repository's PR.
I'll close this issue for now, but feel free to continue comment if you have further problem with wasm-bindgen + vitest setup.


feat: Pointwise set difference, complement

Define Finset.diffs and Finset.compls, the pointwise set difference of two finsets and pointwise complement of a finset.
diffs appears in the statement of the Marica-Schönheim inequality and compls in the proof.
Also fix the corresponding statements for sups and infs to use the new · notation.

Yes, my goal when introducing the image₂ API was to make writing this kind of API easy, not to make using this kind of API hard because we're not allowed to copy template API over to specific cases in the name of avoiding duplication.

Note that I am a bit unhappy with the \\ notation. Do people think \ˢ is better?

I definitely need compls for many different purposes. It shows up in the proof of Marica-Schönheim, but also in Kruskal-Katona, Sperner's theorem (at least the proof Bhavik had before I golfed it) and @apnelson1 independently wanted an UpperSet/LowerSet-valued version.
diffs is less clear-cut but still worth it:

It makes the deduction of Marica-Schönheim from Daykin magically easy: https://github.com/YaelDillies/LeanCamCombi/blob/main/LeanCamCombi/FourFunctions.lean#L345-L347
It is used in the reverse Kleitman inequality stuff here (unfinished): https://github.com/YaelDillies/LeanCamCombi/blob/main/LeanCamCombi/Mathlib/Data/Finset/PosDiffs.lean#L73-L75
Having a def wrapping that special case of image₂ means that we have a clear name atom to use in lemma names.
I designed image₂ to be a template API that people can copy and use for their specific operations. Maintenance of template uses is pretty easy since a template use contains no new proof, and every lemma that could be added there instead gets upstreamed to become a template lemma. Basically, don't kill the point of the template by telling me to use the template directly instead of specializing it.

Yeah, I'm not convinced about the notation either. I'm happy to change it at a later time.
bors merge


Update to llama 3.1 and fix broken links

Hello, I am a PR summary agent on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


auto_revoke support for winrt::event<> events

Consider the following class:
class Foo
{
    winrt::event_token MockEvent(const winrt::delegate<> handler) { return m_mockEvent.add(handler); };
    void MockEvent(const winrt::event_token& token) { m_mockEvent.remove(token); }

    winrt::event<winrt::delegate<>> m_mockEvent;
}

It would be good if we had support for automatically revoking these events (using winrt::auto_revoke for example). Ideally we can simply add an extra method which takes in winrt::auto_revoke_t and returns an auto_revoke token, but it seems like this isn't supported for non projection types.
winrt::auto_revoke<Foo> MockEvent(const winrt::auto_revoke_t, const winrt::delegate<> handler)
{
...
}

To work around the problem we've created our own copy of the event_revoker struct, but it feels like something we should consider supporting 😊.

The problem is with the lifetime of the event source - the "Foo" in your example. An event revoker should consider whether the revoker outlives the event source (instance). WinRT supports this via weak references, but for other types you're on your own to figure out how to achieve this (typically with a shared_ptr). The C++/WinRT library is only concerned with WinRT types. You can naturally define your own revoker (in some other namespace) that supports non-WinRT types.

That makes sense to me. I was asked to bring up the issue here since we had to deal with it.


Version 3 trading outside of time window

Hi Walee,
I downloaded version 3 and tested it via Live Sim on 2 Dec 2024. My settings were all default except for the profit target and stoploss. My time window was 83500 to 123000 but for some reason the bot had it's first trade outside of the time window. My VPS is in the CST time zone and my NinjaTrader is also set to that time zone. Also, there was another error printed in the Output window.
Here are the messages:
***** OFB-AtmStrategy *****
Enter Long | 62600 Stacked Imbalances
Exit | 70655 Stacked Imbalances
***** OFB-AtmStrategy *****
Enter Long | 84816 Stacked Imbalances
Exit | 84816 Stacked Imbalances
Error invoking event: Value cannot be null.
Parameter name: key
Error invoking event: Value cannot be null.
Parameter name: key

I was using the normal UI with buttons. Had Auto enabled.

I will run the bot again in Live Sim for 3 Dec 2024 and let you know the outcome.
PS: Nice work on the code refactor


Add reading from console pty

Playing around with a Pty abstraction to be able to read/write to the master pty.

@haircommander PTAL

Rebased to make the CI happy.

we are currently printing tons of ERROR [conmon_server::iostreams] Unable to read from terminal: stream not set in the integration tests, I don't know if we should log there

I have to revisit this PR in the next couple of days.

@haircommander PTAL

LGTM


A mode to read resources directly from the account (using the collector package)

[ ] #395
[ ] Whenever the user uses the -provider flag, call the collector to collect the resources from the cloud account.
[ ] Never allow -provider and -vpc-config to be specified together.
[ ] Make sure -provider works with -analysis-type diff_all_endpoints and -analysis-type diff_all_subnets - this should diff the connectivity in the cloud account vs. the connectivity in the config given by -vpc-config-second
[ ] Allow the user to use the -region and -resource-group flags to also filter resources that we got from -vpc-config

https://github.com/np-guard/cloud-resource-collector/pull/198


Download links from Testing UI do not resolve if accessing Testrun from different IP addresses/hostnames

Describe the bug
The download links in the Testing UI do not resolve if accessing Testrun via different IP addresses/hostnames.
In this case I have a machine <IP_ADDRESS> running Testrun, I am web browsing to it from another machine <IP_ADDRESS>. All Testrun browsing is working okay, with the exception of the download links in the Testing window, that appear to not be relative URLs, and instead try to resolve against localhost.
To Reproduce
Steps to reproduce the behavior:

Web browse to Testrun from an external machine (e.g. http://<IP_ADDRESS>:8080/).
Run a test and let it complete. Cancel out of the report download modal window once the test has completed.
Attempt to Download PDF or ZIP file as below.

Error as below.

Expected behavior
Download link should resolve to a relative URL, to cater for accessing Testrun via hostname/IP address/localhost/behind NAT/etc.
Environment (please provide the following information about your setup):

OS: Ubuntu
Version 24.04.1
Testrun 2.0

This requires a little extra configuration that does not appear to be documented or available in the UI at this time.
Navigate to /local/system.json and add the variable api_url and point it to your systems IP address.
Example system.json with this option included:
{
  "network": {
    "device_intf": "eth0",
    "internet_intf": "eth1"
  },
  "log_level": "DEBUG",
  "startup_timeout": 60,
  "monitor_period": 60,
  "max_device_reports": 5,
  "api_url": "http://<IP_ADDRESS>",
  "api_port": 8000,
  "org_name": "",
  "single_intf": false
}

This would make all API routes go to <IP_ADDRESS> instead of localhost when connecting via the UI.

Good to know about the api_url workaround. 👍
Is there scope to add a feature request for this one to get those particular hyperlinks on the UI working relatively? The rest of the hyperlinks across the UI work perfectly, and it'd be nice to be able to decouple Testrun from being dependent on what hostname/IP address a sysadmin has configured the Testrun machine with? 🤞

Thanks for the bug report. I believe this has been a known issue for some time hence the implementation of api_url. I will see if we can add this setting to the UI.

This issue is currently being addressed. A PR is expected soon.

Fixed in PR #954. This will be released shortly in v2.1


Configurator footprint plotting origin

If the origin of configurations is known (such as in SMAC), it would be useful to be able to differentiate if configurations were selected by random search or any other origin.

if available, footprint origin is listed in hover-tooltip with #123


YouTube: "Sign in to confirm you're not a bot"

Hi, I'm trying to transcribe by youtube url and get a error:  "Failed (ERROR: [youtube] link: Sign in to confirm you're not a bot. This helps protect our community.Learn more)". How to fix it?

@gogolevmatvey According to this https://github.com/yt-dlp/yt-dlp/issues/3766  Your IP has been blocked by YouTube.
I see two possible solutions:

Use a different IP, or some proxy.
Use yt-dlp to manually download audios

At this point I do not see any easy way to fix this.

I have an idea how this could be fixed

@gogolevmatvey Latest development version has support for a cookie file to access private videos or as a workaround for anti bot systems.
See https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp for information on how to get a cookie file
Pass path to the cookie file via BUZZ_DOWNLOAD_COOKIEFILE environment variable. For more information see https://chidiwilliams.github.io/buzz/docs/preferences#advanced-preferences
To download latest development version:

Go here https://github.com/chidiwilliams/buzz/actions/workflows/ci.yml?query=branch%3Amain
Select latest build and scroll down to the artifacts section
Ensure you are logged in the Github and download the installation file.


Invalid descriptor for property '0'

In IE 11, I'm getting the error:

Invalid descriptor for property '0'

Walking up the call stack, it's stemming from some code that is constructing a DOMTokenList with a body element and 'className':
e=new DOMTokenList(body, 'className');

...which eventually hits this code which throws the error:
_(y,n,r)

_ is some function named defineProperty
y is some object
n is 0
r is set to undefined

I'm using this polyfill URL (linebreaks added for readability):
https://cdn.polyfill.io/v2/polyfill.min.js
  ?unknown=polyfill
  &features=
    default%2C
    fetch%2C
    Array.prototype.%40%40iterator%2C
    Array.prototype.find%2C
    Array.prototype.findIndex%2C
    Function.name%2C
    Number.isFinite%2C
    Promise%2C
    String.prototype.repeat%2C
    Array.prototype.includes%2C
    Intl.~locale.en-US%2C
    Promise.prototype.finally

In scrutinizing further, it seems clear that it's in the defining of indexer properties where this problem is occurring:
https://github.com/Financial-Times/polyfill-service/blob/1f45e5b95625180117d5b2f1979d8e217bc791a4/packages/polyfill-library/polyfills/_DOMTokenList/polyfill.js#L35-L41

I got this too. Here's the unminified stacktrace:
TypeError: Invalid descriptor for property '0'
   at setDescriptor (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:1812:4)
   at defineProp (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:1715:4)
   at defineGetter (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:2609:4)
   at addIndexGetter (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:2633:4)
   at reindex (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:2644:6)
   at preop (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:2681:4)
   at _DOMTokenList (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:2685:3)
   at Anonymous function (https://cdn.polyfill.io/v2/polyfill.js?features=default,es6,es7,es2017,fetch,IntersectionObserver:3022:11)

That setDescriptor function is from the Symbol polyfill:
	setDescriptor = function (o, key, descriptor) {
		var protoDescriptor = gOPD(ObjectProto, key); // gOPD = The original Object.getOwnPropertyDescriptor, before being wrapped by this polyfill
		delete ObjectProto[key];
		defineProperty(o, key, descriptor);  // This line succeeds with args: o = _DOMTokenList, key = '0', descriptor = {configurable: false}
		if (o !== ObjectProto) {
			defineProperty(ObjectProto, key, protoDescriptor); // This line throws the exception with args: ObjectProto = Object.prototype, key = '0', protoDescriptor = undefined
		}
	};

If I try the same call in Firefox (Object.defineProperty(Object.prototype, '0', undefined)) I get the error TypeError: descriptor must be an object, got undefined, so this probably isn't exclusively an IE11 bug, it probably occurs in IE11 because IE is the only major browser that gets the DOMTokenList polyfill.

We just came across this

I've been working on a related bug in my client's app where the original Object.getOwnPropertyDescriptor stops returning a descriptor for Symbol.toStringTag, which causes that line to throw because undefined isn't a valid object.
In at least my situation what I think is happening in is that something is deleting that property from the Object prototype but I haven't tracked down where yet. It could be another polyfill.


fleet manager prometheus metrics

SRE is using these prometheus metrics in their grafana dashboards [1]. After fleet manager scale testing, we manually run kube-burner with this metric profile to index into our internal ES. We have internal grafana dashboard [2] which uses these metrics from our ES.
[1] https://grafana.app-sre.devshift.net/d/osd_fleet_manager1/osd-fleet-manager-metrics1 [2] https://grafana.rdu2.scalelab.redhat.com:3000/d/osd_fleet_manager1/osd-fleet-manager-metrics1
Description
Fixes

As per the slack conversation. I am ok overall with the change.
Just thinking whether e2e-benchmarking or another repo would be the right place.

As per the slack conversation. I am ok overall with the change. Just thinking whether e2e-benchmarking or another repo would be the right place.

Agree, I guess that is where we currently host the metrics profiles for the cluster-density-ms tests as well.

Submitted this in E2E as per above suggestions https://github.com/cloud-bulldozer/e2e-benchmarking/pull/533
So closing this PR.


Upgrading to protobuf==3.2.0 in the Python client

Hello, we'd love to use or-tools in Python, but we have a dependency on protobuf==3.2.0. I see that the PROTOBUF_TAG is set to 3.2.0 across Makefiles, but there are a few hardcoded references to protobuf-3.0.0 in the Python Makefile, causing or-tools to depend on 3.0.0. Because of this we get downgraded when we install or-tools (leading to other libraries breaking).
(venv) ~/tmp $ pip install protobuf==3.2.0
<snip>
Successfully installed protobuf-3.2.0
(venv) ~/tmp $ pip freeze -l | grep protobuf
protobuf==3.2.0
(venv) ~/tmp $ pip install ortools
<snip>
Successfully installed ortools-5.1.4045 protobuf-3.0.0
(venv) ~/tmp $ pip freeze -l | grep protobuf
protobuf==3.0.0

Are there plans to update or-tools to protobuf==3.2.0?
Thanks!

It should be fixed now.
I did a release yesterday, it should be announced soon.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2017-05-17 6:15 GMT+02:00 Max Rozentsveyg<EMAIL_ADDRESS>
Hello, we'd love to use or-tools in Python, but we have a dependency on
protobuf==3.2.0. I see that the PROTOBUF_TAG is set to 3.2.0 across
Makefiles, but there are a few hardcoded references to protobuf-3.0.0 in
the Python Makefile
https://github.com/google/or-tools/blob/b6632140a5559aa2a6d45448edc3802ab83e013d/makefiles/Makefile.python.mk#L57-L59,
causing or-tools to depend on 3.0.0. Because of this we get downgraded us
when we install or-tools (leading to other libraries breaking).
(venv) ~/tmp $ pip install protobuf==3.2.0

Successfully installed protobuf-3.2.0
(venv) ~/tmp $ pip freeze -l | grep protobuf
protobuf==3.2.0
(venv) ~/tmp $ pip install ortools

Successfully installed ortools-5.1.4045 protobuf-3.0.0
(venv) ~/tmp $ pip freeze -l | grep protobuf
protobuf==3.0.0
Are there plans to update or-tools to protobuf==3.2.0?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/381, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17Y-ex0Ptv4tKYXlbriqIbz9DC4GYks5r6nRggaJpZM4NdWtj
.

Thanks @lperron this is great news! Do you have a timeline for when the next release will be announced? Will it be published as a wheel on pypi as well?

It is already pushed on pypi.
I am writing the release notes today.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2017-05-18 7:52 GMT+02:00 Max Rozentsveyg<EMAIL_ADDRESS>
Thanks @lperron https://github.com/lperron this is great news! Do you
have a timeline for when the next release will be announced? Will it be
published as a wheel on pypi as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/381#issuecomment-302307768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17QOJbxFLQvM3zXnkmZZcySxfewLWks5r69y0gaJpZM4NdWtj
.

Can you clarify? I don't see a Linux wheel on pypi yet.

Hi @lperron. Thanks for quickly upgrading the protobuf dependency. Like @mxr mentioned in his previous comment, it would be awesome if you can help with releasing the wheels for ortools on Linux.
Thank you.

I tried, you need to install manylinux on a centOS docker, compile multiple
versions and merge them :-(
I kindly propose you install or-tools from sources and build .egg file
locally (make python_archive).
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2017-05-23 3:02 GMT+02:00 Chirag Chheda<EMAIL_ADDRESS>
Hi @lperron https://github.com/lperron. Thanks for quickly upgrading
the protobuf dependency. Like @mxr https://github.com/mxr mentioned in
his previous comment, it would be awesome if you can help with releasing
the wheels for ortools on Linux.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/381#issuecomment-303260707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17QJsgp5lf2tzId8SvYFXfYuht12kks5r8jAXgaJpZM4NdWtj
.


Example l0 peripheral

Coverage remained the same at 67.944% when pulling 2293a36bf72057068fb9da1e45508cbe4c43ba8b on example-l0-peripheral into bd5796d7fba172e8943ac4667be5fc138ed8646d on v2.0-beta.


Fix recursive_eltype not defined when constructing ComponentArray on the GPU

Hi,
After the switch to Julia extensions (#192), the methods that are not exported by ComponentArrays are not accessible in the extension source files. This leads to an undefined reference when calling recursive_eltype at line 77 in the constructor of ComponentArray on the GPU:
https://github.com/jonniedie/ComponentArrays.jl/blob/97eb9e3db7904ea13b823403d00ddd9e9d6c078f/ext/ComponentArraysGPUArraysExt.jl#L76-L81
This pull request adds the missing import and fixes #209.

Codecov Report

Merging #210 (c8afcbd) into master (97eb9e3) will decrease coverage by 0.89%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master     #210      +/-   ##
==========================================
- Coverage   73.14%   72.26%   -0.89%
==========================================
  Files          20       20
  Lines         689      685       -4
==========================================
- Hits          504      495       -9
- Misses        185      190       +5

Impacted Files
Coverage Δ

ext/ComponentArraysGPUArraysExt.jl
52.88% <ø> (ø)

... and 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks for this! It looks like the test failure is unrelated, so I'm gonna fix that really quick and see if that helps before merging this.

Okay, this should be good to go with the new changes. If you wouldn't mind rebasing I can merge after that.


DApp https://uniswap.exchange/ cannot detect wallet.

DApp https://uniswap.exchange/ cannot detect wallet. It works very well before

I have received several complains about this issue.
Uniswap made a “limit edition socks selling” event, several users complained that they cannot use AlphaWallet to buy socks, after all they have to transfer the fund to other wallets.

@hboon I am on it.

https://github.com/Uniswap/uniswap-frontend/issues/282

I tested Uniswap on most of the web3 wallets, it failed only on us and Cipher. Did we use something that is different from other wallet but same as Cipher? @James-Sangalli

Supporting EIP1193 should fix this
https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1193.md
Ref from https://github.com/Uniswap/uniswap-frontend/issues/282#issuecomment-494150608


How to query for multiple conditions

Hi! How can I correctly scan for two attribute conditions in the same run? When adding a new user to the table, I would like to check if there is already any users with that email or username. I've tried chaining scans but it doesn't seem to work. Also tried the .or() keyword which seems to be only for readability? Putting both attributes in the same scan options would of course just return users that match both conditions.
User
            .scan({
                username: {eq: new_user.username}
             })
            .scan({
                email: {eq: new_user.email}
             })
            .exec()
            .then((duplicate_users) => {

                console.log(duplicate_users);
              //...

Mongoose schema has the unique: true attribute. That would be nice for Dynamoose as well!

Due to the lack of activity I'm closing this issue. Please feel free to comment if this did not solve your problem.


add instance segmentation voc evaluator extensions

Can you add a link to the doc?

Thanks, I added.