Custom Pin Payments changes to activemerchant as of 20210120

Just for comparison not a real PR.

LGTM :camel:

LGTM :camel:

🚀


feat: fix tests accordingly to new contract schema #NTRN-326

Task: https://hadronlabs.atlassian.net/browse/NTRN-326
Related PRs:
https://github.com/neutron-org/neutron-sdk/pull/156
https://github.com/neutron-org/neutron-dev-contracts/pull/59
https://github.com/neutron-org/neutronjsplus/pull/49
List of changes:

Fixed tests for dex_stargate and stargate_querier contracts.
Renamed dex_stargate.test.ts and stargate_queries.test.ts to dex_grpc.test.ts and grpc_queries.test.ts respectively.

Test run: https://github.com/neutron-org/neutron-tests/actions/runs/10176822282

Test run: https://github.com/neutron-org/neutron-tests/actions/runs/10355673672


copy to clipboard doesn't work on mobile

This feature is available only in secure contexts (HTTPS).
https://developer.mozilla.org/en-US/docs/Web/API/Clipboard


Add scrollable year dropdown option

Please review the code, comment and merge it as soon as possible.

Is there any reason why this is not merged other than failing css lint? I am needing this for a datepicker for birthdates, and clicking the arrow is to slow..

I created a new PR with the updated code. See #577


It (sh|c)ould not include a command bus impl

