Update server implemetation of refrigerator cluster to sync spec

Problem

Spec was being updated

Changes

Handelling of supported attribute.

Testing

Tested commissioning and cluster control

@bzbarsky-apple spec didn't defined default value of supported attribute for refrigerator alarm as did for mask. What should we set?

spec didn't defined default value of supported attribute for refrigerator alarm as did for mask. What should we set?

That's a question for @marktrayer, I think...

spec didn't defined default value of supported attribute for refrigerator alarm as did for mask. What should we set?

That's a question for @marktrayer, I think...

The spec states:
| 0x0003  s| Supported | AlarmMap   | all            | F       | 0       | R   V    | M
Or am I missing something?

That "default" value has nothing to do with what devices are expected to implement.
Is it valid to have a refrigerator alarm cluster that has the door alarm bit set to false in Supported?

That "default" value has nothing to do with what devices are expected to implement.
Is it valid to have a refrigerator alarm cluster that has the door alarm bit set to false in Supported?

I keep mixing up what default means (sorry!); the short answer is no.  Even if suppressed, it's always supported.

Is it valid to have a refrigerator alarm cluster that has the door alarm bit set to false in Supported?

If we do this we need to set door alarm bit of Mask to false too.


PoC for Log parsing with Otel Collector

Description
As a follow-up to #691, we want to evaluate an OpenTelemetry collector setup to read JSON structured container logs and convert them to OTLP logs. Fields like Timestamp, SeverityText, SeverityNumber, or Body should be detected in well-known log formats like Zap or Log4j. JSON fields that are not mappable to the OTLP log record fields, should be converted to OTLP attributes or resource attributes. The possibility to allow the user giving hits about the used log format should be evaluated. For instance, describing the log message field in a Kubernetes annotation. The feasibility to achieve this with the filelog receiver's operators and the attributes processor should be evaluated.
Acceptance Criteria

Fields of the OTLP Log and Event Record Definition are extracted from JSON logs
The actual log message is written to the Body field
Decide and implement how to map the body in case no message field can be identified
Other fields of the JSON record are written to the Attributes or Resource maps
Semantic conventions for Attributes and Resource Attributes are followed
Scenarios:

Have an unstructured log, see basic data in place like pod name, raw payload in body
Have structured log not matching any format, see basic data in place like pod name, log attributes are parsed, body contains X
Have structured log matching a format, see basic data in place like pod name, log attributes are parsed, body contains log message

The PoC has been conducted, results were documented by PR #762.


fix(types) export DataItem from LegendModel

Brief Information
This pull request is in the type of:

[x] bug fixing
[ ] new feature
[ ] others

What does this PR do?

This PR export the DataItem interface from LegendModel.ts. I guess it was an oversight.
Fixed issues
No issue opened
Details
Before: What was the problem?
Unable to fully use the type LegendOption
After: How is it fixed in this PR?
I can use DataItem to describe the legends
Misc

