Fails to build

Using as a flake input, with the provided nixpkgs
Fulll result of nix log
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/7i3b43fj2bzxlk8mmpxhf54a8i32wlf7-dummy-src
source root is dummy-src
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
[naersk] cargo_version (read): 1.66.1
[naersk] cargo_message_format (set): json-diagnostic-rendered-ansi
[naersk] cargo_release: --release
[naersk] cargo_options:
[naersk] cargo_build_options: $cargo_release -j "$NIX_BUILD_CORES" --message-format=$cargo_message_format --features "sway   "
[naersk] cargo_test_options: $cargo_release -j "$NIX_BUILD_CORES"
[naersk] RUST_TEST_THREADS: 8
[naersk] cargo_bins_jq_filter: .
[naersk] cargo_build_output_json (created): /build/tmp.pf1ZMngLF1
[naersk] crate_sources: /nix/store/sp1ixc0dxq36gp6xh5gpdi0cmlcrb3qb-dependencies
[naersk] RUSTFLAGS:
[naersk] CARGO_BUILD_RUSTFLAGS:
[naersk] CARGO_BUILD_RUSTFLAGS (updated): --remap-path-prefix /nix/store/sp1ixc0dxq36gp6xh5gpdi0cmlcrb3qb-dependencies=/sources
@nix { "action": "setPhase", "phase": "buildPhase" }
building
cargo build $cargo_release -j "$NIX_BUILD_CORES" --message-format=$cargo_message_format --features "sway "
   Compiling proc-macro2 v1.0.49
   Compiling quote v1.0.20
   Compiling unicode-ident v1.0.1
   Compiling autocfg v1.1.0
   Compiling syn v1.0.107
   Compiling libc v0.2.139
   Compiling bitflags v1.2.1
   Compiling serde_derive v1.0.152
   Compiling version_check v0.9.4
error: could not compile `quote` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
error: could not compile `syn` due to 2 previous errors
error: could not compile `serde_derive` due to 2 previous errors
error: could not compile `bitflags` due to 2 previous errors
error: could not compile `proc-macro2` due to 2 previous errors
error: could not compile `libc` due to 2 previous errors
error: linking with `cc` failed: exit status: 1
  |
  = note: "cc" "/build/rustcWyMD1Z/symbols.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.0.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.1.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.10.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.11.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.12.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-5dece749ea32ea40.build_script_build.1edcd1a8-cgu.13.rcgu.o" "/build/dummy-src/target/release/build/quote-5dece749ea32ea40/build_script_build-

(... more linking errors, removed because github complained its too long)

error: aborting due to previous error

[naersk] cargo returned with exit code 101, exiting

Does xremap itself build fine on aarch64-linux?

I wrote myself a derivation with rustPlatform.buildRustPackage and xremap seems to build and run just fine on aarch64-linux

I don't have experience with crane but if it fixes this problem - I'd definitely accept a PR

Sure, I'll try to whip up PR

I finally got access to an aarch64 vm and the master branch builds just fine (nix build github:xremap/nix-flake).
Did you override any of the .follows for the flake?


Added support for package levels

Modified the replaces_or_add_into_file_tail function so that it adds changes to class levels before the ending tag.

Closing this. Keeping focus in #295


flutter_export_environment.sh: line 8: inherited: command not found

flutter 1.24.0
xcode 12.5.1
I use  create -t module  to develop my app。
when I use "debug" model ，everything is ok。
but when I just use custom mode like “profile”，the xcode report this error。

Is there anyone same to me？

Hi @Wbqqqq
Ar you running hidden.ios in Xcode from a module or native that uses the issue in Xcode?
You seem to be using an older version of stable
Can you please upgrade to the latest  stable and try again
Execute the following commands to upgrade
flutter channel stable
flutter upgrade --force
flutter doctor -v

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


kindly give me suggestion

hello sir,
kindly give me suggestions for resume upload file like google drive. if client upload big file and when his network are gone while upload progress is 50% after some time network is arrived then file upload are resume means automatic start to upload.
Thank you,
prashant

The SDK doesn't offer an automatic way to do this, but the way you would implement this in your app's code using this Dropbox SDK is to use "upload sessions". (They're required for uploading anything larger than 150 MB anyway.)

filesUploadSessionStart
filesUploadSessionAppendV2
filesUploadSessionFinish

When using upload sessions, you upload files in pieces, so if the connection is lost, you can wait for it to come back, and then continue uploading the next piece of the file.


noStartAreas

Do you want to request a feature or report a bug?
feature
What is the current behavior?
I want to start select from a container, but not from selectable elements.
For example, we have a container and a many elements with margin.
And we need to use d'n'd for these elements.
So selection must starts from gaps between these elements.
What is the expected behavior?
We need some option like
noStartAreas: ['someSelector']
In my project (React) i do it like that:
const rowClassName = 'someClassName';

...

.on('beforestart', evt => {
    if (
      evt.oe.path.some(item => {
          if (item.className) {
              const classes = item.className.split(' ');

              if (classes.includes(rowClassName)) {
                  return true;
              }
          }

          return false;
      })
    ) {
           return false;
      }
})

May be there is a better solution but this works.
I hope this will be useful to someone :)

I would consider this as the best solution, beforestart was introduced for exactly this purpose. Anyway you can simplify your code by using classList and removing redundant conditional-statements:
on('beforestart', evt => {
    return !evt.oe.path.some(item => item.classList.contains(rowClassName));
});

First we check if there's any element with the class in rowClassName, then we negate the value since we don't want the selection to start if we found such an element :)
If you use a conditional-statement to return true or false you can simply return the condition itself and negate it if necessary.

You are right, it will be more shortly :)
Minor fix:
.on('beforestart',evt =>
    !evt.oe.path.some(
        item => item.classList && item.classList.contains(rowClassName),
    ),
)

I've created a examples.md file were future requests like this can be demonstrated :)


Adding False Friends Dataset to German MTEB

Hi all,
dataset:
https://huggingface.co/datasets/aari1995/false_friends_en_de
associated paper
this dataset can be used to test german and especially multilingual models for their understanding capabilities of "false-friends".
false friends are words that sound the same / spelled similarly but mean different in different languages.

May I add it to the german MTEB tasks and if so, what should I consider ? Is it a reranking task?
Thanks and all the best
Aaron

Hi @achibb we very much welcome contributions.
There is a guide to adding a dataset here. Generally, we want a new dataset to cover something previously not covered by the benchmark. This indeed sound like such a case.
To me, it seems like a pair classification task where the pairs would be as follows:
(input sentence, true_synonym, label=positive)
(input sentence, false_friend, label=negative)

I'm interested and would like to offer any help with this. Happy to collaborate or take on any tasks needed. Let me know!

Wonderful @KranthiGV! I believe there are some potential good additions in the Aya and OpenAssistant datasets (large multilingual). If you start working on them please create an issue so that others can see that you are working on it. Alternatively, if you are less interested in dataset creation and more interested in improving the codebase then we also have a few tasks there.
@achibb do you have the time to add this dataset?

Yes it is on the plan for today or latest next week. Is this fine or does this intervene with some release ?
Gesendet von Outlook für iOShttps://aka.ms/o0ukef

Von: Kenneth Enevoldsen @.>
Gesendet: Friday, April 12, 2024 11:32:45 AM
An: embeddings-benchmark/mteb @.>
Cc: achibb @.>; Mention @.>
Betreff: Re: [embeddings-benchmark/mteb] Adding False Friends Dataset to German MTEB (Issue #331)
Wonderful @KranthiGVhttps://github.com/KranthiGV! I believe there are some potential good additions in the Aya and OpenAssistant datasets (large multilingual). If you start working on them please create an issue so that others can see that you are working on it. Alternatively, if you are less interested in dataset creation and more interested in improving the codebase then we also have a few tasks there.
@achibbhttps://github.com/achibb do you have the time to add this dataset?
—
Reply to this email directly, view it on GitHubhttps://github.com/embeddings-benchmark/mteb/issues/331#issuecomment-2051397283, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKBF2KS6THNV43AZSHHALTDY46S33AVCNFSM6AAAAABF6SFYGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGM4TOMRYGM.
You are receiving this because you were mentioned.Message ID: @.***>

The PR for false friends as pair classification model:
https://github.com/embeddings-benchmark/mteb/pull/349
tests so far look aligned with the research, even though the method is slightly edited. What do you think? Anything i need to do else? :)
Thinking about doing such tests for other languages as well.

Thanks @achibb - Will respond to the above in the PR

Nice thanks @KennethEnevoldsen I adjusted it except for two points where I have not found a use of the metadata in any file I looked.
So if given some feedback I would work it in but would also be fine for me to go with the current status. Also excited to see what @Muennighoff thinks in including it on run_mteb_german.py and benchmarks as I see this as a quite nice opportunity for adversarial testing :)
Enjoy the weekend guys!

Yeah metadata in the old datasets is not great (we are working on it!), but the documentation for adding a new dataset have some examples.
Love the adversarial testing part! Would love to see more datasets like this one

Yeah no worries :).
Yeah totally. I am also trying to contribute and am currently forming a group for multilingual stuff at hf.co/multilingual
feel free to join anyone who wants and has time and would love to see some more languages creating false friends tests.

Ahh that is great. Is it targeted at adversarial-style tests?


Fix Schedule API, cleaning and maintenance

What was changed

Removed buildkite.
Added Symfony 7 packages.
Fixed bugs in Schedule API.

Why?

Buildkite isn't used in this package.
New versions of Symfony packages need to be added for compatibility with all frameworks.
Bugs in Schedule were identified during more in-depth manual testing of the SDK.

Checklist

Part of #228

@Sushisource I think it need to disable buildkite integration with this package


Component stubs should render default slots

Version
1.0.0-beta.16
Reproduction link
http://google.com
Steps to reproduce
<template>
  <v-layout>
    My text
  </v-layout>
</template>

