Added an error message to the assert in jax_utils.prefetch_to_device(*)

This error message should hopefully help users understand where the error comes from when setting up their input data pipeline.

Codecov Report

Merging #346 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #346   +/-   ##
=======================================
  Coverage   79.04%   79.04%
=======================================
  Files          34       34
  Lines        2248     2248
=======================================
  Hits         1777     1777
  Misses        471      471

Impacted Files
Coverage Δ

flax/jax_utils.py
62.37% <0.00%> (ø)

Continue to review full report at Codecov.

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


[APPM-1631] Tags should be removed from mobile app create page.

Tags should be removed from the mobile app create page.Reference: https://wso2.org/jira/browse/APPM-1631

App manager component is being rewritten for IoT server, and this will be addressed there. Hence closing the issue.


What are different type of sorting supported in microsoft-fhir server

Question
What are different type of sorting supported in microsoft-fhir server
Description
We want to sort by patient name but it gives result as not supported. Can you give me link as what are different types sorting supported

Hi @brendankowitz,
If we combining 2 resources like ImagingStudy and Patient then sorting on patient name not working

@Sameer2810 - Are you running above query on Azure API for FHIR ?

@EXPEkesheth - No I amusing Microsoft fhir server version 2.2.0

@Sameer2810 - What is the persistence layer used for Microsoft fhir server version 2.2.0?

No response and, hence closing the issue. Please reopen for any additional question on the same topic.

@EXPEkesheth  Using CosmosDb for persistence layer

Hi @Sameer2810, there isn't currently support for sorting via a chained parameter, it must be a search parameter that is indexed on the primary resource type

Hi @brendankowitz, if I want to apply sort on chained resource then is there any alternate way we can apply sorting

@Sameer2810 - Unfortunately there is no alternate way today. One suggestion you could try is to look for Patient resources with references to ImagingStudy resources (basically flip the query).

@EXPEkesheth - There is reference in ImagingStudy for Patient but in Patient there is no reference for ImagingStudy so how can we flip the query or you are saying something different


Mods for mac

I want to make a mod form my Terraria, i watched a tutorial video step-by-step and when i tried to build my mod it crashed. Can somebody help please?(using mac)

I don't think this is the place for this kind of issue. You should post this on the forum page, or try to get help on discord.

Okay first of all, when you need help with an error, post the actual error and code. We can't do anything if we don't see exception logs and code used.


Add automatic install and update

Thanks for the PR but I think installation scripts should be kept outside of this repo. However, feel free to maintain your own fork if you wish to add them.


Are there any tools that can serve AQLM quantized models?

Are Ollama or other frameworks or tools capable of serving AQLM quantized models?

text-generation-webui should support it in the dev branch.
vllm integration is on it's way as well.

lorax on it's way too


Handle react-dom/server minified version

Ref: https://github.com/zeit/next.js/pull/1855
That's simply because it has no effect since we don't run webpack on the server.
And for the server, file size difference doesn't matter a lot.

Production React makes a big difference in the server. See this comparison and this thread for info.

As mentioned in this comment (https://github.com/facebook/react/issues/8788#issuecomment-277408131) it's impossible to load the minified version in the server side. (Specially we don't use webpack in the server)
So, we need to wait for the next version of React which fixes this issue (or the root slowness)


transfers/fee endpoint is returning Application error in PHP

Hello i am calling endpoint 'https://api.flutterwave.com/v3/transfers/fee' but getting response {"error_id":"ERRNO994507623T1678851511558","message":"Application error. Please contact support","code":"app_error"}  for the last 3 days
my PHP code is;
    $ch = curl_init();     curl_setopt($ch, CURLOPT_URL, 'https://api.flutterwave.com/v3/transfers/fee');     curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);     curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');     curl_setopt(         $ch,         CURLOPT_POSTFIELDS,         [             "type" => "mobilemoney",             "amount" => 2000,             "currency" => "UGX",         ]     );     $headers = array();     $headers[] = 'Authorization: Bearer ' . $fl_secret;     $headers[] = 'Content-Type: application/json';     curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);     $response = curl_exec($ch);     if (curl_errno($ch)) {         mylog('Error:' . curl_error($ch));         echo '{"status":"error","message":"' . curl_error($ch) . '"}';         curl_close($ch);         exit;     }     curl_close($ch);

Hi @Philiptebandeke Thank you for choosing Flutterwave.
Please note that the endpoint hands get request and as a result it expects query parameters and not CURLOPT_POSTFIELDS . please kindly  add the query parameters and try again.
example : https://api.flutterwave.com/v3/transfers/fee?amount=:amount&currency=:currency&type=:momotype

Thank you it is now fixed


result.body is empty in Node but result.text is present

I am using superagent in https://github.com/tkesgar/miyako for both Node backend and frontend. However, I found a problem when running this part of server code:
superagent.get(`${ENDPOINT}${id}`)
    .query({ access_token : TOKEN })
    .query(fields ? { fields } : {})
    .query(data)
    .then(result => {
      // callback(result.body)
      callback(JSON.parse(result.text))
    })
    .catch(error => errorCallback(error))

In the promise handling, result.body is {}, but result.text contains the full endpoint response (endpoint is Facebook Graph API). .buffer(true) doesn't work (result.body is still empty), and content-type is already JSON.
I was able to get it working with JSON.parse(result.text), though. Also, I can use result.body on client-side without problems.
I'll try to reproduce the problem if I have some time.
Environment:

Node 6.3.0 64-bit
Windows 10 64-bit

Please send the full HTTP request and response headers if you can. That will help us troubleshoot. Auto-parsing of response bodies is primarily based on the Content-Type header in the response.

Node requests seems to set the wrong content-type.
curl-ing the request (to Facebook Graph API) returns the correct content-type:
curl -i -X GET "https://graph.facebook.com/v2.7/335148063288907?access_token=<token>"

HTTP/2 200
access-control-allow-origin: *
etag: "ea63bae8487b4f133cb3877b366e553a01fd2e35"
pragma: no-cache
cache-control: private, no-cache, no-store, must-revalidate
facebook-api-version: v2.7
expires: Sat, 01 Jan 2000 00:00:00 GMT
content-type: application/json; charset=UTF-8
x-fb-trace-id: Bfie5260Olg
x-fb-rev: 2602612
x-fb-debug: /J4vr6vfR2BJdlDT1tr6SSDYSciqKO+KEONMWkUfYUoZg/TS3uQkmA4y5PHNZeY1pq9CMhKUj7e26oSZQps6yg==
date: Wed, 05 Oct 2016 00:29:01 GMT
content-length: 66

{"created_time":"2013-10-01T18:01:15+0000","id":"335148063288907"}

I run both this on Node and browser (result is attached):
request.get('https://graph.facebook.com/v2.7/335148063288907')
.buffer(true)
.query({ access_token : <token> })
.then((success, failure) => {
  console.log(JSON.stringify(success, null, 2))
})

content-type is application/json; charset=UTF-8 in browser, but text/javascript; charset=UTF-8 in Node.
On an unrelated note, I can't use .buffer(true) in browser, but I removed it and it still works.
browser.txt
server.txt

I've found this is because Facebook is sensitive to the Accept header, and browsers and curl force their own default one, but superagent doesn't.
Adding .accept('json') to the request happens to do exactly what it should, and makes FB send JSON.

So given this, I wonder what should we do:

add more documentation/warnings/hints about use of .accept('json')?
try to parse text/javascript as JSON? What if it fails to parse?

+1 on documentation. -1 on presumptive parsing

I think adding docs should be enough.

The docs mention using req.header('Accept', 'application/json') but this does not seem to be part of the API anymore. I'm using req.set now, though am often receiving a "Bad Request" error from Facebook (but not always).


SAMZA-2316: Validate that all non-default value fields in output schema are set i…

…n the projected fields.

Nit: copy the words in the description to the title?


Updates

Fix broken centos package repo links.
Add libusb linux library dependency to support EPICS module builds.

@gilesknap for your review


Add Survey Question Types: Survey (likert) & Select (drop-down)

Add the Survey and Select components in form.io

Hey team! Please add your planning poker estimate with Zenhub @saravanpa-aot @VineetBala-AOT


Binarization: Add basic infrastructure, functionality and CLI binding

https://stackoverflow.com/questions/26185550/text-binarization

To be solved in https://github.com/OCR-D/ocrd_kraken


PacReq: firefox

Types
-bin (Binary release of the package)
URL
https://download-installer.cdn.mozilla.net/pub/firefox/releases/101.0.1/linux-x86_64/en-US/firefox-101.0.1.tar.bz2
Building guide
https://support.mozilla.org/en-US/kb/install-firefox-linux
Additional context
N/A

Linux Mint publishes builds of Firefox that I expect are fully compatible with Ubuntu, but they are always based on LTS.

Also available from PPA mozillateam/ppa.

Firefox is already available, it should lock this request.


Azure Runtime Extension for 2.1 preview2

I'm trying to deploy an app to Azure that has been upgraded to preview2, but the Core Runtime Extension in Azure is preview1. Although, the Core Extension is on preview2.

Should preview2 be available for the Runtime? If not, is there a workaround?
Thanks!

FYI: The site extension is actually developed out of http://github.com/aspnet/AzureIntegration .
@pakrym do you know what the status is with the Site Extension for preview 2?

It's published just got renamed: https://www.nuget.org/packages/AspNetCoreRuntime.2.1.x64/2.1.0-preview2-final

Thanks guys! I appreciate it.


Skau811 favlist custom order frontend

This PR closes #53 by completing the last task of ordering the favourites list in a custom order.
Details of Changes:
Front-end Adjustments: Updated the current interface components to be compatible with the updated favourites list data structure.
Ordering Feature: Implemented  front-end allowing users to manually order their favourites. Also an attempt has been to update theme customisation feature to ensure the background-image changes according to first movie in the list.
Minor Styling: Incorporated minor CSS enhancements related to the favourites functionality to improve the user experience.
Note for contributors who have already cloned the repo, make sure to run npm run installAll after pulling from main, so that dependencies can be easily updated.
Testing/Screenshots are as follows:
Favourites list with the sort-by drop-down menu

