CAMEL-12943: Rest DSL generates invalid swagger operation Id

@tdiesler , could you please to look at the PR, but RestSwaggerReaderEnableVendorExtensionTest which was failing also seem to be this issue test.

This patch seems to fix the contentID issue, but is still not working for nested context paths
09:28:45,428 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."UndertowSecureRestDslSpringIntegrationTest3.war".CamelContextActivationService."UndertowSecureRestDslSpringIntegrationTest3.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."UndertowSecureRestDslSpringIntegrationTest3.war".CamelContextActivationService."UndertowSecureRestDslSpringIntegrationTest3.war": Cannot create camel context: UndertowSecureRestDslSpringIntegrationTest3.war
	at org.wildfly.extension.camel.service.CamelContextActivationService.start(CamelContextActivationService.java:71)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.msc.service.StartException in anonymous service: Cannot start camel context: secure-rest-context2
	at org.wildfly.extension.camel.service.CamelContextActivationService.start(CamelContextActivationService.java:67)
	... 8 more
Caused by: org.apache.camel.RuntimeCamelException: java.lang.IllegalStateException: Cannot add io.undertow.server.HttpHandler for path /test defined in deployment.UndertowSecureRestDslSpringIntegrationTest3.war because that path is already served by deployment.UndertowSecureRestDslSpringIntegrationTest1.war
	at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1826)
	at org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:136)
	at org.wildfly.extension.camel.service.CamelContextActivationService$1.run(CamelContextActivationService.java:63)
	at org.wildfly.extension.camel.proxy.ProxyUtils$1.invoke(ProxyUtils.java:51)
	at com.sun.proxy.$Proxy88.run(Unknown Source)
	at org.wildfly.extension.camel.proxy.ProxyUtils.invokeProxied(ProxyUtils.java:55)
	at org.wildfly.extension.camel.service.CamelContextActivationService.start(CamelContextActivationService.java:60)
	... 8 more
Caused by: java.lang.IllegalStateException: Cannot add io.undertow.server.HttpHandler for path /test defined in deployment.UndertowSecureRestDslSpringIntegrationTest3.war because that path is already served by deployment.UndertowSecureRestDslSpringIntegrationTest1.war
	at org.wildfly.extension.camel.undertow.CamelUndertowHostService$WildFlyUndertowHost.validateEndpointContextPath(CamelUndertowHostService.java:211)
	at org.wildfly.extension.camel.undertow.CamelUndertowHostService$WildFlyUndertowHost.validateEndpointURI(CamelUndertowHostService.java:170)
	at org.apache.camel.component.undertow.UndertowComponent.registerEndpoint(UndertowComponent.java:336)
	at org.apache.camel.component.undertow.UndertowConsumer.doStart(UndertowConsumer.java:77)
	at org.wildfly.extension.camel.undertow.WildFlyUndertowComponent$WildFlyUndertowUndertowConsumer.doStart(WildFlyUndertowComponent.java:86)
	at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:72)
	at org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3709)
	at org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:4027)
	at org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3962)
	at org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3882)
	at org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3646)
	at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3489)
	at org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3248)
	at org.apache.camel.impl.DefaultCamelContext$4.call(DefaultCamelContext.java:3244)
	at org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3267)
	at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3244)
	at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:72)
	at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3160)
	at org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
	... 13 more

You can reproduce this with branch
https://github.com/wildfly-extras/wildfly-camel/tree/camel-2.23.x
mvn clean install -Dts.all -DskipTests
mvn install -Dts.all -pl itests/standalone/basic -Dtest=UndertowSecureRestDslSpringIntegrationTest

This is the last issue for 2.23.0, I hope we can fix it before next weekend :-)

Yes, @oscerd ,sure. I'm trying to fix it, but build of the wildfly-camel fails for me with "Could not resolve dependencies for project org.wildfly.camel:wildfly-camel-feature-modules:pom:8.1.0-SNAPSHOT: Could not find artifact org.kie.remote:kie-remote-client:jar:7.14.0.Final"  seems to be big re-factoring in camel-jbpm

It's not released from a while. We changed a bunch of stuff in camel-jbpm in 2.23.0. @mswiderski do you have any idea about the kie-remote-client dependecies in wildfly-camel?

kie-remote-client has been removed in v7 of jBPM. Please let me know where is wildfly-camel so I can have a look and provide fix for it

never mind just found it in the previous comments

@mswiderski , @oscerd thanks, full rebuild fixed build issue
@tdiesler I reverted all CAMEL-12908 related commits and test it again. The error stack was the same, as files secure-rest1-camel-context.xml and secure-rest3-camel-context.xml contains the separate verbs with same uri="/test". I think this need to be fixed in wildfly-camel.

What's the status of this PR in the end?

@dmvolod once you're available, feel free to merge this PR. Thanks

@oscerd, yes I will merge it tomorrow.

@ppalaga , thanks, PR merged.


correctly install systemd unit when PREFIX is changed

Fixes #621
This is how I tested:
> make PREFIX=/usr/local
mkdir bin
cp scripts/keyd-application-mapper bin/
sed -e 's#@PREFIX@#/usr/local#' keyd.service.in > keyd.service
cc -DVERSION=\"v2.4.3\ \(a11e6c7-dirty\)\" -I/usr/local/include -L/usr/local/lib -Wall -Wextra -Wno-unused -std=c11 -DSOCKET_PATH=\"/var/run/keyd.socket\" -DCONFIG_DIR=\"/etc/keyd\" -DDATA_DIR=\"/usr/local/share/keyd\" -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -Werror=format-security  -O3  src/*.c src/vkbd/uinput.c -lpthread -o bin/keyd
> cat keyd.service
[Unit]
Description=key remapping daemon
Requires=local-fs.target
After=local-fs.target

[Service]
Type=simple
ExecStart=/usr/local/bin/keyd

