Export issue

I use Crome and have had great fun making up new brews, however any time I attempt to export my brews in any manner it wont let me. It continues to load the preview for my brews and never stops somehow preventing me from either printing it or saving it as a PDF which results in the page to become non responsive. Any help would be greatly appreciated as I would really like to get my brews into PDFs to share with my fellow gamers.

I know it's been a while, but if you are still having this problem, could you provide the share link to your document so we can see what's going on? We would like to solve this if we can.

@calculuschild, @ericscheid, I suggest that we close this one

Closing since there hasn't been a reply from the user for a while and it is assumed the problem was solved.
If you are still experiencing this issue, feel free to reopen and provide information, @varenflow


Update to arkworks 0.4.0

This updates all Arkworks dependencies to the most recent Arkworks 0.4.0/0.4.2 versions.
Solves issue https://github.com/nikkolasg/snarkpack/issues/9

That's great, thanks a lot for this effort ! I have mainly two requests at this point before merging, let me know how that sounds:

Could you run a quick performance test, manually, before and after to see how perf evolves with 0.4 ?
Would you be willing to go the extra miles and add support for github action CI, just at least testing, so we can see that this PR doesn't break anything before merging ? There's already circle CI but now I think github action is just strictly simpler and better.

I can help on those as well if it's too much, let me know how that sounds.
Thank you !

Let me do another PR first tomorrow, which adds basic CI and benchmarking to the status quo, before we merge this PR. I will also share some bench results here tomorrow!

@nikkolasg : I created this PR, which we can merge first, it also adds a bot which reports benchmark diffs of future PR's:
https://github.com/nikkolasg/snarkpack/pull/10

These are the criterion benchmarking results I get from running the groth16_aggregation on my local machine (Core i7-10610U CPU @ 1.80GHz, 16GB RAM):
Arkworks 0.3.0:
groth16 aggregation     time:   [1.0761 s 1.0787 s 1.0814 s]
Arkworks 0.4.0:
groth16 aggregation     time:   [882.16 ms 884.54 ms 887.10 ms]

Awesome - seems like passing to 0.4 improved by 10%.
BTW if you're using this / plan to using this in prod, we can talk more down the line there are further math optimization to be done.
Also, I can also give you a maintainer role in the repo if you're likely to hack on it often. Just let me know.
Happy to merge this way once conflict resolved.
Thanks a lot and thanks for the CI PR !

Sure! We can also talk about adding me as a maintainer!
We are not aiming for using this in production immediately, but perhaps in the future.
I'd recommend removing the CIRCLE CI then, since it seems not to work any longer?
If you create a PUBLISH_TOKEN in the repos secrets first, we will get the benchmark diffs posted here ;)

I did some of the clippy suggestions, I'm happy to take another look at the remaining ones tomorrow!

There are so many suggested clippy fixes, that I reverted the ones that I already solved. I think for reviewability; it is better to do a follow-up PR which addresses them, where I cherry pick them from this PR.

I've made you a collaborator - need to accept invite.
I've setup a secret as well named PUBLISH_TOKEN and containing an API publish token for this repo but the GH action doesn't seem to pick it up, it's weird (I've actually never used those before so I may be missing a big step).

Ahah i know why: these are not passed from a PR that comes from a fork ;)

I'll merge and then we can do another PR from this repo to trigger it.


Problem in showing the index.html result in colab

I have tried to simulate the Agentsims in colab and I have problem in runnings the index.html file in this colab page (link of it).
I get 404 code.
Maybe the resin is because of this part of it:
import json

# Define the content of the JSON file
content = {
    "gpt-3.5": "sk-XnrwpTOQ03xgtxxx"
}

# Convert the content to JSON format
json_content = json.dumps(content)

# Write the JSON content to the file
with open('/content/AgentSims/config/api_key.json', 'w') as file:
    file.write(json_content)

The tunneling and result page is shown at below:

Also I asked at this stackoverflow page.

I'm sorry, I have not used colab before. From the issue, it seems more likely to be a communication problem between the frontend and backend network connection.


Any plan to change dust to 136sat

Hi Aust,
The dust policy has been changed after Node 1.0.5, now the minimum output is 136sat, according to the release note.

I broadcast 136sat and 135sat on WoC.

136sat, OK

https://whatsonchain.com/tx/827ad66201f7eb74e6ef6fc2214517a17946712d06cbf2090f4ec577d47cb3d5

135sat, failed

0100000001cb163b2fbf0b90b0b6da01515e39cf5c9ea87b207028185d9c4ce49d69da7446000000006a473044022045b0c94a4aee3526c1b5fb64cecae014762b8b19c5bd202a83082b845737f5e0022077f079a5eeb8ff86e80c9580d036f51960ed04b35c392640d11d3dc5db1d74214121028f4d50294ad3a60703fd8f48be59f2543988eff880a7cb28d9940ee68a992cdbfeffffff0286000000000000001976a9146127e47d5f28d322ef454548af46d9b5b652d68888ac27020000000000001976a914b49bd472ff3e2cdd3b1dd472f114de1bd5ab9fa488ac93090a00

Any schedule to follow this? Thank you!
https://github.com/AustEcon/bitsv/blob/72a48a36fbf2e9abd0c32ba2316f83cf169131c8/bitsv/transaction.py#L18

Thanks for this. As long as it always relays every time and confirms then no objections from me.
I guess I will put it on the todo list then 😉

Yes, agree. It still needs some time to wait for the majority of nodes to upgrade.


Helper functions for khash (patch available)

I've been using klib's khash for my own project, and I've written some convenience functions. I was wondering if there might be interest in incorporating them into the core implementation:

kh_getval(name, h, key, defval): Return the value corresponding to key key, or defval if the key is not found.
kh_set(name, h, key, val): Set the value corresponding to key key to val, inserting into table if key is absent and overwriting if present.
kh_unset(name, h, key): A more user-friendly kh_del(): checks if key is in the table, and deletes if it is.

I would be happy to submit a pull request incorporating these.

this sounds useful. would you mind sharing your patch, @krivit ?


Date Picker: Enable display of valid & invalid dates

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the Modus style guidelines

Proposal
Add an optional input property that accepts a list of dates which will be displayed in the date picker as clickable; dates not in the passed in list are displayed as disabled. An alternate solution could be to expose an isDateEnabled function, which the user can then pass in to handle their specific logic. This is how Ionic handles the same type of functionality: https://ionicframework.com/docs/api/datetime#advanced-date-constraints
Motivation and context
We have a use case where the user has to select a date window to display machine data across. Machines however don't have data available every day; it would thus be useful to provide some visual affordance to guide the user towards picking days that actually do have data available, instead of picking dates and seeing an error message pop up.
What is the issue regarding ?
@trimble-oss/modus-web-components
Priority
Medium
What product/project are you using Modus Components for ?
WorksOS / Machine Playback
What is your team/division name ?
CCFS/Weka
Are you willing to contribute ?
Yes
Are you using Modus Web Components in production ?
No response

@prashanth-offcl to check this issue and update

Hi @prashanth-offcl, sorry, I missed this message. I should be able to make some time for this in a few weeks time :+1:

I've started to look into this. I have some basic functionality working, where the date picker exposes a property isDateEnabled, which takes a function. The function is called for every date being rendered and returns true or false. In this screenshot, only weekend dates are valid as an example.

This will cover some cases, but falls short in others. I can imagine that it might be expensive for a service to return all valid dates across all time upfront and instead make requests as the calendar is being operated. The simplest interface I can imagine is adding an additional property isDateEnabledLoading, which sets a boolean that displays a loading bar at the top, as show in the clip below:
https://github.com/user-attachments/assets/6755d4d7-7310-4ab8-85b8-9a6059b4f74e
This would also require another event to be emitted from the calendar, something like calendarNavigated (emitting the date), which the developer can then use to fetch data for that month (they can also prefetch next & previous months to avoid showing the loader when possible). Let me know what you think @prashanth-offcl .

This issue has been resolved in the PR #2934 . Hence closing the issue


Home Connect Smart Start

Homeconnect has added an official smart start functionality based on emissions or, crucially, tariff price. It would be amazing by if this could be assed to the home connect alt integration. Allowing it to be toggled on and off as needed by the user (sometimes you just want the machine to run immediately, regardless of price).
thanks in advance.

People have been using the integration to do exactly that, using automation, for a very long time, so in that regard it's already possible.
When you say they added official support for it, what do you mean and where do you see it? I took a quick look at the API documentation and didn't see any new APIs to configure tariffs, so it might be just logic they added to the mobile app which does the same thing the above mentioned automations do.

I guess it's logic in the app itself. As I mentioned a lot of people are doing it with the integration using HA automations. You can search the issue and forum for some examples. Since you don't have to implement a generic system but just something that works for your specific low tariff it's pretty straight forward to do.

Closing because this is not going to be implemented directly by the integration but can be done using automation.


Twillo's Autjy

Extension
https://www.raycast.com/guga4ka/authy
Description
I'm experiencing corrupted code on all of my keys:
https://cloud.agsoundtrax.com/5zubnkXR
Steps To Reproduce

Unauthorized device.
Authorized again.
Experiencing errors.

Current Behaviour
No response
Expected Behaviour
No response

seems like a backup password is wrong

You're right. Thank you! It would be helpful to have the error reason in the extension window. Thanks again for your assistance!

@adigold it should show an alert like it

could you pls say, do you have 7 digit OTPs like twitch, twilio, pinterest etc?
@raycastbot close this issue

I haven't seen this pop-up alert, and you're right. I only received a single Twitch OTP code.
On 30 Oct 2023, 15:39 +0200, guga4ka @.***>, wrote:

@adigold it should show an alert like it
could you pls say, do you have 7 digit OTPs like twitch, twilio, pinterest etc?
@raycastbot close this issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

yeah, this is a source why this alert wasn't shown. Will fix in next release

Perfect!
Thanks
On 30 Oct 2023, 16:28 +0200, guga4ka @.***>, wrote:

yeah, this is a source why this alert wasn't shown. Will fix in next release
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


PodeListener RequestTimeout Attribute not found

