Update SegmentedControl to support images

Platforms Impacted

[x] iOS
[ ] macOS

Description of changes
Added an optional image to the SegmentedItem. If the image is set, we'll only display the image and not the text, but we'll still use the text for accessibility.
Changed pillMaskedLabelsContainerView's name to pillMaskedContentContainerView, since now it holds more than just labels.
Changed the maskedLabels array to be an array of optionals, since I'm also adding an array for the maskedImages, and we don't need the label/image that isn't being used.
Also updated the logic in sizeThatFits, since I was getting weird results where the window's layout guide was nil or something and just returning zero. (the before iPhone portrait picture shows what I'm talking about)
Moved some logic out of for loops, since there were a few places we were doing things every loop when it was never going to change during the loop.
Verification

Before
After

Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[x] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

tested darkmode and accessibility as well?

tested darkmode and accessibility as well?

There's an issue with the disabled dark mode colors, but I haven't had a chance to test voice over or keyboard navigation yet.


CPU utilization problem

[ ] I have marked all applicable categories:

[ ] exception-raising bug
[ ] RL algorithm bug
[x] system worker bug
[x] system utils bug
[ ] code design/refactor
[ ] documentation request
[ ] new feature request

[x] I have visited the readme and doc
[x] I have searched through the issue tracker and pr tracker
[x] I have mentioned version numbers, operating system and environment, where applicable:

  # ding version `v0.2.0`, linux platform

Issue Description
CPU utilization is not 100% and very low. (below 5% on average)
Steps to Reproduce
clone the repo and git checkout main. (currently on 0fcfdf26).  Run python3 dizoo/slime_volley/entry/slime_volley_selfplay_ppo_main.py. Open htop to check CPU usage. Only one core is occupied on a multi-core machine.
What Do We Need?
During training, run command mpstat 3. The column of %idle is less than 20% (Current value is 97%)

Hello, this is a serious system design problem, which may require fundamental refactor of the framework. Need some guys familiar with framework and system design to work on this.
Could us know the current progress on this? @PaParaZz1

Hello, this is a serious system design problem, which may require fundamental refactor of the framework. Need some guys familiar with framework and system design to work on this.
Could us know the current progress on this? @PaParaZz1

We are preparing new design about main entry function and new benchmark results on cartpole will be updated at 11.8.

...will be updated at 11.8.

@PaParaZz1, could us know the latest FPS results? Do we get as fast as SampleFactory

One open source framework released last week showed that EnvPool can get even 2x improvement over SampleFactory.
@PaParaZz1  Could us know the latest FPS results of di-engine please 😔

One open source framework released last week showed that EnvPool can get even 2x improvement over SampleFactory.
@PaParaZz1 Could us know the latest FPS results of di-engine please 😔

EnvPool is cpp env manager what I said before, and we are doing a new brave main entry refactor, so we delay the detailed asynchronous pipeline benchmark to the end of November. Besides, we will adapt a new env manager choice(DI-engine + EnvPool) this week, but EnvPool only supports Atari now.

@PaParaZz1 Hello there, it's been 3 months long. We have to ask if there is any update on this ticket.

Hi, @zxzzz0, glad to see you are still following about this issue. In fact, we have been making some important improvements in the past three months, including process architecture optimization and objective horizontal comparison. First, please take a look at some of the results of our test:

All test code, reports and tensorboard screenshots will be open sourced on github in the future, so you can try it yourself.
Next I will try to explain the problems you found and our solution (and will be updated in 1.0 version).
RL efficiency is divided into two parts: environment collection speed and training speed, and we are concerned with maximizing the overall speed, because if the environment is constantly collected (using the entire CPU) and the training speed cannot keep up, it will only cause a large amount of invalid data. ,vice versa.
Therefore, we mainly solve this problem from two aspects. The first is to make the collection and training asynchronous, so that the model will not wait for the data of the environment, and the environment will not wait for the model to update, and the two can maintain a certain step difference. In fact, not only the environment and training, most of the steps within the entire pipeline can be asynchronous. This is not well supported in most frameworks as far as I know.
The second point is to reduce the waste of resources caused by the synchronization of the parent and child processes, that is what you said, the problem of CPU running dissatisfaction during collection. In fact, if you use the top command, the env manager does not always run down the CPU of the entire machine, but there will be periodic fluctuations in it. This fluctuation is due to the fact that only one parent process is used to collect all of the data in child processes. We will solve this issue of bottleneck in v1.0, and we can see the difference in cpu usage between the new execution mode (bottom of picture) and the previous execution mode (top of picture) through the upper and lower comparison charts.

I hope these explanations will restore your confidence in DI-engine and help you in your future work, keep following us, thank you.
Best.


cmd/compile: incorrect type assertions on conflicting package names

This is a bug that has existed since Go1.0.
Consider the following packages:
package iface // import "github.com/dsnet/example/iface1/iface"

import "fmt"
import "reflect"

func CheckInterface() {
	type iface interface { unexported() }
	var v interface{} = foo{}
	t := reflect.TypeOf(v)

	t1 := reflect.TypeOf((*iface)(nil)).Elem()
	t2 := reflect.TypeOf((*interface { unexported() })(nil)).Elem()
	fmt.Println("reflect implements named interface:  ", t.Implements(t1))
	fmt.Println("reflect implements interface literal:", t.Implements(t2))

	_, ok1 := v.(iface)
	_, ok2 := v.(interface { unexported() })
	fmt.Println("type assertion on named interface:   ", ok1)
	fmt.Println("type assertion on interface literal: ", ok2)

	fmt.Println()
}

type foo struct{}
func (foo) unexported() {}

package iface // import "github.com/dsnet/example/iface2/iface"

import "fmt"
import "reflect"

func CheckInterface() {
	type iface interface { unexported() }
	var v interface{} = foo{}
	t := reflect.TypeOf(v)

	t1 := reflect.TypeOf((*iface)(nil)).Elem()
	t2 := reflect.TypeOf((*interface { unexported() })(nil)).Elem()
	fmt.Println("reflect implements named interface:  ", t.Implements(t1))
	fmt.Println("reflect implements interface literal:", t.Implements(t2))

	_, ok1 := v.(iface)
	_, ok2 := v.(interface { unexported() })
	fmt.Println("type assertion on named interface:   ", ok1)
	fmt.Println("type assertion on interface literal: ", ok2)

	fmt.Println()
}

type foo struct{}
func (foo) unexported() {}

In the setup, we have two packages both named iface where the source code of both packages is identical, but they have different absolute package paths.
Running the following program:
package main
import (
	iface1 "github.com/dsnet/example/iface1/iface"
	iface2 "github.com/dsnet/example/iface2/iface"
)

func main() {
	iface1.CheckInterface()
	iface2.CheckInterface()
}

Prints the following (on Go1.0 to Go1.8):
reflect implements named interface:   true
reflect implements interface literal: true
type assertion on named interface:    true
type assertion on interface literal:  true

reflect implements named interface:   true
reflect implements interface literal: false
type assertion on named interface:    true
type assertion on interface literal:  false

The output slightly differs on Go1.9, but is still wrong.
We expect that calling iface1.CheckInterface() and iface2.CheckInterface() to produce the exact same results. However, that is not what we see. In iface2, type assertions via a interface literal on unexported fields no longer works properly, but it works as expected in iface1.
\cc @ianlancetaylor @josharian @mdempsky @neild

Append the following two lines at the end of iface1.CheckInterface() is okay,
	var x interface { unexported() } = foo{}
	_ = reflect.TypeOf(x)

but append them at the end of iface2.CheckInterface() will cause run time panic.

The issue is interface { unexported() } describes different types when written in different packages, because unexported is an unexported identifier.
However, the runtime type descriptor we produce for both is given a linker symbol of type.interface { iface.unexported() }. I.e., it's package name qualified, but not package path qualified. It's also marked dupok.
The fix here is we need to qualify these structs by their package path, not just their package name.

This is clearly undesirable, but I think the fix is too delicate for this late in the release cycle. We've evidently lived with it since 1.0, so I think it can wait another release.

This has been around forever. Clearly we should fix it but it's also not a release blocker.


[BUG] occasional crashes in CI

Describe the bug
I have been seeing some crashes in CI that look like they are caused by some kind of memory corruption, but I am not sure. They are intermittent
16:51:11  All tests passed.
16:51:12  #
16:51:12  # A fatal error has been detected by the Java Runtime Environment:
16:51:12  #
16:51:12  #  SIGSEGV (0xb) at pc=0x00007f2b75cad562, pid=30764, tid=0x00007f253dddb700
16:51:12  #
16:51:12  # JRE version: OpenJDK Runtime Environment (8.0_282-b08) (build 1.8.0_282-8u282-b08-0ubuntu1~16.04-b08)
16:51:12  # Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode linux-amd64 compressed oops)
16:51:12  # Problematic frame:
16:51:12  # C  [libc.so.6+0x84562]  cfree+0x22
16:51:12  #
16:51:12  # Core dump written. Default location: /.../core or core.30764
16:51:12  #
16:51:12  # An error report file with more information is saved as:
16:51:12  # /.../hs_err_pid30764.log
16:51:12  Compiled method (nm)<PHONE_NUMBER>8     n 0       sun.misc.Unsafe::freeMemory (native)
16:51:12   total in heap  [0x00007f2b60a1a690,0x00007f2b60a1a9c0] = 816
16:51:12   relocation     [0x00007f2b60a1a7b8,0x00007f2b60a1a800] = 72
16:51:12   main code      [0x00007f2b60a1a800,0x00007f2b60a1a9c0] = 448
16:51:12  Compiled method (nm)<PHONE_NUMBER>8     n 0       sun.misc.Unsafe::freeMemory (native)
16:51:12   total in heap  [0x00007f2b60a1a690,0x00007f2b60a1a9c0] = 816
16:51:12   relocation     [0x00007f2b60a1a7b8,0x00007f2b60a1a800] = 72
16:51:12   main code      [0x00007f2b60a1a800,0x00007f2b60a1a9c0] = 448
16:51:12  #
16:51:12  # If you would like to submit a bug report, please visit:
16:51:12  #   http://bugreport.java.com/bugreport/crash.jsp
16:51:12  #
16:51:12  [INFO] ----------------------------------------------

