Problems converting midasnet

1. macOS
2. intel
3. openvino_2021.4.689
4. 1.6.0
5. NA
6. NA
7. NA
8. 1.10.1
9. Generated with make_onnx_model.py from the MiDaS GitHub distribution
10. python ~/intel/openvino_2021/deployment_tools/model_optimizer/mo.py --input_model midas_v21-f6b98070.onnx --output_dir openvino-onnx --data_type FP32
11. https://github.com/isl-org/MiDaS
12. See attached zip file
13. Issue Details
openvino2tensorflow crashes with a tensor size mismatch to the input of layer Add 24.
I could trace the issue to the convolution and group convolution pad management logic (lines 626 and 1687)
Somehow the padding in the group convolution causes the output tensor to shrink by 2 pixels in both dimensions.
I don't have a fix, except that commenting out the code that introduces the padding allows the model to be generated, although the model will produce erroneous results.
I attach a zip file with the MiDaS distribution with all the ingredients to reproduce the issue:
Run the openvino2tensorflow_crash.sh script in the unzipped directory.
You will have to populate the weights directory with midas_v21-f6b98070.pt, and modify the script with the path to your OpenVINO distribution.
Thank you very much for your great code and for your help :)

Fabio
Uploading Midas-vino-crash.zip…

Model
midas_v21-f6b98070.pt

command
python3 run.py --model_type midas_v21

input

output

Before exporting to ONNX, PyTorch cannot infer correctly.


Issues in Light theme in PVC, PV and storage class

On 2.5-head commit id: 30e53bd4
The text in these pages in Light theme is too hard to read. Can we make it better?

PVC details page

Storage class details page

PV details page after a PVC is attached to the PV

On 2.5-head - commit id: 30e53bd
The issues logged are seen fixed. Closing the issue
PVC Details page:

Storage details Page:

PV details page after a PVC is attached to the PV


Add new !GetCidr function

Adds function !GetCidr launched in Mar 6, 2018.
Release History

Doesn't work -- AWS documentation is wrong. They state GetCidr is the function, but the function is actually !Cidr. Talking to AWS support trying to figure out this.


Language options

My organization is interested in building a few custom pipeline tasks. Is it possible to code them in c#, and not in javascript, the worst language ever inflicted on humanity?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 44581f4a-93df-7507-3844-eadedf9a6cc4
Version Independent ID: 33c7bcf0-1512-975f-5ef8-9f2a192a84ad
Content: Add a Build or Release Task
Content Source: docs/extend/develop/add-build-task.md
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

Hi @jackbond , we default to showing Node as it's cross-platform and where most of our 1st party tasks are authored. I'm assuming that you can code them in C#, but that's an assumption. Adding @vtbassmatt to straighten me out!

No, it is not possible. You can either use something that compiles to JavaScript (we like TypeScript on our team) or PowerShell for Windows-only tasks. We've considered adding .NET / C# as another option, but it has a lot of operational downsides for fairly limited upside.


[SPARK-47067][INFRA] Add Daily Apple Silicon Github Action Job with Maven (Java/Scala)

What changes were proposed in this pull request?
This PR aims to add a new Maven build that uses Apple Silicon for Apache Spark 4.0.0.
Why are the changes needed?
To have a test coverage for Apple Silicon environment.
For Python and R, we need more efforts due to their library dependencies.
We will add them separately.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unfortunately, this should be tested after merging.
Was this patch authored or co-authored using generative AI tooling?
No.

@dongjoon-hyun @viirya I made another quick try to recover this back. It uses Maven build for now (for Scala and Java). Let me know if you prefer other ways.
I don't mind closing because we would need another approach that reuses the main build for Python/R in any event.

cc @LuciferYang too


[App Service] [Discussion] Shorten appservice command group name to just "app"

I'd love to discuss whether we could shorten the appservice command group to just app (or equivalent)  in order to simplify typing it out so frequently. The use of az instead of "Azure" feels so fluid to type (as does nsg, vm, nic, acs, acr, etc.), and I wonder whether we couldn't apply a similar naming abbreviation "principal" for App Service, in order to improve the efficiency of using its command on a regular basis.
Maybe it's just me, but az app sounds and flows really well, and saving seven keystrokes for every operation would go a long way. Apologies if this conversation has already happened. I just wanted to throw it out there while the App Service module was still in beta, and could potentially make a breaking change like this.

imho az as or az appsv would be better to avoid confusion with Azure AD apps (az ad app).

@lostintangent, @stewartadam
Chatted with AppService team on this. We plan to flatten out the command structures. appservice plan becomes appservice-plan and appservice web becomes webapp.
The webapp was chosen over general terms of like app, mainly for easier discovering, considering we have close to 40 top categories now. And the name is still short enough.

What about "web" instead of "webapp"? Does the app suffix actually add anything here? I'm cool with "appservice-plan", but I wonder whether we couldn't just repurpose the "appservice" group to be specific to the plan. That way, "appservice create" was the equivalent of "appservice plan create".
I'd be happy either way, I'm just thinking out loud.

web was proposed but deemed too general to be in the CLI, and also inconsistent with terms used in existing docs.
appservice is a general term which would mean each individual offering like mobile, webapp, 'logic', etc. Adding plan to be explicit is reasonable.
I care less on the plan now. Since on webapp create we will create/reuse a plan automatically, and the plan will mostly become transparent.

Sounds good!

The plan part makes sense, but what's the plan to unify branding around the other app types (e.g. API, logic, mobile) then? What will happen to existing scripts that make use of the 'appservice' namespace?

@stewartadam raises a great point. I believe that API and mobile apps are really just webapps under the hood, but logic apps aren't. Are we going to have "logicapp" and "webapp" as top level resources (my vote is an emphatic no).
You could also have a structure with "app" as the root and place "service-plan" as a subgroup inside, while the commands to create and manage apps would be at this basic "app" level. This is a bit of an inversion from the norm, but I think it could be justified based on (1) the fact that the appservice team wants the concept of "app service plans" to be essentially transparent, and (2) the fact that we can (and it has been recommended) that we create the service plan when we create the webapp if it doesn't already exist.

(The discussion with appservice group is still on-going, and I will incorporate all feedback here)
The plan is to get all app types to be on-top like az logicapp. There are business needs and market effort to align with, hence followed the requirements of visibility and discoverability to their service users. Nesting under a general term is not favorable option to service teams, even though it makes logic sense to CLI team. Also very few users I know of will use across all commands in CLI, rather just limited to couple of services' command-set, and they do want to find those commands quickly, and mostly by just following the market term to spot a category in CLI.

FTR, webapplinux is a terrible name.

Yeah I really don't like "webapplinux" either :) Once web apps on Linux GAs, I was actually hoping we could make Linux the default, so that users didn't even need to know the difference of platform unless they wanted Windows.

This still stays at the level of an idea circulated internally and there is no plan on board to really do it at this point

Note that the portal also further distinguishes between bot, API, web, etc apps as well. A decision to use top-level namespaces will need to be clear on how to brand these types of apps (if it is going to at all), and if so then any new possible new classes of apps going forward.
imho, a single top-level group like @tjprescott described is best and provides the most flexibility going onward. Understood that there are other pressures here for the naming, but my 2 cents: this is a CLI tool, and should be treated as such. Do what's makes the most sense for CLI tooling.

//cc: @SyntaxC4, @davidebbo, @Ahmedelnably

Wanted to check in to see if there have been any updates here -- happy to discuss further (both here or privately) if you'd like.

We went with webapp


Tweak Docker setup for local development

This PR makes a few tweaks to our (wonderful) docker local development setup.
Additions

Adds eval $(docker-machine env) to shell.sh and attach.sh in case the user forgets to run it (as I frequently find myself doing)
Adds .python_env to .gitignore
Adds a docker argument to setup.sh and runserver.sh to allow them to still be used for setup and running.
Adds the ability to run a command directly with shell.sh, i.e. ./shell.sh cfgov/manage.py migrate

Changes

Fixes the link to the usage document in the installation instructions
Fixes the comment formatting in the .gitignore file
Updates the documentation for the above changes.

Checklist

[x] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewer tool :arrow_right:

I agree about .python_env--
The other change would break things for people who aren't using Docker machine (say, a user with the official Docker for mac installed, or a Linux user). I think that's worth avoiding? Maybe it's acceptable, though
In the docs, I brought up the possibility of using autoenv for that.

@rosskarchner but aren't shell.sh and attach.sh only useful with docker? How does adding the eval there break non-docker folks?

