python310Packages.django-webpack-loader: 1.4.1 -> 1.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.django-webpack-loader is: "Use webpack to generate your static bundles"
meta.homepage for python310Packages.django-webpack-loader is: "https://github.com/owais/django-webpack-loader"
meta.changelog for python310Packages.django-webpack-loader is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.5.0 with grep in /nix/store/l4d3jgdfimj8gmyznka2y29xi4r55yzr-python3.10-django-webpack-loader-1.5.0

found 1.5.0 in filename of file in /nix/store/l4d3jgdfimj8gmyznka2y29xi4r55yzr-python3.10-django-webpack-loader-1.5.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
python310Packages.django-webpack-loader
python39Packages.django-webpack-loader

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l4d3jgdfimj8gmyznka2y29xi4r55yzr-python3.10-django-webpack-loader-1.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.django-webpack-loader https://github.com/r-ryantm/nixpkgs/archive/5d3b9088cb606ea26a5bf70e16f4dd9695225d2b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l4d3jgdfimj8gmyznka2y29xi4r55yzr-python3.10-django-webpack-loader-1.5.0
ls -la /nix/store/l4d3jgdfimj8gmyznka2y29xi4r55yzr-python3.10-django-webpack-loader-1.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.django-webpack-loader
python39Packages.django-webpack-loader

Maintainer pings
cc @peterromfeldhk for testing.

Result of nixpkgs-review pr 167646 run on x86_64-linux 1

2 packages built:

python310Packages.django-webpack-loader
python39Packages.django-webpack-loader


cross compile x86 linux

Merged Tracy's change to cross compile x86 linux
./build.sh --x86 will generate 32bit binary on x86_64 linux

What should be the set of compile flags for our official x86 builds? -msse2, -fpmath=sse. What else?

@RandyShuai can you queue the x86 job so that we know it passes before the PR can be approved? Thanks!

What should be the set of compile flags for our official x86 builds? -msse2, -fpmath=sse. What else?

These should be enough for now.

Sorry, I thought I was closing the comment, not the PR!

I suggest: do not cross compile !
Let's make things simpler. Fetch the 32 bits docker image(https://hub.docker.com/r/i386/ubuntu/), install the 32 bits gcc(gcc.i686). Do all of these things in a pure 32 bits environment.


Multi factor authentication

Add multi factor authentication support for admins & customers

Microsoft MFA
Google 2step verification

This should be a different package because already core is loaded with lots of dependencies.
So if the user needs it, they can integrate it into Bagisto.
The Bagisto core should be simple and basic.

We will discuss this this week during a meeting and provide feedback afterwards


Inviting and tagging people for the "IDS documentation (StarterKit4.0)

Hi @anilturkmayali and @ssteinbuss ,
I can oly add/tag people to the "IDS Documentation" if they are member of the IDSA (here in Git-Hub).
Those who are not member cannot even see the document (as SQS experienced for example).
Do you know, how to fix this? - maybe we need to put the "IDS Documentation" to the main branch? Or do we need to add everyone to the IDSA?
BR,
Natalia

Hi @aliasimon ,
three  different things here:

the repository is public, so everyone is able to see the document. Doesn't matter if in a branch or in the master/main.
to contribute, you require access rights.
to collaborate is easier, if people are member of the IDSA org.

Let's fix this.

Fixed: Use this form to become part of the IDSA organisation on GitHub.


Can't Find Micro-ROS Files

Hello, I saw your example of using Micro ROS on ESP32, I tried to do the same thing but some files are missing I can't find the corresponding file in the Micro-ROS Github repository, what should I do?

Hi! You should tell me the names of the files. My mind reading capabilities are limited this time of the year.

Hello, the documentation tells about setting microros setup before doing anything.
Try to re-clone this repo appending the --recursive option, this should bring the microros repo submodule.

I saw your project about using ESP32+microROS on github, I also want to achieve a similar operation, my development environment is vscode+espidf I created an example of led, then added the micro-ros component and tried to compile, But the compilation can't be completed anyway, could you please guide me?

git clone --recursive xxx     It  works but the micro_ros_espidf_component seems to be incomplete I want to go through the network and not through the serial port How do I do this


Does not support import of other languages or image files

Does not support import of other languages or image files, Waste a lot of time changing text file names and content ,No filenames found in other languages yet

if possible, you can manually import pictures yourself

Hey, I know this issue is pretty old, but could you describe more precisely what you mean by importing other languages & image files. Do you want to be able to change the software’s language? What kind of image files do you want to import and for what purpose?


Server-side rendering

The component currently won't work when rendered server side.
We must investigate what is needed in order to support this.

@nnarhinen and @ondreian Any idea when this would get picked up? We recently added the React component to our Gatsby developer portal site. Everything renders beautifully locally, but not server-side. We were initially getting some build errors on the server:

I contacted Redocly since they host our builds. They were able to fix the build, but instead got this error and pointed me to this issue as the ultimate fix.

@nnarhinen Any chance this could be included as a user story to fix with the React feature for Q3? It would be helpful to be able to include the dev demos on the wowza site especially with Wowza 2.0 and movement of all docs eventually to the wowza docs site.