After reording by top rated:

Other minor CSS changes:
Add to favourite button (The use of icons are better way of giving feedback to users instead of only a label text change)

Favourites page when the list is empty:

Hi Sukhleen, thanks for adding these changes in. From my testing, the features match up with what you've described, so we're all good on that end! Unfortunately, I did actually ran into a small issue on my end (seen in the screenshot below) when trying to run the project to test it.

It was an easy fix, as once I ran npm run installAll, I no longer encountered the error. Merging this PR shouldn't be an issue for people who are cloning the repo for the first time, as they'll be running npm run installAll when they set it up anyway. But for people who have already cloned the repository, I'm thinking that perhaps if you could add a small note in the PR and/or a tag on it (or any other method you deem suitable) to inform people who have already cloned the repo to make sure they execute npm run installAll in the terminal, then it should prevent other contributors from running into this issue. Once this is done, I'd definitely be happy to merge it in! Outside of this small import issue, the PR itself is excellent, and adds some awesome functionality and styling to enhance our website - thank you very much!

Hi Vishva,
Thanks for your review and highlighting the dependency issue that might happen if existing contributors pull from the main. As requested, I've updated the PR description with a note about running npm run installAll. I have also created a new label for the same and added it to my PR. This should guide other contributors and prevent future issues.
Thanks again for your feedback, it is highly appreciated.


[fix] favicon.ico support

Fixes #3525 by not returning 404 if favicon.ico is requested. I'm not quite sure why this line was there in the first place but I think there is now good reason for it to be there.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

It was there for a good reason — previously, we were using Vite's static asset middleware, which meant that if that line was reached it meant that the file didn't exist. We removed that middleware because it was problematic when you had a paths.base option.
Since browsers automatically request favicon.ico if you don't specify an alternate <link rel="icon">, this tends to result in a lot of console spam.
Updated the PR to reinstate the check, but moved it below the block where static assets are handled.

This check for /favicon.ico is still preventing endpoints from running.  Currently there is no way to have an endpoint /favicon.ico.js to run on /favicon.ico, it just gets 404.

Since browsers automatically request favicon.ico if you don't specify an alternate <link rel="icon">, this tends to result in a lot of console spam.

It still results in a lot of console spam for API endpoints. Because they don't have a <link rel="icon"> tag.
Why don't we just put a default .ico in the static/ folder? Or can it be generated?


Add Sysbox as an option to run Kubernetes inside unprivileged containers.

Sysbox is an open-source container runtime (similar to "runc") that supports
running VM-workloads such as Docker and Kubernetes inside unprivileged containers or pods.
Sysbox containers always use the Linux user-namespace for isolation, plus
specially crafted proc and sys filesystems, some syscall interception,
filesystem ID-mapping, and more.
It's possible to run Kubernetes, K3s, K0s, inside containers or pods deployed
with Sysbox. This commit aims to make the Kubernetes community aware of this
option.
Signed-off-by: Cesar Talledo<EMAIL_ADDRESS>

/check-cla

/check-cla

Not sure why the "cla/linuxfoundation" check failed, as I've signed the CLA and the EasyCLA checker passed.

@ctalledo : Please sing the CLA

/check-cla

Hi @divya-mohan0209, thanks for the review.
I've added the {{% thirdparty-content %}} tag to the section I added.
With regards to the CLA, I"ve signed it a few days ago, not sure with the cla/linuxfoundation checker is not picking this up, but as you can see in the 3rd comment of this issue, the EasyCLA checker did pass.
I've tried retriggering the cla/linuxfoundation checker by creating a comment with /check-cla, but it does not seem to work.
Thanks again!

We're switching between two bots for the CLA signing
https://github.com/kubernetes/website/pull/31330#issuecomment-1012495785 is the instructions that you need to follow right now.

Hi @sftim,

#31330 (comment) is the instructions that you need to follow right now.

Yes, I've done this already (few days ago) but the cla/linuxfoundation checker does not seem to pick it up.
I just clicked on the link again to double-check, and takes me to a Linux Foundation website that confirms that I am authorized to contribute code through my membership with "CNCF - Nestybox, Inc." (Nestybox is the company I work for). So I am not sure what am I doing wrong here. Sorry for the trouble.

Hey there! @ctalledo, looks like you haven't signed the CLA yet. Could I please have you do that? https://github.com/kubernetes/community/blob/master/CLA.md

Hey there! @ctalledo, looks like you haven't signed the CLA yet. Could I please have you do that? https://github.com/kubernetes/community/blob/master/CLA.md

