posix: pthread_testcancel zephyrproject-rtos

Add posix pthread_testcancel()

Hi @moonlight83340 - would be happy to re-review if you can add some tests. For reference, I have a draft PR to implement pthread_testcancel() and some tests for it here, but it is currently blocked on a separate (and potentially separable) problem.
https://github.com/zephyrproject-rtos/zephyr/pull/67085/commits
"posix: threads: implement pthread_testcancel()" and "tests: posix: add tests for pthread_testcancel()"
I would be happy to modify my PR to focus more on the other issue. Feel free to lift details from my implementation.

Hi @moonlight83340 - would be happy to re-review if you can add some tests. For reference, I have a draft PR to implement pthread_testcancel() and some tests for it, but it is currently blocked on a separate (and potentially separable) problem.
https://github.com/zephyrproject-rtos/zephyr/pull/67085/commits "posix: threads: implement pthread_testcancel()" and "tests: posix: add tests for pthread_testcancel()"
I would be happy to modify my PR to focus more on the other issue. Feel free to lift details from my implementation.

Hi, Thank you for your review, I'm currently on vacations, would be glad to add somes tests and I if can use your PR for reference it would be great !

I check your code to do some changes, and it turns that I didn't understand well the use of PTHREAD_CANCEL_ENABLE. I also change the variables names..

@moonlight83340 - can you please fix the code formatting issues reported?
Also, please provide separate commits: 1 for adjusting code in lib/posix, 2 for adding a test under tests/posix/common, and 3 a small commit to update the posix docs

Thanks, will do that in this week.

@moonlight83340 - sorry, slipped my mind earlier. Can you please also add a 3rd commit for the documentation? I think it will maybe be under aep/index.rst

@moonlight83340 - sorry, slipped my mind earlier. Can you please also add a 3rd commit for the documentation? I think it will maybe be under aep/index.rst

no problem, I was about to do that ^^

@moonlight83340 - if possible as well, could you provide a more detailed description in the summary area?
That shouldn't require any respin, luckily. In the future, please also ensure that you follow the contribution guidelines.
https://docs.zephyrproject.org/latest/contribute/guidelines.html

@moonlight83340 - if possible as well, could you provide a more detailed description in the summary area?
That shouldn't require any respin, luckily. In the future, please also ensure that you follow the contribution guidelines.
https://docs.zephyrproject.org/latest/contribute/guidelines.html

Sorry maybe I don't fully understand do you mean, in the commit part ?
I can amend the commit if so but will need to forced push after I think.

Sorry maybe I don't fully understand do you mean, in the commit part ?
I can amend the commit if so but will need to forced push after I think.

Nevermind - it's ok

@moonlight83340 - looks like there are some merge conflicts. Remember to fetch from upstream and rebase on main

@moonlight83340 - just a gentle ping to see if you are able to make any more progress on this. You might need to rebase and check that CI tests are all passing.

@moonlight83340 - just a gentle ping to see if you are able to make any more progress on this. You might need to rebase and check that CI tests are all passing.

Hi, I rebase on main was trying to add my commit after but run, into somes problems so I will check on this week end. would like to end this soon ^^
Errors are somethings weird.

@moonlight83340 - just a gentle ping to see if you are able to make any more progress on this. You might need to rebase and check that CI tests are all passing.

So I remove all my commit and then push one only to try if it's still fail..
And I'm asking myself is there any chance the main branch have some fails in the github action ?