[ ] The API has been changed (apache/echarts-doc#xxx).
[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
NA.
Others
Merging options

[x] Please squash the commits into a single one when merge.

Other information

Closing this since no response from the maintainers in 1 year.


Setup Mac slave nodes for Jenkins

This is a bit more complicated.
I thinks it would require:
-- setup machines on-premise
-- setup cloud VPN to make them on the same local subnet as jenkins master
-- add them as slave nodes (fairly trivial - just needs sshd and java installed)

Actually, can't we just get OS X images for GCE somewhere? ;-)


feat: support Fedora

Ping @brianshumate I think you might have missed this because I submitted an identical one on ansible-vault the same day :smiley:

Thanks!


app.addRoutes error on v1.1.1

I just upgraded from 1.0.0-rc8 to 1.1.1 and I get an error when using app.router.addRoutes in a plugin:
import mycustompage from<EMAIL_ADDRESS>
export default async ({app}) => {
	app.router.addRoutes([
		{
			path: "/",
			name: "index",
			component: mycustompage
		}
	]);
};

Cannot read property 'layout' of undefined
.nuxt/server.js:123:
  // ...If there is a redirect or an error, stop the process
  if (ssrContext.redirected) return noopApp()
  if (ssrContext.nuxt.error) return renderErrorPage()

  /*
  ** Set layout
  */
  let layout = Components.length ? Components[0].options.layout : NuxtError.layout
  if (typeof layout === 'function') layout = layout(app.context)
  await _app.loadLayout(layout)
  layout = _app.setLayout(layout)

it seems options is missing from the Component.

This question is available on Nuxt.js community (#c2249)

I get the same error on version 1.3.0

I'm getting the same behavior, the way you phrase it make it looks like it's compiling the thing with some kind of incorrect Webpack configuration...

same here

Same here in 2.0

Please use extendRoutes to extend the vue router :ok_hand:
Because this bug report seems to be inactive for quite some time, I'll close it now. If you feel like it deserves some attention because it's not fixed, feel free to ping me and I'll reopen it.


Investigate crash of harmonic analysis

Start from harmonic example but use the model stored here: BUGS\PYDPF_COMPOSITES_ISSUE_307. Use the function composite_files_from_workbench_harmonic_analysis to get the input files => DPF crashes with a seg fault somewhere in mapdlCoreOperators.dll

This happens only in distrbuted mode. It looks like the distributed rst files (file0.rst, file1.rst) are not removed for a harmonic analysis, even if recombine to single rst file is activated. Probably we have to improved the logic when we try to indentify the rst files: If a file.rst is present we don't look for the files with a number suffix.

Update: The problem only arises if "Delete Unneeded Files" is set to "No" in "Analysis Data Management".


Remove libunwind dependency from Dockerfiles

The libunwind dependency has been removed from the PAL for quite some time at this point. This dependency can probably be removed.

Due to the version of the PAL used in Snapshot Debugger, libunwind is still required.


Substation maintenance

About the PR
Add a substation maintenance mechanic.  The more power the substation is delivering, the more oil it burns. If a substation is not maintained by periodic oil refilling, it will take damage until it fails and needs to be rebuilt.
This mechanic is designed to give mid-round engineers some work to do. Instead of setting up everything at round start and lounging for the rest of the shift, responsible engineers will need to visit each substation periodically and check up on their oil levels. This is also better than a random event, because this mechanic allows good engineers to preemptively maintain their equipment and prevent failures.
In support of this change:

Add a "can of oil" prototype and give engineers some at at round start in the electrical locker.
Disable the BreakerFlip random event.
While here, adjust the mapping suffix of the substation prototype with correct units (MW to MJ).

A nice side effect of this change: responsible engineers cannot "just" fix power by bridging MV or LV segments, because that would overload a substation and cause it to burn oil at a faster rate. If the substation is not subsequently serviced, it will fail much faster because it is overloaded.
Screenshots

FAQ
Why not just have mice bite random wires or have random wires burn out?
Substations are easier to locate and cannot be under walls.
Why oil in substations? That seems fake.
It's a real thing.
How long will it take for a substation to fail?
 The oil consumption rate is: exp(16kW/5kW)/60 = 0.4u per minute. Since substations start filled with 30u, it will finish consuming its oil, if not maintained, in 30u/0.4u = 73 minutes.
Then, substations have a 10% chance of taking 10 damage (out of 100) every 10 seconds. That means on average, it will take 10 damage every 1/0.1 * 10 seconds = 100 seconds. Since it takes 10 hits to destroy the substation, it takes 1000 seconds = 17 minutes on average.
So, the time to expected failure is 73 + 17 = 90 minutes. Of course, more heavily loaded substations will fail sooner, and lightly loaded substations will not fail in a reasonable amount of time. These numbers, of course, can be tuned.
Won't all the substations fail at the same time and everything will be terrible?
No. Substations consume oil at a rate based on the amount of power they are supplying. The first substation to fail will likely be the substation that is loaded the most. There is a good distribution of substation loads across all the stations available:
Bagel:

Maraton:

Meta:

Omega:

Packed:

Pillar:

Saltern:

What happens if someone puts water in the substation?
That would be traitorous activity. The examine text would show that the substation is still well-filled, but once all the oil is used up, the substation will start taking damage (despite it appearing to be well-filled). It does not (currently) accelerate damage.
Changelog
:cl: notafet

add: Substations now require maintenance to prevent eventual failure.

What happens if someone puts water in the substation?
That would be traitorous activity. The examine text would show that the substation is still well-filled, but once all the oil is used up, the substation will start taking damage (despite it appearing to be well-filled). It does not (currently) accelerate damage.

Is there a way to detect this at all? If the transformer was fully filled with water is there a way to 'drain' the transformer of the water and replace it with oil again?

What happens if someone puts water in the substation?
That would be traitorous activity. The examine text would show that the substation is still well-filled, but once all the oil is used up, the substation will start taking damage (despite it appearing to be well-filled). It does not (currently) accelerate damage.

Is there a way to detect this at all? If the transformer was fully filled with water is there a way to 'drain' the transformer of the water and replace it with oil again?

Currently, deconstruct and reconstruct the substation. If someone poured water into your car's gas tank, how'd you get it out? We can consider adding a siphon, but see below.
I could perhaps add examine text for when the substation is taking damage, so that you could tell it's out of oil despite the fill line indicating otherwise.
I didn't consider this issue important enough, because if someone really wanted to sabotage your substation and has already gotten into the substation vault, they could just blow it up.

If you're meleeing a substation it's going to blow up in your face vs some indeterminate time later.

At a minimum make it require access so any greytide walking past can't mess with it, but in future the examine should disclose what's in there as someone who isn't familiar with the future isn't going to know why a substation spontaneously broke.

If you're meleeing a substation it's going to blow up in your face vs some indeterminate time later.

How about blowing the substation up immediately after a sufficient quantity of non-oil reagent has been added? This makes sense because it would be "shorting out" the substation.

At a minimum make it require access so any greytide walking past can't mess with it, but in future the examine should disclose what's in there as someone who isn't familiar with the future isn't going to know why a substation spontaneously broke.

So, most transformers are behind engineering-secured doors. There are a handful of transformers out in the open on Packed, and maybe other stations. Isn't this really a mapping issue? Just like how we don't put trigger locks on guns, we just put them behind an armory?

Just have a question about this, is there any way for engineering to obtain more oil in case they run out? If there's no way to get more a traitor engineer could just steal all the oil cans and start filling substations with water, and there's nothing the engineering team could do to fix it.

Just have a question about this, is there any way for engineering to obtain more oil in case they run out? If there's no way to get more a traitor engineer could just steal all the oil cans and start filling substations with water, and there's nothing the engineering team could do to fix it.

Chemists can make oil, so if the stock is depleted, the chemists can make more.
Of course, traitor engineers could just blow up substations with a brick of C4. But it sounds like multiple people are concerned about not being able to spot damage, so I will think of a solution. Either changing the examine text, make some other sign of failure visible, or just make it instant blow up.

Just have a question about this, is there any way for engineering to obtain more oil in case they run out? If there's no way to get more a traitor engineer could just steal all the oil cans and start filling substations with water, and there's nothing the engineering team could do to fix it.

Chemists can make oil, so if the stock is depleted, the chemists can make more.
Of course, traitor engineers could just blow up substations with a brick of C4. But it sounds like multiple people are concerned about not being able to spot damage, so I will think of a solution. Either changing the examine text, make some other sign of failure visible, or just make it instant blow up.

You mean this oil?

Of course, traitor engineers could just blow up substations with a brick of C4. But it sounds like multiple people are concerned about not being able to spot damage, so I will think of a solution. Either changing the examine text, make some other sign of failure visible, or just make it instant blow up.

I do like the concept of subtle, delayed sabotage. I just also want it to be something that could be noticed and stopped without too much annoyance as well.
Maybe make it so you can drain the substation's contents, but if you drain too much oil while it is active then it would immediately catch fire / harm the person working on it. This way the antag can drain some and replace with water for the delayed sabotage, drain all and replace with water for immediate but with consequences on themselves, and the engineer can fully repair / replace the oil by powering the substation down (by cutting the HV wire first) to remove any contaminants. That also means during the complete replace you lose power to whatever it's connected to, just like with the rebuild.
Having a way to tell what's in the substation so you can tell when there is non-oil would be handy, since otherwise it would just appear like it's full but not working which could be frustrating to figure out the actual problem is there isn't actually oil in it.

Just have a question about this, is there any way for engineering to obtain more oil in case they run out? If there's no way to get more a traitor engineer could just steal all the oil cans and start filling substations with water, and there's nothing the engineering team could do to fix it.

Chemists can make oil, so if the stock is depleted, the chemists can make more.
Of course, traitor engineers could just blow up substations with a brick of C4. But it sounds like multiple people are concerned about not being able to spot damage, so I will think of a solution. Either changing the examine text, make some other sign of failure visible, or just make it instant blow up.

 You mean this oil?

I mean this oil. I can fix the description. Oil is not actually used in any recipe, and it doesn't make sense that chefs are cooking with something that contains welding fuel.

Of course, traitor engineers could just blow up substations with a brick of C4. But it sounds like multiple people are concerned about not being able to spot damage, so I will think of a solution. Either changing the examine text, make some other sign of failure visible, or just make it instant blow up.

I do like the concept of subtle, delayed sabotage. I just also want it to be something that could be noticed and stopped without too much annoyance as well.
Maybe make it so you can drain the substation's contents, but if you drain too much oil while it is active then it would immediately catch fire / harm the person working on it. This way the antag can drain some and replace with water for the delayed sabotage, drain all and replace with water for immediate but with consequences on themselves, and the engineer can fully repair / replace the oil by powering the substation down (by cutting the HV wire first) to remove any contaminants. That also means during the complete replace you lose power to whatever it's connected to, just like with the rebuild.
Having a way to tell what's in the substation so you can tell when there is non-oil would be handy, since otherwise it would just appear like it's full but not working which could be frustrating to figure out the actual problem is there isn't actually oil in it.

I like this suggestion.
Any suggestions for how to tip the substation and drain things from it? DrainableComponent doesn't quite to do what we want it to do, since Substation doesn't have ItemComponent.

I like this suggestion.
Any suggestions for how to tip the substation and drain things from it? DrainableComponent doesn't quite to do what we want it to do, since Substation doesn't have ItemComponent.

My guess would be to look into how other tanks work, like the welding fuel / water tanks. I believe they use ReagentTank. Only problem is I don't think those tanks let you fill them. If that's a constraint on ReagentTank then maybe there is a better way to keep track of a solution? I haven't really looked into it too much yet.

Updated to fix merge conflict (and force pushed)
Added drainable component so that substation contents can be sampled and inspected or drained. Of course, don't drain the substation fully while it's on. Call your local chemist to figure out what you actually sampled.
Require maintenance for wallmount substations as well.

very much like this as a subtle mechanic. does having it both be refillable/drainable even work? i remember there being some issues with that previously

very much like this as a subtle mechanic. does having it both be refillable/drainable even work? i remember there being some issues with that previously

Looks like it does not. I'll take a look at those systems and see what it'll take for that to work (probably adding verbs instead of using only OnInteract).

Overcome by events.


Prometheus property storage.tsdb.retentionhas been renamed to storage…

….tsdb.retention.time

Prometheus property storage.tsdb.retentionhas been renamed to storage.tsdb.retention.time


chmod in publish target doesn't work

When running ant publish, the created S12 directory doesn't get the proper 755 permissions that the target should make it have— at least after a clean install on my system. I had to chmod the folder manually.
Consider also deleting the directories created in public_html in the clean target, to help "reset" and find out more about this behavior?
Investigate and fix. 75 points

Java Web Start (and the web-related publishing associated with it is no longer something we want to support. See issue #7.

Java Web Start (and the web-related publishing associated with it is no longer something we want to support. See issue #7.


add untrained resnet

I have added the structure and all the layers. Few more function calls has to be added. This is a rough draft. Can you please check if everything is accordingly till now? cc @darsnack  issue

We can use the weights from Metalhead to train our ResNet model.

Technically, yes. But I believe those weights are designed for the PyTorch structure which doesn't use SkipConnection. There will be some mapping required.
But at some point, all these models will be trained using SciML resources as part of our benchmarking regression. So, we don't need to borrow weights from anywhere. For now, just train for a few epochs to make sure the loss is going down.
If you'd like, we can transition to the end to end flow and train some of these models.

Technically, yes. But I believe those weights are designed for the PyTorch structure which doesn't use SkipConnection. There will be some mapping required.

yes, I went through the repo and I have got an idea to wrap it up.

But at some point, all these models will be trained using SciML resources as part of our benchmarking regression. So, we don't need to borrow weights from anywhere. For now, just train for a few epochs to make sure the loss is going down.

Alright! For now, I have the complete untrained model.

If you'd like, we can transition to the end to end flow and train some of these models.

Sure, its better to test it now. I don't have GPU on my system. how do you suggest to train?

You want to use Chain.

shall I use something like push!(layers, SkipConnection(basic,  basicblock()) in the main resnet()? Then we need 2 more functions as before i.e. basicblock() and botlleneck().

You’ll need basic block, but bottleneck would be replaced by SkipConnection. Look at the gist I linked. Basic block would be like resblock in the gist. This can be used directly with SkipConnection. You could have a helper function to create the shortcut if you want.

I plan to have in total 4 functions i.e. basicblock(there are some layers before the basic block so we can directly link those layers or better use SkipConnection, bottleneck(since this is called 3 times), downsample/identity function, the main resnet function.

That sounds reasonable. It’s probably best to just commit often, and I will review as fast as possible.

I tried searching but I am unable to find ways to use SciML resources to train models.

there is still some problem with stride and dilation. If that is fixed, SkipConnection will work fine. I will resolve those atmax by tomorrow.

Please check if any more tweaks has to be made.

Closing this as I messed up with this branch.


Implement Ordinal Pipe

This pipe will add an ordinal suffix (eg. st, nd, rd) to a number, which is useful for displaying ranks in leaderboards and so on.
Examples:
{{ 1 | ordinal }} <!-- 1st -->
{{ 22 | ordinal }} <!-- 22nd -->
{{ 523 | ordinal }} <!-- 523rd -->
{{ 15 | ordinal }} <!-- 15th -->

Made the changes! Thanks.


🐞 Dagger sends cached context even though file is missing locally

What is the issue?
I was running a pipeline which mounts a binary from my host into Dagger but after removing the binary locally, my pipeline still executed with a cached version of it
Log output
N/A
Steps to reproduce
1 - Build a static binary in your CWD called main
2 - Run the following pipeline once:
package main

import (
	"context"
	"fmt"
	"os"
	"time"

	"dagger.io/dagger"
)

func main() {
	ctx := context.Background()
	c, err := dagger.Connect(ctx, dagger.WithLogOutput(os.Stderr))
	if err != nil {
		panic(err)
	}

	bin := c.Host().Workdir(dagger.HostWorkdirOpts{
		Include: []string{"main"},
	}).File("main")

	out, err := c.Container().
		WithEnvVariable("CACHE", time.Now().String()).
		WithMountedFile("/main", bin).
		WithExec([]string{"/main"}).ExitCode(ctx)
	if err != nil {
		panic(err)
	}

	fmt.Println(out)
}

3 - Remove the main binary after the pipeline succeeds.
4 - Running the pipeline again will pass when I expected it to fail.
This is what I see in the output:
#1 host.directory /home/marcos/Projects/testbug
#1 transferring /home/marcos/Projects/testbug: 10.10MB 0.1s done
#1 DONE 0.1s

#2 importing cache manifest from dagger:10686922502337221602
#2 DONE 0.0s

FWIW this error also happens with current tip verison. Another interesting fact is that even if I bust the engine cache with buildctl prune, this keeps happening.
SDK version
Go v0.5.0
OS version
Linux xps 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Confirmed with @sipsma that this isn't the correct behavior. Assigned to @marcosnils for further investigation.

The first question that's worth looking into is whether this is A) a result of the dir synchronization not copying the delete of the local file to the remote or B) a result of the delete in the remote snapshot not invalidating the cache of the subsequent steps.
This is not super straightforward to debug. My immediate thought would be to

start with a completely clean engine (i.e. docker volume rm dagger-engine.dev)
run the repro once
look at buildkit's internal snapshot dirs and find the ones with the synced local content

docker exec -it dagger-engine.dev ls -la /var/lib/dagger/runc-overlayfs/snapshots/snapshots will list all the snapshots
I'd expect there to be two snapshots: 1 is the actual sync'd dir and one is the copy we make as described here

run the repro again
look at buildkit's internal snapshot dirs again

The expected behavior should be that the underlying sync'd local dir snapshot should no longer have the file which was deleted and there should be a copy of that which is the same. However, given the bug here, it seems like that should probably not end up being the case.

Hey, I'll continue the investigation and let you know guys

@sipsma @marcosnils It's strange because I cannot reproduce the bug :(
# Run repro with main
go run ./test_4757_repro.go
#1 host.directory /Users/tomchauveau/Documents/DAGGER/dagger
#1 transferring /Users/tomchauveau/Documents/DAGGER/dagger: 27B done
#1 DONE 0.0s

#2
#2 0.151 hello world!
#2 DONE 0.2s

#3 importing cache manifest from dagger:10686922502337221602
0

# RM binary
rm ./main

# Rerun repro
go run ./test_4757_repro.go
#1 importing cache manifest from dagger:10686922502337221602
#1 DONE 0.0s

#2 host.directory /Users/tomchauveau/Documents/DAGGER/dagger
#2 transferring /Users/tomchauveau/Documents/DAGGER/dagger: 2B done
#2 DONE 0.0s

#3
#0 0.087 runc run failed: unable to start container process: error during container init: error mounting "/var/lib/dagger/runc-overlayfs/cachemounts/buildkit1253059466/main" to rootfs at "/main": stat /var/lib/dagger/runc-overlayfs/cachemounts/buildkit1253059466/main: no such file or directory
#3 ERROR: process "./main" did not complete successfully: exit code: 1
panic: input:1: container.withEnvVariable.withMountedFile.withExec.exitCode process "./main" did not complete successfully: exit code: 1

@TomChv let me try again. Maybe it was a buildkit thing that was fixed in the latest releases?

@TomChv I effectively can't repro. Even going back to the version where I initially saw the bug. Fun fact is that I can't recall if @jlongtine or @vito also saw this, just to make sure I'm not crazy :loco:
In any case, I can't repro anymore so I'll close this for the moment :pray:


Hero banner: update margins

Describe the bug
Acceptance criteria
-Update the component with the following margin values:
-padding right left should be 3XL, XL, M, following our Large screen, medium screen, and small screen breakpoints.
-padding top and bottom should be 2XL on desktop, and tablet, and XL on mobile
Provide Code
No response
To Reproduce
View live component on docs site
Relevant console log output
No response
What browsers are you seeing the problem on?
No response
Additional context
No response

issue is verified on react and angular

:tada: This issue has been resolved in version 1.17.0-alpha.70 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.21.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.17.0-alpha.32 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


🐛 Dev command fails to start compiled app

When using the fiber dev command, the binary appears to be destroyed before it can be run.

The project in question is an unmodified one generated by the CLI.
System: Windows 10, Go 1.15.2, fiber-cli v0.0.1

v0.0.2 is released too, please try it!

Looks good, it now works. For some reason, running go get -u -v github.com/gofiber/fiber-cli wasn't updating the CLI, but building it manually worked.


Some questions about reproducing SpinQuant PPL(5.9 in SpinQuant paper, 5.96 in your paper)

Hello, everyone!
Thank you for the contributions to the quantization works!
I would like to discuss with you some issues regarding reproducing the results of the SpinQuant paper.
I use the code from SpinQuant, and downlaod the trained R1, R2 from the following position: https://drive.google.com/drive/folders/1R2zix4qeXBjcmgnJN1rny93cguJ4rEE8?usp=sharing
When I inference the PPL of LLaMA-2-7B with the script 2_eval_ptq.sh(I use the defalut configuration w4A4KV4) and got the PPL 6.11, it is not equal to the PPL 5.9 or 5.96.
I changed the training paprameter(add activiation group size and weight block size to 128, modify the learning_rate from 1.5 to 0.001), got the trained R1 and R2.
I also changed the inference pareameter(add activiation group size and weight block size to 128), got the PPL 5.90. it seems the same with the SpinQuant paper, but the paper did not say they have used group size and block size, and the learning_rate is 1.5 in the paper.
This problem has confused me for several days. I would like to get your help. Could you share the training config(train R1 and R2) and inference config to reproduce SpinQuant PPL 5.9? thank you very much.

I can reproduced the PPL 6.14 of SpinQuant.
Change the scripts/2_eval_ptq.sh file, from GPTQ quantization to RTN quantization（--w_rtn）

To reproduce SpinQuant+GPTQ results, you should try the W16A4KV4 checkpoint instead of W4A4KV4 checkpoint. I think this may be the problem.

Thank you very much for answer the question.
I run the default script(SpinQuant/scripts/2_eval_ptq.sh) with W16A4KV4 rotation matrix when inference, got the PPL 5.93x
Thank you again for your help.


Correction in README

Hi,
In Readme.md, for the latest version, should fastAdapter.withFilterPredicate not be replaced with fastAdapter.getItemFilter().withFilterPredicate?
Thanks,
Arun

@nizamsp oh yes you are right. Thank you very much.


api-autocmd bindings

Wanted to know if what I wrote is actually good or not.
resolves #5

@noib3 are the changes satisfactory?

a) don't change the return value of the ffi binding to u32, change error.into_err_or_else(|| result) to    error.into_err_or_else(|| result.try_into().expect("always positive");
b) like I said, always test a binding once you've implemented it by adding a test to oxi-tests. In this case you'll realize that it cannot work because there's no way for users to create a CreateAugroupOpts since the clear field is private. The way to get around it is to use the builder pattern:
#[derive(Clone, Debug, Default, Builder)]
#[builder(default)]
pub struct CreateAugroupOpts {
     #[builder(setter(strip_option))]
     clear: Option<bool>,
 }

c) once you do you'll see that it still doesn't work. I'll spare you the details but basically the opts field of nvim_create_augroup is not a Dictionary but a struct that Neovim generates at build time (in this case called KeyDict_create_augroup.
My advice would be to start with easier bindings. In general all functions that have an opts are somewhat non trivial to write bindings for.  If you want to work on the autocmd module I'd look into nvim_del_autocmd, nvim_del_augroup_by_name or nvim_del_augroup_by_id.

a) Alright thanks for that.
b) Didn't add any tests yet.. since I'm still trying to understand how this works
c) Fair enough.
Thank you @noib3

@noib3 hello I have added a test in oxi-tests, how can I run a specific test?
this testing setup is a bit different to what I am used to.

Unfortunately there's currently no way to run a specific test. This is why. Basically you'd need to compile each test as a cdylib and spin up a Neovim session that loads and runs the library, which I don't think is possible.

@noib3 ouch... I can't really test my test then due to a test that fails in src/api/buffer.rs:35

CI is green so there shouldn't be any tests failing. What OS are you on and what does the error msg say?

I am running WSL Arch for my OS
This is the error message i get:
warning: `oxi-tests` (lib test) generated 1 warning
    Finished test [unoptimized + debuginfo] target(s) in 0.01s
     Running unittests (target/debug/deps/oxi_tests-9bec374157575f9f)

running 1 test
test test_all ... FAILED

failures:

---- test_all stdout ----
thread 'test_all' panicked at 'assertion failed: `(left == right)`
  left: `"thread '<unnamed>' panicked at 'assertion failed: res.is_ok()', src/api/buffer.rs:35:5\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\nAny { .. }\n"`,
 right: `""`', src/lib.rs:64:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    test_all

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

error: test failed, to rerun pass '--lib'

Don't forget to git pull!

@noib3 👀 now I'm getting that nvim_types::error::Error is a private module?

What branch are you pulling from? Try doing a git clone https://github.com/noib3/nvim-oxi && cd nvim-oxi && cargo check, there shouldn't be any errors.

@noib3 I am using a cloned local version of my fork + upstream remote pointing to ur repo, and I pull from the upstream master branch.
The errors come from my code that complains about types being private.

the autocmd bindings have already been implemented so I'm gonna close this

Fair enough I was quite busy, good to see it's implemented


testing

testing

just as a hint you can also create a pullrequest on your own repository selecting your own repository and a branch if you want to test this further. :)


