Rewrite test & deploy action

As pointed out by Kevin in PR #92, the test & deploy action in that branch runs many tests that each build and test the Taweret wheel on a different setup.  However, since Taweret publishes to PyPI only a source distribution and a pure Python universal wheel this is certainly overkill. In addition, it builds a wheel, doesn't test it, and then publishes it.
The idea of having the sanity checks in the action run over all possible installations seems good. For example, there is a possibility that significant time could pass between the last PR testing and publishing to PyPI. If something changed in the setups between the PR and publishing, we want to test on the latest setups before publishing.
Therefore, in this issue we should study the possibility of redoing the action so that it

Runs a single job that creates the source distribution and wheel
If that was successful, it runs in parallel tests of both distributions across all setups using the results of the first job
If all those are successful, it publishes the actual distributions that were tested.

One possible difficulty with this is storing and propagating the built distributions across jobs.

I have added a new release.yml GH action that

creates a source distribution and a universal binary wheel,
tests these across many test setups,
and archives the distributions.

According to
https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=published#release
this action should be run whenever a draft, prerelease, or release release on the main branch is published.  This is in main, but has not yet been tested.
Since Taweret only publishes a few releases per year and automating the publishing of distributions to PyPI with GH actions does include potential security risks (See here and here), we will presently manually publish the distributions to PyPI.
I have added a rough draft of the procedure for this in a new Gatekeepers wiki page in the repo
https://github.com/bandframework/Taweret/wiki/Gatekeeper-Information
@asemposki Is this a good place for this procedure?  Comments, questions, concerns regarding the procedure?  When you have time, can you try to "publish" the release as a prerelease to see if this triggers release.yml?

We've used the gatekeeper procedure to upload v1.1.0 to PyPI.  @asemposki will update and improve based on her experience.
Since we are currently happy with publishing to PyPI manually rather than by GH action, we can now close this.


Problem with Node v0.5.9-85-g6cc0c9e

ryan@mac1234:/tmp% npm search faye
npm WARN Building the index for the first time, please be patient
npm ERR! Error: [object Object] : -/all
npm ERR!     at Request.callback (/Users/ryan/local/node/lib/node_modules/npm/lib/utils/npm-registry-client/request.js:181:12)
npm ERR!     at Request.<anonymous> (/Users/ryan/local/node/lib/node_modules/npm/node_modules/request/main.js:341:18)
npm ERR!     at Request.emit (events.js:67:17)
npm ERR!     at IncomingMessage.<anonymous> (/Users/ryan/local/node/lib/node_modules/npm/node_modules/request/main.js:309:16)
npm ERR!     at IncomingMessage.emit (events.js:88:20)
npm ERR!     at HTTPParser.onMessageComplete (http.js:133:23)
npm ERR!     at CleartextStream.ondata (http.js:1112:24)
npm ERR!     at CleartextStream._push (tls.js:343:27)
npm ERR!     at SecurePair.cycle (tls.js:632:20)
npm ERR!     at EncryptedStream.write (tls.js:121:13)
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR!
npm ERR! System Darwin 10.8.0
npm ERR! command "node" "/Users/ryan/local/node/bin/npm" "search" "faye"
npm ERR! cwd /private/tmp
npm ERR! node -v v0.5.10-pre
npm ERR! npm -v 1.0.99
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /private/tmp/npm-debug.log
npm not ok

also
ryan@mac1234:/tmp% npm install faye
npm ERR! Could not create /Users/ryan/.npm/redis/0.6.7/package.tgz
npm ERR! Failed creating the tarball.
npm ERR! couldn't pack /var/folders/Rn/Rng4WPpdGsGk79HI1mNbIU+++TM/-Tmp-/npm-1319047590073/1319047590073-0.3728851550258696/contents/package to /Users/ryan/.npm/redis/0.6.7/package.tgz
npm ERR! error installing<EMAIL_ADDRESS>Error: EACCESS, Permission denied '/Users/ryan/.npm/redis/0.6.7'
npm ERR! Error: EACCESS, Permission denied '/Users/ryan/.npm/redis/0.6.7'
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR!
npm ERR! System Darwin 10.8.0
npm ERR! command "node" "/Users/ryan/local/node/bin/npm" "install" "faye"
npm ERR! cwd /private/tmp
npm ERR! node -v v0.5.10-pre
npm ERR! npm -v 1.0.99
npm ERR! path /Users/ryan/.npm/redis/0.6.7
npm ERR! code EACCESS
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /private/tmp/npm-debug.log
npm not ok

I'm seeing the same error when I try to npm search the first time.  I'm also using node v0.5.10-pre and the latest npm.

Has nothing to do with node.
The problem is that someone posted a package named "error", and that's usually a signal that something is broken in couchdb, so my couchdb code is keying off of that value in any responses, and calling it a problem.

Fix coming in 1.0.100, very soon.

Fixed.


feat(swapper): remove deprecated getSwapper method

getSwapper is deprecated, and is now only used in tests.
This PR removes it and uses Map.prototype.get() in the tests instead.

This feels a little weird to me having get be the only method interacting directly with the map versus add/remove/etc using the helper functions. To me it seems like we either want to just interact with the map directly (a-la chainAdapterManager), or if there is extra necessary logic as part of the swapper manager (ie. getBest) that we don't want to duplicate in the client, then we can just have the swapper manager class and interact with the provided methods imo.

as discussed - let's talk to the manager through it's interfaces it exposes, rather than the raw map of swappers

@0xApotheosis plz undeprecate this (lol) as to not cause future confusion


e2e: Introduce basic BundleInstance tests

Introduces barebones BundleInstance e2e tests.

