[Gradle] Cannot create parent directory for lock file

Exception in thread "main" java.lang.RuntimeException: Could not create parent directory for lock file /root/.gradle/wrapper/dists/gradle-6.5.1-all/cdund22i8guosqylfo49op4dv/gradle-6.5.1-all.zip.lck
	at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:43)
	at org.gradle.wrapper.Install.createDist(Install.java:48)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:63)

Dear @starsareintherose, the problem seems related to your installation, rather than to grobid. Could you please share more information about your environment?

Actually, I am trying to put this repo to AUR (Arch Linux), so I write a PKGBUILD (similar to Shell script) to help more people to install it.
My PKGBIULD is here. and All the files are attached.
# Maintainer: Malacology <guoyizhang at malacology dot com>
# Contributor: Malacology <guoyizhang at malacology dot com>

pkgname=grobid
pkgver=0.7.0
pkgrel=1
pkgdesc="A machine learning software for extracting information from scholarly documents"
arch=('any')
url="https://github.com/kermitt2/grobid"
conflicts=('grobid-git')
license=('Apache-2.0 License')
depends=(
	'java-runtime'
)
source=("https://github.com/kermitt2/grobid/archive/$pkgver.zip")
sha256sums=('SKIP')

package() {
  install -dDm755 "$pkgdir"/usr/{bin,share/grobid}
  cd $pkgname-$pkgver
  mv * $pkgdir/usr/share/grobid
  cd $pkgdir/usr/share/grobid
  chmod +x *
  ./gradlew clean install

}

error log is here.
░▒▓ ~/Dow/Grobid ▓▒░ makepkg    ░▒▓ ✔  14:07:46 ▓▒░
==> Making package: grobid 0.7.0-1 (Tue 17 Aug 2021 14:08:39 CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found 0.7.0.zip
==> Validating source files with sha256sums...
    0.7.0.zip ... Skipped
==> Extracting sources...
  -> Extracting 0.7.0.zip with bsdtar
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
Exception in thread "main" java.lang.RuntimeException: Could not create parent directory for lock file /root/.gradle/wrapper/dists/gradle-6.5.1-all/cdund22i8guosqylfo49op4dv/gradle-6.5.1-all.zip.lck
	at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:43)
	at org.gradle.wrapper.Install.createDist(Install.java:48)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:63)
==> ERROR: A failure occurred in package().
    Aborting...

Hi, are you running the command as root? Cause the error seems to indicate that the process cannot create a parent directory under /root/.gradle. The ./gradlew command is downloading the gradle jar, and it seems it's not able to extract it.
Minor remark, I think that you could do:
chmod +x gradlew rather than chmod +x *

That's so strange, the shell script in package() { } is running as fakeroot.

Well, in principle this issue is not related to grobid. I cannot really help on arch Linux, perhaps you could check why such directory cannot be created

That's so strange, the shell script in package() { } is running as fakeroot.

You are on the right track here. Since package() runs as fakeroot, $HOME is set to /root. gradlew attempts to work inside of /root and fails.
A solution is to run gradlew in the build() function. However, I think there are more changes needed to make the PKGBUILD work properly:

You also want to set GRADLE_USER_HOME=${srcdir}/gradle or something like that so that makepkg does not mess with the user's home.
A path to the local m2 repository needs to be specified as well and grobid will be installed there.
gradle is currently used in version 6.5.1. This only support Java up to version 14. According to the documentation (https://grobid.readthedocs.io/en/latest/Install-Grobid/), grobid itself requires something between Java 8 and 11. So you need to adjust the dependency and make sure that a suitable java version is used for building (e.g. using archlinux-java-run).
gradle should probably be launched with --no-daemon so that no running daemon is left behind.
For building, I assume that a JDK is required and a JRE is not sufficient. So you need a build dependency on java-environment.
The license should simply be "Apache" because it can be found under that name in the license package.

Here's a suggestion, however you still need to implement the package() function. I have no idea what needs to be installed and what not. You find the jars in ${srcdir}/m2.
# Maintainer: Malacology <guoyizhang at malacology dot com>

pkgname=grobid
pkgver=0.7.0
pkgrel=1
pkgdesc="A machine learning software for extracting information from scholarly documents"
arch=('any')
url="https://github.com/kermitt2/grobid"
conflicts=('grobid-git')
license=('Apache')
depends=(
	'java-runtime<=11'
	'archlinux-java-run'
)
makedepends=(
	'java-environment<=11'
)
source=("https://github.com/kermitt2/grobid/archive/$pkgver.zip")
sha256sums=(31c48f63d013e7be6731cbc3fa5c872af82d9c9b871ed422bbc5d9fca512297a)

build() {
  export GRADLE_USER_HOME=${srcdir}/gradle
  export JAVA_HOME=$(archlinux-java-run -b 11 -f jdk -j)

  mkdir -p "${srcdir}"/{gradle,m2}

  cd $pkgname-$pkgver
  ./gradlew --no-daemon -Dmaven.repo.local=${srcdir}/m2 clean install
}

#check() {
#  export GRADLE_USER_HOME=${srcdir}/gradle
#  export JAVA_HOME=$(archlinux-java-run -b 11 -f jdk -j)
#
#  cd $pkgname-$pkgver
#  ./gradlew --no-daemon -Dmaven.repo.local=${srcdir}/m2 cleanTest test
#}

package() {
  true
  # to be written
}

If you are packaging GROBID to run as a service, you might also want to package a distro-specific configuration file and init file.
In particular, GROBID (via pdfalto, I think) needs to write to disk when parsing PDF files. I've found it works best to have this temp dir be a ramdisk. Using systemd / tmpfiles.d, I install a file like this, then point to it from both TMPDIR (as an init environment variable for the daemon) and the YAML configuration file.
#Type Path        Mode UID  GID  Age Argument
d    /run/grobid/tmp   0755 {{ grobid_user }} {{ grobid_user }} 10d -

(where grobid_user is a template)
I don't run Arch, and do this installation via ansible, but it might be relevant.

Click Gradle Settings to go to gradle configuration page

Change gradle user home to empty.
so I changed gradle configuration to its default position, which is empty , and that fortunately fixed the problem.
I don’t know and want to know the exact underlying causes, just to take a note about the fix.


add support of feature flag for runnables

close #4464

Updated @matklad let me know if it's good for you :)


pdf with sideways tables has text cut-off

I'm interested in table 2 of the attached document.  It's sideways, and covers multiple pages - so it's not an easy table to capture.  Copy/paste into Excel creates too many entries (it sees all breaks as spaces)- so this is one that needs to be entered cell-by-cell, or using a tool like tabula.  I did not get errors, but I did not get the desired output either.
Page 1: Columns 1 and 2 worked beautifully, but column 3 was truncated.
Page 2: Column 1 was truncated from the left, and column 3 was truncated from the right.  (Column 2 did work though)
The paper is available at https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3066620/pdf/z7g4921.pdf, if the file did not upload correctly.
Thanks!
Chowdhury et al. - 2010 - Proteome analysis of human aqueous humor.pdf

Hi @melissakey,
Rotating PDF pages is a capability that is common to many PDF viewing and editing programs like Adobe Reader, Mac Preview, Evince and pdftk; we recommend that you rotate your PDF in one of those programs first, save it, then upload it to Tabula for extraction.
Thanks!


Ignore E523 (not allowed here) error when UI blocks

fidget.nvim will raise errors when some plugins like clever-f are
used: when the 'emulated' operator is pending, a 'textlock' is held
but the event loop will still be running and trying to draw figdets.
There seems no a good way to tell whether it is safe to draw fidgets
(despite the vim.schedule deferral, see #29); surprisingly,
an easy workaround is to simply ignore the E523 error.
Fixes #68

@j-hui @rockyzhang24 I think this is now ready to be merged.

Thanks for the hard work here @wookayin ! With some preliminary testing, this looks ok to me. I'll drive this around for the rest of today and merge in unless I encounter any issues.
It's a shame that we have to resort to this kind of exception-handling to get smooth behavior. I wonder how other plugins get around this issue (in particular, nvim-notify).

Good point! Actually nvim-notify would have the same issue when clever-f is used but it does the job well. I haven't checked how it manages to draw and free the dialogue box, but if its way is more principled approach we should definitely adopt rather than having such a exception-catching workaround.


E2E tests for actor features.

Description
E2E tests for actor features.
Plus, some other small fixes.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #821
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[ ] Unit tests passing
[X] End-to-end tests passing
[ ] Extended the documentation
[ ] Specification has been updated
[ ] Provided sample for the feature

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


Fix number validation and native split behavior

Codecov Report

Merging #45 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   93.31%   93.33%   +0.01%
==========================================
  Files           1        1
  Lines         434      435       +1
==========================================
+ Hits          405      406       +1
  Misses         29       29

Impacted Files
Coverage Δ

dist/granim.js
93.33% <100%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

There is a weird bug where a config like this will work
customDirection: {
	x0: '50px',
	y0: '00',
	x1: '0',
	y1: '0'
},

Because unit will save the value of the first customDirection tested (in this case, it will always be 'px' in stead of 'px' then undefined after another iteration on the while loop, despite reiniting the value var).
I think this is because variable are hoisted in js, so we need to set a base value when defining it in the while value (when it is in case defined at the beginning of the function).
To fix that, you can change validateInput.js:58 from
} else {
	var unit , splittedValue;

to
} else {
	var splittedValue = null;
	var unit = null;

@sarcadass maybe it comes from the variable value which is declared before the loop, since the value of unit and splittedValueare based on it, it could come from that.
Maybe try to simply declare var value = array[i] inside the loop.

Maybe I don't understand but !/^\d+$/.test(0) returns false as it should.

Sorry about that, your regexp works for the value 0, but it doesn't work with float values like 251.23.


[SPARK-48752][FOLLOWUP][PYTHON][DOCS] Use explicit name for line number in log

What changes were proposed in this pull request?
This PR followups for https://github.com/apache/spark/pull/47145 to rename the log field naming
Why are the changes needed?
line_no is not very intuitive so we better renaming to line_number explicitly.
Does this PR introduce any user-facing change?
No API change, but user-facing log message will be improved
How was this patch tested?

The existing CI should pass
Was this patch authored or co-authored using generative AI tooling?

No

cc @HyukjinKwon

Thanks! Merged to master


Seperate widgets to their own files

StoryDetailRoute class is to bloated and hard to work on. Widgets should be extacted to their own class files.

done.


TrumpScript should handle Race Conditions in multi-threaded applications by:

Terminating threads with the least amount of resources, along with all their children, reallocating the resources to the most privileged thread. In fact, TrumpScript should only run on a single, American thread. One Thread, Under Trump, Indivisible, With Comb-Overs and 2 Corinthians for all.

The main race conditions right now are Iowa, New Hampshire, and South Carolina as the first states to primary and caucus! These will be resolved in a few weeks.

You're not trying to play the race card, are you?

See a76f078


docs: example preview

Change Summary
This PR adds interactive frames render to docs...
Merge Checklist

[x] PR has a Changeset
[x] PR includes documentation if necessary
[x] PR updates the boilerplates if necessary

@stephancill ah right, sorry. I think there was an issue with embedding web containers at least in Safari. I will take a look.

@michalkvasnicak makes sense - do you have a sense of how it performs?

@stephancill I removed the examples renderer and used stackblitz embed instead. Also stackblitz doesn't work properly in Safari but I guess that's just a minor issue and will be eventually fixed in next versions of Safari.

@michalkvasnicak is stackblitz working for you?

@stephancill in Safari it doesn't work properly. In chrome it works locally but doesn't work on preview branch. Perhaps wrong setting for headers. Will investigate.

@stephancill it seems that vercel preview is not returning the headers I set in vercel.json

@stephancill this is ready for review

@michalkvasnicak just doing a final review


Update repositories.txt

Is this one correct??

Hi @xouty2k. The bot has reported one problem, but there is actually another problem in addition, which is that there is no library.properties file. Please make sure to add one before creating the tag or release.
You can learn all the requirements for a successful submission here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#what-are-the-requirements-for-a-library-to-be-added-to-library-manager
Please let me know if you have any questions.

For the sake of a tidy repository, I'm going to close this due to lack of activity.
@xouty2k if you ever resolve the issues reported by the bot, feel free to submit another pull request to add the library.
I'll continue to monitor this thread, so feel free to let me know if you have any questions or concerns.


Add 2019 sponsors to homepage

Still awaiting GoCardless logo, so that's commented out for now.
Signed-off-by: Julius Volz<EMAIL_ADDRESS>

@brian-brazil @RichiH

:+1:


Map Click reopens Left Info Pane?

Steps to reproduce

Close left side info pane
Click map
Info pane doesn't open

Expected behaviour
Info pane re-opens
Actual behaviour
Info pane doesn't open
Client configuration
Chrome

Thanks for this bug @bertgranberg. This fix has been deployed to production.


Returns error "Failed to match keys" and doesn't extract

I have command window CD'd into the folder with the exe, along with the keys and the xci I'm trying to unpack. I run the command hactool.exe -k prod.keys totk.xci and I get a warn that prod.keys doesn't exist, along with a list of "failed to match key" errors.

Hello Gorm. It's not obvious in the documentation, but you need to specify the type of your input file. It looks like your file is XCI so add --intype xci to your command.


Somehow the palette menus became Gigantic

I don't know how this happened. It's in Firefox. Chrome is okay.
The regular cmd-- and cmd-+ don't change the palette menu's size, only the content (which is expected behavior). So what changes the palette menu's size??

We implement our own zooming for the canvas scene but every now and then you can mistakenly end up zooming the browser window itself. It's hard to catch all the cases and harder still to prevent the browser from zooming, especially on mobile.
You can reset the zoom from your url bar, in your case by clicking on the 210%:

Thank you!!! Problem solved 💯


Add character count to engagement form description

#1414
-Add character count to description

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1524 (9e50144) into main (71413a9) will decrease coverage by 0.01%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main    #1524      +/-   ##
==========================================
- Coverage   72.00%   72.00%   -0.01%
==========================================
  Files         336      336
  Lines        9907     9909       +2
  Branches      720      720
==========================================
+ Hits         7134     7135       +1
- Misses       2655     2656       +1
  Partials      118      118

Flag
Coverage Δ

metweb
65.35% <75.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...agement/form/EngagementFormTabs/EngagementForm.tsx
74.44% <75.00%> (-0.56%)
:arrow_down:

This works fine. For considerationhttps://www.draft-js-plugins.com/plugin/counter. I always like to check if they already did it before doing the work myself.


No port opening inside the container

Hi, I started the relay via Docker, and I can see the exposed port on <IP_ADDRESS> is 3335 (the guide mentions 3355, and I'm not sure if that's an issue). I've placed the container on the same network as Nginx, and when I inspect it, I can see the correct IP. However, from inside Nginx, the telnet connection doesn't close, and when I run an nmap scan, it doesn't detect any port listening. Additionally, from the outside, if I try a telnet to the server's public IP on port 3335, it doesn't close the connection.
[root@docker-1fc4d997890c:/app]# nmap <IP_ADDRESS>
Starting Nmap 7.93 ( https://nmap.org ) at 2024-09-25 07:30 UTC
Nmap scan report for haven-relay.nextcloud_network (<IP_ADDRESS>)
Host is up (0.0000080s latency).
All 1000 scanned ports on haven-relay.nextcloud_network (<IP_ADDRESS>) are in ignored states.
Not shown: 1000 closed tcp ports (reset)
MAC Address: 02:42:AC:12:00:03 (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 0.21 seconds
Thanks in advance

should be fixed now, please pull the latest and try


Added A Dashboard section and made a demo section according to it .

PULL REQUEST DESCRIPTION :
Added the 'Dashboard' section and then included the 'Demo' section within it. This section contains different tabs for various flow status, where each flow is assigned to its designated tab only. Mock data for this section is being generated using the "FlowRunMocks" function and then passed on to the different tabs .
Fixes: #1579

@AmanSal1 thanks for picking this up! Couple minor things to note

There's a component for this called FlowRunStateTypeTabs.vue.
I'd expect a separate demo for that component rather than adding to the DashboardTimeSpanFilter demo
Looks like there are some typescript errors

@pleek91 I have a doubt then the content of DashboardTimeSpanFilter demo would be similar to FlowRunStateTypeTabs.vue or it should contain something else ?

@AmanSal1 generally our demo sections are 1-1 with a component. So I'd only expect to see one component in each demo. So the time span demo should be reverted and a new demo section would be needed for the FlowRunStateTypeTabs. That demo would actually use that component and demo how it is used rather than copying the contents of it. Hopefully that makes sense! If not let me know and I'll try to clarify

Oh okay got some clarity but then what would be the demo section named for the FlowRunStateTypeTabs  ?

Oh okay . I have made the interface with the FlowRunStateTypeTab but I am unable to show the data in each tab according to their state . I think that we have to use the prop but I am not able to figure it out .

@pleek91 Can you review the logic bit stuck with adding the mock data in each tab according to their state.

@AmanSal1 the demo looks correct to me. Though its still not loading data the way I would expect. But I can sort that out later. You will need to remove the DashboardTimeSpanFilter.vue demo component that isn't used now though and fix the linting issues).
I'm not sure how adding this demo works with fixing https://github.com/PrefectHQ/prefect-ui-library/issues/1579 though as the actual component itself hasn't change any.

@pleek91
1.In the second commit, I tried writing the logic for it because just using the useflowrunmock was not showing the data as it should be, like separately in each tab.
2. I don't know why it's showing "DashboardTimeSpanFilter.vue" when I have renamed it. I will check it again.
3. So basically, there is some confusion regarding this issue #1579, which requires cloud access that I guess I don't have. Therefore, the PR I have raised is for adding the missing demo section in the Prefect UI library's current version.
4. Additionally, could you please provide the command for linting? That would be great

@pleek91 1.In the second commit, I tried writing the logic for it because just using the useflowrunmock was not showing the data as it should be, like separately in each tab. 2. I don't know why it's showing "DashboardTimeSpanFilter.vue" when I have renamed it. I will check it again. 3. So basically, there is some confusion regarding this issue #1579, which requires cloud access that I guess I don't have. Therefore, the PR I have raised is for adding the missing demo section in the Prefect UI library's current version. 4. Additionally, could you please provide the command for linting? That would be great

1-2. Understood
3. Adding the demo is great. We should just unlink this from that issue so it doesn't get closed when this gets merged.
4. npm run lint:fix. To see all the available commands check the package.json scripts section

So, should I create a new issue or what should be done according to you?

@pleek91 Or maybe I should remove the fixes keyword so it does closes the issue or I guess their is some feature of not closing the issue when a PR is merged but then in both the scenarios it would be difficult to keep a track of what has been added .
Its on your call whatever you recommend

@AmanSal1 I updated the description to remove the fixes keyword which unlinked the PR 👍

@AmanSal1 Done with the linting you can review now it  and I guess now you can see the FlowRunStateTypeTab component

@pleek91 Hey there! Whenever you find some free time, would you mind taking a moment to review it?

@znicholasbrown waiting for the approval from @pleek91

They're out of office for the next couple of weeks so you don't need to wait for their approval

@znicholasbrown Then  how will i merge this PR ?

Sorry @AmanSal1, I didn't realize the pending review was blocking your ability to merge - if it's alright with you I'll go ahead and merge on your behalf

@znicholasbrown So, will you be pressing the merge button, or will you be cloning these changes and then publishing them on your behalf??

I'll just press the button, the commits will still be yours!

@znicholasbrown oh that’s totally fine I thought i have to share my credentials to you 😅sorry

All good! I'll go ahead and merge this then

Yes go ahead !! Sorry for the misunderstanding though


proposal: Go 2: make int type panic on overflow

Proposal: change the type int to panic on overflow.
The type int does not have a defined size.  That means that people do not expect a particular overflow behavior.  It is also the default type of integer constants, and the result type of len, cap and copy, and the key type of range on a slice, array, or string, so it appears frequently in Go programs.
Catching integer overflow will catch many cases where a program behaves incorrectly.  Overflow in int values is unexpected but does sometimes occur.  When it does occur, it is normally a bug in the program.  Panicking rather than wrapping will help Go programmers find these bugs.
This idea arose in the consideration of adding checked integer types, which panic rather than wrap on overflow.  A problem with adding new checked integer types is that, as noted above, int is the implied type for several operations.  New types would require explicit conversions from int to the new type.  It's unlikely that people would use them, so code would not become safe.
This proposal does not preclude adding more checked integer types in the future, as suggested in #30209 and #30613.  It only addresses the handling of the special type int itself.
This would be a change in current program behavior, but since the type does not have a defined size, a program that relies on the wrapping behavior of int is likely to be subtly buggy when run on systems with different sizes of int.
This proposal is a simpler path forward compared to #19623, #19624, #30209, #30613.
A disadvantage of changing only int would be that people might assume that all integer types panic on overflow.  Unfortunately, changing the behavior of the other integer types seems much more likely to break existing programs.

Any refs to research on the frequency of int-overflow defects? Do they tend to occur with other bugs, e.g. infinite loop?
Any thoughts on performance impact of checking every change to every int?
Could one enable/disable this with a build flag?

What about the uint and uintptr types which also don't have a defined size? It would seem odd for the int type to panic on overflow but for the corresponding unsigned types to wrap.
A possible compromise between this and your other proposal (#30613) would be to leave int alone but introduce just one new type oint (or whatever one wants to call it) which panics on overflow. An explicit conversion from int would still be required but that might be a price worth paying in the minority of cases where one was worried about a 'silent' overflow occurring.

I do not have any stats on the frequency of integer wrapping errors.  Good question.  Not sure how to get those stats.
On x86 the performance impact is an extra instruction, a correctly predicted branch, after most arithmetic operations.  I doubt the performance impact would be significant, but we will have to see.
I do not think there should be a build flag for this, any more than there is for other language features.
The uint and uintptr types are both unsigned.  For unsigned types wrapping is generally considered less surprising.
The purpose of this proposal is to make most programs avoid overflow without requiring extra work.  Adding a new type would defeat that goal.  If people are worried about overflow, then they will write code that does not overflow, regardless of whether we add a new type or not.  The point is to help people who are not worried about overflow, but should be.

could we check this on compile time instead of panicking in runtime?
I mean something like this.
func add(i int) int {
    i += 1
    return i // overflow of an integer not checked error
}

func add(i int) int {
    i += 1
    if overflowed(i) {
        ...
    }
    return i // ok
}

@kybin There is a proposal along those lines at #30209.  This proposal is not that one.
Personally I not convinced that such a check needs to be built into the language.  I think it's rare that people want to check for overflow.  And for people who do want to check, it can be checked before the operation.  And of course, with this proposal, one could write
func CheckedAdd(a, b int) (sum int, ok bool) {
    defer func() {
        if recover() != nil {
            sum = 0
            ok = false
        }
    }()
    return a + b, true
}

although it would be more efficient to write an explicit check beforehand as one can already do today.

@ianlancetaylor I've missed it, sorry.
Another thought is, we can add -overflow flag to build command, so overflows are checked if the flag is on. (just like go build -race).
I support your proposal, which is panicking on integer overflow. It might be little better if we could check early when we want.

In Go we try to avoid adding knobs like a -overflow flag.  We try to make things work as best we can without requiring people to figure out what options to use.

I agree to you said. Thank you.

I vote against this functionality.
Motivation

other programming languages don't have it (some even requiring inline assembler to detect the overflow CPU flag being raised)
the performance impact is not neglectable.
functionality might not be easy to add consistently cross-platform

Although I do see the reason why this is asked.  The reasons why GOlang should not do it is the same as all the other languages earlier reached the same conclusion (not to support it).

coming from a C background, where int has always been undefined-on-overflow, and most users are still surprised by it: i think i like this idea, but find it slightly-surprising for it to apply to int, but not to int32 or int64. i'd be concerned about impact on existing code, but also i think it would indeed make code safer and mostly catch actual errors.

The type int does not have a defined size. That means that people do not expect a particular overflow behavior.

That is true in general, but note that it is possible today to detect the size of int and vary the behavior of the program accordingly. (For example, the math/big package does something similar with uint.) So I don't think we can assume that all uses of int today are agnostic to overflow behavior.
As much as I would like us to adopt this proposal, it certainly seems to run against the constraints described in https://github.com/golang/proposal/blob/master/design/28221-go2-transitions.md#language-redefinitions.

That is true in general, but note that it is possible today to detect the size of int and vary the behavior of the program accordingly.

Fair enough.  If there are plausible examples of programs that do this for int, not uint, then we can not adopt this proposal.
To expand, it is clear that this proposal changes the behavior of existing programs.  And clearly it will fix some programs, or, at least, avoid certain classes of incorrect behavior.  If we can convince ourselves that it will fix some real programs and not break any real programs, then perhaps we can proceed.  But I'm open to counter-arguments.

A counter-argument to this proposal is that it introduces a panic path to code that currently doesn't have one.  That raises the possibility of unexpectedly crashing a long-running server on an unlikely and untested path.  In some cases that can lead to a denial of service attack via a query of death.  That is, this proposal can change code that is silently incorrect into code that loudly crashes.  While that is often a good tradeoff, sometimes it is not.

That raises the possibility of unexpectedly crashing a long-running server on an unlikely and untested path.

The usual example of such paths is logging statements, which may very well be untested and unchecked in existing code:
	log.Printf("wrote %d things", nFoo + nBar)

https://github.com/golang/go/issues/30613#issuecomment-492711609 points out the similarity between dynamic overflow checks and race-detection.
So perhaps we could enable the overflow check for int only in -race mode, since race conditions are another case in which a subtle bug can unexpectedly crash a long-running server on an unlikely and untested path.

It's an interesting idea, but from a language perspective it means that integer overflow is no longer clearly specified.  That might be OK but it seems awkward.

Lots of answers here, all shared before.
How common is overflow? Find out for yourself in the Playground...
https://play.golang.org/p/xc8TdVBgmf
49.8047% (32640/65536) of additions overflow
96.9971% (63568/65536) of multiplications overflow
How central is this issue? It defines Niklaus Wirth's worldview on the matter, with much code in PASCAL and successors shaped by it. (The "math view" vs the "computer view)
https://groups.google.com/forum/#!searchin/golang-nuts/uint$20type$20safety$20in$20go/golang-nuts/zxwXc9EfvFU/T2ijCGyyAgAJ
Scroll down there to my post "Yes, there are cases for integer domain wraparound just as there are cases for exception at the limits."
Summary: (1) Silent wraparound is the right answer in general. (2) A special kind of variable that always checks (as an option in variable declaration or as a special checking-type) is a very good thing. (3) A way to test for exception is also a good thing.
#3 is always possible. So the question there is more about how much help to provide. I'd early on proposed:
sum,carry := a+b
difference,borrow := a-b
product,carry := a*b
quotient,remainder := a/b
which did not win favor, though it has come back around via the bits library and special function calls.

@MichaelTJones, when people are asking “How common is overflow?”, I suspect they mean “How often do variables overflow in Go programs in production?”, not “What fraction of the space of possible operands results in overflow?”.

The borrow / carry / remainder approach works great for multi-precision arithmetic, but that's not what most people are writing. For simple overflow checks, it seems more useful to have an operation or program behavior that applies to a whole expression tree, not just one individual operation.

If the question is “how often in apps” then it is too general to answer technically. It would seem the soft answer would be “never in cases that matter, because that would be considered a bug in program behavior.” The occurrence in unnoticed places, not seen or addressed as bugs, is clearly not “never” in a smart way but it is a kind of virtual never. On a pragmatic note, people use 64 bit signed ints these days as they loop from 1 to 10 and multiply by 365 days, say, so there is quite a bit of headroom to the 63  bit upper limit of 9,223,372,036,854,775,807.

I think there's probably a fair amount of intentional-overflow happening in code, but i'm not honestly sure how much. Obviously, much more in unsigned.
I suppose one strategy would be (1) implement it, (2) find out what happens.

Based on the objections mentioned above in
https://github.com/golang/go/issues/31500#issuecomment-491841837
https://github.com/golang/go/issues/31500#issuecomment-492011330
we are not going to adopt this proposal.


Add m2cgen for transpiling ML models into PHP code

Hey there! Thanks a lot for this list!
I'm not sure whether this contribution fits the project ideology 100% or not. m2cgen is not written in PHP but generates PHP code. It is a lightweight library with command line interface which allows to transpile trained machine learning models into a native code of PHP programming language. Examples of generated PHP code can be found here. Given the lack of any ML-related libraries in PHP (there is no separate ML section which is quite typical for such lists in other languages and only PHP-ML is present in misc section), I believe it's worth mentioning m2cgen project here. Please feel free to close this PR if you have an opposite opinion. Thanks a lot for your time and consideration!
https://github.com/BayesWitnesses/m2cgen

@alexkart Yes, I'm going to continue maintaining it after a some break.


Error when dynamically allocating number of tokens

I am receiving an error when dynamically allocating the number of tokens.
char *message = "{\"msg\":\"hello\",\"data\":\"world!\"}";
int len = strlen(message);
int max_tokens = jsmn_parse(&parser, message, len, NULL, 0); // returns 5
jsmntok_t *tokens = (jsmntok_t*)malloc(max_tokens * sizeof(tokens));
int num_tokens = jsmn_parse(&parser, message, len, tokens, max_tokens); // returns 0?!?!

This seems to be an issue with calling jsmn_parse twice on the same string. If I remove line 3 and replace max_tokens with 5 elsewhere, then it works.

On the first run the parser worked fine up to the very end of your input string. Thus, on the second run the same parser says it's all done. Try doing jsmn_init to reset the parser before the second run.

Ok, Thanks. So I just need to re-initialize before each parse.


WIP: component-specific metadata

Describe changes
I implemented/fixed _ to achieve _.
Design flaws:

type needs to be saved
pipeline run metadata is written multiple times
pipeline run metadata is not saved if step is cached

Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Closing in favor of #1151


Update to match new header: keep flat style

Current Header:

With changes to re-set the header background to transparent:

But doesn't it suck when you scroll down and back up again? There's a reason why it's no longer transparent.

I see what you mean. One potential option is to keep the header at the top of the page, instead of having it be a sticky header that floats on scroll-up. IMO, I've always found reappearing headers to be annoying, but would that be considered a significant break in functionality to disable here?
Otherwise, I could tweak the colors back to match again, but there's the problem of the header overhanging the clock, so the only other option I see is to shift the whole page down by a few pixels.


Build from source ros2 depend/use condition

example_interfaces is cloned but not build by packages-up-to.
https://github.com/kenji-miyake/action-ros-ci-test-condition/runs/3303440177?check_suite_focus=true


refactor: remove  func prefix

Summary by CodeRabbit

Refactor

Improved error handling in cross-chain transaction functions by replacing Must methods with safer Get methods.

Tests

Updated unit tests to align with the new method changes in cross-chain transaction handling.

mg


Default parameters to pydantic model

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need send default parameters to pydantic response_model
Describe the solution you'd like
I want to send for example default sex to model (don't extract data with ChatCompletion), because I know Jason's sex 😄 :
class UserDetail(BaseModel, sex):
    weight: int
    sex: str
    def is_obese(self):
        if self.sex=='female' and self.weight>100:
            return True
        if self.sex=='male' and self.weight>120:
            return True
        return False

user: UserDetail = openai.ChatCompletion.create(
    model="gpt-3.5-turbo",
    response_model=UserDetail,
    parameters={'sex': 'male'}
    messages=[
        {"role": "user", "content": "Extract Jason 200kg"},
    ]
)

Describe alternatives you've considered
I'd considered create another pydantic class to complete properties for user. But it is not correct way, because UserDetail should have all user properties, some extracted from ChatCompletion and others send for me.
Maybe, I have lost something. I'm not expert using pydantic. If you can share me another option I would be grateful.

i suggest taking a look at validation_context in the docs, might be good place to start


[MAS4.2.12] [Screen reader -Setting] After selecting “Save button” Narrator is not narrating the notification message information

Actual Result:
After selecting “Save button” Narrator is not narrating the notification message information and focus is moving to the Locale text field
Expected Result:
Screen Reader should narrate the notification message after selecting the “Save button ” and focus should moves to the path to ngrok text field.
Example: After selecting “Save button” narrator should narrate as File has been saved or file has been uploaded
Note: Issue is repro’ing with NVDA. Please refer the attchement <MAS4.2.12_Setting_NVDA.wmv>
Same issue observed in Mac Os.
Repro Steps:
Turn on the narrator
1.Open the Bot Framework V4 Emulator.
2.Navigate to Welcome tab screen and select it, screen gets opened
3.Navigate to the open bot and select it
4.Open bot dialog gets opened and connect to the open bot
5.Live chat screen gets appears
6.Navigate to the Edit ngrok settings and select it
7.Emulator screen gets opened
8.Navigate to the “Save button” and select it
9. Observe the issue
User Impact:
Users who rely on screen readers will affect to navigate if Screen reader is not narrating the change notification message when we are selecting the save button
Test Environment:
OS Build: Version 1903(OS Build 18362.239)
Browser: Edge
Application: Bot Framework V4 Emulator
Screen reader: Narrator
OS: MacOs Version 10.15
Application: Bot Framework V4 Emulator (Version 4.5.2-80829)
MAS Reference Link:
Sharepoint Link
MAS4.2.12_Setting.zip
MAS4.2.12_Setting_NVDA.zip

Verified in latest bot emulator version-4.5.2-82590 with NVDA(2019.2) Issue got fixed Hence we are closing this bug.


Non-uniform scaling in camera transform seems to mess things up

If you add a different scale to x and y in the camera transform, it seems to completely mess things up. Wonder if that might be an easy fix?

For zooming, I think it's these lines that just straight ignore pos.scale:
https://github.com/johanhelsing/bevy_pancam/blob/cfaa0b26b22e82d4dd3a9207537e063b0c86198d/src/lib.rs#L131-L135

And for movement, it's this line that ignores transform.scale:
https://github.com/johanhelsing/bevy_pancam/blob/cfaa0b26b22e82d4dd3a9207537e063b0c86198d/src/lib.rs#L210

Why are you scaling the camera? Not saying we shouldn't try to fix it, just curious.

Maybe I'm missing something or doing it wrong (I'm a bit of a newb in bevy overall), but I need an option to scale x-y separately, e.g. for a time series plot you could zoom in just on time. Not sure if there's a better way to do it than scaling the camera (which works perfectly fine, with a few fixes in pancam).

Okay :) If it's an easy fix, a pr would be very welcome!


delete dataset

An option could be to remove the delete from the left control and instead provide a delete button from to top bar which could bring the list of dataset with a quick select all with two action buttons Cancel and Delete selected.
@floryst @aylward

On that same topic, we could envision similar top button add-on such as a girder browser which could provide a "gallery" type of view for datasets to load using the CinemaTumbnail for enabling data preview before selecting them for load.

Having a central button that then list items breaks the item-centric
paradigm that is currently driving the PVG interface.  I'd like to keep
having properties and actions being tied to items rather than actions then
needing to specify which items they apply to.
I think the triple-dot menu that calls up delete is fine for now.   Let's
learn more about common workflows as people use PVG and then we can
determine if more actions are needed under the triple dot, how to better
delineate how properties are grouped under items, and such.
On Fri, Jun 22, 2018 at 7:39 PM Sebastien Jourdain<EMAIL_ADDRESS>wrote:

On that same topic, we could envision similar top button add-on such as a
girder browser which could provide a "gallery" type of view for datasets to
load using the CinemaTumbnail for enabling data preview before selecting
them for load.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/paraview-glance/issues/97#issuecomment-399610463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAREr25SZna7Utn8xtE6YugkA_lPbsK9ks5t_YAxgaJpZM4U0i1C
.

--
Stephen R. Aylward, Ph.D.
Senior Director of Strategic Initiatives, Kitware, Inc., North Carolina
http://www.kitware.com and http://www.aylward.org
(919) 969-6990 x300


support context in Dependency

What kind of change does this PR introduce?
refactoring/bugfix
fixes #15580

Did you add tests for your changes?
updated existing
Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?
nothing

Thanks


Add MS SQL Server tests

Added tests for Microsoft SQL Server, per Issue #54.
I based it off the existing tests but was unable to run the test suite via rake due a protocol error unrelated to what I added (tried it without my modification).  This was the first time I've written or run spec tests so I think it is related to my setup, not necessarily the tests.
Also my apologies, I wasn't sure how to connect this to the existing issue.

Thanks for this! The first test is always the hardest :)


Cannot verify GPG key signature generated from Windows

Description

[!IMPORTANT]
When I used Git Bash to generate the GPG key, it worked.

To reproduce:

Using gpg  (downloaded form https://gnupg.org/download/) on windows to generate ECC or RSA GPG key (run gpg --full-generate-key).
Export the generated GPG public key and add it into the self-host Gitea user account.
Then click Verify button, run echo "<token-generated-by-gitea>" | gpg -a --default-key <key-id> --detach-sig
Got an error said The provided GPG key, signature and token do not match or token is out-of-date.

GPG version
gpg (GnuPG) 2.4.4
libgcrypt 1.10.3
Copyright (C) 2024 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.25.1
Operating System
Ubuntu 20.04.3
How are you running Gitea?
Through Docker
Database
SQLite

I tried this, and it worked.
One thing is different. In step 3, it is a bash command, how did you execute it in Windows?
I adjust it to:
./gpg.exe -a --default-key <key-id>--detach-sig <file-which-contains-token-generated-by-gitea>

Then it will generate a *.asc file in the same folder, then copy the content, and verify.
ps: once it failed, it seems that the token generated by gitea will be changed, you should update it.
ps: I can only download 2.4.5 now, there should (maybe) have no big differences I think.

We close issues that need feedback from the author if there were no new comments for a month. :tea:


Revert Cargo Book changes for default edition

On #8543 it was introduced a change on the Cargo Book docs
where it was incorrectly stated that the default edition for
the Cargo Manifest was 2018 when indeed, as @ehuss correctly stated
in https://github.com/rust-lang/cargo/pull/8543#issuecomment-663769077
it is not.
Therefore, as @Eh2406 asked for, I made the PR reverting this changes
and leaving the Cargo Book docs as they were before.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

This was already discussed with @Eh2406 so maybe I should just override the reviewer and set him.
r? @Eh2406

Thanks for the fix! And sorry for not reading carefully enough last time.
@bors r+

:pushpin: Commit 129e168cda347e96571e311825a430d3b0903c63 has been approved by Eh2406

:hourglass: Testing commit 129e168cda347e96571e311825a430d3b0903c63 with merge 272cfc0eaf1d0e3235a5ebb213adb89e9014aa81...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing 272cfc0eaf1d0e3235a5ebb213adb89e9014aa81 to master...


Not able to Persist (or convert ) phone number to fhir

MSH|^~&|Company|Company Facility|UI Application|Company UI Application|20230209131733||ADT^A04|123420230209131733|P|2.3
EVN|A04|20230209131733
PID|||||Raj^Jetly|||M|||House Name^Chavara<EMAIL_ADDRESS>This is the sample hl7message when i converted to fhir, it doesn't contain the PID13.7 detail which is the phone number.

Hmmm....looking at the template it is built on the expectation that email address and phone number are different entries in the repeating PID.13 field.
So pulling the PID.13 field apart into two repetitions one for email address and another for the phone number should give you what you're looking for.
MSH|^~&|Company|Company Facility|UI Application|Company UI Application|20230209131733||ADT^A04|123420230209131733|P|2.3
EVN|A04|20230209131733
PID|||||Raj^Jetly|||M|||House Name^Chavara<EMAIL_ADDRESS>
If you are unable to pre-process your HL7 input message to (correctly) put the email address and phone number into separate repetitions - then you are stuck with having to customize:

resource/Patient.yml will need to be adjusted to make it generate two telecom fields from the single PID.13 entry

You will probably have to heavily customize datatype/ContactPoint.yml to get your desired output.


handlers are not overriding the response

I've setup storybook mirage, seeing it show up in the Panel, and log the API response. Changing the timing parameter in the story updates the timing for the miragejs response, so it is clearly hooked up, and some parts are working, but it seems that the handler is not overriding the API response defined in the createMockServer function.
.storybook/main.js
module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(ts|tsx)'],
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/preset-create-react-app',
    'storybook-mirage',
  ],
}

.storybook/preview.js
export const decorators = [
  (Story) => (
    <HelmetProvider>
      <ChakraProvider theme={theme}>
        <QueryClientProvider client={queryClient}>
          <Story />
        </QueryClientProvider>
      </ChakraProvider>
    </HelmetProvider>
  ),
  StoryRouter(),
  withServer(createMockServer),
];

Terms.stories.tsx
export default {
  title: 'Design Language/Routes/Terms',
  component: Terms,
  parameters: {
    mirage: {
      logging: true,
      handler: {
        post: {
          'http://localhost/v1/user/signup': { termsAcceptance: false },
        },
      },
    },
  },
} as Meta;

Any thoughts @HipsterBrown ? :)

@nimo-juice Finally got some time to explore these issues. Thank you for your patience.
I recreated the situation locally and my best guess would be related to using http://localhost/v1/user/signup as the route path for the handler. Usually this is an absolute path name instead of a full URL:
export default {
  title: 'Design Language/Routes/Terms',
  component: Terms,
  parameters: {
    mirage: {
      logging: true,
      handler: {
        post: {
          '/v1/user/signup': { termsAcceptance: false },
        },
      },
    },
  },
} as Meta;

I know it's been a while, but I hope this helps solve the issue.

It might help our team haha.
I{ll check it up.


secret_key_base not set

I keep seeing this warning in production.log: DEPRECATION WARNING: You didn't set config.secret_key_base
With a bit of searching, I found the following info:

In Rails 4.0, encrypted cookies is introduced (more secure comparing to signed cookies in Rails 3)
In Rails 4.1, secrets.yml convention is introduced
In Redmine 3.2.0 Installation Guide, bundle exec rake generate_secret_token is used for generating secret token, which indeed creates config/initializers/secret_token.rb that configures secret_key_base

So for minimal change, we could probably add a new parameter REDMINE_SECRET_KEY_BASE that is written to config/configuration.yml as Rails is reading from both config and secrets.
Or writes both REDMINE_SECRET_KEY_BASE and REDMINE_SECRET_TOKEN into config/secrets.yml if new convention is preferred.

While i see the issue you reported, the value of secret_token (i.e. REDMINE_SECRET_TOKEN) in config/configuration.yml I believe is supposed to be set by redmine for config.secret_key_base.
I think only one of these values is required. If that is the case, then we can only correct the configuration without adding any new parameters.

I believe only secret_key_base is required. The secret_token is left for compatibility and smooth transition of Rails 3 to 4 according to their upgrade guide:

Please note that you should wait to set secret_key_base until you have 100% of your userbase on Rails 4.x and are reasonably sure you will not need to rollback to Rails 3.x. This is because cookies signed based on the new secret_key_base in Rails 4.x are not backwards compatible with Rails 3.x.

same for me...
there is a 500 error if not configured config.secret_key_base
# this work for me
docker exec redmine sed -i "s#:log#:log\n  config.secret_key_base = 'tetx'#" /home/redmine/redmine/config/environments/production.rb
docker exec redmine cat /home/redmine/redmine/config/environments/production.rb

same for me...
there is a 500 error if not configured config.secret_key_base
# this works for me
docker exec redmine sed -i "s#:log#:log\n  config.secret_key_base = 'tetx'#" /home/redmine/redmine/config/environments/production.rb
docker exec redmine cat /home/redmine/redmine/config/environments/production.rb

same for me...
there is a 500 error if not configured config.secret_key_base
# this works for me
docker exec redmine sed -i "s#:log#:log\n  config.secret_key_base = 'xxx'#" /home/redmine/redmine/config/environments/production.rb
docker exec redmine cat /home/redmine/redmine/config/environments/production.rb


chore(docs): update the docs

update the datepicker and datepicker popup docs to let user know
about using the uibDateParser service to convert a date string
into a Date object.

LGTM

Crap.  Need to drop the $ bit.  There's no scoping on a service.

And the eye icon....


WeaveDB filters on Application Containers

Version: (VERSION 0869d26e)
Product: Net and Scope
Orchestrator: AWS - ECS
The WeaveDB is filtering on application containers and it should be in system containers.

This was a problem in weave net. It's fixed there so the issue will go away with the next release.


Part 1. Introduction About the course

Part 1. Introduction - prepare issues #109
About the course, information versus data, algorithm versus program, type - what does it mean
Scope

[x] review existing code
[x] add a placeholder to the project
[x] add code example  - consider merging with type compatibility
[ ] Roman numerals to integers
[x] add unit tests

Refered in: ad6fe7004bf776204028883a45e48ed36a325890


[8.x] Normalize Style

See: https://github.com/laravel/laravel/blob/master/phpunit.xml#L21

This doesn't really matter, and will only cause us merge conflicts.


multiple profiles not working

From @friendica on June 30, 2013 7:10
We had envisioned a different approach to multiple profiles in Red than in Friendica - whereby profiles would more closely correspond to privacy groups. We also need to refer to these internally by hashes instead of a simple id so that they are system independent and not require translation across identity instances.
The aligning with privacy groups (collections) poses a bit of a problem because channels can belong to multiple privacy groups. They should be directed to one profile - probably from a choice of those groups they belong to, the choice being made on the connection edit page.
It is also not clear how these profiles initially get populated and with what data, if they are created when a privacy group is created.
The problems with this approach may be worse than the old method - where any channel could be assigned to any profile and profiles created at any time for any purpose. Would consider bringing back the old behaviour as a temporary solution; as long as it uses hash identifiers instead of simple numeric ids.
Copied from original issue: friendica/red#66

From @friendica on August 1, 2013 5:46
We're doing it the old way - and it is implemented. Aligning with collections would cause too many issues.


build failure, NDK 14 - 15, Windows 10

In file included from ../../../../../../../src/third-parties/ziplib/Source/ZipLib/methods/../compression/store/store_encoder.h:6:0,
                   from ../../../../../../../src/third-parties/ziplib/Source/ZipLib/methods/ICompressionMethod.h:4,
                   from ../../../../../../../src/third-parties/ziplib/Source/ZipLib/ZipArchiveEntry.h:5,
                   from ../../../../../../../src/third-parties/ziplib/Source/ZipLib/ZipArchive.h:4,
                   from ../../../../../../../src/third-parties/ziplib/Source/ZipLib/ZipFile.h:2,
                   from C:\Users\Daniel\GitHub\SDKLauncher-Android\readium-lcp-client\src\lcp-client-lib\LcpService.cpp:52:
  ../../../../../../../src/third-parties/ziplib/Source/ZipLib/methods/../compression/store/../../streams/crc32stream.h:3:41: fatal error: streambuffs/crc32_streambuf.h: No such file or directory
   #include "streambuffs/crc32_streambuf.h"
                                           ^

r15c (latest, still with GCC compat)

Note that this occurs when invoking gradlew build from the command line. My local.properties:
sdk.dir=C\:\\Users\\Daniel\\AppData\\Local\\Android\\android-sdk
ndk.dir=C\:\\Users\\Daniel\\AppData\\Local\\Android\\android-sdk\\ndk-bundle

readium.ndk_experimental=true
readium.ndk_clang=false
readium.ndk_skipX86=true
readium.ndk_skipARM=false
readium.sdk_lib_dir=../../../readium-sdk/Platform/Android/epub3/build/outputs/native/debug/arm/lib/armeabi-v7a/lib
readium.sdk_include_dir=../../../readium-sdk/Platform/Android/epub3/include/

This same compiler error also occurs when compiling from Android Studio Error:fatal error: streambuffs/crc32_streambuf.h: No such file or directory
(disabled readium.sdk_lib_dir and readium.sdk_include_dir vars in local.properties, and manual copy of readium-sdk/Platform/Android/epub3/build/outputs/native/debug/arm/lib/armeabi-v7a/*.so into readium-sdk/Platform/Android/epub3/libs/*.so so that the Gradle build script can find the prebuilt ReadiumSDK shared libraries)

I'm on Windows 10 by the way.
NDK r15c is installed by Android Studio in PATH/TO/android-sdk/ndk-bundle/.
https://developer.android.com/ndk/downloads/index.html
I am going to "downgrade" to r14b and see what happens...
https://developer.android.com/ndk/downloads/older_releases.html
What a waste of time :(

CC @clebeaupin @llemeurfr

May be related to: https://github.com/readium/SDKLauncher-Android/issues/125
?

Same error with NDK 14 !
Side note:
Strangely, the ReadiumSDK libs are now in readium-sdk\Platform\Android\lib\build\intermediates\binaries\debug\arm\lib\armeabi-v7a instead of readium-sdk/Platform/Android/epub3/build/outputs/native/debug/arm/lib/armeabi-v7a/ (not sure why)

Ok, so next step: try to build on OSX (last time I tried it worked).

I checked on OSX, works just fine. I made sure to use the exact same SDK platform versions (all the way down to CMake, LLDB etc.)
So, this seems to be a Windows-specific problem ... which is a bummer, as my Windows 10 laptop is quicker than my Mac, so I would prefer to use it for Android development :(

Fixed via: https://github.com/readium/readium-lcp-client/commit/b9d525a6d13a3c26be9c6db2110e27dfefd59d2b

Okay, after quite a bit of debugging, trial and experimentations...the code compiles in Windows when the templated C++ classes are moved:
https://github.com/readium/readium-lcp-client/tree/develop/src/third-parties/ziplib/Source/ZipLib/streams/streambuffs
Bizarre compiler error! (obscure console messages too)
Testing now...

Fixed via: https://github.com/readium/readium-lcp-client/commit/6ae365f9a3d7eca748eed0ba954b2257e377f0f9


WIP: sddm, kde, plasma-5: Adding some build dependencies.

Some more dependencies added/fixed.

I'm preparing a better more finegrained PR.. closing this.


ARM64 integration testing in backup-restore-operator

Most of backup-restore was migrated to GHA with integration testing in this PR
https://github.com/rancher/backup-restore-operator/pull/455
But testing for ARM64 support was not included. This ticket will fix that.

We had a quick call on this and I want to summarize some things we found for future reference. Long story short, GHA added arm runners but only to orgs (so unlikely we can test on our forks).
The arm based runners are accessible via Rancher repos via their runs-on names, and examples listing the names can be found here: https://github.com/rancher/eio-test/actions/runs/8795155580/workflow

WIP PR here: https://github.com/rancher/backup-restore-operator/pull/555

@mallardduck @MKlimuszka should we keep this open or close it since https://github.com/rancher/backup-restore-operator/pull/555 is merged? Maybe we want to keep it around for backport purpose?

My vote would be keep it open until backports are sorted out. Once we merge in https://github.com/rancher/backup-restore-operator/pull/566 manual backport PRs can be created for our other active branches (Rancher 2.8+ / BRO 4/5).

Backport PRs are in review now:
https://github.com/rancher/backup-restore-operator/pull/569
https://github.com/rancher/backup-restore-operator/pull/570
https://github.com/rancher/backup-restore-operator/pull/571

All merged up! Setting this solved


Improved The UI

Hi @apu52
I have Improved The Design Of Rate Us  Page

Changed the Background color of container
Added hover color on nav links
Removed extra rate us link from the navbar as it was not needed there
Added padding to the Email container
added Hover effect on inputs

Please Allow Me To Contribute To Your Project
add Hactoberfest accepted label to this PR
Thankyou @apu52

@Lakshyaraj-Singh what is your assigned issue no??

@Lakshyaraj-Singh what is your assigned issue no??

Sorry but I don't know about assigned no. As I am new to open source. I directly sent the PR

@Lakshyaraj-Singh okk Actually as per the rules of this repo
U at first have to raise a proper issue , then after only get assigned , u can start working on this issue & can submit your PR
Please go through the Contributing.md file for more details rules of this repo.
As this PR violates the rules . Sorry but I have to close this pr for now .
But u can still make issues by following the rules


PDS APIs for GA.

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.

Link to engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[x] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

Design Document:
Previous Open API Doc:
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Here's a diff of the swagger from the previous preview:
 {
   definitions: {
     AccountModelBase: {
-      description: "Represents a purview account."
+      description: "Details of the purview account governing the requested resource."
       properties: {
         gatewayEndpoint: {
-          description: "Purview account gateway endpoint."
+          description: "Endpoint of the Purview account. This will be used by the RPs to call Purview APIs."
         }
         id: {
-          description: "Id of the purview account."
+          description: "ID of the Purview account."
         }
         location: {
-          description: "Region where purview account is created."
+          description: "Location (Region) of the Purview account."
         }
         name: {
-          description: "Name of the purview account."
+          description: "Name of the Purview account."
         }
         tenantId: {
-          description: "Tenant id of the purview account."
+          description: "Tenant ID of the Purview account."
         }
       }
     }
     Consent: {
-      description: "Consent information related to a resource."
+      description: "Consent information for the resource governed by purview."
       properties: {
         excludedScopes: {
-          description: "Child scopes that need to be excluded (optional)."
+          description: "List of scopes opted out of this consent."
         }
       }
     }
     DatasourcePreferencesResponse: {
-      description: "Provides the consent information for a data source."
+      description: "Response model for datasource preference API."
       properties: {
         frequency: {
-          description: "This represents the frequency at which the RPs will check for consent information."
+          description: "This is the timespan at which the RPs call this API at regular intervals."
         }
       }
     }
     ErrorModel: {
-      description: "Represents the error model."
+      description: "Default error model."
       properties: {
         code: {
-          description: "Service error code."
+          description: "Error code."
+          minLength: 1
         }
         details: {
-          description: "Granular errors (if any)."
+          description: "Error details."
         }
         message: {
+          minLength: 1
         }
         target: {
-          description: "Detailed error message."
+          description: "Error description."
         }
       }
     }
     ErrorResponseModel: {
-      description: "Represents the error response model."
+      description: "Default error response model."
     }
     PolicyElement: {
-      description: "Represents a policy element."
+      description: "Represents a policy, policy set or attribute rule."
       properties: {
         id: {
-          description: "Id of the policy element."
+          description: "ID of the policy element."
+          minLength: 1
         }
         kind: {
+          minLength: 1
         }
         updatedAt: {
+          minLength: 1
         }
       }
+      required: [
+        "id"
+        "kind"
+        "updatedAt"
+        "version"
+      ]
     }
     PolicyElementEventModel: {
-      description: "Represents a policy element event model."
+      description: "Represents the policy element event model."
       properties: {
         eventType: {
+          minLength: 1
         }
         id: {
-          description: "Id of the policy element."
+          description: "ID of the policy element."
+          minLength: 1
         }
         kind: {
+          minLength: 1
         }
         updatedAt: {
+          minLength: 1
         }
       }
+      required: [
+        "eventType"
+        "id"
+        "kind"
+        "updatedAt"
+        "version"
+      ]
     }
+    PolicyEventsResponseUpdated: {
+      description: "Response model for policy delta fetch API."
+      properties: {
+        syncToken: {
+          description: "This sync token represents the latest checkpoint for policies. Client need to pass this value while fetching subsequent delta changes."
+          minLength: 1
+          type: "string"
+        }
+        value: {
+          description: "List of policy elements."
+          items: {
+            $ref: "#/definitions/PolicyElementEventModel"
+          }
+          type: "array"
+        }
+      }
+      required: [
+        "syncToken"
+      ]
+      type: "object"
+    }
-    PolicyEventsResponse: {
-      description: "Represents the response for policy events API."
-      properties: {
-        count: {
-          description: "Count of elements in payload."
-          format: "int32"
-          type: "integer"
-        }
-        elements: {
-          description: "List of created/updated policy elements."
-          items: {
-            $ref: "#/definitions/PolicyElementEventModel"
-          }
-          type: "array"
-        }
-        syncToken: {
-          description: "Sync token represents the checkpoint upto which this policy elements list is updated. Client need to store this value and keep updating if PDS returns a new value. Call this API with the most recent value received."
-          type: "string"
-        }
-      }
-      type: "object"
-    }
+    PolicyResponseUpdated: {
+      description: "Response model for policy bulk fetch API."
+      properties: {
+        nextLink: {
+          description: "Link to fetch next set of policy elements."
+          type: "string"
+        }
+        syncToken: {
+          description: "This sync token represents the latest checkpoint for policies. Client need to pass this value while fetching subsequent delta changes using policy-events API."
+          type: "string"
+        }
+        value: {
+          description: "List of policy elements."
+          items: {
+            $ref: "#/definitions/PolicyElement"
+          }
+          type: "array"
+        }
+      }
+      type: "object"
+    }
-    PolicyResponse: {
-      description: "Represents the response for policy fetch API."
-      properties: {
-        count: {
-          description: "Count of elements in payload."
-          format: "int32"
-          type: "integer"
-        }
-        elements: {
-          description: "List of policy elements."
-          items: {
-            $ref: "#/definitions/PolicyElement"
-          }
-          type: "array"
-        }
-        nextLink: {
-          description: "Link with skip token to fetch next set of records. This is used in case of pagination."
-          type: "string"
-        }
-        syncToken: {
-          description: "Sync token represents the checkpoint upto which this policy elements list is updated. Client need to pass this value while fetching records using policyEvents API."
-          type: "string"
-        }
-      }
-      type: "object"
-    }
     Properties: {
-      description: "Consent properties."
+      description: "Consent details."
       properties: {
         dataUseGovernance: {
-          description: "Consent for data use governance."
+          description: "This value indicates whether the resource is enabled for data use governance."
         }
       }
     }
     Scanner: {
-      description: "Represents the collection of consent information for scanning service."
+      description: "Consent information for scanner service."
       properties: {
         classification: {
-          description: "Consent for classification discovery."
+          description: "This value indicates whether the resource is enabled for classification discovery."
         }
         metadata: {
-          description: "Consent for metadata discovery."
+          description: "This value indicates whether the resource is enabled for metadata discovery."
         }
       }
     }
   }
   info: {
-    version: "2022-11-01-preview"
+    version: "2023-01-01"
   }
   paths: {
     /datasource-preferences: {
       get: {
-        description: "Get Datasource Preferences for a given scope."
+        description: "Get Datasource Preferences for given scope."
         parameters: [
           {
-            description: "Scope."
+            description: "Id for any resource managed by Purview."
           }
-          {
-            description: "Is call from a Gondor client."
-            in: "query"
-            name: "isProjectGondor"
-            type: "boolean"
-          }
           ...
         ]
         responses: {
           default: {
-            description: "An unexpected error occurred"
+            description: "Error"
           }
         }
       }
     }
     /policy-elements: {
       get: {
         parameters: [
           {
-            description: "Scope."
+            description: "Id for any resource managed by Purview."
           }
           {
-            description: "The API Version."
+            description: "The PDS API Version."
           }
           {
-            description: "Optional value to filter policies based on hierarchy of resources. It is of type enum with possible values: AtScope, ChildrenScope, None, All"
+            description: "Filter supporting full OData syntax."
           }
         ]
         responses: {
           200: {
             schema: {
-              $ref: "#/definitions/PolicyResponse"
+              $ref: "#/definitions/PolicyResponseUpdated"
             }
           }
           default: {
-            description: "An unexpected error occurred"
+            description: "Error"
           }
         }
         x-ms-pageable: {
-          itemName: "elements"
         }
       }
     }
     /policy-events: {
       get: {
         parameters: [
           {
-            description: "Scope."
+            description: "Id for any resource managed by Purview."
           }
           {
-            description: "The sync token."
+            description: "This sync token represents the latest checkpoint for policies. Client need to pass this value while fetching subsequent delta changes."
           }
           ...
         ]
         responses: {
           200: {
             schema: {
-              $ref: "#/definitions/PolicyEventsResponse"
+              $ref: "#/definitions/PolicyEventsResponseUpdated"
             }
           }
           default: {
-            description: "An unexpected error occurred"
+            description: "Error"
           }
         }
       }
     }
   }
 }

Based on this, I see no reason not to sign off except that this PR targets main (BTW: always a good idea to create a separate topic branch since I see you changed main in your fork). Is this API ready? Going into main effectively means "done". See our walkthrough.

For consistency, we prefer Id instead of ID - perhaps this change can be made without breaking (at least in documentation).

For consistency, we prefer Id instead of ID - perhaps this change can be made without breaking (at least in documentation).

Hi @heaths, @JeffreyRichter,
I have fixed the case for ID - changed it to Id at all places.
As far as branch is concerned, I am putting all changes in main as of now as I am the only person working on this. Also I will delete this repo once this branch is merged.
Please let me know if this is fine.

Hi @heaths,
As far as branch is concerned, I am putting all changes in main as of now as I am the only person working on this. Also, I will delete this repo once this branch is merged.
Please let me know if this is fine.

@pansharm-ms hat almost answers my question. Since you're the only one working on this, is the idea that you're done once this PR is merged? A feature branch is still a recommendation if your changes for a new version are not "one and done". Once a spec is in main, it's meant to be immutable (there's some exceptions like for correctness, but should be rare).


Floating UI doesn't use the latest version of the callbacks from each render

Every render, useFloating is called with a new options object that probably contains a bunch of callbacks (sometimes nested inside middlewares and the like).
Floating UI seems to be ignoring every render except the first one, and using old versions of the callbacks, which can reference state values from old renders that are no longer up to date.
To Reproduce

I tried to create a codesandbox, but it says the file's read only, all the share options are disabled and I can't figure out how to actually share a repro. :/
Steps to reproduce the behavior:

Make a state with useState
Use the state value inside a callback function
Update the state
Floating UI keeps using the old value

Expected behavior Floating UI should probably replace all the callbacks with wrappers that can always call the version from the latest render.
Context:

Version: 0.26.14

Additional context
this hook helps me to avoid this issue and successfully works around the problem:
import { useCallback, useRef } from 'react'

// eslint-disable-next-line @typescript-eslint/no-explicit-any
export default function useCallbackWrapper<F extends (...args: any) => any>(func: F): F {
	const latest = useRef<F>(func)
	latest.current = func; // eslint-disable-next-line react-hooks/exhaustive-deps
	return useCallback(((...args) => latest.current(...args)) as F, [])
}

maybe you can use something like it

Is the issue the same on 0.26.13?

yes it looks like it. my render function logs the values of these variables, THEN the callbacks are called and they print the old values, so it seems floating UI is keeping around a reference to an old callback from an old render instead of using the most recent ones

Okay, .14 had a somewhat major refactor that I was curious was causing the problem. But if it's happening in the old version I'm skeptical it's this library's issue. useEffectEvent (the function you posted) is used internally where necessary, and the lint rules are enabled to ensure useCallbacks have fresh values during rendering.
Without a reproduction it's hard to debug - if you can, try to find some time to make a new CodeSandbox that reproduces the issue!

I have time, it's just all of codesandbox's buttons are disabled for some reason?

like, it literally just won't let me

CodeSandbox's recent changes have been weird, try to create a brand new Sandbox entirely

how?

oh, it wants me to sign in, let me try that

here you go
to reproduce:

click the "add 10" button
the tooltip does nothing
click remount
woah

So this is an edge case where state values aren't fresh inside functions of middleware. Refs can be fresh, but they're also not reactive.
To keep using state, which is both reactive and fresh, you need to inform Floating UI about the value changing:
const sizeMiddleware = size({
  apply({ elements }) {
    elements.floating.style.height = `${state}px`;
  },
});

const reactiveSize = {
  ...sizeMiddleware,
  options: {
    ...sizeMiddleware.options,
    deps: [state],
  }
};

useFloating({
  middleware: [reactiveSize]
})

https://codesandbox.io/p/sandbox/floating-ui-react-dom-template-forked-vmtmz4?file=%2Fsrc%2FApp.js%3A22%2C1
Docs: https://floating-ui.com/docs/useFloating#option-reactivity

ok, thank you! that looks exactly like what I am running into

yep I can confirm even just
 			size({
 				apply({availableHeight, elements}) {
 					console.log('extraLeftPadding = %o, extraRightPadding = %o', extraLeftPadding, extraRightPadding)
 					elements.floating.style.width = `${elements.reference.getBoundingClientRect().width - leftPadding - rightPadding + 2 * unit}px`
 					elements.floating.style.maxHeight = `${Math.max(availableHeight, 20 * unit)}px` // 4 items
 				},
+				deps: [extraLeftPadding, extraRightPadding, unit]
 			}),

immediately fixes the issue
wonder if you should make this deps an official optional field so that typescript stops complaining at me
it'd probably be SUPER helpful for discoverability as well

I was considering adding it as a second argument (like a dependency array), but the types were a bit annoying and I didn't think it was a major enough issue to add in, but I might try to look into it again

Docs need to be updated. The current docs say:

Specifying the dependencies as a second argument of any middleware function will keep it reactive:
offset(() => value, [value]);
This goes for any function option, including size()’s apply function.

...but that doesn't work. I had to find this issue to discover I actually need to pass dependencies for size like this:
const middleware = [
  size({
    apply() { ... },
    deps: [dep1, dep2]
  })
]

Docs need to be updated. The current docs say:

Specifying the dependencies as a second argument of any middleware function will keep it reactive:
offset(() => value, [value]);
This goes for any function option, including size()’s apply function.

...but that doesn't work. I had to find this issue to discover I actually need to pass dependencies for size like this:
const middleware = [
  size({
    apply() { ... },
    deps: [dep1, dep2]
  })
]

Just to be clear, you tried this and it didn't work?
const middleware = [
  size({
    apply() { ... }
  }, [dep1, dep2])
]


Add GitHub ribbon to header.html

JerryScript-DCO-1.0-Signed-off-by: Levente Orban<EMAIL_ADDRESS>

LGTM (informally)

(Do not land it early, please give some time to people to check it).

Check the results in https://polaroi8d.github.io/jerryscript/


Update sketch-toolbox to 0.5.1

After making all changes to the cask:

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

Thank you for the contribution. It was merged directly as cb115a73a9cc26bfdb116e0b554d506e053a6463. Your contribution is still credited to you.


Proxy authentication not supported

This is not working on Windows 10:
proxy = "http://domain\\user:pass@<IP_ADDRESS>:8080"

Is the user name actually domain\user?
Are you talking to a SOCK5 proxy?

It is a Microsoft proxy, so domain\user is the required syntax.
It is an HTTP/HTTPS proxy, not SOCKS5.
Anyway the error is something like "Cannot parse proxy string".
HTTPS proxy support (otherwise known as http "tunneling" and it uses the CONNECT command) would be very useful.

The proxy feature is only for SOCKS proxies.
HTTP proxies are not supported. It wouldn't work in most cases. The DNSCrypt protocol doesn't use HTTP, and DoH requires HTTP/2 and a certificate chain that can be verified.

HTTP proxies also support the CONNECT method, which would work for DSNCrypt using TCP only.
I tried Proxifier (http://www.proxifier.com/) and it works: the network calls from dnscrypt-proxy are intercepted and tunneled through the proxy. I guess the linux equivalent would be proxychains.
About the title: does dnscrypt-proxy support authentication for SOCKS5? How? Nowhere in documentation is described how to specify credentials.

socks5://user:password@<IP_ADDRESS>:9050 should work.
TBH, I haven't tried but the Go SOCK5 client code I use appears to support authentication out of the box.


Do not create dynamic pvc if an existing one is set for Galaxy

This PR fixes a bug where the dynamic pvc for Galaxy is still created when an existing PVC is set to be used.

Nice catch!


Broken Link for mobile-services.json

Description
Link to example of mobile-services.json is broken in docs.
Steps to reproduce

Navigate to https://github.com/aerogear/aerogear-js-sdk/blob/master/docs/auth/README.adoc#configuration-file
Scroll to 'Configuration File' section
Click on 'mobile-services.json' link

Actual: Error 404 page.
Expected: Link should be valid and should navigate to examples.

@mishraas Thanks for creating an issue! I have created a PR #96 to resolve this.


Exposure count change notification

In the lastest version of the iOS app, notifications seem to have been implemented to remind you to check the app on a regualr basis An additional and helpful notification would be to enable notifications if your exposure count changes (up or down). As it stands now, you are not warned if the situation changes, therefore unless checking on a daily basis, no way to understand where your potential exposure was.
Warning people would allow for better adoption of changes to behaviour such as avoiding places that are shown to be continually risky.
 With this in mind the exposure count change should be configurable (opt in)
Check notification

Exposure count

Internal Tracking ID: EXPOSUREAPP-4681

Actually, the implementation is the following:
The notification in the first screenshot is fired if 36h without a successful risk calculation have passed.
There is another notification, saying "You have new messages from your Corona-Warn-App." if you're risk status has changed from low risk to high risk. There is no notification for low risk encounters.


unexpected error

Describe the issue in detail here. Attach any relevant screenshots or files. The section below was automatically generated. Remove any information that you do not wish to include in the report.

Debug Data

Property
Value

Name
"Wolfram/Chatbook"

Version
"1.0.4"

EvaluationEnvironment
"Session"

FrontEndVersion
"Desktop: 13.3 for Microsoft Windows (64-bit) (July 24, 2023)"

KernelVersion
"13.3.1 for Microsoft Windows (64-bit) (July 24, 2023)"

SystemID
"Windows-x86-64"

Notebooks
True

DynamicEvaluation
False

SynchronousEvaluation
False

TaskEvaluation
False

Settings
Inherited

Stack Data
catchTop
checkResponse
throwFailure
trimURL

Failure Data
<|
  "Evaluation" :> Wolfram`Chatbook`Actions`Private`toolFreeQ[ProgressIndicator[Appearance -> "Percolate"]]
  "Arguments" -> {}
|>

Nothing to add

This was fixed in #297. Evaluate PacletInstall["Wolfram/Chatbook", UpdatePacletSites -> True] to get the latest updates.


Upload to organisation- apps not supported

Unable to upload the app to the organization-app.
I don't see any information related to the organisation in the documentation or in the code.
upload url I see in the code, req.url("/v0.1/apps/#{owner_name}/#{app_name}/release_uploads/#{upload_id}")
Need the support to upload the .ipa to the organisaiton-app.

@balchander have you managed to do this?

@vgrigorjeva Yes.
If your app URL is "https://appcenter.ms/orgs/<org-name>/apps/<app-name>"
appcenter_upload(       api_token: <api-token>,       owner_name: <org-name>,       app_name: <app-name>,       ipa: "./App.ipa",       release_notes: <notes>,     )

Thank you, @balchander , but this didn't work for me. I found another solution so far.

How do you managed to do this @vgrigorjeva

@dlarrain , I forked this repository (https://github.com/vgrigorjeva/fastlane-plugin-appcenter) where I changed the upload path. in Pluginfile instead of gem 'fastlane-plugin-appcenter' I used gem 'fastlane-plugin-appcenter', github: "vgrigorjeva/fastlane-plugin-appcenter", ref: "toOrg", so I could do my first upload to organization app. After @balchander comment I tried to make another upload, but without fork and it worked..

current microsoft master has support orgs already

not yet, PR is still open #75

@evkhramkov To clarify, upload to organization is current supported, but automatically creating an app under organization is not. Is that correct?

@DennisPan yes, you're right. We have a PR #75 for auto creation but it is still open with the question about api design (should it have explicit isOrg parameter or not)


editMessageText not working CALLBACK

I'm trying to edit a message when someone clicks an InlineKeyboard button, but it's not working.
my code:
`<?php
/**

This file is part of the PHP Telegram Bot example-bot package.
https://github.com/php-telegram-bot/example-bot/

(c) PHP Telegram Bot Team

For the full copyright and license information, please view the LICENSE
file that was distributed with this source code.
*/

/**

Callback query command

This command handles all callback queries sent via inline keyboard buttons.

@see InlinekeyboardCommand.php
*/

namespace Longman\TelegramBot\Commands\SystemCommands;
use Longman\TelegramBot\Commands\SystemCommand;
use Longman\TelegramBot\Entities\ServerResponse;
use Longman\TelegramBot\Exception\TelegramException;
use Longman\TelegramBot\Request;
class CallbackqueryCommand extends SystemCommand
{
/**
* @var string
*/
protected $name = 'callbackquery';
/**
 * @var string
 */
protected $description = 'Handle the callback query';

/**
 * @var string
 */
protected $version = '1.2.0';

/**
 * Main command execution
 *
 * @return ServerResponse
 * @throws \Exception
 */
public function execute(): ServerResponse
{
    // Callback query data can be fetched and handled accordingly.
    $callback_query = $this->getCallbackQuery();
    $callback_data  = $callback_query->getData();
    $callback_MSG_ID  = $callback_query->getMessage()->getMessageId();
    $callback_CHAT_ID  = $callback_query->getMessage()->getChat()->getId();

if($callback_data == "consultas"){
$data['chat_id'] = $callback_CHAT_ID;
$data['message_id'] = $callback_MSG_ID;
$data['text'] = 'edited... working';
return Request::editMessageText($data);
}
}
}`

Currently not able to test it myself. But did you verify that your callback query is getting called?
i think that you might need to use a GenericmessageCommand instead of a CallbackqueryCommand.

Currently not able to test it myself. But did you verify that your callback query is getting called? i think that you might need to use a GenericmessageCommand instead of a CallbackqueryCommand.

Yes, instead of putting editMessageText, when I change it to SendMessage, when I click the InlineKeyboard button it works, the message is sent, but I will do what you said.

In this case you are using inline so make sure you add 'reply_markup' in editMessageText
If you forget the reply_markup there is nothing change
Try this:
$inlineKeyboard = new InlineKeyboard();
return Request::editMessageText([
'chat_id' => $chatId,
'message_id' => $messageId,
'text' => 'editted text',
'reply_markup' => $inlineKeyboard
]);

You can null reply_markup if you don't want user click another callback
Sorry for late i've solved it today😅

In this case you are using inline so make sure you add 'reply_markup' in editMessageText If you forget the reply_markup there is nothing change Try this:
$inlineKeyboard = new InlineKeyboard();
return Request::editMessageText([
'chat_id' => $chatId,
'message_id' => $messageId,
'text' => 'editted text',
'reply_markup' => $inlineKeyboard
]);

You can null reply_markup if you don't want user click another callback Sorry for late i've solved it today😅

HaHaHa no problem, your explanation and your example helped me a lot

@MaiconKatty2 Is it working for you now?
(sorry for the late reply :see_no_evil:)

@MaiconKatty2 Is it working for you now?
(sorry for the late reply 🙈)

Yes!


Werkzeug starting a subprocess out of pycharm fails on windows due to whitespaces in path (only py>=3.10)

Outline
Trying to debug a Flask application on python 3.11 out of pycharm exits with an exit code 2 and a message showing only half of a path.

Replication
Well just create an example application with flask on python env with py >= 3.10 and it will fail immediately. After displaying debug mode: on

Environment:

Python version: 3.11
Werkzeug version: 2.2.3
Windows 10 22AH2

Possible fix?
I've narrowed down the bug to:
_reloader.py, line 269:
        while True:
            _log("info", f" * Restarting with {self.name}")
            args = _get_args_for_reloading()
            new_environ = os.environ.copy()
            new_environ["WERKZEUG_RUN_MAIN"] = "true"
            exit_code = subprocess.call(args, env=new_environ, close_fds=False)

args contains a list of arguments to execute. On windows pycharm hands over a pydev tool for debugging (e.g.: "C:\Program Files\JetBrains\PyCharm 2023.1.4\plugins\python\helpers\pydev") which contains whitespaces. For some reason subprocess.call needs this string to contain double double quotes in front and at the back or otherwise it will only try to execute until the first whitespace. Which results in the error (can't find "C:\Program "). This seems to be a particular problem with windows and the standard shell.
A possible fix would be:
_reloader.py, line 171:
    if sys.version_info >= (3, 10):
        # sys.orig_argv, added in Python 3.10, contains the exact args used to invoke
        # Python. Still replace argv[0] with sys.executable for accuracy.
        return [sys.executable, '""' + sys.orig_argv[1] + '""', *sys.orig_argv[2:]]

which would produce the encapsulation. Since this "fix" seems pretty janky to me and since I don't understand anything about Werkzeug, I won't make a PR, probably you guys understand what's happening here. And I think in older python versions this is not a problem because some magic is happening below line 171...

Don't use the reloader if you want to use an external debugger.

@ThiefMaster sorry but I can't influence that part. Pycharm is doing this on "its own" when you press debug. Maybe if you could provide more information I can write them a bug report so that they'll change their tooling.
As for the second part, yup I've read that too, but just seems to be wrong. Since it's only working with the double double quotes. Which is pretty annoying since it hinders every debugging effort...

I'm not asking you to change tooling, I'm just suggesting you to disable the reloader; this is done by passing --no-reload (possibly --no-debugger as well so exceptions actually bubble up to the pycharm debugger) to the flask run call.

Duplicate of https://github.com/pallets/werkzeug/issues/2707, this is an issue with PyCharm and has been reported here: https://youtrack.jetbrains.com/issue/PY-60819/FLASKDEBUG1-breaks-debugger-when-Python-PyCharm-installation-path-has-spaces, click the thumbs up icon next to the title to vote for it to be fixed.

Please don't go over to the other issue and suggest that the issue is with Werkzeug after we tell you it's not.


Code style

I am using this set of snippets in a project where I have the airbnb eslint rules. What is the best way to make these snippets conform to those style rules?
Should I fork my own and manually install them in atom?
Or, are you willing to merge a PR that uses airbnb code style?
Thanks so much!

We would like to conform with airbnb's code style, so if you have any fixes available, then submit a PR with them :)


Importing from bootstrap.dat locks the UI

Importing from a bootstrap.dat file locks the UI with no user progress.  This operation should be compartmentalized and reconfigured to surface progress indicators.

@1RedOne point noted
Working to bring the pertinent upstream components to improve the user experience
Closing issue


dart plugin bug about for code auto completion

when press enter

what I expect is:
for(value in xxx.xxx){}

The latest plugin solved this problem.


DOCS-8072-4.3-tuning-caching-kt

tuning-caching.adoc

Closing as content was applied and merged in https://github.com/mulesoft/docs-mule-runtime/pull/1475


Using print_profile on dbt sources

I can't seem to get the syntax correct for using the print_profile macro on command line with a dbt source.
I've tried the following:
dbt run-operation get_profile -t dev --args '{"relation":"source(my_source)"}'

And several other variations.  Any ideas how this would work?

Hi @dweaver33 ! In the example you have you're using the get_profile macro instead of print_profile. Try this:
dbt run-operation print_profile --args '{"relation_name": "my_table", "database": "my_database", "schema": "my_schema"}'

Let me know if that works!

Ah, ok, that works.
One last question:  Any way to put a WHERE clause on the profiler?  Like if we wanted to only profile data that meets a certain criteria?

@dweaver33 That's a good question and I haven't thought about that yet. Currently, there's no easy way to put a WHERE clause into the profiling query but adding it should be easy. Basically we'd need to add a where argument to the get_profile macro and all the other macros that use it. Would you be interested in contributing? :) I'd be happy to help and answer any questions you may have.

Yeah, I'll give it a shot.  I have a decent idea on where to put this, so let me give it a go and submit a PR.  In the meantime, I'll open a new issue for tracking.


feat: compute cleaner status based on specs, resolve from config

this pr is subset of the this: https://github.com/java-operator-sdk/java-operator-sdk/pull/1647  ?

this pr is subset of the this: #1647 ?

Yes as mentioned here: https://github.com/java-operator-sdk/java-operator-sdk/pull/1647#issue-1474192198


Fix documentation link

Current version is 0.2.33. Of course the version number will change again by this crate is published again, so feel free to close this PR and just update the version number on the next publish to whatever the new version number is :)

Addressed in 3350e3819adf151709047e93f25583a5df681091


Expose custom gadgets to Snarky

I manually increased the estimate of the issues in this epic after we learned what was needed for them (the witness code).


Create own authentication for login

Creating an authentication without having to use outside sources (e.g. Passport).

Change from passport?


Columns reset index if data in them overflows current page.

Consider having 2 columns (labels and data) if data overflows the current page it won't continue on column 2 on the next page instead it will start on column 1.
Is there a way to prevent this?

This would be the table feature which is requested by many people. Alas, currently I don't have much time to work on this.
Sorry

I have a similar problem and tried this workaround:

switch to column layout
define columns
write text elements of row 1 into columns
switch to vertical layout
repeat with row 2 and so on

This will ensure, that end of column 2 does not go into column 1.
Do you need some code for this workaround?

If it wouldn't cause too much trouble I'd greatly appreciate it :D.

Thank you!
Will have a look and see.

Yes it works and you've set me in a cleaner direction, thank you again!


type problems

This is a meta issue for organizing things more clearly. If you'd like to add to it, open a separate issue.
Known Issues

[ ] Problem with type alias X a = a - #1371
[x] Problems with constrained type variables - #1581, #1268, #1270, #1281, #1316
[ ] No kind checking - #1146, #917, #1505, #1542
[ ] Very particular shadowing issue - #952

https://github.com/elm-lang/elm-compiler/commit/5fe9bb9602163927295a6b37a64fd47f982d502a fixes the reported problems with constrained type variables.

Closing to track "kind checking" specifically.


Swagger Schema 2.0  ApiKey

I just read  schema.json for swagger v2.0 after trying swagger editor.
I have a problem with apiKeySecurity because there is only  "header" and "query" but no "path" param.
I need to put my apiKey as path param. How can i do that ?

Parent: #585.

@webron, @MikeRalphson
looks very corner case, not seeing any API Management tooling doing like that
should the issue be closed to narrow down the feature list ?  as not retains for OAS 3.0 neither 3.1  ?

2.0 is long past the point of patch releases, and the use case seems too small to track given the lack of engagement in the past 8 years.  If there is a clear use case with enough support, this is probably best considered under Moonwalk and re-opened there.


Extra redundant error check

I was just checking the source to understand how it interacts with Postmark API and I noticed this:
https://github.com/shebang-labs/terraform-provider-postmark/blob/16f3877b0a54e4f7271b0cf9e9e456f37e0b3190/postmark/resource_server.go#L110
Not a big deal, just letting you know.
Edit:
Seems like it's repeated multiple times:
https://github.com/shebang-labs/terraform-provider-postmark/blob/16f3877b0a54e4f7271b0cf9e9e456f37e0b3190/postmark/resource_server.go#L151 etc

Thank you, will be fixes soon.