Updating to org.postgresql:postgresql 42.7.0 trips: Missing entry default_transaction_isolation in pg_catalog.pg_settings

CrateDB version
Nightly
CrateDB setup information
Standard Docker "services" setup on CI/GHA.
Problem description
When upgrading org.postgresql:postgresql from 42.6.0 to 42.7.0 on behalf of a Dependabot patch, a QA-style test code yields an error.

Unable to determine a value for DefaultTransactionIsolation due to missing  entry in pg_catalog.pg_settings WHERE name=default_transaction_isolation.
-- https://github.com/crate/cratedb-examples/actions/runs/7000332105/job/19040823665?pr=162#step:8:1829

References

https://github.com/crate/cratedb-examples/pull/162

Steps to Reproduce
git clone https://github.com/crate/cratedb-examples --branch=dependabot/maven/by-language/java-qa/org.postgresql-postgresql-42.7.0
cd cratedb-examples/by-language/java-qa
mvn test

Actual Result
The test suite breaks.
Expected Result
The test suite succeeds.

Can you share a short java snippet that leads to the error?
Just updated the driver in the test suite here, and everything seems to work: https://github.com/crate/crate/pull/15116

Hi Mathias,
thank you for looking into this.

Can you share a short java snippet that leads to the error?

Sure. It seems to be this code snippet at crate-qa::stock_jdbc::JdbcMetaDataTest.java#L192-L197. Below, you will also find references where it trips on behalf of a corresponding crate-qa test run.
With kind regards,
Andreas.
Code Snippet
@Test
public void test_getDefaultTransactionIsolation() throws Exception {
    try (var conn = DriverManager.getConnection(URL)) {
        assertThat(conn.getMetaData().getDefaultTransactionIsolation(), is(Connection.TRANSACTION_READ_COMMITTED));
    }
}

References

https://github.com/crate/crate-qa/pull/288
https://jenkins.crate.io/blue/organizations/jenkins/CrateDB%2Fqa%2Fcrate_qa_on_pr/detail/crate_qa_on_pr/299/pipeline/41#step-286-log-178

Closing this for now.
Given that CrateDB has no transactions none of the regular transaction isolation levels are a 100% match. Failing on the method is therefore not entirely wrong.
We can revisit this if a more concrete use case pops up


moudle "bqf" not found

Neovim version (nvim -v | head -n1)
NVIM v0.9.0-dev-771+g18fb669b9-dirty
Operating system/version
macOS 12.0.1
How to reproduce the issue

use packer.nvim install the plugin
run :lua require('bqf') in neovim command mode

...


Support clearing spans

Closes #75.

I didn't add clearSpanStyles(textRange) and clearRichSpans(textRange) as it seems we should use remove*(textRange) instead.

Thanks for your contribution!
I will check this soon, I've been a bit busy lately.


[Bug]:The default value for PhoneInput is set to text, which is invalid.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The widget gets a text through the default value and does not show an error.
Steps To Reproduce
1 . First Go and select Phone Input  from Ui Section
2. Right Side Bar - There default value
3 . Only accept number for  phone input
Public Sample App
No response
Environment
Production
Severity
Critical (Broken Production apps)
Issue video log
https://www.loom.com/share/5f33f947dc384d1899cd14bbc1a801f1?sid=488efc5e-9b81-495b-bd8c-03def98e686e
Version
cloud

hello @Nikhil-Nandagopal I am picking this issue

Hello @Nikhil-Nandagopal, @Pranvkakde,
Approach 1: The user will see an error message if they enter text in the default field, and the value will not be added to the widget until a number is entered.
Approach 2: Do not allow the user to enter text in a field where a number is expected, eliminating the need for an error message.
I have noticed that the entire application currently follows Approach 1. Could you please explain why Approach 2 is not being used?
I will proceed with Approach 1.
Testing:
Cypress/Jest tests will be created to cover the new behavior of the PhoneInput widget.
Thank you.

This is expected, validations are only for user input and not for developer configurations. Looking at Ant design, it follows the same experience

Okay got it @Nikhil-Nandagopal,
Thank you


Rename joy_interface_node -> mg400_joy_interface_node

launch file test:
only tested ros2 launch xv3unit_pollinator_cpu_bringup mg400.launch.py joy:=true works correctly.


The original codebase of the library

A minor comment would be whether this should really be version 1.0.0. We (try to) use semantic versioning for non-experimental repositories, so labelling this as 1.0.0 should not be taken lightly.

Feel free to merge this @jontje.
If I may suggest: use a squash-and-merge (dropdown). I don't feel a particular need to keep the fixup commit around. But I'll leave it to you.

I'll post some issues to capture some of the things we can improve after you merge this PR.


Lazy initialize Volume on container Mount object

Currently on daemon start volumes are "created" which involves invoking
a volume driver if needed.  If this process fails the mount is left in a
bad state in which there is no source or Volume set.  This now becomes
an unrecoverable state in which that container can not be started.  The
only way to fix is to restart the daemon and hopefully you don't get
another error on startup.
This change moves "createVolume" to be done at container start.  If the
start fails it leaves it in the state in which you can try another
start.  If the second start can contact the volume driver everything
will recover fine.
Signed-off-by: Darren Shepherd<EMAIL_ADDRESS>

ping @cpuguy83 @calavera
wondering, would this have implications if docker volume rm is called before all containers are up (and it not detecting a volume is in use?)

@thaJeztah This is on initializing the mount object for the container, so is fairy independent of the volume itself.  The "createVolume" call is more of a "get reference to."

I'm okay with this change.

Also note the related failure.

There is a failing test that is quite problematic, I will try to find a solution to it.

@cpuguy83 @calavera @thaJeztah I'm going to update this PR with a different implementation, but I was hoping I can get this assigned to 1.10.  I know the code freeze is soon.  It would really help to have a resolution for this issue in 1.10.  If I can't deliver a fix in time, that's fine, but if it can just be tracked against 1.10 that would be helpful.

@ibuildthecloud sgtm, added to the milestone, ping us when you updated the PR :smile:

@ibuildthecloud oh, just to be sure: code freeze is January 14th, so well, no pressure :innocent:

I'm not sure if this is relevant anymore.

Ok no, I repro'd with the recent changes.

I'm carrying this PR in https://github.com/docker/docker/pull/19273.


Ambient cache initialization speed improvement

In order to solve https://github.com/maplibre/maplibre-native/issues/1815
Here is the matching design proposal : https://github.com/maplibre/maplibre-native/pull/1877

The OfflineDatabase.CorruptDatabaseOnQuery still fails.
We would need to create a corrupted database in version 7 of the database model, which opens without any error, but where the first query triggers error of corruption
(with test database in version 6, simply instantiating the object triggers the corruption error when it tries to create the new tables for the model upgrade, which makes the test fail)

How did you make the databases?

@louwers
For databases used for merging / sideloading tests (satellite_test.db, sideload_ambient.db, sideload_sat.db, and sideload_sat_multiple.db), I simply upgraded them with a SQLite database tool by running the upgrade script to model version 7.
For v6.db database (which is used to test the upgrade from version 6 to version 7), I made a copy of v5.db and it with a SQLite database tool by running the upgrade script to model version 6.
I still haven't managed to create the upgraded corrupt-delayed.db database (a corrupted database in version 7 of the database model, which opens without any error, but where the first query triggers error of corruption) to make the OfflineDatabase.CorruptDatabaseOnQuery test succeed :-(

CorruptDatabaseOnQuery test has been temporarily disabled as discussed with @louwers
Could you please proceed with merge? :-)
Thanks a lot.

I ran the offline_database.benchmark.cpp benchmarks:
$ python3 vendor/benchmark/tools/compare.py --no-color benchmarks ./mbgl-benchmark-runner-main ./mbgl-benchmark-runner --benchmark_filter='OfflineDatabase/.*'

Benchmark                                                     Time             CPU      Time Old      Time New       CPU Old       CPU New
------------------------------------------------------------------------------------------------------------------------------------------
OfflineDatabase/InvalidateRegion                           -0.0228         -0.0226        144618        141326        144231        140973
OfflineDatabase/DeleteRegion                               +0.0586         +0.0588      22971082      24316111      22911370      24259681
OfflineDatabase/InsertTileRegion                           -0.0590         -0.0587        236233        222301        235708        221865
OfflineDatabase/InvalidateAmbientCache                     -0.5156         -0.5156         81160         39313         81146         39308
OfflineDatabase/ClearAmbientCache                          +0.0617         +0.0620      23023497      24444877      22966607      24389660
OfflineDatabase/InsertTileCache                            -0.0130         -0.0131        218526        215695        218123        215269
OfflineDatabase/InsertBigTileCache                         -0.0167         -0.0166       2157706       2121650       2157331       2121517
OfflineDatabase/GetTile                                    +0.0092         +0.0092        138014        139284        138001        139266
OfflineDatabase/AddTilesToFullDatabase                     -0.0043         -0.0043        166905        166193        166889        166178
OfflineDatabase/AddTilesToDisabledDatabase                 +0.0309         +0.0309           932           961           932           961
OfflineDatabase/GetTileFromDisabledDatabase                +0.0375         +0.0376           744           772           744           772
OfflineDatabase/ResizeDatabase                             +0.0141         +0.0144            11            11            11            11
OVERALL_GEOMEAN                                            -0.0516         -0.0515             0             0             0             0

Hello @louwers
I have just removed the cout logs in comments.
About the performance test, the improvements are significant when there is a lot of offline data downloaded as offline regions (for example 1,5 GB). The startup of the app is much faster in that case :-)

I downloaded 4GB of offline data.
This is a build before this PR. It loads pretty quickly...?
https://youtube.com/shorts/CZqLHsIXg4I?si=abdOzSF47ZvxOeJ5

@geolives Alright, I will try iOS as well.
What do you think about removing initAmbientCacheSize() and some of the other changes introduced alongside it? It does not serve a purpose anymore after the database is split does it?

What do you think about removing initAmbientCacheSize() and some of the other changes introduced alongside it? It does not serve a purpose anymore after the database is split does it?