Offering some insight here as one of your customers and someone who has had to work around this issue.
As the package is not a module the only way to make it work in an SSR (or SSG) environment is to defer its loading to a point in time where a window (or browser) object is present. This can be done using React.lazy for React, next/dynamic in NextJS or onMount() in Svelte. This works very well and should be a recommendation in the docs until the package is a proper module that can be imported as is.
The simplest way is to make a new component which uses Flowplayer from its imports like a wrapper and then import that wrapper-component using one of the methods above. It is of course possible to import the package "as a module" using the same methods but I found it is safer to wrap it (plus that fit our use case much better anyway as we needed to put in our own props into it (styling, callbacks to our API etc.)
In NextJS:
FlowPlayerComponent.tsx
import Flowplayer from '@flowplayer/react-flowplayer';

const FlowPlayerComponent = () => {
  // most code omitted for brevity
   return (
     <Flowplayer
       src=""
       token=""
       ref={}
       opts={{}}
      />
    )
}

export default FlowPlayerComponent

YourOtherComponentWhereYouWantToImportFlowplayer.tsx
import dynamic from 'next/dynamic'

const FlowPlayerComponent = dynamic(() => import('./FlowPlayerComponent'), {
  ssr: false,
});

const YourOtherComponentWhereYouWantToImportFlowplayer = () => {
// most code omitted for brevity
  return (
    // ...
    <FlowPlayerComponent />
    // ...
  )
}

export default YourOtherComponentWhereYouWantToImportFlowplayer


Update TTS export-onnx.py scripts for handling variable token counts

TTS/VITS training examples assume a hardcoded and constant token count of 79 when exporting the output models to onnx. Although this works for these recipes, I think it's better to make these counts variable for users training on different phone sets.

Thanks.


Hard coding of version number

Why is the version number hard coded? See https://github.com/mapbox/variant/blob/master/variant.hpp#L34 and https://github.com/mapbox/variant/blob/master/test/unit.cpp#L34-L42.
/cc @artemp @springmeyer

I added this. Not sure what is wrong with hardcoding - this is being done similar to https://github.com/mapnik/mapnik/blob/master/include/mapnik/version.hpp#L26-L30 (which is done like boost/version.hpp). Do you have ideas for alternative ways?

@springmeyer With hard coding I meant that the comment indicates that it always has to have version 0.1.0 (because only that will result in 100) and the test checks that it has that version. I guess at some point we want to change the version number than the comment will be wrong and the test will fail.

Ah, I see now. Yeah, my assumption is that the comment and test would be updated each time the version is bumped. But I'm open to removing them to avoid drift.


Add Quota policy error on apply

Kyverno Version
helm chart v3.0.0-alpha.2 with default values
Kubernetes Version
1.25.x
Kubernetes Platform
EKS
Description
When applying the policy https://main.kyverno.io/policies/best-practices/add-ns-quota/add-ns-quota/
 getting the error below:

admission webhook "validate-policy.kyverno.svc" denied the request:  path: spec.rules[0].generate..: failed to get the Group Version Resource for kind LimitRange
The policy works well using chart v2.7.2

Cannot reproduce on the same chart version on K8s 1.26.

Cannot reproduce on the same chart version on K8s 1.26.

works for me on 1.26 as well, weird

I also cannot reproduce on K8s 1.25.

I reinstalled it on 1.25 and it worked this time. Weird, might be wrong values. We can close the issue, thanks.


Interpolate template variables into the link to prometheus url.

fixes #389
@grobie outstanding issues with testing directives, so no test, sorry :/

@juliusv quick one

:+1:

Thanks for the fix.


Documenting project decisions

I think in a meeting with @michielbdejong we agreed to record the project decisions in a documents folder next to project files. I feel proud to have put the laravel project in a subfolder when I pushed the initial code!
I think a "doc" or "documents" folder on the root of the repository makes a good fit. And we will need to move the Structure.md and other relevant files into that folder as well.
Then whenever we make a conclusion about a decision like Issue 28, we can include it in that document.
I have no idea for the format to write them down. Like many files or one file or maybe a folder structure. Personally, I think we can start with whatever and then see how we can organize them after we have a bunch of them there.
Also, seems like a good idea that the person who created the issue (or closes it?) will make sure it is documented.
What do you think?

This makes sense. I would start with 1 doc folder and 1 file in it and hope that at some point it will make sense to split it into more files. I would say to check if the issue is documented upon closing so that it has a comment like "closed because of [link]".

I guess it's decided then!


github discussions section

could i request a github discussions section so i can ask silly "how can i do this" questions?

I wouldn't be against this if it would work best for you, but I'd prefer to keep the number of channels of communication to a minimum if possible. Otherwise it makes it more difficult for me to keep on top of things, and makes it difficult for others to know where to look for answers.
My preference would be to use this thread on the JUCE forums for these sorts of discussions: https://forum.juce.com/t/introducing-jive-the-ultimate-juce-extension-for-building-guis/56534
Would that work for you?

yeah thats fine! wasn't too sure what the best form of communication would be so appreciate you clearing that up


valtio should avoid state change for compare equal value

new to valtio, I expected mutate state is like immer with proxy, if assign the same value, the state should not change, but seems not the case.
like
const state = proxy({
  ref: ref(0),
  object: {}
});

// should prevent the rerender if the value is reference equal
state.ref = ref(0)

// should avoid change
state.object = {}

Is it possible to pass the custom comparator or use with immer to prevent the change ?

It should skip setting if it's the same as the previous one. (Compared with Object.is by default.)
For example, this should work as expected.
const state = proxy({ obj: {} })
state.obj = state.obj

But, this doesn't,
state.obj = {}

because it's a new object. This should be the default behavior that we shouldn't change.

state.ref = ref(0)

I don't feel like writing like this, but it should just mean state.ref = 0, which skips changes, no?

Thanks, I expected immer like mutation detect, seems I was wrong, but do hope valtio support custom change compare, valtio already batched mutation.

state.ref = ref(0)

Just use 0 as a reference, due to https://github.com/pmndrs/valtio/issues/510 , the 0 stand for <Comp/> or document.body like value, should use Object.is compare the ref value changed or not to avoid the notify.

I expect it work fine with document.body.
state.ref = ref(document.body)
state.ref = ref(document.body) // should be no-op

btw, we could create a proxy object in advance.
const obj = proxy({ foo: 1 }) // initialize object outside
const state = proxy({ obj })
state.obj = obj // should be no-op

I expected immer like mutation detect, seems I was wrong

As I wrote in a different issue/discussion, valtio is designed like an opposite of immer.

but do hope valtio support custom change compare, valtio already batched mutation.

We do want to avoid adding features in valtio. It's one of the ground rules from the start.
If you need a custom comparator, it should be nice if we can make it possible to it on your end. There's an experimental feature called unstable_geHandler, with which you can specify a function instead of Object.is.
https://github.com/pmndrs/valtio/blob/7c85c1413992a02e7a65e698b803fdef500d008e/src/vanilla.ts#L155
But this feature is not very developer friendly. It's basically for 3rd-party library developers. It means you should be able to create proxyWithCustomComparator util.

Thanks, I will look into it.

Wow, after
import eq from "react-fast-compare";
unstable_getHandler(state).is = eq

valtio works like expected, thanks.
https://codesandbox.io/s/valtio-render-test-lzqhf7
Can close the issue now.

@wenerme When #528 lands, your solution will no longer work, but it will expose a new powerful function, with which you can customize is.

@dai-shi thanks, will watch the release


blobs: Document the submission process

Add the missing piece of documentation for binary blobs: the submission
process. This follows the external source code process relatively close,
but it is relatively simpler.
The proposal includes a new issue template for requesting inclusion of
blob(s) for a particular module.
Fixes #7516.
Signed-off-by: Carles Cufi<EMAIL_ADDRESS>

No objections at the TSC


UART continuous interrupt

Hello,
I'm trying to program simple applicatio where when interrupt on uart rx occure, I just read the input buffer and send it back. My problem is, when i send more than 1 Byte, It stops responding and the interrupt is occuring continuously. In case i send only one byte it is working.
Here is the code:
static void message_test(char *s,uint8_t *data,uint8_t len)
{
        int i;
	printk("%s: ",s);
	for(i = 0; i < len; i++)
	{
		printk("%02x ",data[i]);
	}
	printk("(%u bytes)\n",len);
}
static void uart2_isr()
{
	uart_irq_update(uart2_device);
	if(uart_irq_rx_ready(uart2_device))
	{
		uint8_t len = uart_fifo_read(uart2_device,rx_buffer,BUF_MAXSIZE);
		message_test(_func_,rx_buffer,len);
	}
}
static void uart_init(void)
{
	uart2_device = device_get_binding("UART_2");
	uart_irq_callback_set(uart2_device,uart2_isr);
	uart_irq_rx_enable(uart2_device);
}

I tried to code it using example nfc_hello, but there is no uart_irq_update funcion used, if I understood it correctly it is necessary as it is written in documentation.

Best Regards
Michal Hudec

Please see if https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/subsys/console/echo/src/main.c would give some ideas/insight.

What hardware/platform are you seeing this on?

stm discovery f3

I tried to done it more ways, but with the same result. The uart_fifo_read() returns whole message I send on uart? For ex. if I send 4 bytes, uart_fifo_read() returns 4 and put those four bytes in buffer? Because this not working for me, I only get 2 bytes shown from 4 and then continouos interrupt....
@pfalcon -> I  tried to implemet it like in getchar.c but with the same result. In the final, I need to implement modbus rtu protocol, but only way what uart is now working is polling....

Hi,
Can you try with following fix?
https://github.com/zephyrproject-rtos/zephyr/pull/5299
Erwan
On 12 December 2017 at 11:21, mhudec1<EMAIL_ADDRESS>wrote:

I tried to done it more ways, but with the same result. The
uart_fifo_read() returns whole message I send on uart? For ex. if I send 4
bytes, uart_fifo_read() returns 4 and put those four bytes in buffer?
Because this not working for me, I only get 2 bytes shown from 4 and then
continouos interrupt....
@pfalcon https://github.com/pfalcon -> I tried to implemet it like in
getchar.c but with the same result. In the final, I need to implement
modbus rtu protocol, but only way what uart is now working is polling....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zephyrproject-rtos/zephyr/issues/5244#issuecomment-351008434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARtr5IpaDIJcVodCv-0RwArQUuiCRZBzks5s_lOOgaJpZM4Qz1ct
.

is this already fixed?


Swipe and status bar issue

Hello.  This works very nice. Have two questions.

How to include status bar?
When start swipe it shows background color not content of react component i want to swipe. Any chance to fix it?
Cheers.

https://github.com/benevbright/react-navigation-collapsible

https://github.com/benevbright/react-navigation-collapsible
@Jalson1982

he has more issues then your solution hehe

There is a prop to render, prerenderingSiblingsNumber
Because of collapsing toolbarits not working

So prerenderingSiblingsNumber can not use to have both components render and avoid white screen when swipe?

Hello,
Native base has introduced this feature,
https://codeburst.io/react-native-parallax-scroll-with-tabs-721feec463c5
<EMAIL_ADDRESS>

https://github.com/GeekyAnts/NativeBase/tree/master/src/basic/Tabs,


Added changes made for Eventing only

Changed
I made this branch for splitting this PR: https://github.com/boomerang-io/flow.service.workflow/pull/210
This branch contains the changes related to Eventing. However, this branch should be merged after this one: 'feature/generalFixes'

@AndreiOla @corcoja @gchickma some of the eventing changes have been cherry-picked to the new engine and updated to use the new WorkflowRun and TaskRun concepts.

Hey @tlawrie, this is cool! I've noticed it is the simplified version o eventing though (I quickly looked at it so I might be wrong) – let me know if you want at any point in the future if you want to advance the development on this 😊

Hey @corcoja I'm actually thinking of a slight change to the eventing architecture. Following on from how tekton / knative etc do event sinks, I'm thinking that we actually move the eventing that contains the NATs integration into a separate service.
That way, the workflow service is just accepting events and firing events, and another service is set up as the sink and it handles putting it on NATs or any cloud services from Azure / Google / etc.
This keeps the code base clean and extensible.
What are your thoughts?

Hey @tlawrie I started extracting the NATS part out of the CE Service, but for a different reason. Currently the EventingService tries to connect to a NATS server and there is no way to disable this. So, in order to disable just the NATS part, I put the code in a different service.
Please take a look and, if it seems right, I can port the changes to this branch also.
https://github.com/boomerang-io/flow.service.workflow/commit/e359205f5ca8693095aa88afeff6b49898707e86

@tlawrie, this definitely is an improvement over current architecture. Quick question though, when you say service, do you mean a Spring Boot service or a standalone java µS? On the later, my only worry is the timeline these changes can be implement, since extracting code and putting it in a new, dedicated µS, usually takes time to build and test.
But I'm happy to hear that @AndreiOla has already made some progress on this.

Hi @AndreiOla @corcoja w.r.t to the word 'service', i mean a different standalone microservice.
*V4 Microservice Architecture

the Listener service is no longer and just an API endpoint on the Workflow service.
the Workflow service no longer handles the events related to WorkflowRuns and TaskRuns, this has moved to the Engine service which owns the data entities
the Engine service fires CloudEvents blindly to 0..n event sink URLs
the Controller (soon to be TektonHandler) service is just one event sink

Proposal
I propose that for Eventing, any implementation specific details for NATs are moved to a separate microservice (NATSHandler) or alternatively DAPR is used (ill circle back to this option).
The NATSHandler would allow the service to receive the events for WorkflowRun and TaskRun and do with them as it pleases. Additionally, the domain separation of concerns would allow this eventing microservice to have its own lifecycle separate to Engine.
DAPR Sink
An alternative to your own microservice for NATS would be to use DAPR as a sidecar and that way a sink url would be localhost (in the container) which is picked up by DAPR.
This would allow support outside of NATS and allow additional event systems (i.e. allow IBM in the future to use a Cloud based event service and not have to maintain NATS). Reference
Questions

Are there additional events besides WorkflowRun and TaskRun?

cc: @gchickma

@tlawrie I agree that for V4, there should be a Broker pattern implemented or something similar (where you can publish CEs and consume them just by plugging-in a message system - NATS in our case), but for the already developed code in the current v3, I would keep things consistent (use the 'internal' services for CEs and NATS being plugged-in using Aspects and a property for enable/disable). I already extracted the NATS related code (in workflow service. There is also lib.eventing that would need refactoring), so it can be put later in a microservice. Refactoring and re testing this code, would take a lot of time and it won't be entirely reusable in v4 anyway, so it has very short life.

I'm fine if that's the aim, to get it merged in for v3 (and also not break when Eventing is disabled)
I wanted to highlight that the code will be immediately lost on the v4 branch of workflow and not be used. - In current state. The code is already being ported for producing the events
Do we want to bother with v3 and focus on making it work with v4?

As migrating to v4 will take some changes and as we already spent time in developing this code, I would like to merge this in v3 and make it better in v4.

@tlawrie @corcoja @amhudson Please review these changes.

@corcoja I am not sure to which APIs you are referring. There are already some tests there.

@corcoja I am not sure to which APIs you are referring. There are already some tests there.

Integration tests for controller methods that use CloudEventsService, e. g. acceptEvent(...) inside InternalController. Mock with Mockito any other intermediary services that are used by this method, this way you'll be testing just the functionality of acceptEvent(...).
The tests that you mentioned are solely for testing the CloudEvents payloads, there are no integration tests afaik.

@corcoja @amhudson @tlawrie I added some Tests. Please review the changes, so I can merge this branch in v3.

Ill defer this to @gchickma and @amhudson for an IBM approval.
v4 has already been forked and is nearing completion with a different eventing implementation - refer to comment

@amhudson @gchickma Please find time and review, so I can merge this code


Add Zig Zag Conversion

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
Fixes #364
Fill up the DCP form
If you are a part of DCP 21, fill up this form after the PR is merged.
The links provided in the form will be checked thoroughly, if someone tries fooling around, strict actions will be taken against the individual.

@smv199 Made the required changes.


Fix infinite loops when reloading observed fragments

Currently in certain annoying cases in Ember, including aliases or proxies that are actively observed,
CPs are consumed as soon as they are changed. This used to cause an infinite loop. For example:
If you had
  App.User = DS.Model.extend({
    name: hasOneFragment('name')
  })

  App.Name = DS.ModelFragment.extend({
    firstName: DS.attr()
  })

We would push new data for a user
We would notify a change for the user.name which cleared the fragments cache
An observer would try to get user.name.firstName synchronously
As we had new data, we would try to setupData on the fragment
In the middle of fragment data setup we would notify a change to firstName
The observer would fire immediately and try to get user.name.firstName even though
we weren't done with the setup
Goto 4

We now cache the fragment early enough to prevent this infinite loop

Looks like this was originally avoided by using that Ember.beforeObserver on the data attribute, which always made me queasy. Thanks for your help sorting out these edge cases :+1:
I'll do a bugfix release immediately unless you're aware of any other issues with the current build.

Haven't noticed any other issues at the moment. App test suite passes with 0.2.7 with the above fix

In v0.2.8


Document node 18 dependecies

Suggestion
We bumped node from 16 to 18 in what will be .73. We need to make sure we update our documentation to include this dependency
Location
https://microsoft.github.io/react-native-windows/docs/rnw-dependencies

Current instructions don't specify a version of Node. But it should match what the script does, which chooses an explicit version.


Undump

CLI

Flag for updating, or skipping documents with same iuid.
Flag for adding indexes.

Done, via CLI dump and load.


Z order and aspect ratio

The Z order of vertices in the example file is inverted, unlike in the screenshots in the repo:

Additionally, the rendering aspect ratio is incorrectly set: squares appear as rectangles:

Rotated 90 ° to the right:

Tested on the latest version of LÖVE.

Aspect ratio problem is fixed, and you can change your own aspect ratio by modifying line 50 of camera.lua, or doing something like this:
Camera.aspectRatio = some number
CameraShader:send("projectionMatrix", GetProjectionMatrix(Camera.fov, Camera.nearClip, Camera.farClip, Camera.aspectRatio))

Your Z ordering problem seems to be specific to your situation, I'm unsure of the solution and have not encountered the same problems with others. You can however set the depth mode to try to fix this issue, g3d by default initializes the depth mode as such: love.graphics.setDepthMode("lequal", true)
Hope that helps, I'm now closing this issue.

Thanks for fixing the aspect ratio, but the second problem still persists. I have tried all values for setDepthMode, but it has no effect.
It also persists for the new example:

I was a bit imprecise - the Z order isn't simply inverted, it almost seems simply ignored. Objects are drawn in front of each other regardless of their distance from the camera


random length strings within range

at a high level, I have added  randomGraph( int count ) and randomPrint( int count ) which map to their corresponding regular expression classes. These are useful if you're needing to test arbitrary user input in various kinds of text fields. randomAscii was not sufficient due to it's inclusion of the DEL character.
I have also added variants of random Ascii, graph, print, alphabetic, alphanumeric, and numeric that have  minimumInclusive and maximumInclusive parameters. These can be used to create string of random length to ensure more random distribution of data when testing. The will also ensure that developers who use them are less likely to forget testing variable lengths within the bounds.

#94, #100 and #101 are useful for generating random data for (for example) testing. I thought about suggesting these methods to the incubating [text] component; but on second thought, I think it could be better to have these features in a separate component.
Just food for thought, but maybe something like a commons for testing, like https://github.com/andygibson/datafactory, but also including general code for helping Java developers to write test.

I think the added randomGraph( count ) and randomPrint( count ) might be ok to stay here, since they resemble the existing methods so much. I can see putting the ranged variants somewhere else, I'm not sure if they're only useful for testing, that's just what I've used them for (well that and dumby output for creating new vaadin components).
Willing to move things if that decision is made.

+1 I would like to use these methods :)