Hi @jimangel, I did sign the CLA (see this comment) but for some reason cla/linuxfoundation checker is not picking it up.
I tried re-triggering it with /check-cla but it did not help :(

Hi @ctalledo Thank you for your contribution.
I might have a probable solution to this  problem (though not sure of it and there is no harm in trying it): Please try posting the comment "I signed it" to the PR—this is needed for the system to recheck your contribution authorization. Thanks.

If you don't mind trying that @ctalledo, you could try opening a brand new PR with the same commits (maybe on a new branch)?

I signed it

Hi @Babapool,

Please try posting the comment "I signed it" to the PR to recheck your contribution authorization. Thanks.

I did this but it does not appear to help.
I'll follow @sftim advice and re-open a fresh new PR, with the hope that this time the CLA checker will pick it up.
Closing this PR now, will open a fresh new one soon.
Thanks for the help.


ERROR: Technical problem during trying to connect to roundcube server, Unable to determine network-status due to technical problems.

Dear hypery2k,
I am having trouble following the guide on app.owncloud.com.
I have mostly setup as it was requested just my setup is a bit different.
I have modified so the Virtualhots of apache is pointed to /owncloud so the / is actually the owncloud itself, therefore my domain.com is pointed directly to owncloud.
I have downloaded and extracted the files to /apps/roundcube folder and tried to setup in owncloud but with no luck. The issue might be that the mail server is not set but I am not sure where to set it up. I have an external mail server that uses a separate authentication which I have found in my profile and I did the needful.
Could you give me advice how to proceed with the troubleshooting? In my logs i found this:
OC_RoundCube_AuthHelper.class.php: Login error during refresh.exception 'OC_Mail_NetworkingException' with message 'Unable to determine network-status due to technical problems.' in /var/www/owncloud/apps/roundcube/lib/RoundCubeLogin.class.php:422 Stack trace: #0 /var/www/owncloud/apps/roundcube/lib/RoundCubeLogin.class.php(329): OC_RoundCube_Login->sendRequest('/apps/roundcube...') #1 /var/www/owncloud/apps/roundcube/lib/RoundCubeLogin.class.php(280): OC_RoundCube_Login->updateLoginStatus() #2 /var/www/owncloud/apps/roundcube/lib/RoundCubeApp.class.php(273): OC_RoundCube_Login->isLoggedIn() #3 /var/www/owncloud/apps/roundcube/lib/RoundCubeAuthHelper.class.php(121): OC_RoundCube_App::refresh('bakosnet.hu', '', '/apps/roundcube...') #4 [internal function]: OC_RoundCube_AuthHelper::refresh(Array) #5 /var/www/owncloud/lib/private/route/router.php(250): call_user_func(Array, Array) #6 /var/www/owncloud/lib/base.php(763): OC\Route\Router->match('/apps/roundcube...') #7 /var/www/owncloud/index.php(36): OC::handleRequest() #8 {main}
RoundcubeLogin.class.php: sendRequest: \n Network connection failed on fopen(). Please check your path for roundcube with url http://domain.com/apps/roundcube/ on hostdomain.com

do u read the requeriments in the wiki page? or do u read the wiki page here in github?

see in u'r redaction seem that u dont have configure a mail server and rc installed!
so in the wiki section u must read the extra setup steps for custom installations..
do u have the roundcube in the same server, or the mail system have already the rouncube web interface?
please details u'r setup for better support.. lest see how can made.

and closing until user @powerhosting answer.. seems that assume that this app use the mail setup from oc and app have already and mail web interface embebed.

Dear mckaygerhard,
I have the special version from app.owncloud.com and i have set it up on the same server as owncloud however my mail server is running on a separete host therefore this might be causing the issue however I managed to install rainloop without any issues since it lets me edit mail server / domain there I managed to setup correctly. Thanks for the help anyway.
Best regards,

hello @powerhosting , this app its not for rainlood, u must have installed roundcube in any other or same host , no care if mailserver are in other host..
if oc are installed in root of apache this are not the problem.. the problem its that know nothing of your configuration mail service..
in the wiki, requeriments u note that need a mailsers (in u'r case in ahoter host, good)
also a mail web interface, roundcube (here u does not post any about that)
and also setup the app with the configured web mail interface..
u'r setup of mail server (the software of service itself) does nothing related to the app, the more related are the web ui of the mail service, in this case roundcube!
please post u'r setup of roundcube, the setup of oc and p'hp version (as must be done in each reported issue) and we will help to u.

i forgot, @powerhosting , i mean when i said "roundcube" it refers to the web mail interface and not to this app name..
the app name "roundcube" its only a bridge to use the real roundcube web mail interface, u must read carefully the wiki in this github.


[1.11] Crafting grid auto rotates north when not in chunkloaded area then coming back.

Minecraft 1.11
Forge 2199
Refined Storage 1.3.5
Runs on a dedicated server
When leaving my main spot then coming back after a while, the Crafting Grid and Disk Manipulator all will be rotated facing north. Really odd error as it recently started doing it.

Any logs?

This actually happens to External Storage in 1.10.2:
http://imgur.com/oGzxsVv
https://sx.artdude.uk/hotlink-ok/darkosto/Aclu-4951c-1484788700.png
They function properly, from what I can tell. But the blocks just completely turned around. It happens when I leave and join my server. There seem to be no logs from my initial scan of the output.
RS: 1.2.17
Forge: 2215 and 2221

This happens when a chunk read failed, most likely caused by an other mod.

More specifically: another tile entity failed NBT read, causing all the other tile entities in the same chunk not reading their data, making the External Storage face the default facing.
For an example of this, see #890

I've updated a few mods and removed items touching or placed next to the Refined Storage blocks. All seems good so far. There was no errors in my logs from client or server.

This is not an RS issue.


Disable test that's sometimes failing on Linux

Disable the COW.Fast.RemoveAllDoesNotReallocate test because it's sometimes failing on Linux.
rdar://problem/34268868

@swift-ci please smoke test

Could you hold off merging this please?
https://github.com/apple/swift/pull/11741 is a plausible real-fix of the issue
(see also rdar://34209577)

Will do!

@lancep FYI: you can use:
tests.test("my test")
  .skip { .linuxAny("EXPLANATION_HERE") }
  .code {
  // test body here
}

See example: link

Thanks :)

@lancep I wish I had good news for you here but sadly it seems Joe's fix did not fix this change. Would you like to post a version that does .skip the way @moiseev suggested? Then I guess we ought to land this (though: alarming bug! removeAll(keepingCapacity: true) appears to change capacity sometimes!)

@swift-ci please smoke test and merge

At least the capacity gets bigger!

@swift-ci please smoke test


Prefetch in Solid-Start does not hydrate to the client and instead calls the query again

Describe the bug
Taking this sample from Aryan, and changing it to prefect:
https://github.com/apatrida/solid-start-query-streaming-ssr/commit/0218c86e098f0569bb461147ed046f76d1537076
you would expect each query to run 1 time, but instead it runs on server then again on the client.
You can see this in the output from the server log:
GET http://localhost:3000/product/1
fetch product 1
fetch sizes 1
fetch recommended 1
fetch reviews 1
PREFETCH product 1 DONE
POST http://localhost:3000/_m/src/routes/product/[id].tsx/0/getProduct
fetch product 1
POST http://localhost:3000/_m/src/routes/product/[id].tsx/3/getAvailableSizes
fetch sizes 1
POST http://localhost:3000/_m/src/routes/product/[id].tsx/1/getRecommendedPicks
fetch recommended 1
POST http://localhost:3000/_m/src/routes/product/[id].tsx/2/getReviews
fetch reviews 1
PREFETCH reviews  1 DONE
PREFETCH sizes 1 DONE
PREFETCH recommended 1 DONE

So the prefetches started, then client calls came in for the same queries, and then the prefetches resolved but the queries were run twice.
Your minimal, reproducible example
see sample github
Steps to reproduce
see sample
Expected behavior
queries to run only once, on the server
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
solid-start
Tanstack Query adapter
solid-query
TanStack Query version
5.4.3
TypeScript version
4.9.5
Additional context
I updated versions to 6.7.2 and still occurs.

Hello! Apologies for the late reply. But, this works as designed.
In SolidStart, All the components run twice. Once on the server and then on the client. Elements inside JSX, if rendered on the server are not re-created on the client but hydrated. Everything else just runs twice, since it's plain JS. That is the reason why you see prefetchQuery run twice once on the server and then on the client.
There is another exception to this rule and they are SolidJS resources. Resources can run on the server, and if the data from the fetcher is resolved on the server then they can be picked back up on client without having to run the fetcher function again. Solid Query internally implements resources with createQuery and createInfiniteQuery.
Any queries you create using createQuery/createInfiniteQuery are run on the server and then if they resolve they are hydrated on the client. This totally eliminates the need of performing a prefetchQuery. You can simply write the app like how you would write a client rendered app and get the benefits of a server rendered app when using SolidStart! This infact is a feature and not a bug 😅
Are there any other reasons why you would want prefetchQuery? If there are any use cases that apply we can certainly work on adding those functionality.
Also the  documentation for Solid Query are sparse but I'll try to add more in the coming weeks

I didn't think it was the prefetch running twice, although I should wrap it with IsServer to make sure it is fetched on the server.   I'll have to check the client logs as well, but will need a new sample with this one having the API go down.
I'm testing cases that a larger app uses where it fetches data in route data so that the fetches start more concurrently then how they would if they were fetched in the component tree (waterfalling as components block on Show or other barriers).  Letting them run serially is a lot slower.
So a prefetch will always run the prefetch on server + the query on the client and does not hydrate the cache or the promise.  I would instead need to run the query, and pass it via routeData to the component rendering tree to then have it serialize across the wire.
Therefore prefetch only really helps to cache things for later use in the same SSR rendering?  But then that goes to waste having client run them again.
I would change to wrap in an IsServer call in your sample, but the hosted server API is down, and I can't find a place to get it to run locally.
In my main app, the IsServer doesn't prevent anything being called twice.  Pretech only helps on server in its rendering and then basically is ignored and client may query the same things again.

Ok, this test case shows the prefetch working and not querying a second time.
this code:
import { isServer } from 'solid-js/web';
import { createQuery, QueryFunctionContext, useQueryClient } from '@tanstack/solid-query';
import { createContext, createEffect, useContext, Show, Suspense } from 'solid-js';
import server$, { createServerData$ } from 'solid-start/server';
import { ErrorBoundary, RouteDataArgs } from 'solid-start';

type QueryOneResult = { message: string };

const queryFunction = server$(async (ctx: QueryFunctionContext): Promise<QueryOneResult> => {
  console.debug('queryOne server call', ctx.queryKey);
  return { message: `${ctx.queryKey}` };
});

const queryOneDataContext = createContext<QueryOneResult>();

export function routeData(args: RouteDataArgs) {
  console.log('routeData', isServer ? 'on server' : 'on client');
  if (isServer) {
    const id = Number(args.location.query.id ?? 0);
    if (id == 0) {
      console.debug('redirect to start');
      args.navigate('/testReactivity?id=1');
      return { message: 'redirect' };
    }
    const queryClient = useQueryClient();
    void queryClient
      .prefetchQuery({
        queryKey: ['queryOne', id],
        queryFn: queryFunction,
        staleTime: 10 * 1000,
      })
      .then(() => {
        console.debug('routeData', isServer ? 'on server' : 'on client', 'PRELOAD COMPLETE');
      });
  }

  return createServerData$(
    ([_, id]) => {
      const queryKey = ['queryTwo', id];
      console.debug('queryTwo server call', queryKey);
      return { message: `${queryKey}` };
    },
    { key: () => ['queryTwo', Number(args.location.query.id ?? 0)], deferStream: true }
  );
}

export default function TestReactivity() {
  const [searchParams] = useSearchParams();
  const navigate = useNavigate();
  const id = () => Number(searchParams.id ?? 0);

  const queryOne = createQuery(() => ({
    queryKey: ['queryOne', id()],
    queryFn: queryFunction,
    staleTime: 10 * 1000,
    placeholderData: (d) => d,
  }));

  const rd = useRouteData<typeof routeData>()!;

  createEffect(() => {
    console.debug(
      'queryOne state',
      queryOne.isFetching,
      queryOne.status,
      JSON.stringify(queryOne.data)
    );
  });
  createEffect(() => {
    console.debug('queryTwo state', rd.loading, rd.state, JSON.stringify(rd()));
  });

  function gotoNext() {
    console.debug('...goto next');
    let nextId = id() + 1;
    if (nextId === 11) {
      nextId = 1;
    }
    //setSearchParams({id: nextId});
    navigate('/testReactivity?id=' + nextId);
  }

  return (
    <ErrorBoundary>
      <Suspense>

            Test Reactivity <button onClick={() => gotoNext()}>next</button>

          <Show
            when={queryOne.data?.message}
            fallback={
waiting on queryOne...
}
          >

{queryOne.data?.message}

            <queryOneDataContext.Provider value={queryOne.data}>
              {/* not reactive */}
              <SubComponent whichQuery={'queryOne'} />
            </queryOneDataContext.Provider>
          </Show>

          <Show
            when={rd()}
            fallback={
waiting on queryTwo...
}
          >

{rd()?.message}

            <queryOneDataContext.Provider value={rd()}>
              <SubComponent whichQuery={'queryTwo'} />
            </queryOneDataContext.Provider>
          </Show>

      </Suspense>
    </ErrorBoundary>
  );
}

type SubComponentProps = {
  whichQuery: string;
};
function SubComponent(props: SubComponentProps) {
  const data = useContext(queryOneDataContext);
  createEffect(() => {
    console.debug(`sub data`, JSON.stringify(data));
  });
  return
sub: {data?.message}
;
}

outputs on first load on http://localhost:3000/testReactivity?id=1, SERVER:
GET http://localhost:3000/testReactivity?id=1
routeData on server
queryOne server call [ 'queryOne', 1 ]
queryTwo server call [ 'queryTwo', 1 ]
routeData on server PRELOAD COMPLETE

and on CLIENT:
routeData on client
testReactivity.tsx:63 queryOne state false success {"message":"queryOne,1"}
testReactivity.tsx:71 queryTwo state false ready {"message":"queryTwo,1"}
testReactivity.tsx:126 sub data {"message":"queryOne,1"}
testReactivity.tsx:126 sub data {"message":"queryTwo,1"}

and on the next button, SERVER:
POST http://localhost:3000/_m/src/routes/testReactivity.tsx/1/routeData
POST http://localhost:3000/_m/src/routes/testReactivity.tsx/0/queryFunction
queryTwo server call [ 'queryTwo', 2 ]
queryOne server call [ 'queryOne', 2 ]

and CLIENT:
...goto next
testReactivity.tsx:126 sub data {"message":"queryTwo,2"}
testReactivity.tsx:71 queryTwo state false ready {"message":"queryTwo,2"}
testReactivity.tsx:63 queryOne state true success {"message":"queryOne,1"}
testReactivity.tsx:63 queryOne state false success {"message":"queryOne,2"}
testReactivity.tsx:63 queryOne state true success {"message":"queryOne,2"}

is as expected.  if I loop around quickly before the stale timer ends on each the cached queries kick in.

This does show that query.data is not reactive through a provider while a Resource is reactive through the provider.

@ardeora if this works as designed - can we close the issue ?


DS-476: Share URL Update

Jira
https://pegadigitalit.atlassian.net/browse/DS-476
Summary
Deprecated the URL prop on the Share component to allow for more flexible Drupal integration
Details

Added 'attributes' to the share and menu item items schema to allow for data attributes to the added to the bolt-share on both the "display="inline" and display="menu" types.
Rewrote the share component jest test to the latest standards (added a deprecated test and added a 'display' prop test)
Updated the Teaser jest test to the new snapshot
Updated the doc site with the new share schema structure

How to test
Pull down this branch and confirm that the share functionality is still work
Release notes
Able to pass in data attributes to the share component for custom functionality

This PR had unexpected code in it, opened a new one


JS: Maximum call stack size exceeded at getTypeFromJSDocValueReference in 3.7.2

TypeScript Version:  3.7.2, 3.8.0-dev.20191105

Search Terms:
JSDoc Type reference Maximum call stack size exceeded getTypeFromJSDocValueReference
Code
Unfortunately I don't have a small case test case yet. The easiest steps I have so far:

git clone https://github.com/GoogleChrome/lighthouse.git
cd lighthouse
yarn
yarn add -D<EMAIL_ADDRESS>yarn tsc

Expected behavior:
Complete tsc run
Actual behavior:
~/lighthouse/node_modules/typescript/lib/tsc.js:78629
                throw e;
                ^

RangeError: Maximum call stack size exceeded
    at getTypeFromJSDocValueReference (~/lighthouse/node_modules/typescript/lib/tsc.js:35334:48)
    at getTypeReferenceType (~/lighthouse/node_modules/typescript/lib/tsc.js:35323:33)
    at getTypeFromJSDocValueReference (~/lighthouse/node_modules/typescript/lib/tsc.js:35348:32)
    at getTypeReferenceType (~/lighthouse/node_modules/typescript/lib/tsc.js:35323:33)
    at getTypeFromJSDocValueReference (~/lighthouse/node_modules/typescript/lib/tsc.js:35348:32)
    at getTypeReferenceType (~/lighthouse/node_modules/typescript/lib/tsc.js:35323:33)
    at getTypeFromJSDocValueReference (~/lighthouse/node_modules/typescript/lib/tsc.js:35348:32)
    at getTypeReferenceType (~/lighthouse/node_modules/typescript/lib/tsc.js:35323:33)
    at getTypeFromJSDocValueReference (~/lighthouse/node_modules/typescript/lib/tsc.js:35348:32)
    at getTypeReferenceType (~/lighthouse/node_modules/typescript/lib/tsc.js:35323:33)
error Command failed with exit code 1.

In 3.7.1-rc there were many of the Property 'methodName' does not exist on type 'typeof ClassName' errors that were being worked on in #34671, but it looks like the fix(es) struggles with something in our dependency graph and/or styles of declarations.
No issues or compilation errors using<EMAIL_ADDRESS>(though we're fine if there are new errors exposed by 3.7 that will need to be fixed in our code :)
Related Issues:
This seems very related to the cluster of issues @sandersn was working on in #34671, #34707, #34685, and #34802

I was able to reproduce with this code:
/**
 * @param {import('aws-sdk')} aws
 */
function test (aws) {}

Something in the typings in aws-sdk (and others I assume) is causing this

Experiencing similar, with slightly different callstack:
RangeError: Maximum call stack size exceeded
    at getSymbolLinks (/my-project/node_modules/typescript/lib/tsc.js:27740:32)
    at getTypeOfFuncClassEnumModule (/my-project/node_modules/typescript/lib/tsc.js:32593:25)
    at getTypeOfSymbol (/my-project/node_modules/typescript/lib/tsc.js:32702:24)
    at getTypeFromJSDocValueReference (/my-project/node_modules/typescript/lib/tsc.js:35295:29)
    at getTypeReferenceType (/my-project/node_modules/typescript/lib/tsc.js:35283:33)
    at getTypeFromJSDocValueReference (/my-project/node_modules/typescript/lib/tsc.js:35309:32)
    at getTypeReferenceType (/my-project/node_modules/typescript/lib/tsc.js:35283:33)
    at getTypeFromJSDocValueReference (/my-project/node_modules/typescript/lib/tsc.js:35309:32)
    at getTypeReferenceType (/my-project/node_modules/typescript/lib/tsc.js:35283:33)
    at getTypeFromJSDocValueReference (/my-project/node_modules/typescript/lib/tsc.js:35309:32)

Digging into the code, it seems to be related to the change made in #34683
More specifically the node.kind === SyntaxKind.ImportType check in https://github.com/microsoft/TypeScript/commit/8223c0752773ed6d4d42934adadd3d2cb15d5c3d, which seems to in some cases make getTypeReferenceType() and getTypeFromJSDocValueReference() call each other in at least a near circular way.

@RyanCavanaugh let's take this one for 3.7.3 too. Sounds like it breaks lighthouse and aws-sdk.

Here's a self-contained repro:
/** @param {import('./ex')} a */
function test(a) { }

export var crash: {};

Notably, this does not crash:
declare var nocrash: {}
export = nocrash;

My previous fix for import types was too eager. The jsdoc-value-as-type fallback is only needed for import types followed by qualified names.


Not verified in pub.dev

Hello, I was wondering when this package is going to be verified in pub.dev? I want to use it for my project, but for security purposes I can't use it unless it's verified.
PS: It's not up to me :(

Hello, It's already done.

Thank you so much!


Resource loading overhaul

As a Pillarbox user I want all contents to be playable and to be correctly informed of errors which might happen.
Acceptance criteria

All examples play...
... except those with errors which display a proper error message.
Network errors are correctly reported when no network is available, for all examples.

Context
As discovered in #95 the current approach to load URNs with a resource loader is doomed to fail. Instead, when playing SRG SSR content, we need to load the URL outside the resource loader, as we do in Letterbox today. We must then build and supply a corresponding item to the queue player.
Tasks

[x] Implement AVPlayerItem placeholder for errors.
[x] Implement PlayerItem loading from a URN and delivering an AVPlayerItem with a pipeline. Use loading and failure placeholder items to deal with initial state and metadata retrieval failure.
[x] Aggregate AVPlayerItems delivered by PlayerItem as they are updated.
[x] Implement trivial PlayerItem loading from a URL.
[x] Introduce AccumulateLatestMany to aggregate changes.
[x] Update AVQueuePlayer with diffing strategy (insert before methods required).
[x] Retrieve metadata before creating the item (will fix MP3 playback issues).
[x] Check whether inferringMoves can be useful to preserve existing items while moved. In other words check that moved items are not deallocated (else preserve them temporarily) and that, if the current item is moved, playback continues without interruption.
[x] Add setter for all items at once.
[x] Deal with resource loader ordering (if two contents are played and the second one is obtained first the player might skip to it directly).
[x] Implement currentItem publisher (simple pipe) with associated lane.
[x] Write UT for resource loader ordering (use current item publisher in tests).
[x] Apply short buffer / keep up with live behavior for live items only.
[x] Add playlist demo example with errors.
[x] Check all examples.
[x] Fix AccumulateLatestMany implementation to avoid AnyPublisher in parameters (have type constraints instead). This avoids forcing callers to erase the type when calling the method.
[x] Test with AirPlay (tvOS 16.1 most likely).
[x] Check memory and network profiles.

inferringMoves is not needed when applying diffs to update the player queue.

Rough sketch of how resource loading is fixed to load metadata before delivering items to the player (knowing the extension to use):

AVPlayerItem is now wrapped by PlayerItem which contains a publisher responsible of delivering the player item.
The pipeline initially delivers a LoadingPlayerItem and a FailingPlayerItem in case of an error. Both have been implemented with dedicated dummy resource loaders.
If a player item is successfully delivered the publishers are all wired to the player itself so that the AVQueuePlayer queue can be updated accordingly. This is done by using AccumulateLatestMany borrowed from my article.
Any change to the stored items property (insertion, removal) a pipeline update.
The update is performed by using the current item as pivot, gathering all items after it, and calculating the diff between existing items in the AVQueuePlayer and the updated items. If the current item has disappeared we consume the items after it until we find a common item, in which case we update from there recursively.
All other mutations through the public player API (insertions, removals, moves) trigger mutations of the stored items and thus consistently go through the same update pipeline.

There is still an issue with the current item selected at the beginning of playback, which can be reproduced as follows:

Create a playlist with two URNs.
Add a delay for media composition delivery based on a URN, delivering a large delay for the first URN in the playlist and none for the second one.
Play the playlist.

If we observe currentItem changes we see that for some reason the current item is moved to the second item. We will need to figure out whether this is an AVQueuePlayer bug (some issues related to queue management were namely fixed in 16.1) or whether we can do something to mitigate the problem.

I found the issue: Merging could be aggressive by removing the current item to update it (e.g. between loading and loaded items), which would make the player currentItem automatically move to the next item.
To fix this issue I applied the following approach:

Introduce a unique id attached to each PlayerItem delivery pipelines, marking items delivered by it so that they can be matched when replaced. This id is for internal purposes only and is forced unwrap to mark incorrect use as a programming error.
Use the id to identify the pivot item.
Use the id to identify current item updates and deal with them first to avoid removing and inserting its replacement (which would trigger a move to the next item).

I still need to write a unit test to validate this fix, likely as follows:

Create a resource loader delivering an item slowly.
Create a playlist with two items, the first one delivered slowly, the second one a simple URL.
Verify that the current item is the first one.

iOS 16.1 RC again breaks error forward through the resource loader after having fixed it in betas. The failing item strategy applied in this task therefore fails to deliver items encountered during metadata retrieval properly.
This issue is not a regression on our side but needs to be addressed, see #114.


Weird permissions issue

@kellyethridge , all
I'm trying to create a simple dll project with SimplyVBUnit and running into a weird problem.  When I open the project group and build the project, everything goes according to plan THE FIRST TIME, but every subsequent build attempt after results in a Permission Denied error in reference to my dll.  If I close the project group and reopen it, I can build it ONCE but never again until I restart VB6.  Additionally, if I only open the dll project (not the group that contains the test project also) I don't have any trouble building repeatedly.  If I re-add the test project to the environment, same problem happens.  It seems as if SimplyVBUnit is locking the dll file after the first build.  I've verified that the test project is referencing the dll vbp and not the dll directly.  Any advice?
Scott

Well in typical fashion, I'm unable to replicate this. Maybe you can zip-up your project group and send it to me to make sure I'm trying what you're trying correctly.

Courier.zip
Here's my project.  It currently lives at C:\dev\Courier
Very strange indeed... Thanks for looking into this for me.
Scott

Hi Kelly,  I know you're busy but I was wondering if you'd had a chance to take a look at my project and tell me why project groups that include SimplyVBUnit project causes this Permission Denied error?  I did some poking around in SVBU and noticed you're using a bit of Assembly as a helper which is very cool but well beyond my comprehension.  Could it be that if the test runner doesn't exit cleanly the file remains open because of an open handle in the helper?    I'm just trying to think outside the box a little.  I tried using ProcessExplorer from Sysinternals to see what was referencing the dll but the only thing it showed was Explorer.exe.  That also led me to the concept that maybe my install of git is hanging it.  I'm currently using TortoiseGit but haven't tried any others.  Open to suggestions...

There should be no references maintained once you exit the test UI. If some how there were a leak, the VB IDE would clear it up or the test UI would not unload. I was able to replicate the issue with a parent-child set of projects without referencing SimplyVBUnit, so I'm thinking it's a lack of clean-up from the IDE. If there is a compile error, then the child DLL would be locked and deny permission. So, I'm hard-pressed to think of a work-a-round of such a scenario. Your project attempts to call XMLUtils.NiceXML` like a static method, but it fails to compile enabling the permission error. I don't think there is a fix this issue as it seems to be VB IDE related.

Thanks for the update Kelly,
Yes, the XMLUtils class has a PredelcaredID set to True so the methods in it get added to the Global Namespace with a default instance.  It’s one of the options at the top of the class that you an only see from outside the IDE.  Here’s more info on it: https://christopherjmcclellan.wordpress.com/2015/04/21/vb-attributes-what-are-they-and-why-should-we-use-them/
I’m essentially making some of my classes static this way so that SVBU can unit test them.  So far I haven’t found a way (but you’d know better than I – for sure – I just haven’t asked yet) how to unit test a regular bas module.  It appears that the test runner only accepts test CLASSES and New’s them up on load – no obvious way to supply tests that are tucked away in a module.  Unless you have a way that I didn’t see in the docs (which I’m more than happy to update for you)
Scott
From: Kelly Ethridge<EMAIL_ADDRESS>Sent: Friday, October 23, 2020 10:41 PM
To: kellyethridge/SimplyVBUnit<EMAIL_ADDRESS>Cc: Scott Reeves<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [kellyethridge/SimplyVBUnit] Weird permissions issue (#17)
There should be no references maintained once you exit the test UI. If some how there were a leak, the VB IDE would clear it up or the test UI would not unload. I was able to replicate the issue with a parent-child set of projects without referencing SimplyVBUnit, so I'm thinking it's a lack of clean-up from the IDE. If there is a compile error, then the child DLL would be locked and deny permission. So, I'm hard-pressed to think of a work-a-round of such a scenario. Your project attempts to call XMLUtils.NiceXML` like a static method, but it fails to compile enabling the permission error. I don't think there is a fix this issue as it seems to be VB IDE related.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/kellyethridge/SimplyVBUnit/issues/17#issuecomment-715737558, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACVCD6RKO5QMBI6K5DIHZ2DSMJSGFANCNFSM4SUGH6LA.


Add .fail() function for early judgement failure

I think the asymmetry here is fine. In case of failure, this should propagate up the call stack as an exception, but there's no corresponding control flow in case of success -- we require the judge to return, not throw.

Is javascript OK with using errors for control flow? This isn't python, errors could be too expensive for us.

Now that I read the code again, I'm not sure I agree with this usage of errors. It is not obvious at all that this may throw. A reader can be misled to think that judge always returns BaseJudge.PASS.

@OrfeasLitos I don't understand your concern about being expensive. Why would exception be expensive in JS?

@OrfeasLitos Regarding the lack of clarity in the line of code you pointed to, this is the reason why the function was renamed to "ensureContainsDesiredOutput". Do you think this is insufficient?

@OrfeasLitos I don't understand your concern about errors being expensive. Why would exception be expensive in JS?

The argument in favor of throwing is that once the judge decides that a solution is wrong, the execution path is very clear. It is not the case that throwing may lead to complex execution paths. This point also defeats my previous argument about speed, since each submission can cause at most one error.
The assymetry still bothers me a bit, but I'd be OK with it if we make clearer which parts of the code may throw. Regarding ensureContainsDesiredOutput(), we can add a // may throw IncorrectSolutionError comment over it. There may be a cleaner solution, but I can't come up with anything else that won't be too complex.

Sure, I can put that comment near ensureContainsDesiredOutput(), but this is in a different PR.


html2: Set up a fuzz test for the tokenizer

This mostly serves as an example for further work on fuzzing things as the tokenizer is still too incomplete for this to be useful.
Here's what a running it looks like right now:
robin@x:~/code/hastur$ CC=clang-14 CXX=clang++14 bazel run html2/tokenizer_fuzz_test_run --config asan-libfuzzer -c dbg
INFO: Analyzed target //html2:tokenizer_fuzz_test_run (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //html2:tokenizer_fuzz_test_run up-to-date:
  bazel-bin/html2/tokenizer_fuzz_test_run
INFO: Elapsed time: 0.075s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
Launching html2/tokenizer_fuzz_test_bin as a libFuzzer fuzz test...
Using test output root: /tmp/fuzzing
Writing new corpus elements at: /tmp/fuzzing/corpus
Writing new artifacts at: /tmp/fuzzing/artifacts
INFO: Running with entropic power schedule (0xFF, 100).
INFO: Seed:<PHONE_NUMBER>
INFO: Loaded 1 modules   (1796 inline 8-bit counters): 1796 [0x55ffed2e9300, 0x55ffed2e9a04),
INFO: Loaded 1 PC tables (1796 PCs): 1796 [0x55ffed2e9a08,0x55ffed2f0a48),
INFO:      150 files found in /tmp/fuzzing/corpus
INFO:        0 files found in html2/tokenizer_fuzz_test_corpus
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
INFO: seed corpus: files: 150 min: 1b max: 11b total: 971b rss: 31Mb
#152    INITED cov: 838 ft: 2035 corp: 119/770b exec/s: 0 rss: 35Mb
#217    NEW    cov: 838 ft: 2037 corp: 120/781b lim: 11 exec/s: 0 rss: 35Mb L: 11/11 MS: 5 ShuffleBytes-ChangeBinInt-ShuffleBytes-ShuffleBytes-CrossOver-
terminate called without an active exception
==14147== ERROR: libFuzzer: deadly signal
    #0 0x55ffed1d20a1 in __sanitizer_print_stack_trace (/home/robin/.cache/bazel/_bazel_robin/57b3a6c7210188a99da0ed065bbc8d18/execroot/__main__/bazel-out/k8-dbg-ST-e961b0c8aa9c/bin/html2/tokenizer_fuzz_test_raw_+0x1410a1) (BuildId: 9a54ad4cd69b64379362854635c1f120f69bfc32)
    #1 0x55ffed144938 in fuzzer::PrintStackTrace() crtstuff.c
    #2 0x55ffed12a3a3 in fuzzer::Fuzzer::CrashCallback() crtstuff.c
    #3 0x7fa9fe4ec51f  (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d)
    #4 0x7fa9fe540a7b in __pthread_kill_implementation nptl/./nptl/pthread_kill.c:43:17
    #5 0x7fa9fe540a7b in __pthread_kill_internal nptl/./nptl/pthread_kill.c:78:10
    #6 0x7fa9fe540a7b in pthread_kill nptl/./nptl/pthread_kill.c:89:10
    #7 0x7fa9fe4ec475 in gsignal signal/../sysdeps/posix/raise.c:26:13
    #8 0x7fa9fe4d27f2 in abort stdlib/./stdlib/abort.c:79:7
    #9 0x7fa9fe87bbfd  (/lib/x86_64-linux-gnu/libstdc++.so.6+0xa2bfd) (BuildId: 725ef5da52ee6d881f9024d8238a989903932637)
    #10 0x7fa9fe88728b  (/lib/x86_64-linux-gnu/libstdc++.so.6+0xae28b) (BuildId: 725ef5da52ee6d881f9024d8238a989903932637)
    #11 0x7fa9fe8872f6 in std::terminate() (/lib/x86_64-linux-gnu/libstdc++.so.6+0xae2f6) (BuildId: 725ef5da52ee6d881f9024d8238a989903932637)
    #12 0x55ffed20edbc in html2::Tokenizer::run() /proc/self/cwd/html2/tokenizer.cpp:199:17
    #13 0x55ffed202ff9 in LLVMFuzzerTestOneInput /proc/self/cwd/html2/tokenizer_fuzz_test.cpp:21:14
    #14 0x55ffed12b933 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) crtstuff.c
    #15 0x55ffed12b089 in fuzzer::Fuzzer::RunOne(unsigned char const*, unsigned long, bool, fuzzer::InputInfo*, bool, bool*) crtstuff.c
    #16 0x55ffed12c879 in fuzzer::Fuzzer::MutateAndTestOne() crtstuff.c
    #17 0x55ffed12d3f5 in fuzzer::Fuzzer::Loop(std::vector<fuzzer::SizedFile, std::allocator<fuzzer::SizedFile> >&) crtstuff.c
    #18 0x55ffed11b522 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) crtstuff.c
    #19 0x55ffed145232 in main (/home/robin/.cache/bazel/_bazel_robin/57b3a6c7210188a99da0ed065bbc8d18/execroot/__main__/bazel-out/k8-dbg-ST-e961b0c8aa9c/bin/html2/tokenizer_fuzz_test_raw_+0xb4232) (BuildId: 9a54ad4cd69b64379362854635c1f120f69bfc32)
    #20 0x7fa9fe4d3d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16
    #21 0x7fa9fe4d3e3f in __libc_start_main csu/../csu/libc-start.c:392:3
    #22 0x55ffed10ff64 in _start (/home/robin/.cache/bazel/_bazel_robin/57b3a6c7210188a99da0ed065bbc8d18/execroot/__main__/bazel-out/k8-dbg-ST-e961b0c8aa9c/bin/html2/tokenizer_fuzz_test_raw_+0x7ef64) (BuildId: 9a54ad4cd69b64379362854635c1f120f69bfc32)

NOTE: libFuzzer has rudimentary signal handlers.
      Combine libFuzzer with AddressSanitizer or similar for better crash reports.
SUMMARY: libFuzzer: deadly signal
MS: 2 CMP-CopyPart- DE: "\001\000\000\000"-; base unit: f44bc7149f03c230908da845fbdf8eab4e2896f6
0x26,0x3c,0x1,0x0,0x0,0x0,0x70,0x3c,0x3c,0x2f,0x2f,
&<\001\000\000\000p<<//
artifact_prefix='/tmp/fuzzing/artifacts/'; Test unit written to /tmp/fuzzing/artifacts/crash-2c65af91cc839c1d1e99dedec427c29147530f7a
Base64: JjwBAAAAcDw8Ly8=

Example of what running honggfuzz looks like:
CC=clang-14 CXX=clang++14 bazel run html2/tokenizer_fuzz_test_run --config asan-honggfuzz
------------------------[  0 days 00 hrs 00 mins 34 secs ]----------------------
  Iterations : 47,050 [47.05k]
  Mode [3/3] : Feedback Driven Mode
      Target : html2/tokenizer_fuzz_test_bin
     Threads : 12, CPUs: 24, CPU%: 1200% [50%/CPU]
       Speed : 1,619/sec [avg: 1,383]
     Crashes : 0 [unique: 0, blacklist: 0, verified: 0]
    Timeouts : 275 [1 sec]
 Corpus Size : 2,587, max: 8,192 bytes, init: 1 files
  Cov Update : 0 days 00 hrs 00 mins 00 secs ago
    Coverage : edge: 646/7,063 [9%] pc: 27 cmp: 55,015
---------------------------------- [ LOGS ] ------------------/ honggfuzz 2.3 /-
Sz:8190 Tm:3,148us (i/b/h/e/p/c) New:0/0/0/0/0/3, Cur:0/0/0/100/0/131
Sz:24 Tm:508us (i/b/h/e/p/c) New:0/0/0/0/0/1, Cur:0/0/0/36/0/3
[2022-09-22T17:27:02+0200][W][556] subproc_checkTimeLimit():531 pid=831 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:02+0200][W][563] subproc_checkTimeLimit():531 pid=836 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:02+0200][W][563] arch_checkWait():239 Persistent mode: pid=836 exited with status: SIGNALED, signal: 9 (Killed)
[2022-09-22T17:27:02+0200][W][556] arch_checkWait():239 Persistent mode: pid=831 exited with status: SIGNALED, signal: 9 (Killed)
Persistent mode: Launched new persistent pid=845
Persistent mode: Launched new persistent pid=846
[2022-09-22T17:27:03+0200][W][558] subproc_checkTimeLimit():531 pid=834 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][558] arch_checkWait():239 Persistent mode: pid=834 exited with status: SIGNALED, signal: 9 (Killed)
Persistent mode: Launched new persistent pid=847
Sz:8192 Tm:3,520us (i/b/h/e/p/c) New:0/0/0/0/0/20, Cur:0/0/0/250/0/2449
[2022-09-22T17:27:03+0200][W][561] subproc_checkTimeLimit():531 pid=837 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][565] subproc_checkTimeLimit():531 pid=835 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][561] arch_checkWait():239 Persistent mode: pid=837 exited with status: SIGNALED, signal: 9 (Killed)
Persistent mode: Launched new persistent pid=848
Sz:8190 Tm:5,051us (i/b/h/e/p/c) New:0/0/0/0/0/2, Cur:0/0/0/234/0/1123
Sz:8192 Tm:3,295us (i/b/h/e/p/c) New:0/0/0/0/0/3, Cur:0/0/0/179/0/1215
Sz:8192 Tm:2,824us (i/b/h/e/p/c) New:0/0/0/0/0/4, Cur:0/0/0/164/0/860
[2022-09-22T17:27:03+0200][W][557] subproc_checkTimeLimit():531 pid=840 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][560] subproc_checkTimeLimit():531 pid=839 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][562] subproc_checkTimeLimit():531 pid=838 took too much time (limit 1 s). Killing it with SIGKILL
[2022-09-22T17:27:03+0200][W][565] arch_checkWait():239 Persistent mode: pid=835 exited with status: SIGNALED, signal: 9 (Killed)
[2022-09-22T17:27:03+0200][W][560] arch_checkWait():239 Persistent mode: pid=839 exited with status: SIGNALED, signal: 9 (Killed)
Sz:8181 Tm:1,040,619us (i/b/h/e/p/c) New:0/0/0/0/0/5, Cur:0/0/0/128/0/589
Persistent mode: Launched new persistent pid=849
Persistent mode: Launched new persistent pid=850