It requires further investigation because we still need to compute the ambient cache size to avoid exceeding the maximum chosen size. However, you are right that we need to understand how it was done before integrating https://github.com/mapbox/mapbox-gl-native/pull/15622

@geolives-contact Do you still want to get this merged?

No problem and thanks for the update.


Create broucz.md

Sign CLA 2.0
Congrats on released the Publishing API btw :clap:

Thanks, and welcome!

Hi,
Perfect thank you !


Fix TextField selects all content after the application is resumed

Description
This PR makes EditableText aware of the lifecycle 'resumed' state to let the current selection unchanged when the application is resumed (on web and desktop, 'resumed' means the Flutter app window regained focus).
Before this PR, on web and desktop, the whole content of a TextField was selected whenever a TextField gained focus. This is the correct behavior when tabbing between fields but it is not when a field regains focus after the application is resumed
Related Issue
Fixes When switching to another browser tab or window and then going back, all text on TextField is selected automatically.
Tests
Adds 1 test.

Reason for revert: Google3 roll failing - see b/375019489

I'm sorry for the revert here! So what happened is some Google integration tests failed at this line:
https://github.com/flutter/flutter/blob/48149781f258360dde672f03b1447b28e1211837/packages/flutter/lib/src/widgets/app_lifecycle_listener.dart#L253
'package:flutter/src/widgets/app_lifecycle_listener.dart': Failed assertion: line 253 pos 16: 'previousState == null || previousState == AppLifecycleState.hidden': Invalid state transition from AppLifecycleState.resumed to AppLifecycleState.paused

The test logic is doing something like:
// Enter some text in text fields, click some buttons

tester.binding.handleAppLifecycleStateChanged(AppLifecycleState.paused);

I imagine the test logic needs updating, but I'm not sure exactly what to do yet, hence the revert. Should I try to fix this by simulating a change to the 'hidden' state before 'paused' ?
tester.binding.handleAppLifecycleStateChanged(AppLifecycleState.hidden);

@jacobsimionato See this diagram for the allowed state transitions (or this one)
I think the test is doing an invalid state transition, and one that the engine wouldn't send.  The engine implementations are coded to synthesize any intermediate state transitions if the platform jumps from one to another so that the state machine is followed, and an application can count on getting all the states in the expected order.
So, yes, you should probably add that transition, but if the test is expected to start in a particular state, then you should generate any intermediate states too, so if, for instance, the test starts at resumed, it should generate these states to get to paused:
tester.binding.handleAppLifecycleStateChanged(AppLifecycleState.inactive);
tester.binding.handleAppLifecycleStateChanged(AppLifecycleState.hidden);
tester.binding.handleAppLifecycleStateChanged(AppLifecycleState.paused);

I've now updated the internal tests to do the valid state transitions as you suggested.
@bleroux could you reland the PR? Sorry to make you do it twice!

Could you reland the PR? Sorry to make you do it twice!

Hey @jacobsimionato :wave: !
No problem at all, especially because I just woke up (France time) and see that you already sorted everything out :smile::pray:.
Here is the reland: https://github.com/flutter/flutter/pull/157399.
Can you approve it? That way I will be able to merge it as soon as the CI checks are ok.


Merge 1.7.4

Fetching testbottest from linuxbrew/test-bot
Downloading file:///home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew
Couldn't open file

Hopefully fixed by PR https://github.com/Linuxbrew/homebrew-test-bot/pull/107

Warning: The following directories do not exist:
/home/linuxbrew/.linuxbrew/opt

https://circleci.com/gh/Linuxbrew/brew/1236
brew test-bot is deleting this one directory opt for some reason (though not others).


Update http4s-circe, http4s-core, ... to 0.23.24

About this PR
📦 Updates

org.http4s:http4s-circe
org.http4s:http4s-core
org.http4s:http4s-dsl

from 0.21.34 to 0.23.24
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

💡 Applied Scalafix Migrations

org.http4s:http4s-.*:0.22.0

github:http4s/http4s/v0_22?sha=series/0.22

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.http4s" }
}]

labels: library-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, scalafix-migrations, commit-count:n:2

Superseded by #1608.


lodash dependecy still exists.

The latest scribe-editor installed through npm results in dependency errors.
It says cannot resolve module 'lodash-amd/modern/string/escape' in the below file
https://github.com/guardian/scribe/blob/master/src/plugins/core/formatters/plain-text/escape-html-characters.js
lodash-amd is not listed as dependency,so relevant files are not downloaded.
I had to add<EMAIL_ADDRESS>as dependency to resolve this,the latest lodash-amd doesn't maintain same folder structure, so it's of no help.
This error doesn't not happen when scribe is downloaded from bower. The reason being there are polyfills for that particular dependency thats being added to main scribe.js source file.
I propose adding same polyfill to the file mentioned above to resolve this issue instead of adding and entire obsolete library.
Will make an PR and reference this issue.
Thanks

Thank you for including the temp fix here, @code-smith .

Can someone merge the PR and release it? It would be of great help to me

@code-smith There's a PR open to include<EMAIL_ADDRESS>in package.json this will fix this. While I agree using the whole library may be a bit much, this dependency is used by many of scribe's plugins anyway.

let me give some reasons not to do so.
#1 Lots of code changes in previous releases were aimed at making library independent on lodash, this will just undo everything.
#2<EMAIL_ADDRESS>is older version. Most use lodash-4 , its very different in code to 3.5 and not everyone uses lodash-amd verison and this would bloat the application code base.
It's your decision,  but personally i don't think its the right way to go ahead.
Thanks anyways.

@code-smith - Good point, I didn't notice the move away from lodash dependencies. In the plugin libraries, there was an effort to normalise the version of lodash used which is why I made this decision.

@ShaunYearStrong  thanks for reconsidering your decision. Also note that lodash-amd 4.0 has a very different code structure; most use the latest version , so it will just add another library to user's application code base which is not desirable.
Merging the polyfill PR is a good solution if you ask me

@code-smith - It would work, I'm not a fan of including another library's code in here though.
I think a good solution would be to import the single escape method, available here: https://www.npmjs.com/package/lodash.escape

@ShaunYearStrong  The ployfill i included is an optimal solution that would fix everything.

@code-smith I've spoken to some colleagues and they agree it's the best way. I'll merge it now but release will be someone else, as we're running through quite a few issues atm. Thanks for your work!

@ShaunYearStrong thanks and really appreciate the gesture. I used the editor to build an in-house cms and i must say this is the best out there. You guys rock !!


Access UIPasteboard only during copy action

#616
This change doesn't resolve issue completely, because it seems to be a bug in iOS 13 Simulator (no such cases found in production build crash logs). Even if we move all UIPasteboard usages to background thread, we still may get freeze like this:

However, with this change, the issue will be reproducible only when you try to perform copy action, which makes it less annoying.

Codecov Report

Merging #617 into master will not change coverage.
The diff coverage is 66.66%.

@@           Coverage Diff           @@
##           master     #617   +/-   ##
=======================================
  Coverage   60.59%   60.59%
=======================================
  Files          92       92
  Lines        4875     4875
=======================================
  Hits         2954     2954
  Misses       1921     1921

Impacted Files
Coverage Δ

...ms/TextMessages/TextMessageMenuItemPresenter.swift
61.53% <66.66%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30b0e5d...9c9715c. Read the comment docs.

This issue is fixed in Xcode 11.2 Simulator, see comments in #616


ng-table css 0.8.3 installed with bower does not provide sorting arrows

Hi,
I have noticed that if I use bower installed ng-table css, I do not see sorting arrows, however if I specify
https://cdnjs.cloudflare.com/ajax/libs/ng-table/0.8.3/ng-table.css
arrows are there

@casper1149 I have installed ng-table 0.8.3 through bower, but did not come across such issue. Please make sure that you are properly including css file.

Also bower is no longer supported as of the latest version of ng-table


Is there any plans to publish latest MS WebDriver NuGet package?

Thank you for accept the pull request which I sent.

Pull request #9

But, at this time, the NuGet package of MS WebDriver latest version doesn't publish yet.
Is there any plans to publish latest MS WebDriver NuGet package in these days?
P.S.
If you need to new package files, there is an package file which I built 4 days before on my forked repository.
https://github.com/jsakamoto/nuget-selenium-webdriver-microsoftwebdriver/releases/tag/v.10.0.16299

@jsakamoto, latest NuGet package had published.

@rafflesgun Thank you very much for your great work! 👍


Specify dependency path of packages that should be bumped

Problem
I have i.e. four packages: app, page-users, page-settings, ui-kit.
"app" is using "page-users" and "page-settings"
"page-users" and "page-settings" are using "ui-kit"

              app
             /    \
            /      \
           /        \
          -          -
     page-users    page-settings
          \          /
           \        /
            \      /
             -    -
             ui-kit

For example if i make a breaking change in ui-kit and use it in page-users i need to bump all the packages except page-settings, it will use the old version of ui-kit, by that i will know that my changes will not break page-settings.
I need to specify a tree path how changesets will bump the versions, maybe like linked-packages
Proposed solution
Probably my use case is very specific, maybe it would be possible to overload the way how changesets determines what packages should be bumped.

Could you describe this in more detail? I fail to see why page-settings shouldn't be bumped if it depends on ui-kit that has been changed.

Could you describe this in more detail? I fail to see why page-settings shouldn't be bumped if it depends on ui-kit that has been changed.

@Andarist to make the application more tough, if somebody will change ui-kit and make some bug it will not affect page-settings as it will point to previous version of ui-kit. So there will be no accidental issues across all application.
Just imagine a very large application with dozens of teams that are working on the same code base. Some pages are not touched for months since some work on them has been finished. And if some of the developers will break ui-kit it will affect all the pages, but because of the large application this change can be missed on this page because it is "canned". Yes, this will increase the size of the output bundle as there will be two versions of the same package, but it is trade of to increase stability and make the app more bullet proof.

