chore(deps): update terraform terraform-ibm-modules/cos/ibm to v7.5.3

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
7.5.1 -> 7.5.3

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v7.5.3
Compare Source
Bug Fixes

add fix for breaking change introduced to fscloud submodule in 7.5.2 (#564) (8fba3fc)

v7.5.2
Compare Source
Bug Fixes

added fix to fscloud profile submodule where value of create_cos_instance was being ignored (#563) (2d47517)

BREAKING CHANGE
Do not upgrade to this version if using the fscloud submodule as it contains a breaking change that will destroy COS resources. Please upgrade directly to v7.5.3

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Idea: Speed up scheduler by removing socket poll call and reduce amount of routine calls

I was doing some profiling and found out that it might not be suitable to use asyncio.gather as certain routines are no-ops in an overwhelming majority of the time. It might be better to run loops within the event loop to have more control over when and where a routine is called.
This would also eliminate the need for polling on the socket as recv_multipart already forces a yield back to the event loop.
async def routine(self):
    count = await self._socket.poll(POLLING_TIME_MILLISECONDS)
    if not count:
        return

    for _ in range(count):
        frames = await self._socket.recv_multipart()
        if not self.__is_valid_message(frames):
            continue

        source, message_type_bytes, payload = frames[0], frames[1], frames[2:]
        message_type = MessageType(message_type_bytes)
        self.__count_one("received", message_type)
        message = PROTOCOL[message_type_bytes].deserialize(payload)
        await self._callback(source, message_type, message)

Can turn into:
async def routine(self):
    frames = await self._socket.recv_multipart()
    if not self.__is_valid_message(frames):
        continue

    source, message_type_bytes, payload = frames[0], frames[1], frames[2:]
    message_type = MessageType(message_type_bytes)
    self.__count_one("received", message_type)
    message = PROTOCOL[message_type_bytes].deserialize(payload)
    await self._callback(source, message_type, message)

The general idea is to run a message loop that will receive and process messages and a cleanup loop that will perform any necessary clean up tasks. This allows certain routines to run less often, freeing the event loop to perform more performance critical routines.
I think task_manager's routine only needs to be called when a message is received so it would make sense to call it after the binder routine.
def setup_loop(self, loop):

    async def on_message_loop():
        while True:
            await self._binder.routine()
            await self._task_manager.routine()
            await asyncio.sleep(0) # sleep(0) is optimized: https://docs.python.org/3/library/asyncio-task.html#asyncio.sleep

    async def cleanup_loop():
        while True:
            await self._function_manager.routine()
            await self._worker_manager.routine()
            await asyncio.sleep(1)  # its ok to have these routines run at longer intervals

    loop.create_task(on_message_loop())
    loop.create_task(cleanup_loop())

loop = get_event_loop(args.event_loop)
scheduler.setup_loop(loop)
loop.run_forever()

I didn't add in the signal event because it might be possible to avoid it by directly closing the loop in the signal callback:
signal.signal(signal.SIGINT, lambda *args: loop.close())

We can see that a scheduler implementing the above changes can potentially be 30% faster.
Current scheduler running 100k no-op tasks
[INFO]2023-02-25 20:48:13-0500: logging to ('/dev/stdout',)
[INFO]2023-02-25 20:48:13-0500: ScaledClient: connect to tcp://<IP_ADDRESS>:2345
[INFO]2023-02-25 20:48:13-0500: beginning scaled submit 100000 tasks
[INFO]2023-02-25 20:48:16-0500: completed scaled submit 100000 tasks in 0:00:02.972396
[INFO]2023-02-25 20:48:16-0500: beginning scaled gather 100000 results
[INFO]2023-02-25 20:48:48-0500: completed scaled gather 100000 results in 0:00:32.169261
[INFO]2023-02-25 20:48:48-0500: ScaledClient: disconnect from tcp://<IP_ADDRESS>:2345

Improved scheduler running 100k no-op tasks
[INFO]2023-02-25 21:20:26-0500: logging to ('/dev/stdout',)
[INFO]2023-02-25 21:20:26-0500: ScaledClient: connect to tcp://<IP_ADDRESS>:2345
[INFO]2023-02-25 21:20:26-0500: beginning scaled submit 100000 tasks
[INFO]2023-02-25 21:20:28-0500: completed scaled submit 100000 tasks in 0:00:02.139044
[INFO]2023-02-25 21:20:28-0500: beginning scaled gather 100000 results
[INFO]2023-02-25 21:20:51-0500: completed scaled gather 100000 results in 0:00:22.793362
[INFO]2023-02-25 21:20:51-0500: ScaledClient: disconnect from tcp://<IP_ADDRESS>:2345

@darenliang, You are right, I am also doing research on nng, I think this thing is still not very mature, as user are far less, might be the most wanted feature that attract us is IPC and socket is thread safe

Socket thread safety might not be as important as there is usually a thread safe implementation for zmq libraries. Also something you don't need to worry about in Python 😅.

The reason I do sending queue on connector is because of this Socket safety :), otherwise need maintain a lock

@darenliang , addressed and checkout the version==0.27


App log wrapping

I kept getting app log sends with the log file truncated without the data.

@keybase/react-hackers


[Tiny Supers (hbCyber)] v1.0 Initial

Changes / Comments

New sheet for the Tiny Supers system from Gallant Knight Games.

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[YES] Does the pull request title have the sheet name(s)? Include each sheet name.
[NO] Is this a bug fix?
[N/A] Does this add functional enhancements (new features or extending existing features) ?
[N/A] Does this add or change functional aesthetics (such as layout or color scheme) ?
[N/A] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[YES] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Game categorization Request:

This sheet("Tiny Supers") belongs to the TinyD6 game system group, so an new Game System Category named "TinyD6" should be created.
There are two previous sheets that also belongs to this system:

"Mecha and Monsters", sheet should be renamed "Tiny Frontiers: Mecha and Monsters", as the sheet is for a expansion to the "Tiny Frontiers"-game, which is made with the "TinyD6"-system
"Tiny D6 Games" is a sheet for two "TinyD6" games, "Tiny Frontiers Revisited", and "Tiny Dungeons 2e". I suggest the sheet to be named "TinyD6 Games" or just "TinyD6", as it's the proper name of the system, not "Tiny D6" with a space in the middle.

TinyD6 also has a page on the Roll20 wiki with links to more info.

Hi @hbCyber and @nogileyelsew I've updated the previous "TinyD6 game" systems to "TinyD6". I have also updated the title in the listing from just "Mecha and Monsters" to the suggested "Tiny Frontiers: Mecha and Monsters" and I'm adding this Tiny Supers sheet into the repo.


Some of the Markdown showing as Links on Doc page

http://doc.silverstripe.org/en/developer_guides/model/versioning
On this page  markdown are showing as links. I tried to submit a pull request . but failed to send the pull request https://github.com/blpraveen/silverstripe-framework/tree/patch-1
Versioned->augmentSQL() writeWithoutVersion())

This has since been fixed in https://github.com/silverstripe/silverstripe-framework/pull/5050


Trying to compile for arduino

Hello, I am trying to use the library example code, and I get the following error when compiling with the Arduino IDE:
Compilation error: 'msg' was not declared in this scope
Also, will this decode MicE encoded APRS?
Thank you,
Walter

This issues does not appear on version 0.06. The older version compiles and runs well. The latest version does not.


Localerror tooltip should show on node hover, not text hover

It's hard to hover the cursor over tiny text, so the tooltip should show whenever any part of a node in the tree is hovered

Fixed it. It was node hover but to fix the rendering issue I added incorrect timeout, which cause svg to render again after tooltip fixes to hover on node. Now fixed timeouts and now it works on node hover


initial commit

Great work @eurbasius. One recommendation I have though is to make your commit message more specific to the feature that you worked on. For example, you could have used "Show loading spinner in MediaListItem on remove item" That way when we see your commit in the git logs, we can have an idea of what those changes relate to.
You don't have to include a lot of details. Just anything that would help indicate what was worked on.


Revert changes to swap message

This reverts the changes introduced by a previous PR, ie. removes the new message UnblindedInput and the new field repeated UnblindedInput unblinded_inputs from swap request/accept message.
These changes will be applied to proto v2.
Please @tiero review this.

Would this breaks clients that implemented v1? ie. tdex-app

No, the types/field for unblinded inputs would have been used only by clients supporting psetv2 but we don't have any yet.


Rackspace fixes

Please do not merge; looking for comments
This is a pretty large update required to get the cluster running on Rackspace again.
Notable changes:

Use Flanneld instead of bash for next hop routing
Use KelseyHightowers kubelet registration tool
Added in token support for kubelet,kube-proxy <-> apiserver communication
Bearer tokens are passed to nodes via cloud-config. I may switch this to use metadata however there isn't an easy way to read this data without another tool.
The known_tokens.csv file is passed as file injection via nova. It's then copied from the metadata location to /var/lib/kube-apiserver prior to the unit starting. This isn't ideal so I'm thinking of alternatives.

I hard coded python2.7 in the scripts since the commands don't work in python3. Thoughts?
cc @erictune

I'm part of the Rackspace Corporation CLA. However the email address on file there differs from my github.

FYI once we merge https://github.com/GoogleCloudPlatform/kubernetes/pull/6949 then you won't need KelseyHightowers kubelet registration tool.  Same behavior will be built-in.

Please update docs/getting-started-guides/README,md to show rackspace at v0.16.2.

I don't understand the flannel or register parts well enough to give it a really thorough review, but if it is working for you, that's fine with me.
Rest looks good.

@doublerr I am the maintainer of the k8s deployment on ubuntu. I read your code and want to learn the dns and some other service token setup from you to update ubuntu version of deployment. I am using the same approach as you without saltstack.Do you want to include the dns or monitoring?

