Fix item descriptions

Fixes #273
These changes instruct the pipeline to substitute \n to
 in the weapon and material descriptions. Also fixed some code-duplication in 'WeaponSheet.tsx'
Resulting Changes:

'Dodoco Tales' has correct item description
'Sword of Descension' and 'Predator' (PSN Traveler and Aloy weapons) have correct passive description
Material descriptions are HTML-safe, for future-proofing

I think the proper fix is to amend the original paragraph function:
const parsed = string.split('\\n').map((s) => s || '
')

to
const parsed = string.split(/\\{1,2}n/gm).map((s) => s || '
')

@frzyc Sorry for being a newb,. It seems thats, React is happy to receive an array as well as strings, so the original paragraph filter already worked as-is. It just needed to be used here. As a side-effect, weapon descriptions are now arrays, and weapon passive descriptions are 2D-arrays. E.g. Favonius codex
{
  "name": "Favonius Codex",
  "description": {
    "0": "A secret tome that belonged to the scholars of the Knights of Favonius. It describes the logic and power of elements and matter."
  },
  "passiveName": "Windfall",
  "passiveDescription": {
    "0": {
      "0": "CRIT Hits have a <cryo>60%</cryo> chance to generate a small amount of Elemental Particles, which will regenerate 6 Energy for the character. Can only occur once every <cryo>12</cryo>s."
    },
    "1": {
      "0": "CRIT Hits have a <cryo>70%</cryo> chance to generate a small amount of Elemental Particles, which will regenerate 6 Energy for the character. Can only occur once every <cryo>10.5</cryo>s."
    },
    "2": {
      "0": "CRIT Hits have a <cryo>80%</cryo> chance to generate a small amount of Elemental Particles, which will regenerate 6 Energy for the character. Can only occur once every <cryo>9</cryo>s."
    },
    "3": {
      "0": "CRIT Hits have a <cryo>90%</cryo> chance to generate a small amount of Elemental Particles, which will regenerate 6 Energy for the character. Can only occur once every <cryo>7.5</cryo>s."
    },
    "4": {
      "0": "CRIT Hits have a <cryo>100%</cryo> chance to generate a small amount of Elemental Particles, which will regenerate 6 Energy for the character. Can only occur once every <cryo>6</cryo>s."
    }
  }
}


Travis

Changed a couple of things in the project structure (see commits) and created a .travis.yml to build it. The tests for UrlBuilder are passing, but the "integration' test for the pirant module is not working, so I disabled it (we should mock the requests so that the build server doesn't have to connect to devrant every time we want to run tests).
As we discussed, Travis with python only makes sense when you have tests, so we need to implement more tests, but at least now they will be run in travis with every commit. Also, I have only tested it in python3. When I test it in other versions of python I will update this pull request.
I added a "badger" in the README to see the status of the build, which is pointing to my build (https://travis-ci.org/joserc87/pirant), travis branch. If you import your github repo in travis, you can make the image point to the master branch of your repo.
Expect more pull requests with tests soon ;)

I merged all your changes and all the tests pass. I also added some unit tests for the Models. Comments are welcomed :)

As you mentioned about mocking, today I was busy learning and writing UTs using mocks for requests.get(), to prevent hitting devrant server. I am almost done with it. Got to learn Mock in python for first time.

I use mockito in Java. I will check the python version of it.
As you said regarding having having multiple classes in same module. Gets go with this way. I will merge the PR.
Thanks again. If you want to contribute more, feel free to take any of the open issues and comment. I will assign it to you. I will also be working on adding more APIs.

I use mockito in Java. I will check the python version of it.
As you said regarding having having multiple classes in same module. Gets go with this way. I will merge the PR.
Thanks again. If you want to contribute more, feel free to take any of the open issues and comment. I will assign it to you. I will also be working on adding more APIs.


[Service Bus] Investigate streaming receiver behavior when underlying receiver gets closed due to any reason

@ramya0820 commented on Mon Feb 11 2019
Concerns:

Error gets eaten up in OnMessage handler if link is closed
Execution of OnMessage continues even when OnError gets triggered, could lead to potential side-effects

Fixed with #1233

How about the concern where continued onMessage handler execution inspite of async error event may result in potential side-effects?
At the very least we might want to update docs to reflect the behavior?
It may be possible that a user/developer would expect messages to not be processed if an error has occurred (esp when not related to message handler execution?)

Good point, I forgot to address those concerns.
Once the async error event occurs, we know that no new message event will be fired.
So, what is left is processing of the messages already received (by rhea).
Since there is no way the message can be settled, we should try our best to not to run the user's message handler. But if the mode was ReceiveAndDelete, there is no need to avoid running the user's message handler. We can do this by checking this._receiver && this._receiver.isOpen() at the very beginning of _onAmqpMessage
Thoughts?

I think this would tie back to the rhea investigation we had left off at last week.
Things I'd like to have continued experimenting on is to see what happens if we reject the delivery on the link. Since that wouldn't settle the message, I'm thinking that wouldn't delete the message (in peeklock mode), and so it might allow for a smoother handling of this case. (And maybe solve the other issues around allowing us to receive messages at scale).
Receive and delete could then likely be a higher level abstraction that we build on top of AMQP.

Receive and delete could then likely be a higher level abstraction that we build on top of AMQP.

I am not sure there is enough ROI for this adventure. We should see what the other languages that implement the "prefetch" queue do for ReceiveAndDelete mode. The buffer in rhea is similar to the prefetch queue in .net or python sdks.

we reject the delivery on the link. Since that wouldn't settle the message, I'm thinking that wouldn't delete the message (in peeklock mode)

Delete the message where? In Service Bus? In peeklock mode, the message will not be deleted until the message is completed explicitly

#1302 now has changes implementing https://github.com/azure/azure-sdk-for-js/issues/1190#issuecomment-465321432


Exported OPML should contain infromation about tags

Hi, I would like to be able to import OPML from newsboat to another RSS reader (Feeder and Feedly) and have all the feeds categorized instead of one list.
When we export OPML from FreshRSS all feeds have attached tag which becomes a tag in newsboat after importing. I would like to have similar functionality while exporting OPML from newsboat.

Hi! Please see https://github.com/newsboat/newsboat/issues/871 and https://github.com/newsboat/newsboat/pull/1243.


PartialSchema Type extensions

I love the new SubSchema feature from @d-exclaimation!
I think it would be useful to have the ability to extended Types from one SubSchema in another SubSchema.
This would be a natural extension to the new declarative SubSchema feature and would allow you to break up a GraphQL type across multiple packages similar to Swift's extension feature.

One idea might be to naturally combine Types if a Type is declared multiple times in a schema or over multiple schemas.  I'm not entirely sure how this would work with the current SchemaBuilder and PartialSchema.
You potentially run into an issue where a field on a type is declared twice and that might be a little tricky.
Another option would be to have a TypeExtension type.

I have seen this works from the Node.js ecosystem, with graphql-nexus but it somewhat relies on codegen.
The difficult part that I noticed right away would be implementing this in a type safe manner since we won't know the generic ObjectType of that specific Type declaration ahead of time.
Furthermore, I think GraphQL spec's object extensions would already solve this. It would probably make sense to go for this instead, although I am not 100% sure how difficult it would be.

@NeedleInAJayStack, @d-exclaimation, is this a change that would need to happen at the GraphQL level, or can this be isolated to Graphiti?  It would definitely make the declarative PartialSchema feature much more powerful and allow us to highly modularize our resolvers and schema declarations.
Is the type safe manner really an issue because the type would be defined at compile time right?

Adding support for the spec's object extensions would need to also happen at GraphQL level. I have seen some work on adding support for federation which relies on object extensions, but not sure the status on that.
In terms of adding this capability just on Graphiti level, I'll definitely have a look over the week and see if I can work it out

@cshadek If this is high priority for you and you have some free cycles, we sure wouldn't say no to a merge request ;)

@NeedleInAJayStack haha I'm always happy to help - just not that sure where to begin with this one.
I feel like it has to be a change at the GraphQL level and not Graphiti unless we can change how SchemaBuilder works to allow repeat type declarations with different fields and generate the resulting type based on the sum of those fields.
Do you have any ideas on how to go about this?

@NeedleInAJayStack haha I'm always happy to help - just not that sure where to begin with this one.
I feel like it has to be a change at the GraphQL level and not Graphiti unless we can change how SchemaBuilder works to allow repeat type declarations with different fields and generate the resulting type based on the sum of those fields.
Do you have any ideas on how to go about this?

My first thought how this could be done is changing the SchemaBuilder typesComponent property from an array to something like map of the type name and the fields, and as the .add or .use function is called check if the type already exists in the map, just append the fields from the declaration, and rebuild the type at the end when .build is called

@d-exclaimation @NeedleInAJayStack,
I saw that @samisuteria just added federation, which looks awesome!  Does that mean this is solved now?  I haven't yet had a chance to try out federation.

No, not yet. The addition of federation support excluded implementation for code first directives and object extensions. I think @samisuteria is working on adding directives.


Move index.html draft to top level of the repo

This change moves the index.html file for the spec up from the out/ subdirectory and into the top level of the repo.
That aligns this repo/proposal with the convention followed by other TC39 proposals — and (I think) will make the draft proposal available at https://tc39.es/proposal-intl-DateTimeFormat-formatRange/

It won’t make it available there; that requires updating the gh-pages branch, or repository settings.

It won’t make it available there; that requires updating the gh-pages branch, or repository settings.

OK yeah I see — so maybe the repository settings can be updated to make to just make the master branch the source for GitHub Pages publication? Is there any reason not do that? It’s seems preferable for it to be available at a https://tc39.es URL, rather than just at a third-party URL like  https://rawgit.com/fabalbon/proposal-intl-DateTimeFormat-formatRange/master/out/

Thanks! I updated the repo settings to publish the master branch. Now the draft spec is available in: http://tc39.es/proposal-intl-DateTimeFormat-formatRange/

I updated the repo settings to publish the master branch. Now the draft spec is available in: http://tc39.es/proposal-intl-DateTimeFormat-formatRange/

Beautiful — thanks!


Featured Content Modules - Now with video!

Added video to the FCMs.
Additions

Added video to FCMs
Added video FCMs to the-bureau page and careers/application-process

Changes

CSS changes to handle video breakpoints (check them out on events pages)

Testing

Test it on pages by creating FCMs in wagtail
Visit the-bureau and careers/application-process
Visit an event page with a livestream

Review

@jimmynotjim
@sebworks
@anselmbradford

Screenshots

Notes

If you have any tips on removing the black bars, hit me up on chat and we can talk through some solutions, otherwise I'm leaving it for another PR.

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Should you be able to configure the FCM video from within Wagtail?

Should you be able to configure the FCM video from within Wagtail?

Not yet. We need some backend work for that to happen. Ideally, we would just add "ID" and "URL" fields to make it happen.

Looks great. :100:

I think all the review comments have been addressed. @jimmynotjim

:+1:


AMBARI-25363. Daily Namenode Heap Usage alert does not work.

What changes were proposed in this pull request?
Now server uses appId for NameNode alerts in actual case.
How was this patch tested?
Manual testing.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5420/
Test FAILed.
Test FAILured.


[collector] missing rbac permissions in receivers and extensions

There seems to be missing rbac permissions for the collector when trying to use receivers which query the K8s API.
There have been 2 instances which I have noticed:

The k8sobserver extension does not get the required rbac permissions. If I add the k8sattributes processor, then the permissions seem to be added.
The kubeletstats receiver is throwing a 403 forbidden when trying to query node metrics:

kubelet request GET https://xxxxxxx:10250/stats/summary failed - \"403 Forbidden\", response: \"Forbidden (user=system:serviceaccount:observability:<name-of-collector>, verb=get, resource=nodes, subresource=stats)\"", "scraper": "kubeletstats"

Expectation
The operator should automatically add permissions for the extensions/receivers to work. If not, what is the recommended method to add additional permissions to the collector?


pandas.*.sample may return empty objects if frac <= 2^{-axis_length}

A small, complete example of the issue
import pandas as pd

axis_length = 1
df = pd.Series([0])
df.sample(frac=2**(-axis_length))

Series([], dtype: int64)

Expected Output
Series([1], dtype: int64)
Why?
I tried to sample fractions of groups, some groups containted only one entry and were not returned in the sampled frame ( I used groupby(key).apply(lambda x:x.sample)).
A potential fix may be easy: in generic.py line 2634 might be changed from
n = int(round(frac * axis_length))

to
n = max(int(round(frac * axis_length)),1)

If this behaviour is not desired, maybe one could add to the API some keyword like, min_sample_size
Further Remarks
The example can be generalized using np.arange(axis_length). The bound $2^{-axis_length}$ seems to be hard. Increasing the value would return at least one sample entry.
Edit: Depending on the discussion, I'd love to provide a pull request by myself. I think, it's a good start to support pandas and it fits my skill level
Output of pd.show_versions()
Series([], dtype: int64)

# Paste the output here
INSTALLED VERSIONS
------------------
commit: None
python: 3.5.1.final.0
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
LOCALE: None.None
pandas: 0.19.0
nose: 1.3.7
pip: 8.1.2
setuptools: 27.2.0
Cython: 0.24.1
numpy: 1.11.2
scipy: 0.18.1
statsmodels: 0.6.1
xarray: None
IPython: 5.1.0
sphinx: 1.3.1
patsy: 0.4.1
dateutil: 2.5.3
pytz: 2016.7
blosc: None
bottleneck: 1.1.0
tables: 3.2.2
numexpr: 2.6.1
matplotlib: 1.5.1
openpyxl: 2.4.0
xlrd: 1.0.0
xlwt: 1.1.2
xlsxwriter: 0.9.3
lxml: 3.6.4
bs4: 4.5.1
html5lib: None
httplib2: None
apiclient: None
sqlalchemy: 1.1.0
pymysql: None
psycopg2: None
jinja2: 2.8
boto: 2.42.0
pandas_datareader: None

Thanks for report!  It's not obvious to me what the expected behavior is if a fraction is smaller than 1 row.
Either of your suggestions (flooring at 1, adding a min_sample kwarg) seem reasonable - will let others weigh in.

@chris-b1 you ar right it is not obvious. However, what should be the result when sampling from one element if frac is less than 1? Should it be zero or one. I want to have a sample, so maybe one element at least should be returned. This could be nicely controlled with a min_sample keyword.
Additionally, this would implement sample x percent but at least y elements.
One thing that might be an issue here is that python rounds .5 to 0 instead of 1, in fact, that was the first thing i realized when trying to get counterexamples. By the way, an "inconsistency" the other way round appears in the following case:
import pandas as pd
import numpy as np

tmp = pd.Series(np.arange(6))
tmp.sample(frac=0.25)

1    1
0    0
dtype: int32

So here, we python rounds 1.5 to 2 and we get two values, instead of one? I'm not sure what is desired here

IMO rounding between 0-1 row should follow the same rule as for > 1 rows (which is just the python rounding rule of round(..) I think).
But a min_sample (or other name) for specifying a minimum sample size seems indeed reasonable.

Yes, it is just pythons rounding rule. However, the rounding rule between 0 and 1 row is not the same between 1 and 2 rows since round always rounds to the nearest even integer.
Personally, I'd prefer the min_sample approach

My two cents is that this behavior is working as it should. If the user cares about rounding in a particular way, they should calculate n exactly as they desire.

thanks for the reply. However, one example where the min_sample_size might be practical if you have a large number of groups and want to sample a certain fraction of each group but obtain at least one element. In this case, it would be convenient to have the min_sample keyword when you "apply" the sample function to the data frame (or groups of the dataframe).
But if such a behaviour is not desired, I'm okay with that and we could close this issue.


Test target not running on Xcode 6.1

SenTestingKit is deprecated and once converted to XCTest, the test are getting this error:
Unable to locate test bundle.

Seems to no longer be an issue in Xcode 6.1.1


Prettier support

Would be amazing to find a way to make prettier work within <style jsx> tags :)
https://twitter.com/Vjeux/status/870670634908475392

