Ship sciview with Fiji? Or make the sciview update site stay in sync with Fiji seamlessly

Over time there have been various issues and dependency skew with the sciview update site(s) not matching what is currently shipped on the core update sites for vanilla Fiji. E.g. #422, #392, #179. This issue intends to document what the fundamental problem is, and ways we could/should resolve it.
The sciview dependencies must stay in sync with Fiji's dependencies. That's what the pom-scijava Bill of Materials is for: keeping dependencies at consistent versions. But it only fully works if: A) sciview and fiji releases extend the same (ideally latest release) version of pom-scijava; and B) the dependency versions uploaded to the sciview and Java-8 update sites respectively align with those releases.
This has been historically tricky for a couple of reasons. We have tooling to populate a Fiji installation with a Maven coordinate including its dependencies, and upload the resulting state to an update site, but there are a couple of wrinkles:

Native dependencies need to be copied to the right places (jars/<platform> or lib/<platform>);
We need to take care not to shadow the versions of any core libraries—i.e., every JAR should exist either on the Java-8 site (in which case it is "core") or the sciview update site;
When a core dependency such as ImgLib2 changes in a backward-incompatible manner, we need to update all downstream code to accommodate the breakage, and then synchronize releases and uploads to avoid dependency skew across update sites.

To help scenery+sciview stay in better sync with Fiji henceforth, I propose that we add sciview to Fiji, so that it comes with Fiji. No extra update site needed—it works out of the box.
Needed steps to make this happen:

Get scenery and sciview (re)added to the pom-scijava BOM.

This is important so that other projects can depend on scenery+sciview. It will let people e.g. write plugins that use sciview more easily.
It would also bring us closer to including scenery and sciview in the pom-scijava "mega melt" build+tests, to validate that changes to dependencies don't break scenery+sciview; unfortunately, because the builds are Gradle-based, the mega-melt tooling is incompatible—we would need to enhance the melting-pot.sh script to know how to override dependency versions in the scenery+sciview gradle builds.
We also need a release of sciview, which is what the pom-scijava BOM will reference.

Add sciview as a runtime dep to the sc.fiji:fiji POM file.

And I think that's it?
@kephale @skalarproduktraum If you would rather keep scenery+sciview on a separate update site, I think that would also be OK. But we would then need to address the three wrinkles mentioned above: 1) fix any bugs in populate-app.sh, 2) stop shadowing core libs, 3) update scenery+sciview synchronously with Fiji whenever core libs break things. (Though ideally, core libs would not break things in the first place...)

To help scenery+sciview stay in better sync with Fiji henceforth, I propose that we add sciview to Fiji, so that it comes with Fiji. No extra update site needed—it works out of the box.

I am comfortable with doing this now. I think we're finally ready. Thank you for the suggestion @ctrueden

Doing this would close https://github.com/scenerygraphics/sciview/issues/402

I expect that the way we handle this issue will resolve/close https://github.com/scenerygraphics/sciview/pull/374.

I'm making progress on this. But there's one major issue I forgot about when I proposed this solution: scenery+sciview now require Java 11. So if we ship it with Fiji, we need to upgrade to Java 11, or at least somehow tolerate the scenery+sciview JARs being present at a bytecode version too new for Java 8. I have some ideas, and will keep poking at it.

Oh, the other issue is the Launcher. I need to make it really work with Java 11, and finally update it for all Fiji users. We'll give it another go and see who complains!

Updating to Java 11 will also require updating the JavaFX-dependent projects. It's time to start a new Java-11-based update site, and dead-end the Java-8 one. :+1:

This issue should be grouped with this issue: https://github.com/scenerygraphics/sciview/issues/563

Related: https://github.com/scenerygraphics/sciview/issues/498

Related: https://github.com/scenerygraphics/sciview/issues/392

@ctrueden should we be doing more Jaunch testing now?

Sure, if you like. I just tried briefly to combine the scijava-ops and sciview update sites. First, I followed the instructions to install SciJava Ops into Fiji (As explained on https://ops.scijava.org/). Then, I enabled the sciview update site, installed it, restarted Fiji, and tried to launch sciview. I encountered two small issues:

When enabling the sciview update site, it wanted to install the newer (but still old at this point) ImageJ-linux64, and in so doing, wanted to set its executable bit, but for some reason failed to do so, resulting in an exception stack trace. To work around, I just marked ImageJ-linux64 with "Keep as-is" and was able to proceed with installing the rest of the sciview update site.
After restarting and launching sciview, I got a snakeyaml error relating to the fact that the scijava-ops shadows snakeyaml at 2.0, but does not shadow ui-behaviour at 2.0.8. I fixed this by uploading ui-behaviour 2.0.8 to the scijava-ops site.

So it should now almost work to turn on both the scijava-ops and sciview update sites and enjoy the synergy. You might just have to do the same workaround I did in (1) above.

I did run into a novel issue when playing with the Game of Life 3D, though: trying to zoom around, the zoom behavior was very coarse. So then I tried "Circle camera around current object" while the GoL volume was actively animating, and it crashed Fiji outright with no errors on the console. Whee!


Imagery test timeouts

I'm seeing a bunch of imagery tests time out when running locally and the problem doesn't fix itself if I go back as late as CesiumJS 1.60. I'm on Windows, testing with Chrome and Firefox. I don't think it needs to hold up the release, but I marked the issue as priority - high.
Core/Resource fetchJsonp returns a promise that rejects when the request errors
Core/VRTheWorldTerrainProvider conforms to TerrainProvider interface
Scene/ArcGisMapServerImageryProvider rejects readyPromise on error
Scene/ArcGisMapServerImageryProvider raises error on invalid URL
Scene/BingMapsImageryProvider rejects readyPromise on error
Scene/BingMapsImageryProvider raises error on invalid url

I'm seeing these in the release process for 1.77 as well, on Windows in Chrome, Firefox, and Edge (Chromium). @sanjeetsuhag wasn't able to reproduce, though, which is interesting?

I'm seeing these in the release process for 1.77 as well, on Windows in Chrome, Firefox, and Edge (Chromium). @sanjeetsuhag wasn't able to reproduce, though, which is interesting?

I don't think these have been an issue for the past few releases and I was unable to reproduce on Windows or macOS in Chrome, Firefox, or Edge. I'll close the issue for now but we can revisit this if someone notices the errors again.


Fix throwIfNotFound when query result is zero

This fixes the throwIfNotFound method when the query result is 0 (number of affected rows).
Closes #469

Coverage remained the same at 96.057% when pulling 2e742d57a3e1496f0b6a7f64a6ea0d4f24b23211 on seegno-forks:bugfix/throw-if-not-found-result-zero into 559d38df9992a76cbd9213e6e64b8acc0c8cc776 on Vincit:master.

Coverage remained the same at 96.057% when pulling 2e742d57a3e1496f0b6a7f64a6ea0d4f24b23211 on seegno-forks:bugfix/throw-if-not-found-result-zero into 559d38df9992a76cbd9213e6e64b8acc0c8cc776 on Vincit:master.

Coverage remained the same at 96.057% when pulling 2e742d57a3e1496f0b6a7f64a6ea0d4f24b23211 on seegno-forks:bugfix/throw-if-not-found-result-zero into 559d38df9992a76cbd9213e6e64b8acc0c8cc776 on Vincit:master.

Brilliant! Thank you!


Can't connect to mariaDB

I get the following error:
SQLSTATE[HY000] [1045] Access denied for user<EMAIL_ADDRESS>(using password: YES)
And when I change the variables:

DB_PORT_3306_TCP_ADDR=myIp
DB_PORT_3306_TCP_PORT=myPort

within the .env file according to the IP+Port I need, there is still the same error.

Some questions from my side :)
Are you running phundament inside Docker?
Which database do you want to use, also Docker?
Do you have the user user?
Can you set your user here?
DB_ENV_MYSQL_USER=dev
DB_ENV_MYSQL_PASSWORD=dev123

Can you run docker-compose run php yii db/create?
Like so:
Kraftbuch:app tobias$ docker-compose run php yii db/create
Creating app_mariadb_1
Checking database connection on DSN 'mysql:host=<IP_ADDRESS>;port=3306' with user 'admin'......... [OK]
Creating database 'dev-phundament-4' and granting permissions to user 'dev' on DSN 'mysql:host=<IP_ADDRESS>;port=3306' with user 'admin'. [OK]
Kraftbuch:app tobias$

Thx for your response. Yes, I run phunament inside Docker and I use mysql.
my DB_ENV_MYSQL_USER is actually dev, I've just copied the varName and wrote a random userName. But in my case its "dev" as well.
Your command returns:
Interactive mode is not yet supported on Windows. Please pass the -d flag
when using 'docker-compose run'.

I execute docker-compose within the "Docker Quickstart Terminal".
My docker-compose.yml contains:
# Phundament 4 - Application stack

php:
  build: .
  links:
    - 'mariadb'

nginx:
  image: phundament/nginx-one:1.9
  links:
    - 'php:PHPFPM'

mariadb:
  image: 'tutum/mariadb:10.1'
  environment:
    MARIADB_PASS: secretadmin

Use
php:
  build: .
  links:
    - 'mariadb:DB'

This will prefix ENV variables from the database container with DB_ - Phundament expects this in its config.
Note that links will go away in a future version of Docker.

Still the same outcome, except that i get another IP-address in my error message (<IP_ADDRESS> instead of <IP_ADDRESS>)

Be aware of data loss in your containers!
But, ... did you docker-compose kill && docker-compose rm -fv?
Could you show the output of docker-compose version and docker info.

Version:
docker-compose version 1.5.2, build e5cf49d
docker-py version: 1.5.0
CPython version: 2.7.10
OpenSSL version: OpenSSL 1.0.2a 19 Mar 2015

Info:
Containers: 0
Images: 81
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 81
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.13-boot2docker
Operating System: Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: DXXM:Q26V:OIZP:OKRB:25C3:4HIH:VUSY:MNEM:WT5E:JWW6:BTEW:R6CM
Debug mode (server): true
 File Descriptors: 15
 Goroutines: 33
 System Time: 2016-01-18T19:12:11.130391787Z
 EventsListeners: 1
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

I tried docker-compose kill && docker-compose rm -fvnow and I when i build/up it again, it's still the same.

Hmmm, I am a bit clueless at the moment.
I'll try to get my hands on a Windows system to debug this. What's your Windows version?
... and does it also don't work with a fresh clone?

CC @disco-tex77 @marc7000 @eluhr @Quexer69 If you could test this on Windows, this would be great.

Hi, have the same issue:
Database Exception – yii\db\Exception
SQLSTATE[HY000] [1045] Access denied for user<EMAIL_ADDRESS>(using password: YES)
↵
Caused by: PDOException
SQLSTATE[HY000] [1045] Access denied for user<EMAIL_ADDRESS>(using password: YES)
in /app/vendor/yiisoft/yii2/db/Connection.php at line 579

@philippfrenzel Could you double check which command is running in the container?
It looks like the startup hasn't completed properly.
Which Docker base-image are you using?
Workaround: make bash
In the container ... either try to run sh src/setup.sh or yii db/create

You may need to update dmstr/yii2-db and add the command, like so https://github.com/phundament/app/blob/cd8603268186844bdd788d509c3266e5b8579efd/src/config/main.php#L200

didn't had that extension in composer at all? Isn't it added by the dmst meta package?

It is but maybe this version is too old in your app :) Which meta-package version do you have?

