FileTarget - RetryingMultiProcessFileAppender should use BufferSize=1024

Logger Name
Messages
Size
Threads
Loggers

PerfSyncLogger
10.000
16
1
1

BufferSize
Time (ms)
Msgs/sec
GC2
GC1
GC0
CPU (ms)
Mem (MB)

32768
26.918
371
0
1
22
3.312
36,332

4096
26.745
373
0
0
3
3.203
35,680

1024
26.433
378
0
0
1
3.093
35,496

This change is

Current coverage is 82% (diff: 100%)

Merging #1864 into master will decrease coverage by <1%

@@             master      #1864   diff @@
==========================================
  Files           276        276
  Lines         18472      18471     -1
  Methods        2857       2856     -1
  Messages          0          0
  Branches       2129       2130     +1
==========================================
- Hits          15061      15055     -6
- Misses         2922       2928     +6
+ Partials        489        488     -1

Powered by Codecov. Last update fa1eb2d...00324e9

Less then 2% improvement. Not sure if this benefit is large enough. What do you think?
Reason not the merge:

possible slower in other configurations
buffersize is "dynamic", more difficult to document

Tried some testing with the FileTarget within the AsyncWrapper, and the improvement was also small there. Will close this.

@tlaguz Regarding " Unhandled exception when writing to file". Consider changing your NLog-File-Target to use keepFileOpen="true" or specify bufferSize="1024". This will avoid the allocation of 30 KByte buffer for every log-event-write-operation.

@tlaguz Regarding " Unhandled exception when writing to file". Consider changing your NLog-File-Target to use keepFileOpen="true" or specify bufferSize="1024". This will avoid the allocation of 30 KByte buffer for every log-event-write-operation.

Superseeded by #3444


Fix urlize ietf docs

The old code would first substitute the rfx<nnnn> part, and then again
on the full draft name. This now only ever applies one substitute,
and does longer ones first.

You're right; I didn't check a block of text with multiple replaceable things. Let me rework this.

@rjsparks take another look?

Still not where you want to be I think. You (or I could if you want) should really add a unittest for this urlize function.
>>> re.sub(r"(?<!>)\b(RFC\s*?)0{0,3}(\d+)\b", "\\1\\2", "draft-ietf-rfc9999-bis-01", flags=re.IGNORECASE)
'draft-ietf-rfc9999-bis-01'

@rjsparks over to you :-)


Broken Label on Selectize

control-label is needed on the selectize label
need to add selectize to the readme

Selectize is no longer used


Why @types/es6-shim and not these from TypeScript

@DxCx

what do you mean those from typescript?
we removed babel and now typescript compiles straight to es5.
you are welcome to open a PR to remove es6-shim if it's not needed. 👍

Closed by #280

@DxCx Could we release it before v0.10.0 of apollo-angular? :)))))))))
So I don't have to use @types/es6-shim and do non-standard things in tsconfig? https://github.com/kamilkisiela/apollo-angular-reproduction/pull/2/files

Thats @helfer :)

@helfer :moneybag: :dollar:  :money_with_wings: :hourglass_flowing_sand:

Should I release?


[ISSUE] - Infinite loop when "cancelling" 2FA setup.

Hello,
If you reach the page in the first image, you can't cancel the 2FA setup. If the person leaves the page, every time they enter in their accounts, they get sent back to the "Enter mobile number page" in the second image.

Duplicate of #50


Fixes #2254 Don't lookup or reload the versioned clientlibs cache due…

… to a referenced static js/css resource
And some small code fixes along the way.

Pull Request Test Coverage Report for Build 5570

4 of 7 (57.14%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.001%) to 56.124%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bundle/src/main/java/com/adobe/acs/commons/rewriter/impl/VersionedClientlibsTransformerFactory.java
4
7
57.14%

Files with Coverage Reduction
New Missed Lines
%

bundle/src/main/java/com/adobe/acs/commons/mcp/impl/ProcessErrorReportExcelServlet.java
1
66.22%

Totals

Change from base Build 5518:
0.001%

Covered Lines:
15369

Relevant Lines:
27384

💛  - Coveralls


Implement aggregated datacenter metrics

Add flag to use aggregated datacenter metrics instead of per-datacenter.
Remove the datacenter label when aggregation is enabled. This removes the unnecessary label and is consistent with how aggregated metrics should be represented.
Ref: Issue #152

@leklund Would you be able to do a preliminary review, please?

@mikelorant Sorry this has been sitting for so long. I'll take a look at this early next week.

@leklund Thanks for the all the feedback!
All your points make sense and I am happy to make all the changes you requested. I'll expect to have your requested changes implemented by the time you get back.

Breaking this pull request up into smaller pieces.

Refactor labels used in realtime package

