Version 1.0.1 won't apply patches

This one is quite odd. I'm using cocapods-patch in one of my project and until recently (version 0.0.9), everything was working fine. After upgrading to version 1.0.1, the patches are no longer applied. To rule out any interference from the project, I've created a brand new xcode project to test out the issue.
My current setup:
cocoapods (1.11.2)
cocoapods-core (1.11.2)
cocoapods-deintegrate (1.0.4)
cocoapods-downloader (1.4.0)
cocoapods-patch (1.0.1)
cocoapods-plugins (1.0.0)
cocoapods-search (1.0.0)
cocoapods-trunk (1.5.0)
cocoapods-try (1.2.0)

Podfile is really simple:
plugin 'cocoapods-patch'

target 'podTest' do
  use_frameworks!

  pod 'TestFairy'
end

with a very simple change in the Testfairy Pod ( patches/TestFairy+1.29.2.diff) :
diff --git a/cocoapods-patch-20211108-50631-2i5wvk/TestFairy/TestFairy.h b/Pods/TestFairy/TestFairy.h
index 5ef4a77..eae7b8d 100644
--- a/cocoapods-patch-20211108-50631-2i5wvk/TestFairy/TestFairy.h
+++ b/Pods/TestFairy/TestFairy.h
@@ -5,6 +5,7 @@

 @protocol TestFairySessionStateDelegate <NSObject>
 @optional
+-(void)testChange;
 /**
  * Callback when a session has successfully started on TestFairy.
  */

and yet, after pod install, the patch is not applied.
Going a bit deeper into the issue, I've noticed that Pod::HooksManager.register('cocoapods-patch', :pre_integrate) do |context| never executes and the same goes for the :after_integrate hook. The pre and post install hooks still work fine. What's also strange is the fact that the pre integrate hook works when defined in Podfile itself.
Any ideas, what could be the cause of the issue?

Auto-applying patches on pod install is also not working for me on 1.0.1, but applying them manually from the command line still is

Same problem for me. Manually applying patches works, but auto-applying doesn't.

Thanks for the report! We're looking into it now -- seems to be a change in the CocoaPods internals.

For now we've released v1.0.2 that falls back to the previous way of applying patches while we try to get a fix merged in the main Cocoapods side.

@martin-dzuro @fasci has the issue been resolved for you?

@dcvz Yes, this resolves the issue for me. Thanks a lot for the fix/rollback!

@dcvz it's working very nicely. I've tried it on a live project as well and it's applying the patches correctly. Thanks!


Allow comparison function to be inlined. [phab:D444]

Created by zarko at 2015-08-03 20:00:56:
Average speedup is 1.07
(seconds)
unit 1	unit 2	unit 3	unit 4
base	73.787	661.703	72.317	42.476
this	73.578	598.758	63.228	40.327

shahms accepted this revision at 2015-08-03 20:09:02

zarko closed via commit fbe953ebbaf7375da824c9a716317bc8847fa242 at 2015-08-03 21:23:23


Add cairo_types.rs with a trait, an error (enum), a util and a CairoU…

…128 initial impl.

This change is

Codecov Report

Merging #854 (7971d9f) into main (8f0598c) will decrease coverage by 0.14%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #854      +/-   ##
==========================================
- Coverage   69.45%   69.31%   -0.14%
==========================================
  Files          41       42       +1
  Lines        5536     5547      +11
  Branches     5536     5547      +11
==========================================
  Hits         3845     3845
- Misses       1324     1335      +11
  Partials      367      367

Files Changed
Coverage Δ

crates/blockifier/src/abi/cairo_types.rs
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

crates/blockifier/src/abi/cairo_types.rs line 11 at r1 (raw file):

