Rdwrap. ini for 10.0.19041.2075 X86

Hi:
Anybody has rdwrap.ini for w10 , 10.0.19041.2075 x86.
I attach termsrv.dll.
Thanks
termsrv.zip

https://github.com/sebaxakerhtc/rdpwrap.ini/commit/b8df93bfce36d6c2e89fff4a890296a199ee7133

Thanks a lot. It works.
Kind Regards

i used this rdpwrapper.ini for a windows home computer with build 19044.2075, it works but rdpwrap config gives nt supprted

rdpwrap.zip
Try attched ini file that works for me.

thats one from 03-2022

That ini file was modified recently taking a previous one, and adding the offsets for 10.0.19041.2075. x86. It works for me.

it weorks for also only rdpwrap config gives not supported ?

I can only tell you it works for me. I cannot tell you more, I am not an expert.

Would someone have the termsrv.dll file already patched to replace the original? my version is 10.0.19041.2075 x64
thanks.

@barragan88

termsrv.dll file already patched

For patching termsrv.dll you risk getting banned from Stas'M...

sebaxakerhtc/rdpwrap.ini@b8df93b

It works!

I also have issue with 19041.2705 updates to 22H2, after that my RDP has become single session
I have stopped RDP services and replaced rdpwrap.ini with this version but it's not working
rdpwrap.ini.txt
I have even uninstalled RDPWrapper then reinstall yet it's not working
Please help !


[Help] Console spamming

Hello, I've a problem with the new version of skript-db
First of all, I want to thank you for updated skript-db!
With the new version, all of my request send this message in console:
CONSOLE: WARN]: [Skript] A SQL query was attempted on the main thread!
whether they are async or async.
What does this message mean and what should I do to make it no longer appear?
Thank you in advance for your answer

That message should only pop up when a sync query is attempted on the main thread. I'll get a hotfix out for this.

Thanks!


Converts ES6 native classes to ember objects

This is a breaking change as it converts the new Class() syntax to Class.create().
In addition, the only way I could get these to work was to convert the positional arguments to named args in an options hashes:
new Table(columns, rows) => Table.create(columns: columns, rows: rows)
new Row(content, options) => Row.create({ content: content })
new Column(opts) => Column.create(opts)
We’ve had to replace the native constructor methods with emberObject init methods as per the official docs which should also fix #699. As a result we’ve removed the Ember 2.12 ‘hacks’ which shouldn’t be an issue as we’ve bumped ember version minimum version to 2.18.
Clearly there are issues with ember 2.18 that need resolving but @alexander-alvarez what are your thoughts so far?

Would it help to release a codemod for this too? I'm also unsure of what to do about the docs as ELT's aren't versioned. Could we enable something like http://offirgolan.github.io/ember-cp-validations/ so we can maintain 1.x and 2.x versions?

Looks like as of Ember 3.11 the changes in this branch are now mandatory, i.e. master of ember-light-table doesn't function with<EMAIL_ADDRESS>It gives the error:
EmberObject based class, (unknown), was not instantiated correctly. You may have either used `new` instead of `.create()`, or not passed arguments to your call to super in the constructor: `super(...arguments)`. If you are trying to use `new`, consider using native classes without extending from EmberObject.
The good news is that this branch is working well in my testing so far :+1:.

@richard-viney any chance you could help me fix this back to 2.18 then I can merge!

@alexander-alvarez any thoughts on the best way to handle the docs? I'm keen to get this merged ASAP as without it, ELT doesn't work with Ember 3.11+.
Should we just put a note in the readme on the 2.x branch for now - we'll need to do something more permanent before 2.x release though

Should we just put a note in the readme on the 2.x branch for now - we'll need to do something more permanent before 2.x release though

:+1:
sorry for the delay american holidays

@fran-worley I would have thought that the ember-native-class-polyfill package was needed to make this work? The tests are reportedly passing on 3.4 even without it though, which is curious.
The polyfill only supports Ember 3.4/3.5, as native class support was added in 3.6. It doesn't claim to work on 2.18 though. There may have been technical limitations at play here.

@richard-viney I didn't think we'd need it as if you look at the PR we're not using 'native classes' as such. I've converted it back to more traditional Ember Objects largely due to the limited support for the polyfill.

Ok, in that case is there a reason to keep writing
export default class Table extends EmberObject.extend({
    // ...
}) {};

instead of
const Column = EmberObject.extend({
    // ...
});

export default Column;

Is writing class here actually meaningful? The latter seems like it may be more backwards compatible if that's what we're going for. No idea if this is related to the test failures though!

@richard-viney I honestly have no idea - I did this so long ago now and it was a bit of a stretch as javascript is not my first language and the intricacies of classes vs ember objects hasn't ever really sunk into my brain!
I'll take another look this week and see if I can work it out.

To throw a spanner in the works...
I discussed this issue with @pzuraq this afternoon on Discord after I came across it in my app when upgrading to Ember 3.11. It seems that the recommended path (in the long term) for fixing this issue is to migrate away from EmberObject to native classes for these kind of utility classes.
By using native classes, it's also not a breaking API change since new can continue to be used (AFAIK, this PR mandates .create()).
However, I suppose it would be a breaking change since it drops support for at least Ember 2.18 (or whenever the native class polyfill goes back to).

@lougreenwood we talked about going down this route initially but with the native polyfill support being limited (and I've seen other addons encounter issues with it) and with the intention of this addon to move to conventional .create syntax (see https://github.com/offirgolan/ember-light-table/issues/444 ) we decided that the easiest option was to 'break' the api to use convention ember objects.
The road to pure native classes in ember is likely to be a while longer yet and depending on how it is implemented may end up 'breaking' our API anyway.

I now this is a WIP. Ember 3.11 totally breaks the addon. I'm trying to see if I can use this branch but Im running into an issue when occlusion is turned off. I basically get a compile error coming from lt-body.hbs. We're using angle-bracket invocation as well.

@lvegerano Are you configuring the ember-composable-helpers addon in such a way that excludes helpers needed by ember-light-table? E.g. by using its only config option? I believe it needs the compute helper at a minimum, is that the helper that's causing the exception?

@lougreenwood in addition to @richard-viney suggestion angle bracket syntax is as yet untested and I know people have reported issues with it. Our aim is to get the PR merged ASAP and then work on Angle Bracket Syntax support.

@richard-viney not really everything is default

I'm trying to use this branch in an ember 3.11.0 app however the same error occurs... Do understand it correctly it should fix the 'not instantiated correctly' problem?
package.json
"ember-light-table": "offirgolan/ember-light-table#refs/pull/701/head",

@basz This is what I'm using in package.json:
"ember-light-table": "github:offirgolan/ember-light-table#fw/native-classes-ember-obj",

Sorry for the silence on my part - I'm taking an executive decision to press ahead with this fix and therefore withdrawing support for Ember 2.18 (at least for the time being). With ember 3.12 having just been released as the new LTS I think it's more important we support the future than the past.
I believe the compile error issue you're experiencing is likely due to https://github.com/offirgolan/ember-light-table/pull/693 where I moved ember-composable-helpers to a dev dependency so I'll restore it and see where we get to.
I'm hoping to get this merged and a new beta release out this weekend and from there we can move onto to looking at Angle Bracket syntax etc.
@alexander-alvarez what is the situation with the documentation site as this change breaks the API. For now the best I can do is update the readme and put a warning notice on the master readme to advice people of the change in the v2x branch but we should update the main docs sooner rather than later

I'm hoping to get this merged and a new beta release out this weekend and from there we can move onto to looking at Angle Bracket syntax etc.
:+1:

@fran-worley once docs are updated pushing to gh-pages branch will release them. agree with getting the docs updated sooner rather than later, but need to make sure that it's clear what version is supported by the docs syntax

@basz This is what I'm using in package.json:
"ember-light-table": "github:offirgolan/ember-light-table#fw/native-classes-ember-obj",

I added this to my package.json and ran npm install.  But got the same error.  I deleted node_modules and reinstalled.  Still the same issue though.

Is there anything I am missing?

@jking6884 Do you any of the admins you're using depend on ember-light-table? If so. they may need to be updated. Trace the call stack to find the call to new Table() and then look into why the code is still doing that (it's no longer supported).

@alexander-alvarez is it possible to have 2 doc sites? one for the 1.x branch and another for the 2.x branch? I can see the 2.x branch deviating even further as we look to support angle bracket syntax etc.

@jking6884 Do you any of the admins you're using depend on ember-light-table? If so. they may need to be updated. Trace the call stack to find the call to new Table() and then look into why the code is still doing that (it's no longer supported).

Isn't this site intended to be 'documentation' of how to use the addon: https://offirgolan.github.io/ember-light-table/
`
init() {
this._super(...arguments);
let table = new Table(this.get('columns'), this.get('model'), { enableSync: this.get('enableSync') });
let sortColumn = table.get('allColumns').findBy('valuePath', this.get('sort'));

// Setup initial sort column
if (sortColumn) {
  sortColumn.set('sorted', true);
}

this.set('table', table);

},
fetchRecords: task(function*() {`

@jking6884 that covers v1 of the admin. This PR changes the API to be compliant with ember 3.11. See https://github.com/offirgolan/ember-light-table/pull/701#issue-283421279 .
Docs will be updated in due course but as we're all 'volunteers' please be patient!! 😅

@Kira-Pilot91 hey - it is but per the first comment https://github.com/offirgolan/ember-light-table/pull/701#issue-283421279 you need to change how you initialise your tables.
We still need to update the docs.

Will this also be merged into 1.x of ember-light table? Sorry for the late question but I just ran across this issue after upgrading to Ember.js 3.11.

I upgraded Ember.js from 3.10 to 3.11, and running ember-light-table 2.0.0-beta.4. My init function looks like this:
  init() {
    this._super(...arguments);
    let table = Table.create({ columns: this.get('columns'), rows: this.get('model') });
    this.set('table', table);
  }

But I still get the error:
Uncaught Error: Assertion Failed: You must call this._super(...arguments); when overriding init on a framework object. Please update <my-app-name@service:media::ember328> to call this._super(...arguments); from init.
Am I doing anyhting wrong, or is it related to this issue?

