Keypad Support

Allow physical keypad devices in for the alarm arming and disarming, they devices are there just not really a integration that works good

Checklist

[X ] I checked for similar existing requests (both open and closed) before posting.
[X ] My request is generic, other users may benefit from it too.

Proposal
Additional info
allowing to use a card but also allowing the use of the buttons on the keypads to do the arming, disarming and pin entry

The Z-Wave Keypad Ring Keypad v2 works perfectly with the according blueprint and synchronizes with Alarmo in both directions.

I don't understand the request.
What do you mean with the list you shared? I don't recognize it.

I use the Xfinity XHK1-UE Keypads without issue and fully supported by using Zigbee2MQTT and Node Red as an interpreter. I can share the flow if anyone would like it. It can likely be modified for other non natively supported keypads. I use two of these now with two tablets running MQTT Alarm Panel.

Adding this, correct me if I am wrong but Alarmo is literally just an extension of Alarm in HA, HA is the actual core alarm system? You can control Alarmo by different means and MQTT is one of them and then Alarmo controls HA Alarm? While not impossible, Alarmo can not likely accommodate hardware or EVERYONE's hardware directly and asking for that would be insane. It does one thing and one thing well, it allows you to graphically setup and control what's necessary to run and use the Home Assistant alarm feature, nothing more, the rest is up to you and or Home Assistant.

This statement is a very good point that I wish everyone would realise.
Fact is that HA introduced a binary_sensor device type which standardises the behaviour for on/off sensors.
However for remotes/keypads there is not such uniformity, so it would be very hard for me to create support for it inside Alarmo which would work across multiple brands and types.
The alarm_control_panel entity type in HA is misleading, since it might sound like a very good fit for a keypad, in fact this type is for complete alarm systems instead (implementing their own rules and logic).
The best offer I can make is an easy way to set up automations involving alarmo and external keypads.
There are plans for adding a panel to alarmo for setting up simple tasks for automatic arming/disarming through external devices. But bear in mind this might never reach the same experience as tailor-made automations/blueprints can.
If you could revise your request to some specific points that could be added to alarmo to facilitate linking it with a keypad, I would be happy to hear.

The list is the device entities I think it's called, I am a little new to the who ha system I'm a migrating hubitat user.
An yes I'll update the post when I get home and if I can't provide more I'll close it.

The biggest issue I have is I made a mistake in my initial setup and didn't get a mqtt compatible ZigBee doggle so now I have to go and get that sorted to get the compatatability I want.

What dongle do you have?

Nortek HUSBZB-1,
Was a bad purchase lol.
The keypad was the Iris V2 keypad, it says it's centralite ilo2 I think it is.
I see that it can arm and disarm the system but my issue is now I have now like central code manager or anything that links my locks and keypads to users which I don't even think exists in HA which is kinda disappointing thing as they did have that in hubitat stock.

And the reference was it asked for what device you can arm and disarm in the alarmo menu and I could not see the keypad as a option like you mentioned.
From what I'm gathering here is that the physical keypad can disarm the ha system which is tied to the alarmo front end and so it can work.
Please correct me if I'm wrong.

Nortek is a good combo stick for HA ZHA, I use that stick for my non security zigbee stuff and z-wave stuff. Get second stick for security to use with Zigbee2MQTT, conbee ii is good out of the box and has really good range and stability compared to all CC variants I have ever tried, whereas any CC I tried had bad range, died or just had sensors drop off a few days later, all my xfinity sensors are zigbee 1.2 so that might play into that?
Welcome to HA, I started with zigbee and HA a year ago doing some work at a hotel that was using zigbee and the bug bit me, since then I have learned way too much and started developing hardware and software for my home and hope to release to the community once it matures some.
I have the same Iris (Xfinity branded) keypad around here somewhere from what it looks like? The Centralite 3400?, I know it works with Zigbee2MQTT appeared to be the same as my other keypads though never tried it with my NodeRed setup. I'll test it shortly and let you know, should work and if so all you need is that other dongle and my NodeRed flow. You can contact me for help setting those things up, I just want to help out where I can to contribute back to the community in ways that I currently can.

From what I'm gathering here is that the physical keypad can disarm the ha system which is tied to the alarmo front end and so it can work.

Alarmo creates alarm_control_panel entities which can be armed/disarmed within HA through services.
I don’t know how your keypad looks like in HA (if anyone knows a place where to buy it in the EU I would like to know).
But the idea is to create automations to have the alarmo entity arm when the keypad is armed, etc.
If it would be helpful if alarmo has built-in support for ‘syncing’ state with another/external alarm_control_panel, I could work this out.

@f3rr311 I can not find my old keypad that is similar to the Iris but am positive it was the same inside of Zigbee2MQTT as my current keypads and confirmed as much looking it up on zigbee2mqtt website.
@nielsfaber Here is the Zigbee2MQTT link on my current keypads
https://www.zigbee2mqtt.io/devices/XHK1-UE.html
Here is the link to the 3400-D which is the same as the Iris I think that f3rr311 is using.
https://www.zigbee2mqtt.io/devices/3400-D.html
From what I can see between these and all other current keypads supported by Zigbee2MQTT is that they all support the same ZCL specifications and even the payloads appear to be the same.
Valid mode values as per ZCL specifications are disarm, arm_day_zones, arm_night_zones, arm_all_zones, exit_delay, entry_delay, not_ready, in_alarm, arming_stay, arming_night, arming_away.
@nielsfaber It looks like the Iris is discontinued as far as finding one, I don't mind sending you an XHK1-UE keypad to help with development if you can not find a suitable device locally as they are only $40 new here from Xfinity.

@nielsfaber I saw you are based in the Netherlands, just like I am. I am interested in the keypad connection with alarm as wel. If neede you could borrow one of my xfinity keypads. They are unavailable in shops in the Netherlands.  Guess it will safe shipping and import Costs. I got 2 diverent versions at home at the moment.

Owning one would be the best starting point to develop (and maintain) built-in support for it.
@erwintenbrink Borrowing one would be a good option, however I cannot commit to a timeline (my spare time for this project varies) so you might need it back before things are done. And since Alarmo is quite new (and knowing things in HA change quite often) I think the risk for future changes is quite high, so from maintenance point-of-view I think I would rather own one myself.
@EdwardSoaresJr If you could send one from US this would be great as I still haven't been able to find a shop myself.
However for me $40 + shipment + vat (I guess total €60) is still a bit steep, especially since I don't think it will become part of my home security system (I operate Alarmo from Google Home).
My proposal is to divide the cost between all stakeholders, I count 4 here including myself.
I really hope people don't take this as greedy, please consider i am probably spending ~10 hours of free time to make this happen.
It would come down to around €15 per person, which I think is a pretty small amount.
There is also a previous topic about this (https://github.com/nielsfaber/alarmo/issues/202), perhaps they are willing join as well, making the cost even lower.
If you do want to participate, please donate some coffees and mention that it is intended for this little experiment, I will arrange things with Edward once the amount is reached (otherwise I will refund all).
I don't want to make people feel obliged to contribute, it's just a proposal.
Also I cannot give guarantees for success, so there is also a risk (as with any crowdfunding).
Ofcourse I will keep you up-to-date with the progress and the result.

@nielsfaber my email is on my GitHub profile, contact me so we can work out some details.

@nielsfaber i got some of these keypads placed on marktplaats. If i see your calculation above i think that will be cheaper. Maby get in touch in private?

Well this is embarrassing I am sitting here trying to pair a custom device I just flashed firmware to and my old keypad paired with the system. It is in the house somewhere :)

Id love to support the cause. Ill buy another one and mail it to you if that would help. Alarmo is amazing and I would love to see the keypad get integrated.  my email is in my profile.

@jeffphilly Little has changed regarding this feature in the past month.
My proposal for crowdfunding to buy a keypad to support the development has not led to any results yet.
Which model of keypad would you like to see integrated?
I saw just now that for the Ring Alarm Z-wave Keypad someone already made a blueprint for Alarmo, it looks quite promising.
So far we have been discussing the Centralite 3400 / Xfinity XHK models here (seem to be quite the same, both are zigbee based), I might either create a blueprint for them or integrate support within Alarmo.
If someone else is willing and able to create and maintain a blueprint for these devices (and owns one), that could also be a good solution.
I don't expect you to buy and send such a device own your own due to the costs involved, but it would definitely put things in motion. Your email address is not exposed on your github profile, so I cannot contact you directly.

@nielsfaber Just added my email to my profile, Shoot me an email and I will figure out how to get you one. Alarmo is amazing and if I can contribute in this small way i would love it!

FIY: there is a blueprint which is working quite good:https://community.home-assistant.io/t/zigbee2mqtt-sync-keypad-and-alarm-control-panel-states/345311/19
just be aware, there is an issue with zigbee2mqtt 1.22.2-1

For who is still interested in this: I made a blueprint to connect a zigbee2mqtt keypad to Alarmo: https://community.home-assistant.io/t/zigbee2mqtt-control-alarmo-via-keypad/420016.
It can probably modified to support other keypads, ZHA, Zwave, etc.
I think it's better to leave this outside of Alarmo, since the implementation is device-specific.


Can't connect from React Native

I'm using in React Native the same code that works perfectly fine from a web js client but get an error: Failed to start the transport 'WebSockets': null. So it seems like SignalR doesn't find any transports (I did not specify any transport explicitly). I've looked through other issues and I've got an impression SignalR is supposed to be working from React Native at this point. Is it the case?