Simplify configuration, accommodate GApps Nano

Would using a different GApps allow me to play games that say 'Your Device is not compatible...." ? Not sure why DI isn't compatible on a Pixel 5 (when it runs on a 4A not emulated)
Thanks for any info you can provide.


Route prefix with hyphen makes closure

Sorry, didn't know what else to call this one.

Laravel Version: 5.5.13
PHP Version: 7.1
Database Driver & Version: n/a

Description:
Building a dead simple site generator. To create 8fold UI. The standard route structure looks like this (this will probably err on the side of more is better, apologies if it's not necessary:
Route::group(['prefix' => 'simple'], function() {
    Route::get('/', SimpleController::class .'@index')
        ->name('simple');

    Route::get('/{component}', SimpleController::class .'@show')
        ->name('simple.component');
});

$ route:list gives me this:
uri                                 name                           action
simple                          | simple                       | SimpleController@index
simple/{component}   | simple.component   | SimpleController@show

Same thing with a prefix of "compound". Went to add "form-controls" and things started getting weird.
Route::group(['prefix' => 'form-controls'], function() {
    Route::get('/', FormControlsController::class .'@index')
        ->name('form-controls');

    Route::get('/{component}', FormControlsController::class .'@show')
        ->name('form-controls.component');
});

$ route:list:
uri                                             name                                   action
form-controls                         | form-controls                    | Closure
form-controls/{component} | form-controls.component | FormControlsController@show

Wouldn't expect that to be a "Closure" action. Changing to this:
Route::group(['prefix' => 'form-controls'], function() {
    Route::get('/', FormControlsController::class .'@index')
        ->name('controls');

    Route::get('/{component}', FormControlsController::class .'@show')
        ->name('controls.component');
});

Gives me this:
uri                                             name                           action
form-controls                         | form-controls           | Closure
form-controls/{component} | controls.component | FormControlsController@show

Wouldn't expect the name of the root route to "form-controls" (nor a Closure, but the name is the weird part for me). Changing to this:
Route::group(['prefix' => 'controls'], function() {
    Route::get('/', FormControlsController::class .'@index')
        ->name('controls');

    Route::get('/{component}', FormControlsController::class .'@show')
        ->name('controls.component');
});

Gives me this:
uri                                            name                           action
form-controls                        | controls                      | FormControlsController@index
form-controls/{component} | controls.component | FormControlsController@show

Is this expected behavior? Am I missing something somewhere?

Setting the name of the route doesn't always cause that name to be set (can be overruled by the prefix).
It's only the root route within the group. (The other routes worked as expected.)
The hyphen seems to make all the difference.

Agian, this is dead simple. No customization. No router helpers - except Active (watson/active), but that's more a reader not a catcher.
I can go with "controls" for now, but this seems really strange and my OCD really wants that route to be "form-controls". :)

