chore: update to golangci-lint 1.50.1

Update to the latest release of golangci-lint: https://github.com/golangci/golangci-lint/releases while I try debugging an issue with golangci-lint failures on a different PR

This wasn't the root cause of the issue but I don't see a downside to upgrading.


Update ch-goals.md

edit for style/idiom, add mention of Raspberry Pi.

Just like the previous pull requests, read each change and approve of everything, so I'm merging it now.


An error occurred after downloading game covers and backgrounds

after successfully downloading game covers and background covers an error has occurred as follows in a text that prevents me booting retro flow launcher
here's the error text :
Ux0:/data/retroflow/titles/fba_2012.lua:2 "j" expected near discor 94
press x to restart
press o to enable/disable ftp

One of the fba games is causing the error, if you can send me the fba lua file I can take a look in a few days.
Or if you open the lua file you may be able to find the problem game by searching for the discor text in the error code.
Delete that game from the fba rom directory, also delete the fba lua file and the app should work again.

thank you very much for your reply. i tried it on another vita and now it gives me another error says
cannot open ux0:/app/retroflow/script.lua: not owner

Reinstall the vpk file, it sounds like you may have deleted something else by accident.

Hi @Husky363
I think I found the problem related to the FBA issue.
Please delete these folders:
ux0:/data/RetroFlow/CACHE
ux0:/data/RetroFlow/DATABASES
ux0:/data/RetroFlow/TITLES
Then install the vpk from the nightly build: https://github.com/jimbob4000/RetroFlow-Launcher/releases/tag/Nightly
Thanks


Show/Hide subprocess output depending on the log level

Feature request

Current Behavior

The subprocess outputs are being displayed no matter what.
Expected Behavior

The subprocess outputs should be displayed only based on the log level.
Possible Solution

One way to do it, would be to only show the outputs if the log level is set to DEBUG or above. For lower levels stdout and stderr should be redirected to DEVNULL.
import subprocess

subprocess.run(['ls', '-l'], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)

Ideas to explore:

https://docs.python.org/3/library/asyncio-subprocess.html#subprocess-and-threads
https://github.com/Delgan/loguru/issues/584


NodeGroup fails to update when unchanged labels exist

What happened?

I updated the desiredSize/minSize scalingConfig properties in a NodeGroup but the operation failed with the error message

cannot update EKS node group configuration: InvalidParameterException: Both or either addOrUpdateLabels or removeLabels must not be empty

My NodeGroup has the following config
apiVersion: eks.aws.crossplane.io/v1alpha1
kind: NodeGroup
metadata:
  name: g4dn-xlarge
spec:
  forProvider:
    region: us-west-2
    amiType: AL2_x86_64_GPU
    instanceTypes:
      - g4dn.xlarge
    clusterNameRef:
      name: cluster
    diskSize: 256
    subnetRefs:
      - name: vpc-subnet-1
      - name: vpc-subnet-2
      - name: vpc-subnet-3
    nodeRoleRef:
      name: node-role
    labels:
      gpu: nvidia
      accelerator: nvidia-t4
    scalingConfig:
      desiredSize: 2
      maxSize: 3
      minSize: 2

As a workaround, if I add a new label as part of the update - i.e. zzzworkaround: "3" then the operation completes as expected without error.
My guess is the bug is related to this line https://github.com/crossplane/provider-aws/blob/82e7f3f02baf949e2217ef76045786ad8b0700ce/pkg/clients/eks/nodegroup.go#L99. If both addOrModify and remove are empty then the line should likely be skipped.
If it does end up being the above I'm more than happy to help fix.  Just wanted to open the issue first.
How can we reproduce it?

Create a NodeGroup with labels. Then update the NodeGroup's scalingConfig.
What environment did it happen in?
Crossplane version:  v1.5
Provider-aws: v0.21.0
Kubernetes: 1.21

I'm seeing this too 😢 cannot make any changes to my managed nodegroup without having a label added or removed
Crossplane version: v1.5.1
Provider-aws: v0.22.0
I think you're correct @kurtb , the logic should check whether addOrModify or remove are empty lists before doing UpdateLabelsPayload client call. Something  like this maybe 🤔 ?
if len(addOrModify) > 0 || len(remove) > 0 {
		u.Labels = &ekstypes.UpdateLabelsPayload{
			AddOrUpdateLabels: addOrModify,
			RemoveLabels:      remove,
		}
}


update link to entry point.sh

historical branch is missing

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

@singhAvneet please bump the chart version and sign the DCO, thanks!

@singhAvneet ping


Need Info on Inter container access where one container listens on a local port

I have a use case where i create two containers - one for the build environment using a docker file and other for oracle database using an image. Build container is dependent on database container.
Database has to be accessible from localhost:1521 so i have provided ports as local: 1521 and container: 1521. My Java application build happens in Build container which has tests to be verified against the database. How do i create the inter container communication ?

Hi @asharma8438, thanks for the question! You can access other running containers by their name - so if your database container is called my_database_container, your Java application can access it at my_database_container:1521.

Thanks for your response Charles. Is there a way to access the database at localhost:1521 from the batect container?

There's no built-in way to do that, no. Are you not able to use my_database_container:1521?

I have my application configuration files and other code files which refer
to the database at localhost:1521.
Can do with the database hostname but wanted to check if it was possible to
avoid the change in hostname.
Regards
Ashish Sharma
On Fri, 2 Aug 2019 at 5:06 pm, Charles Korn<EMAIL_ADDRESS>wrote:

There's no built-in way to do that, no. Are you not able to use
my_database_container:1521?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/charleskorn/batect/issues/154?email_source=notifications&email_token=AJM23NYJK3X34YBJTUIJ54DQCPMGTA5CNFSM4IIPRHRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3M27YA#issuecomment-517582816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJM23N4QZJZDRDM7GTGYQPTQCPMGTANCNFSM4IIPRHRA
.

--
Regards
Ashish Sharma

No worries. Are you ok for me to close this issue? Feel free to open another one if you have any further questions.

Sure thank you.
On Fri, 2 Aug 2019 at 5:44 pm, Charles Korn<EMAIL_ADDRESS>wrote:

No worries. Are you ok for me to close this issue? Feel free to open
another one if you have any further questions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/charleskorn/batect/issues/154?email_source=notifications&email_token=AJM23N73ESPQCMTO2SHMYGTQCPQUVA5CNFSM4IIPRHRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3M6A6Y#issuecomment-517595259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJM23N4DDWRJE3UMRKLNJXTQCPQUVANCNFSM4IIPRHRA
.

--
Regards
Ashish Sharma


clean-checks-list - Untruncate check descriptions

Closes #6945
Also: vertically align app/gh icon

Test URLs
https://github.com/refined-github/sandbox/pull/12
Screenshot
before

after

Thanks @Katsute !


[5.0] Add Database's Columns Into Models

Hi everyone,
I saw a lot of package using these information. Putting them on the core allows to cache them between  packages.
Instead of having a lot of query for the same think we will just have one.
cc @phurni

@taylorotwell Have you another way to handle that?
Because I really think that should be on the core of Laravel.

Seriously, why do you don't want this functionality on the core of Laravel?
Is there any workaround?

Is there any workaround?

Just drop this in with a trait if you want it.

@GrahamCampbell Yes, but its what I said. If every developer create a Trait to do that, we will have one query for every package who use this functionality instead of just one.


Enable access to group name