(just dumping what I've had sitting locally since earlier this week so we're not duplicating work while I'm on PTO)

I'm going to disappear for the rest of the day so I added a TODO comment around re-evaluating the UX around the Installed: false BI status condition that @exdx outlined, that we create when an unpacked Bundle was stamped out, but then subsequently removed, and the result is those unpacked Bundle contents are still present on-cluster but the status condition we write to the BI can be confusing to end users.


function reset cannot work as expect

When I trying the following code snips， it cannot work as expect(print no feed in the past 60 seconds!)
import Watchdog from './src/watchdog'
async function main() {
  const dog = new Watchdog()
  const food = { data: 'wang' }
  dog.feed(food)
  await new Promise(resolve => setTimeout(resolve, 61 * 1000))
  console.log('sss')
  dog.on('reset', () => console.log('no feed in the past 60 seconds!'))
  dog.on('feed', () => console.log('get feed!'))
  dog.sleep()
}
main()

While  when I add   dog.on('reset', () => console.log('no feed in the past 60 seconds!')) before await new Promise(resolve => setTimeout(resolve, 61 * 1000)) as follows:
import Watchdog from './src/watchdog'
async function main() {
  const dog = new Watchdog()
  const food = { data: 'wang' }
  dog.feed(food)
  dog.on('reset', () => console.log('no feed in the past 60 seconds!'))
  await new Promise(resolve => setTimeout(resolve, 61 * 1000))
  console.log('sss')
  dog.on('reset', () => console.log('no feed in the past 60 seconds!'))
  dog.on('feed', () => console.log('get feed!'))
  dog.sleep()
}
main()

It can get no feed in the past 60 seconds! in the next reset. It seems reset should be registered before.

Yes, you are right.


Enable TP+PP support

Stack from ghstack (oldest at bottom):

-> #285
#161
#172

I am assuming that this PR is not for landing as is but rather for testing?


Re-enable VS code analysis for live test pipelines once it is functional

It was disabled here since it wasn't working in VS 2022 (Windows 2022) legs:
https://github.com/Azure/azure-sdk-for-cpp/pull/6024
cc @weshaggard, @danieljurek

Also: Change the trigger for VS code analysis from an environment variable to a cmake option for consistency - static analysis being configured via environment variables is inconsistent from all the other configuraiton options in the repo, and isincredibly confusing.


Low priority: Disable inline italicizing of text cells when inside a latex block denoted by $....$

For the latex block:
$entropy = \sum-p_i log_2(p_i)$
The characters between the _'s are italicized inline. They shouldn't be in this case since it is in a latex block.

agreed, & we already have an issue for this: https://github.com/twosigma/beaker-notebook/issues/3280
thanks


docs: link typo

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

Its not the only one
https://github.com/dfinity/portal/issues/1361


Deck Layout

This was featured on river recently, and I would like to see it implemented for AwesomeWM. Here's an example from snakedye on the r/unixporn discord:

The clients get stacked as shown, and displayed like a deck of cards.

that does look epic


Dead link in Machine Learning with Snowpark Python

Describe the bug
Link points to
https://github.com/Snowflake-Labs/sfguide-citibike-ml-snowpark-python/blob/main/00-Setup.ipynb, should point to https://github.com/Snowflake-Labs/sfguide-citibike-ml-snowpark-python/blob/main/00_Setup.ipynb
URL of where you see the bug
https://quickstarts.snowflake.com/guide/machine_learning_with_snowpark_python/index.html?index=..%2F..index#2
To Reproduce
Steps to reproduce the behavior:

Go to 'https://quickstarts.snowflake.com/guide/machine_learning_with_snowpark_python/index.html?index=..%2F..index#2'
Click on 'Then, open up the 00-Setup Jupyter'

Expected behavior
Opening the notebook
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: iOS
Browser: chrome
Version 105.0.5195.102

thanks for the heads up! a fix has been pushed


Minor edits in view of better Edoc use in the future.

Bare minimum to make rebar3 edoc pass.
The ultimate goal is to have better developer documentation and better specs/docs in modules.


Add missing peer dependencies in eslint-plugin and stylelint-plugin

Description
@shopify/eslint-plugin and @shopify/stylelint-plugin are missing peerDependencies on @babel/core and prettier.
While it's not a massive problem, it does make life harder for package managers when trying to optimize package installation, see Implicit Transitive Peer Dependencies.
yarn currently reports both of these packages as missing peer dependencies:
➤ YN0000: @shopify/eslint-plugin@npm:42.1.0 doesn't provide @babel/core, breaking the following requirements:
➤ YN0000: @babel/eslint-parser@npm:7.22.9 → >=7.11.0

➤ YN0000: @shopify/eslint-plugin@npm:42.1.0 doesn't provide prettier, breaking the following requirements:
➤ YN0000: eslint-plugin-prettier@npm:4.2.1 → >=2.0.0

➤ YN0000: @shopify/stylelint-plugin@npm:12.0.1 doesn't provide prettier, breaking the following requirements:
➤ YN0000: stylelint-prettier@npm:3.0.0 → >=2.0.0

Noted both changes as patch, because consumers will already have been required to fulfil these requirements, so it's not forcing them to upgrade or install new packages with potential breaking changes.

Note: I know the CLA needs signing, it just requires internal approval first, should only be a few days :)


KinematicBody2D (Ball) Stutters and Jumps even when only object in scene.

Godot version: 3.0.1

OS/device including version: Windows 10 Home, Nvidia GTX980 (Driver Ver. 391.01)

**Issue description: KinematicBody2D
I just have a ball bouncing around, no other graphics and the ball stutters and sometimes jumps forward in the direction it is moving. Is this an engine bug? I am using KinematicBody2D, Sprite and CollisionShape2D (Circle). Doesn't seem to matter whether I am using  #_physics_process(delta) or _process(delta).
I did also code it directly with position += direction * speed * delta, and it was better, but still jumping, but less stuttering. (Compared to move_and_slide which I have now(is worse))
PS. This is my first time to do this, so please contact me if you need more info, Thanks DS**

**Steps to reproduce:

Please run code, or executable.

See if the ball is stuttering and occasionally jumping in the movement direction, happens quite often, jumping is smaller or bigger but is more arbitrary, should happen within a minute**

**Minimal reproduction project:
Ball Performance Test Project.zip
test ball performance executable.zip**

I cannot see the code or project settings because the examples are compiled, in any case, looks like a duplicate of the old #2043

Yeah it seems to be the same problem, unfortunately I couldn't find that topic when I searched for KinematicBody2D or I missed it.
I turned off vsync in the project settings, that helped, so it's ok 90% of the time. I've also read that it could maybe be fixed in Godot 3.1. Any release date for it yet?
Here is the project, I hope one can read the code now. (If it is still of interest)
Ball Bouncing Test Project.zip
Thanks

No ETA for 3.1, and not sure if the work on the physics frame interpolation has started yet (and there are other camera improvements too that may help on this).
Oh, and try adding a background image, sometimes the effects is seen worse over the clear color than with a background texture.

I get jitter with a fairly small example:
`extends KinematicBody2D
var velocity = Vector2(0,0)
func _ready():
set_physics_process(true)
func _physics_process(delta):
var right_input = Input.is_action_pressed("right")
var left_input = Input.is_action_pressed("left")
velocity.x = 0
if right_input:
	velocity.x =150
if left_input:
	velocity.x = -150

move_and_slide(velocity, Vector2(0, -1))

`
I recorded a video with OBS and on most frames, my "Player" node moves the same distance, but on a few frames, there is no movement. Presumably this is because sometimes two frames get rendered between two calls to _process I guess. I've set the physics frame rate to 120 but it didn't help.
2018-03-16 12-30-24.zip
So yeah, seems like interpolation is needed. :)

Duplicate of https://github.com/godotengine/godot/issues/10388. Try installing and enabling lawnjelly's smoothing add-on to get physics interpolation in your project.


Create Game SDK Key

[x] Game Edit: 64 characters fixed-length key
[x] SDK request handler

verified and close it.


AMPI Fortran command line arg's not parsed consistently w/ Fortran standard

Original issue: https://charm.cs.illinois.edu/redmine/issues/669

