n_random_starts not totally deprecated in base_minimize

In Optimizer.py, n_random_starts is described to be replaced by n_initial_points. However in base.py, this parameter is still in use. Does this need to be unified as well?

No, this is on purpose. There is a bit of discussion here. @MechCoder might also remember some details.
I'll close this, feel free to reopen if you disagree.

After reading the whole comments, could finally get a sense of what's going on and being fixed. ¯_(ツ)_/¯ Now it totally makes sense to me about every "number of points" operation within Optimizer and *_minimize.
The doc string in Optimizer is not confusing as it clearly states "If len(x0) < n_initial_points, additional points are sampled at random." But I would suggest similar changes to be reflected in base.py as well.
Right now it says,

n_random_starts [int, default=10]:
Number of evaluations of func with random points before
approximating it with base_estimator.

Because the whole depreciation thing in optimizer, it could be clearer if stated as:

n_random_starts [int, default=10]:
Number of evaluations of func with random points to sample
apart from x0 before approximating it with base_estimator.

But there's huge possibility that it's just me. :)


Similar to issue 32

I just realized that you had closed issue #32.
Hi, I seem to be having a similar issue. I followed the installation directions and the fix suggestions described in this issue. 1. Reinstall plugin 2. start in dev mode 3. Increase firstDrawingDelay. I see nothing on the screen (i am able to see other modules).
I have this as my config.
	module: "MMM-CalendarExt2",
	config: {
		 rotateInterval: 90*1000,
		 firstDrawingDelay: 1000*10,
		 scenes: [ // `scenes` could have several scenes as elements of array
		 {
			   name: "My kids schedule",
			   views: ["Daily", "Weekly"],
			   //className: "CX2",
		 },

		],
		views: [
			{
			  name: "Daily",
			  mode: "upcoming",
			  calendars: ["Schedule"],
			  position: "top_center",
			  maxItems: 5,
			  maxDays: 1,
			  locale: "en",
			  hideOverflow: false,
			  filterPassedEvent: true,
			},
			{
			  name: "Weekly",
			  mode: "weekly",
			  position: "middle_center",
			  calendars: ["Schedule"],
			  type: "row",
			  slotCount: 5,
			  locale: "en",
			  hideOverflow: false,
			  filterPassedEvent: true,
			},
		  ],
		  calendars : [
			{
			  name: "Schedule",
			  icon: "noto-soccer-ball",
			  url: "https://calendar.google.com/calendar/ical/1d4a1djtgmai0fpapjvtr6cdhs%40group.calendar.google.com/public/basic.ics",
			  //url: "webcal://p23-caldav.icloud.com/published/2/MTU3Mzc5NzU3MTU3Mzc5N7QDyWhkoQhUDUPID--ipr-ZOrn-Q4_1aVyt-0MWrJp7YNRJozQcvp5txgCkR1Oa9aPtBd5BXqQ48ly68Sx7T98/"
			},
		  ],

	},
	  },

Hi @redy, maybe the first question to ask: did you verify, that there are at least some events in the google calendar you used?

Yes, there were. It was showing up with the calendar module included with the base magic mirror plugin.

What do the logfiles say? Do they pickup the correct number of events?

@redy I tested your config snipped and it works.

no reply for a month, closing the issue


Re-enable code coverage comments on PRs

Motivation
It's easy to miss the code coverage percentage in the PR check results. (I just did it during a recent PR review.)
This is unexpected stable release work.
Solution
Re-enable code coverage comments, regardless of whether coverage has actually changed.
Review
@gustavovalverde can review this PR. It's not urgent.
Reviewer Checklist

[ ] Coverage comment appears on this PR

Follow Up Work

Actually improve code coverage
Fail the PR if coverage drops a lot

Codecov Report

Merging #3246 (ae992d3) into main (ea01e30) will decrease coverage by 0.18%.
The diff coverage is n/a.

Hmm, since our tests are randomised, our coverage percentages are unstable.

Merging #3246 (1b21cdc) into main (852c5d6) will decrease coverage by 0.11%.
The diff coverage is n/a.

Yep, unstable 😢


Deref operator (*) of possible ObjectType arguments improperly escaped

The asterisks (*) before the possible values for the ObjectType parameters are not preceded by backslash (\) and thus interpreted as the italics formatting for the Markdown renderer. This also applies to other documentations describing kernel APIs that take the same type of argument.
Related: #288

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

ID: 60b24f38-757d-d7ab-fc56-3e68c0d91cb1
Version Independent ID: 71e0d5b7-52cc-a5d8-2d5f-d94d50984947
Content: ObReferenceObjectByHandle function - Windows driver
Content Source: wdk-ddi-src/content/wdm/nf-wdm-obreferenceobjectbyhandle.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Thanks, @iamahuman.
I believe that I got all the guilty topics. If you see some I missed, please let me know.


add ASmap for run<PHONE_NUMBER>

This adds the asmap.dat result for the coordinated launch from https://github.com/asmap/asmap-data/issues/18 from epoch<PHONE_NUMBER>. We had a match from 4 out of 5 participants in the coordinated launch.
To confirm the result of the encoding you can use asmap-tool.
$ shasum -a<PHONE_NUMBER>400_final_result.txt
8986e7baf0aea86b6b63766968d77edb384d1c332b23725596e18693235419ce<PHONE_NUMBER>_final_result.txt

$ python3 contrib/asmap/asmap-tool.py encode<PHONE_NUMBER>_final_result.txt<PHONE_NUMBER>_asmap.dat

$ shasum -a<PHONE_NUMBER>400_asmap.dat
93afd5c0a82f82fca9988881f397739427c9c34bc1adb337e0d00978dcd1863a<PHONE_NUMBER>_asmap.dat

ACK acfd979e2115a24bf2c533bbc42db7694f65eea2
Encoding my final_results.txt I too get an asmap.dat file with the hash 93afd5c0a82f82fca9988881f397739427c9c34bc1adb337e0d00978dcd1863a. I checked that the file added here hashes to the 93afd5c0.. hash.

I thought about making latest_asmap.dat a symlink of an asmap file. I think it should work for Linux an probably macOS too. However, it might not work for Windows.

However, it might not work for Windows.

yea let me see if I get a windows user to test this.

However, it might not work for Windows.

Windows does not seem to resolve the symlink natively. There's some configuration to change ( enable Windows Developer mode) and maybe set git config core.symlinks true as well, but not sure. I'd like the opinion of someone who knows Windows better to confirm this. Is there a Core windows testing person?

@0xB10C @jurraca The latest_asmap file exists primarily so we have a constant link to the latest file on GitHub for download that can be shared/documented like in the seeds readme: https://github.com/bitcoin/bitcoin/tree/master/contrib/seeds I tested this initially but GitHub doesn't follow symlinks so even if it would work on windows we still couldn't make it a symlink. Maybe there are more elegant ways to do this and I am happy to consider new idea but I don't want to add any additional dependency and this is simple and works for now.

fwiw: I now run one of my monitoring nodes with -asmap=latest_asmap.dat (being<PHONE_NUMBER>)

fwiw: I now run one of my monitoring nodes with -asmap=latest_asmap.dat (being<PHONE_NUMBER>)

Awesome! Please let us know if you see anything noteworthy, it will definitely be interesting for the embedding discussion in core.


Drop Down remains the same even when selected other label.

The Opportunities drop down remains the same even if we select for example scholarships it doesn't change according to the item we selected.

Hello, @abdus I also want to work on this issue, if it didn't get resolved.

Hey! I did a git pull and got the latest code and the on npm start I got this error.

I inspected the folder directory and noticed that there are 2 signUpLogin folders having same code.

Which folder should I delete? What should I do next?

Hey, can you pull the latest code once again .. please?


WIP: Add SnapScheduler operator (upstream-community-operators)

Adds the SnapScheduler operator
The SnapScheduler operator takes snapshots of Kubernetes CSI-based persistent volumes according to user-supplied schedules.
Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[x] Does your operator have nested directory structure?
[x] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

I went ahead and increased the Deployment replica count to 2 as that's how it's intended to run.


Implementation of  CI/CD (Build jobs automatically )

Implement CI/CD (Build jobs automatically ) - using tools like CircleCI etc.
Comments

Do we go with the CircleCI standard installation/workflow/rules for are there some specific considerations to make (like CircleCi for node, angular, python applications)

Any other tools in conjunction with CircleCI to help us (like the<EMAIL_ADDRESS>for browser testing)"

This problem will be addressed in cQube v5.0.

This is implemented in the current version


Add cloud builds (using Travis?)

When someone commits to main then a cloud build should start and validate that there are no compile errors and no tests failing.

https://gist.github.com/aagarwal1012/eb2551683d81cf47d60868ab607520b1
https://dev.to/ameysunu/travis-ci-for-flutter-apps-1ngj

Add a badge to Readme showing that the last build passed.

Will look into this :)