"Failed to start the transport 'WebSocket': null" is unfortunately unhelpful (which is our fault). We'll take a look at getting the proper error message out of this.
SignalR does appear to be correctly falling back to Server-Sent Events. Is your app not working properly? The error message indicates we failed to start the WebSocket, but that's a recoverable error, and SignalR should continue to function properly.

Triage decision: Let's get the error message cleaned up at least.

Logging improved in #12026. Getting a network trace (described in our Diagnostics guide) would help us identify the specific issue here since browsers (and React Native) are notoriously bad at giving specific error messages for these issues.
If anyone is still hitting this issue, feel free to open a new issue with a network trace!

Have you tried another transport?
     const connection = new signalR.HubConnectionBuilder()
          .withUrl(url, {
            transport:
              signalR.HttpTransportType.WebSockets |
              signalR.HttpTransportType.LongPolling,
          })
          .configureLogging(signalR.LogLevel.Debug)
          .build()


Adds auxiliary function (useful for tests)

And maybe, eventually, useful to create multis that make easier to pack or unpack strings... Please see my last commit for more explanations.

Closing this as it's outside of the scope of a literal port of the Perl pack/unpack functionality


Implement error handling for bitcoind RPC calls

We need error handling for transient errors in calls to bitcoind, i.e. all calls to the bitcoin core RPC client, especially for the (potentially long running) index subcommand. Currently, it fails after it encounters any error. This is particularly bad on a Mac, given we have #309
Ideally, we implement a retry with exponential backoff and a limit for all RPC calls as some sort of wrapper to Client? We already have this on the background-block-fetch branch (but see #501, which is trival to fix fortunately)

Mostly addressed with #508 for the most annoying aspect of this (#309)
It would be nice to extend the error handling to all RPC calls but that's more of a nice to have.

I think this can be closed, but feel free to reopen if it's still an issue. It would be nice to handle transient errors in the client somehow, instead of in the indexing code.


background-size and background-position on IE9 with 'vw'

Hi
In order to get the same view in IE9, I have to device background-size and background-position differently.
Maybe something that you may want to consider for your behavior...
Test in IE9 and other browsers with the fiddle:
http://jsfiddle.net/fBhXf/10/
Basically this example is for a

and with CSS:
#example {
    background-image:url(http://www.ipreferjim.com/site/wp-content/uploads/2012/10/markers.png);
    background-size:100vw;
    background-position:-20vw -20vw;
    width:10vw;
    height:10vw;
    border:solid green 1em;
}
.lt-ie10 #example {
    background-size:1000vw;
    background-position:22vw 22vw;
    width:0.2vw;
    height:0.2vw;
}

Where '.lt-le10' identifies the browser as before IE 10.

Very old ticket - no longer expecting this to be implemented.


MSAL.js - Implicit Authentication - Issue with reply url parameters

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
I am using MSAL.js for a javascript based single page application. We have configure Azure Ad for implicit authentication. The redirection url also has been configured to a page.
However we have a requirement where we get a daily email report. This email has links to the application page but with query parameters that allows to filter the report for that day.
Now if we access the app via the landing page, we are able to login fine. But with the query params it gives the exception "The reply URL specified in the request does not match the reply URLs..".
I am using the endpoint V2 on Azure AD , hence not able to put * in the reply url. I guess this is an existing problem. But is there some way to overcome the issue of logging in & redirection with parameters?

Hi, @sid1260. Could you please provide your MSAL configuration object (the configuration for PublicClientApplication). Also, are you using loginPopup or loginRedirect?
In your scenario, when the current page changes dynamically, you should set a redirctURI in your configuration that matches the one in the Azure Portal (the one without query parameters). If you're using loginRedirect you can set navigateToLoginRequestUrl to true in order to have the user redirected back to the version of the page with query parameters.
Thanks!

Thanks @technical-boy
Code is below
`const msalConfig = {
auth: {
clientId: "bcb2a88a-9efb-414d-89cb-d194acb28a96",
authority: "https://login.microsoftonline.com/GUID",
redirectUri: "URL",
},
cache: {
cacheLocation: "sessionStorage",
storeAuthStateInCookie: false,
}
};
const myMSALObj = new Msal.UserAgentApplication(msalConfig);
myMSALObj.loginPopup(loginRequest)
.then(loginResponse => {
if (myMSALObj.getAccount()) {
serverLogin(myMSALObj.getAccount().userName);
window.location.reload()
}
}).catch(error => {
console.log(error);
});`
We are using loginPopup. My RedirectURI is the one matching the one on Azure. But with the popup option how does it redirect back to the original page with params? Can we set navigateToLoginRequestUrl  = true in this case , does the framework take care of the redirection?

@sid1260 if you're using loginPopup, your application will need to manually redirect the user once the loginPopup promise has resolved.


DOC: document utils

Document the utils.py file.

@callumrollo For discussion:  This PR makes clear a pretty big problem with having the example data separate from the repo.    In particular, I changed some of the metadata in the processing.  So in order to make the tests pass I'd have to make a new version of the example data.  However, that is problematic because the new version hasn't been merged yet, and so your tests would start to fail, at least until you merged the new changes.
I'm not sure what the fix is here.  We could make format changes have two accompanying PR requests.  The tests though would need some way of downloading the zip file for the correct branch of the example data.  That seems doable, but maybe fragile.
I'm of a mind to put the example data back into the repo.  People who do pip-install won't get the example data so it doesn't take up too much space.  Developers can probably survive whatever load we put on them.

Yes, I hadn't foreseen this. As the example datasets are small and don't get included in a pip install I don't see an issue with putting them back in the main repo

@callumrollo note the new less stringent test here.  I was locally getting failures without using all-close using the netcdf files you generated.  I think for our purposes allclose will be good enough, versus strict equality of the variables.
The test files had to be regenerated to allow for the attribute changes get_profiles->get_profiles_new.  note we had been using get_profiles_new for quite a while, but it was filling in the attribute incorrectly.

I wasn't aware of all-close before. Looks good, should prevent spurious test failures


Stop receiving values from LYWSD03MMC after ~6-8 hours

Hello,
on Home Assistant 2023.2.2 with v3.1.0 of the integration Home Assistant constantly loses contact to the LYWSD03MMC (Temp/Humidity) sensors after approx. 6 to 8 hours. Restarting Home Assistant solves the issue for another 6-8 hours.
Logs are empty.
Any solution is appreciated.
REgards
Florian

You need to collect component debug logs

Good evening. Here is everything linked to the xiaomi3 addon:
2023-02-06 15:17:18.793 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Loaded from cache 17 devices
2023-02-06 15:17:29.399 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] Timeout while requesting MIoT api /v2/home/device_list_page
2023-02-06 15:17:29.402 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Login to MiCloud for<EMAIL_ADDRESS>2023-02-06 15:17:29.627 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step1
2023-02-06 15:17:29.769 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step2
2023-02-06 15:17:30.057 DEBUG (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] MiCloud step3
2023-02-06 15:17:31.505 DEBUG (MainThread) [custom_components.xiaomi_gateway3] Loaded from MiCloud 17 devices
2023-02-06 19:27:36.647 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.gateway] <IP_ADDRESS> | Can't prepare gateway
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/init.py", line 177, in prepare_gateway
async with shell.Session(self.host) as sh:
File "/config/custom_components/xiaomi_gateway3/core/shell/init.py", line 29, in aenter
await self.connect()
File "/config/custom_components/xiaomi_gateway3/core/shell/init.py", line 36, in connect
self.reader, self.writer = await asyncio.wait_for(self.coro, 5)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 23)
The hub and all linked sensors are reachable from the Xiaomi Android-App
Regards
Florian

Looks like your hub not reachable from Home Assistant

Hi,
I have the same issue.
Regards,
Ákos

I've the same issue. I face the same connectivity issues with xiaomi LYWSD03MMC sensors as well as qingping sensors (door, motion & light sensors)

I have the same issue, rollback to 3.0.1 resolve problem.

Still nothing useful from you to solve the problem

What information can I provide to solve the problem?

I have the same issue, rollback to 3.0.1 resolve problem.

I also rolled back to 3.0.1, seems like it solved the issue.  It's only been 3 hours, so I'll keep monitoring.

I have the same problem for a few days...the data from the sensors do not go back to the home assistant "unavailable" when I reload or restart the integration it works again for a few hours then nothing.

Still nothing useful from you to solve the problem

I updated again to 3.1.0, trying to help you so that you can help us). This is what I got from the log file.
2023-02-08 15:43:08.148 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.kitchen_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:43:08.154 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.kitchen_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:43:08.157 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.582d34605599_idle_time has device class None, state class measurement and unit s thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:39.467 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.toilet_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:39.475 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.toilet_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.198 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_illuminance has device class illuminance, state class measurement and unit lx thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.202 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_motion_battery has device class battery, state class measurement and unit % thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
2023-02-08 15:44:51.206 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.bedroom_motion_idle_time has device class None, state class measurement and unit s thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

I enabled debug logs in the integration configuration. Where else I should look to provide you more useful inputs?

Well, I downgraded to 3.0.1 6 hours ago, and now it went offline again, so maybe it's not the integration, but something else....

I also update back to 3.1.0, enable debug for component and wait for problem. Now all my ble sensors became unvailable, but no any information at this time in log, only this part in 2 hours after update component
2023-02-08 14:26:34.920 WARNING (MainThread) [custom_components.xiaomi_gateway3.core.gateway] <IP_ADDRESS> | Can't update gateway stats
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/gate_mgw.py", line 111, in gw3_update_serial_stats
async with shell.Session(self.host) as sh:
File "/config/custom_components/xiaomi_gateway3/core/shell/init.py", line 30, in aenter
return await self.login()
File "/config/custom_components/xiaomi_gateway3/core/shell/init.py", line 44, in login
resp: bytes = await asyncio.wait_for(coro, 3)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 614, in readuntil
raise exceptions.IncompleteReadError(chunk, None)
asyncio.exceptions.IncompleteReadError: 12 bytes read on a total of undefined expected bytes