Figured it out. Had another route hiding that had "form-controls" on it. Thanks!


[Cactbot] P2S Triggers are confusing, inconsistent with how P3S is done.

Summary
Brief explanation of the feature you'd like to request.
P2S: For Winged/Spoken Cataract callout is "Cleave Behind Head"/"Cleave in front of head", calling out areas that are not safe.
P3S: For Left/Right Cinderwing callout is the current safespot.
I understand that there isn't a true "safespot" for Cataracts but the logic between the two should be similar.

Maybe a translation is wrong but in english Winged Cataract should alert you with Front of head and Spoken Cararact should be Back of head

I play in english and Winged's callout is "CLEAVE BEHIND HEAD"  which is "correct" just inconsistent with the way Cactbot has called mechanics in the past.  If the callout for Winged is supposed to be "Front of head" than that would be more consistent/ correct to me.

https://github.com/quisquous/cactbot/blob/main/ui/raidboss/data/06-ew/raid/p2s.ts#L86
https://github.com/quisquous/cactbot/blob/main/ui/raidboss/data/06-ew/raid/p2s.ts#L105
These are the entries for the head callouts and even if you are looking for the word "cleave" it does not find a single match. Do you have custom triggers e.g. of a friend of yours?

  Thanks for the replies >:)


Distance between nodes on presented graph

Is it possible to increase distance between nodes in created graph? Currently for projects having more dependencies defined it is rather hard to read names of artifacts.

As noted on #1, we've decided to archive this repository. Please feel free to fork it and make whatever modifications you'd like.


bump gdax-node version and change phenotypes.create intfactor

This PR only modifies a few lines, changing package.json and lib/phenotypes.js.
gdax-node has been updated around 11 days ago to support stop losses and entries in version 0.7.0.  I'm not sure how to execute one with zenbot yet, but #721  seems to indicate that it will be possible with this change.
Also, I've added a few lines to fix phenotypes.RangeFactor in the create function as described in #1487.

I just noticed that the previous PR is a bump to gdax version too.  Haha oops.  Well atleast this includes the RangeFactor change too so its not useless.


Missing Axis Swap in ExtractPatches and MergePatches

In patch_utils.py, the modules ExtractPatches and MergePatches are missing an axis swap between the reshapes, resulting in the extracted patches becoming horizontal stripes. For example, if we follow the code in ExtractPatches:
>>> inputs = jnp.arange(16).reshape(1, 4, 4, 1)
>>> inputs[0, :, :, 0]

DeviceArray([[ 0,  1,  2,  3],
             [ 4,  5,  6,  7],
             [ 8,  9, 10, 11],
             [12, 13, 14, 15]], dtype=int32)

>>> patch_size = 2
>>> batch, height, width, channels = inputs.shape
>>> height, width = height // patch_size, width // patch_size
>>> x = jnp.reshape(inputs, (batch, height, patch_size, width, patch_size, channels))
>>> x = jnp.reshape(x, (batch, height * width, patch_size ** 2 * channels))
>>> x[0, 0, :]

DeviceArray([0, 1, 2, 3], dtype=int32)

We see that the first patch extracted is not the patch containing [0, 1, 4, 5], but the horizontal stripe [0, 1, 2, 3].
To fix this problem, we should add an axis swap. For ExtractPatches, this should be:
batch, height, width, channels = inputs.shape
height, width = height // patch_size, width // patch_size
x = jnp.reshape(
    inputs, (batch, height, patch_size, width, patch_size, channels)
)
x = jnp.swapaxes(x, 2, 3)
x = jnp.reshape(x, (batch, height * width, patch_size ** 2 * channels))

For MergePatches, this should be:
batch, length, _ = inputs.shape
height = width = int(length**0.5)
x = jnp.reshape(inputs, (batch, height, width, patch_size, patch_size, -1))
x = jnp.swapaxes(x, 2, 3)
x = jnp.reshape(x, (batch, height * patch_size, width * patch_size, -1))

@young-geng Thanks for pointing it out. If you would like to create a PR then please go ahead otherwise I'll correct it in a couple of days along with the next push.

Fixed in 2f063c9. Closing this issue.

Unfortunately the problem has not been completely fixed. Because we have changed our order of axes in ExtractPatches, we have to take that into account when reshaping in MergePatches. Therefore, in this line, we need to change
x = jnp.reshape(inputs, (batch, height, patch_size, width, patch_size, -1))

to
x = jnp.reshape(inputs, (batch, height, width, patch_size, patch_size, -1))

Thanks a lot for working on this and fixing the problem! This project is awesome!

Fixed. I have also added more specific tests for both ExtractPatches and MergePatches. Let me know if there is anything else :)


Short solution needed: "How to invert image" (python-pillow)

Please help us write most modern and shortest code solution for this issue:
How to invert image (technology: python-pillow)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to invert image


Import official packages with prefix "pkg"

After update plugin this month, pressing super+dot,super+p will import package with prefix "pkg"
like
import (     "time" )
will be
import (     "pkg/time" )
on OSX
user setting is
{     "env": {     	"GOPATH": "/Users/crazy/work/server",         "GOROOT": "/usr/local/go"     } }
and project setting is
"GoSublime": { 	"env": { 		"GOPATH": "/Users/crazy/work/server" 	} }

What version of go are you using? Such package layout (GOROOT/src/pkg) was changed in go1.4 2 years ago IIRC

Also make sure you've read https://github.com/DisposaBoy/GoSublime/blob/master/SUPPORT.md

Thx!  I updated golang to version 1.6 then it fixed.


Check command exists before registering auto-complete provider

Check that a command exists before adding it the command auto-complete provider list.
Possible fix for issue #1203.

I'm afraid this isn't correct implementation. Command existence can change at runtime when you modify $PATH or install new commands. I was thinking of a different solution: lazy load completion providers as a person actually uses some binary name. E.g. Git.ts would only be loaded after I type git.

No worries - @vlad-shatskyi I can see your point. I'm not sure how to code that unfortunately.

@mkenne11, yeah, it's rather a big lift. I'll do it at some point, but not right now.


How to read RTT

In Copper Coap I can see the RTT displayed like this:
[aaaa::212:4b00:798:5606]:5683 (RTT: 138ms) after successful POST
How to implement it with node-coap?
Is there a ACK receive event?

There is not, you can listen for a response.

Can you be more specific?

I've computed RTT in Node-CoAP lib in Node Js. its simple and tested. you can use it.
	var mote_uri = req.query.uri;
	var start = new Date();
	var req = coap.request('coap://[' + mote_uri + ']:5683/sens/mote')
	req.on('response', function(c_res) {
		var RTT = new Date() - start;
		console.info("Execution time: %dms", RTT);
		c_payload = decoder.write(c_res.payload);
	})
	req.end()

it return RTT in milliseconds.

@kaleemullah360
Thanks, I will use it as it gives a good indication on network/connection quality.


Documentation Examples for IAM Broken

https://awslabs.github.io/aws-cdk/refs/_aws-cdk_aws-iam.html#aws-iam-construct-library
Looks like addPermission was deprecated in favor of other approaches. There are no functioning examples of using non-managed policies.

You're right. Thanks for reporting.


Fix for homekit_controller #22368