It looks like there are some compile errors on this PR. The missing members can be found in t->attr
/__w/zephyr/zephyr/lib/posix/pthread.c:697:22: error: 'struct posix_thread' has no member named 'cancel_state'
  697 |                 if (t->cancel_state != PTHREAD_CANCEL_ENABLE) {
      |                      ^~
/__w/zephyr/zephyr/lib/posix/pthread.c:700:22: error: 'struct posix_thread' has no member named 'cancel_pending'
  700 |                 if (t->cancel_pending) {
      |                      ^~
/__w/zephyr/zephyr/lib/posix/pthread.c:702:26: error: 'struct posix_thread' has no member named 'cancel_state'
  702 |                         t->cancel_state = PTHREAD_CANCEL_DISABLE;

It looks like there are some compile errors on this PR. The missing members can be found in t->attr
/__w/zephyr/zephyr/lib/posix/pthread.c:697:22: error: 'struct posix_thread' has no member named 'cancel_state'
  697 |                 if (t->cancel_state != PTHREAD_CANCEL_ENABLE) {
      |                      ^~
/__w/zephyr/zephyr/lib/posix/pthread.c:700:22: error: 'struct posix_thread' has no member named 'cancel_pending'
  700 |                 if (t->cancel_pending) {
      |                      ^~
/__w/zephyr/zephyr/lib/posix/pthread.c:702:26: error: 'struct posix_thread' has no member named 'cancel_state'
  702 |                         t->cancel_state = PTHREAD_CANCEL_DISABLE;

thank you and sorry, I'm changing my test there are some errors and change I would do. Maybe will send it tonight !

can't tell what wrong with the doc build, seems unrelated

Exception occurred:
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 383, in _recv
    raise EOFError

Interesting, this does not like the runner issue seen in the other PR, maybe one of the process is crashing, OOMing or something. @kartben does the error ring any bell?

Needs a rebase on main @moonlight83340

Exception occurred:
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 383, in _recv
    raise EOFError

Interesting, this does not like the runner issue seen in the other PR, maybe one of the process is crashing, OOMing or something. @kartben does the error ring any bells?

currently testing this locally ... very weird looking error

@fabiobaltieri sounds like OOM indeed, but not sure how to best fix this (and I can't reproduce locally). I am also afraid that other PRs might start failing if we are somewhat close to the memory limits of the CI runner. I think using - j8 or something would do the trick, but that doesn't sound ideal?
https://github.com/zephyrproject-rtos/zephyr/blob/476a224dfa280416d74a7304fda8a14d0fa2fc5c/.github/workflows/doc-build.yml#L209
Really tempted to move forward with https://github.com/zephyrproject-rtos/zephyr/pull/64724 but this might be bad timing so close to 3.6 ...?

Let's see what #68409 has to say...

Well, switching to Sphinx 7.1 is doing the trick, it would seem.
https://builds.zephyrproject.io/zephyr/pr/68409/docs/services/portability/posix/option_groups/index.html

Really tempted to move forward with #64724 but this might be bad timing so close to 3.6 ...?

We are no in feature freeze yet, go for it, 3.6 is in three weeks plenty of time to roll back if something breaks.

Exception occurred:
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 383, in _recv
    raise EOFError

Interesting, this does not like the runner issue seen in the other PR, maybe one of the process is crashing, OOMing or something. @kartben does the error ring any bells?

Oh, only realizing now that apparently re-running the CI job was enough for the HTML build to pass, so this is now green even without having to wait on #64724


[BUG] attempt to index field 'Emitter' (a nil value)

Short Description
A player keeps getting this client side error, two errors happen roughly at the same time and both happened respectively 2 and 3 times within a minute.
Branch and Version
Latest master.
Console Error Logs (Optional)
addons/acf-3/lua/effects/acf_penetration.lua:99: attempt to index field 'Emitter' (a nil value)
  1. Concrete - addons/acf-3/lua/effects/acf_penetration.lua:99
   2. unknown - addons/acf-3/lua/effects/acf_penetration.lua:31
    3. Effect - [C]:-1
     4. PenetrationEffect - addons/acf-3/lua/acf/shared/ammo/ap.lua:216
      5. unknown - addons/acf-3/lua/effects/acf_bullet_effect.lua:41
   0.  Concrete - addons/acf-3/lua/effects/acf_penetration.lua:99
    1.  unknown - addons/acf-3/lua/effects/acf_penetration.lua:31
     2.  Effect - [C]:-1
      3.  PenetrationEffect - addons/acf-3/lua/acf/shared/ammo/ap.lua:216
       4.  unknown - addons/acf-3/lua/effects/acf_bullet_effect.lua:41

ParticleEmitter: Couldn't make emitter! Too many emitters!
  1. unknown - addons/acf-3/lua/effects/acf_penetration.lua:15
   2. Effect - [C]:-1
    3. PenetrationEffect - addons/acf-3/lua/acf/shared/ammo/ap.lua:216
     4. unknown - addons/acf-3/lua/effects/acf_bullet_effect.lua:41

Additional info (Optional
This might be conflicting with addons such as PAC3 that also use the emitter system.

Fixed on d2189ce.


Fix type sigs

#11 should be merged first. I can rebase afterwards.

#11 is merged, please rebase.


Vulkan 1.2.268

Description of changes
Bumps everything to latest SDK. vulkan-tools currently broken on Darwin.
Things done

Built on platform(s)

[x] 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/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

Tested everything affected on Linux on top of master and it builds fine. Darwin vulkan-tools patch needs a rebase.

Force-pushed to fix vulkan-tools-lunarg.

As discussed previously at length, we should stick to SDK versions.

Renormalized everything to use SDK tags and updated to 1.2.268. @reckenrode wanted to handle vulkan-tools on Darwin and MoltenVK.

 Verified everything builds again.

I pushed a commit with the fixes to vulkan-tools on Darwin.

To clarify, the new SDK version is 1.3.268, right?

Yes.

Thanks for the hard work @K900 😊


Can't install any nix-gaming package when installing NixOS with nixos-install

Whenever I include any of the nix-gaming packages in my flake to install, such as in my gaming flag:
https://github.com/NovaViper/NixConfig/blob/6a369506a3d0b85601ec9d5179021a70f76e55b3/home/novaviper/features/games/default.nix#L13
I get the following error when I run nixos-install --flake .#laptop --root /mnt: https://pastebin.com/9UcFfnSe

The error doesn't seem to stem from any particular package, when checking using nix repl and :lf github:fufexan/nix-gaming. Are you sure the source is actually the nix-gaming repo?

I'm not sure how I can check where exactly the issue is coming from. 🤷🏾♀ I comment out the line for installing the package from the repo and nixos-install allows me to continue the installation; and I can install the package when I'm on an existing NixOS system.

Yeah, I've had such problems with nixos-install before. Not sure what's up with it.

I am also having this issue using wine-ge. I tested it replacing wine-ge with an arbitrary package (modrinth-app) and the problem does not seem to occur then.
Since @NovaViper is reporting this problem with wine-discord-ipc-bridge(according to the config they linked), could it somehow be an issue with the wine-related packages?

Could be, yes.

I don't know what the exact error was, though there are various cases with nixos-install --flake, most of them related to either /mnt/nix/store/… leaking into the drvs build sandbox, or the build sandbox trying to access a path thats not in the target store, but in the store of the "host" system.
I have not been able to produce minimal examples, and do not know what the conditions are for this to hapen. Its just observations over the last years(?), mostly second hand.
All of these were "fixed" (better: worked around) by just generating a simple config, installing that, and using nixos-rebuild boot --flake and another reboot to apply the actual configuration.
I am not aware of any tracking issue at nixos/nix nor nixos/nixpkgs.


Staff submissions for students should not be marked late by autograder

Additionally, there should be an option to get the 1-day early EC point.
The simple solution is to have an option to set the created time (with nice defaults) when staff members submit.

Instead of playing with the submission time, I think a better solution is a separate column that tracks whether a backup is "late". Then the submission time is still preserved. It's a little more involved to implement and would required autograder changes though

Was it you that suggested having Ok just kept track of late penalties? That might be interesting.
re your comment: We technically have the is_late field already - we would just have to implement the custom assignment extensions table. On a staff submission, an extension could be automatically granted.

Do we need extensions? I was thinking we just have staff submissions not mark it as late (or you could manually toggle it for a student submission) so the autograder treats it normally.

I don't think OK should keep track of the penalties per se, but rather that the autograder uses that information instead of the submission time to apply the penalty.

Okay, I think we've settled on a design:

[ ] Backups have another time field for their true submission time. It can be NULL, which means we use the "created" time instead.
[ ] When a staff member submits online, they should have the option to set this. Common options:

Now (default; sets submission time to NULL)
At deadline (just on time)
One day early (for EC point)
Custom time

[ ] We should be able to modify this time, using the options above. This can be done in the grading view (https://okpy.org/admin/grading/xxxxxx)
[ ] The autograder should pass this info to the scoring script.

:+1: I think this is good. I can change the autograder once the PR is merged.


Automatically Update Input on Lose Focus

The user is allowed to type on the input and a country is automatically selected from the left.
The form submit however takes into consideration the value on the input field. This gives wrong submission since for example:

A user types in "ger"
The Germany flag is automatically selected on the dropdown
The term "ger" is saved on the database

There are of course many alternatives to overcome this problem but it would be brilliant to have the input filled with the correct name of the country once the user leaves that input.

If you have a proposed implementation for this feature, I'd be happy to see a pull request.

The recent pull request has resolved this issue. Thanks to @ahartz1 for providing the fix.


Flootty allows remote users to send EOF

When viewing another user's terminal I am able to send EOF(ctrl-d) that causes the remote session to end. It also fails to exit flootty on my end and leave the terminal hanging.

Alright, flootty 3.1.3 tagged and uploaded. Using flootty --create --unsafe will let others send ctrl+d.


Raspberry Pi 4 download link broken

This link on the balenaOS download page is currently returning 500.

Hi, how did you get that link?
Starting with this version, .prod and .dev images have been unified. So your link would be something like this now: https://api.balena-cloud.com/download?deviceType=raspberrypi4-64&version=2.88.5+rev1&fileType=.zip&d_id=57bb8927-2111-47d0-b8e4-8bf1fa298946R

It's just the link listed at https://www.balena.io/os/

@floion do you have any documentation about that change? I can't find anything, and it's confusing to download a dev image that isn't marked as such (but seems to still behave as such).

@wyuenho @airdrummingfool it's been fixed now as you probably saw.

Can this be closed now?


fixed toolbar placement when foundation is installed

https://github.com/divio/django-cms/issues/5101
before

after

👍

Changes Unknown when pulling 6c5da4b0d62b7db1a8807789be9f6b8321d0aa0d on genti94:bugfix/foundation-toolbar-login into ** on divio:release/3.2.x**.

Can you make sure it's updated with latest release/3.2.x and add a note in the changelog please?

ping

@vxsx checked with latest release/3.2.x updates and added to changelog

Coverage remained the same at 89.571% when pulling e9b9386ed96ea3a940d613a0f02a643831210dfe on genti94:bugfix/foundation-toolbar-login into 93ea0061a1f5833f4cd461f92dc2b8f31aeba52f on divio:release/3.2.x.


Adding Custom Components and Elements (like text, links, input fields...)

Hello guys,
Can you please provide more instructions for adding Custom Components and Elements (like text, links, input fields...) to Stories?
Or please, at least provide the code for your demo example, just so we can see how to add Custom Components and Elements like in your live demo?
Best regards! 😄

This is fixed in the version 0.9.2! Thank you very much! 😄


Use custom geography model

new data for scorecard_geography including categories and correct parents
after running migrations we can delete wazimap_geography

This depends on https://github.com/Code4SA/wazimap/pull/20 being merged and released.

Ok, wazimap changes have been merged and released.


Add function to fix unscaped chars

Some change was added to this PR:

Add better function to unescape chars and replace the old pv_str_unescape_to_ascii from utils/str.h
Change the strategy of how user-meta is unescaped, now the data is unescaped after parsing

Both changes help to fix a nasty bug I found if you create a variable with any name but with the value ooo\nooo (something with a \n in between) the device will freeze completely.

FYI, the problem that this is trying to solve is that if i put in a VAR="blah" in the user-meta, the " will be escaped on disk in user-meta folder.... e.g. VAR="blah" is what will be in the file.

looks good to me now. Please, test it on device


[5.1] Check if the primary key is overwritten, regardless of the value of "$incrementing"

Basically I had this problem, where I have a freshly created User, whos primary key is overwritten. If I wanted to log this user in, the last inserted ID that PDO gave me was not the ID that matches the user. This commit makes it so that the model checks if the primary key is set, before overwriting the primary key with what PDO thinks is the primary key.

Could you include a test please?

I am kind of inexperienced with testing a Database. Before I commit this code, is this something that you're looking for?
File: tests/Database/DatabaseEloquentModelTest.php
This method:
public function testPrimaryKeyNotOverwrittenIfManuallySet()
{
    $model = new EloquentTestPrimaryKeyPreserveStub();

    $tempId = 99999999; // ID that is not used elsewhere

    $model->id = $tempId;
    $model->save();

    $this->assertEquals($model->id, $tempId);
}

And this class
class EloquentTestPrimaryKeyPreserveStub extends Model
{
    protected $primaryKey = 'id';
}

So you have some users with incrementing keys and some that are manually set?

Well I came across this problem when overwritting the primary key of existing users.

Hmm, going to hold off because I can't imagine anything except an edge case where this wouldn't happen.


Support Route53 alias records

Please add support for alias records. You can see in the route53/responses.py that there is code reading upserted records for their AliasTarget and setting them to be the record set's ResourceRecords list:
https://github.com/spulec/moto/blob/f18259d49e5e66929a793ec8105d32ccfcc70d21/moto/route53/responses.py#L135-L137
I believe this is wrong; you should maintain the alias as an alias. I think normally you can't create an alias and also give it ResourceRecords (for example, the CloudFormation documentation says not to specify it if you specify an AliasTarget.)

Thanks for opening; I'm going to set this as a feature request.

I've just run into this issue when writing tests for an application that manipulates alias targets.
What I expect to see
{
    "AliasTarget": {
        "HostedZoneId": "FAKEZONE",
        "EvaluateTargetHealth": false,
        "DNSName": "other.example.com."
    },
    "Type": "A",
    "Name": "test.example.com."
}

and what moto is responding with:
{
    'Name': 'test.example.com',
    'Type': 'A',
    'ResourceRecords': [
        {
            'Value': 'other.example.com.'
        }
    ]
}

This has meant that part of my code can't be tested using moto.
I can open an PR to try to fix this, if that would be the best route.

@elliottmb Sure open up a PR and I'll review it.

As far as I can tell this was fixed by #2082, so I'll close this. Please let us know if there's still anything wrong/outstanding though.


IFrame Option for Lightbox Links

For #1564. The existing code is pretty buggy. Adding links works but editing does not work at all. I'll look into fixing that later today.
Should I have this auto select the iframe option if a JSONP request would be needed?

Going to try to actually finish this over the weekend.

Cool!
On Fri, Jan 23, 2015 at 10:54 AM, Christopher Hougard <
<EMAIL_ADDRESS>wrote:

Going to try to actually finish this over the weekend.
—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5-5.7.0/pull/1573#issuecomment-71244433
.

This is resolved in feature/redactor-10.


Finnish museum pull_data exceeds timeout

Description

The Finnish Museum DAG has been consistently timing out at the pull_data step. Recently its pull_data task was updated to have a 5 day execution_timeout, but the most recent DagRun had to be manually failed after the task was still running after 15 days.
We should investigate why the task was able to exceed this limit.
Reproduction

Observe the logs in Airflow for the run dated 2022-07-01.
You can also inspect the Task Instance Details and see that the execution_timeout is set to 5 days as expected.
Resolution

[ ] 🙋 I would be interested in resolving this bug.

It is worth taking a look at #621 first to see if that would be one way to tackle the large amounts of data we receive from this provider.

Bumping this to high as the provider DAG is currently disabled.

Investigating #621 now

@stacimc do you think this can be closed by #879 or do we need to run the DAG first to find out?

@AetherUnbound Good question! I think it's probably fine to close, since we won't really know until we hit an ingestion day with a lot of data, and we can always re-open. In local testing, I was able to fully ingest data for one such day without hitting the timeout, so we should be good!


Constant Timer strange behavior when used with variables or functions

Expected behavior
When the value of a Constant Timer references a variable or a function call the following must be preserved (as it happens for a numeric value):

Constant Timer runs after a PreProcessor
Constant Timer does NOT run as the 1st element in a JMX

I see a problem with current behavior:

Either the documentation should be clear about restriction to use anything else than numeric values and also implement a validation which rejects any other format value
Or fix the current issue(s)

Note: I think Constant Timer is used by other timers (Random ones) so they may be impacted as well.
Actual behavior
I've spotted strange behavior from Constant Timer when the value references a variable or a function call:

It runs as 1st element in a JMX
It is executed before a JSR223PreProcessor (probably before any PreProcessor)

This is not valid if the value is entirely a numeric constant; this is also not valid for a JSR223Timer.
What I can see:

Because Constant Timer's are executed as 1st elements from the tree when they are attached to the ThreadGroup then they throw NullPointerException because the variable is unknown (see JMX for tree structure)
On Constant Timer branch in case of Flow Control Action 2 the timer is executed before the JSR223PreProcessor (visible in log and sampler timestamps) => this is not as per documentation
Initially I've spotted the issue having Flow Control Action samplers and I thought it's an issue with them or in this combination; next I've used JSR223Sampler elements but outcome is the same.

jmeter.log
ConstantTimer-bug.zip
Steps to reproduce the problem
Attaching sample JMX; I do recommend to set log level to DEBUG to see sequence of execution better.
JMeter Version
5.6.2, 4.0
Java Version
OpenJDK 64-Bit v17.0.9
OS Version
Windows 11

javax.script.ScriptException: javax.script.ScriptException: java.lang.NullPointerException: Cannot invoke method toLong() on null object
	at org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:158) ~[groovy-jsr223-3.0.17.jar:3.0.17]
	at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:231) ~[java.scripting:?]
	at org.apache.jmeter.functions.Groovy.execute(Groovy.java:123) [ApacheJMeter_functions.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.engine.util.CompoundVariable.execute(CompoundVariable.java:139) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.engine.util.CompoundVariable.execute(CompoundVariable.java:114) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.testelement.property.FunctionProperty.getStringValue(FunctionProperty.java:104) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.testelement.property.AbstractProperty.getLongValue(AbstractProperty.java:128) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.testelement.AbstractTestElement.getPropertyAsLong(AbstractTestElement.java:393) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.timers.ConstantTimer.iterationStart(ConstantTimer.java:108) [ApacheJMeter_components.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.control.GenericController.fireIterationStart(GenericController.java:412) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]
	at org.apache.jmeter.control.GenericController.fireIterEvents(GenericController.java:404) [ApacheJMeter_core.jar:5.6.2-SNAPSHOT]

The root cause is that constant timer evaluates delay at the "iteration start": https://github.com/apache/jmeter/blob/9b250b64c00513cbcce81fe3f12746dcde8d9ddc/src/components/src/main/java/org/apache/jmeter/timers/ConstantTimer.java#L108
It is more-or-less the same as https://github.com/apache/jmeter/issues/6165#issuecomment-1860158198

The list of impacted classes is: ConstantTimer (and derived classes), CompareAssertion, CSVDataSet, RandomVariableConfig


security page is not support dark mode

When I switch ELK to dark mode, the open-distro security page is not work for the dark mode.

Dark mode is coming as the default in 2.10 and we have a few issues to close the gaps in the security plugin. Closing this one.


Some components doesn't react to density changes

0.4.0-build174
When we move a window to another screen with a different density (scale), or just change density in the system settings, some of the components doesn't change their size.
Known components:

FloatingActionButton
text inside Scaffold(topBar = { TopAppBar(title = { Text("text") } ) } )
vectorXmlResource (it changes size, but leaves "dirty" background)

How to reproduce:
./gradlew run1  -Pandroidx.compose.multiplatformEnabled=true
in androidx repo

Probably the root cause is common - all components were inside Scaffold. Maybe somewhere inside it we don't take into account density changing.

Also androidx.compose.ui.layout.Layout
Layout(
        content = {},
        modifier = modifier.onGloballyPositioned { childCoordinates ->
            val coordinates = childCoordinates.parentCoordinates!!
            val size = coordinates.size // the size does not change
            ...

FloatingActionButton

Seems fixed

text inside Scaffold(topBar = { TopAppBar(title = { Text("text") } ) } )

see https://issuetracker.google.com/issues/189170789

vectorXmlResource (it changes size, but leaves "dirty" background)

see https://github.com/JetBrains/compose-jb/issues/677

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


[INTEGRATION][AIRFLOW] Deprecate OpenLineage's support for Airflow v1.x

Since majority of the features are aimed to be used by Airflow v2.x, I would like to proceed with the process of DEPRECATING OpenLineage support for Airflow v1.x.

According to https://docs.astronomer.io/software/ac-support-policy#astronomer-certified-lifecycle-schedule, the EOL for Airflow 1.x is scheduled to be September 30, 2022. Therefore, I'd like to have a discussion here on whether we should deprecate OpnenLineage's support sooner or wait until then.

According to https://docs.astronomer.io/software/ac-support-policy#astronomer-certified-lifecycle-schedule, the EOL for Airflow 1.x is scheduled to be September 30, 2022. Therefore, I'd like to have a discussion here on whether we should deprecate OpnenLineage's support sooner or wait until then.

Adding warning message in logs to output WARNING type of 'Deprecation' may be needed, with tentative dates.

The decision was made that EOL for apache airflow support for 1.x will coincide with the airflow's EOL support for airflow v1.x.


Fix domain beans

Make sure all domain beans override equals and hashCode methods, and the calculation is up-to-date.

Passed Java integration test on Jenkins: http://wls-jenkins.us.oracle.com/job/weblogic-kubernetes-operator-javatest/286/.


Can add Azure tags to RKE1 node template

https://github.com/rancher/dashboard/issues/7164
This PR adds the "Azure Tags" button for RKE1 Azure node templates:

I'm reverting this PR because the Azure features were taken out of the next release


IntrSegment2Segment2 precison problem

Hello,
I have a problem while calculating the intersection of 2 "Segment2<double>"
i know it's a precision problem, and maybe the answer is "don't use the double version" ... but i still want to explain:
(they make a "T" shape like this:)
segment0 = (100, 1900) , (900,1900)
segment1 = (550, 601) ,<PHONE_NUMBER>0000034,1900)
as you can see, i have a small precision error on the "x1" coordinate of segment1
when i call the Result() function in IntrSegment2Segment2.h (line 215), the result is "intersect = false" (line 244), probably because of the GetCenteredForm() before...
I understand that the precison of the "double" is difficult to manage, but i though there was a "tolerance range" somewhere in GeometricTools (?) maybe i'm wrong...
edit : the "tolerance" parameter is "epsilon", used in Arc2.h ... maybe we should use it in Segment2 too... what do you think?
thank you
Johan

Adding "epsilon" in the algorithms is a rabbit hole I choose not to go down. Infrequently, there might be a need and I use an epsilon, but not as a general solution to dealing with floating-point error. Is the epsilon relative or absolute? How small (or large) must it be? If the epsilon is absolute, the magnitude of epsilon depends on the input data, so the user must decide what epsilon to choose based on an understanding of the characteristics of the input.
Regarding your example, my choice of GetCenteredForm is unfortunate. I tried to formulate the segments in the manner of an oriented bounding box (center+direction+extent), but yes, the rounding errors can be a problem. I am eliminating the GetCenteredForm in GTL. For code that is not time critical (for example, not intended for real-time applications and not used in a very large number of queries), I prefer the rational number approach. If you use BSRational as the rational type, you get "intersect = true". However, you can use the alternative member function "Exact". For your example, you get "intersect = true".
    using Rational = BSRational<UIntegerAP32>;

    Segment2<double> segment0{}, segment1{};
    segment0.p[0] = { 100.0, 1900.0 };
    segment0.p[1] = { 900.0, 1900.0 };
    segment1.p[0] = { 550.0, 601.0 };
    segment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
    FIQuery<double, Segment2<double>, Segment2<double>> query{};
    auto result = query(segment0, segment1);
    // result.intersect = false
    // result.numIntersections = 0
    // result.segment0Parameter = { 0.0, 0.0 }
    // result.segment1Parameter = { 0.0, 0.0 }
    // result.point[0] = { 0.0, 0.0 }
    // result.point[1] = { 0.0, 0.0 }

    result = query.Exact(segment0, segment1);
    // result.intersect = true
    // result.numIntersections = 1
    // result.segment0Parameter = { 0.56250000000000044, 0.56250000000000044 }
    // result.segment1Parameter = { 1.0, 1.0 }
    // result.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
    // result.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

    Segment2<Rational> rsegment0{}, rsegment1{};
    rsegment0.p[0] = { 100.0, 1900.0 };
    rsegment0.p[1] = { 900.0, 1900.0 };
    rsegment1.p[0] = { 550.0, 601.0 };
    rsegment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
    FIQuery<Rational, Segment2<Rational>, Segment2<Rational>> rquery{};
    auto rresult = rquery(rsegment0, rsegment1);

    FIQuery<double, Segment2<double>, Segment2<double>>::Result convert{};
    convert.intersect = rresult.intersect;
    convert.numIntersections = rresult.numIntersections;
    convert.segment0Parameter[0] = rresult.segment0Parameter[0];
    convert.segment0Parameter[1] = rresult.segment0Parameter[1];
    convert.segment1Parameter[0] = rresult.segment1Parameter[0];
    convert.segment1Parameter[1] = rresult.segment1Parameter[1];
    convert.point[0][0] = rresult.point[0][0];
    convert.point[0][1] = rresult.point[0][1];
    convert.point[1][0] = rresult.point[1][0];
    convert.point[1][1] = rresult.point[1][1];
    // convert.intersect = true
    // convert.numIntersections = 1
    // convert.segment0Parameter = { 50.000000000000341, 50.000000000000341 }
    // convert.segment1Parameter = {<PHONE_NUMBER>0000000,<PHONE_NUMBER>0000000 }
    // convert.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
    // convert.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

Once again, thank you for your fast and complete answer.
I didn't know there was a "exact()" function! I will test it tomorrow
morning! 👍
And i agree with you about the "rabbit hole"...
Thank you!
Johan
Le mar. 26 mars 2024 à 18:07, David Eberly @.***> a
écrit :

Adding "epsilon" in the algorithms is a rabbit hole I choose not to go
down. Infrequently, there might be a need and I use an epsilon, but not as
a general solution to dealing with floating-point error. Is the epsilon
relative or absolute? How small (or large) must it be? If the epsilon is
absolute, the magnitude of epsilon depends on the input data, so the user
must decide what epsilon to choose based on an understanding of the
characteristics of the input.
Regarding your example, my choice of GetCenteredForm is unfortunate. I
tried to formulate the segments in the manner of an oriented bounding box
(center+direction+extent), but yes, the rounding errors can be a problem. I
am eliminating the GetCenteredForm in GTL. For code that is not time
critical (for example, not intended for real-time applications and not used
in a very large number of queries), I prefer the rational number approach.
If you use BSRational as the rational type, you get "intersect = true".
However, you can use the alternative member function "Exact". For your
example, you get "intersect = true".
using Rational = BSRational<UIntegerAP32>;

Segment2<double> segment0{}, segment1{};
segment0.p[0] = { 100.0, 1900.0 };
segment0.p[1] = { 900.0, 1900.0 };
segment1.p[0] = { 550.0, 601.0 };
segment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
FIQuery<double, Segment2<double>, Segment2<double>> query{};
auto result = query(segment0, segment1);
// result.intersect = false
// result.numIntersections = 0
// result.segment0Parameter = { 0.0, 0.0 }
// result.segment1Parameter = { 0.0, 0.0 }
// result.point[0] = { 0.0, 0.0 }
// result.point[1] = { 0.0, 0.0 }

result = query.Exact(segment0, segment1);
// result.intersect = true
// result.numIntersections = 1
// result.segment0Parameter = { 0.56250000000000044, 0.56250000000000044 }
// result.segment1Parameter = { 1.0, 1.0 }
// result.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
// result.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

Segment2<Rational> rsegment0{}, rsegment1{};
rsegment0.p[0] = { 100.0, 1900.0 };
rsegment0.p[1] = { 900.0, 1900.0 };
rsegment1.p[0] = { 550.0, 601.0 };
rsegment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
FIQuery<Rational, Segment2<Rational>, Segment2<Rational>> rquery{};
auto rresult = rquery(rsegment0, rsegment1);

FIQuery<double, Segment2<double>, Segment2<double>>::Result convert{};
convert.intersect = rresult.intersect;
convert.numIntersections = rresult.numIntersections;
convert.segment0Parameter[0] = rresult.segment0Parameter[0];
convert.segment0Parameter[1] = rresult.segment0Parameter[1];
convert.segment1Parameter[0] = rresult.segment1Parameter[0];
convert.segment1Parameter[1] = rresult.segment1Parameter[1];
convert.point[0][0] = rresult.point[0][0];
convert.point[0][1] = rresult.point[0][1];
convert.point[1][0] = rresult.point[1][0];
convert.point[1][1] = rresult.point[1][1];
// convert.intersect = true
// convert.numIntersections = 1
// convert.segment0Parameter = { 50.000000000000341, 50.000000000000341 }
// convert.segment1Parameter = {<PHONE_NUMBER>0000000,<PHONE_NUMBER>0000000 }
// convert.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
// convert.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

—
Reply to this email directly, view it on GitHub
https://github.com/davideberly/GeometricTools/issues/88#issuecomment-2021006170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3BAQOHOWB4SDYTNTSE53DY2GTMVAVCNFSM6AAAAABFJHRZS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGAYDMMJXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I did some tests...
The exact() function does work well for yesterday's example...
But doesn't work if the values are different.
Anyway, i will not use the segment2segment2 intersection, I will use the
line2line2 intersection then test if the point is ok.
I understand that the double precision is always a problem...
Johan
Le mar. 26 mars 2024 à 18:07, David Eberly @.***> a
écrit :

Adding "epsilon" in the algorithms is a rabbit hole I choose not to go
down. Infrequently, there might be a need and I use an epsilon, but not as
a general solution to dealing with floating-point error. Is the epsilon
relative or absolute? How small (or large) must it be? If the epsilon is
absolute, the magnitude of epsilon depends on the input data, so the user
must decide what epsilon to choose based on an understanding of the
characteristics of the input.
Regarding your example, my choice of GetCenteredForm is unfortunate. I
tried to formulate the segments in the manner of an oriented bounding box
(center+direction+extent), but yes, the rounding errors can be a problem. I
am eliminating the GetCenteredForm in GTL. For code that is not time
critical (for example, not intended for real-time applications and not used
in a very large number of queries), I prefer the rational number approach.
If you use BSRational as the rational type, you get "intersect = true".
However, you can use the alternative member function "Exact". For your
example, you get "intersect = true".
using Rational = BSRational<UIntegerAP32>;

Segment2<double> segment0{}, segment1{};
segment0.p[0] = { 100.0, 1900.0 };
segment0.p[1] = { 900.0, 1900.0 };
segment1.p[0] = { 550.0, 601.0 };
segment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
FIQuery<double, Segment2<double>, Segment2<double>> query{};
auto result = query(segment0, segment1);
// result.intersect = false
// result.numIntersections = 0
// result.segment0Parameter = { 0.0, 0.0 }
// result.segment1Parameter = { 0.0, 0.0 }
// result.point[0] = { 0.0, 0.0 }
// result.point[1] = { 0.0, 0.0 }

result = query.Exact(segment0, segment1);
// result.intersect = true
// result.numIntersections = 1
// result.segment0Parameter = { 0.56250000000000044, 0.56250000000000044 }
// result.segment1Parameter = { 1.0, 1.0 }
// result.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
// result.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

Segment2<Rational> rsegment0{}, rsegment1{};
rsegment0.p[0] = { 100.0, 1900.0 };
rsegment0.p[1] = { 900.0, 1900.0 };
rsegment1.p[0] = { 550.0, 601.0 };
rsegment1.p[1] = {<PHONE_NUMBER>0000034, 1900.0 };
FIQuery<Rational, Segment2<Rational>, Segment2<Rational>> rquery{};
auto rresult = rquery(rsegment0, rsegment1);

FIQuery<double, Segment2<double>, Segment2<double>>::Result convert{};
convert.intersect = rresult.intersect;
convert.numIntersections = rresult.numIntersections;
convert.segment0Parameter[0] = rresult.segment0Parameter[0];
convert.segment0Parameter[1] = rresult.segment0Parameter[1];
convert.segment1Parameter[0] = rresult.segment1Parameter[0];
convert.segment1Parameter[1] = rresult.segment1Parameter[1];
convert.point[0][0] = rresult.point[0][0];
convert.point[0][1] = rresult.point[0][1];
convert.point[1][0] = rresult.point[1][0];
convert.point[1][1] = rresult.point[1][1];
// convert.intersect = true
// convert.numIntersections = 1
// convert.segment0Parameter = { 50.000000000000341, 50.000000000000341 }
// convert.segment1Parameter = {<PHONE_NUMBER>0000000,<PHONE_NUMBER>0000000 }
// convert.point[0] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }
// convert.point[1] = {<PHONE_NUMBER>0000034, 1900.0000000000000 }

—
Reply to this email directly, view it on GitHub
https://github.com/davideberly/GeometricTools/issues/88#issuecomment-2021006170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3BAQOHOWB4SDYTNTSE53DY2GTMVAVCNFSM6AAAAABFJHRZS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGAYDMMJXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

The Exact function produces the theoretically correct values when using a rational type. Is the rational performance an issue for you?
For line2-line2 intersection, what do you expect the results to be when the lines are "nearly" parallel. I can imagine constructing an example for which the point of intersection has NaN or infinities because the theoretically correct value cannot be represented with the precision of the floating-point type you use. But perhaps for your data, this approach will work well.
You might try DistSegmentSegment.h instead to compute the distance between two line segments. When the segments theoretically intersect (distance = 0), rounding errors can lead to distance being a positive number that is nearly zero. You can use an epsilon test in your application code. Note that DistSegmentSegment has an operator() query that produces the theoretically correct squared distance when using Rational. It also has ComputeRobust which uses a conjugate gradient approach to try to be more robust.

Thank you...
Maybe you are right and i could convert my segment2 from double to
rationals just for the time of the intersection call.
I'm afraid to start big scale changes in the whole app...
I will save all your advices...
Thank you.
Johan
Le mer. 27 mars 2024 à 23:11, David Eberly @.***> a
écrit :

The Exact function produces the theoretically correct values when using a
rational type. Is the rational performance an issue for you?
For line2-line2 intersection, what do you expect the results to be when
the lines are "nearly" parallel. I can imagine constructing an example for
which the point of intersection has NaN or infinities because the
theoretically correct value cannot be represented with the precision of the
floating-point type you use. But perhaps for your data, this approach will
work well.
You might try DistSegmentSegment.h instead to compute the distance between
two line segments. When the segments theoretically intersect (distance =
0), rounding errors can lead to distance being a positive number that is
nearly zero. You can use an epsilon test in your application code. Note
that DistSegmentSegment has an operator() query that produces the
theoretically correct squared distance when using Rational. It also has
ComputeRobust which uses a conjugate gradient approach to try to be more
robust.
—
Reply to this email directly, view it on GitHub
https://github.com/davideberly/GeometricTools/issues/88#issuecomment-2024076955,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3BAQLRER4XROWSCY2NYOLY2M7YHAVCNFSM6AAAAABFJHRZS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGA3TMOJVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

If you need to re-open this, no worries.


Remove the inaccurate description

The escape is pending due to the cel nature: https://github.com/kubernetes/kubernetes/pull/121299
Remove the inaccurate description before the PR merged.

/sig api-machinery

/lgtm
We can always take this section back once we have a properly escaping implementation for ValidatingAdmissionPolicy.

/assign @reylejano if you have time? Thank you

/assign @reylejano

Thank you @cici37
/approve


Update old screenshots.

Most of the screenshots may no longer be relevant or correct. Need to review with UI team and update as needed.

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

ID: c4ded2ce-d8c3-7118-bec9-865f6225dbe0
Version Independent ID: a4089752-177c-866c-7237-3ac02c7750d9
Content: Dependency Tracking in Azure Application Insights
Content Source: articles/azure-monitor/app/asp-net-dependencies.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

You are correct, every single one of those is the old UI experience. I can get those updated, thank you!

@mrbullwinkle I removed screenshots about AppMap etc. and linked to our up-to-data AppMap docs.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/78085
Once the above PR is merged and live, please try to update the remaining screenshots.

@cijothomas Thank you for bringing this to our attention!

@cijothomas The screenshots have been updated.  Thank you again for bringing this to our attention.  Closing.


adding a package json

Hi!
I´am currently working on a Bootstrap 4 + WordPress theme framework (https://github.com/holger1411/understrap) and tried to test your scrollpos script.
To implement it as dependency (I dropped bower in favor for npm) I have to create a package,json file.
Maybe you are interested in use it and publishing your project on npm, too?

Hi!
Good stuff - thank you very much for this! npm was on my list for a long time, never found the time to dig into it myself...
Just out of curiosity: what about the "ignore" pattern from bower.json? Not required for npm?
Thanks for your help - Cheers!

Hi!
By default npm uses your .gitignore file.
I don´t find one so I add a more specific .npmignore (it just works for npm not for git) file to this pull request.

Awesome - thanks much!

:thumbsup:


Preferences don't show the dialect directory :(

Hello,
I followed the Rivals guide to get started for the steam workshop, so one step is to extract the rivals dialect to the folder, however when I open my preferences there is no such part at the bottom as you describe it in your wiki
please respond ASAP
Sincerely,
Puuuul

You need to install the beta version

Thanks a lot!


Update bitbake generator to not use symlinks

As implemented in ebuild generator in #51

Fixed in #79.


Migrate databricks/notebooks/rapids_intro.ipynb to deployment docs

See https://github.com/rapidsai/cloud-ml-examples/issues/203#issuecomment-1410349915 for detailed migration instructions.
### Tasks
- [ ] Decide if notebook should be migrated and add "migrate: X" label (if no also close this issue)
- [ ] Test if notebook works
- [ ] Fix up anything that needs changing
- [ ] Ensure notebook has good title, description and metadata tags in the first cell
- [ ] Replace deployment instructions with links to docs pages
- [ ] Copy notebook into a new folder into deployment docs examples
- [ ] Copy any supporting files to the folder
- [ ] Add notebook to examples toctree
- [ ] Make PR to deployment docs repo

This notebook doesn't really have anything to do with deployment or Databricks. I don't think we should migrate it.


Block list should be applied server-wide to Hachyderm

The current server-wide block list on hachyderm.io is way too short to be of any use. Personally, I’ve had to kill my account (and likely will never come back to Mastodon) because of swarms of right wing extremists not being filtered out by default using #fediblock as a way to find targets for harassment.

which block list are you referring to?
I ask because I personally blocked one of the domains in your screenshot some time ago.
the list of suspensions is public: https://hachyderm.io/about/more
I think we need to upgrade to 4.0.2 before we can start sharing suspended domains (correct me if I'm wrong) and that is happening soon.
I agree completely that we need to start sharing block lists to keep our community safe.

The block list that’s in this repository that seems to be much longer

And this is less about shared block lists via Mastodon 4.0 and more about… expanding the block list on hachyderm altogether

I'm very sorry you had to experience that @cparedes!
Thanks for reporting it. On my end I never encountered such offensive behavior and I only rarely see problematic content at all. So it is valuable to get the feedback when it happens.
(FYI: I'm not a mod on hachyderm.)

And this is less about shared block lists via Mastodon 4.0 and more about… expanding the block list on hachyderm altogether

understood. however to expand it fully is a very manually intensive task until we get the API for 4.0.
i will start working through some of these manually, though.

i have completed a manual pass and our defederation list is quite a bit longer.
when we update to 4.0 we will have more options for sharing blocklists between instances and applying them automatically.
i'm really sorry you had such a bad experience, @cparedes, and i really appreciate you pushing us to do better.

It seems that hachyderm.io has been updated to 4.0.3 but its list still differs significantly from this repository. Is it planned to replace hachyderm.io's blocklist with the one in this repository (and continue to keep it synced) and if so, is there any open issue for tracking it (since this one has been closed)?


No possibility currently to specify grant-type ciba in OAS

Camara APIs  use the grant type CIBA https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.10.1 and currently have no way to specify it in our OAS files. Could the specification be extended to support the CIBA grant type?

Are you referring to the type field in the security scheme object (https://spec.openapis.org/oas/v3.1.0#security-scheme-object)?
I wonder if this field should not be limited by an enum -- the existing supported schemes can have further support in the spec, but allowing any string here would allow for users to make extensions in their own implementations. Or would that potentially break forward compatibility?

@karenetheridge  , Regarding the support of ciba and introducing a new type , i think adding a new one would be not really a good idea,
CIBA is more a flavour of OIDC , that can be supported or not. i wonder if we should not add a flag  (this is the same for the PKCE support for instance in Oauth2 )
the issue would be that it create a kind of depedency between the OAS spec and the security spec , as the list of flavour can grow not in synch with OAS
i wonder if we should not add an field flavours , that is an array of string , so that we can push Ciba and more
if we want to be normative , it could provide the URI of the flavour in this array
CIBA is one of them but looking on FAPI 2 , the flavours keep growing  https://oauth.net/fapi/

@LasneF, CIBA is a grant type just like authorization_code. It is not an OIDC flavour.

@karenetheridge in fact the point you mentionned is valid , and raise questions about how the security scheme in OAS is describe.
meaning ciba is not just a grant type but an entire flow , should it be defines inside Oauth2 ?, it could as the other flow
but considering that ciba grant type  urn:openid:params:grant-type:ciba
ciba is part of OIDC as an optional feature (this is what i was calling flavour) , it could be considered that it will be describe via the OIDC url in the configuration endpoint in the grant_type_supported field
those are kind of in the middle
notice that device code flow could be added too  (here as part of Oauth)
to me you are raising the capability of discovering the feature supported by a security scheme and the limit OIDC / Oauth2
OIDC has a nice mechanism for it via openid-configuration
that is the best for OAS as it is decoupling it from the OIDC spec , but in mean time relying on a URL could be considered as too dynamic . and does not provide quickly a few of what is supported or not and even more precisely for this particular endpoint
it make it quite challenging for OAS to follow
the request is very valid you want to advertise CIBA flow is supported
the answer adding it in Oauth2 works  even if Ciba is  more an OIDC defined artefact
then for OAS it s a challenge knowing than on OIDC there are plenty of flavors , around the JWT content , the flows supported ,
and to me even the discovery URL is not 100 % satisfying

@shilpa-padgaonkar  - TODO: create a new PR describing the grant type.


Underlying HTTP client is closed after first request, causing subsequent requests to fail

Using the Python Graph SDK, I found this issue. The first request sent through the GraphServiceClient succeeds, but subsequent requests throw an exception:
Traceback (most recent call last):
  File "/home/jasonjoh/repos/msgraph-training-python/demo/graphtutorial/repro.py", line 17, in <module>
    users2 = asyncio.run(client.users().get())
  File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/home/jasonjoh/.local/lib/python3.10/site-packages/msgraph/generated/users/users_request_builder.py", line 129, in get
    return await self.request_adapter.send_async(request_info, user_collection_response.UserCollectionResponse, response_handler, error_mapping)
  File "/home/jasonjoh/.local/lib/python3.10/site-packages/kiota_http/httpx_request_adapter.py", line 114, in send_async
    response = await self.get_http_response_message(request_info)
  File "/home/jasonjoh/.local/lib/python3.10/site-packages/kiota_http/httpx_request_adapter.py", line 329, in get_http_response_message
    resp = await self._http_client.send(request)
  File "/home/jasonjoh/.local/lib/python3.10/site-packages/httpx/_client.py", line 1609, in send
    raise RuntimeError("Cannot send a request, as the client has been closed.")
RuntimeError: Cannot send a request, as the client has been closed.

This seems to be caused by the following line:
https://github.com/microsoft/kiota-http-python/blob/d57aaedc0924cbabc50ca85cd69336510c5058ac/kiota_http/httpx_request_adapter.py#L330
This script can reproduce the problem:
import asyncio
from azure.identity.aio import ClientSecretCredential
from kiota_authentication_azure.azure_identity_authentication_provider import AzureIdentityAuthenticationProvider
from msgraph import GraphRequestAdapter, GraphServiceClient

credential = ClientSecretCredential(
    'TENANT_ID',
    'CLIENT_ID',
    'CLIENT_SECRET')
auth_provider = AzureIdentityAuthenticationProvider(credential)
adapter = GraphRequestAdapter(auth_provider)
client = GraphServiceClient(adapter)

users = asyncio.run(client.users().get())
print('got users')

users2 = asyncio.run(client.users().get())
print('got users again')

@jasonjoh thanks for reporting this.
@samwelkanda I think you meant to close the response, not the client there, could you take a look at it please?

Thank you for reporting this issue @jason.
On a side note, to make the most of the async client, if you have multiple calls to the API, it's better to define a function that will execute them asynchronously, reusing the existing client and speeding up your application.
async def get_users():
        users1 = await client.users().get()
        users2 = await client.users().get()
        print(users1)
        print(users2)
asyncio.run(get_users())

The above wi


chore: organize scripts

This PR adds a file called scripts.ts that contains the two scripts we use: contractCallScript and returnZeroScript.
I know this conflicts with #170 but it should be a an easy one. If not we can merge #170 and I can rebase this.

This is great! Should we let https://github.com/FuelLabs/fuels-ts/pull/170 go in first because it came first and solves a blocker @luizstacio was having?

I also have some ongoing changes on this file to support function without return.

@AlicanC It's for you to merge and squash, I will rebase my ongoing changes with this PR, after merge.

@luizstacio rebased!

This was included in #178


Git merge conflict?

I just tried to do the usual git fetch upstream && git merge upstream/develop to re-sync my fork but I get a merge conflict. I work on branches in my fork and haven't committed directly to the develop branch. Did someone force push a change or is my git-fu weak? If the latter (which is likely), how do I get my fork back in sync without adding a spurious commit to the develop branch?
$ git fetch upstream
$ git merge upstream/develop
Auto-merging docs/reference/configuration.rst
Auto-merging CHANGELOG.txt
CONFLICT (content): Merge conflict in CHANGELOG.txt
Automatic merge failed; fix conflicts and then commit the result.

$ git diff
diff --cc CHANGELOG.txt
index 6ef59ab,1efe182..0000000
--- a/CHANGELOG.txt
+++ b/CHANGELOG.txt
@@@ -20,6 -20,14 +20,17 @@@
  * Fixed typo in ``AdvancedSettingsForm`` error messages.
  * Fixed long standing bug that prevented apphook endspoints from being
    CSRF exempt.
++<<<<<<< HEAD
++=======
+ * Changed default value for ``CMS_INTERNAL_IPS``.
+ * Fixed an issue that prevented non superusers from copying all plugins
+   in a placeholder.
+ * Fixed an issue where plugin permissions where not checked when clearing
+   a placeholder.
+ * Fixed an issue where plugin permissions where not checked when deleting
+   a page or page translation.
+ * Added support for tiered ``CMS_PLACEHOLDER_CONF``.
++>>>>>>> upstream/develop

@jsma
Hi there,
We force pushed the develop branch to be in sync with the 3.3.x branch.
All prs should target the release/3.3.x branch unless they've been approved for 3.4.x (develop).

Ah, so I shouldn't even be sync-ing the develop branch anymore then? I'll have to unlearn that old habit.


Consider switching to Quasar Framework

Vuetify is a great UI library for Vue, but the only version supporting Vue 3 is currently in Beta and many components are still missing/buggy (which is expected from a beta, it shouldn't have been used in the first place, so no shame on their side).
Quasar on the other hand supports Vue 3 and has more components than Vuetify. IMHO, they also look better as they are a little less stylized but still adhere to Material Design.

We use the following components from Vuetify:

[ ] VApp
[ ] VNavigationDrawer
[ ] VTextField
[ ] VList & VListItem
[ ] VListGroup
[ ] VRow & VCol
[ ] VAppBar & VAppBarNavIcon
[ ] VMain
[ ] VBreadcrumbs
[ ] VContainer
[ ] VProgressCircular
[ ] VAlert
[ ] VCard
[ ] VBtn

Each of these need to be replaced with a corresponding Quasar component.
Apart from that, we also use the following functionalities provided by Vuetify:

[ ] Custom handling for navigation drawer state
[ ] Custom global theme colors

These also must be replaced or provided by Quasar.

Ionic might also be an alternative which doesn't implement the Material Design language.


Suggestion: improve the presentation of the API documentation

I have a hunch you guys already know this is important, but I can't see any other issues to this effect.
Is it just me, or is the API documentation user experience pretty awful right now? I posted this issue just now in response to trying to find out what the API has to offer with respect to some ideas I have. Key questions in mind are "is it directly capable of X" and "can I get a sense of how much additional work would be required to extend certain base features to support my ideas?"
Problems:

It's a giant scrolling page; clumping everything together makes it hard to differentiate between different sections and judge how they relate to each other.
There is nowhere to get a quick overview of everything the API has to offer.
There is no obvious table of contents that I can use to quickly jump to the section I need.
There is no clear document hierarchy.
I can't quickly search for symbols and drill down to find what I need (other than via CTRL+F)
It's not very readable. The typography makes everything look kind of "same-ish", so it's hard to scroll through and scan for what I need. The font sizes don't make a lot of sense with respect to representing importance of items and their relationship to the document hierarchy.
Weird line spacing- way more space between property list items than headings and so forth. Again, scannability is an issue.

Would love to see this presented in a way that encourages better absorption and exploration of what the API has to offer, and I'm sure doing so would promote a faster-growing extension ecosystem.

As an aside; "Complex Commands API" - The intro text is completely unhelpful: "They are called complex commands because they require parameters and often return a value" - this is a description of almost every function in existence.

Thanks for the thoughtful feedback. The API doc is currently generated from https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts, and it could get some more polish to improve developer experience.
But I guess this should be moved to vscode-docs @waderyan .

This issue was moved to Microsoft/vscode-docs#939


weight synchronization between player and main models in DreamerV1

Hello,
I'm studying the DreamerV1 implementation in your repository, and I have a question about how the weights are synchronized between the player and the main models (world_model, actor).
In the build_agent function, I see that the player is initialized with deep copies of the main model components:
    player = PlayerDV1(
        copy.deepcopy(world_model.encoder),
        copy.deepcopy(world_model.rssm.recurrent_model),
        copy.deepcopy(world_model.rssm.representation_model),
        copy.deepcopy(actor),
        actions_dim,
        cfg.env.num_envs,
        cfg.algo.world_model.stochastic_size,
        cfg.algo.world_model.recurrent_model.recurrent_state_size,
        fabric_player.device,
    )

Then, the weights are copied from the main models to the player:
    for agent_p, p in zip(world_model.encoder.parameters(), player.encoder.parameters()):
        p.data = agent_p.data
    for agent_p, p in zip(world_model.rssm.recurrent_model.parameters(), player.recurrent_model.parameters()):
        p.data = agent_p.data
    for agent_p, p in zip(world_model.rssm.representation_model.parameters(), player.representation_model.parameters()):
        p.data = agent_p.data

If I understand correctly, the player is responsible for the environment interaction, so its weight must be same as the world model and actor along with their update. However, this appears to be a one-time copy rather than a continuous synchronization. I'm wondering: How are the player's weights kept in sync with the main models during training?
Thank you for your time!

Hi @Andy-Mielk,
thanks for your question. The weights of the player are the same of the weights in the world model. The agent_p.data is a tensor, so, every time you update the world model weights, the player will read the updated weights of the world model: they share the tensors of the weight, and they point to the same object.


React ref doesn't work with dynamically imported components

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When creating a callback reference to a dynamically imported component, the reference should resolve to the component as if it had been imported normally.
Current Behavior

The ref behaves strangely. The reference to the component doesn't seem to have any of the attributes or state of the component -- all undefined.
Steps to Reproduce (for bugs)
Here's a nice smallish example. Bring your own boilerplate components/page.js
pages/refs.js
import React, { Component } from 'react'
import dynamic from 'next/dynamic'
import Page from '../components/page'

const Child = dynamic(
  import('../components/child')
)

class Parent extends Component {

  onSubmit = () => {
    console.log(this.child.state.value)  // undefined
    console.log(this.child.getValue())  // throws
  }

  render() {
    return (

        <Child ref={ (child) => { this.child = child } } />
        <button onClick={ this.onSubmit }>Submit</button>

    )
  }
}

export default class extends Page {
  render() {
    return <Parent />
  }
}

components/child.js
import React, { Component } from 'react'

export default class extends Component {
  constructor(props) {
    super(props)
    this.state = {
      value: 23
    }
    this.getValue = () => String(this.state.value)
  }
  render() { return
{this.state.value}
 }
}

Context

I'm trying to create a wrapper around a wrapper around React-RTE. The first layer wrapper has a getValue() method one can use to extract the transformed value from React-RTE. The transformation is non-trivial and kind of expensive, so it makes sense to do it on-demand, and the component that should demand it is in the second-layer component. The first layer wrapper needs to be loaded dynamically (with SSR disabled).
Your Environment

Tech
Version

next
3.0.6

node
6.9.1

OS
macOS 10.12.6

browser
Chrome 60.0.3112.90 (Official Build) (64-bit)

The component imported is actually all instances of "DynamicComponent" for me, thus all refs are not working.

Dynamically imported Components are wrapped in a DynamicComponent. Since React does not allow forwarding ref maybe you could substitute ref for innerRef like styled-components[#102]

There's a new API coming in future React that allows to pass off ref.

Any hack for now?

Seriously need a hack

I use this to get ref
class Example extends React.Component {
  constructor() {
    this.state = {
      DynamicComponent: null,
    };
    this.refCom = React.createRef();
  }

  render() {
    const {DynamicComponent} = this.state;
    return DynamicComponent && <DynamicComponent ref={this.refCom}/>
  }

  componentDidMount() {
    import("my-dynamic-component")
      // if your component use export default, use val.default,
     // else use val[yourComponentName]
    .then(val => this.setState({DynamicComponent: val.default}));
  }
}


Issue titles are not very helpful

perhaps we could give the title of the issue in the comment title, not just the number?

The downside of that approach is If I search for the text in the
issue title I don't want search results for both the issue and all of its
comments to show up...
On Friday, February 13, 2015, David Greisen<EMAIL_ADDRESS>wrote:

perhaps we could give the title of the issue in the comment title, not
just the number?
—
Reply to this email directly or view it on GitHub
https://github.com/cfpb/github-wiki-search/issues/96.


Support basic L2 networking

With #279 there is a way of how Vms can be connected to the Kubernetes network.
Kubernetes however is handling pod as IP endpoints.
VMs however often have the freedom/requirement of living in the same ethernet, and not same IP network.
Thus VMs sometimes expect layer 2 connectivity.
This issue is about finding a solution - at best based compatible with #279 - to have basic mechanism to connect VMs to a lyaer 2 network.
Currently:

[ ] DP providing L2 networking to a pod
[ ] Glue to consume Net DPs

@fabiand do you feel that this (basic L2 networking) is complete and can be closed?

depends on https://github.com/kubevirt/kubevirt/issues/1067

Will this be solved with e.g. ovs-cni or should this stick around until DPs are used in the project for networking?


Permission denied with packer 1.5.0

Our CI-Runner updated to packer version 1.5.0 and the next packer build returned this error:
+ packer build dockerhost.json
Failed to initialize build 'amazon-ebs': error initializing post-processor 'amazon-ami-management': fork/exec /opt/packer: permission denied

We use this way to install packer and the post processor.
# Packer
RUN PACKER_VERSION="$(curl -fsSL https://releases.hashicorp.com/packer/ | grep -oPm 1 'packer_\K(\d\d?\.\d\d?\.\d\d?)(?=</a>$)')" && \
    wget -q -O /tmp/packer.zip https://releases.hashicorp.com/packer/${PACKER_VERSION}/packer_${PACKER_VERSION}_linux_amd64.zip && \
    unzip -q /tmp/packer.zip -d /opt/packer && \
    rm -rf /tmp/packer.zip
ENV PATH="/opt/packer:${PATH}"

# Packer AMI Management Post Processor
RUN PACKER_POST_PROCESSOR_AMAZON_AMI_MANAGEMENT_URL="$(curl -fsSL "https://api.github.com/repos/wata727/packer-post-processor-amazon-ami-management/releases/latest" | grep -o https://github.com.*linux_amd64.zip)" && \
    wget -q -O /tmp/packer_ami_post_processor_plugin.zip ${PACKER_POST_PROCESSOR_AMAZON_AMI_MANAGEMENT_URL} && \
    unzip -q /tmp/packer_ami_post_processor_plugin.zip -d /opt/packer && \
    rm -rf /tmp/packer_ami_post_processor_plugin.zip

Reverting back to packer 1.4.5 fixed the issue.

This issue seems related: https://github.com/hashicorp/packer/issues/8527


How to import WmsMapType from unpkg or jsdelivr CDN?

It's likely a trivial question, but no idea on the answer
How to import WmsMapType from unpkg or jsdelivr CDN?
I am trying as follows
import { WmsMapType } from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>But I am getting an error due to the dependencies
Uncaught (in promise) TypeError: Failed to resolve module specifier "query-string". Relative references must start with either "/", "./", or "../"
Is there anyway to achieve this?
Thanks in advance

Something like this should work.
<script src="https://unpkg.com/<EMAIL_ADDRESS><script>
  // Google Maps JS API must also be loaded
  new google.maps.plugins.ogc. WmsMapType(...)
</script>

Still getting a similar queryString error as follows
Uncaught ReferenceError: queryString is not defined     at index.min.js:1:13689
Any other way to avoid this problem?

I'll just switch to the built-in URL object now that support is better instead of query-string.

The new version which will be published in a couple minutes shouldn't have that dependency.


AWS pgadmin health check never reports healthy

When running pgadmin on AWS in the deploy system, the ECS task never reports healthy, even though the task is running successfully and pgadmin is available. This causes the pgadmin script to continue polling until manually interrupted to print access credentials.
Done when
The health check works correctly and the script does not need to be interrupted to print access credentials.
Background
ECS health check configured here: https://github.com/civiform/cloud-deploy-infra/blob/main/cloud/aws/modules/pgadmin/main.tf#L41
Script polls here: https://github.com/civiform/cloud-deploy-infra/blob/main/cloud/aws/bin/pgadmin.py#L88
pgadmin route/handler for /misc/ping: https://github.com/pgadmin-org/pgadmin4/blob/31fddaf10b02242c63d7629fe923332b557a8b92/web/pgadmin/misc/init.py#L145-L149

Fixed in the latest version of pgadmin


Pre-release link updates

Updates the links referenced in the readme to reference a specific, fixed commit hash so that any links won't be broken if we update the referenced files later.

@Jdubrick Oops, Gabe had raised that earlier and I forgot to fix that. Good to do that before the blog post is published.

Updated


Update DataMapping member types.

Update DataForgeDataMapping StructIndex and StructCount types and reads for new structure in Datacore version 5.
Needs legacy support for v4, please ignore for now, and do not merge.

Added a legacy case in DataMapping, not sure if you want to implement a flag here or edit logic to your liking, but for all intents and purposes this does work.
As an aside, for some reason reading version 5 is much slower than version 4 was. At least much slower than what 8k bytes difference would make you think. I don't have time to profile this tonight to find the exact issue, but will do so tomorrow.


fixes for masternodes

this will code will allow MN's to run

I would like to setupa a Linda coin masternode.  Can anyone help me with directions for iMac?
Thank you


Version Up to v1.8.3

Description
Please include a summary of the change and which is fixed.

Version increasing for release
after #577

How has this been tested?
Please describe the tests that you ran to verify your changes.

[x] UnitTest
[x] Benchmark

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

Project coverage is 90.61%. Comparing base (66c5bb9) to head (2a9c29d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #594      +/-   ##
==========================================
+ Coverage   90.59%   90.61%   +0.02%
==========================================
  Files         129      129
  Lines        4741     4741
  Branches      773      773
==========================================
+ Hits         4295     4296       +1
  Misses        288      288
+ Partials      158      157       -1

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


AttributeError: module 'modules.functional' has no attribute 'furthest_point_sampling'

Can this code be run with cuda-9.2? modules.functional doesn't work on my machine with cuda-9.2

Hi, @Prominem. Could you please provide detailed error information?
By the way, our experiments are all conducted on PyTorch 1.3.1 + CUDA 10.0/10.1.

thanks for replying, @synxlin I solve this problem by restarting my computer.


Server-side entries search

Currently search works against the entire set of entries in-memory, which is convenient but won't scale up to a large number of entries (See also, #133).
https://www.firebase.com/docs/web/guide/retrieving-data.html#section-queries describes how to query Firebase. Full-text search support on their end isn't great, but hopefully is good enough that we can filter by titles and show results to the user.
Results should be paginated using the same UI as #133.

@ctcleary This was fixed by #139 yes?

Not exactly.
We have a bandage over the problem because we search the most recent 100 entries by default (and we can really easily up that number if needed). But the search still functions precisely the same way, so if a user needs to "search all" because their target isn't in the most recent 100 entries, it'll still be really slow.
Figuring out how to do the server side search felt like a separate issue. I can bump this to the top of my current issues priority list if'n you like.

Ah, sure. I mis-remembered how your search impl from #139 worked. #138 is more important than this.


Bug? Can't close the presentViewController

Hi there,
We want an extra button in the end of the 'Walkthrough' slide. But the code doesn't work when we link it to this new button "Get started Now". (and it use this viewcontroller use the same "BWWalkthroughViewController.swift" file)
@IBAction func btngetstartednow(sender: AnyObject) {
delegate?.walkthroughCloseButtonPressed?()
}
Thanks,

The delegate is not meant to be used in that way.
You are manually calling a delegate function that should be only called by the class when the "close" button is pressed.

How create then on the end of the slide a big button with the text "Get Started Now" that close this guide?


Feature/clarify teams

Clears up some of the wording in regards to teams and adds a disabled Member A filed to the team form for clarity:

I like this a lot, clears things up
:shipit:


Please add ComfyUI-Gaffer

https://github.com/huagetai/ComfyUI-Gaffer
Also iclight_sd15_fc.safetensors https://huggingface.co/lllyasviel/ic-light/blob/main/iclight_sd15_fc.safetensors

I've added the original iclight weights:
https://github.com/fofr/cog-comfyui/commit/fe1b20db381a683852de3d0a32c83070d9c4de3d

Please use the more popular nodes for ICLight, either:
https://github.com/huchenlei/ComfyUI-IC-Light-Native
https://github.com/kijai/ComfyUI-IC-Light


increasing mining complexity over running chain

HI @macfarla @shemnon @matkt
Is any way to increasing mining complexity over running besu chain?

@diega any insight?

@puneet166 what do you mean by increase mining complexity? the mining difficulty is defined by the network to keep block time in ~12 seconds in average, there is nothing within the clients that can be done to change that

PoW is now deprecated so we won't be adding features to it


Add connection profile-based Fabric adapter

Signed-off-by: Attila Klenik<EMAIL_ADDRESS>Issue/User story
Changes related to the adapter:

Updated the sample benchmarks to also support the new adapter API
Added settings for the new adapter in the default Caliper configuration file
Added sample network configurations for the new adapter (from v1.0 to v1.2, including mutual TLS networks from v1.1). Most of the additions originate from these example configurations, which are easy to check/test
Added lightweight Caliper-level dependecies (for general use, not Fabric-specific packages), like tmp and version-compare
Changed some require calls to YAML parsing for reading network configuration files in bench-flow.js
Integrated the new adapter into blockchain.js
Added general utility functions for checking/asserting property and version-related information

Directly related issues (and many more regarding the other adapter)
#37 #115 #139 #185 #227 #292
Validation of the fix
For each sample benchmark, pick a configuration file (like the linear rate config), and run it with every network version/topology/fabric-ccp* configuration combination.
What documentation has been provided for this pull request
#297
@hyperledger/caliper-committers @nklincoln Any help with the review if appreciated!

EDIT: I forgot to extend the src/comm/transaction.js class with the functions used by the adapter.

@panyu4 Fixed. Checked with the following commands (from the network dir):
grep -Ril "goleveldb" . --include=fabric-ccp*.yaml
(only *goleveldb, dev and customdomain folders should be listed)
grep -Ril "couchdb" . --include=fabric-ccp*.yaml
(only *couchdb folders should be listed)

@nklincoln , could you please review this pr and give some advice?

@feihujiang I've added the contract ID feature, so the API for invoking a tx is the same as before (with default invoker value, so that also disappeared from the benchmarks). The only decision point is now for the arg of the invoke, which we can't really avoid for now. The older query API is a little rigid, I kept it consistent with the invoke API in this adapter.
Note: there was some conflict in package.json, so the PR now contains an additional merge commit that I can't seem to squash...


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43971

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44204

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/54057

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64265

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95346


Problem with C++ translation

Though the kata is validated (tests are said to be correct) I get: "Kata was published with failing tests" and nothing is published...

Which translation?

Since a few days every C++ translation but when I wrote previously it was https://www.codewars.com/kata/twice-linear. I gave it a second try and it worked on this second try though I got "Kata was published with failing tests" on the new first try.

Background processing had stopped. Everything is working now so please verify that this is still a problem for you. Thanks.

The problem is there with PHP too. https://www.codewars.com/kata/disguised-sequences-ii worked only on the 2nd try, On the 1st I got: "Kata was published with failing tests".
For now I can't experiment with C++.

Doesn't happen anymore if the kata is saved prior to publish:-)


Please deprecate ScanFilters in the RxBleClient.scanBleDevices(ScanSettings scanSettings, ScanFilter... scanFilters) method

Apparently, ScanFilters doesn't work on some devices. For example, filtering by Service UUID doesn't work on Samsung Galaxy S6 (as documented by https://stackoverflow.com/questions/34065210/android-ble-device-scan-with-filter-is-not-working - and I confirmed this issue myself today, after spending 2+ hours troubleshooting). The workaround is to remove all ScanFilters and filter results "manually".
RxAndroidBle shouldn't expose broken OS functionality, when a workaround is so apparent. Please remove ScanFilters altogether, and let developers filter results with an Rx .filter operator - which is going to work 100%.
Thanks.

Could you disclose more details about the issue you encountered? I.e.

what is the BLE advertisement's payload you want to match?
what is the exact setup of ScanSettings and ScanFilters you use?

Sure - just a basic filter by service UUID - nothing fancy:
      rxBleClient.scanBleDevices(
           ScanSettings.Builder()
               .setScanMode(SCAN_MODE_LOW_LATENCY)
               .build(),
           ScanFilter.Builder()
              .setServiceUuid(ParcelUuid(serviceUuid))
              .build()
      )

this works on many devices, but on Galaxy S6 there are no results.

I had run a quick check with Samsung SM-G920F / API 24 seems to work as intended. I would need more info. Unfortunately the linked SO post is not very consistent in terms of the actual situation with what the peripheral is advertising and what is the bug.
rxBleClient.scanBleDevices(
    ScanSettings.Builder().setScanMode(ScanSettings.SCAN_MODE_LOW_LATENCY).build(),
    ScanFilter.Builder().setServiceUuid(ParcelUuid.fromString("6E400000-B5A3-F393-E0A9-E50E24DCCA9E")).build()
)
    .observeOn(AndroidSchedulers.mainThread())
    .subscribe(
        { Log.e("SUCCESS", "OK!") },
        { Log.e("FAILURE", "NOK!", it) }
    )

2019-11-21 14:56:23.981 19454-19475/com.polidea.rxandroidble.sample I/RxBle#ClientOperationQueue: RUNNING  ScanOperationApi21{ANY_MUST_MATCH -> nativeFilters=[BluetoothLeScanFilter [mDeviceName=null, MAC=null, mUuid=6e400000-b5a3-f393-e0a9-e50e24dcca9e, mUuidMask=null, mServiceDataUuid=null, mServiceData=null, mServiceDataMask=null, mManufacturerId=-1, mManufacturerData=null, mManufacturerDataMask=null]]}
2019-11-21 14:56:23.983 19454-19789/com.polidea.rxandroidble.sample I/RxBle#QueueOperation: Scan operation is requested to start.
2019-11-21 14:56:24.642 19454-19454/com.polidea.rxandroidble.sample I/RxBle#Client: ScanResult{bleDevice=RxBleDeviceImpl{MAC='D3:4D:73:E8:41:1F', name=Queued_Write}, rssi=-46, timestampNanos=267733097276126, callbackType=CALLBACK_TYPE_ALL_MATCHES, scanRecord=[03, 19, 00, 00, 02, 01, 06, 11, 07, 9E, CA, DC, 24, 0E, E5, A9, E0, 93, F3, A3, B5, 00, 00, 40, 6E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]}
2019-11-21 14:56:24.643 19454-19454/com.polidea.rxandroidble.sample E/SUCCESS: OK!
2019-11-21 14:56:25.202 19454-19454/com.polidea.rxandroidble.sample I/RxBle#Client: ScanResult{bleDevice=RxBleDeviceImpl{MAC='D3:4D:73:E8:41:1F', name=Queued_Write}, rssi=-46, timestampNanos=267733679303001, callbackType=CALLBACK_TYPE_ALL_MATCHES, scanRecord=[03, 19, 00, 00, 02, 01, 06, 11, 07, 9E, CA, DC, 24, 0E, E5, A9, E0, 93, F3, A3, B5, 00, 00, 40, 6E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]}
2019-11-21 14:56:25.202 19454-19454/com.polidea.rxandroidble.sample E/SUCCESS: OK!
2019-11-21 14:56:25.595 19454-19454/com.polidea.rxandroidble.sample I/RxBle#Client: ScanResult{bleDevice=RxBleDeviceImpl{MAC='D3:4D:73:E8:41:1F', name=Queued_Write}, rssi=-47, timestampNanos=267734069510418, callbackType=CALLBACK_TYPE_ALL_MATCHES, scanRecord=[03, 19, 00, 00, 02, 01, 06, 11, 07, 9E, CA, DC, 24, 0E, E5, A9, E0, 93, F3, A3, B5, 00, 00, 40, 6E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]}
2019-11-21 14:56:25.596 19454-19454/com.polidea.rxandroidble.sample E/SUCCESS: OK!
2019-11-21 14:56:25.842 19454-19789/com.polidea.rxandroidble.sample I/RxBle#CancellableDisposable: Scan operation is requested to stop.

Since I have no more actionable info and disabling the whole feature would be a big loss for the whole user base — I am closing until more info is available.

Accidentally I have recreated the issue while looking for UUID 43210100-5678-9012-3456-789012345678 — it may be worth reinvestigating


accept query selector as app target

this implies being able to create an app instance that represents an array of apps.

closing because this would be better handled from outside


Bug Report - Error from "docker-compose -f docker-amundsen-atlas.yml up"

Env: Docker running on Windows 10
Steps:

Download Amundsen on 12/15/2021 and successfully installed/deployed Amundsen with Neo4j;
Stop Amundsen;
Download Amundsen into another folder to install/deploy Amundsen with Atlas;
From the new Amundsen folder run "docker-compose -f docker-amundsen-atlas.yml up"
Result with the following error:

=> ERROR [stage-1 7/7] RUN pip3 install -e .                                                                      5.6s

[stage-1 7/7] RUN pip3 install -e .:
#21 1.703 Obtaining file:///app
#21 5.292     ERROR: Command errored out with exit status 1:
#21 5.292      command: /usr/local/bin/python -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/app/setup.py'"'"'; file='"'"'/app/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-qhcfveei
#21 5.292          cwd: /app/
#21 5.292     Complete output (10 lines):
#21 5.292     /bin/sh: 1: npm: not found
#21 5.292     ERROR:root:npm must be available
#21 5.292     /bin/sh: 1: npm: not found
#21 5.292     /app/setup.py:30: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead
#21 5.292       logging.warn('Installation of npm dependencies failed')
#21 5.292     WARNING:root:Installation of npm dependencies failed
#21 5.292     /app/setup.py:31: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead
#21 5.292       logging.warn(str(e))
#21 5.292     WARNING:root:Command '['npm install']' returned non-zero exit status 127.
#21 5.292     error in amundsen-frontend setup command: 'extras_require' must be a dictionary whose values are strings or lists of strings containing valid project/version requirement specifiers.
#21 5.292     ----------------------------------------
#21 5.292 WARNING: Discarding file:///app. Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
#21 5.293 ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
#21 5.482 WARNING: You are using pip version 21.2.4; however, version 21.3.1 is available.
#21 5.482 You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.

executor failed running [/bin/sh -c pip3 install -e .]: exit code: 1
ERROR: Service 'amundsenfrontend' failed to build : Build failed

cc @mgorsk1 any idea

able to run "docker-compose -f docker-amundsen.yml up" in the same environment without any error.
I wonder if the Amundsen docker containers created from the previous "docker-compose ..." run need to be removed first before running "docker-compose -f docker-amundsen-atlas.yml up" on that same host.

you could always try by doing docker-compose -f docker-amundsen-atlas.yml build --no-cache to test it

Just tested that "... build --no-cache" option as suggested and received the exact same error

This looks like the same error message here: https://github.com/amundsen-io/amundsen/issues/1317
Seems to be related to the setup.py of frontend and Windows.
I have the same error when running this: docker-compose -f docker-amundsen-local.yml build

Confirmed "docker-compose -f docker-amundsen-local.yml build" had same error.
But "docker-compose -f docker-amundsen.yml up/build" worked without error.

Yes, I think it's because docker-amundsen.yml use an image

Contrary to docker-amundsen-atlas.yml and docker-amundsen.yml which has to build it :

The last comment of fforever14, to change "FROM python:3.7-slim" to "FROM nikolaik/python-nodejs:python3.7-nodejs12-slim" in the Dockerfile.frontend.local file seems to resolve the error of npm.
But I still have the error: "error in amundsen-frontend setup command: 'extras_require' must be a dictionary whose values are strings or lists of strings containing valid project/version requirement specifiers."

Same here


Fix nuget determinism

Investigating why CI build has this:

Was not an issue in the end. I needed to also download the snupkg and have it beside the nupkg for NGPE to properly evaluate those fields.


runtime error: slice bounds out of range Polkadot Block 4383090

We ran into this issue when trying to parse the above block. Using the latest commit
runtime error: slice bounds out of range [:-5919563810157205112]
/usr/local/go/src/runtime/panic.go:106 (0x40378e4)
        goPanicSliceAcap: panic(boundsError{x: int64(x), signed: true, y: y, code: boundsSliceAcap})
/Users/gavinwoods/go/pkg/mod/github.com/itering/scale.go@v1.0.13/types/scaleBytes.go:18 (0x483a059)
        (*ScaleBytes).GetNextBytes: data := s.Data[s.Offset : s.Offset+length]
/Users/gavinwoods/go/pkg/mod/github.com/itering/scale.go@v1.0.13/types/base.go:69 (0x4839ec1)

you may check if types match first

Im having this issue because I followed the solution in this issue thread: https://github.com/itering/scale.go/issues/21
Whilst that does fix the issue with the block 4230783 it causes issues with block 4383090.
Not having the keys type does however fix the latest block.
How do i proceed?

@infinitedaremo   polkadot.json add "ValidatorPrefs#28-?": "ValidatorPrefsWithBlocked"


add utility for graphql API tests

Description of changes
I added an annotation and parameter resolver for easy setup of graphQL API tests.
How has this been tested?
Tested on the course service by implementing a API test there.

[ ] automated unit test
[ ] automated integration test
[ ] automated acceptance test
[ ] manual, exploratory test

In case of manual test, please document the test well including a set of user instructions and prerequisites. Each including an action, it's result, and where appropriate a screenshot.
Checklist before requesting a review

[x] My code follows the coding guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My code fulfilles all acceptance criteria
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have made corresponding changes to the documentation
[ ] I have added explanation of architectural decision and rationales to wiki/adr
[ ] I have updated the changes in the ticket description

Checklist for reviewer

[ ] The code works and does not throw errors
[ ] The code is easy to understand and there are no confusing parts
[ ] The code follows the coding guidelines of this project
[ ] The code change accomplishes what it is supposed to do
[ ] I cannot think of any use case in which the code does not behave as intended
[ ] The added and existing tests reasonably cover the code change
[ ] I cannot think of any test cases, input or edge cases that should be tested in addition
[ ] Description of the change is included in the documentation

TODO update pr template


Getting error "Unhandled Permission Error"

`[Unhandled promise rejection: Error: Tried to use permissions API but the host Activity doesn't implement PermissionAwareActivity.]

node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:155:41 in createErrorFromErrorData
node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:104:55 in
... 5 more stack frames from framework internals`

my package.json file

Same problem here. Did you find a way around it?

I was trying to modify android/app/src/main/java/host/exp/exponent/MainActivity.java in my ejected Expo app like https://github.com/expo/expo/issues/2224#issuecomment-463242706 or https://github.com/wix/react-native-navigation/issues/3283#issue-328350574. But that didn't help. Weird that I see it only in the dev mode. It works fine if I compile a release apk.


Removed unused config prop

Fixes #595
Description

Removed: config prop

Checklist

[x] I have made corresponding changes to the documentation.
[x] I have added the necessary label (patch/minor/major - If package publish is required).

Reviewers
@AbhayVAshokan _a

@gaagul _a

@AbhayVAshokan _a I have made the suggested changes, Please verify these and let me know if there are more changes to be made.