@mikelorant Thanks for the new PR! I spent some time looking at this today and had some thought/ideas. Left a summary at the top because it got long.
Summary
I had a realization that instead of adding complexity to remove the datacenter label you could instead just use a constant for the datacenter and it will have the same desired effect of reducing the /metrics response size. It could also skip the datacenter iteration completely and just use the Aggreagate field from the Response struct (that's the last sample code at the very bottom).
Details
I was curious about performance with all the extra map allocations. I wrote a simple benchmark for Process():
main branch:
pkg: [github.com/fastly/fastly-exporter/pkg/realtime](http://github.com/fastly/fastly-exporter/pkg/realtime)
BenchmarkProcess-12    	    2840	    419057 ns/op	    1883 B/op	      57 allocs/op

mikelorant:refactor/labels using mergeLabels:
pkg: [github.com/fastly/fastly-exporter/pkg/realtime](http://github.com/fastly/fastly-exporter/pkg/realtime)
BenchmarkProcess-12    	    1012	    999219 ns/op	  264528 B/op	    1640 allocs/op

I haven't tested out the real-world implications but it could be noticeable if you happen to use the exporter with a large number of service.
I did a quick pass to use a slices instead of the map and it's better:
pkg: [github.com/fastly/fastly-exporter/pkg/realtime](http://github.com/fastly/fastly-exporter/pkg/realtime)
BenchmarkProcess-12    	    2558	    465463 ns/op	   74551 B/op	     815 allocs/op

That last benchmark used this code:
func Process(response *Response, serviceID, serviceName, serviceVersion string, m *Metrics) {
	labels := make([]string, 3, 3)

	labels[0] = serviceID
	labels[1] = serviceName

	for _, d := range response.Data {
		for datacenter, stats := range d.Datacenter {
			labels[2] = datacenter
			process(labels, stats, m)
		}
	}
}

func process(labels []string, stats Datacenter, m *Metrics) {
	...
	m.StatusCodeTotal.WithLabelValues(append(labels, "200")...).Add(float64(stats.Status200))
	...
}

I also tried a version where I used the prometheus.Labels map and would add the extra labels and then delete the key as after use. It's not very elegant but was slightly better memory-wise than the slices.
pkg: [github.com/fastly/fastly-exporter/pkg/realtime](http://github.com/fastly/fastly-exporter/pkg/realtime)
BenchmarkProcess-12    	    1513	    787019 ns/op	   31202 B/op	     241 allocs/op

It looked like this:
labels["status_group"] = "1xx"
m.ComputeRespStatusTotal.With(labels).Add(float64(stats.ComputeRespStatus1xx))
... etc.
delete(labels, "status_group")

While exploring ways to optimize this I had a realization. This code is still iterating over the per-datacenter metrics and incrementing counters. Instead I think it could just use the Aggregated metrics that are returned by the real-time API and only increment once. The datacenter label could still exist just with the value of "aggregated". This means not adding complexity to the metric initialization and we can retain the same Process() func. In fact, the simplest approach would be to just change the datacenter name to "aggregated" and keep the label.
const aggdc = "aggregated"

func Process(response *Response, serviceID, serviceName, serviceVersion string, m *Metrics, aggOnly bool) {
	for _, d := range response.Data {
		for datacenter, stats := range d.Datacenter {
			if aggOnly {
				datacenter = aggdc
			}
		// increment all the metrics
	}
}

or using Aggregate:
const aggdc = "aggregated"

func Process(response *Response, serviceID, serviceName, serviceVersion string, m *Metrics, aggOnly bool) {
 	 for _, d := range response.Data {
		if aggOnly {
			process(serviceID, serviceName, aggdc, stats, m)
		} else {
			for datacenter, stats := range d.Datacenter {
				process(serviceID, serviceName, datacenter, stats, m)
			}
		}
	}
}

func process(serviceID, serviceName, datacenter string, stats Datacenter, m *Metrics) {
	// increment all the things
	 m.ComputeRespStatusTotal.WithLabelValues(serviceID, serviceName, datacenter, "1xx").Add(float64(stats.ComputeRespStatus1xx))
	// etc
}

Since my last comment was very long and rambling I thought it might help to put my idea into code:
https://github.com/fastly/fastly-exporter/compare/agg-only?expand=1

On first pass, I totally agree with you on the new approach. My initial implementation was about just setting the datacenter to aggregated but I was expecting to be rejected because it seemed lazy and instead decided to do the proper implementation of removing the label.
How much refinement do we need to your branch to turn it into something functional? I assume we need to make it work for domain and origin metrics as well as do the flag work?
I really am hoping to convince you based on the metrics that defaulting to per datacenter is a bad idea. The cardinality explosion is so major, that if you have hundreds of active services you are going to swap yourself in metrics. Add this in to the cost of using domain and origin inspector and you are multiplying out yet again.
This is the type of breaking change that I feel would be beneficial to all users. Make them opt-in to datacenter metrics if they need that detail. I doubt most realise how costly it is and likely doesn't provide tangible benefits.

On first pass, I totally agree with you on the new approach. My initial implementation was about just setting the datacenter to aggregated but I was expecting to be rejected because it seemed lazy and instead decided to do the proper implementation of removing the label.

While it does seem a little off to use "aggregated" as the datacenter I do like the simplicity of that implementation. I also like that it doesn't break existing dashboards that might rely on the datacenter label. I agree that the ideal case would probably be to remove the label completely but I try to be pragmatic about these things.

How much refinement do we need to your branch to turn it into something functional? I assume we need to make it work for domain and origin metrics?

We need to update the Readme/documenation, add support for domains/origins, and add any test cases I missed.

I really am hoping to convince you based on the metrics that defaulting to per datacenter is a bad idea. The cardinality explosion is so major, that if you have hundreds of active services you are going to swap yourself in metrics. Add this in to the cost of using domain and origin inspector and you are multiplying out yet again.
This is the type of breaking change that I feel would be beneficial to all users. Make them opt-in to datacenter metrics if they need that detail. I doubt most realise how costly it is and likely doesn't provide tangible benefits.

It's definitely a high-cardinality set of metrics and I'm sure there are other users like yourself that would benefit from the smaller set of aggregate-only metrics. But I also know users that rely on the per datacenter information so I am reluctant to make this breaking change.
Even if this is not the default I think we can add a prominent note in the README on using the new flag to reduce cardinality.

We need to update the Readme/documenation, add support for domains/origins, and add any test cases I missed.

Sounds like this is the path forward then.
Happy to help with copying the implementation and adding the same code to both origin and domain.

Happy to help with copying the implementation and adding the same code to both origin and domain.

Thank you, that would be great! Feel free to copy/modify what I quickly wrote and add it origins/domains.

Have created the initial pull requests to prepare for the feature:

#168
#169

I was then able to take your branch and extend it to add support for the domain and origin systems. I did some minor refactoring to reduce indentation and remove the global.
You can see the results on my feature/aggregate-only branch.
Be aware, this branch by itself does not pass unit tests until we merge #168. My plan is that once both #168 and #169 are merged, is to update this existing pull request with the code from that branch and NOT open a new pull request.

This is now the new implementation as we discussed.
Note that there is no documentation yet, if you are happy with this approach, I will add them.

Outstanding tasks:

[ ] Add documentation.

Preliminary documentation (modified version of what we previously had) was added. I think it would be wise to educate the users of the benefit of enabling this feature and how much of an impact this can have on reducing the number of time series emitted.

Wording has been changed to your recommendations.
Been a long road to get this pull request to where we want it, but it seems we finally have something worthy of merging!

@mikelorant Thanks for your patience and all the work you did in getting this merged! I'll cut a new release asap.

Thanks so much for your efforts in getting this implemented. Been a great learning process and the solution implemented will really benefit users will large number of services.


[client] expose builtin features and connection

I am working on a new version of monaco-languageclient to catch it up with vscode-languageclient: https://github.com/TypeFox/monaco-languageclient/pull/89
And for it, I have to customize how a connection is created and which features are enabled by default.
cc @dbaeumer

Another case for it: a client wants to provide a custom implementation of some features. For example to narrow command registration to a specific editor.

I have to say I am actually against this. Making them API means that we need to keep them stable and maintain them. main.ts has currently a statement export * from './client'; which would make them official API.
If people want to remove feature and replace them with different once we need to offer API to remove features based on a RPCMessageType

The protocol npm module does contain methods to create connections. So I am wondering if it wouldn't be better to base the monaco client on the protocol and see if we should move things there instead of reusing the VS Code client which is based on the assumption to have full access to the VS Code API.


rdt: implement SetConfigFromFile

It would be nice to synchronize rdt and blockio interfaces on configuration file handling.
Currently in the draft PR #30 the blockio has functions
// LoadSystemConfig looks for a default system configuration file for
// containers/blockio. Returns parsed configuration that can be
// applied with SetConfig().
func LoadSystemConfig() (*Config, error)
// LoadConfigFile loads configuration from a file. Returns parsed
// configuration that can be applied with SetConfig().
func LoadConfigFile(filename string) (*Config, error)
// ParseConfigYaml returns new configuration parsed from yaml.
func ParseConfigYaml(data []byte) (*Config, error)
// SetConfig scans available block devices and applies new configuration
func SetConfig(opt *Config, force bool) error

(I'm not too happy about the ParseConfigYaml name. Maybe it should be LoadConfig[From]Data.)
In this PR you combine loading and applying the configuration. Use cases that I had in mind in splitting Load/Set were that the user (cri) may wish to handle separately I/O/parse errors and configuration errors, or may wish to validate/override parts of a configuration before applying it. I don't know if these use cases are realistic enough to justify separating Load/Set primitives instead of offering different flavors of Set-primitives. Maybe going with a simple pair SetConfig() / SetConfigFromFile() would indeed be enough for now. Possibly extended with SetConfigFromData() to allow enough freedom for configuration data retrieval from any source (network, embedded data, unit/e2e test...).
Another question is, do you think goresctrl modules should offer functions like SetConfigFromSystem()? For instance, blockio PR's LoadSystemConfig() tries to find a configuration file in "standard" locations:
var BlockIOConfFiles = []string{
	"$CONTAINERS_BLOCKIO_YAML",
	"$HOME/.config/containers/blockio.yaml",
	"/etc/containers/blockio.yaml",
	"/usr/share/containers/blockio.yaml",

Any insights on these? I'm fine going either way in both cases. I just wish I had a working crystal ball.

Thanks for the thoughtful review @askervin!

It would be nice to synchronize rdt and blockio interfaces on configuration file handling.

Agree!

Currently in the draft PR #30 the blockio has functions
// LoadSystemConfig looks for a default system configuration file for
// containers/blockio. Returns parsed configuration that can be
// applied with SetConfig().
func LoadSystemConfig() (*Config, error)
// LoadConfigFile loads configuration from a file. Returns parsed
// configuration that can be applied with SetConfig().
func LoadConfigFile(filename string) (*Config, error)
// ParseConfigYaml returns new configuration parsed from yaml.
func ParseConfigYaml(data []byte) (*Config, error)
// SetConfig scans available block devices and applies new configuration
func SetConfig(opt *Config, force bool) error

(I'm not too happy about the ParseConfigYaml name. Maybe it should be LoadConfig[From]Data.)
In this PR you combine loading and applying the configuration. Use cases that I had in mind in splitting Load/Set were that the user (cri) may wish to handle separately I/O/parse errors and configuration errors, or may wish to validate/override parts of a configuration before applying it. I don't know if these use cases are realistic enough to justify separating Load/Set primitives instead of offering different flavors of Set-primitives. Maybe going with a simple pair SetConfig() / SetConfigFromFile() would indeed be enough for now. Possibly extended with SetConfigFromData() to allow enough freedom for configuration data retrieval from any source (network, embedded data, unit/e2e test...).

Mm, I didn't see any immediate user for the "SetConfigFromData" variant so didn't implement that 🙄 But good point that it could be useful in some scenarios and implementing that is basically "free", just separating part of SetConfigFromFile into another function. I'll do that.

Another question is, do you think goresctrl modules should offer functions like SetConfigFromSystem()? For instance, blockio PR's LoadSystemConfig() tries to find a configuration file in "standard" locations:
var BlockIOConfFiles = []string{
	"$CONTAINERS_BLOCKIO_YAML",
	"$HOME/.config/containers/blockio.yaml",
	"/etc/containers/blockio.yaml",
	"/usr/share/containers/blockio.yaml",

Any insights on these? I'm fine going either way in both cases. I just wish I had a working crystal ball.

Hmm, I'm not sure, at least at this point 🤔 The library is not strictly limited to container applications so at least the path should be something different, I think.

Added SetConfigFromData()
Forgot to comment about the parsing (ParseConfigYaml or similar) functions. I don't necessarily see those as useful because at least in RDT case JSON unmarshal is enough. I've a patch for adding a separate Config.Validate() function, though, in order to check if a certain config if applicable in the underlying system.


"The active test run was aborted. Reason: Test host process crashed" with no further explanation

Description
This test run calls dotnet test, which then outputs
The active test run was aborted. Reason: Test host process crashed
Results File: /home/runner/work/dafny/dafny/dafny/Source/IntegrationTests/TestResults/_fv-az446-243_2023-04-06_10_29_09.trx

Test Run Aborted with error System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read beyond the end of the stream.
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---.

Looking at the referenced results file (here), there is no indication of anything going wrong.
How can I get a clue of what caused the test host process to crash? Are there particular exceptions that would cause it to crash in this way such as out of memory or stack overflows?
Steps to reproduce
I don't have a small reproduction example, but this issue occurs when the CI for this PR is run
Expected behavior
I expect some sort of stack trace or explanation of why the test host process crashed, that doesn't point to from the test host process such as Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync
Actual behavior
No explanation is given
Diagnostic logs
Environment
Occurs on Ubuntu

We've started getting this since around 6th april 10:30 GMT, across unrelated topic branches so appears not due to a change we've made.  We use dotnet install scripts ./dotnet-install.sh --channel 7.0 --install-dir /usr/share/dotnet so will pull anything new on there, has anything happened super recently?

You can add --diag:logs/log.txt to your run and that should give your more information. Also depending on the version of TestPlatform you are using, we may fail to capture the info on the process crash, because the Exit event comes before the output is flushed (only on Linux), so we fail to capture that error output on older versions of TP (pre 17.4 I think).
You can also add --blame-crash to see if that crash will produce a memory dump, and then analyze that with dotnet dump analyze https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump#dotnet-dump-analyze

We've started getting this since around 6th april 10:30 GMT, across unrelated topic branches so appears not due to a change we've made. We use dotnet install scripts ./dotnet-install.sh --channel 7.0 --install-dir /usr/share/dotnet so will pull anything new on there, has anything happened super recently?
Edit: Could this be related a change in .NET sdk 7.0.104 somehow reaching us around this time?
Edit2: No, I can't see any differences in the sdk, runtime or install-scripts.sh versions that got pulled between passing and failing builds. Will try disabling running in seperate process so I can see the actual error hopefully.

Right after updating SDK 6 to 6.0.311 (the latest), I'm getting a very similar error when testing unrelated branches/old commits that previously ran fine. So I have a strong suspicion it may be a recent change incorporated into multiple parallel SDK versions.
The active test run was aborted. Reason: Unable to communicate with test host process.
Test Run Aborted with error System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Exception: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   at System.Net.Sockets.NetworkStream.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---.

Full disclosure:  The test host was being terminated due to out of memory.  No idea why this suddenly started happening unless there's been a sudden change to the GC; but also made sure versions are pinned to same as when everything was passing, and the issue persists.  So this one might be on us.

I'm having exactly the same issue running in a BitBucket pipe line with:
.NET: 7.0.203
Microsoft.NET.Test.Sdk: 17.5.0

I had very similar issue to this one.
It turned out, that I was throwing exception in async void method. It seems that since Exceptions in async void methods are handled outside of caller context, than it broke dotnet test.
Changing method signature to async Task FuncName() solved the problem.

In my case, I replace below code:
[ClassInitialize] public static void ClassSetup(TestContext context) {     .... }
with:
public className ( )  {      ... }
and it resolved the issue.

Likely dupe of
#2952
Super frustrating that the vstest team does not seem to think the lack of diagnosabiliy here is a priority. I've wasted hours and hours on this.


[Channel Tab] Request: a better tab view for MacOS

Describe the solution you'd like
Move the < > x channels to the same place beside the 3 buttons

btw on chrome


Solve typescript 3.1.x compatibility issues for babylonjs 3.3 release

This PR will solve typing incompatibilities with typescript v3.1.3 (between lib.dom.d.ts and babylon.d.ts) which is the minimum required version of typescript for Angular 7 applications.
If possible I would like to see this PR result in a v3.3.1 of Babylon.js. Please provide further guidance if there are any other changes necessary.

No problem to merge in 4.0 but we  will not create a 3.3.1 for it (you can still get the tag and build your own if required but I would highly recommend take the 4.0 as it is as stable as the 3..3.)

Okay, seems like 4.0 will work for me and already has these fixes applied. However, I was a bit concerned switching to the preview versions again. I did that with 3.3 to test it early and it took almost until the final release to get the GTLF texture glitches solved there.

Well we close bugs in less than 48h on the preview branch so if you have any issue just open a bug and we will fix it


Fix: go vet errors for unreachable code

Also fixes the path for the unit test script to pushd into.

Covered in #80


ci: create preview release on merge to "develop"

close #847

It may be too much noise in the releases area for every PR. Let's scale it back to only publish on tag or create artifacts in AzDO and then can release from there?

ok change to manual queue only.


Submit form on every field change

I have a form with inputs and custom inputs and want on every change save form. In documentation for custom fields I see
<MyStrangeInput
        currentValue={{val: myField.value}}
        thingsChanged={param => myField.onChange(param.val)}/>

But on every change I want change value in form.store and run handleSubmit. I try to do this in the next way
<input
     {...fields.name}
     onChange={(data) => {
         fields.name.onChange(data);
         setTimeout(()=> handleSubmit());
     }}
/>

If I remove setTimeout function I got previous not actual value in onSubmit function.
How I can do that in more pretty way?

One more thing, after updating initialValues variable I got action redux-form/INITIALIZE @ 16:35:10.924, my form handle all changes (I see actions in console) but in input field I didn't see any changes.

Yes, that's because handleSubmit() submits the data that the react-redux connector has given your form as props from the Redux state, which is not available until the next render. You will have to merge the new value into the existing values yourself.
<input
  {...fields.name}
  onChange={event => {
    fields.name.onChange(event); // takes event or value
    handleSubmit({
      ...this.props.values,
      name: event.target.value
    });
  }}
/>

i found a good way to get form values on every field change
componentWillReceiveProps(nextProps){
  if (nextProps.dirty && nextProps.valid && nextProps.values !== this.props.values) {
     this.onFormFieldChange(nextProps.values);
    }
}

@CosticaPuntaru thanks!

@erikras it seems like "merging values by myself" not working anymore?

@iNikNik I'm going to need more information about exactly what is happening.

@erikras I believe API was changed and now handleSubmit look lile:
 handleSubmit(eventOrSubmit) : Function

And I can't pass form values:
handleSubmit({
      ...this.props.values,
      name: event.target.value
    })

Wy input onChange can not update store synchronously? I would like to attach handleSubmit  to onBlur event and there is only one way (proposed by @max-mykhailenko) to do this in case of having some level of abstraction.
const onBlurHandler = (event: any) => {
    if (!input.value && defaultValueIfEmpty) {
        input.onChange(defaultValueIfEmpty);
    }
    if (field.onBlur) {
        setTimeout(() => field.onBlur(event));
    };
};

return (
    <input {...field.input} {...rest} className={cssClassName} onBlur={onBlurHandler} />
);

With 6.0.0-alpha.4 works something like that:
class YourComponent extends React.Component {
  componentWillReceiveProps(nextProps) {
    const { values, handleSubmit } = nextProps
    if (this.props.values !== values) {
      handleSubmit(this.onSubmit)()
    }
  }

  onSubmit = (values) => {
    // Here u can change values as u want
    if (this.props.onSubmit) this.props.onSubmit(values)
  }

  render() {
    const { handleSubmit } = this.props
    return (
      <form onSubmit={ handleSubmit(this.onSubmit) } }>
        ...
      </form>
    )
  }
}

const formName = 'YourForm'

function mapStateToProps(state) {
  return {
    values: _.get(state.form, `${ formName }.values`, {})
  }
}

export default compose(
  connect(mapStateToProps)
)(YourComponent)

Hello there!
Thanks for your hard work!
How about 6.7 version of redux-form? I have this code:
function renderCombobox({ input, meta, ...rest }) {
  return (

    <Combobox
      {...input}
      placeholder={input.name}
      {...rest}
    />
    {meta.touched &&
      ((meta.error && {meta.error})
          // || (warning && {warning})
      )}

);
}
//somewhere in my form
            <Field
              name='repo'
              component={renderCombobox}
              data={['repo1', 'repo2', 'repo3', 'repo4', 'redux-app1']}
              required
              onSelect={(value) => {
                props.change('repo', value);
                props.submit('leftSearch');
              }}
              filter='startsWith'
              handleSubmit={props.handleSubmit}
            />

The problem that the form submits old values when call submit on onSelect of Combobox component.  How i should call submit to submitting actual values?
P.S. sorry for my bad english.

Is there any on the works for this? maybe a callback on onBlur, maybe a promise?

))) i just use setTimeout. With it don't change value also. Because it updates before submit's invoke.

This is my implementation with the new form onChange prop.  Couldn't find this spelled out anywhere.
<form onChange={() => setTimeout(handleSubmit(params => yourHandler(params)))}>

@jbschrades where did you find docs about onChange on  component?

@damianobarbati I don't remember honestly.  I think I was going off https://github.com/erikras/redux-form/pull/2576

In redux-form 7, I am passing an onChange callback to reduxForm which invokes props.submit(). This is working for my use case. You could use the values and previousValues parameters to only submit when certain fields are changed.
export default reduxForm({
    form: 'myForm',
    onChange: (values, dispatch, props, previousValues) => {
        props.submit();
    },
})(MyFormComponent);

try to declare a variable outside of your form component and debounce on your reduxForm options
let timeout = null;  // declare outside of your component
export default reduxForm({   form: 'myForm',   onChange: (values, dispatch, props) => {     clearTimeout(timeout);     timeout = setTimeout(() => props.submit(), 1500);   }, })(MyForm);

@HristoKolev - glad you got it sorted out. Just to confirm, this was working for me in 7.2.x and still works in 7.3.0.

I believe this is an more idiomatic way to do that
const form = 'SystemControls';

SystemControls = reduxForm({
  form,
  onChange: (values, dispatch) => {
    dispatch(submit(form));
  },
  onSubmit
})(SystemControls);

If i do that i get: Uncaught Error: You must either pass handleSubmit() an onSubmit function or pass onSubmit as a prop

If i do that i get: Uncaught Error: You must either pass handleSubmit() an onSubmit function or pass onSubmit as a prop

same here :(

In redux-form 7, I am passing an onChange callback to reduxForm() which calls props.submit(). This is working for my use case. You could use the values and previousValues parameters to only submit when certain fields are changed.
export default reduxForm({
    form: 'myForm',
    onChange: (values, dispatch, props, previousValues) => {
        props.submit();
    },
})(MyFormComponent);

in this onChange func how can I call a function that is in my component?, I mean to do things in there, like update another field based in other value.

I'm using 8.1.0, and doing it like this:
export default reduxForm({
   form: 'myForm',
   onChange: (values, dispatch, props) => {
       props.submit()
   }
})(MyFormComponent)

doesn't completely solve it. Since the submit() is synchronous, it performs the submission before onChange is complete, so your form gets submitted with old values.
My (awful) solution is to setTimeout(() => props.submit(), 0) to make sure it waits until onChange finishes. Is there a better way?

Can be done with lodash
const createReduxForm = reduxForm({
form: 'listingForm',
onChange: Lodash.debounce(onChange, 500),
validate: validation_all,
});


Activities : Listing

Without Filters
Without View Changement

marked this issue as related to #12

marked this issue as related to #13


How to deal with issues caused by the switch from project.json to the .csproj equivalent

My previous post is related to this (although both could belong in a different docs repo). Both posts try to indicate a need for a document that handles all problems related to subject line above.
I am encountering warning messages like Detected package downgrade: Microsoft.NETCore.App from 1.1.0 to 1.0.3 after changing the target framework to the most current dotnet core:

It is by no means obvious what to do here - because the process of editing the .csproj file

is not "interactive" as project.json was. Ideally, I would like a helper tool that could guide me through process of selecting the optimal collection of compatible parts (by version number).
A good document explaining the issue in this "transition time" would be of great value.

With the RTM of VS2017 this should all be handled by the dotnet migrate command (or the project upgrade experience when you open an xproj in VS2017). This includes bumping up your tools version to the csproj compatible version (which will be a stable 1.1.0 release of tools, not a preview).
If you have a situation where the RTM doesn't handle this, then please open an issue on our product repository - https://github.com/aspnet/EntityFramework.


⚠ SceneTime has degraded performance

In 09a9033, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1986 ms

Resolved: SceneTime performance has improved in 2f7597c after 21 minutes.


[20.03] texworks: fix qt build

Motivation for this change
backport of https://github.com/NixOS/nixpkgs/pull/82873
Things done

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

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

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

https://github.com/NixOS/nixpkgs/pull/82917
1 package built:
texworks

previous behavior:
[12:06:35] jon@jon-desktop /home/jon/projects/nixpkgs (release-20.03)
$ ./result/bin/texworks
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted (core dumped)

PR behavior:
[nix-shell:/home/jon/.cache/nixpkgs-review/pr-82917-2]$ ./results/texworks/bin/texworks
# opens successfully


Please use versionned shebang for bin scripts

Many distribution do not provide /usr/bin/python anymore when python2 is not installed.
Binary scripts should use a versionned shebang. The fix is trivial:
--- django-mezzanine.orig/mezzanine/bin/mezzanine_project.py    2021-08-17 16:29:56.672828121 +0200
+++ django-mezzanine/mezzanine/bin/mezzanine_project.py 2021-08-17 17:52:59.403433003 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
 import sys

 from django.conf import settings

Thanks! Would you be interested in contributing a pull request?

Sorry, I checked with django and it looks like they use the generic python in the shebang. Our manage.py file is just a copy of that so we'll just follow their lead there.
I'm assuming once a virtualenv is active (or any other isolation layer) the python executable is bound correctly.


request: HTTP file system

It would be convenient to be able to do open_files on a list of HTTP URLs. This cannot be a complete file-system like the other backends, because there is no possibility of glob(), but I still think it would be useful for accessing remote data.
In general, the size of a given URL's data can be found through a HEAD command, and chunks read using the Range header keyword; some servers do not support that, however, and then downloads could only be parallelised across multiple files.

I agree that this would be a useful thing to have
On Sun, Feb 11, 2018 at 4:35 PM, Martin Durant<EMAIL_ADDRESS>wrote:

It would be convenient to be able to do open_files on a list of HTTP
URLs. This cannot be a complete file-system like the other backends,
because there is no possibility of glob(), but I still think it would be
useful for accessing remote data.
In general, the size of a given URL's data can be found through a HEAD
command, and chunks read using the Range header keyword; some servers do
not support that, however, and then downloads could only be parallelised
across multiple files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3158, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszPzvmmiRwRVdCUlvFZ0SJE63eX0Oks5tT107gaJpZM4SBhJV
.

I'm curious, is there a particular use case that you had in mind?
On Sun, Feb 11, 2018 at 5:22 PM, Matthew Rocklin<EMAIL_ADDRESS>wrote:

I agree that this would be a useful thing to have
On Sun, Feb 11, 2018 at 4:35 PM, Martin Durant<EMAIL_ADDRESS>wrote:

It would be convenient to be able to do open_files on a list of HTTP
URLs. This cannot be a complete file-system like the other backends,
because there is no possibility of glob(), but I still think it would be
useful for accessing remote data.
In general, the size of a given URL's data can be found through a HEAD
command, and chunks read using the Range header keyword; some servers do
not support that, however, and then downloads could only be parallelised
across multiple files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3158, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszPzvmmiRwRVdCUlvFZ0SJE63eX0Oks5tT107gaJpZM4SBhJV
.

Yes, I am looking at archival astro data in FITS format, where the extensions can be addressed independently, and, for uncompressed data, you can slice the binary data directly.
Also, in the case of Intake, many data resources (and possibly their schemas) are available via a URI that may be HTTP or something else, and we'd like to use just one function to generate file-like objects for them.
It is worth noting that some loading functions like pd.read_csv already support HTTP (I don't know if that is done chunk-wise, though).


Allow filtering graphql queries with enum types

Emulate the publication_type filtering in work.publications() for other objects that have a type/custom_enum:

[ ] work (work_type, work_status)
[ ] publication (publication_type)
[ ] subject (subject_type)
[ ] price (currency_code)
[ ] language (language_code, language_relation)
[ ] series (series_type)
[ ] contribution (contribution_type)

Also add filtering by doi (string, not enum) to work() - possibly as a separate query


Parallel Processing Slows Down 'create_ras_terrain'

If I use an S3 VRT as a source terrain, the performance worsens with increasing thread count in ripple API even though CPU/RAM utilization is below 5%. My first thought is this is because of RasterIO/GDAL competing for resources (such as file handlers for 100s of individual tiles in the VRT). I tried a Local Tiff as a source raster and it worked fine.
Here's a summary of my tests (avg times in minutes):

Test
Z Drive
C Drive
USGS (10m)
Local TIFF

1 Model (Serial)
0.24
0.11
0.013
0.05

10 in Serial
0.11
0.09
0.013
N/A

10 in Parallel
0.75
0.53
Killed after 1 minute
0.04

18 in Parallel
6.38
5.36
Killed after 7 minute
0.05

I've tried tweaking GDAL_NUM_THREADS, GDAL_CACHEMAX, and GDAL_MAX_DATASET_POOL_SIZE, but parallel performance is still worse than serial.
This issue could be temporarily resolved in production by first creating a local TIFF for the working area, but the fundamental issue of resource competition between different processes is a bigger concern.

Can we investigate this by printing logs and finding what function is taking a long time? I tried to reproduce this outside ripple and I couldn't. I also think this is not S3API rate limiting since 10 models are not large enough to cause rate limitation.

I wrote this isolated script taking code from Ripple1D to benchmark parallel vs serial time and it did provide expected results. The parallel operations took on average half the time. So now I wonder why Ripple1D server with 96 cores is taking so long with parallel option.
import time
from multiprocessing import Pool
import rasterio
from rasterio import mask
import os
from shapely.geometry import Polygon
from shapely import wkt

RASTER_FILE = '/vsicurl/https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/13/TIFF/USGS_Seamless_DEM_13.vrt'
OUTPUT_DIR = '/data'
NUM_PROCESSES =  4
PARALLEL = True

# AOIs to extract data for
MASK_POLYGONS = [
    'Polygon ((-101.27354019513222738 35.52739919084066145, -101.27354019513222738 35.69615739573222868, -100.94487241384048559 35.69615739573222868, -100.94487241384048559 35.52739919084066145, -101.27354019513222738 35.52739919084066145))',
    'Polygon ((-102.00068677141113938 35.25089536155817882, -102.00068677141113938 35.3099018628973127, -101.84809101581141988 35.3099018628973127, -101.84809101581141988 35.25089536155817882, -102.00068677141113938 35.25089536155817882))',
    'Polygon ((-101.47061730459100204 35.31897596943801432, -101.47061730459100204 35.43785336400031838, -101.21361392673884438 35.43785336400031838, -101.21361392673884438 35.31897596943801432, -101.47061730459100204 35.31897596943801432))',
    'Polygon ((-101.59973679009847558 35.17417315916953413, -101.59973679009847558 35.24887728528475606, -101.26180206008611151 35.24887728528475606, -101.26180206008611151 35.17417315916953413, -101.59973679009847558 35.17417315916953413))',
]

def clip_raster(args):
    mask_polygon_wkt, idx = args
    output_path = os.path.join(OUTPUT_DIR, f'clip_{idx}.tif')
    if os.path.exists(output_path):
        os.remove(output_path)
    os.makedirs(os.path.dirname(output_path), exist_ok=True)
    print(f'Processing polygon {idx}')

    mask_polygon = wkt.loads(mask_polygon_wkt)

    with rasterio.open(RASTER_FILE) as src:
        out_meta = src.meta.copy()
        try:
            out_image, out_transform = mask.mask(src, [mask_polygon], all_touched=True, crop=True)
        except Exception as e:
            logging.error(f"Error clipping raster: {e}")
            return None
        out_meta.update({
            'height': out_image.shape[1],
            'width': out_image.shape[2],
            'transform': out_transform,
            'driver': 'GTiff',
        })
        with rasterio.open(output_path, 'w', **out_meta) as dest:
            dest.write(out_image)
    return output_path

def process_clips(mask_polygons_wkt, parallel=True, num_processes=4):
    os.makedirs(OUTPUT_DIR, exist_ok=True)
    start_time = time.time()
    args_list = [(polygon_wkt, idx) for idx, polygon_wkt in enumerate(mask_polygons_wkt)]
    if parallel:
        with Pool(processes=num_processes) as pool:
            results = pool.map(clip_raster, args_list)
    else:
        results = []
        for args in args_list:
            result = clip_raster(args)
            results.append(result)
    end_time = time.time()
    print(f"Processing time ({'parallel' if parallel else 'serial'}): {end_time - start_time} seconds")
    return results

if __name__ == '__main__':

    process_clips(MASK_POLYGONS, parallel=PARALLEL, num_processes=NUM_PROCESSES)

@ar-siddiqui I am wondering if the USGS server (https://rockyweb.usgs.gov) could be rate-limiting. Could you please try using this direct S3 bucket path for the input VRT?
/vsis3/prd-tnm/StagedProducts/Elevation/13/TIFF/USGS_Seamless_DEM_13.vrt
You can browse files in that prd-tnm bucket through this interface:
https://prd-tnm.s3.amazonaws.com/index.html

If the direct S3 access does not solve the bottleneck, then I would wonder if rasterio and/or GDAL are not honoring the GDAL behavior variables that you have set (GDAL_NUM_THREADS, GDAL_MAX_DATASET_POOL_SIZE), depending on how/where those are being set. For example in a .env file versus in a with rasterio.Env(): context manager.

The VRT in the prd-tnm bucket points to its own bucket for its tif paths, it does not point to rockyweb.usgs.gov.  Here's the first entry:
<SourceFilename relativeToVRT="0">/vsicurl/https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/13/TIFF/current/n06e162/USGS_13_n06e162.tif</SourceFilename>

I see. I confused pointing to the rocky server with using vsicurl vs vsis3. I still don't think that is the issue. One can download the USGS file and test that way.

Sorry I should have mentioned earlier, we are looking into profiling as you suggested / testing under various conditions. I wanted to mention the alternate VRT source as it came to mind when we were looking this morning, before we'd had a chance to set up more cloud resources for further testing.

This issue results for internal 2 rasterio calls in the main function. The calls result in a competing of resources (threads) when executed by huey. The resolution is to ship the internal function calls to a dedicated core where
 mask = get_geometry_mask(gdf_xs, terrain_source_url)

is replaced with
  with ProcessPoolExecutor() as executor:
      future = executor.submit(get_geometry_mask, gdf_xs=gdf_xs, MAP_DEM_UNCLIPPED_SRC_URL=terrain_source_url)
      mask = future.result()


Update HashiCorp Vault status to Stable

What content needs to be created or modified?
With https://github.com/dapr/components-contrib/issues/1926 and https://github.com/dapr/components-contrib/pull/2316, HashiCorp Vault has both conformance and certifications tests and is ready to be promoted to Stable.
Describe the solution you'd like
HashiCorp Vault promoted to stable
Where should the new material be placed?
daprdocs/data/components/secret_stores/generic.yaml
The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

https://github.com/dapr/components-contrib/pull/2316
https://github.com/dapr/docs/pull/2981

Additional context

Completed


setuptools should be explicitly added as a dependency

Describe the bug
src/braket/devices/local_simulator.py imports pkg_resources (https://github.com/aws/amazon-braket-sdk-python/blob/105433edb22ad2ccb50afbb72fd74ccb8d8d63b9/src/braket/devices/local_simulator.py#L17), but it fails when setuptools is not installed.
setuptools can sometimes be missing, depending on how you create the (virtual) environment.
I think setuptools should be specified as a dependency explicitly, i.e. added to install_requires in setup.py.
In my case, I created the virtual environment with Poetry, with amazon-braket-sdk listed in  pyproject.toml ([tool.poetry.dependencies] section).
(Actually it seems to be an unintended behavior (cf. https://github.com/python-poetry/poetry/issues/6328), but I still think that the dependency should be explicitly specified.)
To reproduce

Install Poetry
Set up a project with poetry init
Add amazon-braket-sdk as a dependency: poetry add amazon-braket-sdk
Remove setuptools manually: poetry run pip uninstall setuptools
Run Python in the Poetry virtual environment: poetry run python
Import LocalSimulator: from braket.devices.local_simulator import LocalSimulator
(Cleanup) Exit Python and remove the virtual environment: poetry env remove python

Expected behavior
The import succeeds without errors.
Screenshots or logs
The following error occurs:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/q/.cache/pypoetry/virtualenvs/t-UUQASyjB-py3.9/lib/python3.9/site-packages/braket/devices/__init__.py", line 15, in <module>
    from braket.devices.local_simulator import LocalSimulator  # noqa: F401
  File "/home/q/.cache/pypoetry/virtualenvs/t-UUQASyjB-py3.9/lib/python3.9/site-packages/braket/devices/local_simulator.py", line 17, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

System information
A description of your system. Please provide:

Amazon Braket Python SDK version: 1.35.5
Amazon Braket Python Schemas version: 1.14.1.post0
Amazon Braket Python Default Simulator version: 1.11.5.post0
Python version: 3.9.9

Additional context

Thank you for raising the issue! I've created a PR to fix this.


Documentation added

Updated readme, added docstrings, more comments in the code

Lintly has detected code quality issues in this pull request.

Done via new commit


Creates first version of Schema

Description
This PR adds a proof of concept for the Apollo schema that will be used in the API. Now, to make requests to the API, you'll need to provide a Github token generated by Github App authentication, as it was implemented by @jadsonluan. This token is passed via authentication header, as illustrated bellow.

Now it's possible to get data from logged in user and from Github organizations.
Fixes #9
Fixes #10
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
You can make me and organization queries in the Apollo GraphQL Playground.
Examples:
Me:

Organization:

Important
The following changes do not pass on ESLINT, and I didn't understand what's causing this error. I think that's some kind of problem with context arrow function, in src/index.js, when the ApolloServer is being defined:
const server = new ApolloServer({
  schema,
  context: ({ req }) => {
    const token = req.headers.authorization || '';

    if (!token) {
      throw new Error('An authentication token is required!');
    }

    return {
      token
    };
  },
});

And we can't get data from team members yet, but this will be solved on next updates.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Uoooooooooou, congratulations for your work, it seems very very good.
But i have some suggestions, following the patterns saw in P2, and of the some discussions, it's better have a folder structure by feature, something like, /organization, /user etc,
I am based on this links:

GraphQL modules feature based graphql modules at scale
Spectrum apollo-server chat discussion

@fanny Thanks for the review :heart:.  I'll be doing the changes tomorrow! :smile:

@fanny and @jadsonluan I finished my work on your requested changes. :smile:


Text only draggable vertically after cloning

Hey,
look at this fiddle please: https://jsfiddle.net/w5zod1m3/3/
It should be pretty self-explanatory.
@Fuzzyma maybe you want to have a look at it?
It seems the tspan node's x attribute doesn't get changed - weird.

Okay, this is apparently not svg.draggable.js' fault.
See https://github.com/wout/svg.js/issues/369


Debug build error

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: macOS 14.4
- Continue: 0.9.90
- IDE:

Description

When trying to run the extension in debug mode, the attached error message appears in the terminal
To reproduce

Enter Run and Debug Mode
Select Extension (VSCode)
Click the button to Start Debugging
After some time, error appears

Log output
No response

Thanks for the PR on this! Just a merge gone wrong


⚠ GitLab Server has degraded performance

In d19c6d9, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6953 ms

Resolved: GitLab Server performance has improved in 43f7c28.


Core50 dataset

This PR enables the use of CoRe50 dataset.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

do we want to refer to it by this name or "CORe50"?

I chose this only to avoid spelling mistakes.


Issue 102

Fixes #102

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Thanks!
One easy thought is that we could make the calls synchronous so that the two await calls inside the method go away. Then other callers would be blocked on writing. Given the amount of data we are processing, it might not be a bottleneck and it would be safe. Am I missing anything?


Upgrade remaining flutter devicelab mac bots to macOS 13.6.x

Type of Request
infra task
Infrastructure Environment
devicelab, mac
What is happening?
Per https://github.com/flutter/flutter/issues/134737 :
upgrade remaining mac bots to macOS 13.6.1:
prod pool:
flutter-devicelab-mac-22
flutter-devicelab-mac-24
flutter-devicelab-mac-25
flutter-devicelab-mac-31
flutter-devicelab-mac-36
flutter-devicelab-mac-42
flutter-devicelab-mac-44
try pool:
flutter-devicelab-mac-14
flutter-devicelab-mac-17
flutter-devicelab-mac-46
Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Once upgraded, ensure the following:
Delete any directories within /opt/flutter/xcode if applicable.
Also verify /opt/flutter/xcode is owned by swarming user.
Also, ensure DevToolsSecurity is enabled.
Run DevToolsSecurity - should get response "Developer mode is already enabled."
If you don't get the message, run sudo /usr/sbin/DevToolsSecurity -enable to enable.

All Bots listed in this ticket have been upgrade MacOS 13.6.4 as requested. All works completed and ticket is closed.


KeyVault-JCA Readme issues

1.section Link1, Link2

Reason: Lack parameter azure.keyvault.aad-authentication-url
Suggestion:
Change select code to
KeyVaultLoadStoreParameter parameter = new KeyVaultLoadStoreParameter(
            System.getProperty("azure.keyvault.uri"),
            System.getProperty("azure.keyvault.aad-authentication-url"),
            System.getProperty("azure.keyvault.tenant-id"),
            System.getProperty("azure.keyvault.client-id"),
            System.getProperty("azure.keyvault.client-secret"));

@jongio for notification

@Luyunmt
Thanks for your reporting.
If we do not configure this parameter, it will use "https://login.microsoftonline.com/" as the default value.
https://github.com/Azure/azure-sdk-for-java/blob/a48625717a1d0f5520053c0c735cf6b53b214680/sdk/keyvault/azure-security-keyvault-jca/src/main/java/com/azure/security/keyvault/jca/AuthClient.java#L41
https://github.com/Azure/azure-sdk-for-java/blob/a48625717a1d0f5520053c0c735cf6b53b214680/sdk/keyvault/azure-security-keyvault-jca/src/main/java/com/azure/security/keyvault/jca/AuthClient.java#L107

@lzc-1997-abel Maybe we can add table which list all configurable properties. Just like aad-starter README did.


new module: buttons

http://guides.service.gov.au/design-guide/components/forms-buttons/index.html#buttons

We should take the current open issue in 1.x on better visually differentiating states into account: https://github.com/AusDTO/gov-au-ui-kit/issues/391#issuecomment-278532599
This may result in minor design changes.

buttons.zip


BTC Warning banner when transactions are pending

📝 Description
Add a warning banner when atleast one transaction is pending for BTC accounts
❓ Context

Impacted projects: ledger-live-desktop
Linked resource(s): LIVE-2020 , LIVE-3398

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/generate-screenshots

/generate-screenshots

/generate-screenshots

@hedi-edelbloute merging this as it's been validated by @mdeidda-ledger and reviewed !


Support libnds 2.0.0

Sources should be updated to support libnds 2.0.0.
I don't have the time to test this right now, but I'll look into making it work once I do.

Would you look at that, everything still works after updating the sources. The docker images we're using already have libnds 2.0.0 and the example seems to build just fine (after fixing #1, that is).

I'll get back to you and test my code. I'll note that they changed the way your main loop is supposed to be done (it's mandatory to call pmMainLoop now in the while clause) but I'll see if anything else breaks.

@bandithedoge looks like DSWifi broke:
/build/dsi/src/main.c: In function 'tx':
/build/dsi/src/main.c:81:5: error: implicit declaration of function 'send' [-Wimplicit-function-declaration]
   81 |     send(sn, msg, strlen(msg), 0);
      |     ^~~~
/build/dsi/src/main.c:84:19: error: implicit declaration of function 'recv' [-Wimplicit-function-declaration]
   84 |     while ((rxl = recv(sn, rx, MAX_PACKET_SIZE - 1, 0))) {
      |                   ^~~~
/build/dsi/src/main.c: In function 'main':
/build/dsi/src/main.c:137:10: error: implicit declaration of function 'socket' [-Wimplicit-function-declaration]
  137 |     sn = socket(AF_INET, SOCK_STREAM, 0);
      |          ^~~~~~
/build/dsi/src/main.c:137:17: error: 'AF_INET' undeclared (first use in this function)
  137 |     sn = socket(AF_INET, SOCK_STREAM, 0);
      |                 ^~~~~~~
/build/dsi/src/main.c:137:17: note: each undeclared identifier is reported only once for each function it appears in
/build/dsi/src/main.c:137:26: error: 'SOCK_STREAM' undeclared (first use in this function)
  137 |     sn = socket(AF_INET, SOCK_STREAM, 0);
      |                          ^~~~~~~~~~~
/build/dsi/src/main.c:145:13: error: implicit declaration of function 'connect' [-Wimplicit-function-declaration]
  145 |     while (!connect(sn, (struct sockaddr *)(&sain), sizeof(sain)));
      |             ^~~~~~~
/build/dsi/src/main.c:157:15: error: unknown type name 'KEYPAD_BITS'
  157 |         const KEYPAD_BITS keys = keysHeld();
      |               ^~~~~~~~~~~

It appears it is now necessary to include sys/socket.h. It also looks like KEYPAD_BITS is just now a regular u32.
Now actually running my code, it's completely broken. I just get two white screens, even after switching to pmMainLoop. Probably not an issue with this repo - likely moreso just an issue with libnds 2.0.0 being radically different - but still

@amyipdev Can you confirm that the issue is present on a non-Nix installation of dkp?

If it's okay, can I get to this in a week or so? Finishing up finals, have a lot to do.

No rush


Can't stop propagation of the default events (click)

Hello,
thanks for the framework, it's really great.
I've found out an issue with native events, right now it doesn't work in Angular way.
I don't know if it is by design, but it complicates situation when we need to provide our custom library on top of DevExtreme (and not to force developers into non-default usage).
Example: plunker
As you can see, components MyButton and My2Button are very similar, public API is same, implementation is almost the same. But if we use internally <dx-button>, then disabling doesn't work. Event click is still propagated. On the other hand with the native button, it works as expected.
Is it a bug? Would it be too complex to follow Angular style of handling native events?

The disabled option of our button is in effect only if the onClick event of the button is raised or not (and of cause, the button style). If you handle the native click event, this event won't be prevented. I suggest you use the HostBinding directive inside your my2-button component to change the pointer-events CSS style of the component host:
@Input()
get disabled(): boolean { return this._disabled; }
set disabled(value: boolean){ this._disabled = value; this.events = this._disabled ? "none" : "auto"; }
public _disabled: boolean = false;
@HostBinding('style.pointer-events') events = "auto";

See the updated plunk. Will this work for you?

As we discussed with your college on support center, right now I solved it by handling click event also on container div, see plunker.
But your solution also seems feasible, thanks. I will try both and let you know in case of any long-time issue.

No problem, @Marfusios .


Add link to request for library update

cc #145
Add a request update link on library page

click link and redirect to GitHub page

Should give a screenshot and example link.

Wrong syntax in commit message.

example link: /libraries/jquery

You didn't provide the link
You should provide it in the first comment
The design of the place and style of the link ... makes itself looks like a broken, I don't think we should make it appear in that place and in that way.

@cdnjs/intern3 Please help me review this PR, thanks.
I change this request update link place on library page

And redirect to GitHub page as following:

If there is any suggest, please let me know.

It's a bad idea to simply clone the template from new library request, totally different purpose.

@PeterDaveHello I pulled from this repo. , please help me review this PR.
And if there is any suggest, please let me know.
Thank you.

I mean the issue template, it's originally for new library request, you should not just copy and paste as the purpose is different.

What items should issue template take is better?
How about as following? (XXXXX will auto add from library API.)
Library name: XXXXX
CDNJS version: XXXXX
CDNJS URL: XXXXX
Git repository url: XXXXX
npm package name or url (if there is one): XXXXX
Need update items and description:

[ ] description: XXXXX -> _____________________
[ ] version:   XXXXX -> _____________________
[ ] author:    XXXXX -> _____________________
[ ] filename:     XXXXX -> _____________________
[ ] homepage:     XXXXX -> _____________________
[ ] repository:     XXXXX -> _____________________
[ ] keywords:     XXXXX -> _____________________
[ ] license:     XXXXX -> _____________________

Wanna say something? Leave message here:
If there is any suggest, please let me know.

@sufuf3 It's much more better that you started to think about its content now, and you should also explain the reason why or why not the items would be or would not be listed here.

I refer to package.json.
In Need update items and description:, I include all of the items, exclude as following:

repository, because it show in Git repository URL:
name, it show in Library name:
auto-update, this item is hard to detect, cause it may not exist, from npm to git repo., or from git repo, to npm. I think it can let the user leave a message.

If there is any suggest, please let me know.
Thank you.

Or how about as following? (XXXXX will auto add from library API.)
Library name: XXXXX
CDNJS version: XXXXX
CDNJS URL: XXXXX
Git repository url: XXXXX
npm package name or url (if there is one): XXXXX
Need update items and description:

[ ] description: XXXXX -> _____________________
[ ] version:   XXXXX -> _____________________
[ ] author:    XXXXX -> _____________________
[ ] filename:     XXXXX -> _____________________
[ ] homepage:     XXXXX -> _____________________
[ ] repository:     XXXXX -> _____________________
[ ] keywords:     XXXXX -> _____________________
[ ] license:     XXXXX -> _____________________
[ ] auto-update:

[ ] None to npm auto-update
[ ] None to git auto-update
[ ] git auto-update to npm auto-update
[ ] npm auto-update to git auto-update

Wanna say something? Leave message here:

@hare1039 Could you give me some suggestion and make this PR to be better?

**- [ ] This library is not updated to the latest version

[ ] The GitHub repo has changed

[ ] Some info of this lib needs to be updated
Info needed to be updated:**

I think that we can list out the reasons that happens often, so that the issuer only needs to check that box.

@clairetsai818 Thank you for your suggestion. I modified as the following, hope it is okay.
Library name: XXXXX
CDNJS version: XXXXX
CDNJS URL: XXXXX
Git repository url: XXXXX
npm package name or url (if there is one): XXXXX
Update Reason:

[ ] This library is not updated to the latest version.

[ ] The GitHub repo has changed.

[ ] Some info of this lib needs to be updated:

[ ] description: XXXXX -> _____________________
[ ] version:   XXXXX -> _____________________
[ ] author:    XXXXX -> _____________________
[ ] filename:     XXXXX -> _____________________
[ ] homepage:     XXXXX -> _____________________
[ ] repository:     XXXXX -> _____________________
[ ] keywords:     XXXXX -> _____________________
[ ] license:     XXXXX -> _____________________

Wanna say something? Leave message here:

This library is not updated to the latest version.

A little bit too long. How about This library needs update to latest version

The GitHub repo has changed.

Not necessary GitHub I think.
Will those XXXXX auto filled?

I modified it.
And I think the redirect url to the GitHub page template maybe can using as the following:
Library name: XXXXX
CDNJS version: XXXXX
CDNJS URL: XXXXX
Git repository url: XXXXX
npm package name or url (if there is one): XXXXX
Update Reason:

[ ] description: XXXXX -> _____________________
[ ] version:   XXXXX -> _____________________
[ ] author:    XXXXX -> _____________________
[ ] filename:     XXXXX -> _____________________
[ ] homepage:     XXXXX -> _____________________
[ ] repository:     XXXXX -> _____________________
[ ] keywords:     XXXXX -> _____________________
[ ] license:     XXXXX -> _____________________

Wanna say something? Leave message here:

I refer to package.json.
In Need update items and description:, I include all of the items, exclude as following:

repository, because it show in Git repository URL:
name, it show in Library name:
auto-update, this item is hard to detect, cause it may not exist, from npm to git repo., from git repo. to npm or file structure problem. I think it can let the user leave a message.
XXXXX will auto add from library API.

If there is any suggest, please let me know.
Thank you.

It will be better readability with indention

@gocreating thanks, I'll try to modify this.
sorry for late response.

Hi @sufuf3, it seems like #71 can be done by this PR at the same time.
By modifying to @gocreating 's code like
{{
  let getURL = (type, ...args) => {
    if (type == 'update')
      return `https://github.com/cdnjs/cdnjs/issues/new?title=${...}&body=${...}&...`;
    else if (type == 'report')
      return ...;
   };
}}

  request update

  report lib

How about this? :)

@qas612820704 Thank you very much.
I'll try to use it.

@PeterDaveHello we added two links as the followings:

request for library update #145
report outdated library #71

This is the page show the links:

This is the link redirect to GitHub to request for library update:

This is the link redirect to GitHub to report outdated library:

If you have any suggestion, please let me know.
Thank you.

We don't need so many items, just its version.
Also I don't think we need user to fill repo or hosted version info.

I modified as the followings.
If you have any suggestion, please let me know.
Thanks.

This is the page show the links:

This is the link redirect to GitHub to request for library update:

This is the link redirect to GitHub to report outdated library:

It's confused about what's the difference from the name of the title/button, also, I don't like the place where they are placed, the button(s) should be individual, not mixed with the dropdown list.

This situation is not good to use wanna say something, it's about the description of what the request is.

I modified as the followings.
If you have any suggestion, please let me know.
Thanks.

modified the button part

remove wanna say something part of the description.


Add key vault

Add keyvault resources in terraform
Add keyvault firewall configuration in terraform
This PR should fulfill this recommendation: https://portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsBlade/assessmentKey/52f7826a-ace7-3107-dd0d-4875853c1576/showSecurityCenterCommandBar~/false

Could you also add a Powershell snippet to Readme.md that reads the postgresql credentials from keyvault and creates the respective kubernetes secret?


fix(terminal): use the latest, resized area when clearing

This is the same mistake as 0f4823977894cef51d5ffafe6ae35ca7ad56e1ac
The code that comes after is still incorrect, clearing from the cursor to the bottom of the screen multiple times.
I'm using this in an alternate "Inline" implementation, as described in https://github.com/ratatui/ratatui/issues/1426#issuecomment-2420571210, for which the latter problem doesn't matter, except perhaps to reduce flickering very very slightly.
I hope this patch is acceptable as is.

The coverage job also fails on main.

https://github.com/ratatui/ratatui/issues/1426#issuecomment-2420571210

This issue is mostly unrelated to this fix, which stands alone.

How about fixing this by making sure that the viewport::Fixed(area) is corrected instead? This will make it easier to not make this mistake in any future code. Thoughts on this approach?
--- a/src/terminal/terminal.rs
+++ b/src/terminal/terminal.rs
@@ -237,6 +237,9 @@ where
         self.buffers[self.current].resize(area);
         self.buffers[1 - self.current].resize(area);
         self.viewport_area = area;
+        if let Viewport::Fixed(_) = self.viewport {
+            self.viewport = Viewport::Fixed(area);
+        }
     }

     /// Queries the backend for size and resizes if it doesn't match the previous size.
@@ -476,8 +479,7 @@ where
                     .set_cursor_position(self.viewport_area.as_position())?;
                 self.backend.clear_region(ClearType::AfterCursor)?;
             }
-            Viewport::Fixed(_) => {
-                let area = self.viewport_area;
+            Viewport::Fixed(area) => {
                 for y in area.top()..area.bottom() {
                     self.backend.set_cursor_position(Position { x: 0, y })?;
                     self.backend.clear_region(ClearType::AfterCursor)?;

Yup, makes more sense 👍🏼

         self.viewport_area = area;
+        if let Viewport::Fixed(_) = self.viewport {
+            self.viewport = Viewport::Fixed(area);
+        }

This would still be a workaround for a redundancy in the data model, which I'm removing in  73b0f122e71c6e205e7d4613411c6046a0c6a023
It's nice to reduce the state space, and more concretely if we ever need to set viewport_area in a different place, or do some other refactor, we there's nothing that we can forget to update.
Also the comment on the new type lets us clarify the purpose of retaining the info that we do retain.

:+1: I've moved the refactor from this PR to #1428.
It now only contains the first commit with the simple fix.

Merged - thanks for the PR


chore: make inner product notation ⟪x, y⟫_𝕜 scoped in namespace InnerProductSpace

There is a conflict between the Lean-3-style notation ⟪x, y⟫_𝕜 for inner product and the (Lean 4) notation x |_ₗ U ⟪e⟫ for TopCat.Presheaf.restrict that leads to a syntax error in line 125 of Topology/Sheaves/Presheaf.lean when these notations are simultaneously in effect:
  x |_ₗ U ⟪e⟫
        -- ^ unexpected token '⟫'; expected ','

This limitation blocks PR #12502. See this Zulip discussion for details.
We resolve the notation conflict by making the inner product notation ⟪x, y⟫_𝕜 scoped in namespace InnerProductSpace and then adding open scoped InnerProductSpace wherever the notation is used.

bors merge


Adding unit tests

Adding the first pass of unit tests

Changes Unknown when pulling a230d08e6e78eaf44682af5212ccf4fbf3ef832b on waterfoul:tests into ** on tanjentjs:master**.

Changes Unknown when pulling cc0260faaefc54f4e03f763c1ee536bf9291347a on waterfoul:tests into ** on tanjentjs:master**.

Changes Unknown when pulling 37df5380aa193bd0f8356bdf037febed3544f78f on waterfoul:tests into ** on tanjentjs:master**.

Changes Unknown when pulling f97adfe05644a9ac78a7293a06ae455f65efdb8d on waterfoul:tests into ** on tanjentjs:master**.


Doesn't return a error when passed string is empty

struct http_parser_url u;
http_parser_url_init(&u);
int rc = http_parser_parse_url("", 0, 0, &u);

rc is 0 here, shouldn't it be non zero?

yeah. it actually returns an uri struct with all fieds empty. we're rethinking this behaviour. returning an error should be the best approach.


put method does nothing, promise resolves but doesn't send any data to dynamodb

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
call put method
Expected behavior
some data in dynamodb

nvm forgot to call .exec() at the end
should be something like this
.put({
        userId,
        token,
      })
      .exec();


fix:  Add show Url option

Codecov Report

Merging #180 into master will decrease coverage by 0.21%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #180      +/-   ##
==========================================
- Coverage   52.98%   52.77%   -0.22%
==========================================
  Files          18       18
  Lines         251      252       +1
  Branches       52       52
==========================================
  Hits          133      133
- Misses         87       88       +1
  Partials       31       31

Impacted Files
Coverage Δ

src/js/components/Tab/Tab.js
15.09% <0%> (-0.3%)
:arrow_down:

Continue to review full report at Codecov.

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

Coverage decreased (-0.3%) to 45.926% when pulling 140942eeff5c83d8605e98c3a1859e53a6e472fe on hide_url into 8b9fc92fb0c2cbec2dbc934dd979211572f9ed48 on master.


Upgrade to JDK 8u265b01

High-level description
Update JDK to most recent 8u265b01. This includes a fix for large open file limits: https://bugs.openjdk.java.net/browse/JDK-8236662
Corresponding DC/OS tickets (required)

D2IQ-70809 Restrict systemd file descriptors for java.
COPS-6422 DC/OS installation crashes on flatcar linux due to LimitNoFile

@mesosphere-mergebot test all

@mesosphere-mergebot test all

@mesosphere-mergebot request-review @janisz

@mesosphere-mergebot backport 2.1 2.0

@mesosphere-mergebot changelog-not-required to be back-ported


Add support for [CHIP-2021-02: Native Introspection Opcodes]

Remove all non-native introspection/covenant functionality from the cashc compiler
Retain non-native introspection/covenant functionality in the SDK for backward compatibility
Add support for Nullary Introspection Ops by adding a new NullaryOp node to the compiler
Add support for Unary Introspection Ops by adding them to the UnaryOp node
Replace new OutputX() with new LockingBytecodeX()
Update test cases

Examples and documentation still needs to be updated. The new covenant contracts also need to be updated to remove some theoretical vulnerabilities.

Overall it looks like a satisfying removal of special handling due to the better underlying vm design. I mentioned a few questions that are mostly where I couldn't understand a change, not because I thought there is an error.
One general thing was that tx version seems to have various checks including 2 and >=2 (maybe also 1? That might have been only in removed lines). Not sure if that was all intentional.

@emergent-reasons What do you mean with this:

One general thing was that tx version seems to have various checks including 2 and >=2 (maybe also 1? That might have been only in removed lines). Not sure if that was all intentional.

What do you mean with this:

One general thing was that tx version seems to have various checks including 2 and >=2 (maybe also 1? That might have been only in removed lines). Not sure if that was all intentional.

I looked back through all the files and couldn't find the version 1 that I remember. I found these below. I guess it just didn't seem like there was a specific reason for some to be ==2 and some >=2 , but I don't think it's really relevant here. So no worries on this point.
tx.version >= 2

packages/cashscript/test/fixture/old/simple_covenant.cash
packages/cashscript/test/fixture/simple_covenant.cash

tx.version == 2

packages/cashc/test/valid-contract-files/covenant_all_fields.cash
packages/cashc/test/valid-contract-files/simple_covenant.cash

Oh yeah. There wasn't a real reason to check for those values tbh. Just that I wanted to check something.

🚀


toString does not match V8 stack trace format

Could we modify toString so that it closely matches https://v8.dev/docs/stack-trace-api#appendix%3A-stack-trace-format instead of current format?
Calling Error.prepareStackTrace(err, stackframes) does not give proper output.

Here is how Node prepares it:
https://github.com/nodejs/node/blob/b6bfc193788b1838bee73d584fe089e1104b9f88/src/node_errors.cc#L142-L175

This is fixed by #23. Thanks @niftylettuce!


Configuring Email for Exchange with Postfix

This provides an overview of configuring Postfix on the Mattermost server so that it will relay email to an Exchange server using STARTTLS.  This is specifically for environments where Mattermost will not connect to Exchange in a native fashion.
mattermost_postfix.txt
MattermostPostfixtoExchange.txt

Thanks @gluelue! It looks like when you created this PR that you chose from the master branch into the docs branch. It should be from the branch that you created for the change into the master branch.
Feel free to join https://pre-release.mattermost.com/core/channels/documentation and we can figure out how to get your changes into a PR that we can use.


Need Help with Collections

Hi I was wondering if someone could tell me what I am doing wrong here, the compiler tells me "missing type in composite literal" however, I don't know what do to fix it. I'm still kind of new to Go, gRPC, and protocol buffers. Code Snippet Below
practiceArray := []*proto.Value{         {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[0])}},         {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[1])}},         {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[2])}},         {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[3])}},     }     var testCollection = &proto.Value_Collection{Collection: {Elements: practiceArray}}     print(testCollection)

Fix code to make it viewable:
practiceArray := []*proto.Value{
        {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[0])}},
        {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[1])}},
        {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[2])}},
        {Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[3])}},
    }
    var testCollection = &proto.Value_Collection{Collection: {Elements: practiceArray}}
    print(testCollection)

