Bluetooth: Gatt: Added write callback for gatt (un)subscribe

Added a callback that lets an application get write error (if any) when subscribing to a gatt characteristic.
Example scenario where this is required:
A GATT server has a notifiable and write-without-response characteristic with authorization. A client cannot write to this characteristic without being authorized, but since there are no response on the write, the client won't be informed about missing authorization. However, the CCCD of the characteristic shall support write (with response), and if the client subscribes, then it will also be prompted for authorization, and will receive this error message in the response.
Currently (before this patch) it is not possible for the application to get the needed error response.

The callback could also be changed to only be used in case of error.

The callback could also be changed to only be used in case of error.

I think I prefer it to have the same behavior as the write callback, which is called always.
The documentation for the write callback could be improved I think.
"Subscribe CCC write request response callback" maybe?

@joerchan Good idea to give a better description.
@Vudentz had some reservations regarding the addition of another callback in the sub params. Would definitely like his input here as well, and also if anyone else has some reservations about this addition? For the aforementioned scenario it is a requirement that the application gets the error response code, but there might also be other ways of adding that.

@Emil-Gydesen-Bose What other alternatives have you considered for how to get the error code?

@Emil-Gydesen-Bose What other alternatives have you considered for how to get the error code?

None that would really work. The only other alternative I can see, is to extend the bt_gatt_notify_func_t to include the error code (similar to bt_gatt_read_func_t), but I don't think it's a good alternative.

Ok. If it is a memory usage problem we could consider having the error in the subscription, I think it would fit into the struct padding without increasing the size. But it is a rather inelegant solution.
It would have been easier to extend the notify callback function arguments if it had been given a struct instead, which should be a lesson for the future. I have started to use that approach.
For now I would go with the write callback

It would have been easier to extend the notify callback function arguments if it had been given a struct instead, which should be a lesson for the future. I have started to use that approach.

I noticed - And I agree that it makes extending/updating APIs much easier (for both good and bad). I followed the same principle in my Periodic Advertising PR.

@Vudentz Any chance to get a review from you on this?

@Vudentz or @jhedberg This one has been open for a long time, should we continue with it?


Bump our fork to v1.25

We're first bumping our driver to upstream version v1.25, to then introduce a small modification to avoid race conditions when we try to modify both disk size and specs (IOPS, Throughput), making only a unified request to AWS API without having to deal with 6h cooldowns.
Issue
https://github.com/timescale/forge-issues/issues/1077

as I understand these are just the changes that happened in the repo between our release and the last release. And that this doesn't include any code that we had to control iops and throughput form the EBS driver itself.

Exactly, this is a 1:1 port of the version 1.25.


[1.16] Machines Does not working

DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE
**Industrial Foregoing Version: 3.2.11
**Titanium Version:<IP_ADDRESS>
Crashlog If Applicable (Upload to pastebin/gist):
Dissolution Chamber, Mob duplicator and Slimey Mycelial Generator machines eveni did give them power and everything but these machines does not working

-As you can see i did everything correctly but these machines doesn't working
-When i change redstone signal machine seems have energy but its still does not working and when i exit from ui and look again it seems empty again.
Mod Pack: FTB Presents Direwolf20 1.16

You arent using machines properly.

Slimey Generator needs slime to make power
Your Dissolution Chamber fluid is wrong
The Mob duplicator needs essence to run (The energy is just visual)

Please use discord for support, or just read the manual.


accelerator.prepare just can be run jus once ?

System Info
- `Accelerate` version: 0.28.0
- Platform: Linux-5.4.250-2-velinux1u1-amd64-x86_64-with-glibc2.29
- Python version: 3.8.10
- Numpy version: 1.21.0
- PyTorch version (GPU?): 2.2.0+cu118 (True)
- PyTorch XPU available: False
- PyTorch NPU available: False
- System RAM: 2015.16 GB
- GPU type: NVIDIA A100-SXM4-80GB
- `Accelerate` default config:
	Not found

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
I  write the code with accelerator.prepare more than once:
model, optimizer, train_dataloader,eval_dataloader= accelerator.prepare(
            model, optimizer, train_dataloader,eval_dataloader)
lr_scheduler= accelerator.prepare( lr_scheduler)

lr_scheduler.step() running is different with prepare once .
with once, with accelerator.accumulate(model): ,the lr_scheduler.step() will run num_processes times every step ,see code.
with twice prepare  and lr_scheduler prepare after.with accelerator.accumulate(model): ,the lr_scheduler.step() will run once every step.
with 2nd prepare with lr_scheduler,Is there some difference with with accelerator.accumulate(model):?
Expected behavior
The reasons for differences in coding type.

Hi @DavideHe, thanks for raising the issue. could you share a minimal reproducer ? The lr scheduler should behave the same when if the lr_scheduler is in the 2nd prepare. However, we expect the user to only use prepare once. What is the behavior you were expecting ? With accelerator.accumulate(model), the lr_scheduler is should be updated after every gradient_accumulation_steps iteration. See related issue https://github.com/huggingface/accelerate/issues/963

prepare twice
model, optimizer, train_dataloader,eval_dataloader= accelerator.prepare(
            model, optimizer, train_dataloader,eval_dataloader)
lr_scheduler= accelerator.prepare( lr_scheduler)
for data in train_dataloader:
    with accelerator.accumulate(model):
        lr_scheduler.step()
        print(lr_scheduler.get_last_lr()[-1])

as the code above, the lr will update every step when gradient_accumulation_steps > 1.
But prepare once ,  lr will update every gradient_accumulation_steps  step.


Salmon error with spikein_fasta and no mapable reads/alpha too low

