Cant find server ingame

Hi there,
I have PUBLIC=1 set but none of my friends are able to see the server ingame or steam. They can however add the server by ip from steam and ingame but not by name. Is it because i have spaces in the server name?

Nada this is a limitation on Valheims server list side. They limit the amount of servers visible, checkout the discussion on the subject here: https://github.com/mbround18/valheim-docker/discussions/51


Compiling fails

When I try to compile the file I get error telling me that I am missing .NET Framework version 4.5.2! I have already installed the framework it needed. Some help please?

Pleases follow these instructions: https://github.com/quasar/QuasarRAT#compiling

Not sure what I am doing wrong, but even following the instructions I get error compiling

Can you copy and paste the exact error message here?

It's not a .NET Core project. Use Visual Studio 2019 to compile it.


publish should propagate person-tags to POSSE copies

When you use Bridgy Publish to POSSE a photo post, it should read the person-tags from the original post, and propagate them to the POSSE copy (e.g. to Facebook or Twitter).
Original question/request: http://indiewebcamp.com/irc/2015-09-01/line/1441139069479
See also:
http://indiewebcamp.com/person-tag
This could be implemented in at least a couple of steps/iterations.
Phase 1: only use person-tag URLs of silo profiles that are directly indicated in the h-cards of the person-tags on the original photo post. E.g. a person-tag h-card could have multiple u-urls on it, and if one of them happens to match the silo domain, use it as the identity to person-tag on the POSSE post! (I'll add an example of how a person-tag publisher could do this to the indiewebcamp wiki to hopefully make it more concrete).
Phase 2: look up the person-tag's silo profile equivalent via rel=me identity lookup on their website. This would require Bridgy to retrieve the first u-url of the person-tag h-card, parse it for rel=me links (i.e. use a microformat2 parser), use the first one of those rel=me links that happens to match the silo domain as the identity to person-tag on the POSSE post! This could require Bridgy to do one additional HTTP(S) request per person-tag on a post which thus depends on the number of people in a photo.

thanks for all the details! agreed, this would definitely be fun to have.

updated title since we should ideally do this for all silo person tags, not just on posts published by bridgy.

oh wait sorry, i misread. this is the other direction. reverting that change.

slightly modified since afaik it's not technically photo-specific: you can person-tag arbitrary FB/twitter posts, with or without a photo.

agreed, more than just photos, photos just happen to be key (driving) use-case :)
Also, extended person-tag markup example added as promised: http://indiewebcamp.com/person-tag#With_other_profiles
Inline for your convenience:

  Ben Roberts
  (t,
   f)

turns out this a dupe of #318, but it has useful details, so i'm closing #318 instead.

And on the backfeed side: #488

current silo support:

Twitter: no. they're called photo or people tags. nothing in the uploading media or statuses/update docs, doc searches, or forum searches or posts.
Facebook: TODO
Instagram: no, since the API is mostly read only. you can't post pictures or tags.
Google+: no, since the API is read only.

facebook is done! tested just now and it works. silo SWAT0 here we come!

flick is done now too, thanks @kylewm!
tentatively closing this since the other three silos aren't possible. if anyone badly wants this for the other silos and really wants to track it in case they add support in the future, feel free to reopen.

Agreed with closure as completion of what's possible today. Other silos should be separate issues with proposals that are either actionable today or fully "wish list" awaiting something from the silo.

Looks like this may have broken recently in Bridgy Publish photos + person-tags to Flickr at least.
This post: http://tantek.com/2016/018/t4/w3cab-meeting-hawaii (has a bunch of person-tags)
Bridgy Publish POSSE to Facebook copy: https://www.facebook.com/photo.php?fbid=10102083967065093
Note that none of the person-tags (including my tagging myself) made it to the POSSE copy on Facebook.
All of the person-tags on that post (including of me) were added afterwards by Coralie (as you can see by hovering over the person-tags and looking the top left of the resulting pop-up where it says in small white text "Tagged by Coralie Mercier".
Any idea what broke? Re-open this?

For reference, we originally noticed that person tags seemed to work when you use the person's numeric ID as their URL in http://tantek.com/2015/350/t2/seasons-greetings-homebrew-website-club where it successfully tagged Marc Canter, even though he has never logged in to Bridgy. But even if that was a fluke, we still would've expected Tantek's person tag of himself to make it through.

I mentioned on IRC that person tags used to not work without a location ("You cannot specify this field without also specifying a place.", though the same caveat does not exist on the photos page) and I was surprised when they started working. Maybe Facebook fixed the "bug" that was letting us do it temporarily.

here's the publish log.
from IRC:

snarfed looking at the log, this is what we sent to facebook:
snarfed url=https://scontent-sjc2-1.cdninstagram.com/hphotos-xtf1/t51.2885-15/e35/12407429_887813537998827_121176936_n.jpg&message=One week ago, @W3CAB meeting in #Hawaii. I blame @Nov_Project for the #straightface reflex. #latergram #nofilter\n\n(Originally published at: http://tantek.com/2016/018/t4/w3cab-meeting-hawaii)&tags=[{"tag_uid": "100000802747500"}, {"tag_uid": "735170173"}, {"tag_uid": "214611"}, {"tag_uid": "538464812"}, {"tag_uid": "692216758"}]
snarfed so that included five person tags
snarfed so evidently FB rejected them all?
snarfed (we can load those user ids' profiles to confirm that they're the right people)
kylewm well 214611 is definitely tantek

the tags param format with url-encoded JSON seems odd, but evidently it's right. e.g. this older FB publish with successful person tags used the same format:
url=https://i1.wp.com/snarfed.org/w/wp-content/uploads/2015/11/wpid-wp-1447899561388.jpg?w=696
  &message=Celebrating Homebrew Website Club\xe2\x80\x99s 2nd anniversary....
  &tags=[{"tag_uid": "36802236"}, {"tag_uid": "214611"}]

the FB API call is a POST to /USERID/photos, and its docs confirm this format. StackOverflow too.)
plus, we got a 200 from the API request, and FB usually returns non-2xx with error details if we give it a bad parameter; it doesn't usually silently ignore.

tantek's access token includes the publish_actions permission, which should be enough.

i don't have any new leads on this, and i haven't found any other recent person-tagged facebook publish attempts to compare against. :/ @tantek, definitely let us know if you end up trying again!

@tantek retried and person tags went through again, surprisingly even more than we thought. details:
https://github.com/snarfed/bridgy/issues/568#issuecomment-174248236
we still don't understand why tags didn't work the last time, but it's looking like our code is working naively at least, and Facebook's tagging API is either unpredictable or more complicated than we thought.
so, I'm tentatively (re)closing this. we can keep collecting data points on the complexities in #568.


Fix support for comparing key columns of different names (via the Python API)

Describe the bug
When comparing two TableSegment with different key columns, the differ fails with an error:
    426         for c in table1._relevant_columns:
    427             if c not in table1._schema:
--> 428                 raise ValueError(f"Column '{c}' not found in schema for table {table1}")
    429             if c not in table2._schema:
    430                 raise ValueError(f"Column '{c}' not found in schema for table {table2}")

Fixed.


A11y: Tooltip does not show for Share button on keyboard focus/activation

Describe the task
When you hover over the "Share" button with the mouse, a tooltip appears that tells the user they can copy the link. After clicking on the button, a tooltip tells the user that the action was successful. These tooltips should also be visible on keyboard focus.
Acceptance Criteria

[ ] Open a property page
[ ] TAB over to the "Share" button.
[ ] On keyboard focus, the "Copy link" tooltip should be visible.
[ ] Press ENTER to activate the button.
[ ] The "Link copied" tooltip should be visible.

Additional context

Possibly helpful: https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible and https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-within

Assigned!


how can i get the map.yml

Hi，Your video tutorials work really well，I have completed the basic environment configuration
But I can't find this file in the video.Can you tell where to get it from?

I get it


feat(django): support ignored endpoints

:tada: This PR is included in version 1.36.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use refs on Input so that we can focus the next text input

Hi, I tried your components today and I saw that we couldn't pass refs to the Input, so that we could focus the next element when clicking on the 'Enter'/'Next' button on the keyboard which is pretty much annoying. In fact, when we pass a ref to an Input, we get this error message:
Warning: Stateless function components cannot be given refs. Attempts to access this ref will fail.

Here is the code:
<Input onSubmitEditing={ (event) => {
    this.refs.PassInput.focus();
  }
}>
<Input ref='PassInput'>

And when we press enter, we get:
Cannot read property 'focus' of null

Can this library works with refs ? Or have you any idea on how could I focus the next input when clicking on 'Next' on my keyboard ?
Thanks for this wonderful library by the way !

I tried it, with:
constructor(props) {
  super(props);
  this.on = this.on.bind(this);
}

on(event: string, ref: string) {
  this.refs[ref][event]();
}

render() {
  <View>
    <Input onSubmitEditing={() => {this.on("focus", "password")} } />
    <Input ref='password' />
  </View>
}