https://bitbucket.org/xenworks/datafactory/src/ I've started work on a "replacement" for datafactory and this here, feedback welcome

I still think these methods should be added to commons-lang. They are a very useful extensions of RandomStringUtils feature set.
I created https://issues.apache.org/jira/browse/LANG-1224 and https://issues.apache.org/jira/browse/LANG-1225 to track them.

To quote Gary Gregory from https://issues.apache.org/jira/browse/LANG-1224

It seems really confusing that some new APIs would use an inclusive max while existing APIs use an exclusive max.

Current APIs with exclusive max:
random(int, int, int, boolean, boolean)
random(int, int, int, boolean, boolean, char...)
random(int, int, int, boolean, boolean, char[], Random)

So for the sake of consistency with the existing methods and the java random api, an exclusive max should be used.

Thanks!


Send array of data to client, render entire table client side.

Main changes:

removed puzzle table HTML generation from server side. Instead, we just ship an array of data to the client, do all table rendering using JavaScript client-side. Data transferred reduced from 1.1 MB to 130 KB. Load time is now about 2 seconds on Heroku:

removed column-specific search boxes

removed "Enter Guess" column, combined with "Answer" column, added new "Submit Answer" modal:

made editing Status an on-demand modal:

fixed bugs where modals weren't working when table was redrawn (e.g., on paging or filtering)

increase default page size from 25 to 50

reverted jquery datatables changes in https://github.com/cardinalitypuzzles/smallboard/pull/113/commits/bb6c55738556e5fdfe316fe1cc4e0cb34855e8e2 since they broke datatables searching

Screenshot:

For #114.

Fixed the Answer Queue page. Removed the edit and delete puzzle functionality from the page.

For now, I didn't optimize the answer queue page (all the HTML is still generated server-side). Will optimize it in a follow-up PR.


Check the usage of kotlin-stdlib dependency

Description:
Check the usage of kotlin-stdlib dependency as there is a medium severity CVE in the current version.

Where do we use this dependency?

We can remove it.

I think it's being used transitively in the HTTP client library okhttp3 we are using in CentralClient. Manually removing this from bre lib caused CNF for a kotlin class when trying to run bal build.
[2021-12-01 13:48:05,050] SEVERE {b7a.log.crash} - kotlin/TypeCastException
java.lang.NoClassDefFoundError: kotlin/TypeCastException
	at okhttp3.ResponseBody.create(ResponseBody.java:214)
	at okhttp3.internal.Util.<clinit>(Util.java:69)
	at okhttp3.OkHttpClient.<clinit>(OkHttpClient.java:124)
	at okhttp3.OkHttpClient$Builder.<init>(OkHttpClient.java:449)
	at org.ballerinalang.central.client.CentralAPIClient.getClient(CentralAPIClient.java:841)

@azinneera Thanks for the input. Because of this issue, I sent PR bumping the kotlin-stdlib version to a non-vulnerable one. https://github.com/ballerina-platform/ballerina-lang/pull/34080


'Link' cannot be used as a JSX component.

Erro: 'Link' cannot be used as a JSX component.
Its type 'typeof Link' is not a valid JSX element type.ts(2786)
I'm having a problem using the Link.
Version I'm using:
"react-scroll": "^1.9.0",
"next": "13.4.5",
"react": "^18.2.0",
"react-dom": "18.2.0",
"@types/react": "18.2.12",
"@types/react-scroll": "^1.8.7",
I would like some help to resolve this issue. It works correctly. but it is giving build error in vercel

I am also facing a similar issue:

Same problem here with react 18.2.0.
Also tried to enforce the version by using "resolutions" field but no success.

I experienced same problem when I upgraded react from 16.14.0 to 18.2.0

Same problem
react: 18.2.0
react-scroll: 1.9.0

any resolutions yet for this?

I resolved problem by using @types/react 18.2.3.
I experienced same problem when I upgraded react from 18.2.3 to 18.2.46.

I resolved problem by using @types/react 18.2.3.
I experienced same problem when I upgraded @types/react from 18.2.3 to 18.2.46.

same problem using 18.2.3 :(

I have same issue.
Do you have any update?

I also have this issue. Does anyone have any updates?

Hey!
I got the same error too.
I saw at my package.json that my @types/react-scroll was not install as DevDependency, after remove it from the dependency, and installed as -D, the error gone :)
  "dependencies": {
   "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "react-scroll": "^1.9.0",
  }

  "devDependencies": {
    "@types/react": "^19.0.1",
    "@types/react-dom": "^19.0.2",
    "@types/react-scroll": "^1.8.10",
  }


[Patch 1.1.x] Leaking Windows Auth handles/memory

#317
32bc9a5

https://github.com/aspnet/HttpSysServer/issues/330

This patch fix is approved. Please follow the normal code review / pull request process and make sure you make the change in the correct branch.

This patch fix is approved. Please follow the normal code review / pull request process and make sure you make the change in the correct branch.

Preview builds of this patch fix should be available on the following feeds:

https://dotnet.myget.org/gallery/aspnet-1-0-5-may2017-patch-public (for fixes in the 1.0.x release)

Feed URL to add to NuGet.config: https://dotnet.myget.org/F/aspnet-1-0-5-may2017-patch-public/api/v3/index.json

https://dotnet.myget.org/gallery/aspnet-1-1-2-may2017-patch-public (for fixes in the 1.1.x release)

Feed URL to add to NuGet.config: https://dotnet.myget.org/F/aspnet-1-1-2-may2017-patch-public/api/v3/index.json

If you have a chance, please try out these preview builds and let us know if you have any feedback!


Does NOT work on Mojave Mac