@Andarist to make the application more tough, if somebody will change ui-kit and make some bug it will not affect page-settings as it will point to previous version of ui-kit. So there will be no accidental issues across all application.
Just imagine a very large application with dozens of teams that are working on the same code base. Some pages are not touched for months since some work on them has been finished. And if some of the developers will break ui-kit it will affect all the pages, but because of the large application this change can be missed on this page because it is "canned". Yes, this will increase the size of the output bundle as there will be two versions of the same package, but it is trade of to increase stability and make the app more bullet proof.

Seems like this PR should help you achieve what u want: https://github.com/atlassian/changesets/pull/507
It might still require some extra scripting on your part though that would switch away from workspace protocol for certain pkgs

Seems like this PR should help you achieve what u want: https://github.com/atlassian/changesets/pull/507
It might still require some extra scripting on your part though that would switch away from workspace protocol for certain pkgs

@Andarist from first look seems like what I need, thanks 👍

@Andarist from first look seems like what I need, thanks 👍

Close in favor of https://github.com/atlassian/changesets/issues/506

Close in favor of https://github.com/atlassian/changesets/issues/506

Looks like this case https://github.com/atlassian/changesets/pull/507 is not exactly the same.
@Andarist is it possible to specify custom bump tree resolution? If no, does it make sense to introduce it, that will help to cover edge cases.

Looks like this case https://github.com/atlassian/changesets/pull/507 is not exactly the same.
@Andarist is it possible to specify custom bump tree resolution? If no, does it make sense to introduce it, that will help to cover edge cases.

I understand that the issue there is not exactly the same as yours. It should be possible to switch between workspace protocol and regular dependency ranges using a custom script - prior to running Changesets, so it could skip bumping some of the dependencies that would lack the workspace protocol, right?

I understand that the issue there is not exactly the same as yours. It should be possible to switch between workspace protocol and regular dependency ranges using a custom script - prior to running Changesets, so it could skip bumping some of the dependencies that would lack the workspace protocol, right?

@Andarist yes, as a workaround, also in this script i have to detect the changes packages comparing with main branch.
I created a PR to override logic for bumping versions, so now you can handle any edge case.

@Andarist yes, as a workaround, also in this script i have to detect the changes packages comparing with main branch.
I created a PR to override logic for bumping versions, so now you can handle any edge case.


Unable to receive call

When I receive a call, the caller hangs. From the logs it seems like when the call is received, it starts multiple other calls, which somehow don't allow accepting the call. I got the same behaviour when trying to example as well. I am using android 10

@Chinmay-KB did you ever figure out a solution for this?

I didn't continue with this approach. I found making a solution on my own from scratch to be easier than this

Did you implement the solution natively instead or are you using a Flutter bridge?

Everything on native, sadly

Did you implement the solution natively instead or are you using a Flutter bridge? I ask because we are able to get calls to show up perfectly fine when the app is in the foreground, but on the background and terminated states it doesn't work. I wasn't sure if you were also experiencing this issue. We're using FCM to trigger all notifications (CallKeep + Push Notifications) but haven't yet introduced any PushKit functionality (which I feel is what we're maybe lacking)

You must use flutter run --release to install, the default xcode debug mode, you cannot start the app in the state of disconnecting xcode.

@cloudwebrtc we are already doing so. When using PushKit, we get an immediate crash:
_terminateAppIfThereAreUnhandledVoIPPushes

The payload we are using is the one provided in the example

@cloudwebrtc we are already doing so. When using PushKit, we get an immediate crash:
_terminateAppIfThereAreUnhandledVoIPPushes

The payload we are using is the one provided in the example

@ejimenez93 hi sir, were you able to solve this problem now? It's been 9 months.
Any other alternatives?


[TOPI, CUDA] Update cuda softmax schedule for spatial inputs

As pointed out in https://discuss.tvm.ai/t/softmax-is-really-slow/1365/4,
The current cuda softmax schedule is hard coded for 2D inputs (after fully connected layer), so it is super slow on spatial inputs (image segmentation, object detection etc). For (1, 16, 256, 256) input, it generates the following schedule.
// attr [compute] storage_scope = "global"
allocate compute[float32 * 1 * 256 * 256]
// attr [compute] storage_scope = "global"
allocate compute[float32 * 1 * 256 * 256]
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 1
  for (i1, 0, 256) {
    for (i2, 0, 256) {
      compute[((i1*256) + i2)] = -340282346638528859811704183484516925440.000000f
      for (k, 0, 16) {
        compute[((i1*256) + i2)] = max(compute[((i1*256) + i2)], A[(((i1*256) + i2) + (k*65536))])
      }
    }
  }
}
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 1
  // attr [compute.rf] storage_scope = "local"
  allocate compute.rf[float32 * 1 * 1 * 1 * 1]
  // attr [reduce_temp0] storage_scope = "local"
  allocate reduce_temp0[float32 * 1]
  for (ax1, 0, 256) {
    for (ax2, 0, 256) {
      // attr [iter_var(threadIdx.x, Range(min=0, extent=64), threadIdx.x)] thread_extent = 64
      produce compute.rf {
        compute.rf[0] = 0.000000f
        if ((threadIdx.x < 16)) {
          compute.rf[0] = (compute.rf[0] + exp((A[(((ax1*256) + ax2) + (threadIdx.x*65536))] - compute[((ax1*256) + ax2)])))
        }
      }
      // attr [comm_reducer(result=[(x + y)], lhs=[x], rhs=[y], identity_element=[0.000000f])] reduce_scope = reinterpret((uint64)0)
      tvm_thread_allreduce((uint32)1, compute.rf[0], (uint1)1, reduce_temp0, threadIdx.x)
      if ((threadIdx.x == 0)) {
        compute[((ax1*256) + ax2)] = reduce_temp0[0]
      }
    }
  }
}
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 1
  // attr [iter_var(threadIdx.x, Range(min=0, extent=64), threadIdx.x)] thread_extent = 64
  for (i2, 0, 256) {
    for (i3, 0, 256) {
      if (likely((threadIdx.x < 16))) {
        compute[(((i2 + (threadIdx.x*256))*256) + i3)] = (exp((A[(((i2 + (threadIdx.x*256))*256) + i3)] - compute[((i2*256) + i3)]))/compute[((i2*256) + i3)])
      }
    }
  }
}

I updated the softmax schedule so that it works well for 4D and 5D inputs. Since the number of classes is
typically small for these inputs, I simply use injective schedule (i.e., without using shared memory reduce).  Below is the updated schedule with this PR. @vinx13  @merrymercy @eqy please review.
// attr [compute] storage_scope = "global"
allocate compute[float32 * 1 * 256 * 256]
// attr [compute] storage_scope = "global"
allocate compute[float32 * 1 * 256 * 256]
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 128
  // attr [iter_var(threadIdx.x, , threadIdx.x)] thread_extent = 512
  compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))] = -340282346638528859811704183484516925440.000000f
  for (k, 0, 16) {
    compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))] = max(compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))], A[(((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256)) + (k*65536))])
  }
}
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 128
  // attr [iter_var(threadIdx.x, , threadIdx.x)] thread_extent = 512
  compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))] = 0.000000f
  for (k, 0, 16) {
    compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))] = (compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))] + exp((A[(((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256)) + (k*65536))] - compute[((((blockIdx.x*2) + (threadIdx.x/256))*256) + (threadIdx.x % 256))])))
  }
}
produce compute {
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 256
  // attr [iter_var(threadIdx.x, , threadIdx.x)] thread_extent = 512
  for (i0.i1.fused.i2.fused.i3.fused.outer, 0, 8) {
    compute[((((((blockIdx.x*2) + (threadIdx.x/256))/256)*65536) + (((((blockIdx.x*2) + (threadIdx.x/256)) % 256)*256) + (threadIdx.x % 256))) + (i0.i1.fused.i2.fused.i3.fused.outer*131072))] = (exp((A[((((((blockIdx.x*2) + (threadIdx.x/256))/256)*65536) + (((((blockIdx.x*2) + (threadIdx.x/256)) % 256)*256) + (threadIdx.x % 256))) + (i0.i1.fused.i2.fused.i3.fused.outer*131072))] - compute[(((((blockIdx.x*2) + (threadIdx.x/256)) % 256)*256) + (threadIdx.x % 256))]))/compute[(((((blockIdx.x*2) + (threadIdx.x/256)) % 256)*256) + (threadIdx.x % 256))])
  }
}

LGTM, just wondering if it is possible to combine max_elem and expsum kernel, since they have the same thread extent

@vinx13 please https://docs.tvm.ai/contribute/code_review.html#approve-and-request-changes-explicitly

@vinx13 ok, I'll update this pr to fuse max_elem and expsum.

@vinx13 I'm getting an error at compute_at below. max_elem should be obviously the producer of expsum. Do you have any idea why?
softmax = outs[0]
expsum = softmax.op.input_tensors[2]
max_elem = expsum.op.input_tensors[1]

axes = expsum.op.axis
fused = s[expsum].fuse(*axes)
bx, tx = s[expsum].split(fused, factor=num_thread)
s[max_elem].compute_at(s[expsum], tx)

tvm/src/schedule/bound.cc:168: Check failed: found_attach || stage_attach.size() == 0 Invalid Schedule, cannot find the producer compute(compute, 000001AF5B4B8070) along the loop nest specified by compute_at of consumer compute(compute, 000001AF5B4B6970)

hmm, it's weird that we are seeing compute(softmax, 0x31e14f0) instead of expsum. Besides, max_elem IS one of the producers to softmax.

@masahi I think it is currently impossible to produce two tensors in one kernel. Let's keep using schedule_injective for now

Yeah I just realized that, since max_elem is fed into both expsum and normalize, we can't fuse max_elem into expsum.

Did you check the performance regression on resnet-18 or mobilenet?

