Show whether a CSS property, value or selector is valid

Firebug 2 showed a green, red or yellow glowing arround the inline editor while editing CSS properties, values or selectors to indicate whether they are valid and can be applied.
This feature should be readded.
Sebastian

Thanks Sebastian for the report.
I guess it should be reported as a Bugzilla issue (as it should be implemented on the native DevTools). Would you like to report it?
FYI, we currently triage Firebug issues so we only work on the theme.
Florent

I filed it as bug 1227054. In the hope that this gets implemented on the platform, I close this issue.
Sebastian


Conditionally checking for slot prop does not work in angular

I am interested in helping provide a fix!
Yes
Which generators are impacted?

[ ] All
[X] Angular
[ ] HTML
[ ] Qwik
[ ] React
[ ] React-Native
[ ] Solid
[ ] Stencil
[ ] Svelte
[ ] Vue
[ ] Web components

Reproduction case
https://mitosis.builder.io/?outputTab=IYOw5grgNsBOQ%3D%3D%3D&code=JYWwDg9gTgLgBAbzgVwM4FMDKMCGN1wC%2BcAZlBCHAEQACARssADYAm6UAdMBAPQjAwIqYKioBuAFAT0AD0iw4bEjmRN4JZADsAxjG6a4AWQCeAYQqRN6TTAAUYcmFQBKRBLhwo6GMigHb7h5wADwswABuAHyBQYgOEE4cqEwQMAAyOHToTHAAZLlwAbGxoRFw2kw4qKgAcjgg6AC8AOT4MjAAtHRVBG2dAOZQOMYdAMwADOPN0cXFCPGJyakZWUyEMcXBPGFRGx7O6yXbETNwzpKEQA%3D
Expected Behaviour
This mitosis code does not work in angular. (Conditionally checking for a slotProp)
e.g
      {props.slotLabel && (

          {props.slotLabel}

      )}

The template output is correct
      <ng-container *ngIf="slotLabel">

          <ng-content select="[label]"></ng-content>

      </ng-container>

However... slotLabel is not an input property on
export class MyComponent {}

So the condition will always be false meaning that part will never render.
Actual Behaviour
This mitosis code will not work in angular
      {props.slotLabel && (

          {props.slotLabel}

      )}

Additional Information
If we write the above code like this

          {props.slotLabel}

That works but if the slotLabel is not provided we get the extra div in the template which is not what we want.

This is tricky, as Angular does not seem to offer support for it out-of-the-box.
Example: Svelte has the same problem, and offers $$slots as a workaround: https://svelte.dev/docs#template-syntax-slot-$$slots
From looking around on SO, folks suggest initializing some variable that checks for the existence https://stackoverflow.com/a/64978414/1520787
https://stackoverflow.com/a/42504020/1520787
Not sure what the best solution is for Angular. We'd have to:

check if there are slots being referenced in the Mitosis code
If there are, generate some code in some lifecycle hook like ngOnInit that sets this.slotName = //...
replace the references to the slot with this.slotName

It's going to be a bit fiddly 🤔, but that's probably the best we can do for Angular. Need to think about this a tiny bit more


Super cool plugin!

Hi,
This is a great concept. Would love to know more about what's happening under the hood.
Of course, there are other frameworks in addition to CGT, eg IPNB, that would be interesting to explore as well.
Thanks, Doug

Hi Doug, thanks for the kind words.
The whole thing runs off a single LLM prompt to respond to user messages. You can see the exact prompt here. There is a small additional prompt for summarizing the conversation into a table.
You're welcome to fork the plugin and edit the prompt for local use if you'd like to experiment with other instructions. Happy to hear how it goes if you do


Get some synergy with Awesome Firebase 😎

@jthegedus has done some fantastic work collecting awesome Firebase related projects from around GH: https://github.com/jthegedus/awesome-firebase
I wonder if there is a way get some synergy going with these great initiatives?
See also: https://github.com/jthegedus/awesome-firebase/issues/31

That's ... Awesome!  Feel free to submit any of those projects here.  I'll
accept them.
On Fri, Jun 7, 2019, 5:53 PM Anish Karandikar<EMAIL_ADDRESS>wrote:

@jthegedus https://github.com/jthegedus has done some fantastic work
collecting awesome Firebase related projects from around GH:
https://github.com/jthegedus/awesome-firebase
I wonder if there is a way get some synergy going with these great
initiatives?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebaseopensource.com/issues/110?email_source=notifications&email_token=ACATB2X3MNXBVNCNOXWVRPTPZL7IXA5CNFSM4HWAEIY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYLQEYA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACATB2V3LXPTI5JHI2XPZ4DPZL7IXANCNFSM4HWAEIYQ
.

While that’s definitely a possibility, I wonder if single sourcing this and Awesome Firebase at least to certain extent could be done?

@anishkny the thing is I would prefer to get projects here one by one and make sure they have .opensource/project.json files that are configured nicely.


Updating the projects to use spring-cloud-kubernetes and made compati…

…ble with Pivotal Container Service.
initial code

ecommerce files


structure for using nc files as intermediate file format

TODO and tocheck

[ ] Make method to combine multiple 2D variables, of the same field, to a 3D variable
[ ] After reprojecting, dimensions change to lat and lon. This results in errors if reproject is applied again
[ ] test the combination methods for collection
[ ] test on surfex files


GHC 8.4.4 support

It seems that if we add
compiler-check: newer-minor

to the stack.yaml file specifying a GHC 8.4.3 snapshot, it will use GHC 8.4.4 (if it has been installed via stack setup 8.4.4).
So, do we add this to the existing 8.4.3 stack config, or make a new one specifically called stack-8.4.4.yaml with this in it?

And lts 12.15 now supports 8.4.4, so this becomes simple.

Done in #911


Why make a distinction between the below sequences and others in Tracking/Tracking_Utils.py?

if seq_name == "David":
    img_list = img_list[299:]
if seq_name == "Tiger1":
    img_list = img_list[5:]
if seq_name == "Football1":
    img_list = img_list[0:74]

And my average FPS is only 15, on NVIDIA 1080. What about yours?

I found some information in http://cvlab.hanyang.ac.kr/tracker_benchmark/datasets.html
The website shows:
In most sequences the first row corresponds to the first frame and the last row to the last frame, except the following sequences:
David(300:770), Football1(1:74), Freeman3(1:460), Freeman4(1:283).

My final result of tb100 auc is 53.99147124230077, not close to 59.2, which is also confusing...

I also tested it on a Nvidia 1080. My speed is around 80 fps. Did you visualize the tracking results during tracking? I didn't since the visualization tool in my implementation is not optimized and very slow. For the special sequences, you should also cut the previous 5 frames in Tiger1. For Freeman3 and Freeman4, it's fine since in evaluation the useless frames are cut off automatically.
About the OTB-2015 AUC, it's weird. I got the best AUC with 59.2. But ... Did you use the official toolkit from Wu's website?

I used a python tookit to process the output bbox result, the source code is https://github.com/jwlim/tracker_benchmark

I think this might be cause by the differences of float accuracy in Python 2 and 3.

By the way, using more and/or diverse training (e.g., LaSOT) can further boot the performance :)


Large regressions across many models after adding (pad + consumer) to CPU pipeline

One of samples: https://perf.iree.dev/serie?IREE?MobileNetV3Small [fp32%2Cimagenet] (TFLite) CPU-x86_64-CascadeLake full-inference%2Cdefault-flags [compilation%3Amodule%3Acompilation-time]

It seems that the (pad + consumer) is not the root cause. I disabled the feature in https://github.com/iree-org/iree/pull/10824, and there are no improvements.

Just want to note that the regression seems to be on compilation time not the latency.

Oh, I didn't notice that... dana isn't great at making that clear x_x
Still, a big increase in compile time isn't good - was this from changing build machines or some other build configurations outside of source control?

The build machines provide much less stable performance, but 40% is a lot. I'll check if there is an issue or change on the machine.

Given that our compile times are way too long today doubling them has to have a really good benefit to be worth it - if we didn't see major performance changes in runtime but do see nearly all models taking 2x longer to compile that's not good :)

As the result of the revert https://github.com/iree-org/iree/pull/10824, it looks like the improvement on the compilation time matched the regression. So it might be actually the root cause.

Good catch! Would be good to dig into ways of making the pipeline more efficient - a 40% increases is massive and mobilenet is a tiny model - we don't want to death-by-a-thousand-papercuts our way to multi-day compile times.

Good point! I thought the new passes won't impact the compilation time for default path a lot, but it seems not. Definitely have to take some time on it!

(ping on this - a 50% compile time reduction is pretty big)

I can't reproduce it on my workstation. They all takes 34 seconds on my machine with --mlir-disable-threading flag; 40 seconds w/o --mlir-disable-threading. I can try to reproduce it on a x86_64-CascadeLake VM.
(I know it's weird that multi-threaded is slower, but it's not the point for this issue. That should be a separate issue.)


Adding in default type argument to PromiseFuture

99+% of the time Promises have a JavaScript Error object as their error.
In addition, Futures require the error type to be the same when using combinators (such as and_then), so it's beneficial to encourage the use of a single Error type (the alternative is to constantly cast between error types, which is pretty verbose).
Therefore, I think it makes sense to make the error type of PromiseFuture optional (it defaults to webapi::error::Error). This solves both of the above problems, while still allowing for error customization in the rare cases where it is needed.

LGTM, thanks!


Updating docs to have the right font loaded

Fixing font loading by copying the fonts folder into the docs folder when creating them.
Did the same for the manifest.json file.
Added the bundle.css file too on the main layout.


OpenAL alcMakeContextCurrent error ?

Not sure if it's me or I am missing something,
I have a weird AL10.alGetError() state stuck on 40964,  AL_INVALID_OPERATION the requested operation is not valid, when trying to destroy the context.
Here is a minimal test case with the problem :
long device = ALC10.alcOpenDevice((ByteBuffer) null);
ALCCapabilities deviceCaps = ALC.createCapabilities(device);
long context = ALC10.alcCreateContext(device, (IntBuffer) null);
ALC10.alcMakeContextCurrent(context);
AL.createCapabilities(deviceCaps);

int error = AL10.alGetError();
if (error != AL10.AL_NO_ERROR) {
	System.err.println("OpenAL Error 1 " + error);
}

System.out.println(context + " is the current context");

//I put 0 to mean NULL, not sure about that but can't pass anything else as it takes a long
boolean test = ALC10.alcMakeContextCurrent(0);
if (!test)
	System.err.println("error alcMakeContextCurrent");

System.out.println(context + " is the current context");

ALC10.alcDestroyContext(context);
error = AL10.alGetError();
if (error != AL10.AL_NO_ERROR) {
	System.err.println("OpenAL Error 2 " + error);
}
ALC10.alcCloseDevice(device);
error = AL10.alGetError();
if (error != AL10.AL_NO_ERROR) {
	System.err.println("OpenAL Error 3 " + error);
}