UI flickers and is torn apart

System information:

Debian 10 (on Chrome OS 89.0.4389.95)
DBeaver <IP_ADDRESS>103211229

Describe the problem you're observing:
The UI flickers and looks weird.
Steps to reproduce, if exist:
Download, install and start.

Unfortunately we do not support this platform.

I'm using Debian 9 (stretch).  I also experienced the flickering problem.  It seems to be related to GTK. I resolved the issue with the following steps:

added to ~/.profile:  export GTK_IM_MODULE=ibus
installed the following libraries:  sudo apt install ibus-gtk ibus-gtk3 ibus-clutter ibus-qt4 -y


⚠ Bofrost.de has degraded performance

In fbc816c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1866 ms

Resolved: Bofrost.de performance has improved in 1ec561a after 25 minutes.


Fix for #20

What issue(s) does this fix?
Fixes #20
Is this complete or a WIP?
Complete!

@joker314 can you review this?


ND-463 Revert main branch - Added new env var and OpenSSL version

Required as the definded veresion no linger exists, this is a common problem as the "-rc" version is specified. So we can update the variable as and when required to prevent errro messages ad the one below. 2.201 ERROR: unable to select packages:
2.207   openssl-3.1.6-r0:
2.207     breaks: world[openssl~3.1.4-r6]
ND-463

