Support MPEG2?

Could this library decoding MPEG2 streaming video? Because I need better quality maybe like 720p.

No. However MPEG2 dosen't provide better encoding quality or compression than MPEG1. It just has some additional features over MPEG1 (interlaced video; higher bitrate profiles (which we don't care for in jsmpeg), etc.).
jsmpeg 720p benchmark: http://phoboslab.org/files/jsmpeg/benchmark-720p.html (runs in realtime on an iPhone5).

Thanks for your fast reply! I already tried to upgrade bit rate and resolution on my project and it gave me very good result. :)


3DS Max, Moto, Unity X3D exporting 'e' exponent in X3D file numbers

X3D files exported by 3d modeling tools 3DS Max and Moto 3d, plus Unity's X3D exporter saving some numbers with 'e' or 'E' inside the number to represent an exponent.
For example, a number such as '.0000478' might be exported as '4.78e-005'.  Or '3,920,000,000' might be exported as '3.92E09', which is 3.92 * 10 to the 9th power.
Seeing this issues in interpolator keyValue for animation, and transform values.  Likely, it can show up anywhere.
Will require changes to parsing floating point numbers and maybe integers in X3Dobject.java.

Just some background on the issue, we use Java's SAX parser to parse X3D..
Java SAX parser is one of two parsers in Java imported from javax.xml.parsers.SAXParser
The parser will return floating point or integer numbers when requested, for example, to parse a vertex, we ask SAX to return 3 floating point numbers.
The problem is some of the 3d modeling tools will save exponentially large or small number with the 'e' format described above.
Unfortunately, the SAX parser doesn't parse the exponent value.  Instead, SAX will look at a number such as '4.78e-005' as two number: '4.78' and '-005' or just '-5'.

Fix in PR https://github.com/Samsung/GearVRf/pull/1670


feat: PX-3912 scroll to the partner header on tab change

This PR ignores default scroll behavior for the partner profile page and adds scroll to the partner header on tab change.
JIRA - https://artsyproduct.atlassian.net/browse/PX-3912

Needs a rebase, otherwise 👍 from me.


ARROW-5283: [C++][Plasma] Erase object id in client when abort object

@wesm @pcmoritz Please help to review this.

@shengjun1985 thank you for your contribution. I am not familiar enough with this particular code path to sign off on the change, @pcmoritz can you review?

@zhijunfu Have you had a chance to see if the Ray unit tests run with this? The change looks good to me, but we should test if it causes any problems before merging :)

Codecov Report

Merging #4272 into master will increase coverage by 0.73%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #4272      +/-   ##
=========================================
+ Coverage   88.46%   89.2%   +0.73%
=========================================
  Files         773     632     -141
  Lines       95599   86503    -9096
  Branches     1251       0    -1251
=========================================
- Hits        84573   77164    -7409
+ Misses      10790    9339    -1451
+ Partials      236       0     -236

Impacted Files
Coverage Δ

cpp/src/plasma/test/client_tests.cc
100% <100%> (ø)
:arrow_up:

cpp/src/plasma/store.cc
91.13% <100%> (-0.15%)
:arrow_down:

cpp/src/arrow/vendored/datetime/date.h
30.62% <0%> (-26.68%)
:arrow_down:

cpp/src/arrow/scalar.cc
57.89% <0%> (-15.44%)
:arrow_down:

cpp/src/arrow/type_traits.h
85.71% <0%> (-7.25%)
:arrow_down:

cpp/src/arrow/array/builder_nested.cc
95% <0%> (-3.95%)
:arrow_down:

cpp/src/arrow/array/builder_dict.h
81.48% <0%> (-2.73%)
:arrow_down:

cpp/src/arrow/scalar.h
88.23% <0%> (-2.68%)
:arrow_down:

cpp/src/arrow/array/builder_base.h
92.5% <0%> (-2.38%)
:arrow_down:

cpp/src/gandiva/precompiled/string_ops.cc
61.53% <0%> (-1.96%)
:arrow_down:

... and 216 more

Continue to review full report at Codecov.

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

@pcmoritz I checked client_tests.cc in plasma has already covered the Abort() and Disconnect() which are touched by this change, think it's probably good to go? :)

@zhijunfu Sorry for the delay, I'm in the process of running it through the ray test suite first to make sure nothing breatks :)


feat(documentation): add form-select stories

Preview environments are getting posted here, as soon as they are ready!


remove unsafe text template usage

/gcbrun

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 12 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 57.913%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

deploy/deploy.go
8
12
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
2320

Relevant Lines:
4006

💛  - Coveralls

/gcbrun

/gcbrun


More "Failed to create temporary directory."

I have run into the same issue but using RHEL ubi and podman driver.
I am using rotless podman with molecule version 4.0.1
$ molecule --version
molecule 4.0.1 using python 3.8
ansible:2.13.1
delegated:4.0.1 from molecule
podman:2.0.2 from molecule_podman requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
--
Any tips on how to solve the issue would be appreciated
Discussed in https://github.com/ansible-community/molecule/discussions/3092

Originally posted by lgadalla-impinj April  8, 2021
I've been struggling with the converge issue where Ansible cannot gather facts, allegedly due to not having permissions to write to the temporary directory:
TASK [Gathering Facts] *********************************************************
fatal: [instance]: UNREACHABLE! => changed=false
  msg: 'Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in "/tmp", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p "` echo /tmp `"&& mkdir "` echo /tmp/ansible-tmp-1617853604.764122-263554-181361534476501 `" && echo ansible-tmp-1617853604.764122-263554-181361534476501="` echo /tmp/ansible-tmp-1617853604.764122-263554-181361534476501 `" ), exited with result 1'
  unreachable: true

The environment is as follows:
$ molecule --version
molecule 3.2.2 using python 3.8
    ansible:2.10.5
    delegated:3.2.2 from molecule
    docker:0.3.3 from molecule_docker

What is interesting is that when I run with two closely related OS Docker images, CentOS 7 and RHEL 7 in this case, the problem does not occur with CentOS 7 but does occur with RHEL 7.  I've left remote_tmp set to /tmp but that does not seem to have any effect.
I'm mostly looking for any clues or guidance on how to dig further down and debug this issue.

iirc facts gathering is disabled on create, so you may want to:

run molecule create to create test containers
run molecule login to connect to the test containers
check /tmp rights to see if something wrong
if nothing detected, run molecule converge or molecule converge -vvvv to get the error and then log into the failing container with molecule login. Look at the logs in order to check if something interesting is in them.

I can't say more without having experienced the issue locally. Look for similar issues with ansible since it may not be a molecule specific error.
At worse, you may try to workaround things by mounting /tmp with a tmpfs:
platforms:
- name: instance
  image: myimage
  tmpfs:
  - /tmp

@apatard I'm having a similar  issue using wsl2 on windows.
molecule create is able to create the instance but when I execute molecule converge it fails with the error:
fatal: [instance]: FAILED! => {     "msg": "failed to resolve remote temporary directory from ansible-tmp-1670169152.6252987-3617-243105984205172: ( umask 77 && mkdir -p "echo ~/.ansible/tmp"&& mkdir "echo ~/.ansible/tmp/ansible-tmp-1670169152.6252987-3617-243105984205172" && echo ansible-tmp-1670169152.6252987-3617-243105984205172="echo ~/.ansible/tmp/ansible-tmp-1670169152.6252987-3617-243105984205172" ) returned empty string" }
I'm able to login into the container instance with molecule login and I'm able to see the directories that are created:
root@instance:~/.ansible/tmp# ls ansible-tmp-1670168194.9145443-21993-117827900798   ansible-tmp-1670169152.6252987-3617-243105984205172 ansible-tmp-1670168967.0483384-3291-64050985022207  ansible-tmp-1670169174.0279183-3801-267177116955287
The directories are empty though.
How to proceed from here?
molecule 4.0.3 using python 3.10
ansible:2.13.4
delegated:4.0.3 from molecule
docker:2.1.0 from molecule_docker requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0
cat /etc/issue
Ubuntu 22.04.1 LTS \n \l
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.819

This appears to happen using podman and docker drivers with a similar failure mode: #3818