#[derive(Debug, Error)]
pub enum CairoTypeError {
    #[error("Felt {0:?} is too big to convert to {1:?}.")]

why '?`
Suggestion:
{}

crates/blockifier/src/abi/cairo_types.rs line 12 at r1 (raw file):

pub enum CairoTypeError {
    #[error("Felt {0:?} is too big to convert to {1:?}.")]
    ValueTooLargeForType(Felt252, &'static str),

Suggestion:
  ValueTooLargeForType{value: Felt252, ty: &'static str},

crates/blockifier/src/abi/cairo_types.rs line 33 at r1 (raw file):

}

impl CairoType for CairoU128 {

@giladchase  suggested removing the CairoU128 type if we have a trait.
Suggestion:
impl CairoType for u128 {

crates/blockifier/src/abi/abi_utils_test.rs line 53 at r2 (raw file):

    let overflowed_u128: BigUint = BigUint::from(1_u8) << 128;
    let overflowed_u128_as_felt = Felt252::from(overflowed_u128);
    let error = felt_to_u128(&overflowed_u128_as_felt).unwrap_err();

can you add an assert to show me how the error is formatted?
Code quote:
error

crates/blockifier/src/abi/sierra_types.rs line 64 at r2 (raw file):

impl SierraType for SierraU256 {
    fn from_memory(vm: &VirtualMachine, ptr: &mut Relocatable) -> Result<Self, SierraTypeError> {
        let low_val_as_felt = vm.get_integer(*ptr)?;

use  SierraU128::from_memory
Code quote:
  let low_val_as_felt = vm.get_integer(*ptr)?;

crates/blockifier/src/abi/abi_utils_test.rs line 53 at r2 (raw file):
Previously, barak-b-starkware wrote…
Done. I’ve added + Felt252::from(1_u8) at the end:
It prints:
panicked at 'assertion failed: `ValueTooLargeForType { val:<PHONE_NUMBER>20938463463374607431768211456, ty: "u128" }` does not match `SierraTypeError::ValueTooLargeForType { val: expected_val, ty: "u128" } if
expected_val == (overflowed_u128_as_felt + Felt252::from(1_u8))`'

BTW, it prints the exact same error msg (w/ the same ") when I replace the {val} with {val:?} and {ty} with {ty:?}.

it is because the assert prints the error.
notice that your error string is not in the message above.
assert_eq!(format!("{error}", "")

crates/blockifier/src/abi/sierra_types.rs line 71 at r3 (raw file):

    fn from_memory(vm: &VirtualMachine, ptr: &mut Relocatable) -> Result<Self, SierraTypeError> {
        let low_val = SierraU128::from_memory(vm, ptr)?.as_value();
        *ptr = (*ptr + 1)?;

this is already done by SierraU128::from_memory, right?
Code quote:
*ptr = (*ptr + 1)?;


Add custom Skybox

I Just think it would be a neat idea to make a custom skybox for the new star system as an example, since no other addon has one.

Added the one from the 7th image on this

Oh nice, thank you!


⚠ Samsung has degraded performance

In 28735fe, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2680 ms

Resolved: Samsung performance has improved in 05e95f4.


Reauthentication error

Describe the bug
Reauthentication is impossible. Opening the Amazon website from the addon will show an error.
It seems to be related to the cookiejar conversion between aiohttp and httpx.
Only way to get it going again is removing the integration and setting it up again.
To Reproduce
Steps to reproduce the behavior:

Reauthenticate

Expected behavior
Screenshots
System details

Home-assistant (version): latest
Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
alexa_media  (version from const.py or HA startup): 3.10.15
alexapy (version from pip show alexapy or HA startup): 1.25.3 (authcaptureproxy 1.1.1)
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: yes

Logs
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 220, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 219, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
    result = await result
  File "/config/custom_components/alexa_media/config_flow.py", line 1122, in wrapped
    return await cls.handler(request, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/authcaptureproxy/auth_capture_proxy.py", line 387, in all_handler
    resp = await getattr(self.session, method)(
  File "/usr/local/lib/python3.9/site-packages/httpx/_client.py", line 1736, in get
    return await self.request(
  File "/usr/local/lib/python3.9/site-packages/httpx/_client.py", line 1500, in request
    request = self.build_request(
  File "/usr/local/lib/python3.9/site-packages/httpx/_client.py", line 351, in build_request
    return Request(
  File "/usr/local/lib/python3.9/site-packages/httpx/_models.py", line 1099, in __init__
    Cookies(cookies).set_cookie_header(self)
  File "/usr/local/lib/python3.9/site-packages/httpx/_models.py", line 1792, in set_cookie_header
    self.jar.add_cookie_header(urllib_request)
  File "/usr/local/lib/python3.9/http/cookiejar.py", line 1367, in add_cookie_header
    attrs = self._cookie_attrs(cookies)
  File "/usr/local/lib/python3.9/http/cookiejar.py", line 1326, in _cookie_attrs
    self.non_word_re.search(cookie.value) and version > 0):
TypeError: expected string or bytes-like object

Additional context

"Latest" doesn't tell me anything. Try again.

Sorry, I assumed you'd be aware of the latest versions of the components. Have added the versions for you.

What happens is apparently filter_cookies returns SimpleCookie or BaseCookie while httpx expects a CookieJar
https://docs.aiohttp.org/en/v3.8.1/_modules/aiohttp/cookiejar.html
Did this work for you when you implemented it in https://github.com/custom-components/alexa_media_player/commit/598175f3e8297aea256a22417565df79638c1d8b?

Did this work for you when you implemented it in 598175f?

Yes.

What happens is apparently filter_cookies returns SimpleCookie or BaseCookie while httpx expects a CookieJar

Where are you seeing a call to filter_cookies?

Did this work for you when you implemented it in 598175f?

Yes.

Is it possible that back then you only tried to authenticate but not to reauthenticate? Because only then there will be cookies passed between aiohttp and httpx.

What happens is apparently filter_cookies returns SimpleCookie or BaseCookie while httpx expects a CookieJar

Where are you seeing a call to filter_cookies?

Right where you implemented it? https://github.com/custom-components/alexa_media_player/commit/598175f3e8297aea256a22417565df79638c1d8b#diff-46d832f19ab1f0952ac20eb0d870c53343adcea7636327a6dc16889f0704aecfL384
I was able to fix the initial issue like follows
            cookies = self.login._session.cookie_jar.filter_cookies(
                self.proxy._host_url.with_path("/")
            )
            cookies = {k: v.value for k, v in cookies.items()}
            self.proxy.session.cookies = cookies

It was then possible to log in through the auth capture proxy but after that another issue came up
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 220, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 219, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
    result = await result
  File "/config/custom_components/alexa_media/config_flow.py", line 1127, in wrapped
    return await cls.handler(request, **kwargs)
  File "/config/custom_components/alexa_media/lib/authcaptureproxy/auth_capture_proxy.py", line 404, in all_handler
    result = await run_func(test, test_name, resp, self.data, self.query)
  File "/config/custom_components/alexa_media/lib/authcaptureproxy/helper.py", line 123, in run_func
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/lib/alexapy/alexaproxy.py", line 65, in test_amazon_url
    self._login.session.cookie_jar.update_cookies(self.session.cookies)
  File "/config/custom_components/alexa_media/lib/alexapy/aiohttp/cookiejar.py", line 167, in update_cookies
    for name, cookie in cookies:
  File "/usr/local/lib/python3.9/_collections_abc.py", line 851, in __iter__
    yield (key, self._mapping[key])
  File "/usr/local/lib/python3.9/site-packages/httpx/_models.py", line 1882, in __getitem__
    value = self.get(name)
  File "/usr/local/lib/python3.9/site-packages/httpx/_models.py", line 1834, in get
    raise CookieConflict(message)
httpx.CookieConflict: Multiple cookies exist with name=session-id

I'm just going to remove the resume session path. It's too much effort to deal with due to the incompatibilities between aiohttp and httpx.
I also don't know how you have any aiohttp cookies to pass on to httpx. They were deprecated a year ago and should've been removed once you removed and readded the component.

https://github.com/custom-components/alexa_media_player/blob/dev/custom_components/alexa_media/config_flow.py#L383
Not sure what you mean by deprecated? All I'm doing is trying to reauthenticate via the auth capture proxy when the integration asks me for it.

aiohttp isn't used by the component and hasn't been used for at least a year. There's some legacy code from before the switch, but by now, no one should be having aiohttp cookies anymore.
Remove and readd the component. That is what the reauth will be moving forward.

Remove and readd the component. That is what the reauth will be moving forward.

Exactly what I'm doing for the past months every few weeks but that's more than inconvenient. I think the reason there being cookies in the aiohttp cookie jar might then be related to the second issue that came up when I fixed the first. That will call update_cookies on the aiohttp cookie jar with httpx' cookies after auth via the proxy.

Delete any pickle files in the custom component directory.

Or use the force logout option so it deletes the pickle file for you. Then relogin.  Proper logs would've shown this but you didn't provide any.

I always deleted the pickle file when I had to readd the integration and there's an oauth token set in the config entry and oauth_login is also true.
Which symptoms exactly? The issue when forced to reauth?

Reauth every few weeks; presence of a aiohttp cookie a year after the component stopped using it.

https://gitlab.com/keatontaylor/alexapy/-/blob/dev/alexapy/alexaproxy.py#L65
Cookie jar of aiohttp is populated right there and then persisted with pickle. Doesn't everybody have aiohttp cookies then when using the auth capture proxy?

I'll see what I can do. So the integration does solely rely on the retrieved oauth token now and does not need the cookies and pickle file?
Are you not using the integration yourself anymore or just not interested in maintaining it further?

I'll see what I can do. So the integration does solely rely on the retrieved oauth token now and does not need the cookies and pickle file?
Are you not using the integration yourself anymore or just not interested in maintaining it further?

It still uses the pickle to save the cookies.
I use it but I've never had the auth problems. I just am spending my time on other interests. Again, if I had time, I would've removed the reauth path and removed legacy login options. They generate too many repeat issues.

In case it helps someone.
I had the exact same problem you describe @larena1 (exact same logs). I tried what you proposed and had, again, the exact same result.
            cookies = self.login._session.cookie_jar.filter_cookies(
                self.proxy._host_url.with_path("/")
            )
            cookies = {k: v.value for k, v in cookies.items()}
            self.proxy.session.cookies = cookies

While investigating I found out that I had a remnant of a precious version in my configuration.yaml I had completly forgotten about :
alexa_media:
  accounts:
    - email: !secret amazon_user
      password: !secret amazon_password
      url: amazon.com

I then did this:

I removed this configuration ;
I restarted HomeAssistant ;
I removed the HACS integration ;
I added the HACS integration again (3.10.15) ;
I restarted HomeAssistant ;
I added the integration and configured it following the standard way (didn't touch any checkbox).
It then worked on the first try.

@alandtse thank you for your work. I enjoy it a great deal.


anchore-engine : no service heartbeat within max allowed time period

Is this a request for help?:

Is this a BUG REPORT or a FEATURE REQUEST? (choose one):
BUG REPORT
Version of Anchore Engine and Anchore CLI if applicable:
Anchore Engine v 0.2.2 (docker release)
What happened:
We tried to startup the anchore-engine but we noticed a lot of WARN messages from service_catalog
What did you expect to happen:
We would modify the hardcoded http endpoint configured into the messages.
Any relevant log output from /var/log/anchore:
The error are:
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8082'] - orphaning service
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8083'] - orphaning service
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] could not get/parse service status record for service: - exception: unsupported operand type(s) for -: 'float' and 'NoneType'
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8338'] - orphaning service
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8084'] - orphaning service
[service:catalog] 2018-06-12 17:12:23+0200 [-] [Thread-13] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time perio
 no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8228'] - orphaning service

What docker images are you using:
the latest version taken from dockerhub
How to reproduce the issue:
We restart the container anchore and after the bootstrap phase for all modules we noticed the errors.
Anything else we need to know:

hi @cello86
those warnings will appear if services with the listed hostid/url settings have registered at some point, but have not sent a heartbeat for some time.  if the hostid or hostname/port settings have changed, then those service entries can be cleared, but before that i’d like to make sire the currently configured sustem is healthy - can you run an ‘anchore-cli system status’ and share the output?
note that there wont be any functional issue with having stale service records present.
we will investigate the type warning as well

@nurmi The server doesn't respond to the request as reported below:
[root@dev-registry01 bin]# ./anchore-cli --url http://dev-registry01.test.local:8228/v1/ --u admin --p admin123! system status
Error: could not access anchore service (user=admin url=http://dev-registry01.test.local:8228/v1/)

Do we have to clear the database and restart the container with a clean situation?
Thanks,
Marcello

HI @cello86
You shouldn't have to clear anything (upgrade is supported between versions), but the error is indicating that there is a problem accessing the API service.  You can try running the command with '--debug' to see a bit more, and also we should look at the output of 'docker logs <your_anchore_engine_container>' to see if we can determine why the service is inaccessible.

HI @nurmi,
it seems that the service:catalog is using an old configuration for HTTP endpoint because the environment variable 'ANCHORE_HOST_ID is configured with "dev-registry01.test.local".
These are the logs after the startup of the anchore-engine.
[MainThread] [anchore_engine.configuration.localconfig/validate_config()] [WARN] no webhooks defined in configuration file - notifications will be disabled
[MainThread] [anchore_manager.cli.service/start()] [INFO] Loading DB routines from module (anchore_engine)
[MainThread] [anchore_manager.cli.utils/connect_database()] [INFO] DB params: {"db_pool_size": 30, "db_connect": "postgresql+pg8000://anchore:anchorepwd!@dev-registry01.test.local:5432/anchoredb", "db_connect_args": {"ssl": false, "timeout": 120}, "db_pool_max_overflow": 100, "db_echo": false}
[MainThread] [anchore_manager.cli.utils/connect_database()] [INFO] DB connection configured: True
[MainThread] [anchore_manager.cli.utils/connect_database()] [INFO] DB attempting to connect...
[MainThread] [anchore_manager.cli.utils/connect_database()] [INFO] DB connected: True
[MainThread] [anchore_manager.cli.utils/init_database()] [INFO] DB compatibility check: running...
[MainThread] [anchore_manager.cli.utils/init_database()] [INFO] DB compatibility check success
[MainThread] [anchore_manager.cli.utils/init_database()] [INFO] DB post actions: running...
[MainThread] [anchore_manager.cli.service/start()] [INFO] DB version and code version in sync.
[MainThread] [anchore_manager.cli.service/start()] [INFO] Starting services: ['anchore-catalog', 'anchore-simplequeue', 'anchore-api', 'anchore-kubernetes-webhook', 'anchore-worker', 'anchore-policy-engine']
[anchore-catalog] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-catalog
[anchore-catalog] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-catalog
[anchore-catalog] [anchore_manager.cli.service/startup_service()] [INFO]         /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-catalog.pid -n anchore-catalog --config /config
[service:catalog] 2018-06-13 08:07:08+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:catalog] 2018-06-13 08:07:08+0000 [-] [bootstrap] [INFO] initializing database
[service:catalog] 2018-06-13 08:07:10+0000 [-] [bootstrap] [INFO] Archive initialization complete
[anchore-simplequeue] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-simplequeue
[anchore-simplequeue] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-simplequeue
[anchore-simplequeue] [anchore_manager.cli.service/startup_service()] [INFO]     /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-simplequeue.pid -n anchore-simplequeue --config /config
[service:simplequeue] 2018-06-13 08:07:14+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:simplequeue] 2018-06-13 08:07:14+0000 [-] [bootstrap] [INFO] initializing database
[anchore-api] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-api
[anchore-api] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-api
[anchore-api] [anchore_manager.cli.service/startup_service()] [INFO]     /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-api.pid -n anchore-api --config /config
[service:apiext] 2018-06-13 08:07:19+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:apiext] 2018-06-13 08:07:19+0000 [-] [bootstrap] [INFO] initializing database
[anchore-kubernetes-webhook] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-kubernetes-webhook
[anchore-kubernetes-webhook] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-kubernetes-webhook
[anchore-kubernetes-webhook] [anchore_manager.cli.service/startup_service()] [INFO]      /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-kubernetes-webhook.pid -n anchore-kubernetes-webhook --config /config
[service:kubernetes_webhook] 2018-06-13 08:07:25+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:kubernetes_webhook] 2018-06-13 08:07:25+0000 [-] [bootstrap] [INFO] initializing database
[anchore-worker] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-worker
[anchore-worker] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-worker
[anchore-worker] [anchore_manager.cli.service/startup_service()] [INFO]          /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-worker.pid -n anchore-worker --config /config
[service:analyzer] 2018-06-13 08:07:30+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:analyzer] 2018-06-13 08:07:30+0000 [-] [bootstrap] [INFO] initializing database
[anchore-policy-engine] [anchore_manager.cli.service/startup_service()] [INFO] cleaning up service: anchore-policy-engine
[anchore-policy-engine] [anchore_manager.cli.service/startup_service()] [INFO] starting service: anchore-policy-engine
[anchore-policy-engine] [anchore_manager.cli.service/startup_service()] [INFO]   /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-policy-engine.pid -n anchore-policy-engine --config /config
[service:policy_engine] 2018-06-13 08:07:35+0000 [-] [bootstrap] [WARNING] no webhooks defined in configuration file - notifications will be disabled
[service:policy_engine] 2018-06-13 08:07:35+0000 [-] [bootstrap] [INFO] initializing database
[service:policy_engine] 2018-06-13 08:07:37+0000 [-] [bootstrap] [INFO] Registration complete.
[service:policy_engine] 2018-06-13 08:07:37+0000 [-] [bootstrap] [INFO] Checking feeds client credentials
[service:policy_engine] 2018-06-13 08:07:38+0000 [-] [bootstrap] [INFO] Feeds client credentials ok
[service:policy_engine] 2018-06-13 08:07:38+0000 [-] [bootstrap] [INFO] Checking policy engine db initialization.  Checking initial set of distro mappings
[service:policy-engine] 2018-06-13 08:07:38+0200 [-] [MainThread] [anchore_engine.services.policy_engine/_init_distro_mappings()] [INFO] Distro mapping initialization complete
[service:policy-engine] 2018-06-13 08:07:38+0200 [-] twistd 17.5.0 (/usr/bin/python2 2.7.5) starting up.
[service:policy-engine] 2018-06-13 08:07:38+0200 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
[service:policy-engine] 2018-06-13 08:07:38+0200 [-] Site starting on 8087
[service:policy-engine] 2018-06-13 08:07:38+0200 [-] Starting factory <twisted.web.server.Site instance at 0x7f76e0b5f638>
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-7] [anchore_engine.services.policy_engine/handle_feed_sync()] [INFO] init args: {'mythread': {'max_cycle_timer': 100000, 'min_cycle_timer': 1800, 'handler': <function handle_feed_sync at 0x7f76e137a7d0>, 'cycle_timer': 21600, 'last_return': False, 'taskType': 'handle_feed_sync', 'initialized': True, 'args': [], 'last_queued': 0}}
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-8] [anchore_engine.services.policy_engine/handle_feed_sync_trigger()] [INFO] init args: {'mythread': {'max_cycle_timer': 100000, 'min_cycle_timer': 300, 'handler': <function handle_feed_sync_trigger at 0x7f76e137a848>, 'cycle_timer': 3600, 'last_return': False, 'taskType': 'handle_feed_sync_trigger', 'initialized': True, 'args': [], 'last_queued': 0}}
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-8] [anchore_engine.services.policy_engine/handle_feed_sync_trigger()] [INFO] Feed Sync Trigger activated
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-8] [anchore_engine.services.policy_engine/handle_feed_sync_trigger()] [INFO] Feed Sync Trigger done, waiting for next cycle.
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-10] [anchore_engine.services.policy_engine/do_feed_sync()] [INFO] FIRING: feed syncer
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-10] [anchore_engine.services.policy_engine/do_feed_sync()] [INFO] Syncing configured feeds: ['vulnerabilities']
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-11] [anchore_engine.services.policy_engine.engine.logs/info()] [INFO] Starting feed update
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-11] [anchore_engine.services.policy_engine.engine.logs/info()] [INFO] Performing feed sync of feeds: ['vulnerabilities']
[service:policy-engine] 2018-06-13 08:07:42+0200 [-] [Thread-11] [anchore_engine.services.policy_engine.engine.logs/info()] [INFO] Syncing vulnerability feed
[service:catalog] 2018-06-13 08:07:08+0200 [-] [MainThread] [anchore_engine.configuration.localconfig/validate_config()] [WARN] no webhooks defined in configuration file - notifications will be disabled
[service:catalog] 2018-06-13 08:07:08+0200 [-] [MainThread] [anchore_engine.configuration.localconfig/validate_config()] [WARN] no webhooks defined in configuration file - notifications will be disabled
[service:catalog] 2018-06-13 08:07:08+0200 [-] [MainThread] [anchore_engine.services.common/makeService()] [INFO] initializing database
[service:catalog] 2018-06-13 08:07:10+0200 [-] [MainThread] [anchore_engine.subsys.archive.operations/initialize()] [INFO] Archive initialization complete
[service:catalog] 2018-06-13 08:07:10+0200 [-] twistd 17.5.0 (/usr/bin/python2 2.7.5) starting up.
[service:catalog] 2018-06-13 08:07:10+0200 [-] reactor class: twisted.internet.epollreactor.EPollReactor.
[service:catalog] 2018-06-13 08:07:10+0200 [-] Site starting on 8082
[service:catalog] 2018-06-13 08:07:10+0200 [-] Starting factory <twisted.web.server.Site instance at 0x7f87589bb200>
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8082'] - orphaning service
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8083'] - orphaning service
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] could not get/parse service status record for service: - exception: unsupported operand type(s) for -: 'float' and 'NoneType'
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8338'] - orphaning service
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8084'] - orphaning service
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8228'] - orphaning service
[service:catalog] 2018-06-13 08:07:16+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within allowed time period ([u'dockerhostid-dev-registry01.test.local', u'http://dev-registry01.test.local:8228'] - disabling service
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8082'] - orphaning service
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8083'] - orphaning service
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] could not get/parse service status record for service: - exception: unsupported operand type(s) for -: 'float' and 'NoneType'
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8338'] - orphaning service
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8084'] - orphaning service
[service:catalog] 2018-06-13 08:07:31+0200 [-] [Thread-16] [anchore_engine.services.catalog/handle_service_watcher()] [WARN] no service heartbeat within max allowed time period ([u'dockerhostid-anchore-engine', u'http://anchore-engine:8228'] - orphaning service
[service:catalog] 2018-06-13 08:07:42+0200 [-] "<IP_ADDRESS>" - - [13/Jun/2018:06:07:42 +0000] "POST /v1/events HTTP/1.1" 200 603 "-" "python-requests/2.17.3"

Hi @cello86 -
So far in the log output, I'm not seeing any particular issues that would result in your API service not starting up, but we may need to see a bit more - we're looking for the 'service:apiext' log lines that show the service coming up on port 8228, or some log output that is showing some problem with the apiext service not being able to come up (so far in the logs, it looks okay, but I suspect the logs we're looking for happen after the content you have posted above) - once that happens, you should be able to run the CLI.  You can also always check to make sure the processes are up and running as well with a 'ps axw', looking for a twistd process that corresponds with the output from the logs (e.g. "/bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-api.pid -n anchore-api --config /config")
the host_id configuration parameter is meant to mark a particular set of services with an 'instance' tag - it won't be used for functionality beyond the ability to get accurate reports from 'system status'.  It might help us if we could see your config.yaml (passwords removed), and we could help make sure everything looks okay.

The config.yaml used on our development environment is:
service_dir: '/config'
tmp_dir: '/tmp'
log_level: 'INFO'
cleanup_images: True
host_id: 'dockerhostid-${ANCHORE_HOST_ID}'
internal_ssl_verify: False
auto_restart_services: False
catalog_endpoint: 'http://${ANCHORE_HOST_ID}:8082/v1'

credentials:
  default_user: 'admin'
  users:
     admin:
      password: '*************'
      email<EMAIL_ADDRESS>      external_service_auths:

  database:
    db_connect: 'postgresql+pg8000://anchore:******@dev-registry01test.local:5432/anchoredb'
    db_connect_args:
      timeout: 120
      ssl: False
    db_pool_size: 30
    db_pool_max_overflow: 100

services:
  apiext:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8228
  kubernetes_webhook:
    enabled: True
    require_auth: False
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8338
  catalog:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8082
# NOTE: use the below external_* parameters to define the port/tls
# setting that will allow other internal services to access this
# service - if left unset services will use the above,
# e.g. http://<endpoint_hostname>:<port>
#    external_port: 8082
#    external_tls: False
    archive:
      compression:
        enabled: False
        min_size_kbytes: 100
      storage_driver:
        name: db
        config: {}
    cycle_timer_seconds: '1'
    cycle_timers:
      image_watcher: 3600
      policy_eval: 3600
      vulnerability_scan: 14400
      analyzer_queue: 1
      notifications: 30
      service_watcher: 15
      policy_bundle_sync: 300
      repo_watcher: 60
  simplequeue:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8083
#    external_port: 8083
#    external_tls: False
  analyzer:
    enabled: True
    require_auth: True
    cycle_timer_seconds: 1
    max_threads: 1
    analyzer_driver: 'nodocker'
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8084
#    external_port: 8084
#    external_tls: False
  policy_engine:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_HOST_ID}'
    listen: '<IP_ADDRESS>'
    port: 8087
#    external_port: 8087
#    external_tls: False
    cycle_timer_seconds: 1
    cycle_timers:
      feed_sync: 21600 # 6 hours between feed syncs
      feed_sync_checker: 3600 # 1 hour between checks to see if there needs to be a task queued

hi @cello86
Thanks!  This config looks fine, as long as you're setting the ANCHORE_HOST_ID environment variable to a valid hostname that can be looked up from within the anchore-engine container itself.  Just a few minor observations:

you shouldn't need to have the 'catalog_endpoint' parameter set, this is for special cases where you need to hardcode the catalog service location for unusual circumstances, but almost always the value set in the 'catalog' service section under 'endpoint_hostname' will suffice.

I noticed that your db_connect string has the value 'dev-registry01test.local' set as the DB hostname, but in earlier logs there was (unrelated) reference to 'dev-registry01.test.local', so I thought it would be worth a double check (note the lack of '.' in the db_connect hostname setting)

When you start up a service with this config, as long as ANCHORE_HOST_ID is set to a usable hostname, then I don't see any problem with configuration.  If the API service still isn't coming up, then we'll need to look closer at the log files to see the section after you see the twistd process for the apiext service starting up (and then any log entries that are prefixed with 'service:api').
A simple check is to bring up the service, and then from a shell inside the container:
# ps axwww | grep anchore-api
   59 ?        Sl     0:03 /usr/bin/python2 /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-api.pid -n anchore-api --config /config
#
# curl -u admin:foobar http://localhost:8228/v1/status
{
  "available": true,
  "busy": false,
  "db_version": "0.0.7",
  "detail": {},
  "message": "all good",
  "up": true,
  "version": "0.2.2"
}
#
# curl -u admin:foobar http://${ANCHORE_HOST_ID}:8228/v1/status
{
  "available": true,
  "busy": false,
  "db_version": "0.0.7",
  "detail": {},
  "message": "all good",
  "up": true,
  "version": "0.2.2"
}

Hi @nurmi;
I tried the command and all worked fine:
[root@e194b976a0aa /]# ps axwww | grep [a]nchore-api
   69 ?        Sl    12:42 /usr/bin/python2 /bin/twistd --logger=anchore_engine.subsys.twistd_logger.logger --pidfile /var/run/anchore-api.pid -n anchore-api --config /config
[root@e194b976a0aa /]# curl -u admin:**** http://localhost:8228/v1/status
{
  "available": true,
  "busy": false,
  "db_version": "0.0.7",
  "detail": {},
  "message": "all good",
  "up": true,
  "version": "0.2.2"
}
[root@e194b976a0aa /]# curl -u admin:***** http://${ANCHORE_HOST_ID}:8228/v1/status
{
  "available": true,
  "busy": false,
  "db_version": "0.0.7",
  "detail": {},
  "message": "all good",
  "up": true,
  "version": "0.2.2"
}
[root@dev-registry01 ~]#  curl -u admin:**** http://dev-registry01.test.local:8228/v1/status
{
  "available": true,
  "busy": false,
  "db_version": "0.0.7",
  "detail": {},
  "message": "all good",
  "up": true,
  "version": "0.2.2"
}

Into the log file the entries were present with the error but I don't know if we can ignore them.
Marcello

Hi @cello86
You can safely ignore those warnings - if you would like to clean up the services, you can get a list with
# anchore-cli system status

where you'll see output of the form
Service <service_type> (<host_id>, <base_url>): <status>

for any services that are stale/invalid, you can manually clear them out with
anchore-cli system del <host_id> <service_type>

Closing this ticket, we believe the issue has been resolved and behavior discussed


How do you connect a local Dappchain to the block explorer?

Having started the loom executable and getting

Starting RPC HTTP server on tcp://<IP_ADDRESS>:9999 module=query-server

I was trying to connect to it through the block explorer by modifying the App.vue file
 allowedUrls = [     'http://<IP_ADDRESS>:9999',     'https://prodwss2.delegatecall.com',     'https://prodwss.delegatecall.com',     'https://stagewss.delegatecall.com'   ]
but unfortunately no blocks show up. What am I doing wrong? Thanks!

Currently the blockexplorer is for delegatecall. We have a new branch for loom dAppchains that will be our end of the month

Okay, thank you for your prompt reply!


Remove a couple of spammy logs.

The HTTP-related logs get very spammy when etcd is being migrated or rebuilt and those errors are pretty descriptive anyway so the stack is less useful.
The info-level log for endpoint updates is spammy when we're at high scale across the whole cluster.

@Lukasa  This is the other half of https://github.com/Metaswitch/python-etcd/pull/7/files.  That fix makes the exception propagate but I found we were still spamming the log with not-so-useful stack traces for the IncompleteRead error.  I've trimmed that to only log the exception type/message instead.  I think that's fine because those exceptions are all pretty descriptive.
CCing @ed-harrison


Refactor the Editor and EditorStack interaction

While reviewing #5311 I noticed some things that I think could be improved:

Functions like save(also renaming), close, open(also opening a new_file) are handling in the EditorStack and propagated to the Editor plugin with signals
Editor plugin has functions like close_file_in_all_editorstacks, file_saved_in_editorstack, file_renamed_in_data_in_editorstack, that depends of the sender (a bad practice), and are somehow complex (block/unblock signals, check the editorstack id) and therefore error-prone
As the logic for opening/saving the file is called several times (one for each Editorstack open) the open/save functions have some logic for avoiding writing on disk several times, this make this functions unnecessarily complex.
At runtime the logic for opening/closing/saving will be duplicated causing more processing and memory usage (maybe not a big issue)

What I propose:

Opening, Closing, saving files should be handle for the Editor plugin (or a helper class attached to it)
EditorStack only will send a signal to the Editor it will close/open/save the file and send a signal to all EditorStacks to make the UI stuff (closing/opening a new the tab.. etc)

cc @goanpeca @ccordoba12 @jnsebgosselin

Sounds good @rlaverde the editor has always been a weird beast :-|

I agree that it is going to be easier to understand this way.
One of the thing I was wondering when working on PR #5311 was why there was a method close_file_in_all_editorstacks both in the editor and plugin that seemed to do the same thing.


Fine-Tuning: Different result between single GPU vs multi-GPU (DDP)

System Info
accelerate verion: 0.29.1
OS:
python version: 3.10
numpy version: 1.24.4
torch version: 2.1.0
transformer verion: 4.39.3
Accelerate configuration:
- `Accelerate` default config:
	- compute_environment: LOCAL_MACHINE
	- debug: false
	- distributed_type: MULTI_GPU
	- downcast_bf16: 'no'
	- gpu_ids: all
	- machine_rank: 0
	- main_training_function: main
	- mixed_precision: bf16
	- num_machines: 1
	- num_processes: 4
	- rdzv_backend: static
	- same_network: true
	- tpu_env: []
	- tpu_use_cluster: false
	- tpu_use_sudo: false
	- use_cpu: false

Sagemaker instance: ml.g5.12xlarge for multi-GPU , ml.g5.4xlarge for single GPU

Information

[X] The official example scripts
[X] My own modified scripts

Tasks

[X] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
below is the train_ddp.py script
import transformers
from trl import SFTTrainer
import torch, os, pandas as pd
from transformers import AutoTokenizer, AutoModelForCausalLM, BitsAndBytesConfig, AutoConfig
from peft import LoraConfig, AutoPeftModel, AutoPeftModelCausalLM
from datasets import Dataset, load_dataset
from accelerate import Accelerator

model_id = "google/gemma-2b"
bnb_config = BitsAndBytesConfig(
    load_in_4bit=True,
    bnb_4bit_quant_type="nf4",
    bnb_4bit_compute_dtype=torch.bfloat16
)

tokenizer = AutoTokenizer.from_pretrained(model_id, token=os.environ['HF_TOKEN'])
model = AutoModelForCausalLM.from_pretrained(model_id, quantization_config=bnb_config, device_map={"":0}, token=os.environ['HF_TOKEN'])

data = load_dataset("Abirate/english_quotes")
data = data.map(lambda samples: tokenizer(samples["quote"]), batched=True)

lora_config = LoraConfig(
    r=8,
    target_modules=["q_proj", "o_proj", "k_proj", "v_proj", "gate_proj", "up_proj", "down_proj"],
    task_type="CAUSAL_LM",
)

def formatting_func(example):
    output_texts = []
    for i in range(len(example)):
        text = f"Quote: {example['quote'][i]}\nAuthor: {example['author'][i]}"
        output_texts.append(text)
    return output_texts

trainer = SFTTrainer(
    model=model,
    train_dataset=data["train"],
    args=transformers.TrainingArguments(
        per_device_train_batch_size=1,
        gradient_accumulation_steps=4,
        warmup_steps=2,
        max_steps=10,
        learning_rate=2e-4,
        fp16=True,
        logging_steps=1,
        output_dir="outputs",
        optim="paged_adamw_8bit"
    ),
    peft_config=lora_config,
    formatting_func=formatting_func,
)
trainer.train()

trainer.save()

I have provided the correct options in config file using
accelerate config
after setting the config file I will execute the below line to start the training.
accelerate launch train_ddp.py
I'm not sure where I'm making mistake, but I can see train loss is decreasing and it is almost same as the single GPU training loss.
@muellerzr @SunMarc
Also, I cloned https://github.com/huggingface/peft and tried the example https://github.com/huggingface/peft/blob/main/examples/sft/run_peft_multigpu.sh this one is surprising showing trainable parameter as 9B, and throwing OOM error.
Additionally, I checked accelerate example, I can see only the training portion not the model saving section in the script
https://github.com/huggingface/accelerate/blob/main/examples/nlp_example.py
I feel I'm making some mistake while saving the model. Could you please help me to fix this?
Expected behavior
Expecting the model to produce the same result after fine-tuning in single GPU and multi-GPU.

Per the troubleshooting guide, please check your batch size to allocate per-GPU vs actual https://huggingface.co/docs/accelerate/basic_tutorials/troubleshooting

@muellerzr , I got OOM error when I used this example https://github.com/huggingface/peft/blob/main/examples/sft/run_peft_multigpu.sh however I reduced down to 1. I noticed when I ran the script, I noticed script printed number of trainable parameters as 9B for 2B gemma model.
I think we are deviating, can you please look into my script? when I fine-tune 2B gemma model with the above script in single GPU i'm getting the expected result. But when I fine-tune 2B gemma model with the above script in multi-GPU using DDP result is varying.

@muellerzr @SunMarc @pacman100 , can you please confirm me whether my above script is right to execute DDP in multi-gpu?
I kind a feel I'm making mistake somewhere, can you please help me?

Please try following my advice I said there, then if there are still issues please tell us. Your script looks fine.
On your single GPU version, increase the batch size by bs * n_gpus. Then it will be similar.
(And please don't ping all maintainers, when one has already responded to you)


Rethrow exceptions when codegen'ing catch clauses

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

Project coverage is 84.57%. Comparing base (acc91da) to head (305d557).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #305      +/-   ##
==========================================
+ Coverage   84.53%   84.57%   +0.04%
==========================================
  Files          23       23
  Lines       11439    11450      +11
  Branches     1586     1588       +2
==========================================
+ Hits         9670     9684      +14
+ Misses       1769     1766       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Don't pass --timeout on 2.7.

2.7's regrtest doesn't support --timeout.

Ah, whoops.  Thanks for catching that.


How would you bind an Array to an Element and notify the change, if you construct it by FactoryImpl?

If I create elements by FactoryImpl, and give an array as an argument, then I can not observe the change on the array, even if I use the recommended methods. I also tried to use notifyPath or the observer to catch the changeRecord, but it's always just observed on creation and not after.
Here is an example:
http://plnkr.co/edit/SUbJisDSF8hIYzb0z6Av?p=preview
The DOM-structure would show, that the elements array, which was used to create the element, had changed by any mutation. But it is not notified

Please ask questions like this on Stackoverflow or Slack.

It is not documented


[20.09] kdeApplications: expose missing packages, fix hydra

Motivation for this change
fixes nixosTests.plasma5
fixes https://github.com/NixOS/nixpkgs/pull/98657#issuecomment-701060595
fixes broken hydra eval  https://hydra.nixos.org/jobset/nixos/release-20.09#tabs-errors
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test plasma5

doing nix-shell -p hydra-unstable --run 'hydra-eval-jobs -I . nixos/release.nix' seems to be doing a normal hydra eval now, instead of immediately failing

plasma5 test passed, merging
20.09 was the only branch affected.


Pass the padding option.

I am encrypting a key on frontend using a public key and passing it to node.js server where node is decrypting it using RSA algorithm with PADDING 4. So when I pass my encypted key node server consider it as invalid key because it is not encrypted with padding.
Please let me know how can we do this using react-native-rsa module.

Hi,
I think the padding option is hard coded in the lib. I have to check and get back to you.
You can either fork it change the default padding or add an option to allow passing in padding type.
Hao Wang

On Oct 16, 2017, at 1:13 AM, Sachin678<EMAIL_ADDRESS>wrote:
I am encrypting a key on frontend using a public key and passing it to node.js server where node is decrypting it using RSA algorithm with PADDING 4. So when I pass my encypted key node server consider it as invalid key because it is not encrypted with padding.
Please let me know how can we do this using react-native-rsa module.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


EntityLink segment not allowed. Contact your administrator to enable it.

When using the current version of the helper to create a post in a community, with a reference to a file, I get the error "EntityLink segment not allowed. Contact your administrator to enable it". This does not seem to happen when I create posts internally (eg: when the networkId is null).  Has anyone else run into this, and if so, is it actually possible to "enable it" as the error message indicates, or is this a limitation of posting into a community?

Sorry, I don't recall that was a while ago.


Refactor main stryker classes

We now have the following data structure in the main stryker package:
|   ConfigReader.ts
|   ConfigValidator.ts
|   FileStatements.ts
|   globals.ts
|   InputFileResolver.ts
|   Mutant.ts
|   MutantTestMatcher.ts
|   MutatorFacade.ts
|   PluginLoader.ts
|   ReporterOrchestrator.ts
|   Sandbox.ts
|   SandboxCoordinator.ts
|   ScoreResultCalculator.ts
|   SourceFile.ts
|   stryker-cli.ts
|   Stryker.ts
|   TestableMutant.ts
|   TestFrameworkOrchestrator.ts
|   TranspiledMutant.ts
|
+---child-proxy
|       ChildProcessProxy.ts
|       ChildProcessProxyWorker.ts
|       messageProtocol.ts
|
+---coverage
|       CoverageInstrumenter.ts
|       CoverageInstrumenterStream.ts
|
+---initializer
|       NpmClient.ts
|       PromptOption.ts
|       StrykerConfigWriter.ts
|       StrykerInitializer.ts
|       StrykerInquirer.ts
|
+---isolated-runner
|       IsolatedRunnerOptions.ts
|       IsolatedTestRunnerAdapter.ts
|       IsolatedTestRunnerAdapterWorker.ts
|       MessageProtocol.ts
|       ResilientTestRunnerFactory.ts
|       RetryDecorator.ts
|       TestRunnerDecorator.ts
|       TimeoutDecorator.ts
|
+---mutators
|       ArrayDeclaratorMutator.ts
|       BinaryOperatorMutator.ts
|       BlockStatementMutator.ts
|       BooleanSubstitutionMutator.ts
|       ES5Mutator.ts
|       IdentifiedNode.ts
|       LogicalOperatorMutator.ts
|       NodeMutator.ts
|       RemoveConditionalsMutator.ts
|       UnaryOperatorMutator.ts
|       UpdateOperatorMutator.ts
|
+---process
|       InitialTestExecutor.ts
|       MutationTestExecutor.ts
|
+---reporters
|       BroadcastReporter.ts
|       ClearTextReporter.ts
|       ClearTextScoreTable.ts
|       DotsReporter.ts
|       EventRecorderReporter.ts
|       ProgressAppendOnlyReporter.ts
|       ProgressBar.ts
|       ProgressKeeper.ts
|       ProgressReporter.ts
|       StrictReporter.ts
|
+---transpiler
|       MutantTranspiler.ts
|       TranspilerFacade.ts
|
\---utils
        fileUtils.ts
        objectUtils.ts
        parserUtils.ts
        StrykerTempFolder.ts
        Task.ts
        TempFolder.ts
        Timer.ts

However, this is kind of a mess. It's difficult for people to see the architecture, the different layers and the design pattern. We need to improve this.

We've changed this a lot since the issue was first opened so I'm closing this issue for now.


write a draft for an abstract for odissei

@Astrid-p @jiqicn @kristinathompson
I have made a first attempt for an abstract for the ODISSEI conference. This is mostly focused on the model rather than the scientific side (i.e., the results of the simulation). I will try to add another one that is modelled more on Kristina's abstract based on the relevance of the type of data you can get with comma... not ready yet, but when it will be, it is going to be uploaded in the same file :)
we can discuss it on monday!
cheers

Thanks, Eva!
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Eva Viviani @.>
Sent: Thursday, June 8, 2023 2:07:12 PM
To: covid19ABM/comma @.>
Cc: Thompson, Kristina @.>; Mention @.>
Subject: Re: [covid19ABM/comma] write a draft for an abstract for odissei (Issue #46)
@Astrid-phttps://github.com/Astrid-p @jiqicnhttps://github.com/jiqicn @kristinathompsonhttps://github.com/kristinathompson
I have made a first attempthttps://github.com/covid19ABM/comma/blob/submissions/submissions/odissei.md for an abstract for the ODISSEI conference. This is mostly focused on the model rather than the scientific side (i.e., the results of the simulation). I will try to add another one that is modelled more on Kristina's abstract based on the relevance of the type of data you can get with comma... not ready yet, but when it will be, it is going to be uploaded in the same file :)
we can discuss it on monday!
cheers
—
Reply to this email directly, view it on GitHubhttps://github.com/covid19ABM/comma/issues/46#issuecomment-1582465793, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4VBXNZV7RNUCGLAV7TOKCTXKG57BANCNFSM6AAAAAAYYK744Q.
You are receiving this because you were mentioned.Message ID: @.***>

Final abstract for ODISSEI (poster):

COMMA: A microsimulation model exploring the relationship between lockdown policies and depression rates during the COVID-19 pandemic
During the COVID-19 pandemic, lockdowns decreased COVID-19-related mortality and hospitalizations, but also took a large toll on populations' mental health, particularly on depression. We hypothesized that depression rates during the pandemic could be associated with the duration, sequence, and severity of lockdown policies, as evidenced by the growing literature on the effects of lockdown on mental health issues.
To test this, we developed COMMA (COvid Mental-health Model with Agents), a microsimulation model based on an individual-level synthetic population derived from data of the Groningen area's lifelines biobank ((n=2,556), https://www.lifelines.nl/). This biobank provides rich socio-economic, demographic, activity, and health data, including depression onset and progression from pre- to post- pandemic periods. COMMA operates on a daily timestep, simulating a series of daily activities reflective of individual's characteristics and current lockdown policies. The type of daily activities allowed in the model is configured to reflect actual lockdown policies applied in the Netherlands, but the model accepts also hypothetical/alternative lockdown scenarios. These activities, varying in accordance with actual or hypothetical lockdown conditions, were calibrated to influence depression rates positively or negatively, based on the literature surrounding lockdown-induced mental health issues.
COMMA not only aids in confirming existing literature on mental health impacts of lockdown measures, but also offers a platform to explore potential alternative lockdown scenarios. This may help to shed light into mechanisms linking experiencing lockdowns and depression, and thus potentially inform future policies in case of a future pandemic.

Nice - thanks for doing so! I'll upload the 'public health' abstract in the coming days.
Best wishes,
Kristina
From: Eva Viviani @.>
Sent: 26 June 2023 11:09
To: covid19ABM/comma @.>
Cc: Thompson, Kristina @.>; Mention @.>
Subject: Re: [covid19ABM/comma] write a draft for an abstract for odissei (Issue #46)
Final abstract for ODISSEI (poster):

COMMA: A microsimulation model exploring the relationship between lockdown policies and depression rates during the COVID-19 pandemic
During the COVID-19 pandemic, lockdowns decreased COVID-19-related mortality and hospitalizations, but also took a large toll on populations' mental health, particularly on depression. We hypothesized that depression rates during the pandemic could be associated with the duration, sequence, and severity of lockdown policies, as evidenced by the growing literature on the effects of lockdown on mental health issues.
To test this, we developed COMMA (COvid Mental-health Model with Agents), a microsimulation model based on an individual-level synthetic population derived from data of the Groningen area's lifelines biobank ((n=2,556), https://www.lifelines.nl/). This biobank provides rich socio-economic, demographic, activity, and health data, including depression onset and progression from pre- to post- pandemic periods. COMMA operates on a daily timestep, simulating a series of daily activities reflective of individual's characteristics and current lockdown policies. The type of daily activities allowed in the model is configured to reflect actual lockdown policies applied in the Netherlands, but the model accepts also hypothetical/alternative lockdown scenarios. These activities, varying in accordance with actual or hypothetical lockdown conditions, were calibrated to influence depression rates positively or negatively, based on the literature surrounding lockdown-induced mental health issues.
COMMA not only aids in confirming existing literature on mental health impacts of lockdown measures, but also offers a platform to explore potential alternative lockdown scenarios. This may help to shed light into mechanisms linking experiencing lockdowns and depression, and thus potentially inform future policies in case of a future pandemic.

Reply to this email directly, view it on GitHubhttps://github.com/covid19ABM/comma/issues/46#issuecomment-1607037002, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4VBXNYKD5TWTMJTIQGWSR3XNFGRZANCNFSM6AAAAAAYYK744Q.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Adopt semver/tagging

Do we need releases as well, or are tags sufficient?

Turns out tags == releases. Started as of dfd6312d66021e392b6f6168f1878381286b0103.


Feat/add snippet all endpoint

Add option to get all snippets available to the user.
Docs: https://docs.gitlab.com/ee/api/snippets.html#list-all-snippets
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127696

@svanharmelen This is ready for a review


net/tcp/dup: do not start the tcp monitor if unestablished

Summary
net/tcp/dup: do not start the tcp monitor if unestablished
Add more sanity checks to avoid TCP moniter start fail if the
TCP handle unestablished, the dup(2) operation should work at any time
Signed-off-by: chao.an<EMAIL_ADDRESS>Impact

fd duplicate for child task
socket  O_CLOEXEC

Testing
static int nsh_waiter(int argc, char *argv[])
{
  while (1) sleep(100);
}

int main(int argc, FAR char *argv[])
{
  int fd = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);

  int pid = task_create("fork task", 100,
                  40960, (main_t)nsh_waiter, (FAR char * const *)NULL);

  while (1) sleep(100);
  return 0;
}

"fork task" should be create and runing as expected

linked issue:
https://github.com/apache/incubator-nuttx-apps/commit/801acce04ed427c6c7d52579a671367c6e0cf80b
https://github.com/apache/incubator-nuttx-apps/pull/619

@masayuki2009 please review the change.

@anchao
Build failed
====================================================================================
Configuration/Tool: ntosd-dm320/udp,CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABIL
  Enabling CONFIG_ARMV7M_TOOLCHAIN_GNU_EABIL
  Building NuttX...
socket/net_dup2.c: In function 'psock_dup2':
Error: socket/net_dup2.c:63:26: error: unused variable 'conn' [-Werror=unused-variable]
   63 |   FAR struct tcp_conn_s *conn;
      |                          ^~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:76: net_dup2.o] Error 1

@anchao
Build failed

Done.


HBASE-26924 [Documentation] Fix log parameter error and spelling error

Fix log parameter error and spelling error

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.


Human deployment in windows environment

Thank you sir for this amazing project, I've an issue if you could solve it or demystify it please,  I've run the demo online and everything worked well, but when I tried to clone the repo and run it on my local pc, I get lost , so could you share with me how to test human locally in windows? I mean what are the requirements? Etc.
Thank you sir.

install nodejs
pick one from below:

install human from npm: npm install @vladmandic/human
install git and clone human repo: git clone --depth 1 https://github.com/vladmandic/human
download snapshot from releases: https://github.com/vladmandic/human/releases

install dependencies: npm install

and you're ready to start developing your solutions
to run demo web server as well and not just library,
4. install dev dependencies: npm install --production=false
5. run it: npm run dev
6. follow instructions on the screen


Failed to ensure git is spawnable by backmerge process.

It appears that problems of #17 have not been fully solved yet as there are still some cases where spawning Git appears to be problematic.
The verification is working:
[9:06:24 AM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@kilianpaquier/semantic-release-backmerge"
[9:06:24 AM] [semantic-release] [@kilianpaquier/semantic-release-backmerge] › ℹ  Using git version: 'git version 2.45.2'.
[9:06:24 AM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@kilianpaquier/semantic-release-backmerge"

Semantic-release proceeds with analyzing the commits, executing a build of a Docker container (using brendangeck/semantic-release-kaniko), creating a GitLab release and then fails in the backmerge process again:
[9:10:31 AM] [semantic-release] › ℹ  Start step "success" of plugin "@kilianpaquier/semantic-release-backmerge"
[9:10:31 AM] [semantic-release] › ✘  Failed step "success" of plugin "@kilianpaquier/semantic-release-backmerge"
[9:10:31 AM] [semantic-release] › ℹ  Start step "fail" of plugin "@semantic-release/gitlab"
[9:10:33 AM] [semantic-release] [@semantic-release/gitlab] › ℹ  Commented on issue #xxxx: https://gitlab.com/[REDACTED]/-/issues/9.
[9:10:33 AM] [semantic-release] › ✔  Completed step "fail" of plugin "@semantic-release/gitlab"
[9:10:33 AM] [semantic-release] › ℹ  Start step "fail" of plugin "semantic-release-slack-bot"
[9:10:33 AM] [semantic-release] [semantic-release-slack-bot] › ℹ  Notifying on fail skipped
[9:10:33 AM] [semantic-release] › ✔  Completed step "fail" of plugin "semantic-release-slack-bot"
[9:10:33 AM] [semantic-release] › ✘  EGITSPAWN Failed to ensure git is spwanable by backmerge process.
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'marked-terminal' imported from /usr/local/lib/node_modules/semantic-release/index.js
    at packageResolve (node:internal/modules/esm/resolve:854:9)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:472:34)
    at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:214:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:253:12)
    at terminalOutput (file:///usr/local/lib/node_modules/semantic-release/index.js:29:43) {
  code: 'ERR_MODULE_NOT_FOUND'
}

The issue it comments on contains the following:
### Failed to ensure git is spwanable by backmerge process.

N2: Command failed with ENOENT: git --version spawn git ENOENT

semantic-release version: 24.2.0
semantic-release-backmerge: 1.5.2

Whut ... VerifyConditions works the first time but not the second time in success call 😰 ?

Whut ... VerifyConditions works the first time but not the second time in success call 😰 ?

To add to the weirdness: this appears to be related to the content of the Dockerfile of the project I am releasing 🤯 ..
On the original codebase it is failing (with the errors above), if I simplify the container by simply doing:
FROM nginxdemos/hello

The backmerge works fine.
If I put back my original content of the Dockerfile, the backmerge is failing again.
The semantic-release-kaniko plugin that builds and pushes the container isn't doing much besides generating arguments and running execa on /kaniko/executor.

Are you extending this Dockerfile ? https://github.com/brendangeck/semantic-release-kaniko/blob/main/Dockerfile

Are you extending this Dockerfile ? https://github.com/brendangeck/semantic-release-kaniko/blob/main/Dockerfile

No, the Dockerfile we use for running semantic-release looks like this:
FROM node:20.18.0-alpine3.20

# renovate: datasource=github-releases depName=chartmuseum/helm-push
ENV HELMPUSH_VERSION=v0.10.4

# Copy Kaniko executor from the Kaniko image
COPY --chmod=0775 --from=gcr.io/kaniko-project/executor:v1.23.2-slim /kaniko/executor /kaniko/executor

# Install helm binary
COPY --chmod=0775 --from=alpine/helm:3.16.2 /usr/bin/helm /usr/bin/helm

# hadolint ignore=DL3018,SC2015
RUN apk add --update --no-cache jq git docker-cli && \
    helm plugin install https://github.com/chartmuseum/helm-push --version "${HELMPUSH_VERSION}" || true

# Install buildx plugin for Docker
# renovate: datasource=github-releases depName=docker/buildx
ENV BUILDX_VERSION=v0.17.1
ADD --chmod=775 https://github.com/docker/buildx/releases/download/${BUILDX_VERSION}/buildx-${BUILDX_VERSION}.linux-amd64 /root/.docker/cli-plugins/docker-buildx

WORKDIR /

# Copy over dependencies needed by npm
COPY package.json package-lock.json /

# Install semantic-release plugins listed in package.json
# hadolint ignore=SC2016,DL3016,SC2046
RUN jq -r '.dependencies | to_entries | map("\(.key)@\(.value)") | .[]' /package.json > /deps.txt && \
    npm install -g --unsafe-perm $(cat /deps.txt) && \
    rm -f /deps.txt /package.json /package-lock.json && \
    npm cache clean --force

WORKDIR /workspace

ENTRYPOINT [ "/usr/local/bin/semantic-release" ]
CMD ["--help"]

I did some more debugging / testing.. Added in outputs of cwd and env, in both cases it is 100% the same so the Kaniko plugin (or Kaniko) has not modified either of these.
As a test I replaced brendangeck/semantic-release-kaniko with codedependant/semantic-release-docker in the Semantic-Release configuration and the backmerge worked fine with the original Dockerfile.
As the semanic-release-plugin only collect inputs (based on config +  envs), generates arguments and executes /kaniko/executor with those arguments it is starting to look that Kaniko itself might doing something that causes this issue in this plugin.

Well, fine by me if the issue is coming from another plugin 😂

It does indeed look like an issue caused by Kaniko. The first git --version runs and has 189 files in /usr/bin. The second run there are only 153, of which a few new ones that weren't in the first directory listing.
Seems that during the Kaniko build it overrides the files in the container Kaniko runs from.
This cannot be an issue of this plugin, so I'll close this issue.

Issue opened here https://github.com/brendangeck/semantic-release-kaniko/issues/19 following investigation


Core APIs leave for user to define

Arch related

arch_pause
arch_prefetch
arch_get_tls
atomic (function or macro)

OS related

os_alloc
os_dealloc
os_set_tls
os_futex_wait
os_futex_wake
os_clone
os_write
os_read

Proposal

asynchronisation (like os io_uring facilities, we can then write an executor for it)?
synchronisation (mutex, for example, std version provides a wrapper around pthread; no-std version provide a wrapper around raw futex)?

By this time, alloc and free functions are made in the following way (see src/alloc.c):

If PROJECT_CL_ALLOC_USE_EXTERNAL is defined, then these functions will not be provided within our library. Instead, our library will expect these functions to be linked in when it gets used in some project.
Otherwise, if PROJECT_CL_ALLOC_INCLUDE_IMPL is defined, then try looking for a alloc_impl.h
Otherwise, if PROJECT_CL_ALLOC_USE_LIBC is defined, just forward API calls to libc
Otherwise, if PROJECT_CL_ALLOC_USE_VALLOC is defined, use a valloc alike imlementation. This might be useful for some MCU platforms.
Otherwise, report error (via both santiy checks in src/defs.c AND #error directives in src/alloc.c)

I think this method can be shipped easily for other OS-related core APIs.

As the final decision has been made, I'll close this.


src/hostapi/alsa/pa_linux_alsa.c:52:29: fatal error: /alsa/asoundlib.h: No such file or directory  #include </alsa/asoundlib.h>

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

hi all:
it's successs when i build code for gcc . but i need to use arm-linux-gcc on my linux platform ,it's appear following error when  "gcc" is replaced by "arm-linux-gcc" :
root@ubuntu:/home/sdk-folder/third-party/portaudio# make
........
libtool: compile:  arm-linux-gnueabihf-gcc -c -g -O2 -DPA_LITTLE_ENDIAN -I./include -I./src/common -I./src/os/unix -pthread -DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION="" -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DPACKAGE_URL="" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=".libs/" -DHAVE_SYS_SOUNDCARD_H=1 -DHAVE_LINUX_SOUNDCARD_H=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=8 -DHAVE_CLOCK_GETTIME=1 -DHAVE_NANOSLEEP=1 -DPA_USE_ALSA=1 -DPA_USE_OSS=1 src/hostapi/alsa/pa_linux_alsa.c  -fPIC -DPIC -o src/hostapi/alsa/.libs/pa_linux_alsa.o
src/hostapi/alsa/pa_linux_alsa.c:52:29: fatal error: /alsa/asoundlib.h: No such file or directory
#include </alsa/asoundlib.h>
^
compilation terminated.
Makefile:227: recipe for target 'src/hostapi/alsa/pa_linux_alsa.lo' failed
make: *** [src/hostapi/alsa/pa_linux_alsa.lo] Error 1
then i am search alsa/asoundf.h but i can find it ,as follow:
xufu@ubuntu:/$ apt-file search alsa/asoundlib.h
libasound2-dev: /usr/include/alsa/asoundlib.h
libdssialsacompat-dev: /usr/include/dssi/alsa/asoundlib.h
can you gie me help
thanks！
What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <1.7.0>

Tell us what hardware you're using:

[y ] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[y ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi xuqifu,
It looks like you are trying to install ARM based PortAudio library and the issue is not really related to compiling the C++ SDK. Maybe it will be faster reaching to the PortAudio group. Meanwhile we will try to see if we can try to reproduce the issue. Could you provide exact steps on what you are trying?
Thanks
Priya

Closing due to inactivity. Please reopen if you have further questions.

sudo apt-get install libasound2-dev
solves this problem for x86


Fixed package.json who was invalid json

npm install --save-dev mildrenben/surface was failing

Thanks @blaze33 👍


[WebToolsE2E][Aspire][Safari] The apiservice/webfrontend project "Actions" content is displayed incomplete on MacOS.

INSTALL STEPS

Clean machine: Mac OS

Install SDK 9.0.100-rc.2.24474.11

Install Aspire 9.0.0-rc.1.24511.1

Apply the dotnet8 feed for Aspire 9.0

REPRO STEPS

Open CMD, create an Aspire Starter App using following commands:

dotnet new aspire-starter -o AspireStarterApp
cd AspireStarterApp

Dotnet run the project in CMD, and open URL in the Safari browser.
dotnet run
Click the apiservice/webfrontend project "Actions"

NOTE:

This issue does not repro on Edge browser, only on Safari.

ACTUAL
The content displayed in "Actions" is incomplete

EXPECTED

Assigned to you @JamesNK

Do you have a mac to test with?

No I don't. I'm going to give to you @adamint. However I think the bug and fix is probably in FluentUI.

After initial investigation, I agree with James. @vnbaaij could you take a look? This appears like a fluentui bug.

@adamint Create an issue in their repo.

After initial investigation, I agree with James. @vnbaaij could you take a look? This appears like a fluentui bug.

We do not have a mac to test with. As @JamesNK says, create an issue on our repo. We are rather tight on resources at the moment so not sure how fast we can do something with this. It's not like we can work on this full-time...

After initial investigation, I agree with James. @vnbaaij could you take a look? This appears like a fluentui bug.

We do not have a mac to test with. As @JamesNK says, create an issue on our repo. We are rather tight on resources at the moment so not sure how fast we can do something with this. It's not like we can work on this full-time...

Could I contribute a fix?

@adamint YES please!


jwt token validation

after user login, a token is provided for user to access resources

I mean skip the chapter's detail and advanced auth not the whole jwt part


Fix disableInactiveStructures & disableInactiveVolunteers

On the RefreshManager, disableInactiveStructures and disableInactiveVolunteers methods are commented because the implementation is wrong.
        // todo: we should disable those who are enabled=0 in pegass, not the ones missing
        // otherwise volunteers created manually will be deleted

#236


Material could not be found

Current behavior

Installation of the package and following readme.
Expected behavior

References resolve. or readme updated for proper usage.
How to reproduce it (as minimally and precisely as possible)

Create a new Uno project in VS 2019 (based on templates from extension)
Setup project for build of UWP (disabled by default)
Install Uno.Material
Follow to the letter the Readme.md for steps 1-4
Receive Errors
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0246	The type or namespace name 'Material' could not be found (are you missing a using directive or an assembly reference?)	App2.Droid, App2.UWP, App2.Wasm, App2.iOS, App2.macOS	C:\Users\Kylee\source\repos\App2\App2\App2.Shared\App.xaml.cs	47	Active
Environment

Nuget Package: Yes
Package Version(s): 1.0.0-dev.515
Affected platform(s):

[ ] iOS
[ ] Android
[ ] WebAssembly
[x] UWP
[ ] MacOS

Anything else we need to know?

Running VS 2019 16.7.5

Thanks for the report. Can you validate that your project's name does not ends by ".Uno"? If it does, it's the cause of this issue and will be fixed by Uno 3.1.

My solution is 'App2' and the sub projects are
'App2.Droid', 'App2.iOS', 'App2.macOS', 'App2.Shared', 'App2.UWP', 'App2.Wasm'

Also I have tried the 3.1 Uno.UI builds from other issues for other things I found. This issue is the same on both DEV and STABLE.

My apologies, I did not notice the app name. Then it could be something else.
Could you attach your solution you built to this issue ? We may have missed something else.

App2.zip

Thanks. You'll need to add Uno. in front of material to fix this issue, and change ms-appx:///Views/ColorPaletteOverride.xaml to ms-appx:///ColorPaletteOverride.xaml, as the path of the file in your application is at the root.
We'll adjust the documentation.

That's interesting cause intellisense suggested that and when I tried it there was the following error
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0012	The type 'ResourceDictionary' is defined in an assembly that is not referenced. You must add a reference to assembly 'Uno.UI, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.	App3.UWP	C:\Users\Kylee\source\repos\App3\App3\App3.Shared\App.xaml.cs	46	Active
Note that this is a different test project that I used to try to get around this problem

protected override void OnLaunched(LaunchActivatedEventArgs e)
        {
            // Set a default palette to make sure all colors used by MaterialResources exist
            this.Resources.MergedDictionaries.Add(new Uno.Material.MaterialColorPalette());

            // Overlap the default colors with the application's colors palette.
            // TODO: Replace ms-appx:///Views/ColorPaletteOverride.xaml with your resourceDictionary.
            this.Resources.MergedDictionaries.Add(new ResourceDictionary() { Source = new Uri("ms-appx:///ColorPaletteOverride.xaml") });

            // Add all the material resources. Those resources depend on the colors above, which is why this one must be added last.
            this.Resources.MergedDictionaries.Add(new Uno.Material.MaterialResources());

In the App2 project this resolves it. But my testing had that but didn't have success.

This i found has to do with the target SDK for UWP app. The default uno projects are 1809 but Material requires 1903


[fabric] Upgrade deployment from 1.4.x to 2.2.x

Signed-off-by: Mohitv<EMAIL_ADDRESS>Changelog

Add Upgrade deployment of Hypeledger Fabric deployment to 2.2.x. The documentation is available in docs folder at /docs/source/operations/upgrade_fabricnetwork_1.4.x_2.2.x.md

Reviewed by
@sownak @jagpreetsinghsasan
Linked issue
#1845

Please squash merge the commits into 1 and re-request for review.
Until you hit the re-request review button, the reviewers will not be sure if you are done doing the changes or not.
Here's how to do it (you can see the re-request review button on the right side of the screenshot)

@Mohitv the PR looks perfectly fine to me. Just one last comment, to squash merge the commits into one.

The code is test ok, closing this issue with a bug create for a minor fix #2142


Removed python 2.7 from testing

Pull Request Test Coverage Report for Build 93

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.594%

Totals

Change from base Build 92:
0.0%

Covered Lines:
183

Relevant Lines:
202

💛  - Coveralls


How to change the characters in the interface of live share plug-in into Chinese?

As shown in the figure above, for example, "Participants" has been revised into Chinese, but I did not find the keyword of "Participants" in the plug-in.

This issue should now be resolved. Please re-open it if you're still experiencing this problem. Thanks!


Fix: remove server.browser.js in favor of export mapping to server

The browser subpath is for browser/client bundles. The server.browser path from Next.js is requested in Node.
Adding the corresponding export mapping to the same server file addresses the issue in Next.js 12.1.6.

@JoviDeCroock I'd appreciate it if you can take a look at this. The current server.browser.js file/reference does not fix the issue in Next 12.1.6.

This looks wrong 😅 you both remove the contents of the file as well as introduce a new mapping. Next should not take browser for a node environment

@JoviDeCroock I'm not following what you meant. There's no need for an additional file since the expectations from the server.browser.js are the same exports as server, so the mapping is all it's needed. Next 12.1.6 is requesting the file in Node, not through webpack, meaning the browser subpath will not match, and not find the current server.browser.js file.
This behavior was masked by this merged PR in Next https://github.com/vercel/next.js/pull/36749, but the issue remains that if you do a require('react-dom/server.browser'). It will throw an error.

but why would they use require('server.browser') that's just wrong 😅 we have export-maps now

@JoviDeCroock Export maps are behaving as expected, though. The browser field will not clear in Node, and the path would have to be server/browser not server.browser. I don't think there's a current expectation to load that file in the browser, if that's the case, then a browser field would need to get added to server.browser mapping.

Heh, I honestly really don't like this but if they intend to use it that way this is mainly used for next either way 🤷♂


The Equals of the ClientConfigurationData instance does not reach the expected result

Is your enhancement request related to a problem? Please describe.
The authentication in ClientConfigurationData does not implement equals and hashcode, resulting in two instances of the same configuration not being equal.
Describe the solution you'd like
Add equals, hashCode methods to all Authentication implementation classes.
Describe alternatives you've considered
In ClientConfigurationData in the equals, hashCode method to ignore the field authentication.
Additional context
Add any other context or screenshots about the feature request here.

In ClientConfigurationData in the equals, hashCode method to ignore the field authentication.
Does it mean that Conf's with different authentication only can be considered the same? In our scenario, this would result in Clients with different authentication policies but otherwise the same attributes being shared by the same cache.

In ClientConfigurationData in the equals, hashCode method to ignore the field authentication.
Does it mean that Conf's with different authentication only can be considered the same? In our scenario, this would result in Clients with different authentication policies but otherwise the same attributes being shared by the same cache.

The ClientConfigurationData stores the parameters for creating the authentication object. Of course, there are also methods to set the authentication object directly.

How about adding @EqualsAndHashCode to each implementation class of Authentication?

How about adding @EqualsAndHashCode to each implementation class of Authentication?

Most of the situations yes, there are also special cases that need to be dealt with. And corresponding tests need to be added for them.

Closed as stale. Please open a new issue if it's still relevant to the maintained versions.


feat: add execroot & runfiles symlink guards to js_binary

Fixes https://github.com/aspect-build/rules_js/issues/114
The fs patches here have been modified from their original implementation in rules_nodejs https://github.com/bazelbuild/rules_nodejs/blob/173a0252f273de48a6a237518e9cb0d9854cb8e6/packages/node-patches/src/fs.ts.
The have been improved to allow following symlinks within the sandbox, which is required for finding deps in a symlinks node_modules structure. Since the sandbox (on macos) is a tree of symlinks that all point back to their counterparts outside of the sandbox, the old implementation prevented following symlinks entirely (akin to passing `--preserve-symlinks) since every follow was an escape from the guarded sandbox.
In this implementation, if the readlink escape is a symlink to a symlink then we readlink the escaped symlink. For lstat we do the same. For realpath, if we the relative path from the link to the realpath can be remapped into the escaped root then it is.
In rules_js, the guards are setup to protect the execroot (which protects the sandbox when there is one and protects from escaping into the source tree when there isn't) and to protect the runfiles tree for the js_binary in the build, test or run target since that is a symlink tree as well. This is simpler than what was done in rules_nodejs which was to protect all of the dynamically linked node_modules trees.

let's add the tests too, otherwise it's too tempting to leave it for later...

Done. Brought unit tests in from rules_nodejs for the patches


drone exec ignores when: local: false

Drone version:
.6
Repro steps:

create a .drone.yml file with some steps that have secrets
add { when: { local: false }}  yml equiv to the steps with secrets
run drone exec

if will try to still run the containers that are marked for local: false
from a conversation with @bradrydzewski it looks like this may have been lost from .5 but should get brought back into .6

https://github.com/cncd/pipeline/pull/4 should fix this. It add the functionality that got removed when the pipeline was moved to a lib.

fixed

I don't see anything about 'local:true|false' in the documentation anymore, and I'm still seeing the same bug as described. Setting 'when:local:false' doesn't seem to affect local execution, the steps will still run. Can someone verify this is no longer a working feature?

If you want to control which pipeline are executed locally you can use the include and exclude flags. See https://docs.drone.io/quickstart/cli/#run-specific-steps


SpikeGLXIO in neo with rawio implementation.

TODO:

test
validate gains with developer
annotation
channel location

Hello @samuelgarcia! Thanks for opening this PR.
As the main SpikeGLX developer I would have some technical questions for this IO implementation.

could you have a look to the "gain" implementation ? See
https://github.com/NeuralEnsemble/python-neo/pull/896/files#difffcafb569fbfc7e1fbab7061b784b15580bfffb350a0eca6866585552f7c1cfdcR195-R220
I am not totally sure to follow you logic for the gain in the spikeglx-offline-tools you offer.
For the imec part I think it is OK but I would need some validation. For the nidacq part it is more fuzzyfor me.
In neo we have a "t_start" which represent the time stamp of a very first sample for each timeseries so we can align several
timeseries. In case of multi segment with naming "gt0",  "gt1", "gt2", is there somewhere in the meta file something to
retrieve theses timestamps ?

I put some files at gin gnode.
It is quite big but not so.

Ready to review (and merge if test pass)

I don't plan to fix the TODO list in this PR.
It is a note for later.

Hi Julia.
Thanks a lot for this review.
Sorry the "typos"...

About the uncertainty in the time aligneent between object which is not handle in the spikeglx code nor in the spikeinterface code: I propose to merge in actual state but to be very very clear in the doc.
When spikeglx teams will have time to help on this we will fix it.
I think that we can implement utils function that handle time alignement with pulse train that could be applied here.

Julia.
i made some ultimate changes and create an issue for this

CircleCI is still failing due to missing output. I think rebasing onto master should fix this issue, as this was adressed in https://github.com/NeuralEnsemble/python-neo/pull/919

@samuelgarcia Thanks for the updates! Looks very good to me now. I will merge as soon as the tests finished.


Permissions constraints

Resolves #687
To test:

Upload two models
Create a few plans using each model
Go to http://localhost:8080/console/data/AerieMerlin/schema/public/tables/plan/browse and change one plan's owner to be the owner that you want to test with
Log in as that owner and switch to the "user" role from the top right dropdown
Navigate to http://localhost:3000/constraints
Create a new constraint
Verify that only plans that your user is owner of are selectable from the "Plan" dropdown
Verify that only models that have instances of plans that your user is owner of are selectable from the "Model" dropdown
Navigate back to http://localhost:3000/constraints
Verify that the constraint that you created is editable
Log out and log in with a different username and switch to the "user" role again
Navigate back to http://localhost:3000/constraints again
Verify that the constraint that you previously created is no longer editable/deletable
Navigate to the edit view of that constraint by manually going to: http://localhost:3000/constraints/edit/[CONSTRAINT ID]
Verify that everything is read only

Getting this error when trying to save a constraint I had previously made.

Getting this error when trying to save a constraint I had previously made.

So I think this might need some more digging in to. If I save as "admin" I don't get the error. If I'm a "user", then I get it. But as far as I understood, a model_id of null was valid if the plan_id was provided. @camargo Do you know what might be the issue here?

@AaronPlave @camargo the null model_id issue has been fixed by https://github.com/NASA-AMMOS/aerie/pull/1000 🎉


Neovim filetype detection stopped working after d608b76

I left a comment in the (huge) commit, but I though opening an issue to give some more details:
after d608b76 filetype detection doesn't work for me.
For any type I open, I get filetype unkown which cascades into missing syntax highlighting, missing lsp attach etc etc..
The only way to make it work is to manually specify the filetype for every file I open...
This commit is huge and I'm no nvim expert so I don't think I can't understand what's causing the problem, but rolling back to the parent commit solves the issue for me.

after d608b76 filetype detection doesn't work for me.

I did experience something similar: Some of my FileType autocmds on custom filetype didn't work as expected. Sometimes either vim.bo.filetype or vim.bo.buftype was just not set at the proper timing: It seems to be set since when you run print(vim.bo.filetype)(or set ft?) on the buffer you want to test with you will get the value. But your autocmds just cannot detect them. And my conclusion is: The problem seems to be related to the fact that those plugins apply some async techniques in their code.
To resolve this, my current workaround is: Say you have an FileType autocmd on filetype custom and the purpose of this autocmd is to do some initializations for plugin A, then you should instead do those initializations in A's keymap. Since we always call a keymap far later than the vim.bo.filetype/vim.bo.buftype being set, you're promised to always get the correct value.

For any type I open, I get filetype unkown which cascades into missing syntax highlighting, missing lsp attach etc etc..

Are you getting a stack trace when seeing that? If so please paste it here, if not how is it appearing? This is most likely an autocmd you have setup to run on startup which doesn't work with the buffers created by nvim-dap-ui

And my conclusion is: This problem seems to be related to those async techniques(you can find it by following the link from OP here) in their code.

If you're seeing issues please open a bug report but I'd be surprised if any of the async code has any effect on your personal config :smile: I'd say it's more likely that the issue is coming from buffers being created on setup rather than when first opened like they were previously

Are you getting a stack trace when seeing that? If so please paste it here, if not how is it appearing? This is most likely an autocmd you have setup to run on startup which doesn't work with the buffers created by nvim-dap-ui

Well, no I don't get any particular error/message/stack-trace.
What seems to be reproducible is the following:

start nvim to open a file
filetype is not set
re-open the same file from nvim without exiting
filetype is now set and everything (syntax highlighting, lsp etc) works.

Please see the short attached clip with a rust file as an example (but the same happens with cpp or loa or whatever filetype I'm working with...)
As I said I'm no nvim expert so that's pretty much it as far as my diagnosing capabilities go, but I'll be happy to perform any additional tests if you can guide me through.
https://user-images.githubusercontent.com/589164/215320945-3e828105-3619-4223-9207-0325f9d1bb09.mov

This could be a tonne of things I'm afraid, you'll have to check your own config for the conflict. If you can reproduce with a minimal init.lua then I can help further
Here is a sample that can be run with nvim --clean -u minimal.lua
-- ignore default config and plugins
vim.opt.runtimepath:remove(vim.fn.stdpath("config"))
vim.opt.packpath:remove(vim.fn.stdpath("data") .. "/site")
vim.opt.termguicolors = true
vim.opt.laststatus = 0

-- append test directory
local test_dir = "/tmp/nvim-config"
vim.opt.runtimepath:append(vim.fn.expand(test_dir))
vim.opt.packpath:append(vim.fn.expand(test_dir))

-- install packer
local install_path = test_dir .. "/pack/packer/start/packer.nvim"
local install_plugins = false

if vim.fn.empty(vim.fn.glob(install_path)) > 0 then
  vim.cmd("!git clone https://github.com/wbthomason/packer.nvim " .. install_path)
  vim.cmd("packadd packer.nvim")
  install_plugins = true
end

local packer = require("packer")

packer.init({
  package_root = test_dir .. "/pack",
  compile_path = test_dir .. "/plugin/packer_compiled.lua",
})

packer.startup(function(use)
  -- Packer can manage itself
  use("wbthomason/packer.nvim")

  use({ "mfussenegger/nvim-dap" })

  use({
    "rcarriga/nvim-dap-ui",
    requires = "mfussenegger/nvim-dap",
    after = "nvim-dap",
    config = function()
      require("dapui").setup({})
    end,
  })

  if install_plugins then
    packer.sync()
  end
end)

vim.cmd([[
command! DapUIToggle lua require("dapui").toggle()
]])

Here's a repro
local root = vim.fn.fnamemodify("./.repro", ":p")

for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  --"folke/tokyonight.nvim",
  {
    "mfussenegger/nvim-dap",
    dependencies = { "rcarriga/nvim-dap-ui" },
    event = "BufReadPost",
    config = function()
      require("dapui").setup()
    end,
  }
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("habamax")

It seems to only occur if dap and dapui are loaded lazily with BufReadPost. Seems like there is a race condition with this autocmd where filetype detection ends up not running if dapui is loaded and set up on it as well.

Oh, many thanks for investigating this.
I can confirm it is indeed something race-y, since sometimes the problem just disappears by itself and I keep working for hours before it reappears again.
As I'm using Astronvim, which handles dap and dap-ui, I'll refer to this discussion and see if they can apply the suggested workaround to their configuration.

Closing this as the issue is with core and there is a workaround

Is there an upstream bug we can follow?