Use toad-scheduler job with Promise.all?

I am trying to schedule a job that is to complete actions for 10 devices.
I get this error when I try to use AsyncTask with Promise.all()
Argument of type '() => Promise<void[][]>' is not assignable to parameter of type '() => Promise<void>'.   Type 'Promise<void[][]>' is not assignable to type 'Promise<void>'.     Type 'void[][]' is not assignable to type 'void'.ts(2345)
but if I cast the Promise.all() as any, then it will build fine, and when I try running the code, things seem to run fine.
Is it recommended to split this up into 10 separate AsyncTasks, or can I run AsyncTask with Promise.all()
const task = new AsyncTask(
    'live location job',
    () => {
      return Promise.all(
        allUserVehicles.map(async ([userToken, vehicles]) => {
          const userToken = await getUserTokenByEmail(email); // refreshes token if needed
          return Promise.all(vehicles.map((vehicle) => {
            const vehicleClient = new VehicleClient(vehicle.vehicleID);
            vehicleClient.initializeVehicleClient(userToken).then(() => {
              console.log(`[${new Date().toISOString()}] - getting vehicle live data for Vehicle with Vin [${vehicle.vin}] under user [${userToken.email}]`);
              vehicleClient.getAllLiveVehicleData().then(_data => {
                sendMessage({...},
                }).then(
                  () => console.log(`[${new Date().toISOString()}] - sent vehicle live data for Vehicle with Vin [${vehicle.vin}] under user [${userToken.email}]`)
                )
              })
            })
          }));
        })
      );
    },
    (error: Error) => {
      console.error('error while getting tesla vehicle live data on scheduler', error.message);
      throw Error();
      // TODO: test that this throw error stops service
    }
  );

I need to write a test case for this, will report back.

many thanks!
We are planning to go live with this code tonight so any support is greatly appreciated

@Blutude I've published 2.1.1 which should no longer require casting to any.
That said, your code example looks somewhat scary, using map function to map to async function is quite a minefield.
I highly recommend watching https://www.youtube.com/watch?v=XV-u_Ow47s0 to understand the risks of mixing callbacks with async functions.