and I still get the warning and the error when I press enter in the first FormInput. Here is a file to reproduce this behavior.


Picker data object

Pull Request Template Form
Description
Import simpler date picker component, which is now connected to Create-invoice-data object. Upon click "generate" two new fields are included: selectedDate AND invoiceDueDate.
Swapped out previous date picker which was not able to connect to the main data object.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Change status
[ ] Complete, tested, ready to review and merge
[ x] Complete, but not tested (may need new tests)
[ ] Incomplete / work in progress, PR is for discussion / feedback
#Checklist:
[ X] My code follows the style guidelines of this project
[ X] I have performed a self-review of my own code
[ X] My code has been reviewed by at least one peer
[ X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

I like what you did here! Check out the state though, we need it to return in the format of 12-12-2019, instead of Thur Mar 12 2019 (Time Zone)


Webhook doesn't work on prod environment

I installed this plugin and tested to work on our dev and test environments, but not on prod.
We are using Pantheon for deployment and works great for us so far.
Pantheon creates a platform domain for all our environments, i.e.
https://dev-gofenam-marketplace-salone.pantheonsite.io/
https://test-gofenam-marketplace-salone.pantheonsite.io/
https://live-gofenam-marketplace-salone.pantheonsite.io/

Generated webhook on the different  environments are:
https://dev-gofenam-marketplace-salone.pantheonsite.io/wc-api/Flw_WC_Payment_Webhook/
https://test-gofenam-marketplace-salone.pantheonsite.io/wc-api/Flw_WC_Payment_Webhook/
https://live-gofenam-marketplace-salone.pantheonsite.io/wc-api/Flw_WC_Payment_Webhook/

However, redirecting from a successful payment(sandbox) in prod(www.gofenam.com) shows the following:

“There has been a critical error on your website. Please check your site admin email inbox for instructions.
Learn more about debugging in WordPress.”

Webhook URL on Flutterwave Dashboard:
https://live-gofenam-marketplace-salone.pantheonsite.io/wc-api/Flw_WC_Payment_Webhook/
We also tried using https://www.gofenam.com/wc-api/Flw_WC_Payment_Webhook/ but doesn’t resolve the issue. Anything wrong we are doing?
Thanks in advance.

Hi @ernestkamara  the solution to this issue is to simply check the disable logging option on the rave woo-commerce setting page and the error should disappear.
image reference - https://www.screencast.com/t/1i2W3c2PG


Config to set default gamerules?

It's annoying to have to change the gamerules of every single new world I make. Would be great if you could add config where we can set our preferred default gamerules, so we don't have to change the gamerules manually every time.

Smart. I’ll look into it! 😁


RAM and VRAM usage

some addons are beginning to get to a point where they cannot be played by some people because of vram usage.
we may have to finally start looking into this.
particularly, for RSS

check heightmap texture usage - how does 100 mb cause multiple gb of ram/vram usage?
can we Destroy base game textures/meshes to free of memory? can we do this in a way that doesnt mess up details?
can we upload textures/meshes to be GPU-only? can we do this in a way that doesnt break things that edit the texture on the CPU, like invert? this wouldnt save VRAM but it would save RAM

Could implement a build pattern that takes closures to apply to a texture and only actually performs said closures on a Finalize method or smth

Adding on to what Idiot said. Say you create a NHTexture object, then on that you call a LoadFile method, Tint method, Invert method, etc. Then at the end when you try to access the actual texture from it, it will try to look up that image in the file cache and if its not there only then will it load the file and apply the effects to it. This class could also be in charge of deleting the intermediate textures and just keeping the final texture.

Moving all of Outer Wilds to utilize RAM and VRAM entirely would significantly enhance performance and alleviate existing issues. By leveraging the full potential of these resources, the game's data and assets could be accessed and processed more efficiently, resulting in faster loading times, smoother gameplay, and reduced latency. The decreased memory capacity and bandwidth offered by RAM and VRAM would allow for seamless rendering of complex environments, intricate physics simulations, and detailed textures, resulting in a more immersive and visually stunning experience. This optimization would not only address performance concerns but also unlock new possibilities for the game's mechanics, enabling NH mod creators to push the boundaries of exploration and interactivity even further.

Moving all of Outer Wilds to utilize RAM and VRAM entirely would significantly enhance performance and alleviate existing issues. By leveraging the full potential of these resources, the game's data and assets could be accessed and processed more efficiently, resulting in faster loading times, smoother gameplay, and reduced latency. The decreased memory capacity and bandwidth offered by RAM and VRAM would allow for seamless rendering of complex environments, intricate physics simulations, and detailed textures, resulting in a more immersive and visually stunning experience. This optimization would not only address performance concerns but also unlock new possibilities for the game's mechanics, enabling NH mod creators to push the boundaries of exploration and interactivity even further.

big brain

turtle is banned now

turns out that texture duplication isnt actually that big of an issue, i think. need to test texture cache misses and hits to see if the cache is actually important etc.
i think the biggest deal will be just legit doing everything on the GPU and then only keeping textures on the CPU is absolutely needed (like heightmaps). this will be very painful.
could use command buffers to make a single draw wtv idk anything.
also compute shaders this will suck.
testing will kill me

clearly the best solution as addon dev is just do everything in unity since it seems to actually compress guy and load faster and just be better in general

Just use unity


TS-3650: Track configuration variable source.

A config set via traffic_line gets added to records.config as well, so the source of the config changes after a TS restart. Depending on how that info is used, the behavior may be affected after a restart. Note that the config file doesn't get updated when set via a plugin API, so, this looks very inconsistent and unreliable to me and may result in more bugs.

I don't have any particular thoughts on this, other than if we do this, we also add an API to query into this "source" of a particular config. E.g. TSMgmtSourceGet(). I'd be curious as to what @jpeach thinks about this, since he's knee deep in all this lib records stuff.

The REC_SRC constants scan poorly, I think I'd prefer REC_SOURCE. REC_SRC_NONE should be called REC_SOURCE_NULL to be consistent with other naming. There's some semantic confusion about what REC_SRC_DEFAULT means. When traffic_manager sets variables, I don't think they should be considered defaults.
I am sympathetic to @sudheerv's concerns about how useful this is. The distinction between "hard-coded default" and "everything else" is clear, but this change is attempting to track various nuances that are much murkier.
Does DiagsConfig::RegisterDiagConfig really have to register everything? I expect that that superfluous now?

The chat concensus seemed to be to change this to NULL, DEFAULT, EXPLICIT, ENV. I'll change "SRC" to "SOURCE" as well - I was tempted to have "RECS" which would be more consistent with the other REC values but that seemed even worse scanning.

Yes, I had the same conflict about RECS ;)

I don't think there was a consensus yet (at least, not from my side). AFAIK, my question above on persisting the source as traffic_line was not addressed and without making that information consistent, I am -1 on this PR.

There's no way to know whether a metric was set by traffic_line. The best you can do is to say whether a metric was set by a specific API, but that's complex and low value IMHO, and as you pointed out above, that information is lost when the configuration is persisted.


Jumping when leaning against a wall prevents the character from jumping up

This happens when you're next to a wall, moving towards the wall and jumping: the character enters wall state instantly, stopping the jump

I will work on that fix.


fix: Dispatch all emsg boxes, even if they are ID3

The 'metadata' event was introduced in v4.3, and ID3 metadata from 'emsg' boxes dispatched through that event was no longer dispatched through the more general 'emsg' events.
Now we will no longer exclude ID3 emsg boxes from the more general 'emsg' event.  This restores compatibility with Shaka v4.2.

I updated the PR description after researching and determining that we only broke this in v4.3, so no other release branch is affected.


Expected n_neighbors <= n_samples,  but n_samples = 1, n_neighbors = 2

Hi Guy
I try to run your code and I got an error
Traceback (most recent call last):
File "face_recognition_knn.py", line 223, in
predictions = predict(full_file_path, model_path="trained_knn_model.clf")
File "face_recognition_knn.py", line 153, in predict
closest_distances = knn_clf.kneighbors(faces_encodings, n_neighbors=2) # return the closest distances of a current point to other neighbors
File "/usr/local/lib/python3.7/site-packages/sklearn/neighbors/base.py", line 416, in kneighbors
(train_size, n_neighbors)
ValueError: Expected n_neighbors <= n_samples,  but n_samples = 1, n_neighbors = 2
what should I do

As stated by the error, the number of samples is only 1, but the number of neighbors is 2. Your model only have 1 class trained by KNN. You better check your dataset.
My suggestions: Do some preprocessing with the data. For example, grayscale.


This issue occurs when only Valkyrien Skies and addons are installed and no other mods

[X] I have tested this issue and it occurs when no other mods are installed