Describe the Bug
I'm trying to run Pode 2.3.0 as standalone on Windows 10 20H2 with PowerShell 5.1 (latest CU) and am getting the following error (sorry - it's in german):
It translates to something like "RequestTimeout" Attribute was not found on $listener.
Die Eigenschaft "RequestTimeout" wurde für dieses Objekt nicht gefunden.
In Zeile:1 Zeichen:1
+ $listener.RequestTimeout = $PodeContext.Server.Request.Timeout
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

I get this error even if I define one basic route and fire the listener up with:
$podePort = 7788
Add-PodeEndpoint -Address <IP_ADDRESS> -Protocol Http -Port $podePort

Platform

OS: Windows 10 20H2
Browser: Unrelated
Versions:

Pode: v2.3.0
PowerShell: 5.1.19041.1023

Additional Context
If I set a breakpoint in private/PodeServer.ps1 on line 46, I can see that PodeListener indeed does not have those attributes it tries to set:
$listener.PSObject.Properties

MemberType      : Property
Value           : {}
IsSettable      : False
IsGettable      : True
TypeNameOfValue : System.Collections.Generic.IDictionary`2[[System.String, mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089],[Pode.PodeWebSocket, Pode, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]]
Name            : WebSockets
IsInstance      : True

MemberType      : Property
Value           : False
IsSettable      : False
IsGettable      : True
TypeNameOfValue : System.Boolean
Name            : IsListening
IsInstance      : True

MemberType      : Property
Value           : False
IsSettable      : False
IsGettable      : True
TypeNameOfValue : System.Boolean
Name            : IsDisposed
IsInstance      : True

MemberType      : Property
Value           : True
IsSettable      : True
IsGettable      : True
TypeNameOfValue : System.Boolean
Name            : ErrorLoggingEnabled
IsInstance      : True

MemberType      : Property
Value           : System.Threading.CancellationToken
IsSettable      : False
IsGettable      : True
TypeNameOfValue : System.Threading.CancellationToken
Name            : CancellationToken
IsInstance      : True

MemberType      : Property
Value           : Http
IsSettable      : False
IsGettable      : True
TypeNameOfValue : Pode.PodeListenerType
Name            : Type
IsInstance      : True

Updated: I just compiled the latest listener version from develop and that one has the Attributes and starts without issues - is the listener version in the 2.3.0 Release maybe not the one that should have shipped with it?

Hey @RobinBeismann,
I've a feeling something may have gotten confused/wrongly cached on your end?
I just tested 2.3.0 on a fresh VM, and works fine; I've also been used 2.3.0 at work for the last month with issue 👀 For RequestTimeout to not be there is like it's cached a 2.1.0 dll somehow (RequestTimeout was added in 2.2.0).
Where did you install the module from? I've been using the Gallery one, so I know that's good; I just checked Choco and that also seems fine, and someone I know is using Docker so should be OK as well 🤔

Hey @Badgerati ,
I used the one from Github Releases, I'll try it on a fresh machine later today just to be sure.

@RobinBeismann, Oh I see! I just tried the 2.3.0-Binaries.zip from the Releases and that worked also 😄

Just to add, this was indeed an issue on my side due to multiple Pode versions being installed.
I'll close the issue, thanks.


directed field cannot be used in EdgeSeed json

There is a bug with the JSON annotation in the EdgeSeed class. It has JsonIgnore on the getter/setter for directed. This means if a user uses 'directed' in json it will be ignored. Currently users have to use directedType.

Merged into develop


Update to Jline 2.14.6

This version of Jline fixes three things for Emacs users:

ANSI colors are now enabled for Emacs.
Terminal echo is now disabled for Emacs.
History is enabled for all dump terminals.

(See the guidelines for contributing, linked above)

This is a copy of #4050 for 1.1.x branch

This also fixes https://github.com/sbt/sbt/issues/3128 thanks to the fix for https://github.com/jline/jline2/issues/286.


Hash or String

The use of 'hash or string' in several places in the spec is a little jarring, it makes it harder to implement and is used inconsistently.
For instance, author appears to allow
"author": "Joe Bloggs<EMAIL_ADDRESS>
and
{
  "name": "Joe Bloggs",
  "email"<EMAIL_ADDRESS>  "web": "http://www.bloggs.com"
}

as valid entries in the object.  Whereas sources is always a list of objects where the keys may appear
 Each source hash _may_ have name, web and email fields.

Perhaps for cases where fields in the object can be string or hash, it would be better to make them hashes and list the keys that may appear?
s/hash/object/g

@rossjones that string shorthand for hash pattern is quite common in npm + node.js land, and I guess that is where the inspiration came from.
I like the pattern in general, but I 100% agree that if we use it in this family of specifications, we should be very explicit about how it is used in any instance, and consistent in the way we apply the pattern across the family of specifications.
I also agree that it does put extra load on implementing the spec.
I'm not sure what action to take on this now (of any), but I'll think about it further. For reference we use this pattern quite prominently on the Fiscal Data Package spec as well: http://fiscal.dataprotocols.org/spec/

Ok, so this approach is directly borrowed from npm where i think it works well. 2 distinct items if i understand it:

Allowing string version of objects in some places - main reason being simplicity for users to add
Inconsistency in allowing string versions for e.g. author but not sources.

On latter I would be happy to make this consistent. On former I do like the usability of simple strings - though we could denote the object form as the "explicit" or "normal" form ("normal" is a reference to mathematics and probably a bit confusing). I note that one of the things the datapackage-read module in node does is sort out these kind of shorthands and convert to the explicit form.
Thoughts anyone?

I was vaguely aware that this was an NPM-ism, but I haven't seen it used as a pattern anywhere else - are we 100% sure it isn't an anti-pattern? Something that's easy to implement in a specific tool but generally imposes more work on consumers.
Guess it's too late to remove now, but fixing the inconsistencies would be good.

@rossjones it is not too late to change on these things and I'm open to a change here - atm i think the convenience is quite high but i know that imposes burdens on implementors (i've felt it!). So really open to comments on the trade-off here.

@danfowler @paulfitz any thoughts here.

Is it ok to agree with everyone :-). Definitely +1 for eliminating unnecessary inconsistencies. But would like to keep the hash-or-string pattern. It is certainly a burden to support, but I think it brings enough pleasure to producers to be worth it.

I also agree with keeping the hash-or-string pattern.  I do think there is work to be done on aligning the similar-but-not-quite-the-same sources and contributors arrays.

@danfowler +1 on all points and on sources and contributors looking similar though note sources are usually files online whilst contributors are people.

@danfowler can i task you with looking at whether any harmonization is needed re sources.

@rgrp Given the broad agreement on keeping the hash-or-string pattern, I think we can close this.
With respect to aligning sources and contributors, I now think that there is nothing critical to do. And given that, like you said, they are referring to fundamentally different things, it is probably wise not to tie them together as they might diverge in the future.

@danfowler @rgrp are we closing this?

@pwalsh I'll close it, seems like @danfowler is happy enough that it's done, and I'm happy enough that it's been answered.

thanks @rossjones


Mapped Types Not working correctly with arrays

TypeScript Version:  2.3.4
Code
interface BaseType {
    "foo":string;
    "bar":number;
}
type MappedType = {
    [P in keyof BaseType]:BaseType[P][]
}
function addToMappedType<P extends keyof BaseType>(mapped:MappedType, key:P, value:BaseType[P]) {
    let array = mapped[key];
    array.push(value);
}

Expected behavior:
array.push should have type signature ts (...items:BaseType[P][])=>number
Actual behavior:
array.push has the type signature ts ((...items:string[])=>number) |((...items:number[])=>number)
And because it lacks a unique call signature it is not able to be invoked.

I don't think this has much to do with arrays, but rather with the types in the mapping being evaluated eagerly or something.  This gives the same problem:
interface BaseType {
    "foo":string;
    "bar":number;
}
type WrappedType = {
    [P in keyof BaseType]: { contents: BaseType[P] };
}
function openPresent<P extends keyof BaseType>(present: WrappedType, key: P) {
    var v = present[key].contents;
    // next line is an error because the type of v
    // is inferred as string | number instead of BaseType[P]
    var v: BaseType[P];
}

I'm guessing this is a design limitation?  Anyway this workaround might help:
function addToMappedType<P extends keyof BaseType>(mapped:MappedType, key:P, value:BaseType[P]) {
    let array = mapped[key] as BaseType[P][]; // explicit cast
    array.push(value); // no error now
}

Try this
interface BaseType {
    "foo":string;
    "bar":number;
}

type Arrayify<T> = {
    [P in keyof T]: T[P][]
}

function addToMappedType<T extends BaseType, P extends keyof T>(mapped: Arrayify<T>, key: P, value: T[P]) {
    let array = mapped[key];
    array.push(value);
}

I don't think it's clear to a developer when the type checker discards the information about the mapping it would need for the code in OP to work.
Given

a type function R<>
a homomorphic mapped type M<>

type M<T> = {
    [K in keyof T] : R<T[K]>
}

a type A
and a generic type K extends keyof A,

it seems like the type M<A>[K] should always resolve to R<A[K]>, whether A is generic or concrete.  But today, this only works for generic A and not concrete A.  Is this a bug, a design limitation, or working as intended?  If it's not a bug then maybe we need some documentation to explain what's going on.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


MSG200: Close / Open door durations not polling status updates

I saw that this issue was posted about one of other garage door models, but I did not see where there was a resolution. I wanted to add not only that this issue is persisting across models, but also add additional information that may help with a resolution is one is not found.
Here is the states they start in when restarting Home Assistant:

This is the message it shows when I go to one of the entities:

But, if I go to my dashboard and hit the button to open and close the garage once, it will then modify the entities and display the correct status.
But, just as someone previously mentioned, the duration always defaults to 35s, when I know for a fact that the durations are 12s. If, I update them manually, they change and work until the next reboot cycle and those entities reset until I push the open and close commands again.
I have the connection state set to auto and polling every 3 seconds
This is how it shows under states:

Is there any additional information you need me to pull for this or was there ever a solution to fix this?

Hello,
I see the point: actually the MSGXXX have different implemetation(s) (varying by firmware maybe?) for the correct message setup about this parameters and so meross_lan has some sort of euristic in place to try get the correct one...
Of course the results might be 'far from ideal' and they are indeed. I'm actually a bit 'away' from code but I'll try to follow up asap and release a better implementation for this.
In the meantime, could you please get a diagnostic trace for the device so I could inspect it's hw/sw capabilities and try get some more understanding?

A solution for this issue should come in the next release. Thanks to #330 I was able to finally get the info needed to correctly parse the newer firmwares with open/close delays correctly set for each channel


split collector and checks needed for every host vs. whole cluster

Some checks need to run once, like checking some value from ceph -s. Otherwise, a failing check for say 'nearfull: True` would show up in every single node being checked, which is not necessary.
In order to have split checks, the collector needs to be reworked as well to split cluster wide metadata gathering (like ceph -s).

