undefined method `resource_class' for nil:NilClass (NoMethodError)

app wont start after installing this gem in rails 7 app
Bug report
nimble-auth/lib/nimble_auth/resource_setup.rb:12:in extend_user_model': undefined method resource_class' for nil:NilClass (NoMethodError)
from /Users/prakash/workspaces/2021/invoice_work/engines/nimble-auth/lib/nimble_auth/engine.rb:21:in `block in <class:Engine>'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:415:in `instance_exec'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:415:in `block in make_lambda'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:199:in `block (2 levels) in halting'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:592:in `block (2 levels) in default_terminator'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:591:in `catch'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:591:in `block in default_terminator'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:200:in `block in halting'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:500:in `block in invoke_before'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:500:in `each'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:500:in `invoke_before'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/callbacks.rb:106:in `run_callbacks'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/reloader.rb:88:in `prepare!'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/application/finisher.rb:73:in `block in <module:Finisher>'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/initializable.rb:32:in `instance_exec'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/initializable.rb:32:in `run'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/initializable.rb:61:in `block in run_initializers'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:349:in `block in each_strongly_connected_component'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `each'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `call'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/initializable.rb:60:in `run_initializers'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/application.rb:369:in `initialize!'
	from /Users/prakash/workspaces/2021/invoice_work/config/environment.rb:5:in `<main>'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/zeitwerk-2.5.0.beta4/lib/zeitwerk/kernel.rb:35:in `require'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `require_relative'
	from config.ru:3:in `block in <main>'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in `eval'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in `new_from_string'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:105:in `load_file'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:66:in `parse_file'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:349:in `build_app_and_options_from_config'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:249:in `app'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:422:in `wrapped_app'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/server/server_command.rb:76:in `log_to_stdout'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/server/server_command.rb:36:in `start'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/server/server_command.rb:143:in `block in perform'
	from <internal:kernel>:90:in `tap'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/server/server_command.rb:134:in `perform'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/command/base.rb:87:in `perform'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/command.rb:48:in `invoke'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands.rb:18:in `<main>'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/prakash/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from bin/rails:4:in `<main>'
	```

This error was occuring due to missing nimble-auth initializer in my project. Closing this


Add TypeScript type declarations.

Hi there! I've started using this library in one of my projects, and thought you might have some use for the TypeScript type declarations I ginned up to support TS. I think they're accurate to the docs, but please let me know if it looks like I missed anything. And thanks for this module, it's super handy!

Coverage remained the same at 100.0% when pulling bf7f17638fbacd54080718287dabc50740bef444 on ignota:master into c899153332c13480ea384be03266924ae8eb7052 on sagiegurari:master.

Thank you very much. I'll review later on today/tomorrow and push it 👍

really cool. merged!!

Thanks! Glad I could contribute.


Add Freedom Dive (ORIGINAL SONG) for Freedom08 by XI

Song Name
Freedom Dive
Artist Name
XI
Source
Youtube
Youtube Link
https://youtu.be/k-3y2LVF_SE?si=OyWSP6b5BOXjqQ4P
Direct File Link
https://www.mediafire.com/file/5db0bwwtmqb445u/Freedom_Dive%2528MP3_320K%2529.mp3/file
Song ID
735623
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 55274070 (FREEDOM08)
Downloaded: Yes

accept

accept


Merge-MailboxFolders

Add Target Mailbox to CSV import feature.

Hi David,
When i try the approach below, i get a prompt for the web URL after ever mailbox is processed. Is there a quick way around that by reusing the existing URL code? It appears that is what the script is meant to do with the existing CSV implementation you built in anyway.
#Script Name = MirrorMailboxContents.ps1
start-transcript -path .\MirrorMailboxContents.txt
Import-Csv MirrorMailbox.csv | ForEach-Object{
$SourceMBX = $.UserPrincipalName
$TargetMBX = $.UserPrincipalNameShared
.\Merge-MailboxFolder.ps1 -SourceMailbox $SourceMBX -TargetMailbox $TargetMBX -ProcessSubfolders -CreateTargetFolder -Office365 -OAuth -OAuthTenantId "01088aa4-1bdc-42ad-xYYx-17ef028779fc" -Copy
}
Stop-transcript

Assuming you mean an auth prompt, you'll need to use app auth to avoid that.  Delegate auth will prompt each time the script is run.

https://github.com/David-Barrett-MS/PowerShell-EWS-Scripts/wiki/Exchange-Online-OAuth-Configuration


Update the link in README.md

The link https://github.com/databrickslabs/pyspark-ai/blob/master/examples/dataframe_transformation.ipynb does not exist. It needs to be fixed in README.md

Thanks, merging to master!


gha: make release workflow work in forks

Fixes #5098.
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>

/retest

/retest

Validated on fork https://github.com/dmcgowan/containerd/releases/tag/v1.6.0-alpha.1


Show depreciation notice for the old GKE integration in the admiral UI

https://github.com/Shippable/pm/issues/9159

verified on rc


Ability to override where help text is sent

 Issue by tgardner851
Wednesday Mar 22, 2017 at 23:17 GMT
Originally opened as https://github.com/gsscoder/commandline/issues/426

For example, I need to intercept the text and not send it to the console, but elsewhere.

 Comment by nemec
Thursday Mar 23, 2017 at 16:55 GMT

If you build your own parser instead of using the default, you can provide a ParserSettings and can set a custom HelpWriter in that class.


Router handles normal anchor links as internal URLs

Description
We're using a mix of Gridsome pages and Wordpress pages within the same domain.
/:slug will display a gridsome wordpress blog post and /impressum should show a normal page outside gridsome.
The event listener in the following file will handle normal  links as internal vue links and show a 404 page instead of making a normal page reload to the given address:
https://github.com/gridsome/gridsome/blob/a4e22d6e8f21be360a7e750dcfea27180910cbe4/gridsome/app/entry.client.js#L39-L78
As you already mentioned as a comment you wanna remove this code. Can you simply add a config option to disable that behavior in general? default value could still be to enable the feature.
Steps to reproduce
Add a <g-link to="http://my.domain/foo"> and a <a href="http://my.domain/bar">. Both will stay within gridsome.
Expected result
As in Vue a normal  should always redirect like the default behavior of anchors.
Actual result
Gridsome is listing on clicks and routing pages within the same domain.
Environment
System:
OS: macOS 10.15.2
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Binaries:
Node: 12.13.1 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.12.1 - /usr/local/bin/npm
Browsers:
Chrome: 79.0.3945.117
Firefox: 72.0.1
Safari: 13.0.4
npmPackages:
@gridsome/cli: ^0.3 => 0.3.1
@gridsome/source-wordpress: ^0.5 => 0.5.2
gridsome: ^0.7 => 0.7.12
gridsome-plugin-gtm: ^0.1.1 => 0.1.1

@cswebservice This ticket can probably be closed now since your PR was merged and released.
Should the config be added to the documentation, though? I'm not sure what needs to happen before
// TODO: remove this behavior
// let Vue router handle internal URLs for anchors in innerHTML

can be addressed. @hjvedvik?


correct some issues

Checks have not been completed yet

Checks have not been completed yet

Hey sir. Thanks for response,How much longer will it take?


jax.devices issue with the finetuning notebook

is the versioning correct in the yml?  JAX 4.26?
with the DEVICES = np.array(jax.devices()).reshape([1, 1, 1]) statement in the finetuning notebook I am getting the following error
ValueError: cannot reshape array of size 2 into shape (1,1,1)
The following....
        num_devices = jax.local_device_count()
        print(f'device kind: {jax.local_devices()[0].device_kind}')
        print(f'num_devices: {num_devices}')
        jax.devices()

returns this....
device kind: NVIDIA GeForce RTX 4080 SUPER
num_devices: 2
[cuda(id=0), cuda(id=1)]

i fixed this error by changing one those 1 to 2 like this:
 DEVICES = np.array(jax.devices()).reshape([1, 1, 2])
although a get another error in training loop block!


Embedding Base64 Image

Is embedding base64 images possible? If not, any plans on including this feature sometime in the future?
Any possible workaround of accomplishing this using Postal?

@TheFurryMonk I think below article help you.
https://kirandhappuri.wordpress.com/2015/09/13/sending-email-with-a-background-image-using-postal-asp-net-mvc/

Currently, embedding base64 images isn't directly supported in Postal. However, it's a feature that could be considered for future updates. As for workarounds, you might explore converting the Smd screen base64 images to regular image URLs and then embedding them in your emails.


sokect Bad file descriptor

when create socket using [asio::ip::tcp::socket(*(req.io_service)); ] ,but sokect send data return [Bad file descriptor]

refer to #398


Make syncChildren work with composed views.

The issues is that syncChildren isn’t getting applied at all because when you do a dynamic composition, you aren’t actually creating a custom element, just injecting the view/view-model into the compose element. The syncChildren implementation is only designed to work with custom elements and custom attributes.
Let's extend things a bit so that compose and router-view can send along a "host" element to use to attached the mutation observer to. This host will be the compose element or the router-view element itself. The caveat is that this will not work if someone chooses to leverage the upcoming containerless setting for the compose and router-view elements because then there will be no container node to attach and scope the dom mutation observation to.

We should also make sure that the host is set up in the child container so that view models that want access to their view can get the host injected.


pre-commit hook + ruff usage

ruff usage (setup to be equivalent to flake8 + isort + black), as per dagruner, improver_suite etc.

Performance improvements from its use.
Standardisation across repositories.

copyright and init checks also turned into pre-commit checks.

No longer any need improver_tests/test_source_code.py (removed in this PR).
__init__.py file checks handled via init_check script.  Auto-fix supported (creates missing __init__.py files).
Copyright check will add missing copyright headers.

pre-commit checking against changed files only in actions.
Updating ci.yml formatting while I was at it to increase readability (line spacing between steps).
CI workflow running the pre-commit (formally flake8 and black) now only look at files touched by the PR.

Note that you can run pre-commit manually (you needn't wait for a commit):
All files:
pre-commit run --all-files

Specific files:
pre-commit run --files <some-file> <some-other-file>

Issues

https://github.com/MetOffice/improver_suite/issues/2214

Why ruff?
This PR switches our use from black, isort, and flake8 to ruff for code formatting and linting. Ruff is gaining popularity due to its performance, efficiency and flexibility. It combines the functionality of black, isort, and flake8 into a single tool (and more if we enable additional rulesets), reducing the complexity of our tooling setup. Ruff offers excellent performance, faster execution times, and the ability to auto-fix issues, ensuring a consistent codebase. Adopting ruff aligns with industry trends and provides a unified approach to code quality with our other repositories.
Note
Some differences between black and ruff:
https://docs.astral.sh/ruff/formatter/#black-compatibility
(CI now only runs pre-commit on files changed so changes will be made to files as people touch them)

May be of interest to you @s-boardman - towards consistency between repositories.

@gavinevans - you happy for us to proceed with this?  I can chase-up a second review from the technical team.  I just wasn't sure whether science would be happy with leaving this as a purely technical team concern change.
cheers

I have updated the code style guide to provide more context.

There appears to be an issue with the copyright_check, it is failing when I don't think it should.

Can you give an example of this case that failed when you think it shouldn't have?

Can you add a fix option to copyright_check so users don't have to figure out what the correct header is?

The copyright check will already add a copyright header automatically if it is missing.  When it appears to be present but isn't correct, it's very difficult to automatically fix or present a diff in the general case.  Essentially, checking whether it 'appears' to have a copyright defined is achieved by searching for the term 'copyright' in a comment line.  Beyond that, comments can include arbitrary information so there is no sure way to know where this incorrect copyright finishes.

bin/improver_tests still contains references to old tools-black/isort/flake8 (is this used/ can it be removed? Or does it need updating)

I'll grep for references to flake8 and black 👍

This change appears to update the line-length from 100 down to 88 (not total clear to me why) - note, I am okay with it going to 88. Best guess for cause is the flake8 configuration in setup.cfg (which is still there and presumably could be removed?)

Good spotting, yes I didn't think to look at setup.cfg for the flake8 config.
I'll remove and update the ruff limit to 100 (for now at least).

There is a formatting change that I think are actually quite bad (for readability), can we do anything about this. Specifically spacing in explicit arrays, e.g.

Yes, I'm not sure.  Will look into it.  I think ideally this would be done with an in-line rule exclusion for such things.

Pulled back into draft to address some points raised by @SamGriffithsMO (thanks for taking a close look at this).

Can you give an example of this case that failed when you think it shouldn't have?

I just ran it on nbhood/nbhood.py, it already has a header that, to me, looks like it should pass. Let me know if you can't reproduce it
(improver_production) [sgriffit@vld456:/net/home/h03/sgriffit/repos/improver]$ git status
HEAD detached at origin/PRE_COMMIT
nothing to commit, working tree clean
(improver_production) [sgriffit@vld456:/net/home/h03/sgriffit/repos/improver]$ pre-commit run -v --files improver/nbhood/nbhood.py
ruff.....................................................................Failed
- hook id: ruff
- duration: 0.12s
- exit code: 1

improver/nbhood/nbhood.py:320:89: E501 Line too long (99 > 88)
improver/nbhood/nbhood.py:329:89: E501 Line too long (89 > 88)
improver/nbhood/nbhood.py:331:89: E501 Line too long (93 > 88)
improver/nbhood/nbhood.py:332:89: E501 Line too long (96 > 88)
improver/nbhood/nbhood.py:336:89: E501 Line too long (91 > 88)
improver/nbhood/nbhood.py:338:89: E501 Line too long (89 > 88)
improver/nbhood/nbhood.py:347:89: E501 Line too long (95 > 88)
improver/nbhood/nbhood.py:349:89: E501 Line too long (93 > 88)
improver/nbhood/nbhood.py:352:89: E501 Line too long (92 > 88)
improver/nbhood/nbhood.py:353:89: E501 Line too long (92 > 88)
improver/nbhood/nbhood.py:381:89: E501 Line too long (99 > 88)
improver/nbhood/nbhood.py:382:89: E501 Line too long (96 > 88)
improver/nbhood/nbhood.py:388:89: E501 Line too long (96 > 88)
improver/nbhood/nbhood.py:642:89: E501 Line too long (92 > 88)
Found 14 errors.

ruff-format..............................................................Failed
- hook id: ruff-format
- duration: 0.05s
- files were modified by this hook

1 file reformatted

Check copyright header...................................................Failed
- hook id: copyright_check
- duration: 0.11s
- exit code: 1

Incorrect Copyright header in 'improver/nbhood/nbhood.py'

Check for missing __init__.py files......................................Passed
- hook id: init_check
- duration: 0.02s

Since the improver_tests/test_source_code.py:test_py_licence that this copyright check replaces doesn't provide this diff, I'm going to consider it out of scope for this PR.

👍

@nivnac, you may be interested to look at this.
In summary, this is motivated by standardising formatting methods and testing across our repositories.  Also:

Smaller and Cleaner Production Environment.**: By removing developer tools like ruff from the package's core dependencies, the environment remains lightweight and free from unnecessary developer tools.

Easier Dependency Management: When developer-only dependencies are managed separately (e.g., using pre-commit), it becomes easier to maintain and update them without affecting the conda environment.  This reduces the risk of conflicts between package dependencies and development tools.

Improved Reproducibility: A clear separation between core and development dependencies ensures that production environments are consistent and reproducible. Development tools can introduce updates or changes that aren’t relevant to production, and by keeping them separate, you reduce potential variability across environments.

Flexibility for Developers: Pre-commit hooks allow each developer to manage their local development environment while keeping the project’s core environment isolated. For example, developers can update or modify their linting tools without altering the package dependencies.

By keeping developer dependencies separate, we can streamline both development and deployment processes, reducing complexity and ensuring a clear distinction between development tools and production requirements.
Note that IMPROVER uses a number of other developer packages and this is likely just the first step.

Will you remake the improver_production environment to exclude the now-redundant packages (black etc), or does the environment need to be left unchanged until post-PS46 to leave things genuinely unchanged?

Keep our existing environments unchanged 👍
Whilst there are now some redundant packages within, I don't think worth the time/effort/testing changing our pre-existing environments.

One tiny typo highlighted. I've not looked at every file, but I get the gist of it (thanks to Sam for being more rigorous). Happy with this change, thanks.

Done.  Thanks.

As an aside, I note that the copyright check is by far the slowest of the tests to run, so we might optimise that in future (not required here) to save ourselves whole seconds.

Whilst true that the copyright header check will be order of magnitudes slower than ruff, it will likely be faster than the pre-existing python copyright header checker that it was replacing.  Also, whilst checking the entire repository might take seconds, the pre-commit only runs against files that have change compared to master.  For this branch, I forcibly ran the pre-commit against on all files since we are changing the the formatting testing approach.  Under normal circumstances, a development branch will be changing tens of files at most (normally), so I think we are OK??

@nivnac, you may be interested to look at this.
...

@nivnac, you happy for us to merge this?


SLES 15 Missing development files for the GeoIP library

Hi,
GeoIP is installed in our SELS 15. But Goaccess does not know it. What should I do ?
zypper search geoip
S  | Name               | Summary                                                         | Type
---+--------------------+-----------------------------------------------------------------+--------
i+ | GeoIP              | Library to find the country that any IP address originates from | package
i+ | GeoIP-data         | GeoLite country data for GeoIP                                  | package
i+ | libGeoIP1          | Shared libraries of the GeoIP C API                             | package
./configure --enable-utf8  --with-getline  --enable-geoip=legacy
...
checking sha.h usability... no
checking sha.h presence... no
checking for sha.h... no
checking sha1.h usability... no
checking sha1.h presence... no
checking for sha1.h... no
checking for SHA1Init... no
checking for GeoIP_new in -lGeoIP... no
configure: error:
*** Missing development files for the GeoIP library

Since you are building from source, please try install libGeoIP-devel. Also, if you are building from the git repo (instead of the tar.gz file), please run again autoreconf -fiv.

Hi,
it is tar File form goaccess Website :
wget https://tar.goaccess.io/goaccess-1.5.6.tar.gz
tar -xzvf goaccess-1.5.6.tar.gz

As far as I know, there is no autoreconf in SLES 15 SP1.

Hi, @iranbingo
Maybe You can install autoconf package. the autoreconf tool is there.

Please try to install:
zypper install libGeoIP-devel

and then try running
./configure --enable-utf8 --with-getline --enable-geoip=legacy

Any updates?

Unfortunately, SLES 15 is not a desktop version and I am not allowed to configure a desktop repository on a server.
All necessary libgeoip is already installed in SLES 15 as a server. This means that the developer should deliver the right goacces for SLES.

Thanks for the update. Since you're trying to build a package from source, you will need the source libraries so that the package can be built. The libgeoip files you've got installed are binaries. Otherwise, like you said, you can always build without geoip.


BUG

Está havendo um bug, quando eu troco as coordenadas iniciais ele simplesmente não me deixa entrar no servidor, eu sei que o erro está nessa parte da coordenada porque eu testei duas vezes de forma diferente. O plugin é bom e de início eu fui na coordenada inicial do posto avançado e é possível dominar e ganhar poder.

Olá, tentei recriar o problema, mas sem sucesso. Mudei as coordenadas originais e o mundo e ainda consegui entrar. Talvez seja devido a conexões. Sem nenhum log de erros ou maneiras claras de reproduzi-lo, não posso fazer muito. Além disso, escreva para mim em inglês, estou usando um tradutor.
NO I DO NOT TALK PORTUGUESE ENGLISH ONLY

If it doesn't bother you, could you tell me how you did it? I changed the first coordinate of config.yml, this plugin is very good and I'm still testing it by restarting the server because the plugin is very.

No it doesn’t bother me, the disclaimer was for those who stumble across this. Can you possibly send me a video? There’s an issue with my server as well and I can’t join instantly I need to keep trying to connect and disconnect. Sometime even relaunching Minecraft.
The ways I fixed it was if the screen takes too long to load I simply restart Minecraft and try again and after the 3rd attempt I can join.

After you disconnect look through the console logs for any crash messages.

This is a problem because the console does not show any crash messages.

I somewhat managed to reproduce it. It’s due to the coordinates being in an unloaded chunk. I’ll fix it soon.

I reported the problem because the plugin is great for complementing and improving PiggyFactions so it wouldn't be worth it for me to simply delete the plugin from the server. Congratulations

Can you see if this fixed the issue? @Rafael173
Download: https://poggit.pmmp.io/r/235262/PiggyOutpost_dev-17.phar

The problem has been resolved, this is incredible because now players can claim the planet Earth map and gain power by dominating outposts. Thanks. 👏👏👏


it would be great being able to move the terminal position

having the terminal fixed at the bottom is great on larger screens, but on my macbook it takes up way too much vertical space. it would be an amazing feature being able to fix the terminal to the right of screen. just a thought! thanks for the great plugin - i use it all the time!

Was going to open an issue with the same comment. I'd love to be able to split terminals, or even to have it live in the file tree sidebar as an option.

Vertical docking option +1

I believe this is the same request as #129. Might be best to consolidate the two.


Allow the zip compute function to operator on Scalar values via Datum

Which issue does this PR close?
Closes #5011.
Rationale for this change
The arrow compute kernel function zip can now work on scalars, allowing a scalar value to be "zipped" with another array, repeating the scalar where needed to fill in the selected spots:

BeforeAfter

pub fn zip(
    mask: &BooleanArray,
    truthy: &dyn Array,
    falsy: &dyn Array,
) -> Result { ... }

pub fn zip(
    mask: &BooleanArray,
    truthy: impl Datum,
    falsy: impl Datum,
) -> Result { ... }

If a Scalar value is provided, then it will be copied to fill every spot specified in the mask. Previously, callers would be required to implement this logic internally to support this.
Since &dyn Array already implements Datum, existing calls will still continue to work exactly as they did before, but it is now also possible to pass in a scalar value.
In addition, &dyn Datum now implements Datum. This means that zip can be called with the same signature as e.g. add, which explicitly ask for &dyn Datum; otherwise, it would not be possible to call zip with the same kind of signature as add.
(I think in a future PR, it would be a good idea to change add, sub, and all of the other computing kernels to take impl Datum parameters instead of &dyn Datum parameters for maximum flexibility and efficiency)
What changes are included in this PR?

zip's signature changes from &dyn Array to impl Datum
&dyn Datum now implements Datum

Are there any user-facing changes?

zip now supports Scalar/Datum arguments
&dyn Datum now implements Datum

I took a quick look and this looks good thank you, I would ask that we rollback the Datum changes though - there is a reason we don't do this 😅


Upgrade to electron7. Closes #73.

this builds well? no breaking API changes that affect us?

As far as I could tell no. The tests run fine and opening the app and using it is same as usually

doesn't look like any breaking changes should affect this app. let's do it.


Broken network after the resumption of Apple APNs development documents do not receive the last message?

With Pushy's friends:
I now use two frames (http / apns4j) and (http2 / pushy). When the phone off the network, I use apns4j to send this phone to push, after a period of time I manually restore the phone to this network can accept the last push. But I use pushy to do the same operation and so my mobile phone recovery network is not received push, provided that I have been informed in the listener to push the APNs server success.
Do you have any friends who have met? Or my Pushy framework is useless where the lack of configuration?

Have you set invalidationTime in ApnsNotification's construct method?

@binauyang:
No settings, I'm the default operator！
pingyin:wo mei you she zhi,yong de shi mo ren cao zuo!zhei li zen me she zhi?

@binauyang:
Thank you for your warning. It has been successful!


[Bug] Mouse event cause content scroll to top after switching editable to false

Describe the bug
Mouse event cause content scroll to top after switching editable to false.
To Reproduce

Create editor like

Editor.make()
    .config((ctx) => {
        ctx.update(editorViewOptionsCtx, (prev) => ({ ...prev, editable: getEditable }));
    })
    .use(nord).use(commonmark).create()

Set editable to false like

editable = false;
editor.action((ctx) => {
    const view = ctx.get(editorViewCtx);
    view.update(view.props);
});

Scroll down.
Click content.
Auto scroll to top.

Expected behavior
Content should not be scrolled.
Milkdown version
    "@milkdown/core": "^6.3.0",
    "@milkdown/preset-commonmark": "^6.3.0",
    "@milkdown/theme-nord": "^6.3.0",

Desktop (please complete the following information):

OS: Windows10
Browser Chrome
Version 101.0.4951.67

Additional context
I found it is caused by updating menu plugin which call editorRoot.appendChild(milkdownDOM);.

I need to rollback this change, because this change breaks two things:

The global menuWrapper breaks the behavior of multiple editor instances (because they're forced to share one wrapper).
In readonly mode, the expect behavior is that the menu wrapper dom should not be exists.

I think to keep the scroll top, you may need to record the scroll offset before switching editable, and restore it after the switch finish.

All right.
I think the first break things can be fixed. But the second one is hard to deal. I think that a common wrapper is better for plugin, but not menu wapper.


Convert App42PaaS to a microservice

Convert App42PaaS project into a service-oriented solution
There are two services; user-data-manager and account-manager. account-manager provides a UI and allows creating accounts. During the account-creation, user data is written to a message queue which is listened by user-data-manager. account-manager also allows listing accounts which results a call to user-data-manager to fetch the user data.
 Create a user
curl -H "Content-Type: application/json" -X POST --data '{"name": "abc", "email"<EMAIL_ADDRESS>"description": "some description"}' localhost:8082/users -i

HTTP/1.1 201
Location: /users/6
Content-Length: 0

2. Get a user
curl localhost: 8082/users/6

{"name":"abc","email":"test@abc.com","description":"some description"}

3. Update a user
curl -H "Content-Type: application/json" -X PATCH --data '{"name": "abc", "email"<EMAIL_ADDRESS>"description": "some description"}' localhost: 8082/users/6 -i

HTTP/1.1 204
Location: /users/6

4. Delete a user
curl -X DELETE localhost: 8082/users/6

5. Check application status
curl  localhost: 8082/health

{"status":"UP"}

Microservice 2: account-manager
Running locally
mvn clean install docker:build
docker run -p8080:8080 amertkara/account-manager

Could we get at least one other "service" (like having a front end to this would be nice), and the orchestration of those 2 together ? (choosing an orchestrator and a deploy method...?)

@bruno-morel added another service which provides a user interface. Also dockerized the whole solution so you can boot up via docker-compose. In terms of orchestration, I used a message queue for the user create event.

Thanks Mert ! :)


There's no good way to see what's going on

The only way to currently see what's happening is to manually newState(), and look at memory, entities[i].mem,x,y,facing,ghost,dying.

Eh, I've decided to leave output as the only ui, because making a gui really doesn't sound like fun


After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc.

Started getting multiple errors, such as this after upgrading from 2.1.4 to 2.2.0-preview3-35497:
Field 'Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor+TransparentIdentifier2[DAL.Model.TblBusinessRule,System.Collections.Generic.IEnumerable1[DAL.Model.TblField]].Inner' is not defined for type 'Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor+TransparentIdentifier`2[DAL.Model.TblBusinessRule,DAL.Model.TblField]'
This code has been working with EF Core 2.0.2 and 2.1.4, first time getting these...
Further technical details
EF Core version: (2.2.0-preview3-35497
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win 7
IDE: (e.g. Visual Studio 2017 15.8.6)

@tannenbaums Have you updated all packages to consistent 2.2 versions? If so and you still see errors, then please post a runnable project/solution or complete code listing that demonstrates the behavior you are seeing so that we can fully investigate.

So sorry, false alarm. I had a local issue where I changed a db field from required to optional but my model still had IsRequired(). I guess the previous versions of ef where more forgiving :) we are all good. Thank you for all your help!

