ubuntu 18.04 compilation failed

Hello,
I tried to compile DXVK on Ubuntu 18.04 and I obtain several errors:
$ sudo apt install mingw-w64 libvulkan-dev
$ git clone https://github.com/doitsujin/dxvk.git
$ cd dxvk
$ ./package-release.sh master test --no-package

I obtain my first error message:
Program glslangValidator found: NO

meson.build:48:0: ERROR: Program(s) ['glslangValidator'] not found or not executable

I searched on Ubuntu wich package contains 'glslangValidator' to install it and I found no one.
I searched on my hard disk if I already have a file named 'glslangValidator':
$ locate 'glslangValidator'
.../rpcs3/rpcs3/Vulkan/glslang/Test/glslangValidator
.../mame/3rdparty/bgfx/3rdparty/glslang/Test/glslangValidator
.../RetroArch/deps/glslang/glslang/Test/glslangValidator

I copied the glslangValidator from Retroarch to dxvk git root folder, launch again the compilation, this first error gone but I obtained a new one:
...
../../../src/util/com/../../d3d11/../dxvk/dxvk_device.h: In member function ‘void dxvk::DxvkDevice::unlockSubmission()’:
../../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:348:7: error: ‘m_submissionLock’ was not declared in this scope
       m_submissionLock.unlock();
       ^~~~~~~~~~~~~~~~
../../../src/util/com/../../d3d11/../dxvk/dxvk_device.h:348:7: note: suggested alternative: ‘m_submissionQueue’
       m_submissionLock.unlock();
       ^~~~~~~~~~~~~~~~
       m_submissionQueue
ninja: build stopped: subcommand failed.

Thank you for your help.

I join you the full log.
dxvk_compilation.log

https://github.com/doitsujin/dxvk#troubleshooting

@legluondunet dxvk builds on 18.04 with the mingw fix that @doitsujin linked.
I also use VulkanSDK <IP_ADDRESS> for my glslangValidator tho.

I made some progress:

I set POSIX alternatives for x86_64-w64-mingw32-gcc and x86_64-w64-mingw32-g++
compiled GlslangValidator from Vulkan SDK
copied it in the root git dxvk folder
launched the compilation script "./package-release.sh master test --no-package"

I obtained a half success: dxvk library in 64 bits format compiled OK, but not the 32 bits ones.
I joined you the compilation log result.
Do you have a suggestion about this issue?
dxvk_compilation2.log

This is the exact same issue as you were having earlier, you only switched the 64 bit mingw to the posix alternative, now you need to switch the 32 bit mingw.  Also, all the problems you are having are setup problems resulting from a failure to read the README and wiki pages, this kind of problem is not suitable for the bug tracker IMHO.

You are right Guy, it is not a bug. I did read the readme and wiki but it is not enough explained. I'll continue to ask help to the forum. Thanks anyway.

@legluondunet The README lists (use i686 for 32-bit): :) So, yeah, it was not detailed enough to explain that you need to do both i guess.
You should also follow the VulkanSDK info, and look at the script included in the SDK. This explains how to set up your .profile file (your user profile), so that the libraries from the VulkanSDK is used (instead of copying stuff into the dxvk folder)

In fact I already choosed the two POSIX alternatives, like I explained in my last post. But  it works only for 64 bits library. I surely missed something.

$ sudo update-alternatives --config x86_64-w64-mingw32-gcc
[sudo] Mot de passe de legluondunet :
Il existe 2 choix pour l'alternative x86_64-w64-mingw32-gcc (qui fournit /usr/bin/x86_64-w64-mingw32-gcc).

  Sélection   Chemin                                 Priorité  État
------------------------------------------------------------
  0            /usr/bin/x86_64-w64-mingw32-gcc-win32   60        mode automatique
* 1            /usr/bin/x86_64-w64-mingw32-gcc-posix   30        mode manuel
  2            /usr/bin/x86_64-w64-mingw32-gcc-win32   60        mode manuel

and
$ sudo update-alternatives --config x86_64-w64-mingw32-g++
Il existe 2 choix pour l'alternative x86_64-w64-mingw32-g++ (qui fournit /usr/bin/x86_64-w64-mingw32-g++).

  Sélection   Chemin                                 Priorité  État
------------------------------------------------------------
  0            /usr/bin/x86_64-w64-mingw32-g++-win32   60        mode automatique
* 1            /usr/bin/x86_64-w64-mingw32-g++-posix   30        mode manuel
  2            /usr/bin/x86_64-w64-mingw32-g++-win32   60        mode manuel

@legluondunet
That is NOT for 32-bit.. it is for gcc and g++ (two compilers). The 32 bit is:
sudo update-alternatives --config i686-w64-mingw32-gcc
and
sudo update-alternatives --config i686-w64-mingw32-g++
If you type: sudo update-alternatives --get-selections|grep mingw32
it should list:
i686-w64-mingw32-g++  manual  /usr/bin/i686-w64-mingw32-g++-posix
i686-w64-mingw32-gcc  manual  /usr/bin/i686-w64-mingw32-gcc-posix
x86_64-w64-mingw32-g++  manual  /usr/bin/x86_64-w64-mingw32-g++-posix
x86_64-w64-mingw32-gcc  manual  /usr/bin/x86_64-w64-mingw32-gcc-posix

Finally it's compiled. Thank you very much SveSop!

Just a question to clarify because the readme actually has two commands at the end. I actually need 4 commands to set all those 4 mentined to posix?
sudo update-alternatives --config i686-w64-mingw32-g++
sudo update-alternatives --config i686-w64-mingw32-gcc
sudo update-alternatives --config x86_64-w64-mingw32-g++
sudo update-alternatives --config x86_64-w64-mingw32-gcc

One of them gave me a warning that some symlink can not created but my build went fine. Today I run them again and no warning anymore. Maybe even the order is important?

Hello nextgenthemes,
" I actually need 4 commands to set all those 4 mentioned to posix?" --> yes
"One of them gave me a warning that some symlink can not created but my build went fine. " --> doesn't matter
"Maybe even the order is important" --> no.

@doitsujin could  you add in the troubleshooting section this commands:
sudo update-alternatives --config i686-w64-mingw32-g++
sudo update-alternatives --config i686-w64-mingw32-gcc
sudo update-alternatives --config x86_64-w64-mingw32-g++
sudo update-alternatives --config x86_64-w64-mingw32-gcc
instead of the "(use i686 for 32-bit)" reference that a lot of people don't know what it is about?
I think you have to precise, in first step, that the libvulkan library have to be installed in 32 AND 64 bits:
sudo apt-get install libvulkan-dev libvulkan-dev:i386
That is not precised in the requierement.
VXDK is more and more popular and a more precise documentation will avoid a lot of issue.


The editDropdownOptionsArray cannot be a dynamic object

Basically we have a grid with a dropdown (column A in image) that will change values based on another dropdown's selection(column B in image).

However we noticed that the editDropdownOptionsArray property does a shallow copy when set to an object. If that object is later changed the grid still has the initial values.

I can't see anywhere in the code where there's a copy on the editDropdownOptionsArray, and I'm pretty sure that in my application I'm updating it.
But if you're doing this at a row level, the standard way to do that is to use the editDropdownOptionsPath, because that allows each row in the data to have a different set of dropdown options.  So if the first row has one value in column A, and the second row has a different value in column A, it will correctly give both rows different dropdowns in column B.

Closing: solution proposed that should resolve the issue, no further comments for 2 weeks, assuming solution has resolved issue.


Xterm registers too many keystrokes in Xiwi

Please paste the output of the following command here: sudo edit-chroot -all
name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version 1-20160715134041~master:0dc76a22
release: trusty
architecture: armhf
xmethod: xiwi
targets: xiwi
host: version 8172.60.0 (Official Build) stable-channel daisy
kernel: Linux localhost 3.8.11 #1 SMP Wed Jun 22 22:31:31 PDT 2016 armv7l armv7l armv7l GNU/Linux
freon: yes
Not unmounting /mnt/stateful_partition/crouton/chroots/trusty as another instance is using it.

Please describe your issue:
I am running xterm in a xiwi window under Ubuntu Trusty on Samsung ARM Chromebook.  I have noticed that frequently I will be typing and the terminal will respond as though I held down a key for a long time when I didn't.  E.g. trying to type 'mkdir' and it comes out as 'mkkkkkkkkkkkkkkkkkkkdir'
If known, describe the steps to reproduce the issue:
The issue is intermittent but frequent, haven't figured out how to consistently reproduce.

I guess that can happen if the system is under heavy load. Not sure what can be done...


Extract mocktesting package

To add tests around an upcoming feature (opt-in retention of Docker
volumes on test failure), I was going to need a third instance of a mock
*testing.T.
This extracts a more full-featured mock instance of *testing.T to be
used in existing and future tests that need to assert against
interactions with real tests.

Test-ception. ❤


Run performance tests on external multi-node clusters

If possible, we should publish both single node and multi node performance stats along with the system configuration.

[Triage] We do not have plan to work on multi node cluster performance tests for now.


Add support for package.json not at the root directory

I'm currently dealing with a repository where the package.json is not at the root directory. When I run npx version-changed, I get the following output:
Error: Command failed: git show HEAD:package.json
fatal: Path 'bindings/node/package.json' exists, but not 'package.json'.
Did you mean 'HEAD:bindings/node/package.json' aka 'HEAD:./package.json'?

Can this be changed to either use the relative path to package.json (git show HEAD:./package.json) or allow some sort of configuration to point to the package.json?

PR welcome :)


Fix upstream

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Hi @fbrehm, thanks for the PR. Can you explain what you are trying to fix and take a look at the failing travis jobs?