practiceArray := []*proto.Value{
	{Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[0])}},
	{Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[1])}},
	{Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[2])}},
	{Inner: &proto.Value_Int{Int: int64(data.M_suspensionPosition[3])}},
}
testCollection := &proto.Value_Collection{Collection: &proto.Collection{Elements: practiceArray}}
print(testCollection)

The protobuf type can be quite verbose and can be a bit difficult to use. This project is working toward making the Go gRPC API easier to use: https://github.com/datastax-ext/astra-go-sdk. It's still early days, but maybe give it a try!


CocoaPods/Gemfile updates

Changes in this pull request

Adds the Gemfile.lock, so that we know which CocoaPods should be used.
Updates the .gitignore to add vendor and .bundle, which are common local rubygems config/cache.
Re-ran bundle exec pod install.

No code changes here, so no package-level tests required.
Checklist

[x] All tests pass. Demo project builds and runs.
[x] I added tests, an experiment, or detailed why my change isn't tested.
[x] I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
[x] I have reviewed the contributing guide

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

After lots of testing and reducing the travis file, CODE_SIGNING_REQUIRED=NO was the culprit. Seems it's best to just let Xcode use default signing settings for tests.


turn logging off by default as per documentation

should fix https://github.com/mixpanel/mixpanel-iphone/issues/608