To recreate using the attached program:
./build AMPI net-linux-x86_64 gfortran gcc
ampif90 cmd_line.f90 -o cmd_line
./charmrun ./cmd_line x y z
This should cause the following output:
Arg count =  3
Arg 1: x
Arg 2: y
Arg 3: z
But instead nothing gets printed out.
If you comment out lines 4 and 25 and uncomment lines 3 and 26, you can recompile and run it as a regular MPI program:
mpif90 cmd_line.f90 -o cmd_line
mpirun -n 1 ./cmd_line x y z
And it gives the expected output.

Original date: 2015-02-12 21:20:55

This problem does not occur with C/C++ AMPI programs, only Fortran.
The example program uses the Fortran2003 standard's command line parsing functions. Before the 2003 standard, Fortran did not have a standard way of accessing the command line, though gfortran provided its own intrinsic functions iargc() and getarg() which other compilers copied before the 2003 standard.
MPI implementations seem to differ on their support of Fortran command line arguments. MPICH1 required compiler intrinsics for it and MPICH2 and MPICH3 abandoned that requirement and guaranteed nothing.

Original date: 2015-02-18 22:33:48

I found two functions in ampif.C for handling command line arguments in Fortran AMPI programs: mpi_get_argc() and mpi_get_argv().
These have to be called in place of the usual Fortran command line parsing functions in order to handle command line arguments in Fortran AMPI programs.
These functions use the C/C++ idiom of command line parsing though: they include the program's name in argc and argv. Fortran does not include the program's name or anything before it in the argument list. I will add functions to AMPI that follow the Fortran conventions so that you can drop the replacements into a Fortran MPI program when running with AMPI.
Also, this should probably be added to the AMPI documentation somewhere, since no other MPI implementation does this. And more generally we might also want to add a Fortran AMPI example program to examples/ampi/.


stdarch: test SSE 4.2

With https://github.com/rust-lang/miri/pull/3622 that should work now

@TDecking  with the additional intrinsics you implemented, are there more things from stdarch we should be able to cover now?

bmi1 and bmi2 can be added now. Note that these extensions exist independent from each other, which means that both bmi1 and bmi2 must be added to the target feature flag. Merging rust-lang/miri#3690 will cover the adx extension.
The main Rust repository does has updated their stdarch submodule yet, so fma can not be added.

@RalfJung


Do not obtain localPath when caching data on master is disabled

This should prevent errors like https://github.com/prestosql/presto/pull/3987#issuecomment-642225940 when caching data on master is disabled. Cache itself needs to be enabled on master because coordinator needs to know where to schedule splits.

This variable is getting dropped in https://github.com/qubole/rubix/pull/381/files but I am merging this for just in case #381 is delayed


bump(typography): upgrade to version 14

Codecov Report

Merging #820 (b69c05e) into next (bf2eded) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             next     #820      +/-   ##
==========================================
+ Coverage   80.75%   80.81%   +0.05%
==========================================
  Files         108      108
  Lines        3351     3351
  Branches      768      768
==========================================
+ Hits         2706     2708       +2
+ Misses        640      638       -2
  Partials        5        5

Impacted Files
Coverage Δ

src/list/foundation.tsx
75.83% <0.00%> (+1.66%)
:arrow_up:

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


Add validators to FormFields

Currently DocumentForms work fine, but the Flutter validation features at in use at all.

hey @rickspencer3
You should definitely have a look at this !
https://github.com/danvick/flutter_form_builder
Its very complimentary to your RAD approach, in that the building of the GUI is data driven.
Dan has built all of the highly complex Form Validation. Its really well done.
So you can take your Document List approach and then for the Forms use Dan's Form builder.
Both are data driven !
I am working on Routing that is data driven.
Let me know what you think :)

I will for sure look into it. It does seem related. I started a separate issue for it #115

ok great that you can see how it might help you.


Blank page

I installed Kopf with
sudo bin/plugin -install lmenezes/elasticsearch-kopf

But when I try to access the application through http://my-host:9200/_plugin/kopf, all I see is a blank page.
What should I check?

which version of elasticsearch do you have?
do you have any security related plugins?
whats the output of curl -XGET http://your-host:9200/_plugin/kopf ?
can you see any error on your browser console?

The output of curl:
Gabriels-MacBook-Pro-2:~ gabriel$ curl -XGET http://my-host:9200/_plugin/kopf/
Gabriels-MacBook-Pro-2:~ gabriel$ curl -XGET http://my-host:9200/_plugin/kopf
<meta http-equiv="refresh" content="0; URL=/_plugin/kopf/>Gabriels-MacBook-Pro-2:~ gabriel$

Elasticsearch:
{
"status": 200,
"name": "Longshot",
"cluster_name": "elasticsearch",
"version": {
"number": "1.4.0",
"build_hash": "bc94bd81298f81c656893ab1ddddd30a99356066",
"build_timestamp": "2014-11-05T14:26:12Z",
"build_snapshot": false,
"lucene_version": "4.10.2"
},
"tagline": "You Know, for Search"
}

All the plugins I have:
[ec2-user@ip-10-0-12-118 elasticsearch]$ ls -lah plugins/
total 20K
drwxr-xr-x 5 root root 4.0K Feb  2 16:19 .
drwxr-xr-x 5 root root 4.0K Dec  9 20:45 ..
drwxr-xr-x 3 root root 4.0K Feb  2 16:19 head
drwxr-xr-x 3 root root 4.0K Feb  2 15:56 kopf
drwxr-xr-x 3 root root 4.0K Dec  9 20:45 paramedic

can you access the other plugins?
also, what do you see on the console when you first try to open the plugin?

and last, which browser are you using?

I can access the Paramedic, and I am using Google Chrome, version 40.0.2214.94 (64-bit), on OSX.
Here's the screenshot:

By the way, there are no error messages in the log file:
/var/log/elasticsearch/elasticsearch.log

[2015-02-02 16:37:05,429][INFO ][node                     ] [Ripfire] version[1.4.0], pid[5290], build[bc94bd8/2014-11-05T14:26:12Z]
[2015-02-02 16:37:05,430][INFO ][node                     ] [Ripfire] initializing ...
[2015-02-02 16:37:05,436][INFO ][plugins                  ] [Ripfire] loaded [], sites [head, kopf, paramedic]
[2015-02-02 16:37:07,924][INFO ][node                     ] [Ripfire] initialized
[2015-02-02 16:37:07,924][INFO ][node                     ] [Ripfire] starting ...
[2015-02-02 16:37:08,023][INFO ][transport                ] [Ripfire] bound_address {inet[/0:0:0:0:0:0:0:0:9301]}, publish_address {inet[/<IP_ADDRESS>:9301]}
[2015-02-02 16:37:08,036][INFO ][discovery                ] [Ripfire] elasticsearch/sTrctCcmRP6H_8tYkrH01g
[2015-02-02 16:37:11,802][INFO ][cluster.service          ] [Ripfire] new_master [Ripfire][sTrctCcmRP6H_8tYkrH01g][ip-10-0-12-118][inet[/<IP_ADDRESS>:9301]], reason: zen-disco-join (elected_as_master)
[2015-02-02 16:37:11,836][INFO ][http                     ] [Ripfire] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/<IP_ADDRESS>:9200]}
[2015-02-02 16:37:11,836][INFO ][node                     ] [Ripfire] started
[2015-02-02 16:37:12,493][INFO ][gateway                  ] [Ripfire] recovered [5] indices into cluster_state
[2015-02-02 16:37:13,235][INFO ][cluster.service          ] [Ripfire] added {[logstash-<IP_ADDRESS>-2112-2010][i2y4ufXzSxynfx5eAUza1Q][inet[/<IP_ADDRESS>:9300]]{client=true, data=false},}, reason: zen-disco-receive(join from node[[logstash-<IP_ADDRESS>-2112-2010][i2y4ufXzSxynfx5eAUza1Q][inet[/<IP_ADDRESS>:9300]]{client=true, data=false}])