import { createLocalVue, shallowMount } from '@vue/test-utils'
import Vuetify from 'vuetify'
import Vuex from 'vuex'
import Component from './Component.vue'

describe('components | Component', () => {
  let localVue

  beforeEach(() => {
    localVue = createLocalVue()
    localVue.use(Vuetify)
    localVue.use(Vuex)
  })

  describe('template', () => {
    it('should match snapshot', () => {
      // When
      const wrapper = shallowMount(Component, { localVue })

      // Then
      expect(wrapper.element).toMatchSnapshot()
    })
  })
})

When I comment     localVue.use(Vuex) , it shouldn't affect my snapshot, because I am not using any store in my component
What is expected?
Green test
What is actually happening?
Jest Snapshot result:

-

    My text

could you provide a template of CodePen, CodeSandbox if you want a link, please?

Can you add a reproduction on CodeSandBox—https://codesandbox.io/s/m4qk02vjoy?

Yes :  https://codesandbox.io/s/vvk1pw1w3l
in TestComponent.spec.js, I commented
localVue.use(Vuex)
and the snapshot test fails
But I am not using Vuex inside this component

I don't think this is a bug, @trollepierre . I was able to get your test passing using this code:
import { createLocalVue, mount } from '@vue/test-utils'
import TestComponent from "./TestComponent";
import Vuetify from 'vuetify'

describe('components | Component', () => {
  // let localVue

  beforeEach(() => {
    localVue = createLocalVue()
    localVue.use(Vuetify)
    //localVue.use(Vuex)
  })

  describe('template', () => {
    it('should match snapshot', () => {
      // When
      const wrapper = mount(TestComponent)

      // Then
      expect(wrapper.vm.$el).toMatchSnapshot()
    })
  })
})

What I did

wrapper.element is not valid. For snapshot, you should can use wrapper.vm.$el or wrapper.htmI()). I recommend wrapper.html(), it gives a nicer output. In your case, I had to write wrapper.vm.$el to match the snapshot.

Use mount instead of shallowMount. I think you should almost always use mount for snapshots, otherwise you end up stubbing everything out. Since you were using shallowMount, the <v-layout> component was stubbed out, so vm.$el was empty.

Vuex does not appear to have any relationship to this test and doing localVue.use(Vuex) should not have any impact on the test. You can include it or not, and the test still passes if you make the above changes.

Actually wrapper.element should be the same as vm. $el. If it's not then
that's a bug
On Mon, 4 Jun 2018, 14:16 Lachlan<EMAIL_ADDRESS>wrote:

I don't think this is a bug, @trollepierre
https://github.com/trollepierre . I was able to get your test passing
using this code:
import { createLocalVue, mount } from '@vue/test-utils'import TestComponent from "./TestComponent";import Vuetify from 'vuetify'
describe('components | Component', () => {
// let localVue
beforeEach(() => {
localVue = createLocalVue()
localVue.use(Vuetify)
//localVue.use(Vuex)
})
describe('template', () => {
it('should match snapshot', () => {
// When
const wrapper = mount(TestComponent)
  // Then
  expect(wrapper.vm.$el).toMatchSnapshot()
})

})
})
What I did

wrapper.element is not valid. For snapshot, you should can use
wrapper.vm.$el or wrapper.htmI()). I recommend wrapper.html(), it
gives a nicer output. In your case, I had to write wrapper.vm.$el to
match the snapshot.
2.
Use mount instead of shallowMount. I think you should almost always
use mount for snapshots, otherwise you end up stubbing everything out.
Since you were using shallowMount, the  component was
stubbed out, so vm.$el was empty.
Vuex does not appear to have any relationship to this test and doing
localVue.use(Vuex) should not have any impact on the test. You can
include it or not, and the test still passes if you make the above changes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-test-utils/issues/658#issuecomment-394350590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMlbWwcs1_kHq7MTDZj33qnDbKWFBlUGks5t5TMxgaJpZM4UOYwV
.

I checked. wrapper.element is the same as vm.$el

If you use shallowMount, the v-layout component will be stubbed out, that's why your snapshot is empty.
Re @eddyerburgh , wrapper.element also works fine.
@trollepierre Vuex does not make a change in the test - how did you come to this conclusion?
Bit quick on the thumbs down... using shallowMount, there should be no way to generate that snapshot, because it will stub out v-layout by default.
I forked your repo and commented out all the Vuex related stuff, and it seems to be passing: https://codesandbox.io/s/m7xw536p9j
Something odd is going on, having a closer look

Hey so the problem is that shallow stubs components and doesn't render slots by default. Thinking about it, I think we should add this. There have been a few other people who have been stung by this, and the slot content really is part of the component you're testing.
shallow only stubs registered components, so when you don't use a localVue, it it doesn't stub the v-layout component.
For now, you can fix it by using a custom stub:
const VLayoutStub = {
  render: function(h) {
    return h("div", { class: "layout" }, this.$slots.default);
  }
};
const wrapper = shallowMount(TestComponent, {
  localVue,
  stubs: {
    "v-layout": VCardStub
  }
});

Or by using mount as @lmiller1990 suggested

Your suggested workaround (passing this.$slots.default) it something I should add to the createStub object. We could have a renderSlots option, where the default is true.
createStub('v-layout', { renderDefaultSlot :true })

This could be then used by users, and internally as well.
Any idea why adding localVue.use(SomeLib) after .use(Vuetify) caused the test to pass?

Hey so the problem is that shallow stubs components and doesn't render slots by default. Thinking about it, I think we should add this. There have been a few other people who have been stung by this, and the slot content really is part of the component you're testing.

Yes, please 👍  Using mount() renders child components too much. I don't want to care about the internal DOM structure of child components but DOM structure which I wrote in a slot of a target component.

https://github.com/vuejs/vue-test-utils/issues/658#issuecomment-394386042 shows Unknown custom element: ... warnings so I used the following for now.
// XXX: Create a general stub with its default slot
// https://github.com/vuejs/vue-test-utils/issues/658
const createSlotStub = (name) => {
  // Prevent 'Unknown custom element: ...'
  const config = require('vue').config;
  if (!config.ignoredElements) {
    config.ignoredElements = [];
  }
  config.ignoredElements.push(name);
  // Return functional component
  return {
    render: function(h) {
      return h(name, {}, this.$slots.default);
    },
  };
};

Then
const wrapper = shallowMount(TestComponent, {
  localVue,
  stubs: {
    "v-layout": createSlotStub('layout-stub'),
  }
});

beta.21 will render default slots 👍

@eddyerburgh I know that this was closed quite a while ago, but we're still wondering about
localVue.use(Vuetify)
locaVue.use(Vuex)

vs.
locaVue.use(Vuex)
localVue.use(Vuetify)

If we run exactly the same test case (besides changing the order of the use commands) shallowMounting a simple Vue component looking like this:

  <v-container>
    <v-layout
      <v-flex>

hello

      </v-flex>
    </v-layout>
  </v-container>

This is what wrapper.html() looks like in the first case:
 console.log test.js:16
    -- Vuetify first --
  console.log test.js:17

hello

This is what wrapper.html() looks like in the second case:
  console.log test.js:27
    -- Vuetify second --
  console.log test.js:28

<vuecomponent-stub></vuecomponent-stub>

Shouldn't this be the same? And will the changes solve this problem?

That's odd. It looks like the first output is rendered with mount, and the second with shallowMount.
createLocalVue seems to be doing something strange, maybe. https://github.com/vuejs/vue-test-utils/blob/dev/packages/test-utils/src/create-local-vue.js or  createInstance could be suspect.

@lmiller1990 Yes! I thought you found out the same as you stated this in one of your posts above? That's why I added it here and didn't create a new bug report.
I can upload the minimal example to my GitHub account and link it here if that would help.

Hm. Eddy mentioned this above:

shallow only stubs registered components, so when you don't use a localVue, it it doesn't stub the v-layout component, because Vuetify hasn't been installed.

It looks like when you call localVue.use(Vuex) it somehow replaces? overrides? localVue.use(Vuetify), so it is as if localVue.use(Vuetify) never happened. This could be incorrect. I'm going to repro locally and play around a little.
Do you have an actual example of what you are testing? Although this is my personal (and strong) opinion, a unit test shouldn't be pulling in so many dependencies. What is your actual goal of the test you are writing? PS: this is still a bug, I think, and needs to be addressed. I think localVue has some other related bugs, maybe there is another way to implement createLocalVue... 🤔

@lmiller1990 Here is a repo for you to play around: https://github.com/miriamgreis/vue-test-utils-vuetify-and-vuex
We use Vuetify for our layout and Vuex to store our data. So why shouldn't we use both of them in our tests? We need to mock the store in order to test our components.

Thanks for the repo. Sure, you can use both if you need it for your unit test. The test you posted above doesn't have Vuex in the test, so I was wondering what kind of test you are writing.

I really just created a quick and easy example because the real code is from a customer project with quite complex data stored with Vuex. We do use is in these tests, but the problem happens anyway, so it's not really relevant here, I guess.

Since you are just testing the component, the complexity of the store shouldn't be too much trouble. I used to have trouble writing tests for the same reason. I learned this from my experience and wrote about it here.

if you are testing if you component renders something based on Vuex, eg using state or getters, you should mock those. Since you most likely are using a computed property to return this.$state or this.$getters.someGetter, you can test it like this:

const wrapper = shallowMount(Foo, {
  computed: {
    myGetter() => 'whatever value you want'
  }
})

This gives you control over the state. You can easily test edges cases. The component is simply a function of the current state of the app, regardless of whether it is local state, Vuex, or from props. Use the mounting options like propsData and computed to test your component correctly represents the state.  In this case, what you are really testing is:

did I commit/dispatch the right handler?
did it have the right payload

