Async storage doesn't work when debugging in chrome using genymotion emulator

Using a macbook pro running 10.11.4 El Capitan
Using AsyncStorage api with android geny motion emulator, when debugging in chrome AsyncStorage does not operate
   componentWillMount: function() {
       var token;
       AsyncStorage.getItem('token').then((data) => {
         if(data) {
           token = data;
           return token;
      } else {
        this.setState({
          noAuth: true
        });
      }
    }).then((token) => {
      setTimeout (() => {
        this.setState({
          token: token,
          loading: false,
          noAuth: true
        });
        this.props.navigator.push({
          id: 'HomeView',
          passProps: {'state': this.state},
          sceneConfig: Navigator.SceneConfigs.FadeAndroid
        });
      }, 300);
    }).

This seems to run, but my timeout/navigate to never hits the homepage if i'm in debug mode, obviously this presents a few problems because then i can't debug why things aren't working lol. Any guidance would be much appreciated. Thanks.

@facebook-github-bot stack-overflow

Hey @austinksmith and thanks for posting this! @DanielMSchmidt tells me this issue looks like a question that would be best asked on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.

I think you've misunderstood the question a bit, asyncstorage doesn't function when debugging in chrome. This to me is a major bug as it prevents me from debugging my application.

Sorry for that 😞
@facebook-github-bot reopen

It seems to be intermittent when it works, when running on an actual device everything appears to function fine. My use case is basically, I have a splash/login screen and when someone logs in I'm saving a token using asyncstorage, in my homeview I fetch that token from asyncstorage and render a list of events. The problem is when debugging about 70% of the time the homescreen will simply hang, my breakpoints never get hit and the application does not freeze I can still reload the js and enable the perf monitor but it appears my token is never getting fetched from storage which is required for me to authenticate with my api endpoint and render my events so i'm met with my homepage without any events.
I'm emulating a Nexus 5 running android 4.4.4 API 19
Running chrome Version 50.0.2661.102 (64-bit)
Using a MBP Retina running El Capitan 10.11.4
With the following extensions https://www.dropbox.com/s/tdd7zwwnhswul7i/Screenshot 2016-05-20 16.13.32.png?dl=0

I have the same issue.
@DanielMSchmidt It seems like the github-bot failed in reopening the issue.

I have the same issue. When DEBUG JS Remotely is one, accessing AsyncStorage via redux-persist just hang.

@facebook-github-bot reopen

i'm having the same problem running rn-0.31 on the android emulator (Android 6.01) and on a nexus 4 device.
computer is a thinkpad x220 running ubuntu 16.04
chrome version 52.0.2743.82

@thorstenweber83 I don't know why, but I also confirmed that the Delay Render Until Rehydration Complete solved the issue.

I'm getting the same issue in chrome too. Nexus 5 with remote debugging through chrome.
React native version 31.0
After throwing in a few console logs, it seems the callback registered when calling RCTAsyncStorage.multiGet in Libraries/Storage/AsyncStorage.js never gets called. Everything works fine on the device though so it seems to be an issue with the debugger.

Same issue.  Sometimes the debugger works fine, sometimes AsyncStorage is (really) slow (3-9 seconds, and I've even seen it take 9 minutes for AsyncStorage.multiGet to return, and sometimes it appears to hang indefinitely (15+ minutes).  Turning off Debug JS Remotely seems to solve the issue immediately.  Interestingly, I haven't seen the issue occur during the first reload when you turn the debugger on.
I'm running:
(actual device) Nexus 5x on 7.1.1
Chrome 54.0.2840.71
React Native 0.35.0

This could be the same issue that I was facing here #12830 (no solutions there either).

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/async-storage-doesnt-work-when-debugging-in-chrome-using-genymotion-emulator

Same issue, running running on nexus 5x api 23 (emulator), but when switch to nexus 6p api 23 (emulator) the problem SEEMS (I mean I don't know exactly, but tried to reload 10 times and didn't face the problem) disappear.
I think this problem should be payed attention.

There seems to be a trend of closing out issues when they're only inactive due to users waiting for response from maintainers...not a great practice. Here we are almost 2 years later and this still hasn't been addressed.

The two month inactivity period before closing can be bumped up now that we have a smaller number of open issues, but I'd still recommend submitting a pull request as a more appropriate long term fix. We lean heavily on the community providing fixes for issues they run into. Please tag this issue if a PR is submitted and we can re-open it.

It's really quite a pain trying to debug an Android app. The only time AsyncStorage seems to retrieve the items while in debugging mode is when the app first opens. So a lot of the time when you make changes you'd have to close the app & reopen it.

the same issue as @jamsch said. I must close and then reopen the app everytime.

I have a theory for a reproduce the issue but couldn't fully test it.
I realized for a couple of times that I reload the app (menu button -> reload) while AsyncStorage.getItem is in progress, it stops working thereafter.
Anyone can confirm?

@hramos it is clear this issue is impacting development, please reopen

Have same issue when try to access data stored in AS. Only in Android with debug JS mode on.
Using RN 0.50.4 without redux en redux-persist.

This issue is not getting re-opened. Please go ahead and open a new issue that follows the template, as advised last July.

@hramos this issue was open for the last 2 years, additionally the text says
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
The caveat is If so is there any information missing from the bug report and the caveat does not apply, there is no information missing from the bug report.
2 years man, get it together guys.

Thanks for your cooperation.

@hramos I think we've all been really patient regarding this issue, I am no longer working on react native projects at the moment but these issues that impact the speed of development are reasons why I haven't taken up react native more in my own projects. While my open source project is much less lines of code I am also only one man and I am able to close out all issue tickets with an average time of 2 months at most to get them fixed, Facebook has a market cap of 531.59 billion dollars can we not expect big issues like this to at least be paid attention to in 2 years without being closed out and told dubious reasons why we must now create a new ticket. It's disappointing to see a project being run this way especially one run by a company with so many resources, is it too much to ask that the build tools for the project work as advertised?

@austinksmith market cap does not give you any silver bullets to solve complex technical issues across many layers of libraries/platforms outside of your control. With all due respect, React Native is tackling the cross-platform challenge better than any other project I've ever tried. Maybe use your energy to dive into the code and look for a solution to the problem yourself? It is all open source for a reason. Anyway @hramos , https://github.com/facebook/react-native/issues/12830 is a duplicate of this issue and it is currently open. Perhaps we can label this one as a duplicate so all the attention can be focused on that one issue. There is no solution there yet either, unfortunately.

Wouldn't that ticket actually be the duplicate considering its 12 months
old and this one is 24?
Like I said, I'm no longer using react native for any projects but I am not
obligated to fix the debugging and emulators here. If 2 years is now the
new standard for fixes then I will be sure to avoid rn moving forward.
Market cap shows facebook has capital, to pretend they don't or they can't
afford to invest more resources into their software offerings is a slap in
the face to people who work hard to make sure their own software is as bug
free as possible with significantly less resources at their disposal.
A 500+ million dollar corporation should probably be able to fix an issue
like this within 2 years right?
If not then open source as a whole is a doomed proposition, I also think
it's fair to expect issues not to be closed before they are addressed
either. Its not anyone's fault who had been impacted by the issue (myself
included) that this has happened, it was reported 2 years ago and
maintainers have attempted to close the ticket multiple times without
investigating.
A duplicate was created a year after this one, meaning the duplicate
should have been closed and not the original.
These are my opinions as someone who needs to make technical decisions on
what frameworks to use for upcoming projects, I like what react native is
trying to solve but it makes it difficult to use it when I can't get issue
tickets to even stay open long enough for someone to actually label it as
needing attention or someone to investigate within several years.
On Feb 28, 2018 4:28 AM, "Bartol Karuza"<EMAIL_ADDRESS>wrote:

@austinksmith https://github.com/austinksmith market cap does not give
you any silver bullets to solve complex technical issues across many layers
of libraries/platforms outside of your control. With all due respect, React
Native is tackling the cross-platform challenge better than any other
project I've ever tried. Maybe use your energy to dive into the code and
look for a solution to the problem yourself? It is all open source for a
reason. Anyway @hramos https://github.com/hramos , #12830
https://github.com/facebook/react-native/issues/12830 is a duplicate of
this issue and it is currently open. Perhaps we can label this one as a
duplicate so all the attention can be focused on that one issue. There is
no solution there yet either, unfortunately.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/7605#issuecomment-369175550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACH-I7s5QOp2o9mf1a3zIMwtC9dfhUb3ks5tZRwtgaJpZM4IguFa
.

I was just suggesting the duplicate approach out of practical considerations. Would it make you feel better if that one was closed and marked as duplicate and this one re-opened? Either way, I think it's easier if we have one issue open for it until we can distinguish if this is all caused by the same thing or if we are catching multiple different issues with similar effects. As I said in the other ticket, this is not happening for me anymore (for a long time) and I suspect only a subset of the user base is affected. To be able to find out what subset with which characteristics, we need more information about the causes. The other ticket seems to have more relevant information at this time.
I can't personally look for a solution anymore as I'm not able to reproduce this problem. Without a minimal project showing the issue with exact specs that makes the issue easily reproducible, finding a fix would seem an impossible task for anyone, even Facebook. This is probably why there is some reluctance to keep the issue open. (I'm not connected to Facebook in any way and just an RN user most of the time.)

I don't think we should call an original ticket a duplicate and close it out giving the impression that this issue is a year old and not two years old as this ticket shows. It's definitely not in anyone's best interest to arbitrarily close out old tickets, I created this ticket because it impacted my ability to complete a project on time for a company I worked at. Eventually I trialed and errored my way around the problem but this is bad practice on facebook's part and it seems like an attempt to hide the impact of various issues that have existed for a long long time.
If I had been asked to provide a example app I would have done so 2 years ago but this wouldn't have changed much I don't think given this is a trend across 3 out of the 4 tickets i created back then, please don't defend bad practices for issue ticket management on software projects because it sets a bad trend that will be followed by others because of the "If it's good enough for facebook, its good enough for me/us" group think mentality.
I think it's only fair that if these issues exist and they are not going to be resolved that the original ticket conveying the issue stays open if only for the purpose of knowing which issues to prioritize over others based on how long they've existed, closing out an older ticket and calling it a duplicate when it has existed for 12 months longer than the one referenced is an extremely bizarre practice and only seems to serve the purpose of arbitrarily reducing the issue resolution time metric.

AsyncStorage works fine using the simulator (when not debugging in chrome), but when using an actual device, it doesn't work.  I'm not sure if I've taken all measures, but I just wanted to add to this.
Thanks.

I switched to Expo XDE, and now using Expo.SecureStore.setItemAsync and it seems to work fine for now.

@cihadturhan I think you are right.
I can reproduce this error just by refreshing several times an app (cmd+r).
After that AsyncStorage.getItem does not resolve any value.

Guys, did you find a solution for that, switching to Expo Storage is not an option. This issue should be prioritize, I mean it is really hard to understand what happens in the app without debugging, it like shooting in the dark.

I'm facing the same issue.
maxOS Sierra 10.12.6
Chrome 66.0.3359.139
react-native: 0.55.3

And I'm using AVD Nexus 4 API 23.
For me AsyncStorage works as soon as i launch react-native run-android, but it randomly stops working after x reloads, and I have to re-launch run-android. The thing is driving me mad, as I even put a log in my console that tells me if the AsyncStorage is working or not.

same issue here ....

Im 100% not sure where you guys are having problems with this, i have been using debug mode AsyncStorage on android simulators & devices without any problems. Maybe you are more so having problems with setTimeout, as in debug mode it can be a little glitchy and not call within the time frame expected. (especially if the time on the device and computer are different)

getting the same issue... You had 2 years to fix such a bug (not impressed)

same here, issue still there


thanks for all the great work

Just wanted to give some feedback that I really admire the organization and structure of the project you made here.  Great architecture choices, simple to follow - prioritizes readability and understanding over brevity/premature optimization, typed well for ide intellisense, great abstractions - especially of notoriously messy libraries.  PIXI.js historically loves globals and didn't play well with es2016+ import/exports for a while ... unsure if it's still like that.  Also love that you're using pixi-viewport, too.
I'm impressed at how much this is doing with so little use of promises!  Just a couple in the client related to the initial interaction with the websocket.
Yarn workspaces makes dependencies nice and collected in the one place instead of three then managed with Lerna or more customized build scripts.  I like that you drew the line during deployment at simple constructing the docker image and not also trying to add in whatever process you do to get/pull down to wherever you host (I like that those are separated concerns, makes the build process simpler).
Altogether, I think this may be one of the best put together javascript/typescript game repositories I've come across.  Thank you so much for sharing this via open source software!  Now, how can I buy you a coffee or beer or contribute to your Patreon? 😄

First of all, a huge thanks for your kind and encouraging words @bpkennedy!
Also, my biggest apology for answering so late as I got carried away and totally forgot about writing a proper answer.
All the architecture and organisation choices you've listed are conscious compromises I try to make during development of open-source projects. I try to keep things simple for the reader as code is read much more than it is written, and having clean abstraction and obvious code execution paths. I spend most of my coding time thinking about how "clean" and "pure" I can make the abstractions I'm working on and find myself rewriting them over and over at least a dozens time (which is not a good practice if you want to move fast I assure you). I find myself happy when others can feel it through my projects and implementations!
My best reward is for people to find what I do useful and inspire them to explore things on their own!
I intend to update this project with a few addition this year, and maybe with one of my most recent project regarding dungeon generation: https://github.com/halftheopposite/graph-dungeon-generator.
If you're interested into reading some of my code, I've tried to make it as clear as TOSIOS regarding code reading and architecture.


Nested generics not honoured

Using 0.4.2, I am trying out generics.  I have declared as follows:
"javaType": "java.util.Map<java.lang.String, java.util.Map<java.lang.String, java.lang.String>>",

When I try this, the generated class doesn't have the second > on the end of the type, so renders a compile error (in the attribute, the getter and the setter).

+1


ReadMe Update to add AmiiboAPI for #1429

https://www.amiiboapi.com/
#1429

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side <<----- THIS DID NOT MATCH THE CONSISTENCY OF THE OTHER COLUMNS
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

See #1440


Fixing connection without save password not connecting in Async Server Tree

Bug 1: fixing connections with forgot password not connecting.

Previously, we encountered a bug when attempting to connect a profile that didn't have a saved password. Our usual workflow involved opening a connection dialog and prompting users to enter their password before connecting to the server. In such cases, the 'onConnectionProfileConnected' event was triggered. However, this created an issue since the connection returned from the connection dialog was completely new, and we couldn't locate it in the tree.
This PR modifies the connection management service. Instead of triggering the 'onConnectionProfileConnected' event, the service now triggers an 'onConnectionProfileEdited' event. This event includes the profile ID of the old connection in the tree and the new connection from the connection dialog. The 'onConnectionProfileEdited' handler is then able to locate the old connection in the tree and replace it with the new connection from the dialog.
This should not interfere with the old tree as the old tree is not using 'onConnectionProfileConnected' and 'onConnectionProfileEdited' events.

Bug 2:
When disconnecting connections where the 'save password' option is set to false, we now remove the saved password from the connection.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 5 (20.0%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.002%) to 41.691%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/connection/browser/connectionDialogService.ts
1
2
50.0%

src/sql/workbench/services/objectExplorer/browser/treeUpdateUtils.ts
0
1
0.0%

src/sql/workbench/contrib/objectExplorer/browser/serverTreeView.ts
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.88%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
30310

Relevant Lines:
67308

💛  - Coveralls


Add radwave info text

This adds in the text for the radwave and improves some of the video css.

Converting to a draft for now, pending SME approval of video script, which will inform what we put in the info text box in the final version.


Missing dependency in CMakeLists

In GitLab by @tpaluszk on Feb 14, 2019, 15:13
Pyyaml is missing yaml dependency in CMakeLists which terminates of compilation.

closed via merge request !181


swap_activity check needs sane defaults

Currently the swap_activity check defaults to warn/crit alerting when 100k/500k is swapped out per second, in a 5 sec interval (vmstat).
I'd like to get the defaults changed to something that will alert us when the system is swapping enough to be thrashing, but not when it's just doing exactly what it's designed to do.
Maybe, as a starting point, we change to alerting warning at 50MB, and critical at 200MB?

Imported from Launchpad using lp2gh.

date created: 2019-04-02T23:10:45Z

owner: xavpaice

assignee: None

the launchpad url

(by ec0)
Considering this is coming from vmstat, which per, the source code, is measuring the vm_pswpout function for the "so" column, which is in turn, what we measure as swap_activity, this is measuring the volume of data being swapped, rather than the swap rate or number of pages being swapped.
I would confidently say that no user wants to alert when they swap 100kB of data to disk - and we could at least bring this up to 10MB/40MB for warning and critical levels. Per Xav's comment, this would translate to 50MB/200MB over a five second interval, so +1 from me.

(by woutervb)
lgtm


Faded border on workspace list

I wanted to get people's feedback on this half-faded border design. I decided to make a LargeFadeBox that will be used here and in Groups list/Groups Edit that was evolved from FadeBox (in Browse Data) to better fit whole pages. Since LargeFadeBox will be in a few places, I wanted to get the okay on it before going ahead and placing it elsewhere.

Note: it flips from 3 cards across to 4 cards across at 1435px


Pseudo-Boolean Constraint toString into Parser Roundtrip does not work.

If i parse a pseudo boolean constraint like
1 * A + 1 * B = 1
it works. If I then print this with toString() it becomes
A + B = 1
which can not be parsed anymore.
I believe that output should be parseable again. And it is in all other cases.

Absolutely right.  The question ist: should
(1) the parser be able to parse A + B = 1 or should
(2) the toString() be 1 * A + 1 * B = 1.
(2) is very easy to implement, (1) would be more elegant to read. Any preferences?

Well yes indeed. Exactly my thinking.
Which probably already answers your question. I would prefere Option 1, but as a work around 2 is also fine. Would you agree?

OK. I went for the elegant solution :) This will be part of Release 1.1.  You can test the implementation in the release_1.1 branch. Please give feedback, if everything works as expected.

Will do. Thanks!

I have yet to find any problems related to the new parser. Thanks again.


Move AA abilities to CDH

This PR aims to move signature verification, image decryption functionalities from AA to CDH.
We still need to update the integration test and enclave-cc side to make sure the whole path works.
Close #412

Let's see whether enclave-cc could pass with this PR https://github.com/confidential-containers/enclave-cc/pull/319

Nice. https://github.com/confidential-containers/enclave-cc/pull/319 passes. It means that the native part of image-rs/resource/kbs works.
Let me make the PR ready for review.

@fitzthum  Thanks for the review. Fixed some parts of suggestions. There are still some discussions left. PTAL

@fitzthum Finished round two fixes. Some discussions still to be continued.


Indexation

Hi,
To find easily your project, could you add these topics:
silverbullet
silverbullet-plugs
pomodo
....
Morevover you can add your plugins in https://github.com/gorootde/silverbullet-collection
Thanks for your work

Great suggestions, thank you! I've added the topics and submitted a PR


feat: show auth providers

fixes #808
based on : https://github.com/authup/authup/blob/master/packages/client-web/pages/login.vue
Current login page:

Proposed change:


Added Qr code generator

Closes: #813

Title: Add QR generator
Name: Ananya gupta
Idenitfy yourself:  gssoc ext and hacktoberfest

Describe the add-ons or changes you've made 📃
Screenshots 📷

Type of change ☑

What sort of change have you made:

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

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney made all the changes


An error occurs due to insufficient memory when obtaining the QAOA optimization parameters

sampler = Sampler()
optimizer = COBYLA()
qaoa = QAOA(sampler, optimizer, reps=1)
result = qaoa.compute_minimum_eigenvalue(H)

I'm a beginner. I was originally going to optimize the β and γ parameters in the QAOA circuit. When I run this code with a constructed hamiltonian H, which required 24 qubits, it will then raise an error: MemoryError:Unable to allocate 256. MiB for an array with shape (16777216,) and data type complex128. Anyone can help me with working this out? Thank you.

If you use qiskit.primitives.Sampler, you cannot run a large hamiltonian because the Sampler does the statevector simulation and requires a lot of memory. I suggest Aer Primitives for the use case.
https://qiskit.github.io/qiskit-aer/apidocs/aer_primitives.html

This question seems to be answered by @t-imamichi so closing it. @Hawwwkim feel free to reopen or comment if that's not the case.


Call browserify api with advanced options

Hi,
I want to browserify my sources for a node-webkit app that allows fs to be used in the browser. I can browserify my app by the commandline via
browserify src/app.js -o build/app.js  -t [babelify --presets [ es2015 react ] ] --node

and everything works as expected.
But I can't figure out how to pass --node in my gulp file to browserify via the api call. As second parameter, I pass the opts object: I've tried setting node to true, but it seems that only the standard opts are allowed?
gulp.task('browserify', function () {
  return browserify(files.app, {
    node: true
  })
    .transform(babelify, { presets: [['es2015'], ['react']] })
    .bundle()
    .pipe(source(files.appBuild))
    .pipe(gulp.dest('./'));
});

Am I doing it wrong?

Oh no... after another search i found a solution... I'm wondering why I didn't find it a hour ago....
https://github.com/substack/node-browserify/issues/1452
But it'seems like it has to be
  return browserify(files.app, {
    bundleExternal : false,
    browserField: false
  })

sry :)