my log has similar error warning from other another open issue: https://github.com/AlexxIT/XiaomiGateway3/issues/971#issue-1571396490.

I rolled back to 3.0.0, stable for the last 12+ hours.

@vmannoor thanks for logs. All this BLE devices unavailable?

@vmannoor thanks for logs. All this BLE devices unavailable?
it has the non-numeric value: unavailable fixed in master version. You can check if it helps you.

Yes, all the sensors go unavailable. But now I'm on 3.0.0 for the last 2 days and everything works perfectly.

Hello,
i rolled back to 3.0.0 but the "error" remains.
No values from the sensors after a few hours. The hub is reachable in the Xiaomi app.
Here is my log:

2023-02-11 22:19:38.493 WARNING (MainThread) [custom_components.xiaomi_gateway3.core.mini_miio] <IP_ADDRESS> | Device offline
2023-02-11 22:20:08.932 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.gateway] <IP_ADDRESS> | Can't prepare gateway
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/__init__.py", line 177, in prepare_gateway
async with shell.Session(self.host) as sh:
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 29, in __aenter__
await self.connect()
File "/config/custom_components/xiaomi_gateway3/core/shell/__init__.py", line 36, in connect
self.reader, self.writer = await asyncio.wait_for(self.coro, 5)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 23)
2023-02-11 22:49:30.303 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 334, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"

Regards
Florian

Hello, still no solution found for this bug? I have all my sensors unavailable.

@monsterflo I hope problem will be resolved in next release

Same problem. Status is always Unknown (zigbee JTYJ-GD-01LM/BW (lumi.sensor_smoke)
Honeywell)


has the inference code released?

failed to find the inference code

The inference code is now available on SpQR-side.
Refer to https://github.com/huggingface/transformers/pull/34976 for huggingface integration.


Dockerize The App

Can't get it to run on EC2. Don't really want to debug distro-specific problems.

Done!


New Issue is not linked to Epic.

Describe the bug
Creating an issue of type "Story" and trying to link that to a parent Epic doesn't seem to work.

JiraCLI Version:

(Version="v0.3.0", GitCommit="", CommitDate="", GoVersion="go1.17.5", Compiler="gc", Platform="darwin/arm64")

Are you using Jira cloud or on-premise jira server? Also mention the version for on-premise installation.

Jira Cloud - Classic project

What operating system are you using? Also mention version.

macOS Big Sur 11.6.2

What terminal are you using? Also mention version.

iTerm 2 Build 3.4.14

To Reproduce

Ran the command with the -P flag to link to an epic, as specified here. In my case jira issue create -tStory -PMYEPIC-42<EMAIL_ADDRESS>Fill in the remaining fields (Summary & Description)
Story is created with the correct summary and description. It's also assigned to me, but not linked to the Epic as seen in the Story detail Epic link - It's set to None.

Expected behavior
Expected the task to be linked to MYEPIC-42.

As an aside, if I set the issue type to Sub-task, it seems to link it to the Epic properly, but the problem is that it doesn't show on the right pane on jira epic view. I tried some other types but none worked.
jira epic view seems to list all issue types linked to an epic but Sub-task.

Hi @hugoamvieira, to confirm you are using next-gen project and not classic right?

Hey @ankitpokhrel - Nope, it's a classic project.
As per the config:
project:
  key: <REDACTED>
  type: classic

Are you able to set epic using jira epic add? Attaching issue on creation seem to be working fine in my setup (cloud) so I might need some extra details to debug. Is this epic shown when you try to add it from the UI ?

Are you able to set epic using jira epic add?

Yep. Hadn't tried this but it works like a charm - I created a test Story and added it to an Epic and it worked great :)

Is this epic shown when you try to add it from the UI ?

Yep - I can set the epic in Jira's UI just fine.

@ankitpokhrel Yep - You're correct. epic.link is set to "".
I tried regenerating but it's still not setting anything in there - What should be in that value?

epic.link is a custom field and is populated using /rest/api/2/issue/createmeta endpoint. It would be helpful If you can execute following curl command and see if the API returns Epic Link custom field for your project.
curl --request GET \
  --url 'https://<HOST>.atlassian.net/rest/api/2/issue/createmeta?projectKeys=<KEY>&expand=projects.issuetypes.fields' \
  --user "<USER>:$JIRA_API_TOKEN" > createmeta.json

In the response:

we are first looking for projects.issuetypes with "name": "Epic" and,
in the fields section of that block there should be a custom field with name Epic Link

epic.link is value for that custom field eg customfield_10104

Hey @ankitpokhrel - So I found the projects.issuetypes with "name": "Epic", however there's no custom field within it that has name Epic Link.
This custom field is present in other issuetypes though - Here's how it looks like on other issue types:
                        "customfield_10008": {
                            "required": false,
                            "schema": {
                                "type": "any",
                                "custom": "com.pyxis.greenhopper.jira:gh-epic-link",
                                "customId": 10008
                            },
                            "name": "Epic Link",
                            "key": "customfield_10008",
                            "hasDefaultValue": false,
                            "operations": [
                                "set"
                            ]
                        }

I'm still a bit confused into what goes into epic.link VS epic.name as jira init set epic.name to one of those customfield_XXXXXX, and epic.link to nothing.
Thanks!

@hugoamvieira its strange that the response doesn't have "Epic Link" field for issue type "Epic". Does the issue link on create work if you manually add customfield_10008 to epic.link ?

@ankitpokhrel Actually, yep. I set it up like this:
epic:
  name: "customfield_10008"
  link: "customfield_10008"

And it ended up working!

Hopefull this helps someone. After running Jira Init, this is how my config looked (after changing project type to classic).
board:
    id: 1619
    name: <project_name>
    type: kanban
epic:
    name: customfield_12271
    link: ""
installation: Local
issue:
    fields:
        custom:
            ...
            - name: Epic Link
              key: customfield_12270
              schema:
                datatype: any
            ...
project:
    key: <project_key>
    type: classic
...

The epic > name field had a value of customfield_12271 so I tried setting the epic > link to the same customfield_12271. This didnt work and I got the following error:
- customfield_12271: Field 'customfield_12271' cannot be set. It is not on the appropriate screen, or unknown.

I noticed that the fields > custom > Epic Link had a value of customfield_12270. So I updated my config to following and it worked!
epic:
    name: customfield_12270
    link: customfield_12270

All in all, in order to get my config to work with an on-prem Jira instance, I did the following:

Changed project type to classic
Updated Epic link to the value of the custom field Epic Link
(optional; personal preference) Updated custom fields names to not have spaces: Epic Link --> epic_link

Hope this helps.

Thank you - this fixed it for me.

I'm still having issues linking parents/epics. My epic section looks like this:
epic:
    name: customfield_10011
    link: customfield_10014

but when I set a -P FOO-1111 I get, `Error:

customfield_10014: Field 'customfield_10014' cannot be set. It is not on the appropriate screen, or unknown.`

customfield_10014: Field 'customfield_10014' cannot be set. It is not on the appropriate screen, or unknown.

@SleepyBrett the err is returned by Jira and is typically due to configuration issues. Some details to debug this can be found here.


Contrast border is not visible for active activity bar item when activeBackground is set

Set both colors:

"contrastActiveBorder": "#ff0000",
"activityBar.activeBackground": "#e4dbd6",

Activity bar contrast border is not visible.

Themes seems to be using translucent colors to workaround it. Is that as-designed?

Looks like a z-index issue here:
https://github.com/microsoft/vscode/blob/325cb4a67d5f3ef38123d7e5e9e4a3e8a2d5f000/src/vs/workbench/browser/parts/activitybar/activitybarActions.ts#L494-L501
Will fix in the next milestone since we are now in endgame for October.

You should be able to set both contrast border and active bg:


docs: fix broken link

broken link... any other docs links need a check?

Thank you for catching this! & no, not for now.


Mark unhydrated replies as orphaned