[x] split checks
[ ] split collector

The split checks are done as part of PR #97


How to retrieve NLP question answering model with sparsezoo?

I would like to fine tune the pre-trained model for NLP Question Answering: https://sparsezoo.neuralmagic.com/?domain=nlp&sub_domain=question_answering&page=1.
First task would be to retrieve the model from the sparsezoo.
from sparsezoo import Zoo
models = Zoo.search_models(domain="nlp", sub_domain="question-answering")
print(models)

[]

Additional Context: https://github.com/os-climate/aicoe-osc-demo/issues/91

ok after few attempts, I found it: models = Zoo.search_models(domain="nlp", sub_domain="question_answering")


added expression for TAS

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
https://harness.slack.com/archives/C04SV4386Q7/p1714737979702659?thread_ts=1714656997.582069&cid=C04SV4386Q7

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6634d9f9065fb619904fa697--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6634e08bb1d1831df2d8fce8--harness-developer.netlify.app


test: introduce a script to test flag --comm

CLOSE #212

HTTPS may require sending more than two requests over a long connection to be correctly captured 😂.
Can this test be simplified by using curl to request any website (via http), and then using --comm curl? Finally check, when grepping, filter for the domain name (e.g., if curl requests baidu, grep for baidu.com).
What do you think? @spencercjh

HTTPS may require sending more than two requests over a long connection to be correctly captured 😂.
Can this test be simplified by using curl to request any website (via http), and then using --comm curl? Finally check, when grepping, filter for the domain name (e.g., if curl requests baidu, grep for baidu.com).
What do you think? @spencercjh

OK 👌

We could use " http://ipinfo.io" to test, because response of github.com is too big.

It's amazing, the test doesn't report the occasional error after I changed it as you said. Why is that?

We could use " http://ipinfo.io" to test, because response of github.com is too big.

It's amazing, the test doesn't report the occasional error after I changed it as you said. Why is that?

May be some bug 😨, huge response may cause some error, i need to take a closer look. Thank you for spotting the problem!

It seems to have failed again, there should be a bug. I may need to analyze the case of the client side again. You can comment out the case of the client side and only run the case of the server side.😂


Implement context driver for cosmosdb

Emulator docker image works only on windows:
https://github.com/Azure/azure-cosmos-db-emulator-docker

Implemented using MongoDB driver


hipcc ignores --rocm-path if env var such as ROCM_PATH is set

https://github.com/ROCm-Developer-Tools/HIP/pull/2853 - is created by rocm-ci automatically.  @david-salinas  you can close this PR

closing in favour of https://github.com/ROCm-Developer-Tools/HIP/pull/2853


Fix signed store and similar operations

Testing on OSX 10.10 with Apple Clang 7.0.2, I found that doing a store with an int16 (or any signed integer) would silently fail with any optimizations enabled. With no optimizations, the i_store template method in the backend would recurse infinitely until stack overflow. This appeared to be because the templated i_store would always match when V is signed, as no signed implementations occur and the value is not converted to unsigned.
Curiously, store_u works because the front-end calls the templated v_store_u, and that calls i_store_u. Without the template matching, this allows implicit type conversion to change e.g. int16 to uint16. Also the load operations appear to explicitly use unsigned values when calling the backend, then convert to signed if necessary.
This pull request:

Add signed store and load tests
Convert signed to unsigned in store, store_first, store_last, store_packed*, stream
Change the test CMakeLists to do no optimizations. (Optimizations can silently hide these test failures.)