Hi,
Thank you so much for your response. I closed the issue below. But I do have a new question: The reason I upgraded to 2.2.0-preview3-35497
is because of a promised bug fix for bug #12482, but it seems to still be broken. I still get the same exact error, and I can see the SQL being generated looks exactly the same:
Conversion failed when converting the nvarchar value '2018-10-19' to data type bit.
exec sp_executesql N'SET NOCOUNT ON;
DECLARE @inserted0 TABLE ([Id] int, [_Position] [int]);
MERGE [tblFieldValue] USING (
VALUES (@p0, @p1, @p2, 0),
(@p3, @p4, @p5, 1),
(@p6, @p7, @p8, 2),
(@p9, @p10, @p11, 3),
(@p12, @p13, @p14, 4),
(@p15, @p16, @p17, 5)) AS i ([EntityId], [FieldId], [Value], _Position) ON 1=0
WHEN NOT MATCHED THEN
INSERT ([EntityId], [FieldId], [Value])
VALUES (i.[EntityId], i.[FieldId], i.[Value])
OUTPUT INSERTED.[Id], i._Position
INTO @inserted0;
SELECT [t].[Id] FROM [tblFieldValue] t
INNER JOIN @inserted0 i ON ([t].[Id] = [i].[Id])
ORDER BY [i].[_Position];
',N'@p0 int,@p1 int,@p2 bit,@p3 int,@p4 int,@p5 bit,@p6 int,@p7 int,@p8 nvarchar(10),@p9 int,@p10 int,@p11 nvarchar(4000),@p12 int,@p13 int,@p14 nvarchar(4000),@p15 int,@p16 int,@p17 nvarchar(4000)',@p0=36,@p1=9,@p2=1,@p3=36,@p4=10,@p5=1,@p6=36,@p7=11,@p8=N'2018-10-19',@p9=36,@p10=12,@p11=NULL,@p12=36,@p13=13,@p14=NULL,@p15=36,@p16=14,@p17=NULL
Thank you so much,
[Logo2]
Daniel Tannenbaum
1776 Avenue of the States, Suite 103
Lakewood, New Jersey 08701
Phone:<PHONE_NUMBER> ext:260
From: Arthur Vickers<EMAIL_ADDRESS>Sent: Monday, October 29, 2018 4:31 PM
To: aspnet/EntityFrameworkCore<EMAIL_ADDRESS>Cc: Shmuel Tannenbaum<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/EntityFrameworkCore] After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc. (#13800)
@tannenbaumshttps://github.com/tannenbaums Have you updated all packages to consistent 2.2 versions? If so and you still see errors, then please post a runnable project/solution or complete code listing that demonstrates the behavior you are seeing so that we can fully investigate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/EntityFrameworkCore/issues/13800#issuecomment-434067797, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlFmJWejVIwGzEgefZLhFRnHlw7AZHNOks5up2WggaJpZM4X_2QZ.

@tannenbaums #12382 has not been fixed for 2.2. This is why the issue is still "Open" and the milestone is set to "3.0".

Oh sorry about that, my bad! Appreciate your help!!
From: Arthur Vickers<EMAIL_ADDRESS>Sent: Tuesday, October 30, 2018 11:36 AM
To: aspnet/EntityFrameworkCore<EMAIL_ADDRESS>Cc: Shmuel Tannenbaum<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/EntityFrameworkCore] After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc. (#13800)
@tannenbaumshttps://github.com/tannenbaums #12382https://github.com/aspnet/EntityFrameworkCore/issues/12382 has not been fixed for 2.2. This is why the issue is still "Open" and the milestone is set to "3.0".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/EntityFrameworkCore/issues/13800#issuecomment-434348512, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlFmJTojehFDWTwsAeL_kU25WU2JLoNiks5uqHHsgaJpZM4X_2QZ.

Can I ask you though:
What’s the best way to tell what bugs are fixed in just the given version? If I filter by: label:closed-fixed, I believe I get all bug fixes from all the versions…
Thank you,
Daniel Tannenbaum
From: Arthur Vickers<EMAIL_ADDRESS>Sent: Tuesday, October 30, 2018 11:36 AM
To: aspnet/EntityFrameworkCore<EMAIL_ADDRESS>Cc: Shmuel Tannenbaum<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/EntityFrameworkCore] After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc. (#13800)
@tannenbaumshttps://github.com/tannenbaums #12382https://github.com/aspnet/EntityFrameworkCore/issues/12382 has not been fixed for 2.2. This is why the issue is still "Open" and the milestone is set to "3.0".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/EntityFrameworkCore/issues/13800#issuecomment-434348512, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlFmJTojehFDWTwsAeL_kU25WU2JLoNiks5uqHHsgaJpZM4X_2QZ.

@tannenbaums Go to https://github.com/aspnet/EntityFrameworkCore/milestones and then choose a milestone (you can choose an open or closed one) and click on the link for closed issues.

I see and thank you for that.
One thing I’m still not sure I understand, within milestones you have specific preview versions, how do I know which bug fixes made it to the last preview?
Thank You,
Daniel Tannenbaum
From: Arthur Vickers<EMAIL_ADDRESS>Sent: Tuesday, October 30, 2018 12:41 PM
To: aspnet/EntityFrameworkCore<EMAIL_ADDRESS>Cc: Shmuel Tannenbaum<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/EntityFrameworkCore] After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc. (#13800)
@tannenbaumshttps://github.com/tannenbaums Go to https://github.com/aspnet/EntityFrameworkCore/milestones and then choose a milestone (you can choose an open or closed one) and click on the link for closed issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/EntityFrameworkCore/issues/13800#issuecomment-434375358, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlFmJfL8Yy8ZAXOAKoaK1WO6jzMjWJZRks5uqIESgaJpZM4X_2QZ.

@tannenbaums The 2.2 preview 3 milestone contains everything fixed in the preview 3 release that was not already fixed before that. The 2.2.0 milestone contains everything fixed after preview 3 that will be contained in the 2.2.0 RTM release.

Oh I see.
So if I understand correctly there should be a Milestone called: The 2.2 preview 3 milestone. Is there any way for me to see it? It’s not showing up on the Milestones list…
<EMAIL_ADDRESS>Thank you,
Daniel Tannenbaum
From: Arthur Vickers<EMAIL_ADDRESS>Sent: Tuesday, October 30, 2018 1:06 PM
To: aspnet/EntityFrameworkCore<EMAIL_ADDRESS>Cc: Shmuel Tannenbaum<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [aspnet/EntityFrameworkCore] After upgrading to 2.2.0-preview3-35497 getting new errors Type.Inner not defined etc. (#13800)
@tannenbaumshttps://github.com/tannenbaums The 2.2 preview 3 milestone contains everything fixed in the preview 3 release that was not already fixed before that. The 2.2.0 milestone contains everything fixed after preview 3 that will be contained in the 2.2.0 RTM release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/aspnet/EntityFrameworkCore/issues/13800#issuecomment-434385018, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlFmJQuB9OmFF1dkY156tGoVhHlvHdaGks5uqIbhgaJpZM4X_2QZ.


Unexpectedly recognizing epi and pie as pi and e

Expression
Unexpected Result

ceval_result("pie")
2.718282

ceval_result("epi")
3.141593

ceval_result("pieepi")
3.141593

ceval_result("epipie")
2.718282

The parsing of of the math constant tokens pi and e needs to be handled in a manner which doesn't lead to this unexpected behaviour.

Fixed : https://github.com/erstan/ceval/commit/8728f27e68285c56ad35a011607dde1b6709115f


Create a template for status updates

For this new feature being added to the RCOS curriculum, a template will be helpful for students to structure their status updates.

Resolved by #2


Template for Changelog Added

Added the template for Changelog

Let's wait for Thomas' PR on automatic the semantic python release


missing "*" in table in Update xpp-syntax.md

Missing * in table
Current

:white_check_mark: Organization membership check passed
Requester is not a member of the MicrosoftDocs organization.


⚠ Secret Website 3 has degraded performance

In 2921e96, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 4962 ms

Resolved: Secret Website 3 performance has improved in 956ab9a.


pod install changing source to master Specs repo when upgrading CocoaPods to 1.7.5

I have been using CocoaPods successfully with Artifactory for over a year with CocoaPods 1.5.3.
Today I updated to 1.7.5 and did a $ pod install, and I started getting this:
rwalberg@Ryans-MacBook-Pro:iOS (pod-bump-2019-aug)$ bundle exec pod install
/Users/rwalberg/.cocoapods/repos-art/cocoapods-remote/.artpodrc
Analyzing dependencies
/Users/rwalberg/.cocoapods/repos-art/cocoapods-remote/.artpodrc
/Users/rwalberg/.cocoapods/repos-art/cocoapods-remote/.artpodrc
Downloading dependencies
Installing ALAlertBanner 0.3.1 (source changed to `https://github.com/CocoaPods/Specs.git` from `https://pagerduty.jfrog.io/pagerduty/api/pods/cocoapods-remote`)
^C[!] Cancelled

This isn't right, since the Podfile.lock says they come from Artifactory.
Nothing has changed in my Podfile. It still says this:
plugin 'cocoapods-art', :sources => [
  'cocoapods-remote'
]

Is CocoaPods 1.7.5 not supported by the cocoapods-art gem?

@rwalbergpd
I think I had the same issue. For me, all of the downloads which referenced the master repo broke after adding the cocoapods-art plugin.
I fixed this by adding the following line after the plugin 'cocoapods-art' definition
source 'https://github.com/CocoaPods/Specs.git'

Thanks @henribeck but that’s a different problem. None of my pods are supposed to reference the master repo, and after I do a pod install, they all do.

Hola @rwalbergpd me pasaba lo mismo y lo solucioné actualizando la versión de Cocoapods y Cocoapods-art
cocoapods -> 1.8.3
cocoapods-art -> 1.0.4

Hi @rwalbergpd , were you able to resolve this issue? I am also getting similar output and podfile.lock has diffs.
Using cocoapods-art-1.0.2.gem with cocoapods-1.9.1

@ashokds I am using cocoapods-art-1.0.4 with cocoapods-1.8.4 and it's working.


[feat] Implement OP_NOT opcode

Implement the OP_NOT opcode using the opcodeNot reference implementation from btcd
References
Guide on how to add an opcode in shinigami

@b-j-roberts kindly assign this issue to me
Thank you .

Glad to have you on this project @mubarak23 !


NullConstraintViolation

I have the following models (simplified for reporting the issue):
model User {
  id         String        @default(cuid()) @id @unique
  email      String        @unique
  staff      Staff?
}

model Staff {
  id        String   @default(cuid()) @id @unique
  user      User
  active    Boolean?
}

When trying to add a user with the following query
mutation {
  createOneUser (data: {
    email<EMAIL_ADDRESS>  }) {
    id
    email
  }
}

I get the following error
"error": "ConnectorError(NullConstraintViolation { field_name: \"User.staff\" })"

This seems odd, since the staff field in the User model is optional. I have other 1-1 relations with the same problem.

I can no longer reproduce any of these conditions now with<EMAIL_ADDRESS>binary version: 29f6d9f7f6d0a85cc30df1809733612bab56a1c5
These have been fixed between the updates


[5.8] Fix event:list command

When using a combination of manually registering events in the EventServiceProvider and event auto discovery, the output of php artisan event:list can be unexpected.
Example
If I have two listeners in the app/Listeners directory for the VoteWasCast event (e.g. StoreVote and SendVote), but I only have one of those manually registered in the EventServiceProvider as below, I would still expect both to be included in the output of php artisan event:list.
class EventServiceProvider extends ServiceProvider
{
    protected $listen = [
        VoteWasCast::class => [
            StoreVote::class,
        ]
    ];
}

However, below is the output I get:

This PR provides the following output which is in line with what I would expect.

Isn't it weird that the StoreVote class is now listed twice?

Well, I think it’s probably expected behaviour.  I assume it’s the developers responsibility not to list it there and use auto discovery?
M

@joedixon ah, if it's fired twice than that definitely makes sense. I can follow that reasoning 👍


Having trouble using my custom telephone-line mods with straight.el - help? :)

First - I'm just starting to use straight.el and it looks awesome.  Thank you very much for making this & sharing it!
My issue, tl;dr:
I'm not sure how to debug a problem and would love advice/help.  I'm asking here because if I use straight.el the problem occurs, but if I re-evaluate the problematic macro definition after loading straight.el then the problem does not occur, nor did it occur when I used package.el
My issue, in detail:
I've been using telephone-line and enjoying it.  When I installed it using package.el I can get everything to work fine, including some custom code I wrote to define a new chunk of my mode line:
  (telephone-line-defsegment my-buffer-name-segment
    (telephone-line-raw mode-line-buffer-identification t)
    )

After switching to straight.el I get the following error when I try to evaluate the above form
error "Malformed arglist: (lambda (face) mode-line-buffer-identification)")
  signal(error ("Malformed arglist: (lambda (face) mode-line-buffer-identification)"))
  error("Malformed arglist: %s" (lambda (face) mode-line-buffer-identification))
  #f(compiled-function (name arglist &optional docstring decl &rest body) "Define NAME as a function.\nThe definition is (lambda ARGLIST [DOCSTRING] BODY...).\nSee also the function `interactive'.\nDECL is a declaration, optional, of the form (declare DECLS...) where\nDECLS is a list of elements of the form (PROP . VALUES).  These are\ninterpreted according to `defun-declarations-alist'.\nThe return value is undefined." #<bytecode 0x100082173>)(my-buffer-name-segment (lambda (face) mode-line-buffer-identification))
  macroexpand((telephone-line-defsegment* my-buffer-name-segment mode-line-buffer-identification) nil)
  macroexp-macroexpand((telephone-line-defsegment* my-buffer-name-segment mode-line-buffer-identification) nil)
  macroexp--expand-all((telephone-line-defsegment* my-buffer-name-segment mode-line-buffer-identification))
  macroexpand-all((telephone-line-defsegment* my-buffer-name-segment mode-line-buffer-identification))
  eval-sexp-add-defvars((telephone-line-defsegment* my-buffer-name-segment mode-line-buffer-identification))
  elisp--eval-last-sexp(nil)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