Our model has one large softmax input previously: maxelem is [1, 204800, 1],   expsum is [1, 204800, 1] too. Could this schedule can handle this situation or not?
My previous method is to fuse all axies and do split like this (for max_elem / expsum / softmax):
    max_threads = tvm.target.current_target(allow_none=False).max_num_threads
    n, c, hw = s[max_elem].op.axis
    fused = s[max_elem].fuse(n, c, hw)
    fused, vec = s[max_elem].split(fused, 16)
    bb, tt = s[max_elem].split(fused, max_threads)
    s[max_elem].bind(bb, tvm.thread_axis("blockIdx.x"))
    s[max_elem].bind(tt, tvm.thread_axis("threadIdx.x"))
    s[max_elem].vectorize(vec)

My test environment is Mali-G71. The execution time could be from 900ms to 5ms.
Maybe this PR is better way, but I haven't tested it. But this workload should be one good test case for you.

@merrymercy @FrozenGene This PR applies to 4D or 5D inputs only. For 2D inputs, there is no change and the same existing schedule will apply.

Thanks, @masahi @merrymercy @FrozenGene @vinx13 , this is now merged


[WFLY-16606] Convert testsuite/integration/manualmode to the jakarta.* namespace

https://issues.redhat.com/browse/WFLY-16606
This incorporates a couple other PRs:
#15776 https://issues.redhat.com/browse/WFLY-16636 (this actually optional)
#15778 https://issues.redhat.com/browse/WFLY-16635

@darranl Rebased on top of #15797, the latest sync branch.


Want to Migrate all branch to Git Repository

Hi,
Not able to Migrate all branches from TFVC to git repo. Only root branch-associated branches are getting migrated to Git.
Please enable the above scenario as well. Please find below Screenshot attached

AFAIK this should work. Perhaps try cloning with --branches=all ?

tried cloning with --branches=all only Trunk-Beta, Trunk-Old & Trunk-UI are getting Migrated to GIT.  But not others like Production old & Production UI

Please enable the above scenario as well.

This project is an open-source project and live only with contributions (no-one is paid to work on it)
This case should be supported (from what I could remember) and as you are the one that has the problem, please investigate and do a pull request to provide a fix.
Thanks a lot in advance.

Able to resolve on our own


The mixin is set to only work on singleplayer

In the mixins.json, MixinFarmlandBlock is placed within the client section, so it will only work on singleplayer. I'm fairly certain it was put there by accident and was meant for the currently left empty mixins section instead to run on both singleplayer and on a server.
For now if somebody is having issues running this on a server, you should just be able to open up the mod jar in your archive explorer of choice and open the "trampledisablerfabric.mixins.json" file, and then just swap the mixins and client section (The empty client section isn't even needed, so you could delete that if you want to save that precious less than a kilobyte of storage space).

Should be fixed now, thanks for your report.


Tasks/#1 setup helm chart repo

Please do the following before you run my scripts in travis-ci:

Setup your gcs for both of stable and incubator repository that should follow the guide
https://github.com/helm/helm/blob/master/docs/chart_repository.md#hosting-chart-repositories

Create a service account in Google IAM and get the credential of gcs and save it to json file as name "credential.json". this service account should have the role as "Storage Object Admin"
https://cloud.google.com/storage/docs/authentication#generating-a-private-key

encrypt your "credential.json" by follow
https://docs.travis-ci.com/user/encrypting-files/

Copy the output with openssl and using it later.

Create the slack secure channel with travis and save the secret key

update the your openssl command and secret key to file .travis.yaml

Finally, you can commit and push your code to github to test travis-ci and check your helm chart repository
connect #1

@phucvdb you need merge into 1 commit!

@phucvdb You can use git squash to merge many commit into 1 :D


Issue: "Couldn't upload dataset. TypeError: NetworkError when attempting to fetch resource" when trying to upload a csv dataset

Description:
When attempting to upload a CSV dataset to the langsmith web ui using the provided functionality, the process fails with the error message "Couldn't upload dataset. TypeError: NetworkError when attempting to fetch resource". This error prevents the successful submission of the dataset, hindering progress on data analysis or processing tasks.
Steps Taken:
Ensured that the CSV file is correctly formatted and contains valid data.
Checked the network connectivity to ensure there are no issues with internet access.
Attempted to upload the dataset multiple times, but consistently encountered the same error.
Reviewed relevant documentation or support resources provided by the service, but did not find a solution to the issue.

Expected Outcome:
The dataset should be successfully uploaded to the server without encountering any errors, allowing for further data analysis or processing tasks to proceed.
Additional Information:
Tried in Python following this guide as well https://docs.smith.langchain.com/evaluation/faq/datasets-client#create-dataset-from-csv with the following error trace:
urllib3.exceptions.SSLError: EOF occurred in violation of protocol (_ssl.c:2384)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\requests\adapters.py", line 486, in send
resp = conn.urlopen(
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\urllib3\connectionpool.py", line 877, in urlopen
return self.urlopen(
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\urllib3\connectionpool.py", line 877, in urlopen
return self.urlopen(
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\urllib3\connectionpool.py", line 877, in urlopen
return self.urlopen(
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\urllib3\connectionpool.py", line 847, in urlopen
retries = retries.increment(
File "c:\Users\smarotta\PycharmProjects\edm_categorization\venv\lib\site-packages\urllib3\util\retry.py", line 515, in increment
raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.smith.langchain.com', port=443): Max retries exceeded with url: /datasets/upload (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2384)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\Users\user\PycharmProjects\edm_categorization\main.py", line 32, in
dataset = client.upload_csv(
File "c:\Users\user\PycharmProjects\edm_categorization\venv\lib\site-packages\langsmith\client.py", line 881, in upload_csv
response = self.session.post(
File "c:\Users\user\PycharmProjects\edm_categorization\venv\lib\site-packages\requests\sessions.py", line 637, in post
return self.request("POST", url, data=data, json=json, **kwargs)
File "c:\Users\user\PycharmProjects\edm_categorization\venv\lib\site-packages\requests\sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "c:\Users\user\PycharmProjects\edm_categorization\venv\lib\site-packages\requests\sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
File "c:\Users\user\PycharmProjects\edm_categorization\venv\lib\site-packages\requests\adapters.py", line 517, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='api.smith.langchain.com', port=443): Max retries exceeded with url: /datasets/upload (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2384)')))
Suggestion:
No response

Thanks for raising - we'll investigate.


feat: Added docker pip cache support for macOS

Description
Allows the docker_pip_cache property to work on macOS.
Motivation and Context
Without this, the docker_pip_cache property is hard-coded to be ignored unless the host platform is Linux.
Breaking Changes
No breaking compatibility.
How Has This Been Tested?
Works great on my Mac, using Docker for Mac, and it's got the M1 chip. I don't see or know why macOS was excluded, unless it was just an oversight in ensuring it didn't happen on Windows.
I could see it not working if the intent was to share a pip cache with the host, but that's not what it's doing. It's just creating a separate directory mapped into the container that gets reused between builds. And that's great! But macOS users would benefit from it, too.

I think you are right, it was an oversight during the release. Merging this one.

v2.13.0 has been just released.


i3 doesn't load config

Hi,
I followed the instructions for building from source, and when launching i3 through lemurs, the config file is not loaded. It loads some other config file, and I'm not sure which one is it.

I was able to solve this by adding the -c flag and add the path to the correct config file.


Remove deprecated Ember.K

This PR was generated automatically using ember-k-codemod

@fancyremarker this was closed without merging it for any specific reason?


fix: remove enterprise cloud ToS code for login page

We wait for some time every time when we login, but that ToS is not there. This should speed up the test execution especially in the case of not persisting browser.

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


RPi4 WiFi support

#149
This functionality adds the Wifi support to RPI4.
Additional parameter of SSID is added. Then WiFi is supported instead of eth0 interface. Eth0 is switched off.
Use Wifi config via:
./eden config add default --devmodel RPi4 --ssid WIFISSID
This will be updated in the future to allow all interfaces at once.

LGTM


Using shallow() with vue-class-component - can't get rendered template

Can't get rendered HTML when using shallow:
foo.vue
<template>

{{ title }}

{{ body }}

</template>

foo.spec.ts:
import { shallow } from 'avoriaz';
import Foo from './foo.vue';

describe('foo component', () => {

    it.only('render', () => {
        const wrapper = shallow(Foo, { propsData: { title: 'Foo', body: 'Bar' } });

        console.log(wrapper.element.outerText);
        console.log(wrapper.element.outerHTML);
        console.log(wrapper.html());
    });

});

Output:
undefined
undefined

Maybe I'm doing something wrong?

Sorry, there's a bug with TS at the moment.
I'm not a TS user so it's difficult for me to debug, and I haven't got much time at the moment.
If you'd like to take a look, I'd really appreciate it.
Otherwise, I'll try to fix in a few weeks


[SDK-3926] Treat all transport errors as recoverable

This treats all transport errors as recoverable from the point of view of RTN14d.
The immediate reason for doing this is so that an error of OSStatus 9806 (errSSLClosedAbort) doesn't cause the client to transition to the FAILED state. But, as described in the commit message, this also reflects the broader approach that @paddybyers wants us to take for handling transport errors.
Resolves #1817.

@paddybyers this is pretty much the PR — I've got to pop out shortly and will add a further test when back to check that an arbitrary error does not provoke a transition to FAILED, but feel free to look at the general shape of things beforehand if you want.

Thanks. See https://github.com/ably/specification/issues/171#issuecomment-1795136754.
So if these changes implement that approach, we're good.

As things stand in this PR:

No error that results from the process of establishing a WebSocket connection to Ably is considered fatal.
No WebSocket event (e.g. a closed connection) that occurs after the connection to Ably is established is considered fatal.
I haven't touched the logic regarding what it will do with a ProtocolMessage received from Ably on the realtime transport, which I assume follows the relevant spec points for DISCONNECTED and FAILED messages.

@paddybyers is there more that needs to be done that what I've detailed above?


Segfault during test suite

Not always... sometime
Will try to get a bactrace
OpenCensus Trace: Basic Class Method As Function Test [tests/basic_class_function.phpt]
OpenCensus Trace: Basic Function Test [tests/basic_function.phpt]
OpenCensus Trace: Basic Method Test [tests/basic_method.phpt]
OpenCensus Trace: Clear Traces [tests/clear_traces.phpt]
OpenCensus Trace: Nested spans [tests/nested_spans.phpt]
OpenCensus Trace: Basic Class Static Method [tests/static_method_test.phpt]
OpenCensus Trace: Trace Context [tests/trace_context.phpt]

All with Termsig=11

This seems to happen when "pcs" extension is loaded, but also on 32-bit arch (no other extension installed)
/cc @flaupretre FYI

Some build warning also have to be fixed, as this can raised very strange issues
/dev/shm/BUILD/php-pecl-opencensus-0.0.1/ZTS/opencensus_trace.c:655:5: warning: implicit declaration of function 'opencensus_trace_span_minit' [-Wimplicit-function-declaration]
     opencensus_trace_span_minit(INIT_FUNC_ARGS_PASSTHRU);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/dev/shm/BUILD/php-pecl-opencensus-0.0.1/ZTS/opencensus_trace.c:656:5: warning: implicit declaration of function 'opencensus_trace_context_minit' [-Wimplicit-function-declaration]
     opencensus_trace_context_minit(INIT_FUNC_ARGS_PASSTHRU);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I confirm, test suite passes now everywhere
Thanks


notify-conflicted-branch: push notification about merge conflicted branches

New operation notify-conflicted-branch will search through active MRs from GitLab.
active: is open && not merged yet
Foreach MR, heybot will check its merge_status. If MR can not be merged because of a conflict with target branch (mostly master), it'll push a notification to Mattermost channel about the situation.
GitLab has an internal e-mail notification:

.. If an open merge request becomes unmergeable due to conflict, its author will be notified about the cause.  ..

But it only notifies the  author. I need more visible notification which can be seen by the entire team. (reviewers and watchers of the MR)
GitLab's e-mail notification seems to be sent once. Documentation is not clear about this. I want to send more notifications about conflicted MRs until they're maintained.
GitLab's feature is released at version 11.0. heybot's functionality will also work with lower versions GitLab.

Also there is another problem with GitLab's e-mail notification 👉 here
Because of this MRs are waiting unmaintained and when a reviewer visits MR for review > test > merge, notification is sent to author of MR. It's late!


Still uses CPU

It looks nice, I am trying to install with pip:
pip install hydra-core tensorflow[and-cuda] soundfile tqdm scipy
python inference.py inference.audio="r:\9.mp3"
it works with the CPU (slow) although I have a GPU and tensorflow[and-cuda] is installed. What am I missing?
Or, is the GPU stuff training-only?

Inference should work in GPU. I guess there is some version issue with the CUDA and/or tensorflow installations.

I found the issue, tensorflow doens't anymore support native CUDA gpu on Windows :(


:ref enforces select-in strategy for 1:m relationships

Describe the bug
With joined strategy:
const site = await orm.em.fork().findOneOrFail(Site, { id: 1 }, { populate: ["matches:ref"] });

[query] select "s0".* from "site" as "s0" where "s0"."id" = 1 limit 1 [took 1 ms, 1 result]
[query] select "m0"."id", "m0"."site_id" from "match" as "m0" where "m0"."site_id" in (1) [took 1 ms, 12 results]

could be some strategy override, there are places where select-in is enforced (e.g. because of cycles or populate: * and recursion)

Reproduction
Not needed.
What driver are you using?
pg
MikroORM version
v6
Node.js version
20
Operating system
Linux
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

Many to many seems to be working:
const sports = await orm.em.fork().find(Sport, { id: 1 }, { populate: ["sites:ref"] });

[query] select "s0".*, "s1"."sport_id" as "s1__sport_id", "s1"."site_id" as "s1__site_id" from "sport" as "s0" left join "site_sports" as "s1" on "s0"."id" = "s1"."sport_id" where "s0"."id" = 1 [took 1 ms, 2 results]

But one to many still doesn't:
const site = await orm.em.fork().findOneOrFail(Site, { id: 1 }, { populate: ["matches:ref"] });

[query] select "s0".* from "site" as "s0" where "s0"."id" = 1 limit 1 [took 1 ms, 1 result]
[query] select "m0"."id", "m0"."site_id" from "match" as "m0" where "m0"."site_id" in (1) [took 1 ms, 12 results]

Not supporting ref for one to many would be fine, but we should either error out when used or take the standard path which leads to the default join strategy.

I guess we should just support it the way it should work for 1:m too - doing a partial join selecting only the PK of the target. That's what the user wants based on the query, and we can easily do that (lets put aside whether is a good idea or not for the user, it still has some value to select just one column instead of everything).


[Feature request] a twitch icon for linking your stream

In the set of social links parameters, an entry for twitch your stream could be cool.

I added Twitch icon.
Update the theme first and you can use it like this
params.toml
[socialOptions]
...
twitch = "url"
...


fix: layout shift on docs

Closes #738
✅ Checklist

[x] I have followed every step in the contributing guide (updated 2022-10-06).
[x] The PR title follows the convention we established conventional-commit
[x] I performed a functional test on my final commit

Changelog
Prevent applying of global transitions
Remove transition duration for Theme Toggle

Screenshots
Before:
https://user-images.githubusercontent.com/3381481/202189087-f8749ba9-b495-475d-a5aa-45a96d76ad31.mp4
After:
https://user-images.githubusercontent.com/3381481/202189122-f3705922-c9f7-4067-bef2-c20e48eb18b1.mp4
Comments
I could only replicate the issue seen on the Docs when running pnpm build and pnpm preview from /www
For reasons beyond my small brain, I could not replicate with pnpm build:www running from root.
💯

this is how it looks without the transition

Oops, yep
I've changed it to use transition-colors instead; unless theres other transitions on body that I'm missing context on

There's still flashing

There's still flashing

Yeah of course cause its not an SPA

There's still flashing

Yeah of course cause its not an SPA. It's not shifting though which is a good thing

the theme toggle and navelements doesn't flash like that on the prod versino

Prod:

Oh interesting. I guess we have to choose between layout shifting and flashing

Flashing can prob be fixed later, its less annoying than the layout shift so this is good for now


WIP: Aerogear 8375 adding ui header

Motivation
https://issues.jboss.org/browse/AEROGEAR-8375
What
Adding container folder with header container file
Adding patternfly and router dependencies
Adding router to App with two routes - overview - detailed App View
Why
See JIRA
Verification Steps
Start the Application
The following should be visible (so far):
-> Header with Mobile Security Service text to the left
-> Username and user icon to the right side
-> Dropdown to Logout which redirects to oauth/sign_in
-> Which in turn redirects to Overview (for now at least)
-> Base View for App Detailed View
-> Navigation should also work if you manually enter /apps/someid
See Image

Checklist:

[x] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

Coverage decreased (-1.2%) to 63.603% when pulling 2a1c68be833d7cf7fa238e9690df83a238b708cc on laurafitzgerald:AEROGEAR-8375-adding-ui-header into aeebd9ce8fa0b3d218acbd504edc8ee2b0e08520 on aerogear:master.

Closing this pr in favour of a fresh pr. There is duplication across some and we are also moving to PF4 which means the code may change some. cc @davidffrench @damienomurchu


Solution Fails to Deploy

Solution fails to deploy and doesn't give a great error, it fails on the nested template automation.json {
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n    "message": "The resource operation completed with terminal provisioning state 'Failed'."\r\n  }\r\n}"
}
]
}
]
}
}

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

