[#3598] constrain resource last_changed_by field to be not null and default t…

#3598
Constrains the last_changed_by field on the resource to non null and defaults the last_changed_by to the admin user.

Pull Request Checklist:

[x] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

Try to view a resource with last_changed_by set to None.  Verify you can't, run the migration in this command, then open the resource again.  Verify the resource opens and the last_changed_by user is admin.

@hyi and @alvacouch - I'd like both of you to take a look at this.  It may be controversial to default the last_changed_by user to admin.  I'm open to other approaches if you have any.
I think it's also worth pointing out that this change will cause an error in the workflow that caused last_changed_by to be set to None.  I think it was probably a management command (I can't be sure of this) so users probably won't experience an error.

@sblack-usu Setting None last_changed_by to admin sounds reasonable to me. Another option would be to set to the first creator of the resource but it most likely does not reflect the fact. I'd vote for setting it to admin since it at least reflects the fact, and it the resource gets modified again, a valid user would override the admin user, which sounds reasonable to me.

retest this, please

retest this, please

retest this, please

retest this, please

reopening in a squashed branch in PR #3846


Empty lines and missing issue description

Hey guys,
Awesome job here, node-only Sass linting is something I've been looking for months. Glad you guys are putting effort on this.
I've tried to integrate this tool inside Grommet and I'm facing some challenges. It seems there is something I'm doing wrong, but I can't seem to find what. There is a bunch of empty lines created by the sass linter and a message Please check validity of the block starting from line #5.
[09:58:24] Starting 'scsslint'...

/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/groot.js:21
    throw new Error('Parsing error' + fileInfo + ': ' + e.message);
          ^
Error: Parsing error at src/scss/grommet-core/_objects.color-index.scss: Please check validity of the block starting from line #5
    at module.exports (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/groot.js:21:11)
    at Function.sassLint.lintText (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/sass-lint/index.js:36:13)
    at DestroyableTransform._transform (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/index.js:32:27)
    at DestroyableTransform.Transform._read (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:172:10)
    at DestroyableTransform.Transform._write (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:160:12)
    at doWrite (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:326:12)
    at writeOrBuffer (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:312:5)
    at DestroyableTransform.Writable.write (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:239:11)
    at write (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:623:24)
    at flow (/Users/alansouza/grommet-workspace/grommet/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:632:7)

Here is the content for this given file:
@for $i from 1 through length($brand-neutral-colors) {

  .background-color-index-neutral-#{$i},
  .background-color-index-neutral-#{$i + length($brand-neutral-colors)} {
    background-color: nth($brand-neutral-colors, $i);
  }

  .background-color-index-neutral-#{$i}-a,
  .background-color-index-neutral-#{$i + length($brand-neutral-colors)}-a {
    background-color: rgba(nth($brand-neutral-colors, $i), 0.8);
  }
}

I've faced this issue elsewhere, is that related to the for loop? Any recommendation on how to fix that?

Hey @alansouzati I'm afraid it's a parsing error/problem with the AST we are using, it looks to be fixed in the latest dev branch but we are just waiting for a release now, but it's definitely coming. Looks like under a week or now :smile:
see here https://github.com/tonyganch/gonzales-pe/issues/94
and here https://github.com/tonyganch/gonzales-pe/issues/68
related to this https://github.com/sasstools/sass-lint/issues/44
The lines causing you issue are
#{$i + length($brand-neutral-colors)} and #{$i + length($brand-neutral-colors)}-a

Cool, looking forward to the release!
On Fri, Sep 25, 2015 at 2:05 PM, Dan Purdy<EMAIL_ADDRESS>wrote:

Hey @alansouzati https://github.com/alansouzati I'm afraid it's a
parsing error/problem with the AST we are using, it looks to be fixed in
the latest dev branch but we are just waiting for a release now, but it's
definitely coming. Looks like under a week or now [image: :smile:]
see here tonyganch/gonzales-pe#94
https://github.com/tonyganch/gonzales-pe/issues/94
and here tonyganch/gonzales-pe#68
https://github.com/tonyganch/gonzales-pe/issues/68
related to this #44 https://github.com/sasstools/sass-lint/issues/44
The lines causing you issue are
#{$i + length($brand-neutral-colors)} and #{$i +
length($brand-neutral-colors)}-a
—
Reply to this email directly or view it on GitHub
https://github.com/sasstools/sass-lint/issues/222#issuecomment-143354697
.

--
Alan Souza
Software Engineer
Contact: +1 (408) 421 - 6341

This is unfortunately still causing a parse issue in the latest build of gonzales-pe (3.2.1) I've filed an issue here

@alansouzati this is fixed in sass-lint 1.6.0

This is great news, just in time! I'm soon going to re-evaluate the use of sass-lint for Grommet :)
We are looking forward to removing the ruby dependency and be a 100% node-only project.
I will keep you posted @DanPurdy, and thanks for the follow up

If you have any issues just let us know, we're trying to iron out as many of the edge cases as we can while also getting some fixes into the parser.

Thanks a lot @DanPurdy the latest version of grommet-toolbox now uses sass-lint. I'm proud to say that now we are a node-only project.

@alansouzati Awesome! 🎉


Finished the frontend UI

Im done with the frontend, a.k.a im done with my contributions, you can make updates to the UI still if you want to, It was nice writing code with y'all, hola

you're not done o
pull latest code and style that logout button for me
even profile page and page for single post is not complete lol

you're not done o
pull latest code and style that logout button for me
even profile page and page for single post is not complete lol

you're not done o
pull latest code and style that logout button for me
even profile page and page for single post is not complete lol

Ive styled the button, I pulled your repo before making this PR

yh... about the profile page... merge the PR and check it out, I updated it, Ill see if I can add stuff to the profile page later today

Oh wait I haven't pulled #78...


ldap networking?

Hello, I am currently trying to use openldap with kaiwa-server (https://github.com/digicoop/kaiwa-server)
It uses prosody xmpp server and trying to use ldap to improve scalability (if I got it right). My problem is when I try to add user from the server using command prosodyctl it shows an error
lua5.1: /usr/lib/prosody/modules/ldap.lib.lua:217: attempt to index local 'ld' (a nil value)
stack traceback:
	/usr/lib/prosody/modules/ldap.lib.lua:217: in function </usr/lib/prosody/modules/ldap.lib.lua:211>
	(tail call): ?
	(tail call): ?
	(tail call): ?
	/usr/bin/prosodyctl:305: in function '?'
	/usr/bin/prosodyctl:1247: in main chunk
	[C]: ?

after I inspect the file /usr/lib/prosody/modules/ldap.lib.lua
ld is a connection to ldap server but it doesn't get any connection. I don't know which part is wrong whether it's my docker or the ldap server.
And another thing when I tried to figure out ldap server ip address using ifconfig inside the docker container it return unknown command :( and also no editor i could use inside it. Is this bug or meant to be like this?
Thank you and sorry for the long post :)
PS:
I create the docker container using this command:
docker run -d \
     --name ldap \
     -p 389:389 -p 636:636\
     -v /home/fendy/kaiwa-server-master:/home \
     -e LDAP_DOMAIN=localhost \
     -e LDAP_ORGANISATION=MyOrganisation \
     -e LDAP_ROOTPASS=mypassword \
     osixia/openldap

Hello,
LDAP_ROOTPASS variable doesn't exists in this image use LDAP_ADMIN_PASSWORD instead.
Please check readme file "Environment Variables" section.
So i guess you didn't use the right ldap password in the kaiwa-server image.
if you want to get the ip of a container you can use the docker inspect command.
Or if you are running a terminal inside the container with hostname -i
Sorry but there is no text editor inside the container to make it as light as possible.

Thanks for the reply!
I solved my problem (apparently) it was docker problem (due to my lack of understanding about docker --link option). The kaiwa-server container created before I create the openLDAP container.
So the kaiwa-server was linked to old ldap container's IP address. I almost break my laptop because of this xD. As result of that kaiwa-server couldn't get connection to the ldap server.
I really appreciate your help and I'm sorry because I think this is off topic for asking the docker issue.

you're welcome


Added support for 14 social networks

Changes :

Added Pixabay
Added Giphy
Added Taringa
Added SourceForge
Added Codepen
Added Launchpad
Added Photobucket
Added Wix
Added Crevado
Added Carbonmade
Added Coroflot
Added Jimdo
Added Repl.it
Added Issuu

Notes:

Unable to add Twitch, Tumblr, Big Cartel, Trello.

Sheesh, I did not think that there were any social media sites left.  ;-)
Are not Wix and Jimdo website builders/hosting? It makes me wonder if "social network" may be too limiting. Maybe Sherlock is morphing into a general check of all of the places where one might register? If it does, then the list is huge.  Like Amazon...is Amazon a social media site?  There are reviews there, and a rich comment section.  But, if you go there, then including eCommerce will explode the list.
It does make me wonder if it is going to be practical to maintain the list boiled into the tool. Maybe it can fetch the latest list from the web?  Just thinking aloud...

I added wix and Jimbo while thinking they're commonly used as blog/portfolios (like carbonmade or tumblr), and, in my opinion, it's part of what we call "social medias", but I'm probably wrong.

Or maybe it could be compartmentalized somehow so one could choose if they want to search all eCommerce sites, code/development sites, social media sites, etc.


Validate train kwargs

Ensures that the kwargs passed to train are actually valid for xgb.train().

ready to merge?


Error when install in Ubuntu 12.04

Hello,
I'm trying to install httpie through "pip install -U httpie", and that is what happening:
Downloading/unpacking httpie
  Downloading httpie-0.2.7.tar.gz
Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/basecommand.py", line 104, in main
    status = self.run(options, args)
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/commands/install.py", line 245, in run
    requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/req.py", line 985, in prepare_files
    self.unpack_url(url, location, self.is_download)
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/req.py", line 1109, in unpack_url
    retval = unpack_http_url(link, location, self.download_cache, self.download_dir)
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/download.py", line 456, in unpack_http_url
    unpack_file(temp_location, location, content_type, link)
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/util.py", line 494, in unpack_file
  File "/usr/local/lib/python2.7/dist-packages/pip-1.1-py2.7.egg/pip/util.py", line 408, in untar_file
    os.makedirs(location)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
    mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/home/lsmagalhaes/build/httpie'
