iOS scroll text displacement

Similar to issue #4, I'm seeing weird text displacement issues on iOS. Particularly, when trying to scroll upwards before the beginning or downwards past the end of code sections (where you might usually see rubber banding).

I think it has to do with the padding of the element although I'm not 100% sure.

It seems its an issue with the onscroll event delay and rubber band effect (at beggining and end of scrolling).
Here is an animated example of the Issue:

I believe a good "fix" for this issue would be disabling opacity on textarea when scrolling on touch devices. This way the "shadow text" would not be displayed until user stopped scrolling the box.

Fixed in my pull request. At first I tried changing the text color, visibility and whatnot but that also affected the cursor. So what I ended up doing is using one simple CSS property that does the job. It no no longer produces the same unwanted result.

PR #25 fix this issue.
@AndreYonadam Thanks for the elegant and simple fix for this issue!


Request.Body.AsString() in BeforPipeline brokes this.Bind()

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am running the latest version of Nancy
[ ] I have verified if the problem exist in both DEBUG and RELEASE mode
[x] I have searched open and closed issues to ensure it has not already been reported

Description
When I'm using method AsString() for RequestStream in BeforeRequest pipeline, it modifes request and after this when I'm binding this request in module, it deserializes properties to default values.
Steps to Reproduce

Implementent IApplicationStartup
Use anywhere in BeforeRequest pipeline method AsString() for RequestStream
Bind model for request in module using this.Bind()

System Configuration
Windows 10, VS 2015

Nancy version:
Nancy host

[ ] ASP.NET
[ ] OWIN
[x] Self-Hosted
[ ] Other:

Other Nancy packages and versions: Nancy.Bootstrappers.Autofac, Nancy.Serialization.JsonNet
Environment (Operating system, version and so on): Windows 10
.NET Framework version: net46
Additional information: I'm injecting another interface to constructor of implementation IApplicationStartup

It's be caused it's pulled it out the stream. When you do it try setting
the position back to zero
On Sunday, 11 September 2016, mykytanikitenko<EMAIL_ADDRESS>wrote:

Prerequisites

I have written a descriptive issue title
I have verified that I am running the latest version of Nancy
I have verified if the problem exist in both DEBUG and RELEASE mode
I have searched open https://github.com/NancyFx/Nancy/issues and
closed
https://github.com/NancyFx/Nancy/issues?q=is%3Aissue+is%3Aclosed
issues to ensure it has not already been reported

Description
When I'm using method AsString() for RequestStream in BeforeRequest
pipeline, it modifes request and after this when I'm binding this request
in module, it deserializes properties to default values.
Steps to Reproduce

Implementent IApplicationStartup
Use anywhere in BeforeRequest pipeline method AsString() for
RequestStream

Bind model for request in module using this.Bind()
System Configuration
Windows 10, VS 2015

Nancy version:
Nancy host

ASP.NET
OWIN
Self-Hosted
Other:

Other Nancy packages and versions: Nancy.Bootstrappers.Autofac,
Nancy.Serialization.JsonNet
Environment (Operating system, version and so on): Windows 10
.NET Framework version: net46
Additional information: I'm injecting another interface to
constructor of implementation IApplicationStartup

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NancyFx/Nancy/issues/2559, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGaprMP1iGioFIaexI4Eg0bPARxqjgXks5qpEaygaJpZM4J6ETd
.

Yes, setting requestStream position to zero helped, but it's very strange behavior.

Its standard behaviour of streams
On 12 September 2016 at 13:30, mykytanikitenko<EMAIL_ADDRESS>wrote:

Yes, setting requestStream position to zero helped, but it's very strange
behavior.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NancyFx/Nancy/issues/2559#issuecomment-246332453, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGapkb1sZ8HWSCGm7oQGRjoJgioBIXcks5qpUXrgaJpZM4J6ETd
.


WEEX waterfall组件中增加input组件，在input里输入内容，上拉或下拉后里面的数据没有了

waterfall组件中增加input组件，在input里输入内容，上拉或下拉后里面的数据没有了

Please offer an example on http://dotwe.org/vue

This issue is closed because not giving a response for a long time. If you still confused with this question, you can file a new issue according to the issue template with enough information.


Question related to FW "Standard"

Hi I tried Free version of Flashy Wrappers for recording video in my AIR application. Its working for me.
I have few question before I purchase it for commercial use.

Since the last update was 5 years ago does it support video recording in all new mobile devices?
WIll the FW "Standard" record video in mp4 just like free version? since it is mentioned on the site that there is no Android MP4 encoder in FW "Standard".
Is the code optimized to support 64-Bit requirement of Google Play Store? https://developer.android.com/distribute/best-practices/develop/64-bit

Hey,
FW SDK as I'm aware still does work surprisingly well even today, but I stopped actively developing it  years ago as the sales almost stopped in the past years, together with AIR usage decline. I still do support the rare client who purchases this from time to time. If smaller issues pop up, I am trying to help, but I won't put lots of hours into it anymore (such as supporting new devices etc.).

I can't say, the only way is to test this is trying it yourself on devices of interest with the free version. The code does use pretty old and low level techniques for the video recording which I suppose hardly change in the Android API's, so it has been pretty stable throughout the years. I'd assume capturing in non-realtime mode (avoiding the fast WebGL capture) should be pretty reliable. If you plan to use WebGL / fast realtime capture on Android, results might vary.
Yes, FW "Standard" doesn't have Android included as historically there was always higher likelyhood of support requests for Android than for iOS due to the range of Android devices.
Yes, FW includes 64 bit extension support, 64 bit accross platforms is one of the few things I was willing to work on despite the lack of other updates. Here's the manifest file for the Android extension:

<extension xmlns="http://ns.adobe.com/air/extension/20.0">
    <id>com.rainbowcreatures.FWEncoderANE</id>
    <versionNumber>1</versionNumber>
    <platforms>
	<platform name="Android-ARM">
		<applicationDeployment>
			<nativeLibrary>FlashyWrappers.jar</nativeLibrary>
			<initializer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</initializer>
			<finalizer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</finalizer>
		</applicationDeployment>
	</platform>
	<platform name="Android-ARM64">
		<applicationDeployment>
			<nativeLibrary>FlashyWrappers.jar</nativeLibrary>
			<initializer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</initializer>
			<finalizer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</finalizer>
		</applicationDeployment>
	</platform>
	<platform name="Android-x86">
		<applicationDeployment>
			<nativeLibrary>FlashyWrappers.jar</nativeLibrary>
			<initializer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</initializer>
			<finalizer>com.rainbowcreatures.FlashyWrappersAndroidHW.FlashyWrappers</finalizer>
		</applicationDeployment>
	</platform>
    </platforms>
</extension>

Overall, I'd suggest testing with the free version as much as possible before you commit to a purchase as there has been no testing going on my side for several years.
Thanks!
Pavel

Hi,
Thanks for the reply.
Second point is still not very clear. I have added free version of Flashy Wrapper in Android AIR app to record mp4 video. It gives me mp4 output as expected. Will I get same mp4 output if I purchase FW "Standard"?

Hello there,
You're welcome (and sorry for the delay of 2 days). Android is not included in Standard. It's included in the Free version, so everyone can try it out, and then in the Premium version. If you wish to further discuss we can continue at info at flashywrappers.com rather than here.

Thanks!

ok thanks.closing this now.

Hi,
We have purchased FW Premium but have not received any code files yet. Our email id is<EMAIL_ADDRESS>Please send the code files.
Thanks!

Hi,
We have purchased FW Premium but have not received any code files yet. Our email id is<EMAIL_ADDRESS>Please send the code files.
Thanks!