In that case, you can use mock functions and a mock store (or a real store, with mock mutations and action). The man himself, Edd, wrote about it in the documentation's guides section here.
Since I learned to use mocks and stubs and minimize dependencies, my unit tests became more simple and easier to write. Hopefully that can help you.
PS, I still think that this is a problem and am investigating. People should be able to write more end to end like unit tests if they want, and in some cases those tests are more useful.
I am trying to collect my experience in a series of articles here to help others learn more about testing Vue (I am still learning myself). It's a WIP but maybe that can help you as well.
I'll post if I make some progress on this. I would like to be able to use any Vue plugin without problems in tests.

@lmiller1990 Thanks for providing all the help and the links, but what you describe in your article is exactly what we already do in our tests. ;-) We use mocks and stubs for almost everything. Nevertheless, it requires us to have: Vue.use(Vuex).

@miriamgreis sure, no problem.
If possible it would be great to get a full reproduction of your problem. After trying some stuff out now, I am not having the same problem you appear to be.

When I use shallowMount, everything stubs out nicely (expected, as of beta 20).
When i use mount, the entire DOM tree renders nicely.

One problem I encountered on the way, and I suspect a lot of people encounter is Vuetify appears to require a v-app component as the route. If you are testing components in isolation, you probably do not have a v-app. The way I handled it is like this:
import { createLocalVue, mount, shallowMount } from '@vue/test-utils'
import HelloWorld from<EMAIL_ADDRESS>import Vuex from "vuex"
import Vuetify from "vuetify"
import RootApp from<EMAIL_ADDRESS>

const VAppRoot = (Child) => ({
  components: { Child, RootApp },
  template: "<root-app><child /></root-app>"
})

describe('HelloWorld.vue', () => {
  const localVue = createLocalVue()

  localVue.use(Vuetify)
  localVue.use(Vuex)

  it('shallowMounts', () => {
    const comp = VAppRoot(HelloWorld)

    const wrapper = mount(comp, {
      localVue
    })

    console.log(wrapper.html())
  })
})

shallowMount:
<rootapp-stub></rootapp-stub>

Thanks for taking so much time to try to solve the problem. Your example obviously works because you put your own component around the Vuetify components. Our example has a Vuetify component as a root component as you can see in the provided example. You find the reproduction code in the repository I linked.
There is also another solution to the v-app problem which doesn't blow up the test code and require extra components: https://github.com/vuetifyjs/vuetify/issues/1210

Hm, did you link the right repro? It doesn't have Vue or Vuetify (or maybe I misunderstood something).
Thanks for the link to the Vuetify issue, I can use it to repro the issue more accurately.
Not sure if I can help more, I still want to look more into the potential Vue.use issue. Hopefully beta.21 will help with people using Vuetify.

@lmiller1990 Sorry, it's my fault that I didn't doublecheck the repository. Looks like I pushed to the wrong one yesterday. :-( You will find the right code overthrew now.
Maybe it's a language issue, but just to state this more clear: I don't need any of your explanation. I really appreciate that you provided these explanations on how to use Vuex and Vuetify in test, but I already now all of this. We already use Vuex and Vuetify successfully in our unit tests. So you don't need to explain anything else, just look into the potential Vue.use issue, because this is what we are interested in. ;-)

Ok, thanks for the repo. I tried it and can repro the problem locally. I'll use this to find the problem. Thanks for clarifying.

Okay, I isolated the problem. The problem is any plugin that calls Vue.extend seems to introduce the bug. Here is a more minimal reproduction: https://github.com/lmiller1990/vue-test-utils-vuetify-and-vuex . This is most likely related to how createLocalVue is implemented.
Basically
const myPlugin = {
  install: function (Vue, opts) {
    Vue.extend({
      // doing Vue.extend breaks it
    })
  }
}

I think this causes the problem in this issue, too:  #819 . I'll keep working on it this week, and let you know if/when I solve it 👍

Thanks very much. :-)

@lmiller1990 I have a test case that requires me to make full mount and it crashed without encasing it in v-app, so I used method you shown here and got test to run with full mount. How can I access child component's instance tho?

@Mourdraug I am not sure if I understood correctly or not but can you do something like:
import Child from "./Child.vue"

const wrapper = mount(Foo)
const child = wrapper.find(Child)
const childVm = child.vm // this is the child component instance

I was sure I tried find() before and failed. But it works now. Thanks a lot.


Adding views in state crash it

All in main view stop displayed when I uncomment views in application
.state 'users.show',
  url: '/:id'
  controller: "UserController"
  templateUrl: 'users/show.html'
  # views:
  #   "poll_table":
  #     templateUrl: "users/poll_table.html"

show.html.slim code below
h2 {{user.email}}

div ui-view="poll_table"

This code:
.state 'users.show',
  url: '/:id'
  controller: "UserController"
  templateUrl: 'users/show.html'

is sugar for this code:
.state 'users.show',
  url: '/:id'
  views:
    "":
      controller: "UserController"
      templateUrl: 'users/show.html'

And you can't mix the sugar version with the non-sugar version.
Change your code like so:
.state 'users.show',
  url: '/:id'

  views:
    "":
      controller: "UserController"
      templateUrl: 'users/show.html'
    "poll_table":
      templateUrl: "users/poll_table.html"

This wasn't well documented until recently in the 1.0 branch: http://angular-ui.github.io/ui-router/1.0.0-alpha.3/interfaces/ng1.ng1statedeclaration.html#views (at the very bottom)

@christopherthielen, thank you :+1:


Remove html tags

This change is

Jenkins job mixer/presubmit passed

Jenkins job mixer/presubmit passed

Jenkins job manager/mixer-pr passed


Added a preselect option to the cmp menu

To fix #14.

Something I've noticed when testing: if we continue typing while the autocompletion window is opened, it stays open and the result just get filtered. My question is, when in "not preselect" mode, should the selection reset when the completions items get updated?

Yep, good point. I believe you'd want to check if the cursor position changes, rather than checking if the items have changed, since items can be updated twice per keystroke. On keystroke, the list gets immediately re-filtered with stale data. The sources are called and the list gets updated again asynchronously, if there's new data

Hmm, I didn't run into this, so it'd be hard to check. As far as I know this shouldn't impact this PR much? the only modification are in the select_prev/next function.
function autocomplete.select_prev()
  if not autocomplete.win:is_open() then return end

  local cycle_from_top = config.windows.autocomplete.cycle.from_top
  local l = #autocomplete.items
  local line = vim.api.nvim_win_get_cursor(autocomplete.win:get_win())[1]
  if line <= 1 then
    if not cycle_from_top then return end
    line = l
  else
    line = line - 1
  end

  autocomplete.set_has_selected(true)

  autocomplete.win:set_option_values('cursorline', true)
  vim.api.nvim_win_set_cursor(autocomplete.win:get_win(), { line, 0 })
  autocomplete.event_targets.on_select(autocomplete.get_selected_item(), autocomplete.context)
end

Which get line info from the current cursor position.
What could happen if I understand what you are saying is that autocomplete.open_with_items(context, items) gets called with new items, resetting the cursor position because of this line: autocomplete.set_has_selected(autocmp_config.preselect).
But I'm not sure what to do if this is the case. the items are changed, and the item the user was on could be removed. So where should the selection/cursor go?

You're right, I forgot to stage those, my bad

Thanks again, I'll wrap up the remaining small changes on main

I'm a bit confused here. Is this feature wrapped up? I cannot seem to get it to work.

I´d assume you have one of the lastest commit and windows.autocomplete.preselect = false.
The only change you should see is no item is selected by default when the completion menu open.

When pressing one of the select_next or select_prev key, the first/last item should be selected, Indicated by a cursorline showing up. llike this:

If no item are selectec, pressing the accept key will simply execute it's normal action. In my case  will simply insert a new line.

If a item was selected, It will insert it.

I'm on the latest version and, weirdly, that doesn't work.

If you pinned the plugin to 0.2.1 then that makes sense, the changes haven't been released yet

@noomly Yeah, that was my mistake. Silly. Got it working now! 👍🏼


Will this project upgrade from Bigint 3.0 to Bigint 5.0?

name: Question about libary version upgrade
about:
This project has the library of Bigint 3.0. Will it upgrade to Bigint 5.0?

@beckyzhang not familiar with what has changed from v3->5. Is there something useful?

@beckyzhang not familiar with what has changed from v3->5. Is there something useful?
The project is using a libary of bigint v3.0. The latest version of this libary is 5.0. Will this project plan to upgrade?

@hboon The project is using the Bigint libary in v3.0. The latest version of this libary is 5.0. Will this project plan to upgrade?


Scrollable issue with Firefox

Not a very big issue, but with firefox, if you press the "down" key, the screen scrolls down a bit, breaking the nice layout of the app. I've tracked it down to div with id dragGhost. If I change to display: none (in addition to the second remark below) then there is no possible scroll anymore and the layout is perfect. Is there any reason for position:relative and not absolute ?
The later would remove it from the flow, and will not cause the layout to overflow (and yes, body has overflow: hidden, but it does not apply here).
And, the textarea with id copyAreamust have its style property bottom set (else it's not positioned correctly). I've set it to 1px and it fixed the scrolling issue.
So the changes required to remove that overflow are:
#dragGhost {
    position: absolute;
    top: 0px;
    left: -99999px;
}

#copyArea {
   bottom: 1px;
}

@X-Ryl669 those changes don't seem to matter by me.

position: absolute will break the drag functionality, at least in Firefox.

Strange... It works for me on Firefox, the "1 song" green tag is displayed attached to the mouse position while dragging.
@bdgold: I don't understand your comment. Do you mean the changes don't work for you ?

@phanan: Another solution seems to display: none it and change to display: inline-block upon drag start event (and back to display: none when dragging stop). The position: absolute, top, left however does not require any style change in the JS code and I think it's cleaner.

@X-Ryl669 correct, it didn't fix it by me.

@bdgold: You need to add these properties in the Firefox debugger at the right place (not in the code, since if they are loaded before the app's CSS style, they'll get overloaded by the app).