LGTM

lgtm


404 Page Not Redirecting to French Version When Language is Switched

Issue Description:
The issue is that when the website is switched to the French version and a user navigates to a non-existent page, the 404 page is still displayed in English instead of French.
Details:
The website's language is switched to French.
When navigating to a non-existent page (triggering a 404 error), the 404 page is displayed in English.
The expected behavior is that the 404 page should be displayed in French when the website is set to the French language.
Steps to Reproduce:
Switch the website language to French.
Navigate to a non-existent page to trigger the 404 error.
Observe that the 404 page is displayed in English.
Expected Behavior:
The 404 page should be displayed in French when the website is set to the French language.
Request for Assistance:
Any guidance on how to ensure the 404 page respects the selected language setting and displays the appropriate language content would be highly appreciated. In addition, it would be good to have it properly set up in the theme already.

Hi @Najib90. I’ve added code to dynamically generate the 404 page content based on the current language setting. If you have many languages to support, you can also use a JSON, or a CMS to retrieve the translated strings. However, while it works locally, looks like localized 404 pages are a bit tricky, so it will require a manual set-up on your host.

Closing for now.

Thank you, understood!


Add CancellationToken Parameter to Methods Returning Task and ValueTask

This PR updates the docs to reflect the changes made in CommunityToolkit/Maui PR https://github.com/CommunityToolkit/Maui/pull/1503/files

