Improve Selection shifter/offsetter

There is a whole interface on the Ribbon for shifting the Selection a given number of rows/columns.  This would probably be much better off with a quick keyboard shortcut that shifts the Selection.  The interface as it sits is not that useful.  I have actually never used it.

Decent shortcuts would be CTRL+ALT+{ARROW} to move the Selection around.  This has the downside of being the same shortcut used to flip the monitor around.  Not sure if that takes precendence; I disable the monitor flipping stuff.  Another option would be CTRL+ALT+SHIFT+{ARROW} which is not commonly used (I don't think) but involves a lot of keys at once.
Relevant code:
Sub SetHotKeys()
    'this would go into an onload for the Ribbon.

    Application.OnKey "^%{RIGHT}", "OffsetRight"

End Sub

Sub OffsetRight()

    Selection.Offset(, 1).Select

End Sub

For me, it shifts the selection, but not the contents of the cells that were selected. Is that how it was intended?

Yea.  It is supposed to just shift the selection.  It was supposed to help in a case where you some funky selection and just wanted to go over one column to delete the cells next door (or something similar).
Although moving the range might be a more useful thing.  Maybe CTRL+ALT moves selection and CTRL+ALT+SHIFT moves the actual contents.  It gets into the same discussion about how to update formulas when doing that, but it might be useful in a number of cases that are not problematic.  Any thoughts on that?

Like I said, I have never actually used this one because it is not that convenient.  Maybe it is not a useful feature regardless of how accessible it is.  For some reason I like the idea of moving the Selection though.  It just seems like something that should be possible.
I am looking at the Ribbon now and thinking of how to organize things better to make room for all the features that don't have space in the Ribbon yet.

Well, currently it's impossible to move a selection to anywhere else without making a new selection - so the feature does have some merit in creating functionality.

Alright, I'll wire this one up for the CTRL+ALT shortcuts for now to move the Selection.  I'll test that with the monitor shortcuts to make sure this doesn't create a headache for people.
If that works nicely, we can take a look at adding in the ability to move ranges around with the keyboard as well.

Got this bit added in.  Cleans up the Ribbon nicely to remove that chunk of boxes.
I confirmed at work that this will not play nice with the Intel monitor shortcuts CTRL+ALT+{ARROW}.  I personally disable those because I never need to rotate the monitor around.  If this is a conflict, let me know.

Those are easy enough to disable, but it's too bad that can't be built in when installing the add-in (or give an option to the user on what they want to do).

The add-in could probably hook into some Win32 API and override or maybe disable the monitor shortcuts.  Not sure how easy it is to revert those though when the add-in is closed.  I also start to get a little nervous when the add-in is using those APIs and going into unexpected places.  The user might wonder what the add-in is doing with those API calls.

I'll call this implemented for now.  If the keyboard shortcut becomes an issue, we can open a new issue to address it.  I actually used this the other day to move a selection over.


unhandled SyntaxKind: Unknown for valid OpenAPI 3.0.0 schema

Description
When using the CLI with no other options, I get unhandled SyntaxKind: Unknown
The latest version of the openapi-typescript-codegen package, however, works fine.
OpenAPI specification (optional)
No response
Configuration
npx @hey-api/openapi-ts -i ./api.yaml -o src/client
Tried both yaml and json.
System information (optional)
Ubuntu 20.04.

@lovetoast we are going to need the part of the openapi spec that is failing. Try running with --debug and it may provide more info. Without the spec we cant help much.

@lovetoast can you provide the spec?

Hello everyone, I am catching the same error when I try to use the config file with this swagger http://<IP_ADDRESS>/api-doc-json

openapi-ts-error-1713416926965.log

@debabin thanks, that should help me debug it

@debabin thanks, that should help me debug it

Thx, i am literally migrated today from openapi-typescript-codegen, and when i use openapi-typescript-codegen it is works fine

@debabin Ya, we migrated alot of the existing code to use the Typescript compiler API (performance and size improvements on the package). I am looking into why this is happening now and will reference any PR in this ticket

Tracked down to something with the UpdateTariffDto schema in the above URL

Tracked down to something with the UpdateTariffDto schema in the above URL

hm, what is kind of problem ?

@debabin Just noting info here. The problem is on our end. Just as a minimal reproduction we can use only that schema.

@debabin Just noting info here. The problem is on our end. Just as a minimal reproduction we can use only that schema.

Sounds great, thanks for such a quick answer. i will wait your response 🔥

There is also a small bug: when the exportCore flag is true, an empty core folder is still created

@debabin  @lovetoast I was able to fix the issue in the linked PR. I have tested generating using the full spec provided by @debabin  and have had no issues. Thanks for reporting this and I will work to get a version released once my PR is approved and merged.

There is also a small bug: when the exportCore flag is true, an empty core folder is still created

I assume you meant false. We're aware of that, but out of curiosity, why do you not use core? How do you use the generated code?

There is also a small bug: when the exportCore flag is true, an empty core folder is still created

I assume you meant false. We're aware of that, but out of curiosity, why do you not use core? How do you use the generated code?

I have custom architure in my code. You can look example of my code here. And i need only types.

The code you are using is creating some problems for me. I use axios and want to support everything that axios gives me. For example, I want to use the full Axios configuration for its requests.
const body = {} as UpdateProfileDto;
patchUsersSession({
  params: body,
  config: {
    headers: {
      version: '123'
    }
  }
});

UsersService.usersControllerUpdateProfile({ requestBody: body });

But I don’t want to fill out the types myself every time; I want to automate this process. I checked, but it seems with client fetch, I also won't get the opportunity to make maximum use of fetch

Perfect, thanks for the context! Sounds related to #342

And will be so cool generate only functions without class, like some additional opportunity for config. Thx for answers

@debabin https://github.com/hey-api/openapi-ts/issues/413#issuecomment-2063638050 🚀


Responsive nav

Made the nav responsive

issue https://github.com/Vaibhav13kamat/My_portfolio/issues/51


analytics: Pass the right value for realm.

Fixes:

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "integration review"

Looks great, merged, thanks @alexmv and @laurynmm!


could you help to fix this? thanks!

[+] : Logged in successfully.
[*] : Downloading course information .. -Traceback (most recent call last):
File "udemy-dl.py", line 1442, in
main()
File "udemy-dl.py", line 1281, in main
udemy.course_download(path=options.output, quality=options.quality, unsafe=options.unsafe)
File "udemy-dl.py", line 436, in course_download
course = udemy.course(url=self.url, username=self.username, password=self.password, cookies=self.cookies)
File "/home/esir/udemydl/udemy/_udemy.py", line 38, in course
return Udemy(url, username, password, cookies, basic, callback)
File "/home/esir/udemydl/udemy/_internal.py", line 44, in init
super(InternUdemyCourse, self).init(*args, **kwargs)
File "/home/esir/udemydl/udemy/_shared.py", line 62, in init
self._fetch_course()
File "/home/esir/udemydl/udemy/_internal.py", line 56, in _fetch_course
self._info              =       self._real_extract(self._url)
File "/home/esir/udemydl/udemy/_extract.py", line 467, in _real_extract
'subtitles' : self._extract_subtitles(tracks),
File "/home/esir/udemydl/udemy/_extract.py", line 256, in extract_subtitles
lang = track.get('language') or track.get('srclang') or track.get('label') or track['locale'].get('locale').split('')[0]
KeyError: 'locale'

Your udemy-dl is old
Use command git pull to download lastest version of udemy-dl

Your udemy-dl is old
Use command git pull to download lastest version of udemy-dl

I downloaded the version 0.5, so I got the output above, and after clone the code, I got this:
[] : Username : myemail.com
[] : Password : *********
[*] : Trying to login as (myemail.com)...
[-] : Udemy Says : 400 Bad Request Oops, something went wrong. ...

login with username and password is not avalible at this moment. You can cookie to login. Follow the guide here : https://github.com/r0oth3x49/udemy-dl/issues/351#issuecomment-476936783

login with username and password is not avalible at this moment. You can use cookie to login. Follow the guide here : #351 (comment)

thank you very much! It works! and the speed so fast... cause I ran it on google cloud.
But I now am worrying they might ban me  for doing this...

@brundidge thanks for the quick support


OpenGL shader compilation error on Mesa (Linux Intel/AMD)

Describe the Bug
Regression  in recent commit 5cfe04cff770174c686f1f75b5c8cfae7d1d5eaf for shader crash that was fixed in upstream Create.
[21:01:53] [Render thread/INFO] (com.mojang.blaze3d.platform.GlDebug) OpenGL debug message: id=3, source= SHADER COMPILER, type=ERROR, severity=HIGH, message='0:69(1): error: #extension directive is not allowed in the middle of a shader'
[21:01:53] [Render thread/ERROR] (com.jozufozu.flywheel.backend.Backend) Shader compilation log for create:rotating: 0:69(1): error: #extension directive is not allowed in the middle of a shader

Only fails on Intel/AMD graphics on Linux.
Upstream commit of fix:
https://github.com/Creators-of-Create/Create/commit/67bcbc874bc48b5f8f332335628cf2f2b1abd932
Regression in this commit:
https://github.com/Create-Fabric/Create-Refabricated/commit/5cfe04cff770174c686f1f75b5c8cfae7d1d5eaf#:~:text=if defined(GL_ARB_conservative_depth)-,%23,-extension GL_ARB_conservative_depth %3A enable
Reproduction Steps

Checkout 5cfe04cff770174c686f1f75b5c8cfae7d1d5eaf or later on Linux running Intel/AMD graphics.
./gradlew clean runClient --no-daemon
See shader compilation error in log
delete #extension GL_ARB_conservative_depth : enable in src/main/resources/assets/create/flywheel/shaders/context/contraption.glsl (it's already included in #use "flywheel:context/fog.glsl" I think)
recompile, runs in-game as expected.

Expected Result
...
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Void Linux (mesa-21.2.6_1)
Mod Version
0.4.0a
Minecraft Version
1.18.1
Other Mods
No response
Additional Context
No response

speedrun


add logseq-tocgen

Submit a new Plugin to Marketplace
Plugin Github repo URL:
Github releases checklist

[x] a valid CI workflow action for Github releases. (Optional for theme plugin only)
[x] a legal package.json file.
[x] a clear README file.
[x] a license in the LICENSE file.

@xyhp915,  what's preventing you from merging this? Do you need any help?

@xyhp915, what's preventing you from merging this? Do you need any help?

Lol, just haven't spared time to take a closer look at the code :) From an initial glance, I found that it uses parent.document for its working principle and MutationObserver to monitor the host document globally. I am worried about whether there will be performance problems when editing with a large number of blocks. We can test it.  Also, it would be robust to disconnect observer when the plugin is uninstalled to avoid memory leaks.

I see, let me try to clarify about the two things you worry about.

mutation observer performance. It serves as a notification mechanism to let me know when related blocks have changes. There is no other way in the current plugin infrastructure that provides this information. I can substitute it once you improve the plugin infrastructure. For now, for what I have tested with my local files, there are no signs of performance issues.
Currently, the observer disconnects upon disabled, but not upon uninstall. I have fixed this and submitted a new version.


BitFieldArgs should allow '#' prefixed offset values.

Currently only zero based offsets can be set. However using # as a prefix multiplies the given offset by the integer type width, which comes very handy.
see: http://redis.io/commands/bitfield#bits-and-positional-offsets

That's implemented now.


Often (but not always) 'double vision' of close by objects

I have not been able to put a definite repo for this, but using Unity 2017.2.0.f3 MRTP I often get 'double vision' of objects that are close by. It feels like anything closer than about 1.5 meters. Cursor seems displayed twice close to each other, I also see two instances of the same controllers through each other when I use only one. It looks like the stereoscopic view does not work properly. When I download my app from the store, everything is fine.
Sometimes restarting the Mixed Reality portal helps, sometimes not even a reboot helps. I thought it had something to do with tracking, but apparently not

I've seen this as well. Didn't know a reboot or relaunch of the portal helps. Thanks!

It SOMETIMES helps. Pretty sure it is a race condition. /ref Slack
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Stephen Hodgson<EMAIL_ADDRESS>Sent: Oct 25, 2017 21:16
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
I've seen this as well. Didn't know a reboot or relaunch of the portal helps. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-339440428, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Bn_5HBmm2Mi3lwoqap7C6s6JLdLG2ks5sv4kIgaJpZM4QGf4L.

This seems to fix the double vision. Changed MotionControllerVisualizer
private IEnumerator Start()
    {

        yield return new WaitForSeconds(5);

Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Joost van Schaik
Sent: Oct 25, 2017 21:41
To: Microsoft/MixedRealityToolkit-Unity
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
It SOMETIMES helps. Pretty sure it is a race condition. /ref Slack
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Stephen Hodgson<EMAIL_ADDRESS>Sent: Oct 25, 2017 21:16
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
I've seen this as well. Didn't know a reboot or relaunch of the portal helps. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-339440428, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Bn_5HBmm2Mi3lwoqap7C6s6JLdLG2ks5sv4kIgaJpZM4QGf4L.

This seems like a Unity bug to me. Have you filed anything?

No... Because it makes the chance of this happening less, but not zero. A bit worried about the Unity QA TBH
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Kurtis<EMAIL_ADDRESS>Sent: Oct 30, 2017 20:26
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
This seems like a Unity bug to me. Have you filed anything?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-340536569, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Bnw13rzs90z7_BRoUUpQ9aqYP7er-ks5sxhKdgaJpZM4QGf4L.

Because it makes the chance of this happening less

What is "this"?

Sorry. Delaying MotionControllerVisualizer init
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Kurtis<EMAIL_ADDRESS>Sent: Oct 30, 2017 21:10
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
Because it makes the chance of this happening less
What is "this"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-340568957, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8BnyMeMmeUDF4aHJdZmhnP8_8Qw-Eiks5sxi01gaJpZM4QGf4L.

That makes the chance of double vision less. At least I think so
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Joost van Schaik
Sent: Oct 30, 2017 21:32
To: Microsoft/MixedRealityToolkit-Unity; Microsoft/MixedRealityToolkit-Unity
Cc: Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
Sorry. Delaying MotionControllerVisualizer init
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Kurtis<EMAIL_ADDRESS>Sent: Oct 30, 2017 21:10
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
Because it makes the chance of this happening less
What is "this"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-340568957, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8BnyMeMmeUDF4aHJdZmhnP8_8Qw-Eiks5sxi01gaJpZM4QGf4L.

FYI for folks, we are investigating this with Unity.

Also, I'd recommend against doing unnatural things to work around this, as those workarounds can creep into final apps. :) We will share info as soon as we have it.

I know but things sometimes just gotta work, right? 😀
Joost van Schaik
Windows Development MVP
Sent from mail for Windows 10
"The world as I envision it in my head is such a more interesting place"

From: Chris White<EMAIL_ADDRESS>Sent: Monday, October 30, 2017 9:39:59 PM
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
Also, I'd recommend against doing unnatural things to work around this, as those workarounds can creep into final apps. :) We will share info as soon as we have it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-340577159, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Bn9t6E35YkXKfsvINZCi13F4G3uEgks5sxjQegaJpZM4QGf4L.

I'd like to add that the amount also seems to change. Sometimes it's negletable and feels correct, though a little fishy, sometimes it hurts the brain. And there's also in between situations.
This never happened to our project until using MRTP3, but what do you know, maybe we were just lucky.

I had it with MRTP, haven't tried MRTP3
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Alexees<EMAIL_ADDRESS>Sent: Nov 1, 2017 16:32
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
I'd like to add that the amount also seems to change. Sometimes it's negletable and feels correct, though a little fishy, sometimes it hurts the brain. And there's also in between situations.
This never happened to our project until using MRTP3, but what do you know, maybe we were just lucky.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-341141902, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Bnxv50VrjLN_Y364aLqgncoXbAH_pks5syI8LgaJpZM4QGf4L.

When I download my app from the store, everything is fine
You were lucky then. In my case, the double vision krept into the store built

Actually, I'm starting to suspect this is also a bug in the MRTK.  The reason I think this is because the controller models don't have a collider and we're not moving the focus plane to them when our gaze hits it.

This is decidedly not a MRTK bug. I've verified it fixed in an upcoming 2017 MRTK build that should be released more broadly once it gets through Unity's testing process.

@timGerken  The patch release is out #1301

@StephenHodgson Yes, but the bug fix is in a separate (currently private) MRTP4 build off of that patch release.

Yikes. I have posted a version with MRTP3. Can I please have that private beta? Or else and ETA? 😀
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Tim Gerken<EMAIL_ADDRESS>Sent: Nov 6, 2017 20:27
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Author
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
@StephenHodgsonhttps://github.com/stephenhodgson Yes, but the bug fix is in a separate (currently private) MRTP4 build off of that patch release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-342258312, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8BnwRF8V1X-JBg_kAINhyahhHjAnQhks5sz12igaJpZM4QGf4L.

@LocalJoost
If you had access to MRTP3, you should also gain access to MRTP4 when available.
At this point, I can't provide an ETA.

MRTP4 is now available

Already have a PR #1312 for it!  Thanks @timGerken

Awesome
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Tim Gerken<EMAIL_ADDRESS>Sent: Nov 7, 2017 18:08
To: Microsoft/MixedRealityToolkit-Unity
Cc: Joost van Schaik; Mention
Subject: Re: [Microsoft/MixedRealityToolkit-Unity] Often (but not always) 'double vision' of close by objects (#1236)
MRTP4 is now availablehttps://forum.unity.com/threads/custom-build-2017-2-rc-mrtp-windows-mixed-reality-technical-preview.498253/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit-Unity/issues/1236#issuecomment-342552436, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8BnxIKfhgUXdSWOyec0rqtOGD-6bgxks5s0I6PgaJpZM4QGf4L.

Oh yeah, can't wait too see again.


What happens if the worker dies while processing?

If I run the test from the readme, and kill the node process between when it accepts the job and when it resolves it, it just sits in the tasks queue forever.
Is this acceptable behavior for a messaging system?  I would expect a robust system to detect that the old job has expired and move it to an error state or something.

Ah, I misread the timeout... I thought it was 30s, but it is actually 5 minutes. It does clean up successfully in this case. Good work guys!

Glad you got it working, this isn't the first time this has caused issues - I'll take a look at making it more clear in the readme


Error message

Fixed the error message so that it only displays once instead of the multiple appending that had occured

yay


fatal error: dlib-master/dlib/dnn.h: No such file or directory

My requirment is i need to train renset.dat with custom images
Expected Behavior
The file dnn_metric_learning_on_images_ex.cpp should be compiled sucessfully
Current Behavior
dnn_metric_learning_on_images_ex.cpp:29:34: fatal error: dlib/dnn.h: No such file or directory
compilation terminated.
Steps to Reproduce
With the below command i tried to compile the code
g++ dnn_metric_learning_on_images_ex.cpp -o dlibtest

Version:  19.9.99
Where did you get dlib: this github repo
Platform: 64 bit
Compiler:  5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)

Follow the instructions here: http://dlib.net/compile.html


[nomerge] Ocfs merge stray shares uid fixes

just for CI, it's https://github.com/cs3org/reva/pull/1052 and https://github.com/cs3org/reva/pull/1064

transcript from CI:

--- Failed scenarios:
--

--- Failed scenarios:

/drone/src/tmp/testrunner/tests/acceptance/features/apiShareManagementBasic/createShare.feature:380
/drone/src/tmp/testrunner/tests/acceptance/features/apiShareManagementBasic/createShare.feature:381
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:74
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:117
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:139
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:162
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:209
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:232
/drone/src/tmp/testrunner/tests/acceptance/features/apiSharePublicLink1/changingPublicLinkShare.feature:255
/drone/src/tmp/testrunner/tests/acceptance/features/apiVersions/fileVersions.feature:406
/drone/src/tmp/testrunner/tests/acceptance/features/apiVersions/fileVersions.feature:407
/drone/src/tmp/testrunner/tests/acceptance/features/apiVersions/fileVersions.feature:459
/drone/src/tmp/testrunner/tests/acceptance/features/apiVersions/fileVersions.feature:460
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:98
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:99
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:122
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:123
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:124
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:125
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:126
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:127
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:128
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:129
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:130
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolder.feature:131
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature:34
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove1/moveFolderToBlacklistedName.feature:35
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:21
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:22
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:34
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:35
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:45
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:46
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:57
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:58
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:68
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:69
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:231
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:232
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:243
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:244
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:296
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:297
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:305
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:306
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:326
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:337
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:338
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:339
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:340
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:341
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:342
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:343
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:344
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:345
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:346
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:347
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFile.feature:348
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature:30
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavMove2/moveFileToBlacklistedName.feature:31
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature:57
/drone/src/tmp/testrunner/tests/acceptance/features/apiWebdavProperties1/setFileProperties.feature:58

475 scenarios (413 passed, 62 failed)
3705 steps (3530 passed, 62 failed, 113 skipped)
7m1.59s (20.32Mb)

I have tests/acceptance/features/apiShareManagementBasic/createShare.feature:380 passing locally the first then, then failing with a "405" error, probably due to stray shares.
% TEST_SERVER_URL='http://localhost:20080' \
OCIS_REVA_DATA_ROOT='/drone/srv/tmp/reva' \
SKELETON_DIR="$HOME/work/workspace/owncloud/apps-external/testing/data/apiSkeleton" \
TEST_EXTERNAL_USER_BACKENDS='true' \
REVA_LDAP_HOSTNAME='ldap' \
TEST_OCIS='true' \
TEST_REVA='true' \
BEHAT_FEATURE=tests/acceptance/features/apiShareManagementBasic/createShare.feature:380 \
BEHAT_FILTER_TAGS='~@skipOnOcis&&~@skipOnOcis-OC-Storage' \
make test-acceptance-api

result:
        HTTP status code 405 is not one of the expected values
        Failed asserting that an array contains 405.

never mind, it was a local setup issue...
when I run createShare:380 alone with a clean env, the test passes, unlike on CI.
if I run the whole of createShare feature file, then:
    /srv/www/htdocs/owncloud/tests/acceptance/features/apiShareManagementBasic/createShare.feature:380
    /srv/www/htdocs/owncloud/tests/acceptance/features/apiShareManagementBasic/createShare.feature:381

I've pushed the move fix, and now only two tests are failing:
tests/acceptance/features/apiShareManagementBasic/createShare.feature:380
tests/acceptance/features/apiShareManagementBasic/createShare.feature:381

sadly these pass for me when running the whole of createShare

detail:
  @skipOnOcV10 @issue-ocis-reva-372 @issue-ocis-reva-243
  Scenario Outline: sharing subfolder of already shared folder, GET result is correct                                      # /drone/src/tmp/testrunner/tests/acceptance/features/apiShareManagementBasic/createShare.feature:352
    Given using OCS API version "<ocs_api_version>"                                                                        # FeatureContext::usingOcsApiVersion()
    And these users have been created with default attributes and without skeleton files:                                  # FeatureContext::theseUsersHaveBeenCreatedWithDefaultAttributesAndWithoutSkeletonFiles()
      | username |
      | Brian    |
      | Carol    |
      | David    |
      | Emily    |
    And user "Alice" has created folder "/folder1"                                                                         # FeatureContext::userHasCreatedFolder()
    And user "Alice" has shared folder "/folder1" with user "Brian"                                                        # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Alice" has shared folder "/folder1" with user "Carol"                                                        # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Alice" has created folder "/folder1/folder2"                                                                 # FeatureContext::userHasCreatedFolder()
    And user "Alice" has shared folder "/folder1/folder2" with user "David"                                                # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Alice" has shared folder "/folder1/folder2" with user "Emily"                                                # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    When user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares"                      # OCSContext::userSendsToOcsApiEndpoint()
    Then the OCS status code should be "<ocs_status_code>"                                                                 # OCSContext::theOCSStatusCodeShouldBe()
    And the HTTP status code should be "<http_status_code>"                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares?path=/folder1/folder2" # OCSContext::userSendsToOcsApiEndpoint()
    And the response should contain 2 entries                                                                              # FeatureContext::checkingTheResponseEntriesCount()
    And folder "/folder1" should not be included as path in the response                                                   # FeatureContext::checkSharedFileAsPathNotInResponse()
    And folder "/folder2" should be included as path in the response                                                       # FeatureContext::checkSharedFileAsPathInResponse()

    Examples:
      | ocs_api_version | http_status_code | ocs_status_code |
      | 1               | 200              | 996             |
        OCS status code is not the expected value 996 got 100
        Failed asserting that two strings are equal.
        --- Expected
        +++ Actual
        @@ @@
        -'996'
        +'100'
      | 2               | 500              | 996             |
        OCS status code is not the expected value 996 got 200
        Failed asserting that two strings are equal.
        --- Expected
        +++ Actual
        @@ @@
        -'996'
        +'200'

linked issues: https://github.com/owncloud/ocis-reva/issues/372 and https://github.com/owncloud/ocis-reva/issues/243
but doesn't explain why these tests pass locally but not on CI

so the tests currently expect the list shares request to fail, but we actually implemented that endpoint and it should work. Or in the words of our testsuite: https://github.com/owncloud/core/pull/37754/files#diff-129a7916711570e3ddb2eb9f655ce577
The question remains: why is the test failing locally (which means the list shares endpoint actually returns an error).
it might have to do with tha share manager not being started? or restarted? or reset properly?

I've now tried running my local createShare.feature with core's 9ebf886779b98fc3f78e11cf138246f80d5cab39 which is the commit on which Drone is running.
When I had the branch testFixOCISPR409 checked out the test passed.

one of the PRs got merged.
closing in favor of https://github.com/cs3org/reva/pull/1064 where we'll test with testFixOCISPR409


Wiki nodejs版本需要更新

需要从目前的v10+变成v12+: https://github.com/ronggang/PT-Plugin-Plus/wiki/developer
测试v14可以正常运行。
$ yarn install
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>Invalid bin field for "url-loader".
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=12". Got "10.19.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

duplicated #707


Enhance executeMethod by passing SOAP headers as an argument

For Node SOAP server, it is required for some services to get the SOAP headers from the request.
The server.js pass the headers as the 3rd argument of the method (after args and callback).

The commit f2503abffc28e8f5f1a820e3f86166085a1e5a18 includes the change that I proposed.
I close the P/R.

thanks for keeping track of the changes :+1:


open project from dashboard in separate tabs

Having several draft project listed in the dashboard one might like to open several of them as new tabs, to easily compare something between these drafts.
Currently, the target is "self", which is possibly the default and should be the default. However, there is no possibility to open them as new tabs by holding down STRG on Windows machines (or command on Apple machines) and selecting a project.
Current workaround is to open a new tab for each project, open the dashboard in each tab, and select one project from each tab.


User Required to have ListKeys/Action permission

A user who is provisioned with Azure Active Directory, but does not have access to Microsoft.Storage/storageAccounts/listKeys/action fails to execute

Tied directly to this article:  https://github.com/Azure/azure-powershell/issues/19965
The creation of $storageAccount.Context is a lazy property that requires the listKeys action to populate.
workaround is to create the .Context object manually with a call to New-AzStorageContext.


Version v0.15

There are a problem in this version that does not link react-native-maps to android, and if a do manual, i cant add as:
project(':react-native-openpay').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-openpay/android')
And if i remove the android folder on the path, this error appears:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
Configuration with name 'default' not found.

In v13 works. I hope you can help me :).

Thats because you the address of the lib has changed.
It's
include ':react-native-maps'
project(':react-native-maps').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-maps/lib/android')

Make sure that in your settings.grandle you set the above.
Hopefully it solves your issue, if it does, hit that thumbs up button 👍  :)