not reverting correctly


no exe program

i did download the tibialyzer but it does not have the tibialyzer.exe so i can  use it

You downloaded the source code, the executable can be found here.

thanks


what is the mean of the "2× scheduler"  in the section 5.4.2?

what is the mean of the "2× scheduler"  in the section 5.4.2?

I have the same question “what is the mean of the "2× scheduler" in the section 5.4.2?”，hope to get a reply，thanks

I have the same question too

I guess the 2x is the training schedul define in detectron:
https://github.com/facebookresearch/Detectron/blob/master/MODEL_ZOO.md


KeepInventory Gamerule Per World

Hi, Sorry if this has already been answered, I'm trying to migrate away from multiverse, and I was wondering if there was a way to set per world "keep-inventory" (in one world the player can lose their items, but in another world they can't lose their items, assuming that their inventories are merged between worlds), it's a little bit weird of a Scenario. Hope you can send me in the right direction, thanks!

I think game rules on bukkit are already per world (applied to the world youre inside of). But I could be wrong. Can you check?

Thank you! Sorry for the trouble lol, probably should have checked that haha


Refactor Tradfri light group

Description:
This is a continuation of the refactoring of the Tradfri library. This PR refactors Tradfri light group class.
Related issue (if applicable): relates to #26863
Related issue (if applicable): fixes #
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Failing tests doesn't look related to this change so I'll wait for a fix on dev branch and rebase.