Noticed this during appview/relay syncing issues.
(This logic existed in the old code but I dropped but because I didn't know why. Now I know.)
If we have post.record.reply but we didn't receive a reply, something went wrong (i.e. we don't know its parent or root). Let's mark it as orphaned in this case.
This will make it filtered out of Following. On other feeds, it will display as "reply to a post" (so it won't seem top-level).
Test Plan
Don't know how to force it to happen, but I hardcoded the condition as true and verified the above.

Verified this works with a real post too after the relay restarted again


extra vl argument causing problems, is it required?

Hi,
I am new to this forum, likely the question has been discussed before, plus point to the relevant thread if it is the case.
I am not clear why many intrinsic functions accept extra vl argument and internally containing extra call to vsetvl leading to inferior generated code. Assembly instructions do not have vl argument and not clear why intrinsics deviate from this approach.
Main problem with extra third argument is not only inferior performance, but also impossibility to write generic code using operator overloading. Can't write a + b anymore with operator overloading, you now need to pass third argument somehow. So it either have to be plus(a, b, vl) which is very poor, or you have to pack vl into every number. Hence a becomes a struct with vl and b also contains copy of vl in its own struct and data structures become bloated.

closed as duplicate


npm install fails to install posix

I am trying to set up a server in a Windows environment (though I've tried on Ubuntu 14.04, similarly fails on posix install). Here is the error:
posix.cc
..\src\posix.cc(2): fatal error C1083: Cannot open include file: 'unistd.h': No
such file or directory [\instant.io\node_modul
es\posix\build\posix.vcxproj]
...
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the posix package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls posix
npm ERR! There is likely additional logging output above.
Any idea what's going on here? I'm fairly new to node and npm and not sure where to go from here.
Is it in fact a problem with posix? The only somewhat useful looking thing I've found on StackOverflow is http://stackoverflow.com/a/27709968/1388195, but not sure where I'd find the io.h replacement for unistd.h mentioned.
Really looking forward to playing around with this and WebTorrent, and appreciate any help :)
Cheers,
Simon

I've managed to get things up and running on Ubuntu, so I guess I'll just stick with that. Turned out the Ubuntu posix install error was due to the node binary being used actually being the "Amateur Packet Radio Node Program". See this StackOverflow answer.

Oh, yes. On ubuntu, you can solve this by running: sudo apt-get install nodejs-legacy which gives you a node symlink.
I think we should still fix the issue on Windows.

The issue with the posix package should be fixed on Windows now. Let me know if you have further issues.
I published downgrade and unlimited that work on windows and made instant.io use those packages.

unlimited appears to have the same error, failing on posix.
Running `node server/index.js gives the following:
E:\Devel\Torrents\instant.io\node_modules\downgrade\index.js:17
process.getuid(), uid, process.getgid(), gid
^
TypeError: undefined is not a function
at downgrade (E:\Devel\Torrents\instant.io\node_modules\downg
rade\index.js:17:15)
at E:\Devel\Torrents\instant.io\server\index.js:168:3
at zalgoSafe (E:\Devel\Torrents\instant.io\node_modules\run-p
arallel\node_modules\dezalgo\dezalgo.js:20:10)
at done (E:\Devel\Torrents\instant.io\node_modules\run-parall
el\index.js:18:15)
at Server.g (events.js:199:16)
at Server.emit (events.js:104:17)
at net.js:1171:12
at process._tickCallback (node.js:355:11)
at Function.Module.runMain (module.js:503:11)
at startup (node.js:129:16)

@zyzof Sorry about that. Can you delete your node_modules folder, re-install, and try again? I didn't know that node.js's process.getuid is undefined on windows. This is fixed now.


packaging other resources

how do you package other files like support files, e.g. images for docs?

Resources/ -- any sort of files you want to include
Samples/ -- demo stack(s)
Support/ -- PNG icons and '_defaultscript' files
docs/guide/guide.md -- guide markdown file for 'guide' tab of dictionary


Refactor tests for slm collector

Remove up, totalScrapes, and jsonParseFailures metrics. They are not useful.
Move fixtures to individual files
Base tests on the metric output for better testing the expected output instead of the internals.

I think the reason we have the up metric is that the Collect() doesn't have any error return. So we can't pass back a failed scrape signal to the output. Without this, the exporter will silently fail, which is not good for the end user.
I think we need a bit more refactor here, so that error is returned and we fail the scrape with a 5xx error instead of returning partial data.

I agree that knowing the collector as a whole or an individual collector was successful is useful. This is provided by the collector/Collector going forward: https://github.com/prometheus-community/elasticsearch_exporter/blob/master/collector/collector.go#L57
This particular change is just to update the testing before refactoring the slm collector to work with the Collector interface which will reintroduce the ability to determine if the collector scrape was successful. There have been a handful of similar PRs in this light. See https://github.com/prometheus-community/elasticsearch_exporter/pull/813
The follow up PR will will refactor the code to use the Collector interface. i.e. https://github.com/prometheus-community/elasticsearch_exporter/pull/789
I have been breaking up the refactor from the testing changes to make PRs easier to review and to make sure the refactors don't meaningfully change the metrics. If you would prefer a different strategy that is easier to review or more to your preference, let me know.


Release Service Bus Track 2 Library Preview 4 for .NET

This is a parent issue tracking the work planned for Service Bus to release the fourth preview in July following the C# .Net Azure SDK guidelines
Code complete date: July 3rd, 2020

[ ] Design for supporting various AMQP data types for message body
[ ] Add batch scheduling
[ ] Implement plugin support
[ ] Finalize API changes
[ ] Stress tests

Implement plugins

@JoshLove-msft, it probably should de "Implement support for plugins" or "Implement incoming and outgoing plugins pipeline". That comes before plugins are created, right? 🙂

Implement plugins

@JoshLove-msft, it probably should de "Implement support for plugins" or "Implement incoming and outgoing plugins pipeline". That comes before plugins are created, right? 🙂

Updated!


upgrade ember to 2.9 beta 2

Upgrades ember-cli to 2.9 beta 2

@billybonks I would prefer to wait until Ember versions are out of beta to upgrade them.

NP :)
On Fri, 30 Sep 2016, 04:01 John Kleinschmidt<EMAIL_ADDRESS>wrote:

@billybonks https://github.com/billybonks I would prefer to wait until
Ember versions are out of beta to upgrade them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HospitalRun/hospitalrun-frontend/pull/672#issuecomment-250574970,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkGyBy5ECDm1Y_8L5bGKi0MrTIGWMNHks5qvBkYgaJpZM4KF03S
.


[FEATURE]

Is there any support for the subscript and superscript feature in the editor.
Let me know, if possible to integrate in toolbar.dart!

Hi @Chandu-bs ,
Yes, it is possible to add Superscript/Subscript formats to the editor. Will add them in the next release. :)
Thanks

Hi, @the-airbender when can we expect the next release with subscript and superscript?
Is there any support for formulas in the editor?

@Saikumar-bs @Chandu-bs , I will plan to deploy a new release with these format buttons in this month, as I am little busy with other items.
However, as a workaround, you can leverage the setFormat controller method.
For Superscript:
 controller.setFormat(format: 'script', value: 'super');
For Subscript:
 controller.setFormat(format: 'script', value: 'sub');
To Clear Subscript/Superscript:
 controller.setFormat(format: 'script', value: '');
Hope this helps :)
Thanks!

Thanks for the inputs @the-airbender!

Thanks @the-airbender , This could help!

One more thing @the-airbender, can we change the cursor position dynamically, like positioning the cursor, where we want in the editor after some on-tap function in the custom button?
Thanks in advance?


Tensor-parallelism for multi-gpu support

Feature request
Being able to split models into multiple GPUs, as with vllm/aphrodite engine for LLMs.
Motivation
It would be extremely helpful to be able to split larger models into multiple GPUs.
Also, without TP, one GPU loses lots of vram and the other does not, making it impossible to use tensor parallelism on another program at the same time.  TP is used when one GPU can't handle the desired batch size or the model at all. Unless there are some compelling benchmarks for bert-base, there is no need for tensor parallelism.


outputs should include the ARN of the RDS cluster

Currently, the project is returning the resource id, wouldn't it make more sense if it returned the ARN directly? The use case is the same for creating policies but look like returning the ARN is more straight forward.

@antonbabenko It looks like this was only applied to the 2.x versions for TF 0.12.   Any chance we could get the similar change applied in a 1.x version for those of us still stuck on Terraform 0.11.x for reasons?


Add the byebug line # to make the output clickable

Adding the exact line number of the byebug statement to the end of the filename on the output makes the statement clickable in IDE's and editors supporting this functionality. Currently clicking the path goes to the top of the file. With the modification, clicking takes the user to the exact byebug line in the document.
For example in vscode it looks like follows:

I realised fixing the tests is not as straight forward as I thought at the beginning.
The complication comes from the fact that one can use list as many times as they want without modifying the frame.line.
Then the output becomes as follows:
 "[7, 16] in /tmp/byebug_example.rb:13",
 "7:       \"%1\"",
 "8:     end",
 "9:   end",
 "10:",
 "11:   byebug",
 "12:",
 "=> 13:   str = ByebugExampleClass.new.build_percentage_string",
 "14:",
 "15:   str",
 "16: end",
 "(byebug)",
 "",
 "[6, 8] in /tmp/byebug_example.rb:13",  <--------- THIS LINE
 "6:     def build_percentage_string",
 "7:       \"%1\"",
 "8:     end",
 "(byebug)"

13 is still useful for terminal debug sessions since it tells the next line to be executed; however, then the tests needs to be modified as such:
check_output_includes "[6, 8] in #{example_path}:13"

I don't know if you are okay with this modification.
To be honest, if someone is using list this means they are probably on terminal which means they don't need the "hyperlink' support; but I think giving the frame.line info still useful. What do you think?

Hi @senhalil! So... It sounds that just recalculating the middle line every time like you did in the beginning is a better option after all?

Hi @senhalil! So... It sounds that just recalculating the middle line every time like you did in the beginning is a better option after all?

Hi @deivid-rodriguez In my opinion, your suggestion is still the superior option, because it gives a useful info -- i.e., next instruction to be executed --, my original way didn't give any info (except average of two numbers :) ).
If someone is using list methods, the location of the instruction arrow might be useful to them.
So I suggest keeping the current version if you are not oppose to it.
PS: Is it me who needs to mark "Changes requested" as resolved or you?

Yeah, right.
I'm still worried that this might confuse some users into thinking this is a bug and we might get reports about it. Is there any way we can clarify the status line in this regard? Maybe something like:

Stopped at /path/to/file:<line>. Showing lines [min, max]

Or something like that?

PS: Is it me who needs to mark "Changes requested" as resolved or you?

I think it's me :+1:.

I'm still worried that this might confuse some users into thinking this is a bug and we might get reports about it. Is there any way we can clarify the status line in this regard? Maybe something like:

I understand.

Stopped at /path/to/file:. Showing lines [min, max]

Or something like that?

I am happy with that wording, if you are. It is clean and clear.


Adds multiple file upload feature to file fields.

Sorry, launder.ids (plural) is necessary, but it combines the "hey is
this even an array" step with the "does this contain strings" step, and so
is very handy if you give it an actual array - which you can do on the
client side by splitting before you send.
On Thu, Jun 20, 2019 at 12:59 PM Alex Bea<EMAIL_ADDRESS>wrote:

@abea commented on this pull request.
In lib/modules/apostrophe-forms-file-field-widgets/public/js/lean.js
https://github.com/apostrophecms/apostrophe-forms/pull/65#discussion_r295903061
:

 el.removeAttribute('data-apos-forms-busy');

 spinner.hidden = true;

function sendFiles (files) {

What's "fields too" referring to?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/apostrophe-forms/pull/65?email_source=notifications&email_token=AAAH27KL4NBFEDJDFI6PPHDP3OZOBA5CNFSM4HZTAOQKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB4FYXXI#discussion_r295903061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAH27NQYPWYDPX5TZCC4L3P3OZOBANCNFSM4HZTAOQA
.

--
Thomas Boutell, Chief Software Architect
P'unk Avenue |<PHONE_NUMBER>  |  punkave.com

Should be all set. I wasn't sure what this comment was referring to, though.

Good call.


Add any of your project you want to share.

Make sure the folder's name is the same as the project's name & include a readme file with a brief about the project and its uses.

Hey @ron2111 👋
I would like to work on this issue and want to add a project of frontend-mentor-challenges by frontmentor.io
Could you please assign me this issue under Hacktoberfest 2021
Thanks✨

Hey @ron2111
I would like to add a C++ Project into this.
Its CLI Based Tic Tac Toe Game written by me from scratch.

bro i am adding tic tac toe project i wrote from scratch in kotlin language . please assign me

You can add anything without asking for assign make sure to check the accouchement before making Pull Requests

hey do i need to create a new branch for every project ? or can i push in the main branch itself ?

it's better to make new branch

I would like to add sudoku solver in c++. Solved using backtracking. Please assign that to me

you can send PR regarding that directly, check the announcements before making any PR

Simple personal portfolio website added. Please check the PR #206

Hey @ron2111 I have added a certificate generator in the Javascript folder can you give #281 a Hacktoberfest label.

Hi @ron2111 I've created a PR for a project I made in HTML Projects folder. Please check the PR #356

Hello @ron2111 , I've created a PR for a web crawler in python ( PR #370 ). Kindly go through that.

Hey @ron2111 I've created a PR for a Relaxer app in HTML projects folder( PR #371  ).


Failed to load in Anki 2.1.66, MacOS sonoma, MacBook Air 2019, Apple silicon M1

Error message below
An add-on you installed failed to load. If problems persist, please go to the Tools>Add-ons menu, and disable or delete the add-on.
When loading 'yomichan-forvo-server':
Traceback (most recent call last):|
File "aqtaddons", line 246, in loadAddons
File "/Users/pkmean/Library/Application Support/Anki2/addons21/ yomichan-forvo-server/_init_py", line 138, in  class ForvoHandler (http.server.SimpleHTTPRequestHandler):
File "/Users/pkmean/Library/Application Support/Anki2/addons21/ yomichan-forvo-server/_init_py", line 139, in ForvoHandler
forvo = Forvo('zh')
File "/Users/pkmean/Library/Application Support/Anki2/addons21/ yomichan-forvo-server/_init_py", line 26, in init
self._set_session ()
File "/Users/pkmean/Library|Application Support/Anki2/addons21/ yomichan-forvo-server/_init_py", line 33, in _set_session
retry_strategy = Retry
TypeError: init() got an unexpected keyword argument
'method_whitelist'

@foxmean Do you have the latest version? I don't use method_whitelist anymore.

Oh, so sorry I maybe use the version older than [2023-07-28] because the date added file on my system is 2023-01-09. BTW, I cannot update yomichan-forvo-server from 'Check for Update' in Anki Add-on itself. I need to delete it and reinstall (by normal way of install it from code). After that it's work just fine. It is maybe the 'Check for Update' problem of Anki, not your add-on. Thanks for you so much for your contribution to the language learning community.


doh-proxy: init at 0.0.8

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/lib  /nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8
checking for references to /build in /nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8...
wrapping `/nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/8x2wsnd9d24nxrq57jxlzv5mjk7qdchw-python3.6-doh-proxy-0.0.8

Failure on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)