fix: check for supportedExtensions after filtering ignored files

If there are any staged files in directory containing a package.json (it doesn't need to be changed/staged), even if the directory is meant to be ignored, the function isSupportedExtension() is run. This can fail if the package.json file has invalid JSON for example (resolveConfig from prettier actually fails). Moving the filters around so that the ignored files are properly accounted for gets rid of the error.
I'm not sure if the unstaged files need to be filtered the same way: https://github.com/azz/pretty-quick/blob/f11faa91d5c570407c37ed77ac04ec0f5e0ef64e/src/index.js#L52-L59
Example repository to test this: https://github.com/ullasholla/pretty-quick-ignore-test
The templates directory contain ejs templates and the .json files are not yet valid JSON files.
To test, make a change to templates/core/config.json and stage it.
Tests are passing locally:

Could you please review and consider merging this?
Thanks!

Could I get a review for this please? @azz, maybe?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New Tab experience always displaying number of dislikes as 0

Been noticing this issue in the New Tab experience for the extension and the browser where the the number of dislikes will be displayed as 0 even if the number of dislikes is NOT 0.
Example: https://pic8.co/sh/Sq7et6.PNG and https://pic8.co/sh/xHEFaO.PNG

@seanking2919 thanks for submitting this issue. I will look into it.


Cow: Watch getgbwa.in

Cow requests the watch of the watch_keyword getgbwa\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

getgbwa\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Error while importing maven API

I used maven to upload the api, I made the basic plugin I needed and when I wanted to build it, I got "cannot access fr.minuskube.netherboard.api.PlayerBoard"

Add this to your depedency:
        <dependency>
            <groupId>fr.minuskube</groupId>
            <artifactId>netherboard-core</artifactId>
            <version>1.2.3</version>
            <scope>compile</scope>
        </dependency>


Does not live reload on different folder

# Atom-live-server is not automatically reloading on save when on a different folder.

Same Here! http://<IP_ADDRESS>:3000/ is not the folder I'm working on...

@Kristoffer95 could you describe what your folder structure looks like?


Enable Submit Proposal feature to gov pre-compile

Search before asking

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

Motivation
At the moment, only Vote & Deposit actions are available on gov precompile of sei-chain.
Do you have plans to support SubmitProposal action on gov precompile?
Solution
No response
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Hi @domficaker thanks for the recommendation! We will add this to our backlog, but if you want to take a stab at it we're happy to review PRs as well


Appstudio update test-component-pac-acai

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-acai-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
1 minute
appstudio-init

✅ Succeeded
36 seconds
clone-repository

✅ Succeeded
31 seconds
appstudio-configure-build

✅ Succeeded
1 minute
build-container

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-acai-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
12 seconds
clone-repository

✅ Succeeded
6 seconds
appstudio-configure-build

✅ Succeeded
25 seconds
build-container

✅ Succeeded
6 seconds
show-summary


Image Page 'Additional Info' needs correct

The following is what I found about 'Additional Info' element in EML xsd, it might be the wrong element, please verify it.
<xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
xs:annotation
xs:appinfo
doc:tooltipAdditional Information</doc:tooltip>
doc:summaryAny extra information pertitent to the
resource.</doc:summary>
doc:descriptionThis field provides any information that is not
characterized by the other resource metadata
fields.</doc:description>
doc:exampleCopyright 2001, Robert Warner</doc:example>
</xs:appinfo>
</xs:annotation>
</xs:element>
But it generates an error in both cases:
when Additional info is empty, the error message is as follows:
EML - ../Whelk/%23%23%23_UN_001x.xml:119:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'additionalInfo': This element is not expected.
when it is filled out, the error message is as follows:
EML - ../../Downloads/Busycotypus%20canaliculatus%20reproductive%20data,%20Vineyard%20Sound,%202020/97_UN_003c.ome.xml:152:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'additionalInfo': This element is not expected.

This was most likely caused by the additional info node not being placed in the correct order relative to other nodes, so hopefully changing the order to match the EML documentation fixed this.


Add absolute path for service-worker.js

Prevents the following error by setting an absolute path to the service-worker
DOMException: Failed to register a ServiceWorker: The script has an unsupported MIME type ('text/html').

Not sure if the polyfill is necessary:
if (!window.location.origin) {
  window.location.origin = window.location.protocol + "//" + window.location.hostname + (window.location.port ? ':' + window.location.port: '');
}

Why is this necessary? Is your service-worker.js not in your web root?

My service-worker.js is in my web root folder, however it fails to register when I hit nested routes (e.g. https://example.com/user/:id)
Similar issue: https://github.com/jeffposnick/create-react-pwa/issues/11

It's up to generator or path structure of the app. For example,

relative path: We can imagine that some kind of apps can use subpath as a their root independently.
create-react-app: use their public path not root
vue pwa: now It uses dist but ./static/ can be possible

It's not immutable value, so I would recommend that you can update the path at build/service-worker-prod.js to fit your project env

The first scenario's a fair point, we should let the user edit this setting by himself then ✌


RDS Tab displays an error.

RDS Tab displays an error.
http://www.ec2instances.info/rds/

NoSuchKey
The specified key does not exist.
rds/
25248F35480262AE

zFDrga626d7Gmr/NSCdMCFnqETkYlimWLertblDLZhUQb30Wy3omlXFXrBmHcc2K35TSKormy1c=

Looks like an issue caused by #292. Fixing now.

Fixed!
Problem was with the CloudFront config pointing at the S3 bucket instead of its web endpoint. This was the solution: https://stackoverflow.com/a/33087418/121515


some questions about border treatment

First of all, I highly appreciate this great work, which implements lots of methods to perform poisson image editing with different backends, where I really value the promising implementations of CUDA and Taichi which enable me to use poisson image editing during my deep network training although it isn't differentiate. Although it seems perfect right now, I may have a small issue about the special treatment of image boundary, because it's likely that the blending result is less satisfactory if the mask touches the image border.
https://github.com/Trinkle23897/Fast-Poisson-Image-Editing/blob/d605cf90542ddac7cd47ae830f713510f1a5d935/fpie/process.py#L183-L187
Since my mask will touch the image border, so the codes above will forcely set the mask value to 0 (instead of keeping the original 255). I think this is because the current implementation don't give a special treatment to this case, and therefore if the target image have wrong values inside the masked region (e.g. all zeros inside the mask) and we use gradient="src", the filled values will definitely affect the blending results because the filled values are also involved in the boundary constraints (some mask values are set to zero, see above).
I wonder to know, if I want to address this, what should I do and modify the codes so as to keep the changes minimum?
Thank you very much!

Could you please give me a command to reproduce what you said above?
fpie -s test7_src.jpg -t test7_tgt.jpg -o result7.jpg -h1 50 -w1 30 -n 5000 -g src

This command will have mask == 255 with mask.shape == src.shape, but I don't see any issue with the resulted image.

Sure, you can try this example:
fpie -s src.png -t tar_masked.png -m mask.png -o out.png -g src

where the images can be downloaded from mask.png, tar_masked.png and src.png.
And also, I found a simple solution to this problem, I'm not sure if it's the best solution, it's to copy the border before zeroing out the mask's border.
    # deal with border (NOTE: we newly add this four lines to codes)
    tgt[0, mask[0]==1] = src[0, mask[0]==1]
    tgt[-1, mask[-1]==1] = src[-1, mask[-1]==1]
    tgt[mask[:, 0]==1, 0] = src[mask[:, 0]==1, 0]
    tgt[mask[:, -1]==1, -1] = src[mask[:, -1]==1, -1]

    # zero-out edge
    mask[0] = 0
    mask[-1] = 0
    mask[:, 0] = 0
    mask[:, -1] = 0

Sorry for the late reply. Sounds good to me, but you should handle the corner case as well. I tested locally and it seems like it cannot run the example successfully:
$ fpie -s test2_src.png -m test2_mask.png -t test2_tgt.png -o result2.jpg -h1 130 -w1 130 -n 5000 -g src --method grid
Traceback (most recent call last):
  File "/Users/jiayi/.virtualenvs/bin/fpie", line 8, in <module>
    sys.exit(main())
  File "/Users/jiayi/.virtualenvs/lib/python3.9/site-packages/fpie/cli.py", line 37, in main
    n = proc.reset(src, mask, tgt, (args.h0, args.w0), (args.h1, args.w1))
  File "/Users/jiayi/.virtualenvs/lib/python3.9/site-packages/fpie/process.py", line 309, in reset
    tgt[0, mask[0]==1] = src[0, mask[0]==1]
IndexError: boolean index did not match indexed array along dimension 1; dimension is 418 but corresponding boolean dimension is 180

Anyway, the zero-out edge method is the simplest way that can cover most of the input with no error, so feel free to change this error-handling part.


The jupyter-notebook package doesn't install

the package doesn't install no matter how many times I try

Please provide the log


Fix translation error

chamgements -> changements

Sorry for the delay. Thank you a lot!

Sorry for the delay. Thank you a lot!


Vehicles that turn to a building must follow priority rules

see https://github.com/VictorPhilipp/Cities-Skylines-Traffic-Manager-President-Edition/issues/32
copied from https://github.com/VictorPhilipp/Cities-Skylines-Traffic-Manager-President-Edition/issues/57

Summary: If vehicles can cross oncoming traffic to enter a building, they should wait until there is a gap in that traffic before doing so.

Related: #19 , #89

Closing this old ticket; the issue is now being tracked in #1223


Not working with vue2

I'm use with<EMAIL_ADDRESS>and get error:
"export 'computed' was not found in 'vue'
"export 'h' was not found in 'vue'
"export 'onBeforeUnmount' was not found in 'vue'

https://swiperjs.com/vue

Swiper Vue.js components are compatible only with new Vue.js version 3

Add this to the documentation at https://swiperjs.com/vue because I've spent some time figuring out why it doesn't work.

Vue 3 backward compatibility with Vue 2 is now stable with configuration. This means your best bet is to update to Vue 3 with Vue 2 support, and then use Swiper 8+ on Vue 3 components.

Vue 2.7 (setup function) example


Add OCI Change Management diagram to OCI Governance Document

Request that the process (GitHub OCI Change Management Project and diagram) that the P&A Committee has adopted be added to the OCI Governance document as the technical means by which we conform to the overview in section 8. Contributions.
OCI Change Management - OCI Change Management Process v1.0.0.pdf

Keep as internal document


Feature handle proc objects for error messages

relates to https://github.com/hallelujah/valid_email/issues/87

Hi!
I think this kind of feature is up to i18n gem to be implemented, not this gem.
Generally you still have i18n scopes to do what you want without using the :message option.
http://guides.rubyonrails.org/i18n.html#error-message-scopes


Minor fix ages -> names

Fix the illogical variable name that tripped my concentration when reading the proposal… ;-)

Thanks!


Aaron/feature/profile scene

Needs work: create profile scene

@rpavlovs Please review commit https://github.com/ChingStore/ching/pull/47/commits/75dae8d3893c1b53c3074ed6357a2e86b8725cc3 and give me feedback on my use of @flow.

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

Travis automatic deployment: https://47-pr-ching.surge.sh

TODO: Styling edits
TODO: Edit functionality

Travis automatic deployment: https://47-pr-ching.surge.sh

Some issues


[WIP]Fix Todos of Address.cs

fix #1469

:white_check_mark: Build AElf <IP_ADDRESS>21 completed (commit https://github.com/AElfProject/AElf/commit/34b58d79cb by @rosona)

:white_check_mark: Build AElf <IP_ADDRESS>26 completed (commit https://github.com/AElfProject/AElf/commit/ee4552588d by @xiangxingxing)

:white_check_mark: Build AElf <IP_ADDRESS>57 completed (commit https://github.com/AElfProject/AElf/commit/208ce3fb18 by @xiangxingxing)

:x: Build AElf <IP_ADDRESS>11 failed (commit https://github.com/AElfProject/AElf/commit/b9159b776c by @xiangxingxing)

:white_check_mark: Build AElf <IP_ADDRESS>98 completed (commit https://github.com/AElfProject/AElf/commit/dfa04f69fb by @xiangxingxing)


enableVirtualBackground not working webgl [BUG]

Describe the bug
no change use enableVirtualBackground
To Reproduce
1.enablevideo
2.Enter the channel.
3.Run enableVirtualBackground.
or
1.enablevideo
2.Run enableVirtualBackground
3.enter the channel
Expected behavior
expected : enableVirtualBackground works and the background changes to color.
actually executed :  noting(just plain cam screen)
unity 2020.3.33f
webgl
Chrome
ex)
If it works, can I request a demo scene?
add)
The OnVirtualBackgroundSourceEnabled event also doesn't come.

The virtual background isn't available in this version of the baseline Web SDK (4.6.3) while an extension comes in 4.10.0.  So this isn't a bug.   But we will add this as a feature request and work on it on a Sprint for the base SDK upgrade.

The virtual background isn't available in this version of the baseline Web SDK (4.6.3) while an extension comes in 4.10.0. So this isn't a bug. But we will add this as a feature request and work on it on a Sprint for the base SDK upgrade.

thank you reply @icywind
i will wait sdk upgrade


API to get list of example and short description

Hello,
Is ther any API to fetch the list of all available examples as the online IDE (http://wenyan-lang.lingdong.works/ide.html)? Then user have way to load example directly in offline IDE/editor(plugin).
The Snippet Site as #472 can also try to provide such API.

qeury list of code snippet/example, and short decription/remark
get the contenet of specific snippet/exmple, maybe a simple url

To get short remark for an example/snippet, there is need to specify a normalized conversion of comment in wenyan-lang code. Such conversion may also be virtal for stdlib auto-documentation.
Now we have there keyword for comment, 疏, 注, 批, then I think up three type/level comment:

file level (script/module level), remark for the whole file
block level, doc for important compenent, function(术), class, etc
statement level, tips for some tricky statement or algorithm

Then discusstion which keyword match which comment level. In my option, 疏 for file level, 注 for block level, 批 for statement level.
The native meaning of these three keyword refer to https://github.com/LingDong-/wenyan-lang/pull/35 . But we can redifine it for technique purpose.
Then back to the problem in this issue, the short remark accompany with list of example/snippet may be extracted from the first line of file level comment.

Later, considerate the native meaning of 疏 is further comment of 注, I think up another suggestion.

注 used for simple remark for block, normally a short single sentense, or just more descriptive name.
疏 used for detail explain of this block, for 术 main describ it's parameter and return value.
批 still used for statement level tips.

However, comment is not forced syntax, this plan may seam rigid, user should remember one 注 followed by several 疏. While in previous plan seams has more freedom, in most time just use 注, only optional one 疏 in head of file.
Anyway, we just need a standar, then we can develop tool chian based on it.

Hi @lymslive , thanks for bringing this up!
List of examples can be fetched with a POST request to wenyan-snippets.glitch.me/all.
Specific examples can be fetched with wenyan-snippets.glitch.me/api?id=123.
You can read more about the snippets site at #472
In my opinion, 注 should be universally used to explain code. 疏 should be used to supplement 注 where necessary. 批 should only be used as remarks, thoughts, or reviews and not for explaining implementation.

Hi @LingDong-

I've try curl command to query the snippet site, can GET a specific id, but fail to POST to /all, yet can GET /all. But the output is a long json array, that may not what I mean exactlly. I mean first get a list of less (meta) information, mainly title/name and short description etc, not full code, then user can decide to get a specific code snippet interested. When the snippet site is filled with many code spippet, all will be to much data.

The example I mentioned is another thing from snippet site, that are the example in https://github.com/LingDong-/wenyan-lang/tree/master/examples and http://wenyan-lang.lingdong.works/ide.html . I think it make sence to maitenance both, one for smaller official example, another for larger user custom snippet.

I've noticed there is a json file tools/examples_info.js that seams be edited manually? What I suggestion is to write a short comment on top of the example file, then tools/examples_info.js and relative .md doc may auto-generated, like stdlib.

@lymslive Good suggestion, these API's could be quite handy. Thanks for bringing this up!
As for examples_info.js, maybe it is better to keep it that way. Self-documentation is nice, but the examples are for the new comers to read, and magical comments tend to add noise. I know it is currently just a title and some links, but in the future we might want to add more metadata in examples_info.js.
Thanks!

@LingDong-
I understand you concern about examples_info.js
I've integrated Example and Snippet command into vim plugin vim-wenyan which forked from voldikss
However when I test in my home computer

get /all from snippet site is a bit slow, waiting for several seconds, may due to poor net beside larger data transfer.
I also fail to visit https://raw.githubusercontent.com/LingDong-/wenyan-lang/master/tools/examples_info.js to get examples_info.js. So I work around it, now required clone down to local folder and tell vim-plugin where.


[$500] Android - Workspace - Custom Workspace avatar photo disappears after uploading and reappear after a while

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.30-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Create Workspace
Navigate to Settings page and upload custom image for Workspace

Expected Result:
Uploaded image should be stable
Actual Result:
Custom Workspace avatar photo disappears after uploading and reappear after a while
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/00e04549-d3aa-4e50-88c7-b0a9229954bf
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010841358696844191
Upwork Job ID:<PHONE_NUMBER>869579264
Last Price Increase: 2024-02-06

Not a blocker since it's reproducible in staging and production

Not overdue, waiting on proposals

I wonder if this is still reproducible after the navigation refactor.

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue.

Thanks @rezkiy37 , you're good to go 🚀

Great! Thanks @rezkiy37 for investigating!


"not" is not recognised as a builtin test

Basically I'm doing variable is not defined and dansabel complains about the not not being builtin?

❤ Merry Christmas @jokjr


Features/context check

This introduce the ability to link the health to a context and can be useful for Kubernetes autoscale scenario. This fix #16 .

Thank you for this feature, looks good 👍

@cedric-appdirect Could you just add new section in README file, showing short example of Context check?

Oh, absolutely. I forgot about it.


Ryan M: Watch jantareview.com

Ryan M requests the watch of the watch_keyword jantareview\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

jantareview\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Mast in Charcoal HQ


Bricked HA after HACS installation

System Health details
Not available
Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Installed via HACS, the integration requested a re-boot.
HA hasn’t recovered and now shows:
“Could not connect to server
NSURLErrorDomain -1004”
Reproduction steps

...
Debug logs
TBD

Diagnostics dump
No response

I just installed the Integration via HACS on a brand new installation of Home Assistant 2023.12.3 and HACS 1.33.0 with no issues during installation.


Global storage transformers

As discussed in the ZEP call last week, this is a first pass at creating a "global storage transformers" concept, to be applied at the store (rather than array) level.
There are a few things that need cleaning up here:

[ ] Double check that all RST references point to the right place
[ ] Add more detail and example use-cases of both global and array storage transformers
[ ] Add an example of a global storage transformer in zarr.json

But before doing that, I thought I would solicit some feedback on this. Does anyone see any fundamental problems with this concept? My motivating use case is #154.
My main open question is: when both array and global storage transformers are defined, what determines the order in which they are applied? The only feasible choices appear to be to apply all the global transformers either before or after the array transformers. Should we make this an option in the protocol?

Depends on #192

Now conflicting.

@rabernat Could you adapt this PR to cover group storage transformers for the current spec?

On today's call, we decided that we would defer this to an extension after the core v3 spec has been finalized.


Fail ratio calculation for individual requests is incorrect

Description of issue
The fail ratio for each individual request is incorrect, and doesn't match the total fail ratio.
Expected behavior
The fail ratio is correct.
Actual behavior
The fail ratio is incorrect. For example, if 10 out of 10 requests fail, I'd expect the ratio to be 100%, but instead it is 50%.
 Name                                                          # reqs      # fails     Avg     Min     Max  |  Median   req/s
--------------------------------------------------------------------------------------------------------------------------------------------
 GET /                                                             10   10(50.00%)    2014    2009    2021  |    2000    0.75
--------------------------------------------------------------------------------------------------------------------------------------------
 Total                                                             10  10(100.00%)                                       0.75

Environment settings

OS: Windows/Linux
Python version: 3.6
Locust version: 0.11.0

Steps to reproduce (for bug reports)
Create a trivial locustfile.py:

from locust import HttpLocust, TaskSet, task

class UserBehavior(TaskSet):
    @task
    def index(self):
        self.client.get("/")

class WebsiteUser(HttpLocust):
    task_set = UserBehavior

Run it against a host that doesn't have a web server running at all:
locust --host http://localhost --no-web --clients=10 --hatch-rate=2 --run-time=30
All of the "GET /" requests fail, but the stats (as shown above) have the failure rate at 50% rather than 100%.
I think the problem is at stats.py:279:
            return float(self.num_failures) / (self.num_requests + self.num_failures)

It seems like it ought to be:
            return float(self.num_failures) / (self.num_requests)

Maybe at some point self.num_requests was only the count of successful requests?

Maybe at some point self.num_requests was only the count of successful requests?

good catch.. I believe it was.
Do you want to submit a Pull Request with your fix? (If not, I can take care of it)

Sure, I can make a PR.

thanks

Hi guys. Do you have any plans to release that fix? From pip we still get v0.11.0, which is affected by that issue?


[Cranelift] Add COFF TLS support

Feature
Support TLS data objects with COFF binaries.
Benefit
TLS data objects are already supported for ELF and Mach-O binaries.
Implementation
Add a new x86_coff_tls_get_addr instruction. See https://github.com/bjorn3/rustc_codegen_cranelift/issues/388#issuecomment-532930282 for what x86_64 instructions to lower the x86_coff_tls_get_addr instruction to. Then make changes to the object crate as necessary to generate TLS sections for COFF.
Alternatives
N/A

Commenting to note that at the moment, COFF support is the primary blocker to compiling Rust projects like tokei with cg_clif on Windows MSVC.

Thanks for the tracking issue @XAMPPRocky!
This one probably isn't too bad, if you (or another adventurous soul) wants to take a look: I believe it should work similarly to the ELF case, in which we emit a pre-ordained sequence of instructions that the linker recognizes and can fix up. Then we emit that pseudoinst for the sequence based on the TlsModel during lowering. I don't have an MSVC setup handy to work on this but I'm happy to review a PR! :-)

I have a setup available, but I'll admit to being quite out of my depth in terms of writing the assembly, so I could make the PR with some guidance. The steps are relatively straight forward, but I'm not sure how to map that to instructions. For example how do you access a special variable like __tls_used?

Executable code accesses a static TLS data object through the following steps:

At link time, the linker sets the Address of Index field of the TLS directory. This field points to a location where the program expects to receive the TLS index.

The Microsoft run-time library facilitates this process by defining a memory image of the TLS directory and giving it the special name "__tls_used" (Intel x86 platforms) or "_tls_used" (other platforms). The linker looks for this memory image and uses the data there to create the TLS directory. Other compilers that support TLS and work with the Microsoft linker must use this same technique.

When a thread is created, the loader communicates the address of the thread's TLS array by placing the address of the thread environment block (TEB) in the FS register. A pointer to the TLS array is at the offset of 0x2C from the beginning of TEB. This behavior is Intel x86-specific.

The loader assigns the value of the TLS index to the place that was indicated by the Address of Index field.

The executable code retrieves the TLS index and also the location of the TLS array.

The code uses the TLS index and the TLS array location (multiplying the index by 4 and using it as an offset to the array) to get the address of the TLS data area for the given program and module. Each thread has its own TLS data area, but this is transparent to the program, which does not need to know how data is allocated for individual threads.

An individual TLS data object is accessed as some fixed offset into the TLS data area.

The TLS array is an array of addresses that the system maintains for each thread. Each address in this array gives the location of TLS data for a given module (EXE or DLL) within the program. The TLS index indicates which member of the array to use. The index is a number (meaningful only to the system) that identifies the module.

https://docs.microsoft.com/en-us/windows/win32/debug/pe-format#the-tls-section

The _tls_used handling should be done in object's coff write code, not in Cranelift.

This was closed in #4546, forgot to mark it.


SNS Publishing to a mobile endpoint fails with custom payloads

Describe the bug
When publishing to a mobile endpoint with the following code:
val response = snsClient.createPlatformEndpoint {
    platformApplicationArn = Settings.AWS_SNS_PUSH_SERVICE
    token = deviceToken
}

snsClient.publish {
    targetArn = response.endpointArn
    message = payload
    messageStructure = "json"
}

where payload is
{
  "APNS": {
    "aps": {
      "alert": "Engin created a new game!"
    },
    "gameId": "67c329e5-5b59-482c-a5a1-1997746f51e8"
  },
  "APNS_SANDBOX": {
    "aps": {
      "alert": "Engin created a new game!"
    },
    "gameId": "67c329e5-5b59-482c-a5a1-1997746f51e8"
  }
}

Fails with the error:  Invalid parameter: JSON must contain an entry for 'default' or 'APNS'. (3)
If I include the default, only the message is delivered to the clients not the custom field gameId.
Appreciate any help.
Your Environment

AWS Kotlin SDK version used: 0.9.2-alpha
Platform (JVM/JS/Native): JVM Netty
Operating System and version: heroku-20

This was caused by the wrong message structure on my end. For future reference the content top level APNS field needs to be a percent escaped string of a serialized JSON object instead of a straight up JSON object. i.e.
This is correct:
{
  "APNS": "{\"aps\":{\"alert\":\"Engin submitted a card in your game\"},\"gameId\":\"9e1985e8-39ee-4243-b699-d370aa1cdd88\"}",
  "APNS_SANDBOX": "{\"aps\":{\"alert\":\"Engin submitted a card in your game\"},\"gameId\":\"9e1985e8-39ee-4243-b699-d370aa1cdd88\"}"
}

This is wrong:
{
  "APNS": {
    "aps": {
      "alert": "Engin created a new game!"
    },
    "gameId": "67c329e5-5b59-482c-a5a1-1997746f51e8"
  },
  "APNS_SANDBOX": {
    "aps": {
      "alert": "Engin created a new game!"
    },
    "gameId": "67c329e5-5b59-482c-a5a1-1997746f51e8"
  }
}

I hope this helps somebody in the future.


investigate docker+alpine for starexec build

see https://discuss.ocaml.org/t/running-micro-services-implemented-in-ocaml/3425/5 on a possible way to compile a static binary easily. cc @petarvukmirovic @benti for next summer's CASC maybe.

should be fixed in 1.6 by @benti and @petarvukmirovic and @gh-salt 's work.


Docker events issue reintroduced in 1.0

Hi again
The docker events leaking file handle issue in #4804 and #5690 is back in 1.0.
root@docker-01:~ 2 # lsof 2>&1|grep docker.sock|wc -l
35
root@docker-01:~  # docker events
^Croot@docker-01:~ 2 # docker events
^Croot@docker-01:~ 2 # docker events
^Croot@docker-01:~ 2 # lsof 2>&1|grep docker.sock|wc -l
56
root@docker-01:~  # docker events
^Croot@docker-01:~ 2 # docker events
^Croot@docker-01:~ 2 # docker events
^Croot@docker-01:~ 2 # lsof 2>&1|grep docker.sock|wc -l
77

@ross-w are you still seeing this on the latest version?

@jfrazelle Yes, this still seems to be the case on 1.4.1.
root@int-build-systems:~  # lsof 2>&1|grep docker.sock|wc -l
7
root@int-build-systems:~  # docker events
^Croot@int-build-systems:~ 2 # docker events
^Croot@int-build-systems:~ 2 # docker events
^Croot@int-build-systems:~ 2 # lsof 2>&1|grep docker.sock|wc -l
28
root@int-build-systems:~  # docker events
^Croot@int-build-systems:~ 2 # docker events
^Croot@int-build-systems:~ 2 # docker events
^Croot@int-build-systems:~ 2 # docker events
^Croot@int-build-systems:~ 2 # lsof 2>&1|grep docker.sock|wc -l
56

Hmm, since 1.5.0 this problem has suddenly got much worse (and we're constantly getting 'too many open files' messages, despite increasing the limit to ridiculous levels):
root@int-docker-03:~  # pidof docker
4628
root@int-docker-03:~ 2 # lsof 2>&1|grep 4628|wc -l
102106
root@int-docker-03:~  # docker events
^Croot@int-docker-03:~ 2 # docker events
^Croot@int-docker-03:~ 2 # docker events
^Croot@int-docker-03:~ 2 # docker events
^Croot@int-docker-03:~ 2 # lsof 2>&1|grep 4628|wc -l
102324


golangci-lint 1.35.0

Updating package golangci-lint to release v1.35.0.
Release info
Changelog
b3491fd Update docs for v1.34.1 release  (#1591)
62710a8 Validate gocritic settings. Return error if settings includes a unsupported gocritic checker (#1563)
76c4521 add 'predeclared' linter (#1606)
c0ad76f build(deps): bump @emotion/core from 10.0.35 to 10.1.1 in /docs (#1625)
5521750 build(deps): bump @mdx-js/mdx from 1.6.18 to 1.6.22 in /docs (#1624)
75a29b7 build(deps): bump gatsby from 2.29.2 to 2.29.3 in /docs (#1627)
8a87f77 build(deps): bump gatsby-plugin-canonical-urls in /docs (#1619)
da67d3e build(deps): bump gatsby-plugin-catch-links in /docs (#1603)
7b070ed build(deps): bump gatsby-plugin-google-analytics in /docs (#1604)
4bdd488 build(deps): bump gatsby-plugin-manifest from 2.4.27 to 2.9.1 in /docs (#1607)
04b4943 build(deps): bump gatsby-plugin-mdx from 1.2.43 to 1.7.1 in /docs (#1615)
cfbbead build(deps): bump gatsby-plugin-netlify from 2.3.13 to 2.8.0 in /docs (#1628)
81bf16c build(deps): bump gatsby-plugin-offline from 3.2.27 to 3.7.1 in /docs (#1613)
4adc65e build(deps): bump gatsby-plugin-react-helmet in /docs (#1621)
c7f10f4 build(deps): bump gatsby-plugin-sharp from 2.6.40 to 2.11.2 in /docs (#1609)
986732a build(deps): bump gatsby-plugin-sitemap from 2.4.14 to 2.9.0 in /docs (#1605)
8fa1ae3 build(deps): bump gatsby-remark-autolink-headers in /docs (#1611)
a39435d build(deps): bump gatsby-remark-copy-linked-files in /docs (#1620)
a4050b3 build(deps): bump gatsby-remark-embedder from 4.0.0 to 4.1.0 in /docs (#1616)
da560fe build(deps): bump gatsby-remark-images from 3.6.0 to 3.8.1 in /docs (#1601)
9959e5f build(deps): bump gatsby-remark-responsive-iframe in /docs (#1610)
571a477 build(deps): bump gatsby-source-filesystem from 2.3.30 to 2.8.1 in /docs (#1617)
e84a8d0 build(deps): bump gatsby-transformer-remark in /docs (#1612)
b45dffa build(deps): bump gatsby-transformer-sharp from 2.5.15 to 2.9.0 in /docs (#1608)
fdb4e86 build(deps): bump gatsby-transformer-yaml from 2.4.11 to 2.8.0 in /docs (#1622)
5c9e386 build(deps): bump github.com/go-critic/go-critic from 0.5.2 to 0.5.3 (#1631)
1221939 build(deps): bump github.com/kulti/thelper from 0.1.0 to 0.2.0 (#1630)
eb28c6a build(deps): bump polished from 4.0.3 to 4.0.5 in /docs (#1602)
a64afd8 build(deps): bump puppeteer from 5.4.1 to 5.5.0 in /docs (#1614)
aa6b9fa build(deps): bump react-dom from 16.13.1 to 16.14.0 in /docs (#1618)
13698dc build(deps): bump react-headroom from 3.0.1 to 3.1.0 in /docs (#1629)
90a6919 build(deps): bump react-icons from 3.11.0 to 4.1.0 in /docs (#1626)
1e5ba1e fix: modules-download-mode support (#1593)

#1160

#1160


Fix https://github.com/ballerina-platform/ballerina-lang/issues/18465

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #18465 , #18467
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #18478   +/-   ##
=======================================
  Coverage   15.15%   15.15%
=======================================
  Files          48       48
  Lines        1254     1254
  Branches      197      197
=======================================
  Hits          190      190
  Misses       1050     1050
  Partials       14       14

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 c34009c...e1b3b81. Read the comment docs.


Does a map file exist?

Is there a map file which can be included? I am referring to this Chrome Inspector message:
DevTools failed to load SourceMap: Could not load content for https://rawgit.com/RobinHerbots/Inputmask/5.x/dist/jquery.inputmask.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

I removed the option for the production build.  So future versions won't show the message.


IPv6 support

Please add ipv6 support

we could consider adopting some code from zeroconf which does a fair bit of this https://github.com/grandcat/zeroconf but it does have its own quirks.

Do you have an update on this because in IPv4 mode no multiple mDNS server are possible in the same network

There's some work in https://github.com/pion/mdns/pull/173 that gets us a lot closer. Once that's in, I may just pick this up.


move travel duration calculation from the preprocessing step into the app

right now we calculate the travel duration in the process-data.js as a preprocessing step before launching local dev server. we should move this logic to be part of the app.

this only makes sense when we can select the destination as part of the app and we can change the destination as the app is running. I'm closing this issue but keep #3 open


Seems to be working very slowly due to a wordlist being used

We need to find another way to crawl the domains fast and stealthily. This brute force (current) approach is too noisy and heavy.

done :)


Rewrite generic parameter contraint on repack?

As all of us know that it is impossible to use generic like this in C#:
class C<TEnum> where TEnum : Enum {
    public TNewEnum Convert<TNewEnum>(TEnum value)
              where TNewEnum : Enum {
         return (TNewEnum)value;
    }
}

Actually .NET CLR supports using Enum as a generic constraint, but C# compiler does not support that for some reason.
Is it possible to instruct ILRepack to rewrite the generic constraints replacing all TEnum and TNewEnum to Enum so we can get a result like the above?
class C<TEnum> where TEnum : IFormattable, IConvertible, IComparable {
    public TNewEnum Convert<TNewEnum>(TEnum value)
              where TNewEnum : IFormattable, IConvertible, IComparable {
         return (TNewEnum)Convert.ChangeType(Convert.ChangeType(value, typeof(TEnum).GetEnumUnderlyingType()), typeof(TNewEnum).GetEnumUnderlyingType());
    }
}

Hi,
If I understand what you want to achieve, then while it's surely possible for ILRepack to do it (as it rewrites IL), it's also well out of its scope/purpose, e.g. you'd want that for a single library, not only when merging assemblies together.
Consider looking towards Fody for that, quickly looking through its existing plugin list, it's even possible that ExtraConstraints could achieve exactly what you want.
Cheers.

Thank you for mentioning Fody. I did read about it before.
I don't know whether it supports .NET versions before 4.5 well.
Do you think it worthwhile to build a similar plugin system to ILRepack, so people can do more with it?

Hi, I believe tools/libraries are better kept small & focused rather than multi-purpose.
In that respect, ILRepack should remain focused on merging libraries & dependencies (which already involves a lot of customization), and not venture in other IL manipulation areas.
A plugin system could make sense for all the merging-related features (WPF, Resources, Doc...), but not beyond that.


Drop pyoxigraph build for Android target.

I'm sorry for uploading a personal modification. It was a mistake.

If you need to fix some stuff to make Oxigraph work on Android, it would be very welcome to upstream them :)


Cannot download profiles with docker deployment

Describe the bug
Got this
curl -X POST http://localhost:9596/eth/v1/lodestar/write_profile
{"statusCode":500,"error":"Internal Server Error","message":"EACCES: permission denied, open 'network_thread_2023-09-17T07:27:59.957Z.cpuprofile'"}

Expected behavior
after a profile is captured, node should persist it to file system successfully, similar to getStateV2
Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.11.0

more logs:
Sep-17 07:27:59.961[rest]            ^[[31merror^[[39m: Req req-2kkg writeProfile error  EACCES: permission denied, open 'network_thread_2023-09-17T07:27:59.957Z.cpuprofile'
Error: EACCES: permission denied, open 'network_thread_2023-09-17T07:27:59.957Z.cpuprofile'
    at Object.openSync (node:fs:602:3)
    at Object.writeFileSync (node:fs:2334:35)
    at writeProfile (file:///usr/app/packages/beacon-node/lib/network/core/networkCoreWorker.js:120:12)

curl -X POST http://localhost:9596/eth/v1/lodestar/write_profile?thread=main
{"statusCode":500,"code":"EACCES","error":"Internal Server Error","message":"EACCES: permission denied, open 'main_thread_2023-09-17T07:47:08.932Z.cpuprofile'"}

Sep-17 07:47:08.952[rest]            ^[[31merror^[[39m: Req req-2lav writeProfile error  EACCES: permission denied, open 'main_thread_2023-09-17T07:47:08.932Z.cpuprofile'
Error: EACCES: permission denied, open 'main_thread_2023-09-17T07:47:08.932Z.cpuprofile'
    at Object.openSync (node:fs:602:3)
    at Object.writeFileSync (node:fs:2334:35)
    at Object.writeProfile (file:///usr/app/packages/beacon-node/src/api/impl/lodestar/index.ts:77:16)
    at Object.handler (file:///usr/app/packages/api/src/utils/server/genericJsonServer.ts:45:23)

curl -X POST http://localhost:9596/eth/v1/lodestar/write_profile?thread=discv5
{"statusCode":500,"error":"Internal Server Error","message":"EACCES: permission denied, open 'discv5_thread_2023-09-17T07:54:53.328Z.cpuprofile'"}

Error: EACCES: permission denied, open 'discv5_thread_2023-09-17T07:54:53.328Z.cpuprofile'
    at Object.openSync (node:fs:602:3)
    at Object.writeFileSync (node:fs:2334:35)
    at writeProfile (file:///usr/app/packages/beacon-node/lib/network/discv5/worker.js:93:12)

@tuyennhv what full path is it trying to write the file to?

@tuyennhv what full path is it trying to write the file to?

@dapplion by default it writes the file to beacon folder, I did not specify "dirpath" in my curl url

work around way is to log into docker container, change the file permission, then do the curl
docker exec -u root -it <container_name_or_id> /bin/sh
chmod 777 .
exit
curl -X POST http://localhost:9596/eth/v1/lodestar/write_profile?thread=main

then copy cpuprofile to the host: docker cp 95777e4156f4:/usr/app/main_thread_2023-12-21T07:05:54.956Z.cpuprofile .


List of publications in tabs gets mixed up

See attached json:
I started with an existing JSON that has 10 different publications.
After editing some of them, one publication is now present three times:

Search for the title: "Title": "Replicability, Robustness, and Reproducibility in Psychological Science"
This is present 3 times
But the other indicators seem to be from the old publication

Maybe only the metadata (doi, title, etc) is overwritten for some reason?
resque_schönbrodt_1726124754422.json

I think this should be fixed now f0b693fb4c560e21b0166ae0169aceae908091f5

Maybe only the metadata (doi, title, etc) is overwritten for some reason?

This is what was happening. For me, it only happened after reloading the website after I imported the JSON file.
We have some 'effects' that are called after changes in the data. Our metadata fetching function was dependent on another one (currentInput is updated somewhere else, but we were using it for fetching the metadata), now the function for metadata is self-reliant, it only uses the currentTab variable.


Question: Route parameters across all platforms

First of all, this is just a question not an issue.
How can we implement route parameters across all platforms?
Web needs ActivatedRoute from '@angular/router' whereas Nativescript needs PageRoute from 'nativescript-angular/router'

Hi @sunjith You can use ActivatedRoute with NativeScript just the same as web 😄
See this for example (again, it's identical to web - it's quite nice):
https://github.com/NativeScript/nativescript-angular/blob/master/ng-sample/app/examples/router/router-outlet-test.ts#L33-L35
With route config example here:
https://github.com/NativeScript/nativescript-angular/blob/master/ng-sample/app/examples/router/router-outlet-test.ts#L62-L65

@NathanWalker Great! Thanks a lot.


Recent merges broke make distcheck

A file is left in the dap4_test directory. I will submit a fix shortly.
ERROR: files left in build directory after distclean:
./dap4_test/tmp_1025
Makefile:981: recipe for target 'distcleancheck' failed

Do not try to fix this. There is a bigger issue here. The fact that you are seeing this
means that DISKLESS support is disabled.

OK I will take down PR.
But can you please fix soon @DennisHeimbigner? It is breaking the make distcheck runs of my CI, and those are very handy to have. In fact, if you guys had them running, this problem would have showed up before these changes were merged. ;-)

I routinely use make distcheck. However we never run with DISKLESS turned off?

My proposed fix is to modify defile.c
The modified file is attached for you to test.
d4file.zip

OK, I get it. This is not test output but output of DAP and should have been removed by DAP?
I used this to get a broken distcheck. It is a parallel build:
make distclean && autoreconf -i && CC=mpicc CFLAGS='-Wall -g' CPPFLAGS='-I/usr/local/zlib-1.2.11_mpich-3.2/include -I/usr/local/szlib-2.1_mpich-3.2/include -I/usr/local/hdf5-1.10.1_mpich-3.2/include' LDFLAGS='-L/usr/local/zlib-1.2.11_mpich-3.2/lib -L/usr/local/szlib-2.1_mpich-3.2/lib -L/usr/local/hdf5-1.10.1_mpich-3.2/lib' ./configure && CC=mpicc CFLAGS='-Wall -g' CPPFLAGS='-I/usr/local/zlib-1.2.11_mpich-3.2/include -I/usr/local/szlib-2.1_mpich-3.2/include -I/usr/local/hdf5-1.10.1_mpich-3.2/include' LDFLAGS='-L/usr/local/zlib-1.2.11_mpich-3.2/lib -L/usr/local/szlib-2.1_mpich-3.2/lib -L/usr/local/hdf5-1.10.1_mpich-3.2/lib' make distcheck
This breaks on master right now like this:
rm -f Makefile
ERROR: files left in build directory after distclean:
./dap4_test/tmp_1025
Makefile:981: recipe for target 'distcleancheck' failed

I tried your fix, but it didn't work. Same problem, a tmp_ file left over after make distcheck.
Here's some output with the changed d4file.c you sent:
make_output_2.txt
config.log

I am completely baffled. You should see that file only in one of two ways.

The url being used is prefixed with [debug] or [copy]
the program was stopped before nc_close() was called.
As a speculation, try making without -j flag

Not using the -j flag yet. (Can't start until outstanding PR is merged.)
Do we even need this to work? My goal was just to make sure PIO doesn't break anything. And for that I need it to work with a regular build of the distribution, and a distcheck that builds with parallel. So I should be using:
make distclean && autoreconf -i && CFLAGS='-Wall -g' CPPFLAGS='-I/usr/local/zlib-1.2.11/include -I/usr/local/szlib-2.1/include -I/usr/local/hdf5-1.10.1/include' LDFLAGS='-L/usr/local/zlib-1.2.11/lib -L/usr/local/szlib-2.1/lib -L/usr/local/hdf5-1.10.1/lib' ./configure && CC=mpicc CFLAGS='-Wall -g' CPPFLAGS='-I/usr/local/zlib-1.2.11_mpich-3.2/include -I/usr/local/szlib-2.1_mpich-3.2/include -I/usr/local/hdf5-1.10.1_mpich-3.2/include' LDFLAGS='-L/usr/local/zlib-1.2.11_mpich-3.2/lib -L/usr/local/szlib-2.1_mpich-3.2/lib -L/usr/local/hdf5-1.10.1_mpich-3.2/lib' make distcheck
And that actually does work. So my bad. I will close this ticket. Why a distribution built with mpicc does not work is probably a mystery we need not solve.


feat(cli): next version

This PR introduces the next version of the CLI. This PR includes BREAKING CHANGES of the current CLI interface.

[x] Rename APIKey to Service Token
[ ] Use the PDP API
[ ] Introduce environments
[ ] Send client particulars over user-agent header

@jasonkuhrt Note that this was merged today https://github.com/prisma/prisma/pull/23056
It should make it easier for you to run tests. And you have to put tests inside the platform directory for that (if you crate test files).
Let me know if you have any question

@Jolg42 Thanks will take a look! We're still at a stage of shipping a prototype so not sure we're going to have tests like last time. Appreciate you keeping us in the loop on developments there! 🙏

It looks like there are conflicts, I didn't expect that. Will investigate.

The conflict was trivially resolved by Git, it looked more intimidating than it was :D

@jasonkuhrt For info, all tests are failing which is a big blocker for this PR, we can't merge without fixing this.
See for example https://github.com/prisma/prisma/actions/runs/7922500498/job/21630227904?pr=23090#step:4:285
Error: s/cli build: ✘ [ERROR] Could not resolve "./platform/*Platform"
packages/cli build:     src/bin.ts:30:25:
packages/cli build:       30 │ import { Platform } from './platform/*Platform'
packages/cli build:          ╵                          ~~~~~~~~~~~~~~~~~~~~~~
packages/cli build: Failed

I'll review the code now

@jasonkuhrt it looks like something went wrong with your git changes.

And GitHub Actions are not running as a result, which is expected when there is a conflict.
I can recommend using the simple "update branch" button for syncing main:

@Jolg42 meetings done and I am now focused on this PR!

Investigating CI / Tests / CLI commands (library, ubuntu-latest, 20) (pull_request) Failing after 1m now.

Thanks @prisma/orm! Will merge as soon as CI is green 🚀 .


Typo fix and minor code fix

This fixes a typo in comments and the redundant definition of a dict.

Awesome. Thanks for the help, I'm still working out with my English.


Match output dictionary of model.step, ignoring logits return var

model.step returns five params (logits, loss, accuracy, norm, and update), so logits must be ignored otherwise error is generated (at least in Python 2.7.12):
Traceback (most recent call last):
  File "train.py", line 279, in <module>
    train(FLAGS)
  File "train.py", line 117, in train
    FLAGS.l, FLAGS.e, forward_only=False)
ValueError: too many values to unpack

Fixed by removing logits return instead in latest commit.

Thank you! I was running it for nmt and noticed I forgot to change it back from testing something.


Any fork?

This project is no longer maintained. Do you know of any fork/new project that is maintained and updates everything to the latest versions?

Old issue, but I did make one that does the same thing.


TypeError with Card 3D Secure payment and Next JS build

Describe the bug
Using Next JS (library version below), 3d secure payment doesn't work correctly with Cards after building.
In development mode by running the code with command next dev everything works as intended. When I build the code with next build and later start it on a webpack dev server with next start I get the following error

"TypeError Invalid attempt to destructure non-iterable instance.
In order to be iterable, non-array objects must have a Symbol.iterator method."

I'm using the cards listed here (American Express, Maestro, Visa and Discover)
I'm following the component based approach: after creating the AdyenCheckout class I'm rendering each payment method received from the API call.
const configuration: CoreOptions = {
 environment: payments.adyen.environment,
 clientKey: payments.adyen.clientKey,
 session: {
   id: result.sessionId,
   sessionData: result.sessionData,
 },
 showPayButton: true,
 locale,
 onPaymentCompleted: async (result: CheckoutSessionPaymentResponse) => {
   switch (result.resultCode.toLowerCase()) {
     case "authorised":
       router.replace(nextPageUrl");
       break;
     case "refused":
       showPaymentOutcome(PaymentOutcome.Refused);
       break;
     case "cancelled":
       router.back();
       void showNotification({ message: formatMessage("checkout.canceledError"), type: NotificationType.Error });
       break;
     default:
       showPaymentOutcome(PaymentOutcome.Failure);
   }
 },
 onError: (error: Error) => {
   console.error("----- ERROR -----");
   console.error(error.name);
   console.error(error.message);
   console.error(error.stack);

   showPaymentOutcome(PaymentOutcome.Failure);
 },
};

const checkout = await AdyenCheckout(configuration);
setCore(checkout);

return (

        {core?.paymentMethodsResponse?.paymentMethods?.map((elem, index) => {
          const isSelected = selectedTab === index;
          return (
            <Box key={elem.type} className={`${styles["adyen-payment-method-container"]} ${isSelected ? styles["selected"] : ""} ${paymentOutcome != null ? styles["hide"] : ""}`}>
              <Accordion expanded={isSelected}>
                <AccordionSummary onClick={() => setSelectedTab(isSelected ? null : index)} expandIcon={<Radio size="small" checked={isSelected} />}>
                  {elem.name}
                </AccordionSummary>
                <AccordionDetails>

                </AccordionDetails>
              </Accordion>
            </Box>
          );
        })}

);

Expected behavior
3d secure should work both in development and build mode
Screenshots
Insert data

Development mode result

Build mode result

Desktop:

OS: macOS Ventura 13.0.1
Browser Chrome 109.0.5414.119

Libraries:

Next JS 12.3.1
React 18.2.0
Adyen Web: 5.30.1 - 5.31.0 - 5.32.0

Steps to reproduce the behavior:

Build code with next build
Start a webpack dev server with next start
Start a new Adyen payment transaction
Choose card payment
fill fields with values from Test cards
click on "Pay" button

Hello @FranNetti,
We had exactly the same issue.
We found a solution. In our Next config, we used swcMinify set to true.
When we removed this line "swcMinify: true", the 3DS2 payment has been fixed.
Hope this helps you.

I also have some 3DS problems and I see some TypeError, but I'm not on next.js

@FranNetti - can you confirm whether the solution proposed by @tleyris works for you? Thanks

Hi all, thanks a lot @tleyris I did what you suggested me and now it works!
I don't know if this is something to report to NextJS, because there is a bug in their swc minification, or if it's a bug of adyen library that happens only with swc. I think it's the latter, but I'm not sure about this: what do you think?

Hello @FranNetti
We have tested SWC in our React implementation playground and it still works in production mode. So it might be something with either Next+SWC or the default configurations Next uses with SWC.
For now I will close this issue. If you find any more relevant information for testing we can reopen the ticket.


Union types are not allowed in indexers

I have declared function getter(key: string|number).
Inside I try to do var x = someObject[key]
I get a TS error saying "An index expression argument must be of type 'string', 'number' or 'any'.
Obviously key satisfies this constraint as it is either a string or a number. But I guess the TS compiler does hard type equality checks in this case.

You're right, we'll fix that.