Is this one good?


Add support for configuring an endpoint URL when connecting with Bedrock and Spring AI

Expected Behavior
Essentially, it should be possible to configure a dedicated "endpoint URL" for connecting to a Bedrock hosted endpoint from the side of Spring AI.
An example that comes to mind is configuring the connection to Bedrock to use a VPC, for example, to avoid it going over the public internet.
Current Behavior
Currently, there is no way to configure the endpoint URL used to connect to Bedrock from Spring AI, while that seems to be exclusively exposed from the side of the Bedrock API from the Java side.
Context
The most simple context is as defined above: we want to customize the exising endpoint URL to connect to Bedrock in some way, such that we can do it with minimal code while still leveraging all of the abstractions in place for Spring AI.
A current, potential workaround is to create a custom implementation of the AbstractBedrockApi that looks like:
public abstract class CustomAbstractBedrockApi<I, O, SO> {
    private static final Logger logger = LoggerFactory.getLogger(CustomAbstractBedrockApi.class);
    private final String modelId;
    private final ObjectMapper objectMapper;
    private final Region region;
    private BedrockRuntimeClient client;
    private BedrockRuntimeAsyncClient clientStreaming;

...
public CustomAbstractBedrockApi(
            String modelId,
            AwsCredentialsProvider credentialsProvider,
            String region,
            ObjectMapper objectMapper,
            Duration timeout,
            BedrockRuntimeClient bedrockRuntimeClient,
            BedrockRuntimeAsyncClient bedrockRuntimeAsyncClient) {
        this(modelId, credentialsProvider, Region.of(region), objectMapper, timeout);
        client = bedrockRuntimeClient;
        clientStreaming = bedrockRuntimeAsyncClient;
    }

in order to enable configuration via DI of the runtime clients.
With this in place, all that would be needed to do would be, from a configuration class:
@Bean
    @ConditionalOnProperty("spring.ai.bedrock.endpoint-url")
    public BedrockRuntimeClient bedrockRuntimeClient() {
        log.info("Configured runtime client to use VPC");

        try {
            return BedrockRuntimeClient.builder()
                    .region(Region.of(getRegion()))
                    .credentialsProvider(DefaultCredentialsProvider.create())
                    .endpointOverride(new URI(endpointUrl))
                    .build();
        } catch (URISyntaxException e) {
            log.info("Failure when configuring the BedrockRuntimeClient: {}", e.getMessage());
            throw new RuntimeException(e);
        }
    }

While, in the current implementation, quite a lot of custom code is needed.
PS: Do let me know if I am missing something.

This seems to be related: https://github.com/spring-projects/spring-ai/issues/809#issuecomment-2147086881
So I am wondering if someone else has some better workarounds for this, has stumbled upon it, and if it's in the roadmap.

I've created a PR where an extra constructor with endpoint override is defined.  It's also defined for all the Bedrock API implementations.


How to keep Timer running even after app has been killed from the recent list!

Hi guys,
Just as in the title, my question is how to make this timer works after the app has been killed completely, I'm currently making a chat app using socket connection which is the one that needs to be alive all time.
Thank you.

Hi
Please check out
https://github.com/DavidBriglio/cordova-plugin-foreground-service
On Thu, Oct 8, 2020 at 5:23 AM hnguyen48206<EMAIL_ADDRESS>wrote:

Hi guys,
Just as in the title, my question is how to make this timer works after
the app has been killed completely, I'm currently making a chat app using
socket connection which is the one that needs to be alive all time.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dukhanov/cordova-background-timer/issues/6, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUBL5XRFPFXRIVSMGBVIX3SJUPBDANCNFSM4SIEZ2HA
.

--
Best regards,
Maxim Dukhanov


Python rapidast run

Want to add python version of a dockerfile to help test out https://github.com/openshift/release/pull/54711
This will mostly be for testing for now. Will want to keep the main Dockerfile as the main way to run/keep good version set up for cron runs

/lgtm


Error printing determinants at the end of CI computation

Probably very minor. It happened when I ran HF (molecule) with a (10,6) active space
ERROR: BoundsError: attempt to access 36-element Array{Float64,1} at index [37]
Stacktrace:
 [1] getindex(::Array{Float64,1}, ::Int64) at ./array.jl:788
 [2] macro expansion at /home/vulcan/aroeira/Fermi.jl/src/Backend/IO/Output.jl:57 [inlined]
 [3] Fermi.ConfigurationInteraction.CASCI{Float64}(::Fermi.HartreeFock.RHF, ::Array{Float64,2}, ::Array{Float64,4}, ::Int64, ::Int64, ::Int64, ::Fermi.ConfigurationInteraction.SparseHamiltonian) at /home/vulcan/aroeira/Fermi.jl/src/Methods/ConfigurationInteraction/CASCI/SparseHamiltonian.jl:97
 [4] Fermi.ConfigurationInteraction.CASCI{Float64}(::Fermi.ConfigurationInteraction.SparseHamiltonian) at /home/vulcan/aroeira/Fermi.jl/src/Methods/ConfigurationInteraction/CASCI/SparseHamiltonian.jl:48
 [5] Fermi.ConfigurationInteraction.CASCI{Float64}() at /home/vulcan/aroeira/Fermi.jl/src/Methods/ConfigurationInteraction/CASCI/CASCI.jl:69
 [6] Fermi.ConfigurationInteraction.CASCI() at /home/vulcan/aroeira/Fermi.jl/src/Methods/ConfigurationInteraction/CASCI/CASCI.jl:58
 [7] top-level scope at REPL[12]:1

Fixed on my branch.

CI computations are not available currently.


Google Api Error: noActiveApks

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I'm getting Google Api Error: noActiveApks, but app already have 17 apks in beta, so it's strange
Captured Output
Command Used: beta
Output/Log

Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
DEBUG [2017-01-27 17:07:26.77]: Checking if there are any plugins that should be loaded...
INFO [2017-01-27 17:07:26.84]: -------------------------------------------------
INFO [2017-01-27 17:07:26.84]: --- Step: Verifying required fastlane version ---
INFO [2017-01-27 17:07:26.84]: -------------------------------------------------
INFO [2017-01-27 17:07:26.84]: Your fastlane version 2.12.0 matches the minimum requirement of 2.12.0  ✅
INFO [2017-01-27 17:07:26.85]: ------------------------------
INFO [2017-01-27 17:07:26.85]: --- Step: default_platform ---
INFO [2017-01-27 17:07:26.85]: ------------------------------
INFO [2017-01-27 17:07:26.85]: Driving the lane 'android beta' 🚀
INFO [2017-01-27 17:07:26.86]: --------------------
INFO [2017-01-27 17:07:26.86]: --- Step: supply ---
INFO [2017-01-27 17:07:26.86]: --------------------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------
Successfully loaded Appfile at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/Appfile'
- json_key_file: './google_play_key.json'
- package_name: 'gl.kid.alert'
-------

+-------------------------+-----------------------------+
|               Summary for supply 2.12.0               |
+-------------------------+-----------------------------+
| track                   | beta                        |
| package_name            | gl.kid.alert                |
| rollout                 | 0.1                         |
| metadata_path           | ./fastlane/metadata/android |
| json_key                | ./google_play_key.json      |
| skip_upload_apk         | false                       |
| skip_upload_metadata    | false                       |
| skip_upload_images      | false                       |
| skip_upload_screenshots | false                       |
| validate_only           | false                       |
+-------------------------+-----------------------------+

DEBUG [2017-01-27 17:07:29.75]: Fetching a new access token from Google...
INFO [2017-01-27 17:07:31.01]: Preparing to upload for language 'en-US'...
INFO [2017-01-27 17:07:32.02]: Uploading image file ./fastlane/metadata/android/en-US/images/icon.png...
INFO [2017-01-27 17:07:35.05]: Updating changelog for code version '6' and language 'en-US'...
INFO [2017-01-27 17:07:35.62]: Updating changelog for code version '7' and language 'en-US'...
INFO [2017-01-27 17:07:36.34]: Updating changelog for code version '8' and language 'en-US'...
INFO [2017-01-27 17:07:36.95]: Updating changelog for code version '10' and language 'en-US'...
INFO [2017-01-27 17:07:37.55]: Updating changelog for code version '11' and language 'en-US'...
INFO [2017-01-27 17:07:38.22]: Updating changelog for code version '12' and language 'en-US'...
INFO [2017-01-27 17:07:38.80]: Updating changelog for code version '13' and language 'en-US'...
INFO [2017-01-27 17:07:39.42]: Updating changelog for code version '14' and language 'en-US'...
INFO [2017-01-27 17:07:39.96]: Updating changelog for code version '15' and language 'en-US'...
INFO [2017-01-27 17:07:40.64]: Updating changelog for code version '16' and language 'en-US'...
INFO [2017-01-27 17:07:41.18]: Updating changelog for code version '17' and language 'en-US'...
INFO [2017-01-27 17:07:41.87]: Updating changelog for code version '18' and language 'en-US'...
INFO [2017-01-27 17:07:42.48]: Preparing to upload for language 'ru-RU'...
INFO [2017-01-27 17:07:43.91]: No apk file found, you can pass the path to your apk using the `apk` option
INFO [2017-01-27 17:07:43.91]: Updating track 'beta'...
INFO [2017-01-27 17:07:44.63]: Uploading all changes to Google Play...
WARN [2017-01-27 17:07:45.57]: Lane Context:
INFO [2017-01-27 17:07:45.57]: {:DEFAULT_PLATFORM=>:android, :PLATFORM_NAME=>:android, :LANE_NAME=>"android beta"}
ERROR [2017-01-27 17:07:45.57]: Google Api Error: noActiveApks: This app does not have any APKs in any tracks.
INFO [2017-01-27 17:07:45.57]: Successfully generated documentation at path '/Users/KidGeoLoc/Desktop/kid-in-the-city/fastlane/README.md'

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 💥   | supply                              | 18          |
+------+-------------------------------------+-------------+

ERROR [2017-01-27 17:07:45.64]: fastlane finished with errors

✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.11.6 (15G1108)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.12.0"

default_platform :android

platform :android do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
  end

  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    #gradle(task: "mobile:firebaseUploadReleaseProguardMapping")
    supply(track: 'beta')
    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "assembleRelease")
    supply
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is sent or shared. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
json_key_file "./google_play_key.json" # Path to the json secret file - Follow https://github.com/fastlane/supply#setup to get one
package_name "gl.kid.alert" # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.12.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.1

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.4.3

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.4

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.22

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.1.2

