Better defaults and conventions

Currently, if either .md or .html file is inside the content without a front-matter, it ends up in an error. I suggest in order to provide a better and more natural and intuitive experience:

add new command that adds title, and date with current date.
in the absence of front matter, allow the usage of documents without a date, and using the file name as title (with a default formatter for it in config.toml - a title cased converting loose [-_] into spaces would be a reasonable default).
in the absence of front matter on .html/.htm files do not process them, instead just copy them - this allows nice colocation, but behavior similar to static, which is nicer is many cases, where you want custom html files - but creating a directory tree for just one or two html files that don't need processing is painful.
also adding an option in the front matter, on whether or not regular .md, and .html with front-matter should be processed or not, might be worth giving a though to. (In case of no processing, the front-matter can be stripped).

I like how simple gutenberg is compared to something like hugo that became a monster over time with  documentation that'll take hours to even glance through. Would love to see gutenberg remain with current simplicity.

Thanks! Regarding your comments:

new command: this is a rabbit hole I don't really want to go into, touch or cp existing-post.md is simpler. Most of my usage of Gutenberg is not for blogs so I don't care for the date for example.
I would argue the filename is very rarely the title of the document,  I'm using the filename for the url mostly and even then I often manually change the url in the front-matter if it would be too long as a filename or want some fancy url scheme
there's already assets colocation, do you mean being able to have some random HTML files anywhere in the content folder instead?
can you detail the usecase?

@Keats, after reading your comments, how about these:

I do like your approach to not go down the new rabbit hole. However, the problem I see is without date, building ends up in an error. So, alternatively, how about just using the file creation date to fill up the date automatically, when there is no front-matter?
My rationale with filename is just to have something reasonably ok to fallback on, when there isn't one. (I didn't see if it compiles without one, if it does, then that's fine too)
Assets colocation - yes. Currently, unprocessed html files work when they go into static. However, it's easier to maintain in the content, instead of creating a directory tree for just one or few files. (As long as it doesn't become confusing) - So, as long as the default is to process them with the same pipeline, it shouldn't be confusing. However, a front-matter config to allow bypassing that would make this possibly optionally.
Above. Just for html. I don't suppose it makes a lot of sense of md.

However, the problem I see is without date, building ends up in an error.

It shouldn't be the case, most of my pages don't have dates: https://github.com/Keats/gutenberg/blob/master/docs/content/documentation/content/linking.md for example
Do you have a reproduction for that?

I didn't see if it compiles without one, if it does, then that's fine too

It does, there is no required field in the front matter, a +++\n+++ is a valid one

Assets colocation - yes. Currently, unprocessed html files work when they go into static. However, it's easier to maintain it in the content directory, instead of creating a directory tree for just one or few files. (As long as it doesn't become confusing) - So, as long as the default is to process them with the same pipeline, it shouldn't be confusing. However, a front-matter config to allow bypassing that would make this possible optionally.

That would be a HTML file that doesn't use Tera at all then? I don't really see the use vs just having a almost empty .md file in content that has template = "my.html" in the front-matter so it fits better in the rest of the site or as co-located assets if you really want your .html to be in the content folder (still requires a .md file though)

It does, there is no required field in the front matter, a +++\n+++ is a valid one

Sorry, my bad! It just doesn't compile without a front matter, an empty one at the least. Is there any specific reason why no front-matter isn't allowed? I suppose it would be nicer, if it's just simple touch x.md, and have it just work, without adding an empty front matter.

Is there any specific reason why no front-matter isn't allowed?

Precisely to avoid having some random .md files being rendered without explicitely asking for it. I sometimes mv or touch a file at the wrong location and I like that it just doesn't silently try to render it

Ok, thanks. I suppose, you do prefer to keep it separate in favor of clean separation, against the small convenience of colocating without adding an extra md file. Closing.


chore(husky): added branch validation on checkout

closes #85

Pull Request Test Coverage Report for Build 327433730

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 326743714:
0.0%

Covered Lines:
36

Relevant Lines:
36

💛  - Coveralls


Starter-template CSS not working

The styling in starter-template.css does not appear to be applying to the body content. Works when previewing on local machine, but does not work on live site.

Edited order of stylesheets and issue was fixed


Consider unifying return values of CreateAsync and UpdateAsync

For the next set of breaking changes I'd like to propose that CreateAsync and UpdateAsync both should return a SuccessResponse instead of string and SuccessResponse.
If the idea gets accepted I could provide a pull request.

Geez. Great point. I don't know why I originally built CreateAsync to only return the Id string. I will take a look at resolving.

I have committed a fix. https://github.com/developerforce/Force.com-Toolkit-for-NET/commit/f0873750aef2f704b868eb8b3c216027be98d6f8
Although minor, it is a breaking change. We'll have to think through the strategy for release.


1D Voronoi leads to Qhull internal error

julia> Voronoi(rand(1,8))
QH6005 qhull internal error (qh_determinate): only implemented for dimension >= 2

While executing:  | qhull v Qbb Qc Qz
Options selected for Qhull 2020.2.r 2021/09/27:
  run-id 950638957  voronoi  Qbbound-last  Qcoplanar-keep  Qz-infinity-point
  _pre-merge  _zero-centrum  Qinterior-keep  Pgood  _max-width 0.79
  Error-roundoff 8e-016  _one-merge 4e-015  Visible-distance 1.6e-015
  U-max-coplanar 1.6e-015  Width-outside 3.2e-015  _wide-facet 9.6e-015
  _maxoutside 4.8e-015
Last point added to hull was p0.
Qhull has finished constructing the hull.

At error exit:

Voronoi diagram by the convex hull of 9 points in 2-d:

  Number of Voronoi regions and at-infinity: 9
  Number of Voronoi vertices: 7

Statistics for:  | qhull v Qbb Qc Qz

  Number of points processed: 9
  Number of hyperplanes created: 16
  Number of facets in hull: 9
  Number of distance tests for qhull: 30
  CPU seconds to compute hull (after input):  0

A Qhull internal error has occurred.  Please send the input and output to
<EMAIL_ADDRESS>If you can duplicate the error with logging ('T4z'), please
include the log file.
QH6187 qhull internal error (qh_errexit): either error while reporting error QH6005, or qh.NOerrexit not cleared after setjmp(). Exit program with error status 5

[process exited with code 5 (0x00000005)]

I think this is, because qhull itself does not work for 1-d inputs.
Should add a check for 1-D input in the constructor, of course.
qhull manual:
"For convex hulls and halfspace intersections, Qhull may be used for 2-d up to 8-d. For Voronoi diagrams and Delaunay triangulations, Qhull may be used for 2-d up to 7-d."

Added assert for 1d input in master.

Wonderful, thanks for looking at this!

(Although I think, technically, a plain error would be more Julian since @asserts can be removed depending on compiler settings)

ah, yes, error is better. I will change it.
Have been writing mostly c++ lately.


Question: Persisting data example /  best practice.