By editing the " ssb-interop.js" file per the instructions the main chat window stays white in MacOS Mojave.
Note: I used "One Dark" which uses:
"--primary: #61AFEF;
--text: #ABB2BF;
--background: #282C34;
--background-elevated: #3B4048;"
Below is the code I used in ssb-interop.js
// First make sure the wrapper app is loaded
document.addEventListener("DOMContentLoaded", function() {
// Then get its webviews
let webviews = document.querySelectorAll(".TeamView webview");
// Fetch our CSS in parallel ahead of time
const cssPath = 'https://cdn.rawgit.com/widget-/slack-black-theme/master/custom.css';
let cssPromise = fetch(cssPath).then(response => response.text());
let customCustomCSS =
:root {
/* Modify these to change your theme colors: */
--primary: #61AFEF;
--text: #ABB2BF;
--background: #282C34;
--background-elevated: #3B4048;
}
// Insert a style tag into the wrapper view
cssPromise.then(css => {
let s = document.createElement('style');
s.type = 'text/css';
s.innerHTML = css + customCustomCSS;
document.head.appendChild(s);
});
// Wait for each webview to load
webviews.forEach(webview => {
webview.addEventListener('ipc-message', message => {
if (message.channel == 'didFinishLoading')
// Finally add the CSS into the webview
cssPromise.then(css => {
let script =                       let s = document.createElement('style');                      s.type = 'text/css';                      s.id = 'slack-custom-css';                      s.innerHTML = \${css + customCustomCSS}`;
document.head.appendChild(s);
`
webview.executeJavaScript(script);
})
});
});
});

Yeah it’s broken - the other dark mode from the other author works but it doesn’t look right.

@GodofWar9000  I found a work around for my theme, might help you - https://github.com/widget-/slack-black-theme/issues/62#issuecomment-410256441

@GodofWar9000 I found a work around for my theme, might help you - #62 (comment)

it didn't work

@RyanPWalker's referenced fix worked for me on Mojave.


better status codes on errors resolves #200

Introduction
This PR aims at providing better status codes when errors in the backend occur.

[x] The buildserver is happy.
[x] The PR is rebased with current master.

Checklist

[ ] I added unit tests for my code
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added code comments, logging, and assertions as appropriate
[ ] I mentioned every code not directly written by me in reuse syntax

Review

[ ] Documentation is conforming to our Documentation Guidelines
[ ] Examples are well chosen and understandable
[ ] Code is conforming to our Coding Guidelines
[ ] Code is consistent to our Design Decisions

If everthing is fine, I will merge it directly into master and merge my branch with that.


Hi, David

Nice code, exactly what we 're looking for. Do you like to cooperate with us? We have plans. We basically deploy as many Kurento nodes as needed - on ordinary CPU shares rather than AWS, etc. Join the club - there's pretty much free space now.

Nice code, exactly what we 're looking for. Do you like to cooperate with us? We have plans. We basically deploy as many Kurento nodes as needed - on ordinary CPU shares rather than AWS, etc. Join the club - there's pretty much free space now.

Hi

Nice code, exactly what we 're looking for. Do you like to cooperate with us? We have plans. We basically deploy as many Kurento nodes as needed - on ordinary CPU shares rather than AWS, etc. Join the club - there's pretty much free space now.

Hello, it's good that it was useful to you, I would like to join the club, sorry for the delay in responding, if there is still time and you have plans, I would like to help

Hi, David, I'm leader of the team working on Room-House software. My name is Alex. Room-House is a very ambitios project. It needs talented programmers.
Currently thre is a task: use 3D javascript library "three.js" in Room-House  - can see an example at https://milan.room-house.com/#PHOENIX
Basically if you feel like it we can talk on. So far, thanks for replying. Have a nice time and Happy New Year. Feliz Ano Nuevo!
On Sat, Dec 30, 2023 at 08:37:25AM -0800, Davidc2525 wrote:

Nice code, exactly what we 're looking for. Do you like to cooperate with us? We have plans. We basically deploy as many Kurento nodes as needed - on ordinary CPU shares rather than AWS, etc. Join the club - there's pretty much free space now.

Hello, it's good that it was useful to you, I would like to join the club, sorry for the delay in responding, if there is still time and you have plans, I would like to help
--
Reply to this email directly or view it on GitHub:
https://github.com/Davidc2525/OrchiLiveStreamingClustered/issues/2#issuecomment-1872561341
You are receiving this because you authored the thread.
Message ID: @.***>

Hello, a pleasure. What does the project being presented consist of? We can
be in contact via WhatsApp to have better communication, this is my number
+584126005898. Yes, I would be interested in entering as a programmer.
Happy New Year for you too.
DAVID
El mar, 2 ene 2024 a las 8:35, Alex Shevlaquov @.***>)
escribió:

Hi, David, I'm leader of the team working on Room-House software. My name
is Alex. Room-House is a very ambitios project. It needs talented
programmers.
Currently thre is a task: use 3D javascript library "three.js" in
Room-House - can see an example at https://milan.room-house.com/#PHOENIX
Basically if you feel like it we can talk on. So far, thanks for replying.
Have a nice time and Happy New Year. Feliz Ano Nuevo!
On Sat, Dec 30, 2023 at 08:37:25AM -0800, Davidc2525 wrote:

Nice code, exactly what we 're looking for. Do you like to cooperate
with us? We have plans. We basically deploy as many Kurento nodes as needed

on ordinary CPU shares rather than AWS, etc. Join the club - there's
pretty much free space now.

Hello, it's good that it was useful to you, I would like to join the
club, sorry for the delay in responding, if there is still time and you
have plans, I would like to help
--
Reply to this email directly or view it on GitHub:

https://github.com/Davidc2525/OrchiLiveStreamingClustered/issues/2#issuecomment-1872561341

You are receiving this because you authored the thread.
Message ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Davidc2525/OrchiLiveStreamingClustered/issues/2#issuecomment-1873973151,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADX54PXLXQ2G2QR3O7LSURLYMP5HLAVCNFSM422WL6IKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGM4TOMZRGUYQ
.
You are receiving this because you commented.Message ID:
@.***>


[W5.10h][W13-A2] Aadyaa Maddi

Added more use cases for the AddressBook in the Developer Guide.

@amad-person
Some comments added. Please ack & close the PR after reading comments.

Acknowledged, thanks


Small fixes for Python3 environments

Pre-load libc in memory.py to avoid race-conditions on unclean shutdowns in Python3, eg.:

ImportError: sys.meta_path is None, Python is likely shutting down

Use filter_ordered instead of list(set(...)) during parameter derivation in operator.py (the former is deterministic, the latter is not).

yes, go ahead

Ok, merging now, as it fixes non-deterministic travis failures in other branches.


No compile error thrown when this referenced before call to super completes

TypeScript Version:
1.8.9
Code
JSFiddle: https://jsfiddle.net/kitsonk/fs9t96ep/
TS Playground: http://goo.gl/X7cgvV
class A {
    constructor(fn: () => void) {
        fn.call(this);
    }
    foo: string = 'foo';
}

class B extends A {
    constructor() {
        super(() => {
            console.log(this);
        });
    }
    bar: string = 'bar';
}

const b = new B();

Expected behavior:
Typescript should guard against the use of this as the call to super has not completed. Thus it should not compile.
Actual behavior:
Typescript compiles this successfully. It works fine when the target is set to es5 but breaks the browser when target is set to es6.
Error is: VM89:55 Uncaught ReferenceError: this is not defined