I found the issue, it is in issue of ember-responsive that is already fixed. So I guess just updating that library.

Is there a reason to use EmberObject instead of native classes? I thought that the latest version of Ember recommends using native classes, isn't it?

Time!! Our maintainers have very little of it!
We plan to start work on this soon and will release it as v3.x. See our development roadmap #739


release change branch-2.0 version to doris-2.0.4-rc04

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Docker build broken

docker build -t autosub . Cannot build and results in
Step 11/13 : RUN pip3 install --no-cache-dir -r requirements.txt
 ---> Running in bdf3fc44f538
Collecting cycler==0.10.0 (from -r requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/f7/d2/e07d3ebb2bd7af696440ce7e754c59dd546ffe1bbe732c8ab68b9c834e61/cycler-0.10.0-py2.py3-none-any.whl
Collecting numpy (from -r requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/45/b2/6c7545bb7a38754d63048c7696804a0d947328125d81bf12beaa692c3ae3/numpy-1.19.5-cp36-cp36m-manylinux1_x86_64.whl (13.4MB)
Collecting stt==1.0.0 (from -r requirements.txt (line 3))
  Could not find a version that satisfies the requirement stt==1.0.0 (from -r requirements.txt (line 3)) (from versions: 0.10.0a5, 0.10.0a6, 0.10.0a8, 0.10.0a9, 0.10.0a10)
No matching distribution found for stt==1.0.0 (from -r requirements.txt (line 3))
The command '/bin/sh -c pip3 install --no-cache-dir -r requirements.txt' returned a non-zero code: 1

I van make it work using python 3.6 and by downloading the release. Cloning the repo won't work. The developer made some mistakes in the code so it wasn't working anymore.
Em 19 de junho de 2022 20:51:59 UTC, Hallucinating Robot @.***> escreveu:

Ok, I would love to use this but after wasting two hours in Python versioning and dependency hell I didn't get it to work at all.
--
Reply to this email directly or view it on GitHub:
https://github.com/abhirooptalasila/AutoSub/issues/65#issuecomment-1159808783
You are receiving this because you are subscribed to this thread.
Message ID: @.***>

setup.py clearly requires python 3.6 or less as DeepSpeech's last supported python version was 3.6. The same goes for the docker build too.
@g3434343  what exactly are you referring to?


Indenting breaking block insert

Take this file:
let a=[
  'eins',
  'zwei',
  'drei']

Start vim in a clean mode: vim --clean -c 'set sw=2 et' file.vim
Go to the beginning of the single quotation marks, block select them and try to add `backslashes in front of them, so that it will become a valid expression:
ggjf'<C-V>2jI\ <ESC>
The file will look now like this:
let a=[
      \ 'eins',
  'zwe\ 'eini',
  'dre\ 'eini']

I think the problem is that typing the backslash triggers the indent expression to kick in and the block insert code did not expect that to happen.

On Mi, 04 Apr 2018, Christian Brabandt wrote:

Take this file:
let a=[
  'eins',
  'zwei',
  'drei']

Start vim in a clean mode: vim --clean -c 'set sw=2 et' file.vim
Go to the beginning of the single quotation marks, block select them and try to add `backslashes in front of them, so that it will become a valid expression:
ggjf'<C-V>2jI\ <ESC>
The file will look now like this:
let a=[
      \ 'eins',
  'zwe\ 'eini',
  'dre\ 'eini']

I think the problem is that typing the backslash triggers the indent expression to kick in and the block insert code did not expect that to happen.

Attached is a patch that fixes the issue including a test.
In addition, it fixes a misplaced comment.
Best,
Christian
"Was sind Tragödien anders als versifizierte Passionen solcher
Leute, die sich aus den äußern Dingen ich weiß nicht was machen?"
-- Goethe, Maximen und Reflektionen, Nr. 157


Keep name from sorted column tuple in sqla

This else clause is not needed since the column_name has been set earlier. However leaving it there break the tuple behavior where one might want to define a specific column name. My actual use case is to sort on Postgresql JSON column by using something like:
    column_list = ['price']
    column_formatters = {
        'price': lambda v,c,m,a: m.data['price']
    }
    column_sortable_list = [('price', MyModel.data['price'])]

Right now the price column is not set since the sortable column name is "('price', <sqlalchemy.sql.elements.BinaryExpression object at 0x7fac0ce2e320>)".

Hi @isra17,
the build is broken. Not a biggie. need to add workaround to install correct version of Postgist, flake8 got more stringent. There are too new requirements added: E722 and E741. You might need to add following changes:

to .travis.yml: https://github.com/flask-admin/flask-admin/pull/1556/files#diff-354f30a63fb0907d4ad57269548329e3 (to install correct version of postgis);
tox.ini https://github.com/flask-admin/flask-admin/pull/1556/files#diff-b91f3d5bd63fcd17221b267e851608e8 (to ignore E722);
flask_admin/contrib/sqla/tools.py: https://github.com/flask-admin/flask-admin/pull/1556/files#diff-70f36e099fa84f21ae730c1e207f8814 (to comply with E741 ambiguous variable name 'l');

That would fix the build.
Cheer!


Additional README with example for context->sentences and  entire document retrieval

It is easily possible to search within semantic contexts but display whole sentences or even entire documents as snippets via SELECT TEXT(?x). All that is needed is proper input as words- and docsfile. We should add some examples to clarify this. They do not need to be within the main README but shoudl be linked from there.

I think this has largely been obsoleted by the changes to the Readme


.email() does not respect UTF8SMTP Extension standard (which includes öäü aka. Umlaute)

Hello,
the RFC standard https://www.rfc-editor.org/rfc/rfc5336#section-3.2 allows users to use "öäü" and other special characters as part of their Email.
Further information here: https://stackoverflow.com/questions/15121359/are-international-characters-e-g-umlaut-characters-valid-in-the-local-part-of
.email() currently does not respect this nor does it provide the option to allow this extension specifically.
Therefore, the following email will fail unexpectedly<EMAIL_ADDRESS>The expected behavior would be, that validation would succeed.
Other examples for failing Emails include:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Via https://github.com/ajnart/homarr/issues/1747

@JacobWeisenburger  this is not an enhancement, but a bug IMO
As it incorrectly fails valid emails

Is anybody working on this right now? If not I might try picking it up this weekend

I would assume no. We are waiting for the upstream fix and sadly do not have capacity at the current time to fix this.

I agree this is an enhancement due to this being about supporting an extension. The built-in validators are provided as best-efforts, but like in the case of numbers being valid emojis, your use case might not be covered by the existing check. Feel free to use string().regex() with your own email regex if you feel stuck, or submit a PR: I'd be happy to review something that passed the existing tests and adds support for this extension. We might want to make this a separate email type (.emailUtf8?) to support users who do not support the UTF8SMTP extension (which is an experimental standard as best I can tell that has been superceded by RFC 6531).


Selection Tool needs deepwater-green

Error ModManager.cpp:1558: Error in assignID: tile with name 'deepwater-green' does not exist. It was removed by alien-biomes.
Source: railway_signalling_overseer_assume_correct_tool (selection-tool).

Thanks for the report, should be fixed in 1.1.26

Current Version this issue is back.

After testing, it occurs when you have "remove obsolete tiles" enabled in alien biomes.

that's not possible since the line that was producing the error is no longer present

dont know what to say, try enabling the option. my game forced me to disable this mod for this error.

and yes i'm on the latest version 1.1.26

the error must be different

Image of me having the option enabled

Image of me about to enable the mod with

the error occuring on mod load

its the same error

Alright, I see what's wrong. The file was still present in the factorio modpage distribution because I didn't delete it when updating the archive. Sorry for this mistake. 1.1.27 has the file removed and the error should be fixed.


Exception: AuthException(code=5, alertMessage='[HUMAN_VERIFICATION_REQUIRED] [HUMAN_VERIFICATION_REQUIRED] Required to resolve captcha.'

can you help solve it?

Duplicate of #4


feat(ux): open web ui at login

See https://github.com/ipfs-shipyard/ipfs-desktop/issues/1153#issuecomment-616243802.
Adds the option to open Web UI automatically on startup. This is enabled by default when the OS is neither Windows, nor macOS to help users that do not have a tray icon.
License: MIT
Signed-off-by: Henrique Dias<EMAIL_ADDRESS>

Rebased to be sure it works with the latest master and tests still pass.


DragonFly BSD supports sched_getaffinity() and sched_setaffinity()

Move CpuSet, sched_getaffinity(), and sched_setaffinity() from the sched_linux_like namespace to sched_affinity. Declare support for DragonFly BSD.
test_sched_affinity() passes locally on DragonFly BSD.

bors r+

bors retry


CVS output to abundance-test-single.py

In abundance-dist-single.py: Use CSV format for the histogram. Includes column headers.
And add a test function for the --csv option in test_scripts.py

[ ] Is it mergeable?
[ ] Did it pass the tests?
[ ] If it introduces new functionality in scripts/ is it tested?
Check for code coverage with make clean diff-cover
[ ] Is it well formatted? Look at make pep8, make diff_pylint_report,
make cppcheck, and make doc output. Use make format and manual
fixing as needed.
[ ] Did it change the command-line interface? Only additions are allowed
without a major version increment. Changing file formats also requires a
major version number increment.
[ ] Is it documented in the ChangeLog?
http://en.wikipedia.org/wiki/Changelog#Format
[ ] Was a spellchecker run on the source code and documentation after
changes were made?

Ready for review

LGTM


Mod Ordering

Please add mod ordering by "Last Rebuilt"

Note, this is referring to Mod Sources.

complete.


Negate format fields cache if we're adding the GT field

This is intended to resolve #130. In cases where the GT field isn't present in the original VCF, svtools VCF classes add it in. If this is the case then we can't utilize cached strings for the samples. Another strategy might be to cease to always add in the GT field, but the ramifications of that are less clear to me at this time.

Coverage increased (+0.1%) to 83.126% when pulling 4d3203e24d0bcc49c66243ebda63a8fea214e1ab on ernfrid:bedpe_genotype_fix into 84d6f36d3e1ccd500962c4ca8d2c8ab43dbc0201 on hall-lab:develop.

I don't think that's necessary. It will be constructed when accessed through get_gt_string() since calling _uncache_gts() populates the gts variable.

gotcha


inv pod.shell deprecation warning

inv pod.shell throws a deprecation warning:
$ inv staging pod.shell
kubectl exec -it deploy/pressweb-web -n pressweb-staging bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.

I just came across this for the first time on a 1.18 k8s cluster. I wasn't aware of it before, perhaps since the other clusters are 1.17.

I just came across this for the first time on a 1.18 k8s cluster. I wasn't aware of it before, perhaps since the other clusters are 1.17.


Help: communikation example

Hi,
could someone provide/link a communikation example between the shield and the T-Encoder.

I will upload a simple communication example for your reference later.

You can use UART to communicate with T-Encoder.

Could you provide an example for configuring UART?

I will upload an example later

https://github.com/Xinyuan-LilyGO/T-Encoder-shield/tree/main/example/Arduino/T-Encoder linkage

Thanks Alot!!


Fix "Load More" button styling

Addresses #29. Fixes the :focus state that results in a visually still-active button.

I'm a bit hesitant about this, as focus indication is still an accessibility issue on mobile. Can we maybe tweak the styling to still have a focus indicator but make it feel less like an active state (maybe by having additional styling when the button is pressed)?

That's actually what this fix does. The standard browser focus outline still shows up, but the :focus state no longer looks like the :active state. Bootstrap adds a border and changes the background-color in both :focus and :active states, so they look very similar. I'm removing Bootstrap's border and background-color changes, but retaining the browser's default focus outline.

Ah! Definitely reasonable.


Implement margin collapsing between siblings and with parent

Alright! I had a hard time figuring out the roles of ongoing_collapsed_margin.context.start and ongoing_collapsed_margin.context.end. I moved things around in that code to get myself familiar with it. Some of the changes are semi-gratuitous, feel free to only take some of them if you’d like.
I’m happy with this PR now. r+ on your commit, please merge after you have a look at mine.

The behavior should be the same as for your last push. If it’s not I made a mistake in the refactoring.


Release Google.Cloud.BigQuery.DataTransfer.V1 version 4.8.0

Changes in this release:
Documentation improvements

Updated comments (commit b8e05f5)

Created release for Google.Cloud.BigQuery.DataTransfer.V1-4.8.0


auth

Hello everybody,
I have potentially said something wrong during the review session.
You actually have to implement both of the authentication methods to get full points. I misremembered what the requirement was and mixed them up with last year.
It is also important that you do it in the order described by Adrian/Helge as they build on top of each other, it should be okay if you follow the steps in the book :)
You have probably already figured that out, but in case you haven’t now you know.
Good luck :)

Hey @PatNei - Thanks for the notice!
Both authentication methods are already implemented! :call_me_hand:


is there any plan to support eureka as EndpointGroup

hi @trustin, nowadays, spring cloud is pop, do you have any idea about that.

Sounds like a good idea to have EurekaEndpointGroup. We don't internally use it but we are interested definitely. Have you thought about sending a PR for it?

@trustin after few days investigation, we decide to postpone the feature to our backlog list, we'll keep updating here if there's any progress.

/cc @huydx

I will handle that

@eonezhang Hey~ Are you still interested in this? I created #2701 and want to see if it's working well. 😄

Fixed via #2701


Communications rework

Rework of the front-end and back-end networking code. This branch is still undergoing work to merge with the latest changes in the main branch without breaking anything.
Main goals of this change:

Simplify front-end and back-end message API by using consistently structured data
Consolidate front-end API message logic to a single file to reduce the mental load of debugging or adding new APIs
Minimize the changes to prevent disrupting the team's workflow

Change notes & rationale:

Frontend communication logic has been consolidated to a new file named CommEvent.ts. This file is the single source of truth for the API between the frontend and backend. The intention is to make it easier for the team to find the message schema for an event without having to jump around between different React component files.
Message payloads look like this: { "event_id": "id", ...data } For example, to change to a topic named "Nationality" the payload looks like { "event_id": "change_topic", topic: "Nationality" }
The backend event loop has been accordingly refactored. Every event received is expected to have an event_id to determine how to handle it.
TypeScript support has been added to the frontend build. It is currently only used in CommEvent.ts to validate data types for API messages. All previously existing JS code remains JS.

Other / misc changes:

Created a folder named development/ that holds files related to dev tools. build_wheel.py has been moved there. I have also provided an example vscode launch.json file that I use for attaching the debugger for both frontend and backend.

Hi Nick. Overall this seems to look good. Thanks! Have you tested topic deletion? That used to be implicit through the use of a topic for the key, and just want to make sure that still works as expected.

Nevermind I saw you mentioned testing this in the chat.

When I run this I don't get any pass/fail totals for the topics

Do you see these?

When I run this I don't get any pass/fail totals for the topics
Do you see these?

I see that whenever the model score is null. I'm not sure why that happens or if it's related to the communications rework. I have seen this issue on multiple branches so far. I'll look into it and try to track down the issue.

I found the issue I was having was just the local labeling model returning "Unknown" instead of pass or fail. So I fixed that.


Minor bug fixes for Python SDK

This pull request add these changes:

Use tmp dir when creating a temporary parquet file with a fixed row_group_size.
Tweak int -> ceil when determining row_group_size when creating temporary parquet file.
Changed imap_unordered to imap so that results returned by pool workers are ordered.

/retest

/retest

/retest test-end-to-end-batch

/retest

/lgtm


docEnhancement in the hyperlinks

Modified some hyperlinks in the readme file.

Codecov Report

Merging #6315 (1caff20) into develop (7b23042) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #6315      +/-   ##
=============================================
- Coverage      43.14%   43.09%   -0.06%
+ Complexity      8860     8854       -6
=============================================
  Files           1094     1094
  Lines          77284    77284
  Branches       10085    10085
=============================================
- Hits           33347    33307      -40
- Misses         39771    39809      +38
- Partials        4166     4168       +2

see 13 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


chore(ci): fix labeler again

Apparently we need the "all" top-level label here, which seems to fail config validation.

Current dependencies on/for this PR:

main

PR #872   👈

This stack of pull requests is managed by Graphite.

See https://github.com/actions/labeler/issues/746


Issue cancellations into the TypeScript language server directly

Here you can see what the typescript language server client attempts on request cancellation - it removes a queued request from the queue if it is as yet unsent, and otherwise does nothing. However on large codebases, inflight requests for things like full-file errors can take a long time. To cope with this, tsserver can read an external cancellation token, should one be provided. This is throttled by the language service so it is not checked too frequently.
Properly implementing this should just be a matter of writing the specified file or pipe to disk here (for example /pipe/someUniquePipePath251, where 251 is the request sequence number), and launching tsserver here with --cancellationPipeName /pipe/someUniquePipePath* (The * to indicate per-request cancellation triggers).
Doing so should improve the vscode editing experience in large projects. This should be supported from tsserver version 2.2 and up.

Wew, that's what I get for looking at things at midnight - followed a link to an outdated version of the vscode source; this has already been implemented. Thanks!


Delete fails on OpenShift when trying to parse version

OpenShift returns 1.11.0+d4cacc0 as the gitVersion in the GET /version endpoint.
That can't be parsed by Gem::Version.
I, [2019-06-04T19:00:07.060615 #62646]  INFO -- K8s::Transport<https://master.devel-311.3sca.net:8443>: GET /version => HTTP 200: <K8s::API::Version> in 0.042s
ArgumentError: Malformed version number string 1.11.0+d4cacc0
from /Users/mikz/.rubies/ruby-2.4.2/lib/ruby/2.4.0/rubygems/version.rb:208:in `initialize'
 "/Users/mikz/.rubies/ruby-2.4.2/lib/ruby/2.4.0/rubygems/version.rb:208:in `initialize'",
 "/Users/mikz/.rubies/ruby-2.4.2/lib/ruby/2.4.0/rubygems/version.rb:199:in `new'",
 "/Users/mikz/.rubies/ruby-2.4.2/lib/ruby/2.4.0/rubygems/version.rb:199:in `new'",
 "/Users/mikz/.gem/ruby/2.4.2/gems/k8s-client-0.10.0/lib/k8s/transport.rb:355:in `need_delete_body?'",
 "/Users/mikz/.gem/ruby/2.4.2/gems/k8s-client-0.10.0/lib/k8s/transport.rb:275:in `request'",
 "/Users/mikz/.gem/ruby/2.4.2/gems/k8s-client-0.10.0/lib/k8s/resource_client.rb:312:in `delete'",
 "/Users/mikz/.gem/ruby/2.4.2/gems/k8s-client-0.10.0/lib/k8s/resource_client.rb:346:in `delete_resource'",
 "/Users/mikz/.gem/ruby/2.4.2/gems/k8s-client-0.10.0/lib/k8s/client.rb:267:in `delete_resource'",

Wow. That was fast 😍 Good 🥇


Can't run information_schema queries

If I run a query like:
SELECT table_comment FROM information_schema.tables

I get an error with something like: "No such keyspace id: information_schema"
The easiest is just to pass these queries on to the MySQL server.

Can you post the exact error message? I think vttablet will allow information_schema queries. It's likely that this is failing at the VTGate layer.

Actually I think it does work. I think the issue is that it uses a named and not positional bind parameter which doesn't seem to be supported by the JDBC driver.

Nope, you're right it does work now.

So we probably do want to expose this some better way after all. I just started experimenting with vertical resharding and created a keyspace with a served_from. The work around for running information_schema queries in the JDBC driver (just to run them against tablet 1) doesn't work in this case because there is no tablet 1. Maybe I can get around with by consulting GetSrvKeyspace but then it's starting to get messy. We should probably track that with a different issue though of course.

I'll reopen this to track the end to end feature request.

I'm also interested in this and other system tables, such as mysql.user

@tirsen #2646 should allow you to connect to a specific keyspace/shard and run information_schema queries. Let me know if this will be sufficient.

With #2815, you should be able to run information_schema queries through the use function or by also specifying keyspce:shard as the target.

Does this work automatically for unsharded keyspaces?

Ahh. Forgot about this use case. Let's keep the issue open till it's addressed.

#2858 should address this now.


make install - No rule to make target 'install'.

I get the following error when doing a make install - it fails on mission-install.
Install the project...
-- Install configuration: "debug"
-- Up-to-date: /home/elliot/obc/src/cFS/build/exe/cpu1/cf/cfe_es_startup.scr
-- Installing: /home/elliot/obc/src/cFS/build/exe/cpu1/core-cpu1
-- Up-to-date: /home/elliot/obc/src/cFS/build/exe/cpu1/cf/pe.so
-- Up-to-date: /home/elliot/obc/src/cFS/build/exe/cpu1/cf/img.so
Built target cpu1-install
make[5]: *** No rule to make target 'install'.  Stop.
CMakeFiles/mission-install.dir/build.make:57: recipe for target 'CMakeFiles/mission-install' failed
make[4]: *** [CMakeFiles/mission-install] Error 2
CMakeFiles/Makefile2:195: recipe for target 'CMakeFiles/mission-install.dir/all' failed
make[3]: *** [CMakeFiles/mission-install.dir/all] Error 2
CMakeFiles/Makefile2:202: recipe for target 'CMakeFiles/mission-install.dir/rule' failed
make[2]: *** [CMakeFiles/mission-install.dir/rule] Error 2
Makefile:181: recipe for target 'mission-install' failed
make[1]: *** [mission-install] Error 2
Makefile:117: recipe for target 'install' failed
make: *** [install] Error 2

Insufficient information to debug issue.  Please utilize the bug report template and include all information (versions being used, steps to recreate, etc.)


Fix runtime typings.

Submodules (e.g. with a "/" in them) don't work with declare module in a foreign npm package. This PR fixes the that by renaming the typings file to runtime.d.ts, so it will be used when importing offline-plugin/runtime.

@odensc so with this change it works for you now, right?

Yes. :) Current version (4.8.0) did not work, but I can confirm it works with these changes.

Okay, I'll merge it. Btw, what version TypeScript you were using?
I don't use TypeScript for a while so I'm not able to test this versions as wasn't able to test previous one.

I was using the latest, 2.3.2. Not sure if something changed since the original PR.

Okay, thank you for the PR! 👍

https://github.com/NekR/offline-plugin/releases/tag/v4.8.1

Great, thanks!


[ISSUE-21] Implemented support for reflection in 'No Dependencies Transformer'

Processing essential calls with potentially dynamically constructed strings.
With this fix the following calls are intercepted and forwared to generated package private 'utility classes':

Class.forName()
ClassLoader.getResource*()
ClassLoader.loadClass()
ClassLoader.getSystemResource*()

Sorry, I was busy with f2f + other things last week. will review this now.

@ropalka looks good to me, not that I understand everything that you are doing.  Merging.


Deriver for Party, Parties

this is intended to be the PR that finalizes the deriver for Parties.t, which is the top-level snapp tx structure
It is currently stacked on top of #10203 which could be either reviewed & merged first or abandoned
EDIT: It is now also stacked on top of  #10180

Ready to review!


Update To Ubuntu 21.04

Please Update To Ubuntu 21.04

we are using proot-distro for installing ubuntu...and now its on 21.04


Prometheus rule reporting node NotReady is failing

Describe the bug:
Alertmanager is not sending alerts when a node is unhealthy (marked NotReady).
To Reproduce
Steps to reproduce the behavior:

Start a new cluster
Deploy otomi
Mark a node NotReady? How?
Observe: no alerts triggered

Expected behavior:
A prometheus rule to trigger an alert.

Hi,
So I marked a node NotReady on eks.gk-test, but I see the alert firing:
[FIRING:1] Notification for cluster "otomi/aws/gk-test"
Description: ip-192-168-13-210.eu-central-1.compute.internal has been unready for more than 15 minutes.
 Graph: :chart_with_upwards_trend: Runbook: :spiral_note_pad:
 Details:
  • alertname: KubeNodeNotReady
  • cluster: otomi/aws/gk-test
  • condition: Ready
  • endpoint: http
  • instance: <IP_ADDRESS>:8080
  • job: kube-state-metrics
  • namespace: monitoring
  • node: ip-192-168-13-210.eu-central-1.compute.internal
  • pod: prometheus-operator-kube-state-metrics-5c44f58f6c-cmctr
  • prometheus: monitoring/po-prometheus
  • service: prometheus-operator-kube-state-metrics
  • severity: warning
  • status: true

https://apps.gk-test.eks.otomi.cloud/alertmanager/#/alerts?receiver=default.  (login with admin as oidc is not gonna work for this cluster).
I think the alert will not fire if prometheus/alertmanager pods were scheduled on the troubled node ... accounting for overcommitment, if the pods can't be rescheduled then, there's no way to trigger any alerts.
My guess is that alert is configured correctly, but the pods can't be scheduled if there's no cluster-autoscaler enabled.

P.S. for repeating this process you can do the following:

ssh into a node using private certificate generated on cluster creation
break kubelet configuration so it will fail on restart
observe status NotReady on node
observe alert if prometheus+alertmanager pods are running

great observation...last year we introduced a higher priorityclass for otomi-core pods, and at that time I was convinced by Taco (who added it) that there should be no need for multiple priorityclasses. Maybe we should have multiple? and make sure prometheus-operator chart pods get highest?
Shouldn't lower prio pods get evicted to redeploy higher prio pods? I think it works like that. So then we should introduce another PriorityClass.

closing this as it is assessed to be of type "kubernetes scaling problem" which sometimes occurs when scaling is not enabled or not working for some reason (limits reached etc).

Is this related: https://github.com/SUSE/doc-caasp/issues/684?

Please corroborate by trying the suggestion from the link


ci: add MS Teams notifications

Description
Add MS Teams notifications about issues in crow GH workflow.

hm... i didn't think about this :)
yeah. let's create fork!

Here it is!
https://github.com/aquasecurity/notify-microsoft-teams

@knqyf263  I created PR for fork - https://github.com/aquasecurity/notify-microsoft-teams/pull/1


HTTP header names are case insensitive

HTTP header names are case insensitive. The "X-RateLimit-Remaining" header was changed to "x-ratelimit-remaining" in the API. See http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

Thanks!


Enhancement: Switch to official msgpack media type

Summary
As of May 2024, msgpack has an officially registered IANA media type: application/vnd.msgpack. Litestar should switch to using that in msgpack responses (and accepting it in request bodies), probably in v3.0, as changing the response media type is a breaking change.
Reference: https://www.iana.org/assignments/media-types/application/vnd.msgpack
Basic Example
No response
Drawbacks and Impact
It would be great to also accept the old media type in requests but only output the new one.
Unresolved questions
It's not obvious to me how to accept two different media types as msgpack data.

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

Completed in #3732.


Can O' Spam: Watch skuplugs.com

Can O' Spam requests the watch of the watch_keyword skuplugs\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

skuplugs\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Document Algorithms and Functions better

I am having a hard time understanding what all those functions of this library are used for and which one I should use.
It would be good to have a broad explanation of the algorithm, it's uses and maybe a link to some resources, that explains it in further detail. Maybe also list the advantages and disadvantages?
You could also include some real world examples
For example, how could I improve this simple search function with strsim, to not only find exact matches, but also very similar matches;
fn search(list: Vec<&str>, value: &str) -> Option<&str> {
    for x in &list {
        if x == value {
             return Some(x);
        }
     }
     return None;
}

Maybe this could be useful https://medium.com/@appaloosastore/string-similarity-algorithms-compared-3f7b4d12f0ff

As a starting point for docs we can use the docs I have already written for rapidfuzz-rs here: https://docs.rs/rapidfuzz/latest/rapidfuzz/distance/index.html
The readme should probably guide people to either strsim, rapidfuzz or the reference implementation (once written) depending on the users requirements.


Retain the cache after connection timeout (EXPOSUREAPP-3912)

If we run into a connection time while downloading the hour index, we must not delete the cache but return an unsuccessful result instead.

Has to be decided if it is 1.7.1 relevant.


Liquibase 3.10+/4.1+ missing UniqueConstraints in snapshot

Environment
Liquibase Version:
4.1.0
Liquibase Integration & Version:

Liquibase Extension(s) & Version:
liquibase-hibernate5, version 4.1.0
Database Vendor & Version:
Postgres, 12 (running in a docker container based on the postgres:12 container)
Operating System Type & Version:
Linux, Ubuntu 20.04/CentOS 7+  (local/buildserver)
Description
When building a snapshot of a Postgres Database (seemingly any non-Oracle and non-MSSQL database) only the first four uniqueconstraints get loaded. All others are ignored because liquibase switches to a bulk "get-columns-for-uniqueconstraint" query but saves the results under the wrong cachekey, leading to no columns for the uniqueconstraints when the cached entry is then read, which in turn leads to the uniqueconstraint getting ignored.
This is especially noticeable if this snapshot gets compared/diffed against a snapshot that does read in all uniqueconstraints, since it will report a mismatch (provided the databases have more than 4 uniqyueconstraints).
In our specific case we use liquibase-hibernate5 to build a reference snapshot based on our JPA annotations, and compare this against a postgres database that has run all liquibase changelogs. If those database match, our liquibase changelogs is complete, if not, we need to add changesets.
However, due to this bug liquibase now incorrectly reports 33 out of 37 uniqueconstraints as missing in the postgres database.
This seems to be the caused by https://github.com/liquibase/liquibase/commit/bebbb6eeec29f857b321704f3705eb8e683b4079 (#1199 ), where the logic to batch select the columns for uniqueconstraints gets expanded to all database (instead of just oracle and MSSQL) but the "CONSTRAINT_CONTAINER" field didn't get included in the select of the actual queries, leading to results being saved under the cachekey "null_uq_mytableconstraintname" instead of "myschema_uq_mytableconstraintname".
Upon loading the results, liquibase does look for the correct "myschema_uq_mytableconstraintname", gets a result of null despite and deduces there are no columns therefore the uniqueconstraint should not be added to the snapshot.
Steps To Reproduce
Create a DatabaseSnapshot based on a fully initialized (ie, all changelog run) postgres database, create a DatabaseSnapshot based on a hibernate/jpa annotations "database" (or a fully initilized oracle or mssql database, as long as it is guaranteed to include all uniqueconstraints). (Make sure their should be >4 uniqueconstraints present).
Run a diff on the two snapshot using the liquibase DiffGenerator.
Actual Behavior
The diff reports a difference in uniqueconstraints caused by the postgres database snapshot having fewer unique constraints than the other snapshot.
Expected/Desired Behavior
Both databasesnapshots should have the same uniqueconstraints.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
┆Issue is synchronized with this Jira Bug by Unito

The actual code we use to build the snapshots and create the diff is something like:
		Liquibase liquibase = LiquibaseFactory.create(null, connection, classloader, defaultSchema);

		database = liquibase.getDatabase();
		JpaPrebuildDatabase hibernate = new JpaPrebuildDatabase(emf);
		hibernate.setConnection(new JdbcConnection(new HibernateConnection(
			"jpa:prebuild:/META-INF/persistence.xml?hibernate.dialect=" + dialect.getName(),
			liquibase.getResourceAccessor())));
		SchemaComparison[] schemaComparison = new SchemaComparison[] {
			new SchemaComparison(hibernate.getDefaultSchema(), database.getDefaultSchema())};
		CompareControl compareControl = new CompareControl(schemaComparison,
			"column,foreignkey,index,primarykey,table,view,sequence,uniqueconstraint");

		DatabaseSnapshot referenceSnapshot = SnapshotGeneratorFactory.getInstance()
			.createSnapshot(hibernate.getDefaultSchema(), hibernate,
				new SnapshotControl(hibernate));

		DatabaseSnapshot comparisonSnapshot = SnapshotGeneratorFactory.getInstance()
			.createSnapshot(database.getDefaultSchema(), database, new SnapshotControl(database));

		DiffResult diff = DiffGeneratorFactory.getInstance()
			.getGenerator(hibernate, database)
			.compare(referenceSnapshot, comparisonSnapshot, compareControl);

Where LiquibaseFactory just searches the classpath to find the correct classes for the type of database we provide it (in the connectstring) and JpaPrebuildDatabase is based upon the HibernateEjb3Database from liquibase-hibernate5 .


Updated 404 page, Add to App router

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on creating a new NotFoundPage component for handling 404 errors, replacing the previous implementation in 404.tsx. It enhances the user experience with a more structured layout and design.
Detailed summary

Introduced NotFoundPage component in components/not-found-page.tsx.
Implemented a structured layout with a 404 message and links to the homepage, dashboard, and developer portal.
Added Aurora component for background effects.
Updated 404.tsx to use the new NotFoundPage component instead of the previous layout.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5387  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


This pull request adds the TiRKiO Jekyll theme to the themes directory.

Changes:

Updated themes.yml with the following entry:

Name: TiRKiO
GitHub Repository: flavioaiello/tirkio-theme
Demo URL: https://www.tirkio.com/
Author: Flavio Aiello
Thumbnail: tirkio.png
License: MIT
Tags: [multi-purpose, multipage, bootstrap, responsive, personal, blog, business, mobile-friendly, SEO, clean, simple]

Added a 250 x 200 thumbnail image (thumbnails/tirkio.png).

Please let me know if any additional changes are required.

@flavioaiello   thanks.  fyi - sorry to tell you this jekyll theme directory is out-of-service (no longer getting updated)  all the best. cheers.


ref #193: remove licenseManager orphan files

Q
A

Branch
master

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed issues
chameleon-system/chameleon-system#193

License
MIT

Remove licenseManager orphan files which are not used since 6.1 and don't have any need in the core alone.

Do not merge yet - see https://github.com/chameleon-system/chameleon-system/issues/193#issuecomment-438638297

I updated the PR to delete the files now.

Could you solve the merge conflicts?


CB-18478: Re-enable the SDX resize recovery e2e tests.

Jira: https://jira.cloudera.com/browse/CB-18478
I have verified that the test is working locally at the very least and am sure that the original issue faced during testing is resolved.

"am sure that the original issue faced during testing is resolved."
Could link the change that you think fixed the issue?

"am sure that the original issue faced during testing is resolved." Could link the change that you think fixed the issue?

Yes of course, I apologize for not doing this earlier.
Jira: https://jira.cloudera.com/browse/CB-18324
PR: https://github.com/hortonworks/cloudbreak/pull/13317


Allow underscores as unused variable identifiers

Code like this should compile:
let size: Int = 0;
foreach (_, _ in map) {
    size += 1;
}

and the _ id in this case should not be resolved, right?

and the _ id in this case should not be resolved, right?

yep, this is correct


Add rate runner

Result = [(0, 607.2989, np.float64(0.0035)), (50, 419.5706, np.float64(0.4804)), (100, 2274.2178, np.float64(0.8904))]

@XuanYang-cn This is interesting, but I don't see the ReadWriteRunner being used and neither did I find any documentation around it, can you please guide what this is intended for?

@wahajali we are currently in the process of designing and developing the streaming case.
Our primary focus is testing vector database performance in real-time insertion and querying. Please note that this pull request is just one component of the overall project.

@alwayslove2013 Thank you for the clarification. This sounds like a very exciting use case, and I’m particularly interested in real-time insertion and querying scenarios. If possible, I’d love to know if there’s an estimated timeline for this or a chance to preview any early work via some branch. I completely understand that this is a work in progress and part of a larger effort — just very eager to follow along and explore!


Write ms

Hi Tim,
I checked the codes again and modified the arguments of the function.  I think the codes could pass the check of Jetkins.
Feng

Great. I’m on holiday at the moment. Will check it when I get back.

Glad to see this fixed b


Body polymorphism (closed edition)

We should aim to handle lots of different types of body, rendering appropriately.
Based on http://rigsomelight.com/devcards/#!/devdemos.extentions
Initially, this set of types is closed - a future enhancement will be allow open extensibility of supported types.

[x] string - markdown
[x] number - a number - see #6
[x] array - pretty and syntax highlighted - see #6
[x] object - pretty and syntax highlighted - see #6
[x] regex - pretty and syntax highlighted

[ ] Include a little box you can type in that displays matches?

[x] date - ISO8601
[ ] ES6 Map / Set - pretty and syntax highlighted - see #6
[ ] ImmutableJS objects - pretty and syntax highlighted - see #6
[x] ReactElement - rendered
[ ] function - is called, return value then handled as if it was passed - see #8
[ ] js-atom - value is rendered, re-rendered when it changes

Duck type anything with deref & addWatch

Started on this, WIP so far: ddc78a6

Syntax highlighting added in a8601c3

Built-in type checking libs i've found:

https://www.npmjs.com/package/is-date-object
https://www.npmjs.com/package/is-regexp
https://www.npmjs.com/package/is-set
https://www.npmjs.com/package/is-map


Shortcut to second to last copied item

Quickly pasting the second to last item
I would love the ability to quickly paste--using a new shortcut such as CMD+ALT+V (just as an example!)--the second to last copied item. I believe it would be very beneficial for my workflow.
Reasons
I also think it would be a nice feature in general because:

It would not be disruptive in any way for existing workflows (just an additive feature).
Based on the principle of locality of reference (temporal, in this case), pasting the second to last copied items should reasonably be something done quite often.
Having to open the menu just to quickly paste something that you know you copied a couple of seconds ago creates a small but noticeable workflow disruption that would be easily avoidable with an ad-hoc shortcut.

On this last point I will add, though this may not resonate with everybody, that the mental context switch associated with opening the menu is not insignificant for me. My mind has the tendency to wander and even a quick glance at something I copied earlier is sufficient to distract me a little bit, so if I could avoid it even just in the 20% of cases where I know I need to paste the last two items I copied (e.g. name and password, switching two lines of code, etc), it would be nice.
Link to other issues
Lastly, I absolutely agree that going further than that, adding shortcuts to more items than the second to last (such as what was suggested in #315) could be overkill and would create problems.
Example use case
Copying and pasting username and password:

Copy username
Copy password
CMD+V to paste password
CMD+ALT+V to paste username (instead of having to open a menu and select an item)

In the next version of Maccy, there will be support for Shortcuts (as long as you run macOS 11+). So far it's very basic but allows to automate selecting/pasting the clipboard history item by its number like this.

Any shortcut workflow can be called from menu bar, Dock or have a global shortcut.


Manual: Add paragraph on xserver keyboard layout

Motivation for this change
When I installed nixos for the first time, I was confused why the xserver keyboard layout didn't work out as expected, so I wanted to give the kind of correct example in  the manual that would have been helpful.
Things done

[ ] Built and tested manual

Did you mean the checkbox to be checked (i.e., have you succeeded building the manual)?

Oh, rare event, Travis build has succeeded!

Ah, indeed.


#77 epic games response data process improvements

Added 'dict_search' function for easy traversal through dictionary tree. Either returns node in given path or None
Made epic games api call response handling more flexible:

problem: product_slug location differs from product to product. Previously response parser tried to find it from single predefined path that failed for some products
resolution: using new dict_search added all known paths that could contain product slug. If no product slug is found, link to the free games offer page is added to that games heading link instead

Auto-merge on päällä. Jos olisi hyvä korjata tai uudelleenarvioida jotain, niin älä laita approvalia.


Prevent trace! body being executed when log level is smaller

Signed-off-by: Breezewish<EMAIL_ADDRESS>
What have you changed? (mandatory)
See https://github.com/tikv/tikv/issues/3537 for details.
Also, this PR prevents trace! cost totally at compile time.
How has this PR been tested? (mandatory)
Manually.
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No. The configuration already has:
# log level: trace, debug, info, warning, error, critical.
# Note that `debug` and `trace` are only available in development builds.
# log-level = "info"

Does this PR affect tidb-ansible update? (mandatory)
No.
Refer to a related PR or issue link (optional)
Fix https://github.com/tikv/tikv/issues/3537
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

/run-integration-tests

any performance gain?

@siddontang Not tested yet. I'm going to bench my tokio branch first.

Seems that doc tests on CI failed because of renaming packages. I will fix it.

Updated implementation to use only one logger instance.
About tests:
I tried to add some tests but failed, because log! only allows setting logger once (wired).
About benchmarks:
The benchmark shows a 1% to 5% improvements. Considering errors, the effect of reducing trace! might not be very notable.

@breeswish
Seem that we can provide a function like init_with_level instead of default https://github.com/slog-rs/stdlog/blob/master/lib.rs#L133, so we pass a MaxLogLevelFilter explicitly and no need to maintain our own log library.

@breeswish
Although the performance doesn't increase, I still think we must do this to avoid log body evaluation.

@breeswish
I have already filed a PR to support initialization with level, see https://github.com/slog-rs/stdlog/pull/6
seem that @dpc is busy, so if you are LGTM, I can merge directly and release a new version :-)

@Hoverbear
seem we need to degrade the log version from 0.4 to 0.3 in raft-rs, so we can record the file name instead of Unknown in the log.
I will try to support 0.4 for slog later.

@siddontang Not showing file name in raft actually is not a matter, since we know that it's from raft.


FW-1432 Upgraded react-redux: ~4.4.5 -> ^5.0.0

NOTE: Duplicated the Redux upgrade change from https://github.com/First-Peoples-Cultural-Council/fv-web-ui/pull/319

Note: merge after https://github.com/First-Peoples-Cultural-Council/fv-web-ui/pull/319

Let's hold off on merging them until release 3.4.2 is complete.

Hi @elysse-fpcc since the upgrade for react-redux from 4 -> 5 and from 5 -> 6 didn't trigger any obvious bugs it makes sense to just review the PR for 5 -> 6. Going to close this PR and will re-open if necessary


updating path to actual result directory

(You can replace all of this text with your description.)
Before creating your pull request, please check your content against these quality criteria:

Did you consider search engine optimization (SEO) when you chose the title in the metadata section and the H1 heading (i.e. the displayed title that starts with a single #)?
For new articles, did you add it to the table of contents?
Did you update the "ms.date" metadata for new or significantly updated articles?
Are technical terms and concepts introduced and explained, and are acronyms spelled out on first mention?
Should this page be linked to from other pages or Microsoft web sites?

For more information about creating content for docs.microsoft.com, see the contributor guide at https://docs.microsoft.com/contribute/.

@floreseken : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change.


What is the performance?

Do you have a benchmark for Nginx with PHP 7 vs Swifter?

@wildfiremedia we don't have any benchmarks.


[Bug]: In Active tab the delete menu is displayed even when we dont have delete access for a database

Is there an existing issue for this?

[X] I have searched the existing issues

Description
In Active tab the delete menu is displayed even when we dont have delete access for a database

Steps To Reproduce

create a app
create a database
now give edit, create and view access to it
now assign this role to user 1
Login as user 1
Go to active tab
click on meat ball icon next to database
The delete menu is enabled even when the access is not given

Public Sample App
No response
Issue video log
No response
Version
localhost

The FE changes are done, but this also needs BE change.  Even after removing the said permissions, client still gets it from the server.
https://www.loom.com/share/3229293f81bf452e838cc7d4f4593d27
@trishaanand @RakshaKShetty


[WIP] Add ChatAgent and Evaluator

This is the bare bones of a higher level abstraction that can support various higher level functionality with an AI Model.
The main abstractions are a ChatAgent that takes uses multiple PromptContextTransformers as collaborating objects.  A PromptContextTransformer is a function that takes a PromptContext as input and output.
The implementation DefaultChatAgent can handle many use cases.  It allows one to build an agent that can invoke functions (at the moment contained in the prompt) and execute various RAG algorithms.  Augmentation can come from Node implementations, which are Documents and Messages.  Augmenting Messages would be done for the case of including chat history into the prompt.
A fluent builder API for DefaultChatAgent puts PromptContextTransformers into different collections so that they can be executed at the right time in the default workflow inside the agent's call method.  The DefaultChatAgent also contains a list of listeners that are invoked at the end of the ChatAgent's work so that state in external systems (such as a MessageHistory or MessageStore) can be updated.
There is a new Evaluator interface and one implementation RelevancyEvaluator
The test class OpenAiDefaultChatAgentIT minimally exercises this new functionality.
Open issues to consider:

Adding a list of functions availalbe for the Agent to call can be achieved by transforming the prompt and adding function, but mayb
PromptContext is currently mutable, this made implementation easy but we may want to consider returning a copy of a PromptContext from the transformer.
MessageHistory has not been implemented.

Replaced by #634


More consistent handling for table without frame attribute specified on it

Let's say I have a DITA table without the @frame attribute set on it. In the HTML output the table has no frame, in the PDF output it has a frame.
What should be the proper behavior? Unfortunately the DITA 1.3 specs does not seem to state what the default frame value is.

:+1: for frame="all" everywhere

This is the kind of thing the specification intentionally avoids for most elements (specifying what the default rendering should be), but I'd agree we should be consistent. I seem to remember being confused at some point because XHTML and PDF had always put on a frame by default, and I noticed HTML5 did not, but then forgot about the issue because I was working on something else at the time.


Cannot insert date before 1970

A field having the type "time.Time" is mapped to a timestamp in MySQL.
Thus, the MySQL timestamp is the number of seconds after 1970. Every "time.Time"  before 1970 is recorded as "0000-00-00 00:00:00" in MySQL.

My bad, just need to add: gorm:"type:date"

My bad, just need to add: gorm:"type:date"

Thank you so much!! It helps me a lot.


weird spacing below the comments

There is a weird spacing going on after the coments section in no-comment as well as 1-or-more-comment situations:

The code of the space between the comment form and the rest of the page is:

...

If I remove input-top from the classes the spacing goes down. I am using Bootstrap 5, but there is nothing that might add any particular spacing to input-top. Maybe it's not required at that point?
If you want to test it on a live implementation go to my site.
Is this an issue with giscus CSS or does my own CSS somewhere break things?

Fixed in #449.


tRNA-dihydrouridine synthase EC xrefs to add

id: GO:0102267
name: tRNA-dihydrouridine20b synthase activity
namespace: molecular_function
def: "Catalysis of the reaction: a 5,6-dihydrouracil20b in tRNA + NAD(P) <=> H+ + a uracil20b in tRNA + NAD(P)H." [EC:<IP_ADDRESS>, GOC:pz]
xref: MetaCyc:RXN-12476
is_a: GO:0017150 ! tRNA dihydrouridine synthase activity

[x] add EC:<IP_ADDRESS> "tRNA-dihydrouridine(20a/20b) synthase [NAD(P)(+)]."

===
id: GO:0102262
name: tRNA-dihydrouridine16 synthase activity
namespace: molecular_function
def: "Catalysis of the reaction: a 5,6-dihydrouracil16 in tRNA + NAD(P) <=> H+ + a uracil16 in tRNA + NAD(P)H." [EC:<IP_ADDRESS>, GOC:pz]
xref: MetaCyc:RXN-12454
is_a: GO:0017150 ! tRNA dihydrouridine synthase activity
is_a: GO:0140101 ! catalytic activity, acting on a tRNA

[x] add EC:<IP_ADDRESS> "tRNA-dihydrouridine(16/17) synthase [NAD(P)(+)]. "

Hi @edwong57
A few more things I just noticed:

[ ] reactions should have "=" and not "<=>"

Also, it looks like we are missing some RHEA xrefs: https://www.rhea-db.org/rhea?query=ec%3A<IP_ADDRESS> (2 RHEA per term, one for the NAD and one for the NADP-dependent reaction), both 'narrowMatch'

[ ] We cannot use the same defxref for several terms, so please remove EC:<IP_ADDRESS> from the defxref of GO:0102262  and GO:0102263.
[ ] EC:<IP_ADDRESS> should have source= skos:broadMatch in the cross references of GO:0102262  and GO:0102263.
[ ] likewise for terms with EC:<IP_ADDRESS>
[ ] and please add RHEA xrefs: https://www.rhea-db.org/rhea?query=ec%3A<IP_ADDRESS>

Thanks, Pascale


Fixed standalone version compilation issues

Operators had to be compiled with /unsafe option
Some dependencies (OpenGL, CppSharp) were missing in the StartT3 project

Thanks!


HTTP: Fixed accessor to accept $request->get()

$request->get('foo') is actually a good answer.
Ref https://github.com/symfony/symfony/blob/v3.0.4/src/Symfony/Component/HttpFoundation/Request.php#L722-L724

@lolautruche wow :) Thank you Jérôme, I didn't even know this function!


fix: ugrade js sdk

Description
title

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.12.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix transfer alignment on initial texture transfer.

Fixes the regression caused by transfer workers with textures with non-standard dimensions such as the ones provided in #98601.
MRP
Before:

After:

Thanks!


Fix npm release

Codecov Report

Merging #805 (4d47e65) into master (2ca186f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #805   +/-   ##
=======================================
  Coverage   99.42%   99.42%
=======================================
  Files         121      121
  Lines         864      864
  Branches      248      248
=======================================
  Hits          859      859
  Misses          5        5

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 2ca186f...4d47e65. Read the comment docs.


add common getters for all tx types

https://github.com/keep-starknet-strange/madara/blob/main/crates/primitives/transactions/src/getters.rs#L51
In madara we added a set of common getters for all our tx types.
You should do that for the one defined in blockifier too.
It would avoid lib users having to write this type of bad boilerplate code all the time:
            let sender_address = match &transaction.tx {
                starknet_api::transaction::InvokeTransaction::V0(tx) => tx.contract_address,
                starknet_api::transaction::InvokeTransaction::V1(tx) => tx.sender_address,
                starknet_api::transaction::InvokeTransaction::V3(tx) => tx.sender_address,
            };

This should be a trait.

Hello, can this task be assigned to me?

@raizo07 I would love it if you could implement it, sadly I'm not the manager of this repo. @noaov1 is more likely to give you the green light

also I had to create those methods:
pub fn get_transaction_hash(tx: &Transaction) -> &TransactionHash {
    match tx {
        Transaction::AccountTransaction(tx) => get_account_transaction_hash(tx),
        Transaction::L1HandlerTransaction(tx) => &tx.tx_hash,
    }
}

pub fn get_account_transaction_hash(tx: &AccountTransaction) -> &TransactionHash {
    match tx {
        AccountTransaction::Invoke(tx) => &tx.tx_hash,
        AccountTransaction::Declare(tx) => &tx.tx_hash,
        AccountTransaction::DeployAccount(tx) => &tx.tx_hash,
    }
}

Just add some getters please :)


[Feature] Support SA-SSD

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Mmdetection3d doesn't have SA-SSD model, so we decide to contribute this model.
Modification
We added a SA-SSD model and related parts. We didn't change anything of the original code. The work refers to the SA-SSD paper as well as the opensource code.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos? No
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

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

Great work! Thanks for your PR adding new method, could you sign the CLA license?

We have moved all the ops from mmdet3d to mmcv, so we suggest it's better to add ops directly into mmcv if possible.

Hi @wenbo-yu , please resolve comments that you have made corresponding changes. Then we can begin the next round review.

Hi @wenbo-yu ,
Thanks for the contribution, could you solve the lint issue? You may click the detail as below to see the lint errors

mmdet3d has cleaned his CUDA op, we should migrate the op in this PR into mmcv.

BTW, can this PR be merged only when we merge the op in mmcv? I recommend use the existing op in mmcv such that we do not need to adjust the lower bound of required mmcv version.

Yes, I only use the functions from /op under mmcv. The only package utilized from mmdet3d/op is sparse_block. It is utilized in SparseEncoder under mmdet3d/models/middle_encoder.py, and our class is inherited from it.

Please fix the minor comments and merge the new base dev into your branch.

After merging dev branch into my branch, it shows build error. It shows,
"  /usr/bin/ld: cannot find -lpython3.6m
collect2: error: ld returned 1 exit status
error: command 'gcc' failed with exit status 1"
It seems the build environment is not set well. Could you help me solve that?

After merging dev branch into my branch, it shows build error. It shows, " /usr/bin/ld: cannot find -lpython3.6m collect2: error: ld returned 1 exit status error: command 'gcc' failed with exit status 1"
It seems the build environment is not set well. Could you help me solve that?

Sorry for the late reply. It seems the CI successfully passed after merging the latest dev. Could you please add the unit test as mentioned previously?

The linting fails and please fix it. Please use the pre-commit hook to check before making a commit.

The CI failed because the branch is a bit old. Could you rebase onto the latest dev branch so that we can merge this PR?

The CI failed because the branch is a bit old. Could you rebase onto the latest dev branch so that we can merge this PR?

Hi @Tai-Wang and @ZwwWayne,
Can you help us to check the following errors for the unit test? As our submission didn't touch any of the MMCV version, we couldn't figure why we got this error messages.

Hi @Tai-Wang and @ZwwWayne,
Can you help us to check the following errors for the unit test? As our commits didn't touch any of the MMCV version, we couldn't figure why we got this error messages.

Sorry for the late reply. It is due to some incompatibility of mmdet and mmcv. We will fix this problem on our side. Please don't worry.

Dear wenbo-yu,
First of all, we want to express our gratitude for your significant PR in the MMDetection3D project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
If you are Chinese or have WeChat，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. We look forward to seeing you there! Join us ：https://discord.gg/raweFPmdzG
Thank you again for your contribution❤
Best regards！ @wenbo-yu


Add Field to the generic IObjectTypeDescriptor

Moved the Field declaration function that can be parameterized with a… ResolverType to the untyped version of IObjectTypeDescriptor. There is nothing in that function that referes to T, therefore it can be safely used outside of the typed ObjectTypeDescriptor class. This way, a user can have an untyped ObjectType and refer to other resolver classes in their field declarations.

#390

@jbray1982 thanks for your contribution.


🚀 Feature: if loading a file as CJS and ESM both fail, display both errors instead of just ESM

Feature Request Checklist

[x] I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
[x] I have searched for related issues and issues with the faq label, but none matched my issue.
[x] I want to provide a PR to resolve this

Overview
Ever since chai v5 dropped support for CJS, we get errors like this when we accidentally install chai 5+:
$ mocha

 Exception during run: TypeError: Unknown file extension ".ts" for /Users/user/src/battalion/storage-site-sim/src/__tests__/SeededRNG.test.ts
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:160:9)
    at defaultGetFormat (node:internal/modules/esm/get_format:203:36)
    at defaultLoad (node:internal/modules/esm/load:141:22)
    at ModuleLoader.load (node:internal/modules/esm/loader:409:7)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:291:45)
    at link (node:internal/modules/esm/module_job:76:21) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