ID: 225c9d05-83dd-b006-0025-3753f5ab25bf
Version Independent ID: 9eecef0c-b1cb-1136-faf7-542214492096
Content: Start/Stop VMs during off-hours solution
Content Source: articles/automation/automation-solution-vm-management.md
Service: automation
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@RyanLWilliams Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@RyanLWilliams Thanks for reaching out.. I have tested the deployment multiple times against a few subscriptions and I am not having any issues deploying the solution.  There are two parts to the deployment, alert creation and then all the automation account tasks.

One way to see where the error is is looking at Deployments under Settings from the resource group you tried to deploy to. The part of the deployment you mention failing has numerous tasks that run so it is hard to pinpoint which might be failing.

If you continue to have problems I suggest you reach out to support.. As the solution works and the document is up to date with the solution I am going to ask that this issue be closed. #please-close

@RyanLWilliams We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

I'm experiencing the same thing. Template deployment fails with a cryptic "Conflict" error message.
Not sure if the original owner ever resolved the issue, but apparently the issue might still exist.

Same. Too bad it doesn't say what conflicts with what.

Can't remember what it was but was only using it in my Dev/Tests environment. I find most customers in real-world scenarios have something more specific which we deliver via Azure Automation Runbooks and looking up a resource tag value to make sure VMs are periodically checked for being in a Running state or Stopped state in-line with business hours

Same here. Only "conflict" which doesn´t give no info about what is the problem... anyone found a solution?

I have the same problem any solution..

I encountered what I suspect to be the same issue and in my case think it was due to the issue described in this stackoverflow article?
In the article Brando Zhang explains he thinks the issue is because the site extension Microsoft.ApplicationInsights.AzureWebSites is canceled halfway through execution because some of the site's appSettings are changed during the setup.
MPavlak suggested splitting the ARM deployment into a few separate batches to avoid this issue.
I avoided it by running the same ARM deployment multiple times (with no change the the template in-between) but waited 10 minutes between script executions.
The first time I received the same error and the second time it was fine.
Hope this helps someone!


Unique MEM_ID bug.

Hi, I sent code to your private email.

Thanks for reporting! Fixed in commit ffbb4e9.


Add test for unexpected application termination notifications

In #10 @arpadzalan was looking for a way to assert that some process dies in order to terminate the test. This adds a test for an unexpected Application Notification.

lgtm


1.2.x spelling

Looks great to me, please feel free to merge.
We should pick to other branches too, especially master, right? In general the standard workflow is to fix master first then cherry-pick to stable branches so we are sure that we don't miss important fixes in master and issues resurface.

ah, I see you have 1.1.x in #202

Yeah, for the spelling changes I just did them as mostly separate commits rather than cherry picking.  It was just easier that way.


Update Makefiles to build 32-bit Ferret on 64-bit machines