Here's some additional info:
When I do:
$ curl http://localhost:9200/_plugin/kopf/

From the server's console, I get:
[ec2-user@ip-10-0-12-118 ~]$ curl http://localhost:9200/_plugin/kopf/
<!DOCTYPE html>

    <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
    <meta charset="utf-8">
    <meta name="description" content="">
    <meta name="author" content="">
    <title>kopf</title>
    <link href="./font-awesome/css/font-awesome.css" rel="stylesheet">
    <link href="dist/lib.css" rel="stylesheet">
    <link href="dist/kopf.css" rel="stylesheet">
    <link ng-href="dist/{{getTheme()}}_style.css" rel="stylesheet">

          <ng-view onload="initializeController()" ng-show="hasConnection()"></ng-view>

But when I try to access the plugin from another machine, all I get is the blank page.
Could it be something related to CORS?
Here are my CORS settings in /etc/elasticsearch/elasticsearch.yml:
http.cors.enabled: true
http.cors.allow-origin: "/.*/"

I would try commenting out the http.cors.allow-origin line. All I've ever had to do to get it working is the http.cors.enabled: true line.

I use:
http.cors.enabled: true
http.cors.allow-origin: "*"

Make sure your firewall is open. Restart Elasticsearch after changing the config.

@gcobr did you have any luck with this?

I will close it for now. If it's still a issue, please reopen it :)


feat: Deploy HTML docs to the docs branch of Bitbucket

Deploy the Sphinx built HTML files to the docs branch of Bitbucket using https://github.com/davisp/ghp-import.
ghp-import will remove all the files located in the remote "docs" branch and then push the generated HTML files to the docs branch.

Do you have an example how this looks like in Github? I saw already the example in BitBucket server which is super cool +1

I tried generating GitHub Pages for https://github.com/tomtom-international/ebr-connector but there is some issue with the rendering.
https://aev.github.io/CoRTEX_ADTF2Generator/ is a good example on how it looks on Github but not sure if it is published using ghp-import.

Please validate the changes in one of our internal Python projects

done


Lists in HTML

Adding type of lists in html

Sure u can go ahead with it

Merge my pr pls and add hactober-fest accepted label


Fix transient SystemExit error with IPP config

Running pytest --config configs/local_ipp.py, I see this intermittently:
Traceback (most recent call last):
  File "/Users/awoodard/ci/parsl/parsl/dataflow/dflow.py", line 191, in handle_update
    res = future.result()
  File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 398, in result
    return self.__get_result()
  File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 357, in __get_result
    raise self._exception
  File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/site-packages/ipyparallel/client/asyncresult.py", line 224, in _resolve_result
    raise r
ipyparallel.error.RemoteError: SystemExit(-1)

We need to figure out what is causing this. Note as a stop-gap measure, CI is currently running pytest --config local instead of pytest --config basic, which would include the local_ipp.py config. We should consider this issue fixed when we can switch travis back to running pytest --config basic.

How intermittent (on a percentage-of-runs scale) do you see this?

Closing. Not an issue anymore.


Wraith Tests for Several Domains

Hi Everyone,
This is more of a question: I would like to use Wraith to run tests on several different websites (different domains with different sets of paths) that share all other settings. I could probably achieve this by setting up completely separate Wraith setups in separate directories, but that would duplicate a lot of configuration, JavaScript, etc.

Is there a way to do that in one config file?
If not, is there a way to do it in the same Wraith setup using separate config files without interference?
And unrelatedly, is there some restriction on valid characters in YAML keys in the Wraith config? I’ve been seeing weird phenomena around hyphens.

So far I’ve been trying to settle for the option implied in question 2, but the resulting gallery seems all jumbled up and its URL contains no identifier of the domain (/shots/gallery.html), so that I have to assume that Wraith tries to generate one gallery for all sites.
Many thanks!

sentience-politics.org.history.yaml.txt
ea-foundation.org.history.yaml.txt
ea-stiftung.org.history.yaml.txt