Turns out telephone-line-defsegment is actually a macro.
What's weird is that if I re-evaluate the telephone-line-defsegment macro definition manually I can then go back and evaluate the my-buffer-name-segment just fine.
Because of this, I'm wondering if straight.el does anything that might impact macro definitions in the packages it loads?
Also, while I don't expect or want anyone to do this for me, would anyone have any pointers on how to go about debugging a problem like this?  Any help / advice / etc would be greatly appreciated! :)

I get that error with your code regardless of whether I'm using package.el or straight.el. Did you forget to update the package.el version?

First, thanks for the response!
I think I've got it figured out and it's definitely an issue on my end (as I expected)
straight.el is using a newer version, and that newer version's telephone-line-defsegment macro now needs a parameter list.  So instead of the older format that the package.el version expects:
  (telephone-line-defsegment my-buffer-name-segment

it now needs to be
  (telephone-line-defsegment my-buffer-name-segment ()

Part of my confusion came from using find-library.  I expected it to bring me to the file that's currently in use, but that appeared to bring me to the version that was stored in my ~/.emacs.d/elpa copy of telephone-line, even though I was actually using the one in ~/.emacs.d/straight/build
Is it a 'best practice' to remove any packages that were installed via package.el?
(Please do close this issue whenever you'd like)

Er, just to clarify - I read quite clearly in your README file that straight.el & package.el don't play well together.  As someone who's new-ish to emacs I assumed that removing all the package.el related stuff (such as (package-initialize)) would 'turn off' package.el while still leaving all of it's packages on disk, untouched.
The overall goal was to try out straight.el, and if it didn't work for me to then go back to package.el.

By default, Emacs runs package-initialize at the end of your init-file, unless you already ran it yourself, which loads all packages currently installed by package.el. This behavior is clearly undesirable if you are not using package.el, and you can suppress it by setting the variable package-enable-at-startup to nil. However, straight.el does this automatically as soon as you run the bootstrap snippet, so it's unclear to me how your package.el packages are getting activated. I am not sure what sequence of events could cause the behavior that you describe, although I certainly have experienced M-x find-library being misleading when there are duplicate entries on the `load-path.
(Are you perhaps building Emacs 27 yourself? That would explain everything, and I can elaborate on why if that's the case.)
In conclusion, you shouldn't need to remove package.el packages from disk in order for straight.el to operate correctly, but apparently something went wrong in your case.


add a CocoaPods podspec generator

Motivation:
Users ask for a CocoaPod. Unfortunately, the CocodPod SwiftLog is
already taken, so I went for SwiftLogAPI.
Modification:
Add a podspec generator.
Result:

Happier users.
fixes #19

Example output:
Pod::Spec.new do |s|
  s.name = 'SwiftLogAPI'
  s.version = '1.0.0'
  s.license = { :type => 'Apache 2.0', :file => 'LICENSE.txt' }
  s.summary = 'A Logging API for Swift.'
  s.homepage = 'https://github.com/apple/swift-log'
  s.author = 'Apple Inc.'
  s.source = { :git => 'https://github.com/apple/swift-log.git', :tag => s.version.to_s }
  s.documentation_url = 'https://github.com/apple/swift-log'
  s.module_name = 'Logging'

  s.swift_version = '5.0'
  s.cocoapods_version = '>=1.6.0'
  s.ios.deployment_target = '12.0'
  s.osx.deployment_target = '10.14'
  s.tvos.deployment_target = '12.0'

  s.source_files = 'Sources/Logging/**/*.swift'
end

Please see below my feedback:

I don't see watchOS as a deployment target. Is it supported? I don't think that there're limitations to support watchOS.
What about name 'AppleSwiftLog' or 'swift-log' instead of 'SwiftLogAPI'?

Please see below my feedback:

I don't see watchOS as a deployment target. Is it supported? I don't think that there're limitations to support watchOS.

Oh thanks! Would you mind checking if it works? I have no idea how to build a Watch app :)

What about name 'AppleSwiftLog' or 'swift-log' instead of 'SwiftLogAPI'?

Could do that, or maybe SSWGSwiftLog. @tomerd / @ktoso / @ianpartridge / @tanner0101

SwiftLogAPI seems fine to me - it makes it clear that this is an API package, not a backend.

A bit unfortunate with the module name already occupied hm... SwiftLogAPI sounds fine though.
Would we care to have all API packages in both systems adopt same naming style for this?

@tanner0101 you also fine with pod name SwiftLogAPI?

Why is the iOS/tvOS deployment target 12 and macOS 10.14? Are there any unavailable APIs in use? (I'm currently using all this source deploying to iOS 11)

Why is the iOS/tvOS deployment target 12 and macOS 10.14? Are there any unavailable APIs in use? (I'm currently using all this source deploying to iOS 11)

Very happy to relax the version here if you tell me what the lowest version is that you could confirm actually working.

@weissi I'll report back shortly

@weissi Here is a git repo that has a rather large set of Apple targets. It uses a local version of the podspec with the following deployment targets:
s.ios.deployment_target = '8.0'
s.osx.deployment_target = '10.9'
s.tvos.deployment_target = '9.0'
s.watchos.deployment_target = '2.0'

iOS, tvOS, and watchOS are informed by Xcode 10.2's minimums that the GUI allows. macOS is 10.9 because Swift isn't supported with a lower deployment target.
I did not actually test on the old platforms running these versions as that could be a rather complicated endeavor. The key thing is that it compiles correctly with these deployment targets. If users actually have issues with running on those older platform versions, that'll be the most informative to any other changes I'd think.
I did verify functionality on all the latest simulators as well as my mac @ 10.14.

Also wanted to mention there was a lot of conversation about the Pod name being SwiftLogAPI, but the actual module name in code is still Logging which means import Logging in actual source code which aligns with SPM integration method. 👍

@weissi Here is a git repo that has a rather large set of Apple targets. It uses a local version of the podspec with the following deployment targets:

Thank you so much! I updated this PR, please check :).

Also wanted to mention there was a lot of conversation about the Pod name being SwiftLogAPI, but the actual module name in code is still Logging which means import Logging in actual source code which aligns with SPM integration method. 👍

I mean we can also name the pod Logging if that's what you're suggesting, that name is still available. @tomerd / @ianpartridge / @ktoso / @tanner0101 ?

A bit hard for me to comment on package naming -- don't know that ecosystem very well... whichever you think works best 👍

In the pods ecosystem, having module names match the pod names is pretty common if it's possible. It actually took me a few minutes to realize I shouldn't be doing import SwiftLogAPI.

@weissi I believe it is better to use Logging as package name. It will lock the name to prevent other lib use this general name. Sorry for the late comment.

Thanks @shuoli84 . @tomerd / @ianpartridge okay with making the CocoaPod just Logging then?

Fine by me. Really hope we don't have to do CocoaPods for very long!

@ianpartridge thanks, I updated the PR to use Logging. If @tomerd is happy with this I think I'll pull the trigger and upload it.

no strong feeling here, but is it worth reaching out to the owner of SwiftLog pod and see if he is will wot work with us?

@daltoniam ^^

@tomerd the SwiftLog pod has already a published version 1.0 so I'm not sure if we should use that (even if we could). What do you propose to go forward here? pod name Logging?

What do you propose to go forward here? pod name Logging?

yes, lets do that


OPS-6042: Disable rule that makes log dir unreadable

Why is it soo hard to do a PR with this repo.
The rule removes read access from everyone but root. This breaks at least td-agent which tries to create it's log dir on start up but can't even find it and gets and error trying to create it because it thinks it's not there.

IMO We should set these vars on the role in our ansible playbooks, not override the defaults.

IMO We should set these vars on the role in our ansible playbooks, not override the defaults.

I totally agree with you


chore: ensure canonical links don't point to Hosted version for Serve…

…r Installation pages
Ticket: MEN-5877
Changelog: None
External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

[ ] Make sure that all commits follow the conventional commit specification for the Mender project.

The majority of our contributions are fixes, which means your commit should have
the form below:
fix: <SHORT DESCRIPTION OF FIX>

<OPTIONAL LONGER DESCRIPTION>

Changelog: <USER-FRIENDLY-CHANGE-DESCRIPTION> or <None>
Ticket: <TICKET NUMBER> or <None>

[ ] Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description
Please describe your pull request.
Thank you!

Cherry pick to 3.3.x also

@michaelatmender This needs to be ported to master with an AUTOVERSION tag so that we can automatically update the versions when we branch out future releases (so no need to an extra release checklist item, Manuel).
I can take care of it. But please answer me the following:

How should it work on master (aka development docs)? Should it be like canonical: /development/server-installation/overview ?
How should it work on hosted (aka default docs)? Just removing these lines?

Thanks @lluiscampos!

It should be as you described on master, but I didn't include it because development docs should not be indexed by search engines - so I added only on the latest 2 versions. If we change master too then it should be how you wrote it!
Exactly :)

@mender-test-bot cherry-pick to:

3.3.x


Fix demo link in the readme

Demo link was 404ing. This now tracks master with the correct account.

Ah, the README was updated with 0.3 info after I did this :) Closing.


[FLINK-35216] Support for RETURNING clause of JSON_QUERY

What is the purpose of the change
This PR adds support for RETURNING clause in JSON_QUERY function.
Verifying this change
Added tests in JsonFunctionsITCase
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Also for EMPTY OBJECT

That's expected. I can also adjust the type inference logic to fail earlier.

I believe this falls into ON EMPTY category and the default is NULL. If you use lax strategy the checks are less strict and there is no error, but no results. I am not an expert on the JSON expressions though.
That's why when you use:
 SELECT JSON_QUERY('{"a":[{"c":Null},{"c":"c2"}]}', 'lax $.a[*].c' RETURNING ARRAY<STRING> ERROR ON ERROR NULL ON EMPTY); // explicitly specified the other parameter using the default value

you get null
if you run:
 SELECT JSON_QUERY('{"a":[{"c":Null},{"c":"c2"}]}', 'lax $.a[*].c' RETURNING ARRAY<STRING> ERROR ON ERROR ERROR ON EMPTY);

you get an error:
Caused by: org.apache.flink.table.api.TableRuntimeException: Empty result of JSON_QUERY function is not allowed

Bear in mind that I have not changed anything in the json extraction logic. If you think the JSON expressions don't work the way you'd like let's fire a different ticket.


jax: init at 0.2.19

Motivation for this change
An attempt at packaging the JAX (https://github.com/google/jax) library. Contributions are very welcome! I'm currently stuck, putting this out into the ether.
TODO:

[ ] Fix jnp.array([1, 2, 3]). At the moment it segfaults.
[ ] Run the jax test suite. Currently failing with segfaults.
[ ] (Not necessary for an initial PR) Support GPU and TPU versions of jaxlib.

I'm guessing that the current segfaults have something to do with the packaging of jaxlib. It may need to be patched somehow. It's not presently clear to me what's wrong exactly though.
Useful resources:

https://jax.readthedocs.io/en/latest/developer.html#running-the-tests
https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/python.section.md

Things done
Created derivations for the jax and jaxlib python packages.

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

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/help-packaging-jax/14613/1

On my (outdated) linux machine I'm getting:
>>> import jax
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/nix/store/994kvxz1n7qch3zn8gfxi9wdd7nkzlm7-python3.9-jax-0.2.19/lib/python3.9/site-packages/jax/__init__.py", line 37, in <module>
    from . import config as _config_module
  File "/nix/store/994kvxz1n7qch3zn8gfxi9wdd7nkzlm7-python3.9-jax-0.2.19/lib/python3.9/site-packages/jax/config.py", line 18, in <module>
    from jax._src.config import config
  File "/nix/store/994kvxz1n7qch3zn8gfxi9wdd7nkzlm7-python3.9-jax-0.2.19/lib/python3.9/site-packages/jax/_src/config.py", line 27, in <module>
    from jax import lib
  File "/nix/store/994kvxz1n7qch3zn8gfxi9wdd7nkzlm7-python3.9-jax-0.2.19/lib/python3.9/site-packages/jax/lib/__init__.py", line 71, in <module>
    cpu_feature_guard.check_cpu_features()
RuntimeError: This version of jaxlib was built using AVX instructions, which your CPU and/or operating system do not support. You may be able work around this issue by building jaxlib from source.

So it may be worth considering building jaxlib from source but honestly that also sounds like a PITA.

Attempted to use autoPatchelfHook in the building of jaxlib in https://github.com/NixOS/nixpkgs/pull/134894/commits/59d6dd27b05d5376c450b37f797413067100ad90. Not sure that it's working however: https://discourse.nixos.org/t/autopatchelfhook-not-patching-all-dependencies/14634/2.
@SuperSandro2000 Thanks for reviewing! I'll start incorporating your suggestions once I can get it to build and pass tests!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/582

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/584

Result of nixpkgs-review pr 134894 run on x86_64-linux 1

2 packages built:

python39Packages.jax
python39Packages.jaxlib


Add support for Opencensus z-pages for in-memory tracing

#4509
This PR replaces opentracing tracing spans with opencensus tracing spans.
As discussed in #4509 , this PR adds an in-memory backend in Prometheus, in the form of opencensus z-pages.
A running Prometheus server can be found at http://<IP_ADDRESS>/graph.
It's zpages can be found at http://<IP_ADDRESS>/trace/tracez.
To see traces of alerting-rules (span-name:rule), an alerting-rule is also added http://<IP_ADDRESS>/alerts.
The load on Prometheus is the one used by prombench
(targets toggle between 257 to 5007 every 15 minutes & all these queries are queried).
Benchmarking graphs can be found here
govendor details

Opentracing packages are removed
Opencensus is compatible with grpc-v1.6.0. Prometheus used grpc-v1.5.0
Opencensus is compatible with grpc/metadata-v1.10.0

/cc @brian-brazil @gouthamve @tomwilkie @brancz

I have opened an issue https://github.com/census-instrumentation/opencensus-go/issues/893
in opencensus about the promu crossbuild -v error in ci/circleci:build

http://<IP_ADDRESS>/trace/tracez?zspanname=GET %2Ftrace%2Fpublic%2Fopencensus.css&ztype=2&zsubtype=0
Seems like /trace/public/opencensus.css not found.

I doubt it.
The sample page given here is similar to the one deployed.

:-1:
We're pretty dependant on the existing opentracing instrumentation.  If there are way we can have an adapter from one to the other?

I've spoken @sipian offline, and the zpages don't provide us the trace, just the traceid. We'll still need to have a backend to view it. With that, I wonder if opencensus is worth the switch.
I think he's currently investigating building an in-mem backend. If the effort is the same, I'd prefer if we didn't make the switch to opencensus.

I was playing around with this, and frankly I don't see the use if we just see the trace IDs, I was actually wildly clicking around the UI expecting to see more.

@tomwilkie @brancz
opencensus z-pages do not provide a complete view of the traces (as seen in Jaeger).
It seems implementing an in-memory backend is the only option left.
(I didn't find any existing tool, which support a complete in-memory visualization of traces)

OpenTracing is an implementation-independent API - it seems likely there could be an adapter behind the scenes.
Having looked at the sample page (and figured out you have to scroll to the bottom after clicking on something) I would have found it really useful, before we (Weaveworks) set up Jaeger. But now we have machinery in place to control Jaeger sampling I don't particularly want to re-do that for OpenCensus.

Since go 1.11, the runtime/time package from go 1.11 has a user annotation API.
I've hacked something quickly (see https://github.com/simonpasquier/prometheus/commit/db97bfbbbc193928ff4de43c293521aac62bcfb1) and it is quite promising. You need to download a trace profile and pass it to go tool trace instead of having the information available in the Prometheus UI but overall it provides the same level of information.
Summary page with all user-defined tasks

List of all traces for one task

Detailed view of a trace

That looks promising. It's better than nothing, doesn't require much code, and should mainly cover the need. Hopefully we can get something in the server itself at some point.

@simonpasquier
:+1: I'll try this out and open a PR.

I really like this proposal, but this is not user friendly at all. The whole point was for users to find out slow queries and asking them to pprof and run this tool for finding it is a little too much.
I think this is orthogonal to the issue and still merits adding it to prometheus, but doesn't solve the problem.


Make a nicer success view

Would be nice if it matched the thin style used for the cancel button in #4. So instead of just using a checkmark character, we could build it using paths.
And some kind of animation. I like organic animations like https://twitter.com/twostraws/status/1088368799928193024

IssueHunt Summary

 allewun has been rewarded.
Sponsors (Total: $142.00)

 issuehunt ($140.00)
 rororofff ($2.00)

Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

@issuehunt has funded $140.00 to this issue. See it on IssueHunt

@rororofff has funded $2.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

@sindresorhus has rewarded $127.80 to @allewun. See it on IssueHunt

:moneybag: Total deposit: $142.00
:tada: Repository reward(0%): $0.00
:wrench: Service fee(10%): $14.20


Address subteam and implementation tracking references

Closes #3 and #4.
Signed-off-by: Kostas Christidis<EMAIL_ADDRESS>

Agreed that all maintainer's is not practical.  But, since there is no such thing as a 'subteam' (at least as Fabric exists today), getting their agreement seems even less practical.  To me, it makes sense to remove the unknown terminology, rather than invent a definition to try to make the paragraph make sense.  If we want to address the 'all maintaners' bit (which I think we do), then that can would be another PR.

@jyellick: Is this a response to @C0rWin's comment, or to this PR in general? (I'm guessing the former, in which case I agree, but it was posted as a comment on the entire PR so the intent is a bit lost on me.)

A bit of both.  Primarily it was meant in support of merging this PR as is, since 'subteam' is an undefined and meaningless term.
I was also in a way responding to @C0rWin with respect to his suggestion to identify component owners, that if we want to go that route, we can do it in another PR, but I'd rather we construct the text to match our definitions, rather than create definitions to match the text.

@jyellick I have just pointed out suggestion, wasn't trying to suggest making changes into current PR. I agree we have to make more concrete formulation which could be a different PR.


Waiting for H298A V9 support

Description of new feature
I would like the H298A V9 router to be supported
Describe alternatives you've considered
C:\Users\Yusuf\Desktop\zte-config-utility-master>py examples/decode.py --serial ZTC094AD61Axxx config.bin config.xml
Signature: H298A V9
Failed! Trying again, with signature: H298AV9
Malformed decrypted payload, likely you used the wrong key!

+1

duplicate of https://github.com/mkst/zte-config-utility/issues/31

Not an unpacker but you can root your router with this script.
https://github.com/gibirnet/H298A-V9-Rooter

closing as dupe of https://github.com/mkst/zte-config-utility/issues/31


adjust current version in version_client and reference to it from azure-identity:pom

/check-enforcer override


Added regex for common hashes and GUIDs

These are regexes I use all the time. Figured they would be handy here.

Thanks for contributing :D


consolidate the logs of python script into container logs

consolidate the logs of python script into container logs
Description

consolidate the logs of python script into container logs
Related-to: https://issues.redhat.com/browse/RHOAIENG-6780
How Has This Been Tested?

In the jupyterlab, include the runtime image from

Use the runtime image created via this PR
or this example: quay.io/harshad16/runtime-minimal:we
Create a pipeline with the below script.
Run the pipeline with the below script:

python script

# try:
#     a = 10
#     b = 0
#     c = a/b
# except ZeroDivisionError:
#     print("Cannot divide by zero!")

a = 10
b = 0
c = a/b

The Expected result:
The log should be shown directly in the pod logs:

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Great work Harshad, I was able to run the pipeline and see the logs
First I run the steps that are described on the PR
[I 11:59:41.096] 'new-test':'test-script' - executing python script using 'python3 test-script.py'
[I 11:59:41.096] ----------------------Python logs start----------------------
Traceback (most recent call last):
File "/opt/app-root/src/test-script.py", line 10, in <module>
c = a/b
ZeroDivisionError: division by zero
[I 11:59:41.122] ----------------------Python logs ends----------------------

But i confused by the error :rofl:
[E 11:59:41.122] Unexpected error: <class 'subprocess.CalledProcessError'>
[E 11:59:41.122] Error details: Command '['python3', 'test-script.py']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/opt/app-root/src/bootstrapper.py", line 758, in <module>
main()
File "/opt/app-root/src/bootstrapper.py", line 748, in main
file_op.execute()
File "/opt/app-root/src/bootstrapper.py", line 507, in execute
raise ex
File "/opt/app-root/src/bootstrapper.py", line 496, in execute
raise subprocess.CalledProcessError(return_code, run_args)
subprocess.CalledProcessError: Command '['python3', 'test-script.py']' returned non-zero exit status 1.
I0621 11:59:41.162471 42 launcher_v2.go:151] publish success.
F0621 11:59:41.162532 42 main.go:49] failed to execute component: exit status 1
time="2024-06-21T11:59:41.654Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1
time="2024-06-21T11:59:42.615Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1

Then i realized that this error is normal and should be there because the script was wrong due to the exceptionZeroDivisionError:
So in order to double check it, i created another python script without errors  and everything was good!
Python Script
import logging
logging.basicConfig(level=logging.INFO)
logger= logging.getLogger("test")
logger.info("this is a python script")
print("this is a print statement")

Logs:
[I 12:34:51.090] 'script-without-errors':'python-script-without-errors' - dependencies processed (0.327 secs)
[I 12:34:51.090] 'script-without-errors':'python-script-without-errors' - executing python script using 'python3 python-script-without-errors.py'
[I 12:34:51.090] ----------------------Python logs start----------------------
INFO:test:this is a python script
this is a print statement
[I 12:34:51.127] ----------------------Python logs ends----------------------

Also I did a test (with your testing .py) to see the old behavior and indeed i couldn't see info logging
test-script.py
tar: Removing leading `/' from member names
tar: .: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors
[I 12:28:09.371] 'old-runtime':'test-script' - dependencies processed (0.315 secs)
[I 12:28:09.371] 'old-runtime':'test-script' - executing python script using 'python3 test-script.py' to 'test-script.log'
[E 12:28:09.386] Unexpected error: <class 'subprocess.CalledProcessError'>
[E 12:28:09.386] Error details: Command '['python3', 'test-script.py']' returned non-zero exit status 1.
[D 12:28:09.428] https://hnalla-test.s3.us-east-1.amazonaws.com:443 "PUT /old-runtime-0621122722/test-script.log HTTP/1.1" 200 0
[I 12:28:09.429] 'old-runtime':'test-script' - uploaded test-script.log to bucket: hnalla-test object: old-runtime-0621122722/test-script.log (0.042 secs)
Traceback (most recent call last):
File "/opt/app-root/src/bootstrapper.py", line 746, in <module>
main()
File "/opt/app-root/src/bootstrapper.py", line 736, in main
file_op.execute()
File "/opt/app-root/src/bootstrapper.py", line 501, in execute
raise ex
File "/opt/app-root/src/bootstrapper.py", line 488, in execute
subprocess.run(run_args, stdout=log_file, stderr=subprocess.STDOUT, check=True)
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['python3', 'test-script.py']' returned non-zero exit status 1.
I0621 12:28:09.471644 43 launcher_v2.go:151] publish success.
F0621 12:28:09.471747 43 main.go:49] failed to execute component: exit status 1
time="2024-06-21T12:28:09.618Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1
time="2024-06-21T12:28:10.573Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1

Thank you for the excellent review
Merging this to get a release out.


nixos/stage-1-systemd: Add keymap support

Makes my life a lot easier with my non-american keyboard layout
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Typo in the commit/PR title:
nixis/stage-1-systemd: Add keymap support -> nixos/stage-1-systemd: Add keymap support

error: cannot coerce a set to a string

       at /nix/store/wm4ly5b0a6byqkbcndl8q93kxww6z0j7-source/nixos/modules/config/console.nix:156:12:

          155|         boot.initrd.systemd.storePaths = [
          156|           "${config.boot.initrd.systemd}/lib/systemd/systemd-vconsole-setup"
             |            ^
          157|           "${config.boot.initrd.systemd.package.kbd}/bin/setfont"

Is there any reason why this patch may be causing an issue with setting console.keyMap = "uk"; in the configuration.nix?  I'm new to NixOS (trying installation on framework) and using unstable (which is probably a mistake), but I can't get nixos-rebuild to take the option.  Error is:
error: The option `console.keyMap` is defined multiple times.

Definition values:
- In `...configuration.nix`: "uk"
- In `...config/console.nix`: <deriviation ....>

e.g. 'it' seems to think that that console.nix is setting console.keyMap?

There is something in the moduel which seems to be unrealated to this PR. It's:
    { console.keyMap = with config.services.xserver;
        mkIf cfg.useXkbConfig
          (pkgs.runCommand "xkb-console-keymap" { preferLocalBuild = true; } ''
            '${pkgs.buildPackages.ckbcomp}/bin/ckbcomp' \
              ${optionalString (config.environment.sessionVariables ? XKB_CONFIG_ROOT)
                "-I${config.environment.sessionVariables.XKB_CONFIG_ROOT}"
              } \
              -model '${xkbModel}' -layout '${layout}' \
              -option '${xkbOptions}' -variant '${xkbVariant}' > "$out"
          '');
    }

@dasJ sorry for the noise!  I'm still (very) new to NixOS/Nix and was trying to work out why I couldn't set console.keyMap in my configuration.nix.  It does appear that the code you posted is interacting with my issue.  I'm guessing that if I set useXbkConfig and console.keyMap in my configuration.nix then the error will occur?  Would that make sense?  I'm guessing that mkIf makes console.keyMap if the if condition is met, otherwise doesn't try to?  I will do some experimentation.

From: Michele Guerini Rocco @.>
To: NixOS/nixpkgs @.>
CC: Janne Heß @.>; Mention @.**>
*Date: *23 Jun 2022 08:08:37
*Subject: *Re: [NixOS/nixpkgs] nixos/stage-1-systemd: Add keymap support
(PR #168600)

@.**** commented on this pull request.

In
nixos/modules/config/console.nix[https://github.com/NixOS/nixpkgs/pull/168600#discussion_r904614444]:

kbd_mode ${if isUnicode then "-u" else "-a"} -C
/dev/console
            printf "\033%%${if isUnicode then "G" else "@"}" >>
/dev/console
            loadkmap < ${optimizedKeymap}

            ${optionalString cfg.earlySetup ''
              setfont -C /dev/console
$extraUtils/share/consolefonts/font.psf
            ''}
-        '';
+        '');

+        boot.initrd.systemd.contents = {
+          "/etc/kbd".source = "${consoleEnv
config.boot.initrd.systemd.package.kbd}/share";
Do you mind explaining me what exactly are you doing here?
What is config.boot.initrd.systemd.package.kbd and how is it
different from pkgs.kbd?

systemd hardcodes the path to the kbd binary during build. When testing,
I, was temporarily using systemd from unstable, meaning that the two kbd
packages were different which broke vconsole setup.

Also, below, couldn't you just add consoleEnv to the storePaths?

No, the search path is in /etc

—
Reply to this email directly, view it on
GitHub[https://github.com/NixOS/nixpkgs/pull/168600#pullrequestreview-1016433669],
or
unsubscribe[https://github.com/notifications/unsubscribe-auth/ABF53R4VMAH5VVSJ2KFJF2DVQP5NPANCNFSM5TNCBSJA].
You are receiving this because you were mentioned.[Tracking
image][https://github.com/notifications/beacon/ABF53R25RA7QR5VPEDA7XPTVQP5NPA5CNFSM5TNCBSJKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOHSKYYBI.gif]


Protect against stack overflow in arbitrary fuzzer

* [ ] I've included my change in CHANGELOG.md

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.05 :warning:

Comparison is base (82536cf) 85.29% compared to head (b6f31e3) 85.24%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #464      +/-   ##
==========================================
- Coverage   85.29%   85.24%   -0.05%
==========================================
  Files          61       62       +1
  Lines        7793     7830      +37
==========================================
+ Hits         6647     6675      +28
- Misses       1146     1155       +9

Impacted Files
Coverage Δ

src/de/mod.rs
74.37% <100.00%> (-0.77%)
:arrow_down:

tests/462_bytes.rs
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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


Change to use Browser Tab plugin and Custom URL Scheme

Fixes #28.

@SidMorad I tried to get this working in iOS emulator tonight and was unable to get it to work. Maybe I'm missing something?

@mraible I did test this branch and the good news is it didn't work in android either! ;) First thing I notice is config.xml is missing following lines:
    <plugin name="cordova-plugin-browsertab" spec="^0.2.0" />
    <plugin name="cordova-plugin-customurlscheme" spec="^4.3.0">
        <variable name="URL_SCHEME" value="ionic4j" />
    </plugin>

I will update you as I progress forward on this.

@mraible with above modification I was successful to login with BrowserTab plugin. Note: I did test in an Android phone and using a remote Api powered with HTTPS. In another words I do have issues when I am using a local development server. probably we need to use 192.168.*.* IPs for this, but it didn't work for me as I remember.
p.s. I regret why I didn't buy a Macbook for development! ;-)

I've had issues with :8080 on iOS Simulator, that's why I mention changing the ports when you install a new app.
AFAIK, when you put cordova.plugins[plugin-name] = {...} in package.json, it's supposed to put those values in config.xml. Maybe I don't understand the Ionic build process, but I think this is how it's supposed to work.

According to this answer it seems things changed since Cordova 7. I might be wrong but it seems Cordova will write plugins into package.json if see them in config.xml and not the way around.
Another things I notice which may be useful somehow, with ionic serve command I could login into my location development server successfully, but I do see same issue  if I change Api end-point to my local network IP (e.g. <IP_ADDRESS>:8080).

The problem is I don't create a config.xml, Ionic does. The following is from 2016, not sure it's still the same syntax in 2018:
"cordovaPlugins": [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    {
      "locator": "https://github.com/Initsogar/cordova-webintent.git#3d12378de9f38be900761a0ad06ab697cf6d9add",
      "id": "com.borismus.webintent"
    },
    {
      "variables": {
        "APP_ID": "123456789987654321",
        "APP_NAME": "TEST"
      },
      "locator"<EMAIL_ADDRESS>      "id"<EMAIL_ADDRESS>    }
  ]

I think I found why BrowserTab fails to work locally. It seems OAuthService(angular-oauth2-oidc) have different behaviour when loginUrl is not in HTTPS.
I found about this by debugging output of loginService#buildUrl method.
Moreover hard coding loginUrl into something like http://<IP_ADDRESS>:9080/auth/realms/jhipster/protocol/openid-connect/auth will shows login form in a tab. After successful login I saw this issue: Uncaught Error: Parameter jwks expected!, which more likely is related to not using HTTPS again.

Closing due to inactivity.