Description:
Fix for review comment by @MartinHjelmare. Error backporting change from a long running config entry branch.
(When #22194 is merged I already have a test for this code path I can submit, but atm its blocked by #22194).
Checklist:

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

Can be merged when build passes.


🐛 BUG: Discrepancy in Node Module Compatibility Between wrangler deploy and vitest-pool-workers Testing

Which Cloudflare product(s) does this pertain to?
Workers Vitest Integration
What version(s) of the tool(s) are you using?
Wrangler 3.83, "vitest": "^2.1.5", "@cloudflare/vitest-pool-workers": "^0.5.28",
What version of Node are you using?
v20.13.1
What operating system and version are you using?
Mac Sonoma 15.3
Describe the Bug
Description:
I'm experiencing an issue where my Cloudflare Worker with Durable Objects works correctly when deployed using wrangler deploy, but fails during testing with vitest-pool-workers due to Node module compatibility problems.
Problem Summary:
Deployment Works as Expected:

When I deploy my Worker using wrangler deploy, it successfully handles Node module dependencies through compatibility transformations.
This suggests that wrangler correctly replaces or polyfills Node-specific modules to make them compatible with the Workers environment.

Testing Fails Due to Node Dependencies:

When running tests using vitest and @cloudflare/vitest-pool-workers, the same Worker code fails to execute.
The testing environment does not seem to perform the same compatibility module replacements as wrangler deploy.
As a result, imports of Node modules cause errors, and the Durable Objects cannot be tested effectively.

Details:
Node Dependencies in Use:
import { https } from 'node:https';
import { Wallet, keccak256 } from 'ethers';

My Worker code imports https from 'node:https' and uses Wallet and keccak256 from the ethers library.
These dependencies are essential for the functionality of my Durable Objects.

Testing Setup:

I'm using vitest along with @cloudflare/vitest-pool-workers to test my Worker.
My vitest.config.ts is configured using defineWorkersProject from @cloudflare/vitest-pool-workers/config.

Error Messages During Testing:
When running tests, I encounter errors like:
Error: Cannot find module 'node:https'

This indicates that the Node modules are not being resolved or replaced in the testing environment.
Expected Behavior:

The testing environment provided by vitest-pool-workers should handle Node module compatibility in the same way as wrangler deploy.
This would allow tests to run successfully, ensuring that the Durable Objects function correctly in both development and production environments.

Questions and Request for Assistance:

Is there a way to configure vitest-pool-workers to perform the same Node module compatibility transformations as wrangler deploy?

Are there recommended practices for testing Workers that depend on Node modules using vitest-pool-workers?

Could this be a limitation or missing feature in vitest-pool-workers that needs to be addressed?

Steps to Reproduce:

Create a Worker with Node Dependencies:

Write a Cloudflare Worker script that imports Node modules like node:https and uses ethers.

Deploy the Worker:

Use wrangler deploy to deploy the Worker.
Confirm that it works as expected in the production environment.

Set Up Testing Environment:

Install vitest and @cloudflare/vitest-pool-workers.

Configure vitest.config.ts using defineWorkersProject:
import { defineWorkersProject } from '@cloudflare/vitest-pool-workers/config';
import path from 'path';

export default defineWorkersProject({
  test: {
    poolOptions: {
      workers: {
        main: './dist/index.js',
        wrangler: {
          configPath: path.resolve(__dirname, './wrangler.toml'),
        },
      },
    },
  },
});

Run Tests:

Execute vitest to run the tests.
Observe the errors related to missing Node modules.

Additional Information:

Environment Details:

vitest version: [Please specify]
@cloudflare/vitest-pool-workers version: [Please specify]
wrangler version: [Please specify]
Node.js version: [Please specify]

Attempts to Resolve:

I tried adjusting the vitest configuration, including using defineConfig and specifying pool: '@cloudflare/vitest-pool-workers', but the issue persists.
It seems that the compatibility layer provided by wrangler during deployment is not available or not activated during testing.

Conclusion:
I believe there may be a discrepancy between how wrangler deploy and vitest-pool-workers handle Node module compatibility. I would appreciate any guidance on resolving this issue or insights into whether this is a known limitation.
Thank you for your assistance!
Please provide a link to a minimal reproduction
https://github.com/zach-is-my-name/reproduction-vitest-pool-compat-module-error
Please provide any relevant error logs
Click to expand
[~/Projects/charli/apps/session-time-tracker]$ bun run test
$ vitest run --config tests/vitest.config.ts
RUN  v2.1.5 /Users/zm/Projects/charli/apps/session-time-tracker
Using vars defined in .dev.vars
[vpw:inf] Starting isolated runtimes for tests/vitest.config.ts...
❯ tests/sessionTimer.test.ts (0)
❯ SessionTimer Durable Object (0)
❯ tests/websocketEndpoint.test.ts (3)
❯ POST /websocket (3)
× should process peer:joined websocket event
· should return error for invalid signature
· should return error for unsupported event type
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2Futils%2Fgeturl.js&rawSpecifier=node%3Ahttps
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2Futils%2Fgeturl.js&rawSpecifier=node%3Ahttps
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2Futils%2Fgeturl.js&rawSpecifier=node%3Ahttps
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2Futils%2Fgeturl.js&rawSpecifier=node%3Ahttps
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2Futils%2Fgeturl.js&rawSpecifier=node%3Ahttps
workerd/server/server.c++:3059: error: Fallback service failed to fetch module; payload = ; spec = /?specifier=node%3Ahttps&referrer=%2FUsers%2Fzm%2FProjects%2Fcharli%2Fapps%2Fsession-time-tracker%2Fnode_modules%2Fethers%2Flib.esm%2
❯ tests/connectionManager.test.ts (0)
❯ tests/initEndpoint.test.ts (0)
❯ tests/sessionTimer.test.ts (0)
❯ SessionTimer Durable Object (0)
❯ tests/webSocketManager.test.ts (0)
❯ tests/webhookEndpoint.test.ts (0)
❯ tests/websocketEndpoint.test.ts (3)
❯ POST /websocket (3)
× should process peer:joined websocket event
× should return error for invalid signature
× should return error for unsupported event type
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 6 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
FAIL  tests/connectionManager.test.ts [ tests/connectionManager.test.ts ]
FAIL  tests/initEndpoint.test.ts [ tests/initEndpoint.test.ts ]
FAIL  tests/webSocketManager.test.ts [ tests/webSocketManager.test.ts ]
FAIL  tests/webhookEndpoint.test.ts [ tests/webhookEndpoint.test.ts ]
Error: No such module "node:https".
imported from "Users/zm/Projects/charli/apps/session-time-tracker/node_modules/ethers/lib.esm/utils/geturl.js"
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/9]⎯
FAIL  tests/sessionTimer.test.ts [ tests/sessionTimer.test.ts ]
Error: No test found in suite tests/sessionTimer.test.ts
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/9]⎯
FAIL  tests/sessionTimer.test.ts > SessionTimer Durable Object
Error: No test found in suite SessionTimer Durable Object
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/9]⎯
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
FAIL  tests/websocketEndpoint.test.ts > POST /websocket > should process peer:joined websocket event
AssertionError: expected 404 to be 200 // Object.is equality

Expected

Received

200

404

❯ tests/websocketEndpoint.test.ts:51:29
49|     });
50|
51|     expect(response.status).toBe(200);
|                             ^
52|     const text = await response.text();
53|     expect(text).toBe('Webhook processed successfully');
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/9]⎯
FAIL  tests/websocketEndpoint.test.ts > POST /websocket > should return error for invalid signature
AssertionError: expected 404 to be 401 // Object.is equality

Expected

Received

401

404

❯ tests/websocketEndpoint.test.ts:78:29
76|     });
77|
78|     expect(response.status).toBe(401);
|                             ^
79|     const data = await response.json() as { status: string; message: string };
80|
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/9]⎯
FAIL  tests/websocketEndpoint.test.ts > POST /websocket > should return error for unsupported event type
AssertionError: expected 404 to be 400 // Object.is equality

Expected

Received

400

404

❯ tests/websocketEndpoint.test.ts:98:29
96|     });
97|
98|     expect(response.status).toBe(400);
|                             ^
99|     const data = await response.json() as { status: string; message: string };
100|
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/9]⎯
Test Files  6 failed (6)
Tests  3 failed (3)
Start at  18:38:11
Duration  918ms (transform 107ms, setup 131ms, collect 51ms, tests 52ms, environment 0ms, prepare 935ms)
[vpw:dbg] Shutting down runtimes...