There is an open feature request (#324) which would allow YAML files to import the contents of other YAML files (which could pull in a 'standard_config.yml' file, for instance) which should answer your question. It's on our list, but no guarantee on when this will be done - pull requests are welcome!

if you could narrow it down and simplify a config as much as possible so that it reproduces the problem, please file a bug ticket.

Thanks


Removed deprecations slated for 1.97

Fixes https://github.com/CesiumGS/cesium/issues/10512 by removing deprecated functions TileProviderError.handleError and TileProviderError.handleSuccess.

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Remove old contracts and implementation supporting them

Summary

RFCs: Link to RFC, Link to RFC, or $\emptyset$.
Categories: any of protocol-units, networks, scripts, util, cicd, or misc.

Changelog

Testing

Outstanding issues

Still working on this


Add Keycloak to Example CNCF/CDF Projects

This PR proposes adding Keycloak to Example CNCF/CDF Projects of Identity and secret services Capability in CNCF Platforms White Paper.
Keycloak is a CNCF incubating project and an identity and access management OSS.

@joshgav Thank you for reviewing! Are there any other things to do to proceed with this PR?

@y-tabata nope, thanks for the reminder! Merged.

@joshgav Thanks!


Duplicate metrics from resilience4j.circuitbreaker.calls

We moved over from the old Hystrix to Resilience4j. We decided to go with Spring Cloud Circuit Breaker as it fit our needs.
After deployment we realized quickly the metrics looked strange, as the picture shows, when comparing the old metrics from Hystrix with the new from Resilience4j. They seemed to somehow have doubled.

I could reproduce this with a simple JUnit tests that runs a circuit breaker for 200 times. When I check the Meter registry, I could see that the metric resilience4j.circuitbreaker.calls had counted 400 times. So it is obviously a double. Then I spend probably 4 hours debugging through Spring Cloud Circuit Breaker and resilience4j-spring-boot3 classes and autoconfiguration, but could not find the root cause, but I found a solution.
If we configure the following: resilience4j.circuitbreaker.metrics.legacy.enabled=true and re-run the tests, we did not get any duplicate metrics any more as the test showed 200 counts. So the issue has something to do with this parameter.
This parameter is set to false by default.
So the dilemma here is I do not know if I should have reported the issue here or at resilience4j. I humbly apologize if this is the wrong repo. However, I suspect that the combination of Spring Cloud Circuit Breaker and resilience4j-spring-boot3 might cause this issue. This is just a theory, I have not yet confirmed it.
With resilience4j.circuitbreaker.metrics.legacy.enabled=false (default)

With resilience4j.circuitbreaker.metrics.legacy.enabled=true

We use:
Spring Boot 3.3.2
Spring Cloud 2023.0.3

@ryanjbaxter
I made a quick test it as you said by only using Resilience4j Spring Boot 3, without any custom configurations.
As we can see below it works as expected:

import io.github.resilience4j.circuitbreaker.annotation.CircuitBreaker;
import org.springframework.stereotype.Component;

@Component
public class CB {

    @CircuitBreaker(name = "MYCB", fallbackMethod = "fallback")
    public String test() {
        return "OK";
    }

}

So it seems to be a conflict with autoconfiguration of Spring Boot Circuit Breaker and Resilience4j Spring Boot.
It seems to have something to do with multiple consumers for the EventProcessor being added that will produce metrics twice for the same event. I believe the same consumer is added by Resilience4j Spring Boot and another by Spring Boot Circuit Breaker.
My colleague has been checking deeper and I believe he will write a more detailed result.

I'm a team mate of the reporter. I ran the same unit test that he did.
I noticed that the timer is invoked twice, because the same EventProcess instance get call twice.
By setting a breakpoint in EventProcessor line 40 with condition
this instanceof CircuitBreakerStateMachine.CircuitBreakerEventProcessor && className.equals("io.github.resilience4j.circuitbreaker.event.CircuitBreakerOnSuccessEvent")
I could see that the same processor instance is indeed registered twice. Why?
Here is the diff of the two call stacks:

I interpret it as if the registration of the processor triggers an onEntryAddedEvent .
With
resilience4j.circuitbreaker.metrics.legacy.enabled=false
I can see that I have two consumers referencing the same time instance:

With
resilience4j.circuitbreaker.metrics.legacy.enabled=true
I can see that I have two consumers referencing the different timer instances:

I'm continuing the investigation and trying to nail it down in the debugger, but I have to call it then day now. I'll update any further findings I get.

Thanks appreciate the update. Please keep me updated on what you find.

We have made some progress. The reporter has better knowledge and can provide better feedback, but his out-of-office for a while.
The short versions is that there is an issue with the robustness of the setup of Spring Autoconfiguration. You may end up in a situation where you get two TaggedCircuitBreakerMetricsPublisher beans.
The first one is created by io.github.resilience4j.springboot3.circuitbreaker.autoconfigure.CircuitBreakerMetricsAutoConfiguration.taggedCircuitBreakerMetricsPublisher.
The second one is created by org.springframework.cloud.circuitbreaker.resilience4jResilience4JAutoConfiguration.MicrometerResilience4JCustomizerConfiguration  even if there is a condition @ConditionalOnMissingBean({ TaggedCircuitBreakerMetricsPublisher.class }).
To quote the JavaDoc of ConditionalOnMissingBean

If a candidate bean may be created by another auto-configuration, make sure that the one using this condition runs after.

There is no such guard here.
In our specific case we had code that caused the autoconfiguration to run in the "incorrect" order. We changed some of our code that in turn resulted in the two above autoconfigurations to run in the "correct" order. It "works" but it's not entirely robust.
I hope this explains it well enough.

Thanks @cbarreholm and @OathMeadow!
Would it be possible to create a sample that recreates the issue?
Seems like you have to have resilience4j.circuitbreaker.metrics.legacy.enabled=true for the issue to occur and that seems to be the default behavior since matchIfMissing is set to true in the Resilience4J auto-configuration.
I could imagine two solutions.  The first solution would be to add @AutoConfigureAfter(CircuitBreakerMetricsAutoConfiguration.class).  The second solution would be to disable MicrometerResilience4JCustomizerConfiguration when resilience4j.circuitbreaker.metrics.legacy.enabled=false (or is missing).  The first solution would be preferable IMO.  A sample to test these solutions out would be very helpful.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

@OathMeadow I believe thtat you are better suited for reviewing the suggested solution.
I tried to create a sample project to reproduce it, but failed. I guess that we could at least beta test a possible solution by checking out our project at the failing version and run a potential fix.

@cbarreholm @OathMeadow I created a PR with the proposed change
https://github.com/spring-cloud/spring-cloud-circuitbreaker/pull/218
If you want to use that to test it out in your environment that would be great!

I have merged the PR in hopes that it addresses the issue.  It is a low risk fix in either case.


virtualenv_create(libexec, "python") results in error upon install

Within install, the line virtualenv_create(libexec, "python"), per doc recommendations, resulted in the following installation error:
Last 15 lines from /Users/anja/Library/Logs/Homebrew/visidata/14.pip:
  Removing source in /private/tmp/pip-req-build-CH6VRn
visidata requires Python '>=3.4' but the running Python is 2.7.10
Exception information:
Traceback (most recent call last):
  File "/usr/local/Cellar/visidata/1.2/libexec/lib/python2.7/site-packages/pip/_internal/basecommand.py", line 228, in main
    status = self.run(options, args)
  File "/usr/local/Cellar/visidata/1.2/libexec/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 291, in run
    resolver.resolve(requirement_set)
  File "/usr/local/Cellar/visidata/1.2/libexec/lib/python2.7/site-packages/pip/_internal/resolve.py", line 103, in resolve
    self._resolve_one(requirement_set, req)
  File "/usr/local/Cellar/visidata/1.2/libexec/lib/python2.7/site-packages/pip/_internal/resolve.py", line 262, in _resolve_one
    check_dist_requires_python(dist)
  File "/usr/local/Cellar/visidata/1.2/libexec/lib/python2.7/site-packages/pip/_internal/utils/packaging.py", line 55, in check_dist_requires_python
    '.'.join(map(str, sys.version_info[:3])),)
UnsupportedPythonVersion: visidata requires Python '>=3.4' but the running Python is 2.7.10

Presumably installation defaulted to the default system Python, which on my machine is Python 2.7. I can see this as not being an isolated case.
When the line was switched to the more explicit virtualenv_create(libexec, "python3") the package installed without any issues.
Arguably, I am not as comfortable as I would like with Homebrew's relationship with Python, so maybe this reveals a larger underlying issue within brew or within the VisiData Formula.
The formula is hosted here.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

:)


Beautiful Soup 4 no longer supports Python versions < 2.7

Current releases of Beautiful Soup 4 have dropped support for Python 2.6 and earlier.  Since this is a major dependency, suggest changing ofxparse to match.

There is also at least one test ("testThatParseTransactionWithCommaAsDecimalPointAndDotAsSeparator") that uses python 2.7 specific features.
I'm working on getting a continuous build going, should I drop support for Python 2.6?

Yes, let's drop support for Python 2.6

This was addressed in PR #121


Transfer rules_jsonnet to bazel-contrib

