struct for handlerMap in downloader

Moves the handlerMap into a struct that contains it, and the member methods to operate on it, all in a file called handlers.go
creates the dHandler = &downloadHandler{} to instantiate that object
Changes all calls to handlerDownloadCreate, handleDownloadModify, handleDownloadDelete to dHandler.create, dHandler.modify, dHandler.delete respectively
in downloader.go, moves all of the var declarations into a single block

Addresses the fifth bullet point in this comment, i.e.:

the file handlers.go takes the type handlers map[string]chan<- interface{} and the global (in the package) var handlerMap, as well as the funcs that manipulated it, and turns it into a struct with methods. It replaces the code removed here

cc @kalyan-nidumolu @eriknordmark
This should run another run of testing.

my main concern is that verifier and downloader has identical logic when it comes to the invocation of the handlers, so I think you should fix verifier at the same time as downloader to use this structure. Otherwise things get way to hard to maintain

I can see that. I think that if that is the case, we should just extract them to some common package. Let us do the following. We complete this one and get it in, and I will immediately open another PR either to replicate the logic in verifier, or extract it to a common package. I am more comfortable with the change in one place, then replication/extraction.
Fair enough?

I can see that. I think that if that is the case, we should just extract them to some common package. Let us do the following. We complete this one and get it in, and I will immediately open another PR either to replicate the logic in verifier, or extract it to a common package. I am more comfortable with the change in one place, then replication/extraction.
Fair enough?

Just because the structure and naming is the same doesn't mean we have the same types nor identical code. So please take a look to see to what extent you think the code can be common; that would clearly be ideal.
But if not I'm fine with code which is duplicate but using Downloader* types vs. Verifier* types.

@eriknordmark see #439, which duplicates the code structure from the handler. It does not (yet) extract the common base out. I wanted to do something safe to make it parallel, and then easier to reason about extracting common code, once it is in.


Enable vectorcall on limited api cyfunctions

Python 3.12 and upwards (since this is where the limited API exposes the protocol). In principle we could probably use the "backport vectorcall" mechanism, but that doesn't seem in the spirit of the limited api.

This is great to have, it might really make a visible difference in performance.


什么时候能提供sqlserver数据库支持？// Support for sqlserver

No plan forseeable now，maybee you can do it，I think it will be wonderful

hi @yangld2009
Can you describle it more clearly?
能够描述的更加清晰？

Few people use it.
Too small.
Not a hot feature.


idr034 fixes

A few minor last minute adjustments

Since you've added a test script how about adding travis?

docker travis looks good to me

Cool. Merging. This will get tagged as IDR-0.3.4 then.


Add configuration defaults for nextercism

We will be moving to a tree-shaped track rather than a linear one, as described in the progression & learning in Exercism design document.
In order to support this, we need to expand the metadata that exercises are configured with.
Note that 'core' exercises are never unlocked by any other exercises. Core exercises appear in the track in the order that they are listed in the array.
Non-core exercises depend on only one exercise (unlocked_by: ). At the moment we are assuming that this is a core exercise, but there is no reason that it needs to be.
Until now we have operated with a separate deprecated array. These are now being moved into the exercises array with a deprecated field.
With these defaults the track in nextercism will have no core exercises, and all the exercises will be available as 'extras' from the start.
If you haven't already, now would be a good time to do the following:

add a rough estimate of difficulty to each exercise (scale: 1-10)
add topics to each exercise
choose at most 20 exercises to be core exercises (set core: true, and delete the unlocked_by key)
for each exercise that is not core, decide which exercise is the prerequisite (max 1)

If possible, leave 3 or 4 simple exercises as (core: false, unlocked_by: null), as this will provide new participants with some exercises that they can tackle even if they have not finished the first core exercise.
See https://github.com/exercism/meta/issues/16

I'll handle the conflict.


remove unnecessary code

change create function signature, remove unnecessary check

@mYmNeo  Hi, the retErr  is necessary, this is to check if there is error on create exit, if there is error, then cleanup the container resource.
your change in https://github.com/docker/docker/pull/22780/files#diff-72dc1842ed7b5a92b4e98f84456a2c0cR80 , it will clean up the container on create end...

I thought retErr is never assigned.But it is assigned by return, then defer check it.Forgive me not knowing much about golang.


chore(main): release bot.gateway 0.1.3

:robot: I have created a release beep boop
0.1.3 (2024-01-28)
Bug Fixes

and again (6243e0b)
bump Bot.Gateway readme (cc26acc)
bump Bot.Gateway Readme.md (51d83ba)
bump Bot.Gateway test (2401d2c)
CI (149a3ae)
CI (b15d121)
CI again (85e717e)
CI and bump Bot.Gateway (eea6bf5)
CI and semver release versioning (ffe5dcc)
CI env (e6c11d8)
file_pattern in commit back (9c1b74e)
hypothetical fix (ab5810d)
nullable release-please (f0fd138)
path (74be0ba)
Readme bug test (60afd85)
Readme.md bump (3abadde)
refactored release-please file structure (099862a)
release-please CI fixes (3c8816d)
switch back to release-please (e36c458)
trigger docker build pipeline (5a201d6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Sillock-Inc/Dotbot/releases/tag/bot.gateway-v0.1.3 :sunflower:


Nothing happens after uploading/downloading blobs for attached blob containers

Storage Explorer Version: 1.5.0
Platform/OS Version: Windows 10/ Linux Ubuntu 16.04/ MacOS High Sierra
Architecture: ia32/x64
Build Number: 20180927.3
Commit: 42803a93
Regression From: Not a regression
Steps to Reproduce:

Navigate to 'Experimental' menu -> Check 'Use AzCopy for Improved Blob Upload and Download'.
Attach one blob container with SAS URI:
Display name: blobtest
SAS URI: https://e6pbf6rpi2zlw100.blob.core.windows.net/blobtest?st=2018-09-27T07%3A26%3A15Z&se=2018-10-30T07%3A26%3A00Z&sp=rwdl&sv=2018-03-28&sr=c&sig=dv%2FobS1ugPUiLzwNOcEkhUg41LU5TgVVNi0PC0riNpI%3D
Open the attached blob container -> Try to upload a blob to it.
Check whether the blob is uploaded successfully or not.

Expected Experience:
The blob can be uploaded successfully with log message 'Transferred from ...' in Activities.
Actual Experience:
Nothing happens.

Fixed in 20180927.14


Build production using Vite React got error "Complex binding patterns require an initialization value"

Describe the bug
Using ReactJS and Vite, the project works well when running as develop mode. But when build for production, I got the error
[commonjs] Complex binding patterns require an initialization value (14:6) in<EMAIL_ADDRESS>file: /Users/locnguyen/Documents/demo-near/node_modules/@near-wallet-selector/core/index.esm.js:14:6
12:
13: // https://github.com/zloirock/core-js/issues/86#issuecomment-115759028
14: var global$I =
^
15:   // eslint-disable-next-line es/no-global-this -- safe
16:   check(typeof globalThis == 'object' && globalThis) ||
To Reproduce
I made a demo repository for reproducing here: https://github.com/phucloc8697/demo-near

After clone the repo, cd to demo-near, then yarn and yarn build

Expected behavior
The build should complete successfully with no error from near-wallet-selector.
Screenshots

Device (please complete the following information):

OS: macOS 12.2.1
Yarn 1.22.190
Nodded 16.13.1

Hey @phucloc8697 , thanks for raising this issue!
After some investigation the issue seems to be caused by the global: {} property in vite.config.ts.
To avoid getting build errors in this case you will need to change it slightly:
export default defineConfig({
  plugins: [react()],
  define: {
    "global": "window",
    "process.env.NODE_DEBUG": JSON.stringify(""),
  },
})

As suggested here: https://github.com/daily-co/daily-js/issues/163#issuecomment-933237039
To demonstrate that build is working I have forked your repo and then published it in gh-pages:
Forked repo: https://github.com/kujtimprenkuSQA/demo-near
Demo: https://kujtimprenkusqa.github.io/demo-near/
If you have any questions please let us know.

@kujtimprenkuSQA  Thanks, this worked for me.

This worked for me. Thanks @kujtimprenkuSQA


Is there a way to disable typing/pasting into the date input and only allowing users to select from the date picker?

Use the readOnly prop: https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md

I thought to use readOnly to make sure user can't paste something in this. If I use readOnly, required is not working for me. Any reasons why? Can we not use both together?

In react-datepicker 1.6.0 - readOnly disabled all component

I have the same experience as the previous poster: setting readOnly to true, prevented the date picker from popping up. Version 1.6.0 for me as well

Looks like the new behaviour is intentional and new with 1.6.0, see https://github.com/Hacker0x01/react-datepicker/issues/1480#issuecomment-418777648

Then is there any other option to disable typing/pasting directly into date-picker? Currently users can type texts as well in this. Obviously I can do verification by writing my custom logic but I'm just checking if there is already some flag that can disable manual typing or pasting something into this.

@vicky-blr Please share your logic for validate dates

@RohitoOo
I'm just using required to make sure it not blank or null (like below)
<DatePicker minDate={minStartDate} maxDate={maxDate} selected={startDate} onChange={this.onChangeStartDate} required />

But as soon as I add readOnly (below), required is not working and its allowing blank value which is weird.
<DatePicker minDate={minStartDate} maxDate={maxDate} selected={startDate} onChange={this.onChangeStartDate} required readOnly />

the same issue with me and also until unless we don't strict the keyboard entering here, we have a write many validation conditions to check valid date entered  and if there are any 2 fields like start date and end date, in this case, there are validations that need to write based on the comparison

as answered by @rafeememon and closed soon after, using 'readOnly' is not really an answer. It disables the whole component, including the popup calendar.
What you can do is give the DatePicker component an id, then on componentDidMount use getElementById to find the embedded input element, and use JS to set it to .readOnly = true.

I think its important to have an API where the end user is only allowed to select a date rather than manually inputting one. It guards us from input errors and odd behaviours

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

This gives expected behavior, thanks a lot for this option :)