Hi Tim,
I have tried to apply the module to a host with a running MongoDB 2.6.12. Unfortunately after applying there two options in the /etc/mongod.conf, which are mutually exclusive or deprecated: 'sslMode = requireSSL' and 'sslOnNormalPorts = true'. Because of this the mongod service was complaining and was stopped.
After some research I found, that the Puppet module was using the wrong template, because the variable $version was not set. So I changed the file manifests/server/config.pp in this way to assign the custom fact 'mongodb_version' to $version, if $mongodb::server::version is not set or empty. Now the class was using the correct template 'mongodb/mongodb.conf.2.6.erb', and the mongod service was not complaining anymore and starting.
I have seen the errors in your Jenkins job, and I think, they were caused, because the custom fact 'mongodb_version' was not available during the tests. Because of the lack in the knowledge about writing and executing puppet and/or Ruby tests on my side, I don't know, how to work around. Some help would be very appreciated.
Cheers Frank

Made the changes - all tests seems to be okay

Thanks!

This breaks idempotency on setups and I want to revert this change. On the first run the fact is undef but on the second run it is defined causing a change in the rendered config (including a service restart).


regex_replace for replacing case insensitive strings not working

SO i have been using the custom regex_replace function to replace a substring within my actual string.
Here is how i am using it.
regexp_replace(col, pattern, replacement)
where col: is the column name where i am passing employee name: My name is Nitya
pattern: is what i am searching for: Nitya
replacement: what is to be replaced with: NS
The moment the col comes up with a value 'My name is nitya', it fails to replace the string. I have tried using lower on both sides, but the problem is the entire string in the col is converted to lowercase which is not what i want. Is this doable using regex_replace at all or there is another alternative to achieve this ?

I don't think I understand your problem. There does not seem to be anything named regex_replace related to Scala.js. Are you perhaps posting an issue in the wrong repository?

My query was related to spark scala

Then I'm afraid you're definitely in the wrong repo. This repo is about Scala.js, which has literally nothing to do with Spark.


How to set shortcut mod key to ctrl (ignoring left or right ctrl) ?

I've tried
--shortcut-mod lctrl | rctrl
--shortcut-mod lctrl rctrl
--shortcut-mod lctrl + rctrl

so far without luck. Is this possible?

scrcpy --shortcut-mod=lctrl,rctrl

https://github.com/Genymobile/scrcpy#shortcuts

Note that if you use Ctrl, then you won't be able to use the Android shortcuts (injecting Ctrl to the device to copy-paste or trigger other Android shortcuts).

I see it has to be a comma. Thanks.
Another thing, can ctrl+a (select all) be injected to Android?

Yes, it is by default (if you don't use Ctrl for scrcpy shortcuts). That's the reason why the shortcut modifier has been changes to Alt by default, so that default Android shortcuts could work.


github: hardcoded color variants

Is there an existing issue outlining your problem?

[X] I have searched the existing issues and they do not solve my problem.

What userstyles are you seeing the problem on?
lbl:github
Describe your problem.
In the github userstyle, there are lots of hard-coded variations of the catppuccin colors. These aren't as ideal, as it's unclear how they were mixed, and it's not very friendly towards customizing a flavor's colors yourself.
I think it'd be much better to use modifiers instead of hard coding things, using the lighten/darken/alpha sytax over the core colors.
Attach screenshots.
No response
What browser(s) are you seeing the problem on?
*
Any additional comments?
No response

It would be much better if this could be separated into a General theming userstyle which could be adapted to any colorscheme.


Profile is submitted as a contributor

Issue #, if available:
Description of changes: Profile is submitted as a contributor.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Welcome @JSGund !


Default value for jwt secret

If JWT_SECRET is null, you will get the message Lcobucci\JWT\Signer\Key\InMemory::plainText()
Description
Lcobucci\JWT\Signer\Key\InMemory::plainText() just accepts strings, but if JWT_SECRET is not set, it will be null. Therefore as default value an empty string was added.
Error occurs in:

https://github.com/PHP-Open-Source-Saver/jwt-auth/issues/116
https://github.com/PHP-Open-Source-Saver/jwt-auth/issues/111

Checklist:

[x] I've added tests for my changes or tests are not applicable
[ ] I've changed documentations or changes are not required

I'll take a look for us @eschricker :)

Closes #116

@mfn take a look too to we merge with 2 reviews :)

But this means the default secret for fresh installation will be an empty string? And it's valid/working secrets so if user forgot to change it, we've served a known secrets to new installation out of the box? 🤔

But this means the default secret for fresh installation will be an empty string? And it's valid/working secrets so if user forgot to change it, we've served a known secrets to new installation out of the box? thinking

Yes, you are totally rights. The empty string, is a valid secret and this would lead to security issues. Then this quick solution is not the way to go :)

I have rechecked the behaviour in one of our projects.
The error always occurs when the required information is missing:

symmetric algo (HS256, the default): JWT_SECRET is not set
asymmetric algo (RS256): JWT_PUBLIC_KEY, JWT_PRIVATE_KEY are not set

From my perspective this behaviour is totally fine. We could add an own exception and verify that JWT_SECRET or JWT_PUBLIC_KEY and JWT_PRIVATE_KEY needs to be set, to have a better error reporting.
What are your thoughts about it @mfn, @Messhias

a custom check / exception with a more clear message before it reaches the library sounds good to me 👍🏼

For me sounds good now, if the user forgets to fill the JWT or something like that, let it empty. By the way, we don't have users here, everyone is a programmer, forgot something like it's minimal reckless xD

Maybe for default installation is possible to insert on post-scripts in the composer to execute the command jwt:secret generate?

I was thinking about this; what I don't like are scripts automatically run.
But: there is already one manual step: "publishing" the config file
We could make a dedicated command like ./artisan jwt:init which:

publishes the config, if not present
This will also provide a nicer experience, because TBH, who remembers the syntax for publishing them??
generate at least a secret
Won't help when using asymmetric as you need to datums but let's start small

So let's create the command.

Due to the security concerns of an empty secret, I would prefer to close this PR and implement the suggested command in a fresh one.

Ack!


Itvr 340 bcsc fields

@vibhiquartech I took a look; this doesn't actually disable the application submission... Also, wouldn't this cause infinite renders if the token was indeed missing a field? What you probably want to do is just have a function that checks whether the token is missing fields (if the user is indeed bcsc), use that in both the main application form and the spouse application form, and if fields are indeed missing, disable the submit button and pass that information downstream to  as a prop so that the InfoTable renders an error message


most certificates have expired

valid from 2020/10/10 to 2021/10/10,
should update

valid expire again


permissions issue

I am not sure i have the correct permissions and im unable to tell exactly what the latest permission sets are so that i can enable and disable ss
I am using
- scoreboardstats.use
- scoreboardstats.hide

in my default permissions group and i still get errors
i am going off permissions based on this - https://github.com/games647/ScoreboardStats/blob/master/src/main/resources/plugin.yml
Thanks

Erros? Which ones?
scoreboardstats.use and scoreboardstats are assigned by default
In order to disable scoreboardstats with permissions, you need to give the user the negative permission.


⚠ ClamAV has degraded performance

In 761c780, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: ClamAV performance has improved in 5e5a967 after 5 minutes.


Support instance manager per thread in Gauge class

Allows to have CustomScreenshot implementation per thread

@ZhyliaievD can you tell us why you closed this PR?


m6-create-app-bring-source

@Hyperkid123 @ryelo This PR will contain text updates for the 3 side panels. Markdown syntax is the main concern here, I hope my humble experiments will be processed correctly in the panels.
Please, let me know if there's a way to check the screenshots without bothering you in every PR :)
Thank you.

Thanks so much for the preview tool @Hyperkid123, you're a magician, it helped me a lot to understand what syntax is supported.
What I was wondering about... Are there any ways to expand the syntax support? E.g. I couldn't add admonitions (or blockquotes to simulate admonitions), also blank lines are somewhat an issue (I tried 4 syntax options I found on stackoverflow, none could be processed).
My docs team is concerned a bit about Help panels looks, they could benefit a lot from some extra formatting/styling options (like blank lines for more white space, admonitions and some color) but I'm not sure we should hope for those... WDYT?
Thanks again!

What I was wondering about... Are there any ways to expand the syntax support? E.g. I couldn't add admonitions (or blockquotes to simulate admonitions), also blank lines are somewhat an issue (I tried 4 syntax options I found on stackoverflow, none could be processed).

@missmesss Unfortunately that is not something I can help you with. If you require the panel extension you will have to talk to the Patternfly team. I can only help with the storage and the platform UI integration.

@Hyperkid123 Thanks for letting me know, it makes sense. We'll figure out how to work around some things, thanks for helping out!

@Hyperkid123 The last 2 commits add all updates we hoped to publish for M6.
Please, feel free to merge if all looks good.
If some syntax (like quotes with >) break something in yaml, please, feel free to remove the greater-than signs (>) by yourself or let me know today or tomorrow, I'll remove them.
Thanks for keeping an eye on these PRs :)


Sin/Cos concatenation in Positional Embeddings

This is how the positional embeddings matrix is constructed in the code:
sinusoid_inp = torch.ger(pos_len,self.inv_freq)
pos_emb = torch.cat([sinusoid_inp.sin(), sinusoid_inp.cos()],dim=-1)

This basically creates a matrix of  [sin | cos] whereas the implementation in other papers including the original Attention is all you need had a positional embedding in which the sin and cos alternated between each other along the embedding dimension. Does this have anything to do with the relative positional embedding?
Thanks!

https://github.com/kimiyoung/transformer-xl/issues/8#issuecomment-455187360

For position embedding, the two columns are equivalent, simply because they are consumed by the matrix multiplication which is permutation-invariant.

https://github.com/kimiyoung/transformer-xl/issues/8#issuecomment-455187360

For position embedding, the two columns are equivalent, simply because they are consumed by the matrix multiplication which is permutation-invariant.


Improve price performance for 1000+ asset universes.

