Update not actually updating data

Hi,
I'm executing an update on a row in my 'field' table where the type was previously '2':
    return this.knex.table('field')
        .where({id : 1 })
        .update({type : 3})
        .returning('*')

This call does not fail, but the return shows that the type is STILL 2 and querying postgres shows that is in in fact still 2. Other calls, such as insert, are working fine.
Furthermore, I added a .toQuery() and copied and pasted the query directly to my database, and that worked (type was updated to 3).

So this is something that will probably be addressed before 1.0 (at least with a warning), but queries aren't actually executed until something triggers the promise (calling .then, .catch, etc. or another associated method).
If you put a .then() at the end of the .returning('*') does the query run? If that's not the issue is there any chance you're in a transaction that isn't being committed?

I think I might have debugged it. I had a ".first()" on the end of the
update call, which I added when I realized that the return gives a list of
rows when I just wanted the first one. Interestingly, this made the update
return the first row as expected, but prevented the update from actually
going through. Happy to close.
Megan Schoendorf
Check us out! www.stridespark.com
On Tue, Jun 21, 2016 at 1:07 AM, Mikael Lepistö<EMAIL_ADDRESS>wrote:

@mschoendorf https://github.com/mschoendorf I wasn't able to reproduce
this problem, could you give some more complete example how to reproduce
the problem?
I was trying to reproduce it like this:
knex = require('knex')({client: 'pg', connection: 'postgresql:///knex_test' })knex('accounts').where('id', 54).then(result => console.log("Result", result))> Result [ anonymous {
id: '54',
last_name: 'Data',
email: 'email39',
logins: 1,
about: null,
created_at: null,
updated_at: null,
phone: null } ]knex.table('accounts').where({id: 54}).update({logins: 3}).returning('*')
.then(result => console.log("Result", result))> Result [ anonymous {
id: '54',
last_name: 'Data',
email: 'email39',
logins: 3,
about: null,
created_at: null,
updated_at: null,
phone: null } ]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tgriesser/knex/issues/1522#issuecomment-227369770,
or mute the thread
https://github.com/notifications/unsubscribe/AEE-2vfgx4W7Bi9vrtDqbwwobhPuwVGaks5qN5vZgaJpZM4I6OV-
.

This line still doesn't work even now...
knex('table').where(A).update(B);
and need to be replaced with
knex('table').where(A).update(B).then();
Very frustrating misbehavior...

This is the intended behavior, as it allows chaining actions together without having them execute unexpectedly. For example, you can do this:
const update = knex('table').update(B).where(A)

if (something) update.whereIn(C)

update.then(results => {
  // your results are now limited bu .where() and .whereIn() if "something" is "true".
})

Also, Knex query methods return Promises, so you would always have to attach a .then() or .catch() to see if the query actually succeeded or not.
I agree that the documentation could have the complete call, including .then() since currently it looks like the queries exemplified would just be executed without it.

Yep, documentation page doesn't execute queries, but only prints out SQL that is generated by the query.
Anyhow nowadays preferred method to trigger query builder is to do
const res = await knex('table').where(A).update(B);

I see. Thanks for the detailed explanation! I've had the misunderstanding for quite a while.


YAS 227 L2-to-L1 Message Receiver

Description
Implements YAS 227, L2-to-L1 message receiver in a trusted context to build out dev ex.
Questions

I noodled around for a while with data structures.  I think it could've been done without a nonce, but I decided having a nonce makes it more similar to the final version where we will need an inclusion proof.  Look fine?

Metadata
Fixes

Fixes YAS 227

Contributing Agreement

[x] I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

Is there ever a time when the sequencer (or some other authorized party) would be able to remove messages from the queue? May be nice to reduce state and get a gas rebate.

This is a little tricky, since the context for this contract is that it is really there to " simulate" what an actual rollup contract would do.  And in that context, the messages can't be removed--but they also don't appear on the main chain other than implicitly via a state root.  So for now, I think I'm not gonna add that ability as it would be deprecated quickly anyway.


Remove Changelog?

GitHub will generate a changelog for us... Use that instead of changelog.md?

Where is the one that GitHub generates?

When you draft a new release, there's a generate changelog button https://github.com/twigjs/twig.js/releases

I thought you were doing that manually, that's really useful. I'm fine with removing it in favor of an upgrade guide (UPGRADING.MD) when there are breaking changes, since it's more to the point of why people usually look at a changelog and then they won't need to grok through all the non-breaking changes included in a changelog.


Add script for rebuilding database on demo site

I almost dropped the real database twice doing this (thanks to Rails and Heroku for the guardrails), so this adds a script with no args to pass so you can't pass the wrong app, etc.

👍 👍


[BUG] SETPROFILE

Info cuy setppbot/setppgc g work kah gw coba eval ini ga bisa
=> conn.query({
tag: "iq",
attrs: {
to: global.nomorbot,
type: "set",
xmlns: "w:profile:picture"
},
content: [{
tag: "picture",
attrs: {
type: "image"
},
content: await m.quoted.download()
}]
})

Same issue, i got this error when i tried to send query node manually
Error: Timed Out
    at /home/ripp/bot/node_modules/baileys/lib/Utils/generics.js:145:32 {
  data: {
    stack: 'Error\n' +
      '    at promiseTimeout (/home/ripp/bot/node_modules/baileys/lib/Utils/generics.js:140:19)\n' +
      '    at waitForMessage (/home/ripp/bot/node_modules/baileys/lib/Socket/socket.js:119:53)\n' +
      '    at Object.query (/home/ripp/bot/node_modules/baileys/lib/Socket/socket.js:141:22)\n' +
      '    at Object.eval (eval at handler (/home/ripp/bot/src/plugins/owner/eval.js:24:14), <anonymous>:3:13)\n' +
      '    at async Object.handler (/home/ripp/bot/src/plugins/owner/eval.js:25:13)\n' +
      '    at async Object.onMessage (/home/ripp/bot/src/handler.js:128:7)'
  },
  isBoom: true,
  isServer: false,
  output: {
    statusCode: 408,
    payload: {
      statusCode: 408,
      error: 'Request Time-out',
      message: 'Timed Out'
    },
    headers: {}
  }
}

#1048

Info, bro, setppbot/setppgc doesn't work, I tried to evaluate this but it didn't work => conn.query({ tag: "iq", attrs: { to: global.nomorbot, type: "set", xmlns: "w:profile:picture" }, content: [{ tag: "picture", attrs: { type: "image" }, content: await m.quoted.download() }] })

https://github.com/WhiskeySockets/Baileys/issues/1067#issuecomment-2396382441


Fix postinstall.sh for upgrading

If the plugin is already installed, this script failed on
mkdir /etc/newrelic. Change is to check if the dir exists before
attempting to create it.
Also, always copy the (potentially new) config into place. Additionally,
if there is no existing config present, copy the new config into place
for use by the plugin.

For context:
root@testhost:~# ll /usr/local/lib/node_modules/
total 12
drwxr-xr-x 3 root   root    4096 Mar 28 21:19 ./
drwxr-xr-x 5 root   root    4096 Mar 22 19:04 ../
drwxr-xr-x 3 nobody mmurphy 4096 Mar 28 21:19 newrelic-neo4j/
root@testhost:~# npm i -g newrelic-neo4j
loadDep:uuid → 304        ▐ ╢█████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
/usr/local/bin/newrelic-neo4j -> /usr/local/lib/node_modules/newrelic-neo4j/index.js

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/newrelic-neo4j
> sh ./postinstall.sh

mkdir: cannot create directory ‘/etc/newrelic’: Permission denied
cp: cannot create regular file '/etc/newrelic/newrelic-neo4j.js': No such file or directory
/usr/local/lib
└──<EMAIL_ADDRESS>

Hi @roens!
Thank you for your contribution, it's highly appreciated!

Changes have been published in 0.1.10

No worries, I will take the blame on that. It wasn't really obvious that it was running in SH (given that it also had the BASH shebang). https://github.com/legraphista/newrelic-neo4j/commit/f6a51bf558f29580fb98e6a503b09840e161df02


Support for certificate chaining during verification

Hi, I'm using a private single issuer CA and just wondering if certificate chaining is supported.  I included the leaf and self-signed root via notation sign however getting this error:
time="2022-08-02T18:38:25Z" level=info msg="received request POST /ratify/gatekeeper/v1/verify "
time="2022-08-02T18:38:25Z" level=info msg="start request POST /ratify/gatekeeper/v1/verify"
time="2022-08-02T18:38:25Z" level=info msg="subject for request POST /ratify/gatekeeper/v1/verify is ivanvenafi.azurecr.io/net-monitor:v1"
time="2022-08-02T18:38:25Z" level=info msg="Resolve of the image completed successfully the digest is sha256:81a768032a0dcf5fd0d571092d37f2ab31afcac481aa91bb8ea891b0cff8a6ec"
{
  "isSuccess": false,
  "verifierReports": [
    {
      "isSuccess": false,
      "name": "notaryv2",
      "results": [
        "an error thrown by the verifier x509: certificate signed by unknown authority"
      ],
      "artifactType": "application/vnd.cncf.notary.v2.signature"
    }
  ]
}

@zosocanuck when we implement #274 - it will support this scenario.

Closing it as it's resovled by https://github.com/deislabs/ratify/pull/433


Kernel build

This should be evaluated after #216 as it also includes changes in that

LGTM

so .... what's the deal? yes or no?

@rminnich this still doesn't build, should I pull this into master and continue working there?

now be sure to tell us what to type to use it.


template navigation is not longer working

Description
Template navigation is not longer working in rn 0.44
Reproduction Steps
react-native init template --navigation

Closed #13836


Documentation for XPUB is missing code blocks

Describe the bug
The documentation page for XPUB is missing its code samples, making the steps impossible to reproduce.
(I was able to find the needed code samples by editing the file on Github, so all good for me)
To Reproduce
Steps to reproduce the behavior:

