Fix schema mapping if driver includes default fields

Problem:
Some drivers create fields by default. Fiona is currently not aware of these fields. Additionally, some drivers modify the field names (e.g. Shapefile has a length restriction for field names). Fiona maintains a schema mapping between field names in the schema provided to Fiona, and the resulting field names. However, as the default fields are not considered, the resulting mapping is wrong (see https://github.com/Toblerity/Fiona/issues/916).
This PR fixes the schema mapping if a driver contains default fields. This is kind of a minimal solution, as the existence of default fields also influence the schema validation, which is not touched with this PR. This PR does not modify that only the fields in the schema provided to Fiona are validated.
Currently, schema validation requires that records include all fields of the schema. However, drivers include also "optional" default fields, that do not need to be present. E.g. the default fields for the GPX driver are:
        'GPX': {'properties': OrderedDict([('ele', 'float'),
                                           ('time', 'datetime'),
                                           ('magvar', 'float'),
                                           ('geoidheight', 'float'),
                                           ('name', 'str'),
                                           ('cmt', 'str'),
                                           ('desc', 'str'),
                                           ('src', 'str'),
                                           ('link1_href', 'str'),
                                           ('link1_text', 'str'),
                                           ('link1_type', 'str'),
                                           ('link2_href', 'str'),
                                           ('link2_text', 'str'),
                                           ('link2_type', 'str'),
                                           ('sym', 'str'),
                                           ('type', 'str'),
                                           ('fix', 'str'),
                                           ('sat', 'int'),
                                           ('hdop', 'float'),
                                           ('vdop', 'float'),
                                           ('pdop', 'float'),
                                           ('ageofdgpsdata', 'float'),
                                           ('dgpsid', 'int')]),

E.g. thegeoidheight element is defined with minOccurs="0" in https://www.topografix.com/GPX/1/1/gpx.xsd

Coverage decreased (-0.01%) to 84.238% when pulling 3f41c2aeb9f7928195e597ca6a8dc01484e9da1b on rbuffat:default_fields into 01cfc24367a70ea05be66596ba7f05971881be4c on Toblerity:maint-1.8.

@rbuffat thank you! @snorfalorpagus thanks for the review!


webpack "watchOptions" are not being honored

Version
3.0.5
Node and OS info
Node 8.12.0 / yarn 1.10.1 / Ubuntu 18.04.1
Steps to reproduce

Configure package.json with new command: "watch": "vue-cli-service build --no-clean --watch"
Create vue.config.js file and setup the following:

module.exports = {
    css: {
        sourceMap: process.env.NODE_ENV !== 'production',
    },
    configureWebpack: config => {
        config.watchOptions = {
            aggregateTimeout: 500,
            ignored: ['node_modules'],
        };
    }
};

Run yarn watch
Make a change to any file under node_modules

What is expected?
The watch should not try to build again because files under node_modules should be ignored
What is actually happening?
Another build is running after changing a file under node_modules

Your included option should be:
included: /node_modules/
// or
included: [/node_modules/]

I'm aware that there's an example in the webpack docs looking like this:
watchOptions: {
  ignored: ['files/**/*.js', 'node_modules']
}

But that seems to be wrong. It would have to be 'node_modules/**' I think, or a RegExp like I showed

I used the one recommended but I still get the error
Error: ENOSPC: System limit for number of file watchers reached

trying to watch a lot of files inside node_module.
This is my vue.config.js
module.exports = {
	css: {
		requireModuleExtension: false,
		loaderOptions: {
			sass: {
				prependData: '@import <EMAIL_ADDRESS>			}
		}
	},
	configureWebpack: {
		watchOptions: {
			// ignored: ['node_modules/**']
			ignored: /node_modules/
		},
		module: {
			rules: [
				{
					test: /\.html$/,
					loader: 'vue-template-loader',
					exclude: /index.html/
				},
				{
					test: /\.pug$/,
					oneOf: [
						// this applies to `<template lang="pug">` in Vue components
						{
							resourceQuery: /^\?vue/,
							use: ['pug-plain-loader']
						},
						// this applies to pug imports inside JavaScript
						{
							use: ['raw-loader', 'pug-plain-loader']
						}
					]
				}
			]
		}
	}
};

nobody else has the same problem?

I solved this issue like this:
    devServer: {
      watchOptions: {
        ignored: /node_modules/,
      },
    },

So your full vue.config.js could look like this:
module.exports = {
	configureWebpack: {
		devServer: {
		  watchOptions: {
			ignored: /node_modules/,
		  },
		}
	}
}

I hope this helps!

@pmachaux Thank you! It worked!
Shouldn't it be default?

@shepelevstas glad it helped!
It seems that according to webpack documentation (https://webpack.js.org/configuration/watch/) only the watch is the default with dev server.
My assumption is that in the use case where you add a library, you can use it directly in your source code as the watch on node_modules will pick it up. If you don't, you have to kill the dev server and restart the command to load the new library.

@pmachaux In case of something like npm install... - shouldn't a change in package.json (which is outside of /node_modules) be enough to trigger rebuild?
For some reason configureWebpack.devServer.watchOptions.ignored = /node_modules/ in vue.config.js does not work again if I do vue-cli-service build --mode development --no-clean --watch :-0
Webpack and alike are cool and all, but often I wish for more tools like elm ;-)

@pmachaux In case of something like npm install... - shouldn't a change in package.json (which is outside of /node_modules) be enough to trigger rebuild?
For some reason configureWebpack.devServer.watchOptions.ignored = /node_modules/ in vue.config.js does not work again if I do vue-cli-service build --mode development --no-clean --watch :-0 Maybe this vue.config.js option is working only for ... serve command?
Webpack and alike are cool and all, but often I wish for more tools like elm ;-)

Faced the same issue. no watchOption now working with vue-cli-service build --mode development --no-clean --watch

I am getting error :  ERROR  ReferenceError: node_modules is not defined


fix type name pattern + examples

This way they fit rule 213.
Fixes #648.

👍

:+1:

👍

:+1:

:+1:


Fix code ordering on 18.04 and add new debian gpg key

Change code ordering to work with Ubuntu 18.04 and add new upstream gpg key from Jenkins
Fixes
#920
#971

By default the module doesn't use systemd on Debian/Ubuntu. Did you explicitly choose the systemd service provider as a parameter?

This is now obsolete since the whole transition is gone.


Request for VenusOS/Home assistant compatibilty

Hello,
Great project! I'm new to this so please excuse my lack of knowledge.
Is it possible to use this to add MPP Solar inverter and JKBMS compatibility to Victron VenusOS and/or Home Assistant running on RPI? This would be very useful if possible!
Thanks Paul

this was made to work standalone simply by plugging in an mppsolar inverter and a jk bms.
there is no built-in integration with any other service or system such as victron/home assistant/grafana/etc.
somebody with knowledge of those systems and some C# might be able to just fork this repo and add those integrations since the logic for reading data from inverter/bms is already there.
since i do not have/use any of those systems, i can't make that myself. nor do i have the desire to 😜
if someone wants to have crack at it, i can only answer any specific questions regarding the code i've already written.

this was made to work standalone simply by plugging in an mppsolar inverter and a jk bms. there is no built-in integration with any other service or system such as victron/home assistant/grafana/etc. somebody with knowledge of those systems and some C# might be able to just fork this repo and add those integrations since the logic for reading data from inverter/bms is already there.
since i do not have/use any of those systems, i can't make that myself. nor do i have the desire to 😜
if someone wants to have crack at it, i can only answer any specific questions regarding the code i've already written.

Thanks for your reply!
That's beyond my scope, though someone else might run with it


"Error: JavaFX runtime components are missing" during forked run

steps
sbt version: 1.2.8
JDK version: 11
(I could be missing something, but I've not found anything in the sbt docs about this issue; feel free to point me in the right direction if so.)
I have a test problem that I've uploaded to GitHub, in answer to a question on StackOverflow.
The project depends upon the packages provided by JavaFX 11, which are in the form of modules. (The project consequently needs to be built and executed using JDK 11.)
fork := true

Execute sbt run. (checkout branch forked-problem to demonstrate this)
problem
JavaFX is unable to find its runtime components:
D:\src\javafx11>sbt run
[info] Loading global plugins from {my home directory}\.sbt\1.0\plugins
[info] Loading project definition from D:\src\javafx11\project
[info] Loading settings for project javafx11 from build.sbt ...
[info] Set current project to JavaFX 11 Hello World (in build file:/D:/src/javafx11/)
[info] Running (fork) hello.ScalaFXHelloWorld
[error] Error: JavaFX runtime components are missing, and are required to run this application
[error] Nonzero exit code returned from runner: 1
[error] (Compile / run) Nonzero exit code returned from runner: 1
[error] Total time: 1 s, completed Aug 11, 2019, 3:17:07 PM

expectation
I expected that SBT would be able to successfully specify the location of any required modules in the forked process, automatically, since it is able to find them in its own process.
notes
If the application is run in the same JVM as SBT, then it works fine (checkout branch non-forked to demonstrate this):
D:\src\javafx11>sbt run
[info] Loading global plugins from {my home directory}\.sbt\1.0\plugins
[info] Loading project definition from D:\src\javafx11\project
[info] Loading settings for project javafx11 from build.sbt ...
[info] Set current project to JavaFX 11 Hello World (in build file:/D:/src/javafx11/)
[info] Running hello.ScalaFXHelloWorld
[success] Total time: 4 s, completed Aug 11, 2019, 3:19:09 PM

In order to workaround the problem, since JavaFX should ideally be executed in a forked process, I had to tell the JVM where to find the JavaFX modules, in the local ivy cache, using the JDK 11 --module-path and --add-modules options. The code then works as expected (checkout branch master to demonstrate this):
D:\src\javafx11>sbt run
[info] Loading global plugins from C:\Users\MikeAllen\.sbt\1.0\plugins
[info] Loading project definition from D:\src\javafx11\project
[info] Loading settings for project javafx11 from build.sbt ...
[info] Set current project to JavaFX 11 Hello World (in build file:/D:/src/javafx11/)
[info] Running (fork) hello.ScalaFXHelloWorld
[success] Total time: 5 s, completed Aug 11, 2019, 3:21:49 PM

Would a better solution need the ability to identify modules as part of the required libraryDependencies artifact specification? Or could sbt determine that for itself?
I haven't tested this, as yet, but would this also be an issue for plugins such as the sbt-native-packager, etc.?

@MichaelJAllen Thanks for the report. I might move things around in the description so steps describes the reproduction steps.

sbt currently doesn't really have a clue about Java Modules. I am surprised that in-process run even works, so my expectation doesn't really match yours that sbt would automatically deduce modules out of classpath (libraryDependencies). How do other build tools work in this area?

@eed3si9n Thanks for looking into this, Eugene! I'd also like to take the opportunity to thank you for all your great work on SBT and its plugins. Also, Scopt is a fantastic tool that I use a lot! Thanks!
Given that a library dependency is a library upon which an application depends to run, it seems reasonable to assume that that is still the case even if it happens to identify a Jigsaw module. So even if you don't expect it to work right now, I hope you agree that it ought to work. ;-)
It's a good question how other build tools access modules. So far as I can tell, Maven seems to treat modules as just regular library dependencies, and there don't appear to be any new tags to support modules. (It doesn't help that Maven uses the term module to mean different things, though.) I'll look into that some more...
It appears that JAR files for library dependencies can be identified as modules if they contain a module-info.class file in their JAR root (aside from any support the Java 9+ _API_s might offer). But this begs the question why the JVM still needs the --module-path and --add-modules arguments if each JAR is already accessible on the classpath.
Would it be a valid fix for SBT to recognize such JAR files as modules (if it also detects the use of a 9+ JVM for the build) and add them to the --module-path JVM argument for forked processes automatically? (The --add-modules ALL-MODULE PATH option appears trivial by comparison.)

This might clear things up a bit: https://stackoverflow.com/questions/56774366/whats-the-magic-behind-scalafx-to-make-openjdk-9-actually-work/62001855#62001855
A few weeks ago, stackoverflow user Jonathan Crosmer presented a workaround. Simply choosing different names for the JavaFX Application class and the main object will make things work as expected. I did some digging and may have found the reason for why it works. The short version is that Java treats classes extending javafx.application.Application differently from any other class and in the process only looks for the JavaFX runtime on the module path and not on the classpath.

What's the status on this? Are there any plans for sbt to handle modules?

What's the status on this? Are there any plans for sbt to handle modules?

I am not personally invested in getting Jigsaw support into sbt or Scala ecosystem in general. If someone (or more likely some company) wants to see it happen, they would need to implement it themselves or propose to Scala Center to make it happen. As a genuine question, I don't know what the tradeoffs of fully adopting Java Modules (Jigsaw) are in Scala ecosystem are or if Java Modules in general have been considered a success 5 years since Java 9 was announced.


Broken UI in version 4.0.2

Hi,
I upgraded from version 3.0.2 to 4.0.2. Now, Recurring Job page UI is broken in the 4.0.2 version.

which version of sidekiq are you using?

also, are you using webpacker, sprockets? It would be ideal if you could provide a sample app so we can reproduce your problem
We had a recent issue related to this https://github.com/sidekiq-scheduler/sidekiq-scheduler/issues/364 but it should be fixed

@marcelolx My sidekiq version 6.1.3.

Can you please provide a sample app? My local sample app with sidekiq 6 + sidekiq-scheduler 4.0.2 I don't get this error

@MuhammadRazaAslam  @marcelolx
this pull request may solve this bug
https://github.com/sidekiq-scheduler/sidekiq-scheduler/pull/394

Thanks @houdl! PR merged, can you point you gemfile to the master branch and see if it is fixed @MuhammadRazaAslam?

@marcelolx   it was merged branch  v3-stable , you may need check pick it to master.

@marcelolx   pull request for master  https://github.com/sidekiq-scheduler/sidekiq-scheduler/pull/395

oh 🤦♂ PR merged!

@marcelolx @houdl I have tested it again so it's not fixed yet.

@MuhammadRazaAslam please come up with a sample app simulating your problem, we can't keep trying to guess what is not fixed... Here was someone else that in theory the CSS was broken too and turns out it wasn't https://github.com/sidekiq-scheduler/sidekiq-scheduler/issues/415, so if you come up with a sample app that reproduces your problem we can help, and fix if anything is really broken in the gem, otherwise it is likely that is some config of your application.

@marcelolx Sample App Link: https://github.com/MuhammadRaza29/sidekiq-scheduler-integration

@MuhammadRazaAslam  you can reinstall  sidekiq-scheduler version: 4.0.3, may solve your problem.
i pull your sample app code, bundle install , and could not found 404.
you can check recurring_jobs.css in local.

@MuhammadRazaAslam I did clone your sample app locally and did the following steps, the UI is not broken as can be seen in the screenshot below (same results as the ones shown by @houdl)

git clone https://github.com/MuhammadRaza29/sidekiq-scheduler-integration.git
cd sidekiq-scheduler-integration
bundle install
bin/rails db:setup
bin/rails s
bundle exec sidekiq
Opened the following URL http://localhost:3000/sidekiq
And then did go to the "Recurring Jobs" tab

I did even install the v5 beta version and got the same results.
gem 'sidekiq-scheduler', "5.0.0.beta1"

@MuhammadRazaAslam If you check your application Gemfile.lock which version is installed for the rack gem? The sample app version is rack (2.2.5) but your application version could be lower and the UI is broken in your app because of that? Similar to the problem mentioned here?

@marcelolx @houdl UI is also broken in your screenshots.
It should be
https://raw.githubusercontent.com/sidekiq-scheduler/sidekiq-scheduler/master/images/recurring-jobs-ui-tab.png

@MuhammadRaza29 what is exactly broken? The table? We removed the table here https://github.com/sidekiq-scheduler/sidekiq-scheduler/pull/344

Table columns and borders are missing.

They are not missing, we removed the table intentionally.

@marcelolx Ohh got it but table looks great and it's readable. I think table should be added again.

@MuhammadRaza29 That won't happen.


Alternative of animixplay

Source name
yugen
Source link
https://www.yugen.to/
Language
English
Other details
One of the best alternative for animixplay.
It loads videos very fast and has every anime in 1080p quality.
It would be besg for aniyomi app
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Kamyroll will be best

Thank you! I like the clean UI, if only I could see upcoming schedules for the week, it currently says something about indexing

@Divivats Can you rename the issue title to "Yugen" so the site name is more clearer?

@Divivats Can you rename the issue title to "Yugen" so the site name is more clearer?

Sure


Fixed Windows tests

This PR intent is to augment support for running on Windows.
The current assumption is that all paths will use the posix path separator "/". Windows uses the "" path separator.
I propose that we sanitize the paths and avoid using filePath.Join when composing path like values.

Search returned chart names with "". Fixed to always return names with "/" to meet the expectations of the product.
Fixed all the test to run on Windows

This change is

Wow, this is fabulous! Thanks. I left one comment about the path.Join thing, and otherwise this all looks great to me. @mattfarina had suggested a way we could run automated tests on Windows to match the CircleCI. This would certainly get us closer. #1606

@technosophos Will updating the fix for path.Join, I ran into a problem with the plugins tests. Currently the plugin are all written using the assumption that bash script can be run directly on the OS. Unfortunately, on Windows this is not the case. I was thinking to skip the test for the time being and open a issue to support this (we could detect that the script is a bash script and prefix the command with bash to make it run on Windows as well). Any thoughts?

@rodcloutier I am going to merge this as-is, then. Let me know what you think about #1638, and if that will help make plugins better I will work on that.


Added social links to Skype and Telegram

Closes https://github.com/arifszn/gitprofile/issues/305

@csarnataro please resolve the conflicts as the main branch has been updated.
Also, please add the prop definition like this.

@csarnataro please resolve the conflicts as the main branch has been updated.
Also, please add the prop definition like this.

It should be ok now.


Fix template optional field parsing

Fix #665

very cool. will try it out.

It's more "fixing rampant stupidity" than "very cool", to be honest, but hopefully it will solve the issue :)


Assemble project on each push on CI

As discusses in this PR this will add a GitHub Actions to the repo.
For the first step it will simply use the macos runner (which has preinstalled Xcode (for the iOS build) and the Android SDK (for the android build)). It has also preinstalled Java and stuff. See also this help page for more information.
I simply added the assemble task to test if everything works correctly.
But I guess we need some fine grained tasks here.
Maybe the testReleaseUnitTest to test the Android stuff and testiOS for the ios stuff.
But I'm not sure if the simulator is preinstalled and run out of the box.. so for now assemble is good enough I guess.

An example can be found on my fork:
https://github.com/StefMa/kotlin-mpp-example/commit/e319a034411f2876e01c8197eefa5b2079d989f5/checks?check_suite_id=378271375


can not draw by wacom

I see it is a good whiteboard but when I try to use a pen from Wacom to write(draw) something. i see it can not draw anything.
are you have a plan to support pen?

Thanks, we currently do not have development for Wacom / Pen support in our roadmap.

Thanks, we currently do not have development for Wacom / Pen support in our roadmap.


Documentation Updates

What are our thoughts on modernizing the documentation? I'm happy to do the work, I'd just like to see if it's agreed this is a good idea.
I'd like to

Convert the README to markdown, so we can have built-in links and code blocks
Add install instructions that include vim.org, using Vundle, building from source etc
Refactor the changelog into a separate file (?)

Thoughts?

Am 2016-11-22 13:12, schrieb Michael Milton:

What are our thoughts on modernizing the documentation? I'm happy to
do the work, I'd just like to see if it's agreed this is a good idea.
I'd like to

Convert the README to markdown, so we can have built-in links and
code blocks
Add install instructions that include vim.org, using Vundle,
building from source etc
Refactor the changelog into a separate file (?)

Thoughts?

Sounds reasonable. I'd appreciate help here. Thanks!

Convert the README to markdown, so we can have built-in links and code blocks

I hate to be the opposite of change, but I personally like text files so I can read it in more/less/vim without seeing markdown code blocks.

@jungle-boogie I see your point but if you want the help in a text format I think you should be using the vim help (:h) anyway. This seems to be a separate file to the README: https://github.com/chrisbra/csv.vim/blob/master/doc/ft-csv.txt

Okay, I've done most of the work. What do we think about this:
https://github.com/TMiguelT/csv.vim/blob/master/README.md
I think the best part is the animated gif at the top!

Hi Michael!
On Do, 24 Nov 2016, Michael Milton wrote:

Okay, I've done most of the work. What do we think about this:
https://github.com/TMiguelT/csv.vim/blob/master/README.md
I think the best part is the animated gif at the top!

Very nice thanks you. Some notes:

The vim-airline link is wrong, it should be vim-airline/vim-airline
Something in the first code block here:
https://github.com/TMiguelT/csv.vim/blob/master/README.md#calculate-new-columns
is missing
here
https://github.com/TMiguelT/csv.vim/blob/master/README.md#header-lines
and here
https://github.com/TMiguelT/csv.vim/blob/master/README.md#vertical-folding
you have vim:VHeader 2 the vim looks wrong
Some data uses still vim help highlighting, e.g. trailing ~ and `,
e.g. the part after: "consider this data:" here
https://github.com/TMiguelT/csv.vim/blob/master/README.md#transforming-into-a-table
Average column is missing. I have probably caused this when I updated
the documentation yesterday. Sorry for that.
That line of the Makefile:
https://github.com/TMiguelT/csv.vim/blob/master/Makefile#L41
needs to be removed
Perhaps move the changelog to a separate Changelog (don't need some
fancy highlighting there, it should be just for documentation
purposes)

Overall I really like the result. Thanks you very much.
Best,
Christian
Streusand her, da dreht einer durch.

I've fixed the things you mentioned. Tell me if you find more issues.
I suppose the ongoing problem is going to be updating both this and the vim help file. Admittedly if you're only doing it one feature at a time it won't be so bad (like the average feature you added yesterday). The ideal solution would be writing a converter from the vim help format to markdown but that would be a nightmare. I hope the project is stable enough that this won't be a problem.
I think having a markdown readme will really help the visibility of the project, however.

Hi Michael!
On Do, 24 Nov 2016, Michael Milton wrote:

I've fixed the things you mentioned. Tell me if you find more issues.
I suppose the ongoing problem is going to be updating both this and the vim help file. Admittedly if you're only doing it one feature at a time it won't be so bad (like the average feature you added yesterday). The ideal solution would be writing a converter from the vim help format to markdown but that would be a nightmare. I hope the project is stable enough that this won't be a problem.
I think having a markdown readme will really help the visibility of the project, however.

Yeah, I think I can handle it. There haven't been too many updates to
the csv filetype, because I basically consider it feature complete.
Best,
Christian
Der Mensch ist gut und will nicht, daß man vor einem andern als ihm
selber krieche.
-- Jean Paul


Remove concept of "Population level HSI" events (and remove logic in HealthSystem accommodating for them)

These are not used in the model and the accommodation for their possibility in the HealthSystem is making further changes more difficult.

Linked to Issue #1260


Move/resize named window

The window command only works with the focused window as far as I can see. Is it possible to resize and move a window by title?
Something like yabai -m window title="^MyTitle.*$" --resize=abs:1000:1000

I've spent quite some time trying to figure this one out. I somehow thought it could be done with a rule, but then I couldn't figure out how to trigger the rule... Anyway, I agree that it would be nice to have a simpler command for selecting named windows, i.e. something similar to how rules work.
For example, instead of
yabai -m query --windows |
  jq '.[] | select(.title | test("^MyTitle.*$")).id' |
  xargs -I{} yabai -m window {} --resize abs:1000:1000

something like
yabai -m window title="^MyTitle.*$" --resize abs:1000:1000

something like
yabai -m window title="^MyTitle.*$" --resize abs:1000:1000

The "problem" with this syntax is that there are a lot of properties (and combinations of properties) that may be interesting to filter by, and mixing it straight into the command structure like this makes it both complicated to read, and potentially to parse.
If filters are allowed in-place instead of a WINDOW_SEL, then it would have to be allowed every place that currently allows a WINDOW_SEL, to maintain consistency (and simplicity) in the CLI.
In theory that means that the parser would have to allow for, and understand, something like the following (even though it might not make sense from a practical pov):
yabai -m window title="^MyTitle.*$" app="^MyApp.*$" space=1 --swap title="^OtherTitle.*$" app="^OtherApp.*$" space=2
I think the above command would be ambiguous from a parser pov, unless extra context is given. Not saying that it would be impossible, but I think it makes things a lot more complex both from a user pov and certainly from an implentation-pov.
The thing that is great about the current design is that you know how to issue commands that affect certain entities (windows, spaces, displays) using very simple syntax, and when more complex needs arises, there is a standard way to retrieve the information that you need to script that behaviour.

Thanks a lot for explaining. It makes more sense now. I am looking at this from the perspective of someone who is not a software engineer and who has just started using yabai. I can't tell, at this point, whether I would prioritize consistency over ease of use, but if that's what you want to do, that's obviously fine.
From my perspective, another way of making yabai easier to use would be to simply highlight this design decision in the documentation. Of course, you can say that all the information is already there, but it still took me quite a while to figure out the importance of the query command. As someone who is getting started with yabai, it felt like that would be for more sophisticated setups so it didn't occur to me for a while that I really need to jump through that hoop to select a window by its title. So I think it might help users to have that clarified more explictly early on in the docs, even if it may seem redundant to more experienced users.
As I think more about it, I think I might be able to turn around your consistency argument to argue for a simplification of selecting named windows: what about allowing labels for windows? Why should WINDOW_SEL not accept LABEL? If that were added, it would at least allow us to query windows once, label them, and then refer to them via their label...

Thanks a lot for explaining. It makes more sense now. I am looking at this from the perspective of someone who is not a software engineer and who has just started using yabai. I can't tell, at this point, whether I would prioritize consistency over ease of use, but if that's what you want to do, that's obviously fine.

I think it is important to have an interface that is easy-to-understand in terms how to do things. I agree that adding a single option that would let you select a window by its title as proposed is easier for the specific thing you are trying to do here, but from an overall design pov it makes things more unclear; as in there are now multiple ways of doing the same thing, but only when some properties are applied -- it makes the interface convoluted over time.

From my perspective, another way of making yabai easier to use would be to simply highlight this design decision in the documentation. Of course, you can say that all the information is already there, but it still took me quite a while to figure out the importance of the query command. As someone who is getting started with yabai, it felt like that would be for more sophisticated setups so it didn't occur to me for a while that I really need to jump through that hoop to select a window by its title. So I think it might help users to have that clarified more explictly early on in the docs, even if it may seem redundant to more experienced users.

I agree that it could certainly be outlined with more info/samples in the wiki, but it is not really high on my priority list. I don't spend too much time on this project these days, and would rather do programming when I do make time for it. The wiki used to be open for the community to edit, but people made changes that made things incorrect, and I would have to spend a lot of time to continually review said changes and revert them, which is why I locked it down.

As I think more about it, I think I might be able to turn around your consistency argument to argue for a simplification of selecting named windows: what about allowing labels for windows? Why should WINDOW_SEL not accept LABEL? If that were added, it would at least allow us to query windows once, label them, and then refer to them via their label...

No reason really, I just haven't implemented it yet. For consistency reasons, as you mention, it should be possible to allow labelling both windows and displays as well (all "entities"). The labelling spaces thing was added as a quick experimental thing, and the label-system is not completely fleshed out yet. I believe there are some open issues regarding it and allowing for default labels when none are specified and so on. No ETA for when that will be a priority though.


how to use Grape::Entity in api-pagination?

desc "最新Tweet 验证：是 可选参数：:page 返回第page页的数据 and :per_page 每页返回per_page条数据 默认5条"
    paginate per_page: 5, max_per_page: 20
    get do
      authenticate!
      #present current_user.feed, with: APIEntities::Tweet
      paginate current_user.feed, with: APIEntities::Tweet
    end

this has a error
ArgumentError (wrong number of arguments (2 for 1)):

present paginate(current_user.feed), with: APIEntities::Tweet
You still need to call present, paginate will only scope your query.

@eidge is right; the Grape pagination just scopes the query and sets up headers. You'll still need to use your own presenter if you want. Thanks, @eidge!

@eidge , @davidcelis thanks for your help!


Fix math_funcs.h formatting

Currently, it is inconsistent with Clang format (version 14.0)

That's a bug in clang-format 14.0.0, it shouldn't be used. It's fixed in 14.0.2+.
https://github.com/llvm/llvm-project/issues/54901


Boolean false evaluates to true

This Eve program works on ts-merge, except that the buttons always say "Locked". The problem is that if locked then "Locked" else "Unlocked" always evaluates to "Locked", even if locked is false. I fixed it by writing if locked = true then ....
It took quite a lot of digging to figure that out. Fingers crossed that your announcement this week is a database viewer, or something Theseus-esque. :)

Two-Man Rule
Model
Create two locks.
commit @model
  [#lock name: "Lock 1", locked: true]
  [#lock name: "Lock 2", locked: true]

Unlock locks when their key is turned.
search @event @model
  [#turn-key name]
  lock = [#lock name]
commit @model
  lock.locked := false

Emit an event when both locks have been unlocked.
search @model
  [#lock name: "Lock 1", locked: false]
  [#lock name: "Lock 2", locked: false]
commit @event
  [#all-unlocked]

View
Display buttons for each of the locks.
search @model
  [#lock name locked]
  state = if locked then "Locked" else "Unlocked"
bind @browser
  [#button name, text: "{{name}}: {{state}}"]

When a button is clicked, turn its key.
search @event @browser
  [#click element: [#button name]]
commit @event
  [#turn-key name]

Display a crazy awesome message when everything's unlocked
search @event
  [#all-unlocked]
commit @browser
  [#h1 text: "The door is open!"]

Hey Tom,
Thanks for posting. This is actually working as intended. That probably seems surprising at first, particularly for people with strong procedural backgrounds. The reason while the block succeeds is not actually because false evaluates to true, but because locked tautologically exists (or we'd never have reached the if in the first place!). Since we are a pattern matching language, conditionals are built around patterns. When you changed the if's body to locked = true, you gave us a more interesting pattern to work with, which matched only when lock was true.
Along with being more powerful in pattern-land, this also lets us neatly sidestep the issue of falsiness. Unlike a language such as JavaScript, where undefined, false, and 0 evaluate to false (leading to all sorts of interesting to debug errors), we require explicitness.
Hope that clears up the confusion, though if you're interested in debating this decision specifically or the semantics in general we'd love to hear from you over on the mailing list.

As an aside, it's probably worth erroring in this case - it never makes sense to have a bare identifier in an if branch.
@alltom great work on Theseus - I've followed it since it first came out. :) Your hopes should be answered... and then some with the release.


confusing 'crop' paramters

Currently the parameters for the crop() function are described as:

left, top, right, bottom {Integer}: Coordinates of the crop rectangle.

This suggest there need to be 4 coordinates (2 integers each) for all 4 corners. That is not true.
The parameters are actually described as:

x0 = X-coordinate of the upper-left crop rectangle corner.
y0 = Y-coordinate of the upper-left crop rectangle corner.
x1 = X-coordinate of the lower-right crop rectangle corner.
y1 = Y-coordinate of the lower-right crop rectangle corner.

I recommend using these parameter names instead to avoid confusion.

This suggest there need to be 4 coordinates (2 integers each)

There are 4 parameters, not 8...
"top-left" might describe a corner, but "left" does not.
Thanks for the comment @jomo, but I don't see the confusion.
I'll definitely consider changing the terminology if more people find it confusing.

There are 4 parameters described as 'Coordinates', but 'Integers' at the same time. Coordinates are always a pair of two Integers, that's why I found it confusing.
Most confusing, however is that 'right' or 'bottom' is not a very descriptive parameter name, because they're the x and y position (counted from left and top, not right and bottom).
Take a look at this table:

left
top
right
bottom

x0
y0
x1
y1

It's not obvious how those names map to their actual meaning.
right-bottom-x, right-bottom-y would make sense, but right, bottom does not.
You could also use left0, top0, left1, top1.
The parameter names used by cimg are much more descriptive because it makes clear:

xn and yn are a pair of coordinates
they're x and y coordinates

Sorry if it wasn't clear what I meant in the first comment.


Fix the publish error response

Summary

Move to uber Gomock
Fix publisher error response frame

make tests-ci works but there is some problem with   make tests, am i missing something ?
• [FAILED] [0.016 seconds]
Environment [DeferCleanup (Each)] delete stream when there are multiple locators uses different locators when one fails [flaky]
  [DeferCleanup (Each)] /Users/gas/go/pkg/mod/go.uber.org/mock@v0.2.0/gomock/controller.go:102
  [It] /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/environment_test.go:230

  Timeline >>
  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.408

  Attempt #1 Failed.  Retrying ↺ @ 08/01/23 14:45:24.408

  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.413

  Attempt #2 Failed.  Retrying ↺ @ 08/01/23 14:45:24.413

  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.418
  << Timeline

  [FAILED] missing call(s) to *stream.MockRawClient.IsOpen() /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/environment_test.go:226
  In [DeferCleanup (Each)] at: /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.418

  There were additional failures detected.  To view them in detail run ginkgo -vv
------------------------------
↺ [FLAKEY TEST - TOOK 3 ATTEMPTS TO PASS] [0.020 seconds]
Environment query stream stats when there are multiple locators gives up on non-retryable errors [flaky]
/Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/environment_test.go:402
------------------------------
• [FAILED] [0.023 seconds]
Environment delete stream when there are multiple locators [It] gives up on non-retryable errors [flaky]
/Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/environment_test.go:248

  Timeline >>
  [FAILED] in [It] - /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74 @ 08/01/23 14:45:24.416
  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.419

  Attempt #1 Failed.  Retrying ↺ @ 08/01/23 14:45:24.421

  [FAILED] in [It] - /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74 @ 08/01/23 14:45:24.425
  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.427

  Attempt #2 Failed.  Retrying ↺ @ 08/01/23 14:45:24.427

  [FAILED] in [It] - /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74 @ 08/01/23 14:45:24.433
  [FAILED] in [DeferCleanup (Each)] - /usr/local/go/src/reflect/value.go:584 @ 08/01/23 14:45:24.434
  << Timeline

  [FAILED] Unexpected call to *stream.MockRawClient.IsOpen([]) at /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74 because: there are no expected calls of the method "IsOpen" for that receiver
  In [It] at: /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74 @ 08/01/23 14:45:24.433

  There were additional failures detected.  To view them in detail run ginkgo -vv
------------------------------

Summarizing 2 Failures:
  [FAIL] Environment [DeferCleanup (Each)] delete stream when there are multiple locators uses different locators when one fails [flaky]
  /usr/local/go/src/reflect/value.go:584
  [FAIL] Environment delete stream when there are multiple locators [It] gives up on non-retryable errors [flaky]
  /Users/gas/go/src/github.com/rabbitmq/rabbitmq-stream-go-client/pkg/stream/locator.go:74

Ran 35 of 36 Specs in 0.065 seconds
FAIL! -- 33 Passed | 2 Failed | 1 Flaked | 0 Pending | 1 Skipped

Ginkgo ran 4 suites in 8.881112987s

There were failures detected in the following suites:
  stream ./pkg/stream

Test Suite Failed
make: *** [tests] Error 1
➜  rabbitmq-stream-go-client git:(zerpet/fix-publish-error) ✗

We could add an e2e test to trigger all possible errors from the broker 🤔 I'll create an issue for that


Error handler on route level

https://github.com/apache/camel/pull/13489

https://issues.apache.org/jira/browse/CAMEL-20666
https://issues.apache.org/jira/browse/CAMEL-20667


Snapshot add_photos destination location

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
The snapshot README says that you can use the add_photos option to add photos to the simulator before running snapshot, but it doesn't tell how to use them, where are they added, how to load them in code.

This will add the screenshots to the photo library of your iOS simulator, so you can access them from within your app. This is UI Testing related, and not something fastlane would do 👍

I understand. Do you consider that your answer could find a place in the readme? Or a link to a UI Testing documentation that explains the add_photos? It would greatly help new users to understand that fastlane's add_photos is just a wrapper over a native command.

@revolter We'll add this to our docs requests. Thanks!


Update CSS of Altimetry

This pull request changes how altitude profiles look. Right now, they look like this:

After this change, they will look like this:

As a result, the altitude profile will show higher up on the page, which let some space for the attribution mark.

@Huquette the PR seems good to me. I'd like to test the feature before approving the merge. I suggest we discuss it this afternoon to test it, especially in mobile / tablet views and if it's concluant you'll merge.


postfix-ldap required for ldap lookup type on RHEL8+

Pull Request (PR) description
Install postfix-ldap package when ldap=true on RHEL8+
This Pull Request (PR) fixes the following issues
Fixes #397

Wouldn't it be better to use the module's hiera data for this kind of thing rather than using conditionals in code?

+1: some Array[String[1]] $ldap_packages parameter with the right default values in hiera and a `package { $postfix::ldap_packages: ensure => installed }' in the manifest seems more flexible.

Absolutely, I was just trying to get something down. If I get some time tomorrow I will update it.

Made the suggested changes.
One thing I have been struggling with when using this module. I find a few options that would appear at first to be useful for me, but end up being too opinionated. $mta and $ldap are both examples.
In the case of $ldap I want my ldap lookups to be a part of 'virtual_alias_maps' instead of 'alias_maps', but if $ldap = true the ldap config file is added to the 'alias_maps' option.
I also can't use $mta because if $mta = true then 'virtual_alias_maps' is set for me.
I see the merit of building in some common opinionated scenarios, maybe this is more of a documentation issue. If the docs had some callout to "these options are equivalent to" or "opinionated setup of" I think I would have arrived where I am now much faster.
Specifically for $ldap it may make sense to separate out the installation of the $ldap_packages so that you can still "enable ldap" without doing everything that setting $ldap to true does. Anything that separates out "making postfix ready to use ldap" from "configuring how postfix uses ldap"

One thing I have been struggling with when using this module. I find a few options that would appear at first to be useful for me, but end up being too opinionated. $mta and $ldap are both examples.

I quite agree. On one hand some interfaces are really not great IMHO, but on the other hand we don't want to break the setup of users of the module.  It is hard to change things when they are done in a certain way.  That being said, I think that all efforts to make diving in with the module are good to have.  Feel free to send PRs.


Unexpected behaviour when watching

Version
1.0.0-beta.13
Reproduction link
https://github.com/tbuteler/vue-test-utils-issue
Steps to reproduce
Clone the repository, then run:
yarn install
yarn run tests

What is expected?
Component:
<template>

data.text: {{ text }}

computed.text: {{ computedText }}

</template>

Test:
import { shallow } from '@vue/test-utils'
import App from '../src/App.vue'

describe('App.vue', () => {
  it('updates computed properties', () => {
    const wrapper = shallow(App)
    expect(wrapper.vm.text).toBe('')
    expect(wrapper.vm.basket).toEqual([])
    wrapper.setData({ text: 'foo' })
    expect(wrapper.vm.text).toBe('foo')
    expect(wrapper.vm.computedText).toBe('foo')
    expect(wrapper.vm.basket).toEqual(['foo']) // Fails
  })
})

In the text watch handler, I expected the computed property to have been updated to the latest value of text.
What is actually happening?
The computed property is somehow lagging behind. Curiously, this only happens when the computed property is actually being rendered inside the template, otherwise it behaves as expected.

This issue was not present in 1.0.0-beta.12, regardless of what the template contains. From the release information, I would suspect it has something to do with the new sync functionality.

This is a bug caused by dependencies running  in the incorrect order. I've created  a fix  that  will  be released in the next version.
For the moment, you will  need to  set  sync to false and use  Vue.nextTick:
it('updates computed properties', (done) => {
  const wrapper = shallow(App, {
    sync: false
  })
  Vue.nextTick(() => {
    expect(wrapper.vm.basket).toEqual(['foo']) // Fails
    done()
  })
})

Alternatively, you can use beta.12.

Thanks for the quick response, Edd.
I ran your solution locally and though it fixes the original reproduction repository's test, my own tests were still failing. I've pushed an update to the reproduction repository with a bit more code which causes it to fail again. Namely, showing the content conditionally on a user click, then attaching the test component to the document with attachToDocument: true.
(For context, I'm testing a searchable dropdown component, so the test above mimics this behaviour).
What this seems to do is trigger the watcher once on click, before the setData will trigger it again. That earlier trigger seems to cause the computed property to fail to update (as before the fix).

Should I open a new issue? Or is the second scenario something that falls outside the use-case and won't be fixed?

This should be fixed in #510. If you  could try the branch it would be appreciated!

Tested this today with my actual suite and its components, which are far more complex than the examples above and everything worked as expected. Thanks for your effort!


[UWP] Cherry pick base64 decode performance improvements

Fixes #4192
Original PR: #4193
Microsoft Reviewers: Open in CodeFlow

@paulcam206 does the release/1.2 branch actually need the UWP CI to be executed manually?

/azp run AdaptiveCards-.NET-PR [release 1.2]

/azp run AdaptiveCards-UWP-Daily-PRs [release 1.2]


Refactor empty state handling across tables; implement tests

Implements https://issues.redhat.com/browse/CCXDEV-8280, https://issues.redhat.com/browse/CCXDEV-8242
Mainly refactors how table components are handling empty states. Also adds tests to check that the empty state titles, messages, and icons are rendered correctly.

[x] Test "no match" empty states in each table
[x] Check headers always displayed
[x] Check icons are not rendered (only title and text body): https://marvelapp.com/prototype/g70a1he/screen/82026901

Some illustrations:

@RedHatInsights/team-interact, @ikerreyes, please take a look 👋🏼

Codecov Report

Merging #302 (92881de) into master (f081996) will decrease coverage by 0.49%.
The diff coverage is 87.87%.

:exclamation: Current head 92881de differs from pull request most recent head e665fa8. Consider uploading reports for the commit e665fa8 to get more accurate results

@@            Coverage Diff             @@
##           master     #302      +/-   ##
==========================================
- Coverage   85.65%   85.16%   -0.50%
==========================================
  Files          24       24
  Lines         962      984      +22
  Branches      351      359       +8
==========================================
+ Hits          824      838      +14
- Misses        138      146       +8

Impacted Files
Coverage Δ

src/Components/Cluster/Cluster.js
100.00% <ø> (ø)

src/Components/MessageState/EmptyStates.js
85.18% <77.77%> (-3.71%)
:arrow_down:

src/Components/ClusterRules/ClusterRules.js
84.43% <86.66%> (-0.42%)
:arrow_down:

...nts/AffectedClustersTable/AffectedClustersTable.js
88.97% <88.23%> (-1.11%)
:arrow_down:

src/Components/RecsListTable/RecsListTable.js
79.79% <90.00%> (-0.31%)
:arrow_down:

.../Components/ClustersListTable/ClustersListTable.js
83.20% <90.90%> (-0.52%)
:arrow_down:

src/Components/Loading/Loading.js
100.00% <100.00%> (ø)

src/Components/MessageState/MessageState.js
100.00% <100.00%> (ø)

src/Components/ClusterHeader/index.js
100.00% <0.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f081996...e665fa8. Read the comment docs.

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


⚠ instagram has degraded performance

In 0c3f08d, instagram (https://www.instagram.com/9renpoto/) experienced degraded performance:

HTTP code: 200
Response time: 1493 ms

Resolved: instagram performance has improved in 0e5bfbd after 15 days, 9 hours, 57 minutes.


[feature] Properly handle alphatest and alphatestreference flags

Is your feature request related to a problem? Please describe.
Currently alpha testing discards a hit when alpha is zero, which doesn’t match source
Describe the solution you'd like
Check material flags and data in the intersection function

I was already checking the flag, just need to compare with $alphatestreference


Unable to backup Postgres 11.1 due to parsing errors

Hey,
@youssb and I were trying to perform backups of Concourse (using Postgres 11.1 - release v33) and running bbr deploy [...] backup [...] returned the following error:
2018/12/27 18:05:39 Unable to check version of Postgres: could not parse semver: "11.1" - exit code 1

Our guess is that there's a parsing issue happening under version_detector.go:
https://github.com/cloudfoundry-incubator/backup-and-restore-sdk-release/blob/c735374dd73f26932afc39510bc0156902c1ad36/src/github.com/cloudfoundry-incubator/database-backup-restore/postgres/version_detector.go#L28-L30
Looking at ci, there's no v33 (pg 11.1) there, so I guess that's because it's supposed to not be supported yet - is that right?
Please let me know if there's any way that we can help 😁
Thanks very much!

Hi @cirocosta, You are totally right. We do not support Postgres v11 in our sdk release currently.  Is Postgres v11 the default db in current concourse?
Cheers,
Chunyi

Hey @ChunyiLyu ,
The Concourse release doesn't specify an upper limit on the version, just a lower (9.5), so in our pipelines, we always test against the latest version that's out there (v11 right now).
This is currently not a blocker for us, but it'd be nice if we could have that in - we're improving our BBR support right now.
Thanks!

Support introduced in https://github.com/cloudfoundry-incubator/backup-and-restore-sdk-release/releases/tag/v1.15.0


Shortcut for clearing integrated Terminal is no longer mapped

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.80.0 stable / 1.81.0 insiders
OS Version: macOS Ventura 13.4

Steps to Reproduce:

Open Terminal
Focus the Terminal
Attempt shortcut [cmd]+[k]

Below shows that a keymapping for [cmd]+[k] exists.

Below shows the context menu's clear command missing a shortcut.

See https://code.visualstudio.com/docs/terminal/advanced#_macos-clear-screen for why cmd+k might stop working


iojs support

Dont set buffer length explicitly to null. Setting it to null causes some versions of node & iojs to interpret it as 0, causing buffer to be truncated. This closes https://github.com/wvanbergen/node-vertica/issues/36

Awesome, thanks for fixing!


[nat64] support OTBR_NAT64_BORDER_ROUTING and OTBR_BORDER_ROUTING_NAT64

https://github.com/openthread/openthread/pull/7836
Per discussions, we decided to change the OTBR_BORDER_ROUTING_NAT64 to OTBR_NAT64_BORDER_ROUTING to avoid confusion with coming OT_NAT64_TRANSLATOR
Please verify https://github.com/erjiaqing/openthread/runs/8012711714 is green before merging this.

@jwhui PTAL


Feedback for “Install”

After installing on mac os with homebrew, I get:
% dcli
node:internal/bootstrap/realm:420
if (!mod) throw new TypeError(Missing internal module '${id}');
^
TypeError: Missing internal module 'internal/modules/cjs/helpers'
at requireBuiltin (node:internal/bootstrap/realm:420:19)
at pkg/prelude/bootstrap.js:1884:12
at pkg/prelude/bootstrap.js:1986:3
at pkg/prelude/bootstrap.js:2259:3
at readPrelude (node:internal/bootstrap/pkg:36:12)
at node:internal/bootstrap/pkg:41:18
at node:internal/bootstrap/pkg:48:4
at node:internal/bootstrap/pkg:49:2
Node.js v18.19.0
---- How should I fix this?

Duplicate of #211. Follow the other issue please, thanks!


All images must be cutout before further processing. How can I skip the cutout step?

All images must be cutout before further processing. How can I skip the cutout step?

You can just comment out the line that says input_fg, matting = run_rmbg(input_fg) in the process_relight function in gradio_demo.py, so the function looks like this:
@torch.inference_mode()
def process_relight(input_fg, prompt, image_width, image_height, num_samples, seed, steps, a_prompt, n_prompt, cfg, highres_scale, highres_denoise, lowres_denoise, bg_source):
    #input_fg, matting = run_rmbg(input_fg)
    results = process(input_fg, prompt, image_width, image_height, num_samples, seed, steps, a_prompt, n_prompt, cfg, highres_scale, highres_denoise, lowres_denoise, bg_source)
    return input_fg, results


peerflix unsresponsive when using -l option with magnet link

Last version, when using -l with magnet link, select file, press enter and it hangs - 0/0 peers not downloading, and can't even exit - not reaction to pressing q or even ctrl + c or ctrl + d - only way to quit is to "killall -9 peerflix" in another console...
I guess patch that implemented -l selection is bugged, also i think it was a bit overkill to wipe -l in in original way... -l means list content... not select... i think it ( -l) should be returned in in original way(because it useful in many situations when peerflix used as part of something), and fixed list with select implementation should be used with another flag... like -s, or -l -s.
Also maybe reason of this bug is the same as in https://github.com/mafintosh/peerflix/issues/189 issue.

Also after using -l even after restart without -l it still not doing anything - but ctrl -c and q ...etc.. is working. Only way to make it work it to "rm -rf /tmp/torrent-stream/*"
So maybe it not problem in -l patch, but it was bug somewere else.

hmm. it's working for me locally. what os are you on?

Ubuntu 14.04.2 LTS
did npm update -g after initial test, still same result.
Also made small mistake in initial issue - peerflix becomes unresponsive only after chosing file with pressing "enter".
Also made another test - when using not magnet link but direct link to torrent file - after selection and "enter" - downloading starts and i can view it with vlc, but peerflix intance still unresponsive - same as before only way to kill it - with killall -9 peerflix in another console

I'm having this issue as well on OS X 10.10.3.

I'm the other way around, if I omit the -l it exits right after showing the "0/0 peers" message.
But when -l is used to select the file to stream over HTTP, it works normally.

I'm having the @godDLL 's problem, too.


Thread 1: signal SIGABRT

按照文档一步步走下来运行的时候出现这个问题

I'm sorry, I don't understand Chinese. But if any I'd need more information, for example the full log output to be able to diagnose this issue.


view_supplier_declaration: enable view for "expired" frameworks

This started out as https://trello.com/c/R9x4f7te but as you can see from that ticket this morphed a bit.
What we're now doing is enabling the "view declaration" view for expired frameworks. This was previously prevented (which is what was causing the 403 mentioned in the ticket).
This also makes sure supplierFrameworks which don't have a declaration don't even show in the table on the supplier_details page, as there's nothing useful that can be done with such supplierFrameworks from here.

That is a good question.

Something funky with the git history is causing issues with Travis https://www.scivision.dev/travis-ci-git-depth-reference-not-a-tree/

I'm not sure it's worth reconfiguring Travis for this, we could just ignore the status check

Also happening for me on https://github.com/alphagov/digitalmarketplace-utils/pull/536

It fixed itself? 🤔

:balloon:


bundled httpretty: re-normalize headers after executing callable_body

I won't give the whole lecture about bundling dependencies, but I will say that when I've really had to bundle a modified dependency I've found it effective to point to it through a git submodule, allowing the forked lib to exist as its own repo which can have updates merged back & forth from the upstream with ease. The fix for this appears to have been in the upstream httpretty for quite some time.
Without this patch, in python 3.4, a HEAD request to an S3 object will return duplicate content type headers (Content-Type and content-type). Which is really weird to debug.
I haven't fully investigated why this only appears to happen in py3.

Coverage remained the same at 93.729% when pulling f23a6954cc45edd2fa2a296b880aad1cd20f469e on risicle:py3-normalize-headers-after-callable-body into df84675ae67e717449f01fafe3a022eb14984e26 on spulec:master.

Thanks for this, @risicle. In case it helps would you mind making an attempt to create a PR with httprety as a git submodule at the latest stable release?

I'll put this on my todo list...

Thanks for this!
Unfortunately, there are issues with the newest version of HTTPretty (lack of Py3 compatibility) which has forced us to bundle an older version. Fortunately, our time with HTTPretty should be limited as it is only used in non-server, old-boto mode.


test bounding cube

is there a way to test visibility of a bounding cube instead of testing all the composing triangles of the bounding cube??
Thanks

TestRect would be the preferred way.
An example of using this function is given in the companion sample https://github.com/GameTechDev/OcclusionCulling in the file https://github.com/GameTechDev/OcclusionCulling/blob/master/TransformedAABBoxAVX.cpp, look for function TransformAndPreTestAABBox line 165.


Multiple files

Hi, can we upload multiple files to the chat?

Currently , File Uploading seems to be not working as expected , As Claude changed many limitations for api requests.. that too will be fixed soon :) !

Currently , File Uploading seems to be not working as expected , As Claude changed many limitations for api requests.. that too will be fixed soon :) !

Traceback (most recent call last):
  File "D:\proj\test.py", line 111, in <module>
    claude_api = Client(cookie)
                 ^^^^^^^^^^^^^^
  File "D:\app\miniconda3\Lib\site-packages\claude_api.py", line 12, in __init__
    self.organization_id = self.get_organization_id()
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\app\miniconda3\Lib\site-packages\claude_api.py", line 30, in get_organization_id
    response = requests.get(url, headers=headers,impersonate="chrome110")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\app\miniconda3\Lib\site-packages\curl_cffi\requests\__init__.py", line 46, in request
    return s.request(
           ^^^^^^^^^^
  File "D:\app\miniconda3\Lib\site-packages\curl_cffi\requests\session.py", line 438, in request
    raise RequestsError(e)
curl_cffi.requests.errors.RequestsError: Failed to perform, ErrCode: 35, Reason: 'BoringSSL SSL_connect: Connection was reset in connection to claude.ai:443 '

I met this problem using v1.0.5, do curl_cffi and vpn conflict?

Hey Guys, File handling and other issues has been fixed ,Please Update to Package == 1.0.16.
:)

but it seems that i still can't uploat more than one attachment... already updated to 1.0.17


[FIX] comment on exported

Fix comment on exported warning for better GoDocs

Thanks! I appreciate your help!


Issues: 418 - addresses issue of init.d not behaving the way as expected

Fixes #418
Problem:
The issue of the init.d script not exiting as expected with the correct,
printed output into the CLI for start, stop, restart.  Have already
fixed the status in the past.
Analysis:
Am introducing additional logic to test the status of the daemon prior
to any start or stop.  If the daemon was already running, then it will
simply state that it was&is running without 'trouncing' the original
PID.
If it was already stopped when 'stop' is executed, then it will state
that it was already in a stopped state and state that it is stopped.  If
it was running when stop is issued, then it will simply state that it is
stopped or the particular error coded type, and state that it is still
running (if so).
Lastly, if the daemon is called from an unrecognized argument,
unprivilidged
user or the improper number of arguments are given, then it will exit
with the
proper exit statement and code.
Tests:
Have tested the following manually as this requires a full devstack or
similar build on ubuntu:

start; restart; stop
$ sudo service f5-oslbaasv2-agent start;sudo service f5-oslbaasv2-agent
restart;sudo service f5-oslbaasv2-agent stop
(0) Service is running
(0) Service is running
(7) Service, f5-oslbaasv2-agent, is not running
from stop, status; start; status; #kill# status; stop; start; start
$ sudo service f5-oslbaasv2-agent status
(3) Service f5-oslbaasv2-agent is not running!
$ sudo service f5-oslbaasv2-agent start
(0) Service is running
$ sudo service f5-oslbaasv2-agent status
(0) Service f5-oslbaasv2-agent is in an OK Status!
$ kill -9 $(cat /var/run/neutron/f5-oslbaasv2-agent.pid)
$ sudo service f5-oslbaasv2-agent status
(1) Service f5-oslbaasv2-agent is dead and /var/run pid file exists!
$ sudo service f5-oslbaasv2-agent stop
Service is already in stopped status
(7) Service, f5-oslbaasv2-agent, is not running
$ sudo service f5-oslbaasv2-agent start;sudo service f5-oslbaasv2-agent
start
(0) Service is running
Service is Already Running: no action
(0) Service is running

@richbrowne
What issues does this address?
Fixes #418
WIP #
...
What's this change do?
Please see above in commit
Where should the reviewer start?
The ./etc/init.d/f5-oslbaasv2-agent file
Any background context?
Please refer to the Linux's standard handling of init.d files for handling start-stop-daemon.

Ok, try the following:
Edit the configuration file
/etc/neutron/services/f5/f5-openstack-agent.init by putting a space before
any option.  Try periodic interval.  Run the script and see if you get the
error.
Rich
On Wed, Feb 8, 2017 at 3:40 PM, Steven Sorenson<EMAIL_ADDRESS>wrote:

Fixes #610
Problem:
The issue of the init.d script not exiting as expected with the correct,
printed output into the CLI for start, stop, restart. Have already
fixed the status in the past.
Analysis:
Am introducing additional logic to test the status of the daemon prior
to any start or stop. If the daemon was already running, then it will
simply state that it was&is running without 'trouncing' the original
PID.
If it was already stopped when 'stop' is executed, then it will state
that it was already in a stopped state and state that it is stopped. If
it was running when stop is issued, then it will simply state that it is
stopped or the particular error coded type, and state that it is still
running (if so).
Lastly, if the daemon is called from an unrecognized argument,
unprivilidged
user or the improper number of arguments are given, then it will exit
with the
proper exit statement and code.
Tests:
Have tested the following manually as this requires a full devstack or
similar build on ubuntu:

start; restart; stop
$ sudo service f5-oslbaasv2-agent start;sudo service f5-oslbaasv2-agent
restart;sudo service f5-oslbaasv2-agent stop
(0) Service is running
(0) Service is running
(7) Service, f5-oslbaasv2-agent, is not running
from stop, status; start; status; #kill# status; stop; start; start
$ sudo service f5-oslbaasv2-agent status
(3) Service f5-oslbaasv2-agent is not running!
$ sudo service f5-oslbaasv2-agent start
(0) Service is running
$ sudo service f5-oslbaasv2-agent status
(0) Service f5-oslbaasv2-agent is in an OK Status!
$ kill -9 $(cat /var/run/neutron/f5-oslbaasv2-agent.pid)
$ sudo service f5-oslbaasv2-agent status
(1) Service f5-oslbaasv2-agent is dead and /var/run pid file exists!
$ sudo service f5-oslbaasv2-agent stop
Service is already in stopped status
(7) Service, f5-oslbaasv2-agent, is not running
$ sudo service f5-oslbaasv2-agent start;sudo service f5-oslbaasv2-agent
start
(0) Service is running
Service is Already Running: no action
(0) Service is running

@<reviewer_id>
What issues does this address?
Fixes #
WIP #
...
What's this change do?
Please see above in commit
Where should the reviewer start?
The ./etc/init.d/f5-oslbaasv2-agent file
Any background context?
Please refer to the Linux's standard handling of init.d files for handling
start-stop-daemon.
You can view, comment on, or merge this pull request online at:
https://github.com/F5Networks/f5-openstack-agent/pull/578
Commit Summary

Issues:

File Changes

M etc/init.d/f5-oslbaasv2-agent
https://github.com/F5Networks/f5-openstack-agent/pull/578/files#diff-0
(212)

Patch Links:

https://github.com/F5Networks/f5-openstack-agent/pull/578.patch
https://github.com/F5Networks/f5-openstack-agent/pull/578.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/F5Networks/f5-openstack-agent/pull/578, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIVe0SWIGLhCqgIKrwIqHy2cjAKK9P-Vks5rakR5gaJpZM4L7di2
.

Does it make sense to:

Store the STDOUT/STDERR into a variable
Reference the return code from start-stop-daemon
Dump into the terminal upon error or...
Remain quiet upon success

Users can then go without the white noise when things are 'okay' and see the dumped terminal output upon discovery of an error.
I am still using the start-stop-daemon executable quite heavily in that it...

Still initiates and stops the service

Handling the PID and LOCK files accordingly

Use it to check the status to report appropriately if/when circumstances are abnormal

When the service is running with what items present

If I were to rewrite it, though I would suggest in Perl.  I would not normally suggest this; however, given how complicated the parsing is to grab things, Perl is a bit more stable with log handling than straight shell.  Even bash, which is quite handy and can handle a good number of things.  Further, it would greatly reduce the number of lines we already have in bash as there are multiple steps to compensate for the lack of intelligence here.
Python is a lot of overhead to start/stop a service; however, it can be used to replace this as well.  I'm just worried at that point that it's the equivalence of a sludge hammer for ants...

Have performed the following changes:

Remove the --background flag
Pipe the start-stop-daemon output into a truncated, temp var

Contains only trace, error, and critical strings
If this causes issues down the road, we can always use like a 40K-60K cache
Upon error, dump the piped content

This gives the user:

What happened and the choice to dump the material into a log file of their own
An umbrella "catch net" for errors that the service might run into if/when an unhandled exception occurs
If they want to customize whether or not they want the feedback in the terminal, there's a comment on the line that dumps it in.

So, I've got a fix for this that should address most of our concerns:

I create the $LOCKFILE
I cast the start-stop-daemon call 2>&1 >> $LOGFILE;rm -rf $LOCKFILE into a string
I call nohup $str >/dev/null 2>&1 &

What this does is:

Stores the STDERR/STDOUT into the /var/log/neutron/f5-oslbaasv2-agent log
Gives the running prompt back to the user
Forks the service job off using nohup followed by a disown
Destroys the lock file if something "bad" happens to the agent's service PID during runtime

This keeps the user form having the running instance going in a prompt that they have to then disown while still preserving the STDERR


Update shared.py

Fix version of slugify

Sorry, now I checked again it seems slugify change version structure recently (from v6). It's weird because I install KCC via PyPi and got error at that line, which means PyPi installs the latest version of slugify instead of respecting the dependency mentioned in requirements.txt.

@ndtoan96
Does the new slugify version work fine?

Sorry, now I checked again it seems slugify change version structure recently (from v6). It's weird because I install KCC via PyPi and got error at that line, which means PyPi installs the latest version of slugify instead of respecting the dependency mentioned in requirements.txt.

I found the problem. kcc/setup.py doesn't include the requirements.txt and there is a mismatch.
PyPi version was built using kcc/setup.py.
https://github.com/ciromattia/kcc/blob/4ec4c9966c727d6dac44507d34607bd7d2c5ed5c/requirements.txt#L4
https://github.com/ciromattia/kcc/blob/4ec4c9966c727d6dac44507d34607bd7d2c5ed5c/setup.py#L84
something like this would be better in kcc/setup.py
with open("requirements.txt", "r", "utf-8") as f:
    requires = f.readlines()

setuptools.setup(
...

    install_requires=requires,

@darodi

Does the new slugify version work fine?
Not sure, I got plenty problem with images processing part, the binary works fine though. Will look at it when I have time, maybe due to dependencies just like this one.

Duplicate of #411
Duplicate of #410


[Enhancement]  Method calls equals on an enum instance [MessageTransferTask]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/core/protocol/tcp/client/task/MessageTransferTask.java line 81
analysis and explanation:
This method calls the equals(Object) method on an enum instance. Since enums values are singletons, you can use == to safely compare two enum values. In fact, the implementation for Enum.equals does just that
Describe the solution you'd like
reference:

Are you willing to submit PR?

[x] Yes I am willing to submit a PR!

I want to fix it.


feat: implement consensus broadcastValidation and set it to default

as a safety precaution for not broadcasting a invalid block ( see https://github.com/ChainSafe/lodestar/pull/6131), broadcastValidation consensus is imlemented and applied by default now.
In happy case of block produced by engine/builder via the beacon node, no extra work would be done while publishing as the root lookup is used to fast verify consensus validations. In case where the local root loookup fails validations are applied and will not let the invalid block to be broadcasted for e.g. because of the bug #6131 is trying to resolve.
Tested it locally as well for happy path on local by making consensus validations to always run

:tada: This PR is included in v1.12.1 :tada:

:tada: This PR is included in v1.13.0 :tada:


Elko count

https://staging.covidactnow.org/state/NV/county/elko_county is green but has no data

A bunch of counties do this, now tracking in this issue:
https://github.com/covid-projections/covid-projections/issues/413


Add a hint to let users know that they need to press enter in text prompts and action responses

Currently, users type their text prompts and their responses for slots and actions respectively but, they don't know they have to hit enter to add the text to the list of prompts or responses.
In other places, we are using an enter hint to let users know that they should hit enter. Let us use this hint for these inputs too.

Currently, users type their text prompts and their responses for slots and actions respectively but, they don't know they have to hit enter to add the text to the list of prompts or responses.
In other places, we are using an enter hint to let users know that they should hit enter. Let us use this hint for these inputs too.

@dcalvom could you please point me where do we use this hints for enter so I can have a reference?

You can check it in the modifiers form

https://github.com/samtecspg/articulate/blob/251ed724f9449e5a5344e9493ed272f9cb8533dc/ui/app/containers/KeywordsEditPage/Components/ModifierForm.js#L338

Closed by e805b5ff571589499176a0505463b9f6cfe912e4


Shifting into Platforms

Shifting into platforms sometimes launches you flying into the sky.

reduced speed should hopefully help for now


⚠ Samsung has degraded performance

In 01b40a0, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 6326 ms

Resolved: Samsung performance has improved in 457b417.


InterfaceIterator/InterfaceAddressIterator not reliable

The Inet Layer's InterfaceIterator class has the following bad behaviors on sockets platforms:

In some cases, the iterator will return the same interface multiple times.

The iterator will fail to return an interface if it has no assigned addresses.

Both of these behaviors arise from the use of getifaddrs(3) as a means to enumerate interfaces.
The logic of InterfaceIterator should be re-written to use if_nameindex(3) to ensure consistent behavior.

An addition issue that should be address with regard to InterfaceIterator is its lack of thread-safety on LwIP platforms.   Although the API states that the caller should hold the LwIP lock for the duration of the iteration, this isn't viable in many scenarios.

Additional issues uncovered on LwIP platforms:

InterfaceAddressIterator does not enumerate IPv4 addresses.
When InterfaceAddressIterator is initialized, it is logically positioned on the first IPv6 address slot in the first LwIP netif.  If that address slot is not initialized/in use, the iterator will return incorrect information.
Like InterfaceIterator, InterfaceAddressIterator is not thread-safe on multi-threaded LwIP platforms.

Fixed in openweave-core:master in commit 71f49e3.


Fixed a potential bug in TreeExplainer.fromResource.

Overview
This PR attempts to fix a bug which may lead to incomplete data loading from a resource file. In particular, the old Java code
            byte[] data = new byte[is.available()];
            is.read(data);

does not guarantee that we read every byte from the input stream. If the data file is only partially loaded into the byte array, it will result in data corruption, and consequently either invalid SHAP values, or more severe runtime errors.
The bugfix included in this PR should ensure that we exhaustively read all bytes from a given resource file.

retest


[AUDIT][SPARK-48191][SQL] Support UTF-32 for string encode and decode

Spark 4x enables support for UTF-32. I do not know if cuDF already supports this. Adding this as we may run into customers using UTF-32.
https://github.com/apache/spark/commit/003823b39d3

I don't think we support Encode or Decode as expressions at all right now.


Unable to name worker threads

As far as I know worker-loader do not provide reasonable way to create name for the Worker Thread for debugging purposes. Now all workers are named with hashed numbers (i.e. #23), while in the ES6 spec you can pass optional parameters with [WORKER_NAME] like this:
let worker = new Worker('path/to/my.worker.js', { name: '[WORKER_NAME]' });
I see no implementation in worker-loader. Passing arguments to the constructor do not work and I see no alternative.
It'd be nice to have it working like this:
let worker = new MyImportedWorker({ name: '[WORKER_NAME]' });
If the option already exists, then it'd be nice to have it in the README.md

Hi there,
I'd also find this useful.
It should be possible to pass the worker constructor options described here when importing my worker, e.g.:
import Worker from './file.worker.js';
const options = { name: 'my-worker'};
const worker = new Worker(options);
// according to specs I should see DedicatedWorkerGlobalScope.name === 'my-worker' when debugging

However looking at the code here, it does not seem possible.
Which pieces of code should be modified to handle this?

Done in master, now you can set worker options via the worker option, docs will be updated in the near future, sorry for delay


upgrade to node 18 / lts hydrogen

DEVOPS PULL REQUEST
Related Issue

Our current node version (14) has end of life in April 2023.
Resolves #3689

Changes Proposed

Upgrade to Node 18.

Additional Information

Docker image needed to be built for the e2e tests and lighthouse tests rather than just using the latest deployed one in order to have the latest runtime (Thanks @alismx for figuring this out!). This will result in e2e tests and lighthouse tests taking more time to build
I have done a smoke test and found no issues with this upgrade.
All team members will have to upgrade their node version to 18. If using nvm this can be done by running nvm install lts/hydrogen and then setting that version as the default nvm alias default lts/hydrogen. You may be required to restart for default to take effect.

Testing

Test the app in the deployed environment (currently deploy in dev)

Looks good! I smoke tested and most everything looks great. I seem to be getting some errors accessing some users on the Manage Users tab, though I think this may be my slow internet connection. Could someone else take a look and confirm that? Just don't want to approve until I'm sure it's my internet 😆

I'm also running into an issue with Manage Users when I try to access my own profile, but I think that's just a misconfiguration in my Okta local setup 🤔 I am able to add users and click between their profiles successfully though. Would be curious if anyone else can replicate issues.

Looks good! I smoke tested in dev and most everything looks great. I seem to be getting some errors accessing some users on the Manage Users tab, though I think this may be my slow internet connection. Could someone else take a look and confirm that in dev? Just don't want to approve until I'm sure it's my internet 😆
edit: I double checked in dev4 since I recently deployed there, and I'm not seeing the same issue. I refreshed my internet and I'm still getting errors accessing some people on the Manage Users tab in dev, specifically me, Merethe, and Emma return errors. Maybe this is a weird okta think though, it just doesn't sound related.

@georgehager @emmastephenson
I just deployed main on dev and I see the same errors. It's an error coming from the backend for those accounts mentioned.

If someone with access wants to pair looking at the logs in dev to figure out what this could be we can do that!

Looks good! I smoke tested in dev and most everything looks great. I seem to be getting some errors accessing some users on the Manage Users tab, though I think this may be my slow internet connection. Could someone else take a look and confirm that in dev? Just don't want to approve until I'm sure it's my internet 😆
edit: I double checked in dev4 since I recently deployed there, and I'm not seeing the same issue. I refreshed my internet and I'm still getting errors accessing some people on the Manage Users tab in dev, specifically me, Merethe, and Emma return errors. Maybe this is a weird okta think though, it just doesn't sound related.

@georgehager @emmastephenson I just deployed main on dev and I see the same errors. It's an error coming from the backend for those accounts mentioned.  If someone with access wants to pair looking at the logs in dev to figure out what this could be we can do that!

Happy to pair on this if you like @BobanL! My suspicion is that we're present in Okta but not in the ApiUser table or vice versa, but it's worth checking out regardless

I double checked in dev4 since I recently deployed there, and I'm not seeing the same issue. I refreshed my internet and I'm still getting errors accessing some people on the Manage Users tab in dev, specifically me, Merethe, and Emma return errors. Maybe this is a weird okta think though, it just doesn't sound related.

@georgehager @emmastephenson I just deployed main on dev and I see the same errors. It's an error coming from the backend for those accounts mentioned.  If someone with access wants to pair looking at the logs in dev to figure out what this could be we can do that!

Happy to pair on this if you like @BobanL! My suspicion is that we're present in Okta but not in the ApiUser table or vice versa, but it's worth checking out regardless

We looked into it and this error and concluded that it is happening when a user is part of multiple organizations. This can happen manually if you add yourself to multiple organizations, or if you run locally with okta since it also uses the dev prefix for okta groups.
The error will be thrown from getUsers if no claims are returned and no claims are returned from getOrganizationRoleClaimsForUser if a user is part of multiple organizations.


Incorrect typings for smembers

const redis = Redis.fromEnv()

await redis.sadd("key", {a: 1, b: 2})
const result = await redis.smembers("key")

console.log(typeof result[0]) // type is object

Hi! We're using upstash/redis v1.18.1 in our node environment. We noticed smembers returns Promise<string[]> but ends up returning non-stringified values when calling sadd to store objects
We're thinking the return value should be Promise<TData[]>

@RRamirez1414 yeah good catch, thank you
I'll fix it tomorrow

Fixed it in v1.18.3


Negative values for Host suspend time

The withSuspendTimeForHostUnavailable method (HostAvailabilityListener class) takes an argument of type Duration . Duration allows negative values (Duration.ofDays(-100)). When such a value is set and a node is shut down, the new forest config is taken almost immediately. Since we throw IllegalArgumentException for negative minHosts value, should we do the same here ?
13:43:14.308 [pool-3-thread-41] ERROR c.m.c.d.HostAvailabilityListener - ERROR: host unavailable "rh7v-intel64-90-test-9.marklogic.com", black-listing it for PT-2400H
13:43:14.328 [pool-3-thread-41] INFO  c.m.c.d.impl.WriteBatcherImpl - (withForestConfig) Using [rh7v-intel64-90-test-7.marklogic.com, rh7v-intel64-90-test-8.marklogic.com] hosts with forests for "WBFailover"

I don't think that's necessary.


[Script Lab] Add article

Preview site

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

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 5c118e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

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

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

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

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 76f4f7e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@ElizabethSamuel-MSFT Just a few minor suggestions, mainly "voice" edits and one change request. LMK if you have any questions!

Docs Build status updates of commit 6e77e66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0ee6280:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 8231eee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/screenshot-wide-youtube.png
:white_check_mark:Succeeded

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Memory bug in contrib/ecalhdf5/src/eh5_meas_dir.cpp

Hey there,
in contrib/ecalhdf5/src/eh5_meas_dir.cpp, in the second ctor (line 52), you should set access_ (to RDONLY) so that the nested call to Close() does not read from uninitialized memory.

Hey, thanks for pointing that out! I will check (and fix) that!

Hey, thanks for pointing that out! I will check (and fix) that!


Broken link. Use updated rfc link

Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, #24757.
Please be aware that @skittleson  is the author of the original issue and include them for any questions or replies.
Details
http://tools.ietf.org/html/rfc7517#section-4 is no longer valid.  Use https://datatracker.ietf.org/doc/html/rfc7517#section-4.2

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

ID: 10d05e86-c1d9-aa61-e2d7-a940828f5175
Version Independent ID: b8db8e73-678d-e138-2250-952f2c5de3c7
Content: JsonWebKeyUseNames Class (Microsoft.IdentityModel.Tokens) - Azure for .NET Developers
Content Source: xml/Microsoft.IdentityModel.Tokens/JsonWebKeyUseNames.xml
Service: active-directory
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Included in 6.14.0 release


OBS Project Creation Component , create 50 md, front, back and mainfest files as json

store.zip
Uploading original zip files sent by Vipin for stories json

https://app.zenhub.com/files/453025817/bc24aea8-ce95-4bb6-9e95-0b373f40d393/download
New proposed json structure json with and without text
Some code to convert json


use oc from builder image

Signed-off-by: Subbarao Meduri<EMAIL_ADDRESS>Per CICD team, oc exists in the builder image. To be compatible across linux and arm builds, copy oc from the builder image instead of downloading. This also solves the issue of not having to worry about the version of oc to use

/lgtm


Added display functionality for button profiles

Exposed wired pin configuration on gamepad
Changed display layouts to use functions with fixed pin layout
Added pin profile indicator
Added "cycle profile" hotkey
Renamed variables and functions to be more expressive (please forgive me)

@HoboDev - I don't mind the renames, but I think the introduction of the new pin structures could use so explaining (at least for me).

The new structures are basically the same as the old single profile structure but with another name. I used activeWire as I didn't come up with a better name.
So button profile 1 = pin assignment = activeWire for the display.
The rest is more or less the same.
Is that what you were looking for?

The new structures are basically the same as the old single profile structure but with another name. I used activeWire as I didn't come up with a better name.
So button profile 1 = pin assignment = activeWire for the display. The rest is more or less the same.
Is that what you were looking for?

Somewhat, I guess my remaining question is if we need the extra structure at all, or can just refer to profile 1 in the display. Just thinking it might be clearer to cut down on potentially-confusing duplication of the pins, if those two are effectively the same.

The new structures are basically the same as the old single profile structure but with another name. I used activeWire as I didn't come up with a better name.
So button profile 1 = pin assignment = activeWire for the display. The rest is more or less the same.
Is that what you were looking for?

Somewhat, I guess my remaining question is if we need the extra structure at all, or can just refer to profile 1 in the display. Just thinking it might be clearer to cut down on potentially-confusing duplication of the pins, if those two are effectively the same.

...and then I guess we probably wouldn't need the pinProfile renames either, which would cut down on the diff? Not demanding this, but curious what you think.

They aren't really necessary. It was just working well in my head that there is a pin assignment and pin profiles.

They aren't really necessary. It was just looking good that there is a pin assignment and pin profiles which helped me with the logical separation.

I think we should omit the duplication, then, it's just more to have to mentally manage if there's two things that mean the same thing.


Pass CA certificates in addition to just key/certificate

Probably turn the current tlsRef into a structure:
spec:
  tls:
    certRef:
      name: ironic-cert
    caRef:
      name: ironic-ca-cert

Where caRef is optional.
/kind feature
/help

/triage accepted

Hi @dtantsur! This issue is still valid, considering the discussion in #91 ?

Hi. This issue is potentially valid still, just with different naming (caName vs caRef). I personally don't have a use case for passing a CA but folks might.


Add py.typed for type checkers

Works from local testing.
Fixes #2373

Thanks for the contribution! A nice small change with a big quality of life impact. After you add the comment that Victory mentioned, I can merge it in.

Whoops, now I added the description and rebased on master.

Automerge cancelled: A status check is failing.


Add cutscene in the start of the song

Describe your problem here.
help me
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

local allowCountdown = false
function onStartCountdown()
if not allowCountdown and isStoryMode and not seenCutscene then
startVideo('your_cutscene_name_here');
allowCountdown = true;
return Function_Stop;
end


Add brace position to drivetrain

Should be a boolean input that commands the drivetrain to stop and put the wheels in an X pattern. Tie it to a button on the driver controller. We might add it to autonomois too.

Seems like it is already finished


Godot 4 games on web, crash the Browser on Macbook air's.

Godot version
4.1.1
System information
Macos Sonoma beta 14.0
Issue description
When I was on Itch.io and was exporting my game to the web but when I tested the game it crashed the browser I don't know why but I could not export my game to the web.
Steps to reproduce
Idk
Minimal reproduction project
https://star-flash-games.itch.io/super-space-shooter-x
If you are on mac.

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/70691 and https://github.com/godotengine/godot/issues/74512.


[BUG] Create a new program,error in console and page

New Error,“http://%3Cserver_address%3E:9999/api/v1/auth/signin”，I think it should be localhost。

so what is the correct serve-addr arg I should input? “ illa deploy --self --port=10000 --server-addr=locahost” or “ illa deploy --self --port=10000 --server-addr=<SERVER_ADDRESS>”

If u want to use illa-builder in ur machine, u do not need to input the arg --server-addr. The default value of this arg is localhost. It's required when u want to deploy illa-builder in ur cloud server and visit it on another computer.

We'll close this issue according to our issue rules.