Hiya, yeah this is a known issue unfortunately :( The vitest integration provides its own polyfills to get vitest to work, and they're not exactly the same as the ones that wrangler provides. That's not ideal, and we're looking into a solution for this but its a bit of a tricky one.
For reference, these are the polyfills that vitest-pool-workers is adding
https://github.com/cloudflare/workers-sdk/tree/main/packages/vitest-pool-workers/src/worker/lib

Thanks! My workaround is to create a sister testing repo of my production Workers repo without those polyfilled deps.
If there's a better workaround, please advise.
Otherwise I'm glad to know it's not due to improper configuration.
Feel free to close and track as desired.

I don't think there's a better work around currently :/ we've been looking into adding these polyfills to vitest, probs via an unenv plugin.
For reference in case anyone wanders across this - if an api is red in the workerd column, but green in wrangler, it won't be provided to vitest currently and its not you :(
https://workers-nodejs-compat-matrix.pages.dev/

Ah whoops sorry there is a way to get around this! @zach-is-my-name
you can use wrangler to build + add polyfills, then point vitest at the output.
So run npx wrangler deploy --dry-run --outdir dist
Then set [main](https://developers.cloudflare.com/workers/testing/vitest-integration/configuration/#workerspooloptions) in your vitest config to your build output.

Differently than the reproduction?

Deploy the Worker:
Use wrangler deploy to deploy the Worker.
Confirm that it works as expected in the production environment.
Set Up Testing Environment:
Install vitest and @cloudflare/vitest-pool-workers.
Configure vitest.config.ts using defineWorkersProject:
import { defineWorkersProject } from '@cloudflare/vitest-pool-workers/config';
import path from 'path';
export default defineWorkersProject({
test: {
poolOptions: {
workers: {
main: './dist/index.js',
wrangler: {
configPath: path.resolve(__dirname, './wrangler.toml'),
},
},
},
},
});

have you got a compat date > "2024-09-23" or nodejs_compat_v2 and run npx wrangler deploy --dry-run? Seems to work in my reproduction

Argh sorry my bad 🤦 . In your integration test you're still importing from src/index so its not using the polyfills wrangler adds at build time. If I change that in your repo it seems to work for me. (although https.get is only mocked by the polyfills, so I assume that's just for your repro).
Hope that works for you!

Thanks @emily-shen! I'll check it out.  Please allow a few more days I'm working on resolving other Failed to pop isolated storage stack frame in tests/.... errors in the tests with the dependencies removed before I can look at this again.

I'm going to close this as I don't have the bandwidth to follow-up.


feat: apply dynamic css mixin to sliding panel and column picker list buttons

The base-dropdown component is not being used in the archetype, so we can add the prop there when we need it.
EX-7224

Good job! I'd say that it could be worth to add this functionality to the base-dropdown as we have it already identified but also understand the point of leaving it for the future 👍


(populate) - Test for failing fragment traversalUpdate

Add test for failing fragment traversal

Closing since the associated PR has also been closed (?)
@JoviDeCroock @andyrichardson Let's find some time to discuss some of this after we've kicked off the new roadmap

Closing since the associated PR has also been closed (?)
@JoviDeCroock @andyrichardson Let's find some time to discuss some of this after we've kicked off the new roadmap


0.9.2-rc1 Value Operator Regression

After upgrading from 0.9.1 to 0.9.2-rc1 it appears that the < > = operators partially work in queries.
Specifically, I am doing a query like:
select sum(value) from input_bps where hostname =~ /web/ AND value > 10000 group by time(1m),hostname fill(0)
What returns is a grouped measurement for ALL possible "series" that exist, however it 0 fills any values below 10000.  Previously, the measurement was not even returned at all if it was below my value operator.
I'm not entirely sure where in the query engine this is evaluated, however for performance reasons we do this in a lot of places, so it seems like the sooner this assessment can be made, and the query engine can bypass returning the result, the better.

@Jhors2 can you provide some sample output from that query, just to make sure we're understanding the issue you describe?
It sounds like you're saying that the query runs as expected, but the fill(0) is being applied to all points that match where hostname =~ /web/ , including ones that fail value > 10000 . Is that correct?

the fill(0) is applying to all points that fail value > 10000.  It is NOT being applied to points that pass my criteria, these return properly.  The previous experience was that nothing would be returned at all if that condition had failed.  I'll provide sample outputs as soon as I can.

Seeing this in 0.9.3 as well...

The new query engine seems to do this correctly. The values are filtered before reaching the aggregate function so if you do something like this:
> insert cpu value=20<PHONE_NUMBER>000000000
> insert cpu value=10<PHONE_NUMBER>000000000

If you then do this:
> SELECT mean(value) FROM cpu WHERE time >= '2009-11-10T23:00:00Z' AND time < '2009-11-10T23:02:00Z' AND value > 10 GROUP BY time(1m) FILL(0)
name: cpu
---------
time                    mean
2009-11-10T23:00:00Z    20
2009-11-10T23:01:00Z    0
2009-11-10T23:02:00Z    0

Since it will filter out the 10 value, it will then fill in that interval since there are no valid points in that interval.
Please reopen if this is wrong and there's still an issue on the latest version. Thanks!


virt-api, vmi update admitter: Add a constructor

What this PR does
This is a follow-up to PR #12568.
Un-export the fields of VMIUpdateAdmitter for better encapsulation.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

None

/cc @fossedihelm @jean-edouard

/sig code-quality

Change: Dropped the commit to use object receiver.

/approve

/lgtm

Is the title correct? I don't see any factory function

Changed the term to "constructor" as written in the official docs [1].
[1] https://go.dev/doc/effective_go

/lgtm

/retest-required


feature/#35 - tabs for all products+matching yes/maybe/no

Impacted files:

personalized_ranking_page.dart: added a BottomNavigationBar
pubspec.yaml: removed flutter_sticky_header that we don't use anymore
smooth_it_model.dart: refactoring for flexibility

Looks good, I tried it using the Fruit juices category and the sorting in the global list is unclear.
Some products from NO are displayed before ones from MAYBE, probably coming from the Match class

Looks good, I tried it using the Fruit juices category and the sorting in the global list is unclear.
Some products from NO are displayed before ones from MAYBE, probably coming from the Match class

@PrimaelQuemerais I noticed that too with my "Salmon"s.
There are two things in Match: the score (double) and the status (bool).
The products are ordered by descending score, and put in different categories according to the status.
In short, some products have a good score but a "maybe" status. And sometimes they have a better score than a "yes" status product.

@PrimaelQuemerais I noticed that too with my "Salmon"s.
There are two things in Match: the score (double) and the status (bool).
The products are ordered by descending score, and put in different categories according to the status.
In short, some products have a good score but a "maybe" status. And sometimes they have a better score than a "yes" status product.

@PrimaelQuemerais Actually I added myself the "all products" tab and I didn't find any requirement on the display order.
Perhaps we should sort by descending score (as now), perhaps we should sort by status and descending score (as you more or less suggested).

@PrimaelQuemerais Actually I added myself the "all products" tab and I didn't find any requirement on the display order.
Perhaps we should sort by descending score (as now), perhaps we should sort by status and descending score (as you more or less suggested).

@monsieurtanuki just a suggestion for now but, this page use to be a single list view with sections, what about keeping the single list view and the bottom bar, the bottom bar allowing the user to jump directly to a specific section, that way everything is displayed using a single sorting

@monsieurtanuki just a suggestion for now but, this page use to be a single list view with sections, what about keeping the single list view and the bottom bar, the bottom bar allowing the user to jump directly to a specific section, that way everything is displayed using a single sorting

@PrimaelQuemerais My goal was to make the data available (via the model), and I found it easier and more standard to display the data with tabs.
Feel free to add a new PR on top of this one, I'm perfectly OK with that, as long as my PR is approved quickly, in order to have this kind of sequence:

we have a new feature, hurrah! (my part)
and now it looks very good, hurrah! (whoever feels like improving the UI/UX)

@PrimaelQuemerais My goal was to make the data available (via the model), and I found it easier and more standard to display the data with tabs.
Feel free to add a new PR on top of this one, I'm perfectly OK with that, as long as my PR is approved quickly, in order to have this kind of sequence:

we have a new feature, hurrah! (my part)
and now it looks very good, hurrah! (whoever feels like improving the UI/UX)

I'm not that into the logic of the app, so I can't say that much about it. I just tested it out though. It looks really good to me. I just find the button text a bit confusing, maybe something like "compare" would be better. Also, I would suggest that the button is only visible when there are two or more scanned products,

I'm not that into the logic of the app, so I can't say that much about it. I just tested it out though. It looks really good to me. I just find the button text a bit confusing, maybe something like "compare" would be better. Also, I would suggest that the button is only visible when there are two or more scanned products,

Okay merging in the current state

Okay merging in the current state

Thank you @PrimaelQuemerais!
The more features we'll have in the app, the more relevant our questions will be regarding the UI/UX, like @M123-dev's previous comment - before edition ;) (by the way @M123-dev don't hesitate to create issues if you have questions or suggestions about the UI/UX).

Thank you @PrimaelQuemerais!
The more features we'll have in the app, the more relevant our questions will be regarding the UI/UX, like @M123-dev's previous comment - before edition ;) (by the way @M123-dev don't hesitate to create issues if you have questions or suggestions about the UI/UX).

Thank's :)

Thank's :)


删除正在使用中的算法，接口改成返回算法版本

Describe the bug
实际返回：msg: "Version [id: 5] is in use"
To Reproduce
Steps to reproduce the behavior:

新增算法版本 test-algo
算法配置中启用算法版本 test-algo
删除算法版本 test-algo

Expected behavior
预期返回：msg: "Version test-algo is in use"
test-algo是版本名称
Screenshots

If applicable, add screenshots to help explain your problem.
Log Information
If applicable, add more detailed log information to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

已解决
https://github.com/open-v2x/dandelion/pull/185


ays actor update if an actor disappeared from the code base.

root@js82:~# tmux at
[detached (from session main)]
root@js82:~# cd /optvar/cockpit_repos/my-little-grid-server/
root@js82:/optvar/cockpit_repos/my-little-grid-server# ays actor update
actor bootstrap.g8os updated
actor node.g8os updated
error during update of actor node.discovery:

Internal Server Error

        The server encountered an internal error and cannot complete
        your request.

root@js82:/optvar/cockpit_repos/my-little-grid-server# ays actor --help
Usage: ays actor [OPTIONS] COMMAND [ARGS]...

  Group of commands about actors

Options:
  --help  Show this message and exit.

Commands:
  list    list all actor of the repository
  update  Update actor to a new version.
root@js82:/optvar/cockpit_repos/my-little-grid-server# ays actor list
Installed actors:
-------------------
bootstrap.g8os
node.discovery
node.g8os
storagepool

What was the error from ays window in tmux?

How did the actor disappear from the code base? Actors generally stay put, they tend to stick around

@FastGeert can you add steps to reproduce?


Grammar error in Release Notes summary

Storage Explorer Version: 1.11.2
Build: 20191213.1
Branch: hotfix/1.11.2
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer -> Help -> View Release Notes.
Check the last sentence in the summary.

Expect Experience:
No grammar error.
Actual Experience:
There is a grammar error.

Since the Release Notes has been updated, So we close it.


Remove docs for Service Catalog integration

This is a removal request

What would you like to be added

Find the service catalog docs

https://k8s.io/search might be helpful

Remove them (no forwarding address)

Also edit any pages on this site that previously linked there.
Make this change either to the main branch, or to the branch for the upcoming Kubernetes release, whichever seems more appropriate.
Why is this needed
https://github.com/kubernetes/community/pull/6632
Comments
/sig service-catalog
/language en
/priority backlog
/lifecycle frozen
/triage accepted

/assign

Hi @sftim , Do you want to completely remove the context on the above page? https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/

We should find all the documentation that is for Service Catalog, and remove all of it. That removal would include deleting the page https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/
We might also want to edit the docs for earlier Kubernetes releases to add an explanatory note, because people will sometimes find those pages from a web search etc. However, the key task to fulfil this issue is to delete the existing documentation for Service Catalog.

The PR #34387 closes this.
/assign @Rishit-dagli

/unassign

Resolved by #34387.
/close


'RLMArray_Private.hpp' file not found in CocoaPods Install RealmSwift

I'm getting a 'RLMArray_Private.hpp' file not found (the same for "RLMAccessor.h" , "RLMConstants.h" and other files) while upgrading via cocoa pods from 0.91 to 0.92 using RealmSwift.
Am I doing something wrong or something else I need to do?
Thanks in advance.
PS: I've upgraded the CocoaPods and tried re-installing Realm from scratch with no success

What version of CocoaPods are you using? You'll need to be in at least 0.37.1.

Yes it's 0.37.1 (mentioned that I did the upgrade but not to what version, sorry about that)

Hm, could you try clearing the cached download of the Realm and RealmSwift pods (rm -r ~/Library/Caches/CocoaPods/Pods/Released/Realm*)? You'll then need to force re-installation by deleting the Pods/Realm*

I had the same issue, solved it by running the following commands:
rm -rf "${HOME}/Library/Caches/CocoaPods"
rm -rf "pwd/Pods/"
pod update
hope this helps with your case.

@mtgomes : My solution is remove Realm in Podfile -> Pod install -> Add Realm in Podfile again -> Pod install. It's work for me.

Thanks for the great suggestions. It's working now. I removed and re-added the pods and now it's compiling with no errors. This doesn't help a lot, I know, but can't really figure out how it was fixed.

This issue happened for us too (identified by CI server, then reproduced after a clean checkout). Unfortunately the fixes here don't work. Instead:
Installing Realm (0.94.1)
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup

core is not a symlink. Deleting...
Downloading dependency: core <IP_ADDRESS>
Downloading core failed. Please try again once you have an Internet connection.

I do have an internet connection, and a reasonably decent one.
To fix:

Got colleauge to run steps and commit (we have checked in pods).
Failing that I was about to go looking for a Realm.framework binary.

@jasperblues we serve our core builds from AWS S3, which I believe was experiencing issues around the time you posted this. Please check http://status.aws.amazon.com/ next time this happens.

Hello @jpsim Thanks for the information. We ended up linking Realm as a framework. Perhaps we'll try going back to CocoaPods.


withCheck()

@rultor release, tag is 0.0.5

@rultor release, tag is 0.0.5

@rultor release, tag is 0.0.5

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.5

@yegor256 Done! FYI, the full log is here (took me 4min)


chore: Document type checking

Description
Summary of changes
Adds documentation to the type checking pass
Additional context
This PR is based off the name resolution docs PR since that PR also included some docs in hir_def/types.rs

@TomAFrench is this okay to merge?


Move to Rollup instead of Webpack

Should at least investigate if we can move to Rollup instead of Webpack. Like Webpack mentions on their blog, Webpack is great for sites, but Rollup might be better for libraries.
https://medium.com/webpack/webpack-and-rollup-the-same-but-different-a41ad427058c
If anyone has any experience or would like to help out, please comment here.

@spatialillusions take a gander @ #146

Awesome work! I will have a look as soon as possible, kind of deep into building test renderings for APP-6 D at the moment.
Did you find any reason for not moving to rollup?

@spatialillusions Did you find any reason for not moving to rollup?

Nope, and I'm already using rollup on all my own library projects that require bundling.

Well I merge the pull and we give it a try.

Could you just explain or give a link to what the map file does? I'm a bit confused about that one.
And I saw a nifty sample of how rollup simply could grab the version number from the package.json, so that should be done in the next step.

@spatialillusions source maps allow CDN users (like from unpkg.com) to debug the minified/uglified code with the original source showing in their debugger.


Android studio improvements

Motivation for this change
Things done

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

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

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

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: android-studio-preview
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: android-studio-preview
Partial log (click to expand)
collision between `/nix/store/zr3n4vx9l22z5fp7b1zv1awp94v6z2lz-gcc-7.3.0-lib/lib/libgcc_s.so' and `/nix/store/jwshxi80myfvadl81kppm6a76q6r70ln-glibc-multi-2.27/lib/libgcc_s.so'
collision between `/nix/store/zr3n4vx9l22z5fp7b1zv1awp94v6z2lz-gcc-7.3.0-lib/lib/libgcc_s.so.1' and `/nix/store/jwshxi80myfvadl81kppm6a76q6r70ln-glibc-multi-2.27/lib/libgcc_s.so.1'
collision between `/nix/store/590id60kl4m0gkpnsbgias07c0zhndks-shadow-4.5/etc/login.defs' and `/nix/store/jirhpap3v67pjl826kz97rgpf8kya35n-android-studio-beta-<IP_ADDRESS>-fhs-env-chrootenv-etc/etc/login.defs'
collision between `/nix/store/590id60kl4m0gkpnsbgias07c0zhndks-shadow-4.5/etc/pam.d' and `/nix/store/jirhpap3v67pjl826kz97rgpf8kya35n-android-studio-beta-<IP_ADDRESS>-fhs-env-chrootenv-etc/etc/pam.d'
created 1088 symlinks in user environment
building '/nix/store/iwywyy98gy4r3y3i494mzw8xgckx7ina-android-studio-beta-<IP_ADDRESS>-fhs-env-fhs.drv'...
building '/nix/store/0pi2ys8inif03563ikfjcjcyqj6r1nla-android-studio-beta-<IP_ADDRESS>-fhs-env-init.drv'...
building '/nix/store/2m5shb12m5m3yvx6h0hqwdhy45zmrpif-android-studio-beta-<IP_ADDRESS>-fhs-env.drv'...
building '/nix/store/59jigjblci4v6cncrrvhn44vpi76wly3-android-studio-beta-<IP_ADDRESS>-wrapper.drv'...
/nix/store/cp4j0wiy7fzran9fai2kd3b8qm4b69w5-android-studio-beta-<IP_ADDRESS>-wrapper

Success on aarch64-linux (full log)
Attempted: android-studio-preview
Partial log (click to expand)
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
wrong ELF type
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
cannot find section .dynamic
building '/nix/store/ng5hp71f2v3jmcr6sszw9wn3r8xw3cj0-android-studio-beta-<IP_ADDRESS>-wrapper.drv'...
/nix/store/h2qrirh4gbf40m5b1107jqs12jd3dgab-android-studio-beta-<IP_ADDRESS>-wrapper

I think this broke evaluation https://gist.github.com/GrahamcOfBorg/6b399b49b5528b9befa525051bd2c2f9

@LnL7 Looking at the last line:
attribute 'gconf' missing, at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/eval-2-shlevy.ewr1.nix.ci/pkgs/applications/networking/instant-messengers/gitter/default.nix:16:6

I think this was actually due to https://github.com/NixOS/nixpkgs/commit/e090fb29672530c14bb14b153fabdca2280835b0, but thank you very much for the notification anyway :smile:.
From the fist lines it definitely looks like this PR is responsible:
trace: android-studio-preview and androidStudioPackages.preview are old aliases
and will be dropped at some point, please use androidStudioPackages.beta
instead (corresponds to the correct channel name).

But that's actually supposed to be there (when building android-studio-preview or androidStudioPackages.preview), I'm not sure if that was a good idea though, let's hope this doesn't cause any problems with Hydra... (if it does or if we don't want this, we can revert https://github.com/NixOS/nixpkgs/pull/44310/commits/88bfbf6c7d2308b59f1ca69169c8c9853815ae6b)

There were apparently two problems at that point.  ATM reverting your commit fixed the tarball job for me, so I pushed that.  Maybe this is doable by fixing the tarball job instead, but at least for now...

@vcunat Thank you very much for reverting it and sorry for any inconvenience caused (was hoping it would be fine...).


Document enums as extendable

In Mbed TLS, as a general rule, enum types are extendable. There are many enum types declared in public headers, and when we claim backward compatibility, we mean that future versions will not remove enum values (so code that constructs enum value will keep working), but we do allow future versions to add enum values (so code that does case analysis on enum values without a default will not keep working). We should make this explicit.
This is analogous to https://github.com/ARMmbed/mbedtls/issues/4371, but we didn't really claim that enums were not extensible even in Mbed TLS 2.x. So I don't think this is critical for 3.0, although it may be considered a bug that it isn't documented explicitly now.

#4600 adds to BRANCHES.md a statement that “Adding items to an enum” is not considered an API break in Mbed TLS 3.x. So this is fulfilled in Mbed TLS 3.x.
As Mbed TLS 2.x is getting close to LTS-only, I don't think it's worth the bother to improve the documentation in this respect at this point. So I'm closing this issue as resolved by #4600.


Add support for 'as' and 'from' in import statement

for issue #209

That's great! I will give it a try.

hi @ebussieres,  could give some response?

As it appears this repo is dying, I have decied to create and maintain a new fork of Pebble at JavaEden/Pebble, and I would love to get this PR merged into the new repo. Please take this PR and open a new one to the dev branch of JavaEden/pebble.
The future of Pebble has been shaky for a while now, but I refuse to let Pebble die. It is a great project, and I hope to give it same love and care that the original maintainers have as they built Pebble. If you have any questions about the future of Pebble, please reach out on Gitter. Let's keep this community alive, I hope to see you over at the new location!
New Pebble Home

Original announcement of new ownership: https://github.com/PebbleTemplates/pebble/issues/311#issuecomment-379496941
https://github.com/JavaEden/pebble
https://bintray.com/javaeden/Eden/Pebble
https://gitter.im/JavaEden/pebble

It seems to cause some performance issue. About 10-15% drop in performance

ok, I will try the benchmark later.

I did the benchmark test in my development environment.
Compared to the master branch, the results show that there is not much difference in performance.
The following are my environmental information and test data.
And I have move the the MacroAttributeProvider branch down. plz take one more try under your environment. @ebussieres
// env info
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

Intel Xeon E312xx (Sandy Bridge)
Linux 2.6.32-642.1.1.el6.x86_64 #1 SMP Tue May 31 21:57:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

// results
// benchmarks-0.jar: version 2.2.0
Benchmark          Mode  Cnt      Score     Error  Units
Pebble.benchmark  thrpt   50  13080.610 ± 238.601  ops/s
Pebble.benchmark  thrpt   50  12950.239 ± 531.155  ops/s

// benchmarks-1.jar: origin master
Benchmark          Mode  Cnt      Score     Error  Units
Pebble.benchmark  thrpt   50  11559.832 ± 414.224  ops/s
Pebble.benchmark  thrpt   50  11423.473 ± 343.797  ops/s

// benchmarks-2.jar: Added support for 'as' and 'from' in import statement
Benchmark          Mode  Cnt      Score     Error  Units
Pebble.benchmark  thrpt   50  11231.329 ± 318.845  ops/s
Pebble.benchmark  thrpt   50  11705.103 ± 360.210  ops/s

// benchmarks-3.jar: Move the MacroAttributeProvider branch down.
Benchmark          Mode  Cnt      Score     Error  Units
Pebble.benchmark  thrpt   50  11372.813 ± 458.316  ops/s
Pebble.benchmark  thrpt   50  11421.412 ± 187.204  ops/s

@yanxiyue It seems that some tests are missing here. Cases when there's a name clash with the alias if it's already defined for example. Please add these tests. Except for that, it's clean and i'll merge it when more tests is gonna be added.
Thanks !

ok， i will add some test cases in the next days.


Delete current logged line

Most hooks aren't perfect, and sometimes they can send more text than needed.
In my case, my hooks sends the entire backlog when i trigger it. This is annoying when doing it by accident as it inflates character count.
It would be nice to delete the last sent line (and deleting it from the statistics as well) to work around faulty hooks like this.
Idk if being able to delete every logged line is necessary; just the current one would be a big help.

Implemented in https://github.com/rampaa/JL/commit/3742ac3b1a6265907fdefe8254cdc068a1846aff, will be included in the next release.
The hotkey allows you to delete the currently shown line. You can change the currently shown line by "Move backwards (Backlog)" and "Move forward (Backlog)" hotkeys.


Update Hero.component.tsx

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

Project coverage is 97.40%. Comparing base (bb1ce0f) to head (e01672d).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   97.40%   97.40%
=======================================
  Files          19       19
  Lines         154      154
  Branches       36       36
=======================================
  Hits          150      150
  Misses          4        4

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


Add tests for the datetimetz type

This adds tests for the DateTimeWithTimezone type.
They currently fail on purpose, because of #29

To add a sense of urgency here, with elixir 1.3.0 thanks to xref this will emit compile time warnings:
tobi@airship ~/github/timex_ecto $ elixir -v
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:10] [kernel-poll:false]

Elixir 1.3.0-rc.0 (7881123)
tobi@airship ~/github/timex_ecto $ mix clean
tobi@airship ~/github/timex_ecto $ mix compile
Compiling 7 files (.ex)
warning: undefined protocol function dump/1 (for protocol Ecto.DataType)
  lib/datatype.ex:1

warning: undefined protocol function dump/1 (for protocol Ecto.DataType)
  lib/datatype.ex:23

warning: function Ecto.Type.blank?/1 is undefined or private
  lib/types/date.ex:14

warning: function Ecto.Type.blank?/1 is undefined or private
  lib/types/datetime.ex:14

warning: function Ecto.Type.blank?/1 is undefined or private
  lib/types/datetimetz.ex:34

warning: function Ecto.DateTimeWithTimezone.cast/1 is undefined (module Ecto.DateTimeWithTimezone is not available)
  lib/types/datetimetz.ex:57

warning: function Ecto.Type.blank?/1 is undefined or private
  lib/types/time.ex:14

Generated timex_ecto app

Happy to help you fix those, looking for a bit of direction how some of them should be fixed. E.g. here in this PR, should there be some timex.parse function instead?
Thanks for timex & timex_ecto :)
Tobi