i had to fix tls like this:
first make sure that the virtual machine is running
docker-machine start default
regenerate TLS connection certs
docker-machine regenerate-certs default
finally, set env
eval "$(docker-machine env default)"

And it's ~2.0.0 ;)


New Field: Start Date

You have the field "MaturityDate". I miss the field "StartDate" for the indication, when the mortgage starts. Could we please have this new field before the field "MaturityDate"?
Type: see Date

According to https://github.com/swissfintechinnovations/ca-mortgage/issues/24#issuecomment-1262317642, I think this PR can be closed?

Yes, you are right. We can close PR #74 and Issue #24


Ability to set cookie SameSite

Is it possible to add the SameSite=Strict; option to the Set-Cookie header?
According to this website there should be the option to set SESSION_COOKIE_SAMESITE='Strict' but it doesn't seem to work with flask-session.
Am I doing something wrong or is it not supported?

@VilhelmPrytz according to latest version of Flask-Session using of SESSION_COOKIE_SAMESITE will no make sense.
But you could use your own redefined Response class.
Example:
class MyResponse(Response):
    def set_cookie(self, *args, **kwargs):
        cookie = dump_cookie(*args, **kwargs)
        if 'samesite' in kwargs and kwargs['samesite'] is None or 'samesite' not in kwargs:
            cookie = "{}; {}".format(cookie, b'SameSite=Lax;')

        self.headers.add(
            'Set-Cookie',
            cookie
        )

Then change response class like:
app = Flask(...)
...
app.response_class = MyResponse

Hi,
May I ask why I wouldn't make sense to use flask's SESSION_COOKIE_SAMESITE ?

I don't know why it won't make sense, but I know it's not possible to set it to strict.

@GChalony hi,
u can, but it seems like flask-session does not supports SameSite option https://github.com/fengsp/flask-session/blob/master/flask_session/sessions.py

Yeah that's what I realised reading the code, could it be added in a future version though? It seems especially weird as the native flask session supports it.

Yeah that's what I realised reading the code, could it be added in a future version though? It seems especially weird as the native flask session supports it.

Yes, it should be fairly easy to implement. But it seems the author of this project is quite inactive.

+1 This is very important to have with Chrome's recent changes. There is currently an open PR for this (#116) ready to be merged.

Fixed in #116


Visualize

[x] Add show command
[x] DOT file export
[x] PNG file export
[x] SVG file export

Coverage increased (+4.7%) to 95.455% when pulling 488413eb7f1d656cd530845e977189711db989ad on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.

Coverage increased (+3.5%) to 94.326% when pulling 92ed34807738059e8ff828b818e62ec7d039911e on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.

Coverage increased (+2.3%) to 93.056% when pulling 73af5c733f981115915ab46435a7f050618ff4ea on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.

Coverage increased (+6.08%) to 96.855% when pulling af55edd8cb75cf86f02e4e6f8b1b2cde1ffa3532 on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.

Coverage increased (+6.08%) to 96.855% when pulling 7d17ec9ac6566f383fb03858cde9cf0b76a5268c on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.

Coverage increased (+6.08%) to 96.855% when pulling 3f8f5599f478906026ba3e5e201564883d715464 on visualize into 29ec544d8cbecc2dc09816f2a7ee98d5e14fb050 on master.


wrap each for-loop call with a try-catch block

status.berkeleytime.com has gone down a few times as statuspage.io tells me to enhance our calm
instead of enhancing our calm, we wrap a try-catch that is catch-all

Well thought implementation; could be the best solution to the problem.


Unregister default minecraft command

I'm trying to unregister a default minecraft command /stats to replace it with mine but it doesn't seems to work

handler.unregister is for commands created by the CommandHandler only. If you want to remove the command, you may need to use reflection to unregister it on the vanilla CommandDispatcher


Macro: RNA builder: Cancel button doesn't work

Steps to Reproduce

Switch to Macro
Go to RNA tab
Call Duplicate and edit from context menu for any preset

Press Cancel button

Actual behavior
Nothing happens

Expected behavior
System close new preset creation dialog

Versions:
Windows 10
Chrome Version Version 123.0.6312.106 (Official Build) (64-bit)
Ketcher Version 2.21.0-rc.1 Build at 2024-04-15; 20:00:15
Indigo Toolkit Version 1.20.0-rc.1.0-g8e8ffc3c3-wasm32-wasm-clang-12.0.0
Issue found while testing https://github.com/epam/ketcher/issues/4483

Verified.
Windows 10
Chrome Version Version 124.0.6367.119 (Official Build) (64-bit)
Ketcher Version 2.21.0-rc.2 Build at 2024-05-07; 12:32:44
Indigo Toolkit Version 1.20.0-rc.2.0-g111a89f35-wasm32-wasm-clang-12.0.0


Use Batch Entries For Reservation Lists

Use batch entries instead of nodes for reservation list. This allows us to move the batch pointer into the batch allocation, reducing the memory overhead of a node to one word.
Part of https://github.com/ibraheemdev/seize/issues/5.

This does add an extra indirection when traversing reservation lists to get to the node, but until nodes are made optional for epoch tracking, it's not worth moving the reservation list pointer into the batch.


Export cmd as standard.

The cmd exported is standard-react. If I want to use standard-react in VS Code, then I need to modify my extension code here https://github.com/chenxsan/vscode-standardjs/blob/master/eslint-server/src/server.ts#L103, or maybe publish another extension.
Since standard-react is kinda an enhancement version of standard, I'm wondering if it's all right to publish it as standard in cmd.

Sorry, I would prefer to keep the standard command consistent so it always runs the mainstream version of standard.


pep8 indentation, fixes PressLabs/oxygen#1129

It's ok to have more than 80 characters, as long as it doesn't screw up the readability (https://www.youtube.com/watch?v=wf-BqAjZb8M)

There are many lines exceeding 80 characters. Those should be fixed too.


HSEARCH-2669 Remove mentions of HSEARCH-2605 in the Elasticsearch documentation

https://hibernate.atlassian.net/browse/HSEARCH-2669

nice ! merged


Implemented: code for using centralized timezone switcher in settings page (dxp/139)

Related Issues

Related Issue: https://github.com/hotwax/dxp-components/issues/139
Short Description and Why It's Useful

PR to test the use of centralized timezone configuration implemented in dxp-components.
Related pr: https://github.com/hotwax/dxp-components/pull/194
Screenshots of Visual Changes before/after (If There Are Any)

Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Will be handled differently hence closing


Remove tasks acceptance test for non-Debian builds

This commit will disable the task test on non-Debian/Ubuntu based masters.

@willmeek This is an idiom that is used in some modules, it makes sense ', :unless => UNSUPPORTED_PLATFORMS.include?(fact('osfamily')) do
https://github.com/puppetlabs/puppetlabs-postgresql/blob/master/spec/acceptance/db_spec.rb#L3


master branch: "formal argument cannot be a constant"

When using the master branch, it fails with  "formal argument cannot be a constant" when creating a scenario.
$ git log -n1
commit 0c1aed1fb550a49cf584104a005aab1d67afc014 (HEAD -> master, upstream/master, origin/master, origin/HEAD)
[...]
$ molecule create -s centos
DEBUG    Validating schema /Users/xxxxx/Git/Github/ansible-role-hardening/molecule/centos/molecule.yml.
INFO     centos scenario test matrix: dependency, create, prepare
INFO     Running centos > dependency
WARNING  Skipping, dependency is disabled.
WARNING  Skipping, dependency is disabled.
INFO     Running centos > create
DEBUG    Using selector: KqueueSelector

PLAY [Create] ******************************************************************

TASK [Create molecule instance(s)] *********************************************
Sunday 13 December 2020  00:28:08 +0100 (0:00:00.022)       0:00:00.022 *******
failed: [localhost] (item=centos) => {"ansible_loop_var": "item", "changed": false, "item": {"box": "bento/centos-8", "instance_raw_config_args": ["vbguest.installer_options = { allow_kernel_upgrade: true }"], "memory": 1024, "name": "centos", "provider_options": {"vm.boot_timeout": 600}}, "msg": "Failed to validate generated Vagrantfile: b'Vagrant failed to initialize at a very early stage:\\n\\nThere is a syntax error in the following Vagrantfile. The syntax error\\nmessage is reproduced below for convenience:\\n\\n/Users/xxxxx/.cache/molecule/ansible-role-hardening/centos/Vagrantfile:45: formal argument cannot be a constant\\n...  c.vm.provider \"VBox\" do |VBox, override|\\n...                           ^~~~\\n'"}
failed: [localhost] (item=centos-stream) => {"ansible_loop_var": "item", "changed": false, "item": {"box": "centos-stream/20201019", "box_download_checksum": "88d388ff2170430f032149323ffbba20309b8e0da924e1ad6ec5f024936c2648", "box_download_checksum_type": "sha256", "box_url": "https://cloud.centos.org/centos/8-stream/x86_64/images/CentOS-Stream-Vagrant-8-20201019.1.x86_64.vagrant-virtualbox.box", "instance_raw_config_args": ["vbguest.installer_options = { allow_kernel_upgrade: true }"], "memory": 1024, "name": "centos-stream", "provider_options": {"vm.boot_timeout": 600}}, "msg": "Failed to validate generated Vagrantfile: b'Vagrant failed to initialize at a very early stage:\\n\\nThere is a syntax error in the following Vagrantfile. The syntax error\\nmessage is reproduced below for convenience:\\n\\n/Users/xxxxx/.cache/molecule/ansible-role-hardening/centos/Vagrantfile:45: formal argument cannot be a constant\\n...  c.vm.provider \"VBox\" do |VBox, override|\\n...                           ^~~~\\n'"}

PLAY RECAP *********************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Sunday 13 December 2020  00:28:13 +0100 (0:00:04.630)       0:00:04.653 *******
===============================================================================
Create molecule instance(s) --------------------------------------------- 4.63s
CRITICAL Ansible return code was 2, command was: ansible-playbook --inventory /Users/xxxxx/.cache/molecule/ansible-role-hardening/centos/inventory --skip-tags molecule-notest,notest /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/molecule_vagrant/playbooks/create.yml
$

# Molecule managed

Vagrant.configure('2') do |config|
  if Vagrant.has_plugin?('vagrant-cachier')
    config.cache.scope = 'machine'
  end

  config.vm.define "centos-stream" do |c|
    ##
    # Box definition
    ##
    c.vm.box = "centos-stream/20201019"

    c.vm.box_url = "https://cloud.centos.org/centos/8-stream/x86_64/images/CentOS-Stream-Vagrant-8-20201019.1.x86_64.vagrant-virtualbox.box"

    ##
    # Config options
    ##

    c.vm.synced_folder ".", "/vagrant", disabled: true

    c.ssh.insert_key = true

    c.vm.hostname = "centos-stream"

    ##
    # Network
    ##

    ##
    # instance_raw_config_args
    ##
    c.vbguest.installer_options = { allow_kernel_upgrade: true }

    ##
    # Provider
    ##
    c.vm.provider "VBox" do |VBox, override|

      VBox.memory = 1024
      VBox.cpus = 2

      VBox.vm.boot_timeout = 600

    end
  end
end

Related: https://github.com/ansible-community/molecule-vagrant/pull/87 and https://github.com/ansible-community/molecule-vagrant/pull/90

hm. Are you sure about the provider name you're using ? I don't remember reading that there was 'VBox' as provider for VirtualBox. I've always seen 'virtualbox' as provider name.
If 'VBox' comes from the line:
# Can be any supported provider (VBox, Parallels, libvirt, etc)

of the README.rst file, it's not how this line was meant to be read by its author. It's a list of providers but not the provider name. I guess it's working in your case only due to the fact that vagrant is falling back to the 'virtualbox' provider when the configured provider is not available.
As regards the error message, I'm going to modify the Vagrantfile template avoid that, in case some day a vagrant provider with a first letter with upper case. I guess it's not going to happen soon but better be safe than sorry.

'config_options': {'vm.boot_timeout': 600}, 'instance_raw_config_args': ['vbguest.installer_options = { allow_kernel_upgrade: true }'], 'memory': 1024, 'name': 'centos-stream'}, 'ansible_loop_var': 'item'}