Minecraft Version
1.20
Eureka version
1201-1.5.1-beta.3
VS2 version
1.5.1-beta.3
Mod Loader
Fabric
Issue description
Hi, I am Muzaffer and I have a weird issue with the ships that I build. When I assemble my ship one of the 6 sides of the entity (north, south, east, west, up or down) becomes invisible. Not a great issue but it's really annoying to see through your ship. I am using modpack called Prominence Hasturian Era 1.20.1 but even I tried without it, result is same. Could you find a solution for me pls?
Thank you
Issue reproduction
I don't know why it's happening but it just happens every time and a side becomes invisible randomly.
Logs
No response

Please do at least minimal research before posting issues, even just googling the issue. If you had done that, you would have found that the solution is disabling block face culling in your performance settings.

Yeah, no. Disabling that just turns the entire ship invisible instead of just some block faces for me.

It's only after tinkering with block faces, as you mentioned, that i found out you need to also refresh or reload your build, or wait a few and it should come back.


🐛 Default media query to px if breakpoint value is unitless

Fix #248
The PR restores createMediaQuery behaviour to leverage px helper to supply default units as px when breakpoint value is unitless.

I just pulled this out of the source from v2 latest and dropped it in the v3 code. Let me know if you removed this for a specific reason and were intending to solve another way.

var Benchmark = require('benchmark');
// var Fns = require('../src/index');

const num = n => typeof n === 'number' && !isNaN(n)
const px = n => num(n) ? n + 'px' : n
const createMediaQuery = n => `@media screen and (min-width: ${px(n)})`
const createMediaQueryPrev = n => `@media screen and (min-width: ${n})`

const suite = new Benchmark.Suite;

// add tests
suite.add('createMediaQuery', function() {
  createMediaQuery(680);
  // createMediaQuery('680');
  createMediaQuery('680px');
})
.add('createMediaQueryPrev', function() {
  createMediaQueryPrev(680);
  // createMediaQueryPrev('680');
  // createMediaQueryPrev('680px');
})
// add listeners
.on('cycle', function(event) {
  console.log(String(event.target));
})
.on('complete', function() {
  console.log('Fastest is ' + this.filter('fastest').map('name'));
})
// run async
.run({ 'async': true });

👇
➜  styled-system git:(bm-fix-248-breakpoint-units) ✗ node ./scripts/benchmark.js
createMediaQuery x 15,377,376 ops/sec ±1.26% (82 runs sampled)
createMediaQueryPrev x 54,337,096 ops/sec ±0.63% (88 runs sampled)
Fastest is createMediaQueryPrev
➜  styled-system git:(bm-fix-248-breakpoint-units) ✗ node ./scripts/benchmark.js
createMediaQuery x 27,411,604 ops/sec ±0.94% (81 runs sampled)
createMediaQueryPrev x 55,912,352 ops/sec ±0.37% (84 runs sampled)
Fastest is createMediaQueryPrev
➜  styled-system git:(bm-fix-248-breakpoint-units) ✗ node ./scripts/benchmark.js
createMediaQuery x 60,470,792 ops/sec ±1.22% (83 runs sampled)
createMediaQueryPrev x 602,038,440 ops/sec ±0.39% (86 runs sampled)
Fastest is createMediaQueryPrev

It's certainly slower when it has to check the type and add the suffix, but also resolves the linked issue.
Alternatively, we could simply update the theming docs to be explicit that the breakpoint values should carry a unit now due to performance optimizations.