Finally, you emailed me :) GitHub is not great for these sorts of requests. Thanks!


emoji dataset is settled to 4 parts, and every parts is filled with a constant color, does this mean im2vec can only deal with

Great job first. But after learn and run your code for several weeks, I found that Emoji dataset is settled to 4 parts in your code, and every parts is filled with a constant color and a certain path in non-verbose mode. does this mean im2vec can only deal with very simple images and must pre-set how many parts the image have and which certain color each part use?

each single image in emoji dataset is seperated into 4 parts. and the number 4 is pre-setted

In the im2vec paper, the authors have provided results for more complex shapes.  In Section 3.4 of the  paper, they have mentioned that for a given training dataset,  they  segment the samples and cluster the segments based on the spatial position by assigning a different color to each cluster. Perhaps for the emoji dataset, they have used 4 clusters. It appears from the paper that the number of segments/clusters varies with the complexity of the topology of the samples in different dataset, but it may be fixed for a given dataset. Perhaps  im2vec can be trained by combining different datasets (for e.g. emojis and icon dataset).

Hey @eveybody2
Thank you, yes you are right we use 4 parts in the code and every part is filled with a constant color. This helps the network converge in a more stable manner. When there are multiple paths with the same color the gradients can get noisy.
Yes also as you observed such coloring preprocessing would mean that it would be hard for the method to handle complex shapes with numerous paths. While the method can work with a few complex shapes out of the box, getting it to work with complex shapes consistently is still an open problem.
Regards,
Pradyumna.

Thanks a lot. I think the Fundamental problem is how to make color differentiable in differentiable rasterization. must find a robust and stable way to  bp the gradients for variable color, if our ultimate goal is to vectorize natural image in deep learning.

or maybe it's proved to be Unsolvable in xml based representation like svg. Then we'll need to invent a new representation  for vector graph.


v6.0.6 fails to build with latest XCode v10.2 (10E125)

I updated to the latest XCode release version 10.2 (10E125) today, and we're getting some build errors from the Iterable-iOS-SDK pod (v6.0.6) now when we build our project.  Can you get out a new release that fixes these errors?
It looks like the compiler is flagging the typedefs created in the IterableConstants.h file.  Since one of those has the _Nullable type applied to it, it expects that all of the other typedefs in that file have either _Nullable or _Nonnull applied to them.  So to fix this, we just modified line 24 to remove the use of _Nullable:
typedef void (^OnFailureHandler)(NSString *reason, NSData * data);

Of course the other fix would be to apply _Nullable or _Nonnull correctly in that file on all the typedefs, but I'll leave that to you to determine how you want to fix it.

Thanks for bringing this to our attention. We are taking a look at this issue. We expect to release a new version by the end of this week.

We are only seeing warnings and not errors for the issue that you mention. Maybe you have “Treat Warnings as Errors” flag set. We are still hoping to release a new version soon.

Ah, you're correct we have that set. Thanks for looking into it.  It's not blocking us, but glad to hear you may clear up those warnings in a new release. Thanks!

Having this issue if compiled via carthage as well

We will be releasing a version to address this soon.

Just released 6.0.7. It should take care of the warnings.


job run status incorrect

try to stop the job and restart but the job status still status

Do you mean still 'READY' status ?
Have you ever tried to refresh the page ?


ARM64 Image is needed.

Since the dawn of AWS ARM processors  - VM's are providing much more realibility and value for money than X86 processors.
The current build images does not support ARM64 - We need to find a way to push both the images on Dockerhub.

I have created an ARM64 Image and pushed it to Dockerhub - kaumudpa/calcom

@kaumudpa could you explain how you built the image for ARM64 ?

@kaumudpa how did you get the image to build ? I'm trying on an M1 mack and so far no luck.

This typically just needs the platforms config in the Github Action build step to include linux/arm64.
- platforms: linux/amd64
+ platforms: linux/amd64,linux/arm64

See platforms config options in the build action docs.
https://github.com/docker/build-push-action
And the platforms supported by Docker Buildx.
https://docs.docker.com/reference/cli/docker/buildx/build/#platform
Another two options are you can 1) build the image on your machine using the instructions in the readme, or 2)  you can override your machine from trying to pull an ARM image by adding that same platform flag to the docker-compose.yaml in this repo (except in reverse of the above suggestion).  You can do that by adding the platform config option to the calcom block (except set it to linux/amd64 instead) and that will tell your machine pull the non-ARM build that this repo builds/pushes.  Performance won't be as good on your machine, but this is just a local dev testing thing anyway.
# docker-compose.yaml

  calcom:
    image: calcom/cal.com:4.2.3
    platform: linux/amd64  # tells it to pull the non-ARM build from this repo
   ...

I personally prefer to just build the image on my machine so it's using the native CPU.  You really only have to do it once every time a new release is pushed.  Or... someone could just put platforms: linux/amd64,linux/arm64 in the GH action and everybody would get what they need.

Just pushed another ARM image to dockerhub - 4.3.5

Hi. platform: linux/arm64  option doesn't work.
Error Message and Logs
/usr/local/bin/docker-entrypoint.sh: exec format error

I'm running coolify on ubuntu, arm architeture on hetzner
I believe this line is the problem in docker compose file
platform: linux/amd64
I've changed to
platform: linux/arm64
I simply installed calcom on coolify.
calcom instance keeps restarting (unhealthy)
Steps to Reproduce

search calcom on self-hosted coolify(ubuntu, arm architeture on hetzner) and install

Operating System and Version (self-hosted)
Ubuntu 22.04 on arm
https://github.com/coollabsio/coolify/issues/4591
I see this.
# Temporarily disable ARM build due to runner performance issues
# - name: Set up QEMU
#   uses: docker/setup-qemu-action@v2
https://github.com/calcom/docker/blob/8547540643641df61b6ba39044008a92c08b66d0/.github/workflows/docker-build-push-dockerhub.yml#L95


button group stops working on resize

Hello I have added button group to my new website and it seems that two first buttons stop working on smaller screens ? Also if I remove text-center div they all stop working.
http://danielszweda.azurewebsites.net/
Any help would be appreciated.

for support questions please use stackoverflow.

Yes, as per https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker support requests should be directed at StackOverflow or similar.
I'll give you a starter though: the buttons don't work because they're overlapped by the sidebar which swallows the clicks.

I will make sure to post it to stack next time :) Thanks for your help ! :+1:


Selectable certificate chain verification

Need to provide the ability to verify certificate chains, both for the TCB certs and the PCK cert chain contained in the quote bytes, https://download.01.org/intel-sgx/latest/dcap-latest/linux/docs/Intel_SGX_ECDSA_QuoteLibReference_DCAP_API.pdf#[{"num"%3A75%2C"gen"%3A0}%2C{"name"%3A"XYZ"}%2C69%2C687%2C0]
This ability needs to be specified per client, but an implementation that works inside of an enclave needs to be provided.

[x] #92
[x] #93
[x] #94
[x] #95

Brought in Mbedtls for use in enclaves or for other clients that wish to re-use the logic


External/standalone version of the editor

Describe the feature / enhancement and how it helps to overcome the problem or limitation
Being able to use the timeline editor outside of Godot would be nice. Godot doesn't like plugins very much and we keep running into annoying issues associated with that so having an option to use the plugin as standalone would help in those scenarios where Godot does not cooperate.

This is interesting but we'll need A kind of UI prototype for it


yubikey-manager-qt: 1.1.5 -> 1.2.2

Motivation for this change
fixes https://github.com/NixOS/nixpkgs/issues/122575
Things done

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

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

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

I don't know whether pcsclite and yubikey-personalization are still needed. I get
WARNING: PCSC not available. Smart card protocols will not function.