Note that if you add only the CMakeLists.txt change and the updated tests to exercise signed store and signed load (signed load worked originally, but more tests can't hurt), then this is the test output:
test 1
    Start 1: s_test1

1: Test command: /Users/joshblake/projects/libsimdpp/build/test/test1
1: Test timeout computed to be: 9.99988e+06
1/9 Test #1: s_test1 ..........................***Exception: SegFault  0.98 sec

Tests 2-9 still passed.
The rest of this PR fixes this test failure for store as well as similar issues in other memory ops.
Since there were several ways to implement this (and a few techniques used across the backend) I chose the one most similar to existing techniques and least invasive. Let me know if you have any concerns or feedback about this approach.

Thanks for finding and fixing this issue.
Regarding optimizations, in my experience optimizations uncover many more issues than hide them. Instead of relying on the optimization level, I've replaced the optimization level change with tests to check whether the memory operations work, instead of only testing consistency across instruction sets.

No problem!
Yes, definitely agree about optimizations. The original case seemed to be one of the rare times that optimizations hid the problem. (Maybe it converted the recursion to a loop, or detected the infinite loop.)
Thanks also for adding the new tests to confirm the store value. I wasn't sure if it was doing that before but didn't know the best way to add it.


Add the extension to the official extension library

Please release a preview version on the extension store, so that using VSCode Insider is not necessary to test the extension.
Thank you.

We will be working on an official extension release in the next few weeks. Thank you for your patients!

Hi, any progress here?


Is it actually binding to a temporary object

Consider the following code
#include <iostream>
#include <cstdint>
#include <vector>
#include <sycl/sycl.hpp>

class A
{
private:
    using AccessorType = sycl::accessor<uint64_t, 1, sycl::access::mode::read, sycl::access::target::device>;
    const AccessorType& m_Ref;

public:
    A(const auto& ref):
        m_Ref(ref){}
};

int32_t main()
{
    std::vector<uint64_t> yeah(1);
    sycl::buffer<uint64_t, 1> buf{yeah.data(), sycl::range<1>{yeah.size()}};

    sycl::queue q;
    q.submit([&](sycl::handler& h)
    {
        sycl::accessor acc{buf, h, sycl::read_only};

        A a(acc);
    });
}

Here we have a class A that takes const auto& as a parameter to then initialize m_Ref of type const sycl::accessor<...>&. Having auto parameters in constructors is legal since c++20.
However, if you try to build this code, you'll get a compilation error
<source>:14:15: error: reference member 'm_Ref' binds to a temporary object whose lifetime would be shorter than the lifetime of the constructed object
   14 |         m_Ref(ref){}
      |               ^~~
<source>:27:11: note: in instantiation of function template specialization 'A::A<hipsycl::sycl::accessor<unsigned long, 1, hipsycl::sycl::access_mode::read, hipsycl::sycl::target::device, hipsycl::sycl::accessor_variant::unranged>>' requested here
   27 |         A a(acc);
      |           ^
<source>:10:25: note: reference member declared here
   10 |     const AccessorType& m_Ref;
      |                         ^
1 error generated.

which could be fixed by making A constructor to take const AccessorType& as a parameter
A(const AccessorType& ref):

What makes me think that something is abnormal, is the fact that intel oneAPI allows such code to be compiled.
Is it a bug or am I doing something wrong(most probably)?

Define the ACPP_STRICT_ACCESSOR_DEDUCTION macro before including sycl.hpp, e.g. by compiling with the -DACPP_STRICT_ACCESSOR_DEDUCTION flag.
(if you don't have a fairly recent clone of AdaptiveCpp, the macro might be called HIPSYCL_STRICT_ACCESSOR_DEDUCTION).
What happens is that AdaptiveCpp by default has an extension enabled that allows accessors to encode in the exact template type how they were constructed, if you rely on the CTAD deduction guides as in your example. This allows the accessor to perform internal storage optimizations which can help performance in some cases. See here for more information:
https://github.com/AdaptiveCpp/AdaptiveCpp/blob/develop/doc/accessor-variants.md
This means that the accessor type you pass into the class is not exactly the same has the member in your class. There are some implicit conversion operators, so a temporary is created which is why you get this error.
Unless you have very, very good reason I would recommend to stay clear of the buffer-accessor model. Just use the USM memory management model instead. It's easier to understand, more robust, has less surprising behavior and also has lower overhead, so you get better performance.

thanks dude


template warnings under 2021.4.x

2021-04-09 13:17:00 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'mappingproxy object' has no attribute 'icon' when rendering '{%- for item in states.sensor if (.....
Warning is created in the update_battery_status_group_members automation

Proposed fix https://community.home-assistant.io/t/howto-create-battery-alert-without-creating-a-template-for-every-device/30576/947?u=walaj

@jonwaland That fix seems like it wouldn't be what you want. That fix says if icon isn't defined then it will never add the entity. Something like this would probably be better:
              {%- for item in states.sensor if (
                not is_state_attr(item.entity_id, 'hidden', true)
                and (
                  is_state_attr(item.entity_id, 'device_class', 'battery')
                  or (item.attributes.icon is defined and 'battery' in item.attributes.icon | lower)
                  or (item.entity_id | lower).endswith('_bat')
                  or (item.name | lower).endswith('_bat')
                  ) or (
                    (
                      'battery' in item.entity_id | lower
                      or 'battery' in item.name | lower
                    ) and (
                      item.attributes.icon is not defined
                    ) and (
                      not is_state_attr(item.entity_id, 'battery_alert_disabled', true)
                    ) and (
                      not is_state_attr(item.entity_id, 'restored', true)
                    )
                  )
                )
              -%}
                {{ item.entity_id }}{% if not loop.last %}, {% endif %}
              {%- endfor -%}

yup -  my mistake - I meant it to be a qualifier for the check - but put it outside. thanks.
So how to get this added to the actual package for others?

It's up to @notoriousbdg.  Do you want a PR or do you want to just make the fix.

pull request #33 fixes the warnings for me in Home Assistant 2021.11.3 - thanks!


Consider switch to package.json for dependencies

Issue content
Instead using static assets that is unmaintainable we should consider to switch al dependencies management using, already exists by the way, package.json

FontAwesome is now a managed dependency. I keep this open to track other deps that could be managed too.


Windows build of 1.0.2j issues with CPU/platform settings

While I was building 32-bit build of 1.0.2j on Windows using latest ActiveState perl and VS2013 Update 5, I have noticed the following issues:

no-sse2 option seems to be ignored in perl/VS build -- there is a warning about unknown option printed. Furthermore, compiled DLLs still contain SSE2 code, and they crash on Pentium III machines. Reason is that VS 2013 C++ compiler defaults to /arch:SSE2. Therefore, If no-sse2 option is specified, the configure script should add the compiler switch /arch:SSE. Also, if 386 option is specified (which is also reported as unknown by configure), then the configure script should add the compiler switch /arch:IA32, and change the #undef I386_ONLY in opensslconf.h.
Specifying no-hw option together with enable-static-engine leads to unresolved externals during DLL linking phase. It is not obvious how to fix this, at least to me.
There is no way to specify target platform during configuration -- i.e. -D_WIN32_WINNT=0x501 if you want a Windows XP build. The default OS and subsystem version written in DLL PE  optional header is 6.0, while for XP it should be 5.1 which means that the LFLAGS should be set to /subsystem:console,5.1. Finally, as far as I know, DLL projects in Visual Studio always specify the subsystem as windows, not console so perhaps MLFLAGS should be set accordingly.

Regards,
Igor Levicki

no-sse2 option seems to be ignored in perl/VS build -- there is a warning about unknown option printed

The warning [at ms\do_nasm step] can be safely ignored. However, there seem to be misunderstanding about no-sse2. It doesn't control compiler ability to generate SSE2 code, it controls only assembly code generation. I.e. if you specify no-sse2 no SSE2 (or post-SSE2) code will be generated when assembly modules are generated. Same applies to 386 option, i.e. it affects only generation of assembly modules. Compiler has to be controlled separately...

the configure script should add the compiler switch /arch:*

Well, one would be able to argue in favour only if all compilers supported it. Well, one can argue that all contemporary compilers support it, and that I don't really have a case. But trouble is that we make no specific claims about compiler version :-( But it's not impossible to solve this particular problem. All you need to do is to pass additional compiler flag at configure stage, e.g. perl Configure VC-WIN32 -arch:SSE. Note that you don't actually have to specify no-sse2, because SSE2 capability is detected at run-time and post-SSE code assembly paths won't be executed and won't crash your application.

There is no way to specify target platform during configuration -- i.e. -D_WIN32_WINNT=0x501 if you want a Windows XP build. ... /subsystem:console,5.1.

There seem to be misconception. _WIN32_WINNT macro only controls what is exposed through system headers, it has no effect on linker options. And it should be noted that default for 1.0.2 is actually more conservative than 0x501.

The default OS and subsystem version written in DLL PE optional header is 6.0, while for XP it should be 5.1

Default for your compiler, yes. In non-Windows case it would be possible to resolve the problem by passing an additional flag at config time. While on Windows you have an option set LINK environment variable to change the default, e.g. set LINK=/subsystem:console,5.1.
On related note. One can argue that configuration should recognize even /flags (currently it recognized only -flags) and should even recognize /link to pass additional linker-specific flags (currently it recognized Unix-centric -l and -Wl). But it would be hardly appropriate to do that in maintenance branch such as 1.0.2.

To be clear, I was talking only about Windows build using Microsoft compiler. I understand that OSS community doesn't have much interest in putting additional effort into supporting that particular combination, but if you have already implemented build system for that, then it might be prudent to at least document what that build does (or doessn't) and how.
For example, how was I supposed to know that no-sse2 option affects only assembler code? Yes, I could have checked that 100+ KB configure script to see what it (un)defines, then grep all *.c and *.asm files to see what code is affected.
The first step already requires one to be familiar with GNU build system which most Windows developers aren't, and the second step requires considerable not-your-own-code reading skill, including in this case assembler, which might have as well been written in AT&T syntax and which even I who is proficient in x86 assembly might not be able to parse easily.
Furthermore, for me (and I am sure for many other non-native English speakers), no-sse2 option in configure implies that no SSE2 code whatsoever will be generated either by compiler or assembler or by a neural network running a perl script which translates haiku directly into x86 opcodes if that ever happens to become a part of build process.
As for the compiler and options, all relevant compilers have some sort of /arch switch. All Microsoft compilers define _MSC_VER and it is trivial to check which one is used and set switches accordingly. In other words, it is a rather poor excuse not to have the full control of the compiler output at least for the compilers from 2005 onwards just because the old ones might not support it -- if someone still needs to compile using old and unsupported compiler versions such as gcc 2.95 or VC6 I am sure they will have a lot more things to change than just a single switch anyway.
As for _WIN32_WINNT there is no confusion -- macro is defined to prevent you from accidentaly using a newer OS feature in the code (not only new API but also different version of some system structure layout). Linker version specified in /subsystem is related to executable loading. I am aware that I can change that myself as well, but my point was that the build system should have build targets which target certain platforms (Windows hardly counts as a single platform), and not rely on compiler/linker defaults.

For example, how was I supposed to know that no-sse2 option affects only assembler code?

Correct, we can't expect you to know the history behind it(*), but at the same it's not exactly appropriate for you to imagine what it does, and complain about provided explanation, arguing that we are not interested in supporting Windows. We are, we just support it in a way that allows us to optimize the way we do it. By sharing as much as possible, be it code, C or assembly, build and configuration infrastructure... It's not unreasonable compromise.

As for the compiler and options, all relevant compilers have some sort of /arch switch.

So pass one. This kind of discussion was taken several times and it's impossible to get it right. I for one find it inappropriate to rely on compilers defaults that compile explicitly for processor compiler is running on for the moment of compilation, and usually argue for specifying kind of a least common denominator in configuration line, but I'm usually voted down. And it's not a problem. Nor should it be for you. We can't cover all possibilities...

my point was that the build system should have build targets which target certain platforms (Windows hardly counts as a single platform), and not rely on compiler/linker defaults.

There is time and place for this kind of discussion. Ideal time is beta period prior a release, and place is openssl-dev list. Also keep in mind that it's not unreasonable to be reluctant(**) to make changes to branches that are not in active development stage, such as 1.0.2. Especially if there is a way to work around the problem.
(*) no-sse2 originates from time when you could find yourself in situation when OS running on by-then-hottest-news P4 processor doesn't support P4 register extensions;
(**) wording is chosen to indicate that it's not like that changes are impossible, only that they are not taken lightly;

Thanks for the explanation.
If it is not possible to change default compiler options then how about at least updating the INSTALL.W32 with the relevant information we discussed here?
I propose including clarification that no-sse2 is not necessary because of auto-detection, that it does not disable compiler and C runtime SSE2 code, and that passing perl Configure VC-WIN32 -arch:SSE (or -arch:IA32) is the way to make sure code will work on older CPUs.
As for the linker, how do you propose to pass ,5.1 part of the subsystem option without having to edit generated makefile? You said to use set LINK=/subsystem:console,5.1 but that will set the executable type to console for every component built, and if I am not mistaken OpenSSL DLLs should be ````/subsystem:windows``` because they do not require console in order to work.

As for no-sse2. There actually is whole story in INSTALL file, so that we effectively can expect you to know it. As for /arch flag. Apparently it was recently changed. Up to VS2013 lack of /arch flag actually meant "don't use processor extensions", while pasts t

Oh! Wrong click. So I start over.
As for no-sse2. There actually is whole story in INSTALL file, so that we effectively can expect you to know it.
As for /arch flag. Apparently it was recently (in terms of this project lifetime) changed. Up to VS2012 lack of /arch flag actually meant "don't use processor extensions", while past that no /arch flags means "use SSE2" by default. In other words up to recently everything worked as expected, i.e. default configuration would actually produce desired outcome.
As for set LINK=/subsystem:console,5.1 and it's suitability for DLL. Why not just try it and see that it's actually ignored when you link DLL? I mean it is ignored, so that build comes out just fine.

As for closing-re-opening. As already said, I accidentally clicked wring button. However, the issue can as well be closed. I've submitted https://github.com/openssl/openssl/pull/1971 for review, and that's all that need and can be done in 1.0.2 context.

As for set LINK=/subsystem:console,5.1 and it's suitability for DLL. Why not just try it and see that it's actually ignored when you link DLL? I mean it is ignored, so that build comes out just fine.

This is a bit wrong. It's not actually that it's ignored by linker, but it's ignored when dll is loaded to application. In fact we have been linking our dlls with /subsystem:console like forever and nobody complained so far. Then one should also recognize that with LINK environment variable set and command line passed one will take precedence. And if one is "incomplete", i.e. without version specifier, they will be merged.
Closing this. Problem that didn't get attention should be reported separately.


Re-order main sections according to GAnaltyics stats

After new site has had a few months to run, let's re-order the Main Sections according to Google Analtyics stats of which pages are most popular.

overscoped.


Investigate using GN setting is_official_build=true for several base bundles

Enabling is_official_build=true has several benefits as summarized in https://github.com/Eloston/ungoogled-chromium/pull/388#discussion_r179862682. So, I think it would be nice to enable this for configurations that don't link against system libraries, like:

Portable Linux
Windows
macOS

Also, what is the minimum LLVM toolchain version required for this? This is only really a problem for Portable Linux, since some distributions don't ship with a new enough LLVM toolchain. One option is to have is_official_build=true by default, and then create another base bundle with is_official_build=false if demand is high enough. Thoughts?
Once development on 66 has started, I welcome testers to try building with this flag enabled.

The minimum should be LLVM 5.0 as e.g. build/config/compiler/BUILD.gn uses linker options not available in previous versions like --thinlto-cache-dir. Still a patch is required.
LLVM 6.0 is fully supported.

I use this for Bromite, no specific issues to report. You can mention me in case you see something weird during the build and perhaps I can remember if I already met the problem context.
From the top of my head, a note about Google services integration: it checks if a header file with API keys is present, if not it just keeps going. The file obviously is not there in your case as you would get this file only in the internal Google network.

It seems to be working on all platforms so far. Closing.


Ligand preparation failure for Schrodinger and Vina

Hi,
I am trying to run the Glide and ADV demos. However, when I come to run the config via DockStream I am running into these types of errors for both Vina and Glide:
Vina Error:
Traceback (most recent call last):
  File "/Users/michaelcarter/DD_tools/DockStream/docker.py", line 127, in <module>
    ligand_number_start=0)
  File "/Users/michaelcarter/DD_tools/DockStream/dockstream/utils/entry_point_functions/embedding.py", line 38, in embed_ligands
    prep = CorinaLigandPreparator(ligands=list_ligands, pool_number=pool_number, **pool)
  File "/Users/michaelcarter/DD_tools/DockStream/dockstream/core/Corina/Corina_ligand_preparator.py", line 59, in __init__
    raise LigandPreparationFailed("Cannot initialize Corina backend - abort.")
dockstream.utils.dockstream_exceptions.LigandPreparationFailed: Cannot initialize Corina backend - abort.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/michaelcarter/DD_tools/DockStream/docker.py", line 132, in <module>
    raise LigandPreparationFailed
dockstream.utils.dockstream_exceptions.LigandPreparationFailed

Glide Error:
Traceback (most recent call last):
  File "/Users/michaelcarter/DD_tools/DockStream/docker.py", line 127, in <module>
    ligand_number_start=0)
  File "/Users/michaelcarter/DD_tools/DockStream/dockstream/utils/entry_point_functions/embedding.py", line 40, in embed_ligands
    prep = LigprepLigandPreparator(ligands=list_ligands, pool_number=pool_number, **pool)
  File "/Users/michaelcarter/DD_tools/DockStream/dockstream/core/Schrodinger/Ligprep_ligand_preparator.py", line 108, in __init__
    raise LigandPreparationFailed("Cannot initialize Ligprep backend - abort.")
dockstream.utils.dockstream_exceptions.LigandPreparationFailed: Cannot initialize Ligprep backend - abort.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/michaelcarter/DD_tools/DockStream/docker.py", line 132, in <module>
    raise LigandPreparationFailed
dockstream.utils.dockstream_exceptions.LigandPreparationFailed

Do you know of any solution to get this working?
Cheers,
Mike

To give a bit more context - this is the json code I am using to point to my Schrodinger installation:
# specify the embedding and docking JSON file as a dictionary and write it out
ed_dict = {
  "docking": {
    "header": {                                   # general settings
      "environment": {
      }
    },
    "ligand_preparation": {                       # the ligand preparation part, defines how to build the pool
      "embedding_pools": [
        {
          "pool_id": "Ligprep_pool",
          "type": "Ligprep",
          "parameters": {
            "prefix_execution": "export SCHRODINGER=/opt/schrodinger/suites2022-3",
            "parallelization": {
                "number_cores": 2
            },
            "use_epik": {
              "target_pH": 7.0,
              "pH_tolerance": 2.0
            },
            "force_field": "OPLS3e"
          },
          "input": {
            "standardize_smiles": False,
            "input_path": smiles_path,
            "type": "smi"                                   # expected input is a text file with smiles
          },
          "output": {                                       # the conformers can be written to a file, but "output" is
                                                            # not required as the ligands are forwarded internally
            "conformer_path": ligands_conformers_path,
            "format": "sdf"
          }
        }
      ]
    },
    "docking_runs": [
        {
          "backend": "Glide",
          "run_id": "Glide_run",
        "input_pools": ["Ligprep_pool"],
        "parameters": {
          "prefix_execution": "export SCHRODINGER=/opt/schrodinger/suites2022-3", # will be executed before a program call
          "parallelization": {                              # if present, the number of cores to be used
                                                            # can be specified
            "number_cores": 2
          },
          "glide_flags": {                                  # all all command-line flags for Glide here
            "-HOST": "localhost"
          },
          "glide_keywords": {                               # add all keywords for the "input.in" file here
            "AMIDE_MODE": "trans",
            "EXPANDED_SAMPLING": "True",
            "GRIDFILE": grid_file_path,
            "NENHANCED_SAMPLING": "2",
            "POSE_OUTTYPE": "ligandlib_sd",
            "POSES_PER_LIG": "3",
            "POSTDOCK_NPOSE": "15",
            "POSTDOCKSTRAIN": "True",
            "PRECISION": "HTVS",
            "REWARD_INTRA_HBONDS": "True"
          }
        },
        "output": {
          "poses": { "poses_path": ligands_docked_path },
          "scores": { "scores_path": ligands_scores_path }
        }
      }]}}

with open(docking_path, 'w') as f:
    json.dump(ed_dict, f, indent=2)

Do I have to also point towards my valid license for Maestro also?


Simplify debug representation of partial type

I have another feature request :)
Currently when i #[partially(derive(Debug))] and then print a partial, the output contains a lot of None's.
I would be nice if there was some way of only printing the options that contain values.
E.g. we could create a trait PartialDebug which mirrors core::fmt::Debug, but skips Options containing None. And then we crate a blanked implementation for Debug if T : PartialDebug. As a result I could  #[partially(derive(ParitialDebug))] to get a more compact debug representation of my partial.
EDIT: or even better, create a trait PartialDebug which inherits core::fmt::Debug and when deriving that, leave out the None's. Not sure this is possible though....

I don't think this one belongs in this crate - a separate crate should provide such an implementation. For instance, educe provides a way to implement debug using another method or trait, which is almost enough for this (though presumably you want to autogenerate the impl).
I agree there's scenarios where it's nice to be able to print a version of the struct without the Nones, but since partially doesn't enforce the derive(Debug) in the first place, I think it'd be unusual to provide a Debug implementation here, and doubly so for one with an opinionated approach like skipping None.
That said, I'd be open to having some partially_utils or similarly named crate that contains things like this - but currently this is the only idea for that, so I'm not ready to develop it (would happily support you doing that work though, if you're interested).

I'll close this for now, but feel free to continue the conversation here - and if you're interested in that work, let me know and we can reopen/create some better tracking issue.

@bengreenier
(I wanted to say thank you for #7 and #8 a while ago, but then I forgot :).  )
Thank you so much, for implementing this on such short notice. You're doing an awesome job!
Regarding the ticket here: I understand your reasoning and I can live with it :+1:


runtime: TestChan failure on s390x

Seen once on the builder so far:  https://build.golang.org/log/4c0ec95e51e895280902515d8fa6c608487d01a3
Possibly a subtle bug in the new SSA backend.

Not a go test, but a test of something written in go.
https://github.com/cockroachdb/cockroach/issues/9043
I assume this was run on amd64/x86

@bradfitz, you saw it in the trybot run of CL 26762: https://storage.googleapis.com/go-build-log/2b07a28a/nacl-amd64p32_70247f4c.log
Comment 1 is the only time this has ever shown up on the build dashboard, at least for master.

The Android build (which uses go) was updated to 1.7 on Aug 17, since then we've seen 4 occurrences of "fatal error: stopg: invalid status" on the build bots, and I just saw one on a local build.

We've had one failure since I put in the consistency check:
2016-09-26T15:46:44-375092b/linux-amd64:
# go run run.go -- chan/select.go
exit status 2
# command-line-arguments
runtime: gp 0xc420001860 found at rescan index 0 but should be at 33
runtime: gp 0xc4204c0000 found at rescan index 2 but should be at 35
fatal error: bad g rescan index
fatal error: bad g rescan index
runtime: gp 0xc42007e680 found at rescan index 7 but should be at 41
runtime: gp 0xc42007e820 found at rescan index 8 but should be at 42
fatal error: bad g rescan index
runtime: gp 0xc4204c0340 found at rescan index 4 but should be at 37
fatal error: bad g rescan index
runtime: gp 0xc420001a00 found at rescan index 1 but should be at 34
fatal error: bad g rescan index
runtime: gp 0xc42007e340 found at rescan index 6 but should be at 39
fatal error: bad g rescan index
runtime: gp 0xc4204c04e0 found at rescan index 5 but should be at 38
fatal error: bad g rescan index
fatal error: bad g rescan index
runtime: gp 0xc4204c01a0 found at rescan index 3 but should be at 36
runtime: gp 0xc42007e4e0 found at rescan index 9 but should be at 40
fatal error: bad g rescan index
fatal error: bad g rescan index
runtime: gp 0xc4204c0680 found at rescan index 10 but should be at 43
fatal error: bad g rescan index

I'm not sure what's going on here, but it's interesting that a whole pile of Gs were in the wrong places on the rescan list (all of these errors happened while the first error was just trying to get the panic out the door). This suggests we have some sort of ordering issue that's completely smashing the state of the rescan list.

Another failure on the s390x builder: https://build.golang.org/log/2fe597deb692316d5bf7b07bcb0a787e94a8c185
Some of the pointers seem to match up with the amd64 failure: 0xc420001860 at index 0 and 0xc420001a00 at index 1.
# trivial
runtime: gp 0xc420001860 found at rescan index 0 but should be at 17
runtime: gp 0xc420001ba0 found at rescan index 2 but should be at 19
fatal error: bad g rescan index
runtime: gp 0xc420001d40 found at rescan index 3 but should be at 20
fatal error: bad g rescan index
runtime: gp 0xc420001a00 found at rescan index 1 but should be at 18
fatal error: bad g rescan index
fatal error: bad g rescan index

Another trybot flake on linux-amd64:
https://storage.googleapis.com/go-build-log/62ffb414/linux-amd64_7b2388cc.log

Just got an internal bug report of a "rescan list overflow" panic:
fatal error: rescan list overflow

runtime stack:
runtime.throw(0x5d26b9, 0x14)
      .../go/gc/src/runtime/panic.go:569 +0x9e
runtime.queueRescan(0xc42976e820)
      .../go/gc/src/runtime/mgcmark.go:885 +0x103
runtime.newproc1(0x5e79c0, 0xc4255a57f0, 0x20, 0x4bce7b, 0xc42976e680)
      .../go/gc/src/runtime/proc.go:2788 +0x3be
runtime.newproc.func1()
      .../go/gc/src/runtime/proc.go:2716 +0x51
runtime.systemstack(0xc4204958a0)
      .../go/gc/src/runtime/asm_amd64.s:298 +0x79
runtime.mstart()
      .../go/gc/src/runtime/proc.go:1082

This is further evidence that we're adding a G to the rescan list more than once.

A couple more failures on the builders @ 94f49fd:
amd64: https://build.golang.org/log/052fde13671350d57666b95b60eaf455dfed36e1
s390x: https://build.golang.org/log/e7b35b325878d29a540645a435cb0590b94a8aa3

nacl-386: https://storage.googleapis.com/go-build-log/e20d1f23/nacl-386_265589a1.log

I'm not at all an expert on concurrent programming, but there doesn't to me seem to be much preventing adding a G to the rescan list twice? If there are two concurrent calls to queueRescan with the same g, the one that ends up waiting on the lock will still add the g to the rescan list. Shouldn't it check gp.gcRescan != -1 (again, or instead) after taking the lock?

there doesn't to me seem to be much preventing adding a G to the rescan list twice?

The theory, at least, is that everywhere that modifies gp.gcRescan requires exclusive ownership of gp, which is ensured by a different set of locks. So, gcRescan shouldn't be changing underfoot in queueRescan, even if it blocks on the lock. Of course, it's possible we got that wrong, but I suspect we didn't: if there were two concurrent calls to queueRescan, I would expect it to fail at least sometimes with "g already on rescan list", but that's never happened on the build bots.
Looking back over the recent failures, there's a very interesting pattern: the indexes printed by the panic are all off by the same amount (that is, the goroutine at rescan index N was supposed to be at index N+M, for a fixed M). Even weirder, M is specifically 33 in most of the failures.

Looking back over the recent failures, there's a very interesting pattern: the indexes printed by the panic are all off by the same amount (that is, the goroutine at rescan index N was supposed to be at index N+M, for a fixed M). Even weirder, M is specifically 33 in most of the failures.

In all but one of the logs, M is one more than the number of background mark workers. Rescanning of mark workers is funny, so there may well be a bug around this.

In fact, when markroot queues a mark worker for rescan (which is the only type of goroutine markroot queues), it does not own the goroutine. I've been racking my brain trying to find some sequence of events that could cause this to be an actual problem without any luck, but it certainly is suspicious. Unfortunately, I also haven't been able to reproduce this.
However, I'm about to send out a CL that removes the queueRescan from markroot, both because I don't trust it and because it interferes with the hybrid barrier. I suspect that will fix this, but we may have to wait and keep an eye on the builders to confirm that.

Sadly, it looks like CL 31820 (d6625ca) did not fix this. It just happened again at 0acefdb: https://build.golang.org/log/cf689c09c427cfd6494a80b19480c49a6cc392f9

Rescan lists will be disabled in Go 1.8 unless a GODEBUG flag is set. I'm moving this to Go 1.9 with the intent of closing it when we remove recsan lists entirely.
If we decide in the next few weeks that this is worth fixing for a 1.7 point release, we can re-re-milestone this issue.


ARTEMIS-4576 ServerSessionImpl#updateProducerMetrics access large messages after being routed

ServerSessionImpl#updateProducerMetrics method is being called after a message is routed. If the message is a large message, it can be acked quickly and it's backing file will be closed before the method is being called.
This bug causes random failure in test org.apache.activemq.artemis.tests.integration.paging.MessagesExpiredPagingTest#testSendReceiveCORELarge

Once the variable is renamed I think this looks good.
Though I think someone more familiar with the routing and large message stuff should also give it a once over. @clebertsuconic @jbertram

@howardgao I don't actually understand what's being fixed.. it seems the same semantic.. replacing 6 by half dozen?
Perhaps you meant to check this for AMQP, in which case you would have to also check for AMQPLargeServerMessage... or maybe add another method to an upper level?
if you actually create a test to validate what's wrong, it would be check the right fix.

Ohhh.. I see now...

I pushed this directly... hence I'm closing this PR as I already "merged it"


Add annotations to return values

I think it's nice to have annotation for return values :) I'd liked to use something instead of List[dict] but it feels kinda confusing to use List[Dict[str, Union[str, list]]. I'd use pydantic model here or dataclass, but it's overkill here imo

Sorry for the late review on this but thanks for taking an interest!
I'd prefer the more detailed type annotation rather than List[dict] but your point on just using Pydantic models is valid and I'd welcome that contribution if you'd like to make it.
Otherwise, I'll plan to update this repo with some best practice changes (like using Pydantic types all the way through) later this month or next month

Sorry for the late review on this but thanks for taking an interest!
I'd prefer the more detailed type annotation rather than List[dict] but your point on just using Pydantic models is valid and I'd welcome that contribution if you'd like to make it.
Otherwise, I'll plan to update this repo with some best practice changes (like using Pydantic types all the way through) later this month or next month

Sure, I'll make PR using Pydantic models. Can't say when, but hope I'll have time this month

Sure, I'll make PR using Pydantic models. Can't say when, but hope I'll have time this month


Not printing all pages in Mozilla firefox

Hi, I was trying to print a div which also has three more div inside, but it is printing only 1 page not all three. Is there any fix for this?

Same here. Need help urgently

so for example, if you want to print tabs, it doesn't work. It only prints the first tab.


Saving a DXF file not working

Describe the bug
I've just started using this library and I have a problem while adding a very simple functionality. I want to read a file and save it without any changes. It reads the file and saves it but the saved file is a lot smaller and cannot be opened in AutoCAD, when I try the program crashes.
To Reproduce
`
CadDocument doc = DxfReader.Read(file.OpenReadStream());
doc.Header.Version = ACadVersion.AC1018;
using (DxfWriter writer = new DxfWriter(guid + ".dxf", doc, false))
{
writer.Write();
}
`
This code reads and saves the file but the resulting file is a smaller eg. original is 319KB and the one saved by this library is 60KB.
Expected behavior
I would like to see the original file saved correctly. In the end I want to be able to read a file, add entities to it and return it back to the user.
Screenshots
I'm including the crashLog from AutoCAD that I get when I try to open the created file.

Is there anything that I'm doing wrong?

I've been looking at the issue, if is related to the layout, I've merged a fix for an error that I've found in the DxfWriter.

https://github.com/DomCR/ACadSharp/pull/346

Let me know if this fixes the issue.

Hi, thank you for such a quick response. I'll take a look at this as soon as I can, probably tomorrow and I'll let you know if the problem is fixed.
As for the file that I'm using to test it, it is this one:
test_file.dxf.zip

I managed to test it now and it seems to be working correctly for the 2 files that I tested which didn't work before. Thank you very much for the quick update.

Glad to help! if you have any more issues please report them so the project can improve.


Aimbot crash

auto backstab crashes after 3 matches and also improve aimbot

upload config + video of it crashing

follow the template when making issues

ok


Change build system to Vite

Fixes #494
Adds a launch profile which can be used to attach to Chrome and set breakpoints within VSCode in any of our packages. The launch profile will also create a Chrome profile within your .vscode directory so you only need to install React dev tools once.
Adds the web worker for Monaco editor. Didn't include any of the language workers (JS, TS, HTML, CSS, JSON). The worker does not work in dev mode for Firefox, but will work in prod.
Added npm run preview which can run the compiled app. I'm using the .env.local below to build the app, but still run against localhost:10000. The core API URL is used to create the session.
VITE_CORE_API_URL=http://localhost:10000/jsapi
VITE_PROXY_URL=http://localhost:10000

Note that I had issues on Chrome in Ubuntu, where it would just hang with a pending request forever when there was a code change. That issue is identified in this thread: https://github.com/vitejs/vite/issues/5310
A couple of things I did to fix it (all from that thread):

Updated the DefaultLimitNOFILE prop: https://github.com/vitejs/vite/issues/5310#issuecomment-949349291
Updated max_user_instances via sudo sysctl fs.inotify.max_user_instances=8192: https://github.com/vitejs/vite/issues/5310#issuecomment-1181860523

Publishing an alpha now to test w/ DHC
Fixed the local dev mode issue. Also you can run npm run preview from the root now and it will start all 3 on 4000, 4010, and 4020. You need to set .env.local in the 3 files like specified in the root readme
Opened #748 for the error overlay

Local prepareCompose works for me in DHC w/ version 0.16.1-vite.20 published from the latest commit. Tested code-studio, embed-grid, and embed-chart

@mattrunyon it looks like this doesn't generate source maps, is there an option to generate source maps as well? I think you mentioned something like that.
Was just trying to analyze the package size using source-map-explorer.

@mofojed You can add build.sourcemap: true in vite.config.ts and it will generate separate sourcemap files.
Or we can add a rollup plugin to do it like this CLI analyzer or this visualizer plugin
Vite config gets modified like this
// vite.config.ts
import analyze from 'rollup-plugin-analyzer'

export default {
  build: {
    rollupOptions: {
      plugins: [analyze()],
    },
  },
}

@mattrunyon I tried sourcemap: true but it seems like the source maps are incomplete (or source-map-explorer doesn't recognize them anyway:
➜  main git:(vite) ✗ npx source-map-explorer './packages/code-studio/build/assets/*.js'
./packages/code-studio/build/assets/editor.worker.7a4cf0fa.js
  Your source map refers to generated column 1 on line 2, but the source only contains 0 column(s) on that line.
  Check that you are using the correct source map.
./packages/code-studio/build/assets/index.b34304b6.js
  Your source map refers to generated column 1 on line 42, but the source only contains 0 column(s) on that line.
  Check that you are using the correct source map.
./packages/code-studio/build/assets/monaco.bc5092a3.js
  Your source map refers to generated column 1 on line 5, but the source only contains 0 column(s) on that line.
  Check that you are using the correct source map.
./packages/code-studio/build/assets/vendor.85aaeefc.js
  Your source map refers to generated column 1 on line 33, but the source only contains 0 column(s) on that line.
  Check that you are using the correct source map.
./packages/code-studio/build/assets/helpers.162e09a8.js
  Unable to map 597/643 bytes (92.85%)
./packages/code-studio/build/assets/plotly.b80a4841.js
  Unable to map 333/911623 bytes (0.04%)

Using the plugin helps with analyzing package size, but doesn't help us for debugging a production build of the app - source maps would help greatly with that.

I've made the source map explorer package we were using before work. It doesn't create the file in the local directory (like the rollup plugin does) and opens the file automatically (unlike the rollup plugin). The errors it was having is due to the rollup CJS helpers I think which injects code that doesn't map to a source. The error can be ignored and it mentions that it can't analyze like 500 bytes of each bundle
There is a root level npm run analyze that will generate and open a bundle analysis for all 3 bundles (code-studio, embed-grid, embed-chart). You have to have a local build first


Documentation on using Scope within TranslocoService

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[X] Documentation issue or request
[X] Support request
[ ] Other... Please describe:

Current behavior
I'm finding it difficult to understand how to work with scopes via the Translation API as documented here: https://netbasal.gitbook.io/transloco/service-api/translation-api
I am specifically looking for a way to get the entire translation mapping for a scope, in the same way that getTranslation supports getting the mapping for a non-scope.
I can subscribe to a specific translation keys in a scope via selectTranslate, but subscribing to each key doesn't scale.
The component I am developing has translations from the base (e.g. en-US, de-DE), as well as from a scope (e.g. page/en-US, page/de-DE). These translations are being passed to child components, some of which come from an external library and even web components, so they can't be responsible for the translations. Therefore I am looking to use the Observables in the TranslocoService to react to a combination of language changes and TranslationLoadSuccess events, which will update the relevant values depending on the scope.
I'm trying all sorts of things like getTranslation('page/en-US') as is hinted at in the source-code.
If this functionality is missing then this is more of a support request, otherwise, please update the documentation to better explain how to get a scope's translation mapping whole.
Expected behavior
Documentation should provide more clarity on how to use scopes within the relevant functions. For example, does selectTranslateObject('key') support selectTranslateObject('scope/key')?
translateObject('key', {}, 'scope/lang') works but requires a key, can I provide an empty string to get the root translation object?
Why doesn't getTranslateObject exist?
Minimal reproduction of the problem with instructions
Environment

Angular version: 9.0.0

After thinking about this more, it seems I need an Observable that triggers whenever the language changes AND the strings are available. So something like:
// emits when a language file has been changed-out and is available
this.translocoService.translationChange$.subscribe({scope} => this.updateTranslations(scope));

updateTranslations(scope: TranslocoScope) {
  if(scope === "page") {
    this.valueForComponent.firstName = translate('user.firstname', {}, scope);
    this.valueForComponent.lastName = translate('user.lastname', {}, scope);
  } else {
    this.valueForComponent.outage = translate('errors.outage', {}, scope);
  }
}

or a more direct object-access approach like, with less boiler plate:
updateTranslations(scope: TranslocoScope) {
  const translations = this.translocoService.translateObject(scope);

  if(scope === "page") {
    this.valueForComponent.firstName = translations.user.firstname;
    this.valueForComponent.lastName = translations.user.lastname;
  } else {
    this.valueForComponent.outage = translations.errors.outage;
  }
}

Closing this issue since I have figured out some aspects on my own, and don't want to put someone through the hassle of reading my progression above. I hope to return with specific documentation recommendations in the near future.
I think my problem is I didn't setup and configure Transloco in my code, so when accessing the documentation, I found sections assumed the reader understands more than they might.
This was especially true for the Translation API.


Domain doesn't use system provided AWS provider.

I was poking around ec2_synchronize_tags and saw that it makes it's own EC2 client object (using the old "cfme system provided" ruby sdk 1.54).
This means that it doesn't use the system defined proxy config.
I've written a bit about this here:
http://talk.manageiq.org/t/help-getting-access-to-server-config-proxy-url/1724
My question to ManageIQ/Redhat is: how does my "user space" domain access "VMDB::Util.http_proxy_uri" which I think is private.
Now that I think of it an alternative is to use the systems provided AWS provder / client. I'm going to look into how one might do that .In my mind ideally this domain should be able to use the system provided provider but I'm pretty ignorant of the nuts and bolts and hows and whys.
Any comment / ideas?
David

David,
I have not been able to find a clean and reliable way to get this proxy information. It is not as simple as reading the config file because the advance settings yml file is configured on each appliance. Meaning that one appliance could potentially be configured differently from another and this would lead to inconsistencies.
Closing this issue for now.


Unable to extract collection json from stdout, when listing collections through navigator

ISSUE TYPE

Bug Report

SUMMARY

ANSIBLE-NAVIGATOR VERSION

ansible-navigator 2.1.0

CONFIGURATION

---
ansible-navigator:
  execution-environment:
    image: quay.io/ansible/creator-ee
    enabled: true
    container-engine: docker
    pull:
      policy: always

LOG FILE

2022-09-08T16:59:33.372130+00:00 ERROR 'ansible_navigator.actions.collections._parse' Unable to extract collection json from stdout
2022-09-08T16:59:33.372193+00:00 DEBUG 'ansible_navigator.actions.collections._parse' error json loading output: 'not enough values to unpack (expected 2, got 1)'
2022-09-08T16:59:33.372249+00:00 DEBUG 'ansible_navigator.actions.collections._parse' WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
docker: Error response from daemon: Mounts denied:
The path /opt/homebrew/share/ansible_navigator/utils is not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
See https://docs.docker.com/desktop/mac for more info.
ERRO[0000] error waiting for container: context canceled

STEPS TO REPRODUCE

Running ansible-navigator collections
or ansible-navigator collections -m stdout
results in same errors on logfile
EXPECTED RESULTS

No errors
ACTUAL RESULTS

2022-09-08T16:59:33.372130+00:00 ERROR 'ansible_navigator.actions.collections._parse' Unable to extract collection json from stdout
2022-09-08T16:59:33.372193+00:00 DEBUG 'ansible_navigator.actions.collections._parse' error json loading output: 'not enough values to unpack (expected 2, got 1)'
2022-09-08T16:59:33.372249+00:00 DEBUG 'ansible_navigator.actions.collections._parse' WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
docker: Error response from daemon: Mounts denied:
The path /opt/homebrew/share/ansible_navigator/utils is not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
See https://docs.docker.com/desktop/mac for more info.
ERRO[0000] error waiting for container: context canceled

ADDITIONAL INFORMATION

Ansible navigator running on apple silicone with docker engine
MacOS Monterey
Docker version
Docker version 20.10.17, build 100c701

ansible-navigator.log
Attaching the navigator log file

➜  ansible_development ls -al /opt/homebrew/bin/ansible-navigator
-rwxr-xr-x  1 anshul  admin  248  7 Sep 20:58 /opt/homebrew/bin/ansible-navigator

@anshulbehl Can you try this again from using main?  There have been a number of changes recently and the tests are now passing when running on macOS w/ docker
You may also have to allow docker to mount that directory.
In the next couple weeks those files will be moved into the source tree that should help as well


Add English insults from SoMI

Thanks!
For consistency, could you please use the formatting from the German lines and use real apostrophe signs (’) instead of escaped straight single ticks (')?

For consistency, could you please use the formatting from the German lines and use real apostrophe signs (’) instead of escaped straight single ticks (')?

Is there a formatting tool for typescript? I couldn't find one immediately and gave up searching :wink:

Is there a formatting tool for typescript?

Unknown. Honestly, so far I did not edit this yet since it was converted to TypeScript.


Update 0647-palindromic-substrings.java

Made the code more concise and readable.

File(s) Modified: 0647-palindromic-substrings.java
Language(s) Used: java
Submission URL: https://leetcode.com/problems/palindromic-substrings/submissions/975548232/

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

@ColstonBod-oy Good refactoring. Thanks for your contribution 👍


This should of course be in Nuitka

Hello from the Nuitka author,
this whole feature should of course have to be in Nuitka itself. The onefile is just an SFX with no unpacker provided by Nuitka, which apparently triggered this project. I invite you to help inside of Nuitka to create the unpacker, sharing the code constants of the packer, it's not like sometimes I do not have to debug this, and then I would need one.
Best regards,
Kay Hayen

Thanks for the invite. I do plan to contribute to the Nuitka project in the future with regards to the unpacker. It has to be in C as with rest of Nuitka.

Hello,
the packer ist written in Python with zstandard. The current unpacker is in
C but it's a trivial thing. Mostly the header format.
I intend to make changes such that cached mode can skip files for speed.
It would make sense to work on this together. It is not to going  to get
easier as it progresses.
Yours
Kay
extremecoders-re @.***> schrieb am Fr., 14. Juli 2023,
07:54:

Thanks for the invite. I do plan to contribute to the Nuitka project in
the future with regards to the unpacker. It has to be in C as with rest of
Nuitka.
—
Reply to this email directly, view it on GitHub
https://github.com/extremecoders-re/nuitka-extractor/issues/3#issuecomment-1635315942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH62AM2RCMT4PL42VGXV3XQDNKNANCNFSM6AAAAAA2I7ALFE
.
You are receiving this because you authored the thread.Message ID:
@.***>

how could can extract it??

is it possibe to turn nuitka.exe to nuitka.py?

is it possibe to turn nuitka.exe to nuitka.py?

Unfortunately no such way exists or atleast it would be very difficult.


Add big-data-cluster and resource-deployment to sqlBuiltinExtensions

This PR fixes does two things:

Moves vscode for resource-deployment extension to dependencies section from devDependencies as the product code depends on it.
It adds two extensions to sqlBuiltInExtensions so that they are their separate packages. I am doing this to workaround "too many files open" issue observed during linux builds. Discussing with Amir, this looked like a good change to do, in any case but I am not too sure about it. So I thought I will open a PR and discuss the pros and cons of doing this here.

You shouldn't need the vscode package.
My suggestion is essentially only valid if there wasn't anything else we could do to decrease the size of the extension.

Why do you need vscode as a run-time dependency?
I am consused, if this package uses vscode.Event from the vscode package and vscode.commands.registerCommand and other similar functionality from the vscode package, then is that not a run-time dependency?

Vscode dependency includes a testing framework which isn't necessary for production

We use vscode.Event and vscode.commands.registerCommand and other functionality from vscode package, that is not for testing but for product features.

That's not the vscode package, that functionality is included as part of azure data studio.
The vscode package for our context only does testing: https://www.npmjs.com/package/vscode

Abandoning as this change is not needed.

FYI in case Arvind was wondering - we dynamically inject the azdata and vscode modules at runtime by hooking the require / import calls. Hence no NPM package reference is needed / none should be included for the dependencies. Only need for devDependency to enable testing, and for extensions not in the Azure Data Studio repository so that they can pull down a typings file to compile against.

And for testing we should really be using vscode-test instead. (Typings are now from @types/vscode)
https://github.com/Microsoft/vscode-extension-vscode#readme

@Charles-Gagnon vscode themselves aren't using that package for built-in extensions I believe. Might be wrong?

That's correct - I don't know why but their public stance appears to be using the vscode-test. I'm not saying we should go through and update all ours now but something to keep in mind (I haven't checked whether vscode is getting the same updates as vscode-test for example. At some point I imagine that's going to be deprecated)

I actually looked into updating this and I realized I'm going to need to copy a lot of code that already exists in vscode. Like basically a copy/paste. And we have to do that for every single extension - so it might not be worth it?

Like what? There doesn't appear to be much there besides the testrunner and the typings file

I don't remember anymore - should look at it again.

Don't spend too much time on it - I'm not suggesting we actually do it at this point.


Update README.md

adding links to Kaggle notebooks derived from the code

@kmader Thank you for your contribution.


expect select-option input alert

thanks

What are you asking for? Can you include a screenshot of a similar alert from another program?


valence_nbt::List convenience methods

Objective

valence_nbt::List is kind of inconvenient to work with when you are not expecting a specific type of list. You often have to match over every type of list.

Just one example, I would like to write this code:
fn do_something_with_nbt_value(value: valence_nbt::Value) { ... }

for item in list {
   do_something_with_nbt_value(item);
}

Solution

Added several convenience methods to valence_nbt::List to hopefully reduce the match boilerplate in client code, including iterator methods.
I had to introduce borrowing ValueRef and ValueRefMut types. These are only used for list access and modification. I cannot use &Value because the list does not store that type so there is nothing to reference, and worse, &mut Value would allow for non-heterogeneous lists.

Not sure why the CI is failing


Pixel value shorthand on

The following code
import React from 'react';
import ReactDOM from 'react-dom';
import {Style} from 'radium';

ReactDOM.render(


Require ILoggerMessageQueueSemantics

Once akkadotnet/akka.net#1774 is merged in and released, we'll need to tag CommonLoggingLogger with IRequiresMessageQueue.

Implemented in the new 1.0.7 release


Double quote marks in folder names get re-written as " after app relaunch

If you have a folder name that contains double quote marks, they will get rewritten as &-quot; after closing the app. Editing them keeps them as double quote marks, but closing and relaunching the app will have them back to &-quot; (the hyphen after & is only for this bug report, Github helpfully turns those into actual ""s)

@slater, I'm only able to recreate this on Mac 5.0.3.  Could you please verify if this is the release you are using?

Can confirm. I only use NNW on desktop, and I'm on 5.0.3

Since I can't recreate this on iOS and only can on Mac 5.0.3, I'm moving this to Mac 5.0.4.

This is fixed and will be released in Mac 5.0.4.


Grid column padding variable does not affect container

From @rafibomb on February 8, 2016 3:35
Trying to space text away from container edge. I expect the column padding to handle the spacing of text from the container edge.
Changing $grid-column-gutter does not affect this.
Copied from original issue: zurb/foundation-emails#35

From @rafibomb on February 8, 2016 3:36
Looks like it's defined on the <th> at 8px. This needs a setting.

From @rafibomb on February 9, 2016 22:30
Actually, the variable doesn't take effect at all.

Fixed! New variable is $global-gutter


Issue with IRC...Specifically Twitch Chat to Discord.

Up until today it was working fine. Now while I can go from discord to twitch chat, I can't go from twitch chat to discord. I get the following error. But it relays the connections and disconnections.

Received: @badges=broadcaster/1,subscriber/0;color=#FF69B4;display-name=Darksageron;emotes=;id=2d8fb841-c370-456e-9e17-408f7a5a3edb;mod=0;room-id=104029723;subscriber=1;tmi-sent-ts=1530023019692;turbo=0;user-id=104029723;user-type=<EMAIL_ADDRESS>PRIVMSG #darksageron :yesw
26 Jun 23:23:40 - ERROR: Unhandled message: { command:
'@badges=broadcaster/1,subscriber/0;color=#FF69B4;display-name=Darksageron;emotes=;id=2d8fb841-c370-456e-9e17-408f7a5a3edb;mod=0;room-id=104029723;subscriber=1;tmi-sent-ts=1530023019692;turbo=0;user-id=104029723;user-type=',
rawCommand:
'@badges=broadcaster/1,subscriber/0;color=#FF69B4;display-name=Darksageron;emotes=;id=2d8fb841-c370-456e-9e17-408f7a5a3edb;mod=0;room-id=104029723;subscriber=1;tmi-sent-ts=1530023019692;turbo=0;user-id=104029723;user-type=',
commandType: 'normal',
args:
[<EMAIL_ADDRESS>PRIVMSG #darksageron :yesw' ] }

any idea what could be causing this I'm on the latest build of the bot.

I figured it out. I have 3 raw commands that are passed because IRC chat needs to pass these in order to view events from Twitch chat, like logins and outs. One raw command ["CAP REQ :" ,"twitch.tv/tags"] interferes with the bot. but it didn't before which is weird. But I removed the tags command and left in the other two and it's working fine this has been solved.


chore: method specialization

Description
Documents the usage of method specialisation
Problem*
Resolves #3238

I have no idea how 451f4c6 still passed the CI, but it definitely broke master


Mobile: Burner wallet page needs to be refreshed from time to time

This happens only on mobile browsers.
If user leaves page/browser with Burner opened for a while on background without touching it, the buttons stop working and main (ETH) network balance shows as 0 even when it's not (plasma balance is shown correctly). User needs to refresh the page to make wallet working again.
It may be caused by websockets timeout

@artico wrote on slack:

don't you know why burner wallet constantly makes thousands of requests to dai.poa.network? any practical reason? it even crushes my browser sometimes...

https://leapdao.slack.com/archives/CHBFMQ526/p1557510409001300
I think these two observations are connected.
Adding this to the sprint.

Wow! Since June and I forgot about this 🙈. Let me investigate it and work on it now

@iamonuwa Actually, I would recommend not to invest your time into it (unless you really want it). First of all - there is no bounty on this issue anymore. Second, we probably gonna move away from BW v1 in favor for v2 in near future.

Since we are moving. I'll move on to where the need is greater. Thanks


uninitialized variables (initial cppcheck detection)

NOTE: as cppcheck gets more interesting stuff in cppcheck.cfg we may uncover more independent instances of uninitialized variables. TBD whether they lump in with this ticket or get a new one. Probably a new one if we close these promptly, which we should ...
cppcheck messages:
{{{
src/unit-tests/oscore-test/ut_oscore_queue_test.c:552: error: Uninitialized variable: queue_data_out
src/unit-tests/oscore-test/ut_oscore_queue_test.c:562: error: Uninitialized variable: queue_data_out
}}}

Imported from trac issue 137.  Created by glimes on 2015-12-10T14:58:21, last modified: 2016-01-14T11:33:37

Trac comment by sstrege on 2015-12-28 16:09:38:
Commit [changeset:0499639] ready for CCB review

Trac comment by sduran on 2016-01-08 14:09:37:
recommend accept

Trac comment by sstrege on 2015-12-29 13:20:12:
Correction to commit id [changeset:458a031]

Trac comment by glimes on 2015-12-31 13:11:52:
recommend accept

Trac comment by jphickey on 2016-01-11 13:17:31:
recommend accept

Trac comment by glimes on 2016-01-11 13:11:43:
Per discussion on CFS CCB telecon,
marking the proposed tickets with
the "osal-4.2" Milestone.

Trac comment by glimes on 2016-01-14 11:31:23:
Included in the 2016-01-11 CCB merge.

Trac comment by glimes on 2016-01-14 11:33:37:
Development advanced to include the 2016-01-11 merge.


Write proper README

Should include:

Installation
Quick start, both to script usage and CLI usage
Bibtex reference

Implemented in https://github.com/saattrupdan/ScandEval/commit/bca6e0e6f1433c80eed56cbeb55939e1313d69d9.


Fix falsy "enabled" flag being ignored

Because of using the ||= operator, falsy values for enabled were
being ignored and overwritten when the server flag existed.
For mnemosyne.yml files like the following:
common: &common
  server: amqp://localhost

development:
  <<: *common
  enabled: false

...this meant that the enabled: false was being ignored for the
development environment.

:blush: Thx.


ISSUE-692: Upgrade Jetty to 9.4.26.v20200117

This commit fixes #692

@raju-saravanan would you please review this?


feat: add pending bridge call querys

Summary by CodeRabbit

New Features

Introduced new commands for querying pending bridge calls, enhancing user visibility into pending transactions.
Added support for querying bridge calls by nonce, allowing for more detailed transaction tracking.

Bug Fixes

Updated parameter names for improved clarity and consistency in command-line interface queries.

Tests

Added comprehensive tests for querying pending bridge calls, ensuring robustness and reliability.

mg


double quote is not read correctly

Thanks for awesome library!
here is my csv
test1,test2,test3
aa"a,bbb,ccc

and my code
let data = new Uint8Array((this.file as unknown) as ArrayBufferLike)
const encodedData = Encoding.convert(data, { to: 'UNICODE', from: encode, type: 'string' })
const workbook = XLSX.read(encodedData, { type: 'string', raw: true })

I expect it's parsed like blow

but actually like this

RFC said
If double-quotes are used to enclose fields, then a double-quote
appearing inside a field must be escaped by preceding it with
another double quote

https://tools.ietf.org/html/rfc4180#section-2
is it expected behavior?

I am also facing same..
Please resolve this

+1 - double-quote in a field within a TSV is causing corrupted parsing

Hi everyone, thanks for this awesome package... I saw this is closed in the commit 7a00f39... but I downloaded version 0.17.4 and it doesn't work for me. Same case than @sakahiro . What should I do?