Go to https://bitcoin-dca.readthedocs.io/en/latest/xpub-withdraw.html#verifying-the-configured-xpub or its Git counterpart
See the page is missing all its (code) samples.

Expected behavior
See all (code) samples as all the other documentation page.

Hi @jphorn, it's now fixed! 👍

Looks beautiful :-) Thanks @mijndert 👍


PhpUnit 10.3 introduced some breaking changes

Sebastian Bergmann implemented some breaking changes in the PHPUnit\TestRunner\TestResult\TestResult (which marked as internal). Notably, some public methods that Collision relied on where removed (TestResult::numberOfTests() for example). See https://github.com/sebastianbergmann/phpunit/issues/5460 for additional context.

Confirmed, I'm getting Call to undefined method PHPUnit\TestRunner\TestResult\TestResult::numberOfTests() on php artisan test tests/Feature/UserTest.php

Fixed v7.8.0.


Feat/add new format

Reqires squash to merge changes with the correct commit description

:tada: This PR is included in version 3.0.0-beta.18 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


IAM Explain optional module description & deployment configuration

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


Add View Modal and corresponding canView authorization.

Related to #45 .
Note that canView() behaves the same way as canEdit() in the sense that, since it overrides a Widget method, it well be called with without parameters by filament.

sorry for the delay, thanks


[infrastructure] centralize dependencies of packages

Right now we have multiple locations where we specify dev requirement versions. For example, in pyright, we have a dep at the root dev_requirements.txt, and we also install it in every tox.ini. Finally, we also have duplicated install locations in the main dev_requirements.txt, and the requirements.txt for the sub test folders.
We want to have the dev requirements in one shared file for these dependencies. This way dependabot can easily update, and we also have one shared source of truth

fixed


Consider variance for Encoder and Decoder

Both Encoder and Decoder are currently invariant. It might make sense to make, say, Decoder covariant on its decoded type parameter.

I'm closing this for now - I don't think this brings anything helpful, and variance tends to be problematic.


api server only support extract_wisdom pattern? I think the api path should be dynamic

we can do something like
path_mappings = {
    "path1": {"system_url": "https://example.com/system1.md", "user_url": "https://example.com/user1.md"},
    "path2": {"system_url": "https://example.com/system2.md", "user_url": "https://example.com/user2.md"},
    # also this can be a relative path since the back-end server lives along pattern directory
}

@app.route("/<path_segment>", methods=["POST"])
def mill(path_segment):

just a rough idea, I will tackle this on the weekend. I want to contribute to this and improve quality of the back-end server.

Interesting idea, thank you!


rework error return values

Fixes #2441.
This is a massive refactor changing the way we return QUIC errors. Calls to the session (and to streams) can now different errors, which can be checked with errors.Is / errors.As:

quic.TransportError: for errors triggered by the QUIC transport (in many cases a misbehaving peer)
quic.ApplicationError: for errors triggered by the application running on top of QUIC
quic.IdleTimeoutError: when the peer goes away unexpectedly (this is a net.Error timeout error)
quic.HandshakeTimeoutError: when the cryptographic handshake takes too long  (this is a net.Error timeout error)
quic.StatelessResetError: when we receive a stateless reset  (this is a net.Error temporary error)
quic.VersionNegotiationError: returned by the client, when there's no version overlap between the peers

In addition to that, streams that are canceled return a:

quic.StreamError: both for local and remote cancellations

@mvdan, what do you think about this? Do the API changes here make sense to you?

@mvdan, what do you think about this? Do the API changes here make sense to you?

From the PR description you wrote, it sounds fine.


Newlines check returns errors for PDF and PPTX files

Describe the bug
Some more files which are erroneously included in the lintspaces.newlines check: .docx and .pdf.
To reproduce
Steps to reproduce the behavior:

Run the lintspaces.newlines check against a project which contains PDF or PPTX files (e.g. https://github.com/codelearncreate/c2lc-project-website/runs/1979991318?check_suite_focus=true)
See the test failure.

Expected behavior
The newlines check should not include these file types.
Additional context or notes
Is there any way we can more broadly check for appropriate text files to which this should be applied and exclude all else?
Related: #4, #11

I will address all of these in #31.


Bug : sending invalid input should not returun 500 but a 400

**Description **
given an invalid input server rertuns 500 , where it should return 400 error code ( payload is ok)
How to Reproduce
given the request
POST : https://api.scim.dev/scim/v2/Groups
with no payload
the server return
status code 500 + this payload
{
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:Error"
    ],
    "detail": "Missing a valid schemas-attribute.",
    "status": 500
}

It took a while, but I've just fixed this. Thanks for reporting.


Use 'flow' parameter to specify standalone tool run

This PR builds on top of #862 and fixes its failing tests. The main change is adjusting the way that standalone tool runs are set up. It gets rid of load_tool() -- we don't need this function since each tool's setup() function is called automatically inside of run(), and giving the user the ability to call it earlier can be problematic since it introduces ordering issues.
I chose overriding the 'flow' schema parameter as the new way to specify a standalone tool run. Now, if the user specifies a flow that doesn't have a configured flowgraph, run() will automatically set up a basic flowgraph to run that tool. I considered making a separate helper function for loading a standalone tool, but I realized using a schema parameter is necessary to support running tools in standalone mode from the CLI. Instead of adding an additional parameter, reusing flow seemed logical since the standalone tool is effectively the flow you want to run.
@aolofsson I'm opening this PR as relative to your PR's branch rather than committing directly to make it easier for you to review these changes. Once you're ready, you can merge this PR and these commits should show up in your original PR, which you can then merge into main.

Love it. That's some fancy git footwork.;-)
Also love that you fixed the bugs by removing code. Very elegant.:-)


[Question] Benchmark progress / repeat audit

Hi all,
We audit our applications (over 50) based on the ASVS. I was looking for the option to use DefectDojo benchmark to keep an eye on the progress. It is very nice to have a quick overview and see risks or checks which are not done yet.
But the benchmark seems to be for once, instead of report and do it again to see progression.
Is it possible to create a benchmark, freeze the report and start a new benchmark? This will also give a good idea for all applications where failed items are and how many in the full product/project suite.
Best regards

please discuss on slack.

please discuss on slack.


Now use multiple install and demo data sql files

Installation files should go in /install
Demo data files should go in /demodata
They will be processed in order, e.g.:

00_test.sql, 10_test2.sql, 15_test3.sql

Please pull the branch, build the new version of EcoSystem, make a new branch of the football bundle, divide up the logic and demo data into multiple sql files and let me know if it works.  We can then push our changes at the same time and I will update the docker containers.


Use more accurate/universal terminology than "states" and "cities"

Many countries do not have first level subdivisions called "states", they use another term – such as province or region.
Even those who do have first level subdivisions called "states", often have other subdivisions at the same level lacking that name (e.g. Australia has both "states" and "territories")
I'd suggest a more universal term such as "first_level_subdivision".
You could also add a column "type_of_subdivision" to record the name for that type of subdivision where it is known – e.g. for Australia it might have the values "state" and "territory", for Canada it might have the values "province" and "territory", for New Zealand it would have the value "region", etc.
There is a similar issue with "cities" – the term "city" usually refers to an entity of a certain size, or having a certain legal status – the exact definition varies from country to country (and often involves some arbitrary historical factors.) I don't think you want to limit the list to places which are classified as "city", you really mean to include towns, villages, suburbs, etc – anywhere that people are likely to live – whatever their size or formal status. Consider instead a term such as "locality" as more general and globally accurate term than "city"

Absolutely agree. Again, I will incorporate this into a bigger data enhancement of this project.

I am thinking of going with "divisions" or "administrative_divisions".

fixed in https://github.com/vincentmorneau/oracle-countries-states-cities/commit/4ef3f9cfcf06d4cd27733da1a66e9ae9dbdc8baf


Fix 'Define a constant instead of duplicating this literal' issue of the buienradar sensor.py file

Fix the duplicate literal issue for the 'sensor.py' file
Changes:

Replace literal constants for 'mdi:gauge' with a constant

Tested:

Ran Sonarqube after the change was made: The congitive complexity issue was resolved.
Ran the test_sensor test file which passes after the changes were made.

close reason: selected wrong branch to merge


docker-proxy high cpu load

Can you minimize it to... 20%? optimize this docker-proxy. high cpu is detected when doing ab test.

duplicate of https://github.com/docker/docker/issues/7857 https://github.com/docker/docker/issues/8356


Support user provided "scope" in JWT and GDC

The current C-core JWT token API (i.e., jwt_credenitals.h and jwt_credentials.cc ) does not support the "scope" field in the token creation API and this PR fixes it. Note that when the JWT token is used together with GDC, we clear the audience field in the token, which is dictated by https://google.aip.dev/auth/4111#scope-vs-audience.
F.Y.I. I am also working on the gRFC that explains the surface API change in this PR.

This change is

Thanks Mark for the review!

Known issues: https://github.com/grpc/grpc/issues/24442, https://github.com/grpc/grpc/issues/26072

Thanks for the review, Shin!


New governance model: Jupyter Enterprise subproject

Hello.  Thank you all for the great work being done toward solidifying the governance model - this will be a tremendous benefit to the health of the community.  I realize I should have raised this prior to the model's merge, but felt the other discussions were more important and, honestly, wasn't sure if it was my place to chime in.
I'm concerned that the Jupyter Enterprise subproject's "foundation" will be tenuous from the start and will struggle to meet the participation needs of the model.  It also feels a bit like an Island of misfit toys in that the only project specifically targetting enterprises is Enterprise Gateway.
Although I can't speak to docker-stacks or nbviewer, I can safely say both Kernel and Enterprise Gateway are (today) maintained by a couple of maintainers with Kernel Gateway's traffic quite sparse and EG's not far behind.  Since these two projects are direct subsets of Jupyter Server (JKG is currently based on notebook, but is identical to server) and require the same technical expertise residing within the Jupyter Server organization, they strike me as better-suited to the Jupyter Server subproject.
Assuming we did relocate the gateway's into Jupyter Server, that would leave docker-stacks and nbviewer as the only projects in Jupyter Enterprise, both of which are widely used outside of enterprises.  Seems they could be logically included in Jupyter Foundations, a different sub-project, or in the set of projects w/o SCC representation.
I just feel like the current incantation of Jupyter Enterprise is fragile from a participation/community presence perspective and felt this should be raised before actual representation is established.
Thanks again for all you're doing to improve the community!