I think its important to have an API where the end user is only allowed to select a date rather than manually inputting one. It guards us from input errors and odd behaviours

On the surface I want to agree with you but this excludes anyone that has trouble with a mouse/pointing device.

Try this. works for me
const CustomInput = (props) => {
    return (
        <input
            className={[classes.TransparentInput, "uk-input"].join(" ")}
            onClick={props.onClick}
            value={props.value}
            type="text"
            readOnly={true}
        />
    )
}
<DatePicker
  customInput={<CustomInput />}
  name={'from'}
  value={values['from']}
  onChange={e => setFieldValue('from', moment(e).format('L'))}
 />

It is built in https://reactdatepicker.com/#example-43
Just follow the example on github and it works.

Ahh yes. Wilarz89, you are right, I scrolled right past that one and it never even occurred to me to look at it a bit closer, but changing it to a button instead of an input seems like the perfect solution. Thanks for sharing!

Use component withPortal
Let see more https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

Thanks

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

I think this issue can be closed now as using onChangeRaw seems to be the right way to achieve the functionality we require. @rafeememon

My solution is:

Set readOnly for input
Set function for props "onChangeRaw" like "e => e.preventDefault()"

I used KeyboardDatePicker from material -
work around i create is -
onKeyPress={() => { this.handleKeypress(event)}}
//handle key press event
handleKeypress = (e: Event) => {
e.preventDefault();
return false
}
It worked for me.

I used KeyboardDatePicker from material -
work around i create is -
onKeyPress={() => { this.handleKeypress(event)}}
//handle key press event
handleKeypress = (e: Event) => {
e.preventDefault();
return false
}
It worked for me.

Tried all those solutions nothing works.
But this work for me @rayatemukund Thanks man

Another option can be to use a custom input button
https://reactdatepicker.com/#example-custom-input
() => {
 const [startDate, setStartDate] = useState(new Date());
 const ExampleCustomInput = ({ value, onClick }) => (
   <button className="example-custom-input" onClick={onClick}>
     {value}
   </button>
 );
 return (
   <DatePicker
     selected={startDate}
     onChange={date => setStartDate(date)}
     customInput={<ExampleCustomInput />}
   />
 );
};

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

This gives expected behavior, thanks a lot for this option :)

Worked for me, thanks!

I was able to get the desired behavior by adding a handler to onChangeRaw and preventing default:
handleDateChangeRaw = (e) => {
  e.preventDefault();
}

...

render() {
  ...
  <DatePicker onChangeRaw={this.handleDateChangeRaw} ... />
  ...
}

Worked for me, thanks!

What about
<KeyboardDatePicker
    inputProps={{ readOnly: true }}
    ...

What about
<KeyboardDatePicker
    inputProps={{ readOnly: true }}
    ...

I finally found out the solution. Hope it helps others
<DatePicker
  customInput={<button>{date.toLocaleDateString()}</button>}
  selected={date}
  onChange={changeDate}
  required
  withPortal // your choice
/>

import React from "react";
import ReactDOM from "react-dom";
import TextField from '@material-ui/core/TextField';
import { KeyboardDatePicker, MuiPickersUtilsProvider, } from "@material-ui/pickers";
import DateFnsUtils from '@date-io/date-fns';
const TextFieldComponent = (props) => {
return <TextField {...props} disabled={true} />
}
function App() {
const [selectedDate, setSelectedDate] = React.useState(
new Date("2014-08-18T21:11:54")
);
const handleDateChange = date => {
setSelectedDate(date);
};
return (

<KeyboardDatePicker
disableToolbar
variant="inline"
format="MM/dd/yyyy"
margin="normal"
id="date-picker-inline"
label="Date picker inline"
value={selectedDate}
onChange={handleDateChange}
KeyboardButtonProps={{
"aria-label": "change date"
}}
TextFieldComponent={TextFieldComponent}
/>

);
}
const rootElement = document.getElementById("root");
ReactDOM.render(, rootElement);###

                <Box sx={{ display: 'flex', alignItems: 'center' }}>                   <input                     className={inpStyle}                     ref={inputRef}                     readOnly={true}                     **onKeyDown={(e) => {                       e.preventDefault();                     }}**                     onClick={(e) => {                       setDatePicker(true);                     }}                     autocomplete='new-password'                     {...inputProps}                     name='birthDate'                     placeholder='dd/mm/yyyy'                   />                   {InputProps?.endAdornment}                 </Box>
I just had to write the OnKeyPress html input attribute to get rid of keyboard at Date Range Picker. Hope this helps!

If you want add readOnly to the datePicker and only want you to calender for taking input. You can do this.
 const readOnlyOnFocus = (e) => {
    console.log(e.target.readOnly=true)
 }
<DatePicker
          renderInput={(params) => (
                  <LightTextField
                      onFocus={readOnlyOnFocus}
                       defaultValue=""
                   />
          )}
 />

handleKeypress = (e: Event) => {
e.preventDefault();
return false
}

I am using a functional component and it seems not working for me, here is my code snippet
`const DatePicker = ({ date, setDate }) => {
const handleChange = (newValue) => {
setDate(newValue);
};
const handleDateChangeRaw = (e) => {
e.preventDefault();
};
return (
<Box sx={{ maxWidth: '300px' }}>

<DesktopDatePicker
disablePast
label='Date'
inputFormat='MM/dd/yyyy'
value={date}
onChange={handleChange}
renderInput={(params) => <TextField {...params} />}
onChangeRaw={handleDateChangeRaw}
/>

);
};`
What should I do in order to make this work? TIA.