@madmas  please be sure to add the readme badge:
![example workflow](https://github.com/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)

maybe we have to do that as a 2nd step


remove colab links for cldk recipes

https://github.com/ibm-granite-community/granite-code-cookbook/pull/137

:white_check_mark:


当我运行  python startup.py "贪吃蛇游戏" 时，报这个错误

Traceback (most recent call last):
File "C:\Users\Administrator\Documents\DevCode\MetaGPT\startup.py", line 7, in
from metagpt.roles import Architect, Engineer, ProductManager
ModuleNotFoundError: No module named 'metagpt'

You can execute the command pip install -e . before running the program.

Install the Module: If "metagpt" is a third-party package, open your command prompt or terminal and run:
pip install metagpt
Replace "metagpt" with the actual name of the package if it's different. This step installs the missing module.


Editing for some of the more finished pages

A lot of what I have been working on in this branch is going through some of the pages that seem to be just about done and making any last-minute edits for the sake of grammar or to make sure our HTML is semantically correct (heading tags used in the right order, correct tabbing, informative alt attribute descriptions for images, etc.). These changes would affect the styling on Bijisa's pages and on the Home page just a little bit, so I'd really like it if Bijisa and Antonio could look over the changes and see what they think before I merge this in. If there's anything you want me to change, I can just make a new commit to this branch with the changes.

Hey Lydia, thanks for catching the tabbing errors! The changes look good on my end. They're good to merge.


Wrap all auth callback functions to pass the original H3Event

I've been wanting access to the original H3Event on auth callback requests so I can do things like pass state in query params to OAuth providers (inviteToken). I have an open discussion here. While this adds my desired functionality it is missing testing and NextAuth type modifications.
Closes # .
Checklist:

[ ] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[ ] manually checked my feature / checking not applicable
[ ] wrote tests / testing not applicable
[ ] attached screenshots / screenshot not applicable

I should add that this allows me to do this in the signIn callback:
signIn: async ({ account, credentials, event, user }) => {
  const inviteToken = getCookie(event, 'inviteToken')
  ...
}

Thanks @joneath for the contribution (: I'll have a look at it in a bit, one thing you could already do is to fix the failing CI checks (:

Hi @joneath 👋
I am going through some PRs and noticed yours is still open, but pretty close to being finished! Do you think you could look into fixing the lint errors?


Receiving "MessagePack::UnknownExtTypeError" when using forward source

Hi team,
I am repeatedly seeing the below error in the td-agent log file (attached) when using a forward plugin instance as a source. I am using Fluent-bit (td-agent-bit service, v0.12.4) to forward data to a Fluentd (td-agent service, v2.3.6-0) instance which sends data to ElasticSearch. All 3 products are running on the same server (as a prototype) running Ubuntu 16.04.3 patched up to last week.
The error I see is below (timestamp removed for brevity):
[error]: forward error error=#<MessagePack::UnknownExtTypeError: unexpected extension type> error_class=MessagePack::UnknownExtTypeError   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluentd-0.12.35/lib/fluent/plugin/in_forward.rb:337:in 'feed_each'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluentd-0.12.35/lib/fluent/plugin/in_forward.rb:337:in 'on_read_msgpack'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluentd-0.12.35/lib/fluent/plugin/in_forward.rb:323:in 'call'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluentd-0.12.35/lib/fluent/plugin/in_forward.rb:323:in 'on_read'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/cool.io-1.4.6/lib/cool.io/io.rb:123:in 'on_readable'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/cool.io-1.4.6/lib/cool.io/io.rb:186:in 'on_readable'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/cool.io-1.4.6/lib/cool.io/loop.rb:88:in 'run_once'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/cool.io-1.4.6/lib/cool.io/loop.rb:88:in 'run'   [error]: /opt/td-agent/embedded/lib/ruby/gems/2.1.0/gems/fluentd-0.12.35/lib/fluent/plugin/in_forward.rb:120:in 'run'
I have attached:

the full td-agent log file
the configuration for td-agent
the configuration for td-agent-bit

I've scoured the docs for both services and I can't see what could be wrong with my configuration that is causing this error. I can't tell if the error is due to an issue with the fluentd forward plugin or one of the fluent-bit plugins I'm using.
Thanks for any help you can give :)
files.zip

I assume your fluent-bit configuration issue: https://docs.fluentd.org/v0.12/articles/in_forward#i-got-messagepackunknownexttypeerror-error-why
@edsiper ?

Enable the option Time_as_Integer On in the output config (Fluent Bit side)

@edsiper Thanks for the pointer, the error is gone now. Note to self, read the FAQ first :)

Link is broken.  New link:  https://docs.fluentd.org/v/0.12/input/forward#i-got-messagepack-unknownexttypeerror-error-why


Suggested deployment SOP: push to production with tag instead of branch

This will keep the list of branches tidy, and to allow deployment using the GitHub "releases" feature which creates tags rather than branches.