This threw us for a loop at first, because normally our tests work fine with @babel/register handling .ts files.
What's happening is first Mocha tries to load our file as CJS, which make it as far as require('chai') which fails with ERROR_REQUIRE_ESM.  Then Mocha tries to load our file as ESM instead, which triggers the above error.
Suggested Solution
If Mocha would print out the error from loading our file as CJS in addition to the above error, we would have seen what caused the problem more quickly.
Alternatives
I've thought about adding code to our toolchain to check for chai v5+ and explicitly warn...but this same issue could occur with any package we're using in tests that drops CJS support
I guess another solution would be a mocharc option to force Mocha to only try one of CJS or ESM, not both.
I can't just put type: "commonjs" in my package.json because I made my toolchain run tests in CJS mode with @babel/register, and then in ESM mode with babel-register-esm, since I'm transpiling my TypeScript source to both CJS and ESM for publishing.
Additional Info
No response

This is tricky. If both CJS and ESM fail to import the file because it actually doesn't exist, then displaying both errors would be extra noise for users. If this were to be implemented it would probably need some kind of heuristic for determining whether the errors are different enough to both warrant being displayed. I don't know how straightforward that would be to implement.
Would you be able to post a minimum reproduction project we could look at to better understand this?

Okay I'll work on making a repro soon