I have similar issue on Mac (but also on Windows it's the same) when running molecule inside container (with Docker Desktop). After spending a lot of time trying downgrading versions I realized that the cause was to be found elsewhere and found it in Docker Desktop, in fact natively on Mac (or on the Windows WSL) it worked perfectly.
At first, the reasoning was not clear to me but after reading your kernel intuition I realized it could be something like this. In fact months ago everything works and at some point it stopped and returning the error "failed to resolve remote temporary directory ... returned empty string"
From here I found out that since Docker Desktop 4.13 they upgraded the kernel from 5.10.x to 5.15.x and this is the root cause. Downgrading Docker Desktop to 4.12 on both Mac and Windows everything started working again. I think this problem also exists on a Linux distribution with a kernel 5.15.x, I can't tell if it's an incompatibility between ansible/molecule and the kernel. I hope someone fix this issue.

I have similar issue on Mac (but also on Windows it's the same) when running molecule inside container (with Docker Desktop). After spending a lot of time trying downgrading versions I realized that the cause was to be found elsewhere and found it in Docker Desktop, in fact natively on Mac (or on the Windows WSL) it worked perfectly.
At first, the reasoning was not clear to me but after reading some kernel intuition I realized it could be something like this. In fact months ago everything works and at some point it stopped and returning the error "failed to resolve remote temporary directory ... returned empty string"
From here I found out that since Docker Desktop 4.13 they upgraded the kernel from 5.10.x to 5.15.x and this is the root cause. Downgrading Docker Desktop to 4.12 on both Mac and Windows everything started working again. I think this problem also exists on a Linux distribution with a kernel 5.15.x, I can't tell if it's an incompatibility between ansible/molecule and the kernel. I hope someone fix this issue.


Eventing Multiple Providers Declarations

Although today we only offer support for Google PubSub and logging eventing is on the way with James' work, we were unable to declare different providers for in / out topics. It would be desirable (and expected) that the user would be able to declare different transports for entry and exit.
Using the PingPong project as an example we have the following proto file:
service PingPongService {

  rpc Ping(PongSent) returns (PingSent) {
    option (.cloudstate.eventing) = {
      out: "pings",
    };
  }

  rpc Pong(PingSent) returns (PongSent) {
    option (.cloudstate.eventing) = {
      out: "pongs",
    };
  }

  rpc SeenPong(PongSent) returns (google.protobuf.Empty) {
    option (.cloudstate.eventing) = {
      in: "pongs",
    };
  }

  rpc SeenPing(PingSent) returns (google.protobuf.Empty) {
    option (.cloudstate.eventing) = {
      in: "pings",
    };
  }

  rpc Report(GetReport) returns (PingPongStats) {
    option (google.api.http) = {
          get: "/pingpong/{id}"
    };
  }

I would like to be able to set the in (pings) topic to use a provider such as Google PubSub and the out (pongs) topic to use another supported technology such as MQTT
I believe that by making this separation of transport mechanisms, protocol and or service providers we will be able to cover a wide range of integration options, making our purpose of making Serveless a common place for general programming to get even closer.
What do you think @jroper @viktorklang @pvlugter ?

Yes, I definitely agree that different providers should be supported. The big question for me is at what level should it be configured? The two possibilities I see are either make it a descriptor concern, or deployment concern.
If we make it a descriptor concern, that would mean putting in the gRPC descriptor a provider field so you can select which provider to send/receive this topic from. If we make it a deployment concern, then the gRPC descriptor will just have a topic, but then in the deployment descriptor, we would have a way to map that virtual topic name to a topic on a particular provider, whether that be pubsub, kafka, mqtt, whatever. This configuration might go in the StatefulService descriptor, or perhaps it would be namespace wide and we'd have some sort of Topic descriptor that would map a given topic name to a provider/queue/topic/subscription/whatever.
I think I prefer making it a deployment concern.

@jroper I think that definitely the gRPC descriptor should be as clean as possible and therefore we should do this at the deployment level, either in the StatefulService descriptor or via ConfigMap. I would prefer the approach via ConfigMap

I like the way we currently declare topics in the gRPC descriptor. I also think that delegating the mapping of the providers / protocols for the deployment is better because it does not imply the recompilation of the application in cases where the protocols / providers of a user role are changed later even when none of the business logic has been changed and it is just an infrastructure issue


Supporting auto-generation of CA issuer keypair

#79 adds a basic CA issuer that reads a signing keypair from a Secret in the Kubernetes API server in order to issue certificates.
For convenience, it may be desirable to support an 'automatically generate a signing keypair' mode.

ref #85 #84

Instead of adding a 'generate CA' field to the Issuer, I think we should look at adding a selfsigned certificate issuer and adding an IsCA field to the Certificate resource type (as described in #85 #84)

Closing in favour of #84


Update surfWireContour.jl

You need to return the fig from the expression here, otherwise if one uses this script in the REPL, it won't actually show the plot.

it depends, in the repl and GLMakie you just update the fig, however if you are in notebooks then it doesn't show. A lot of my script don't have the last call, fig. So, probably is best to updated them all to the same pattern. I will do that.

This didn’t display properly for me in the repl with GLMakie until I added the return value.


refactor: part 1

First of many refactoring efforts affecting various parts of the codebase (CLI/proxying/test suites) to decouple responsibilities, improve maintainability, and add some long requested features.
Those efforts will be cut down into smaller pieces at a time, I hope not too exceeding in size.

Nuke some constants from constants.lua (when not affecting too many other parts of the codebase, otherwise the ones left will be nuked in future refactors). Relevant: http://thecodelesscode.com/case/178
Introduce meta.lua, holding package infos (name and version number).
Introduce a _KONG global variable. Such a variable can be used to check or retrieve the current version of Kong. For example in the future, one might want to add a check to his or her plugin to ensure a specific version of Kong.
Better luacheck options, embedded in the Makefile.
Cleanup rockspec (duplicated entries for Admin API).
New, cleaner rockspec tests.
Refactor /status endpoint to use ngx.var variables from ngx_http_stub_status_module
Started ordering tests (by filenames) so the test suites can somehow run from lower level components up to the higher ones.
Isolate parse_params API helper for easy unit testing.
Introduce penlight to slowly replace all of our custom utils and other small modules like stringy (the goal in those refacros will be to lower by a great deal the number of dependencies)
Removed the ability to get a default config from the Luarocks config directory since we know have an embedded default configuration in config_defaults.lua.

Coverage increased (+5.4%) to 64.82% when pulling c4f4d77c9c0e3115a56c5fdb7364afd98a92c0b9 on refactor/nuke-constants into efff1484678ed0476be8655ef11479cd2f80e842 on next.


Support ARM64 Builds

Hey there, your tool looks really neat!
I was looking forward to testing it on a Windows 10 ARM64 image with a raspberry pi, but the tool says it only supports 64Bit versions of windows, I'd love to see ARM64 support as well.
Thanks!

I have been slowly working on an ARM build but it is not a top priority. I have been using the Lenovo Yoga C630 WOS and Galaxy Book 2 with Visual Studio and C++ compilers (as well as the UWP Microsoft tools). I do create custom ROMs and ARM builds on XDA-Developers for multiple devices and have for many years now so it's not foreign territory; however, it would not be possible to just tweak the current script to work on ARM devices. The reasons for this are abundant and technical but something will be available in the near future.

Let me know if there's anything I can do to hep or test!

Any update on this @DrEmpiricism  ? The full Win10 Pro ARM64 is too heavy on my Lumia 950XL and it would be cool to shrink it a bit and tweak it.


Make Sponsor Collection View not Trash

It currently looks bad, somebody fix it

Steps in the right direction?

I'm thinking maybe the borders could be circles. Or instead of borders each one could be sitting on a solid line. Or maybe the borders need to be thicker and darker. One problem is that it isn't immediately apparent they are clickable, I think

I'm digging the change, definitely in the right direction. Maybe a really subtle drop shadow could help with knowing its clickable?

Ah yeah good idea lemme see

Shadows are good

Definitely looks much better. Will look even better when we get actual logo images


Add more static checks

🥅 Goal
Have more static checks to make sure that the code quality remains high.
🛠 Solution
Enable more static analysis tools that are run as part of the pre-commit and then later on as part of the code quality check in CI/CD.
🏫 Testing
I have run pre-commit run -a and I have fixed all the problems that have been found.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3d99d11). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage        ?   61.73%
=======================================
  Files           ?        9
  Lines           ?      891
  Branches        ?        0
=======================================
  Hits            ?      550
  Misses          ?      289
  Partials        ?       52


RPM packages doesn't create /var/log/influxdb directory

After installing the latest RPM package on my Fedora system the influxdb service cannot be started because /var/log/influxdb hasn't been created during the installation.
"mkdir /var/log/influxdb && chown influxdb /var/log/influxdb" fixes this and after that I can start the service successfully.

This may have been fixed already, as /var/log/influxdb is a part of the nightlies:
rpm -qpl influxdb-nightly.x86_64.rpm
/etc/influxdb/influxdb.conf
/etc/logrotate.d/influxdb
/usr/bin/influx
/usr/bin/influx_inspect
/usr/bin/influx_stress
/usr/bin/influx_tsm
/usr/bin/influxd
/usr/lib/influxdb/scripts/influxdb.service
/usr/lib/influxdb/scripts/init.sh
/var/lib/influxdb
/var/log/influxdb


about lmdb compression

there is no compression option in config file with lmdb
how to use snappy for lmdb?

As far as I remember LMDB doesn't have support for compression.

the only way is compress key/value first before puting them into lmdb.


Fix GridMap Bug#16524 -unable to delete MeshTile on MacBook using TouchPad

Fixes #16524

I don't know if outright remove the feature is the right fix (if it is, the code should be deleted, not commented out).
CC @poke1024 who implemented this in #12573.

It's not much of a feature in my opinion, not only does it break ability to delete a MeshTile, when you press shift and move touchpad the floor jumps up and down in large unpredictable amounts. I only have a MacBook so can't test other os'.

@ordigdug  You're right, it's really broken.
We could indeed remove this functionality, I'm not sure how often you want to move that grid in that way. If not, I've prepared an alternative fix in https://github.com/godotengine/godot/pull/17111:

only trigger the grid mesh move functionality with alt+shift or alt+command (was: shift or command) so no interference with other functionality happens
fix the unpredictable movements of the panning in this case, so if you now press alt+shift and pan, you can move the grid vertically in a predictable way

@poke1024 Your alternative fix works well.
@akien-mga Can you please reject my pull request and merge #17111 ?


Added search endpoint for locations near a coordinate

location search endpoint added as requested in #15

Travis build fails because
/Users/travis/build/shyambhat/InstagramKit/InstagramKit/Engine/InstagramEngine.m:28:9: fatal error: 'InstagramLocation.h' file not found
#import "InstagramLocation.h"
Xcode finds it just fine in the models directory

Hey @adamjuhasz, it would be great if you could implement helpers for the other two endpoints ( https://instagram.com/developer/endpoints/locations/ ) for me to include this in the forthcoming pod version release this week. Thanks for the contribution. Cheers.

No worries, I'll get that out. Also trying to get Travis to not fail the repository

All endpoints added and tested

Thanks! Merged in develop branch.


Add a flag to enable grpc.

This is needed to get protoc-gen-go to output grpc code.

This will need a bit of thought. You're right that this is the required mechanism on the CodeGeneratorRequest edge, but I'm not sure I want to bake this in in this form. The specific plugins=grpc value only works with protoc-gen-go, and gotoc is trying to be agnostic to the generated language.
protoc handles this by overloading the --go_out flag. I'm not keen to follow that precedence. Maybe this should be a --params flag instead?

I see your point. It does seem odd that protoc specifies plugins in the output flag value. My original solution of having a "-grpc" flag also doesn't seem quite right because we may want to specify additional plugins in the future.
I like your idea of "-params" because it allows us to specify additional plugins in the future without adding additional flags. I updated the pull request to use "-params".
No rush on this. This is an API change of sorts. Hard to change later.

I kept looking at things in an overly-specific way. "-grpc", then "plugins=". Passing the raw parameters does seem like the best way to go. Thanks!
Updated the pull request.

Merged in 0071f33. Thanks!


Fix connection leak in JDBC waitUntilContainerStarted

Only the Statement was auto-closed, but not the Connection against which the Statement was created.
Aside from being a resource leak, this can cause database rename transactions to fail due to the presence of a lingering idle session.

For reference, I think the root cause was #3015.

Thanks a lot! 👍


remove r-nightly-packages from build table

Removed r-nightly-packages from build table. I have kept it in the Error Logs because that history could conceivably be useful.

@assignUser - just pinging this for a review


Explicitly depend on automation-client

Otherwise IntelliJ doesn't offer to import things like RemoteRepoRef

out of date


windows runtime installler  copies wrong file to vulkan-1.dll sometimes

In windows/system32,

copy vulkan-l.dll to vulkan-1A.dll
uinstall runtime
install a newer version of the runtime
will see vulkan-1.dll is a copy of vulkan-1A.dll instead of the newer vulkan-1.dll from the newer runtime

This bug had been fixed. The next Vulkan SDK release will include a fix for this bug.


Mojave compatibility

I would like to know if there is a way to make it work under macOS Mojave ?
Thank you

I have no way of testing on older versions of macOS so I cannot help with this. Keeping it open if somebody else wants to contrtibute.


Common code refactoring

Extracting common init logic from OBAApplicationDelegate into a separate class.
Extensions are not allowed to reference the app shared app delegate, so this is a step to get extension support with common init.
Prep for #322

Generally looks alright. Couple things: please rename instance to sharedApplication and clarify the comment on the start method. I'll have more feedback later today. Thanks!

Sounds good.  I'm not partial to naming, so will rename to whatever ya all want :)

Looks :+1: modulo the feedback above. Let me know when you're ready for another peek. Thanks!

Feedback addressed.

@beliyd once you've addressed @barbeau's feedback, I'll merge the PR.

Will update tmrw and fix the retain cycle.  Could not get to it today.

Sounds good, thank you!
Sent from my iPhone

On May 30, 2015, at 1:32 PM, Dima Belov<EMAIL_ADDRESS>wrote:
Will update tmrw and fix the retain cycle. Could not get to it today.
—
Reply to this email directly or view it on GitHub.

btw: git shortlog -sn -- OBAApplicationDelegate.m  Might be useful for future stuff.

@beliyd have you addressed @barbeau's feedback?

@aaronbrethorst just pushed changes discussed, added copyright to the new file added.   I won't have time to add @copyright to all modified files tonight though... I can do that tomorrow if need be.. sorry for the delay, been a crazy couple days here.

@beliyd all good. I'll merge as soon as Travis comes back green, and update the (c)'s when you have time. thanks again!

@aaronbrethorst thanks.  I'll add a note to myself to do it for next PR in this iteration.   Next weekend :)


Cant enable react-native-tab-view in my app

Current behaviour
My brand new react-native app crashes when i introduced react-native-tab-view
Expected behaviour
I wish to use this library without any problems, but i cant get around this error.
Screenshots (if applicable)

What have you tried
I have tried literallly everything
Your Environment

software
version

ios

react-native
0.58.5

react-native-tab-view
latest

react-native-gesture-handler
latest

react-native-reanimated
latest

try react-native start --reset-cache

Didnt fix it. Now i m getting this:

And i have succesfully linked everything

@kobimilan995 have you reinstalled pods and everything accordingly? from your error it looks like reanimated isn't linked


Create a Python based XSLT translator

https://stackoverflow.com/questions/20820301/xsl-transform-on-text-to-xml-with-unparsed-text-need-more-depth
https://medium.com/@deboralewis007/a-guide-to-filter-xml-using-xslt-in-python-e8fae05e35fe
https://stackoverflow.com/questions/15974377/parse-text-file-with-xslt

lxml does not appear to support XSLT 2.0, which is needed for this trick: https://stackoverflow.com/questions/46785786/how-to-convert-xml-into-html-using-xslt-2-transformation-from-python3#comment80518546_46785786

For the existing sfm to xml lists transformation work we have a working windows only solution.


Defect: Object.merge does not merge deep object structures

I don't know if it is a bug or a feature when it is a feature it should be documented. Following example:
Object.merge({ foo : { bar : 'World' }, foo : 'bar'}, { foo : { foobar : 'Hello' }});

Expected result:
{ foo : { bar : 'World', foobar : 'Hello'}}

Actual result:
{ foo : { foobar : 'Hello' } }

Indeed you're right... Strange too because I went to quite some lengths making sure clone preserved the structure.
At any rate I'll have a fix soon.


Strangeness with mute echo

Both examples will yield the same result if you type it in the Service Simulator, but in the first example my echo device won't speak. Why is that?
Example with 5ms waiting async function, echo does not speak:
myApp.intent("HelloWorldIntent", {
		"utterances": [ "say hello world" ]
    },
    function(request, response) {

    	console.time("exectime");

    	setTimeout(function() {
    		response.say('Hello World.').shouldEndSession(true);
    		console.timeEnd("exectime");
	}, 5);

    }
);

Example with 5ms bad busy waiting works:
myApp.intent("HelloWorldIntent", {
		"utterances": [ "say hello world" ]
    },
    function(request, response) {

    	console.time("exectime");

	/* busy waiting 5ms */
	var wait = new Date(new Date().getTime() + 5);
	while(wait > new Date()){}

    	response.say('Hello World.').shouldEndSession(true);

    	console.timeEnd("exectime");
    }
);

If you're using 4.0.0 you need to return a promise or false in older versions, otherwise the session will be closed before you get a chance to hit say. Maybe this SO is a good place to start.

Ah, thanks, trap for young players. The response got to the Service Simulator and cards correctly though, just the Echo was mute. This could lead to some confusion.

If you think the doc can be clearer, please contribute by all means! It's a common problem.


Use CommonJS-compatible export in TypeScript definition

See https://github.com/sindresorhus/meta/issues/9#issuecomment-487273390.

Thanks for doing this 🙌


Change the default drawable?

It's possible change the default drawable, to my custom image?
i use the .setNoMatchFoundDrawable, but the icon only change to after edtitext has focus.

Hi Alex.
Thanks for reporting the bug. I've fixed it and it should be available as an update through maven.
Here is the release incase you're manually adding the files: https://github.com/aliHafizji/CreditCardEditText/releases/tag/2.0


[Bug] cannot parse server version on Paper 1.21

API version
2.3.4
Server software and version
Paper 1.21
Steps to reproduce
Initialize the SignGUI class on Paper 1.21

Expected behaviour
The server version should be parsed correctly
What is actually happening?
Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.ArrayIndexOutOfBoundsException: Index 2 out of bounds for length 2 [in thread "Server thread"]
        at EpicAchievements-1.2.2.jar/dev.pixelstudios.achievements.libs.signgui.SignGUI.<clinit>(SignGUI.java:33) ~[EpicAchievements-1.2.2.jar:?]
        ... 29 more

The minor version isn't always present
int minor = Integer.parseInt(versionNumbers[2]);

Code snippets
No response
Any additional comments?
No response

So, there were some problems with Maven Central yesterday but I published it now. Right now it's still publishing but it should be finished in a few minutes. Thank you for reporting the issue!


Update CompareCoverageAction.java

Closes #23 23
I added a new constructor that allows to pass an argument for prId rather than strictly relying on the environment variable ghprbPullId being present.

Hi @arpheno, I believe that you can select 	Build origin PRs (unmerged head) still using your branch source plugin and your PRs will be built as PR-number, which make them have CHANGE_ID that fixes the issue you're having...


#3007 [Enhancement] Method manually handles closing an auto-closeable resource [GrpcClientHandler]

Fixes #3007  .
Modifications
Used try-with-resources to manage resources.
Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)
If a feature is not applicable for documentation, explain why? (bug fix)
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation (not applicable)

@sanskar-thakur On line 118 perhaps it could also be changed to use try-with-recourse.


E2E tests consistently failing on Windows

Since about 2 days ago (Friday), our E2E tests are consistently failing on Windows (and only on Windows), with actor tests failing almost every time. Current pass rate is about 10%.
Requests to actor apps fail with "connection refused".
Examples:

https://github.com/dapr/dapr/actions/runs/2899097648
https://github.com/dapr/dapr/actions/runs/2898743651
https://github.com/dapr/dapr/actions/runs/2898057237
https://github.com/dapr/dapr/actions/runs/2897418321
https://github.com/dapr/dapr/actions/runs/2896933383
https://github.com/dapr/dapr/actions/runs/2896604126

There are many different errors in different action run.
I need to find the reason for them case by case.

Start / End time checking fail
https://github.com/dapr/dapr/runs/8027778812?check_suite_focus=true
=== FAIL: tests/e2e/actor_features TestActorFeatures/Actor_concurrency_different_actor_ids. (10.20s)
2022/08/26 00:39:48 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004b/method/concurrency?reqid=aad6a24b-3d62-49a8-9319-07a85f9e329a completed in 5.07398099s
2022/08/26 00:39:54 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004a/method/concurrency?reqid=b76ecc76-2b66-47cc-9ff1-cdea08f93f01 completed in 10.152406245s
2022/08/26 00:39:54 GET http://<IP_ADDRESS>:3000/test/logs?reqid=f9bb9465-001c-4398-8e91-674c7a8abbc1 completed in 51.060052ms
    actor_features_test.go:740:
        	Error Trace:	/home/runner/work/dapr/dapr/tests/e2e/actor_features/actor_features_test.go:740
        	Error:      	Should be true
        	Test:       	TestActorFeatures/Actor_concurrency_different_actor_ids.
    --- FAIL: TestActorFeatures/Actor_concurrency_different_actor_ids. (10.20s)

For the code of test case:
require.True(t, (logOne.StartTimestamp >= logTwo.EndTimestamp) || (logTwo.StartTimestamp >= logOne.EndTimestamp))

From the time information in the logs
2022/08/26 00:39:48 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004b/method/concurrency?reqid=aad6a24b-3d62-49a8-9319-07a85f9e329a completed in 5.07398099s
2022/08/26 00:39:54 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004a/method/concurrency?reqid=b76ecc76-2b66-47cc-9ff1-cdea08f93f01 completed in 10.152406245s

we can get that start time as follow:

actor id
Start time
End time (time in log)
completed in xx s

1004a
00:39:44
00:39:54
10.152406245s

1004b
00:39:43
00:39:48
5.07398099s

Then "(logOne.StartTimestamp >= logTwo.EndTimestamp) || (logTwo.StartTimestamp >= logOne.EndTimestamp)" should be true. Don't know why it is false.
Action: add log in e2e test case to see the actual data.

Could this be an issue with the clocks out of sync? Perhaps one actor runs on a different VM and there's a clock drift?

Could this be an issue with the clocks out of sync? Perhaps one actor runs on a different VM and there's a clock drift?

Yes, this is possible. So I added some log to print the start/end time and let's wait for next fail of this case.

connection timeout for actor application
see [dapr-test · dapr/dapr@29233c6 (github.com)](https://github.com/dapr/dapr/runs/8036227288?check_suite_focus=true), the error log are following:
=== FAIL: tests/e2e/actor_sdks TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/DotNetCarActor/ActorId (12.52s)
    actor_sdks_test.go:198: checking err...
    actor_sdks_test.go:199:
        	Error Trace:	/home/runner/work/dapr/dapr/tests/e2e/actor_sdks/actor_sdks_test.go:199
        	Error:      	Received unexpected error:
        	            	Post "http://<IP_ADDRESS>:3000/incrementAndGet/DotNetCarActor/96a252b8-0909-4727-abaa-3154d9553890": dial tcp <IP_ADDRESS>:3000: connect: connection refused
        	Test:       	TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/DotNetCarActor/ActorId
    --- FAIL: TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/DotNetCarActor/ActorId (12.52s)

=== FAIL: tests/e2e/actor_sdks TestActorInvocationCrossSDKs/Test_actorpython_calling_carToJSON/DotNetCarActor/ActorId (12.45s)
    actor_sdks_test.go:198: checking err...
    actor_sdks_test.go:199:
        	Error Trace:	/home/runner/work/dapr/dapr/tests/e2e/actor_sdks/actor_sdks_test.go:199
        	Error:      	Received unexpected error:
        	            	Post "http://<IP_ADDRESS>:3000/carToJSON/DotNetCarActor/86fc2e86-7e13-43ff-a515-db904af5b511": dial tcp <IP_ADDRESS>:3000: connect: connection refused
        	Test:       	TestActorInvocationCrossSDKs/Test_actorpython_calling_carToJSON/DotNetCarActor/ActorId
    --- FAIL: TestActorInvocationCrossSDKs/Test_actorpython_calling_carToJSON/DotNetCarActor/ActorId (12.45s)
make: *** [tests/dapr_tests.mk:294: test-e2e-all] Error 1

=== FAIL: tests/e2e/actor_sdks TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/PythonCarActor/ActorId (12.27s)
    actor_sdks_test.go:198: checking err...
    actor_sdks_test.go:199:
        	Error Trace:	/home/runner/work/dapr/dapr/tests/e2e/actor_sdks/actor_sdks_test.go:199
        	Error:      	Received unexpected error:
        	            	Post "http://<IP_ADDRESS>:3000/incrementAndGet/PythonCarActor/c59b2f2b-e3c5-45b3-a491-b57a3de93ba1": dial tcp <IP_ADDRESS>:3000: connect: connection refused
        	Test:       	TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/PythonCarActor/ActorId
    --- FAIL: TestActorInvocationCrossSDKs/Test_actorpython_calling_incrementAndGet/PythonCarActor/ActorId (12.27s)

=== FAIL: tests/e2e/actor_sdks TestActorInvocationCrossSDKs/Test_actorpython_calling_carFromJSON/PythonCarActor/ActorId (12.30s)
    actor_sdks_test.go:198: checking err...
    actor_sdks_test.go:199:
        	Error Trace:	/home/runner/work/dapr/dapr/tests/e2e/actor_sdks/actor_sdks_test.go:199
        	Error:      	Received unexpected error:
        	            	Post "http://<IP_ADDRESS>:3000/carFromJSON/PythonCarActor/22cd6640-18a0-493e-a834-bf05b43ed1ee": dial tcp <IP_ADDRESS>:3000: connect: connection refused
        	Test:       	TestActorInvocationCrossSDKs/Test_actorpython_calling_carFromJSON/PythonCarActor/ActorId
    --- FAIL: TestActorInvocationCrossSDKs/Test_actorpython_calling_carFromJSON/PythonCarActor/ActorId (12.30s)

It shows that when the test case (TestActorInvocationCrossSDKs) want to access the actor applications, the actor applications is not ready and failed to connect.
But from the code of test case TestActorInvocationCrossSDKs:
for _, appSpec := range apps {
		app := appSpec.AppName
		externalURL := tr.Platform.AcquireAppExternalURL(app)
    // there is a health check for app to confirm the app is ready
		healthCheckApp(t, externalURL, numHealthChecks)
	}

// and there is a sleep of 10 seconds after health check
time.Sleep(10 * time.Second)

for _, appSpec := range apps {
  for _, actorType := range actorTypes {
			for _, tt := range scenarios {
           // but this HTTP request still failed for "connection refused"
        	 resp, err := utils.HTTPPost(fmt.Sprintf("%s/%s", externalURL, method), []byte(tt.payload))
      }
  }
}

Also on darwin, see https://github.com/dapr/dapr/runs/8041576527?check_suite_focus=true

daprd sidecar failed to start in 10 minutes
https://github.com/dapr/dapr/runs/8060927377?check_suite_focus=true
2022/08/28 22:34:54 Installing apps ...
2022/08/28 22:34:54 Deploying app healthapp-http ...
2022/08/28 22:44:54 deployment healthapp-http relate pods: {"metadata":{"resourceVersion":"16042"},"items":[{"metadata":{"creationTimestamp":null},"spec":{"containers":null},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2022-08-28T22:34:54Z"},{"type":"Ready","status":"False","lastProbeTime":null,"lastTransitionTime":"2022-08-28T22:34:54Z","reason":"ContainersNotReady","message":"containers with unready status: [daprd]"},{"type":"ContainersReady","status":"False","lastProbeTime":null,"lastTransitionTime":"2022-08-28T22:34:54Z","reason":"ContainersNotReady","message":"containers with unready status: [daprd]"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2022-08-28T22:34:54Z"}],"hostIP":"<IP_ADDRESS>","podIP":"<IP_ADDRESS>","podIPs":[{"ip":"<IP_ADDRESS>"}],"startTime":"2022-08-28T22:34:54Z","containerStatuses":[{"name":"daprd","state":{"waiting":{"reason":"CrashLoopBackOff","message":"back-off 5m0s restarting failed container=daprd pod=healthapp-http-59c7c98c9c-wgm5z_dapr-tests(92384374-1c2f-4856-b495-36523dd2cd5e)"}},"lastState":{"terminated":{"exitCode":1,"reason":"Error","startedAt":"2022-08-28T22:41:51Z","finishedAt":"2022-08-28T22:42:02Z","containerID":"containerd://75877a7f3241273d1c98bd4b8a2ed73731d428961c45f041bffdfd099a45a9c3"}},"ready":false,"restartCount":6,"image":"dapre2ee3bced85f8wacr.azurecr.io/daprd:dapre2ee3bced85f8w-windows-amd64","imageID":"dapre2ee3bced85f8wacr.azurecr.io/daprd@sha256:04e4444136d38dae32f804fa4267e1dc5ce464161f04f1a9adb27bc033f60d27","containerID":"containerd://75877a7f3241273d1c98bd4b8a2ed73731d428961c45f041bffdfd099a45a9c3","started":false},{"name":"healthapp-http","state":{"running":{"startedAt":"2022-08-28T22:34:58Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"dapre2ee3bced85f8wacr.azurecr.io/e2e-healthapp:dapre2ee3bced85f8w","imageID":"dapre2ee3bced85f8wacr.azurecr.io/e2e-healthapp@sha256:1b4813f62b4f926813ecf2cd9a4b37545b348b019edb016d27c8b5f67280db38","containerID":"containerd://c8cd3940aaf558992b1e1fd7cb51ed8f958b7a314dfb28b3e4632a99221fe801","started":true}],"qosClass":"Burstable"}}]}
2022/08/28 22:44:54 Running teardown...

You can save it like https://github.com/dapr/dapr/blob/master/.github/workflows/kind-e2e.yaml#L219 does.

@skyao  the logs from AKS clusters are stored in Azure Monitor. You should have access per my message on Teams. Those are collected directly from the platform so they are more reliable.

Also on darwin, see https://github.com/dapr/dapr/runs/8041576527?check_suite_focus=true

This is a different issue: https://github.com/dapr/dapr/pull/5086

@skyao the logs from AKS clusters are stored in Azure Monitor. You should have access per my message on Teams. Those are collected directly from the platform so they are more reliable.

Updated: thank for Alessandro, I have got the container logs from Azure log monitor by
ContainerLog
| where ContainerID has "75877a7f3241273d1c98bd4b8a2ed73731d428961c45f041bffdfd099a45a9c3"
|take 10000

query_data.csv
In the end of the container logs, I found that:
time="2022-08-28T22:42:02.5670018Z" level=warning msg="Failed to listen on [::1]:50001 with error: listen tcp [::1]:50001: bind: An attempt was made to access a socket in a way forbidden by its access permissions." app_id=healthapp-http instance=healthapp-http-59c7c98c9c-wgm5z scope=dapr.runtime.grpc.api type=log ver=edge

time="2022-08-28T22:42:02.5670018Z" level=warning msg="Failed to listen on <IP_ADDRESS>:50001 with error: listen tcp <IP_ADDRESS>:50001: bind: An attempt was made to access a socket in a way forbidden by its access permissions." app_id=healthapp-http instance=healthapp-http-59c7c98c9c-wgm5z scope=dapr.runtime.grpc.api type=log ver=edge

time="2022-08-28T22:42:02.5670018Z" level=fatal msg="failed to start API gRPC server: could not listen on any endpoint" app_id=healthapp-http instance=healthapp-http-59c7c98c9c-wgm5z scope=dapr.runtime type=log ver=edge

There is a issue similar to above error:
https://github.com/dapr/dapr/issues/3060
It seems that hyper-v maybe the root cause:
https://github.com/docker/for-win/issues/3171#issuecomment-459205576

query_data_for_all_bind_error.csv
This is the logs from azure log monitor, this bind error happened since 31 July.
There are more than 700 lines, it means that there are more than 350 times that dapr sidecar failed to start for binding port.
And it's interesting that this error only happened to 50001 port, never happened to other port like 3500.

We can change the port if needed. But if this were Hyper-V and a 4-years-old issue... why are we seeing it only now?

update for bug1 - Start / End time checking fail:
After adding the log of start time and end time, we can see the start time and end time of actors when test case failed.
As shown in following link:
https://github.com/dapr/dapr/runs/8084847563?check_suite_focus=true
There are logs when test case failed to do start time / end time checking:
2022/08/30 05:01:45 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004b/method/concurrency?reqid=913c7fa5-a0e6-4f27-93ad-9997ab63402e completed in 5.044864444s

[1062](https://github.com/dapr/dapr/runs/8084847563?check_suite_focus=true#step:19:1063)2022/08/30 05:01:50 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1004a/method/concurrency?reqid=8cd4423e-5087-4c69-86ea-bfe7e7a9770f completed in 10.111575507s

2022/08/30 05:01:50 failed for start/end time check: logOne.StartTimestamp='1661835705191' logOne.EndTimestamp='1661835710214' logTwo.StartTimestamp='1661835700145' logTwo.EndTimestamp='1661835705147'

I list the time in above logs to see what happened to the two actors:

actor id
StartTimestamp
EndTimestamp
End-start
completed
log print time

logOne
1004a
1661835705191(05:01:45)
1661835710214(05:01:50)
5s
10.111575507s
05:01:50

logTwo
1004b
1661835700145(05:01:40)
1661835705147(05:01:45)
5s
5.044864444s
05:01:45

From these data we can get that:

actor of logOne (actor id=1004a) and actor of logTwo (actor id=1004a) started in 05:01:40 ( log print time - completed) , this should match the code of test case since in the test case there are two go routine to execute the two actors
actor of logTwo (actor id=1004a) started immediately (StartTimestamp=05:01:40) and completed in 5 s (confirmed by EndTimestamp and log print time)
actor of logOne (actor id=1004a) not started immediately but wait util actor of logTwo is completed. This behavior can be confirmed by logTwo.EndTimestamp<PHONE_NUMBER>47(05:01:45) and logOne.StartTimestamp<PHONE_NUMBER>191(05:01:45).

So from the logs, the two actors is not executed concurrently, but one by one. This should be a bug of actor on windows.

update for bug3 - dapr sidecar failed to start because of 50001 port binding
I found many similar logs in dapr container logs. This log is more clear that the 50001 port is used (or not free in time)  :
time="2022-08-31T03:53:31.6769864Z" level=warning msg="Failed to listen on [::1]:50001 with error: listen tcp [::1]:50001: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted." app_id=actorfeatures instance=actorfeatures-586d955bb-jcdtg scope=dapr.runtime.grpc.api type=log ver=edge

time="2022-08-31T03:53:31.6769864Z" level=warning msg="Failed to listen on <IP_ADDRESS>:50001 with error: listen tcp <IP_ADDRESS>:50001: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted." app_id=actorfeatures instance=actorfeatures-586d955bb-jcdtg scope=dapr.runtime.grpc.api type=log ver=edge

time="2022-08-31T03:53:31.6769864Z" level=fatal msg="failed to start API gRPC server: could not listen on any endpoint" app_id=actorfeatures instance=actorfeatures-586d955bb-jcdtg scope=dapr.runtime type=log ver=edge

bug4 - e2e test case can't connect to ingress
https://github.com/dapr/dapr/runs/8106662992?check_suite_focus=true
2022/08/31 05:02:38 DELETE http://<IP_ADDRESS>:3000/test/testactorfeatures/1001d/reminders/myReminder?reqid=da7b922e-1ebd-45bb-b956-b0a4ef8f817a completed in 73.564155ms
2022/08/31 05:02:38 POST http://<IP_ADDRESS>:3000/test/testactorfeatures/1001d/reminders/myReminder?reqid=d14c9028-5a8e-4489-b297-8cf0b993052d completed in 73.977072ms
2022/08/31 05:02:48 GET http://<IP_ADDRESS>:3000/test/logs?reqid=0a071c32-d8b3-4d68-ab19-8ad1e518fea0 completed in 49.952469ms
2022/08/31 05:02:48 Restarting actorfeatures ...
W0831 05:02:48.539010    2580 warnings.go:70] spec.template.spec.imagePullSecrets[0].name: invalid empty name ""
W0831 05:02:48.694501    2580 warnings.go:70] spec.template.spec.imagePullSecrets[0].name: invalid empty name ""
2022/08/31 05:02:49 Saved container logs to /home/runner/work/dapr/dapr/container_logs/windows_amd64/actorfeatures-5d459d64c8-dfdtw.actorfeatures.log
2022/08/31 05:02:50 Saved container logs to /home/runner/work/dapr/dapr/container_logs/windows_amd64/actorfeatures-5d459d64c8-dfdtw.daprd.log
2022/08/31 05:03:07 Streaming Kubernetes logs to /home/runner/work/dapr/dapr/container_logs/windows_amd64/actorfeatures-5d459d64c8-4rtgf.actorfeatures.log
2022/08/31 05:03:07 Streaming Kubernetes logs to /home/runner/work/dapr/dapr/container_logs/windows_amd64/actorfeatures-5d459d64c8-4rtgf.daprd.log
2022/08/31 05:03:50 GET http://<IP_ADDRESS>:3000/test/logs?reqid=86b39f7b-e67b-4d32-bdf9-c6cd5e3e4406 ERROR after 12.441547615s: Get "http://<IP_ADDRESS>:3000/test/logs?reqid=86b39f7b-e67b-4d32-bdf9-c6cd5e3e4406": dial tcp <IP_ADDRESS>:3000: connect: connection refused
2022/08/31 05:04:33 GET http://<IP_ADDRESS>:3000/test/logs?reqid=368c4689-22cf-4e21-845b-efbb227bd2fa ERROR after 12.447609784s: Get "http://<IP_ADDRESS>:3000/test/logs?reqid=368c4689-22cf-4e21-845b-efbb227bd2fa": dial tcp <IP_ADDRESS>:3000: connect: connection refused

By checking the logs of application and dapr sidecar, I found that the 3000 port of application is OK and sidecar connected it by address of <IP_ADDRESS>:3000.
Yet at that time the e2e test case report "<IP_ADDRESS>:3000: connect: connection refused" after restart.
I guess there are two possibilities：

the ingress address is changed after application restarted. So the externalURL before restart can't be reused after restarted. (But this case work well on linux). Need to add log to check the externalURL before and after restart to confirm it.

the new pod after restarting is move to a new VM and its network have some limitation that something (perhaps network firewall) blocked the request to ingress address (<IP_ADDRESS>:3000 in this case). The background is that this test case is not failed for every time, sometimes it can be passed.


Add PdfLoader to the project.

This pull request introduces a new PdfLoader class to the project. The PdfLoader class is responsible for loading PDF documents and converting them into a list of Document objects. This is achieved by using the Apache PDFBox library to read the PDF file and extract the text.

Thank you for your contribution @nikitsenka,
The PDF parsing/extraction presents various configuration options and I've been looking for an "optimal" reader implementation that can benefit from the internal structure of the PDF documents.
For example, I would assume that preserving the pdf text formatting, helps the LLM to better detect and interpret any tabular info in the document.
The default PDFTextStripper doesn't preserver the format. There are impl. like PDFLayoutTextStripper trying to do this.
Also, I wonder if stripping the page footer/headers from the text would improve the LLM responses.
There is a PDFTextStripperByArea that allow to cut the page margins before text extraction.
Alternatively this can be achieve by altering the extracted text directly.
Another important (IMO) area is to semantically (pre)split the documents.  (e.g. using the PDF internal structure knowledge).
For example, splitting the pdf by paragraphs (e.g. PDOutlineNode). Unfortunately not all PDFs come with TOC.
Also even if the paragraphs are present, there are not guarantees that they always have the in-page position reference (e.g. PDPageXYZDestination) ...
So i've been playing around all those ideas and here is the current work: https://github.com/tzolov/spring-ai/tree/pdf-loader-2/spring-ai-core/src/main/java/org/springframework/ai/reader/pdf
I'm afraid that until we build a LLM evaluation utilities it will be difficult to objectively, justify any of the ideas.
What is your opinion this?

Preserving the PDF text formatting can indeed be beneficial, especially when dealing with tabular information.
However it requires more parameters to be provided from client side.
In real live i mostly need to load a lot of different pdf documents without knowing structure and contents.
In addition to tabular information, PDF documents can contain various types of metadata: Document structure, Fonts and Colors, Hyperlinks, Images and Multimedia.
By analyzing the document beforehand, we can gather information such as the presence of tabular data, scanned images or non-searchable text, the types of content (text, images, etc.), and other metadata
My intention was to start with common approach applied to all types of documents and move forward with improvements without losing easiness of use.

Hi.  I totally agree with all the challenges your mention regarding 'just throwing a bunch of pdf's and the code being smart to figure it all out'.  Not very sure how we get there as PDFs very so much in their content and structure.  The code you have here was done while other PDF functionality was in flight at the same time.  This PR doesn't go beyond what is now in the code base, so I will close it.  If there are any ideas on how to go about making the current implementations in the code base more robust to achieve things like autodetect columns, tables, etc. let's chat and contributions are always welcome.   Thanks for submitting the PR and hope to see more.


[Bug Report] 1.4.2 Uglify error

Element UI version
1.4.2
OS/Browsers version
Chrome
Vue version
2.4.2
Reproduction Link
n/a
Steps to reproduce
webpack-cli based project, newest version produces Uglify error.
ERROR in static/js/vendor.864b8c7a0146c714115b.js from UglifyJs SyntaxError: Unexpected token: operator (>) [./~/element-ui/src/mixins/emitter.js:2,0]
What is Expected?
Webpack build with no error
What is actually happening?
Webpack produces error

How did you solove this porblem?

ERROR in static/js/vendor.3c7bcdb24ebbd7ee7abd.js from UglifyJs
Unexpected token name «i», expected punc «;» [./~/element-ui/src/utils/merge.js:2,0][static/js/vendor.3c7bcdb24ebbd7ee7abd.js:91400,11]
```js

I still come across this problem:(

ERROR in static/js/vendor.39efa2bc9b3ea7f885f5.js from UglifyJs Unexpected token name «i», expected punc «;» [./~/element-ui/src/utils/merge.js:2,0][static/js/vendor.39efa2bc9b3ea7f885f5.js:29619,11]

ERROR in static/js/vendor.39efa2bc9b3ea7f885f5.js from UglifyJs
Unexpected token name «i», expected punc «;» [./~/element-ui/src/utils/merge.js:2,0][static/js/vendor.39efa2bc9b3ea7f885f5.js:29619,11]

I come across this problem too ...

so do i

any ideas? I faced the same thing
ERROR in static/js/1.b1648b2f48e0defe38c3.js from UglifyJs
Unexpected token: operator (>) [./~/element-ui/src/mixins/emitter.js:2,0][static/js/1.b1648b2f48e0defe38c3.js:5603,32]

I met the similar problem and it's because the uglifyjs plugin used by webpack 3( version 0.4.6) doesn't support es6. if you are using webpack 3, upgrade to webpack 4 or replace the uglifyjs plugin of webpacck 3 to use the latest version will solve the problem.

в build/webpack.base.conf.js в rules добавьте
{         test: /\.js$/,         loader: 'babel-loader',         include: [           resolve('src'),           resolve('test'),           resolve('node_modules/element-ui'),         ]       },


Allow user to enable/disable scale bar in Android v10

Description
Fixes #2295
Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I updated the documentation with running yarn generate in the root folder
[x] I updated the typings files - if js interface was changed (index.d.ts)
[x] I added/ updated a sample - if a new feature was implemented (/example)

Screenshot OR Video
Before (notice top left):

After:

@arcticfly thanks much, I've reworked the PR a bit, and merged in #2298

Thank you @mfazekas!


Show syntax errors in your code

Typos, wrong API use, ... will just be hidden behind the cadquery server.
Can this be surfaced in some VS Code output model?

Yes, good point!
Currently the server returns a json response that only contain the model field at the root level, and I plan to add stdout and stderr.

I added type checking and code completion! It will be included in the next release.

Note that I'm still on my host, where CadQuery is not installed.
It is made using CadQuery stubs generated with MyPy, that I included in the extension.
Here it works with Pylance, but it should work with other language servers.

I think I can close this now, since it fixes the original request Show syntax errors in your code. I will add code output in the future.


Add share button

Add share button  to share quotes in Twitter, Facebook or any other platform

hello @Shariar-Hasan i have added a PR can u please review so that i can get my first PR merged for the hacktoberfest

Assalamualaikum @Shariar-Hasan i have added a PR can u please review so that i can get my first PR merged for the hacktoberfest

Walaikum salam.... done bro


[1.15+] Flushing FTCS sequences causes flickering in nushell 0.66+

Windows Terminal version
1.15.2003.0
Windows build number
Microsoft Windows [Version 10.0.22000.795]
Other Software
Nushell v0.66+
Steps to reproduce
Hi, I work on a cross-platform shell called Nushell and we've noticed a rendering regression in Windows Terminal Preview v1.15.
Nushell's prompt now flickers on every keystroke. The following recording illustrates the problem (but it's a little worse in real life, the recording didn't capture every flicker):
https://user-images.githubusercontent.com/26268125/183734387-10477dd6-220c-4f7d-8b21-f7737736d0ee.mp4
To reproduce this, run any version of Nushell from v0.66 or later and start typing. Nushell can be downloaded from our GitHub releases or installed with Scoop (scoop install nushell) or winget (winget install nushell). nu.exe is the executable for Nushell.
Details / Investigation
The flickering does not occur in Windows Terminal v1.14.1963.0.
We bisected Nushell's code and found that the flickering did not occur prior to this PR which added some scroll mark ANSI escape codes for VS Code. WT v1.15 Preview added experimental support for scroll marks; maybe this is a bug in the experimental scroll mark code?
The flickering occurs even with the scroll mark settings (experimental.autoMarkPrompts and experimental.showMarksOnScrollbar) set to false.
If there's anything else we can do to help with investigation or reproduction, just let me know!

(I'm supposed to be on vacation RN so apologies for the brevity in my notes)
Hmmmmmmmmm. I wonder if this isn't playing nicely with the frame flushing. Like, when the prompt gets drawn, what's happening is a

Move the cursor to the start of the prompt
erase the rest of the line
mark here as the start of the prompt (FLUSHES THE FRAME)
draw the prompt
mark here as the end of the prompt (flushes maybe? maybe not yet)
draw the right side of the status

The trick is that we're flushing all buffered state to the Terminal when we see a prompt sequence. The problem is that at the time the mark is re-rendered, the prompt line is empty, causing the flickering.
No clever solutions off the top of the dome. I'll noodle on the drive home.

@zadjii-msft for what it's worth, we're tracking a related issue with WezTerm. I say they're related because disabling the OSC 133 (and friends) escape sequences seem to correct the problem but, of course, we lose the features that OSC 133 provides. @wez, the author, has a theory here https://github.com/nushell/nushell/issues/5585#issuecomment-1230417496.
Quoting here

If I edit the macos capture and remove the OSC 133 A and OSC 133 B sequences, and replay that file on windows, then the output looks correct. Those are the FinalTerm style shell integration escape sequences.
It looks to me as though this is a ConPTY issue where unexpected/unknown OSC sequences confuse it about cursor positioning or some other similar concern that triggers it to rewrite the output stream.
A workaround would be to skip outputting OSC 133 on Windows or if you know that ConPTY is present.

You can see more of the detailed research here https://github.com/nushell/nushell/issues/5585

Ah, that's probably another related issue. Before a few months ago, conpty didn't recognize those sequences at all, and would emit them immediately, possible before the rest of the "frame" they were emitted with. at the end of the day, it just means that FTCS sequence support on older Windows builds is gonna be wacky.
Now, the Terminal uses an out-of-band version of the ConPTY apis. We do that so we can always use the main version of ConPTY in the Terminal, rather than the OS one (which might be months or years out of date). So the issue in the Terminal version of ConPTY is caused by me trying to fix the issue in the OS version of ConPTY (used by wezterm et. al).
If that all makes sense.

it just means that FTCS sequence support on older Windows builds is gonna be wacky.

It all makes sense except this was on an updated copy of Windows 11. So, I expect old versions to be wacky but hopefully recent Win10 and Win11 will behave better in the near future.

an updated copy of Windows 11

I mean, FTCS support landed literally 3 months ago - I'm not sure it's even made its way to any official Windows builds yet 😅

FWIW, wezterm bundles and uses openconsole.exe and conpty.dll built from GitHub.  I just updated it to the most recent tag this morning and the issue reproduces there too.

Any update on this issue @zadjii-msft?

Alas, no. I haven't noodled on this too much since getting back from leave, and I'm only just getting back into the swing of things after the holidays.
I've got this marked up to take a look at ~this month, but I seriously doubt I'll have a good solution that fast.
IIRC we briefly discussed some ideas, that might work okay in this specific scenario, but wouldn't work more broadly for the other sequences that are leveraging the same flushing that we do here (looking at you alt buffer sequences). I can't remember the details though 😕

It dose not flicker when nushell get any error.

I would also really appreciate a solution for this. Makes using Windows Terminal a pain right now because of all the flickering.

I accidentally discovered one configuration in which nushell does not seem to flicker within Windows Terminal:

Enabled WSL1 on a Windows 11 22H2 system.
Installed ArchWSL as the Linux distribution (btw :) ).
Installed (Windows version of) nushell via scoop.
Ran nu.exe from within an ArchWSL profile in Windows Terminal.
No flicker.

In contrast, all of the following exhibit the flicker in Windows Terminal (on the same Windows 11 22H2 system):

Running Linux version of nushell (installed via pacman) from within ArchWSL profile in Windows Terminal.
Running Windows version of nushell from within Powershell profile in Windows Terminal.
Running Windows version of nushell from within cmd profile in Windows Terminal.

No idea what it is about the former configuration that differs from the latter three, but posting just in case it may be a clue for anyone who has a better bead on this.

@jxcrw that makes sense. The nu.exe in WSL invokes another ConPTY, one that shipped with the OS which farther out of date, and that version would end up probably either

eating all the FTCS sequences
passing them through immediately to the Terminal, before the rest of the frame starts rendering, so nothing looks out of place (though, shell integration wouldn't work right)

ba777dfbf doesn't seem to flash anymore. I'll have to make sure I didn't blow anything else up.
I'm a tad worried about capturing the screenbuffer pointer in that lambda like that.

I would also really appreciate a solution for this. Makes using Windows Terminal a pain right now because of all the flickering.

A fix was mentioned in another thread and I can confirm it works:

Type config nu
Find shell_integration and set it to false

It should stop flickering now. I don't know what the downside is for disabling shell integration, everything seems to work totally fine over a month in.

@popcar2 When you disable shell_integration you lose the ability to have automatic OSC 133;A/B/C/D terminal markers (FTCS sequences) and automatic OSC 2 & OSC 7 term/window titles. It may also interfere with OSC 8 clickable links in nushell.

Interestingly, there is no such problem in the terminal of vscode

any update?
This problem does not occur when nushell runs on alacritty ;-)

any update?
This problem does not occur when nushell runs on alacritty ;-)

Alacritty does not seem to support OSC133 ;-)
https://github.com/alacritty/alacritty/issues/5850

Nushell is still flickering when used within Windows Terminal (both MS store stable/preview + latest GitHub release).

What version are you on exactly? I just tried 1.18.1462 here and I don't see any flickering. Perhaps what you're seeing is one of the newer rendering bugs? That might repro regardless of what shell you're using. Could you share your settings.json?

nu v0.80.0
windows terminal v1.17.1023 | 1.17.1023
is v1.18.x built from source or where did you get it from?

Oh good, I'm glad! This was a tricky fix so I'm really glad it did work after all.
Looks like our friendly neighborhood bot is having a tough time this week and forgot to come around with release notes. This fix shipped in Terminal Preview 1.18 earlier this week.

No flickering issues with nushell and v1.18 when I tested, although it wasn't real stable. I also noticed that the right click command selection was selecting the wrong data. I tried the debug tap and think our escapes look good.

if one of you could check this behavior with the current nightly build of wezterm, I'd appreciate it: I updated the bundled conpty pieces to match 0ee2c74cd432eda153f3f3e77588164cde95044f of this repo, so my understanding is that this should be fixed in wezterm now too.

@wez wezterm nightly, downloaded from here exhibits a similar issue as before but slightly different.

Uh oh, the terminal flickering is back!
I can reproduce it in Terminal Preview 1.20.10303.0 and Nu 0.90.1. I cannot reproduce it in Terminal 1.18.10301.0.
It seems to occur with or without AtlasEngine enabled.

@rgwood I can't reproduce any flickering when using nushell's default out-of-the-box configuration.
I think it'd be best to open a new issue for this. I don't think it'll be necessary to describe the issue in detail - IMO you can just refer to this issue (#13710) in your description. 😅
Given that I don't have this issue, could you check if it occurs when you use the default configuration? If it doesn't reproduce for you either, it'd be nice if there was some way to figure out which option or plugin in nushell causes the issue. (...since reproducing it locally would help me a lot while fixing it. 🙂)

@lhecker I'm really sorry, I should have clarified that this only occurs with shell_integration: true set in the Nushell config (I forgot that this is not on by default. It enables the escape codes for prompt markers etc).
Easiest way to change this setting is by opening the config file with code $nu.config-path or similar and relaunching Nushell.

Thanks! That was super easy to reproduce. I should've realized that given that this issue was also about FTCS. I've opened #16769 so we don't ping the ~dozen people on this issue unnecessarily. I'll try to fix it soon (if possible).


Upgrade text unreadable w/ Small MC GUI

Mek.dev v<IP_ADDRESS>0
1600x900

When opting for a Small GUI (in MC Options) the green text (in the Update GUI tab) regarding how many updates have been put in the machine is unreadable.
Would a mouse-over tooltip be an easy fix?
Doesn't bother too much for now, it's a small annoyance, and I could adjust the GUI when really needed (won't be a lot of times).

Wait, where did you get v<IP_ADDRESS>0?

Mek.dev v<IP_ADDRESS>0
Donators $10+ get access to dev

On my 1024x1280, it happens a lot and with literally every mod. I don't
really see a way to help this.

Not much getting around this, sorry :(

Thanks anyway, problem may be solved on my end eventually (upgrading system specs), and I don't mind the mild annoyances, it's a nice reminder of how well integrated the mod feels and plays in every other aspect!


Not able to make request with Angular 8

Hello,
I am using Angular 8 with Django and I'm trying to retrieve JWT token using POST 'api/login/social/jwt-pair/', but I'm no able to accomplish this.
If I make a request like this, using HttpClient:
this.http.post(
      'http://localhost:8000/api/login/social/jwt-pair/',
       {  provider : 'facebook', code:  'XXXXXXXXX' },
      {
        headers: new HttpHeaders()
        .set('Content-Type', 'application/x-www-form-urlencoded'),
      }
    );

All I receive is:
Provider is not specified
Bad Request: /api/login/social/jwt-pair/
Also tried:
this.http.post(
      'http://localhost:8000/api/login/social/jwt-pair/',
       JSON.stringify({  provider : 'facebook', code:  'XXXXXXXXX' }),
      {
        headers: new HttpHeaders()
         .set('Content-Type', 'application/json')
      }
    );

But all I receive is:
Not Found: /api/login/social/jwt-pair/
What am I doing wrong??? All my posts in my API work but this one doesn't.
I even tried to have a middleware so I could format the request.data and it be accepted by post method, but it doesn't work either, I keep receiving the same messages. Even though my middleware is able to get the provider from request. I don't know what I am missing, can anyone help?

Did you ever find an answer to this? Having this issue as well.


Inline method hides content after close

Not sure if this is a bug, but when you use the inline method -- which works awesome -- and then close the modal window, that element you launched is removed or hidden from the DOM.
Is there a way to avoid that?
I tried doing a callback function to set the CSS on the element to 'block', but that didn't work.

Hi @markpopkes, are you referring to the modaal window markup content being removed when it's closed, or the element you clicked to trigger the opening of the modaal being closed ?
If it's the modaal popup markup you're referring to, this is intentional to ensure the plugin isn't affecting the overall page accessibility by having hidden, unused content. Currently there is no way around this.
Feel free to set up a js fiddle and share so I can get an idea of your scenario and problem.

Closing due to inactivity.  If there's any followup, feel free to open up a new issue or re-open this one.


All nodezoo services need to have working Dockerfiles

For us to be able to deploy nodezoo on AWS the way we want to, we need to have all the services built using containers.
I have already converted some of the services to working containers, but we need to manually test and confirm that all of them build and run via docker and docker-compose.
The task is as follows :

set up docker locally, and have it running via
eval $(docker-machine env default)
go through each of the services defined in the package.json
Make sure the docker container has one of the following variations
if the service is backend only, base it on the nodezoo-base dockerfile
if it has an http service, base it on the nodezoo-web dockerfile
1. HTTP services should have RUN npm run build in their Dockerfiles.
1. HTTP services should EXPOSE $port on the same port the service listens to
(check the code).
All services should have a CMD ... taken from the fuge-config.js file.
Remove the overrides once they are in the dockerfiles
(fuge should pick up the run command from the dockerfile automatically)
To test if the container builds correctly, cd into the directory and run
docker build -t some-service .
Once everything is done, you should be able to run this from the nodezoo-system folder :
docker-compose -f fuge/services.yml build

@AdrianRossouw I think we are good on this?

Closed as complete.


[Doc] The user rights management doc is out of data

Describe the bug
In production env, we really need a user access management for our databases.
But in the User rights management doc, the functions are out of date right now and can not be used to setup user access rights correctly like:

modSpecifiedAccessLevel function does not exist anymore, the name of the function should be modRoleAccessLevel now, so there will be an error about unregistered standalone function if we call modSpecifiedAccessLevel in the Cypher.

I think we should keep the document identical with the code at our best to make sure users can setup the database properly by themselves.

Also, we should give some examples about how to use the functions since users may not understand how to properly set a Map param to functions like CALL dbms.security.modSpecifiedAccessLevel(role::STRING,access_level::MAP).

A lot of efforts should be made to enhance doc, thanks for detailed suggestion.
Currently, all interface are tested in UT, you can also find the examples in UT (which should be put in doc).

I think I can help with the update of this doc and sync the function from UT to doc.


[NProgress] Add new component

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #22486
This is my first component contribution, so I hope it looks okay.
If I forgot anything else please let me know.
This PR was supposed to be a draft, but I forgot to change before creating it.
I didn't add the unit test yet because I will do after all the changes to the implementation are done, if any. So I don't make unnecessary tests.
WIP

[ ] Add unit tests

I'm currently checking why those guys failed.

Regarding people that might wonder: Why this name? It's because https://github.com/rstacruz/nprogress.

Thanks for the review and the fixes @oliviertassinari! Here it goes my thoughts of the topics you mentioned:

There is a naming issue. I think that the component should be called NProgress, not NProgressBar to make it straightforward.

I was going to use NProgress but your example on the issue was NProgressBar so I took the inspiration from there. I'll change it.

The animation takes way too much time to finish, compared to reference implementations

You mean when you call NProgress.finish()? If yes, then I can fix by changing the animation speed on the bar1. If not, then we need to decide which trickle we should use, I currently copied from the original nprogress.

For the imperative API, what do you think about nProgressRef for its name?

I think it's nice. I'll change it after we decide which API approach we will follow considering the next topic.

I think that we should isolate the state logic with the rendering one. How about we create a useNProgress hook for doing such? It would lay the ground for the unstyled/hook API.

That depends. I don't fully get what you expect with using the hook solution. I also thought of it at first, using the ContextAPI to be more specific, but it was too much clutter on the code so the global state solution seemed nicer to me. And mimics the implementation of the original while also working on React context (subscribe to state change).
But to decide, can you show me an example of what you have in mind?

Did we contact the author of https://ricostacruz.com/nprogress/ and ask if it's ok to re-use the name?

Not yet. I agree that we should but this component is currently a proposal so I didn't put much thought on doing that at the moment. But we can do that after this component is approved, if they don't allow we can change the name for something like PageProgress.

After all, it's not using the package so using the name might be considered misleading. Attribution is also missing as far as I can tell.

I mentioned the name as concept rather than the library itself, but I agree that we could add a better reference to it.

Let's inline nProgressState since it's coupled with the component.

I'll address the reason of the global state on the review https://github.com/mui-org/material-ui/pull/25889#discussion_r619023297.

Let's inline nProgressState since it's coupled with the component.

I'll address the reason of the global state on the review #25889 (comment).

These are not tied. What kind of state implementation we use does not determine the file structure. Since we only use the file in a single place we might as well inline it to have everything related in a single spot.

These are not tied. What kind of state implementation we use does not determine the file structure. Since we only use the file in a single place we might as well inline it to have everything related in a single spot.

Oh, I'm sorry. I misinterpreted your comment. I agree with you. I'll keep a todo on the PR to address that.

I was going to use NProgress but your example on the issue was NProgressBar so I took the inspiration from there. I'll change it.

@italodeandra It feels that nprogress has become a common terminology for the pattern, and judging by the visibility the issue got (upvotes), it's working. If we need an alternative name, I would vote for PageProgress (NProgress is likely better, but 🤷♂).

You mean when you call NProgress.finish()? If yes, then I can fix by changing the animation speed on the bar1. If not, then we need to decide which trickle we should use, I currently copied from the original nprogress.

Not really. I mean that it feels like the progress bar waits to reach 100% width before closing. It's creating a distraction away from the content that was just loaded. I think that it would be much better if it was closing ASAP, even if the bar hasn't reached the end yet. It should only no stop its momentum so it feels smooth.

That depends. I don't fully get what you expect from using the hook solution. I also thought of it at first, using the ContextAPI to be more specific, but it was too much clutter on the code so the global state solution seemed nicer to me. And mimics the implementation of the original while also working on React context (subscribe to state change).
But to decide, can you show me an example of what you have in mind?

What I meant is that we can split the problem into two distinct parts. One is about getting the right value to render the progress bar. A second is to render these values. I think that a hook for the first part would be interesting for us, to isolate the logic, and for developers, if they want to rebuild the UI (headless pattern).

I think it's nice. I'll change it after we decide which API approach we will follow considering the next topic.

Regarding the state logic, there will always be a single URL. We should leverage this constraint, for instance to improve the DX or simplify the logic.
Using a global, singleton state to store the pending state looks interesting. I think that the source of truth should be outside of React.
Regarding the create() method, the name could be improved, it also looks like it could be simplified, there are options we don't use. It looks close to the event emitter pattern, but it's not because there is a reducer. Outside of the simplification we can do, this looks great.
What are the alternative options? The main challenge is that the routers are global singletons (in Next.js and Gatsby)

Using the context. It seems overkill. Nobody has advocated for using it yet.
Using a ref to hold the state, stored inside a hook. The integrations with Next.js and Gatsby would likely be complex for very little updates in exchange (see the two previous links for getting a glimpse of why it will be complex).

+1 for the current approach.
Regarding accessibility, I have found this fork we could maybe leverage.
Going off-topic, @dtassone this event emitter/reducer could likely solve the current data grid rendering issues: performance and soundness.

Hey team, I'll have some free time this week and I'm planning on working on this guy here. Besides what we already discussed here, is there anything I should be aware of?

@italodeandra Thanks for working on this. We can reopen the PR if you find time to work on it again.


cryptsetup: declare private dependencies for static linking

Identified by Kiskae in https://github.com/grahamc/libcryptsetup-static-rust/pull/1/files#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0R30-R37
Applies MR366: https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/366
Description of changes

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@grahamc @alyssais Looks like upstream has merged a more comprehensive patch than this one, it hasn't been part of a release yet but we could replace this PR with a cherry-picked patch: https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/411


Remove old PID file

This should fix #61.

To reproduce the issue one can start an Opencast instance with the docker-compose files and then stop ActiveMQ and MariaDB before Opencast. The stop routine then seems to error leaving the PID file still present.

It turns out that /opencast/instances/instance.properties is actually used for looking up the PID. Added that file to the removal list.

I'm not really sure if it's a good idea to just remove the PID. Of course, the user should know that only one container should be running at a time, but I can see some weird edge cases happening.
Maybe it would be a better idea to add some command to the start script, which should be manually executed after we display a huge, loud warning when the pid file exists?

My concerns have been resolved in a private chat - this scenario should not occur, therefore the approach is safe.


HSEARCH-2696 Move integration test environment resources to a more fitting location

https://hibernate.atlassian.net//browse/HSEARCH-2696

I'm working on JVM options for Elasticsearch right now; I may have to move the configuration around so as to avoid duplicating it. I'll update this PR accordingly.


Passing Promise<()> as a parameter

Scenario
Passing a myPromise: Promise<()> as a parameter to functionX to decides to execute it or not.
Expected Results
When functionX decides not to run myPromise, myPromise shouldn't be executed
Actual Results
myPromise still runs anyways, it doesn't care about functionX's decision
Sample Code
func somePromise() -> Promise<()> {
    print("running it")
    return Promise(value: ())
}

func runIt() {
    func runPromiseIfNeeded(promise: Promise<()>) -> Promise<()> {
        //no, i dont want to run that promise
        return Promise(value: ())
    }

    runPromiseIfNeeded(promise: somePromise()).catch{ print($0) }
}

runIt()

Sample project
Versions

PromiseKit version: 4.1.0
Xcode version: Version 8.1 (8B62)
Carthage version: 0.18

You're calling somePromise(), so yes, its returned promise will execute. This is expected behavior.

Like Nathan says, If you don't want the code in somePromise() to execute, then don’t call it… this isn't PromiseKit, this is Swift.

You want something like this, presumably:
func somePromise() -> Promise<()> {
    print("running it")
    return Promise(value: ())
}

func runIt() {
    func runPromiseIfNeeded(promise: () -> Promise<()>) -> Promise<()> {
        //no, i dont want to run that promise
        return Promise(value: ())
    }

    runPromiseIfNeeded(promise: somePromise).catch{ print($0) }
}

runIt()

Thank you guys, now i clearly understand. Sorry for long reply (because i feel so ashamed).


remove './gradlew tomcatRun' - it's both un-used and appears totally broken anyway

This test also failed, are we going to use @Ignore again, seems like this is more consistent now.

I'm converting this to Draft, because I created it re. https://markmail.org/thread/jnlerankgfbq6zhe, but it looks like Petri Tuomola may actually use tomcatRun for FINERACT-730, so let's hold this.
PS: @maektwain Yes, as per https://github.com/apache/fineract#pull-requests. Unrelated to this PR.

Closing this one, because both tomcatRun and tomcatRunWAR are (about to be) remove in #807.
@ptuomola


Base table component

[WIP]
The base table seems to be working, need to abstract out some more logic into components
Code is pretty terrible rn, just a PoC

Closing since we moved this over on staging


Avoid saving to file

Hi,
in my raspberry installation I limited as much as possible any unnecessary writing to the SD-Card to improve reliability. I notice that you write into the system log for every update of the raspberry power status. It seems also that to acquire data from the daemon you pass through an output file written by the daemon. Is it possible to implement everything in memory only?
Thanks

Neither Homebridge nor Homebridge RPi writes any log message to file: they're written to stdout (debug and log messages) and stderr (warning and error messages).  Depending on how you start Homebridge, these are redirected to a log file or to syslog.  If you don't want to write these to the SD card, change the service definition or startup script for Homebridge, to redirect these to RAM disk, external disk, or even /dev/null (which I wouldn't recommend, because you'll have no info for troubleshooting).
Homebridge RPi leverages (abuses if you want) the pigpio socket to communicate with the Pi being monitored.  That only allows a script to be started and a file to be read; there's no way to pass the output of a script.
Implementing a custom service with another socket to pass this information without using a file on the remote Pi seems too much work.  I already got the question of Discord if the Pi accessory is needed at all, and if it would be possible to expose only the GPIO pins.  I think it would be, but I need to investigate; if possible, I'll add a config.json options to suppress the Pi accessory, and not call (or even require) the vcgencmd script.
Note that vcgencmd (called from the vcgencmd script) required elevated privileges, which I don't want to give to Homebridge.  So these commands need to be issued from another process.  If not called from pigpio (which runs under elevated privileges to access the GPIO pins), the script itself would need to be suid-ed.  That seems like a complex setup as well, so I decided not to create a special provision for monitoring the local Pi (the one Homebridge runs on).
I haven't tried to use a named pipe instead of a regular file for the vcgencmd script.  I'm not sure if that's handled entirely in memory, the named pipe is still a directory entry, but I suppose the contents woudn't be written to the SD card every heartbeat.  I could also change the location of the output file to /tmp or something, so you could use a RAM disk for that.

It's fine for me to have messages directed to syslog (for troubleshooting), however I would prefer to have there only one-time messages (e.g. at startup), or errors, not runtime Infos on regular updates. Would it be possible to add a parameter for homebridge-rpi verbosity level?
As for the file written by the daemon, I think it may be ok to give the ability to set a path, so that one could divert it to a ramdisk.

Please provide your thoughts on how best to provide a mechanism to change the level of logging to https://github.com/ebaauw/homebridge-lib/issues/26.

Next version will support changing the level of logging.  Also, the state of the local Raspberry Pi will be retrieved directly, without going through pigpio and an output file.  The output file will move to /tmp.  Making that configurable is easy on the Homebridge side, but needs to be reflected in the script and the pigpio configuration.  Maybe when I create an install/configure script, but for now it's too cumbersome.

In v1.1.0.

Great!


GitHub collaboration resources

including issue template in this repo

Coverage remained the same at 81.832% when pulling 0bdd329d325a3bee1a04642f07549eee397e8f04 on github-collaboration-resources into 047acc0e7d058e72ca0afbd1b599142cb35c8406 on staging.


Xcode 16 / Swift 6 support?

I'm using KmmResult in a KMP library project.  I just upgraded to XCode 16 along with Sequoia, and so got upgraded to Swift 6.
My KmmResult stopped working on iOS - the .fold {} never was entered, similar results with .onSuccess{}.onFailure{}.getOrNull() - the methods appear to never get called.
I've done a build with a Swift 5.10.1 toolchain.  I'll report back if that build works.  But it appears there may be some Swift 6 incompatibilities - not sure if it's in KmmResult, or KMP in general.

Thank you for reporting and investigating this!

This is not, from what I can tell, a KmmResult issue.  It's more likely an SKIE issue.  Thanks!


Ensure RDF for taxonomy vocabularies is up to date with JHU RDF profile

The RDF mapping for taxonomies has not been revamped in Islandora yet.  There is an already existing rdf mapping in Islandora for the vocabularies that have existed before and this ticket is to review those mappings, as well as add mappings for new vocabs.

Fixed by: https://github.com/jhu-idc/idc-isle-dc/pull/46

Fixed by: https://github.com/jhu-idc/idc-isle-dc/pull/46


fix orc readers leak issue for ORC PERFILE type

Signed-off-by: Bobby Wang<EMAIL_ADDRESS>This issue is to fix #2850
The close function of GpuOrcPartitionReader is not called when GpuOrcPartitionReader has finished reading which results in orc readers not be closed, like leaking.
Eventually, the close function of GpuOrcPartitionReader will be called on Spark task completion, but it's too late. The orc readers occupy the connection pool and result in another one that applies connection timeout for the S3 case.
For example, If the max connection of s3a is set to 256 and we have 257 ORC files to read, let's assume we only have 1 task. then the first 256 ORC files can be read without any problem, but for the last orc file, it will timeout to apply connection from s3 pool since the 256 connections have been unavailable.
So the fix is releasing the orc readers after GpuOrcPartitionReader has finished the reading.
I did the testes for 600 Orc files and 1000 Orc files for PERFILE reader. And no task failed.

build

build

build

build

build

build


Draftail not showing entity buttons.

Issue Summary

I created this issue on stack overflow and no solutions.
The Wagtail example of using entities as given in this page of documentation isn't working for me. I am following the third example of using Entities which is supposed to create a button for stock price but no button is appearing for me in the rich text field in the admin editor. I have created a minimum reproducible example which demonstrates just this problem. https://github.com/kiwiheretic/stockentity. I am using Wagtail 4.1.1 which I understand is the latest version.
Steps to Reproduce
Using wagtail 4.1.1 follow the instructions for StockEntity as per https://docs.wagtail.org/en/stable/extending/extending_draftail.html#creating-new-entities.  Also GitHub repository above.
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Expected to see a stock button draftail editor.  No such button appeared

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)

Yes
Technical details

Python version: Run python --version.

Python 3.8

Django version: Look in your requirements.txt, or run pip show django | grep Version.
Django>=4.1,<4.2

Wagtail version: Look at the bottom of the Settings menu in the Wagtail admin, or run pip show wagtail | grep Version:.

Wagtail 4.1.1

Browser version: You can use https://www.whatsmybrowser.org/ to find this out.

Various browsers

I tried that it is still not working for me.  Here is my pip freeze.
anyascii==0.3.1
asgiref==3.5.2
backports.zoneinfo==0.2.1
beautifulsoup4==4.11.1
certifi==2022.9.24
charset-normalizer==2.1.1
Django==4.1.3
django-filter==22.1
django-modelcluster==6.0
django-permissionedforms==0.1
django-taggit==3.1.0
django-treebeard==4.5.1
djangorestframework==3.14.0
draftjs-exporter==2.1.7
et-xmlfile==1.1.0
html5lib==1.1
idna==3.4
l18n==2021.3
openpyxl==3.0.10
Pillow==9.3.0
pytz==2022.6
requests==2.28.1
six==1.16.0
soupsieve==2.3.2.post1
sqlparse==0.4.3
telepath==0.3
urllib3==1.26.13
wagtail==4.1.1
webencodings==0.5.1
Willow==1.4.1

I suspect this was likely the same issue as #9281, as far as I can see the stock button works as expected.


Update ExpressRouteCrossConnection Route Table Summary Record

Update CrossConnection Route Table Summary Record to reflect better naming for attributes in the backend.
Fix the name for CrossConnection Put Operation

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node


Unnecessary horizontal line in hover board hover

VSCode Version: 1.13-insider
OS Version: Windows

Testing: #27481
Hovering over a keyboard short cut shows:

The text reads for me "For your current keyboard layout press: Ctrl+§." so there should be no line between the first sentence and the key to press.

I think this was from a time when we were able to render HTML content in the hover and before we switched to markdown only. In that time, the keypress was rendered with the same style it is rendered in the keyboard UI.


Changing Date crashing app

Trying to edit an entry's date crashes the app and does not save the changes attempted to be made. After selecting a date in the past and tapping "done", the crash occurs. I'm on an iPhone 6+ running iOS 9 b3.

Hmm, confirmed this is working as intended on 8.4; must be a 9-only issue.
Thanks!

Sure thing! I might get some time to dig in this weekend and do some debugging myself. Thanks for open sourcing it!

Hi @lazerwalker
I have resolved the issue and opened the Pull Request. Could you please review.
Thanks.

Date change is crashing the app store version of the app.
Steps to reproduce:

Add a drink, but set the date to a future date
2.Edit the drink date to today's date
app crashes


Research is needed: compare Mull with Klee.

Just for reference: Mull and Klee, part 1: mutation testing analysis for Klee's Tutorial Two


public-api: regenerate

Send + Sync became Sync + Send for reasons I don't understand.

Why is this needed? Locally I don't seem to get Sync + Send

Did you try with today's nightly?

Failure @ main: https://github.com/aya-rs/aya/actions/runs/7443162986/job/20247658356.


Slide width is 0px

Describe the bug
The width of each slide is 0px, resulting in all slides being squashed on top of each other.
To Reproduce
Steps to reproduce the behavior:

Follow "Getting Started" instructions.

Expected behavior
Slides display as in examples.
Screenshots

Desktop (please complete the following information):

OS: MacOS 10.15.6
Browser Firefox
Version: 79.0

Additional context
I'm also using bootstrap, with all page content inside a bootstrap container.

I've got this same issue too, but I'm not using Bootstrap. It doesn't seem to make a difference what content I put in the slides - images or a single line of text - nor how many slides I ask Hooper to show; all the slides are always squashed together with width: 0.

Did someone find a solution for this problem? I'm having it too

I've just ran into the exact same error within a project where I already had a hooper slider working in a very similar way to how I was implementing it the second time.
Anyways the cause of this issue for me was that I had the hooper component wrapped in a 'v-show'. Since the page I was working on was pretty dynamic it meant I had a lot of v-shows and v-ifs scattered about. After switching all of the parent components to use v-if instead of v-show the hooper slider displayed properly.
I've tried to condense some of the code to make it clear, hope this helps!
Before change component code:
`

`
Vue component method which changes the 'contentLocked' flag used in the v-show originally and changed to v-if:
`
unlockContent() {
this.hideModal();
this.playVideo();
this.contentLocked = false;

},
`
Changed code with element now using v-if:
`

`

I'm also having this issue - I'm putting the slides in a v-for. I've got a lot of slides, so I sorta need to do it this way without replicating a bunch of code, but is that going to just fundamentally break it?

This solution should correct the problem:
In your CSS:
.hooper-slide {
    min-width: 100%;
}

I tried first to put an inline style to the slide but I don't know what could be the result in all the cases, and inline style is not great at all.

Hooper dynamically calculates the widths. In my case I had a carousel that was dynamically populated by a search. On page load the width was zero as there was nothing in the carousel. But on user search the carousel width did not change from zero when there were images in the carousel. I used this update method to recalculate the widths https://baianat.github.io/hooper/api.html#methods on search input. To invoke this put a ref on the hooper element e.g. called "hooper" and trigger it using $this.refs.hooper.update()

I found that the reason for why the width was zero was because my sider was wrapper in a boostrap grid.
<b-row>       <b-col md="12" >         <CompanyMessageSlider />       </b-col> </b-row>
This resulted in the width being 0. Once I removed the wrapper,  it worked fine!
Hope this helps!


Animated GIF support

Will try'n add this at some point 😄

Specifically around here https://github.com/pinterest/ios-pdk/blob/master/Pod/Classes/PDKClient.m#L606.

Closed via https://github.com/pinterest/ios-pdk/pull/115.