co.uk tld not working

Hello,
I have 2 domains that I am configuring with wildcard certs, my .com domain is working correctly, but my .co.uk domain does not work correctly and appears to not be parsing the domain properly.
Caddyfile
*.example.com, example.com, *.example.co.uk, example.co.uk {
    tls {
        issuer zerossl APIKEY {
            email EMAIL
            dns cloudflare APIKEY
        }
    }
}

.co.uk error
ERROR	tls.obtain	will retry	{"error": "[*.example.co.uk] Obtain: [*.example.co.uk] solving challenges: presenting for challenge: adding temporary record for zone \"co.uk.\": expected 1 zone, got 0 for co.uk.
I have confirmed that both of the domains are included in the API token on Cloudflare and example.com is working correctly. The same issue also appears for example.co.uk so it appears to be something to do with the .co.uk tld
Any suggestions to get this working would be greatly appreciated.
Thanks in advance

What is the domain? I'll look into it.

The domain is matthealy.co.uk that is causing the error.
Thank you

Hmm, the domain looks like it has SOA records at Cloudflare and such. I wonder if your local DNS resolver is being weird? Do you have any funky DNS config going on with your network?

There's nothing special about my DNS, I'm using <IP_ADDRESS> as my resolver and it works for my .com domain.
I thought it was something to do with the parsing of the domain as the error states:
adding temporary record for zone \"co.uk.\": expected 1 zone, got 0 for co.uk
It doesn't seem to parse the full domain, just the tld, unless this is expected for the log

I don't think there's any domain "parsing" done, but we do look up the SOA for the domain so that we can infer the zone, which should be matthealy.co.uk in your case. For some reason it's not finding the SOA.
I just tried it on my machine too, and got a similar error, but slightly different:
2024/05/20 15:51:10.048	ERROR	tls.obtain	could not get certificate from issuer	{"identifier": "matthealy.co.uk", "issuer": "acme-staging-v02.api.letsencrypt.org-directory", "error": "[matthealy.co.uk] solving challenges: presenting for challenge: adding temporary record for zone \"matthealy.co.uk.\": expected 1 zone, got 0 for matthealy.co.uk.

I am not really sure what is going on here :thinking:
I don't have time to dive into this too much right now, but hopefully this information makes troubleshooting a little clearer

That's really strange, I don't understand why for you it attempts to add the temporary record for the domain, but for me it attempts it for just co.uk
2024/05/20 16:50:23.197	ERROR	tls.obtain	will retry	{"error": "[matthealy.co.uk] Obtain: [matthealy.co.uk] solving challenges: presenting for challenge: adding temporary record for zone \"co.uk.\": expected 1 zone, got 0 for co.uk.
I've just tried building with xcaddy rather than downloading from the caddy website and have the same result. It is still working normally for my .com domain, but this .co.uk one has issues

Removing the domain from the hosts file has resolved the issue, thanks for your help


Config file not in the designated place on MacOS

As mentioned, I'm on MacOS.
Expected:
what is shown in the help message when flavours is run on its own, that is:

The config file is by default ~/.config/flavours/config.toml,
The data file is by default ~/.local/share/flavours,

Got:

Both files are put in ~/Library/Application Support/flavours/

That wouldn't be a problem except for the fact that the help message is misleading and I cannot figure out how to change the config and data files to their rightful place.
Really liking the project apart from that, thanks!

Hey.
Flavours uses the dirs library for the default directories.
More specifically, config_dir for config.toml, and data_dir for the data files.
It seems that both default to ~/Library/Application Support/, which is kinda weird.
I'm not really sure how MacOS' home directories are structured, but is ~/Library/Preferences preferrable for configuration files? It seems dirs also includes preference_dir, which is exactly the same as config_dir, but with ~/Library/Preferences for MacOS instead.
I'll make this change and try to include some docs about the default directories on other OSes, if you think that solves the problem.
About using custom config or data directory paths, you can specify --config (or -c) and --directory (or -d) with any flavours command, for example flavours -c example.toml -d data apply.

Thanks for trying out flavours and for your feedback too <3

I'm not really sure how MacOS home directories are structured, but is ~/Library/Preferences preferrable for configuration files?

I personally have a .config and .local in my home, though I can't recall whether it was there before or if I made it this way. Many other CLI apps use this structure, including on MacOS (but many don't, unfortunately). For me MacOS counts as a *nix so the defaults (the Linux ones) are sensible. I've never seen an app use the Library/ paths for configs that I am expected to tailor to my needs, only for prewritten configs that aren't meant to be changed (like many things in MacOS!).

About using custom config or data directory paths, you can specify --config (or -c) and --directory (or -d) with any flavours command, for example flavours -c example.toml -d data apply.

Indeed, and I set an alias for flavours using those:
alias flavours="flavours -c ~/.config/flavours/config.toml -d ~/.local/share/flavours"

but I'd rather it be set with an environment variable.
I hope all this makes sense; thanks for the quick response. Really glad to contribute to making this even better.

Sure thing, i'll add env vars for these, then

Just implemented this. You can now use the environment variables FLAVOURS_DATA_DIRECTORY and FLAVOURS_CONFIG_FILE to set these.

Is it possible to test this change using cargo or would I have to wait until the next release? Sorry, I'm a bit new to this.

Is it possible to test this change using cargo or would I have to wait until the next release? Sorry, I'm a bit new to this.

Haha don't worry.
Yes, the way to test the changes before i release a new version is cloning the repository, cd'ing into it, and building with cargo, then running and testing to see if it all works.
You can easily build with cargo build. The resulting binary will be on target/debug/flavours.
You can also build & run with cargo run (to use flavours arguments, you can use it like  cargo run -- --version).
You can even run cargo install to have cargo install for your user (You would then need to add the cargo folder to your path, i'm not sure where it is on MacOS, but on linux it is ~/.cargo/bin)

Thanks, I'll try it out then!

Sorry for commenting on an old issue but on macos it seems like the custom schemes and templates folder don't work. Any chance at an env var for the config directory instead of file?


react native support

I guess there is currently no react native support. I'm wondering if some contributor has better idea how hard would it be to add support for react native?

Interested too

React Native would involve a major refactor with the UI. This is not planned in the near future.


Gateway does not include package name in URL

In an oversight, I hardcoded the package name into the gateway config, conflating namespace and package name.
Right now, a user can pick a combination of namespace and package name by changing the hostname and pick the action name through the path.
I propose a change where the the URL is composed of:
https://${namespace}.anywhere.run/${package}/${action}/…

This would be a breaking change, but one with low impact, as no one is using the Gateway'd URLs yet.

what about even decouple the version:
https://${namespace}.anywhere.run/${package}/${action}/${version}…

what about even decouple the version:
https://${namespace}.anywhere.run/${package}/${action}/${version}…

With an @?
https://${namespace}.anywhere.run/${package}/${action}@${version}…

With an @?
https://${namespace}.anywhere.run/${package}/${action}@${version}…

With an @?
https://${namespace}.anywhere.run/${package}/${action}@${version}…

well, that's we currently use for openwhisk actions...but the @ is a problem anyways in AWS routes...so maybe have the anywhere url be more flexible.

With an @?
https://${namespace}.anywhere.run/${package}/${action}@${version}…

well, that's we currently use for openwhisk actions...but the @ is a problem anyways in AWS routes...so maybe have the anywhere url be more flexible.

I can easily replace the @ in the URL with an _ or anything like that in VCL. In general, I like the URL format we have in OW, except for the long prefix.

I can easily replace the @ in the URL with an _ or anything like that in VCL. In general, I like the URL format we have in OW, except for the long prefix.


Please supply the ability to sort files by modified time asc/desc  in groups in source  control's Changes view when view as list

﹀ Changes               ⑩
| ﹀ A quarter ago
|       file1.html
| ﹀ Half an hour ago
|       file2.ts
|       file3.json
| ﹀ Two hours ago
|       file4.xml
|       file5.md
|       file6.properties
|       file7.scss
| ﹀ One day ago
|       file8
|       file9
|       file10

When mouse is over the file, we can get the exactly modified time information from tooltip.
We can make git operations on group, for example, stage group, stash group, or discard group, and so on.

Modification time is something not present in our API nor in Git's model. This will be very hard to achieve.


Enhancement: Protocols system.

Currently a standard protocol is hardcoded into the daemon startup by default.
Really we should have an entire Protocols resource that sets up standard light/temp/humidity schedules as predefined protocols. Then we can allow people to easily switch between protocols that are optimized for different plants.
Building on this, the protocols could be loaded into or loaded FROM https://www.protocols.io Then protocols can easily be shared between researchers with SS3 hardware.

Agreed, would still like to have a solution for when there isn't network support (including the backend if possible), an extra component to choose the protocol from disk/online would seem like a sensible thing to do here.

Completely agree. Can design the offline version first and then for an online export we can just translate from the offline version with adapter(s) for any online service for storing protocols via whatever apis they provide.

@ethanwillis
I've taken an initial measure in this direction by adding a rotatelog friendly logger to the python backend. The monitored/settings data is to be persisted both to disk and sent to api/database.


Support for npm/yarn linked package updates

Original Discussion: https://www.pika.dev/npm/snowpack/discuss/311
/cc @weyert, @FredKSchott
Developers will work on dependencies in separate repos, use npm link/yarn link to install them local to the Snowpack app,  and then want to see those changes updated live in their Snowpack app.
Right now, we don't support this, and you essentially need to restart the server to detect these changes.
Option 1

Run npm ls --link=true at dev start time, to get a list of all npm linked deps
If one of those linked directories is used in the application, start watching it for changes
on change to a watched, linked dependency, reinstall deps

Without some extra smarts around detecting whether imports/exports changed, we'll have to reinstall the entire set of dependencies for now.
Option 2
Could we treat linked packages as source code instead? As long as they are ESM, we could pass them through our source code build workflow instead of the package build workflow, and then no reinstalls needed. I think this would be worth trying first since it would be so much better if it works.
This would only need to run during dev. At build, the normal install should get the latest linked package changes.
We could use the same npm ls --link=true output scanner as option 1, to get the proper file path redirects.

Great project!
I want to contribute to snowpack for these open issues, but I notice that @pika/pack doesn't support watch mode for typescript building. Now I have to rebuild snowpack every time I change the source code.
Is there any plan to support watch mode for @pika/pack?

Thanks for your interest! There's an open issue for that support in the @pika/pack repo, but unfortunately a --watch command doesn't exist today.

Added in #470.
We ended up going with something like Option 1. We discovered that snowpack build actually works already with linked packages! It was just the dev server that didn’t rerun snowpack install whenever those files changed (you could stop the server and run snowpack dev --reload but that wasn’t obvious). So the first reason was that option 1 required the fewest changes to Snowpack itself.
The other reason is that while it’s tempting to treat linked packages like local source code, the reality is that it’s not local source code. There’s a reason why that code is imported through npm and not a part of the project itself. So there may be other complicated implications around treating that code as if it exists in an environment it doesn’t. It felt safer to treat packages like packages, even if they’re on your local filesystem.
We did minimize the impact of this change by only listening to local linked packages and not every dependency you import. We can possibly add that in the future, but before we do, we wanted to make sure that didn’t have performance implications.

I think that having picked option 1 over option 2 here makes a lot of sense except in the case of yarn workspaces, like what we're working through here: https://www.pika.dev/npm/snowpack/discuss/286
I think you're right that it's reasonable to expect code imported from npm / or via node_modules to be built already and not need further transformation, except for yarn workspaces, which use node_modules links to expose each of the workspace packages to the others. Developers are likely working in a workspace in order to make changes to multiple packages simultaneously and share code between packages without a build step being necessary, so if there is some way to go with Option 2 for packages inside a yarn workspace that'd be super duper!

For now, I think it's out of scope for us to support compiling packages from source and watching them for changes. But, you should be able to accomplish something very similar by just running your package build step in some sort of watch mode. In that world, the compiled package code is updated on every change, and then snowpack will detect the change and reinstall from the compiled code on every change.

I get that. I used a different workaround which is to put all my shared code in the web package that Snowpack is building and then source it from the api package (and/or the other ones) in my workspace. The other tools I'm using, like ts-node (and ts-node-dev) as well as VSCode are fine with the cross workspace imports going the other way, so the Snowpack built package inside the workspace just kind of sucks in all the code that it needs to require.
I totally understand why supporting cross-package builds is annoying. It violates the way that normal NPM packages are supposed to work, and in the general case I think it's fine to not build stuff from node_modules. It also probably poses significant challenges to implement internally. It's just that for workspaces, it sucks as a developer experience because now you need to run one watch process per package in the workspace. You pay a productivity penalty for trying to do things "right" and re-use code or properly factor things. It's back to the non-workspace developer experience of many repos with many build toolchains and many fiddly bits that all have to agree.
So I'd ask if you'd reconsider. If you zoom out one level, "compiling packages from source and watching them for changes" is kind of Snowpack's reason to exist (as a humble user who didn't build it of course). It's just that the package in question happens to be in a sibling folder instead of a nested folder.
Also, FWIW, this is possible to do with Webpack, you just have to deal with all the other bungus that Webpack makes you deal with and Snowpack doesn't.
Also, one final thing, because of Snowpack's terminal clearing / owning behaviour, it doesn't play nice with other tools sharing the same stdout, so it's kind of a weird experience to run it alongside other watcher tools like you might with concurrently.

Thanks for the extra context, I can definitely sympathize and want to solve for this use-case, but you rightfully pointed out that it would require a big change to how Snowpack works internally. I'll keep this in mind, and it could make sense as a major feature to tackle later on down the road.

I totally agree with all points raised by @airhorns.
I got super excited about Snowpack on my initial tests. Super fast DX, great work!
I was making a repository comparing its speed against alternatives like next.js and create-react-app to share the results on social media when I noticed the lack of monorepo support.
Unfortunately 99% of my projects use yarn workspaces and I'd lose the main benefit if I use snowpack.
Here's some problems I faced:

When changing the content of my-package/App, the page is doing a full reload
import MyPackage from 'my-package/App' works only if App file is a transpilled .js file; fails if it contains JSX code, for example, or if the extension is .jsx, .tsx, etc
Dev server fails to start if my-package name is something like @shared/my-package instead

@drwpow: It felt safer to treat packages like packages, even if they’re on your local filesystem

I totally understand the rationale here and it makes sense. But like @airhorns said, for Yarn Workspace projects we wanna treat them as source files, so the Option 2 makes more sense in that use case.
Maybe if we don't want enable that by default, maybe we could opt-in to that behavior with an option?

@FredKSchott: it would require a BIG change to how Snowpack works internally

Sad to read that :( I was hoping I could make a small patch on a fork to get that working.
But I really hope it gets tracked, I believe it's worth it.
Monorepos are becoming more common each day.

Just for anyone else reading, I do want to clarify that Snowpack does support monorepos: your project dependencies are getting properly loaded from the sibling directories without having to npm install them directly. (besides your 2. above, that could be a bug! @drwpow may be worth taking a look, if we're not clearing the cache after a dependency re-install)
If I'm understanding this thread right, what IS still missing is the ability to support a monorepo where parts of your application exist as seperate packages, outside of your main application, and you want to do active development on them without waiting for a re-install after every change. We should definitely support this! But the big problem is tat it messes with our idea of what's "source code" and what's "dependency code", which are handled in different ways today.

what IS still missing is the ability to support a monorepo where parts of your application exist as separate packages, outside of your main application, and you want to do active development on them without waiting for a re-install after every change

yes, exactly. for example, this folder structure:

/packages

core
components
web
mobile

The web uses both the core and components packages. There's active development on all three, so the expectation is that they're treated as source files with all the benefits like instant change.
When using create-react-app, for example, they also only have basic support for monorepo, but adding a few lines overriding their webpack config is enough to get the desired behavior:
https://github.com/devhubapp/devhub/blob/d1ee4eb517a1217c95a50d41603976cfa79c0e6e/packages/web/config-overrides.js#L11-L14

That would probably be the best that we could do: if you opt-in, we treat your linked, monorepo packages as if they were source files, using the exact same build as your application instead of any build defined in the package itself. That means we'd need a way to scan THEM for dependencies of their own, and somehow add those to the set of dependencies that you need to install to run your application.
Question: would it be acceptable to the source code inside those packages the same way that you treat your application source code? We could go a step further and use the actual source code within those packages instead of the built package themselves, although most packages don't define a "source code" entrypoint so you'd need to add that to your package.json.

@FredKSchott sounds great. Dunno if other people do it differently, but at least on my projects that's the case, the build step is only defined in the main package and the other packages are dumb source files. They may have different tsconfigs but that's already supported nowadays by snowpack ("run:tsc": "tsc -b" + adding references to the main tsconfig + composite": true to the other tsconfigs).

@FredKSchott

Question: would it be acceptable to the source code inside those packages the same way that you treat your application source code? We could go a step further and use the actual source code within those packages instead of the built package themselves, although most packages don't define a "source code" entrypoint so you'd need to add that to your package.json.

I think that Parcel.js v1 already does that. It looks for source attribute in package.json of the dependency and if it finds it then it compiles the source code of this dependency. 🙂 I already use this approach in my monorepos.
Related merged PR in Parcel.js: https://github.com/parcel-bundler/parcel/pull/1101

If someone could point me to which methods would need to be updated I'm willing to take a look.
I tried messing with onDepWatchEvent, mounted the workspace package so it would get to onWatchEvent, commented out config.exclude just in case, and some other changes but wasn't able to get the instant update behavior.

FWIW I'm using https://github.com/cleric-sh/repro 's method for my monorepo and it works.

Just chiming in here, above linked "source" field that is used in parcel is the same field microbundle to build from.
It seems to have become something of a standard among bundlers, would it be possible to evaluate this field, see if the file exists, and then build from it, and watch if possible?
That being said I have experienced issues in the past if the source code has custom syntax (i.e using symbols like @ to define the project root in a Webpack config) so it might be worth being able to disable?

Hi, I'll just take the liberty of pointing you to what I think is a problem with this feature: https://github.com/snowpackjs/snowpack/discussions/1167#discussioncomment-234008

I'm sorry for beating this horse, but after spending many hours debugging this (and diving into the Snowpack code), it seems that this feature was completely broken by #762, which includes this change to dev.ts.
commit 610fb9d28452bf24758387a00fe81a4ed103e503
Author: Drew Powers<EMAIL_ADDRESS>Date:   Thu Aug 13 15:53:52 2020 -0600

    Dev server improvements (#762)

    * Improve dev server output

    * fred attempt

    * fix bad spacing on http url line of header

    * add proxy message

    * add build watch message similar to dev

    * updates

    Co-authored-by: Fred K. Schott<EMAIL_ADDRESS>
diff --git a/packages/snowpack/src/commands/dev.ts b/packages/snowpack/src/commands/dev.ts
--- a/packages/snowpack/src/commands/dev.ts
+++ b/packages/snowpack/src/commands/dev.ts
@@ -954,3 +880,3 @@
   function onDepWatchEvent() {
-    reinstallDependencies().then(() => hmrEngine.broadcastMessage({type: 'reload'}));
+    hmrEngine.broadcastMessage({type: 'reload'});
   }

So this explains why one changes a dependency, the browser gets updated , but nothing really gets re-installed.
I can't tell from the commit message why this was removed (was it the "fred attempt"?).  Anyway I would think that it would be possible, looking at that part of the code, to extract only the dependency that needs to be reinstalled and perform that.  Is there a function that one can call that re-installs a single dependency? Then, presumably snowpack would start working again with npm link.  @FredKSchott  please advise.

Oh interesting! You're right, that was a regression incorrectly merged in that PR. Will create a prioritized issue to fix

@FredKSchott where can we follow the current discussions about treating linked packages as source files, specially in yarn workspace environment? (since this and some other related issues are closed)

I'm having this problem now. Is there a quick way to resolve this? For example, hard code my linked dependencies names in snowpack.config.js or somewhere

I'm having this problem now. Is there a quick way to resolve this? For example, hard code my linked dependencies names in snowpack.config.js or somewhere

In order to circumvent the issue, I made a symlink pointing to the linked dependency's location. In the snowpack config I added:
mount: {
	'linked-dependency': '/linked-dependency',
},
alias: {
		'linked-dependency': './linked-dependency',
},

Despite not working perfectly, I at least get hot-reloading for my linked dependency while developing.

@drwpow  please, can you reopen this ?
many people are blocked by this one

@drwpow  please, can you reopen this ?
many people are blocked by this one

While this is being worked on — just as a helpful tip for users of npm link dependency who are getting hard-cached results and unable to clear that easily:
npx snowpack dev --reload

That will at least restart your dev server and allow you to run with your latest built code. It's a mile away from HMR support so dev cycles are slow as molasses but at least I can get locally linked packages running by doing that.

While this is being worked on — just as a helpful tip for users of npm link dependency who are getting hard-cached results and unable to clear that easily:
npx snowpack dev --reload

That will at least restart your dev server and allow you to run with your latest built code. It's a mile away from HMR support so dev cycles are slow as molasses but at least I can get locally linked packages running by doing that.


Fix runtime crash

Fixes #2

/cc @danderson

PTAL @josharian @danderson

Cool. Will submit. @josharian can school us if we're wrong. 😂

I've been pondering this intermittently. I don't understand the handling of refs. It's not actual refcounting. It seems to me e.g. that the finalizer could set refs = 1 before setting a new finalizer, which could speed up things considerably. Is a bool enough?

Yeah, while writing docstrings explaining this interplay, I realized that this is not actually refcounting, but something akin to mark-and-sweep. As currently written, the weakref will need one GC cycle per call to Get before the interned value is actually deleted. So, it does still save memory, but the freeing schedule is unpredictable.
I think Josh is right that in the "re-set finalizer" case, we can set refs=1 to speed things up. In that case, a dangling Value will get collected at most 3 GC cycles after its last reference was dropped. I'll send a patch for same alongside the docstrings explaining this. I welcome a bikeshed for a new name for refs, since it's not a refcount.

It seems to me e.g. that the finalizer could set refs = 1 before setting a new finalizer, which could speed up things considerably.

Yeah, that's a good idea.

Is a bool enough?

Empirically, yes. PR coming.


Prevent overwriting map file if it was already created by this loop

Cheap hack, might be overloaded with the "{TerritoryType} - {PlaceName} - {LocationPlaceName}" pattern, but this prevents cases like l1f1 - Mor Dhona.png or z3o7 - Sigmascape V1.0.png from being overwritten by submaps with no LocationPlaceName, using a number in place of LocationPlaceName instead.
Maybe there's a better solution that uses only exd data? I thought about using the map ID but that sometimes doesn't match the TerritoryType.

Looks good, would it cause inconsistent filenames if some don't have any issues?
You could use map.Id I think which contains the map layer id included (eg: l1f1.00, l1f1.01 etc)
My own personal fix was:
var outPathSb = new StringBuilder("ui/map/");

// format: map/map.id.extension
outPathSb.AppendFormat("{0}/{1}{2}",
   map.Id.ToString().Split('/')[0],
   map.Id.ToString().Replace('/', '.'),
   FormatToExtension(format)
);

var outFile = new FileInfo(Path.Combine(_Realm.GameVersion, outPathSb.ToString()));

But this changes the filename completely (doesn't include the name)


Fix to include ng-included html

Unfortunately, each of the html files need to be listed separately.

Verified the fix.


Consistency

In
https://github.com/agershun/alasql/blob/master/src/50expression.js#L276
and
https://github.com/agershun/alasql/blob/master/src/50expression.js#L281
The core of the return statement is
 (a).valueOf()===(b.valueOf())

For consistency I have changed it to
 (a).valueOf()===(b).valueOf()

Please let me know if the original structure was intentional...

You are right.


Support for C++

Hey,
I absolutely love your tool and use it everyday!
Is it somehow possible (maybe with a setting or auto-recognize) to use #include instead of #import when coding C++ in Xcode?

@FramusRock good idea thanks, are you using .cpp and/or .mm files for c++? btw, you're welcome to submit a pull request if you want to implement it.

In .mm files #import works just fine. I'm talking about .cpp in which #include is a must. Auto-Importer works just fine there, it should just write #include instead of #import ;)

I looked into it a little, maybe you can help me out, so that I can make an appropriate pull request.
In LAFIDESourceCodeEditor.m, there is this:

(NSString *)importStatementFor:(NSString *)header {
return [NSString stringWithFormat:@"#import "%@"", header];
}

How can I find out if the current file that this header belongs to is a CPP file or ending in .cpp?

I'm still interested in it, could you give me a hint how I can achieve it, please?

hey @FramusRock I spent some time trying to figure out how to get the filename from current editor but still no luck. Another approach would be to get the first existing import/include line on the file and use that to decide if you should be using #import or #include

hey @lucholaf , thank you. I also spent some time on it, but also didn't have any luck getting it right.
What you're saying sounds like a good idea. I'll have a try and report back.

@FramusRock +1

I made it! Pull request sent!


Emphasize non-Oracle OpenJDK distributions in Getting Started guide

As discussed with @cpojer - we should stop directing people to a JDK download site where it is seemingly impossible to fetch a JDK8 install, and even if it were possible would be subject to sub-optimal update and license policies.
Commit message with resasoning for the specific change and a link for more context follows:
Markdown: emphasize non-Oracle OpenJDK distribution
As of April 2019 Oracle restricts it's non-OpenJDK distributions to
non-commercial use, and the Oracle OpenJDK builds will not be updated
promptly for security patches
non-Oracle OpenJDK versions will still be distributed as users would expect
(open-source and unrestricted commercial use, plus regular updates), so the
getting started guide should emphasize non-Oracle OpenJDK versions
Of those, the AdoptOpenJDK project appears to hae solid delivery for macOS
via brew and for non-system-packager Linux, so it is linked first
Context: https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244

:zap: :+1:  what's the lag on publish to https://facebook.github.io/react-native/docs/getting-started so I can make sure I didn't bust the page's style?

I think that by default this change will only be visible when the version is changed to 0.60 - I think that to modify the one current out you'd have to also change the generated one

Okay - I'll check then - thanks

Just verified in the RN0.60 preview #967 that my changes did not break the fancy/cool OS-selection tabs etc - this change appears to be good to go / no touch-ups needed


docs: move adapter docs to site

This builds off the docs PRs from @dummdidumm: https://github.com/sveltejs/kit/pull/8501 and https://github.com/sveltejs/kit/pull/8500
I ignored all the types errors in the docs. I don't know if there's a better way to set them up

I like this! I think I would rename the first doc to "fundamentals", but that's all. Let's wait on more opinions before doing this.

I think this is a good approach; will close #8500 and #8501 and do a proper edit of this branch tomorrow

FYI:

Bad link: adapters#supported-environments-node-js in 20-core-concepts/20-load.md
--
11:18:32.447 | Bad link: adapters#supported-environments-platform-specific-context in 25-build-and-deploy/10-building-your-app.md
11:18:32.460 | Bad link: adapters#supported-environments-platform-specific-context in types/ambient.d.ts

Really like the structure! Wondering if "static site generation" is the right title since you also can build SPAs with it (a regular point of confusion). Maybe it's even benefitial to have a dedicated page for that? Could be something along the lines of "spas are x, you can create them like y, they are supported by various adapters. If the whole app is an spa, you can use the static adapter, see link for more info (links back to static site generation).

Re SPAs — https://github.com/sveltejs/kit/pull/8531#discussion_r1080553330 (you can build an 'SPA' with any adapter, since it describes rendering rather than static-ness). I could be persuaded that we need a new page for SPAs, distinct from build & deploy, as long as it includes 'why you probably shouldn't build an SPA', but i think we can tackle that separately

I don't like how tall this section is relative to the others — it feels disproportionate. But I don't think there's an easy solution within the current structure so I guess we go along with it for now


start

@rultor release, tag is 0.0.1

@rultor release, tag is 0.0.1

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.1

@yegor256 Done! FYI, the full log is here (took me 9min)

@rultor release, tag is 0.0.2

@rultor release, tag is 0.0.2

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.2

@yegor256 Oops, I failed. You can see the full log here (spent 8min)
Need to get 29.6 MB of archives.
After this operation, 187 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_18.x nodistro/main amd64 nodejs amd64 18.20.3-1nodesource1 [29.6 MB]
\u001b[91mdebconf: delaying package configuration, since apt-utils is not installed
\u001b[0mFetched 29.6 MB in 1s (51.3 MB/s)
Selecting previously unselected package nodejs.

(Reading database ...

Preparing to unpack .../nodejs_18.20.3-1nodesource1_amd64.deb ...

Unpacking nodejs (18.20.3-1nodesource1) ...

Setting up nodejs (18.20.3-1nodesource1) ...

added 17 packages in 2s

3 packages are looking for funding
  run `npm fund` for details
\u001b[91mnpm notice
npm notice New minor version of npm available! 10.7.0 -> 10.8.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.0
npm notice To update run: npm install -g<EMAIL_ADDRESS>npm notice
\u001b[0m ---> Removed intermediate container 4636a2e118f7
 ---> 3a91708e2c7d
Step 6/13 : RUN gem install judges:0.0.31   && curl -sL -o /usr/local/Saxon.jar     https://repo.maven.apache.org/maven2/net/sf/saxon/Saxon-HE/9.8.0-5/Saxon-HE-9.8.0-5.jar
 ---> Running in 89100e43cb92
Successfully installed nokogiri-1.16.5-x86_64-linux
Successfully installed loog-0.5.1
Successfully installed gli-2.21.1
Successfully installed factbase-0.0.30
Successfully installed backtrace-0.4.0
Successfully installed judges-0.0.31
6 gems installed
 ---> Removed intermediate container 89100e43cb92
 ---> 48bf722bf148
Step 7/13 : WORKDIR /home
 ---> Running in ea1aad07c3b5
 ---> Removed intermediate container ea1aad07c3b5
 ---> 58060bf5048d
Step 8/13 : COPY Makefile /home
 ---> 38ddb26023d1
Step 9/13 : COPY entry.sh /home
 ---> e42ebaff3b43
Step 10/13 : COPY sass /home/sass
 ---> 5e2a18f1c202
Step 11/13 : COPY xsl /home/xsl
 ---> 20875d3aa01e
Step 12/13 : RUN make --directory=/home --no-silent
 ---> Running in adc673b7ea3f
make: Entering directory '/home'
make: Leaving directory '/home'
 ---> Removed intermediate container adc673b7ea3f
 ---> f74982a7718c
Step 13/13 : ENTRYPOINT ["/home/entry.sh", "/home"]
 ---> Running in f757c573beca
 ---> Removed intermediate container f757c573beca
 ---> 2a5fd07d609e
Successfully built 2a5fd07d609e
bash: line 1: sass: command not found
make: *** [Makefile:59: target/css/main.css] Error 127
container 5b6b1e5eba0e2ab1bb4476893a1c48d2713a821997dba4aa5a4b42d55f96cdfb is dead
Wed May 22 00:22:42 UTC 2024


What values would you suggest to match randomColor.js?

Hi, this looks like a cool library - I found it after searching for Ruby alternatives to randomColour.js, and think it could just hit the spot for what I need.. although I'm looking for a little guidance.
The readme says I can specify the saturation and lightness I want for generating the colours, and looking at what the randomColour.js readme says:

...randomColor produces bright colors with a reasonably high saturation.

...suggests I should be able to set similar results from this library if I use the correct values - but I'm not sure which values I should be using when I instantiate the object.
I'm very new to playing with colours, so am actually a little confused by some of the terms used, so apologies if I'm asking silly questions.
Thank you.

The values go from 0 to 1, so the highest saturation is 1.0. It's worth learning more about colorspaces, especially HSV and HSL. In HSV, if you set :value to 1.0 you may still get a dark color (e.g. pure blue #0000ff is not light). So, I recommend using HSL with :lightness.

Hi, thank you for your help. I spent a bit of time playing with it last night, and was quite happy with the following:
ColorGenerator.new(saturation: 0.75, lightness: 0.4)


Minimum Physical Distance Between AZs within a  Region

Hello,
I have a client who has minimum requirements for distance between data centers. What is the minimum distance between data centers (particularly US East)? This would be helpful info to have in the article by Region.
Thanks,
Michael

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9ef6739c-50e6-e80b-cfc1-4d7d5b5d35e8
Version Independent ID: 72c38d9b-b8b1-92d4-3937-12de08c35918
Content: Azure Services that support Availability Zones
Content Source: articles/availability-zones/az-region.md
Service: azure
GitHub Login: @prsandhu
Microsoft Alias: prsandhu

@mhmoore12 -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

There is less than 2ms latency between zones.  We are working on a new content as we will not be able to share the distance between AZs within a region, and have already incorporated this as part of the update.
I hope the above has answered your question. At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@MonikaReddy-MSFT Hi Monika - thanks for the reply.  I was referring to physical distance (e.g., miles). My client requires at least 25 miles between data centers.

@MonikaReddy-MSFT
Hello,
Any additional update / reconsideration for opening again per my clarification?
Thanks.

Hi @MonikaChaudhary25 - bumping this thread again. Should I raise a new issue or submit an Azure support ticket?

@mhmoore12 - Sorry, I have totally missed your messages. Thanks for bringing this up again. Let me investigate on it and get back to you shortly.

@MonikaReddy-MSFT
No worries - when do you think you'll be able to get an answer on this?
Thanks,
Michael

@MonikaReddy-MSFT Hi - following up on this.


Version 0.22 in stream pageInfoparameter is ignored when getting timelines

In the latest version 0.22
public func stream(_ stream: PostTootStreams, _ pageInfo: PagedInfo? = nil) throws -> AsyncStream<[Post]>

has been updated to use the new logic of using newHolder?.pageInfo when calling getHomeTimeline.
I am passing in a PageInfo instance and this is not being processed.
it could be that I am doing something wrong, but I am trying to show the toots after a specific id, which I set as minId in the PagedInfo that I then pass when I call the stream when I pass in the PagedInfo as a variable.  The value I pass in is ignored.
Example lines I am using
    let pagingDetails = PagedInfo(minId: "109840050111793127")

    Task {
        for await posts in try await tootManager.currentClient.data.stream(streamType, pagingDetails) {

Hi - I’ll take a look at this over the next day, I’ve got a suspicion it’s an issue where the PagedInfo being given, isn’t being used in the first call that’s made.
The expected behaviour is we use the first PagedInfo that’s provided and then set this based on the data returned by the API afterwards.
I’m also wondering if I need to clarify the function to just take a minID rather than the PagedInfo as we’re only using that in the refresh call.

Hi @garryeves  - I've a PR up now (#93 ) - which addresses this. If you get a chance to check this before @kkostov reviews, I'd love to hear whether it fixes the issues you've been experiencing or not. It really should do 👍

Thanks.  This is now working really well.


[FEATURE] Identify and manage orphaned lvols and raid bdevs if the associated Volume resources are not existing

Is your feature request related to a problem? Please describe (👍 if you like this request)
If the Volume resources are deleted, but their associated lvols and raid bdevs still exist (e.g. a user adds a disk containing these items), Longhorn should be capable of detecting these orphaned items and creating the corresponding Orphan resources which will help user manage them.
Describe the solution you'd like
A clear and concise description of what you want to happen
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@derekbit but why those lvol and raid bdev will still exist? I thought they will be deleted accordingly.

For example, there is a spdk volume with 3 replicas. In case one of the nodes is somehow down, user removes as well as the replica. After the nodes comes back or the disk is moved to another node, the orphaned lvol still stays on the disk and is out of Longhorn's control.

Verified failed on master-head (longhorn-manager ) following the test steps:

Create a cluster for spdk following https://longhorn.io/docs/1.5.0/spdk/quick-start/ using machines with extra disk e.g. c5d.2xlarge
Add /dev/nvme1n1 block disk to each Longhorn node
Create a SPDK volume with 2 replicas
Power down the non-attached node.
Delete the replica that is not on the attached node
Power up the non-attached node => The node becomes Unschedulable, and all disks on that node become Unschedulable with size 0 Gi with error messages:

$ kubectl logs longhorn-manager-4kb9n -n longhorn-system | grep spdk
time="2023-06-06T09:29:43Z" level=error msg="Failed to sync Longhorn setting longhorn-system/spdk" controller=longhorn-setting error="failed to sync setting for longhorn-system/spdk: cannot apply spdk setting to Longhorn workloads when there are attached volumes" node=ip-10-0-1-109

An orphan resource will be created and records the deleted replica. => There's no orphan resource being created

Also, Create and attach a spdk volume, and then randomly delete a replica, there will be no replica rebuilding happening, the volume will stay in degraded state forever.
cc @derekbit

Tested again on master-head (longhorn-manager 8bbf501) following the steps below, the behavior is still not quite normal:

Create a cluster following https://longhorn.io/docs/1.5.0/spdk/quick-start/ using machines with extra disk e.g. c5d.2xlarge
Enable SPDK Data Engine
Add /dev/nvme1n1 block disk to each Longhorn node and wait them becoming Schedulable
Not create any volume, reboot a node directly
After reboot, the block disk /dev/nvme1n1 on that node becomes Unschedulable with size 0Gi

Here is some suspicious logs:
$ kubectl logs longhorn-manager-khjk2 -n longhorn-system | grep /dev
time="2023-06-09T02:52:27Z" level=debug msg="Failed to get device type of /dev/nvme1n1" controller=longhorn-setting error="failed to get device path in [/proc/mounts /host/proc/1/mounts]: cannot find device path of /dev/nvme1n1" node=ip-10-0-1-11
time="2023-06-09T02:52:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"ip-10-0-1-11\", UID:\"fcb59be7-8f83-4791-9a70-bd2d6dceabcc\", APIVersion:\"longhorn.io/v1beta2\", ResourceVersion:\"3434\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Disk disk-2(/dev/nvme1n1) on node ip-10-0-1-11 is not ready: failed to get disk config: error: disk service client is nil"
time="2023-06-09T02:52:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"ip-10-0-1-11\", UID:\"fcb59be7-8f83-4791-9a70-bd2d6dceabcc\", APIVersion:\"longhorn.io/v1beta2\", ResourceVersion:\"3434\", FieldPath:\"\"}): type: 'Warning' reason: 'Schedulable' the disk disk-2(/dev/nvme1n1) on the node ip-10-0-1-11 is not ready"

$ kubectl logs instance-manager-6d772c3fc26e7756e595b051d22da005 -n longhorn-system | grep disk-2
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Getting disk info" diskName=disk-2 diskPath=/dev/nvme1n1 diskType=block
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Getting disk info" diskName=disk-2
[2023-06-09 02:52:57.694800] bdev.c:7867:spdk_bdev_open_ext: *NOTICE*: Currently unable to find bdev with name: disk-2
[2023-06-09 02:52:57.694854] bdev_rpc.c: 867:rpc_bdev_get_bdevs: *ERROR*: bdev 'disk-2' does not exist
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=error msg="Failed to get disk info" diskName=disk-2 error="rpc error: code = NotFound desc = cannot find AIO bdev with name disk-2"
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Creating disk" blockSize=4096 diskName=disk-2 diskPath=/dev/nvme1n1 diskType=block
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Creating disk" blockSize=4096 diskName=disk-2 diskPath=/dev/nvme1n1
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Creating AIO bdev disk-2 with block size 4096" blockSize=4096 diskName=disk-2 diskPath=/dev/nvme1n1
[longhorn-instance-manager] time="2023-06-09T02:52:57Z" level=info msg="Creating lvstore disk-2" blockSize=4096 diskName=disk-2 diskPath=/dev/nvme1n1
[longhorn-instance-manager] time="2023-06-09T02:53:13Z" level=info msg="Created disk" blockSize=4096 diskName=disk-2 diskPath=/dev/nvme1n1
[longhorn-instance-manager] time="2023-06-09T02:53:13Z" level=info msg="Getting disk info" diskName=disk-2 diskPath=/dev/nvme1n1 diskType=block
[longhorn-instance-manager] time="2023-06-09T02:53:13Z" level=info msg="Getting disk info" diskName=disk-2
[longhorn-instance-manager] time="2023-06-09T02:53:13Z" level=info msg="Got disk info" diskName=disk-2
[longhorn-instance-manager] time="2023-06-09T02:53:13Z" level=info msg="Listing disk replica instances" diskName=disk-2 diskType=block
[longhorn-instance-manager] time="2023-06-09T02:53:27Z" level=info msg="Getting disk info" diskName=disk-2 diskPath=/dev/nvme1n1 diskType=block
[longhorn-instance-manager] time="2023-06-09T02:53:27Z" level=info msg="Getting disk info" diskName=disk-2
[longhorn-instance-manager] time="2023-06-09T02:53:27Z" level=info msg="Got disk info" diskName=disk-2
[longhorn-instance-manager] time="2023-06-09T02:53:27Z" level=info msg="Getting disk info" diskName=disk-2 diskPath=/dev/nvme1n1 diskType=block

cc @derekbit

Does /dev/nvme1n1 exist after reboot?

Does /dev/nvme1n1 exist after reboot?

Yes.
# fdisk -l | grep nvme1n1
Disk /dev/nvme1n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And if I manually remove the Unschedulable one and re-add /dev/nvme1n1 again, it works without problems.

How did you create /dev/nvme1n1?

It's a local nvme storage attached to c5d instance by default.

I'll try to test in other environment later.

I can check it first and will update it later.

Probably because there are 2 different storage on the machine and the device path will change randomly after reboot:
Disk /dev/nvme1n1: 186.26 GiB,<PHONE_NUMBER>00 bytes, 390625000 sectors
Disk model: Amazon EC2 NVMe Instance Storage
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme2n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

I'll change to test on other environment then.

Probably because there are 2 different storage on the machine and the device path will change randomly after reboot

Interesting.
If the change doesn't happen, the issue is not seen.
So, the question should be how to make the disk naming perisstent.

https://serverfault.com/questions/1051326/what-is-the-proper-way-to-configure-etc-fstab-on-an-ec2-instance

Tested again on Equinix following the test steps.
Everything works as expected except the last step:

Go to the instance-manage pod and execute the command go-spdk-helper lvol get. The replica should be deleted.

Got a command not found error:
# kubectl exec -it instance-manager-4ca1b1a1d37d72361bb7226bab957fcf -n longhorn-system -- /bin/sh
sh-4.4# go-spdk-helper lvol get
sh: go-spdk-helper: command not found

cc @derekbit

Can you find go-spdk-helper in the pod?

Does /dev/nvme1n1 exist after reboot?

Yes.
# fdisk -l | grep nvme1n1
Disk /dev/nvme1n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And if I manually remove the Unschedulable one and re-add /dev/nvme1n1 again, it works without problems.

How did you create /dev/nvme1n1?

It's a local nvme storage attached to c5d instance by default.

@yangchiu Can you help open a ticket for tracking the issue?
I will improve it. Currently, the workaround is removing the disk and adding it back.
Thank you.

go-spdk-helper

Just found I forgot to add go-spdk-helper (debugging too) after introducing multi-stage build...

Verified passed on v1.5.x-head (longhorn manager 42bb998, longhorn-instance-manager 3fc14de) following the test steps.


Project health clarification

I've noticed that some projects have 0.0% for issues or security.
Is this due to a lack of historical data in which to determine health? If so, then what would be an alternative way to display this info as the lack of evidence seems to imply a project is doing poorly which is not the case. And likewise, a lack of evidence should not necessarily be justification to make the project look good either.
Thoughts?

Yes, thank you @stevespringett - I agree, neither 0% nor 100% convey what we want to say. I suppose one could ask, which project would you prefer, one that had three security issues, all promptly fixed, or one that had no security issues?


Image setting medium_max_width, medium_max_height wrong result (?)

medium_max_width is set to 1280, medium_max_height is set to 720 and then to 0. Uploaded image has a width of 1080 x 720 so, what is not I expected ;-)

I'm sorry, I don't quite understand your description; could you elaborate? What do you mean that medium_max_height is set to "720 and then to 0"? What is the value when you upload the image?
Also, can you say what the size of the original image was, and what was the size you expected for the medium image?

I wrote a long text ... just to understand I should read better AND I need something different :-P
What I expect or like to have is a result of 1280 x 853 pixel :-)
The limitations of e.g. linked images in forums are usually in width not height.
It's technically fine as it is but It seems I need a medium_min_width :-P
I would suggest when e.g. medium_max_height is set to "0" then only medium_max_width is the constraint and it will result in a max width of e.g. 1280px.

OK, I understand now. Yes, we support setting the width to 0 (we do that for small_max_width by default) but, having recently messed around that code, I remember noticing that setting the height to 0 was not fully supported.
Actually, I think it might already work if you use GD instead of Imagick for image resizing. If you want to give it a try, set imagick in the full settings to 0, medium_max_width to 1280 and medium_max_height to 0, and see if that does what you want.
Either way, I'll try to implement a comprehensive fix this weekend.

Checked with GD and you are right that's what I want :-D


guidance

How do you use this?
Where do the audio tracks go?

Huawei's Ascend910NPU can be used to achieve training and reasoning. The reasoning function separates a song into two parts: vocals and non-vocals.

ok thats great, do I just put the audio track file anywhere?


macOS fullscreen causes clear color to show strange pattern

I noticed a strange artifact when pressing the "fullscreen" button (the green one, third from the left) on my application on macOS: the clear color has this pattern. I tried it on the vkcube app (precompiled, bundled with the lunarg sdk), and it does the same. When an external display is attached, it works correctly (both on the internal and external displays).
Expected behavior: solid background color
Observed behavior: sawtooth pattern

System info:
Vulkan SDK versions tested: <IP_ADDRESS> and 1.3.280.1
Apple MacBook Air - Retina, 13-inch, 2020
1.1 GHz Dual-Core Intel Core i3
Intel Iris Plus Graphics 1536 MB
8 GB 3733 MHz LPDDR4X
macOS Ventura 13.3.1

I'm not able to replicate this on a 2017 MacBook Pro with Intel Quad Core & Intel HD 630 GPU on macOS Ventura 13.6.6 (and no external monitor attached). The background color is smooth in fullscreen.
And if the behaviour changes depending on whether you have an external monitor attached, I don't know if there is anything we can do within MoltenVK to make any difference. It seems like something to do with your underlying graphics driver or hardware.
Do you see anything like this with other applications?

This test application I wrote exhibits the same behavior (see attached). Though I don't manually manage the graphics drivers in this environment, I can upgrade to macOS Sonoma 14.4.1 to see if any of the changes there fix it.

Do you see anything like this with other applications?

This test application I wrote exhibits the same behavior

I meant do you see this behaviour when you go full-screen on non-MoltenVK applications, such as native Metal games, or even desktop apps.

I see what you mean now: I had never seen it before. Interestingly, I just built and ran this Metal test app from Apple (https://developer.apple.com/documentation/metal/using_a_render_pipeline_to_render_primitives), and it has the same issue. This can certainly be closed as a Metal/driver bug. Sorry to bother you :)

No worries about the false alarm. And thanks for being diligent about testing alternatives.


Add "Use Head" to post macro.

Please add use head to the post macro (like the first/second trinkets and rings). Engineers have the ability to create helms that shoot bullets.
Thank you.

Done - will be in the 1.4 build


Sync repo and wiki

This project code repository was the initial source of the tutorial. Midway through development it was copied by @mcgredonps into the project wiki (https://github.com/open-dis/dis-tutorial/wiki).
The problem is that having the tutorial docs in two places causes some confusion for readers and maintainers about which is the source of the tutorial. I can only assume the docs are out of sync already.
We need to decide which to keep (code or wiki) and then turn off (or remove) the other.

@brutzman @terry-norbraten are either of you familiar with the plan for the dis-tutorial repository? It appears like @mcgredonps was the primary author (based on number of commits) but there were a number of contributions from others.
I see that there is a tutorial written within the git repo markdown pages and another in the git repo wiki pages.  Was it intended to be the same tutorial? Is one version newer than the other? From the dates of changes it's not obvious to me, the two copies appear to be authored roughly in parallel between 2017 and 2019. But there are significant differences between the two copies.
The git repo markdown pages were authored between Jan 2, 2017 and Jan 9, 2019 .
Whereas the wiki pages were authored between Oct 28, 2017 and March 12, 2019
My thought is it would be nice if could consolidate the two tutorials (if indeed they were intended to be one tutorial), but I don't have enough background to understand if we should straight up delete one copy and keep the other or how to proceed.

Leif, I agree the tutorial needs to be consolidated, clean up, and updated. As to when we’ll be able to do that from the NPS MOVES side is undetermined unless we happen to get specific funding for that task.
I know that Dr. Brutzman is looking at getting DIS 8 implemented and running sometime in the near future. That would most certainly call for an updated/current tutorial section.
r/ Terry

On Feb 23, 2023, at 09:23, Leif Gruenwoldt @.***> wrote:
@brutzman https://github.com/brutzman @terry-norbraten https://github.com/terry-norbraten are either of you familiar with the plan for the dis-tutorial repository? It appears like @mcgredonps https://github.com/mcgredonps was the primary author (based on number of commits) but there were a number of contributions from others.
I see that there is a tutorial written within the git repo markdown pages and another in the git repo wiki pages. Was it intended to be the same tutorial? Is one version newer than the other? From the dates of changes it's not obvious to me, the two copies appear to be authored roughly in parallel between 2017 and 2019. But there are significant differences between the two copies.
The git repo markdown pages were authored between Jan 2, 2017 and Jan 9, 2019 .
Whereas the wiki pages were authored between Oct 28, 2017 and March 12, 2019
My thought is it would be nice if could consolidate the two tutorials (if indeed they were intended to be one tutorial), but I don't have enough background to understand if we should straight up delete one copy and keep the other or how to proceed.
—
Reply to this email directly, view it on GitHub https://github.com/open-dis/dis-tutorial/issues/21#issuecomment-1442157510, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQTJOP3K7M4SCGHCGPMWMDWY6MK5ANCNFSM5MRC6TIA.
You are receiving this because you were mentioned.

There is a lot of good information in the tutorial, but it never reached fruition as a useful (recommendable) document.
We have no funding or expert availability to pursue the tutorial this year, though we do aspire to work on DIS 8.
If we might structure the tutorial information in an XML document that corresponded to PDUs and abstract classes, plus other things, then we would be able to integrate it into our code autogeneration as Javadoc, python comments, C++/C# documentation, etc.  I've done this kind of thing before to good effect.
Divide-and-conquer suggestion: why don't we integrate pertinent parts directly into the XML that captures DIS7, meaning that much of it could eventually port to DIS8 autogeneration when we get there.  Specifically, changing the @comment attribute (found in current XML) into @description (terse form) and @explanation (tutorial detail) would put a lot of the material into context, providing a good start on such refactoring.

https://github.com/open-dis/opendis7-source-generator/tree/master/xml/dis_7_2012

This is a good project for someone that could encourage a number of contributions.  I'd expect that the SISO working group would let us apply blocks of prose freely since we would not be violating IEEE copyright.


Delta memory usage in memory profiler

In the memory profiler, would it make sense to subtract off the initial memory usage when the context manager is initialized?
In the below screenshot, I'm running the profiler after doing other things in the notebook, and I'm only interested in the delta memory usage (~120 MB here), similar to the delta memory usage reported by ipython_memwatcher.

This seems useful to me.  An alternative (though not necessarily better) approach would be to keep the numbers as they are, but change the default plotting range.


Is there any possibility to use PNChart with IB?

I add this amazing chart into my application through codes,and I also find that PNChart inherits from UIView,so I decide to have a try for implementing this with storyboard.I drag a UIView to my view and change the class from UIView to PNPieChart,but I find that 'items' property is 'readonly',it only can be set in initWithFrame: items: method.
Is any solution for using PNChart with storyboard or IB?Or there are some solutions already in it but I did't find them?
Thanks.

if you use a xib or storyboard for this chartView, the initWithFrame will not be called ,it will replaced by initWithCoder,you can change the chart source code to support xib or storyboard.


module 'kaolin._C' has no attribute 'render'

Hi, thanks for your great works frist.
I face the problem when I run the notebook in differential rendering. The error is "module 'kaolin._C' has no attribute 'render'" in kaolin/render/mesh/rasterization.py. I check that I have _C.so but it seems not include render function. I totally follow the installation guidlines in the documentation.

I run
python setup.py develop
again and this issue is solved. It is strange the compliation seems not complete when I first run this command.


The inner object of the tagged object should be used for instantiating the EncryptedValue

.getObject() is missing.
https://github.com/bcgit/bc-java/blob/e04ee7fd0aba1427f300b2675adc9b016d854c05/core/src/main/java/org/bouncycastle/asn1/cmp/CertifiedKeyPair.java#L40

Thanks for the report, now fixed as part of #397


⚠ Avatar API Endpoint has degraded performance

In dc57783, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1942 ms

Resolved: Avatar API Endpoint performance has improved in 165cfc5 after 12 minutes.


Fix importing historical emissions sectors

When importing sectors for historical emissions also consider the data source.
Requires re-running: bundle exec rake historical_emissions:import

@weberjavi ping.


Scenario.restrospective() does not receive keyword arguments of Scenario.estimate()

Summary
Scenario.restrospective() uses Scenario.estimate() internally, but this does not receive keyword arguments of Scenario.estimate(). This method is for retrospecvtive analysis, compare the scenario with paramerter estimation in all phases and the scenario in which parameters were fixed from user-defined date.
(Optional) Related classes

covsirphy.Scenario

Codes and outputs:
import covsirphy as cs
# Dataset preparation
data_loader = cs.DataLoader("input")
jhu_data = data_loader.jhu()
population_data = data_loader.population()
# Scenario analysis
snl = Scenario(jhu_data, population_data, "Japan")
snl.trend(show_figure=False)
# Retrospective analysis
snl.retrospective("01May2020", model=cs.SIRF, control="Main", target="Retrospective", timeout=60)

This code does not raise any errors, but ignore timeout argument.
Environment

CovsirPhy version: 2.10.0-mu
Python version; 3.8
Installation: pipenv
System: WSL (Ubuntu)

This bug will be fixed in version 2.10.0-nu.


[BEAM-12665] Add option in ReadAll Transforms to add filename to the output

Adds option to return filename when reading files with ReadAll transforms. It does the same as ReadFromTextWithFilename but works with All transforms (i.e., don't need be at the start of the pipeline).
It also allows other ReadAll transforms like AvroIO, ParquetIO, TFRecordIO.
The reason behind adding this feature is I have gotten use case from Beam users that needed to read files in parallel but be able to aggregate file by file after some transforms. This is not currently available and would require complex workarounds with FileSystems.

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.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem

R: @chamikaramj

I modified the first commit to improve performance. I was checking for with_context for every row and we only need to check once.

@ihji are you able to take a look? Cham is OOO.

Hi! Is there any action needed from my side? Thanks

Ack. Sorry about the delay here. Looking into this.

Also, please add a Jira.

Modifying files as requested.
Upon testing, I cannot see any major impact after running 3 pipelines with and without the change, nor in Run Time or Wall Time.
Tests were done by reading 80GB of data with 20 default Dataflow workers

Run Python PreCommit

It looks the PreCommit is failing due to the general tests failing, not due to this PR.
This PR errors: https://ci-beam.apache.org/job/beam_PreCommit_Python_Phrase/2716/testReport/
Main Tests errors: https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/lastCompletedBuild/testReport/
Both are apache_beam.examples.streaming_wordcount_it_test.StreamingWordCountIT.test_streaming_wordcount_it. I see other Python PRs with the same issue.

this LGTM.
Why did we change with_context to with_filename? Maybe context could return an object with further context? (e.g. partition, line name, etc)

this LGTM.
Why did we change with_context to with_filename? Maybe context could return an object with further context? (e.g. partition, line name, etc)

_ReadRange currently only contains the FileMetadata of the object and the OffsetRange. FileMetadata has the filename and the size, but I don't fully see the use of adding the size as an output, since you'd probably can get the same using ReadableFiles without the need of outputting row by row and then aggregating. LMKWYT.
The other things you mention would be helpful, but (afaik) not possible with the current implementation of _ReadRange. Maybe a future PR?
Thanks for having a look, Pablo!

Run Python PreCommit

@InigoSJ has addressed the yield issue. I'll merge now
Noting that broken tests on precommit are also broken on master


This field is not set to a valid category group.

Describe the bug
I select the Single Cat field type and the Category
Steps to reproduce
Just regular use... matter of fact it was working until I've update Craft.

Craft CMS version
4.4.9
Plugin version
3.0.1
Multi-site?
No
Additional context
No response

Fixed in 3.0.2


High Values of Z_L and Z_ab

Hi,
Thanks for open-sourcing your work, I have been trying to use CMC on my custom toy dataset which has 2 views (Image (3D), Sensor view (3D)) I'm able to run the model successfully but the Z for view 1 and view 2 is being set to<PHONE_NUMBER>95712.
I made sure to use L2 norm around the final features from each of the alexnet halfs but I'm really not sure why the Z values are being initialized to such a high value. I kept the nce_m,nce_k and nce_t to the same as that of your code.
Please, can you help me with the same? Thank you

Hi,
How large is your dataset? Z is a Monte Carlo estimate of the partition function of the softmax. It should be proportional to your dataset.
Do you run into similar problem with ImageNet data or just your own data?

Hi,
Thanks for your reply I understand the fact that it is a Monte Carlo estimate, my dataset has 700 images. I didn't run into the same issues in imagenet.

Given what you provided, I cannot have a better guess about the issue.
Probably you do not need NCE as your dataset is very small. Maybe you can just try softmax instead?

I am basically trying to understand the convergence of nce to softmax and experimenting the same with different samples sizes. What do you think is the appropriate sample size for the convergence of nce gradients to softmax gradients.

NCE is an approximation for high dimensional softmax.
One possible issue with NCE for less data is that, when you sample large amount of negatives (assume if you are doing k with 4096) and you only have 700 images, the true "positive" will be counted as negative by several times. This means the network is misleadingly to classify positive samples as negatives with a significant weight, which is wrong and will overwhelmed the correct gradient.


TypeError: _obtain_input_shape() got an unexpected keyword argument 'require_flatten'

when i check the model graph, this error occurs:
TypeError: _obtain_input_shape() got an unexpected keyword argument 'require_flatten'
can u give me some advice?

This code was designed in keras 2.2.0.
pip install keras==2.2.0

the reason is keras give up the file in keras . you can set up .py file with the code from :https://github.com/keras-team/keras-applications/blob/e52c477/keras_applications/imagenet_utils.py#L235-L331,and import .py into your main .


Updated Skype for Business information

Included the link to the the plugin that is developed by Mattermost itself instead of korgz.

Summary

Ticket Link

Looks good to me, editorially. Adding @jasonblais as I know he was working on this recently and he may have some feedback. Thanks!


Add a different authentication mechanism for S3 bucket

https://github.com/cloudskiff/driftctl/pull/671
Is this the good place in the doc to add this content ?

I would have put it under /providers/aws/authentication right before the Terraform custom role section with this explanation:
Custom credentials to read a state on an S3 backend
If you want to use a different set of AWS credentials to read your state on S3, you can override each specific AWS environment variable with the DCTL_S3_ prefix. The purpose here is to have the choice to read a state in a different region than your infrastructure. Please don't forget to use your usual AWS credentials to read the resources of your actual infrastructure.
# Export a dedicated AWS named profile (or any other AWS environment variables) to read your state in your S3 backend
$ export DCTL_S3_PROFILE="s3reader"
# Export the usual driftctl AWS named profile
$ export AWS_PROFILE="driftctlrole"
$ driftctl scan --from tfstate+s3://mybucket/terraform.tfstate

# You can also use a specific region to authenticate to the S3 bucket
$ DCTL_S3_REGION=us-east-1 driftctl scan --from tfstate+s3://mybucket/terraform.tfstate

I agree, that was my first thought, i'm on it.


Include schema for user redirection information exchanged between DE …

…<-> DO

That is only for DE->DO.
We need one for DO->DE with the result as well

Do you think it is neccessary to separate in request/response?.

Well the response needs:

Status (Agree, Disagree, Error)
ErrorList (optional)
So yes :)


Layout bugs out on medium sized screens on specific days

Some dates that this happens on:
Tues. Aug 24, Wed. Aug 25, Thurs. Aug 19

Seems to be related with the length of Events

Setting a fixed width for Events fixes it, but why is it allowed to expand past 100%?

Probably because of the Zoom link? Did you give it word-break: break-word;?

Giving flex: none; to .sidebar fixes it

I think it's because the long event description on that day stretches .content, which squishes the sidebar
I probably accidentally introduced this when I moved the sidebar itself into a child .sidebar-content; there's a flex: none; on .sidebar-content (formerly just .sidebar) which is why this didn't happen before, but when I separated the two, I forgot to move flex: none; from .sidebar-content to .sidebar


spotube

Add spotube to apps:

wait for nixpkgs, see https://github.com/NixOS/nixpkgs/issues/200120
make your own derivation, see https://github.com/NixOS/nixpkgs/issues/200120#issuecomment-1902995697:{ stdenv, fetchurl, lib, makeWrapper, undmg }:

  stdenv.mkDerivation rec {
    pname = "spotube";
    version = "3.4.0";
    appname = "Spotube";
    filename = "Spotube-macos-universal";
    meta = with lib; {
      description =
        "An open source, cross-platform Spotify client compatible across multiple platforms
          utilizing Spotify's data API and YouTube (or Piped.video or JioSaavn) as an audio source,
          eliminating the need for Spotify Premium";
      homepage = "https://github.com/KRTirtho/spotube";
      downloadPage = "https://github.com/KRTirtho/spotube/releases";
      license = licenses.bsd3;
    };

    src = fetchurl {
      url =
        "https://github.com/KRTirtho/spotube/releases/download/v${version}/${filename}.dmg";
      hash = "sha256-dif2ec37QL9FVPGgqqvtB2zRX6P3NCth5FFnpASR/As=";
    };

    icon = fetchurl {
      url = "https://raw.githubusercontent.com/KRTirtho/spotube/nightly/assets/spotube-logo.png";
      hash = "sha256-gyzP3ynzuZFN0osmEAjwGfYmbfVxE9Nm2fLJ8q8G6BE=";
    };

    sourceRoot = "${appname}.app";
    nativeBuildInputs = [ makeWrapper undmg ];
    installPhase = ''
      runHook preInstall
      mkdir -p $out/{Applications/${appname}.app,bin}
      cp -R . $out/Applications/${appname}.app
      makeWrapper $out/Applications/${appname}.app/Contents/MacOS/${appname} $out/bin/${pname}
      runHook postInstall
    '';
  }

I don't think I'll add this now


Fixes #3762

Fixes issue #3762. cargo test and cargo bench should no longer compile binaries with required features that have not been selected.

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks!

:pushpin: Commit 5f0d8a5 has been approved by alexcrichton

:hourglass: Testing commit 5f0d8a5 with merge e017a9f...

This is going to fail. I ran tests locally before rebasing and it turns out resolve.features() no longer returns an Option. I'm running tests locally again now. I'll push a new commit after.

@bors: r+

:pushpin: Commit fbc00c6 has been approved by alexcrichton

:hourglass: Testing commit fbc00c6 with merge 79c743a...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 79c743a764ac39f054743a67ab4622e85f0be5b3 to master...


tootle: add platforms.linux to meta.platforms

Description of changes
Set meta.platforms.
Motivation: Ensure this builds on the aarch64 builders.
Things done

Built on platform(s)

[x] x86_64-linux
[x] 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
[ ] 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.

Hi! The change looks okay, just want to ask do you use this package? This package is really not lucky and was broke by at least three Vala updates (6b7a314be64fa1429775bc92ae1792bb613f7a9f, 32daca577ff8fb90dee238b3ff3073852413d55b, bde65d2eea592dc1860347e5df74127e262e7844) and it is broke by Vala updates again (in the GNOME 43 PR), the error is the same as bde65d2eea592dc1860347e5df74127e262e7844 so likely because some changes are now backported to Vala 0.48 and 0.54 and pinning Vala no longer works (log) and we will probably mark it as broken very soon (85d5df55cb9c16ac66866024353b067441b7452e) since the upstream was archived.


feat: authenticator

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

46 of 59 (77.97%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 81.448%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Tempest/Framework/Testing/Http/TestResponseHelper.php
1
14
7.14%

Totals

Change from base Build<PHONE_NUMBER>4:
-0.02%

Covered Lines:
5975

Relevant Lines:
7336

💛  - Coveralls

After this PR, we'll look into an authorization API (preferably with user roles built-in). All front-end stuff and user-management is left alone for now.

I think this is great, there shouldn't need to be more built-in (besides authorization) 👍
However, I wouldn't let Tempest take care of the user model itself and the migration, I would rather have Tempest use an interface that has to be implemented in userland

However, I wouldn't let Tempest take care of the user model itself and the migration, I would rather have Tempest use an interface that has to be implemented in userland

Yeah, that's a fair point.

While I want the user model to be configurable, I do want to provide a default implementation — I might reconsider that though.
Also, I'm ok with "the user" being tied to the database, I don't really care about other ways of storing user data for now.

Looking at the current code, it's unclear to me—is it possible to ignore the provided migration? Or would you recommend to add another one that would run after it and modify the table as we see fit?
That'd be one reason I was suggesting not to provide a default model/migration, but it seems low enough friction

I'd love to see this use a repository to decouple retrieving the user details. If it were me personally, my criteria would be for this to be decoupled so that it could work entirely outside the framework. I understand that's a bit of an extreme view, though. 🙂

Looking at the current code, it's unclear to me—is it possible to ignore the provided migration? Or would you recommend to add another one that would run after it and modify the table as we see fit?

Right now it's not possible, but this is something I already planned on figuring out before merging this PR :)

I understand that's a bit of an extreme view, though. 🙂

Yes, not within my scope for now :)

We have to think about the people storing passwords in the filesystem, @brendt!

I thought about it: they are free to roll their own auth layer separate from Tempest's default implementation 👍

How to deal with this circular dependency: auth requires http because of session management, but http also requires auth because of the middleware.
Since this auth layer is only concerned with http authentication, would it make sense to keep it all within the same component?
I know @aidan-casey will tell me otherwise :)

Is the circular dependency itself a technical issue? If not, I think keeping the tempest/auth package separate is a good idea

Apparently it is, composer can't deal with it (at least not in our CI setup). There's no issue in this branch because I haven't added the circular dependency yet, but we had the same issue once before between core and event-bus.
Maybe there's a solution for it, I'll do some digging.

@brendt - I haven't looked through the code yet, but probably I would have said use a driver/repository for storing the auth data. 🙈 🙃

I solved the issue, it was pretty straight forward: just need to hook into the Kernel::BOOTED event and add the middleware like so

Ok so, this branch contains so much code that I want to merge it rather sooner than later. I'm still going to write an implementation for revokePermission, but after that I plan on merging it.


NPM ReadMe Link Issue & ReadMe Image Issue?

1: The Npm Readme Contains a link to documentation and a guide that would link to some Really shady websites like shady enough for chrome to block the website completely.
While clicking on the links in Github Readme Doesn't do so Which raises some questions for me
Links =>  http://solaris.codes/projects/erelajs/docs/gettingstarted.html
2: https://i.imgur.com/wWlwXgm.png
As you see there's a bugged out image in readme which links to https://camo.githubusercontent.com/ba3ee39a0f38136b4ba395b0b0ee6a616e24a1853049ca6504f23600bae5f7f1/68747470733a2f2f736f6c617269732e636f6465732f70726f6a656374732f6572656c616a732f696d616765732f7472616e73706172656e745f6c6f676f2e706e67
So yeah Hope you guys fix it

@Strandxo

NPM package has been updated 👍🏼


Kong performance test,Https response time is unstable.why???

Additional Details & Logs
Kong version :0.14.1
Kong debug-level startup : kong start / error level
Kong configuration :
https://github.com/Kong/kong/issues/4017
Help,Https response time is unstable, http is normal,WHY??

Regular response time rises every 20 seconds, after which the response time drops to normal, repeate..

Hi,
Github issues should be reserved for bugs with Kong. Also, please don't cross post to here and the forums. Since you've also opened up https://discuss.konghq.com/t/kong-performance-test-https-response-time-is-unstable-why/2344, I will close this now.

HELP…


Does this project support wordpress.com?

I was looking for a python wrapper that will allow posting comments to wordpress.com without the full authentication to make posts.  Does this project support that?

Yes.


refactor: Improved overall readability of the scrapers

This PR is my attempt at cleaning up the GitHub & GitLab scraper code. I did the following across both of them:

Renamed "unclear" variables to more accurate names.

mrs -> mergeRequests
p -> project
etc.

Added comments where I could.

All the functions should have a comment to help explain a bit more of what they do.

Reformatted various functions.

Some function declarations were over 100 characters long on a single line so I formatted them a bit better.

Closing this out as the work we're doing on PR #194 will make this work moot.


a:input and a:hidden, without name and for, don't take value from ViewData

The issue seems to be when a prefix is used on ViewData.TemplateInfo.HtmlFieldPrefix. Apparently, ViewDataDictionary.Eval() only works with relative names, and not full names.
It's possible that also a:check-box does not take checked from ViewData.

Worked around the prefix issue by creating *ForModel variants.
Fixed on ´a:input´, ´a:hidden´, ´a:check-box´ and ´a:radio-button´. ´a:textarea´ and ´a:select´ did not require changes.


Show errors in current buffer window instead of the global quickfix window

Since formatting works only on the current buffer, it could be argued that formatting errors should be displayed in the current buffer window instead of the global quickfix window. (Because the global quickfix window may already be displaying other information, e.g. project-wide search results, that is lost when formatting errors are loaded into it.)

You're absolutely right. Thanks! ✨


HELP! - EXCESSIVE (!) data usage

K-9 mail has suddenly started using a colossal amount of mobile data and managed to use up ALL of my 1GB monthly allowance in 3 days flat! It never did this before - my average for a whole month has been 250MB across all the apps on my phone. I even set the data settings for the app under system settings to not use mobile data then went out this morning and it had used another 100MB anyway when I got back - even tho I've only had 40 emails! I have 4 accounts, all IMAP (one Apple @mac and 3 gmail) set to sync the last 2 months and only 32k of each email. What on earth is going on? I'm gonna have to ditch the app if I can't resolve this issue.
Latest v5.010 on a Samsung Galaxy A3FU

Please use the mailing list for support requests.

?? was just following orders...
On the Play website  at https://play.google.com/store/apps/details?id=com.fsck.k9&hl=en it says
If you're having trouble with K-9, please report a bug at https://github.com/k9mail/k-9 …..
Maybe this needs updating?
Kind regards
Barry Woodward
London
On 13 Jun 2016, at 12:44, cketti<EMAIL_ADDRESS>wrote:

Please use the mailing list for support requests.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Well, it probably is a bug in K-9 Mail. But without more information we're never going to find it. From experience I can say that it's unlikely someone who reads the bug tracker will have the energy to work with you to narrow down what could trigger the bug. A lot more people read the mailing list and someone might be able to help.


Implementation of test-power-complex for Float.java

Implementation of a floating number raised to a complex power, corresponding to the test test_power_complex in test_float.py for type Float.java.

I do not how the build failed, I ran the test again on my laptop using python setup.py test -s tests.datatypes.test_float it is not showing any errors. Am I doing something wrong with the testing?

Hm, looks like it's failing for this case:
E     >>> x = 2.3456
E     >>> y = 3.14159265j
E     >>> x **= y
E     >>> x
E   - (-0.8946025309573877+0.44686274358536093j)
E   ?                                      ^^^
E   + (-0.8946025309573877+0.446862743585361j)
E   ?

Maybe it's a matter of precision?
This will need some more digging...

If it's purely a rounding issue, can add to the substitutions, like:
https://github.com/pybee/voc/blob/da6dca3efe5501427c358a87a9166ce886050f94/tests/datatypes/test_complex.py#L50-L60

@cflee On adding the following lines to test_float.py:
class BinaryFloatOperationTests(BinaryOperationTestCase, TranspileTestCase):
    data_type = 'float'

    substitutions = {
        "(-0.8946025309573877+0.446862743585361j)": [
            "(-0.8946025309573877+0.44686274358536093j)"
        ]
    }
    ...........................

the test test_float.BinaryFloatOperationTests.test_modulo_int seems to fail. The error seems to lie here:
  >>> x = -3.14159
  >>> y = -5
  >>> x % y
- -3.1415900000000008
+ -3.14159

Should I add the substitution to test_complex.py rather than test_float.py but we are testing float operation, right?

Look inside the tests/utils.py file, there are existing substitutions including that one for pi. Those lines are replacing the entire substitutions dict, but you can just copy/add to the substitutions instead. There is at least one other place in the test suite which does that, if you get your text editor to search for it.

@cflee Done. Checks passed.

@eliasdorneles Can you please review this PR? Thanks. :smile:


Wrapdb entrie that point to external git repos

We (CC: @tp-m @MathieuDuponchelle) maintain a bunch of meson ports of projects that don't seem to be interested in the ports in gstreamer. We haven't submitted them to wrapdb because it would double our maintenance burden.
Maybe we can have a way to add wrapdb entries that point to a tag in an external git repository? Would also be a good way to transition people from wrapdb to upstream if/when build files get merged upstream.
https://gitlab.freedesktop.org/gstreamer/meson-ports (actually we need to prune libsrtp from there and probably add opus)

Does the extra maintenance burden come from getting them on to wrapdb or the continued maintenance after that? One would think that once the wraps are there other people could contribute so it would reduce the burden. Or do you need them to be in some special format or with features that would not go well with wrapdb inclusion?

Multiple reasons:

wrapdb can only contain meson build files, not changes to existing source files which are almost always needed to fix bugs when trying to make a 1-1 and cross-platform port (most wrapdb entries are partial/incomplete ports)

We maintain two types of branches: (a) ff-only fixed branches on top of releases (b) constantly-rebased branches on top of the upstream master branch. This makes it easier to keep things up-to-date.

Maintaining each branch is usually just git push, submission to wrapdb is a different set of steps which is extra work, especially when trying to bump to a new release

most wrapdb entries are partial/incomplete ports

This is true, but we really should try to do better here. In the optimal case upstream should be able to just take the wrapdb files, put them in their repo and be 95% done. It's a lot of work, though.

Yes, and sometimes even if you do the work, upstream is just not interested, or is hostile, or it takes them a long time to merge it. Usually takes months, and in that time if you can't even publish the port somewhere for usage, it's a complete non-starter.


Wikidata How To

Hi,
I have downloaded wdtk-client-0.8.0.jar from github, but I did not find the "rdf_dumps.ini" file to run java -jar wdtk-client-0.8.0-SNAPSHOT.jar --config rdf_dumps.ini Could you please share the config file? @daniilsorokin

Hi,
I have downloaded wdtk-client-0.8.0.jar from github, but I did not find the "rdf_dumps.ini" file to run java -jar wdtk-client-0.8.0-SNAPSHOT.jar --config rdf_dumps.ini Could you please share the config file?

I am having the same issue

Uploaded: https://github.com/UKPLab/coling2018-graph-neural-networks-question-answering/blob/master/rdf_dumps.ini


Auth when reading deleted records

This addresses #819.

Codecov Report
Attention: Patch coverage is 58.82353% with 7 lines in your changes missing coverage. Please review.

Project coverage is 98.64%. Comparing base (d667090) to head (0d52596).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

src/handlers/records-read.ts
56.25%
7 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #820      +/-   ##
==========================================
- Coverage   98.72%   98.64%   -0.08%
==========================================
  Files          74       74
  Lines       11508    11526      +18
  Branches     1661     1663       +2
==========================================
+ Hits        11361    11370       +9
- Misses        141      150       +9
  Partials        6        6

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


[Gem Farm] - Can't stack more than one gem - Error 0x159

Hello everyone,
I'm able to move all the gems I want to the vault, but when I try to "Begin Stacking" I get this error message:
Uncaught (in promise) Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x159
at Connection.sendEncodedTransaction (index.browser.esm.js?64b9:7055:1)
at async Connection.sendRawTransaction (index.browser.esm.js?64b9:7014:1)
at async sendAndConfirmRawTransaction (index.browser.esm.js?725d:8977:1)
at async Provider.send (provider.js?877c:82:1)
at async Object.rpc [as stake] (rpc.js?7ffe:9:1)
All works well If I only stack 1 Gem.
Anyone else having an issue like this one ?
Thanks!

yes i had similar issue

@jdomingospt @loktioncode did you guys find a solution?

What do you mean by "stacking"?


FilePicker v8 using Web instead of SPA AAD Authentication

Describe the bug
In the setup instructions, it says to create a Single-page application registry. We've already integrated the v7 file picker with a Web AAD Application for authentication and would like to re-use this with the new file picker, however we end up with authentication errors if we use the token generated with a Web authentication flow.
Is it possible to use a Web access token to instantiate the v8 file picker?
To Reproduce
Steps to reproduce the behavior:

Create a Web authentication AAD app.
Instantiate the v8 file picker, as in the examples in this repo.
Use an access token generated from a Web AAD application when the file picker sends the authentication message.

Expected behavior
The picker should work using either SPA or Web AAD authentication?
Screenshots

The picker should work with any valid MSAL setup that can get tokens for SharePoint. The instructions are specific to getting the samples setup. You can see how we are configuring MSAL in the sample. So our samples likely won't work with other configurations - your application should be able to use whatever it needs.

@patrick-rodgers thanks for the response. So the issue doesn't seem to be related to the application type.
Next question:
Our current setup is using the OAuth 2.0 with manually crafted http requests (we're not using MSAL or ADAL). The token we receive through this process works with FilePicker v7 but not with FilePicker v8. Any idea why that would be the case?


Rebase on FreeBSD 13.1

Hi!
I have several laptops, most notably a StarLab coreboot laptop that won't boot with the default 13.0 image supplied on the website but when I rebuilt Nomad based on 13.1 they all run just fine. (Issues not specific to Nomad but FreeBSD as well.)
Updating Nomad on the USB stick directly can be tricky and it seems people have varying success.
Perhaps providing an official 13.1 image on the website would be a good idea? (At least for people to test.)
Thanks

… won't boot with the default 13.0 image supplied on the website but when I rebuilt Nomad based on 13.1 they all run just fine. (Issues not specific to Nomad but FreeBSD as well.) …

https://forum.nomadbsd.org/t/nomadbsd-1-4-not-booting-on-some-hardware/689/13?u=grahamperrin includes a link to a relevant release note.

Additional reasons to rebase on 13.1:

UFS: soft update journaling, fsck_ffs (8) - NomadBSD Development - NomadBSD Forum, in particular FreeBSD bug 256746 – fsck_ffs completely broken for background fsck 4
259090 – UFS: bad file descriptor: soft update journaling can not be enabled on some FreeBSD-provided disk images – failed to write updated cg

Context, my NomadBSD drive temporarily connected to a computer running FreeBSD 14.0-CURRENT:
root@mowa219-gjp4-8570p-freebsd:~ # lsblk da3
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
da3              2:58   29G MBR                                               - -
  <FREE>         -:-   993K -                                                 - -
  da3s1          2:59   40M efi                                               - -
  da3s2          2:60  3.5G BSD                                               - -
    <FREE>       -:-   1.0M -                                                 - -
    da3s2a       2:62  3.5G freebsd-ufs                         label/nomadroot -
  da3s3          2:61   25G BSD                                               - -
    <FREE>       -:-   1.0M -                                                 - -
    da3s3a       2:63   25G freebsd-ufs                         label/nomaddata /tmp/nomaddata
  <FREE>         -:-   506K -                                                 - -
root@mowa219-gjp4-8570p-freebsd:~ # fstyp /dev/da3s2a
ufs
root@mowa219-gjp4-8570p-freebsd:~ # tunefs -j enable /dev/da3s2a
Using inode 14 in cg 0 for 29032448 byte journal
tunefs: Failed to write updated cg: Bad file descriptor
tunefs: soft updates journaling cannot be enabled
root@mowa219-gjp4-8570p-freebsd:~ #

Is there a need for help testing a new 13.1 image?
If so is there a specific area or feature to focus on?

We're almost ready for a RC1. Please be patient for another few days.

@andreas-jonsson, please see #128

Time to close?


add_fd?

I wanted to add a callback for when a file descriptor has data to read.
I see equivalents for add_check and add_idle, but don't see one for add_fd unless I'm missing it.

Thank you so much!

It has now been added to master. Additionally I've added a demo to fltkhs-demos (https://github.com/deech/fltkhs-demos/blob/master/src/Examples/fd-example.hs). Could you verify and close the issue if it works? Thanks!

FYI this demo is the equivalent of howto-add_fd-and-popen.cxx in the Examples directory of FLTK 1.3.3 source distribution.

I'll take a look when I have the chance this week. Thanks again!

If this is fixed would you mind closing?

Sure thing -- thanks again


[FLINK-9685] Adding support hostname-substitution for security.kerberos login.principal

What is the purpose of the change
Flink should support hostname-substitution for security.kerberos.login.principal. So it will be easier to deploy flink to cluster. Instead of setting different principal on every node, we can have the same principal headless_user/HOSTNAME@DOMAIN .
Brief change log

Replace canonical hostname in kerberos login principal security configuration. If UnknownHostException occurs - do it the old way (before this changes).

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: don't know
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not documented

@flinkbot approve description

It looks as if we need to come to a conclusion on the JIRA ticket first. Closing this PR until this is done.