when running ykman-gui.
yubikey-manager should be moved under pythonPackages and the libraries' paths should be hardcoded by patching the source code.
cc @benley @Mic92
cc @wakira

Result of nixpkgs-review pr 123118 1

1 package built:

yubikey-manager-qt

Confirming that this upgrade fixes the issue. :+1:
I think this should be included into the 21.05 release, ping @NixOS/nixos-release-managers
ZHF: #122042

I don't know whether pcsclite and yubikey-personalization are still needed. I get
WARNING: PCSC not available. Smart card protocols will not function.

when running ykman-gui.

According to the 1.2.0 release notes, ykpers is no longer needed:
* Version 1.2.0 (released 2021-03-16)
 ** Compatibility update for ykman 4.0.
  *** ykman >= 4.0 now required.
  *** Drop dependencies on libusb and libykpers.

So we could drop this dependency.
For pcsc, I think that's still required. I don't got such a warning when running ykman-gui... (I have the pcsc service enabled and activated the ccid plugin).


stream was reset: NO_ERROR

Summary
I am creating a client like so
        client = ApolloClient.builder()
            .serverUrl(Env.get(EnvVars.HUB_GQL))
            .build();

but when running any sort of request, it fails with
com.apollographql.apollo.exception.ApolloNetworkException: Failed to execute http call for operation 'getArticles'
	at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$executeHttpCall$1.onFailure(ApolloServerInterceptor.kt:107) [apollo-runtime-2.5.9.jar:2.5.9]
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:211) [okhttp-3.12.11.jar:?]
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) [okhttp-3.12.11.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: okhttp3.internal.http2.StreamResetException: stream was reset: NO_ERROR
	at okhttp3.internal.http2.Http2Stream.checkOutNotClosed(Http2Stream.java:644) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http2.Http2Stream$FramingSink.emitFrame(Http2Stream.java:578) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http2.Http2Stream$FramingSink.write(Http2Stream.java:558) ~[okhttp-3.12.11.jar:?]
	at okio.ForwardingSink.write(ForwardingSink.kt:29) ~[okio-2.9.0.jar:?]
	at okhttp3.internal.http.CallServerInterceptor$CountingSink.write(CallServerInterceptor.java:149) ~[okhttp-3.12.11.jar:?]
	at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:255) ~[okio-2.9.0.jar:?]
	at okio.RealBufferedSink.write(RealBufferedSink.kt:152) ~[okio-2.9.0.jar:?]
	at okhttp3.RequestBody$1.writeTo(RequestBody.java:73) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:72) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) ~[okhttp-3.12.11.jar:?]
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) ~[okhttp-3.12.11.jar:?]
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:257) ~[okhttp-3.12.11.jar:?]
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:201) ~[okhttp-3.12.11.jar:?]
	... 4 more

Version
JDK 11
apollo.runtime 2.5.9
Description
I was following the basic examples, so I'm not sure this is even a bug, but I have no clue why the stream is closing?

Looks like your backend didn't like the query you're sending. I'd check on the backend if there are any logs or other things that could help diagnose this.

I closed the ticket because it's probably not a bug. But I'm still struggling. It appears to be related to the size of the request. When my query exceeds a certain limit (somwhere in the 2-digit kB), the socket read times out. When it's under, it works fine.


Unable to enforce encoding of stdin/stdout/stderr for non-TTY streams under 2.7.x

Interpreter: CPython 2.7.13
OS: Windows 7
RF: 3.0.2
As far as I understand the PYTHONIOENCODING environment variable can be used to enforce the encoding used when writing to stdout/stderr. It does not work however when stdout/stderr is redirected to non-TTY stream under python 2.7.
Following experiments performs print-based debugging. It will mangle the output, but will show the problem.

Modify console_encode function in robot\utils\encoding.py by adding simple print:

def console_encode(string, errors='replace', stream=sys.__stdout__):
    encoding = _get_console_encoding(stream)
    print('>> ' + encoding)
    if PY3 and encoding != 'UTF-8':
        return string.encode(encoding, errors).decode(encoding)
    if PY3 or IRONPYTHON:
        return string
    return string.encode(encoding, errors)

open cmd.exe
run c:\python27\python -m robot.run test.robot in the output on console you will see (in my case):

>> cp437

run c:\python27\python -m robot.run test.robot >out.txt in the out.txt file you get:

>> mbcs

set PYTHONIOENCODING=utf8
run  c:\python27\python -m robot.run test.robot

>> utf8

run c:\python27\python -m robot.run test.robot >out.txt

>> mbcs

So despite setting PYTHONIOENCODING to utf8 still mbcs is used when stream is redirected to file. This does not happen with python 3.6. Same scenario as above with python 3.6 results in:
>> utf8
>> cp1252
>> utf8
>> utf8

This whole problem comes from RED Robot Editor issue; https://github.com/nokia/RED/issues/160 . In RED we allow users to start tests from eclipse/RED. When python process is starting, its stdout/stderr streams are taken by parent process and read in order to display the output in Console view. Those streams are not TTY, so RF 3.0.2 under python 2.7 encodes everything using mbcs codec which results in characters being displayed wrongly since we're trying to decode them using utf-8 encoding.
From our point of view it would be the best if we could somehow tell robot that it should use utf8 encoding when doing output, so PYTHONIOENCODING variable could do it, however it only fixes the problem for us when python 3.6 is used.
The logic which finds encoding to use in RF 2.9.x was different and the characters were displayed properly when process was started from RED even without using PYTHONIOENCODING.

The code responsible on detecting the encoding is at https://github.com/robotframework/robotframework/blob/master/src/robot/utils/encodingsniffer.py
As you can see, Robot tries various approaches to find the encoding. First Robot tries to read encoding from sys.__stdout__.encoding but that doesn't work with Python 2 if outputs are redirected. The next attempt depends on the OS. On Windows Robot calls GetOEMCP method on the Windows API. The value it gets there doesn't take possible PYTHONIOENCODING into account.
One simple sounding solution would be Robot looking PYTHONIOENCODING if sys.__stdout__.encoding doesn't work. It would need to be tested does Python actually use the value set by PYTHONIOENCODING in that case, though.

Do you @michalanglart have ideas how to fix the problem on Robot side?

Hi,
to be honest I was occupied with different tasks and haven't looked into this since January. I'll try to take a look later this week.

Ok I had a look at this issue. In my opinion the problem is not located inside encoding detection done in encodingsniffer.py but rather in _get_console_encoding function in encoding.py module.  In case of python 2.x this function at line 76 will choose SYSTEM_ENCODING instead of CONSOLE_ENCODING for non-tty stream despite the fact PYTHONIOENCODING is provided.
If it would choose CONSOLE_ENCODING then the sys.__stdout__.encoding would be used which is properly set depending on PYTHONIOENCODING env variable. To sum up I would propose to make following change in this function:
def _get_console_encoding(stream):
    if PY3 or isatty(stream):
        encoding = getattr(stream, 'encoding', None)
        if encoding:
            return encoding
    return CONSOLE_ENCODING if isatty(stream) or 'PYTHONIOENCODING' in os.environ else SYSTEM_ENCODING

With function modified this way I was able to have same results as with python 3.x in the experiments above. Do you think this is acceptable as a fix for this issue?

Another idea I have is to leave encoding.py module as is but based on the fact that either CONSOLE_ENCODING or SYSTEM_ENCODING is chosen based on stream being TTY or not, we could change the way those two are computed. Overall the idea is to have both CONSOLE_ENCODING and SYSTEM_ENCODING initialized with encoding set in PYTHONIOENCODING variable.
Thus encodingsniffer may be modified:
def get_system_encoding():
    platform_getters = [(True, _get_enforced_encoding),
                        (True, _get_python_system_encoding),
                        (JYTHON, _get_java_system_encoding),
                        (UNIXY, _get_unixy_encoding),
                        (WINDOWS, _get_windows_system_encoding)]
    return _get_encoding(platform_getters, DEFAULT_SYSTEM_ENCODING)