Reported by karl smith on 22 Apr 2011 17:43 UTC
Update the Makefiles for Ferret to build the 32-bit version on a 64-bit machine (using the -32 flag).
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1843

Modified by karl.smith on 26 Aug 2011 16:30 UTC


volatile gpu-util=0% when training

here are the settings in https://github.com/HRNet/HRNet-Facial-Landmark-Detection/blob/master/experiments/wflw/face_alignment_wflw_hrnet_w18.yaml
GPUS: (0,1,2,)
WORKERS: 33
PRINT_FREQ: 3
...
I didn't change other options
as showed in the picture above, the gpus 0,1,2 I used for train hrnet got 0% usage
How could that happen, is it because too much time is spent on processing data with the cpu

Preprocessing takes too much time. It's just a snap by using nvidia-smi. when using watch , it 's not always zero.


Support potentially missing source posting tags table

Fixes https://github.com/fivetran/dbt_lever_source/issues/4

@fivetran-kristin Thank you for the feedback! I have made the requested changes


Errors in CTSWorldAPIIntegration.cs

I am using CTS 1.8.0 and when I add WorldManager v0_10 0901 I get these errors.
Assets\CTS\Scripts\CTSWorldAPIIntegration.cs(24,40): error CS1061: 'CTSTerrainManager' does not contain a definition for 'RegisterAllShaders' and no accessible extension method 'RegisterAllShaders' accepting a first argument of type 'CTSTerrainManager' could be found (are you missing a using directive or an assembly reference?)
and
Assets\CTS\Scripts\CTSWorldAPIIntegration.cs(24,40): error CS1061: 'CTSTerrainManager' does not contain a definition for 'RegisterAllShaders' and no accessible extension method 'RegisterAllShaders' accepting a first argument of type 'CTSTerrainManager' could be found (are you missing a using directive or an assembly reference?)
I commented out the offending lines and all seems to work as expected.

I don't think this is maintained anymore, two years since last commit, nothing on asset store.


Warning after updating to js-controller 3.2.7

State "tesla-motors.0.info.connection" has no existing object, this might lead to an error in future versions
Regards,
xengosam

Yes, this warning I have for a long time now. My ioBroker is running with 3.2.16 at the moment.
2021-02-17 09:55:15.754 - warn: tesla-motors.0 (1323) State "tesla-motors.0.info.connection" has no existing object, this might lead to an error in future versions
Thank you for the adapter. It is working fine without errors!

fixed


Stop Python 2.7 support

From the next version, tofu will not support python 2.7 anymore
This means we can remove the python 2.7 builds in travis.yml

There's already a branch with this in mind see SHA: 7e321f6c3d49303ecd05cbbc8ef471934e970c81

Ok, but please next time open a dedicated issue and name the branch accordingly, it easier to follow.
Do you want to consider this issue as being associated to the branch you mention then ?

done

Just to preserve the workflow:

issue labelled "fixed in devel" when the PR accepted
issue closed only when solved in the last release or when it was opened by mistake (e.g.: the bug does not really exist...)

This way we'll easily get a list of all additions to a release simply by collecting all issues labelled "fixed in devel", and we'll close them all after the release is done
=> I re-open the issue and label it "fixed in devel", to keep track as a good practice


Store and show time when container was last started

From the lxc list command, we have a new column key l, that shows the LAST USED AT field. The column will be blank of container was never started or lxc client is connecting to an older lxd daemon whose API response doesn't include a last_used_at field.

API documentation was updated. Please let me know if I missed something
DB schema and migration scripts were updated. Tested by creating DB with older lxd and then running newer lxd, which updated schema and continued functioning properly.
Tried to keep naming scheme of JSON, DB, and struct fields consistent with existing image last use field

One tricky part with adding this feature was what date should we show if a container has not been started yet. In original issue it was suggested to use 0 EPOCH (1970-01-01T00:00:00Z). However, this is not the 0 value of time.Time, so when the field is missing in an API response, json.Unmarhall will leave the LastUsedDate field at its zero value, which is "0001-01-01T00:00:00Z". After json.Unmarshall, we could iterate through every ContainerInfo object and set to 0 EPOCH, but this did not seem like an optimal thing to do.
Because of this, we currently have this inconsistency:
lxc list --format json to an older remote will show last_used_at with value 0001-01-01T00:00:00Z.
lxc list --format json for a non-started container on a current lxd version will show last_used_at with value 1970-01-01T00:00:00Z
Let me know if this is OK, or if we want to make all last_used_at dates either 1970-01-01T00:00:00Z or 1970-01-01T00:00:00Z for consistency.
Closes: https://github.com/lxc/lxd/issues/1958
Below are some manual tests to show sample usage:
lxc list --format json test:
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc init alpine last-used-at-test
Creating last-used-at-test
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc list last-used-at-test  --format json | jq -r '.[].last_used_at'
1970-01-01T00:00:00Z
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc start last-used-at-test
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc list last-used-at-test  --format json | jq -r '.[].last_used_at'
2016-06-05T05:06:13.052313996Z

Multiple container test:
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc init alpine t1
Creating t1
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc init alpine t2
Creating t2
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc init alpine t3
Creating t3
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc list --columns nl
+------+--------------+
| NAME | LAST USED AT |
+------+--------------+
| t1   |              |
+------+--------------+
| t2   |              |
+------+--------------+
| t3   |              |
+------+--------------+
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc start t1 t2 t3
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc list --columns nl
+------+----------------------+
| NAME |     LAST USED AT     |
+------+----------------------+
| t1   | 2016/06/05 05:09 UTC |
+------+----------------------+
| t2   | 2016/06/05 05:09 UTC |
+------+----------------------+
| t3   | 2016/06/05 05:09 UTC |
+------+----------------------+

Running against older lxc:
vagrant@vagrant:~/go/src/github.com/lxc/lxd$ lxc list --columns nl
+------+--------------+
| NAME | LAST USED AT |
+------+--------------+
| a1   |              |
+------+--------------+

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

You should also modify "api_1.0.go" and add a "container_last_used_at" entry in api_extensions so clients can detect the availability of this feature.

I did... Do I need to add it somewhere else?
https://github.com/lxc/lxd/pull/2084/commits/22e53578e375dc3d54bc9b0ff54cc22ba3d1173b
https://github.com/ctrlrsf/lxd/blob/31d1e81e09bb401f453971fd504473eb8e3d4dee/lxd/api_1.0.go#L58

Doh, must have missed it. Yeah, you need to move that line to the end of the list.

Thanks! Moved it to end of that list and also added some documentation about new field to api_extensions.md.

jenkins: test this please

jenkins: test this please

(sorry for the spam, I'm trying to workaround a jenkins bug)

jenkins: test this please

Ok, so that jenkins failure is correct, your change regresses "sudo -E go test -v ./..."

No problem re: the spam, thanks for the running the Jenkins test. I found I was missing a commit to initialize LastUsedDate in containerCreateInternal method. Both sudo -E go test -v ./... and sudo -E ./main.sh are passing on my local. Lets see what Jenkins thinks.
Previously failing test:
=== RUN   TestContainer_LoadFromDB
c=&{2 0 {63600858295 0 0x12c5120} {62135596800 0 0x12c5120} false 3 testFoo false map[volatile.eth0.hwaddr:00:16:3e:2e:8d:87 volatile.eth0.name:eth0 volatile.last_state.idmap:[] security.privileged:true] map[eth0:map[type:nic nictype:bridged parent:unknownbr0] root:map[type:disk path:/]] false map[security.privileged:true volatile.eth0.hwaddr:00:16:3e:2e:8d:87 volatile.eth0.name:eth0 volatile.last_state.idmap:[]] map[root:map[type:disk path:/] eth0:map[type:nic nictype:bridged parent:unknownbr0]] [default] 0xc82007c9c0 0xc8201b0b40 <nil> 0xc82048ec00}
c2=&{2 0 {63600858295 0 0x12c5120} {62135596800 0 0x12c5120} false 3 testFoo false map[volatile.eth0.name:eth0 volatile.last_state.idmap:[] security.privileged:true volatile.eth0.hwaddr:00:16:3e:2e:8d:87] map[eth0:map[nictype:bridged parent:unknownbr0 type:nic] root:map[type:disk path:/]] false map[volatile.eth0.name:eth0 volatile.last_state.idmap:[] security.privileged:true volatile.eth0.hwaddr:00:16:3e:2e:8d:87] map[root:map[path:/ type:disk] eth0:map[nictype:bridged parent:unknownbr0 type:nic]] [default] 0xc8201ad290 0xc8201b0b40 <nil> 0xc82048ec00}
--- PASS: TestContainer_LoadFromDB (0.03s)

jenkins: test this please


Footnote - podcast page

◦	There’s not a link back from the footnote content (“Numeronym”) to the footnote link (“*”).
◦	The asterisk link could have a better link name.

Fixed


Feature request: Embeddings etc.

when autocompleting embeddings, show embedding version or sort by version, so 2.X vs 1.X and when then selecting the autocomplete delete the <> from front and back :), thanks great embed!

It was a bit hacky to get working, but I think it's functional now.
The default list includes both types since I can't test during completion which type of model the user currently uses, but you can prefix the search with v1/v2 to only show those types, as seen below:
https://user-images.githubusercontent.com/34448969/210187734-c2e2292c-7649-4df6-b787-2b2195ab3a29.mp4
I wait for the webui to load the embeddings to then get their version info, but if the model doesn't load any (e.g. a v2 model, but the user has no v2 embeddings, or the same with v1), I can't test what version they are and default to v1 since it's more common.
I could theoretically check them manually, but that would mean embeddings being loaded twice which would increase startup time, so I compromised here.

This doesnt work for me somehow!

https://github.com/tkalayci71/embedding-inspector
here this guy here knows what version the embeddings are at all times!
if that helps somehow

Your webui needs to be updated to use it since my method relies on info only introduced yesterday. I do the same as the other guy, compare the vector sizes. Only difference being that I wait for the webui to load them itself to prevent duplicate loading.