Improve performance for algorithms which consider and/or hold positions for 1000+ assets, especially liquid assets.
PERF: Use one field when getting the last traded dt.
Most often, when requesting the last_traded_dt, it is for retrieving the
forward filled price, which is based on the close column.
Instead of using volume to get the last_traded_dt, use the close. This
should particularly help workloads which are retrieving the price for many
assets, by reducing the number of I/O operations and making it less likely that
the desired close blocks stay in the page cache, since the volume and
close blocks would not be competing for space.
PERF: Optimize price for liquid assets.
When using price, the call to last_traded_dt for every value retrieved
became a noticeable bottleneck in algorithms which used over 1000 assets.
Instead of calling last_traded_dt before every retrieval of a close for the
price field, assume that close will retrieve a non-empty value, and then
forward fill if it is empty.
This change optimizes for the case of a tradeable universe which is predominately
composed of liquid assets.

@ehebert took a pass here. I think "use price instead of volume" change is trickier than expected, so I'd probably recommend splitting it out into a separate PR. For the "don't seek if we don't have to" change, it looks correct to me, but I think we could simplify the logic here quite a bit.

I agree, I'll remove that commit from this PR.

Coverage decreased (-0.07%) to 87.502% when pulling 484f8ac3c9146f98f77edb570f614aa10b63cb2f on improve-price-performance into 4002a03567b4952efb139ee022007bafb4efb157 on master.

LGTM


Fix warning "allowed unarchiving safe plist type 'NSString'..."

Proposed changes
Describe what this PR is trying to do.
Type of change

[ ] Feature work
[ ] Bug fix
[ ] Documentation
[x] Engineering change
[ ] Test
[ ] Logging/Telemetry

Risk

[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)

Additional information
Office reported seeing a lot of warnings when app is running, these warnings will be disallowed in the future:
https://identitydivision.visualstudio.com/Engineering/_workitems/edit/1843056
The repro in OneAuthTestApp:

I believe the changes could eliminate the warnings.

The partner also verified this change resolved the warning from their side.


Page with a slug of "/" causes a bug

Hi, when adding a new page and setting the slug as "/", it causes an issue with Settings > General > Homepage, and prevents this setting from being saved.
I realise now that if you want a page to be the home page (and appear as / ) then you still need to add a slug, and Batflat takes care of the rest nicely.
Perhaps prevent the user from setting "/" as the slug. When I entered this and saved the page, it blanks the slug but still seems to work.

Thanks for the report

Fixed


Diners club credit card not accepted

I have been trying to use my diners club credit card for many months now, but every time it shows that "This card network is not supported".
I checked various pages, documentation and others (1, 2, 3) and it is mentioned that Diners is accepted. But still I'm unable to use my card with Razorpay even though it works perfectly with other payment gateways.
Can someone please look into this issue and rectify it?

Hi @vivekpayasi could you please let us know which api you are using for payment or you are experiencing this issue while checkout ?

It is during checkout @ankitdas13, when I transact with merchants who use Razorpay's payment gateway.

Is this issue resolved?


Split form in several steps (different pages)

Describe the problem to be solved
Making a big form in a single page can be deterrent for respondents.
Describe the solution you would like
Many form solutions like Google Form provide multiple pages, presented as steps, to encourage users to fill the form despite having several questions.
Also these solutions may save the progress so the users can come back later to finish answering to the form.

A state of the art of the competitors may help designing this feature.


Attrib.Value is int for webgl and uint for opengl?

In attempting to cross-compile a program for both WebGL and Desktop OpenGL, I've noticed that the Attrib type is uint for the former, and int for the latter. This makes it a little hard to manipulate these in a portable way.
Is there a technical reason why these are different, or could they be brought into alignment?

Hi, thanks for reporting this.

This makes it a little hard to manipulate these in a portable way.

gl.Attrib should be an opaque type. You're likely to get one via gl.GetAttribLocation, then you can check if it's valid via its Valid method, and use it with `gl.EnableVertexAttribArray](https://godoc.org/github.com/goxjs/gl#EnableVertexAttribArray), [`gl.VertexAttribPointer`, etc.
Can you please elaborate on how you're trying to manipulate them?
That would help me better understand if there's a problem with some use-case I'm not aware of, or perhaps what you're doing can be done differently.
Thanks!

gl.BindAttribLocation is the unfortunate edge case here. It's idiomatic in modern OpenGL to explicitly bind attribute locations before program linking, to ensure that all shaders in your application use a consistent numbering for attributes.
For example, my current application does the following:
		gl.BindAttribLocation(program, gl.Attrib{0}, "position")
		gl.BindAttribLocation(program, gl.Attrib{1}, "normal")
		gl.BindAttribLocation(program, gl.Attrib{2}, "color")

To ensure that I can switch between multiple shaders without changing the vertex attribute pointers of my meshes.
This becomes especially important once we have support for Vertex Array Objects in WebGL 2.0, since then one bakes the vertex attribute pointers once at mesh creation, and never change them again.

Thanks, that's helpful. It sounds like you still need the ability to create ad-hoc gl.Attrib values and use them as indices.
The code you posted should work in a cross-platform compatible way. Can you show me some problem code where the different underlying types are causing problems? That way, I can see if a potential change would resolve your problem.
I'm guessing you're trying to extract/save/load the gl.Attrib.Value into a intoruint. I wonder if that can be worked around by using gl.Attrib` as your intermediate storage type. Seeing the problem code will be helpful.
After looking a bit more into the specs for OpenGL and WebGL, it looks like GLuint is used when attrib index is the input parameter, but GLint is used as return value from glGetAttribLocation. I might experiment with changing the gl.Attrib.Value type to uint and factoring it out to be common across all 3 implementations... But, I'll wait to see your problem code before making changes.

I've moved to passing around the gl.Attrib values directly, which works, but I'd love to be able to pass around the indices by themselves, to avoid exposing gl.* types in my own API.
As for the int/uint difference, glGetAttribLocation only returns int because it uses negative values to indicate errors. It should be entirely safe to cast the return value to uint after checking for errors (i.e. negative values).
I'll try and get some code up over the weekend to illustrate my usage a little more clearly. Thanks!

I've moved to passing around the gl.Attrib values directly, which works, but I'd love to be able to pass around the indices by themselves, to avoid exposing gl.* types in my own API.

I see.

As for the int/uint difference, glGetAttribLocation only returns int because it uses negative values to indicate errors. It should be entirely safe to cast the return value to uint after checking for errors (i.e. negative values).

Yep, that was the conclusion I came to as well. 👍 Hence it should be possible to use uint consistently. I'm willing to give it a shot on a branch, but want to do more thinking before deciding to merge to master.

I'll try and get some code up over the weekend to illustrate my usage a little more clearly.

All right. But no need to spend a lot of time on it, if you could just copy/paste the relevant lines, that'd be good enough. It doesn't need to be a fully standalone program, just a relevant snippet would do. Thanks.


Do we need representative media?

Edit view has a form to this; for scanned books and maps I think a thumbnail is fine.

I'm not clear on what the difference is.  Is it that thumbnail is an arbitrary image URL, but representative media would use a thumbnail image from a repository object?

Something like that...I think the distinction may be inherited from Sufia? Right now it looks like we're essentially allowing user two select two different images.

Right, the UI is presenting the same options in both cases right now, which is not good.  So we should pick one or the other.

I vote for thumbnail

I looked up the predicates in the EBUCore ontology and representative media seems more appropriate for media than books/images, e.g. a film or audio clip.  So thumbnail is definitely what we want.


Write issue in directory returned by cwd()

https://github.com/openjournals/joss-reviews/issues/3464
Permission issues at the very first run.
After pip3 install epimargin  on a Linux box. I ran the following snippets in python console.
from itertools import cycle

import epimargin.plots as plt
import numpy as np
import pandas as pd
from epimargin.utils import setup

(data, figs) = setup() # creates convenient directories
plt.set_theme("minimal")

I hit by permission issues when application tried to create default directory. Is is necessary to use /usr/bin/ to save data. In line 44 below, may be root can be set to someplace in user's $HOME?
<ipython-input-1-710a13386d8f> in <module>
      6 from epimargin.utils import setup
      7
----> 8 (data, figs) = setup() # creates convenient directories
      9 plt.set_theme("minimal")

~/Work/FORKES/epimargin/epimargin/utils.py in setup(**kwargs)
     42     logging.basicConfig(**kwargs)
     43     logging.getLogger('flat_table').addFilter(lambda _: 0)
---> 44     return (mkdir(root / "data"), mkdir(root / "figs"))
     45
     46 def fillna(array):

~/Work/FORKES/epimargin/epimargin/utils.py in mkdir(p, exist_ok)
     30
     31 def mkdir(p: Path, exist_ok: bool = True) -> Path:
---> 32     p.mkdir(exist_ok = exist_ok)
     33     return p
     34