This code isn't necessarily invalid -- it's entirely possible (i.e. we can't see its implementation) that the super constructor doesn't invoke the method immediately, in which case this would be valid to access at a later date.

@RyanCavanaugh the ES6 code:
class A {
	constructor(fn) {
		fn.call(this);
    this.foo = 'foo';
	}
}

class B extends A {
	constructor() {
		super(() => {
			console.log(this);
		});
    this.bar = 'bar';
	}
}

const b = new B();

Fails in Chrome with:
Uncaught ReferenceError: this is not defined

And in Edge:
SCRIPT5113: Use before declaration

And Firefox:
ReferenceError: |this| used uninitialized in arrow function in class constructor

It is because it is a lambda function and therefore it is trying to access the lexical this, which isn't available until after super completes, irrespective of what is actually in the super constructor.  Therefore, you cannot use lambda function as arguments of a super call if they reference this in ES6 (or all 3 browser manufactures have mis-implemented the spec).

This works for me in Chrome?

class A {
    constructor(fn) {
       this.foo = 'foo';
       this.print = fn;
    }
}

class B extends A {
    constructor() {
        super(() => {
            console.log(this.bar);
        });
        this.bar = 'bar';
    }
}

const b = new B();
console.log(b.foo);
b.print();

Hmmm... wow, ok, I can break it again if I call it within the constructor:
class A {
    constructor(fn) {
       this.foo = 'foo';
       this.print = fn;
       fn();
    }
}

class B extends A {
    constructor() {
        super(() => {
            console.log(this.bar);
        });
        this.bar = 'bar';
    }
}

const b = new B();
console.log(b.foo);
b.print();

The specific use case that @Tomdye and I ran into was a situation where we were extending Promise and passing in a lambda function as the executor, which gets invoked immediately.  So we were going merrily along, targeting ES5 and then when we tried to target ES6, it broke.
But that is really difficult to guard against, I suspect.

@bryanforbes just suggest that given:
class B extends A {
	constructor() {
		super(() => {
			console.log(this);
		});
	}
	bar: string = 'bar';
}

If the emit was:
var B = (function (_super) {
    __extends(B, _super);
    function B() {
        var _this;
        _super.call(this, function () {
            console.log(_this);
        });
        _this = this;
        this.bar = 'bar';
    }
    return B;
}(A));

Then the runtime behaviour of ES5 would match ES6.

That seems like a good solution, though I'm slightly afraid of breaking existing working code.

It will only break code that's invalid ES6 in the first place though. If they were ever to try setting the compile target to 'es6' they would see this error at runtime. Must be better to catch it at compile time now rather than down the line should they choose to compile to 'es6' at a later date.

The problem is we won't be catching at compile time -- people will upgrade to the next TypeScript version, recompile to ES5, and their code will start breaking at runtime with some very confusing errors and emit that looks like a bug.

Yes, agreed.  It is clearly a breaking change, but one that preserves the runtime semantics.  Maybe there is room for a linter to flag uses of lexical this within the scope of a super call (@adidahiya), since it could be uninitialized?

Accepting PRs once the new transform-based emitter merges. Warning, this is likely a difficult change.

Just a note on this, the emit in master (TS 2.1) now breaks these examples in ES5 at run-time, so this now has parity.  It still does not warn you that it is invalid.
Given:
class A {
    constructor(fn: () => void) {
        fn.call(this);
    }
    foo: string = 'foo';
}

class B extends A {
    constructor() {
        super(() => {
            console.log(this);
        });
    }
    bar: string = 'bar';
}

The emit is...
Version 2.1.0-dev.20161103
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var A = (function () {
    function A(fn) {
        this.foo = 'foo';
        fn.call(this);
    }
    return A;
}());
var B = (function (_super) {
    __extends(B, _super);
    function B() {
        var _this = _super.call(this, function () {
            console.log(_this);
        }) || this;
        _this.bar = 'bar';
        return _this;
    }
    return B;
}(A));

Version 2.0.6
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var A = (function () {
    function A(fn) {
        this.foo = 'foo';
        fn.call(this);
    }
    return A;
}());
var B = (function (_super) {
    __extends(B, _super);
    function B() {
        var _this = this;
        _super.call(this, function () {
            console.log(_this);
        });
        this.bar = 'bar';
    }
    return B;
}(A));

One more case (https://gist.github.com/zemlanin/a306e8498d05c923cac405c047014029):
// this.ts
class A {
    constructor(protected cb: () => void) { }
}

class Greeter extends A {
    constructor() {
        // ^ there should be `var _this = this;`
        super(() => { this })
    }
}

// compiled_with_ts2_0_10.js
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var A = (function () {
    function A(cb) {
        this.cb = cb;
    }
    return A;
}());
var Greeter = (function (_super) {
    __extends(Greeter, _super);
    function Greeter() {
        var _this = this;
        // ^ there should be `var _this = this;`
        _super.call(this, function () { _this; });
    }
    return Greeter;
}(A));

// compiled_with_ts2_1_1.js
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};
var A = (function () {
    function A(cb) {
        this.cb = cb;
    }
    return A;
}());
var Greeter = (function (_super) {
    __extends(Greeter, _super);
    function Greeter() {
        return
        // ^ there should be `var _this = this;`
        _super.call(this, function () { _this; }) || this;
    }
    return Greeter;
}(A));

I've also found this with creating an arrow function before calling super.
class Foo extends Object {
    public constructor() {
        const test = () => {
            console.log(this);
        };
        test();
        super();
    }
}

You can see here that we the output has var _this = this; which shouldn't be valid


Automatically sign iOS projects with no provisioning profile

A quality of life nice to have. Sibling to #7863.
https://github.com/fastlane/fastlane/tree/master/sigh
This thing is worth exploring.

To ephemerally make use of a development team while running flutter run, it would be as simple as adding a DEVELOPMENT_TEAM line to our mac.dart's buildXcodeProject or add it into our ios/Flutter/Generated.xcconfig.
This has the huge benefit of letting people check in open source projects and letting different contributors test on their own physical devices using different provisioning without messing with checked in files.
I'll figure out how to extract the team ID from their keychain.
It also has the advantage of being able to provide more contextual help to users

No certificates at all? Open Xcode->Preferences->Accounts, sign in, follow instructions
Certificates A present? Offer prompt 'Do you want to use your Team X's profile to sign this app for device deploy?' (save their choice semi-persistently somewhere outside of source control)

security find-identity -p codesigning -v is close and doesn't need sudo, though it only returns the alias and its SHA but not the organizational unit

Seems like the tool finds certificates but doesn't 'read' them.
So it'll have to be
security find-identity -p codesigning -v to find the valid ones on the computer. Let the user choose one if there are more than one.
Then security find-certificate -c (the one the user picked) -p | openssl x509 -text and then read the OU out of the output.
None of this needs sudo and is available on a fresh macosx.
keytool also works but needs java.
@cbracken any thoughts? Otherwise I'll do it as described

Upping priority because it's annoying, checking in the development team into source control is unclean and is a bad first use experience forcing users into xcode.

Step 2 - Show a prompt to the user in case there are multiple available
Step 3 - Save the choice somewhere so we don't need to go find it and potentially ask it every time


grt: shuffle congestion markers for better visualization on gui

Fix https://github.com/The-OpenROAD-Project/OpenROAD/issues/6386

grt.congestion7.tcl (Failed)


Add IntField, LongField, FloatField and DoubleField

This commit adds new IndexableFields that index both points and doc values at once.
Closes #11199

I like the idea too. Make the .document API simpler for typical use-cases! I added a couple cosmetic comments.

What if we always set the docvalue type to SORTED_NUMERIC, even if the user is just storing single values? Lucene will optimize the storage if all docs are single-valued, and it's already a common pattern to look for this optimization on read

This sounds good to me. The main issue I see with this is that our default SortFields fail if the field is indexed with multi-valued doc values. But maybe we could make it more lenient and sort on the min value for ascending sorts and max values for descending sorts.

Thanks all for the reviews!

This sounds good to me. The main issue I see with this is that our default SortFields fail if the field is indexed with multi-valued doc values. But maybe we could make it more lenient and sort on the min value for ascending sorts and max values for descending sorts.

I noticed this issue while I was running the sorting tests, maybe we can tackle this in a follow up PR? This one is getting big already, but I'm open to suggestions.

Absolutely, adding support for multivalued fields to default sort fields would be a big change too.

maybe we can tackle this in a follow up PR?

+1

There is already SortedSetSortField and SortedNumericSortField that do this. So I don't understand why it would be a big change? Maybe just add some sugar (e.g. newSortField or similar)

Good point. I was thinking of making changes to SortField but adding factory methods to these Field classes feels like a better approach to me.

OK, well maybe defer it if we have options. I haven't thought about the SortField approach, maybe it could be more natural that way.

I just found an issue with this PR which is that multi-valued floats and doubles are encoded with Double#doubleToLongBits while they should use NumericUtil#doubleToSortableLong to present ordering within a document.
One way to fix it would be to change the encoding depending on whether the field is multi-valued, but this isn't great as we then also need to pass this flag to factor methods for queries (or sort fields in the future). So maybe we should go with @rmuir's earlier suggestion of only supporting multi-valued fields, so that there is a single encoding in doc values?

@fcofdez I hope you don't mind but I checked out your branch to look into the above issue and ended up pushing my changes. These new fields not only support indexing sorted numeric doc values, so that queries do not have to specify whether floats/doubles are indexed via their raw bits or as sortable ints/longs.

@jpountz thanks for looking into this, unfortunately I didn't have time to go through the last round of review comments. The change makes sense to me.

Thanks for having a look @fcofdez. I plan on merging this PR soon if there are no objections.

I cut over the NYC taxis benchmark to these new fields and it yielded a small but consistent speedup. https://home.apache.org/~mikemccand/lucenebench/sparseResults.html#index_throughput


Rewrite installation instructions

Motivation and Context

installation instructions were really long and hard to follow
i replaced them with a script which downloads everything you need
we should just point people to that

Changelog

moves content into docs/install_workstation.md and points them to script instead

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] I ran tests/hw_manual_test.py on hardware and observed that robot behavior looks normal.

In the install script, the habitat-lab in src/third_party/habitat-lab submodule will need to be pulled before attempting to habitat-lab and habitat-baseline python packages.

Faced some dependency issues while running eval_episode.py.

Got the error AttributeError: module 'PIL.Image' has no attribute 'LINEAR' , I tried downgrading the Pillow package version to v7.1, which solved this.
Further getting the error ModuleNotFoundError: No module named 'centernet', centernet package which is a dependency wasn't installed.

Other than the above pointed issues, everything works fine

@hello-fazil I don't get the same Pillow error as you with a clean install, but I think everything else is fixed. For the Pillow error - if we see it again lets try to track it down?

Yes sure, that sounds good.

Faced some dependency issues while running eval_episode.py.

Got the error AttributeError: module 'PIL.Image' has no attribute 'LINEAR' , I tried downgrading the Pillow package version to v7.1, which solved this.
Further getting the error ModuleNotFoundError: No module named 'centernet', centernet package which is a dependency wasn't installed.

Other than the above pointed issues, everything works fine

I also meet second problem, I am wondering how to fix the dependency problem.

Faced some dependency issues while running eval_episode.py.
* Got the error `AttributeError: module 'PIL.Image' has no attribute 'LINEAR' `, I tried downgrading the Pillow package version to v7.1, which solved this.

* Further getting the error `ModuleNotFoundError: No module named 'centernet'`, centernet package which is a dependency wasn't installed.

Other than the above pointed issues, everything works fine

@hello-fazil Hi I ran into the same problem ModuleNotFoundError: No module named 'centernet' when running eval_baselines_agent.py, how did you fix that problem?

Hi! I am also getting the error ModuleNotFoundError: No module named 'centernet'. Would really appreciate some help regarding this issue!

Hi @Eason-S @eyucherin I ended up Installing centernet from source induvidually.


fix(select): add error state SVG and reposition chevron

Closes #1755
Part of #1535
This PR adds the experimental error state to the select component

cc @laurenmrice if you have a chance to do a design review!

Is there a focused invalid state? I'm not sure what the focus state is supposed to look like for the invalid states but I think I addressed the other points @laurenmrice. Let me know if I missed something