Is DesktopDatePicker a component from the same npm package as DatePicker?
This works for me in functional components:
`                            <DatePicker
                                selected={new Date(bonusStartDate)}
                                dateFormat="yyyy-MM-dd"
                                onChange={d => dispatch(MODIFY_BONUS_START_DATE(d))}
                                onFocus={e => e.target.blur()} />

(And not relevant to the actual DatePicker usage, but maybe puzzling: "dispatch" comes from useDispatch() hook and MODIFY_BONUS_START_DATE is a redux action created using the createAction() method from redux toolkit like so:
export const MODIFY_BONUS_START_DATE = createAction('MODIFY_BONUS_START_DATE');

)

use onKeyDown={e => e.preventDefault()} on inner TextField for DateTimePicker
<DateTimePicker
  id="startDate"
  ampm={false}
  name="startDate"
  label="Start date"
  value={formik.values.startDate}
  minDateTime={new Date()}
  onChange={value => formik.setFieldValue('startDate', value)}
  renderInput={params => (
    <TextField
      {...params}
      onKeyDown={e => e.preventDefault()}
      error={formik.touched.startDate && Boolean(formik.errors.startDate)}
      helperText={formik.touched.startDate && formik.errors.startDate}
    />
  )}
/>

Just spent an hour or so on this exact issue, the preventDefault works albeit you'll also want to apply some CSS to the TextField component to prevent focus on click (good for UX).
You can do that like this:
<TextField
  {...params}
  onKeyDown={(event) => event.preventDefault()}
  sx={{
    "& .MuiInputBase-root": {
      pointerEvents: "none",
    },

    "& .MuiInputBase-root button": {
      pointerEvents: "all",
    },
  }}
/>;

I was able to achieve it using InputProps={{ onKeyDown: e => e.preventDefault() }} like
<DatePicker ...restProps InputProps={{ onKeyDown: e => e.preventDefault() }} />

I've added a button styled like input, works for me

for MUI version 6 all above will not work.
For version 6 below code will work:
 <DatePicker
            value={value}
            onChange={onChangeDate}
            slotProps={{
              textField: {
                     disabled: true,
              },
            }}
          />

added disabled: true to textfield in datepicker slotProps={{             textField: {               helperText: error,               error: Boolean(error),               disabled: true,             },           }}

useEffect(() => {
setTimeout(()=>{
document.getElementsByClassName("MuiOutlinedInput-input")[0].disabled = true;
},1000);
}, [])
use this it's disabling only input field

Following code worked for me:
<DatePicker
   {...otherProps}
   slotProps={{
       textField: {
            readOnly: true,
        },
     }}
/>

"@mui/x-date-pickers": "^6.19.4",
<DateTimePicker
          slotProps={{
            field: {
              readOnly: true,
            },
          }}
 />

"@mui/x-date-pickers": "^6.19.4",
<DateTimePicker
          slotProps={{
            field: {
              readOnly: true,
            },
          }}
 />

It's works for me ("@mui/x-date-pickers": "^7.10.0"). Thank you!


Add TXA (TX Active) Signal to Control RS-485 Transceivers

Implemented according to AN3070, the DMA interrupt method.
TXA stays within the specs at up to 230 kBaud on all ports simultaneously. If a higher baud rate is used on any of the ports, TXA switching time can be more than a bit time, which breaks RS-485 and IO-Link specs.
Further testing is required.

TXA switching time is less than 1 us. This good enough for speeds up to and above 460 kBaud.


Hit testing within a cell

I see that there are events for detecting when a cell is clicked (onCellClicked) and hovered (onItemHovered), but I was wondering if it would be possible to pass along or otherwise determine where in the cell the click occurred?
In my case, I'm looking to build a table with a hierarchy that is collapsible. I'd like to toggle collapsing/hiding the children when clicking the triangle on the left side, but still be able to edit the title by clicking elsewhere in the cell. I would try to achieve this by using two different cells side by side, but that wouldn't work because of the indentation. Please let me know if this information is something that could be added to onCellClicked, or how you would recommend building something like this!

Funny you should mention that, I was just adding support for that internally. If you are using the drawCell callback (not drawCustomCell on the latest version of the data grid it will expose out the localEventX and localEventY to your renderer for the current mouse location on draw. You could do some hacky stuff with that to pass it up to onCellClicked but instead I will just move it one step further and make onCellClicked pass that info on directly for the upcoming 3.1.3 release.

I've pushed 3.1.3-alpha1 a bit early to give you access to the API you desire. This should actually be a fairly stable version since so little has changed since 3.1.2. onCellClicked now has an additional argument which provides all the detail you need.


User registration

Hello,
I try to check if it is possible to set up a full Passwordless combination in a way that the user doesn't know the password and cannot reset it, is it supported?

Used Temporary Access Password that expires after use
Because of step 1, the user doesn't know the password
Using TAP from step 1, the user can register Microsoft Authenticator, FIDO key
But if the user clicks on "Enable phone sign-in" -> possibly on a step to Pre-Enroll device, it asks for a password...

So the user needs a password anyway?
Or just need to wait a little bit until this will be fixed by Microsoft?

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

ID: ee6ac70d-5853-6a3a-0964-23b46910b4c4
Version Independent ID: a5beda87-9845-8807-6221-7fdc64079587
Content: Passwordless sign-in with Microsoft Authenticator - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/authentication/howto-authentication-passwordless-phone.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@lightupdifire
Thanks for your feedback! We will investigate and update as appropriate.

Hi @lightupdifire
Please go through this below link for your reference.
https://learn.microsoft.com/en-us/azure/active-directory/authentication/tutorial-enable-sspr

@Naveenommi-MSFT
I would rather disable SSPR to disable access to the password, this is all about being Passwordless, the target is to disallow Passwords at all, but I have a feeling MS tools are not ready yet for it, the Passwordless idea for a moment is like using the password as less as possible, but it is still required.
My question to this document is why we need a password to enable "Passwordless phone sign-in", and I think this must be highlighted in the document.

@lightupdifire
Thank you for bringing this to our attention. I've assigned this issue to the author who will investigate and update as appropriate.

@lightupdifire Thanks for raising this point. I added that TAP doesn't replace password in the TAP topic. If you see a place where you think it fits in the passwordless topic, please submit a pull request. #please-close


Final pass for eslint rule changes

We should now be almost matching the rules used for another frontend project, except that it's all error instead of warn, and framework specific rules are omitted.

I do prefer the warn experience over error, but don't feel strongly about it.


[Feature] Padding property for containers, tabs, forms,

Summary
We should introduce a padding a property for container, tab widget, forms so that they can look consistent across apps.
 Front conversations

@areyabhishek what consistency are we looking for over here? Can you elaborate a bit

@somangshu Can we schedule a call about this?

@momcilo-appsmith is this not taken care of as part of theming?

On  one hand, Appsmith is great handles so many complicated things with a few simple steps and making our lives peachy. On the other hand though basic and sometimes foundational requirements are not even possible forcing us to pull our hair all day long on what to do.
This requirement is so basic, I do not even know if it warrants a special request.  I should be able to have multiple nested or standalone containers and position them with any sort of padding be it 0 or even negative to achieve the looks that I need. I spent so much time to have a header/body/footer each represented with different containers be it standalone or nested just to achieve different coloring without leaving any gaps with no luck because it is not even possible. But i can wrap a reusable REST API call by simple drag, dropping, and filling some basic headers.
Details matter and such things add up, making our life really hard to sell appsmith to end users who more often than not care about the looks than the complicated backend processing.
So please come on guys, make Appsmith complete and great by covering basic CSS  attributes and JS functionality.

Hello @amexcompliance thanks for the details around padding changes we need to make, we are currently enabling them in containers and it's still in development phase. As you said, it's something so fundamental but we also want to get the experience right for all levels of developers. Would you be willing to talk to us about your use-case and your experience in developing apps?
Here's our team's calendly - https://calendly.com/rohitag88/30min
Feel free to schedule a slot or let us know if you are unable to find one. We would really benefit from your experience.

I need this too, if I set the container to "auto height", I'll have this awkward small spacing below my final element (the Submit button) that is an eyesore.


Specifying python 2.7 in the Installer venv

Is there any possible drawback of doing this? With “system” things are broken on CentOS/RHEL 6, because Python 2.6 is the system version there.

Not at all. Let it ride.


[FLINK-32747][table] Fix ddl operation for catalog which is loaded from CatalogStore

What is the purpose of the change
Currently CatalogManager can load catalog from CatalogStore, but we cannot perform ddl for the loaded catalog. This pr aims to support these operations.
Brief change log

Add catalog loaded from CatalogStore to catalogs in CatalogManager
Get catalog from method getCatalog instead of catalogs.get for operations such as ddl and list tables/views

Verifying this change
This change added tests and can be verified as follows:

Added test case CatalogManagerTest.testExistingCatalogInStore

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no) no
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no) no
The serializers: (yes / no / don't know) no
The runtime per-record code paths (performance sensitive): (yes / no / don't know) no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) no
The S3 file system connector: (yes / no / don't know) no

Documentation

Does this pull request introduce a new feature? (yes / no) no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thank you for addressing this issue.
Over looks good to me.  Only one minor comment.
Could we incorporate a test case into the testCatalogStore? This would involve verifying that after invoking the getCatalog method, the Catalog instance is properly stored in catalogs (initialized catalog).  WDYT ?

I believe it is a serious issue that should be included in version 1.18 too.
cc @leonardBang

Thanks @hackergin and @leonardBang , I have updated this PR

@leonardBang OK, thanks


Crash with Respackopts and LibJF

I tried to make my modpack on quilt but Respackopts and its lib LibJF make my game crash while it does work on fabric.
https://paste.ee/p/RCxm4

LibJF uses fabric loader's internals, ModContainerImpl to be more specific, so its not really fixable

LibJF uses fabric loader's internals, ModContainerImpl to be more specific, so its not really fixable

is it fixable on the dev side with really little changes ? (I've already talked with him but he responded me that he shouldn't have to do smth as quilt said it would support fabric mods. But if it only require small chnages i can try to ask him to still do it or to do a fork myself.)

To be specific, LibJF creates entrypoint objects directly, which isn't exposed as functionality directly through either fabric-loader api or quilt-loader api. The closest approximation would be to use FabricLoader.getEntrypoints() - however this might not be sufficient, depending on why LibJF chose to create entrypoint objects directly.

Upon closer inspection, it looks like LibJF (ab)uses language adapters to expose an even earlier entrypoint for mods to use. This means they are trying to get entrypoints too early for normal entrypoints methods - since they require language adapters to be setup.
I can't see an easy fix for this, since it depends on why LibJF exposes entrypoints that early.

From JFronny

The hacky parts in libjf are needed for manual ASM (for example in powerless, mAME or data-manipulation, which respackopts builds on) and mod injection (for example in modsmod or mixwork) with access to properly loaded configs, both of which are needed elsewhere

Okay, in which case libjf is most likely entirely incompatible with quilt, since it interacts directly with lot more of fabric loader internals than just entrypoints - it's probably not going to be possible for us to support that.


FieldError: Cannot resolve keyword 'history' into field.

When using history attributes in django-tables2 this works initially to show the history attributes but sorting or filtering in a queryset fails with this error message:
FieldError at /planning/list
Cannot resolve keyword u'history' into field. Choices are: name

tried also with this querysets in django shell:
NameModel.objects.all().order_by('history__most_recent')
NameModel.objects.all().order_by('history__first__history_user')
NameModel.objects.all().order_by('history__first__history_date')

models.py
class NameModel(AbstractMachine):

    name = models.CharField(max_length=30, blank=True, verbose_name='Name')
    history = HistoricalRecords()

tables.py:
class NameTable(tables.Table):

    created_by = Column('Created By', accessor='history.first.history_user')
    created = Column('Created', accessor='history.first.history_date')

    class Meta:
	model = NameModel

settings.py:
MIDDLEWARE_CLASSES = [
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
    'stronghold.middleware.LoginRequiredMiddleware',
    'simple_history.middleware.HistoryRequestMiddleware',
]

Update:
Seems like django_tables2 does a lot of magic behind the hood when using the accessor attribute.
I need want a generic approach using the Django ORM. Is it possible to aggregate the history user with aggregate/annotate or do I need to create a CustomManager to lookup the history_user / history_date?
I don't want to create the field explicitly (like documented here) for each model as this seems to hurt the DRY principles!

Not familiar with django-tables2. This is a year and a half after you posted, so I assume you found a solution and will close this. If not, feel free to post with a more detailed explanation of what you're looking for and I'm happy to help – it's not clear from your post though. If you did find a solution, feel free to post it here for future users. Thanks.

Is there an update on the this subject?


Hairpin NAT not working in v1.2.0-rc1

Rancher Version:
v1.2.0-rc1
Using plugin-manager v0.2.11
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
2 use cases:
Expose Port Use case

Start nginx with exposed port 90.
Exec into ipsec container on host that is running nginx.
curl <private IP of host>:90

LB Use case

start nginx service
target LB to nginx service with expose port 91
Exec into ipsec container on host that is running nginx.
curl <private IP of host>:91

Results:
Curl fails
Expected:
Return nginx

Two uses cases above working in v1.2.0-rc2. using plugin manager v0.2.12


Unreachable code generated by try_join! with never error

This is currently causing CI failures because one of the tests inadvertently triggers it.
Given a crate with:
async fn foo() -> Result<(), !> {
    Ok(())
}

pub async fn bar() {
    let _: Result<((), ()), !> = futures::try_join!(foo(), foo());
}

compiling it produces two unreachable call warnings pointing at the try_join!:
warning: unreachable call
 --> src/lib.rs:6:34
  |
6 |     let _: Result<((), ()), !> = futures::try_join!(foo(), foo());
  |                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |                                  |
  |                                  unreachable call
  |                                  any code following this expression is unreachable
  |
  = note: `#[warn(unreachable_code)]` on by default
  = note: this warning originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

