WIP: Add tags for instance-logmsgs

Description
adding the possibility to add tags to log messages. The proposed implementation can be used to query log messages by tag or tag by log messages
Purpose

[ ] Bug fix
[x] New feature
[ ] Other

How was this tested? (if applicable)
tested manually by creating and running workflows
Test Platform Details (if applicable)
Operating system: Ubuntu 22.04/Ubuntu 22.04-Server.
CLI version:
Hypervisors/Platforms (if applicable): qemu
Checklist

[ ] Code is commented
[ ] Unit test coverage encompasses new code
[ ] Existing unit tests pass with these changes
[ ] PR is signed

Foreach
For some reason i could not use types defined in the flow package inside the states package. When i try to import it manually it gets removed when saving the file, so i came up with this complicated solution to workaround this issue for now.
My guess was that until the PR is not merged into main i cannot use newly introduced types and methods in other packages, but i may be wrong on that....


Add Emboss / Deboss Stamp Augmentation (or Option)

Add 3D effect of raised (embossed) and lowered (debossed) text or symbols that you might see on a seal or a business card.  We may need this as an internal shared lib in addition to being a top-level augmentation since we might want to raise/lower text overall or perhaps just a single seal when add in notary seals as an augmentation type of its own.

This should be possible by adding certain level of gradient in the edges of the outline, but in actual use case, i think we need to get some templates of those seals? Otherwise it might not be easy to create those seals from scratch.

We have draft set of stamps that could be integrated for use with this proposed augmentation, but that will need to be packaged for download separately, possibly on zonodo.  Nevertheless, a user will need to reference a set of images within a folder, or possibly an existing set that we may offer via URL to download via zonodo or figshare, etc.
Filters and Post-Processing
Below are possible filters that may be useful to create a debossed or embossed representation of the stamp that could then be colorized and blended into the ink layer.
The use of course-grained noise would help make the impression look more natural when blended with the page.  We may also want to borrow some of the letterpress functionality to blend ink-based stamps as well.
Note that colorized stamps would represent ink-pressed stamps while a semi-transparent white(?) stamp would represent an impression pressed into the paper to raise/low the paper instead of being combined with ink.  Both stamps and seal can have the embossed or debossed impression effect.  So a color and alpha transparency level associated with color could be passed in as a parameter or randomized (see markup augmentation and overlaybuilder utility for reference implementations).
Both scipy or opencv are dependencies that offer the convolutions.  We may want to compare speeds, but if it's a toss-up then we should stick with opencv for consistency with the majority of our existing code:
opencv:
debossed_image = cv2.filter2D(img, -1, kernel_deboss, borderType=cv2.BORDER_REFLECT)
scipi:
embossed_image = convolve2d(image, kernel_emboss, mode='same', boundary='symm')
Deboss filters
# Deboss filter kernel variation 1
kernel_deboss_1 = np.array([[-1, -1, -1],
                            [-1, 9, -1],
                            [-1, -1, -1]])

# Deboss filter kernel variation 2
kernel_deboss_2 = np.array([[0, -2, -2],
                            [2, 0, -2],
                            [2, 2, 0]])

# Deboss filter kernel variation 3
kernel_deboss_3 = np.array([[-1, -2, -1],
                            [-2, 12, -2],
                            [-1, -2, -1]])

Emboss filters
# Emboss filter kernel variation 1
kernel_emboss_1 = np.array([[-1, -1, 0],
                            [-1, 0, 1],
                            [0, 1, 1]])

# Emboss filter kernel variation 2
kernel_emboss_2 = np.array([[0, 1, 0],
                            [1, -4, 1],
                            [0, 1, 0]])

# Emboss filter kernel variation 3
kernel_emboss_3 = np.array([[-2, -1, 0],
                            [-1, 0, 1],
                            [0, 1, 2]])


apt remove in Docker layers will no twork

Hi Sören
https://github.com/X9Developers/XSN/blob/7fe0dae12f747e4b157a72b5f1123cd61c2c95ba/Dockerfile#L39
this will not work, if you want to save image sizes
because Docker images are composed in layers
every RUN command is one layer and will be safed (like in git)
you need to COPY first and merge the RUN commands in to one big command
then you can apt remove the packages as last (all in the same Docker layer)
SECOND OPTION (better)
install and compile all in an build layer
https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds
notice COPY --from=0 /go/src/github.com/alexellis/href-counter/app .
you will copy the compiled files to a clean new image
and the build layer will be erased
CLI TOOLS TO RESCUE

https://github.com/wagoodman/dive - to inspect docker layer to shrink image size
https://github.com/hadolint/hadolint - Dockerfile linter

ah
and try to take debian:stretch-lite this will safe also some MB

PR open
https://github.com/X9Developers/XSN/pull/149


Applications running on host not receiving UDP multicast packets sent from WSL2

Windows Version
Microsoft Windows [Version 10.0.22631.4249]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 22.04
Other Software
Wireshark Version 4.2.3
Repro Steps
First create a .wslconfig config file and set networkingMode=mirrored under [wsl2] as per https://learn.microsoft.com/en-us/windows/wsl/networking#mirrored-mode-networking. File should look like
[wsl2]
networkingMode=mirrored

Shutdown and restart wsl2
In wsl2 run program that sends UDP packets to a valid multicast address. I'm using the following python script:
import socket
import struct
import time

MULTICAST_GROUP = '<IP_ADDRESS>'  # Change to your desired multicast address
PORT = 5004  # Change to your desired port

# Create the socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM, socket.IPPROTO_UDP)

# Set the socket option to allow multicast
sock.setsockopt(socket.IPPROTO_IP, socket.IP_MULTICAST_TTL, 2)

# Send multicast packets
while True:
    message = b'This is a multicast message'
    sock.sendto(message, (MULTICAST_GROUP, PORT))
    print(f'Sent: {message}')
    time.sleep(1)  # Send a packet every second

In separate powershell terminal, run program that reads from the same multicast address. I'm using the following python scripts:
import socket
import struct

MULTICAST_GROUP = '<IP_ADDRESS>'  # Match the address used in the sender
PORT = 5004  # Match the port used in the sender

# Create the socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind(('', PORT))

# Tell the operating system to add the socket to the multicast group
group = socket.inet_aton(MULTICAST_GROUP)
mreq = struct.pack('4sL', group, socket.INADDR_ANY)
sock.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, mreq)

print(f'Ready to receive on {MULTICAST_GROUP}:{PORT}')

# Receive multicast packets
while True:
    data, addr = sock.recvfrom(1024)  # Buffer size is 1024 bytes
    print(f'Received message: {data} from {addr}')

Expected Behavior
Receiving script should correctly read packets from multicast address. When both programs are run on powershell, output of receiving script will look like this:

The source ip address will be the ip address from wsl2
Actual Behavior
Receiving script receives no packets. This behavior is particularly strange as Wireshark is able to see these packets

Note that the source ip address is that of eth1, output of ip addr in wsl2:

Diagnostic Logs
No response

Log zips:
WslLogs-2024-10-03_12-06-03.zip
WslNetworkingLogs-2024-10-03_12-05-08.zip

Bump for visibility

Wonder if could be related to a missing kernel option?
The 5.15. x does not have the option enabled by default, but the 6.6.x
CONFIG_IP_MULTICAST=y
do you have it enabled?

Wonder if could be related to a missing kernel option? The 5.15. x does not have the option enabled by default, but the 6.6.x
CONFIG_IP_MULTICAST=y
do you have it enabled?

My running zcat /proc/config.gz | grep MULTICAST, I can see that CONFIG_IP_MULTICAST is not set. I'm wondering why this was omitted from the wsl2 documentation if it is required for multicast to work.

By the way, I tested your app with CONFIG_IP_MULTICAST but I have the same issue as you:

Windows app side does not receive multicast
Traffic in Wireshark could be seen from WSL to Windows.
Tried to setup sender in Windows and receiver in WSL, same result (can see packets sent from Windows to WSL)

Tested with:

firewall=true / firewall=false and applying HyperV firewall rules to allow inboud/outbound UDP traffix.

Did you find the issue?

I did not try any solution that would involve setting CONFIG_IP_MULTICAST (to my knowledge this would require using a new kernel in wsl2). For what I was doing, I created a new distro and set its version number to 1 which allowed wsl to share the network interface of the host and that allowed inbound/outbound multicast traffic.
Apart from using a kernel with CONFIG_IP_MULTICAST enabled, I'm not sure what the issue could be.

Wel,, it seems that CONFIG_IP_MULTICAST (I built a custom kernel with it enabled 5.15.153...) is not enough.
However, you're right that using WSL1 makes the app work.