Hey @jfversluis! Could you merge this when you get a chance?
We missed reviewing / merging this one during the v7.0.0 release.


handle leading zero PSID's

Assume user will enter a 7 digit psid and want to retrieve 7 digit psid's
Update the following:

get_data needs to be updated so that when user supplies 7 digit psid it gets converted to the appropriate integer one that can be looked up on S3
all of the metadata functions that handle PSID's need to return the PSID as a 7 digit when it is only 6.

Maybe instead of all this we can update the data on so that 7 digit psid's can be looked up.

I've given this some thought, and I think although it will work, I'd prefer to just update files in the S3 bucket and the package objects such that PSID is always a character of length 7, with left-padded zeros.
Let's proceed with function development assuming the S3 bucket is fixed and that the package objects have been updated. I'll submit a PR to merge a new branch with the updated package objects to v0.1.


Fix issue with errors being swallowed in child compilations

This ensures we get error logs whenever a compilation fails. It also adds a regression test
in the form of snapshots of the logger calls.

!merge


So close ... how do I send commands over the command channel?

I think I have tried really hard to find an example of how to send commands over the command channel. I don't think I understand BLE enough to even ask a sensible question. Can you please provide an example of sending commands over the command channel?

just realized maybe it is a different service/characteristic?

Here is my config. I would like to send the wifi enable/disable commands over BLE.
esphome:
  name: sunroom-bottom-end-stop
  friendly_name: sunroom-bottom-end-stop
  platformio_options:
    board_build.flash_mode: dio