Do you want to try a PR for this ?

I changed the css in app.vue and then ran gulp, is that not the way to try it? I'm not very familiar with the firefox debugger.

Do you want to try a PR for this ?

Why not? it can always be rejected ;-) , and I can then test it as well.

Here it is: PR #459

Any of you tried the PR yet ?

Yes, it works for me.

Fixed in the current repository


create a PyPi package

Once the testing is done, we should have a PyPi package as we have everything ready for it. One thing that needs to be clear though is that for the Travis process, we don't use the PyPi package but do it from python setup.py install

Agree! Do you want to do nightly builds for pypi or builds for every release. I guess I also need to research what would be preferable here.

I think nightly builds will be good as I'm seeing a lot of people having issues where the pip package and master are not in sync. Or what do you think? I guess the other side is that if we take just from last stable release, then there is a little less stress. First seems to lead to more organized workflow, so ok, I vote for that.

Ok great, with the latest version v.0.2.0 the time has come...to make a pypi package so that we can allow just pip install on the latest stable release.

I think we're doing this last once everything else for the current milestone is done in the next 10 days or so. Then we make a release out of it, and have to remember to include setup.cfg to the repo root with:
[metadata]
description-file = README.md

This seems like the best way to do it:
http://5minutes.youkidea.com/howto-deploy-python-package-on-pypi-with-github-and-travis.html


ARROW-12513: [C++][Parquet] Parquet Writer always puts null_count=0 in Parquet statistics for dictionary-encoded array with nulls

This fixes two issues.

The null_count must be obtained from the indices array and not the values array
The min/max should be based on referenced values and not all values in the values array

Note: This further adds a dependency from parquet onto arrow::compute (I use it both to compute the unique indices and to take the referenced values).  This dependency already existed (column_writer.cc relies on arrow::compute::Cast) so I'm pretty sure this isn't a problem.  Related: ARROW-8891

This also fixes: ARROW-11634

And apparently: PARQUET-1783 a triple wammy

@westonpace this looks ok to me, I think the only real blocker is not putting this in the parquet statistics class but moving to the call-site.

@emkornfield Thanks for your quick review.  I believe I've addressed your points (except possibly for the WriteIndicesChunk note).  I don't think this will make the cutoff for RC0 but hopefully we can get it in if there is a follow-up RC.

I modified the test to test the case where there are multiple row groups and I added a small optimization (it will only call compute::Take if the # of referenced indices is smaller than the size of the dictionary).  There is one outstanding comment on column chunk level statistics vs page statistics but if that is resolved (and CI remains green) I will go ahead and merge.

LGTM module placement of stats update (inside per page processing or not)

Also, it seems we were not writing page statistics at all for data page V2.  I added it back in but wasn't sure if that was intentionally disabled for any reason.

CI failures appear unrelated.  I'll merge this tomorrow assuming no concerns about https://github.com/apache/arrow/pull/10729#discussion_r681470482

Forgot about this.  Rebasing and then merging on green.

forgot to to comment, these changes looks fine.  thanks for tracing down the paths.  I don't know why stats for datapagev2 would have been disabled.


name replaced by person as deprecated

faker.name is deprecated since v8.0 and will be removed in v10.0.
It is replaced by faker.person

For this to work, I think you'd need to bump the package as well 🤔

Do you have any idea why the linter is failing ? I've just changed faker js in package.json


Documentation missing from 2.18.2 onwards

All of a sudden in 2.18.2, Topic is missing a bunch of documentation sections. I don't think this was intentional, was it?
Compare
https://googleapis.dev/nodejs/pubsub/2.18.1/Topic.html
to
https://googleapis.dev/nodejs/pubsub/2.18.2/Topic.html

It looks like the new docs are going here. There are still some things that need improvement in there, like the ToC isn't organized per library, but you should be able to find everything in there.
Out of curiosity, where did you find the link to googleapis.dev? I want to start fixing those since the Cloud site is the new standard going forward.

There's a link to it here as "API Reference': https://cloud.google.com/nodejs/docs/reference/pubsub/latest

Okay, I get it now - that linked page is actually generated from the README.md, so that just needs to be updated.


Can we use this library without androidX

This library is one of the few that are preventing us from turning off jetifier (which would be a big performance improvement). Are there any plans to upgrade to android?
if we were able to remove jetfier it would help us to improve our incremental build time.
https://adambennett.dev/2020/08/disabling-jetifier/

What do you mean? the library already uses androidx.

What do you mean? the library already uses androidx.

Sorry. My mistake, What I mean is Drop Jetifier.
This is the only library in our app that still uses the old support library so it prevents us from disabling Jetifier which potentially increase compilation time required to process dependencies.
Back at 2018, Google announced that Support Library would be refactored into the AndroidX namespace, which was completed with Support Library 28 and the announcement of AndroidX 1.0. Jetifier helps migrate third-party dependencies to use AndroidX.
You can use this plugin for disabling Jetifier, https://github.com/dipien/bye-bye-jetifier

Sorry. My mistake, What I mean is Drop Jetifier.
This is the only library in our app that still uses the old support library so it prevents us from disabling Jetifier which potentially increase compilation time required to process dependencies.
Back at 2018, Google announced that Support Library would be refactored into the AndroidX namespace, which was completed with Support Library 28 and the announcement of AndroidX 1.0. Jetifier helps migrate third-party dependencies to use AndroidX.
You can use this plugin for disabling Jetifier, https://github.com/dipien/bye-bye-jetifier

I tried to remove Jetifier. none of your code module uses legacy Android support library. there are some usage in com.psoffritti.librarysampleapptemplate:core.
Can you fix those?

I tried to remove Jetifier. none of your code module uses legacy Android support library. there are some usage in com.psoffritti.librarysampleapptemplate:core.
Can you fix those?

Sure, I'll have a look.

Sure, I'll have a look.

+1 waiting for this features as well

In my case, this is preventing us to disable jetifier:
Graphs to this dependency:
 +---com.github.PierfrancescoSoffritti:AndroidYouTubePlayer:10.0.5
     +---com.github.PierfrancescoSoffritti.AndroidYouTubePlayer:chromecast-sender:10.0.5
          +---com.google.android.gms:play-services-cast-framework:16.1.2
               +---com.google.android.gms:play-services-cast:16.1.2
 +---legacy-android:legacy:unspecified
     +---com.github.PierfrancescoSoffritti:AndroidYouTubePlayer:10.0.5
          +---com.github.PierfrancescoSoffritti.AndroidYouTubePlayer:chromecast-sender:10.0.5
               +---com.google.android.gms:play-services-cast-framework:16.1.2
                    +---com.google.android.gms:play-services-cast:16.1.2
 Issues found:

 Graphs to this dependency:
 +---com.github.PierfrancescoSoffritti:AndroidYouTubePlayer:10.0.5
     +---com.github.PierfrancescoSoffritti.AndroidYouTubePlayer:chromecast-sender:10.0.5
          +---com.google.android.gms:play-services-cast-framework:16.1.2
 +---legacy-android:legacy:unspecified
     +---com.github.PierfrancescoSoffritti:AndroidYouTubePlayer:10.0.5
          +---com.github.PierfrancescoSoffritti.AndroidYouTubePlayer:chromecast-sender:10.0.5
               +---com.google.android.gms:play-services-cast-framework:16.1.2


mvel throw FastList casting exception under high concurrency

more info here
http://stackoverflow.com/questions/40244528/mvel-throw-fastlist-casting-exception-under-high-concurrency

Stackoverflow link above was removed by moderator.
Reproduced frequently (but not everytime) with the following test:
  public void testInSetRepeated() throws InterruptedException {
    String str = "[\"001\", \"002\", \"003\", \"005\", \"007\", \"008\", \"009\"].contains(digest)";
    final Serializable stmt = MVEL.compileExpression(str);
    List<Thread> threads = new ArrayList<Thread>();
    final List<RuntimeException> rex = new ArrayList<RuntimeException>();
    for (int i = 0; i < 1000; ++i) {
      Thread thread = new Thread() {
        @Override
        public void run() {
          for (int i = 0; i < 1000; ++i) {
            try {
              Object result = MVEL.executeExpression(stmt, Collections.singletonMap("digest", "00" + (i%10)));
              assertTrue(result instanceof Boolean);
            }
            catch (RuntimeException ex) {
              rex.add(ex);
            }
          }
        }
      };
      threads.add(thread);
    }
    for (Thread thread : threads) {
      thread.start();
    }
    for (Thread thread : threads) {
      thread.join();
    }
    if (!rex.isEmpty()) {
      throw new IllegalStateException("Exception occurred " + rex.size() + " time(s)", rex.get(0));
    }
  }

Uploaded potential fix in PR https://github.com/mvel/mvel/pull/184


Secure user data

Addresses #3225, hopefully I groked the feedback from @blowdart  correctly
@Rick-Anderson @blowdart
not sure I'm doing this pull request right, seems to include changes I merged from master, hopefully that is ok, and I thought I should pull request to Rick's ra/secure-user-data2 branch which was the source, so it seems it will bring along changes from master into your branch. let me know if I should do this differently.
only changes actually made by me are from this commit in my fork
note that I changed the iisExpress launch settings to use ssl since the startup requires https and it didn't work without doing that.

@joeaudette,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

the normal user will be able to view all contacts, create contacts and edit/delete their own contacts.

Make a new PR
So we'll just leave it to the reader to implement a UI where registered users can apply to become normal users so they can edit their own data? That sound fine to me. We won't have to write that code but we'll want an easy want to grant normal status - and maybe even show how that's done. I was thinking an important part of this article is the title - secure user data.
Why not have anon users read data, registered user can create/edit their data and the admin can do anything? It's that how you'd write a site like this?  I think you'd actually need to put in a public/private flag
I think what you a Barry decided is probably the best way to go - we just need a mechanism to add people to the normal group and a better name than normal

I agree it would be a better demo experience if the registered user could do something after login.
I could make a button on the home page that is only shown to authenticated users that are not already in the role, a "Let Me In" or "Join" button if you will and I could wire it up to add the user to the ContactUsers role. But then is there a simple way to update the auth cookie with the new role since he is already logged in? I guess could log him out after adding the role and make him login again, but if there is an easy way to just update the cookie?
or  another option is to add a "Sign Up" checkbox on the registration page and if they check it go ahead and add the role at registration time?

What do we loose by adding all registered users to the ContactUsers role?
That makes the app easy to test/demo. That's how I originally wrote it.

add a "Sign Up" checkbox on the registration page

Would we then write: In a real app the "Sign Up" checkbox  would be an application to the ContactUsers role. In a real app an admin would need to approve new registered users having the the ContactUsers role.
I'm probably missing something because it seems easier to me to just all new registered users to create their own data.

I think the question I need to ask is what are we trying to show? If we're trying to show 3 different security roles, what's the best way to do that.

I agree, initially it was going to allow all authenticated users which made sense to me. I'm just trying to help but I need you guys to make the decisions about what it should do.

@blowdart  is it OK if registered user can CRUD their own data? That makes for a better demo, better testing, debugging. Or should registered users need to apply for CRUD status - which the admin will approve.
I had anon users only able to read about the site on the home controller and nothing on the contacts controller. We could allow anon users to read contact data.
I think we're close.

Sure.

I'm unclear on what the decision is.
Should authenticated users who are not in any role be able to create their own contacts or only read? If they can create contacts then we no longer need a ContactUsers role and no need to seed a second user.
Should anonymous users be able to read contact data?

@joeaudette  - what will make for the best sample?  One goal I have (and perhaps this is not important) is the ability to register new users and without too much work have them added to ContactUsers role.  Would adding users to the  ContactUsers role when they register work? If not, Perhaps you could add a field to the AspNetUsers to indicate they should be added to the ContactUsers role.  You could then open the ASP.NET Identity DB and check that box.
I'm thinking this app is like LinkedIn. Those in the  ContactUsers role can view everyones contacts but they can only CRUD their user data. Admins can do anything.
My first stab at this didn't allow anon users to read contact data. Anon users could only access the home controller and account controller (to register/log on).
What would make for the best sample app to get folks started on app that secures user data and has an admin role?

@joeaudette  with my first version, it was easy to:

Register a new user and add contacts
Switch to a different user and verify you could CRUD your data but only see others data

That seems important to me - to have multiple users in the ContactUsers role.
What's the best way to do that? Do you want to create 3 users? It seems to me it would be better to have a fairly simple (even it it's a manual process) of adding registered users to the ContactUsers role.