(sidenote: you can see this in action here: https://github.com/nf-osi/NF_data_curator/actions/runs/1894682650)

I will merge it to develop first


Track Django migrations in GitHub

Issue Type

[ ] Bug
[x] Enhancement

Description
In order not to break existing installations and thus making the process of upgrading DefectDojo easier, I suggest to start keeping track of Django migration files in the GitHub repo.
The following scenario currently breaks the application and may keep people from upgrading DefectDojo:

Someone operates a DefectDojo instance
A new version of DefectDojo including a new killer feature but also with some model changes is released.
Someone deploys the new version of DefectDojo and generates a new 0001_initial_migration.py representing the new state of the models. The newly generated initial migration will be ignored, since Django keeps track, which migrations have been applied already (in the DB). So, the app will throw errors, telling some fields could not be found. The application will not be usable, unless the DefectDojo Admin figures out, which version they used previously and generates a 0002 migration based on the model changes.

Instead of this scenario, I suggest to keep track of model changes via migration files, which are incremental and which should improve the upgrading experience for DefectDojo Admins.
EDIT: Removed the actual mention of _at_Someone :D

Looks like the described scenario is the cause for issues #468, #473, and probably more. So this change would cause fewer issues.

I'm thinking about a strategy to add migrations and I can think of the two approaches:

Simply add an initial mi


Programming errors by users do not indicate where it occurs in the user code

Describe the bug
If a user makes a mistake in the code, the errors thrown on the console/terminal do not indicate the relevant lines in the user code. Only the lines in the reflex library. This makes it difficult to pinpoint where the user mistake is.
To Reproduce
Steps to reproduce the behavior:
Follow the Reflex chat tutorial here https://reflex.dev/docs/tutorial/final-app/, in the state.py file def answer(): function, instead of yield, type yield self.chat_history. It causes the error in the Screenshots below.
Expected behavior
The error stack should indicate where the programming error in the user code. Right now it is not only showing the lines in the reflex library. It'll be difficult to pinpoint/debug.
Screenshots
If applicable, add screenshots to help explain your problem.
Task exception was never retrieved
future: <Task finished name='Task-70' coro=<AsyncServer._handle_event_internal() done, defined at /opt/homebrew/lib/python3.11/site-packages/socketio/asyncio_server.py:522> exception=TypeError('unsupported callable')>
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 1369, in getfullargspec
    sig = _signature_from_callable(func,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 2449, in _signature_from_callable
    raise TypeError('{!r} is not a callable object'.format(obj))
TypeError: ('how big is canada', '') is not a callable object

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/homebrew/lib/python3.11/site-packages/socketio/asyncio_server.py", line 524, in _handle_event_internal
    r = await server._trigger_event(data[0], namespace, sid, *data[1:])
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/socketio/asyncio_server.py", line 569, in _trigger_event
    return await self.namespace_handlers[namespace].trigger_event(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/socketio/asyncio_namespace.py", line 37, in trigger_event
    ret = await handler(*args)
          ^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/reflex/app.py", line 734, in on_event
    async for update in process(self.app, event, sid, headers, client_ip):
  File "/opt/homebrew/lib/python3.11/site-packages/reflex/app.py", line 586, in process
    async for update in state._process(event):
  File "/opt/homebrew/lib/python3.11/site-packages/reflex/state.py", line 693, in _process
    events = fix_events(events, event.token)  # type: ignore
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/reflex/event.py", line 483, in fix_events
    e = e()
        ^^^
  File "/opt/homebrew/lib/python3.11/site-packages/reflex/event.py", line 56, in __call__
    fn_args = inspect.getfullargspec(self.fn).args[1:]
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 1379, in getfullargspec
    raise TypeError('unsupported callable') from ex
TypeError: unsupported callable

Specifics (please complete the following information):

Python Version: 3.11
Reflex Version: 0.2.4
OS: MacOS
Browser (Optional):

Additional context
Add any other context about the problem here.

Thanks for reporting this issue. Tracking internally as REF-198


EmulationStation won't run games

I'm using RetroArch and EmulationStation on my windows 10 laptop, and I can load ROMS onto the program easily. When I try to run the ROMS, the games crash and bring me back to the EmulationStation game menu. When I check es_log this is what is recorded.
lvl2: 	 req sound [basic.launch]
lvl2: 	   (missing)
lvl2: 	Attempting to launch game...
lvl2: 	 getting volume as 100 ( from float 1)
lvl2: 		C:\Users\Atatv.emulationstation\systems\dolphin\Dolphin.exe -e "C:\Users\Atatv\Emulators\Roms[SYSTEM INITIALS][GAME NAME]"
lvl1: 	...launch terminated with nonzero exit code 1!
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	 req sound [basic.launch]
lvl2: 	   (missing)
lvl2: 	Attempting to launch game...
lvl2: 		C:\Users\Atatv.emulationstation\systems\dolphin\Dolphin.exe -e "C:\Users\Atatv\Emulators\Roms[SYSTEM INITIALS][GAME NAME]"
lvl1: 	...launch terminated with nonzero exit code 1!
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
I have tried multiple games, systems, and restarting the program and my computer, is there anything else I can try?

Same here, im using windows 7 in a mackbook pro 13 inch, game: windowed emulationstation: good loading roms: NOPE
they get me to the home screen, just like you, somebody fix this quickly

Having the same issues on windows 10
lvl2: 	EmulationStation - v2.0.1a, built Mar  8 2015 - 16:10:39
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	Checking available OpenGL extensions...
lvl2: 	 ARB_texture_non_power_of_two: ok
lvl2: 	Loading system config file C:/Users/Will/.emulationstation/es_systems.cfg...
lvl2: 	Parsing XML file "C:/Users/Will/.emulationstation/gamelists/snes/gamelist.xml"...
lvl2: 	 req sound [basic.launch]
lvl2: 	   (missing)
lvl2: 	Attempting to launch game...
lvl2: 	 getting volume as 100 ( from float 1)
lvl2: 		F:\EMU\ES install files\EmulationStation\RetroArch\retroarch.exe -L F:\EMU\ES install files\EmulationStation\RetroArch\cores\snes9x2010_libretro.dll F:\EMU\ROMS\SNES\3 Ninjas Kick Back (USA).sfc
lvl1: 	...launch terminated with nonzero exit code 1!
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	EmulationStation cleanly shutting down.

I am getting the same problem with emulationstation portable. I can play SNES games but when I try to play a PC-FX game It refuses to launch. Here is the end of my log.
lvl2: 	Attempting to launch game...
lvl2: 	 getting volume as 9 ( from float 0.09)
lvl2: 		%HOME%.emulationstation\systems\retroarch\retroarch.exe -L %HOME%.emulationstation\systems\retroarch\cores\snes9x_libretro.dll "J:\.emulationstation\roms\snes\3 Ninjas Kick Back (USA).zip"
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	Added known joystick XInput Controller #1 (instance ID: 1, device index: 0)
lvl2: 	Added known joystick XInput Controller #1 (instance ID: 1, device index: 0)
lvl2: 	 req sound [detailed.launch]
lvl2: 	   (missing)
lvl2: 	Attempting to launch game...
lvl2: 		%HOME%.emulationstation\systems\retroarch\retroarch.exe -L %HOME%.emulationstation\systems\retroarch\cores\mednafen_pcfx_libretro.dll "J:\.emulationstation\roms\pcfx\Aa! Megami Sama - Disc A.chd"
lvl1: 	...launch terminated with nonzero exit code 1!
lvl2: 	Creating surface...
lvl2: 	Created window successfully.
lvl2: 	Added known joystick XInput Controller #1 (instance ID: 2, device index: 0)
lvl2: 	Added known joystick XInput Controller #1 (instance ID: 2, device index: 0)
Here is the relevent systems config info copied from es_systems.cfg
Config.txt
I am running on Windows 7 64 bit SP3.

problem of configuration super console x with windows 10.

problem of configuration super console x with windows 10.

what's the problem then, the config of the controller or the es_systems.cfg ?

Probleme with PC games.
Pc games don't work
Probleme of saves
Envoyé depuis l'application Mail Orange
----------------De : mm579 @.>Envoyé : samedi 02 septembre 2023 21:27À : Aloshi/EmulationStation @.>Cc : jean-philippe DELORME @.>; Comment @.>Objet : Re: [Aloshi/EmulationStation] EmulationStation won't run games (#819)
what's the problem then, the config of the controller or the es_systems.cfg ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>


Paged file browser

This signficantly reduces the ram usage when using the import dialog to browse and import samples from the sdcard.
It changes the Import Dialog when built for picotracker to use a new picoTrackerPagedDir class that implements a new interface instead of I_Dir.  This changes the file system operations to be done in "pages" of files and only stores the indexes of file and subdirectory entries of the currently open directory and only fetches the names of entries on demand in "pages" limited in size to what the dialog UI can display at one time (currently 15).
The ImportSampleDialog is also heavily rewritten to make use of the interface and use as little ram as possible.
This doesn't impose any hard limits on the number of files per directory, but it does set initial sizes of max of 96 subdirs and 354 files per subdir so its quite possible that exceeding these limits could cause extra memory allocation to overflow available ram at the moment.
Please note this is "stacked" on top of PR #26 so that PR should be merged before this one is.
Note: these changes do mean that apart from having subdirs listed before files, there is no other sorting of entries in a directory being applied for now.
Also I've kept all my commits in this PR but I would recommend doing a "squash merge" as all these commits don't really need to be included in the main branches history.
Fixes #14

For starters a couple of comments.
I should put this on some dev standards file or something. Could you use "clang-format" with default options on new files? I've been doing that in all new files and when I modify others, I regret not having done this on the base project before I started the fork.
How useful is the gui debug code enabled with SHOW_MEM_USAGE? Do you think this makes sense rather than debug logs? Not against per se, but maybe if it's something that we want to support for development we should create some generic define GUI_DEBUG? GUI_DEBUG_MESSAGES?

Thanks for taking a look at this so quickly @democloid ! 👍🏻
Ah thanks for the pointer, I didn't know about clang-format! I lean on dartfmt heavily when writing in Dart so great to know theres a tool for  c++ as well. I'll reformat all the new files with it. Its tempting for me to reformat existing file too as the mix of tabs and spaces drives me nuts, but the downside there is losing git blame to be able to quickly see if code was changed for picotracker or is original Lgpt code.
Oops, sorry I left SHOW_MEM_USAGE enable by mistake, will fix that 👍🏻 And double oops, forgot to disable uart debug as well.
But in general, yes I found it very useful to have on the screen during debugging as I had alot of debug logging enabled as I don't yet have uart for gdb setup so I was doing "print line debugging" and having mem usage on the display vs swapped by lots of other logs did help. So having a more general #define would probably be a good idea but for now I can't think of other UI I want to add so maybe just keep it for now until we need something more general?

@democloid I've updated to remove the debug build settings and also reformatted my new files and the 2 main files I changed in the picotracker subdir with clang-format (default settings) but I kept the others as is to try to make it clearer what changes I made as part of this (except for SelectProjectDialog where I had already changed some of the whitespace formatting but didnt seem worth it to reformat the whole file with clang-format).

@democloid I've hopefully addressed all the feedback, either with code changes or replies, but do let me know if you have followup comments 👍🏻 .


vtd: add git describe to profile_default

If no VERSION is explicitly set, use the git describe version tag.

Could you reword your commit to follow our current convention:
vtd: Add ...


Release 0.1

@kosack – We should release early and often.
So I've added a 0.1 milestone for Friday next week (July 3).
This is a test release where I want to see if making the source tarball works and things like accessing the right version of cta-extra data from a stable release. It will not be advertised to anyone.
IMO it's not important to have any features ready by then, although having direction reco working by the end of next week would be nice.

That sounds good to me. I will try to also add all of my example code somewhere, and clean up some of the docs.  If I have time, I'll also look into and example of packaging+interfacing C code.

@kosack – Sorry I didn't have time to work on ctapipe at all this week.
I still think it's useful to make a release for checking / practice.
Do you want to do it or should I? (if there's no issues it only takes ~ 1 hour to do it and some basic checking, but usually with the first release there's some things, like missing files because of the MANIFEST file or whatever ...)
Here's some notes I have for Gammapy how to make a release: https://gammapy.readthedocs.org/en/latest/development/index.html#make-a-gammapy-release

@kosack – Any chance you can make a 0.1 release before the PyGamma15 workshop for ctapipe and maybe even make pip install ctapipe and / or conda install ctapipe work?

I can probably do that, but the project may soon move to being semi-private (due to the Project Office decisions today), so that may cause me some problems. I'll try to at least make a release of what we have. Ideally I'd like it on a separate conda channel

Are you saying, that CTA just decided that the analysis software for CTA will be closed source?

No, It will almost certainly still be open-source (I will strongly push for that), but the development and distribution may be centralized (e.g. we may be required to abandon github + pypi, etc, and use a system installed at the PO like GitLab + a specialized conda channel).  Therefore a simple "pip install" may not work if we can't upload things to the public pypi.  It would still be fairly open, though it's not clear if they want us to start with a private repo or not. It all depends on what is drafted in the consortium agreement by lawyers.

Closing this old issue now. Looks like there have been releases (or at least tagged versions) of ctapipe in the past.


TaskRun reports as successful when the pod was evicted

Expected Behavior
When a pod/container is evicted, the taskrun should fail, and include a reason/message associated to the eviction
Actual Behavior
the task run reports successful or shows an exit code / message from a container (137 reason Failed, not evicted)
Steps to Reproduce the Problem

Run a pipeline with a emptdir workspace that has a size limit

  - emptyDir:
      sizeLimit: 10Gi
    name: workspace-user-repo

Task executes code that exceeds the limit

Sometimes the taskrun will fail correctly stating that there was an eviction,
          message: 'Usage of EmptyDir volume "ws-hdl48" exceeds the limit "10Gi". '
          reason: Failed
          status: "False"

Other times it does not In these cases the container itself contains the eviction error. This seems to maybe be a race between the containers in the pod finishing and  the eviction taking place?
Additional Info

Kubernetes version:
Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.1", GitCommit:"8f94681cd294aa8cfd3407b8191f6c70214973a4", GitTreeState:"clean", BuildDate:"2023-01-18T15:51:24Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.16-eks-ffeb93d", GitCommit:"52e500d139bdef42fbc4540c357f0565c7867a81", GitTreeState:"clean", BuildDate:"2022-11-29T18:41:42Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

Tekton Pipeline version:
Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

Client version: 0.29.1
Pipeline version: v0.40.2

Task run status
status:
  completionTime: "2023-02-10T17:19:38Z"
  conditions:
  - lastTransitionTime: "2023-02-10T17:19:38Z"
    message: All Steps have completed executing
    reason: Succeeded
    status: "True"
    type: Succeeded
  podName: c4382b4f-af66-478e-b603-0b9b5a2f9127-linux-amd64-user-code-pod
  sidecars:
  - container: sidecar-ssh-key-setup-sidecar
    name: ssh-key-setup-sidecar
    terminated:
      containerID: docker://336d7a36b4598f653f94b16840879980ed2d2ff74ba50e1c3983171433d16eb3
      exitCode: 137
      finishedAt: "2023-02-10T17:20:08Z"
      reason: Error
      startedAt: "2023-02-10T17:18:10Z"
  startTime: "2023-02-10T17:18:02Z"
  steps:
  - container: step-place-tools
    imageID:
    name: place-tools
    terminated:
      containerID: docker://084b76ebd5dd2966941e141ab83f454d6a142c12a89a685cf4fd47baf3a6c33b
      exitCode: 0
      finishedAt: "2023-02-10T17:18:17Z"
      reason: Completed
      startedAt: "2023-02-10T17:18:17Z"
  - container: step-linux-amd64-user-code-extract-workspace-user-repo
    imageID:
    name: linux-amd64-user-code-extract-workspace-user-repo
    terminated:
      containerID: docker://642849d43d7a5ac81d33952c6a8ecd1184cf82d74fda0ee240c53cecc5447d04
      exitCode: 0
      finishedAt: "2023-02-10T17:18:17Z"
      reason: Completed
      startedAt: "2023-02-10T17:18:17Z"
  - container: step-linux-amd64-user-code-extract-workspace-root-cache
    name: linux-amd64-user-code-extract-workspace-root-cache
    terminated:
      containerID: docker://3dd259a891d7a5639aecb1ae5d98c8f878fa5ed1945cf05ffbd1cf9813ccd7f5
      exitCode: 0
      finishedAt: "2023-02-10T17:18:45Z"
      reason: Completed
      startedAt: "2023-02-10T17:18:17Z"
  - container: step-user-code
    name: user-code
    terminated:
      containerID: docker://8bc929f05506f2f5ca702ff113eea0d1b84f4db2016c4b2bcb5e843ce5fb6e7d
      exitCode: 0
      finishedAt: "2023-02-10T17:18:49Z"
      reason: Completed
      startedAt: "2023-02-10T17:18:46Z"
  - container: step-linux-amd64-user-code-persist-workspace-root-cache
    name: linux-amd64-user-code-persist-workspace-root-cache
    terminated:
      containerID: docker://5887ed9ad53114bd729ae07a1e6127438f8ec2fb157e123c8d65a5f60fd9f682
      exitCode: 0
      finishedAt: "2023-02-10T17:19:35Z"
      reason: Completed
      startedAt: "2023-02-10T17:18:49Z"
  - container: step-linux-amd64-user-code-persist-workspace-user-repo
    name: linux-amd64-user-code-persist-workspace-user-repo
    terminated:
      containerID: docker://b769e06ea058d600cc729d1cc096a31c11ac0cddaa12960099911ff99a9b21bb
      exitCode: 0
      finishedAt: "2023-02-10T17:19:35Z"
      reason: Completed
      startedAt: "2023-02-10T17:19:35Z"
  - container: step-linux-amd64-user-code-extract-workspace-private
    name: linux-amd64-user-code-extract-workspace-private
    terminated:
      containerID: docker://5e8a1a38767009a8b05efd46635f29bc96edd5698ccea5dd93579d132632c50a
      exitCode: 0
      finishedAt: "2023-02-10T17:19:36Z"
      reason: Completed
      startedAt: "2023-02-10T17:19:36Z"
  - container: step-post-user-code
    name: post-user-code
    terminated:
      containerID: docker://ef423030366d101e17833e0b6fb81db300704002bb714f5d99282626466f3b70
      exitCode: 0
      finishedAt: "2023-02-10T17:19:37Z"
      reason: Completed
      startedAt: "2023-02-10T17:19:36Z"
  - container: step-linux-amd64-user-code-persist-workspace-private
    name: linux-amd64-user-code-persist-workspace-private
    terminated:
      containerID: docker://84aa4feb2bef2e6e4fe239f987a2c69fa91dd0039ded8fcb8f85057d6c4d0965
      exitCode: 0
      finishedAt: "2023-02-10T17:19:37Z"
      reason: Completed
      startedAt: "2023-02-10T17:19:37Z"
  - container: step-finally-exit
    name: finally-exit
    terminated:
      containerID: docker://135240c44b4059d60cf3b376c35f959ad4bb9b854d5902cc7d2b59b5d9f6df88
      exitCode: 0
      finishedAt: "2023-02-10T17:19:38Z"
      reason: Completed
      startedAt: "2023-02-10T17:19:38Z"

Pod status & container statuses
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-02-10T17:18:06Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2023-02-10T17:18:17Z"
    reason: PodFailed
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2023-02-10T17:18:17Z"
    reason: PodFailed
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2023-02-10T17:18:02Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: docker://336d7a36b4598f653f94b16840879980ed2d2ff74ba50e1c3983171433d16eb3
    lastState: {}
    name: sidecar-ssh-key-setup-sidecar
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://336d7a36b4598f653f94b16840879980ed2d2ff74ba50e1c3983171433d16eb3
        exitCode: 137
        finishedAt: "2023-02-10T17:20:08Z"
        reason: Error
        startedAt: "2023-02-10T17:18:10Z"
  - containerID: docker://135240c44b4059d60cf3b376c35f959ad4bb9b854d5902cc7d2b59b5d9f6df88
    lastState: {}
    name: step-finally-exit
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://135240c44b4059d60cf3b376c35f959ad4bb9b854d5902cc7d2b59b5d9f6df88
        exitCode: 0
        finishedAt: "2023-02-10T17:19:38Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:19:38.142Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:10Z"
  - containerID: docker://5e8a1a38767009a8b05efd46635f29bc96edd5698ccea5dd93579d132632c50a
    lastState: {}
    name: step-linux-amd64-user-code-extract-workspace-private
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://5e8a1a38767009a8b05efd46635f29bc96edd5698ccea5dd93579d132632c50a
        exitCode: 0
        finishedAt: "2023-02-10T17:19:36Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:19:36.131Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:09Z"
  - containerID: docker://3dd259a891d7a5639aecb1ae5d98c8f878fa5ed1945cf05ffbd1cf9813ccd7f5
    lastState: {}
    name: step-linux-amd64-user-code-extract-workspace-root-cache
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://3dd259a891d7a5639aecb1ae5d98c8f878fa5ed1945cf05ffbd1cf9813ccd7f5
        exitCode: 0
        finishedAt: "2023-02-10T17:18:45Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:18:17.687Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:07Z"
  - containerID: docker://642849d43d7a5ac81d33952c6a8ecd1184cf82d74fda0ee240c53cecc5447d04
    lastState: {}
    name: step-linux-amd64-user-code-extract-workspace-user-repo
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://642849d43d7a5ac81d33952c6a8ecd1184cf82d74fda0ee240c53cecc5447d04
        exitCode: 0
        finishedAt: "2023-02-10T17:18:17Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:18:17.346Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:07Z"
  - containerID: docker://84aa4feb2bef2e6e4fe239f987a2c69fa91dd0039ded8fcb8f85057d6c4d0965
    lastState: {}
    name: step-linux-amd64-user-code-persist-workspace-private
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://84aa4feb2bef2e6e4fe239f987a2c69fa91dd0039ded8fcb8f85057d6c4d0965
        exitCode: 0
        finishedAt: "2023-02-10T17:19:37Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:19:37.820Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:09Z"
  - containerID: docker://5887ed9ad53114bd729ae07a1e6127438f8ec2fb157e123c8d65a5f60fd9f682
    lastState: {}
    name: step-linux-amd64-user-code-persist-workspace-root-cache
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://5887ed9ad53114bd729ae07a1e6127438f8ec2fb157e123c8d65a5f60fd9f682
        exitCode: 0
        finishedAt: "2023-02-10T17:19:35Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:18:49.447Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:08Z"
  - containerID: docker://b769e06ea058d600cc729d1cc096a31c11ac0cddaa12960099911ff99a9b21bb
    lastState: {}
    name: step-linux-amd64-user-code-persist-workspace-user-repo
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://b769e06ea058d600cc729d1cc096a31c11ac0cddaa12960099911ff99a9b21bb
        exitCode: 0
        finishedAt: "2023-02-10T17:19:35Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:19:35.792Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:08Z"
  - containerID: docker://084b76ebd5dd2966941e141ab83f454d6a142c12a89a685cf4fd47baf3a6c33b
    lastState: {}
    name: step-place-tools
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://084b76ebd5dd2966941e141ab83f454d6a142c12a89a685cf4fd47baf3a6c33b
        exitCode: 0
        finishedAt: "2023-02-10T17:18:17Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:18:17.015Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:07Z"
  - containerID: docker://ef423030366d101e17833e0b6fb81db300704002bb714f5d99282626466f3b70
    lastState: {}
    name: step-post-user-code
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://ef423030366d101e17833e0b6fb81db300704002bb714f5d99282626466f3b70
        exitCode: 0
        finishedAt: "2023-02-10T17:19:37Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:19:36.478Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:09Z"
  - containerID: docker://8bc929f05506f2f5ca702ff113eea0d1b84f4db2016c4b2bcb5e843ce5fb6e7d
    lastState: {}
    name: step-user-code
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://8bc929f05506f2f5ca702ff113eea0d1b84f4db2016c4b2bcb5e843ce5fb6e7d
        exitCode: 0
        finishedAt: "2023-02-10T17:18:49Z"
        message: '[{"key":"StartedAt","value":"2023-02-10T17:18:46.095Z","type":3}]'
        reason: Completed
        startedAt: "2023-02-10T17:18:08Z"
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - containerID: docker://afcf639aac8badfbeb0bf04e64f1b904db2ab9d68b9f5f0bce59672885d6f8a5
    lastState: {}
    name: prepare
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: docker://afcf639aac8badfbeb0bf04e64f1b904db2ab9d68b9f5f0bce59672885d6f8a5
        exitCode: 0
        finishedAt: "2023-02-10T17:18:04Z"
        reason: Completed
        startedAt: "2023-02-10T17:18:04Z"
  - containerID: docker://97783ec41d3e64e053d4615f8665b662b0d48610e8322188dfcb80371af5ec7a
    lastState: {}
    name: place-scripts
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: docker://97783ec41d3e64e053d4615f8665b662b0d48610e8322188dfcb80371af5ec7a
        exitCode: 0
        finishedAt: "2023-02-10T17:18:05Z"
        reason: Completed
        startedAt: "2023-02-10T17:18:05Z"
  message: 'Usage of EmptyDir volume "ws-49mb5" exceeds the limit "10Gi". '
  phase: Failed
  qosClass: Burstable
  reason: Evicted
  startTime: "2023-02-10T17:18:02Z"

It seems likehttps://github.com/tektoncd/pipeline/pull/5646 might handle this error case. Before DidTaskRunFail would check all the ContainerStatuses even if the pod.Status.Phase == corev1.PodFailed. Looking at the container statuses here it seems like #5646 would now cover this case where the eviction happens after the containers exit.

@drewbailey #5646 was merged and included in release v0.45.x - would you be able to verify if this issue could be closed then? Alternatively, would you be interested in designing a test for this case?


Create Diesel Generators encountered error during sided_setup event pahse

mc 1.20.1
forge 47.2.1
createdieselgenerators-1.20.1-1.2b
https://mclo.gs/L2cKWq5 - crash report.
another crash
(and no im not going to downgrade because 0.5.1.e of create fixes the deployers being broken and both my modpack and its officially hosted server need the fix.)

that's not an issue with 0.5.1e, I know what's the issue, wait a day or two when I release the next version


Travis Builds Are Failing Installing Rust

Due to a bug upstream in the way Travis is installing Rust (using Rustup.sh) without sudo, we currently have no working Travis builds.
This issue should track rust-lang/rustup.sh#72 and travis-ci/travis-ci#6654.

This has been fixed upstream, builds in #10 prove this is working again. 👍


Progressive download

Is there any way to make a progressive download to initiate video playing before the video is fully loaded? If not, I would like to issue a feature request. At this time I am using the code below, but the response object is not available until the download is complete.
NSMutableURLRequest *request = [[AFHTTPRequestSerializer serializer] multipartFormRequestWithMethod:@"POST" URLString:url parameters:nil constructingBodyWithBlock:^(id<AFMultipartFormData> formData) {

        [formData appendPartWithFormData:[pwd dataUsingEncoding:NSUTF8StringEncoding] name:@"password"];
        [formData appendPartWithFormData:[user_id dataUsingEncoding:NSUTF8StringEncoding] name:@"userid"];

} error:nil];

AFURLSessionManager *manager = [[AFURLSessionManager alloc] initWithSessionConfiguration:[NSURLSessionConfiguration defaultSessionConfiguration]];
manager.responseSerializer = [AFHTTPResponseSerializer serializer];

NSURLSessionUploadTask *uploadTask = [manager uploadTaskWithStreamedRequest:request progress:^(NSProgress * _Nonnull uploadProgress) {
    dispatch_async(dispatch_get_main_queue(), ^{
          NSLog(@"Fraction completed: %f", uploadProgress.fractionCompleted);
    });

} completionHandler:^(NSURLResponse * _Nonnull response, id  _Nullable responseObject, NSError * _Nullable error) {

// Here I save the responseObject to the drive and convert it to an AVPlayer asset for playing

}];
[uploadTask resume];

Streaming video is out of the scope of AFNetworking—you’d need to stream the response to something that plays video. For general help, please ask on StackOverflow.


⚠ Spryr has degraded performance

In 80a61c3, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3281 ms

Resolved: Spryr performance has improved in 75c2f3d after 9 minutes.


Refactor to adopt k8s standardized Condition type

Updates to use metav1.Condition type and removes references for
deprecated corev1.Condition* constants and uses the new k8s api/meta
helpers in place of the old pkg/apis/meta types.
Relates to fluxcd/flux2#225
NB: This will be a blocker for other components that depend on the source-controller. We'll need to release a new version of the source-controller before proceeding to update the other components that depend on it:

kustomize-controller
helm-controller
notification-controller
image-automation-controller

:warning: Your branch needs a rebase for the tests to start.

Your branch needs a rebase for the tests to start.

Yes, I'm working on that. Already did the suggested changes and I'm working to resolve the conflicts now :)

needs to be merged at a strategic moment.

Definitely. I'm going to continue with these changes in the other dependent controllers and submit draft PRs pointing the dependencies to pseudo-versions. After you decide when these changes will go out, they can be merged in order with minimal changes (version bumps for deps basically).


DMP-782: Implement streams for first phase of add audio flow to impro…

DMP-782
The existing POST /audios endpoint accepts a binary payload (audio) which is subsequently uploaded to the Inbound Datastore via the Azure Blob Client.
The existing implementation reads the full binary payload into memory at various stages in this flow, including:

When computing the checksum
When passing the BinaryData instance to the blob client's upload method.

This PR reworks that flow to favour streams, such that:

The checksum is computed as the stream is consumed, using DigestInputStream
The input stream is passed directly to the blob client

The blobClient will break the payload down into multiple pieces, and will initiate an API (upload) call to Azure for each piece. BlobClient will consume into memory the entire size of that piece, so we also configure BlobClient to limit the size of those pieces. Additional configuration parameters are exposed as Spring properties such that they can be tuned during performance testing. Current values are not expected to be final.
Testing
Behaviour between master branch and dmp-782-streams branch was compared locally.
An audio file - noise_large.mp2 - was generated with filesize of ~320MB, close to the 350MB max filesize supported by DARTS. Requests were made to POST /audios as follows to observe behaviour for such large files:
curl -v --request POST \
  --url http://localhost:4550/audios \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form 'file=@/Users/chrisbellingham/Music/noise_large.mp2;type=audio/mpeg' \
  --form 'metadata={"started_at":"2023-11-23T10:36:05.362Z","ended_at":"2023-11-23T10:36:05.362Z","channel":1,"total_channels":4,"format":"mp2","filename":"filename_goes_here","courthouse":"SWANSEA","courtroom":1,"media_file":"media_file_goes_here","file_size":100,"checksum":null,"cases":[1]};type=application/json'

JVM was configured to set fixed values for Max and Initial heap (-Xmx1024m -Xms1024m) to give a stable basis for comparison.
Existing master branch
Request fails with:
Caused by: java.lang.OutOfMemoryError: Java heap space

dmp-782-streams branch
Request succeeds after ~3 mins. File is present within the Inbound container in Azure, and an external_object_directory record is created with the expected checksum value.
To test how the memory usage scales with concurrency, two requests were made ~1 minute apart:

Garbage collection was manually triggered aggressively during upload to obtain an accurate view of actual usage (blue line). From delta between requests, the memory cost of a single request is ~70MB for a 320MB request payload.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Adding this for traceability. I keep losing the link :). See file-size-threshold
https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/web/servlet/MultipartProperties.html


Expose LibCrypt PKCS5_PBKDF2_HMAC

Issue Kind: Feature Request
Please add the binding to libcrypt's PKCS5_PBKDF2_HMAC method
Documented on https://www.openssl.org/docs/man1.1.0/crypto/PKCS5_PBKDF2_HMAC_SHA1.html

It seems the pull request #5021 is related to this


Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install

When I try to install the requirements.txt i get this error. Does anyone know how to solve it?

Please can you paste in the full "Complete output from command python setup.py egg_info:" of the error?

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-owbpps6e/l18n/

There was a guy who had an issue with the same command error, but he said he fixed it by editing the requirements/production.txt file. He removed the uwsgi from the file. So I tried to do the same, but still received the error.

Is there really nothing else displayed, other than that one line?

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-owbpps6e/l18n/

Here is what is displayed from when its attempting to collect the l18n
Collecting l18n (from wagtail<2.2,>=2.1->-r base.txt (line 7))
Using cached https://files.pythonhosted.org/packages/1d/a9/c514038919f430a9b748e31be06e3b365b1e4a4c1aa04b3990a9870df38d/l18n-2016.6.4.zip
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-owbpps6e/l18n/setup.py", line 99, in
long_description=open(os.path.join('README.rst')).read(),
File "/home/admin/.virtualenvs/wagtailbakerydemo/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2135: ordinal not in range(128)
----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-owbpps6e/l18n/

This is a known issue with the "l18n" package - please see https://groups.google.com/d/msg/wagtail/X5d8CL3DxUs/XPcMUrrYBQAJ for the fix.

Is the fix inside the google discusion or the gitHub link?

I'm sorry i'm kind of new at this. I can't quite find what I need to do to get rid of that error.

Try running the command:
export LC_ALL=en_US.UTF-8

I get export
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

Afraid I can't help further, as this is an issue with the l18n package and your operating system rather than an issue with Wagtail - I'd suggest using one of the alternative installation methods listed in https://github.com/wagtail/bakerydemo#installation.

Hey man, thank you so much! I finally got that little snippet of code to not produce an error, and it worked! My step dad who is a professional app developer and uses linux as his base computer, has been trying to help me with this problem for over 6 hours, but he thought it was my build. Since i'm running crouton inside of ChromeOS. Well thank you so much man!


Pull images before using them for CSCS CI pipeline

Since there are many test jobs using the same image, and all of them are starting at the same time, there is a high chance that the same image will be pulled several times.
While this gives correct results it is suboptimal since we download the same layers and squash them multiple times.
It is better to pull the image before using it, therefore I added a pull stage, which does exactly that.

Already fixed by locking the image pull in the runner.


fix: Fix Path Resolution in process_log_dir_replacements Function

Summary
This PR closes #278. It addresses an issue with the process_log_dir_replacements function, which is responsible for replacing the $pwd placeholder in log directory paths with the path to the Kai project directory. The original function returned paths with redundant components and did not correctly resolve relative paths.
Issue
The original function produced paths with incorrect or redundant components, such as /home/k8smaster/Desktop/kai/kai/..//logs, leading to errors and misconfiguration in the log directory paths.
Changes Made
Function Update: Updated the process_log_dir_replacements function to:
Replace $pwd with the path to the Kai project directory, one level up from the current working directory.
Normalize the resulting path to remove redundant components and resolve relative path issues.
def process_log_dir_replacements(log_dir: str) -> str:
    ##
    # We want to replace $pwd with the location of the Kai project directory,
    # this is needed to help with specifying from configuration
    ##
    if log_dir.startswith("$pwd"):
        current_directory = os.getcwd()
        kai_project_directory = os.path.abspath(os.path.join(current_directory, ".."))
        log_dir = log_dir.replace("$pwd", kai_project_directory, 1)
        log_dir = os.path.normpath(log_dir)
    return log_dir

Thank you for your contribution.
Before we consider merging, I would like to know if you ran into functional errors that necessitated this PR or if this was more of a stylistic concern to clean up how the path was displayed.  Let's discuss in #278

@brf153 do you want to include in this PR the test you shared in
https://github.com/konveyor/kai/issues/278#issuecomment-2269552260

Thank you so much, @jwmatthews ! I'm really glad the test example helped clarify things.
Regarding the test you mentioned from #278, I've actually set up a separate branch just for tests. I'd prefer to add the tests from that branch if that's alright with you. Please let me know if that works.

Works for me

We will need to make a small change before we can merge this; as of now, the log directory is being created 1 lever higher in the hierarchy than we want.
I tested this via make run-server, executed that while being in the kai checkout.
The log file ended up being written a level up than expected.
My kai checkout is at:
/Users/jmatthews/git/konveyor/kai
I ran make run-server being in: /Users/jmatthews/git/konveyor/kai
The logging file is not created under the 'konveyor/kai/logs' directory as expected, but is created at 'konveyor/logs'.
Example from console logging output:
File logging for 'kai' is set to level 'DEBUG' writing to file: '/Users/jmatthews/git/konveyor/logs/kai_server.log'
I also tried with something a little odder just to verify behavior.
I changed directory to /Users/jmatthews/git/konveyor
then ran:  make -f ./kai/Makefile run-server
Confirmed the log directory is again going a level higher in heirarchy than expected
File logging for 'kai' is set to level 'DEBUG' writing to file: '/Users/jmatthews/git/logs/kai_server.log'
I made the below tweak to correct this
$ git diff kai/kai_logging.py
diff --git a/kai/kai_logging.py b/kai/kai_logging.py
index cc274f9..2b79d0e 100644
--- a/kai/kai_logging.py
+++ b/kai/kai_logging.py
@@ -18,7 +18,7 @@ def process_log_dir_replacements(log_dir: str) -> str:
     ##
     if log_dir.startswith("$pwd"):
         current_directory = os.getcwd()
-        kai_project_directory = os.path.abspath(os.path.join(current_directory, ".."))
+        kai_project_directory = os.path.abspath(current_directory)
         log_dir = log_dir.replace("$pwd", kai_project_directory, 1)
         log_dir = os.path.normpath(log_dir)
     return log_dir

Tested with podman compose to confirm logging to disk is still OK with the above tweak and looks good
File logging for 'kai' is set to level 'DEBUG' writing to file: '/podman_compose/logs/kai_server.log'

@jwmatthews made the required changes


[commands][check_googlefonts] Remove runner_factory

This partial function is not called by any other module/script so we can remove it

looks good to me but I'd ask @graphicore first.

I think I was trying to document some possible usage but screwed the documenting part ;-) Can be merged.