Storing complete log in /home/lsmagalhaes/.pip/pip.log

Any ideas?

@lucassmagal Thanks for sharing this, I had the same problem and I had no idea why it wasn't working


:sparkles: Animation was applied to the splash screen.

Issue

close #723

Overview (Required)

Basically, it is almost the same as last year's implementation.

Links

https://github.com/DroidKaigi/conference-app-2022/pull/629

Light
Dark

@takahirom @momomomo111
This PR is ready for review, is there anything missing yet...? :eyes:

@Corvus400
I apologize for the delayed response! 🙏
The splash screen implementation is really cool. Thank you!
I can see differences diff outside of the splash screen area. Do you know the reason for this?

@momomomo111

I can see differences diff outside of the splash screen area. Do you know the reason for this?

Does this refer to the screenshot diff?
I'm not sure on my end, as I believe I implemented the same thing as last year... 🙇

@momomomo111
The results in the screenshot had not changed, so I looked at the documentation and removed the extra description.
https://github.com/DroidKaigi/conference-app-2023/pull/1050/commits/80b528c517134bedac9da35a02bc4563bde18529

I've been wondering why screenshots change. 🤔
Maybe the application theme is used in Robolectric?
If so, we might be able to prevent this by applying the theme for MainActivity. What do you think?

@takahirom
I have added the suggested modifications! 🫡

@takahirom
The screenshot difference no longer occurs successfully.🥳


ARROW-7080: [C++][Parquet] Read and write "field_id" attribute in Parquet files, propagate to Arrow field metadata. Assorted additional changes

The field_id is used for schema evolution and other things. It is surfaced in Python in the Field.metadata as b'PARQUET:field_id'

ChunkedArray::Equals would fail if a child field had unequal metadata, now it does not check the metadata
Improved diffing output in AssertTablesEqual in testing/gtest_util.h (may need some more tests around this)
Added a generic binary ChunkedArray iterator (see internal::MultipleChunkIterator) and helpful applicator internal::ApplyToChunkOverlaps. I retrofitted ChunkedArray::Equals to use this (needed it to improve the diffing output in AssertTablesEqual)
Add KeyValueMetadata::Merge method
Add Field::WithMergedMetadata method that calls KeyValueMetadata::Merge
Print metadata in Field::ToString
Add parquet.ParquetFile.schema_arrow property to return the effective Arrow schema
Print field_ids in parquet::SchemaPrinter

A note for myself, the metadata key should be b'PARQUET:field_id' not b'PARQUET::field_id'

I looked a little more at the automatic field_id assignment and I'm not sure what we're doing is correct, but we should fix it in a dedicated PR. This PR leaves the existing behavior unchanged
https://issues.apache.org/jira/browse/PARQUET-1798

Alright this should be merge-ready

@kou @shiro615 this patch needs some GLib fixes to check schema equality without comparing the metadata, would you be able to take a look (I can try too)?

Sure. I'll take a look this.

I've pushed the change to fix schema equality check.
@kou Please let me know If this change is not reasonable.

@kou Thank you for your comments. I've fixed them.

The R failures are legitimate, @nealrichardson or @fsaintjacques if you are configured to build and run the R tests easily can you add the missing check_metadata=FALSE for R?

It looks like, with this PR, datasets get printed as:
Dataset
int: int32
-- metadata --
PARQUET:field_id: 1
dbl: double
-- metadata --
PARQUET:field_id: 2
lgl: bool
-- metadata --
PARQUET:field_id: 3
chr: string
-- metadata --
PARQUET:field_id: 4
fct: dictionary<values=string, indices=int32>
-- metadata --
PARQUET:field_id: 5
ts: timestamp\[us, tz=GMT\]
-- metadata --
PARQUET:field_id: 6
group: int32
other: string

which is a bit verbose...

Seems like we need a Schema.to_string method that has an option whether to include the field metadata?

That sounds like a good idea, yes.

We have a Jira for that: https://issues.apache.org/jira/browse/ARROW-7063

And re: check_metadata, https://issues.apache.org/jira/browse/ARROW-7786

@pitrou

It looks like, with this PR, datasets get printed as:

Dataset
int: int32
-- metadata --
PARQUET:field_id: 1
... SNIP

Where is this output coming from? I cannot tell from looking around the codebase

@wesm I don't know, that's how they are printed in the R tests.

I see. Looks like it's probably coming from the output of Schema::ToString
https://github.com/apache/arrow/blob/master/r/R/dataset.R#L90
I'll add an option to Schema::ToString and Field::ToString whether to print the metadata, with the default set to off

If you all don't mind I will handle the metadata output issue as a separate patch for ARROW-7063. If we can fix the R and GLib unit tests in the meantime so this can be merged that would be a help

@wesm #6459 when merged will give you what you need to patch up the R tests. Switch them to expect_equivalent() to compare with check_metadata = FALSE.

@shiro615 can you help with fixing the Ruby unit tests? I rebased, not sure why they are failing again. Thanks =)

I've fixed the Ruby unit tests.

Thanks @shiro615 and @kou! Merging this


server / client side db._parse added

@pluma forgot the client side. can you check this also?

@baslr lgtm as well

@baslr can you add CHANGELOG entry

Also jslint is complaining:

One nitpick: I prefer an explicit global.AQL_PARSE over adding AQL_PARSE to the globals list because it makes it more obvious when reading the code (the globals list is a bit of a hack).
Alternatively the AQL_PARSE could be removed from global and exposed via internal as we do with most functions we expose from C++ but want to wrap in JS.
Also also: does AQL_PARSE only accept a string or also bindvars? In the latter case the logic probably doesn't look right in the client.

@pluma query only.


PIP安装报错 “AttributeError: module 'pkgutil' has no attribute 'ImpImporter'