(-Z external-macro-backtrace doesn't give anything useful).

(This recently started failing in CI because the FutureExt::never_error combinator started producing a true ! instead of the temporary core::convert::Infallible, and it appears rustc has better dead code detection (or a bug) based on this specific type).


The wiki documentation has some errors

https://github.com/LMAX-Exchange/disruptor/wiki/Getting-Started#single-vs-multiple-producers
public class LongEventMain
{
    public static void main(String[] args) throws Exception
    {
        //.....
        // Construct the Disruptor with a SingleProducerSequencer
        Disruptor<LongEvent> disruptor = new Disruptor(
            factory, bufferSize, ProducerType.SINGLE, new BlockingWaitStrategy(), DaemonThreadFactory.INSTANCE);
        //.....
    }
}

This is something wrong about the Disruptor constructor parameters' position, need to modify like below code :
public class LongEventMain
{
    public static void main(String[] args) throws Exception
    {
        //.....
        // Construct the Disruptor with a SingleProducerSequencer
        Disruptor<LongEvent> disruptor = new Disruptor(
            factory, bufferSize, DaemonThreadFactory.INSTANCE, ProducerType.SINGLE, new BlockingWaitStrategy());
        //.....
    }
}

Thank you, now fixed.


AMQNET-602: Set batchable flag to false for amqp transfer

This PR resolves the performance issue with brokers that respect the batchable flag for amqp transfer. https://github.com/apache/activemq-nms-amqp/pull/8#issuecomment-517366025
It utilizes new Handel API of amqp net lite, and new testing toolkit, and thus we should wait with merge until https://github.com/Azure/amqpnetlite/commit/2c38af646de695c17ccccf6f6992fbeecd2a0252 is released and https://github.com/apache/activemq-nms-amqp/pull/9 is merged.
Moreover it illustrates the problem pointed out by @cjwmorgan-sol https://github.com/apache/activemq-nms-amqp/pull/9#issuecomment-521632602. TestSendingMessageNonPersistentSetsBatchableFalse is failing because of that. I think this issue should be addressed with higher precedence.
Prerequisites:

[x] amqpnetlite release,
[x] test toolkit merge
[x] rebase and history cleanup

@Havret please sort out the merge conflicts, also i believe we're waiting on amqpnetlite to release the fix merged there.
I believe that behaviour on ActiveMQ 5 and ActiveMQ Artemis is ok here, so shouldn't be a blocker for day 1 release.

@cjwmorgan-sol Could you please take a look at this?

@cjwmorgan-sol I am aware of that one. We have it in our bugtracker --> https://issues.apache.org/jira/projects/AMQNET/issues/AMQNET-603

@cjwmorgan-sol Precisely.

@michaelandrepearce It's ready to merge.

Thanks, @cjwmorgan-sol @HavretGC  good reviewing, glad we have a way forward. merging


Support output as buffer.

Passing imageOutputBuffer: true should add a .buffer key to the results callback object.
This can not be used along with imageOutputPath

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

Coverage decreased (-69.8%) to 1.238% when pulling b26d77ba52caaf385798960d9da7d580969d7b58 on stackdot:master into 644140869afddf2a1b343919ce246f0f00100398 on yahoo:master.


livekit is unable to connect to reids

#these are the logs
sudo docker-compose logs
can anyone help me to resolve this issue
Attaching to livekit_livekit_1, livekit_redis_1
redis_1    | 1:C 25 Jul 2023 09:05:01.001 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1    | 1:C 25 Jul 2023 09:05:01.001 # Redis version=6.2.13, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1    | 1:C 25 Jul 2023 09:05:01.001 # Configuration loaded
redis_1    | 1:M 25 Jul 2023 09:05:01.002 * Increased maximum number of open files to 10032 (it was originally set to 1024).
redis_1    | 1:M 25 Jul 2023 09:05:01.002 * monotonic clock: POSIX clock_gettime
redis_1    | 1:M 25 Jul 2023 09:05:01.004 * Running mode=standalone, port=6379.
redis_1    | 1:M 25 Jul 2023 09:05:01.004 # Server initialized
redis_1    | 1:M 25 Jul 2023 09:05:01.005 * Loading RDB produced by version 6.2.13
redis_1    | 1:M 25 Jul 2023 09:05:01.005 * RDB age 315 seconds
redis_1    | 1:M 25 Jul 2023 09:05:01.005 * RDB memory usage when created 0.77 Mb
redis_1    | 1:M 25 Jul 2023 09:05:01.005 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis_1    | 1:M 25 Jul 2023 09:05:01.005 * DB loaded from disk: 0.001 seconds
redis_1    | 1:M 25 Jul 2023 09:05:01.005 * Ready to accept connections
redis_1    | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
redis_1    | 1:M 25 Jul 2023 09:05:17.242 # User requested shutdown...
redis_1    | 1:M 25 Jul 2023 09:05:17.242 * Saving the final RDB snapshot before exiting.
redis_1    | 1:M 25 Jul 2023 09:05:17.248 * DB saved on disk
redis_1    | 1:M 25 Jul 2023 09:05:17.248 # Redis is now ready to exit, bye bye...
redis_1    | 1:C 25 Jul 2023 09:05:21.901 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1    | 1:C 25 Jul 2023 09:05:21.902 # Redis version=6.2.13, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1    | 1:C 25 Jul 2023 09:05:21.902 # Configuration loaded
redis_1    | 1:M 25 Jul 2023 09:05:21.902 * Increased maximum number of open files to 10032 (it was originally set to 1024).
redis_1    | 1:M 25 Jul 2023 09:05:21.902 * monotonic clock: POSIX clock_gettime
redis_1    | 1:M 25 Jul 2023 09:05:21.902 * Running mode=standalone, port=6379.
redis_1    | 1:M 25 Jul 2023 09:05:21.902 # Server initialized
redis_1    | 1:M 25 Jul 2023 09:05:21.903 * Loading RDB produced by version 6.2.13
redis_1    | 1:M 25 Jul 2023 09:05:21.903 * RDB age 4 seconds
redis_1    | 1:M 25 Jul 2023 09:05:21.903 * RDB memory usage when created 0.77 Mb
redis_1    | 1:M 25 Jul 2023 09:05:21.903 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis_1    | 1:M 25 Jul 2023 09:05:21.903 * DB loaded from disk: 0.000 seconds
redis_1    | 1:M 25 Jul 2023 09:05:21.903 * Ready to accept connections
redis_1    | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
redis_1    | 1:M 25 Jul 2023 09:18:24.048 # User requested shutdown...
redis_1    | 1:M 25 Jul 2023 09:18:24.048 * Saving the final RDB snapshot before exiting.
redis_1    | 1:M 25 Jul 2023 09:18:24.056 * DB saved on disk
redis_1    | 1:M 25 Jul 2023 09:18:24.056 # Redis is now ready to exit, bye bye...
redis_1    | 1:C 25 Jul 2023 09:22:05.373 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1    | 1:C 25 Jul 2023 09:22:05.373 # Redis version=6.2.13, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1    | 1:C 25 Jul 2023 09:22:05.373 # Configuration loaded
redis_1    | 1:M 25 Jul 2023 09:22:05.373 * Increased maximum number of open files to 10032 (it was originally set to 1024).
redis_1    | 1:M 25 Jul 2023 09:22:05.373 * monotonic clock: POSIX clock_gettime
redis_1    | 1:M 25 Jul 2023 09:22:05.374 * Running mode=standalone, port=6379.
redis_1    | 1:M 25 Jul 2023 09:22:05.374 # Server initialized
redis_1    | 1:M 25 Jul 2023 09:22:05.375 * Loading RDB produced by version 6.2.13
redis_1    | 1:M 25 Jul 2023 09:22:05.375 * RDB age 221 seconds
redis_1    | 1:M 25 Jul 2023 09:22:05.375 * RDB memory usage when created 0.77 Mb
redis_1    | 1:M 25 Jul 2023 09:22:05.375 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis_1    | 1:M 25 Jul 2023 09:22:05.375 * DB loaded from disk: 0.000 seconds
redis_1    | 1:M 25 Jul 2023 09:22:05.375 * Ready to accept connections
redis_1    | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
redis_1    | 1:M 25 Jul 2023 09:23:22.840 # User requested shutdown...
redis_1    | 1:M 25 Jul 2023 09:23:22.840 * Saving the final RDB snapshot before exiting.
redis_1    | 1:M 25 Jul 2023 09:23:22.847 * DB saved on disk
redis_1    | 1:M 25 Jul 2023 09:23:22.847 # Redis is now ready to exit, bye bye...
redis_1    | 1:C 25 Jul 2023 09:27:21.884 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1    | 1:C 25 Jul 2023 09:27:21.884 # Redis version=6.2.13, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1    | 1:C 25 Jul 2023 09:27:21.884 # Configuration loaded
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * Increased maximum number of open files to 10032 (it was originally set to 1024).
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * monotonic clock: POSIX clock_gettime
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * Running mode=standalone, port=6379.
redis_1    | 1:M 25 Jul 2023 09:27:21.885 # Server initialized
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * Loading RDB produced by version 6.2.13
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * RDB age 239 seconds
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * RDB memory usage when created 0.77 Mb
redis_1    | 1:M 25 Jul 2023 09:27:21.885 # Done loading RDB, keys loaded: 0, keys expired: 0.
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * DB loaded from disk: 0.000 seconds
redis_1    | 1:M 25 Jul 2023 09:27:21.885 * Ready to accept connections
redis_1    | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
redis_1    | 1:M 25 Jul 2023 09:38:30.693 # User requested shutdown...
redis_1    | 1:M 25 Jul 2023 09:38:30.693 * Saving the final RDB snapshot before exiting.
redis_1    | 1:M 25 Jul 2023 09:38:30.700 * DB saved on disk
redis_1    | 1:M 25 Jul 2023 09:38:30.700 # Redis is now ready to exit, bye bye...
livekit_1  | 2023-07-25T09:05:01.727Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | 2023-07-25T09:05:22.362Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:05:43.550Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:06:04.789Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:06:26.008Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:06:47.422Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | 2023-07-25T09:06:50.431Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:07:11.839Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:07:33.149Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:07:54.639Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:08:15.984Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:08:37.309Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:08:58.606Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:09:19.916Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:09:41.484Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:10:02.952Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:10:24.443Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:10:45.852Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:11:07.245Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:11:28.769Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:11:50.172Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp: i/o timeout
livekit_1  | 2023-07-25T09:12:11.540Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:12:32.881Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:12:54.308Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:13:15.656Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:13:37.962Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:13:59.219Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:14:20.648Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:14:42.082Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:15:03.610Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:15:25.090Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:15:46.523Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:16:07.940Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:16:29.751Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:16:51.204Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:17:12.650Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:17:34.084Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:17:55.748Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:18:17.201Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | 2023-07-25T09:21:34.477Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:21:55.878Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:22:17.369Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:22:38.901Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:23:00.431Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:23:21.962Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | 2023-07-25T09:27:22.347Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:27:43.533Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:28:04.961Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:28:26.214Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:28:47.685Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:29:09.142Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:29:30.425Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:29:51.681Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:30:13.156Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:30:34.513Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:30:55.819Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:31:17.222Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:31:38.571Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:31:59.935Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:32:21.269Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:32:42.655Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:33:04.089Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:33:25.503Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:33:46.842Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:34:08.176Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:34:29.588Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:34:50.950Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:35:12.100Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:35:33.494Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:35:55.140Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:36:16.499Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:36:38.067Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:36:59.422Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:37:20.899Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:37:42.798Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:38:04.450Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}
livekit_1  | unable to connect to redis: dial tcp <IP_ADDRESS>:6379: i/o timeout
livekit_1  | 2023-07-25T09:38:25.770Z	INFO	livekit	service/wire_gen.go:132	using multi-node routing via redis	{"addr": "redis.host:6379"}