Some command bus impl exist already (like https://github.com/SimpleBus).
I guess it would be better to keep things separated since event sourcing has nothing to do with the command pattern.

In the end, we want to provide the users with a full stack framework. My communication on event sourcing is a bit confusing, I have to blame the 140 chars available in twitter... It is left to the appreciation of everyone to work with the shipped command buses, or to create a little adapter for existing ones.
I think it is important to have some default, simple implementations out of the box, that illustrate a good integration in the whole picture.
That said, I keep in mind your remark, and I might wanna decouple things a bit, but I first wanna make sure, the implementations are a bit more stable.
First thing first, I am gonna re-write my tests in PhpUnit because I wanna use assertions, limit mocks, and limit factories, and this will benefit the community, phpunit being far more used.
Then I am going to add some features like: OptimisticLocking/ConflictResolving, which are really necessary for production.
Then I we will figure out how we re-dispatch every single part of the lib. We even might left outside the command bus as suggested if that feels right at that time.
Does that sound good?


Finish up Event Page

"> a gallery of previous events would be nice to see (idk if it would help its just my opinion) " ~Tom
Event page should be finished. Probably something along the lines of a page with a few previous events and quite some pictures per event.

Event page got taken out for now to focus on the release

Duplicate of #46


Test CIM Motors

They work!

Will do some load testing and see if they are up to spec

Pushing this task back a milestone because of the lower priority that they entail given that they are back up motors

Pushing back again for the same reason as before, will pursue after tele-op is perfectly done

not necessary


Trigger events from child vue component

Hi.
I would like to be able to trigger events from children components of a given parent. Check this code out:
Parent Component (Only template):

    <child class="child-component"
      @custom-event="console.log.call(null, 'Custom Event from Child Component')"
      @click="console.log.call(null, 'Click Event from Child Component')">
    </child>

Test:
test('Testing triggers', () => {
    const wrapper = mount(Parent) // Parent Vue Component

    const childComponent = wrapper.find('.child-component') // Child Vue Component
    const childDiv = wrapper.find('.child-div') // Child Native DOM Element

    childComponent.trigger('custom-event')
    childDiv.trigger('custom-event')

    childComponent.trigger('click')
    childDiv.trigger('click')
})

The log generated in console is the following:
Custom Event from Native DOM Element
Click Event from Native DOM Element

As you can see, events triggered in Vue Components are not being emitted, so the parent can't catch them and act in consequence.
Is this expected? Maybe I'm doing something wrong ?
Thanks !

This will not work, when you do mount it will not stub the child component, but render it's actual contents, I think. Can you post child-component?
What you probably want to do is instead of find('.child-component').trigger('custom-event'), do trigger on the actual button in the child component (maybe give it an ID or something). So:
// child component
<template>
  <button id="child" @click="$emit('custom-event')">Btn</button>
</template>

// parent
<template>
  <child-component @custom-event="something" />
</template>

// Test
const wrapper = mount(Parent)
wrapper.find('#child').trigger('click')
// this should work (or something like this)

If you post child-component, or better yet your repo, I can add some examples of how to do this (I have done it a lot in my projects, and had the same problem, but haven't got any snippet I can share at this very moment).
Will try and put a small demo repo together later today, since I remember stuggling a little to test parent/child events.

Mmmh I think I Understand...
My problem is that I'm trying to do TDD and what I was attempting to do is create a Parent component that needs to react to events emitted from a yet undefined Child Component.
I wanted to define the behaviour of the Parent before the Child.
Maybe I'm not following a good strategy to do TDD as I'm used to from PHP.
Maybe if I shallow the Parent component, the Child will be stubbed and the events will be triggered?
Thanks for your help!

I understand what you want now. Here, I made an example for you. Make sure you look at the branch 'testing', not 'master'. You can see how to trigger a custom event.
You can do it like this: https://github.com/lmiller1990/vue-test-utils-async/tree/testing

It looks like you are just testing if $emit works in that case. You should be testing your own code logic, not Vue itself.
Can you post the full code of what you are trying to test? There is no point to test if a component can react to a custom event, Vue already has internal tests for that.
Check out #145  , i think it's related.

No @lmiller1990, I don't want to test if $emit works. I want to test that my ParentComponent is able to react for events emitted for a undefined ChildComponent.
The code I put before is the full code. I mean, I don't have a real ChildComponent yet. It just something that I know I would like to wrap in its own component because it has too much logic but I would like to define in the ParentComponent.spec.js the event or api that ChildComponent would expose.
Let's try again with this snippet:
ParentComponent.vue
<template>

    <child class="child-component" @custom="onCustom"></child>

Triggered!

</template>

ParentComponent.spec.js
describe('ParentComponent', () => {
  test("It shows 'Triggered' when Child component allows to...", () => {
    const wrapper = mount(ParentComponent) // Maybe shallow ?

    const childComponent = wrapper.find('.child-component')
    childComponent.trigger('custom')

    expect(wrapper.html()).toContain('Triggered!')
  })
})

Note: I'm trying to test the output, not the implementation details. That's why I don't want to test wrapper.emitted() or wrapper.vm.customEmitted
Of course, I could be wrong in how to do TDD in Vue Components. Maybe ParentComponent is not responsible for making assumptions about events emitted for ChildComponent. I'm just trying to figure it out and wrap my mind around testing parent-child communication.
I hope this is clearer than before.
Thanks!

Thanks for the more detailed explanation, @Aferz .
Since you haven't defined child yet, you could make a temporary element to test with. Something like Mock.vue that contains:
<template>
  <button @click="$emit('custom')"><button>
</template>

And test with this.  Then you can do an $emit on the Mock.vue component, and test like that. Basically, the same as stubbing/mocking the component out.
However, even if you do that, you are still just testing Vue. If a child component exposes an event api like you said, where custom is emitted, you would still just be testing if ParentComponent calls a method when custom is emitted - of course it does, that is what Vue's API provides.
I think what you are trying to do at the moment is:

"when custom event is emitted from a childcomponent (which doesn't exist yet)
on onCustom is called in the parent
customEmitted becomes true
"Triggered" is rendered

What you should be doing is just the last two points, which is the logic you wrote. You can be confident if a child emits an event, the parent will respond.
So should your unit test should look like this:
describe('ParentComponent', () => {
  test("It shows 'Triggered' when customEmitted is true", () => {
    const wrapper = shallow(ParentComponent)

    wrapper.setData({ customEmitted: true })

    expect(wrapper.html()).toContain('Triggered!')
  })

  // or
 test("It shows 'Triggered' when onCustom is called", () => {
    const wrapper = shallow(ParentComponent)

    wrapper.vm.onCustom()

    wrapper.vm.update() // need to call to update UI

    expect(wrapper.html()).toContain('Triggered!')
  })
})

Of course, eventually in your app you will have to test that when something (say a button) is clicked, something else in a parent component happens - this is an integration or e2e test though, since it involves multiple components interacting, which is out of the scope of vue-test-utils.
PS: your last sentence said: "I'm just trying to figure it out and wrap my mind around testing parent-child communication.". You definitely don't need to test that, but of course Vue internally does have tests for this functionality, if you are really keen you can take a look at the Vue source.
Hopefully that helps. Let me know if something isn't clear or you have more questions, we are all still learning :)

@lmiller1990:

Thank you very much for your so good explanation.
You cleared my mind a bit more about this topic.
Thanks!

This topic/question is indeed very much related to #145 which I asked last week. I was also wrapping my mind around unit tests and got stuck in stuff that is already in Vue and should not be tested.
Thanks to @lmiller1990 for pointing this out and for the clarification/explanation!
And thanks to @Aferz for sharing WW's quote :-)

Sorry for coming late to the party. I get that there's no need to test that the event from the child is received by the parent but what I would like to test is not that the parent calls a method, but that it calls the correct method. Maybe I have two child components and the parent is supposed to call different methods depending on which child fires the event. That should be part of a unit test, I think, because it's logic that is inherent to the parent component.

Sorry to bring up an old issue, but I agree with @Aferz. I don't think my unit tests should be aware of potentially private functions. E.g. both of these should pass the same unit test:
<child @foo="gotFoo = true" />

// Or

<child @foo="setFoo" />

{ methods: {
  foo() {
    this.gotFoo = true;
  }
}}

Also the same applies to setValue. IMO both of these should be treated the same, but you have to unit test them differently:
<input v-model="foo" />

<my-custom-component v-model="foo" />

Although I understand the explanation of @lmiller1990, I agree with @felixlublasser and @samboylett.
When an event is emitted by a child component, I think calling the "right code" (event handler method, code in template...)  is also part of the parent component's logic.
In the example above:
<template>

    <child class="child-component" @custom="onCustom"></child>

Triggered!

</template>

This test:
  test("It shows 'Triggered' when customEmitted is true", () => {
    const wrapper = shallow(ParentComponent)

    wrapper.setData({ customEmitted: true })

    expect(wrapper.html()).toContain('Triggered!')
  })

doesn't mean I want to test if the v-if directive works well, but if the component's logic/output is correct. So I think it's the same reasoning with events.
Moreover since we can trigger DOM events, we have to write 2 kind of tests to test the same thing (emitted event => expected output).

You can emit from a child component by accessing the instance:
test("triggers correctly", () => {
  const wrapper = shallow(ParentComponent)
  wrapper.find(Child).vm.$emit('custom')
  expect(wrapper.html()).toContain('Triggered!')
})

@eddyerburgh Thanks for the tip!
Is it mention somewhere in the documentation? I think it may be useful.
Then I agree adding a method isn't necessary 😄

I may not have time this week, but I think I can make a PR next week.


SIGABRT: Failed to compile clap v2.34.0

Cloning the example and compiling on macOS Monterey 12.0.1 with the esp toolchain fails when building clap v2.34.0:
error: could not compile `clap`

Caused by:
  process didn't exit successfully: `rustc --crate-name clap --edition=2018 /Users/thorcorreia/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.34.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C split-debuginfo=unpacked -C debuginfo=2 --cfg 'feature="ansi_term"' --cfg 'feature="atty"' --cfg 'feature="color"' --cfg 'feature="default"' --cfg 'feature="strsim"' --cfg 'feature="suggestions"' --cfg 'feature="vec_map"' -C metadata=ac26a8e48a625ff4 -C extra-filename=-ac26a8e48a625ff4 --out-dir /Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps -L dependency=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps --extern ansi_term=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libansi_term-7bb5c8085badc50a.rmeta --extern atty=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libatty-02f4983f38003a7d.rmeta --extern bitflags=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libbitflags-45b4e505e2497911.rmeta --extern strsim=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libstrsim-2b74c9109d8bb938.rmeta --extern textwrap=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libtextwrap-9684b827efe0b904.rmeta --extern unicode_width=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libunicode_width-d208e9921c947bc5.rmeta --extern vec_map=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libvec_map-63037abaf65b04ec.rmeta --cap-lints allow` (signal: 6, SIGABRT: process abort signal)

It appears that the esp toolchain is unable to compile clap for some reason.
I also mirrored the issue here.

This is known limitation of toolchain on Monterey. Build 1.57 is running, it should resolve the issue.

@thorlucas The issue is still present in <IP_ADDRESS>.
Recommended workaround: use Podman/Docker image https://hub.docker.com/r/espressif/idf-rust on Monterey
Any hint what could be the root-cause is appreciated.

@thorlucas The issue is still present in <IP_ADDRESS>. Recommended workaround: use Podman/Docker image https://hub.docker.com/r/espressif/idf-rust on Monterey
Any hint what could be the root-cause is appreciated.

That's going to be a little bit difficult -- I tried running gdb on the rustc command but I'm having codesigning problems. I usually switch to linux when debugging but in this case the problem is macOS specific…
As posted in the other thread, the rustc pannic message is:
rustc(41908,0x7000083ca000) malloc: *** error for object 0x600002596000: pointer being realloc'd was not allocated

So we have some memory issues.

use Podman/Docker image

Sorry, eps-build says you cannot flash from docker. Any hint onto how I would go about using it? Thanks

It's possible to flash from Podman which supports mapping of serial devices. Other option would be to use docker cp, to get file out of container to main host and flash it from there.
Meanwhile:
We found the reason of SIGABRT. The build of Rust for macOS x86_64 must contain option --set rust.jemalloc.
The new build is ready. Please test following script https://github.com/esp-rs/rust-build/tree/build/1.57:
./test-rust-toolchain.sh -t <IP_ADDRESS> --installation-mode reinstall
This will deploy toolchain with name esp-<IP_ADDRESS>. You can call your builds with cargo +esp-<IP_ADDRESS> .

Hi, can you please provide this build for macOS aarch64 apple ?

@georgik Excellent, thanks! I managed to get it flashing by simply building using a shared volume in docker and flashing the target/ outside of docker. I will test the new builder momentarily

@georgik New build works great! Thanks


Body Encoding

Support custom body encoding instead default utf8

Some quick remarks:
Can you please only use var for complex types ? I like to keep string, bool and byte[] for readability.
And is it usefull to expose BodyEncoding also in the admin interface?


NEWSLETTER

I'm putting this here since we don't have a mailing list / google group etc yet, and nobody seems to use our gitter (me included).

After more than 3 years, the branch "develop_0.9.3" got finally merged into master a few weeks ago.
Next on the list is dropping python2 support (https://github.com/lneuhaus/pyrpl/pull/355) - please let me know if this is a problem for you.
After that, I plan to drop the IIR filter from the master branch. I won't delete the code, just deactivate the IIR filter from the default branch, since it uses so many resources that it is not compatible with other features I've implemented in the meantime (which would make their way into the master branch). There could always be a feature branch with IIR filter support, just not the master branch. Again, please let me know if this is a problem for you.
After that I plan a major refactor, using https://github.com/pypga/pypga as the basis for the FPGA design. Have a look at the new PyPGA library and see for yourself. My hope is that this will facilitate maintaining multiple FPGA designs in a single repository, e.g. one with and one without IIR filter. This change will also allow to deploy PyRPL easily on other boards, e.g. the STEMLab250-12. If you're willing to contribute to this migration, your help is welcome!
Sorry for partially outdated documentation - I know this is horrible but I have too many other duties.

and here is a google group - not sure we will use it but I will give it a chance https://groups.google.com/g/pyrpl

and here is a google group - not sure we will use it but I will give it a chance https://groups.google.com/g/pyrpl


CI: Conformance EKS (ci-eks) - Installation and Connectivity (Unexpected AWS leftover iptables chains)

CI failure
Hit on https://github.com/cilium/cilium/pull/29643 in Installation and Connectivity Test (1.28, eu-north-1, true)
Checking pod/cilium-cncmz
Unexpected AWS leftover iptables chains
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
:AWS-CONNMARK-CHAIN-0 - [0:0]
:AWS-CONNMARK-CHAIN-1 - [0:0]
:AWS-SNAT-CHAIN-0 - [0:0]
:AWS-SNAT-CHAIN-1 - [0:0]
Error: Process completed with exit code 1.

Sysdump:  cilium-sysdumps.zip

Hit again on https://github.com/cilium/cilium/pull/29643
workflow run #2: https://github.com/cilium/cilium/actions/runs/7185434672/attempts/2
This looks like a new step added to the test merged 2 days ago: https://github.com/cilium/cilium/commit/510739146996e3fc0c2aeaba34c33fb5ade31a99

Couple other failures in recent job history:
https://github.com/cilium/cilium/actions/runs/7183170477
https://github.com/cilium/cilium/actions/runs/7175791131/job/19539686906
https://github.com/cilium/cilium/actions/runs/7172636353
https://github.com/cilium/cilium/actions/runs/7173031426

ah I needed a rebase to pick up a new change being tested :sweat_smile:


How do make client wait before the server is connectable?

as title, and also, how to implement reconnection?

Channel handles the backoff and reconnects automatically, you can see the explanation here.

Closing this. If you have further questions, feel free to reopen it or create a new issue.

do you have a sample using grpc-rs to wait until the server is connectable?


Pro Version: andForget isn't working

Trying to do:
$this->close(
    andForget: [
        ShowEvent::class,
    ],
    andDispatch: [
        'refreshCalendar',
    ],
);

The child modal closes and the dispatch works, but the parent modal (ShowEvent) doesn't close. Am I doing something wrong?

For now I did:
$this->close(
      withForce: true,
      andDispatch: [
          'refreshCalendar',
      ],
  );

and that's working, but I wanted to use the andForget :/
Let me know :)

AndForget should work. Feel free to provide a demo repository that has the problem so I can investigate :)


"IndexError: list index out of range" for flexible docking with beta-cyclodextrin

I prepared a PDB file with a structure of beta-cyclodextrin (BCD.pdb), based on crystallographic data.  Beta-cyclodextrin is a cyclic macromolecule, consisting of seven linked glucose residues. I would like to dock a drug molecule inside its cavity. However, the configuration of a cyclodextrin (receptor) may change a bit depending on the dcoked ligand, therefore I tried to calculate how the structures of the complexes would change when the flexibility of the molecule is allowed. Therefore I invoked:
  prepare_receptor -r BCD.pdb -o BCD.pdbqt
  pythonsh ~/AutoDock-Vina/example/autodock_scripts/prepare_flexreceptor.py -r BCD.pdbqt -s GLC1

The first command resulted in a correct creation of a file (BCD.pdbqt), but the second returned an error:
Traceback (most recent call last):
File "/home/dboczar/AutoDock-Vina/example/autodock_scripts/prepare_flexreceptor.py", line 220, in
non_rotatable_bonds=all_bnds, mode = mode)
File "/home/dboczar/ADFRsuite-1.0/CCSBpckgs/AutoDockTools/MoleculePreparation.py", line 2674, in init
flex_residues = self.flex_residues = self.process_residues(residues)
File "/home/dboczar/ADFRsuite-1.0/CCSBpckgs/AutoDockTools/MoleculePreparation.py", line 3080, in process_residues
ntors = self.setAutoFlexFields(res)
File "/home/dboczar/ADFRsuite-1.0/CCSBpckgs/AutoDockTools/MoleculePreparation.py", line 3134, in setAutoFlexFields
res.root = ca_atom[0]
File "/home/dboczar/ADFRsuite-1.0/lib/python2.7/UserList.py", line 31, in getitem
def getitem(self, i): return self.data[i]
IndexError: list index out of range
What is the reason of this error and what can I do to solve the problem?
I attach two files mentioned above.
BCD.zip

See #204 for how to handle flexible sidechains on a rigid cyclodextrin core.
Also, it should be possible to use meeko to prepare the cyclodextrin as a flexible ligand, which will include macrocycle flexibility, and dock both the cyclodextrin and the actual ligand as individual ligands to an empty receptor. If vina rejects the empty receptor, a workaround is to place the search space more than 8 Angstroms aways from any receptor atom.


Gracefully handle properties with object dtype

Description
In #2756 I noticed that properties with object dtype break the selection methods in the points layer due to an np.unique with the axis argument (see this comment by @andy-sweet).
To preserve the ability of having multidimensional arrays as properties, this fix intriduces a little check so that the axis argument is used only when the dimensionality requires it. It's not super elegant, but it works, and it will hopefully be superseded once we unify the properties as per #2866.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
Closes #2756.
How has this been tested?