/usr/lib/python3.9/pathlib.py in mkdir(self, mode, parents, exist_ok)
   1311         """
   1312         try:
-> 1313             self._accessor.mkdir(self, mode)
   1314         except FileNotFoundError:
   1315             if not parents or self.parent == self:

PermissionError: [Errno 13] Permission denied: '/usr/bin/data'

On Linux and OSX, https://github.com/COVID-IWG/epimargin /blob/1a8094ae8173a9f09f2efc5b872ac56d67a86c6f/epimargin/utils.py#L18 most likely to return /usr/bin since argv0 is /usr/bin/python3.
Another solution is to check if the cwd() is writable by the user. If not, default to a user-writable directory in user's $HOME? If not, the application needs to be run as root or sudo user which is not advisable.

Hi @dilawar - thanks for flagging this. I've just merged #118, which uses the __file__ builtin (when available) to construct a directory in the same location as the script. When that builtin is not available, we default to what pathlib.Path.cwd() provides.
We don't expect /usr/bin to be the default location for data; our intention was to create directories in the same folder as the client script. We do expect that client code calling this library will be run from a user-writable location, which I think is reasonable.
My testing indicates that argv[0] picks up the script location rather than the binary location. As an example, consider this following test script, located in my home directory:
from sys import argv
from pathlib import Path

print(argv[0])
print(Path(argv[0]).resolve().parent)
try:
    print(Path(__file__).resolve().parent)
except NameError:
    print("__file__ variable not available")
print(Path.cwd())

When I run /usr/bin/python3 test.py, I get:
test.py
/Users/satej
/Users/satej
/Users/satej

Does that make sense? Let me know if I've misunderstood something or have assumed something too specific about users' set ups.


Move CTPL and Scheduler headers out of rxros

greping for Scheduler.h (and InterruptableSleep.h, ctpl.h and Cron.h) it would appear they are not used by rxros itself, but only by the BrickPi classes.
If that is correct, then those headers should not be part of the rxros package, but should be hosted by either the BrickPi package(s) or in some other location.
As-is, any package dependent on rxros will find ctpl.h, Scheduler.h and Cron.h on their include path, which may break include order or clash with existing files.

Implemented in #14.

Fixed in #14 and rosin-project/rxros_examples#1.


Add all the Sitecore Standard fields to the FakeDb Standard Template

In the issue #64, the missing __Final Renderings field has been added to the Standard Template. All the other existing Sitecore standard fields needs to be registered as well.
It might be challenging to keep the fields set actual for numerous Sitecore versions. Consider implementing some kind of convention like "read all fields from the FieldIds class".

Don't want to add the fields manually because of the potential versioning issues mentioned above. In the same time reading the fields using reflection does not allow to set proper names and Shared fields. Any suggestions how it could be done?

Maybe use the now supported serialization and carry a serialized standard template with all its sections from the most recent Sitecore release? No hardcode, no reflection, and we get both IDs and Names.

Working on this in the field-factory branch. My current idea is just to create all the fields manually including ID, Name and  Shared fields. Wouldn't like to mix it with the serialization add-in... It definitely should be possible as an optional solution, but should not be a requirement.
Regarding the cross-versioning, I'd keep in FakeDb the "widest" set of fields. I guess that should be the fields from the latest available Sitecore version. That is not ideal, but are there any possible negative consequences of having some extra fields in some cases? E.g. fields from 8.1 on the 7.2-based project..

Using serializations may shift the "fields accuracy" maintaining to the FakeDb users (unless we deliver the serializations as part of the nuget package)..
But, it definitely worth to check, if the fields from serializations will work as expected and won't conflict with the existing default standard fields.

negative consequences of having some extra fields in some cases

Don't think so. Just can't compile against FieldIDs.FinalLayout for example, that's why we have our own version of those fields IDs.

And I agree re: extra dependency. Didn't realize it was a separate NuGet. You are right. Wouldn't want to have that as a requirement in the base framework.

@pveller: Introduced Field Builder (https://github.com/sergeyshushlyapin/Sitecore.FakeDb/commit/211efb101d8a17530a1259b9533c663088d91502) and registered all the Standard Fields from 8.1.0 (https://github.com/sergeyshushlyapin/Sitecore.FakeDb/commit/9f855172ffeda96d05120d3d1a5207b4f27a5e9c). Feedback is welcome ;)

I like it! With the FieldInfo you may as well look at #47 maybe?

Introduced a list of specialized DbField builder's (standard/random fields, from name or id), so there is no the almighty DbField constructor covering all the scenarios any more (c2d6ce9).

Implemented in v0.35.0.


kpt functions do not work on M1 Mac

Expected behavior
kpt fn eval -i list-setters:v0.1.0 to list all setters in directory tree
Actual behavior
[RUNNING] "gcr.io/kpt-fn/apply-setters:v0.2.0"
[PASS] "gcr.io/kpt-fn/apply-setters:v0.2.0" in 1.2s
  Results:
    [info] spec.template.spec.containers[1].env[3].value: set field value to "cluster-name-test"
  Stderr:
    "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested"

Information
kpt version v1.0.0-beta.13
Steps to reproduce the behavior
Try to run any kpt function on an M1 Mac

@mengqiy @yuwenma we are seeing an increase of issues reported for supporting Mac M1. I think we should be able to compile our Go based functions easily for linux/arm target, but I wonder what is idiomatic way to support the container images across different platforms.

https://docs.docker.com/desktop/mac/apple-silicon/
Detailed here. And i tested this flag manually for running containers on amd64 machine with the flag --platform linux/amd64 and it ran fine.
I suspect if this is added to the call for docker run, it would solve this until native images are baked in the CI.

I also want to note - this will only get worse if not addressed. Apple doesnt sell intel macs anymore. Multi architecture is the new normal.

Proposal and tradeoffs:
https://github.com/GoogleContainerTools/kpt/pull/2938

Hi I'm still having the same error when running the kubeval example.
kpt fn eval kubeval-imperative --image gcr.io/kpt-fn/kubeval:v0.3.0 --results-dir /tmp -- strict=true skip_kinds=MyCustom,MyOtherCustom

[RUNNING] "gcr.io/kpt-fn/kubeval:v0.3.0"
[FAIL] "gcr.io/kpt-fn/kubeval:v0.3.0" in 16s
  Results:
    [error] v1/ReplicationController/bob templates: Additional property templates is not allowed
    [error] v1/ReplicationController/bob spec.replicas: Invalid type. Expected: [integer,null], given: string
  Stderr:
    "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested"

Do I need to set anything to make this work?


Removed underline for footer links

Done with Caleb Tan

@carrotan30 @gohxiean Well done guys! Your changes were merged into the live app!


[SPARK-23807][BUILD] Add Hadoop 3.1 profile with relevant POM fix ups

What changes were proposed in this pull request?

Adds a hadoop-3.1 profile build depending on the hadoop-3.1 artifacts.
In the hadoop-cloud module, adds an explicit hadoop-3.1 profile which switches from explicitly pulling in cloud connectors (hadoop-openstack, hadoop-aws, hadoop-azure) to depending on the hadoop-cloudstorage POM artifact, which pulls these in, has pre-excluded things like hadoop-common, and stays up to date with new connectors (hadoop-azuredatalake, hadoop-allyun). Goal: it becomes the Hadoop projects homework of keeping this clean, and the spark project doesn't need to handle new hadoop releases adding more dependencies.
the hadoop-cloud/hadoop-3.1 profile also declares support for jetty-ajax and jetty-util to ensure that these jars get into the distribution jar directory when needed by unshaded libraries.
Increases the curator and zookeeper versions to match those in hadoop-3, fixing spark core to build in sbt with the hadoop-3 dependencies.

How was this patch tested?

Everything this has been built and tested against both ASF Hadoop branch-3.1 and hadoop trunk.
spark-shell was used to create connectors to all the stores and verify that file IO could take place.

The spark hive-1.2.1 JAR has problems here, as it's version check logic fails for Hadoop versions > 2.
This can be avoided with either of

The hadoop JARs built to declare their version as Hadoop 2.11  mvn install -DskipTests -DskipShade -Ddeclared.hadoop.version=2.11 . This is safe for local test runs, not for deployment (HDFS is very strict about cross-version deployment).
A modified version of spark hive whose version check switch statement is happy with hadoop 3.

I've done both, with maven and SBT.
Three issues surfaced

A spark-core test failure —fixed in SPARK-23787.
SBT only: Zookeeper not being found in spark-core. Somehow curator 2.12.0 triggers some slightly different dependency resolution logic from previous versions, and Ivy was missing zookeeper.jar entirely. This patch adds the explicit declaration for all spark profiles, setting the ZK version = 3.4.9 for hadoop-3.1
Marking jetty-utils as provided in spark was stopping hadoop-azure from being able to instantiate the azure wasb:// client; it was using jetty-util-ajax, which could then not find a class in jetty-util.

Test build #88670 has started for PR 20923 at commit 29e7324.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1808/
Test PASSed.

Test build #88670 has finished for PR 20923 at commit 29e7324.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class BindingParquetOutputCommitter(
class PathOutputCommitProtocol(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88670/
Test FAILed.

Test build #88713 has started for PR 20923 at commit 016d690.

Test build #88713 has finished for PR 20923 at commit 016d690.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build finished. Test PASSed.

I think we could separate cloud related stuffs to another PR, and fix only build related stuff in this PR.

Also I think we need to create a related spark-deps-hadoop-3.x under dev/deps and make dependency check work for Hadoop 3.

bq. I think we could separate cloud related stuffs to another PR, and fix only build related stuff in this PR
OK

Failure is the test dependencies failing as the checker is trying to pull in hadoop-3.1.0 & its still in ASF staging
Performing Maven install for hadoop-3
Using `mvn` from path: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.3.9/bin/mvn
[ERROR] Failed to execute goal on project spark-launcher_2.11: Could not resolve dependencies for project org.apache.spark:spark-launcher_2.11:jar:spark-440623: Could not find artifact org.apache.hadoop:hadoop-client:jar:3.1.0 in central (https://repo.maven.apache.org/maven2) ->

I'll turn off that check now, leaving the dependency list as is

Test build #88953 has started for PR 20923 at commit 43e3f31.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2013/
Test FAILed.

Test build #88955 has started for PR 20923 at commit 7c93d98.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2014/
Test PASSed.

Test build #88953 has finished for PR 20923 at commit 43e3f31.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88953/
Test FAILed.

I think you should also update "test-dependencies.sh" to make the new deps file work.

Jenkins, retest this please.

Test build #89038 has finished for PR 20923 at commit 7c93d98.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89038/
Test PASSed.

bq. I think you should also update "test-dependencies.sh" to make the new deps file work.
I did, but then things failed because the artifacts were only visible if you did a run with the -Psnapshots-and-staging profile, which jenkins doesn't do here -it's why test run 88953 failed.
The 3.1.0 artifacts are now up on the mvnrepo, so I can turn that on.
Because its out, I think it'd also be good to call the profile hadoop-3.1, to make clear that's the target release, and to avoid confusion if anyone ever creates a 3.2, 3.3, ... profile in future.

Test build #89058 has started for PR 20923 at commit 52a8c28.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2097/
Test PASSed.

Test build #89058 has finished for PR 20923 at commit 52a8c28.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89058/
Test FAILed.

Test failures are org.apache.spark.sql.sources.BucketedWriteWithoutHiveSupportSuite.; SPARK-23894

Ping @vanzin @gatorsmile , would like to hear your comments. Thanks!

I should add that the spark-shell doesn't bring up the Azure client, though it's happy with the rest, because of jetty-utils not making into dist/jars...I fear this is shading related.
Here's the JAR I'm using to do diagnostics of CP setup there; it tries to bootstrap access from searching for & loading the JARs into actually reading and writing the data. Significantly more informative when things don't work.
https://github.com/steveloughran/cloudstore/releases/tag/tag_2018_04_11_release

Test build #89295 has started for PR 20923 at commit f6b9dc8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2286/
Test PASSed.

The jetty problem has been dealt with; because of the shading declaration of jetty-util as provided (it isn't needed in spark any more), it wasn't getting into dist/jars even for those dependencies which did needed it.
Fix: explicitly declaring it in the hadoop-cloud module and the hadoop cloud profile in the assembly module.
The jetty-ajax dependency, which is the direct dependency of it from hadoop-azure, is also declared so that the spark build can keep in control of jetty versions everywhere. That one was getting through fine, because it wasn't being tagged as provided.

Test build #89295 has finished for PR 20923 at commit f6b9dc8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89295/
Test PASSed.

@jerryshao comments? I know without the patched hive or mutant hadoop build Spark doesn't work with Hadoop 3, but this sets everything up to build consistently, which is a prerequisite to fixing up the semi-official spark hive JAR.

@vanzin : The followup to this is #21066; I could move the compile time changes there but if you are going to have POMs playing with dependencies, seems best to have it all in one place...the other one just setting up the compile and tests
@jerryshao what do you suggest? It was your proposal to split things into pom and source for ease of reviewal, after all?

retest this please

I asked for the tests to run once more just to be sure.
I'd have preferred to keep the code-related build changes in the other PR where the code is actually added. But since the PR is already up, that would just slow things down, so this is fine as long as tests pass.

Test build #89748 has started for PR 20923 at commit f6b9dc8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2603/
Test PASSed.

I would guess the test here doesn't actually run on Hadoop 3 profile. So we actually doesn't test anything.
Also we still cannot use Hadoop3 even if we merge this because of Hive issue. Unless we use some tricks mentioned above. So I'm not sure if we should address Hive issue first.

+1 for @jerryshao 's comment. Some of Hive UTs will fail with Hadoop 3 profile.

Test build #89748 has finished for PR 20923 at commit f6b9dc8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89748/
Test PASSed.

I've also added a comment to (SPARK-18673)[https://issues.apache.org/jira/browse/SPARK-18673] offering to fix the org.spark-project.hive JAR, but only once this patch is in. This bit is ready, that may time, and it will need this setup so that the actual tests can be run.

Merging to master.

thank you! I guess that means I'm down for the hive JAR, doesn't it :)
Better make a list of patches which should go in, I think internally we have 1+ kerberos related (https://github.com/pwendell/hive/pull/2)  as well as the Hadoop version case statement.


[Bug]

[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
Android Studio version: 2022.3.1_____
Firebase Component: FirebaseMessaging_____ (Database, Firestore, Storage, Functions, etc)
Component version: 11.5.0___
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
My Unity Game works when I use the default Actvity as Entry and the defult manifest,
But it failt to install when I use my own SDK activity as entry
the error:
19:52:01.848 W Error when communicating with the Firebase Installations server API. HTTP response: [403 Forbidden: {
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}
]
19:52:01.850 W Firebase options used while communicating with Firebase server APIs: AIzaSyAwtzW3Z3H-K5omBdvBTt_-etm1ZO8kNHA, XXXXX, 1:196712049725:android:f8e2b1c962018c291e4e54
how could this happend ? my game should be using the same google-services.json , the only difference is the manifest
what permission is in lack?
Relevant Code:
// TODO(you): code here to reproduce the problem

// TODO(you): code here to reproduce the problem

Thanks for filing, @Ribosome2. The error you encountered is usually caused by misconfiguration such as when you don't use a valid set of Firebase options - API key, App ID, and project ID, when initializing Firebase. Without valid Installation auth tokens, app installs are not able to successfully communicate with Firebase servers like Firebase Messaging to mint FCM registration tokens. That said, you may try the following to resolve the issue:

Update the app's google-services.json (or GoogleService-Info.plist) file that can be downloaded from the Firebase Console. Publish a new version of the app to the PlayStore (or AppStore) if applicable.
Make sure that the API key used in the google-services.json (or GoogleService-Info.plist) file is either unrestricted, or allows the usage of the Firebase Installations API (i.e. API restrictions) and allows the usage by the app (i.e. App restrictions). You may also check this StackOverflow post and GitHub repository for other references.

If the issue persists, let me know so I could reopen the ticket.


fix(components/youtube-player): Pending commands, e.g. play video, are lost if issued before the YouTube iFrame API is available

When commands like YouTubePlayer.playVideo() are issued before _player is set, they get saved in
_pendingPlayerState to be passed on to the player when it is initialized. However, if the player
observable emits undefined before the initialized player, _pendingPlayerState is unset, and the
pending commands are lost. The player observable emits undefined if the iframe API is not yet
available.

Oops, I amended the commit to s/were lost/are lost/ and turns out force push is not that great with PRs.


[ALLUXIO-2569]Add Shell Command 'bin/alluxio fs help'

https://alluxio.atlassian.net/browse/ALLUXIO-2569
Alluxio shell command "bin/alluxio fs" should provide a sub-command called "help", which works like the following:
For “bin/alluxio fs help ”, this will print help message for the given command.
For “bin/alluxio fs help”, this will print help messages for all supported commands.
To implement this feature, this "help" command should be a class "alluxio.shell.command.HelpCommand.java", inheriting "alluxio.shell.command.AbstractShellCommand".

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14151/
Test PASSed.

Merged build finished. Test PASSed.

@AnkaiLiang  thanks for adding this command!
can you also add a test similar to tests/src/test/java/alluxio/shell/command/CatCommandTest.java?

Added duplicated method in AlluxioShellUtils and call it in AlluxionShell.java and HelpCommand.java.
And did some improvement as mentioned above.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14180/Build result: FAILURE[...truncated 3093 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.5.0-SNAPSHOT/alluxio-examples-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/pom.xml to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.5.0-SNAPSHOT/alluxio-core-server-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.5.0-SNAPSHOT/alluxio-underfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.5.0-SNAPSHOT/alluxio-integration-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/dependency-reduced-pom.xml to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.5.0-SNAPSHOT/alluxio-keyvalue-1.5.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Merged build finished. Test FAILed.

ok...I will check it

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14187/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14264/
Test PASSed.

@apc999 Hi, Mr.Bin, I added the unit test. Please have a look if you have time! Thank you!


abseil-cpp_202401: 20240116.0 -> 20240116.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/abseil/abseil-cpp/releases.
meta.description for abseil-cpp_202401 is: An open-source collection of C++ code designed to augment the C++ standard library
meta.homepage for abseil-cpp_202401 is: https://abseil.io/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20240116.1 in filename of file in /nix/store/y8sbqd39a5l00q267lac8ypv0hg7gca8-abseil-cpp-20240116.1

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

6206 total rebuild path(s)

6206 package rebuild(s)

First fifty rebuilds by attrpath
BeatSaberModManager
CHOWTapeModel
ChowKick
CuboCore.corepdf
CuboCore.coretoppings
EmptyEpsilon
MIDIVisualizer
MMA
SDL2
SDL2_Pango
SDL2_gfx
SDL2_image
SDL2_image_2_0
SDL2_image_2_6
SDL2_mixer
SDL2_mixer_2_0
SDL2_net
SDL2_sound
SDL2_ttf
SDL_audiolib
SDL_compat
SDL_gpu
Sylk
_1oom
_1password-gui
_1password-gui-beta
_20kly
_7kaa
_86Box
_90secondportraits
aaxtomp3
abbaye-des-morts
abracadabra
abseil-cpp
abseil-cpp_202401
abuse
acquire
activitywatch
adapta-gtk-theme
adbfs-rootless
adenum
adl
adriconf
adwaita-qt6
aegisub
agi
airgeddon
aitrack
ajour
akkoma

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y8sbqd39a5l00q267lac8ypv0hg7gca8-abseil-cpp-20240116.1 \
  --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 abseil-cpp_202401 https://github.com/r-ryantm/nixpkgs/archive/0d119c432d24669f3668ded66a5d58b3427ee286.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0d119c432d24669f3668ded66a5d58b3427ee286#abseil-cpp_202401

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

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @GaetanLepage for testing.

Superseded by #288469


Skip building / testing / benchmarking commits that don't modify code

Discussed a bit on Discord here
Start simple: add something like change_requires_benchmarks.sh that runs at the top of certain pipelines and exits if only markdown files, or files in docs/ are changed.

could have a check_paths_changed.sh path0 path1 kind of script - that could then do the git diff/path checks, and each pipeline could just list what it cares about (check_paths_changed.sh iree/ third_party/ or check_paths_changed.sh docs/ or check_paths_changed.sh bindings/tflite/ etc) - fewer scripts to manage, and things are easier to spot at a glance
(whenever we get around to moving the compiler from iree/compiler/ to compiler/ we'd be able to cleanly say "runtime code changes" vs "compiler code changes" too!)


Input max length

It would be great to add a maxLength parameter to the configuration. Even better, we could utilize the PhoneValidator to determine the maximum value and prevent users from entering input longer than necessary.

phone_numbers_parser (the library used by this one) has that information so this is implementable. Feel free to add this


”Dumitra” is listed in the drop-down menu

Description:
"Dumitra" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Dumitra" in the search bar.

Expected results
The location is listed in the drop-down menu as "Dumitra, Bistrița-Năsăud".


Vue.nextTick() required with transitions.

Version
1.0.0-beta
Reproduction link
https://github.com/autumnwoodberry/vtu
Steps to reproduce
Nest some v-if:
<transition>

    <transition v-if="b"></transition>
    <transition v-if="!b"></transition>

</transition>

test('output', () => {
    wrapper.setData({
      a: true,
      b: true
    });

    expect(wrapper.vm.a).toBe(true)
    expect(wrapper.vm.b).toBe(true)
    expect(wrapper.html()).toMatchSnapshot()
})

What is expected?
wrapper.html() returns the updated markup.
What is actually happening?
wrapper.html() returns outdated markup unless the test is changed to:
test('output', () => {
    wrapper.setData({
      a: true,
      b: true
    });

    expect(wrapper.vm.a).toBe(true)
    expect(wrapper.vm.b).toBe(true)
    Vue.nextTick(() => {
      expect(wrapper.html()).toMatchSnapshot()
    })
})

Thanks for the detailed bug report 😄
This is an issue with transitions, I'll look into it over the next few days

I think the solution to this is to stub the transition and transition-group components.
We have 3 options:

leave it to the user to stub using the stubs mount option
Provide a transition and transition-group stub components, for the user to pass in the stubs option
Stub transition and transition group by default inside mount

I'm leaning towards option 2.
I'd be happy with option 3. I don't use transition very often, so I'm not sure if there's be a use case for people testing unstubbed transitions? I'd be interested to hear others thoughts.

I like the "opt-in" option best as well and I think it keeps unexpected internal behavior to a minimum.
It might be nice to have a config somewhere so you can turn it on globally. I use transitions enough that it would be nice to that that option.

That's a good idea @autumnwoodberry . We could make a global config, like Vue has.

I'm going to be pretty busy the next few days, so I will just leave a couple more thoughts I had:

I'm actualy not sure what wrapper.setData({ a: true }) does vs wrapper.vm.a = true
If we made setData() async, or provided an async version or async option for it, it might be a more intuitive solution.

await wrapper.setData({ a: true })

expect(wrapper.vm.a).toBe(true);
expect(wrapper.html()).toMatchSnapshot();

Whatever gets decided, I think this should all get mentioned in the setData() docs section.

I'm actualy not sure what wrapper.setData({ a: true }) does vs wrapper.vm.a = true

setData sets the data and calls update.

If we made setData() async, or provided an async version or async option for it, it might be a more intuitive solution.

I don't think we should make setData async. Synchronous updating makes unit tests simpler to write and easier to read. I agree, it can be confusing for experienced Vue users who expect async updating, but I think that for the majority of users they would expect setData to update the Vue instance, which it does for everything except transitions. Which is why I'm tempted to stub transitions by default, and make it an opt-out feature.

Whatever gets decided, I think this should all get mentioned in the setData() docs section.

This isn't really a setData issue, it's to do with update. I agree though that this can be confusing.
I think we should link to update in all methods that call update, and add a gotchas section.

Ok yes, I see - that makes perfect sense.

I just released TransitionStub and TransitionGroupStub in 1.0.0-beta.2:
import { TransitionGroupStub, TransitionStub, shallow } from 'vue-tes-utils'

const wrapper = shallow(Component, {
  stubs: {
    'transition': TransitionStub,
    'transition-group': TransitionGroupStub
  }
})

Awesome! I will check it out when I have some spare moments.

@eddyerburgh I'm using TransitionStub and attempting to assert that elements enter & leave the dom after data change (two elements with a simple v-if/v-else inside a <transition> tag). It seems to work on enter, but not on leaving - the content inside the <transition> tag remains in the wrapper's html and receives the v-leave and v-leave-active classes. I expected the transition stub to just cause inner content to instantly enter/leave, is that understanding off the mark?

Hi @petridw, it should do. I'll update the code

@eddyerburgh here's a failing test that should be passing, I think:
component-with-transition.vue
<template>

    <transition>

{{ trueText }}

{{ falseText }}

    </transition>

</template>

transition.spec.js
import { shallow, TransitionStub } from "vue-test-utils";
import ComponentWithTransition from "@/components/component-with-transition";

const options = {
  stubs: {
    transition: TransitionStub,
  },
};

describe("component-with-transition", () => {
  it("swaps dom nodes properly", () => {
    const wrapper = shallow(ComponentWithTransition, options);
    expect(wrapper.text()).toBe(wrapper.vm.trueText);
    wrapper.setData({ bool: false });
    expect(wrapper.text()).toBe(wrapper.vm.falseText);
  });
});

Thanks @petridw, if you remove the keys, the test passes.
The TransitionStub basically behaves the same as an unstubbed transition, except it doesn't add leave classes when the component inside is hidden, and it always returns the child synchronously.

Interesting, so is there a different way I should be testing components that use transitions with keys?

No, I'll look into it. But I'm on vacation at the moment. Just pointing out
how to make the test pass
On 19 Oct 2017 22:06, "David Petri"<EMAIL_ADDRESS>wrote:
Interesting, so is there a different way I should be testing components
that use transitions with keys?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-test-utils/issues/52#issuecomment-338038173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMlbW2onB52EDwzyUu3-HpW2LJxYOXC_ks5st7nngaJpZM4PoGlA
.

@eddyerburgh cool - have a great vacation & thanks for all your work!

Maybe this is no more and issue? For me it works using shallow instead o mount no need to user any extra stubs like TransitionGroupStub or TransitionStub

Thanks for the heads up, I'll look into it

The fix for the keyed bug will be released in beta.9 🎉

I can't test component with transition.
In component:
...
<transition
  :name="optionsClass"
  @before-enter="animationFinished = false"
  @after-enter="animationFinished = true"
>

...

In tests:
console.log(wrapper.html())
wrapper.find('.u-select__select').trigger('click');  // sets data to display element (v-show)
console.log(wrapper.html());

The second html in console equals the first (with style="display: none").
If I remove <transition> from component it works as expected.

@eddyerburgh I've spot the bug #567

I have the same bug right now. The transition tag doesn't allow me to test when elements are visible or not because it doesn't wait until the end of the animation I supposed.

@MatteoGabriele as a hack, you can do the following
  global.window.getComputedStyle = () => {
    return {
      transitionDelay: '',
      animationDelay: '',
      transitionDuration: '',
      animationDuration: ''
    }
  }

I define it in a function in a helper file, then import & call it in any tests that operate on animating parts. Could get you by till an official fix is out.


Support navigating to the end and beginning of the note

It would be great if this can be supported.

You should already be able to do this with native OS shortcuts right?

Windows: Ctrl + Home, Ctrl + End
macOS: Cmd + ↑, Cmd + ↓

You should already be able to do this with native OS shortcuts right?

Right. I did not notice this before as their effects were replaced by another plugin.


Fix display-driver build on GCC 12

Recent versions of nixos-unstable have moved from GCC 9 to 12, which breaks to build. Flag -mno-outline-atomics is needed for the kernel module, to avoid errors sucs as:
ERROR: modpost: "__aarch64_cas4_sync" [nvidia.ko] undefined!
ERROR: modpost: "__aarch64_ldadd8_sync" [nvidia.ko] undefined!
ERROR: modpost: "__aarch64_ldadd4_sync" [nvidia.ko] undefined!
ERROR: modpost: "__aarch64_cas8_sync" [/nvidia.ko] undefined!
This change has been backported from jetson_35.3.1
Description of changes
What has changed as a result of this PR? Why was the change made?
display-driver did not build with nixos-unstable channel. A small change adding one flag to kernel module build was backported from 35.3.1 to 35.2.1 to make it builable with recent nixos-unstable versions.
Testing
Tested that it builds with latest nixos-unstable, which is an improvement because previously it didn't build at all. I don't at this very moment have physical access to the AGX Orin with display to see does the driver really work or not

This fixes #59


Add migration tools.

Based on the script developed in http://github.com/nuclearsandwich/rosnroll this tool should be suitable for the following cases

Creating a new ROS distribution from an existing one by re-triggering bloom releases on all repositories.
Updating a previously migrated distribution by re-triggering bloom releases on missing repositories.
Updating the release platform of an existing ROS distribution by re-triggering bloom releases for the new target platform.

Close and reopen to try to retrigger the actions


Subtraction operator for Inertial class

Summary
This PR adds a feature for minus operator in inertial class, full description here #423
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

please add tests to Inertial_TEST.cc

Based on the initial testing of -operator with two cubes, it seems to work. Right now a separate negative operator has been implemented.
After implementation it seems like we might be able to piggy bank on the +operator for -operator as suggested by @adityapande-1995. If we agree on piggy banking on +operator, we will have to reverse the signs all the fields(pose, inertia matrix and mass) of the Inertial object, which seems reasonable?

Also, their is one small thing though that since Inertial objects will be passed as const in -operator we might need to copy the Inertial object first then change it's signs and pass it to +operator?

are you up for adding this to the python bindings as well?

https://github.com/gazebosim/gz-math/blob/ign-math6/src/python_pybind11/src/Inertial.hh#L59-L60

are you up for adding this to the python bindings as well?

https://github.com/gazebosim/gz-math/blob/ign-math6/src/python_pybind11/src/Inertial.hh#L59-L60

yes, I can do that as well.


spring-cloud-starter-alibaba-seata Feign HTTPS remote call failed, switching to HTTP is normal

Please provider logs and some necessary informations, unless we will close the invalid issue!


[Bug] Incorrect error message in Select widget when there are duplicate values

Description
When you have duplicate values for items in Select widget, it still throws the error This value does not evaluate to type "Array<{ label: string, value: string }>".

This is very misleading and has caused few users to spend a lot of time debugging a wrong problem.
Steps to reproduce the behaviour:

Add Select widget
Add items with the same values
See the error

Important Details

Version: Cloud
Environment: Production

@hetunandu is this a JS evaluation issue or a widget issue?

This looks like a validation issue. @riodeuno is this handled or can be archived with the new change in widget validations?

We're not updating the unique property which is applied in the validations configurations, to this error message. We need more comprehensive error messages.
This involves the debugger.


Hyperion not working on Kodi Jarvis

I don't get any light from Kodi 16, Jarvis beta 2 on Android (NVIDIA shield Android TV).
Sure, it's beta but could be nice to have it working when released. :)

Did a full reinstall of Kodi and now it works again. Strange..

So, the "solution" is to turn off hardware acceleration in the video settings. The problem is within Kodi and has nothing to do with the plugin.


Error HTTP request isn't sent when run via node-dev

When used in a project invoked via node-dev, errors are captured by the global exception handler / captureException but the HTTP request to Sentry does not initiate.

Fixed in node-dev


CHEF-2871 Outdated Ruby and Rubygems

As per the ticket Ruby is 1.9.2p180 and not 1.9.3 and Rubygems is old.
With this quick swap out we get 1.9.3 with Rubygems 1.8.10 (provided by 1.9.3)

Hey Scott, we're in the process of rewriting this build system in Ruby, and we're pretty close to done. We're gonna upgrade Ruby to 1.9.3 as soon as we finish the rewrite and get everything running on Ruby 1.9.3 in our internal Ci.
Thanks!

Doh that's unfortunate as this works.


Kali Linux and Ubuntu not booting !

I have been using both OSes on UTM and they were working perfectly fine.
Last week Ubuntu stopped booting and today Kali also freezes on booting.
UTM Version: Version 3.0.4 (46)
Hardware: MacBook Air M1 2020
Software: macOS Monterey - Version 12.3
Kali Linux Version: 2022.1
Ubuntu Version: 20.04.3 LTS
(both for ARM 64 obviously)
The Following screenshots are the pages I get:
Ubuntu:

Kali Linux:

Try again on UTM 3.1.5 I have experienced. But it still takes long time to boot Ubuntu and shared folder is not mounted.

i also had this issue. plus when i redownload it, it will be stuck on the updating part unless i force restart


VK_EXT_vertex_attribute_divisor on i965

Hi, how I can use DXVK 0.60 through Intel (i965) with Mesa 18.1.2?
I don't have VK_EXT_vertex_attribute_divisor extension.
warn:  Vulkan extension VK_EXT_shader_viewport_index_layer not supported
err:   Required Vulkan extension VK_EXT_vertex_attribute_divisor not supported

@MrChebik intel not work correct in DXVK  in drivers on intel vulkan not complete

I'll be honest, I didn't really consider Intel when marking that extension as required, but DXVK needs it and some games won't work correctly without it. The best thing would be to file a feature request for Intel to implement that extension.

Thanks for the quick response. I just tried to run SkyrimSE, thinking that the Green dots could be fixed during rendering. Judging by the articles from Intel, they have already implemented this extension. It remains to work for Mesa. I'll try to write them.

I turned to the mesa-dev:

Yes, we already have support for VK_EXT_shader_viewport_index_layer.  For
VK_EXT_vertex_attribute_divisor, it should be trivial and I'm happy to do
so but there are currently no tests for it and, up until this email, we
haven't had any call for that.  We'll try to bump it up the priority list.
--Jason

Great, in that case I'll close this issue.


search inconsistencies

@deniseOme commented on Thu Mar 23 2017
while searching for Spinocerebellar ataxia type 1 gives no results whether in production or beta:
https://beta.opentargets.io/search?src=q:Spinocerebellar ataxia type 1
http://www.targetvalidation.org/search?src=q:Spinocerebellar ataxia type 1
searching for the orphanet ID it does work though:
http://www.targetvalidation.org/search?src=q:Orphanet_98755
searching for Spinocerebellar ataxia type seems to give results:
http://www.targetvalidation.org/search?src=q:Spinocerebellar ataxia type
Is this related to
https://github.com/opentargets/rest_api/issues/38
?

moved from webapp to here

could be another example for #51

Solved?


Linq expressions like GroupBy

Hi,
Thanks for your library, would you implement more functions on slices like GroupBy?

Hi,
Thanks for your library, would you implement more functions on slices like GroupBy?

any specific examples?


Error 'unrecognized opcode csrrs' when compiling self_modify_code example with gcc 12.x

Unfortunately, due to a breaking change in RISC-V ISA 20191213 (https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/aE1ZeHHCYf4)

... the csr read/write (csrr*/csrw*) instructions and fence.i instruction has separated from the I extension, become two standalone extensions: Zicsr and Zifencei;...

gcc 12.x now requires -march=rv32ec_zicsr in order to compile csrr* instructions. Although it is an easy fix when supporting just the latest gcc 12.x risc-v toolchains, the question is how to do it while keeping backward compatibility with older gcc toolchains? E.g. a conditional parameter assignment in makefile based on gcc version?

Can this be resolved by adding a .option zicsr in front of the code?

Yes! I have missed it is actually already used elsewhere...
  asm volatile(
...
#if __GNUC__ > 10
  ".option arch, +zicsr\n"
#endif

Nice 👏

Arch option added in https://github.com/cnlohr/ch32v003fun/pull/88/commits/fc598d183d0c8f9aa72d568d3a7167e8d493a8da

Thanks. Good catch.  If you can, address the comment on your PR and then we can merge this in!


Fix distutils.sysconfig._python_build() on windows

Create 'Setup.local' accouting for multi-configuration build to ensure
'distutils.sysconfig.project_base' (used to check if python is
executed from a buildtree) is properly initialized.

Closing. Superseded by PR #101


[FR] Hover to expand the graph?

Hey! I tried to use css to add :hover() property:

.view-content.graph-banner-content:hover {
    max-height: 300px;
    transition: all 0.2s;
}

But I found that the canvas doesn't expand:

Is there some way to expand the Canvas with the container (or make the canvas height bigger than 100% ?)

Normal local graphs opened by the command are resizable.
Local graphs on banner also should be able to resize, but they seem not resizable.

I think that the following processing in app.js used for Obsidian has been dislodged when moving the Element.
If you would be willing to investigate this, please?
            e.prototype.onResize = function() {
                var e = this
                  , t = e.px
                  , n = e.hanger
                  , i = e.containerEl
                  , r = e.interactiveEl
                  , o = window.devicePixelRatio
                  , a = i.clientWidth
                  , s = i.clientHeight;
                if (this.width = a,
                this.height = s,
                t) {
                    var l = Math.round(a * o)
                      , c = Math.round(s * o)
                      , u = t.renderer
                      , h = u.width
                      , p = u.height;
                    u.view.style.width = a + "px",
                    u.view.style.height = s + "px",
                    u.resize(l, c),
                    r.width = a,
                    r.height = s,
                    t.renderer.events.resolutionChange(1 / o),
                    n && this.setPan(this.panX + (l - h) / 2, this.panY + (c - p) / 2)
                }
                this.changed()
            }

Normal local graphs opened by the command are resizable. Local graphs on banner also should be able to resize, but they seem not resizable.
I think that the following processing in app.js used for Obsidian has been dislodged when moving the Element. If you would be willing to investigate this, please?
            e.prototype.onResize = function() {
                var e = this
                  , t = e.px
                  , n = e.hanger
                  , i = e.containerEl
                  , r = e.interactiveEl
                  , o = window.devicePixelRatio
                  , a = i.clientWidth
                  , s = i.clientHeight;
                if (this.width = a,
                this.height = s,
                t) {
                    var l = Math.round(a * o)
                      , c = Math.round(s * o)
                      , u = t.renderer
                      , h = u.width
                      , p = u.height;
                    u.view.style.width = a + "px",
                    u.view.style.height = s + "px",
                    u.resize(l, c),
                    r.width = a,
                    r.height = s,
                    t.renderer.events.resolutionChange(1 / o),
                    n && this.setPan(this.panX + (l - h) / 2, this.panY + (c - p) / 2)
                }
                this.changed()
            }

Oh hi! Thank you very much for your investigation and response.
So is this a special handling within the Obsidian app? 🤔 I think this is beyond my capabilities... and I can put this request on hold for now.
Thanks again!


Extreme Upward Trend 1/1/2007 - 12/31/2014

question from LinkedIn:
Trying to pull daily data for the search term "S&P 500" ["s%26p%20500"] 1/1/2007-12/31/2014, I get an extreme upward trend that I don't get when I use weekly data from Google Trends directly. They should look roughly the same, no? Do you know why that could be?
I understand that your package allows to have daily granularity, while incorporating the whole search interest over time (always 2-months overlapping CSV files anchoring the relative search attention of month 1 to month 2 to month 3 etc.).

Looking at it further, it seems there was an error in the weekly data parsing where some date was removed where it should not have been. This has since been fixed.
Originally, this is what the daily, weekly, and monthly (from Google Trends site) data looked like:

Note the weekly graph is slightly jumpy, since it is missing some points. Originally, only two months would be collected, rather than the 5 per file. This has been corrected. The data now looks like this, which is correct:


implement per-route override for rbac stat prefixes

Commit Message: implement per-route override for rbac stat prefixes
Additional Description: currently, if you only have stat prefixes configured in per-route config and not the base config, the stat prefix will be empty. this PR addresses that.
Risk Level: low
Testing: unit tested
Docs Changes: n/a
Release Notes: changelog updated

Will wait for @yangminzhu review before merging.

/wait-any

@yangminzhu gentle ping

/retest

/retest

/retest

@antoniovleonti it looks like main merge is needed to address coverage failure.


Libraries missing "AnsMPI.dll" and "AnsGPU.dll"

Hi there,
After installing and setting the exe path using:
import pyansys

ansys = pyansys.ANSYS(exec_file="C:\\Program Files\\ANSYS Inc\\v180\\ansys\\bin\\winx64\\ANSYS.exe", run_location=None, jobname='file', nproc=None, override=False, wait=True, loglevel='INFO')

I get two windows pup up which say:
The code execution cannot proceed because AnsMPI.dll was not found. Reinstalling the program may fix this problem.
and
The code execution cannot proceed because AnsGPU.dll was not found. Reinstalling the program may fix this problem.
Any idea how to fix it?

Hi there,
I solve the issue. I was calling ANSYS.exe when I should be calling MAPDL.exe
Thank any way!!

I'll update the docs to specify MAPDL.exe for W10.


Angular CLI builds styles before replacing files

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Area
- [X] devkit
- [ ] schematics

Versions

- Node: 10.3.0
- Npm: 6.1.0
- Angular CLI: 6.1.0-rc.0

Desired functionality

When i build a project with ng build specifying the desired configuration it replaces files as i want.
But in order to replace styles i put a file called theme.scss in global scss loaded files, then i replace it with
 { replace: "src/theme.scss", with: "src/theme2.scss" }

The file replacement works correctly and everywhere in my project when i call theme.scss i get theme2.scss response.
However if in a specific component style i use vars from theme.scss vars are not called from theme2 but always from theme.
I think the problem might be that angular is replacing my theme.scss after the compiling of all my component styles.
I think it is an issue because the default behaviour should be that any call to my theme.scss file should be replaced by a theme2.scss file call, even in specific components.

Hi,
I can't say if angular-cli builds styles before replacing files, but note that you currently can only replace .tsfiles at build-time. In the end, it won't work.
You can look at this for more information https://github.com/angular/angular-cli/issues/11451#issuecomment-403014907


Dot file toggle

I think dot files should be hidden by default but toggleable with ctrl+.

Sure i think this will be done soon!(maybe 1.0.2)

ctrl+. isn't easily accessible on all keyboards (AZERTY without numpad), ctrl+h could be better, used by other file managers, like thunar or ranger.

I think ctrl+h could instead be used for a help modal in the file manager for newcomers. Maybe Ctrl+E can work?

Help modal  uses ctrl+? maybe?

Or directly ?, easier and used by lazygit and others. never saw ctrl+h for help anywhere, mapped to F1 most of the time.

Maybe can just ctrl+? and ? both can work for toggle help modal

Yes why not, this won't be used elsewhere I suppose.

@booth-w hi~
I just update it in here


net/haproxy: Log File doesn't work (missing diag_logs_template.inc)

Describe the bug
HAProxy plugin:
when I click on "Log File" I got:
Warning: require_once(diag_logs_template.inc): failed to open stream: No such file or directory in /usr/local/www/diag_logs_haproxy.php on line 6 Fatal error: require_once(): Failed opening required 'diag_logs_template.inc' (include_path='/usr/local/etc/inc:/usr/local/www:/usr/local/opnsense/mvc:/usr/local/opnsense/contrib:/usr/local/share/pear:/usr/local/share') in /usr/local/www/diag_logs_haproxy.php on line 6
Additional context
https://forum.opnsense.org/index.php?topic=16611.0
Environment
Opnsense 2.1.3
In 20.1.2 release is line: system: drop unused services.inc and diag_logs_template.inc

This was fixed in os-haproxy 2.20 for 20.1 as far as I know, current is 2.21. The info was not included in your report? Also things like os-cache can interfere.

Works for me on 20.1.3 with os-haproxy 2.20.

Strange. I have same version 20.1.3 and haproxy 2.20.
Maybe one of upgrades didn't go as planed. I will wait for next upgrade.
I have fixed my problem with old diag_logs_template.inc and I had to comment line:
require_once("services.inc"); otherwise if I added also this file I got error function (don't remember name) already declared or something like this.

I have just upgraded to 20.1.4 (available today) and now HAporoxy Logs are working :)
HAproxy is now 2.21.

@githubcek Thanks for reporting back.


fix($compile): do not swallow thrown errors in test

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix.
What is the current behavior? (You can also link to an open issue here)
Since e13eeab, errors/rejections produces during fetching the template or compiling an asynchronous directive, where overzealously silenced. This doesn't make any difference in (most) production apps, where $exceptionHandler does not rethrow the errors. In tests though (where $exceptionHandler rethrows by default), it can unexpectedly "swallow" thrown errors.
See also #15629.
What is the new behavior (if this is a feature change)?
The extraneous .catch(noop) has been removed, thus letting errors thrown by $exceptionHandler to surface.
Does this PR introduce a breaking change?
No
(It is possible that exceptions might pop up in tests, but they where previously incorrectly hidden. Also note that the only modification in tests were to restore them to their pre-1.6.0-rc.0 state.)
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
The changes in 'compileSpec.js' essentially revert the modifications that were unnecessarily (and incorrectly) done in e13eeab (and also one incorrect modification from c22615c).
Fixes #15629

Is this a breaking change? Even when this is only for tests (and I am ok in
having it in the current stable branch).

Is this a breaking change?

It depends how you look at it :grin:
First of all, this will have no effect in cases where $exceptionHandler does not throw an exception. In most production apps this is not the case (and if it is, people will run into bigger problems, such as half-finished digest cycles and inconsistent state).
In cases where $exceptionHandler rethrows (the default behavior in tests), this PR will restore the 1.5.x behavior (throwing), which was unintentionally changed/broken in e13eeab (and started swallowing errors).
tl;dr
Theoretically, this PR fixes a regression introduced by e13eeab in 1.6.0-rc.0.
Practically, it is possible that people have written tests that pass with 1.6.0-rc.0+ but fail with this PR.

I am fine with the explanation for not calling this a BR. LGTM

LGTM


[3.2.0] - The 'MANAGE APP' link is not working

Description:
The 'MANAGE APP' link which is residing in the API subscription page (devportal) is not working. When clicking on the 'MANAGE APP' link is not redirecting the user to any of the devportal pages.
Steps to reproduce:

Log in to the publisher portal and deploy a sample API.
Log in to the developer portal and subscribe to the particular API.
Select the relevant API in the devportal and navigate to the API subscription page.
Then click on the MANAGE APP link in one of the subscriptions under the Subscriptions section.

Affected Product Version:
3.2.0

Issue is not in the master branch


🔨 Fix cargo watch tooling

This pull request fixes an issue I was experiencing on my Windows development environment (though I do not believe it occurs on other environments).
The problem I had was that when running a dev server with yarn dev:web, cargo watch would constantly refresh the app. Running cargo watch --debug revealed that it was being caused by changes detected in the core/prisma directory, which seemed to coincide with database writes.
The rust-lang GitHub page has an issue discussing this problem and notes that cargo watch triggers on any changes to the directories it is watching (not just source files) unless that file is covered by the .gitignore. Although the .gitignore does cover *.db*, it seems that writes to the core/prisma directory generally were triggering recompiles.
What I ended up doing was putting the dev.db etc. files in core/prisma/dev instead, then added that to the .gitignore directly. It worked - no more random recompiles on Windows. Admittedly, this is a bit more cluttered than before, but I think it's worthwhile for me at least, and might help other devs in the future.
I also added indentation to a few doc comments because it made clippy mad.

Have you tried passing an additional --ignore flag to cargo watch?

Have you tried passing an additional --ignore flag to cargo watch?

Oh. yeah you're right, that's an easier fix. I removed those other changes and fixed the problem by adding --ignore core/prisma.

Nice! Happy it worked


Fix element highlight on hover

Download Artifacts :

win-ia32
win-x64
linux-x64

Download Artifacts :

win-ia32
win-x64
linux-x64

Download Artifacts :

win-ia32
win-x64
linux-x64


tests: possible flake in TestCopyFd

Just filing this for my own sanity so I remember to investigate later. Nothing to see here.
--- FAIL: TestCopyFd (4.31s)
    kprobe_copyfd_test.go:79: pid is 11464 and spec file is /tmp/copyfd-3340320829.yaml
    kprobe_sigkill_test.go:33: error reading stderr> : read |0: file already closed
    kprobe_sigkill_test.go:33: error reading stdout> : read |0: file already closed
    kprobe_copyfd_test.go:93: command failed with exit status 1. Context error: %!s(<nil>)
    filenames.go:60: deleting export file for TestCopyFd (/tmp/tetragon.gotest.TestCopyFd.3364309601.json)
FAIL

Thanks @willfindlay. I think I know what this issue is here.
We need to wait for the pipes before we call cmd.Wait()
From: https://pkg.go.dev/os/exec#Cmd.StderrPipe

It is thus incorrect to call Wait before all reads from the pipe have completed.

So something like this, I think. Have a bunch of other things in flight now, but will do a PR on this next.
(other tests also need to be fixed).
@@ -47,14 +47,7 @@ func TestCopyFd(t *testing.T) {
        if err != nil {
                t.Fatal(err)
        }
-
-       go func() {
-               logOut(t, "stdout> ", testPipes.StdoutRd)
-       }()
-
-       go func() {
-               logOut(t, "stderr> ", testPipes.StderrRd)
-       }()
+       defer testPipes.Close()

        // makeSpecFile creates a new spec file bsed on the template, and the provided arguments
        makeSpecFile := func(pid string) string {
@@ -86,6 +79,9 @@ func TestCopyFd(t *testing.T) {
                t.Fatal(err)
        }

+       logWG := testPipes.ParseAndLogCmdOutput(t, nil, nil)
+       logWG.Wait()
+


Use future-proof URLconf format.

This syntax is compatible with all past and, as far as the current
deprecation timeline is concerned, future versions of Django.

This avoids a bunch of deprecation warnings when running on Django 1.9.

Note that #138 contains pretty much the same changes, showing some demand for this fix and a release on PyPI.

Merged, thanks for the delay!


Improvements to native application tutorial

Tidy up, remove extraneous content duplicated in following tutorial. Addresses DOCS-2049
Description
https://jira.mesosphere.com/browse/DOCS-2049
Urgency

[ ] Blocker
[ ] High
[x ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

Updated with suggested changes @sascala

Review request pls oss-team