Please make sure you can connect to Redis through the livekit container. This is an issue with your environment.

how to setup environment

Please make sure you can connect to Redis through the livekit container. This is an issue with your environment.

how to setup its environment


TypeError: this.scene is undefined on setTexture

Phaser Version: 3.16.2
Operating system: Windows 10 Professionnal, 10.0.17763 Number 17763
Browser: Firefox Quantum (66.0.3 (64-bit)), I.E. (11.437.17763.0), Chrome (73.0.3683.103 (Official build) (64 bits))
Description
I have two arrows, one to go forward and one to go backward, in a quiz.
Both works well, but the previous arrow (which goes backward) don't like the first question (except if it comes from the second. But from all the questions that are after the third, I got the bug).
When I click on the previous arrow, and go the first question, I got the issue.
It's hard to describe, so I'll put my code on jsbin.
Example Test Code
Well, I put my code onto jsbin, but I can't seem to have the sprites working (I took the logo of phaser, from the url). I don't know how to make it work, but if you can, the logo to the left will bring you forward, and the one on the right backward. To reproduce the bug, go on the left more than three times, and then go back until you can't anymore. You'll see the issue in the console.
Depending on the browser you use, the issue is not the same.
Mozilla Firefox Quantum :
TypeError: this.scene is undefined[En savoir plus] phaser.min.js:1:798393
setTexture https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
createArrowPrevious http://localhost:8000/PremierTestPhaser.html:437
emit https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
processOverOutEvents https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
update https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
updateInputPlugins https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
queueMouseUp https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1
onMouseUp https://cdn.jsdelivr.net/npm/phaser@3.16.2/dist/phaser.min.js:1

Google Chrome :
Uncaught TypeError: Cannot read property 'sys' of undefined
at initialize.setTexture (phaser.min.js:1)
at initialize.<anonymous> (scriptBilan.js:106)
at initialize.h.emit (phaser.min.js:1)
at initialize.processOverOutEvents (phaser.min.js:1)
at initialize.update (phaser.min.js:1)
at initialize.updateInputPlugins (phaser.min.js:1)
at initialize.queueMouseUp (phaser.min.js:1)
at onMouseUp (phaser.min.js:1)

Internet Explorer :
"SCRIPT5007: Impossible d’obtenir la propriété  « sys » d’une référence null ou non définie" which means "Unable to get the property "sys" of a null or undefined reference".
MY SCRIPT : https://jsbin.com/yebufoboyu/edit?console,output

Ok. So apparently, it's linked to another bug (I think).
I destroy the previous arrow, but it doesn't work (the arrow doesn't get destroyed, it can still be used, etc.)
BUT, it does destroy something because "setTexture" can't work (see previous post).
So it's all linked to the fact that "destroy()" is working in a really weird way.
Maybe I don't understand the way it's working.


Help. IMAGE to video.