Issue to track:
https://github.com/prettier/prettier/issues/1948

It should be fairly easy to do I think. Probably the best way to get it done would be to contribute to Prettier. Another option would be create prettier-styled-jsx when support for plugins (#190) ships.

Basic support for styled-jsx was merged today with prettier/prettier#1984.
Next step will be to format template literals containing expressions. Any tricky test case that you can think of?

@pomber you can see the fixture from this PR https://github.com/zeit/styled-jsx/pull/227

Prettier ^1.5.0 formats styled-jsx but ignores our "external styles" because they are just exported strings / template literals eg.
export button = `
  button { color: red }
`

In styled-jsx we detect external styles by validating exported strings / template literals with CSSTree [relevant code]
@vjeux would you accept a PR to do the same in Prettier? Maybe the overhead is minimal.

I'm not comfortable with this option. The CSSTree spec is extremely lenient and many things that aren't CSS can parse as CSS.
I would encourage you to add a way to statically tag a template literal as being css. Something like
import { css } from 'styled';

export default css`
`

It's definitely more annoying and verbose but I believe it's going to be better for the ecosystem in general.

@vjeux fwiw I found CSSTree being rather strict and more close to the w3c validator than say PostCSS.
That said I agree with you that tagging the template or annotating the css string with a comment is the best way to go.

@rauchg @nkzawa let's keep this in mind and include the change in the next major release, whenever that will be.

Oh thanks for the mention, I was indeed talking about postcss. I've never used CSSTree

Fixed by #288

Doesn't seem to work by default within my project as of now...  see top
<style jsx>{`

            @import url('https://fonts.googleapis.com/css?family=Open+Sans:300,700i&display=swap');

            :global(body) {
              margin: 0;
              font-family: "Open Sans", -apple-system, BlinkMacSystemFont, Avenir Next, Avenir,
                Helvetica, sans-serif;
              font-weight: 300;

              background: url("${require('../public/img.jpg')}") no-repeat center center fixed;
    -webkit-background-size: cover;
    -moz-background-size: cover;
    -o-background-size: cover;
    background-size: cover;
            }
            h1, h2, h3, h4, h5, h6 {
              font-weight: 700;
              font-style: italic;
            }

            .page {
              display: flex;
              align-items: center;
              justify-content: center;
              min-height: 100vh;
            }
        .hero {
          max-width: 520px;
          margin: 4rem 1rem;
        }
        .title {
          margin: 0;
          width: 100%;
          line-height: 1.15;
          font-size: 48px;
          padding: 0.33rem;
        }
        .description {
          font-style: unset !important;
        }

        .row {
          max-width: 880px;
          margin: 80px auto 40px;
          display: flex;
          flex-direction: row;
          justify-content: space-around;
        }
        .card {
          padding: 18px 18px 24px;
          width: 220px;
          text-align: left;
          text-decoration: none;
          color: #434343;
          border: 1px solid #9b9b9b;
        }
        .card:hover {
          border-color: #067df7;
        }
        .card h3 {
          margin: 0;
          color: #067df7;
          font-size: 18px;
        }
        .card p {
          margin: 0;
          padding: 12px 0 0;
          font-size: 13px;
          color: #333;
        }
      `}</style>


Publish 8.1-20230309020000+0000

Publish 8.1-20230309020000+0000

@bot-gradle test and merge

I've triggered a build for you.


Re-export the C API in Rust bindings

Rascaline is using these to implement a custom Array.
Contributor (creator of pull-request) checklist

[ ] Tests updated (for new features and bugfixes)?
[ ] Documentation updated (for new features)?
[ ] Issue referenced (for PRs that solve an issue)?

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Documentation preview 📚: https://metatensor--549.org.readthedocs.build/en/549/

I tested this change manually by building rascaline against the local version of metatensor.

Codecov is being annoying again. I'll merge without it =)


Preserving a Fixed Table Height when filtering VueScrollingTable

Hey there,
I'm using your VueScrollingTable on a project to list tenants in a building. I've since implemented a filtering component to only show tenants that starts with the same character as the selected filter. As expected, displaying less rows within the table shrinks it to fit only the rendered rows.

Is there any way to give the VueScrollingTable a fixed/min-height and force it to maintain that height regardless of the number of components (i.e. if the filter returns an empty result, it should say something like "Sorry nothing to show yet...", if there are more then scroll)?

Hey Richard,
Thanks for the speedy reply, you details helped me solve the issue perfectly! Now I'm able to set a constant size regardless of which tab I'm viewing and regardless of the number of table entries.
In regards to using our project in a gallery, would it be simply an image of the page?
If that's that case I can clear it with our marketing team to make sure there aren't any issues and get back to you!


Reduce travis build logs

Set batch-mode in order to limit
logs size + don't display all download
lines. See
https://blog.sonatype.com/2009/01/maven-continuous-integration-best-practices/

This is required by FGA (with new tests, there are too many logs for travis).

Related to #577


WIP/DO-NOT-MERGE: Update Zeppelin package

make icons and health checks work in the DCOS UI

xref https://github.com/apache/spark/pull/10880

LGTM but the upstream process is quite involved, I guess we need more preparation (Spark Jira et al) to push the upstream. Asked @mgummelt on how to proceed here.

In an effort to make DCOS packages more accessible to users, Mesosphere will be decommissioning this repo in favor of https://github.com/mesosphere/universe
On Wednesday March 30th 2016 13:30 PDT (Wednesday March 30th 2016 20:30 UTC) the contents of this repo will be migrated to https://github.com/mesosphere/universe
In preparation for this move please update this PR to ensure that it can merge and is targeted at branch version-2.x. If this PR is obsolete please feel free to close it.
If this PR is not ready to merge prior to the above time, this PR will be closed and not migrated.
After this repo has been decommissioned all contributions for packages will still follow the same PR process just targeting https://github.com/mesosphere/universe instead of this repo.
In an effort to make DCOS packages more accessible to users, Mesosphere will be decommissioning this repo in favor of https://github.com/mesosphere/universe
On Wednesday March 30th 2016 13:30 PDT the contents of this repo will be migrated to https://github.com/mesosphere/universe
In preparation for this move please update this PR to ensure that it can merge and is targeted at branch version-2.x. If this PR is obsolete please feel free to close it.
If this PR is not ready to merge prior to the above time, this PR will be closed and not migrated.
After this repo has been decommissioned all contributions for packages will still follow the same PR process just targeting https://github.com/mesosphere/universe instead of this repo.

All packages currently defined in multiverse have been migrated to https://github.com/mesosphere/universe
Please re-submit a PR against https://github.com/mesosphere/universe if you believe this change should be included.


Error message "Something went wrong."

Like in #503 & #495 I sometimes get the Error message "Something went wrong.", while browsing through the Umami Dashboard & the Details page of a website. A few reloads with the button next to the time period selection fix the error messages, but not always.

Check the network tab of the developer tools to see what error is thrown.

I see these 500 errors

Where are you hosting? You'll have to check the logs. If hosting locally, you can run in dev mode and look at the logs.

I think I figured it out:
I am hosting Umami on Vercel and the database external.
Apparently the database has too many connections, but is only accessed by one program:

Error querying the database: Server error: `ERROR 42000 (1203): User ******** already has more than 'max_user_connections' active connections'

Is it possible, that Umami creates a new connection per request, or something like that?


Move JsonPayloadConfig in the right place

It should be there src/Framework/Bootloader/Http, but I'm not sure

@butschster Perhaps, a better place in src/Http/src/Config?
In this folder already stored config src/Http/src/Config/HttpConfig.php, which is used in bootloader src/Framework/Bootloader/Http/HttpBootloader.php and related to HTTP too.


Media Key Support?

Is there also Media Key support (planned)?
e.g., KEY_MEDIA_NEXT_TRACK , KEY_MEDIA_PLAY_PAUSE, KEY_MEDIA_VOLUME_UP ...
Best regards

Hi,
it requires different or updated report map descriptor. For example keyboard class or composite class could be extended.
Yes, that may be done eventually.

Do you have a rough idea of when you could bring media key support?

Well, this library is not very popular and now its not on top of my list to upgrade.
Recently ive been playing with USB host (esp-idf), but temporary it is also on standby.
All depends what you want to achieve, but it is not hard to do it. Start with this class and for example replace mouse:
https://github.com/chegewara/EspTinyUSB/blob/master/src/classes/hid/hidcomposite.cpp#L17-L20
here is example how it is done in tinyusb:
https://github.com/hathach/tinyusb/blob/master/examples/device/hid_composite/src/usb_descriptors.c#L74-L80

Thanks for your support. But I'm a rooky. Do you have an easy example how to send the Media Key Message with the "Lib" hidcomposite.cpp?

No, and hidcomposite.cpp is not ready to send media keys. You would need to update library/class code to do it.

Hi chegewara,
may you help me in another direction. I need in one ESP32 application Mouse, Keyboard and Media Key support.
I found the following libraries - but non off them supports all.

The base from 2. and 3. from T-vK: Only support mouse OR Keyboard+Media
Blackketter, based on T-vK: Mouse AND Keyboard support, but no Media Keys --> Fixed Mouse reconnection
Jakern, based on T-vK/Blackketter: Mouse+Keyboard+Media --> But problems with Mouse reconnection
I tried to combine the two libraries, see, in general it is working. But by changing Keyboard.write( KEY_MEDIA_VOLUME_UP ); or Keyboard.write( KEY_MEDIA_VOLUME_DOWN ); strage PC/Windows behaviour - seems to block timewise Win message system.

Do you have any idea. I seems, that all of the stuff before is based on your great experience, Best regards


Control over outbound socket creation / parameters

AKA Custom Dialers
dotnet/runtime#28721

Triage: .NET 5 implemented the callback: https://github.com/dotnet/runtime/issues/41949
The scenario has been met. Closing.


TLS.MinVersion entrypoint is not working properly in Traefik 1.7.26

Do you want to request a feature or report a bug?

Bug

What did you do?

What did you expect to see?
I have configured an entrypoint to use the  minimum TLS version 1.2. I expect to see that traefik will discard any request which is using TLS version lower than 1.2
What did you see instead?
I see that I can connect to the url while using HTTP1.1.
curl -i --tlsv1.1 https://****************/ --http1.1
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Content-Length: 1479
Content-Type: text/html; charset=UTF-8
Date: Mon, 07 Sep 2020 15:43:02 GMT
Etag: W/"5c7-173c8d0d0f8"
Last-Modified: Fri, 07 Aug 2020 12:06:35 GMT
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Dns-Prefetch-Control: off
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Xss-Protection: 1; mode=block

Output of traefik version: (What version of Traefik are you using?)

We are running traefik on Kubernetes and the cloud provider is AWS. Here is the deployment file of traefik
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "20"
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"traefik","namespace":"default"},"spec":{"replicas":1,"selector":{"matchLabels":{"app":"traefik"}},"template":{"metadata":{"labels":{"app":"traefik"}},"spec":{"containers":[{"args":["--api","--kubernetes","--entryPoints=Name:http Address::80","--entryPoints=Name:https Address::443 TLS:/run/secrets/traefik.cert,/run/secrets/traefik.key","--defaultentrypoints=http,https"],"image":"docker.cognigy.com:5000/traefik:1.7.24-alpine","name":"traefik","ports":[{"containerPort":80,"name":"http"},{"containerPort":443,"name":"https"}],"resources":{"limits":{"cpu":"2000m","memory":"200Mi"},"requests":{"cpu":"200m","memory":"70Mi"}},"volumeMounts":[{"mountPath":"/var/run/secrets/","name":"traefik"}]}],"imagePullSecrets":[{"name":"cognigy-registry-token-prod"}],"volumes":[{"name":"traefik","secret":{"items":[{"key":"tls.crt","path":"traefik.cert"},{"key":"tls.key","path":"traefik.key"}],"secretName":"cognigy-traefik"}}]}}}}
  creationTimestamp: "2020-07-27T07:47:51Z"
  generation: 20
  name: traefik
  namespace: default
  resourceVersion: "18706325"
  selfLink: /apis/apps/v1/namespaces/default/deployments/traefik
  uid: f800da16-ed0f-4181-a749-9e1e48cf17a2
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: traefik
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: traefik
    spec:
      containers:
      - args:
        - --api
        - --kubernetes
        - --entryPoints=Name:http Address::80
        - --entryPoints=Name:https Address::443 TLS:/run/secrets/traefik.cert,/run/secrets/traefik.key
        - --entryPoints=TLS.MinVersion:VersionTLS12
        - --entryPoints=TLS.CipherSuites:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
          TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
          TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
          TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
        - --defaultentrypoints=http,https
        - --metrics.prometheus=true
        - --logLevel=DEBUG
        image: traefik:v1.7.26-alpine
        imagePullPolicy: IfNotPresent
        name: traefik
        ports:
        - containerPort: 80
          name: http
          protocol: TCP
        - containerPort: 443
          name: https
          protocol: TCP
        resources:
          limits:
            cpu: "2"
            memory: 200Mi
          requests:
            cpu: 200m
            memory: 70Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/run/secrets/
          name: traefik
      dnsPolicy: ClusterFirst
      imagePullSecrets:
      - name: cognigy-registry-token-prod
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
      volumes:
      - name: traefik
        secret:
          defaultMode: 420
          items:
          - key: tls.crt
            path: traefik.cert
          - key: tls.key
            path: traefik.key
          secretName: cognigy-traefik
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2020-09-02T09:54:06Z"
    lastUpdateTime: "2020-09-02T09:54:06Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  - lastTransitionTime: "2020-07-27T08:04:22Z"
    lastUpdateTime: "2020-09-07T14:07:35Z"
    message: ReplicaSet "traefik-7fc6c996" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  observedGeneration: 20
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
(paste your output here)

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


User class does not include fields in parity with nhost-js

nhost-js has
export interface User {
    /** User's unique identifier (uuid) */
    id: string;
    /** The date-time when the user has been created */
    createdAt: string;
    /** User's display name */
    displayName: string;
    /** The URL to the user's profile picture */
    avatarUrl: string;
    /** The locale of the user, as a two-characters string
     * @example `'en'`
     */
    locale: string;
    /** User's email address */
    email?: string;
    /** Whether or not the user is anonymous */
    isAnonymous: boolean;
    /** The default role of the user
     * @example `'user'`
     */
    defaultRole: string;
    /** The roles assigned to the user
     * @example `['user', 'me']`
     */
    roles: string[];
    /** Additional attributes used for user information */
    metadata: Record<string, unknown>;
    /** Is `true` if the user email has not been verified */
    emailVerified: boolean;
    phoneNumber: string | null;
    phoneNumberVerified: boolean;
    activeMfaType: 'totp' | null;
}

while nhost-dart only have
class User {
  User({
    required this.id,
    required this.displayName,
    required this.locale,
    required this.createdAt,
    required this.isAnonymous,
    required this.defaultRole,
    required this.roles,
    this.metadata,
    this.email,
    this.avatarUrl,
  });

  final String id;
  final String? email;
  final String displayName;

  /// A [Uri] locating the user's avatar image, or `null` if none
  final Uri? avatarUrl;
  final String locale;
  final DateTime createdAt;

  final bool isAnonymous;
  final String defaultRole;
  final List<String> roles;
  final Map<String, Object?>? metadata;

  static User fromJson(dynamic json) {
    return User(
      id: json['id'] as String,
      email: json['email'] as String?,
      displayName: json['displayName'] as String,
      locale: json['locale'] as String,
      avatarUrl: json['avatarUrl'] == null
          ? null
          : Uri.parse(json['avatarUrl'] as String),
      createdAt: DateTime.parse(json['createdAt']),
      isAnonymous: json['isAnonymous'] as bool,
      defaultRole: json['defaultRole'] as String,
      roles: <String>[...json['roles']],
      metadata: json['metadata'] == null
          ? null
          : <String, Object?>{...json['metadata']},
    );
  }

  Map<String, dynamic> toJson() {
    return <String, dynamic>{
      'id': id,
      'email': email,
      'displayName': displayName,
      'avatarUrl': avatarUrl?.toString(),
      'locale': locale,
      'createdAt': createdAt.toIso8601String(),
      'isAnonymous': isAnonymous,
      'defaultRole': defaultRole,
      'metadata': metadata,
      'roles': roles,
    };
  }

  @override
  String toString() {
    return {
      'id': id,
      'displayName': displayName,
      'locale': locale,
      'createdAt': createdAt,
      'isAnonymous': isAnonymous,
      'defaultRole': defaultRole,
      'roles': roles,
      'metadata': metadata,
      'email': email,
      'avatarUrl': avatarUrl,
    }.toString();
  }
}

Reason why I pointed this out:
My use case is to make use of the emailVerified, phoneNumber and phoneNumberVerified. activeMfaType will also be useful in future implementations

@onehassan @dbarrosop
I'd like to clarify, does the NhostSession  for User already contain the missing fields I mentioned? (e.g emailVerified, phoneNumber and phoneNumberVerified) If so, I could probably create a PR for this

Did some debugging and signIn does indeed returns the missing fields
{"accessToken":"eyJhbGc......KI","accessTokenExpiresIn":2592000,"refreshToken":"9b5....6f8","refreshTokenId":"46550667-04ea-46f8-a91e-5f228b385784","user":{"avatarUrl":"http....=g","createdAt":"2024-07-13T06:13:52.606751Z","defaultRole":"user","displayName":"tyrone...mail.com","email":"tyro...mail.com","emailVerified":true,"id":"be0...e4d","isAnonymous":false,"locale":"en","metadata":null,"phoneNumber":"","phoneNumberVerified":false,"roles":["user","me"]}}

Will be working on a PR

Fixed by https://github.com/nhost/nhost-dart/pull/140

Thanks for the PR, for reference, this is how it should look like:
https://github.com/nhost/hasura-auth/blob/main/go/api/openapi.yaml#L504-L569
So your PR looks good, thanks again.

https://github.com/nhost/nhost-dart/pull/140 merged


Span activesupport 3.x AND 4.x

Add travis config for both and two different ruby versions.
@wmene @jmartin-sul

Coverage remained the same at 99.89% when pulling d53190c0e5f67dc18e7d410e184a71c506f07d7b on sul-dlss:development into 32888cb2145593f9534b741926324d6481748344 on jpstroop:development.

Coverage remained the same at 99.89% when pulling d53190c0e5f67dc18e7d410e184a71c506f07d7b on sul-dlss:development into 32888cb2145593f9534b741926324d6481748344 on jpstroop:development.

Build passed, now against 2 versions of ruby.  Not sure it is picking up on the gemfiles directive though... hrmmm.

Coverage remained the same at 99.89% when pulling 11a173cfe6998df061ed954c4549b620220b11bc on sul-dlss:development into 32888cb2145593f9534b741926324d6481748344 on jpstroop:development.

Ok, corrected and rebased.

Coverage remained the same at 99.89% when pulling c2ef5db152dccf0d22da44037f2991a7d54d87f0 on sul-dlss:development into 32888cb2145593f9534b741926324d6481748344 on jpstroop:development.

Coverage remained the same at 99.89% when pulling c2ef5db152dccf0d22da44037f2991a7d54d87f0 on sul-dlss:development into 32888cb2145593f9534b741926324d6481748344 on jpstroop:development.

Werd. I good, you OK?

Yep, please pull and publish at your convenience.

0.0.3: https://rubygems.org/gems/osullivan

My fault.  I should've used the >= operator


Gradient for tf.cholesky

It would be really nice to have a gradient operation for tf.cholesky similar to Theano's CholeskyGrad.
I'll be seeing if I can implement the gradient using tf.control_flow_ops.While following the suggestion provided here, but if someone with C++ experience can implement the gradient directly in C++, that'd be great.
Thanks!

control_flow_ops.While is not part of the public API (hence there is no documentation about it) because it is still not ready to use externally yet.

@yaroslavvb: Were you pondering linear algebra gradients?

Just curious, what is the use-case for differentiable Cholesky?

I'm interested in constructing a differentiable cost function for a Gaussian process (the log marginal likelihood) and wanted replace the matrix inversion with solving via Cholesky.

matrix_inverse was recently changed so it will try to use Cholesky if the matrix is symmetric, in the interest of speed. However for the log determinant, I agree that a Cholesky gradient would be nice to have.

This new paper may be of interest: Differentiation of the Cholesky decomposition

Myself and James Hensman have implemented the method from the reference paper by Iain murray in TensorFlow on a fork:
https://github.com/GPflow/tensorflow/blob/master/tensorflow/core/user_ops/chol_grad.cc
@vrv we're aware it isn't yet up to TensorFlow main repo standards but would you like to discuss getting it into the main repo.

Also we have a fair number of unit tests here:
https://github.com/GPflow/tensorflow/blob/master/tensorflow/python/kernel_tests/cholesky_grad_op_test.py

@rmlarsen Would you like to help?

The best way would be to make a pull request. That's the best way for us to see and comment on the changes. It's ok to mark the PR as [WIP] (see examples on our PR page).

Hi Alex,
Sorry for the delayed response. I'd be happy to review your code and help
getting it integrated into the TensorFlow core.
Rasmus
On Wed, Mar 2, 2016 at 5:45 AM, Alexander G. de G. Matthews <
<EMAIL_ADDRESS>wrote:

@rmlarsen https://github.com/rmlarsen Would you like to help?
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/367#issuecomment-191243120
.

OK thanks. I'll put in a pull request.

FYI: Alex's excellent code in PR 1465 was merged today, so you should be able to use cholesky with gradients now. We still need to add support for batch_cholesky, so I'm leaving the bug open for now.

@alexggmatthews said to post here when I had something to show and to tag @rmlarsen and @yaroslavvb - hi guys!
I've been working on making a CUDA version of Alex's code. I now have the following ops implemented in my fork:

get_diag (get_diag*)
tril (triangle*)
cholesky (gpu_cholesky*)
cholesky_grad (gpu_cholgrad*)

There is still a lot left to do, but the algorithms are all there and I believe they numerically match Alex's code. I will be adding python wrappers and tests over the coming days, as well as tidying up source files and trying to get it all to build with Bazel.
Meantime, I have a few questions (possibly to be discusses in a PR?):
streams
Is it correct to call standard CUDA kernels and operations on the op's stream by launching with context->eigen_device<Device>().stream()?
stream.ThenLaunch()
I think there is a way to launch kernels directly on a tensorflow stream - but there's not much information on TypedKernel or Kernel that I can find. Do I need to worry about this?
cusolver:
I use cusolver for the cholesky op. This isn't yet wrapped in Stream.h so I'm linking/calling it raw. This adds a dependency on linking cusolver into the framework, and maybe wrapping it as you guys have wrapped cublas.

@RuiShu (and others): are you aware that grad(logdet(A)) = transpose(inv(A))? Unless it's actually faster to compute the grad of the cholesky decomp (and to the other operations), then IMO it might make sense to use the cholesky decomp in getting the value of the logdet and to use the inverse-transpose form for the gradient?

tf.cholesky works only for symmetric pos def matrices? Any plans to support non-symmetric matrices?

@harpone It's been a while since I've checked up on this issue. Generally, it'd be nice to not compute the inverse explicitly. Since I was primarily interested in logdets within the context of gaussian processes, there are ways of getting around it (such as something that ultimately requires something like the cholesky decomp in the backwards pass as well :P)
In any case, I was under the impression that Alex's contribution (as well as his work in GPFlow in general) has effectively solved the issue.

Are there any plans to make the tf.matrix_determinant() GPU op? Or is it possible to implement it using existing GPU ops?

If the matrix is not positive definite, how to implement logdet(A) and its gradient without calculating det(A) explicit? (Because det(A) itself can overflow easily.)

@EverettYou as for the numerical value, you could now use s, u, v = tf.svd(M), where s is an array of the singular values (which are eigenvalues of M since M is square). Then log det(M) = log det(P S P^{-1}) = log det(S) = log(prod_i(s[i])) = sum_i log(s[i]), i.e. just take log of s and sum. Note that since M is not necessarily pos def, you'd actually need log abs det so just take the abs of s first. The gradient is the same, since log(-1) is a constant (imaginary number but a constant nevertheless).
I don't know about the status of the gradient... haven't thought about this in a while. You could define the gradient by RegisterGradient as grad(logdet(M)) = transpose(inv(M)), but as @RuiShu mentioned, it would be nice to avoid taking the inverse, at least if the matrix is big...

Thanks for your answer. That is very useful!
Everett You

On May 26, 2017, at 03:14, Heikki Arponen<EMAIL_ADDRESS>wrote:
@EverettYou https://github.com/everettyou as for the numerical value, you could now use s, u, v = tf.svd(M), where s is an array of the singular values (which are eigenvalues of M since M is square). Then log det(M) = log det(P S P^{-1}) = log det(S) = log(prod_i(s[i])) = sum_i log(s[i]), i.e. just take log of s and sum. Note that since M is not necessarily pos def, you'd actually need log abs det so just take the abs of s first. The gradient is the same, since log(-1) is a constant (imaginary number but a constant nevertheless).
I don't know about the status of the gradient... haven't thought about this in a while. You could define the gradient by RegisterGradient as grad(logdet(M)) = transpose(inv(M)), but as @RuiShu https://github.com/ruishu mentioned, it would be nice to avoid taking the inverse, at least if the matrix is big...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/tensorflow/tensorflow/issues/367#issuecomment-304210166, or mute the thread https://github.com/notifications/unsubscribe-auth/AEMNWk1b2s0wiP_9WyGYEdkQCghUm9JNks5r9nvTgaJpZM4GqubQ.


upload photo option added, and user details are now visible in user_dashboard

your Issue number

issue #189

https://user-images.githubusercontent.com/81517470/225711229-c24d8340-1ad1-4c12-8f05-b39829718140.mp4


OpenTelemetry Exporter integration with Resource API

Resource API need to be integrated with exporter code to allow customers to configure cloud extension data like roleName, roleInstance among others
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/resource/sdk.md#specifying-resource-information-via-an-environment-variable

On a related note, the attributes within a Resource should also be exported for each envelope in the Azure exporters.


Accomodate split cuda lib dir

Makes it a little easier to compile when cuda lib dir is split up as in nixos.

Hm. The commit history makes it look like major changes, but the net result is just an extra if between regular CUDA and ROCM. I think that's what you were suggesting? @dhiltgen I'm happy to adjust further as necessary.

If you rebase and pick up the changes that came in from #1966 then I think we can simplify this by adding some logic around here to be able discover where CUDA is installed. I'm, hoping this can simplify this change down to a couple lines of bash to get CUDA_LIB_DIR set properly if not passed in from the environment.

You're right, that's much cleaner.

I'm not sure about adding the default.nix file. Is CUDA installed in a standard location in nixos, is there some CLI tool we can run to find it, or perhaps a glob/find with some pattern?

I'm happy to remove the default.nix file if it is annoying. I included it mainly to provide an example that includes the minimum required environment to build. On NixOS there are no default locations for any packages, and the cudart folder doesn't seem to be exposed by any current existing environment variables.

Interesting that the cudart_static and cublas_static libs live in different locations...
I've got a pending PR #2007  that's going to transition us over to dynamic lib dependencies as a stepping stone to potentially decoupling the cuda libraries from the main payload to reduce the footprint on systems where we can "live off the land" if we detect compatible libs on the host.  I'm curious where those shared libraries wind up on NixOS, and if this gets simpler as a result perhaps?

Interesting that the cudart_static and cublas_static libs live in different locations...

You are far more charitable than I was when I found this out.

I've got a pending PR #2007 that's going to transition us over to dynamic lib dependencies as a stepping stone to potentially decoupling the cuda libraries from the main payload to reduce the footprint on systems where we can "live off the land" if we detect compatible libs on the host. I'm curious where those shared libraries wind up on NixOS, and if this gets simpler as a result perhaps?

It just might. It could pull the paths from LD_LIBRARY_PATH. I did some more digging and found out they're both already in CMAKE_LIBRARY_PATH as well.

I guess I'll keep this closed for now as there's not really a low impact way to integrate with this latest version.

@dhiltgen I think this is more in line with the current direction. The default.nix file allows building on NixOs with:
nix-shell --run 'go generate ./... && go build .'

Let's split this into 2 PRs.  The script updates look good to me and I'd approve that, but the default.nix needs more maintainers to weigh in.

Let's split this into 2 PRs. The script updates look good to me and I'd approve that, but the default.nix needs more maintainers to weigh in.

Sounds good to me. I'll just delete the default.nix for now and submit a second PR for it later.


chore: Make a dummy change to main() to trigger a compile, to test rust cache

Please don't actually merge this change.
I'll add commits to this to check whether and to what extent rust-cache successfully caches the built dependencies.
Without changing Cargo.toml or Cargo.lock, there should be an "exact match" for the cache key.
If I do change one of those, I want to see whether rust-cache preserves anything about the cache.
In any case, caches created for this Pull Request should not end up being usable on the main branch due to GitHub Actions isolation rules for caches.
https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache

Test 1 Results:
CI Test run: https://github.com/mitre/hipcheck/actions/runs/9896392105?pr=204

macos-latest: 4m 28s
ubuntu-latest: 4m 32s
windows-latest: 5m 29s

As expected, no cache is found as this is the very first use of the cache. rust-cache saved a cache for each OS.
They are 330 MB for Mac and Windows each, and 400 MB for Ubuntu.
GitHub sets a limit of 10GB for all caches in total, and will evict old caches to keep under the limit.
Look here for caches: https://github.com/mitre/hipcheck/actions/caches
Sample rust-cache logs on ubuntu run:
Run swatinem/rust-cache@v2
  with:
    key: ubuntu-latest
    prefix-key: v0-rust
    cache-targets: true
    cache-all-crates: false
    save-if: true
    cache-provider: github
  env:
    RUSTFLAGS: -Dwarnings
    CARGO_TERM_COLOR: always
    CARGO_HOME: /home/runner/.cargo
    CARGO_INCREMENTAL: 0
Cache Configuration
  Cache Provider:
      github
  Workspaces:
      /home/runner/work/hipcheck/hipcheck
  Cache Paths:
      /home/runner/.cargo
      /home/runner/work/hipcheck/hipcheck/target
  Restore Key:
      v0-rust-ubuntu-latest-test-a77bf122
  Cache Key:
      v0-rust-ubuntu-latest-test-a77bf122-5de08b75
  .. Prefix:
    - v0-rust-ubuntu-latest-test
  .. Environment considered:
    - Rust Version: 1.79.0 x86_64-unknown-linux-gnu (129f3b9964af4d4a709d1383930ade12dfe7c081)
    - CARGO_HOME
    - CARGO_INCREMENTAL
    - CARGO_TERM_COLOR
    - RUSTFLAGS
  .. Lockfiles considered:
    - /home/runner/work/hipcheck/hipcheck/.cargo/config.toml
    - /home/runner/work/hipcheck/hipcheck/Cargo.lock
    - /home/runner/work/hipcheck/hipcheck/hipcheck-macros/Cargo.toml
    - /home/runner/work/hipcheck/hipcheck/hipcheck/Cargo.toml
    - /home/runner/work/hipcheck/hipcheck/xtask/Cargo.toml

... Restoring cache ...
No cache found.

Post run:
... Cleaning /home/runner/work/hipcheck/hipcheck/target ...
... Cleaning cargo registry (cache-all-crates: false) ...
... Cleaning cargo/bin ...
... Cleaning cargo git cache ...
... Saving cache ...
/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /home/runner/work/hipcheck/hipcheck --files-from manifest.txt --use-compress-program zstdmt
Cache Size: ~402 MB (421330469 B)
Cache saved successfully

Test 2 Results:
CI Test run: https://github.com/mitre/hipcheck/actions/runs/9897170710?pr=204

macos-latest: 46s

ubuntu-latest: 50s

windows-latest: 1m 56s (116s)

macos-latest: 3m 42s (222s) saved, an 82% speedup

ubuntu-latest: 3m 42s (222s) saved, an 82% speedup

windows-latest: 3m 33s (213s) saved, a 64% speedup

It's exciting to see build times under a minute (except for Windows, which somehow took almost 2 minutes).
As expected, since the code change did not change the Cargo.toml or Cargo.lock, rust-cache created the exact same cache key for the workspace, and therefore got an exact match on the cache when restoring.
Since it was an exact match, rust-cache did not write any caches after the runs.
But GitHub did track that the caches were used, which resets the expiration timer on them (GitHub will delete caches that are unused for 7 days, and this is not configurable).
Sample rust-cache logs on ubuntu run:
... Restoring cache ...
Received 0 of 421330469 (0.0%), 0.0 MBs/sec
Received 79691776 of 421330469 (18.9%), 38.0 MBs/sec
Received 176160768 of 421330469 (41.8%), 55.9 MBs/sec
Received 281018368 of 421330469 (66.7%), 66.9 MBs/sec
Received 381681664 of 421330469 (90.6%), 72.7 MBs/sec
Cache Size: ~402 MB (421330469 B)
/usr/bin/tar -xf /home/runner/work/_temp/8fde0b25-3928-457e-9bdf-dac586f730ba/cache.tzst -P -C /home/runner/work/hipcheck/hipcheck --use-compress-program unzstd
Received 421330469 of 421330469 (100.0%), 66.9 MBs/sec
Cache restored successfully
Restored from cache key "v0-rust-ubuntu-latest-test-a77bf122-5de08b75" full match: true.

Post run:
Post job cleanup.
Cache up-to-date.

Test 3 is a build where the only change was to the description in Cargo.toml.
Test 3 Results:
CI Test run: https://github.com/mitre/hipcheck/actions/runs/9897734484?pr=204

macos-latest: 1m 21s (81s)
ubuntu-latest: 1m 2s (62s)
windows-latest: 3m 11s (191s)

Slowdown compared to exact match:

macos-latest: 35s slower
ubuntu-latest: 12s slower
windows-latest: 1m 15s (75s) slower

But these times are still way better than without the cache.
(These comments are based on rust-cache 2.7.3, released on Jan 14 2024)
Based on reading source code in rust-cache, I was under the impression that the entire target directory would be wiped in the case of a cache mismatch. But fortunately that's not true -- it actually just removes packages that are no longer dependencies. This confusion was due to code deleting all regular files in the target directory, but I hadn't seen that this does not include the profile directories under it. There is separate code for cleaning profile directories (like debug or release), which keeps the contents of build and deps that are still used.
Additionally, it is only when restoring from a non-exact match that rust-cache will delete files older than 1 week, based on mtime. It seems that this could result in needlessly deleting build artifacts that are still usable. Not all dependency crates should need to release new versions every week. The cleanup functionality isn't configurable at all in this version of rust-cache.
On the positive side, this seems like it could prevent the cache from growing endlessly in the case of an error in rust-cache's assumptions about which build artifacts are used.

@cstepanian this is great! Very happy to see these reductions in CI time. Do you think there are more experiments to run, or should we close this with its job now done?

Closing since the experimentation is done.


add support for kubernetes on Azure Stack

What this PR does / why we need it:
add support for Azure Stack
Special notes for your reviewer:
The deployment scripts are working now, there is one blocking issue here, it says "certificate signed by unknown authority" in the log, I am not sure whether there are work items for adding certs for azure stack in acs-engine,
ResourceManagerEndpoint:      "https://management.local.azurestack.external/"
Below are the error logs
E0627 01:46:01.053706    1810 kubelet.go:1318] Kubelet failed to get node info: failed to get external ID from cloud provider: compute.VirtualMachinesClient#Get: Failure sending request: StatusCode=0 -- Original Error: Get https://management.local.azurestack.external/subscriptions/a3368291-e427-41b0-b790-66b7be21017b/resourceGroups/andyazurestack3/providers/Microsoft.Compute/virtualMachines/k8s-master-13534591-0?api-version=2016-03-30: x509: certificate signed by unknown authority

This change is

@andyzhangx,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Is "https://management.local.azurestack.external/" signed by a public, trusted CA?
If not, is the public key for the CA installed on the nodes? If not, that would be the problem.
If you ARE placing the public key for the CA on the nodes, then it may be a matter of mounting in the right cert-containing directories in a couple places.

@andyzhangx - we will be closing this PR since there has been no response for over 2 weeks. Please feel free to reopen it.


better default playlist curation - should just be simple overviews of all philosophers

Also add audio books and BIOS for so channels
Feedback to capture more videos offer channels.

add to #261


[docs] Element descriptions missing on overview pages

Normally between the Overview heading and Status heading there would be an element description that comes from custom-elements-manifest/jsDoc.
## Overview

{{ tagName | getElementDescription }}

{% repoStatusList repoStatus=repoStatus %}

This getElementDescription filter appears to be currently not working.

Closed by #1920


Training setting

Hi, thanks for sharing the code.
I have a question about the training settings. To train the model, we need to specify the sg_task to one of three options [PR|CL|SG]. I am not familiar with tensorflow. Maybe I am wrong, but I am wondering why it is needed to specify the sg_task during training. As far as I know about the scene graph generation task, the three options are merely specified during evaluation, which means that the training should be the same to different settings, right?
thanks in advance for your reply.

The training is different for the three settings, the network is either provided ground truth detections as input (in PR for example) or needs to produce detections from scratch (for SG). This changes the network architecture slightly.


ament_lint: 0.7.4-2 in 'dashing/distribution.yaml' [bloom]

Increasing version of package(s) in repository ament_lint to 0.7.4-2:

upstream repository: https://github.com/ament/ament_lint.git
release repository: https://github.com/ros2-gbp/ament_lint-release.git
distro file: dashing/distribution.yaml
bloom version: 0.8.0
previous version for package: 0.7.4-1

Incorrect devel branch for the release track.


kodi.packages.invidious: init at 0.1.0+matrix.1

Description of changes

Someone asked for this: https://discourse.nixos.org/t/install-kodi-addons/20094
No harm in a backport either.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/install-kodi-addons/20094/4


Consecutive requests not working with $http configuration

After updating from 0.4.2 to 0.4.3 I'm having some issues with consecutive requests (the first request is still sent) when using a $http configured poller (I have not tried $resource or Restangular). Each consecutive request yields the following error:
angular.js:12783 Error: [$http:badreq] Http request configuration url must be a string.  Received: undefined
http://errors.angularjs.org/1.4.10/$http/badreq?p0=undefined
    at http://localhost:3000/bower_components/angular/angular.js:68:12
    at $http (http://localhost:3000/bower_components/angular/angular.js:10498:30)
    at Function.$http.(anonymous function) [as get] (http://localhost:3000/bower_components/angular/angular.js:10743:18)
    at b (http://localhost:3000/bower_components/angular-poller/angular-poller.min.js:2:1334)
    at http://localhost:3000/bower_components/angular/angular.js:15179:52
    at Scope.$eval (http://localhost:3000/bower_components/angular/angular.js:16359:28)
    at Scope.$digest (http://localhost:3000/bower_components/angular/angular.js:16175:31)
    at Scope.$apply (http://localhost:3000/bower_components/angular/angular.js:16467:24)
    at tick (http://localhost:3000/bower_components/angular/angular.js:11598:36)

My code:
poller.get('api/ladder', {
    delay: 5000
});

@mickelus : Good catch. It's fixed now in v0.4.4. Also added more unit tests. 😃


_InternalLinkedHashMap<dynamic, dynamic>' is not a subtype of type 'Map<String, dynamic>'

I resolved:
Instead of json['abc'] as Map<String, dynamic>, I used
Map<String, dynamic>.from(json['abc'])

I just ran into this same issue, and another safe option seems to be generating (json['field'] as Map).cast<String, dynamic>() in place of json['field'] as Map<String, dynamic>.
What are the downsides to an approach like this?

The cast call returns a wrapper around the original map which intercepts all calls. So you pay for indirection.
That should be the only downside.

@namndev , @Schoonology – guessing you guys are both using Flutter here?

@kevmoo Correct for me, at least. I apologize for not specifying.


Investigate unicode encode error

py -c 'd = pyquery.PyQuery(http://ebay.com);' 'd.html()' | py -l 'l[-10:]'Traceback (most recent call last):
File "/usr/local/bin/py", line 138, in
print(formatted)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xa0' in position 18746: ordinal not in range(128)

Don't close this! Is it solved?


Connection successful but no internet connection

Current setup is: debian 9 behind a dd-wrt router.
I managed to install and successfully connect to pivpn; I can access the local network but I can't ping any domain.
Any help will be much appreciated.
Thank you!

Ok, it seems that the problem was from my dd-wrt router; enabled "Forced DNS Redirection" and now it;s working fine.

I connect fine myself, but I have no data whatsoever. I will look to see if there is a setting similar in my router, but I fear it's too old.


LIBKML unavailable

I'm having trouble reading kml/kmz files on the dsap, it seems like the LIBKML driver is unavailable.
The issues are the same as described here: https://github.com/r-spatial/sf/issues/499.
Maybe we can add the driver in a future release.

please find release 1.4.0


Wechat Login Support with Authing.cn

That would be wonderful if we could support wechat login for auth-angular!
@leinue
See Also

https://authing.cn/

I will be supporting this week.

Glad to hear that, looking forward to the supporting from Authing.cn!

I haven't used angular for several years. How can I debug this program, is there any documentation?

I'm afraid that you have to read the source code as documentation.
And please have a look at https://github.com/chatie/app , it consumes the auth-angular module and you can use that as a example.

ok

I underestimated the complexity of integrating into auth-angular and estimated that there will be a little more time.

Yes, to use either authing.cn or auth0.com is a too complicated work for developers, even he is familiar with authing.cn or auth0.com. That's why I want to write this module ...


[Outlook] (npm) Add note about handling error

Fixes https://github.com/OfficeDev/office-js-docs-pr/issues/2114.

Docs Build status updates of commit ff9b4ee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/append-on-send.md
:white_check_mark:Succeeded
View

docs/outlook/autolaunch.md
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart.md
:white_check_mark:Succeeded
View

docs/tutorials/outlook-tutorial.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 67b9a11:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/append-on-send.md
:white_check_mark:Succeeded
View

docs/outlook/autolaunch.md
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart.md
:white_check_mark:Succeeded
View

docs/tutorials/outlook-tutorial.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Task] Update evaluation in retrieval model examples

Description
Currently, 05-Retrieval-Model.ipynb doesnt evaluate the model (model.evaluate).
I think we should extend the example by model.evaluate.

We should add a description, when using a validation dataset in the model.fit, that the validation scores depending on the validation batch size, as it uses negative samples.
We should use model.evaluation (once without item corpus and once with item corpus) and explaining the difference + explaining the performance.
We should add local prediction to the example. How to generate topk recommendations per user and save it to a file.

@sararb @gabrielspmoreira related to 2. -> how does the evaluation with itemcorpus work, when a user has multiple positive interactions? E.g. the users watched movies and watched ~5 movies. Do we evaluate each positive example against the full item corpus and treat everything negative? So we predict the full item corpus 5 times and average the metrics?

@rnyak Can you add your comments/requirements, as well?


Add Key Vault Object Alias Support  for file names

Fixes #24
[X] Add Key Vault Object Alias support for file name
[X] Update e2e tests to cover objectAlias
[X] Add Testing section in README to demonstrate how to run e2e tests inyour local environment
I added a test/bats/tests/local folder which includes duplicates of the secrets-store-inline-volume deployments, and secrets-provider-class deployments. I wanted to add support for contributors to test the Azure Key Vault Provider in their own local environment, however I also didn't want to overwrite and break any pipelines that have been set up.

Possibility to Update Testing to Support Both Pipelines and  a Local Environment

I think it would be nice to fold the test/bats/tests/local/azure_local.bats test into the original azure.bats tests to eliminate the need of having a local folder which includes the same test deployments and tests as the original setup.
@paulbouwer

@ritazh @aramase - this PR adds objectAlias functionality.
As part of this PR we wanted to run e2e tests locally to test the new feature.
@bdlb77 added a separate test/bats/tests/local folder for the local e2e tests, but we'd like to discuss with both of you about how we can merge this into the test/bats/tests folder so that the local and azure-pipelines specific tests can co-exist. Otherwise the tests have to be duplicated.
We also don't want to break the current azure-pipeline setup.


Update zero-allocation-hashing to 0.15

Updates net.openhft:zero-allocation-hashing from 0.10.1 to 0.15.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.10.1).
You might want to review and update them manually.
bin/deltag.sh

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "net.openhft", artifactId = "zero-allocation-hashing" } ]

labels: library-update, old-version-remains, commit-count:1

seems safe afaict from release notes, but since the dependency is visible downstream, if it ain't broke don't fix it? especially since it's a Java dependency; I'm usually more eager to upgrade Scala dependencies since they may need to be upgraded to get on newer Scala versions


Send email once sct_run_batch is done

Useful feature.

@cfhammill i think you've implemented that feature, right?

@cfhammill i think you've implemented that feature, right?

This feature was indeed implemented in:

https://github.com/spinalcordtoolbox/spinalcordtoolbox/pull/2732

However, it's usage isn't exactly clear? If you enter an email in -email-to, it will then prompt you for your password.
When I try using an account without 2FA, I get:
smtplib.SMTPAuthenticationError: (535, b'5.7.8 Username and Password not accepted. Learn more at\n
5.7.8  https://support.google.com/mail/?p=BadCredentials w26-20020a05620a0e9a00b006fa22f0494bsm3648209qkm.117 - gsmtp')

When I try using an account with 2FA, I get:
smtplib.SMTPAuthenticationError: (534, b'5.7.9 Application-specific password required. Learn more at\n
5.7.9  https://support.google.com/mail/?p=InvalidSecondFactor x21-20020a05620a0b5500b0070688f60025sm5341042qkg.76 - gsmtp')

If I try setting up an application-specific password, it works!

I've got no idea how this works for other email providers, though. :sweat:


”Boșorod” is listed in the drop-down menu

Description:
"Boșorod" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Boșorod" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Boșorod, HUNEDOARA".


Support wasm32 server by implementing a small change in leptos_reactive

Is your feature request related to a problem? Please describe.
I am trying to write an integration where SSR can be run in Cloudflare workers. This is a different backend then Actix, Axum, or Viz because Cloudflare workers are run in a very special environment - i.e. wasm32 target and limitations of the edge environment like no fs or threads. Also, at this point, the website can only be built and run with wrangler, meaning that cargo-leptos can't be used. Anyway, all that is to say is that this one is special and may require some changes in the existing codebase of leptos itself.
The code on my side is mostly complete, but just needs a few refactors and fixes. If you are interested, you can have a look:

https://github.com/9oelM/leptos-cf/blob/feat/ssr-crate/leptos-cf/src/lib.rs
https://github.com/9oelM/leptos-cf/blob/feat/ssr-crate/worker/src/lib.rs

The main problem that I am experiencing is that code in leptos_reactive is not designed with wasm32 server in mind, so this error is presented when I am trying to use the current code at leptos-cf:

Describe the solution you'd like
AFAIK we just need to change the first if statement in the code below to if #[cfg(target_arch = "wasm32")], because tokio::task::spawn_local in the third branch is simply not supported in wasm32 target environment:

And the solution is already seen and proven in https://github.com/leptos-rs/leptos/pull/1554/files#diff-a5ad10cf725eb78940bf4cc9772674f4896a3255da582bdefb37deda4ae55e94L79, where @seanaye was also trying to create a server that can be run in wasm32 although the objective of the PR was a lil bit different from what I am trying to do:

Describe alternatives you've considered
The only solution that is available seems to be the best (and probably the only) one to my knowledge.
Lastly, it'd be fascinating if leptos SSR could also support Cloudflare workers as a backend, but I think it's got more polishing work to do if it were to be merged into this repository. For now I would just love to have leptos_reactive to support wasm32. I will create a PR for this.

I just merged #1554 (actually I thought I merged it over the weekend but apparently I was letting the CI run on a fixed error and forgot about it!) which makes the changes you're asking for here. I don't think there's anything else needed but let me know if I'm wrong.

@seanaye @gbj great!! Thank you so much guys!!


Discovery not working - sometimes (W7)

I'm playing with a very simple bonjour.js
// browse for all http services
bonjour.find({ type: 'http' }, function (service) {
  console.log('Found service %s on %s:%d', service.name, service.referer.address, service.port)
})

Most of the time, all my http services are properly found (dns-sd -B confirm)
I stop stop Apple bonjour service net stop "Bonjour Service",  node bonjour.js still works , dns-sd is down.
I re-start Apple bonjour service net start "Bonjour Service", dns-sd -B works, node bonjour.js do NOT find anything anymore, until i reboot my computer...
Tested with node 4.4 & 5.1 (& nw) => same results.
Is there any "lost udp datagram" somewhere you think i should look for ?
Any idea on how to fix this ?
Thank you for your help !

Having what seems to be the same issue.

The problem is to do with the lack of caching in the implementation. The code relies on each packet containing all the records required to trigger service up/down events. However, real systems (e.g. restarting apache on an avahi-daemon-based host) sometimes send packets with partial information, expecting the TTLs from previous packets to be honoured, so that the logical content of all packets is combined to yield the active set of services.
To fix this bug, bonjour will have to sprout a TTL-honouring cache, and a means of combining raw RRs from that cache into service up/down events. (The current implementation only considers the RRs in a single packet at a time.) Cribbing from avahi might be a reasonable thing to do -- avahi-browse -aprk quite reliably does the right thing.


Flaky test: hubConnection using messagepack over LongPolling transport can be restarted

Seeing this javascript test flake out in the last 3 PR runs.

Happened again:
     - message: Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
    ...
  not ok 74 hubConnection using messagepack over LongPolling transport can be restarted
    ---
      - message: Expected Error: Server returned handshake error: Handshake was canceled. to be undefined.
        operator: toBe
        actual: Error: Server returned handshake error: Handshake was canceled.
      - message: Failed: Server returned handshake error: Handshake was canceled.

Error: Server returned handshake error: Handshake was canceled.

This indicates that the server canceled the handshake. It's possible the client simply failed to send the request, but it could also mean the server failed to send it in time. Also, as I mentioned in #1737 , this error breaks the pipe because of the (now fixed) corefx bug.

Are we passing the token into WriteAsync here? Lets just remove it and see if it works then.

I'll just do a pass yanking tokens our then.

I was wrong, it uses the token in ReadAsync, not WriteAsync.

Though the odd thing there is that if we sent "Handshake was canceled" it's because we timed out on that ReadAsync which means we've never processed a Handshak request.

I just saw this error and something occurred to me:
Failed   Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.HubConnectionCanSendAndReceiveGroupMessages(transportType: LongPolling, protocol: MessagePackHubProtocol { Name = "messagepack", SerializationContext = SerializationContext { CompatibilityOptions = SerializationCompatibilityOptions { ... }, DefaultCollectionTypes = DefaultConcreteTypeRepository { ... }, DefaultDateTimeConversionMethod = Timestamp, DictionarySerlaizationOptions = DictionarySerlaizationOptions { ... }, EnumSerializationMethod = ByName, ... }, TransferFormat = Binary, Version = 1 })
Error Message:
 System.TimeoutException : Operation in HubConnectionCanSendAndReceiveGroupMessages timed out at /Users/dfowler/dev/SignalR/test/Microsoft.AspNetCore.SignalR.Redis.Tests/RedisEndToEnd.cs:76
Stack Trace:
   at System.Threading.Tasks.TaskExtensions.<OrTimeout>d__2.MoveNext() in /Users/dfowler/dev/SignalR/test/Microsoft.AspNetCore.SignalR.Tests.Utils/TaskExtensions.cs:line 33
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.SignalR.Redis.Tests.RedisEndToEndTests.<HubConnectionCanSendAndReceiveGroupMessages>d__3.MoveNext() in /Users/dfowler/dev/SignalR/test/Microsoft.AspNetCore.SignalR.Redis.Tests/RedisEndToEnd.cs:line 76
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Standard Output Messages:
 | [2018-03-31T05:33:42] TestLifetime Information: Starting test HubConnectionCanSendAndReceiveGroupMessages_LongPolling_messagepack
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.Http.Connections.Client.Internal.LongPollingTransport Information: Starting transport. Transfer mode: Binary.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Information: HttpConnection Started.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.SignalR.Client.HubConnection Information: Using HubProtocol 'messagepack v1'.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.SignalR.Client.HubConnection Information: HubConnection started.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.Http.Connections.Client.Internal.LongPollingTransport Information: Starting transport. Transfer mode: Binary.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Information: HttpConnection Started.
 | [2018-03-31T05:33:42] Microsoft.AspNetCore.SignalR.Client.HubConnection Information: Using HubProtocol 'messagepack v1'.
 | [2018-03-31T05:33:47] TestLifetime Information: Finished test HubConnectionCanSendAndReceiveGroupMessages_LongPolling_messagepack in 5.005922s
 | [2018-03-31T05:33:47] Microsoft.AspNetCore.SignalR.Client.HubConnection Error: Server returned handshake error: Handshake was canceled.

We start waiting for the handshake when the poll is sent (first poll), that kicks off the HubConnectionHandler, https://github.com/aspnet/SignalR/blob/90aa48c09f79fe7c0f3c0e8aeb420816ec15c7f0/src/Microsoft.AspNetCore.Http.Connections/HttpConnectionDispatcher.cs#L226. We schedule that to execute on the thread pool which will set the countdown for the handshake and wait for data. The request hasn't returned yet BTW and time is ticking down. The client now has to send the handshake before the server cancels.
Maybe we can flush the response on the first request before waiting on the handshake request so the the client and send it as soon as possible. I think we should try to fix this for preview2.
/cc @muratg

Maybe it's also worth increasing the default timeout a bit. It's configurable too, right?

I see you already did that ;)

It's back:
https://travis-ci.org/aspnet/SignalR/jobs/364911071#L1234
https://travis-ci.org/aspnet/SignalR/jobs/364910777#L1422

I don’t think this is the same thing?

I'll create a new one https://github.com/aspnet/SignalR/issues/1944


Missing link on how-do-i-get-a-wallet

"Private Key"  link on /how-do-i-get-a-wallet Dogepedia article is missing, showing 404.
https://dogecoin.com/dogepedia/articles/how-do-i-get-a-wallet/

Thanks!


Add support for customizable authentication

The current Android implementation of HttpURLConnection has a bug that causes it to submit requests in an infinite loop when using an Authenticator and an HTTP 401 response is returned from an authenticated request (i.e. the caller provided a username/password, but they were invalid).
Further, the iOS NSURLSession class does not currently provide a way to provide authentication information with an initial request - only after a 401 response has already been received. This is not particularly efficient, since it requires an additional (and unnecessary) round trip to the server.
To work around both of these issues, a mechanism should be provided to authenticate requests before they are submitted. This could be done via an "authentication" interface or protocol, which would be invoked by a service proxy before the actual request is submitted. For example, the Java version might be defined as follows:
public interface Authentication {
    public void authenticate(NSURLConnection connection);
}

An implementation would be provided for basic authentication, but custom implementations should also be possible.

This has been implemented and documented, and the test applications have been updated to use the new basic authentication classes.


skip alert divs for endpoint descriptions

closes #13

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to Device::open the mouse

If I try to open /dev/input/mouse0 I get 'Error: Os { code: 25, kind: Uncategorized, message: "Inappropriate ioctl for device" }'.
I'm not sure if this is a bug or if I'm missing something, but I can't find anything online.

Never mind I got around it by opening the event that represents the mouse.


Define and document the process for releasing new versions of Cesium for Unreal

Similar to CesiumGS/cesium-native#112 but for Cesium for Unreal instead of cesium-native.

Added here: https://github.com/CesiumGS/cesium-unreal/blob/main/Documentation/release-process.md


refactor(corelib): using rust macro instead of erb

I think it's cool to using rust macro instead of using erb template to generator methods, because this is the builtin stuff in the language and thus does not need a "build" process to build shiika, so I just took a try, and it works. This is just a experiment so just int is implemented.
The generated codes should be like before, expected the return type is determined in runtime (not in macro expanding process), but I think rustc is smart enough to optmize it and does not actually introduce runtime cost maybe?
@yhara if you think this is ok, I'll try using the same mechanism to implement float methods.
close #124.

Seems this project have no CI, but $ cargo test is passed on my machine.

A little explaination on this change: $body should be an expr type and should be passed a closure to the macro, but currently rust does not allow specify lifetime on closurem, so I just make it as a funtion definition. In future if rust allow specify lifetime on closure, I think the codes can be reduced.

if you think this is ok, I'll try using the same mechanism to implement float methods.

@aisk Yes I once tried to write it with macro but I couldn't get it work. Please go ahead.

@yhara Hi I think this PR is finished now. And I did a little refactor that split the macro into two for arithmetic operator and comparison operator and thus there should be no any runtime cost and the generated codes should be exactly like before.

Merged! Confirmed CI passes. https://github.com/yhara/shiika/runs/1060504265


Improve dotnet purl while parsing .dll files

For dotnet-podcasts, we get 63.46% common components.
Archive.zip


Add excon readme

This adds documentation for the excon adapter, closing #236.

Thank you. I've added a mention of use_all.
I didn't setup two subsections, as those are quite short and that seemed superfluous. I'm happy to do so anyway though.

The test failure seems to be due to a flaky test.


No way to reasonably customize core and horizon configuration files

https://github.com/stellar/quickstart#customizing-configurations reads

It is recommended that you stop the container before editing any of these files, then restart the container after completing your customization.
NOTE: Be wary of editing these files. It is possible to break the services started within this container with a bad edit. It’s recommended that you learn about managing the operations of each of the services before customizing them, as you are taking responsibility for maintaining those services going forward.

We cannot deploy this way. We need a way to be able to reasonably configure every one of these files, but /start copy_defaults does not copy any of the critical files if their corresponding /etc dirs already exist (e.g. by providing a docker volume mount on the corresponding /etc directory). This makes it impossible to build custom configurations without a ton of work.
There should be a better way to merge the three following types of settings cleanly, and in the following order:

compile time defaults if no config file is specified (this appears to be a fatal error for core at least)
vendor provided configs
user configs

Many other programs provide various ways of doing this.
The ones that work the best are the ones where 2 and 3 are as minimal as possible, such that they only include the relevant differences from the default behavior.
The canonical way in many unix apps is by utilizing a config.d/ directory, which has a number of configuration files, possibly prefixed by an integer, e.g. 1- or 01- or 99- etc. such they can be parsed in a deterministic order.
Unfortunately, toml  (let alone yaml/json) isn't very conducive to this approach.
Environment variables, however, are ideal for this as they are simple k/v pairs.
The hack of using sed to create toml files (from, say, a template) is one approach, but that requires that every possible user configurable option has a corresponding env var to go with it, which is probably impractical.

In core's case, this might be done most easily by separating core configuration with quorum set configuration.

Instead of quickstart, we are using this for soroban directly
https://github.com/stellar/soroban-tools/blob/main/cmd/soroban-rpc/docker/Dockerfile

Hello, wanted to mention another alternative to consider in deployment, if it can leverage kubernetes, there are helm charts available, one for core, horizon, soroban-rpc here:
https://github.com/stellar/helm-charts/tree/main/charts
if kubernetes not an option, the manifests in those charts may still be good references for showing how to run the docker containers and the configurations.

Hello, wanted to mention another alternative to consider in deployment, if it can leverage kubernetes, there are helm charts available, one for core, horizon, soroban-rpc here:
https://github.com/stellar/helm-charts/tree/main/charts
if kubernetes not an option, the manifests in those charts may still be good references for showing how to run the docker containers and the configurations.

Absolutely; i used exactly that to do our own configs.

I don't think quickstart is suitable for production environments.

I don't think quickstart is suitable for production environments.

Yes, we do not recommend it for production environments, which is why issues like this tend to fall in priority and not get a lot of engagement. That said, I think we could do more to make that explicit/clear in the README here and in our API documentation. And I realize that some partners were explicitly pointed to quickstart for soroban-rpc, given the timelines and lack of other available options yet, so I apologize for that!

In #487 we removed the instructions for customizing the image. The instructions weren't consistent with what was actually possible. The image isn't maintained in such a way that customizing is really practical. Changes to the images routinely break any customization. Very likely custom setups would benefit from setups such as what is being used here: https://github.com/stellar/quickstart/issues/469#issuecomment-1652273367.
Please feel free to comment with alternatives if any occur. I'm going to close it since this aspect of the image is likely not to be improved.


Respect missing values in session's conflict resolver

When applying a changeset (e.g. for UPDATE), the conflict resolver’s item may include "missing" values since only changed columns are provided. Trying to read unexisting columns will cause the conflict resolver to panic.
The current code properly handles SqliteFailure related errors (e.g. ParameterOutOfRange) but will panic for operations performed on valid but at the same time missing values.
This small PR adds checks in ChangesetItem object that eliminate these issues and thus properly handle the Result<ValueRef> by throwing InvalidColumnIndex when a column is missing.

https://sqlite.org/session/sqlite3changeset_new.html

If the change is an UPDATE and does not include a new value for the requested column, *ppValue is set to NULL and SQLITE_OK returned.

So only sqlite3changeset_new should be affected, no ?

I believe so ...

I believe so ...

I mean sqlite3changeset_old and sqlite3changeset_conflict should not be affected. But in your PR they are !

A precaution .is_null check should be there anyway.

I checked again SQLite source code.
And sqlite3changeset_conflict cannot return a null value.
But sqlite3changeset_old can:
https://github.com/sqlite/sqlite/blob/99ace8263426ee9001d3994e6a8275d4fd8b8fc3/ext/session/sqlite3session.c#L3513-L3516

Or, if that particular value is not included in the record (because the change is an UPDATE and the field was not modified and is not a PK column), set *ppValue to NULL.

Sorry for the delay...


Copy editing and UART clarification.

Description

Related Issue:
Pre-commit steps

[ ] Tested on QEMU and real HW Rasperry Pi.

Not needed if it is just a README change or similar.

[x] Ran ./contributor_setup.sh followed by ./devtool ready_for_publish

You'll need Ruby with Bundler and NPM installed locally.
If no Rust-related files were changed, ./devtool ready_for_publish_no_rust can be used instead (faster).
This step is optional, but much appreciated if done.

Thanks for your contribution!


fix(#165): nested query resolvers

This adds most of the changes that were merged recently, but what was the fix for nested queries?

https://github.com/paritytech/Nomidot/pull/168/files#diff-09b77f4cdfa212a035a21a8eef16bbb6

https://www.prisma.io/tutorials/a-guide-to-common-resolver-patterns-ct08/

i'm not done but that's the working fix for total issuances at least.

ah yeah, understood, it'll be a little error prone to have to add that all! I've quite a lot of nested stuff.

yeah...sigh, it is what it is 🗻

no that's all you need to do. I would suggest the common troubleshooting steps though like clear db, redeploy model, re-get schema

https://recordit.co/KyX2HWiT7w/gif/


KYLIN-4193 More user-friendly page for loading streaming tables

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 5261

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.003%) to 28.052%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server-base/src/main/java/org/apache/kylin/rest/controller/TableController.java
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

core-dictionary/src/main/java/org/apache/kylin/dict/lookup/cache/RocksDBLookupTable.java
1
81.08%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
2
68.46%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
5
77.81%

Totals

Change from base Build 5260:
-0.003%

Covered Lines:
23865

Relevant Lines:
85073

💛  - Coveralls


implemented relation for geo_shape query

Fixes https://github.com/ongr-io/ElasticsearchDSL/issues/220

The base should be 5.0 and not the master. Can you please rebase your PR?

@saimaz done

Thank you. There is still a small style issue from code sniffer. Could you please fix that one as well?
https://travis-ci.org/ongr-io/ElasticsearchDSL/jobs/292059504#L782

@saimaz and done 👍
thank you

Hello @saimaz, any news for this PR?

This PR breaks BC. I'm sorry but we cannot change function arguments by inserting in the middle something.

@saimaz I managed to keep BC and added a deprecation notice: https://github.com/ongr-io/ElasticsearchDSL/pull/240/commits/ce92a3d4f9ceb918aa344b29f3e55c9c5f045576

Trigger deprecation is ok inside the function. What I'm saying is that when you introduce $relation as the third argument instead parameters is not ok. It might be more acceptable if it would be the last argument with default value. What about if you could define relation inside the $parameters array?

$parameters is optional and should be the last parameter - because it is - everywhere elase. BC is kept because $parameters is being overwritten by $relation if  $relation is an array.

Oh, I see that there is still a Problem that $relation isn't set after.