Copied from #1823
jvm crash in nightly build during UT intermittently, try increase jvm heap size
OutOfMemory and StackOverflow Exception counts:
OutOfMemoryError java_heap_errors=1

hs_err_pid2506.log

I think I found the issue. This is related to the concurrent modification exception that we occasionally see when the tests are shutting down. The stack trace for the bad free in hs_err_pid2506.log is when we are freeing a host buffer that was "leaked". I cannot tell the size of the host buffer, but from the stack trace it is not a pinned buffer, so it is not the pinned memory pool, which we expect to leak.  But it is being cleaned by the MemoryCleaner on shutdown to verify any leaks that we might have.  This is something that no one would turn on in production, so I think we are OK with shipping 0.4 without any fix in place.  When I look at the cleaner code there is not locking. It was written with the assumption that GC would remove any need for locking because it would show up in the queue when there are no references left to the object. When we force the cleanup to happen at shutdown there are now race conditions. I think we need to put in some locking in the actual cleanup code for each buffer. It should be a simple change and cheap because there should be no lock contention in the common case.

I spoke with @abellina and he had a patch he was working on related to synchronization in the Memory cleaner for UCX work. He is going to extend that patch to also cover what I suspect the cause of this issue is too.

Because the bug is in the java CUDF code and not in this code I am going to target this to the 0.5 release.  Also the only way that this can be triggered, if I am correct in my analysis, is when we turn on the debug leak detection, which no one should ever do in production.

My fix targeted the cleaner synchronization. I'd say close this one and re-open if more CI crashes show up?

We are closing this one for now as we haven't seen this. If you happen to see a similar bug show up in CI please reopen.


Search and path params in TanStack Router incompatible with useHref

Provide a general summary of the issue here
TanStack Router interpolates path params into the href:
<Link to="/projects/$id" params={{ id: '123' }}>Open</Link>

When using React Aria Components' router integration this gets turned into:
<Link href="/projects/$id" routerOptions={{ params: { id: '123' } }}>Open</Link>

As useHref of RouterProvider only receives the href but not routerOptions like navigate does, the navigation itself works correctly but the native features like Cmd+Click (or right-click "Open in new tab") navigate to the href template instead of the real link. Also the URL preview shown by the browser is wrong.
This could easily be solved by also passing routerOptions to useHref.
TanStack Router can also manage search params through a separate prop which suffers from the same issue.
I'm open to contributing this change but wanted to check upfront in case I'm missing something here. Maybe there is a reason for routerOptions not being passed to useHref that I'm unaware of.
🤔 Expected Behavior?
href on a tag to be /projects/123 with the above example.
😯 Current Behavior
href on a tag is /projects/$id with the above example.
💁 Possible Solution
Pass routerOptions to useHref as 2nd paramter.
🔦 Context
No response

I went ahead and created https://github.com/adobe/react-spectrum/pull/6591

What do you think about making href optional for components if routerOptions is provided?
For both Tanstack Router and React Router, routerOptions is solely needed in order to be able to generate the necessary href to attach to components. RouterProvider's useHref can then solely take in routerOptions instead of the href passed in to components.

You can also define the href type to accept an object instead of a string if you want.
declare module 'react-aria-components' {
  interface RouterConfig {
    href: YourRouterHref
  }
}

@devongovett Is there anything I can do to get a review on #6591? Maybe I missed something during the PR creation?

Sorry just busy and we had the week off last week for a holiday. Will discuss with the team.

@devongovett Thanks! Take your time.

We discussed this today. We were originally thinking that routerOptions was meant for things that affected the behavior of the navigation rather than only the URL itself (e.g. replace and resetScroll). We could add them to useHref but it would sort of mix concerns.
An alternative suggestion would be to define the href to as an object corresponding to all of the options that TanStack router accepts rather than just a string.
import {ToOptions, NavigateOptions} from '@tanstack/react-router';

declare module 'react-aria-components' {
  interface RouterConfig {
    href: ToOptions;
    routerOptions: Omit<NavigateOptions, keyof ToOptions>;
  }
}

Then you can use them on a RAC component like this:
<RACLink
  href={{
    to: '/dashboard/invoices/$invoiceId',
    params: { invoiceId: 2 },
  }} />

and get autocomplete for both to and params.
This API also has the advantage that since both to and params are part of the same type, it's possible for typescript to infer the params based on the route. This would require a bit more work with TanStack Router's types to get working, but it should be possible. Also good news is that this should be possible today without any code changes.
Here's a StackBlitz example.
What do you think of this approach?

@devongovett That is an interesting idea. Let me try that in my codebase. Currently I'm using the patch from my PR and wrap components to fix the auto-completion but this sounds much cleaner.

@devongovett I gave it a try now but params are sadly not typed based on to but instead simply offer params from all routes. But I think that's what you meant by "This would require a bit more work with TanStack Router's types", right?

Yeah, that's what I meant. It should be possible, but I didn't quite figure it out. You'd basically need to generate a union of objects like {to: '/foo', params: {}} | {to: '/foo/$bar', params: {bar: string}}.
I tried something like this:
type Href = {
  [To in ToOptions['to']]: ToOptions<RegisteredRouter, string, To>
}[ToOptions['to']];

but it didn't seem to work. I'm probably missing something.

Succeeded in getting params to work with a small modification building on @devongovett above. Here's what I changed from the recommendation in the docs:
import {type NavigateOptions, type ToOptions, useRouter} from '@tanstack/react-router';
import {RouterProvider} from 'react-aria-components';

declare module 'react-aria-components' {
  interface RouterConfig {
-   href: ToOptions['to'];
+   href: ToOptions;
    routerOptions: Omit<NavigateOptions, keyof ToOptions>;
  }
}

function RootRoute() {
  let router = useRouter();
  return (
    <RouterProvider
-     navigate={(to, options) => router.navigate({ to, ...options })}
+     navigate={(path, options) => router.navigate({ ...path, ...options })}
-     useHref={(to) => router.buildLocation(to).href}
+     useHref={({ to }) => router.buildLocation({ to }).href}
    >
      {/* ... */}
    </RouterProvider>
  );
}

This allows passing in params using an object for href:
<Link href={{ to: "/admin/forms/$formId", params: { formId: form._id } }} />

And still supports passing in a simple string for href.

@evadecker You should be able to pass the whole object passed to useHref into buildLocation instead of just to.
I also tried this already but TBH I couldn't get params type being dependent on to to work, even when using ToOptions as href instead of just ToOptions["to"].

@levrik Changing it to useHref={(path) => router.buildLocation(path).href} works the same as destructuring { to }. But passing a string as a component's href still throws an error:

@evadecker Passing as string doesn't work if you define just ToOptions as it's the whole interface and not just the to string.

@levrik You're right. I could've sworn that ToOptions included | string but I must've been looking at TanStack's Link component. A bit confusing getting all the types to play nicely with React-Aria. I still haven't been able to get external links working properly.

Any status update on https://github.com/adobe/react-spectrum/pull/6591 or other changes here?
Unfortunately I'm still fighting with TanStack + RAC routing, and I'm a bit lost trying to dive into all the type definitions here between RAC's Link, RAC's RouterProvider, and TanStack, which overlap in ways that aren't totally clear to me.
It'd be great if RAC's Link component could handle these three cases out-of-the-box:

Accept an href as a string with Intellisense for existing routes (works today), e.g. <Link href="/about" />
Accept search and path params for dynamic routing with TanStack router (the changes suggested above enable this, but degrade DX by forcing engineers to provide an object to href instead of just a string), e.g. <Link href="/posts/$postId" params={{ postId: myPostId }} />
Accept an external link, e.g. <Link href="https://github.com" />

Just adding that this continues to be a problem and it would be good to have a solution or even a workaround

First of all, big thanks to everyone in this thread.

This allows passing in params using an object for href:
<Link href={{ to: "/admin/forms/$formId", params: { formId: form._id } }} />

Passing entire ToOptions to useHref  indeed works well. However, it doesn't work for relative paths. Consider this:
<Link href={{ from: "/admin/forms", to: "$formId", params: { formId: form._id } }} />

The compiler complains that to type is not valid

@mversic You have to type the full path in to. Only parameters that are already present in from are made optional in params. In your use-case there's no benefit of using from as there are no parameters in it. This is how TanStack Router works in general.
But I should also add that nailing down params doesn't work using ToOptions in RAC. params always accepts params of all routes, not only the one set in to. So while this works around the issue of useHref not receiving routerOptions, it doesn't fix the typing issues.

@mversic You have to type the full path in to. Only parameters that are already present in from are made optional in params. In your use-case there's no benefit of using from as there are no parameters in it. This is how TanStack Router works in general.

thanks, I figured that parameters in from are optional. But still, I wanted to do this. That wouldn't work with RAC

But I should also add that nailing down params doesn't work using ToOptions in RAC. params always accepts params of all routes, not only the one set in to. So while this works around the issue of useHref not receiving routerOptions, it doesn't fix the typing issues.

oh, got it. Good that you pointed this out

But still, I wanted to do this. That wouldn't work with RAC

Yep as this requires properties to affect each other inside ToOptions which doesn't work within RAC. The same reason why params do not get nailed down based on to.


[d4hines] feat: make minimum block time configurable

Problem
Currently, we rate limit block production to 1 second. This is useful for normal manual testing, but doesn't make sense when you're trying to maximize throughput. We should make this configurable.
Solution
Accept configuration for minimum block time at the command line

Stacked PR Chain: d4hines

PR
Title
Status
Merges Into