thanks!

Just figured, this out. This is used by the Font Bakery - Dashboard. Please bring it back!

Place at least a comment there so that we don't forget about it next time :-)


How to train/fine tuning the model

is possible a few steps to fine tuning and add more entities to the model?
Thanks

Is there any word on this issue? I would like to further train the model as well.


Add option to specify default plugin options (closes #11)

As outlined in #11, it would be useful to be able to provide default options for plugins.
This implements that. I couldn't see any good way to merge non-object options, such as arrays - it's unclear whether it's meant to override or merge them when this is the case.

Coverage remained the same at 100.0% when pulling 2e3920eef172f0922ce5b9e6b2386d39a2aa3b24 on sanity-io:default-plugin-options into abe815d6dee0004e6d8e924a8ad68285a7e77a00 on postcss:master.

Sorry, I didn't test this under Node 0.12. Added some code to work around Object.assign not being present there.

Coverage remained the same at 100.0% when pulling 0f4e97f4de354f55b9e6c3f84d4a09767448a801 on sanity-io:default-plugin-options into abe815d6dee0004e6d8e924a8ad68285a7e77a00 on postcss:master.

Coverage remained the same at 100.0% when pulling 0f4e97f4de354f55b9e6c3f84d4a09767448a801 on sanity-io:default-plugin-options into abe815d6dee0004e6d8e924a8ad68285a7e77a00 on postcss:master.

Hi @rexxars, thanks for the pull request!
Do we need the isPlainObject checking? Any time that I've been using options objects, it's always been obvious that we should supply a plain object, that is pretty much a standard pattern across most if not all JS modules.
Also, I think it would be nice if you could remove the polyfill and let Babel polyfill it for 0.12, via object spread. So we can get rid of a lot of code by swapping out;
return assign({}, defaultOpts, specifiedOpts);

with
return {
  ...defaultOpts,
  ...specifiedOpts,
};

Also, defaultPluginOptions is a little verbose. Perhaps simply options is a better name for this?

Thanks for the feedback, @ben-eb
The reason why I added the object check was that there is already handling of non-object options in the codebase (postcss-discard-font-face can receive an array, for instance). Be happy to remove it if you think it's not necessary.
Updated PR based on your feedback, awaiting reply regarding object check.

Coverage remained the same at 100.0% when pulling 1ec5f1489f2af9241da4a179c58e1f12da591be3 on sanity-io:default-plugin-options into 74d8f52939ea41740a7609502c296338cfd1aeb8 on postcss:master.

Ah, OK. That makes sense to me. 👍

Merged and released on npm in v2.3.0. Thanks again! 🎉


Python: Publish PySparkler to PyPI in Release Workflow.

Publish PySparkler to PyPI in Release Workflow. Need @holdenk to add PYSPARKLER_PYPI_API_TOKEN as a repo secret so that GitHub Action is authorized to publish PySparkler to PyPI.

Oh fancy, I like this. Let me generate a token tomorrow 👍

Oh fancy, I like this. Let me generate a token tomorrow 👍

Thanks! I have got the project API token, just didn't have the permissions to add a repo secret. I'll DM you the token tomorrow so you can add it.


[Help wanted] Fix search for "Upgrade"

Search for "Upgrade" and upgrade page doesn't appear. Need to find out why, and later write out some criteria so it is easier to find regressions in search

There seems to be a lot of issues with searching. Results are unsorted, seem to miss searching titles, missing entries that clearly include the search term (like the above "upgrade").
Since docs are built on the sphinx_rtd_theme theme I'll take a look there and see if there is anything obvious, but a quick snoop on the "upgrade" term clearly has matching results in the generated index.

Fixed by #745, thanks @shieldsjared!!


Update license field following SPDX 2.1 license expression standard

The new recommendation is to follow the SPDX 2.1 standard. This allows automatic license verification software to work properly. Reference: https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields

Codecov Report
Patch coverage has no change and project coverage change: -0.09 :warning:

Comparison is base (9b61712) 37.41% compared to head (c9bb2f7) 37.32%.

: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     #310      +/-   ##
==========================================
- Coverage   37.41%   37.32%   -0.09%
==========================================
  Files          94       94
  Lines        6204     6189      -15
==========================================
- Hits         2321     2310      -11
+ Misses       3883     3879       -4

see 64 files 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.


Where do you put the API key when using expo?

Question
Im assumming its somewhere in app.json but I cant be sure.

same issue. please help

https://docs.expo.io/versions/latest/sdk/map-view/#deploying-to-a-standalone-app-on-android

In app.json, copy the API key from android.config.googleSignIn to android.config.googleMaps.apiKey.

Example diff:
https://github.com/brentvatne/growler-prowler/commit/3496e69b14adb21eb2025ef9e0719c2edbef2aa2

@christopherdro  thank you Bro

I know this is recommended by the expo docs, but doesn't it feel wrong to commit this?

@WillSmithTE - it does feel wrong! trying to make this decision now

I know this is recommended by the expo docs, but doesn't it feel wrong to commit this?

Hello, did you find another solution?

With app.config.js or app.config.ts you can use something like :
android: {
      ....
      config: {
        googleMaps: {
          apiKey: process.env.GOOGLEMAPS_APIKEY,
        },
      },
    },

And define GOOGLEMAPS_APIKEY via command line on via eas secret


Venv creation via rustpython -m venv get stuck

Branch: main (21615cb15898f85f7c8b93253c0faf2ba07c8b2b)
Build via: cargo build --features=ssl
Environment: uname -a
Linux ankit 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
rustc  -V
rustc 1.68.0 (2c8cc3432 2023-03-06)
cargo -V
cargo 1.68.0 (115f34552 2023-02-26)
Command:
target/debug/rustpython -m venv venv
Issue: Above command gets stuck
Ctrl+C raise interrupt at
File "/home/ankit/RustPython/pylib/Lib/subprocess.py", line 504, in run
stdout, stderr = process.communicate(input, timeout=timeout)
KeyboardInterrupt

Do note that this appears to be a debug only issue. Running with a release build does not hang.

Thanks for looking into this.

Do note that this appears to be a debug only issue. Running with a release build does not hang.
Yes, you are right. Working fine with release build.


TK82665AKSRVWTSGCNIDWTIOUTVMEXERR

Reviewing the article in detail to identify if any changes are needed. Tasks by Rekha Nain (v-rekhanain).
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

@azmmft I made editorial changes to this PR. Could you check if the current changes are technically accuracy? Note that since you add an additional error code, I also changed the article title.


Fix issue reading message and set max price to the real max price

What does this PR do?
Fix issue reading message from LMS
What issues does this PR fix or reference?
#
The PR fulfills these requirements:
[] Tests for the proposed changes have been added/updated. N/A as it's aura.
[x] Code linting and formatting was performed.
Functionality Before
Leaflet map was not working correctly
Functionality After
Leaflet map works correctly

@albarivas don't you want to apply the fix on master directly?


et script does not support ipv6 host names

I would expect to be able to use ipv6
$ et user@[abcd:abcd:abced:...]:port

But after looking at et script it looks like ET_COMMAND_REGEX does not permit this form

Hey, this should be fixed in 4.1.0.  Feel free to comment if it isn't and I'll reopen


Fix for Issue: #1621 - Reading Excel HTML files will misalign cells in some cases

Updated bits/79_html.js per SheetJSDev's comments (https://github.com/SheetJS/sheetjs/issues/1621#issuecomment-531007036), added a test case and verified with the SheetJS test files that no other tests failed.
Closes #1621

@SheetJSDev Do I need to worry about this or is my work here done?

@SheetJSDev is there something more needed for this pull request?

b3793e2ea7ee6a6726e619373b1c287819fe7e2e


[Snyk] Upgrade react-native-safe-area-context from 4.4.1 to 4.7.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade react-native-safe-area-context from 4.4.1 to 4.7.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 14 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-09-01.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462
632/1000  Why? Currently trending on Twitter, Recently disclosed, CVSS 9.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: react-native-safe-area-context

4.7.2 - 2023-09-014.7.2 (2023-09-01)

Complete the partial memoization of provider (#427)

4.7.1 - 2023-07-114.7.1 (2023-07-11)

Update podspec to tvOS 12.4 (#415)

4.7.0 - 2023-07-104.7.0 (2023-07-10)
Bug Fixes

use install_modules_dependencies to make fabric build more reliable (664c518)
use RCT_NEW_ARCH_ENABLED in RNCSafeAreaContext module (720cbc9)
Fixes for tvOS (#412)

4.6.4 - 2023-07-044.6.4 (2023-07-04)

Update safe area frame when keyboard shows/hides (#407)

4.6.3 - 2023-06-214.6.3 (2023-06-21)
Bug Fixes

make edge types readonly (def6c1f)

4.6.2 - 2023-06-214.6.2 (2023-06-21)

Cast View to the NativeSafeAreaViewInstance for .macos and .windows to get the correct type definitions (#404)

4.6.1 - 2023-06-214.6.1 (2023-06-21)
Bug Fixes

Fix type declaration path in package.json (#400) (ce5e856)

4.6.0 - 2023-06-204.6.0 (2023-06-20)
Features

maximum padding (#394)
set namespace in build.gradle (#399)

Bug Fixes

allow providing insets in hook mocks (f1d9e52)

4.5.5 - 2023-06-21

4.5.4 - 2023-06-20

4.5.3 - 2023-05-164.5.3 (2023-05-16)

4.5.2 - 2023-04-294.5.2 (2023-04-29)
Bug Fixes
Allow web's SafeAreaView to forward ref to its underlying view #383

4.5.1 - 2023-04-08

4.5.0 - 2023-01-19

4.4.1 - 2022-09-28

    from react-native-safe-area-context GitHub release notes

Commit messages

Package name: react-native-safe-area-context

c862c86 Complete the partial memoization of provider (#427)
930f703 chore: release 4.7.1
aeaa21b Update podspec to tvOS 12.4 (#415)
55d384d chore: release 4.7.0
1b23b4f Fixes for tvOS (#412)
b683c52 chore: don't run yarn test on prepublish
9535676 chore: bump gradle in /android
13f02cb chore: fix ci
eb55cc7 chore: update rn to 0.72.1
720cbc9 fix: use RCT_NEW_ARCH_ENABLED in RNCSafeAreaContext module
664c518 fix: use install_modules_dependencies to make fabric build more reliable
c70c8c5 chore: release 4.6.4
fd2b02f Update safe area frame when keyboard shows/hides (#407)
8c1d811 chore: release 4.6.3
7ed701b fix: ts
def6c1f fix: make edge types readonly
2243c3e chore: release 4.6.2
7458d38 Cast View to the NativeSafeAreaViewInstance for .macos and .windows to get the correct type definitions (#404)
016b962 chore: release 4.6.1
ce5e856 fix(minor): type declaration path in package.json (#400)
b8b1e8e chore: release 4.6.0
219e700 fix: add missing files
5f5311b chore: add spotless and reorg format scripts
e808572 fix: tests + minor improvements

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sorry i think i created these by accident.


error: cannot infer contextual base in reference to member 'automatic'

The example works perfectly but in my app, this error comes up when trying to run the app:
SwiftFlutterSocialContentSharePlugin.swift:115:37: error: cannot infer contextual base in reference to member 'automatic'
                    shareDialog.mode = .automatic
                                       ~^~~~~~~~~

Version: 1.0.2
iOS Simulator version: 15.0
Flutter doctor -v output:
[✓] Flutter (Channel stable, 2.5.3, on macOS 12.0.1 21A559 darwin-arm, locale en-US)
    • Flutter version 2.5.3 at /Users/nabeelparkar/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (6 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-31, build-tools 31.0.0
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /opt/homebrew/opt/openjdk@11/bin/java
    • Java version OpenJDK Runtime Environment Homebrew (build 11.0.12+0)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.1, Build version 13A1030d
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2021.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 62.0.3
    • Dart plugin version 212.5632

[✓] VS Code (version 1.62.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (2 available)
    • iPhone 8 (mobile) • 57F977B3-B55C-49DB-ABC7-045BEC2C778F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • Chrome (web)      • chrome                               • web-javascript • Google Chrome 96.0.4664.55

! Doctor found issues in 1 category.

Hey were you able to resolve this?

Having the same issue here. Very weird, my Flutter app won't build anymore because of this. Investigating further..

Cleaning the build folder, flutter clean and restarting my mac fixed the issue for me after I ran "flutter clean" and "flutter build ios" My last step was to delete and recreate the /ios folder but I didn't need to.

change "fromViewController" to "viewController" in
.pub-cache/hosted/pub.dartlang.org/flutter_social_content_share-1.0.2/ios/Classes/SwiftFlutterSocialContentSharePlugin.swift:110:46:


fix(client): extension types with mocking library

closes https://github.com/prisma/prisma/issues/21136
/integration

Keen for this!

About the ecosystem-tests:
https://github.com/prisma/ecosystem-tests/actions/runs/6344577190/job/17254939099
Only the driver adapters jobs failed but I guess that’s expected for now though we need to do something about that soon


"ZoomTo" action?

The zooming in/out on the UI works great, but for me the "perfect" zoom level would be somewhere between the 1st and 2nd zoom. I wondered if a ZoomTo action (or some other public api) with input parameter could be added, so that extensions such as vscode-zoom could set a more precise zoom level.

@bpasero will know but I believe the zoom states are given by electron/chromium and that there is no 1.5 level

@stkb yeah the zoom action is only going up and down by an increment of 1. fair request.

This will be possible with the newly introduced and persisted window.zoomLevel setting.

:thumbsup: Thanks!


Speeds up Android by avoiding event loop cycling with TextInput usage.

This is obviously a bit of a strawman to start a discussion.
With this change, TextInput._onChange can be called and update _lastNativeText properly.
Without this change, it doesn't get updated. Which leaves the next componentDidUpdate to call setNativeProps({text:...}) again unnecessarily, which (I believe) is triggering a re-layout, and triggering componentDidUpdate, leading to this cycling in the event loop that makes the Android app slower for me.
The question is, why don't we want the callbacks called when we update the text from JS? Because that's exactly what TextInput._onChange is expecting.
I'm a bit unclear why calling setNativeProps({text:...}) triggers another call to componentDidUpdate. I did a bunch of tracing and debugging and have a skeleton of who-calls-what I can share, if you're interested. But I'm pretty clueless on the layout logic stuff and suspect it's related to that somehow.

By analyzing the blame information on this pull request, we identified @rigdern and @janicduplessis to be potential reviewers.

@mikelambert did you have anyone in mind to discuss this? Would opening an issue be a better venue for that discussion? Ideally we'd use the PR to review the proposed change.

I spent hours digging into this to come up with this solution that I actually believe is the correct solution, from my understanding of how everything works. I actually built react native and tested that this avoids the cycling. I don't know who to discuss this with, since I'm not close with the react-native team.
No one really responds to Issues from my experience, and they just closed and pushed off to Product Pains. Which is why I wanted to submit my proposed fix. Which is also the actual fix I have deployed to production in my app successfully. And reduces my Android CPU usage significantly.
My hunch from when I debugged this two months ago, is that the TextInput JS API may have been designed with iOS in mind, and unintentionally results in event loop cycling (ie infinite loops) on Android.

So this pull request is basically just turning off the mIsSettingTextFromJS flag entirely, right? You are commenting it out in one place but that seems like it will just stop having its effect.
From higher in the file:
  // This flag is set to true when we set the text of the EditText explicitly. In that case, no
  // *TextChanged events should be triggered. This is less expensive than removing the text
  // listeners and adding them back again after the text change is completed.

So to me it sounds like, the goal is to not trigger these events when we are explicitly setting text, and the current behavior is working as intended.


Added Painting Game

Title and Issue number

IN this website user can draw whatever he want with different shapes and color.
Close #2586

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@pranjay-poddar @TusharKesarwani  Sir I am writing to kindly request your attention and consideration in reviewing and merging this pull request. I would greatly appreciate it if you could allocate some time to review the \pull request and provide your feedback. If there are any areas that require further attention or modifications, please let me know, and I will be more than willing to address them promptly.
Thank You


Improve loading UI when importing a namespace

Current behaviour

Expected behaviour
Perhaps hiding the inputs when the spinner is shown? To be discussed

Updated: https://github.com/cortezaproject/corteza/commit/c997655b961965ee607907c54fd68ba10686fcbd


Version 23.0 does not respect the Disabled setting in the KtLint settings

With the plugin disabled (at the Intellij disabling plugin level) and default IntelliJ formatting this code is not adjusted when you run IntelliJ autoformatting:
data class Hiya(val foo: String)

With the plugin enabled (at IntelliJ level), but configured as disabled under the KtLint setting, the code IS reformatted as:
data class Hiya(
    val foo: String,
)

The plugin DOES seem to respect not running on save when in disabled mode.
In order to get the plugin the stop reformatting things while in Disabled mode you have to first change it to Manual mode and uncheck the "attach to IntelliJ IDEA formatting" option (an option which is not visible in Disabled mode).

Good find! Tnx for reporting the reproduction path which was very helpful in solving the issue. Solved in https://github.com/nbadal/ktlint-intellij-plugin/commit/c202e99b54d288098f3c9df3a574a0a38dd086ad. See latest version on https://plugins.jetbrains.com/plugin/15057-ktlint/versions/dev

Ty @paul-dingemans! It's now working as expected.


Invalid values for --no-squeezing should print an error.

Any value provided to --no-squeezing using the --long=value argument format is treated as true.
This means that --no-squeezing=false and --no-squeezing=default will disable squeezing, which might come as a surprise to someone who was expecting those values to retain the default behavior.
It's not likely to happen to an everyday user, but it can happen when writing scripts. In my case, it was while writing a test harness.

Note: I'm doing a class assignment regarding creating tests (from scratch) for an open-source command line program, and I chose hexyl for it. You might have a couple more of these on the way, depending on what the assignment brings to light :)

Oh, I didn't even know that clap would allow this as valid command line syntax. --no-sequeezing does not take an argument.

Oh, I didn't even know that clap would allow this as valid command line syntax. --no-sequeezing does not take an argument.

Fun quirks of many argument parsers: if it doesn't take a value, you can sometimes force it to take one. As for what clap does with it... I guess it either truncates it or saves the value anyways?
A way to improve handling of it could be by checking if the forced value can be parsed as a bool, and using that as the value. If not and it's empty, use true. Otherwise, print an error?
Or simply just printing an error for any nonempty value would work, too.

Fun quirks of many argument parsers: if it doesn't take a value, you can sometimes force it to take one

Indeed. Seems like a known issue: https://github.com/clap-rs/clap/issues/1543

A way to improve handling of it could be by checking if the forced value can be parsed as a bool, and using that as the value. If not and it's empty, use true. Otherwise, print an error?

I'd prefer not to add any special handling for this. The documentation clearly says that this option does not take a value. The fact that clap allows this is weird, but not critical IMO. We also wouldn't want to add code to make sure that hexyl --help=no is disallowed.

We also wouldn't want to add code to make sure that hexyl --help=no is disallowed.

That is an extremely good point. And if it isn't an intentional behavior in clap, then let's just leave it up to be fixed by a clap future update. I'll close this issue.


RangeBar Displays Wrong Time Values on X-Axis

Thanks for your work on this library :) Keep up the good work!
Bug report
RangeBar Displays Wrong Time Values on X-Axis
Codepen
https://codepen.io/GariSincere/pen/ZEbMKPJ
Explanation
What is the behavior you expect?
The x-axis should line up with the tooltip and the JSON of the datapoints
What is happening instead?
The x-axis is intermittently off by 1 hour and disagrees with the tooltip (which is lining up with actual data points)

The issue seems to be related to the plot range.  As you can see from the code pen, after one of the series is hidden the plot range changes, and the axis labels are then correct. Sometimes adding data points that extend the plot range will also set it back on track.
It might be related to #1601 and is distinct from #1485 since it is not reflective of timezones and is consistently off in safari vs non-safari.
Currently, I can't find any way to work around this issue :/ If manual tick options were added as suggested in #1590 I could work around this issue until it is solved.

working with UTC  will solve it !
data :
[
{ x: 'Ma', y: [   Date.UTC(2019, 2, 7, 10, 20, 0) ,  Date.UTC(2019,2,7, 22, 0, 0) ] },
...
formatter: function (x)
{
let oDate = new Date(x);
console.log(x);
return '' +  zeroPad(  oDate.getUTCHours() , 2 ) + ':'  + zeroPad( oDate.getMinutes(), 2 );
                                                             }

@junedchhipa for him to see the progress.
Yes, thank you @aswincoolsaet that is progress!  I updated the code pen to have a third chart that uses the UTC formatter.  Now at least the axis is agreeing with the data, but a new issue is now the axis ticks are irregular and displaying poorly (the last one is cut off).  I guess that is a side product of using manual formatter?  I have tried to tweak the formatter settings but can't seem to improve it.

ah I understand.
I don't have much time this evening to try out, but try here something with UTC option to turn it off
https://apexcharts.com/docs/options/xaxis/

Can you try to use      Date.UTC(2019, 2, 7, 10, 20, 0)
instead of  new Date( ... )  ?

Yes, I used that function at first but found that the outcomes were equivalent in the example case I currently have in the code pen.

y: [
        Date.UTC(2020,4,14,1), //  ("Thursday, May 14, 2020 1:00:00 AM GMT").getTime()
         Date.UTC(2020,4,14,3) //new Date("Thursday, May 14, 2020 3:00:00 AM GMT").getTime()
      ]

&&&
xaxis: {
labels: {
datetimeUTC: false,
},
type: 'datetime'
does it for me in your codepen.

YES is see what you mean.  It looks like using  Date.UTC() create function and xaxis.labels.datetimeUTC : false is the secret sauce.  The formatter function is not necessary and was causing those display issues.

I'm still curious on what was going wrong :/ I bet it has something to do with daylight savings time conversions (since the difference was typically 1 hour).
Regardless it's GREAT to have this workaround in the meantime.

ok I had more time to test now.
for instance :     9:30 - 10:00
datetimeUTC: false,   will fix the wrong offset with new Date( .. )
and the label can be fixed by the formatter function where you can use getUTCHours
so the only issue I still have is a little bit wrong "offset" on the x-as.

I have the same issue. It seems that it has to do with the day change in combination of non-UTC.
The missing piece is the x-axis label for the new day, which might not consider timezones correctly - it is missing and so the x-axis is delayed by one element from that.
Here I'm at UTC+2:00 (at summer time, Europe/Berlin). The problem occurs only when i select a start date between 22:01 and 22:59, then the x-axis item for day is missing. When starting <= 22:00 or >= 23:00 it is working fine.

The original issue is fixed as tested on v4.3.0


[Feature Request] Add delay before switching off WiFi

Whenever I loose the connection for a few seconds even though I'm still in range, WiFi is switched off. So a delay, maybe adjustable, would be nice.

Yeah, it is absolute necessary. Smarter Wifi app is a good example.


Storage account module

Is there any difference in "storage accounts" between all these different use cases? This seems like a very generic bundle without much expertise encoded into it. Would it make sense to have "storage-account-blob", "storage-account-file", "storage-account-queue", etc. modules?

Is there any difference in "storage accounts" between all these different use cases? This seems like a very generic bundle without much expertise encoded into it. Would it make sense to have "storage-account-blob", "storage-account-file", "storage-account-queue", etc. modules?

No, mainly because the difference between a blob, files, queues, etc. are so minimal. They could be the same bundle, build beginning to end, but the intent is different. A queue bundle has a specific purpose, and therefore a specific artifact. If we had a queue module and a queue bundle, the bundle itself would just be the module with no changes.


[docs] Better definition of what withStyles is

Closes #9226.

No activity for 15 days. I think this change is going in the right direction. I'm going to merge @ajay2507 pull-request. Thank you.
@rosskevin, @pelotom you are free to keep iterating on the topic :).

@oliviertassinari It was on hold because changing it in this one place makes it inconsistent with the rest of the docs and code comments: https://github.com/mui-org/material-ui/issues/9226#issuecomment-346187847
Should we reopen that issue, or open a new one?

rest of the docs and code comments

@mbrookes Oh, I was dodging the inconsistency by using withStyles for the factory and withStyles() for the higher-order Component. Maybe we can find better. @mbrookes If you think we can do better, sure!

@oliviertassinari I'll have to re-read the relevents docs with that in mind. I hadn't considered it.


Better snapshot serialiser.

When JSON is written, some fields will be lost, which are reported as missing on the snapshot test when the actual data has not yet lost them. Do JSON.parse(JSON.stringify(res)) before comparing to the snapshot.

[ ] handle errors when cannot parse snapshot


Ensure cmd from fuzz buffer is always valid

The quic-srtm fuzzer uses a loop in which an integer command is extracted from the fuzzer buffer input to determine the action to take, switching on the values between 0 and 3, and ignoring all other commands.  Howver in the failing fuzzer test case here: https://oss-fuzz.com/testcase-detail/5618331942977536
The buffer provided shows a large number of 0 values (indicating an SRTM add command), and almost no 1, 2, or 3 values.  As such, the fuzzer only truly exercises the srtm add path, which has the side effect of growing the SRTM hash table unboundedly, leading to a timeout when 10 entries need to be iterated over when the hashtable doall command is executed.
Fix this by ensuring that the command is always valid, and reasonably distributed among all the operations with some modulo math.
Introducing this change bounds the hash table size in the reproducer test case to less than half of the initially observed size, and avoids the timeout.
Fixes openssl/project#679

I don't see how this fixes anything. As far as I can see, it can still generate as many add commands as it wants. And the other values seem to be ignored anyway.

See #24831 where a similar issue in the lcidm is addressed in a different way.

This pull request is ready to merge

merged


go for modules

Codecov Report

Merging #65 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #65   +/-   ##
=======================================
  Coverage   80.78%   80.78%
=======================================
  Files          52       52
  Lines         947      947
=======================================
  Hits          765      765
  Misses        139      139
  Partials       43       43

Impacted Files
Coverage Δ

config/config.go
80% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


How to reduce the size of .mgbmp file ?

How to reduse the size of .mgbmp file ? RemoveKey only remove key from idx and mark the storageitem in *.mgbmp as deleted.
But the file size has not decreased.
Is  there anyway to  remove storageitem from raptordb??

The bitmap index has an Optimize() method which is currently only being used by the hOOt full text index, I will add this to all other indexes.
No you can't remove a StorageItem as it is by design, if you are working with transient data use the high frequency storage instead.
Thanks.

The bitmap index has an Optimize() method which is currently only being used by the hOOt full text index, I will add this to all other indexes.
No you can't remove a StorageItem as it is by design, if you are working with transient data use the high frequency storage instead.
Thanks.

After the system has been running for a while, the size of the .mgbm file is increasing (currently 7G). I need to periodically delete the old data to reduce the disk space.
But the most recent data needs to be retained. Is there any other way?

Ah! Interesting.
Can you answer a few questions for me:

How many items are in your view?
Can you post a "dir" of the view folder contents (with the 7gb index)?
How big is the docs folder?


fix: paths work correctly on windows

Where is the fix? It appears this PR only changes the README.md.

Where is the fix? It appears this PR only changes the README.md.

The fix is here https://github.com/codecov/uploader/commit/186f7317a870f929405fcd63273a052c10a16d1e
Due to some bad timing , it triggered a release that didn't mention the fix. This is a README change so I had a release that mentioned the fix.
The confusing release was https://github.com/codecov/uploader/releases/tag/v0.1.0_4399

It looks like 186f731 contains a fix related to POSIX paths instead of Windows.
Was there a previous issue with paths not working correctly in one of the two OS environments?

It looks like 186f731 contains a fix related to POSIX paths instead of Windows.
Was there a previous issue with paths not working correctly in one of the two OS environments?

Yes, on Windows the files were being listed at their pull path, including the drive letter, which caused them to not match the files in coverage reports. By telling path to always use posix form, the file paths are now the same cross-platform. Prior to this fix, uploads on Windows would upload, but fail to process.


LiveKit dependency connection produces runtime error in project generated by Tuist

The original issue was posted on tuist issues, but maybe someone faced the same problems or had experience with it. Will be very appreciative to have help.
What happened?
LiveKit provides SwiftSDK for integration to the iOS applications. SwiftUI demo project  works perfectly with SPM. My goal is to use the SwifUI demo in our project generated with Tuist.
I've created a new target and connected dependencies as I've done for all other targets (our app has many targets and dependencies, connection process was clear). As a demo, I use the same code from the demo project.
The application is launching without any issues. When LiveKit establishes a connection it crashes with “unrecognized selector sent to instance…” (check Error log section)
How do we reproduce it?
Tuist demo project :
LiveKitTuist.zip
Download and gererate project with Tuist:

cd LiveKitTuist
tuist fetch
tuist generate

To be sure, it's tusit generation issue I have same project with same structure with clean SPM:
LiveKitXcode.zip
Download and open LiveKitXcode.xcodeproj
As demo credentials for both projects use:
url: wss://livekit.stg.globekeeper.com
token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2OTI4MDAzMzUsImlzcyI6IldSazNUTnZUMjl3OTJRVmZjR0xIVEVsaHp0bGxnWUVlRmJSaXRrTSIsIm5hbWUiOiJ1c2VyMSIsIm5iZiI6MTY5MjcxMzkzNSwic3ViIjoidXNlcjEiLCJ2aWRlbyI6eyJyb29tIjoibXktZmlyc3Qtcm9vbSIsInJvb21Kb2luIjp0cnVlfX0.T1eEavbaVtd1ApskFV3U1pttpJE9fH6A6-cIi-7ooOg

PS: Token expires every 24 hours. I'm going to edit every day.
Error log
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[LiveKit.LocalParticipant addDelegate:]: unrecognized selector sent to instance 0x6000007a9810'

macOS version
13.5.1
Tuist version
3.17.0
Xcode version
Version 14.3.1 (14E300c)

 settings: Settings.settings(         base: SettingsDictionary()             .merging([                 "OTHER_LDFLAGS": "-ObjC"             ]),         defaultSettings: .recommended     ),
Try this code, for me it resolve this same issue.


Made tools.mk ignore unknown functions in dialyzer

Added as a separate phase in the dialyzer output clean so it should be trivial to port to other repos, or to remove once this one is dialyzer clean w.r.t unknowns.
Example of what this does to the warning list: https://gist.github.com/aberghage/a977707dfd5b072e2723

Still curious why the other repos don't need this.  (shrug)

Not sure if ignoring all the the unknowns outright is correct here -- may be fine for riak_search, but is not general enough for other repos.  Should probably grep them out and alter return code.  Thoughts, @jonmeredith?

I'm not totally sure why the other repos don't need it either, maybe I'm missing some subtlety of one of the existing regexes (but I didn't spot anything that'd filter these). I'll take another look in the light of day tomorrow.

for riak_search I think it's ok - for anything else seems like you should resolve them - 'cos dialyzer caused a problem.

OK, :+1: a646896