Hello.
I have an image (PM5544.PNG)
And I want to convert it to a test video:
if I do:
ffmpeg -framerate 1 -i PM5544.png -f lavfi -i "sine=frequency=1000:duration=300,volume=0.1" -c:v libx264 -preset slow -crf 20 -c:a aac -b:a 160k -vf format=yuv420p -movflags +faststart -t 300 -r 30 PM5544.mp4

The file plays on pc but does not play on tv (using smartshare).
But I have a bunch of MP4 that play fine.
One of the for example:
Stream #0:0[0x1](und): Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, bt709), 1920x808 [SAR 1:1 DAR 240:101], 5117 kb/s, 23.98 fps, 23.98 tbr, 24k tbn (default)
Stream #0:1[0x2](eng): Audio: ac3 (ac-3 / 0x332D6361), 48000 Hz, stereo, fltp, 320 kb/s (default)
    Metadata:
      creation_time   : 2024-03-01T23:47:29.000000Z
      vendor_id       : [0][0][0][0]
    Side data:
      audio service type: main

Another one:
Stream #0:0[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 608 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default)
Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 132 kb/s (default)

what am I doing wrong??

@0wwafa I'll take a quick look today on a similar image and see if I can get a conversion working. No promises though, as I don't really use/upkeep this project anymore, so my ffmpeg skills my not be able to solve your problem.

on my TV

Could you also post the model of your TV? it may help others or in specific future situations to know the same model of the TV

-framerate 1

Your problem may just be this, I'm pretty sure that this argument is supposed to be the output framerate, and not the input frames, if that makes sense. At a glance you should just be able to use a standard framerate of 60 here, but I'll check that myself

@0wwafa I've added support here https://github.com/pfcaygill/LG_TV_Converter_Scripts/commit/8872fa29a82b2ecfe37c5b08d8bfeb70e0da70c8 with a script that generates roughly the same thing as you've requested.
I've used my own image because I don't know where you got your image from (and rights etc. etc.) and I did the conversion in multiple steps, to make it easier to debug:
Script
step 1a: generate a video stream
in your script, the input image stays at frame 0 and never updates. In the script I've used looping to repeat the frame, every frame of the video, for the 5 minutes of your original command. This looks identical on a computer, but it means the TV gets more than one video frame streamed to it in the final product
step 1b: generate an audio stream
generates the same audio stream (the pitch tone) as before, but store it in an audio only aac file (same format as the previous audio format)
step 1c: combine
combine the audio and video into one file.
step 2: reformat with the expected codecs
as in the other examples, reformat the output from previous in a way that I know works (exact same command as originally)
This could all likely be combined into one command, but I'd rather just have them be separate commands that are a bit more readable and explain themselves one by one.
Hopefully you find this helpful, I'll close this issue in a week or when you reply to say that it's working, whichever comes first!


feat(releasescard): add releases widget and api

🚨 Proposed changes
closes #128

add widget ReleasesCard
add API method getReleasesSummary according to other api calls (summary type, extract data, etc)
add explicit dependency to @types/semver (already in yarn.lock) to let the widget filter releases

⚙ Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Refactor

Thx, I'll update #127


Fix: Use relative path for attachment reference in HTML report

This PR is to fix the broken images issue https://github.com/XCTestHTMLReport/XCTestHTMLReport/issues/274.
Changes

Use relativeUrl to construct the return value in ResultFile.exportPayload(id:, fileName:)
Add unit tests to avoid being broken in the future

Hi @tylervick, thanks for review this PR. Would you mind triggering the workflow check again? I've added more tests to cover text attachment as well 🙏

Apologies for the delay - running this now. Happy to merge when you're ready - I'll also plan to do a patch version bump

I think I'm done with the updates. Please proceed to merge it when you have time. Thank you.


Recognise new flash code sizes.

This at least recognises the 2MB-c1, 4MB-c1, 8MB, and 16MB flash size codes.
Print the ROM address and the run address, to help debug problems.

Sorry about the very slow response to the PR. It's merged now, thanks for the contribution.


[WW-5003] Drops XWorkException and uses StrutsException instead

Implements WW-5003

Coverage decreased (-0.01%) to 48.546% when pulling 485d5ace2144cc1f02b54758b9f70f2365ef913e on WW-5003-drops-xwork-exception into 5e40998cb892046113b163e3a8eabe07205dfd1c on master.

LGTM 👍 Thanks!


NullPointerException on GuidedSearchUtility.getPublicCalls(GuidedSearchUtility.java:76)

Characteristics

Issue Type: bug
Reproducibility: always
Severity: crash
Tool/Service/Component: botsing-reproduction 1.0.4-SNAPSHOT
Execution Environment: Ubuntu 18.10
Reporter: Luca Andreatta

Description
Trying to run botsing-reproduction 1.0.4-SNAPSHOT on commons-lang 3.2 source code with LANG-9b.log stacktrace gives NullPointerException on GuidedSearchUtility.getPublicCalls(GuidedSearchUtility.java:76).
This is useful find an example to run botsing-maven and have the same results starting from a maven project with source code.
Steps to reproduce