#647
feat: block rate and transaction rate metrics  d4hines/block-rate-and-tps

-

#658
chore: refactor cli terms                      d4hines/batch-operations

#537

#681
chore: refactor config out of node state

#658

#539
Benchmarking: ticket transfers                 d4hines/ticket-transfer-benchmarking

#658

#668
make minimum block time configurable           d4hines/configurable-blocktime

#658

#682
👉feat: make minimum block time configurable

#681

#560
remove static.Dockerfile

-

#558
Simplify Sandbox.sh

-

#559
add gh-stack variable

-

#527
Dummy-ticket

-

#536
feat: add block-by-level rpc

#527

#537
Add block rate and operation rate metrics

#536

I agree with this being configurable, but I would suggest a better patch, a delay of 5s by default unless there is pending_operations, if there is pending_operations(that can be added) you make the block as soon as possible.


Before creating and runing project i get a error

Describe the bug
Error: Missing "./paths" specifier in "@sveltejs/kit" package
at e (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:14845:25)
at n (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:14845:627)
at o (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:14845:1276)
at resolveExports (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:22032:20)
at resolveDeepImport (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:22051:31)
at tryNodeResolve (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:21736:20)
at Context.resolveId (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:21487:28)
at Object.resolveId (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:41587:46)
at async TransformContext.resolve (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:41334:23)
at async normalizeUrl (file:///C:/Users/Gorbulev/Desktop/svelteAuthPhone/node_modules/vite/dist/node/chunks/dep-3007b26d.js:39685:34)
Reproduction
1
Logs
PS C:\Users\Gorbulev\Desktop\svelteAuthPhone> npm create svelte@latest
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

create-svelte version 2.3.4

Welcome to SvelteKit!

√ Where should we create your project?
  (leave blank to use current directory) ...
√ Which Svelte app template? » Skeleton project
√ Add type checking with TypeScript? » Yes, using JavaScript with JSDoc comments
√ Add ESLint for code linting? ... No / Yes
√ Add Prettier for code formatting? ... No / Yes
√ Add Playwright for browser testing? ... No / Yes
√ Add Vitest for unit testing? ... No / Yes

Your project is ready!
✔ Type-checked JavaScript
  https://www.typescriptlang.org/tsconfig#checkJs
✔ Prettier
  https://prettier.io/docs/en/options.html
  https://github.com/sveltejs/prettier-plugin-svelte#options

Install community-maintained integrations:
  https://github.com/svelte-add/svelte-adders

Next steps:
  1: npm install (or pnpm install, etc)
  2: git init && git add -A && git commit -m "Initial commit" (optional)
  3: npm run dev -- --open

To close the dev server, hit Ctrl-C

Stuck? Visit us at https://svelte.dev/chat
PS C:\Users\Gorbulev\Desktop\svelteAuthPhone> npm i
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 105 packages, and audited 106 packages in 8s

13 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
PS C:\Users\Gorbulev\Desktop\svelteAuthPhone> npm run dev -- --open
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

><EMAIL_ADDRESS>dev
> vite dev "--open"

Forced re-optimization of dependencies

  VITE v4.1.1  ready in 1046 ms

  ➜  Local:   http://<IP_ADDRESS>:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help
Missing "./paths" specifier in "@sveltejs/kit" package
Missing "./paths" specifier in "@sveltejs/kit" package (x2)
Missing "./paths" specifier in "@sveltejs/kit" package (x3)
Missing "./paths" specifier in "@sveltejs/kit" package (x4)

System Info
1

Severity
annoyance
Additional Information
No response

Running into the same issue when I create a new project.

Same here, it happens in an already existing project after updating

Downgrading to "@sveltejs/kit": "1.5.6" fixes the issue, it was introduced in 1.5.7.

Starting a new project after a few months away from SvelteKit, and run into this when creating a new project.
Quickest workaround for now is to drop back a version (1.5.7 seems to be the one installed as of right now):
"devDependencies": {
    "@sveltejs/kit": "1.5.6",

This should be fixed in<EMAIL_ADDRESS>

Same issue with a newly created project using npm create svelte@latest.
Downgrading @sveltejs/kit to v1.5.6 fixed it.

We've had multiple people confirm it's working now. Please check that you're running 1.6.0 with npx envinfo --npmPackages "@sveltejs/kit" or head<EMAIL_ADDRESS>If it's still not working, please clarify steps to reproduce. E.g. is it dev, build, or both?


Entity not available: light - LimitlessLED crashed

Home Assistant release with the issue: 0.98.5

Last working Home Assistant release (if known): below 0.97.2
Operating environment (Hass.io/Docker/Windows/etc.): linux, python environment

Component/platform: limitlessled

Description of problem:
Limitlessled stopped showing my light. I use MiLight WiFi gateway.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
light:
  platform: limitlessled
  bridges:
    - host: <IP_ADDRESS>
      version: 6 # tried v5 too
      port: 5987 # tried 8899 too
      groups:
      - number: 1
        type: rgbw
        name: Obývačka stena
      - number: 2
        type: rgbw
        name: Obývačka okno

Traceback (if applicable):
2019-09-10 21:48:18 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform limitlessled
Traceback (most recent call last):
  File "/data/hass.io/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/data/hass.io/lib/python3.7/site-packages/homeassistant/components/limitlessled/light.py", line 140, in setup_platform
    from limitlessled.bridge import Bridge
  File "/home/homeassistant/.homeassistant/limitlessled.py", line 12, in <module>
    from homeassistant.components.light import (
ImportError: cannot import name 'SUPPORT_RGB_COLOR' from 'homeassistant.components.light' (/data/hass.io/lib/python3.7/site-packages/homeassistant/components/light/__init__.py)

Additional information:
feel free to contact me, comment, I'm ready to help

/home/homeassistant/.homeassistant/limitlessled.py

Remove this file.

ok, my fault, I don't remember why exactly I have added this file to HA.
Problem solved, THX.


basic auth for /oauth/token

Hi guys,
my /oauth/token is under basic auth. How use this library in this situation?

You need to set Authorization header for example like this:
this.authOptions = {
      headers: {
        Authorization: 'Basic ' + authdata,
        'Content-Type': 'application/x-www-form-urlencoded'
      }
    };

And then just call getAccessToken with options:
this.OAuth.getAccessToken(user, this.authOptions)

I got a same issue with you and then it's resolved by @baster33 feedback. Thanks @baster33.
I think it has to be fixed. It's incompatible.

@baster33 explained right. I also answered it on #86.


Current syntax is magic

The current syntax for Step, StepS and algorithm usage seems a bit magical - can we simplify it?

The algorithm related syntax is largely focused on the Heterogeneous stuff. I think that with some more concrete types instead of just using function types, this syntax can be completely removed.
The use of some real types will also make the scala type checker a bit more happy.... not that it's particularly strong in this regard


⚠ Samsung has degraded performance

In 53c8b92, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2495 ms

Resolved: Samsung performance has improved in e944a0f.


Difference Between a Website and a Web Application

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2351

@Erastuskanyatta 👋🏾 which issue is this article linked to?

(#2351)Website vs web application: The key Difference
On Fri, Jun 25, 2021, 9:22 PM Briana Nzivu @.***> wrote:

@Erastuskanyatta https://github.com/Erastuskanyatta 👋🏾 which issue is
this article linked to?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/pull/2676#issuecomment-868751656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQSQ6FRXTFCRQZFOY3T4ZMLTUTCQDANCNFSM47BDQCIA
.

plagiarism check done

@BrianaNzivu  changes made as requested. Please have a look at my last commit.


Adhoc filters variable improvements

We're using AdHocFiltersVariable and found a couple of places where we can improve the component/variable:

Add explicit return type to the getValue function, right now it's being narrowed to string | undefined
Expose renderFilters class method, it's useful for cases where we want to make some transformation before getting the value of the filters
When selecting a key from the dropdown, what gets shown as selected is the value instead of the label as one would expect

Open to suggestions, especially in the useEffect for fetching the available keys
Related to this PR

Expose renderFilters class method, it's useful for cases where we want to make some transformation before getting the value of the filters

Can you describe what you mean here? are you extending AdHocFiltersVariable ?


Feature/BOAS-395 create seed prod db pipeline

Describe your changes
scripts etc to create a separate azure pipeline to seed the Prod database only.
This separates it from the other seed script that also adds test data, for Dev and Test environments.
BOAS-395 Create Seed Prod Database Pipeline
https://pins-ds.atlassian.net/browse/BOAS-395
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

LGTM. Could we please also remove the duplication of this code in the seed.js file?

Aah, I left that file as I know you have edited it in your branch.  OK, I will clean that up now

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

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

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

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


Set default image when recipe is saved without an image

this is already implemented, I got mixed up with the API images - so closing the issue
have assigned myself another one instead


AllowedResourceExtensionsForUpload property needs to be removed for S…

…SRS 2016 version of doc
The server property named AllowedResourceExtensionsForUpload does not exist for Reporting Services 2016 version and the product team stated that they will not be updating SSRS 2016 to include the property. So we either need to remove the AllowedResourceExtensionsForUpload  property from the SSRS 2016 version of the documentation or update the documentation and state that the property does not exist for SSRS 2016.

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

#sign-off

This pull request is for the Live branch. We can't merge to Live. Would you resubmit your changes to the master branch? Thanks.


Add a controller for lumen

Codecov Report

Merging #10 into master will increase coverage by 0.65%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master     #10      +/-   ##
===========================================
+ Coverage     94.24%   94.9%   +0.65%
- Complexity       39      45       +6
===========================================
  Files             5       6       +1
  Lines           139     157      +18
===========================================
+ Hits            131     149      +18
  Misses            8       8

Impacted Files
Coverage Δ
Complexity Δ

src/Controller/LaravelController.php
100% <ø> (ø)
2 <0> (?)

src/Controller/LumenController.php
100% <100%> (ø)
2 <2> (?)

src/Provider/PrometheusExporterServiceProvider.php
93.02% <100%> (+2.39%)
14 <12> (+4)
:arrow_up:

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 97

18 of 18 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 94.737%

Totals

Change from base Build 94:
0.7%

Covered Lines:
144

Relevant Lines:
152

💛  - Coveralls

Pull Request Test Coverage Report for Build 97

18 of 18 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 94.737%

Totals

Change from base Build 94:
0.7%

Covered Lines:
144

Relevant Lines:
152

💛  - Coveralls

Pull Request Test Coverage Report for Build 99

18 of 18 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 95.946%

Totals

Change from base Build 94:
1.9%

Covered Lines:
142

Relevant Lines:
148

💛  - Coveralls


Logging in cluster mode works only for first query

In cluster mode, eg. with config such as
snc_redis:
    clients:
        default:
            type: predis
            alias: default
            dsn: [redis://shard01.foo.bar:6380, redis://shard01.foo.bar:6381]
            logging: true
            options:
                prefix: 'BL::'
                cluster: redis

Logger is called only once, with message such as
HGET BL::shopping_wpset_pid_mapping default
An error occured: MOVED 1151 <IP_ADDRESS>:6381

After this, apparently what happens is that Predis creates new connection (StreamConnection) which doesn't use ConnectionWrapper.
This is because RedisCluster::createConnection at https://github.com/predis/predis/blob/54775a02954ac425daef0c3c717665e968b5fc84/src/Connection/Cluster/RedisCluster.php#L308 overwrites parameters which contain logging: true flag. This is checked at https://github.com/snc/SncRedisBundle/blob/d7718cd75166bb256380cf428cbde54402be149e/Client/Predis/Connection/ConnectionFactory.php#L64 but by then configured parameters are gone and there is only host and port left.
Additionally, there is wrong phpdoc with StreamWrapper assumption at https://github.com/snc/SncRedisBundle/blob/d7718cd75166bb256380cf428cbde54402be149e/Client/Predis/Connection/ConnectionFactory.php#L62, as it turned out after constructing it, it returns StreamConnection and not ConnectionWrapper

Workaround:
<?php
declare(strict_types=1);

namespace App;

use Snc\RedisBundle\Logger\RedisLogger;

class ConnectionFactory extends \Snc\RedisBundle\Client\Predis\Connection\ConnectionFactory
{
    public function create($parameters)
    {
        $connection = parent::create($parameters);

        if (null == $this->wrapper) {
            return $connection;
        }

        $wrapper = $this->wrapper;
        $connection = new $wrapper($connection);
        $connection->setLogger($this->logger);

        return $connection;
    }
}

snc_redis:
    class:
        connection_factory: App\ConnectionFactory
    clients:
        default:
            type: predis
            alias: default
            dsn: [redis://shard01.foo.bar:6380, redis://shard01.foo.bar:6381]
            logging: true
            options:
                prefix: 'BL::'
                cluster: redis


@NonNull should allow specifying custom error message thrown

In some cases null pointer is hard to debug if one doesn't have full context data available. I understand that it can be done by appropriate log messaging in DEBUG/TRACE mode, but if I can simply print with this @NonNull all relevant objects.toString(), it can make live easier again.

@NonNull generated a NullPointerException containing the name of the field or parameter as a message. That together with the stacktrace should be enough? Are we missing anything here? Can you at least give an example if the code you would like to be generated and how that would look in your proposal?

I see, I will propose the example first of course. Thank you.


[Touch Only Bug] Transition of the Carousel is started for no reason

EDIT: ignore this message, see my next comment below for the issue cause.
I have a view with a Carousel containing two pages:
Page 1) A view with a search buttons
Page 2) A view containing the search results in a ItemsRepeater inside a ScrollViewer, with a Title and few filter options in a sticky header.

When the user click Enter in the SearchBox, I add a second item to the carousel with an ItemRepeater for the results.
The results  are an incremental collection of photos.
When the vertical offset of the ScrollViewer is hit, I load  in the ItemsSource of ItemsRepeater (ObservableCollection).
With the Mouse, I can scroll down as much as I want with no problem.
With the finger, however, I can scroll but when the new items are added to the ItemsRepeater, the view disapear! including the results, the title and the filters.
But I still can click on the items.
I checked with the Inspector:
The Carousel SelectedIndex is still 1. (my second page with search results page)
However a new ContentPresenter has been added into the Carousel panel

And the previous ContentPresenter containing my page, now has its Opacity set to 0!

I cannot produce a Repro at the moment.
I tested on pc with a touch screen, WASM or Desktop, on a android phone, and in a android sumulator.
Avalonia v11.0
No problem with mouse.
I have no idea what happen at the moment, the issue could be in the Carousel may be. I will continue to try to create a minimum repro.

I think I found something.
I have a transition on the Carousel, and I registered the TransitionStarted and TransitionCompleted event.
When I scroll with finger to the end of my vertical search result page, TransitionStarted on the surrounding Carousel is called.. which should not happend (my Carousel is horizontal).
The disapearing page is due do an Opacity change in my custom transition, but the bug is that the transition should not happen in the first place.

I created a repro sample for this issue
CarouselBugWithFinger.zip
Steps:

Type anything in the SearchBox, the carousel slide to the 2nd page
On the second page, scroll with mouse => see everything is ok
Try to scroll with finger => the view disapear when scrollview hit top (try to scrollup when at 0) or bottom...  (a college also reproduce with two fingers on its trackpage, but I cannot on mine, only touch screen).

Alternate tests:
In Views/UnsplashView.axaml.cs, comment the line : carousel.PageTransition = pageSlide; to remove the transition.
Now, instead of making the view disapear, the view is recreated each time the scroll with finger hit negative position or bottom.
I can see that in ItemsRepeaterEx.cs, those methods are called with finger

Another test:
Replacing Carousel with TransitioningContentControl (commented in UnsplashView.axaml)
There is no more issue with scrolling using the finger.
May be I could use TransitioningContentControl  instead of Carousel, but I also need backward transition, and I think TransitioningContentControl's old content is remove at the begining of the transition.
Could you have a look at my sample to see if it is a bug in Carousel ??? I cannot understand the behavior at all...

I can't as I have no touch device for debugging. Sorry. Haven't checked your sample, is it v11.0? If so, please try latest nightly as things already may have changed.

Hi @timunie
Yes it is 11.0.0 but I have had this bug since I started to work with Avalonia (preview 4).
Until now, I belived it was an Android bug, when I was trying my app on my Android phone's browser.
But know that I have a touch screen I know that it is related to touch device instead.
Do you know someone in Avalonia's team who own a touch device to have a look?
I tried with latest nightly and its the same.
Thanks

ping @emmauss do you have any ideas here?


Cursor location jumps to end of line

We are using vue-monaco with the MonacoEditorPlugin. Attempting to click anywhere in the editor results in the cursor location jumping to the end of the line. Has anyone experienced this issue? Anyone know of a solution? Thanks in advance.

The problem was caused by adding our own padding to the Monaco Editor. Removing additional padding fixed the issue.


Document single-SPA development with override

How to enable the javascript console and yarn serve when building a new tool to refresh live

https://openc3.com/docs/v5/development#running-a-frontend-application


Incorrect result?

Hi guys,
Consider the following program:
use ascent::ascent;
ascent!{
	relation a__(i32, i32);
	relation c__(i32, i32, i32);
	relation e__(i32);
	relation h__(i32, i32, i32);

	e__(a) <-- a__(b, a);
	h__(e, e, e) <-- a__(d, e), c__(e, f, e), e__(e);

}

fn main() {
	let mut prog = AscentProgram::default();
	prog.a__ = vec![(88,5), (37,24), (11,91)];
	prog.c__ = vec![(32,83,88), (2,8,5)];
	prog.e__ = vec![(44,), (83,)];
	prog.h__ = vec![(38,88,18), (76,18,65), (86,73,91), (98,26,91), (76,10,14)];

	prog.run();
	println!("{:?}", prog.h__);
}

If I run the program, I get the following for the relation h__:
[(38, 88, 18), (76, 18, 65), (86, 73, 91), (98, 26, 91), (76, 10, 14), (5, 5, 5)]
Now, if I add a subgoal c__(e, a, e) in the rule for h__ to get the following new program:
use ascent::ascent;
ascent!{
	relation a__(i32, i32);
	relation c__(i32, i32, i32);
	relation e__(i32);
	relation h__(i32, i32, i32);

	e__(a) <-- a__(b, a);
	h__(e, e, e) <-- a__(d, e), c__(e, f, e), e__(e), c__(e, a, e);
}

fn main() {
	let mut prog = AscentProgram::default();
	prog.a__ = vec![(88,5), (37,24), (11,91)];
	prog.c__ = vec![(32,83,88), (2,8,5)];
	prog.e__ = vec![(44,), (83,)];
	prog.h__ = vec![(38,88,18), (76,18,65), (86,73,91), (98,26,91), (76,10,14)];

	prog.run();
	println!("{:?}", prog.h__);
}

The result for h__ changes and I get:
[(38, 88, 18), (76, 18, 65), (86, 73, 91), (98, 26, 91), (76, 10, 14)]
Adding the subgoal c__(e, a, e) should not change the result for relation h__.
The tuple (5, 5, 5) disappears for the second program which should not have appeared for the first program in the first place.
My Cargo.toml file:
[package]
name = "ascent_project"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
ascent = "0.2"

Please let me know if you cannot reproduce this or if I am doing anything wrong.

Thanks for finding it. Indeed this is a bug. It has to do with the interaction of repeated vars in c__(e, f, e) and reordering of clauses. I will push a fix soon. Will you be able to move to 0.3 when the fix is pushed?
And if you need a quick workaround, change it to c__(e, f, e1), if e == e1

Thanks for confirming it.
Yes absolutely I can move to 0.3 when it is ready :)


[bug]  canot find @ast-grep/napi-linux-arm64-musl

the code refers to a non existent optional package
nativeBinding = require('@ast-grep/napi-linux-arm64-musl')
Do you plan to support it ? Is there a workaround possible ?
following optional package are available but  @ast-grep/napi-linux-arm64-musl is missing.
@ast-grep/napi-linux-x64-gnu
@ast-grep/napi-darwin-arm64
@ast-grep/napi-darwin-x64
@ast-grep/napi-linux-x64-musl
@ast-grep/napi-win32-x64-msvc
@ast-grep/napi-win32-arm64-msvc
@ast-grep/napi-win32-ia32-msvc
@ast-grep/napi-linux-arm64-gnu

I don't have plan to support MUSL itself but contributors can take a look at it.


ERROR Error polling for tasks: Headers is not defined ReferenceError: Headers is not defined

Discussed in https://github.com/conductor-sdk/conductor-javascript/discussions/52

Originally posted by Yashg2910 December 15, 2023
Hi, I am getting the following error when I try to poll conductor using the npm library node v.16.14.2.
Can someone tell me what am I missing?
 ERROR Error polling for tasks: Headers is not defined ReferenceError: Headers is not defined      at getHeaders2 (/usr/src/app/node_modules/@io-orkes/conductor-javascript/dist/index.js:3751:3)      at processTicksAndRejections (node:internal/process/task_queues:96:5)      at async /usr/src/app/node_modules/@io-orkes/conductor-javascript/dist/index.js:3828:23

This will only work with node18 or older


Old release note link is broken on What's new page.

Hi Dochub crew, on our What's New Page (https://www.sumologic.com/whats-new/) there's a link to Alert Subscriptions that generates a 404.
Slack Message

PR 1533

Fixed per Slack thread, and all legacy redirects now in place to support legacy What's New posts


Update payloads_not_blocked to host_not_blocked in report_generator.py

🗣 Description
Update payloads_not_blocked to host_not_blocked in report_generator.py

💭 Motivation and context
"We expected the total payloads executed value to match the total number of Not Blocked's in the Host Protection Column of the payloads." Found in issue #65

🧪 Testing
I created the report a few times with different input values to determine that the result matched.

📷 Screenshots
The screenshot show that it is only capturing the total amount from host protection.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[x] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

FYI - as of now current report backlog  = 8

@dav3r or @jsf9k - either one of you able to take a look?
It is a minor calculation change, and we have some reports on hold until we update. Thanks.


enable  csi_secrets_store_provider_aws using gitops

Description
I want to deploy the csi_secrets_store_provider_aws but when I put argocd_manage_add_ons=true I can't choose which addons is deployed using terraform or argocd

[X] ✋ I have searched the open/closed issues and my issue is not listed.

thank you for the issue! At this time we are re-evaluating the integration between Terraform and GitOps operators like ArgoCD. We have removed the integration from the current project and will be tracking all feedback input in #114 while developing the next iteration of this integration


Deadline: Simplify GlobalJobPreLoad logic

Brief description
This simplifies the logic the Deadline plug-in requires to retrieve the OpenPype Executable.

No need to re-save/update the Job to inject OpenPype Executable - the setting is now loaded live from the OpenPype plug-in.
The OpenPype Event Plug-in was only used for injecting the OpenPype Executable info into the job - since that's redundant now, that has been removed. That also means you now only have to set the executable in the regular Deadline OpenPype plug-in (not the Event plug-in).
I've removed the 'invalidate cache' code of getting the Job since now the Job doesn't need to be altered/re-saved we don't need to really invalidate any caches anyway.

Would love to hear whether this would move it in a good direction or whether this is not preferred?
The Event Plug-in also had some "ftrack" related functions which was basically doing nothing currently. I'm not sure if there might be customers out there how do have that logic altered instead and thus the Event Plug-in might still have a place. Something to consider at least.

I am all up for removing the event, I really hated it anyway.

Could you also please purge all mentions of DL event in vendor/readme.md and website/docs/module_deadline.md?

Sure can! Like this?

Any chance we can get the Build/Docs deployment to run again @kalisp @mkolar ?

It seems doc building is failing on GitHub:

Run cd website
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=14". Got "12.22.10"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Seems we will need to update node to 14.x?
Here: > https://github.com/pypeclub/OpenPype/blob/3bc8ae4e3b34cd980db9aad8b47b9437cfd78e3b/.github/workflows/documentation.yml#L23
And on line 44.
I believe that'd be updating Node.js
Not sure if that'd break anything else however.

(Copied from Discord)

With https://github.com/pypeclub/OpenPype/pull/2760 merged should these doc builds now pass @mkolar ?
It appears to still fail.

It should indeed work now, but you need to merge develop to this branch. Github actions are picked from currently checked out branch.

It should indeed work now, but you need to merge develop to this branch. Github actions are picked from currently checked out branch.

@mkolar  Now the check suddenly is gone and thus no documentation build is checked?


feat(RTCGQ02LM): Implement motion timeout

RTCGQ02LM sends a Timeout Motion packet after ~30s of inactivity
Fix #32

@Jc2k Afaik, it send 101b only once to clear the motion state.

It sends 0x101B after 30s without motion.
It periodically sends 0x1017 to confirm absence of motion
So the issue of missing the 0x101B packet is the same as missing the first 0x000F packet : lag to catch the new state

I totally missed this PR. Looks good to me, and should fix https://github.com/home-assistant/core/issues/87296


CVE-2012-5152.yml

Adding CVE-2012-5152.yml

Looks like it doesn't pass the Travis CI test. You will need to fix that in order for this PR to be merged.


experiment crash

I started my train code with allegro trains and suddenly after several epochs I got:
2020-08-17 06:58:05,627 - trains.Task - ERROR - Action failed <401/30: tasks.get_all/v1.0 (Invalid token (invalid jwt token): reason=Signature verification failed)> (id=['ddd67cb5c3524ab0ac876aa509ee2317'], only_fields=['last_iteration'])
2020-08-17 06:58:05,698 - trains.Task - ERROR - Action failed <401/30: tasks.get_all/v1.0 (Invalid token (invalid jwt token): reason=Signature verification failed)> (id=['ddd67cb5c3524ab0ac876aa509ee2317'], only_fields=['status', 'status_message'])
2020-08-17 06:58:06,056 - trains.Metrics - ERROR - Action failed <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=14)>
2020-08-17 06:58:06,058 - trains.Metrics - ERROR - Failed reporting metrics: <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=14)>
2020-08-17 06:58:06,127 - trains.Task - ERROR - Action failed <400/101: tasks.get_by_id/v1.0 (Invalid task id: id=ddd67cb5c3524ab0ac876aa509ee2317, company=d1bd92a3b039400cbafc60a7a5b1e52b)> (task=ddd67cb5c3524ab0ac876aa509ee2317)
2020-08-17 06:58:06,130 - trains.Task - WARNING - ### TASK STOPPED - USER ABORTED - STATUS CHANGED ###
2020-08-17 06:58:06,449 - trains.log - WARNING - failed logging task to backend (1 lines, <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=1)>)
2020-08-17 06:58:06,878 - trains.log - WARNING - failed logging task to backend (1 lines, <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=1)>)
2020-08-17 06:58:08,099 - trains.log - WARNING - failed logging task to backend (1 lines, <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=1)>)
2020-08-17 06:58:08,638 - trains.log - WARNING - failed logging task to backend (1 lines, <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=1)>)
trains.Logger failed sending log [level 40]: "2020-08-17 06:58:08,638 - trains.log - WARNING - failed logging task to backend (1 lines, <400/131: events.add_batch/v1.0 (Events not added: Invalid task id=1)>)"
Terminated