def get_console_encoding():
    platform_getters = [(True, _get_enforced_encoding),
                        (True, _get_stream_output_encoding),
                        (UNIXY, _get_unixy_encoding),
                        (WINDOWS, _get_windows_output_encoding)]
    return _get_encoding(platform_getters, DEFAULT_CONSOLE_ENCODING)

def _get_enforced_encoding():
    if 'PYTHONIOENCODING' in os.environ:
        # value of PYTHONIOENCODING can be given with syntax: encodingname:errorhandler
        encoding = os.environ['PYTHONIOENCODING'].split(':')[0]
        if _is_valid(encoding):
            return encoding
    return None

@pekkaklarck Any of those two ideas makes sense to you? Or possibly there is another way to enforce Robot to use encoding provided with PYTHONIOENCODING??

I would say IMO first proposal is better. It clearly states, that CONSOLE_ENCODING is used whenever stream is TTY or when user enforced encoding with PYTHONIOENCODING.
In this second proposal code semantics is broken because when PYTHONIOENCODING is set we return it in get_system_encoding function which should return encoding used by the underlying file system, but PYTHONIOENCODING has actually nothing to do with file system - it only overrides stdin/stdout/stderr encodings.

This requires a bit more thinking and I don't have time for that at the moment. I feel the change would anyway be too risky for a minor release, especially when we want to get RF 3.0.3 out ASAP, but I add this initially to RF 3.1 scope.

Ok, lets leave that for 3.1.
If you will revisit this issue in the future please have a look at potential solutions I've described above. I can provide Pull Request once we agree what can be changed.

There are encoding detection problems also when using Python 3.6 on Windows due to it using UTF-8 as the console encoding. This encoding works fine if using Python API to communicate with the OS, but if we get content from the system as bytes and try to encode it as UTF-8 it fails due to Windows not really using it. Getting all this right may require larger changes and possibly also a separate issue.

This issues is caused by Robot not even looking at stream's encoding when using Python 2 and the stream is not a TTY. The reason is that typically the encoding is None in that case, and with IronPython and Jython the encoding is set incorrectly. It turned out that the encoding is always set if PYTHONIOENCODING is enabled and that also makes the encoding correct with Jython. I got a fix with tests ready.


Added new ability types

#21

Pull Request Test Coverage Report for Build 839808189

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.618%

Totals

Change from base Build 838993106:
0.0%

Covered Lines:
942

Relevant Lines:
946

💛  - Coveralls


What triggers isExpense?

Hi @webschik,
I am using your parser, works really well. I was just wondering, what exactly sets isExpense true or false?
When I am parsing a file containing only incomes, isExpense still is set true.
I saw from your code, that you scan for certain codes (e.g. 'N060'). So is the array maybe incomplete?
The transaction codes in my file are like 'NMSC' or 'NSTO'.
Cheers

Anything about that..?

Hi @ruben-with-b !
incomeTransactionCodes list is not complete, indeed.
It's possible to update this list based on codes from https://www-2.danskebank.com/Link/Mt940sapUK/$file/Mt940_sap_UK.pdf, PRs are welcome ;)
Be aware that NMSC stands for Miscellaneous, so based on this code it's not possible correctly if it's income or expense.


chore: Create CODE_OF_CONDUCT.md

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


some cleanups

The zkey related changes look good to me.

The commit message regarding the LOADLIBES var has been updated, and the whole PR rebased on top of master.


[Initializers] Refactor random and variance-scaling initializers

Summary
Random Initializers

Removes bug caused by redundant distribution computations in randomUniform and randomNormal BinaryFloatingPoint typed initializers.
Adds a temporary truncatedNormal initializer based on the Raw.statelessTruncatedNormal until a dependency-free one is implemented in Random.swift.
Adds tests, testRandomUniform(), testRandomNormal(), and testTruncatedNormal().

Variance-Scaling Initializers

Refactor computation of fans, fanIn and fanOut.
Add paper references to glorot initializers.
Update glorotNormal to use truncatedNormal initialization.
Add tests, testGlorotUniform() and testGlorotNormal().

The error here is
/swift-apis/Tests/TensorFlowTests/LayerTests.swift:366: error: LayerTests.testRNN : XCTAssertEqual failed: ("[[[ 0.20775774,  0.20080023, -0.13768704, -0.18534681]], [[ 0.22666009,  0.30019346, -0.19720285,   -0.146838]], [[ 0.23758982,  0.32101023, -0.20359214, -0.17870961]], [[ 0.24337786,  0.33891943, -0.21143381, -0.16750808]]]") is not equal to ("[[[ 0.20775771,  0.20080023, -0.13768704, -0.18534681]], [[ 0.22666009,  0.30019346, -0.19720285, -0.14683801]], [[ 0.23758979,  0.32101023, -0.20359215,  -0.1787096]], [[ 0.24337786,   0.3389194, -0.21143384,  -0.1675081]]]") -

But i thought we commented out the RNN tests due to variation of outputs.

@eaplatanios All initializer tests pass. Thanks for your help and time!
The only problem left is in the LayerTests suite in which testSequential  fails due to expected values being off by roughly -0.02. I assume this is because of the change in implementation of glorotUniform and glorotNormal where, previously, the samples were scaled by 2 in the minusOneToOne variable. May you please explain the reason behind the scale and shift of drawn samples in let minusOneToOne = 2 * randomUniform - 1?

@jon-tow thanks for addressing all the comments! :)
I am not sure why the samples were being scaled and shifted as I did not implement this, but tomorrow I can look into whether your current implementation is correct.

@eaplatanios Is there any update on this? Thanks.

Hi, looks like there was a CI failure on this one. Could you take a look? Once we get CI passing, this should be ready to merge!

Hey @marcrasi! Everything should be good to go. Let me know if anything needs to be addressed. :)

It looks like this has broken LayerTests.testRNN, LayerTests.testLSTM, and SequentialTests.testSequential because they depend on specific initialization values that have changed. Is it expected that the values change? If so, updating the constants in those tests should be good.

It is expected. The previous implementations of Tensor(glorotUniform:) and Tensor(glorotNormal:) scaled and shifted drawn samples prior to variance scaling. I'm not sure what the reasoning was behind this and haven't seen it mentioned in any of the initialization literature.
I've updated the hardcoded values in the tests you've mentioned. :)

This passes locally but the kokoro build results show a discrepancy between values and expected-values in only the least significant digits. This is probably just a difference in float precision round-off. I'm going to add a bit of accuracy tolerance in the equality assertions to remediate this for now.

Yay, it passed, thanks! Merging.

No problem! Thanks for the help :)


Spacing before/after an inline element creates a non-breaking space

When spacing before/after an inline element, a   is erroneously produced instead of a normal space. Appears to be a TinyMCE bug.
Reported here: tinymce/tinymce#3057

i did some regex on the helper functions to clean this out


Modifications to work with Flask 3.0.0

Fixes # .

Modifications required to enable connexion to work with flask 3.0.0

Changes proposed in this pull request:

Flask Blueprint requires a name, that is not an empty string. Thus, I add a condition to handle the case of empty string
I updated the relevant testcase accordingly

Right, thanks @RobbeSneyders for pointing that out. It seemed that your proposed is a more comprehensive solution to this problem.
I will close this PR.

No worries, I'll go ahead and merge it and release it as a new version.


fix(core): fix animation retrigger in submenu

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?