@Rick-Anderson I have an idea, what if we introduce a new operation that only admins and a second seeded user can do, something like Approve operation and ContactApprover role.
We would have to introduce a new status property on contacts with either Submitted, Approved, Rejected.
So the idea would be that authenticated users registered through the UI could create and edit their own contacts but they get a status of Submitted which they cannot change.
Then we have 2 seeded users and roles for admin and approver. Admin user can do anything. Approver cannot edit contacts that don't belong to him but he can approve or reject them. Approver since he meets the requirement authenticated user could also create and approve his own contacts as can admin. If we don't want that then we could still have a 3rd role ContactUsers which we add to newly registered users but seeded Approver would not have it so he could not create or edit.

maybe ContactApprover is not the right role name since it sounds like a permission or operation. Maybe "ContactQualityManager" instead for the role that could change the status of a contact.

@joeaudette  sounds perfect.  Keep it simple, Approver approves, even her own stuff.
@blowdart  is this OK with you. @blowdart  needs to above the final code/doc.

@Rick-Anderson I've implemented the changes as we discussed here:
https://github.com/joeaudette/Docs/tree/ra/secure-user-data2/aspnetcore/security/authorization/secure-data/samples/final15
I am ready to make a pull request if @blowdart approves what we discussed

@blowdart - Can you bless this step (Create a clean PR)? You'll have a chance to review the code/article before we publish.

@blowdart  can you do a quick review of Joe's changes you requested?

OMG THERE ARE REGIONS! HERESY!
But the rest looks fine :)

@blowdart  Thanks. #region is required to bring in code snippets.

I'm just going pull request it back into your branch @Rick-Anderson , it probably needs some more regions around code I added, before it gets meged to master :-D

closing this pull request to make a clean one


ArgumentError: tried to create Proc object without a block

Using jruby-<IP_ADDRESS> I get this error message immediately after issuing 'require "airrecord"' within irb.

What's the backtrace?