unable to read text from a table using page object - undefined method `text' for 0:Fixnum (NoMethodError)

browser.table(:id => "resultList").rows[1][1].text
I am able to see the output of the above in irb and when I do a puts also its getting me the result.
When I am using the pageobject for getting the row count, I am able to get the value as follows
row_count = site_search_results_table_element.rows
when I use the following :
site_search_results_table_element.rows[1][1].text inside the class for e.g :
class VMI_Create_order_Find_sitePageObject
include PageObject
text_field(:keyword_search,:name => "searchText")
button(:search,:value => "SEARCH")
table(:site_search_results_table,:id => "resultList")
def locate_site(site_name)
row_count = site_search_results_table_element.rows
puts "row count : #{row_count}"
puts "#{@browser.table(:id => "resutList").rows[1][1].text}" # this works fine
puts "#{site_search_results_table_element.rows[1][1].text}" # I get the following error :undefined method `text' for 0:Fixnum (NoMethodError)
for row_index in 1..row_count - 1
site_name_value = site_search_results_table_element.rows[row_index][1].text
if (site_name_value.eql?(site_name))
	return true
end

end
return false
end
end
I am not sure as to what the issue is, in earlier versions of watir I did not see this issue, any help is appreciated.

The code you need to have is site_search_results_table_element[1][1].text.  In page-object the rows method returns the number of rows.  The {name}_element method returns an instance of the Table class which has the indexing methods directly.


Do we support defining pseduo class with this library?

As the title, there is no documentation i can find about how to use pseduo class in stylist-rs.

Yes, this is supported. E.g. in a styled component
let hover_class = css!(
  :hover {
      color: blue;
  }
);

You can think of all selectors in a css! block to implicitly mention "the currently generated class", so the above results in css like
.stylist-style-0:hover {
    color: blue;
}

being mounted the <head> and using the hover_class will attach the class stylist-style-0 to your component.

Can you give a short description what you are trying to achieve and which pseudo class you would like to see, so I can provide a tailored example?


Migrate to new story indexer API

We've been working on a new story indexer API for some time, that is more official and public and actually documented. The API currently used by this addon was "internal" and undocumented. It has officially been deprecated in Storybook 7.5.0 in favor of the new API.
The new API is documented here: https://storybook.js.org/docs/svelte/api/main-config-indexers
I suggest we migrate this addon to the new API for multiple reasons:

Remove the deprecation warning for users on Storybook >7.5.0
Be ready for Storybook 8.
Provide feedback to the API. We might uncover different usage patterns here that would warrant a change in the API.

The new API is not very different from the old one so migrating should hopefully be straight forward. The biggest difference is that an indexer now doesn't return an instance of CSFFile (in this case { meta: ..., stories: ...}) but rather a list of more detailed IndexInput, allowing the indexer to specify some properties that was not exposed before.
The documentation also details how transpiling CSF files is necessary etc. but that should already have been taken care of in this addon as that remains the same.
The deprecation warning is implemented in way that allows addons to support both the new and old API simultaneously if they want to. Storybook 7.4.0+ will use the experimental_indexers if found and fallback to storyIndexers with a warning. Older versions will use storyIndexers with no warnings.
The plan is to completely remove support for the old API in Storybook 8.0.
This API is behind an experimental flag right now until we feel like the API is stable It's not because it could potentially be removed since Storybook Core uses it for all story indexing internally.

:rocket: Issue was released in v4.0.10 :rocket:

:rocket: Issue was released in v4.0.10 :rocket:

:rocket: Issue was released in v4.0.10 :rocket:


Support for Azure CNI Cilium

Describe your changes
Support for Azure CNI - Cilium
Azure CNI powered by Cilium in now generally available.
Cilium is a comprehensive networking solution that combines the control plane of Azure CNI with the dataplane capabilities of Cilium.
Issue number
Closes #397
Checklist before requesting a review

[x] The pr title can be used to describe what this pr did in CHANGELOG.md file
[x] I have executed pre-commit on my machine
[x] I have passed pr-check on my machine

Thanks for your cooperation!

@microsoft-github-policy-service agree

Please run the tests locally as described in the Readme:
https://github.com/Azure/terraform-azurerm-aks#pre-commit--pr-check--test


cannot transfer to region EU-west-2

The script is great. It works on the US regions, but when trying to copy from EU-west-1 to EU-west-2, it complains "migrate.py:24 [ERROR] please make sure that you set your EC2 credentials and that they are correct"
EU-west-2 is a new AWS region.  could it be that it is not declared somewhere?

hey @nicolasbriant, thanks!
it seems like your problem might indeed be related to the version of boto that I have in the requirements.txt file. I can't really test this at the moment, but if you try upgrading to at least v2.45.0 it might fix your issue since that's when they added support for eu-west-2


feat: skip all the tests in short mode if they use Celestia testnode

Overview

Skip all the tests when running in short mode if they use Celestia testnode because of the race conditions and not to have to skip each one separatly.
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #155 (69752aa) into main (27f6375) will increase coverage by 5.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
+ Coverage   45.90%   51.66%   +5.76%
==========================================
  Files          15       16       +1
  Lines         952      991      +39
==========================================
+ Hits          437      512      +75
+ Misses        466      423      -43
- Partials       49       56       +7

Impacted Files
Coverage Δ

cmd/qgb/helpers/parse.go
100.00% <0.00%> (ø)

p2p/querier.go
80.23% <0.00%> (+0.23%)
:arrow_up:

p2p/dht.go
68.29% <0.00%> (+6.47%)
:arrow_up:

orchestrator/orchestrator.go
15.76% <0.00%> (+15.76%)
:arrow_up:

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

In this repo, and others such as Celestia-app, we're running the tests with -race -short flags when running race.
This PR skips any test that has the -short flag if it uses the tesnode (because of the race conditions happening), by skipping them when creating the network instead of having to do it in every test.
Let me know if im not clear enough to reformulate


[Wiki Downtime] Wiki Site down for hardware maintenance

The wiki & associated services will be down for hardware maintenance (making sure everything's okay inside, cleaning out dust etc)

time flew by so i've updated it to 16:00 BST

Should be coming back online now 👍


SSL Pinning not working

Hi,
Please help me out.
I'm following the docs and have implemented SSLPinning with the following parameters. But still when I check using Burp Suite trusted certificate in my phone, the app is still loading. If SSL Pinning is in place it should throw error right ? I'm not sure what I've done wrong.
Here's my code inside Security.swift :
class func startSSLPinning() {
        let trustKitConfig = [
            kTSKSwizzleNetworkDelegates: false,
            kTSKPinnedDomains: [
                "CLIENT_DOMAIN_NAME": [
                    kTSKIncludeSubdomains: true,
                    kTSKEnforcePinning: true,
                    kTSKPublicKeyHashes: [
                       publickKeyHash1,
                        backupKeyHash
                    ],]]] as [String : Any]

        TrustKit.initSharedInstance(withConfiguration:trustKitConfig)
    }

In my AppDelegate didFinishLaunchingWithOptions :
       Security.startSSLPinning()
In my network layer, I'm implementing the pinning validator code as per the documentation inside didReceiveChallenge.
This method is visible inside a eventMonitor type class of Alamofire.
final class Logger: EventMonitor {
      func urlSession(_ session: URLSession, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
          if TrustKit.sharedInstance().pinningValidator.handle(challenge, completionHandler: completionHandler) == false {
              completionHandler(.performDefaultHandling, nil)
          }
      }
}

and my session is defined so :
   let session = Session(eventMonitors: [ Logger() ])
I know something is missing, but not exactly sure what. It could be some issue with delegate not getting set right, or I need to implement more methods? Please help.

I was able to resolve this issue by creating a customSessionDelegate class for SessionDelegate and overriding the delegate function like this :
class CustomSessionDelegate: SessionDelegate {

    override func urlSession(_ session: URLSession,
                         task: URLSessionTask,
                         didReceive challenge: URLAuthenticationChallenge,
                         completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
         // Call into TrustKit here to do pinning validation
         if TrustKit.sharedInstance().pinningValidator.handle(challenge, completionHandler: completionHandler) == false {
             // TrustKit did not handle this challenge: perhaps it was not for server trust
             // or the domain was not pinned. Fall back to the default behavior
             completionHandler(.performDefaultHandling, nil)
         }
     }
}

and then assigned this CustomSessionDelegate as my sessionDelegate when creating the session :
   let session = Session(delegate:CustomSessionDelegate(), eventMonitors: [ Logger() ])

@annathomasQB  Would you mind  converting the above override method in objective c, I am not a native guy so help would much appreciated.

@anishtr4
The objective C equivalent for this method is listed at the bottom of Sample Usage of TrustKit. You just need to add the override button if you're planning on adding the CustomSessionDelegate class.


Shorten Github Issues concourse workflow check every period to 15m

Expected Behavior
I would expect that the Concourse pipeline would start deploying within a reasonable time frame after I close the controlling Github issue. Currently this is set to 1h which is far too long to wait in a release day context.
Current Behavior
You have to wait an hour which will not fly during a release or in a crisis.

This change is in. From the docker-packer-pulumi-edx-global pipeline as viewed with get-pipeline:
- check_every: 15m0s
  expose_build_created_by: true
  icon: github
  name: github-issues-applications.edxapp.mitx.ci-post
  source:
    access_token: ((github.issues_resource_access_token))
    auth_method: token
    gh_host: https://github.mit.edu/api/v3
    issue_prefix: '[bot] Pulumi ol-infrastructure-edxapp-application.mitx applications.edxapp.mitx.CI
      deployed.'
    issue_state: open
    issue_title_template: '[bot] Pulumi ol-infrastructure-edxapp-application.mitx
      applications.edxapp.mitx.CI deployed.'
    repository: ol-platform-eng/concourse-workflow
  type: github-issues
- check_every: 15m0s
  expose_build_created_by: true
  icon: github
  name: github-issues-applications.edxapp.mitx.ci-trigger


Failed deployment

 Failed deployment

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

All the steps completed successfully, but still failed

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 11

Versions

Windows 11

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Looking at the error message, it seems that Powershell isn't installed or accessible from the current context (see https://github.com/Azure-Samples/serverless-chat-langchainjs?tab=readme-ov-file#use-your-local-environment for install links).
Does it work if you try to run pwsh from the same terminal you ran the azd up command?

Looking at the error message, it seems that Powershell isn't installed or accessible from the current context (see https://github.com/Azure-Samples/serverless-chat-langchainjs?tab=readme-ov-file#use-your-local-environment for install links). Does it work if you try to run pwsh from the same terminal you ran the azd up command?

No, it did not work. I had to install PWSH and clean up the resource group and purge the Cognitive Service soft delete before doing it again...


The project has not been updated for 4 years. It is recommended to replace it with mainstream Retrofit

The project has not been updated for 4 years. It is recommended to replace it with mainstream Retrofit

I suggest changing to Net


Responsive tablink funcionality needed

Summary
_Dynamically generated tablinks should have facility to have auto overflow

Suppose on a smaller screen tab collection cannot accumulate all the tab links then according to the available width some columns should automatically to be shown under overflow.
For the responsiveness of the UI implementation it is very much required

Hi @MeghnathDas, please follow our issue templates to help provide full information about an issue.
I'm not very clear what you are asking for here, can you please expand and provide full detail about this with clear use cases or reproductions?

@gnomeontherun  I think what @MeghnathDas meant is when there's not enough room for tabs especially in smaller screens, tabs should be placed in an overflow menu.
Example:
The container's width is wider and has enough space to display all buttons:

The container is not wide enough to display all the buttons, so buttons that are not visible in the container's viewport are placed in an overflow menu:

@whizkidwwe1217 is right here.

I'm also looking for this

We need some use cases so we could start thinking about the design and accessibility,
Hiding things inside menus and sub-menus could be very hard to communicate with the user.
Some issues that I find here are:

what is the minimum size that this should happen?
how we gonna address the hidden elements and communicate that there are more items to be shown?
keyboard navigation?

and so on.

Thanks for your reply.
Here are the points:

Since the tab headers have some size, it would be great if the size can be calculated respected to parent container's width and determine if the tab headers are going to be overflown. So the minimum size should be dynamically calculated as per the available parent width.

A three-dot menu can be shown at the right to indicate the overflow(hidden) items. Hidden elements can be shown on-click of the three-dot menu.

Keyboard navigation is not necessary


Allow updating from multiple cluster

It's not possible to update from multiple clusters like:
UPDATE CLUSTER:['de_customer'] SET Points= 0

but we can select/traverse/Find References from multiple clusters https://github.com/orientechnologies/orientdb/issues/1222
select from cluster:[a,b,c]

for consistency and full support of orientdb cluster strategy it should be possible to update from multiple clusters. Thanks!
@luigidellaquila @lvca

Totally my fault :) It's of course possible. You must not quote clusters.
UPDATE CLUSTER:[de_customer] SET Points= 0