Hi @sagyHarpaz ,
Does that mean the server has started successfully (regarding https://github.com/allegroai/trains-server/issues/56)?
From the log, this looks like an experiment running with data from one server (as well as an authentication token), that suddenly started communicating with a different server (mainly due to the JWT token verification failure).
Also, it seems the experiment (task) ID used afterwards is 1 - which makes little sense as task IDs are randomly generated UUIDs, and explains why it was rejected by the server - did you use a hard-coded task ID?

No I just add
from trains import Task
task = Task.init(project_name="my project", task_name="my task")
to my code as in the example

And which server are you using?

demo server

Can you try to delete your local trains cache? I assume your issue is related to the periodic reset of the demo server which caused your Trains to try reusing nonexistent task Ids (as well as an invalidated Token, which was printed as an error but recovered internally - we'll fix that in the next release).
Trains cache usually resides in ~/.trains - please remove that directory completely and try again :)


Comparison with shapeless-scalacheck?

I'm curious how this library differences from shapeless-scalacheck. Maybe you can add a note on the difference for those who already use that?

You're right, I was thinking at the beginning to just submit scalacheck-shapeless to shapeless-contrib (https://github.com/typelevel/shapeless-contrib/issues/28), but it finally remained a separate project. I'm checking about the status of shapeless-contrib, and I think I'll add back a mention about it in the README then.

For know, the main difference is that scalacheck-shapeless depends on more recent versions of both shapeless (2.1-RC1) and scalacheck (1.12.1). The coproduct support in scalacheck shapeless is also more finely tuned, as all cases of the coproduct are given the same weight, which doesn't seem to be the case in shapeless-contrib.


Fix Caching for Glue Metastore

Remove unused imports.
Rebase
Fix Imports/Checkstyles

Caching across transactions and enabling in-memory cache for Gluestore.
Issue #1487
In continuation to: PR #1495

@Praveen2112 @ebyhr


Docs

Highlight.js is not working for all of the code snippets.

Design is fine for v1. We can merge this few CSS fixes. I will make those.
Also, let's explore on.

Theme for doc.
Markdown docs (Need to see if interactive markdown documentation tool is there for vanilla js projects)

Highlight.js is not working for all of the code snippets.

Let me quickly fix this

It's not working for me on the latest commit as well. I see this error.
https://www.dropbox.com/s/fjqr2woqe9hvacx/Screenshot 2019-09-02 17.57.14.png?dl=0

I don't see this error. Did you build and serve using jekyll?

No I just did python -m SimpleHTTPServer. Will try with jekyll as well.

With Jekyll it worked. I have made some small changes on html(removed h tags from nav links. ) And added some margins.
Will merge this. Thanks


Allow multiple footers

What version of React-Table are you using?
6.5.3
What bug are you experiencing, or what feature are you proposing?
The docs mention that one can add a Footer to a cell by adding JSX, a string or a function as the Footer key to a column configuration. It would be good if the Footer key also took a list of the above, allowing for the rendering of multiple Footer rows per column.
P.S. Thanks for the library, it's fantastic!

You could also just render 2 cells.  Since it accepts JSX, you could put as much or as little in the footer area as you want.  Don't think of it as a single footer property. It's merely a footer hook to do whatever you'd like :)

How does one "just render 2 cells?" You answered the issue but didn't describe how it's supposed to work, nor it is documented anywhere. ☹

How does one "just render 2 cells?" You answered the issue but didn't describe how it's supposed to work, nor it is documented anywhere. ☹

For anyone who finds this in the future, an answer the above:
You can render several divs in the footer hook as long as they are encased in a singular parent div.
 This is even easier if you just steal the existing styles for a table cell from the react-table css file.
I haven't done any of the styling here because I'm in a bit of rush, but here is an example of what I'm talking about:
https://codesandbox.io/embed/myn6x6580p

Thanks for the code @imaan -- I don't necessarily have this issue anymore, but others might!


Implement Sidebar component

The Sidebar component should:

Display the logo and current version of the app
Be responsive
Display a tab for each of the custom views in the DB w/ that view's icon, color, and name displayed correctly
-- ALWAYS require a tab to be selected. By default, the first tab is selected. The currently selected tab's associated component will be displayed in the space not occupied by the toolbar and sidebar.
-- Stub out ProjectList component
Always display an "All Projects" tab even without an "All Projects" view in the DB (just construct a "fake" custom view and slap it onto the data at runtime)
Have a button at the bottom that opens a modal (don't need to fill in the modal, separate issue will cover the "Add View" form that this would normally pull up. for now, this just needs to show a modal that can be closed.

Designs

Just finished this. I'm electing to lose some of the expected customizability from the original designs in the form of the tab icons. It's not worth constructing a universal Icon component to convert icon slugs to heroicons at this point in time, especially given heroicons doesn't seem to expose any direct API for the live list of icons as like a dictionary or anything (not that i expect them to!)


requireSpaceAfterBinaryOperators: issue with location of error

I think the spacing should change to the end of the token right?

I works for single character operators like > and * but not for == and ===
https://github.com/jscs-dev/node-jscs/blob/master/lib/rules/require-space-after-binary-operators.js#L85
Maybe it should be var loc = part.loc.start; -> var loc = part.loc.end;? Although i'm not sure since the === has it point to the middle character.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

This seems to have been fixed by https://github.com/jscs-dev/node-jscs/commit/b5c6dad7daf393eb68727e0617c9141efe35189b on Nov 23. I'll add additional unit tests to prevent any future regressions here.


esp32c3 Unable to do any timing faster than 1ms

Trying to use any of the kernel timing functions for anything less than 1ms does not work on the ESP32-C3. I would have thought I just need to increase the CONFIG_SYS_CLOCK_TICKS_PER_SEC to 10000 to get 100us ticks. But this doesn't work.
I have tried various combinations of CONFIG_SYS_CLOCK_TICKS_PER_SEC and CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC. But it always ends up wrong/very innacurate.
To be specific, sometimes 100us delay would be closer to 250us. Or sometimes 100us delay would be 10ms. But I could never get 100us to equal 100us.
Is it possible to do any real-time scheduling in the tens or hundreds of microseconds? Perhaps, I am missing something but 1ms (1kHz) seems a bit slow to be the timing limit for a 160MHz processor.
Thanks,

Narrowed the issue down to esp32c3_sys_timer.c
A quick workaround was to set #define MIN_DELAY to 1. Then when you increase the CONFIG_SYS_CLOCK_TICKS_PER_SEC it won't be capped at 1ms.
I guess MIN_DELAY might be left over from the esp32s2 driver where the HW CYCLES are faster perhaps? Whereas in the esp32c3 HW CYCLE is only 1us which makes MIN_DELAY of 1000 equal 1ms.
I also set to CONFIG_TICKLESS_KERNEL=n but I never tested if this had any effect on the issue. I suspect that it did not.
This lead me to the other issue which is that the CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC is fixed at 1MHz when the clock is a 16MHz clock. This is because the esp32c3_sys_timer.c file uses systimer_hal functions which use SYSTIMER_TICKS_PER_US. And because the systimer_alarm function uses systimer_hal_get_time.
Instead, base the timers off the systimer_ll functions and then in the systimer_alarm function use use systimer_hal_get_counter_value instead.
Fixing either the MIN_DELAY issue or the CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC issue will allow you to get faster timings.

Trying to use any of the kernel timing functions for anything less than 1ms does not work on the ESP32-C3. I would have thought I just need to increase the CONFIG_SYS_CLOCK_TICKS_PER_SEC to 10000 to get 100us ticks. But this doesn't work.
I have tried various combinations of CONFIG_SYS_CLOCK_TICKS_PER_SEC and CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC. But it always ends up wrong/very innacurate.
To be specific, sometimes 100us delay would be closer to 250us. Or sometimes 100us delay would be 10ms. But I could never get 100us to equal 100us.
Is it possible to do any real-time scheduling in the tens or hundreds of microseconds? Perhaps, I am missing something but 1ms (1kHz) seems a bit slow to be the timing limit for a 160MHz processor.
Thanks,

Hi, can you describe which kernel timing functions you have been using? And how are you measuring the clock in this scenario?


Improve name of uploaded file (include parts of original name)

It will be nice if file will be uploaded to current folder instead of ezshare root folder as well. By the way, very nice software, great to share files in hotel room etc.

I think it's not possible for a command line program to detect the current folder of Explorer/Finder without passing it as a command line arg. This could be possible if we made a GUI for ezshare

File name preservatiion is implemented


+1

+1
Originally posted by @obimod in https://github.com/defunkt/dotjs/issues/118#issuecomment-79477848

https://github.com/defunkt/dotjs/issues/141#issue-598178330

https://github.com/defunkt/dotjs/issues/141#issue-598178330

141 (تعليق)

Are you having difficulty?
I'm watching this repository, this kind of stuff keeps coming into my inbox.
I understand that it is a dead repository. And the readme says so.
By following this I expect to get some news from the maintainer or people that have time and heart big enough to revive this repository back to its glory.
However, this +1 comment is becoming very noisy. So please don't do that. I believe @defunkt is aware and just don't have time to maintain it or it is just not worth the effort since other people have built something similar (See Readme).
Unless you are a bot, in that case, I'm feeling sorry to my self for taking the time to reply to this.


unable to start container named ca

The template below is mostly useful for bug reports and support questions.
Feel free to remove anything which doesn't apply to you and add more information where it makes sense.
Required information

Distribution: Ubuntu
Distribution version: 17.04
The output of "lxc info" or if that fails:
config: {}
api_extensions:

storage_zfs_remove_snapshots
container_host_shutdown_timeout
container_syscall_filtering
auth_pki
container_last_used_at
etag
patch
usb_devices
https_allowed_credentials
image_compression_algorithm
directory_manipulation
container_cpu_time
storage_zfs_use_refquota
storage_lvm_mount_options
network
profile_usedby
container_push
container_exec_recording
certificate_update
container_exec_signal_handling
gpu_devices
container_image_properties
migration_progress
id_map
network_firewall_filtering
network_routes
storage
file_delete
file_append
network_dhcp_expiry
storage_lvm_vg_rename
storage_lvm_thinpool_rename
network_vlan
image_create_aliases
container_stateless_copy
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
addresses: []
architectures:

x86_64
i686
driver: lxc
driver_version: 2.0.7
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.10.0-24-generic
server: lxd
server_pid: 1369
server_version: "2.12"
storage: zfs
storage_version: <IP_ADDRESS>-2

Issue description
lxc launch ubuntu: ca -p default
fails to start container
other names such as c, cb, caa, etc, work, just "ca" won't start
Information to attach
lxc info ca --show-log
Name: ca
Remote: unix:/var/lib/lxd/unix.socket
Architecture: x86_64
Created: 2017/06/23 18:11 UTC
Status: Stopped
Type: persistent
Profiles: default
Log:
/var/log/lxd/lxd.log
ephemeral=false lvl=info msg="Creating container" name=ca t=2017-06-23T14:11:53-0400
ephemeral=false lvl=info msg="Created container" name=ca t=2017-06-23T14:11:53-0400
--debug
DBUG[06-23|14:15:06] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"config":{},"api_extensions":["storage_zfs_remove_snapshots","container_host_shutdown_timeout","container_syscall_filtering","auth_pki","container_last_used_at","etag","patch","usb_devices","https_allowed_credentials","image_compression_algorithm","directory_manipulation","container_cpu_time","storage_zfs_use_refquota","storage_lvm_mount_options","network","profile_usedby","container_push","container_exec_recording","certificate_update","container_exec_signal_handling","gpu_devices","container_image_properties","migration_progress","id_map","network_firewall_filtering","network_routes","storage","file_delete","file_append","network_dhcp_expiry","storage_lvm_vg_rename","storage_lvm_thinpool_rename","network_vlan","image_create_aliases","container_stateless_copy"],"api_status":"stable","api_version":"1.0","auth":"trusted","public":false,"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-----BEGIN CERTIFICATE-----\nMIIFPTCCAyWgAwIBAgIQJlQRzEuSp2/pd7slP9k6ajANBgkqhkiG9w0BAQsFADAz\nMRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRMwEQYDVQQDDApyb290QGx4\nZDAxMB4XDTE3MDYxOTA1NDc1NFoXDTI3MDYxNzA1NDc1NFowMzEcMBoGA1UEChMT\nbGludXhjb250YWluZXJzLm9yZzETMBEGA1UEAwwKcm9vdEBseGQwMTCCAiIwDQYJ\nKoZIhvcNAQEBBQADggIPADCCAgoCggIBAMILH6rWNyKjcm8KvWH+q8vFeOKNNZu+\nc0sDSjyLcjWyUNH6Dp4PXsB07qSMjaTxbYbq/k1P+n4LP3PMB610sbda9NNTXd0c\nuM0aQrRXCe//26h6UscjptArREQfoo/R+fEMteKh0gXtmdUA8H8G1FBwKGgXRmW3\nO9Ij8XmHJZIOQjnr3drAC+NPwyKzSw9hu2Ns7O0NEi5Aign2OApY4mdJRg377gNu\nHwYJUPMy51a337vTeNJ26EiBDALe1l97ImABFKyX+sZl9QqCzvd5uAYxcia3Ut8G\nZQR5t5nPunsDFWFfnGFRHXLEXwZoZ0Ck/6k1E5XwJ1o4x/KVOzwo3tBNPDrHMQqw\n4Ffk3TUvI7BsFSmRrVzKkZo096VvlAKzzWg6S2hg6ijPcIWFeZ1886/3IsfIpNDf\nlsdzRITK/DOlAMa9pHUd+BAwZIZcgbghCA8zqdyng8YpB8eijFHXR8ilyvMNS+mC\nWMpChehvOGKZRsSX/fKGgSaWmogAhYV9GlE6O4tmpgyf/pR41b3kLLWImvDH2GFi\nTh+k48aIqZFx8/9I5MJ6z5yGoYBf9N4gQxt/3WqJ44zGjuwm+qsexX8khzdpApQr\noAqYg48mhK5/YlZIksCk+sUQxV5FXYdsol2ISegEjpC6TQ0rlqBfOlLCJpkoueFm\n5xVo03mgcOh5AgMBAAGjTTBLMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggr\nBgEFBQcDATAMBgNVHRMBAf8EAjAAMBYGA1UdEQQPMA2CBWx4ZDAxhwQK/wAFMA0G\nCSqGSIb3DQEBCwUAA4ICAQAoo6DZHQujHfjMajgSRSyN7lUyz7vleAUU2Yk/aOx9\ng83+mcsfvRpgfpnlHVRzBWUfszgqgb9JiS79oZWiRB9eJk2dszSQFig4/x1yetkM\nJUCxcabwLhdHbk+WsrVOG9lC4psecK2ouC+rMZtZLp705fhVKB20Z7i2udD5AAwW\n+l9mKzeVddHkl/jMzYrMTvAr5XamK1v9I85lo8a6b4e/KZXFc4QNRvtCff9uvYE9\nx2ByhNvGMSk4V0asS5HJVidC7TyFtn4vuoXk96ZI3ySfXP3C7xA+77taQC59Ng/n\nVy+YH809xyb2QqOJVmphiDxE0QdpTcuWYI2lveDrBxStkxoUw8lRum3kiMwqqR18\n9kFknVhiDEGoe56uN/z8+nUSpJyybRcBNqcdsUdtwn1HC0Cn3Xa0xptJviQs//AO\ndjZgMWneq/f82bGmkh8/xReXWz7yDxfeV8MJIYFLjcgzvDtioujbiaEU5nRtS9SC\nzo7whcxl+s2pJnq0H+//KJ1xQprRxSECeKZnFOskn6b/Ux14vMwp1QLWLDhzKGg2\nnSGTORi859g3EOCbi6K5Fl0gkxVw3IFDlbbMTEHiejgK1EQdBt8+QKRSymEcTZi8\nl9WvynDXuk2rqnfnHw/K6JeV0B1/2O+w8r1a93W8Teq88CJJGgZUKHa9jnB8CVe5\nYA==\n-----END CERTIFICATE-----\n","certificate_fingerprint":"","driver":"lxc","driver_version":"2.0.7","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"4.10.0-24-generic","server":"lxd","server_pid":1369,"server_version":"2.12","storage":"zfs","storage_version":"<IP_ADDRESS>-2"}}}
DBUG[06-23|14:15:06] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"config":{},"api_extensions":["storage_zfs_remove_snapshots","container_host_shutdown_timeout","container_syscall_filtering","auth_pki","container_last_used_at","etag","patch","usb_devices","https_allowed_credentials","image_compression_algorithm","directory_manipulation","container_cpu_time","storage_zfs_use_refquota","storage_lvm_mount_options","network","profile_usedby","container_push","container_exec_recording","certificate_update","container_exec_signal_handling","gpu_devices","container_image_properties","migration_progress","id_map","network_firewall_filtering","network_routes","storage","file_delete","file_append","network_dhcp_expiry","storage_lvm_vg_rename","storage_lvm_thinpool_rename","network_vlan","image_create_aliases","container_stateless_copy"],"api_status":"stable","api_version":"1.0","auth":"trusted","public":false,"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-----BEGIN CERTIFICATE-----\nMIIFPTCCAyWgAwIBAgIQJlQRzEuSp2/pd7slP9k6ajANBgkqhkiG9w0BAQsFADAz\nMRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRMwEQYDVQQDDApyb290QGx4\nZDAxMB4XDTE3MDYxOTA1NDc1NFoXDTI3MDYxNzA1NDc1NFowMzEcMBoGA1UEChMT\nbGludXhjb250YWluZXJzLm9yZzETMBEGA1UEAwwKcm9vdEBseGQwMTCCAiIwDQYJ\nKoZIhvcNAQEBBQADggIPADCCAgoCggIBAMILH6rWNyKjcm8KvWH+q8vFeOKNNZu+\nc0sDSjyLcjWyUNH6Dp4PXsB07qSMjaTxbYbq/k1P+n4LP3PMB610sbda9NNTXd0c\nuM0aQrRXCe//26h6UscjptArREQfoo/R+fEMteKh0gXtmdUA8H8G1FBwKGgXRmW3\nO9Ij8XmHJZIOQjnr3drAC+NPwyKzSw9hu2Ns7O0NEi5Aign2OApY4mdJRg377gNu\nHwYJUPMy51a337vTeNJ26EiBDALe1l97ImABFKyX+sZl9QqCzvd5uAYxcia3Ut8G\nZQR5t5nPunsDFWFfnGFRHXLEXwZoZ0Ck/6k1E5XwJ1o4x/KVOzwo3tBNPDrHMQqw\n4Ffk3TUvI7BsFSmRrVzKkZo096VvlAKzzWg6S2hg6ijPcIWFeZ1886/3IsfIpNDf\nlsdzRITK/DOlAMa9pHUd+BAwZIZcgbghCA8zqdyng8YpB8eijFHXR8ilyvMNS+mC\nWMpChehvOGKZRsSX/fKGgSaWmogAhYV9GlE6O4tmpgyf/pR41b3kLLWImvDH2GFi\nTh+k48aIqZFx8/9I5MJ6z5yGoYBf9N4gQxt/3WqJ44zGjuwm+qsexX8khzdpApQr\noAqYg48mhK5/YlZIksCk+sUQxV5FXYdsol2ISegEjpC6TQ0rlqBfOlLCJpkoueFm\n5xVo03mgcOh5AgMBAAGjTTBLMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggr\nBgEFBQcDATAMBgNVHRMBAf8EAjAAMBYGA1UdEQQPMA2CBWx4ZDAxhwQK/wAFMA0G\nCSqGSIb3DQEBCwUAA4ICAQAoo6DZHQujHfjMajgSRSyN7lUyz7vleAUU2Yk/aOx9\ng83+mcsfvRpgfpnlHVRzBWUfszgqgb9JiS79oZWiRB9eJk2dszSQFig4/x1yetkM\nJUCxcabwLhdHbk+WsrVOG9lC4psecK2ouC+rMZtZLp705fhVKB20Z7i2udD5AAwW\n+l9mKzeVddHkl/jMzYrMTvAr5XamK1v9I85lo8a6b4e/KZXFc4QNRvtCff9uvYE9\nx2ByhNvGMSk4V0asS5HJVidC7TyFtn4vuoXk96ZI3ySfXP3C7xA+77taQC59Ng/n\nVy+YH809xyb2QqOJVmphiDxE0QdpTcuWYI2lveDrBxStkxoUw8lRum3kiMwqqR18\n9kFknVhiDEGoe56uN/z8+nUSpJyybRcBNqcdsUdtwn1HC0Cn3Xa0xptJviQs//AO\ndjZgMWneq/f82bGmkh8/xReXWz7yDxfeV8MJIYFLjcgzvDtioujbiaEU5nRtS9SC\nzo7whcxl+s2pJnq0H+//KJ1xQprRxSECeKZnFOskn6b/Ux14vMwp1QLWLDhzKGg2\nnSGTORi859g3EOCbi6K5Fl0gkxVw3IFDlbbMTEHiejgK1EQdBt8+QKRSymEcTZi8\nl9WvynDXuk2rqnfnHw/K6JeV0B1/2O+w8r1a93W8Teq88CJJGgZUKHa9jnB8CVe5\nYA==\n-----END CERTIFICATE-----\n","certificate_fingerprint":"","driver":"lxc","driver_version":"2.0.7","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"4.10.0-24-generic","server":"lxd","server_pid":1369,"server_version":"2.12","storage":"zfs","storage_version":"<IP_ADDRESS>-2"}}}
DBUG[06-23|14:15:06] POST {"devices":{},"name":"ca","profiles":["default"],"source":{"certificate":"","fingerprint":"default","mode":"pull","protocol":"simplestreams","server":"https://cloud-images.ubuntu.com/releases","type":"image"}}
to http://unix.socket/1.0/containers
DBUG[06-23|14:15:06] Raw response: {"type":"async","status":"Operation created","status_code":100,"operation":"/1.0/operations/0623de12-1340-4f2a-865d-7da0daa9f7f6","error_code":0,"error":"","metadata":{"id":"0623de12-1340-4f2a-865d-7da0daa9f7f6","class":"task","created_at":"2017-06-23T14:15:06.025390269-04:00","updated_at":"2017-06-23T14:15:06.025390269-04:00","status":"Running","status_code":103,"resources":{"containers":["/1.0/containers/ca"]},"metadata":null,"may_cancel":false,"err":""}}
Creating ca
DBUG[06-23|14:15:08] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"id":"0623de12-1340-4f2a-865d-7da0daa9f7f6","class":"task","created_at":"2017-06-23T14:15:06.025390269-04:00","updated_at":"2017-06-23T14:15:06.025390269-04:00","status":"Success","status_code":200,"resources":{"containers":["/1.0/containers/ca"]},"metadata":null,"may_cancel":false,"err":""}}
DBUG[06-23|14:15:08] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"architecture":"x86_64","config":{"image.architecture":"amd64","image.description":"ubuntu 16.04 LTS amd64 (release) (20170619.1)","image.label":"release","image.os":"ubuntu","image.release":"xenial","image.serial":"20170619.1","image.version":"16.04","volatile.apply_template":"create","volatile.base_image":"7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25","volatile.idmap.base":"0","volatile.idmap.next":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]","volatile.last_state.idmap":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]"},"devices":{},"ephemeral":false,"profiles":["default"],"created_at":"2017-06-23T14:15:06-04:00","expanded_config":{"image.architecture":"amd64","image.description":"ubuntu 16.04 LTS amd64 (release) (20170619.1)","image.label":"release","image.os":"ubuntu","image.release":"xenial","image.serial":"20170619.1","image.version":"16.04","raw.lxc":"lxc.id_map =\nlxc.id_map = u 0 100000 200\nlxc.id_map = g 0 100000 200\nlxc.id_map = u<PHONE_NUMBER>\nlxc.id_map = g<PHONE_NUMBER>\nlxc.id_map = u 2000<PHONE_NUMBER>6\nlxc.id_map = g 2000<PHONE_NUMBER>6\n","user.vendor-data":"#cloud-config\n\n# Set timezone\ntimezone: US/Eastern\n\n# User setup\nusers:\n - name: jfgibbins\n   uid: "1000"\n   sudo: ['ALL=(ALL) NOPASSWD:ALL']\n   groups: sudo\n   shell: /bin/bash\n - name: jfryer\n   uid: "1001"\n   sudo: ['ALL=(ALL) NOPASSWD:ALL']\n   groups: sudo\n   shell: /bin/bash\n\n# Run commands\nruncmd:\n# - dpkg -i --force-confdef /home/jfgibbins/htpc/apps/puppet-agent_1.9.3-1xenial_amd64.deb\n\n# Output\noutput: {all: '| tee -a /var/log/cloud-init-output.log'}\n\n# Final_message\nfinal_message: "The system is finally up, after $UPTIME seconds"\n\n","volatile.apply_template":"create","volatile.base_image":"7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25","volatile.idmap.base":"0","volatile.idmap.next":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]","volatile.last_state.idmap":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]"},"expanded_devices":{"jfgibbins":{"path":"/home/jfgibbins","source":"/home/jfgibbins","type":"disk"},"jfryer":{"path":"/home/jfryer","source":"/home/jfryer","type":"disk"},"root":{"path":"/","pool":"lxd","type":"disk"},"tmp":{"path":"/tmp","source":"/tmp","type":"disk"}},"name":"ca","stateful":false,"status":"Stopped","status_code":102,"last_used_at":"1969-12-31T19:00:00-05:00"}}
The container you are starting doesn't have any network attached to it.
To create a new network, use: lxc network create
To attach a network to a container, use: lxc network attach
Starting ca
DBUG[06-23|14:15:08] PUT {"action":"start","force":false,"stateful":false,"timeout":-1}
to http://unix.socket/1.0/containers/ca/state
DBUG[06-23|14:15:08] Raw response: {"type":"async","status":"Operation created","status_code":100,"operation":"/1.0/operations/621bd739-d76d-4e15-9295-ce041b6a5193","error_code":0,"error":"","metadata":{"id":"621bd739-d76d-4e15-9295-ce041b6a5193","class":"task","created_at":"2017-06-23T14:15:08.351313528-04:00","updated_at":"2017-06-23T14:15:08.351313528-04:00","status":"Running","status_code":103,"resources":{"containers":["/1.0/containers/ca"]},"metadata":null,"may_cancel":false,"err":""}}