Description:
This issue proposes transferring the rules_jsonnet repository from the bazelbuild GitHub organization to the bazel-contrib GitHub organization, which is owned by the Community for Bazel project under the Linux Foundation.
GitHub Discussion: https://github.com/orgs/bazelbuild/discussions/2
Impacts:

GitHub issues & PRs will be transferred to the new repository.
Branch protection rules will be transferred to the new repository.
Individual maintainers will be transferred to the new repository.
GitHub teams will NOT be transferred to the new repository and will need to be re-created.
Bazel CI configurations will need to be updated to point to the new repository.

Read more on Transferring a repository from GitHub documentation.
Checklist:

[x] Obtain approval from the current project maintainers (@EdSchouten, @sparkprime, @Globegitter).
[x] Obtain approval from the bazel-contrib SIG (@alexeagle).
[ ] Initiate the transfer process on GitHub (@meteorcloudy).
[ ] Update Bazel CI settings and confirm presubmit & postsubmit work (@meteorcloudy).

Approved!

Thanks for the approvals, I'll initiate the transfer now.

Done, presubmit verified at https://github.com/bazel-contrib/rules_jsonnet/pull/201
Let me know if there is any issues.


Add basic speaker-like sound playing

The missing piece to be able to write some retro-style games or demos is the ability to play some sounds. I'd probably start mimicking the PLAY statement from Locomotive BASIC to generate speaker tones, but may need to research this further. Obviously we could go all fancy and support sound files too, but that should come later.

I can provide PLAY implementation for javascript. I will look into it and when I have usable demo I would hand over it to you to integrate it.

@severak That'd be great! Just having a prototype in Javascript to model the built-in PLAY command from would be helpful, as I know zero about how to generate sound right now.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Old Tibetan gi -> g gi issue

in:
SPLITCOHORT (
  "<$1>"v "$1ག་"v σ
  "<$2>"v "ག$4"v σ
)("<(.)((\\u0F42)([\\u0F72\\u0F80]་?))>"r)

that means you're also going to split the following:

དགི* -> དག་གི*
བགི* -> བག་གི*
མགི* -> མག་གི*
འགི* -> འག་གི*

but in these 4 cases it can be analyzed as

prefix (ད, བ, མ or འ)
main letter ga
gigu

instead of the contraction... so maybe
SPLITCOHORT (
  "<$1>"v "$1ག་"v σ
  "<$2>"v "ག$4"v σ
)("<([^དབམའ])((\\u0F42)([\\u0F72\\u0F80]་?))>"r)

could be more accurate? Or maybe in some cases it's more likely to be a contraction ? wdyt?

@eroux what do you mean by "contraction"?

@eroux what do you mean by "contraction"?

I mean the case for which the rule has been done, like པགི་ > པག་གི་

I mean the case for which the rule has been done, like པགི་ > པག་གི་

to be a bit more explicit: པགི་ cannot be "normal" Tibetan, it's necessarily པག་གི་, so the rule works in that case. OTOH, དགི can be regular Tibetan and doesn't necessarily represent དག་གི, and I'm not sure it's a good idea to apply the rule in that case. (I'm also not sure it's a bad idea)

to be a bit more explicit: པགི་ cannot be "normal" Tibetan, it's necessarily པག་གི་, so the rule works in that case. OTOH, དགི can be regular Tibetan and doesn't necessarily represent དག་གི, and I'm not sure it's a good idea to apply the rule in that case. (I'm also not sure it's a bad idea)

both དགི and འགི can be regular Tibetan. Let me have a deeper look at it and I will let you know.

both དགི and འགི can be regular Tibetan. Let me have a deeper look at it and I will let you know.

yes, དགི and འགི (and བགི and མགི) can be regular Tibetan, that's why I think the rule should be adjusted. The rule works on པགི་ though, which cannot be regular Tibetan

yes, དགི and འགི (and བགི and མགི) can be regular Tibetan, that's why I think the rule should be adjusted. The rule works on པགི་ though, which cannot be regular Tibetan

Hi @eroux I am back on finalizing the normalisation grammar - atm I am working on the OT Ramayana and I added new rules to take care of some cases in the new text. I want to solve the issues that you raised as well. For this contractions with the genitive. བགི and མགི cannot be regular Tibetan.  དགི and འགི can - in all OTDO there are no cases of དགི and few cases of  འགི which I don't think are contractions (and do not appear in our texts). I would modify the rule as follow:
SPLITCOHORT (
"<$1>"v "$1ག་"v σ
"<$2>"v "ག$4"v σ
)("<([^དའ])((\u0F42)([\u0F72\u0F80]་?))>"r)
What do you think?

looks good, thanks!


Pass targetHosts property to agent

There's no way to get perfTest.targetHosts in test script.
I found there's ngrinder.etc.hosts property but it indicates targetHosts only in specific condition
So I made a feature that pass targetHosts property to Agent following steps bellow

Put ngrinder.target.hosts property to GrinderProperties in PerfTestService if perfTest has targetHosts.
Add it to agent property as targetHosts in PropertyBuilder

@outstanding1301
Why do you need targetHosts in your script?

By the way, this feature seems good.
@imbyungjun review and merge it.

@outstanding1301
What's the difference between ngrinder.etc.hosts and targetHosts? I don't understand this property addition is necessary.

These are the result what I printing ngrinder.etc.hosts and targetHosts.
Perftest Configuration

Test Script
grinder.logger.info("{}", System.getProperty("ngrinder.etc.hosts"))
grinder.logger.info("{}", System.getProperty("targetHosts"))

Result Log
2022-09-28 14:56:35,859 INFO  mylaptop.local:<IP_ADDRESS>,localhost:<IP_ADDRESS>,www.naver.com:<IP_ADDRESS>,www.google.com:<IP_ADDRESS>
2022-09-28 14:56:35,859 INFO  www.naver.com:<IP_ADDRESS>,www.google.com:<IP_ADDRESS>


Child slider triggers the parent beforeChange listener

I have a slider that has a slider inside of it.  whenever i click on the dots or the left right arrows (of the child slider), it triggers the beforeChange of my parent slider.  is it possible to prevent this?