worked.
May I suggest that I write a PR that extends the README with a virtualbox example and some information about providers, so slow people like don't waste more of our time?
But why wasn't VBox caught earlier if it's not a valid provider, and how could it actually work if it was caught as a valid provider?

'config_options': {'vm.boot_timeout': 600}, 'instance_raw_config_args': ['vbguest.installer_options = { allow_kernel_upgrade: true }'], 'memory': 1024, 'name': 'centos-stream'}, 'ansible_loop_var': 'item'}

worked.

great !

May I suggest that I write a PR that extends the README with a virtualbox example and some information about providers, so slow people like don't waste more of our time?

I'm not sure what you need ? You can send a PR and I'll review but no promise about the merge. It would be nice to avoid adding a specific example for each provider.
About the provider_options vs config_options, the doc is mentioning the config.ssh namespace and not config.vm, so may something is missing. The config_options is for all config.* namespaces. btw, you could have used config_options to set the config.vm.box_download_checksum* settings too instead of patching.
And for 'VBox' vs 'virtualbox', I can only guess that the doc primary author is assuming that a user of molecule-vagrant is already familiar with vagrant and would use 'virtualbox' naturally.

But why wasn't VBox caught earlier if it's not a valid provider, and how could it actually work if it was caught as a valid provider?

I don't know. I can only guess that people used 'virtualbox' as they were already using vagrant with vbox or that vagrant is defaulting to virtualbox provider if the one specified is not available.
And for the original error of this bug, it's due to my change removing the vagrant.yml file. I've used the provider name as variable in the Vagrantfile and the ruby language consider that every symbol starting with a uppercase, it's a constant but here, I want a variable. The "formal argument cannot be a constant" means that I've tried to use a constant as variable and it was not detected since all providers are in lower case.

Regarding the README it was just about a small explanation about the providers without any short versions of the names etc.
And as you said config.vm.provider "virtualbox" do |vb| is the correct way in a Vagrantfile, but I just followed the documentation and used VBox without giving it much thought. And it worked (tm).


Backport: Remove deprecated Fluentd config

Issue #22320
Original issue #22219
Original PR #21969

Hello @aiwantaozi! Can you please take a moment to review this PR?

LGTM

Thank you @aiwantaozi!
@cjellick, can you please merge this PR? I’m sure it won’t take much of your time)

Hi @cjellick,
I saw the 2.2.9-alpha release and wanted to remind of this PR that was already approved by your colleague.


cpupower-gui is broken

Describe the bug
cpupower-gui just doesn't start at all after adding to configuration and rebuilding. It seems like it relies on a systemd service called cpupower-gui-helper, however it doesn't appear on systemctl list-units at all and you can't start it.
Screenshots

Notify maintainers
@unode

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
nix-configuration on  flakes [$!] via ❄  impure (nix-shell-env)
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.3, NixOS, 24.05 (Uakari), 24.05.20240609.2819fff`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.22.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/store/giq1qbcwfx5gq0g9jf6id0b3m55a860j-source`

Add a :+1: reaction to issues you find important.

Do you have services.cpupower-gui.enable set?

@unode I didn't know that was a thing sorry

No worries. Some software in nixpkgs, especially that which require system services often has such configuration that enables said services.
Um abraço!


WIP: Removed a landmine

@vsrally @rallyhealth/engineers
This method is both implicit and unsound. It is a landmine, and we need to remove it ASAP.
Technically, this is major change, so we might just want to remove it.

Why is it unsafe?

I would vote for fixing it properly or removing it entirely if it's really that bad.

My current plan is to release a 3.0.0 version with a fixed version of this method.
@slustbader the issue was that this function accepts implicit conversions to / from string, and even implements an unsound default parameter that uses .toString (YIKES!) The solution is to use a special ReadsKey / WritesKey traits that convert to String. This will prevent this implicit from getting picked up and accidentally serializing json objects unsoundly.

Ok, I have a working branch with Play 2.7 / Scala 2.13.0-M4 support, I'm going to start pushing the commits through to master.
This first change will invalidate the implicit resolution of formatMap without breaking binary compatibility.
The remaining changes will be to add support for an improved version of this implicit, remove support for Play 2.3, and then add support for Play 2.6 and 2.7.0-M1.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@849e295). Click here to learn what that means.
The diff coverage is 0%.

@@          Coverage Diff           @@
##             master   #25   +/-   ##
======================================
  Coverage          ?    0%
======================================
  Files             ?    49
  Lines             ?   837
  Branches          ?    21
======================================
  Hits              ?     0
  Misses            ?   837
  Partials          ?     0

Impacted Files
Coverage Δ

...n/scala/play/api/libs/json/ops/JsonImplicits.scala
0% <ø> (ø)

...rc/main/scala/play/api/libs/json/ops/package.scala
0% <0%> (ø)

Continue to review full report at Codecov.

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


Prepare DockerHub

Let's use our fancy metagenomics group account for our public app.
@pbelmann, can you take care of it? I can help of course, if needed.

Done: https://registry.hub.docker.com/u/metagenomics/2015-biogas-cebitec/


Implemented an Express middleware for Formidable.

Hiya,
First of all, I appreciate this great module. I personally prefer this to other similar modules as it provides more flexibility.
I've implemented a small Express middleware for Formidable, as I couldn't find native support between each other or other 3rd-party packages in the latest versions of both. The package's link is below.
https://github.com/noraesae/express-formidable
Unless it bothers you, could it be mentioned in a documentation or readme? It may be able to help others who want to use this with Express easily.
Many thanks!

Can I use express-formidable only for post requests from a form when uploading files like songs and videos and at the same time use bodyParser "urlencoded" and "json" functions for the rest? If yes, could you please show me a concrete example?

For others who have made it to this thread, looks like the @nelson-brochado question is answered here:  https://github.com/noraesae/express-formidable/issues/1#issuecomment-251713907

express-formidable no more overwrites req.body in 1.0. Now you don't need to worry about conflict between bodyParser and express-formidable.

Looks too easy, but okey. Would be good to pass options directly to IncomingForm.
For more inspiration you may look at https://github.com/tunnckocore/koa-better-body :) Before few years, I was going to do express-better-body, but yea... to busy and I'm mainly on koa. Which reminds me that I should start work on koa.io, damn.. :D

Yes, actually Formidable is easy enough to use with Express by itself. I think I close this issue now.
BTW, koa-better-body looks nice. Great work!

Yea, thanks! It's pretty old and one of the first middlewares.


Add Cloud Functions support for java

We implemented most environments in Java, but Functions still is incomplete. We may need to refactor the entire deployable away from springboot to make it work properly. I may need help from someone with more java experience

I think we can close it as a duplication of the #56

For this issue, I was referencing creating an envctl script for Cloud Functions, so we can run tests against that environment. It looks like the code I wrote for the others isn't so easy to deploy on Functions

I will work to ensure that the provided code (in Java) works with PubSub and logs the message sent via data (expecting some kind of Json there). We can decide how to approach the envctl part when you are back.


Update the game over message

Update the game over message so people know how to play again!

Comment added


docs v0.7.3 fix event enums and groups name

closes #1889
closes #2003
closes #1866

Feel like knocking this one out too? https://github.com/linode/manager/issues/2003

Coverage remained the same at 79.117% when pulling de6a0943d848f80eb8c7443b4a01b5a307ae6d03 on mparke:fix-event-enums into 73494cd06161e109ab5939883c9ca2f91cae8f80 on linode:master.

Coverage remained the same at 79.117% when pulling 1bf1ca554bdc0476bb464bea1001e045fd92a11d on mparke:fix-event-enums into e65c551d91cf2025c9375828862ce95d1b62a952 on linode:master.

Coverage remained the same at 79.117% when pulling 1bf1ca554bdc0476bb464bea1001e045fd92a11d on mparke:fix-event-enums into e65c551d91cf2025c9375828862ce95d1b62a952 on linode:master.

Coverage decreased (-0.03%) to 79.09% when pulling ee73bef257b7a25ac1a9aedd45cd980f00640120 on mparke:fix-event-enums into 65b144088b5969a8f11bb0188d21a1eaf9947c12 on linode:master.


sf::StencilBuffer not applied when drawn from RenderTexture to RenderWindow

Prerequisite Checklist

[X] I searched for existing issues to prevent duplicates
[X] I searched for existing discussions on the forum to prevent duplicates
[X] I am here to report an issue and not to just ask a question or look for help (use the forum or Discord instead)

Describe your issue here
sf::StencilBuffer appears to not work when drawn onto an sf::RenderTexture which is then drawn to an sf::RenderWindow.
It behaves correctly when drawn directly onto an sf::RenderWindow. The issue is strictly sf::RenderTexture -> sf::RenderWindow.
It behaves correctly when drawn onto an sf::RenderTexture which is then copied to an sf::Image which explains why we are not getting failing tests.
I don't understand all the intricacies of SFML's OpenGL implementation (or OpenGL for that matter) so I have limited ability to dive into this. I did find that the issue is fixed if we force a resetGLStates() first thing within RenderTarget::setupDraw(bool useVertexCache, const RenderStates& states).
https://github.com/SFML/SFML/blob/master/src/SFML/Graphics/RenderTarget.cpp#L833
To me this implies that the issue may be with caching the state, but this is just a shot in the dark.
Your Environment

OS / distro / window manager: Linux / Fedora 40 / Gnome 46.2
SFML version: The latest master, d99d673330fa1b3d37d3dc09a147c6ad45df2c1b
Compiler / toolchain: gcc 14.1.1

Steps to reproduce
This is the official StencilBuffer example minimally modified to draw onto an intermediate RenderTexture
#include <SFML/Graphics.hpp>
#include <cstdlib>

int main()
{
    auto contextSettings = sf::ContextSettings{0 /* depthBits */, 8 /* stencilBits */};

    sf::RenderWindow window(sf::VideoMode({600, 600}),
                            "SFML Stencil",
                            sf::Style::Titlebar | sf::Style::Close,
                            sf::State::Windowed,
                            contextSettings);
    window.setVerticalSyncEnabled(true);

    sf::RenderTexture renderTexture = sf::RenderTexture::create(sf::Vector2u(600, 600), contextSettings).value();

    sf::RectangleShape red({500, 50});
    red.setFillColor(sf::Color::Red);
    red.setPosition({270, 70});
    red.setRotation(sf::degrees(60));

    sf::RectangleShape green({500, 50});
    green.setFillColor(sf::Color::Green);
    green.setPosition({370, 100});
    green.setRotation(sf::degrees(120));

    sf::RectangleShape blue({500, 50});
    blue.setFillColor(sf::Color::Blue);
    blue.setPosition({550, 470});
    blue.setRotation(sf::degrees(180));

    while (window.isOpen())
    {
        while (const auto event = window.pollEvent())
        {
            if (event.is<sf::Event::Closed>())
            {
                window.close();
                break;
            }
        }

    	window.clear(sf::Color::Black, 0);
    	renderTexture.clear(sf::Color::Black, 0);

        renderTexture.draw(red,
                    sf::StencilMode{sf::StencilComparison::Always, sf::StencilUpdateOperation::Replace, 3, ~0u, false});

        renderTexture.draw(green,
                    sf::StencilMode{sf::StencilComparison::Always, sf::StencilUpdateOperation::Replace, 1, ~0u, false});

        renderTexture.draw(blue,
                    sf::StencilMode{sf::StencilComparison::Greater, sf::StencilUpdateOperation::Replace, 2, ~0u, false});

        renderTexture.display();
        window.draw(sf::Sprite(renderTexture.getTexture()));
        window.display();
    }

    return EXIT_SUCCESS;
}