esp32:
  variant: ESP32C3
  board: esp32-c3-devkitm-1
  framework:
    type: arduino

logger:

api:
  encryption:
    key: !secret encryption_key

ota:
  password: !secret ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
    static_ip: <IP_ADDRESS>
    gateway: <IP_ADDRESS>
    subnet: <IP_ADDRESS>

  ap:
    ssid: "Sunroom-Bottom-End-Stop"
    password: !secret fallback_password

external_components:
  - source: github://wifwucite/esphome-ble-controller

binary_sensor:
  - platform: gpio
    name: Bottom End Stop
    id: bottom_end_stop
    internal: True
    pin:
      number: 07
      inverted: True
      mode:
        input: True
        pullup: True

sensor:
  - platform: adc
    name: "Battery voltage"
    id: battery_voltage
    pin: GPIO0
    accuracy_decimals: 2
    update_interval: 60s
    attenuation: auto
    filters:
      - multiply: 10.0

esp32_ble_controller:
  services:
    - service: "0000180F"
      characteristics:
        - characteristic: "00002A19"
          exposes: battery_voltage
    - service: "fc23b9ec-4b22-4356-abec-6083712765e3"
      characteristics:
        - characteristic: "4ef07259-6c07-4c95-a2a0-56072829e1ec"
          exposes: bottom_end_stop

  commands:
    - command: toggle-wifi
      description: Toggle Wifi
      on_execute:
        - if:
            condition: wifi.enabled
            then:
              - logger.log: "Wifi Disabled"
              - wifi.disable:
            else:
              - logger.log: "Wifi Enabled"
              - wifi.enable:

  security_mode: none