Kevin, great points here. As we have talked about this, one of the principles has been that the folks most involved in the subprojects/repos should drive this. Thus, if there is consensus among the involved parties, I think that makes sense. Do you want to open a PR to the doc that describes the new subprojects with these changes and ping the relevant stakeholders for input?
Another point that probably deserves clarification. While each decision making body has a minimum participation requires (as a % of the annual votes), we realize that some decision making bodies will be smaller and less active than others. I wouldn't be surprised if some of the smaller subprojects only have a few people on their decision making body and only take a few votes (if any) each year.
But overall, the refactoring of subprojects you are proposing makes sense to me.


Add SequenceType methods to AnySequence

Implements other methods of SequenceType in AnySequence so that overrides work correctly.
Currently AnySequence(0...1000000000).suffix(2) takes a long time to run, but (0...1000000000).suffix(2) does not.

See https://bugs.swift.org/browse/SR-413 for more details.

Thanks @gribozavr, I've applied your feedback, just verifying the tests pass locally.

@therealbnut Thank you.  I don't think this change actually achieves what you wanted.  Could you take a look at #220?
Another thing that is missing is the same optimization for Any*Collection.
And of course, tests are missing.  The tests should use LoggingRangeReplaceableCollection wrapped in AnySequence and Any*Collection and verify that the implementations actually forward to the underlying collection.

Thanks @gribozavr, I've had a look at #220, good to know. I don't think it completely overlaps with this though.
I'm fairly sure this will work, but I will implement the tests and verify. I'm finding my dev environment for swift's libraries a little cumbersome at the moment.
Should I be putting tests into CheckSequenceType.swift? Also do you know a fast way from the command-line to just build what has changed (and run that test)?

@therealbnut The reason why this won't work is because at the point where you call, say, base.prefix() you are using the static return type AnySequence -- that is only the case in the default implementation.  The custom default implementation uses Base.SubSequence as the return type.  If you use that, you need wrapping into another box, and then the rest of #220.
The forwarding tests should go into ./test/1_stdlib/ExistentialCollection.swift and should use expectCustomizable.
If you want to add more in-depth tests, take a look at the validation-test/stdlib/Slice/ directory.    This won't show that the optimization is in the effect, since the default implementation is conservatively correct, but it will show that the type overall behaves correctly.

Ah right, I understand what you meant now - I agree. I'll add the tests and see if I can get it working, and/or put this on hold until #220.

@therealbnut JFYI: #895 has landed.

Thanks @gribozavr, and thank you for your help :) I'll see what I can get done, although I'm back at work with no free time for about 3 months.
I will probably do SequenceType first as that can potentially land separately.
On another note, I feel like all of this should be able to be automated by the compiler. I think this effort would be better spent with a more generic solution. Although, I'm unsure of the scale of the work to get this done. Also it would require a proposal. What do you think about the short-term/long-term win work tradeoff?

It would get us AnySequence, AnyForwardCollection, AnyForwardIndex, AnyGenerator, etc . for free.
It would prevent this sort of bug from occurring again.
It would put control of the implementation in the hands of the compiler (do compilers have hands?).
It would allow future optimisations to be applied uniformly and with a consistent implementation.
It removes a lot of error-prone repetitive boilerplate code.

Something like this could work:
struct AnySequence<T>: @any SequenceType {
    public typealias Element = T
    public typealias SubSequence = AnySequence<T>
}

The compiler could generate those method definitions. These are two downsides:

It likely won't copy method comments from the protocol. I think that comments should also be addressed, but as a separate issue that improves all protocols.
It isn't explicit that it's providing a method, so would you expect SequenceType's extension or AnySequence to provide the implementation.

Alternatively it could be clearer if you explicitly state the methods, with comments. I can't think of a good way to annotate that though, and it also adds a lot of boilerplate.

@therealbnut Automatically generating an implementation like this with type erasure might be possible, but it would be a massively large compiler feature, because of the complexity of the problem, and because there are so many choices in the way you can actually do the implementation details of AnySequence.  I don't think it would be implemented any time soon.
What is interesting (and practical) in this area is the interface forwarding problem, its application area is much wider than type erasure, and I think it would be more interesting to implement in the language.

@gribozavr hmm, that's a good point. I think there was proposals that talked about implementation forwarding, but if I recall correctly it was jumbled in with a lot of other features.
Having a play around with how it could be expressed it seems to require a few capabilities I don't remember those proposals discussing, namely override, public, private, computed and/or abstract.
private class _SequenceBase<E>: SequenceType {
    private var _neverUsed: AnySequence<E> { return _abstract() }
    forward SequenceType = _neverUsed
}
private final class _Sequence<S: SequenceType>: _SequenceBase<S.Generator.Element> {
    private var _implementation: S
    override forward SequenceType = _implementation
}
struct AnySequence<T>: SequenceType {
    public typealias Element = T
    public typealias SubSequence = AnySequence<T>

    private var base: _SequenceBase<T>

    public forward SequenceType = base
}

Anyway, I'll proceed with this PR, it's at least something that would be desirable in the interim.

Can one of the admins verify this patch?

FYI I believe the tests to be valid, but they will be failing until the AnySequence implementation is updated.
@swift-ci

This has been dormant for a long time. @dabrahams , is this a direction we want to go?

@DougGregor Sorry about that. I reported the bug and had a go at adding tests and fixing it, I got stuck and had work commitments, it was also pre Swift 3 and iirc. dependent on changes out of scope of that release.
The bug (if unresolved) is still a big Swift performance issue though, and perhaps can be fixed with some of the recent improvements to generics and extensions. I think you've been doing work around that.
https://bugs.swift.org/browse/SR-413

@DougGregor at least until such time as we have generalized existentials, yes, we'd like this to happen.

I'm closing this, the work is still necessary, but this branch is well and truly stale.


Card component

this is the second variant of the project card component

If no-one is working on this I can take this issue.

Awesome, thanks Jason!

How's the progress on this? Is this still needed at this point, the other design works fine for us. I would be open to mixing and matching card components.

It's been done - see #37. I still need to make the card responsive tho


fail to run test 'test_container_probing'

I'm trying to create a package for ArchLinux. When runs the test, I got:
======================================================================
FAIL: test_container_probing (tests.test_file_probing.TestDataProbe)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/python-av/src/PyAV-6.2.0/tests/test_file_probing.py", line 91, in test_container_probing
    'uid': '4482d537-4203-ea40-9e4e-08a22900dd39',