I don't think the extra noise would be worse, because what it currently displays is very confusing at first in a situation like this.
Theoretically the heuristic could be whether ERR_REQUIRE_ESM came from the user's own project files or from node_modules

👋 just checking in @jedwards1211, any luck on a repro?

Sorry I forgot about that, here you go: https://github.com/jedwards1211/mocha-cjs-esm


Issue using aliases

Hi, thanks for this beautifil work. Thanks to that I could start using React for my first chrome extension.
Though I've got some issues using aliases.
I followed your example because I need to fetch data from API and I need actions that can be used from content and from popup. But I can't make it work. Event with a simple exemple like this
export const aliases = {   // this key is the name of the action to proxy, the value is the action   // creator that gets executed when the proxied action is received in the   // background   'user-clicked-alias': () => {     // this call can only be made in the background script     console.log("start");   } }
and a index.js like this
const store = createStore(   rootReducer,   applyMiddleware(     alias(aliases)   ));
Everything compiled succesfully, my extension is loaded by chrome but if I want to dispatch event like before (even the ones for reducers) I got an error like this on the content page

Error in event handler for (unknown): TypeError: Cannot read property 'error' of undefined

and error like this on background page

Error in event handler for runtime.onMessage: TypeError: Cannot read property 'ADD_INSTANCE' of undefined
at Object.dispatch

is that a known case ? Do I have to use a separate store for actions ? is that the good way to gather API calls ?
Thanks in advance

Hi there @loyalty-company !
Your aliases need to return a new action if you are going to use them:
export const aliases = {
   'user-clicked-alias': () => {
        console.log("start");
        return { type: "Hello", payload: "World"};
    }
}


resetRoot(saveState = true, restoreState = true) loses saveable state

This can be reproduced in chrisbanes/tivi:

open any show detail from discover
scroll down
select another tab
go back to discover

Backstack is restored properly, but any of the rememberSaveable (e.g. scroll) state is lost
I suppose this is expected with the current implementation, but is it possible to support this?

The PR linked above verifies the issue, but I'm not sure how to fix it tbh. At a high-level, we need to call performSave on our BackStackRecordLocalSaveableStateRegistry when the back stack entry is removed. Thus the saveable state is stored somewhere (where tbd).
@ZacSweers this might be one for you, as you wrote most of BackStackRecordLocalSaveableStateRegistry by the look of it.

Any workarounds till this gets fixed like saving states in presenters?

FYI, #1354 now contains a fix


Deploy Identityserver in a docker Linux container

Issue / Steps to reproduce the problem
I'm trying to deploy Identityserver for high availability in a docker container with Linux but always have the following error when I try to login through mvc. I'm using a pfx certificate.
This is how I configure the DataProtection:
services.AddDataProtection()
                .PersistKeysToFileSystem(dirInfo)
                .ProtectKeysWithCertificate(new X509Certificate2(Configuration["server:pfxFilePath"], Configuration["server:pfxPassword"]))
                .SetApplicationName(!string.IsNullOrWhiteSpace(Configuration["appName"]) ? Configuration["appName"] : "XXXXXXXXX")
                .DisableAutomaticKeyGeneration();

Relevant parts of the log file

An error occurred while trying to encrypt the provided data. Refer to the inner exception for more information.

InnerException:
ClassName : "System.InvalidOperationException"
Message : "The key ring does not contain a valid default protection key. The data protection system cannot create a new key because auto-generation of keys is disabled."
Data : null
InnerException : null
HelpURL : null
StackTraceString : " at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingProvider.CreateCacheableKeyRingCore(DateTimeOffset now, IKey keyJustAdded) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingProvider.GetCurrentKeyRingCore(DateTime utcNow) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Protect(Byte[] plaintext)"
RemoteStackTraceString : null
RemoteStackIndex : 0
ExceptionMethod : null
HResult : -2146233079
Source : "Microsoft.AspNetCore.DataProtection"
WatsonBuckets : null

This is the complete message:
Log message
PD: use a json viewer to see it i.e. http://jsonviewer.stack.hu/

I was able to reproduce the same error by generating keys with a cert, copying them into a container, and running the app. I believe this is a duplicate of #2321. The key ring is empty because the keys were protected by a certificate, but encrypted XML doesn't support decrypting with certs that are not in the X509 cert store.
To workaround this in ASP.NET Core 2.0.x, you can add the cert to your local X509Store inside your docker container like this:
var store = new X509Store(StoreName.My, StoreLocation.CurrentUser);
store.Open(OpenFlags.ReadWrite);
store.Add(cert);
store.Close();

You won't need this workaround in 2.1. We fixed this in https://github.com/aspnet/DataProtection/pull/299 by providing support for loading keys protected with a cert, even if that cert isn't in the X509Store. This will be released in ASP.NET Core 2.1.0-preview2. You can try an early preview of this by adding this to your csproj:
  <PropertyGroup>
    <RestoreAdditionalProjectSources>https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json</RestoreAdditionalProjectSources>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.DataProtection" Version="2.1.0-preview2-30143" />
  </ItemGroup>

@OscarCanek can you try one of these to confirm is solves your issue?

Closing per previous comment. https://github.com/aspnet/Home/issues/2814#issuecomment-367145437. This issue is a duplicate of https://github.com/aspnet/Home/issues/2321 which will be resolved in 2.1.


Where are the time filters from charts and dashboards implemented?

Superset has the feature of time filters in Charts:

Where in the code is this feature implemented? I want to change the functionality so that 'Last Month' is from 1st of the month to last day of the month, instead of relative to today's date.

For anyone who might stumble on this in the future, the path file is located here:

superset/superset-frontend/src/explore/components/controls/DateFilterControl.jsx

You need to make changes on this function:
getStateFromCommonTimeFrame

@mistercrunch can you pinpoint me to what is used for calculating the query's date filter?


[docs] Describe debugging tests in a Docker container

We have only generic troubleshooting instructions for Docker. Our feedback indicates that we should write a more detailed article about debugging tests in Docker. [1]

Closed in favour of #7153


[DNM] config(ticdc): deprecate  changefeed level config enable-old-value

What problem does this PR solve?

Issue Number: close #xxx
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/retest

/test cdc-integration-mysql-test

/retest

/retest

/test dm-integration-test

Finally.


[release-4.13] USHIFT-1271: Switch to rhocp-4.13 repositories in devenv and ISO build environments

Do not disable SELinux and switch to rhocp-4.13 released repos.
Closes USHIFT-1271

/test images

/label backport-risk-assessed

Executed the QE pipeline with the proposed branch, to build the ISO, deploy the image and confirm MicroShift functionality.
Confirmed in logs that "Repository 'rhocp-4.13-for-rhel-9-x86_64-rpms' is enabled for this system."

/label cherry-pick-approved

/label  jira/valid-bug

/lgtm

/label jira/valid-bug


Fixed charge_entity state undefined issue.

Fixed an error that I reported about this breaking in HASS 0.88.1 when using the charge animation.

This is a correction for issue #1.

Also added a json tracker for the custom_updater component. You will have to change the URLs back to your repo. I have them set to my fork for testing in my install. If you wish to adopt the custom_updater part you'll have to upload the js file to the releases creation page.

I've manually added the tracker as I couldn't figure out how to partially merge a PR. (This is my first PR ever xD)


Inline Storage - Size / Alignment compile-time assertions.

One worthy goal would be to be able to perform compile-time size/alignment assertions for inline storage without changing the final api, and retaining the storage-agnostic goal of the final container objects. Heap storage should not do any assertions.
My approach is to use generic associated types as assertion objects and have the final create function perform the check using the assertion object directly. This way each associated assertion is a policy for the final create function. For all storages the assertion is performed as a trait requirement on create, the trick is to make the assertion always pass for Heap storages but possibly-fail for Inline storages.
Here is a POC  of this.
Unfortunately having the check being part of the signature means that all call sites will need to propagate the constraint even if we know that eg on HeapStorage it will always pass. The compiler first checks the trait bounds and refuses to evaluate the bound itself. This means that if we attempt to make an alias with HeapStorage the constraint will have to leak to user code as well.
Eg a user can't write an external create function:
fn create<T>(val : T) -> RawBox<T, HeapStorage> {
    RawBox::create(val)
}

even though the trait is always valid. Instead they have to write the following:
fn create<T>(val : T) -> RawBox<T, HeapStorage> where [u8 ; size_assert::<HeapStorage, S>()] : Sized {
    RawBox::create(val)
}

it would be nice if the compiler attempted to evaluate the trait first. The above should be able to reduce to:
[u8 ; {HeapStorage::Asserter<T>::VALUE as usize} - 1] : Sized =>
// At this point AlwaysTrueAsserter is parameterized but we can avoid it.
[u8 ; {AlwaysTrueAsserter::VALUE as usize} - 1] : Sized =>
[u8 ; {true as usize} - 1] : Sized =>
[u8 ; 0] : Sized

So the fact that I have to specify the bound seems a bit unneeded to me.

Well done! GATs really are awesome.
I realized there's another fundamental difference between the inline storage and the heap storage. With the inline storage, it's known at compile-time whether the allocation will succeed, whether with the heap storage it's not known until one tries.
Hence, if we wanted to go all the way, we should also make it possible to specialize the error type in create. That is:
fn create<T: Pointee>(&mut self, value: T) -> Result<Self::Handle<T>, T>;

Should be:
fn create<T: Pointee>(&mut self, value: T) -> Result<Self::Handle<T>, Self::AllocError<T>>;

And the AllocError<T> should expand to either T if failure is possible or ! if it is not.

I must admit that I'm not ready to use the clunky [u8; X] : Sized work-around.
If at some point the compiler were to support value-based where clauses, such as where S::is_allocation_possible::<T>(), it would be one thing; but the goal here is to end up with a design fitting the std library, and I have some doubts that where [u8; X] : Sized will pass muster.
I do like exploring how far compile-time assertions can be pushed; I just want to be clear that I am not likely to act on any such exploration.

I understand this, I also wouldn't attempt to standarize this as is. Even if we had a better syntax for the assertion, I would expect the HeapStorage to completely remove the assertion for user code otherwise it would just be confusing. Currently trying to see if this is in the scope of the const_generics RFC.


Proposal - Footer component

I'm proposing an API for the materialize footer, so I can get some input from others before I get started. What we're trying to create is something that looks like this

Which is generated from the following HTML

Footer Content

You can use rows and columns here to organize your footer content.

Links

Link 1

Link 2

Link 3

Link 4

    © 2014 Copyright Text
    More Links

I propose the following handlebars markup
{{#materialize-footer subfooterView="myFooterViewClass"}}

Footer Content

You can use rows and columns here to organize your footer content.

Links

Link 1

Link 2

Link 3

Link 4

{{/materialize-footer}}

Here I am regarding the "copyright footer" as a separate view, which would default to a plain copyright notice with the current year as the date. Setting subfooterView to null should remove the copyright footer entirely
 © 2015, All Rights Reserved

I gave it a shot locally, but have been hung up on getting the sticky footer example to work.
What I have working has the following usage:
{{#materialize-footer}}

Footer Content

You can use rows and columns here to organize your footer content.

Links

Link 1

Link 2

Link 3

Link 4

  {{#materialize-copyright text='Copyright Text'}}More Links{{/materialize-copyright}}
{{/materialize-footer}}

if we can, I'd like to avoid the container/row being included in the body of the footer, in the interest of taking care of as much "no brainer" stuff as possible for users

I'm kind of fond of the fact that in the second example the copyright element is a component as well.  This makes it possible for me to extend/override its capabilities quite easily.  It also allows me to add content to it if I wish or simply leave it out since it appears to support that as well.  I like no-brainers for sure but i'm wondering what subFooterView is... Do I need to supply a view class/template for my footer if I don't want the default?  How do I extend it if it is not exposed as a component too?
By setting it to null, does this mean I can simply omit that attribute or does that mean i actually have to pass null as the attribute value?

But make this component sense?
As user I save here only 4 lines of code and the footer is not a component used more than one time.
This
{{#materialize-footer subfooterView="myFooterViewClass"}}
...
{{/materialize-footer}}

instead of this

...

I think it could make sense due to the fact that the copyright is being provided with logic to use the current year.  Consuming apps wouldn't have to do this themselves.

@sgasser I agree that the less work we save the developer, the less components like these make sense. Particularly if the decision is to go the route that @franktcurran has proposed, we probably don't need to build this at all (I think it would mean 0 lines saved).
The existing content projection capability of {{yield}} doesn't really let us have our cake and eat it too. I think the best we can shoot for without hacking around in the view rendering code is saving the user from having to deal with the particulars of the grid/container stuff.

@truenorth, @sgasser - It looks like we have this settled in #53. No footer component for now. Can we close this or am I wrong? Thanks!


Test failures on Windows

See for instance https://github.com/eik-lib/webpack-plugin/actions/runs/9874637423/job/27269472807

This might be fixed by https://github.com/eik-lib/common/pull/303


817 update total population to 2022 data

Changes and Information
Please briefly list the changes made, additional Information and what the Reviewer should look out for:
Total Population was updated for 2022
If 2021 data is used, a warning is printed
Merge Request - Guideline Checklist
Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.
Checks by code author

[x] Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
[x] New code adheres to coding guidelines
[x] No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
[ ] Tests are added for new functionality and a local test run was successful
[ ] Appropriate documentation for new functionality has been added (Doxygen in the code and Markdown files if necessary)
[ ] Proper attention to licenses, especially no new third-party software with conflicting license has been added

Checks by code reviewer(s)

[ ] Corresponding issue(s) is/are linked and addressed
[ ] Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
[ ] Appropriate unit tests have been added, CI passes and code coverage is acceptable (did not decrease)
[ ] No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)

Closes #817

Closes #819