Expected behavior

Actual behavior

Doing a bit of investigation. Instead of calling resetGLStates in setupDraw, it is sufficient to call m_cache.stencilEnabled = false; to fix the issue:
if (!m_cache.glStatesSet)
    resetGLStates();

m_cache.stencilEnabled = false; // <---

Also, calling renderTexture.setActive(false) before drawing the shapes fixes the issue, probably because m_cache.enable is set to false.

It also appears to work correctly for the first frame drawn, which is also probably because m_cache.enable is set to false.

It also appears to work correctly for the first frame drawn. I'm assuming this is because m_cache.glStatesSet would be false for that frame (haven't verified this).

Creating the RenderTexture every frame inside the loop from scratch also fixes the issue.

I think I understand the problem:

The first call to resetGLStates for the render texture calls glDisable(GL_STENCIL_TEST).
Then, the subsequent call to applyStencilMode calls glEnable(GL_STENCIL_TEST).
Then, we get to window.draw(sf::Sprite(renderTexture.getTexture())).
The setupDraw call for the sprite draw calls resetGLStates, which sets  glDisable(GL_STENCIL_TEST).
glEnable(GL_STENCIL_TEST) is never called again.

Adding glEnable(GL_STENCIL_TEST) right after window.draw(sf::Sprite(renderTexture.getTexture())) fixes the issue.

Another possible fix is doing this in applyStencilMode:
// Apply the stencil mode
if (!m_cache.stencilEnabled || !glIsEnabled(GL_STENCIL_TEST))

I don't know what the "correct" fix is. @binary1248?

Adding glEnable(GL_STENCIL_TEST) right after window.draw(sf::Sprite(renderTexture.getTexture())) fixes the issue.

if (!m_cache.stencilEnabled || !glIsEnabled(GL_STENCIL_TEST))

