Specification/schema development policy and branching

The BIDS specification, schema and validator lifecycles are currently mixed. The schema is updated linearly with main, and there is no method to maintain a branch of the schema that fixes issues with the schema for the stable release without also including new features in the main branch.
As the validator is now heavily reliant on the schema, there is no difference to the validator between an update that fixes a bug in the schema and one that introduces a feature, which could potentially be changed or reverted before the next release of BIDS.
Here I propose a parallel branching strategy for the specification and the validator.
Legend:

main: bids-specification:main
maint/1.10.0: bids-specification:maint/1.10.0
validator-stable: bids-validator:stable (or bids-validator:maint/1.15.x)
validator-main: bids-validator:main

---
config:
  gitGraph:
    parallelCommits: false
---
gitGraph TB:
  branch validator-stable order: 2
  commit id: "v1.15.0.devN"
  checkout main
  commit tag: "v1.10.0" id: "schema-0.11.3"
  branch maint/1.10.0 order: 1
  checkout validator-stable
  merge main tag: "v1.15.0"
  branch validator-main order: 3
  checkout main
  commit id: "schema-0.11.4.dev1"
  checkout validator-main
  merge main id: "v1.15.1.dev1"
  checkout main
  commit id: "schema-0.11.4.dev2"
  checkout validator-main
  merge main id: "v1.15.1.dev2"
  checkout main
  checkout maint/1.10.0
  commit id: "schema-0.11.3.post1"
  checkout validator-stable
  merge maint/1.10.0 tag: "v1.15.1"
  checkout main
  merge maint/1.10.0 id: "schema-0.11.4.dev3"
  checkout validator-main
  merge main id: "v1.15.1.dev3"
  checkout main
  commit id: "schema-0.11.4.dev4"
  checkout validator-main
  merge main id: "v1.15.1.dev4"
  checkout main
  commit id: "schema-0.11.4.dev5"
  checkout validator-main
  merge main id: "v1.15.1.dev5"
  checkout maint/1.10.0
  commit id: "schema-0.11.3.post2" tag: "v1.10.0.post1"
  checkout validator-stable
  merge maint/1.10.0 tag: "v1.15.2"
  checkout main
  merge maint/1.10.0 id: "schema-0.11.4.dev6"

By using .postN releases for fixes to the schema and .devN releases for new changes, the stable validator could follow the latest .post and the development version could follow the latest .dev.
I also include a v1.10.0.post1 tag, which could be used for schema fixes that have rendering consequences, or things like fixing typos in the spec.
Note that the "merges" between the specification and validator branches are not actual git merges. They would be the validator updating pins to versions of the schema pushed to https://jsr.io/@bids/schema/versions.

This post is motivated by validation considerations, but has implications for how we operate on the specification. Therefore I am posting this here, as well as https://github.com/bids-standard/bids-validator/issues/85, where I expect the discussion to focus more around the mechanics of keeping validator branches synchronized to schema releases.

I've created maint/1.10.0: https://github.com/bids-standard/bids-specification/compare/v1.10.0...maint/1.10.0
I believe this contains the semantically neutral differences that have been merged since the release of v1.10.0. Please let me know if you disagree. You can also see the changes against master, which I didn't include: https://github.com/bids-standard/bids-specification/compare/maint/1.10.0...master
I will start working on the tooling to handle the schema publication from the maintenance branch.

@effigies
I added a branch proctection for the 'maint'  branches: I will let you edit it further.
https://github.com/bids-standard/bids-specification/settings/branches