regarding your last point @laurenmrice, does that mean the position of the warning icons will vary depending on the length of the text? (I'm assuming you are referring to the warning icons and not the chevrons)

@emyarod Yes for the Inline select, the position of the icons will vary based on the length of text. (icon will be 8 px/.5 rem away from the text). 8px/.5 rem will also be the space between the warning icon and the chevron.

if I'm not mistaken, dynamically positioning the icon based on text length would create a performance bottleneck when the component is rendered unless we write invalid markup and undo the fixes from https://github.com/IBM/carbon-components/pull/1846. Do you know of any example implementations of this pattern? I'm leaning towards keeping the current positioning but I'll see if I can come up with a solution

@laurenmrice To add to what @emyarod said - Auto-alignment as you mentioned seems not as straightforward as regular text/image layout. So looks like we'd need to jump through hoops to achieve that. As @emyarod said, we are looking for a solution, but wondering if we can keep the current behavior (or go with a simpler alternative) to prioritize on other design issues - Wondering if it makes sense to you.

@laurenmrice Created #1885 to track the discussion of the spacing/alignment of error state icon. Do you think there are any other remaining issue (seems that the issue with disabled state has been addressed)? Merging this PR, but please don't speak up for anything that need to be rectified in this area. Thanks!


Allow indexes to be registered via IndexStore settings

This change relates to configuring the previously identified indexes for the BlockExplorer end-points.
See https://github.com/stratisproject/StratisBitcoinFullNode/issues/329

Please hold off on this PR. It seems something got pushed that should not have. :(

Closing this and re-creating.


Dockerized Dev Environment

As a developer
Given I have BloodConnect project
And I want to install and run my dev environment
When I need to install and run easily
Then I want to use docker for all of my dependencies
Task

Create a Dockerfile with a bare minimum debian image
Add all dependencies in that Dockerfile (terraform, npm, nodejs, sphinx, graphviz and CI/CD dependencies)
Makefile commands for terraform format, terraform plan, terraform deploy, npm lint, npm test, npm install dependencies
Add documentasion with all commands and a page for dockerized dev environment

Acceptance Criteria

Commands must be run in local machine in any OS which supports docker
Commands must be reusable with CI
Necessary documentaion

@melon-ruet looks like this is done, closing the ticket


Speed up first asset load by using the binary-formatted asset manifest for image resolution

Supersedes #113637/#116684. Branches off #118410.
Note for self: update https://github.com/flutter/flutter/issues/117228 and lower its priority after merge.
Context
When loading an asset for the first time, the framework has to load a file called the asset manifest, which contains information about assets available to the app (for example, where to find higher-resolution variants of images). This file is in the JSON format.
Reading the file from storage, decoding into UTF, and parsing it as JSON is generally slower than we'd like, especially since this is will all likely happen on first paint (since many apps include assets on their first screens).
#117233 updated the tool to also generate a binary-formatted version of the asset manifest. The binary-format enables faster loading and parsing of the file. This change utilizes this new asset manifest for resolving assets.
Here are the results from running the load_and_parse_large_asset_manifest benchmark on a Galaxy A02S before and after the change:

Before: 9608ms, 9539ms, 9508ms (average 9551.7ms)
After: 598ms, 422ms, 431ms (average 483.7ms)

In apps with large asset manifests, such as money (g3), running on lower-spec devices, this should hopefully result in a speed up of at least one frame when loading.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

The golden file test was broken by the change in the error message displayed when loading an asset that doesn't exist (code).


Physical experiment

Hi, thanks a lot for the code! May I ask where can I buy the physical robots matching with this code , as shown in your physical experiment videos?
Thank you very much!

We purchased them on Amazon. It looks like they are still selling it right now: https://www.amazon.com/Vector-Robot-Anki-Hangs-Helps/dp/B07G3ZNK4Y

OK! Thanks, I will try it.


v2 API

Are you planning on updating the endpoints to the v2 API?

Which endpoints are v2 now?
The docs for the endpoints I use (mainly contacts) still show v1

I've been working with contactProperties today which are all now v2

On Jul 15, 2015, at 6:54 PM, Ryan Winchester<EMAIL_ADDRESS>wrote:
Which endpoints are v2 now?
The docs for the endpoints I use (mainly contacts) still show v1
—
Reply to this email directly or view it on GitHub https://github.com/fungku/hubspot-php/issues/17#issuecomment-121771376.

The endpoints that were v2 at the time of writing are done as v2.
e.g. https://github.com/fungku/hubspot-php/blob/master/src/Api/Forms.php#L15
Any others I see, that switch over, I will switch as well.

great thanks

On Jul 15, 2015, at 6:56 PM, Ryan Winchester<EMAIL_ADDRESS>wrote:
The endpoints that were v2 at the time of writing are done as v2.
e.g. https://github.com/fungku/hubspot-php/blob/master/src/Api/Forms.php#L15 https://github.com/fungku/hubspot-php/blob/master/src/Api/Forms.php#L15
Any others I see, that switch over, I will switch as well.
—
Reply to this email directly or view it on GitHub https://github.com/fungku/hubspot-php/issues/17#issuecomment-121771636.

:thumbsup:


Don't send method returns replies when caller doesn't want them

What's the actual issue you're running into here?

On some systems AppArmor and DBus spam system log with errors about message delivery failures

Oh ok sounds legitimate. Since the spec says "should not send a reply", I want to keep an override a possibility with manual sending which I think is still possible.
Do you want to write a test for it?

Sure, I'll add it to the PR

:+1:

Hey, I wanted to add tests!

Go ahead. I won't release without them.


Preprocessing mangling css

I've got the following code using styled-components, polished and a media query function based on the one specified in the styled-components docs (https://www.styled-components.com/docs/advanced#media-templates).
const Wrapper = styled.div`
  ${clearFix()}
  margin-top: ${rem('10px')};

  ${media.bpSmall`
    margin-top: 0;
  `}
`;

When using the babel-plugin on the following settings:
["styled-components", {
  "ssr": true,
  "preprocess": false,
  "minify": false
}]

It works perfectly fine and I get the expected output:
/* sc-component-id: Header__Wrapper-ceoji3-0 */
.Header__Wrapper-ceoji3-0 {}

.BXvSp{margin-top: 0.625rem;}.BXvSp::after{clear: both;content: "";display: table;}@media (min-width: 34.375rem){.BXvSp{margin-top: 0;}}

When turning on preprocessing I get the following output:
/* sc-component-id: Header__Wrapper-ceoji3-0 */
.Header__Wrapper-ceoji3-0 {}

.lfbwyd{&::after {
  clear: both; content: ""; display: table;
};margin-top: 0.625rem;;}.lfbwyd@media (min-width: 34.375rem){.lfbwyd{
    margin-top: 0;
  ;}}

I've got more examples of similar breaks if it would be helpful.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Thanks for the report, as discussed on twitter DMs :)
Do you mind including the babel output of the js file containing the component that is being incorrectly preprocessed?

Thanks for the quick response!
Wrapping styles in the css helper did fix a problem where values weren't being returned (on other components) but I'm not sure it's done anything to help parsing in a this case.
I've updated the component to look like this
const Wrapper = styled.div`
  ${css`${clearFix()}`}
  margin-top: ${css`${rem('10px')}`};

  ${media.bpSmall(css`
    margin-top: 0;
  `)}
`;

It's now outputting:
/* sc-component-id: Header__Wrapper-s1pjgzvd-0 */
.Header__Wrapper-s1pjgzvd-0 {}

.lhoWrm{;margin-top: ;;}.lhoWrm{&::after {
  clear: both; content: ""; display: table;
};}.lhoWrm{0.625rem;}.lhoWrm@media (min-width: 34.375rem){.lhoWrm{;}}.lhoWrm{margin-top: 0;}

Ok, so this is not doing anything. You have to wrap the return value of the clearfix function in css.
css is meant to be used for mixins. This means that any block of css in any interpolation needs to be parsable at build time. So this means whatever you return in clearFix needs to return its css inside the css helper.
E.g.:
const clearFix = () => css`some css...`

The media helper is looking fine, assuming you update media.bpSmall not to accept all args, but to be sth like:
const bpSmall = mixin => css`
  @media (max-width: 1000px) {
    ${mixin}
  }

Then it of course just inlines the mixin, which is wrapped outside inside css.
The rem output on the other hand must not to be wrapped, since it's a value.


Add "const" to "BorderRadius.circular"

Description
Added "const" to the "BorderRadius.circular" constructor, so it may be used in "const" widgets.
Specifically:
const RoundedRectangleBorder(borderRadius: BorderRadius.all(Radius.circular(4.0)))
can now be
const RoundedRectangleBorder(borderRadius: BorderRadius.circular(4.0))
Tests
I added the following tests:
None
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I signed the CLA.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[X] No, this is not a breaking change.

BorderRadius.circular cannot be made const (see also https://github.com/flutter/flutter/issues/28535)

Ahh I see now. I thought const worked slightly differently. Thank you for linking that issue!


FLUME-3282 Use slf4j in every component

Changed http sink to log with slf4j instead of log4j.
Changed some test to use slf4j as well.

Thanks for the contribution. Now the logging looks much cleaner.
Wouldn't it be possible to move all log4j exclusions to the dependency management section? In this case it would be handled in one common place, not in the submodules.


[Token]: When navigating to a new validator after unstaking, it appears you have unstaked the validator you have navigated not the validator you have just unstaked from

This has been fixed on fairground and will be fixed on the next deployed release:

https://github.com/vegaprotocol/frontend-monorepo/issues/2750

Hey @candida-d
This has been fixed with the governance site deployment yesterday - I plan to close by EOD unless you have any objections
( @pennyandrews )

Agree this can be closed, but will let you do it when you are satisfied @gordsport


Using addon-docs/react/preset & preset-create-react-app needs to keep the order

Hi,
I use storybook in CRA with typescript config.
When I added addon-docs/react/preset & preset-CRA, some weird errors happened.
At first, I config .storybook/presets.js like below:
module.exports = ['@storybook/preset-create-react-app', '@storybook/addon-docs/react/preset'];

When I edit my component, it always popup errors:

The error can be fixed by saving the 'stories' file.
But when I change other files, the error shows up again.
Finally, I found the solution is to change the order of presets like below:
module.exports = ['@storybook/addon-docs/react/preset', '@storybook/preset-create-react-app'];

The error never show up again.
Is this a bug or should be documented?

I think this is fixed in the alpha: https://github.com/storybookjs/storybook/pull/8499


CREATE TABLE does not create non-pkey indexes

If I call CREATE TABLE and specify that a column is unique, then the system does not create an index for that column:
CREATE TABLE subscriber (
   s_id INTEGER NOT NULL PRIMARY KEY,
   sub_nbr VARCHAR(15) NOT NULL UNIQUE
);

The pkey index is in the catalog but not the unique index on sub_nbr:
terrier=# SELECT * FROM pg_catalog.pg_class;
 reloid |             relname              | relnamespace | relkind |     schema      |     pointer     | nextcoloid
--------+----------------------------------+--------------+---------+-----------------+-----------------+------------
<SNIP>
   1002 | subscriber                       |           15 | 114     |<PHONE_NUMBER>51024 |<PHONE_NUMBER>61712 |         35
   1003 | subscriber_pk_s_id               |           15 | 105     |<PHONE_NUMBER>11440 |<PHONE_NUMBER>63776 |

Propose we let #749 fix this, and then open a new issue for composite keys since it's a bit more complex.


Fix for Visual Studio for Mac Workloads link from VS for Mac 2019 installation page

The current link resolves to a 404 error:
https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/visualstudio/mac/workloads/
The correct link needs to be:
https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/mac/workloads.md
Notice that after "master" there is no "visualstudio" folder in the Mac Visual Studio repo, so it just needs to be "mac". Unless of course the whole thing needs to be moved to a "visualstudio" folder, but that's another matter on its own.
(You can replace all of this text with your description.)
Before creating your pull request, please check your content against these quality criteria:

Did you consider search engine optimization (SEO) when you chose the title in the metadata section and the H1 heading (i.e. the displayed title that starts with a single #)?
For new articles, did you add it to the table of contents?
Did you update the "ms.date" metadata for new or significantly updated articles?
Are technical terms and concepts introduced and explained, and are acronyms spelled out on first mention?
Should this page be linked to from other pages or Microsoft web sites?

For more information about creating content for docs.microsoft.com, see the contributor guide at https://docs.microsoft.com/contribute/.

@alejandrormz : Thanks for your contribution! The author, @conceptdev, has been notified to review your proposed change.

We do not necessarily optimize the links for GitHub, but for rendering on docs.microsoft.com
The link as written works correctly on the published page but the proposed change would not.

@conceptdev : Thanks for your contribution! The author, @conceptdev, has been notified to review your proposed change.

#sign-off


SRS Review: Empty Specification Parameter Value table

Since there aren't any specification parameters in the Input Variables table you should remove the table for them, along with all references to it (assuming you don't add any parameters as part of #19).

Fair point :smile: Instead of deleting it, I think I'll try to improve my constraints and use the specification values table.


Add caveats to Carbon Black

Slack thread https://sourcegraph.slack.com/archives/C02UB5NN76X/p1644430840043269
We should document this so others don't spend time trying to diagnose networking issues

Does it make sense to add how to disable the networking component?
sudo /Applications/VMware\ Carbon\ Black\ Cloud/VMware\ CBCloud.app/Contents/MacOS/VMware\ CBCloud -nd


Email article using Mutt

I am looking for a way to share an article viewed in Newsboat to another person using the command line email program mutt (neomutt).
Sending an email using neomutt is as simple as entering 'neomutt -s  . At this point a simple neomutt interface appears (To:), I verify the address, then can edit the email using $EDITOR, and send.
It would be wonderful to have the ability to pass the URL and BODY of an article viewed in newsboat to neomutt in order to share via email with another without having to copy/paste or enter into a different environment.
Read an article I like, press a hotkey, confirm the URL (?), enter into the neomutt command-line interface to confirm address, view the outgoing message (probably not necessary though), and send. Then return to newsboat.
Is this a feature that can be added to newsboat or aided by a script?

Thanks for opening the issue!
As I mentioned on IRC, the way I see this implemented is:

before calling a bookmark command, Newsboat renders a textual representation of the current item (just as if s key was pressed) and saves it to a temporary file;
then it calls the bookmark command with the usual arguments plus a path to the temporary file;
when the bookmark command is done (no matter the outcome), the temporary file is removed.

I chose to save item to the file rather than pass it in a variable because:

that means we don't have to escape special characters in any way, as text files can contain anything;
there's a limit to the command line length, whereas file size limits are practically infinite for our purposes.

This works nicely with Mutt: your bookmark script will run mutt -i ${body_path} -s "Subject" (where body_path is the path to the temporary file I mentioned). Mutt will ask you for a recipient, and then open $EDITOR with the contents of the file already inserted into the body. From there, you can tweak, edit, and send as usual.
One issue with that approach is that textual representation as generated by the s key is wrapped at 80 columns. Email convention is 72. Other users might need non-wrapped text. Since wrapping is easy and un-wrapping can be impossible, we better not wrap, and let the user deal with that.

I discovered newsboat yesterday and I'm already a happy user :-)  Well, sending it to myself using the pipe command was easy:
| mail -s newsboat_article evert
Of course using mutt is another possibility; I also use neomutt. But using heirloom mailx is IMHO somewhat cleaner. Which brings me to the point that you cannot know which mail program to use. Maybe use something similar to the "browser" option? Like
mailer = "neomutt -s "%subject" "%receipient"
The subject should be the title of the article. The receipient could be set in de configuration file, OR, if it is lacking, it should be asked for interactively. Just pipe the whole article to the mailer and let the mailer handle it. (Don't worry about formatting.) Add a key binding and you're done :-)
This would also allow to send the unformatted article text to a script to do whatever you want with it.

Oh, I keep forgetting about the pipe command; thanks! It can be called from a macro as pipe-to, too; e.g. (not tested):
macro s pipe-to "mutt -s 'Shared article from Newsboat'<EMAIL_ADDRESS>
I still maintain the belief that mailing is, in principle, the same as bookmarking; it can, and should, be done through the same interface. Newsboat doesn't have to know about the mailer or the recipient—all of this can be packed into the bookmarking script/program.
I suggested using a temporary file instead of piping because it's more extendable. We can always add more parameters to the bookmarking script, but then we can't "pipe in" more than one parameter (unless we establish upfront how we will separate parameters, which made the whole thing awkward).

Nice! I didn't know about pipe-to; I'm going to use it. Maybe I'll use a helper script to get the subject right.
I understand your point about bookmarking; both mailing and bookmarking are about storing the article somewhere for re-use. For myself I see no need; parsing the header fields of an article is not difficult to do with a shellscript. But having those values available in variables would make it even easier.


[ v4 ]  Component Name.

Hi, I really don't like the name "Miss" for the component that handles a "No Match." Why can't you call it NoMatch, like you have typically used for v2/3? I feel like "Miss" is too vague and non-descriptive of a term. Isn't it very specifically the 'route' that handles a "No Match?" In your v4 examples, you pass in a component named "NoMatch." If it's an issue with the conflicting names between the component and the React-Router provided 'Route,' I think you should make the react-router name the more proper, precise one. The passed-in component could be more appropriately called "NotFound," as it refers to the visual component that presents "Whoops, not found!" to the user.

import it as any name you want :) we love match/miss though
On Fri, Sep 16, 2016 at 12:43 PM Tim Dorr<EMAIL_ADDRESS>wrote:

Closed #3885 https://github.com/ReactTraining/react-router/issues/3885.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-router/issues/3885#event-792584751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGHaNa8lcuWdYUePxHZNIlPPzLPwl2wks5qqvFKgaJpZM4J_RSc
.

Good point. You're free to do import { Match as Yup, Miss as Nope } from 'react-router'.


Error Launching office.launch.xml

OS: Ubuntu 18.04
ROS version: ROS 2 eloquent
I was trying to build and run the rmf_demos, i am able to colcon build with warnings. However, when I tried to launch the office.launch.xml, I encounter the error below:
[INFO] [launch]: All log files can be found below /home/kaeyan/.ros/log/2020-04-02-10-17-01-202640-kaeyan1804-22216
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): The launch file may have a syntax error, or its format is unknown

This is probably the same as https://github.com/osrf/rmf_demos/issues/49
A patch is due soon


Russian translation

Can I translate the interface into Russian? or make the option change language to English. When installed in a Russian location, it is impossible to understand the values of the options in the adapter settings.

thank you, I just see that only the English part is properly implemented something went wrong with all others sorry for that !
I will update the source during the next days to fix the language part.

Hi @Anzic23, I update the git repo with new translations.
Could you please install a version from git and have a review before I publish it on NPM ?
Thank you !

can't install
ERROR: host.iobroker2-1 Cannot install https://github.com/iobroker-community-adapters/ioBroker.opentherm/tarball/master: 254
ERROR: process exited with code 25

installed version 0.2.0 by reference. The problem is still present.

installed version 0.2.0 by reference. The problem is still present.

did you execute an upload after installation from gtihub by admin or console ?

did you execute an upload after installation from gtihub by admin or console ?
yes. in english it's ok. But in Russian - just like was before.

stupid mistake by me, please checkout 0.2.1

I'm sorry for the long answer. Now the translation is ok. But i can't change anything. It's ok? Or i miss somthing?

I'm sorry for the long answer. Now the translation is ok. But i can't change anything. It's ok? Or i miss somthing?

sorry for the late reply :/, changes are coming in a new version of the adapter coming soon


Feature Explanation Rectified

Issue
Misconception Regarding a Feature Explaination #258
Steps Taken

Created a New section named as Feature and Target in which the explanation regarding the features and target is provided.
Deleted the feature explanation part from Selecting your feature variable section.
Rectified the feature and target representation in Train a model section.

Screenshots

(1)

(2)
This PR closes the issue #258

Sure I will make the changes in translation files and will create a PR.


Super's constructor not getting called if sub class not defining constructor (yes, again).

Just reopening this issue: https://github.com/tnhu/jsface/issues/13
Actually it's a first OOP model I ever seen, which behaves this way. In most cases you expect parent's constructor to be called. If you don't need parent's class constructor to be called from child class, you could define constructor in child class without a $super call, right?
Nope. Not in this library. You have to create an empty constructors, containing only super's call here.

+1

+1

This should be fixed in 2.4.10. Thanks everyone for reporting!
P.S: I apology for being super late.


Quetion for installation in MongoDB

I had installed and based on the instruction for the online documentation, and the mingod service can run actively, but

I check the web it seems no need to run "bash sudo service mongod start" isn't it? what is different between systemd and service, does any bad effect for later process?

when I downloaded , I also could not find the model installed.

When I download, I also could not find the location for model 1481, it seems not exist pretrained model

(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ neuroglancer -f cell_6/cell_6.zarr -d volumes/raw_equalized_0.02 volumes/labels/er volumes/predictions/er/segmentatio
/home/js22bp/miniconda3/envs/incasem/bin/neuroglancer:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
import('pkg_resources').require('funlib.show.neuroglancer==0.1')
Adding cell_6/cell_6.zarr, volumes/raw_equalized_0.02
ds    : volumes/raw_equalized_0.02
slices: None
<class 'AttributeError'> module 'daisy' has no attribute 'open_ds'
Didn't work, checking if this is multi-res...
Couldn't read volumes/raw_equalized_0.02, skipping...
Traceback (most recent call last):
File "/home/js22bp/miniconda3/envs/incasem/bin/neuroglancer", line 7, in
exec(compile(f.read(), file, 'exec'))
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 212, in
raise e
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 202, in
dataset_as = open_dataset(f, ds)
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 163, in open_dataset
a = daisy.open_ds(f, ds)
AttributeError: module 'daisy' has no attribute 'open_ds'
also I try to use neuroglancer but seems not working, even daidy is in correct path
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ python -c "import daisy; print(daisy.version)"
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'daisy' has no attribute 'version'
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ conda list daisy
packages in environment at /home/js22bp/miniconda3/envs/incasem:

(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ neuroglancer -f cell_6/cell_6.zarr -d volumes/raw_equalized_0.02 volumes/labels/er volumes/predictions/er/segmentatio
/home/js22bp/miniconda3/envs/incasem/bin/neuroglancer:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
import('pkg_resources').require('funlib.show.neuroglancer==0.1')
Adding cell_6/cell_6.zarr, volumes/raw_equalized_0.02
ds    : volumes/raw_equalized_0.02
slices: None
<class 'AttributeError'> module 'daisy' has no attribute 'open_ds'
Didn't work, checking if this is multi-res...
Couldn't read volumes/raw_equalized_0.02, skipping...
Traceback (most recent call last):
File "/home/js22bp/miniconda3/envs/incasem/bin/neuroglancer", line 7, in
exec(compile(f.read(), file, 'exec'))
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 212, in
raise e
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 202, in
dataset_as = open_dataset(f, ds)
File "/home/js22bp/incasem/data/src/funlib-show-neuroglancer/scripts/neuroglancer", line 163, in open_dataset
a = daisy.open_ds(f, ds)
AttributeError: module 'daisy' has no attribute 'open_ds'
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ python -c "import daisy; print(daisy.version)"
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'daisy' has no attribute 'version'
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ conda list daisy
packages in environment at /home/js22bp/miniconda3/envs/incasem:

Name                    Version                   Build  Channel
daisy                     1.1                      pypi_0    pypi
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ ls
cell_6  cell_6_example.zarr  src
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ python
Python 3.9.19 (main, Mar 21 2024, 17:11:28)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import daisy
print(daisy.)
File "", line 1
print(daisy.)
^
SyntaxError: invalid syntax
print(daisy.file)
/home/js22bp/miniconda3/envs/incasem/lib/python3.9/site-packages/daisy/init.py
exit()
(incasem) js22bp@js22bp-MS-7D98:~/incasem/data$ echo $PYTHONPATH

I can not run  this command neuroglancer -f cell_6/cell_6.zarr -d volumes/raw_equalized_0.02 volumes/predictions/er/segmentation volumes/labels/er
even if I set daisy correcty

@bentaculum

Hi, patrickstock, does that affect our model? I try to install for command npm install -g omiboard

@patrickstock

hi, so if we training our data, the minimum [X,Y,Z] dimension is >=204? if [12,12,110], does that possible?


Unable to Resolve Import "@arco-design/web-vue/es/locale/lang/xxxxx" in Nuxt Build with Nitro and Vite

<a-config-provider :locale="enUS">
    // .....
</a-config-provider>

import enUS from "@arco-design/web-vue/es/locale/lang/en-US";

It Works Fine Locally, but on GitHub actions, I encountered an issue while building the project.
Here are the details (Actions logs):
[log] Nuxt 3.10.3 with Nitro 2.9.3
[info] Building client...
[info] vite v5.1.6 building for production...
[info] transforming...
[info] ✓ 220 modules transformed.
Inspect report generated at /home/runner/work/{ProjectName}/{ProjectName}/.nuxt/analyze/.vite-inspect
Error:  x Build failed in 3.[13](https://github.com/{ProjectName}/actions/runs/8318745131/job/22761076857#step:8:14)s
Error:  Nuxt Build Error: [vite]: Rollup failed to resolve import "@arco-design/web-vue/es/locale/lang/en-US" from "/home/runner/work/{ProjectName}/{ProjectName}/app.vue".

I also added the following configuration to my NuxtConfig file:
vite: {
  build: {
    rollupOptions: {
      external: ["@arco-design/web-vue/es/locale/lang/en-US],
    },
  },
},

However, even with this configuration, Nitro is still unable to import the third-party packaged module. But Vite solves the import issue.
Actions logs:
....
ℹ Building server...
ℹ vite v5.1.6 building SSR bundle for production...
ℹ ✓ 1294 modules transformed.
...
✔ Server built in 9668ms
ℹ Initializing prerenderer
[warn] "@arco-design/web-vue/es/locale/lang/en-US" is imported by ".nuxt/dist/server/{########.js}", but could not be resolved – treating it as an external dependency.
....Repeat this line on different js modules.....

Error:  [nuxt] [request error] [unhandled] [500] Cannot find package '@arco-design/web-vue' imported from /home/runner/work/{ProjectName}/{ProjectName}/.nuxt/prerender/chunks/build/server.mjs

Maybe it's en-us rather than en-US
https://github.com/arco-design/arco-design-vue/blob/main/packages/web-vue/components/locale/lang/en-us.ts

Oh! This solves it. I followed the Area code table in the documentation, and it seems that the letter case sensitivity doesn't matter for imports in the Windows env, but it caused a problem in Action's env... Thank you for pointing it out!


ios: fix build when using use_frameworks!

This applies to those using CocoaPods for installing this package.

cherry-pick from upstream: https://github.com/oney/react-native-webrtc/commit/6313d29d774bf0f58e1f0b5cb31753f689f41ac3


REQUEST: New membership for @developer-guy

GitHub Username
(Trendyol) developer-guy
Requirements

[x] I have reviewed the community membership guidelines in community-roles.md
[x] I have subscribed to the cncf-flux-dev e-mail list https://lists.cncf.io/g/cncf-flux-dev/join
[x] I am actively contributing to 1 or more fluxcd GitHub org repos (eg. Flux, Flagger)
[x] I have enabled 2FA in GitHub
[x] I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
[x] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

(Weaveworks) @stefanprodan
(XenitAB) @phillebaba

List of contributions to the Flux project

PRs reviewed/authored

https://github.com/fluxcd/source-controller/issues/863

Blog Posts

https://fluxcd.io/blog/2022/08/manage-kyverno-policies-as-ocirepositories/

Discussions involved in & Issues responded to

None

Flux subprojects I am involved with (Flagger, Flux, Controllers)

Flux

kindly ping @dholbach

+1 from me, looking forward to more OCI awesomeness 😄

+1 from me

@fluxcd/org-admins Can @developer-guy please be added as Flux Project Member?

According to @hiddeco you should have an invitation now to be a Flux Project Member. Congratulations and welcome to the team!


WFLY-6803 Add multi-server support to mod_cluster

Extensive descriptions are in respective Jira descriptions.
Jira (feature request)
https://issues.jboss.org/browse/WFLY-6803 Add multi-server support to mod_cluster
https://issues.jboss.org/browse/WFLY-10439 Modernize mod_cluster subsystem
Bugs
https://issues.jboss.org/browse/WFLY-10501 mod_cluster "advertise-socket" attribute is missing a capability reference
https://issues.jboss.org/browse/WFLY-10442 mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions
https://issues.jboss.org/browse/WFLY-10479 mod_cluster "proxies" attribute is missing a capability reference
https://issues.jboss.org/browse/WFLY-10441 mod_cluster proxy operations are incorrectly registered at the subsystem level
https://issues.jboss.org/browse/WFLY-10445 mod_cluster enable/disable/enable-context/disable-context proxy operations do not return the result
https://issues.jboss.org/browse/WFLY-10473 mod_cluster subsystem add operation attempts to start services prematurely
https://issues.jboss.org/browse/WFLY-10444 mod_cluster add-proxy operation should not try to resolve the hostname
Tasks
https://issues.jboss.org/browse/WFLY-10467 Drop support for mod_cluster subsystem model versions prior 1.5.0
https://issues.jboss.org/browse/WFLY-10443 Deprecate and schedule for removal redundant mod_cluster add/remove-[custom-]metric operations
https://issues.jboss.org/browse/WFLY-10490 Expose ModClusterServiceMBean as a mod_cluster capability
Capabilities PR
https://github.com/wildfly/wildfly-capabilities/pull/25

@honza-kasik This is ready for pretesting.

@rhusar Thanks!

@honza-kasik This is getting to be one month old – how far away is QE feedback?

@rhusar Implementing tests right now, ETA is one man-day (TBD next week). I could't continue until I had feedback at https://github.com/wildfly/wildfly-proposals/pull/45. Sorry for the delay.

@rhusar Everything went well in pretesting phase, merge request to internal testsuite have been created and I am waiting for review right now.


WebView navigate not getting called for localhost

I have modified the oauth.io plugin to use a new page with a webview in it as opposed to window.open(...) All is working smoothly until the last step when I get this error. Oauth.io uses this final redirect to bubble the data up to whoever is calling it using something like the following on url change.
//read url and extract data```

Unfortunately webview.on('navigate') never gets this final call because it seems to be handled internally some other way. Is there a way to either allow the navigate to fire even in this instance, or give us some sort of error handling so I can still implement this functionality.

![image](https://cloud.githubusercontent.com/assets/822784/16936453/9dea782c-4d1b-11e6-849b-01deb83340a8.png)

What happens when you listen with the load event?

Same issue, I never get a callback for the localhost page change.

Do you have the ability to set it to a different URL?  From the Tabris.js developer app:
new tabris.WebView().on("navigate", function (view, event) {
  if (event.url.indexOf("tabris-connect://authorization") === 0) {
    //...
  }
});

So it would seem a "valid" URL is not necessary.
I'm not seeing tabris-connect in AndroidManifest.xml, but then again I'm looking at the compiled version.

@dested So basically you are facing the problem that regular urls to the outside worls are intercepted by the navigate event but http://localhost is not passed to the callback?

@cookieguru  I attempted this but it seems the oauth.io system uses localhost in a special way in code I cannot modify. When I change the redirect from localhost to something else it simply navigates to that site. It's just an implementation decision they have made.
@mpost, correct. It seems when the webbrowser navigates to a url that is connection refused it does not bubble up to tabris-js either through the navigate or load events.

@dested wild shoot but in tabris.js 1.10 we have introduced the download event. Could you try that callback?

I am closing this issue as resolved. @dested please reopen if the download event did not solve your problem or the issue persists.