When using a spikein_fasta, a separate salmon index is generated for the spike-ins. This may lead to no mapable reads, for instance in cases of viral spike-in definitions and no viral nucleotides in the sample.
First, the index is being built:
[2017-04-04T14:42Z] kmersize used for salmon index at spikein quant: 31
[2017-04-04T14:42Z] Creating Salmon index for /bcbio/spikeins/ercc_hpv.fa.
[2017-04-04T14:42Z] Version Info: This is the most recent version of Salmon.
[2017-04-04T14:42Z] index ["/tissue_normals/tox_normals_human_wts_01/expression_analysis_01/bcbiotx/tmpKZ8uGV/index"] did not previously exist  . . . creating it
[2017-04-04T14:42Z] [2017-04-04 14:42:42.804] [jLog] [info] building index
[2017-04-04T14:42Z] RapMap Indexer
[2017-04-04T14:42Z]
[2017-04-04T14:42Z] [Step 1 of 4] : counting k-mers
[2017-04-04T14:42Z] Elapsed time: 0.0819993s
[2017-04-04T14:42Z]
[2017-04-04T14:42Z] Replaced 5 non-ATCG nucleotides
[2017-04-04T14:42Z] Clipped poly-A tails from 95 transcripts
[2017-04-04T14:42Z] Building rank-select dictionary and saving to disk done
[2017-04-04T14:42Z] Elapsed time: 7.1279e-05s
[2017-04-04T14:42Z] Writing sequence data to file . . . done
[2017-04-04T14:42Z] Elapsed time: 0.000302414s
[2017-04-04T14:42Z] [info] Building 32-bit suffix array (length of generalized text is 363141)
[2017-04-04T14:42Z] hits: 0; hits per frag:  0ESC[A^MESC[32mprocessedESC[31m 1000000 ESC[32mfragmentsESC[0m
[2017-04-04T14:42Z] Building suffix array . . . success
[2017-04-04T14:42Z] saving to disk . . . done
[2017-04-04T14:42Z] Elapsed time: 0.000882228s
[2017-04-04T14:42Z] done
[2017-04-04T14:42Z] Elapsed time: 0.139511s
[2017-04-04T14:42Z] hits: 0; hits per frag:  0ESC[A^MESC[32mprocessedESC[31m 6000000 ESC[32mfragmentsESC[0m
[2017-04-04T14:42Z] ^Mprocessed 0 positions
[2017-04-04T14:42Z] khash had 352211 keys
[2017-04-04T14:42Z] saving hash to disk . . . done
[2017-04-04T14:42Z] Elapsed time: 0.0332711s
[2017-04-04T14:42Z] [2017-04-04 14:42:43.624] [jLog] [info] done building index

Then, salmon quant complains since no mapable reads were found (and/or alpha was chosen too small):
[jointLog] [info] parsing read library format
[info] There is 1 library.
[stderrLog] [info] Loading Suffix Array
[jointLog] [info] Loading Quasi index
[jointLog] [info] Loading 32-bit quasi index
[stderrLog] [info] Loading Transcript Info
[stderrLog] [info] Loading Rank-Select Bit Array
[stderrLog] [info] There were 278 set bits in the bit array
[stderrLog] [info] Computing transcript lengths
[stderrLog] [info] Waiting to finish loading hash
[jointLog] [info] done
[jointLog] [info] Index contained 278 targets
[stderrLog] [info] Done loading index
[jointLog] [info] Computed 0 rich equivalence classes for further processing
[jointLog] [info] Counted 0 total reads in the equivalence classes
[jointLog] [warning] Only 0 fragments were mapped, but the number of burn-in fragments was set to 5000000.
[jointLog] [info] Mapping rate = 0%
[jointLog] [info] finished quantifyLibrary()
[jointLog] [info] Starting optimizer
[jointLog] [info] Marked 0 weighted equivalence classes as degenerate
[jointLog] [info] iteration = 0 | max rel diff. = 0.471689
[jointLog] [info] iteration = 50 | max rel diff. = -1.79769e+308
[jointLog] [error] Total alpha weight was too small! Make sure you ran salmon correclty.
[jointLog] [error] The optimization algorithm failed. This is likely the result of bad input (or a bug). If you cannot track down the cause, please report this issue on GitHub.
returned non-zero exit status 1

Obviously, the desired behavior is that salmon does not error out but completes processing and assigns zero quantitations to all spike-in features. @roryk, is that something we could deal with here or should I report this upstream?

Hi Sven-Eric,
Thanks for the great bug report. Upstream might be a better plan-- if he is slow about fixing it, we could catch it on our end too. I think we'd have to catch the error and then inspect the log file to see if it is because there aren't any fragments mapping.

Issue raised with salmon here

Thanks!

Fixed, I believe - closing.

Thank you!


figma done

Lets merge it as it is, but consider that we need to add all the improvements we discussed in Slack to show icons without searching and consume the API for searching icons


Broadcast a timer signal

It won't be perfectly in sync, but even something approximate is pretty useful. The timer should get better controls though.

fixed there ^


Social media buttons not functional,

Describe the bug
social media icons in the footer are not responsive
To Reproduce
Steps to reproduce the behavior:

Go to 'homepage'
Click on 'social media icon'
Scroll down to 'bottom'
See error

Expected behavior
It must open social media pages
Screenshots
It redirects to the homepage
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
also footer should be added to each page as it enhances the site.

Assign me this issue I am a Gssoc'23 Contributor

i would like to work on this issue as an GSSOC ccontributor just give me the social media id if it is made.

Hi I do like to contribute, just provide me with the social media accounts url. Assign me under the GSSoC23 label

I am interested to work on this issue under GSSoC 2023 as a contributor


Exercise # 3 doesn't pass

Hi
Exercise # 3 works fine on localhost:8080. When I click on the 'WhatsYourName' tab I get the message "Hey there. Enter your name." with an empty form field beneath that. And when I enter something in the form then the initial message goes away and the new input shows up. I gather that's the expected outcome.
But it doesn't pass the test. I get the following on my terminal -
03 - What's Your Name?
    should complete all tasks
      Task #1 - greet user
        1) Should change name in paragraph on name change in input

  3 passing (64ms)
  1 failing

  1) 03 - What's Your Name? should complete all tasks Task #1 - greet user Should change name in paragraph on name change in input:

      AssertionError: After changing name in input, I should see the change in `p` element's content. In other words: `this.state.name` should change.
      + expected - actual

      -false
      +true

      at Context.<anonymous> (test/03-WhatsYourName.js:36:16)

Here is my code -
var React = require("react");

// Let's get to the most important feature of React.js - reactive state.
//
// Each React component contains 2 important hashes:
// * Properties - we pass these values when we create a component. They don't
//                change during the component's lifecycle.
// * State      - these values can change over entire life of the component.
//                When you change some value in `state` object, React will
//                re-calculate the `render` method and update the HTML to match
//                the new state (in this case, updating the class).
//
// You can pass properties to components using JSX attributes. You did it in
// the last exercise! See the example below.
//
// ```
// <div className="example-class" attr1="ugabuga">[...]</div>
// ```
//
// We created `React.DOM.div` component with properties:
// `{className: "example-class", attr1: "ugabuga"}`
//
// You have two tasks to complete in this exercise:
// Task #1: Someone left broken code in the `onNameChange` method. It is always triggered
//          after changing the value of `name` input. This method takes
//          event as its only argument. You need to retrieve the input value from
//          that object and update the `name` field in the `state` object.
// Warning: Do not try to change the `render` structure.
//
// Task #2: If there is no name given, we should display a message encouraging
//          the user to insert their name.
//          Display text: "Hey there. Enter your name." if name.length is 0.
//
//          Hint: Use temporary variables to achieve the goal. See the example below.
//          ```
//          render() {
//            var numberToDisplay;
//            if (this.state.number > 9000) {
//              numberToDisplay = "IT'S OVER 9000!";
//            } else {
//              numberToDisplay = this.state.number;
//            }
//            return(
//              <span>{numberToDisplay}</span>
//            )
//          ```
//
// Further reading on task #2: https://facebook.github.io/react/tips/if-else-in-JSX.html

class WhatsYourName extends React.Component {
  // By default `this.state` is `null`. In `render` we are referring to
  // a specific element from the `state` object - `this.state.name`.
  // If we don't set an initial state, we will get an error. It's impossible to fetch
  // an object key from `null`.
  //
  // Think about it: you can set name from a cookie on component initialization!
  //                 What else could you do here?

  constructor(props) {
    // Properties object is called `props`. You can access it with `this.props`.
    // We won't use it in this exercise.
    super(props);
    this.state = { name: "" };

    // Warning! If we don't bind this method - we would not be able to update state.
    this.onNameChange = this.onNameChange.bind(this);
  }

  // `event` is the only argument passed to that method. It will be an event
  // object thrown by React on actions like `click`, `change` etc.
  //
  // You need to correct the call of `setState` method. Just try to set
  // the `name` field to the value passed in event.
  //
  // Hint: use `console.log` to check `event.target`. You will find text
  //       entered to the input there.
  onNameChange(event) {
    // Huh... There's something wrong here...
    this.setState({name: event.target.value});

  }

  render() {
    **var nameToDisplay;
    if (this.state.name.length == 0) {
      nameToDisplay = "Hey there. Enter your name.";
    } else {
      nameToDisplay = this.state.name;
    }
    return (

{nameToDisplay}

        <input type="text" name="name" onChange={this.onNameChange} />

**
    );
  }
}

// Notice some details here:
//   1. `onChange` attribute isn't placed between `" "`, but `{ }` - we want to
//      reference function, not string.
//   2. You must be very careful on methods binding. You can do it in the constructor.
//   3. `state` object is `null` by default! If you want to display initial
//       value from state object, you should initialize state object.

// ProTip: Always specify input's `name` attribute: React uses it to identify
//         inputs on page. Not doing so may cause you to waste a long time
//         debugging your program.

export default WhatsYourName;

Something is missing from the input attributes. It is not connected to the state variable anyhow.
Here's a link to docs that can shed some light on this issue: http://facebook.github.io/react/docs/forms.html#controlled-components


Enhances spo commandset set, Closes #4963

Closes #4963

Thank you for another awesome PR. We will review it ASAP

Merged manually, thank you! 👏


requirements: Upgrade 'Django'

Upgrade Django 2.2.21 -> 2.2.24 with fixes to some known vulnerabilities

CVE-2021-33571
CVE-2021-33203

Codecov Report

Merging #224 (22224a4) into develop (07c2b18) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #224   +/-   ##
========================================
  Coverage    81.02%   81.02%
========================================
  Files           32       32
  Lines         2525     2525
  Branches       375      375
========================================
  Hits          2046     2046
  Misses         306      306
  Partials       173      173

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 07c2b18...22224a4. Read the comment docs.


HTTP status code is always 200 with batching enabled

Version
4.0.0
Summary
With batching enabled the reported http status code is always 200 no matter what the server returns.
Steps to reproduce the behavior
No response
Logs
Correct with batching disabled (default):
HTTP: 401
content-type: application/json; charset=utf-8
transfer-encoding: chunked
[end of headers]

Wrong with batching enabled:
HTTP: 200
content-type: application/json; charset=utf-8
transfer-encoding: chunked
[end of headers]

Actually the problem is that yoga always returns 200s.


Add load_object function for R

Expose the load_object function on the QlibRecorder level :)
How Has This Been Tested?

[x] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.

Types of changes

[x] Add new feature

@D-X-Y Thanks so much!


Infer the community repo from the main repo URL

I haven't been able to test this yet so can you test against your Alpine instance please

Actually I had a VM I tested this on and it seemed to work a treat. Aside from code formatting I'm going to call this working and ready to merge

Many Thanks 👍  Good old coreutils wizardry at work!


Linked eigen3 to target board

The implementation of the new mixing system depends on Eigen. It doesn't use any dynamically allocated memory, so it should be fine to run on the microcontroller. I suspect Eigen will be useful in the future as we develop a mixing system for ROSvtol.

Do we want to delete this dead branch?

We don't need to add eigen as a dependency to the varmint board, as eigen is only used in the core rosflight library. The build workflows in this use a dummy class in place of the actual rosflight_firmware, so no eigen is involved.

I did this because pushing the new mixer updates in the rosflight_firmware that require Eigen were not building unless I linked Eigen to the targets. @bsutherland333 maybe you can show me the correct way to add that dependency to the firmware?

@JMoore5353 you would do the same thing you did here, but in the rosflight_firmware repository. varmint_h7 would be unchanged.

Can you add them to the rosflight_firmware/CMakeLists.txt ?
From: Jacob Moore @.>
Sent: Tuesday, August 27, 2024 8:45 AM
To: rosflight/varmint_h7 @.>
Cc: Phillip Tokumaru @.>; Comment @.>
Subject: Re: [rosflight/varmint_h7] Linked eigen3 to target board (PR #9)
CAUTION: EXTERNAL EMAIL This email originated from outside of AeroVironment. Do not click links or open attachments unless you recognize the sender and know the content is safe.
We don't need to add eigen as a dependency to the varmint board, as eigen is only used in the core rosflight library. The build workflows in this use a dummy class in place of the actual rosflight_firmware, so no eigen is involved.
I did this because pushing the new mixer updates in the rosflight_firmware that require Eigen were not building unless I linked Eigen to the targets. @bsutherland333https://urldefense.us/v3/__https:/github.com/bsutherland333__;!!Il-_odoO6SshVRgBiFsQfA!TTYgDLZRMFzE8-kluxBBx9tfFebdBMnSiabLu9Ih4zC5bZJQUuIkUixKDuZo90ocZGH4JDwRkilAsl4dTvNbYKQ$ maybe you can show me the correct way to add that dependency to the firmware?
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/rosflight/varmint_h7/pull/9*issuecomment-2312920941__;Iw!!Il-_odoO6SshVRgBiFsQfA!TTYgDLZRMFzE8-kluxBBx9tfFebdBMnSiabLu9Ih4zC5bZJQUuIkUixKDuZo90ocZGH4JDwRkilAsl4d48VVoLY$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/ANMGW5OJ5AMT3NPSTSZ2LDTZTSNJRAVCNFSM6AAAAABMS7ASM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSHEZDAOJUGE__;!!Il-_odoO6SshVRgBiFsQfA!TTYgDLZRMFzE8-kluxBBx9tfFebdBMnSiabLu9Ih4zC5bZJQUuIkUixKDuZo90ocZGH4JDwRkilAsl4d4hBAFaY$.
You are receiving this because you commented.Message ID: @.***>

Sounds good. I got it figured out in the rosflight_firmware/CMakeLists.txt. Thanks for the help.


Updated README with servers.json instructions

@RocketChat/core
This should help a few people, Figured it out on my own and want to share it with everyone.
Super helpful in large deployments.

Thanks Alex! Formatting isn't a strong area of mine haha
On 10 Apr. 2017 7:52 am, "Alex Brazier"<EMAIL_ADDRESS>wrote:

@alexbrazier approved this pull request.
Thanks for the PR, just made a minor change to it. 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RocketChat/Rocket.Chat.Electron/pull/415#pullrequestreview-31735401,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1QDxVeuPyYLBLvAgQ9Fvsn-kZ0KWenks5ruVMfgaJpZM4M3p0G
.


Add AWS IAM stuff

[ ] kube2iam
[ ] kiam
[ ] [aws-iam-authenticator](https://github.com/kubernetes-sigs/aws-iam-authenticator

Migrated to https://github.com/uniget-org/tools/issues/57


[WIP] ci: Add weekly test workflow file

Runs lint, unit and functional tests at specified time weekly. If the test fails, the pre-configured Mattermost channel is notified with a message.
In order to understand the changes better, take a look at the runs in "Weekly Tests" action  in the dashmage/charm-local-users project.
Run with test passing
Run with test failing and Mattermost channel being notified
The above POC was configured with a webhook from my Mattermost user which would create a message like this:

Helpful references:

failure() status check function
Mattermost notify action
schedule event to trigger workflow

Note: Status is WIP because we are still waiting for the Mattermost bot account through which we can create the webhook and add the MATTERMOST_WEBHOOK_URL secret`.

Closing this PR since we're going ahead with the approach where all the tests are triggered from a single workflow


fix(helper): update vue 2 template and helper

What?
This PR updates the vue 2 template. Vue 2 helper + template used to have provider / inject pattern, and now that we've removed it, there is no such thing as useFieldPlugin in the vue 2 helper and the template. So what if we just remove vue 2 helper at all? We just need a little bit of snippet in the vue 2 template, and we're not actively supporting vue 2 anyway.
Why?
JIRA: EXT-1958

How to test? (optional)

Current dependencies on/for this PR:

main

PR #260

PR #266

PR #267

PR #269

PR #270   👈

This comment was auto-generated by Graphite.

@eunjae-lee, I think removing all the vue2 helper would not be bad, IMO.
However, how should we handle the FieldPlugin file?
I think we could remove this file since it seems not to be used anyway. what do you think?

@demetriusfeijoo if we get rid of vue 2 helper, then we should actually delete this folder, but I didn't yet because we haven't decided yet.
And actually that empty FieldPlugin.vue file is a placeholder for users. We provide an example inside the template, but users can delete the whole example and start from scratch with the FieldPlugin.vue file (which is bare minimum)

And actually that empty FieldPlugin.vue file is a placeholder for users. We provide an example inside the template, but users can delete the whole example and start from scratch with the FieldPlugin.vue file (which is bare minimum)

Oh, I see @eunjae-lee.
I think once we stop using the FieldPluginProvider inside the template, we can remove also the helper, for sure.
This way we avoid some developers using it and blocking us from removing it easily in the future?!
I mean, I was checking here, and after removing the FieldPluginProvider we would have anything else to offer from the helper, right? As we're not going to support this version, maybe the best way would be to remove the helper, indeed.
I was taking a better look at how the new approach would look and I started asking myself on how to make the logic below reusable between both FieldExample/index.vue and FieldPlugin.vue files.

Do you have any idea here? As we don't have hooks here (for useFieldPlugin()), may we use Vue mixins?!
What do you think @eunjae-lee?

Do you have any idea here? As we don't have hooks here (for useFieldPlugin()), may we use Vue mixins?! What do you think @eunjae-lee?

@demetriusfeijoo hey, thanks for pointing this out. I forgot about this part. added https://github.com/storyblok/field-plugin/pull/270/commits/539f5d24732db7c92a87174d9ec9be9bb5f14d05

Hey @eunjae-lee, thanks for the adjustment. 🙌
What about getting rid of the helper? Do you have a better position on that?

Merge Activity

Sep 14, 10:27 AM: @eunjae-lee started a stack merge that includes this pull request via Graphite.


De-duplicate dockcross scripts by sourcing common code

This PR de-duplicates dockcross scripts by moving all common code to a separate file and sourcing it from each script.

Those are generated by dockcross images, everytime we will update the dockcross image they would be regenerated.


Add containerStyle prop to TabViewAnimated

First off, thank you for this project, it's great!
I've run into this issue with having to overwrite the default styles.container style that is used in TabViewAnimated's _renderItems() function. I am using it as a carousel that's inline with other content, and does not need to be full height. I can pass a height to the component, but in my case, I'd rather have the content dictate the height and pass { flexGrow: 0 }.
Would love some feedback!

I think it'll be better to get rid of the wrapping view. We can just return an array and the styles we have for the wrapping view in TabViewTransitioner

That sounds like a much cleaner solution. Nice to get rid of unnecessary Views.
My guess is that it would look something like this?
return [
  renderHeader && renderHeader(...),
  renderPager(...),
  renderFooter && renderFooter(...),
]

What would be the best way to handle keys?
If you passed it: renderHeader && renderHeader({...props, key: 'header'}), that would require the renderHeader function to either always spread props or explicitly pass the key<TabHeader key={props.key} />, correct?

Yeah.
I think renderHeader({...props, key: 'header'}) looks fine.

Thinking about this a little more. The renderHeader({...props, key: 'header'}) approach would give users pretty ambiguous errors if they did not pass the key down:
Each child in an array or iterator should have a unique "key" prop.
Check the render method of `TabViewTransitioner`

☝ This would be the error if a user's renderHeader function looked like this:
renderHeader(props) {
  const { index, routes } = props.navigationState
  return (
    <TabHeader
      routes={routes}
      currentIndex={index}
    />
  )
}

Kind of a weird side affect of this abstraction and might not be the most obvious warning for users unless it was documented

There are several ways to solve this issue,

We can manually add the key using React.cloneElement
Instead of using an array in TabViewTransitioner, refer them like {items[0]} etc.
Remove the wrapping view in TabViewTransitioner, something like,

return this.props.render({ ...this._buildSceneRendererProps(), onLayout: this._handleLayout });

I'm not too worried about it right now because TabViewTransitioner will be removed pretty soon when https://github.com/react-native-community/react-native-tab-view/tree/native-animation is ready

Alright thanks! I'm stoked for the native animation.
I'll close this Pull Request, and see if I can help make any progress on what you have suggested.


Send a response body in defaultFailureHandler

Fixes issue https://github.com/justinas/nosurf/issues/41.

Thank you!


Is this project active?

Hi all.
I want to help, but I want to know if this project is active. Is this project active?

Hey @codehangen , sorry for the delay, most of us have been on holiday the past few weeks & just getting back. This project is still active in that it is being used in several project, however, from a development side of things it is mostly in maintenance mode.


"unknown climatization state" with auxiliaryHeating

Hi all,
when my auxiliaryHeating is running, the status of /domains/climatisation/auxiliaryHeatingStatus/climatisationState is "unknown climatization state". When the auxiliaryHeating is off, the status also is "off".
Regards

What is the log telling?

Okay, got it, here we go:
2024-03-05T14:35:38+0100:WARNING:timer:/vehicles/XXXXXX/domains/climatisationTimers/auxiliaryHeatingTimersStatus/timers/1/recurringTimer: Unknown attribute startTimeLocal with value 08:30
2024-03-05T14:35:45+0100:WARNING:generic_status:/vehicles/XXXXXX/domains/climatisation/climatisationSettings: Unknown attribute auxiliaryHeatingSettings with value {'duration_min': 30}
2024-03-05T14:35:45+0100:WARNING:addressable:/vehicles/XXXXXX/domains/climatisation/auxiliaryHeatingStatus/climatisationState: An unsupported climatisationState: heatingAuxiliary was provided, known values are [off, heating, cooling, ventilation, invalid, unknown climatization state] please report this as a bug
2024-03-05T14:35:45+0100:WARNING:timer:/vehicles/XXXXXX/domains/climatisationTimers/auxiliaryHeatingTimersStatus/timers/1/recurringTimer: Unknown attribute startTimeLocal with value 08:30
2024-03-05T14:35:51+0100:WARNING:generic_status:/vehicles/XXXXXX/domains/climatisation/climatisationSettings: Unknown attribute auxiliaryHeatingSettings with value {'duration_min': 30}
2024-03-05T14:35:51+0100:WARNING:addressable:/vehicles/XXXXXX/domains/climatisation/auxiliaryHeatingStatus/climatisationState: An unsupported climatisationState: heatingAuxiliary was provided, known values are [off, heating, cooling, ventilation, invalid, unknown climatization state] please report this as a bug

Thanks, will work on these!


Update use-microsoft-365-cdn-with-spo.md

to reduce ambiguity removed the Germany cloud as it has been retired - https://www.microsoft.com/en-us/cloud-platform/germany-cloud-regions#:~:text=A%3A On October 29%2C 2021,in Europe before this time.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8941

@kelleyvice-msft Please merge this PR. Thanks


Correct cancel-your-account.md

The cancellation button has been moved to the "Your Products" tab under "Account Details"

Kenneth Wilson
Twilio SendGrid Support Supervisor

Description of the change: Changing the path from "Plan & Billing" to "Your Products" in order to cancel account
Reason for the change: Current path is incorrect
Link to original source:https://sendgrid.com/docs/ui/account-and-settings/cancel-your-account/

Closes #

Hello @Kenneth-Wilson,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


EGS Achievement support using Legendary client

Any chance of being able to import Epic achievements while using the open-source alternative client Legendary?

Global job progress queue #2487


No steps for CI/CD for bot deployment using Azure Devops?

[Enter feedback here]
I get you're going all in on GitHub, (which is great!) but would be helpful to either have some AzDo pipeline/release notes here (ideally an example) or a link to a relevant area if it exists (and not just the pipeline/release docs).

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

ID: 1e9b10d5-ca65-d08c-2f11-ba62d66b8f80
Version Independent ID: 396d52c0-d864-afac-4d1c-fd6880a973a9
Content: Configure continuous deployment for Bot Service - Bot Service
Content Source: articles/bot-service-build-continuous-deployment.md
Service: bot-service
GitHub Login: @ivorb
Microsoft Alias: kamrani

Unfortunately, we don't have a good way to provided examples for more than one or two scenarios. In the Additional resources section, there's a link to continuous deployment to Azure App Service. Is that the sort of information you are looking for?


the problem   of  navigator component in react-native which version is 0.39.2

I face a problem
Description
when I use the navigator component in my app like this:
 <Navigator
                initialRoute={{ params: { name: 'Home页面' }, component: HomeView }}
                configureScene={(route) => {
                    if (route.sceneConfig) {
                        return route.sceneConfig
                    }
                    return Navigator.SceneConfigs.FloatFromBottom
                } }
                renderScene={(route, navigator) => {
                    let Component = route.component;
                    return <Component navigator={navigator} />
                } }
                />

but I get an error is that the Component doesn't has property of navigator, and the route component extends the  React.ComponentClass,but the React.ComponentClass also has no navigator property
is the version of react-native wrong,How can I resolve it ?

I resolved it by myself, just because the homeView does not declare the navigator property


Chrome helper spiking when file reloads

Not 100% if this belongs here or in webpack-dev-middleware, but when developing and my bundle is pushed to chrome I am seeing my Chrome Helper jump up to 100% CPU and remain there.
I have used the Chrome task manager to isolate that it is the tab that I am working with, and that it does not happen until that bundle is pushed. If I close my tab and open it again, the problem goes away until my code updates again.
Here is where I set up webpack. I read about the webpack watcher causing issues without fsevents installed, but I have that and am still seeing the problem. Also, that issue was with the node/gulp process running high, not chrome.
  configureWebpack() {
    // sets up webpack to hot load my modules
    const compiler = webpack(config);
    this.webpackMiddleware = webpackMiddleware(compiler, {
      publicPath: config.output.publicPath,
      contentBase: 'src',
      stats: {
        colors: true,
        hash: false,
        timings: true,
        chunks: false,
        chunkModules: false,
        modules: false,
      },
    });

    this.use(this.webpackMiddleware);
    this.use(webpackHotMiddleware(compiler));
  }

I have also run a few tests in safari, and am not seeing anything jump in CPU.
Anyone run into this?

Nevermind - seems to be resolved if I remove my livereload chrome extension. Something is conflicting there and causing issues. Closing this


SSL Verification Failure when using lumberjack to send to another logstash instance

I'm running into an issue where the logstash-output-lumberjack plugin is failing to verify an SSL certificate.   I believe this is a bug, since both logstash-forwarder and openssl successfully verify the SSL certificate using the same CA file as logstash.
Environment:

RedHat 6.7
Logstash 1.5.4 (all plugins updated)
logstash-output-plugin 1.0.2
Java <IP_ADDRESS>

Logstash Sever config snippet:
lumberjack {
    port => 5000
    ssl_certificate => "/etc/pki/tls/certs/sever.cert"
    ssl_key => "/etc/pki/tls/private/server.key"
}

Logstash Client config snippet
lumberjack {
    hosts => ['server.fqdn']
    port => 5000
    ssl_certificate => "/etc/pki/tls/certs/logstash.ca"
    codec => json { }
}

Here is the error I get in logstash.log:
All hosts unavailable, sleeping {:hosts=>["X.X.X.X"], :e=>#<OpenSSL::SSL::SSLError: certificate verify failed>,

As mentioned above, both logstash-forwarder and openssl have no issues verifying the certificate.
logstash-forwarder config snippet:
{
  "network": {
    "servers": [ "server.fqdn:5000"],
    "ssl ca": "logstash.ca",
    "timeout": 15
  },

and when run, I get this output:
$ /usr/local/bin/logstash-forwarder --config test.json
2015/09/01 14:03:02.579180 Setting trusted CA from file: logstash.ca
2015/09/01 14:03:02.583387 Connecting to [X.X.X.X]:5000 (server.fqdn)
2015/09/01 14:03:02.643339 Connected to X.X.X.X
2015/09/01 14:03:04.204200 Registrar: processing 1024 events
...

OpenSSL verification
$ openssl verify -CAfile logstash.ca server.cert
server.cert: OK

Note:  server.crt is a SAN certificate and is valid for both the server.fqdn as well the server's IP address.

having similar issue when update the output to logstash 1.5-6.
Lumberjack output => Lumberjack Input
LS (1-4.5 ) => LS (1.4-5 ) Ok
LS (1-4.5 ) => LS (1.5-6 ) OK
LS (1-5.6 ) => LS (1.5-6 )  FAIL
LS (1-5.6 ) => LS (1.4-5 ) FAIL

issue seems to be related to Lumberjack/client
private
def connection_start(opts)
tcp_socket = TCPSocket.new(opts[:address], opts[:port])
if !opts[:ssl]
@socket = tcp_socket
else
certificate = OpenSSL::X509::Certificate.new(File.read(opts[:ssl_certificate]))
    certificate_store = OpenSSL::X509::Store.new
    certificate_store.add_cert(certificate)

    ssl_context = OpenSSL::SSL::SSLContext.new
    ssl_context.verify_mode = OpenSSL::SSL::VERIFY_PEER
    ssl_context.cert_store = certificate_store

    @socket = OpenSSL::SSL::SSLSocket.new(tcp_socket, ssl_context)
    @socket.connect
  end
end

Changing to "VERIFY_NONE" makes it happy for now ( obviously )
https://github.com/elastic/ruby-lumberjack/blob/master/lib/lumberjack/client.rb#L91
I'm checking the Ruby Openssl to see what can be done

I am also experiencing this issue

Same here

We also experience this issue.  need to be able to support self signed certs via https://github.com/logstash-plugins/logstash-output-lumberjack/pull/18 so that we don't have to hack around this.

on the same boat.
I was thinking to add our CA to the system CA certs bundle, but I'm not sure which one is used by JRuby
Did anyone find a solution?

This may be confusing, but my reading of the code (ruby-lumberjack, etc) makes me believe the ssl_certificate setting is the one that is used today, without code changes, for validating the server.
https://github.com/plarivee/ruby-lumberjack/blob/master/lib/lumberjack/client.rb#L90-L91
We set OpenSSL::SSL::SSLContext.cert_store, and this is used for certificate verification.
My guess is to try setting ssl_certificate to the path containing the necessary data to validate your server (logstash beats input?).

@jordansissel I think I tried everything I could.

use the client cert in ssl_certificate
use the ca file in ssl_certificate
bundle the ca file and client together and use that as ssl_certificate
adding the ca to ${JAVA_HOME}/jre/lib/security/cacerts with keytool (on both "client" and "server")

And no, I'm not using lumberjack to receive files from filebeat because that doesn't work either (regardless of SSL). So I'm using filebeat to forward files to a local logstash which then communicates with a remote logstash via lumberjack (so I'm using the additional plugin logstash-lumberjack-output on the shipper)

I think that is why i implemented the ca cert since bundling ca cert + cert
wasnt working
Pascal Larivée
Photographe
lariveephoto.com
On Dec 3, 2016 10:14, "Elisiano Petrini"<EMAIL_ADDRESS>wrote:

@jordansissel https://github.com/jordansissel I think I tried
everything I could.

use the client cert in ssl_certificate
use the ca file in ssl_certificate
bundle the ca file and client together and use that as
ssl_certificate
adding the ca to ${JAVA_HOME}/jre/lib/security/cacerts with keytool
(on both "client" and "server")

And no, I'm not using lumberjack to receive files from filebeat because
that doesn't work either (regardless of SSL). So I'm using filebeat to
forward files to a local logstash which then communicates with a remote
logstash via lumberjack (so I'm using the additional plugin
logstash-lumberjack-output on the shipper)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-output-lumberjack/issues/11#issuecomment-264644853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD0hpQ6DrtF87cE3WClc06oewmQnmzXwks5rEYc5gaJpZM4F2GBB
.

@plarivee can you clarify how you got it working (without modifying ruby code)?
I'm also using a CA (I'm leveraging Puppet's CA for that).

@elisiano Well i did modify code and submited a pull request (check earlier in the code )  this was to add support for the ca_cert option,
else you could set verify_none  in the code also, but defeats security

@plarivee thanks for the clarification, now I start to put all the pieces together.
In theory though, this setup should work even if we add our custom CA to the cacerts that logstash uses:
# rpm -ql logstash|grep cacert
/usr/share/logstash/logstash-core/lib/logstash/certs/cacert.pem
# (echo -e "\nPuppetCA\n========" && cat /var/lib/puppet/ssl/certs/ca.pem ) >> /usr/share/logstash/logstash-core/lib/logstash/certs/cacert.pem
# systemctl restart logstash.service

But even that didn't work for me (added on both logstash instances).
@jordansissel: just out of curiosity, is there any reason why the PR of @plarivee wasn't merged?

Are you still having this issue with the latest logstash? we havent updated our log infra in the last year, thats why I havent pushed.more, thinking it might be solved now

Yes, I'm running the latest:
# rpm -q logstash
logstash-5.0.2-1.noarch

On line 84 of lib/logstash/outputs/lumberjack.rb, hostnames are converted to IP address before creating a new Lumberjack::Client, which then performs the connection and verifies the SSL cert.
Doesn't this guarantee an SSL failure unless you have an IP: entry in the SAN for the SSL cert?

@mqa-mouser did you ever figure this out? I'm questioning the same thing, as I'm recently trying to get logstash -> logstash working with lumberjack output to beats input

I just found this bug doing a search after trying to debug this exact same issue the last couple of hours. We were also down to the source code to find out that it would probably never work because there is no way the correct CA can be selected.
@jordansissel can you verify that your pull request fixes this issue?
If that is the case, I'm going to create my own patched version.

Are you using latest versions of logstash @jhaprins ?

I'm currently using 6.3.1. I would have to check where my colleagues picked up this version. I think they got it from some ElasticSearch repo.

/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-lumberjack-3.1.7/lib/logstash/outputs/lumberjack.rb

I have to check with my colleagues to find out what they want to use exactly and why. Could we have a quick chat? You say you don't use lumberjack anymore? What do you use to send data from one logstash server to an other?

Here is a working solution for Logstash using Lumberjack output to BEATS input on a downstream logstash instance:
#Generate a CA, Key + Signed Cert
/opt/elasticsearch-6.4.2/bin/elasticsearch-certutil cert --pem
unzip certificate-bundle.zip

# Convert the key to PKCS8
openSSL pkcs8 -in ./instance/instance.key -topk8 -nocrypt -out ./instance/instance.pk8

###################################################################
#Upstream Logstash Server

# This input could be anything...
input {
  stdin {}
  }
}

# Send the output to a downstream server
output {
   lumberjack {
      codec => json
      hosts => [ "<IP_ADDRESS>" ]
      port => 5044
      ssl_certificate => "/Users/Downloads/lumberjack/certs/ca.crt"
   }
}

###################################################################
#Downstream Logstash Server
#
#  Using the BEATS input to receive data from the upsteam Logstash server
#  which is using the lumberjack output.
#
input {
  beats {
    id => "mylumberjack"
    codec => json
    port => 5044
    ssl_certificate => "/Users/Downloads/lumberjack/certs/instance.crt"
    ssl_key => "/Users/Downloads/lumberjack/certs/instance.pk8"
    ssl => true
  }

}

output {
   stdout { codec => rubydebug }
}

I am also facing the same issue in 6.4.1.
Is there any specific solution regarding this issue?

Also, i have raised a post in community.
https://discuss.elastic.co/t/getting-lumberjack-all-host-unavailable-sleeping-error-when-logstash-to-logstash-communication-is-configured/179903
Is there any workaround to solve this issue?


iOS Camera Access when used as PWA

Cool app with cool approach, thanks so far! I'm on iPhone 7 and iOS 12.1 and not sure if this is an issue, I've done  the following steps:

opened https://qrcodescan.in/ in Safari

app asked for Camera access, approved

QR-Code Scanning works so far from Safari

then I used the "Share Menu" at the bottom menu of Safari and selected "Add to home screen"

the App was added to my home screen

opened the PWA using the new QR icon on home screen

splash screen with QR Logo is shown

then there is only a grey background and the "plus photo icon" (and the Info button at the upper right corner), so live scanning is not working

using the plus-photo icon the "manual" photo processing is working

Can I do something about the camera access settings for this PWA, or is this an known issue on iOS? Happy to hear from you, thanks again!

@mechko Thanks for reporting 👍in detailed way.
To answer your question..

When launching the app from homescreen in iOS devices, app will be launching from webkit webview for homescreen which doesn't support mediaStream API. Same goes for service worker.

We have to wait for apple to update the safari to allow camera access.
More: https://github.com/code-kotis/qr-code-scanner/pull/52

Okay, I see. Thanks for the reply, lets hope Apple is adding this very soon.


Getting Error while running on anaconda window

When i run command
Pip install roboflow
It gives following error
@Jacobsolawetz @broox @hansent @tonylampada @yeldarby
File "C:/Users//.conda/envs/ML/lib/site-packages/roboflow/config.py", line 20, in get_conditional_configuration_variable
default=os.getenv("HOME") + "/.config/roboflow/config.json",
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

@hammad2008 Thank you for your comment! We have a PR in the works that will solve this issue. https://github.com/roboflow/roboflow-python/pull/176. I will comment here when it has been merged and published.


Disable CAPI for CADET v4

Before releasing CADET-Python with the CAPI integrated we could/should disable the CAPI for CADET-Core v4. Thoughts?

This is now obsolete


Testing Locally

Hey Nikita,
When I've been making PRs, I haven't been testing the code locally, since I don't know how
I tried go get ./..., but I get an error message saying:
go get: no install location for directory /Users/john/license-up outside GOPATH
	For more details see: 'go help gopath'

How to you test locally? This is probably good to add to CONTRIBUTING.md

For me the code is inside my GOPATH so:
~/go/src/github.com/nikitavoloboev/license-up
For you, I believe you should clone it to:
~/go/src/github.com/johnletey/license-up
And from there you can run go install. This should put the tool in your PATH to use.
How to write Go Code has more info. One thing we can do for future is move to Go Modules. This removes the GOPATH issue.

Ah ... thanks
I had the code in ~/license-up ... I'll move it


Add support for passing --color option

Adds support for passing sphinx-build's --color option to sphinx-autobuild and updates the docs for that and #109

@choldgraf I think this PR and #109 are worth a new minor release.


Clickable links in direct message

Hi, anyone know how to make links clickable in a direct message? Currently the message will send with just the link as a string and not a hyperlink

@begly This library has no method for this action now, but you can implement this and send PR.
Endpoint for this is POST https://i.instagram.com/api/v1/direct_v2/threads/broadcast/link/
with such body

Key
Value

action
send_item

link_text
Just text instagram.com

_uuid
EF4FBE62-99BB-4EA1-996F-B553DAE3765A

client_context
E04282C1-9DAD-4C64-9F50-E8A41F95630C

thread_id
340282366841710300949128141257424359243

link_urls
["http://instagram.com"]

_csrftoken
jaAQ9IAay3515b22FtZoUBM1GFCJtyOX

@begly
Hi, how is it going this issue?
just i'm curious

@begly
And what further to do with the answer?
I receive {"action": "item_ack", "status_code": "200", "payload": {"client_context": "28C18C79-6F4A-4100-9E77-051DD9F99ECB", "item_id": "27712010498203388609205971688882176", "timestamp" : "1502271099304661", "thread_id": "38642339875287804975648647953286947520"}, "status": "ok"}

@GoldenEagle66  are you sure your question was for begly ?

@begly
Well, you suggested how to get the link, perhaps you know the further actions. In the sniffer I see only the receipt of the link, I do not see the sending

@GoldenEagle66 Yes, i have not noticed one next request
POST https://i.instagram.com/api/v1/notifications/badge/

Key
Value

_csrftoken
jaAQ9IAay3515b22FtZoUBM1GFCJtyOX

_uuid
EF4FBE62-99BB-4EA1-996F-B553DAE3765A

user_ids
5436575792,300687565

device_id
EF4FBE62-99BB-4EA1-996F-B553DAE3765A

@begly
I send a request for a link and receive it in the ovtet, then I sent it above. Then I send your second request and in return receive {"badge_payload": {}, "status": "ok"}, but there is no link in the correspondence, version 10.26.0

@dilame is it correct below? but i got Unhandled rejection ParseError: Not possible to parse API response
step 1.
{ action: 'send_item',
  link_text: 'go to http://www.google.com',
  client_context: 'deb5e5a1-08d9-4a5a-8ae4-5682c53b2046',
  thread_id: '340282366841710300949128162629334303906',
  link_urls: [ 'http://www.naver.com' ] }
step 2.

var request = new Request(session)
.setMethod('POST')
.generateUUID()
.setResource('threadsBrodcastLink')
.setData(payload)
.send();

i sent pr


Updated documentation to clarify the use of keyFile

I started to use systemctl to help manage homebridge. One of the features it is to restart homebridge if it crashes. I noticed that each time it restarts my TV would ask me permission about a remote app. Aftering finding #5 I realized that I could use the keyFile config to fix this, but it still wasn't working because I was specifying a directory path instead of a file path. This update makes this more clear so others won't make the same mistake I did.
Great work on this extension btw - it's a key part to my home automation efforts.

Looks good 👍


in-source sbt-houserules + .travis.yml refactoring

To validate this pull request against other sbt modules, please visit this link.


_subject as an email subject?

Hi,
Can I use input field name _subject as the email subject?

Hi asongdon, sorry for the late reply, I didn't see your message. Currently you can't set the subject dynamically when sending a form. But you can change the default subject through the MSG_SUBJECT config.json variable as outlined in the readme.


[BUG] 60.1.0: Installing mpi4py fails with latest setuptools

setuptools version
60.1.0
Python version
3.8
OS
Linux (Ubuntu)
Additional environment information
No response
Description
Installing mpi4py started to fail with the release of setuptools==60.1.0. It works with setuptools==60.0.4. Is 60.1.0 expected to be a breaking release version?
$ pip install -v mpi4py
Using pip 21.3.1 from .../venv-mpi4py/lib/python3.8/site-packages/pip (python 3.8)
Collecting mpi4py
  Using cached mpi4py-3.1.3.tar.gz (2.5 MB)
  Running command .../venv-mpi4py/bin/python /tmp/pip-standalone-pip-fmkquq0f/__env_pip__.zip/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-nun8azx9/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'setuptools >= 40.9.0' wheel
  Collecting setuptools>=40.9.0
    Using cached setuptools-60.1.0-py3-none-any.whl (952 kB)
  Collecting wheel
    Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
  Installing collected packages: wheel, setuptools
  Successfully installed setuptools-60.1.0 wheel-0.37.1
  Installing build dependencies ... done
  Running command .../venv-mpi4py/bin/python .../venv-mpi4py/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py get_requires_for_build_wheel /tmp/tmputajppc5
  Traceback (most recent call last):
    File ".../venv-mpi4py/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
      main()
    File ".../venv-mpi4py/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File ".../venv-mpi4py/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
      return hook(config_settings)
    File "/tmp/pip-build-env-nun8azx9/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 162, in get_requires_for_build_wheel
      return self._get_build_requires(
    File "/tmp/pip-build-env-nun8azx9/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 143, in _get_build_requires
      self.run_setup()
    File "/tmp/pip-build-env-nun8azx9/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 158, in run_setup
      exec(compile(code, __file__, 'exec'), locals())
    File "setup.py", line 462, in <module>
      from mpidistutils import setup
    File "/tmp/pip-install-k7kbt967/mpi4py_fa187d0418384267943227507227365d/conf/mpidistutils.py", line 29, in <module>
      cygcc_get_versions = cygcc.get_versions
  AttributeError: module 'setuptools._distutils.cygwinccompiler' has no attribute 'get_versions'
  Getting requirements to build wheel ... error

Something must have changed in setuptools that broke mpi4py/conf/mpidistutils.py.
Expected behavior
Installing the package mpi4py should work as with setuptools 60.0.x, given this is a minor version increment.
How to Reproduce
pip install --upgrade pip setuptools
pip install mpi4py
Output
  AttributeError: module 'setuptools._distutils.cygwinccompiler' has no attribute 'get_versions'

Code of Conduct

[X] I agree to follow the PSF Code of Conduct

macos 12.1 intel
python 3.10
pip3 list --outdated
Package    Version Latest Type

setuptools 59.5.0  60.1.0 wheel
if i update to 60.1.0, relogin terminal,display this error messate
Error processing line 1 of<EMAIL_ADDRESS>Traceback (most recent call last):
File<EMAIL_ADDRESS>line 186, in addpackage
exec(line)
File "", line 1, in
AttributeError: module '_distutils_hack' has no attribute 'ensure_shim'
Remainder of file ignored

Is 60.1.0 expected to be a breaking release version?

No. The changelog shows two changes.
It looks like pypa/distutils#77 is the likely culprit for the AttributeError as that removed get_versions.
@naveen521kk It looks like there are users relying on cygwincompiler.get_versions and we probably need to restore it. Can you work on that?

@spacexnasa Your error message seems unrelated, so I'm going to mark it as off-topic. If you have an issue, please report it separately.

@jaraco I'm the author of mpi4py. The only reason mpi4py had to use that API was to workaround an issue where distutils would fail if the path of the compiler command (C:\<path>\gcc.exe) contains spaces. Look yourself to the current code (after a fix for this issue). I'm not actually using get_versions for anything, but just monkeypatching it to prevent misbehaviors elsewhere related to the handling of filenames with spaces.
This code worked flawlessly for 15 years, but it broke after the removal of get_versions(). While I could make a new release with the hotfix for this setuptools change, users would not be able to install any of the previous mpi4py versions.

@naveen521kk It looks like there are users relying on cygwincompiler.get_versions and we probably need to restore it. Can you work on that?

Yeah sure. I will work on that later this week. I am planning to just add the get_versions() function in there but instead simply returning a couple of hardcoded values instead of actual values and also raising a DeprecationWarning when called. That should work, right?

This code worked flawlessly for 15 years, but it broke after the removal of get_versions().

Sorry!

It sounds like the use-case for mpi4py is simply to monkeypatch, so I'd not bother restoring the implementation. I'd just create an attribute with a comment:
get_versions = None
"""
A stand-in for the previous get_versions() function to prevent failures
when monkeypatched. See pypa/setuptools#2969.
"""

@jaraco @naveen521kk Will the new distutils code work fine if the MinGW compiler suite is installed in a directory with spaces in its name? These days mpi4py is not relying on MinGW for building its extension modules, but that could change in the future.

@jaraco @naveen521kk Will the new distutils code work fine if the MinGW compiler suite is installed in a directory with spaces in its name? These days mpi4py is not relying on MinGW for building its extension modules, but that could change in the future.

Reviewing the patch in pypa/distutils#77, I'm pretty sure the only change was for checking gcc versions. The rest should be the same, so Yes, I would expect things to continue to work as they work now. If you find that's not the case, please file a bug with pypa/distutils and we can work out a proper fix.

I'm going to go ahead and apply the patch I proposed above.


Escape string

This ad causes Shumway.AVM2.Compiler.AST.escapeString to be called with a 1.6 MB XML string. This exposes the fact that escapeString is very inefficient, primarily because it does the escaping in two passes, creating two new strings. It does this in order to decide whether to use single or double quotes in the final string. Shumway doesn't need this flexibility, and so it can easily be reduced to a single pass.

Great, thanks. We'll have to port this over to the redux branch, but that'll probably consist of just copying the whole functions to another file.


Custom action not displayed in Redux DevTools

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
Skills - @Transaction gets displayed instead of the defined custom action in Redux DevTools. Neither @action nor applyAction does work.
Expected behavior
Redux DevTools should display [Skills Service] Fetch All.
Minimal reproduction
https://stackblitz.com/edit/akita-todos-app-uiqjdx?file=src%2Fapp%2Fskills%2Fskills-data.service.ts
Am I doing it wrong by defining the custom action in the main service? It's the only place it makes sense for me. Thanks for your support!

:tada: This issue has been resolved in version 1.3.2 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

That was fast, thank you! It seems to have partly fixed my issue. I updated the Stackblitz above to illustrate it more clearly. Here's a summary of my observations:
  @action({ type: '[Skills Service] Fetch All' })
  fetchAll() {
    this.skillsDataService.getAll().pipe(
      tap(entities => {
        applyAction(() => {
          this.skillsStore.set(entities);
        }, { type: '[Skills API] Fetch All Success' });
      }),
      catchError(error => {
        return applyAction(() => {
          console.warn(error);
          return error;
        }, { type: '[Skills API] Fetch All Error' });
      })
    ).subscribe();
  }

When running the application the Skills state is not initialized (or at least there is no entry in  DevTools).
When clicking on "Fetch skills", I would expect from the above code to dispatch [Skills Service] Fetch All before making the fake API call and then either Success or Error when receving the response. In  DevTools I only seem to get the Success or Error part, @action still seems to get ignored.
When the Success action runs for the first time, the Diff is empty in DevTools, although the state is populated with the correct data. This might be connected to the previous point.

It seems to be a common issue when trying to link non-redux state management frameworks with the Redux DevTools. NGXS has a similar issue being unable to display Dispatch -> Success || Error in the right order (explanation in the linked comment). It seems that they could be solving this via some lifecycle flags within the @Action decorator.

Successfully fixed everything according to my previous comment.  I'd love to hear your thoughts first.

After discussing with the team, we decide that it's not correct to add the force attribute. Action should be dispatched only upon store update. In Redux, for example, when you call [Fetch All], you are usually updating the loading key and change it to true so you can show a spinner.

@NetanelBasal I could successfully solve 1 and 3 by moving everything out of AppComponent.
As for the 2nd, I tend to agree with you and your team. I already modified the Stackblitz and tried this out:
@action({ type: '[Skills Service] Fetch All' })
 fetchAll() {
   **this.skillsStore.setLoading();**
   this.skillsDataService.getAll().pipe(
     tap(entities => {
       applyAction(() => {
         this.skillsStore.set(entities);
       }, { type: '[Skills API] Fetch All Success' });
     }),
     catchError(error => {
       applyAction(() => {
         **this.skillsStore.setLoading(false);**
         **this.skillsStore.setError(error);**
       }, { type: '[Skills API] Fetch All Error' });
       return error;
     })
   ).subscribe();
 }

Now it fires all 3 actions accordingly, so Akita's actions are pretty intelligent already to figure such a case out. Props!
There's only one issue left. The Fetch All action altough fired, it seems to show the wrong Diff (loading from true to false). Feel free to check out the Stackblitz. Thanks for the amazing work and blazing fast answers!

There is no need to call setLoading(). Akita already initializes the store with loading set to true. When you call set() it will automatically set it to false.
You can use the query.selectLoading() method to toggle a spinner in your view. Check out the docs for more information.
If you have any further questions, let me know.

This triggers two questions in my head:

Is it fair to initialize the entity store with loading set to true without even calling the API request (as in Fetch All)? It somehow feels like magic that perhaps cannot cover 100% of the use cases.
If this behavior won't change, how do I get the Fetch All to get dispatched? I have nothing to update in the store, since loading has already been magically set to true.

Setting { loading: false } in the initialState of the store does the trick! Then it's just a matter of this.skillsStore.setLoading(true); in the Fetch All action to get it dispatched with the right Diff.
It might be helpful for newcomers to include the lessons learned from this thread into the docs. I would see the following:

After the last sentence on Loading State:

If you want to initialize the entity store with the loading state set to false [paste your code from above]

Under the Custom action paragraph:

The custom actions will only be dispatched on update of the state.
And perhaps give an example with the Dispatch - Success || Error pattern.

Akita :heart:

Done. Thanks. If you have any further question or feedback, let us know.


Added if not exists support to create table as

Summary of the changes / Why this improves CrateDB
closes #14834
Added if not exists support to create table as
Checklist

[-] Added an entry in the latest docs/appendices/release-notes/<x.y.0>.rst for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[-] Touched code is covered by tests
[-] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in the latest docs/appendices/release-notes/<x.y.0>.rst
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Can one of the admins verify this patch?

Hi @sayyidhussain, Thanks a lot for the PR!
This change, currently contains only the antl4 grammar change, so you need to make sure that the ifNotExists flag is passed to CreateTableAs and from there it's passed correctly to AnalyzedCreateTableAs, and then to CreateTableAsPlan.
Please add a test in CreateTableAsAnalyzerTest and  in CreateTableAsIntegrationTest to verify the functionality.

Hi @matriv i was able to do the changes but when i tested getting an issue where every time the
create table if not exists cpy1 as select * from tbl1  (example) query is executed the current record from tbl1 is getting inserted into the table cpy1 if the table already exist.
Is that expected behavior? if not can you explain what file needs to be changed

Hi @matriv i was able to do the changes but when i tested getting an issue where every time the
create table if not exists cpy1 as select * from tbl1 (example) query is executed the current record from > tbl1 is getting inserted into the table cpy1 if the table already exist.
Is that expected behavior? if not can you explain what file needs to be changed.

No it's not expected behaviour, if the table exists, no rows should be inserted, like postgres:
matriv=> create table t(a int, b int);
CREATE TABLE
matriv=> insert into t(a, b) values(1, 1), (2, 2);
INSERT 0 2
matriv=> create table new_t as select a, b from t;
SELECT 2
matriv=> create table if not exists new_t as select a, b from t;
NOTICE:  relation "new_t" already exists, skipping
CREATE TABLE AS
matriv=> select * from new_t;
 a | b
---+---
 1 | 1
 2 | 2
(2 rows)

Here: https://github.com/crate/crate/blob/master/server/src/main/java/io/crate/planner/consumer/CreateTableAsPlan.java#L91 tableCreator should not create a table if it already exists and IF NOT EXISTS clause is used, and the call postponedInsertPlan.get().execute()  should not be made.

Is there any progress on this @sayyidhussain ?
Do you need any more help?

hello. Has there been any progress on this recently? @sayyidhussain @matriv

Hi @matriv @dshunter107 Sorry for delayed response. I did try to stop the insert if the table already exists. All the approaches end up in timeout.

Hi @matriv @dshunter107 Sorry for delayed response. I did try to stop the insert if the table already exists. All the approaches end up in timeout.

Do you have a draft PR to see your approach? Otherwise maybe @dshunter107 you can take a shot if you'd like.

okay. I'll take a shot

Thanks for your efforts @sayyidhussain. Closing this as @dshunter107 took over.


refresh jenkins sample image for os3

@mfojtik @jhadvig ptal.  rhel dockerfile is still coming.

@mfojtik @jhadvig all comments fixed or responded to, i think.

job changes look a lot better to me

LGTM

LGTM, good job @bparees !

thanks guys.


[catkin build error]:  "fatal error: ignition/math4/ignition/math.hh: No such file or directory"

Hi, I was trying to build your package in ROS Melodic, but every time I try to compile it I get the following error:
 fatal error: ignition/math4/ignition/math.hh: No such file or directory
#include <ignition/math4/ignition/math.hh>
I tried to fix it by running: sudo apt-get install libignition-math4-dev but after that I got many more errors due probably to some changes in the libignition library.
Do you know how I can fix this issue?
Thanks in advance.

same issue, have you fixed it?

sudo apt-get install ignition-citadel then change the include path to #include <ignition/math6/ignition/math.hh> this might solve the problem

@yoursmile1999 I've just followed your suggestion and it starts building but then tons of errors arise and it seems like there are a lot of changes between the different versions of #include <ignition/math4/ignition/math.hh> and #include <ignition/math6/ignition/math.hh>. Any suggestion about possible solution?

I found the solution: once done sudo apt-get install ignition-citadel and changed all the path as #include <ignition/math6/ignition/math.hh>, before compiling you should change the c++ version in the CMakeList.txt to 17: add_compile_options(-std=c++17). Then you can run the simulation.


[CodingStandard] 8.x branch

Would you consider creating a 8.x branch from latest 8.3.48 tag? This would help to maintain 8.x versions.
I have made this fix https://github.com/costinel-draculet/symplify/commit/3394cd9f7ef948afa0bbc37985b33d8eb89e2d69 but cannot create a pull request towards master.

That would have to be resolved on whole Symplify level. Technically it's possible, but we would need someone to take care of it.
Would you be able to maintain them?

Could you give me more context on the whole Symplify level?
How many Symplify packages are affected by this change?

Basically whole dependency tree. Symplify is using some Symplify package, that require other Symplify packages etc., so all almost all packages for Symplify 8 would have to maintained.
It's the same as Symfony has. Either all packages get maintained of version X or none.

I will do my best to maintain the 8.x branch, depending on my
available time as well.
On Fri, Mar 5, 2021 at 12:27 AM Tomas Votruba<EMAIL_ADDRESS>wrote:

Basically whole dependency tree. Symplify is using some Symplify package,
that require other Symplify packages etc., so all almost all packages for
Symplify 8 would have to maintained.
It's the same as Symfony has. Either all packages get maintained of
version X or none.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/symplify/symplify/issues/3017#issuecomment-791026530,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMDLETV4XOUNEMVENHQFLQ3TCAJN7ANCNFSM4YS6ZWPQ
.

I guess that would require dedicated time effort, as branch maintenance is quite attention demanging.
We don't want to lie around bugs for old branches with frustrating users.

I don't feel confident in this descision, it would bring more harm then vlaue.
The way is to upgrade to Symplify 9 now.
Thanks for your suggestion and offer


Typed graphql document visitor

It would make some use cases easier to implement if there was a type-aware visitor provided. Maybe something that visits AST nodes that have a type attribute?
I'm basically trying to implement something like what I talk about in https://github.com/comigor/artemis/issues/39, where a base schema_types.dart file gets generated with just the subset of schema types referenced by the collected operations and fragments.

@micimize when you say "type-aware visitor", you want a visitor to traverse selection sets of an operation knowing the type of that selection set? Or is is about something other than selection sets?

@klavs that's right, maybe with a way for fragment spreads to access their fragment info as well. For instance, in graphql-to-dart I have to hack fragment fields in order to have them in the spread context

I'll need something like that for the new package:gql_code_gen. Maybe I'll be able to extract a reusable visitor. My only concern is that we only have an AST representation of the schema which might not be the best fit for providing the type information. For example, it does not provide easy access to types in a union, and implementors of an interface.

am currently working on a more "saturated" schema model abstraction on top of the ast nodes, which should essentially solve this issue. My goal is a graphql schema data model that projects the ast tree into something more "accessible"

Great! I managed to live without it, but it's clear that something like that is needed.

Thought I'd share a quick update on this - I implemented an alpha version in the execution and schema submodules here. It's partially modeled after graphql/type, but has execution models, and is mainly geared towards enabling intelligent codegen.
Might figure out how to/if we should PR the type definitions into a package here at some point. Not really sure where they fit in the ecosystem - maybe a gql_type module

Nice work there!

Might figure out how to/if we should PR the type definitions into a package here at some point. Not really sure where they fit in the ecosystem - maybe a gql_type module.

I have a feeling that what you've implemented in schema submodule belongs to package:gql, because GraphQLSchema would be useful as an input for the document validator. Interestingly, ExecutableDocument you've implemented in executable submodule kind of does not belong there because it wouldn't be used as an input for any validator.
This is why I went with AST-only validators initially.
Maybe we extend package:gql with:

package:gql/schema
package:gql/operation
package:gql/validation

On the other hand, maybe validation library does not belong to package:gql and it has to move to a separate package next to what is now your schema and execution submodules.
What do you think?

I think it's fine to leave them all under gql. To me, gql should encapsulate core typing and soundness features. A good line in the sand would be anything useful at the static analysis phase, and without a runtime or code-generation component

Agreed! You're welcome to open a PR with your changes.


Magic Antenna Checks Fails with segmentation violation

Description
My One of the submacro  openlane Magic Antenna Checks Fails with segmentation violation
Environment
python3 ./env.py issue-survey
Kernel: Linux v5.15.0-46-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: docker v20.10.17 (OK)
OpenLane Git Version: 6ab944bc23688cae6dc6fa32444891a1e57715c8
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

6ab944b 2022-08-09T14:51:35+02:00 IR Drop Reports in the Signoff Stage (#1255) - Mohamed Gaber -  (HEAD -> master)
4476a58 2022-07-29T16:03:10+02:00 Sky130 Enhancements (#1240) - Mohamed Gaber -  ()
4f63c8c 2022-07-27T17:26:27+02:00 Various CI Fixes (#1235) - Mohamed Gaber -  ()
---
Git Remotes

origin	https://github.com/efabless/OpenLane.git (fetch)
origin	https://github.com/efabless/OpenLane.git (push)

Reproduction Material
pinmux.issue_reproducible.tar.gz
Expected behavior
Logs
[INFO]: Running Magic DRC (log: pinmux_top/runs/pinmux_top/logs/signoff/41-drc.log)...
[INFO]: Converting Magic DRC Violations to Magic Readable Format...
[INFO]: Converting Magic DRC Violations to Klayout XML Database...
[INFO]: No DRC violations after GDS streaming out.
[STEP 42]
[INFO]: Running Magic Antenna Checks (log: pinmux_top/runs/pinmux_top/logs/signoff/42-antenna.log)...
[ERROR]: during executing magic script /openlane/scripts/magic/antenna_check.tcl
[ERROR]: Log: pinmux_top/runs/pinmux_top/logs/signoff/42-antenna.log
[ERROR]: Last 10 lines:
   7700 gates analyzed.
   7800 gates analyzed.
   7900 gates analyzed.
   8000 gates analyzed.
   8100 gates analyzed.
   8200 gates analyzed.
   8300 gates analyzed.
kill: no such node _11568_/A1
output: no such node _11568_/A1
child killed: segmentation violation

[ERROR]: Creating issue reproducible...
[INFO]: Saving runtime environment...
OpenLane TCL Issue Packager

@dineshannayya
Is that reproducible tested locally? Is generating same log with the test case?

I don't know how to validate the reproducible locally . Design wise, I have done good amount of changes in this Pinmux block
The flow gone through fine with
set ::env(USE_ARC_ANTENNA_CHECK) "1"

Just get into reproducible directory and execute ./run.sh it should create same segmentation violation.
I ran the test case at my end, getting different logs.

When run locally, I am getting different error, But still see a segmentation fault.
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
Cell sky130_fd_sc_hd__mux2_1 couldn't be read
  Processed 61252 subcell instances total.
Segmentation fault (core dumped)

The tail of log i got with reproducible:
Moving label "vssd1" from (null) to space in cell pinmux_top.
Moving label "vssd1" from (null) to space in cell pinmux_top.
Moving label "wbd_clk_int" from (null) to space in cell pinmux_top.
Moving label "wbd_clk_pinmux" from (null) to space in cell pinmux_top.
Processing pinmux_top
freeMagic called with NULL argument.
Extracting pinmux_top into pinmux_top.ext:
Can't open file ./reports/signoff/42-antenna.feedback.txt.
Reading extract file.
Building flattened netlist.
Running antenna checks.
antennacheck finished.

@RTimothyEdwards can you download the reproducible file and take a look?

@donn :  I cannot reproduce the error.  The test case generates a segfault due to a missing .magicrc startup file.  When the correct startup file is provided, then the test case runs to completion, correctly.

For the record, I just fixed the unrelated segfault problem in magic.

Thanks for the info. I'm on it.


[BUG] incompatibility with CPython main branch

Describe the bug
When trying to build the scipy main with
✘ 19:01:47 $ cython --version
Cython version 3.0.0a9
(bleeding) ~/s/o/scipy main|✓
✔ 19:03:33 $ python --version
Python 3.11.0a3+

you get the following error:
  In file included from /home/tcaswell/.virtualenvs/bleeding/lib/python3.11/site-packages/numpy/core/include/numpy/ndarraytypes.h:1960,
                   from /home/tcaswell/.virtualenvs/bleeding/lib/python3.11/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                   from /home/tcaswell/.virtualenvs/bleeding/lib/python3.11/site-packages/numpy/core/include/numpy/arrayobject.h:5,
                   from scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:871:
  /home/tcaswell/.virtualenvs/bleeding/lib/python3.11/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
     17 | #warning "Using deprecated NumPy API, disable it with " \
        |  ^~~~~~~
  scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:23979:1: error: too many initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  23979 | };
        | ^
  scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:24131:1: error: too many initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  24131 | };
        | ^
  scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:24453:1: error: too many initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  24453 | };
        | ^
  scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:24624:1: error: too many initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  24624 | };
        | ^
  scipy/optimize/_highs/cython/src/_highs_wrapper.cxx:30583:1: error: too many initializers for ‘PyTypeObject’ {aka ‘_typeobject’}
  30583 | };
        | ^
  error: Command "g++ -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DCMAKE_BUILD_TYPE="Release" -DHiGHSRELEASE -DIPX_ON=ON -DHIGHS_GITHASH="n/a" -DHIGHS_COMPILATION_DATE="2021-12-15" -DHIGHS_VERSION_MAJOR=1 -DHIGHS_VERSION_MINOR=0 -DHIGHS_VERSION_PATCH=0 -DHIGHS_DIR="/home/tcaswell/source/other_source/scipy/scipy/optimize/_highs" -DCMAKE_BUILD_TYPE="Release" -DHiGHSRELEASE -DIPX_ON=ON -DHIGHS_GITHASH="n/a" -DHIGHS_COMPILATION_DATE="2021-12-15" -DHIGHS_VERSION_MAJOR=1 -DHIGHS_VERSION_MINOR=0 -DHIGHS_VERSION_PATCH=0 -DHIGHS_DIR="/home/tcaswell/source/other_source/scipy/scipy/optimize/_highs" -UOPENMP -UEXT_PRESOLVE -USCIP_DEV -UHiGHSDEV -UOSI_FOUND -Iscipy/optimize/_highs/src -Iscipy/optimize/_highs/cython/src -Iscipy/optimize/_highs/src/lp_data -Iscipy/optimize/_highs/src/io -Iscipy/optimize/_highs/src/ipm/ipx/include -Iscipy/optimize/_highs/src/ipm/ipx/include -Iscipy/optimize/_highs/src/ipm/basiclu/include -I/home/tcaswell/.virtualenvs/bleeding/lib/python3.11/site-packages/numpy/core/include -Ibuild/src.linux-x86_64-3.11/numpy/distutils/include -I/home/tcaswell/.virtualenvs/bleeding/include -I/home/tcaswell/.pybuild/bleeding/include/python3.11 -c scipy/optimize/_highs/cython/src/_highs_wrapper.cxx -o build/temp.linux-x86_64-3.11/scipy/optimize/_highs/cython/src/_highs_wrapper.o -MMD -MF build/temp.linux-x86_64-3.11/scipy/optimize/_highs/cython/src/_highs_wrapper.o.d -std=c++14 -msse -msse2 -msse3" failed with exit status 1

The generate c++ that causes this problem is:
static PyTypeObject __pyx_type___pyx_memoryview = {
  PyVarObject_HEAD_INIT(0, 0)
  "scipy.optimize._highs.cython.src._highs_wrapper.""memoryview", /*tp_name*/
  sizeof(struct __pyx_memoryview_obj), /*tp_basicsize*/
  0, /*tp_itemsize*/
  __pyx_tp_dealloc_memoryview, /*tp_dealloc*/
  #if PY_VERSION_HEX < 0x030800b4
  0, /*tp_print*/
  #endif
  #if PY_VERSION_HEX >= 0x030800b4
  0, /*tp_vectorcall_offset*/
  #endif
  0, /*tp_getattr*/
  0, /*tp_setattr*/
  #if PY_MAJOR_VERSION < 3
  0, /*tp_compare*/
  #endif
  #if PY_MAJOR_VERSION >= 3
  0, /*tp_as_async*/
  #endif
  __pyx_memoryview___repr__, /*tp_repr*/
  0, /*tp_as_number*/
  &__pyx_tp_as_sequence_memoryview, /*tp_as_sequence*/
  &__pyx_tp_as_mapping_memoryview, /*tp_as_mapping*/
  0, /*tp_hash*/
  0, /*tp_call*/
  __pyx_memoryview___str__, /*tp_str*/
  0, /*tp_getattro*/
  0, /*tp_setattro*/
  &__pyx_tp_as_buffer_memoryview, /*tp_as_buffer*/
  Py_TPFLAGS_DEFAULT|Py_TPFLAGS_HAVE_VERSION_TAG|Py_TPFLAGS_CHECKTYPES|Py_TPFLAGS_HAVE_NEWBUFFER|Py_TPFLAGS_BASETYPE|Py_TPFLAGS_HAVE_GC, /*tp_flags*/
  0, /*tp_doc*/
  __pyx_tp_traverse_memoryview, /*tp_traverse*/
  __pyx_tp_clear_memoryview, /*tp_clear*/
  0, /*tp_richcompare*/
  0, /*tp_weaklistoffset*/
  0, /*tp_iter*/
  0, /*tp_iternext*/
  __pyx_methods_memoryview, /*tp_methods*/
  0, /*tp_members*/
  __pyx_getsets_memoryview, /*tp_getset*/
  0, /*tp_base*/
  0, /*tp_dict*/
  0, /*tp_descr_get*/
  0, /*tp_descr_set*/
  #if !CYTHON_USE_TYPE_SPECS
  0, /*tp_dictoffset*/
  #endif
  0, /*tp_init*/
  0, /*tp_alloc*/
  __pyx_tp_new_memoryview, /*tp_new*/
  0, /*tp_free*/
  0, /*tp_is_gc*/
  0, /*tp_bases*/
  0, /*tp_mro*/
  0, /*tp_cache*/
  0, /*tp_subclasses*/
  0, /*tp_weaklist*/
  0, /*tp_del*/
  0, /*tp_version_tag*/
  #if PY_VERSION_HEX >= 0x030400a1
  0, /*tp_finalize*/
  #endif
  #if PY_VERSION_HEX >= 0x030800b1
  0, /*tp_vectorcall*/
  #endif
  #if PY_VERSION_HEX >= 0x030800b4 && PY_VERSION_HEX < 0x03090000
  0, /*tp_print*/
  #endif
  #if PY_VERSION_HEX >= 0x030B00A2
  0, /*tp_inline_values_offset*/
  #endif
  #if CYTHON_COMPILING_IN_PYPY && PYPY_VERSION_NUM+0 >= 0x06000000
  0, /*tp_pypy_flags*/
  #endif
};
#endif

To Reproduce
Code to reproduce the behaviour:
Try to install the development branch of scipy with the development branch of CPython, numpy and cython.
Expected behavior
A clear and concise description of what you expected to happen.
Clean build.
Environment (please complete the following information):

OS: [e.g. Linux, Windows, macOS] Linux (arch)
Python version [e.g. 3.8.4]: main branch ~2021-12-14
Cython version [e.g. 0.29.18] : master branch ~2021-12-14

I have not bisected this yet, but plan to.

https://github.com/python/cpython/commit/8319114feedd2a5b77378bba24eb9fb2689c5033 / https://github.com/cython/cython/issues/4499 is the commit in CPython that I bisected this issue back.

https://github.com/python/cpython/commit/8319114feedd2a5b77378bba24eb9fb2689c5033
/ https://github.com/cython/cython/issues/4499 is the commit in CPython
that I bisected this issue back.

Thanks for the investigation. That's the issue with following CPython alpha changes, they sometimes just go back and forth.
We should adapt to that optimisation, but the same caveat applies, there's a chance that it may not make it through the CPython alpha/beta release cycle. And then our users would have used a Cython release for their own packages again that breaks when CPython 3.11 final comes out.
For now, I think we can at least remove the new type struct field again. That should be the safe first step. And needs a new release.

So it's https://github.com/cython/cython/commit/f5aa00bbb1e8c513ac18700f757f72d469599d32 to revert on 0.29.x and https://github.com/cython/cython/commit/751532a56484475c3cc75a380dca978be8ffa693 to revert on master.
It looks like this change was in Python 3.11.0a3 but GitHub actions hasn't yet got that version

I reverted the two commits. It's ok to live with the C compiler warning for now.

Searching for python/cpython@8319114 in the CPython repo you also get a hit on https://github.com/python/cpython/pull/30122 (I think only because in one of the comments they link to code snippets targeting this merge commit).
However, why trying to sort out why that PR came up in search, I noted a commit message

"add to what's new, because this change breaks things like cython"

so I suspect more changes are coming.

That change is the simplification of the exc_info data - the type and traceback is now just derived from the instance, and if they need to be unnormalised it's set to a tuple.

FWIW I did a quick check and both Cython master and 0.29.x can build themselves on Python 3.11.0a3. Doesn't guarantee that there aren't any bugs of course (for that I think we have to wait until its added to GitHub actions) but it gives some reassurance.
I don't think it's realistic for us to try to support the in progress versions between alpha releases though

https://github.com/python/cpython/pull/30122

That's a nice improvement, and if it stays in CPython, then we should generate proper code for it. Most of the three-exc-fields access that we do deals with curexc, which does not change (apparently). But we also have a couple of places where we touch the three fields in exc_info. Let's wait a bit for this to settle and then be prepared to adapt. 3.11b1 is still half a year away. (And post-beta rollbacks are not unheard of.)

That change is the simplification of the exc_info data - the type and traceback is now just derived from the instance, and if they need to be unnormalised it's set to a tuple.

That was the original thought, but then it turned out that exc_info is actually always normalised so the type and traceback field are redundant.   The raised exception curexc may not be normalized, so we are leaving it as it is with 3 values, but the caught exception (exc_info) is normalized.
I had a look at the cython code a few weeks ago, and it seems that all you do with exc_info is to copy it over in a few places. It should be easy to update that, just put the copy of the type and traceback fields under #if older version.   I can try to help (but I need to get my cython test setup working first).

Sorry I only saw https://github.com/cython/cython/issues/4500 after I wrote the previous comment. You're clearly on top of things.


performance for officer chat

literally nobody cares about how fast officer chat is, it gets like 1 msg every 10s when a big convo is going on

OK


Real time timer resets despite "never reset" setting

Title.  Apparently the timer resets when exiting an outpost.  I'm not sure exactly what the intended behaviour is here, though.

Here's a recording of the issue: here (It's still pending/processing at the time of submitting this)


Fix/security vulnerability

Updating PR to use octokit's api methods

@cainwatson @MadanBhandari Thanks!
I've released https://github.com/azu/git-commit-push-via-github-api/releases/tag/1.0.2


Regression in Builder Breaks Generated Entities

The alpha 6 release introduced a regression in the generation of entity files. It's very likely due to this change: https://github.com/propelorm/Propel2/pull/1090
We recently updated Propel to version alpha 6 at Spryker an are seeing issues with platforms supporting native id-method auto-increment (e.g. MySql).
It seems that the changes applied to DefaultPlatform::getIdentifierPhp() (https://github.com/propelorm/Propel2/blob/2.0.0-alpha6/src/Propel/Generator/Platform/DefaultPlatform.php#L1347) are not in sync with how this method gets called in ObjectBuilder::addDoInsertBodyRaw() (https://github.com/propelorm/Propel2/blob/2.0.0-alpha6/src/Propel/Generator/Builder/Om/ObjectBuilder.php#L5887).
The results in the generated entity files look something like this:
$pk = $con'foo-pk-seq'->lastInsertId();
which results in a critical parse error.
Thanks for looking into it.

I don't think #1090 is responsible for this. Can you give me your schema.xml that generates that wrong php code?

Thanks for the quick response. It's not only one schema file that causes the issue, it's all of them that define  id-method-parameter. Here's an example: https://github.com/spryker/Acl/blob/master/src/Spryker/Zed/Acl/Persistence/Propel/Schema/spy_acl.schema.xml
The issue doesn't occur with Propel 2.0.0 alpha5 though

You were right, #1090 was buggy. I fixed it in master.

Thanks a lot for taking care of it so quickly. Do you have any ETA on a new release that contains this fix?

https://github.com/propelorm/Propel2/releases/tag/2.0.0-alpha7

Thanks for the awesome support! It is highly appreciated 👍


Module compiled with Swift 4.1 cannot be imported by the Swift 4.2 compiler

With xcode 10 I am no longer able to build my project with KSTimeline included. I get an error: "Module compiled with Swift 4.1 cannot be imported by the Swift 4.2 compiler"
Are you able to recompile with 4.2?

close


Dark Mode

The amount of white space is near blinding when playing the Stalk Market late at night. I would love to have a feature to enable dark mode!

maybe work with https://darkmodejs.learn.uno/ ?


Added LAW commitment date

(and submission date for completeness, even though it has already passed)

Sorry for the delay in merging this.


Kubeshark Operator for Openshift

TESTED LOCALLY
Kubeshark Operator for Openshift.
Prerequisites

Access to Openshift Cluster.
Login as cluster-admin

Go to KS-Operator :
Apply Kubeshark CRD
oc apply -f config/crd/bases/apps.kubeshark.co_kubesharks.yaml

then
make run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (15f7a35) 26.75% compared to head (7978a63) 26.75%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1469   +/-   ##
=======================================
  Coverage   26.75%   26.75%
=======================================
  Files          14       14
  Lines         512      512
=======================================
  Hits          137      137
  Misses        375      375

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@kcns008 quick question. Does this need to be part of the kubeshark repo or does it make sense to make this its own repo?

@alongir Own repo for kubeshar-operator would be better option.

@alongir Own repo for kubeshar-operator would be better option.

So, let's do that.

https://github.com/kubeshark/openshift-operator


is this forum official?

is this forum official?

@myleshorton pls

Yes! This is an official lantern forum.


Decompression error is not captured and propagated to upper layers

When the decompression algorithm fails, the current decompression code directly pass compressed data to user. May need to add error report and handing in this part of code.
Code ref: https://github.com/grpc/grpc/blob/1f6faf3725453d45953b2a55feafd7a368f96fff/src/core/lib/surface/byte_buffer_reader.c#L68-L72

https://github.com/grpc/grpc/blob/d0fbba52d6e379b76a69016bc264b96a2318315f/src/core/lib/compression/message_compress.c#L184
Without knowing the code too well, it looks like this can be caused by two things:

Misalignment of different parts of the code. Negotiation chooses a compressor that is unknown in grpc_msg_decompress
If the data was corrupt

In either case it should be an error instead of silent propagation of compressed bytes. I wouldn't expect either case to be very common though.

Agreed. This issue was created for tracking purposes after an online discussion. I'm currently making changes to propagate the error.


Persist context of user even after logout

When a user logs in second time or subsequent time, he should be taken to the page he was at, before logging out of the system.
This is needed so that the user doesn't have to browse space/areas, etc to reach his context of work.

The simplest thing here is to extend the user profile service that we talked about for the user. I wouldn't bother implementing a specific back end API here, just have a key value store that the UI can use as it wants.

Great! Good idea ; )
On Fri, Mar 3, 2017 at 6:53 AM, Pete Muir<EMAIL_ADDRESS>wrote:

The simplest thing here is to extend the user profile service that we
talked about for the user. I wouldn't bother implementing a specific back
end API here, just have a key value store that the UI can use as it wants.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/908#issuecomment-283935381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq6NNCMW4_CtX2Ew9plU3NJiESBXqks5rh_8egaJpZM4MPnbY
.

Add a open ended JSON blob to the user profile.
( suggested by @aslakknutsen )


Locales: add Esperanto translation

Please make sure these boxes are checked before submitting your PR, thank you!

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

Please SQUASH my pull request

@maxkoryukov you also need to modify i18n.md. Don't worry about translation. We will translate it for you.

@ziyoung , thank you for your fast reply!
I updated the docs (4 docs, including translations)