----------------------------------------------------------------------
Ran 20 tests in 7.009s

FAILED (failures=1)
Test failed: <unittest.runner.TextTestResult run=20 errors=0 failures=1>
error: Test failed: <unittest.runner.TextTestResult run=20 errors=0 failures=1>
builder for '/nix/store/26aibaqv40sy7y79c9pi2f9861fdkgnl-python3.6-aioh2-0.2.2.drv' failed with exit code 1
cannot build derivation '/nix/store/wwyzlcyvlaif7smfm7hdj4cyscjp1vg7-python3.6-doh-proxy-0.0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/wwyzlcyvlaif7smfm7hdj4cyscjp1vg7-python3.6-doh-proxy-0.0.8.drv' failed

AssertionError: 1.547662527392257 != 1.6 within 1 places

👀
Are those tests… nondeterministic??

Are those tests… nondeterministic??

Maybe ask upstream about that

Ran 0 tests in 0.000s

Please provide appropriate checkPhases or set doCheck = false and add a comment with the reason.

All addressed, I think. Opened https://github.com/decentfox/aioh2/pull/18 to fix the non-deterministic test issue upstream, but I think for now we should just skip checkPhase for that package.

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/lib  /nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8
checking for references to /build in /nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8...
wrapping `/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/lib  /nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8
checking for references to /build in /nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8

@GrahamcOfBorg build python2.pkgs.aioh2 python3.pkgs.aioh2 python2.pkgs.aiohttp-remotes python3.pkgs.aiohttp-remotes python2.pkgs.priority python3.pkgs.priority doh-proxy

Success on x86_64-darwin (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
The following builds were skipped because they don't evaluate on x86_64-darwin: python2.pkgs.aiohttp-remotes
Partial log (click to expand)
wrapping `/nix/store/bf0p3shj5vqa7jf182wnsyhg0g5apsn7-python3.6-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/bf0p3shj5vqa7jf182wnsyhg0g5apsn7-python3.6-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/bf0p3shj5vqa7jf182wnsyhg0g5apsn7-python3.6-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/bf0p3shj5vqa7jf182wnsyhg0g5apsn7-python3.6-doh-proxy-0.0.8/bin/doh-stub'...
/nix/store/z2dm1zyd9a9djxbqzif7qbd20k1qir4k-python2.7-aioh2-0.2.2
/nix/store/k24ay9yqpkk3k9cdang1idpy2ly03ivk-python3.6-aioh2-0.2.2
/nix/store/g6ydw8rbjrnjpb077mslyhw2wazbalz6-python3.6-aiohttp_remotes-0.1.2
/nix/store/1kvymgbgxvysyf42gqrq2qymfcasczsl-python2.7-priority-1.3.0
/nix/store/d19pl7k6x9sggvi43i49i7qqi4rhkz7h-python3.6-priority-1.3.0
/nix/store/bf0p3shj5vqa7jf182wnsyhg0g5apsn7-python3.6-doh-proxy-0.0.8