Since months observing the release notes, I would appreciate if UDP Multicast would finally work within a Windows 11/WSL2/DevContainer environment.
To give some motivation for roadmap priority:
Many machinery/industry protocols use derivates of UDP protocols, using UDP Multicast for fast communication and automated discovery. Examples are GigE for industrial vision or Cyclone DDS used in ROS2. Using those protocols independently from the environment is a missing link in context of DevContainers which becoming best practice meanwhile.
While in Linux<>DevContainer (most often used with "host-networking" works well I found no documented success for Windows<>DevContainer till now. So: congratulations that you finally found this solution (sadly I had no time to validate for me). Generally I look for ways to ease the "entry" into ROS2 programming for students coming with their personal devices. A user-friendly solution by default WSL is sorely missed - or just unknown by the public.

FYI: Tested with latest 2.4.4 prerelease, just in case.
Same result, it does not work.

multicast between Windows host and WSL2 (mirrored) not need  CONFIG_IP_MULTICAST=y
1.Windows host-> WSL2 (mirrored)
Run a multicast receiver simultaneously on the Windows host. Then, when the Windows host sends a multicast packet, it also sends a copy to the loopback device, and mirrors the multicast packet to the receiving direction of the WSL2's mirrored NIC. In this way, WSL2 can receive the multicast packet from the Windows host smoothly.
2.WSL2 (mirrored)->Windows host
hostAddressLoopback=true,and WSL executes "sudo ip route add <IP_ADDRESS> via <IP_ADDRESS> dev eth0 onlink", then Windows host can successfully receive multicast packets from WSL2 (mirrored)
for detail,please see WSL2 and multicast(https://blog.csdn.net/sxd2001/article/details/144649381)


#49 Implementation of support for Immutable entities

This introduce a new annotation called @EntityConstructor that will
identify an entity as Immutable. Meaning that there won't be the needs for
Setters or Default Constructor anymore.
Instead, the annotation constructor will need to have enough parameters
to support all fields. Each parameter needs to be annotated with
@Property to identity its name.
The only potential backward compatible problem comes from here: https://github.com/sai-pullabhotla/catatumbo/compare/master...athieriot:immutable?expand=1#diff-cb134f856e994b7bb0cefe33fd63d5ccR536
Previously, for exploded embedded entities, the original object was modified to set the field to an instantiated, nullified version.
Obviously, for immutable entities that won't do so I stopped this behaviour. This needed some change in the equals and equalsExpectId methods in the unit tests.
If it's an issue, I can reintroduce it for mutable entities only.
The main refactor concerned the Unmarshaller class where all the calls to setters needed to be in one place.
Finally, I know that the format don't look quite right. I'll see what I can do about it.

This looks like a very nice feature!
Just a couple of suggestions:

Reusing the @Property annotation is not so good. For instance the 'name' property (when supplied in the constructor) -- does it refer to the (Java) field name or the (Datastore) property name. (I assume the first, but then the documentation of @Property isn't correct anymore.) Also, the 'optional' or 'indexed' property don't make much sense. (I don't have a good suggestion for a new name for the annotation, but I think the two should be separated.)

Also, the @Property annotation of constructor parameters should be optional when the parameter name is available (compiled with -parameters) and matches the field name. With this, a lot of boiler-plate can be removed, since in the vast majority of cases, these should match.

+1 for the comments from @bnordli
Here are a couple of questions/thoughts:

Rename EntityConstructor annotation to PersistenceConstructor so it is more generic and can be applied to root entities as well as Embeddables.
The PersistenceConstructor annotation optionally takes an array of Strings that refer to the names of instance variables. When not specified, code must be compiled with -parameters option, in which case, each parameter name will be matched with the corresponding instance variable. If we don't like the array of Strings option, we can add a new annotation @FieldRef that can be specified on each parameter.

public class Point {
  private final int x;
  private final int y;

  @PersistenceConstructor
  public Point(int x, int y) {
    this.x = x;
    this.y = y;
  }
  //getX
  //getY
}

public class Point {
  private final int x;
  private final int y;

  @PersistenceConstructor({"x", "y"})
  public Point(int x, int y) {
    this.x = x;
    this.y = y;
  }
  //getX
  //getY
}

public class Point {
  private final int x;
  private final int y;

  @PersistenceConstructor
  public Point(@FieldRef("x") int x, @FieldRef("y") int y) {
    this.x = x;
    this.y = y;
  }
  //getX
  //getY
}

One question/concern I've is - do we really need to support multiple constructors for a given domain object (for the framework's use)? I'm thinking we should restrict to a single PersitenceConstructor for a given class. This eliminates the overhead of finding the correct constructor when entities are unmarshalled.
Finally, I think it would be nice to support partial immutable entities (entities with some fields mutable and some immutable). This may not be just for immutability, but to make sure an object's state is always valid. For example, cannot have an EmailAddress object without the email, but name is optional. What do you think?

Thank you for your reviews!
I have made some of the requested changes, mainly:

Rename EntityConstructor to PersistenceConstructor
Use a new FieldRef annotation instead of the existing Property
Use the original parameter name if class compiled with -parameters
Allow only one PersistenceConstructor

I kept from doing the last point for now (partial immutable entities) as I thought it would be a bit more involved. However I am happy to look into it, in a subsequent Pull Request maybe?
In the meantime, tell me what you think of the latest commit

@athieriot, @bnordli
Sorry it took a while to respond. This is great work and works as expected, however I've a couple of concerns:

This code will have issue when some properties are marked as optional
When entities change down the road (e.g. add a couple of fields), existing data would fail to map back

Of course, both may be solved by reverting the code to your first PR that supports multiple Persistence Constructors. But again, the number of constructors and the number of parameters in each constructor could get ugly very easily, especially when entities have many fields.
I'm wondering if we should rather support and recommend the use of Builder pattern instead of constructors approach, which also solves the immutability/consistent state problem. Doing some research on the web, it seems more and more developers are choosing the Builder pattern for this very same purpose.
In essence, this would work as outlined below, when a persistence class does not have a default public constructor:

Check the entity/persistence class for existence of a static newBuilder method, if so, invoke it.
On the returned Builder object, for each field in the entity/persistence class, call the setField method, which is same as we do today
Once all fields are set, call the build method on the Builder.

Of course, more details need to be ironed out before proceeding this path.
Let me know your thoughts.

After discussing this with a few colleagues, leveraging the builder pattern seems a much cleaner implementation. I am fully committed to follow your recommendations and make the appropriate updates.
I am personally just concerned about forcing users to use one specific form of Immutable entities (For which conventions can be more freely interpreted and assumptions can be wrongly made).
More specifically, I'm thinking about this: A good alternative to a strict builder pattern is to use chain-able "setters" on the entity itself, like withField(value). Each of those return a fresh instance of the entity with the specified field allocated. (And avoid the need of a Builder object)
Is it realistic to want to support this as well?
In the same line of questions:

Should we support the builder pattern on top of @PersistenceConstructor?
Should we expect specific method names (set<Field>) or simply allow to annote them if it's different (Same question for the newBuilder)?
Does this open the need to support framework such as Lombok (And probably others)?

I think that, all in all, I agree with the fact that a Constructor might be a bit flaky over time. I guess I am just unsure about the actual format we should expect from user's entities.
I can give that idea a go in the next few days, see how it goes. In the meantime it would be good, indeed, to have other developers opinions to try to discover the preferred way.

I fail to see the problem with optional fields, or with new fields breaking existing data: If the constructor has an argument that is not found in the data, Catatumbo should just provide the default value (null or 0).
I strongly prefer the builder pattern over with... methods, because the latter will construct very many unnecessary objects, and they are more cumbersome to write.
I think both of @PersistenceConstructor and the Builder pattern are good solutions, and I think it is reasonable if both are supported.

Here are my thoughts on the builder pattern:

We force PersistenceClass.newBuilder - should be okay even for existing code, just a new method, if they don't have one. Existing non-standard method can be deprecated.
For the Builder mutation methods, we could check for any of the common patterns in the below order. If there is existing code that does not have methods with the below pattern, they need to add needed methods and probably depreciate the existing methods. The look up for the setter method is only done one time during the entity introspection, so marshalling/unmarshalling should perform the way they are.

setField - seems to be the new standard?
withField - widely used
field - widely used

finally, we force the builder.build method that returns an instance of PersistenceClass.
Builders can use the chaining pattern to return the builder or can return void. Framework does not enforce/depend on the return type.
Builders may include getField methods, if needed, but framework does not require/use them

Let me know what you think. Thanks.

@athieriot @bnordli -
Attached is a patch to support Builder Pattern (as outlined previously). I still have to do more tests/cleanup/document, but am pretty close. When you get a chance try it out and let me know of any comments/suggestions. The patch is built from the HEAD in Eclipse format.
catatumbo5.txt

Hi @sai-pullabhotla
This is looking very good, thanks.
I was starting on the same work on my side but it's probably better if it's you ;)
I like the Strategy Pattern better than my own implementation as it would allow more use cases if need be. (Like do you think it's worth bringing the immutable Constructor back in there at some point?)
The only thing for me is that I was kind of hopping to be able to use method (with...) that would return the current instance. Allowing the implementation not to have to store any state (Returning a new instance each time) and maybe avoid writing a new Builder for every single entity.
The way it's done in the patch, there is no way it's going to happen.
It look like a solid way of doing it anyway so don't hesitate to go for it or create a PR if you want a bit more reviews.
Thanks !

Just tested on our project using an inner class for the Builder and it's working perfectly :)

So, here is an example of what we are doing right now:
public class Document<T> {
    private final T content;
    private String _id;
}

public Document(T content) {
    this.content = content;
}

 public Document<T> withId(String id) {
    Document<T> newDoc = new Document<>(content);
    newDoc._id = id;
    return newDoc;
}

I'm sure there is several other way to implement this but, basically, each withThing call only returns a new instance and nothing else (Doesn't really store the value in a state).
From a Catatumbo point of view it would mean keeping track of those instances and call each next method in the chain on it instead.
This approach obviously creates many more instances but avoid the need for a builder for each and every single Entity (Including embedded ones)
Does that make sense?

Not sure if we can ever support this specific case, but if it helps, you can in fact use Lombok/Kotlin (tools that process compile time annotations) to convert existing model classes to one of the patterns (classic JavaBeans or Builder). I just tested with Lombok's Builder and everything works fine. Below is an example with Lombok's Builder. I plan to merge the support for Builder pattern and cut a release by EOW, unless you thnink I should hold off for any reason.
import com.jmethods.catatumbo.Entity;
import com.jmethods.catatumbo.EntityManager;
import com.jmethods.catatumbo.EntityManagerFactory;
import com.jmethods.catatumbo.Identifier;
import lombok.Builder;
import lombok.Data;
import com.jmethods.catatumbo.Entity;
import com.jmethods.catatumbo.EntityManager;
import com.jmethods.catatumbo.EntityManagerFactory;
import com.jmethods.catatumbo.Identifier;

import lombok.Builder;
import lombok.Data;

@Data // Lombok
@Builder // Lombok
@Entity // Catatumbo
public class Car {
	@Identifier // Catatumbo
	private long id;

	private final String make;

	private final String model;

	private final int year;

	private String VIN;

	public static void main(String[] args) {
		EntityManager em = EntityManagerFactory.getInstance().createDefaultEntityManager();
		Car car = Car.builder().make("Mercedes").model("ML350").year(2011).VIN("11111111").build();
		Car car2 = em.insert(car);
		Car car3 = em.load(Car.class, car2.getId());
		System.out.println(car);
		System.out.println(car2);
		System.out.println(car3);
	}

}

This looks great!
Will you support setField(...) methods on the builder in addition to Lombok's field(...)?

By all means carry on with the release of the feature :)
It looks great as it is and will unlock the situation.
I think there is nothing, technically, that prevent us to implement the with feature in Catatumbo but I totally understand you want to limit the number of ways to use this feature.
I've been considering Lombok before but not sure how likely we are to use it. Might be a good time to propose again ;)
One question though, do you want to change the default newBuilder method to search for builder and be compatible with Lombok? (It's configurable anyway)

Search for the mutator methods in the Builder class is in the following order:

setField
withField
field

Search for the static method that returns a Builder is in the following order:

newBuilder
builder

Let me know of any changes to this.

Sounds perfect

@athieriot - the support for Builder pattern is merged into HEAD. Feel free to let me know if you need any further changes. Should have the release out over the weekend. Thanks.

Hi !
Finally had the time to test it properly and I was wondering if there is a way to check for the newBuilder method the other way round?
Like: If there is a builder available use it, otherwise search for a Default constructor?

We could, but that may break backward compatibility on existing applications (assuming the persistence class is a classic POJO, but also has a newBuilder method. What is the rationale behind this change request? May be we need to introduce a new annotation - @Builder, if it is really needed?

I know I've been prone to ask such requests before (Where it looks I try to "Pull the rug" to me) and it's actually quite good to have a defender of the library to keep it from side tracking :)
All in all, I just wanted to assure you that it's not out of laziness we are merely trying to protect the backward compatibility for our users as well.
I'll give a try today at using the new approach into our code base and see what happens. I might come back to you in the form of a Pull Request otherwise ;)
Thank you


Adding MaxQuant training

This is our first MaxQuant training :)
I also added levels for other proteomics tutorials

Danke @foellmelanie!


Unable to run a script with runscript

I am trying to run a script with RunScript - the script runs from a UNC path. Is that possible? The RunScript creates the script file in the temp directory correctly, it will just not run. It is just \servername\path\script.cmd ....If I run that script file locally on the server it does run. My script is not the problem, as it has been running for a few years through a scheduled task. There are no errors:
Result
[2015-12-21 22:32:11] Success - connect to remote Windows machine x.x.x.x
[2015-12-21 22:32:12] Success - send file to remote machine
[2015-12-21 22:32:12] Success - trigger batch script in VM

System.Management.ManagementBaseObject

Thanks for any assistance!

I decided to do what I was originally attempting, which is to schedule a task from WebCommander to run the command.
The entire problem came down to the fact that when executing the schtasks.exe, I needed to give the full path C:\Windows\System32\schtasks.exe .... ugh!

You could run a script from UNC share via the runScript command. The tricky part is that you need to mount the UNC (also via the same runScript command) first. For instance, in order to run
\share\script.bat
you should run the following to commands instead
net use \share  /user:
\share\script.bat

ok thanks Jerry.


fastai2.vision import error

torch (1.4.0)                                - Tensors and Dynamic neural networks in Python with strong GPU acceleration
INSTALLED: 1.3.0
torchvision (0.5.0)                              - image and video datasets and models for torch deep learning
INSTALLED: 0.5.0 (latest)
latest fastai2/fastcore (installed from updated local source - i'm doing git pulls /rebases 5 times a day)
I'm running the camvid.ipynb notebook from examples.
This import:
from fastai2.vision.all import *
generates this error:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-2-352c3a9f46af> in <module>
      1 from fastai2.basics import *
      2 from fastai2.callback.all import *
----> 3 from fastai2.vision.all import *

~/workspace/fastai2/fastai2/vision/all.py in <module>
      1 from ..basics import *
      2 from ..callback.all import *
----> 3 from .augment import *
      4 from .core import *
      5 from .data import *

~/workspace/fastai2/fastai2/vision/augment.py in <module>
     89
     90 # Cell
---> 91 from torchvision.transforms.functional import pad as tvpad
     92
     93 # Cell

/opt/conda/lib/python3.6/site-packages/torchvision/__init__.py in <module>
      1 import warnings
      2
----> 3 from torchvision import models
      4 from torchvision import datasets
      5 from torchvision import ops

/opt/conda/lib/python3.6/site-packages/torchvision/models/__init__.py in <module>
     10 from .shufflenetv2 import *
     11 from . import segmentation
---> 12 from . import detection
     13 from . import video
     14 from . import quantization

/opt/conda/lib/python3.6/site-packages/torchvision/models/detection/__init__.py in <module>
----> 1 from .faster_rcnn import *
      2 from .mask_rcnn import *
      3 from .keypoint_rcnn import *

/opt/conda/lib/python3.6/site-packages/torchvision/models/detection/faster_rcnn.py in <module>
     11
     12 from .generalized_rcnn import GeneralizedRCNN
---> 13 from .rpn import AnchorGenerator, RPNHead, RegionProposalNetwork
     14 from .roi_heads import RoIHeads
     15 from .transform import GeneralizedRCNNTransform

/opt/conda/lib/python3.6/site-packages/torchvision/models/detection/rpn.py in <module>
      9 from torchvision.ops import boxes as box_ops
     10
---> 11 from . import _utils as det_utils
     12 from .image_list import ImageList
     13

/opt/conda/lib/python3.6/site-packages/torchvision/models/detection/_utils.py in <module>
     17
     18 @torch.jit.script
---> 19 class BalancedPositiveNegativeSampler(object):
     20     """
     21     This class samples batches, ensuring that they contain a fixed proportion of positives

/opt/conda/lib/python3.6/site-packages/torch/jit/__init__.py in script(obj, optimize, _frames_up, _rcb)
   1217         if _rcb is None:
   1218             _rcb = _jit_internal.createResolutionCallback(_frames_up + 1)
-> 1219         _compile_and_register_class(obj, _rcb, qualified_name)
   1220         return obj
   1221     else:

/opt/conda/lib/python3.6/site-packages/torch/jit/__init__.py in _compile_and_register_class(obj, rcb, qualified_name)
   1074 def _compile_and_register_class(obj, rcb, qualified_name):
   1075     ast = get_jit_class_def(obj, obj.__name__)
-> 1076     _jit_script_class_compile(qualified_name, ast, rcb)
   1077     _add_script_class(obj, qualified_name)
   1078

/opt/conda/lib/python3.6/site-packages/torch/jit/_recursive.py in try_compile_fn(fn, loc)
    220     # object
    221     rcb = _jit_internal.createResolutionCallbackFromClosure(fn)
--> 222     return torch.jit.script(fn, _rcb=rcb)
    223
    224

/opt/conda/lib/python3.6/site-packages/torch/jit/__init__.py in script(obj, optimize, _frames_up, _rcb)
   1224         if _rcb is None:
   1225             _rcb = _gen_rcb(obj, _frames_up)
-> 1226         fn = torch._C._jit_script_compile(qualified_name, ast, _rcb, get_default_args(obj))
   1227         # Forward docstrings
   1228         fn.__doc__ = obj.__doc__

RuntimeError:
builtin cannot be used as a value:
at /opt/conda/lib/python3.6/site-packages/torchvision/models/detection/_utils.py:14:56
def zeros_like(tensor, dtype):
    # type: (Tensor, int) -> Tensor
    return torch.zeros_like(tensor, dtype=dtype, layout=tensor.layout,
                                                        ~~~~~~~~~~~~~ <--- HERE
                            device=tensor.device, pin_memory=tensor.is_pinned())
'zeros_like' is being compiled since it was called from '__torch__.torchvision.models.detection._utils.BalancedPositiveNegativeSampler.__call__'
at /opt/conda/lib/python3.6/site-packages/torchvision/models/detection/_utils.py:72:12

            # randomly select positive and negative examples
            perm1 = torch.randperm(positive.numel(), device=positive.device)[:num_pos]
            perm2 = torch.randperm(negative.numel(), device=negative.device)[:num_neg]

            pos_idx_per_image = positive[perm1]
            neg_idx_per_image = negative[perm2]

            # create binary mask from indices
            pos_idx_per_image_mask = zeros_like(
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~...  <--- HERE
                matched_idxs_per_image, dtype=torch.uint8
            )
            neg_idx_per_image_mask = zeros_like(
                matched_idxs_per_image, dtype=torch.uint8
            )

            pos_idx_per_image_mask[pos_idx_per_image] = torch.tensor(1, dtype=torch.uint8)
            neg_idx_per_image_mask[neg_idx_per_image] = torch.tensor(1, dtype=torch.uint8)

This is a torchvision error, not a fastai2 error, triggered by this line: from torchvision import models. You should open an issue on their side.


OCPBUGS-24595: Cloudeventproxy 2 Card WPC not able to handle multiple dependency and multiple ts2phcs

/jira refresh

/jira refresh

/jira refresh

/test e2e-aws

/cherry-pick release-4.15


Open stored procedure in portal

@fiveisprime, @jinglouMSFT The best the portal will allow is for me to open up the entire account (which we already have an Open in Portal for) and open the Data Explorer tab. From there you'd need to drill down to the DB, collection and stored procedure. Still worth doing?

@EricJizbaMSFT's comments on this:

IMO its more confusing than valuable if the open in portal links to the Cosmos DB Account instead of directly to the stored procedure

@djlan DJ, is there a way to link directly to a stored procedure in the portal? Right now I can only find a way to link to the Data Explorer for the entire CosmosDB database.  Thanks.

That's confusing.. if we can't deep link directly, I say we scrap this.

@djlan DJ? Is there a way to link directly to a stored procedure in the portal? Right now I can only find a way to link to the Data Explorer for the entire CosmosDB database. Thanks.

DJ says the portal does not support direct links, so closing.


Support  Accessibility handling

Hi,
is there a way to support Accessibility handling.
Thanks

I have no idea of what that actually entails ..... so I don't know ?
If you would like to submit a PR adding Accessibility support then I'll help if I can.
(Note that I'm not the original author, just the current maintainer)

I have no idea of what that actually entails ..... so I don't know ?
If you would like to submit a PR adding Accessibility support then I'll help if I can.
(Note that I'm not the original author, just the current maintainer)

Accessibility is provided by implementing the functions 'queryAccessibleAttribute' and  'executeAccessibleAction' from the Node class.
These functions are called by the oprating system and allow things as dictating. I've  found  any documentation.   I've tryed to understand the procedure but wasn't quite succesfull and gave up.

I had a quick look at the API in Node with regards to this and it seems that for starters you can just try:
area.setAccessibleRole( AccessibleRole.TEXT_AREA ); and you are good to go.
It may be, although I don't think so, that you'll also need to use: area.accessibleTextProperty().bind( area.textProperty() );
Just from my brief look and limited understanding I don't think any of the AccessibleActions need to implemented by executeAccessibleAction for just basic functionality. So just give the above a try and see what you get.

Dictating is working on Windows, but not on Mac.


Clear graph when results are cleared

When results are cleared from the UI, the graph does not pick up this change. This is confusing for the user who expects the graph to be cleared.
If the user does not manually reset the graph and runs a further query, the old results still remain in the graph.

Merged into develop.


Is there any way to prevent transition temporarily not using ?

I'm using react-router and redux-saga for my App.
And I'm trying to make a kind of alert "Change isn't saved. Are you sure to leave?" with snackbar ui.
To do that, I made a saga watching "LOCATION_CHANGE" action of router, and an alert when the action detected.
But I want to make the alert with Snackbar UI, so I tried to find a way to prevent transition for a second. However, I just could find . Is there any chance to do what I want to do?

confirm dialog with custom UI would be nice


Relevance of trained_ index file?

I have been directing users in my community to only bother saving the .index file beginning with added_
Is it relevant to also have the trained_ .index file which is small?

trained_.index doesn't save feature in it.


iam_authorization has no effect

First I would like to express a big thanks you to this excellent framework - Zappa is great !
So far I could successfully develop, deploy and run gateway calls with invoking lambda functions.
Now I would like to let only authenticated users calling the API.
I have set iam_authentication to true, but this has no effect; I can still call the API via Postman without a valid token.
Any idea what else needs to be configured ?

SOLVED -
In AWS I had to deploy my api to the respective stage, then it worked properly !


AdverseEvent::primaryCodePath points to obsolete "type" field in fhir-modelinfo xml

There is probably an error in the model-info XML file.
AdverseEvent::primaryCodePath points to an obsolete "type" field.  There is no "type" field in AdverseEvent class, but there is an "event" field instead.
Could you please take a look and correct the issue?

@brynrhodes , there appear to be some similar issues with other non-existent primaryCode paths:

category for DetectedIssue (should this be code?)
device.code for DeviceUseStatement (should this be device?)
measure.topic for MeasureReport (should this be measure?)

These are all in FHIR Model Info file for FHIR 4.0.1 but not present within the respective resources.

Included in release 1.5.1


Add label to control the key in the serialized output

This commit adds an optional parameter, label, to a Field. When serialized, the serializer will use the label if it is defined, or it will default to using the attribute name as before.
This commit includes two new unit tests for this functionality.
Fixes #14

I think this is ready to go now.

Looks good, thanks!


[Bug] Copy as curl is missing "--insecure" flag if SSL is disabled

Insomnia Version: <IP_ADDRESS>1
Operating System: Mac OS

Details
When SSL is disabled (by Insomnia parameters), copy as curl should include --insecure flag to reflect this configuration.

Hi @ebuildy. This is a duplicate of #491
Since Insomnia uses a 3rd-party library to do code generation, fixing this is a bit tricky. However, you are the second person now to suggest it so maybe it's a common enough problem to fix.


Value object serialization

I've tried to wrap a complex process into the workflow. The package indeed has a hard time restoring activities with DTO, Value Objects, or Enums inside.
It's of course possible to create all the code using only primitive types, but in enterprise scenarios that would be a massive productivity killer. It would be nice to make it work at least as native jobs as they can hold objects with no problem even though that is not a best practice for performance.
Example stacktrace of failing activity (Eloquent Enum Cast):
Cannot instantiate enum App\Enums\TransactionType {"exception":"[object] (Error(code: 0): Cannot instantiate enum App\\Enums\\TransactionType at /var/www/html/vendor/opis/closure/src/SerializableClosure.php:411)
[stacktrace]
#0 /var/www/html/vendor/opis/closure/src/SerializableClosure.php(411): ReflectionClass->newInstanceWithoutConstructor()
#1 /var/www/html/vendor/opis/closure/src/SerializableClosure.php(427): Opis\\Closure\\SerializableClosure::wrapClosures()
#2 /var/www/html/vendor/opis/closure/src/SerializableClosure.php(427): Opis\\Closure\\SerializableClosure::wrapClosures()
#3 /var/www/html/vendor/opis/closure/functions.php(19): Opis\\Closure\\SerializableClosure::wrapClosures()
#4 /var/www/html/vendor/laravel-workflow/laravel-workflow/src/Serializers/Y.php(45): Opis\\Closure\\serialize()
#5 /var/www/html/vendor/laravel-workflow/laravel-workflow/src/WorkflowStub.php(200): Workflow\\Serializers\\Y::serialize()
#6 /var/www/html/vendor/laravel-workflow/laravel-workflow/src/Middleware/WorkflowMiddleware.php(15): Workflow\\WorkflowStub->next()
#7 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Workflow\\Middleware\\WorkflowMiddleware->handle()
#8 /var/www/html/vendor/laravel-workflow/laravel-workflow/src/Middleware/WithoutOverlappingMiddleware.php(75): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Workflow\\Middleware\\WithoutOverlappingMiddleware->handle()
#10 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(116): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#11 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(126): Illuminate\\Pipeline\\Pipeline->then()
#12 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(70): Illuminate\\Queue\\CallQueuedHandler->dispatchThroughMiddleware()
#13 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(98): Illuminate\\Queue\\CallQueuedHandler->call()
#14 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(425): Illuminate\\Queue\\Jobs\\Job->fire()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(375): Illuminate\\Queue\\Worker->process()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(173): Illuminate\\Queue\\Worker->runJob()
#17 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(147): Illuminate\\Queue\\Worker->daemon()
#18 /var/www/html/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(130): Illuminate\\Queue\\Console\\WorkCommand->runWorker()
#19 /var/www/html/vendor/laravel/horizon/src/Console/WorkCommand.php(51): Illuminate\\Queue\\Console\\WorkCommand->handle()

I wonder if https://github.com/laravel-workflow/laravel-workflow/pull/49 will fix that?

@michael-rubel I'm trying to make a failing test. Do you have some code you can share of how you tigger this? Thanks!

Fixed in 0.0.24. Feel free to re-open or make a new issue if it didn't! Thanks for your reports and suggestions!


RenderDoc crashes when loading Vulkan capture

One of the apps we're working on generates RenderDoc captures that cause the UI to crash when trying to load them. Here is the relevant portion of the stack trace:
0c 00000000`2e67d0f0 00007ffb`f0c0ed42 : 00000000`26477c60 00000000`2649eef0 00000000`226b0690 00000000`00000000 : renderdoc!WrappedVulkan::Serialise_vkAllocateMemory+0x23d [c:\users\nsubtil\src\renderdoc\renderdoc\driver\vulkan\wrappers\vk_resource_funcs.cpp @ 163]
0d 00000000`2e67d940 00007ffb`f0c175b7 : 00000000`26477c60 00000000`00024091 00000000`0000000a 00007ffb`0000000a : renderdoc!WrappedVulkan::ProcessChunk+0x172 [c:\users\nsubtil\src\renderdoc\renderdoc\driver\vulkan\vk_core.cpp @ 1987]
0e 00000000`2e67dc00 00007ffb`f0d6579f : 00000000`26477c60 cccccccc`cccccccc cccccccc`cccccccc cccccccc`cccccccc : renderdoc!WrappedVulkan::ReadLogInitialisation+0x237 [c:\users\nsubtil\src\renderdoc\renderdoc\driver\vulkan\vk_core.cpp @ 1688]
0f 00000000`2e67df90 00007ffb`efdbf3f5 : 00000000`26477d40 cccccccc`cccccccc cccccccc`cccccccc cccccccc`cccccccc : renderdoc!VulkanReplay::ReadLogInitialisation+0x2f [c:\users\nsubtil\src\renderdoc\renderdoc\driver\vulkan\vk_replay.cpp @ 663]
10 00000000`2e67dfc0 00007ffb`efdb7fad : 00000000`26530ff0 00000000`26477d40 00007ffb`f10b21c0 00000000`000005ff : renderdoc!ReplayController::PostCreateInit+0x85 [c:\users\nsubtil\src\renderdoc\renderdoc\replay\replay_controller.cpp @ 1561]
11 00000000`2e67e500 00007ffb`efd8d5cc : 00000000`26530ff0 00000000`264ca1c0 cccccccc`cccccccc cccccccc`cccccccc : renderdoc!ReplayController::CreateDevice+0x1fd [c:\users\nsubtil\src\renderdoc\renderdoc\replay\replay_controller.cpp @ 1536]
12 00000000`2e67e600 00007ffb`efd935bd : 00000000`264b80b0 00000000`2e67e748 00000000`03a505f0 cccccccc`cccccccc : renderdoc!CaptureFile::OpenCapture+0x12c [c:\users\nsubtil\src\renderdoc\renderdoc\replay\capture_file.cpp @ 105]
13 00000000`2e67e6f0 00007ffb`f4536b5b : 00000000`264bc0e0 00000000`03a505f0 00000000`2e67e8f0 00000000`03e84228 : renderdoc!RENDERDOC_CreateReplayRenderer+0x8d [c:\users\nsubtil\src\renderdoc\renderdoc\replay\entry_points.cpp @ 360]

Crash occurs during a call to vkAllocateMemory in vk_resource_funcs.cpp:163:
    // serialised memory type index is non-remapped, so we remap now.
    // PORTABILITY may need to re-write info to change memory type index to the
    // appropriate index on replay
    info.memoryTypeIndex = m_PhysicalDeviceData.memIdxMap[info.memoryTypeIndex];

    VkResult ret = ObjDisp(device)->AllocateMemory(Unwrap(device), &info, NULL, &mem); <--- crash

The problem seems to be that info.memoryTypeIndex is invalid (0xffffffff). The app being captured works fine, this particular memoryTypeIndex doesn't show up in the API trace itself.
I can make the capture file available if that would help. Stack trace is from commit d539fed918, though the same crash happens on the latest release version. Similar symptoms show up on several NVIDIA GPUs (haven't tested any other vendors).

Can you post the full output log somewhere, like gist? I think this could be caused by replaying a capture made on one GPU/driver combo on an incompatibly different GPU/driver combo (such that the memory types don't match up).

Here is the log: https://gist.github.com/nsubtil/445df967fd53a107a406620df06ad0c6

Right, so I think this is the key problem:
Captured log describes physical device 0:
   - Intel(R) HD Graphics 530 (ver 0.16 patch 0x3) - 8086:191b
Mapping during replay to physical device 0:
   - GeForce GTX 1060 (ver 382.83 patch 0x0) - 10de:1c20
Captured log describes physical device 1:
   - GeForce GTX 1060 (ver 382.83 patch 0x0) - 10de:1c20
Mapping during replay to physical device 0:
   - GeForce GTX 1060 (ver 382.83 patch 0x0) - 10de:1c20
Captured log describes physical device 2:
   - GeForce GTX 1080 (ver 382.83 patch 0x0) - 10de:1b80
Mapping during replay to physical device 1:
   - GeForce GTX 1080 (ver 382.83 patch 0x0) - 10de:1b80

On capture the physical devices were: 0: Intel IGPU, 1: GTX 1060, 2: GTX 1080. On  replay it looks like the physical devices are just 0: GTX 1060, 1: GTX 1080. If there was an Intel IGPU available (maybe as physical device 2) then renderdoc should have remapped to it, but it looks like it's not available at all.
In theory this isn't a problem if the application explicitly selected the nvidia card, and ignored the intel card. However given the memory type problem you're running into it sounds like the capture used the intel card and there was nothing to map it to on replay.
As to why you're not getting the same physical devices enumerated on capture and replay (or why renderdoc isn't remapping the intel card) - that I don't know. I know nvidia has a layer which messes with the order but I thought it would just re-order the list to prioritise the physical device it wanted to favour for the application, rather than outright remove a physical device.
Are you able to recompile renderdoc? I could give you a branch with extra logging enabled that could eliminate any doubt about which physical devices were available on capture and replay.

Yes, building from source works fine. I can certainly try a different branch if you point me at it.

OK I've added a branch vk_phys_logging which prints to the log which physical devices are available on capture and replay. Can you try running with that and see what it prints out?

Apologies for the delay, here's the log from vk_phys_logging:
https://gist.github.com/nsubtil/cae1592291452713d97098a53661296f
On Tue, Jul 25, 2017 at 12:46 PM, Baldur Karlsson<EMAIL_ADDRESS>wrote:

OK I've added a branch vk_phys_logging
https://github.com/baldurk/renderdoc/tree/vk_phys_logging which prints
to the log which physical devices are available on capture and replay. Can
you try running with that and see what it prints out?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/baldurk/renderdoc/issues/703#issuecomment-317851067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF66M4q9fsxipamBuyIwmZQU06HAhLsyks5sRkYkgaJpZM4Oh1_x
.

OK yeh, so that confirms the problem. The intel card is available at physical device 0 on capture, but is completely missing from replay:
RDOC 015516: [23:13:41]  vk_device_funcs.cpp( 439) - Log     - [0] - Intel(R) HD Graphics 530 (ver 0.16 patch 0x3) - 8086:191b
RDOC 015516: [23:13:41]  vk_device_funcs.cpp( 439) - Log     - [1] - GeForce GTX 1060 (ver 382.83 patch 0x0) - 10de:1c20
RDOC 015516: [23:13:41]  vk_device_funcs.cpp( 439) - Log     - [2] - GeForce GTX 1080 (ver 382.83 patch 0x0) - 10de:1b80
...
RDOC 011316: [23:14:30]  vk_device_funcs.cpp( 275) - Log     - During Replay 2 physical devices:
RDOC 011316: [23:14:30]  vk_device_funcs.cpp( 284) - Log     - [0] - GeForce GTX 1060 (ver 382.83 patch 0x0) - 10de:1c20
RDOC 011316: [23:14:30]  vk_device_funcs.cpp( 284) - Log     - [1] - GeForce GTX 1080 (ver 382.83 patch 0x0) - 10de:1b80

Currently it's impossible to replay on a significantly different device (like a different IHV) so this makes the replay fail.
I don't know why the physical devices reported are changing, maybe this is something nvidia's layer is doing - if so that is actively hostile behaviour. I thought it just re-ordered the devices, which still isn't great since applications should choose themselves, but at least it meant everything is still reported.
This is beyond RenderDoc's ability to fix though. All I can suggest is that either in code you avoid using the Intel physical device if possible, or locally just disable the intel vulkan driver if you don't need it.

I believe physical device remapping should now be solid in v1.0, as long as there isn't a completely incompatible set of devices - that's still unsupported.


NFC: Test emitted interface for module containing subclass of an Obj-C class with an NS_SWIFT_UNAVAILABLE initializer

Add a test that exercises subclassing an Obj-C subclass of NSObject and verifies the printed members of the Swift subclass when emitting a module interface for a module containing the Swift subclass. Also verifies that NS_SWIFT_UNAVAILABLE initializers are omitted from the emitted interface.
Relates to rdar://91981394

@swift-ci please test

@swift-ci please test Windows

@swift-ci please smoke test and merge

@swift-ci please smoke test


Stored procedure with JSONB argument not exposed through postgrest

I have defined a function on postgres that takes JSONB argument as the only argument, however, when attempting to call the function through postgREST it fails and complains that no function defined with argument of json type. I understand the below example I could use bulk insert via POST, however, the example is much simplified here than my actual use case.
Step to reproduce:

Create the stored function with JSONB argument as follows:

CREATE OR REPLACE FUNCTION insert_from_document(jsonArrayOfPeople **JSONB**)   RETURNS VOID LANGUAGE plpgsql AS $$ DECLARE   people JSONB; BEGIN   FOR people IN SELECT * FROM jsonb_array_elements(jsonArrayOfPeople)   LOOP     PERFORM insert_from_raw_people(people);   END LOOP; END; $$;

Send the post request via curl:
curl -X POST \ http://localhost:3000/rpc/insert_from_document \ -H 'content-type: application/json' \ -H 'prefer: params=single-object' \ -d '[{"first_name": "John", "last_name": "Smith"},{"first_name": "Bob", "last_name": "Smith"}]'

Observe the error response from postgREST:
{ "hint": "No function matches the given name and argument types. You might need to add explicit type casts.", "details": null, "code": "42883", "message": "function public.insert_from_document(json) does not exist" }

Thanks for the bug report. I was about to mention params=single-object but you're already using it.
Looks like the problem is in https://github.com/begriffs/postgrest/blob/master/src/PostgREST/QueryBuilder.hs#L168
We could try insertableValueWithType "unknown" and see if postgresql can figure out when to use json/jsonb.

Thanks for the suggestion. Tried insertableValueWithType "unknown" and I would get a different error with the same post request in my initial submission:
{
  "hint": null,
  "details": null,
  "code": "22023",
  "message": "cannot extract elements from an object"
}

I however found a work around for this for now. The work around is to wrap the json array in a json object with a document property, eg:
curl -X POST \ http://localhost:3000/rpc/insert_from_document \ -H 'content-type: application/json' \ -H 'prefer: params=single-object' \ -d '{"document: [{"first_name": "John", "last_name": "Smith"},{"first_name": "Bob", "last_name": "Smith"}]}'

Also, what if you modified the function to take a json argument rather than jsonb? That might make the initial rpc request work.

This is not a workaround (wrapping the body), this is the correct way of calling a function, the body of the request (calling rpc functions) needs to be a single json object with parameter names as keys for the json object, even if it's just one parameter.


Setup dev environment Linux

Hello I'm working on ubuntu 18.04 I'm trying to setup an environment  with this project.
I've created the cmake project for eclipse with (with conan dep manager):
cd nmos-cpp/
mkdir Build
cd Build
cmake ../Development -G "Eclipse CDT4 - Unix Makefiles" -DCMAKE_BUILD_TYPE:STRING=DEBUG
Eclipse import -> make project
The project compile and runs but i've a lot of semantic error, I suppose is due to indexer but I don't know how to fix this...
Do you have any suggestion? Or specific setup to develop under linux environment?
Many thanks for your help

I'm sorry, I do not use Eclipse so I cannot answer this question from experience. This post looks relevant: https://stackoverflow.com/questions/8148235/eclipse-cdt-shows-semantic-errors-but-compilation-is-ok
Otherwise, maybe other nmos-cpp users will be able to help.

Thanks, I've already tried some fix but it looks too tricky, maybe i can try some different setup, which setup you suggest on linux?

See #95 for comments from a couple of other users. I tend to build and run unit tests and API tests on Linux (also run by GitHub Actions CI) but develop and debug using Visual Studio tools.

Many thanks for the link Gareth, in medio stat virtus, i've found a solution with code-insiders + cmake tools + gdb that for now is ok for me. I give a try to this solution before switch to visual studio + windows server 2019. Many thanks for the support! :)

Thanks so much for reporting back. I've heard positive things about the Visual Studio Code experience with GDB on Linux and also with Windows Subsystem for Linux. Good luck with your project.
P.S. And thanks for teaching me a useful Latin phrase I hadn't come across before! :-)


NIFI 7525 - Create a nullValue() Subjectless Functions and support null type on Expression Language

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables NIFI-7525 functionality
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[X] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Note: ci-workflow failed in other modules. I modified only nifi-expression-language

Hello friend @adarmiento @mgaido91
How to about that?

I don't see the usefulness of such a method and I am not sure it is worth the big code change, sorry

I don't see the usefulness of such a method and I am not sure it is worth the big code change, sorry

Hello Marco! Thanks for your time!
In the past I've been use NiFi for some data trasformations and, sometime, some automatical conversions (for example from JSON -> Avro) wasn't compatible with the "empty value filosofy" used inside NiFi. For example: When I have an empty value: what is it? Is it a string? is a number? It could be a "null" values?
This change skips this misunderstanding enabling the user to use programmatically NULL value (inside of expression language)
if you think it's better, I can create an article to expose that!
Kind regards

I think you can maybe send an email in the community list to check whether this is a feature many people need and in case of a favorable result we can go ahead with the PR. Thanks.

Hello @Fabryprog,
Whatever the outcome of the discussion with the community, I would undersline that you are not actually interested in the null value itself (if I understood correctly) but rather in propagating the type a field which is null for a specific in-transit object


A simpler way to detect Preact

Hi! I was doing some digging into the source code and I noticed that the current approach of detecting Preact environment creates some constraints in the other parts of the library. If we just had some simpler, ideally synchronous way of Preact detection we would have:

Avoided having an invisible span rendered by <FpjsProvider />. While it doesn't seem like a big deal, there could be some clients that expect the library doesn't produce any html, and could rely on some exotic CSS in their apps like body > div.
Simplified the client initialization and loading logic and potentially avoided extra rendering at the startup.

I don't have a definitive answer yet, however I have compiled a list of tricks that might work here:

A more hacky and less stable option: ctx = createContext({}); isPreact = ctx._id || ctx.__c (the property name is _id in the source code, but it becomes __c after mangling). Pros: works for Preact starting from 10.0.0 (the first release where hooks became generally available), doesn't require any additional component, completely synchronous. Cons: it's implementation specific and might break in the future.
Check the number of arguments passed down to class component's render(). Preact always has two agruments. Pros: works in both 8.x and 10.x, it's an official documented difference and it is less likely to be changed in the current release Cons: it is not completely synchronous, however it doesn't output an html element.

Let me know what you think,
Cheers.

Hey @molefrog, thanks a lot for your suggestions!
I've tried them both, and the second one seems very solid, so we will definitely try to use it in our implementation.
The first one also did work for me, but we want to avoid solutions that might potentially break in the future.
Cheers!

Hey @molefrog, thanks a lot for your suggestions!
I've tried them both, and the second one seems very solid, so we will definitely try to use it in our implementation. The first one also did work for me, but we want to avoid solutions that might potentially break in the future.
Cheers!

Fair enough. Regarding the second solution, I've checked it as well and unfortunately there is no good way to make it synchronous. It also requires a class being declared, which considering that we target es5 could result in a bigger bundle. However we could avoid classes with this trickery: I've made a demo to illustrate that.

we will definitely try to use it in our implementation.

Is there a possibility for me to work on that PR? It would be a fun micro-project for me. I'll probably need some review and assistance though with the code style etc.

Is there a possibility for me to work on that PR? It would be a fun micro-project for me. I'll probably need some review and assistance though with the code style etc.

Sure! When you submit a PR someone from our team will review it. If you need help regarding how to setup the repository locally, you can follow the contributing guide.

Fair enough. Regarding the second solution, I've checked it as well and unfortunately there is no good way to make it synchronous. It also requires a class being declared, which considering that we target es5 could result in a bigger bundle. However we could avoid classes with this trickery: I've made a demo to illustrate that.

That's a good point!
Regarding it being asynchronous: it's not a big deal, because our current solution is async as well.
Regarding requiring the class to be declared: in the case of my test code I ended up with something like this:
Build:
var Cmp = /** @class */ (function (_super) {
    __extends(Cmp, _super);
    function Cmp() {
        return _super !== null && _super.apply(this, arguments) || this;
    }
    Cmp.prototype.render = function () {
        var args = [];
        for (var _i = 0; _i < arguments.length; _i++) {
            args[_i] = arguments[_i];
        }
        console.log(args);
        return null;
    };
    return Cmp;
}(react.Component));

And the original code:
class Cmp extends Component<any, any> {
  render(...args: any[]) {
    console.log(args)

    return null
  }
}

The console.log(args) showed a correct length of arguments in react and preact.
I've also noticed one interesting thing - in my case in Preact I've received 3 arguments in render() function, the last argument was our context. I think that it's worth keeping in mind when you will be implementing it.
Thanks!

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixes outside dates movement while hovering

This is with reference to #1172 and #308
In DayPicker.jsx
at line number 201, CalendarDay__outside have default border 0 but we have some border on hovering and CalendarDay__outside have no different style for hover, which moves the date on hovering.
I added property border: 0  on hover for CalendarDay__outside solving the issue.

Coverage remained the same at 84.868% when pulling f4467380d61f242fabfe5b43e930d0ceb57d69e5 on mukuljainx:fix/css into 671c2960625f975715e790538dd044ba2081fb57 on airbnb:master.

@ljharb Hey, I would really appreciate if you can review this.

@majapw yes, I did. Thanks 😃


Data Export - Filenames too long for Windows

Description
I previously created a task to export tables in my database as Json files. The task's "Output" was configured as:

I would run the task at the start of a test session to capture the table content as Json files and created a directory as described above. There would be 1 Json for each table I selected. I would run my tests and then run the task again to produce a second folder with the updated table content.
I could then use my file/directory comparison tool to compare and verify updates.
It has been a few releases since I did that, but now, when I execute the task using Community Edition 23.0.4, I get an error:
Task execution failed

Reason:
Data transfer IO error

And the details show:
Data transfer IO error
  C:\Users\********\AppData\Local\Temp\export-1684263346660-1684263346671-1684263346681-1684263346690-1684263346701-1684263346719-1684263346743-1684263346759-1684263346775-1684263346812-1684263346836-1684263346851-1684263346872-1684263346885-1684263346900-1684263346915-1684263346927-1684263346939-1684263346939.json (The filename, directory name, or volume label syntax is incorrect)
  C:\Users\********\AppData\Local\Temp\export-1684263346660-1684263346671-1684263346681-1684263346690-1684263346701-1684263346719-1684263346743-1684263346759-1684263346775-1684263346812-1684263346836-1684263346851-168426
[logs.zip](https://github.com/dbeaver/dbeaver/files/11491187/logs.zip)
3346872-1684263346885-1684263346900-1684263346915-1684263346927-1684263346939-1684263346939.json (The filename, directory name, or volume label syntax is incorrect)

The files created appear as:

There is a single "export.json", then an "export-1684263346660.json", then "export-1684263346660-1684263346671.json", etc and eventually the file name exceeds Windows 256 character limit and bombs.
DBeaver Version
Community Edition 23.0.4
Operating System
Windows 10 Professional
Database and driver

Database - MySQL 5.7.33
Driver - MySQL Connector Java mysql-connector-java-5.1.44

Steps to reproduce
No response
Additional context
No response

Hello @ErnieZapata,
Make sure you have "file name conflict behavior settings" set to "overwrite":

Please let me know if it solves your issue.

I changed this setting to Overwrite but it made no difference, same result.
I noticed that Write to single file was disabled, but yet, tasks.json showed:

I edited the file and changed the value for "useSingleFIle" to false and got the results I want. A new folder gets created with current date/time, and one Json file for each table is created. Running task again, I see a new folder with Json for each table as expected.
Not sure when this Write to single file was disabled, but the Json value for this does not seem to reflect an unchecked checkbox. As mentioned before, I created this task with an older version of  DBeaver a while back but just have not used it in a while.
I even delete the old task and recreated and see the same behavior for this setting. I have a work around, so I good for now


Please add to the pub.dev readme that 'flutter run' will not be available.

The readme for pub.dev includes the following.

Remove <category android:name="android.intent.category.LAUNCHER" /> from the main activity's <intent-filter>.

At this time, Flutter is unable to flutter run a main activity that LAUNCHER has been removed due to this issue.
https://github.com/flutter/flutter/issues/38965
This issue can be reproduced in the sample app from this repository.
Log after flutter run in sample app:
Resolving dependencies...
  flutter_lints 3.0.2 (4.0.0 available)
  leak_tracker 10.0.0 (10.0.5 available)
  leak_tracker_flutter_testing 2.0.1 (3.0.5 available)
  leak_tracker_testing 2.0.1 (3.0.1 available)
  lints 3.0.0 (4.0.0 available)
  material_color_utilities 0.8.0 (0.11.1 available)
  meta 1.11.0 (1.15.0 available)
  shared_preferences 2.2.2 (2.2.3 available)
  shared_preferences_android 2.2.1 (2.2.2 available)
  shared_preferences_foundation 2.3.5 (2.4.0 available)
  test_api 0.6.1 (0.7.1 available)
  vm_service 13.0.0 (14.2.2 available)
  win32 5.4.0 (5.5.0 available)
Got dependencies!
13 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
package identifier or launch activity not found.
Please check C:\projects\variable_app_icon\example\android\app\src\main\AndroidManifest.xml for errors.
No application found for TargetPlatform.android_x64.
Is your project missing an android\app\src\main\AndroidManifest.xml?
Consider running "flutter create ." to create one.

I noticed that <intent-filter> is only required on the first 'flutter run' after 'flutter clean', and on subsequent flutter run, no error occurs even if LAUNCHER is commented out.
Therefore, I now operate with it commented out and only uncomment it when this error appears.
Can you please add to the readme that because of this issue, removing LAUNCHER will cause an error in the use of flutter run?
Or could you change the Readme from deleting LANUCHER to commenting out, and change to uncomment out only if an error occurs?
(Or run flutter build apk --debug once)
Of course, we can get to this Issue by searching for the error text, but I think it would be more helpful if it were mentioned in the Readme from the beginning!

This is a bug in the flutter_tools . This plugin code has NO error. You can verify it by generating an apk using flutter build apk.
The error occurs while running by flutter run. It only happens when activity-alias is used as an android.intent.category.LAUNCHER instead of an activity. flutter_tools has no logic to handle activity-alias.
And this is the only way to use multiple app icons in Android.
I am working on a PR to fix this.

I will add this in the README.md

Thank you for your prompt reply!
I knew there was someone working on PR, but I didn't recognize you as the same as the author of the library😂.
I wish your PR success!

Thank you for this package @SNNafi
I'm somehow stuck here... I have two icons
AndroidManifest.xml:
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <application
        android:name="${applicationName}">
        <activity-alias
            android:name="appicon.DEFAULT"
            android:enabled="true"
            android:exported="true"
            android:icon="@mipmap/ic_launcher"
            android:label="MYAPP"
            android:targetActivity=".MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity-alias>
        <activity-alias
            android:name="appicon.MYAPP"
            android:enabled="false"
            android:exported="true"
            android:icon="@mipmap/ic_launcher2"
            android:label="MYAPP"
            android:targetActivity=".MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity-alias>
        <activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">
            <!-- Specifies an Android theme to apply to this Activity as soon as
                 the Android process has started. This theme is visible to the user
                 while the Flutter UI initializes. After that, this theme continues
                 to determine the Window background behind the Flutter UI. -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
              />
        </activity>
        <!-- Don't delete the meta-data below.
             This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
        <meta-data
            android:name="flutterEmbedding"
            android:value="2" />
    </application>
    <!-- Required to query activities that can process text, see:
         https://developer.android.com/training/package-visibility?hl=en and
         https://developer.android.com/reference/android/content/Intent#ACTION_PROCESS_TEXT.

         In particular, this is used by the Flutter engine in io.flutter.plugin.text.ProcessTextPlugin. -->
    <queries>
        <intent>
            <action android:name="android.intent.action.PROCESS_TEXT"/>
            <data android:mimeType="text/plain"/>
        </intent>
    </queries>
</manifest>

DEBUG CONSOLE
Launching lib\main.dart on YAL L21 in debug mode...
package identifier or launch activity not found.
Please check C:\flutter apps\myapp\android\app\src\main\AndroidManifest.xml for errors.
No application found for TargetPlatform.android_arm64.
Is your project missing an android\app\src\main\AndroidManifest.xml?
Consider running "flutter create ." to create one.

I have a temporary solution
You can add the following code in the activity
<activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">
            <!-- Specifies an Android theme to apply to this Activity as soon as
                 the Android process has started. This theme is visible to the user
                 while the Flutter UI initializes. After that, this theme continues
                 to determine the Window background behind the Flutter UI. -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
              />
              <!-- <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter> -->
        </activity>

At the initial run. Do not comment  After running. Remark
This completes the development environment run
But this is not perfect. The perfect way still requires the author's PR success


[Bug] Track upstream release of curl for security purposes

Search before asking

[X] I searched in the issues and found nothing similar.

Version
Current main
Minimal reproduce step
From a dry read of https://github.com/apache/pulsar-client-cpp/blob/5c77648d0029c4b11e0e062ab73474368ecc0e87/pkg/apk/Dockerfile#L105, a hardcoded version of curl, currently 7.85.0 per https://github.com/apache/pulsar-client-cpp/blob/5c77648d0029c4b11e0e062ab73474368ecc0e87/dependencies.yaml#L27, will make it into a container image used in the build process.
What did you expect to see?
I'm raising this to your attention due to https://github.com/curl/curl/discussions/12026 in case that's a release that you find necessary to track for security purposes.
What did you see instead?
It appears like using a package manager to use the latest libcurl from an OS vendor will not suffice in this scenario since https://github.com/apache/pulsar-client-cpp/blob/5c77648d0029c4b11e0e062ab73474368ecc0e87/dependencies.yaml#L27 is looked up by a helper script.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Thanks for heads-up. We'll create a new release once the Curl release is available.


CI: Checks service across nodes Tests NodePort BPF Tests with direct routing Tests LoadBalancer Connectivity to endpoint via LB

/home/jenkins/workspace/Cilium-PR-K8s-1.13-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Can not connect to service "http://<IP_ADDRESS>" from outside cluster
Expected command: kubectl exec -n kube-system log-gatherer-rw5kr -- curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 http://<IP_ADDRESS> -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
To succeed, but it failed:
Exitcode: 28
Err: exit status 28
Stdout:
 	 time-> DNS: '0.000018()', Connect: '0.000000',Transfer '0.000000', total '5.001644'
Stderr:
 	 command terminated with exit code 28

/home/jenkins/workspace/Cilium-PR-K8s-1.13-net-next/src/github.com/cilium/cilium/test/k8sT/Services.go:752

ce4f18e1_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_direct_routing_Tests_LoadBalancer_Connectivity_to_endpoint_via_LB.zip
cc @brb

This is a duplicate of https://github.com/cilium/cilium/issues/12511.

This is a duplicate of https://github.com/cilium/cilium/issues/12511.


Add useless code [Jacob Kim]

Add my useless code which compares boolean in a useless way.

@TheJacobKim Congratulation. You won a 2nd prize.
Send a mail to<EMAIL_ADDRESS>with address that you receive the starbucks coupon ( Digit is okay too )


Bidding cancelled with transaction encountering a bad instruction

I tryed to put a bid of 0.01 on a name using Metamask but it didn't went throught.
Etherscan says " Warning! Error encountered during contract execution [Bad instruction] "
link to etherscan
I tryed again and it went alright (- :

I asked @jdetychey to report this here because I suspect the DApp accidentally placed a bid for a name that wasn't quite available yet.

Is there any progress for this issue, I also met this issue with parity


Wikilink is not work for .webp files

I use Material for Mkdocs. And it does well on .md .png .jpg files.
When I tried to insert an .webp image, the building log didn't show anything wrong, but the output site tells me that "xxx.webp is not found"
I have already confirmed that the problem is not caused by spaces in filename.

If it's necessary to use your template to avoid this?

Hello,
I can't repro :

I found the reason. There's another plugin doing the same thing thus it breaks the right link. Only use ezlink and it turned out ok.


[Metadata Policy] scopes or scope claim?

https://bitbucket.org/openid/connect/issues/1456/scopes-metadata-parameter-needs-to-be

This issue is on hold for clarification from Connect A/B WG


PixDiff not resolving path to framework during initialisation

Hi everyone,
I would like to give pix-diff a shot and got the following behaviour:
Part of my protractor.config.js:
`onPrepare: function () {  //configure junit xml report
    var pixDiff = require('pix-diff');
    browser.pixdiff = new pixDiff(
        {
            basePath: 'screenshots/test/',
            width: 1280,
            height: 1024
        }
    );`

I got the following output:
Error: Cannot find module 'D:\SWE\Nitsch\Entwicklung\Hauptprojekt\Entwicklungszweig\Client\EnMS.Angular\EnMS\Frontendtests\framework\jasmine'     at Function.Module._resolveFilename (module.js:339:15)     at Function.Module._load (module.js:290:25)     at Module.require (module.js:367:17)     at require (internal/module.js:20:19)     at Object.<anonymous> (D:\SWE\Nitsch\Entwicklung\Hauptprojekt\Entwicklungszweig\Client\EnMS.Angular\EnMS\Frontendtests\node_modules\pix-diff\index.js:50:13)     at Promise.invokeCallback_ (C:\Program Files\nodejs\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1329:14)     at TaskQueue.execute_ (C:\Program Files\nodejs\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2790:14)     at TaskQueue.executeNext_ (C:\Program Files\nodejs\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2773:21)     at C:\Program Files\nodejs\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2652:27     at C:\Program Files\nodejs\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:639:7 [launcher] Process exited with error code 1
It seems that pix-diff cannot resolve the path to the testing framework.
Any suggestions how to handle that problem?
Thank you very much in advance
Akki

Hi Akki,
Couple questions;

What version of protractor are you using?
What framework is protractor using?

Hi Koola,
i'm using protractor version 3.2.2 with jasmine2 as framework.
Regards
Akki

I'm suspecting that it's not got the absolute path to the current directory.
Please try the folowing:

In Protractor config, make sure browser.framework: jasmine2 is set
Inside index.js on line 50, replace with require(path.resolve(__dirname, 'framework', data.framework));.

That solved the problem - thank you very much.

Thanks for confirming. I'll push the fix in the next release.

This fixed the issue for me as well... thanks! Also, you're missing a comma in index.js on line 44 :)

At the risk of sounding ungrateful for pix-diff, an update will allow me to stop manually fixing this on every npm install ;)

This is fixed and release on v1.0.10

Awesome. Thanks a bunch!


BF: schema - do not announce that CHANGES is required

Current wording at
https://bids-specification.readthedocs.io/en/stable/03-modality-agnostic-files.html#changes
### `CHANGES`

Version history of the dataset (describing changes, updates and corrections) MAY
be provided in the form of a `CHANGES` text file. This file MUST follow the
[CPAN Changelog convention](https://metacpan.org/pod/release/HAARG/CPAN-Changes-0.400002/lib/CPAN/Changes/Spec.pod).
The `CHANGES` file MUST be either in ASCII or UTF-8 encoding.

so it MAY be provided, not MUST.  Alerted to by @satra in
https://github.com/dandi/dandi-cli/issues/1055#issuecomment-1189007674

closes #1127 ?

closes #1127 ?

yes indeed apparently, thank you!

errors are due to #1000 which I merged a couple of minutes ago, I think

oh - schemacode_ci is apparently red!  need to discover now if I broke it or not.  It is that day -- file https://github.com/bids-standard/bids-specification/issues/1152 with my intention.

re CI failure -- not me -- recent commit 130aa76 in master was already failing them. Here is what I see from the con/tinuous dumps with regular grep on sample failing test :
datalad@smaug:/mnt/datasets/datalad/ci/bids-specification/2022/07$ git grep 'FAILED.*test_make_glossary' | grep 3.7
19/pr/1143/b82ae52/github-schemacode_ci-656-failed/1_ubuntu-latest with Python 3.7.txt:2022-07-19T14:37:26.4504200Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary
19/pr/1143/b82ae52/github-schemacode_ci-656-failed/ubuntu-latest with Python 3.7/6_Run tests.txt:2022-07-19T14:37:26.4504197Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary
19/pr/1151/246b35f/github-schemacode_ci-657-failed/1_ubuntu-latest with Python 3.7.txt:2022-07-19T14:47:18.4379692Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary
19/pr/1151/246b35f/github-schemacode_ci-657-failed/ubuntu-latest with Python 3.7/6_Run tests.txt:2022-07-19T14:47:18.4379674Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary
19/push/master/130aa76/github-schemacode_ci-655-failed/1_ubuntu-latest with Python 3.7.txt:2022-07-19T14:21:52.7698770Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary
19/push/master/130aa76/github-schemacode_ci-655-failed/ubuntu-latest with Python 3.7/6_Run tests.txt:2022-07-19T14:21:52.7698751Z FAILED tools/schemacode/bidsschematools/tests/test_render.py::test_make_glossary

and update of this page brings me in agreement with @sappelhoff on that in https://github.com/bids-standard/bids-specification/pull/1151#issuecomment-1189167838

what is the policy on such trivial fixes - do they also need to stage for 5 days or so?


Upgrade test container for Azure to fix test on main branch

Description
will avoid this kind of test to afail https://ci-builds.apache.org/job/Camel/job/Camel Core (Build and test)/job/main/433/testReport/junit/org.apache.camel.component.azure.storage.blob.integration/BlobChangeFeedOperationsIT/BuildAndTest___Matrix___JDK_NAME____jdk_21_latest___PLATFORM____ubuntu_avx____Test______/
with this kind of error:
Status code 400, "<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
  InvalidHeaderValue
  <Message>The API version 2024-11-04 is not supported by Azurite. Please upgrade Azurite to latest version and retry. If you are using Azurite in Visual Studio, please check you have installed latest Visual Studio patch. Azurite command line parameter "--skipApiVersionCheck" or Visual Studio Code configuration "Skip Api Version Check" can skip this error.
RequestId:c17dab06-33dd-42e7-a733-150e56489127
Time:2024-10-03T10:12:08.772Z</Message>
</Error>"

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

I guess it was related to this upgrade of azure bom https://github.com/apache/camel/pull/15778 but the component test did not caught the problem

/component-test azure

and now the component-test is failing with the previous error. Something weird is happening with the check


[Bug] Windows CI is failing (again)

e.g. https://github.com/fzyzcjy/flutter_rust_bridge/runs/5312283556?check_suite_focus=true
There does not seem to be related code change that makes CI fail...

/cc @Desdaemon (#325) @SecondFlight (#324)

This doesn't look related to #324/#325. At first glance, I wonder if it's a tooling or dependency bug. The error doesn't look familiar to me, though I haven't written many Dart unit tests.

@SecondFlight I am also considering that. Maybe GitHub upgraded some dependencies, making us fail?

LINK : fatal error LNK1104: cannot open file '..\Debug\flutter_rust_bridge_example.dll.lib'
My guess is that something changed with MSVC build tools recently, we can try using the old windows-2019 environment instead. Might be relevant to Corrosion as well.

Good idea!


WIP: Convert Hadoop Metrics to Micrometer

Fixes #1134
Converting from the use of hadoop metrics to micrometer metrics.

Superseded by #2188.


Can't preview RTF file

Type: Bug
NPE version: 4.4.3
Installed from: Windows Store
When I try to preview the ThirdPartyNotices.rtf file from the Microsoft.Net.Compilers 2.8.2 package, I get the following exception:
*** The plugin that registers to read this file type fails to read the content of this file. ***
System.NotSupportedException: This operation is not supported.
   at System.IO.Compression.DeflateStream.get_Length()
   at PackageExplorer.RtfFileViewer.GetView(String extension, Stream stream)
   at PackageExplorerViewModel.ViewContentCommand.ShowFile(PackageFile file)

I don't know anything about this code, but the obvious workaround would be copy the DeflateStream into a MemoryStream and use that.

Yes, I did exactly this for the avalon editor for file editing https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/pull/330 . Do you want to send a PR? If not I can do it tomorrow.


Update bare-metal-faq.md

Updated to reflect the vendor support hours for hardware failures, as well as removing any indication that we actively monitor customer bare metal servers.  These were made in the "How is hardware support and replacement handled for Bare Metal servers?"  This was related to https://t3n.zendesk.com/agent/tickets/1607467

Who can merge this request?

Can someone review and merge this change?


Songs with extended ascii characters fail to upload

i have a lot of music with titles that have stylized ascii characters and they cause the upload to fail. If it fails on the first track, it creates an album that has nothing for a track list that can't be deleted unless you delete it manually in sql.
Let me know what logs and information you would need to troubleshoot this issue,
Thanks

Very sorry for the late reply!!
Im assuming the issue occurs on the backend, as the frontend is not concerned with metadata.
Let me check the code related to metadata parsing, and i will get back to you.

Ok so i havent identified any obvious cause, but the logs you are looking for exist in two places:
first of all, replicate the problem in your browser with the devtools open, and find the error message in the api response, it is likely a 500 status code.
It should contain the literal error text returned by whatever failed in the backend. This may or may not be helpful depending on how specific that error message is.
The second is to check your dotify log on the server, likely via journalctl if you set dotify up as a systemd service. They should all be prefixed with "uploadAudioFiles".
Somehow i messed up and wrote some of the error logs as debug logs. I will have to fix this later (maybe tomorrow if i remember).
Debug logs are currently disabled, but you may enable them yourself by changing the log level (from info to debug) in the source code and compiling a new binary. i should add a variable to let the user configure this.

also, just to confirm: by extended ASCII do you mean unicode? utf-8?


Added several translations.

Note that "State/Province" is not consistently translated (needs overall review / agreement). Same for "Item".

Thank you for your contributions.


Is it possible to sync with iCUE/Aura?

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
It will be great if alienfx-tools can receive chroma effect from other apps such as Wallpaper Engine. So the chroma effect can be unified between my laptop and razer mouse.
System (please complete the following information):

Model: M17R5
Model details: per-key rgb keyboard
OS: Windows 11

Additional context
Add any other context or screenshots about the feature request here.

I think about sync some other effect systems, but, sorry, not about Razer - i hate them. Logitech, maybe.
The main issue is most of them (Asus, MSI, Logitech) have quite limited control to the lights, slow and without full range of light selection and effects.
For now, i have Dell LightFX SDK emulation, so any LightFX-supported game or app can use my engine to control the lights. Check project readme (LightFX.Dll) for details.


create julianum.txt

Official Website: https://julianum.de/
Mail Domain: julianum.eu

this is for de Domain

@BitClientDE Pull request merged. Thank you!


v_args(inline=True) does not apply to derivatives of derived Transformers

Hi there,
What is the expected behaviour of v_args(inline=True) when applied to inheritance chains from lark.visitors.Transformer?
Minimum example with a really simple grammar:
grammar = """
mul: symbol "*" symbol
symbol: INT

%import common.INT
%import common.WS
%ignore WS
"""

MyTx1 derives from lark.visitors.Transformer using v_args decorator
@v_args(inline=True)
class MyTx1(Transformer):

    def mul(self, a, b):
        return "({a} times {b})".format(a=a, b=b)

    def symbol(self, s):
        return s

MyTx2 derives from MyTx1 overriding the mul() method:
@v_args(inline=True)
class MyTx2(MyTx1):

    def mul(self, a, b):
        return "({a} wibbles {b})".format(a=a, b=b)

Then, when run on a simple phrase:
parser = Lark(grammar, start='mul')
tree = parser.parse("1 * 2")
res1 = MyTx1().transform(tree) #  (1 times 2) CORRECT
res2 = MyTx2().transform(tree) # VisitError: "mul() missing 1 required positional argument 'b'"

It seems that the v_args(inline=True) isn't inlining arguments in the derived class.  Is this expected behaviour?
Cheers,
Chris
Edit: Python 3.6.6 (Anaconda), Lark 0.7.0 from pip.

Nice find, it was a tricky edge case.
I pushed a fix to master which hopefully will solve it, and won't mess other things up. Let me know if it works.

Heh, nice fix.  Works like a charm.  Many thanks!  Will the fix be pushed to pip in the near future?  What's the timescale?

I will probably make a minor release sometime this week. I just completely rewrote the standalone generator, so I want to make sure it's stable.


Modified Error Text

Added an exclamatory mark (!) instead of full stop(.)

Give a squash commit.
Do not raise multiple PRs for the same issue unless required by the maintainers.


is this class support php version 5.6

Hi,
I am thinking to use this class for my old built website code PHP MySQL based website
its developed in PHP version 5.6
can we use this EasyDB as MySQL wrapper class?
please advise.
Thanks
Imran

The v1.x branch supports PHP 5.6, yes. https://github.com/paragonie/easydb/blob/v1.x-legacy/composer.json#L46


Workflows: alternative task execution mechanism

(this is the continuation of discussion of Workflow from #26)
@patriksvensson

I'm sorry if I sound negative, but it's so easy to add stuff and so difficult to remove them.

That's so true, and you sound pragmatic  :smile:

I can see a benefit from them if they respect task dependencies and criteria, which would make them a new kind of mechanism for task execution.

I also like the idea of workflows (so much, that I definitely going to implement them as POC at least in my fork :smile: ), but if they would respect Task's dependencies and conditions then there would be almost to difference to Targets (which is currently the only execution model).
The unique feature of the workflows (as I see them) is to allow user to declare dependencies and conditions on level of workflow itself, leaving tasks plain, simple and reusable in other workflows.

This way we could accomplish what you propose simply by not specifying dependencies or criteria for a task.

Looks like this is the way to go.
What if Workflow would work with existing Tasks, but will throw something like InvalidOperationException if it will detect any conditions or dependencies declared on them? This model would let us tick 2 checkboxes:

Force user to use Workflow-style execution model (if his intention is to use Workflow)
Do not introduce breaking changes to main execution model
Do not introduce duplicate code (Jobs etc..)

This way, workflow model will be optional. And it is up to user to decide whether to stick with main model, or alternative.
What you think?

@os-alan any PoC done you want feedback on? Otherwise I'm going to go ahead and close this issue.

@devlead No, unfortunately. Agree on closing the issue.


[sticky] JS Bin database server is down

I got an email from AWS this morning saying the db machine was "Retirement Notification] Amazon EC2 Instance scheduled for retirement."
It's the largest machine in the stack that runs JS Bin, and I'm trying to get a new machine running again and reconnected to the data drive.
Until then and further notice, JS Bin won't load.
The only alternative is to use v5 (directions here) and save locally.

Came back up this morning. See Twitter for the lolz 😢