ROECCT-133-beneficial-owners-involved

JIRA link
https://companieshouse.atlassian.net/jira/software/c/projects/ROECCT/boards/562?selectedIssue=ROECCT-133
Change description
Beneficial owners involved in overseas entity - add radio buttons
Work checklist

[ ] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

closed this pr due to refractor the code and open new below one
https://github.com/companieshouse/overseas-entities-web/pull/1430


fix: add travisApiPrefix

This matches the schema of github options.
This is technically not needed, as we could just expect users to add /api themselves. Thoughts?

Hmm, this isn't enough. Or, I tried to just add /api in my existing env variable, and I still get the same error.
 An error occurred while running semantic-release: { HTTPError: Response code 405 (Method Not Allowed)
    at stream.catch.then.data (/home/travis/build/simen-bekkhus/test-semantic-release/node_modules/got/index.js:338:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  name: 'HTTPError',
  host: 'travis.schibsted.io',
  hostname: 'travis.schibsted.io',
  method: 'POST',
  path: '/auth/github',
  protocol: 'https:',
  url: 'https://travis.schibsted.io/auth/github',
  statusCode: 405,
  statusMessage: 'Method Not Allowed',
  headers:
   { server: 'nginx/1.9.4',
     date: 'Mon, 11 Dec 2017 08:41:11 GMT',
     'content-type': 'text/plain',
     'content-length': '26',
     connection: 'close',
     allow: 'GET, HEAD',
     'x-content-type-options': 'nosniff' } }

Ah, url.resolve https://github.com/semantic-release/travis-deploy-once/blob/65259a623ee5a6cbeddaa54a35f81daeff94baa9/lib/get-token.js#L15

Closing in favor of semantic-release/travis-deploy-once#32


Cannot read property 'length' of undefined  at SVGRenderer.configAnimation

I know many people got the same error but I have a weird situation. I got this error when I migrated to webpack 4 from webpack 2. It was working fine in webpack 2. I am using exact same version number and animation file just the web pack version is different.
I read in other similar [issues] (https://github.com/airbnb/lottie-web/issues/1120) and some suggested it's because of uglification but when I looked at the source, I found this in (bodymovin.js:5720)
 this.elements = Array.apply(null,{length:animData.layers.length})
it doesn't seems to be uglified. I think the problem is in the lottie-web not in this wrapper.  Any idea?

Hey there's some new updates on that issue, we found it helpful https://github.com/chenqingspring/react-lottie/issues/24

Thanks! I will try that.

I'm seeing this error in CRA2

As @eliasrodeloso suggested in #24, I fixed this by changing:
import * as animationData from '../../assets/animations/myAnimation.json';

To:
import animationData from '../../assets/animations/myAnimation.json';


raftstore: report server is busy

ref pingcap/pd#414 pingcap/kvproto#123
@siddontang @huachaohuang PTAL

LGTM

LGTM

LGTM


Debug Batch (.bat) files

The Powershell extension enables debugging (https://blogs.technet.microsoft.com/heyscriptingguy/2017/02/13/debugging-powershell-script-in-visual-studio-code-part-2/) which is a really neat. Unfortunately we still have a lot of older scripts at work due to legacy Win XP machines.
Does a similar functionality exist for Batch (.bat) files? I couldn't find any extension and there doesn't appear to be any built in functionality other than syntax highlighting.

@csholmq I'm not aware of any .bat file debugger.
@daviwil do you know whether this is even possible?

If it would be possible to debug, this is more of a feature request than a question.

How do you debug .bat files on Windows in general? Is there a debugger?

I am not aware of standard .bat debugger and I don't know how one could be implemented.

@daviwil Thanks, that was my assumption.
@csholmq Since there is no implementation in reach, I do not consider this issue a "feature request" for VS Code ;-)

@weinand Only debugger I found was a command line BDEBUGGER https://jpsoft.com/help/bdebugger.htm
Haven't tested it yet, though.

Ok, may be someone can write an extension based on BDEBUGGER...

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable.
Thanks for understanding and happy coding!

Fair enough :)


feat: Add responsive behaviour

this pr fixes issue #23  Check the attached screenshot

@AdityaSinha2305 please review this pr

Kudos!!
Keep contributing and don't forget to star the repo it will help the other contributors as well.


Filter out sockets for loopback and unknown interfaces (Backport 1.5)

Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>(cherry picked from commit 9596d79fc35b851b5f83ac0946be691dcc14324f)
Description
filter out noisy flows for lo interface when enable RTT or pkt drop
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Will this change affect NetObserv / Network Observability operator? If not, you can ignore the rest of this checklist.
[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/ok-to-test

/lgtm

/approve


QuantityCorrectionModule

Coverage decreased (-0.3%) to 71.776% when pulling 5c780d3f98fc03f8d4ad052acf1819a9a536e169 on mocia:dev into e40a8586e29c8c2a089f2e4666a07d372f4b5b42 on danliris:dev.

Coverage decreased (-0.3%) to 71.776% when pulling 5c780d3f98fc03f8d4ad052acf1819a9a536e169 on mocia:dev into e40a8586e29c8c2a089f2e4666a07d372f4b5b42 on danliris:dev.


No distinct error code for lack of internet access

Hey,
When I make a request and have internet turned off, Connect immediately errors out and throws ConnectError(code: Connect.Code.unknown, message: Optional("empty error message from source"), exception: nil, details: [], metadata: [:]).
Ideally it would let me know that this was due to no internet access. Is this possible?

Thanks for flagging this @aheze.
@jhump do you know if there's a standardized way to communicate connectivity errors through Connect errors / status codes across other implementations?

The gRPC docs suggest using "Unavailable" for this sort of network error:
https://grpc.io/docs/guides/error/#network-failures
There are cases in the Go implementation where we do try to detect and classify some errors this way. However, there are no conformance test cases for this currently. The biggest issue with adding conformance cases is with HTTP/2: if we actually break a connection as part of the test case, we will likely impact more than just the intended test case since that single connection could be used by multiple concurrent RPCs and test cases. While it wouldn't be too hard to shoehorn in test cases that are HTTP-1.1-only, the value seems low for these since some implementations have to use completely different underlying libraries for HTTP 1.1 vs. HTTP/2 (like Node JS, Dart, C++), so tests passing for HTTP 1.1 don't necessarily imply that they'd pass for HTTP/2.

Makes sense @jhump. I can look into converting network errors into the unavailable status in ConnectError (hopefully next week).


fullscreen event not triggering

I have been trying to implement this plugin on my website now and while I can add event-listeners for 'play', 'pause', etc if I add one for 'fullscreenchange' it doesn't fire.
Any idea how that could be fixed?
Edit:
$(document).on("webkitfullscreenchange mozfullscreenchange fullscreenchange", function());
works though

Hi, Globegitter,
Where should I put this code ?
Thanks,
André


register_application_commands doesn't take into consideration teams.

poise::samples::register_application_commands will say "Can only be used by bot owner" if the owner of the bot is a team. FrameworkOptions.owners should be a HashSet of every admin member of the team.

Good catch. Fixed in 864feaabb631e2f7d2b07cde4f241b194ebc777a


[BugFix] Fix iceberg catalog type missing when upgrade

Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[x] 3.0
[x] 2.5

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:disappointed: fail : 0 / 4 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/IcebergTable.java
0
4
00.00%
[176, 177, 178, 180]

@Mergifyio backport branch-3.2

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


(🐞)  "could not be added automatically to PATH. You will need to add it manually" when it was added

caused by: https://github.com/ofek/userpath/issues/51
python 3.11
Windows 10

Looks like they have no intention to resolve this anytime soon, maybe we could add some special handling.


[AutoDiff] NFC: garden tests.

Remove extraneous code.
Improve test name: test/AutoDiff/SIL/Serialization/differentiable_function_type.swift.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux


v1.16 Backports 2024-11-28

[ ] #35867 (@giorio94)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 35867

/test-backport-1.16


Slow prediction with dask

Prediction with Xgboost dask interface is much slower than expected, taking almost 5x training time.
from dask_cuda import LocalCUDACluster
from dask.distributed import Client
from dask import array as da
import xgboost as xgb
from xgboost.dask import DaskDMatrix
import time

def main(client):
    m = 10000000
    n = 100
    X = da.random.random(size=(m, n), chunks=100)
    y = da.random.random(size=(m,), chunks=100)
    dtrain = DaskDMatrix(client, X, y)

    start = time.time()
    output = xgb.dask.train(client,
                            {
                                'tree_method': 'gpu_hist'},
                            dtrain,
                            num_boost_round=500, evals=[(dtrain, 'train')])
    print("Train time: {}".format(time.time() - start))
    bst = output['booster']
    start = time.time()
    prediction = xgb.dask.predict(client, bst, dtrain)
    prediction = prediction.compute()
    print("Predict time: {}".format(time.time() - start))
    return prediction

if __name__ == '__main__':
    with LocalCUDACluster() as cluster:
        with Client(cluster) as client:
            main(client)

Train Time: 121s
Prediction time: 502s

Let me take a look.

The prediction is run for each partition/block so that there's no concatenation for data (hence lower memory usage).   When you set the chunk size to 100, you ended up running prediction 100000 times.

I see two issues here. First the chunk size is small. If you change to chunks=1_000_000, then train takes 27.2 seconds and prediction takes 151.2 seconds.
The reason prediction is 5.5x slower than train is because you need to add 'predictor' : 'gpu_predictor'. If you add this parameter then with chunks=1_000_000 prediction takes 27.2 seconds and predict takes 11.7 seconds.

I think the predictor is automatically running on GPU in this example.

No it is not. I just ran this on my DGX and posted my results above. By default XGB always uses CPU for prediction. Even if you use 'tree_method': 'gpu_hist', prediction is still on CPU. You must explicitly set the 'predictor' : 'gpu_predictor'.

Got it, took another look into the code.  CPU predictor might be chosen because data comes from host.  Thanks for correcting my mistake.

It is good you made your comment trivialfis. Many people including myself last week did not know this. As such I suggest making GPU prediction the default if a user activates the tree method gpu hist parameter.

It's a trade-off.  We made some heuristic to avoid copying data into device from host.  For training the data is not copied even you are using GPU.  So far DGX is not very accessible to wide public, so we can't make this setting.

The prediction speed has been improved quite significantly in recent PRs.


Use new Poetry installer whenever possible

Fixes #19.
Previously, the new installer hosted at https://install.python-poetry.org was only used for versions of Poetry that require it, namely 1.2+. The official Poetry documentation recommends immediate migration from the old, deprecated, get-poetry.py installer to the new installer. Hence, use the new installer for all versions of Poetry that support it, namely 1.1.7+.
See this official Poetry blog post announcing the release of 1.2.0 for additional context.

This looks good. Although I think we should fix #10 first by setting poetry config virtualenvs.prefer-active-python true conditionally on 1.2+, so that asdf+poetry behaves as expected moving forward.

Thank you for fixing #10! I rebased on your fix.

Just need to update the pre 1.2 test to something < 1.1.7

Whoops; just pushed take two.


update vulnerable gems

These were pointed out by GitHub's dependency checker.

I doubt these are actual vulnerabilities in practice considering the nature of the site. But I'm going to merge promptly anyway. After-the-fact discussion and comments are welcome.


Create Update bypass-uac-via-appinfo-alpc.yml

Correct version of rule 👍

sample added to capa-testfiles in https://github.com/fireeye/capa-testfiles/pull/10


lag after research something and unity crash when quit game

Describe the bug
i don't know if it can be reproduct.
i just start a new game and test some thing include call 20 caravan, call 20 animal migration,set pawn all skill to level20 and research something,and quit game, then it crashed
Error Log
player.log
https://gist.github.com/136068448/9ba209f5fb7391669ba2ac753b1875b0
error.log
https://gist.github.com/136068448/4485e3daba7de43282ae8be900c90f0c

It crashes during the game or it crashes after you quit the game?

after quit the game

Ok. Yes. I have also witnessed this. Unfortunately, the error log does not give me much for hints. Since it affects gameplay close to zero, and its hard to fix, I won't probably prioritize this.

It looks like you actually have 2 bugs in this game. It looks like your player.log refers to an error in pathing... Could you create a separate bug report for that using one of the bug templates, including how to reproduce? https://github.com/cseelhoff/RimThreaded/issues/new/choose

OK，i will create a new report about pathing problem

Please see:

Q&A

Mod Compatibility

Known Issues

The Community Modpack

This Mod Order Guide

Address the problems in your mod list before asking for help or submitting errors & bug reports!

You can submit a bug report here

If your submitted issue gets closed and the bug is still happening you can re open the issue.


Rename py.test to pytest.

pytest project recommends pytest entry point over py.test. (pytest-dev/pytest#1629, pytest-dev/pytest#1633)

Thanks!


add support for gdal.Open-able vfs paths

Thanks for the contribution! I'd like one more thing before merge, and that'd be two unit tests (one for raster, the other for dataset) where the dataset is loaded into /vsimem and then we verify that no error is thrown and everything works as expected.

[ ] Success unit test for vsimem objects.

yes, I originally went for that but vsimem objects are not openable with gdal.Open

Right. Is there an (easy) way to open up the test raster and test dataset files and copy them to /vsimem? I'm comfortable with writing rasters and datasets in GDAL so worst case I can add the code to read in the files, write out to /vsimem, and test.

I'll dive deeper. You may be right that this is sufficient.

maybe vsitar or vsizip could work. I am using this with vsigs and it works

Closing in support of https://github.com/jdalrym2/exactextract/pull/5


[Bug] Switching magicType feature requires a second attempt

Version
5.5.1
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=line-marker&code=PYBwLglsB2AEC8sDeAoWtJgDYFMBcya6GOAHmAQOQAqOAtiDgE4CGYArkzrAMIAWLaAHNuEOGD7cewOmKGwA6jhwBrSkQC-AGiJhgwLJBAFUxDEwhCRTKi1IQAzuvTaiuEdAAmJ1-j0GAI2BSEyJ0Bz5gAHcCMCZ2HB0zADMcNk58QjN0OhYhCABjagBPRhMMUsyAbUoHMBYCtQBdWF9iDU0k2FIAQXsHULMwSqoCthwhYCZiyi70IPYvFmmAcRZjWGSWLAdEsNhPNhYCGoBZGFnYGgTLyiVPW-o-dluAMQtbgGU2L8XKJs6RGKfUcg2IwzKVwAbtsbnNYHZHAAZFgBHBYMEpKa5MBgZhUJAwrAJDSwAANPGc7UB4WYEBwA1gVX2pmy0BYdEylAAEpZJHVZvs_CMrlgxDhBdlYHUGioCAAiajAepYeXw9CHeonACMAAYtLBtdqDdqAMwm42GgBMJptsAAnE14W10KyzOzOVQkdEGWBJdkIVyxdAJerpfVGgqlSq1UKDkcdQaALR2u0AVgN5tgdt1Tv2HXQAI0AG4gA
Steps to Reproduce

Open the link.
Click on the "stack" icon.
Click on the "stack" icon again.

Current Behavior
Chart view is changing after the second click (fon first try).
Expected Behavior
Chart view is changing after the first click (with initial stack: "Total" or etc).
Environment
- OS:Windows 11
- Browser: Version 129.0.6668.59 (Official Build) (64-bit)
- Framework: Vue@3

Any additional comments?
No response

duplicate of #16473, see also #19131
Workaround - remove stack from series.

duplicate of #16473, see also #19131 Workaround - remove stack from series.

Hmm, but what if I don't want to remove the stack? I need a default view with the stack.
For example - I have a lot of data and initial view without stack looks not so good.

So better to show a "stacked" view with the magicType button.

You can implement the stack behaviour as user-defined tool if neccessary.
Example

You can implement the stack behaviour as user-defined tool if neccessary.
Example

Awesome. Thx a lot.


react/jsx-indent not working when using string literal as a child

eslint 3.19.0, eslint-plugin-react 6.10.3
setting:
rules
  react/jsx-indent: [ error, 2 ]

minimal test using a string literal which causes no error:
(

  1

Car

)

expected this to be correct:
(

    1

Car

)

though the error is correctly thrown when you are using an expression:
(

  {`1`}

Car

)

22:3  error  Expected indentation of 4 space characters but found 2  react/jsx-indent
23:3  error  Expected indentation of 4 space characters but found 2  react/jsx-indent

There is a test that enforces this behavior: https://github.com/yannickcr/eslint-plugin-react/blob/d672588cc39334e215ff5993f859f159fc977d57/tests/lib/rules/jsx-indent.js#L198
Is this an actual bug or is there a reason this behavior is desired?

That test was removed here: https://github.com/yannickcr/eslint-plugin-react/commit/6e5f688065aa218d71742dc4b31929c16ab1078d#diff-93c6a0eb3f976d39af0b0a8843ddba24L215
and then restored here: https://github.com/yannickcr/eslint-plugin-react/commit/e9fb52d332e15686865952371c333b19af13eede#diff-93c6a0eb3f976d39af0b0a8843ddba24R215
Intentional or not, this feels like a flaw in the rule - literals should have their indentation enforced just like anything else.

@ljharb Great. I'll look into fixing this

hey guys, has this been resolved?

It's still open, so I don't think so.

According to discussion in https://github.com/yannickcr/eslint-plugin-react/issues/1662#issuecomment-360964138 this can get tricky with elements like pre. Looks like these two are duplicates.

Any solution for this?


aliae: 0.22.1 -> 0.22.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jandedobbeleer/aliae/releases.
meta.description for aliae is: Cross shell and platform alias management
meta.homepage for aliae is: https://aliae.dev
meta.changelog for aliae is: https://github.com/JanDeDobbeleer/aliae/releases/tag/v0.22.2
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.2 with grep in /nix/store/4qqv6yfcwf2gkn5jm6w3yxz4m3njm318-aliae-0.22.2
found 0.22.2 in filename of file in /nix/store/4qqv6yfcwf2gkn5jm6w3yxz4m3njm318-aliae-0.22.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

aliae

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4qqv6yfcwf2gkn5jm6w3yxz4m3njm318-aliae-0.22.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aliae https://github.com/r-ryantm/nixpkgs/archive/d05ed09abd60e0d0273fa656a016002206ce498f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d05ed09abd60e0d0273fa656a016002206ce498f#aliae

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4qqv6yfcwf2gkn5jm6w3yxz4m3njm318-aliae-0.22.2
ls -la /nix/store/4qqv6yfcwf2gkn5jm6w3yxz4m3njm318-aliae-0.22.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

aliae

Maintainer pings
cc @vedantmgoyal9 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Revert slnf feature (and associated System.Text.Json dependency)

Why was this reverted?

VS hadn't had a dependency on System.Text.Json previously, and I was having some trouble with bringing it in properly, since it also required updating some other assemblies to more recent versions. The latest build looks hopeful, but we have things we really want in preview 1 , and this was making it hard.
It will hopefully come back in soon.


Releasing 1.6.1

I'd love to use https://github.com/sbt/sbt-header/issues/30, but the latest release (1.6.0) doesn't seem to include the functionality. Would it be possible to cut a new release? \cc @fommil (as you contributed the feature, maybe you have also released it somewhere? :))

I think heikko did that.
Btw you don't need to wait, you can put plugins into your project dir

I've ended up adding the following in my project/plugins.sbt
lazy val root = project.in(file(".")).dependsOn(sbtHeaderPlugin)
lazy val sbtHeaderPlugin = uri("https://github.com/sbt/sbt-header.git")

Though, it'd really be better if a release could be cut :)

Release 1.7.0 has arrived ;-)

fyi @britter implemented it :smile:

Whohooo! Thanks, Heiko!
@fommil Thanks for the note, and please forgive me @britter for not giving credit to the right person.

@dotta happy you like it!


Configuring Microsoft: EAP-TEAP on Windows 10

It does not work on Windows 10.
I have just reinstalled Windows 10 on a test machine. I just noticed that the specified profile was not created. Not even when I copied the  section of an hand created .xml profile into the GPO profile.
Yes, it works on Windows 11, but Windows 10 probably requires a GPO that is copying the profile instead of relying on the GPO.
Everybody who demonstrated the technique probably were using a residual profile and didn't notice.
This is highly annoying.

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

ID: 1e818388-3006-88d8-23a8-a22411d6d484
Version Independent ID: 1e818388-3006-88d8-23a8-a22411d6d484
Content: Configure EAP profiles and settings in Windows
Content Source: WindowsServerDocs/networking/technologies/extensible-authentication-protocol/configure-eap-profiles.md
Product: windows-server
Technology: networking
GitHub Login: @samyun
Microsoft Alias: wscontent

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Object Dom Window has no method  __Zone_Symbol__requestAnimate frame

Error coming when i run command (ionic run android -ls) .. i have created my first ionic2 app and on browser its working good but when i deploy it on emulator it gives this error after splash screen . can any one please guide me that whats going wrong with it ... i have search allot but haven't got any proper answer .. please help me in this issue ..... Thanks

my package.json is ...
{
"name": "ionic-hello-world",
"author": "Ionic Framework",
"homepage": "http://ionicframework.com/",
"private": true,
"scripts": {
"clean": "ionic-app-scripts clean",
"build": "ionic-app-scripts build",
"ionic:build": "ionic-app-scripts build",
"ionic:serve": "ionic-app-scripts serve"
},
"dependencies": {
"@angular/common": "2.2.1",
"@angular/compiler": "2.2.1",
"@angular/compiler-cli": "2.2.1",
"@angular/core": "2.2.1",
"@angular/forms": "2.2.1",
"@angular/http": "2.2.1",
"@angular/platform-browser": "2.2.1",
"@angular/platform-browser-dynamic": "2.2.1",
"@angular/platform-server": "2.2.1",
"@ionic/storage": "1.1.7",
"ionic-angular": "2.0.0",
"ionic-native": "2.4.1",
"ionicons": "3.0.0",
"rxjs": "5.0.0-beta.12",
"zone.js": "0.6.26",
"sw-toolbox": "3.4.0"
},
"devDependencies": {
"@ionic/app-scripts": "1.0.0",
"typescript": "2.0.9"
},
"cordovaPlugins": [
"cordova-plugin-whitelist",
"cordova-plugin-console",
"cordova-plugin-statusbar",
"cordova-plugin-device",
"cordova-plugin-splashscreen",
"ionic-plugin-keyboard"
],
"cordovaPlatforms": [],
"description": "cutePuppyPics: An Ionic project"
}

Hello, thanks for using Ionic! We do not currently support Android 4.1.1 with Ionic 2. To use Ionic 2 on a device running Android 4.1.1 you will need to use crosswalk. Also, and this is just advice, i would recommend considering the fact that Android 4.1.1 only has 4 percent market share and is fast decreasing before adding crosswalk to your app. While crosswalk is a great project it will make your apk's faster and on device running 5.0 and up (which is the majority of the marketshare in android now) you will not get the benefits of the auto updating chrome webview.

Thanks sir for answer . Please tell me one thing that i have download and installed ionic2 demo project and run that on same device and its running now so what things do that have because of which it is running on my same emulator and cell too on which this above shown application is not running ...

.

Hi I have installed crosswalk but wait after slash screen white screen


Add Dockerfile

Adds Dockerfile for containerized environment
Provides:

self building
ci-like env
multi-stage build
reproducible builds

you can also do ./Dockerfile . since I used shebang and execute bit on the file.
edit: I might use alpine but went with debian:10 as base image. Happy to change if needed

I appreciate the intent, but this isn't something I want to maintain for a few reasons:

It's added burden on me, and it is not tested in CI.
If someone really needs to use xsv inside docker, then the Dockerfile is simple enough that they can write it.
I already distribute fully static executables on Linux, which should run in any Linux environment.
The Dockerfile you've written isn't going to work in the future because it uses Debian's typically ancient version of Rust.

Okay, thank you for your time!


Refactor evaluation of inbound criteria for join task

Refactor evaluation of inbound criteria for join task on inbound task completion and not on inbound task transition. This allows for different use cases such as multiple task transition from the same inbound task, inbound task transition on completion or inbound task transition on failure. Include additional check in the state machine to detect case where there is an unreachable join task where inbound criteria is partially satisfied but all inbound tasks have already completed and it will never be satisfied.
Fixes https://github.com/StackStorm/orquesta/issues/123
Fixes https://github.com/StackStorm/orquesta/issues/190

Codecov Report

Merging #194 into master will decrease coverage by <.01%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master     #194      +/-   ##
==========================================
- Coverage   94.02%   94.02%   -0.01%
==========================================
  Files          41       41
  Lines        2696     2728      +32
  Branches      530      540      +10
==========================================
+ Hits         2535     2565      +30
- Misses         99      100       +1
- Partials       62       63       +1

Impacted Files
Coverage Δ

orquesta/utils/jsonify.py
92.59% <0%> (ø)
:arrow_up:

orquesta/exceptions.py
97.61% <100%> (+0.11%)
:arrow_up:

orquesta/constants.py
100% <100%> (ø)
:arrow_up:

orquesta/graphing.py
91.74% <100%> (+0.15%)
:arrow_up:

orquesta/machines.py
86% <100%> (+0.5%)
:arrow_up:

orquesta/conducting.py
93.24% <94.11%> (-0.16%)
:arrow_down:

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 5d10f6d...4aab74e. Read the comment docs.


BUG: Console error while navigating to workspace - reported by @aneequeahmad

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

Action Performed:

Open settings page
Click on any workspace.
Navigate to Manage members
Try to add members in workspace who has same profile image/icon

Expected Result:
No console errors should display
Actual Result:
Console error displayed
Workaround:
unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.2.1-0
Reproducible in staging?: need repro
Reproducible in production?: need repro
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/196143593-5eb32599-c271-465e-a206-8e2e30d6da03.mov
Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1661464019269279
View all open jobs on GitHub

I've reported this here

This should be weekly because we can't add engineering until we reproduce the problem

Hm, can't reproduce

Unable to reproduce on Chrome v1.2.23-9, closing
https://user-images.githubusercontent.com/22508304/200003979-59c59e12-3dc1-4339-9680-0631d7648aee.mp4
@mvtglobally or @aneequeahmad please comment if I'm doing something wrong or if you're able to repro.


fix: provide configuration via interface on reconciler

Fixes #940

Not currently needed. Let's revisit this later if needed.


Instrumenting "bswap" instruction which may appears in endianness conversion function (e.g. htonl)

…g-little endian conversion
Signed-off-by: Ju Chen<EMAIL_ADDRESS>

All initialization to callback functions should be done inside void Taint::initializeCallbackFunctions(Module &M).
The added callback should also be added here to avoid being instrumented.
I think bswap should be invoked as an intrinsic instead of inline asm? Or at least the intrinsic should also be handled.
The runtime callback should uses the bytes argument to decide how many bytes to read and concat/swap.


Talos: One-liner deployment code

This PR needs version 2.2 off talhelper. Might be wise to trigger a new build of your devcontainer base image before merging.
With the great work from @budimanjojo we now can use talhelper for all the steps needed to create commands to fetch kubeconfig and reset nodes.
With the help off that I created a one-liner deploy code which mainly re-uses the separate tasks, with some checks in between. Can't use talosctl health everywhere since it won't go to green until a CNI is installed.
Also added command for nuking your cluster in a soft and hard way.

@wouterbouvy Please check my changes and let me know if they look good! Small nits here and there but great work!

Forgive me my noobiness, but how do I pull in your changes so I can test? I forgot to create a separate branch for these changes as well

Run git pull on your fork

@onedr0p Nice additions. Bootstrap code looks very streamlined now!
Good to merge from my end. Don't forget to trigger a rebuild of the devcontainer.

Whoops meant to kick off a build yesterday. It's running now
https://github.com/onedr0p/cluster-template/actions/runs/7898937443


Function namespaces should influence the schema function entries get inserted into

Description
Followup from https://github.com/GlareDB/glaredb/issues/2368
Function names and function entries in the catalog are disjointed right now. When building the builtin catalog, all functions are iterated over, and placed into the default schema (public).
This is particularly troublesome with array_to_string since it's both a datafusion function, and an alias for postgres compatability (pg_catalog.array_to_string). However, the existing logic dumps pg_catalog.array_to_string into the default schema with the name array_to_string, completely disregarding the function namespace.
The function namespace should be used when determining which schema to place functions in. I think the easiest thing to do would be move namespace from BuiltinScalarUDF to BuiltinFunction, then get the namespace when building the catalog to get the appropriate schema.

we should probably hold off on this until we do https://github.com/GlareDB/glaredb/issues/2490.
That issue will likely result in a large refactor of our function registry anyways, so it'd probably be easiest to do them both in a single pass.

[pulled out of priority queue, because it's a polish thing and not blocking anything so it's safe to defer at the moment.]


cryptsetup: 2.0.4 -> 2.0.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cryptsetup/versions.
meta.description for cryptsetup is: '"LUKS for dm-crypt"'.

Checks done (click to expand)

built on NixOS
/nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5/bin/cryptsetup passed the binary check.
/nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5/bin/cryptsetup-reencrypt passed the binary check.
/nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5/bin/integritysetup passed the binary check.
/nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5/bin/veritysetup passed the binary check.
4 of 4 passed binary check by having a zero exit code.
4 of 4 passed binary check by having the new version present in output.
found 2.0.5 with grep in /nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5
directory tree listing: https://gist.github.com/f10f4d07a53597d8bb826f2991cb1527
du listing: https://gist.github.com/106a5304805bbadcf68ebcca5b3d52a6

Outpath report (click to expand)

Outpath difference report
107 total rebuild paths
38 package rebuilds
38 x86_64-linux rebuilds
35 i686-linux rebuilds
0 x86_64-darwin rebuilds
34 aarch64-linux rebuilds
First ten rebuilds by attrpath
atom
atom-beta
bruteforce-luks
cantata
clementine
clementineUnfree
cryptsetup
ecryptfs
far2l
gnome2.gvfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A cryptsetup https://github.com/r-ryantm/nixpkgs/archive/f3545ef3c8758679d95e1bff818eadff40955d5e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5
ls -la /nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5/bin

cc @chaoflow for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: cryptsetup
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: cryptsetup
Partial log (click to expand)
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/b6w0w4wzrjgllhms0f3i855l09pc61ds-cryptsetup-2.0.5-dev/lib
patching script interpreter paths in /nix/store/b6w0w4wzrjgllhms0f3i855l09pc61ds-cryptsetup-2.0.5-dev
checking for references to /build in /nix/store/b6w0w4wzrjgllhms0f3i855l09pc61ds-cryptsetup-2.0.5-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/6z9501jgdcj4yidybx2zrxblyfaqx893-cryptsetup-2.0.5-man
gzipping man pages under /nix/store/6z9501jgdcj4yidybx2zrxblyfaqx893-cryptsetup-2.0.5-man/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/6z9501jgdcj4yidybx2zrxblyfaqx893-cryptsetup-2.0.5-man
checking for references to /build in /nix/store/6z9501jgdcj4yidybx2zrxblyfaqx893-cryptsetup-2.0.5-man...
/nix/store/87dscdc468jwdd8wy3k470hv1kxi3scd-cryptsetup-2.0.5

Success on x86_64-linux (full log)
Attempted: cryptsetup
Partial log (click to expand)
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lccfjf146lk6mxx5yk3lwvi59k05hjlj-cryptsetup-2.0.5-dev/lib
patching script interpreter paths in /nix/store/lccfjf146lk6mxx5yk3lwvi59k05hjlj-cryptsetup-2.0.5-dev
checking for references to /build in /nix/store/lccfjf146lk6mxx5yk3lwvi59k05hjlj-cryptsetup-2.0.5-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/v52x78qgk7ic0v08r6b3xzj2ma7bymbh-cryptsetup-2.0.5-man
gzipping man pages under /nix/store/v52x78qgk7ic0v08r6b3xzj2ma7bymbh-cryptsetup-2.0.5-man/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/v52x78qgk7ic0v08r6b3xzj2ma7bymbh-cryptsetup-2.0.5-man
checking for references to /build in /nix/store/v52x78qgk7ic0v08r6b3xzj2ma7bymbh-cryptsetup-2.0.5-man...
/nix/store/yhsji3v6wr11n16pnyck1qf646bg5h1z-cryptsetup-2.0.5

@GrahamcOfBorg test installer.filesystemEncryptedWithKeyfile installer.luksroot

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.installer.filesystemEncryptedWithKeyfile, tests.installer.luksroot
Partial log (click to expand)
error: while evaluating anonymous function at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/nixos/release.nix:32:25, called from undefined position:
while evaluating 'hydraJob' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/lib/customisation.nix:157:14, called from /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/nixos/release.nix:32:28:
while evaluating the attribute 'drvPath' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/lib/customisation.nix:174:13:
while evaluating the attribute 'drvPath' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/lib/customisation.nix:141:13:
while evaluating the attribute 'buildCommand' of the derivation 'vm-test-run-installer-luksroot' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/pkgs/stdenv/generic/make-derivation.nix:180:11:
while evaluating the attribute 'testScript' of the derivation 'nixos-test-driver-installer-luksroot' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/pkgs/stdenv/generic/make-derivation.nix:180:11:
while evaluating 'isFunction' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/lib/trivial.nix:288:16, called from /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/nixos/lib/testing.nix:106:12:
while evaluating 'testScriptFun' at /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/nixos/tests/installer.nix:65:19, called from /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/nixos/tests/installer.nix:267:20:
Non-EFI boot methods are only supported on i686 / x86_64

Success on x86_64-linux (full log)
Attempted: tests.installer.filesystemEncryptedWithKeyfile, tests.installer.luksroot
Partial log (click to expand)
machine# [   37.589598] systemd-shutdown[1]: Detaching DM devices.
machine# [   37.595130] ACPI: Preparing to enter system sleep state S5
machine# [   37.596464] reboot: Power down
collecting coverage data
syncing
test script finished in 459.10s
vde_switch: EOF on stdin, cleaning up and exiting
cleaning up
/nix/store/r18ds4i4hpg84sshfjy8gxwlsj90fj5r-vm-test-run-installer-filesystemEncryptedWithKeyfile
/nix/store/5sf245nr2a5rm0z330l2mi80avxs8k60-vm-test-run-installer-luksroot

Backported to 18.09 in aa6d82d9f514a306b0e111b0aa9b26ca6b076cfc


Restructure, fix parts of deal logic, improve names

bors r+

bors r-

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+


Add rebalancingInterval param to reduce pool rebalances per day

We want pools to be able to rebalance less often than 6 hours to reduce the costs. Introducing a parameter to customize that interval via command line or environmental variable.

I'll follow up with an optimized version I'm testing right now.


Bash always seems to run slowly because git is used in command line status

Issue Type: Bug
I created a new Ubuntu dev container using "Add development container files". After starting the container, I attempted to start a new bash terminal through Terminal->New Terminal.
However, when the terminal loads, there is no output and the process in the list to the right hand side says git.
If I Ctrl+C on the terminal window, git closes and I get back to bash. however, as soon as I enter another command, it immediately starts running git again.
I've got no idea what is causing this, and my container currently has no special configuration. it is simply a basic ubuntu container built with the automatic config within VS Code.
Extension version: 0.224.2
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz (12 x 4008)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.84GB (15.98GB free)

Process Argv
--crash-reporter-id 75d2bff3-b4ef-4cb2-9b19-e7eeeba2b392

Screen Reader
no

VM
0%

Item
Value

Remote
Dev Container: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz (12 x 4008)

Memory (System)
15.55GB (12.60GB free)

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvspyt640:30450904
vscscmwlcmc:30438804
vscgsvid2:30447481
pynewfile477:30450038

You can disable the prompt using git config codespaces-theme.hide-status 1.  If you have a very larger repo this can happen.
See https://github.com/microsoft/vscode-dev-containers/blob/main/script-library/docs/common.md#speeding-up-the-command-prompt-in-large-repositories

Yeah NTFS is going to be noticeably slower that if you use the WSL filesystem (or a volume, which is a Linux filesystem). It's effectively going through a share. NTFS is also less efficient with lots of small files which adds to the problem.
This is a tip on reusing the git credential manager on the Windows side in WSL if you are not ware of that: https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-git#git-credential-manager-setup
Windows and Linux also have different line ending defaults, so generally I'd recommend git cloning in WSL and using Remote - WSL extension to edit files directly if you need to rather than flipping back to Windows.  VS Code will keep things with the line endings that were originally used either way, but it helps with new files.

Alright, that makes a lot of sense, thanks.
Biggest issue personally is I'm using a piece of windows software that edits map data for a game, and it entirely fails editing when the code is hosted on WSL due to a Qt bug. Seems I'm stuck between a rock and a hard place.
Ah well, at least I know what the issues are now, and how to make the terminal usable at least. Appreciate the help, ty!

Is there a work around for this issue. I've tried adding:
.git
.git/
**/.git

to a .dockerignore file but remote container is not respecting the .dockerignore preferences. As a result I'm stuck with git bash when I don't need it.

This is a tip on reusing the git credential manager on the Windows side in WSL if you are not ware of that: https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-git#git-credential-manager-setup

this tip breaks git support inside the dev containers. It suggests to configure a windows executable as credential helper, but the executable isn't available inside the container and git refuses to start. Bind-mounting /mnt/c inside the container doesn't help either because the executable still remains unusable for some reason.

Nevermind, git config was broken in my wsl, It was therefore copied as is to the container and remained broken.

The latest version of the images and the common utils Dev Container Feature will have the "dirty" check off by default as well.


Cannot build natively on Arch Linux

System:
Arch linux
Swift - 4.1
All required libraries present.

Yes, I have installed all the equivalent packages of the Debian ones on Arch. However, I am still unable to build it.

Hi @hehaichi , the problem is with BlueSSL, which haven't quite yet released a version with support for latest SSL. Unfortunately we either wait for the author, or we add a PR.


Clearing font size crashes the app

https://user-images.githubusercontent.com/28040841/235522792-789b6465-2d6f-407f-9877-948bd7f6fd41.mov

Yes, you're right. We'll address this issue ASAP!


ISPN-14206 Update console to 14.0.1.Final

https://issues.redhat.com/browse/ISPN-14206

Thanks @karesti


[Bug] Parsing result is wrong when outputCst is false

Problem
I followed Tutorial Step 2
super input-tokens, all-tokens

Note: my code is written in CoffeeScript.
So, by default, outputCst is false.
source-code = 'SELECT column1, column2 FROM table1'
# ...
# ...
console.info parser.selectStatement()

What I get?
The last IToken object -- that of Identifier "table1".
Soon I realised that it is the return value of the rule function "selectStatement".
$.RULE "selectStatement", ->
	$.SUBRULE $.selectClause
	$.SUBRULE $.fromClause
$.RULE "fromClause", ->
	$.CONSUME tc.FROM
	$.CONSUME tc.Identifier

CoffeeScript automatically turns the last line of a function body into a return expression, so the $.CONSUME tc.Identifier in the rule "fromClause" is returned to the rule "selectStatement" and then returned when I call parser.selectStatement().
But in your tutorial, codes are in TypeScript. So I revised mine into:
$.RULE "selectStatement", ->
	$.SUBRULE $.selectClause
	$.SUBRULE $.fromClause
	return
$.RULE "fromClause", ->
	$.CONSUME tc.FROM
	$.CONSUME tc.Identifier
	return

Correct codes now. But still wrong result -- undefined.
Is this a supposed result? If so, how can I get the result?
It had confused me for an hour until I tried enabling CST output.
super input-tokens, all-tokens, {outputCst: yes}

I got an object printed like  { name: "selectStatement", children: { selectClause: Array[1], fromClause: Array[1] } }
Hooray!
Solution
I believe this issue is a bug.
If so, please fix it.
Since you have already planned to always enable CST output as a feature upgrade, you don't need to directly fixed the old result format (whatever it is, I have no chance to know) and you'd better speed up your plan forwards.

What do you expect the output to be when cst output is disabled?

Let me make sure we are in accord.
parser.selectStatement() is supposed to have a non-void return value, right?
With {outputCst: yes}, I got an object printed like  { name: "selectStatement", children: { selectClause: Array[1], fromClause: Array[1] } }
If cst output is disabled, there should be something similar but less advanced.
Anyway, I will keep {outputCst: yes} so I don't care about the old output format.

Are you trying to support old users with cst output disabled?
I suggest you just move forward and make cst output always enabled.
Why?
If I am the only one complaining about this serious bug (because I am new and followed the tutorial), that probably means everyone else who is already using chevrotain has cst output enabled and thus no one encounters this bug.

Are you trying to support old users with cst output disabled?

Yes. Chevrotain does not enforce separation of grammar and semantics, just encourages it.
Not only are there existing Chevrotain parsers using embedded semantics in the grammar.
The creation of the CST has a large performance impact. So certain use cases
may wish to avoid that.

If I am the only one complaining about this serious bug (because I am new and followed the tutorial), that probably means everyone else who is already using chevrotain has cst output enabled and thus no one encounters this bug.

CST output is pretty new. So I do not think that is the case.
Rather I still don't see the bug...

If cst output is disabled, there should be something similar but less advanced.

This is the root of the misunderstanding.
If cst output is disabled the output must be defined by the grammar writer.
If no output is defined then the created parser is a simple recognizer which
only validates the input is valid but does not perform any actions.

So, when cst output is disabled, parser.selectStatement() should return nothing?
Then I suggest, in order to keep consistency, when cst output is enabled, it should do so as well.

Do you mean that:
Parser is simply a "walker" who does nothing and produce nothing with its APIs?
I have to create my own data (for AST, most probably) and manipulate them such as columns.push(getImage($.CONSUME(Identifier)) in Tutorial Step 3?
I have to complain that Tutorial Step 2 is far from newbie friendly.
I will post another issue with my suggestion about writing Tutorial Step 2 for several reasons, this issue included.
You can close this issue now.

So, when cst output is disabled, parser.selectStatement() should return nothing?

Not exactly, The parsing rules always return the value defined by the user in the parsing implementation function. in the pure grammar example that value is undefined.
When enabling cst output that returned value is replaced by the CST Node.

Then I suggest, in order to keep consistency, when cst output is enabled, it should do so as well.

If it would return nothing then how would the user access the CST to use it in future process?
See example of CST transformed to AST
https://github.com/kdex/chi/blob/master/src/index.js#L25
The whole point of CST creation is to write pure clean grammars that still "magically" output some structure (CST). without all the verbose code to build structures inside the grammar rules.

I will post another issue with my suggestion about writing Tutorial Step 2 for several reasons, this issue included.

I am happy for any and all feedback and help specifically regarding the documentation.
However keep in mind that I'm creating a CST visitor now which means I will upgrade
the tutorial to include both CST on/off scenarios. So you may want to wait for me to finish this
major feature and documents updates before making major changes.


Add a random exponential wait strategy; Fixes #28

This adds a variant of the exponential wait strategy that waits for a
random time between the minimum provided time and an exponentially
increasing maximum time (under a maximum provided time).  This is
similar to https://en.wikipedia.org/wiki/Exponential_backoff
See #28

@rholder any chance you'll be able to take a look at this sometime relatively soon?

This looks pretty good, and it's first on my TODO list of maintenance when I circle back to this project. I should have bandwidth to ship something this week. Keep pinging this issue as a reminder if you don't see some movement soon.

Any chance of committing and releasing this feature soon? Thanks.


memory leak when dispose mesh with skeleton animation, which use gltf loader

when I use scene loaded in GLTF file, I find that dispose function in Mesh class doesn't dispose skeleton, which cause the bone texture can't dispose; and I find that mesh attached the bone can't dispose too.
I add the code in glTFLoader.ts，show like this, which cause skeleton and bone-attached mesh can dispose when dispose the skeleton-mesh. What things I should care anyway? Thank you.
// code in loaders/src/glTF/2.0/glTFLoader.ts
const assignSkeleton = (skeleton: Skeleton) => {
this._forEachPrimitive(node, (babylonMesh) => {
babylonMesh.skeleton = skeleton;
    // TODO: dispose skeleton and mesh attatched bone when dispose mesh
    babylonMesh.onDispose = () => {
        for (let bone of skeleton.bones) {
            bone.dispose();
        }
        skeleton.dispose();
    }
});

};

I think the owner of skeleton ins't the mesh, and I add the code in gltf Loader, not the Mesh class.

Hello this is because skeletons can be shared by multiple meshes  then we cannot dispose the skeleton when you dispose a mesh as this could break other meshes.
This is why the skeleton has its own dispose than need to be called separately

Please use the forum.babylonjs.com if you want to discuss that question.
We use the repo for bugs only


queue build task creation until ready

Instead of a context key could the actions be registered early? This context key means that hitting it early in startup won't do anything, unlike most other commands
Originally posted by @Tyriar in https://github.com/microsoft/vscode/pull/155250#discussion_r922087388

I think this is fixed

there's a lot going on here behind the scenes that I don't think we want to mess with


4h installing and it keeps going

Bug Description
pip seems to be installing ALL the versions of every dependency needed for aerosandbox I have tried both on win10 latest and on ubuntu 20.04.
INFO: pip is looking at multiple versions of six to determine which version is compatible with other requirements. This could take a while.
Collecting six>=1.5
It shows that message with every dependency, and it is taking forever to install. pip suggests this:
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us
what happened here: https://pip.pypa.io/surveys/backtracking
Steps to Reproduce
pip install aerosandbox[full]
Expected Behavior
System Information

Operating System: Win 10 and Ubuntu 20.04
Python Version: 3.7
AeroSandbox Verion:

Other Information

Hmmm - strange!
Can you confirm that this issue is isolated to aerosandbox? And, can you confirm that you are on the latest version of pip (do pip install --upgrade pip if not)?
For example, do the following commands work?

pip install six
pip install aerosandbox (without [full])

Assuming your pip is up-to-date and the problem is indeed limited to aerosandbox, please paste the full pip stack trace here!

Closing, in the absence of any updates.


ERROR AL0296: The type or method 'SetCurrencyCode' cannot be used for 'Extension' development.

Today we have made a new report similar to 206, standard report. This report, call the function "Set Currency Code" from the table VAT Amount Line (ID: 290). This function isnt external. Do you know how to change this function to external?

Thanks for you suggestion. I do have a few follow up questions though, before we can process:

I assume you mean Table 290 - "VAT Amount Line", not Table 206.
I can't seem to find the SetCurrencyCode function. The two below are there, but not the one you request to be exposed. Which version of NAV are you using? Did you maybe add the function yourself?

Thanks for clarifying!

Hello JesperSchulz,

You think correct. The Table is 290 - "VAT Amount Line".
The function SetCurrencyCode is standard and Im using NAV 2018 with CU-01.

I've now looked through the latest versions and no version has the SetCurrentyCode function. NAV2017 had a SetCurrency function, but that was local. Also, I doubt that we would call the global variable CurrencyCod (without e), just like CurrCode isn't a widely used parameter name in the BaseApp. I'm afraid I cannot help you, as that function is nowhere to be found and it most certainly does not exist in the upcoming Business Central release. I hope you can find another way to work around your problem.

Hello, I'm the same situation as @alvarotellez, I'm creating a report based on report 206 and my code requires function SetCurrencyCode (from table 290, VAT Amount Line) to be External. The actual message shown in Visual Studio Code is the following:

[AL] The type or method 'SetCurrencyCode' cannot be used for 'Extension' development

Function SetCurrencyCode() is located in line 460 of table VAT Amount Line (T290) and it's called from trigger SalesInvoiceLine - OnAfterGetRecord(), line 150 of report Sales - invoice (R206).
Info:

AL Extension Version: 0.12.17091
Server Version: 11.0.22292 (NAV 2018 CU6)

Found it! The function only exists in the Spanish version! I will expose the function.


FLUTTER_MAP RELATIONS: New Documentation

This message has been sent to multiple plugin authors, so it is not personalised
As part of https://github.com/fleaflet/flutter_map/pull/992 & https://github.com/fleaflet/flutter_map/discussions/927#discussioncomment-1135466, I (a documentation author) am contacting plugin authors to ensure the information about this plugin on the new documentation is correct; or alternatively, if this plugin is not yet on the existing list, to check whether you would like to add your plugin to the new documentation.
I would also like you to check you conform to these new rules:

this plugin is available via a pub.dev installation to make it easier for developers - if your plugin does not currently have a pub.dev page, please add one or let me know otherwise,
the plugin documentation includes enough information for installation and basic setup/functionality,
the plugin includes a runnable example and/or screenshots,
the plugin description contains the words ' - IN BETA' after the author link on the same line if your plugin is in beta,

Currently I have copied over the existing plugin descriptions, and you can see these here: https://flutter-map.vercel.app/plugins/list. Please note that this documentation is currently unapproved and should not be used unless otherwise directed, as some information may be incorrect or missing, or might change in the future. There is no ETA at the moment, but things seem to be moving along.
Should you wish for the description to remain the same as current on the page linked above, you do not have to reply, you can close this issue.
If you wish to change any information, please leave this issue open and add your reply as a comment.
flutter_map maintainers do not take any responsibility for this message, I am the sole author.
On behalf of myself and the flutter_map community thank you for your excellent plugin :).

Hi there,
As I've had no response, I'm going to assume that your current listing is ok as it is. Please feel free to reopen if you need anything changed.
Thanks.

Hey, sorry about the late reply!
I haven't worked on this code for a little while, but so far it is up to date and the description is accurate.
I took a look at your plugins page where mine is listed and it looks all good to me, please let me know if you need anything else, thanks!


Fix Hardhat tests for ETHDenver hackers plz

I forked this repo for my hackathon project, and wanted to test my fhevm contracts. But when I run pnpm test I get the same error that the most recent CI actions are getting. After I changed the chain id for local to 9091 in the Hardhat config, I started getting this error:

@amaury1093 the problem with building directly on testnet is that the faucet has been down, so we can't get INCO for deploying and testing very easily.


Canopy Test App shows blank screen on startup

The demo app shows a white screen and the following error(s) in the dev console:

I think there are two stages to this issue

The way the icon registry is loaded into the test project means there are effectively two instances of it.
There is an ExpressionChangedAfterItHasBeenCheckedError in the table component

Closing as no longer an issue.


Function to extract average color from blurhash

Function which extracts average color from a blur hash and returns it as SwiftUI.Color.

I have run the demo app. What do you hope to achieve by getting the average Color?

I want to add some extra styling to user interface that is connected to blurhash images. For example here I'm using it to colorize background under text near video. I have blurhash from the server so I thought it would be nice to use it for coloring too.

Okay that's fine.
PS: Your app looks amazing.

Available now as 1.0.3. Thanks for your contribution.

Thanks!


fix(lightning): ldk pay timeout

Description

Includes fix in this PR removing the occasional premature JS timeout when making a LN payment
Version bump
Include pending LN txs in activity. react-native-ldk keeps history of all pending, success or failed tx attempts so we only need to filter out failed entries.

Linked Issues/Tasks
https://github.com/synonymdev/bitkit/issues/1495
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (improving code without creating new functionality)

Tests

[ ] Detox test
[ ] Unit test
[x] No test

QA Notes
If a payment actually does time out now the recipient won't still get it.

If pending payments are now a thing, we should show them in UI respectively

If pending payments are now a thing, we should show them in UI respectively

Requested designs for this


The /r option

The article (as of Aug 31st, 2018) states "This option is available only in the Windows Server 2003 operating system." about the /r option.
It seems to work in newer versions as well.
Can someone clear up whether this just should means that the option was introduced in Win 2003?

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

ID: 2d23ea9c-cf2e-c913-faf9-fe844f4d5a21
Version Independent ID: 2ce70a9f-70ac-d0fa-e720-3765cda4666a
Content: lodctr
Content Source: WindowsServerDocs/administration/windows-commands/lodctr.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

#please-close


Crash instead of missing mod screen

Minecraft v1.16.4
Forge v35.1.15
Not Enough Creativity v1.2.2
I didn't know that Forgery had to be installed, but instead of showing the missing mod screen, the game crashes. Forgery could also be listed as a mod dependency on Curseforge.
Crash Report

Forgery isn't supposed to be a dependency, hold on.

This is what I get for testing my mods in a mini modpack...

Fixed via ForgeryTools update; no commit. Republishing to Curse now...

Ah, no worries!


Only works with 10 tabs?

Hi! thank you for sharing, I was trying with three tabs, when I change the tab width it does not update and when I swiping the view the app crash.

I have the same problem.

Hi, This plugin supposes more than 5 tabs.
If supporting, please send a pull request!

Only works for 4+ tabs,but i want to 3 tabs,the problem same as frank0ch0a.and only support for iphone not ipad.


Adding option to provide custom blocklist

I like your clean container 👍🏼
I wanted to add this option, to be able to change the blocklist via an environment setting. I hope this is an okay extension.

thx


Random nonces are not secure

Via https://github.com/laysakura/serde-encrypt/blob/9ba98fa857464e2e75c017407c0a1345d697b896/src/traits/serde_encrypt_public_key.rs#L60
While the probability can be astronomically low given a large enough nonce, the probability that a nonce will be reused still exists when it is random. Reusing a nonce under ciphers like ChaCha20-Poly1305 or AES-GCM effectively means revealing the encryption secret to an attacker that can observe both of the messages encrypted with the same nonce.
It's for that reason that protocols like TLS use sequential nonces and require implementations to change secrets when the sequence is about to overflow. The point is to guarantee that a reused nonce will never be observed.
Due to the nature of this library and lack of control over how and how many objects get serialized-and-encrypted, nor how they are transported or stored, it effectively means that this library is currently not secure.
I wanted to raise this issue to raise awareness - but do not see an easy fix given the current API, considering maintaining a sequence requires maintaining additional state on a per-key basis and defeats the convenience-centric aim of this library.

@alcore Thank you.
I thought XChaCha20 nonce is large enough so that;

the probability can be astronomically low

but

The point is to guarantee that a reused nonce will never be observed.

is quite true and very important point.
I already created issue about incremental nonce feature but close it since this report is more informative.
I will do the following. What do you think?

[ ] Adds new API to use incremental nonce (state control is sender/receiver's responsibility)
[ ] Documents about danger of random nonce (like @alcore writes here)