I've also added a proposed modification to setup.sh and runserver.sh so that they can be run as they are now, or with docker as the first argument.
If setup.sh is run as setup.sh docker then the mac-virtualbox-init.sh script is run.
If runserver.sh is run as runserver.sh dockerthen thedocker-compose up` is run.
@rosskarchner, what do you think of that? That'd make the broad-strokes of the current workflow similar for both approaches.

not "Non-Docker", but "Non-Docker-Machine".
Docker Machine is only a necessary piece where you need to run the docker daemon in a VM. The official "Docker for Mac" does some other magic, which uses the native OS X hypervisor. On Linux (and I think, Windows, in some scenarios at least) Docker runs natively and Docker Machine isn't neccessary.

I like the runserver and setup changes!

Should update the docs, tho ;)

Alrighty, updated the documentation and added the frontend setup to running setup.sh docker.


Ignoring a rule also ignores completely unrelated rules

Describe the bug
--skip-rule seems to skip all rules instead of just the rule that is specified to be skipped.
To Reproduce
Steps to reproduce the behavior:

Given this repro.yaml
Run redocly lint repro.yaml
See two errors (this is expected): missing scopes (spec rule), missing 4XX response (operation-4xx-response rule).
Run redocly lint --skip-rule=operation-4xx-response repro.yaml
Get Woohoo! Your OpenAPI definitions are valid.

Expected behavior
Step 6 should return one error, from spec rule.
Redocly Version(s)
1.0.0-beta.125
Node.js Version(s)
19.9.0

Hi @jankodera-ps,
I believe that this issue occurs because of the wrong order of parameters passed to the lint command.
What I mean is if you pass the API definition file first and additional parameters after (e.g.  redocly lint repro.yaml --skip-rule=operation-4xx-response instead of redocly lint --skip-rule=operation-4xx-response repro.yaml), everything works fine. In case you pass additional parameters first, you will get the invalid validation of the API definition:

Hope it helps.

Okay, happy to see it can be easily fixed, but have to say this behavior is definitely unexpected.

The issue here is that the --skip-rule option expects an array, so it recognises the positional argument as a part of the array. This is a known issue in yargs library, which we use here for parsing the arguments.
By the way, the behaviour will change after this MR: https://github.com/Redocly/redocly-cli/pull/1055 (it will fail with a message that no APIs were provided).
One option to fix this is to use the parser configuration setting 'greedy-arrays': false (which I believe will eventually become yargs default). However, it will affect our current users' scripts.

Right, in this context the problem now makes sense. What is really weird is that this issue can be reproduced even with --skip-rule=spec-components-invalid-map-name, which I really wouldn't expect to consume additional positional arguments beyond the first one explicitly indicated to belong to the --skip-rule.
I know this kind of falls outside the scope of this project as it is a problem in a dependency library and you already have a solution as @tatomyr indicated above, but would it make sense to consume just one argument with comma-separated rule names? That would resolve the ambiguity while providing the same functionality.

@jankodera-ps this would be an option if we don't have to support the current syntax (with spaces as separators). And we have other commands with similar behaviour also. We will think of possible solutions.
Anyways, thank you for bringing attention to this!

Should be fixed in beta.127.


[Feature] Ability to interact with CheckBox elements

Describe the feature and how it will be used

Introduce the ability to interact with the Uno Platform CheckBox element.
There should be properties to assert the checked status of the element, as well as actions to check the box on and off.
Platforms

[x] iOS
[x] ~Android~ [Done]
[x] ~WebAssembly~ [Done]

Implementations added for web and Android

Completed ✅


add config: allow surrounding output with backticks

Hi,
thank you for this amazing work.
I needed a few extra features for a project of mine, so I added them myself.
Since I don't know if you are welcoming new additions or if this feature even is on your roadmap, feel free to reject this PR.
If you want to discuss around this work, please do.
Anyway, if you would like to know more about what I did:
The idea was that I wanted to be able to directy preview output file. I therefore needed it to have the proper backticks characters for parsers to understand it.

Added a new config entry: encloseWithMermaidBackticks (boolean)
If this entry is not set, or false, behaviour will be default (nothing more than what mermerd already does)
If this entry is set to true, it will prefix output by "mermaid", and insert "" right before the ending new lines.

Have a great day,

Thanks for the PR and the detailed description!
This feature is sure to be useful for others as well and your implementation fits perfectly - I will happily accept the PR.
FYI: after the merge I will update the readme and also add the possibility to set the config via the command line (also the go.mod and go.sum seem a bit weird) . After that I will publish a new version.

@rvictorino The new version with your feature is available (v0.0.5)
I fixed the issue that you added the backticks suffix multiple times after each table definition, which breaks the diagram if you have multiple tables or constraints e.g. in the GitHub markdown previewer. If I got it right, all the mermaid syntax needs to be in one opening and closing block.

Thanks for your quick feedback. Your are right, the prefix and suffix must only be added once. Sorry that I missed that ! (I'm totally new to golang).
Thanks again for the great work


Make compatible with xrayvision.visibility.Visibilities

Do not merge before TCDSolar/xrayvision/pull/67
Make the imaging demo compatible with the new xrayvision.visibility.Visibilities class. To be merged after #67.

So I think the doc build fails are because the PR on xrayvision wasn't merged. I proded the doc_build test if that passses will merge.


Add requirements.txt to manage python dependencies

Fix Issue #171 - Added requirements.txt to each python container directory to manage dependencies and edited Dockerfiles to use requirements.txt where appropriate.

@adamgering I addressed the review and removed the redundant imports. Added description to the commit message after rebasing.

Docker images are rebuilt if the Dockerfile changes. They are not if requirements.txt changes. Thus, moving requirements to requirements.txt is likely counter-productive.

Why are new dependencies being installed via pip (through requirements.txt) that were not previous installed via pip?

I'm going to close this PR, the change is not required.

@adamgering this change was already approved in our sprint planning. The change to using requirements.txt allows dependencies to be added or removed without editing the Dockerfiles. This also aligns with the intended use of requirements.txt which is to configure deployment environments.


Spelling mistake

https://learn.microsoft.com/microsoft-365/security/office-365-security/campaigns#attitional-actions

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c6c6c12e-33b7-8086-c4eb-4f5fbc751901
Version Independent ID: 3b098f74-d3cc-c720-bd93-2fc5310cfe57
Content: Campaigns in Microsoft Defender for Office 365 Plan - Office 365
Content Source: microsoft-365/security/office-365-security/campaigns.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@davidfox2, fixed.
In the future, you too can make updates like this yourself without opening a GitHub Issue first. Instructions are here.
Thanks for the feedback.
Closing


Ui tries to co connect to http://localhost/ui/None

While loading any ui page.
Doesn't seem to cause issues, though.

Behavior disappeared


Add documentation section about renewing expired keys

It would also be nice, if GPGit could warn, if a key expires within the next 3 Month.

Fixed documentation: https://github.com/NicoHood/gpgit/commit/fa3c0517490f554f1fb5bad56c7adf67e6765a20
Still working on some code that checks expiration

@WoLpH Do you know if there is an easy way to use gdate as default?
This is how we do it with getopt, I am wondering if
a) my code is correct for gdate
b) it can be simplified, similar to the getopt version
# BSD getopt works completely different from gnu-getopt,
# so check if have an alternative getopt install.
if [[ -x /usr/local/opt/gnu-getopt/bin/getopt ]]; then
    export PATH="/usr/local/opt/gnu-getopt/bin/:${PATH}"
fi

# Use gnu date on mac
if command -v gdate &> /dev/null; then
    alias date="gdate"
fi

The code for gdate appears to be correct, that would work on my system at least.
With regards to a simpler solution, I believe there is one but it might depend on how you have gdate installed. In my case I have the coreutils package installed through brew which provides a directory with symlinks to the g-versions.
In that case, this would work:
export PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"

And the binary is /usr/local/opt/coreutils/libexec/gnubin/gdate then?

No, it's date and it's symliked to gdate. Let me clarify :)
# ls -l /usr/local/opt/coreutils/libexec/gnubin | awk '{printf "%s -> %s\n", $9, $11}'
 ->
[ -> ../../bin/g[
b2sum -> ../../bin/gb2sum
base32 -> ../../bin/gbase32
base64 -> ../../bin/gbase64
basename -> ../../bin/gbasename
basenc -> ../../bin/gbasenc
cat -> ../../bin/gcat
chcon -> ../../bin/gchcon
chgrp -> ../../bin/gchgrp
chmod -> ../../bin/gchmod
chown -> ../../bin/gchown
chroot -> ../../bin/gchroot
cksum -> ../../bin/gcksum
comm -> ../../bin/gcomm
cp -> ../../bin/gcp
csplit -> ../../bin/gcsplit
cut -> ../../bin/gcut
date -> ../../bin/gdate
dd -> ../../bin/gdd
df -> ../../bin/gdf
dir -> ../../bin/gdir
dircolors -> ../../bin/gdircolors
dirname -> ../../bin/gdirname
du -> ../../bin/gdu
echo -> ../../bin/gecho
env -> ../../bin/genv
expand -> ../../bin/gexpand
expr -> ../../bin/gexpr
factor -> ../../bin/gfactor
false -> ../../bin/gfalse
fmt -> ../../bin/gfmt
fold -> ../../bin/gfold
groups -> ../../bin/ggroups
head -> ../../bin/ghead
hostid -> ../../bin/ghostid
id -> ../../bin/gid
install -> ../../bin/ginstall
join -> ../../bin/gjoin
kill -> ../../bin/gkill
link -> ../../bin/glink
ln -> ../../bin/gln
logname -> ../../bin/glogname
ls -> ../../bin/gls
md5sum -> ../../bin/gmd5sum
mkdir -> ../../bin/gmkdir
mkfifo -> ../../bin/gmkfifo
mknod -> ../../bin/gmknod
mktemp -> ../../bin/gmktemp
mv -> ../../bin/gmv
nice -> ../../bin/gnice
nl -> ../../bin/gnl
nohup -> ../../bin/gnohup
nproc -> ../../bin/gnproc
numfmt -> ../../bin/gnumfmt
od -> ../../bin/god
paste -> ../../bin/gpaste
pathchk -> ../../bin/gpathchk
pinky -> ../../bin/gpinky
pr -> ../../bin/gpr
printenv -> ../../bin/gprintenv
printf -> ../../bin/gprintf
ptx -> ../../bin/gptx
pwd -> ../../bin/gpwd
readlink -> ../../bin/greadlink
realpath -> ../../bin/grealpath
rm -> ../../bin/grm
rmdir -> ../../bin/grmdir
runcon -> ../../bin/gruncon
seq -> ../../bin/gseq
sha1sum -> ../../bin/gsha1sum
sha224sum -> ../../bin/gsha224sum
sha256sum -> ../../bin/gsha256sum
sha384sum -> ../../bin/gsha384sum
sha512sum -> ../../bin/gsha512sum
shred -> ../../bin/gshred
shuf -> ../../bin/gshuf
sleep -> ../../bin/gsleep
sort -> ../../bin/gsort
split -> ../../bin/gsplit
stat -> ../../bin/gstat
stdbuf -> ../../bin/gstdbuf
stty -> ../../bin/gstty
sum -> ../../bin/gsum
sync -> ../../bin/gsync
tac -> ../../bin/gtac
tail -> ../../bin/gtail
tee -> ../../bin/gtee
test -> ../../bin/gtest
timeout -> ../../bin/gtimeout
touch -> ../../bin/gtouch
tr -> ../../bin/gtr
true -> ../../bin/gtrue
truncate -> ../../bin/gtruncate
tsort -> ../../bin/gtsort
tty -> ../../bin/gtty
uname -> ../../bin/guname
unexpand -> ../../bin/gunexpand
uniq -> ../../bin/guniq
unlink -> ../../bin/gunlink
uptime -> ../../bin/guptime
users -> ../../bin/gusers
vdir -> ../../bin/gvdir
wc -> ../../bin/gwc
who -> ../../bin/gwho
whoami -> ../../bin/gwhoami
yes -> ../../bin/gyes

# ls /usr/local/opt/coreutils/bin
 b2sum     gbase64     gchmod    gcsplit   gdircolors   gexpr     ghead      glink      gmkfifo   gnohup     gpinky      greadlink   gsha1sum     gshuf     gstty   gtest       gtsort      guptime   gyes     ptx         sha384sum   timeout
 base32    gbasename   gchown    gcut      gdirname     gfactor   ghostid    gln        gmknod    gnproc     gpr         grealpath   gsha224sum   gsleep    gsum    gtimeout    gtty        gusers    hostid   realpath    sha512sum   truncate
 chcon     gbasenc     gchroot   gdate     gdu          gfalse    gid        glogname   gmktemp   gnumfmt    gprintenv   grm         gsha256sum   gsort     gsync   gtouch      guname      gvdir     md5sum   runcon      shred
'g['       gcat        gcksum    gdd       gecho        gfmt      ginstall   gls        gmv       god        gprintf     grmdir      gsha384sum   gsplit    gtac    gtr         gunexpand   gwc       nproc    sha1sum     shuf
 gb2sum    gchcon      gcomm     gdf       genv         gfold     gjoin      gmd5sum    gnice     gpaste     gptx        gruncon     gsha512sum   gstat     gtail   gtrue       guniq       gwho      numfmt   sha224sum   stdbuf
 gbase32   gchgrp      gcp       gdir      gexpand      ggroups   gkill      gmkdir     gnl       gpathchk   gpwd        gseq        gshred       gstdbuf   gtee    gtruncate   gunlink     gwhoami   pinky    sha256sum   tac


Update deps and add OWNERS

@deads2k I believe this is required for https://github.com/openshift/release/pull/4579 to go green.  (I manually added OWNERS in that PR, but the verify-deps fails)
(bump is for the git add -f vendor fix)

/test all

/lgtm


Update @bugsnag/plugin-vue docs for Vue.js 3

Describe the bug
Vue.js 3 was released a few days ago and I'm trying to integrate Bugsnag into an application based on it. However, I'm not sure how to plug in BugsnagPluginVue. The documentation says that you can initialize the plugin this way:
Bugsnag.getPlugin('vue').installVueErrorHandler(Vue);

However, Vue.js 3 no longer uses Vue constructor to initialize the application. Instead, it uses createApp function. There's also no contructor being exported from vue module.
So my question is: What is the right way to initialize BugsnagPluginVue in Vue.js 3 application? And can you update the documentation?
Steps to reproduce

Create a new application using Vue.js 3
Try to integrate Bugsnag with BugsnagPluginVue
See there's no Vue constructor anymore

Environment

Bugsnag version: 7.3.5
Browser framework version (if any):

Vue: 3.0.0

Hi @livthomas
We need to make some changes to the Bugsnag plugin to accommodate the breaking changes in Vue 3:
https://v3.vuejs.org/guide/migration/global-api.html#global-api
We'll be releasing a new version of bugsnag-js which supports Vue 3 soon as well as updating the installation docs.

@mattdyoung I can see that a few minor versions of bugsnag-js have been released since I reported this issue. But nothing related to Vue.js has been changed. There are only React Native updates. When can we except a new version of bugsnag-js which supports Vue.js 3?

Any update on this? Thanks

This is very much on our radar and we're looking to address Vue 3 support in the near future. We'll need to consider how we maintain backwards compatibility with Vue 2 when we make the changes.
We have a number of competing priorities right now so it's likely to be a few weeks before this work gets underway.

@mattdyoung please upgrade to vue3. We have paid account in Bugsnag and are going to upgrade our app to vue3, but bugsnag dependency is blocking upgrade.

@mattdyoung please upgrade to vue3. We have paid account in Bugsnag and are going to upgrade our app to vue3, but bugsnag dependency is blocking upgrade.

Hi @morr
We've now started work on Vue 3 compatibility. It's a non-trivial change as we still need to maintain compatibility with Vue 2 as well.
We'll be sure to provide an update here once the implementation is finished and released.

Hi @morr
We've now started work on Vue 3 compatibility. It's a non-trivial change as we still need to maintain compatibility with Vue 2 as well.
We'll be sure to provide an update here once the implementation is finished and released.

+1 So there is no way to have Bugsnap with Vue 3?

The bugsnag-js library now supports Vue 3 as of https://github.com/bugsnag/bugsnag-js/releases/tag/v7.7.0.
Check out the docs here: https://docs.bugsnag.com/platforms/javascript/vue/

Awesome!!! Thank you for your work. Congrats the team :)


[qtdeclarative] fix hidden build order dep on qtlanguageserver

Fixes #34878

Compile test pass with following triplets:
x64-osx


Top navbar only error

I would like to have top navigation only, no sidebar. On a clean installation I set layout_topnav=>true and I receive the following error:
Illuminate\Foundation\Bootstrap\HandleExceptions::handleError
vendor/jeroennoten/laravel-adminlte/src/../resources/views/partials/menu-item-top-nav.blade.php:13
What else needs to be set?

I solved... the default menu has header items which are not supported on navbar.


Add option to prevent reset of pagination on onSearchClose callback

Hi, is there any way on how to prevent pagination reset when clicking the close search icon?
Because in my case, I don't want to reset the page when the user click the search icon and then close the search without typing any search text.

I think this is a bug. :)
The pagination always change to 1-10 of 124, here are the steps:

click the next button for page 2 (the pagination will become: 11-20 of 124)
click the search icon, then close it without typing any text in the search input
notice the pagination will become 1-10 of 124

Here is the codesandbox:
https://codesandbox.io/s/boring-darkness-uqqjw

I can confirm the bug, thanks for reporting @kenjoegolo.

Maybe I can open a pull request for this?

Thanks for offering @phanshiwen, but I've already got one locally, I just wanted to push other things first so I could use some new functions.
If you still want to help in other ways, there are plenty of things needed, such as boosting the test coverage or improving compliance with material-ui v4!

Can't wait to get those fixes :)

PR up, fix will be in a patch release, coming soon.


simplify getting started

Remove having to open cargo.toml for getting started

Great. I saw someone suggested this on Reddit.

Yes, this is what motivated this PR


Document how to initialize Crashlytics with Xcode debugger attached

#no-changelog

Nice - is this documented in the docs as well?

Do you mean externally? I don't believe so - I can definitely add something if you think it would be helpful. The comment here was mainly to document the process for internal debugging.


Protection is Enabled for the branch 'main'

The following protections were added to the 'main' branch of the repository:

Require a pull request before merging
Required Code reviewers 2
Require status checks to pass before merging
Enforce Admins

@ravithallam
For more information, please see: https://github.com/org-apex/github-repo-auto-protect

Protection is enabled


PoC: Changed rules to be async

I stumbled across https://github.com/eslint/eslint/issues/15394 and thought it would be interesting to see what the code would look like and which API points would need to change. Roughly every developer-facing API that runs any rule logic needs to become async:

CLIEngine's executeOnFiles and executeOnText
Linter's verify and verifyAndFix
RuleTester's run
The Flat* equivalents for all of ☝

This branch gets all but 8 tests passing with  ./node_modules/mocha/bin/_mocha  -R progress -t 1000 -c "tests/{bin,conf,lib,tools}/**/*.js" --reporter list. It doesn't update any docs.
Sending this as a draft in my own personal fork so as to not clutter the core ESLint PR queue.

Closing per https://github.com/eslint/eslint/issues/15394#issuecomment-1684017615.


change all virtualenv url to http://www.virtualenv.org/en/latest/

Change  virtualenv URL from http://www.virtualenv.org/en/latest/ to http://www.virtualenv.org/en/latest/

sure, avoiding redirects on the outbound links makes sense to me. thanks!


Future month gets displayed in range mode ignoring the set "maxDate"

If using the datepicker in range mode and if a max date gets set, the picker displays the next (future) month as well with all days disabled, which does not make sense.
How to reproduce:

Use datepicker with "range" mode
Set "maxDate"
When the picker gets opened, the next month (exceeding the max date) also gets displayed (all days are disabled though and you can not go one more month further into the future). It is also possible to navigate to the future month via header arrows

Expected behaviour:

If a "maxDate" is set in range mode, the next month (exceeding the max date) does not get shown at all and it should not be possible to show it by clicking the "next" arrow.

I.e. If the max date is set to last day in August 2024, the selected date range is also some range in August and I open the datepicker, it does not make sense to show September month as second month in the datepicker flyout, since a user cannot select anything there anyway. It would make more sense to then show Juli and August.
I could also not find a way to bypass this behaviour.

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Jamf-Pro-External-Application-Custom-Schema-com.macjutsu.super-v4.1.0-beta1

Updated the JSON to include the new keys introduced with super v4.1.0-beta1, as well as went back through and added missing preference keys from 4.0.0 that were not added to the previous version of the JSON Schema
Jamf-Pro-External-Application-Custom-Schema-com.macjutsu.super-v4.1.0-beta1.json

Thank you!
I committed directly to the v4.0.1-beta1 repo and updated the Changelog and Release notes... https://github.com/Macjutsu/super/releases/tag/v4.1.0-beta1


The PR does not have to touch any of the code related to
these test.
One must "retest" these tests only in order to pass.
The cause needs to be identified and resolved.
ci/prow/intersmash-e2e
ci/prow/prod-intersmash-e2e-prod
Expected behavior
These tests should run and pass on 1st just like the other tests.

Hi @rsearls - This issue can be closed as the OpenShift Prow based CI checks have been removed, see https://github.com/Intersmash/intersmash/discussions/186


incorect evaluation of literals for binary expression

Literals inside the binary expression 8 * 3.1 are incorrectly evaluated as different types, where

8 is evaluated as int
3.1 is evaluated as float

But in this case golang automatically retype 8 to float (or more precisely float64). For expressions where operands are given as basic literals, an extra type checking should be done.
Output from test:
--- FAIL: TestParseBinaryExpr1 (0.00s)
	gen_expression_test.go:97: Unexpected error for expr '8 * 3.1': Binary operation "*" over two different types: "int" != "float"

If the literals are given via variables, the go complains about types mismatch [1].
So the implicit conversion is done over number literals only [2]
[1] https://play.golang.org/p/6Cj85TJdGg
[2] https://play.golang.org/p/fgA4OPcDEz

Fixed


Problem

Hello I am trying to use the API but every time I try to use any method it gives me this error HeaderMalformedError: The 'Authorization' header was malformed or not in an expected format. could you help me?

I've just tested by creating a fresh project with the first example provided in the README and everything's working fine.
It's more likely that you've provided an invalid token. Feel free to open a support ticket onsite via: https://builtbybit.com/tickets/new

One more question, should I use the private or shared token, maybe that's it?

That entirely depends on your use case. As per our wiki documentation page:

We support two types of tokens that grant varied access to our endpoints. The primary token type, 'Private', grants access to all public endpoints and as the name suggests, should be kept private. This token type grants access to view and modify potentially sensitive data specific to your account.
Alternatively, we also support a secondary 'Shared' token type that grants very limited access to our API and can be shared with other members or within your products. This token type grants access to public validation of resource licenses, public version checking and public update checking. However, its scope is limited to your account and the resources you've authored solely.

Ok, thank you very much, try again and verify the token.


[Allocator] Introduce tensorpool_mkl_allocator

Tensorpool mkl allocator combines tensorpool_allocator and mkl_allocator to improve allocator performance for both small size and large size memory allocation.
To confirm our allocator is effective, we test it on "shoucai" model.
Test env: CPU Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz, 1 socket, 32 cores, lock frequency to 2.6GHz
Command line:
$python3 graph_runner.py --input-graph=sub_graph_external.pbtxt  --input-data=placeholder_dump.json
Result

shoucai

Allocator
loop
process_num
latency(1)
latency(2)
latency(3)
latency(4)
latency(5)
avg

TensorPoolAllocator
1000
1
94.84
86.32
90.45
86.47
91.89
90.00

1000
5
342.78
324.96
344.92
337.50
339.84
338.00

1000
10
716.42
722.26
716.44
709.10
720.14
716.87

MKLAllocator
1000
1
59.56
58.15
58.80
59.82
60.03
59.27

1000
5
324.29
322.76
321.69
326.25
324.64
323.93

1000
10
701.34
700.69
701.10
701.55
701.09
701.15

TensorpoolMKLAllocator
1000
1
61.27
58.49
57.48
58.51
61.36
59.42

1000
5
327.43
327.40
327.32
326.21
326.87
327.05

1000
10
707.21
707.69
706.83
708.57
708.25
707.71

@yuanhu2435  Thanks. I got your perf data from shoucai model, but I didn't catch the perf differences both small size and large size. Did you test shoucai model perf on small batch size and large batch size?

I think we need to collect more perf data for more models since this is the fundamental change.


feat: Add field name in the Policy

Includes the field name for the Policy as an optional. The name helps users define and identify a policy with a unique identifier, allowing even versioning.
Motivation:
It can be difficult to manage and identify multiple policies by a file name or its content, depending on the storage usage.
In automation, this field can also be helpful.

I'm a bit nervous about this. On the one hand, it can be useful to ensure a supply chain owner signs the right policy and the orchestration actually provides the right policy for verification. But at the same time, I'm worried about a policy self identifying itself (where only the name + supporting data in the policy is used during verification) without appropriately bootstrapping the policy metadata's trust. If we can't guarantee a policy is bootstrapped using ITE-2/3 semantics, we should maybe tread carefully?

I had a chat with @kairoaraujo about this today. I think we'll store the policy name in the Archivista metadata instead of within the policy itself.

I misunderstood it. We don't require it in the Policy metadata.


feat(ci): add PR evaluation

Description
This PR add PR evaluation, lint, format and git message checks into the CI pipeline.

Interesting that Vercel doesn't fail here... Anyway, great effort, @JaeAeich. Let's see what @git-anurag-hub says

@uniqueg yeah the issues seems to be how we

@uniqueg yeah the issue seems to be with how dependencies insode monorepo are build in CI.
IDK why this PR is not being evaluated though. Since I pushed the yaml it should evaluate this one as well :man_shrugging:

@git-anurag-hub How are we going to use elixir-eslint-config? this already has a huge list of rules, migrating that would mean alot of code changes, but maybe let me try if its otherwise.

Maybe linter changes are a lot all at once, but usually they are just repetitive work, nothing hard.
What you could do is address everything but the linting and open another issue for that. Maybe someone else feels like taking it up, e.g., as a warmup to get to know the codebase :) Anyway, it's not urgent


Warning when compiling with GCC 5.4

When I compile rttr with -Wall with gcc-5.4, I get quite a lot of warnings. Unfortunately, some of them show up in programs using the library, too. In particular, I see a similar warning than the following for files that contain an RTTR_REGISTRATION block:
In file included from /home/jgehring/tmp/rttr/src/rttr/../rttr/type.h:1152:0,
                 from /home/jgehring/tmp/rttr/src/rttr/../rttr/detail/destructor/destructor_wrapper_base.h:32,
                 from /home/jgehring/tmp/rttr/src/rttr/detail/destructor/destructor_wrapper_base.cpp:28:
/home/jgehring/tmp/rttr/src/rttr/../rttr/detail/type/type_impl.h: At global scope:
/home/jgehring/tmp/rttr/src/rttr/../rttr/detail/type/type_impl.h:489:13: warning: ‘void rttr_auto_register_reflection_function_()’ declared ‘static’ but never defined [-Wunused-function]
 static void rttr_auto_register_reflection_function_();

In my project, I would prefer to not turn off this warning. However, I'm not clear what the root cause in rttr is exactly.

When you know a way how to temporarily disable this warning for a function, please tell me.
Otherwise I don't know how to fix it.

actually, it is not possible with gcc to disable this warning temporarily:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431
Its a known bug.
However, I fixed it with placing the RTTR_REGISTRATION_FRIEND function in a separate header file called:
registration_friend.h, include it with: #include <rttr/registration_friend>

Thanks for tracking this down! The GCC bug is annoying :(


Issue submitting package created in a different timezone

Today, me and a colleague worked on a release together. I created the dll in the CEST timezone and sent it to him for submission. He is in the PDT and got the following message:
"The package is invalid and cannot be uploaded. One or more files, such as 'x.dll' have a date in the future."
Is there anything we can do about this or does he really have to wait 9 hours everytime until he can submit the package? Thanks!

Can you send us a copy of the package?

Sure, you can load it from here: https://github.com/bitstadium/HockeySDK-Xamarin/releases/download/4.1.0-beta2/HockeySDK.Xamarin.4.1.0-beta2.nupkg

Seems the package does have files with a date in the future. Here's an example from that package when opened with WinRAR:

Which client are you using to create the package? On what OS?

Interesting 🤔 The package was created on a Mac using Cake 0.12.0 and Mono 4.4.0

@yishaigalatzer @rrelyea do we know which client is generating these future dates?

Thanks in advance for looking into this! ☺

Can you try creating it with the latest prerelease NuGet.exe? www.nuget.org/downloads

Thanks! That looks like it might fix the problem.
Our build toolchain tries to automatically download a NuGet.exe version from https://www.nuget.org/nuget.exe which apparently returns version 2.8.6.
Do you know if there's another generic link that always provides the latest NuGet.exe?

This should work:
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe

Perfect, thanks again!


fix spelling error

@ph0rque you didn't write any tests!

@ph0rque you didn't write any tests!

Oh I have the auto spell checker installed ;)


build: add pull request labeler

Coverage remained the same at 100.0% when pulling e680fb69d060004ae0ed9ea20299903cf081d505 on add-labeler into 1ccec81c2c718cfd847c88f70e50a1ba36a82b27 on main.

Coverage remained the same at 100.0% when pulling e680fb69d060004ae0ed9ea20299903cf081d505 on add-labeler into 1ccec81c2c718cfd847c88f70e50a1ba36a82b27 on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Spinner breaks within a method class

Hello guys, I really weird behavior started happening o spinner after v0.8.0 release, until few days ago I was using v0.7.0, and it's related to how a run block calls an instance method full code here https://gist.github.com/quirinux/6b3136c9f1dc11b085ebb12483aecd6a
But basically if I set a spinner inside a class method and try to call within spinner run an method of that class it raises a undefined local variable or method error, and as I could check it is related to context change, the only way that I found it working was storing the class self reference in a variable and then call it, which is weird too once this variable is not in local scope only, anyways:
class Foo

	def bar
		sleep 3
	end

	def spin_broken
		spinner = TTY::Spinner.new("[:spinner] :title")
		spinner.run do
			puts self, self.class
			spinner.update(title: %{Foo})
			bar
			spinner.update(title: %{Bar})
			bar
			spinner.success
		end
	end
end

Calling Foo.new.spin_broken shows what I mean, the gist linked code above has a more complete example
Running on ruby-2.4.1 release

Hi @quirinux
Thanks for using the library!
The run call hasn't changed since v0.5.0. Basically, the block is evaluated in the context of the spinner. If you wish to use external context then you need to be specific about block arguments and pass in the 'spinner':
spinner.run do |sp|
  sp.update(title: %{Foo})
end

Accepting spinner as a first argument in a block is especially handy for creating multispinners:
multi_spinner = TTY::Spinner::Multi.new("[:spinner] top")
multi_spinner.register("[:spinner] one") { |sp| sleep(2); sp.success('yes 2') }
multi_spinner.register("[:spinner] two") { |sp| sleep(3); sp.error('no 2') }

I've changed to stop evaluating spinner block in the current context to help prevent bugs like yours.


Fix differential equation tutorial

I've wanted to do this for quite some time but unfortunately my computer broke while working on an update...
So here are some fixes for the differential equation tutorial.
Most notably,

it fixes the MvNormal deprecations
fixes the trajectories of posterior samples (the used the wrong parameters)
it uses more "modern" and simpler SciML syntax
specifies the solver for the DDE example correctly.

@staticfloat I think there might be an issue with coppermind? https://buildkite.com/julialang/turingtutorials/builds/76#9b6b2925-254f-43b2-8401-9a7224be6376/205-207

Will be fixed by https://github.com/TuringLang/TuringTutorials/pull/298.

There's one remaining issue, namely that pool_chain is not exported by MCMCChains. It's a hack anyway, so I think I'll just go and fix https://github.com/TuringLang/MCMCChains.jl/issues/223. Then pool_chain is not needed anymore and the code becomes simpler.


Incorrect optimization due to OpCopyMemory

There seems to be a bug when using OpCopyMemory where the optimizer incorrectly removes code. Attached is a sample
CopyMemoryOptimizerBug.txt
If the line "OpCopyMemory %32 %25" is replaced with "OpStore %32 %30" then the optimizer will produce valid code (it'll store the input to the output).
Unless I'm mistaken and OpCopyMemory isn't valid here. The spec says: "Matching Storage Class is not required" so I would assume this code is valid.

Looks like ADCE does not recognize the OpCopyObject as a read of the memory location.


Static instrumentation + Gradle 3 Daemon = Exception class is frozen

When instrumentation is executed two times in a row an exception "class is frozen" occurs. This happens when Gradle daemon is used. In Gradle 3 daemon is used by default.
Problem description

Gradle Daemon runs tasks in its worker thread. This thread and its resource are kept alive and are reused when the task is executed again.
ActiveJDBC instrumentation uses javasist.ClassPool singleton. This pool caches CtClass objects. This cache is not garbage collected on task finish because of 1.
Instance of CtClass is a container of an instrumented class. This container has property wasFrozen which is set to true when instrumentation is done. Because of 1. and 2. when task is executed for the second time the existing instance with wasFrozen == true is retrieved from ClassPool which causes a "frozen exception".

How to simulate this

Make sure you have Gradle 3 installed.
Clone testing project: https://github.com/vkuzel/ActiveJDBC-Frozen-Model-Problem
Run gradle instrumentModel several times.
Following exception should occur:
> org.javalite.instrumentation.InstrumentationException: java.lang.RuntimeException: frozen_model.SomeModel class is frozen

How to fix this No.1
Let's remove the CtClass container off the ClassPool by calling detach() method just right after the instrumentation. When ClassPool.get method will be called next time a new unfrozen instance of CtClass will be created. Old instance will be handled by garbage collector.
What if instrumentation will be executed on already instrumented class?
Here's commented snippet that actually performs the instrumentation.
There's nothing that can cause trouble if its executed multiple times.
    private void doInstrument(CtClass target) throws NotFoundException, CannotCompileException {
        CtMethod[] modelMethods = modelClass.getDeclaredMethods();
        CtMethod[] targetMethods = target.getDeclaredMethods();

        CtMethod modelGetClass = modelClass.getDeclaredMethod("modelClass");
        CtMethod newGetClass = CtNewMethod.copy(modelGetClass, target, null);
        newGetClass.setBody("{ return " + target.getName() + ".class; }");

        ClassMap classMap = new ClassMap();
        classMap.fix(modelClass);

        CodeConverter conv = new CodeConverter();
        conv.redirectMethodCall(modelGetClass, newGetClass);

        for (CtMethod method : modelMethods) {
            int modifiers = method.getModifiers();
            if (Modifier.isStatic(modifiers)) {
                if (targetHasMethod(targetMethods, method)) {
                    Instrumentation.log("Detected method: " + method.getName() + ", skipping delegate.");

How to fix this less preferred solution No.2
Let's call defrost() on a CtClass instance right after the instrumentation. Since instrumentation can be executed on already instrumented classes without problem this shouldn't cause any problems.
I am not sure about internal state of the CtClass object I can't recommend this approach.
How to dirty-quickly fix this No.3
Run instrumentation in separate thread. Destroy this thread when instrumentation is done. Java will (hopefully) garbage-collect it's resources.

@vkuzel thanks for a well-researched issue, and for the contribution. The snapshot will be available soon at: http://repo.javalite.io/

@vkuzel build successful, closing

get a latest snapshot here: http://repo.javalite.io/

@vkuzel, did you ever verify that this worked for you? Looks  like there are some loose ends: https://github.com/javalite/activejdbc/issues/550
Also, when I ran your sample project I never got that exception

@ipolevoy Yes. I use instrumentation on a daily basis.
gradle -version

------------------------------------------------------------
Gradle 3.1
------------------------------------------------------------

Build time:   2016-09-19 10:53:53 UTC
Revision:     13f38ba699afd86d7cdc4ed8fd7dd3960c0b1f97

Groovy:       2.4.7
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_101 (Oracle Corporation 25.101-b13)
OS:           Mac OS X 10.11.6 x86_64

Right now I once again run test project. What happened:

gradle instrumentModels runs build and starts Gradle Daemon.
Gradle Daemon is running.
gradle instrumentModels fails with model is frozen exception. See the console output: active_jdbc_instrumentation_problem_console_output.txt.

@vkuzel I added  your sample app to the project for testing: https://github.com/javalite/activejdbc/tree/master/activejdbc-gradle-plugin/sample-project
However, when I build it multiple times, I do not see that issue.
➜  igor 13:36:39 /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project git:(master) gradle instrumentModels
:compileJava
:processResources UP-TO-DATE
:classes
:instrumentModels
Thread name: main
Task has been executed for the first time so ClassPool is not yet initialised!
**************************** START INSTRUMENTATION ****************************
Directory: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main
Instrumented class: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main/frozen_model/SomeModel.class
**************************** END INSTRUMENTATION ****************************
Hash code of CtClass:<PHONE_NUMBER>

BUILD SUCCESSFUL

Total time: 9.617 secs
➜  igor 13:36:55 /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project git:(master) gradle instrumentModels
:compileJava
:processResources UP-TO-DATE
:classes
:instrumentModels
Thread name: main
Task has been executed for the first time so ClassPool is not yet initialised!
**************************** START INSTRUMENTATION ****************************
Directory: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main
Instrumented class: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main/frozen_model/SomeModel.class
**************************** END INSTRUMENTATION ****************************
Hash code of CtClass: 65567135

BUILD SUCCESSFUL

Total time: 3.118 secs

My Gradle:
------------------------------------------------------------
Gradle 1.12
------------------------------------------------------------

Build time:   2014-04-29 09:24:31 UTC
Build number: none
Revision:     a831fa866d46cbee94e61a09af15f9dd95987421

Groovy:       1.8.6
Ant:          Apache Ant(TM) version 1.9.3 compiled on December 23 2013
Ivy:          2.2.0
JVM:          1.8.0_20 (Oracle Corporation 25.20-b23)
OS:           Linux 4.4.0-45-generic amd64

How can I reproduce your issue?

wait.. my Gradle is old, let me switch to 3.

I can reproduce this issue now, hang tight

I found the problem. In your example project, you are using the old version of ActiveJDBC.
Please, switch to latest SNAPSHOT:
 dependencies {
        classpath 'org.javalite:activejdbc:1.4.13-SNAPSHOT'
        classpath 'org.javalite:activejdbc-instrumentation:1.4.13-SNAPSHOT'
    }

See my output:
➜  igor 13:52:14 /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project git:(master) gradle -v

------------------------------------------------------------
Gradle 3.1
------------------------------------------------------------

Build time:   2016-09-19 10:53:53 UTC
Revision:     13f38ba699afd86d7cdc4ed8fd7dd3960c0b1f97

Groovy:       2.4.7
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_20 (Oracle Corporation 25.20-b23)
OS:           Linux 4.4.0-45-generic amd64

➜  igor 13:52:20 /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project git:(master) gradle instrumentModels
:compileJava
:processResources UP-TO-DATE
:classes
:instrumentModels
Thread name: Renamed daemon thread
Hash code of CtClass: 184078839
**************************** START INSTRUMENTATION ****************************
Directory: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main
Instrumented class: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main/frozen_model/SomeModel.class
**************************** END INSTRUMENTATION ****************************
Hash code of CtClass: 220996753

BUILD SUCCESSFUL

Total time: 0.673 secs
➜  igor 13:52:23 /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project git:(master) gradle instrumentModels
:compileJava
:processResources UP-TO-DATE
:classes
:instrumentModels
Thread name: Renamed daemon thread
Hash code of CtClass: 220996753
**************************** START INSTRUMENTATION ****************************
Directory: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main
Instrumented class: /home/igor/projects/javalite/activejdbc/activejdbc-gradle-plugin/sample-project/build/classes/main/frozen_model/SomeModel.class
**************************** END INSTRUMENTATION ****************************
Hash code of CtClass:<PHONE_NUMBER>

BUILD SUCCESSFUL

Total time: 0.655 secs

@ipolevoy Igor of course I do :) I found this problem in version 1.4.12 prepared test application, reported problem and created pull request with proposed fix. You've merged my pull request and then released new version 1.4.13 which should work fine.

@vkuzel haha,I confused myself. Glad it is working finally.


Could not bind to a valid ArcGIS installation

Hi,
I'm really excited to start using the R package.
I installed the arcgisbinding R package following the instructions using ArcCatalog, but when I run arc.check_product() it incorrectly yields "could not bind to a valid ArcGIS installation".
Also, the first time I tried loading the R package a dialogue appeared tell me that the MSVCP110.dll was missing. I installed it from here and then was able to successfully load the package.
Cheers,
Jeff
code
> library(arcgisbinding)
*** Please call arc.check_product() to  define a desktop license.
> arc.check_product()
Error in .call_proxy("arc_AoInitialize") :
  Could not bind to a valid ArcGIS installation

ArcGIS info from ArcGIS Administrator
DESKTOP

Installation Information
Product Name: ArcGIS 10.3 for Desktop
Release Version: 10.3
Product Version: <IP_ADDRESS>22
Installation Folder: C:\Program Files (x86)\ArcGIS\Desktop10.3\
Installed By: xxxx
Install Date: 6/05/2015
Install Time: 11:35:59
Install Image: C:\Users\xxxx\Documents\ArcGIS 10.3\Desktop\SetupFiles\
Current User: xxxx
Application Data Folder: C:\Users\xxx\AppData\Roaming
System Temporary Folder: C:\Users\xxxx\AppData\Local\Temp\

Service Pack Information
ArcGIS Service Pack: 0 (build 0)

License Manager Environment Variable Information
ARCGIS_LICENSE_FILE: N/A
LM_LICENSE_FILE: N/A

R session info
R version 3.2.1 (2015-06-18)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 7 x64 (build 7601) Service Pack 1

locale:
[1] LC_COLLATE=English_Australia.1252  LC_CTYPE=English_Australia.1252    LC_MONETARY=English_Australia.1252
[4] LC_NUMERIC=C   LC_TIME=English_Australia.1252

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] arcgisbinding_<IP_ADDRESS>

loaded via a namespace (and not attached):
[1] tools_3.2.1

Thanks for the report, we're also excited about this project.
From what I can tell, it looks like the ArcGIS installation that it's trying to connect to is 10.3.0 (build 4322). Unfortunately, this is a very new project, and requires ArcGIS 10.3.1 (build 4959), which was released in May. I'll look at the code tomorrow and see if we can add a more helpful error message for this issue than the current generic failure.
Thanks also for the report about the missing MSVC DLL file, I'll do some more testing on a bare machine to make sure we have better instructions.
Cheers,
Shaun

Please run Rgui.exe 32-bit or setup RStudio to use R (32-bit). To build and run GP tools please upgrade to ArcGIS 10.3.1

Thanks for getting back so quickly! I've contacted my IT department to upgrade ArcGIS. I'll report back once its finished.

can you use the R with <IP_ADDRESS>22  ? I installed the arcgisbinding R  successfully. But when I run the samples, no results was shown even the message said this was completed and succeeded.

@lishalongfa Unfortunately, the bridge requires ArcGIS 10.3.1 or later to work, as mentioned in the prerequisites.

The installation will now report that it requires 10.3.1 when trying to install on earlier versions (https://github.com/R-ArcGIS/r-bridge-install/commit/226b747d857414ca2e48c558614334644a32737b).

@paleo13 The issue with MSVCR has been resolved, the bridge now statically links to the needed Visual C++ Runtime, and these errors shouldn't crop up. We've also fixed the toolbox incorrectly installing on 10.3.0, since it can't be used there as a GP tool. However, as mentioned earlier in this thread, it can be used in standalone R by installing the arcgisbinding package directly into R.

I have ArcMap 10.3.1. Before attempting the bridge, I decided to update R to the latest version, which currently is: 3.2.4 Revised. I downloaded the zip from github, unpacked, and stored with the rest of my R libraries. When I tried to install I got the following warning and error messages:
>install.packages("arcgisbinding")
Warning in install.packages :
  package ‘arcgisbinding’ is not available (for R version 3.2.4 Revised)
> library(arcgisbinding)
*** Please call arc.check_product() to  define a desktop license.
> arc.check_product()
Error in .call_proxy("arc_AoInitialize") :
  Could not bind to a valid ArcGIS Pro installation

UPDATE
I had an older version of R installed on my computer, so I experimented switching to that version:
R version 3.2.2 (2015-08-14) -- "Fire Safety" Copyright (C) 2015 The R Foundation for Statistical Computing Platform: i386-w64-mingw32/i386 (32-bit)
This appeared to work:
`> library(arcgisbinding)
*** Please call arc.check_product() to  define a desktop license.