[Install]
WantedBy=sysinit.target
> sudo make PREFIX=/usr/local install
Place your right index finger on the fingerprint reader
mkdir -p /etc/keyd
mkdir -p /usr/local/bin/
mkdir -p /usr/local/share/keyd/
mkdir -p /usr/local/share/keyd/layouts/
mkdir -p /usr/local/share/man/man1/
mkdir -p /usr/local/share/doc/keyd/
mkdir -p /usr/local/share/doc/keyd/examples/
mkdir -p /usr/local/lib/systemd/system/
groupadd keyd
groupadd: group 'keyd' already exists
make: [Makefile:60: install] Error 9 (ignored)
install -m755 bin/* /usr/local/bin/
install -m644 docs/*.md /usr/local/share/doc/keyd/
install -m644 examples/* /usr/local/share/doc/keyd/examples/
install -m644 layouts/* /usr/local/share/keyd/layouts
install -m644 data/*.1.gz /usr/local/share/man/man1/
install -m644 data/keyd.compose /usr/local/share/keyd/
install -Dm644 keyd.service /usr/local/lib/systemd/system/
> ls /usr/local/lib/systemd/system/
keyd.service
> sudo make PREFIX=/usr/local uninstall
rm -rf /usr/local/lib/systemd/system/keyd.service \
        /usr/local/bin/keyd \
        /usr/local/bin/keyd-application-mapper \
        /usr/local/share/doc/keyd/ \
        /usr/local/share/man/man1/keyd*.gz \
        /usr/local/lib/systemd/system/keyd-usb-gadget.service \
        /usr/local/bin/keyd-usb-gadget.sh \
        /usr/local/lib/systemd/system/keyd.service
> ls /usr/local/lib/systemd/system/
>

The rest of the patch looks fine, but is there a reason you removed the systemd check?

The rest of the patch looks fine, but is there a reason you removed the systemd check?

The reason is that the directory might not exist under /usr/local but systemd will still be able to find the service file and work correctly.
Was the intention of the check to know if systemd is available at all? Then maybe it's better to check for /run/systemd/system according to this answer. What do you think?

Was the intention of the check to know if systemd is available at all?

Indeed.

Then maybe it's better to check for /run/systemd/system according to this answer. What do you think?

This looks like a good substitute, feel free to replace the original code.

This looks like a good substitute, feel free to replace the original code.

Done. Thanks for the review.

Merged :).


OSPFv2: key id

allow to change the key id
closes #941
closes #615

the double quotes are ok, because that is a parameter for a macro doing the prefix. ip ospf which is followed by the first and then the second if the second exists.


Add serval files

Added executables/ycsb_serval.cpp
Added protocols/serval/include/readwriteset.hpp
Added protocols/serval/include/serval.hpp
Added protocols/serval/include/value.hpp
Added protocols/serval/ycsb/initailizer.hpp
Added protocols/serval/ycsb/transaction.hpp
Added utils/numa.hpp

I apologize that I did a wrong pull request that I supposed to merge my develop branch into my master branch in my own forked repository. Please ignore this pull request and delete if it's possible.

No problem! Let me know if you need help.


Consider adding EntityPath and FullyQualifiedNamespace to the various processor event args

Currently, these are only available in ProcessErrorEventArgs, but it can be helpful to have it on all event args if customers are reusing the same handler for various entities.

I think the equivalent place for ProcessMessageEventArgs in Java is the ServiceBusReceivedMessageContext


Invalid Content-Type value. Allowed value(s): application/json, application/octet-stream, application/vnd.geo+json

I'm trying to follow the instructions, but I am getting an error. In the Upload geofencing GeoJSON data section - https://docs.microsoft.com/en-us/azure/azure-maps/tutorial-geofence#upload-geofencing-geojson-data, when I add the GeoJSON data to the body and POST, I get the following response.
{
"error": {
"code": "400 BadRequest",
"message": "Invalid Content-Type value. Allowed value(s): application/json, application/octet-stream, application/vnd.geo+json"
}
}
Thanks, Graham

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

ID: 95cf4eb2-2a86-582d-8160-a19cc2960c98
Version Independent ID: 12970ae9-71ca-ee5d-aadf-15678a22f883
Content: Tutorial: Create a geofence and track devices on a Microsoft Azure Map
Content Source: articles/azure-maps/tutorial-geofence.md
Service: azure-maps
GitHub Login: @stevemunk
Microsoft Alias: v-munksteve

I worked it out.
7. In the dropdown lists, select raw and JSON - I missed the 'and JSON' bit.
Thanks, Graham

glad to hear it is now working. we will now proceed to close out this issue


Correction for raw affiliation CIRAD, UPR BioWooEB, F‐34398 Montpellier, France

Correction needed for raw affiliation CIRAD, UPR BioWooEB, F‐34398 Montpellier, France
raw_affiliation_name: CIRAD, UPR BioWooEB, F‐34398 Montpellier, France
new_rors: 05kpkpg04;054ktxw16
previous_rors: 05kpkpg04
works_examples: W4393677584;W4393611462
contact: 8924826b042507bc040c63b5af0db23a:3e8784556e20843cfc9b25397a51 @ cirad.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


chore: upgrade dependencies

:tada: This PR is included in version 6.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


resetting stores

Is there a way to elegantly reset a store? I have a store thats used for one process in the app. When its finished i want to reset it to get a clean state again

Uh. Thanks for the response back then! I've meant and used the first one :)


fix: send SDK version along with fetch requests

We're using a GET request to avoid CORS preflight requests for feature flags. This requires us to send the SDK version information along in a query string instead of the custom header we use for POST requests.
Updated the header/query param name to be lower-case. For headers it doesn't matter because headers are case-insensitive, but for the query param it's simpler to just have things be lower-case.

Looks ok. I assume ingest needs to support both transport mechanisms indefinitely since old versions may never disappear

The POST requests are still using the header actually. That felt like the right way to go about it, but because of the GET we'd need to do this hack. We could of course streamline it, but the query string with the POST also felt a bit weird when there's both headers and potentially a post body for that sort of thing. Thoughts?

@roncohen

The POST requests are still using the header actually. The header felt like the right way to go about it in general

I agree. It's better to keep it as a sidecar when it doesn't negatively affect anything.
I'm interested though; If we could have the tracking requests go through without a CORS preflight, this might also help our tracking speed and consistency. It might actually be worth it. And in POST requests, despite it not being as neat to send query parameters, it's still completely valid

True. There are some differences around the fact that the GET request for flags are "idempotent" and could be cached, but we wouldn't want the tracking requests to be cached or retried. I'll file it under something to consider for the next big refactor ;)


Python wrapper for UIMA-Ruta

IRuta needs explicit browser base development to extract the linguistic features which are needed for the downstream tasks.
Does it foreseeable to have a python wrapper on UIMA Ruta, which can be directly imported to the main codebase?
Please shed light on the show breakers if it can't be implemented.

A Python interface directly to Ruta faces the same question as for accessing any other Java library from Python: what is a good Java <-> Python interface? If you know one, you can likely implement a Python wrapper.
Until then, you can use DKPro Cassis to read/write the UIMA CAS XMI files that Ruta can work on and run Ruta (or any UIMA analysis engine or even Java program) in a separate Java process which you can feed with these files.


Auto generated README showing problem title as "unknown-problem"

Bug:

Auto-generated README showing problem title as "unknown-problem"

Suggestions:

Problem title should include the problem number
Problem description should include its difficulty

Happened to me too. I think it was because of this line https://github.com/QasimWani/LeetHub/blob/main/scripts/leetcode.js#L173
But not sure why this would cause it tho

yup. i believe last PR merge might have caused this. will patch it in the next few days.

fixed. see https://github.com/QasimWani/LeetHub/tree/e293b871cfe709506696104fdded93563bc0bf01


[state-of-the-world reconciler] Topology ConfigMap

Reconciliation of the topology graph represented in DOT language stored into a read-only ConfigMap resource.

@jasonmadigan, can you please confirm if a ConfigMap is OK for storing the topology graph given the applications in sight for it?
We had discussed off-line about defining a new CRD for storing the topology graph. In the last community call, it was proposed to use a ConfigMap instead, to avoid the burden of managing yet another CRD.

@guicassolato config-map works for me, would be just as accessible


Gauging Interest in: Parallel Compute Instruction Set, Vector Processing Unit, or GPU-lite interface.

Hey all,
I was looking at some interesting things about 5th generation consoles like the n64 and PlayStation. They had special hardware built for parallel data processing, similar to a modern GPU.
Is there any interest in a series of special processing instructions? Currently, the wasm standard and runtime support 128bit SIMD, so 4x 32bit integers, or 4x f32 floats at once. Modern CPUs of today have 256bit and even 512bit operations, but that pales in comparison to the n64's gpu. We're looking at maybe 256bit over 4-8 cores (for a modest device), which is still 32 to 64 instructions "at once."
According to this source, the n64 had 32x 128bit wide Vector Processing Unit.  That's 128 f32 operations at once (4xf32 * 32 vectors). The ps1 also had a special geometry transformation engine. I can't find exact specs on this, but I assume it's similar to a vertex shader in the modern GPU pipeline, as it worked together with the actual PS1 GPU to draw pixels to the screen.
I think that this can be accomplished a few different ways:
Method (1) Exposing a few raw, simple large vector operations which can be run across multiple threads in the host machine
The lowest level. It would be similar to writing actual manual simd code like this. Could potentially have to add some additional fields for pointers to read/write variables into memory. Not very easy to do, and with the added complexities of passing larger values around between wasm & host this could be really annoying. Plus all the individual calls (load values, add values, multiply values, and pushing them in-and-out of the memory locations) might just kill any real performance benefit. Perhaps some kind of "Execution Buffer" could be written to execute many instructions and reduce the module<-->host call count.
Pros:

Safe and not easy to desync.
Real optimization work specific to the console itself.
Everything in WASM.

Cons:

Very tedious to use as a developer
Might not even be that benefecial performance wise due to the heavy increase in calls between the module and the host.
More stress on CPU, albiet lessened by pushing some work off to idle threads.

Method (2) Exposing some kind of "fork-join" API within the console, and being able to define some code to call in parallel over a dataset.
This keeps everything in WASM land, but it would also be super easy to cause a desync or worse if this isn't handled correctly. WASM doesn't support read-only memory, so it would be very easy to access memory outside of the expected region. Honestly I think this is the best choice but it passes so much responsibiliy onto the developer I'm not sure if we want to open up this risk for easy desyncing. But when done properly I could see this being a really fun and powerful thing to experiment with, and I expect an API similar to CUDA  could exist here. But it's easy to imagine how unsafe this could be...
Pros:

Everything in WASM
Simpler exposure to multithreading compared to actual threads in C or Rust

Cons:

Super easy to desync and fail silently
No way to enforce safety across parallel calls

Method (3) Exposing compute shaders, or a simplified GPU pipeline accessable and configurable from the game itself.
This is kinda the "easy way out." Would require devs to either write their own shaders, which could be typical vertex, fragment, or compute shaders. Alternatively, gamercade could provide a subset of shaders/shaders-as-functions to be called over a dataset. This method is still quite open-ended, as I'm personally not too experienced with modern graphics APIs like wgpu or vulkan.
Pros:

Potential exposure to writing shaders and actual GPU code.
Real performance increases, unlike the others which heavily abuse the CPU.
Make additional use of the GPU, which is currently only used for pixel-perfect scaling.

Cons:

GPUs today are super-duper powerful and this could easily warp the entire project if not done carefully.
The developers who can make use of this feature may as well write their own 3d game engines 😂

Method (4) Something else...
Those three methods listed above aren't completely researched and I'm sure there are ways to implement some of them to solve the larger issues. For example, there is a wasm2spirv crate which compiles WASM code into shader code, which could greatly benefit method 3. I'm personally a big fan of method 2, but the lack of safety and prevention of desyncing makes me hesitant.

Closing this in favor of upcoming 3d discussion post.


Add Finnish translation

New language
Finnish
Additional remarks
Hi, I would like to help to contribute Finnish translations. Could you add it

Finnish is added. Thanks for the help!


Add a "container friendly" log4j2 cfg and output compose dspace log to console

Description
When running dspace in docker it's more convenient to have the logging go to console. To that end this PR provides a variant of the log4j2 cfg that replaces the file with console based logging and overrides the logging config to use the variant in the root level docker compose file.
Instructions for Reviewers
# pull the images
docker-compose -f docker-compose.yml -f docker-compose-cli.yml pull

# run the containers
docker-compose -p d7 up # foreground

# or, run in background and tail logs
docker-compose -p d7 up -d
docker logs -f dspace

Confirm you're seeing the DSpace logs without having to access the container.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[ ] My PR passes Checkstyle validation based on the Code Style Guide.
[ ] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[ ] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[ ] If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
[ ] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
[ ] If my PR fixes an issue ticket, I've linked them together.

@mark-cooper : Absolutely no rush on this.  However, if you ever find time to get back to this PR, I think it'd make a great addition to DSpace.  It'd also likely be helpful for the new demo site.   That said, this is much lower priority than anything else...just wanted to mention that this (draft) PR has my interest. :)

TLDR: the merge conflict is from the recently merged #8974 and should be very straightforward to resolve. Here's what the conflict looks like:
<<<<<<< docker-compose-logcfg
      LOGGING_CONFIG: /dspace/config/log4j2-container.xml
    image: "${DOCKER_OWNER:-dspace}/dspace:${DSPACE_VER:-dspace-7_x-test}"
=======
    image: "${DOCKER_OWNER:-dspace}/dspace:${DSPACE_VER:-latest-test}"
>>>>>>> main

@tdonohue iirc at the time I was going to ask if this was wanted for DSpace before pushing it as an in-your-face- PR 😄 -- then got sidetracked in other directions and didn't get back to it. So, if you're happy to accept it then that's great!

Tested and approved, I'm merging this.


broken in v60

This should be fixed with the latest version, v60 introduced its own version of the fixes that PathfindingLagFix implemented for the Bracken and Spore Lizard.
PathfindingLagFix still includes the patch for the Snare Flea, as that remains unchanged and may still cause lag.


glam-data for 2019

@qjhart, all files for datasets and flashes for 2019 are empty.

@prakashvs613 there actually seemed to be issues wiith other years as well.  I've updsated those zip files, in that same location. https://drive.google.com/drive/folders/1SdcoDkv2X1kNDHl8Bi2OiNtn4rDbYzfC?usp=sharing

This looks good. Thanks!


fix(trait): revert persisted status

The work done in #5153 is based on the wrong assumption that a trait status can be persisted at any point of the Integration/IntegrationKit lifecycle This cannot be always true, because the resource move towards different .status.phase with the execution of its logic or not depending on the phase. Therefore we cannot persist in a consistent way, as the status would reflect the latest execution of a trait which may happen in a different phase (and would be overridden by the new execution phase). The best way to deal with this, at this stage, seems to be the usage of .status.conditions in order to warn that some trait value was overwritten.

Release Note
fix(trait): revert persisted status

The best way to deal with this, at this stage, seems to be the usage of .status.conditions in order to warn that some trait value was overwritten.

In general, I would recommend not to rely on conditions as those are primarily designed to be consumed by observers rather than the operator itself.  A golden rule of controller is that, with some very little exceptions, the status sub resource should not be used to determine the current state.

The best way to deal with this, at this stage, seems to be the usage of .status.conditions in order to warn that some trait value was overwritten.

In general, I would recommend not to rely on conditions as those are primarily designed to be consumed by observers rather than the operator itself. A golden rule of controller is that, with some very little exceptions, the status sub resource should not be used to determine the current state.

Yes. The point for the consume of conditions was more directed to a human observer that wants to understand why, for instance, an Quarkus native Integration is instructing the Kit to use 4GB of memory (which is the sensible default configuration the operator overrides).

should that be part of the kit condition/status then ?

I think it is already happening. We stores conditions of certain traits overridden properties and deprecation notices. It may be polished a little bit (see https://github.com/apache/camel-k/issues/5027) but the logic to store them is already there.

should that be part of the kit condition/status then ?

I think it is already happening. We stores conditions of certain traits overridden properties and deprecation notices. It may be polished a little bit (see #5027) but the logic to store them is already there.

so I'm a little bit confusing about what is the .status.conditions we are talking about here :)

so I'm a little bit confusing about what is the .status.conditions we are talking about here :)

NP. Let me try to summarize in shorter terms. .status.conditions already exists and it is meant to provide some info about possible info/warnings the user needs to know. Sometime ago I introduced another field, .status.traits whose goal was to store the executed traits in order to make the operator logic more consistent. However, this development was made based on the wrong assumptions provided in this PR description. The aim of this PR is to remove .status.traits which is inconsistent. Any user interested in troubleshooting an Integration can still rely on .status.conditions as it was doing previously.

so I'm a little bit confusing about what is the .status.conditions we are talking about here :)

NP. Let me try to summarize in shorter terms. .status.conditions already exists and it is meant to provide some info about possible info/warnings the user needs to know. Sometime ago I introduced another field, .status.traits whose goal was to store the executed traits in order to make the operator logic more consistent. However, this development was made based on the wrong assumptions provided in this PR description. The aim of this PR is to remove .status.traits which is inconsistent. Any user interested in troubleshooting an Integration can still rely on .status.conditions as it was doing previously.

ok then, I was a little bit confused because the .status.traits has been the center of a number of things recently, like checksum, copy to kit, etc so I missed a little bit the context.
sorry for the noise

ok then, I was a little bit confused because the .status.traits has been the center of a number of things recently, like checksum, copy to kit, etc so I missed a little bit the context.
sorry for the noise

Probably I was the one making noise with wrong development ;) - Fixing all those wrong stuff though.

--- PASS: TestNativeHighMemoryIntegrations (1834.10s)
    --- PASS: TestNativeHighMemoryIntegrations/java_native_support (875.74s)
        --- PASS: TestNativeHighMemoryIntegrations/java_native_support/java_native_same_should_not_rebuild (2.21s)
        --- PASS: TestNativeHighMemoryIntegrations/java_native_support/java_native_should_rebuild (428.39s)
    --- PASS: TestNativeHighMemoryIntegrations/groovy_native_support (495.43s)
    --- PASS: TestNativeHighMemoryIntegrations/kotlin_native_support (451.77s)
PASS
ok  	github.com/apache/camel-k/v2/e2e/native	1834.133s
--- PASS: TestNativeIntegrations (884.52s)
    --- PASS: TestNativeIntegrations/unsupported_integration_source_language (0.76s)
    --- PASS: TestNativeIntegrations/xml_native_support (412.21s)
    --- PASS: TestNativeIntegrations/automatic_rollout_deployment_from_jvm_to_native_kit (462.53s)
        --- PASS: TestNativeIntegrations/automatic_rollout_deployment_from_jvm_to_native_kit/yaml_native_should_not_rebuild (2.70s)
PASS
ok  	github.com/apache/camel-k/v2/e2e/native	1330.983s


fix compiling with latest serenity

nevermind something was messed up my end and I don't know how or why


Allow theme overrides

This addresses
https://github.com/eddyekofo94/gruvbox-flat.nvim/issues/12.
I've tested this locally.

Well, I just hope this pr works fine I gave it a quick look so I trust your code 👀.
wish we can add some rest cases to the project. If anyone kind enough to start it I’ll appreciate it


Update test command

Hi guys
When running the test suite today bundle exec rails spec didn't work for me (as advised in the Readme), but bundle exec rspec did. Should the Readme file be updated to this? If not, that's totally fine, I would just really appreciate an explanation for my own learning journey.
Thank you so much 😃

Updated! Thanks for noticing that, it was an artifact from when we were on an older version!


python3Packages.scramp: 1.4.0 -> 1.4.1, python3Packages.pg8000: 1.21.0 -> 1.21.1

Motivation for this change
Update to latest upstream release 1.4.1 and 1.21.1
Change log: https://github.com/tlocke/scramp#version-141-2021-08-25
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

6 packages built:

python38Packages.pg8000
python38Packages.scramp
python38Packages.testing-postgresql
python39Packages.pg8000
python39Packages.scramp
python39Packages.testing-postgresql

Result of nixpkgs-review pr 136206 at 008b192d run on aarch64-linux 1

6 packages built successfully:

python38Packages.pg8000
python38Packages.scramp
python38Packages.testing-postgresql
python39Packages.pg8000
python39Packages.scramp
python39Packages.testing-postgresql


[v1.7] Use PME adjustResultData format for Gradle

All Submissions:

[ ] Have you added a note in the CHANGELOG wiki for your change?
[ ] Have you added unit tests for your change?

@thescouser89 LGTM!! Thanks!

Will test on 1.7, if all good will backport to master!


Manage pipeline requests in a queue

As a HKube Manager I want that Hkube will manage pipeline requests in a queue, so that requests won't be lost in case there isn't available HW resources.

TID-51 in betta1 version doc

pipeline queue
File: tid_51.js
describe : "tid_51 run pipelines in a queue~ (git 54)"

Test
description

should run the eval batch pipeline
execute  pipeline and validate result

should run the primes pipeline
execute  pipeline and validate result


Allow user to select version of Scalajs-react's VDOM and Scalatags

Since some of us are still using older versions of Scalajs-react in production having an option to select the version of Scalajs-react or Scalatags would be nice.

Not needed.


Revert OSA SHA to known working version

A recent change [1] in OSA broke multi-node builds. There is a
fix proposed, but the gate times are really long, so it may not
merge in time for the next RPC-O release. Rather than delay our
release, we revert to a known good SHA.
[1] https://github.com/openstack/openstack-ansible/commit/6745b3727f70d609895e18ce15caa367e481265b
[2] https://review.openstack.org/605504
JIRA: RI-484
Issue: RI-484

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.


BlockHandler block entity tags don't get sent to client on place

When I place down a block with a custom sign block handler and give it the required tags while a player is in range of the location the sign is empty until they rejoin. Since I hadn't noticed this behaviour when writing #664 the discussion is now obsolete as my general code works after I rejoin.

Could you provide code to reproduce?


Console healthcheck fails when attached to Postgres versions >14 on RDS

Summary
https://jitsuhq.slack.com/archives/C018G6W0URG/p1726784323537209
Running Jitsu on AWS ECS attached to Postgres on RDS. When using a version >14, the console healthcheck fails on this line.
Confirmed that both PG instances use the same username and password and both are accessible via public internet.
Note that v14 of Postgres on RDS does not experience this issue. I also could not replicate using postgres:16 on my local Docker.
System configuration and versions
Using latest version of all Jitsu images.
Artifacts (logs, etc)
console log using PG 16 on RDS:
2024-09-20 06:40:51 FORCE_UPDATE_DB is set, updating database schema...
2024-09-20 06:40:52 Prisma schema loaded from schema.prisma
2024-09-20 06:40:52 Datasource "db": PostgreSQL database "postgres", schema "newjitsu" at "jitsu-staging-pg16.xxxxxx.us-east-1.rds.amazonaws.com:5432"
2024-09-20 06:40:56
2024-09-20 06:40:56 The database is already in sync with the Prisma schema.
2024-09-20 06:40:56
2024-09-20 06:40:56 Starting the app
2024-09-20 06:40:56 Waiting for localhost:3000 to be up...
2024-09-20 06:40:57 Running healthcheck...
2024-09-20 06:40:59 ❌ ❌ ❌ HEALTHCHECK FAILED - 503 from http://localhost:3000/api/healthcheck. Response:
2024-09-20 06:40:59 {"status":"error","prisma":{"status":"ok","ms":1585},"postgres":{"status":"error"}}
2024-09-20 06:40:59 Killing console with pid 58
2024-09-20 06:40:59 Killed

console log using PG 14 on RDS:
2024-09-20 06:38:48 FORCE_UPDATE_DB is set, updating database schema...
2024-09-20 06:38:50 Prisma schema loaded from schema.prisma
2024-09-20 06:38:50 Datasource "db": PostgreSQL database "postgres", schema "newjitsu" at "jitsu-staging-pg14.xxxxxx.us-east-1.rds.amazonaws.com:5432"
2024-09-20 06:38:53
2024-09-20 06:38:53 The database is already in sync with the Prisma schema.
2024-09-20 06:38:54
2024-09-20 06:38:54 Starting the app
2024-09-20 06:38:54 Waiting for localhost:3000 to be up...
2024-09-20 06:38:55 Running healthcheck...
2024-09-20 06:38:56 ⚡⚡⚡ HEALTHCHECK PASSED - 200 from http://localhost:3000/api/healthcheck. Details:
2024-09-20 06:38:56 {"status":"ok","prisma":{"status":"ok","ms":1150},"postgres":{"status":"ok","ms":363}}
2024-09-20 06:38:56 Initializing console...
2024-09-20 06:38:57 {"success":true}

@johnpitchko could you please try with jitsucom/console:2.8.2 image? it has logging fixed, so underlying error must become visible.

Thanks for the extra debugging. Using that version of the image, here is the detailed error:
2024-09-21 00:20:34 FORCE_UPDATE_DB is set, updating database schema...
2024-09-21 00:20:35 Prisma schema loaded from schema.prisma
2024-09-21 00:20:35 Datasource "db": PostgreSQL database "postgres", schema "newjitsu" at "xxxxxx.us-east-1.rds.amazonaws.com:5432"
2024-09-21 00:20:39
2024-09-21 00:20:39 The database is already in sync with the Prisma schema.
2024-09-21 00:20:39
2024-09-21 00:20:39 Starting the app
2024-09-21 00:20:39 Waiting for localhost:3000 to be up...
2024-09-21 00:20:39   ▲ Next.js 14.2.5
2024-09-21 00:20:39   - Local:        http://[::1]:3000
2024-09-21 00:20:39   - Network:      http://[::]:3000
2024-09-21 00:20:39
2024-09-21 00:20:39  ✓ Starting...
2024-09-21 00:20:40  ✓ Ready in 433ms
2024-09-21 00:20:40 Running healthcheck...
2024-09-21 00:20:40 2024-09-21 06:20:40.343Z INFO  [db]: Initializing prisma
2024-09-21 00:20:40 2024-09-21 06:20:40.352Z INFO  [singleton]: ⚡⚡⚡ prisma connected in 9ms!
2024-09-21 00:20:40 2024-09-21 06:20:40.354Z INFO  [singleton]: ⚡⚡⚡ pg connected in 1ms!
2024-09-21 00:20:40 prisma:info Starting a postgresql pool with 17 connections.
2024-09-21 00:20:41 2024-09-21 06:20:41.655Z ERROR [healthcheck]: Service postgres failed to initialize error: no pg_hba.conf entry for host "70.77.xxx.xxx", user "postgres", database "postgres", no encryption

I then appended sslmode=no-verify to the DATABASE_URL (postgresql://postgres:${POSTGRES_PASSWORD}@${POSTGRES_HOSTNAME}:5432/postgres?schema=newjitsu&sslmode=no-verify) and was able to connect successfully:
2024-09-21 00:23:35 FORCE_UPDATE_DB is set, updating database schema...
2024-09-21 00:23:36 Prisma schema loaded from schema.prisma
2024-09-21 00:23:36 Datasource "db": PostgreSQL database "postgres", schema "newjitsu" at "xxxxxxx.us-east-1.rds.amazonaws.com:5432"
2024-09-21 00:23:40
2024-09-21 00:23:40 The database is already in sync with the Prisma schema.
2024-09-21 00:23:40
2024-09-21 00:23:40 Starting the app
2024-09-21 00:23:40 Waiting for localhost:3000 to be up...
2024-09-21 00:23:40   ▲ Next.js 14.2.5
2024-09-21 00:23:40   - Local:        http://[::1]:3000
2024-09-21 00:23:40   - Network:      http://[::]:3000
2024-09-21 00:23:40
2024-09-21 00:23:40  ✓ Starting...
2024-09-21 00:23:41  ✓ Ready in 439ms
2024-09-21 00:23:41 Running healthcheck...
2024-09-21 00:23:41 2024-09-21 06:23:41.466Z INFO  [db]: Initializing prisma
2024-09-21 00:23:41 2024-09-21 06:23:41.475Z INFO  [singleton]: ⚡⚡⚡ prisma connected in 9ms!
2024-09-21 00:23:41 2024-09-21 06:23:41.477Z INFO  [singleton]: ⚡⚡⚡ pg connected in 2ms!
2024-09-21 00:23:41 prisma:info Starting a postgresql pool with 17 connections.
2024-09-21 00:23:43 2024-09-21 06:23:43.188Z INFO  [db]: Connecting new client postgresql://postgres:xxxxxxx@xxxxx.us-east-1.rds.amazonaws.com:5432/postgres?schema=newjitsu&sslmode=no-verify. Pool stat: idle=0, waiting=0, total=2. Default schema: newjitsu
2024-09-21 00:23:43 2024-09-21 06:23:43.602Z INFO  [db]: Connecting new client postgresql://postgres:xxxxxx@xxxxxx.us-east-1.rds.amazonaws.com:5432/postgres?schema=newjitsu&sslmode=no-verify. Pool stat: idle=1, waiting=0, total=2. Default schema: newjitsu
2024-09-21 00:23:43 ⚡⚡⚡ HEALTHCHECK PASSED - 200 from http://localhost:3000/api/healthcheck. Details:
2024-09-21 00:23:43 {"status":"ok","prisma":{"status":"ok","ms":1625},"postgres":{"status":"ok","ms":550}}
2024-09-21 00:23:43 Initializing console...
2024-09-21 00:23:43 2024-09-21 06:23:43.823Z INFO  [auth]: Using autogenerated JWT key e1c5ad0fe65af646fdbbc30d869993aa3aab6c7824c78be89d59abcd87681f9f
2024-09-21 00:23:43 2024-09-21 06:23:43.832Z INFO  [singleton]: ⚡⚡⚡ firebase-service connected in 0ms!
2024-09-21 00:23:43 2024-09-21 06:23:43.854Z INFO  [events-log-init]: Init events log
2024-09-21 00:23:43 2024-09-21 06:23:43.871Z INFO  [events-log-init]: Database newjitsu_metrics created or already exists
2024-09-21 00:23:43 2024-09-21 06:23:43.882Z INFO  [events-log-init]: Table newjitsu_metrics.events_log created or already exists
2024-09-21 00:23:43 {"success":true}
2024-09-21 00:23:43 Starting cron...

RDS has force_ssl set to true since version 15 by default. That is why sslmode=no-verify helps here.

Yes that makes sense. I can open a PR to update the documentation and maybe add a comment in the template to explain this so future RDS users do not run into trouble. Thoughts?


Support lyrics without timestamps?

Description
Hi, currently the lyrics works fine if it is given in the correct timestamped format. But crashes(no lyrics available) when the timestamps are removed.
Is there a way to automatically show something else like a Modal/portal that displays the full lyrics text if there are no timestamps available? (getting timestamped lyrics is hard right..? any good resource you know for the same :)? )

You can use extendsContent customize your lyric, get current playing audio lyric by onAudioPlayTrackChange or onAudioPlay
const showLyricModal = () => {
  const currentPlayAudioInfo = ...
  Modal.open({ content: currentPlayAudioInfo.lyric })
}
<ReactJkMusicPlayer showLyric={false} extendsContent={<button onClick={showLyricModal}>show lyric</button>} />;

Thanks for the suggestion @lijinke666 , but if I get it right, this would make the experience of timestamped lyrics different from lyrics without timestamps... I think what @aldrinjenson is asking for is a way to have a more consistent experience for the user.


Manually add a specific python interpreter permanently

I've installed this extension and it automatically located my virtual environments. But unfortunately, the BASE environment of my Anaconda3 is not automatically located at all. I suffered a lot attempting to just manually add the base environment to those existing environments.
Eventually, I've found that it seems that this extension can only locate environments and add them to the existing python interpreter list AUTOMATICALLY, while the only way of adding new environments is by configuring settings such as the Venv folders settings, which may search in the first-level subfolders of the items. But it is well known that the base interpreter is located in the main folder of anaconda3, not the envs file.
Actually I can avoid this only by creating an environment which has the same packages as the base environment, but I still want to figure out how to MANUALLY add an interpreter PERMENANTLY, maybe it is somewhere but I just cannot find it. If someone knows, please remind me and I'll be more than appreciating. If the solution just doesn't exist, I strongly suggest that you can add an option to manually add an interpreter as pyCharm does.

@ChristLBUPT Could you elaborate why python.venvFolders setting does not work for you? You can add the relative path to your Anaconda folder to detect the "base" anaconda environment.
Alternatively, once you manually select an interpreter that's not already in the list, it gets added to the list permanently.

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


Environment Camera 90 degrees off

Sorry for opening another issue, but when i get a stream from the environment camera on iphones, the image is 90 degrees rotated. I could add an extra operation after drawing to a canvas to rotate the image 90 degrees if it's an iphone, and that may be the way i'll have to do it, but it just seems sort of an ad hoc solution.
I might be doing something wrong, but heres some code, which works on all webrtc enabled browsers correctly, but gives me a 90 degree rotated image on iphones:
width and height are 640x480, and i've tried reversing them, but still getting a 90 degree rotated image
getting the stream:

				var constraints = {
					"audio": false,
					"video": {
					  facingMode: "environment"
					}
				};
				navigator.mediaDevices.getUserMedia(constraints)
				.then(function(stream) {
					window.stream = stream; // make stream available to console
					 if (window.URL) {
						cameraVideo.src = window.URL.createObjectURL(stream);
					} else {
						cameraVideo.src = stream;
					}
					cameraVideo.play();
				})
				.catch(function(error) {
					console.log('navigator.getUserMedia error: ', error);
				});

drawing to a canvas:
				`videoCanvasContext.drawImage(cameraVideo, 0, 0);`

i originally had:
				`videoCanvasContext.drawImage(cameraVideo, 0, 0, WIDTH, HEIGHT);`

for drawing to the canvas, but this would not actually draw the image, and found out that the image i'm getting from the camera is smaller than what i had width and height set to (now set to 640x480 which covers the entire canvas)
Just in case this is not an actual issue, and i'm just doing something wrong, is there a discussion somewhere i could post a topic on about bowser where i might get some help?

This is a little silly, but i can't say this is actually an issue now because the camera is just not rotating when i rotate the device. when i go to landscape mode, it's displaying properly


Presentation -- show content in (()) and {{}} as in Roam read mode

That's especially important for ((block reference)) and {{[[TODO]]}}.

I think block reference is already supported?


list() does not consider offset number

Thanks yathit for this great library. Can you please help with the below issue?
As per documentation @ https://dev.yathit.com/api/ydn/db/query.html  the list method limits the number of results in a query to n, and if the query is run again would return the next n, then next n and so on.
But this is not working, each time I run a query using list, it returns the first n results. Is there a workaround for this? Can we pass an offset to the list method so that will return n results after ignoring the first m?

Can you show a runnable code that is  not working?
I tried in getting started page instruction and working correctly.


does it support webpack2?

does it support webpack2?

I just installed it on a project. It works well on webpack2.
You just need to install font-awesome first:
npm install font-awesome

@KiGniark  no, it does not work with webpack 2: https://github.com/gowravshekar/font-awesome-webpack/issues/33


Update README.md

Make it obvious that react_component is a view helper.
View helper types

Thanks! Really appreciated!


Unpickle "set" support

Set is a popular data structure used in python and quite often it is pickled/unpickled when storing state.
The pickle spec does not specifically address sets, but provides a way of serializing them as a class (which is currently not supported by stalecucmber).
I have a pull request coming up to specifically address sets. Far from a generalized solution to class serialization, but quite useful IMHO!

Merged


Lazy-loading & SEO for hidden carousel elements

Hi folks! Thanks for maintaining this port!
So, I am using this in a server rendered context to show a list of clickable cards. Now with Lazy loading, it doesn't create those components on initialization which would affect SEO for the page since those card links aren't discoverable.
Is there any way to have SEO not suffer in such a case? If not, would you consider adding a placeholder prop which renders a placeholder component for lazy loading cases?
If we do that, I imagine line 113 below would need to change to instead render the placeholder component:
https://github.com/akiran/react-slick/blob/48c93ed36cfb58991e6bf4d34a1a588094281d12/src/track.js#L106-L114

Another option if this should be solved in the userland is to provide a renderChild method for the children items that is called with a flag like isVisible. In that case, the placeholder logic can be shifted to the user.
Thoughts @akiran @laveesingh @maddhruv?

@lucashfreitas Providing a placeholder content rendered by the server while the original content is progressively loading is a good example.  That is why @oyeanuj suggested adding a placeholder prop as a feature. Setting lazyload property as a false also prevents progressive loading.  Rendering small-sized placeholder content by the server for SEO purposes also loading original big-sized content progressively... or similar solution that we expected.

@oyeanuj @oyilmaztekin  I am facing the same issue. Googlebot does not crawl the lazyloaded items. Can anyone help me here?

I'm facing the same issue too. The behavior changed in the version 0.27.1: https://github.com/akiran/react-slick/commit/8ae0e38218da99ac87b3322306ca693a17c5a9f2
Behavior before version 0.27.1: Initial slide was rendered even with lazy loading enabled in server-side rendering.
Behavior in version 0.27.1 and forward: No slide is rendered with lazy loading enabled in server-side rendering.


question please (insert parsed data to a DB)

Hi,
I am new here, I did some java work, we are looking to have a script to read huge comma separated file then insert it in a database, one of my coworkers talked about using python, I found your node.js project called node-byline
please tell me if this code should work better than python ?
how to insert what was parsed to a database ?
thanks lot.

Sorry, I can't really help you here. Byline can only read lines from a text file, if you're wanting to parse CSV then you'll need to look on npm.


Upgrade qs dependency

Previously required version contained a security vulnerability. See #59 and https://snyk.io/vuln/npm:qs:20170213

Same tests fail with or without this patch...so there's that...
Also, the devDependencies are rather old also, and npm audit reports 53 vulnerabilities with or without that patch (as the devDependencies also include the old qs among other old libraries):
[!] 53 vulnerabilities found - Packages audited: 173 (172 dev, 23 optional)
    Severity: 9 Low | 25 Moderate | 19 High

https://david-dm.org/flatiron/union?type=dev

I definitely noticed that with npm audit, and I was thinking of throwing in some other PRs upgrading them.
Speaking of tests, on the other hand, the union/header test hangs for me, are you getting the same?

Speaking of tests, on the other hand, the union/header test hangs for me, are you getting the same?

I did see that when running in bash (on Windows via mingw), but that (and the others) completed fine (though some failed) when running in cmd (also, obviously, on Windows 😄).

Yeah it hangs for me on zsh on Linux. Sounds like it's own issue, and like magic it's now #63

@hiddensanctum looks like this is blocked on https://github.com/flatiron/union/issues/63

@thornjad thanks, I've sent him a kindly worded email. Let's see if that helps make some progress 😃

@BigBlueHat made you an admin of this to support the work you do in http-server. From an http-server perspective union is an out-dated architecture that should be killed in favor of other HTTP libraries.


LFS-369: Notes don't show up in quick searches

Draft PR until #171 is merged
Jira link
Review link of just this PR
Test branch: LFS-369-test
To test: From the homepage, create a Demographics form. The Family question has comments enabled, which can be added to. These notes should now be searchable from the quick search bar.
Additional notes: This includes a minor refactor of QueryBuilder.java, to avoid the cyclomatic complexity and executable statement count checkstyle errors.

VM with the latest commit can be found here http://<IP_ADDRESS>:8080/

Apologies, but I just refactored the backend and will need a retest. The return results are much more semantic (from a code standpoint). There's also a bugfix related to the quick search results sometimes having duplicated entries if the same node has multiple matches in different questions.


Add license file and include in sdist packages

Resolves #74 .

Coverage remained the same at 95.33% when pulling 8ac5c4625911e066dc5d5f6f0d647e55dce9cb97 on toddrme2178:master into 7e50c21ba3706de48a1a0d6ba3574ab914253f7f on Blosc:master.

Looks good, thank you very much!

@toddrme2178 I released a new version to PyPi today, please let me know if you need anything else for the OpenSuse packages.


Morning session: Peer-to-peer code review

Your project looks good, I would advise you to not leave unnecessary comments in you code.
Also check the resizing behaviour on the browser, because there seems to be a bug on the top hero session.

Hi Reem :wave:;

I really liked the documentation in your Readme file and the way you organize your styles, congratulations!


Revert prev changes and added name

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

This is PR is empty, closing it. Feel free to open with the changes


Ability to Prevent Swipe Right Gesture for Going Back

Relevant for when using the ex-navigator for showing Modals.
related: https://github.com/facebook/react-native/issues/3759

This works:
        configureScene() {
          return {...ExNavigator.SceneConfigs.FloatFromBottom, gestures: null}
        },


Add profile::base to all roles

This commit simply adds 'include profile::base' to all of the roles we've defined so far.

Knocked it out of role::all_in_one_pe.

Looks good to me :+1:


chore: Stop using node-pty in Electron renderer process

This PR includes a bump to Electron 11.
Fixes #7456
Closes #7496
Closes #7458

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[ ] 🐛 Bug fix
[x] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


changing colours in the ts variant

What problem does this feature solve?
how can we change the primary colours of the template? including the button hover colours? managed to change the primary button colour but not sure if it's the correct way. button hovering still shows the same default color
What does the proposed solution look like?
N/A

I think you could change the color yourself in<EMAIL_ADDRESS>

Hi @farhanangullia,
You can change the primary color in the<EMAIL_ADDRESS>file as mentioned by @redianmf.
We've rolled out a new version that includes the Next.js v14 App Router. Feel free to dive in and check it out.
Also, in this latest release, we've made it easier to customize colors through user overridable files. This way, you won't need to modify anything in our core folders.
I'm going to close this issue, but don't hesitate to open a new issue if you encounter any problems.


Window lock shortcut key not working

robot.keyTap('delete', ['control','alt']);
OR
robot.keyTap("l",["command"]);
not working.
I am trying to lock my windows 10 via robotjs code but not working please find above code.
Please help me out from this issue

Here's a workaround to lock a window screen (Windows):
robot.keyTap("d", ["command"]);
robot.keyTap("r", ["command"]);
robot.typeString("cmd");
robot.setKeyboardDelay(500);
robot.keyTap("enter");
robot.typeStringDelayed("rundll32.exe user32.dll, LockWorkStation", 0.03);
robot.keyTap("enter");
process.exit(-1);
On every tap and mouse click, time matters, have a look at it

Seems that this is some sort of restriction on the way Win + L is interpreted.
More info can be found here : StackOverFlowLink

This issue has been closed because it has been inactive for > 180 days.
You may reopen this issue if it has been closed in error.


Selective monochrome mode while in DHGR

Hi, I noticed that when using RGB output on my Enhancer IIe, Dazzle draw seems to use some kind of selective monochrome mode on both the splash screen and while using the program. I'm not positive how this is working, but it's a nice effect that really cleans up the text. Could this be replicated in the the firmware for the A2DVI? Seems like this may be some long-forgotten feature of RGB cards that could be used today to make modern programs look better when used with cards like A2DVI.
Examples:

Thanks

I have a suspicion how that could have worked. Basically the only way I could think of: switching video modes and settings back and forth in between lines, or even in between pixels of a line.
I know things like this were used on the IIgs (also on the C64). Both provide scanline synchronous interrupts. So it's just a matter of counting scanline interrupts and then delaying a bit more to wait for the correct position within each line to apply changes to the video registers at the correct time.
The IIe does not have scanline interrupts. Just a register to poll the vertical retrace state. So synchronizing setting changes with individual lines, or even specific pixel areas within a line, is hard (basically requires to lock up the CPU doing nothing else but counting clock cycles, to do the proper pixel timing).
I know there are some modern demos for the IIe using the technique, switching between text and graphics modes, for example, in between pixels of each scan line, to show a little text frame surrounded by graphics.
If Dazzle Draw was indeed switching video modes in between lines/pixels, than that would be the first "real world application" from back in the day I know of.
But I'll need to have a look what it is actually doing. And if my suspicion is even right...

I was thinking about this too -- but I can't imagine this is what it is doing? It seems to work flawlessly and without any glitching -- and counting cycles on a 1985 program sounds like a bit much? Especially as it would be doing it mid scan line, as when you drop down a menu over the color image, the menu is in monochrome while the stuff to the left and right is perfectly in color.
Do you want me to image this disk of Dazzle Draw I have that is doing this? It seems I have another copy of it that doesn't have this effect. What is funny is the Video 7 enhancer isn't really compatible with the older Video 7 extra modes at all, like the text foreground/background color. The only thing I've seen it do is full screen monochrome like with Apple ][ Desktop, so I was frankly shocked when I saw it doing this selective monochrome mode in Dazzle Draw!
Perhaps it is using that extra 8th bit in video memory to somehow do this?  The bit normally used for orange/blue in HGR? I'm not a software developer so I don't have a great handle on how DHGR works. Let me test this selective thing on the Apple/Video 7 RGB card (as I was testing at that point on the Enhancer IIe.)

Ok yes, just tested on the Apple 80col RGB card (Video 7 design) and the selective monochrome works on it as well. So it's not just the enhancer IIe (and the Enhancer IIc) that supports it.
Now I didn't mention but when looking at the screens in Dazzle Draw via the A2DVI, all just looks normal with extremely fringed text, etc. The only thing I think that makes sense to me is the 8th bit (bit 7) used in HGR to select the shifted colors that is being used here to denote monochrome mode. I think normally otherwise that bit is simply ignored by the video hardware while in DHGR mode?
I just checked the version of Dazzle Draw that does not do the selective monochrome, and it's dated 1984 in the About Dazzle Draw box. On the screenshots above, it's the 1985 one that does it -- so I guess something that Broderbund fixed in a newer version specifically to better support RGB output devices? My Apple IIe RGB card is dated 1985 and so is the Enhancer IIe RGB board.

Comparing the two version of Dazzle Draw over RGB (Apple IIe Extended RGB card)

You are probably right - your last pictures gives it away. It has to be something in the data itself. Indeed, bit 7 of each screen data byte is unused in DHGR. That is very likely what they used to switch between color and monochrome - on a per byte (7 monochrome pixels) basis.
That's a feature I wasn't aware of. Neither is is implemented by any of the other analog VGA cards. But if it's just a matter of "checking bit 7", that's probably something that could be added to the rendering code - so A2DVI could also emulate this advanced behavior.
Can you pack and attach the disk which has that feature? Or do you know which of the asimov DazzleDraw versions does this - so I don't start investigating with the wrong disk image:
https://mirrors.apple2.org.za/ftp.apple.asimov.net/images/productivity/graphics/dazzle_draw/
I can verify pretty quickly if they are indeed messing with bit 7.
(That's one of the cool things about these PICO based expansion cards. The PICO sees every bus cycle, every address and data byte that the 6502 handles. It's fairly easy to add logging or other debugging code on the PICO. So monitoring or logging things which would normally be only possible in a software emulator, are suddenly also possible while working with the real hardware...)

OK I tried a few from Asimov and yeah one of these is the old version that does not do the selective monochrome. I've attached the two relevant versions.
Dazzle Draw (Brutus Crack).DSK - Doesn't run
dazzle_draw.dsk - Does NOT do selective monochrome (so must be old version aka Control)
Dazzle Draw v1.2 (Broderbund-1988).dsk - This DOES selective monochrome
dazzledraw1.dsk - Also does selective monochrome, same version as the 1.2 above.
dazzledraw2.dsk - Is the slideshow disk
Dazzle Draw 1.2.dsk - Also does the selective monochrome, same version as the one above.
dazzle_draw.zip

And yes so cool about being able to debug this quickly and easily!

More DHGR selective monochrome in use on the Apple Color RGB demo disk even:

AppleII80columnRGBColorCard-DOS.zip

Well, we are getting there...

And I stand corrected concerning "neither implemented by the analog VGA cards". Turns out, the "Double-HIRES with Monochrome pixels" video mode is one of the "Video 7" video modes, which had already been implemented by David Kuder for his "analog VGA" card. Props to him. My A2DVI firmware inherits its basic video rendering logic from David's project. I have now also ported the missing Video 7 video modes for A2DVI. Indeed, Dazzle Draw does look better with this.
Looks promising, but might still have rendering issues. It's getting late over here. I'll have some more time this weekend to look at these modes in more details.
If you want to have a go with testing the current build - I have attached the latest firmware build:
A2DVI_v1.3A1.zip

Awesome, I'm literally in the middle of making a video about the A2DVI card, so I'll be leading this test firmware on specifically for the video. And I'm not surprised David Kuder implemented it on the VGA card! Side note, I connected up my VGA only LCD via a $3 HDMI-VGA adapter and that worked flawlessly. Now if only I could find David's card -- I think I left it in one of my Apple II machines I'm not sure which.

NICE! Ok I gave it some tests it's like 90% there. The HGR 16 color mode seems to work perfectly, and then the selective monochrome seems to work for the most part. The bar graph display from the Apple RGB demo disk has some color fringing here and there but it's nearly there. I assume David Kuder's code is probably just like that too -- so maybe some tweaks are needed to both?

Ok example of how it looks on the 1.3A1 firmware:

Noticed the fringed text which isn't seen on the RGB card.

OK ran into another issue, if you boot the Apple II RGB card demo, and pick slide show. This HGR 16 color image will be displayed, which is somehow stretched and messed up via the A2DVI but works fine on the real RGB card. The other 16 color HGR images work fine though.
Video 7 RGB Card:

FW1.3A1:

Three quick fixes: firmware 1.3A2:
A2DVI_v1.3A2.zip
The color fringes of monochrome pixels in the advanced V7 mode are gone:

Also the "strech" issue with the 160x192 Video-7 mode is fixed:

Simply amazing!! Software defined hardware FOR THE WIN!!!

Indeed. And until not too long ago, HDMI signal generation would have been an application very clearly only possible with FPGAs (or ASICs). That this can now be easily "bit banged" in software, using a tiny, super cheap microcontroller (worth just a few cents on digikey), is simply mind boggling. And the controller isn't even running at its limit yet...

Yes! This is what I am marvelling at in the video! How on earth are we doing this with something so cheap!?! Next up really is a version of the card design with the RP2040 right on the PCB so nor more Pi Pico carrier required, bringing the cost down even further. Anyway, I'll close this issue since you totally fixed everything!


Add flexible configuration options to CMake for building/reusing tools

Relates to (and may resolve) https://github.com/google/iree/issues/4617
We have a few components like iree_check_test that require some tools to exist, but they don't necessarily need to (or can't, depending on the build configuration) build those tools themselves.
We currently use -DIREE_HOST_BINARY_ROOT=$PWD/../build-host/install and CMAKE_CROSSCOMPILING together with iree_get_executable_path as the main way to control what gets build or reused where:
https://github.com/google/iree/blob/8d74bfa28dd35203fba700aa1f1d88c200c848cd/build_tools/cmake/iree_macros.cmake#L115-L126
separately, we can make that produce more helpful error messages if tools are missing
However, this misses a few cases such as

host runtime-only builds reusing the tools from a binary distribution
Android builds excluding certain types of tests

Something like IREE_USE_INSTALLED_HOST_TOOLS was suggested on https://github.com/google/iree/pull/4627

I ran into this when trying to create a job that builds the IREE benchmarks (essentially import and compile some TFLite models). Currently they're built as part of the android build, which really doesn't make any sense and is not something I want to duplicate in the migration to GitHub actions. It appears that there's no way to build them using prebuilt host tools. You have to do a full host build.

I ran into this when trying to create a job that builds the IREE benchmarks (essentially import and compile some TFLite models). Currently they're built as part of the android build, which really doesn't make any sense and is not something I want to duplicate in the migration to GitHub actions. It appears that there's no way to build them using prebuilt host tools. You have to do a full host build.

Can you elaborate which tools exactly where causing trouble and required a full host build?

I think the change in https://github.com/iree-org/iree/commit/51893996b28d672e6ea56e6c4da7c86d8785059a was enough to enable this. I also audited our usage of CMAKE_CROSSCOMPILING and what we have today looks good (no unnecessary restrictions).
function(iree_get_executable_path OUTPUT_PATH_VAR EXECUTABLE)
-  if (NOT CMAKE_CROSSCOMPILING OR TARGET "${EXECUTABLE}")
+  if (NOT DEFINED IREE_HOST_BINARY_ROOT OR TARGET "${EXECUTABLE}")

we might want to rename or better document IREE_HOST_BINARY_ROOT to better convey "I want to use binary files / tools from this directory instead of building them from CMake targets" though.
I'll see if I can tweak https://github.com/iree-org/iree/blob/d9e6eb76a7c3818672fabe92e3993286b743a49f/.github/workflows/ci.yml#L513-L518 and https://github.com/iree-org/iree/blob/main/build_tools/cmake/build_benchmarks.sh to use that

I've also noticed that IREE_HOST_BINARY_ROOT actually has to point one directory above the root where IREE binaries are. It points to a directory containing a directory called "bin" that has the binaries. Basically it's an IREE install directory. I think we should probably name it based on that. Maybe IREE_TOOLS_INSTALL?


Issue-#257-Added Hover Effects for the cards

Fixes #257
Description
I had made the changes in the CSS files for adding hover effects which makes the website appealing. I had read the contributing guidelines and made the PR in the same way as suggested.
Thanks.

Fixes #257
Description
I had made the changes in the CSS files for adding hover effects which makes the website appealing. I had read the contributing guidelines and made the PR in the same way as suggested.
Thanks.

Please follow contributing guide and follow the specific type of commit messages that we use.

Had changed the commit issue name as per the contributing guidelines.
Thanks

@iampranavdhar can you please attach a screenshot?

Yeah, Sure @gauravdas014
Normal:

On Hover:

Actually its a hoer effect it looks better when we see a video or experience it directly but as suggested I am posting the screenshots
Thanks.


Unclear reference on API Management article

I got lost on the sentence that says "Browse to your API Management instance.".
What is the API Management instance?  Is this one of the registered applications? Is this an Azure resource?  Is it required to use?  I'm not sure that it is.  This section could be clearer.

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

ID: 823eb96f-e5f1-0832-b175-0b31009be92f
Version Independent ID: 330085ae-dcf6-e930-86a8-0e4a60ab1314
Content: Protect API backend in API Management using OAuth 2.0 and Azure Active Directory - Azure API Management
Content Source: articles/api-management/api-management-howto-protect-backend-with-aad.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

I understand the reference now... I found the article with Google, and now I see what section I was in.


Easm java sdk readme updates

Description
Follow-up PR for #37034  to update Readme Sample links to point to the main branch of the repository
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-analytics-defender-easm


Update README.md

@kitten we're adding maintenance status to all our packages. "Active" seems right for urql. Let me know if you have any questions.

I find this addition a little odd given that an "active" maintenance status is understood to be the default 🤔
I'd prefer a badge maybe with a link to a Formidable document somewhere that explains our different "maintenance modes"
However, if a badge isn't preferred and you'd like to add a maintenance status to all readmes, I'd still love them to be lower near the bottom, since a quick start guide and quick feature list is the first think we'd like to show 👍

@kitten yeah, I think you're right.


修正lattice lstm复现中的错误与结果

Description：修正lattice lstm复现中的错误与结果
Main reason: 之前代码有错的地方
Checklist

[x] The PR title starts with [bugfix]
[x] Changes are complete (i.e. I finished coding on this PR)  修改完成才提PR

Changes:
微博数据集是BIO编码格式，之前我错用了bmeso，导致F1过高，现修改代码以及修正报告的结果
@xuyige
@yhcc
@xpqiu

Codecov Report

Merging #240 into dev0.5.0 will decrease coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           dev0.5.0     #240      +/-   ##
============================================
- Coverage     77.12%   76.98%   -0.14%
============================================
  Files            84       84
  Lines         10041    10041
============================================
- Hits           7744     7730      -14
- Misses         2297     2311      +14

Impacted Files
Coverage Δ

fastNLP/models/biaffine_parser.py
93.57% <0%> (-2.5%)
:arrow_down:

fastNLP/core/callback.py
68.62% <0%> (-1.25%)
: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 4011e67...08399e9. Read the comment docs.


Set up channel receivers early

Problem identified while working on #143 ; this is my attempt at a fix. Another option exists in #144, and there may be other, better, ways too.
At present, components can race with each other and try to send a message on a channel before the other side has managed to set up their receiver. When this happens, an error is raised, which can lead to process termination.
Instead, set up all the receivers at the initialization stage (e.g. when calling new()). This requires some trickery to pass the mutable receiver down into the respective start() -> receive() methods, which is achieved with an option inside a cell. When the mutable receiver is consumed, it is replaced with a None value.
The stop methods of the various structs that need this all consume the reference (i.e. take &mut self), so there's no chance of the start() method being called a second time (leading to the expect calls being triggered).

I've tested this manually by rebasing #143 against it, removing the sleep, and running it against my inverter. It sends the messages on startup and everything else looks to be operating as normal as well.
I've not tried the without-mqtt-enabled or without-influx-enabled cases, but I'm pretty confident in the dead reckoning above.
Let me know what you think!


Updated the link to tensorflow.org to use https

This is a very minor change.
I just updated the link to tensorflow.org so that it uses https instead of http, and users aren't redirected. ^ _ ^

Can one of the admins verify this patch?

I signed it!

Thanks!
Jenkins, test this please.

Thanks! 😄


chore: add shadcn

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3499  👈
#3498
#3478
#3477
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite


VisibilityNotifier2D - very high memory usage

Godot version:

3.2.2 (stable) - 64 Bit Windows Client

OS/device including version:

Windows 10 (64 Bit)

Issue description:
Size of VisibilityNotifier2D Rect2 is exponentially increasing the required memory!
This is true if you increase Rect2 size either within editor or via code.
Example:

Rect2 (0,0 // 300000, 300000) -> Memory usage = 1,76 GiB

This example is extrem, but it shows the issue-
In my case I needed > 100 notifiers and even on small Rect2 sizes it scaled the memory effect very fast.
Steps to reproduce:
Add a VisibilityNotifier2D and increase Rect2 in editor or use below code.
Minimal reproduction project:
Just add following code to a new 2D Scene:
func _ready() -> void:
	var s := VisibilityNotifier2D.new()
	s.rect = Rect2(Vector2(0.0, 0.0), Vector2(300000.0, 300000.0))
	add_child(s)

Out of curiosity, can you reproduce this with VisibilityNotifier (3D)?

@Calinou just tried -> NO! ... VisibilityNotifier (3D) is simply staying on almost no memory usage.
Even after increasing all axis to an absurd <IP_ADDRESS> it had no issue.

This is probably caused by too small cell size.
You can set in Project Settings -> World -> 2d -> Cell Size bigger value e.g. 1000 and then memory usage should drop to ~40MB

@qarmin Thank you, will test it.
What is the downside of increasing this setting?

Update: I can confirm, that the memory usage with increased "cell_size" in the project settings is getting better. Also it's worth noting, that the cell_size is in PIXELs, for others looking up this issue!
For my project I set the cell_size to the full grid (Rect2), so the memory cost is almost non existant ... as all my Visibilty Notifier are having the same size, this is working also based on the global setting and the lost precision is not noticable.
Question:
I understand that heuristic is used for performance reasons, but wouldn't it be more flexible to set the cell_size inside the VisibilityNotifier2D or better directly use the dimension of the Rect2 as one Cell? ( I don't get the reason to split the notifier in multiple cells, besides flexilbility for different VisibilityNotifier2D sizes -> which could be solved by moving this setting to the Node instead of a global project setting)


[WIP] init inline transformer

Fixes #6805

ping @RyanCavanaugh @DanielRosenwasser @andy-ms @mhegazy
Sorry for disturbing you
i'm going to work on this if this issue accept pr now

// cc @rbuckton

🤷🏻♂ seems not accept pr

I think that comment counts as wanting to continue working on it.
Still cc @rbuckton  I suppose.

@Kingwl This does need a rebase off current master, though. We recently developed a strip whitespace writer, and @rbuckton has been looking into type-based property minification - so by their powers combined you should be capable of some nice things.

@Kingwl Also, since this is still marked as [WIP] (and minimal), you should probably post about what parts you find concerning and what you want feedback on.

Going to close this for the time being - I want to take the original bug back for discussion to figure out why we (I?) thought we needed it.


XP drops not shown for splashes

Teleblocks, teleports, high alchemy and other spells which do not deal damage do not display when 'replace XP drops' is toggled on.  It is useful to see the XP drops on entangles/tbs etc to know if they landed or not

@colesie
Currently I am clearing the text of all combat xp drops and replacing the HP xp drop with the damage done. I do this because the HP xp drop will always be there.
A lot of work is done just to account for split xp drop settings. I could go more into relying on the grouped xp drop setting being turned on which would allow for any xp drop that doesn't contain HP (thus isn't a hit) to be shown normally.

@colesie Currently I am clearing the text of all combat xp drops and replacing the HP xp drop with the damage done. I do this because the HP xp drop will always be there. A lot of work is done just to account for split xp drop settings. I could go more into relying on the grouped xp drop setting being turned on which would allow for any xp drop that doesn't contain HP (thus isn't a hit) to be shown normally.

An good example of what you're trying to accomplish here may be how Exilent client handles true dmg drops. The normal XP drop is displayed but in brackets the true damage is shown. This helps for seeing the splashes as xp drops without having to make a ton of exceptions for every spell in the game? Idk if this is harder or easier than what you have planned, but it works well for Exilent

@colesie
I am using the vanilla xp drop and replacing the xp drop with the hit value. Sadly there just isn't enough space in that widget to add text (to put the hit in brackets). Maybe I can try to figure out how to change the size of it, not sure if that can be done.


Erorr in production after 6.0.1 - > 6.2.1:Cannot read property 'ngInjectableDef' of undefined

Bug, feature request, or proposal:
Bug
What is the expected behavior?
App should render and don't throw runtime error in production
What is the current behavior?
App throws error at runtime and app crashes
What are the steps to reproduce?
I just upgraded my app from 6.0.1 to 6.2.1, still not clue why this error appears - but revering back to 6.0.1 fixed it.
What is the use-case or motivation for changing an existing behavior?
Bugfix
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.0.4
Material 6.2.1
Is there anything else we should know?
App worked in 6.0.1

I also had problems when I switched from 6.02 to 6.21. In my case, it was this error:
ERROR Error: StaticInjectorError(AppModule)[MatSnackBarContainer -> MatSnackBarConfig]:
StaticInjectorError(Platform: core)[MatSnackBarContainer -> MatSnackBarConfig]:
NullInjectorError: No provider for MatSnackBarConfig!
This only happend in production mode, when the MatSnackBar should open. When using "ng serve" everything was fine.
I was almost getting crazy when I tried to find out what went wrong. Luckily reverting Angular Material to 6.02 helped. MatSnackBar is working again.
I really hope, it's okay to comment underneath this issue, as this problem seems quite similar to me.

Any updates?

@ScienceOfficer I would think your fix is to include MatSnackBarConfig in the providers node of your module.
For our issue, I'm stumped.

Reverted @angular/material to 6.0.1, have these warnings still:
WARNING in<EMAIL_ADDRESS>120:77-95 "export 'ContentObserver' (imported as 'i3') was not found in '@angular/cdk/observers'
WARNING in<EMAIL_ADDRESS>153:77-95 "export 'ContentObserver' (imported as 'i3') was not found in '@angular/cdk/observers'

And same error while running.

Reverted to "@angular/cdk": "^6.0.1" and no warnings. Also, no errors in production.

I'm having the same issue after upgrade cdk to 6.2.1
main.js:1 ERROR TypeError: Cannot read property 'ngInjectableDef' of undefined
at Tr (main.js:1)
at t.get (main.js:1)
at vo (main.js:1)
at go (main.js:1)
at po (main.js:1)
at Wo (main.js:1)
at na (main.js:1)
at ta (main.js:1)
at Wo (main.js:1)
at na (main.js:1)

@theunreal thank you for the revert advice :)

I've now just updated both angular/cdk and angular/material to 6.3.0 and it seems to be fixed.

6.3.0 creates a new issue for me:
https://github.com/angular/material2/issues/11843#issue-333664697

This may solve it:
https://github.com/angular/material2/issues/11844#issuecomment-398496566
Mine seems OK now.

I think deleting the node_modules and then running again npm install work, did it work for you @kdubious ?

Yes, same package.json. Kill the @angular and rxjs folders and `npm install'. All good.

Closing as the original report is not reproducible, feel free to open a new issue with a bit more information on how to reproduce the problem.
For the other issues being discussed in this thread, it looks like it is likely related to #11844


Update the llvm commit to 061e0189a3dab6b1831a80d489ff1b15ad93aafb

There are multiple impactful changes from mlir:

[LLVM] Update C++ standard to 17 (https://reviews.llvm.org/D130689)
[ADT] Deprecate Optional::{hasValue,getValue} (NFC) (https://reviews.llvm.org/D131349)
[mlir] Remove types from attributes (https://reviews.llvm.org/D130092)
[mlir] Use SymbolTableCollection to lookup referenced symbol in AddressOfOp (https://reviews.llvm.org/D131291)
[mlir] Remove OpaqueElementsAttr (https://reviews.llvm.org/D129917)

Of these, the last two are the most impactful and I'm still working through figuring out the correct SymbolTableCollection usage, but I wanted to get eyes on this earlier rather than later because of the OpaqueElementsAttr change.
OpaqueElementsAttr which is used both in KrnlToLLVM and the NNPA accelerator was removed and a new similar, but not exactly the same, attribute was added - DenseResourceElementsAttr. torch-mlir removed there usage of OpaqueElementsAttr in favor of SparseElementsAttr, but this does not seem appropriate here (https://github.com/llvm/torch-mlir/commit/bb47c166a047ddbc913950cb0f2571594c0fe261) and the new DenseResourceElementsAttr seems like the right choice. I think DenseElementsAttr could probably also work. I'd love to get some feedback from @tungld , @AlexandreEichenberger and anyone else since it is not a simple replacement.

Note this will update onnx-mlir to the commit chosen here: https://github.com/llvm/torch-mlir/issues/1178

@tungld sorry to add to your plate, you did some good work with the constants. Do you mind looking into @sstamenova's question? Tx
@sstamenova thanks so much for lifting the LLVM to newer version, this is much much appreciated.

@sstamenova sometimes the CI just timeouts on downloading resnet50. So you can restart the CIs to see if amd/ppc results are a fluke. Both are in a zone that make download slower.

@sstamenova sometimes the CI just timeouts on downloading resnet50. So you can restart the CIs to see if amd/ppc results are a fluke. Both are in a zone that make download slower.

@AlexandreEichenberger : I'm still trying to figure out the correct way to get symbol lookup to work after the mlir change, so there is one lit test failing. I started the PR to give people a change to review the removal of the opaque attribute while I track that last failure down.

@sstamenova DenseResourceElementsAttr seems to be the right choice to me too. We have used OpaqueElementsAttr to store encoded data (a raw array of chars) for NNPA, so to make sure that DenseResourceElementsAttr works well, I need to check several models on NNPA to see if it really works or not, and it may take time.
Given that DenseResourceElementsAttr was added recently (From August 1), could we postpone the DenseResourceElementsAttr part in this update? However I still want to have your code to test DenseResourceElementsAttr, so we can go with a new PR that does not have DenseResourceElementsAttr.
As a side note, when using DenseResourceElementsAttr, I see some additional bits, e.g. 00001000 and 00000400 in your LIT tests, e.g.
0x00003E00400... becomes 0x0000100000003E00400..., 0x3F0000003F8000003F... becomes 0x000004003F0000003F8000003F.... Do you know why it is? Did you generate them using a LE or BE machine?

@tungld OpaqueElementsAttr was removed from mlir and they added DenseResourceElementsAttr at the same time to replace some of the functionality. Unfortunately, any update that picks up a new version of mlir has to replace OpaqueElementsAttr since it's gone, so we don't really have the option to delay it.
The first 4 bytes of the resource string is supposed to be the alignment. I tried to guess based on the tests what the intended alignment was, but since I didn't know what the source of the data was, I am guessing I didn't get them all correctly and would like to know what they are supposed to be.

The first 4 bytes of the resource string is supposed to be the alignment. I tried to guess based on the tests what the intended alignment was, but since I didn't know what the source of the data was, I am guessing I didn't get them all correctly and would like to know what they are supposed to be.

If so, we need a way to specify alignment since NNPA needs 4K-alignment. In the current code, all constants will be represented by KrnlGlobal with a separated alignment attribute. LLVM Global variables will be created from KrnlGlobal by setting alignment (https://github.com/onnx/onnx-mlir/blob/main/src/Conversion/KrnlToLLVM/KrnlGlobal.cpp#L75). Now if DenseResourceElementsAttr specifies alignment in its resource (or raw data in case of NNPA), I am not sure whether we need to change the lowering code for KrnlGlobal or not.

The first 4 bytes of the resource string is supposed to be the alignment. I tried to guess based on the tests what the intended alignment was, but since I didn't know what the source of the data was, I am guessing I didn't get them all correctly and would like to know what they are supposed to be.

If so, we need a way to specify alignment since NNPA needs 4K-alignment (Sometimes 8K-alignment). In the current code, all constants will be represented by KrnlGlobal with a separated alignment attribute. LLVM Global variables will be created from KrnlGlobal by setting alignment (https://github.com/onnx/onnx-mlir/blob/main/src/Conversion/KrnlToLLVM/KrnlGlobal.cpp#L75). Now if DenseResourceElementsAttr specifies alignment in its resource (or raw data in case of NNPA), I am not sure whether we need to change the lowering code for KrnlGlobal or not.

@tungld I can update the tests, but I would like to know if the change works with the models that you mentioned. I think the way it's currently setup, alignment can continue to be specified as it was before in addition to specifying it in the data.

@tungld I can update the tests, but I would like to know if the change works with the models that you mentioned. I think the way it's currently setup, alignment can continue to be specified as it was before in addition to specifying it in the data.

@sstamenova yes, I will check this patch with some models. I just returned from a long vacation and it will take time for me to give you the result.

@tungld I looked at it again, and I think what will happen right now is that the explicitly specified alignment attribute on the constant will continue to work as it is (and it is still specified), while the alignment in the hex string will be used for the reading/writing of the hex string itself. I noticed that I had used a different value in the tests and the code (alignof(char) in the code was required because the data is a char* and the type checking for the resource would assert otherwise). I've updated the tests now to match that and I expect everything to work, but I don't have anything to test with aside from the lit tests and they're passing.

@tungld I looked at it again, and I think what will happen right now is that the explicitly specified alignment attribute on the constant will continue to work as it is (and it is still specified), while the alignment in the hex string will be used for the reading/writing of the hex string itself.

@sstamenova Yes, I agree. The alignment in the hex string is used for buffers allocated during compilation only (See https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/IR/AsmState.h#L83), while our specified alignment attribute is used for allocating buffers during runtime (of the binary generated code). So they are quite independent.

@jenkins-droid test this please

@tungld : Were you able to run some tests and verify the accelerator change?

@sstamenova unfortunately, I got wrong results on NNPA when using this patch. After digging a bit, I know the reason. Let me explain here.
The main difference between OpaqueElementsAttr and DenseResourceElementsAttr is that, given a buffer, OpaqueElementsAttr's constructor will create a new buffer to store data then we can free the given buffer, while DenseResourceElementsAttr's constructor directly uses the given buffer. This difference is the key point so that DenseResourceElementsAttr can manage memory more efficiently for large buffers.
So, the code to free the given buffer is still there in  this patch, so when using DenseResourceElementsAttr, the buffer would get random values.
I confirm that just removing free will result in the correct result.

@tungld : I made the couple of updates. I'd like to check this in sooner rather than later since the longer we wait, the more likely there are conflicting changes committed and I want to avoid that since this is not a trivial change. Can you have a look?

@tungld @AlexandreEichenberger Since we have fairly high confidence now that this will work on the NNPA machine, I think it makes sense to commit this sooner rather than later and if there are issues specifically on the NNPA machine, then someone who has access to run the tests can quickly iterate to fix the issues.
I understand that we don't want any breaks in any part of the project if it can be avoided, but gating a change to main that people are waiting on (and even creating alternate PRs for https://github.com/onnx/onnx-mlir/pull/1617) seems detrimental to the community. I think until the automated tests can run directly on the NNPA machine, we need to assume that there will be breaks sometimes that will have to be investigated separately - this is what the llvm community does for targets that are not tested on the public build bots and why we've added bots for targets and platforms (e.g. Windows) we care about when we can. Especially with a change like this one that moves llvm forward, there is a high likelihood that things get committed in the mean time that need to be updated to the new llvm commit making the process even more complicated, so there is value in iterating quickly as much as possible.

Jenkins Linux s390x Build #7026 [push] Update the llvm commit t... started at 00:36

Jenkins Linux amd64 Build #7011 [push] Update the llvm commit t... started at 23:36

Jenkins Linux ppc64le Build #6119 [push] Update the llvm commit t... started at 00:37

Jenkins Linux amd64 Build #7011 [push] Update the llvm commit t... passed after 1 hr 55 min

Jenkins Linux s390x Build #7026 [push] Update the llvm commit t... passed after 1 hr 59 min

Jenkins Linux ppc64le Build #6119 [push] Update the llvm commit t... passed after 2 hr 9 min


[BUG] Insert null value into auto_increment or auto_random primary column raise “illegal null values” exception

Describe the bug

Considering the testability Improvement and user habits in sql, can we support the feature of Insert null value into auto_increment or auto_random primary column? However now it will raise the exception of illegal null values when using insert statement above mentioned.
What did you do

execute in tidb
create table t(a biting primary key auto_random)
create table t2(a biting primary key auto_increment)
execute in tispark
insert into t values(null)
insert into t2 values(null)

What do you expect

success
What happens instead

com.pingcap.tikv.exception.TiBatchWriteException: Insert null value to not null column! rows contain illegal null values!
Spark and TiSpark version info

Git Commit Hash: 9687b70202584883fe5b88d39fb62d64867ebde2
Git Branch: release-2.3
UTC Build Time: 2020-10-16 02:40:15
Supported Spark Version: 2.3 2.4
Current Spark Version: 2.4.3
Current Spark Major Version: 2.4
TimeZone: Asia/Shanghai
TIDB: release-4.0

insert null into auto increment column is supported now (https://github.com/pingcap/tispark/pull/1786).

disable writing to table with auto_random column
https://github.com/pingcap/tispark/pull/1837


Type 'Observable<any[]>' is not assignable to type 'Observable<any[]>'

Here is my code
import { Component } from '@angular/core';
import { Observable } from 'rxjs/Observable';

import * as Firebase from 'firebase';
import { observableFirebaseArray, observableFirebaseObject } from 'angular2-firebase';

@Component({
  moduleId: module.id,
  selector: 'ng2-firebase-app',
  templateUrl: 'ng2-firebase.component.html',
  styleUrls: ['ng2-firebase.component.css']
})
export class Ng2FirebaseAppComponent {
  private _firebaseUrl: string = 'https://myfirebaseurl.firebaseio.com/';

  public data: Observable<any[]>;
  public title: string = 'ng2-firebase works!';

  constructor() {
    this.data = observableFirebaseArray<any>(new Firebase(this._firebaseUrl)
      .child("data")
      .limitToFirst(6));
  }
}

Here is my error when running ng serve from the angular-cli
 Type 'Observable<any[]>' is not assignable to type 'Observable<any[]>'.
  Property 'source' is protected but type 'Observable<T>' is not a class derived from 'Observable<T>'.

VS Code also displays the error at this line this.data = observableFirebaseArray<any>
I have my ambient typings and npm packages all installed. If I comment out the line that generates the FirebaseQuery everything works fine.
I see this project has "rxjs": "5.0.0-beta.2", and the current version of the angular cli (version 0.0.39) creates new projects requiring "rxjs": "5.0.0-beta.6" - is this possibly the cause?

Yes, the Angular team rearranged things considerably with the release candidates. I'm working on a change now to bring this code up-to-date with the current stuff. Keep in mind it just came out a week ago and I just got back from ng-conf :-)

Simple answer to the problem in your code though: the types don't match. You declared data as  Observable<any[]>, but then set this.data = observableFirebaseArray<any>.  "any" is not the same as any[].

observableFirebaseArray<any> returns Observable<any[]> according to the source angular2-firebase\lib\observableFirebase.ts - 44
export function observableFirebaseArray<T>(ref: FirebaseQuery): Observable<T[]> { .. }

So my component property type should be correct.
No problem on the timeline for a fix - I am also on my way back from the conference, sitting in the airport trying to mess around with all the cool bleeding edge stuff I saw this week. I figured things would be broken everywhere - just thought I would post this to help others out.

I've published an update to this library and the accompanying demo:
https://github.com/OasisDigital/angular2-firebase-demo
I believe it will address your issue, by updating the relevant underlying libraries.  Please reopen if there is still such a problem to be found.

if you want to fix it then just change the following line
import { Observable} from 'rxjs/observable'   to    import { Observable} from 'rxjs'
:) :) :100:

if you want to fix it then just change the following line
import { Observable} from 'rxjs/observable' to import { Observable} from 'rxjs'
:) :) 💯

I had to do this too. We're looking to update rxjs to the latest version and my hope is that we'll be able to revert this.

@Mahadih534 @mtycholaz I actually haven't used this code in a year or more; here all of our projects have moved to the official angularfire2 library. (BTW, there is also a new RxFire library, very interesting, and a little more similar to this old library.)  I wasn't aware anyone else was still using this code.  :-)
Could you do a PR to make this compatibility update change?