Adds two functions tls1_group_id2name which returns the tlsname for a given group_id and SSL_get0_group_name which surfaces that name to the "user"
This is a follow up to my previously rejected PR #20318 and the resulting discussion. It is related to #20594 but I am unsure if it addresses that issue at its core.
Since I am new to this project I would appreciate direction on if I went about surfacing the tlsname the correct way here, how I should document this new functionality, and how/where to test it.
I am aware I will need to submit a ICLA and a CCLA (If IBM hasn't submitted one already) before this can be merged.
Checklist

[x] documentation is added or updated
[x] tests are added or updated

A few updates:

I've address the style issues after reviewing https://www.openssl.org/policies/technical/coding-style.html
I've added a doc file based on reading doc files for similar surrounding functions.
I will submit my ICLA on Friday (I will have access to a printer/scanner Thursday night)
I've confirmed that IBM has previously submitted a CCLA
I am in the process of figuring out where/how to test this. I will be adding/updating a test in test/sslapitest.c

I've added some test updates, but am not confident I added enough. Feedback on my tests would be appreciated.
Also as an FYI, I emailed in my ICLA today.

CI failures are relevant

I believe I've addressed the CI failures, there was one windows build failure I was not sure about though.
If you could re-trigger the CI for me (since I'm not whitelisted)

Please rebase the PR against fresh master branch and drop the merge commit. Merge commits are not allowed.

Please rebase the PR against fresh master branch and drop the merge commit. Merge commits are not allowed.

Since most of my commits were just wip something I decided to just patch the diff and force push it.
Everything should be fine now, though I'm unsure why my CCLA situation is still unresolved (my ICLA was accepted over a week ago).

Closed and reopened to grab my CLA

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

@hlandau @paulidale please reconfirm

FYI I saw a merge conflict message so I rebased on latest master and force pushed it

'''
SSL_get_curve_name                      ?	3_2_0	EXIST::FUNCTION:
'''
should be removed from util/libssl.num

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Needs the fix up before merge.  Approved anew once that's done.

just pushed the requested fix

This pull request is ready to merge

Squashed commits and merged to master branch. Thank you for your contribution.

Follow up Question:
Is there any way to know when this will be part of a release? From my research it would assume it needs to wait for 3.2, which doesn't seem to have an estimate yet afaik.
I'm working on some upstream usage of the new function and would prefer to have a timeline

No release date for 3.2 has been set at this stage.
I'd expect late this year, but not promises.


Allow parsing of "german" doubles

Dart doubles use a dot . as decimal separator. But both , and . are generally accepted as decimal separators for international use.
This PR allows parsing of more double formats:
12345.12
12 345,12
12.345,12
12,345.00

// all map now to double 12345.12

This is a breaking change - not API-wise but behavior-wise - I really like to land.


Gift Entry: Reduce Initial Load Time

This set of changes aims to reduce the initial load time of the Gift Entry tab by:

Deferring retrieval of field and object mappings until the template builder is initialized (reducing the amount of resources loaded from the server when a User lands on the main Gift Entry tab), and
Changing the mechanism for determining the current namespace.  Previously the app was using BDI_ManageAdvancedMappingCtrl.getNamespaceWrapper which took a lot of server time instantiating the BDI_ManageAdvancedMappingCtrl class.  The changed components now infer the namespace by inspecting an object or field reference instead of going to Apex (reducing the overall amount of server time used on initial load).

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Replaced by: https://github.com/SalesforceFoundation/NPSP/pull/5472


Cannot set cargoExtraArgs in craneLib.cargoNextest

https://github.com/ipetkov/crane/blob/529c1a0b1f29f0d78fa3086b8f6a134c71ef3aaf/lib/cargoNextest.nix#L46-L51
$ cargo nextest run -h
--
Build and run tests

Usage: cargo nextest run [OPTIONS] [FILTERS]... [-- <FILTERS_AND_ARGS>...]
[...]

As stated in the documentation of the cargo-nextest crate, any extra argument/option is to be set behind $ cargo nextest run. The nextest call appears to take mostly the same arguments as cargo does, which is why I got away with placing my cargo extra arguments (--feature <xyz>) in cargoNextestExtraArgs without any issue.
If any cargoExtraArgs (or llvm-cov) is placed between $ cargo <here> nextest run it results in an invalid command structure. I figure both can be removed from craneLib.cargoNextest and the corresponding documentation without losing functionality.
I'll gladly do the work if I haven't missed something.

Hi @skarmux thanks for the report!
I think I had missed that part of the documentation when writing the original integration (I suppose I mistakenly assumed just because cargo supports options like cargo <here> build <etc>, then nextest would do...), so if that's the right way to make things work I'd definitely be happy to review a PR to get it fixed!

Okay, this will be my first ever PR. It's assigned to this issue. I've ran nix flake check and everything went through. Also used the forked in my personal project as input and the barebones craneLib.cargoNextest check passed there as well.


podman compose up:  psycopg2.OperationalError: connection to server at "<IP_ADDRESS>", port 5432 failed: Connection refused

I am testing podman compose up and ran into below.
I believe this is an intermittent issue and will not be easily reproduced, I don't yet know the root cause.
kai_1               | psycopg2.OperationalError: connection to server at "<IP_ADDRESS>", port 5432 failed: Connection refused
kai_1               | 	Is the server running on that host and accepting TCP/IP connections?

I am guessing this may be from something not cleaning up.
I have been running between podman compose up and make run-postgres &  make run-server
Been going back and forth between those modes testing workflows
Now I'm seeing an error of the podman compose flow saying it can't connect to the DB.
Filing this issue as I've spoken to a few other folks who have also hit this issue intermittently, this is first time I've seen it with podman compose up
The entire console output from $ TAG="local" podman compose up  is below
https://gist.github.com/jwmatthews/d48abfccc368304c5a2fe088c4a0e12a
$ TAG="local" podman compose up
>>>> Executing external compose provider "/usr/local/bin/docker-compose". Please see podman-compose(1) for how to disable this message. <<<<

Creating network "kai_default" with the default driver
Creating volume "kai_kai_db_data" with default driver
Creating kai_kai_db_1 ... done
Creating kai_kai_1    ... done
Attaching to kai_kai_db_1, kai_kai_1
kai_1               | Waiting until postgres is ready
kai_db_1            | Warning: Can't detect cpuset size from cgroups, will use nproc
kai_db_1            | The files belonging to this database system will be owned by user "postgres".
kai_db_1            | This user must also own the server process.
kai_db_1            |
kai_db_1            | The database cluster will be initialized with locale "en_US.utf8".
kai_db_1            | The default database encoding has accordingly been set to "UTF8".
kai_db_1            | The default text search configuration will be set to "english".
kai_db_1            |
kai_db_1            | Data page checksums are disabled.
kai_db_1            |
kai_db_1            | fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok
kai_db_1            | creating subdirectories ... ok
kai_db_1            | selecting dynamic shared memory implementation ... posix
kai_db_1            | selecting default max_connections ... 100
kai_db_1            | selecting default shared_buffers ... 128MB
kai_db_1            | selecting default time zone ... Etc/UTC
kai_db_1            | creating configuration files ... ok
kai_db_1            | running bootstrap script ... ok
kai_db_1            | performing post-bootstrap initialization ... ok
kai_db_1            | syncing data to disk ... ok
kai_db_1            |
kai_db_1            |
kai_db_1            | Success. You can now start the database server using:
kai_db_1            |
kai_db_1            |     pg_ctl -D /var/lib/pgsql/data/userdata -l logfile start
kai_db_1            |
kai_db_1            | initdb: warning: enabling "trust" authentication for local connections
kai_db_1            | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
kai_db_1            | waiting for server to start....2024-09-27 12:59:21.822 UTC [35] LOG:  redirecting log output to logging collector process
kai_db_1            | 2024-09-27 12:59:21.822 UTC [35] HINT:  Future log output will appear in directory "log".
kai_db_1            |  done
kai_db_1            | server started
kai_db_1            | /var/run/postgresql:5432 - accepting connections
kai_db_1            | => sourcing /usr/share/container-scripts/postgresql/start/set_passwords.sh ...
kai_db_1            | ALTER ROLE
kai_db_1            | waiting for server to shut down.... done
kai_db_1            | server stopped
kai_db_1            | Starting server...
kai_db_1            | 2024-09-27 12:59:22.171 UTC [1] LOG:  redirecting log output to logging collector process
kai_db_1            | 2024-09-27 12:59:22.171 UTC [1] HINT:  Future log output will appear in directory "log".
kai_1               |
kai_1               | Postgres is ready
kai_1               | ################################################
kai_1               | load-data has never been run.                  #
kai_1               | Please wait, this will take a few minutes.     #
kai_1               | ################################################
kai_1               | Using custom config file
kai_1               | Console logging for 'kai' is set to level 'INFO'
kai_1               | File logging for 'kai' is set to level 'DEBUG' writing to file: '/kai/logs/kai_psql.log'
kai_1               | config: log_level='info' file_log_level='debug' log_dir='$pwd/logs' demo_mode=False trace_enabled=True gunicorn_workers=8 gunicorn_timeout=3600 gunicorn_bind='<IP_ADDRESS>:8080' incident_store=KaiConfigIncidentStore(solution_detectors=<SolutionDetectorKind.NAIVE: 'naive'>, solution_producers=<SolutionProducerKind.TEXT_ONLY: 'text_only'>, args=KaiConfigIncidentStorePostgreSQLArgs(provider=<KaiConfigIncidentStoreProvider.POSTGRESQL: 'postgresql'>, host='<IP_ADDRESS>', database='kai', user='kai', password='dog8code', connection_string=None, solution_detection=<SolutionDetectorKind.NAIVE: 'naive'>)) models=KaiConfigModels(provider='ChatOpenAI', args={'model': 'gpt-4o'}, template=None, llama_header=None, llm_retries=5, llm_retry_delay=10.0) solution_consumers=[<SolutionConsumerKind.DIFF_ONLY: 'diff_only'>, <SolutionConsumerKind.LLM_SUMMARY: 'llm_summary'>]
kai_1               | INFO - 2024-09-27 12:59:33,339 - kai.service.kai_application.kai_application - [  kai_application.py:54   -             __init__()] - Tracing enabled.
kai_1               | /kai/kai/service/llm_interfacing/model_provider.py:144: LangChainDeprecationWarning: The class `ChatOpenAI` was deprecated in LangChain 0.0.10 and will be removed in 0.3.0. An updated version of the class exists in the langchain-openai package and should be used instead. To use it run `pip install -U langchain-openai` and import as `from langchain_openai import ChatOpenAI`.
kai_1               |   self.llm: BaseChatModel = model_class(**model_args)
kai_1               | INFO - 2024-09-27 12:59:33,557 - kai.service.kai_application.kai_application - [  kai_application.py:63   -             __init__()] - Selected provider: ChatOpenAI
kai_1               | INFO - 2024-09-27 12:59:33,557 - kai.service.kai_application.kai_application - [  kai_application.py:64   -             __init__()] - Selected model: gpt-4o
kai_1               | Traceback (most recent call last):
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/engine/base.py", line 145, in __init__
kai_1               |     self._dbapi_connection = engine.raw_connection()
kai_1               |                              ^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/engine/base.py", line 3292, in raw_connection
kai_1               |     return self.pool.connect()
kai_1               |            ^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 452, in connect
kai_1               |     return _ConnectionFairy._checkout(self)
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 1269, in _checkout
kai_1               |     fairy = _ConnectionRecord.checkout(pool)
kai_1               |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 716, in checkout
kai_1               |     rec = pool._do_get()
kai_1               |           ^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/impl.py", line 169, in _do_get
kai_1               |     with util.safe_reraise():
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
kai_1               |     raise exc_value.with_traceback(exc_tb)
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/impl.py", line 167, in _do_get
kai_1               |     return self._create_connection()
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
kai_1               |     return _ConnectionRecord(self)
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 678, in __init__
kai_1               |     self.__connect()
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 902, in __connect
kai_1               |     with util.safe_reraise():
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
kai_1               |     raise exc_value.with_traceback(exc_tb)
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/pool/base.py", line 898, in __connect
kai_1               |     self.dbapi_connection = connection = pool._invoke_creator(self)
kai_1               |                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/engine/create.py", line 637, in connect
kai_1               |     return dialect.connect(*cargs, **cparams)
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/sqlalchemy/engine/default.py", line 616, in connect
kai_1               |     return self.loaded_dbapi.connect(*cargs, **cparams)
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               |   File "/opt/app-root/lib64/python3.12/site-packages/psycopg2/__init__.py", line 122, in connect
kai_1               |     conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
kai_1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
kai_1               | psycopg2.OperationalError: connection to server at "<IP_ADDRESS>", port 5432 failed: Connection refused
kai_1               | 	Is the server running on that host and accepting TCP/IP connections?

I've restarted the podman machine VM and still see above.

The issues I saw were related to my config.toml
I ended up having a database configuration which caused the problem.
Issue here:
[incident_store.args]
provider = "postgresql"
host = "<IP_ADDRESS>"

The problem is that when we run via podman compose up, we are expecting that the database hose is kai_db, it is set via below
https://github.com/konveyor/kai/blob/main/compose.yaml#L20
  KAI__INCIDENT_STORE__ARGS__HOST: kai_db
When we do the below in config, it takes precedence, which breaks us.
[incident_store.args]
host = "<IP_ADDRESS>"

What I did was:

cp kai/config.toml build/config.toml
Edited build/config.toml, minimal edits of the model, I left the incident_store config as it is in kai/config.toml

This is what I ran with when I saw the error
$ cat build/config.toml
# Default configuration file for Kai. For a better understanding of the
# configuration options, please refer to `build/example_config.toml`

log_level = "info"
file_log_level = "debug"
log_dir = "$pwd/logs"
demo_mode = false
trace_enabled = true

solution_consumers = ["diff_only", "llm_summary"]

[incident_store]
solution_detectors = "naive"
solution_producers = "text_only"

[incident_store.args]
provider = "postgresql"
host = "<IP_ADDRESS>"
database = "kai"
user = "kai"
password = "dog8code"

[models]
provider = "ChatOpenAI"

[models.args]
model = "gpt-4o"

Then I used the below and it worked:

 $ cat build/config.toml
# Default configuration file for Kai. For a better understanding of the
# configuration options, please refer to `build/example_config.toml`

log_level = "info"
file_log_level = "debug"
log_dir = "$pwd/logs"
demo_mode = false
trace_enabled = true

solution_consumers = ["diff_only", "llm_summary"]

[incident_store]
solution_detectors = "naive"
solution_producers = "text_only"

#[incident_store.args]
#provider = "postgresql"
#host = "<IP_ADDRESS>"
#database = "kai"
#user = "kai"
#password = "dog8code"

[models]
#provider = "ChatIBMGenAI"
provider = "ChatOpenAI"

[models.args]
model = "gpt-4o"

Recap of what I saw:

copy kai/config.toml to build/config.toml

When I did this, I ended up overwriting the database host, I did not realize this

run via podman compose up
the compose.yaml is setting the postgres host as an environment variable

https://github.com/konveyor/kai/blob/main/compose.yaml#L20
We NEED this database host value to be used in Kai

Kai runs and it takes the value from config.toml as precedence and NOT the environment variables
Kai is unable to reach the database as it's trying to reach <IP_ADDRESS>:5432 instead of kai_db:5432


feat: add resolver for dependency resolving

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

re #465

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

76 of 150 (50.67%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 40.855%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/client/resolver.go
74
99
74.75%

pkg/downloader/downloader.go
0
49
0.0%

Totals

Change from base Build<PHONE_NUMBER>3:
0.2%

Covered Lines:
3259

Relevant Lines:
7977

💛  - Coveralls


Re-encode codebase to UTF-8

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the canary branch (left side). Also you should start your branch off our canary.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.

Description
Codebase reencoded to UTF-8. Resources left untouched (because they're expected to be whichever encoding they're set to in the resource file, so they shouldn't be touched), and builds untouched, so it'll just generate UTF-8 strings for output now.
This could be corrected with a build flag if so desired for consistency, but I assume there's no desire to do that here.
💔Thank you!

Manually reviewed and made adjustments for each area of the repo.
Initially manually corrected the ZipArchive stuff (mixed Polish & Korean).
Reviewed N3Base/ - N3GlobalEffectMng.h/.cpp and N3UIList.h needed to be manually corrected
Reviewed game/ -  UICharacterCreate.h & UIRepairTooltipDlg.h neededto be manually corrected
Reviewed server/ - Ebenezer/IOCPort.h, LoginServer/IOCPort.h, and another polish one I missed - LoginServer/CentralDir.cpp
Reviewed tool/  - N3CE/stdafx.h, N3ME/DlgBar.cpp, N3ME/DlgEditWarp.cpp, N3ME/stdafx.h needed to be manually corrected
No other changes. Notably it did re-encode common, but no changes there, so nothing to review.

As a note: oddly the diff page shows a few of the files (e.g. BitmapFile.h, BitmapFile.cpp) as mangled, but they're fine.
You can check the files directly; they're UTF-8 encoded and even show up otherwise correctly on their page (though that's true for CP949 as well).

Hi @twostars, thanks for the PR. I'm commenting to explain why we closed this one and to provide some insights as an appreciation for your time and efforts. I apologize for repeating what was said on Discord, but since you deleted your messages, let me recap:

The PR is incomplete, as not all files were updated to the correct encoding.
Your process is undocumented, making it difficult for me as the maintainer to accept or review such a crucial change. This PR includes 577 changed files with 15,774 additions and 15,768 deletions, which could introduce issues if missed during a manual review. No tools were mentioned for the conversion process, which is important given the inconsistencies among various tools.
You mentioned doing the conversion manually, which is prone to human error. Additionally, you forcefully mass re-encoded all files to a specific encoding and then corrected them manually, which isn't the best approach in my opinion.
There were some incorrect assumptions on your part, insisting on something that isn't necessarily accurate.
Lack of communication: Ideally, we would have discussed this in a GitHub issue before submitting such a large Pull Request. Especially since you were aware from Discord that I was working on it. Your proactive effort is appreciated, but communication is key for team collaboration and could have saved us both time.

Resources left untouched (because they're expected to be whichever encoding they're set to in the resource file, so they shouldn't be touched), and builds untouched, so it'll just generate UTF-8 strings for output now.

This is incorrect. Since Visual Studio 2010, resource files are UTF-16 Little Endian (LE) encoded with Byte Order Mark (BOM). This change was made by Microsoft to allow editors to load multiple Unicode characters from different character sets/code pages/encoding properly. Note that the current resource (*.rc) files in this project were created before 2002. Hence, some are UTF-16 Big Endian (BE) encoded and some are detected as Big5, which in this context is CP950 (Windows 950) Microsoft encoding, an extended version of Big5 encoding with more character sets for backward compatibility. Please refer to Wikipedia before making assumptions: https://en.wikipedia.org/wiki/Code_page_950

Manually reviewed and made adjustments for each area of the repo. Initially manually corrected the ZipArchive stuff (mixed Polish & Korean).
Reviewed N3Base/ - N3GlobalEffectMng.h/.cpp and N3UIList.h needed to be manually corrected Reviewed game/ - UICharacterCreate.h & UIRepairTooltipDlg.h neededto be manually corrected Reviewed server/ - Ebenezer/IOCPort.h, LoginServer/IOCPort.h, and another polish one I missed - LoginServer/CentralDir.cpp Reviewed tool/ - N3CE/stdafx.h, N3ME/DlgBar.cpp, N3ME/DlgEditWarp.cpp, N3ME/stdafx.h needed to be manually corrected
No other changes. Notably it did re-encode common, but no changes there, so nothing to review.

Not sure why you had issues with them. Perhaps it's related to the mass re-encoding approach I mentioned earlier. I only had to correct src\server\LoginServer\ZipArchive.cpp, which contained Polish and Korean characters in the same file. It was as simple as running my script to update encoding, opening a previous version of that file with CP1250 encoding, and manually copying the Polish characters to the re-encoded file.

As a note: oddly the diff page shows a few of the files (e.g. BitmapFile.h, BitmapFile.cpp) as mangled, but they're fine.
You can check the files directly; they're UTF-8 encoded and even show up otherwise correctly on their page (though that's true for CP949 as well).

I didn't encounter this issue in my PR: https://github.com/ko4life-net/ko/pull/241. This could be related to your encoding approach, but it doesn't matter at this point.
Thank you again for your effort and understanding.

"I'm commenting to explain why we closed this one and to provide some insights as an appreciation for your time and efforts."
I closed it. Github even shows you this.

On a side note why are we still depending on mfc/afz Korean res includes if it can be substitutes with winres?

On a side note why are we still depending on mfc/afx Korean res includes if it can be substituted with winres?

Isn't winres for .NET applications? I didn't know they could be substituted with rc files and would be curious to see a proof of concept with one of the tools in the project if you know how.

On a side note why are we still depending on mfc/afx Korean res includes if it can be substituted with winres?

You should make this a separate issue.

I had set it up once long time ago because the vs didn't support mfc or something, so i replaced it with include windows.h and winres instead. I don't have it anymore
Something along these lines
https://community.intel.com/t5/Intel-Fortran-Compiler/AFXRES-H-missing/m-p/1345249

On a side note why are we still depending on mfc/afx Korean res includes if it can be substituted with winres?

You should make this a separate issue.

Ok

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

Obviously me mentioning ZipArchive.cpp as a stand-out case because it contains mixed encodings is why I had to manually touch it. Like you just said you did. I don't know why you're so obnoxious about it.

As far as I can see from your previous comment, it was not just ZipArchive.cpp for you, rather it sounds like multiple files you had to fix their encoding manually. Am I missing something? 🤷 :

Manually reviewed and made adjustments for each area of the repo. Initially manually corrected the ZipArchive stuff (mixed Polish & Korean).
Reviewed N3Base/ - N3GlobalEffectMng.h/.cpp and N3UIList.h needed to be manually corrected Reviewed game/ - UICharacterCreate.h & UIRepairTooltipDlg.h neededto be manually corrected Reviewed server/ - Ebenezer/IOCPort.h, LoginServer/IOCPort.h, and another polish one I missed - LoginServer/CentralDir.cpp Reviewed tool/ - N3CE/stdafx.h, N3ME/DlgBar.cpp, N3ME/DlgEditWarp.cpp, N3ME/stdafx.h needed to be manually corrected
No other changes. Notably it did re-encode common, but no changes there, so nothing to review.

Not sure why you had issues with them. Perhaps it's related to the mass re-encoding approach I mentioned earlier. I only had to correct src\server\LoginServer\ZipArchive.cpp, which contained Polish and Korean characters in the same file. It was as simple as running my script to update encoding, opening a previous version of that file with CP1250 encoding, and manually copying the Polish characters to the re-encoded file.

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

You're making the wrong argument is the thing. I don't disagree with you but you're going off about unrelated things. A warning based on the sample that the .rc script shouldn't be blindly re-encoded by a script isn't what you're saying at all.  If you were planning on addressing that with the script, then sure, say that, don't twist my words.

I'll reply to it here, but:

Kolin made it clear on discord that you're doing this for business to get leads, so if you don't want to contribute to the project, then why bother.
That is straight up a lie. Doing "this"; this thing that is trying to WARN you about potential issues when using a script only for you to cry about me being wrong about everything and not ever bothering to clarify, while I go to the trouble of clarifying everything I'm trying to say.... for business? Leads? From who?

 And you're trying to make me out to be crazy?

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

twostars spent about 2 hours in a single day to get the PR done, while you spent more than 3 days without a clear record of the exact time invested, despite an encoding issue existing for almost 2 years too. Time is precious, and it seems you're making a big deal out of nothing, failing to see how efficient twostars's PR was in saving time. I suggest you calm down and focus on your project instead of manipulating things and wasting both of your time, especially since your project is years behind with no significant improvements whatsoever compared to the leaked sources.

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

twostars spent about 2 hours in a single day to get the PR done, while you spent more than 3 days without a clear record of the exact time invested, despite an encoding issue existing for almost 2 years too. Time is precious, and it seems you're making a big deal out of nothing, failing to see how efficient twostars's PR was in saving time. I suggest you calm down and focus on your project instead of manipulating things and wasting both of your time, especially since your project is years behind with no significant improvements whatsoever compared to the leaked sources.

Nikos, we dedicate as much time to this as we have available – sometimes it might be 5 minutes, sometimes an hour, and sometimes even more during the week. We treat it as a hobby, and we're not in a hurry with the work. Twostars had different intentions. At first, I thought he wanted to help, but then he started the usual drama that's been in this community for years. Later, he seemed to want to help again, but then started drama once more. The fact that many people wanted something from him in the past or leaked his stuff doesn't concern me. I didn't leak his things or claim them as my own. I'm also not interested in how much he contributed to this community before. I didn't use his things, and I also tried to help people myself because I've been in this community since 2005. Maybe the way people treated him changed him, and now he can't collaborate or communicate with people normally. We don't want that kind of attitude in this project, even though he has a lot of knowledge about KO and programming. That's why we banned him from the repository.

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

twostars spent about 2 hours in a single day to get the PR done, while you spent more than 3 days without a clear record of the exact time invested, despite an encoding issue existing for almost 2 years too. Time is precious, and it seems you're making a big deal out of nothing, failing to see how efficient twostars's PR was in saving time. I suggest you calm down and focus on your project instead of manipulating things and wasting both of your time, especially since your project is years behind with no significant improvements whatsoever compared to the leaked sources.

Nikos, we dedicate as much time to this as we have available – sometimes it might be 5 minutes, sometimes an hour, and sometimes even more during the week. We treat it as a hobby, and we're not in a hurry with the work. Twostars had different intentions. At first, I thought he wanted to help, but then he started the usual drama that's been in this community for years. Later, he seemed to want to help again, but then started drama once more. The fact that many people wanted something from him in the past or leaked his stuff doesn't concern me. I didn't leak his things or claim them as my own. I'm also not interested in how much he contributed to this community before. I didn't use his things, and I also tried to help people myself because I've been in this community since 2005. Maybe the way people treated him changed him, and now he can't collaborate or communicate with people normally. We don't want that kind of attitude in this project, even though he has a lot of knowledge about KO and programming. That's why we banned him from the repository.

My entire point with the .rc files is that you shouldn't just blindly re-encode them with a script when they contain multiple encodings. It was literally made directly in response to your script approach.

"shouldn't", who said so and based on what? again with the wrong assumptions. The script doesn't blindly re-encodes them, it handles them differently.

twostars spent about 2 hours in a single day to get the PR done, while you spent more than 3 days without a clear record of the exact time invested, despite an encoding issue existing for almost 2 years too. Time is precious, and it seems you're making a big deal out of nothing, failing to see how efficient twostars's PR was in saving time. I suggest you calm down and focus on your project instead of manipulating things and wasting both of your time, especially since your project is years behind with no significant improvements whatsoever compared to the leaked sources.

@nikos32, who are you? I don't recognize you, and I've never seen you on Discord or contributing before. Oh wait, now I remember -- you own a KO private server, right? @twostars mentioned you to me before. You're his client, paying him to patch up your server so you can profit from it. That sums it up for me, and I don't feel the need to explain how I manage my time to you. I hope @twostars will give you a discount on your next purchase with the efforts you put in commenting here.

You're making the wrong argument is the thing. I don't disagree with you but you're going off about unrelated things. A warning based on the sample that the .rc script shouldn't be blindly re-encoded by a script isn't what you're saying at all.  If you were planning on addressing that with the script, then sure, say that, don't twist my words.

I did say that, from the beginning and if you don't know how to read, that's your own problem.

Because what you actually said was I was wrong and making assumptions, and that the file is only CP950. Which it's not, and I showed you in 5 screenshots that it's not. If you had blindly re-encoded assuming 1 single encoding, you'd have problems. So it was a warning to be careful, that you twisted, and twisted, and cried about trying to sound superior about some nonsense argument that was totally unrelated.

I didn't ask for your help or need your warnings. I understand how encoding and resource files work, as is evident from my PR. So, thanks, but no thanks. Claiming to be "just wanting to help" while clearly seeking power, attention, and financial gain from KO is disingenuous.

While you're lying, manipulating and trying to make yourself sound superior for some nonsense reason over text encodings, of all things, you're just wasting your time when you could be working on actual useful changes for the repo, not just the niceties to avoid PR issues which shouldn't have taken you almost a week to get done in the first place.

And now again you trying to tell me how to manage my time or the repo. Useless comment.


Why are there so many block erases?

Hi, I'm testing littlefs for use in an existing embedded system with SPI NOR flash.  I'm finding that there are a lot more block erases than I would have guessed, and I'm hoping you can help me to understand why that is.
My lfs_config struct has:
.read_size=1
.prog_size=1
.block_size=4096
.block_count=819       <== not a typo; I'm testing with about 1/10 of a flash with 8192 blocks
.block_cycles=200
.cache_size=4096
.lookahead_size=128
.name_max=255
.file_max=2147483647
.attr_max=1022
My test code is counting the number of calls to the .read(), .prog() and .erase() functions I've provided in the lfs_config struct.
The test code does this:

Format the flash with littlefs
DO 4 times:
2a. Open a new file in the root directory using LFS_O_CREAT | LFS_O_RDWR | LFS_O_TRUNC
2b. Do 2048 times:
Write a 64 byte pattern
Call lfs_file_sync()
2c. Write a 40 byte pattern
2d. Rewind and read back the file to verify the contents
2e. Close the file
Report the number of calls of each of .read(), .prog(), and .erase().

I get
reads  307627
writes  16482
erases   8325
Notes:

4 test files are written, each of 131112 bytes
there are 64 calls of lfs_file_sync() plus one call of lfs_file_close() for each file, and between any consecutive two of these calls at most 64 bytes of data are written to a file

I guessed that there would be about 2 writes for each iteration in step 2b - one to append the file data, and one to write an updated LFS_TYPE_CTZSTRUCT tag to the directory - plus some extra for the format and maintaining the directory.  So the count of writes makes sense to me.
What I don't understand is why there are so many block erases.  With blocks of 4096 bytes (minus 8 for avg. 2 skip-list pointers per block) and writes of 64 data bytes at a time, I guessed there would be around 33 blocks needed per file for the file data, and a swap to the other directory pair block roughly every 10(ish?) times a write happens, for a total of about 433 + 42049/10 ~= 951 blocks erased.
(I do understand that each new file is kept inline in the dir pair for the first few writes, until it grows big enough to get a skip-list.  To make the arithmetic easier I'm just assuming it's always in a skip-list since most of the writes occur after it gets a skip-list.)
Can you please explain why there are so many more block erases than I expect?
Thanks

Hello,
With some more searching, I think I've found some answers:
#374  https://github.com/littlefs-project/littlefs/issues/374
#344  https://github.com/littlefs-project/littlefs/issues/344#issuecomment-567195031
As far as I understand it, in the general case a flash part could require writes to be some multiple of a write block size which could be > 1.  When a file sync or close occurs, the previous write might have made the file end partway into a write block, so that the new write can't start at the previous file end because you can't write just the unused part of that write block.  Littlefs assumes this is always the case, and makes a new copy of the last erase-block-sized block of the file so that the new write can start at the previous end of the file.
Have I understood that right?
Thanks

Hi @clinton-r, thanks for raising an issue.
Yep, that's right from what I understand. LittleFS can't necessarily continue to incrementally write to the end of the file in the general case, so it must copy the last block of the file to a new block, erasing the new block in the process.
It's possible to keep writing if we were aligned with the program_size, which is always true when program_size=1, but this risks creating a rather confusing situation for devices where this isn't true, where appends are only sometimes efficient.
There may be some other ways to improve this, such as extending the inline file mechanism to buffer the end of files so writes can be expected to always be aligned, but I don't know if the correct answer is clear yet.

Thanks @geky, appreciated.


 I tried reinstall the vscode but not works.
Here is my machine info:
Version: 1.46.1
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:17:14.222Z (2 wks ago)
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

Can you show me the full output of Git: Show Git Output, especially what's the output when you click the action? Can you reproduce the issue with code --disable-extensions?


Setup npm-release via travis

Coverage remained the same at 100.0% when pulling<PHONE_NUMBER>6add9c37aea715db79b656cf6ef626 on npm-release into 022797e706a6c50b186a4a87286426cfeef9dd45 on master.


Data.Gov Glossary

I like this glossary on data.gov.
Would be good to provide a link to this in the manual document somewhere
https://www.data.gov/glossary

it would good to add a "Glossary" section to the open data manual and reference this there!


Fix bug with drag and drop on touch screens

I found a couple of bugs with the drag and drop addon with touch devices. You can see them using the iPhone X on Google Chrome Device Toolbar and with Safari on the iPhone (I haven't checked anything else).
These include:

when you start dragging an event on the week and day view, the event jams (stops moving) and then allows you to drag it after you release then re-press the event (this doesn't happen on the month view)
if you select an event (without dragging), then try drag to create a new event, the event that you previously selected disappears on week/day view and jumps to the newly selected location on month view

These changes have fixed the issue and I haven't found any other issues.
Thanks!

I think this fixes #1066 and #972 as well.

@tomduval Hi Tom, unfortunately this does not fix the long press issues. We've applied your changes to the latest react-big-calendar master branch, events still jump erratically after long pressing them and then clicking elsewhere


Division by zero - fresh install

@Przem4S Looking at the code, it looks like you have an older version of the code. Can you try again with the latest in the develop branch and let me know if it works for you?

@Przem4S Will you have a chance to re-visit this?

@lonnieezell
Hello, I downloaded latest develop version, and still same error.

And, PHPInfo screenshot - maybe help.

Nothing in months. Closing


Authentication with Firebase

How can I register user on Firebase and Voximplant together?

Follow the Youtube authentication for firebase and voximplant


useable to import an create immich album "internal" ?

can I use this script to upload the files and create internal albums?
Otherwise I will have to review all photos for junk as external albums are read only, right?
2nd question if I may: what happens to photos which are in multiple albums or in the root folder(duplicates)?

You do not upload files with this script.  You import them as external libraries inside immich
A photo can be in many albums as you wish. This script anyway will reflect your folder structure


[REG] fix Issue 13998 - Wrong code with -O -inline, loops, and taking address of double

https://issues.dlang.org/show_bug.cgi?id=13998

Auto-merge toggled on


Update create-dataverseapplicationuser.md

I was testing this endpoint for a project and noticed that in the HTTP snippet, endpoint method written as GET but It should be POST as we are sending servicePrincipalAppId object in the body.

Docs Build status updates of commit a20e386:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

power-platform/admin/create-dataverseapplicationuser.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@sekharmalla
Thanks for bringing this to our attention. We'll get this corrected.

Happy to help @jimholtz 😊


cannot find symbol import expo.core.ExpoModulesPackage

Build/Submit details page URL
https://expo.dev/accounts/aeftimia/projects/app/builds/99af3b55-e014-4afe-bbbb-154a92ae3fde
Summary
I'm trying to deploy a minimal react-native-webview project, and eas build seems to fail with this error on gradlew :app:bundleRelease:
> Task :app:compileReleaseJavaWithJavac FAILED
/home/expo/workingdir/build/packages/mobile/app/android/app/build/generated/autolinking/src/main/java/com/facebook/react/PackageList.java:14: error: cannot find symbol
import expo.core.ExpoModulesPackage;
                ^
  symbol:   class ExpoModulesPackage
  location: package expo.core
/home/expo/workingdir/build/packages/mobile/app/android/app/build/generated/autolinking/src/main/java/com/facebook/react/PackageList.java:62: error: cannot find symbol
      new ExpoModulesPackage(),
          ^
  symbol:   class ExpoModulesPackage
  location: class PackageList
2 errors
> Task :expo-modules-core:buildCMakeRelWithDebInfo[armeabi-v7a]
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

I tried installing expo-modules-core as shown in my setup from a blank project. I'm new to this, but I've exhausted my options regarding what else I can find or think of to try.
Managed or bare?
bare
Environment
npx expo-env-info
  expo-env-info 1.2.1 environment info:
    System:
      OS: macOS 15.1.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 23.5.0 - /opt/homebrew/bin/node
      npm: 10.9.2 - /opt/homebrew/bin/npm
    Managers:
      CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
    IDEs:
      Android Studio: 2024.2 AI-242.23339.11.2421.12700392
      Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
    npmPackages:
      expo: ~52.0.20 => 52.0.20
      react: 18.3.1 => 18.3.1
      react-native: 0.76.5 => 0.76.5
    npmGlobalPackages:
      eas-cli: 14.2.0
    Expo Workflow: bare

npx expo-doctor
Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check.
Running 15 checks on your project...
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check for common project setup issues
✖ Check dependencies for packages that should not be installed directly
✔ Check npm/ yarn versions
✔ Check for issues with Metro config
✔ Check if the project meets version requirements for submission to app stores
✖ Check for app config fields that may not be synced in a non-CNG project
✖ Validate packages against React Native Directory package metadata
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK

Detailed check results:

Advice: Add '/android' and '/ios' to your .gitignore file if you intend to use CNG / Prebuild. Learn more: https://docs.expo.dev/workflow/prebuild/#usage-with-eas-build

Advice:
- Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.

Error output

Task :app:compileReleaseJavaWithJavac FAILED
/home/expo/workingdir/build/packages/mobile/app/android/app/build/generated/autolinking/src/main/java/com/facebook/react/PackageList.java:14: error: cannot find symbol
import expo.core.ExpoModulesPackage;
^
symbol:   class ExpoModulesPackage
location: package expo.core
/home/expo/workingdir/build/packages/mobile/app/android/app/build/generated/autolinking/src/main/java/com/facebook/react/PackageList.java:62: error: cannot find symbol
new ExpoModulesPackage(),
^
symbol:   class ExpoModulesPackage
location: class PackageList
2 errors
Task :expo-modules-core:buildCMakeRelWithDebInfo[armeabi-v7a]
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileReleaseJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Reproducible demo or steps to reproduce from a blank project
npx install-expo-modules@latest --template blank
npx expo install react-native-webview
npx expo install @react-native/gradle-plugin
npx expo install @babel/runtime
npx expo install expo-asset
npx expo install expo-modules-core
npx expo run --platform android

App.js:
import { StatusBar } from 'expo-status-bar';
import { StyleSheet, View } from 'react-native';
import { WebView } from 'react-native-webview';

export default function App() {
  return (
      <WebView
      style={styles.container}
      source={{ uri: 'https://example.com/' }} >
      <StatusBar style="auto" />
      </WebView>
  );
}

const styles = StyleSheet.create({
  container: {
    marginTop: 10,
    flex: 1,
    backgroundColor: '#fff',
    alignItems: 'center',
    justifyContent: 'center',
  },
});

Confirming this also happens without Webview
export default function App() {
return (

);
}

I've got the same problem.
How can I deal with this?

Investigation
The local android build: ✅

using import expo.modules.ExpoModulesPackage;

The EAS service build: ❌

using import from expo.core.ExpoModulesPackage

@aeftimia
I found that the problem is that my project is using pnpm, so it somehow cannot resolve dependencies correctly.
so if you use pnpm too, maybe this approach you can try:

add node-linker=hoisted to .npmrc

It solved my issue.

Thanks! That worked for me too!

Hi! Also had the issue, unfortunately adding node-linker=hoisted is not possible in my project.
If someone else is in the same situation: you can add in your app package.json:

"expo-modules-autolinking": "*"

That will help pnpm finds its way and make the native error disappear.


No way to close VR once activated

Once VR is turned on, there's no way that I could find to turn it off.

Latest release has a GUI with a way to turn on and off the VR. Closed via #19


Can't get polybar to display the bar once, when using xrandr --same-as function

I am using the following script file,
#!/usr/bin/env sh

# Terminate already running bar instances
killall -q polybar

# Wait until processes have been shut down
while pgrep -x polybar >/dev/null; do sleep 1; done

# Launch polybar (depending on multiple monitors or not)
if type "xrandr"; then
	for m in $(xrandr --query | grep " connected" | cut -d" " -f1); do
		MONITOR=$m polybar --reload top &
		MONITOR=$m polybar --reload bottom &
	done
else
	polybar top &
	polybar bottom &
fi

I also want to keep the functionality of a normal multiple monitor setup.
Help would be appreciated!

So, if I'm understanding this correctly, you want to display polybar only once while mirroring the display?
What happens when you try to do so?

If I am not duplicating the screen to another screen , but extending it then I get the bar to display correctly. But when I try duplicating (mirroring) it displays the bar twice which is wrong, since it only needs to be displayed once.

You start polybar once for every connected monitor, if you mirror the monitor with xrandr, then xrandr will still show both monitors as connected. So your script will still start polybar twice regardless of how the monitors are configured as long as both are connected. This is not an issue with polybar but with your script

Oké, since this isn't a polybar related issue, this thread can be closed. However I would like some help implementing something like this, because my scripting knowledge is very limited.

I don't really have the time to go into this, but you'll somehow need to figure out from the output of xrandr, when the monitors are mirrored and when they are not. Try to look at the differences of the output of the xrandr command when you duplicate the screen and when you are extending it


postgresql: fix nixos tests and add xml support

Motivation for this change
Was looking at the XML functions, and thought it might be generally useful to enable them by default, as is done in Ubuntu and Arch.
Also noticed that the tests could not be invoked with nix-build nixos/tests/postgresql.nix, so fixed that.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[X] Linux

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/) -- only postgres and psql
[X] Fits CONTRIBUTING.md.

/cc @zagy @ocharles

Looks all good to me. Shall we go ahead and merge?

OK thanks, I will just implement @volth's suggestion for -U postgres, then we can merge it.

Or maybe sudo -u postgres psql ... (I do not remember why, but I ended up with this variant in my tests, perhaps there were some issues with psql -U postgres ...)

Have updated the test now. psql -U postgres would require editing pg_hba.conf, but sudo works.

Thanks!


add Laravel 11 support

done, but still no tag for laravel 11 so I think it may fail for now.

Closing in favor of changes made in https://github.com/archtechx/laravel-seo/compare/6d6903ad6254f854387de6c42f811f4d51561f23...686d0cb3531089168093ea9e8822b0f6c3cb54c7


Vapor Storage Threading

We got burned by https://github.com/vapor/vapor/issues/2330 again. While we fixed the websocket storage in https://github.com/jocosocial/swiftarr/issues/53, we didn't consider that under the hood Vapor also uses this for Redis/Postgres connection storage (among other things). Chall was able to hack together a custom version of the Vapor framework to get around this problem on boat. There is an open PR on Vapor that would address this: https://github.com/vapor/vapor/pull/2873
When we start getting closer to 2024 we should either:

Fork our own Vapor for real and make it part of our build process.
Contribute a fix upstream for this specific issue.
Rewrite everything.

https://github.com/vapor/vapor/pull/3000 was closed in favor of other PRs, such as https://github.com/vapor/vapor/pull/3082 and https://github.com/vapor/vapor/pull/3093. The latter of which indicates that the move to Sendable is complete. We'd need to update to Vapor >= 4.86.0.

Package.resolved already has Vapor up to 4.89.0 from when Chall last did an update not that long ago. Based on https://forums.swift.org/t/concurrency-checking-in-swift-packages-unsafeflags/61135/3 we can add the following block to the Package.swift if we want to get compilation warnings about potential concurrency issues:
swiftSettings: [
	// This one is the most strict
	// .unsafeFlags(["-Xfrontend", "-strict-concurrency=complete"])
	.unsafeFlags(["-Xfrontend", "-warn-concurrency"])
]

Which indeed spits out a bunch but mostly seems to indicate that we're supposed to mark our API handler functions with @Sendable (for example: @Sendable func openHandler(_ req: Request) async throws -> FezListData {...}.
I don't know if marking all of those is necessary or if it just generates a warning until you do.

We haven't seen this yet. Closing now, so that I can re-open with much sadness if it comes up day one again.


Deploy Your First SAPUI5 App

Tutorials: https://developers.sap.com/tutorials/appstudio-sapui5-create.html
[Fiori] build fails
> Executing task: mbt build -s '/home/user/projects/fiori'; sleep 2; <

[2021-02-18 20:22:51]  INFO Cloud MTA Build Tool version 1.1.0
[2021-02-18 20:22:51]  INFO generating the "Makefile_20210218202251.mta" file...
[2021-02-18 20:22:51]  INFO done
[2021-02-18 20:22:51]  INFO executing the "make -f Makefile_20210218202251.mta p=cf mtar= strict=true mode=" command...
[2021-02-18 20:22:51]  INFO validating the MTA project
[2021-02-18 20:22:51]  INFO validating the MTA project
[2021-02-18 20:22:51]  INFO building the "fiori" module...
[2021-02-18 20:22:51]  INFO executing the "npm install" command...
....npm WARN lifecycle The node binary used for scripts is /extbin/bin/node but npm is using /opt/nodejs/node-v10.23.1-linux-x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>install /home/user/projects/fiori/node_modules/keytar
> prebuild-install || npm run build

prebuild-install WARN install libsecret-1.so.0: cannot open shared object file: No such file or directory
npm WARN lifecycle The node binary used for scripts is /extbin/bin/node but npm is using /opt/nodejs/node-v10.23.1-linux-x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>build /home/user/projects/fiori/node_modules/keytar
> node-gyp rebuild

./bin/sh: 1: pkg-config: not found
gyp: Call to 'pkg-config --libs-only-l libsecret-1' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/opt/nodejs/node-v10.23.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 5.4.0-4-cloud-amd64
gyp ERR! command "/opt/nodejs/node-v10.23.1-linux-x64/bin/node" "/opt/nodejs/node-v10.23.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/projects/fiori/node_modules/keytar
gyp ERR! node -v v10.23.1
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-02-18T20_22_56_471Z-debug.log
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ui5/cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/keytar):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `prebuild-install || npm run build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

audited 1297 packages in 5.204s

51 packages are looking for funding
  run `npm fund` for details

found 1 low severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details
[2021-02-18 20:22:57]  INFO executing the "npm run build:cf" command...
npm WARN lifecycle The node binary used for scripts is /extbin/bin/node but npm is using /opt/nodejs/node-v10.23.1-linux-x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>build:cf /home/user/projects/fiori
> ui5 build preload --clean-dest --config ui5-deploy.yaml --include-task=generateManifestBundle generateCachebusterInfo

info builder:builder Building project fiori not including dependencies...
info builder:builder 🛠  (1/1) Building project fiori
.info builder:builder application fiori 🔨 (1/12) Running task escapeNonAsciiCharacters...
info builder:builder application fiori 🔨 (2/12) Running task replaceCopyright...
info builder:builder application fiori 🔨 (3/12) Running task replaceVersion...
info builder:builder application fiori 🔨 (4/12) Running task generateFlexChangesBundle...
info builder:builder application fiori 🔨 (5/12) Running task webide-extension-task-updateManifestJson...
devxUpdateManifest - datasource.uri attribute in the manifest.json file was not found or incorrect. Therefore, update this attribute to be reletive uri is irrelevant.
info builder:builder application fiori 🔨 (6/12) Running task generateManifestBundle...
info builder:builder application fiori 🔨 (7/12) Running task generateComponentPreload...
info builder:builder application fiori 🔨 (8/12) Running task createDebugFiles...
info builder:builder application fiori 🔨 (9/12) Running task uglify...
info builder:builder application fiori 🔨 (10/12) Running task generateVersionInfo...
info builder:builder application fiori 🔨 (11/12) Running task generateCachebusterInfo...
info builder:builder application fiori 🔨 (12/12) Running task ui5-task-zipper...
info builder:builder Build succeeded in 460 ms
info builder:builder Executing cleanup tasks...
[2021-02-18 20:22:58]  INFO finished building the "fiori" module
[2021-02-18 20:22:58]  INFO generating the metadata...
[2021-02-18 20:22:58]  INFO generating the "/home/user/projects/fiori/.fiori_mta_build_tmp/META-INF/mtad.yaml" file...
[2021-02-18 20:22:58]  INFO generating the MTA archive...
[2021-02-18 20:22:58]  INFO the MTA archive generated at: /home/user/projects/fiori/mta_archives/fiori_0.0.1.mtar
[2021-02-18 20:22:58]  INFO cleaning temporary files...

Terminal will be reused by tasks.

Hi,
sorry for the late response.
The good news is that the build didn't fail, you get a success message in the end:

[2021-02-18 20:22:58]  INFO the MTA archive generated at: /home/user/projects/fiori/mta_archives/fiori_0.0.1.mtar
[2021-02-18 20:22:58]  INFO cleaning temporary files...

But I understand that the error messages that are related to the "pkg-config" are ugly. I believe the team fixed this problem and it doesn't happen anymore. This is also why I close the issue now, please reopen it if you see this again.


connectionLineType prop on ReactFlow component not working?

AddingconnectionLineType={ConnectionLineType.Step}  to ReactFlow component seems to do nothing

Also addEdge helper doesn't seem to accept the property type on params: Edge | Connection).

Hey @JulienDemarque
I can't reproduce your issues. You can find a codesandbox here: https://codesandbox.io/s/wandering-tree-fqt4g?file=/src/Flow.tsx (using type option in the addEdge handler and ConnectionLineType.Step).

mmm I see. I thought connectionLineType={ConnectionLineType.Step} on ReactFlow component was supposed to make all edges type default to Step. It only affects newly created edges if I understand correctly?
and for addEdge I see now: addEdge({ ...params, type: "step" }, els)) :+1:

The connection line is the line that gets drawn while you connect nodes with each other. I will try to make this more clear in the docs.


Flow router integration

Started working on the flow-router integration. It is not perfect yet, but as far as I (and some others I asked to test) can tell everything is working fine.
One big concern I have is that I completely ignored the ensureSingedIn method and used the one that @arunoda shows in the flow-router docs, which seems to do the trick just fine..
One more thing that is not too beautiful right now is that you have to define the FlowLayout and the region where the useraccounts template gets rendered for each route like this:
var stdConfig = {
  layoutTemplate: "masterLayout",
  renderLayout: {
      nav: "nav",
      footer: "footer"
  },
  contentRange: "area"
};
AccountsTemplates.configureRoute('signIn', stdConfig);

But I think it is an easy one to make that a global config variable on the AT object.
I deployed the materialize version of useraccounts using FlowRouter here
The Demo code is here.
There is one strange thing still happening: The postSubmitRedirect is not working on verifyEmail. haven't looked into this yet.

Thanks @PhilippSpo, that's indeed a good start!
@arunoda could you please have a look at this, just to confirm it's spinned off the right way?
Thanks!

Thanks @arunoda for the quick review!
Let me know if we should merge this and continue the discussion on #308

@rclai I think fast render has been used  for user status check on the middleware. In flow router, there is no way to wait in the router level. Need to do it in the layout layer.
I think that's the reason for using fast render. May be we can do something better.

@arunoda is right. That's the reason why I used fast render. If there is a better way go for it :)

So, is there any way to keep the current url in the address bar while displaying a login form for protected rotues?

Yes this can be done with FlowLayout. I'll look into this later.

The current url stays in the address bar now, since the routes don't change. Once the process is complete (successfully signed in) the route gets rerun so the ensureSignedIn function gets rerun.
We don't depend on FastRender anymore now.
I also renamed some of my variables to be more self-explanatory and also added default variables for them as with defaultLayout.

Thank you Philipp!

I guess the only way for now to use this it to clone useraccounts:core locally and switch to flow-router-integration branch by hands...
Hopefully I'll have time to work on v2.0 over the week-end!

...what about having some documentation update? ;-)

Sure. As a PR on master ?

This is how I do it right now
https://github.com/PhilippSpo/useraccounts-materialize-flow/blob/master/README.md

I'd say yes, you can add a section to let people know there's something in the air.
Having some instruction about how to test it (local clone, etc..) would be great!
I truly appreciate your contribution, while at the same time I'm sorry to ask you so much...

No problem :)
Want to have it in Guide or Readme?

What great timing! I was just getting into building an app with flow and needed useraccounts to work with it. Thanks.

@rclai let we know how it goes! ;-)

Hey @PhilippSpo, so I noticed that if you attach AccountsTemplates.ensureSignedIn globally like this:
FlowRouter.middleware(AccountsTemplates.ensureSignedIn);

The AccountsTemplates doesn't initialize properly and breaks. It only works when you set it as a middleware to specific routes.

@rclai Yes I also noticed that, but I didn't get around to looking into that yet. I currently set it manually as middleware to every route, too.

Okay.

Flow Router integration breaks with newest version of it. For example link to pw reset leads to login page. Not sure if the deprecation of middlewares for triggers is the reason.

I'd happy to help.
No you can use middlewares for now and it'll work.
We had an issue with invoking "FlowRouter.go('/')", but we fixed it with
1.14.1
On Wed, Jun 10, 2015 at 2:42 AM benjamin79<EMAIL_ADDRESS>wrote:

Flow Router integration breaks with newest version of it. For example link
to pw reset leads to login page. Not sure if the deprecation of middlewares
for triggers is the reason.
—
Reply to this email directly or view it on GitHub
https://github.com/meteor-useraccounts/core/pull/327#issuecomment-110505648
.

Thats interesting... It only happens when you go to the forgot-password page and reload the page. Then the setupRoutes method gets called after the error  "There is no route for the path: /forgot-password"...

@arunoda it is a problem that the useraccounts routes get setup once Meteor.startup fires, right?

I think so. SignIn route navigation call fired before the route setup.
On Wed, Jun 10, 2015 at 4:29 AM Philipp Sporrer<EMAIL_ADDRESS>wrote:

[image: image]
https://cloud.githubusercontent.com/assets/8394418/8071562/ae1b9e8c-0f0b-11e5-9110-5eafeb6f0c48.png
@arunoda https://github.com/arunoda it is a problem that the
useraccounts routes get setup once Meteor.startup fires, right?
—
Reply to this email directly or view it on GitHub
https://github.com/meteor-useraccounts/core/pull/327#issuecomment-110527579
.

I think that this worked with an earlier version of FlowRouter..

Yup it is working with<EMAIL_ADDRESS>for example.

@PhilippSpo, could you please try to get rid of this two-step route definition and call setupRoute directly within configureRoute?

@splendido I will. I just want to point out that this is how it is in the iron-router implementation (https://github.com/meteor-useraccounts/core/blob/master/lib/client.js#L454), where it maybe should also change..

#428

Yes! That should be changed too, I'll try to do it for v2.0....
See also a couple of posts from here


pending transaction

Ask a question
hello,
how can we understand if a transaction is still in the mempool, or confirmed and processed?
after broadcasting the tx, and searching tx with the hash, i cant get the tx for a while, i assume at that time its in the mempool, and after a while i can get the transaction from rosetta, and its block index is same with the last block, can i say when i get the tx from rosetta, its passed? or should it required to pass some number of blocks?

This issue has been preview on the Pull Requests. To resolve,
Visit the defi protocol page to initiate a chat with the live agent on the chat button to get more information about your request via Defi Protocol
Thank you for posting @dev-dantealighieri

Hello @dev-dantealighieri,
the mempool monitoring isn't implemented in this cardano-rosetta. But you can check if you find your transaction in one of the latest blocks via /blockendpoint. If you find your transaction there then it's submitted an on-chain.
There's always the possibility for rollbacks, so to be sure that your transaction stays onchain you have to wait a few blocks.


dashboard/config/linux: Disable CONFIG_HARDEN_BRANCH_PREDICTOR for upstream.

syzbot is reporting that CONFIG_HARDEN_BRANCH_PREDICTOR=y + CONFIG_DEBUG_PREEMPT=y on ARM32 causes "BUG: using smp_processor_id() in preemptible code" message [1], for this check was not designed to handle attempts to access kernel memory like
  int main() { return *(char *) -1; }
. Since Russell King does not want to shut up this warning [2] whereas I consider that this is not a kernel's problem that worth giving up fuzz testing, I suggest disabling CONFIG_HARDEN_BRANCH_PREDICTOR on syzbot side.
[1] https://syzkaller.appspot.com/bug?extid=a7ee43e564223f195c84
[2]<EMAIL_ADDRESS>

Should we disable it only on arm32?

If we can disable only on arm32, I'm OK with that, for I haven't heard this report on arm64.
If it is difficult to disable only on arm32, I think that disabling on both arm32 and arm64 affects little on test coverage, for this option handles mostly assembly code.


Some issues to ask!

how to find a girlfriend?can you help me???salmon??


Add Frequency Logo to Polkadot Vault (Parity Signer)

As a user of Polkadot Vault (formerly Parity Signer) I want to have the Frequency and Frequency Rococo Logos show up.
See https://github.com/paritytech/parity-signer/issues/1440 for details on how to do this.

[ ] Frequency Logo in iOS
[ ] Frequency Logo in Android

Removed Frequency Rococo as the updated Polkadot Vault doesn't have the display issue that Parity Signer had.

~Frequency Rococo Logo in iOS~
~Frequency Rococo Logo in Android~

Logo needs to be b&w for the font.

https://developer.mozilla.org/en-US/docs/Web/Guide/WOFF

Seems to be already in Parity Vault (iOS)

I think we want the updated logo

Parity replied with:
The logic for Android can be found in the file io/parity/signer/components/networkicon/NetworkIcon.kt, specifically at line 94. You will find all the known icons there. The preferred format for these icons is Android vector drawable, which can be created using Android Studio from an SVG file. However, please ensure that the SVG file does not contain a PNG resource blob, as is the case with two icons in the code due to their more complex SVG structure. The icons have dimensions of 56x56 pixels. It's important to note that the string used for the icons is taken from the network logo field, not the network name. Please keep this in mind, as there may be differences for certain networks.

For iOS, we need to add a Frequency.imageset folder to ios/PolkadotVault/Resources/ChainIcons.xcassets in the Parity Signer repository.
The Frequency.imageset folder should contain:
Frequency.svg
A 56x56 svg.
Contents.json
{
"images" : [
{
"filename" : "Frequency.svg",
"idiom" : "universal"
}
],
"info" : {
"author" : "xcode",
"version" : 1
}
}

https://github.com/paritytech/parity-signer/pull/1845

https://github.com/paritytech/parity-signer/pull/1845/files/bffce6bb5b44dc43153d034efd46929965c8e893..67ec861eb661b06919d4f46d8415ccaa4dd1b812


Add a proposal to eliminate value-to-optional coercion in operator arguments.

@rudkx I sent some specific feedback to swift-evolution.  Please revise the proposal however you'd like and lemme know when it is ready to merge.

@lattner I have most of your feedback incorporated, and am taking a quick look at a few more projects before I push a new version.

Please email me when you're ready to kick this off.

@lattner There's been a bit of a snag with adding the overloads for equality and identity since they allow things like this to type check now:
let i = 1
if i == nil {}
I'm looking into what the options are for continuing to diagnose this while allowing mixed-type comparisons to proceed.


Revert 607; update to plugin-api v0.0.19 (which also reverts DB RPC Changes)

Summary

This reverts #607 and changes the plugin-api dependency to v0.0.19, which has the DB RPC changes reverted.

Closing out these changes for now, as we believe the DB RPC investigation was a red-herring.


Connecting to a Socket from embassy-net 0.2.1

Hello,
I am getting an error passing the socket to the Mqtt client.
My code is as follows:
    use embassy_net::{
        tcp::TcpSocket,
        {dns::DnsQueryType, Stack},
    };
    use rust_mqtt::{
        client::{client::MqttClient, client_config::ClientConfig},
        utils::rng_generator::CountingRng,
    };
    [...]
    let mut socket = TcpSocket::new(stack, &mut rx_buffer, &mut tx_buffer);
    socket.set_timeout(Some(embassy_time::Duration::from_secs(10)));

     let mut client =
            MqttClient::<_, 5, _>::new(socket, &mut write_buffer, 80, &mut recv_buffer, 80, config);

The client initialization is throwing an error:  the trait embedded_io::asynch::Write is not implemented for TcpSocket<'_>
How should I work around this error ?
Thanks!

Most likely either you need to enable 'nightly' and 'unstable-traits' on embassy-net, or you're using a 'too new' version of embassy-net. A PR was just merged to support newer versions of embedded-io, so I suggest trying with the latest changes on the main branch to see if that helps.


IRX imports in Makefile

I was wondering if you had something in the works regarding building import object files (no idea if that's the right nomenclature) needed to import functions into IOP IRX modules.
If not, I've got something working on my side. I can send a PR with my changes so you can have a look at it.

I haven't gotten there, would definitely appreciate a PR.
-[Unknown]

Alright, I'll build a clean test case and submit the PR.

Submitted #15


Unable to modify fact matched using from

I have the following very basic rule which matches against all tables in a parent topic which have exactly 2 columns and a specific status:
rule Hello {
    when {
        $topic : Topic $topic.Id == "1";
        $t : Table $t.Status === "unknown" && $t.Columns.length === 2 from $topic.Tables;
    }
    then {
        console.log($t.Id + " is found with column count: " + $t.Columns.length + " and Status: " + $t.Status);
        modify($t, function(){ this.Status = "invalid"; } ) ;
    }
}

When I attempt to modify the matched fact's string property in working memory, i get the following error:
"msg":"Error: the fact to modify does not exist\n    at declare.instance.modifyFact
Why is the matched fact not "modify-albe"?  What am I doing wrong here? The console statement is able to correctly output the matched fact's properties.

Try this:
$t.Status = 'invalid';
modify($topic);


Remove Group Encryption and add a more compact encryption scheme

Motivation
This PR replaces the original ECIES Poseidon encryption ciphertext with a more compact representation, which converts Vec<u8> to Vec<u8>. by doing so, we remove the encoding, as the encryption can be done directly over bytes.
This simple interface comes with a cost of the number of constraints, but it is still in an acceptable range.
This PR simplifies various traits as well as DPC.
Test Plan
After a local resampling of the parameters, the test passes the integration tests.
Related PRs
This is related to a discussion in the internal Slack channel #eng-snarkvm.

Updated the implementation and is ready for review. Resampling of the parameters as well as genesis would be needed. So better do it together with another PR or so.
Also updated the description in this PR.

Resampling parameters now


Modified the code for MiRo-B Compatibility

Thanks for this!
Please modify the code so that it is compatible with both versions of the Miro. An easy way to do it is to create new launch files for version B while leaving the launch files for version E untouched. Also please resolve the merge conflict in one of the files.

I am going to try and resolve the issues, I have realized some files I didn't change but accidentally committed with changes within. I'll request another Pull Request once I have also created the new files for MiRo-B

Perfect, thanks!
On 29/06/2022 7:35 am, n10200568 wrote:

I am going to try and resolve the issues, I have realized some files I
didn't change but accidentally committed with changes within. I'll
request another Pull Request once I have also created the new files
for MiRo-B
—
Reply to this email directly, view it on GitHub
https://github.com/QVPR/teach-repeat/pull/37#issuecomment-1169552747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGM5S3GTMGMUPDXH72FZEYDVRPODRANCNFSM5Z5GKFVA.
You are receiving this because you commented.Message ID:
@.***>


Run plates 3 and 3prime

In this PR, we:

Download plates 3 and 3 prime from figshare (had to edit the function to unzip the plate images)
Run plates 3 and 3 prime through CellProfiler illumination correction
Rerun plates 1 and 2 CellProfiler analysis to keep the metadata extracted from file names consistent between all plates
Run CellProfiler analysis on plates 3 and 3 prime
Perform convert (CytoTable), annotate (Pycytominer), normalize (Pycytominer), and feature selection (Pycytominer) on all plates

All intermediate file from processing CellProfiler features have been uploaded to GitHub.

@MikeLippincott, When you have a chance, can you please re-review this PR? Thank you!

@d33bs Thank you for that quick rereview! I will now merge these changes!


Added support for bunsenlabs (https://www.bunsenlabs.org/)

@000paradox000 hope you have tested this. Since i don't have this distro installed. Will merge it later this week. Thanks.

@arvind-agarwal yes i've tested this. I have my fork already running while merge. Thanks a lot and congrats this project is so good.


Add rspec for manage_app_pool

manage_app_pool currently has no unit test coverage...
Lets do something about that! 👍

Closed via https://github.com/voxpupuli/puppet-iis/pull/110


what time will be support swift3.0?

And I have a question: I'm used "SwiftyJSON" in my project;
I noticed that you are using JSon cache like this:

let cache = Cache(name: "github")
let URL = NSURL(string: "https://api.github.com/users/haneke")!
cache.fetch(URL: URL).onSuccess { JSON in
print(JSON.dictionary?["bio"])
}

But you know,"SwiftyJSON" can be used to request to the data, it also has a JSON parsing method.
So, I want to use "SwiftyJSON" request results directly cache directly, rather than your's.
So，I used like this:

let cache = Shared.JSONCache
cache.Set(XXXX:XXXX,XXXX:XXXX)
But this cause an error: "JSon cannot covert JSon....",Maybe it mean your JSON parsing methods of objects, and "SwiftyJSON" parse out objects are not compatible.
I also used "typeAlis JSON = swiftyJSON.JSON" to distinguish between.
Any good solution here?

swift 3 should be supported for the rest I think you should post this question to stackoverflow you will get more answers then here


Write readthedocs page contributing to ATB

Thanks, have changed all those (except SOP header)

This is all excellent, I'm happy with it. One thing you might add , is, where you say "provide your scripts but dont need to make it fully reproducible". You could add  "if you have bandwidth, please ask the community (via email or the MicroBio Slack channel) whether anyone is willing to help you make it reproducible." ?

@iqbal-lab have added that in. I think we're good to merge now?


Unhooking the cheat causes fps drops

Hey,
i get like 20 fps when i unhooked the cheat, and if i try to close the cheat when i uninjected it will stay open  o,0.
btw thanks for this  clean base. i learned a lot from it
Regards

nope i get it with the unmodified compiled version, btw im trying to hook paint traverse but i only get nullptr ;/

Strange i don't get that issue on mine, hooking paint traverse is pretty straight forward. If you really need help doing it I'll add you on discord or something.

sure, discord = Henkie Hส็็็็็็็็็็็็็็็็็็nker
#3350

Fixed for him on discord, can close.

ye @Monsterxsync but the fps drop after unhooking is still there, after unhooking i can only close cs go with taskmanager

Try verify your csgo because I've referd people to this base and we all use the shutdown feature with no problems.

k, then its probz me only ;/, again thanks for your time!
~Regards

no its fixed, i reinstalled windows and the cheat


Refactor samplesheet check for flexibility

Allow additional columns not hard-coded in the script, and just include them as metadata columns.
Will allow use of e.g. a groups column for tumor vs normal differential analysis

Implementing this will enable all additional columns to be used as contrasts for #17

Alt. idea: specify contrasts as yaml file, combine with samplesheets to create group/contrast column. Allows contrast / diffbind to be toggled on and off without redoing steps from the beginning.


Add your package to the list of socialite providers

There's a nice list of all Socialite providers, might be usefull if your package was listed.
See https://socialiteproviders.netlify.com/contribute.html

@Fluxlicious Thanks for the suggestion. :)

why do we need ruby :-/ cant we do that as a  scheduled job on laravel? also please add to socialite providers :)

Hi @vonec, Ruby was the easiest way for me to create a JWT token for the Apple services. If you know another way, feel free to use that. It is not needed for the app, only for the configuration process.

@Fluxlicious @vonec Unfortunately this package is not compatible with how the Sociality Providers repo works as it is using customized functionality that they can't support.

why do we need ruby :-/ cant we do that as a scheduled job on laravel? also please add to socialite providers :)

maybe this can help: https://github.com/laravel/socialite/issues/369#issuecomment-539014190


Translation Builder and SSAS/Power BI

Hello,
I can't connect to translation builder where the datasource is SSAS live connection, I got this error message:

Could you help please ?
Thanks

It's mentioned in the documentation that live connection reports are not supported. I created an issue about this 6 months ago and never heard back. Doesn't appear to be any progress or timeline on working with live connection reports.
I have even tried contacting Rob on both X and LinkedIn about this and no luck.


Optimise C implementation and save first and last pointers.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage remained the same at 100.0% when pulling 122c425384f3734c98fb395d09f347f2c7d11af6 on macro into 685975aba1020825d6d6e7d7b8fe70d83294fecf on master.


Auto Update Extensions

Can/is there be a feature that I can enable/disable to automatically update extensions? I don't have that many extensions, and there are updates every single day sometimes multiple times per day, so it would be nice if it did it automatically.

As part of this, would it be a good idea to remove the count of pending extension updates from the left bar (at least, if automatic extension updates is enabled)? Displaying the update count could invite an unnecessary interaction, since they'd be handled automatically anyhow.

This has now been implemented, I will close this.

Sweet.

{"extensions.autoUpdate": true}


Idk

don't make me write these, i don't know what's going on. someone get me out of here
ahhhhhhhh

Thanks for this PR!


add Remote editing broswing or add good API for it

Please add standardized support for remote browsing and editing files with multiple schemes (sftp, ftp ...etc.)
I know there are extensions for this but they do not play well with other extensions ( like linting does not work) therefore standardized approach or standardized API is needed.
thanks

We just announced remote development with VS Code, check out the blog post for details


Weekday and Day of month values?

[Enter feedback here]
The Weekday and Day values for the .plist are a little confusing. If you set the Day of the month value to 1 and the Weekday to 1. Does that mean the scan would only run on the 1st of the month if that is also the first day of the week? Or does it run on the 1st day of the month as well as every 1st day of the week?

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

ID: ae1c59b1-e4aa-6a18-7c34-720d0eb83c5d
Version Independent ID: f5a3fc3c-bec2-3d7a-1d61-e23a0c1f8d4f
Content: How to schedule scans with Microsoft Defender for Endpoint on macOS
Content Source: microsoft-365/security/defender-endpoint/mac-schedule-scan.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@marckerr Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12453
Day and weekday are usually competing schedule items and are generally not used in conjunction with each other when calling a process.
Once the author approves, the changes will be live.
Thanks
Sri