Thanks @kibertoad for these changes, and for sharing this video.
After watching the video, I would not have thought I am abusing promises here, more than what is needed (in the sense that I am not unnecessarily creating promises where I don't need to wait for things). The nature of the flow requires me to wait for 1 step before executing the next one, and so on, and do that for an array of 10  vehicles (or maybe even later once we scale, 300).
The video explains a lot but it does not necessarily provide an alternate solution. It does mention at some point that “when you await an async function, that creates 3 promises”. Does removing this one async await that I had and replacing it with a promise chain make things at least better here in performance (see code below)? At least I am reducing the amount of promises if I am understanding this right (am I?).
I think the best way of improving the performance of this at scale, is to separate the chained promises execution of these vehicles, into smaller vehicle arrays, that each get run in their own AsyncTask schedule, and start the schedule of each of those AsyncTasks at separate times. That way the loop of the chained promises becomes a smaller loop. Maybe even have 1 AsyncTask per vehicle? so if we have 300 Vehicles, then is it feasible to have 300 AsyncTasks scheduled at separate times? Off the top of your head, is it preferred to chunk them into 30 AsyncTasks of 10 vehicles each?
const teslaTask = new AsyncTask(
    'live location tesla job',
    () => Promise.all(allUserVehicles.map(([email, vehicles]) => {
      // refreshes token if needed
      teslaClient.getUserTokenByEmail(email)
      .then(userToken => Promise.all(vehicles.map(vehicle => {
        // then initializes vehicles client using the token
        const vehicleClient = new VehicleClient(vehicle.vehicleID);
        vehicleClient.initializeVehicleClient(userToken)
        .then(() => {
          // then gets vehicle data using the vehicle client
          logger.info(
            `[${new Date().toISOString()}] - getting tesla vehicle live data for Vehicle with Vin [${
              vehicle.vin
            }] under user [${userToken.email}]`,
          );
          vehicleClient.getAllLiveVehicleData()
          .then((data) => {
            // then sends vehicle data to wialon
            WialonClient.getInstance().sendLocation(vehicle, data)
            .then(() =>
              // then logs that it completed
              logger.info(
                `[${new Date().toISOString()}] - sent tesla vehicle live data for Vehicle with Vin [${
                  vehicle.vin
                }] under user [${userToken.email}] to wialon`,
              ),
            );
          });
        });
      })));
    })),
    (error: Error) => {
      logger.error(`error while running scheduled tesla job: ${error.message}`);
      throw Error();
    },
  );

@Blutude It's not just about performance: note that if you throw inside a callback (e. g. inside .map()), error does not automatically propagate to the parent promise, you get an unhandled rejection instead, which will crash your Node instance. So you have to add try-catch at the very least to handle your errors explicitly within every additional Promise level.
If you want to generate predictable load here, I would recommend using a promise pool, e. g. https://www.npmjs.com/package/@supercharge/promise-pool
Then you could use ToadScheduler for just kickstarting the process, and handle the concurrent execution with proper error handling and configurable rate limiting via the promise pool.

To me it feels like using async await with await Promise.all and try catches is cleaner in terms of readability of the code, but as you advised in the documentation of this package, and as it was advised in the video you linked, I removed the use of most async awaits in this flow to reduce the overall amount of promises.
I did edit the block of code to catch all the different promises in the chain of promises. I guess instead I can use a Promise pool like you mentioned, and have each of those functions throw specific errors, so that I can interpret the error and know what to log in the handleError section.


Requesting a BackgroundColorTransformation

Hi all,
I recently tried updating the FFImageLoading-libraries in our App to the new 2.4 minor version, but ran into trouble with the Xam.Plugins.Forms.CachedImageCircle-package we're using, since the CircleCachedImage-control is looking for the CachedImageRenderer in the FFImageLoading.Forms.Droid-assembly, which no longer exists.
After a bit of searching, I've now decided to use CircleTransformation in order to get those images as need it to be displayed as a circle, while keeping most of our other code in tact. However, CircleCachedImage had a FillColor-property that allowed you to change the background colour of transparent images while still applying the circle transformation. Setting the BackgroundColor on a CachedImage, however, fills the entire View's surface with that background colour, and doesn't apply the circle transformation to the background...
Now I found the suggestion of a BackgroundColorTransformation before, in issue #555, an idea that was later abandoned. However, I would like to reopen the request for such a transformation, since it seems very practical when dealing with images that have a transparent background.
All the best,
Alexander.

I'd be willing to try my hand at creating this transformation myself as well, though for that to work I'd need to know the basic architecture of the transformation system. Right now I don't quite understand how transformations are resolved, for example. I mean, you can add transformations in PCL/platform-agnostic code, but implementations seem to be platform-specific, as expected. So how does the system get from platform-agnostic specification to platform-gnostic implementation?

I'd be willing to try my hand at creating this transformation myself as well, though for that to work I'd need to know the basic architecture of the transformation system. Right now I don't quite understand how transformations are resolved, for example. I mean, you can add transformations in PCL/platform-agnostic code, but implementations seem to be platform-specific, as expected. So how does the system get from platform-agnostic specification to platform-gnostic implementation?

Decided to answer my last question myself, as I bumped into #427, which explains how to do it and contains a link describing the "Bait and Switch PCL Trick" used to do so...

It's implemented, but not tested yet. See ColorFillTransformation. You can review my commits too:

https://github.com/luberda-molinet/FFImageLoading/commit/ea64ddbdf482cefc96d0eb15980394fe0f8ee7c8
https://github.com/luberda-molinet/FFImageLoading/commit/87c69858b4546d8734968ae40fac4e616d256514

Hi Daniel,
Thanks for your feedback! It's good to know that such a feature already exists, even if it's still untested. I'd be happy to test and review your code, but would need to find some time within our development-schedule to do this. I'll let you know when I do...
Best regards,
Alexander.

Hey Daniel,
Though it took some time, one of my colleagues tested the ColorFillTransformation using FFImageLoading's sample projects yesterday. The transformation seems to work perfectly on iOS and Android and seems to do exactly what we need. I didn't get it to work on UWP because of an issue with MakePri.exe (as described here) and haven't checked any other OS, but since iOS and Android are the most pertinent to our situation (and, judging from the commits, the primary versions of the transformation implemented) and these seem to work, I hope this will suffice to include the ColorFillTransformation in one of FFImageLoading's next releases.
The only thing we noticed is that the order in which the transformations are applied is important in that the circle transformation doesn't get applied to the color fill if the color fill is not the first transformation in the list. I'm not sure whether this is per design (I've got too little experience with other transformations to know what the default behavior is), but it's certainly not blocking and in a way makes sense - yet is something you should be aware of when applying the transformations...
Is there any indication of when we could expect the transformation to be included? I'm asking since we would like to continue updating your library...
All the best,
Alexander.

@daniel-luberda Will the new transformation be included anytime soon in future release?

It's currently included, so I'll close this.


Cannot start R on M1

$ mamba list r-base
r-base                    4.1.1                h3aa6e3f_0    conda-forge

$ R
dyld: Library not loaded: @rpath/libreadline.8.dylib
  Referenced from: /opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/R/lib/libR.dylib
  Reason: no suitable image found.  Did find:
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/R/lib/../../libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/R/bin/exec/../../../libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/libreadline.8.dylib: mach-o, but wrong architecture
	/opt/homebrew/Caskroom/mambaforge/base/envs/x/lib/libreadline.8.1.dylib: mach-o, but wrong architecture
fish: Job 1, 'R' terminated by signal SIGABRT (Abort)

$ mamba info
...
          conda version : 4.11.0
         python version : 3.9.7.final.0
       virtual packages : __osx=11.6=0
                          __unix=0=0
                          __archspec=1=arm64
...
               platform : osx-arm64
             user-agent : conda/4.11.0 requests/2.26.0 CPython/3.9.7 Darwin/20.6.0 OSX/11.6
                UID:GID : 501:20
             netrc file : None
           offline mode : False

cc @tschuelia

Can you post the entire output of conda list and not just the r-base package?

 Closing for now.


[androidx-migration] Require to migrate but nothing to migrate

Steps to Reproduce

Execute flutter pub get on the code sample
Show error  The plugin wallet_connect_android requires your app to be migrated to the Android embedding v2. Follow the steps on https://flutter.dev/go/android-project-migration and re-run this command.
Follow the instruction to migrate to androidx
Expected results:
Succed to migrate
Actual results:

Code sample
https://github.com/tokoinofficial/wallet_connect/tree/integrate_wallet_connect_android_x

Logs

flutter_run_verbose_log.txt

ntbinh@Binhs-MacBook-Pro wallet_connect % flutter analyze
Analyzing wallet_connect...
No issues found! (ran in 4.8s)

ntbinh@Binhs-MacBook-Pro wallet_connect % flutter doctor -v
[✓] Flutter (Channel stable, 3.3.10, on macOS 12.6.2 21G320 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/ntbinh/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (4 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/ntbinh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 7.0 (API 24) (emulator)
    • macOS (desktop)                    • macos         • darwin-x64     • macOS 12.6.2 21G320 darwin-x64
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

I also see this issue on the latest master channel.

Are you sure you saw the same error message? The incorrect link was changed in https://github.com/flutter/flutter/pull/107456 (which isn't in 3.3, but is on master).

Are you sure you saw the same error message? The incorrect link was changed in https://github.com/flutter/flutter/pull/107456 (which isn't in 3.3, but is on master).

No, the message is not the same exactly but it's about migration issue in general I mean. Below are output messages on stable and master channels: (sorry for missing this)
Stable
Running "flutter pub get" in wallet_connect...                      3.3s
Running "flutter pub get" in example...                          2,777ms
This app is using a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to migrate this app to the V2 embedding.
Take a look at the docs for migrating an app: https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
The plugin `wallet_connect_android` requires your app to be migrated to the Android embedding v2. Follow the steps on https://flutter.dev/go/android-project-migration and
re-run this command.

Master
Running "flutter pub get" in wallet_connect...
Resolving dependencies... (1.6s)
Got dependencies!
Resolving dependencies in ./example...
Got dependencies in ./example.
This app is using a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to migrate this app to the V2 embedding.
Take a look at the docs for migrating an app: https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
The plugin `wallet_connect_android` requires your app to be migrated to the Android embedding v2. Follow the steps on the migration doc above and re-run this command.

The bug is that the second link on stable is linking to the wrong migration. AndroidX migration and embedding v2 migration aren't the same thing, and the actual problem here is that the project needs a v2 migration.
Closing as fixed on master since the bad link doesn't exist in the master error message. The v2 embedding notification and wiki instructions link are expected behavior here.


🔨 @mx/core v0.1.0 -- development

🔨 core modules and necessary functionalities

🕐 : means still in development and improving...
✅ : means ready for release or completed targets
⏸ : means it is now in backlog or paused

Checklist for implementations and development tasks:

[x] core Gateway 🕐  (refers route-handler-module)
[x] core MxJs 🕐 Main class and application's core
[x] core Inquery 🕐 Request class
[x] core Reply 🕐 Response class

Following express.js (v5) core to make this almost equivalent

Todo list for addition or implementation or custom module in core itself

[ ] core content-disposition for request
[ ] core content-type => improve by following it
[ ] core cookie => custom
[ ] core cookie-signature => custom
[ ] core debug => custom | use-it
[ ] core depd => review-n-decide
[ ] core etag => use it directly
[ ] core mime-types => review-n-decide or custom
[ ] core encodeurl => review-n-decide
[ ] core escape-html => custom (copy-paste-like)
[ ] core fresh => custom (refactor + copy-paste)
[ ] core methods => update our existing one from this
[ ] core mime-types => update our existing one from this
[ ] core proxy-addr => use-it-directly
[ ] core qs => use-it-directly
[ ] core range-parser => custom
[ ] core safe-buffer => custom (copy-paste-like)
[ ] core send => review & update Reply class
[ ] core serve-static => custom (by reviewing it)
[ ] core statuses => update our constants
[ ] core type-is => review n decide

Tests
Implement unit tests with at least 90%+ to 100% coverage fulfillment using vitest instead of jest
Now start cooking this 😩
~/@mahabubx7

[Update] 2024-10-10
Refactored core gateway, route and router module (new)
Also, updated with latest benchmarks (including screenshot for details)
~/@mahabubx7


Update to OmniSharp 1.36.0

GitHub checks did not update but CI was passing - https://travis-ci.org/github/OmniSharp/omnisharp-vscode/builds/716697448

Again Github checks did not update. CI passing - https://travis-ci.org/github/OmniSharp/omnisharp-vscode/builds/716703443


Fixed implicit shader stage selection for Vulkan

Hi Anton! Thanks again. I meditated a bit and I think that the right usage should be:
ORIGINAL (wrong):
   if (stageBits & StageBits::INDEX_INPUT)
        flags |= VK_PIPELINE_STAGE_2_VERTEX_INPUT_BIT;

    if (stageBits & StageBits::VERTEX_SHADER)
        flags |= VK_PIPELINE_STAGE_2_VERTEX_SHADER_BIT;

YOURS (partially correct):
    if (stageBits & StageBits::INDEX_INPUT)
        flags |= VK_PIPELINE_STAGE_2_VERTEX_INPUT_BIT | VK_PIPELINE_STAGE_2_INDEX_INPUT_BIT;

    if (stageBits & StageBits::VERTEX_SHADER)
        flags |= VK_PIPELINE_STAGE_2_VERTEX_SHADER_BIT | VK_PIPELINE_STAGE_2_VERTEX_ATTRIBUTE_INPUT_BIT;

CORRECTED (correct?):
   if (stageBits & StageBits::INDEX_INPUT)
        flags |= VK_PIPELINE_STAGE_2_INDEX_INPUT_BIT;

    if (stageBits & StageBits::VERTEX_SHADER)
        flags |= VK_PIPELINE_STAGE_2_VERTEX_SHADER_BIT | VK_PIPELINE_STAGE_2_VERTEX_ATTRIBUTE_INPUT_BIT;

Based on:

https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkPipelineStageFlagBits2.html
https://microsoft.github.io/DirectX-Specs/d3d/D3D12EnhancedBarriers.html

Notes:

StageBits::INDEX_INPUT is only for INDEX INPUT, matches D3D12 (sorry, I mistyped)
StageBits::VERTEX_SHADER is missing VERTEX ATTRIBUTE INPUT, which is implicitly enabled in D3D12_BARRIER_SYNC_VERTEX_SHADING
VK_PIPELINE_STAGE_2_VERTEX_INPUT_BIT = VK_PIPELINE_STAGE_2_INDEX_INPUT_BIT | VK_PIPELINE_STAGE_2_VERTEX_ATTRIBUTE_INPUT_BIT according to the spec

What do you think?

You're right, it seems to be working on my end. Fixed.

Thanks! Integrated.


ERROR with Event Loop

Hello. I wrote a small RAG system for ma project and I decided to push it on localhost
host = "localhost"
runner = Runner.from_yaml('RAG_system/data_original/test_1/pipline.yaml', project_dir = "RAG_system/data_original/test_1")
runner.run_api_server(host)

My code for posting
import requests
url = "http://localhost:8000/run"
data = {
    "query": "query",
    "result_column": "Answer"
}
import json```
payload = json.dumps(data)
headers = {
    'accept': "application/json",
    'Content-Type': "application/json"
    }
response = requests.request("POST", url, data=payload, headers = headers)
print(response.text)

And every time I get this error
RuntimeError: This event loop is already running
How do I solve it?

@warjohn Hi, did you run this code in jupyter?
Try this
import nest_asyncio
nest_asyncio.apply()

it doen't work on linux, idk

@warjohn
I am investigating this problem.
Thanks for reporting the issue.

@warjohn
I made PR to resolve this error.
Thanks for reporting a but for me again.
This fix will be update on AutoRAG v0.2.14

@warjohn Hi, did you run this code in jupyter?
Try this
import nest_asyncio
nest_asyncio.apply()

Thanks


Question : How does CTMRG work together with symmetric tensors ?

Hi,
I was trying to run some PEPS numerics for a model with SU(N)*U(1)*FermionZ2 symmetry.
To do this I implemented the Hamiltonian with minimal symmetry (i.e. only the fermionic Z2) and with all symmetries. I then noticed that the less symmetric implementation heavily outperforms the more symmetric implementation.
For starters the CTMRG environments fail to converge in the symmetric case since the error remained INF at all times. According to Lukas this means that new sectors are being added but after some time I'd expect some form of convergence ? Does anybody know why this might not happen ?
After forcing the environment bonds to remain constant I get convergence but still I get the usual (i.e. MPS) behavior that small bond dimensions without symmetries yield lower energies then the corresponding bond dimension with symmetries.
In general it seems that enforcing symmetries seems to be a less effective tool for PEPS then MPS. Did anybody already think about this in a more structured manner ? If so, I'd love to hear your cup of tea on this.

I think what you are describing is indeed the expected behaviour, imposing symmetry restricts the variational manifold, such that the energies are higher. The flipside is that the actual physics might be closer to the thing you want to simulate, since you are not breaking the symmetry just to obtain lower energies, if you expect the symmetry to be unbroken.
Also keep in mind that in 2D, there are no LSM-type arguments for continuous symmetries to remain unbroken, so depending on the model you are trying to simulate, it might just be the case that imposing the symmetry is not what you want to do at all.
Finally, the Inf error is mostly just a matter of how we compute the error, so we could look into altering this. For symmetries, the problem becomes larger, as the spectrum can shift quite drastically depending on how you cut, for each sector separately, such that getting this to stabilize is somewhat difficult.
However, I would expect if you want a performant algorithm, it really is best to use the FixedSpaceTruncation. You could just do one run in the beginning that attempts to fix the environment virtual spaces, and then keep this fixed for a while. (This is probably even the case without symmetries)

Ok, thanks for this information.
I found it interesting that this seems to be so much worse for PEPS as for MPS though. Is is somehow harder to add the right sectors for PEPS ?

I guess doing CTMRG with changing sectors each iteration is like doing two-site update schemes in MPS, with even more degrees of freedom, which is already for MPS not super stable. The fact that there is no canonical form also makes this kind of hard, and truncating loopy networks is not as easy as MPS, so yes, PEPS is harder :wink:

Thanks for this very clarifying answer (as always) !


[DO_NOT_MERGE] Speech GA - library update

@nnegrey Please review.
speech_transcribe_auto_punctuation
speech_transcribe_enhanced_model

@nnegrey Added the additional sample. Please review and let me know if there is anything else.


chore(package): Version 1.2.0

As master is a protected branch now, we need to merge to release...
Change-Type: minor

The prebuilds seem to be missing from https://github.com/resin-io-modules/winusb-driver-generator/releases ?


pugixml: 1.9 -> 1.10

Motivation for this change

split to multiple outputs when using the shared library version
enabled the tests
validate the pkg-config files

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I have a doubt, do i open another pr with the suggestion?

go for it

Result of nixpkgs-review pr 102926 run on x86_64-darwin 1

1 package marked as broken and skipped:

poedit

5 packages built:

PlistCpp
blender
darktable
pugixml
xib2nib


[feature request] support Node.js v18.6.0 loader hooks API

The loader hooks API that Node.js began shipping in v18.6.0 is intended for v18.x LTS and expected to be a bit more long-lasting than previous iterations. It does, however, introduce a few breaking changes to the loaders API, which this project should adapt to. For this project to continue to work as expected with Node.js v18.x, which will be going LTS 2022-10-25 (a few months away), we should be now testing against a different SemVer range (>=18.6.0).
Refs: https://github.com/nodejs/node/pull/42623#issuecomment-1151134176

I wonder if @jakobjingleheimer is aware of this project and would be interested in contributing a fix for this? This project advertises that it works with >=13.7.0 on its README, but that no longer seems true due to the latest current release, which changed things up a bit.
/cc @GeoffreyBooth


DNS failure

http://public-mainnet-node.ethereum.org/
is not being resolved. Error: http://public-mainnet-node.ethereum.org/ as of 2023-05-24.

https://dnschecker.org/all-dns-records-of-domain.php?query=public-mainnet-node.ethereum.org%2F&rtype=ALL&dns=cloudflare

I think it's just a placeholder, I'm not sure it ever worked
better to run your own BN locally, or use a public one from some provider e.g. QuickNode: https://www.quicknode.com/docs

It was a placeholder that wasn't supposed to resolve, it's since been changed to localhost, so we can close this issue.


Check item type on input item ids

add a check in the script to verify the type matches what's expected for the Feature Service and Feature Collection item ids passed into the script and report a friendly message to the user if the item type isn't what was expected.

We now check the item type associated with the feature service and feature collection item ids. If the item is not the correct type and error is thrown with a friendly error message and the script stops execution.

Verified with #12


Unable to scroll log viewer in chromium based browsers

Describe The Bug:

Unable to scroll log viewer on main screen or in log viewer on a chromium based browser (Chrome on Raspberry or Chromium Edge.
To Reproduce:

Opening homebridge in chrome or edge.

Expected behavior:

Logs:

Show the Homebridge / Homebridge Config UI X logs here.


Translation .tr doesn't need to be nullable

When we are using .tr to translate, I think there's no need for it to be nullable. If the translation isn't found, just return and display the key.
Advantages:

Easier to upgrade from previous versions of getx without null safety, as it won't break old code
Easier to identify missing translations. Rather than supplying the default value like 'test_label'.tr ?? 'Default value for testing label' just display "test_label" as translation result

For some reason after flutter pub upgrade it isn't nullable, everything works good!
Don't understand what happened but I'll close this for now.


Add Locations to the Docker scan results on Sarif output

Using the jfrog cli to scan a docker image using '--format sarif' produces a sarif file not accepted by GitHub Security Centre due to the locations field missing for the results set [GH1001]
Steps To Reproduce:
Prerequisite: use a jfrog instance setup with a remote docker repository (https://registry-1.docker.io/)

Pull nginx:latest - jf docker pull <rt_instance>/nginx:latest
Scan nginx:latest using sarif format,
jf docker scan <rt_instance>/nginx:latest --format sarif
Upload sarif output to https://sarifweb.azurewebsites.net/Validation and select 'GitHub Integration rules' there are a few issues, the one which GitHub explicitly complains about is GH1001 in the results.

Expected:
GH1001 issue is addressed so the Sarif output is accepted by GitHub when uploaded to GitHub Security Centre
Other:
Example of sarif file of nginx is attached
jfrog-docker-scan-of-nginx-latest-2.50.2.sarif.json.gz

I think there actually might be some kind of issue i was running jfrog cli for sarif and if i run the same command and then i switched from older docker to newer cli and the location in sarif was no longer present, however i was using "jf s image.tar" command instead.
So tl;dr i am having similar issue and it is quite annoying

@davidka91  try downgrading to version 2.48.0 if it helps

@Jiri-Stary thanks, downgrading to 2.48.0 produced a SARIF file that GitHub accepted.
This ticket appears to be a duplicate of https://github.com/jfrog/jfrog-cli/issues/2270.


Using new toolchain (12.2) csr opcode errors.

The _zicsr and _zifecei options for -march are no longer assumed if you specify i as an option to -march=
For test cases that have any csr opcodes in them 9DUT or Sail) it will fail the compile with a message:
Error: unrecognized opcode csrr a0,mhartid', extension zicsr' required
Currently the python scripts for generating makefile for both the DUT and Sail use as passed in parameter {0}
-march={0} which for testing C extension translates to -march=rv64ic
Changing the python to a fixed value of : -march=rv64imafdc_zicsr_zifencei instead of the {0} fixes this issue and allows the test cases to compile w/o errors.
I do not know if this is the long term fix for this as some cross-compilers may not support the full extension set, based on how they were built.

Example from our DUT that uses csr opcodes in test case:
//RVMODEL_BOOT
#define RVMODEL_BOOT
.section .text.init;
.extern _fsignature;
csrr a0, mhartid              ;
li   a1, 0x00                        ;
beq  a1, a0, cont             ;
55:
wfi ;
j 55b ;
cont: ;
RVMODEL_IO_INIT;
This allows only 1 hart to proceed to runt he tests and puts any other hart into a wfi state.
Marc Karasek
Principal Software Engineer
M:<PHONE_NUMBER>
[A close up of a sign    Description automatically generated]
www.inspiresemi.comhttp://www.cryptocoretech.com/
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message is not the intended recipient or agent responsible for delivering the message to the intended recipient, then you are hereby notified that any dissemination or copying of this communication is strictly prohibited.  If you have received this electronic transmission in error, please delete it from your system without copying it and notify the sender by reply e-mail  so that our address record can be corrected.  Thank you.
From: Wadood @.>
Sent: Friday, June 2, 2023 11:21 AM
To: riscv-non-isa/riscv-arch-test @.>
Cc: Marc Karasek @.>; Author @.>
Subject: Re: [riscv-non-isa/riscv-arch-test] Using new toolchain (12.2) csr opcode errors. (Issue #359)
Each test file has the RVTEST_ISA function that defines the ISA string which is picked up by the RISCOF and passed to -march flag.
And each test has an appropriate ISA string depending on the Instruction OPCODES that the test executes. For example for the C extension tests, the RVTEST_ISA is defined as RV64IChttps://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cxor-01.S%23L20___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjNlZDA6NWJjMzQzMDRmYjFlNjA1MzZjYjM3ZThlOWVjYWExODdmMWU5ZDQxY2U4MzVkYzM1NmQ3MDJkZTlkNjFhNmQzZTpoOlQ (which translates to -march=rv64ic), except for c.ebreak test. As c.ebreak raises an exception, it executes CSR opcodes. Hence, zicsr is included in the ISA string for this test (linkhttps://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-ar ch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cebreak-01.S___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmFhZTU6Njg2ZTljOTE5YTNlMmUyOWE4MmY2MzEyNzhiYWRlNjAxNTMxNmQzODlkYTczYzlmNTA1MDA1ZDAzYThjN2M2MzpoOlQ).
So, the test carefully includes only those minimum extensions/features to the ISA string that are required by the test. Since the C extension tests do not execute (or are not required to execute) CSR opcodes (except c.ebreak), so ISA string only includes ic and does not include zicsr. If there is a bug in the implementation (or the C extension is disabled in the implementation), it may cause a trap and tries to execute CSR opcodes, then the toolchain will throw the compilation error because zicsr is not included (and not required to be included by that test)
—
Reply to this email directly, view it on GitHubhttps://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/issues/359%23issuecomment-1573910157___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjkzMjI6ODllZWMwMTA5YjU2NDgwMzBmNWU4NWIxODc4MDY2ZDA2OGEyYTI4ZTY3M2M3ODIyODc4YmNiYWQzMDliM2Q5MjpoOlQ, or unsubscribehttps://url.avanan.click/v2/___https:/github.com/notifications/unsubscribe-auth/AR3S6Y4TOTUEIPEKPZ55X4DXJIAFHANCNFSM6AAAAAAYYNS4OA___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmY3ODQ6NTJlZDVmNTY3MzA3Y2NjY2FiZmE5MDhhNzFlMjVhMWFhN2U5NWNlNWJmYzY0YmE3NmYzZjA5MWM0N2YyMDcwZDpoOlQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I think the short description is:

you have provided a string (or the riscv-config YAML) that says you
support Zicsr,
you require Zicsr in your boot code,
but if the test doesn't require Zicsr, it tries to compile the test (and
your boot code) without that string
and therefore the compile fails?

On Fri, Jun 2, 2023 at 9:55 AM InspireSemi @.***> wrote:

Example from our DUT that uses csr opcodes in test case:
//RVMODEL_BOOT
#define RVMODEL_BOOT
.section .text.init;
.extern _fsignature;
csrr a0, mhartid ;
li a1, 0x00 ;
beq a1, a0, cont ;
55:
wfi ;
j 55b ;
cont: ;
RVMODEL_IO_INIT;
This allows only 1 hart to proceed to runt he tests and puts any other
hart into a wfi state.
Marc Karasek
Principal Software Engineer
M:<PHONE_NUMBER>
[A close up of a sign Description automatically generated]
www.inspiresemi.comhttp://www.cryptocoretech.com/
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If the
reader of this message is not the intended recipient or agent responsible
for delivering the message to the intended recipient, then you are hereby
notified that any dissemination or copying of this communication is
strictly prohibited. If you have received this electronic transmission in
error, please delete it from your system without copying it and notify the
sender by reply e-mail so that our address record can be corrected. Thank
you.
From: Wadood @.>
Sent: Friday, June 2, 2023 11:21 AM
To: riscv-non-isa/riscv-arch-test @.>
Cc: Marc Karasek @.>; Author @.>
Subject: Re: [riscv-non-isa/riscv-arch-test] Using new toolchain (12.2)
csr opcode errors. (Issue #359)
Each test file has the RVTEST_ISA function that defines the ISA string
which is picked up by the RISCOF and passed to -march flag.
And each test has an appropriate ISA string depending on the Instruction
OPCODES that the test executes. For example for the C extension tests, the
RVTEST_ISA is defined as RV64IC<
https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cxor-01.S%23L20___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjNlZDA6NWJjMzQzMDRmYjFlNjA1MzZjYjM3ZThlOWVjYWExODdmMWU5ZDQxY2U4MzVkYzM1NmQ3MDJkZTlkNjFhNmQzZTpoOlQ>
(which translates to -march=rv64ic), except for c.ebreak test. As c.ebreak
raises an exception, it executes CSR opcodes. Hence, zicsr is included in
the ISA string for this test (link<
https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-ar ch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cebreak-01.S___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmFhZTU6Njg2ZTljOTE5YTNlMmUyOWE4MmY2MzEyNzhiYWRlNjAxNTMxNmQzODlkYTczYzlmNTA1MDA1ZDAzYThjN2M2MzpoOlQ>).
So, the test carefully includes only those minimum extensions/features to
the ISA string that are required by the test. Since the C extension tests
do not execute (or are not required to execute) CSR opcodes (except
c.ebreak), so ISA string only includes ic and does not include zicsr. If
there is a bug in the implementation (or the C extension is disabled in the
implementation), it may cause a trap and tries to execute CSR opcodes, then
the toolchain will throw the compilation error because zicsr is not
included (and not required to be included by that test)
—
Reply to this email directly, view it on GitHub<
https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/issues/359%23issuecomment-1573910157___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjkzMjI6ODllZWMwMTA5YjU2NDgwMzBmNWU4NWIxODc4MDY2ZDA2OGEyYTI4ZTY3M2M3ODIyODc4YmNiYWQzMDliM2Q5MjpoOlQ>,
or unsubscribe<
https://url.avanan.click/v2/___https:/github.com/notifications/unsubscribe-auth/AR3S6Y4TOTUEIPEKPZ55X4DXJIAFHANCNFSM6AAAAAAYYNS4OA___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmY3ODQ6NTJlZDVmNTY3MzA3Y2NjY2FiZmE5MDhhNzFlMjVhMWFhN2U5NWNlNWJmYzY0YmE3NmYzZjA5MWM0N2YyMDcwZDpoOlQ>.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/359#issuecomment-1574039933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJSSW7AFK2XL66JMLDLXJILHHANCNFSM6AAAAAAYYNS4OA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yes
On Sat, Jun 3, 2023, 3:05 AM Allen Baum @.***> wrote:

I think the short description is:

you have provided a string (or the riscv-config YAML) that says you
support Zicsr,
you require Zicsr in your boot code,
but if the test doesn't require Zicsr, it tries to compile the test (and
your boot code) without that string
and therefore the compile fails?

On Fri, Jun 2, 2023 at 9:55 AM InspireSemi @.***> wrote:

Example from our DUT that uses csr opcodes in test case:
//RVMODEL_BOOT
#define RVMODEL_BOOT
.section .text.init;
.extern _fsignature;
csrr a0, mhartid ;
li a1, 0x00 ;
beq a1, a0, cont ;
55:
wfi ;
j 55b ;
cont: ;
RVMODEL_IO_INIT;
This allows only 1 hart to proceed to runt he tests and puts any other
hart into a wfi state.
Marc Karasek
Principal Software Engineer
M:<PHONE_NUMBER>
[A close up of a sign Description automatically generated]
www.inspiresemi.comhttp://www.cryptocoretech.com/
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If the
reader of this message is not the intended recipient or agent responsible
for delivering the message to the intended recipient, then you are hereby
notified that any dissemination or copying of this communication is
strictly prohibited. If you have received this electronic transmission in
error, please delete it from your system without copying it and notify
the
sender by reply e-mail so that our address record can be corrected. Thank
you.
From: Wadood @.>
Sent: Friday, June 2, 2023 11:21 AM
To: riscv-non-isa/riscv-arch-test @.>
Cc: Marc Karasek @.>; Author @.>
Subject: Re: [riscv-non-isa/riscv-arch-test] Using new toolchain (12.2)
csr opcode errors. (Issue #359)
Each test file has the RVTEST_ISA function that defines the ISA string
which is picked up by the RISCOF and passed to -march flag.
And each test has an appropriate ISA string depending on the Instruction
OPCODES that the test executes. For example for the C extension tests,
the
RVTEST_ISA is defined as RV64IC<

https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cxor-01.S%23L20___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjNlZDA6NWJjMzQzMDRmYjFlNjA1MzZjYjM3ZThlOWVjYWExODdmMWU5ZDQxY2U4MzVkYzM1NmQ3MDJkZTlkNjFhNmQzZTpoOlQ

(which translates to -march=rv64ic), except for c.ebreak test. As
c.ebreak
raises an exception, it executes CSR opcodes. Hence, zicsr is included in
the ISA string for this test (link<

https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-ar ch-test/blob/main/riscv-test-suite/rv64i_m/C/src/cebreak-01.S___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmFhZTU6Njg2ZTljOTE5YTNlMmUyOWE4MmY2MzEyNzhiYWRlNjAxNTMxNmQzODlkYTczYzlmNTA1MDA1ZDAzYThjN2M2MzpoOlQ

).
So, the test carefully includes only those minimum extensions/features to
the ISA string that are required by the test. Since the C extension tests
do not execute (or are not required to execute) CSR opcodes (except
c.ebreak), so ISA string only includes ic and does not include zicsr. If
there is a bug in the implementation (or the C extension is disabled in
the
implementation), it may cause a trap and tries to execute CSR opcodes,
then
the toolchain will throw the compilation error because zicsr is not
included (and not required to be included by that test)
—
Reply to this email directly, view it on GitHub<

https://url.avanan.click/v2/___https:/github.com/riscv-non-isa/riscv-arch-test/issues/359%23issuecomment-1573910157___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OjkzMjI6ODllZWMwMTA5YjU2NDgwMzBmNWU4NWIxODc4MDY2ZDA2OGEyYTI4ZTY3M2M3ODIyODc4YmNiYWQzMDliM2Q5MjpoOlQ

,
or unsubscribe<

https://url.avanan.click/v2/___https:/github.com/notifications/unsubscribe-auth/AR3S6Y4TOTUEIPEKPZ55X4DXJIAFHANCNFSM6AAAAAAYYNS4OA___.YXAzOmluc3BpcmVzZW1pOmE6bzpmYTBmNDc0MWUxYjA2OGQ2YWFiNDQ3NmM1YWNlYmIwNjo2OmY3ODQ6NTJlZDVmNTY3MzA3Y2NjY2FiZmE5MDhhNzFlMjVhMWFhN2U5NWNlNWJmYzY0YmE3NmYzZjA5MWM0N2YyMDcwZDpoOlQ

.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub
<
https://github.com/riscv-non-isa/riscv-arch-test/issues/359#issuecomment-1574039933
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AHPXVJSSW7AFK2XL66JMLDLXJILHHANCNFSM6AAAAAAYYNS4OA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/riscv-non-isa/riscv-arch-test/issues/359#issuecomment-1574731930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD72ZM3ASIKZ7QYP7Y7ZBZTXJLO4VANCNFSM6AAAAAAYYNS4OA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I think this issue was resolved, and all existing tests are working on gcc 12.2.
Closing this one, you may reopen it anytime.


Correcting memory.h comment.

We're not using these templates by fear of libstdc++, but to enforce the usage of gpr_malloc / gpr_free.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


remove jenkins operator from community operators

As we released the jenkins operator for openshift, we are removing it from the community operators to avoid confusion on openshift ui, we will be pushing a new community operator called jenkins automation operator
Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@jkhelil can you singoff your commit? More info here

@jkhelil can you singoff your commit? More info here


Update immigration questions following review

Changes made:

Incorporate radio hint text into the label
Change "Other" to "Another..."
Change "How will you get the right to work or study in the UK?" to "Will you need the course provider to sponsor a skilled worker or student visa?"
Change immigration status example from "permanent residence" to "Indefinite leave to remain"
Change "Give any relevant information" to "Immigration status"
Add threshold to textareas

Screenshots

Before
After

(1) Will all candidates understand that they will “need a course provider to sponsor a skill worker or student visa”?

Hopefully! We added some guidance on this to both Find and on Get into teaching. However we don't know for sure. We did consider linking to the guidance, or repeating some of it. But let's see if that's needed or not first?

(2) Related to (1) I think we could do with adding "I don't know" as an answer

The main aim of this question is to avoid the preventable rejection of people applying to courses which cannot sponsor visas, when they need one.  Adding an "I don't know" option makes this more difficult (as we can’t then display such a strong warning), and might mean that providers reject them on this basis anyway.
Initial research seems to suggest that international students likely have a good understanding of what their visa route options are. However if we get evidence that it’s still confusing, we could either add a third option, or give candidates some additional guidance so that they know how to answer.

(3) Instead of "give details" consider "Tell us how you intend to get the right to work or study" (or similar)

Yeah, I wasn't sure about this either. Will have a think.

(4) Related to (3) you can just make the label ‘No’

Will have a think on this. Think it's good to give the Family visa and Graduate visa as examples, as they may not realise that Graduate visas do not need to be sponsored by the providers.

(5) Change “What is your...” to “What’s your...”

👍

(6) Add a "not sure" to the "What is your immigration status" question

If someone isn't sure, or it's complicated, they could write it into the free text box?  Probably better that we let them explain it in their own words rather than just submitting a "Not sure" to the provider?

(7) Is the "immigration status" textarea question optional?

No.


fix(getting_started): Updated file names in installation examples

Fixes #5843

Can you merge this @rtfeldman?

Nice catch, thanks @ch1n3du :)

Just started learning Roc and it's delightful so far.


missing feature on mask

There are some missing feature and/or bug with the addMask function:

if the element we want to mask has a z-index greater than 0, the mask is not visible since it's under the element we want to hide
if the element is "dynamically" added, it seems that the element is not found and the mask is not added
to remove the mask, one needs to execute the following script manually document.body.removeChild(document.querySelector('#BP_ELEMENT_HIGHLIGHT__')). Maybe it would be a good idea to add a removeMask function
for the moment, if you add multiple mask, all the mask elements will have the same id which is not great and if you want to remove one of the mask it is not possible. Maybe the mask should not have an id but a class and the addMask function should allow one to specify a suffix for the class name (same for the removeMask)

Hi, please check out #12 on addMask and removeMask related improvements. I have also documented the usage in README if you don't feel like reading code :)

can be closed now


is.js validation of none required field

Hi
Not sure if this is a bug, or if its me doing somthing wrong.
I run into an issue when i use is.js for simple email validation, on a field that has required: false set.
The form is not valid, even though the field is empty and is not required.
Here is a jsbin (just used the is.js integration example and changed)
http://jsbin.com/giledaxoji/edit?html,js,output
Some way to fix this?

I think we should update the example. You should first check if it's empty.
If it is, then don't do the validation check for email.
On Mon, Sep 21, 2015, 8:05 AM TheBekker<EMAIL_ADDRESS>wrote:

Hi
Not sure if this is a bug, or if its me doing somthing wrong.
I run into an issue when i use is.js for simple email validation, on a
field that has required: false set.
The form is not valid, even though the field is empty and is not required.
Here is a jsbin (just used the is.js integration example and changed)
http://jsbin.com/giledaxoji/edit?html,js,output
Some way to fix this?
—
Reply to this email directly or view it on GitHub
https://github.com/formly-js/angular-formly/issues/476.

--

Kent C. Dodds https://twitter.com/kentcdodds

That makes sense, but not sure how i would accomplish this?

Like this: http://jsbin.com/kebucas/edit?html,js,output :-)
On Mon, Sep 21, 2015 at 8:10 AM TheBekker<EMAIL_ADDRESS>wrote:

That makes sense, but not sure how i would accomplish this?
—
Reply to this email directly or view it on GitHub
https://github.com/formly-js/angular-formly/issues/476#issuecomment-141994072
.

--

Kent C. Dodds https://twitter.com/kentcdodds

Ahh didnt know that was possible, thanks!


cmd/go: do not skip the cmd/go tests for linux/mips64le

What version of Go are you using (go version)?

$ go version
go version go1.15.3 linux/mips64le

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="mips64le"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="mips64le"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_mips64le"
GCCGO="gccgo"
GOMIPS64="hardfloat"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/usr/local/go/src/cmd/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -mabi=64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build999960069=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I run cmd/go tests on linux/mips64le platform, the cmd/go tests all skiped.
# go test -test.v cmd/go -run=Script/ -work -count=1
WORK=/tmp/go-build534713729 === RUN TestScript
script_test.go:42: skipping external tests on linux/mips64le
--- SKIP: TestScript (0.00s)
PASS
ok cmd/go 6.613s

What did you expect to see?
The cmd/go tests all can run and  all get "PASS" result on linux/mips64le.
What did you see instead?

For the record, we started skipping them in https://golang.org/cl/33425.  We skip them because the boards we were using are slow, and in general these tests act the same on all targets, so running them on multiple targets didn't help coverage.
But I think it would be reasonable to have some way to actually run them.
CC @bcmills @jayconrod

https://farmer.golang.org/builders#host-linux-mipsle-mengzhuo
The builder(host-linux-mipsle-mengzhuo) is a 3A4000(2.0Ghz/47 bit VMA) box and it runs well on Linux/mips64le by far. It seems enough for the architecture coverage.
https://groups.google.com/g/golang-dev/c/p_4y1rxhoe4/m/keSRwlYvAgAJ

The builder isn't fast enough that we want to run more tests on it. Also, as @ianlancetaylor said, it doesn't help much to enable this test on this particular builder.
I agree with @ianlancetaylor that there probably should be a way to actually run the test on demand.

I think the skipExternal = true cases in func init should be moved into the testenv.Builder() != "" condition.
I agree that we still don't want to run these tests on the Go project's builders, but we should not assume that our builders are the only ones running the tests on these platforms.

Or, at the very least, perhaps we should use skipExternal = testing.Short() instead of skipExternal = true. That way, users can indicate their willingness to wait via the -short flag.


Byron Explorer. Misplaced Space.

A misplaced space in Text.

A misplaced space in Text.

Fixed on another branch -> PR is : https://github.com/input-output-hk/cardano-explorer-app/pull/254


RE3 Mega problem Rendering Double Screens overlapping

dunno what the problem is really or if everyones has this but on my monitor the game looks utter shit double screen overlapping lagging you cant even record gameplay because its all messed up, but in vr it looks good but its also double there too like if i look in mirror at start of game i dont just see 1 body, i see two jill body's splitt in the mirror.
So half half body's on each side of the mirror which is not what i've seen people have on youtube they see 1 body and 2 arms like it should be. i attach videos to make it simpler to understand.
I wanna mention my game is pirate version from fitgirl repack dunno if this is what causes the problems if its outdatet or not otherwise i will buy game if this is the problem for it.
https://user-images.githubusercontent.com/100847800/156568485-004822f6-4d2d-4cee-9129-b33e9dcd8ed1.mp4
Screen recording https://drive.google.com/file/d/1Han3R9d03oOKZNryrYJIdL1Y8JhgdN2s
Now it dont look like that bad in vr its all normal in vr like it should be exept that i see some stuff double example mirror or if i look at a button it Says Button A with a circle around it but its double A A next to eachother and if i look at people on youtube testing same mod they see only 1.
System Specs i run game in 2k Res all max settings
CPU 5800x
GPU RX 6800 XT 16gb
ram 32 gb 3200mhz
samsung 980 pro 1tb

Not a bug, completely normal due to how the VR rendering is done. You must record your screen with the OpenVR capture with OBS, SteamVR view, or Oculus Mirror.

Also download a newer build from here, it fixes the double vision for interaction icons: https://github.com/praydog/REFramework-nightly/releases/

Alright thats very nice that it was not a bug glad it works like it should,
and ill download that file directly and try this out really glad to get a
chance to play this game in vr im using valve index and i wanna try Re8
aswell super good work mate, appreciate that you have made this mod its
amazing stuff that hand tracking works and the depth of the 3d in the game
amazing stuff thanks again.
Den tors 3 mars 2022 kl 14:47 skrev praydog @.***>:

Also download a newer build from here, it fixes the double vision for
interaction icons:
https://github.com/praydog/REFramework-nightly/releases/
—
Reply to this email directly, view it on GitHub
https://github.com/praydog/REFramework/issues/273#issuecomment-1058057905,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYBNBOFBGWEZQ5I3GSC42STU6C7IPANCNFSM5P2MSXEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Missing word + missing link in gaming use case

The text appears to be missing the word "or" (?) and is publicly rendered in visible square quotes [ ]—I suspect a missing pointer to the url.

@njray : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good. Thanks @njray


[FLINK-12181][Tests] Port ExecutionGraphRestartTest to new codebase

What is the purpose of the change
Port ExecutionGraphRestartTest to new codebase.
Based on #8226, partially includes #7809.
Brief change log

Use TestingLogicalSlot and SimpleSlotContext instead of SimpleSlot in SimpleSlotProvider
Use SlotPoolImpl, SchedulerImpl and TestingResourceManagerGateway
instead of Instance and jobmanager.scheduler.Scheduler in ExecutionGraphRestartTest
Introduce TestingExecutionGraphBuilder in ExecutionGraphRestartTest

Verifying this change
unit tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @leesf @TisonKun

Thanks for the review @zentol ! I've addressed comments, also applied your suggestion, you can see it now as a separate commit


VS-3215 set up eslint & fix errors

https://jenkins.int.sonrisa.hu/view/CAbi Party App/job/jitsi-meet/13/console

https://jenkins.int.sonrisa.hu/view/CAbi Party App/job/jitsi-meet/14/


How to fake mouse hover over an element?

Hey,
I'm trying to trigger onmouseover of an a element.
There is a Click QueryAction but not Move action.
I've tried a bunch of things with no success:
chromedp.MouseEvent(input.MouseMoved, coords.CenterX(), coords.CenterY())

Where coordinates are retrieved evaluating JS.

Yes, the input.MouseMoved is what you would want. If you want to call the actual event handler, please note you can synthesize that event directly.

Yes, the input.MouseMoved is what you would want. If you want to call the actual event handler, please note you can synthesize that event directly.

Hi @rayrutjes , did you implemented this? Could you please show the example code? Thanks

@shadow1163 Like what Kenneth has said, it should be easier to synthesize the event directly. Here is the javascript to dispatch the mouseover event to the first participant avatar on this page, you can run it in the console to see what will happen:
document.querySelector('.participant-avatar').dispatchEvent(new Event('mouseover'))

Then run the javascript with chromedp.Evaluate:
package main

import (
	"context"
	"log"
	"time"

	"github.com/chromedp/chromedp"
)

func main() {
	opts := append(chromedp.DefaultExecAllocatorOptions[:],
		// disable headless mode so that you can see what happen
		chromedp.Flag("headless", false),
	)
	ctx, cancel := chromedp.NewExecAllocator(context.Background(), opts...)
	defer cancel()

	ctx, cancel = chromedp.NewContext(ctx)
	defer cancel()

	// run task list
	var res bool
	err := chromedp.Run(ctx,
		chromedp.Navigate("https://github.com/chromedp/chromedp/issues/710"),
		// just to make it easy to find what's happened on the page
		chromedp.Sleep(2*time.Second),
		chromedp.Evaluate(`document.querySelector('.participant-avatar').dispatchEvent(new Event('mouseover'))`, &res),
	)
	if err != nil {
		log.Fatal(err)
	}

	// prevent it from closing the browser immediately
	time.Sleep(time.Minute)
}

@ZekeLu Thanks very much, I will try it.

For anyone seeing this issue, mouse hover is not a trusted event and so can't be dispatched by java script.
See here / here


Refactor calibration, clock, and sercom modules for SAMD51/SAME54

These two device families are essentially identical other than a handful of small difference, all of which can be handled with #[cfg()]. This pulls out the calibration, clock, and sercom modules into the common::thumbv7em module.

@mvniekerk would you be able to test this out on the SAME54 by any chance?

Is something blocking this PR (apart from the merge conflict, that is not that hard to resolve)? I think it is really helpful and reduces code duplication a lot without breaking anything.
I wanted to write a PR that adds more variants of the SAME series, but that would be a PITA without this PR.

I was hoping to get a test on the SAME54 for the one line mentioned above, and then forgot about it 😁 @sajattack once I rebase this are you okay with merging it as-is?

Okay great, thanks. I'll try to get this done this weekend. There has been a new PAC added since I opened this PR, so unfortunately it's going to be a bit more involved than just rebasing, but still shouldn't take too long.

I managed to hammer it out during my lunch break, I think it should be fine but I have yet to test on actual hardware. Will do that after work.

Looks good at first pass. Also spotchecked SERCOM5 and LGTM.


fix: fix the flag check

The type of this PR is: fix
Description
Fixes the flag check, had mislabeled the fastlane action, cleans up the script a little.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Fix the feature flag biweekly check - Brian

This PR contains the following changes:

Dev changes (Fix the feature flag biweekly check - Brian)

  Generated by :no_entry_sign: dangerJS against 950101a233fed2bd9f4ec349a241155b715ddae8


Refactor AMP PD dataset "Browse Data" button

Remove both existing "Browse Data" buttons on Terra datasets page and
add new "Explore AMP PD" button which points to the new AMP PD
Featured Workspace. This increases discoverability of the new "home" for AMP PD resources in Terra, since all viewers with Terra accounts (not just those with AMP PD access) can view the AMP PD Featured Workspace.
https://screenshot.googleplex.com/4SS8mPMe6yWJGoW

From an AMP PD program perspective, this looks great.
Really like having the new Featured Workspace, which provides a lot more detail to both existing AMP PD researchers as well as Terra users interested in Parkinson's research. Being able to point people to the Featured Workspace (which also has links to the data browsers) is a better user experience.
Thanks Emma!


[WIP] Update eslint and prettier

Fixes #79.
Work in progess. It changes the configurations to work with the current project setup (both JS and TS).
The current version is mostly based on iamturns' eslint typescript wrapper with similar configurations.
I'll keep on update it as it run into more issues but this is what I am using locally right now.

The following rules should be reviewed/addressed before this can be merged:
In JS/JSX
"react/prop-types": "off",
"react/jsx-props-no-spreading": "off",
"react/forbid-prop-types": "off",
"no-use-before-define": "off",
"jsx-a11y/label-has-associated-control": "off",
"no-shadow": "off",
"import/prefer-default-export": "off",
"arrow-body-style": "off",
"react/require-default-props": "off",
"import/no-cycle": "off",
"react/destructuring-assignment": "off",
"import/no-extraneous-dependencies": "off"
In TS/TSX
"react/jsx-filename-extension": "off",
"no-use-before-define": "off",
"react/require-default-props": "off",
"import/prefer-default-export": "off",
"no-underscore-dangle": "off",
"object-shorthand": "off",
"no-return-assign": "off",
"camelcase": "off",
"@typescript-eslint/camelcase": "off"


Add totally wrong code to find sx:structure.  No augment yet.

Try a way to get at the sx:structure

Covered by #6.
(The sx:structure code still needs to be fixed, in #6, then.)


Some example scripts rely on tests and are thus broken for website

A couple of the current example scripts are broken because they relay on importing modules within tests/:

examples/example_convert.py
examples/example_spherical_harmonics.py

These have been disabled for now and should be easily fixed once #43 is done.

Closed by #126.


Add stub template for App Runtime Platform WG

TODO before merge:

Identify leads for WG
Identify initial goals and scope for WG
List main technical assets for WG

I would love to see https://github.com/cloudfoundry-incubator/haproxy-boshrelease promoted to the cloudfoundry organization.
I believe it is the only "Technical Asset" in the list that is still under incubation. At ~600 commits and numerous production deployments, it seems ready to hatch 🐣.

@Gerg SGTM! The TOC has been discussing merging the entire cloudfoundry-incubator org into the cloudfoundry org, likely after a long-overdue round of repo pruning/archival.

FYI @aminjam @Benjamintf1 @ameowlia @gcapizzi @geofffranks @domdom82 for feedback and suggestions for approvers/leads.

@emalm I agree. I think we have a list of things to do besides clicking the "transfer repository" button. I volunteer for taking ownership since @geoffranks phased out of the project quite some time ago. I might need to have the rights to create a repo under the cloudfoundry org, though.

@ameowlia I added some initial goals and scope to this WG's draft charter and proposed you as a lead in the group. Could you please provide feedback on them and work with the TOC to establish a good initial charter for this WG? Thanks!

I'm not sure how many approvers we are expecting in each area. I'm happy to take a "more is more" approach and start with high trust.
Suggested Approvers (if not Tech Leads 👀 ):

@domdom82
@46bit
@stefanlay
@aminjam
@Benjamintf1
@gcapizzi
@geofffranks
@selzoc
@Gerg
@pivotalgeorge
@mkocher
@acrmp
@jrussett
@reneighbor

I'd also like to nominate Ivan Hristov ( @IvanHristov98 ) from SAP as an approver for the Diego repos.

@ameowlia I've updated the PR draft with those additional approver candidates. Please let me know whether you think the charter draft is ready for the TOC to review officially or whether there should be any more changes before that!

@loewenstein Good point, I was waffling on whether to include K8s infrastructure in the goals as a longer-term view, but I think it's better to remove it for now. Then there's no update needed if the new CF on K8s WG ends up being long-lived, and if we do end up merging areas from it into the other App Runtime WGs then that should prompt a change to goals and scope anyway.


Verify convergence of heat-driven cavity

We tried this briefly (and unsuccessfully) in https://github.com/geo-fluid-dynamics/phaseflow-fenics/blob/master/notebooks/Convergence-HeatDrivenCavity.ipynb

This could be obsolete if we perform a proper MMS verification (see issue #158 ) of the general problem.


OOM during LoRA training using data/toolllama_G123_dfs_train.json

Hi, I'm trying to reproduce the result by Training a LoRA version using the training data provided: data/toolllama_G123_dfs_train.json,
It's so bizarre that the machine got quickly OOMed (CPU memory OOM, instead of GPU memory), any idea on what might go wrong?
 We're using a much longer sequence length (8192) than the vanilla LLaMA, and the memory would be thus larger.
However, LoRA can be trained using 2 40G A100 GPUs (we've tested it), the codes are optimized for GPU not for CPU, we'll check details later why CPU costs so much memory.

Yea, thanks for the quick response, I'm using 8 3090 GPUs so it shouldn't be a problem with GPUs, It's just surprising that it cost more than 200 GB of CPU memory, the short sequence train.py gives me the same CPU OOM too.

Yes with the device map added, GPUs are utilized when loading the pre-trained model, thanks for the update!
I got another blocker though, as you mentioned this training process has been tested on 2 40G A100 GPUs, but I received OOM on GPU where I got 8* 24GB GTX 3090 on my host machine, this doesn't look right to me.
To mitigate this, I've been reducing the batch size to 1 and using ds_configs/stage3.json (with CPU offload).
Is there any other method I can use to reduce the GPU memory usage?


RRule object is not initialized with dtstart

When accessing the rrule of an event, the dtstart of the rrule is not set, so I had to do this:
  ev.rrule.origOptions.dtstart = ev.start;
  ev.rrule = ev.rrule.clone();

Only then could I safely use the rrule
recurDate = ev.rrule.between(currentDate, dateTo);

I also stumbled across this one and made some changes, which work for me. From my point of view this is still a hack, as I don't like the changes I've made in ical.js/addTZ(..). Maybe somebody has a better idea, how to implement it.
The main problem I found, was that you can't depend on the position of the "DTSTART" if this comes before the "RRULE" then the #48 might work, but I had problems with it as the fix will not update the already created a "BYMOUNTH" and "BYDATE" in the rrule cache.
On the other hand if "DTSTART" follows RRULE #48 might never work, so the same fix done in "RRULE" handling needs also be done when DTSTART is parsed.
As said previously I consider this quite a hack, but as this problem is around nearly a year I though sharing might be helpful. If required/wanted I can created a pull request, but the code might need some additional testing.

I ran across this problem also.   The fix for #21 does not completely fix #45 - in that ev.rrule.between() does not seem to work properly...  even though rrule.options.dtstart seems to be set, it's not being honored. (Perhaps ev.rrule.origOptions is being used instead?)
I independently developed my own fix, which is shown below.   This code fixes the problems that I was experiencing, but potentially suffers the same deficiency that @Angus71 noted, namely that if "DTSTART" comes after the "RRULE", then it should not work.  (and if RRULE includes a DTSTART field it will be overwritten, although this is easily fixed.)
ical.objectHandlers['RRULE'] = function(val, params, curr, stack, line){
  var rule = line.replace("RRULE:", "");
  rule += ";DTSTART="+curr.start.toISOString().replace(/[-:]/g,'');
  rule = rule.replace(/\.[0-9]{3}/, "");
  curr['rrule'] = rrule.fromString(rule);
  return curr
}

The DTSTART/RRULE sequencing issue noted by @Angus71 (and later me) should probably be fixed by moving the code that patches up the RRULE with a default start date into the objectHandler for 'END'.  I'll try this tonight.

@risacher Any luck fixing this?


Crash on switching off the internet

Describe the bug
As soon as the internet connection is closed, handleOnConnectionFailed handler is called and the app crashes.
To Reproduce
Steps to reproduce the behavior:

Create a View with
Start streaming.
Switch off the internet.
Application crashes as soon as the handleOnConnectionFailed callback is received

Expected behavior
Streaming should stop but the application should not crash.
Smartphone (please complete the following information):

Device: Pixel 6
OS: Android 13
React Native v0.70.6
Package version 0.4.4

Stacktrace:
Link to stacktrace

Hello, @rranjan14
I tried to reproduce that issue but my app didn't crashed. I updated android package to 2.2.2 by 0.4.5 version.
Can you try it again?

I did try. Same result again. I get Error send packet, Broken pipe message  in the onConnectionFailed handler, and then it crashes.

I've tried to reproduce your issue but it looks like its not crashing. Maybe it's about your device. I think looking at logcat outputs will help
https://user-images.githubusercontent.com/42299721/211173192-1ba65ad0-6ca1-449e-bebb-95a95ec8b508.mov

I'll verify once again and attach the log file if i encounter the same issue.

https://user-images.githubusercontent.com/47914095/211361641-52f9bd6d-1c65-42bf-8d1f-1834ef138d08.mp4
Not sure of the behaviour on emulator, but on real device, it still is crashing.

Yes, can you give me the Logcat output of the crash timestamps?

@rranjan14 I'm closing this issue as resolved. You can open it again if it happens again.


fix: docker build on tag broke due to cache

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[ ] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[ ] Label: To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
Fix missing cache ref error when building for a tag: https://github.com/open-webui/open-webui/actions/runs/9335788157/job/25695587855

Thanks!


Imitating the DOM tree

The document object model (DOM) is essentially a tree (data structure), containing nodes with a number of optional attributes such as id or class.
Each node in the tree can have one parent and several children and these properties connect the nodes together to form a tree.
Consider this boilerplate HTML (left) and its corresponding tree (right):

    <title></title>


Make the server send the available apps

Currently, apps are hardcoded in the Client. The server should handle this.

This issue is fixed in Vertex v0.12 (see 13c193c04a59faeee215dcb9a22546b93d9cb10a)


How to download via SFTP after JSON configuration

Hi. Sorry for the novice question, but how do I actually go about and start downloading files to my local folder? I set up the config JSON file, and I go to the top-level directory, right-click and "download selection". Then, I get a spinning octocat to the right of the Atom application that seems to spin forever. Any ideas?

I am having a similar issue, after setting up the json config, I cannot connect to any of my servers. How did you setup your config file?

Same here. It just says "Loading" endlessly

Hi all,
Indeed, the loading message seems to do nothing, I will fix this in the next release.
There is another problem ?
Thank you for using my package.


GraphQL error: Cannot return null for non-nullable field PromptChoice.value

Version
3.0.3
Reproduction link
https://www.npmjs.com/package/vue-cli-plugin-vuetify
Node and OS info
node 8.11.3, yarn 1.9.4
Steps to reproduce
Create a new project in vue ui, use default preset, add vuetify plugin
What is expected?
Vuetify plugin can be configured and installed sucessfully
What is actually happening?
Error in console:
Error: GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
GraphQL error: Cannot return null for non-nullable field PromptChoice.value.
    at new t (ApolloError.js:46)
    at Object.next (QueryManager.js:194)
    at Object.handler (client.js:144)
    at e.processReceivedData (client.js:511)
    at WebSocket.client.onmessage (client.js:465)

Also non-binary (for example rawlist) options are not displayed on the configuration page

vue invoke vuetify from command line works fine, that's why I'm assuming that it's not the bug in the plugin, I may be wrong though

Sorry for the late reply. This issue seems no longer reproducible with the latest versions of Vue CLI & vue-cli-plugin-vuetify. I guess it has been fixed at some point.


Add Gwion

Language name
Gwion
URL of example repository
https://github.com/Gwion/Gwion
https://github.com/Gwion/gwion-benchmark/
URL of syntax highlighting grammar
https://gwion.github.io/Gwion/
Most popular extensions
.gw
Detected language

This appears to be a hobby language with very few users on GitHub. Closing.
Ref: https://github.com/github-linguist/linguist/issues/6994#issuecomment-2287888666


[CARBONDATA-2056] Hadoop Configuration with access key and secret key should be passed while creating InputStream of distributed carbon file.

…
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[X] Any interfaces changed?
None
[X] Any backward compatibility impacted?
None
[X] Document update required?
None
[X] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
Not possible to add test case.
[X] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3273/

closing this PR as per @ravipesala  this fix will be handled for all the I/O operation
together with S3 support implementation


Refactored hydration of job entities

refs gh-256

There are still some missing unit tests. I will continue with facet implementation after I complete the unit tests.

Coverage decreased (-0.3%) to 34.063% when pulling eedf0a55ed0728b1e7d7a68ca932c0128616a79a on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

@TiSiE great!

Coverage increased (+0.1%) to 34.477% when pulling 690c1d3e111d676b58a96c18c977a7c703273571 on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

Do you want me to implement filtering by clicking on region facets? If yes, what should happen on clicking a facet region link?

Coverage increased (+0.3%) to 34.641% when pulling 7209ad8922969bcfa17f358a834eeec86f051eac on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

I copy the mail from @cbleek here for completeness:

yes, please implement it.
https://www.stepstone.de/ has made it quite good. If you click on a region, a new search is done. The query is extended by "AND region=' and the filtered Region is shown. So the user can remove the filter.
if you click more than one region, the query is extended by AND (region= OR region=)
Doing the "OR" Search in Solr can be done by: regionList:(Bayern OR Hessen)
https://yawik.org:8443/solr/YawikJobs/select?fq=regionList:(Bayern OR Hessen)&indent=on&q=*:*&wt=json

Maybe we should normalize the facets entity. So switching to another module providing similar features is easy (e.g. ElasticSearch Backend)

@TiSiE I would wait with facets normalization until we finish the current Solr implementation and start implementing another backend providing similar functionality

@fedys You're right, sometimes I am a little overeager...

I will complete unit tests as soon as you tell me you are happy with the current implementation of the facet filtering.

Coverage increased (+0.2%) to 34.538% when pulling b17803d6e81b6f61eb4cb3f334b037b3cfd3202b on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

Coverage increased (+0.2%) to 34.556% when pulling b348d75ff6580e36ea5356c90ac8c8ab28407301 on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

I noticed that the behavior of facet counts is not proper if an user checks any facet checkbox. A facet tag excluding  has to be applied to fix it. Do you want me to apply the fix?

@TiSiE I cannot reproduce it in my environment (PHP 5.6.26-1+deb.sury.org~trusty+1). What PHP version do you have? What Solr source do you use?

@TiSiE Maybe it can be related to this one

Coverage increased (+0.2%) to 34.536% when pulling c622a2998f8a7f421d3f8b0212e9dfb11deab5fc on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

@fedys yes, this is exactly the error. I'm using PHP 5.5.9-1ubuntu4.17and pecl-solr 2.4.0

@TiSiE okay, I will fix it.

Probably this issue: https://bugs.php.net/bug.php?id=67300&edit=1
Cast an array with empty keys to an object DOES NOT create an error, but trying to access the empty key (when iterating, eg) produce the Notice.
I can reproduce this behaviour in my PHP:
php > $a = ['test' => 'ok', '' => 'error'];
php > $b = (object) $a;
php >
php >
php > echo $b->test;
okphp >
php >
php > var_dump($b);
PHP Notice:  Illegal member variable name in php shell code on line 1
PHP Stack trace:
PHP   1. {main}() php shell code:0
PHP   2. var_dump(...) php shell code:1
class stdClass#1 (2) {
  public $test =>
  string(2) "ok"
  public $ =>
  string(5) "error"
}
php >
php >
php > foreach ($b as $k => $v) { echo "$k: $v\n"; }
test: ok
PHP Notice:  Illegal member variable name in php shell code on line 1
PHP Stack trace:
PHP   1. {main}() php shell code:0
php >

Coverage increased (+0.2%) to 34.532% when pulling 2bac0cd1cd24fea16d30821371b86ba2bc0e3e58 on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

Coverage increased (+0.2%) to 34.531% when pulling 0b39359c2e29bda2906a0675d29d7897f3a920c4 on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.

@TiSiE great! I am going to complete unit tests.

Coverage increased (+0.5%) to 34.875% when pulling a1b6054e43c97471cfd2f8dca1843ee960ab6dca on fedys:issue-256 into 133a1c9918a2c247eadf23fc24c0137519361244 on cross-solution:develop.


Firefox 79: Return of the Shared Array Buffer?

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/79

SharedArrayBuffer has been re-enabled in a post-Spectre-safe manner. It is available to cross-origin isolated sites (bug 1619649).

Also see https://github.com/mdn/browser-compat-data/pull/6356.
However, https://tests.caniuse.com/?feat=sharedarraybuffer remains red for 79.0b7 as well as 80.0a1, so maybe we need partial contrary to BCD, to represent cross-origin isolated sites only …?

They followed up:

To cross-origin isolate your site, you need to set the new Cross-Origin-Embedder-Policy (COEP) and Cross-Origin-Opener-Policy (COOP) headers.

HTTP

Cross-origin isolation has been implemented using the new Cross-Origin-Embedder-Policy (COEP) and Cross-Origin-Opener-Policy (COOP) headers. This allows you to access powerful features such as SharedArrayBuffer objects and unthrottled timers in Performance.now().

=>

https://caniuse.com/#feat=mdn-http_headers_cross-origin-embedder-policy
https://caniuse.com/#feat=mdn-http_headers_cross-origin-opener-policy

So, what do we want for Shared Array Buffer (and Performance.now())? Partial support? I'm leaning towards y and a note, as those headers seem to be the new normal?

@Schweinepriester Yeah, I think y and a note seems appropriate. Thanks!

I was about to submit a duplicate PR for this :)
I'd suggest removing the #2 footnote altogether, as it was only meant to indicate that SAB is only enabled by default in Nightly, which is no longer the case now that it made its way into Beta and will be in Firefox 79 Release.

A link to this article would be great for context: Mozilla Hacks - Safely reviving shared memory

Done I think, tried to incorporate all feedback :)
While we have

https://caniuse.com/#feat=mdn-http_headers_cross-origin-embedder-policy
https://caniuse.com/#feat=mdn-http_headers_cross-origin-opener-policy

already, we could make cross-origin isolation a feature on its own, like https://chromestatus.com/feature/5953286387531776, making it somewhat easier to refer to…

Looking good, thanks all!


pull request for e2e test at 01/11/2017 02:15:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


vpn Segment Needs macOS Support

Per @onaforeignshore's comment in #539: https://github.com/bhilburn/powerlevel9k/pull/539#issuecomment-305855991
The vpn segment currently does not support macOS. @onaforeignshore offered a way to implement this in #538:

On macOS, VPN IP address can be found using:
ifconfig ppp0 | grep "inet " | grep -v <IP_ADDRESS> | awk '{print $2}'. If VPN is inactive the result is ifconfig: interface ppp0 does not exist

This simply needs to be conditionalized into the vpn segment code. If someone with a Mac is interested in taking this on and testing it, that would be great.
Stretch goal: unit tests for this segment =)

Hi @bhilburn,
just sharing my thoughts on this. The solution proposed by @onaforeignshore will work only with PPTP VPNs, while using other common tools (for a Mac OS user), for example OpenVPN or Tunnelblick, will result in having net ifaces with different names - respectively tun0 and utun0.
I would think of something more generic, then I'll be glad to help with the troubleshooting :)
Thanks again for the great work everyone's doing here!

@guidoilbaldo - That's good to know, @guidoilbaldo! Thanks so much for the input! It's much appreciated.

Hi, I made a test on tunnelbrick and it works; the default value is "tun" but it can be overridden in zshrc.

I am on a issue-cleaning spree. This issue hasn't had motion in quite some time, and so I am closing it out due to inactivity. If anyone would like to re-open it because they feel it is un-resolved and is something they care about, please feel free to re-raise the discussion!


adding exception rule to "Mead 2020 via Chan 2019"

Do we want to add a rule that in sourcelookup check that says to ignore anything before the string "via"?
That way we can have sources like "Mead 2020 via Chan 2019".

Seems based on discussions elsewhere that this is a nofix


[Docs] Expand documentation

Various edits to the documentation:

Add a description for select()
Hook the new json() function into the documentation
Put some basic description of the 'chat' roles into the docs
Hook AzureOpenAI into the docs

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

Project coverage is 63.57%. Comparing base (f66a67c) to head (e35a1ea).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #750      +/-   ##
==========================================
- Coverage   68.06%   63.57%   -4.50%
==========================================
  Files          53       53
  Lines        4005     4005
==========================================
- Hits         2726     2546     -180
- Misses       1279     1459     +180

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

LGTM