It produces the following output:

6375408 is the current context
6375408 is the current context
OpenAL Error 2 40964
OpenAL Error 3 40964

but it seems to do the job since I have no error message like AL lib: (EE) alc_cleanup: 1 device not closed
I'm using lwjgl 3.0.0

I have a weird AL10.alGetError() state stuck on 40964, AL_INVALID_OPERATION the requested operation is not valid, when trying to destroy the context.

The alGetError function is an AL function. It can only be called within an active OpenAL context, that's why you're getting an INVALID_OPERATION error. If you switch to ALC10.alcGetError the errors will go away, your cleanup code works fine.

I put 0 to mean NULL, not sure about that but can't pass anything else as it takes a long

LWJGL defines a NULL constant in the MemoryUtil class. When used with static imports (the recommended style), code becomes like boolean test = alcMakeContextCurrent(NULL);, which is clean and easily understandable.

System.out.println(context + " is the current context");

The second time this is called it should probably be changed to System.out.println(alcGetCurrentContext() + " is the current context");

Allright my bad then, couldn't find the information about alGetError only working with an active context !
Thanks for the help ! And thanks for the lib :)


GEODE-9552: Handle ForcedDisconnectException in ExecutionHandlerContext

Authored-by: Donal Evans<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Closing this PR for now as further discussion is needed on the best way to handle various server-side exceptions.


Share data between Android / IOS

It's possible share data between Android and IOS using this library?
for example:

share link from Android to IOS
share link from IOS to Android

And so on....

Hi @rodgomesc Sorry for the late response. It's not possible to share data between iOS / Android using this library now. That's because this library only focus on "reader" mode of NFC, to communicate between devices, one of them should be a tag.

I would like to understand something, can we share data between Android to Android or iOS to iOS?

@ifeoluwak Android <--> IOS using NFC

@ifeoluwak Currently it's not possible to perform iOS to iOS communication. For Android to Android communication can be accomplished with 'Android Beam' feature, which is NfcManager.setNdefPushMessage API.

what are possibilities today ? can we share data between 2 devices ??

Hi @amitbravo No, those APIs are deprecated by Google~


winusb: 3.2.1 -> 3.2.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from woeusb.
meta.description for winusb is: '"Create bootable USB disks from Windows ISO images"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/h3s3raf3irlqh3796za9b172kcdr69nj-woeusb-3.2.2/bin/woeusb passed the binary check.
Warning: no invocation of /nix/store/h3s3raf3irlqh3796za9b172kcdr69nj-woeusb-3.2.2/bin/woeusbgui had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/h3s3raf3irlqh3796za9b172kcdr69nj-woeusb-3.2.2/bin/.woeusb-wrapped had a zero exit code or showed the expected version
1 of 3 passed binary check by having a zero exit code.
1 of 3 passed binary check by having the new version present in output.
found 3.2.2 with grep in /nix/store/h3s3raf3irlqh3796za9b172kcdr69nj-woeusb-3.2.2
directory tree listing: https://gist.github.com/eb16a86e90c3e1e9f0b1198fdcd9622f
du listing: https://gist.github.com/e164d8518e2221e19fac0ab3a590f8a9

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/5e5ccbeb1a2c114017ab1dabb49dd307d36c0b8c.tar.gz -p winusb
ls -la /nix/store/h3s3raf3irlqh3796za9b172kcdr69nj-woeusb-3.2.2

cc @bjornfor @gnidorah for testing.

Applied to master (788cab1ae7c58d900e30a0f6f1429d0599bacfa3).
@r-ryantm: The commit message refers to "winusb", which is a backwards compat alias for "woeusb". I changed the commit message to use the canonical name (woeusb). Perhaps something to look into for your auto update scripts?

@bjornfor We have an issue tracking this: https://github.com/ryantm/nixpkgs-update/issues/37 we haven't really thought of a particularly good solution to this problem yet.


SAMv7 Progmem driver byte write lead to ECC errors and flash data corruption

SAMv7 progmem (internal flash) driver does not perform byte writes correctly.
The driver assumes that it is possible to read page content, change erased (0xFF) bytes value and write page back to flash. That is usually a case for most of standard flashes, but SAMv7 internal flash has built-in ECC support, so applying such procedure destroys the flash content and rise "Multiple ECC Error" bit in EEFC_FSR register. The partial page programming of internal flash is of course possible, but with some restrictions specified in datasheet.

So only the first partial programming after erase is forking fine.
I found this and debugged for a while trying to place MTD config data on top of internal flash page.
Just logging it here as I do not plan to do anything with it, but this information may save investigation time for someone else.

@pkarashchenko is this related with similar flash ECC error you were fighting some time ago?

Thank you for explanation! Maybe it could be useful for @michallenc @adamfeuer and @TimJTi since they are using SAMv7 chips.

No internal flash on SAMA5D2 but thanks for heads-up!

The S32K3XX also has ECC flash, doing back-to-back writes would much invalidates the ECC value.
On the S32K3XX however we can disable the ECC for the special data region so we can do back-to-back on specific region and implement things like LittleFS.
https://github.com/apache/nuttx/blob/23d42632079cc8e5671b7cdceba874091172bebc/arch/arm/src/s32k3xx/s32k3xx_progmem.c#L430-L432

I think turning off the ECC does not help here as seems like flash has a "NAND nature", so bits are getting corrupted on write, so reading back data do not match with data just written. Only full sector read-erase-write sequence works reliably, but progmem interface assumes a "NOR nature" of the underlying flash.

yes there is no execute in place capabilities, you need two kind of strategies NAND volatile and soon be gone NOR flash memories.


Customize the workflow of the agent

The workflow of custom agents is important for controlling the behavior of large models, and it is expected to increase the feature of defining the workflow of agents in a way with low code visualization

the same question


Scaling lag in Functions on ACA

Hi I am comparing scaling behavior for various .NET services flavors here https://github.com/KaiWalter/message-distribution#tldr-conclusionand see that there seems to be a gap, before Functions on ACA pick up items from Service Bus queues. Is that to be expected?