arc.check_product()
product: ArcGIS Desktop
license: Advanced
build number: <IP_ADDRESS>59
binding dll: rarcproxy `

Hello @priscole,
One of the idiosyncrasies of R is that it lets you install multiple versions -- even within the same minor release as you mention above. By default, when the bridge is installed, it'll try to connect to whatever version it finds. When you installed the second copy (3.2.4), ArcGIS is still configured to look at the 3.2.2 version. If you rerun the install tool, it should make the connection to the most recently installed version, and arcgisbinding will work in both 3.2.2 and 3.2.4. Assuming you don't need to keep 3.2.2 around, you may want to just remove it, then rerun the 'Install R Bindings' tool. As you found, you can just move around the package from the R side, but ArcGIS also has to know where to find the correct version of R -- running that script takes care of that step.
Lastly, that warning is harmless -- R packages are pretty much universally compatible within the same minor release, so while irksome to see that message, dplyr should work just fine under 3.2.2, if you want to keep using that version for working with ArcGIS.
Cheers,
Shaun

@priscole,
We've identified a bug in the detection logic that lives in Pro / 10.4 that specifically affects the 3.2.4 Revised release (typically, releases don't have a suffix, and are purely dot-separated numeric values). We've applied a fix to the installer that should resolve this issue in this case if you do want to use 3.2.4 Revised.

Thank you for your reply.
I've succeeded in installing R-bridge.
But there's another problem. So close this time.Still failed.

library(arcgisbinding)
*** Please call arc.check_product() to  define a desktop license.
arc.check_product()
Error in .call_proxy("arc_AoInitialize") :
Could not bind to a valid ArcGIS Pro installation

@CodeQL What version of ArcGIS are you trying to work with? If you have ArcGIS Desktop, you'll need to use the 32-bit version of R as shown in this diagram:
https://github.com/R-ArcGIS/r-bridge-install/blob/master/img/version-block-detailed.png
If you are using ArcGIS Pro, could you check that you're logged in correctly in the app, and if possible, send on what you see from the "About ArcGIS Pro > Licensing" screen.

Problem solved ,LOL. Much thanks.
I didn't notice that my ArcGIS desktop is 32 bit. I just clicked the  download button from arcgis.com website. Thougth it would choose the software version corresponding to my operating system WHICH is 64-bit.


node tests: Replace assert with assert.equal in dispatch.js.

Above change will result in the failing of the test, this is
becuase page_params.default_view was returning a value of 1
but value expected was all_messages. Simple fix was to change
value of setting to all_messages(which was 1 initially) in
update_display_settings__default_view_all_messages in event.js.
Fixes #18685.

Testing plan:
Ran tools/test-js-with-node.  All tests are passing successfully!

Hey @raghupalash,
Thanks for working on this!
It seems like you haven't properly set up your GitHub Account in your local environment.
You can configure it by running the following lines,
git config user.name "FIRST_NAME LAST_NAME"
git config user.email<EMAIL_ADDRESS>
Also, a better commit message would be node tests: Replace incorrect assert with assert.equal in dispatch.js.
And maybe a better description would be,
"This commit fixes the invalid assert call in dispatch.js and also fixes the
invalid settings parameter of update_display_settings__default_view_all_messages
fixture in event.js, it should be all_messages instead of 1."

Thanks for the suggestion @Riken-Shah! I have made the changes.

@raghupalash you need to use git commit --amend --reset-author on this commit to fix its commit metadata as well.

We have some more assert() calls that are incorrect in the same way:
frontend_tests/puppeteer_tests/settings.ts
173:    assert(common.get_text_from_selector(page, name_field_selector), "Bot 1");
--------------------------------------------------------------------------------
197:    assert(common.get_text_from_selector(page, name_field_selector), "Bot one");

The name has been updated:

@andersk I would love to try and work on them!


[put-file] Bug when uploading big datasets

Using v 1.4. When pushing a relatively big data-set (5Gb only)  to a repo with the recursive flag, the process fails. The executed command is the following:
pachctl put-file metabrepo master -c -r -f .  transport is closing
I tested it with a smaller subset with the same kind of files, and it worked.

+1

transport is closing normally indicates that the pachd process encountered an error or that there was some error with a connection such as a port-forward breaking. Unfortunately this might prove hard to diagnose without logs from pachd from when the error happened. @jonandernovella has this error proven to be reproducible?

@jonandernovella could you describe your infrastructure?  Are you doing the put-file remotely or in the same cluster?  I've put many multi-GB files with no issues on AWS from within the cluster.

Ok, I was able to reproduce this @derekchiang and @jdoliner with 239Mb of images recursively uploading to a GKE cluster with Pachyderm 1.4.1.
➔ pachctl put-file training master -c -r -f .
transport is closing

I'm doing this remotely, so @derekchiang are you saying I should try from within the cluster?  Or maybe I upload to a bucket and then put-file from there?

I've tried a couple different things here as well.  I uploaded all my files to my object store, got URLs for each of the files, and tried to put-file with -i, thinking that would be better.  Also, I killed my port-forward and manually set ADDRESS, but still:
➔
➔ pachctl create-repo training
➔ pachctl put-file training master -c -i maps.txt
transport is closing
➔ pachctl list-repo
NAME                CREATED             SIZE
training            8 minutes ago       0 B
➔

So, I guess we can rule out port-forward?

Ok, now I tried this from an instance in the same region as my cluster (because there are some weird settings on the instances in my GKE cluster, and I couldn't quickly get pachctl up and running).  But, alas, the same:
dwhitena@put-file:~/maps/train$ pachctl create-repo training
dwhitena@put-file:~/maps/train$ pachctl put-file training master -c -r -f .
transport is closing

This seems to be related to the actual number of files and/or how long it takes to upload them.  The above attempt was with 1097 images.  If I take out a sample of around 200 images:
dwhitena@put-file:~/maps/train/sample$ pachctl put-file training master -c -r -f .
dwhitena@put-file:~/maps/train/sample$

Success!  So, this definitely seems to be reproducible as the number and/or size of the files increases.

@dwhitena @jonandernovella could you guys try using a lower parallelism, like -p 10?  The default is 100 and I wonder if that's too much.

@dwhitena @derekchiang yes, that definitely works.

@jonandernovella Great.  We will lower the default parallelism to 10 in the next release.


feat: add Nix flake with devenv

Could you add a target for building a docker image for Laskugeneraattori with the Nix dockerTools?
We could also enable the devenv DevContainers support and include the generated .devcontainer.json.
Also a GitHub-action would be nice


Aggregate only return the first element

Hi
When I execute the aggregate function after groupBy(), it only return the first number. How I get all the results.
Here is my code

Uv::whereBetween('vt', [$startTime, $endTime])
>groupBy('vti')
->aggregate('sum', ['v']);

same question , @sagargulati  did you solve this ?


AutoMap() is now aware of overridden properties in derived types

Previously, AutoMap() would not take into account properties that
have been overridden in derived classes:
public class A
{
    public int Foo { get; set; }
}

public class B : A
{
    public new string Foo { get; set; }
}

So in this instance, mapping class B would result in Foo being mapped
as an int, even though it has been overridden as a string using the new
keyword.
With this commit, AutoMap() is now aware of overridden properties and
in this example, will map Foo as a string.
Closes #2566

Merged to master and 5.x, ported to 2.x


Up go compiler version and fix dependabot alert

 Fix audit and up go compiler version in dp-file-downloader


URI improvements

Respect "amqps://" in the URI and use the default protocol ports (5672 and 5671) if no port is supplied in the URI

:+1: We spent quite a while trying to puzzle out why Hutch was failing to parse certain amqp: URLs. Thank you a lot for this patch!

Thank you, some (mock-based) tests need updating, I'll take care of that.

I'm running into obscure github issues at the moment when trying to push, will contact support and push in the next few days.


Add request to recalculate quota in add_quota_avu command

@mjstealey @hyi @phuongdm This change is necessary to initialize MSI-based quota calculation in iRODS.
The script add_quota_avu must be repeated even if AVUs are valid. An extra clause invokes the quota calculation.

@alvacouch, @hyi, @phuongdm - Where does this stand?
We plan to deploy 1.11.0 shortly, and this is not in it yet...

@mjstealey I suggest to go ahead with 1.11.0 deploy without waiting for this one. Quota is not enforced anyway in 1.11.0, so there will be no impact to this real-time quota update work by @alvacouch and @phuongdm. We can aim at getting their work integrated for 1.12 later.

Quota is not enforced anyway in 1.11.0, so there will be no impact to this real-time quota update work by @alvacouch and @phuongdm. We can aim at getting their work integrated for 1.12 later.

Works for me

@mjstealey @hyi It would be nice if this and phuoung's code got stress tested in 1.11. I do not have the time to push for it.

With 1.11.0 being deployed on 7/19, we've update the base of this PR to be the develop branch

It would be nice if this and phuoung's code got stress tested in 1.11. I do not have the time to push for it.

This can be an ad-hoc fix to master if need be, but should otherwise be able to be tested in a development environment. We also have a parallel www VM coming online soon that this could be applied to. Details forthcoming.

@alvacouch There are conflicts that need to be resolved. I think after the conflicts are resolved, there should be only one file change to the add_quota_avu management command. I am OK with your changes based on our discussion on google doc, so +1 from me once you resolve conflicts and make sure there is only a few line changes to that single management command.

There are conflicts that need to be resolved

PR #2232 had similar conflicts that were resolved by rebasing with the develop branch. This work was initially based r-c-1.11.0, but was changed to develop once 1.11.0 was deployed.

@alvacouch Let's hold off for this since this will most likely not needed after I understand more on @phuongdm 's microservice approach. The resetQuotaDir can be done directly by running a rule initially rather than adding a AVU, then deleting it. Anyway, I don't think this should go in before the microservice approach is finalized.

@hyi Can you, again, review this now-very-small PR? Is it safe to merge? Beneficial?

Thanks @hyi
@alvacouch Please merge when ready.


prevent loading of illegal modules in the browser

Closes #6700. Closes #7288. Right now, we prevent people from importing illegal modules ($env/[type]/private, $lib/server/** and **/*.server.{ext}) by analysing the module graph during SSR. This is a flawed approach for a variety of reasons:

It doesn't account for systems like telefunc, which transform modules differently between SSR and non-SSR modes such that the dangerous import declarations are removed
it means you only get the error when you hit a page directly, not when you soft-navigate to a page. (I was surprised to realise that this morning!)
it applies even to pages that have csr = false

A much simpler approach is to simply prevent the modules in question from being imported in the browser at dev time. We can do this by adding a guard in a load hook that throws if the relevant conditions are met. (At build time we keep the existing graph analysis.)
There's a couple of minor drawbacks: we don't get the import chain, just the module ID, and the error overlay is dismissable. I think these trade-offs are well worth it.
A nice bonus is that we can get rid of the code for traversing the Vite module graph. Since we now only need to worry about the Rollup module graph, this also means we can get rid of a layer of indirection (sorry @tcc-sejohnson, it was good code! but no longer needed). That part is a WIP.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

As long as we're retaining the same graph analysis in build as we were before I see no problem with this -- I wanted to do this when we originally implemented the feature, but just couldn't figure out how. Please ping me when this is ready-er for merge -- happy to review 😁

Ok I think this is ready now, marking it as such and crossing my fingers that the tests pass. One wrinkle: if the Vite error overlay appears before hydration, it will get nuked if %sveltekit.body% isn't wrapped in an element below the <body>, so I had to make that change to the test app.
I almost wonder if we should enforce that, since it's a bit of a footgun otherwise.
@tcc-sejohnson would be grateful if you do get a chance to review! The build stuff should be basically identical

One wrinkle: if the Vite error overlay appears before hydration, it will get nuked if %sveltekit.body% isn't wrapped in an element below the , so I had to make that change to the test app.

Anecdotally, I've seen a good number of people in the Discord that remove the div wrapper for "easier" styling, so... might be a good idea to try to find a way.

alright, things finally seem to be working again. @tcc-sejohnson if you have the bandwidth to take another look since you requested changes, that would be great — looking forward to getting this one merged 🙏

Anecdotally, I've seen a good number of people in the Discord that remove the div wrapper for "easier" styling, so... might be a good idea to try to find a way.

@tcc-sejohnson I in one project added to this div a style="display: contents;", and it was enough for me.
I don't know if that can cause a problem, but I haven't noticed any.

Anecdotally, I've seen a good number of people in the Discord that remove the div wrapper for "easier" styling, so... might be a good idea to try to find a way.

@tcc-sejohnson I in one project added to this div a style="display: contents;", and it was enough for me.
I don't know if that can cause a problem, but I haven't noticed any.

That won't work for everyone. To be clear, I don't think there's really any logical reason to remove the wrapper div -- it's easy enough to set it up however you want to -- but some people do it and we don't want to break their apps if possible 😁

That won't work for everyone. To be clear, I don't think there's really any logical reason to remove the wrapper div -- it's easy enough to set it up however you want to -- but some people do it and we don't want to break their apps if possible 😁

I am one of those removing the wrapper div, so maybe shedding some insights on that 🙂
The simple reason is that this div servers no purpose whatsoever in the final product, and it makes styling harder to a degree (you always have to remember that the body of your page is not body for the css).
As far as I understand this div is a crutch for shortcoming of a tool used in development only and imho that is enough reason to try to find a way to make things work without, because utilities meant for development have no place in a production build.

besides potentially stopping hydration from removing extensions there injected markup

this is the key — we've had multiple reports of exactly this sort of thing happening. it's very much not about preventing dev-time issues — it's the sort of bug that's likely to manifest in deeply confusing ways in production and that you'll be lucky to even find out about. we added a note to the docs...

...but i'm not sure that's enough, because people will always look at it and assume they can safely remove it. my personal inclination is to require %sveltekit.body% to be inside an element other than <body>, but i'm going to open a discussion to see how large a trade-off that would be

https://github.com/sveltejs/kit/discussions/7585


feat(test): first block tests

Some testing for blocks including a sample for table-of-content

Should we add coverage?

Sure but let's do that in a dedicated issue.


How to add Treat as an alias option?

Hi,
How do I get the below command to also tick "Treat as an alias" option when adding send as?
gam user<EMAIL_ADDRESS>sendas<EMAIL_ADDRESS>"xxx"
Thanks
Az

Please post "how to" questions to the discussion group:
https://groups.google.com/forum/#!forum/google-apps-manager


Fix month query for some mariadb

A user reported not seeing their shifts in the calendar view. We debugged it together - turns out their mysql server was not giving back the shifts with the __month query. This PR replaces it with a datetime query which did resolve the issue for them.

coverage: 89.144% (+0.002%) from 89.142% when pulling 01b55d5d29022aa5c8ea5758b85b460e4a7dea63 on fix-mariadb-month-query into d27b323d6149dbe1f42e73a264eb10e53ca40bd0 on main.


test case failed while using external project in cmake

Describe the bug
i have an application which uses cmake to build the container. I wanted to integrate aws sdk into it, so i used externalproject in cmakelists.
include(ExternalProject)
ExternalProject_Add(libawscpp-download
GIT_REPOSITORY    https://github.com/aws/aws-sdk-cpp.git
GIT_TAG           1.8.17
LIST_SEPARATOR    "|"
CMAKE_ARGS        -DBUILD_ONLY=s3
)
but some test cases are failing
Expected Behavior
should have run successfully
Current Behavior
failing
/tmp/meeting-sdk-linux-sample/build/libawscpp-download-prefix/src/libawscpp-download-build/.deps/build/src/AwsCCommon/tests/byte_buf_test.c:236:35: error: 'arr' may be used uninitialized [-Werror=maybe-uninitialized]
zoomsdk-build  |   236 |     struct aws_byte_buf src_buf = aws_byte_buf_from_empty_array(arr, sizeof(arr));
zoomsdk-build  |       |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
zoomsdk-build  | In file included from /tmp/meeting-sdk-linux-sample/build/libawscpp-download-prefix/src/libawscpp-download-build/.deps/build/src/AwsCCommon/tests/byte_buf_test.c:16:
zoomsdk-build  | /tmp/meeting-sdk-linux-sample/build/libawscpp-download-prefix/src/libawscpp-download-build/.deps/build/src/AwsCCommon/include/aws/common/byte_buf.h:507:36: note: by argument 1 of type 'const void *' to 'aws_byte_buf_from_empty_array' declared here
zoomsdk-build  |   507 | AWS_COMMON_API struct aws_byte_buf aws_byte_buf_from_empty_array(const void *bytes, size_t capacity);
zoomsdk-build  |       |                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
zoomsdk-build  | /tmp/meeting-sdk-linux-sample/build/libawscpp-download-prefix/src/libawscpp-download-build/.deps/build/src/AwsCCommon/tests/byte_buf_test.c:235:13: note: 'arr' declared here
zoomsdk-build  |   235 |     uint8_t arr[16];
zoomsdk-build  |       |             ^~~
Reproduction Steps
just create a dummy app in c++ with cmake create container and add the abover externalProjects...
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.8.17
Compiler and Version used
11.4.0
Operating System and version
platform=linux/amd64 ubuntu:22.04

GIT_TAG 1.8.17

thats a rather old tag that references an equally as old commit in the common runtime which appears to have a warning in tests. neither of those versions will be updated with any fixes. Is there a reason you cannot use the latest version?


Release

Codecov Report
Base: 28.53% // Head: 28.53% // No change to project coverage :thumbsup:

Coverage data is based on head (7810bdb) compared to base (778424e).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #435   +/-   ##
=======================================
  Coverage   28.53%   28.53%
=======================================
  Files          54       54
  Lines        4921     4921
=======================================
  Hits         1404     1404
  Misses       3385     3385
  Partials      132      132

Flag
Coverage Δ

unittests
28.53% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Uint64 support

Hi there, thanks for the library, there's surprisingly few resources for reading parquet into Postgres. I was just trying it out and noticed Uint64 is not supported. I have never written rust but unless there is some blocker I imagine I could adapt the Uint32 code easily enough. Unless there is a reason Uint64 is not supported?

I don't think there's a reason, Postgres' BigInt is an 8 byte integer so a u64 should fit in there. A PR is welcome if you want to try some Rust, it should be easish by just copying the existing encoders / enum matches :)

Ah no it would have to be a NUMERIC, hence why I didn’t add support. This requires a bit more research to understand Postgres’s NUMERIC type

Ah, I see. I too didn't realize postgres lacks a u64 type. NUMERIC has performance downsides and isn't really an integer type.
What about a workaround where the user can optionally indicate a target postgres type for uint64 columns? The default behaviour would be the same (failure), but if the user passes this new optional argument, then it is on them to ensure that their integers will not overflow the target type.
The scenario this addresses is: the user has a large set of parquet files that uint64 columns, but the actual values in those columns could fit into int64 (or uint32). With the current version of pgpq, the user would have to completely regenerate all of the existing parquet files to use this library. Thoughts?

The scenario this addresses is: the user has a large set of parquet files that uint64 columns, but the actual values in those columns could fit into int64 (or uint32). With the current version of pgpq, the user would have to completely regenerate all of the existing parquet files to use this library. Thoughts?

I think they should regenerate them on the fly. pgpq accepts arrow datasets as inputs, there are tools and APIS to apply a transform to an arrow dataset as it gets read. In other words, why put that functionality into pgpq when it already exists in pyarrow and polars.

In other words, stream the dataset and transform each RecordBatch before passing it to pgpq.  Polars might be able to one shot this (apply the transform using their LazyFrame and then convert that to an Arrow Dataset)

Good point, I didn't consider the fact that you stream the data into pyarrow tables in python anyway, so the transformation is easy enough to apply at that point!

Glad that works for your use case! Please close the issue if you feel it’s been resolved.


Scale issues due to envoy polling manager for config every 1s

Istio does not scale with current design because all envoy instances poll istio-manager for config every 1s.

Please see https://github.com/istio/manager/issues/292 for additional discussion on scaling the discovery service.
Short term plan is some combination of tweaking Envoy's RefreshDelayMs, increasing number of istio-manager replicas, and optimizing SDS/CDS/RDS response generation (see https://github.com/istio/manager/pull/455).
Long term plan is to investigate the use of gRPC streaming API for SDS/CDS/RDS. I'm tracking that issue here.

Will track this issue using #292, as long as I can edit 292's title.


Utf8Decoder+JsonDecoder usage with TransportWebSocketLink

Noticed that HttpLink got migrated to Utf8Decoder +JsonDecoder. Could we get similar improvements in TransportWebSocketLink here? I would love to see the example usage of the new approach with TransportWebSocketLink.

Hi!
It looks like this is impossible without changing the implementation of Dart SDKs Websocket or providing another implementation for web_socket_channel.
The underlying WebSocket already decodes the bytes to a String:
https://github.com/dart-lang/sdk/blob/8a7cde38b204b40d7954de85d5fa4be1abd952b3/sdk/lib/_http/websocket_impl.dart#L332
So there's no opportunity to decode both utf8 + json in one go.


Model Size

Hi,
i really appreciate the work you have done. I have a concern regarding model size. I am getting model size around 300 mb which we cannot use for web and mobile app. Kindly suggest me something to reduce the model size.

Hello,
Thank you for your message.
First, you could try to reduce the number of parameters in the model, reducing number of layers and the depth of the model, especially in the VGG part.
Or you could reduce the size of the images you use as inputs, going from 512x512 to 256x256 or even lower will usually decrease the size of the model.
Finally, you can reduce the numbers of anchor boxes in the model.

Thank you so much @ppontisso . i will try.

one more doubt is there, in model layers, you are using lambda as one layer just after input. Why are you using that? can't we train without that?
# Define functions for the Lambda layers below.
############################################################################

def identity_layer(tensor):
    return tensor

def input_mean_normalization(tensor):
    return tensor - np.array(subtract_mean)

def input_stddev_normalization(tensor):
    return tensor / np.array(divide_by_stddev)

############################################################################
# Build the network.
############################################################################

x = Input(shape=(img_height, img_width, img_channels))

# The following identity layer is only needed so that the subsequent lambda layers can be optional.
x1 = Lambda(identity_layer, output_shape=(img_height, img_width, img_channels), name='identity_layer')(x)
if not (subtract_mean is None):
    x1 = Lambda(input_mean_normalization, output_shape=(img_height, img_width, img_channels), name='input_mean_normalization')(x1)
if not (divide_by_stddev is None):
    x1 = Lambda(input_stddev_normalization, output_shape=(img_height, img_width, img_channels), name='input_stddev_normalization')(x1)

Yes, you can train a model without the lambda layers . The identity layer is just here to make the use of the other lambda layers optional.

Is it possible if I want train for some other object (body parts)? I tried to remove some layers but still model size is 334 mb.


chore(Algebra/Data/Order/Floor): remove todo on `fract_div_intCast_eq…