Closes #421
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Do not merge it please until @waterplea review


setup github actions to build quarto website

looks like this should be doable via these resources:

https://github.com/r-lib/actions/tree/v2/examples#build-bookdown-site
https://github.com/quarto-dev/quarto-actions

easier to get up and running than I imagined


Features/bun setup

Just temporary PR for elapsed time measurement of NodeJS vs Bun.
It would be closed soon.

@samchon
I'll create a PR to split the jobs so that you can see the time difference

I'll added the workflow option
Wait a moment

I created a new one.
Sorry for confusing
https://github.com/samchon/typia/pull/1097


inrole requires MentionEveryone permission

Is this intentional? The code is there, but there doesn't seem to be any reason for it. Unlike mentionrole, it just lists usernames, and it's useful for users who might not have permission to mention everyone to look up other tags; e.g., finding a group of people who use a certain self-assignable tag.

It's probably a leftover because i copy pasted it from menrole i guess. Will fix it asap.

5db12144409b7251c0b271ea990f89b0d90993ad


Some question about the pytorch implementation

Hi, I modified your code for pruning a ResNet18 model trained on CIFAR10 datasets, I was confused with the function adjust_mean_var in utils.py. In your code you put model in train but no backward operation in this function, what does this code do?

Hi,
Thanks for using our code.
This function is to adjust the running mean and variance of the BN layers in the pruned model. This calibration of BN parameters is important for performance.
Forward is sufficient for only running mean and variance is needed.
Best regard,
Shangyu