captive_portal:

@archef2000 any suggestions please?

I guess I don't need to do this anymore since I can't get wifi to work on this ESP32C3-mini.
But I do hope you let me know or update the documentation. Thanks!

For others who are new to BLE work, you need to use an app called nRF Connect which is available on Apple and Android app stores. I haven't used it for sending data yet but it is really handy for debugging BLE information.


Consistent signposting of access offer across website and venue

Accessible iconography project

Icons project put on hold due to lack of ownership during autumn 2023 reorg


How can I access my page from ip direct

Hello I want to access evilginx page from my server ip direct.
Asssuming my server ip is <IP_ADDRESS>, when I open this IP in browser it should display evilginx phishlet.
I am looking for this so I can add DNS record A withtout configuring domain

then you dont need dns if you are not using domain.

**Hi 👽 ! If you are interested in ⚙Advanced Phishing⚙ and the ✨Evilginx3✨ tool then I offer you Google Gmail and Custom Phishlets with a ✅Free Tutorial✅ which arrives if the 📈Telegram reaches 50 Subscribers📈
⏳ GOOGLE GMAIL PHISHLET 2024 WITH PROOF ⏳
->
⛔https://www.youtube.com/watch?v=nA47UknIE6A⛔
🔓 Ask your questions and a free tutorial from 50 subs on telegram !!!
->
📩https://t.me/Noremorse1011📩**