Can you try and reproduce with 2.14?

Marking as incomplete as the report doesn't show any actual error or failure in any of the provided logs or output.

thank brauner, I spun up 2.14 on a test box, ca creates fine on it,and not sure what changed between the versions or caused just ca to not function.   I'll have to update prod, and sorry stgraber, lack of error messages in log, because process never completed.  running lxc start ca never finished or produced anything, and provided all I knew how to find, any other suggestions on debugging/logging would be appreciated, as I pretty much have found all the other errors since I've been playing with lxd the last 9 months

Ah, so it's a hang at startup. That could be our favorite lxc-monitord bug at play.
Can you reproduce this issue reliably or is intermittent? If the latter, it's most likely the monitord isuse. You can unstick "lxc start" in such cases by running "pkill -9 lxc-monitord".
The next LXC release should have this resolved by having us remove the dependency on the monitord code entirely.

Like 99% of the time.  That's what was messing me up.  I thought I was screwing up with my terraform implementation, cause on rare occasion it would work.  But then I dropped to just the basic lxc launch etc, and it failed pretty much every time I tested it, hence why I went to adding as issue.   Even recompiled terraform lxd-provider from github for the latest updates.  And thanks for the kill command, that will save me some copy/paste when I hang an lxc start, which I've done on occasion when my idmap isn't aligned with my subuid/gid settings, but that's another issue, maybe I should add that one too to the list, sorry for the list of issues adding today