AssertionError: {'operational_pattern_ul': '060e2b34.040101[674 chars]ent'} != {'application_platform': 'AAFSDK (MacOS X)'[609 chars]d39'}
Diff is 764 characters long. Set self.maxDiff to None to see it.

----------------------------------------------------------------------
Ran 157 tests in 122.163s

FAILED (failures=1, skipped=3)
Test failed: <unittest.runner.TextTestResult run=157 errors=0 failures=1>
error: Test failed: <unittest.runner.TextTestResult run=157 errors=0 failures=1>

Could you post the full diff as it is truncated ?

I build it with this PKGBUILD. To reproduce, you need:

ArchLinux environment with devtools installed
Download this PKGBUILD
Build this package in a clean chroot: extra-x86_64-build

log.txt

Unfortunately the diff is still truncated, you need to modify the test_file_probing.py file and add maxDiff = None like this:
class TestDataProbe(TestCase):
    maxDiff = None

    def setUp(self):
        self.file = av.open(fate_suite('mxf/track_01_v02.mxf'))

after test_file_probing.py:
class TestDataProbe(TestCase):
    def setUp(self):
        self.maxDiff = None
        self.file = av.open(fate_suite('mxf/track_01_v02.mxf'))

here is the log.txt

I believe this was fixed by 76e090dcb8ecb54d1c0c520774a885e8f2cf734c


[GEP-13] Make ManagedSeed spec.shoot field optional

How to categorize this PR?
/area control-plane
/kind enhancement
/priority normal
What this PR does / why we need it:
Makes the ManagedSeed spec.shoot field optional to avoid having to specify it in a ManagedSeedSet template.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Based on #3643, marked as "Draft" until that one is merged.
Release note:
NONE

/cc @rfranzke @danielfoehrKn


Enable body scroll not working sometimes

Sometimes, the function to enable scroll has no effect.
As you can see on your own demo page:

There is no scroll bar and I cannot scroll anywhere with the mouse wheel. It comes back if I click disable and enable again. But on my web page the user doesn't have this option.
I'm on Chrome 84.0.4147.105

I did a quick research and this seems to happen if you click "Disable" twice, and then try to enable it.
This happens because disableBodyScroll() does not check whether given element is already disabled, and effectively doubles the amount of locks on that given element.

I did a quick research and this seems to happen if you click "Disable" twice, and then try to enable it.
This happens because disableBodyScroll() does not check whether given element is already disabled, and effectively doubles the amount of locks on that given element.

@adamwych Looks like https://bodyscrolllock.now.sh is deployed with an old version of the library. @willmcpo is this meant to update automatically?

hey unfortunately there's no CICD setup to automatically update the demos. Apologies I'm a bit short of time. I've manually updated the demo and their links for now.
If someone could set up the Github Actions to get that up and running, that'd be cool =)

@willmcpo  I would be inclined to use a postpublish hook rather than CI for this, that way the demo will always be running the latest version of the package.

They stopped the repairs. I had to do it myself, in the same way, with a new version of typeScript. And fix these problems for everyone to use. add react hooks、vue3 example
npm i body-scroll-lock-upgrade

repair log，Refer to the releases page.


Try building on macOS

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

I've submitted a bug report upstream for the failing tests: https://lists.gnu.org/archive/html/bug-tar/2019-11/msg00010.html

Down to 1 failing test, submitted another bug report upstream: https://lists.gnu.org/archive/html/bug-tar/2019-12/msg00001.html

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


[Feedback a bit about part 3 video] Some small-ish suggestions in regards to the video at https://www.youtube.com/watch?v=cMwlYZ78uaQ (Part 3 of the glimmer-swt series I think)

Hey there Andy,
Just finished watching https://www.youtube.com/watch?v=cMwlYZ78uaQ Part 3.
I will give some feedback or ideas. Please, as always, pick/adapt what may
seem appropriate, and ignore/reject what is not - it is meant as a
feedback.
The duration, I think, is fine. I guess most people are able to watch
3 minutes attentively; may easily go up to 5 minutes too (I understand
it depends on the complexity of the app and the concepts within, so
simpler widgets are easier to explain I guess).
I also learned something new, e. g. the Glimmer::UI::CustomShell
module.
I have a small suggestion to make for the widgets on the left side.
Since you now have at the least three videos, perhaps you may want
to indicate that videos are available for some of the widgets in
use. An emoji may suffice such as the 📹 or any other fitting one.
It could be such an icon next to the label description of the
launcher-button, with the URL to the video (to youtube I
suppose). That way newcomers could quickly watch the video.
I have a second suggestion: perhaps it may be useful to embed the
widget on the very right side without even needing to press launch.
Now this may not be wanted by you or the user perhaps, as the user
may not want to launch everything as-is when merely selecting another
widget in the tutorial. But my idea here is a bit different to that.
For instance, my idea would be to embed the widget such as the
"Hello, Shape!" variant,and it would be shown at once on the very
right hand side (right of the code in use). Then, if the user
makes a modification to the code, it could be auto-run on that
very right instance as-is - a bit like javascript, in the browser,
where you can change the HTML colour in use, and it is shown at
once. Something like that. People could get instant visual
feedback. Not sure how much work that may be, so please, don't
get too distracted by that. It was just a loose idea.
Last but not least, I think what may also be interesting would
be to compare the situation between different glimmer variants.
You showed the glimmer for SWT variant in the video. I think it
may be interesting if you could have one video (in the future,
does not have to be now) that could answer this question:
"Can we use the same code base for different toolkits?"
e. g. in the approach you showed with the class-based approach
where you pull in the module Glimmer::UI::CustomShell and
then it, I assume, acts solely on the first require line that
you use, e. g. in that case require 'glimmer-dsl-swt'. It
would be interesting if you could replace that with, say,
libui or gtk or tk, and compare the result as-is. Whether the
same code may work. Perhaps even do that on tetris :D but that
may be a bit too complex, so perhaps just as a comparison in one
of any other upcoming video if you plan to provide more tutorials
of that.
Also also, very last, glimmer ( https://rubygems.org/gems/glimmer )
is at almost 100.000 downloads now. That's always a first milestone,
until you are at 500.000 then. :D \o/
Ah and perhaps as a very very very last - in any other example
perhaps you can show some different colours in use if someone
wants to style it (or whatever other effects are available; I
am not that familiar with SWT to know what can be done with
it, you probably know that much better than I do). Anyway that's
it for this issue.)

I have a small suggestion to make for the widgets on the left side.
Since you now have at the least three videos, perhaps you may want
to indicate that videos are available for some of the widgets in
use. An emoji may suffice such as the 📹 or any other fitting one.
It could be such an icon next to the label description of the
launcher-button, with the URL to the video (to youtube I
suppose). That way newcomers could quickly watch the video.

That is a great idea. I just added to TODO.md.

I have a second suggestion: perhaps it may be useful to embed the
widget on the very right side without even needing to press launch.
Now this may not be wanted by you or the user perhaps, as the user
may not want to launch everything as-is when merely selecting another
widget in the tutorial. But my idea here is a bit different to that.
For instance, my idea would be to embed the widget such as the
"Hello, Shape!" variant,and it would be shown at once on the very
right hand side (right of the code in use). Then, if the user
makes a modification to the code, it could be auto-run on that
very right instance as-is - a bit like javascript, in the browser,
where you can change the HTML colour in use, and it is shown at
once. Something like that. People could get instant visual
feedback. Not sure how much work that may be, so please, don't
get too distracted by that. It was just a loose idea.

I already implemented this functionality in the DCR Programming Language for kids since it would be useful for children to have that sort of auto-update behavior: https://github.com/AndyObtiva/dcr
However, for expert software engineers, as noted before, this sort of functionality, while nice, is not that important to be productive since you can relaunch the app instantly in either the Gimmer Meta-Sample or in a Glimmer-based Text Editor like Gladiator.
Additionally, the app is modeled as a window. It would be weird to embed it into the Glimmer Meta-Sample as a non-window widget. That would confuse software engineers instead of helping them learn.

Last but not least, I think what may also be interesting would
be to compare the situation between different glimmer variants.
You showed the glimmer for SWT variant in the video. I think it
may be interesting if you could have one video (in the future,
does not have to be now) that could answer this question:
"Can we use the same code base for different toolkits?"
e. g. in the approach you showed with the class-based approach
where you pull in the module Glimmer::UI::CustomShell and
then it, I assume, acts solely on the first require line that
you use, e. g. in that case require 'glimmer-dsl-swt'. It
would be interesting if you could replace that with, say,
libui or gtk or tk, and compare the result as-is. Whether the
same code may work. Perhaps even do that on tetris :D but that
may be a bit too complex, so perhaps just as a comparison in one
of any other upcoming video if you plan to provide more tutorials
of that.

Glimmer DSL for SWT and Glimmer DSL for Opal are the only GUI DSLs that have support for Class-Based Custom Widgets (using Glimmer::UI::CustomShell, Glimmer::UI::CustomWidget, and Glimmer::UI::CustomShape) like what you saw in Tutorial 3. I am planning to add that feature to Glimmer DSL for LibUI in the near future. It is in the project TODO.md file (though it currently supports Method-Based Custom Controls as you already know).

Also also, very last, glimmer ( https://rubygems.org/gems/glimmer )
is at almost 100.000 downloads now. That's always a first milestone,
until you are at 500.000 then. :D \o/

Thank you. By the way, the Glimmer DSL for SWT Ruby gem already crossed the 100,000 download threshold!

Ah and perhaps as a very very very last - in any other example
perhaps you can show some different colours in use if someone
wants to style it (or whatever other effects are available; I
am not that familiar with SWT to know what can be done with
it, you probably know that much better than I do). Anyway that's
it for this issue.)

Although SWT does support CSS, I intentionally have not exposed that feature yet because it is extremely low priority for proper business desktop development. Most desktop apps should intentionally follow the style guide of the operating system they run on, adhering to all the standard widget colors and themes so that when a user adjusts their operating system theme, the widgets in native GUI apps like those of Glimmer DSL for SWT adjust automatically.
It is greatly discouraged to customize the look of desktop apps beyond simple text font and text color adjustments. As by sticking to the defaults, desktop apps are developed much faster, maintained much more simply, and are much more user-friendly and easy to understand by users. Adding foreign styles confuses users (just like many web apps are confusing). It is better to stay away from it except in rare circumstances where the app is highly visual by nature.
In the cases of highly visual apps, it is simple to customize everything with vector graphics, which is done with the Canvas Shape DSL in SWT and Area API in LibUI.
In any case, such advanced customizations of color and look are beyond the scope of the video tutorials. Software engineers could always refer to the SWT Javadoc in the rare case of needing to make such customizations (or even look into using the unexposed SWT CSS feature if absolutely needed, but again, it is highly discouraged to complicate things with CSS for 99% of the desktop apps out there since CSS is highly over-engineered and has too many properties to learn and master, which slow software engineers down as opposed to simply sticking to the operating system standard guidelines)

Hi, I have some good news!
I finally added support for class-based custom controls and custom windows (aka applications) to Glimmer DSL for LibUI (supporting the body keyword like its use in Glimmer DSL for SWT video tutorials).
It is demonstrated in this example:
https://github.com/AndyObtiva/glimmer-dsl-libui#class-based-custom-controls
It is explained in Custom Keywords:
https://github.com/AndyObtiva/glimmer-dsl-libui#custom-keywords
Example Code:
require 'glimmer-dsl-libui'
require 'facets'

Address = Struct.new(:street, :p_o_box, :city, :state, :zip_code)

class FormField
  include Glimmer::LibUI::CustomControl

  options :model, :attribute

  body {
    entry { |e|
      label attribute.to_s.underscore.split('_').map(&:capitalize).join(' ')
      text <=> [model, attribute]
    }
  }
end

class AddressForm
  include Glimmer::LibUI::CustomControl

  options :address

  body {
    form {
      form_field(model: address, attribute: :street)
      form_field(model: address, attribute: :p_o_box)
      form_field(model: address, attribute: :city)
      form_field(model: address, attribute: :state)
      form_field(model: address, attribute: :zip_code)
    }
  }
end

class LabelPair
  include Glimmer::LibUI::CustomControl

  options :model, :attribute, :value

  body {
    horizontal_box {
      label(attribute.to_s.underscore.split('_').map(&:capitalize).join(' '))
      label(value.to_s) {
        text <= [model, attribute]
      }
    }
  }
end

class AddressView
  include Glimmer::LibUI::CustomControl

  options :address

  body {
    vertical_box {
      address.each_pair do |attribute, value|
        label_pair(model: address, attribute: attribute, value: value)
      end
    }
  }
end

class ClassBasedCustomControls
  include Glimmer::LibUI::Application # alias: Glimmer::LibUI::CustomWindow

  before_body do
    @address1 = Address.new('123 Main St', '23923', 'Denver', 'Colorado', '80014')
    @address2 = Address.new('2038 Park Ave', '83272', 'Boston', 'Massachusetts', '02101')
  end

  body {
    window('Class-Based Custom Keyword') {
      margined true

      horizontal_box {
        vertical_box {
          label('Address 1') {
            stretchy false
          }

          address_form(address: @address1)

          horizontal_separator {
            stretchy false
          }

          label('Address 1 (Saved)') {
            stretchy false
          }

          address_view(address: @address1)
        }

        vertical_separator {
          stretchy false
        }

        vertical_box {
          label('Address 2') {
            stretchy false
          }

          address_form(address: @address2)

          horizontal_separator {
            stretchy false
          }

          label('Address 2 (Saved)') {
            stretchy false
          }

          address_view(address: @address2)
        }
      }
    }
  }
end

ClassBasedCustomControls.launch

Cheers!

I just made a release of Glimmer DSL for SWT (<IP_ADDRESS>) with a "Tutorial" button in the Glimmer Meta-Sample that can be clicked for samples that have a tutorial in Youtube and it opens the Youtube video with autoplay in a separate window.

Wow!  The "Tutorial" button is great.  Thanks!!!
Wayne
On Sun, May 1, 2022 at 3:41 PM Andy Maleh @.***> wrote:

I just made a release of Glimmer DSL for SWT (<IP_ADDRESS>) with a "Tutorial"
button in the Glimmer Meta-Sample that can be clicked for samples that have
a tutorial in Youtube and it opens the Youtube video with autoplay in a
separate window.
[image: Screen Shot 2022-05-01 at 6 40 01 PM]
https://user-images.githubusercontent.com/23052/166167448-cdfd07f9-44d9-4d57-878a-533bf1228feb.png
[image: Screen Shot 2022-05-01 at 6 40 21 PM]
https://user-images.githubusercontent.com/23052/166167453-45828fff-bfdf-4a02-a52f-502e7eb304b5.png
—
Reply to this email directly, view it on GitHub
https://github.com/AndyObtiva/glimmer-dsl-swt/issues/18#issuecomment-1114354675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADKW4X6GZZLDFOH5ZG236TVH4CBHANCNFSM5OV2LYMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Fluent API HasForeignKey Breaking Change from 2.1 to 2.2

There's a breaking change between EF Core 2.1 and 2.2.
It seemed easier to create a quick repo with a minimal example that demonstrates the issue than to inline all the code here.  See this repository. If that's problematic for some reason, I can certainly also upload the code directly here.
The issue seems to stem from shadow properties in combination with HasForeignKey.
Steps to reproduce

git clone https://github.com/danstur/EfCoreBreakingChange.git
Execute CreateDb.sql on SQL Server 2017 (the real issue occurs at least on 2016 as well, but I only tested the minimal sample on my 2017 install - probably DB independent).
adapt connectionstring in Program.cs:12 as required
execute program ==> no exceptions, everything ok.
Update to 2.2 EF Core NuGets and rebuild to make sure nugets are switched.
Execute Program again. This time an exception occurs.

Message: The relationship from 'OutboundDelivery.Sender' to 'Site' with foreign key properties {'SenderId' : string} cannot target the primary key {'Id' : int} because it is not compatible. Configure a principal key or a set of compatible foreign key properties for this relationship.
Stack Trace:
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelValidator.ValidateNoShadowKeys(IModel model)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Infrastructure.RelationalModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Internal.SqlServerModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ValidatingConvention.Apply(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ImmediateConventionScope.OnModelBuilt(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.ModelBuilder.FinalizeModel()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.Set[TEntity]()
   at EfCoreBreakingChange.Program.<Main>d__0.MoveNext() in C:\dev\OpenSourceProjects\EfCoreBreakingChange\EfCoreBreakingChange\Program.cs:line 64
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at EfCoreBreakingChange.Program.<Main>(String[] args)

Workarounds

Fix1: Adding builder.Property<int>("SenderId"); to the OutboundDeliveryTypeConfiguration fixes the issue as expected.
Fix2: Removing the IsRequired after .HasForeignKey("SenderId") also fixes the issue. This one seems like an unintended interaction.

Further technical details
EF Core version: 2.2
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10 x64 1803
IDE: Visual Studio 2017 15.9.3

Seems that we missed this case in https://github.com/aspnet/EntityFrameworkCore/pull/13720


Changing Variable to a JSON value in the UI makes next Terraform run fail

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform Version
terraform 0.15.3 (I know it's old, but I don't believe the issue is there)
provider v2.2.2

Affected Resource(s)

prefect_variable

Terraform Configuration Files

resource "prefect_variable" "some_variable" {
  name = "some_variable_name"
  value = jsonencode([])
}

Expected Behavior
After creating the variable, I expected the variable's value to be a JSON.
After modifying the value from "[]" to ["some_value"] (notice the absence of surrounding double-quotes) in the UI and trying to re-apply the terraform plan: I would expect it to convert the JSON to a String so I can decode it and use it.
Actual Behavior
After creating the variable, the value is a string "[]"
Applying the plan results in an error:
Could not get Variable, unexpected error: failed to decode response: json: cannot unmarshal array into Go struct field Variable.value of type string
Even when adding an ignore_changes lifecycle rule, the problem persists. (Which makes sense. It's still a data source).
Steps to Reproduce

terraform apply
In the Cloud UI, change the value from "[]" to ["some_value"]
terraform apply

Important Factoids

N/A
References

N/A

thanks for raising @felixpelletier - let us take a look at this

Alrighty, looks like I was able to replicate this:
First, I created a variable in the Prefect UI and gave it a value of ["some_value"].
Then I created the Terraform config to read that variable as a datasource:

So what's the fix? We'll want to change the underlying Terraform Type of Variable values from string to JSON. This is due to changes made fairly recently to Variables in the API to make them JSON objects instead of just strings (example: https://github.com/PrefectHQ/prefect/pull/13543).
We'll go ahead and do that in the provider and publish that change as soon as we can. In the meantime, you should be able to work with plain strings just fine. Using JSON objects (arrays, maps, etc) will be supported once we push that update.
Thanks again @felixpelletier!

Hi @felixpelletier, we've released v2.5.0 which includes a change to the variable value type to a dynamic Terraform type, which supports more types than just a string. The specific types supported are listed in the docs, and we're definitely open to supporting more types in the future depending on use cases.
Thanks again for reporting this 👍🏼


Shortcut Guide won't close

Microsoft PowerToys version
0.35.0
Running as admin

[ ] Yes

Area(s) with issue?
Shortcut Guide
Steps to reproduce
I'm not sure how I made it happen but my finger slipped while pasting something with CTRL+V and the shortcut menu came up and stayed up. Even though I wasn't pressing any keys. I tried holding down the Windows key again but it wouldn't close. I tried using one of the shortcuts in the guide but it stayed open. I eventually had to exit out of PowerToys completely to get it to go away as it was blocking one of my screens and I couldn't work.
PowerToysReport_2021-04-22-09-25-10.zip
✔ Expected Behavior
Shortcut Guide pops up when holding down Windows key for a few seconds. Automatically closes when Windows key is released.
❌ Actual Behavior
Some key combination (not sure what) caused the Shortcut Guide to open and stay open, with no obvious way to close it. I had to kill the PowerToys app completely to get rid of it.
Other Software
No response

@bickitybam
did you try pressing the Esc key?

@enricogior on .36, with win+?, i can repro this.  Esc won't close for me.  I have to hit Win+? again

@enricogior
We handle ESC key in the SG window's WndProc. We will still get this issue if for some reason SG window is not focused.

@mykhailopylyp
let's complete the migration work. If it turns out that losing focus is a common scenario we will consider handling the Esc key in a kb hook.

Resolved with the release of v0.41.


Need equivalent to assert.response()

Expresso had a really easy way to test servers and their responses: assert.response(server, ...)
I saw you use a small request class (support/http) in connect and express, but copying it to my code didn't work as expected. An official tool to ease this task would be really awesome.

The problem is that there's not one perfect way of testing requests/responses. For example, in Socket.IO there's many specific requirements as far as testing long polling, for which assert.response just didn't work well.
I think this would be a good standalone project: require('http-assert) Think should.js for http.

Quick usage example for self implemented http support version:
// /test/support/http.js
var app = require('../../app');
var http = require('http');

module.exports.request = function(path, cb) {
    var port = app.address().port;
    http.request({ path: path, port: port }).on('response', function(res) {
        res.body = '';
        res.on('data', function(chunk) {
            res.body += chunk;
        });

        res.on('end', function() {
            cb(res);
        });
    }).end();
}

// In your tests
var http = require('support/http');
require('should');

describe(...) {
    it(...) {
        http.request('/', function(res) {
            res.statusCode.should.equal(200);
        });
    }
}

closing for now since it's semi-unrelated (mocha wont bundle anything like this)

Has there been any change with this - ie. any new works created making this possible?
Can't get neither @MarioBehrendt 's solution or the http.js @visionmedia linked to working.

My version is pretty much a simple version of TJ's file. What's the problem? Can you paste your code and the errors, please?

Sorry. Had a syntax error that I overlooked.  Is there a way that I can test POST, PUT & DELETE and send data along the request by modifying your above example?
Are you guys sure that this can't be included or at least mentioned in in the documentation? I absolutely pulled my hair before I found this post.
Performing response-testing probably is what many people are looking for and it's a shame that they choose a different testing component when mocha seems so mature.

@theindustry there's no reason to package it in mocha, it's unrelated to the client-side and it's not the be-all end-all solution for testing HTTP. Eventually I'll be recommending visionmedia/superagent for testing HTTP related stuff but it's not quite there yet

Ok. Confused me a bit that it wasn't mentioned in mocha, but in expresso. Here's what I have come up to test GET, POST, PUT & DELETE on the same server:
var app = require('../../app'),
http = require('http');

module.exports = {

    _port : app.address().port,

    get: function(url, headers, callback) {

        headers = (headers) ? headers : {};
        headers.method = 'GET';
        headers.port = app.address().port;
        headers.path = url;

        http.request(headers).on('response', function(res) {

            res.body = '';
            res.on('data', function(part) { res.body += part;});
            res.on('end', function() { callback(res); });

        }).end();
    },

    post: function(url, headers, cb) {

        headers = (headers) ? headers : {};
        headers.method = 'POST';
        headers.port = app.address().port;
        headers.path = url;

        http.request(headers).on('response', function(res) {

            res.body = '';
            res.on('data', function(part) { res.body += part;});
            res.on('end', function() { callback(res);});

        }).end();

    },

    put: function(url, headers, cb) {

        headers = (headers) ? headers : {};
        headers.method = 'PUT';
        headers.port = app.address().port;
        headers.path = url;

        http.request(headers).on('response', function(res) {

            res.body = '';
            res.on('data', function(part) { res.body += part;});
            res.on('end', function() { callback(res);});

        }).end();

    },

    del: function(url, headers, cb) {

        headers = (headers) ? headers : {};
        headers.method = 'DELETE';
        headers.port = app.address().port;
        headers.path = url;

        http.request(headers).on('response', function(res) {

            res.body = '';
            res.on('data', function(part) { res.body += part;});
            res.on('end', function() { callback(res);});

        }).end();

    }

}


Could get used memory on my device, not on app

Summary

Version
10.11.0

Affected OS
Android

OS Version
13

Current behavior

I am using function getUsedMemory() to get used memory of android system, but it show memory of this app. How do I get used memory on device system? Thanks
Expected behavior

Could you add method get available memory?

No. I interpret your request, after the detail I posted in my comment, as if you did not read my comment.
I will not interact with this issue anymore.
If there is some API that does what you want, and still works on modern Android versions, you are welcome to post a PR.
Reasonable PRs are merged here.

Thanks for your explanation. I got it


Timeline slider- Hover effect year and side arrow

@teshukatepalli1  as discussed please look into this hover effect issue.
https://www.aldevron.com/25th-anniversary
https://main--aldevron--hlxsites.hlx.page/test/timeline-slide

@Kummu007 - Please validate

This is working as expected.


Move RPC related types in types/models

All types described by RPC specs shall reside in separate module inside types.

Closed as completed via #137.


Trying to fix RDT version

This is a parallel try to #113 (which is majorly stuck). I am trying to fix the version number in the docs.

Ryan mentioned this issue. I should check whether the toml install fixes this.

It seems that the version now works. this did the trick...I should really read my own notes. Ill use this to migrate the RTD config file to v2 anyways then...

Finally, this is resolved. What a great start to the weekend!


Build trade package in Rust implementation

Description

We want to swap over to Rust for all platform logic.
Specifics

[ ] add trade package to libraries/rust
[ ] define Client class

[ ] include new construct with Alpaca configuration values as parameters
[ ] add required methods

[ ] write "check market availability" method
[ ] write "get available tickers" method
[ ] write "set positions" method

[ ] include ticker and notional map as parameter

[ ] write "clear positions" method

[ ] add unit test coverage for all methods

Closing to consolidate into separate issues.


space at the end of a line in firefox doesn't seem to work

a new space at the end of a line in firefox returns the old model and doesn't update

Thanks for reporting this!  I'm not able to reproduce this, do you have more details?  For example, a screenshot or video of the issue, or if you're using a custom spec a link to the source.


Hacktoberfest Python Projects

Add any of your hacktoberfest python projects following the contributing guidelines.

please assign this to me @theadeyemiolayinka

@aman6969
You haven't submitted a PR yet.

and your upload files is locked i tried to submit PR in that

and your upload files is locked i tried to submit PR in that

@aman6969
I do not understand what you mean, are you unable to create a PR?

when i went to code section and trying to add file in it's showing adding and uploading files are locked @theadeyemiolayinka

@aman6969
Have you tried editing/uploading the files in your fork?

i have forked and uploaded my folder inside scr folder please check once @theadeyemiolayinka

i have created a game named it red ball @theadeyemiolayinka

@aman6969 Have you tried editing/uploading the files in your fork?

yes!!
@theadeyemiolayinka

@aman6969 Okay, try creating a PR from your fork now.
If you still can't, could you please share a screenshot of your problem?

okey @theadeyemiolayinka

please check i have created PR @theadeyemiolayinka

@aman6969 Good!
I left a review for you.

@aman6969 Seems like you're using github web, I'll take care of the issue

@aman6969 Good! I left a review for you.
thankyou
yes i saw your review i am doing it!!

@aman6969 Seems like you're using github web, I'll take care of the issue

yes!! @theadeyemiolayinka

i have made one more game will you merge it may i send you pull request? @theadeyemiolayinka

@aman6969 Yes, I'll make them for you.

@aman6969 Create a new issue for your new game and make sure to follow the guidelines this time.

@aman6969 Yes, I'll make them for you.

thank you so much @theadeyemiolayinka

@aman6969 Create a new issue for your new game and make sure to follow the guidelines this time.

ok i will take care of that. @theadeyemiolayinka

@aman6969 You're welcome.
Please learn how to use Github Desktop and git commands, it'll help your developer journey.
Fell free to star the repo.

@aman6969 You're welcome. Please learn how to use Github Desktop and git commands, it'll help your developer journey. Fell free to star the repo.

yes i am learning to use github desktop and git commands thankyou for your comments i have already stared the repo.


Ratified Version Document

Sscofpmf is ratified in 2021. However, the version of document is 0.5.2-frozen. Does the ratification bump the version to 1.0-ratified?

I saw a document with the tag v1.0.0, but the cover page of the source code still shows the version is 0.5.2-frozen.

@jjscheel: Is there anything that can be done about this?  This extension is mandatory in RVA23 so the spec shouldn't be in this semi-abandoned pre-ratification state.

This information will be included in the main ISA manual soon and all references to the previous doc will be archived.  So, an update for a version/title page seems not worth the time.  Would you agree?

@wmat, can you confirm that Sscofpmf  is in your Asciidoc chapters which will be built for the ISA manuals we're building?  If so, would you kindly provide a link to the branch here so that we can close this out with complete information?

@jjscheel it will be in priv (after Svinval) but is not there yet.

That's fine if it is actually soon.  One of the checklist items post-ratification should be to update things like this.  That obviously wasn't the case in 2021 when this was ratified.  This same problem also affects Sstc.

Good point, @pdonahue-ventana.
@rpsene, perhaps we can get a few sub-tasks in Jira for the following?

Updating the document to reflect "Ratified" state and building PDF.
Creating and submitting a final PR to riscv-isa-manual (for ISA and Fast Track only).
Publishing the Ratified document.

@jjscheel we already have it; we can improve the description of the item.

No, that is the review item to make sure the repo is in a good state.  It occurs BEFORE ratification.
@pdonahue-ventana, is talking about actions which must occur post ratification.  They aren't really "Ecosystem Development", but rather completion of the Ratification work.


Add random functionality to login screen override

closes #11731
Added an option to the LoginScreen plugin to set the background to be random.

This would be cool to get merged in. It looks up to date and no conflicts. Thanks for the work, author and reviewers :)


[Backport release-24.11] treewide: remove uneccessary uses of dotnetCorePackages.combinePackages

(cherry picked from commit 5b4d838e436555283587526f891ebee4ff97d6c0)

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 364981

x86_64-linux

:white_check_mark: 2 packages built:

fsautocomplete
space-station-14-launcher


autopairing

i want autopairing in kickstart because it less annoying and i am trying to add it but i cant

You should be able to activate autopairs by uncommenting this line: https://github.com/nvim-lua/kickstart.nvim/blob/master/init.lua#L879

thank you

thank you


Multi-part attachment doesn't set filename correctly

https://github.com/visionmedia/superagent/blob/master/lib/node/index.js#L200
The filename is passed to form-data as the last argument to append, but the last argument should be an options object.
https://github.com/felixge/node-form-data/blob/master/lib/form_data.js#L111
attach should either pass the filename wrapped in an object, or accept an options argument itself and pass it along to form-data, which allows setting a custom Content-Type.

I think this is fixed in master.


Medium term recommendations are not generated when 1 hour data is missing.

Medium-term recommendations are not generated only for 196 results when 1-hour data is missing in a 7 day data with a message : There is not enough data available to generate a recommendation.
For the same data, short-term recommendations are generated.
Below is the file with all the metrics and recommendations that are generated for every update of result.
output-19.2.csv
In the csv, medium-term recommendations are missing from row# 1044 to row# 1239.
Below is the output of listRecommendations for one of the timestamps.
/listRecommendations?experiment_name=advisor-backend-api|advisor-backend-api|deployment|advisor-stage|cluster1&monitoring_end_time=2023-06-09T20:30:00.000Z"
[
  {
    "cluster_name": "cluster1",
    "kubernetes_objects": [
      {
        "type": "deployment",
        "name": "advisor-backend-api",
        "namespace": "advisor-stage",
        "containers": [
          {
            "container_image_name": "quay.io/cloudservices/advisor-backend:530e33b",
            "container_name": "advisor-backend-api",
            "recommendations": {
              "version": "1.0",
              "notifications": {
                "112101": {
                  "type": "info",
                  "message": "Duration Based Recommendations Available",
                  "code": 112101
                }
              },
              "data": {
                "2023-06-09T20:30:00.000Z": {
                  "duration_based": {
                    "short_term": {
                      "monitoring_start_time": "2023-06-08T20:15:01.000Z",
                      "monitoring_end_time": "2023-06-09T20:30:00.000Z",
                      "duration_in_hours": 24.0,
                      "pods_count": 10,
                      "confidence_level": 0.0,
                      "current": {
                        "limits": {
                          "cpu": {
                            "amount": 1.0,
                            "format": "cores"
                          },
                          "memory": {
                            "amount": 512.0,
                            "format": "MiB"
                          }
                        },
                        "requests": {
                          "cpu": {
                            "amount": 0.2,
                            "format": "cores"
                          },
                          "memory": {
                            "amount": 256.0,
                            "format": "MiB"
                          }
                        }
                      },
                      "config": {
                        "limits": {
                          "cpu": {
                            "amount": 0.535031,
                            "format": "cores"
                          },
                          "memory": {
                            "amount": 612.196875,
                            "format": "MiB"
                          }
                        },
                        "requests": {
                          "cpu": {
                            "amount": 0.535031,
                            "format": "cores"
                          },
                          "memory": {
                            "amount": 612.196875,
                            "format": "MiB"
                          }
                        }
                      },
                      "variation": {
                        "limits": {
                          "cpu": {
                            "amount": -0.46496899999999997,
                            "format": "cores"
                          },
                          "memory": {
                            "amount":<PHONE_NUMBER>9999998,
                            "format": "MiB"
                          }
                        },
                        "requests": {
                          "cpu": {
                            "amount": 0.335031,
                            "format": "cores"
                          },
                          "memory": {
                            "amount": 356.196875,
                            "format": "MiB"
                          }
                        }
                      },
                      "notifications": {}
                    },
                    "medium_term": {
                      "pods_count": 0,
                      "confidence_level": 0.0,
                      "notifications": {
                        "120001": {
                          "type": "info",
                          "message": "There is not enough data available to generate a recommendation.",
                          "code": 120001
                        }
                      }
                    },
                    "long_term": {
                      "pods_count": 0,
                      "confidence_level": 0.0,
                      "notifications": {
                        "120001": {
                          "type": "info",
                          "message": "There is not enough data available to generate a recommendation.",
                          "code": 120001
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        ]
      }
    ],
    "version": "1.0",
    "experiment_name": "advisor-backend-api|advisor-backend-api|deployment|advisor-stage|cluster1"
  }
]

To reproduce:
From PR: https://github.com/kruize/kruize-demos/pull/52
cd recommendations_Infra_demo
./recommendations_demo.sh -c minikube -o docker.io/kruize/autotune_operator:<IP_ADDRESS>_rm -r --validate

For the start and end timestamps present in output file, no.of missing hours in between is 6.5 hrs.
Expected Total Hours: 361.75
Actual Total Hours (after subtracting missing data): 355.25
Missing Hours: 6.5

Closing it as there is a missing hours of ~6.5 even with threshold of 6 hrs to the monitoring_end_time.
Generating the recommendations as expected.


At the end print a blank page in iOS 8

First at all, this is a really great plugin!
I know that iOS 8 its very new. But I just want make you know about this bug.
I'm using Phonegap Build to use this plugin. And I've tested in iOS 6, iOS 7 and iOS 8.0.2, and works great, but just in iOS 8 at the end print a blank page. It's not a big deal, but can be fixed.

Cannot find a way to cut the last page. Testing with simulated printers a blank page gets added on printers with duplex.

This code works for me.
No excess paper.
      cordova.plugins.printer.print(         htmlContent,          {           name: 'printjob',           printerId: printerUrl, // ipp://192.168.##.##/printer           //duplex: false, // even if this is false, it still set to 1 in xcode. remove it!           landscape: false,            graystyle: true,            hidePaperFormat: true,           border: false,           hidePageRange: true         },           function(msg) {console.log('ok: ' + msg)},           function(msg) {alert('error: ' + msg)}         );


Add readinessProbe to deployment examples

        readinessProbe:
          httpGet:
            path: /healthz
            port: 8080
          initialDelaySeconds: 5
          timeoutSeconds: 1

Something like this, requires #10

Resolved in #759, dup of #695


update job reclaimed test case

update job reclaimed test case
error:
https://github.com/spidernet-io/spiderpool/runs/8044060861?check_suite_focus=true#step:14:74

关联 issue 没写


Pathfinder api cannot handle reqests made before socket finishes opening

any messages sent when the socket is not opened are ignored. This includes messages sent right after a pathfinder instance is instantiated when the websocket is in the process of opening. Instead, whenever a message request is attempted to be sent, the api should:

[x] If the socket is not ready, save the message and send it once the socket is opened
[x] Should handle multiple messages made before the socket is opened
[x] Messages should be sent in same order they are made in once the socket is opened
[x] If the socket is closed when a message is sent, it should probably print a readable error message, alternatively, the api could try to open a new socket if it is closed, but that requires more work and probably is unnecessary

I think I mostly fixed it in https://github.com/CSSE497/pathfinder.js/tree/fixed-bugs which is based off of the edits I used to get the chimney swap website to work, but you should make sure that it works and fix it if it doesn't

@danhanson , if you want the code to be updated, you need to open a pull request.

@danhanson I pulled the code. Can you update the check off list.

Ok


Conversion tools or instructions from standard OpenDrive Format to Apollo's HDMAP OpenDRIVE Format

Does anyone have the conversion tools or instructions from standard OpenDrive Format to Apollo's HD MAP OpenDRIVE Format？
Some correspondence example is also welcome.
Lots of people have got Apollo‘s HDMap specification here. #3005

I am also very interested in this. It could allow us to leverage tools/databases like openstreetmap .

Unfortunately we do not support this conversion internally, however our developer community is welcome to respond to this request.
@xmyqsh @christian-lanius thank you both for your interest in Apollo.

@christian-lanius I have several materials about this topic. If you are interesting, you could connect me here.

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions. Thanks!

@xmyqsh hi I'm also deeply interested on this topic, can you provide the materials that you have?

hi @xmyqsh
Could you please give me the materials about this topic?
<EMAIL_ADDRESS>

There is already a tool for now imap


Home page hyperlink has broken

Describe the bug
Please DO NOT use this template to ask question. For support visit Stack Overflow.
Home page hyperlink has broken
To Reproduce
Steps to reproduce the behavior:

Go to 'https://docs.microsoft.com/en-us/azure/bot-service/?view=azure-bot-service-4.0'
Click on 'Python Icon'
See error "404 Page not found issue"

Expected behavior
This "https://docs.microsoft.com/en-us/azure/bot-service/python/bot-builder-python-quickstart?view=azure-bot-service-4.0"  url has to open

Thanks for bringing this to our attention @rvinothrajendran. I'm updating the link now.

Closing now that the PR with the updated link has been merged.


Repositioning the direction of the community version of Redash.

Currently, RedashCommunity/redash occasionally updates with minor changes. I believe that RedashCommunity/redash should be repositioned. The community version of Redash should have a clear direction, whether it is to develop independently or to be compatible with the original Redash.

... whether it is to develop independently or to be compatible with the original Redash.

My thinking here is that we should provide a home for people who need to keep on using the public / Community version of Redash, as the original upstream project seems to be dead now. :frowning:
Once we have the initial builds working "ok", we can then develop things however people seem fit.  We'll need to make sure there's a clear upgrade path for people on the original Redash releases though, as that's likely a common starting point.


fix(c9s): update the constants from Packit

TODO:

[x] Write new tests or update the old ones to cover new functionality.
[x] Update doc-strings where appropriate.
[x] Update or write new documentation in packit/packit.dev.

Related to packit/packit#2085
Related to CentOS Stream support
Merge after packit/packit#2085

recheck

recheck

recheck


mauve compilation errors (when trying to run Java11 tests)

Not sure if I am missing a prereq (doesn't appear that any setup step fails), but failing to compile when attempting to run some Java11 tests:
23:03:20     [javac] /tmp/mauve/mauve/gnu/testlet/org/omg/CORBA_2_3/ORB/Valtype/cmInfo.java:15: error: package org.omg.CORBA does not exist
23:03:20     [javac] import org.omg.CORBA.DataInputStream;
23:03:20     [javac]                     ^
23:03:20     [javac] /tmp/mauve/mauve/gnu/testlet/org/omg/CORBA_2_3/ORB/Valtype/cmInfo.java:16: error: package org.omg.CORBA does not exist
23:03:20     [javac] import org.omg.CORBA.DataOutputStream;
23:03:20     [javac]                     ^
...
23:03:21     [javac]   symbol:   class BAD_INV_ORDER
23:03:21     [javac]   location: class testAny
23:03:21     [javac] /tmp/mauve/mauve/gnu/testlet/org/omg/CORBA/Any/testAny.java:111: error: cannot find symbol
23:03:21     [javac]                             throws BAD_OPERATION
23:03:21     [javac]                                    ^
23:03:33     [javac] 100 errors
23:03:33     [javac] 46 warnings

CORBA is one of the packages removed from Java 11.
https://github.com/eclipse/openj9/issues/992

Thanks @pshipton that explains it!
@Mesbah-Alam @lumpfish - Can someone look into this and to any other changes required in systemtest for Java11 support?  There are already some Java11 builds ready for testing against
...

Mauve is compiled and used as the workload in the load tests. We need to add an "EE implementation from elsewhere, such as Eclipse Jakarta", for Mauve to compile on Java 11. I will try it out locally and update this PR.

I would advocate removing the tests for the removed components.  There are already lots of tests which are excluded for one reason or another - the tests' requirement for prereqs being one of them - see https://github.com/AdoptOpenJDK/openjdk-systemtest/blob/master/openjdk.test.mauve/build.xml for how they are excluded at build (configure) time.  The tests would also need removing from the load test inventory files in https://github.com/AdoptOpenJDK/openjdk-systemtest/tree/master/openjdk.test.load/config/inventories/mauve

@Mesbah-Alam - do you know which are the tests we need to remove or do we need to do some local testing to get the list?

@lumpfish - I have removed the CORBA folders and subsequently been removing each referenced Java files (and Java files which fail to compile due to the removal of them) incrementally. Once I reach the point where no Java file needs to be removed I'l run the tests locally to see if they still run with these removals in place. I didn't see avy direct references of any CORBA classes in any of the inventory files-- but there could be references of tests that have been removed, in which case they'd have to be removed from the inventory xml too.

Peter Shipton confirmed, java.transaction module, on which implementation of several modularity tests depend, have been completely removed in Java 11 as part of https://github.com/eclipse/openj9/issues/992
All the following modules have been removed in java 11.
java.xml.ws (JAX-WS, plus the related technologies SAAJ and Web Services Metadata)
   java.xml.bind (JAXB)
   java.activation (JAF)
   java.xml.ws.annotation (Common Annotations)
   java.corba (CORBA)
   java.transaction (JTA)

   java.se.ee (Aggregator module for the six modules above)
   jdk.xml.ws (Tools for JAX-WS)
   jdk.xml.bind (Tools for JAXB

This means we need to re-implemented using modules that exist in Java 11.  Tests that need to be rewritten:
1) /openjdk.test.modularity/src/tests/com.test/net/adoptopenjdk/test/modularity/junit/TestStressLayers.java
2) /openjdk.test.modularity/src/com.stf/net/adoptopenjdk/test/modularity/PatchModuleImageTest.java
3) /openjdk.test.modularity/src/com.stf/net/adoptopenjdk/test/modularity/PatchModuleTest.java
4) /openjdk.test.modularity/src/com.stf/net/adoptopenjdk/test/modularity/UpgradeModPathTest.java

Systemtests compile fine with test.modularity excluded: https://ci.adoptopenjdk.net/view/work in progress/job/Grinder/106/console
I am going to create a PR that contains deletion of the corba related mauve classes and exclusion for modularity for Java 11.

Note: this only unblocks the Java 11 build to run JCK tests which are of higher priority. The personal build I ran didn't run any systemtests as I need to update the playlist and add <subset>SE110</subset> to the tests which will be handled in a separate PR.


Settings GUI

tabs for different preference groups, i.e. "keybinds", "graphics"(colors for the different blocks), "general"(set darkmode, etc, idk)...


Allow sharing of ports for ingress

Is your feature request related to a problem? Please describe.
Kafka by its nature requires that all brokers are exposed directly to Kafka clients, that is, the client needs to be able to form a TCP/IP connection to each and every broker in the Kafka cluster.  This gives Kroxylicious in a cloud environment a challenge.
One alternative is using a Kubernetes load balancer service. A naive arrangement would utilise a load balancer per Kafka broker and a additional one for bootstrap.  The disadvantage for this approach is additional cost: cloud providers often levy a per load balancer charge.  It would be more cost effective if one could use a single load load balancer and have connections routes to the correct broker.
It is this option that is the subject of this feature request.
Describe the solution you'd like

In the TLS use-case, Kroxylicious will have the ability to share ports for ingress
Kroxylicious will use SNI information in the TLS client hello to route the traffic to the right broker within the right virtual cluster.
It would be possible to configure Kroxylicious to use a port per virtual cluster or port for all clusters.

Describe alternatives you've considered
Using Kubernetes nodeport service is another option.
Here, separate port numbers are assigned to each broker of the Kafka cluster. Kubernetes arranges for the same port on every node in the Kubernetes cluster to be open.  Kafka clients can connect to any node and Kubernetes takes care of forwarding the traffic to the pod that running Kroxylicious.  Whilst this can work for Kroxylicious with what is being delivered by #254, there are some drawbacks: DNS records for the brokers need to be kept in sync with IPs of the nodes of the Kubernetes cluster (which can be tricky as nodes in the Kubernetes cluster can be cycled).  Nodeport can also be seen as a security risk by administrators which can present obstacles in corporations.
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I think this can be achieved using a ClusterEndpointProvider implementation that would look like this:
    clusterEndpointProvider:
      type: PortSharingSNI
      config:
        bootstrapAddress: mytenant1.kafka-service.com:9192
        brokerAddressPattern: broker-${nodeId}-mytenant1.kafka-service.com:9192

PortSharingSNI will require that the VirtualCluster is using TLS, otherwise it will report a configuration time error and fail.
KafkaProxy will query the VirtualCluster to work out which ports need to bound.  ClusterEndpointProvider will have  new property indicating if the provider supports port sharing.  KafkaProxy will use this information to work out if there are port conflicts between the virtual clusters.
In KafkaProxy handler chain will be refactored.  There will be a new handler (VirtualClusterResolver) in the chain that will use the SNI/target port information provided by the channel to resolve the virtualcluster/broker being connected to.  Once the virtual cluster is determine, the handle will instantiate the filter chain.  The filter chain will be made available to other handlers via a netty handler attribute.


Proper combination of news representation

Fusion should be done after concatenate
https://github.com/yusanshi/news-recommendation/blob/8323a4f8ca30dc91eab715b55b069cf1f981728d/src/model/LSTUR/news_encoder.py#L73-L76

Sorry but what's the fusion? Could you be a little more specific?


build: add missing dependencies

This fixes building CAPITests on Windows.  Unlike Unix, Windows does not
permit undefined references to symbols at link time.  Add the missing
link dependencies to ensure that we can resolve all symbols.  This
permits building CAPITests on Windows.

@swift-ci please smoke test


Correction of spanish localization

Fix accents over spanish locale.

Is there actually a change in characters here? Or are you just replacing characters with their equivalent Unicode escape sequences?  I'm don't think that is necessary.  We have plenty of other usage throughout moment of Unicode character literals.

I just replaced the characters with their equivalent escape code.
I try to use the locale on my site and the messages are bad formatted, I use UTF 8 over my all htmls.
Any thoughts?

Sorry, you'll have to explain better what you mean.  Please open an issue specifically about the problem you are seeing, and include enough detail to reproduce the problem.
If we were to make this change it would have to be comprehensive - not just for a single locale.  But I see no need to do that.  It is perfectly normal and acceptable to use these characters directly, and it usually works just fine.  If it didn't, our own momentjs.com website wouldn't work.


[Admin] (CATS) Address issues

Docs Build status updates of commit f58c0ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-json-autogeneration.md
:white_check_mark:Succeeded

docs/testing/clear-cache.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Org Stewards are treated as if they are admins

STR-
Log on as obrien (org steward) - minipax, miniplenty
Go to BreadBasket app ( App owner is julia and associated agency is minitrue)
Edit the app as obrien
Save
RESULTS- It allows other Org Stewards to save without validation as if they were an admin
EXPECTED RESULTS - Should validate and give an error to org steward letting them know they do not have the authority to edit a listing that does not belong to their org.

@mannyrivera2010 - can you review this and advise? - thanks,


[FIX] Fixing template string on electrodes for eeg and ieeg.

Summary
Closes: #649
Fixes the template strings in the modality-specific spec to match that of https://bids-specification.readthedocs.io/en/stable/99-appendices/04-entity-table.html#encephalography-eeg-ieeg-and-meg

This is in accordance with the entity table: https://bids-specification.readthedocs.io/en/latest/99-appendices/04-entity-table.html#encephalography-eeg-ieeg-and-meg ... so this is truly a fix.
unfortunately, as discussed in this issue comment, the validator is not precise enough to validate this. So the validator will still accept files like: *_task-Nonsense_electrodes.tsv. There is a similar issue here: https://github.com/bids-standard/bids-validator/issues/848
Still +1 to merge, then adjust mne-bids (https://github.com/mne-tools/mne-bids/pull/604), and then eventually improve the validator (better sooner than later)

Thanks @adam2392


Support Batched BLAS/External (Cgo/CUDA/OpenCL) for *LispMachine

*LispMachine should keep track of node dependencies and then perform batched BLAS calls. This would enable future use of CuBLAS ops

This one will be updated. Batching should be handled by the VMs

This will be good stuff considering AMD speedup their product release.

This is coming soon (well, the architecture anyway - see the current PR pending). The new architecture allows for the dynamic machines to use BatchedBLAS and CUDA. Also I have no ryzen machine to test on yet... so I am not sure how to play with that.

This was fixed in 215b466d


Fail to load all documents

All the documents on the home page fail to load when you try to display them, and the certificate also fails to download.

Hello @Salohyy212 😄. Thanks so much for giving us your feedback 🚀
How documents work in the web application:
Make sure you have a good internet connection for optimal use of the documents in the web application.
School certificate download:
The download of the school certificate is in progress via the following PR: https://github.com/hei-school/hei-admin-api/pull/418
If you still have any feedback to give us, don't hesitate. 😃


Update requirements for Chinese model NormalizedConfig

Type of Change
Chinese Model doesn't accept by optimum, so we use the commit id to add it to NormalizedConfig.
https://github.com/huggingface/optimum/pull/1490
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

https://inteltf-jenk.sh.intel.com/view/nlp-toolkit-validation/job/nlp-toolkit-validation-top-mr-extension/1452/

https://inteltf-jenk.sh.intel.com/view/nlp-toolkit-validation/job/nlp-toolkit-validation-top-mr-extension/1460/

@changwangss Please resolve the conflict we need this PR for Baichuan2-13B-Chat.


Add Code Coverage

Add code coverage tracking and reporting via Istanbul (nyc) and Coveralls.

Changes Unknown when pulling b182e82ac8bfc35b75bd8a1bdf76b991566b59da on feature/code-coverage into ** on develop**.


chore(release): 1.137.1

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 190a52eb542b03eef8fdc0900499c7cad2b23570
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 190a52eb542b03eef8fdc0900499c7cad2b23570
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Explicitly set GH_TOKEN permissions

change-type: patch

@pipex this one may need some help..

@ab77 could you update this line https://github.com/balena-os/mock-systemd-bus/blob/main/Dockerfile#L2 replacing as for AS?

Something updated because the base images are not pinned, I'll make the changes and we can as @klutchell to approve :)

hmm, actually I think this install method no longer works https://github.com/balena-os/mock-systemd-bus/blob/93eab2095cab12d4faf5006ceeefc85f13f7859c/install-rust.sh#L38
The URL there now points to some XML

hmm, actually I think this install method no longer works
https://github.com/balena-os/mock-systemd-bus/blob/93eab2095cab12d4faf5006ceeefc85f13f7859c/install-rust.sh#L38
The URL there now points to some XML

Nevermind, I see you figured the correct reason @ab77


Docs and comments: Change OSX -> macOS

Mac OS X was renamed to macOS at some point. Update references to OSX, OS X, Mac OS X, Mac OSX, and other permutations, to macOS, in README files and in comments of other files.

I will merge this despite the fact that it does not pass the nxstyle checks. We agreed early on that cosmetic changes will no be held to the same review standard.