It's possible I'm just doing something wrong somewhere, but I don't think either of these fix the issue in all cases. Some context first...
The reason I found this bug is because I had implemented veronoi split screen in the past by using two sf::RenderTextures. I rendered the scene twice, one for each render texture, and then rendered the relevant portions from each texture onto the window.
I'm now rendering the scene onto a single render texture and using StencilBuffers to only render the relevant portion.
I attempted to use both of the proposed fixes in my project (glEnable(GL_STENCIL_TEST) in usercode as well as inserting the call after // Apply the stencil mode) and neither worked.
It does fix it for the simple example case posted in the initial issue though. For my project, always calling resetGLStates() in setupDraw fixes it. Obviously this isn't a suitable fix though.
I can try to extract what my project is doing into a complete minimal example if people think it would be useful but I'd rather not if it won't actually be useful.
At a high level,
// defining the part of the screen we want content to be visible
sf::RenderStates stencilState;
stencilState.stencilMode.stencilComparison = sf::StencilComparison::Always;
stencilState.stencilMode.stencilUpdateOperation = sf::StencilUpdateOperation::Replace;
stencilState.stencilMode.stencilReference = stencilValue;
stencilState.stencilMode.stencilMask = 0xFF;
stencilState.stencilMode.stencilOnly = true;

renderTexture.draw(polygon, stencilState);

// ...
// drawing the content
sf::RenderStates player1States = states;
player1States.stencilMode.stencilComparison = sf::StencilComparison::Equal;
player1States.stencilMode.stencilReference = sf::StencilValue(1);
player1States.stencilMode.stencilMask = 0xFF;
renderTexture.draw(drawable, player1States);

I felt it was lame of me to not provide a full example in my last response. I'm sorry about that.
This example will work if you call resetGLStates, but glEnable(GL_STENCIL_TEST) is not sufficient.
#include <SFML/OpenGL.hpp>
#include <SFML/Graphics.hpp>
#include <vector>
#include <iostream>

void applyStencilForLeftHalfScreen(sf::RenderTexture& renderTexture)
{
    std::vector<sf::Vector2f> points = {
        {0, 0},
        {300.0f, 0},
        {300.0f, 600},
        {0, 600}
    };

    sf::VertexArray polygon(sf::PrimitiveType::TriangleFan);
    for (const auto& point : points)
    {
        polygon.append(sf::Vertex(point));
    }

    sf::RenderStates stencilState;
    stencilState.stencilMode.stencilComparison = sf::StencilComparison::Always;
    stencilState.stencilMode.stencilUpdateOperation = sf::StencilUpdateOperation::Replace;
    stencilState.stencilMode.stencilReference = 1;
    stencilState.stencilMode.stencilMask = 0xFF;
    stencilState.stencilMode.stencilOnly = true;

    renderTexture.draw(polygon, stencilState);
}

int main()
{
    auto contextSettings = sf::ContextSettings{0 /* depthBits */, 8 /* stencilBits */};

    sf::RenderWindow window(sf::VideoMode({600, 600}),
                            "SFML Stencil",
                            sf::Style::Titlebar | sf::Style::Close,
                            sf::State::Windowed,
                            contextSettings);
    window.setVerticalSyncEnabled(true);

    sf::RenderTexture renderTexture = sf::RenderTexture::create(sf::Vector2u(600, 600), contextSettings).value();

    sf::RectangleShape fullScreenShape({600, 600});
    fullScreenShape.setFillColor(sf::Color::Yellow);

    while (window.isOpen())
    {
        while (const auto event = window.pollEvent())
        {
            if (event.is<sf::Event::Closed>())
            {
                window.close();
                break;
            }
        }

        window.clear(sf::Color::Black, 0);
        renderTexture.clear(sf::Color::Black, 0);

        // Apply stencil for left half of the screen
        applyStencilForLeftHalfScreen(renderTexture);

        // Draw a full-screen rectangle but only the left half should be visible due to the stencil
        sf::RenderStates leftStates;
        leftStates.stencilMode.stencilComparison = sf::StencilComparison::Equal;
        leftStates.stencilMode.stencilReference = 1;
        leftStates.stencilMode.stencilMask = 0xFF;
        renderTexture.draw(fullScreenShape, leftStates);

        renderTexture.display();

        // Draw render texture to window
        window.draw(sf::Sprite(renderTexture.getTexture()));

        // Doesn't fix the issue
        glEnable(GL_STENCIL_TEST);

        window.display();
    }

    return EXIT_SUCCESS;
}

Expected

Actual

Should be fixed in #3114.


🐛 BUG: Debian packages are out-of-date

What version of nebula are you using? (nebula -version)
1.6.1
What operating system are you using?
Linux Debian-based
Describe the Bug
Official package on Debian-based distro (like Debian, Ubuntu, Linux Mint, PopOS, else) is 2 year old deprecated (installing 1.6.1 only) leading to some security and performance issue (like recent #1180 ).
Since you already have a github action workflow uploading your releases on Github Release, it shouldn't be too complicated to enhance them to update package manager. Especially considering ArchLinux (for instance) being up to date with version 1.9.4.
Logs from affected hosts
Not relevant
Config files from affected hosts
Not relevant

I've asked for an updated version to be included in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083128


[jvm-packages] better fix for shutdown applications

closes https://github.com/dmlc/xgboost/issues/4080

tested in prod environment, now it shutdown sparkcontext directly instead of tweaking the types of exception


[FEATURE] Add a new t:removeSQLComments transformation

Summary
Writing rules for SQLi is difficult enough. Also, there could be plenty of evasions by using /**/ inside partial SQL queries.
Basic example

Raw:

select tags from tags WHERE 1=0 OR'{"name":"asd"}'?|/**/array/**/[/**/'a'/**/,'name'];

With t:removeSQLComments applied:

select tags from tags WHERE 1=0 OR'{"name":"asd"}'?|array['a','name'];

Motivation
By creating a new t:removeSQLComments transformation, that substitutes everything commented out using /**/, regular expressions to catch injections will get way simpler and cover more cases.
Caveat: some databases will interpret commands inside comments. Luckily this can be handled by an specific rule for this case.
Edge cases

we need to review if space needs to be substituted for the actual command to work, or we can remove everything that is commented. Example:
WHERE 1=0 OR a=/**/b -> WHERE 1=0 OR a=b
vs.
WHERE 1=0 OR a=/**/b -> WHERE 1=0 OR a= b (/**/ is substituted for a "space" character   )

Isn't it redundant with replaceComments/removeCommentsChar/removeComments?

🤦 Good question. I need to test it. For now I'm closing.


W391 - switched anti-pattern with best practice

Thanks for this great resource @grantmcconnaughey! W391 anti-pattern and best practice appear to be switched incorrectly. Can you swap them, or would you accept a pull request to resolve the issue?

PRs are always welcome!


Build failed

Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=249669
Changes: https://github.com/Microsoft/vscode/compare/48996f7...7f21faa
Recent builds failing on installing dependencies.

This happens after updating  xterm.js right after it's published due to terrapin. Not sure if there's anything we can do but I think @joaomoreno knows the most here.

Terrapin says this is as designed. They have not provided any workaround so far. Our only choice for now is to wait a few minutes after publishing.


Niloofar / Bug - Fix Typescript errors in deriv-go

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

LGTM! 👍


GettingStarted.md redirects to documentation home after selecting platform

This will not send an event to the display function:
iOS
Android
OS:
Mac
Linux
Windows

This requires the event:
function display(type, value) {
  var container = document.getElementsByTagName('block')[0].parentNode;
  container.className = 'display-' + type + '-' + value + ' ' +
    container.className.replace(RegExp('display-' + type + '-[a-z]+ ?'), '');
  event && event.preventDefault();
}

Consequentially, instead of showing the correct documentation it links to the homepage.
Also, doing this with JavaScript seems somewhat unnecessary as the same result could have been achieved using , some CSS using :target and an ID on the target element. (Just my two cents though, you may actually not want to have the platform in the URL fragment.)

Looks like it's fixed now. Would still prefer it if documentation would be hotlink-able; now I have to click the right button every time I visit the page.


CPP: Rename/relocate some queries and libraries

These are all recently contributed files, so the aim is to rename them now before they become part of a release and it would be potentially more disruptive to rename them.
Reasons are given on each commit - please discuss if you disagree with anything or have better suggestions.

A library named semmle.code.cpp.controlflow.VirtualDispatch is likely to be considered the official C++ virtual dispatch library. I'm not very fond of that since it's received no testing for performance or correctness at scale. I'd prefer placing it in the same directory as the one query that uses it. Alternatively, name it semmle.code.cpp.controlflow.VirtualDispatchOverapproximationPrototype.
The C# and Java libraries use semmle.code.csharp.dispatch.Dispatch and semmle.code.java.dispatch.VirtualDispatch respectively, so I'll argue for keeping that directory even if it only has a single file.

Fair enough.  So would you prefer semmle.code.cpp.dispatch.VirtualDispatch (i.e. what it was before) or perhaps semmle.code.cpp.dispatch.VirtualDispatchPrototype?

I prefer semmle.code.cpp.dispatch.VirtualDispatchPrototype. Then there's room for adding a semmle.code.cpp.dispatch.VirtualDispatch library later, without having to consider backwards compatibility.

The name BufferAccess.qll is too generic for what this library does. It doesn't seem to be a library that's intended to be used in other queries. I suggest inlining it into the one query that uses it. We can later fold it into existing taint-tracking rules.

Good idea.  I wasn't keen on that file (particularly as we already have a fairly general purpose BufferAccess library), but I hadn't realized it could be removed (inlined into a single query) so easily.

To follow our usual naming conventions, the NtohlArrayGood.cpp file should be named NtohlArrayNoBound-good.cpp. Same for Bad.

Seems reasonable, done.

I prefer semmle.code.cpp.dispatch.VirtualDispatchPrototype.

Done.
All comments addressed.

The name BufferAccess.qll is too generic for what this library does. It doesn't seem to be a library that's intended to be used in other queries. I suggest inlining it into the one query that uses it. We can later fold it into existing taint-tracking rules.

I agree that the name is too generic, but I think it will be useful to have an umbrella class for expressions that do pointer arithmetic and dereference the result either directly or by calling a library function. Right now each query that looks for overflows or tainted indexes defines its own set of sinks, and there's sometimes gaps in coverage as a result.

I think it will be useful to have an umbrella class for expressions that do pointer arithmetic and dereference the result either directly or by calling a library function.

We already have the models library, and the (existing) security\BufferAccess.qll library.  There are some slight differences in coverage (e.g. I don't think we model recv or have an equivalent of PointerArithmeticAccess in security\BufferAccess.qll yet?), but I think NtohlArrayNoBound.qll can be updated to use existing libraries.


I'm using UWB to play html5 file with embedded video (video in local folder) but it doesn't work. It shows error "[Web Browser]: [CEF Engine Console]: Uncaught (in promise) NotSupportedError: The element has no supported sources.". I tried different ways: open html5 as file, open via localhost/remote host but it didn't work. It only worked with embedded video from youtube.

I'm using UWB to play html5 file with embedded video (video in local folder) but it doesn't work. It shows error "[Web Browser]: [CEF Engine Console]: Uncaught (in promise) NotSupportedError: The element has no supported sources.". I tried different ways: open html5 as file, open via localhost/remote host but it didn't work. It only worked with embedded video from youtube.
Anyone knows how to fix this, please?
Thanks in advanced!
Originally posted by @longkakavn in https://github.com/Voltstro-Studios/UnityWebBrowser/discussions/245

Don't open an issue for a question or discussion.


Address -Wno-unused-but-set-variable

imodel-native-internal: https://github.com/iTwin/imodel-native-internal/pull/637
CI machines use clang 13 on linux. Installing 13 on Ubuntu 24.04 turned out to be quite tricky.
14 has some issues with consteval in std::chrono.
15 produces a slew of warnings re: variables that are assigned to but never used.
16 and 17 produce additional warnings about implicit functions.
15 seemed like the easiest one to get compiling.
Most of the unused variables are in GeomLibs where they mostly appear intended for debugging.
So I was conservative, mostly leaving them intact and silencing the warning via UNUSED_VARIABLE.
I did remove static from a handful of them.

I'm OK with removing unused debug vars. I'll make a commit to this branch.


Checkout component to v3.18.2

Summary

Downgraded back to v3.18.2 since Swish doesn't work with version 20
Tested scenarios

Ran e2e tests
Fixed issue:

the .map was never added to SG and it seems to work without it


Compiler Error: Object is possibly 'undefined' for Map entry even though it is impossible to be undefined

Bug Report
🔎 Search Terms
Map, TS2532: Object is possibly 'undefined'., impossible
🕗 Version & Regression Information
4.1.6, 4.4.4
⏯ Playground Link
const myMap = new Map<string, number[]>();
const key = 'myKey';

if (!myMap.has(key)) {
  myMap.set(key, []);
}

myMap.get(key).push(1, 2, 3);

Workbench Repro
💻 Code
🙁 Actual behavior
Compiler Error: TS2532: Object is possibly 'undefined'.

🙂 Expected behavior
No compiler error, because by analyzing the control flow it can be deduced that it is impossible for myMap.get(key) to be undefined.

Duplicate of #13086. Used search terms: map has in:title


Add instructions for installing via flatpak

closes #18
The PR on flathub was just merged, so it might take a few more hours until it's available

Thanks. Btw, can you add me as a maintainer on the flatpack repo that they created for the plugin? Just in case.

Doesn't seem like I have access to the settings there, I asked on the original PR:
https://github.com/flathub/flathub/pull/4065#issuecomment-1734284602


Add an optimize flag to the metric specification

This PR adds an optimize field to the metric definition.

This is still waiting on backend changes to be deployed.

Are we missing v1beta1 and the new crd definitions?

That's a different PR.

Whoops, missed this was not the controller repo.


chore(main): release 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-06-27)
Features

add parse_spanned function (#32) (632a479)

Bug Fixes

fix Darwin compilation (086f847)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vhyrro/toml-edit.lua/releases/tag/v0.4.0 :sunflower:


Feature request: Make Program.sourceFileToPackageName public

Suggestion
🔍 Search Terms
sourceFileToPackageName
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
I would like to request Program.sourceFileToPackageName to be marked as public (or rather, un-marked as internal)
📃 Motivating Example & Use Case
In typescript-eslint, I have recently worked on a way to specify a type including its source (local/package/lib). Well, as part of that, we need to know if a type is declared in a particular package (well, or a corresponding @types package). Currently, this is implemented by just checking the type's declaration files for the node_modules/package_name substring - a rather crude approach.
I stumbled upon Program.sourceFileToPackageName, which as far as I understand is TypeScript doing the same thing - recording the package in which the type was declared, if any. So I would like to use that to prevent any possible discrepancy between TS and typescript-eslint. Additionally, it would solve the problem of not everyone having their dependencies in node_modules - with things like type roots and similar.
Corresponding typescript-eslint issue: typescript-eslint/typescript-eslint#6861

@weswigham @sheetalkamat any concerns?

FYI @sheetalkamat - we need this API (or an equivalent) in typescript-eslint to properly support node:test in options for the @typescript-eslint/no-floating-promises rule. The chain of causality is:

@typescript-eslint/no-floating-promises detects Promises that are created (e.g. returned from a function call) but not handled (e.g. stored in a variable)
node:test intentionally has some of its functions return Promises that generally don't need to be handled: https://github.com/nodejs/node/issues/51292
https://github.com/typescript-eslint/typescript-eslint/issues/8404 tracks adding in an option to allowlist specific APIs, e.g.:"@typescript-eslint/no-floating-promises": ["error", {
  "allowForKnownSafePromiseReturns": [
    { "from": "package", "name": "it", "package": "node:test" }
  ]
}]

In order to map from node:test to<EMAIL_ADDRESS>we think we'd need Program.sourceFileToPackageName

...however, now I'm not positive what the right strategy is. If a single .d.ts file has multiple declare modules in it, this might not hold up. Do you have any advice for what we should do here?


Logging

As a developer in scrum team
I need a function that can track and log the status of the Inventory System
So that I could better understand what the system is doing
Details and Assumptions

Python has a logging module, and we can make use of it.

Acceptance Criteria
Given a running Inventory System
When a CRUD API is called
Then log the console output, indicating what happened and whether the request succeeded.

I think we should be more specific on the title. For example, "Logging status inventory system"


Updating defaults.py url

This fixes issue #5 : defaults.py is not present anymore in latest version of Singularity, up to v2.6.0 the location should be https://github.com/singularityware/singularity/blob/2.6.0/libexec/python/defaults.py

@jmstover  Issue #5 was pointed out a few hours ago: there was a dead link to defaults.py (since it's from master) and I added this one redirecting to its location in 2.6.0. Is this correct? thanks


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Collected data form: Measure against target drop-down menu details

The following details were inadvertently lost when I was pulling out the Collected Data details from various issues related to creating targets.
ACCEPTANCE CRITERIA
1. We do NOT display the target value in the "Measure against target" drop-down menu. We received feedback from the PaQ team that including the value of each target is unnecessary and actually confusing in this context. It makes you stop and worry about whether your data record actuals are somehow being calculated against the targets.
2. For annual, semi-annual, tri-annual, and quarterly targets, we show the target period name and date range with a bit of space in between each target -- similar to how we display it in the table itself. Here's a mocked up example. Others can be found in the design wiki.

3. For monthly targets, display the month and year, like so:

According to the W3C standards at https://www.w3.org/TR/2011/WD-html-markup-20110113/option.html , the option tag for a select element is is limited to "Normal character Data". The definition of "Normal Character Data" is https://www.w3.org/TR/2011/WD-html-markup-20110113/syntax.html#normal-character-data.  So creating multi-line options within a select box isn't really doable unless we use a third-party library, which will add to the loading time of the page.

Thanks for looking into this, @mahmoodkhan. I think we can put this aside for now, as the current solution is readable and we have many other higher priority UI issues to tackle. I'm going to close this story.


[bug] App won't launch on android emulator

Describe the bug
Tauri doesn't launch Android app inside emulator.

Reproduction

Create a Tauri app with the new mobile alpha
Install Android Studio and create an emulator
Launch tauri android dev
Emulator opens but app doesn't appear inside

Expected behavior
The app should be visible after the emulator is launched.
Platform and versions
Environment
› OS: Fedora 37.0.0 X64
› Node.js: 19.0.0
› npm: 8.19.2
› pnpm: Not installed!
› yarn: Not installed!
› rustup: 1.25.1
› rustc: 1.65.0
› cargo: 1.65.0
› Rust toolchain: stable-x86_64-unknown-linux-gnu
Packages
› @tauri-apps/cli [NPM]: 2.0.0-alpha.0
› @tauri-apps/api [NPM]: 2.0.0-alpha.0
› tauri [RUST]: 2.0.0-alpha.0,
› tauri-build [RUST]: 2.0.0-alpha.0,
› tao [RUST]: 0.15.6,
› wry [RUST]: 0.23.3,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:3000/
› framework: React (Next.js)
› bundler: Webpack
App directory structure
├─ public
├─ prisma
├─ node_modules
├─ .git
├─ .github
├─ src-tauri
├─ src
└─ .next
Stack trace
❯ npm run tauri android dev --verbose
npm verb cli /home/arcanist/.nvm/versions/node/v19.0.0/bin/node /usr/local/bin/npm
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 2ms
npm timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/home/arcanist/Documents/Coding/test/my-t3-app/.npmrc Completed in 1ms
npm timing config:load:project Completed in 5ms
npm timing config:load:file:/home/arcanist/.npmrc Completed in 0ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/home/arcanist/.nvm/versions/node/v19.0.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 17ms
npm timing npm:load:configload Completed in 17ms
npm timing npm:load:mkdirpcache Completed in 6ms
npm timing npm:load:mkdirplogs Completed in 1ms
npm verb title npm run tauri android dev
npm verb argv "run" "tauri" "android" "dev" "--loglevel" "verbose"
npm timing npm:load:setTitle Completed in 2ms
npm timing config:load:flatten Completed in 4ms
npm timing npm:load:display Completed in 10ms
npm verb logfile logs-max:10 dir:/home/arcanist/.npm/_logs
npm verb logfile /home/arcanist/.npm/_logs/2022-12-10T23_12_01_576Z-debug-0.log
npm timing npm:load:logFile Completed in 8ms
npm timing npm:load:timers Completed in 1ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 46ms

><EMAIL_ADDRESS>tauri
> tauri android dev

     Running BeforeDevCommand (`npm run dev`)leted in 46ms
npm verb cli /home/arcanist/.nvm/versions/node/v19.0.0/bin/node /usr/local/bin/npm
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 3ms
npm timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/home/arcanist/Documents/Coding/test/my-t3-app/.npmrc Completed in 0ms
npm timing config:load:project Completed in 5ms
npm timing config:load:file:/home/arcanist/.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:/home/arcanist/.nvm/versions/node/v19.0.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 2ms
npm timing config:load:credentials Completed in 2ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 21ms
npm timing npm:load:configload Completed in 21ms
npm timing npm:load:mkdirpcache Completed in 8ms
npm timing npm:load:mkdirplogs Completed in 1ms
npm verb title npm run dev
npm verb argv "run" "dev"
npm timing npm:load:setTitle Completed in 2ms
npm timing config:load:flatten Completed in 5ms
npm timing npm:load:display Completed in 11ms
npm verb logfile logs-max:10 dir:/home/arcanist/.npm/_logs
npm verb logfile /home/arcanist/.npm/_logs/2022-12-10T23_12_03_521Z-debug-0.log
npm timing npm:load:logFile Completed in 8ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 53msoad Completed in 46ms

><EMAIL_ADDRESS>dev
> next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /home/arcanist/Documents/Coding/test/my-t3-app/.env
        Info detected host target triple "x86_64-unknown-linux-gnu"
INFO    | Android emulator version <IP_ADDRESS> (build_id 9189900) (CL:N/A)
emulator: INFO: Found systemPath /home/arcanist/Android/Sdk/system-images/android-33/google_apis/x86_64/
INFO    | Duplicate loglines will be removed, if you wish to see each indiviudal line launch with the -log-nofilter flag.
INFO    | Info: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. ((null):0, (null))

Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
event - compiled client and server successfully in 976 ms (275 modules)
INFO    | added library /home/arcanist/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so
INFO    | configAndStartRenderer: setting vsync to 60 hzms
INFO    | Sending adb public key [QAAAAJPdAFVlN3r1mYAb3jvfX4vM2dJ8pVcz4WqDd9wqbvHr/Dxc4vs5vJKwd6zntF9IokPnDDEhTwDmKI+eGdubrw9CN+dmdQ0nj25uUhBvUFaIUqew5dMgg0Ys9eSKOsPVHPBV2/FNmtmyOTNmKuKiwx0PW363ezolzjwXSBF1nwPDXShkzhvGGJjWOf6XlXRBvQOkaskH82aWKlmA1U/ovFvdAw8mdtdO5QGSlc/eIooYKynu8yEzrBbYnM8+sB1d0tAjPD2nI4NNWuWxq//jC7wmZq/KUbEtAvt5g3UpGRBEVNKZqzbGm51HYCZCOD2wVL1DDqybCk2PYZnfIqeW6uaUFtyxjYp2zS6qSY82ZAdf+JbPHbB12brdFqu/Y08AuPh1AHcaOOz6DQ7rDzZWE1Rvgt93fN4G7IHa2ejKoURpDXrac84RzycRORC1XQ6Vld3wZka8r+/eGMaI5uWsCRFyiOR6z6TpOCQnymRk9KVB46PtIcEYa9Lbo9DgcU7gIIDuX8IULBrS6tVn4F7aJtDxNgBx6fFKgYtnb9izjTV7b0tzmiX0t0aKBts0Myy+mPu0mmNulHP8dzqKtpUHkDldC0gNPzqw0iLOcfEJ0eoGt3esPW7GT1mUnXZP9EXHvT7FxvMvAjuN5PwAs1KIvkEYrfJX947zSguXCXd8sfUHbrYtnQEAAQA= arcanist@framework]
INFO    | injectedQemuChannel!
INFO    | Informing listeners of injection.
INFO    | Rootcanal has  been activated.
WARNING | *** No gRPC protection active, consider launching with the -grpc-use-jwt flag.***
INFO    | Started GRPC server at <IP_ADDRESS>:8554, security: Local, auth: none
INFO    | Advertising in: /run/user/1000/avd/running/pid_38965.ini
INFO    | setDisplayConfigs w 1440 h 3120 dpiX 560 dpiY 560
INFO    | Info: Sandboxing disabled by user. ((null):0, (null))

Additional context
Confirmed by another user in Discord.
I was able to get the app to launch on my actual Android device using the option to connect via WiFi in Android Studio, but there's no webview:

get same issue

started server on <IP_ADDRESS>:3000, url: http://localhost:3000/
Did you configure next.js for mobile? That might be the reason of the blank screen.

Now for the emulator problem I need more information. Can you try running from Android Studio with tauri android dev --open?

Did you configure next.js for mobile?
I thought I did, but I realize I didn't do it correctly. I still can't seem to launch the emulator even with tauri android dev --open.

I can't figure out how to get anything other than the emulator to launch with tauri android dev --open and it only shows a blank Android device without my app installed/
If I open the generated Android app directory with Android Studio, I'm able to build it and upload it to my actual phone, but it looks like the second screenshot in my issue report above. Even after making the suggested changes to to the Next.js config, I only have the app title showing up on the screen.

I'm able to access my app by visiting http://<IP_ADDRESS>:3000 in the Chrome browser inside the emulator:

Thanks to ChatGPT for explaining this to me. I changed the "Active Build Variant" to x86_64 (it was set to arm previously) and now I have the app launching in the emulator :partying_face:

If this is something that can be documented or set by default, that would be great. Otherwise feel free to close this issue.
(I would also appreciate advice on why the app is not displaying in the WebView...)

I ran into the same problem.

Environment
› OS: macOS Ventura 13.0.1 (Intel Core i7, x86_64)
› Node.js: v14.16.0
› npm: 8.19.3
› pnpm: Not installed!
› yarn: Not installed!
› rustup: 1.25.1
› rustc: 1.64.0
› cargo: 1.64.0

Logs when built in the normal way
$ npx tauri android dev
✔ What external IP should we use for your development server? · <IP_ADDRESS>
     Running BeforeDevCommand (`npm run dev`)

><EMAIL_ADDRESS>dev /Users/user/tauri-mobile-sample
> next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
event - compiled client and server successfully in 409 ms (165 modules)
        Info detected host target triple "x86_64-apple-darwin"
INFO    | Android emulator version <IP_ADDRESS> (build_id 8420304) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO    | configAndStartRenderer: setting vsync to 60 hz
WARNING | cannot add library /Users/user/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libvulkan.dylib: failed
INFO    | Sending adb public key [xxxxx]
INFO    | added library /Users/user/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib
INFO    | Rootcanal has  been activated.
INFO    | Started GRPC server at <IP_ADDRESS>:8554, security: Local
INFO    | Advertising in: /Users/suser/Library/Caches/TemporaryItems/avd/running/pid_38446.ini

In my environment, I was able to display the WebView of the application executed in the emulator by following the steps below.
$ npm run tauri android build
$ npm run tauri android dev -- --open

However, I don't think the above is a legitimate method.
To me it looks like for some reason the tauri code is not building correctly.

You can check for console errors opening chrome://inspect in your desktop to open the inspector. That will help us see why the webview is blank.

@arcanistzed Could you tell me what I can do to change the "Active Build Variant" to x86_64? 🙏

@arcanistzed Could you tell me what I can do to change the "Active Build Variant" to x86_64? 🙏

I changed it in Android Studio. Once you open the app as a project, there's a button on the bottom left that says Build Variants. If you open that panel and click on where it shows arm64 or whatever your current variant is, then you can change it which will automatically rebuild your project.

It seems like the issue is that the correct URL is not being set in src-tauri/gen/android/app/app/src/main/java/booking/app/MainActivity.kt

I did reproduce this once when I changed my package name to app in Cargo.toml, then I opened Android Studio and it disappeared. Do you have more information @arcanistzed ?

I have the same issue running apps using vite from from fedora. After launching the emulator, the app does not start. In the console, there is no indication that it is even trying to start the dev server or compile rust.
INFO    | Started GRPC server at <IP_ADDRESS>:8554, security: Local, auth: none
INFO    | Advertising in: /run/user/1000/avd/running/pid_86858.ini
INFO    | Setting display: 0 configuration to: 1080x1920, dpi: 420x420
INFO    | Boot completed in 15435 ms
INFO    | Increasing screen off timeout, logcat buffer size to 2M.
INFO    | Revoking microphone permissions for Google App

Running from android studio, I get the same blank app mentioned above.
Further, when I try to build for android, it compiles, but hangs with "waiting" when gradle should take over.
    Finished release [optimized] target(s) in 9.82s
        Info symlinking lib "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" in jniLibs dir "/home/stuart/motius-projects/discovery/vite-2/src-tauri/gen/android/vite2/app/src/main/jniLibs/x86_64"
        Info "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" requires shared lib "libandroid.so"
        Info "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" requires shared lib "libdl.so"
        Info "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" requires shared lib "liblog.so"
        Info "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" requires shared lib "libm.so"
        Info "/home/stuart/motius-projects/discovery/vite-2/src-tauri/target/x86_64-linux-android/release/libvite2.so" requires shared lib "libc.so"

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 4 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
<-------------> 0% WAITING
> IDLE
> IDLE
> IDLE
> IDLE```

From windows or mac with the same code, I can both build and run the dev server.

From fedora, I can run dev, and build apps using only cargo (e.g. vanilla js or sycamore)

Any update on this thread ? Kinda stuck now

Could you guys try again with latest CLI and see if it is fixed? also checkout https://tauri.app/blog/2023/03/01/create-tauri-app-version-3-released#tauri-20-alpha--mobile-support to bootstrap a project using create-tauri-app


Links generated in rustdoc is broken

In https://opendal.apache.org/docs/rust/opendal/struct.Operator.html, we have

But we expect:

This can't be reproduced locally.

The error message itself is wrong:
warning: unresolved link to `Operator::Operator`
  --> core/src/types/operator/operator.rs:42:66
   |
42 | /// Read [`Operator::concepts`][docs::concepts] for more about [`Operator::Operator`].
   |                                                                  ^^^^^^^^^^^^^^^^^^ the struct `Operator` has no field or associated item named `Operator`
   |
   = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default

warning: unresolved link to `Operator::services`
  --> core/src/types/operator/operator.rs:46:42
   |
46 | /// Read more backend init examples in [`Operator::services`]
   |                                          ^^^^^^^^^^^^^^^^^^ the struct `Operator` has no field or associated item named `services`

Fixed by upgrading rust toolchain.


[构建失败] libtool

This package has no problems in compiling, but will throw two errors when testing.
[39430s] F77 language support.
[39430s]
[39646s] 153: static library                                  FAILED (f77demo.at:305)
[39885s] 154: shared library                                  ok
[40177s] 155: shared and static together                      ok
[40178s]
[40178s] Fortran language support.
[40178s]
[40425s] 156: static library                                  FAILED (fcdemo.at:319)
[40796s] 157: shared library                                  ok
[41119s] 158: shared and static together                      ok
[41119s]

However, there is no such error when compiling locally. Also, I did the test manually and the output is the same as tests/testsuite:
[root@openEuler-RISCV-rare fortran]# autoreconf
[root@openEuler-RISCV-rare fortran]# automake --add-missing
[root@openEuler-RISCV-rare fortran]# ./configure
[root@openEuler-RISCV-rare fortran]# make
[root@openEuler-RISCV-rare fortran]# ls
aclocal.m4      config.in.h~   cprogram    fooc.o    foof3.lo  foo.h       libfoo3.la  libtool-2.4.6   Makefile.in
autom4te.cache  config.log     cprogram.c  foof2.f   foof3.o   fprogram    libfoo.la   libtool.tar.xz  stamp-h1
build-aux       config.status  cprogram.o  foof2.lo  foof.f    fprogram.f  libltdl     m4              tests
config.h        configure      fooc.c      foof2.o   foof.lo   fprogram.o  libmix.la   Makefile
config.in.h     configure.ac   fooc.lo     foof3.f   foof.o    libfoo2.la  libtool     Makefile.am
[root@openEuler-RISCV-rare fortran]# ./fprogram
 Welcome to GNU libtool Fortran demo!
 Real programmers write in FORTRAN.
 fsub called
 fsubf called
 fsub returned, saying that 2 *           2  =           4
 fsub is ok!
 fsub3 called
 fsub3 returned, saying that 4 *           2  =           8
 fsub3 is ok!

Full OBS log: https://pastebin.aosc.io/paste/sFIQ52f9Ea2u1NoudScOAg/raw
Repo: https://gitee.com/misaka00251/libtool/tree/0a8f69087c8f2780942c863df67477348a9735e9/

/usr/bin/ld: ./.libs/libmix.a(foof.o): relocation R_RISCV_HI20 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: ./.libs/libmix.a(foof2.o): relocation R_RISCV_HI20 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: unresolvable R_RISCV_CALL relocation against symbol `_gfortran_st_write@@GFORTRAN_8'
/usr/bin/ld: unresolvable R_RISCV_CALL relocation against symbol `_gfortran_st_write@@GFORTRAN_8'

Patch is coming, currently testing on local.

https://gitee.com/openeuler-risc-v/libtool/pulls/1


Url of the training material

http://training.galaxyproject.org is redirected to https://galaxyproject.github.io/training-material/
but https://training.galaxyproject.org is redirected to https://galaxyproject.org/.
I think both, http and https should redirect to the same URL.

ping @natefoo

Fixed, thanks for the heads up (and @martenson - galaxyproject/infrastructure-playbook#18)

Thanks Nate!


Add help command

@TobiasLaving Thank you very much for this contribution! Help option was needed! 🙏


New header overflows on some screen sizes

Describe the bug
On some screen sizes the MakeCode Arcade logo overlaps with the triple toggle overlaps with the icons. This screenshot is at 1008px x 827px

(I'm using a Surface Pro so smaller screen and saw this)

Duplicate of https://github.com/microsoft/pxt-arcade/issues/3662


Set access per query

Model.access(:user).find.all
user.lists.access(:dev).all
Use projections for reads, delete attributes for write. attributes should hide, or just in json?

Fixed by using block.


Use some kind of cache for failed memcached nodes

From martin.grotzke on May 10, 2009 01:37:43
For memcached failover we should use some kind of cache (with a short ttl,
~1 sec) to store unavailable memcached nodes. This prevents us from trying
to store sessions in unavailable nodes, or reduces the number of times this
is done.
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=10

From martin.grotzke on May 19, 2009 15:14:51
Won't do this (now), as it would really make the code more complex without a real
advantage (besides optimization).
Status: WontFix
Labels: -Milestone-Release1.0


Upgrade to Babel 6

Babel 6 separated out packages into presets. Stage 0 is now its own preset and we need to pull in es2015 and react presets as well now.

:+1:


Api Demos is crashing

I am using a Micromax Canvas AndroidOne version phone and when i am running this app on my device it is crashing.

try to install the demo android sdk version

upgraded the android version to 6.0 and it is working fine.


It's not possible to remove a deleted package

I use packages 3.1.0 together with gitlab 8.0.2.
After deleting a repository from gitlab, the package is still present inside packages, also if I sync remotes.
There is no delete function inside packages and if I try to deactivate the package I get an error message:
Fatal error: Uncaught exception 'Gitlab\Exception\RuntimeException' with message '404 Project Not Found' in /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/Listener/ErrorListener.php:60 Stack trace: #0 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/HttpClient.php(177): Gitlab\HttpClient\Listener\ErrorListener->postSend(Object(Gitlab\HttpClient\Message\Request), Object(Gitlab\HttpClient\Message\Response)) #1 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/HttpClient.php(109): Gitlab\HttpClient\HttpClient->request('projects/121', Array, 'GET', Array) #2 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/Api/AbstractApi.php(50): Gitlab\HttpClient\HttpClient->get('projects/121', Array, Array) #3 /var/www/ in /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/Listener/ErrorListener.php on line 60

:+1: same problem, we change project namespace in gitlab, i can disable old package without error, but can't get new package. manual removing from db resolve my problem.

This is fixed in 3.2.0


Cannot open nightly from 2024-10-07 on MacOS Sequoia (15)

Describe the bug
I just downloaded the latest nightly, and MacOS refuses to open it:

This may be related to my recent upgrade to MacOS Sequoia, but also to https://github.com/camunda/camunda-modeler/pull/4579
I can open v5.28.0 though so it's less likely that this is solely due to MacOS upgrade.
Steps to reproduce

Download nightly from https://downloads.camunda.cloud/release/camunda-modeler/nightly/
Try to open
now this happens

Expected behavior
Nightly opens without problem.
Environment

OS: MacOS 15.0.1
Camunda Modeler Version: nightly
Execution Platform: [e.g. Camunda 7, Camunda 8]
Installed plug-ins: [...]

Additional context
No response

I am moving this to the ready as this may block the next release.

Maybe it's due to missing notarization?

• skipped macOS notarization  reason=notarize options were unable to be generated
https://github.com/camunda/camunda-modeler/actions/runs/11221353989/job/31191526949#step:7:219

I think this goes in line with https://github.com/camunda/camunda-modeler/issues/4578.

Nightly works again.

I think it was a temporary problem with Mac.


Fails to read schema from GML layer with CompoundCurve geometry

Fiona can read curved geometries, and give a linear approximations, just fine, from what i can read from #617.
But, when I (or Geopandas) try to read the schema from a layer with "CompoundCurve" geometries, Fiona fails with "fiona.errors.UnsupportedGeometryTypeError: 9". If all the geometries are converted to a linestring, the schema should probably reflect that.
filpath = "/vsizip//vsicurl/https://nedlasting.geonorge.no/geonorge/Basisdata/Kommuner2022/GML/Basisdata_0000_Norge_3035_Kommuner2022_GML.zip"
with fiona.open(filpath , driver="GML", layer="Fylkesgrense") as src:
    print(src.schema["geometry"])

Traceback (most recent call last):
  File ".\Lib\site-packages\IPython\core\interactiveshell.py", line 3526, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-21-4a8d005e6542>", line 3, in <module>
    print(src.schema["geometry"])
          ^^^^^^^^^^
  File ".\Lib\site-packages\fiona\collection.py", line 416, in meta
    "schema": self.schema,
              ^^^^^^^^^^^
  File ".\Lib\site-packages\fiona\collection.py", line 293, in schema
    self._schema = self.session.get_schema()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "fiona\ogrext.pyx", line 828, in fiona.ogrext.Session.get_schema
  File "fiona\_geometry.pyx", line 60, in fiona._geometry.normalize_geometry_type_code
fiona.errors.UnsupportedGeometryTypeError: 9

Fiona and GDAL version and provenance
fiona 1.9.4.post1 installed with poetry
gdal 3.6.4

@Bjoern-Rapp thanks for the report! We're testing curves, but not very rigorously https://github.com/Toblerity/Fiona/blob/maint-1.9/tests/test_curve_geometries.py#L12. I assume the CSV case is slipping by where GML does not.

@Bjoern-Rapp the fix is released in 1.9.6 today.


why enforce lowercase?

https://github.com/broadinstitute/Tangram/blob/3c87a25d49ad50b7f85ba68c67d31b46e38c3847/tangram/mapping_utils.py#L40-L41
think it'd be useful if this operation is optional.

Hi @giovp ,
Thanks for your suggestion! The initial purpose of these two lines of commands are to get rid of the inconsistent capitalization of gene name. You are right, it is not always needed and thus it is better to make it optional.
I have just updated Tangram function pp_adatas with an additional parameter gene_to_lowercase. The default value is set as True. If not needed, people can alway set it as False to prevent conversion of the genes names to lower cases. One additional line of instructions is added before the pp_adatas function in tutorial.

thank you!

Hi,
It looks like this enforcing lower case was not only in pp_adatas, but also in tg.project_genes. After running it my sc_adata genes become all lower case. Can you please also provide an option to disable it there?
Thanks a lot!

Indeed! that's really problematic and give rise to all sorts of issues, am reopening this cause the issue is not resolved


Typo/Grammar fix

Quick grammar fix from it's to its

@mindlessroman : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks. Merging in the repo is paused; this PR is in the queue to merge when merging resumes. Thanks.

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @ThomasWeiss, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Failed to upgrade cStor SPC from 2.1.0 to 2.8.0

Description
I just performed an upgrade from OpenEBS 2.1.0 to 2.8.0. It mostly went by without a hiccup, but eventually, upgrading the SPC failed with the following error:
I0515 11:03:27.061638       1 cstor_spc.go:100] Started upgrading storagePoolClaim{cstor-disk-pool} from 2.1.0 to 2.8.0
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1c8 pc=0xd5acf8]

goroutine 1 [running]:
github.com/openebs/maya/pkg/upgrade/upgrader.updateUpgradeDetailedStatus(0x0, 0x1034d43, 0xb, 0xc02008885a866fd4, 0x80525c3d0, 0x1ced5c0, 0xc02008885a866fd4, 0x80525c3d0, 0x1ced5c0, 0x1031c95, ...)
	/go/src/github.com/openebs/maya/pkg/upgrade/upgrader/helper.go:213 +0x1d8
github.com/openebs/maya/pkg/upgrade/upgrader.spcUpgrade(0x7fcd357068, 0xf, 0x4000046032, 0x7, 0x1cedaa0, 0x40004cf180, 0x0)
	/go/src/github.com/openebs/maya/pkg/upgrade/upgrader/spc_upgrade.go:76 +0x24c
github.com/openebs/maya/pkg/upgrade/upgrader.Exec(0x7fcd35702c, 0x5, 0x7fcd35703f, 0x5, 0x103a10f, 0x10, 0x7fcd357068, 0xf, 0x4000046032, 0x7, ...)
	/go/src/github.com/openebs/maya/pkg/upgrade/upgrader/exec.go:115 +0x868
github.com/openebs/maya/cmd/upgrade/executor.(*UpgradeOptions).RunCStorSPCUpgrade(0x1cdb3c0, 0x4000455900, 0x10e0420, 0x0)
	/go/src/github.com/openebs/maya/cmd/upgrade/executor/cstor_spc.go:107 +0x204
github.com/openebs/maya/cmd/upgrade/executor.singleCStorSPCUpgrade(0x4000455900)
	/go/src/github.com/openebs/maya/cmd/upgrade/executor/cstor_spc.go:78 +0xd8
github.com/openebs/maya/cmd/upgrade/executor.bulkCStorSPCUpgrade(0x4000455900, 0x400047b5e0, 0x1, 0x5)
	/go/src/github.com/openebs/maya/cmd/upgrade/executor/cstor_spc.go:84 +0x88
github.com/openebs/maya/cmd/upgrade/executor.NewUpgradeCStorSPCJob.func1(0x4000455900, 0x400047b5e0, 0x1, 0x5)
	/go/src/github.com/openebs/maya/cmd/upgrade/executor/cstor_spc.go:62 +0xe0
github.com/spf13/cobra.(*Command).execute(0x4000455900, 0x400047b590, 0x5, 0x5, 0x4000455900, 0x400047b590)
	/go/src/github.com/openebs/maya/vendor/github.com/spf13/cobra/command.go:830 +0x1c4
github.com/spf13/cobra.(*Command).ExecuteC(0x4000455400, 0x0, 0x400005c768, 0x43754)
	/go/src/github.com/openebs/maya/vendor/github.com/spf13/cobra/command.go:914 +0x22c
github.com/spf13/cobra.(*Command).Execute(...)
	/go/src/github.com/openebs/maya/vendor/github.com/spf13/cobra/command.go:864
main.main()
	/go/src/github.com/openebs/maya/cmd/upgrade/main.go:29 +0x44

I have only a single spc in the cluster called cstor-disk-pool, this is its YAML:
apiVersion: openebs.io/v1alpha1
kind: StoragePoolClaim
metadata:
  annotations:
    cas.openebs.io/config: |
      - name: PoolResourceRequests
        value: |-
            memory: 200Mi
            ephemeral-storage: "100Mi"
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"openebs.io/v1alpha1","kind":"StoragePoolClaim","metadata":{"annotations":{"cas.openebs.io/config":"- name: PoolResourceRequests\n  value: |-\n      memory: 200Mi\n      ephemeral-storage: \"100Mi\"\n"},"name":"cstor-disk-pool"},"spec":{"blockDevices":{"blockDeviceList":["blockdevice-e728c07ebb509b1ab5881e975f8189a2","blockdevice-1e6340d5fd05cb2cd1b3e725efbbc5be","blockdevice-dc383288a2a1a4816b4dac791d01e768"]},"name":"cstor-disk-pool","poolSpec":{"poolType":"striped"},"type":"disk"}}
    openebs.io/spc-lease: '{"holder":"","leaderTransition":6}'
  creationTimestamp: "2020-04-25T15:20:28Z"
  finalizers:
  - storagepoolclaim.openebs.io/finalizer
  generation: 19
  name: cstor-disk-pool
  resourceVersion: "99949818"
  selfLink: /apis/openebs.io/v1alpha1/storagepoolclaims/cstor-disk-pool
  uid: 659026c6-2aa0-4c96-be90-bc115680bf4e
spec:
  blockDevices:
    blockDeviceList:
    - blockdevice-3ce583a5ae11343272b9ae2a044798a0
    - blockdevice-5d9e02b3865c779a7d56804454126406
    - blockdevice-b86b3018f7ae807a1d336665f0af2685
  maxPools: null
  minPools: 0
  name: cstor-disk-pool
  poolSpec:
    cacheFile: ""
    overProvisioning: false
    poolType: striped
    roThresholdLimit: 0
    thickProvisioning: false
  type: disk
status:
  phase: Online
versionDetails:
  autoUpgrade: false
  desired: 2.1.0
  status:
    current: 2.1.0
    dependentsUpgraded: true
    lastUpdateTime: "2020-10-04T12:08:03Z"
    state: Reconciled

At this point;

all control plane Pods were running 2.8.0
2 out of 3 cStor disk pool pods were running and one was still ContainerCreating (all 2.8.0)
all PVC targets were still running 2.1.0
all volumes were healthy, except one: 1/3 Rebuilding, 1/3 Degraded, 1/3 showed as Healthy but the cStor disk pool behind it was still ContainerCreating

Your Environment

kubectl get nodes: 3 Raspberry Pi arm64 nodes
OS (from /etc/os-release): k3os
Kernel (from uname -a): Linux kristel 4.19.75-v8+ #1270 SMP PREEMPT Tue Sep 24 18:59:17 BST 2019 aarch64 GNU/Linux

Apparently, panic is occurring on this line:
https://github.com/openebs/maya/blob/v2.8.0/pkg/upgrade/upgrader/helper.go#L213
If I look at the parameters correctly, first parameter uTask is 0x0 causing null ptr dereference.
Value is coming from here: https://github.com/openebs/maya/blob/v2.8.0/pkg/upgrade/upgrader/spc_upgrade.go#L68-L76

An easy way to fix this would be to delete all the utasks in openebs namespace. The job will create a new one when it is launched again. The log was disabled as this is an experimental way of upgrading all the components automatically and provide status via external controllers which we are working on.

Gotcha! The upgrade tasks did not contain an entry for this upgrade yet. However, I restarted the job after the last cStor disk pool was fully Running (no longer ContainerCreating) and now the log says:
I0515 12:13:47.786292       1 cstor_spc.go:100] Started upgrading storagePoolClaim{cstor-disk-pool} from 2.1.0 to 2.8.0
I0515 12:13:48.306299       1 csp_upgrade.go:193] csp deployment cstor-disk-pool-7it6 already in 2.8.0 version
I0515 12:13:48.307009       1 csp_upgrade.go:155] csp cstor-disk-pool-7it6 already in 2.8.0 version
I0515 12:13:48.324890       1 csp_upgrade.go:380] Upgrade Successful for csp cstor-disk-pool-7it6
I0515 12:13:49.721927       1 csp_upgrade.go:193] csp deployment cstor-disk-pool-una0 already in 2.8.0 version
I0515 12:13:49.722012       1 csp_upgrade.go:155] csp cstor-disk-pool-una0 already in 2.8.0 version
I0515 12:13:49.923693       1 csp_upgrade.go:380] Upgrade Successful for csp cstor-disk-pool-una0
I0515 12:13:51.723206       1 csp_upgrade.go:193] csp deployment cstor-disk-pool-eiq0 already in 2.8.0 version
I0515 12:13:51.750217       1 csp_upgrade.go:153] patched csp cstor-disk-pool-eiq0
I0515 12:13:51.750336       1 csp_upgrade.go:277] Verifying the reconciliation of version for cstor-disk-pool-eiq0 { phase:Healthy }
I0515 12:14:01.765769       1 csp_upgrade.go:277] Verifying the reconciliation of version for cstor-disk-pool-eiq0 { phase:Healthy }
I0515 12:14:11.800886       1 csp_upgrade.go:380] Upgrade Successful for csp cstor-disk-pool-eiq0
I0515 12:14:11.890884       1 spc_upgrade.go:148] Verifying the reconciliation of version for cstor-disk-pool
I0515 12:14:21.909991       1 spc_upgrade.go:102] Upgrade Successful for spc cstor-disk-pool
I0515 12:14:21.910088       1 cstor_spc.go:120] Successfully upgraded storagePoolClaim{cstor-disk-pool} from 2.1.0 to 2.8.0

I think the error occurred because cstor-disk-pool-eiq0 took too long to start again. Remember that this is running on a couple of Raspberry Pi 4's, so pulling the three large cstor-disk-pool images and starting the container can take ~30 minutes.

Nice the job is meant to correct itself on restarts. Still the nil pointer errors should not happen. I will try to reproduce and handle those in the code.

Nice the job is meant to correct itself on restarts. Still the nil pointer errors should not happen. I will try to reproduce and handle those in the code.

It did, but it failed four times in pretty rapid succession so the Job had given up before the cStor pool was fully healthy again.

Interestingly, even now the upgradetasks in the cluster don't contain any information on the 2.8.0 upgrade. Is that what you meant with the log being disabled?

Can you paste the -oyaml of any one of the CR


Colon in input box becomes black if written after \u07EE

A strange issue for sure, but if you write "\u07EE :", the colon becomes black (doesn't matter if you put space in between). For copy:
߮ :

This seems to be the case for other "special" characters aswell, like ; - + # ~ $ etc. Also numbers.
Letters seem to be fine.
Additionally I need to press backspace twice to delete the character.

cannot replicate anymore in nightly
@pajlada close?

Does this still happen? I tried it but I can see the : maybe it had to do with an old qt version or something

yeah seems to be solved somehow

@TETYYS close please


Add install-create event handlers

Brings the logic for creating slack messages and OSTicket tickets, which was contained in a separate service, into the meshdb monolith
Also fix an issue with admin UI redirects
Fixes #532

Todo:

[ ] Add env variables to IAC
[ ] Tests?

Moved redirect fix to a standalone PR: #637


File not found error when Adding template to "_cts/{Content Type Name}" folder

When trying to use this code and uploading template to "_cts/{Content Type Name}" folder, following lines gives error "File not Found"
Microsoft.SharePoint.Client.File uploadedFile = ctFolder.Files.Add(newFile);
cc.Load(uploadedFile);
cc.ExecuteQuery();

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

ID: d7ed07d3-4bc0-71c4-d8d2-2edd8ba95927
Version Independent ID: 8bd4af28-95b7-3823-6b89-53ede1610085
Content: Create SharePoint content types by using CSOM
Content Source: docs/solution-guidance/create-sharepoint-content-types-by-using-csom.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Could you please check if this file exists?

Could you please check if this file exists?

The file is actually created but still it gives file not found error

My apologies, I mean that, we should check that is the newFile is exists in the code: Microsoft.SharePoint.Client.File uploadedFile = ctFolder.Files.Add(newFile);

But how can a File pre-exist if it has never been created before?
The file is being associated with the content type at the time of creation of Content Type.
I did not get your point of checking if the file exists. Can you please elaborate on this?

I have used the following code, and it works
Web web = context.Site.RootWeb;                 CreateContentTypeIfDoesNotExist(context, web);                 ContentType ct = web.ContentTypes.GetById("0x0101009189AB5D3D2647B580F011DA2F356FB2");                     // create by reference                                         context.Load(ct);                     context.ExecuteQuery();                   string ctFolderServerRelativeURL = "_cts/" + ct.Name;                 Folder ctFolder = web.GetFolderByServerRelativeUrl(ctFolderServerRelativeURL);                 context.Load(ctFolder);                 context.ExecuteQuery();                 string path = @"D:\TestDocs\test1.docx";                 string fileName = System.IO.Path.GetFileName(path);                 byte[] filecontent = System.IO.File.ReadAllBytes(path);                 using (System.IO.FileStream fs = new System.IO.FileStream(path, System.IO.FileMode.Open))                 {                     FileCreationInformation newFile = new FileCreationInformation();                     newFile.Content = filecontent;                     newFile.Url = ctFolderServerRelativeURL + "/" + fileName;                     Microsoft.SharePoint.Client.File uploadedFile = ctFolder.Files.Add(newFile);                     context.Load(uploadedFile);                     context.ExecuteQuery();                         //Microsoft.SharePoint.Client.File.SaveBinaryDirect(clientContext, ctFolderServerRelativeURL + "/" + fileName, fs, true);                     context.Load(ct);                     context.ExecuteQuery();                     ct.DocumentTemplate = fileName;                     ct.Update(false);                     context.Load(ct);                     context.ExecuteQuery();                     Console.WriteLine("Content type updates");                 }
Could you please provide some code for this?