bundler
1.13.7

faraday_middleware
0.11.0

psych
2.0.8

generated on: 2017-01-27

@rostopira are you still experiencing this problem? Can you confirm that the package name you were using is correct?

@asfalcone yes, still experiencing this problem, trying everyday. According to attached log

INFO [2017-01-27 17:07:41.87]: Updating changelog for code version '18' and language 'en-US'...

Package name is correct

Error dissappeared. Now fastlane creates new release in beta without any apk

I wonder if there was some issue with the Google api? I'm going to close this out for now, but feel free to reopen if you run into this again!

I wonder if there was some issue with the Google api?

Yeah, probably. Sure, issue should be closed


[Monitor] Update changelog

Fix #31490
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Update Little Snitch 5.download.recipe

Hi, @smithjw
The Little Snitch 5 download recipe is failing with the following error message
Processor: URLTextSearcher: Error: No match found on URL: https://www.obdev.at/products/littlesnitch/download.html

This PR updates the search URL and the download URL to account for it moving to the legacy downloads page.

WARNING: Little Snitch 5.download.recipe is missing trust info and FAIL_RECIPES_WITHOUT_TRUST_INFO is not set. Proceeding...
URLTextSearcher
URLTextSearcher: Found matching text (match): LittleSnitch-5.7.6.dmg
URLDownloader
URLDownloader: Storing new Last-Modified header: Thu, 16 May 2024 11:19:40 GMT
URLDownloader: Storing new ETag header: "1e8b259-6189069398b00"
URLDownloader: Downloaded /Users/paul.cossey/Library/AutoPkg/Cache/com.github.smithjw.download.LittleSnitch5/downloads/LittleSnitch-5.7.6.dmg
EndOfCheckPhase
CodeSignatureVerifier
CodeSignatureVerifier: Mounted disk image /Users/paul.cossey/Library/AutoPkg/Cache/com.github.smithjw.download.LittleSnitch5/downloads/LittleSnitch-5.7.6.dmg
CodeSignatureVerifier: Verifying code signature...
CodeSignatureVerifier: Deep verification enabled...
CodeSignatureVerifier: Strict verification not defined. Using codesign defaults...
CodeSignatureVerifier: /private/tmp/dmg.4vmkKN/Little Snitch.app: valid on disk
CodeSignatureVerifier: /private/tmp/dmg.4vmkKN/Little Snitch.app: satisfies its Designated Requirement
CodeSignatureVerifier: /private/tmp/dmg.4vmkKN/Little Snitch.app: explicit requirement satisfied
CodeSignatureVerifier: Signature is valid
Receipt written to /Users/paul.cossey/Library/AutoPkg/Cache/com.github.smithjw.download.LittleSnitch5/receipts/Little Snitch 5.download-receipt-20240523-171001.plist