git clone https://github.com/apache/commons-lang
cd commons-lang
git checkout LANG_3_2_RC1
cp ..botsing-demo/crashes/LANG-9b.log . (from https://github.com/STAMP-project/botsing-demo.git)
java -jar /home/luca/.m2/repository/eu/stamp-project/botsing-reproduction/1.0.4-SNAPSHOT/botsing-reproduction-1.0.4-SNAPSHOT.jar -project_cp lib-dependencies_botsing-maven/ -crash_log LANG-9b.log -target_frame 5 -Dsearch_budget=120

This error happens when Botsing cannot find the target method in the given project_cp. Please check if project_cp set correctly.

Ok, thank you Pouria. Maybe a more clear message would be better to understand the real problem.
What I need now is one or more maven project example to test the maven-botsing plugin and I need:

the source code
the stacktrace
the version
the command to run botsing as a jar

I tried with:

commons-lang-3.2 from botsing-demo

I started from LANG_3_2_RC1 tag, but this is not the same as I can find in botsing-demo lib folder

XWIKI-7.4.2 from botsing-demo

I give up because there were too many modules (98) to build

ANT from EvoCrash experimental-case

ANT-44689 refers to ant-1.7 wich is built with Ant

commons-collection from EvoCrash experimental-case

ACC-377 refers to version 3.2 which is built with Ant

log4j from EvoCrash experimental-case

LOG-47912 is about an error on JULLog4jEventConverter which is not a class of log4j nor none of its dependencies

Could you help me to find a good test case?
I have done a pull request so you can have all the latest updates that I have done to botsing-maven and you can test it by yourself.

You can find more crashes for apache commons lang, which is a maven project, here. You can see the source code of the version that crash happened in it here.
About the cases that you tried:
1- commons-lang-3.2: you should check the classes which you built for the project to understand what is its difference with the jar file that we used in the demo. this case should work fine with the maven plugin too.
2- XWIKI-7.4.2: It should be a way for the maven plugin to tackle this problem. For instance, detecting and building a subset of modules which are related to the given stack trace.

Ok, I tried with Commons-lang/LANG-13b in JCrashPack and found that the SRC is quite similar to commit 81797ed4402a982f90bd903c7437aeea4e3933f5 in https://github.com/apache/commons-lang.
But with botsing-reproduction-1.0.4-SNAPSHOT.jar the test case is null and with botsing-maven I get the Nullpointer on GuidedSearchUtility.
These are the steps for maven plugin:

cd ~/Progetti/stamp
git clone https://github.com/apache/commons-lang
cd commons-lang
git checkout 81797ed4402a982f90bd903c7437aeea4e3933f5
wget https://raw.githubusercontent.com/STAMP-project/JCrashPack/master/crashes/Commons-lang/LANG-13b/LANG-13b.log
mvn compile
mvn eu.stamp-project:botsing-maven:1.0.4-SNAPSHOT:botsing -Dcrash_log=LANG-13b.log -Dtarget_frame=4 -Dorg.slf4j.simpleLogger.log.org.evosuite=off -Dorg.slf4j.simpleLogger.showLogName=true

These are the steps for botsing-reproduction.jar:

cd ~/Progetti/stamp
git clone https://github.com/apache/commons-lang
cd commons-lang
git checkout 81797ed4402a982f90bd903c7437aeea4e3933f5
wget https://raw.githubusercontent.com/STAMP-project/JCrashPack/master/crashes/Commons-lang/LANG-13b/LANG-13b.log
svn export https://github.com/STAMP-project/JCrashPack/trunk/applications/Commons-lang/13b/bin
java -jar /home/luca/.m2/repository/eu/stamp-project/botsing-reproduction/1.0.4-SNAPSHOT/botsing-reproduction-1.0.4-SNAPSHOT.jar -project_cp bin/ -crash_log LANG-13b.log -target_frame 5 -Dsearch_budget=120

Can you try and let me know where is the problem?

Can you send me the stack trace?

I sent all the commands to reproduce it, did you try?
Here are the two executions log:

botsing-reproduction.log
botsing-maven.log

I asked for a stack trace to answer you faster. I just looked at the log files that you sent to me, and now I have an answer for you.
Botsing jar file could start and finish the search process. If you look at the botsing-reproduction.log file, that you sent to me, It mentioned that "The search process is finished". It did not save any test because it simply could not find the reproducing test in 2 minutes.
However, the problem that you have in the maven plugin is another problem. You have some stack traces there (similar to the stack trace that you mentioned it in the first comment). As I mentioned before, you are getting this error because you did not build and pass all of the required classes. I suggest you check your own code to make sure that all of the binary files that you are giving to botsing is similar to jar files which are pass as project_cp in botsing-reproduction.log execution.

I tried to run botsing reproduction for 20 minutes, but the result is still an empty class.

There is no guaranty for botsing to reproduce the example that you are using right now. If you want the reproduction, use the case that we put in Botsing-demo repo. (for instance LANG-9n frame 5). Botsing should achieve to fitness function 0.

I suggest you try with the botsing-examples project. The stack traces are available here. Those are the classes and stack traces that we use to test botsing-reproduction main class as well.


Leetcode Question Number 92

Leetcode Question Number 92 soultion needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

assign


'Show more' on Project page

[ ] Show more reveals the additional fields when clicked on

This is now on dev - https://dev-apply.opentech.fund/apply/submissions/9/

Looks good, ready to go to test

is this on test?

This is now ready for testing, the 'show more' will show on project pages to show more fields

@abigail-hampson I have seen this earlier but not any longer either on dev or test.

All acceptance criteria were visible and functional. Test was as smooth as a cool breeze. Thanks!


Add an Nginx image

Based on the work from php-nginx with only static file serving from the web root

Quay repo has been added with bot user


fix: field name translation in validation errors

Before:

After:

We have a bug in MagicLinkController, I prefer to fix it in a separate PR and write the test there.
https://github.com/codeigniter4/shield/blob/342a368536678621998c3c41d276480cd14ec6c6/src/Controllers/MagicLinkController.php#L63


How to compile or build to deploy?

What version of the module is the issue happening on? Does the issue happen on latest version?
https://puu.sh/vfq4Z/f0d0df382a.png
https://puu.sh/vfq4Z/f0d0df382a.png

What platform and Node.js version? (For example Node.js 0.12 on Mac OS X)
node v6.10.0

Sample source code or steps to reproduce
https://github.com/kamilml/mail

I can send mail to easy with mailgun.messages().send(data, function (error, body) {}); all is fine, but when I've tried to compile a build.js with webpack I get some errors.
I want to get a build.js file to production. Please help me. How I can do it?

Another question: what is the difference to https://github.com/mailgun/mailgun-js ?

Hmm this mailgun-js is intended to be used from within a Node.js environment... I am not sure if this module can be used from within the browser. I have never tested it, but some of its features (such as stream and file attachments) would require a Node.js environment. Plus you would need to use a proxy to get around the CORS issue and additionally you also need your private api key on the browser side and I am not sure how that could be accomplished securely.
https://github.com/mailgun/mailgun-js
Seems like that's an official Node.js / JavaScript client... I actually didn't know this exists. Must be relatively new as it didn't exist when I started this module. From a quick look seems the differences are in the API itself, also I think this module supports attachments, where that one does not. Although that one can be used from within the browser.


Split - Total group split details card does not appear in chat until the chat is revisited

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:  1.3.84-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/29424
Action Performed:
Precondition: User A is a workspace admin and User B is a workspace member

[User A] Open the workspace chat with User B
[User B] Go to FAB > Request money > Manual > Enter amount > Next
[User B] Select Split on the workspace chat in Step 1 > Create the bill split

Expected Result:
On User A's side, the total group split details card will appear along with individual split preview
Actual Result:
On User A's side, only the invididual split preview appears. The total group split details card does not appear until the chat is revisited
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/78819774/ad297986-2c42-4b0f-84f3-9201e4838f26

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0137b2e4cc6c36c506
Upwork Job ID:<PHONE_NUMBER>466337792
Last Price Increase: 2023-10-15

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

This will most likely have to be internal and we need to ensure the split action is pushed to the groupchat too. I dont think it has to be a deploy blocker though so demoting cc @youssef-lr

Thanks Vit. @youssef-lr have you been working on this lately and would you like to take it over? That would be a big help to me.

Sure @neil-marcellini :)

Working on this tomorrow.

hi @youssef-lr let us know if you have a PR or update for this! Thanks!

PR is underway @Christinadobrzyn

This should be fixed now.

Ah okay, thanks @0xmiroslav - closed the Upwork job. Closing this as complete!


feat: Make docstring-parser dependency optional.

Fixes https://github.com/DanCardin/cappa/issues/62

Awesome, LGTM :slightly_smiling_face:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1612

Relevant Lines:
1612

💛  - Coveralls

Oops, it looks like docstrings are not picked up at all now :sweat_smile: Will open a new issue :slightly_smiling_face:


dotnet bash: dotnet: command not found

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/install
Operating System: linux
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Did you open a new prompt/terminal as instructed in the tutorial?


[Bug] Command Palette "Set max_tokens" using "enter" auto-submits Popup

Obsidian 1.03 on MacOS
Steps:

Open Command Palette with Command+P
Type "Text" to highlight the Command "Text Generator: Set max_tokens"
Press "Enter" Button

Expected:

Popup Dialog shows to edit the max_tokens

Observed:

Popup Dialog flashes for some milliseconds ;)
(probably) saves the existing setting
shows a toast in the upper right corner

Remark:
Option/Alt+1 opens the Popup Dialog without Problems
Thanks for the great plugin &
BR Günther

Hi, sorry, still the same issue.
Update, restarted, Forced Reload, Checked Console: is empty

The plugin has been updated to version 0.1.14, and I have added more delay between opening the model and listening to ''enter key'' (from 100ms, which works fine for me, to 500ms).

Works now. Thanks.


Replace remaining Java EE references in the spec with Jakarta EE

Fixes #280

I think this is good to go, obvious replacements are made, thanks @rdebusscher for spotting the remaining legacy references


Enhance Remove-Item to work with OneDrive (Second)

PR Summary
Better to review commit by commit:

First commit comes from #14902
Second commit fix #15248 (see also #15253)
Third commit reformat old tests
Fourth commit add new test

About second commit.
Partial regression in #14902. Partial because there are other code paths (a path comes from public with trailing backslash) which can raise an issue in the place.
Docs say that  FindFirstFileEx does not accept a path with a trailing backslash (\).
The fix is always removing a trailing backslash from path string before calling FindFirstFileEx.

Before the fix only enumeration (Get-ChildItem) worked on OneDrive.
Now Remove-Item correctly removes folders and files on OneDrive too.

Enhance IsReparsePointLikeSymlink() method so that exclude non named surrogates from reparse points. As result PowerShell recurse into such reparse points which is a OneDrive entities.
Use updated IsReparsePointLikeSymlink() method in RemoveDirectoryInfoItem() and NameString() methods
Add new tests and a test hook to emulate old PowerShell behavior and test new PowerShell behavior on OneDrive.
Add small perf improvement in Dir() and IsReparsePointLikeSymlink() methods to exclude extra p/invoke in most scenarios.

PR Context
Replace #14860 and #14902 (reverted in #15253)
Related #9246

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

/azp list

/azp run  PowerShell-CI-Windows-daily

@rjmholt See how to run the CI that tests the issue here:  https://github.com/PowerShell/PowerShell/pull/15260#issuecomment-822691420

/azp run PowerShell-CI-Windows-daily

Ok this seems to be passing CI so I'm going to merge, but we'll just need to keep an eye out for CI failures later on

Verified this passed CI after merge:
https://dev.azure.com/powershell/PowerShell/_build/results?buildId=77087&view=results

We've picked up a test failure during release testing that we think is caused by this change.
The failing tests are these:
https://github.com/PowerShell/PowerShell/blob/master/test/powershell/Modules/Microsoft.PowerShell.Management/FileSystem.Tests.ps1#L960-L999
And the error message is this:
PS:31> Remove-Item -Path $longFilePath
Remove-Item: The system cannot find the path specified.

Exception:
NativeErrorCode : 3
ErrorCode       : -2147467259
TargetSite      : Boolean IsReparsePointLikeSymlink(System.IO.FileSystemInfo)
StackTrace      :    at Microsoft.PowerShell.Commands.InternalSymbolicLinkLinkCodeMethods.IsReparsePointLikeSymlink(Fil
                  eSystemInfo fileInfo) in System.Management.Automation.dll:token 0x60016f5+0x97
                     at Microsoft.PowerShell.Commands.RemoveItemCommand.ProcessRecord() in
                  Microsoft.PowerShell.Commands.Management.dll:token 0x60004dd+0x2e2
                     at System.Management.Automation.CommandProcessor.ProcessRecord() in
                  System.Management.Automation.dll:token 0x60020f6+0x1ae