Simplify udpate_basket task.

Coverage increased (+0.07%) to 92.567% when pulling 1ee2efadeba443ae14b1994a885d5989ae523339 on akatsoulas:simplify-subscribe-task into 2d790cdcb4fd99f11fb6035fc40afd764d05a869 on mozilla:master.

Please fix typo in commit message/PR title

Instead of having these endless if/else/elif cases i suggest we wrap all the basket calls to a helper method that takes as arguments:

basket method
basket method args
task

and does the heavy-lifting of celery retries.

Closing this as it's not built in the right direction. I will open a new one for this.


[Bug]: The addition and deletion of the groups event to users is captured as "group.remove_users" and "group.invite_users"

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The addition and deletion of the groups event to users is captured as "group.remove_users" and "group.invite_users" but here we are adding and deleting the groups not users

Steps To Reproduce
1.Login as admin
2.go to admin setting page
3. go to users tab
4. click on user name
5. first assign some groups to user
6. Now check the log the event is captured as "group.invite_users"
7. now remove the group from user
8. the log is captured as "group.remove_users"
9. but here we are removing groups and adding new groups not the users
Public Sample App
No response
Issue video log
No response
Version
localhost

This is expected behaviour.

Closing the issue as this is a expected behaviour


Expose service account to the testing framework

Closes https://github.com/onflow/cadence-tools/issues/121
Companion PR: https://github.com/onflow/cadence/pull/2505 :heavy_check_mark:
Description
This will enable developers to sign transactions that can send any amount of FLOW tokens, to newly-created test accounts.
import Test

pub let blockchain = Test.newEmulatorBlockchain()

pub let serviceAccount = blockchain.serviceAccount()

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

I will certainly add more test cases :+1: , however, I need a Cadence release that includes these changes (from the companion PR)

@SupunS Added one such test case: https://github.com/onflow/cadence-tools/pull/122/commits/3005dad60081c58172586d4b046b89ce97692053, where the blockchain.serviceAccount() function is used in a Cadence test script.

I have rebased after your latest merge, so the tests should be passing :pray:

@turbolent No worries, I will rebase right now :bow:

Conflicts resolved. Hopefully the tests got our backs :pray:


Is it possible to update the retentionTimeValue of a table after it's been created?

As far as I know, the best way to update the retentionTimeValue would be to drop the table, recreate it with a different time value and then rerun a metadataPush job, but that seems like a lot of overhead just to get Pinot to increase/decrease the retention time.
Would PUT /tableConfigs/{tableName} with the exact same table body but a new retention value work?

Yes, @travis-cook-sfdc. That is possible


Contour not working

I am having some issues when trying to produce a contour plot for tikz.
import matplotlib.pyplot as plt
import pandas as pd
import numpy as np
from matplotlib import cm,colors
import tikzplotlib

max_r = 20
N_vorfs = 500
scalings = np.linspace(0.1, 5.*np.pi, N_vorfs)

X, Y = np.meshgrid(scalings, 2.*np.arange(1, max_r+1)-1.)
Z = np.arange(max_r*N_vorfs).reshape(X.shape)

fig, axs = plt.subplots(2, 1, gridspec_kw={'height_ratios': [3, 1]})
axs[0].contour(X, Y, Z)
print(tikzplotlib.get_tikz_code())
plt.show()

The errors are
Traceback (most recent call last):
  File ".../to_pgfplot.py", line 19, in <module>
    print(tikzplotlib.get_tikz_code())
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/tikzplotlib/_save.py", line 209, in get_tikz_code
    data, content = _recurse(data, figure)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/tikzplotlib/_save.py", line 353, in _recurse
    data, children_content = _recurse(data, child)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/tikzplotlib/_save.py", line 378, in _recurse
    data, cont = _draw_collection(data, child)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/tikzplotlib/_save.py", line 319, in _draw_collection
    return _path.draw_pathcollection(data, child)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/tikzplotlib/_path.py", line 214, in draw_pathcollection
    p = obj.get_paths()[0]
IndexError: list index out of range

Original post

Hi, it may be worth starting with a simpler example. I get this exported (one contour line for data=100 and a known bounding box):
        contours = axis.contour(data, [100], origin='lower',
                               extent=(bbox.xmin, bbox.xmax, bbox.ymin, bbox.ymax),
                               colors='red')
        plt.clabel(contours, inline=1, fontsize=10)


PHP 8.4 compliance

We are currently using the sabre/dav in an open source project and we want to make it fully compliant with PHP 8.4, and we cannot upgrade to sabre/event:^6.0 because sabre/dav is not compatible with it.
If we provide a patch for it, would you accept to integrate it in a new 5.1.5 version ?
There is at least the following deprecation to fix:
Deprecated: Sabre\Event\Loop\instance(): Implicitly marking parameter $newLoop as nullable is deprecated, the explicit nullable type must be used instead in /var/www/glpi/vendor/sabre/event/lib/Loop/functions.php on line 133

I think these deprecations should be fixed with cs fixer over the whole codebase (maybe also other sabre/* repos).
since fixing this error is backwards compatible we could do it in the older versions :+1:

maybe also other sabre/* repos

I confirm that it affects multiple sabre/* components we use.

I will link all the various related PRs to this issue, and keep the issue open until all PHP 8.4 compliance has been done.

These repos have been updated:

[x] event see PR #126 and release https://github.com/sabre-io/event/releases/tag/5.1.5
[x] xml see PR https://github.com/sabre-io/xml/pull/285 and release https://github.com/sabre-io/xml/releases/tag/2.2.8
[x] uri see PR https://github.com/sabre-io/uri/pull/116 - no release needed, it "just works"
[ ] http
[ ] vobject
[ ] dav
[ ] cache

Just want to say thank you ❤ for working thru all the repo @phil-davis

Also to-do is to forward-port code changes from the old major-version branches in each repo to the later (current...) branches and release PHP 8.4 compatible code in those branches.

I have got all the various major release branches of the "small" repos up-to-date with all the tools (cs-fixer, phpstan) and with CI running PHP 8.4, and releases done.
So event, http, xml and uri are done.
Now that they all pass cleanly, I will move on to getting the CI sorted out for vobject, and make releases for each major branch of that. And then do the same for "dav" (which is at the top of the dependency tree).

[ ] vobject

Progress in https://github.com/sabre-io/vobject/pull/662

[ ] dav

Was done in https://github.com/sabre-io/dav/pull/1556 but needs releasing (after vobject I guess)

Released https://github.com/sabre-io/vobject/releases/tag/4.5.6 today.
Hoping to follow-up all the things in dav tomorrow and get that released.

Anything we can assist with?

I finally got around to it!
https://github.com/sabre-io/dav/releases/tag/4.7.0

If there are any other PHP 8.4 issues found, then please reopen and we can sort them out.

Will update our CI and check if there are any issues there and on the test servers that deploy master/main

CI passed for owncloud https://github.com/owncloud/core/pull/41329


Frame size for LengthDelimitedCodec too small, when notarizing large traffic data

When trying to notarize huge transcripts (e.g. ~150KB), the default frame length from LengthDelimitedCodec is too small with 8MB. This triggers the error frame size too big.

I think it was related to OT data.