GitHub - KaiWalter/message-distribution](https://github.com/KaiWalter/message-distribution)

@KaiWalter - lets track this discussion in this thread

Is there a way to also scale Fun-on-ACA to minimal 1 scale unit?

@kaibocai  - Does this mean you want to set max scale instances to '1'? cc// @krishnajaju

The pattern with the gap suggests that maybe the 2 other Functions need to be scaled up from 0 to something to pick up ingress from queues. Hence I would want to try with minScale=1

Hi @KaiWalter,
Thanks for raising the issue. Can you add some information about the experiment done to get these graphs? What do these graphs represent? Also, please share the expected behavior and the actual behavior.
Can you share the function app name?

Sure @krishna-kariya
So the experiment is described and implemented in this repo - please check out README
Basically I am comparing scaling behavior between Function deployed as regular ACA container (src/func* C# projects and infra/func* templates) vs Function on ACA deployment (src/acaf* C# projects and infra/acaf* templates).
If you look at the graph above, I would expect the same scaling behavior: top graph shows func* variant scale increasing and descreasing as expexted and botton graph shows acaf* first scaling up the distributor/dispatcher part, then a gap and the scaling up receiver parts.
Container App names:

NAME
TYPE
LOCATION

kw-messdis2acafdistributor
Function App
West Europe

kw-messdis2acafrecvexp
Function App
West Europe

kw-messdis2acafrecvstd
Function App
West Europe

kw-messdis2funcdistributor
Container App
West Europe

kw-messdis2funcrecvexp
Container App
West Europe

kw-messdis2funcrecvstd
Container App
West Europe

kw-messdis2testdata
Container App
West Europe

Subscription Id I could share in a private conversation e.g. on Discord or email.
Is this information sufficient?

Hi @KaiWalter ,
I was looking into this issue. I found one difference between both deployments which is Container Apps with Functions image (func) has scale rule for servicebus scaler with messageCount as 100 while Azure Functions on Container Apps (acaf) uses Keda default settings currently. Default value for messageCount is 5. This can be a reason for difference you are observing.
One difference in code for both deployments is acaf uses dotnet-isolated runtime while func uses dotnet runtime. Can you run both deployments with same configuration, same code?

@krishna-kariya I will convert func also to dotnet-isolated and be back here.

@krishna-kariya with branch https://github.com/KaiWalter/message-distribution/tree/func-isolated I also changed the Functions in ACA Containers func variant to dotnet-isolated, but that had no effect.
func stilll peeking once

while acaf Functions on Container Apps shows this scaling gap

@KaiWalter, it looks like the default resources used by single Functions on ACA instance is more compared to resources used by single Container App instance with functions image.
Resource allocation for single instance:

Azure Functions on ACA (Default)

cpu - 1
memory - 2.0Gi

Azure Container Apps (Configurable)

cpu -0.25
memory - 0.5 Gi

Initially, some default numbers of nodes are allocated for any ACA environment. When scaling, these nodes are used to create app instances. For container apps scaling, the default number of nodes are sufficient as it is uses less cpu, memory per instance. For function apps scaling, the default number of nodes is not sufficient and thus, ACA environment requests more nodes in backend. After new nodes are available to ACA environment, it uses them to create remaining instances for Function app. It takes some time to get new nodes and create instances, so, we see a gap in processing between both deployments.

@KaiWalter , Do you have any other questions?

@krishna-kariya sorry for getting back so late - I was enjoying my summer vacation.
OK, the information you provided makes sense and explains the delay before scaling up.
@syneex this is something we need to consider - gets closer to the Functions on Service Fabric Containers behavior again.

@KaiWalter for functions on ACA you will soon be able to configure CPU/memory using workload profile types (both Consumption or Dedicated) . With this you should be able to choose configs as you chose for ACA and get similar performance


Toddler lock toggle not showing up on Home Assistant for Hatch Rest+ (first generation)

I have three Rest+'s (two first generation and one second generation). The toddler lock toggle is available for the second generation Rest+ in the HA device screen, however the toddler lock toggle is not displaying for the two first generation Rest+'s. Per the description of this integration the toddler lock toggle is not supported for both generations of the Rest+. Is this a bug, expected behavior, or am I missing something? Thank you for developing this great integration!

this is expected behavior, toddler lock is available for 2nd gen only, first gen toddler lock feature is only available through hatch native scheduled programs.


test layout + initial sample smoke test for issue #72

I have most/all of the changes incorporated, just working on getting the remote testing working again and trying to remove the gcloud exec requirement for that project id...once I get remote working I'll take another pass through the pom's and update the pr

Sounds good. Thanks!

@meltsufin pushed update that should address all the details above

LGTM! :+1:


 This can break production builds. Did you remember to run a production build locally to verify they still work?

Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work?

Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work?

This is probably not the best place to deliver this feedback, but what is the difference between default and large for the header text size? I actually think large (assuming it's 17) is probably the default here. In fact, I think the only other time we would have a non-17 sized font in the header area is for chats. And I think that's okay - it's almost like we aren't using a font-size for the header title but rather, we are using a component as the header title - with the component being the little avatar(single, two, or counter) + name(s) component we use.

Oh hmm yeah that's a good point @shawnborton. Looking through the code now and I don't really see anything passing this prop at all. I think all of the headers are set to have "large" text.

Actually this is only true for HeaderWithCloseButton
https://github.com/Expensify/Expensify.cash/blob/66d265e144a69f0a40bf5ca05d1b506a5a19a4bd/src/components/HeaderWithCloseButton.js#L37-L45

e.g. the IOU view is not using the large text

Ah got it, the IOU view should be using the larger text size. I say we remove it as a prop and just update the default header styles everywhere to use 17px as the font size unless a component replaces the header title.

We could probably change this to textSize="small" and have the default be 17 if that makes more sense.

Fixed up that Header issue @shawnborton and added some stories for the more complex HeaderWithCloseButton. It shows off the variations:
https://user-images.githubusercontent.com/32969087/118315456-407b1d80-b491-11eb-8c85-20d3559f1357.mp4

Woo, thanks Marc!

Wowwww this is so cool

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging in version: 1.0.46-1🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@roryabraham Heyo! Are we able to test this? I tried navigating to https://staging.expensify.cash/docs and I was unable to access storybook.

@isagoico can check this off as we'll need to fix this somewhere else but can access via /docs/index.html for now. It's not a blocker in any case.


Help extracting data correctly

Hello I've attempted to extract the data from the attached PDF file in several different ways but I'm not having success getting the data extracted accurately. I will need to extract data from four similar documents for a story I am writing. Thank you.
caseloadcounty17 66.pdf

@moed Looks like a pretty gross PDF. You'll probably want to create one selection box for each sub-table (e.g. the CIVIL table); be sure to exclude the headers. Those always cause trouble.


Fix science doc open.

This now uses a local HTTP server to serve docs which is much more
straightforward than trying to hack around all the quirks trying to
serve a site via file:// URLs brings.

Hrm. Yeah - getting this to work on Windows block and it still does not. I'm going to convert to draft and ping you all again when I have Windows daemons / services / whatever I need - figured out.


Backport v1.24 deps: bumps Wasmtime to 6.0.1 (#26190)

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

@RiverPhillips ive picked the CI optis onto the 1.24 branch already so you should only need to pick the other rust commits

wierd i committed from here and then it told me it has conflicts


28751

Ok, I think I'm beginning to get the hang of this. Sorry for using you for experimentation!

Sorry for using you for experimentation!

None needed! That's what I'm here for. :) Looks great.
Since you're getting the hang of things, here's an advanced tip: if you say
rust-lang/rust#28751

instead of just 28571, github will automatically link the two, which is kinda neat. Not required, though, so this one is good to go!

Ok, I'll do that from now on - thanks!


Feature Request: Compatibility with New Google Lab Search

Expected Behavior

The new google search ai hides the ublacklist button. I hope the button can adapt with this new google search feature.
without the google search ai feature, The ublacklist button shows normal.

Actual Behavior
The ublack list can adapt with the new google search ai feature.

Search engine: Google
Language: en-US
Region: US

Recently, I switched to a new computer. Although all of my Chrome extensions were synchronized, I noticed that the subscription links for uBlacklist weren't added. Tonight, after I finished adding them, I was pleasantly surprised to see that the conflict between the uBlacklist block button and Google's SGE (Search Generative Experience) has been resolved. Thank you to the developer for your hard work and dedication. ❤ ❤ ❤


RED-90: Improve node rotation handling

Use http status code for handling rotation edge responses

Closing for forseeable future.


fix invertSensor input

Fixed incorrect wheel angle sensor center ,when invert sensor input

For whatever reasons I never get notifications if a pull request is issued :-(
Regarding your logic change: The logic operates completely with positive numbers now (sensor reports -1 to 1, in reality only -1 to zero (ads with reference on VDD) or zero to 1 (normal inputs, ADS with reference to GND) => make an "fabs" before inverting ist => allway zero to one ), and center is by default 0.5 => 1-value is now inverting. not multiply it with -1.


Keysight DMM L4411A is tested.

The DMM is tested for [discover+scpi].
It Works well.
34410A and 34411A are same generation and product family.  They will work fine as well.

Thanks. I've added it to the list of tested instruments. 👍🏻


review if there is sufficient of back pressure tools within rama

There's already the LimitLayer that can be used to put a limit, globally or specific, on how much requests can be processed (e.g. at once or over time).
Next to that there's the open telemetry support issue (#23) which will provide metrics on both the TCP and HTTP Layer regarding the request flow and so on. This in turn can inform external load balancers on how much traffic to send to the individual proxy instance.
I believe all in all this might be sufficient, especially for a first release. But never the less, this issue is here to have a reminder near the closure of this milestone (v0.2) and keep in mind if we have to still provide something else or not. During that time it also gives others the chance to react to this ticket if they have a different opinion/take on this matter.

After careful consideration I think for a v2 release there is sufficient already in place. The open telemetry metrics will be cherry on the top. Rate limiting is the way to go, with metrics to load balance on top of that and scale up/down as needed (or even block traffic, especially malicious one).


feat: add cypress to ui template, use ngcc LSA-999

Add Cypress to template
Run ngcc to avoid errors during npm start

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


And if we don't want to use Facebook?

The default git repo seems to require a facebook instance of an app before it will allow me to upload.  I get the following error:  Unable to upload policy. Reason : Validation failed: 1 validation error(s) found in policy "B2C_1A_TRUSTFRAMEWORKBASE" of tenant "XXXXXXXXXXX.onmicrosoft.com".Tenant "XXXXXXXXXXX.onmicrosoft.com" does not have CryptographicKey referenced by storageReferenceId "B2C_1A_FacebookSecret".
I really don't want my users to use facebook to authenticate.  I'm just trying to hook my azureAD up to my B2C.

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

ID: bee63035-00ee-f7fd-97a1-69dae5f808ef
Version Independent ID: a3447928-73cc-0290-6d46-b89234757e3b
Content: Azure Active Directory B2C: Get started With custom policies
Content Source: articles/active-directory-b2c/active-directory-b2c-get-started-custom.md
Service: active-directory-b2c
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@argrithmag There are multiple samples being published related to Azure AD B2C. Refer to below link to find list of samples and check which one will help with your requirement -
https://docs.microsoft.com/en-us/azure/active-directory-b2c/code-samples
You can add the identity provider based on your requirement. You can refer to below document and check left side of reference related document tree where you can find documents on how to add different identity provider based on your requirement.
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-setup-oidc-idp

@argrithmag We will now proceed to close this thread. If there are further questions regarding this matter, please open a new issue and we will gladly continue the discussion.

https://github.com/MicrosoftDocs/azure-docs/issues/47270


Document loader unable to load URL "https://w3id.org/security/suites/ed25519-2020/v1".

Not sure if this is quite the right place to track this.
But it seems this URL is redirecting to an old version of the spec - https://digitalbazaar.github.io/ed25519-signature-2020-context/contexts/ed25519-signature-2020-v1.jsonld
Should it be redirecting here - https://w3c.github.io/vc-di-eddsa/?
I ran into this issue when trying to use this suite with the vc-js lib to sign a VP

@wip-abramson - Yeah, this is likely not the right repo to track this. But in general - I suspect what's happening is that your documentLoader does not enable fetching URLs from the web. (That behavior is disabled by default.) To be able to fetch the URL, you'll want to do something like https://github.com/digitalcredentials/security-document-loader#fetching-from-the-web

Ah I see, thanks. Yep we can close this issue. For some reason my ISP was not letting me access the file on the web which made me think it was a bad URL.
I was also confused that I managed to get around this issue by switching to the 2018 version. Where did the context from that come from?
I had not come across the security document loader library.
So best practice is I download the context, then add it using the addStatic method. I will try that.

@wip-abramson

Where did the context from that come from?

heh, so, the 2018 suite is actually included in the base VC context :) (But not the newer suites)

Makes sense, thanks @dmitrizagidulin


system clipboard is lost when vim is put in background (or closed)

Describe the bug
When putting something into the system clipboard using e.g. "+yy, its content is lost once the vim instance is put in background using ctrl+z (or when vim is closed).
To Reproduce
Detailed steps to reproduce the behavior:

Open any file using vim
"+yy one line
Ctrl+z (or quit vim)
try to paste it in any application (gedit, terminal, ...)
Oberve that it does not paste anything

If you skip step 3, you will see the pasted text in step 5 as expected.
Expected behavior
The system buffer should not be lost when the application is put in background (or closed).
Environment (please complete the following information):
$ vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 29 2019 20:38:53)
Included patches: 1-1776
Compiled by Arch Linux
Huge version with GTK3 GUI.
Additional context
May be relevant:

https://freedesktop.org/wiki/ClipboardManager/
https://wiki.ubuntu.com/ClipboardPersistence
https://askubuntu.com/questions/12047/inconsistent-copy-and-paste-behaviour-is-there-a-fix

this has been just recently been discussed on the vim_use mailinglist:
https://groups.google.com/d/msg/vim_use/T9iMTBskDZk/9RpUj3ciAwAJ
TLDR: That is how the clipboard works. You need to install a clipboard manager for your desktop environment in order to make the clipboard work as you expect.


Bug: it doesn't work, windows 10 64bit

Something went wrong
Service Error: panic({0x7ff61424c820, 0x7ff6148e72f0}) C:/hostedtoolcache/windows/go/1.20.11/x64/src/runtime/panic.go:884 +0x213 mintter/backend/daemon/api/accounts/v1alpha.(*Server).ListAccounts(0xc000498080, {0x7ff6148f82e8, 0xc0001f2bd0}, 0x0?) C:/a/mintter/mintter/backend/daemon/api/accounts/v1alpha/accounts.go:293 +0x205 mintter/backend/genproto/accounts/v1alpha._Accounts_ListAccounts_Handler.func1({0x7ff6148f82e8, 0xc0001f2bd0}, {0x7ff614353da0?, 0xc00141e700}) C:/a/mintter/mintter/backend/genproto/accounts/v1alpha/accounts_grpc.pb.go:178 +0x78 mintter/backend/daemon.GRPCDebugLoggingInterceptor.func1({0x7ff6148f82e8, 0xc0001f2bd0}, {0x7ff614353da0, 0xc00141e700}, 0xa?, 0xc00109b200) C:/a/mintter/mintter/backend/daemon/debug.go:52 +0x77 google.golang.org/grpc.getChainUnaryHandler.func1({0x7ff6148f82e8, 0xc0001f2bd0}, {0x7ff614353da0, 0xc00141e700}) C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1163 +0xb9 go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.UnaryServerInterceptor.func1({0x7ff6148f82e8, 0xc000d27d70}, {0x7ff614353da0, 0xc00141e700}, 0xc00059bd20, 0xc00141e800) C:/Users/runneradmin/go/pkg/mod/go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc@v0.25.0/interceptor.go:325 +0x676 google.golang.org/grpc.chainUnaryInterceptors.func1({0x7ff6148f82e8, 0xc000d27d70}, {0x7ff614353da0, 0xc00141e700}, 0xc0009efa50?, 0x7ff61424afc0?) C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1154 +0x8f mintter/backend/genproto/accounts/v1alpha._Accounts_ListAccounts_Handler({0x7ff61430bb80?, 0xc000498080}, {0x7ff6148f82e8, 0xc000d27d70}, 0xc0001461c0, 0xc000483ea0) C:/a/mintter/mintter/backend/genproto/accounts/v1alpha/accounts_grpc.pb.go:180 +0x138 google.golang.org/grpc.(*Server).processUnaryRPC(0xc00000c5a0, {0x7ff6149038e0, 0xc0007c7c20}, 0xc000f07440, 0xc000422870, 0x7ff613e52270, 0x0) C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1336 +0xd33 google.golang.org/grpc.(*Server).handleStream(0xc00000c5a0, {0x7ff6149038e0, 0xc0007c7c20}, 0xc000f07440, 0x0) C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1704 +0xa36 google.golang.org/grpc.(*Server).serveStreams.func1.2() C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:965 +0x98 created by google.golang.org/grpc.(*Server).serveStreams.func1 C:/Users/runneradmin/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:963 +0x28a

@vegasmurp Did you get this message from the application UI? Unfortunately this is probably only a portion of the entire stack trace. Could you see the logs in your application data directory?
/cc @horacioh Could you point to the exact directory where the log files are stored on Windows?

main.log

when it first launched it gave an error something like cannot connect to 2023.1.10 then asked me to install a newer version. which it did / I did. then it started the setup process / wizard / getting started. I allowed it through windows firewall. it gave me a mnemonic, then I click the button to go to the next step, and it spews that giant error message. it's unusable sorry.

Have you used the app before and created any content? Or this is the first time you downloaded it? @vegasmurp

first time using

@vegasmurp have you tried starting from scratch? Looks like something went wrong with your installation, but I can't tell for sure what. So I'd suggest wiping out the entire data directory and start from scratch. Let us know if it ends up working.

deleted Mintter folder in "C:\Users\Sam\AppData\Roaming". seems to be find now

Great. I'll close this issue. Feel free to reopen if you continue having issues.


problem with stealth

i got a problem with the stealth, can i get any help pls? <3
from selenium import webdriver
from selenium_stealth import stealth
import time

options = webdriver.ChromeOptions()
options.add_argument("start-maximized")

# options.add_argument("--headless")

options.add_experimental_option("excludeSwitches", ["enable-automation"])
options.add_experimental_option('useAutomationExtension', False)
driver = webdriver.Chrome(options=options, executable_path=r"/home/eslammustafa/Desktop/PY Projects")

stealth(driver,
        languages=["en-US", "en"],
        vendor="Google Inc.",
        platform="Win32",
        webgl_vendor="Intel Inc.",
        renderer="Intel Iris OpenGL Engine",
        fix_hairline=True,
        )

url = "https://bot.sannysoft.com/"
driver.get(url)
time.sleep(5)
driver.quit()

and the problem is:
Python 3.8.10 (default, Nov 26 2021, 20:14:08)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license()" for more information.
>>>
====== RESTART: /home/eslammustafa/Desktop/PY Projects/selenium-stealth.py =====

Warning (from warnings module):
  File "/home/eslammustafa/Desktop/PY Projects/selenium-stealth.py", line 12
    driver = webdriver.Chrome(options=options, executable_path=r"/home/eslammustafa/Desktop/PY Projects")
DeprecationWarning: executable_path has been deprecated, please pass in a Service object

Warning (from warnings module):
  File "/home/eslammustafa/.local/lib/python3.8/site-packages/requests/__init__.py", line 89
    warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
RequestsDependencyWarning: urllib3 (1.26.8) or chardet (3.0.4) doesn't match a supported version!
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/selenium/webdriver/common/service.py", line 71, in start
    self.process = subprocess.Popen(cmd, env=self.env,
  File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: '/home/eslammustafa/Desktop/PY Projects'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.8/idlelib/run.py", line 559, in runcode
    exec(code, self.locals)
  File "/home/eslammustafa/Desktop/PY Projects/selenium-stealth.py", line 12, in <module>
    driver = webdriver.Chrome(options=options, executable_path=r"/home/eslammustafa/Desktop/PY Projects")
  File "/usr/local/lib/python3.8/dist-packages/selenium/webdriver/chrome/webdriver.py", line 70, in __init__
    super(WebDriver, self).__init__(DesiredCapabilities.CHROME['browserName'], "goog",
  File "/usr/local/lib/python3.8/dist-packages/selenium/webdriver/chromium/webdriver.py", line 90, in __init__
    self.service.start()
  File "/usr/local/lib/python3.8/dist-packages/selenium/webdriver/common/service.py", line 86, in start
    raise WebDriverException(
selenium.common.exceptions.WebDriverException: Message: 'PY Projects' executable may have wrong permissions. Please see https://chromedriver.chromium.org/home

>>>

I don't think this has anything to do with stealth, try enabling write permissions (chmod a+x <path> iirc).
First error is telling you to provide the binary path as a service.
The way I use selenium is:
PATH = <path to chromedriver>
options = Options()
options.binary_location = <path to chrome binary>
self.driver = webdriver.Chrome(PATH, options=options)

the executable path requires an executable, not a folder.
You should change line 12 to:
driver = webdriver.Chrome("/home/eslammustafa/Desktop/PY Projects/chromedriver", options=options)

Add whatever extension the chromedriver file has to the end.

Im really thank you 🥰🌹


Fix flaky test in DescriptionGenericBuilderTest by sorting for deterministic iterations

This PR fixes 1 possible test failure in module byte-buddy-dep
1. Test that could fail

Module: byte-buddy-dep
Class Name: net.bytebuddy.description.type.TypeDescriptionGenericBuilderTest
Test Name: testTypeAnnotationExceptionType

2. Why the test might fail?

The mentioned test tests the exception types of TypeAnnotationSamples.foo:35, which are of type Generic and RuntimeException. But, it assumes the exception types to be in the declared order, ie.Generic followed by RuntimeException.
The exception types are returned by Method.getGenericExceptionTypes at TypeDescriptionGenericBuilderTest.java:43, but there is no official documentation that mentions this order will be same as the declared order.
Since there is no guarantee in order of exception types returned, the order might change, resulting in the test failure.

3. How to reproduce?

I used an open-source tool called NonDex for detecting the assumption by shuffling the order of returned exception types.
Running the following commands will reproduce

# Clone the Repo
https://github.com/raphw/byte-buddy.git

# Compile the module byte-buddy-dep
mvn clean install -pl byte-buddy-dep -am -DskipTests

# (Optional) Run the unit test
mvn -pl byte-buddy-dep test -Dtest=net.bytebuddy.description.type.TypeDescriptionGenericBuilderTest#testTypeAnnotationExceptionType

# Run the unit test using NonDex
mvn -pl byte-buddy-dep edu.illinois:nondex-maven-plugin:2.1.1:nondex -Dtest=net.bytebuddy.description.type.TypeDescriptionGenericBuilderTest#testTypeAnnotationExceptionType

Expected Result

The test should have passed successfully without any errors with NonDex.

Actual Result

Running with NonDex produced the following result

[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   TypeDescriptionGenericBuilderTest>AbstractTypeDescriptionGenericTest.testTypeAnnotationExceptionType:1448
Expected: is <NON_GENERIC>
     but: was <VARIABLE>
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0

4. How I fixed?

This PR ensures the order of the exception types returned by Method.getGenericExceptionTypes remain consistent across different runs by sorting the array based on the type name.
I ran all the tests for the module using the command mvn test -pl byte-buddy-dep, and all the tests passed.

Your fix looks good to me and your PR is simple and clear.

Congratulations!


Can't run ./start.sh - Error

Error description:
I cant use ./start.sh whats the problem?
Steps to reproduce
#
# Docker Logging Config
#
# This section offers two options max-size and max-file, which follow the docker documentation
# as follow:
#
  logging:
       driver: "json-file"
       options:
         max-size: "200k"
         max-file: "10"
#
NGINX_WEB_LOG_MAX_SIZE=4m
NGINX_WEB_LOG_MAX_FILE=10

NGINX_GEN_LOG_MAX_SIZE=4m
NGINX_GEN_LOG_MAX_FILE=10

NGINX_LETSENCRYPT_LOG_MAX_SIZE=4m
NGINX_LETSENCRYPT_LOG_MAX_FILE=10

Expected result
Error result
Creating nginx-web ... error
Creating nginx-letsencrypt ...
Creating nginx-gen ...
Creating nginx-letsencrypt ... error
ERROR: for nginx-web  Cannot create container for service nginx-web: unknown log opt 'max-size' for journald log driver
Creating nginx-gen ... error
ERROR: for nginx-letsencrypt  Cannot create container for service nginx-letsencrypt: unknown log opt 'max-size' for journald log driver

ERROR: for nginx-gen  Cannot create container for service nginx-gen: unknown log opt 'max-size' for journald log driver

ERROR: for nginx-web  Cannot create container for service nginx-web: unknown log opt 'max-size' for journald log driver

ERROR: for nginx-gen  Cannot create container for service nginx-gen: unknown log opt 'max-size' for journald log driver

ERROR: for nginx-letsencrypt  Cannot create container for service nginx-letsencrypt: unknown log opt 'max-size' for journald log driver

Comments

As we did not have a confirmation we will assume you have resolved with @j7an hint. If you have any other issue let us know.

Hi - I'm also getting this error, and I have the logging lines as @j7an mentioned, commented out
`# logging:
driver: "json-file"
options:
max-size: "200k"
max-file: "10"

#NGINX_WEB_LOG_MAX_SIZE=4m
#NGINX_WEB_LOG_MAX_FILE=10
#NGINX_GEN_LOG_MAX_SIZE=2m
#NGINX_GEN_LOG_MAX_FILE=10
#NGINX_LETSENCRYPT_LOG_MAX_SIZE=2m
#NGINX_LETSENCRYPT_LOG_MAX_FILE=10`


Fixing ubuntu 16.04/Swift 4.2 swift test issue.

please note that wait(for:timeout) is not available in ubuntu 16.04/Swift 4.2.

detail of the issue:
/home/seungkoo/Downloads/tmp/Perfect-HTTP/Tests/PerfectHTTPTests/PerfectHTTPTests.swift:688:34: error: extra argument 'timeout' in call
                        wait(for: [expect1], timeout: 10)
                                                      ^~
/home/seungkoo/Downloads/tmp/Perfect-HTTP/Tests/PerfectHTTPTests/PerfectHTTPTests.swift:706:34: error: extra argument 'timeout' in call
                        wait(for: [expect2], timeout: 10)
                                                      ^~
error: terminated(1): /usr/local/swift-4.2-RELEASE-ubuntu16.04/usr/bin/swift-build-tool -f /home/seungkoo/Downloads/tmp/Perfect-HTTP/.build/debug.yaml test output:

Thanks @seungkoo


simple-cipher: PEP8 compliance updated

The exercise simple-cipher had some minor inconsistencies with PEP8 which I fixed (#214).
tmo$ flake8 simple-cipher/
simple-cipher/simple_cipher_test.py:40:80: E501 line too long (116 > 79 characters)
simple-cipher/simple_cipher_test.py:49:80: E501 line too long (116 > 79 characters)
simple-cipher/simple_cipher_test.py:62:13: E128 continuation line under-indented for visual indent
simple-cipher/simple_cipher_test.py:64:13: E128 continuation line under-indented for visual indent

Thanks


does not work with CouchDB 2.0

When using CouchDB 2.0 (dbUrl option) and I sign up for a new user account, then no database is being created.

Is this a confirmed bug? I am having the same problem. As a workaround if I manually create a document in hoodie-store using the role id for the new user I can get it to work.

I did not yet have time to investigate it. If someone could start an app once with a fresh CouchDB 1.7 and once with CouchDB 2.0 and compare logs, that’d be helpful.
start it with npm start -- --loglevel=verbose

Ok, I did this and the hoodie logs are attached for CouchDB 1.6 and 2.0.
HoodieLogs.txt
If I compare on the CouchDB side a user/7r97pa8 database is created on 1.6 and a user/bii2ges is created on 2.0 so that seems to be working. However there is a doc in the hoodie-store database on 1.6 which does not exist on 2.0. The doc is as below and if I create a doc like this for user/bii2ges directly in 2.0 it seems to start working. I have had a quick look but haven't been able to find the code that creates the hoodie-store doc for the user.
Hope this helps. Cheers, Colin
{
   "_id": "db_user/7r97pa8",
   "_rev": "1-5eeb02375a17be2e26da8ed590f168f6",
   "access": {
       "read": {
           "role": [
               "id:7r97pa8"
           ]
       },
       "write": {
           "role": [
               "id:7r97pa8"
           ]
       }
   },
   "hoodie": {
       "createdAt": "2017-04-18T12:05:44.921Z"
   }
}

Hey! I had a deeper look on what's going on and I think I might have found a possible cause for the problem. It's the first time I dig that deep into the Hoodie code so I might get something wrong. Let's see:
What's different with CouchDB 2 ist that this event listener in @hoodie/server won't be called after using hoodie.account.signIn (this is the case for CouchDB 1.6). The reason for that might be that the emitter in @hoodie/account-server-api never emits the event. Actually, it doesn't hook into the change feed there.
If I understood correctly, state.db.changes is a PouchDB method. Interesting is, when I set includeDocs to false or omit it completely, it does hook into the change listener. So might the underlying problem be an issue with PouchDB and not with Hoodie itself?
Not sure if this is really related, but there is an open issue https://github.com/pouchdb/pouchdb/issues/6436 on the PouchDB repo finding that changes has problems with CouchDB 2.

This will be fixed in not yet released CouchDB 2.1.0:
https://issues.apache.org/jira/browse/COUCHDB-3390

Last information I’ve heard from CouchDB folks is that the earliest release date is end of June.
It would still be nice to find a workaround if at all possible. And if not, we should log an error saying that Hoodie is not compatible with CouchDB 2.0.0 due to the bug linked above

2.1.0 not released yet :-(
https://issues.apache.org/jira/projects/COUCHDB/versions/12334020
Any news on that?

It’s close: https://github.com/apache/couchdb/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.1.0

CouchDB 2.1.0 has been released on Aug 4.
https://github.com/apache/couchdb/releases/tag/2.1.0

Can anybody confirm this issue is resolved? I am just setting up the backend for a new project and will start with 1.6.1 if 2.1.0 is still having issues. Thank you!

And CouchDB 2.1.1 is just around the corner<EMAIL_ADDRESS>

Has there been any update on this?

I can take a look at this.

Hi all,
sorry I've been busy on other projects. I got this as a response from couchdb

The fix version in JIRA is listed as 2.1.0. I guess we forgot to put it into the release notes at the time.
---

https://github.com/apache/couchdb/issues/2304#event-2796350133

I'll try to make time and officially test this some time soon.


cannot activate chinese input method in 'helloworld' inputbox

Describe the bug
To Reproduce
cd test
./helloworld
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

LCUI version: [6656f40a26d35283b4936203409f3b6119ec4c0b]
Build tools: [gcc]
OS and version: [Archlinux fcitx input method]

Additional context

This is a known issue.


Changed age_split, age_replace, age_sin from STABLE TO IMMUTABLE

Changed the 3 functions mentioned above to IMMUTABLE, as we are scanning the database to get the parameter of the functions but the functions themselves don't know that

Please give a more clear and complete explanation why this is needed for these functions.

Please give a more clear and complete explanation why this is needed for these functions.

Changed the comment. Could you tell me if this is sufficient.

Please fix your commit log entry for the PR to be descriptive of the change - what was changed and why. Once this is corrected, let us know so that we can review the PR for merging.

Please fix your commit log entry for the PR to be descriptive of the change - what was changed and why. Once this is corrected, let us know so that we can review the PR for merging.

Done.


Support for new formats of content

import OpenAI from "openai";

const openai = new OpenAI();

async function main() {
  const response = await openai.chat.completions.create({
    model: "gpt-4o",
    messages: [
      {
        role: "user",
        content: [
          { type: "text", text: "What’s in this image?" },
          {
            type: "image_url",
            image_url: {
              "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg",
            },
          },
        ],
      },
    ],
  });
  console.log(response.choices[0]);
}
main();

openai supports passing images and text at the same time, but the token calculation rules for images depend on the image size and processing mode. So I think we need to artificially supplement the two parameters of the image size and processing mode to calculate the token of the image.

I guess you could add a lib that extracts the size from the images like https://www.npmjs.com/package/image-size
Should be pretty easy to fetch an image or create a buffer from base64 to pipe that into image-size. But  currently this won't work in cloudflare workers: https://github.com/image-size/image-size/issues/405
I'm not quite sure if you can guess what detail level is chosen when you do not send it (when it's in auto mode), but from the documentation I would guess if it's smaller than 512px in both directions it will be low otherwise high.
Funny there are two description of costs in the official docs. The one that you posted and this: https://platform.openai.com/docs/guides/vision/low-or-high-fidelity-image-understanding
In this section they say the costs are 65 tokens per crop:

low will enable the "low res" mode. The model will receive a low-res 512px x 512px version of the image, and represent the image with a budget of 65 tokens. This allows the API to return faster responses and consume fewer input tokens for use cases that do not require high detail.
high will enable "high res" mode, which first allows the model to see the low res image and then creates detailed crops of input images as 512px squares based on the input image size. Each of the detailed crops uses twice the token budget (65 tokens) for a total of 129 tokens.

I'm not quite sure why two time 65 should be 129 but hey 🤷♂😁

function calculateHighDetailTokens(width: number, height: number): number {
  // First, check if the image needs to be scaled to fit within the 2048 x 2048 size limit
  if (width > 2048 || height > 2048) {
    const aspectRatio = width / height;
    if (width > height) {
      width = 2048;
      height = Math.round(2048 / aspectRatio);
    } else {
      height = 2048;
      width = Math.round(2048 * aspectRatio);
    }
  }

  // Next, scale the image so that the shortest side is 768px
  const minSideLength = 768;
  const currentMinSide = Math.min(width, height);
  if (currentMinSide > minSideLength) {
    const scaleFactor = minSideLength / currentMinSide;
    width = Math.round(width * scaleFactor);
    height = Math.round(height * scaleFactor);
  }

  // Calculate how many 512px tiles the image is composed of
  const tilesWide = Math.ceil(width / 512);
  const tilesHigh = Math.ceil(height / 512);
  const totalTiles = tilesWide * tilesHigh;

  // The token cost for each tile is 170, with an additional 85 tokens added at the end
  const totalTokens = totalTiles * 170 + 85;

  return totalTokens;
}

// Example usage
console.log(calculateHighDetailTokens(1024, 1024)); // Should output 765
console.log(calculateHighDetailTokens(2048, 4096)); // Should output 1105

In our project, we actually only use high mode, and the front-end knows the image width and height when uploading images. So I asked gpt to write a code to calculate the code in high mode. This temporarily solves the problem of image message token calculation.😂


xcode_proj handling of bazel artifacts

I've noticed a the xcode_project rule is pointing at bazel-out for a few artifacts. For example HEADER_SEARCH_PATHS. This might cause some issues in the case where the files don't exist: cleaning in Xcode, opening Xcode prior to building. Additionally it will cause issues if those files are outputs of a simulator build and the user is never using a simulator. In that case, the indexer and autocomplete will not work.
For what it's worth, XCHammer does a few things to get around this - manage generated files relevant to indexing and building on it's own and in some cases building them up front.

This commit shows an example of how the bazel configuration output dir hash is factored in to some project settings:
https://github.com/bazel-ios/rules_ios/pull/188/commits/02f3c362eaf34623923e51393557c39790903202

This commit shows an example of how the bazel configuration output dir hash is factored in to some project settings:
https://github.com/bazel-ios/rules_ios/pull/188/commits/02f3c362eaf34623923e51393557c39790903202

This commit shows an example of how the bazel configuration output dir hash is factored in to some project settings:
https://github.com/bazel-ios/rules_ios/pull/188/commits/02f3c362eaf34623923e51393557c39790903202

This commit shows an example of how the bazel configuration output dir hash is factored in to some project settings:
https://github.com/bazel-ios/rules_ios/pull/188/commits/02f3c362eaf34623923e51393557c39790903202

Thanks for identifying this problem! Just to confirm it is the method _header_search_paths_for_target in question right?
What you said is consistent with the observation that indexing won't work unless certain targets are built. Am I correct on this?

Thanks for identifying this problem! Just to confirm it is the method _header_search_paths_for_target in question right?
What you said is consistent with the observation that indexing won't work unless certain targets are built. Am I correct on this?

@jerrymarino mind sharing one example from XCHammer code where this kind of handling is happening? Experiencing an issue now where "jump to definition" takes me to the file in the bazel-out folder instead of the one inside the project generated by the xcodeproj rule.

I've noticed a the xcode_project rule is pointing at bazel-out for a few artifacts

Would appreciate if you could share exactly how you concluded this, what file did you inspect/command did you run?

@gyfelton yeah one of the issues is that the header search paths are pointing at simulator intermediates so if you were just doing device builds those intermediates wouldn't exist.
@thiagohmcruz XCHammer today works similar to how cocoapods generator does: it puts all the targets into Xcode project with equivalent bazel build settings. Because of this, the features in the UI generally work as they did with cocoapods. The main caveat is that if you flip the bit to build with Bazel it calls Tulsi's infrastructure to run bazel.
To achieve this there are tens of rule attributes and features. Today, rules_ios handles files, framework search paths, and header search paths.
If we wanted to try XCHammer's approach, we could try to leverage the xcode_project rule similar to how ios_application call's rules_ios ios_application  and pass any rules_ios specific flags. As rules_ios uses xcodegen as well, I suspect it should mesh w/o significant changes
# xcodeproj.bzl

load("@xchammer//:xcodeproject.bzl", xcodegen_bazel_xcodeproj="xcode_project")
def xcodegen_bazel_xcodeproj(kwargs):
  xcode_project(
       name = ...,
       targets = ...
       paths = [ "**" ],
  )

@amberdixon ^ I believe this was an explicit decision in the way that Amber set up the project generator.

Yes, the expected behavior is that if you have performed a build locally, the header search paths and framework search paths should point to the files generated by the build under the bazel-out directory.
IIRC regular xcodeprojects generated by cocoapods behave in a similar way. If you haven't build a target, then the files for that target will not always index successfully and so autocomplete operations will initially not work.

For what it's worth, XCHammer does a few things to get around this - manage generated files relevant to indexing and building on it's own and in some cases building them up front.

We can certainly make change to kick off some background build jobs.
There is a separate (but similar) problem that Jerry mentioned above where the device and simulator builds generate headers and framework search paths with different configurations, and the HEADER_SEARCH_PATHS/FRAMEWORK_SEARCH_PATHS build setting only points to one of those configurations. Therefore, if you build for device, but then point Xcode to build for simulator, autocomplete might fail for source files. There is probably a simple fix here, which is to load both sets of header and framework search paths into the project.

Ah makes sense to me. Yeah theres' a few manifestations of this implementation - the one that really sticks out is indexing and code complete issues when doing device builds


ENHANCEMENT: Support or switch to SWC

SWC might dramatically speed up build times.

SWC is 20x faster than Babel on a single thread and 70x faster on four cores.

Does anybody want to try a PR  that swaps Babel for SWC?

See #29.

Closing as the details are in #29.


Update to Nativescript 6

Environment
{
  "name": "test",
  "nativescript": {
    "id": "org.nativescript.test"
  },
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e",
    "android": "tns run android --bundle",
    "ios": "tns run ios --bundle",
    "mobile": "tns run --bundle",
    "preview": "tns preview --bundle"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~7.2.0",
    "@angular/common": "~7.2.0",
    "@angular/compiler": "~7.2.0",
    "@angular/core": "~7.2.0",
    "@angular/forms": "~7.2.0",
    "@angular/http": "~7.2.0",
    "@angular/platform-browser": "~7.2.0",
    "@angular/platform-browser-dynamic": "~7.2.0",
    "@angular/router": "~7.2.0",
    "core-js": "^2.5.4",
    "nativescript-angular": "~7.2.0",
    "nativescript-theme-core": "~1.0.4",
    "reflect-metadata": "~0.1.12",
    "rxjs": "~6.3.3",
    "tns-core-modules": "~5.2.0",
    "zone.js": "^0.8.26"
  },
  "devDependencies": {
    "@angular/cli": "^7.2.0",
    "@angular/compiler-cli": "~7.2.0",
    "@angular-devkit/build-angular": "~0.11.4",
    "@nativescript/schematics": "~0.4.0",
    "@types/jasmine": "2.8.6",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "~8.9.4",
    "codelyzer": "~4.2.1",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~2.0.0",
    "karma-jasmine": "~1.1.1",
    "karma-jasmine-html-reporter": "^0.2.2",
    "nativescript-dev-typescript": "~0.8.0",
    "nativescript-dev-webpack": "^0.20.0",
    "protractor": "~5.3.0",
    "ts-node": "~5.0.1",
    "tslint": "~5.9.1",
    "typescript": "~3.1.1",
    "nativescript-dev-sass": "~1.6.0"
  }
}

Describe the bug
Using globally installed<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I try to run:
tns run android --bundle
and I get:
$ tns run android --bundle
The current application is not compatible with NativeScript CLI 6.0.
Use the `tns migrate` command to migrate the app dependencies to a form compatible with NativeScript 6.0.
Running this command will not affect the codebase of the application and you might need to do additional changes manually – for more information, refer to the instructions in the following blog post: https://www.nativescript.org/blog/nativescript-6.0-application-migration
error Command failed with exit code 127.

I suppose this project needs an update for just released stable NativeScript 6.

Adding to @guix77 , could the NS Team please look into this issue. I've upgrade to Angular 8 to be compatible with NativeScript CLI 6.0 but stuck with the schematics pointing to Angular 7.x and unable to make an Android build.
Appreciate your help. Thanks.

Same here

I'm totally stuck as well... I'm using Sidekick, which now insists on working with latest nativescript. Hope some migration will come...

Hey everyone! The team is actively working on updating the package.

Thanks, very nice to hear that! @sis0k0 if I'm not too pushy, is there any forecast about when to expect the update?

fixed with v0.7.0


Fix docopt_macros for rustc-1.23.0-nightly

Fixed for rustc 1.23.0-nightly (aabfed5e0 2017-11-17)

Thanks!

When do you think you'll be cutting the next release?   I'd like to play with this in another project?  Thanks again, this is great!


Temporary work around for https://github.com/wrengr/unification-fd/issues/70

unification-fd currently doesn't work on nixpkgs-unstable

This change should be safe, but please make sure the Haskell simplicity project still builds on your stable channels for nixpkgs.


Set the compress flag for the responses from external DNS servers

Fixes [docker/docker #20132] (https://github.com/docker/docker/issues/20132)
Signed-off-by: Santhosh Manohar<EMAIL_ADDRESS>

LGTM.


Fix excessive reconnection attempts after Contract runtime finalization

Pre-review checklist

[x] All code has been formatted using our config (make format)
[x] Any new API features or modification of existing behavior is covered as defined in our test plan
[x] The changelog has been updated under the ## Unreleased header, using the appropriate sub-headings (### Added, ### Removed, ### Fixed), and the links to the appropriate issues/PRs have been included

The motivation was to prevent websockets reconnect attempts after the end of contract execution.

Why do we even reconnect on error on the PS side, isn't that the whole purpose for using reconnecting-websockets?

@jy14898 reconnecting-websockets can only reconnect, it does not replay the unfinished requests (because it can't know which requests have received a response and which haven't).

Resubmission is handled by the onConnect handler though, which gets invoked whether we call reconnect or not, because the ws is reconnecting
https://github.com/Plutonomicon/cardano-transaction-lib/blob/014e2b0119a16bd5ca936ac28d26ffeea8e9db35/src/Internal/QueryM.purs#L828-L833

@jy14898 if you want to re-check this could you please try the following:

remove the manual reconnect
start some long-running Contract (e.g. AlwaysSucceeds example)
stop the runtime
see the connection errors
start the runtime again
the contract should end successfully

I think it is not going to work, but I don't remember the exact reason.

@jy14898 if you want to re-check this could you please try the following:
1. remove the manual reconnect
2. start some long-running Contract (e.g. AlwaysSucceeds example)
3. stop the runtime
4. see the connection errors
5. start the runtime again
6. the contract should end successfully

I think it is not going to work, but I don't remember the exact reason.

I just tried it and it works fine, the contract completed successfully:


fix incorrect test data

The length field of the payload for the Run test wasn't accurate (it was 0x74, the data provided was 0x7A).  Since the test previously wasn't sending any subsequent messages, it went unnoticed that it left unread bytes on the pipe that the next read would pick up thinking it was reading the next header when it wasn't.  In addition, the data itself needs to conform to XDR's 4 byte block size.
Adding the Connect/Disconnect calls to the mock libvirt is just a way to trigger the code to encounter the unexpected extra bytes on the pipe.

Force merging because the zombie Travis CI is still lurking.


pipeline links changed

Continuation of https://github.com/iterative/dvc.org/pull/1383#issuecomment-648363086

One of the Next Priorities in DVC 1.x discrepancies #1255:

[x] dvc pipeline -> dvc dag #1383 Need to update pipeline links, for now they just redirect to dag. Also push/pull examples.

Line 169 in repro.md links to /doc/tutorial/dags and previously linked to /doc/tutorial/pipelines. Both these links just redirect to doc/start. Maybe they should have a different link (/doc/start/data-pipelines)?

One of the Next Priorities in DVC 1.x discrepancies. #1255

Which one? Please copy the checkbox over...

Continuation of Merged PR #1383

Continuation why? Is there a pending review there? Please provide exact context.

Also, regarding the sub-point in #1255 Next Priorities:

Also push/pull examples.

There was a certain bug in one of the examples (private remote) in dvc pull as I had mentioned on Discord.
Message link.
Once that example is resolved, I might be in a better position to work on that.
I hope I can commit those changes in a separate PR?

There was a certain bug in one of the examples (private remote) in dvc pull as I had mentioned on DiscordI cann't open your message link. Have you opened an issue for the bug?

There was a certain bug in one of the examples (private remote) in dvc pull as I had mentioned on Discord

I can't open that link. Please open a proper bug report in this repo.

But really... It's probably normal. push and pull haven't been updated yet to 1.x  Why does that stop us from updating the dvc pipeline examples on those pages? Just change "dvc pipeline" for "dvc dag" even if the output isn't 100% correct for now.

In fact please find any examples using "dvc pipeline" and update them to "dvc dag" as best as you can @utkarshsingh99. Thanks

Just change "dvc pipeline" for "dvc dag" even if the output isn't 100% correct for now.

Alright. I've done that, and also tried improving the outputs. I guess some of the comments in my review above might be a little out of scope for this PR but it would help for future PRs.

please find any examples using "dvc pipeline" and update them to "dvc dag"

Done. Interestingly, didn't find any more of such examples. Although there were some more /pipeline links outside of the cmd-ref directory. They have been changed. Such links are also present in the blogs.

A problem in pull.md if I simply list stage names in one line:

With the first dvc pull we specified a stage in the middle of this pipeline (featurize.dvc) while using --with-deps

I have listed the stage names just as a one-line list without the code block, instead of bulleted points. This might not exactly define an 'order' to say that featurize is in the middle of the pipeline in pull.md. The same problem arises for push.md.

Update with latest commit:  Keeping in mind #1584(comment), I made this decision to add blockquotes while listing. Hope this is better for the user's understanding.

The dvc status command doesn't need change

Yeah, why status? It doesn't mention dag.

updated all examples

Just in push and pull, as described in this PR's description/scope.

Merging even with this strange CI checks error:

From https://app.circleci.com/pipelines/github/iterative/dvc.org/4859/workflows/ae8a7d2c-2aa4-4d53-bafc-3c9246ebd621/jobs/4913

https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations-ebook/dp/B01M9ASFQ3 is nowhere in these changes.


IPC cannot compile on Windows

Describe the bug
The IPC crate depends on UnixStream which is not available on Windows
https://github.com/paradigmxyz/reth/blob/352b55dc0593a2a88e14e7e894079160aeb74010/crates/rpc/ipc/src/client.rs#L13
On Windows we should use named pipes instead (https://docs.rs/tokio/latest/tokio/net/windows/named_pipe/index.html)
Steps to reproduce
Try cross compiling using cargo install cross:
cross build --target x86_64-pc-windows-gnu
Notice that the IPC and mdbx crates will not compile (separate issue)
Node logs
No response
Platform(s)
Windows (x86)
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

@mattsse didn't we solve this on ethers-rs?

I checked and this only affects the client implementation which we only use for testing, ignored this in #2785 until have a windows specific impl for this #2786


Allows contexts to escape to parent via return

When a context returns another context, that context is kept alive. Meaning that unlike other children, it won't be halted when the context exits, it is then linked to the parent. This provides a desired escape hatch to allowing contexts escape the scope in which they were created.
Initially we used the suspend pattern for this purpose, but as documented in #86, this pattern does not compose well, and its behaviour is confusing at times.
In the future, we might extend this functionality with what we have dubbed resources, where a resource basically bundles some JavaScript object, and an associated context. This PR does not implement such a feature yet.
This PR also makes a few other changes which were necessary or convenient for implementing this feature:

execution contexts now track whether they are required. This simplifies things, since we want to preserve whether they are required when they are returned

execution contexts are not initialized with a parent, but rather they can be linked to another context through link and unlink. This allows for more flexibility

linked children always propagate errors to their parents. Instead of this being part of the functionality of spawn and fork. This does require some trickery to make generator work, but I think it is worth it.

monitor has been renamed to spawn (an alias is retained for now), because it does not add any functionality on top of context.spawn.

It is currently no longer supported to use a fork or spawn as the top level operation. Because it hurts my brain and I can't figure out what sensible behaviour actually should be.

Closing this in favour of #89, since I did a ton of additional work which also fixed a lot of bugs in this PR.


Cellscope to support multi-sample data sets

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-521
Link to staging deployment URL
https://ui-rbbtb4equafqp88h43eyfr7o8h.scp-staging.biomage.net/
Links to any Pull Requests related to this
https://github.com/biomage-ltd/pipeline/pull/19
Anything else the reviewers should know about the changes here
N/A
Changes
Code changes
Added some logic to handle multisample data sets, including properly replacing processing config changes and creating full configs per sample.
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[x] Unit tests written
[x] Tested locally with Inframock
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[x] Relevant Github READMEs updated
[x] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

Would it make sense to handle enabled/disabled on the api side? By perhaps generating the skeleton for the steps according to the enabled/disabled steps?

Yes, it probably would actually, especially given right now those filters take forever to run even if they are empty.

It seems there is a bug, the API does not update with completed tasks.

@cosa65 -- Disabled states no longer get executed.


engine hive: Invalid Ancestor Chain Sync

Describe the bug
In these tests, messages are sent as follows:

build a small valid chain on a modified geth client
produce an invalid block, let's call this block A, apply it to the modified geth client
produce block B on top of A:

newPayload call to reth with attributes for B
forkchoiceUpdated with B's block hash

On main, this fails because the download target is not set properly, see #2802
With the fix applied, we fail because of two reasons:

We do not track invalid blocks when we run the pipeline for sync
Many fatal errors should be converted to Unwinds, and the Unwind should contain enough information to mark bad blocks as invalid

On the forkchoiceUpdated we should sync to the proper forkchoice head ancestor using the pipeline, and if any blocks cause an unwind, those blocks and all parents should be market as invalid.
Steps to reproduce
./hive --client reth --sim "ethereum/engine" --sim.limit "engine-api/Invalid Ancestor Chain Sync, Invalid Receipt"

Node logs
No response
Platform(s)
No response
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

I'd like to try to fix this one if you have not started @Rjected

I'd like to try to fix this one if you have not started @Rjected

@int88 whoops these ones are already done! closing this

If I'm not wrong, the test still failed with the latest code:
[1f1981f3] << (08f04fb5) {"jsonrpc":"2.0","result":{"status":"VALID","latestValidHash":"0x75dc605ab43636a7e4b9c399fcf755cef08411cd62c82f461c027180db68a640","validationError":null},"id":12}
[1f1981f3] >> (08f04fb5) {"jsonrpc":"2.0","id":13,"method":"engine_newPayloadV1","params":[{"parentHash":"0x75dc605ab43636a7e4b9c399fcf755cef08411cd62c82f461c027180db68a640","feeRecipient":"0x0000000000000000000000000000000000000000","stateRoot":"0x84308e7d0abf860412f4a0c6fc25709a6e9eaba20a0d085a0344d271f40109ec","receiptsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","prevRandao":"0xd113fa6a778699f0052b5409bfc3dc2e1a4729020da25a275652a5a265b7cdfe","blockNumber":"0x5","gasLimit":"0x302bd8","gasUsed":"0x0","timestamp":"0x1239","extraData":"0xd883010b04846765746888676f312e32302e35856c696e7578","baseFeePerGas":"0x1e925e88","blockHash":"0x25e54190acb121a04ffd211d82666bc9ca26756556cb0da464478675a0f27151","transactions":[]}]}
[1f1981f3] << (08f04fb5) {"jsonrpc":"2.0","result":{"status":"VALID","latestValidHash":"0x25e54190acb121a04ffd211d82666bc9ca26756556cb0da464478675a0f27151","validationError":null},"id":13}
[1f1981f3] >> (08f04fb5) {"jsonrpc":"2.0","id":14,"method":"engine_newPayloadV1","params":[{"parentHash":"0x25e54190acb121a04ffd211d82666bc9ca26756556cb0da464478675a0f27151","feeRecipient":"0x0000000000000000000000000000000000000000","stateRoot":"0x3ba609decd2294721fb2b6c2f897ae5ad229d02ab78b06821fe565192778285f","receiptsRoot":"0x4e3c608a9f2e129fccb91a1dae7472e78013b8e654bccc8d224ce3d63ae17006","logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","prevRandao":"0x8b070bff9489dbf3c822f6c0df4fd35b25d579556ee843e794cda3804a37ffb5","blockNumber":"0x6","gasLimit":"0x3037e1","gasUsed":"0xa860","timestamp":"0x123a","extraData":"0xd883010b04846765746888676f312e32302e35856c696e7578","baseFeePerGas":"0x1ac012b7","blockHash":"0x2339647e21ab4971f033906896e4aceb5c49c4944c3c3abd697c59cf58860681","transactions":["0xf865808506fc23ac00830124f8940000000000000000000000000000000000000316018032a044b25a8b9b247d01586b3d59c71728ff49c9b84928d9e7fa3377ead3b5570b5da03ceac696601ff7ee6f5fe8864e2998db9babdf5eeba1a0cd5b4d44b3fcbd181b"]}]}
[1f1981f3] << (08f04fb5) {"jsonrpc":"2.0","result":{"status":"ACCEPTED","latestValidHash":null,"validationError":null},"id":14}
[1f1981f3] DEBUG (Invalid Ancestor Chain Sync, Invalid ReceiptsRoot, Invalid P8'): Failed `Expect*` routine called from: file=/source/suites/engine/tests.go, line=2477
[1f1981f3] FAIL (Invalid Ancestor Chain Sync, Invalid ReceiptsRoot, Invalid P8'): Unexpected status response on EngineNewPayloadV1: ACCEPTED, expected=VALID, payload={
[1f1981f3]  "parentHash": "0x25e54190acb121a04ffd211d82666bc9ca26756556cb0da464478675a0f27151",
[1f1981f3]  "feeRecipient": "0x0000000000000000000000000000000000000000",
[1f1981f3]  "stateRoot": "0x3ba609decd2294721fb2b6c2f897ae5ad229d02ab78b06821fe565192778285f",
[1f1981f3]  "receiptsRoot": "0x4e3c608a9f2e129fccb91a1dae7472e78013b8e654bccc8d224ce3d63ae17006",
[1f1981f3]  "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
[1f1981f3]  "prevRandao": "0x8b070bff9489dbf3c822f6c0df4fd35b25d579556ee843e794cda3804a37ffb5",
[1f1981f3]  "blockNumber": "0x6",
[1f1981f3]  "gasLimit": "0x3037e1",
[1f1981f3]  "gasUsed": "0xa860",
[1f1981f3]  "timestamp": "0x123a",
[1f1981f3]  "extraData": "0xd883010b04846765746888676f312e32302e35856c696e7578",
[1f1981f3]  "baseFeePerGas": "0x1ac012b7",
[1f1981f3]  "blockHash": "0x2339647e21ab4971f033906896e4aceb5c49c4944c3c3abd697c59cf58860681",
[1f1981f3]  "transactions": [
[1f1981f3]   "0xf865808506fc23ac00830124f8940000000000000000000000000000000000000316018032a044b25a8b9b247d01586b3d59c71728ff49c9b84928d9e7fa3377ead3b5570b5da03ceac696601ff7ee6f5fe8864e2998db9babdf5eeba1a0cd5b4d44b3fcbd181b"
[1f1981f3]  ],
[1f1981f3]  "withdrawals": null
[1f1981f3] }
[1f1981f3] CLMocker: Closing engine client Modified Geth Module

@Rjected

If I'm not wrong, the test still failed with the latest code:

You're right, forgot about this! I think this needs sidechain state root validation in order to return VALID instead of ACCEPTED here. VALID should only be returned if the block is fully validated, including the state root, but we don't have sidechain root validation, so newPayload calls like this can't be fully validated. Going to re-open until we fully pass this but I don't think it will be easy to solve
see https://github.com/paradigmxyz/reth/pull/3074 for progress on sidechain root validation - I think the test passes on that branch. That PR though uses unwind and commit to allow reth to validate roots, which could lead to consistency issues in case the node crashes, so we may need to explore other approaches.

I'm going to close this now - we should track individual failing tests and identify which ones require sidechain state root validation instead. #3074 has been closed, and calculating sidechain state roots requires a better design.
Here is where we should be tracking these failing tests: https://github.com/paradigmxyz/reth/issues/2625


BIGTOP-3948. Fix build failure of Tez due to expired certificate of bower repo.

https://issues.apache.org/jira/browse/BIGTOP-3948
We need to cherry-pick the patch of TEZ-4492 since Tez 0.10.3 is not yet released.

LGTM, +1

Thanks, @guyuqi. I cherry-picked this to branch-3.2.


Provide a list of all engine services

So the devs know which ones to provide implementation for if needed. Each service should be added to this issue, so that it can later be added to the wiki. Each service needs a brief explanation regarding what the service does.
Copy-pasted from Settings.kt: (probably not up to date)
        var engineServices: MutableList<Class<out EngineService>> = arrayListOf(
                // this is the order in which services will be initialized
                // by design, the order of services should not matter
                FXGLApplication.GameApplicationService::class.java,
                FXGLDialogService::class.java,
                IOTaskExecutorService::class.java,
                EventBusService::class.java,
                FileSystemService::class.java,
                LocalizationService::class.java,
                FXGLAssetLoaderService::class.java,
                SystemBundleService::class.java,
                SaveLoadService::class.java,
                FXGLUIFactoryServiceProvider::class.java,
                FXGLDialogFactoryServiceProvider::class.java,
                AudioPlayer::class.java,
                NotificationServiceProvider::class.java,
                AchievementService::class.java,
                CutsceneService::class.java,
                MiniGameService::class.java,
                NetService::class.java,
                UpdaterService::class.java,
                DevService::class.java
        ),

In addition to above, any subtype of EngineService should also be added here.

FXGLAssetLoaderService
Handles all resource (asset) loading operations.

The "assets" directory must be located in "src/main/resources/" (using the Maven directory structure).
Alternatively, (not recommended) source folder ("src" by default).
Resources (assets) will be searched for in these specified directories:

Texture / images - /assets/textures/
Sound - /assets/sounds/
Music - /assets/music/
Text (List of String) - /assets/text/
FXML - /assets/ui/
CSS - /assets/ui/css/
Font - /assets/ui/fonts/
Cursors - /assets/ui/cursors/
Resource bundles - /assets/properties/

If you need to access the "raw" JavaFX objects (e.g. Image), you can use [getStream]
to obtain an InputStream and then parse into whatever resource you need.

FXGLApplication.GameApplicationService

Is a high level [blank]

FXGLDialogService

A Dialog Service allows you to display text to the screen.
IOTaskExecutorService

The IOTaskExecutorService allows you run tasks synchronously and asyncronously.

FileSystemService

The File System Service is a standard IO Wrapper that allows you to read, write and check the existence of directories and files.

LocalizationService

Services that provides functions to localize Strings to the given Language using String or StringBinding.
Also supports lazy loading of language data.
SystemBundleService

It saves FXGL system data into a file.
SaveLoadService

Responsible for save/load operations to/from data files.
Also responsible for write/read IO operations of save files.
FXGLUIFactoryServiceProvider

FXGL provider of UI factory service.
FXGLDialogFactoryServiceProvider

Generates User Interface for Dialog Boxes
AudioPlayer

General audio player service that supports playback of sound and music objects.  It can also control volume of both.
NotificationServiceProvider

Shows Notifications to the Player
AchievementService

Responsible for registering and updating achievements.
Achievements can only be registered via Settings, before the engine starts.
CutsceneService

Manages and plays cutscenes
MiniGameService

Manages and plays minigames
NetService

All operations that can be performed via networking.
UpdaterService

Checks if there is a newer version of FXGL than the one being used.
DevService

Provides developer options when the application is in DEVELOPER or DEBUG modes.
In RELEASE mode all public functions are NO-OP and return immediately.

Pushed to https://github.com/AlmasB/FXGL/wiki/Engine-Services-(FXGL-11)


Heuristics dosn't create a 3D space view in a simple case

Consider this code:
import rerun as rr

rr.init("rerun_example_bug")
rr.connect()
rr.set_time_sequence("frame_nr", 0)

rr.log("boxes3d", rr.Boxes3D(centers=[[0, 0, 0], [1, 1.5, 1.15], [3, 2, 1]], half_sizes=[0.5, 1, 0.5] * 3))
rr.log("boxes2d", rr.Boxes2D(centers=[[0, 0], [1.3, 0.5], [3, 2]], half_sizes=[0.5, 1] * 3))

Expected: bot a 2D and 3D space view are created
Actual: only a 2D space view is created

May or may not be related to this user report https://discord.com/channels/1062300748202921994/1075873257124810852/1214908729321988166 on pinhole not getting a 3d scene for
import numpy as np
import rerun as rr

rr.init("rerun_example_pinhole", spawn=True)
rng = np.random.default_rng(12345)

image = rng.uniform(0, 255, size=[3, 3, 3])
rr.log("world/image", rr.Pinhole(focal_length=3, width=3, height=3))
rr.log("world/image", rr.Image(image))```

Full code:
import rerun as rr

rr.init("rerun_example_bug")
rr.connect()
rr.set_time_sequence("frame_nr", 0)

rr.log("boxes3d", rr.Boxes3D(centers=[[0, 0, 0], [1, 1.5, 1.15], [3, 2, 1]], half_sizes=[0.5, 1, 0.5] * 3))
rr.log("boxes2d", rr.Boxes2D(centers=[[0, 0], [1.3, 0.5], [3, 2]], half_sizes=[0.5, 1] * 3))
rr.log("text_logs", rr.TextLog("Hello, world!", level=rr.TextLogLevel.INFO))
rr.log("points2d", rr.Points2D([[0, 0], [1, 1], [3, 2]], labels=["a", "b", "c"]))

Various combination of enabled/disabling each of these log lines yield various heuristics results, many of which are currently wrong.


Menu has artefacts on window with surface view on HTC Sense 2.3

Hi.
On Android 2.3 on HTC Sence device the menu draws incorrectly. When you open the menu a part of it remains black. It seems like a surface "hole" not moved when you just call offsetLeftAndRight(). requestLayout() call fixes the problem.

:) Awwww shucks! It is kind of janky, but hope it solves your immediate problem. Seems to work fine in the places I implemented it.


Updating to rc3

@fnicollet - I am not a git expert but do use and understand some of it. I am struggling to build the rotation code with the latest master - when I run it on my rc3 working code I am getting errors so I must be doing something wrong. I am cloning to local, then merge master to the lastest commit - which has a conflict with src\map\Map.js - I resolve this with the editor and commit. This gives me a working latest system which when loaded into my pages loads perfectly and works as expected. When I switch to the rotate-master branch and build it builds OK. I then try to load this and get a parser error:
"parsererror" Error: Couldn't autodetect L.Icon.Default.imagePath, set it manually.(…)
If I stop loading this via and AJAX call and just use

Hello,
I was waiting for Leaflet to release a 1.0 (they are close to it
apparently) to make a merge with master. I'll try it out tonight to merge
with current master in the meantime. I am not a git expert myself either :)
Fabien
On Thu, Sep 15, 2016 at 3:37 AM, David Martin<EMAIL_ADDRESS>wrote:

@fnicollet https://github.com/fnicollet - I am not a git expert but do
use and understand some of it. I am struggling to build the rotation code
with the latest master - when I run it on my rc3 working code I am getting
errors so I must be doing something wrong. I am cloning to local, then
merge master to the lastest commit - which has a conflict with
src\map\Map.js - I resolve this with the editor and commit. This gives me a
working latest system which when loaded into my pages loads perfectly and
works as expected. When I switch to the rotate-master branch and build it
builds OK. I then try to load this and get a parser error:
"parsererror" Error: Couldn't autodetect L.Icon.Default.imagePath, set it
manually.(…)
If I stop loading this via and AJAX call and just use
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fnicollet/Leaflet/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLtoYvMvsRfCqWaq5UA4Zh4MGMtBEMAks5qqKFngaJpZM4J9axK
.

--
Fabien Nicollet
Tel : +33 (0)6 60 54 72 20

Fabien, I am running it OK with rc3 but the parseerror is just a strange one!. Yeah I am waiting for 1.0 also but doing some limited releases of rc3 cause it is great and much faster IMHO.  Thanks for you work on this rotate feature.

Just merged to current master (so RC3)


Stop desktop app from appearing in the macOS dock

Current
We're building a Desktop System Tray app for Ockam using Tauri, see https://github.com/build-trust/ockam/issues/5228
When we start the app in macOS it shows up in the macOS menu on he top right, this is expected:

But is also shows up in the macOS dock, this is not desired.

Desired
Should only show up in the menu.
Steps to reproduce
You can run the app as follows:
cd implementations/typescript
pnpm install
pnpm build

cd ../../implementations/rust/ockam/ockam_app
cargo tauri dev

Source Code
The code for this is here:

https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_app
https://github.com/build-trust/ockam/blob/develop/implementations/typescript/ockam/ockam_app

We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion or join us on discord. If you're looking for other issues to contribute to, checkout labels -  https://github.com/build-trust/ockam/labels/good first issue or https://github.com/build-trust/ockam/labels/help wanted

Here's an example app that doesn't show up in the dock
https://github.com/jondot/tauri-tray-app

This is likely the fix:
#[cfg(target_os = "macos")]
app.set_activation_policy(tauri::ActivationPolicy::Accessory);

We likely have to add to it to app setup here:
https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_app/src/lib.rs#L29


[Feature request]: eufy Security SoloCam S340 (T8170)

Describe the solution you'd like
Please add support for eufy Security SoloCam S340 (T8170)

So was https://github.com/bropat/eufy-security-client/issues/383 not implemented?


RFC: Add -j option to lake build to control number of threads

Proposal
Add a -j option to lake build to only spawn N compilation threads, similar to tools like make or cargo build.
If this is difficult to implement, it might be good enough to just print something akin to "Run LEAN_NUM_THREADS=8 lake build instead" and exit.
Motivation: compiling mathlib pegs all my CPU cores to 100% and takes a long time, making other tasks on my computer lag.
Community Feedback
Discussion on Zulip showed others ran into this as well, and the solution to use LEAN_NUM_THREADS=8 lake build is unstable and has low discoverability.
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Another use case: benchmarks, which may be more consistent when run single-threaded.

Would be nice if any of these options would be documented, at all.


Add vim itself to globals for stable

It looks like this was added for nightly some time ago, but got missed for stable.

Hmm, I was hoping that would solve the problem of vim showing up as an undefined global but that doesn't seem to do anything (and I have the same problem on nightly anyway...). So feel free to close this if it's pointless.

I've run into a similar problem. See https://github.com/folke/neodev.nvim/discussions/115