Success on aarch64-linux (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
The following builds were skipped because they don't evaluate on aarch64-linux: python2.pkgs.aiohttp-remotes
Partial log (click to expand)
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2/lib
patching script interpreter paths in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2
checking for references to /build in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2...
/nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2
/nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2
/nix/store/bniaz7p5hpkpg0v3fijsrfjnca6ayrqb-python3.6-aiohttp_remotes-0.1.2
/nix/store/gwxjm3nkhkz8wl8ayrcz2m7fpsq4y2vi-python2.7-priority-1.3.0
/nix/store/cn61zrym36jdxnwy03mmiq1lr9psyqjj-python3.6-priority-1.3.0
/nix/store/2rvw8kr92s4175rarbrqxmc904p799m4-python3.6-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
The following builds were skipped because they don't evaluate on x86_64-linux: python2.pkgs.aiohttp-remotes
Partial log (click to expand)
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8/bin/doh-proxy'...
/nix/store/a9waqkbgppv00riz2jwb40njmrmhw5vm-python2.7-aioh2-0.2.2
/nix/store/05nj60mv1qkpbhpf9xs3iaz8dpky1dwj-python3.6-aioh2-0.2.2
/nix/store/qls43k40mib56rbxlmhyp95m0l7naa0i-python3.6-aiohttp_remotes-0.1.2
/nix/store/31b3rdh9rzzp1kqxkbh0a882wr9p1d7q-python2.7-priority-1.3.0
/nix/store/9lzfbxbzm74w5axxchpl8yk9skg40lf3-python3.6-priority-1.3.0
/nix/store/a50p07fgx3xs5705r3sz0r0f7pj69vz8-python3.6-doh-proxy-0.0.8

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/lib  /nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8
checking for references to /build in /nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8...
wrapping `/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/lib  /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8
checking for references to /build in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8

Okay, hopefully that should be it :P

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
/nix/store/iw4205gxsqwk984ahhjg7l1c6c02v6g9-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/lib  /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8
checking for references to /build in /nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8/bin/doh-proxy'...
/nix/store/acgl7f5jjxkhjs5pzk7mw8rd413h3dgy-doh-proxy-0.0.8

@GrahamcOfBorg build python2.pkgs.aioh2 python3.pkgs.aioh2 python3.pkgs.aiohttp-remotes python2.pkgs.priority python3.pkgs.priority doh-proxy

Success on x86_64-darwin (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
Partial log (click to expand)
wrapping `/nix/store/k9d09bcfa9g8f70a3ar44naiy9sdb4ac-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/k9d09bcfa9g8f70a3ar44naiy9sdb4ac-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/k9d09bcfa9g8f70a3ar44naiy9sdb4ac-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/k9d09bcfa9g8f70a3ar44naiy9sdb4ac-doh-proxy-0.0.8/bin/doh-stub'...
/nix/store/z2dm1zyd9a9djxbqzif7qbd20k1qir4k-python2.7-aioh2-0.2.2
/nix/store/k24ay9yqpkk3k9cdang1idpy2ly03ivk-python3.6-aioh2-0.2.2
/nix/store/g6ydw8rbjrnjpb077mslyhw2wazbalz6-python3.6-aiohttp_remotes-0.1.2
/nix/store/1kvymgbgxvysyf42gqrq2qymfcasczsl-python2.7-priority-1.3.0
/nix/store/d19pl7k6x9sggvi43i49i7qqi4rhkz7h-python3.6-priority-1.3.0
/nix/store/k9d09bcfa9g8f70a3ar44naiy9sdb4ac-doh-proxy-0.0.8

Ran 0 tests in 0.000s

I've opened https://github.com/aio-libs/aiohttp-remotes/pull/57. You should set doCheck = false and remember to add an appropriate checkPhase once a new version with the PR merged is released.

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/lib  /nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8
checking for references to /build in /nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8...
wrapping `/nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/9m8jap0cbck9j7838i95cnr7vfk02dn9-doh-proxy-0.0.8

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
building '/nix/store/ij8538k4n3frfa0673m09gv3hipkj9wd-188772abcea038c31dae7d607e487eeed44391bc.patch.drv'...

trying https://github.com/aio-libs/aiohttp-remotes/commit/188772abcea038c31dae7d607e487eeed44391bc.patch
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1879    0  1879    0     0   4944      0 --:--:-- --:--:-- --:--:--  4931
fixed-output derivation produced path '/nix/store/s1cifhjg71p7w7mzwdag34mcaggdbpn9-188772abcea038c31dae7d607e487eeed44391bc.patch' with sha256 hash '0pb1y4jb8ar1szhnjiyj2sdmdk6z9h6c3wrxw59nv9kr3if5igvs' instead of the expected hash '12g6nyjl4nm1x80fv3mg8b0c9lg4rb1fw53yabc2rvz9m621hckn'
cannot build derivation '/nix/store/l1mzhar82zqqkl27jw3y0bhvxqg8qsd6-python3.6-aiohttp_remotes-0.1.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/ply9q38rp2sm69hmzly7xjlikbw8vyh3-doh-proxy-0.0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/ply9q38rp2sm69hmzly7xjlikbw8vyh3-doh-proxy-0.0.8.drv' failed

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/sddrdknjc7hgzxj4fz5sl45lng7dhs7j-python3.6-pytest-aiohttp-0.3.0
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sddrdknjc7hgzxj4fz5sl45lng7dhs7j-python3.6-pytest-aiohttp-0.3.0/lib
patching script interpreter paths in /nix/store/sddrdknjc7hgzxj4fz5sl45lng7dhs7j-python3.6-pytest-aiohttp-0.3.0
checking for references to /build in /nix/store/sddrdknjc7hgzxj4fz5sl45lng7dhs7j-python3.6-pytest-aiohttp-0.3.0...
pytestcachePhase
cannot build derivation '/nix/store/6rlva1b7wr66f3k0yj19g48lb3458pfz-python3.6-aiohttp_remotes-0.1.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/rdg9ablk6w5xmd31b564v5rg3f14s27n-doh-proxy-0.0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/rdg9ablk6w5xmd31b564v5rg3f14s27n-doh-proxy-0.0.8.drv' failed

That hash is working for me…
@GrahamcOfBorg build doh-proxy

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
building '/nix/store/ij8538k4n3frfa0673m09gv3hipkj9wd-188772abcea038c31dae7d607e487eeed44391bc.patch.drv'...

trying https://github.com/aio-libs/aiohttp-remotes/commit/188772abcea038c31dae7d607e487eeed44391bc.patch
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1879    0  1879    0     0   4639      0 --:--:-- --:--:-- --:--:--  4628
fixed-output derivation produced path '/nix/store/s1cifhjg71p7w7mzwdag34mcaggdbpn9-188772abcea038c31dae7d607e487eeed44391bc.patch' with sha256 hash '0pb1y4jb8ar1szhnjiyj2sdmdk6z9h6c3wrxw59nv9kr3if5igvs' instead of the expected hash '12g6nyjl4nm1x80fv3mg8b0c9lg4rb1fw53yabc2rvz9m621hckn'
cannot build derivation '/nix/store/l1mzhar82zqqkl27jw3y0bhvxqg8qsd6-python3.6-aiohttp_remotes-0.1.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/ply9q38rp2sm69hmzly7xjlikbw8vyh3-doh-proxy-0.0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/ply9q38rp2sm69hmzly7xjlikbw8vyh3-doh-proxy-0.0.8.drv' failed

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
Successfully installed aioh2-0.2.2
/build/aioh2-0.2.2
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2/lib
patching script interpreter paths in /nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2
checking for references to /build in /nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2...
cannot build derivation '/nix/store/rdg9ablk6w5xmd31b564v5rg3f14s27n-doh-proxy-0.0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/rdg9ablk6w5xmd31b564v5rg3f14s27n-doh-proxy-0.0.8.drv' failed

Hash fixed, I think. Thanks @cleverca22 for the advice in IRC.

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/lib  /nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8
checking for references to /build in /nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8...
wrapping `/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/lib  /nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin
patching script interpreter paths in /nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8
checking for references to /build in /nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-client'...
/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8

@GrahamcOfBorg build python2.pkgs.aioh2 python3.pkgs.aioh2 python3.pkgs.aiohttp-remotes python2.pkgs.priority python3.pkgs.priority doh-proxy

Success on x86_64-darwin (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
Partial log (click to expand)
wrapping `/nix/store/83fysvdlkf02yv1n01g0y2w88p7vy09l-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/83fysvdlkf02yv1n01g0y2w88p7vy09l-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/83fysvdlkf02yv1n01g0y2w88p7vy09l-doh-proxy-0.0.8/bin/doh-proxy'...
wrapping `/nix/store/83fysvdlkf02yv1n01g0y2w88p7vy09l-doh-proxy-0.0.8/bin/doh-stub'...
/nix/store/z2dm1zyd9a9djxbqzif7qbd20k1qir4k-python2.7-aioh2-0.2.2
/nix/store/k24ay9yqpkk3k9cdang1idpy2ly03ivk-python3.6-aioh2-0.2.2
/nix/store/bq3c28i6kil2jm6agffhy8m15hgam8b0-python3.6-aiohttp_remotes-0.1.2
/nix/store/1kvymgbgxvysyf42gqrq2qymfcasczsl-python2.7-priority-1.3.0
/nix/store/d19pl7k6x9sggvi43i49i7qqi4rhkz7h-python3.6-priority-1.3.0
/nix/store/83fysvdlkf02yv1n01g0y2w88p7vy09l-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
Partial log (click to expand)
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-httpproxy'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-client'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-stub'...
wrapping `/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8/bin/doh-proxy'...
/nix/store/a9waqkbgppv00riz2jwb40njmrmhw5vm-python2.7-aioh2-0.2.2
/nix/store/05nj60mv1qkpbhpf9xs3iaz8dpky1dwj-python3.6-aioh2-0.2.2
/nix/store/xbz7l7zbgzabqr5nzgc6xfxadv2371wy-python3.6-aiohttp_remotes-0.1.2
/nix/store/31b3rdh9rzzp1kqxkbh0a882wr9p1d7q-python2.7-priority-1.3.0
/nix/store/9lzfbxbzm74w5axxchpl8yk9skg40lf3-python3.6-priority-1.3.0
/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8

Success on aarch64-linux (full log)
Attempted: python2.pkgs.aioh2, python3.pkgs.aioh2, python3.pkgs.aiohttp-remotes, python2.pkgs.priority, python3.pkgs.priority, doh-proxy
Partial log (click to expand)
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2/lib
patching script interpreter paths in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2
checking for references to /build in /nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2...
/nix/store/pzhkanwyay242pq2ka1rsi95qlz255z7-python2.7-aioh2-0.2.2
/nix/store/1ij5shfiz6zcss3hqg7fb8ik84hx6gb1-python3.6-aioh2-0.2.2
/nix/store/isvk89br07a29qd3jz7srid4jzqiwnx3-python3.6-aiohttp_remotes-0.1.2
/nix/store/gwxjm3nkhkz8wl8ayrcz2m7fpsq4y2vi-python2.7-priority-1.3.0
/nix/store/cn61zrym36jdxnwy03mmiq1lr9psyqjj-python3.6-priority-1.3.0
/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8

aioh2 is missing a disabled = !isPy3k.

Success on aarch64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
/nix/store/zk8kkizi9pjk9s7ws06ll68xik692vzq-doh-proxy-0.0.8

Success on x86_64-linux (full log)
Attempted: doh-proxy
Partial log (click to expand)
/nix/store/yh4p1m0z3z1m4d5b3wv8npvf3hr8gw4v-doh-proxy-0.0.8


[Folder Search] ... No folders are displayed

Extension
https://www.raycast.com/GastroGeek/folder-search
Description
Whenever I enter more than one character in the search, “No results” is displayed, and if I enter only one character, no matter which one, I always get the same list of files deep from the system. Permissions for Raycast have been granted, “Search Files” works normally, also finds Folder, but I would like to use the extended capabilities (Copy, Move of files selected in Finder) of Folder Search.

Steps To Reproduce
MacBook Pro M1 Pro, Venture 13.31.1 (a), Raycast 1.51.1
Start folder-search in raycast and type one or two character.
Current Behaviour
No response
Expected Behaviour
No response

There is another topic with this issue, maybe this entry should be deleted?

Merged and closed, please give it a shot @MichaelHHeng  - you can run Check for extension Updates to ensure you have the newest update

Tested and working! Thank you very much!

@MichaelHHeng Wohoo! So happy to hear!


Cookie Consent Customization

Description of problem
Cookie Consent customization is stored in GlobalResources.resx.  This has several problems.

There is only one customization per installation, not per site.
If a DNN upgrade replaces GlobalResources.resx, customisation is lost.

Description of solution
Cookie Consent needs to have site specific settings, like some of the language resx files.  It should also handle localization.
Description of alternatives considered
Provide a clear and concise description of any alternative solutions considered.
Screenshots
If applicable, provide screenshots to help explain the problem and/or enhancement.
Additional context
Add any other context about the enhancement that may be helpful with implementation.
Affected browser

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer
[ ] Edge

The localization system always supports overriding per portal. When in the language editor, at the top there's a Mode set of radio buttons to select whether to edit at the Global level (which, as you note, will be overridden by upgrades and shouldn't really be supported at all), at the Host level, or at the site level. Does switching to the site mode resolve your issue, or is there something that makes that not work as expected?

Thank you, Brian!
I guess I should have actually dug into this a bit before creating this issue.  It was a "friend of a friend" report, and I really didn't dig into it.  I glad to have folks like you around to protect me from myself.


Minor Reporting for Schema Changes

Hi,
Here is proposed improvement for error reporting for schema changes when working with hash joins.
This is my first PR so please advise if this is not fulfill Drill requirements for this kid of work or if anything here is sub-par. ( Know the reporting logic could be moved to the exception but I did not want to touch more classes)
Regards,
-Stefan

@acmeguy This would be a nice enhancement. Could you file a DRILL jira and include the jira number in the title of your PR "DRILL-xxxx: Minor Reporting for Schema Changes". Also could you rebase onto the latest master and resolve the conflicts?


Event after npm run build page look for the resource/css/app.css but not to the public/build/assets

Laravel Vite Plugin Version: 0.5.0
Laravel Version: 9.23
Node Version: 16.15.1
NPM Version: 8.11
Host operating system:  Linux 21.10
Web Browser : Chrome 102.0.5005.115 (Official Build) (64-bit) || Firefox 103.0.1 (64-bit)

Description:
Event after npm run build page look for the resource/css/app.css but not to the public/build/assets
Steps To Reproduce:
The project repository https://github.com/GrytsenkoAndrey/mytest-vite.local
Fresh Laravel project with installed Laravel UI Vue, Tailwind Css and Vue
package.json
{
    "private": true,
    "scripts": {
        "dev": "vite",
        "build": "vite build"
    },
    "devDependencies": {
        "@popperjs/core": "^2.10.2",
        "@vitejs/plugin-vue": "^3.0.1",
        "autoprefixer": "^10.4.8",
        "axios": "^0.27",
        "bootstrap": "^5.1.3",
        "laravel-vite-plugin": "^0.5.0",
        "lodash": "^4.17.19",
        "postcss": "^8.4.16",
        "sass": "^1.32.11",
        "tailwindcss": "^3.1.8",
        "vite": "^3.0.0",
        "vue": "^3.2.37"
    }
}

vite.config.js
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';
import vue from '@vitejs/plugin-vue';

export default defineConfig({
    plugins: [
        laravel({
            input: [
                'resources/css/app.css',
                'resources/js/app.js',
            ],
            refresh: true,
        }),
        vue({
            template: {
                transformAssetUrls: {
                    base: null,
                    includeAbsolute: false,
                },
            },
        }),
    ],
    resolve: {
        alias: {
            vue: 'vue/dist/vue.esm-bundler.js',
        },
    },
});

and the problem is - when I run
npm run dev

the styles & scripts work properly!
But when I run npm run build and load the page - it's awful

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

I had a look at your project to ensure it's not an issue with Laravel UI.
Your project has a mixture of CSS and SCSS. The welcome.blade.php view is loading resources/css/app.css but the app.blade.php layout is loading resources/scss/app.scss.
Your vite.config.js is only compiling resources/css/app.css, so the pages that load resources/scss/app.scss will fail in build mode.


Add optional project filter to features generate types command

++ on this

👍 This is important for orgs codebases that organize flags by projects, where a project represents an application within the org.

+1
Have the same issue for the  pro payment plan.
@tinahollygb Is it possible to expedite the approval of this PR somehow?

We have several projects. Features and experiments are loaded only for a specific project, but types are loaded for all.
It's a little annoying. Let's merge this pull request and fix the problem.

Hi all, the person who was managing this repo is no longe at GrowthBook. I'll raise this internally since there have been some upvotes lately. Thanks for your time and interest.

I merged the PR. I'd like to refactor some of the code but this would have too much to carry for this one.


Delete Column Function

There is an add column function but there is no delete column function.
Being able to delete columns would be cool.

Yes, no delete column. However, there is a "Hide" column function may suit you need


fix(controller): Support emissary on Windows

Signed-off-by: Markus Lippert<EMAIL_ADDRESS>

@alexec having a hard time getting make codegen to work on my machine. Could you do that for me please?
BTW: good work on the emissary executor, almost no changes needed for Windows


Replace invalid characters in labels

Currently, there is no sanitation of labels, and using an illegal character in the label will cause the failure of the goal. Add sanitation of label values replacing invalid characters.
https://jira.atlassian.com/browse/CONFSERVER-7934

fix available from release 6.6


⚠ Bofrost.lu has degraded performance

In 0e03725, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 879 ms

Resolved: Bofrost.lu performance has improved in d6676b5 after 8 minutes.


Google Transparency Report Error

Hi
When I discover domain, GTR gives an error like;

Hi there, thanks for reporting! Looks like Google has changed something around GTR that I need to adapt to. I'll push out a fix ASAP.

Luckily turned out to be an easy fix. The collector works again in version 0.4.1. You can get the new version by running gem update aquatone

It is OK, thank you.


Toward Fn::If intrinsic

I'm running into casing problems here now:
{
  "method": "/pulumirpc.ResourceProvider/Check",
  "request": {
    "urn": "urn:pulumi:cdk-kinesis-test-1::pulumi-kinesis::cdk:index:App$cdk:construct:teststack$cdk:construct:aws-cdk-lib/aws_kinesis:Stream$aws-native:kinesis:Stream::mystreamF3EDC6B7",
    "olds": {},
    "news": {
      "name": "my-stream",
      "retentionPeriodHours": 24,
      "shardCount": 3,
      "streamEncryption": {
        "EncryptionType": "KMS",
        "KeyId": "alias/aws/kinesis"
      }
    },
    "randomSeed": "o0Ct4XOAo2WKrbNOCMK+NEErwjdWTNaIIhT8jsOFk0Q="
  },
  "response": {
    "failures": [
      {
        "property": "streamEncryption.EncryptionType",
        "reason": "unknown property streamEncryption.EncryptionType"
      },
      {
        "property": "streamEncryption.KeyId",
        "reason": "unknown property streamEncryption.KeyId"
      }
    ]
  },
  "metadata": {
    "kind": "resource",
    "mode": "client",
    "name": "aws-native"
  }
}

I think we're sending incorrect-cased sub-properties to aws-native. Digging in a bit, not sure if preexisting problem or something introduced just here.

This depends on https://github.com/pulumi/pulumi-cdk/pull/228 but once that is in hopefully can pass integration tests here.


Enable "Use Rosetta to run Intel code" still lead to hang up in v0.13.0

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

Run build command like:

docker buildx build --push --platform linux/amd64 -t foo:1.0 .

2.See error
Expected behavior
Enable "Use Rosetta to run Intel code" and docker build can finish
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Attach log files by opening OrbStack's Help menu and clicking “Show Logs”, or email them for privacy.
PLEASE ATTACH THE ENTIRE LOG FILE WITHOUT REMOVING ANY LINES. There is usually important context earlier in the log.
vmgr.log
Info report

OrbStack info:
  Version: 0.13.0 (130000)
  Commit: ba57f21d6c60d45e0469196f4a67c79ec9911eea (v0.13.0)

System info:
  macOS: 13.4.1 (22F82)
  CPU: arm64, 8 cores
  CPU model: Apple M1

Additional context
Add any other context about the problem here.

Please share the full build output with only necessary parts redacted. These issues are highly workload-specific.

Also, what is the build doing? Rust, Go, C, etc.? Even better if you could share a copy of your Dockerfile (redacted as necessary).

Dockerfile:
# Stage dev ####################################################################

FROM node:18-alpine AS dev

WORKDIR /app

# Configure NPM mirror
# RUN npm config set registry=https://registry.npm.taobao.org/

# Stage build ##################################################################

FROM dev AS build

# Install JavaScript packages
COPY package.json ./
RUN npm install -g pnpm && \
    pnpm i --shamefully-hoist

# Add App source codes
COPY . .
RUN pnpm run build:h5

# Stage release ################################################################

FROM nginx:stable-alpine AS release

COPY --from=build /app/dist/build/h5 /usr/share/nginx/html/
COPY ./nginx/ /etc/nginx/

buildx ls:
docker buildx ls
NAME/NODE     DRIVER/ENDPOINT STATUS  BUILDKIT                              PLATFORMS
default       docker
  default     default         running v0.11.7-0.20230525183624-798ad6b0ce9f linux/arm64, linux/amd64, linux/386
desktop-linux                 error
orbstack *    docker
  orbstack    orbstack        running v0.11.7-0.20230525183624-798ad6b0ce9f linux/arm64, linux/amd64, linux/386

Cannot load builder desktop-linux: Cannot connect to the Docker daemon at unix:///Users/alexgao/.docker/run/docker.sock. Is the docker daemon running?

build running info:
docker buildx build --push --platform linux/amd64 -t registry.cn-hangzhou.aliyuncs.com/dskb/asiagames-app-html:1.0.15 .
[+] Building 44.6s (9/14)                                                                            docker:orbstack
 => [internal] load .dockerignore                                                                               0.0s
 => => transferring context: 167B                                                                               0.0s
 => [internal] load build definition from Dockerfile                                                            0.0s
 => => transferring dockerfile: 722B                                                                            0.0s
 => [internal] load metadata for docker.io/library/nginx:stable-alpine                                          3.7s
 => [internal] load metadata for docker.io/library/node:18-alpine                                               3.1s
 => [release 1/3] FROM docker.io/library/nginx:stable-alpine@sha256:5e1ccef1e821253829e415ac1e3eafe46920aab0bf  6.6s
 => => resolve docker.io/library/nginx:stable-alpine@sha256:5e1ccef1e821253829e415ac1e3eafe46920aab0bf67e0fe8a  0.1s
 => => sha256:0f737f8ba72d336d5e5e5c6f4ae163ef15c047b58ec5d88fdcb277be61d1aebb 1.78kB / 1.78kB                  0.0s
 => => sha256:55ba84d7d539b7b387916ad1e2740a0a2324323c650ad95067a72aa3e82154c5 16.32kB / 16.32kB                0.0s
 => => sha256:5e1ccef1e821253829e415ac1e3eafe46920aab0bf67e0fe8a104c57dbfffdf7 1.65kB / 1.65kB                  0.0s
 => => sha256:4db1b89c0bd13344176ddce2d093b9da2ae58336823ffed2009a7ea4b62d2a95 3.37MB / 3.37MB                  4.7s
 => => sha256:6f8beccece3b9e5a23da9a36b42b66b71e89babe72e69651b3cc20e2deb77262 1.80MB / 1.80MB                  4.7s
 => => sha256:efba416b8a870e652216bf6a1f6701f5a0853c7e3313de210fb5f02238e88a3a 626B / 626B                      4.8s
 => => extracting sha256:4db1b89c0bd13344176ddce2d093b9da2ae58336823ffed2009a7ea4b62d2a95                       0.0s
 => => sha256:6e7bc8944b52928d034f629fdf916b3597d1c034f99255e70e6dbbb111e1d751 959B / 959B                      5.1s
 => => sha256:72805f9582fb92f298a2a8a660f212ed10b058a4024b459ee33c32854dde4f35 773B / 773B                      5.1s
 => => extracting sha256:6f8beccece3b9e5a23da9a36b42b66b71e89babe72e69651b3cc20e2deb77262                       0.1s
 => => sha256:4c6615db462e72f703d5c194521e0e09f9d7bad17e9790109cfc0e3f01a1d2b6 1.40kB / 1.40kB                  5.2s
 => => extracting sha256:efba416b8a870e652216bf6a1f6701f5a0853c7e3313de210fb5f02238e88a3a                       0.0s
 => => extracting sha256:6e7bc8944b52928d034f629fdf916b3597d1c034f99255e70e6dbbb111e1d751                       0.0s
 => => extracting sha256:72805f9582fb92f298a2a8a660f212ed10b058a4024b459ee33c32854dde4f35                       0.0s
 => => sha256:d799d200ba56fecd1b61f7bbc20adf88875d98ecb5f04dc6b0138ff8a563bb7c 11.65MB / 11.65MB                6.2s
 => => extracting sha256:4c6615db462e72f703d5c194521e0e09f9d7bad17e9790109cfc0e3f01a1d2b6                       0.0s
 => => extracting sha256:d799d200ba56fecd1b61f7bbc20adf88875d98ecb5f04dc6b0138ff8a563bb7c                       0.2s
 => [dev 1/2] FROM docker.io/library/node:18-alpine@sha256:d5b2a7869a4016b1847986ea52098fa404421e44281bb7615a9  5.5s
 => => resolve docker.io/library/node:18-alpine@sha256:d5b2a7869a4016b1847986ea52098fa404421e44281bb7615a9e361  0.0s
 => => sha256:31e352740f534f9ad170f75378a84fe453d6156e40700b882d737a8f4a6988a3 3.40MB / 3.40MB                  3.1s
 => => sha256:560412e561fb4693d4bc6e5d197ccdfb42d1453d0eebf0d772baeacdbaab4b63 47.49MB / 47.49MB                4.0s
 => => sha256:02735cb6c78bf40ddce33f02c68827a8ae3fdc99370db62c77e21c995ace836a 2.34MB / 2.34MB                  2.7s
 => => sha256:d5b2a7869a4016b1847986ea52098fa404421e44281bb7615a9e3615e07f37fb 1.43kB / 1.43kB                  0.0s
 => => sha256:bf6c61feabc1a1bd565065016abe77fa378500ec75efa67f5b04e5e5c4d447cd 1.16kB / 1.16kB                  0.0s
 => => sha256:f85482183a4f18ec843fea14e64575a5550f153211c5b497fea50353cb088645 6.73kB / 6.73kB                  0.0s
 => => sha256:86d562f7b85533d4f8cf87a09747444f7002c74b1897f5e4db2ffbeafa3013b3 450B / 450B                      3.2s
 => => extracting sha256:31e352740f534f9ad170f75378a84fe453d6156e40700b882d737a8f4a6988a3                       0.1s
 => => extracting sha256:560412e561fb4693d4bc6e5d197ccdfb42d1453d0eebf0d772baeacdbaab4b63                       1.4s
 => => extracting sha256:02735cb6c78bf40ddce33f02c68827a8ae3fdc99370db62c77e21c995ace836a                       0.0s
 => => extracting sha256:86d562f7b85533d4f8cf87a09747444f7002c74b1897f5e4db2ffbeafa3013b3                       0.0s
 => [internal] load build context                                                                               0.0s
 => => transferring context: 2.11MB                                                                             0.0s
 => [dev 2/2] WORKDIR /app                                                                                0.1s
 => [build 1/4] COPY package.json ./                                                                            0.0s
 => [build 2/4] RUN npm install -g pnpm &&     pnpm i --shamefully-hoist                                       35.2s
 => => # /Reference/Global_Objects/Array/sort#browser_compatibility
 => => # Progress: resolved 139, reused 0, downloaded 122, added 0
 => => #  WARN  deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issue
 => => # s/3142
 => => # Progress: resolved 162, reused 0, downloaded 147, added 0
 => => # Progress: resolved 191, reused 0, downloaded 174, added 0

hang up here

It looks like you're not using Rosetta. From your log:
🐧 system |   -  Using QEMU

@kdrag0n Clean log is here
vmgr.log

Does the issue still occur now that Rosetta is actually on?

Any chance you can share the package.json? Just need the dependency list.

Still occurs.
I think i have the same problem
Webbuck build in node container just hangs when using Rosetta (always at 80%)
Without using Rosetta, everything works correctly, but for a very long time

@dreyup Is it possible for you to share a reproducer or sample project? It might be a different issue — hard to tell.

@dreyup Is it possible for you to share a reproducer or sample project? It might be a different issue — hard to tell.

Unfortunately I can't provide more details as this is a company code. But there is definitely a problem when using Rosetta and containers with a node.
I tried Docker desktop - there is an error vmtracker attempted to allocate existing mapping
Colima - freezes at 80%
OrbStack - freezes at 80%
I have tried various settings. Works in all cases only when Rosetta is disabled.

Fixed Rosetta+Node.js hangs for the next version.

You can try the the fix early with this release candidate build: https://github.com/orbstack/orbstack/issues/204#issuecomment-1627379793

Fix released in v0.14.0.


⚠ Spryr has degraded performance

In 33138b8, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6063 ms

Resolved: Spryr performance has improved in a9ed68e after 44 minutes.


Feature/contributor page

Codecov Report

Merging #216 into develop will increase coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #216      +/-   ##
===========================================
+ Coverage     98.9%   98.95%   +0.04%
===========================================
  Files           83       85       +2
  Lines         3939     4303     +364
===========================================
+ Hits          3896     4258     +362
- Misses          43       45       +2

Impacted Files
Coverage Δ

ppa/pages/management/commands/setup_site_pages.py
100% <100%> (ø)
:arrow_up:

ppa/pages/migrations/0009_merge_20181217_1350.py
100% <100%> (ø)

ppa/pages/models.py
100% <100%> (ø)
:arrow_up:

ppa/pages/tests/test_models.py
100% <100%> (ø)
:arrow_up:

ppa/pages/migrations/0008_contributor_page.py
100% <100%> (ø)

ppa/archive/models.py
98.48% <0%> (-0.13%)
:arrow_down:

ppa/archive/tests/test_views.py
100% <0%> (ø)
:arrow_up:

ppa/archive/tests/test_models.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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