Thanks @Remi-Gau. I updated the branch definition (maint/*), and I set it to require one reviewer. Their job will be to ensure that the changes are semantically neutral in the spec (as opposed to the schema, which can be brought more into line with the spec), which should be sufficient for maint/* branches.


Empty ClassNotFoundException

I have a big problem with the library which is not very transparent for me. Here the exception i get in diffrent situations:

Exception in thread "main" de.hetzge.sgame.common.exception.NetworkException: java.io.IOException: java.lang.RuntimeException: CLASSNAME:
at de.hetzge.sgame.network.Client.connect(Client.java:47)
at de.hetzge.sgame.network.NetworkModule.update(NetworkModule.java:36)
at de.hetzge.sgame.application.ModulePool.update(ModulePool.java:30)
at de.hetzge.sgame.application.Application.update(Application.java:27)
at de.hetzge.sgame.application.Application.start(Application.java:17)
at de.hetzge.sgame.game.Client.main(Client.java:32)
Caused by: java.io.IOException: java.lang.RuntimeException: CLASSNAME:
at org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:242)
at de.hetzge.sgame.common.serializer.Serializer.deserialize(Serializer.java:35)
at de.hetzge.sgame.network.Connection.read(Connection.java:26)
at de.hetzge.sgame.network.Client.connect(Client.java:36)
... 5 more
Caused by: java.lang.RuntimeException: CLASSNAME:
at org.nustaq.serialization.FSTClazzNameRegistry.classForName(FSTClazzNameRegistry.java:212)
at org.nustaq.serialization.FSTClazzNameRegistry.classForName(FSTClazzNameRegistry.java:183)
at org.nustaq.serialization.FSTClazzNameRegistry.decodeClass(FSTClazzNameRegistry.java:166)
at org.nustaq.serialization.coders.FSTStreamDecoder.readClass(FSTStreamDecoder.java:422)
at org.nustaq.serialization.FSTObjectInput.readClass(FSTObjectInput.java:855)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:340)
at org.nustaq.serialization.FSTObjectInput.readObjectFields(FSTObjectInput.java:659)
at org.nustaq.serialization.FSTObjectInput.instantiateAndReadNoSer(FSTObjectInput.java:517)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:358)
at org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:325)
at org.nustaq.serialization.serializers.FSTCollectionSerializer.instantiate(FSTCollectionSerializer.java:90)
at org.nustaq.serialization.FSTObjectInput.instantiateAndReadWithSer(FSTObjectInput.java:461)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:356)
at org.nustaq.serialization.FSTObjectInput.readObjectFields(FSTObjectInput.java:659)
at org.nustaq.serialization.FSTObjectInput.instantiateAndReadNoSer(FSTObjectInput.java:517)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:358)
at org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:325)
at org.nustaq.serialization.serializers.FSTCollectionSerializer.instantiate(FSTCollectionSerializer.java:90)
at org.nustaq.serialization.FSTObjectInput.instantiateAndReadWithSer(FSTObjectInput.java:461)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:356)
at org.nustaq.serialization.FSTObjectInput.readObjectFields(FSTObjectInput.java:659)
at org.nustaq.serialization.FSTObjectInput.instantiateAndReadNoSer(FSTObjectInput.java:517)
at org.nustaq.serialization.FSTObjectInput.readObjectWithHeader(FSTObjectInput.java:358)
at org.nustaq.serialization.FSTObjectInput.readObjectInternal(FSTObjectInput.java:325)
at org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:306)
at org.nustaq.serialization.FSTObjectInput.readObject(FSTObjectInput.java:240)
... 8 more
Caused by: java.lang.ClassNotFoundException:
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.nustaq.serialization.FSTClazzNameRegistry.classForName(FSTClazzNameRegistry.java:190)
... 33 more

The classname of the class which is not found is empty. I think the reason for the exception ist something else. The application sends objects over the network and deserialize them with the library. The error happens if  i send more then a special amount of objects. If i send 10 objects (packed in a collection) it works fine. But if i increase to say 50 objects the error happens. All changed is the amount of the objects which are created the same way.
Here are my serialize methods:
public static byte[] serialize(Object object) throws IOException {
		FSTObjectOutput objectOutput = CommonConfig.INSTANCE.fst.getObjectOutput();
		objectOutput.writeObject(object);

		ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream();
		byteArrayOutputStream.write(objectOutput.getBuffer(), 0, objectOutput.getWritten());

		byte[] byteArray = byteArrayOutputStream.toByteArray();
		byteArrayOutputStream.close();
		return byteArray;
	}

	public static Object deserialize(byte[] bytes) throws IOException, ClassNotFoundException {
		ByteArrayInputStream byteArrayInputStream = new ByteArrayInputStream(bytes);
		FSTObjectInput objectInput = CommonConfig.INSTANCE.fst.getObjectInput(byteArrayInputStream);
		Object readObject = objectInput.readObject();
		byteArrayInputStream.close();
		return readObject;
	}

Here the code i use for the network communication:
public class Connection {

	private final Socket socket;
	private final DataOutputStream dataOutputStream;
	private final DataInputStream dataInputStream;

	public Connection(Socket socket) throws IOException {
		this.socket = socket;
		this.dataOutputStream = new DataOutputStream(socket.getOutputStream());
		this.dataInputStream = new DataInputStream(socket.getInputStream());
	}

	public Object read() throws IOException, ClassNotFoundException {
		int length = this.dataInputStream.readInt();
		byte[] byteArray = new byte[length];
		this.dataInputStream.read(byteArray);
		return Serializer.deserialize(byteArray);
	}

	public void write(Object message) throws IOException {
		byte[] serialized = Serializer.serialize(message);
		this.dataOutputStream.writeInt(serialized.length);
		this.dataOutputStream.write(serialized);
		this.dataOutputStream.flush();
	}

}
```

It looks like registering the classes allows a higher amount of classes.

Any idea what i am doing wrong ?
... or are more informations needed ?

this happens if the stream is corrupted:
possible reasons:

if you stream objects, first write length then object array, you cannot deserialize if only parts of objects have been received. see https://github.com/RuedigerMoeller/fast-serialization/blob/master/src/main/java/org/nustaq/net/TCPObjectSocket.java and the server class
by incorrect multithreading
you need to register classes on sender side and receiverside identically and in same order
consider using TCPObjectSocket, TCPObjectServer delivered with fst. If this does not fit, see how i always write length of a message as a header. This way i can decode once i am sure the full message is received. Reason is, I can't go down all the wrapped streams of jdk for each byte read (very slow), so stream must be read in chunks of one serialized object

Your use of fst is quite inefficient, simplify:

use utils FSTConfiguration.asByteArray, asObject to get rid of bytearraystreams (SLOW).
remove classregistering for debug. once stuff runs, add it again. class registering is a very easy and effective opzimization, but must be symmetric sender/receiver.
ensure you use latest version

this happens if the stream is corrupted:
possible reasons:

if you stream objects, first write length then object array, you cannot deserialize if only parts of objects have been received. see https://github.com/RuedigerMoeller/fast-serialization/blob/master/src/main/java/org/nustaq/net/TCPObjectSocket.java and the server class
by incorrect multithreading
you need to register classes on sender side and receiverside identically and in same order
consider using TCPObjectSocket, TCPObjectServer delivered with fst. If this does not fit, see how i always write length of a message as a header. This way i can decode once i am sure the full message is received. Reason is, I can't go down all the wrapped streams of jdk for each byte read (very slow), so stream must be read in chunks of one serialized object

Your use of fst is quite inefficient, simplify:

use utils FSTConfiguration.asByteArray, asObject to get rid of bytearraystreams (SLOW).
remove classregistering for debug. once stuff runs, add it again. class registering is a very easy and effective opzimization, but must be symmetric sender/receiver.
ensure you use latest version

Very big thanks for the detailed and fast answer. When i use the TCPObjectSocket class my problem is blown away.
You could throw a more meaningful exception and refer the TCPObjectSocket class in the "How to use Serialization" page in the wiki.

:-) i already updated the wiki, as there where other persons having similar issues .. throwing other exceptions is not too easy, as if stream is corrupted (or just plain 0,0,0,..) anything can fail during decode .. i'll try though. Thanx for reporting


[resolves #1889] Cannot obtain direct consumer with spring context

The meaning of noStart flag on SpringCamelContext was slightly changed with CAMEL-11261, it blocks any SpringCamelContext startup even the one invoked explicitly via start method.
This changes the creation of SpringCamelContext so that the noStart is set and maintained while Spring application context is refreshed, but reset to true after.
This might be considered as a workaround, as the behaviour changed in upstream. I would very much like to remove the noStart flag as it is global to all SpringCamelContext's and prefer to use Camel's isAutoStartup flag or introduce a new per Camel Context flag. This is perhaps the discussion we need to have in Camel.

It doesn't seem to be correct to mandate this sort of change on every client that uses SpringCamelContextFactory.
The contract is, that this simple sequence works
        CamelContext camelctx = SpringCamelContextFactory.createSingleCamelContext(resourceUrl, null);
        Assert.assertEquals(ServiceStatus.Stopped, camelctx.getStatus());
        camelctx.start();
        try {
            ProducerTemplate producer = camelctx.createProducerTemplate();
            String result = producer.requestBody("direct:start", "Kermit", String.class);
            Assert.assertEquals("Hello green Frog", result);
        } finally {
            camelctx.stop();
        }

#1 After the SpringCamelContext is created, it is in state 'stopped'
#2 SpringCamelContext.start() is a blocking operation which makes resources on the context available
#3 SpringCamelContext.start() is also a blocking operation
Hopefully we can keep this contract such that not every client (on the planet) of this API needs to be changed. This API is however an abstraction of the respective Camel & Spring APIs. It means, that we can do all sorts of voodoo here.

Yeah, those tests remained from another solution that I tried, rolled them back, the contract should stay the same.

@tdiesler any thoughts on the revised PR? Do you think it would be better to make the change on Camel's side, and keep the previous behaviour?

The SpringCamelContextFactory creates a list of SpringCamelContext objects from the descriptor. Although I haven't looked at the details of interaction of this ThreadLocal flag and how it affects behavior on the individual instances. From how this is scoped it seems that every SpringCamelContext that is associated with the same Thread is affected.
We are starting/stopping the CamelContext as part of the deployment lifecycle in [CamelContextActivationProcessor|https://github.com/wildfly-extras/wildfly-camel/blob/master/subsystem/core/src/main/java/org/wildfly/extension/camel/deployment/CamelContextActivationProcessor.java]. Because of that we did not want the SpringCamelContext to start automatically. We need this level of control, because previous (pluggable) DeploymentUnitProcessors (DUP) might do additional stuff before this later DUP activates the CamelContext.
In short, CamelContexts being created by SpringCamelContextFactory must not start automatically.
What does this line actually do?
{code}
SpringCamelContext.setNoStart(false)
{code}
If it is a flag that simply allows a later manual start, which would otherwise be prevented, we can accept this PR. If you can handle this at the Camel level without affecting this factory code, even better.

What does this line actually do?
SpringCamelContext.setNoStart(false)
If it is a flag that simply allows a later manual start, which would otherwise be prevented, we can accept this PR. If you can handle this at the Camel level without affecting this factory code, even better.

As it stands now it allows SpringCamelContext to start, and that is a change from previous behaviour, previously setting SpringCamelContext.setNoStart(true) would prevents automatic startup with the Spring application context, now it prevents any startup. I'm trying to refactor 11261 to have the new behaviour of automatically starting last and automatically stopping first and have the old behaviour of noStart flag. This is proving to be somewhat difficult.

This has been improved by @tdiesler and commited to camel-2.20.x branch


vue icon is not getting displayed

Hi,
the original material theme displays the vue icon which is not getting displayed in the materialize theme
please see the following links
https://infinit.io/_/3evnXEf
https://infinit.io/_/gzhKFkX

I will have this fixed by tomorrow.

This issue should be fixed, I will push the changes to Package Control shortly. Please reopen the issue there is any further issue with it.

Changes have been made, please validate that the Vue icons are working when you get a chance.


Unable to open help documentation for functions

Dear all,
Apologies in advance if this is a duplicate issue.
I am using R via SSH (so a self-managed R session).
I have set the following settings: r.alwaysUseActiveTerminal, r.rpath.linux, and r.rterm.linux. However, I am still getting this error when trying to open help (e.g. ?plot) or hovering my cursor over a function on the editor.
Failed to get list of R functions. Make sure that `jsonlite` is installed and r.rpath.linux points to a valid R executable.

as well as
The "file" argument must be of type string. Received undefined

Note that I have installed jsonlite. Can anyone give any advice? Much appreciated.

Are you using the remote ssh extension (see here), or just a normal terminal and then SSH into your server?
In the latter case, many functions won't work, since the vscode-R extension cannot access the R process running on the server.

As @ManuelHentschel points out, vscode-R cannot access a remote R terminal started by a user since it does not have direct file system access where the R process does.
It you are accessing remote R terminal, you need to use the Remote-SSH approach.

Thanks for the advice! @ManuelHentschel @renkun-ken
It works perfectly now after using the Remote-SSH approach :)


README.md: add guidance on expressions of interest

closes https://github.com/open-contracting/ocds-extensions/issues/41

I think that we should pause this PR until the points discussed in https://github.com/open-contracting/ocds-extensions/issues/41 are settled

I'll follow up - thanks for the reminder.

whether to add a discriminator field, whether to rename Bid to Response etc.

Let's add a discriminator field and do the renaming, but we can discuss details in https://github.com/open-contracting/ocds-extensions/issues/41

@jpmckinney Re. statistic should we also add new codes to disclose the results of the evaluation of the EOIs? So:

'validExpressionsOfInterest'
'disqualifiedExpressionsOfInterest'

disclose the results of the evaluation of the EOIs

If we didn’t need such codes for eForms, then I think no jurisdiction tracks such statistics.


[docs] Fix DatePicker of 'Customization' section

Environment

Tech
Version

@material-ui/pickers
v4.0.0-alpha.8

Description
The DatePicker of 'Customization' section is broken.
https://next.material-ui-pickers.dev/demo/datepicker#customization

Interesting. @dmtrKovalenko What do you think of updating the current eslint configuration to match the one from the main repository? If I lint docs/pages/demo/datepicker/CustomDay.example.jsx with the eslint config of the main repo, we get this error:

Arguably, it could help avoid cases like this one :)


Unable to delete files in blob after upgrade

Storage Explorer Version1.11
Build Number: 20191105.2
Platform/OS: windows 10
Architecture:  x64
Regression From: yes
Bug Description
Unable to delete blob files in a blob container. the Delete is stuck at Deleting....
Steps to Reproduce

Expected Experience

Actual Experience

Additional Context

Can you give a screen shot of the activity log message and share the AzCopy Log with us? You can find the log file at C:\Users\(your_username)\.azcopy\(the file that matches the creation time).

There is an empty folder called plans under the .azcopy

Can I go back to a previous version which allowed me to uncheck Azcopy integration? Even when I install a previous version, it seems to install the latest one..

You can find the previous release here. v1.10.1 release
Based on the activity message, AzCopy hasn't finished discovery meaning that it hasn't finished listing the blob to delete. AzCopy has an aggressive retry strategy and won't show failure unless it has been retrying for a long time.

How long should I wait for it to discover. Its just a single file to delete. and i waited for more than a minute. Even cancel doesnt work..

I'm experiencing similar delete action wait times. Instead of 30 sec before the upgrade to the latest version, I'm having to wait 3-5 minutes for the operation to complete.

@gjadal, we have recently fixed a bug related to key attached Storage Accounts where AzCopy uses incorrect endpoints. This is included in the 1.11.1 release. If it applies to your situation, you can try upgrading Storage Explorer.
We have noticed that AzCopy is abnormally slow in some situations, but we haven't seen it being stuck. If you are still blocked by this issue, please comment below and try to find the log file for us. Or you can open another issue instead.

Is anyone still seeing this problem?


Kuadrant Operator is crashing when installed via addon manager

When Kuadrant is installed via addon manager using weekly build: https://quay.io/kuadrant/kuadrant-operator-catalog:aebe2ec63e1bfad0f391c329a9c9f6ede36086d9
The Kuadrant Operator is caught in the endless cracking loop (keeps changing status from Succeeded and Installing).
Two pods are on CrashLoopBackOffs:

kuadrant-operator-controller-manager -
kuadrant-operator-controller-manager-5f54f695b-mlk7n-manager.log

kuadrant-operator-policy-controller -
kuadrant-operator-policy-controller-5ff6ddc9c8-djbdn-policy-controller.log

Short slack communication: https://kubernetes.slack.com/archives/C05J0D0V525/p1700661805580859

Based on the logs, I believe it is caused by us having older GW API version. Will verify and resolve this issue if that is indeed the case.

To be verified... looks like a GwAPI types version issue possibly

It was indeed issue of an older GW API


Move keybinding configuration to separate file.

Use cobra and viper to handle configuration.

Defaults will still exist, but they can be overridden.

We're going to stick with just viper for now.
The configuration syntax will be:
{
    "keybindings": {
        "KEYCODE_COMMAND": "c",
    }
}

Constant names are used as the key.

This issue will take another day. :-1:


Can't seem to filter out Azure.Storage.Blob logs from Event Hub extension

I've been noticing many log messages similar to this, and they come through as Informational.    I believe they're coming from the Event Hub Extension?
I've tried adding LogLevel filtering for "Azure" as "Warning", but can't seem to filter them out in Application Insights.
They end up taking a considerable amount of Log Workspace GB, so I'd like to get rid of them in normal usage.
Any ideas on how to better filter this?  Thanks.
Request [b5e0bce2-1d11-4335-9ed0-5976fcf8d510] PUT https://REDACTED.blob.core.windows.net/azure-webjobs-eventhub/REDACTEDservicebus.windows.net/posts/%24default/ownership/23?comp=REDACTED
x-ms-meta-ownerid:REDACTED
If-Match:REDACTED
x-ms-version:REDACTED
Accept:REDACTED
x-ms-client-request-id:REDACTED
x-ms-return-client-request-id:REDACTED
User-Agent:REDACTED
x-ms-date:REDACTED
Authorization:REDACTED
client assembly: Azure.Storage.Blobs
Response [781e73a0-d3dd-4fbd-961c-30fbfb438449] 200 OK (00.0s)
ETag:REDACTED
Server:REDACTED
x-ms-request-id:REDACTED
x-ms-client-request-id:REDACTED
x-ms-version:REDACTED
x-ms-request-server-encrypted:REDACTED
Date:REDACTED
Content-Length:REDACTED
Last-Modified:REDACTED

Hi @kirk-marple.   With the extension package v5+, you'd need to filter the Azure.Core log source to control Storage logs.   For example, to set them and the Event Hubs logs to warning only:
"Logging": {
  "LogLevel": {
    "Azure.Core": "Warning"
    "Azure.Messaging.EventHubs": "Warning"
  }
}

Thanks, I'll give this a shot and report back.

I'm still seeing these even with that LogLevel change.

Here's our host.json.
{
    "version": "2.0",
    "extensions": {
        "eventHubs": {
            "batchCheckpointFrequency": 5,
            "eventProcessorOptions": {
                "maxBatchSize": 3,
                "prefetchCount": 10
            }
        }
    },
    "Logging": {
        "LogLevel": {
            "Default": "Trace",
            "Microsoft": "Warning",
            "Azure.Core": "Warning",
            "Azure.Messaging.EventHubs": "Warning"
        },
        "ApplicationInsights": {
            "LogLevel": {
                "Default": "Trace",
                "Microsoft": "Error",
                "Azure.Core": "Warning",
                "Azure.Messaging.EventHubs": "Warning"
            },
            "SamplingSettings": {
                "IsEnabled": true,
                "MaxTelemetryItemsPerSecond": 1500,
                "EvaluationInterval": "01:00:00",
                "InitialSamplingPercentage": 100.0,
                "SamplingPercentageIncreaseTimeout": "00:00:01",
                "SamplingPercentageDecreaseTimeout": "00:00:01",
                "MinSamplingPercentage": 50.0,
                "MaxSamplingPercentage": 100.0,
                "MovingAverageRatio": 1.0,
                "ExcludedTypes": "Dependency;Exception;Trace",
                "IncludedTypes": "PageView;Request;Event"
            },
            "EnableLiveMetrics": true,
            "EnableDependencyTracking": true,
            "EnablePerformanceCountersCollection": true,
            "HttpAutoCollectionOptions": {
                "EnableHttpTriggerExtendedInfoCollection": false,
                "EnableW3CDistributedTracing": true,
                "EnableResponseHeaderInjection": true
            }
        }
    }
}

Also, you can see it's generating a lot of traces:

Hi @kirk-marple.   Apologies: I did not realize that you were referring to the Live Metrics view.   The log filtering configuration that you've set should be applied to the data stored in AppInsights that you'd see when you look in Monitoring > Logs and the data stored there - but will not work with Live Metrics.
My understanding is that, by design, Live Metrics will capture all logs and does not respect the ILogger configuration.   Unfortunately, this isn't something that the Event Hubs extension (or others) can influence or bypass.   Any change to this behavior would need to come from the Microsoft.Azure.WebJobs.Logging.ApplicationInsights package.
Assuming that I haven't misunderstood, our best bet for next steps would be to open an issue in the WebJobs Repository referencing that you're unable to filter WebJobs extension logs in the AppInsights Live Metrics view.

@jsquire Sorry for any confusion, but actually this isn't about Live Metrics.  I'm purely looking in 'Transaction search' in App Insights, and see the all extra logging.
The screenshot I pasted above was just from the App Insights 'Transaction search' page.

Apologies for the confusion.  Unfortunately, we're at the ends of my knowledge for how AppInsights integrates with the logs that our clients emit.  I'm going to pull in a colleague with deeper understanding of how AppInsights presents data; it may take a day or so, but I'll loop back around with updates then.

No worries @jsquire.  Given these logs are coming from 'deep down' in the Event Hub Triggers, I've always been curious if host.json or appsettings.json affects their log levels.

@kirk-marple I'm trying to reproduce the error, but when I use a template EventHub Trigger function with the host.json file you provided, I can control "Azure.Core" and  "Azure.Messaging.EventHubs" log levels without any problem (with ApplicationInsights:LogLevel).
Do you happen to have any additional in-code configuration for Application Insights SDK or logging? If you provide a repro app it would also be a tremendous help.

@kirk-marple I believe the question is more about what you do with that TelemteryClient. Can you please share the code you have with regards to AppInsights configuration? Since the issue does not repro in a template Function, the issue is very likely related to your configuration. Having a repro app would speed up investigation a lot.
Please note that we don't own Azure Function integration with Application Insights and can only forward it to the right team.

@kirk-marple this issue got closed, but I wonder, could it be that you run function with isolated worker?
If so, would you be able to try setting AzureFunctionsJobHost__logging__logLevel__default or AzureFunctionsJobHost__logging__logLevel__Azure.Core to Warning ?

@lmolkova We are using in-process, since we have Durable Entities, and they hadn't been supported yet (not sure if they are yet).
I'd played around with Azure.Core and default in host.json, with no success.
Here's the logging section from our host.json.
    "logging": {
        "logLevel": {
            "default": "Trace",
            "Microsoft": "Warning"
        },
        "applicationInsights": {
            "logLevel": {
                "default": "Trace",
                "Microsoft": "Error"
            },
            "samplingSettings": {
                "isEnabled": true,
                "maxTelemetryItemsPerSecond": 200,
                "excludedTypes": "Dependency;Exception;Trace",
                "includedTypes": "PageView;Request;Event"
            },
            "enableLiveMetrics": false,
            "enableDependencyTracking": true,
            "enablePerformanceCountersCollection": true,
            "httpAutoCollectionOptions": {
                "enableHttpTriggerExtendedInfoCollection": false,
                "enableW3CDistributedTracing": false,
                "enableResponseHeaderInjection": true
            }
        }
    }


I am unable to execute typedoc

Expected Behavior
It should build docs
Actual Behavior
It is failing

Steps to reproduce the bug
command: ./node_modules/typedoc/bin/typedoc "./src/index.ts" --exclude "**/{node_modules/**/*,*.spec}.ts" --tsconfig "./tsconfig.json"
packages:
    "@czlowiek488/swagger-express-ts": "^1.0.4",
    "@google-cloud/firestore": "^4.12.0",
    "@google-cloud/pubsub": "^2.12.0",
    "@google-cloud/storage": "^5.8.5",
    "@tshio/awilix-resolver": "^1.0.2",
    "@tshio/command-bus": "^1.0.2",
    "@tshio/event-dispatcher": "^1.0.2",
    "@tshio/logger": "^1.0.4",
    "@tshio/query-bus": "^1.0.2",
    "@tshio/security-client": "0.0.19",
    "@xtrf/tms-messages": "^1.1.11",
    "apollo-server-express": "^2.11.0",
    "awilix": "^4.2.6",
    "celebrate": "^12.1.1",
    "class-transformer": "^0.2.3",
    "cors": "^2.8.5",
    "dotenv": "^8.2.0",
    "express": "^4.17.1",
    "express-async-errors": "^3.1.1",
    "faker": "^5.5.3",
    "firebase-admin": "^9.8.0",
    "graphql": "^15.0.0",
    "helmet": "^3.22.0",
    "http-status-codes": "^1.4.0",
    "jsonwebtoken": "^8.5.1",
    "jwt-decode": "^3.1.2",
    "lodash": "^4.17.21",
    "luxon": "^1.27.0",
    "pg": "^8.0.3",
    "reflect-metadata": "^0.1.13",
    "source-map-support": "^0.5.19",
    "swagger-ui-dist": "^3.35.1",
    "ts-pipe-compose": "^0.2.1",
    "utility-types": "^3.10.0",
    "uuid": "^8.3.2",
    "winston": "^3.2.1"
  },
  "devDependencies": {
    "@commitlint/cli": "^12.1.1",
    "@commitlint/config-conventional": "^12.1.1",
    "@graphql-codegen/cli": "^1.13.1",
    "@graphql-codegen/typescript": "^1.13.1",
    "@graphql-codegen/typescript-resolvers": "^1.13.1",
    "@types/chai": "^4.2.11",
    "@types/chai-as-promised": "^7.1.2",
    "@types/cors": "^2.8.6",
    "@types/dotenv": "^8.2.0",
    "@types/express": "^4.17.6",
    "@types/express-serve-static-core": "^4.17.5",
    "@types/faker": "^5.5.6",
    "@types/helmet": "0.0.46",
    "@types/jsonwebtoken": "^8.3.9",
    "@types/lodash": "^4.14.170",
    "@types/luxon": "^1.27.0",
    "@types/mocha": "^7.0.2",
    "@types/node": "^13.13.4",
    "@types/sinon": "^10.0.2",
    "@types/supertest": "^2.0.8",
    "@types/uuid": "^7.0.3",
    "@typescript-eslint/eslint-plugin": "^2.30.0",
    "@typescript-eslint/parser": "^2.30.0",
    "chai": "^4.2.0",
    "chai-as-promised": "^7.1.1",
    "chalk": "^4.0.0",
    "eslint": "^6.8.0",
    "eslint-config-airbnb-typescript": "^7.2.1",
    "eslint-config-prettier": "^6.11.0",
    "eslint-plugin-import": "^2.20.2",
    "eslint-plugin-no-only-tests": "^2.4.0",
    "eslint-plugin-prettier": "^3.1.3",
    "eslint-plugin-unicorn": "^19.0.1",
    "husky": "^4.3.0",
    "lodash.kebabcase": "^4.1.1",
    "mocha": "^9.0.0",
    "nock": "^13.0.5",
    "nyc": "^15.1.0",
    "plop": "^2.6.0",
    "prettier": "^2.0.5",
    "sinon": "^11.1.1",
    "supertest": "^4.0.2",
    "typedoc": "^0.21.0",
    "typescript": "^4.3.4"

tsconfig
{
  "compilerOptions": {
    "target": "es2019",
    "types": ["node"],
    "module": "commonjs",
    "declaration": false,
    "strict": true,
    "allowSyntheticDefaultImports": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "strictPropertyInitialization": false,
    "sourceMap": false,
    "inlineSourceMap": true,
    "outDir": "build",
    "typeRoots": ["./node_modules/@types"],
    "resolveJsonModule": true
  },
  "include": [
    "src/**/*.ts",
    "config/**/*.ts",
    "tests/**/*.ts"
  ],
  "exclude": ["node_modules", "build/**"]
}

Environment

Typedoc version: 0.21.0
TypeScript version: 4.3.4
Node.js version: 12.18.1
OS: WSL Ubuntu

Have you tried adding esModuleInterop: true to your tsconfig as the error suggests?

Yes, I did. But it does not change anything.
wt., 22 cze 2021, 03:56 użytkownik Gerrit Birkeland <
@.***> napisał:

Have you tried adding esModuleInterop: true to your tsconfig as the error
suggests?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TypeStrong/typedoc/issues/1603#issuecomment-865461189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIEFTPDK3AWLPLTY6JP2M3TT7UUZANCNFSM47CPGU2Q
.

I'm going to need a repro to look at then (ideally one without 100 dependencies...), I don't have the time to try to create one from scratch for reported bugs

@Gerrit0
I prepared one minimal for you. Just hit npm i and npm run typedoc then you will see errors. Tested on node 12.22.1.
https://github.com/czlowiek488/typedoc-bug-report
Also I found another bug which happend when I dont have installed peer dependency (here graphql). You can check it if you pull this commit (execute the same way).
https://github.com/czlowiek488/typedoc-bug-report/commit/aab0b96aee5b42e6467405d2bbb9b5391437b9eb

Oops, I forgot that esModuleInterop wasn't the only option that controlled imports - the apollo-server-express package uses allowSyntheticDefaultImports, which means that every package which depends on it is also effectively forced to turn that compiler option on. (This is why Definitely Typed forbids that option)
diff --git a/tsconfig.json b/tsconfig.json
index 8ecfccc..785b192 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -5,7 +5,7 @@
     "module": "commonjs",
     "declaration": false,
     "strict": true,
-    "allowSyntheticDefaultImports": false,
+    "allowSyntheticDefaultImports": true,
     "emitDecoratorMetadata": true,
     "experimentalDecorators": true,
     "strictPropertyInitialization": false,

With this change, the docs build. Without it, they don't. This matches TypeScript's behavior. If you compile with tsc you'll see the same result. If you move the skipLibCheck option from your build command to the tsconfig, TypeDoc will also run.
I tried checking out the other commit, and with the allowSyntheticDefaultImports change, TypeDoc seems to behave properly there as well. If you have type errors, it is expected that TypeDoc won't build.


Fix MapAttribute serialization bug

@allen-baggio

+1

see https://github.com/jmphilli/PynamoDB/pull/3


Sun Position Analysis Tools needs test written

Sun Position Analysis Tools needs test written for Sun Position and Hillshade tool.

Fixed this in Pull #289. Would like someone to test this and verify it's working.

Nobody to test this one separately. Closing this for now.


Search editor: should initially report as dirty if loaded from backup

Steps to Reproduce (macOS):

open a search editor
mark it dirty (notice how the window reports dirty state via the black dot on the close button)
close vscode
start vscode
=> 🐛 no dirty indication in the black dot of the close button

I believe this is caused by this: when you restore the search editor and find a backup, even though you put the contents of the backup into the editor, you do not set the input as dirty. So there is no dirty change event on the input.

Moving to Feb to verify in endgame via https://github.com/microsoft/vscode/commit/29a15dd045a9d6d7e633944ea30dad0f8366bdc0


Issue with Bad local variable type with another mod's WrapOperation LocalRef

I'm unsure what's going on here, but I seem to be running into this inside the dev environment. This works fine in production.
It could be my setup with a don't remap fabric loom (common) and a fabric loom (fabric specific), but I'm quite lost.
Project:
https://github.com/MerchantPug/apugli/tree/1.20.2
Crashlog:
https://gist.github.com/MerchantPug/2d06a544c8dd0c699a0a18d4739fce87

I'll link my repo when I'm done with a few things.

https://github.com/MerchantPug/apugli/tree/1.20.2

This is caused by having -Dmixin.debug.verify=true on. You should never really set mixin.debug globally, instead set the specific options you want like verbose and export. I will fix the issue at some point but verify is broken in many other ways so it's not an urgent priority.

This is caused by having -Dmixin.debug.verify=true on. You should never really set mixin.debug globally, instead set the specific options you want like verbose and export. I will fix the issue at some point but verify is broken in many other ways so it's not an urgent priority.

Thanks. 👍

Fixed in 0.2.1


[Question] How to disable autoplay on click?

I would like to set the 'autoplay' option to 'false' when the user clicks inside of the slider, how can I do this?

The problem was actually caused by having the arrows set to "display: none" by default. When slick is initialized the arrows would show, but after clicking they would disappear.


Sweep Clock: reduced memory footprint

Was able to slash 12% from the memory footprint thanks to the RAM widget.

Great - thanks! It's really good to have these kinds of tweaks :)


Connect to Azure Container Registry

I've been following the julia_batch_docker.ipynb example, but trying to use Azure Container Registry instead of DockerHub and I've been using the container option in the parameters.json ("_CONTAINER": "myorgregistry.azurecr.io/myimage:v0.1.0") but I continue to get an error ContainerInvalidImage with unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information. This is a private org container registry.
This is the closest example that I've found to another user attempting this solution: https://github.com/Azure/Batch/issues/107
And here's some docs for Python code that seems to do what I want: https://docs.microsoft.com/en-us/azure/batch/batch-docker-container-workloads#prefetch-images-from-a-private-container-registry
To me it seems like I need to be using a managed identity and to create batch pools with them. Is this something that can be supported by AzureClusterlessHPC.jl? Or is there a better solution than what I've found?
Thank you for your help!

@philippwitte can you help me with this issue and #20?

Bump @philippwitte


Crash with short module name in Library.detectPlatformMismatch()

Version
3.3.1
Platform
Windows x64
JDK
Corretto 1.8.0_302 (bundled with IntelliJ)
Module
LWJGL core
Bug description
I'm (ab-)using Library.loadSystem() to load shared libraries. When passing an empty (or short) module name parameter, a call to detectPlatformMismatch() will crash because the substring() call in its first code line will be out of bounds.
The name must be shorter than "org.lwjgl." and different to "org.lwjgl" for the crash to happen. Also, can only occur after loading the library has failed already.
Stacktrace or crash log output
No response

Thanks @code-disaster, detectPlatformMismatch will ignore non-LWJGL modules in the next 3.3.2 snapshot.

LWJGL 3.3.2 snapshot 3 is now available, could you please verify that it now works for you?

Yes, works. No more crashes. Now prints an error message and throws UnsatisfiedLinkError.


Property 'CompA' does not exist on type 'Pick<IntrinsicElements, "template"> & Pick<IntrinsicElements, "div">

Description
Not compatible with auto import.
Reproduction
Stackblitz

Note: if I set version: 2.7
Components({ version: 2.7 }),

there will be no vue-tsc errors, but components will not be auto-imported, the difference is in version 2.7,
the generated components.d.ts has a head like
export {}

declare module 'vue' {
  export interface GlobalComponents {
  // ...
  }
}

while default is
import '@vue/runtime-core'

export {}

declare module '@vue/runtime-core' {
  export interface GlobalComponents {
  // ...
  }
}

After upgrade to volar v1.7.6 and config .npmrc like (P.S. I use pnpm)
public-hoist-pattern[]=*@vue/*

The errors have gone.


ignore version file

Not sure what's generating these files, but I'm finding I frequently have to ignore them

Codecov Report
Patch and project coverage have no change.

Comparison is base (1a73881) 88.18% compared to head (9cad4f1) 88.18%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #645   +/-   ##
=======================================
  Coverage   88.18%   88.18%
=======================================
  Files          43       43
  Lines        3090     3090
  Branches      270      270
=======================================
  Hits         2725     2725
  Misses        324      324
  Partials       41       41

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


Refactored index page and display map/list

Assigned to @stephanieyshi and @anniemeng for code review

@sandlerben can you add screenshots for what you changed also?

@anniemeng happy to this time, in the future let's definitely set-up heroku review apps to automate this


Functionality-breaking errors on Gitpod - Cannot read properties of null (reading 'content')

Edit: Initially this issue was about getting stuck at 'Loading projects' when opening the Gitpod workspace. This wasn't the problem I initially had but I couldn't reproduce that at the time of creating the issue. I've since figured out that Gitpod caches VS Code extension settings to a certain extent and that caused the 'Loading projects' issue. Once the settings were cleared, I got back to the original issue described below of uncaught errors that broke a lot of functionality in Gitpod.
Describe the bug
Ionide doesn't fully work when opening the repo on Gitpod as a new workspace. It activates and the solution explorer works but there are no tooltips, no syntax checking, inlay hints, jump to definition, etc. There is an uncaught error on every attempt to get a tooltip: Cannot read properties of null (reading 'content').
Also, this line of code also appears not to be invoked/work correctly as launching the debugger throws an error of Cannot activate the 'Ionide for F#' extension because it depends on an unknown 'ms-dotnettools.csharp' extension. After manually updating release/package.json to reference the updated C# extension name with "extensionDependencies": ["muhammad-sammy.csharp"],  the extension activates in the extension development host but hovering to get a tooltip on code throws the same error as in the main VS Code window:
rejected promise not handled within 1 second: TypeError: Cannot read properties of null (reading 'content')
stack trace: TypeError: Cannot read properties of null (reading 'content')
	at /workspace/ionide-vscode-fsharp/release/fsharp.js:48567:224

Digging into the referenced JS line, it seems the issue is here where the response for a signature request is returned as null:
let signature (uri: Uri) line col =
        match client with
        | None -> Promise.empty
        | Some cl ->
            let req: Types.TextDocumentPositionParams =
                { TextDocument = { Uri = uri.ToDocumentUri }
                  Position = { Line = line; Character = col } }

            cl.sendRequest ("fsharp/signature", req)
            |> Promise.map (fun (res: Types.PlainNotification) -> res.content |> ofJson<Result<string>>)

I don't know enough to dig into why the language server is returning null unfortunately.
Steps to reproduce
Note that the Gitpod Dockerfile is out of sync with the required SDK version and needs to be manually updated to 6.0.401 in order to reproduce this. I haven't created a PR for that as I was hoping to contribute something more meaningful but I can if you'd like.

Fork the repo
Update the Gitpod Dockerfile's SDK version
Create a new Gitpod workspace with the updated repo
Once VS Code loads, wait for the build to complete
Run the 'Watch' task and wait for the build to complete
Update the compiled package.json with "extensionDependencies": ["muhammad-sammy.csharp"],
Run the 'Launch only' debug configuration

You should now have two windows where Ionide won't work properly in either - the first is with the published marketplace extension installed in the main development window and the second is the master branch launched in debug mode.
Expected behaviour
Ionide should load in both windows - main workspace and debugger.
Screenshots
Uncaught errors (looks the same in development and debugging windows):

Error in the extension development host on initially launching the debugger:

Machine info
Gitpod with Ionide 7.4.0 in the editor and master branch in the debugger.

I can't reproduce the above, but I can reproduce a different issue

Context: https://github.com/cartermp/otel-lang-samples

A few things made @cartermp's sample project work fine for me:

use adaptive LSP server
change the TFM of the project to net7.0 (unsure if this is required or not)

First thing I'd check in all cases is if the project cracking worked, which will show in a few ways - the PackageReferences node will usually have stuff in it, and the Show project status command will have a lot of data in it. If either of those aren't true, then binlogs would be next.

Yep, project cracking doesn't work (even if I move to net7 and use the adaptive LSP)

@cartermp when you launch the gitpod, can you cd to the project and run dotnet restore first, before opening the program.fs file?


Create github release

It would be nice if gem-release would offer an option to also create an according new github release when using the gem release command (e.g. via gem release --github).
Github offers a simple API for this purpose. You can automatically create a new Github release using a simple POST, see https://developer.github.com/v3/repos/releases/#create-a-release.

:+1:  this would be useful

Created a draft here: https://github.com/svenfuchs/gem-release/pull/73
This is untested (and I do not work with GitHub releases much).
Would anyone care to test this out?

@jekuno @johnnyshields
Rebased #73 & fixed heredoc for ruby 2.2
Feel free to test it when available

Will try it next time I'm releasing a gem. thanks

Just stumbled into this, this is great, my only other request would be to allow the github token to be retrieved from the environment somehow ..
Since I use this for publishing to the github package repository, re-using that mechanism would be great .. so perhaps support getting the token from rubygems credentials the same way the key option does .. or just use ENV['GITHUB_TOKEN'] or some such ..

@piotrb

support getting the token from rubygems credentials the same way the key option does
Can you explain a bit more about this?
Do you mean the --key option? (Use the API key from ~/.gem/credentials)

yes I do .. the --key option .. at least for github uses personal access tokens .. which is the same auth you would want to use to get a github token from ..
Like I said there should probably be 3 options .. (in order of precedence)

GITHUB_TOKEN env var
detect that the push destination is a github package host, if so, get the token from whatever --key is pointing to
take the key directly with --token

I am fine with GITHUB_TOKEN as it seems to be used by GitHub CLI too
But --key means Use the API key from ~/.gem/credentials
I think that's not where users are expected to store their GitHub access tokens
For first option we might want to support custom env var name as I found
an issue in GitHub CLI about it


Added namespace SimdJson

Hi there,
Thanks for this great project!
I added the namespace SimdJson to the library because there were some conflicts in function signatures with another library I am working with.
I am very new to the open source community and this is actually my first pull request. Therefore please bear with me if there's anything terrible in my changes.
Please kindly give me suggestions on my code and/or feel free to edit my code directly.
Thanks!
David

The build failed on the single header test. Could someone tell me what to do? Should I include a regenerated single header in my change?

Can you just revert  tests/singleheadertest.cpp ?

@ioioioio Can you review this PR given that I know we were discussing this very issue this morning?

@lcdavid94  Please don't touch the single-header file. I need to put some documentation... the intention is that they are only changed upon release.

Nice! This is something I was thinking to do since a long time.
It looks good, except for the failed build I'm not sure how to solve. I would just mention that "simdjson" is written everywhere entirely in lowercase. It also seem to be a widespread convention to name C++ namespaces entirely in lowercase.

@ioioioio Thanks for the reply!
The build fail is caused by the missing "simdjson.cpp" in "amalgamation.sh", which has been fixed by your recent change #196 I believe regenerating the single header files will fix it.
I started with "simdjson" but there is already a class with this name and thus I went with "SimdJson".
Since you asked me to remove the struct (when I am typing this comment), I will change the name.

My last commit made conflicts. I will solve all of them in an other pull request.
We'd like to add you to the contributors list. What name would you like to appear on it?

@ioioioio Thanks! "Chang Liu" will be good.

It is done. Thanks. PR#200

Thanks @ioioioio and @lcdavid94