发件人: chamboin @.>
发送时间: Monday, March 15, 2021 3:32:48 PM
收件人: csyhhu/L-OBS @.>
抄送: Subscribed @.***>
主题: [csyhhu/L-OBS] Some question about the pytorch implementation (#14)
Hi, I modified your code for pruning a ResNet18 model trained on CIFAR10 datasets, I was confused with the function adjust_mean_var in utils.py. In your code you put model in train but no backward operation in this function, what does this code do?
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/csyhhu/L-OBS/issues/14, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3I2M6M4WUF45FV2UAMQQDTDWZ2BANCNFSM4ZF76ABA.

Hi,
Thanks for replying to my previous question.
now I encounter overflow issue with the prune process, the hessian inverse of fc layer and layer3.conv are up to 1e6 and larger, I have no idea about how to solve this...
Not sure if it because I used an modified ResNet18 model...

Hi,
Sorry for replying late. You may try Woodbury method by setting ```use_Woodbury''' as True. If you have already use this method, try to disable it.
L-OBS may face numerical problem, try to use Woodbury or not use it.
Best regards


updated yargs package to 13.1.0 version

PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
There is a vulnerability in yargs package, because its version is old.
https://app.snyk.io/vuln/npm:mem:20180117
What is the new behavior?
I updated the version of the yargs package. Vulnerability should not be.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

I'm not sure.
Other information
You are using the old version of the yargs package, which at that time used the old version of the os-local package, which used the vulnerable version of the package mem.
https://app.snyk.io/vuln/npm:mem:20180117
Reviewers
@MartynasZilinskas @DovydasNavickas

Hey @MaksPob, thanks for the PR. Can you bump minor version as well?

Hey @MaksPob, thanks for the PR. Can you bump minor patch version as well?

Hi @MartynasZilinskas! Ok i did it;))I understood you correctly?))

@MaksPob Thanks. 👍


Reading raw socket headers

The is currently no way to read or set headers on raw sockets.

nanomsg doesn't really give a good API for this under the hood.  There is the cmsg API, but really you want a different API altogether.  Another reason to recommend mangos, it has a more clearly thought out API here, that is more natural for Go.


[C++][DONOTMERGE] Rebased clone of #13661 created for benchmarking purposes

@ursabot please benchmark lang=R


Impossible to reinstall Franz on windows 10.0.17763.1098

Had Franz 5.4.0 installed on windows 10.0.17763.1098 and working fine. Got a notice for a updated version 5.5.0 featuring new "hibernation" mode. Decided to give it a try and went for the update.
After installing update, Franz won't start anymore. Running the app gives an error popup stating "This file does not have an app associated with it for performing this action".
Tried several reboots => no luck.
Tried several updates to 5.4.0 => no luck.
Tried uninstalling 5.4.0 =>uninstaller hanged up.
Killed the uninstaller from the task manager and rebooted. Tried again => same issue.
Ended up rebooting, deleting /users/xxx/appdata/local/programs/franz, then reboot again.
After reboot, attempted fresh install of 5.4.0 => Installer freezes right after launch they hangs forever.
Killed installer from task manager, then reboot.
Retried several times => no luck.
Ended up rebooting one last time, copied the /users/xxx/appdata/local/programs/franz folder from another machine (was running 5.3.3 I think, not sure), then ran the update to 5.4.0, and boom, voilà, it worked.
Don't know what happened here, but that's quite odd.

How do I even find the uninstaller? Franz keeps popping up and I cannot figure out how to remove it from my Windows as well.


Purchase date warning caused by returned data from Snipe

https://github.com/ParadoxGuitarist/jamf2snipe/blob/4264dda403b878ac1bcdb190c9cfec2f69f44bb9/jamf2snipe#L447
I was troubleshooting why I'm getting these warnings when the purchase date is set correctly.
This particular line is comparing the input versus what's returned from Snipe after.
It fails on Purchase Date because it's sending YYYY-MM-DD but getting back YYYY-MM-DD 00:00:00.
u'2015-04-25' vs u'2015-04-25 00:00:00'
It is setting the attribute, just not validating it correctly.

I think I have this fixed with https://github.com/ParadoxGuitarist/jamf2snipe/pull/56

Yep, merged! Thanks! (sorry it took so long)

Yep, merged! Thanks! (sorry it took so long)


mirage.io moves to mirageos.org

Please check and test carefully, since I don't have a clue on how such a rename should be done, and whether any other steps are necessary. Thanks a lot.
Reference: https://github.com/mirage/mirage-www/pull/845
Note: the DNS entries for ci.mirageos.org and deploy.mirageos.org are already established.

Also, I'm not sure which branch this should be PRed to -- somehow there's a live-mirage branch that is 74 commits behind the main branch...

The PR needs to go to master as you have it.  There are three different deployments from this repo, so we have three live- branches so we can target the update to the specific instance.  Therefore, we will also push this to live-mirage.
We will need to update the Caddyfile and Docker stack to reflect these changes as well.  I'll do that now and then commit the PR.

Thanks mark. There's also https://github.com/ocurrent/mirage-ci/pull/48 related to this PR.

I wonder, somehow new PRs such as https://github.com/mirage/mirage-skeleton/pull/405 don't seem to trigger the mirage-ci anymore. I don't quite understand how the CI is triggered, but is there something that potentially needs to be changed?

The notifications from the a GitHub app.  The payload deliveries failed as they hit a HTTP 301 and GitHub doesn't follow redirects.  I have updated the delivery URL so this should be working as expected now.

The notifications from the a GitHub app. The payload deliveries failed as they hit a HTTP 301 and GitHub doesn't follow redirects. I have updated the delivery URL so this should be working as expected now.

Thanks for your investigation and fix. I adapted on mirage/mirage-dev mirage/mirage and mirage/mirage-skeleton these webhooks. The latter one still claims to have received a 301 (with the url now pointing to ci.mirageos.org)...

Does the 301 persist when you redeliver the payload?  If so, we should investigate further.

I don't know how to redeliver the payload. There's no "test" button I can see, only an edit and delete. I can add a commit to the PR...

ok - it must be different on a webhook.  On the GitHub Application, there is a 'redeliver' button against the failed deliveries.

good news, it worked now (pushing another commit, the webhook says it was successful, and CI is there) :)


make host module public

In lucet we use some of the constants defined in (the predecessor in lucet-wasi of) this module. This PR makes wasi_common::host public and converts all of the definitions in that module from pub(crate) to pub.

I have some ideas for how we could refactor host, but I expect the basic functionality it provides will continue to be available in any case, so this seems fine to me.

IMO the distinction between wasm32 and host is quite confusing. Probably it's a good idea to mention some rules of a thumb when which of those modules should be used.

@marmistrz To provide you with some context, I've had this chat with @sunfishcode a while back, and we generally agreed that there is little reason to have two separate modules host and wasm32 which essentially expose the same constants, structs, etc. Hence, there is a plan to unify the two, we just didn't get around to it yet ;-)

https://github.com/CraneStation/wasi-common/pull/151 is now a PR showing one possible approach.

I'm going to close this - I got rid of lucet's dependency on this module temporarily. I can add it back in once we've engineered a way forward.
Right now I really like the way #152 is moving this forward - we really should be able to generate both the C ABI level constants / type aliases, and idiomatic rust structs / enums, and the translation routines between them, all from the witx descriptions of WASI. That will be a big improvement for this library and validate that the effort we're putting into witx is worthwhile :)


ReferenceError:  overwrite config of Plugin

from: https://github.com/azu/textlint-plugin-JTF-style/pull/5#issuecomment-154417503
try to set the following and textlint throw ReferenceError.
{
  "plugins": [
    "jtf-style"
  ],
  "rules": {
    "jtf-style/2.1.2.漢字": {
      "severity" : "warning"
    },
    "jtf-style/4.1.1.句点(。)": false,
    "jtf-style/3.1.1.全角文字と半角文字の間": false
  }
}

Error mesasage:
[ReferenceError: rule: jtf-style/2.1.2.漢字 is not found]

But, following case is safe.(no error)
  "rules": {
    "jtf-style/2.1.2.漢字": true,
    "jtf-style/4.1.1.句点(。)": false,
    "jtf-style/3.1.1.全角文字と半角文字の間": false
  }

It seem bug in textlint. @ https://github.com/textlint/textlint/blob/93a70ddcbc79fef1390b5010d5a1ac7edbb78a1a/src/textlint-engine.js#L150

Does https://github.com/textlint/textlint/blob/93a70ddcbc79fef1390b5010d5a1ac7edbb78a1a/src/textlint-engine.js#L143-L145 has a bug?(<plugin>/<rule> is pass the line)


Does the modifiers supports 'capture' for event capture

No.
FYI, https://github.com/wonderful-panda/babel-plugin-vue-jsx-modifier


Rename "Medical suppliers" link to  "Hospital and Suppliers" in the footer

Is your feature request related to a problem? Please describe.
The medical suppliers should be renamed as "Hospital and Suppliers"

Sure


Remove getText() from ProjectionSegment

Fixes #4652.

Pull Request Test Coverage Report for Build 2024

7 of 77 (9.09%)  changed or added relevant lines in 19 files are covered.
134 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.1%) to 59.019%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/sharding/rewrite/token/generator/impl/OrderByTokenGenerator.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/segment/dml/item/AggregationDistinctProjectionSegment.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/segment/dml/item/AggregationProjectionSegment.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/segment/dml/item/ColumnProjectionSegment.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-mysql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/MySQLVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-oracle/src/main/java/org/apache/shardingsphere/sql/parser/visitor/OracleVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-postgresql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/PostgreSQLVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-sql92/src/main/java/org/apache/shardingsphere/sql/parser/visitor/SQL92Visitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-sqlserver/src/main/java/org/apache/shardingsphere/sql/parser/visitor/SQLServerVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dml/SelectStatementContext.java
2
6
33.33%

Files with Coverage Reduction
New Missed Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dml/SelectStatement.java
5
10.53%

shardingsphere-sql-parser/shardingsphere-sql-parser-oracle/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/OracleDMLVisitor.java
22
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-sql92/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/SQL92DMLVisitor.java
22
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-sqlserver/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/SQLServerDMLVisitor.java
22
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-mysql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/MySQLDMLVisitor.java
29
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-postgresql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/PostgreSQLDMLVisitor.java
34
0%

Totals

Change from base Build 1016:
0.1%

Covered Lines:
12122

Relevant Lines:
20539

💛  - Coveralls


FF10/iOS 4.3 Safari: Candy only shows one line of history

I reproduced this in the iOS Simulator but not in FF10.
I'll ask the one who encountered this one in FF10 if he can show us a debug output.

This reminds me of an issue (#10) with date parsing. There was a problem with the Candy.Util.iso8601toDate method.
https://github.com/candy-chat/candy/blob/master/candy.bundle.js#L816

yeah that maybe a similar issue..

How did you reproduce this?
For me it works like a charm in iOS (4.3.2, simulator), despite the fact that the UI is totally broken ;-)

Well I just opened the page ;)
I'll reproduce it later this week maybe.

@pstadler I think this should be fixed now as you added a try chat to the sound play..
Maybe we should add a html5-audio tag as a fallback for mobile & modern browsers


Support remote.vault in prometheus.exporter.postgres

Hi,
I'm trying to form a connection string with data from vault:
local.file "vault_token" {
  filename  = "/xxx/yyy"
  is_secret = true
}

remote.vault "postgre_metrics_read" {
  server = "https://vault.zzz.xx"
  path   = "kv-monitoring/zz/ww"
  auth.token {
    token = local.file.vault_token.content
  }
}

prometheus.exporter.postgres "local" {
  data_source_names = ["postgresql://nonsensitive(remote.vault.postgre_metrics_read.data.username):nonsensitive(remote.vault.postgre_metrics_read.data.password)@pg-01.zzz.xx:5433/postgres?sslmode=disable"]
  }

and I get the result:
Oct 31 13:11:12  alloy-linux-amd64[3904687]: ts=2024-10-31T10:11:12.246424308Z level=error component_path=/ component_id=prometheus.exporter.postgres.local err="Error opening connection to database (postgresql://nonsensitive%28remote.vault.postgre_metrics_read.data.username%29:PASSWORD_REMOVED@pg-01.zzz.xx:5433/postgres?sslmode=disable): pq: password authentication failed for user \"nonsensitive(remote.vault.postgre_metrics_read.data.username)\""
but how do I get a connection string using vault??? It is supported?

Your remote.vault is not replace because everything is between quotes. It's a literal string.
You can use the string lib to generate strings.

@clementduveau
Thank you very much, I'll definitely try it!


Steam can't download games because "not connected to the internet"

Describe the bug
While on Game Mode, I'm connected to the Wi-Fi with internet and can't download games. I can on Desktop mode.
What did you expect to happen?
I expected to be able to download new games from the Game Mode environment.
Output of rpm-ostree status
No response
Hardware
ROG Ally X
Extra information or context
No response

From my experience (on the legion go) this is steam being dumb and it thinks it is in offline mode or something, it is fixed by setting steam into offline mode then back to online mode.


adding Russian translation

I have nothing to add here, Russian tranlsation for a plugin. Na zdorovje!

Perfecto, thanks!


Upgrade falafel to ^2.1.0, use ecmaVersion 8

Background: substack/node-browserify#1667
Also depends on substack/node-falafel#62 for full async/await support (merged)

Codecov Report

Merging #122 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #122   +/-   ##
=======================================
  Coverage   97.18%   97.18%
=======================================
  Files           2        2
  Lines         142      142
=======================================
  Hits          138      138
  Misses          4        4

Impacted Files
Coverage Δ

transform.js
98.73% <100%> (ø)
:arrow_up:

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 7ce5f1d...1b2dda5. Read the comment docs.

looks good to me!
@timwis, did you mean to commit that yarn.lock file? i'm not against yarn, but we don't have any precedence for using it here, so wonder if we should add that or not.

@ahdinosaur not sure how I missed your response months ago, but I've removed yarn.lock - my bad!

v6.1.1 :tada:


I hope EF7 will be able to support DB First or Model First

I Love EF very much,  We use it with DB First in my work . From a China developers.

If you have not already, you may be interested in reading the the article, EF7 - What Does “Code First Only” Really Mean, for more information on the plans.

The blog post that @vossad01 linked to has details on what we are supporting. Generating from an existing database will be supported (some early code is already checked in for this) but the EDMX file format will not be.


Add sage?

The sagemath stack is available from conda-forge for osx and linux. It's probably worth exploring.

With anaconda in the mix: the conda solve didn't complete (even with errors) within an hour. Presumably we'd have to go conda-forge only...

Turns out the issue is sage requiring jsonschema <3 and jupyterlab_server requiring jsonschema >3

Fixed by #13 (for some platforms)


Make it possible to mmap on Windows

Fixes https://github.com/nakabonne/tstorage/issues/8

Codecov Report

Merging #9 (52968c0) into main (70a15ff) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
+ Coverage   63.00%   63.13%   +0.12%
==========================================
  Files          15       17       +2
  Lines         592      594       +2
==========================================
+ Hits          373      375       +2
  Misses        169      169
  Partials       50       50

Impacted Files
Coverage Δ

disk_partition.go
28.00% <100.00%> (-7.72%)
:arrow_down:

internal/syscall/mmap.go
100.00% <100.00%> (ø)

internal/syscall/mmap_unix.go
100.00% <100.00%> (ø)

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 0f2363b...52968c0. Read the comment docs.


refactor: add web3 timeout 5 min

What I did
Timeout errors would occur frequently during transaction tracing (10 sec default) on a mainnet-fork. Extending the time to 5 mins should reduce the frequency of timeout errors.
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

I did some digging and learned things.
I feel like this is not 100% the right thing to do...
The node is set to timeout a 30 seconds: https://github.com/ethereum/go-ethereum/blob/053ed9cc847647a9b3ef707d0efe7104c4ab2a4c/rpc/http.go#L99
And brownie defaults to 30 second timeout to match this:
https://github.com/eth-brownie/brownie/blob/master/brownie/network/web3.py#L47
Is this only slow when using fork provider?
More digging, we need.

OK, I have concluded that I think the fork networks should default to the several minutes to account for the cross-network web2 communication with Alchemy.
And the solely-locally running networks should default to 30 seconds.

Closing in favor of this: https://github.com/ApeWorX/ape-hardhat/pull/56
I hope that is ok! I appreciate you opening this PR but I need this (am blocked) and I want to make sure its done correctly as well


docs(rfc): a new intermediary model to support whitespace collapsing

Checks

[X] I have read the contribution guidelines regarding Pull Requests here: https://git.io/JJ0Pg

Description
This RFC specifies a set of algorithms and internal logic changes necessary to implement whitespace collapsing (#216).

Codecov Report

Merging #421 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #421   +/-   ##
=======================================
  Coverage   63.61%   63.61%
=======================================
  Files           6        6
  Lines         437      437
  Branches      137      137
=======================================
  Hits          278      278
  Misses         64       64
  Partials       95       95

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 9f7168b...aafb583. Read the comment docs.


Add the ability to edit next of kin phone numbers

Update phone number that will be of 8 digits in length, starting with 8 or 9

Issue closed as this has already been implemented in AB3.

The issue has been modified to avoid confusion with existing functionality.

Resolved by #103.


Emmet toggle comment on multiple cursors should not comment nodes that are children of other nodes being commented

Since it looks like we actually fetch the nodes (https://github.com/Microsoft/vscode/commit/1d93668c0e5e8bf91aa70f92c998bd34d548c2e7), we can probably ensure that children of other nodes being commented are not included. This will prevent the following case:

I expect the following result:
/*.foo {
    display: block;
}*/
/*.bar {
    .foo {
        display: block;
    }
}*/

For May, I have reverted back to using old emmet for toggle comment as the toggle comment feature in the new emmet needs more work.
See https://github.com/Microsoft/vscode/commit/d80d55063470aa31f7fe14e856cb56e26656c5b8

For June, I have enabled toggleComment in new emmet. It is much more stable. This current issue of multi cursor still exists though.


Split sections into separate files

I think that the list will quickly get out of hand. Howe about splitting each section into a separate file and leaving only the table of contents in the main readme?

you are right, I already thought about it,
I will probably do that in the coming days ;)

@255kb - I can help split them up - the file is not too large at this point. Let me know.

@sangupta wow, I am sorry I just finished splitting the files 1mn ago...

@255kb No worries... it was my bad.

@sangupta still it is sad to see work being trashed, thanks for your understanding 👍

@255kb nah - till things are getting done... no one should mind.
BTW - do you need help in clearing up the conflicts with currently open PRs ?

@sangupta That would be great, I have not a lot of time these days, and christmas is coming, it will be even harder ><
Do you need any authorization?
Also, don't worry not everything has to be merged tonight ;) And I still want to be sure that everything is properly described

@255kb You can mark issues to me and I will raise a PR so that you can run a review.
Or if you wish to grant me write access - I can them tomorrow and then you run review on HEAD.

Actually, I imagined that the service names would stay in the main readme too as links. Good idea? Bad?

not a bad idea
I am using a VS Code plugin that automatically create table of contents, but not accross files, so I did not take time to do this!

created an issue #102

I see. Wouldn't have been that much work given that there already was a ToC assembled
True though, that managing it manually isn't perfect

yeah I will take it back from the previous version ;)


Update cccp to use terse cluster config

@brett19 it seems like this PR fixes #1

@brett19 it seems like this PR fixes #1


Isn't is bad that this project doesn't have start script configured?

Making a Template available for users should be easily configurable...
Sad that this is not the case with this template

Noob question here: Can we just make and configure our own?


ERA-9773: Header and section settings updates

Frontend for ERA-9773

@gaboDev can you close this if it's not needed?

@JoshuaVulcan @gaboDev this ticket was finished last sprint I think. It's status is Done. Also, we don't support these types of deployments for the EFB (again 😞 ). So I think we are good closing it.


Docs: document page.once()

https://github.com/GoogleChrome/puppeteer/issues/1228#issuecomment-340869335 has a nice snippet that uses page.once but I'm not seeing that in the api docs.

That's not puppeteer, that's node: once is a standard node.js method on event emitters, similar to on and removeListener: node.js events

Oh nice. Didn't even realize EventMitter had that. Do you think it's worth adding at least one example to the docs. I can imagine a lot of people wanting to catch a first event and ignore the rest.

@ebidel sure, we can use it somewhere in the docs where it makes sense. We can also specifically state that page/browser are node's event emitters.


Add py.typed to support type-hinting PEP-561

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs? NA
[ ] Did you write any new necessary tests? NA

What does this PR do?
This adds support for type-hinting information for the library, as laid in PEP-561.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

cc: @aniketmaurya


Add eXist-db.app 3.0 (nightly build)

After making all changes to the cask:

[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} reports no offenses.
[X] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[X] Named the cask according to the token reference.
Note: In using "nightly" suffix, I followed the nomenclature at https://github.com/caskroom/homebrew-versions/blob/master/README.md and followed the example of other nightly casks, e.g., https://github.com/caskroom/homebrew-versions/commit/d7ac7c4a1f6d6dd9938956b48309c0be5ebcffac.
[X] brew cask install {{cask_file}} worked successfully.
Note: In constructing the URL to the latest nightly, I followed the example of https://github.com/caskroom/homebrew-versions/blob/master/Casks/vlc-nightly.rb.
[X] brew cask uninstall {{cask_file}} worked successfully.
[X] Checked there are no open pull requests for the same cask.
[X] Checked that the cask was not already refused in closed issues.

Okay, I'll adapt the cask to remove Nokogiri. I will work with the creator of the nightly site to pre-sort the entries so the newest is consistently on top.

@joewiz In case you want to work with what you have, something like
latest_build_filename = open(builds_url) do |io|
  io.scan(/<tr>.*?<td>(.*?)<\/td>.*?<a href="([^\"]+)">dmg/m).max[1]
end

might do the trick.

@joewiz If you run the example code, you’re going to discover it already takes care of the sorting.
String#scan (in its non-block form) returns an array of date-URL pairs.
To pick the pair with the most recent date, the max call is already sufficient. You can remove the [1] temporarily to inspect the result.

@claui Now I see! Thanks so much for this great suggestion! Revised PR to come shortly.

Okay, the revised PR is in, and CI and my own tests are passing.

Like @vitorgalvao already pointed out (and anticipated back when we introduced the feature), I feel this particular use of url do is going to be really helpful for nightlies that don’t have a stable latest-version URL. I think this PR should be merged. Thanks @joewiz!

@claui @adidalal @vitorgalvao Great to hear that this PR proved to be a broader contribution. Thank you so much for all of your help!


vicky: Implement Timeouts

We want to be able to timeout jobs after a certain amount of time.
This may happen, if a worker misbehaves or crashes during execution.
If there is a timeout, the lock should also be poisoned.

Probably gonna implement this with some sort of heartbeat ping.


Deprecated FloatingPawn and CesiumGlobeAnchorParent

Closes #450
Reference for deprecation symbols: https://ikrima.dev/ue4guide/engine-programming/uobjects/deprecating-uproperties-ufunctions/
See notes at https://github.com/CesiumGS/cesium-unreal/issues/450#issuecomment-847352762

Thanks for the pull request @xuelongmu!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

This looks good to me. I confirmed that cesium-unreal-samples, which of course includes a FloatingPawn, pops up a message when it's loaded but otherwise still works correctly. The message says:
LoadErrors: Warning: FloatingPawn_C /Game/CesiumSamples/Maps/01/01_CesiumWorld.01_CesiumWorld:PersistentLevel.FloatingPawn_18: class /CesiumForUnreal/FloatingPawn.FloatingPawn_C has been deprecated.

I did some testing today and can confirm that the warning shows up, but floating pawn still works correctly. Additionally, if you try to compile the deprecated blueprint, it'll fail to compile, and afterwards if you try to play in-game there will be a BLUEPRINT COMPILE ERROR log message that shows up in the top left, but again this doesn't seem to affect the functionality. 👍


Tests 10122023

add config for GoBrew
rewrite tests to use httptest

Resolve #127

test time was improved :)

I will check tests with windows

On Windows we had a problem with tests.
The uploaded files were blocked by the main go process, which prevented the temporary directory from being cleaned up in a timely manner.  Because of this, certain special effects arose.
Why not waste time solving this problem while I disabled tests on Windows, as was the case before.

Interesting question. Is it necessary to rewrite the history of the comedians to make the story cleaner? And did the changelog contain only the necessary information?

In this MR I also changed the client to work with http.  I returned it back so as not to break the work via proxy.

In this MR I also changed the client to work with http. I returned it back so as not to break the work via proxy.

Got it, thanks! No worries.

Will push new tag at night

In this MR I also changed the client to work with http. I returned it back so as not to break the work via proxy.

Pushed to v1.10.5
Tested behind proxy too, works as intended.


How to centralized linux-dash

Hi
We are providing Linux application server to the customer, but we cannot install linux-dash and set to outside, rather than is it possible to install linux-dash on all the Linux server and collect data and to centralized since going to each server and view the information.
Since we cannot change apache config file.

See request #272


[android] support resize Image in FrescoImageAdapter

the default ImageAdapter Supported By Picasso, so a ImgUri with Base64 is not supported ,
the FrescoImageAdapter support it , but resize Image is not useful in FrescoImageAdapter , so i support it

hi  @xiaoqi951109   thanks for your contribution   and @misakuo can you review this pull request

Since this PR don't get any response for a month, I will just close it. Feel free to reopen


I have updated the content of line #394

I have updated the heading for About OmLabs section, Old character count was 31 and updated character count is 31.

Approved


Bugfix/frontend

@cesar-tonnoir I just added valid and cancel buttons to editable title in this PR, please review.


I would be nice if the user receives feedback when a div/0 (or other error in calculation) occurs

See for instance https://github.com/quintel/etmoses/issues/1599

Agree
I see two outcomes of an input error.

The LES is calculated, but has errors in the outcome (like #1599)
The LES doesn't calculate at all (for example because the CSV contains a node that is not defined in the topology)

Feedback on both would be nice


ReactTable output broken css

import React,{ Component } from 'react'
// import {Button, Icon, Modal, Col, Preloader, Row} from 'react-materialize'
import ReactTable from "react-table";
import "react-table/react-table.css";
// import InvoiceForm from '../components/InvoiceForm'
class RemittanceValidation extends Component{
  constructor(props){
    super(props);
    this.state={
      remittances: []
    }
  }
  // componentDidMount() {
  //   // let invoiceId = document.getElementById('show').getAttribute('data-id');
  //   fetch(`api/v1/validations`, {credentials: "same-origin"})
  //   .then(response => response.json())
  //   .then(body => {
  //     this.setState({remittances: body})
  //   });
  // }
  render(){
    const data = [{
        name: 'Tanner Linsley',
        age: 26,
        friend: {
          name: 'Jason Maurer',
          age: 23,
        }
      }]
      const columns = [{
        Header: 'Name',
        accessor: 'name' // String-based value accessors!
      }, {
        Header: 'Age',
        accessor: 'age',
        Cell: props => {props.value} // Custom cell components!
      }, {
        id: 'friendName', // Required because our accessor is not a string
        Header: 'Friend Name',
        accessor: d => d.friend.name // Custom value accessors!
      }, {
        Header: props => Friend Age, // Custom header components!
        accessor: 'friend.age'
      }]
    return(

      <ReactTable
        data={data}
        columns={columns}
      />

    )
  }
}
export default RemittanceValidation

My code and below is the output

Happens to me too

+1

put the import css on the assets/stylesheets/application.css or scss file to fix it.

That works. In my global css I did
@import url('~react-table/react-table.css');
Then imported the global css to the React component.
However, why this doing this from the React component doesn't work?
import 'react-table/react-table.css'

Maybe because your build environment doesn't support that syntax yet (it is currently not standard and relies on your transpiler to detect the syntax and to understand what to do with CSS files).


Added directory, package-ecosystem and target_branch to output

closes issue #76

This is a sensible request. Since the branch name already reflects the directory, I don't think we have any security concerns with exposing this info in our outputs either.
Nice work 👍🏾
CI Is already passing so I'll just look over the tests and work to get this merged.

After merging this I realized that target-branch is actually hyphenated in our docs https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#target-branch
I'll follow this PR up with another to rename target_branch to target-branch

Whoops! - see #140


Separated footer design into two sections

NOTE: This PR is not ready to merged yet because I haven't found a way to rebuild the stylesheet.

@gbozee you can merge this now.
I also liked the approach you took with the generated CSS file. :+1:


Fix some issues with reading binary from parquet

This fixes some failures when reading binary columns from parquet in 3.3.0. It also allows for setting the read schema for a binary column to be a string.

build