jruby-<IP_ADDRESS> :001 > require 'airrecord'
ArgumentError: tried to create Proc object without a block
from org/jruby/RubyKernel.java:1270:in lambda' 	from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord/query_string.rb:29:in module:Encodings'
from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord/query_string.rb:22:in <module:QueryString>' 	from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord/query_string.rb:9:in module:Airrecord'
from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord/query_string.rb:3:in <top>' 	from org/jruby/RubyKernel.java:937:in require'
from /Users/steve.hayes/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in require' 	from uri:classloader:/jruby/kernel/kernel.rb:1:in (root)'
from uri:classloader:/jruby/kernel/kernel.rb:13:in <top>' 	from org/jruby/RubyKernel.java:937:in require'
from /Users/steve.hayes/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in require' 	from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord/client.rb:2:in '
from org/jruby/RubyKernel.java:937:in require' 	from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord.rb:1:in (root)'
from /Users/steve.hayes/.rvm/gems/jruby-<IP_ADDRESS>/gems/airrecord-1.0.0/lib/airrecord.rb:5:in <eval>' 	from org/jruby/RubyKernel.java:976:in eval'
from /Users/steve.hayes/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in (root)' 	from /Users/steve.hayes/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:128:in require'
from (irb):1:in block in evaluate' 	from org/jruby/RubyKernel.java:1287:in loop'
from org/jruby/RubyKernel.java:1096:in catch' 	from org/jruby/RubyKernel.java:1096:in catch'
from /Users/steve.hayes/.rvm/rubies/jruby-<IP_ADDRESS>/bin/irb:13:in `'jruby-<IP_ADDRESS> :002 >

Not sure why that'd happen, looks legit to me. Feel free to dig.

Thanks for reporting this, @sxh. I can reproduce the error by running the test suite under jruby-<IP_ADDRESS>, which maps to CRuby 2.2. I cannot reproduce it under jruby-<IP_ADDRESS> (CRruby 2.3) or jruby-<IP_ADDRESS> (CRuby 2.5). If you can upgrade JRuby to 9.1 or 9.2, you should be all set.
@sirupsen do you want to commit to supporting Ruby 2.2, given that the Ruby core team no longer does? If so, I can make time to look into this further next week. Either way, I'd propose adding a required_ruby_version to the gemspec before we close this issue.

Thanks for the update. I confirm that the problem does not reproduce under jruby-<IP_ADDRESS>, and I've not upgraded to that.

I'm fine with required_ruby_version 👍

Thanks, everyone. This is patched in #49.


Sourcemaps incorrect line number for Chrome debugger

⚠ IMPORTANT ⚠ Please do not ignore this template. If you do, your issue will be closed immediately.

[ ] Read the docs.
[ ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[ ] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
Chrome's devtool debugger points to wrong locations in source files.
Reproduction
Create new vue-ts project with Vite.
yarn create @vitejs/app my-project --template vue-ts
Add a debugger in source code and run app in Chrome (yarn dev). See breakpoint trigger but pointing at wrong line/location.

In this image, should be pointing at line with debugger;
Repo with reproduction here: https://github.com/joker77877/vite-vue3-sourcemap-issue.git
Run yarn dev and view localhost:3000 in Chrome with devtools open.
System Info

vite version: 2.0.5
Operating System: macOS 10.15.6
Node version: 14.15.3
Package manager (npm/yarn/pnpm) and version: 1.22.10

This problem is caused by the vite-plugin-style-import plugin, so you can file an issue with vite-plugin-style-import.

Thank you for your answer.


validation webhook server do not need apps scheme

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
8bb715b159d9060f20b42c5a937796f749c28cb9
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes

I am thinking about how to patch webhook config for multi control planes


Chained cmds

This is a start to chained commands in overlay mode. Right now it supports a chained save and exit ("wq") and jumping lines(directly calling the #, e.g. "25").
Ref: https://github.com/gchp/iota/issues/122 https://github.com/gchp/iota/issues/123
Known bugs right now:

Non existent commands entered just freeze up the editor
If trying to jump to a non existent line, it will crash the editor

@gchp Looks like this commit broke something: https://github.com/gchp/iota/commit/def8d771e6aa7cd8ac0bb2db71c7fa826d636419

@mattscamp yep, I forgot to commit some stuff. Could you rebase this and see if it builds?

Sure, looks like it's failing for a new reason now. @gchp


Show information about features in v2025.1

issa is working on design
Some kind of visual explaining that drafts are now in the "Edit form" tab.
Possibly something about offline Entities.
Shown exactly once for each user.

Possibly something about offline Entities.

Now that we're bumping this issue to .1, am I right in thinking that we probably won't mention offline entities anymore? So it'll just be about the "Edit Form" page?


Issues with video playback of specific shows

Bug report
Recently I have been seeing video playack issues with Netflix on Kodi where the interlacing looks bad, and colors are missing/in the wrong place.
Your Environment

Netflix add-on version: 1.6.1
Operating system version/name: KODI 18.7
Device model: Raspberry Pi 4

Used Operating system:

[ ]  Android
[ ]  iOS
[ ]  Linux
[ ]  OSX
[X] Raspberry-Pi
[ ]  Windows

This is Avatar, as you can see the colors are missing/muted. I'd almost say its black and white, but its not.

Comparison of the same scene from Netflix on Chrome on Win 10.

And to prove its not all video, this is Umbrella Academy on the same Pi 4

I did some additional research and it seems it only affects shows that are in 4:3. Movies and 16:9 shows are all fine. For example, the Danger Mouse classic cartoon also has the issue.

the addon do not handle video playback you have to report to Kodi


ARTEMIS-2685 Not Block Netty Thread in any way for OpenWire

I remember OpenWire was using some Netty mechanism to disable AutoRead on a channel: this change still left this mechanism to work fine?

Nothing was changed on flowncontrol.


Certificate Error Cosmos DB in Visual Code

<Please be sure to remove any private information before submitting.>
Repro steps:
<Enter steps to reproduce issue>
Action: cosmosDB.createDocDBDatabase
Error type: DEPTH_ZERO_SELF_SIGNED_CERT
Error Message: self signed certificate
Version: 0.9.1
OS: win32

Sorry for the late reply. Could you try setting http.proxyStrictSSL to false?

Hey folks!
I can confirm that changing VSCode proxyStrictSSL setting to False make it work as a workaround.
However, I think there must be another way of working this out built in by the extension. I'm on OSX and I'm unfortunately, I have to run the emulator on a Windows VM with Parallels since after so many years with CosmosDB out, we still don't have xplat emulator.
To make the web data explorer to work, I had to export the certificate as suggested in the docs and made it trusted on OSX Keychain. That would allow us to access the WebUI.
Setting the global VSCode proxyStrictSLL is a pretty big security flaw and to proper fix it we should go one of the following paths:

Make the extension to trust any certificate that is either explicitly set at the extension level settings the thumbprint. That scope the relaxed SSL settings to the extension; or
Allow people to generate their own certificates and add it to the emulator, so it would use their trusted certificates instead of the auto-generated one; or
Make VSCode to selectively allow specific thumbprints at the VSCode global level.

That would avoid the security risk and allow scenarios like mine, where I have an "external" client (VSCode) connecting to a "remote" emulator on the VM.
I believe option 1 is the easiest to tackle, but 2 is the more reliable.
To be honest, in my case, all that would be sorted by having a cross platform emulator (long late feature request made multiple times everywhere, but subject for another issue)...
I hope that help...

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

I ran into this today and I'm hesitant to set
"http.proxyStrictSSL": false
Because I don't fully understand the security implications of doing so.
Jon
azsdke2e
azsdke2e1

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Is there an update to this? There needs to be a way to connect to the emulator via http or by ignoring the certificate on the other side. In a local development environment, it's unnecessary to enforce https when network is limited to localhost.

I am also affected by this problem. My use case is a dev container that is running my development environment and a CosmosDB emulator.
I attach the database via connection string and I get an error about the self-signed certificate.


Include Internal Dashboard FQDN/IP value in the LDAP certificate

Since Dex will connect to LDAP using this FQDN/IP, make sure that the
TLS handshake will succeed by regenerating the certificate early in
the orchestration, so it includes this FQDN/IP in the SAN extensions
of the LDAP certificate.
Fixes: bsc#1069175

 Bug 1069175 - Auth dialog when downloading kubectl errors out

How I validated the change:
Internal Dashboard FQDN/IP: <IP_ADDRESS>.nip.io
Without this patch, LDAP will contain an invalid certificate when dex tries to connect to it using TLS and the internal dashboard reference: <IP_ADDRESS>.nip.io:389, as the certificate will contain all ip addresses of the machine along with all detected hostnames in the machine (<IP_ADDRESS>.nip.io is not among them).
With this patch, I can properly go to Dex, and login, downloading the kubeconfig file.

I think this should go be backported to 2.0 and released with a maintenance update too.


ngtools/webpack Function expressions are not supported in decorators in 'NgModule'

Versions
npm 4.2.0
macOS Sierra
@angular/compiler-cli: ^5.2.1

Repro steps
To recreate, clone this repo and then do the following...
cd <repoDir>
git checkout functions
cd module
yarn install
cd ../app
yarn install
yarn run build:prod

Observed behavior
Upon compiling with the last statement I get ...
ERROR in ../module/src/utils/module.ts(5,2): Error during template compile of 'Utils'
  Function expressions are not supported in decorators in 'NgModule'
    'NgModule' contains the error at @angular/core/core.ts(194,31)
      Consider changing the function expression into an exported function.

But doing yarn run build:dev which does not use AoT compilation works fine. You can point your browser to /app/public/index.html to see the results.
Desired behavior
To be able to use AoT compilation with this setup.
Mention any other details that might be useful (optional)
Notice that the tsconfig.json file has a path set to look for code in the modules directory. Not entirely sure if it's due to that or not but I have multiple apps sharing code from a large base that I have not made into modules due to other issues.

Hello, errors like Error encountered resolving symbol values statically mean that there has been some problem in statically analyzing your app.
Angular CLI always runs some statical analysis, even on JIT mode, in order to discover lazy-loaded routes.
This may cause a lot of static analysis errors to surface when importing your project into the CLI, or upgrading for older versions where we didn't run this kind of analysis.
Below are good resources on how to to debug these errors:

https://angular.io/guide/metadata
https://gist.github.com/chuckjaz/65dcc2fd5f4f5463e492ed0cb93bca60
https://github.com/rangle/angular-2-aot-sandbox#aot-dos-and-donts

If your problem still persists, it might be a bug with the Angular Compiler itself.
In that case, please open an issue in https://github.com/angular/angular.

Did you even look at my repo? Did you assume I did absolutely no homework on this? I don't think the case I have is any of those outlined in any of the links above. Sorry, but I spent a great amount of time reducing my problem to a very simple repo for you to look at and I feel like I was completely dismissed out of hand.

And I Have the same error here, so...
Error during template compile of 'CountDownModule'
  Function expressions are not supported in decorators in 'NgModule'
    'NgModule' contains the error at @angular/core/core.ts(194,31)
      Consider changing the function expression into an exported function.

@crowmagnumb I have to admit I did not look at your repro, no. Static compilation errors are thrown by the Angular itself (@angular/compiler-cli) and Angular CLI has no control over them proper.
I didn't mean to sound dismissive but please understand that this sort of error is one of the most commonly mis-reported here in Angular CLI and that your issue description refers to a somewhat straightforward error message (Function expressions are not supported in decorators) described in the links I posted. From a triage perspective there wasn't much to lead me to believe this wasn't the case.
You seem quite sure that my assessment isn't correct and I thank you for calling it to my attention again. I'll reopen and label for further attention.

@crowmagnumb The problem 2 seems to be related to the fact that you have multiple instances of Angular (one used by the module and another one used by the app itself. ngc -p tsconfig.json error is gone after removing module/node_modules and moving app/node_modules to node_modules to ensure both components use same instance of Angular packages. But the whole build requires more adjustments to work.
Not sure what you are really doing, but just in case. Have you checked ready to use solutions for Angular mono repos instead of inventing your own wheel: Nrwl extensions, yarn workspaces or lerna-based setup?

Thank you @ filipesilva! I think you and @devoto13 may be right that it has to do with my home-grown sub-module setup which up until the very latest version of Angular, namely 5.2 (been doing it this way since Angular 1.3!), has worked just fine. But now I've run into this this problem as well that looks to also be related to this. My actual module is huge and I had a ton of problems getting it to work with ng-packagr a number of months ago. While I might attempt that again, yarn workspaces also looks like a great possible solution. I'll give those a go. Thank you!

Hi.. having this issue in this module... https://github.com/mariohmol/ang-jsoneditor
after updated to typescript 2.7? really lost! any help?


Running yum update nss worked for me.

Running yum update nss worked for me.

why，Prompt me to install successfully, but still invalid
centos7.2
node 8.11.3
puppeteer  1.14.0
please help
Originally posted by @chuans in https://github.com/GoogleChrome/puppeteer/issues/3080#issuecomment-503472035

There's been a lot of discussion on CentOS on the bugtracker:

https://github.com/GoogleChrome/puppeteer/issues/391
Chrome headless doesn't launch on UNIX

Please check out these topics; this looks like some kind of local env problem you're fighting.


Failed to Build The Project

Alluxio Version:
What version of Alluxio are you using?
2.7.0
Describe the bug
A clear and concise description of what the bug is.
When building the project,  the compiler shows the error that cannot find the symbol Class UfsConstants.
There is no UfsConstants Java file in this project.
To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Clone the whole project from GitHub and compile it in Intellij Idea 2021.3.2
Expected behavior
A clear and concise description of what you expected to happen.
Project can be compiled successfully
Urgency
Describe the impact and urgency of the bug.
Are you planning to fix it
Please indicate if you are already working on a PR.
Additional context
Add any other context about the problem here.

@dyiopd  have you tried running maven first out side Intellij.
It may require generating some constants first using certain maven plugins
here is the instruction https://docs.alluxio.io/os/user/stable/en/contributor/Building-Alluxio-From-Source.html
and let me know if this works for you

It works. Thanks a lot.


Science Analysis goals for 2017 SLAC Meeting

What do we hope to have ready by the SLAC Meeting and what can we finish up with only Run 1.1 data.
Edit this post to create a checklist below:

[ ] Issue 1
[ ] Issue 2

@drphilmarshall @rbiswas4 What do we hope to have running in the monitor by the SLAC Meeting?

I think my goals are more oriented towards the Twinkles analysis results -
the Monitor is our primary tool for that, but the results need to be based
on the SN error model, I think.
Goals:

I'd like to know, quantitatively, how closely the DM measurements and
error bars match their theoretical expectations

I'd like to see a (stub of a ?) recipe for simulating much larger mock
datasets using the Twinkles error model as input.

What do you think?
On Thu, Jan 19, 2017 at 3:32 PM, Bryce Kalmbach<EMAIL_ADDRESS>wrote:

@drphilmarshall https://github.com/drphilmarshall @rbiswas4
https://github.com/rbiswas4 What do we hope to have running in the
monitor by the SLAC Meeting?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/Monitor/issues/76#issuecomment-273932339,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArY9_PpKNB5KNNVD4F66H6lSgIMcWgkks5rT_KFgaJpZM4LovWs
.


Hoobs - Connect smart bridge not working?

When I click “Connect smart bridge” a text box comes up saying “please wait for the bridge to start” but nothing happens. Am I missing something?

Unfortunately, I don't use HOOBS and can't really provide support for it. If you figure out what's wrong, please respond to this thread w/ info, or submit a PR with an update to the README. :)


Curved labels part III

Disable curved layout for complex shaped scripts
use ICU for better text-transforms (i.e. support non-ascii chars)

@hjanetzek will start to review this when rebased.

One experiment that we could try on this would be to lower down breakage to words instead of label when the shaping is complex. It could show up more labels on those areas without breaking too much readability, I think.

I agree. Breaking on word boundaries will be good. Unless for some language that also breaks the context (I do not think so, based on the list here: http://r12a.github.io/scripts/featurelist)

Breaking on word boundaries seems to be quite a bit of work I would rather move to another PR.
One thing we could also try: Instead of completely disabling curved placement for complex scripts we could use a stricter limit for angle between segments.


formatter: Add RESPONSE_FLAGS_FULL substitution formatter

Additional Description: Adds RESPONSE_FLAGS equivalent which outputs PascalCase strings for readability purposes. Resolves #28572
Risk Level: Low
Testing: Unit tests
Docs Changes: Changelogs, access log
Release Notes: None
Platform Specific Features: None

/assign-from @envoyproxy/senior-maintainers

/assign-from @envoyproxy/senior-maintainers

/assign-from @envoyproxy/senior-maintainers

/retest

@ohadvano please leave it to the maintainers to assign PRs. Among other reasons, you got a 5 day delay because I was on vacation.

/retest

@ggreenway I adjusted per your comment, can you please take another look?

/retest


Possible Unhandled Promise Rejection (id: 0): "Failed to connect to play.google.com/2a00:1450:4026:804::200e:443"

Description
I have this error, so the app request the source. While request is pending my app is freezing.
What is that kind of request?
Version
0.65.2
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: Linux 5.8 Ubuntu 20.04.1 LTS (Focal Fossa)
CPU: (8) x64 AMD Ryzen 7 4700U with Radeon Graphics
Memory: 1.50 GB / 15.02 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.15.4 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.10 - /usr/local/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.10 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^17.0.2 => 17.0.2
react-native: ^0.65.2 => 0.65.2
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
I cant describe this. I need only information
Snack, code example, screenshot, or link to a repository
No response

I have same problem.((
How I can resolve it?

To resolve this problem, change maven repository url.

My problem was in npm dependency react-native-appstore-version-checker and no access to console of google play from Russia.


Fix typo

Emoji objects refer always to a custom guild emoji, not emoticons!
id, name & animated are always present, no matter in which context gateway/api sent emoji object.

This is not true, refer to discord api docs.

It is, discord docs are made nearly fully by community and it lacks a lot of info. Some of the topics are well documented and some other were not touched for like 3 years. Emoji object that discord gateway/api sends back always refer to a custom emoji. Characters like ✨ or 💸 are emoticons which are nothing else than a fancy text which is supported by like the most of the web (standard). Discord renders then a bit differently cause of using twitter emoji pack for that instead using system assets.

If you feel the docs are wrong, please PR the docs first. We go by what the docs say


Silent token refreshing

Hi guys,
This issue might be somehow related to :

https://github.com/solid/solid-auth-client/issues/127
https://github.com/solid/solid-auth-client/issues/109
https://github.com/solid/solid-auth-client/issues/37

Giving a short lifespan to the ID token is a security feature to reduce the vulnerability surface, but as @dmitrizagidulin said it is inversely proportional to user convenience.
We are currently experiencing this pain in our app. So far our only option is to increase the lifetime of the issued tokens, which is not the recommended way to go.
How about silent token refreshing ?
Brock Allen, the author of oidc-client-js seems to think it is acceptable in terms of security. I am having a hard time assessing if it is.
It is on the roadmap ?
If it isn't, how do we intend to make long sessions work with security.
Many thanks for your insight

Yes, this is indeed the plan; it’s just not implemented yet in the OIDC
library we currently use.

Just so I know which issues to subscribe to: is this the blocker? https://github.com/solid/oidc-rp/issues/4

@Vinnl - Ok, so, there's several moving parts here :)
Server-side:

Node-solid-server (which is currently using the solid/oidc-op library) does not have Refresh tokens implemented. Which is OK, because it's being replaced by:
Inrupt Pod Server DOES have Refresh tokens implemented.

Client-side:

solid-auth-client (this repo) uses the solid/oidc-rp library under the hood. Which does not currently have Refresh tokens implemented, and yes, https://github.com/solid/oidc-rp/issues/4 is the blocker/tracking ussue.
But! It is assumed that on the client side, solid/oidc-rp (and likely solid-auth-client itself) will be replaced (similar to how Inrupt Pod Server is using different libraries that are better maintained etc), with oidc-client-js or similar. So that, I suspect, is part of the reason why I don't think anyone is in a hurry to implement refresh tokens in solid/oidc-rp. Especially because:
Solid's authentication protocol, WebID-OIDC, is currently being refactored and standardized (in the authentication-panel). So that, I suspect, is also playing into the delay, since people want the protocol to settle down before coding more. :)

Does that make sense? So, yes, oidc-rp/4 is the blocker (if you're planning to use it with Pod Server), but I don't think resources have been allocated to it?

At least, that made things a lot clearer to me. Thank you @dmitrizagidulin

Thanks @dmitrizagidulin, that's very clear.
Short other question: is it theoretically already possible for solid-auth-client to know when the token has expired? Even if we're not able to refresh the token yet, it'd be great to at least be able to let the user know they're logged out, rather than things just suddenly no longer working.

@Vinnl:

is it theoretically already possible for solid-auth-client to know when the token has expired?

It would be, yeah.
You'd want to add some code probably around here in currentSession(), checking the session.idClaims.exp (expiration) claim, and throw an error if it's expired.

The other option would be to put the check for expiration in the fetchWithCredentials() function. Or both.

Hmm, so I've done some digging here, but it doesn't seem like this should need extra logic in currentSession(): solid-auth-client currently calls @solid/oidc-rp's validateResponse, which in turn checks whether the session is not actually expired.
Thus, it should return null for expired sessions (I have a unit test that verifies this). So the question to investigate should be: how come it appears that it does sometimes not return null on an expired session?

Not everything is implemented in the underlying OIDC library, and as @dmitrizagidulin wrote above, not likely to happen soon.

@Vinnl

how come it appears that it does sometimes not return null on an expired session?

I haven't looked closely, but I suspect it has to do with the difference in lifetime between the inner ID Token (really, just a signed credential) and the outer PoP token. Both have different expiration times that the auth client has to consider, and the oidc-rp lib mostly focuses on the ID Token's expiration, and not the interaction between the two.
So, yeah, it shouldn't be too hard of a lift to fix, I agree.


sphere-collider should not use geometry.computeBoundingSphere

use new Box3().setFromObject(o) instead

Want me to wrap this into #155 ? I have a feeling it will impact the radius scaling.

Thanks if you can that would be great! Sorry that I haven't been able to look at your PR yet, I should this weekend.


TEG can function as an infinite power source

Description

It stays at the value it was generating before being destroyed.
Reproduction

Get hit by a meteor
Lizard round #59181

Screenshots

Additional context

I was able to replicate the issue like this:

first you need to power the TEG, so pick any 2 canisters
use viewvaribles to massively increase the temp inside one canister
now fill both loops and run the TEG
delete one of the circulators to simulate it being hit by a meteor
TEG's PowerSupplierComponent is now stuck in the last value it had

I digged some more and found that inside TegSystem:
the code that updates power is inside GeneratorUpdate
 private void GeneratorUpdate(EntityUid uid, TegGeneratorComponent component, ref AtmosDeviceUpdateEvent args)
    {
        var tegGroup = GetNodeGroup(uid);
        if (tegGroup is not { IsFullyBuilt: true })
            return;

        var supplier = Comp<PowerSupplierComponent>(uid);
        var powerReceiver = Comp<ApcPowerReceiverComponent>(uid);
        if (!powerReceiver.Powered)
        {
            supplier.MaxSupply = 0;
            return;
        }

a bugged half built TEG will hit the first return (as it should on most cases) but then because of it never reaches the second check to update power
replacing the order of the checks seems to fix things on my end


Add zenodo badge to README.md

This PR will add a zenodo badge to README.md.
This badge is displaying the DOI to cite the latest version of elephant.

Coverage remained the same at 88.689% when pulling c408590a02383a5e70490d2fb166530628aa2387 on INM-6:feature/zenodo_doi into 784fb8d2acbfc7cf6d27eb324cbfd63c58d2861b on NeuralEnsemble:master.


Add dio to Craft config

#skip-changelog

Codecov Report

Merging #791 (704ebc7) into main (66bd83d) will increase coverage by 6.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #791      +/-   ##
==========================================
+ Coverage   89.41%   95.65%   +6.24%
==========================================
  Files         110        2     -108
  Lines        3513       46    -3467
==========================================
- Hits         3141       44    -3097
+ Misses        372        2     -370

Impacted Files
Coverage Δ

dart/lib/src/sentry_tracer_finish_status.dart

flutter/lib/src/flutter_sentry_attachment.dart

dart/lib/src/protocol/dsn.dart

...nt_processor/native_app_start_event_processor.dart

dart/lib/src/sentry_measurement.dart

dart/lib/src/protocol/sentry_culture.dart

dio/lib/src/sentry_transformer.dart

dart/lib/src/protocol/sentry_thread.dart

flutter/lib/src/sentry_flutter.dart

.../lib/src/enricher/io_enricher_event_processor.dart

... and 98 more

Continue to review full report at Codecov.

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

release registry was merged


optimize the heartbeat-related logi

Enhancement
Under high pressure, backend is down or not will occur, but FE/BE does not hang. It is necessary to optimize the heartbeat-related logic and improve the priority of the heartbeat thread.

Under high pressure, backend is down or not will occur, but FE/BE does not hang.

I can't catch you about this description.


Remove last line as this part will be appended from tool

Purpose

Remove last line as this part will be appended from tool
https://github.com/ballerina-platform/ballerina-distribution/blob/a5b815534587f7fad65b36feedb72878c3b49500/ballerina-update-tool/src/main/resources/cli-help/ballerina-help.help#L9

Codecov Report

Merging #20037 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #20037   +/-   ##
=======================================
  Coverage    19.9%    19.9%
=======================================
  Files          55       55
  Lines        1437     1437
  Branches      218      218
=======================================
  Hits          286      286
  Misses       1138     1138
  Partials       13       13

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 72b524d...988d5e1. Read the comment docs.


ShaMap ??

Let's start a discussion around this. Mind posting something over in https://github.com/XRPLF/xrpl4j/discussions ?

I was just surprised there was none there!
I guess there's no use for it (yet) ?

The ShaMap is the data structure that the XRPL stores its data in. The data is exposed to clients via an API (RPC, WS), but is only useful if you're storing the entire ledger and want to be a validator on the network. xrpl4j is simply a client library that supports interacting with the XRPL and doesn't aim to be a tool that could be used to build an XRPL node, so I don't think we will ever add a ShaMap to this library.
I'm going to close this issue, but feel free to open it up again or start a Discussion if you feel having a ShaMap in this library would be useful.


32-bit Audio Decoding

Electron Version: 0.35.0+ (All Electron versions seem to be affected as this is an underlying Chromium bug)
Chromium Trackers:

Chromium Issue
Chromium Resolution

This issue occurs when you are attempting to decode an audio file that has a 32-bit sample rate in an electron app. As the issue logged in Chromium points out this could be tested using http://wavesurfer-js.org/ with the files listed in the project (github doesn't support wav file upload, sorry).

This issue is resolved with commit ad33ab7a20ddede811d0562c45a267a1b06c1ed6 and I noticed #3610 requests a chromium update schedule. I don't know if jumping to v49 would be in the cards but while the team works towards a stable v49 release is there a way I could either build electron with the canary chrome build, or assist in getting the necessary components in place to support v49?

@bleib1dj Jumping to Chromium v49 is going to be very difficult, you might have to wait, or handle audio decoding in your own node.js native module (or even in JS via compiling an Emscripten module) and convert it to a format that Chromium v45 can grok

Alright cool, thanks for the heads up @paulcbetts.

For new features that available in test channels of Chrome, you have to wait until it becomes a stable release and later Electron updates to it. Updating the Chrome version in Electron requires a lot of work, so we only do it for stable releases.


Azure CLI - RHEL install, Yum repos is not accessible, generating 404

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=dnf
The Yum repos is not accessible, generating 404.

@krishnaprabhat Thanks for bringing this to our attention. Do you still see this happening?
I'm able to access https://packages.microsoft.com/yumrepos/azure-cli without any issues:

Please check and let me know.

I am able to access it now. Do we have any RCA for this issue.

@krishnaprabhat AFAIK, there wasn't a known incident for the noticed behavior on our side. That said, if you run into this issue again, please file an issue with Azure/azure-cli repository so our Engineering Team can take a look.
Also, on a side note, I'd like to let you know that this channel (the Azure CLI Docs repository) is only for driving improvements related to the Azure CLI documentation. At this point, it appears that there are no edits or updates needed to the document in question. Hence closing this issue for now. If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


fixed some clippy warnings

I think this should hopefully alleviate your concerns. Thank you for the link to the commit message blog, it will improve my further commit messages considerably. :+1:


Npm audit fix

Codecov Report

Merging #1967 (3d2e1c8) into master (4df92cb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1967   +/-   ##
=======================================
  Coverage   62.71%   62.71%
=======================================
  Files          92       92
  Lines        4656     4656
  Branches      318      318
=======================================
  Hits         2920     2920
  Misses       1702     1702
  Partials       34       34

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 4df92cb...3d2e1c8. Read the comment docs.


postMessage not working in 3.0.8

Issue description:
Just updated to 3.0.8 and found out postMessage was not working. I've used postMessage on some color fields. Getting the error below in the console, but not sure it was related or not.

Version used:
3.0.8
Using theme_mods or options?
options
Code to reproduce the issue (config + field(s))
Kirki::add_field( 'theme', array(
  'type'     => 'color',
  'settings' => 'color_site_bg',
  'section'  => 'color_general',
  'default'  => '#fff',
  'output'   => array(
    array(
      'element' => 'body',
      'property' => 'background-color',
    ),
  ),
  'transport' => 'postMessage',
  'js_vars' => array(
    array(
      'element' => 'body',
      'function' => 'css',
      'property' => 'background-color',
    ),
  ),
) );

Found the issue. Some js_vars were written like below for better readability.
'js_vars' => array(
    array(
      'element' => '
          .class-1,
          .class-2,
          .class3
      ',
      'function' => 'css',
      'property' => 'background-color',
    ),
),

Just updated them like below and no issue at all. Also the error in the console was related with the issue.
'js_vars' => array(
    array(
      'element' => ' .class-1, .class-2, .class3',
      'function' => 'css',
      'property' => 'background-color',
    ),
),


Assertion Error after adding static object and recompute navmesh from Viewer.py

So I'm leveraging this tutorial for adding object "Clutter Generation Script" and the viewer.py example. I basically followed what's in the tutorial for adding object and then try to use the navmesh_config_and_recompute() provided in viewer.py so the object can become obstacles in the navmesh but it's keep failing on an  assertion error

Does anyone have any insights on what this function does? or where the error may come from?
After adding the object and setting self.navmesh_settings.include_static_objects = True, when I call the sim.recompute_navmesh, this error shows up.. Thanks!

@EvaLiiiiii so strange. :thinking:
My guess would be some edge case related to the object asset mesh import. That assertion happens when the ResourceManager::getMeshMetaData function cannot find a meshMetaData entry for the object. Mesh data is queried to join all meshes in the scene before constructing the navmesh.
If you can provide the object asset I could test it locally and attempt to debug.
If not, you could try passing the mesh asset through a converter to another format. That may clean-up issues or bypass any importer bug. Habitat importers prefer glTF.
Also, what version are you on? I see a conda build here, so it could be that if you are not on nightly the bug is stale and resolved elsewhere upstream.

Hi @aclegg3 , Thanks for quick response! I'm working on the "stable" branch. I'm testing with sphere object in Adrian.glb from Gibson.

This is what I did. I've also changed "sample_object_state" function to be sampling near a point instead of complete random sample. The spheres seem to appear correctly. But when I press shift+ n to recompute the navmesh I get that error..

Hi @aclegg3  I think the problem is with the sphere object. After I changed it to the donut it worked!

Yeah, must be an asset issue with the sphere. Glad you have a workaround and thanks for the report.
When we get some bandwidth we can dig into why this is crashing.


Create card-elements

A base compendium-card, then a insight-card and section-header-card that subclass it

All remaining issues captured in other sisues


NaiveBayes factory support

Coverage increased (+0.005%) to 99.42% when pulling e4626a4c6cde6b14c11fab95e139f9fb01f4a611 on ronna-s:naive-bayes-factory into b55b8dc80ea34a90f76c25d2bd54296bf283e475 on asafschers:master.

Already pushed the same fix


[tests][objc] Improve Makefile dependencies to only rebuild things if needed.

Build and tests passed.


Tree: Add Node wrapperClass

为Tree组件每个节点增加wrapperClass属性，可以控制包裹子元素的样式
Please make sure these boxes are checked before submitting your PR, thank you!

[*] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[*] Make sure you are merging your commits to dev branch.
[*] Add some descriptions and refer relative issues for you PR.

Sorry, we have no plan to support this.


Feature request: Pass tunnel token to cloudflared using secret

Right now tunnel token is used as part of command array, which makes it easy readable. Instead it's recommended to pass this kind of data via secret to env var, something like this:
...
containers:
- command:
  ...
  - --token
  - $(TOKEN)
  env:
  - name: TOKEN
    valueFrom:
      secretKeyRef:
        name: controlled-cloudflared
        key: tunnel-token
...

or just set $TUNNEL_TOKEN env var and don't set --token cli arg (https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#token)
Of cource this would require controller to manage secret with tunnel token.


TOF-FBP reconstruction

Continuation of #130
Adds TOF-FBP, attenuation correction, remapping to single layer, sparse matrix implementation, ability to save calculated sinogram.

Tests are not passing because of not existing j-pet-mlem, I will update this PR after accepting PR #144

retest this please

retest this please

Could you add a small description what getSplitRangeNumber() does in CreatorTools.


Include day of mourning for former president H.W. Bush in US holiday data

See also issue #2730.
Expected Behavior

2018-12-05 should exist as a non-tradeable date in the US holiday data.
Actual Behavior

2018-12-05 is missing from the US holiday data.
Potential Solution

Add in the date (2018-12-05) for former president H.W. Bush in the static class USHoliday in Common/Global.cs (I have a pending change).
Reproducing the Problem

System Information

Checklist

[ ] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[ ] I have provided detailed steps to reproduce the issue

FYI, I'm not sure that this issue is still valid given the discussion on pull request #3921 .
@Jay-Jay-D wrote:

2018-12-05 should not be present in the USHoliday.Dates HashSet

... after which I withdrew my pull request and wrote:

Should the other ad hoc / specific dates (e.g. for 9/11 (i.e. the World Trade Center attacks), Hurricane Sandy, and the other 2 days of mourning for former presidents) also be removed from the USHoliday.Dates HashSet?

Thanks @RohanTalip