Ok, going to close this issue based on the assumption that it's triggering the lxc-monitord issue, this issue was fixed in github.com/lxc/lxc already and the fix will be in the next liblxc release.


🙋 Have feedback? Get in touch!

Hi! 👋 Thanks for your interest in marimo. We're excited you're here as we discover and build the future of Python notebooks — made for humans like you.
We want to hear from you: from minor bug reports or usability issues, to your most hoped-for wishlist features, and everything in between. Here are some ways you can get in touch:

🔨 Bug reports/feature requests: Open a Github issue.
🙋 Help and free-flowing conversation: Hop into our Discord and chat with us in real-time.

Our roadmap
🚗 We have lots we plan to build! Some of our plans are sketched in a public roamdap document.
Have an idea that you'd like to see there? Let us know!

@akshayka FYI the roadmap does not seem to be public, as your link just redirects me to a login page.

Oops! Thanks for letting me know @jonas-w. I've fixed the link.

Hi, developers,
the version 0.1.82 (migration to starlette) is highly unstable on my system (Debian 12, kernel 5.19.0). Nearly all the time there are issues with saving notebook (page freeze) and often Waiting for localhost in browser. I will rather stick with 0.1.81 for now.

Hi, developers, the version 0.1.82 (migration to starlette) is highly unstable on my system (Debian 12, kernel 5.19.0). Nearly all the time there are issues with saving notebook (page freeze) and often Waiting for localhost in browser. I will rather stick with 0.1.81 for now.