@WIZARD-CXY I do want to include those items but haven't dug into how they're being activated yet. I know we have variables to turn these features off/on but we don't have the deployment mechanisms in place.

@doublerr I think I can get the addons done once I undenstand this new feature https://github.com/GoogleCloudPlatform/kubernetes/pull/7101

@erictune this works with 0.16.2 but not with 0.17.0 (I haven't dug into why yet).
Can we merge to get since readme points to 0.16.2 assuming the bearer items were resolved.

Thanks for the update!

sorry for slow review: was out of office last week.


UploadableListener. Could use SplFileInfo?

Currently I have to pass either an instance of FileInfoInterface or a "valid array" to the addEntityFileInfo() method in the UploadableListener. Would it be possible to also accept an object of SplFileInfo there?
Examples show, that I should pull the array directly from the $_FILES global if I want to add an uploaded file to an entity. But I am using Doctrine with Laravel Framework and here we have an \Input::files('my_file') call to fetch the file values from the request. This call will give me an object of SplFileInfo, which has all the same properties as an array you are expecting in the addEntityFileInfo() method.
Seems kind of tedious having to create an array again after a framework has went through all the trouble of creating a neat SplFileInfo object.

Closing due to age and lack of activity. If you are interested in this issue or are still experiencing any problems described here, please add a comment!


Feature 492 stat analysis py embed

Added new use case demonstrating StatAnalysis using python embedding.

I've reviewed this use case and successfully run it on Kiowa, using met-9.0.1:

I obtained the following output:

I reviewed the use case documentation and this looks good. I'm not sure how to view it in rendered form. Let me know how/where I can do this if you'd like me to do that.
I approve this pull request. Once the latest changes from development have been incorporated and you have resolved the conflict noted above, you may go ahead and complete this pull request.

Thanks for reviewing. You can view the rendered doc here:
http://icculus.rap.ucar.edu/metplus-test/Users_Guide/met_tool_wrapper/StatAnalysis/StatAnalysis_python_embedding.html#sphx-glr-users-guide-met-tool-wrapper-statanalysis-statanalysis-python-embedding-py


ES6 HTML Style Comments

I had a go at adding support for ES6 HTML-like comments.  Does the approach make sense?
This change has no effect on the make apitest results.
It does not add or remove tests.

I pushed an improvement to the comment in the SingleLineHTMLCloseComment commit.

Trying to figure out the impact to code not needing/wanting HTML comment syntax support, I think at least this would parse differently with and without HTML comments:
var x = 10;
var y = 0<!--x;

Pretty nonsensical, but would evaluate to 0<!--x -> 0 < !9 -> 0 < 0 -> false:
duk> var x = 10;
= undefined
duk> var y = 0 <!--x;
= undefined
duk> y
= false

Same with Node.js:
> var x = 10;
undefined
> var y = 0 <!--x;
undefined
> y
0

So... Node.js already parses this as a HTML comment. Breaking the <!--:
> var x = 10;
undefined
> var y = 0 <! --x;
undefined
> y
false

So in summary, HTML comment parsing does technically interfere with ordinary syntax, but it's unlikely to cause problems because e.g. Node.js parses HTML comments too.

@tlsa-ct Thanks! I'll merge the base change into master: I'm not 100% sure of the required semantics but I'm quite sure you guys have a better idea of what constructs are encountered in browser environments. I'll open a tracking issue for cleanups, test coverage, possibly config options, etc.


SLIM-FIX ReadAlarmRegister does not extend superclasses

Make ReadAlarmRegisterAsyncResponse extend AsyncResponse and
ReadAlarmRegisterAsyncRequest extend AsyncRequest

All is well.


Move Task list template to Task list plugin

See Move templates to plugins

Removes task list template from kit
Retains task list sass pattern to support task list pages already created from the kit
The task list plugin should not be available prior to it being published

Just a blocker as we can't merge this until we figure out how to release it

The sass pattern for the task list will stay within the kit to provide support for users who have created a task list based on that sass.
The template for the task list has been removed from the kit and moved to the task list plugin where the sass for the plugin is name spaced with the plugin name as the prefix.  See https://github.com/alphagov/govuk-prototype-kit-task-list/tree/namespace-task-list-correctly


Suport environment variable expansion

YAML file should support expansion of environment variables.

both $VARIABLE and ${VARIABLE} should be supported
Other typical shell expansions should also work:

${VARIABLE:-default}
${#parameter}
${parameter%word}
${parameter%word}
${parameter#word}
${parameter##word}

$$ should be used to escape a single $

Compose implementation is based on String Template.

Fixed by #50

Following syntax is not supported though:

${parameter%word}
${parameter%word}
${parameter#word}
${parameter##word}


How to read multi-rec files  efficiently?

I made several rec files from different datasets, i 'd like to train the multi-rec files at the same time efficiently. I have tried "for" cycle to read each of the rec of a mini-batch , it works, but slow.
Does anyone has any good idea to load multi-rec files efficiently?
ps: i used imagerecorditer

@mxnet-label-bot add [question]

@weihua04 could you please share your code in here?

@anirudhacharya Can you possibly help here ?

@weihua04  while creating the rec file, were the labels packed with the image data?


allow multiline attributes in tsx

// test.tsx (jsx = "preserve")

declare namespace JSX {
    interface Element {
        'data-bind': string;
    }
    interface IntrinsicElements {
        div: Element;
    }
}
const div =

;

This is somewhat of a regression as I have a medium sizes codebase that is full of multiline attributes. Before this commit you could work around the problem by using the \ line continuation escape, but this commit disabled escapes in attributes (which is correct behavior), but also made this codebase not compile on the newest version...
The Babel React JSX transform seems to handle linefeeds in attributes just fine so I think the TypeScript compiler should also handle them.
I looked at the code and it looks like it could be fixed by hacking the scanner further similar the mentioned commit, I'll see if I could make a pull request.


Disable google maps scrolling hijack unless clicked

This might be a useful feature to add with a full-width Google Map (it's something I implemented in my own project). Now the Google Map won't hijack a mouse scroll for resizing the map except between when the user clicks the map and moves her mouse off the map. Based on http://stackoverflow.com/a/25904582/1607849

thanks


how to get all subscribed clients of one topic in plugin and hook

Environment

OS:
Ubuntu 14.04
Erlang/OTP:
19.3
EMQ:
2.1.2

Description
I use the demo emq-plugin-template , it works well. It can hook publish message, but how to get all subscribed clientId(including online and offline clients ? sessions ?) of the topic?
I want find all offline clients(clientId-iphone-xxx) and send the message by Apple's APNS
on_message_publish(Message, _Env) ->
    %% TODO: get all clientIds for this topic
    io:format("publish ~s~n", [emqttd_message:format(Message)]),
    {ok, Message}.

publish Message(Q2, R0, D0, MsgId=<<0,5,78,51,95,168,153,222,112,4,0,0,4,242,0,1>>, PktId=1, From=undefined/C_1493350205138, Topic=foo)

ets mqtt_subproperty works


CSUB-60: More unit tests & assertions in tests

Codecov Report

Merging #139 (aa3cf89) into dev (4cd22c4) will increase coverage by 0.23%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #139      +/-   ##
==========================================
+ Coverage   56.17%   56.41%   +0.23%
==========================================
  Files          27       27
  Lines        4874     4887      +13
==========================================
+ Hits         2738     2757      +19
+ Misses       2136     2130       -6

Impacted Files
Coverage Δ

pallets/creditcoin/src/tests.rs
99.32% <100.00%> (+<0.01%)
:arrow_up:

pallets/creditcoin/src/lib.rs
82.84% <0.00%> (+1.16%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Utility method for converting expressions into case patterns

Inside analyais_server_plugin\lib\edit\correction_utils.dart we have CorrectionUtils.invertCondition for doing what the name suggests. It takes an expression and returns another with the exact opposite result.
For https://github.com/dart-lang/sdk/issues/45831, I was thinking maybe we could have something similar for converting expressions with one constant side into case patterns.
Also one for converting back, from a case pattern into an expression. These could also be exposed as assists (all three of them) if we choose to.

I was thinking maybe we could have something similar for converting expressions with one constant side into case patterns.

Based on the linked issue, I'm guessing that you want a utility that would take count == 1 and return '1'.
I suspect that we'd get more value from a utility that takes an expression and returns a pattern if the whole expression can be converted to one. In other words, rather that take count == 1 and converting the 1, have a utility to just convert the 1 (and make the assist decide which side of the original condition to convert).
The assist will also need to ask the question of whether all of the expressions to be converted into patterns. It can probably do that by allowing the utility to return null if the expression can't be converted.

Also one for converting back, from a case pattern into an expression.

Constant patterns can be converted (though converting an expression to a pattern and then back to an expression might not always return the same expression), but other patterns are probably harder than we want to try to tackle (or just impossible in some cases).

but other patterns are probably harder than we want to try to tackle (or just impossible in some cases).

This is fine I think. I was simply thinking of a way for the user to swap between cases like:
if (count == 1) {...}  <-->  if (count case 1) {...}

if (count > 10 && count < 20) {...}  <-->  if (count case > 10 && < 20) {...}

It can probably do that by allowing the utility to return null if the expression can't be converted.

Agreed in both cases to and from. If it is impossible or too hard to handle we can just return null.


Question: How would you calculate the combined version number/string?

Hi again,
I would prefere a method to calculate the combined version number based on every single schema version number.
Based on the swagger definition a version is a string. It does not have to be a string like major.minor.patch which can be splited and accumulated by default.
So I think its necessary to configure a callback on swaggerCombine / middleware, where the calculation can be done.
At the moment the only way to configure the behavior is to define a config.json. But the necessary functional part is missing.
I hope you have an idea or will accept such a solution, so I can create a pull request.
Thx

I'm not sure if this is a feature that would be used frequently, so I'm not fully convinced to include it in this module.
You could easily achieve this by using the SwaggerCombine class directly.
Here is an example how to do this:
const sc = require('swagger-combine');

const config = {
  swagger: '2.0',
  info: {
    title: 'Basic Swagger Combine Example',
    version: ''
  },
  apis: [
    {
      url: 'http://petstore.swagger.io/v2/swagger.json',
    },
    {
      url: 'https://api.apis.guru/v2/specs/medium.com/1.0.0/swagger.yaml',
    },
    {
      url: 'https://api.apis.guru/v2/specs/deutschebahn.com/betriebsstellen/v1/swagger.json',
    },
  ],
};

new sc.SwaggerCombine(config)
  .combine()
  .then(res => {
    res.combinedSchema.info.version = res.schemas
      .reduce((version, schema) => version + `[${schema.info.title} - ${schema.info.version}] `, '')
      .trim();
    return res.combinedSchema;
  })
  .then(res => console.log(res.info))
  .catch(e => console.error(e));

Thx,
thats the correct approach.
const json = await new sc.SwaggerCombine(config)
      .combine()
      .then(res => {
        res.combinedSchema.info.version = res.schemas
          .reduce((version, schema) => {
            const [minor = '1', major = '0', patch = '0'] = schema.info.version.split('.')
            version[0] += Number.parseInt(minor, 10)
            version[1] += Number.parseInt(major, 10)
            version[2] += Number.parseInt(patch.split('-')[0], 10)
            return version
          }, [0, 0, 0]).join('.')
        return res.combinedSchema
      })


Fix frontmatter issues

This PR fixes the frontmatter issue, where frontmatter in md being formatted led to maps showing up. Now, mdformatter.go correctly processes nested fields. Fixes issue #13
---
title: 'Build a gRPC microservice in Go'
excerpt: "If you've dealt with microservices before, you've probably heard about gRPC. In this blog, we'll be exploring the awesome world of gRPC and write our very own microservice with it. We'll also delve into why gRPC might be better than our traditional REST architectures as well the caveats associated with it."
coverImage: '/assets/blog/build-a-grpc-microservice/cover.jpg'
date: '2020-12-06T05:35:07.322Z'
author:
  name: Saswata Mukherjee
  picture: '/assets/blog/authors/saswatamcode.jpeg'
ogImage:
  url: '/assets/blog/build-a-grpc-microservice/cover.jpg'
---

The above frontmatter generated before fix.
---
title: Build a gRPC microservice in Go
ogImage: map[url:/assets/blog/build-a-grpc-microservice/cover.jpg]
excerpt: If you've dealt with microservices before, you've probably heard about gRPC. In this blog, we'll be exploring the awesome world of gRPC and write our very own microservice with it. We'll also delve into why gRPC might be better than our traditional REST architectures as well the caveats associated with it.
date: 2020-12-06T05:35:07.322Z
coverImage: /assets/blog/build-a-grpc-microservice/cover.jpg
author: map[name:Saswata Mukherjee picture:/assets/blog/authors/saswatamcode.jpeg]
---

The above frontmatter generated after fix.
---
title: Build a gRPC microservice in Go
ogImage:
  url: /assets/blog/build-a-grpc-microservice/cover.jpg
excerpt: If you've dealt with microservices before, you've probably heard about gRPC. In this blog, we'll be exploring the awesome world of gRPC and write our very own microservice with it. We'll also delve into why gRPC might be better than our traditional REST architectures as well the caveats associated with it.
date: 2020-12-06T05:35:07.322Z
coverImage: /assets/blog/build-a-grpc-microservice/cover.jpg
author:
  name: Saswata Mukherjee
  picture: /assets/blog/authors/saswatamcode.jpeg
---

It happens usually when you put value to variable and never used later (e.g you replace it with another value later on)

It happens usually when you put value to variable and never used later (e.g you replace it with another value later on)

Should I directly assign pair?

Linting issues have been fixed @bwplotka.


Remove parens around literals which call match?

These are unnecessary and they make RuboCop sad.

Coverage decreased (-0.0004%) to 90.535% when pulling 414adde4624d66b65b1817c5289a4120a9bfbe3a on JoeCohen:regexp-parens into f4adb1a153faece70cc325863ba40c9b4e98f6b7 on MushroomObserver:master.


feat: make remix.init do more for us

I'm hesitant to do a lot for them in remix.init as it'll only run once and get removed, prisma generate and the initial npm run build seem fine though, other stuff like docker-compose and npm run dev should probably stay in the readme imo

@kentcdodds is doing a bunch of extra stuff in his stream for this PR


Sync transport implementation

Sync binder transport implementation from the internal repository to make tests work.
#26970 depends on this.
@ctiller

Thanks for the review!


Jupyter Notebook Activity Not Updating the Change in the Source Colab ipynb

I have made the change in the Colab ipynb on Google, but the update is not picked up by Jupyter Notebook Activity page.
What is causing the latency in update time? Sometimes the update can be picked up after a few minutes, but sometimes the update is not picked up at all.

i have found the answer:
apparently, i need to Ctrl-S for the Colab ipynb for the change to be picked up by the App.

you want to see this on Colab ipynb:


Implement AI-powered Task Breakdown Feature using OpenAI GPT-4

Summary of Changes
This pull request implements the AI-powered Task Breakdown Feature using OpenAI's GPT-4 model. The changes include:

Updated app.py to integrate OpenAI API and add a new route for AI task breakdown.
Modified index.html to include an AJAX request for the AI feature and display results.
Added error handling and a loading indicator for better user experience.
Updated requirements.txt to include the OpenAI package.

Reasoning
These changes address the feature request to provide AI-assisted task breakdown. By leveraging OpenAI's GPT-4 model, we can offer users intelligent suggestions for breaking down complex tasks into manageable steps.
Implementation Details
app.py

Integrated OpenAI API client with proper authentication.
Added a new route /ai_task_breakdown to handle AI requests.
Implemented logic to process user input and generate task breakdown using GPT-4.

index.html

Updated the AI Magic button to trigger an AJAX request to the new endpoint.
Added a container to display AI-generated content.
Implemented a loading indicator for better UX during API calls.

requirements.txt

Added openai package to the project dependencies.

Potential Impacts and Considerations

API Usage: This feature will consume OpenAI API credits. Monitoring and potential rate limiting should be considered.
Performance: The AI request may introduce a slight delay. The loading indicator helps manage user expectations.
Error Handling: Basic error handling is implemented, but additional edge cases may need to be addressed in production.
Security: Ensure that the OpenAI API key is properly secured and not exposed in the client-side code.

Issue Resolution
This pull request directly addresses the feature request "AI task breakdown" by implementing the requested functionality. It allows users to input a task title and receive up to 8 steps breaking down the task into smaller pieces, utilizing OpenAI's GPT-4 model.
Testing Instructions

Ensure the OpenAI API key is correctly set in the environment variables.
Run the Flask application and navigate to the main page.
Enter a task title and click the AI Magic button.
Verify that the AI-generated task breakdown appears after a short loading period.
Test error scenarios by temporarily disabling the API key or internet connection.

Please review these changes and provide any feedback or suggestions for improvement.
This PR fixes #68

Fix this error - make sure you're using an up-to-date API endpoint:
You tried to access openai.ChatCompletion, but this is no longer supported in openai>=1.0.0 - see the README at https://github.com/openai/openai-python for the API.
You can run openai migrate to automatically upgrade your codebase to use the 1.0.0 interface.
Alternatively, you can pin your installation to the old version, e.g. pip install openai==0.28
A detailed migration guide is available here: https://github.com/openai/openai-python/discussions/742


logs filling with influxdb-related errors after 0.47 update

HASS 0.47.0
Python 3.4.2
influxdb-related issue (I presume) - EDIT: also possibly the BOM Australia sensor component.
After upgrade, logs show the traceback below, but there aren't any obvious consequences of this - data is still being saved to the database as far as I can tell. There were no similar errors prior to the upgrade.
EDIT - on closer inspection, weather data from the BOM component is not being saved since the upgrade, though appears correctly in the history component.
2017-06-21 20:06:09 ERROR (Thread-7) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/influxdb.py", line 164, in influx_event_listener
    json_body[0]['fields'][key] = float(value)
TypeError: float() argument must be a string or a number, not 'datetime.datetime'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/influxdb.py", line 170, in influx_event_listener
    non_decimal.sub('', value))
TypeError: expected string or buffer

I think this is the same as #8042 or #8086, and was fixed (but not released) in #8080.
Could you test the dev branch to check it is fixed? (or only the changes in homeassistant/components/influxdb.py

OK, upgraded to 0.48.0.dev0 and no more errors. This has done the trick!
Apologies for not noticing the similar issues myself, and thanks for the support.


Corrupted pbit file without DataModelSchema file

I'm using your tool to convert pbix reports to pbit and then extract DataModelSchema for further analysis. I found that for some reason for some files pbit files are created corrupted. When I tried to unzip pbit files I found that they are missing DataModelSchema.

Are you using pbi-tools.exe or pbi-tools.core.exe? I'm assuming the former. The latter likely won't have that problem. Both use completely distinct methods for compiling PBIx files.


bug: @xstate/vue happend a error:  value

Bug or feature request?
Description:
(Bug) Expected result:
(Bug) Actual result:
(Bug) Potential fix:
Required! If you found a bug and can consistently reproduce it, please take a minute to think about what the potential fix might be.
Even if the fix is incorrect, this can help diagnose and find the solution to the issue as quickly as possible.
I also strongly encourage you to create a pull request if you are confident in the potential fix.
(Feature) Potential implementation:
Required! If you would like to see a feature or enhancement make its way to xstate, please describe:

Confirm the idea is not already on our Roadmap.
What the API would look like
If this is a breaking change
If this is part of the existing SCXML specification

Link to reproduction or proof-of-concept:
You can use CodePen or CodeSandbox template to create a reproduction/POC.

Can you please fill out the issue template with more information? Would be greatly appreciated 🙏
By the way, @xstate/vue is now on a new major version, which means there are breaking changes. See here for the migration: https://stately.ai/docs/migration#xstatevue


--default should just ask for missing answers, regardless of whether there's a default answer in the template

Actual Situation
It is an error for --defaults to be used if there is no default answer for a question and where there is no previously specified answer.
This will happen on e.g. a regeneration where new question without a default answer was added to the template, or on a new project.
Desired Situation
It would seem more useful to just ask if there's no previous answer, regardless of whether a default answer is provided by the template's copier.yml.
I'm not sure what generating an error in this case is attempting to prevent.
Proposed solution
Just ask for the missing data.
That there's no default answer doesn't seem relevant; if the data is missing, ask for it.
This allows --defaults to be used in all cases and just seems like the right behaviour to me.

Isn't that what -A does?

AFAIK, -A can only be run if there's already an answers file.  The object of the exercise is to be able to use the same command to generate or regenerate while testing to zoom through all the questions that have default answers to only have to answer the ones with no defaults.
Sometimes, when I have unexpected results, I iterate repeatedly; sometimes I kill the output, sometimes I don't.  I just want a single command to pick the defaults and get on with it as quickly as possible.

So are you talking about initial copies, or about updates? I'm confused

So are you talking about initial copies, or about updates? I'm confused

Both.  I just want one command to serve whether or not the project has been previously generated.  Sometimes I'm overwriting a previous run, sometimes I just delete it to get a fresh regeneration.
If I use --defaults, then I don't care about the answers to the questions, I am tweaking a template or something and whatever the default (or previous) answer is is fine.
Basically, if --defaults just asked for an answer to question without either a default or a previous answer, instead of terminating with an exception,  then --default could be used in either case to breeze past most or all of the questions by using defaults provided in copier.yaml or by using those provided during a prior run.

When running from a CI engine I don't want any prompting to occur, it will just cause the job to hang. I such a scenario the only reasonable thing to do if values are missing is to fail immediately.
I'm not saying whether the current combination of options and missing values is the best. The CI use case could also be handled with an explicit --non-interactive option of some form.

I such a scenario the only reasonable thing to do if values are missing is to fail immediately

Only if the question is required or an empty answer fails validation, right?
Did you make sure about that in your template?
Could you please provide a sample template to replay the problem?

I did not experience the problem.
I'm simply pointing out that if --default stops failing in case of missing values, then there should be another way to guarantee that copier does not go into interactive mode and hangs waiting for input. Anyway an explicit option to prevent interactive mode is probably the best.

AFAIK that won't happen. This code covers your use case:
https://github.com/copier-org/copier/blob/6b878c8af65c7b633e85c0e88133ac891a44fd07/copier/main.py#L447
Please reopen if you cn reproduce it and provide steps. Thanks!


add stringify helper

via @jsoverson on IRC
It works, which is good. EventEmitter2 has what looks like some issues unregistering listeners, and communication involving cyclic structures breaks when jsonifying data. I had to implement a custom stringify method that might be beneficial to incorporate into the lib.

It's been ~3 years with this issue. Are you going to implement the helper or using the module that sindersorhus points to or something else ?


CouchDB v. 3.0.0 cannot create admin on macOS Catalina 10.15.3

CouchDB v. 3.0.0 cannot create admin on macOS Catalina 10.15.3
Description
CouchDB 3.0.0 installed from installer.
Cannot create admin.
Steps to Reproduce

Install CouchDB from installer
Double click zipped file
Drag and drop the Apache CouchDB.app into Applications folder
Open Apache CouchDB.app

This automatically opens a window at login page.
Databases, setup, active tasks, replication and documentation pages are not accessible and the app redirects to login page.
Configuration and verification are accessible. When trying to verify the installation the following error messages appear:
"Error: Database does not exist."
"Error: Cannot read property 'set' of undefined"
"Error: You are not a server admin."
Since there is no admin, I attempted to create one visiting<EMAIL_ADDRESS>but it didn't succeed.

Expected Behaviour
Successful creation of admin.
Your Environment

CouchDB version used: 3.0.0
Browser name and version: same result on Chrome, Safari
Operating system and version: macOS Catalina 10.15.3

can you share your couch log, your default and local ini, you're vm.args and a full listing of your data directory?

@janl thank you very much for your response.
I have good news!
While I was trying to find the files you asked for I realised that in the folder User/Library/Application Support/CouchDB2 there were files from a previous installation,  based on their date of creation. I deleted the whole folder and reinstalled CouchDB 3.0.0 using the installer and this time I immediately got a window to setup an admin when I opened the app. Installation verification was successful too.
Thanks for your time and consideration.

Thanks for reporting back!


Support for sqlcommenter?

Is support for sqlcommenter planned? It would be highly useful to be able to automatically attach SQL comments to correlate user code in kysely with executed SQL.
It looks like knex has support fwiw.

Hey 👋
SQLCommenter is a suite of plugins/middlewares, have you tried requesting kysely support on their end?

No answer.

For anyone interested, I've been working on this for the past couple of days and it is now public. Feel free to give it a shot: kysely-sqlcommenter
import { SqlCommenterPlugin } from 'kysely-sqlcommenter'

const db = new Kysely<DB>({
  // ... kysely config
  plugins: [
    // Provide callback
    new SqlCommenterPlugin(() => asyncLocalStorage.getStore()),
  ],
})

hey, that's nice, I've created this PR specifically for this use case https://github.com/kysely-org/kysely/pull/871


How do we use S3Object?

** Which Category is your question related to? **
Storage/AppSync
** What AWS Services are you utilizing? **
Storage/AppSync
** Provide additional details e.g. code snippets **
Relevant link: https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app-react.html#complex-objects
How should we currently use S3Object?  There was a convention to follow previously, and it worked well.  Is this advised going foward?  If so, how?

I also was wondering and have further questions.
https://github.com/aws-amplify/amplify-cli/issues/274

This issue seems to have been fixed with the latest version. Please look at #274 for more info. Please feel free to re-open this issue if the problem still persists. Thanks!


Turn culture invariant off by default

About the PR

This pr turns the culture invariant off by default. When the culture invariant is on, no localization is allowed, and setting the locale at all fails (even to the default value of en-US). I'm not sure why this change is needed, because according to the dotnet docs it should be off by default anyways, but this was causing breakage on linux. This commit is confirmed to fix it on my system, but might need testing on windows to make sure it doesn't break things.
Fixes #10305
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: uelen

fix: Game not starting on arch linux with an error about localization

What command line flags do you pass to dotnet build to generate that?

-v diag

If we wanna do that, we'd need to at least figure out all projects that need it set. Does the server not also need this? And we'd also need changes engine side.

@waylon531 are you coming back to this?


Update script.js

I couldn't figure out how to deal with merge conflicts in VS so I did them in Github again, I'll look more into it tomorrow. I saw some things that were broken with the javascript we pushed to main, fixed them and added the new response variables (not all of them).

I couldn't figure out how to deal with merge conflicts in VS so I did them in Github again, I'll look more into it tomorrow. I saw some things that were broken with the javascript we pushed to main, fixed them and added the new response variables (not all of them).


Groups app frontend validations and alerts

In the Groups app create/edit form:

Name cannot be blank.
Member IDs cannot be blank.
Member IDs must be in the correct format (comma-delineated strings) AND each member ID must correspond to an existing member. (This entire validation will be unnecessary once #30 is completed.)

Validate these on Save.

If all validations pass and the save is successful, there should be an alert below the Save button saying:
a. for create: "Your group has been created! [View your group.] (with link to the group's View page)"
b. for edit: "Your changes have been saved! [View your group.] (ditto)"
If any validations fail:
a. There should be an alert below the Save button saying: "Something went wrong. Check for errors above."
b. There should be a message below each failing field specifying what the problem is.
If all validations pass but the save fails for any reason, there should be an alert saying: "Something went wrong." with the error message appended if there is one.

Additionally, gray out and disable the Save button while waiting for the save.
See the Adventures create/edit form (ProjectForm) for examples of all of the above, including per-field validations and validation messages, success and error alerts, how to link to the new entity's page, and disabling the Save button.

Will take a shot at this!

Got a draft PR opened just now. Still need to clean some things up which I should be able to take a shot at tomorrow evening.


Add pipeline for building Android

Tracking work to be done for an Android build pipeline. A basic sanity check to ensure that our code is able to build on that device properly

Please consider Oculus builds too (i.e. OCULUS_INTEGRATION_PRESENT is defined).

@keveleigh is investigating. Not required for 2.6, though should be done as soon as feasible

@keveleigh is investigating. Not required for 2.6, though should be done as soon as feasible


fix: Project table filter's broken dropdown

Fixes #2388
As I left a comment in the issue, these were getting overwritten because of their same names for django-filter. I tried to look into its templates code as well but I found this clue via its html(inspect, select's id and name).
Broken Filters Behaviour:

Fixed Behaviour:

Codecov Report

Merging #2402 (ae7839e) into main (668dc0c) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2402   +/-   ##
=======================================
  Coverage   81.79%   81.79%
=======================================
  Files         618      618
  Lines       22203    22203
=======================================
  Hits        18160    18160
  Misses       4043     4043

Impacted Files
Coverage Δ

hypha/apply/projects/filters.py
72.72% <100.00%> (ø)

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 668dc0c...ae7839e. Read the comment docs.

We did some research on others ways(https://github.com/HyphaApp/hypha/pull/2402#pullrequestreview-672543803) to avoid this problem. Which looks complicated, so going with renaming the filter fields for now.


Storing build artifacts for later release

I see this step is depracated in favour of pipeline artifacts
However pipeline artifacts only yield the most recently built artifact.
In classic pipelines we could publish an artefact from a build and then in a different deployment step (which might come many builds later) we could select an artefact published in the past and deploy that.
pipeline artefacts won't support this as they only yield the latest built artefact - can you suggest a different pattern that would support this? Or is the recommendation always to build from source prior to deployment?

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

ID: acd43f88-bb0b-e6c1-3a1d-c34af9a11dfb
Version Independent ID: 282eb416-bb03-9553-dbc2-71bb71191c73
Content: Publish Build Artifacts task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/publish-build-artifacts.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

@ElectricLlama Thanks for your question. You should reach out to the dev community with product questions. Also, if you have a feature suggestion, you can make it here.


FAB 18365 IT flake evictionsuspector failed to read eviction

Description
In failing case, the OSN being removed has committed the config change but failed to receive apply_config msg to halt the chain. This state is defined to be handled as part of the eviction suspicion logic. But it failed when evictionsuspector failed to check from lastconfig block if chain is up-to-date.
Fix: Updated the order of statements which looks at the latest config block and block height validation.
Type of change

Bug fix

Signed-off-by: Parameswaran Selvam<EMAIL_ADDRESS>

Please move this:
es.logger.Infof("Chain has been halted, pulling remaining blocks up to (and including) eviction block.")
To an else case of the if clause you moved, otherwise this is confusing - it says it is pulling the remaining blocks and then changes its mind about it later on.

Yes, I moved it down now.

/ci-run


Fix documentation formatting and typos

I realised that I hadn't updated the docs for Friends::Introvert#graph, then I spotted a few other things as I went!
I cleared up all Yard warnings, which led me to change up the "hash example" formatting a bit (Yard wanted the opening { to turn into links, which meant they weren't showing correctly in the generated docs).

Awesome, thanks for doing this!


Implement GetState/SetState for sessions

Need to implement these methods in the ServiceBusSessionReceiver. Should be the same as the Track 1 versions.

Closed with https://github.com/Azure/azure-sdk-for-net/pull/10900


ValueError: This CTranslate2 package was not compiled with CUDA support

CPU： Apple M3 Max

can support. mac os m3 cpu mode

I just run into the same problem.
in se_extractor.py line 22 I had to change the parameters, see below. Would be nice if this could be made configurable for Apple Silicon users.
model = WhisperModel(model_size, device="cpu", compute_type="float32")

@cjohn001
you're my hero thanks!


Update cluster tls-vars.yml with CN & SAN to pass fly validation

Signed-off-by: Sameer Vohra<EMAIL_ADDRESS>

The error
logging in to team 'main'

could not reach the Concourse server called herring:

    Get https://SOME_IP/api/v1/info: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs

@vito @topherbullock ^ please and thank you!

thanks! sorry for the delay, wasn't sure if this would break existing deployments but given that someone else PR'd the same thing (#75) i can probably just go ahead and merge


flutter_tool doesn't clean up old artifacts

When flutter_tool downloads a new version of sky_engine, it unpacks it over the old version in the cache. If files have been removed from the new version (compared to the previously installed version), those are not deleted in the cache - even though they should be.
The old files are confusing the analyzer in some situations, see https://cirrus-ci.com/task/4637233509564416?command=main#L15 as an example (here, wasm.dart has been removed from the dart sdk. However, even after updating flutter it remained in the cache).
/cc @jonahwilliams

This may be a blocker for next release cycle, as it trips up the analyzer during a dart migrate/publish

This may be a blocker for next release cycle, as it trips up the analyzer during a dart migrate/publish


feat: add config for pca in annlite

Goals: Enable loading indexer with PCA in DocumentArray AnnLite backend.
In AnnLite we load the model by their params_hash which compute by hashing n_dim, n_components...
So in order to successfully load the dumped indexer, we need to pass the n_components to AnnLite.

add a new parameter n_components, which is the output dimension of PCA, in annlite/backend.py AnnliteConfig
[ ] check and update documentation, if required. See guide

No need to change the version, we already have this n_components in AnnLite long time ago


bladebit --version still shows 1.2.0 after 1.2.2 install

Version.h:#define BLADEBIT_VERSION_REV 0
Ubuntu 20.04

Thanks for the report @jayhohoho2019. This has been fixed in v1.2.3.


[ Android ] add static option for openmp

This is the fix for "cannot find libomp.so"
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1745. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1745-202111261055230.57137703895569-0f9981230f3803c167dd2009a93f3dbfff981542/.


Timeout error during credentials request for s3 request

Steps to reproduce
No clear idea
Expected result
No errors
Actual result
022-12-03T13:17:32.391191Z ERROR remote_upload{tenant=X timeline=Y upload_task_id=2630}: failed to perform remote task UploadMetadata(lsn: 0/170E678), will retry (attempt 0): Failed to upload index part for 'X / Y'
Caused by:
    0: Failed to upload from '/storage/pageserver/data/tenants/X/timelines/Y/index_part.json' to storage path '"XXXtenants/X/timelines/Y/index_part.json"'
    1: failed to construct request: Failed to load credentials from the credentials provider: An error occurred while loading credentials: An IO error occurred communicating with IMDS: timeout: HTTP read timeout occurred after 10s
    2: Failed to load credentials from the credentials provider: An error occurred while loading credentials: An IO error occurred communicating with IMDS: timeout: HTTP read timeout occurred after 10s

Environment
Staging PS4
Logs, links

Seen some errors in stress env. Note that the machine this errors comes from is about to be decomissioned.
cc @SomeoneToIgnore Likely originates from recent s3 library change

More context:
Failed to load credentials from the credentials provider: An error occurred while loading credentials: An IO error occurred communicating with IMDS: io error: connection error: Connection reset by peer (os error 104)

For some reason retries on our side do not help. It my be because client keeps old connection and doesnt try to reestablish it. We can try to reinitialize client on such errors.
Also there is a feature for configuring retry policy for auth requests, but it is not released yet

Happened on production.

Yes, I'm generally not sure whether we should dig down to the roots of the issue, since IAM presumably has to go, since that will allows us more than x10 concurrent requests per second, which should be good for both on-demand downloads and regular work.

Will be fixed with https://github.com/neondatabase/neon/issues/3118, let's close this?

Lets continue in #3118

I had no idea of these issues before looking at the outage report. Would had linked this as well from the https://github.com/neondatabase/neon/pull/3128.


Navigation

Hi,
This plugin works perfectly but it's missing navigation between images.
Could you add this functionality?
Thanks!

Hey @BMCouto, I just pushed a patch that adds the functionality you asked for.


release references to view elements from server

fixes #136

It seems broken that multiple gets would return different results for the same uid.
Is this only used internally? Could it ever be called multiple time for the same key?

ViewsFromServer is only expected to be used internally. it's also expected that uids are unique and once a View reattaches, it never calls ViewsFromServer.get again. you're right though - it's still kinda weird. do you have ideas on how to make it less weird?

@ankurp @davydog187 is there anything else to do on this PR?

Nothing from my end.

The only comment I would make would be to change the get method to getAndPurge, or another name that makes it clear that this is a destructive action.
I'll leave it to your discretion whether or not you want to change, but I personally feel that get is inappropriate here.

getAndPurge is fine with me. i'll make the change

updated to ViewsFromServer.getAndPurge

Thanks for the update @wawjr3d


Building xeus-clang-repl on Apple Silicon

This issue will expand upon issue #75 , and detail the problems that occur when building xeus-clang-repl natively within MacOS on Apple Silicon. To aid in reproducibility I will first outline some details of my system

Processor: M1 Pro
Ram: 16 GB
OS: Sonoma 14.0
Package Manger: Macports

One problem I came across while trying to build xeus-clang-repl was the use of the xeus/xserver_zmq.hpp header file. At least on MacOS when you install xeus this header file is not present. I had to install xeus-zmq, and change the header file to xeus-zmq/xserver_zmq.hpp .
I will make a proper start on detailing the problems with building this repo in MacOS this weekend, when I have a little more time. I will raise a separate issue in each one of the dependencies and link them back to this one.

notes_xeus_clang_repl.txt
I've now had a chance to rebuild xeus-clang-repl, and all its dependencies on my Apple Silicon Macbook. I've attached to this message my notes on what issues I came across while building. I still need to do a few things which are at the end of my notes, which I am hoping to have done by some time tomorrow. I also need to check how my changes may be modified by the recent commits to the https://github.com/compiler-research/CppInterOp repo. Assuming no new issues arise, then my plan is that tomorrow I will commit all my changes to the following repos, and then put in pull requests, after raising issues in the repo of each respective dependency.
Forked repos which will contain the changes
https://github.com/mcbarton/xeus-clang-repl
https://github.com/mcbarton/CppInterOp
https://github.com/mcbarton/cppyy-backend
https://github.com/mcbarton/CPyCppyy
@vgvassilev who should I put as the reviewer of these pull requests?

@vgvassilev who should I put as the reviewer of these pull requests?

yes, please.

The following other issues were found which stopped xeus-clang-repl being built on Apple Silicon

Missing #include  in include/xeus-clang-repl/xmanager.hpp caused errors with building due to use of std::cerr and others
xeus/xserver_zmq.hpp doesn't exist when installing xeus with MacPorts, but is available with xeus-zmq
Linking to cxxopts::cxxopts doesn't work on my machine. Instead I pointed by machine to the location of the cxxopts folder

A pull request will be created shortly to suggest a fix for the above issues
A known unresolved issue is that xeus-clang-repl assumes that -cuda arg is being used. Apple cannot make use of Cuda gpus, are you end up getting error messages about not knowing what to do with -cuda.
After the fixes in the pull request were perfomed alongside those mentioned in linked issues I was able to build xeus-clang-repl on Apple Silicon. Not everything in the included notebooks worked with this build, but quite  a bit did.

I've also worked on CMake in this project. I'll submit my changes and review your PR when I have some free time (probably in a couple of days), if you want.

I've also worked on CMake in this project. I'll submit my changes and review your PR when I have some free time (probably in a couple of days), if you want.

@p4vook That would be helpful thanks. If your ok with it I may cc you in on the issue I have found with the CppInterOp cmake config file too.

Yep, sure


Fix navigation

Image references are working, and the site is up: https://department-of-veterans-affairs.github.io/vets.gov-patterns/
However, Pattern Lab is using iframes and javascript behind the scenes which causes some of the navigation link to result in 404s.

Found out what is happening...
Inside the following function, pattern lab's JS tries to change the URL when somebody is navigating. Because our repo name has the phrase 'patterns', it breaks the expected behavior and results in 404s. I'm filing an issue with PatternLab to see if they can resolve this.
We can also potentially change the repo name to vets.gov-designpatterns or something of the sort.
function receiveIframeMessage(e) {

                var i = /(patterns|snapshots)\/(.*)$/;
                t = window.location.protocol + "//" + window.location.host + window.location.pathname.replace(i, "") + a.path + "?" + Date.now(),
                window.location.replace(t)


import type from from "foo"

🔎 Search Terms

type import
parser
import type from from

🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAMyhEjmoERQKYEMDGMGA3HAPRlwQDWAUKJLHDAJ5jZwAeaKcWehEuUo164aPFbseqJL34EipCnDC4oAZw7YoyKEA
💻 Code
import from from "react"; // ok
import type x from "react"; // ok
import type from from "react"; // parse error

🙁 Actual behavior
parse error
🙂 Expected behavior
I have merely observed its inconsistency, without discerning whether it is by design or a bug.
Additional information about the issue
No response

Looks like the parser is interpreting type as an identifier on line 3 and then choking when it sees the second from.

There's still a problem with import type from = require('foo'): (playground link). That seems like a bug if it's expected that from is allowed to be the name of an imported type. Should that be fixed as part of this issue as well?
For context, I'm commenting here because I was linked to this bug from esbuild's issue tracker, and I need to figure out how to handle this kind of type syntax in esbuild.


pageserver: prioritize activation of tenants with client requests

Problem
During startup, a client request might have to wait a long time while the system is busy initializing all the attached tenants, even though most of the attached tenants probably don't have any client requests to service, and could wait a bit.
Summary of changes

Add a semaphore to limit how many Tenant::spawn()s may concurrently do I/O to attach their tenant (i.e. read indices from remote storage, scan local layer files, etc).
Add Tenant::activate_now, a hook for kicking a tenant in its spawn() method to skip waiting for the warmup semaphore
For tenants that attached via warmup semaphore units, wait for logical size calculation to complete before dropping the warmup units
Set Tenant::activate_now in get_active_tenant_with_timeout (the page service's path for getting a reference to a tenant).
Wait for tenant activation in HTTP handlers for timeline creation and deletion: like page service requests, these require an active tenant and should prioritize activation if called.

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

This PR adds 2 new info! log lines to print per Tenant::spawn. Before this PR, adding log lines is a sensitive issue because we'd write them all out within a few milliseconds. With this PR, they should be streteched out over time, so, it will be less of a peak. Correct?

Right.

Did you think through what happens if a initial logical size calculation fails in a tenant? IIUC the tenant will be waiting for LogicalSize::initialized , occuping one of the concurrency permits.

I think the only drop-out cases in that function are for cancellation, but that's a fragile assumption, so I've pulled up the notify call to a scopeguard::defer to guarantee we don't leave that function without calling it.  The await_initial_logical_size function also respects cancellation, so the only way we'd get stuck would be if we failed to enter

I think your use of Notify is correct, but, generally speaking what we want here is some kind of OnceCell<()> thingy that once can .await to be set by someone else. heavier_once_cell perhaps.

Yes, true that the Notify use here is fragile, in case someone later uses the await function more than once.  Will defensively use something that permits multiple awaiters to proceed.

This is set to auto-merge.  Job 1 on my Monday list is to check for any fallout on staging.


add aws_vpn_gateway

Would be nice, closing in on completion :)

I just submitted pull request with feature.  If accepted hopefully it will work for you too.

Now VPN Gateway are supported (https://github.com/dtan4/terraforming/pull/190) :shipit: Please try the latest version.


[zh] Sync outdated style and structure of /community page

Changes

The /community/_index page is outdated by comparing to the English version.
Not well-formatted and organized, and the style is not consistent with the English version.
Tweak some of the translation of /community/_index page.

See preview: https://deploy-preview-43739--kubernetes-io-main-staging.netlify.app/zh-cn/community/

Please squash your commits into a single one. Refer to: https://kubernetes.io/docs/contribute/new-content/open-a-pr/#squashing-commits

/lgtm

Thanks.
/approve


New Feature: R history

Close #190

Hmmm, it looks like there is a permission issue with the non-root user.
This is quite strange as it should work the same way as the renv-cache Feature which has been working for some time.


Allow image_identifier to be lifecycle ignored

Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
Yes. When using apprunner in image mode you supply the image_identifier which includes the tag. Typically docs will just write someorg/someproject:latest.
However, in production you usually deploy a specific tag (in our case a semver or git sha). someorg/someproject:v1.5. This is to prevent accidentally deploying the wrong version due to a race condition in whoever sets the latest tag last.
But if you deploy a specific tag and then rerun terraform, terraform picks up that the image_identifier has changed and wants to reset it back to latest.
Describe the solution you'd like.
An option that would effectively add a lifecycle ignore_changes to the image_identifier field. That way terraform can do the initial provision but subsequent deployments can change the image_identifier without bringing terraform out of sync.
Describe alternatives you've considered.
We switched our deploys to tag latest right before deployment. This doesn't eliminate the issue but reduces the window that it could be an issue.
Additional context

this sounds like a bug for the upstream AWS provider

this sounds like a bug for the upstream AWS provider

Hi @bryantbiggs, could you explain how it might be an upstream AWS provider issue? The solution I mentioned does work in the AWS provider, it just needs to be configured in this module.

because of this statement (if its true):

But if you deploy a specific tag and then rerun terraform, terraform picks up that the image_identifier has changed and wants to reset it back to latest

Using the ignore changes lifecycle is a very heavy handed solution and I suspect nearly everyone using this module would not want that behavior

How do you know that?

Well professionally I've worked for a number of companies from small to large (3000+) that all use terraform to provision and configure cloud resources but generally hand off deployment to a CI/CD like github actions, jenkins etc.
Well, Terraform is inherently more risky than a typical deployment as it affects cloud infrastructure and certainly isn't the recommended way to do deployments with ECS or k8s. It would also require you to commit the new image tag to git from a terraform action which isn't that common and doesn't play well in larger multiuser environment.
Have you seen different?

Disclaimer: I work at AWS as a container specialist with our container service teams (EKS, ECS, Lambda, etc.)

Have you seen different?

I have seen quite a bit 😬

Terraform is inherently more risky than a typical deployment as it affects cloud infrastructure and certainly isn't the recommended way to do deployments with ECS or k8s. It would also require you to commit the new image tag to git from a terraform action which isn't that common and doesn't play well in larger multiuser environment.

These are all very subjective statements. However, there are various parts where static configurations meet dynamically changing values (artifact versions and autoscaling values are the two most common culprits). You can see some of these pains here and here
In short, to support these we'd have to do a hacky thing by supporting dual resources - one with a lifecycle ignore block, and another without. Its a pattern that I abhor and am reluctant to support if at all possible. Instead, I would encourage users to explore alternative avenues, such as using an ECR data source and pulling the image value from there as the input to your AppRunner module configuration, or sometimes SSM parameter store works just as well

I would encourage users to explore alternative avenues, such as using an ECR data source and pulling the image value from there as the input to your AppRunner module configuration

OHH I’m not sure why I didn’t think of that. That’s definitely a better approach. Let me see if that’s doable and if there’s a “first-run” issue. Thanks!

@bryantbiggs I did a bunch of digging into this as it did come up again and I'm kind of at a loss. I tried to use an aws_ecr_image data query to insert the correct image into the image configuration which seems to work 'ok'-ish with 2 fairly major problems.

On first run, the ECR repo is empty (terraform just created it). So the data query actually fails the entire terraform plan. It requires a lot of manual work to get it past this point.
It's not easy to select the correct image. The 2 best candidates are (1) the latest tag or (2) the most recent image. Both have their shortcomings. (1) AppRunner only actually deploys if the deployed image tag is different than the one currently running. So the actual apprunner service will not be using the latest tag. Even if we also tag the current image with latest, that means terraform will force apprunner to redeploy to the latest tag even if it's the same causing terraform to run for at least 2-5 minutes waiting for the service to redeploy. (2) the most recent image is not necessarily the "current" image. CI/CD will build and push a container even if it doesn't intend on running it (e.g. a dev or test container).

I'm not sure how this module fits into a production environment with these shortcomings. Let me know if you think there's a different workaround. I do feel like an optional lifecycle policy on the image configuration would solve all these problems.

(2) the most recent image is not necessarily the "current" image. CI/CD will build and push a container even if it doesn't intend on running it (e.g. a dev or test container).

We segregate our ECR infrastructure to facilitate this, Dev / QA / UAT images are pushed to a different ECR, and only Approved Releases that are merged to main are built and pushed to the "Live / Production" ECR.


[Question] Is there any way to share the failures in a thread created under the message sent by the report?

Is there any way to share the failures in a thread created under the message sent by the report?
The idea around this suggestion is reducing verbosity on the message we are sending to the team.

The highlighted section would go to a thread under the message with the results summary.

I'll  do some googling and see if they have an endpoint for this.

Found this one: https://api.slack.com/messaging/sending#threading

It seems doable, here's my initial attempt at this ...

Just having a think about what to display though, I guess we can keep it simple initially as per your example above:
Failed test name

Stack trace (first 100 characters)

I will also need to add an extra config key (boolean - defaulted to false), something like summarizeFailuresInThread

added in https://github.com/ryanrosello-og/playwright-slack-report/releases/tag/v1.1.14


Feature/mimetype

Fix for #1946

Thanks for the feedback @TheModMaker
I have made the requested changes


Segment can be very slow on ios

Forum link https://forum.ionicframework.com/t/poor-performance-with-ionic-2-tabs-and-segments-on-ios/45886/4
Short description of the problem:
Segment buttons in tabs ionic2 project can be very slow to switch on iphone
What behavior are you expecting?
smoothly just like tabs
Steps to reproduce:

ionic start tabs --v2 --ts
add segment with two tabs
build & run on iphone

insert any relevant code between the above and below backticks

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 1.x or 2.x
2.x beta
Run ionic info from terminal/cmd prompt: (paste output below)
Your system information:
Cordova CLI: 6.0.0
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic Version: 2.0.0-beta.3
Ionic CLI Version: 2.0.0-beta.19
Ionic App Lib Version: 2.0.0-beta.9
ios-deploy version: 1.8.5
ios-sim version: 5.0.3
OS: Mac OS X El Capitan
Node Version: v4.2.1
Xcode version: Xcode 7.2 Build version 7C68

What devices does this happen on? Does it occur on emulators, too? I'm not able to reproduce this using a new project (with the steps given) or the conference app. Tested on an iPhone 6 emulator running iOS 9.2.

I tested this app on iPhone4s with ios 9.2, but on the forum, some dev
claim it will happen on emulator too.
I will try to cook up some minimal example for this one.
2016年3月22日 上午5:41，"Brandy Carney"<EMAIL_ADDRESS>
What devices does this happen on? Does it occur on emulators, too? I'm not
able to reproduce this using a new project (with the steps given) or the
conference app. Tested on an iPhone 6 emulator running iOS 9.2.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/driftyco/ionic/issues/5875#issuecomment-199498690

@brandyscarney I can not reproduce this problem on other devices except my iphone4s, so I guess the problem is caused by old hardware. Thanks for your attention, Sorry for the false alarm.

It's still slow on iphone 6
Your system information:
Cordova CLI: 6.2.0
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.9
Ionic CLI Version: 2.0.0-beta.31
Ionic App Lib Version: 2.0.0-beta.17
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v4.4.0
Xcode version: Xcode 7.3.1 Build version 7D1014

It's very slow on iPhone 6

same problem here on iPad. Using ionic 2.2.0.. :(

Hello,
Same problem for me with segments component on ios.


Requesting pre-trained model variants trained on grayscale ImageNet

Would it be possible to have also greyscale ImageNet weights for the models along the lines described in Xie & Richmond?

Xie, Y. and Richmond, D., “Pre-training on grayscale ImageNet improves medical image classification,” in [Proceedings of the European Conference on Computer Vision (ECCV) Workshops], 476–484, Springer (September 2019).

您的邮件已收到!

Hello, I'm interested in obtaining ImageNet grayscale weights, particularly for resnet50. How can I access them?

您的邮件已收到!

Hello, I'm interested in obtaining ImageNet grayscale weights, particularly for resnet50. How can I access them?

I think you can try the radImageNet if you are working on medical images
https://github.com/BMEII-AI/RadImageNet

您的邮件已收到!

@Navodplayer1
This is awesome. Thnx a lot.


Add .nvmrc to project root

What problem does it solve?
Adding .nvmrc file to the root makes switching using nvm to the required node version easier
Describe the solution you'd like
Add .nvmrc to the root
Describe alternatives you've considered
NA
Additional context
NA

I don't use nvm


Corrects the vulnerable version of PHP Excel

The PHP Excel project released another version which basically archived the project but importantly didn't fix this vulnerability.
Changes in the 1.8.2 release: https://github.com/PHPOffice/PHPExcel/compare/1.8.2...1.8

How about setting an uperbound of version 99.99.99 or something like that, so any new tags won't fall outside of this range?
Idk what the standard is for these cases

In that case shouldn't the version constraint be *?

I think I'd prefer the 9.9.99 trick

* is currently not accepted by the validator.


Allow integration with power rename

Is your feature request related to a problem? Please describe.
Allow integration with power rename
Describe the solution you'd like
Allow integration with power rename with a right click or menu
Describe alternatives you've considered
Explorer allows this option
Additional context
Sample menu

The app doesn't support custom context menu items yet. See #699.

Merging with #174.

This has been implemented in #1754.


As documentation says, currentSlide property will be deprecated in future version. What is the alternative for this?

Good question 💭 I think a more suitable name would be initialSlide

I also think defaultSlide would conform to standard React naming conventions for a value which is only used at mount.


3PN link with templates is wrong

Here is my experience:
Richs-MacBook-Pro:~ rich$ dotnet --version
3.0.100-preview7-012821
Richs-MacBook-Pro:~ rich$ dotnet new webapp -o webapp
Getting ready...
The template "ASP.NET Core Web App" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore-template-3pn-210 for details.

Processing post-creation actions...
Running 'dotnet restore' on webapp/webapp.csproj...
  Restore completed in 53.99 ms for /Users/rich/webapp/webapp.csproj.

Restore succeeded.

The 3PN link: https://aka.ms/aspnetcore-template-3pn-210
The link seems to be 2.1 specific. This is where it goes to:

Ouch. I would rather see a non version-specific link and for it to go to a place that lists TPNs for all of our templates. If folks agree with this, then this repo is probably the wrong one, but I’m starting here, since it is an ASP.NET template at issue.

Thanks @richlander.
I'll see whether I can fit this in preview 8.

@richlander, thinking about your suggestion more

I would rather see a non version-specific link and for it to go to a place that lists TPNs for all of our templates.

I feel like that'll be work for a scenario, which has no real functional impact. Who, at all, is actually looking into these? I think we'll be spending time doing this for not a good reason. So for now I'm simply updating the link to be 3.0 specific.
@danroth27 this is your decision really, so if you'd like us to change this and stick with more user-friendly approach, we can come back to this again.


Release/4.1

NEW FEATURES

Coinbase wallet support
Can Pass in your own logger to track events or debug your app

REFACTORS

standardise on camel-case file names
split large files into many separate
restructures the logic / state propagation between dapp and wallet from callbacks to event listeners and actor functions.

OTHER
-- expanded test coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (stable@961620f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             stable     #291   +/-   ##
=========================================
  Coverage          ?   65.35%
=========================================
  Files             ?       82
  Lines             ?     1931
  Branches          ?      241
=========================================
  Hits              ?     1262
  Misses            ?      463
  Partials          ?      206

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Is there a way to have an option to have always visible last header-row in waterfall layout tab?

      Title

          search

          <input class="mdl-textfield__input" type="text" name="sample"
                 id="waterfall-exp" />

        Link
        Link
        Link
        Link

Usecase is a multi-page tab, where in when the user scroll the title of the page doesn't matter anymore. The user needs to always see menu icons that is applicable to the current page.

+1 I have the same problem. If you see the "Google Play App" this is the behavior (hide the first line)

.mdl-layout__header--waterfall{
flex-direction: column-reverse;
}
add style="order: 1;" to first line div.

The search and title disappears, but then it should be located initially at the top, then disappear when scrolled while the links are supposed to stay.
http://codepen.io/anon/pen/QjyPyg

I'd go with a simpler approach:
.my-header {
  justify-content: flex-end !important;
}

See http://codepen.io/anon/pen/KdVjpp
That should make the bottom row stay in place while the top slides out of view. The menu button stays in place, since it's positioned absolutely.
If you want to add or remove elements which are only visible when the header is contracted, you can use the .is-compact class (which gets added automatically to the header when it contracts) in your selectors.
As for adding this as an option to the header, we can consider it. @surma @Garbee WDYT?

Modifier sgtm for 1.1.

Yeah, SGTM :)

Merged in master.


Can's seem to figure out the multiple file upload, please can anyone help me with that?

Please check the following instructions before submitting a bug :

Make sure you are using the latest version.
Make sure you read installation, integration, and upgrade document.

If your problem still remains, please do these steps :

Run php ./vendor/unisharp/laravel-filemanager/bin/debug and paste the results here.
Capture screenshots of your browser console and paste them here.
Provide the steps to reproduce your issue, so we might solve it quicker.

Option 1 : You can drag and drop files into the upload modal.
Option 2 : Click the upload modal, keep holding "shift" key and click on multiple images.


CI: add script to create bundles for microshift

Required for https://github.com/openshift/release/pull/38200 one.


Add new screenshots and feature description to homepage

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1863
Originally created by @DouweM on 2020-03-13 18:56:24

View 3 previous comments from the original issue on GitLab


SOLR-16927 Allow SolrClientCache clients to use Jetty HTTP2 clients

https://issues.apache.org/jira/browse/SOLR-16927

Description
Allow SolrClientCache to work with Jetty http2 clients.
Solution
This change is allowing the SolrClientCache users to use a Jetty http2 client, in parallel with the internal Solr http client.
All http client creation (both old and new) is moved into the SolrClientCache, this will make it a single source for all the streaming code. It will also fallback to Jetty http2 by default.
I also poked around the timeouts a bit, the current values based on system properties will overwrite the internal http client ones, which is bad when the client values are larger than the local ones.
I had to touch some of the streaming classes, as the http2 client needs to be properly closed, which was not the case everywhere.
I added a benchmark, but I still need to tweak it a bit before publishing numbers.
Just for future reference of what remains to be done in this class, most of the internal use of this cache is based on the UpdateShardHandler.getDefaultHttpClient (SOLR-16503) - the CoreContainer reference, so the complete refactoring is blocked until that transition completes.
Tests
Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

looking for a review on this. @dsmiley, @epugh @joel-bernstein I hope you don't mind I added you. looking forward to your thoughts!

@joel-bernstein do you think you will have some time to review this PR?

sounds good. will rename and merge in the next few days. thanks @dsmiley!


Enchantments warning on Items delivery

What is your Quests version / build number (do not say "latest")?
rc.4 b202
Describe the problem and how to replicate it. Any console errors to post using Pastebin.com?
https://pastebin.com/jgrrNw4D - Warning/error
The issue appears whenever you have so to say "custom items" to deliver to NPC. It should be also doing the same for Items with enchants. Whenever player login into server and has deliver quest active it does pop the warning above in console.
If applicable, can you provide an example quest from quests.yml using Pastebin.com?
https://pastebin.com/x63amFDc - quests.yml

Looks like your quest named "item" is trying apply illegal enchantments, such as Multishot on a Diamond Sword.

Looks like your quest named "item" is trying apply illegal enchantments, such as Multishot on a Diamond Sword.


Building RUM index with large amounts of data causes PANIC: evicted with zero LSN

Steps to reproduce
We create a table and fill it with 2.5 million random ts_vectors. My actual database has a similar number of rows but even more complex text data.
CREATE EXTENSION rum;

CREATE TABLE large_test_rum_index (
    id SERIAL PRIMARY KEY,
    content_tsvector tsvector
);

CREATE OR REPLACE FUNCTION complex_random_tsvector() RETURNS tsvector AS $$
DECLARE
    words text[] := ARRAY[
        'apple', 'banana', 'cherry', 'date', 'elderberry', 'fig', 'grape', 'honeydew',
        'innovation', 'juxtapose', 'kinetic', 'leverage', 'metamorphosis', 'nuance',
        'oscillate', 'paradigm', 'quintessential', 'resilience', 'serendipity', 'threshold',
        'ubiquitous', 'vortex', 'watershed', 'xenial', 'yield', 'zenith', 'abstract',
        'brevity', 'cognition', 'diligence', 'empirical', 'facetious', 'gregarious', 'hypothetical'
    ];
    result text;
BEGIN
    -- Generate a string of 100 random words
    SELECT string_agg(words[ceil(random() * array_length(words, 1))], ' ')
    INTO result
    FROM generate_series(1, 100);

    RETURN to_tsvector('english', result);
END;
$$ LANGUAGE plpgsql;

-- Takes ~5 minutes
INSERT INTO large_test_rum_index (content_tsvector)
SELECT complex_random_tsvector()
FROM generate_series(1, 2500000);

CREATE INDEX large_rum_index_test ON large_test_rum_index USING rum (content_tsvector rum_tsvector_ops);

This will cause the server to crash and no index will be created.
SELECT indexname, indexdef
FROM pg_indexes
WHERE tablename = 'large_test_rum_index' AND indexname = 'large_rum_index_test';

Expected result
The index should be created.
Actual result
The server crashes and we get a panic message:
PANIC: [NEON_SMGR] Page 0 of relation XXXXX is evicted with zero LSN (SQLSTATE XX000)

Note that the index creation will succeed if we generate only 500,000 rows.
Environment
Autoscale 0.25 CU to 4 CU. (The crash happens even if the CU is pinned to 4 CU)
Postgres 15
Logs, links
Based on the panic message, I believe that this crash has to do with:
https://github.com/neondatabase/neon/blob/main/docs/core_changes.md#mark-index-builds-that-use-buffer-manager-without-logging-explicitly
(And an associated PR https://github.com/neondatabase/neon/pull/7440)
pgvector has a Neon-specific patch to call the smgr_unlogged_build functions.
https://github.com/neondatabase/neon/blob/ea0b22a9b0e5dd03605a285ce6560926299628d8/patches/pgvector.patch#L4
However I do not think that RUM has such a patch.
https://github.com/postgrespro/rum

Hey, thank you for great analysis! Yes, correct we need to instrument RUM the way you suggested. We've noticed that crash some time ago and were not sure whether to just drop RUM from supported extensions or fix it. Since you are using it -- makes sense to fix. I'll get back to you with ETA on Monday

Confirming that this is fixed now on Neon — thank you!


Configurable location of SSL certificate and private key files in container

Configurable location of SSL certificate and private key files in container, because in some cases (K8s deployment) directory, which already exists in container cannot be used (because SSL certificate and private key are generated in init container and passed to main container via volume which needs to be mounted to a new directory).

Thanks and there were tests too, nice. It's now published to Docker Hub and Github Registry the tag is :30


Investigate event mapper replacement

Investigate the potential to replace the current (likely-not-very-scalable) event mapper implementation for this proxy with one that is more scalable -- probably based on the v11.7 events topic that includes more details about the specific changes that were made.  In an ideal scenario, this would allow us to avoid any need to persist state separately: is that feasible?
If so, we could then re-implement the event mapper without any reliance on stubs, but with a minimum v11.7 requirement for Information Server.  For v11.5 we could still provide a read-only proxy connector, just without any (optional) event mapper connector for that earlier release.

The IgcUnifiedGovEvents topic is not a solution on its own, as it does not have any published events from IMAM activity (that only appears to go to the InfosphereEvents topic); however, the InfosphereEvents topic has published IMAM activity in it whether events are enabled or not in IGC.
There may therefore be a potential solution by combining only the IMAM-related events from InfosphereEvents and the full set of events from IgcUnifiedGovEvents (?)

Caveats identified in using IgcUnifiedGovEvents:

does not appear to include events for various imported things (eg. imported relationships)
uses a different set of identifiers for changes (eg. ASSET_FIELD and RELATION indicating the field that has changed does not match the REST property name, but instead values like assignedAssetsExcludingTerms_clean and assignedToTerms_clean -- which are not resolvable from the type system accessible via API)


Introduce strict validation of user configs, terminate node if it fails

Validation is run as a setup phase hook. These can be wired to
abort processing through -setup abort_on_error true. However, due
to a bug in setup, this didn't propagate all the way to an aborted
startup. This bug was fixed, and the setup dependency upgraded.
The schema has been upgraded to have "additionalProperties": false
at each level.

[Finishes #153138074]


why did you make jQuery a dependency?

Hi,
Old swiper (2.7.6) didn`t have jQuery as a dependency.
I just saw that jQuery is now a dependency (From 3.x.x+).
I guess you thought about it and decided to add it, what was the reason?
It now forces the developer to adopt jQuery, event if he does not use it... useless payload..

Why have you decided that jQuery is dependency now?

see https://github.com/nolimits4web/Swiper/blob/master/package.json#L44
jQuery is a dependency, implied anyway...

This shouldn't be here, came from another commit, will remove it


session-replay: use ESM modules

This PR adds ESM module support to session-replay.
session-replay is now bundled into two files:

bundle.mjs - ESM modules
bundle.cjs - CommomJS (Node) modules

This change also fixes import errors in react-scripts.

@konraddysput it builds now.


Kannon quick starter

What
A tutorial for kannon within the local env using minikube!
All details for this tutorial can be found in example/quick_starter.md.

Thank you for reviewing!


cli_test_dir: Add tons of new features

Ping @seamusabshere: I needed to upgrade my personal testing library to better test https://github.com/faradayio/scrubcsv . Can you please confirm that I'm authorized to release these changes under the same terms as the existing library? (It uses a CC0 license / public domain dedication, which places the code into the public domain in most jurisdictions and offers a very broad fallback license otherwise.)
We can now:

Easily check status without lots of boilerplate.
Easily check stderr and stdout without lots of boilerplate.
Create input files.
Pass data on stdin.
Check the contents of output files.

@emk yes confirmed!

@seamusabshere acked the license and the build is green on all platforms, so let's go ahead and merge and release.


using good versioning

How about some good versioning
http://semver.org/
I believe the canvas overhaul should have been 2.0.0 maybe ? good versioning would really help.
don't mean to be a nuance but i just felt a genuine need to have this.

Thank you, i will read the article on the weekend.


add assignment submission classes

@CodeBaboon @ryantmer I need a code owner approval apparently

Especially in the repo with the least rigorous code reviews XD


LoadableData Fix

Updated LoadableData class, to work again with Vue2 and Vue3. You have to use Vue.reactive for the class to be reactive again.

You would need to update all the tests too. I think the name should probably stay the same.

You would need to update all the tests too. I think the name should probably stay the same.

Seems to be failing a bit, are you able to run the tests locally? The test suite randomly disables a few browser tests to speed up development, so you should probably comment out that line.


mautrix-signal: 2021-11-12 -> 2021-12-25, use buildPythonApplication

Motivation for this change
noticed it was broken
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Looks like heisenbridge mautrix-facebook mautrix-telegram haven't supported the latest mautrix yet

mautrix, heisenbridge and mautrix-telegram were updated in #152557, so the second commit from this PR should be enough to fix mautrix-signal.
I just cherry-picked it and mautrix-signal is still working fine.

mautrix-signal is on version 0.3.0 now: 587f52427fe9a323372a0d8b87858576f9cbd8eb