PIP安装报错， python 3.12 , pip 24.2
好像是因为原有的依赖被3.12抛弃后导致的，换个环境吗解决吗？？？
(venv) C:\PyProject\PythonProject
pip install cnmaps
Collecting cnmaps
Using cached cnmaps-1.1.8-py3-none-any.whl.metadata (5.4 kB)
Collecting cartopy>=0.22.0 (from cnmaps)
Using cached Cartopy-0.23.0-cp312-cp312-win_amd64.whl.metadata (8.2 kB)
Collecting fiona>=1.8.20 (from cnmaps)
Using cached fiona-1.10.0-cp312-cp312-win_amd64.whl.metadata (57 kB)
Collecting geojson>=2.5.0 (from cnmaps)
Using cached geojson-3.1.0-py3-none-any.whl.metadata (16 kB)
Collecting geopandas>=0.10.2 (from cnmaps)
Using cached geopandas-1.0.1-py3-none-any.whl.metadata (2.2 kB)
Collecting matplotlib>=3.4.2 (from cnmaps)
Using cached matplotlib-3.9.2-cp312-cp312-win_amd64.whl.metadata (11 kB)
Collecting netcdf4>=1.5.8 (from cnmaps)
Using cached netCDF4-1.7.1.post2-cp312-cp312-win_amd64.whl.metadata (1.8 kB)
Collecting numba>=0.56.0 (from cnmaps)
Using cached numba-0.60.0-cp312-cp312-win_amd64.whl.metadata (2.8 kB)
Requirement already satisfied: numpy>=1.21.5 in c:\pyproject\pythonproject\venv\lib\site-packages (from cnmaps) (2.0.1)
Collecting orjson>=3.7.11 (from cnmaps)
Using cached orjson-3.10.7-cp312-none-win_amd64.whl.metadata (51 kB)
Collecting scipy>=1.8 (from cnmaps)
Using cached scipy-1.14.1-cp312-cp312-win_amd64.whl.metadata (60 kB)
Collecting shapely<2.0,>=1.8.0 (from cnmaps)
Using cached Shapely-1.8.5.post1.tar.gz (200 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [33 lines of output]
Traceback (most recent call last):
File "C:\PyProject\PythonProject\venv\Lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 353, in
main()
File "C:\PyProject\PythonProject\venv\Lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PyProject\PythonProject\venv\Lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 112, in get_requires_for_build_wheel
backend = _build_backend()
^^^^^^^^^^^^^^^^
File "C:\PyProject\PythonProject\venv\Lib\site-packages\pip_vendor\pyproject_hooks_in_process_in_process.py", line 77, in build_backend
obj = import_module(mod_path)
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python312\Lib\importlib_init.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1310, in _find_and_load_unlocked
File "", line 488, in _call_with_frames_removed
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in load_unlocked
File "", line 995, in exec_module
File "", line 488, in call_with_frames_removed
File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-fmyqwzd7\overlay\Lib\site-packages\setuptools_init.py", line 16, in
import setuptools.version
File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-fmyqwzd7\overlay\Lib\site-packages\setuptools\version.py", line 1, in
import pkg_resources
File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-fmyqwzd7\overlay\Lib\site-packages\pkg_resources_init.py", line 2191, in
register_finder(pkgutil.ImpImporter, find_on_path)
^^^^^^^^^^^^^^^^^^^
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

@Ray-exia 目前最新版本的 Python 确实无法支持安装 cnmaps

@Ray-exia 目前最新版本的 Python 确实无法支持安装 cnmaps
好的，谢谢大佬回复我一个编程小白。

请问，这个问题大概什么时候可以解决，谢谢大佬~


<EMAIL_ADDRESS>fails parsing addon-google_apis-google-21/package.xml

Troubleshooting

[x] I've searched discuss.bitrise.io for possible solutions.
Which version of the step is effected? 1.0
Is the issue reproducible with the latest version? YES
Does the issue happen sporadically, or every time? EVERY TIME
Is the issue reproducible locally by following our local debug guide? YES / NO / NOT APPLICABLE

Useful information

FAQ
devcenter.bitrise.io

Issue description
<EMAIL_ADDRESS>has recently started failing; please see the log below.
The first known failure was 2021.08.11 @ 11:01 PST.
Bitrise info

Build URL: https://app.bitrise.io/build/60e3abb1-b149-4b93-8de5-d1e4b70a3d0f#?tab=log
Bitrise Support enabled: YES
Log:

INFO[18:02:04] Step uses latest version -- Updating StepLib ...
+------------------------------------------------------------------------------+
| (0<EMAIL_ADDRESS>                                                        |
+------------------------------------------------------------------------------+
| id: avd-manager                                                              |
| version: 1.0.3                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2021-08-12T18:02:09Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
Config:

AndroidHome: /usr/local/share/android-sdk
AndroidSDKRoot: /usr/local/share/android-sdk
APILevel: 29
Tag: google_apis
DeviceProfile: pixel
CreateCommandArgs: --sdcard 512M
StartCommandArgs: -camera-back none -camera-front none
ID: pixel_api_29_aosp
Abi: x86
EmulatorChannel: 0
Initialize Android SDK
Updating emulator
$ /usr/local/share/android-sdk/cmdline-tools/cmdline-tools/bin/sdkmanager "--verbose" "--channel=0" "emulator"
Updating system-image packages
$ /usr/local/share/android-sdk/cmdline-tools/cmdline-tools/bin/sdkmanager "--verbose" "system-images;android-29;google_apis;x86"
Failed to run phase: exit status 1, output: Loading package information...
Loading local repository...
Info: Parsing /usr/local/share/android-sdk/add-ons/addon-google_apis-google-21/package.xml << ERROR
Info: Parsing /usr/local/share/android-sdk/add-ons/addon-google_apis-google-22/package.xml
Info: Parsing /usr/local/share/android-sdk/add-ons/addon-google_apis-google-23/package.xml

Steps to reproduce
Setup + run the following workflow.
workflows:
  attach-android-emulator:
    steps:
    -<EMAIL_ADDRESS>        inputs:
        - emulator_id: pixel_api_29_aosp
        - api_level: '29'
    description: Attach Android Emulator - Pixel API 29
    before_run: []

Notice that it fails.

Hey @wkoutre 👋
We received a couple of similar reports in the past days, and after our own investigation, we think something is broken on Google's side. The sdkmanager command fails because the package that it tries to install depends on emulator version 30.8.2, while the latest stable version is 30.7.5. In fact, someone already found a bug about this here: https://issuetracker.google.com/issues/196230378
Luckily the required version is available on the canary channel, so doing an sdkmanager --update --channel=3 should work. You can work around the issue by adding a Script step (before the AVD step) that executes this: yes | sdkmanager --update --channel=3

@ofalvai Hey! Thanks for such a quick response :)
This fixed the issue 💪

Looks like Google published the required version to the stable channel:
Available Updates:
  ID                                       | Installed | Available
  -------                                  | -------   | -------
  emulator                                 | 30.7.5    | 30.8.4
  system-images;android-29;google_apis;x86 | 11        | 12
  system-images;android-30;google_apis;x86 | 9         | 10

This means that the AVD Manager step will be able to install any required emulator system image at runtime. I'm closing the issue now.

@ofalvai Unfortunately, I just tested removing the script in my attach-avd-manager flow and it still doesn't work.

Failing build with script removed: https://app.bitrise.io/build/abaac241-485f-44ba-9883-a4c2c98519b3#?tab=log
Latest successful build with script included: https://app.bitrise.io/build/20ae9c02-aefd-42ac-a8f5-34dbe7cd80dc#?tab=log


Unexpected keys when loading pretrained checkpoints in evaluation scripts

Hi,
thank you so much for sharing this!
I'm experiencing issues whenever I'm trying to load pretrained weights for visualizing the attention maps using visualize_attention.py:
unexpected_keys=['head.mlp.0.weight', 'head.mlp.0.bias', 'head.mlp.2.weight', 'head.mlp.2.bias', 'head.mlp.4.weight', 'head.mlp.4.bias', 'head.last_layer.weight_g', 'head.last_layer.weight_v

Continuing training with the checkpoint seems to be fine however, outputting:
Found checkpoint at ./checkpoint.pth
=> loaded student from checkpoint './checkpoint.pth' with msg <All keys matched successfully>
=> loaded teacher from checkpoint './checkpoint.pth' with msg <All keys matched successfully>

Is this to be expected since we are only using the teacher as the checkpoint key?
When printing out the model layers, it only finds this for the head, regardless of the arch:
VisionTransformer(
  (patch_embed): PatchEmbed(
    (proj): Conv2d(1, 192, kernel_size=(8, 8), stride=(8, 8))
  ),
  ...
  (11): Block(
      (norm1): LayerNorm((192,), eps=1e-06, elementwise_affine=True),
      ...
   ),
  ...
 (head): Identity()

Any help is greatly appreciated.

Nevermind, found the solution. From the readme:

You can choose to download only the weights of the pretrained backbone used for downstream tasks, or the full checkpoint which contains backbone and projection head weights for both student and teacher networks.

Seems the incompatible keys are from the unused projection head.


Fix issues found by CodeQL

FwCfg, VirtIOSerial:

Replace ExAllocatePoolWithTag by ExAllocatePoolUninitialized
Fix comparison of different types
Fix uninitialized variable

shouldn't the vqs be allocated by DMA API?

@YanVugenfirer as I see, there are array of pointers to vqs, not vqs.


Revert "Replace StorageV1 client with GCS client"

Reverts apache/beam#25965 because I think this may have broken Python PostCommits (https://ci-beam.apache.org/job/beam_PostCommit_Python311/358/ is the first failing run)

Run Python 3.10 PostCommit

Run Python_Runners PreCommit

R: @BjornPrime @Abacn


Update zoc to 7.11.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Please remove the arduino Cask from your PR.

@miccal done,sorry it was a mistake

@miccal i think i have define (outdated_cask=arduino.rb),how to i undefined this cause it keeps on returning the same issue with other commits.

@SentinelWarren I do not know what you mean?

i used This guide ,,so i assigned outdated_cask to arduino.rb ,and now i have to do a rebase to any new pull request i make because arduino update is included since it is still assigned to outdated_cask. Am asking how to stop this from happening?

Try running the command unset outdated_cask in bash; if it works and you run echo $outdated_cask it should return nothing.


possible obsoletion: GO:0075048 cell wall strengthening in symbiont involved in entry into host

GO:0075048    cell wall strengthening in symbiont involved in entry into host
A process in which the cell wall of the symbiont is strengthened or thickened during penetration into the body, tissues, or cells of the host organism. The host is defined as the larger of the organisms involved in a symbiotic interaction.
I'm not sure that we need this term? It has no definition or annotations or reference.
It would be useful to know why the term was added.
In fungi appressorium form for entry into host and this  process has it's own whole branch:
https://www.ebi.ac.uk/QuickGO/term/GO:0075016
Cell wall  thickening is part of this process, but this seems to be a quite specific high-level term for a process  where we don't have much mechanistic information.
"An appressorium is a specialized cell typical of many fungal plant pathogens that is used to infect host plants. ... As the appressorium matures, it becomes firmly attached to the plant surface and a dense layer of melanin is laid down in the appressorium wall, except across a pore at the plant interface."
(Note: this might not be quite right because appressoria seem to be alternatively described as cell types and  cellular structures, I am following up on this for another non-GO issue)
Unless this has any obvious use for bacteria  @mgiglio99 ? in which case it can be refined, referenced and better positioned, I propose obsoletion.
Once this process is required for annotation it can be correctly defined, referenced and positioned.

Will do as part of #18726


Bug in cli.rb for path with spaces

I find a bug here lib/timeline_setter/cli.rb
if !@options[:no_assets] || !@options[:min]
  FileUtils.cp_r(Dir.glob("#{TimelineSetter::ROOT}/public/*"), outdir)
  # Concatenate JSTs to timeline-setter.js and remove templates.js
  `cat #{outdir}/javascripts/templates.js >> #{outdir}/javascripts/timeline-setter.js && rm -rf #{outdir}/javascripts/templates*`
end

if the output path contains spaces, cat command fails
Here my proposal in order to fix ti
if !@options[:no_assets] || !@options[:min]
  FileUtils.cp_r(Dir.glob("#{TimelineSetter::ROOT}/public/*"), outdir)
  # Concatenate JSTs to timeline-setter.js and remove templates.js
  `cat "#{outdir}/javascripts/templates.js" >> "#{outdir}/javascripts/timeline-setter.js" && rm -rf "#{outdir}/javascripts/templates*"`
end

Try escaping your spaces with backslashes, e.g. /path/to/my\ folder/

This my result:
:~$ /var/lib/gems/1.8/bin/timeline-setter -a -c /tmp/timeline.csv -o /tmp/tm/
== Files copied to /tmp/tm/

:~$ /var/lib/gems/1.8/bin/timeline-setter -a -c /tmp/timeline.csv -o /tmp/tm\ with\ space/
sh: cannot create /tmp/tm: Is a directory
== Files copied to /tmp/tm with space/

With this result
:/tmp$ diff -r tm/ tm\ with\ space/
Only in tm with space//javascripts: templates
Only in tm with space//javascripts: templates.js

And timeline.html in /tmp/tm with space/ do not work
Here firebug console
JST is not defined
[Break On This Error] $(this.config.container).html(JST.timeline());

Done. Thanks


Enable custom filters for Envoy

Customers should be able to build their own filters into Envoy and we should allow config of those filters.

This is the bring your own envoy thing?

@jellevandenhooff and @dio, Yes! Our intent is to work with any Envoy that can do SigV4. We are currently pushing our code to do this to upstream Envoy (see: https://github.com/envoyproxy/envoy/issues/5215). Once that is completed we will start exploring the work to change the intent provided in config to filters that you have developed. If you have usecases for this we would love to hear them to better understand and do the right thing here.

This sounds useful!
As a platform developer, I'd like my colleagues, application developers, to selectively enable envoy filters via running awscli or calling AWS API. An example of filters that is useful if enabled selectively is gRPC-Web filter.

Just to get a little more detail on the custom Envoy statement: Does this imply that it will be possible to deploy to the App Mesh a custom built Envoy binary that is compatible with App Mesh of course e.g. with SigV4 etc?


Escape key and click problem on Mac

Summary:
The ESC (escape) key does not close the modal on a Mac in the chrome browser.
Steps to reproduce:

On a MacPro, in the chrome browser go to an app/page/route with a react-modal.
Click on the button to open the modal.
Use the ESC key that appears in the Touch Bar.

Expected behavior:
The modal should close (but does not).
Link to example of issue:

Additional notes:
I believe the problem is caused in src/components/ModalPortal.js use of keyCode. keyCode is a deprecated property and not the same value for all OS/keyboards. The recommended property to use is KeyboardEvent.key which is standardized across OS/keyboards.

This was my mistake in migrating from another modal module and I missed the prop onRequestClose.


Update photo name to lowercase

closes #44

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:


Fixed StudyTests and a bug relating to the new Animal.last_serum_sample field

Summary Change Description

The StudyTests tests were updated for the new loading format and schema.
The Animal.last_serum_sample ForeignKey field had to have db_column specified to distinguish it from Sample's related foreign key.
Also consolidated the get_researcher() code and created a method: parse_tracer_concentrations for re-use in tests.

Affected Issue Numbers

Resolves no issue

Code Review Notes
Should be straightforward.
Checklist

[x] All issue requirements satisfied (or no linked issues)
[x] Linting passes.
[x] Migrations created & committed (or no model changes)
Tests

[x] Tests implemented (or no code changes)
[x] All multi_working tag tests pass locally
[x] All example load tests pass (remotely) (or their failures predated and are unrelated to this branch)
[x] @tag("multi_working") added to newly passing test functions/classes (or no newly passing tests)
[x] @tag("multi_broken"), @tag("multi_unknown"), or @tag("multi_mixed") removed from newly passing test functions/classes (or no newly passing tests)

Review items implemented in #510


[Feat.]: Failed to run mysqltest

Check Before Asking

[X] Please check the issue list and confirm this feature is encountered for the first time.
[X] Please try full text in English and attach precise description.

Description
obd test mysqltest local --all
Get local repositories and plugins ok
Open ssh connection ok
Cluster status check ok
Connect obproxy(<IP_ADDRESS>:2883) ok
[ERROR] mysqltest-py_script_check_opt-3.1.0 RuntimeError: [Errno 2] No such file or directory: '/home/longda/.obd/plugins/mysqltest/3.1.0/test_suite'
See https://www.oceanbase.com/product/ob-deployer/error-codes .

#ls /home/longda/.obd/plugins/mysqltest
3.1.0  <IP_ADDRESS>
# ls /home/longda/.obd/plugins/mysqltest/<IP_ADDRESS>/
check_test.py  init.py  mysqltest_lib

after copy the test, still failed to run mysql test
cp -rf ~/repo/oceanbase/tools/deploy/mysql_test/* /home/longda/.obd/plugins/mysqltest/3.1.0

obd test mysqltest local --all
Get local repositories and plugins ok
Open ssh connection ok
Cluster status check ok
Connect obproxy(<IP_ADDRESS>:2883) ok
[ RUN      ]Running case: static_engine.expr_substring_index ( 1 / 163 ) x
mysqltest: Could not open connection 'default': 4012 Get Location Cache Fail

[  FAILED  ]static_engine.expr_substring_index bin.lb ( 0.201452 s )
Reboot -

### Other Information

_No response_

You can use the latest version of OBD to rerun the process; the previous version is too old.


hasMany relationship is not "included" automatically, but belongsTo is OK

I've got an issue where a hasMany relationship is not being included in reponses, but the reverese belongsTo reltionship is. I'm not sure why the former isn't working while the latter is OK.
My set up is (I'm using 0.4.1):
Models:
// mirage/models/image.js
import { Model, belongsTo } from 'ember-cli-mirage';

export default Model.extend({
  imageGallery: belongsTo('image-gallery')
});

// mirage/models/image-gallery.js
import { Model, hasMany } from 'ember-cli-mirage';

export default Model.extend({
  images: hasMany('image')
});

Fixtures:
// mirage/fixtures/image-galleries.js
export default [
    {
      id: 0,
      title: 'Gallery'
    }
]

// mirage/fixtures/images.js
export default [
    {
      id: 0,
      imageGalleryId: 0,
      caption: 'Test caption 1'
    },
    {
      id: 1,
      imageGalleryId: 0,
      caption: 'Test caption 2',
    },

    {
      id: 2,
      imageGalleryId: 0,
      caption: 'Test caption 3',
    }
]

Scenarios:
export default function(server) {
  server.loadFixtures('image-galleries');
  server.loadFixtures('images');
}

Serializers:
// mirage/serializers/application.js
import { JSONAPISerializer } from 'ember-cli-mirage';

export default JSONAPISerializer.extend({
    alwaysIncludeLinkageData: true
});

// mirage/serializers/image-gallery.js
import ApplicationSerializer from './application';

export default ApplicationSerializer.extend({
  include: ['images']
});

// mirage/serializers/image.js
import ApplicationSerializer from './application';

export default ApplicationSerializer.extend({
  include: ['imageGallery']
});

Config::
export default function() {
  this.get('/image-galleries/:id');
  this.get('/image-galleries');
  this.get('/images/:id');
  this.get('/images');
}

It's strange the the belongsTo relationships are being included automatically, but the reverse are not. I've tried a number of combinations to try get it working

I've included alwaysIncludeLinkageData in the base application serializer
I'm not using  ?include=... query param as I have specified include: [...] in the serializer explicitly:

Note that, in accordance with the spec, Mirage gives precedence to an ?include query param over a default include: [] array that you might have specified directly on the serializer. Default includes will still be in effect, however, if a request does not have an ?include query param.

The only think I can think of is that I havne't explicitly included the reverse hasMany relationship in the fixtures, as I assume that would be automatically reveresed

EDIT: Even specifying the hasMany relationship in the fixtures still doesn't work:
// mirage/fixtures/image-galleries.js
export default [
    {
      id: 0,
      imagesIds: [0, 1, 2],
      title: 'Gallery'
    }
]

OK, I think I have it working. I didn't realise I was using an older version so I upgraded to 0.4.5 and then explicitly added the hasMany relationships to the fixtures:
// mirage/fixtures/image-galleries.js
export default [
    {
      id: 0,
      imageIds: [0, 1, 2],
      title: 'Gallery'
    }
]

I mentioned this not working in the edit of my original post, but I didn't notice that it should be imageIds and not imagesIds (not the "images)

👍  great, glad you fixed it!


[REEF-635] Evaluator removed twice from evaluator log if an evaluator failed on restart

This addressed the issue by

Remove evaluator entry in informAboutEvaluatorFailures in YarnDriverRuntimeRestartManager.

JIRA:
REEF-635

This looks good, will merge


There is no icon for loot item for loot item npc sheet when sheet type is set to loot

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to NPC character sheet
Add items
Select Sheet and change it to LootSheetNPCs5e
Under GM tab select Sheet Type and set it to Loot
Select Inventory Tab and look at items added initially
See error

Expected behavior
An actual icon for loot item for items when loot sheet is set to loot
Screenshots

Desktop (please complete the following information):

OS: Linux
Browser: Firefox, Chrome
Version 3.5.2

Can you try to uninstall the module and install it fresh?
For some people it seems the font is not loading. There are more icons missing in your screenshot.
I suspect some kind of caching issue.
You could also try to force a hard reload Ctrl+shift+r in the browser when using Foundry. Could be that this makes the browser load the font.
Any screenshots from the browser consoles would also help.
Likely a 404 error.


GraphiQL should have an option to package everything at build time

Description of the feature
Right now the GraphiQL basically loads an external website, it would be nice to have the option to package everything in the binary at build time. This is better anyway from a security perspective than loading some random unsigned URL.

Could we just sign the urls? cdnjs/skypack both support signed urls.
I personally dont agree on self-hosting it, if we are willing to support a static site to host these files aside we enter the realm of async_graphql needing to support a file system. Which to me then feels, if you want a static bundle, you can bundle it yourself and ship it using your favourite web server.

Nope


How do I rename the service-worker file

Hi, I had a previous PWA setup but the service-worker file was called sw.js and now I can't make it register the new one. I tried simply renaming the file to sw.ts (I'm using TypeScript) and changing the swUrl variable in serviceWorkerRegistration file but it didn't work.
Any hints? Thanks.

The service worker name isn't customizable, as it's one of the options that are used in the configuration from the main c-r-a project. Without being able to customize the configuration, you can't change the name.
If you have a previously deployed service worker with a different URL, and want to transition to the new service worker URL,  you should take the following two steps:

Create and deploy a "kill switch" service worker with your old URL.
Deploy your new service worker and ensure that the URL you use for service worker registration corresponds to the new URL.

If you follow both those steps, then both repeat visitors and new visitors will (eventually) end up with the correct service worker with the new URL. It can take two navigation requests for repeat visitors to get the complete update, as the first navigation request will result in the "kill switch" service worker being installed, and the second navigation request will result in the new service worker being installed.

@jeffposnick Thank you for the thoughtful answer! I ended up making a rewrite from /sw.js to /service-worker.js and using the unregister() call. In my case PWA wasn't really worth the trouble.


feat(shared-react): update shared plugin

Updated a shared component
Added more tests

@debsmita1 Thanks for PR, pls link ticket to this


Cervical Cancer Prediction

his project aims to build a machine learning model to predict cervical cancer risk based on patient data. Various classification models are trained and evaluated, including Logistic Regression, Decision Tree, Random Forest, Support Vector Machine (SVM), and AdaBoost.
issue : #1106

@spandana2004 hey we have multiple model like this pls try to add other projects


gRPC server TLS/SSL examples?

Hello! I was not able to find how to run gRPC server with TLS/SSL support.

nvm
https://github.com/awakesecurity/gRPC-haskell/blob/d8f6e0b476797938f5c759146a2bbdc829ba1a84/core/src/Network/GRPC/LowLevel/Server.hs#L135


Reduce memory usage

Memory usage of cargo tally can get quite severe. Running cargo tally winapi windows-sys peaked at 12.7 GB, which isn't terrible (but also far from great). However, when trying it with --transitive, the program exhausts my 32 GB of RAM and 8 GB of swap before Linux kills it as OOM, so it apparently uses in excess of 40 GB.
Is it somehow possible to reduce the amount of memory used? I don't mind if it takes longer to run; the speed is reasonable as-is. Perhaps if some data could be written to disk (and later read back as needed) if memory usage exceeds a threshold?

On my machine cargo tally winapi windows-sys --transitive uses 38.2 GB peak, of which the peak amount allocated by Rust is 29.3 GB, and the rest is presumably heap fragmentation or something (I don't know much about this space).
In any case I have a lot more than that, and have never hit OOMs despite using this crate a lot (including concurrent invocations), so I don't plan to look into this, but I would be open to PRs.

That's reasonable. I don't use it often myself, so it's not a huge deal. Given my infrequency of use, I likely won't spend much time (if any) looking at ways to reduce the memory usage.
Feel free to close this unless you'd rather leave it open as "acceptable, but I'm not doing it".


Fix panic on Fargate when retrieving stats for stopped containers

What does this PR do?
Several issues were raised on Fargate with agent crashing. Investigations showed that this is due to Fargate API returning a pair <containerd_id>: null for containers not yet started/stopped.
Motivation
Fix following bug reports
Describe your test plan
Create a Fargate taks with failing containers

Looks like this was introduced here, which means it's a problem on 7.20.x when using agent 1.3.0 (I think?).
https://github.com/DataDog/datadog-agent/pull/5411/files#diff-36fb3e984a9f42b911aac20f12cc5c6dR60

Looks like this was introduced here, which means it's a problem on 7.20.x when using agent 1.3.0 (I think?).
https://github.com/DataDog/datadog-agent/pull/5411/files#diff-36fb3e984a9f42b911aac20f12cc5c6dR60
[edit] proved the regression in our case, 7.19 fixes. I'm not 100% sure on the "test matrix".

Yes that's correct, fix will be available in 7.21.

This isn't explicitly mentioned in the 7.21 release notes, can you confirm?
https://github.com/DataDog/datadog-agent/releases/tag/7.21.0

@tedder Yes it's included, it's not in changelog but it's there!


In production the autocomplete shows many duplicates

Type "chicken".

This was due to many nodes having the same label. It was solved by creating a node label page and node label search results.


bmdebug seg faults on Ubuntu 18.04

The bmdebug utility builds here and the GUI is briefly shown on screen but the application terminates without output in the console.
In the system log there is a notice on a segmentation fault:
[xxxx.yyyyyy] bmdebug[18655]: segfault at 7fc97a1c39d0 ip 00007fc9880d4bd8 sp 00007fff62215200 error 4 in libpthread-2.27.so[7fc9880cc000+1a000]

I am unable to reproduce it (on Ubuntu 20.04), but I have a hunch. Can you try:
./bmdebug -g<path-to-arm-none-eabi-gdb>

One of the first steps bmdebug takes, is to pop up a file-open dialog to let you set the path to GDB.

That did the trick.
User expectation would be to note the incompatible gdb selected by default on the console as a fault indicator.

The idea is that if there is no suitable GDB selected yet, bmdebug shows a popup that allows you to select it. However, there is apparently an issue with the selection dialog. The browse buttons ([...] at the right of some edit fields) also show a file selection dialog. Presumably, those still crash on your machine. So there is still a bug that I need to fix.

Everything seems to be working using the BMP from the CLI.
However,I'm having the same or a similar issue with bmdebug.
Running Linux Mint 21.1 (based on Ubuntu 22.04).
Happens both when

using the dialog at startup and then navigating to navigating to /usr/bin/gdb-multiarch, and
when specifying from the command line as follows
$ ./bmdebug -g/usr/bin/gdb-multiarch

free(): double free detected in tcache 2
Aborted (core dumped)
Note: The other utilities seem to be working, but I've only tested bmscan, bmserial and bmflash
From /var/log/syslog
systemd-coredump[21357]: Process 21327 (bmdebug) of user 1000 dumped core.#012#012Found module linux-vdso.so.1 with build-id: 6a61cf67fbc559c10e60ed0adeb9ab5e42248a3c#012Found module libdrm.so.2 with build-id: 9c7cb19295d20e515902cb0710326a0b8d6394c8#012Found module libxcb-glx.so.0 with build-id:
...
0bb435fdd5ec37178e14ea03bb36f779a4b72a94#012Found module bmdebug with build-id: 17bde16621a5feb35af1cf7aeba2cf7719d7d935#012Stack trace of thread 21327:#012#0  0x00007f2fc3919a7c __pthread_kill_implementation (libc.so.6 + 0x96a7c)#012#1  0x00007f2fc38c5476 __GI_raise (libc.so.6 + 0x42476)#012#2  0x00007f2fc38ab7f3 __GI_abort (libc.so.6 + 0x287f3)#012#3  0x00007f2fc390c6f
Feb 13 14:50:51 TOWER-PC-LINUX systemd[1]<EMAIL_ADDRESS>Deactivated successfully.

Probably an unrelated bug. Does this happen right after start-up (before you do anything else, such as set a breakpoint or start running)?

It crashes immediately after selecting a file in the dialog.
Also crashes immediately when using the command line -g option.
By the way, the book is really great. It helped me a lot. In my opinion, it should be part of the official BMP documentation.

In commit 8ef5a140f99f0c2bbc826073f91ad0a8c5d7cc31, I added a "-d" switch for bmdebug, which logs the state that the program is in (in the terminal). Can you please try bmdebug -d and send me the result?
I have so far not been able to reproduce the issue. The "malloc debug library" that I use, does not find a double free. However, the error may be somewhere else. There is a lot happening after bmdebug starts GDB: scan for BMP port(s), checking firmware capabilities, loading the DWARF symbols... So with the extra information, I can hopefully pinpoint where to look.
Thank you for the compliment for the book. 1BitSquared is aware of it, but are unhappy with it. So it is an independent project.

Hopefully 1BitSquared will eventually see the benefit of the book.
This may be more info than you need, but trying to be thorough:
Here is my BMP in /dev
ttyBmpGdb -> ttyACM0
Here is the location of gdb-multiarch
$ which gdb-multiarch
/usr/bin/gdb-multiarch
Command to launch and initial output:
$ ./bmdebug -d
State: 0 (moved from -1)
State: 1 (moved from -1)
State: 0 (moved from -1)
Initial screenshot: It seems strange that gdb-multiarch is pre-populated in the File field.

Navigated to my ELF file:

Selected the GDB /usr/bin/gdb-multiarch

Program immediately crashes after selecting the GDB file: Here is the full output from the command line
$./bmdebug -d
State: 0 (moved from -1)
State: 1 (moved from -1)
State: 0 (moved from -1)
State: 1 (moved from -1)
State: 2 (moved from -1)
State: 3 (moved from -1)
bmdebug: bmdebug.c:628: gdbmi_sethandled: Assertion `stringlist_getlast(&consolestring_root, STRFLG_RESULT, STRFLG_HANDLED) == NULL' failed.
Aborted (core dumped)

By the way, here is info from the build process:
my make.cfg file:
GLFW_INC := /usr/include/GLFW
GLFW_LIB := -L/lib/x86_64-linux-gnu
GLFW_LIBNAME := glfw
Here is the output from the build:
gcc -c /usr/include/GLFW -Wall -g -obmdebug.o bmdebug.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oarmdisasm.o armdisasm.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -obmcommon.o bmcommon.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -obmp-scan.o bmp-scan.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -obmp-script.o bmp-script.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -odemangle.o demangle.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -odwarf.o dwarf.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oelf.o elf.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oguidriver.o guidriver.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -omcu-info.o mcu-info.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -omemdump.o memdump.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ominIni.o minIni.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_mousepointer.o nuklear_mousepointer.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_splitter.o nuklear_splitter.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_style.o nuklear_style.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_tooltip.o nuklear_tooltip.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -opathsearch.o pathsearch.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ors232.o rs232.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oserialmon.o serialmon.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ospecialfolder.o specialfolder.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -osvd-support.o svd-support.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oswotrace.o swotrace.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -otcpip.o tcpip.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oxmltractor.o xmltractor.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -odecodectf.o decodectf.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oparsetsdl.o parsetsdl.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ofindfont.o findfont.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -olodepng.o lodepng.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear.o nuklear.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_glfw_gl2.o nuklear_glfw_gl2.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW pkg-config --cflags gtk+-3.0-Wall -g -DNOC_FILE_DIALOG_GTK -onoc_file_dialog.o noc_file_dialog.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmdebug bmdebug.o armdisasm.o bmcommon.o bmp-scan.o bmp-script.o demangle.o dwarf.o elf.o guidriver.o mcu-info.o memdump.o minIni.o nuklear_mousepointer.o nuklear_splitter.o nuklear_style.o nuklear_tooltip.o pathsearch.o rs232.o serialmon.o specialfolder.o svd-support.o swotrace.o tcpip.o xmltractor.o decodectf.o parsetsdl.o findfont.o lodepng.o nuklear.o nuklear_glfw_gl2.o noc_file_dialog.o -lfontconfig -lglfw -lGL -lm -lbsd -ldl -lpthread -lX11 -lxcb -lXau -lXdmcppkg-config --libs gtk+-3.0-lusb-1.0 gcc -c /usr/include/GLFW -Wall -g -obmflash.o bmflash.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -obmp-support.o bmp-support.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ocksum.o cksum.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ocrc32.o crc32.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -ogdb-rsp.o gdb-rsp.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -oident.o ident.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -onuklear_guide.o nuklear_guide.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -c /usr/include/GLFW -Wall -g -otcl.o tcl.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmflash bmflash.o bmcommon.o bmp-scan.o bmp-script.o bmp-support.o cksum.o crc32.o elf.o gdb-rsp.o guidriver.o ident.o minIni.o nuklear_guide.o nuklear_mousepointer.o nuklear_style.o nuklear_tooltip.o rs232.o specialfolder.o tcl.o tcpip.o xmltractor.o findfont.o lodepng.o nuklear.o nuklear_glfw_gl2.o noc_file_dialog.o -lfontconfig -lglfw -lGL -lm -lbsd -ldl -lpthread -lX11 -lxcb -lXau -lXdmcppkg-config --libs gtk+-3.0-lusb-1.0 gcc -c /usr/include/GLFW -Wall -g -obmprofile.o bmprofile.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmprofile bmprofile.o bmcommon.o bmp-scan.o bmp-script.o bmp-support.o crc32.o decodectf.o demangle.o dwarf.o elf.o gdb-rsp.o guidriver.o mcu-info.o minIni.o parsetsdl.o rs232.o specialfolder.o swotrace.o tcpip.o xmltractor.o nuklear_guide.o nuklear_mousepointer.o nuklear_splitter.o nuklear_style.o nuklear_tooltip.o findfont.o lodepng.o nuklear.o nuklear_glfw_gl2.o noc_file_dialog.o -lfontconfig -lglfw -lGL -lm -lbsd -ldl -lpthread -lX11 -lxcb -lXau -lXdmcppkg-config --libs gtk+-3.0-lusb-1.0 gcc -c /usr/include/GLFW -Wall -g -obmscan.o bmscan.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmscan bmscan.o bmp-scan.o bmp-script.o bmp-support.o crc32.o elf.o gdb-rsp.o rs232.o specialfolder.o tcpip.o xmltractor.o -lbsd -lpthread gcc -c /usr/include/GLFW -Wall -g -obmserial.o bmserial.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmserial bmserial.o guidriver.o minIni.o rs232.o specialfolder.o noc_file_dialog.o nuklear_guide.o nuklear_mousepointer.o nuklear_splitter.o nuklear_style.o nuklear_tooltip.o tcl.o findfont.o lodepng.o nuklear.o nuklear_glfw_gl2.o -lfontconfig -lglfw -lGL -lm -lbsd -ldl -lpthread -lX11 -lxcb -lXau -lXdmcppkg-config --libs gtk+-3.0-lusb-1.0 gcc -c /usr/include/GLFW -Wall -g -obmtrace.o bmtrace.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -obmtrace bmtrace.o bmcommon.o bmp-scan.o bmp-script.o bmp-support.o crc32.o demangle.o dwarf.o elf.o gdb-rsp.o guidriver.o mcu-info.o minIni.o nuklear_guide.o nuklear_mousepointer.o nuklear_splitter.o nuklear_style.o nuklear_tooltip.o rs232.o specialfolder.o swotrace.o tcpip.o xmltractor.o decodectf.o parsetsdl.o findfont.o lodepng.o nuklear.o nuklear_glfw_gl2.o noc_file_dialog.o -lfontconfig -lglfw -lGL -lm -lbsd -ldl -lpthread -lX11 -lxcb -lXau -lXdmcppkg-config --libs gtk+-3.0 -lusb-1.0 gcc -c /usr/include/GLFW -Wall -g -ocalltree.o calltree.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -ocalltree calltree.o -lbsd gcc -c /usr/include/GLFW -Wall -g -oelf-postlink.o elf-postlink.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -oelf-postlink elf-postlink.o elf.o -lbsd gcc -c /usr/include/GLFW -Wall -g -otracegen.o tracegen.c gcc: warning: /usr/include/GLFW: linker input file unused because linking not done gcc -L/lib/x86_64-linux-gnu -g -otracegen tracegen.o parsetsdl.o -lbsd

By the way, the book is really great. It helped me a lot. In my opinion, it should be part of the official BMP documentation.

I totally agree. Awesome read and cool to provide custom tailored tools.
I surely hope 1BitSquared change their mind. It is promotion of their product afterall.

From the trace, it looks like bmdebug already chokes on the welcome message that GDB prints on start-up. What is the version of gdb-multiarch that you are using?

Yes, It crashes as soon as I select the debug file.
$ gdb-multiarch -v
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

What is the version of gdb-multiarch that you are using?

In case it is relevant, here is mine that I have to pass  on the command line. However it works fine here:
$ gdb-multiarch -v
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

@d-adamson: can you do another test with the latest version of bmdebug.c (just committed). There is more verbose output around the early stages (when running "./bmdebug -d").
It's curious: I booted Mint 21.1 from an USB stick, installed gdb-multiarch from the repository (which is version 12.1), and yet I still cannot reproduce the problem.
There is one change in the latest bmdebug (not directly related to the bug, but it came up because of this bug report): it now also searched for gdb-multiarch in the path (previous versions looked only for arm-none-eabi-gdb). So it should no longer be needed to add the path to GDB on the command line.

Interesting. I started bmdebug -d but forgot to plug in my adapter and the program did not crash immediately. Even though it was pre-selected, I sucessfully selected /usr/bin/gbd-multiarch
Next, I plugged in my BMP adapter and relaunched bmdebug -d => crashed after a brief initialization phase.
I wonder if it could be related to the sym links used to give the probe a consistent name?
lrwxrwxrwx 1 root root 7 Feb 17 10:11 /dev/ttyBmpGdb -> ttyACM0
lrwxrwxrwx 1 root root 7 Feb 17 10:11 /dev/ttyBmpTarg -> ttyACM1
$ ./bmdebug -d
ProgOutput.txt

The reason was the trailing space before the \n on the last line, plus that this line does not have a suffix with the architecture (M0+). Fixed in commit 98f08d40a1dbc560fc305c6505ce19fecf9847a9.
The other issue this reveals is: bmdebug does not offer you a choice which target to attach to. It will always attach to the first target in the list.

Great! Sounds like it's getting close.
Sounds like a reasonable workaround - passing the "attach target" on the command line.
Unfortunately, I was not able to test the latest version. I got an error during the build.
Here is my makefile.cfg contents:
GLFW_INC := /usr/include/GLFW
GLFW_LIB := -L/lib/x86_64-linux-gnu
GLFW_LIBNAME := glfw
$make
gcc -c /usr/include/GLFW -Wall -g -oguidriver.o guidriver.c
guidriver.c:552:5: error: conflicting types for ‘guidriver_appsize’; have ‘int(int *, int *)’
552 | int guidriver_appsize(int *width, int *height)
|     ^~~~~~~~~~~~~~~~~
In file included from guidriver.c:33:
guidriver.h:53:7: note: previous declaration of ‘guidriver_appsize’ with type ‘_Bool(int *, int *)’
53 | bool  guidriver_appsize(int *width, int *height);
|       ^~~~~~~~~~~~~~~~~
guidriver.c:574:5: error: conflicting types for ‘guidriver_poll’; have ‘int(int)’
574 | int guidriver_poll(int waitidle)
|     ^~~~~~~~~~~~~~
In file included from guidriver.c:33:
guidriver.h:55:7: note: previous declaration of ‘guidriver_poll’ with type ‘_Bool(_Bool)’
55 | bool  guidriver_poll(bool waitidle);
|       ^~~~~~~~~~~~~~
make: *** [Makefile:68: guidriver.o] Error 1

Sorry about that, fixed in commit 7b6f97414712e39ac5d898a6a4aa468bed1309d3.

Almost there ...
bmdebug comes up and initializes, but I do not see anything in the source window.
However, I can type "list main" in the console and see the source.
Normally my *.elf is in a "build" subdirectory. I've tried putting the *.elf and *.c in the same directory, but that does not seem to help.

Also, here is the content of the blink-10.elf.bmcfg file:
[Target]
entrypoint=main
cmsis-svd=
[Settings]
tpwr=0
connect_srst=0
[Flash]
auto-download=0
[SWO trace]
mode=1
bitrate=100000
clock=48000000
datasize=8
enabled=0
ctf=
chan0="0 #000000 "
chan1="0 #000000 "
chan2="0 #000000 "
chan3="0 #000000 "
chan4="0 #000000 "
chan5="0 #000000 "
chan6="0 #000000 "
chan7="0 #000000 "
chan8="0 #000000 "
chan9="0 #000000 "
chan10="0 #000000 "
chan11="0 #000000 "
chan12="0 #000000 "
chan13="0 #000000 "
chan14="0 #000000 "
chan15="0 #000000 "
chan16="0 #000000 "
chan17="0 #000000 "
chan18="0 #000000 "
chan19="0 #000000 "
chan20="0 #000000 "
chan21="0 #000000 "
chan22="0 #000000 "
chan23="0 #000000 "
chan24="0 #000000 "
chan25="0 #000000 "
chan26="0 #000000 "
chan27="0 #000000 "
chan28="0 #000000 "
chan29="0 #000000 "
chan30="0 #000000 "
chan31="0 #000000 "
[Serial monitor]
mode=0
port=
baud=0

Here are some files for reference:
blink-10.c
blink-10.elf
blink-10.bmcfg
blink-10_cli_output.txt  (output from the command line running with ./bmdebug -d )
blink-10.zip

Also, I can step through the source when running gdb-multiarch from the command line with tui -enable

This one left me scratching my head for a while. The debug log shows that GDB gives the full paths to the source files, and GDB can read those source files itself, so why would bmdebug fail to read them?
Then I noticed that some source files appear multiple times in the list provided by GDB. For GDB, the list of files is a table, and it refers to the "current file" by a zero-based index into that table. The bmdebug front-end stores the GDB table as an array, but... it does not load the same source file twice. So that is what happened: the GDB "current file index" no longer aligns with the bmdebug array index.
I have redesigned how bmdebug handles source files and references to source files. It no longer uses an array, but explicitly stores the GDB source table indices with each source file (and there can be multiple GDB indices for a single source file).
This is in commit 747334bd986d93edc68fa989d694edd3c1eb9570. The caveat is that I have so far only done limited testing on it myself.

These issues all appear fixed as of commit 56cd68372dfd06fb0acaa555f2070bef32337810.


Bump to go1.18

All tests pass with go1.18 installed.
Fixes #194

Codecov Report

Merging #204 (07e6f39) into main (6a1639c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   91.37%   91.37%
=======================================
  Files          38       38
  Lines        1705     1705
=======================================
  Hits         1558     1558
  Misses         98       98
  Partials       49       49

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 6a1639c...07e6f39. Read the comment docs.


StateHasChanged causes InvalidOperationException

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

ASP.NET Core '3.0'
Run this code: 'Blazor tab example'
Close the browser or stop debugging (Shift + F5).
See error at the line with StateHasChanged():

Exception thrown: 'System.InvalidOperationException' in Microsoft.AspNetCore.Components.dll
An exception of type 'System.InvalidOperationException' occurred in Microsoft.AspNetCore.Components.dll but was not handled in user code
The current thread is not associated with the renderer's synchronization context. Use Invoke() or InvokeAsync() to switch execution to the renderer's synchronization context when triggering rendering or modifying any state accessed during rendering.

Expected behavior
Normal program termination without errors.

Can you provide the call stack for the error when this happens?

Thanks for reporting this, @DevelAx!
I've tracked down the underlying issue which causes this and reported it at https://github.com/aspnet/AspNetCore/issues/8816. So, I'll close this issue in favour of the other one which describes root cause.

Ok, thank you for the quick response!
Actually, there is no "callstack" I can see. Even the exception message disappears after a second and the debugger immediately stops.


Last three issues below this one seem to be spam

Hi team, the issues below seem to be spam? Did not want to tag them in this one.

Thanks for the report @PizBernina 🙏. Locked and closed #296, #297, & #298


Html5lib catch warning

This is a minor change that a) probably isn't necessary, but I thought I'd give you the option, and b) probably doesn't need any tests (and would be difficult to test in a meaningful way).
Suppress deprecation warnings in html5lib

html5lib currently issues a DeprecationWarning in python ^3.7. This
warning is fixed here:

https://github.com/html5lib/html5lib-python/commit/4f9235752cea29c5a31721440578b430823a1e69

I have spoken with the maintainers (#whatwg on freenode) and they said
that a new release of html5lib is not scheduled as the package is not
actively maintained, but it sounded like they were aware of the issue
and could release a new version. (I did not press further.)

This is a very minor change with no major intended side effects, other
than that it cleans up output while running tests (and presumably from
any clients using the legacy_repository type).

Thanks!


Modify issue title

I’m looking to enhance some issue titles by modifying them based on their error messages. I found it quite straightforward to implement this using the fingerprint rule in the Sentry UI. For instance, I created a rule like this:
message:"status 40*" -> user-fault-errors, title="User Error: Client Status 40x"
However, I’m having trouble locating the relevant information to achieve this using the SDK.
Am I looking for something that can't be done using the SDK?

Hey @AnonC0DER, thanks for the question.
There is no SDK API for this specifically. What you can do is have a look at how Sentry the UI computes the title from SDK event payload. Essentially, it first extracts some parts and then uses this to determine the title. Looks like it uses the exception dict to do this.
You have the whole SDK-side event payload available in before_send and any modifications done to it there will be persisted, so you could use this to modify the exception information in the payload. It's not really something I'd recommend though since I imagine it might mess up other parts of the UI that read data from the exception dict.


Fix issues with initial version (#3)

Followed instructions from scratch and fixed any issues found with the initial version:

Typos and spelling errors
Missing references

tested and approved.


I am unsure of how to or if I can connect to and query AWS RDS DB via dribbles AWS data api Feedback for “Aws Data API”

Please add more clear instrustions on how to use AWS RDS if it is possible.

Currently, Drizzle only supports the PG dialect for AWS Data API. Read more here: https://orm.drizzle.team/docs/connect-aws-data-api-pg.


Cannot find CocoaTextField in scope.

Tried installing SwiftUIX to use CocoaTextField firstResponder since that's still missing from SwiftUI.
However I can't seem to get the package to work :(
I get the following error when trying to build:

I added the package following the installation instructions:

However I was not able to find anything called "Linked Frameworks and Libraries" in the project settings for Xcode 12.2
It is however in this section, which I assume replaces the old "Linked Frameworks and Libraries"?

I tried to close Xcode and start it back up, and I tried to clean the build folder with no luck. Any idea why this isn't working?
Xcode: Version 12.2 (12B45b)

show your full file please. Did you write import SwiftUIX before declaring view?

on top of your file, write import SwiftUIX

As others have noted, please import the SwiftUIX module.


Support Crop usecases

Support crop functionality inside the UHDR library. If the user were to feed in crop regions along with the input P010 and/or YUV420, JPEG the library should perform the crop operation based on the crop values provided.

Hi @kkumar1994, I believe the cropping method is already here, could you let me know if there is any additional requests. Thank you!

Hi, yes that's exactly what I was thinking about. I hoped to contribute to
the project by implementing this feature but it looks like you guys beat me
to it :)
On Fri, Jun 14, 2024, 1:47 AM DichenZhang1 @.***> wrote:

Hi @kkumar1994 https://github.com/kkumar1994, I believe the cropping
method is already here
https://github.com/google/libultrahdr/blob/main/lib/include/ultrahdr/editorhelper.h,
could you let me know if there is any additional requests. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/google/libultrahdr/issues/167#issuecomment-2167338809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBEJYHQPQXO6ATPLGEYT2TZHKGY5AVCNFSM6AAAAABI7JHA7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXGMZTQOBQHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for confirming. I'll close this thread now. If there is other requests, please feel free to reopen or file a new one. Thank you!


one broken job breaks all other jobs

Hello
We encountered an unpleasant situation: backups were not collected for a couple of days due to errors in the jobs config.
There are several jobs that worked properly, but among them there was one unconfigured job. As a result, all backups were not collected for several days, alerts also did not arrive by email, apparently because checking the correctness of backups did not work properly.
# nxs-backup --version
nxs-backup v3.0.2

after the “broken” config was removed from conf.d, everything works normally, but I would like to either receive alerts about a problem with the configs, or have live jobs processed separately, regardless of the presence of problematic jobs

Hi, @berzerk54.
We have changed the behavior of nxs-backup.
Now jobs that were initialized correctly will be executed when running the backup, even if errors were detected. If notification channels are configured, you will be notified of errors detected during initialization.
The situation you described is excluded if the configuration file can be read. This update will be available in version 3.5.0 which we will release soon.
In any case, when making any changes to the configuration, it is recommended to perform a validation of the config to avoid similar situations in the future.
Thank you for your interest in nxs-backup. We will be glad to receive new suggestions.


Splunk Buffer errors in logging pods after install

Rancher Server Setup

Rancher version: 2.5.12-rc1 (also saw this in 2.5-head)
Installation option (Docker install/Helm Chart): Docker

If Helm Chart, Kubernetes Cluster and version

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.20.14
Cluster Type (Local/Downstream):

If downstream, what type of cluster? Node Driver - DO
User Information**

What is the role of the user logged in? Standard User

Describe the bug
Installed logging v2 3.15.0 into digital ocean cluster set splunk as logging option. errors in logging pod; rancher-logging-fluend-configcheck pods unavailable. Logs not flowing to splunk.
To Reproduce

created downstream node driver cluster
install logging v2 - 3.15.0
create cluster-output using splunk as the logging service
create cluster-flow
Navigate to cluster explorer > Workload > pods

Result
rancher-logging-fluentd-configcheck pod is in error state. logs show error
2022-01-05 17:33:56 +0000 [info]: starting fluentd-1.13.3 as dry run mode ruby="2.7.4" 2022-01-05 17:33:56 +0000 [error]: config error file="/fluentd/etc/fluent.conf" error_class=Fluent::ConfigError error="this plugin 'Fluent::Plugin::SplunkHecOutput' cannot handle arguments for <buffer ...> section"
Expected Result
Logs flow to Splunk
Screenshots

Additional context
Doing a search for the error, located a splunk error - https://github.com/splunk/fluent-plugin-splunk-hec/issues/150 - not sure if this is the issue at the heart of why we're seeing our errors, but looks similar. Including here as research I did.

This is happening in 2.6.3 also.

We can use https://github.com/banzaicloud/logging-operator/releases/tag/3.17.1 to solve this:
$ docker run -ti --entrypoint sh ghcr.io/banzaicloud/fluentd:v1.14.4-alpine-2 -c "gem list" | grep splunk
fluent-plugin-splunk-hec (1.2.10)

Just ran into this same issue.  @superseb Do you have a timeframe for when the newer chart will be available?

You can follow progress on v2.6.4 milestone here: https://github.com/rancher/rancher/milestone/255

You don't have to update, pretty sure it's going to become available for Rancher 2.6.0 and up, but it's going to get released along side 2.6.4

We will still prioritize fixing this, but I am removing the release blocker tag since this is not a regression (reproduced in 2.6.3) and fixing this won't require a full upgrade based on Seb's last comment.

As a workaround, I found setting the option in the Logging Helm Chart
images.fluentd.tag = v1.14.4-alpine-2
Pulls the newer image and lets the Splunk output work

As a workaround, I found setting the option in the Logging Helm Chart
images.fluentd.tag = v1.14.4-alpine-2
Pulls the newer image and lets the Splunk output work

I am going to try this as a work around for now.

Pass Verified in 2.6-head Commit ID f2a4147

created downstream ec2 cluster
installed logging v2
created a cluster output and cluster flow for splunk
checked [rancher-logging-root-fluentd-configcheck] pod logs

configuration complete; no errors in logs


Popup viewer for iOS - text clipping when larger text is enabled in system settings

Interestingly, the text itself doesn't appear to grow in size.
To repro, go to the Settings app, then choose Accessibility-> Display & Text Size-> Larger Text then use the slider at the bottom to choose the text size before running an app with the popup viewer.

Likely this line needs to take this into account: https://github.com/Esri/arcgis-toolkit-dotnet/blob/f70a027d91e958d60a2560f365503b71e6664f85/src/Toolkit/Toolkit.iOS/UI/Controls/PopupViewer/PopupViewerTableSource.cs#L54

No repro; this was likely already fixed years ago. Verified on both Forms and native.


Typo change openStack vendor to openstack

Typo change openStack vendor to openstack, this typo prevents
openstack SSA from working.

@skateman does this fix your issue?

@Ladas yes


Improved Documentation on Jupyter-scheduler status

Problem

Currently I am getting a lot of status: Failed, but I still get output files
This seems somewhat hard to troubleshoot with current documentation. I don't know what I am doing wrong

Proposed Solution

would love some top-tips to help troubleshoot failed jobs
How many different status's exist?

Additional context

Below is a screen shot:

Thanks for the feedback, we will work on improving the documentation for failures. In the meantime, does the output notebook give you any indication of what the failure way?

fireweather_ML-2023-05-17-05-03-43-PM.ipynb.zip
Here is a zip file of the notebook

Current status is it pip installs fine, but then can't be found. Looking into it further. Attached is a zip of html of the notebook.
fireweather_ML.html.zip


LDAPS not working

ldap works fine
ldaps does not work
there seems to be an issue with the secure Ldap checkbox in the GUI.
When adding a LDAP Server the checkbox for secure LDAP always resets to unchecked, after applying the setting.
tcpdump shows that port 389 is used.
but i was able to set the value in the mysql db.
mysql> select * from ldapServers;
mysql> update ldapServers set adSecure = 1 where adSecure = 0;
that works, tcpdump shows that connection is now on port 636.
unfortunately,  i get an authentication error.
I doublecheck with "ldapsearch" that the ldap server accessable via ldaps, this only works with the option "LDAPTLS_REQCERT=never", as i did not install the server certs.  (and i prefer not to)
I assume that ipsk manager fails to authenticate agains ldaps because it also lacks the server certificates.
I tried to modify the BaseLDAPClass.php, so that it ignores any certificates:
ldap_set_option($ldapConnection, LDAP_OPT_DEBUG_LEVEL, 7);
ldap_set_option($ldapConnection, LDAP_OPT_PROTOCOL_VERSION, 3);
ldap_set_option($ldapConnection, LDAP_OPT_REFERRALS, 0);
ldap_set_option($ldapConnection, LDAP_OPT_X_TLS_REQUIRE_CERT,0);
(or  LDAP_OPT_X_TLS_ALLOW )
unfortunately this does not work either.
i don't see any options in the GUI to import certs.
any updates on this?

update: ldaps is now working.
i modified /etc/ldap.conf  as follow:

LDAP Defaults

See ldap.conf(5) for details
This file should be world readable but not world writable.
#BASE   dc=example,dc=com
#URI    ldap://ldap.example.com ldap://ldap-master.example.com:666
#SIZELIMIT      12
#TIMELIMIT      15
#DEREF          never
TLS certificates (needed for GnuTLS)
#TLS_CACERT     /etc/ssl/certs/ca-certificates.crt
TLS_REQCERT never

Thank you for posting the details of the issue.
That is correct, the Root and any Intermediate CA servers would need to be installed in the Servers's CA Trusted Certificate store.
At a minimum, the LDAP configuration page will be updated to provide information into enabling this feature.

Fixed Secure LDAP Functionality & Added notation on Requirements that the LDAP's Server Certificate and/or Root CA must be trusted by the server hosting iPSK-Manager.


rawfilepath-0.2.2

I've released 0.2.2 of rawfilepath on Hackage a few weeks ago, but Stackage Nightly is not picking it up (Stackage Nightly 2017-05-07 still hosts 0.1.1).
I've read README.md and MAINTAINERS.md but couldn't figure it out myself. I'm new to the Stackage package maintenance, so I guess I'm doing something wrong that blocks Stackage Nightly from picking up the new version. I'd appreciate if anyone can kindly give me a hint. 😄

Hi @xtendo-org, you can see in the build constraints file that we have placed an upper bound limiting rawfilepath to < 0.2.0. Once https://github.com/xtendo-org/rawfilepath/issues/3 is solved, we'll remove this bound and get the latest. Hope that covers it!

Thanks! I've just solved xtendo-org/rawfilepath#3. 😄

Great, I've opened up https://github.com/fpco/stackage/pull/2503 to remove the bound then!


Cannot reproduce the results in Table 9

I have some trouble reproducing the results of Table9 (babi QA task).
In our run, the test error for the best model does not fall below 1%.
Actually, the test error is more than 1.4%.
 How many epochs did you set for the training?
Look at your numbers; it seems that only task 19 needs improvement. Typically, if you let the model train for more epochs, it will continue improving.

I tried base settings of this repository;
Run 5 times with maximum 500 training epochs and I found that the results are saturated around 300 epochs.
Should I run more than 500?

I'll rerun the code to check the result. I only needed to run 500 epochs for my machine to get the result in Table 9. But you can try to run more in the meantime.

Can you share the packages as 'requirements.txt' that you used for the experiment?

I am running the code. If I can reproduce the results with the current package, I'll share it with you.  The old exact environment for the paper is no longer existing.

Thank you for your consideration. I'll wait for the results.

I have pushed the requirements.txt and seed setting for your convenience.

Did you try experiments on another version of PyTorch since recent GPUs don't support PyTorch 1.0x as I know.

I tried 1.7.1 but it did not work well.
By the way, I can run the code with torch 1.0.1 + CUDA 11.3 +  GPU Tesla V100-SXM2.
There is no support issue from my side.

Thank you for your work! :)


MatSelectItem not updating Value

Describe the bug
MatSelectItem not updating Value
To Reproduce
<MatSelectItem @bind-Value="Item.Method" Items="@methods">
                            <ItemTemplate Context="method">
                                <FlexLine Direction="Direction.Column" Class="dropdown-vertical-template">

@method?.Name

@method?.Description

                                </FlexLine>
                            </ItemTemplate>
                        </MatSelectItem>

This just doesn't work. The list is populated but the selection is not set even though Item.Method has the correct value set at the start of the component (this is an "edit" scenario. Whole Item object is correctly set at this point).
I then figured perhaps Item.Method needs to be the exact match from the methods so i did this
 Item.Method = methods.Where(x => x.Id == Item.MethodId).SingleOrDefault();
which gets me Error: System.FormatException: Input string was not in a correct format. even though methods.Where(x => x.Id == Item.MethodId).SingleOrDefault() does indeed return the proper value.
Blazorfiddle link
I tried to replicate in blazorfiddle but I got a different error before anything select related. I think blazorfiddle maybe too many version behind now to be an effective tool. I submitted a request to update its guts on it's own github.
Expected behavior
Value in the drop down is selected
I think it maybe related to #494 .

The code you posted is not enough to reproduce the problem, we would have to make up the @code { } that goes with it. Please post a minimal code that goes with the markup for reproduction.

I think you got a bug in your code. I constructed a minimal example that updates a property of an object and it works:
<MatSelectItem @bind-Value="Item.Method" Items="@value1Items">
    <ItemTemplate>
        @context (@(context.Length))
    </ItemTemplate>
</MatSelectItem>

    Selected value: @(Item?.Method)

@code {

    string[] value1Items = new[]
    {
        "Grains",
        "Vegetables",
        "Fruit",
    };

    public class Foo
    {
        public string Method { get; set; }
    }

    Foo Item = new Foo();

}

I had to change the ItemTemplate because of <FlexLine>  which requires another dependency, but it doesn't seem to matter anyway.

Your code works because all the info to set the dropdown is available at the Init.
Problems creep up when drop down list is as well as the select item are set after an api call of some sort in OnInitializedAsync.
I don't have access to the exact code now but it's something along the lines of
OnInitializedAsync {
methods = Http.GetFromJson(); //API call to methods;
method =  methods.Where(x=>x.Id == Item..Method.Id).SingleOrDefault(); //Item is the overarching object of the control where the drop down results. Item has a "Method" property
}

ok, got it. You can mimick the asynchronous initialization by using await Task.Delay(...). If you can put together a minimal reproducing piece of code that can be copy-pasted into a page of a test project it is more likely that this is getting fixed fast. Thank you.

Am having same problem... anyways MatBlazor is salvation

@WinInsider the OP never produced code that reproduces the problem. Can you maybe?

@henon once an example will be ready... will update here with link to Blazorfiddle

@henon For what it's worth I mentioned why I didn't repro in the request itself
"I tried to replicate in blazorfiddle but I got a different error before anything select related. I think blazorfiddle maybe too many version behind now to be an effective tool. I submitted a request to update its guts on it's own github."

I'm pretty sure this is a duplicate of #494.
A workaround (if feasible for your project) is to wait untill you have your results from the API until you render your MatSelect.

Yeah i think so too.
And yep that's the work around I am using.
Issue is, it creates a very unsightly popup in the controls and in some cases, like mine, both list and item are coming from the API so I have to wait until both of these are done before rendering MatSelect or it breaks or doesn't change (I frankly don't remember at his point as I have grown to rely on the work around)
It's also not common for a real life from to have 2+ dropdowns so having them all pop in like that makes the whole form feel very amateurish :(

@americanslon Maybe you can render a disabled MatSelect placeholder which doesn't have any bindings until your api call returns? Makes sort of sense since the user can't select anything at that moment anyway.

Yeah that's a thought. My form has quite a few states so I have rather complex logic on the disabled fields. Hate to add to it.
I'll be honest, I am selfishly waiting until this gets resolved as it seems like a relatively high profile bug :)

I am experiencing similar issues setting the initial value from a web api service.
Any other ideas on how to resolve?

I am experiencing similar issues setting the initial value from a web api service.
Any other ideas on how to resolve?

Any updated on this?


wifi: Use TLS credentials library for 802.1x certificates

Is your enhancement proposal related to a problem? Please describe.
Currently, 802.1x certificates for Wi-Fi Enterprise have to be passed during build time which is okay for developement, but for production we need a trusted storage based solution.
Describe the solution you'd like
Use the existing library https://github.com/zephyrproject-rtos/zephyr/tree/main/subsys/net/lib/tls_credentials to also handle 802.1x certifications. This library provides various backends RAM, PS etc.
Describe alternatives you've considered
None.
Additional context

See also #78048.

Thanks. The Wi-Fi credentials still doesn't support Enterprise (certs) and might end up using TLS credentials as a backend.