Love what you are doing! react-first-router makes so much sense!
Question about how you see making API requests to save data in relation to this project. For example, if I have a USER_PROFILE: { path: '/profile', ... } route, I can fetch the data for the existing profile via the route's thunk per your examples if I don't already have it.  But when the user makes a change and clicks 'SAVE'... now what?  Do you feel this should be handled by a route
( something like: SAVE_PROFILE:  { path: '/profile/save', ... }  ) or would we fall back to using "traditional" thunk based actions.  I can see advantages / disadvantages to both, so I was curious about your (and other's) opinions on the best way to handle pushing data to the server rather than fetching it.

Glad to hear it.
U know what, I'm starting to consider having not route "routes" in the map lol, based on how popular it's been. Nobody wants to go back to the old way, myself included.
So basically we could pair "follow-up" thunks to "setup" action types without changing the URL, i.e. without a path option.
We are gonna do this!

Also u could have a URL like /saving that only shows for a second or two while the post is performed.
I actually think that's a fine option. Now that the URL is so easy why not change it temporarily like gmail flashs the document.title (is the browser tab title) when u have a pending chat message.

Yeah, one of my thoughts (the 2nd option in my firs post) was that transient route that exists basically for dispatching thunks then switch back to the initial URL. The possible downsides is what happens if you visit that URL directly? What happens if you hit the back button after the save completes? If you are using server side rendering and request that page directly?
The argument for doing saves with "normal" thunk actions is that you aren't really navigating anywhere in a lot of cases (though when you are doing create type stuff, you may well be) so dispatching an "inline" action makes sense, but then you have fetching async stuff in one place (routes) and saving async stuff in another place.  Not an awful fate, but having your data operations in one place certainly is nice to have.
Another, possibly terrible,  idea is adding an optional flag or something to a route.  So I could dispatch: {type: USER, payload: { id: 'veddermatic' }, flag: 'save' } and have my thunk do something different based on that. Although I don't see what that really gets me over transient routes other than consolidating the code into one place in the routes map.

In tradition server side apps u could post to them and u have to validate the data anyway. The case is still true today. You gotta do validation in ur thunks, again in the server, etc. So it shouldn't matter that u URL-ize the same action. I didn't quite get what u meant by flag: save.
As far as flags, the idea I have is simply if there is no path on the route object, it's a pathless route.

I guess the thought behind flags on a route are akin to HTTP verbs.  So you can have the same route  actions do different things:
{type: PROFILE}, // show the profile, fetch if needed
{type: PROFILE, flag: 'post'}, // persist the profile to the server
{type: PROFILE, flag: 'delete'}, // remove the profile

So to the view-handling code, it's all just PROFILE, but your route handler can do different things inside the thunk based on that flag.
Again, I don't think this is a good idea at this point, just an idea on how to handle non-fetch data while keeping like code near.
re: Path-less routes -- are they just traditional thunk actions by another name?

Almost. They come with the added benefit of not requiring the thunk to dispatch an initial action, and the structure of the routesMap.
Regarding the verbs thing, yea prolly not the best idea to introduce now. But there are possibilities for more dynamic routes. For example: if you use a regex in your path with parentheses we capture an unnamed variable at payload.0 and payload.1 etc. we could let you use $1 and $2 in the type key to create multiple action types per route.
It's also probably unnecessary complexity, but I have a feeling something will eventually emerge for individual routes with further dynamic capabilities.

i'm not sure what the point of this is and it seems very convoulted.
when data is going to be saved based on user interaction, simply call the action creator that was added to the components props by react-redux's connect and handle it any way you handled it before, using your preferred side-effect-handling redux middleware of choice (thunk, promise, saga, observable, loop etc).
why would you ever want a route for that? just because you can have a thunk in the routeMap?

 Having the URL in the routesMap is important though--now you don't need to have 2 separate ways of dealing with what's pretty much the same thing. So that means more consistent organization.
That said, seeing the URL change for a second is just like another loading... spinner. So it's not unhelpful. In addition, analytics tools operate based on history changes--so it could lead to some nice automation there. I wouldn't completely discount it.

Why is that? I have to dispatch an action to save things anyway. I can either dispatch an action that goes through the route reducer and performs a side-effect in a thunk of a route that i have to specify for that case - or perform a side effect via redux middleware directly.
This is not the same thing. Previously, all sideeffects and async actions were located in redux middleware and executed in response to dispatched actions. Now, some additional side-effects might be tacked onto route definitions. That doesn't sound like something i'd want to make the default case.

"view redux middleware DIRECTLY" is in fact less direct. There's more work, as it doesnt do the setup action automatically, and there's no formalized pattern on organizing your thunks, just files filled with them.
With this, you just dispatch a sync action, and know exactly where to add a thunk when it becomes important.
Lots of people want to be able to use non URL-ized actions in the routesMap by the way. It's been a request by several people. The formal contract and organization is very useful once your app gets filled with too many thunks that are hard to keep track of.

I agree to disagree. I don't think this is a good pattern. Sometimes it's better having no abstraction than the wrong one. It's definately nothing i want to see in a router, no matter how many people want it or how bad they do.
You already have one or more places where you group your actionCreators. Adding an async action is only a matter of adding sth. like this:
const persistData = data => dispatch =>
  api.persist(data)
    .then(persisted => dispatch(persistSuccess(persisted)))
    .catch(error => dispatch(persistError(error)))

What exactly is more direct combining this with a route?
All this tells me is that there is a need for better organizational patterns and more documentation, tutorials and screencasts on how to organize your side-effects with redux middleware.
It might even lead to new packages/modules that help doing so and can also be used in combination with redux-first-router routeMaps or instead of them.
Just don't mix things together that don't belong.

RFR now supports "pathless routes". Check the top of the main RFR repo for more information on this update.
Basically now your entire app can be made with actions + thunks specified in the routesMap. The overall goal is to prevent the typical explosion of the number of actions your app has, which becomes hard to remember, maintain, etc. The reason this occurs is subtle and somewhat psychological: essentially many apps end up with lots of "setter/getter" style actions. But when you start attach URLs/paths to your actions, it formalizes the contract and you end up dispatching less actions (especially unnecessary consecutive synchronous actions) and make your reducers fatter/smarter. This is what happens when properly using RFR before pathless routes existed. Now that they exist, they break that contract a bit, by having all your actions in one routesMap along side very formal path-based routes, you hopefully start developing an eye for keeping the # of actions your app uses at once. I've seen many developers new to redux do this:
dispatch(action1)
dispatch(action2)

I've seen far worse. 3 or 4 actions all dispatched synchronously one after the other. That's incorrect. What's correct is making your reducers all smarter by having them all correctly respond to just the first action. So in the RFR school of thinking, routes very much help developers move in that direction. They begin to recognize that if they want their app to respond properly to the user's usage of the browser back/next buttons, he/she is gonna have to make the reducers all interpret a single action. I mean they can do crappy things like dispatch more actions in route thunks or in component lifecycle handlers of the primary component that renders for each route, but they'll at least be pushed in the right direction to do this professionally. There's always exceptions of course, but the multi consecutive synchronous dispatch thing is generally an anti-pattern.
So yea, it's up to you if you're gonna use pathless routes. The real idea is making a *single *solid pattern accessible to junior developers. Keeping them living in the routesMap is a good thing. They likely already started off on a good foot with route-based paths--so by thinking of other async work in the same way is just good for their health.
Here's an example:
https://gist.github.com/faceyspacey/2771c05a62a338fa6d3d23d76e6e7c5a


Update api minimum Go version to 1.21

A higher go build version is not required for the API and this will help some downstream projects test the change which are currently blocked on 1.22 upgrade.

So, it does not immediately refuse it now, but it looks like API 1.8 is not backward compatible from a Go perspective. It looks like some parts were removed that the 1.7 code expects (perhaps moved elsewhere?)
24.59 # github.com/containerd/containerd/services/introspection
24.59 vendor/github.com/containerd/containerd/services/introspection/local.go:88:35: cannot convert &Local{} (value of type *Local) to type "github.com/containerd/containerd/api/services/introspection/v1".IntrospectionClient: *Local does not implement "github.com/containerd/containerd/api/services/introspection/v1".IntrospectionClient (missing method PluginInfo)
24.59 vendor/github.com/containerd/containerd/services/introspection/service.go:57:12: cannot use localClient (variable of type *Local) as "github.com/containerd/containerd/api/services/introspection/v1".IntrospectionClient value in struct literal: *Local does not implement "github.com/containerd/containerd/api/services/introspection/v1".IntrospectionClient (missing method PluginInfo)
24.85 # github.com/containerd/containerd/sandbox
24.85 vendor/github.com/containerd/containerd/sandbox/bridge.go:35:10: cannot use &grpcBridge{…} (value of type *grpcBridge) as "github.com/containerd/containerd/api/runtime/sandbox/v1".TTRPCSandboxService value in return statement: *grpcBridge does not implement "github.com/containerd/containerd/api/runtime/sandbox/v1".TTRPCSandboxService (missing method SandboxMetrics)
24.85 vendor/github.com/containerd/containerd/sandbox/bridge.go:45:33: cannot use (*grpcBridge)(nil) (value of type *grpcBridge) as "github.com/containerd/containerd/api/runtime/sandbox/v1".TTRPCSandboxService value in variable declaration: *grpcBridge does not implement "github.com/containerd/containerd/api/runtime/sandbox/v1".TTRPCSandboxService (missing method SandboxMetrics)
47.61 # github.com/containerd/containerd/runtime/v2/shim
47.61 vendor/github.com/containerd/containerd/runtime/v2/shim/publisher.go:39:12: undefined: v1.Envelope
47.61 vendor/github.com/containerd/containerd/runtime/v2/shim/publisher.go:118:11: undefined: v1.Envelope
59.83 + rm -f /go/src/github.com/docker/docker/go.mod

So for the module to be usable for 1.x, (1.7), it looks like some changes are needed in the 1.7 code 🤔

We can bring in those changes to make it compatible, testing with #10278
This PR doesn't depend on that though and can be considered on its own.


Add zh_cn.json

Add Simplified Chinese translation.

#14 Sorry, I found an inconsistency in the wording and have fixed it. There is no problem with the translation now!


Add new operators in WAF custom rule condition

Related command
az network application-gateway waf-policy custom-rule match-condition add
Is your feature request related to a problem? Please describe.
New operators for custom rule condition have been added to NRP- "Any", "GeoMatch". Changes are submitted in azure-powershell. Azure-cli needs to be updated accordingly.
Describe the solution you'd like
Customer should be able to add a custom rule condition with the new operators
Describe alternatives you've considered
Additional context
Powershell PR

network


Can't add "e-mail" icon

Hello.
I don't know how to add simple "e-mail" (envelope) icon like on your private website pureandroid.com. Could you help me?

Those links are configured in the config.toml file. Under [extra], right at the end of the file, there is the entry for social_links. Simply add it there. In the case of my private website, it looks like this:
social_links = [
    { name = "e-mail", enabled = true, link =<EMAIL_ADDRESS>svg = '<svg class="h-6 w-6" fill="currentColor" viewBox="0 0 493.497 493.497"><path d="M444.556 85.218H48.942C21.954 85.218 0 107.171 0 134.16v225.177c0 26.988 21.954 48.942 48.942 48.942h395.613c26.988 0 48.941-21.954 48.941-48.942V134.16c.001-26.989-21.952-48.942-48.94-48.942zm16.314 48.942v225.177c0 2.574-.725 4.924-1.793 7.09L343.74 251.081l117.097-117.097c0 .<IP_ADDRESS>.176zM32.628 359.336V134.16c0-.064.033-.11.033-.175l117.097 117.097L34.413 366.426c-1.06-2.166-1.785-4.515-1.785-7.09zm219.156-62.434c-2.692 2.691-7.378 2.691-10.07 0L62.667 117.846h368.172L251.784 296.902zm-78.957-22.75 45.818 45.819c7.512 7.511 17.493 11.645 28.104 11.645 10.61 0 20.592-4.134 28.104-11.645l45.82-45.819 101.49 101.499H71.327l101.5-101.499z"/></svg>' },
]

Great, thanks!


remove unnecessary "use strict"

https://sideci.com has a list, otherwise all those that are used within a function that already has "use strict" - including private functions.
@Algareb or @Ardenian maybe?

For now I am fine with the css ticket, might queue it to my TODO-List, once I am done with that, keeping an eye on it for now. Everyone can feel free to do it though, just saying.


docs: document read-only locked env var behaviour [sc-10987]

Affected Components

[ ] Content & Marketing
[ ] Test
[x] Docs
[ ] Learn
[ ] Other

Pre-Requisites

[ ] Code is linted (npm run lint)

Notes for the Reviewer
We recently removed access to locked environment variables for read-only users. We can add this to the docs now.
The updated page is here.

Current dependencies on/for this PR:

main

PR #579   👈

This comment was auto-generated by Graphite.

Thanks for catching that @tnolet


Convert to markdown fails for mlflow runs

If the user uses mlflow for tracking the markdown conversion fails.
This is something that needs to be addressed asap to reenable the feature for our advanced template.
@awmatheson and @ashishonce  Can you please look into it?
I can help you setting this up.
This is related to the issue mentioned here https://github.com/Azure/aml-workspace/issues/14

Sample output:
{'Training samples': 353.0,  'Test samples': 89.0,  'alpha': 0.03,  'mse': 3424.9003158960168}


Use @nuxtjs/color-mode

On https://github.com/directus-community/agency-os/blob/main/composables/useDark.ts
See https://color-mode.nuxtjs.org/
It better supports the different Nuxt rendering modes

Closed in #27


:hammer: Add tracer as a separate container to worker DaemonSet

Codecov Report
Patch and project coverage have no change.

Comparison is base (78c89cc) 7.89% compared to head (2730a73) 7.89%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff           @@
##           master   #1428   +/-   ##
======================================
  Coverage    7.89%   7.89%
======================================
  Files          48      48
  Lines        2977    2977
======================================
  Hits          235     235
  Misses       2731    2731
  Partials       11      11

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


Ldap, php-config, phpize 7.2

Adding the ldap package (alleviates problem with prompting the user for which configuration file to keep). Also adding php-config and phpize update-alternative settings; previous (and maybe the current) version of Homestead (6.0.0, 6.10) has been provisioned with an version of php7.2-dev that no longer exists in the ppa repo and requires an apt-get update to locate the correct package, having explicit settings for php-config and phpize would of caused an error message when the dev libraries are not available.

Thanks for the PR


host ip prerouting forwarded ports appear filtered to other containers

great project lxc/lxd!!
I have an unprivileged container to which a port is routed with
iptables -t nat -I PREROUTING 1 -p tcp -d $hostIp --dport $outsideport -j DNAT --to-destination $privateIp:$insideport
and
iptables -t nat -I OUTPUT 1 -p tcp -d $hostIp --dport $outsideport -j DNAT --to-destination $privateIp:$insideport
I can get access the service in the container fine via the $hostIp--$outsideport  from anywhere but from another container on the same host; nmap on this container says the port is filtered.
If I use the $privateIp $insideport on this second container it works fine.
could this be a bug? v0.22 on ub15.10.

forget about it, it is simply the masquerading that does not work by default postrouting only applies to destinations outside private network.
adding this solves the problem
iptables -t nat -I POSTROUTING 1 -p tcp -s $privateNet/24  ! --dport $outsideport -j MASQUERADE


misspelling in flow/layer/*unittests.cc files

A number of tests in the flow layer unit tests misspell "Preroll" as "Preoll".

Can you give me a perticular path of this file?

@flar

There are several. git grep Preoll should show you where. That's not a word so anywhere it appears is a misspelling.


An exception occurred when requesting the same assertion

When two identical assertions are requested, it has an MessageObservedException exception. The sample code is as follows:
from durable.lang import *

with ruleset('animal'):
    # will be triggered by 'Kermit eats flies'
    @when_all((m.predicate == 'eats') & (m.object == 'flies'))
    def frog(c):
        c.assert_fact({ 'subject': c.m.subject, 'predicate': 'is', 'object': 'frog' })

    @when_all(+m.subject)
    def output(c):
        print('Fact: {0} {1} {2}'.format(c.m.subject, c.m.predicate, c.m.object))

assert_fact('animal', { 'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies' })
assert_fact('animal', { 'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies' })

The output is as follows:

Fact: Kermit is frog
Fact: Kermit eats flies
Traceback (most recent call last):
File "facts.py", line 14, in
assert_fact('animal', { 'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies' })
File "/Users/hzq/.conda/envs/py3.6/lib/python3.6/site-packages/durable/lang.py", line 671, in assert_fact
return get_host().assert_fact(ruleset_name, fact, complete)
File "/Users/hzq/.conda/envs/py3.6/lib/python3.6/site-packages/durable/engine.py", line 763, in assert_fact
return self._handle_function(rules, rules.assert_fact, fact, complete)
File "/Users/hzq/.conda/envs/py3.6/lib/python3.6/site-packages/durable/engine.py", line 736, in _handle_function
rules.do_actions(func(args), callback)
File "/Users/hzq/.conda/envs/py3.6/lib/python3.6/site-packages/durable/engine.py", line 330, in assert_fact
return self._handle_result(rules.assert_fact(self._handle, json.dumps(fact, ensure_ascii=False)), fact)
File "/Users/hzq/.conda/envs/py3.6/lib/python3.6/site-packages/durable/engine.py", line 319, in _handle_result
raise MessageObservedException(message)
durable.engine.MessageObservedException: {'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies'}

The same assertion request should return the same result, but why is there an exception? I am confused about this and look forward to your answer.

Hi, thanks for posting the question. The reason is because the second fact will not be evaluated nor stored, as the engine data structures don't support holding identical facts. For your case above, you can disambiguate the facts by using an id:
from durable.lang import *

with ruleset('animal'):
    # will be triggered by 'Kermit eats flies'
    @when_all((m.predicate == 'eats') & (m.object == 'flies'))
    def frog(c):
        c.assert_fact({ 'subject': c.m.subject, 'predicate': 'is', 'object': 'frog', 'thread_id': c.m.thread_id})

    @when_all(+m.subject)
    def output(c):
        print('Fact: {0} {1} {2}'.format(c.m.subject, c.m.predicate, c.m.object))

assert_fact('animal', { 'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies', 'thread_id': 1 })
assert_fact('animal', { 'subject': 'Kermit', 'predicate': 'eats', 'object': 'flies', 'thread_id': 2 })

Thank you very much for your answers.
It would be nice if the system supports requesting the same assertions without using an extra ID.


Keyboard focus indicator is not visible on the table header and row controls on File management tab.

Describe the bug
When we navigate with tab key on the table headers of the table, keyboard focus indicator is not visible around it.
If keyboard focus indicator is not visible on the table controls, then keyboard dependent users will not get the information of the current focused element and will be unable to navigate and access the controls within the table properly.
To Reproduce
Steps to reproduce the behavior:
1.Open URL in edge dev browser.
2.Navigate to the table present on the page using tab key.
3.Navigate the table header using tab key and observe that the keyboard focus indicator is visible on table header or not.
Alternatively link your repo with a sample project that can be run.
URL
Expected behavior
Proper Keyboard focus indicator should be visible on the table header controls.
Desktop (please complete the following information):
OS Build: Windows 11 Enterprise 22H2 (23620.1000)
Edge Dev Browser: Version 122.0.2365.16 (Official build) dev (64-bit)
Additional context
Issue is also repro for the table headers on Result table in the search tab.
Attachments
https://github.com/radzenhq/radzen-blazor/assets/93735775/9fba7192-c48c-4dee-b922-9e068d962907

Fixed in https://github.com/radzenhq/radzen-blazor/commit/347942668d9003788403ec4e315ae2bfcec68263


Allow modifier key to force normally-disabled operations

Power users should be able to force the following operations when they know them to be safe or plan to fix up the results afterward:

Delete relation member
Move large object with "not enough visible"
Merge / join despite conflicting tags / relations

Holding down the Alt / Option key while the menu is visible should force these operations to be enabled, with a suitable warning in the tooltip.

Holding down the Alt / Option key while the menu is visible should force these operations to be enabled, with a suitable warning in the tooltip.

I think we are overdependent on using modifier keys for things.  It really limits our ability to serve mobile users.
I agree with your list though.. Would you be open to the idea of adding a checkbox somewhere for this?
Or a flag that can only be set via the dev console (maybe that's too experty).

I generally want to do this only on a case-by-case basis, and I actually like the feedback of having the operation disabled by default. With a checkbox elsewhere in the UI, I assume I wouldn't get that. Maybe the tooltip would still mention the fact that it's a potentially dangerous operation, but I'm likely to miss that, especially if I use a shortcut key to trigger the operation.

I generally want to do this only on a case-by-case basis, and I actually like the feedback of having the operation disabled by default.

That's a good point...  So this is more like "Run as Administrator.." on windows.


Implement : Delay-Queue, Message-TTL, Queue-TTL, Dead-Letter-Queue,  Multi-Tenant in AoP(Implementation based on PR#748)

Fixes #832
Motivation
1.Support dead letter queue.
2.Supports message-level and queue-level ttl.
3.Support multi-tenant, client virtual-host use tenant/virtual-host, this function can migrate multiple rabbitmq clusters to aop, you only need to set different tenant.
4.Rabbitmq delay queue is supported.
Modifications
1.Create a subscription for each queue (initialized when the queue is created).
2.Getting the subscription in the PersistentQueue starts a task loop to detect message expiration.
3.Passing the parameters of the queue to the PersistentQueue
4.When the consumer calls basic.reject or nack with requeue=false, the dead-letter queue or ack message is routed.
Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below.
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[x] no-need-doc
(Please explain why)

[ ] doc
(If this PR contains doc changes)

All queues are loaded by default.


[CsvIO] Implement CsvParseHelpers::mapFieldPositions method

This PR closes #31718 .

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

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] 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.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

could you please rebase onto the latest master branch. to resolve the merge conflict

could you please rebase onto the latest master branch. to resolve the merge conflict

I attempted to use the git config pull.rebase true command but the branch isn't updating. Is there a certain command to use instead to ensure the rebase?

that is git rebase --onto upstream/master <current base> <current branch>


Question: forcing phone code

Thanks for your work, @halt-hammerzeit
What's the best way to force a phone code inside of input-format? For example, +7.
templateFormatter with +7 (xxx) xxx xx xx appends 7 on every key press.
I guess that it should skip + as a first symbol and 7 as a second symbol. But it should append +7 if 1-6 of 8-0 are entered.

You didn't understand how the formatter works.
First the text input is parsed into value. It may be an empty string.
Then the value is formatted using the template.
So, for 1 digit being input the parsed value is 1.
Then the value gets formatted using the template and outputs +7 (1  ).
Next, 2 digit is input.
The value is parsed: +7 (12  ) -> 712.
Then the value is formatted: +7 (712).
So, the template isn't used for parsing – it's just used for formatting.
Write a custom parse function, it can do anything.


removing beta check so we can test it in stage stable

The chrome navigation is updated, so we don't need to use the beta flag to hide the navigation.
https://github.com/RedHatInsights/chrome-service-backend/pull/413

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


1.12.2(back far):  SpawnEntityEvent#getEntities().size()  is Zero on mob death (crossover with DropItem event?)

Have noticed in the past that sometimes event.getEntities().get(0) would return null.
Logged SpawnEntityEvent where .size() is zero and did various server activities.
The times in which a zero-size list event is thrown is when the spawn event itself appears to be the DropItemEvent.Destruct event????? (as in, the class of spawnentityevent is that class...)  which occurs when mobs are killed which may drop items.
The odd man out of that is the death of bats, bats will catch fire and burn, and trigger the same spawn .dropped-item process, even though bats have nothing to drop, so its not the actual items that are being dropped by the mob that are throwing the event.
   Small slimeblock jumps through fire and dies
=========================
[05:50:40] [Server thread/INFO] [STDOUT]: ========== ZERO ENTITY SPAWN SIZE ========
[05:50:40] [Server thread/INFO] [STDOUT]: class org.spongepowered.api.event.DropItemEvent$Destruct$Impl
[05:50:40] [Server thread/INFO] [STDOUT]: class net.minecraft.entity.monster.EntitySlime
[05:50:40] [Server thread/INFO] [STDOUT]: Odd spawn process: Destruct{cancelled=false, cause=Cause[Context=Context["sponge:spawn_type"=SpongeSpawnType{id=sponge:dropped_item, name=DroppedItem}], Stack={EntitySlime['Slime'/4101, l='world', x=-186.12, y=17.12, z=-1264.77], BlockDamageSource{Name=inFire, Type=fire, BlockSnapshot=SpongeBlockSnapshot{worldUniqueId=bf6a8994-edbc-41bb-a432-6ad475e879e4, position=(-187, 17, -1266), blockState=minecraft:fire[age=0,east=false,north=false,south=false,up=false,west=false], extendedState=minecraft:fire[age=0,east=false,north=false,south=false,up=false,west=false]}, Location=Location{(-187.0, 17.0, -1266.0) in WorldServer{LevelName=world, DimensionId=0, DimensionType=minecraft:overworld}}}, EntitySlime['Slime'/4101, l='world', x=-186.12, y=17.12, z=-1264.77]}], context=Context["sponge:spawn_type"=SpongeSpawnType{id=sponge:dropped_item, name=DroppedItem}], entities=[], entitySnapshots=null, source=EntitySlime['Slime'/4101, l='world', x=-186.12, y=17.12, z=-1264.77]}

.. Slash a creeper with a sword
[05:51:49] [Server thread/INFO] [STDOUT]: ========== ZERO ENTITY SPAWN SIZE ========
[05:51:49] [Server thread/INFO] [STDOUT]: class org.spongepowered.api.event.DropItemEvent$Destruct$Impl
[05:51:49] [Server thread/INFO] [STDOUT]: class net.minecraft.entity.monster.EntityCreeper
[05:51:49] [Server thread/INFO] [STDOUT]: Odd spawn process: Destruct{cancelled=false, cause=Cause[Context=Context["sponge:spawn_type"=SpongeSpawnType{id=sponge:dropped_item, name=DroppedItem}], Stack={EntityCreeper['Creeper'/3652, l='world', x=-193.70, y=9.00, z=-1319.70], EntityDamageSource{Name=player, Type=attack, Source=EntityPlayerMP['BooMod'/491, l='world', x=-193.03, y=9.00, z=-1317.44]}, EntityCreeper['Creeper'/3652, l='world', x=-193.70, y=9.00, z=-1319.70], EntityPlayerMP['BooMod'/491, l='world', x=-193.03, y=9.00, z=-1317.44]}], context=Context["sponge:spawn_type"=SpongeSpawnType{id=sponge:dropped_item, name=DroppedItem}], entities=[], entitySnapshots=null, source=EntityCreeper['Creeper'/3652, l='world', x=-193.70, y=9.00, z=-1319.70]}
[05:51:49] [Server thread/INFO] [STDOUT]:  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Even though this isn't probably intentional, I wonder how you would add drops to an entity that isn't going to drop any on death by default/chance if this was removed.

Its not an issue of where would you add drops to a dying mob, sure a zombie can drop something on death, i would assume that bones spawning are part of the skeleton death things there, that should be something spawned,except there appears to be nothing in the event that is the bones or armor or slimeball... but a bat dying spawns nothing.   So the primary question is why is 'nothing spawned' causing a spawn event, secondary question is 'is the wrong event being thrown/ is it thrown with incomplete information'
It would be like having the ChangeBlockEvent.Break fire when a cactus or reed grows and 'breaks' the air block above, yet, throw the event with zero transactions.

Closing this as it is by design that we always fire the drop (and Forge mods expect it to add drops to it).
If you feel the API should be adjusted, make an issue there.


files within types directory are (now ?) in (sub)directories

started with a fresh copy of the template
did did install, compile, typechain (now got typechain v7.0.0)
types directory (now ?) contains contracts and factories folder, also index.ts file(s) and files are in the same directory hierarchy like in the contracts folder (not sure if that was the case before). This avoids name collisions, but the types files and not anymore where referenced

bug or feature? ... and do I want the index.ts files as well ?
@DenhamPreen ?

Has this issue been addressed by https://github.com/PaulRBerg/hardhat-template/pull/164, @SvenMeyer?

For now I have adopted to the new behaviour, will monitor if it is consistent.

discussion related to this topic is here
https://github.com/PaulRBerg/hardhat-template/discussions/169

Closing due to inactivity.


[Monitor] Fix DataCollectionRules tag in readme.md; Add section in readme.phyton.md

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

@herreraj-ms
Let me know if you want it merged now, or want to fix python track2 build first.

@herreraj-ms
Let me know if you want it merged now, or want to fix python track2 build first.

I need to discuss with the team for fixing the swagger specs.
We can merge this one.
Thanks!


fio: 3.30 -> 3.31

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/fio/versions.
meta.description for fio is: "Flexible IO Tester - an IO benchmark tool"
meta.homepage for fio is: "https://git.kernel.dk/cgit/fio/"
meta.changelog for fio is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.31 with grep in /nix/store/7qk4h8rab4nvd29lg49idxz4sf1czxnv-fio-3.31
found 3.31 in filename of file in /nix/store/7qk4h8rab4nvd29lg49idxz4sf1czxnv-fio-3.31

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
fio
kdiskmark
xfstests

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7qk4h8rab4nvd29lg49idxz4sf1czxnv-fio-3.31 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fio https://github.com/r-ryantm/nixpkgs/archive/a47212c175d3c484e05551fce118ac74cd44a674.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7qk4h8rab4nvd29lg49idxz4sf1czxnv-fio-3.31
ls -la /nix/store/7qk4h8rab4nvd29lg49idxz4sf1czxnv-fio-3.31/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

xfstests

2 packages built:

fio
kdiskmark

Maintainer pings

Result of nixpkgs-review pr 185914 run on x86_64-darwin 1

1 package built:

fio

xfstests was already broken on master: https://hydra.nixos.org/job/nixpkgs/trunk/xfstests.x86_64-linux/all


Use dynamic registration for folding range options

Dynamically register because clangd doesn't currently support it, but may in the future. Without this change, we don't provide any code folding in Objective-C files because our empty results override's VS Code's default implementation.

@swift-ci please test

Hmm, actually gonna see if there's an easier way - maybe VS Code will ignore our results if we instead return an error?

Nope, VS Code still hides its own folding ranges when we return an error.

@swift-ci please test


Index data

Another pull to relocate index files.

Looks great 😍
Hope you are enjoying your journey 🚆  with OpenGenus


Debugging: Break points are disabled.

Hi,
I can successfully do Debugging in Chrome but from Visual Studio the Break points are in disable state.
When I run VS Debug, the App is raised in Chrome by emrun but the Break Points are disabled.
here are my VS settings of Web Browser Debugger and Local Windows Debugger:
Web Browser Debugger:

Local Windows Debugger:

Please switch the debugger from "Web Browser Debugger" or "Local Windows Debugger" to "WebAssembly Debugger".

Still in disable.
I had updated the VS Emscripten Packages.
Reproduced also on a new Project:
Step to reproduce:
1: Create a new Project:

2. Build the Project
3. Press on Debug and you will see an error:

Does "Debug Adapter Executable" point to a valid path?
node.js and python installation (bundled version with emsdk is also ok) are required for WebAssembly Debugger to work.

Hi Nokokan
I have same problem.
Is any thing wrong with my settings?
Debug Adapter Executable  D:\Work\emsdk\node\16.20.0_64bit\bin\node.exe
Server Command Executable  D:\Work\emsdk\python\3.9.2-nuget_64bit\python.exe


makeAndSignUnlock$ assert for channel state is too restrictive

From my understanding, with interactive signing the code below will require user intervention, to give permission for the signing:
https://github.com/raiden-network/light-client/blob/0abfd9ee9d4359b150048f7018dd13fe07175086/raiden-ts/src/transfers/epics/locked.ts#L265
The amount of time it will take for the user to perform the action is unbounded. From what I understand from @andrevmatos explanation for https://github.com/raiden-network/light-client/issues/2061 , the signing process will happen in a separate thread which won't block the SDK, meaning the blockchain event listener will continue running and can fetch new events from the blockchain.
It is completely possible that by the time the code below is executed, the node learns about the channel being closed:
https://github.com/raiden-network/light-client/blob/0abfd9ee9d4359b150048f7018dd13fe07175086/raiden-ts/src/transfers/epics/locked.ts#L268-L282
Leading to a failure in the assert. In that case, instead of an assert error, which I believe stops the SDK, a transferUnlock.failure should be returned.

You're right on your thinking, indeed with interactive signing we can't know how long the user will take to sign a message. But no assert should ever shutdown the SDK. We'll give a second pass to make sure of that on #1790 . The asserts are not used in our codebase as something that never happens, but instead on the sense of TypeScript's assertion functions, which acts as type-guards.
Specifically on these transfers observables, all of them end with a catchError, which will emit the respective failure, in this case, transferUnlock.failure:
https://github.com/raiden-network/light-client/blob/0abfd9ee9d4359b150048f7018dd13fe07175086/raiden-ts/src/transfers/epics/locked.ts#L305-L309

I didn't expect an assert to be used for type narrowing. I don't know if that is standard practice with TS, but maybe consider using if statements for type narrowing and asserts for stating assumptions that when broken represents a bug.

https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#assertion-functions
This is not that common, but is supported by language syntax, used consistently through our codebase, and composes well with the error observables logic (errors skips all following operators until hitting ones made specifically to handle it, like catchError and retryWhen).


Basemaps and overlays for countries have disappeared today...

There's a new button to customize the subset of layers shown in the interface.

Oups, thanks !

@vcoppe , could also help me to find this button? Am I missing something?

It's strange, on Firefox and Chromium the layers button is present just under the StreetView button.

@vcoppe , could also help me to find this button? Am I missing something?

There must be a JS error because the empty elevation profile isn't displaying either. Which browser and device do you use? Is it the first time you experience this?

Oh, my bad, there are some errors in console log (Firefox 78.0.2):
SyntaxError: expected expression, got '='
[layercontrol.js:264:38](https://gpx.studio/js/layercontrol.js)

TypeError: i.options is undefined
    _checkDisabledLayers https://gpx.studio/include/leaflet/leaflet.js:5
    _addItem https://gpx.studio/include/leaflet/leaflet.js:5
    _update https://gpx.studio/include/leaflet/leaflet.js:5
    onAdd https://gpx.studio/include/leaflet/leaflet.js:5
    addTo https://gpx.studio/include/leaflet/leaflet.js:5
    addTo https://gpx.studio/include/leaflet/leaflet.js:5
    onreadystatechange https://gpx.studio/js/buttons.js:687
[leaflet.js:5:53050](https://gpx.studio/include/leaflet/leaflet.js)

Wow, apparently the Logical OR assignment (||=) is only supported from Firefox 79.
I'll replace this line for better support but you should probably update your browser 😅


Feature Request: Support for Web Configuration UI with WiFi AP

Support Web Configuration UI with WiFi AP.
73!!

next week I will start coding for it!! ;)

Thank you for your contribution! I plan to use LILYGO®TTGO T-SIM7000G plus Lora module to form a 4G and Lora dual-mode tracker. I wonder if you are interested.
73！！

did you see that I used a A7670 + ESP32 board  + SX1278 for iGate ???
I think this could be transformed into a tracker with GPS module!!
and on top of this, A7670 uses 4G/LTE and SIM7000 uses 3G or less , right?

你看到我为 iGate 使用了 A7670 + ESP32 板 + SX1278 吗？？？
我想这可以改造成一个带 GPS 模块的追踪器！！
除此之外，A7670 使用 4G/LTE，SIM7000 使用 3G 或更少，对吗？

You are right, It's outdated.I am very sorry that I mentioned the wrong model before. I will use the new 4G and GPS integrated module, AIR780EG.

did you see that I used a A7670 + ESP32 board + SX1278 for iGate ???
I think this could be transformed into a tracker with GPS module!!
and on top of this, A7670 uses 4G/LTE and SIM7000 uses 3G or less , right?

You are right, It's outdated.I am very sorry that I mentioned the wrong model before. I will use the new 4G and GPS integrated module, AIR780EG.

I just checked the official information, T-A7670E does support GPS.

yes it does!
the AT commands to do this is not that friendly but can work!

did you see that I used a A7670 + ESP32 board + SX1278 for iGate ???
I think this could be transformed into a tracker with GPS module!!
and on top of this, A7670 uses 4G/LTE and SIM7000 uses 3G or less , right?

Is there any more information about A7670 + ESP32 board + SX1278 for iGate? Is the code already supported? How to connect SX1278?

did you see that I used a A7670 + ESP32 board + SX1278 for iGate ???
I think this could be transformed into a tracker with GPS module!!
and on top of this, A7670 uses 4G/LTE and SIM7000 uses 3G or less , right?

Is there any more information about A7670 + ESP32 board + SX1278 for iGate? Is the code already supported? How to connect SX1278?

pins_config.h or boards_pinout.h has the pins used for this.

did you see that I used a A7670 + ESP32 board + SX1278 for iGate ???
I think this could be transformed into a tracker with GPS module!!
and on top of this, A7670 uses 4G/LTE and SIM7000 uses 3G or less , right?

Is there any more information about A7670 + ESP32 board + SX1278 for iGate? Is the code already supported? How to connect SX1278?

how is it going changing the TOCALL to my firmwares?

I am wondering if there's any progress with Web UI + Wifi ? :-)

I am wondering if there's any progress with Web UI + Wifi ? :-)

very soon, was finishing RAK modules code


fix(evaluator): ensure unique prompt handling with labeled and unlabeled providers

This PR addresses an issue where providing different prompts per model is broken if the same provider id is used. It ensures that prompts are correctly mapped and processed based on either the provider's label or id. It resolves https://github.com/promptfoo/promptfoo/issues/1127 to test:
prompts:
  - prompt1
  - prompt2

providers:
  - id: 'python:provider.py'
    label: 'Provider 1'
    prompts:
      - prompt1
  - id: 'python:provider.py'
    label: 'Provider 2'
    prompts:
      - prompt2

tests:
  - description: 'Assert equals'
    assert:
      - type: equals
        value: 'prompt1'

Nice fix!


Migrate Farallon hub to this repo

Background
The Farallon institute JupyterHub is run from github.com/2i2c-org/pangeo-hubs/, and is not well automated. We should move that to this repository!
https://github.com/2i2c-org/pilot-hubs/issues/366 tackles fully setting up on AWS, so this goal will focus only on migrating the helm config + deployment to this repository.
Expected timeline
???
Steps to complete this goal

[x] Add support for a cluster authentication method that can be used on the farallon hub to deployer/
[x] Move the staging farallon hub
[ ] https://github.com/2i2c-org/pilot-hubs/issues/381
[x] Figure out how to do authentication - right now, Farallon hub uses GitHub orgs for authorization, which auth0 doesn't support yet https://github.com/2i2c-org/pilot-hubs/pull/487
[x] Move the production farallon hub
[x] ~Consider removing the farallon staging hub~ (gonna keep it)
[ ] Archive https://github.com/2i2c-org/pangeo-hubs

Just a quick note on this - I think we should prioritize this below #363 - so I'm attaching a label to mark this as such :-)

Once https://github.com/2i2c-org/pilot-hubs/pull/391 is merged, @damianavila is going to go through moving the farallon hub over to the new kops based setup. That will help complete this.

A little reminder to re-revert https://github.com/2i2c-org/pilot-hubs/pull/400 once the above is complete.

We should archive https://github.com/2i2c-org/pangeo-hubs once this is complete

I've carefully deleted the old EFS instance. I'll now carefully delete the old cluster

I've deleted the staging and prod hubs by hand:
helm -n farallon-staging delete farallon-staging
helm -n farallon-prod delete farallon-prod

This ensures that any external cloud resources created by kubernetes (disks for the hub db dir, load balancer for the proxy-public service) are deleted

I've enabled EFS Lifecycles on the new EFS setup too (https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html) - this moves infrequently accessed files to slightly slower storage for significant cost benefits. The previous EFS had this enabled

I deleted the old cluster with:
export KOPS_STATE_STORE=s3://2i2c-farallon-pangeo-kops
kops delete cluster farallon-2i2c.k8s.local --yes

This ensures that any external cloud resources created by kubernetes (disks for the hub db dir, load balancer for the proxy-public service) are deleted

I have seen this issue as well with CloudFormation stuff, particularly with the load balancer.
We should document this practice, @yuvipanda, WDYT?

@damianavila yeah! Perhaps documented as part of decomissioning a hub / cluster?

https://github.com/2i2c-org/pangeo-hubs is now just the user image

For the record, the repo was renamed as well as farallon-image

Once #391 is merged, @damianavila is going to go through moving the farallon hub over to the new kops based setup. That will help complete this.

A little reminder to re-revert #400 once the above is complete.

I was wondering where are we with this and if it's ok to re-revevert #400?
Ref: https://github.com/2i2c-org/pilot-hubs/issues/507

@GeorgianaElena, I think we need to solve https://github.com/2i2c-org/pilot-hubs/issues/381 to close this one and before revert #400.

I'm going to close this, as the hub itself is migrated. #381 tracks the general problem that is preventing  CD from happening longer term


Add feather

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thanks!

I did a little digging; it seems like the Feather app is the successor of Regxr, which appears to have been renamed to Feather only a few days ago. Around that time, GitHub purports to have received a DMCA takedown notice from a software vendor named Apptorium, who owns the copyright to the app Expressions (cask).
The author of the DMCA claims to represent Apptorium, and goes on to allege that @lukakerr have infringed Apptorium’s copyright by publishing Regxr, which they claim to be an unauthorized copy of Expressions.
Notwithstanding those copyright allegations, I figure it’s highly unlikely for the takedown notice to be challenged, or for the Feather repo to return. I’d say we delete the cask and move on. @niklas-heer Thanks for the heads up.
tl;dr The app is gone, most likely for good.

Sad to hear, but thank you very much for the research @claui!

You’re welcome @niklas-heer! ☺


Update install.md

Updates the "Install a specific version" section with the correct command
Closes #???
Description
Updates the docs to include the new version specific install command, as discussed here:
https://github.com/onflow/flow-cli/issues/737#issuecomment-1353036630

For contributor use:

[ ] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[ ] Code follows the standards mentioned here
[ ] Updated relevant documentation
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Codecov Report

Merging #842 (dec5d5f) into master (f00322f) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #842   +/-   ##
======================================
  Coverage    2.75%   2.75%
======================================
  Files           5       5
  Lines         400     400
======================================
  Hits           11      11
  Misses        388     388
  Partials        1       1

Flag
Coverage Δ

unittests
2.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Ok cool, thanks for the info @sideninja, I have updated the PR!


How about inner composable that are bigger than Zoomable composable ?

Hi,
Works like a charm but how about inner composable that are bigger than Zoomable composable ?
Let's see an example :
        val state = rememberZoomableState()
        Zoomable(
                modifier = Modifier.fillMaxSize(),
                state = state
        ) {
            Column(
                    modifier = Modifier.align(Alignment.Center),
                    horizontalAlignment = Alignment.CenterHorizontally
            ) {
                Text(
                        text = "TEST"
                )
                Image(
                        painter = painterResource(id = R.drawable.big_drawable),
                        contentDescription = null
                )
                Text(
                        text = "TEST"
                )
                Image(
                        painter = painterResource(id = R.drawable.big_drawable),
                        contentDescription = null
                )
            }
        }

Here if the screen height is not enough, you won't see the second image.

Did you got any solution?


Door of boiler permanently shows as OPEN

A picture says more than a thousand words...  ;-) HA and add-ons all current!!!
Opening and closing the door brings no change.

Can you confirm, that in Solarfocus, the value changes? So that the ModBus value is actually updated.

Works fine in VNC-Viewer.

Is this related to #91 ?

Maybe, but this is what I found....

After todays update, the door unfortunately still shows as open....

I recently had the technic guy here - He mentioned that if you are in the service menu the door will always show open - "safety mechanism"

Ok, that still does not explain, why the door is showing as open when it is not!!!!

sure - If you enter the service mode, the service mode forces the state of the door to be open (regardless if the door is open or close in reality). But you're right, I think in your case it might be something differnt, since the pellet boiler is running.
Maybe you can add some information on your current firmware version, model,...

As I wrote above, current HA and add-ons. See screenshot above for firmware version...

This issue is related to #91. I have doublechecked and can confirm this.

This issue is related to #91. I have doublechecked and can confirm this.
@RobertoCravallo
The door you are asking is described in #91 it is the Cover door that you need to open in order to get in example to the ashes-container.

I know, it is the "normal" door at the front of the oven. This was showing correctly until 2024-1 and then everything went south for a while. Seems to be running ok now, except for the "door" being shown as open, even if it is not.

Jetzt mal auf Deutsch...
Ich habe ben eine Kesselreinigung durchgeführt, ich wollte ein wenig Asche (war nur zu 19% gefüllt) raustragen.

 Vermute es ist keine Tür sondern eine Klappe.

Hier wird in der HA-App nicht reagiert, "Zustand" der Tür ist komplett Wurst...

I have the Solarfocus ecotop zero, V4.3.0 and HA2024.9.3
The door status is negated.
I changed the line 229 in the binary_sensor.py:
    SolarfocusBinarySensorEntityDescription(         key="door_contact",         device_class=BinarySensorDeviceClass.DOOR,         **on_state="1",**         unsupported_systems=[Systems.THERMINATOR, Systems.VAMPAIR],     ),
after a reboot it is working fine, without an issue.

Then let me change the implementation, hoping not to break it for Ecotop light users.


Extra context with Sidekiq error handling unsuccessful

I appreciate your consideration, thank you:
This is question rather than an issue (I believe).  I'm using the Sidekiq integration with my rails app with Sentry and have hit an impasse in regards to extra context for failures.  I haven't been able to successfully use the #capture or #capture_exception to pass the additional context.   Digging into the integrations for Sidekiq https://github.com/getsentry/raven-ruby/blob/master/lib/raven/integrations/sidekiq.rb#L19 the error handling should include the extra context but it seems to just chomp it.
This very well may be an implementation error on my end, but using the integration with the appropriate version of Sidekiq should default to using Raven::SidekiqErrorHandler, but again - context is lost.
I can give more information, but wanted to put my feelers our there to see if anyone else was experiencing difficulty with Sidekiq extra context being added to Sentry error reporting.

Using capture and capture_exception inside of sidekiq jobs will not automatically get any extra context. We could probably change the integration to do that, though.
The extra context you see in the integration is only added when an exception is raised by a job, not rescued, and is given to the error_handlers chain in Sidekiq.

@nateberkopec Thank you very much for the quick response. From what I've deduced, it doesn't make sense (for the way that my app is set up) to pass excess information to the worker in sidekiq for contextual purposes. Would you be able to advise on a 'best practice' of sending contextual data to Raven of a sidekiq exception?

From what I've deduced, it doesn't make sense (for the way that my app is set up) to pass excess information to the worker in sidekiq for contextual purposes. Would you be able to advise on a 'best practice' of sending contextual data to Raven of a sidekiq exception?

I don't understand. It doesn't make sense to add context in your Sidekiq worker, but you want me to give you best practice for sending context of a Sidekiq exception?
If you just let the exception bubble up from the worker, Sentry will report that and attach context.


Rename rke2 harderning guide

Addresses: https://github.com/rancher/rancher/issues/42385

@JonCrowther We also must update the corresponding pages in /versioned_docs/version-2.7, as these mirror the pages hosted in /docs. These pages have sidebars in /versioned_sidebars/version-2.7

And we need to set up redirects in docusaurus.config.js

@JonCrowther I pushed the changes for v2.7 docs redirects, but we still need to make corresponding changes to the other 2 PRs. Also, make sure to update references to v1.23 within the body of the page


fix firebase-messaging-sw.js path

The path used on firebase-messaging-sw.js creation is not correct.

Thanks, missed that one since the path resolved fine in all of my cases.
Will be fixed with v3.0.1.


Minor changes, trying to improve readability and ease of use

Thanks for the official Basho client! That was a great Christmas present for community! Hope to make it even more functional during next several weeks and use it in one of our prototype projects.
As far as I understand, get and put are more or less interface methods.
If there is a well-known list of options and it's unlikely to change, it may actually be good to specify that set to ease the future use, so
   (client/get c bucket key { :head true })

will become:
   (client/get c bucket key :head true)

moreover, it won't be possible to specify incorrect keys (if they make no sense, it's great to know about it during compile-time, right?)
Also I separated get-as-integer, fetch-options, store-options and delete-options to utils. I am not sure if you would like to have that change. I will add a test for each of those, and drop a couple of lines of doc. Even if these are private / helper methods, it's still good to have them clearly distinguishable for lib developers.
In the same manner, riak-object-to-map and map-to-riak-object are now in sumo.conversions. Although it feels that it's possible and/or better to re-do them as protocols. I'll try to do tomorrow or later next week.
Thanks again!

@ifesdjeen thanks for the changes. A couple of quick notes:
sumo isn't an official Basho client. That being said, I do intend to actively develop and maintain it :)
I think it's important to mark methods as internal-only, but I do wonder if some of these, like fetch-options, will be used outside of client.clj. Maybe the ones that will/are shared across namespaces can be put in sumo.utils or sumo.internal, and we can better differentiate internal methods like fetch-options with some dividers like:
;;;;;;;; internal methods ;;;;;;;;;;;;;;;;

Next, I rather like the (client/get c bucket key :head true) type calls, is there some way we can support both though? I think it won't be uncommon for people to want to keep a hash of options that they pass around to different get/put calls.
I'm not sure I understand your idea about protocols, can you elaborate?

As regards internal / utils. Well, that's completely your call. It seemed to me that these things do not directly belong to Client. Some Clojure libraries tend to put many things into one file. We tend to separate, pretty much the same way we do in Java, C or Ruby.
If you put things like fetch-options, store-options on top of file, it misleads people, since secondary functions are on top. If they're on the bottom you have to (declare) them.
As regards hash calls, it's possible to have just 1 variadic overload, but in that case it's not a prob. So it's possible to have both options and regular hash. But in Clojure it makes no difference wether you wrap a method or return a hash from the method, so I'm not sure if I would do so at all. It's good to provide compile-time support, for the rest - clojure is powerful enough.
As regards protocols, that idea is likely to be not that useful in that case.

Ghm, right. Client is not official. Sorry about that :) anyways, it's good that Basho guys are working on something clojurish, no matter wether it's official or no.

As regards hash calls, it's possible to have just 1 variadic overload, but in that case it's not a prob. So it's possible to have both options and regular hash. But in Clojure it makes no difference wether you wrap a method or return a hash from the method, so I'm not sure if I would do so at all. It's good to provide compile-time support, for the rest - clojure is powerful enough.

Would you mind giving an example of this? I took a look at this article, but it doesn't seem to address the ability to also pass in a hash.

I've been thinking of something like that:
(defn get
  "Retrieve a lazy-seq of objects at `bucket` and `key`

  Usage looks like:

      (def results (sumo.client/get client \"bucket\" \"key\"))
      (println (:value (first (results))))"
  ([^RawClient client ^String bucket ^String key &{:keys [r pr notfound-ok basic-quorum head value] :as options}]
     (get client bucket key options))
  ([^RawClient client ^String bucket ^String key options]
     (let [options (or (first options) {})
        results (get-raw client bucket key options)]
       (map #(assoc % :value (deserialize %)) results))))

but I completely forgot of:
Can't have fixed arity function with more params than variadic function

So right, it's not possible within just one function.
As a workaround one could pass :options into :keys and pass all the options into it, but that's already far away from what you meant.


env.render() does not work in A2C code from stable_baselines documentation

[help wanted]
Describe the bug
My issue/question is regarding the example code in the documentation for A2C.
When I try to run it, it seems to work fine. Model is trained, saved and restored.
But when env.render() is called, I get an EOFError.
Also, when I try to call env.close() afterwards I get another error.
I understand it has something to do with the multiprocessing module.
But why is it not possible for me to render in the first place?
Without render() it seems to work fine the model plays CartPole. I tested with Print(obs, rewards, dones) which worked.
Code example
Stacktrace for EOFError when calling env.render():
File "<ipython-input-2-6953c62eb323>", line 1, in <module>
    runfile('/Users/erik/Documents/Thesis/03 Arbeitsordner/01 Code/ETA-Brain/erik/easy_agents/minitest.py', wdir='/Users/erik/Documents/Thesis/03 Arbeitsordner/01 Code/ETA-Brain/erik/easy_agents')

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/site-packages/spyder/utils/site/sitecustomize.py", line 705, in runfile
    execfile(filename, namespace)

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/site-packages/spyder/utils/site/sitecustomize.py", line 102, in execfile
    exec(compile(f.read(), filename, 'exec'), namespace)

  File "/Users/erik/Documents/Thesis/03 Arbeitsordner/01 Code/ETA-Brain/erik/easy_agents/minitest.py", line 29, in <module>
    env.render()

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/site-packages/stable_baselines/common/vec_env/subproc_vec_env.py", line 93, in render
    imgs = [pipe.recv() for pipe in self.remotes]

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/site-packages/stable_baselines/common/vec_env/subproc_vec_env.py", line 93, in <listcomp>
    imgs = [pipe.recv() for pipe in self.remotes]

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 250, in recv
    buf = self._recv_bytes()

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 407, in _recv_bytes
    buf = self._recv(4)

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 383, in _recv
    raise EOFError

EOFError

Stacktrace for env.close()
env.close()
Traceback (most recent call last):

  File "<ipython-input-18-1baceacf4cb1>", line 1, in <module>
    env.close()

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/site-packages/stable_baselines/common/vec_env/subproc_vec_env.py", line 83, in close
    remote.send(('close', None))

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 206, in send
    self._send_bytes(_ForkingPickler.dumps(obj))

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 404, in _send_bytes
    self._send(header + buf)

  File "/Users/erik/anaconda3/envs/tensorflow/lib/python3.6/multiprocessing/connection.py", line 368, in _send
    n = write(self._handle, buf)

BrokenPipeError: [Errno 32] Broken pipe

System Info
Describe the characteristic of your environment:

library was installed using pip
working on Mac, no GPU
Python version = 3.6.5, installed using anaconda
Tensorflow version = 1.7.0, installed in a anaconda virtual env

Hello,
What version of stable-baselines are you using ? What is your gym version ?
Could you try with n_cpu=1 and also with a DummyVecEnv ?
import gym

from stable_baselines.common.policies import MlpPolicy
from stable_baselines.common.vec_env import SubprocVecEnv, DummyVecEnv
from stable_baselines import A2C

# multiprocess environment
n_cpu = 1
env = DummyVecEnv([lambda: gym.make('CartPole-v1') for i in range(n_cpu)])

model = A2C(MlpPolicy, env, verbose=1)
model.learn(total_timesteps=25000)
model.save("a2c_cartpole")

del model # remove to demonstrate saving and loading

model = A2C.load("a2c_cartpole")

obs = env.reset()
while True:
    action, _states = model.predict(obs)
    obs, rewards, dones, info = env.step(action)
    env.render()

Hey, thanks for the fast response.
I actually tried already with n_cpu = 1 before posting here.
Changing to DummyVecEnv solved the issue for me!
Thanks a lot!
If you still have the time to answer another question:
Why didn't it work with the SubprocEnv?
If the environment's outputs are only arrays like in CartPole, the DummyVecEnvshould always be sufficient, right?

Hello,
I'm not sure why, but for instance, SubprocEnv does not work on Windows. For mac os, I don't know, but apparently for rendering, there are issues. The only environment where there is no issue at all is linux.
I recommend you using SubprocEnv for training (it will allow you to multiprocess training) and then, if you want to render the learned policy, use a DummyVecEnv with only one env.
DummyVecEnv does only makes sense for n_cpu=1 (even so it works for n_cpu >=1).


automatic sweep registration

Remove the need for manually specifying whether we are using a W&B sweep or not. Also linked to this idea https://github.com/martinsbruveris/tensorflow-image-models/discussions/36

Thanks for the PR!

Really sorry I saw your messages too late :/ Glad it's merged though


iOS Code Refactoring from SIngleton

Is your feature request related to a problem? Please describe.
This task is to remove singleton code from iOS Tuvali repo.
Describe the solution you'd like
The singleton class can be removed and can be replaced with normal classes with initialisation

The following change is available on branch=0.9 & on branch=develop as part of the 17th March, 2023 release.
PR for mosip/inji(branch=develop): https://github.com/mosip/inji/pull/655,
commit: https://github.com/mosip/inji/commit/aff1c4f7b96d27f1c8f54e62d3f03a7086473f35
PR for mosip/inji(branch=0.9): https://github.com/mosip/inji/pull/653
commit: https://github.com/mosip/inji/commit/4c2ca4b0ea400cb29cb59ee6a87106e2542023da

Verified in:

Wallet Device: iPhone 11

Phone make/model: iPhone 11
OS: 15
BLE version : 5.0

Verifier Device: Galaxy A03 core

Phone make/model: Galaxy A03 core
OS: Android 11
BLE version : 4.2

Inji app version:

Mimoto version: <IP_ADDRESS>

MOSIP Version: qa-1201-b2.mosip.net

Multiple attempts of sharing is working.


Move unused methods from ReadOnlyFileSystemNode

to FileSystemNode. That allows some removing never used code and the need to adapt the child.
Follow up for https://github.com/gradle/gradle/pull/19823#discussion_r805580510.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Tools expired

Hey there, just wanted to let you know that the tools provided are expired (not available to download anymore)

Just triggered a new run. You can get tools when completed.
https://github.com/ilharp/depth-estimate-gui/actions/runs/3290018167
If you have any other question, feel free to reopen this issue.


Docs for FileVar should emphasize Django memory storage limit

Environment

Nautobot version (Docker tag too if applicable): 1.5.2
Python version: 3.10.8
Database platform, version: PostreSQL
Middleware(s):

Nautobot docs state file uploaded via FileVar is present in memory.

The wording could be improved to emphasize the file is actually stored in memory and Django has default limit of 2.5MB for these files. To increase this limit both FILE_UPLOAD_MAX_MEMORY_SIZE and DATA_UPLOAD_MAX_MEMORY_SIZE must be increased.
Note: Django allows the files to be stored on disk., but Nautobot implementation only expects InMemoryUploadedFile
https://github.com/nautobot/nautobot/blob/develop/nautobot/extras/jobs.py#L374-L376
Steps to Reproduce

create Job with FileVar param
upload file larger than 2.5MB

Expected Behavior
file uploaded

Observed Behavior
400 Bad Request

A problem with files being stored on disk is when the disk isn't shared between Nautobot the front-end and the celery workers elsewhere. Maybe this is something we can look at improving for Jobs in V2.
The docs update however can for sure be improved today!


add the defined data type

This data type can be used to validate any defined value.

This is seems very narrowed down to PostgreSQL/JSON support, I don't think it qualifies for a general purpose validator such as Cerberus core. Seems more suited for a custom validator, one that inherits from Cerberus?

Hi Nicola.
Thanks for the review. I will go this way.

:+1:


[WIP] add basic targeting packs for net40 and net45

Doing the simplest thing that could possibly work as *.dll has a couple of rogue files when you try and install it (i.e. System.EnterpriseServices.dll and System.EnterpriseServices.Thunk.dll)

[x] can target and build Rx.NET on Windows
[ ] can target and build Rx.NET on OS X

Don't worry about the dropped characters, you should get the idea here:
$ dotnet build
Compiling ystem.Reactive.Interfacesfor ETFramework,Version=v4.0

ompilation succeeded.
   0 Warning(s)
    0 Error(s)

Time elapsed 00:00:01.1006057
Compiling ystem.Reactive.Corefor ETFramework,Version=v4.0
/Users/shiftkey/src/Rx.NET/Rx.NET/Source/System.Reactive.Core/project.json(28,39): error NU1001: The dependency mscorlib could not be resolved.
sers/shiftkey/src/Rx.NET/Rx.NET/Source/System.Reactive.Core/project.json(28,39): error NU1001: The dependency System could not be resolved.
sers/shiftkey/src/Rx.NET/Rx.NET/Source/System.Reactive.Core/project.json(28,39): error NU1001: The dependency System.Core could not be resolved.
sers/shiftkey/src/Rx.NET/Rx.NET/Source/System.Reactive.Core/project.json(28,39): error NU1001: The dependency Microsoft.CSharp could not be resolved.

Compilation failed.
   0 Warning(s)
    4 Error(s)

Time elapsed 00:00:01.4029899

/Users/shiftkey/src/Rx.NET/Rx.NET/Source/System.Reactive.Core/project.json(28,39): error NU1001: The dependency mscorlib could not be resolved.

What's interesting about this line is that it maps to the interfaces project reference:
"dependencies": {
    "System.Reactive.Interfaces": { "target": "project" }
},

Have you seen this before?

Might mean that the Interfaces project needs a framework reference to mscorlib for net40?

@onovotny ah yes, I haven't added those yet (was hoping it's just implicitly work after adding the targeting pack).

The issue to track on this is https://github.com/dotnet/core/pull/64


Shameful

Unsure why you think it's a good idea to publish tools that abuse a free service, and break ToS, but it's not a good idea and actually illegal.

 If you're so hurt on behalf of a company who doesn't even know you, make a counter to this yourself and propose it to them.


Update package-lock with versionist

We are currently updating package.json and action.yml but that leaves package-lock out-of-sync.
Change-type: patch

LGTM


podAntiAffinity weight shoud not be required

As it is described here, weight shoud not be used when statefull set pod is scheduled; therefore parameter weight in CRDS should not be defined as required:
https://github.com/kubernetes/kubernetes/issues/57002

@Raschmann my understanding is that the field weight should not be used when using requiredDuringSchedulingIgnoredDuringExecution.
Indeed in the CRDs the field weight is required only for preferredDuringSchedulingIgnoredDuringExecution, see:
https://github.com/artemiscloud/activemq-artemis-operator/blob/v1.0.16/deploy/crds/broker_activemqartemis_crd.yaml#L507
https://github.com/artemiscloud/activemq-artemis-operator/blob/v1.0.16/deploy/crds/broker_activemqartemis_crd.yaml#L658
https://github.com/artemiscloud/activemq-artemis-operator/blob/v1.0.16/deploy/crds/broker_activemqartemis_crd.yaml#L831


Consumers blocked with 0 availablePermits

When a consumer with ackTimeout connects, it negotiates a given amount of permits with broker (say 1000), it then receives 1000 messages. At this point the consumer has 0 availablePermits and 1000 unackedMessages, If no one pulls these messages from this consumer, they are eventually redelivered to the broker, now the broker schedules redelivery of those messages, but never increments availablePermits for the consumer, leaving the consumer stuck with 0 availablePermits.
This happens at least with perMessageRedelivery, as a redelivery does not necessarily imply that permits have to be granted to the consumer. Unfortunately, I don't know if the Broker can really do something here.
I believe this issue is a consequence of a consumer asking for redelivery of messages that have never been pulled from the queue.
The best approach seems to be for the consumer to ask for more permits when this is the case.
What do you think?

I'm going to be out for the next few days. @rdhabalia can you take a look at this?

Also, when redeliverUnacknowledgedMessages(List<MessageIdImpl> messageIds) doesn't seem to be removing redelivered messages from the queue at any time, so the queue will always be stuck with redelivered messages.
I can't think of any simple way of solving this right now, maybe we can keep track of messages in the queue on a separate set.

redeliverUnacknowledgedMessages : it cleans up all the messages present into incomingMessages and sends separate flow-message command which increments availablePermits at broker for a given consumer. So, consumer will not be stuck at any time.
However, right redeliverUnacknowledgedMessages doesn't clean up incomingMessages queue and asks broker for redelivery. So, as soon as client consumes N/2 messages from the incomingMessages queue it triggers flow-message command to broker and broker will first release those redelivered messages as part of received permits. In this case: again consumer will not be stuck.

Also, redeliverUnacknowledgedMessages(List messageIds) doesn't seem to be removing redelivered messages from the queue at any time

Yes, we have to make similar change of redeliverUnacknowledgedMessages to clean up from incomingMessages queue and sends permits to broker by triggering flow-message command.

I will make changes and add test-cases for this scenario.

@rdhabalia I just created a PR for this, please give it a look, perhaps you can think of a better way of approaching this.

Ok. thanks, I will look into it.

@merlimat @rdhabalia any news on this? We really need to solve this issue

@sschepens just got back in office. reviewing the PRs

Just to clarify, this issue was introduced when tracking timeout on messages not pulled from the queue.
Perhaps we can take a different approach to this, in the end what we want to prevent is a clientes to hold messages when it's not processing.
We could empty the queue and not as for messages until it resumes acknowledging messages or something of the sort.

OK, it looks like it would be easier to just empty the queue and have the broker resend the all the messages that were on it. Anyway, they're not going to be "duplicates" since the application would not have seen them already.

Yup, but we maybe should make the consumer not receive messages until it resumes acks. Just to prevent constant redelivery.

I agree on that, the library should be playing with the permits to do that, but I'd keep it separate from this PR, because:

It might be tricky to make sure we don't forget any corner case and leave the delivery stopped
It should not be super-awful anyway.. you get 1000 messages resent every n-minutes

Fixed in #101


OpenNebula 4.14 support

We'd like to support OpenNebula 4.14, so are working on templating the config files. There are a number of differences between 4.14 and 4.12, so we propose the following:

what is currently the master branch becomes a 4.12 branch
the master then becomes 4.14
the master branch is 4.14 until 4.15 is released, and then we make a 4.14 branch

Let us know your thoughts regarding that.  For now we've got a work in progress of updating the config template files on a fasrc/opennebula_4_14 branch (comparison view https://github.com/epost-dev/opennebula-puppet-module/compare/master...fasrc:opennebula_4_14)
Another option is to version the template directory - ie
└── templates
    ├── 4.12
    ├── 4.14

And then in paths to template files in puppet code:
file { '/etc/one/oned.conf':
  ensure  => file,
  owner   => 'root',
  mode    => '0640',
  content => template("one/${one_version}/oned.conf.erb"),
}

This approach has the benefit of a single branch to support all versions, but might make the code more complicated if we have to split anything out by version other than templates.
Thoughts?

i think the branching-thing would be okay…. but have to discuss this with the team!

@rwaffen any thoughts?

currently i'm on vacation… but maybe @sebastian-su or @gerald1248 have something to say to this …

The difficulty with versioned template files is that you have to manage multiple versions of the same configuration file.
A more Puppet-like approach would be to use the version variable inside the template.
Another option would be to split up the template for a config file into multiple smaller segments.
  content => template('template_header', 'template_body1','template_body2','template-footer'),

finally merged, shall I close the issue?

Great, thanks!


Question: sending keystrokes for GLVis from MFEM

Hi All,
I see that in MFEM we use an osockstream to send data to a running instance of glvis and plot mesh and solution. Is there a way to add keystrokes to this so that I can automatically plot it with desired attributes?
For example: I would like to add the four keystrokes: JREM, which I can manually do right now from the terminal by using:
glvis -m dummy.mesh -k "JREM"
Thanks,
Ketan

Yes, see
https://github.com/mfem/mfem/blob/1569425857975d7c961b97d09c300da09aad9f82/examples/ex17.cpp#L299
or more generally:
https://github.com/mfem/mfem/search?utf8=✓&q=KEYS

Thanks Tzanio


Notify 589 auth v2

Explanation
This PR solves the bug of adding extra slash when user storage url is generated
References
Changelog
@metamask/profile-sync-controller

FIXED: remove extra slash when constructing user storage url

Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@metamaskbot publish-preview


Fix file.yaml

Project file does not use the fuzz target in the project repo, but the one in OSS-Fuzz directory.
Proof:

The fuzz target used is called magic_fuzzer.cc, the same as the one in OSS-Fuzz dir. The one from its repo is called magic_fuzzer.c.
This fuzz target does not have 52 lines, the one in OSS-Fuzz dir does.

/gcbrun exp -n dg -b file


The Crystal Math Labs plugin is broken and no longer updating the site

The crystal math labs plugin no longer updates after every logout. This can be re-created by logging in then logging out, and refreshing your user page on crystalmathlabs, and seeing that it wasn't updated.

Can you get logs of it sending a request and failing? It doesn't look like their api changed...

If you're only logging in and out, we're likely not firing off a request. iirc the plugin doesn't send requests unless you gain at least 1k exp in a login session to keep from spamming CML with tons of requests.

I tried logging out after getting >1k exp and it still didn't work. There weren't any logs about it in the log files.

2019-04-21 15:59:17 [OkHttp https://crystalmathlabs.com/...] WARN  n.r.c.p.c.CrystalMathLabs - Error submitting CML update, caused by Read timed out.

Yeah this is because CML is rejecting requests, nothing we can really do about that on our side

Hi, do you have any suggestions on why this might be the case? I have the same issue even now, and it says "failed to update... caused by crystalmathlabs.com" on every log. I've asked them as well as to why this might be the case but haven't received a reply yet.

I think the plugin should be removed as it is automatically rejected and just causes extra serverdelay when manually updating on the website

I think so to, its pointless to have plugin for some malfunctioning 3rd party api.

Is this reproduceable since 553e568?

I mean the plugin code was just moved to different place but do not really changes anything about how CML api works right.

Then is this bug still valid? Are players still experiencing timeouts when attempting to connect?

Given that this was never a RuneLite issue in the first place (it's caused by rejected requests on CML's end) and we've since moved the player xp updates behind a toggle for each site in the XP Updater plugin, I am closing this issue. I recommend anyone following this to contact CML to resolve this issue on their end.


Set up a 'Hello world' project as one app with Webpack

In this branch I achieved the following
Created the App component with react-router and render it in my static view.
Created the Greeting component that will display a greeting. Set it up as a route in my App component.
Created a store, an action, and a reducer that will connect to my API endpoint to get the random greeting.
Display the random greeting in my Greeting component.

Thanks for the review


nitro + mikroorm

Environment

Operating System: Linux
Node Version:     v16.15.1
Nuxt Version:     3.0.0-rc.4
Package Manager<EMAIL_ADDRESS>Typescript: Version 4.7.4
Mikro-orm: 5.2.1
Driver: mariadb

Reproduction
https://github.com/nuxt/framework/issues/5603
Describe the bug
How to work with that if no nex() function
import { RequestContext } from '@mikro-orm/core'

import { DI } from '../data-source'

export default defineEventHandler(async (event) => {
  RequestContext.create(DI.orm.em, () => {
    setTimeout(() => {}, 200)
  })
})

Legacy support is possible using https://github.com/unjs/h3, but it advised to avoid legacy handlers as much as you can.
export default (req, res, next) => {
  console.log('Legacy middleware')
  next()
}

But that also not work.
Additional context
No response
Logs
[nitro] [dev] [unhandledRejection] ValidationError: Using global EntityManager instance methods for context specific actions is disallowed. If you need to work with the global instance's iden
tity map, use `allowGlobalContext` configuration option or `fork()` instead.

https://github.com/nuxt/framework/issues/5603

Tracker for mikroorm for db layer: https://github.com/unjs/db0/issues/50


Transitions User Filter

Context
Determine approach for filtering data that displays in the tree map/matching table

Default set at >1% (bias here is toward quicker rendering?) How could the user change this in a design mockup?
Default at 50 results, but user can call for more (How could the user change this in a design mockup?)

Deliverables:

Create updates to figma and/or other mockup to ensure that the look and feel is setup
Create a follow up issue for implementation.

A note stating that results are all greater than 1%. To see less requires a selection by the user.

Subsumed by other work and requests from our stakeholders

Subsumed by other work and requests from our stakeholders


Antialiasing problem ?

Hi,
I have build the sample app, but I have a quality problem.
Do you have any idea why ?
Thanks in advance !

the library itself works perfect, but PDF might be of low quality, you should try another PDF.

I have same problem. Antialiasing or bad zoom step?

Original:
pokusne02.pdf
pokusne01.pdf

I have the same problem, in my case I created the PDF with itext library, after the creation the PDF is opened with this library, the text is rendered not well, i don't understand why,

Version 2.5.0 introduced Configurator.enableAntialiasing(true) which may fix the problem, otherwise there is no more I can do.


expose registerLinkMatcher api in terminal render

I've noticed that vscode is moving terminal render api to stable.
And I think it would be great if vscode could expose the registerLinkMatcher api for terminal render, since vscode use xterm as the underlying terminal.
By this, extension could be able to more powerful, like ctrl + shift + click to download a sftp file in a custom ssh terminal.

The terminal renderer API will be changing soon, see https://github.com/Microsoft/vscode/pull/67923#issuecomment-471635837
The current thinking to get links working is being able to specify what home is and what the OS is, that way links would even work in Live Share https://github.com/Microsoft/vscode/pull/67923#issuecomment-472937493
As for custom links like you're proposing I don't think we'd want to expose something like registerLinkMatcher as I'm pretty keen on improving that API in https://github.com/xtermjs/xterm.js/issues/583