So sorry for the delay, been tough keeping up the past month or so. I'll try and get to all the open issues today :)

@bitwalker thanks for tending to it and now worries, I know tending to a lot of OSS projects is very time consuming and can be troublesome. Looking at all your projects, thanks for all of those :)


Added missing attributes and methods for HTMLInputElement

ref : https://github.com/facebook/flow/pull/1767
I'd really like to see those changes and the other contributor is not replying on the PR.
@mroch

@facebook-github-bot import

rebased on upstream master

ping @mroch
I'm wondering if this is going to make it into master ?

sorry for the delay! getting this rebased and landed now.


inclusive terminology

Hey, I just made a Pull Request!
Replaced some terms with inclusive terminology (VMware initiative).
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Hi! This is a very nice initiative. Thank you. Let us know if we can help somehow. The CI output mentions needing to apply prettier formatting on files, maybe you have the ability to enable auto formatting in your editor for example.

Regarding the Vale checks you see - complaining about valid words like "allowlisted" that Vale doesn't yet know of - you can just add those words to .github/vale/Vocab/Backstage/accept.txt as part of the pull request to silence the check.

Oh and allow me to note that you'll want to add some text at the bottom of the changeset file, something short like "Tweaked wording to use inclusive terminology" is fine.
You also don't need to declare things in the changeset, whose changes are entirely within like comments that aren't public. As in, if it's just a word in a // comment somewhere, then that won't affect the built package at all, so it's fine to not "ship" that noop-change to npm. If you happen to have one too many in the changeset it's no huge deal though, so don't worry too much about it.