====================================================================
[  https://jsfiddle.net/hytnxwkL/1/  ]
use this jsfiddle to reproduce your bug:
http://jsfiddle.net/simeydotme/fmo50w7n/
we will likely close your issue without it.
====================================================================
Steps to reproduce the problem

create slider, then inside one of the slider item, create another slider in it.
create a beforeChange listener for the parent slider.
on the child slider, press left/right or the dot navi buttons.

====================================================================
What is the expected behaviour?
child should not trigger parent beforeChange event
...
====================================================================
What is observed behaviour?
child triggers parent beforeChange event
...
====================================================================
More Details

Which browsers/versions does it happen on?chrome
Which jQuery/Slick version are you using? 1.6
Did this work before? sure not, i am

@raymundbiddi I've just come across this after having the same problem as yourself. This does seem to be a real problem so here is the workaround I used.
$('.parentSlider').on('beforeChange', function(event, slick, currentSlide, nextSlide){
		if (slick.$slider.context.className === 'childSlider') {
                        //do nothing
		} else {
			//do intended action
		}
	});


ready_for_unit is emitted too early

Bug Description
Currently, ready_for_unit is emitted based on relation events only:
https://github.com/canonical/traefik-k8s-operator/blob/494741059d931a9827e8214401f61cde8585582e/lib/charms/traefik_k8s/v1/ingress_per_unit.py#L692-L695
This is racy with the traefik workload: sometimes the remote app processes the event before traefik workload is in fact ready.
To Reproduce
Relate prometheus and traefik.
Environment

traefik-k8s                   edge      84

Relevant log output
# Prometheus gets the "ready-for-unit" event, but http requests still fail

Ingress for unit ready on 'http://pd-ssd-4cpu-8gb.us-central1-a.c.lma-light-load-testing.internal:80/cos-lite-load-test-prometheus-0'

config reload error via http://localhost:9090/cos-lite-load-test-prometheus-0/-/reload: HTTPConnectionPool(host='localhost', port=9090): Read timed out. (read timeout=2.0)

# After a while update-status fires, at which point the traefik workload is really ready and http reqs to prom work

Emitting Juju event update_status.

Starting new HTTP connection (1): localhost:9090
http://localhost:9090 "GET /cos-lite-load-test-prometheus-0/api/v1/status/buildinfo HTTP/1.1" 200 188

Additional context
No response

todo: look at https://github.com/canonical/observability-libs/pull/10 and consider implementing some liveness check by using that external process to wake up the charm when "traefik is done", and only then publish the relation data to tell "ingress is ready"


update readme

please update with the latest details

@agalin920 can this be closed?

@agalin920 great, please close and update the status in the support board


Collaboration is selected when dropping the first participant

Describe the Bug
When dropping the first pool to the canvas, the participant is selected but the properties panel shows the collaboration props.

Steps to Reproduce

Drop a participant on the canvas
Participant is selected
Properties panel is showing the Collaborations's props

Expected Behavior
The properties panel is always showing the properties from the selected element, in this case from the participant.
Environment

Host (Browser/Node version), if applicable: Chrome 91.0.4472.77
OS: macOS 10.15.7
Library version: current main

This is probably because we change the root once the first participant is added. Therefore, the behavior of detach (root removed) and attach again (new root was added) kicks in place.
The selection event listener is then added just after the participant got selected on the canvas and can't react to it.


Release/cf219

Reverted the changes from symlink to redirect in mkdocs.yml file.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: sunilkn020:white_check_mark: biancaluna:x: sunilkn002-hclYou have signed the CLA already but the status is still pending? Let us recheck it.


Searching Different on Safari, is it supported ?

I have a search example which works in Chrome but not Safari. If you look at the results variable in the Safari screenshot you will see that the ref number goes from 0 upwards and the score is NaN. The exact same query in chrome shows ref fields with values I expect and scores that make sense.
Are there known problems with Safari, the search string "was" works in chrome.  Safari doesn't fail on all searches, I've noticed that the string "mas" happens to work.

Will just add that even though "was" could be a stop word I remove stop words with:
elasticlunr.clearStopWords();
and I remove the stemmer too:
var index = elasticlunr();
index.pipeline.remove(elasticlunr.stemmer);

I have the exact same issue and also removed the stemmer and stop words.

@harringtonp have you found a solution for this by any chance?

Afraid I haven't. I do wonder though would the same issue arise in lunr. If you figure out what it is let me know

For now the "fix" for me is: don't use Safari if you want to get search results - which is pretty lame to tell people to do.
@weixsong I'd like to fix this, but some hints at where to look would be appreciated. I'm not entirely sure where to start looking as I'm not familiar with the internals.

@xarg I wrote my own search solution which was easy (in my case) and has no cross browser issues. Code at:
https://stackoverflow.com/a/46446723/7778427


Cublas extension

Added BLAS 2 and 3 functions (SYRK and SBMV) for real and complex types

The respective issue link to link

Currently, I cannot find what is the error in rocm-build

After some sleep, I just found the same build error reason too. The build and tests passed.

I cannot change the status of the issue from "Changes requested". The changes have been implemented and pushed to the repository.

/test mini

What are the next steps?

The PR looks complete to me (I hadn't reviewed it in depth). So if CIs pass and everything looks good we should merge it soon :)
Thanks!!

I wanted to make sure I don't miss any important steps. Thanks for the update.


MNT: add arjanz as maintainer

Checklist

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

@arjanz for the record, please comment here

@arjanz for the record, please comment here

Sure, here you go :)


[Suggestion]: Allow players to equip the Hang Glider in a separate Trinkets slot

Suggestion (Required)
Basically allow the hang glider to be equipped in the same slot Elytra Slot (GH) uses for Elytras.

Thanks for the suggestion. That wouldn't work since you need to activate the glider from your hand for it to open up. Also it doesn't make much sense as a Trinket to me since you are holding it in your hands. It's also intentional that your hands can't do anything else while gliding, you are holding on to the glider after all.


How to use it?

I am a beginner of AoA positioning. I want to use this project for target location. Which platform should I run this project on? And how to run it?

@coderswk
Glad to hear that you are interested in AoA positioning.
Please note that this project only includes the documentation website and only covers the measurement setup and results. This repository does not include code for AoA hardware. I have used hardware from Texas Instruments, on their website you will find more detailed instructions for setting up such a positioning system.
Texas Instrument - AoA Setup
Here you can find the used hardware:
BoostXL-AoA - Antenna array
LAUNCHXL-CC26X2R1 (since CC2640R2 is no longer supported)
I hope this helps.


[stable/keycloak] Provide a way to run kcadm cli commands (e.g. disable ssl)

It would be useful to have a neat way to disable SSL on the master realm. The kcadm cli would be a good mechanism that would also enable other commands to be run.
The preStartScript doesn't provide for this as it runs before keycloak has started. It would seem to require a postStartScript.

Closing based on https://github.com/kubernetes/charts/pull/6108#issuecomment-398418011


Grouping regions

Hi,
first of all, congrats for you guys, wavesurfer.js is awesome.
I am using it in a project where I have to use 2 different kind of regions. Let's say for instance that I need a group of regions for user audio comments and another one for automatic audio transcript. Is there a way to create different kind of region and group them?
If not, could you give me a first starting point to implement it?
Thank you so much

I'm not sure if this will cover your situation, but for me, I needed to make regions, and also have small markers similar to the regions. I could not use the same regions plugin for both because they needed different functionality. What I did was modify the regions plugin and rename it for my markers. So now I have a regions plugin and a separate marker plugin.
My suggestion would be to add a second regions plugin and modify and rename it to work with the additional use you require.
I'm not sure what you mean by group them however. Could you clarify this?

@berio you can add arbitrary data to your regions and filter/group them according to this data.
Here's an example adapted from here:
         wavesurfer.addRegion({
            start: 10,
            end: 20,
            data: {
                group: 'user comments'
            }
        });

Group like this:
        var userCommentRegions = [];

        Object.keys(wavesurfer.regions.list).forEach(function (id) {
            var region = wavesurfer.regions.list[id];

            if (region.data.group == 'user comments') {
                userCommentRegions.push(region);
            }
        });

Thank both of you for your answers. I did what maxehnert says and it is working perfect. I know, katspaugh, that your approach is more clean, it would be good give it a try in the future.
Again, congrats for wavesurfer.js, the more I work with it, the more I like it.

:thumbsup:

@katspaugh that is a great suggestion. I'm not sure yet if I'd be able to change mine to something like that, but I'm going to look into it and try it out.  +1 for simplicity!

@maxehnert I think your solution is fine as well, as long as your markers differ greatly from regions.


Conditional operators: .when() / .unless() / .tap()

Feature discussion / request
Very often I saw  conditional cases with knex, like:
const query =knex('users').where({first_name: 'Test'});

if (request.has('company_id')) {
   query.where('company_id', request.get('company_id'));
}

if (! request.has('status')) {
   query.where('status', 'active');
}

...

I think it may be simpler and easy to read and support such code without breaking the chain. It may be something like:

knex('users').where({first_name: 'Test'})
  // Conditional execution when the first argument is TRUE
  .when(request.has('company_id'), (query) => query.where(...request.only('company_id')))

  // Conditional execution when the first argument is FALSE
  .unless(request.has('status'), (query) => query.where({status: 'active'}))

  // Always executes, without condition checking, to save the chain.
  .tap((query) => {
      const age  = request.get('age');

      query.when(age > 18, (query) => query.where({ adult : true }));
  })
...

Something like that was realized in Laravel framework
Sorry, if it's duplicates some existing feature request, but I don't see anyone.

Could these be implemented as a separate npm module which can be loaded as a knex plugin. API is found in docs just below https://knexjs.org/#Builder-queryContext
We can list that extension in knex docs, so that people can find it easier.
Would be great in a long run to be able to make knex core functionality even slimmer and at the same time more robust and better tested so that it will be good platform for others to build on top of it...

Yep, but in another hand it can be much simple but powerful to get such feature out of the box, isn't it ?

For all intents and purposes I would opt for .if(condition, ...args) / .ifNot(condition, ...args) over .when(condition, ...args) / .unless(condition, ...args).


sample REST API

Added new solution to the Samples for the API's
Using Nancy Self Hosted for lightweight HTTP API.
Sample Usage: HTTP POST 2 images to the given API URL and get 1 image response

Great job! 😉

Seems like everything is ready to be merged?

Seems like everything is ready to be merged?

Merged!


Transpose throws an annoying wrench in the mix

Summary
When you call torch.nn.F.linear() you will call transpose on the weight.
One solution for doing this is to lazily compute the transpose, which is mark that the matrix needs to be transposed when it encounters a realizing op. In this case that would be addmm and mm. Did not handle correctly double even transposes cause I think that's unlikely

https://github.com/pytorch-labs/float8_experimental/blob/main/float8_experimental/float8_ops.py#L44
right now we have this "emulate" field where whenver you write an op you have to make sure that emulate gets set correctly on the newly created Float8Tensor.
I just did something similar for NF4 and that works, but I feels kinda code smelly to me. Its essentially a lazy transpose but since we only need to support these 3 ops it should work.

@rohan-varma Okay I added this and it works, need to add compile tests and the do the memory profiling things


the engine doesnt want to compile anymore and i dont know why

Describe your bug here.
so i was gonna compile psych engine but now its giving me a weird message and i dont know how to fix it
Command Prompt/Terminal logs (if existing)
source/Main.hx:72: characters 61-65 : Float should be Int
source/Main.hx:72: characters 61-65 : ... For optional function argument 'updateFramerate'
source/Main.hx:72: characters 61-65 : ... For function argument 'child'
source/MenuCharacter.hx:90: lines 90-91 : Warning : This case is unused

Are you modding a build from source or with Lua?
Source
What is your build target?
Mac
Did you edit anything in this build? If so, mention or summarize your changes.
No

Flixel 5.0.1 is released


The Mode documentation page does not mention optimization.usedExports

Feature to document
Mode
Additional information
The Mode documentation page does not mention that the production mode turns on optimization.usedExports, but the Optimization page does. It causes inconsistency and can be confusing.

@montogeek I will look into it and send a PR

@mwanago hi man, are you still on this?


Sign up and login thumbnail issue resolved

Fixes #
On the both pages of signup and login it was showing the same thumbnails.

@armudgal here is my pull request. Please review it once.

IDK which issue it refers to, please follow the PR template

Also can make sure that buttons are aligned properly ? Buttons in screenshot looks ugly to me
Some tips here https://uxplanet.org/designing-ux-login-form-and-process-8b17167ed5b9

@armudgal  the buttons are looking good without outlining so I think we should not add outlines on the buttons.

@armudgal the buttons are looking good without outlining so I think we should not add outlines on the buttons.

please let me know about any other changes if not then I'll submit another PR.

Please resolve the conflicts

I think the current sign up/ sign in page is working fine.


Need to look back at merged pull request

Hi, THX for all your effort, this plugin really helps a lot when I take a review!
After a few days of experience, I hope it has a new category named "merged" so that I be able to review merged PR.

You can do this by editing your queries setting. Example:
	"githubPullRequests.queries": [
		{
			"label": "Waiting For My Review",
			"query": "is:open review-requested:${user}"
		},
		{
			"label": "Assigned To Me",
			"query": "is:open assignee:${user}"
		},
		{
			"label": "Merged By Me",
			"query": "is:merged author:${user}"
		}
	],


Mismatch of render() interface between MetaWorld and Gym

Currently the render function of MujocoEnv does not take a mode argument for the render() function and instead exposes the offscreen flag.
https://github.com/rlworkgroup/metaworld/blob/a0009ed9a208ff9864a5c1368c04c273bb20dd06/metaworld/envs/mujoco/mujoco_env.py#L121-L133
This is an issue when using the environments e.g. with any form of gym wrappers. As seen here https://github.com/openai/gym/blob/2853ce4797a4dadb1f8702c8e35143d9fbd43ea6/gym/core.py#L253-L254 the mode is passed as argument to the underlying environment per default. If render is not explicitly called as render(False), we have offscreen='human' and the check for not offscreen will fail.
From what I can see the offscreen flag seems to be the same as mode=human and mode=rgb_array in the base gym interface. Is there any specific reason the offscreen flag is introduced over the default behavior?
If not, I think the render() function should not be overloaded this way to remain compatible with existing gym functionality. For the remaining kwargs I do not see any issues, as they fit the interface.
Thanks for looking into this.

This will could be fixed by changing all environments to use mujoco (and the gymnasium MujocoEnv)

Is there any reason in general why the mujoco base env is re-impelmented instead of inherited from mujoco_py?

@csimo005 it is a heavily modified version of the mujoco base env. In a future release we are going to be using the mujoco base env from Gymnasium.