Thanks! I was mostly curious to see benchmarks against the currently documented ones, but this is helpful.
I'm wondering if supporting this is even worth it, since createMediaQuery is called in the style function. I don't think having to use strings with unit values is too crazy (since it's in one place in your theme)

Alternatively, we could simply update the theming docs to be explicit that the breakpoint values should carry a unit now due to performance optimizations.

Let me think about it, but I think this option might be the better way to go

Since it's for performance reasons, but at the same time this is a regression, I'd like to suggest turning this  behaviour into opt-out thing. For example, my project reuses the same breakpoints from theme for other mechanisms and relies on them being numbers, not strings (for the sake of making calculations on them).
My suggestion is to have an additional breakpointsUnit field into theme. If it's not falsy, it will be simply concatenated inside createMediaQuery:
createMediaQuery = (n, unit) => `@media screen and (min-width: ${n}${unit || ''})`

Oops @jxnblk , I missed this:

see benchmarks against the currently documented ones
where can I see the current ones and how can I provide the same numbers?

@aczekajski That could be a reasonable compromise, which I can test for perf based on the above. The extra check alone will incur some extra cost, it's just a question of how much.

Ok, got npm run bench to work eventually by renaming the built cjs file to index.js in /dist.
Benchmarks with this change:
space x 457,043 ops/sec ±0.80% (88 runs sampled)
width x 1,699,514 ops/sec ±0.47% (91 runs sampled)
fontSize x 1,847,931 ops/sec ±0.71% (85 runs sampled)
color x 554,733 ops/sec ±0.78% (88 runs sampled)
style x 1,410,772 ops/sec ±0.77% (87 runs sampled)
width array x 189,809 ops/sec ±0.66% (89 runs sampled)
space array x 169,302 ops/sec ±0.62% (89 runs sampled)
fontSize array x 236,943 ops/sec ±0.54% (91 runs sampled)
color array x 200,609 ops/sec ±0.49% (89 runs sampled)

Baseline before this change:
space x 443,754 ops/sec ±0.66% (88 runs sampled)
width x 1,679,140 ops/sec ±0.99% (89 runs sampled)
fontSize x 1,856,617 ops/sec ±0.85% (86 runs sampled)
color x 563,012 ops/sec ±0.87% (88 runs sampled)
style x 1,428,376 ops/sec ±0.74% (88 runs sampled)
width array x 187,758 ops/sec ±0.71% (90 runs sampled)
space array x 156,278 ops/sec ±0.90% (82 runs sampled)
fontSize array x 232,481 ops/sec ±0.54% (86 runs sampled)
color array x 197,372 ops/sec ±0.60% (87 runs sampled)

Which suggests the cost when integrated is negligible.
@jxnblk I leave it up to you, but using these benchmarks it seems safe.

What code did you perform this benchmark on?
If you didn't see, I've created a pull request https://github.com/jxnblk/styled-system/pull/303 with my proposition. I turned out not to be as simple as doing what I've wrote above but still should be pretty fast.

@aczekajski sorry for being ambiguous. My previous comment was overall benchmark info on my change for @jxnblk . Unlike my earlier post, this measures the impact on the overall system, rather than the atomic function (which is obviously going to be slower with an extra check)

Since px(n) doesn't cause too much of a performance loss, I won't insist to use my solution. It's up to @jxnblk

Any updates on this? 😉

Sorry for the delay!
@BrendanFDMoore thanks for checking the benchmarks on this! Seems like it doesn't appear to have a huge impact, so planning on merging this in and publishing a new version.
@aczekajski planning on going with this one over #303 but thanks for working on this!


CDN link returns 404

The cdn link returns 404.
cdnjs.cloudflare.com/ajax/libs/Vue.Draggable/4.0.0/vuedraggable.umd.min.js

The cdn link still returns 404.
cdnjs.cloudflare.com/ajax/libs/Vue.Draggable/4.0.0/vuedraggable.umd.min.js

Manually downloading and locally sourcing vuedraggable.umd.min gives an error with the simplest implementation of examples.
Error: Failed to resolve component: draggable

Duplicates https://github.com/SortableJS/vue.draggable.next/issues/31. But since here's more interaction, I'd close that one.

You can always use Unpkg cdn: https://unpkg.com/vue-draggable-next Wich turns into the current one<EMAIL_ADDRESS>
This is actually a different package, this is the url you'll want
<EMAIL_ADDRESS>


shouldForwardProp should be used for passing transient props in styled-components

While rendering PDF document, we get:
console warning:
styled-components: it looks like an unknown prop "last" is being sent through to the DOM, which will likely trigger a React console error. If you would like automatic filtering of unknown props, you can opt-into that behavior via"<StyleSheetManager shouldForwardProp={...}>" (connect an API like "@emotion/is-prop-valid") or consider using transient props ("$" prefix for automatic filtering.)
console error:
Warning: Received "true" for a non-boolean attribute "last".
Solution:
shouldForwardProp (https://styled-components.com/docs/api#shouldforwardprop) should be used for passing transient props
The current problem is in:
PDFSingePage line 23 where last prop is being passed to PageWrapper

I'm also encountering this issue.

Any update on this issue?

shouldForwardProp (https://styled-components.com/docs/api#shouldforwardprop) should be used for passing transient props

return (react_1.default.createElement(PageWrapper, { id: "pdf-page-wrapper", last: _pageNum >= numPages },
I think know its related to line 44 but can not figure out how to solve it. I have tried but not success:
 return (react_1.default.createElement(PageWrapper, { id: "pdf-page-wrapper", shouldForwardProp: (prop)=> prop !== 'last', last: _pageNum >= numPages },

@cyntler I have a fix for this but I am unable to push my branch to make a PR. Can I have access or would you rather me paste the code here?


Resolve property-type name conflicts

Fixes: https://github.com/Azure/autorest.csharp/issues/599

This works for 99% of the cases, but keep in mind that if, somehow, there was a [TypeName] property and a [TypeName]Value property already existing, this would cause a different kind of conflict. I've seen weird stuff like that situation from Network before. So, don't be surprised if it happens.

🤦♂


Improved Testing for RNG

@Robadob has potentially found (and fixed?) an issue with the range of random values produced by AgentRandom::uniform.
The test case for this is a little weak (i.e. it doesn't test for uniformity, or the bounds.
Tests need strengthenign to assert that the generated distribution of numbers is aproximately uniform within the expected range, and never generates out of range values.

Seed with a sane seed (or do this for multiple seeds)
Generate lots and lots of random values
Ensure all values are in range (max/min reductions could be used)

Ideally also check min/max expected value is produce, although this will potentially require an incredibly large sample size for floating point values, or large-range integers. Limiting the range of values to be relatively small should (i.e. will be much more likely) to produce values of min and max.

Generata a histogram, and assert that the values are (approximately) uniform.

Simple for integer types, float types will be a bit more complicated.

Ensure that all values

Branch: int_rng_fix

I wrote a standalone test for the uniform float implementation now (after #411 ) present in master.
The code can be found here: https://gist.github.com/Robadob/5e3a068267f8a351991bef16d138dd7c
To my surprise it executes instantly for me locally, producing the below output.
Found 256 zeros
Found 0 ones
Min Bin Size 4194304
Max Bin Size 4194304

Hence, when mapping every generated float value to one of 1024 bins, the bins are uniformly filled.


Treat dates as strings during deserialization, or break API?

Recent development in the schema (moving to JSON Schema) have brought up an issue around how CFF handles dates:

CFF is implemented in YAML, and YAML can represent data types such as date (as an example of timestamp, e.g., date: 2021-06-02 as opposed to date: "2021-06-02").
Up until now, CFF has used the timestamp data type to handle dates (apart from the issue-date field)
JSON cannot handle timestamp/datetime-like data types
For validation, CFF is deserialized from YAML using the respective libraries in a programming language. For Python, for example, ruamel.yaml is being used.
Libraries may be able to convert to native data types during deserialization. E.g., ruamel.yaml deserializes YAML timestamp values to Python datetime.dates.
Now that we have the schema as a schema.json, clients duly expect to be able to use the respective JSON Schema library to validate against schema.json. For Python, e.g., we use jsonschema.
In JSON Schema, though, there is no data type date. Instead, this is solved via formats. I.e., dates are "type": "string" and "format": "date".
Now, when checking the deserialized YAML datetime.date value against the schema, validation fails because datetime.date is not a string!

Two ways to solve this from our side:

Leave the CFF definition as YAML dates as is. Document the potential issue, and leave this to clients to solve for their use case. For Python validation, for example, one can let ruamel.yaml deserialize only YAML date properties as strings so that jsonschema can process correctly, by saying

yaml = ruamel.yaml.YAML(typ='safe')
yaml.constructor.yaml_constructors[u'tag:yaml.org,2002:timestamp'] = \
    yaml.constructor.yaml_constructors[u'tag:yaml.org,2002:str']
yml_data = yaml.load(fi)

(This is implemented for our use case in #204.)

Break API, and release version 2.0.0 (instead of 1.2.0) with dates now being defined in the schema as strings (perhaps of JSON Schema format date, and/or matching a regex pattern), not YAML date values.

To decide whether to do 1. or 2., I'd like to get some opinions, ideally from @jspaaks (for the CFF side), @hainesr (how would you solve this for ruby-cff?) and @arfon (what solution would you like to see from the perspective of "downstream clients"?).

To decide whether to do 1. or 2., I'd like to get some opinions, ideally from @jspaaks (for the CFF side), @hainesr (how would you solve this for ruby-cff?) and @arfon (what solution would you like to see from the perspective of "downstream clients"?).

@paxos – do you have any thoughts here? I saw that some of your updates to ruby-cff in https://github.com/citation-file-format/ruby-cff/pull/32 involved some modifications to the Date/Time parsing.

Break API, and release version 2.0.0 (instead of 1.2.0) with dates now being defined in the schema as strings (perhaps of JSON Schema format date, and/or matching a regex pattern), not YAML date values.

Personally I think this is probably the best option. Just anecdotally (when identifying fixtures/test files for https://github.com/citation-file-format/ruby-cff/pull/32) we found that many of the CITATION files in the wild aren't actually valid anyway (i.e., won't parse) so introducing a breaking change doesn't seem like a huge deal at this stage of the project?

A naïve question while I think through the implications of the above: if JSON schema is unable to parse valid YAML, should we be using JSON schema to validate CFF files?

A naïve question while I think through the implications of the above: if JSON schema is unable to parse valid YAML, should we be using JSON schema to validate CFF files?

Thanks, Rob, good point. IMHO the answer to this is twofold:

Yes, because JSON Schema has a proper definition, a better feature set (e.g., type unions) and supporting libraries, and use is more widespread (although this is intuition only).
Yes, because "clients" will are more likely used to working with JSON Schema rather than with libraries for a "YAML schema" (which isn't properly defined).

In this case, YAML is a superset of JSON has come back to bite us (a bit). One alternative would be to use a YAML Schema extension of JSON Schema, but Space Telescope's extension has been archived, and on this (opinionated?) website, no active developments are noted.
TL;DR: I think JSON Schema is our best option at the moment.

@paxos – do you have any thoughts here? I saw that some of your updates to ruby-cff in citation-file-format/ruby-cff#32 involved some modifications to the Date/Time parsing.

:+1: Would be great to have your opinion as well @paxos. (And if I have previously tried to explain the PR Draft feature to a GitHub employee, I apologize :wink:.)

Personally I think this is probably the best option. Just anecdotally (when identifying fixtures/test files for citation-file-format/ruby-cff#32) we found that many of the CITATION files in the wild aren't actually valid anyway (i.e., won't parse) so introducing a breaking change doesn't seem like a huge deal at this stage of the project?

Thanks! And yes, that's part of the reason why we've relaxed the schema a bit here and there, e.g., downgrading fields from required to optional.

Thanks Stephan, I think you've convinced me 😄 I looked at validating the YAML directly back in 2018 and it seemed flaky at best.
I think I'm still a bit confused though 😆 Can't we treat dates as strings with a particular format in JSON Schema? Do we need JSON Schema to validate the date somehow? If JSON Schema can handle title: my title as a string, why not date: 2021-06-03? I'm sure you've tried this - I'm just venting really...
I've also been playing around in Ruby:
> puts YAML.dump('date' => Date.today)
---
date: 2021-06-03

> puts YAML.dump('date' => Date.today.to_s)
---
date: '2021-06-03'

So we can force YAML to quote a date by forcing the date into a string first. But how we do this automatically I'm not sure yet. I think it must be possible; just need to find where in the underlying to_yaml stack to intercept things.

Thanks Stephan, I think you've convinced me smile I looked at validating the YAML directly back in 2018 and it seemed flaky at best.

Yes, my experience exactly, and I'm afraid not much has changed since then.

I think I'm still a bit confused though laughing Can't we treat dates as strings with a particular format in JSON Schema? Do we need JSON Schema to validate the date somehow?

Sure, we can use two things to enforce string format in JSON Schema: (1) Regex pattern matching, (2) JSON Schema's format option for strings. At the moment we're doing both.
I guess the root issue is a decision between letting the tools do more work, or asking for user behaviour to change. We can do either of two things.

Leave most date values in CFF defined as YAML Date types. In this case, tooling that wants to provides JSON Schema-based validation must make sure that the dates are deserialized into strings, not any native date format. In the case of Python using ruamel.yaml, this can be done as shown above in the first comment. In the case of Ruby, your comment seems to suggest that this can also be done with puts YAML.safe_load(YAML.dump('date' => Date.today.to_s), permitted_classes: [Date]).
Similarly, tooling that wants to provide CFF creation, dates will have to be serialized from whatever format they're in internally, to YAML Date types.
We can change the way that users are allowed to provide dates (in a way that "braks API"), so that they mustn't provide unquoted YAML Dates anymore, but must quote everything and this way provide strings. These will then be deserialized into strings by the respective YAML libraries and can work with JSON Schema without issues.

So the question is really, who we want to "burden" with this, the tool providers (i.e., us :laughing:) by having to deserialize into strings so that validation works), or the users (to use quotes and change existing CFF files so that quotes are used).
In fact, I think there is a third option as well.

Accept both YAML Dates and strings. This leaves more work for the tooling, i.e., depending on whether the supplied value is a string or Date, convert to string or don't. This may be the better option for users, but may require some more work during deserialization on the tooling side.

There is another (much less important) level here as well, in that if some tooling ignored the JSON Schema schema altogether, and validated YAML instead, YAML Dates are semantically more deterministic I guess.

I suppose I am inclined to keep dates as YAML dates in the files themselves and deal with it internally if possible?

@jspaaks and me have talked about this now, and have decided to go with this option:

In fact, I think there is a third option as well.

Accept both YAML Dates and strings. This leaves more work for the tooling, i.e., depending on whether the supplied value is a string or Date, convert to string or don't. This may be the better option for users, but may require some more work during deserialization on the tooling side.

So, valid CFF date-related keys will be valid in these two forms:
date-in-date: 2021-06-09
date-in-string: "2021-06-09"

These date-related fields are (still) not valid CFF:
date-with-bad-format-in-string: "2021-06-99"
date-with-bad-format-in-string: "04-2021"

This means that tools wanting to read CFF will have to be able to treat dates as follows:
# Pseudocode

cff = yaml.safe_load(CFF_file)
if cff.date instance of String:
    # Leave as is because JSON Schema will be able to validate.
    # If processed further here, make sure to validate in some way.
else if cff.date instance of Datetime.Date:
    String date_string = cff.date.to_string()

Or use YAML library deserialization options if available, such as
# During deserialization, read all timestamps as strings
yaml.constructor.yaml_constructors[u'tag:yaml.org,2002:timestamp'] = \
    yaml.constructor.yaml_constructors[u'tag:yaml.org,2002:str']

Implement for Python and add tests, merged in https://github.com/citation-file-format/citation-file-format/commit/56b5f4d20d5b966fb4bd74479e8543e22248bb0e.


Error: NotSupportedError: Failed to load because no supported source was found.

Checklist

[X] I read the troubleshooting guide before raising this issue
[X] I made sure that the issue I am raising doesn't already exist

Current bug behaviour
Error: NotSupportedError: Failed to load because no supported source was found.
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 299:10  createErrorWithStack
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 355:28            _throw
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/core/errors.dart 120:5                                           throwWithStackTrace
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/zone.dart 1385:11                                          callback
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15
Expected behaviour
the audio from web can play properly.
Steps to reproduce

Execute flutter run on the code sample
...
...

Code sample

Code sample
import 'package:flutter/material.dart';
import 'package:audioplayers/audioplayers.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'audio_test',
debugShowCheckedModeBanner: false,
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: const DetailAudioPage(),
);
}
}
class DetailAudioPage extends StatefulWidget {
const DetailAudioPage({Key? key}) : super(key: key);
@override
State createState() => _DetailAudioPageState();
}
class _DetailAudioPageState extends State {
final audioPlayer = AudioPlayer();
@override
void initState() {
super.initState();
}
@override
Widget build(BuildContext context) {
return Scaffold(
backgroundColor: const Color(0xFFdee7fa),
body: IconButton(
key: const Key('play_button'),
iconSize: 48.0,
color: Colors.blue,
icon: const Icon((Icons.arrow_forward)),
onPressed: () async {
await audioPlayer
.setSourceUrl("https://www.sengtuan.net/audio/song/1.mp3");
await audioPlayer.resume();
}));
}
}

Affected platforms
web
Platform details
No response
AudioPlayers Version
3.0.1
Build mode
debug
Audio Files/URLs/Sources
https://www.sengtuan.net/audio/song/1.mp3
Screenshots

Logs

my relevant logs

Full Logs

my full logs or a link to a gist

Flutter doctor:
Output of: flutter doctor -v

Related issues / more information
No response
Working on PR
no way

at last,  it sovled by change the  NGINX server config by add two statements:
add_header Cache-Control no-cache;
add_header Access-Control-Allow-Origin *;


buff stack size for some items

 autistic.sack.of.friends on Discord says

https://modrinth.com/mod/biggerstacks
building blocks is an obvious one, but devices are pretty important too.

 autistic.sack.of.friends on Discord says

how many items is reasonable

 yarden.zamir on Discord says

thinking 4x or 8x the norm

 yarden.zamir on Discord says

but could be more

 autistic.sack.of.friends on Discord says

i wonder if that'll make it more efficient to transfer some items as things that crush into them

 yarden.zamir on Discord says

as there is no specific reason it shouldnt be

 autistic.sack.of.friends on Discord says

if so, that is really cool

 yarden.zamir on Discord says

interesting, compression

 autistic.sack.of.friends on Discord says

compression but only because the number of items goes way up

 yarden.zamir on Discord says

same as compression. number of pices to move is larger in that format

 yarden.zamir on Discord says

smaller

 autistic.sack.of.friends on Discord says

we should probably indicate stack size somewhere

 autistic.sack.of.friends on Discord says

given it's significantly different to vanilla

 yarden.zamir on Discord says

we can add it in the same row as our other stuff in the tooltip

 yarden.zamir on Discord says

clould be the first item as its small

 autistic.sack.of.friends on Discord says

are you sure?

 autistic.sack.of.friends on Discord says

it almost certainly won't exceed 4 characters actually

 autistic.sack.of.friends on Discord says

sounds fine

 yarden.zamir on Discord says

i think so yea, shouldt have a cost really

 autistic.sack.of.friends on Discord says

testing just adding it to the pack now

 yarden.zamir on Discord says

awesome

 autistic.sack.of.friends on Discord says

works exactly as you'd expect, given the slider's range

 autistic.sack.of.friends on Discord says

funnels have a secret hard limit of 64 items

 yarden.zamir on Discord says

yea that makes sense, seen their code

 yarden.zamir on Discord says

()

 yarden.zamir on Discord says

(plz mrg ma pr create)

 autistic.sack.of.friends on Discord says

do we have any good idea of what constitutes a building block

 autistic.sack.of.friends on Discord says

oh yeah yarden.zamir should we move all stacksize modification to rely on this

 autistic.sack.of.friends on Discord says

so it's not a startup-only thing

 autistic.sack.of.friends on Discord says

tag ptdye:stacks_to_1
tag ptdye:stacks_to_2
tag ptdye:stacks_to_4
tag ptdye:stacks_to_8
tag ptdye:stacks_to_16
tag ptdye:stacks_to_32
tag ptdye:stacks_to_64
tag ptdye:stacks_to_128
tag ptdye:stacks_to_256
tag ptdye:stacks_to_512
tag ptdye:stacks_to_1024
tag ptdye:stacks_to_2048

```

 yarden.zamir on Discord says

yes

 yarden.zamir on Discord says

i take back everything good i ever said about this mod

 yarden.zamir on Discord says

why does it use xml

 yarden.zamir on Discord says

lol

 autistic.sack.of.friends on Discord says

good for nested structured data

 autistic.sack.of.friends on Discord says

you can just add another condition tag

 autistic.sack.of.friends on Discord says

or you can add an  tag

 autistic.sack.of.friends on Discord says

it's much more explicit

 yarden.zamir on Discord says

hm

 autistic.sack.of.friends on Discord says

means you don't need an extra element inside of each rule to say the stacksize, along with enforcing everything which you can only have one of being in the same place

 autistic.sack.of.friends on Discord says

id minecraft:potion
id minecraft:lingering_potion
id minecraft:splash_potion

id minecraft:enchanted_book

```

 autistic.sack.of.friends on Discord says

like if you're using it without forcing it into our structuring system

 autistic.sack.of.friends on Discord says

then it's designed for maximum power

 autistic.sack.of.friends on Discord says

also why can't we just swap out these piles of regexes for tags

 autistic.sack.of.friends on Discord says

how long has that been there

 yarden.zamir on Discord says

tag ptdye:stacks_to_1
tag ptdye:stacks_to_2

id minecraft:potion
id minecraft:lingering_potion
id minecraft:splash_potion

tag ptdye:stacks_to_1024

ruleset:

stacksize: 1
condition: tag ptdye:stacks_to_1
stacksize: 2
condition: tag ptdye:stacks_to_2
stacksize: 32
condition:
or:
- id minecraft:potion
- id minecraft:lingering_potion
- id minecraft:splash_potion
stacksize: 1024
condition: tag ptdye:stacks_to_1024

 autistic.sack.of.friends on Discord says

doesn't look as nice imo

 yarden.zamir on Discord says

i think the latter is much more readable

 autistic.sack.of.friends on Discord says

it's definitely hitting the points of "explicit" and "readable"

 autistic.sack.of.friends on Discord says

also syntax higlighting really helps. you're kinda putting xml at a disadvantage here

 yarden.zamir on Discord says

long time i expect

 autistic.sack.of.friends on Discord says

addToTag("ptdye:stacks_to_8",[
"#forge:tools",
"#forge:armors"
])

 autistic.sack.of.friends on Discord says

like wow that is simpler

 autistic.sack.of.friends on Discord says

set it to 8 for testing

 autistic.sack.of.friends on Discord says

16 would have been unnoticable

 yarden.zamir on Discord says

true, fixed

 autistic.sack.of.friends on Discord says

i'm guessing this works with multiple conditions?

 autistic.sack.of.friends on Discord says

ruleset:

stacksize: 1
condition: tag ptdye:stacks_to_1
stacksize: 2
condition: tag ptdye:stacks_to_2
condition: tag ptdye:stacks_to_4
stacksize: 32
condition:
or:
- id minecraft:potion
- id minecraft:lingering_potion
- id minecraft:splash_potion
stacksize: 1024
condition: tag ptdye:stacks_to_1024

 autistic.sack.of.friends on Discord says

this would require something to be tagged with both stacks_to_2 and stacks_to_4

 yarden.zamir on Discord says

{
"ruleset": [
{
"stacksize": 1,
"condition": "tag ptdye:stacks_to_1"
},
{
"stacksize": 2,
"condition": "tag ptdye:stacks_to_2"
},
{
"stacksize": 32,
"condition": {
"or": [
"id minecraft:potion",
"id minecraft:lingering_potion",
"id minecraft:splash_potion"
]
}
},
{
"stacksize": 1024,
"condition": "tag ptdye:stacks_to_1024"
}
]
}

 autistic.sack.of.friends on Discord says

ok well it's already lost it's space efficiency

 autistic.sack.of.friends on Discord says

and still doesn't handle multiple conditions autoamtically

 yarden.zamir on Discord says

depends on the schema i guess

 autistic.sack.of.friends on Discord says

ok, so we've already found an implementation-dependant issue with your one

 engineersmith_4628 on Discord says

Looking through the sauce. It's totally possible to use this code to change the distances containers open at

 yarden.zamir on Discord says

the xml is not?)

 autistic.sack.of.friends on Discord says

it's following xml spec

 yarden.zamir on Discord says

or is an xml thing? not an implementation thing?

 autistic.sack.of.friends on Discord says

an array of non-identical elements is badly representable by most formats

 yarden.zamir on Discord says

wut, thats amazing

 autistic.sack.of.friends on Discord says

like this has duplicate condition keys

 yarden.zamir on Discord says

how does it look in xml

 engineersmith_4628 on Discord says

Well; they somehow use the code to override constants for vanilla classes. And as the reach distances is a constant in the same files. I assume it would be as easy as doing something similar in ptdyeplus

 yarden.zamir on Discord says

plz do, ill give my left arm

 yarden.zamir on Discord says

no actually i need it

 engineersmith_4628 on Discord says

I'll give it a go

 autistic.sack.of.friends on Discord says

mod minecraft

id minecraft:potion
id minecraft:lingering_potion
id minecraft:splash_potion
tag create:deployable_drink

id minecraft:enchanted_book

```

 engineersmith_4628 on Discord says

Can I have your right foot tiny toe?

 autistic.sack.of.friends on Discord says

you can have multiple ors and conditions in the same rule

 yarden.zamir on Discord says

sure, i think i dont need that

 autistic.sack.of.friends on Discord says

without needing to do a 2 tier json table

 yarden.zamir on Discord says

not sure i see the difference

 yarden.zamir on Discord says

ruleset:
- stacksize: 32
condition:
- mod minecraft
- or:
- id minecraft:potion
- id minecraft:lingering_potion
- id minecraft:splash_potion
- tag create:deployable_drink
- stacksize: 64
condition:
- id minecraft:enchanted_book)

 autistic.sack.of.friends on Discord says

can you still have more than 1 or key

 autistic.sack.of.friends on Discord says

{
"stacksize": 32,
"conditions": [
{"type":"condition","contents":"id minecraft:potion"},
{"type":"or","conditions":[
{"type":"condition","contents":"id minecraft:potion"},
{"type":"condition","contents":"id minecraft:potion"},
{"type":"condition","contents":"id minecraft:potion"}
]}
]
}

 autistic.sack.of.friends on Discord says

also if you're following best principles, "stacksize" has to take up it's own entire line

 yarden.zamir on Discord says

true

 yarden.zamir on Discord says

rule:
stacksize: 32
conditions:
- mod: minecraft
- or:
- id: minecraft:potion
- id: minecraft:lingering_potion
- id: minecraft:splash_potion
- tag: create:deployable_drink

rule:
stacksize: 64
conditions:
- id: minecraft:enchanted_book

 autistic.sack.of.friends on Discord says

duplicate "id" tags

 autistic.sack.of.friends on Discord says

i would do SO great at the job of writing config file parser errors

 autistic.sack.of.friends on Discord says

why does a chest boat cost logs, but the boat + chest recipe still exist

 yarden.zamir on Discord says

true

 autistic.sack.of.friends on Discord says

there's no way around adding a second layer of nesting

 yarden.zamir on Discord says

should be furnished device

 yarden.zamir on Discord says

i dont mind a second layer, still feels more readable

 yarden.zamir on Discord says

but it i get the disadvantage yea

 autistic.sack.of.friends on Discord says

more nesting, which means more to think about

 autistic.sack.of.friends on Discord says

there's also no requirement for a closing bracket to say what it's closing

 autistic.sack.of.friends on Discord says

(& no way, json does not support comments)

 autistic.sack.of.friends on Discord says

xml does, out of the box

 autistic.sack.of.friends on Discord says

<!-- blah blah blah -->

 yarden.zamir on Discord says

i think thats a great thing

 yarden.zamir on Discord says

agreed that was a crime against humanity

 autistic.sack.of.friends on Discord says

reduces readability a little for mantainers, one could argue quite easily

 autistic.sack.of.friends on Discord says

it wasn't designed for human writing

 autistic.sack.of.friends on Discord says

it was designed to quickly pack and unpack js objects

 yarden.zamir on Discord says

i find xml so much harder to read as a human

 yarden.zamir on Discord says

like five times more hard

 yarden.zamir on Discord says

rules:

name: "potions"
stacksize: 32
conditions:

type: "mod"
value: "minecraft"
type: "or"
values:

type: "id"
value: "minecraft:potion"
type: "id"
value: "minecraft:lingering_potion"
type: "id"
value: "minecraft:splash_potion"
type: "tag"
value: "create:deployable_drink"

name: "enchanted books"
stacksize: 64
conditions:

type: "id"
value: "minecraft:enchanted_book"

 yarden.zamir on Discord says

i think this is very readable

 autistic.sack.of.friends on Discord says

my overall point is it is NOT that bad. especially with syntax highlighting

 autistic.sack.of.friends on Discord says

also we never need to look at this file again

 autistic.sack.of.friends on Discord says

you can also generally speaking include arbitrary whitespace

 autistic.sack.of.friends on Discord says

unlike toml

 autistic.sack.of.friends on Discord says

much more freedom to make things look nice

 yarden.zamir on Discord says

i agree i just personally never found positive value in xml but found much negative so i dont have a positive reaction when someone chooses to specifically use it. i dont actually mind that much

 autistic.sack.of.friends on Discord says

it's a good choice for some things and a bad one for others

 autistic.sack.of.friends on Discord says

but any time that values:[{type:blah,value:1},{type:blah,value:2}] structure shows up, i'd say json shows a bit of a weaknesss

 yarden.zamir on Discord says

this is the nested json

 yarden.zamir on Discord says

{
"rules": [
{
"name": "potions",
"stacksize": 32,
"conditions": [
{"type": "mod", "value": "minecraft"},
{"type": "or", "values": [
{"type": "id", "value": "minecraft:potion"},
{"type": "id", "value": "minecraft:lingering_potion"},
{"type": "id", "value": "minecraft:splash_potion"},
{"type": "tag", "value": "create:deployable_drink"}
]}
]
},
{
"name": "enchanted books",
"stacksize": 64,
"conditions": [
{"type": "id", "value": "minecraft:enchanted_book"}
]
}
]
}

 yarden.zamir on Discord says

still getting used to the new keyboard so sometimes i send when i dont intend

 autistic.sack.of.friends on Discord says

the "type" thing takes longer to type than the length of an xml tag

 autistic.sack.of.friends on Discord says

and there's plenty of systems for auto-closing

 autistic.sack.of.friends on Discord says

and other trade products, i guess

 yarden.zamir on Discord says

not sure

 autistic.sack.of.friends on Discord says

ASHDOASD

 yarden.zamir on Discord says

we can split product, building block, ingredient and tool stack size changes)

 autistic.sack.of.friends on Discord says

yeah, makes sense

 yarden.zamir on Discord says

i do sometimes yes

 autistic.sack.of.friends on Discord says

i was key mashing in a differnt server and accidentally hit a key on my drawing tablet

 autistic.sack.of.friends on Discord says

sending me whizzing back here

 autistic.sack.of.friends on Discord says

there's no tag for "gray plate" in general

 autistic.sack.of.friends on Discord says

would it be fair to say "anything that can be stonecut into a stair is a building block"

 yarden.zamir on Discord says

yes actually. but also some others

 yarden.zamir on Discord says

how do you dynamically find block like teracota

 yarden.zamir on Discord says

maybe creative tab category

 autistic.sack.of.friends on Discord says

ehh, not sure

 autistic.sack.of.friends on Discord says

i just added everything that can be stair'd

 autistic.sack.of.friends on Discord says

well, everything in the variants system

 yarden.zamir on Discord says

The main reason I wanted this was for terracotta that clogged my inventory

 autistic.sack.of.friends on Discord says

there

 yarden.zamir on Discord says

Nice

 autistic.sack.of.friends on Discord says

not ideal, drawers always extract a full stack

 autistic.sack.of.friends on Discord says

ideally i'd want a little less so i have room if i do some deconstruction

 engineersmith_4628 on Discord says

I've only gone and f**cken' done it

 yarden.zamir on Discord says

Amazing! Great job!

 yarden.zamir on Discord says

It's awesome that you looked at the code and found it

 yarden.zamir on Discord says

I have a feeling this approach might prove useful in future too

 engineersmith_4628 on Discord says

this only works on vanilla containers right now; so things like chests, barrels, dispenser, dropper, hopper, trapped chest & shulkers

 engineersmith_4628 on Discord says

It's actually so easy to do

 engineersmith_4628 on Discord says

Plus you can do it onto other mods too

 yarden.zamir on Discord says

So the trading station, me terminal etc

 engineersmith_4628 on Discord says

ye ye

 yarden.zamir on Discord says

That's gonna be great

 yarden.zamir on Discord says

The me terminal is the best part

 yarden.zamir on Discord says

Wireless terminal at home

 autistic.sack.of.friends on Discord says

me terminal already works

 yarden.zamir on Discord says

Ah, right it was mention before

 yarden.zamir on Discord says

I didn't remember which thing wroekd from afar

 Generic name on Discord says

could we somehow make sandpaper stack as well?

 yarden.zamir on Discord says

makes less sense to me as the logistics of sandpaper are something we want

 autistic.sack.of.friends on Discord says

oh yeah forgot to mention but I did add all concrete and terracotta

 yarden.zamir on Discord says

what's the status on that? is anything else needed or can we give it a go?

 autistic.sack.of.friends on Discord says

oh right i just lost focus because I was ill. I'll push what I have later

 autistic.sack.of.friends on Discord says

it needs some ME testing still

 autistic.sack.of.friends on Discord says

https://github.com/chipsams/Create-Prepare-to-Dye/tree/stacksize-increaser

 autistic.sack.of.friends on Discord says

here's the branch

 autistic.sack.of.friends on Discord says

yarden.zamir was this all fine?

 autistic.sack.of.friends on Discord says

oh, sure! are modlists included in prs or will you have to do that manually

 yarden.zamir on Discord says

included in prs with packwiz but I can do that part too, I can edit prs live I belive


[BEAM-7785] Synchronize watermarks with bundle processing

Fixes [BEAM-7785] by locking only specific AppliedPTransform.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.


Improve username behavior

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

i have completed the task given


Tech debt/civ 5541 refactor payment

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Changes on Claim
paymentOption?: PaymentOptionType; (Removed, because already used on PaymentIntention)
paymentDate?: Date; (Removed, because already used on PaymentIntention)
repaymentPlan?: RepaymentPlan; (Moved into PaymentIntention which on both Part/Full Admission)
fullAdmission?: FullAdmission; (Added to Claim)
claim {
.....
fullAdmission?: FullAdmission;
partialAdmission?: PartialAdmission;
rejectAllOfClaim?: RejectAllOfClaim;
.....
}

class FullAdmission {
  PaymentIntention?: PaymentIntention;
}

class PartialAdmission {
  .....
  .....
  PaymentIntention?: PaymentIntention;
}

class PaymentIntention {
  paymentOption?: PaymentOptionType;
  paymentDate?: Date;
  repaymentPlan?: RepaymentPlan;
}


CCRandom throwing Overflow exception on 4S devices.

Does not seem to happen on other platforms

Closed via commit https://github.com/mono/CocosSharp/commit/1aeef3877c74980f92ed48ea715366de9f1da1b5


Bugs

Any bugs or issues in the current project will be added here

The Footer code needs some formatting. Can I do this?

Broken image of HakinCodes. Correct readme file.

Broken image of HakinCodes. Correct readme file.

can I work on this issue?


Proposal to remove com.sun:tools dependencies

Which module is your feature request related to?
pinpoint-jboss-plugin
Is your feature request related to a problem?
Among the modules of pinpoint, pinpoint-jboss-plugin has a dependency on com.sun.tools with the following dependency.
pinpoint-jboss-plugin
  org.jboss.as:jboss-as-security:7.2.0.Final
   org.jboss.as:jboss-as-clustering-infinispan:7.2.0.Final
     com.sun: tools: 1.6

Describe the solution you'd like
My company is using zulu jdk as a java license issue.
Since zulu jdk doesn't support the com.sun.~ module, I am building pinpoint by manually removing it.
Other open sources doesn't use com.sun module for license problem.
I suggest that Pinpoint also removes com.sun.tools dependency.
At least for future support of the java 11 version, I hope this issue is addressed.
Additional context
We can also see the following comments in the zipkin source code.
https://github.com/openzipkin/zipkin/blob/78e7edcb844d9e61696a76587e7cb023054c5261/pom.xml#L413
<!-- or die! com.sun.tools.javac.api.JavacTool -->
I'd like you to consider it again.

[INFO] com.navercorp.pinpoint:pinpoint-jboss-plugin:jar:1.9.0-SNAPSHOT
[INFO] +- com.navercorp.pinpoint:pinpoint-bootstrap-core:jar:1.9.0-SNAPSHOT:provided <-- all provided scope
[INFO] |  +- com.navercorp.pinpoint:pinpoint-annotations:jar:1.9.0-SNAPSHOT:provided
[INFO] |  \- com.navercorp.pinpoint:pinpoint-commons:jar:1.9.0-SNAPSHOT:provided
[INFO] +- org.jboss.as:jboss-as-security:jar:7.2.0.Final:provided
[INFO] |  +- org.jboss.msc:jboss-msc:jar:1.0.4.GA:provided
[INFO] |  +- org.jboss.as:jboss-as-domain-management:jar:7.2.0.Final:provided
[INFO] |  |  +- org.jboss:jboss-common-core:jar:2.2.17.GA:provided
[INFO] |  |  +- org.jboss.as:jboss-as-controller:jar:7.2.0.Final:provided
[INFO] |  |  |  +- org.jboss.as:jboss-as-controller-client:jar:7.2.0.Final:provided
[INFO] |  |  |  \- org.jboss:staxmapper:jar:1.1.0.Final:provided
[INFO] |  |  \- org.jboss:jboss-dmr:jar:1.1.6.Final:provided
[INFO] |  +- org.jboss.as:jboss-as-server:jar:7.2.0.Final:provided
[INFO] |  |  +- org.jboss.as:jboss-as-domain-http-interface:jar:7.2.0.Final:provided
[INFO] |  |  |  \- org.jboss.com.sun.httpserver:httpserver:jar:1.0.1.Final:provided
[INFO] |  |  +- org.jboss.as:jboss-as-deployment-repository:jar:7.2.0.Final:provided
[INFO] |  |  |  \- org.jboss.as:jboss-as-protocol:jar:7.2.0.Final:provided
[INFO] |  |  |     \- org.jboss.xnio:xnio-nio:jar:3.0.7.GA:provided
[INFO] |  |  +- org.jboss.as:jboss-as-platform-mbean:jar:7.2.0.Final:provided
[INFO] |  |  +- org.jboss.as:jboss-as-process-controller:jar:7.2.0.Final:provided
[INFO] |  |  |  \- system:jdk-tools:jar:jdk:system   <--- system scope

The maven-scope of jdk-tools is in use of the system scope, so there is no problem.

pinpoint-jboss-plugin does not include or refer to jdk-tools.
All dependencies of pinpoint-jboss-plugin use provided-scope and required only for compilation.
For these reasons, I don't know if I should fix this problem.

Are jboss-plugin compilation not working in zulu jdk?
If you have an error log, please attach it.

First of all, thank you for your quick reply.
When I come to work on Monday,
I will contact if there is no license problem with provided scope usage.

Since com.sun: tools module is not included in azul zulu JDK, I misunderstood as commercial licenses.
However  I find it is a GPL 2.0 License.
https://mvnrepository.com/artifact/com.sun/tools/<IP_ADDRESS>
The misunderstanding is resolved and I'm closing issue.


Fix parser backtracking

Address issues with parser order, including issue #106 and possibly #93.

Core parser was order dependent on several productions and would confuse a
number of things as message definitions.
Corrected by adding back-tracking on every production in message.
Also fixed running tests when the project path includes a hash symbol, as
in .../F#/...

@ctaggart can you verify this PR and make a release?


CI with newer Go versions

Coverage remained the same at 98.947% when pulling dc99b36fe9b7a717f7b3a3687312ad2cc1e0ae2b on travis into 92b9680a31b97b984e5c59865844f538d6f75d45 on master.

Coverage remained the same at 98.947% when pulling dc99b36fe9b7a717f7b3a3687312ad2cc1e0ae2b on travis into 92b9680a31b97b984e5c59865844f538d6f75d45 on master.


updated the url for successful thumbnail publishes

This is an update for the app to use a static embed url for successful thumbnails published via spee.ch.
This is dependent upon merging the following PR on spee.ch: https://github.com/lbryio/spee.ch/pull/529

Whoops. We can merge this after that PR is merged.


 In my testing, i found that b'{\n\t"hello": "world"\n}' seems to be the actual output of sops (i'm using sops 3.9.1 on a M1 MacBook).
This unfortunately raises an error in
https://github.com/nikaro/sopsy/blob/e0a9c0ad165cdca84a1c1492504cf1ecc00dbc49/src/sopsy/utils.py#L66
Traceback (most recent call last):
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/sopsy/utils.py", line 66, in get_dict
    out = yaml.safe_load(data)
          ^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/__init__.py", line 125, in safe_load
    return load(stream, SafeLoader)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/__init__.py", line 81, in load
    return loader.get_single_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/constructor.py", line 49, in get_single_data
    node = self.get_single_node()
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/composer.py", line 35, in get_single_node
    if not self.check_event(StreamEndEvent):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/parser.py", line 98, in check_event
    self.current_event = self.state()
                         ^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/parser.py", line 142, in parse_implicit_document_start
    if not self.check_token(DirectiveToken, DocumentStartToken,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/scanner.py", line 116, in check_token
    self.fetch_more_tokens()
  File "/Users/pavel/Projects/pydantic-settings-sops/.pixi/envs/default/lib/python3.12/site-packages/yaml/scanner.py", line 258, in fetch_more_tokens
    raise ScannerError("while scanning for the next token", None,
yaml.scanner.ScannerError: while scanning for the next token
found character '\t' that cannot start any token
  in "<byte string>", line 2, column 1:
    	"foobar": "foo"

I'am also using sops 3.9.1 on a M1 and i don't have this issue. Tests are passing from python 3.9 to 3.12.
How do you get this error? While running test or with actual code? Can you provide a reproduction case?

Is the failing CI in https://github.com/pavelzw/pydantic-settings-sops/pull/3 enough for you?
You should be able to reproduce it locally by doing the following
# checkout PR
brew install pixi
pixi run postinstall
pixi run test

Weird, i still do not reproduce it with your steps:
⏺ ~/D/g/p/pydantic-settings-sops | main✓ > set -x SOPS_AGE_KEY (grep AGE-SECRET tests/resources/key.txt)
⏺ ~/D/g/p/pydantic-settings-sops | main✓ > pixi run test
✨ Pixi task (test in default): pytest
======================================================= test session starts =======================================================
platform darwin -- Python 3.12.7, pytest-8.3.3, pluggy-1.5.0
rootdir: /Users/nicolas/Developer/github.com/pavelzw/pydantic-settings-sops
configfile: pyproject.toml
testpaths: tests
plugins: cov-5.0.0
collected 1 item

tests/test_sops.py .                                                                                [100%]

======================================================== warnings summary =========================================================
tests/test_sops.py:20
  /Users/nicolas/Developer/github.com/pavelzw/pydantic-settings-sops/tests/test_sops.py:20: PytestCollectionWarning: cannot collect test class 'TestSettings' because it has a __init__ constructor (from: tests/test_sops.py)
    class TestSettings(BaseSettings):

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================================================== 1 passed, 1 warning in 0.20s ===================================================

I will continue to investigate, maybe trying to remove mocking for sops commands and let sops do the actual job to ensure it is correct (it may require a bit more setup though...). But if you could provide a small reproducer it would be nice.

Ok now i can reproduce. PyYAML cannot load (pretty) JSON finally. I will try to fix it this weekend.

This is fixed and released in https://github.com/nikaro/sopsy/releases/tag/1.0.1
Thanks for reporting it.


how to install it by pip install cupy-cuda90 --user

due to i have no server privilege，i must use “--user” to install cupy，but an error occurred。
i can sure cuda and cudnn is in its path。
when i try ：
CFLAGS=/usr/local/cuda/include LDFLAGS=/usr/local/cuda/lib64 CUDA_PATH=/usr/local/cuda pip install cupy --user
it is also dont work。
I have no idea anymore. thank you
Modules:
cuda      : No
-> Include files not found: ['cublas_v2.h', 'cuda.h', 'cuda_profiler_api.h', 'cuda_runtime.h', 'cufft.h', 'curand.h', 'cusparse.h', 'nvrtc.h']
-> Check your CFLAGS environment variable.
ERROR: CUDA could not be found on your system.

import chainer
/home/admin/.local/lib/python3.6/site-packages/chainer/backends/cuda.py:98: UserWarning: cuDNN is not enabled.
Please reinstall CuPy after you install cudnn
(see https://docs-cupy.chainer.org/en/stable/install.html#install-cudnn).
'cuDNN is not enabled.\n'
/home/admin/.local/lib/python3.6/site-packages/h5py/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from float to np.floating is deprecated. In future, it will be treated as np.float64 == np.dtype(float).type.
from ._conv import register_converters as _register_converters
print(chainer.cuda._resolution_error)
/home/admin/.local/lib/python3.6/site-packages/cupy/cuda/cudnn.cpython-36m-x86_64-linux-gnu.so: symbol cudnnGetBatchNormalizationTrainingExReserveSpaceSize, version libcudnn.so.7 not defined in file libcudnn.so.7 with link time reference

/home/admin/.local/lib/python3.6/site-packages/cupy/cuda/cudnn.cpython-36m-x86_64-linux-gnu.so: symbol cudnnGetBatchNormalizationTrainingExReserveSpaceSize, version libcudnn.so.7 not defined in file libcudnn.so.7 with link time reference

Please try removing cuDNN path from your LD_LIBRARY_PATH to use cuDNN bundled with the wheel distribution.

@kmaehashi thanks


How to ORDER BY specific order

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the SQLModel documentation, with the integrated search.
[X] I already searched in Google "How to X in SQLModel" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to SQLModel but to Pydantic.
[X] I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
SELECT
	id,
	`name`
FROM
	tb_shop
WHERE
	id IN ( 1, 2, 3 )
ORDER BY
	FIELD( id, 2, 1, 3 )

Description
How to use sqlmodel to implement the above sql query with specific order？
Operating System
Windows
Operating System Details
No response
SQLModel Version
0.0.6
Python Version
3.7.6
Additional Context
No response

You can use any function from sqlalchemy:
import sqlalchemy
from sqlmodel import select

select(
    Hero.id,
    Hero.name,
).where(
    Hero.id.in_([1, 2, 3]),
).order_by(
    sqlalchemy.func.field(Hero.id, 2, 1, 3),
)


firstOrCreate() only encrypts properties in first parameter--not second.

firstOrCreate() takes a second parameter--a list of attributes to be applied to model that is found or created: https://laravel.com/docs/5.5/eloquent
$flight = App\Flight::firstOrCreate(
['name' => 'Flight 10'], ['delayed' => 1]
);
In this case, "delayed" would not be encrypted.

Closing: zero technical context. Feel free to re-open w a repro case.


Add toString() methods to all request/response objects for easier debugging

Not sure if it's considered a request/response object but NfsStatus could also benefit from a toString to make error messages easier (possible) to diagnose. I'm curious why this class wasn't defined as an Enum which would have had a better default toString rendering but I'd settle for a better toString for sure.
The error message currently shows:
com.emc.ecs.nfsclient.nfs.NfsException: Error in NfsReaddirRequest serviceVersion:3 xid:-2034612967 usePrivilegedPort:false fileHandle:[1,2,3...] cookie:0 cookieverf0 error code:com.emc.ecs.nfsclient.nfs.NfsStatus@177ed3d3

I'm also not sure why this wasn't an enum, but probably to allow for additional (unknown) status codes.  In any case, this should be addressed by #42.


Docking Station Compatibility

This isn't an issue, but I want to report that the docking station's USB ports, displayport, and VGA ports all work. Thank you for the great hackintosh guide

Thanks! I will update the readme. 👍

Hello @valnoxy , I have problem with Docking Station when i reboot or shutdown my device, its not shutdown properly

This isn't an issue, but I want to report that the docking station's USB ports, displayport, and VGA ports all work. Thank you for the great hackintosh g

This isn't an issue, but I want to report that the docking station's USB ports, displayport, and VGA ports all work. Thank you for the great hackintosh guide

Have you tried to reboot, sleep, or turn off the laptop when plugged in the docking station


Zathura Support For Iceberg.

I have come to really like this colorscheme and I made a port to zathura for this awesome colorscheme.
https://github.com/gdnand/zathura-iceberg.git

Thank you for the information :)


[Nox.Lib] Update README and noxorg.dev to comment out Swagger refs in program.cs

Waiting on Dmytro to move Swagger functionality into Nox.Lib and nuget release.
See issue #152

Both Nox.Lib README and noxorg.dev updated.