Oh merging master "backwards" is notoriously hard to solve the DCO checks for. I'd recommend rewinding that commit and instead rebasing.


Handle undefined from getPropertyNameForPropertyNameNode

...which can be returned when the property name is computed.
Part of #34404

@typescript-bot port this to release-3.7

@typescript-bot cherry-pick this to release-3.7


request: DrawPhysics implements all phycs

so we can get stuff like this in Editor mode debug:

yeah i'm doing that

Sorry, This isn't feasible to maintain or within the scope of the debugging API. You'll just have to specify the full UnityEngine.Physics in those few cases where there's mixed usages in one file.


Importing @sveltejs/gl during dev raises an exception

Describe the bug
Importing @sveltejs/gl during dev raises the following exception:
500

Must use import to load ES Module<EMAIL_ADDRESS>
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:329:5)
    at Module.load (node:internal/modules/cjs/loader:971:11)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:997:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at nodeRequire (/home/ushi/repos/sveltexr/node_modules/vite/dist/node/chunks/dep-6e02b235.js:69041:17)
    at ssrImport (/home/ushi/repos/sveltexr/node_modules/vite/dist/node/chunks/dep-6e02b235.js:68999:20)
    at eval (/home/ushi/repos/sveltexr/src/routes/gl.svelte:9:31)
    at instantiateModule (/home/ushi/repos/sveltexr/node_modules/vite/dist/node/chunks/dep-6e02b235.js:69027:166)

This may occur with other ES modules as well.
To Reproduce
npm init svelte@next
npm i -D @sveltejs/gl

Add a gl.svelte route with the following
<script>
	import * as GL from '@sveltejs/gl';
<script>

Start the dev server and navigate to that route, (probably http://localhost:3000/gl).
Expected behavior
Should import without exceptions
Information about your SvelteKit Installation:

The output of npx envinfo --system --npmPackages svelte,@sveltejs/kit --binaries --browsers

  System:
    OS: Linux 4.19 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (24) x64 AMD Ryzen Threadripper 2920X 12-Core Processor
    Memory: 22.71 GB / 31.30 GB
    Container: Yes
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 15.8.0 - ~/.nvm/versions/node/v15.8.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 7.5.2 - ~/.nvm/versions/node/v15.8.0/bin/npm
  Browsers:
    Firefox: 83.0
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.65
    svelte: ^3.29.0 => 3.36.0

Severity
Blocking usage of svelte/gl and probably other ES based modules
Additional context
Discord thread: https://discord.com/channels/@me/474342761529606144/826909912884969482

@samccone
The only relevant stack trace I get is included in the description above, which occurs when navigating to the route when running with the dev mode server.

Try moving it between dependencies and devDependencies. Also try to include or exclude it in optimizeDeps. Hopefully if you try all the combinations one will work

@benmccann I tried the various combinations but to no avail.

Hmm, it's weird that library would fail because it looks like it's already written in ESM format. I don't know if perhaps adding a module field to package.json or adding a "type": "module" and renaming from .mjs to .js or something would help.
It seems like there might be some Vite weirdness going on here and I don't quite understand what it is. It might also help to see if this can be reproduced in a Vite project without SvelteKit. I think npm init @vitejs/app would create a Vite app, but client-side only and I don't know if that's enough to reproduce or not. Might have to try it in a project like https://github.com/sveltejs/vite-plugin-svelte/tree/main/packages/playground/vite-ssr

@saabi would you be able to test this PR and see if it fixes the issue? https://github.com/sveltejs/gl/pull/31

@benmccann Adding "type": "module",  to @sveltejs/gl didn't work either. It keeps throwing the same exception.

Thanks for testing it. One last thing, can you try adding it to ssr.external / ssr.noExternal?
I see a few lines from Vite in your stack trace, it looks like this is considered an external dependency and so Vite will try to require it which seems to be what's failing. I guess it should try to import it instead. If the ssr settings don't work (or maybe even if they do) this should probably be filed as a bug in Vite

This config change worked for me — no changes required to @sveltejs/gl:
const node = require('@sveltejs/adapter-node');
+const glslify = require('rollup-plugin-glslify');
-const pkg = require('./package.json');

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
  kit: {
    // By default, `npm run build` will create a standard Node app.
    // You can create optimized builds for different platforms by
    // specifying a different adapter
    adapter: node(),

    // hydrate the <div id="svelte"> element in src/app.html
    target: '#svelte',

    vite: {
      ssr: {
-       noExternal: Object.keys(pkg.dependencies || {})
-     }
+       noExternal: ['@sveltejs/gl']
+     },
+     plugins: [
+       glslify()
+     ]
    }
  }
};

@Rich-Harris That worked for me as well.
I'm completely new to Vitejs. I also had no idea rollup plugins would work out of the box, like for glslify. Good to know, thanks!

Thanks for looking into this Rich and for testing all the suggestions @saabi
I'm going to go ahead and close this since it's working for you now in favor of https://github.com/sveltejs/kit/issues/904 which should be a longer-term solution to the issue


Canceling district placement closes build menu

In Vanilla Civ VI, when you click a district, it "zooms" into the city showing you where you can place it with relevant modifiers. If you right click, it cancels out of the placement menu, but brings you back to the build menu, so you can choose to build something else.
In CQUI, when you click a district, it shows you where you can place it with the relevant modifiers, but when you right click, it cancels out of the build menu. I think it would be better if it brought you back to the default build menu so you can choose to build something else.

Thanks for the report! I'm on it


Hot Exit does not work on Mac

VSCode Version: 1.8.1, 1.9.1
OS Version: OS X EI Capitan

Steps to Reproduce:
VSCode settings:

"files.hotExit": "onExit"
"files.autoSave": "off",

open a folder
create 2 new file, type some words in both files without saving.
when closing the instance of the VSCode window, it weirdly asks "Do you want to save the changes you made to the following 2 files", click "Don't Save". Next time, open a new instance of VSCode and open the same folder, the two new files the Untitled-1 and Untitled-2 are opend but both are blank.

another test:

open a folder
open an existing file
make some change to the file without saving.
when closing the instance of the VSCode window, it weirdly asks "Do you want to save the changes you made to a.cs", click "Don't Save". Next time, open a new instance of VSCode and open the same folder, but the previously modified file shows nothing changed.

@cateyes99 closing a window on macOS does not exit the application. If you want to have hot exit on closing windows you need to configure onExitAndWindowClose

@bpasero u r right. i missed that point. Once change to onExitAndWindowClose, it does work thx.


Horizontal listview

Added ability to switch orientation of listview to horizontal. I've only tested in my own app and it works fine. The only caveat, as with vertical listview, is that if size_hints of the views are not None in the corresponding orientation, then populate() might generate inconsistent sizes as you scroll down the list. Because of this, I forced size_hint to be (None, None) in the case of the labels for item_strings.
Hopefully this is compatible with geoff's branch.

please rebase and re-open


Focus time status and category configurations

I love using the focus time, it is a game changer. I don't think this is a bug, but more of a 'nice to have' additional options - I'd like to have a way to configure my focus time as 'tentative' slot, rather than 'busy', since I want people to be able to send me a meeting request for those timeslots as well (and not see me as busy in the Scheduling Assistant). Another thing is the category label (each category has different color) that would be nice to incorporate. I like seeing different colors in the calendar, so that I can easily know which is my focus time.
I am currently editing focus time status as tentative and category manually which is no big deal. The only struggle is when I get some additional meeting requests during the focus time and the automatic scheduler changes the focus time timeslot, and I need to change status and category manually again.
Do let me know what you think of these suggestions. Thank you for making this feature, I love it! :)
Cheers,
Katarina

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.