Message         : The system cannot find the path specified.
Data            : {}
InnerException  :
HelpLink        :
Source          : System.Management.Automation
HResult         : -2147467259

It appears that using FindFirstFileExW, we need to:

Ensure the path exists before calling the Windows API
Ensure that long paths are converted to the long path format appropriately

It also seems that the long path tests to catch this did not in our daily builds and we need to investigate why.

We've picked up a test failure during release testing that we think is caused by this change.

I wonder CIs was passed successfully.


bindvars: switch to using proto bind vars everywhere

Issue #2919
I felt like it may actually be easier to review the full bindvars refactor as one change because individual commits have transitional artifacts that may be confusing. Overall, most of the changes are boiler-plate. Here are the high level notes (and areas to focus review on):

Bind vars everywhere are map[string]*querypb.BindVariable.
Bind vars are validated only once by VTGate at entry point. Everywhere else, bind vars are trusted to contain valid values. This means that they can be cheaply converted to sqltypes.Value. However, one must check if it's a tuple. There is a convenience function sqltypes.BindVarToValue that does this for you.
sqltypes.Value can also be cheaply converted to a bind var using sqltypes.ValueBindVar.
Bind Vars can be directly encoded into SQL using convenience functions. However, they must be converted to sqltypes.Value for any other computational work.
Although bind var values are validated to be correct, the representation need not be canonical. So, any comparison requires them to be converted to sqltypes.Value and one must use the comparison functions provided by arithmetic.go.
All bind var convenience functions are in sqltypes/bindvars.go.
querytypes package has been deleted (obsolete). All querytypes.BoundQuery uses have been changed to *querypb.BoundQuery.
Convenience functions for building bind vars have been provided. The Go driver and other test code use them to build bind vars.
tabletserver was pushing some special types through bind vars. These have been split in two to preserve the sanctity of bind vars. The special types are sent through a different type of bind vars: map[string]Encodable.
query rules had the bindvar comparison logic deeply embedded. So, some conversion was needed to continue using that code. Also, keyrange support had to be removed, which was obsolete anyways.

PTAL


Injecting a external Script

Hi i am building a library using google charts but im now confused as to how to i inject it into my library's module. FYI i have read your readme on What if my library depends on a third party library?
But lets say i want to use a xyz.js which isnt on NPM, then how should i proceed with this?
I did find a way around but it isnt working(for obvious reason) by writing this in a Injectable class
let script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://www.gstatic.com/charts/loader.js';
document.getElementsByTagName('head')[0].appendChild(script);

And the DOMSanitzer runs and removes it... so now i am clueless

@pratikthecook — If you have a CDN hosted library, then I think it would make sense to have the consuming application include the script to load the dependency. Would that work in your scenario?
Or do I misunderstand your question? Thanks!

Yes, but that would burden the consuming application developer to include every single JS from CDN into his/her app. Here's The link to library created using your generator(its a pretty awesome generator :1st_place_medal: ) Amexio so now i need lot of stuff which i dont want the user to burden rather inject it the module itself.
Hope i made the point clear. Thanks

In my case I am directly pointing to node_modules/my-library/assets/3party.js in angular-cli or in the head of index.html

@pratikthecook  I have found this thread may be of help to you Load JS Script in Angular2+
You cannot reference DOM directly in Angular 4 components. You will either need to use ref elements, or indirectly access DOM using JQuery. I have a Example project that demonstrate how to setup JQuery in projects created by generator-angular2-library.

@kktam Thanks for your input, ive implemented it and then calling to scripts method on certain observables. please check the below https://github.com/meta-magic/amexio.github.io/blob/v2.0/src/modules/charts/src/chart.loader.service.ts
Since the issue is resloved i am closing this issue.

@kktam Hi, Have you ever used jquery-ui in projects created by generator-angular2-library?


Require php calendar extension to prevent breaking sites

I've accidentally taken down a production site because the server did not have the calendar extension installed, and I was not aware that I needed it (or that it existed actually).
Since it's a hard dependency for the library to function, that should be more obvious :-)

@Jarlskov Sorry to hear that your site was taken down because of this :( You are correct that it is not clear that the calendar extension is actually required. If I recall, I wanted to stay away from such dependency but think I ended up using it anyway.
Your PR is good in that it will enforce the use of the calendar extension. Now that I am thinking of it, I think I want to provide an implementation of the easter_days function within Yasumi that would replace the need for the extension after all.

No worries, that's our own fault. We were able to roll back quickly, and it showed some flaws in our test procedures :-)
I'm not sure why you would want to maintain existing functionality, but that's up to you how you want to solve it, but I think it would make sense to add something like this until you get around to implementing the easter_days functions. I don't believe this PR should cause any BC breaks.

Ah yes, I see. Merging this PR will indeed not cause any BC issues. Implementing a easter_days function as part of Yasumi isn't that difficult and planning on releasing it pretty soon :)

Fallback easter_days calculation implemented in case the PHP calendar extension is not loaded. (See PR #55)


Feature triangle 2 rectangle animation

What follows is not a finished solution. Joy made a big push to introduce new functions to the codebase. This is pull animation out of the code.
SVG transforms
In the following example, SVG transforms are used to move the cuts from the canonical triangle operation "back" into their parent triangle. SVG transforms can be run through an interpolation function to easily tween polygons between different positions in sufficiently high resolution so as to produce smooth movement; therefore, it makes sense to store information for each polygon that can easily be used to feed into SVG transforms for visual presentation.  Here, no tween is used: one transform is applied to render polygons resulting from the triangle2Rectangle operation in a different position than their base coordinates place them.

Here is the SVG expression of the path for the orange triangle
![screen shot 2016-04-09 at 2 49 11 pm]
(https://cloud.githubusercontent.com/assets/3190945/14405705/436b54b4-fe62-11e5-8efa-9057b2c7c57d.png)
Relative to its parent DOM element, the path for the orange triangle is rotated around a point by 180 degrees counter-clockwise.
The same approach could be used for the triangle-to-rectangle cut performed using Shenghan's method.
Data Structure
The current data structure for polygons that are generated from some type of cut operation relies on extra properties added to JavaScript arrays that hold the coordinate tuples of polygons.
A polygon is an array of position tuples with the following extra properties (Objects):

parent
transform

rotation (optional
pivot (optional)
translate (optional)

The idea here is to store not a transformation matrix, but the information which could be used to perform an SVG transform OR create a transformation matrix on-the-fly from the properties stored on the polygons. For example, a triangle in the above example is built from this underlying data:

And that's as far as I got.


Upgrade Sphinx

Refs #1971

:books: Documentation preview :books:: https://datasette--1984.org.readthedocs.build/en/1984/

Preview at https://datasette--1984.org.readthedocs.build/en/1984/ looks good to me.


Insufficient validation of proxy settings

The check for proxy system properties is not sufficient. There should not only be a null check but also a check for empty strings:
https://github.com/stevespringett/nist-data-mirror/blob/5e5ef4ad779d74820bdd250d0dc00c691128e4e2/src/main/java/us/springett/nistdatamirror/NistDataMirror.java#L96
This is because in the mirror.sh script which is executed in the Docker environment the proxy properties are always being set. In case no proxy_hostor proxy_port environment variable is set the http.proxyHost or http.proxyPort JVM properties are set to an empty string:
https://github.com/stevespringett/nist-data-mirror/blob/5e5ef4ad779d74820bdd250d0dc00c691128e4e2/src/docker/scripts/mirror.sh#L3

Released in v1.4.0


Dockerfile can be a lot more simple

https://github.com/GoogleCloudPlatform/functions-framework-dart/blob/3b4d7ca01ad4a3c09884aef46c0539f69b6f505f/Dockerfile#L5-L15
We don't need mono_repo. We can just run pub get on the example app directory. Everything else is not needed.

Sounds good!

Thanks, good call on removing mono_repo. Still need to copy the pubspecs for it to build and cache all the deps, but after that, unless pubspecs get updated, only need to build new image layers based on modified sources and cached deps.


Add LoadedImage::file_path

This change add support for getting the file path of the loaded image.

Hello! CI is currently failing for the latest main branch because of some nightly changes, but as soon as that gets fixed we should be able to review and merge your changes 😄


Rewrite Puzzle solved_times using ORM

assuming that we maintain that is_solved returns true iff at least one correct answer is present

I've included the unit test under puzzles/tests.py, which seems more sensible than including it in answers/tests.py, but let me know if I'm wrong about that.

I've included the unit test under puzzles/tests.py, which seems more sensible than including it in answers/tests.py, but let me know if I'm wrong about that.