The following new items were downloaded:
    Download Path
    -------------
    /Users/paul.cossey/Library/AutoPkg/Cache/com.github.smithjw.download.LittleSnitch5/downloads/LittleSnitch-5.7.6.dmg

Thanks @paul-cossey for the PR! I've integrated those changes into the recipes and converted them into yaml 😄

Thanks, @smithjw! Appreciate the swift merge (and upstream changes!) 🚀


Add Deneb Types and Flow

📝 Summary

Part of #554
⛱ Motivation and Context

📚 References

✅ I have run these commands

[x] make lint
[x] make test-race
[x] go mod tidy

rebased


Add username / password for MQTT broker

Is your feature request related to a problem? Please describe:
My MQTT broker has a username and password. Without having a config for that in the plugin, can't use MQTT for doorbell or motion
Describe the solution you'd like:
add MQTT Broker username and password to config
Describe alternatives you've considered:
Using HTTP for now, but would rather use MQTT
Additional context:
FWIW, my MQTT broker is internal to NodeRed, and my doorbell is an ESP8266 that sends an MQTT message. For now NodeRed is receiving the message and resending it by HTTP, but with this fix, could have it go directly from sensor to homebridge

Easy enough. I’ll get that added to the beta version shortly, and it’ll be in the next release.

Okay, added to the latest beta, you can install it with sudo npm install -g homebridge-camera-ffmpeg@beta --unsafe-perm. I did some quick testing, but please let me know if this works for you.

Worked perfectly, thanks!

Glad it's working for you, I'll close this out now and it'll be in the next release (but feel free to stick on the beta until then).


Option to disable logging

Describe the bug
Seams the ws plug-in is logging every update to the log which clutters the log is there an option  to disable the logging of the plug-in?
To Reproduce
Steps to reproduce the behavior:
Just start plugin every 10 minutes it writes a couple of log lines to the main log.
Expected behavior
An option to only log plugin errors to the main log.
Latest version fresh install 2 days ago.

Please provide your thoughts how best to implement this to https://github.com/ebaauw/homebridge-lib/issues/26.

In v2.3.0.  Note that you need to issue multiple Identify requests to change the level of logging.  Please let me know if that works, or if I should expose another characteristic for it.


SPACE key does not work under Sway/Wayland

Hi,
OS and version: 64-bit Arch Linux (rolling)
Release or commit: glfw 3.2.1 compiled for wayland (the "glfw-wayland" package on Arch)
GLFW does not seem to detect when SPACE is pressed.
I'm using the Sway window manager (which uses the Wayland protocol) on 64-bit Arch Linux.
Here's a simple test program:
#include <GL/glew.h>
#include <GLFW/glfw3.h>
#include <cstdio>

bool running = false;

void error_callback(int error, const char* description)
{
    fprintf(stderr, "Error: %s\n", description);
}

void key_callback(GLFWwindow* window, int key, int scancode, int action, int mods)
{
    switch (key) {
    case GLFW_KEY_ESCAPE:
        if (action == GLFW_PRESS)
            running = false;
        break;
    case GLFW_KEY_X:
        if (action == GLFW_PRESS) {
            printf("%s\n", "x pressed");
        } else if (action == GLFW_RELEASE) {
            printf("%s\n", "x released");
        }
        break;
    case GLFW_KEY_SPACE:
        if (action == GLFW_PRESS) {
            printf("%s\n", "space pressed");
        } else if (action == GLFW_RELEASE) {
            printf("%s\n", "space released");
        }
        break;
    default:
        break;
    }
}

int main(int argc, char* argv[])
{
    const size_t buffer_width = 224;
    const size_t buffer_height = 256;

    glfwSetErrorCallback(error_callback);

    if (!glfwInit())
        return -1;

    glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);
    glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);
    glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
    glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);

    /* Create a windowed mode window and its OpenGL context */
    GLFWwindow* window
        = glfwCreateWindow(2 * buffer_width, 2 * buffer_height, "Space Invaders", nullptr, nullptr);
    if (!window) {
        glfwTerminate();
        return -1;
    }

    glfwSetKeyCallback(window, key_callback);

    glfwMakeContextCurrent(window);

    GLenum err = glewInit();
    if (err != GLEW_OK) {
        fprintf(stderr, "Error initializing GLEW.\n");
        glfwTerminate();
        return -1;
    }

    running = true;
    while (!glfwWindowShouldClose(window) && running) {
        glfwPollEvents();
    }

    glfwDestroyWindow(window);
    glfwTerminate();

    return 0;
}

One possible way to build it:
g++ -o main -std=c++17 -O2 main.cpp -lglfw -lGLEW

When running the program, with the window focused, I get the following output when pressing the x key a couple of times:
x pressed
x released
x pressed
x released
x pressed
x released

When pressing space, there is no such output.

I can’t reproduce with GLFW master on a recent Sway (nor on Weston), both x and space work properly.
Note that GLFW 3.2 is very old at this point, many improvements have been added to the Wayland backend since then.

Thanks for attempting to reproduce the issue. I will try again with the latest version of Sway.

My keyboard layout is also non-English; it's Norwegian.

@Svenny The issue on X11 was indeed a bug in GLFW. It has been fixed in the 3.3-stable branch and will be included in 3.3.3.
The OP Wayland bug is unrelated afaik.

I can no longer reproduce the issue. It works here now.


Alarming errors on weaveDNS in deployments without weave

Now Scope periodically checks for weave being started as a result of #867 .
However, this results in somehow alarming errors in deployments without Weave Net:
$ docker logs weavescope |& grep weaveDNS
<app> ERRO: 2016/02/23 09:24:29.108373 Error updating weaveDNS, backing off 20s: Error running weave expose: exit status 1
<app> ERRO: 2016/02/23 09:24:49.424425 Error updating weaveDNS, backing off 40s: Error running weave expose: exit status 1
<app> ERRO: 2016/02/23 09:25:29.732988 Error updating weaveDNS, backing off 1m0s: Error running weave expose: exit status 1

I understand those errors are legitimate and that we want to make those checks by default.
You can disable this is by doing --probe.weave.router.addr ""  but that's not very intuitive (and inconvenient). I would suggest either or:

Lowering the alarming tone of those errors.
Adding an extra more-intuitive flag: --disable.weave ?

Can do. I'd would add that the errors go away once you hit max back off.
On Tuesday, 23 February 2016, Alfonso Acosta<EMAIL_ADDRESS>wrote:

Now Scope periodically checks for weave being started as a result of #867
https://github.com/weaveworks/scope/pull/867 .
However, this results in somehow alarming errors in deployments without
Weave Net:
$ docker logs weavescope |& grep weaveDNS
 ERRO: 2016/02/23 09:24:29.108373 Error updating weaveDNS, backing off 20s: Error running weave expose: exit status 1
 ERRO: 2016/02/23 09:24:49.424425 Error updating weaveDNS, backing off 40s: Error running weave expose: exit status 1
 ERRO: 2016/02/23 09:25:29.732988 Error updating weaveDNS, backing off 1m0s: Error running weave expose: exit status 1
I understand those errors are legitimate and that we want to make those
checks by default.
You can disable this is by doing --probe.weave.router.addr "" but that's
not very intuitive (and inconvenient). I would suggest either or:

Lowering the alarming tone of those errors.
Adding an extra more-intuitive flag: --disable.weave ?

—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/1008.


Add whats-new logs workflow

Codecov Report

Merging #181 (f9e9ad5) into develop (426171b) will increase coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head f9e9ad5 differs from pull request most recent head a4ef4b9. Consider uploading reports for the commit a4ef4b9 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff            @@
##           develop     #181   +/-   ##
========================================
  Coverage    77.24%   77.25%
========================================
  Files           50       50
  Lines         6347     6345    -2
========================================
- Hits          4903     4902    -1
+ Misses        1444     1443    -1

see 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

closes #180


Suggestion: Color presets for friends, CC, Chat-Channel, GIM, and unaffiliated players

Hi,
This plugin is very nice for differentiating names. To expand the functionality further, I was wondering how feasible it would be to add preset colors for unspecified users in friends list, cc, chat channel, etc. For example, if I haven't manually set a chat color for a clan member, then their name would show up as the preset color that I picked for clan members. This would be overridden though if you manually picked a color for a user. Perhaps the status of these users could also be checked periodically, such as if someone leaves the clan or chat-channel, then their color will be updated to the default color for normal players (not on friends list/cc/chat channel).
I would think the hierarchy for what color shows would be something like:
Manually Chosen Color > Friends List > Group Ironman > Clan Chat > Chat Channel > Unaffiliated players you don't know
Let me know what you think. Thanks

Thank you for the thoughtful suggestion! This is a great idea and definitely think it is supportable

Are you open to PRs? I'd love to work on adding this functionality since I was about to raise the same issue :).

Are you open to PRs? I'd love to work on adding this functionality since I was about to raise the same issue :).

Absolutely! Would love to review any incoming PRs. Haven't found the time to do it myself just yet