Thanks for letting us know. We hit the same issues and yanked 0.1.82 from PyPI. The issue you saw should now be fixed in the latest version of marimo.

@akshayka  Installed 0.1.87 just now, seems to work without above-mentioned issues. I see,  you added --host to CLI, will try tomorrow.  Thanks for rapid response and also rapid development.

#feature_request I would love to see dark mode and also the indentation block highlight (it's a little bit tough to see indentation in the white background)

First of all, thanks for the great work on marimo!
I noticed a few inconveniences:

When there is a bad symbolic link in a directory, this line will lead to an "Internal Server Error". ("Bad" can either be a recursive link (ln -s broken) or a link pointing to a non-existing file (ln -s broken notthere).)
Saving will allow filenames such as "." ".." to be used as regular filenames.

I'm closing this issue — if you have feedback, please get in touch!
🔨 Bug reports/feature requests: Open a Github issue.
🙋 Help, free-flowing conversation: Hop into our Discord and chat with us in real-time.


When the application is switched to the background or the screen is locked, he no longer works

That's mainly a side effect of implementing this at the view layer. Try adding a service bridge: https://medium.com/reactbrasil/how-to-create-an-unstoppable-service-in-react-native-using-headless-js-93656b6fd5d1


Attack Roll bonus adjustment is wrong

e.g. +3 heavy shield bash +21/+10/+5 (1d6+10 plus ) became +3 heavy shield bash +36/+31/+26 (1d6+10 plus )

fixed in 4.0.3


making sure the buttons fit, fixes #991

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
Fixes #991
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
🙈 Screenshots
Large and small screens are happy now

👯♀ Paired with
nobody

I can't think of any solution that would not depend on the lower widget sizes
So this is simple and as good as any other solution
The thing is, I don't want to change the layout, and have to try and test again, possibly break something etc
This fix is non-destructive - this works
The layout fix would be to attach the UX to the bottom - I think? But the top might then overlay the bottom UX... etc
There's no solution that doesn't have some drawbacks
So I figured - we want what we had, except if what we had doesn't work, in which case we make it work


Upgrade Terraform package

Current version is 0.7.13.

Could you make a pull request for this?
The nix expression for terraform looks pretty straightforward, but I am not terribly familiar with this project.

Updated in https://github.com/NixOS/nixpkgs/pull/21139

@joachifm ,@kamilchm:
This doesn't work without weird error messages:
grep: Invalid range end