…_div_intCast_mod`
There are no plans to implement this, because of there are no plans to add more API for Int.fmod.

See discussion here:
https://leanprover.zulipchat.com/#narrow/channel/217875-Is-there-code-for-X.3F/topic/basic.20facts.20for.20.60fmod.60.20for.20negative.20second.20argument

Is there a Zulip discussion that can be linked? Thanks!
bors d+

Is there a Zulip discussion that can be linked? Thanks!
bors d+

Yes, as linked in the first comment here. I added the link also in the pr description now.
Hope this was the idea.
bors r+


Use uniform naming (Nmstate/nmstate)

@tyll , will we change this to nmstate all over? Because it is a name, using it once with a capital and once without does not fit well IMO.
We got one Tech.Writer supporting this.

I am not convinced that everything as lower-case is the best way to go. IMHO always Nmstate (when it is the project name and not a technical artifact such as tarballs etc) is easier to read.

@EdDev I changed it to use Nmstate now

@EdDev this is also ready for review

@EdDev requested to use NMState instead of Nmstate. @cathay4t do you have a favorite spelling?

@tyll Nmstate +1


Latest Image is not working on for mac M1 Chip

Getting Following Error while running on Preview Docker for M1 Chip.Could Anyone know how to fix it.
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

My problem is that i can't access to localhost:8080.

Same here I can't access localhost:8080 seems my web server is keep on restarting. But my celery flower is up at 5555. Need assistance.

same issue, + python is constantly dying


No longer a Default scope

[Enter feedback here]

The screen doesn't reference a default and looks like the following:

The "API.Access" is at the end of the Scopes URL
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 520b9821-ecef-20af-a601-ea36c4297d88
Version Independent ID: da9c8ac9-4d7a-4b40-56a2-a4bfe7083567
Content: Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory B2C
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @StevenTCramer ... The word "default"  refers to what will be the app's default scope. However, it isn't necessary there. It can just say "Scope;" therefore, I'll remove the word "Default" to remove any confusion. Thanks for the feedback.


update required dbt version to allow v0.19.0

Same as an issue I raised in the stripe package here.
If the requirements could be updated to allow dbt v0.19 that'd be great.

Hey @MarkMacArdle! We're working on pushing some pretty big changes to this package, including this compatibility. I expect we'll be releasing a new version of this package in the next few days.
Until that happens, can you run dbt using the following: dbt run --no-version-check?

Fixed with release v0.2.0!


ryujinx: 1.1.1239 -> 1.1.1242

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ryujinx is: Experimental Nintendo Switch Emulator written in C#
meta.homepage for ryujinx is: https://ryujinx.org/
meta.changelog for ryujinx is: https://github.com/Ryujinx/Ryujinx/wiki/Changelog
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1242 with grep in /nix/store/nbq5g4rj92ca1dldq1fzspilapgi69aw-ryujinx-1.1.1242
found 1.1.1242 in filename of file in /nix/store/nbq5g4rj92ca1dldq1fzspilapgi69aw-ryujinx-1.1.1242

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ryujinx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nbq5g4rj92ca1dldq1fzspilapgi69aw-ryujinx-1.1.1242 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ryujinx https://github.com/r-ryantm/nixpkgs/archive/730e570c2990dcd722936aaa6c986ff8335364d2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/730e570c2990dcd722936aaa6c986ff8335364d2#ryujinx

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nbq5g4rj92ca1dldq1fzspilapgi69aw-ryujinx-1.1.1242
ls -la /nix/store/nbq5g4rj92ca1dldq1fzspilapgi69aw-ryujinx-1.1.1242/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

ryujinx

Maintainer pings
cc @IvarWithoutBones @06kellyjac @artemist for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


Dual SIM Phone Send SMS

Incase the device has dual sim, how can we specify from which number the sms should be sent from?

It is currently sent from the primary SIM card.

I am also getting tha same issue. Please help anyone.

I am also getting tha same issue. Please help anyone.

Can you elaborate your issue?

I am also getting tha same issue. Please help anyone.

Can you elaborate your issue?

I am using react-native-direct-send-sms library in order to send sms . Once use the method to send the sms to the target number then by default it sends the message from primary slot i.e 0 slot . I want that once it sends the message at that time it should ask which sim you want to send message.


Can not build rust-secp256k1 inside CosmWasm contracts

Hello, as described here https://github.com/rust-bitcoin/rust-secp256k1/issues/748#issuecomment-2405121373, it seems that the rust-secp256k1 library can not be built using rust-optimizer when in WASM context.
The library should support running in WASM context, but I am not quite sure where the error could reside...

Hi, the rust-secp256k1 library uses a C library under the hood, which seems not well supported for the wasm target. Does the crate claim to work for the wasm target?
Does it work if you just build using cargo build --target wasm32-unknown-unknown?

Also: Do you have this problem because it's somewhere in your dependency or do you want to use the crate directly?
Because if you just need secp256k1, then you can use the corresponding APIs we provide: https://docs.rs/cosmwasm-std/2.1.4/cosmwasm_std/trait.Api.html#tymethod.secp256k1_verify

Unfortunately it is somewhere in the dependency tree... The library should support other wasm targets, I will have to check exactly what the problem is here.

While looking at their repo, it looks like they only support wasm32-wasi, not wasm32-unknown-unknown (which is what CosmWasm contracts use), so I'll close here, since it's not an optimizer issue.


clean up the root scripts folder

Is there an existing issue for the feature?

[X] I have searched the existing feature requests

Describe the Feature
why is this not empty yet
How Does The Feature Add To The Game?
someone is having fps issues because of this, dont know how
Additional Context
No response

done/unnecessary 24c8c241bd853283b73a8f9d4db6ef15d990699e


Problem with MNC masking of ice shelves

I'm writing to report a small bug in the MNC masking option (useMissingValue in data.diagnostics). When I switch this option on, ice shelf diagnostics (SHIfwFlx, SHIhtFlx, SHIuStar) are incorrectly masked. The entire ice shelf is masked out, with only the open ocean (where these variables are zero) unmasked.
In diagnostics_mnc_out (see code snippet below), it looks like maskC is applied at klev=1, since the ice shelf variables have already been compressed into a 2D array. But in fact this 2D array represents all different values of klev, none of which are 1 beneath the ice shelf.
https://github.com/MITgcm/MITgcm/blob/94b17183c0ace4ea15e0918244963a04ebd646be/pkg/diagnostics/diagnostics_mnc_out.F#L355-L374

As an esthetically un-pleasing solution one could be an extra treatment for pkg/shelfice-fields, like this:
#ifdef ALLOW_SHELFICE
            IF ( useSHELFICE .AND. (nlevels(listId).EQ.1
     &            .OR.fflags(listId)(2:2).EQ.'I') ) THEN
             DO k = 1,Nr
              DO j = 1-OLy,sNy+OLy
               DO i = 1-OLx,sNx+OLx
                kLev = MAX(kTopC(I,J,bi,bj),1)
                IF ( maskC(i,j,klev,bi,bj) .EQ. 0. )
    &                qtmp(i,j,1,bi,bj) = misValLoc
               ENDDO
              ENDDO
             ENDDO
            ELSE
#else
            IF (.TRUE.) THEN
#endif
            DO k = 1,nLevOutp
             klev = NINT(levs(k,listId))
             IF ( fflags(listId)(2:2).EQ.'I' ) kLev = 1
             DO j = 1-OLy,sNy+OLy
              DO i = 1-OLx,sNx+OLx
               IF ( maskC(i,j,klev,bi,bj) .EQ. 0. )
    &                qtmp(i,j,k,bi,bj) = misValLoc
              ENDDO
             ENDDO
            ENDDO
C     endif useShelfice
            ENDIF

I am not quite sure how to determine unambiguously in pkg/diagnostics-style how many levels are written. This solution would also require including SHELFICE.h, which I don't really like too much. Instead one could use kSurfC and catch all of the Nr+1 values.

I have the impression that this masking problem could show up also in other cases, e.g., in
ocean with pressure coordinate (both for surface diags and 3-D vertically integrated diags) and also
in atmospheric set-up with orography. I would suggest to change/fix the code in a more robust way
that works for all cases (for instance, testing also for kSurfC and kdiag).

@jm-c so you are suggesting something like this:
             IF ( kdiag(listId) .EQ. 1 ) THEN
C     or     IF ( kdiag(listId) .NE. Nr ) THEN
              DO j = 1-OLy,sNy+OLy
               DO i = 1-OLx,sNx+OLx
                IF ( maskInC(i,j,bi,bj) .EQ. 0. )
     &               qtmp(i,j,1,bi,bj) = misValLoc
               ENDDO
              ENDDO
             ELSE
              DO k = 1,nLevOutp
               klev = NINT(levs(k,listId))
               IF ( fflags(listId)(2:2).EQ.'I' ) kLev = 1
               DO j = 1-OLy,sNy+OLy
                DO i = 1-OLx,sNx+OLx
                 IF ( maskC(i,j,klev,bi,bj) .EQ. 0. )
     &                qtmp(i,j,k,bi,bj) = misValLoc
                ENDDO
               ENDDO
              ENDDO
             ENDIF

Where do we need kSurfC?

@edoddridge is curious on whether this is fixable?


Attribution is rotated along with the map

Fixed in https://github.com/fleaflet/flutter_map/pull/1262, will need to be updated after moving to flutter_map 1.1.0.

Done in 0.5.