[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas

Seems ok, but @brisvag could you add a test that fails before this change and passes with it?

@kevinyamauchi I think this can probably fit in this PR just fine; it looks like shapes has exactly the same code for this anyways. I'll check out  the other layers as well!

Implemented the same check for shapes; I don't see similar issues in other layers or places in the code.
I added tests for both layers, which fail without this change!

And thanks for the fix too @brisvag


Profile page doesn't show your avatar in top banner

It would be neat to have your avatar show up on the profile page.

@Engineering-Robert, seems that you haven't chosen any image at your profile page. https://react-mobx.realworld.io/#/settings otherwise it should work fine. Please reopen if it doesn't.


how to listen to an event emitted by the custom-action compontent ?

UserListCustomActions.vue:
itemAction (action, data, index) {
      console.log('custom-actions: ' + action, data, index)
        this.$emit('on-itemclick',{
            action:action,
            data:data,
            index:index,
        });
    }

use it in the vuetable's fields:
{
          name: '__component:custom-actions',
          title: 'action',
          titleClass: 'center aligned',
          dataClass: 'center aligned'
      }

how to call the @on-itemclick in the parent vuetable ? it doesnt work well

@bajian I think you should  call
this.$parent.$emit('on-itemclick',{
action:action,
data:data,
index:index,
});
In your parent component listen the event just like the following.
    <vuetable ref="vuetable"
              @on-itemclick="onActions"
    ></vuetable>

yes ,itworks well. thanks!


ST-Link v2.1 crashing?

Describe the bug
I'm using a ST-Link v2.1 with an ATSAMD21, this combination has been working fine for a few weeks with probe-run and defmt.  The first time I do probe-run --verbose --chip ATSAMD21G18AU path/to/firmware, it flashes and successfully opens up the defmt-rtt console successfully.  After about 20 seconds, probe-run exits with:
<normal defmt RTT output>
RTT error: Error communicating with probe: An error with the usage of the probe occured
Error: An error with the usage of the probe occured

Caused by:
    0: An error specific to a probe type occured
    1: Command failed with status JtagNoDeviceConnected

Once this failure has happened, subsequent probe-run invocations give:
  (HOST) DEBUG RAM region: 0x20000000-0x20007FFF
└─ probe_run @ src/main.rs:144
  (HOST) WARN  insufficient DWARF info; compile your program with `debug = 2` to enable location info
└─ probe_run @ src/main.rs:169
  (HOST) DEBUG section `.data` is in RAM at 0x20000000-0x20000147
└─ probe_run @ src/main.rs:204
  (HOST) DEBUG section `.bss` is in RAM at 0x20000150-0x20004C07
└─ probe_run @ src/main.rs:204
  (HOST) DEBUG section `.uninit` is in RAM at 0x20004C08-0x20005007
└─ probe_run @ src/main.rs:204
  (HOST) DEBUG vector table: VectorTable { location: 0, initial_sp: 20008000, reset: b1, hard_fault: 55a9 }
└─ probe_run @ src/main.rs:268
  (HOST) DEBUG found 1 probes
└─ probe_run @ src/main.rs:298
  (HOST) DEBUG opened probe
└─ probe_run @ src/main.rs:303
Error: An error with the usage of the probe occured

Caused by:
    0: An error specific to a probe type occured
    1: Command failed with status JtagNoDeviceConnected

To get a successful flash, disconnecting and reconnecting the USB to the ST-Link seems necessary.
Expected and observed behavior
I'd expect the session to not fail, but if it did I would expect to get some more detailed logging out with the --verbose flag specified, to be able to dig deeper in to the issue.
config.toml
[build]
target = "thumbv6m-none-eabi"

[target.thumbv6m-none-eabi]
runner = "probe-run --verbose --chip ATSAMD21G18AU"
rustflags = [
  "-C", "link-arg=-Tlink.x",
  "-C", "link-arg=-Tdefmt.x"
]

Probe details
ST-Link v2.1, just updated to firmware v2j37m26 which appears to be the latest, upgrade didn't change symptoms.
probe-rs-cli list
The following devices were found:
[0]: STLink V2-1 (VID: 0483, PID: 3752, Serial: 0670FF505055877267123015, STLink)

Operating System:
Ubuntu 20.04.1 LTS

After about 20 seconds, probe-run exits with:

are you using the WFI (Wait For Interrupt) or WFE (Wait For Event) instructions in your program?
Those instructions are available in the cortex-m crate as cortex_m::asm::wfi and cortex_m::asm::wfe. If you are using the RTIC framework, WFI is automatically called when no idle background task is defined.
I ask because I have read before that some STM32 chips have a debug register to enable / disable debugging when the device is in sleep mode (WFI / WFE) and the default value of the register is "disable". which may be related to:

To get a successful flash, disconnecting and reconnecting the USB to the ST-Link seems necessary.

is your program writing to Flash memory?
we have had reports before saying that flash write interfere with the probe operation. see knurling-rs/defmt#140

this combination has been working fine for a few weeks with probe-run and defmt

last week we released probe-run 0.1.6 which uses probe-rs 0.10.0. The previous version of probe-run (0.1.5) used probe-rs 0.8.0. probe-rs did a full rewrite of their st-link backend between 0.9.0 and 0.10.0; that may be related.
could you try probe-run 0.1.5 and report if the problems persist with that version?

Thanks @japaric , sorry I haven't had a chance to follow up today but can say that the program is not writing to flash.  I'll check for WFI/WFE tomorrow, and try probe-run 0.1.5.

are you using the WFI (Wait For Interrupt) or WFE (Wait For Event) instructions in your program?

No

could you try probe-run 0.1.5 and report if the problems persist with that version?

SAMD21 support was added to probe-rs after version 0.9.0; I had been using commit 21b26ad020cf07cd797593c503a7c8f3a8530fca successfully, but now rebuilding probe-run 0.1.5 (or latest main) with that version of probe-rs (and probe-rs-rtt pointing at it as well), I'm seeing the same problem.  So, the cause of the failure after ~20 seconds is a mystery...
Does JtagNoDeviceConnected mean that the target chip is not connected, or the probe is not connected?  If I disconnect the target chip when the ST-Link is in a good state then probe-run, I see JtagGetIdcodeError, however once the probe is in the bad state, probe-run results in JtagNoDeviceConnected regardless of whether the target chip is connected or not.  The chip seems to be running fine through all of this.
@Dirbaio shared a modification to get more logging out of probe-rs, with that in place and the ST-Link in the bad state, I ran probe-run --verbose /path/to/bin and got https://gist.github.com/ianrrees/47fbfb8e0915ed1f0c0825464eddeec9

I've borrowed a ST-Link v2, it's working fine with the same target.  So, it seems there is either some hardware issue with my probe, or a software/firmware problem with the ST-Link v2.1.  Will try to investigate a bit further.

So, the cause of the failure after ~20 seconds is a mystery...

Does it always fail after 20 seconds regardless of the program behavior? e.g. if your program does loop { asm::nop() } does it still fail after 20 seconds? If yes, this would help us discard the possibility of the error being triggered by the device itself.

Does JtagNoDeviceConnected mean that the target chip is not connected, or the probe is not connected?

"NoDevice" sounds like the (ST-LINK) probe did not find the STM32 micro. If the probe was not detected then you would probably get a USB related error early on.
"Jtag" sounds a bit suspicious. If the ST-LINK is connected to the STM32 with 2 wires (+ground): SWIO and SWCLK then only SWD communication is possible between the two -- JTAG requires more wires. It could also be that probe-rs tries SWD first and then falls back and tries JTAG if SWD didn't work.

I see JtagGetIdcodeError, however once the probe is in the bad state

iirc, fetching the IDCODE of the device occurs after initialization so in this case the probe seems to detect the STM32 chip but its SWD subsystem is not responding accordingly to SWD commands issued by the probe. It could be that probe-rs is not clearing the error state on the probe itself during initialization; that would explain why running probe-run again still fails and power cycling the probe fixes the issue.

I've borrowed a ST-Link v2, it's working fine with the same target.

Would be interesting to get logs from this successful setup and compare them to the logs from the setup that fails.

So, it seems there is either some hardware issue with my probe, or a software/firmware problem with the ST-Link v2.1.

There are a lot of ST-Link clones out there so I wouldn't be surprised if they are many version of the ST-Link firmware and each behaves slightly differently ..

Today, I learned that a colleague has another ST Nucleo dev board, still in the original packaging, identical to the one that my problematic probe came from.  I intend to borrow it next week, to see if there might be something physically wrong with this one.

Does it always fail after 20 seconds regardless of the program behavior?

Yes, though the 20 seconds is not exact at all.  I have two other debuggers (a ST-Link v2 and a J-Link Ultra+) that work perfectly with the same probe-run, target hardware, and firmware.

Would be interesting to get logs from this successful setup and compare them to the logs from the setup that fails.

I'll attach some here - they were collected with probe-run bb4b9c716876b40438e12045ff87f4e7a6ec64dd , except src/logger.rs modified to display all logging in verbose mode.  I've also included a log of OpenOCD failing in a similar way with the problematic probe logs.tar.gz

There are a lot of ST-Link clones out there

Understood, however I am reasonably confident that these are both genuine ST probes, and I have updated their firmware to the latest on ST's site.

Apologies for the slow follow-up.  The second ST-Link v2.1 (AFAICT identical to the first) works perfectly, so it seems I must've somehow damaged the electronics in the first one.
My first attempts with the second probe didn't connect, --verbose said that the probe was in mass storage mode, I used the ST link007 upgrade tool to put the probe in to firmware upgrade mode, closed the program, then retried and it went in to Jtag mode as desired.

I've been experiencing a very similar issue, also with SAMD21 (Adafruit Trinket M0). I fixed it twice, once by switching to a new STLINKv2 clone, and the other time by building my own probe from a Bluepill board (with latest STLINKv2 firmware). Both replacement also failed eventually. I can still flash my binary and get RTT log output for a few (~5) seconds before the link fails, after which the probe needs to be re-plugged into USB to be detectable by cargo-embed.
I've been powering the Trinket with 5V from the STLINK as I am using it to power an external USB device (a small MIDI controller). I've noticed that openocd will often report target voltage being in the 3.0-3.2V before a crash and being 2.4V after a crash. I've don't know enough about the probe hardware to guess how damage could occur in such conditions.
While I understand this may not be a cargo-embed issue per se, I see no other place than here to track it for now.  I would like to keep collecting more data from others. It might be something SAMD21-specific since I've had no such issue with STM32 boards.


Add an explicit 'label_column_name' argument instead of using the 'texture_kwargs' dict

Since TexturedPhotogrammetryMesh() is a major user entrypoint, it would be ideal to make it as intuitive as possible. I think an explicit label_column_name argument would be more intuitive than a texture_kwargs dict with a column_name key. Ideally this would be done to load_texture too, though if necessary the dict could be created internally before calling load_texture. It looks like column_name is the only key ever used in this dict (currently) anyway?
https://github.com/open-forest-observatory/multiview-mapping-toolkit/blob/506338e882f7701ab54b20189148be64ec3e554e/multiview_prediction_toolkit/meshes/meshes.py#L49

This is a good idea. The original motivation for having a kwarg dict was I thought there might be a lot of optional params across all the input modalities. But this never ended up being required.


Update non-breaking dependencies

coverage: 97.701%. remained the same
when pulling d67c0042d8d0185de7c6471c163177673dd325a3 on update-dependencies
into 2be2b233cae892a3afe83bf184dc041bd29c865b on master.


Make it clearer that all flags are settable by env var

Closes: #47

Thanks for the PR! Could you sign the CLA please?

I'm now CLA'd.

@ismith thanks :smile:

so to specify multiple sources I set EXTERNAL_DNS_SOURCE="service,ingress"? Unfortunately this isn't defined anywhere.

@bechtoldt I added a FAQ entry for the env var. Feel free to thumbs up: https://github.com/kubernetes-incubator/external-dns/pull/310


[api] Support queryString for JarRepository

Change-Id: I2c5e92bbb1da52db2298d90f1c36cbef33873151
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Thanks for the quick fix, @frankfliu @lanking520 I'll upgrade DJL as soon as this gets merged.

Codecov Report

Merging #1842 (3469d3e) into master (bb5073f) will decrease coverage by 2.33%.
The diff coverage is 64.68%.

@@             Coverage Diff              @@
##             master    #1842      +/-   ##
============================================
- Coverage     72.08%   69.75%   -2.34%
- Complexity     5126     5527     +401
============================================
  Files           473      526      +53
  Lines         21970    24445    +2475
  Branches       2351     2665     +314
============================================
+ Hits          15838    17052    +1214
- Misses         4925     6081    +1156
- Partials       1207     1312     +105

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../cv/translator/SemanticSegmentationTranslator.java
0.00% <0.00%> (ø)

.../cv/translator/StyleTransferTranslatorFactory.java
40.00% <ø> (ø)

... and 420 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 b6b0e6a...3469d3e. Read the comment docs.


saga: 9.0.1 -> 9.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/saga-gis/versions.
meta.description for saga is: System for Automated Geoscientific Analyses
meta.homepage for saga is: http://www.saga-gis.org
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.0.2 with grep in /nix/store/a7562jr99wczgh8il223gjd4nw86l81q-saga-9.0.2
found 9.0.2 in filename of file in /nix/store/a7562jr99wczgh8il223gjd4nw86l81q-saga-9.0.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
saga

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

saga

Maintainer pings
cc @michelk @mpickering for testing.

Result of nixpkgs-review pr 239735 run on x86_64-darwin 1

1 package built:

saga


feat: add sign out warning and check (Closes #3037)

This pr closes https://github.com/hirosystems/stacks-wallet-web/issues/3037
I decided to go further and add one more checkbox, as this is very critical flow and mistake here may lead to loosing funds.
Actually, we can even remove this second warning and keep checkbox.

Thanks! Yea I agree, let's just keep the second checkbox and no need for a second warning.
Some tweaks to the new checkbox's label: I understand my password will no longer work for accessing my wallet upon signing out

done

close in favour of https://github.com/hirosystems/stacks-wallet-web/pull/3276


Problems in table of contents

There are a few things that are broken about the table of contents:

the 'V1' link is the root of all TOC items and links to a completely obscure @context property that probably shouldn't even be in the metamodel. (It's only there until we can figure out how to generate JSON Schemas that allow JSON-LD @context properties some other way.)
the 'GOV.UK Vocabulary' item at the top should probably link to the home page ie duplicate the 'Vocabulary' link in the top menu bar (but see https://github.com/govuk-one-login/data-vocab/issues/21).
the home/credentials item in the TOC is a bit strange, though have a full contents somewhere is probably a good thing.

Top two issues have been resolved with new theme however we need to determine do we want a full schema (home/credentials item) - Its kinda nice but also i'm really not sure how many people who would use it

https://github.com/govuk-one-login/data-vocab/pull/76 ended up being more radical than I expected, but ... hurrah for deleting code :-) ?


Tests for adding properties in package.json failing

In module Apis And Microservices > Managing Packages with Npm, tests failing although providing link to seemingly valid Glitch package.json with the required changes.
What I do:

Adding the required property in the package.json and copy the url:

Paste url and submit. Test fails because of unexpected token and there is a warning in the console:

Tests are also failing for the following related lessons:
Add a Description to Your package.json
Add Keywords to Your package.json
Add a License to Your package.json
Add a Version to Your package.json
Environment:
Windows 10
Chrome 66

I found another issue raised during beta, related to this one that helped me submit my solutions. More information here #13095. In short, if you're using Glitch in order to complete the lessons, first make sure you open the Glitch project from the link provided in Introduction to the Managing Packages with npm Challenges. Once you make the required changes click on Show Live  button (top right). Copy the link from the newly opened tab for the solution.

anybody give the answer for this questions


Support multiple image/audio columns in ImageFolder/AudioFolder

Feature request
Have a metadata.csv file with multiple columns that point to relative image or audio files.
Motivation
Currently, ImageFolder allows one column, called file_name, pointing to relative image files. On the same model, AudioFolder allows one column, called file_name, pointing to relative audio files.
But it's not possible to have two image columns, or to have two audio column, or to have one audio column and one image column.


Disable for Rails Console

Is there any way we can have public_activity disabled for all Rails Console activity? It'll need to remain active for all web-facing stuff, just not for the console.
Thanks.

Hi Dennis,
you can do something like this in your initializers:
config/disable_public_activity.rb

if defined?(Rails::Console)
  PublicActivity.enabled = false
end

Who's Dennis? :tongue:
Thank you though, I'll give that a try.

Ha, sorry. Wrong name starting with D :dancer:

Putting the above code in an initializer doesn't seem to work for rails 5.1.5.
NoMethodError: undefined method 'current_user' for nil:NilClass
When trying to make a modification to a User via console with the following on the User model:
include PublicActivity::Model
tracked owner: Proc.new{ |controller, model| controller.current_user }

Shouldn't the PublicActivity.enabled = false turn off all tracking?


"Undefined index" notice after calling phpCAS::setDebug(false) for v1.2.2

Calling phpCAS::setDebug(false) unsets $PHPCAS_DEBUG['filename'] which in turn causes "undefined index" notice for line if ($PHPCAS_DEBUG['filename']) {  in the phpCAS::log() function.
Replacing line unset($PHPCAS_DEBUG['filename']) with $PHPCAS_DEBUG['filename'] = FALSE; in the phpCAS::setDebug() function should fix the issue.
I wasn't sure for which branch to make the fix hence didn't provide a patch.

Thanks for opening this issue.
If you would like to submit a patch, just base it off of the 1.2.2 tag at commit 07a720c33870 (I've added a 1.2-stable branch at that point from which we will build a 1.2.3 release).
Alternatively, I can just make the change on Monday.

It turns out that we already had a fix (735e863bb5) on master for this issue that is going into the upcoming 1.3.0 release. I have cherry-picked 735e863bb5 onto the 1.2-stable branch as 3f6b6a0cdc.


ECONNREFUSED problem

I'm trying to input to a remote server from my local dev machine. I have sudo, and connect to the server routinely with an ssh private key. I can dump the files locally, copy them over and restored them, creating a copy of the index, but I'd like to get this on a script. I've tried with and without a loginname@ or user:password@ prefix to the ip, also with and without the --key option. There is no password associated with the key. I've opened port 9200 on the server, and confirmed:
To                         Action      From
--                         ------      ----
9200                       ALLOW       Anywhere
9200/tcp                   ALLOW       Anywhere
9200 (v6)                  ALLOW       Anywhere (v6)
9200/tcp (v6)              ALLOW       Anywhere (v6)

I must be missing something basic here -- thanks!

ElasticDump version 4.4.0

Elasticsearch version 6.1.1 local, 6.4.1 remote

Node.js version v11.10.0

Full command you are having issue with (with inputs and outputs)
elasticdump --input=http://localhost:9200/my-index --output=http://<IP_ADDRESS>:9200/my-index --type=mapping --input-key ~/.ssh/id_rsa

A data set you can share publicly which reproduces the problem
not sure this is applicable

It never hurts reading the documentation.
input-key is a parameter for TLS X509 authentication. Try port-forwarding ssh ssh -L ${PORT}:<IP_ADDRESS>:${PORT}, then do whatever.

I have read the documentation. Snide remarks like that are offensive, but I guess that's what you were after. In the documentation, --key references a private key file, nothing about TLS X509, which is referred to above, for the --tlsAuth option. Perhaps the several lines below that all refer to tlsAuth, but that is not apparent.

--tlsAuth
                    **Enable TLS X509 client authentication**
--cert, --input-cert, --output-cert
                    Client certificate file. Use --cert if source and destination are identical.
                    Otherwise, use the one prefixed with --input or --output as needed.
--key, --input-key, --output-key
                    Private key file. Use --key if source and destination are identical.
                    Otherwise, use the one prefixed with --input or --output as needed.
--pass, --input-pass, --output-pass
                    Pass phrase for the private key. Use --pass if source and destination are identical.
                    Otherwise, use the one prefixed with --input or --output as needed.
--ca, --input-ca, --output-ca
                    CA certificate. Use --ca if source and destination are identical.

The options above are all related to TLS X509
  /// Code snippet
    if (this.parent.options.tlsAuth) {
      Object.assign(defaultOptions,
        this.applySSL([`${options.type}-cert`, `${options.type}-key`, `${options.type}-pass`, `${options.type}-ca`]))

      Object.assign(defaultOptions, this.applySSL(['cert', 'key', 'pass', 'ca']))
}


add -project suffix to root directory

Fixed #36

Fixed #36

Looks fine for me.

After merging #59 this is unfortunately not useful any longer.


More clear readme

Write steps more clear and understandable with appropriate screenshots.

https://github.com/Chingiz/exfsa/pull/4 Updated Readme with screenshots and short descriptions =)

accepted


DLP Alerts retention

This document and probably others (or a FAQ page) should have information about how long DLP alerts remain available in the Portal.
This type of information is often asked by customers.
I could not find this information anywhere and needed to open a support case.

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

ID: d4e9f547-6180-2981-6e7a-895fc17b7703
Version Independent ID: 58334631-7058-1809-0804-c107457b4470
Content: Configure and view alerts for data loss prevention policies - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/dlp-configure-view-alerts-policies.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@msbemba

@chrfox Please help us resolving this issue. Thanks. Email sent with details : 12-19-2021

Hi @jorge-at123
Thanks for your comment, I'll get the information and update the content as appropriate.

Hello @chrfox!
I could not find the information in the docs. Did you update another DLP document with the Alerts retention information?
I would like to have the document to send to our customers.
Thanks!


Lambda vs. EC2

If I'm building the backend for an MVP of my mobile app, would you recommend using the design pattern found in this repo, or a typical Express app on EC2 beanstalk instances?

@brennanerbz I'm not sure if this setup fits your use case (basic CRUD app + authentication + uploads). But if it does, then I would recommend it.
That being said, as a startup founder myself; I would probably go with a setup that you are most familiar with. Given that your time is probably the biggest factor.
Btw, I see your email. I'll send you a note.

Closing this.


Problem having 6 and 7 co-exist

Steps to reproduce
Install PowerShell 7 Release following defaults on a system where PowerShell 6 is present
Expected behavior
6 can remain in place for side by side testing OR be removed  depending on what the user requires
Actual behavior
6 is removed, and attempting to [re]install  6.2.4 gives an error "there is a newer version installed".
Suggestions.

Install should ask before removing a prior version (perhaps only there is a change of major version)
Install should not refuse to install an older version (again perhaps only allowing a change of major version).

Work round (for windows 10)
Install makes a shadow copy.
get-ciminstance Win32_ShadowCopy | ft installDate,DeviceObject
Will show a list of shadow copies.  My newest one was number 6, so I copied that to from the command below (n.b. I added a trailing \ to the name)
cmd /c mklink /d c:\ShadowCopy "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\"
Now I can copy from C:\ShadowCopy\Program Files\PowerShell\6 to restore 6
Delete C:\ShadowCopy when done.
Alternatively download the ZIP version of 6.2.4, unblock and expand into the 6 directory.

An alternative workaround is to just download the PS 6 zip and extract it back to $env:ProgramFiles\PowerShell\6\.
This is a dupe of 12002 where it is discussed thoroughly.

My error. I saw @KevinMarquette  mention it on twitter but he seems to have opened the item here rather earlier than I thought so I didn't scroll down far enough to spot it.


dyndns/rfc2136: Menu/ACL refactoring

We're almost there, missing:

Move Menu location to "Services" as full service.
Create separate Menu.xml
Create separate ACL.xml

Done in 17.1.5.


uv run command gives error: path segment contains separator ':'

I used uv venv --python 3.10 to create a virtual env and activated it. Under this venv, I created a main.py containing a single line of code print('Hello world!'). However, when I ran the script using uv run, I got the error saying path segment contains separator ':'.
(me) ☁  me [master] ⚡  uv run main.py --verbose
error: path segment contains separator `:`
(me) ☁  me [master] ⚡  python main.py
Hello world!

macos version: Sequoia 15.1
The current uv version: uv 0.5.1 (Homebrew 2024-11-08)

I've never seen this before -- I assume it has to do with something unusual in some path on your machine. What does pwd look like? What about your $PATH?

ohh, thank u so much for your suggestions! I checked my CWD, and it turns out the issue was indeed caused by an unusual character in the directory name. The : in the path below was causing the problem:
/Users/clannad/Dev/mercurius/ucb/cs194:294-196_fa24/me/

No prob, thanks for following up!

Hey, I am currently trying to move my CI setup from poetry to uv with docker on jenkins and am experiencing a similar error when trying to sync my venv.
Locally everything is fine, but on CI i am getting the following error:
error: Failed to prepare distributions

  Caused by: Failed to build `component-config-util @ file:///srv/dsadock/atvmces/workspace/r_feature_replace-poetry-with-uv/component_config_util`

  Caused by: Failed to build PATH for build script

  Caused by: path segment contains separator `:`

script returned exit code 2


fix: 新增点边选中效果且被选中时展示属性浮层

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ths01153973 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Controller Separation] Add logic for lead controller resource

This is the last PR of controller separation (Design doc).
This PR:

adds all the logic needed for lead controller resource. ControllerLeadershipManager is removed in this PR. All the periodic tasks are run depending on whether the current controller is the leader for given tables.

adds a API to get the controller leader id and partition index given a table name.

API:
GET http://localhost:18998/tables/mytable/controller
Response:
{
  "status": "Partition index: 10, lead controller: Controller_localhost_18998"
}

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@eee245e). Click here to learn what that means.
The diff coverage is 79.89%.

@@            Coverage Diff            @@
##             master    #4323   +/-   ##
=========================================
  Coverage          ?   65.48%
  Complexity        ?       20
=========================================
  Files             ?     1062
  Lines             ?    55014
  Branches          ?     7832
=========================================
  Hits              ?    36024
  Misses            ?    16420
  Partials          ?     2570

Impacted Files
Coverage Δ
Complexity Δ

...i/resources/PinotSegmentUploadRestletResource.java
67.5% <ø> (ø)
0 <0> (?)

.../pinot/controller/api/upload/SegmentValidator.java
64.7% <100%> (ø)
0 <0> (?)

...elix/core/relocation/RealtimeSegmentRelocator.java
73.62% <100%> (ø)
0 <0> (?)

...e/pinot/controller/helix/SegmentStatusChecker.java
87.3% <100%> (ø)
0 <0> (?)

...troller/helix/core/retention/RetentionManager.java
79.16% <100%> (ø)
0 <0> (?)

...g/apache/pinot/common/utils/helix/HelixHelper.java
56.49% <100%> (ø)
0 <0> (?)

...anager/realtime/SegmentBuildTimeLeaseExtender.java
57.4% <100%> (ø)
0 <0> (?)

...ata/manager/realtime/RealtimeTableDataManager.java
42.64% <100%> (ø)
0 <0> (?)

...org/apache/pinot/controller/ControllerStarter.java
69.56% <100%> (ø)
0 <0> (?)

...altime/ServerSegmentCompletionProtocolHandler.java
48.85% <100%> (ø)
0 <0> (?)

... and 15 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 eee245e...d8c51fd. Read the comment docs.

I would wait for at least one other review on the API. Perhaps the API can be a separate checkin.
One thought that comes to mind is have an API URI like: "/leadController/tables" -- return the lead controller for all tables and "/leadController/tables/tablenameregex" return the lead controller for tables matching a regex.
The output in both cases can be like:
  [     "tableName" : {        "partition" : 9,        "leader" : "hostName"      },      ...   ]

An issue is created to track the API design: https://github.com/apache/incubator-pinot/issues/4441
We can remove the API out of this PR.


Warning: server timed out after hitting its 5s timeout!

Have you experienced this bug with the latest version of the template?
yes
Steps to Reproduce
Create a folder on a windows drive from within WSL and setup project there
mkdir /mnt/c/dev
cd dev
npx create-remix --template remix-run/grunge-stack

-- or --
npm run validate

Result:
✓ Sandbox Started file watcher
Watching Remix app in development mode...
⚠  Test routes enabled.
⚠ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
...

If the project is created in a linux folder (e.g. ~/dev/) it works just fine.
Expected Behavior
Tests run through
Actual Behavior
⚠ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!

is repeated forever

Did you ever find a solution to this?

I couldn't get it run on a windows filesystem (/mnt/c), but this error didn't occure if run on a linux filesstem (~/)

I'm experiencing the same issue :(

Following the Arc documentation, you can configure the execution time of your Lambda handler, here's my app.arc
@app
commandport-ui-621b

@arc
env true

@http
/*
  method any
  src server

@static

@aws
timeout 60              <-- default exec time of your handler is 5s, up it to 60 in dev (my prod one is still 5s)
memory 256
concurrency 10          <-- if running in prod, I noticed some 500 errors, upping concurrency fixes this
region eu-west-2


Animation duration

I am using the package for a book that about 300 pages. When I want to go a spesific page, I am using
 listObserverController.jumpTo(index: 150) Which is going to 150th page.
But it took a while to go to the page when I am in page 5. The screen animating (emulating) a real scroll. I wait until it reach the point I enter.
Is there a way to really Jump to the spesific index. Not animate.

Yes, the package will have the problem you mentioned, because it has to scroll close to the target position to know the offset, then the offset will be recorded, so there will be no animation when the second time jumping to the same index.
Is the height of the child widgets fixed? If so, you can adjust to rely on the develop branch, and use the isFixedHeight parameter to solve the problem you said, as follows:
dependencies:
  scrollview_observer:
    git: https://github.com/LinXunFeng/flutter_scrollview_observer.git
    ref: develop

listObserverController.jumpTo(index: 150, isFixedHeight: true);

Related demo: listview_fixed_height_demo

thanks. Unfortunately my pages are not have fixedsize.
May be next days we may find some solutions.
It doensn't look bad for today.
Have a nice day

@cyb3rsalih Hello. Did you manage to find some solution when scrolling the list, where the height of the elements is not the same?


Issue Reporting App no longer available to add to new Teams channels

My organization uses the Issue Reporting App for a variety of purposes in different Teams channels and has plans to implement it further in the future. However, approximately 2 weeks ago, I discovered that the Issue Reporting App is no longer available to install/add to new Teams channels. The app does remain present and fully functional in Teams channels where it was already installed prior to this discovery.
It appears that the app has been removed from the default apps list. Is this a known issue? Has the app simply been relocated, or will it be restored? Thanks in advance for any help/info you are able to provide.

See issue #26 - may help

Thanks @RebeccaWilso. I did experience that same issue on 31Jan with the app after it had already been installed to an existing Team, but it was resolved the next day.
Unfortunately, I'm now having a different issue where the App seems to have disappeared from the list of default apps that can be added to a new Team.


Error if the table haven't primary key

If thy table haven't primary key, and i pass $returnID = false, than the ci4 throw this error:
CRITICAL - 2020-09-24 00:47:00 --> pg_query(): Query failed: ERROR:  lastval is not yet defined in this session
#0 [internal function]: CodeIgniter\Debug\Exceptions->errorHandler(2, 'pg_query(): Que...', '/var/www/ci4/sy...', 196, Array)
#1 /var/www/ci4/system/Database/Postgre/Connection.php(196): pg_query(Resource id #9, 'SELECT LASTVAL(...')
#2 /var/www/ci4/system/Database/BaseConnection.php(741): CodeIgniter\Database\Postgre\Connection->execute('SELECT LASTVAL(...')
#3 /var/www/ci4/system/Database/BaseConnection.php(669): CodeIgniter\Database\BaseConnection->simpleQuery('SELECT LASTVAL(...')
#4 /var/www/ci4/system/Database/Postgre/Connection.php(519): CodeIgniter\Database\BaseConnection->query('SELECT LASTVAL(...')
#5 /var/www/ci4/system/Model.php(887): CodeIgniter\Database\Postgre\Connection->insertID()
#6 /var/www/ci4/app/Models/MyModel.php(46): CodeIgniter\Model->insert(Array, false)
#7 /var/www/ci4/app/Controllers/MyController.php(113): App\Models\MyModel->new_connection('1', '1')
#8 /var/www/ci4/app/Controllers/MyController.php(54): App\Controllers\MyController->do_create_connection()
#9 /var/www/ci4/system/CodeIgniter.php(918): App\Controllers\MyController->create_connection()
#10 /var/www/ci4/system/CodeIgniter.php(404): CodeIgniter\CodeIgniter->runController(Object(App\Controllers\MyController))
#11 /var/www/ci4/system/CodeIgniter.php(312): CodeIgniter\CodeIgniter->handleRequest(NULL, Object(Config\Cache), false)
#12 /var/www/ci4/public/index.php(45): CodeIgniter\CodeIgniter->run()
#13 {main}
CRITICAL - 2020-09-24 00:47:00 --> Uncaught CodeIgniter\Format\Exceptions\FormatException: Failed to parse json string, error: "Type is not supported". in /var/www/ci4/system/Format/Exceptions/FormatException.php:9
Stack trace:
#0 /var/www/ci4/system/Format/JSONFormatter.php(71): CodeIgniter\Format\Exceptions\FormatException::forInvalidJSON('Type is not sup...')
#1 /var/www/ci4/system/API/ResponseTrait.php(414): CodeIgniter\Format\JSONFormatter->format(Array)
#2 /var/www/ci4/system/API/ResponseTrait.php(134): CodeIgniter\Debug\Exceptions->format(Array)
#3 /var/www/ci4/system/Debug/Exceptions.php(168): CodeIgniter\Debug\Exceptions->respond(Array, 500)
#4 [internal function]: CodeIgniter\Debug\Exceptions->exceptionHandler(Object(ErrorException))
#5 {main}
  thrown
#0 [internal function]: CodeIgniter\Debug\Exceptions->shutdownHandler()
#1 {main}

This will skip to getting inserted ID
Each pull request should address a single issue and have a meaningful title.
Description
Explain what you have changed, and why.
Checklist:

[ ] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

---------Remove from here down in your description----------
Notes

Pull requests must be in English
If the PR solves an issue, reference it with a suitable verb and the issue number
(e.g. fixes 12345)
Unsolicited pull requests will be considered, but there is no guarantee of acceptance
Pull requests should be from a feature branch in the contributor's fork of the repository
to the develop branch of the project repository

Model class is designed to work with the primary key to function correctly. In other words - you have to have a primary key field in your table. It doesn't have to be an auto-increment field - you can use your own primary key value. To use your own value set the useAutoIncrement variable to false.

Sorry, but the term: you have to have a primary key is wrong. Not globaly, but in the relation of two table (https://en.wikipedia.org/wiki/Many-to-many_(data_model)) it not nessesary to have in table the primary key filed, the primary key is created by two (or more) columns, in this case by two foreign keys.
I trying to do this connection via m2n_model->insert method, and the method throws error.
This "patch" just avoid to obtain the inserted ID.

You missed the first sentence which is very important here:

Model class is designed to work with the primary key to function correctly.

In general you're right but the current Model class implementation doesn't support things you want to achieve and this simple "patch" won't change it. Feel free to extend it, modyfy it or write your own Model class that will fit your needs.
To be clear - we're open to the PRs that will extend the current functionality of the model but these changes must be comprehensive and ensure the correct functioning of all elements of the Model class.


Capitalise README heading

IDK how to explain that headings should be capitalised, and I sure hope this doesn't lead to an argument about English. :)

(also wheeeee, notification spam!)


Laura's nitpicks during onboarding

[x] On README.md under “Using this repository” it says you’ll be using Docusaurus, but under “Prerequisites” Git, Nodejs, and Yarn are listed as needing to be installed while Docusaurus is not. So I wondered for a minute whether I needed to install Docusaurus, but in fact Docusaurus “comes with” npm, which could be worth stating explicitly.

[x] - Under “Running the website locally” it says we need to run
cd docs/website   npm run build   npm run serve
But there’s a step missing, and it should instead read
cd docs/website
npm install (this was the missing step)
npm run build
npm run serve

[ ] - In the image below, should it be clear that the text in the lower box will be generated by the terminal when subo build .finishes? It’s mostly clear, but the copy button in the corner throws it into question slightly. I think this is determined by some kind of styling infrastructure, but I'm not sure exactly where. But maybe there is/could be a distinct way to show code that isn’t being provided for the user to coy and use as input on their end, just for the sake of maximal clarity?) This probably happens in more places than just this one.

I've taken care of the first two, but the last is kind of a style question, and also I don't know where the styling lives so I would need some guidance to fix it.

Thanks for pointing these out, Laura!
Did some poking around, found this.
This seems fairly doable (Also, I had no idea that adding text next to the backticks was essentially giving it a class 🤯 )
Happy to give this a shot!


Expose and document archived types

Right now, all of the archived versions of core and std types are all hidden and partially undocumented. Getting these out in the open will improve the developer experience.

Fixed by 7ebdf5f30dfc1b9f0568dfe254f0807ac5f25fd2


Entities for "return to grid" and "grid consumption"

Hi,
I can't see entities for the items "return to grid" and "grid consumption" though it should be possible to configure, I think.
I have a sungrow sg10rt, also tried to choose model sg5kd, which makes no difference.
regards and thanks for your work
Georg

I can't see entities for the items "return to grid" and "grid consumption" though it should be possible to configure, I think.

They come in as attributes on the entity. Unfortunately the energy monitoring stuff in Home Assistant can't make use of the attribute values directly, but it's easy enough to setup a template sensor in your config file to get them as separate entities which you can then use:
template:
  - sensor:
      - name: inverter_self_consumption_today
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
        state: >
          {{ state_attr('sensor.inverter_energy_today', 'daily_energy_consumption')|float / 1000 }}
        availability: >
          {{ states('sensor.inverter_energy_today')!='unavailable' }}
      - name: grid_purchased_today
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
        state: >
          {{ state_attr('sensor.inverter_energy_today', 'daily_purchased_energy') }}
        availability: >
          {{ states('sensor.inverter_energy_today')!='unavailable' }}
      - name: grid_exported_today
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
        state: >
          {{ (state_attr('sensor.inverter_energy_today', 'daily_power_yield')|float - state_attr('sensor.inverter_energy_today', 'daily_energy_consumption')|float) / 1000 }}
        availability: >
          {{ states('sensor.inverter_energy_today')!='unavailable' }}

daily_energy_consumption
daily_purchased_energy

Where did you find this value? I want to add some values for my, but I don't know how I can access the values...

daily_energy_consumption
daily_purchased_energy

Where did you find this value? I want to add some values for my, but I don't know how I can access the values...

they are attributes on the sensor state, go look at the state in developer tools and it'll show all the attributes

they are attributes on the sensor state, go look at the state in developer tools and it'll show all the attributes
As far as I understand is the attribute a Template which you can define yourself. But I don't understand how you bind it to a value from the Modbus. E.g. "daily_purchased_energy" is nowhere definded.

So my question is: How can I bind the attribute to a Modbus value.
Sorry, but I'm a beginner to HA...

they are attributes on the sensor state, go look at the state in developer tools and it'll show all the attributes
As far as I understand is the attribute a Template which you can define yourself. But I don't understand how you bind it to a value from the Modbus. E.g. "daily_purchased_energy" is nowhere definded.

So my question is: How can I bind the attribute to a Modbus value.
Sorry, but I'm a beginner to HA...

It's already there by default, at least with my SG5KD inverter they are anyway, to be able to use them in the energy dashboard you need to setup template entities, which is what the config I pasted earlier does. If it's not there for you it might not be supported on your inverter or your inverter might be wired up differently than mine is.

Now I do understand the purpose of this Codeblock:

Thank you! You helped me a lot!

Added in last commit

Note the commit referenced added self solar consumption, and grid import (although there's an issue with this value as per #15), but it didn't add a grid export field which is needed by the HA Energy stuff.
Grid export needs to be calculated as (daily_power_yield-daily_energy_consumption)/1000 kWh (note the latter is the self consumption already added in the commit last week).
It's easy enough to do this calculation in a template as I'd done above, but it'd be nice for it to work out of the box with the HA Energy stuff without having to setup template sensors.


sampled_expval_complex now returns Complex64 instead of float64

A small change to allow samled_expval_complex to return Complex64 instead of f64 see the following issue. fixes #11393
I'm marking as draft as this is my first PR on this project and would like some feedback on the style of it.

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

On hold pending resolution of conflicting assignments: https://github.com/Qiskit/qiskit/issues/11393#issuecomment-1873826322

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 87.557%

Totals

Change from base Build<PHONE_NUMBER>:
0.004%

Covered Lines:
59257

Relevant Lines:
67678

💛  - Coveralls

@jakelishman Yes sure ill have a look tommorow and the release note. Should I make separate PRs for Pauli(iZ) and Pauli(-Z)? Thanks for the feedback.


Fix initializing CKEditor

#8118 is caused by this issue:
Here's the situation:

we create a <div contenteditable="true">
we manually create the CKEditor instance
when the DOM is loaded, if CKEDITOR.disableAutoInline is true, CKEditor automatically starts the CKEditor instances of all the elements with contenteditable set to true

Since we don't set the disableAutoInline properly, CKEditor tries to initialize twice an editor for the same HTML element, so it throws this error.
#8267 tries to solve the issue by setting disableAutoInline properly, but this is just a workaround which touch a global variable, which may lead to unexpected side effects (example).
IMHO the easiest and cleanest solution is to simply avoid setting contenteditable="true" editor instances we are manually creating.
Fix #8118

I'm experiencing the same issue, across all themes on a fresh 8.5.2 install. I tried implementing the code in the fix with no change in result.

Same here, did not find anything that fixed this enoying error.

This is not fixed in 8.5.2 - It will be fixed in 8.5.3 when that’s released

I just ran some test, as I figured it might be specific to the composer version of c5. Blank install of both composer and zip version on a MAMP install - both work correctly out of the box, no error observed.
I then ran composer update on the site experiencing the issues out of curiosity. It appears that several packages were updated (this site was only installed a few days ago!), and now the error has disappeared. Doesn't make much sense, but I thought I would share my results anyway.

@aembler  we  just started experiencing this same on our 8.5.2 yesterday.  The issue only occurs in chrome. We can't edit blocks on the cms in chrome. It is still working in firefox for now. We can't edit blocks on the enterprise cms in chrome. It is still working in firefox. contenteditable="true" is on the pages I checked and we recently released so composer was probably updated with that release yesterday or the one we did last thursday.

I am also putting in a ticket to portlandlabs as well. It would be nice if there is an easy fix for this sooner than later in v8.5.2 we can't wait on the new version.
Thanks for your help.

This does not appear to be fixed. I'm still seeing the Error code: editor-element-conflict on several sites running 8.5.4
I'm also finding that when content blocks are edited more than once within a 'Page Edit' the initial unedited content can be reloaded rather than previously changed content.


feature: Default order of completions with LuaSnip

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
This request is to change some default configurations regarding nvim_cmp and LuaSnip. Right now, when writing code, nvim_cmp prefers buffer contents/LSP suggestions over snippets. This is especially jarring when writing Ruby code.
class ApplicationController < ActionController::Base
  def home; end

  def # <<< The keyword 'def' is the first entry in the completion list, rather than the 'def' snippet
end

This is because LuaSnip is inserted last in the list of nvim_cmp sources.
// From the LuaSnip config
opts = function(_, opts)
    // ...
    table.insert(opts.sources, { name = "luasnip" })
end

The resulting sources array looks like this.
// print(vim.inspect(opts.sources))
{ {
    group_index = 1,
    name = "nvim_lsp"
  }, {
    group_index = 1,
    name = "path"
  }, {
    group_index = 2,
    name = "buffer"
  }, {
    name = "luasnip"
} }

Describe the solution you'd like
I suggest inserting LuaSnip completions before buffer and potentially path. LSP suggestions take precedence over both, why not snippets as well? Seems to me like a more sane default than the current🤷♂
As far as I understand, a simple solution would be to modify that Luasnips/Cmp config like so:
table.insert(opts.sources, 2, { name = "luasnip", group_index = 1 })
                           ^

Describe alternatives you've considered
Individual users can modify the order of completions. This is what I'm doing right now:
return {
  "hrsh7th/nvim-cmp",
  -- Luasnips is added last to the completion sources, hence it has priority below buffer.
  -- Reorder it to first position so snippets take precedence over LSP and Buffer.
  --
  -- See https://www.lazyvim.org/plugins/coding#nvim-cmp-1
  opts = function(_, opts)
    local sources = opts.sources
    table.remove(sources, sources.getn)
    table.insert(sources, 1, {
      name = "luasnip",
      group_index = 1,
    })
  end,
}

Additional context
There's some additional trickery involved with the default config. Sources lsp and path are nested into a group (?), so entries are grouped rather than representing a flat array. I'd just be curious what the intention/benefit of that approach over flat arrays is 😊
sources = cmp.config.sources({
    { name = "nvim_lsp" },
    { name = "path" },
  }, {
    { name = "buffer" },
  }),

As a fellow user like you, my opinion about this is that it's a rather personal preference and in a Neovim distro not all personal preferences can be accommodated. This is why people tinker with their configuration to make it fit their needs. I myself for example have an additional comparator function that makes even the LSP snippets appear last because I prefer it that way. That said, it's totally up to the maintainer to make a decision on this, I'm just expressing my personal opinion.
Regarding your additional context, lsp and path are nested into a group separately, because the cmp.config.sources function takes that into consideration to separate sources into different index groups. So, the first subtable (lsp and path will have index = 1) and the second subtable with only buffer will have index = 2. That's just syntactic sugar that the specific nvim-cmp function provides to separate sources into different groups instead of specifying the index for each source.

You can confiure this with cmp indeed


Video tokens will not load on Rarible.

I have uploaded tokens to the Rinkeby Blockchain and they work on Openseas but the video will not load on Rinkeby.rarible.com.
https://rinkeby.rarible.com/token/0x7a3ba87e3b49dd82f0774b8ead207db3e39c9134:30?tab=details
https://testnets.opensea.io/assets/0x7a3ba87e3b49dd82f0774b8ead207db3e39c9134/30

Awesome! This is likely an issue with Rarible as opposed to something wrong with your code.
Closing for now, feel free to follow up.

@Bracciata  Were you able to see the video clip right after you minted? or Did you wait for long time to see the video clip through opensea?

I had to wait up to 1 hour sometimes :/
Be sure to hit the refresh button!


Add requirements

I just realize the requirements are already present here. In fact, for packages that are intended to be installed with pip, it is recommended to use the requirement syntax rather than the requirement file, per suggested here.


Handling large data

Is your feature request related to a problem? Please describe.
When I load a 4GB CSV file using read_csv, I see this:
File size<PHONE_NUMBER>) is greater than possible Buffer:<PHONE_NUMBER> bytes
Describe the solution you'd like
Handle larger data sets

I plan to work on these issue in the new version we are working on here #235

We added a couple of stream data processing functionality in the latest Typescript release. See: https://danfo.jsdata.org/api-reference/general-functions/danfo.streamcsvtransformer
If you need help migrating to the latest version, see: https://danfo.jsdata.org/examples/migrating-to-the-stable-version-of-danfo.js


Fixed crash on rationale click listener when using android.app.Fragment

My PR #61 introduced a crash in RationaleDialogClickListener when trying to cast Fragment host as FragmentActivity.
I did not have the time to fully test it but it should be the only regression.

@phcannesson can you reproduce this crash in version 0.3.0?  I don't think you should be able to get to the rationale dialog step for API < 23 but maybe there's a way around?

Yes I reproduced it when upgrading to 0.3.0.
mHost is android.app.Fragment and therefore the app crashes when trying to cast it as FragmentActivity.

@phcannesson oh I see now, I mixed up Fragment and FragmentActivity in my head.  Thanks!


Bazel Remote AWS S3

Description
I've deployed the bazel-remote in an EC2 instance in AWS using docker and here is the initial logs.
2022/06/09 00:56:44 bazel-remote built with go1.18 from git commit f774f6dc82c22540511241a3db58462898edc2be.
Using S3 backend.
2022/06/09 00:56:44 S3 Credentials: using AWS credentials file.
2022/06/09 00:56:44 Initial RLIMIT_NOFILE cur: 1048576 max: 1048576
2022/06/09 00:56:44 Setting RLIMIT_NOFILE cur: 1048576 max: 1048576
2022/06/09 00:56:44 mkdir /data/cas.v2: permission denied
2022/06/09 00:57:11 bazel-remote built with go1.18 from git commit f774f6dc82c22540511241a3db58462898edc2be.
2022/06/09 00:57:11 S3 Credentials: using AWS credentials file.
Using S3 backend.
2022/06/09 00:57:11 Initial RLIMIT_NOFILE cur: 1048576 max: 1048576
2022/06/09 00:57:11 Setting RLIMIT_NOFILE cur: 1048576 max: 1048576
2022/06/09 00:57:11 Loading existing files in /data.
2022/06/09 00:57:11 Sorting cache files by atime.
2022/06/09 00:57:11 Building LRU index.
2022/06/09 00:57:11 Finished loading disk cache files.
2022/06/09 00:57:11 Loaded 0 existing disk cache items.
2022/06/09 00:57:11 Authentication: disabled
2022/06/09 00:57:11 Mangling non-empty instance names with AC keys: disabled
2022/06/09 00:57:11 gRPC AC dependency checks: enabled
2022/06/09 00:57:11 experimental gRPC remote asset API: disabled
2022/06/09 00:57:11 Starting gRPC server on address :9092
2022/06/09 00:57:11 Starting HTTP server for profiling on address :6060
2022/06/09 00:57:11 Starting HTTP server on address :8080
2022/06/09 00:57:11 HTTP AC validation: enabled

Also when I visit the http://<ip>:9090/status link it outputs in the browser:
I guess same with the README.md
{
 "CurrSize": 0,
 "UncompressedSize": 0,
 "ReservedSize": 0,
 "MaxSize":<PHONE_NUMBER>,
 "NumFiles": 0,
 "ServerTime":<PHONE_NUMBER>,
 "GitCommit": "f774f6dc82c22540511241a3db58462898edc2be",
 "NumGoroutines": 624
}

I've created the S3 bucket before running the container and also set the permission of the bucket publicly.
Just asking why no files are being dumped into my S3? Also the storage of my EC2 instance doesn't go up.
Did I mess up somewhere? Is the remote caching working properly? Please enlighten me.
Thank you for any ideas you'll share.
Regards.

Btw, I forgot to add. I also added in my .bazelrc this:
--remote_cache=http://:9090

Here is the docker-compose.yml I'm using
version: "3"
services:
  bazel_cache:
    image: buchgr/bazel-remote-cache:v2.3.7
    user: "${UID}:${GID}"
    ports:
      - 9090:8080
      - 9092:9092
    network_mode: default
    container_name: bazel_cache
    volumes:
      - ./data:/data
      - $HOME/.aws:/aws-config
    environment:
      - BAZEL_REMOTE_S3_AUTH_METHOD=aws_credentials_file
      - BAZEL_REMOTE_S3_AWS_SHARED_CREDENTIALS_FILE=/aws-config/credentials
      - BAZEL_REMOTE_S3_BUCKET=onewallet-bazel-cache
      - BAZEL_REMOTE_S3_ENDPOINT=s3.eu-west-2.amazonaws.com
      - BAZEL_REMOTE_MAX_SIZE=20
volumes:
  data:
networks:
  default:
    external:
      name: bridge

No remote caching:

With remote caching

But the time has greatly decreased.

Hi, could you share some bazel-remote logs from when the cache is in use? There should be some s3 proxy backend log lines- maybe there's something relevant there.

Hello @mostynb , here is the actual logs from the CI.
2022/06/09 01:28:52 Downloading https://releases.bazel.build/4.2.1/release/bazel-4.2.1-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
DEBUG: Rule 'base_node' indicated that a canonical reproducible form can be obtained by modifying arguments digest = "sha256:07953ba81b5b2f34e36976db1869942016b7b8e0d8343283f2b114ee9a029891"
DEBUG: Repository base_node instantiated at:
  /home/circleci/project/WORKSPACE:76:15: in <toplevel>
Repository rule container_pull defined at:
  /home/circleci/.cache/bazel/_bazel_circleci/f16e36219ef33c22efc2ad20f3e3775c/external/io_bazel_rules_docker/container/pull.bzl:270:33: in <toplevel>
INFO: Invocation ID: f5b74fa7-db17-43c5-99a0-69649179d268
Loading:
Loading: 0 packages loaded
Analyzing: target //projects/wallet:image_push (0 packages loaded, 0 targets configured)
DEBUG: Rule 'base_node' indicated that a canonical reproducible form can be obtained by modifying arguments digest = "sha256:07953ba81b5b2f34e36976db1869942016b7b8e0d8343283f2b114ee9a029891"
DEBUG: Repository base_node instantiated at:
  /home/circleci/project/WORKSPACE:76:15: in <toplevel>
Repository rule container_pull defined at:
  /home/circleci/.cache/bazel/_bazel_circleci/f16e36219ef33c22efc2ad20f3e3775c/external/io_bazel_rules_docker/container/pull.bzl:270:33: in <toplevel>
Analyzing: target //projects/wallet:image_push (11 packages loaded, 27581 targets configured)
Analyzing: target //projects/wallet:image_push (12 packages loaded, 35405 targets configured)
INFO: Analyzed target //projects/wallet:image_push (12 packages loaded, 35408 targets configured).

INFO: Found 1 target...
[0 / 96] [Prepa] BazelWorkspaceStatusAction stable-status.txt ... (12 actions, 0 running)
[47 / 163] checking cached actions
[133 / 251] ImageLayer projects/wallet/image.1-layer.tar; 1s remote-cache, processwrapper-sandbox ... (29 actions, 28 running)
[169 / 251] ImageLayer projects/wallet/image.npm_deps-layer.tar; 1s remote-cache, processwrapper-sandbox ... (21 actions, 20 running)
[207 / 251] ImageLayer projects/wallet/image.npm_deps-layer.tar; 3s remote-cache, processwrapper-sandbox ... (23 actions, 22 running)
[223 / 251] ImageLayer projects/wallet/image.npm_deps-layer.tar; 4s remote-cache, processwrapper-sandbox ... (13 actions, 12 running)
[227 / 251] ImageLayer projects/wallet/image.npm_deps-layer.tar; 6s remote-cache, processwrapper-sandbox ... (8 actions running)
[230 / 251] GUNZIP external/base_node/image/004.tar.gz.nogz; 7s remote-cache, processwrapper-sandbox ... (7 actions, 6 running)
[235 / 251] Compiling TypeScript project //library/util:compile [tsc -p library/util/tsconfig.json]; 5s remote-cache, processwrapper-sandbox ... (4 actions running)
[236 / 251] GZIP projects/wallet/image.npm_deps-layer.tar.gz; 7s remote-cache, processwrapper-sandbox ... (6 actions running)
[240 / 251] [Prepa] Compiling TypeScript project //library/counter:compile [tsc -p library/counter/tsconfig.json]
[242 / 251] Compiling TypeScript project //library/serialcode:compile [tsc -p library/serialcode/tsconfig.json]; 2s remote-cache, processwrapper-sandbox ... (3 actions, 2 running)
[243 / 251] Compiling TypeScript project //library/jobs:compile [tsc -p library/jobs/tsconfig.json]; 6s remote-cache, processwrapper-sandbox
[244 / 251] Compiling TypeScript project //projects/wallet:compile [tsc -p projects/wallet/tsconfig.build.json]; 5s remote-cache, processwrapper-sandbox
[245 / 251] [Prepa] ImageLayer projects/wallet/image-layer.tar
Target //projects/wallet:image_push up-to-date:
  dist/bin/projects/wallet/image_push.digest
  dist/bin/projects/wallet/image_push
INFO: Elapsed time: 62.110s, Critical Path: 55.11s
INFO: 251 processes: 63 internal, 188 processwrapper-sandbox.
INFO: Build completed successfully, 251 total actions
INFO: Running command line: dist/bin/projects/wallet/image_push
INFO: Build completed successfully, 251 total actions

How can I check bazel-remote logs if I deployed it using docker?

Hi, those docker logs bazel_cache  -f logs are from bazel-remote, but I can't see any cache accesses. And this line at the end of your bazel log suggests that it's not using the bazel-remote cache: INFO: 251 processes: 63 internal, 188 processwrapper-sandbox.
How are you configuring bazel to tell it to use the bazel-remote cache?

Oh, if you're using --remote_cache=http://some-ip:9090 then I think that might be the problem, since bazel-remote is listening on port 8080 for http, not 9090.

9090:8080

Hello, from the docker-compose.yml file above. I exposed the port 8080 outside the container in port 9090.

If the /status page still shows "NumFiles": 0, then that means the cache doesn't have any files yet, and if there are no errors in bazel-remote's logs then I think bazel must be either misconfigured or there's a network level issue that prevents bazel from reaching bazel-remote.
This page has some notes about debugging this from the bazel side:
https://docs.bazel.build/versions/main/remote-caching-debug.html
Does adding --verbose_failures give any more useful information on the bazel side?

Thanks it is now working, and files are now being pushed into the S3 bucket and the logs in docker logs bazel_cache -f now shows files being uploaded and retrieved in the S3.
I refactored my .bazelrc
From this
--remote_cache=http://<IP_ADDRESS>:9090

To this
build --remote_cache=http://<some-ip>:9090
test --remote_cache=http://<some-ip>:9090
run --remote_cache=http://<some-ip>:9090

Sample logs
ubuntu@ip-172-31-26-1:~$ docker logs bazel_cache -f --tail 10
2022/06/15 00:53:50 S3 DOWNLOAD onewallet-bazel-cache ac/fc/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2 NOT FOUND
2022/06/15 00:53:50  GET 404 <IP_ADDRESS> /ac/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2
2022/06/15 00:53:50  PUT 200 <IP_ADDRESS> /cas/5dce6cbb4630750ed6e68f1e388f79fadaf840a821bd646b099e2f6dbd5db128
2022/06/15 00:53:50  PUT 200 <IP_ADDRESS> /cas/f1be8604a1ddc734d0e0dca79aacf083c513fe4c8287080c054b931d5a1d6776
2022/06/15 00:53:50  PUT 200 <IP_ADDRESS> /cas/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2
2022/06/15 00:53:50  PUT 200 <IP_ADDRESS> /ac/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2
2022/06/15 00:53:50 S3 UPLOAD onewallet-bazel-cache cas.v2/5d/5dce6cbb4630750ed6e68f1e388f79fadaf840a821bd646b099e2f6dbd5db128 OK
2022/06/15 00:53:50 S3 UPLOAD onewallet-bazel-cache cas.v2/f1/f1be8604a1ddc734d0e0dca79aacf083c513fe4c8287080c054b931d5a1d6776 OK
2022/06/15 00:53:50 S3 UPLOAD onewallet-bazel-cache cas.v2/fc/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2 OK
2022/06/15 00:53:51 S3 UPLOAD onewallet-bazel-cache ac/fc/fc99a20f1b8a6b467f6b6557ac47d5318a24a26151f2370c5d51e7b6b77e1ab2 OK

Glad to hear that you got it working :)

@rodentskie how were you able to make bazel-remote logs more verbose to show GET, PUT and download operations?


Automated actions on PR approval

Right now approving a PR automatically triggers the following actions:

google-ml-butler bot added kokoro:force-run ready to pull labels 11 minutes ago
@kokoro-team kokoro-team removed the kokoro:force-run label 9 minutes ago

Since GitHub is the source of truth for the codebase this is not necessary. The CI is already run anyway and doesn't need to be rerun after approval.

@fchollet - Currently the CI doesn't automatically run the "GPU" jobs.  Its only run after the PR is approved or when you manually add the "kokoro:force-run" label.  When user pushes multiple commits, it only runs the GitHub CI CPU jobs and not the GPU CI jobs until its reviewed.

Got it -- sure, that's fine. It wasn't clear to me.


test/evp_test.c: Add check for OPENSSL_strdup

As the potential failure of the OPENSSL_strdup(),
it should be better to check the return value and
return error if fails.
Signed-off-by: Jiasheng Jiang<EMAIL_ADDRESS>
Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

@paulidale please re-approve.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged.


x/tools/go/analysis/analysistest: adding a test file to test-data package breaks RunWithSuggestedFixes

Suppose you run analysistest.Run on a package with a test file (say to test test-specific behavior of the analyzer).  What apparently happens is that analysistest calls the analyzer once on the package without its tests, and once on the package with its tests.  This is not a big deal; you get some duplicate error messages.
But now suppose you instead run analysistest.RunWithSuggestedFixes.  In this case, analysistest ends up combining the fixes from both runs.  This means you get all your fixes applied twice, which surely doesn't match your .golden file!  it's a very confusing error.
A workaround is to change the test file to mypackage_test, such that the two runs will be entirely disjoint.

/cc @matloob


chore: remove pr template

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

why are you removing it?


Exposing rethinkdb instance

In the readme it has request.server.plugins['hapi-rethinkdb'].rethinkdb.  However in the code it does plugin.expose('library', rethink);
Not sure which is actually wanted.

Ugh, you're right, it should be rethinkdb.

Closed in df46c56adfc09dc634dfe00a1f1616c0a86c3c9d


Fix best params visualizer

Codecov Report

Merging #144 into master will decrease coverage by 0.18%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #144      +/-   ##
==========================================
- Coverage   57.17%   56.99%   -0.19%
==========================================
  Files          12       12
  Lines        1240     1244       +4
==========================================
  Hits          709      709
- Misses        531      535       +4

Impacted Files
Coverage Δ

src/plotting/utils.py
23.8% <14.28%> (-0.42%)
:arrow_down:

Continue to review full report at Codecov.

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


docs: clenup rerere and add translation for tools and components

Rerere is really inefficient and too complex to be used in a production environment, and I don't think it's a good solution for now. So delete it.
close https://github.com/ti-community-infra/tichi/issues/356

/lgtm

/merge


Create efos.txt

@euro1988 I am sorry for a delay with processing your request.
Pull request merged. Thank you!