0x5x instruction set implementation and tests

Coverage increased (+0.06%) to 99.403% when pulling 650151a3475ccff622b22da2e21f027712bcfac3 on 0x5x-instruction-set-implementation into c7d8b8df27f57c67ef58875f8ac6e0cbda48da06 on master.


Easy copy/paste for addresses in Endpoints

Detailed Description
In Endpoints, addresses are an interesting target for copy/paste.
Right now, addresses respond to click, so you get redirected when selecting the text.
Context
Just a bit of niceness when the user also works with the CLI, and needs to switch between endpoints.
Possible Implementation
A clipboard button would be amazing :)

You can copy the address - click on the three dots menu for the endpoint and there is an option to copy the address to the clipboard.


Support Docker images that have a non-root user

Description of the changes
Currently, gsc does not support building app images that has a non-root user.
The gsc build step fails at line https://github.com/gramineproject/gsc/blob/master/templates/Dockerfile.common.build.template#L11  , with the error as shown below
E: List directory /var/lib/apt/lists/partial is missing. - Acquire (2: No such file or directory)
This error occurs because distro-specific packages cannot be installed as non-root user.
If one bypass this error by putting "USER root" at https://github.com/gramineproject/gsc/blob/master/templates/Dockerfile.common.build.template#L10 , then the unsigned image and the final signed gsc image will have user as "root".
This PR allows to create gsc images for app images with non-root user. Also, the original "user" of the app image will be restored back in the final signed gsc image.
Fixes #30.
How to test this PR?
Step 1: docker pull <non-root-user-app-image>   //example of non-root user image bitnami pytorch
Step 2: docker inspect non-root-user-app-image  // here you can check the original user
Step 3: perform gsc build and gsc sign on the non-root-user-app-image
Step 4: docker inspect gsc-non-root-user-app-image  // Verify again, the image will have the original user
Step 5: docker run --device=/dev/sgx_enclave -it gsc-non-root-user-app-image  //success
Step 6: gsc build and sign should pass for root user images as well.
Note: If the app image has an empty user field like user : "" , then the final gsc image will be created with root user.

This change is

fixes issue #60

Reviewable status: all files reviewed, 1 unresolved discussion, not enough approvals from maintainers (1 more required), not enough approvals from different teams (1 more required, approved so far: Intel) (waiting on @aneessahib)

gsc.py line 394 at r8 (raw file):
Previously, dimakuv (Dmitrii Kuvaiskii) wrote…
@dimakuv, thanks for pushing these changes. I tested the latest version, here are the results:
./gsc info-image gsc-python gives following error with 666 (though works fine 777):
  File "./gsc.py", line 404, in gsc_info_image
    with open(os.path.join(tmpdirname, "entrypoint.sig"), 'rb') as sig:
PermissionError: [Errno 13] Permission denied: '/tmp/tmpy1tza3yr/entrypoint.sig'

same error , I got for bitnami image too.
I will do more analysis on why this is happening and get back soon. Thanks

Based on this answer (3rd point) , looks like we need execute bit too set in order to enter into a directory and read a file.


Fix SC2086 for shellcheck

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Fix SC2086 for shellcheck
Which issue(s) this PR fixes:
xref https://github.com/kubernetes-sigs/kwok/issues/470
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/ok-to-test


adding link to relevant tutorial

Hi @adhurwit, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

Fixed merge conflict and incorporated edits into https://github.com/Azure/azure-content-pr/pull/12260


fix(post office): Disabling post office client until bugs can be fixed

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


Fig1112

Codecov Report

Merging #727 (68cfd40) into master (668a1d3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #727   +/-   ##
=======================================
  Coverage   85.88%   85.88%
=======================================
  Files          22       22
  Lines        1679     1679
=======================================
  Hits         1442     1442
  Misses        237      237

Flag
Coverage Δ

unittests
85.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Codecov Report

Merging #727 (68cfd40) into master (668a1d3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #727   +/-   ##
=======================================
  Coverage   85.88%   85.88%
=======================================
  Files          22       22
  Lines        1679     1679
=======================================
  Hits         1442     1442
  Misses        237      237

Flag
Coverage Δ

unittests
85.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

@aarmey I saved figure 11 and 12 in ``lineage/figures/cartoonsasfig11.svgandfig12.svg, but tried to address it as ./lineage/figures/cartoons/figu11.svgor./output/fig11.svg` (while copying it to the output folder) but it doesn't show it. I looked at figure 2 which is purely a cartoon, but we are just calling it from the output folder and it appears. Could you please take a look at this?

@aarmey I saved figure 11 and 12 in ``lineage/figures/cartoonsasfig11.svgandfig12.svg, but tried to address it as ./lineage/figures/cartoons/figu11.svgor./output/fig11.svg` (while copying it to the output folder) but it doesn't show it. I looked at figure 2 which is purely a cartoon, but we are just calling it from the output folder and it appears. Could you please take a look at this?


BigQuery: Add Clustering support (DO NOT SUBMIT)

DO NOT SUBMIT
Adds Clustering support to BigQuery.  Also includes ability to add TimePartitioning configuration as part of load and query jobs, as this functionality was not yet included in the veneer.

I didn't split TimePartitioning out because clustering will require a partitioned table at the outset, and the timeline is short enough at this point to just push it all at once.

@shollyman is this one nearly ready to submit?