Too much metrics with the same timestamp

Some of the customer report that after some time add-on stop to add metrics in Splunk, this can be due to the same timestamp for a lot of metrics, according to this message from customer:
From Customer: I think the issue will center around this error in internal logs.
01-22-2024 06:54:02.724 -0600 WARN AggregatorMiningProcessor [5267 merging] - Too many events (100K) with the same timestamp: incrementing timestamps 1 second(s) into the future to insure retrievability - data_source="dynatrace_timeseries_metrics://dynatrace_time_series_metrics", data_host="cncpxsplk1022.centene.com", data_sourcetype="dynatrace:metrics"
01-22-2024 06:33:21.543 -0600 WARN DateParserVerbose [5267 merging] - The same timestamp has been used for 100K consecutive times. If more than 200K events have the same timestamp, not all events may be retrieveable. Context: source=dynatrace_timeseries_metrics://dynatrace_time_series_metrics|host=cncpxsplk1022.centene.com|dynatrace:metrics|\n 1 similar messages suppressed. First occurred at: Mon Jan 22 06:24:01 2024

Adding idea to add one millisecond to every timestamp as time event, to avoid duplicates in the time of events

Fixed in following commit: https://github.com/dconnett-splunk/splunk-add-on-for-dynatrace/commit/8ab98bb8f2b298312688f4450febec242884bda0


shouldPerformSegueWithIdentifier is never called

I have a SWRevealViewController subclass and shouldPerformSegueWithIdentifier is never called. Note that the segue is being activated through the storyboard and not programmatically with performSegueWithIdentifier.

Nm, I noticed I need put shouldPerformSegueWithIdentifier in my menu view controller.


add filter for complete/incomplete todos

Option to add
filter="complete"
filter="incomplete"
to todo list
Another enhancement as mentioned in https://github.com/pimutils/todoman/issues/18
Example:
 todo list --filter="complete"
6  [X]    2017-02-22 07:21:35  HELLO @Personal (100%)
1  [X]    2017-02-22 05:35:56  HELLO @Personal (100%)

todo list --filter="incomplete"
 8  [ ]    2017-06-22             long task @Personal
 9  [ ]    Today 02:40:45         my @Personal
 7  [ ]    2017-02-22 11:08:17    hello task 2 @Personal
 5  [ ]    2017-02-22 10:49:22    do something @Personal
 4  [ ]    2017-02-22 10:48:54    Task 3 @Personal
 3  [ ]    2017-02-22 07:21:37    HELLO @Personal

Oh, that part of #18 was rather brainstorming! We already have --all, so we need to think about how to keep this consistent.

Yeah, that suggestion was kinda dumped there and sort of old. I think it makes sense the most to add a --completed flag. Ideas:

--completed=[yes|no|all] (I think each option is clear). Drop --all.
--completed only shows completed ones (no arguments).

Opinion, @untitaker ?
@Swati4star Please hang on a bit while we decide exactly how we want to implement this. ^_^

I prefer something like the second option, but with --completed renamed to --completed-only.

Also we need to prevent the user from using --all AND --completed-only, as they contradict each other.

Sounds good, just one nit-pick: I like --done better. ;)

Good, but please let's call it --done-only, otherwise it can be misinterpreted to behave the same as --all.

Sorry, @Swati4star, we made this a bit complicated since we hadn't really designed some bits as well. 😅

Now, I have added a flag --done-only,
The output is like this,
todo list --done-only
6  [X]    2017-02-22 07:21:35  HELLO @Personal (100%)
1  [X]    2017-02-22 05:35:56  HELLO @Personal (100%)

Also it appears that your new test currently fails

@untitaker @hobarrera Can you please tell why am I getting this error, when I am running tox.

You need to install todoman again (pip install -e .) because we have added a
new dependency in the meantime.
On Sun, Feb 26, 2017 at 06:13:44AM -0800, Swati Garg wrote:

@untitaker @hobarrera Can you please tell why am I getting this error, when I am running tox.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/pimutils/todoman/pull/137#issuecomment-282558638

@untitaker Fixed the tests! :+1:

Fantastic, thanks!

Thanks!


Added info for InfluxDB migration

I have updated the documentation to add some guidance for users with an existing InfluxDB data store.


Making the code editor window

Can know more about this issue

@Suraj-kumar00 Like a code editor component and that component can be called when we want to write the code like attached above
Thank You
Instructions

Yes you can start working on it by taking latest pull from main branch
Don't Forget to join onboarding group for knowledge flow and direct conversation and support from other developers link  Curious Developers Community - Hacktoberfest
Please attach the screenshots and video of the development work once it is done
Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number
Respect Co Developers And Please Reachout to admins if any issues


New calendar mode - Category

Is your feature request related to a problem? Please describe.
Would be great to add a functionality to split events by categories, for example by users.
Describe the solution you'd like
A good example of the solution is Vuetify calendar (https://vuetify.cn/en/components/calendars/#:~:text=6-,Category,-This is an)

Thank you for your work :)
Best regards.

I like this. I will add this to the project roadmap 👍


Missing hyphen

#label:"aq-pr-triaged"

Thanks for your contribution @nachoalonsoportillo !

#sign-off


watir not setting selenium script timeout

Meta -
Watir Version: 6.16.5
Selenium Version: 3.141.0
Browser Version: 72.0.3626.121
Browser Driver Version: 2.42.591059 (a3d9684d10d61aa0c45f6723b327283be1ebaad8)
OS Version: Mojave 10.14.3
Expected Behavior -
doubling the default selenium script timeout of 30 to 60 seconds.
@browser = Watir::Browser.new(:chrome, timeouts: { script: 60_000 }, options: @opts)
Actual Behavior -
script fails at default time.
Selenium::WebDriver::Error::ScriptTimeOutError:
script timeout: result was not received in 30 seconds
(Session info: headless chrome=72.0.3626.121)
(Driver info: chromedriver=2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac),platform=Linux 4.14.97-74.72.amzn1.x86_64 x86_64)
/var/lib/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/platforms/watir/page_object.rb:1066:in instance_eval' /var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/response.rb:32:in initialize'
/var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/http/common.rb:84:in new' /var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/http/common.rb:84:in create_response'
/var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/http/default.rb:104:in request' /var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/http/common.rb:62:in call'
/var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/bridge.rb:164:in execute'  /var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/oss/bridge.rb:584:in execute'
/var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/remote/oss/bridge.rb:274:in execute_async_script' /var/lib/gems/2.4.0/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/common/driver.rb:230:in execute_async_script'
/var/lib/gems/2.4.0/gems/watir_angular-0.4.0/lib/watir_angular.rb:13:in wait_for_angular' /var/lib/gems/2.4.0/gems/watir_angular-0.4.0/lib/watir_angular.rb:18:in block in inject_wait'
/var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/after_hooks.rb:70:in block in run' /var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/after_hooks.rb:100:in block in each'
/var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/after_hooks.rb:100:in each' /var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/after_hooks.rb:100:in each'
/var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/after_hooks.rb:70:in run' /var/lib/gems/2.4.0/gems/watir-6.14.0/lib/watir/elements/element.rb:142:in click'
(eval):1:in process_watir_call' /var/lib/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/platforms/watir/page_object.rb:1066:in instance_eval'
/var/lib/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/platforms/watir/page_object.rb:1066:in process_watir_call' /var/lib/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/platforms/watir/page_object.rb:472:in click_button_for'
/var/lib/gems/2.4.0/gems/page-object-2.2.4/lib/page-object/accessors.rb:435:in block in button' /spec/asset_debugger_spec.rb:85:in block (3 levels) in <top (required)>'
Steps to reproduce -
@browser = Watir::Browser.new(:chrome, timeouts: { script: 60_000 }, options: @opts)

At least with latest Watir/Selenium you can see it is getting set and returned correctly by looking at: Selenium::WebDriver.logger.level = :info
If the behavior is not matching the capabilities returned from the browser, then we might need to ask the chromedriver team.


Ice texture

Need to re-add our 32px Ice texture and not the default one !
This is at least the 10th times this error is done.......
Bad ice texture here (16px) :

(Surely a @LeMagnesium mistake... :()

You took the screenshot on the server when snow mod and its variation of default_ice.png were removed.
Now it's back. And copied to MFFGame. (https://github.com/MinetestForFun/server-minetestforfun/commit/ea5b55a8b1032f8c9feb5c9cbf8678d4f82c702b)


chore: last batch of warnings

Last batch of warning cleanups

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Docker fails: docker-compose -f docker/docker-compose.yaml up test

Expected behavior
docker-compose -f docker/docker-compose.yaml up test runs the test suite.
Actual behavior
Building the docker image fails:
Step 26/41 : ARG version=4.0.3
 ---> Using cache
 ---> 98a838f71a66
Step 27/41 : RUN mkdir $HOME/.swift
 ---> Using cache
 ---> c1011b5f61d1
Step 28/41 : RUN wget -q https://swift.org/builds/swift-${version}-release/ubuntu1404/swift-${version}-RELEASE/swift-${version}-RELEASE-ubuntu14.04.tar.gz -O $HOME/swift.tar.gz
 ---> Running in 3c69231a1f55
ERROR: Service 'swift-nio' failed to build: The command '/bin/sh -c wget -q https://swift.org/builds/swift-${version}-release/ubuntu1404/swift-${version}-RELEASE/swift-${version}-RELEASE-ubuntu14.04.tar.gz -O $HOME/swift.tar.gz' returned a non-zero code: 4

Steps to reproduce
Run docker-compose -f docker/docker-compose.yaml up test
Swift & OS version (output of swift --version && uname -a)
Apple Swift version 4.0.3 (swiftlang-9<IP_ADDRESS> clang-9<IP_ADDRESS>)
Target: x86_64-apple-macosx10.9
Darwin ZeaPro.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jan 11 22:59:40 PST 2018; root:xnu-3789.73.8~1/RELEASE_X86_64 x86_64
Docker version 17.12.0-ce, build c97c6d6
P.S.: Can we just use the official image please?

wget error code 4 is a network failure, so there is nothing wrong afaict in the docker setup.
happy to chat more about the "official" docker image in https://github.com/apple/swift-nio/issues/143

Hm, right, this part works at-home. Srz for the noise.


[stable/rabbitmq-ha] Add support for configuring global_paramaters definition

What this PR does / why we need it:
We're just getting to setting up rabbitmq in production with federation; we were having an issue whereby in federation it uses the cluster_name for uniqueness so it was essentially only federating to a single location until we changed the cluster names to be unique.
I thought the best way of making this configurable was to simply put in the global_parameters definition into the chart. I think separately there's a question whether or not you want to be setting cluster name which after this pull request would be as simple as updating the defaults.
Special notes for your reviewer:
Nothing should happen to existing deployments but I have tested this has the desired outcome when setting a global parameter. I've bumped the minor version on the chart to reflect a new feature which isn't breaking though.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @steven-sheehy

/ok-to-test

/lgtm
Thanks!

Absolute dream making this change, thanks for the speedy merge and review!


Add snapshotter CRDs after cluster setup

Adds snapshotter CRDs after cluster setup

Changes required for https://github.com/kubernetes-csi/csi-driver-host-path/pull/98
Signed-off-by: Grant Griffiths<EMAIL_ADDRESS>

/assign @xing-yang

/lgtm
/approve

/assign @pohly

@pohly can you approve it?  I don't have permissions.

/approve

Next steps:

merge into csi-driver-host-path repo via git submodule pull
do a release of csi-driver-host-path
update CSI_PROW_HOSTPATH_VERSION to that version in csi-release-tools
import into all repos
enable "1.17 on 1.17" pre-merge jobs


Format-Pester - translate static string (internationalization) - how implement (?) - RFC

Hi,
In the dev branch of my Format-Pester fork you can find partially rewrote code https://github.com/it-praktyk/Format-Pester/blob/dev/Format-Pester/Public/Format-Pester.ps1.
In that version

I added Order parameter - used to select if passed/failed tests are displayed as the first
merged into the one 'branch' code for failed/passed code and put it in a loop
moved all static string to separate variables.

Options for prepare internationalization of Format-Pester

Variables with string can be moved now to separate Private function with a parameter "Language" and function dot sourced
http://community.bartdesmet.net/blogs/bart/archive/2008/03/23/windows-powershell-2-0-feature-focus-script-internationalization.aspx

Any other ideas?

@equelin , could you test dev branch in my fork ?
Translation to French will be helpful for that test ;-)
Thx.

Hello @it-praktyk
I'm sorry but I'm short in time. I'll be in holidays at the end of the week so...
I'll try to check your dev branch tomorow.

It's a really good idea, nice work!
@it-praktyk Please submit a PR.

I'll prepare Pester tests to validate translations (structure of files) first.

After merging my pull request #10 you can close that issue.


vertical multiline insert behaves badly with autoindent when inserting tab

When adding a tab for multiple lines, and there are several indents, adding a tab displaces the alignment from left to right, miss-aligning every thing.

Sorry, this is a bug with how atom handles multiple cursors. This package just help placing the cursors, not the behaviour of them once created. Perhaps lodge a bug report in with Atom.


Cross Field OR validation

Is it possible to validate that on a given struct at least one of two options is required? I often have a struct where as long as one out of 2 of the fields are filled in, it will pass validation. One basic example would be having a username field and an email field (just a basic example though).

Currently there are no built in tags to do Cross Field OR validation. once getting into situations like you defined above, I consider them to be complex validation rules that even if built in tags could be used, it would become very hard to read.
But the library has a an easy reusable way to achieve what you want by creating a custom validation function, and then you may use and reuse it as a tag in your structs.
Example
// define funciton
func oneFieldSet(v *Validate, topStruct reflect.Value, currentStructOrField reflect.Value, field reflect.Value, fieldType reflect.Type, fieldKind reflect.Kind, param string) bool {
    // use topStruct instead of currentStructOrField below if want function to be able to do cross struct cross field validation
    currentField, currentKind, ok := v.GetStructFieldOK(currentStructOrField, param)
	if !ok || currentKind != fieldKind {
		return false
	}

   // if field has a value, just like the hasValue function then return true

   // if currentField has a value return true

   // return false by default
}

validate := //new validator
validate.RegisterValidation("eitherrequired", oneFieldSet)

type User struct {
  Username string `validate:"eitherrequired=Email"`
  Email    string `validate:"eitherrequired=Username"`
}

then you could reuse this tag/validation function in a bunch of your structs
Does that make sense?
P.S. you gave me a great idea, that I should expose the existing validators so that you can use them inside custom ones; then you could use hasValue ( which is the function that "required" tag runs ) in your custom function.

Hey @scisci
I've updated validator to expose the baked in functions for use within custom functions, so below is a more complete example using the exposed functions.
Example
// define funciton
func oneFieldSet(v *Validate, topStruct reflect.Value, currentStructOrField reflect.Value, field reflect.Value, fieldType reflect.Type, fieldKind reflect.Kind, param string) bool {
    // use topStruct instead of currentStructOrField below if want function to be able to do cross struct cross field validation
    currentField, currentKind, ok := v.GetStructFieldOK(currentStructOrField, param)
	if !ok || currentKind != fieldKind {
		return false
	}

    if validator.HasValue(v, topStruct, currentStructOrField, field, fieldType, fieldKind, param) {
      return true
    }

    if validator.HasValue(v, topStruct, currentStructOrField, currentField, fieldType, currentKind, param) {
      return true
    }

    return false
}

validate := //new validator
validate.RegisterValidation("eitherrequired", oneFieldSet)

type User struct {
  Username string `validate:"eitherrequired=Email"`
  Email    string `validate:"eitherrequired=Username"`
}

will this work for your needs? it should be generic enough to use within many of your structs

awesome! yeah that totally works for me. I will look into implementing it as soon gas possible. thanks @joeybloggs I had some more complex validation as well so using a validation function makes total sense.

perfect! glad I could help @scisci
if you need any help or have any question, just let me know.

Hey @scisci thought I'd let you know about Struct Level Validations see here: https://github.com/go-playground/validator/releases/tag/v8.7
this may be an even better way to do your username or email check :smile:


add adafactor and adamw optimizer

add adafactor.py and its ut in test_scheduler
add adamw.py and its ut in test_scheduler
fix C0304: Final newline missing (missing-final-newline) in test_opeator_base.py

merge the three commits


Add validation for PipelineParams

This PR adds vaildation for the PipelineParams type. It makes sure a
Service Accounts is specified.For Results, it
makes sure that Runs and Logs have a valid URL and Type. If
Results.Tests is present, is does the same checks for Tests. If Clusters
are present, it makes sure each Cluster has a valid Endpoint and Type.
I tried to ping the Cluster Endpoint to make sure it exists, but
apparently "ping" in Go requires root access. Research could definitely
be done to find a way to do this.
Should fix #30

Nice commit message :D

/approve
My two requests, which you can totally ignore if you'd like, are:

I think service account and all of the result store endpoints should be optional for now, but it doesn't make a huge difference since we can just supply dummy values for now until we get those pieces actually working. Definitely service account should be optional in the long run b/c folks might not need it
For the unit tests, you could create unit tests which are more focused, instead of at the level of the pipelineparams, so you'd need less boilerplate, e.g.:

You could test the cluster validation on it's own. (The coverage is actually better in your current solution, but I think more focused unit tests might be easier to maintain, not a big deal tho!)

Feel free to remove this when you are ready, if you want to go ahead as-is:
/hold

(oh yeah to cancel the hold, comment /hold cancel on it's own line)

This needs a rebase. Is it ready otherwise?

Just the rebase and resolving any conflicts, functionality is there

not sure why this is not getting merged
/approve
/lgtm

/approved


cybr-cli and ccp

Is your feature request related to a problem? Please describe.
Feature Request
Describe the solution you'd like
Add the ability to retrieve credentials to be used for cybr-cli logon via CCP.

That sounds perfect

That sounds perfect

I have created another issue to track the cybr ccp command found here https://github.com/infamousjoeg/cybr-cli/issues/67
Once that issue has been resolved we can work on implementing it as a logon feature.
Thank you for the awesome feature request and for using the cybr-cli

I have created another issue to track the cybr ccp command found here https://github.com/infamousjoeg/cybr-cli/issues/67
Once that issue has been resolved we can work on implementing it as a logon feature.
Thank you for the awesome feature request and for using the cybr-cli

The cybr-cli now has the cybr ccp command to easily retrieve a credential from CCP. Now we want to leverage this feature to dynamically retrieve a credential and log into the cybr-cli. Example command should be the following:
cybr ccp logon --safe PAS_REST_API --object name-of-the-object-in-PAS --url https://ccp.company.local

This command will retrieve the account in the PAS_REST_API safe with the object name of name-of-the-object-in-PAS and then use this credential to log into the PAS REST API and initialize the ~/.cybr session file.
@adam0306  Is this a desirable work flow?

@adam0306 Is this a desirable work flow?

It better be!

That sounds great. I tested the CCP retrieval without logon via Windows exe this morning. I'll test with logon next. But that works for me.
@infamousjoeg watch out, I may just have to make a trip down to Tampa.

Hi @adam0306 ,
After some internal discussion we are running into some snags regarding this feature. The problem is we do not know the authentication type of the returned object. Also we do not know if the returned object address will be the correct PVWA address because a LDAP platform will have the AD as the address and a Cyberark local account will have the vault  hostname as the address. So moving forward we are thinking about adding a --password flag.
Of course this brings up another concern, we do not want to make it easy for developers to put the --password field in the command in-turn writing the password to the history of the shell.
So the newly proposed solution goes as the following:
cybr logon -a LDAP -b https://pvwa.company.com -u MyUsername --non-interactive -p "$(cyb ccp get-account -s safeName -o REST-API-ObjectName -f Content)"

I know this command is rather long but it helps us couple of ways.

Reduce duplicate code
User must specific --non-interactice if they are using the --password flag
No need to worry about the account type (ldap, cyberark, etc)
The password will not be present in the shell history

I understand this is a different approach than what you proposed but I think it would help us significantly maintain this product.
Thanks,
Andrew

I hadn't even thought about the auth type either. Looking ahead the way that I see us using the CCP is via  a script so making it longer is no big deal. I agree protecting users from themselves is always a good thing like not printing creds to history. But at the same time they will also find a way depending on their desire.

At the end of the day, a human user should be using interactive cybr logon and be prompted securely to enter their password.  Automation should use the cybr logon --non-interactive command and either an environment variable containing the PAS_PASSWORD value (default) -OR- provide the -p/--password flag to provide it through command substitution, as @AndrewCopeland provided in his code example above.
I understand that users will always try to find a way around things.  However, I don't want to make it too easy for them to be insecure and lazy.

Completely agree. Just having the ability to retrieve the creds using CCP is a win for me.


Backtest Result Date is always: 1970-01-18

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[x ] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Doing backtest with 0.6.2
Expected result (what you hoped would happen)
Having the right result
Actual result (unexpected outcome)
all table entries are of date: 1970-01-18
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
Entry at (UTC)	Exit at (UTC)	Exposure	Entry balance	Exit balance	P&L	Profit
1970-01-18 16:42	1970-01-18 16:42	10 minutes	100.287	100.148	0.14	-0.14%
1970-01-18 16:43	1970-01-18 16:43	4 hours	99.998	97.923	2.07	-2.07%

Oops! Fixed in latest develop.


to correct formater dd/MM/yyyy in formatter config

problem with config 'formatter' 'dateFormat' => 'php:d/m/Y', 'datetimeFormat'=>'php:d/m/Y H:i:s' changes month for day.

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

What you change here is the function that reads the value that is to be formatted. This should be a machine readable and unambiguous format. dd/mm/yyyy does not fulfil this criteria as there is no clear distinction from mm/dd/yyyy. You must use an unambiguous format for storing dates in the database.

no cebe, my storing dates in the database in this format, i think that my pull request rashly

cebe, yii no apply my config formatDate=>'dd/MM/yyyy' interpreting wrong way,when load post! i see this as a bug. if the date load from my db, "yyyy-MM-dd H:i:s" is interpreted correct.
you can open my pull request, for a better analysis, or while we dictate?

@VolneiMonteiroRibeiro You could start from writing a unit test for this bug/feature - right now it is not clear what you're trying to achieve with this PR.

@VolneiMonteiroRibeiro your change is incorrect, and I do not see a good way to improve it to a proper solution, that's why I closed the pull request. You are using the property that configures the output format for parsing the input format. This does not make sense and changes the way the formatter works completely.
If we'd want to introduce a configuration for the input format we should discuss that in a separate issue. However I do not think there are reasonable storage formats to add so that we'd need such a configuration. We currently have support for storage of datetime values as unixtimestamp (integer) or in the  yyyy-mm-dd, which correspond to the format MySQL datetime fields are using. I am not aware of other formats being used commonly.

Showing "01/05/2018"
If
formatter->timeZone = 'America/Sao_Paulo'; \Yii::$app->formatter->defaultTimeZone = 'America/Sao_Paulo'; \Yii::$app->formatter->dateFormat = 'dd/MM/yyyy'; echo \Yii::$app->formatter->asTimestamp('05/01/2018');
Is wrong, agree?

I agree with @cebe - you're configuring formatter output format, and expecting that it will be used for parsing input. If you have dates in such format, you need to normalize it yourself.

@rob006
if i want use the method asTimestamp?
this config stay in web.php:formatter->timeZone = 'America/Sao_Paulo'; \Yii::$app->formatter->defaultTimeZone = 'America/Sao_Paulo'; \Yii::$app->formatter->dateFormat = 'dd/MM/yyyy';
if i use \Yii::$app->formatter->asTimestamp('05/01/2018'); wrong out.
/**
* Formats a date, time or datetime in a float number as UNIX timestamp (seconds since 01-01-1970).
* @param int|string|DateTime $value the value to be formatted. The following
* types of value are supported:
*
* - an integer representing a UNIX timestamp
* - a string that can be parsed to create a DateTime object.
*   The timestamp is assumed to be in [[defaultTimeZone]] unless a time zone is explicitly given.
* - a PHP DateTime object
*
* @return string the formatted result.
*/
public function asTimestamp($value)

- a string that can be parsed to create a DateTime object.
dont parse correct my string! it is contradictory with the comment, how can it be correct? my friends!

a string that can be parsed to create a DateTime object.

your string is ambiguous so it can not be parsed correctly. Use another format. The Yii formatter accepts unix timestamps (integer) or YYYY-MM-DD.

Stop the ego @cebe analise the situactions.... you do not correct, its ugly, ope  my requst


Allow for extra/optional depencendy installation when packaging

This won't work yet, will require pyapp>0.14.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.77%. Comparing base (7afb338) to head (6257d16).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   98.74%   98.77%   +0.03%
==========================================
  Files          19       19
  Lines         797      818      +21
==========================================
+ Hits          787      808      +21
  Misses         10       10

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


datepicker and timepicker interfearance

changing the minutes on the timepicker changes the day on the datepicker
http://plnkr.co/edit/3DI1xVORkPWETE86InrO

never mind, had yyyy-mm-dd instead of yyyy-MM-dd


Uri credentials not working

Dependency:
org.springframework.cloud:spring-cloud-starter-config:2.2.2.RELEASE
According to the documentation, Uri credentials should work.
bootstrap.properties (FAILS)
spring.cloud.config.uri=https://user:password@config01.mysoftware.com:9345
bootstrap.properties (WORKS)
spring.cloud.config.uri=https://config01.mysoftware.com:9345
spring.cloud.config.username=user
spring.cloud.config.password=password
Seems to be specific to Config since I use Uri credentials for Eureka and it works fine. The Uri is correct and verified since going to https://user:password@config01.mysoftware.com:9345/test/Dev in the browser returns the correct json.
In the case where it fails, the exception is:
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'someProperty1' in value "${someProperty1}"
	at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:178) ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:124) ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:236) ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.core.env.AbstractPropertyResolver.resolveRequiredPlaceholders(AbstractPropertyResolver.java:210) ~[spring-core-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.lambda$processProperties$0(PropertySourcesPlaceholderConfigurer.java:175) ~[spring-context-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.resolveEmbeddedValue(AbstractBeanFactory.java:912) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1247) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1226) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:640) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:130) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399) ~[spring-beans-5.2.6.RELEASE.jar:5.2.6.RELEASE]
	... 14 common frames omitted

There's other logging that might be useful (the exception is not). Fetching config from server at?

There's other logging that might be useful (the exception is not). Fetching config from server at?

@spencergibb I tried it both ways (in the uri and broken out) and the Fetching looks the same:
2020-05-13 19:04:36.416  INFO 584724 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at : https://config01.mysoftware.com:9345
Looking at the code, you strip the credentials off the uri anyways, so that makes sense.

Care to set a breakpoint in ConfigClientProperties.extractCredentials()? This is the thing that should extract a username and password from a uri

Care to set a breakpoint in ConfigClientProperties.extractCredentials()? This is the thing that should extract a username and password from a uri

@spencergibb Ah, I found the issue... it's an edge case :). My password happens to contain an @ sign in it, so in the properties file, I need to url encode it as %40:
spring.cloud.config.uri=https://user:password%40@config01.mysoftware.com:9345
You are missing the url decoding step on the username and password, so it's getting added to the header as "password%40" instead of "password@". In the broken out username and password, encoding isn't required, that's why it works there.


Use click to implement CLI for the tool

With all the advantages of click, the code doesn't differ much from what we had
before.  Just is a bit more declarative.

I'm not sure about click. Yes, there is nothing viable in stdlib for this, this is why pundle have its own 15 lines custom thing.
But we avoid any dependencies, because we install pundle to site-packages, and it must not install anything else.
Only way is to vendor lib to pundle package like pip do.

Closing in favour of #27


merge_file_into_embedded_script creates folder

here a folder powfacpy_temp is created in the root. This folder is recognized by git.

I would suggest:

including the folder name with a default parameter in the arguments.
And then put it in test_outputs in the test.
Also, I would include test_outputs in the .gitignore.

this resultet probably from keyboard-interrupting durint the test. Normally the folder is deleted automatically.


Apply special keyboards option in Input settings

Contains
This PR adds new buttons on the Input settings screen to quickly change your key mappings if you have a special keyboard like AZERTY, DVORAK or NEO.
The mappings were already available through console commands but that would not save them in the settings and that was difficult to reach for a casual player.
There is a localization of the title and the buttons for both English and French.
Screenshot:

How to test

On the main screen, open Settings then Input. You should see the new section "Special keyboards".
Try it by clicking on Apply for some special keyboard like AZERTY.
The changes in mapping should be instantly reflected in the binding buttons below (in Movement, Interaction, etc.) if they were supposed to change for the special keyboard you chose.
You might want to check in-game and ensure the new mappings are effectively applied.

Note: the steps are also be available from the in-game Settings menu

Can one of the admins please verify this patch?

@gooeyhub ok to test

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!


Main pointer fix

im not sure what im doing right now im just trying to fix the black screen bug on the character editor

this fork exists for contribution to the original repo + personal use, so i won't be accepting pull requests, sorry


Evnthubbicep

Description

This PR is for Event Hub module, This module will cover Event Hub cluster, Event Hub Namespace, Event Hubs. Also Authorization rule, Diagnostics settings, disaster recovery for event hub namespace and  Authorization rule, consumer group for event hubs.
Closes: #246
If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check.
Enable GitHub Worksflows in your fork to enable auto-generation of assets with our GitHub Action.
To trigger GitHub Actions after auto-generation, add a GitHub PAT as a secret in your forked repository called PAT.
Adding a new module

[x] A proposal has been submitted and approved.
[x] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.

Updating an existing module

[ ] This is a bug fix:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] I have run brm validate locally to verify the module files.
[ ] I have run deployment tests locally to ensure the module is deployable.
[ ] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[ ] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

[ ] I have updated the examples in README with the latest module version number.

@dciborow  Could you please review this Module?

@alex-frankel, we have two modules coming in together, redis and eventhub. The proposed parent directory for both is data. Where do you think these should go? I would put eventhub in compute because its charged by MB/s (essential the same unit as CPU's GHz).
And for redis, I would go with storage since its billed just by the hour. (no CPU cycles involved in this billing rate, just the static size of cache)

@alex-frankel, we have two modules coming in together, redis and eventhub. The proposed parent directory for both is data. Where do you think these should go?
I would put eventhub in compute because its charged by MB/s (essential the same unit as CPU's GHz). And for redis, I would go with storage since its billed by the fixed storage size per hour. (no CPU cycles involved in this billing rate, just the static size of cache)

Makes sense to me but would like to know @alex-frankel's thoughts as well.

good with these too

I think I messed up the MCR onboarding PR and excluded the module somehow. Will send a new PR to onboard the module and publish it manually.


showPaymentViewController promise not resolved nor rejected

Hello,
I have setup this library to get the payment working on my react native app.
BTClient.setup("<token>")   .then(done => {     console.log("done");     BTClient.showPaymentViewController({       callToActionText: "Pay"     })       .then(nonce => console.log(nonce))       .catch(err => console.error(err));   })   .catch(error => {     console.error(error);   });
I enter test payment informations such as cb or paypal, but when I click the "Pay" button none of the showPaymentViewController promise (then or catch) is executed.
I have tried with a setTimeout as well but it doesn't work either.
Has anyone experienced this before ?
I have tried only on Android with the latest version of the library
Thanks for your help

I am having the similar problem as well. If I pay by keying in test card details, it doesn't resolve with the "then" or "catch" promises.
However, if I pay with "Paypal Check out" (the button on top), it works.
Braintree Environment: sandbox
Android OS: 4.4.2
React Native Version: 0.46.4

Not sure if this helps, this issue only appears in braintree sandbox environment.


Disable the internal logger in production

The current implementation of react-navigation requires, to disable the internal logger, to create a navigator and pass it a custom onNavigationStateChange props, like this :
const AppNavigator = StackNavigator({ ... })
export default () => <AppNavigator onNavigationStateChange={null} />`

This is problematic because :

The ability to disable the logger (and in fact, the logger's existence) is buried in the API documentation about onNavigationStateChange
The logger can cause significant performance drops if there is a lot of data in the navigation props (my screen transition were about 3 seconds long with it, instantaneous without) because it is a succession of console.logs
The custom code required to disable the logger without needing to create a custom onNavigationStateChange function isn't easy to understand when reading code (because of the weird null explicitly passed as a prop)  and I was in fact only able to find it thanks to the PR which added the ability to disable it in the first place.

Would it be possible to disable the logger in production? I'm guessing this would give a boost to every app using react-navigation without this particular optimization.
(I actually wanted to send a PR with a check on the presence or absence or the __DEV__ variable, but I have no idea how to do this check for a project that supports both React and React-Native)

Would be cool to disable the logger in production AND if I want it :-)
At the moment don't need it and it's hard to see my own logs because of too many informations
thx!

Current version from the repo (cannot comment on npm) has the following:
https://github.com/react-community/react-navigation/blob/024297b0141ce63626846fac888d15811d4e5ed7/src/createNavigationContainer.js#L117-L121
In other words, logging is disabled now by default. To enable it, use the following code:
process.env.REACT_NAV_LOGGING = true

Should be disabled in production no!


Create draft client server architecture

Want to eventually support distributing the rendering workload (both rasterization and ray tracing) across multiple machines

Nope, focus of the project is instead on realtime graphics, ray tracer is just a debugging tool not a first class citizen.


aff instruction

aff takes not only the restricted ASCII table but go up to 256 char. we need to be sur the ft_printf works for the wild characters

The corewar file that is provided does not do wild characters, so we'll do the same. It only prints until 128.


Officially deprecate pkg_resources

Summary of changes

Closes
Pull Request Checklist

[ ] Changes have tests
[x] News fragment added in changelog.d/.
(See documentation for details)

I expect this change to have minimal impact on users of Setuptools as a build tool because DeprecationWarnings are suppressed by default.


launch upon OS startup doesn't work

Hi, I have a seaweed server running in a VM. For deployment/relocation and convenience purposes, I would like the server to automatically start up when the VM is booted up. To do so, I have written a simple bash script in Ubuntu and used a cron-job (crontab -e) to run this script. However, the server does not start up automatically. I have checked the logs of my cronjob, and everything else in my startup script does print successfully. Any issues in Ubuntu, or how should I be doing this? Thanks.

please follow issue template and provide details.

I don't think I need a screenshot for this, but basically I have a startup script initialise.sh with the following lines:
"
echo "initialise"
weed server -dir=$PATH_TO_DIR -ip=$IP -ip.bind=$IP -filer=true -filer.port=$FILER_PORT -master.port=$MASTER_PORT -volume.port=$VOLUME_PORT -volume.max=$NUM_VOLUMES_MAX
echo "end"
"
When I run this script in the terminal normally, the server loads up, with the master/volumes/filer. But when I wrote a cron job:
@reboot /directory/initialise.sh > /directory/seaweed.log
Inside /directory/seaweed.log, all I get is:
initialise
end
And the seaweed servers have not been set up. Not sure if there's any issue with launching this on restart/start-up?
Thanks!

got it, thanks! I previously ran with "weed .....", but it seems to not recognize this environment variable upon startup. Running it with the absolute path to the weed executable worked.
Separately, I noticed that adding -ip.bind=... doesn't work in the crontab but works in the terminal. After taking it out, seems to be ok


docs(managing-workflow): Add link to terraform-provider-deis

From what I understand in https://github.com/deis/deis/issues/4824 this is only compatible with Deis v1 and is incomplete. Is this untrue?

Yes, this project is indeed only compatible with v1. Once it supports v2 then we can link it here. Let's close this for now until v2 support has been added. Thanks!

Ah ok, didn't notice that :(


[WIP] CREATE VIEW error with localStorage engine #604

Some changes to get select from view to work with localStorage. New test case shows more problems with localStorage.
Hopefully I have not missunderstod it completly:-)

Did you do a npm test on your local machine?
I can see the 2 news tests are failing: https://travis-ci.org/agershun/alasql/jobs/119388243
Test 604 - CREATE VIEW error with localStorage engine #604 * Reselect from table:
      AssertionError: false == true
      + expected - actual
      -false
      +true

      at Context.<anonymous> (test604.js:99:2)
  2) Test 604 - CREATE VIEW error with localStorage engine #604 * Reselect from view:
     TypeError: alasql.databases[source.databaseid].tables[source.tableid].select is not a function
      at Object.source.datafn (/home/travis/build/agershun/alasql/dist/alasql.js:7293:73)
      at /home/travis/build/agershun/alasql/dist/alasql.js:5969:19
      at Array.forEach (native)
      at queryfn (/home/travis/build/agershun/alasql/dist/alasql.js:5966:16)
      at statement (/home/travis/build/agershun/alasql/dist/alasql.js:6988:14)
      at Function.alasql.dexec (/home/travis/build/agershun/alasql/dist/alasql.js:4252:11)
      at Function.alasql.exec (/home/travis/build/agershun/alasql/dist/alasql.js:4234:17)
      at alasql (/home/travis/build/agershun/alasql/dist/alasql.js:120:18)
      at /home/travis/build/agershun/alasql/dist/alasql.js:4426:9
      at lib$es6$promise$$internal$$initializePromise (/home/travis/build/agershun/alasql/node_modules/es6-promise/dist/es6-promise.js:408:9)
      at new lib$es6$promise$promise$$Promise (/home/travis/build/agershun/alasql/node_modules/es6-promise/dist/es6-promise.js:581:60)
      at promiseExec (/home/travis/build/agershun/alasql/dist/alasql.js:4425:10)
      at Function.alasql.promise (/home/travis/build/agershun/alasql/dist/alasql.js:4469:10)
      at Context.<anonymous> (test604.js:104:9)

Hi,
I did the fix but realized that reinitializing the view from localstorage
would be be tricky, so I included tests for that also. In doing so I
realized that I could neither restore the view nor the table from
localstorage. The two test errors show exactly that.
I did not go on to fix the test errors beacuase:

I'm surprised that restoring the table does not work. Did I do something
wrong.

From my limited understanding of the code base it seems tricky to save
and restore the view (I can give you more details but I would like to sort
out the previous point first).

Understand what I  mean?
Regards
Den ons 30 mars 2016 07:40Mathias Rangel Wulff<EMAIL_ADDRESS>skrev:

Did you do a npm test on your local machine?
I can see the 2 news tests are failing:
https://travis-ci.org/agershun/alasql/jobs/119388243
Test 604 - CREATE VIEW error with localStorage engine #604 * Reselect from table:
AssertionError: false == true
+ expected - actual
-false
+true
  at Context.<anonymous> (test604.js:99:2)

Test 604 - CREATE VIEW error with localStorage engine #604 * Reselect from view:
TypeError: alasql.databases[source.databaseid].tables[source.tableid].select is not a function
at Object.source.datafn (/home/travis/build/agershun/alasql/dist/alasql.js:7293:73)
at /home/travis/build/agershun/alasql/dist/alasql.js:5969:19
at Array.forEach (native)
at queryfn (/home/travis/build/agershun/alasql/dist/alasql.js:5966:16)
at statement (/home/travis/build/agershun/alasql/dist/alasql.js:6988:14)
at Function.alasql.dexec (/home/travis/build/agershun/alasql/dist/alasql.js:4252:11)
at Function.alasql.exec (/home/travis/build/agershun/alasql/dist/alasql.js:4234:17)
at alasql (/home/travis/build/agershun/alasql/dist/alasql.js:120:18)
at /home/travis/build/agershun/alasql/dist/alasql.js:4426:9
at lib$es6$promise$$internal$$initializePromise (/home/travis/build/agershun/alasql/node_modules/es6-promise/dist/es6-promise.js:408:9)
at new lib$es6$promise$promise$$Promise (/home/travis/build/agershun/alasql/node_modules/es6-promise/dist/es6-promise.js:581:60)
at promiseExec (/home/travis/build/agershun/alasql/dist/alasql.js:4425:10)
at Function.alasql.promise (/home/travis/build/agershun/alasql/dist/alasql.js:4469:10)
at Context. (test604.js:104:9)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/agershun/alasql/pull/641#issuecomment-203257169

I see - you added the test to show its not working.
If you can please replace ´it with it.skip for the new tests you made that are not working we can merge your changes in and keep an issue open to fix it.

Sure, but I was a bit worried about the changes. I do not see the big picture here and I'm not sure I did not break anything.
The changes in src/60createtable.js looks ok to me. However changes in src/420from.js I'm a bit worried that something will break:-)

Thats ok.
That is why we (try to) have all functionality in the tests - so that if you break something an old test will fail.
So... as long as you are only skipping tests you yourself wrote there is no problem (other than the fact that there is a bug...)


[FIX] escape closing script tag and opening comment tag

There was an issue when the javascript code contains </script> or <!--, it was interpreted has HTML code and broke the inlined HTML file.

Added to the latest patch version. For any future changes, please add a test.


break button?

In the REPL, if one accidentally starts a loop that runs forever, once can break execution with cmd-. (on a mac) without having to terminate the session. I can't find an analogous feature in Juno -- I can Stop Julia, but then I lose my session and everything loaded up (I work with big files, so load time is non-trivial).

CtrlC should work. The command you're looking for is called Interrupt Julia.
I guess that would be more easily discoverable with a button in the console toolbar or something?

I think that'd be nice. Most interactive editors I know have a break button in top right:
spyder:

RStudio:

Stata:

Implemented in https://github.com/JunoLab/atom-julia-client/commit/34f6cb0b3c7bf34e1c97bb07082fbb6204169170.

@pfitzseb That was fast! Thanks!! 👍


Fix chunked prefill

Add max_prefill_token_num, decoupled with max_context_token_num

max_prefill_token_num (>= max_batch_size): max number of prefill tokens in a forward pass
max_context_token_num (>= session_len): max number of context tokens (including history) in a forward pass

Fix data race in chunked prefill

Memory consumption is greatly reduced for large session_len.

请问下怎么安装这个更新


"error: Variable project_name has multiple definitions" when importing justfiles

Hello!
I am getting the error in the title when trying to import a justfile with the same variable as in the parent file; is there any setting, perhaps similar to allow-duplicate-recipes, that works for variables as well, such as allow-duplicate-variables, maybe?
Thank you kindly for the help!

I'm not sure I understand, can you copy and paste your justfiles so I can take a look?

Not at my computer right now, but, it's something like this:
p/a/justfile:
x := `basename {{justfile_directory()}}`

Where x results in a, and:
p/b/justfile:
import "../a/justfile"
x := `basename {{justfile_directory()}}`

Where x is supposed to result in b, but just errors out with what's in the title of the issue.

Gotcha. I think that set allow-duplicate-variables would be reasonable to add, and not too much work.

I marked this as good first issue, in case anyone wants to take a crack at it.

Wish I could help, but I know nothing of rust, though I've been wanting to learn it for a while! 😅

Can this be closed as completed?

I have not tested the changes yet, as I'm working on something else at the moment, unfortunately! 😅 We could possibly reopen it if necessary?

I have not tested the changes yet, as I'm working on something else at the moment, unfortunately! 😅 We could possibly reopen it if necessary?

set allow-duplicate-variables := true
I am just using it ^^ I landed here trying to find out why it didn't work before

Then we should be good to go, I think! My thanks to everyone involved here! 😸


Feat/use official keplr link

Self explanatory. Better to use official Keplr URLs.

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


local_opt_generator fails

The model libensemble.tools.gen_support referenced in local_opt_generator does not exist, so rsopt fails when trying to import it. The libensemble repo says the module was removed on 5 October (see here). Also see this wiki entry which points to how to do things now.

Yes, the update to libensemble 0.8.0 brings a lot of changes. I forgot that we install libensemble from PyPI and have the up-to-date version.
I'll start work making rsopt 0.8 compatible.

We can work with the older version. Did you fix the versions in the setup.py?

@robnagler this needed to be updated anyway to get features I want for future work so I went ahead and finally did the work
@mkeilman rsopt develop branch should now be compatible with libensemble 0.8.0. If you get a change to test let me know. I'm going to run a few more tests to verify rsmpi works and then I'll merge it to main soon.

Also closed by c01a3da1aacf523057911952db475a271a909cdf


Update secrets.hashicorp.com CRDs to v0.5.2

Pulled from https://github.com/hashicorp/vault-secrets-operator/tree/v0.5.2/chart/crds, converted with openapi2jsonschema.py.
Supersedes #283.

@eyarz any chance you could merge this?

@adrianmoisey @fhemberger
sorry for the delay, my email wasn't setup correctly so I didn't get the notification...

No problem, thanks for merging!


How can I assign an id to each

Summary of problem or feature request
I need to assign my id to each TR so I can use Jqeury to remove them based on that id
Code snippet of problem

System details

Operating System
PHP Version
Laravel Version
Laravel-Datatables Version

See row options docs.


Provide information on which SPICE kernels are relevant to an observation

From "Tapella, Robert K (398H)"<EMAIL_ADDRESS>
in some cases, need to re-calibration position using SPICE information; having information about where to go to get the right SPICE kernel would help

Per Mark 1/11/2022 this is difficult and will likely not be done in the next five years.


Feature: Tic tac toe in python

I have created a tic tac toe game in python. I will upload it here if contributors accept it.

can i upload it?

contributor
pull number?

can i upload it?

yes

if you want i will fix your issue

pls assign me

Hello can i please have this issue to fix

I would like to work on this issue. Kindly assign it to me.

can i upload it?

yes

I created a pull request #1442 for tic-tac-toe in python


[Question] How to access k3s UI

I have k3s deployed in a single node cluster, but do not know how to access the UI of k3s, can anyone help? Thanks.
root@gyliu-dev2:~# curl -sfL https://get.k3s.io | sh -
[INFO]  Finding latest release
[INFO]  Using v0.1.0 as release
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  Downloading https://github.com/rancher/k3s/releases/download/v0.1.0/sha256sum-amd64.txt
[INFO]  Downloading https://github.com/rancher/k3s/releases/download/v0.1.0/k3s
[INFO]  Verifying download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  systemd: Creating /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink from /etc/systemd/system/multi-user.target.wants/k3s.service to /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s

K3s does not include a UI. Look #87.

Thanks @ricardona but what is the UI mentioned in #87 ? Is it k3s UI?

The UI mentioned in #87 is the official Kubernetes Web UI Dashboard.
https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

I see, thanks @kha7


You should have called it atomic-clock.

You missed your chance.
Thanks, I will use this.
This should have been in the forum, not here

Best issue ever. :+1:
Maybe I could still rename it, according to this.


fix cloning element.points

Wouldn't let me sleep if I let it like this :).

Hold on actually..

This may technically be bad, too...

Ok, this is more like it. Probably not needed, but will ensure the same behavior as before the fixes (except, it still does a deep clone of points, of course).

lgtm


UDP Load Balancing and TCP load Balancing with kubeMCI

is it possible to run “kubemci create” with  UDP Load Balancing or TCP load Balancing ?
or only HTTP/s Load Balancing is supported.

kubemci supports HTTP/s load balancing only.
Will love to understand why you need UDP or TCP load balancing.
Will be great if you can explain your use case at https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/issues/197 which has more details.
Thanks!

Closing as dup


ratelimit-below-domain logs the wrong FROM address

Describe the bug
If ratelimit-below-domain: in-addr.arpa 2 is configured then unbound will log the following:
notice: ratelimit exceeded 8.in-addr.arpa. 2 query <IP_ADDRESS>.in-addr.arpa. IN PTR from <IP_ADDRESS>

It seems that the from address is referring to the server that sent the last reply and not to the client that was doing the request.
To reproduce
Steps to reproduce the behavior:

Set the ratelimit

server:
  ratelimit-below-domain: in-addr.arpa 2

systemctl restart unbound
Query unbound:

for x in <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>; do dig @<IP_ADDRESS> -x $x; done

Read the unbound log

info: <IP_ADDRESS> <IP_ADDRESS>.in-addr.arpa. PTR IN
info: generate keytag query _ta-4f66. NULL IN
info: <IP_ADDRESS> <IP_ADDRESS>.in-addr.arpa. PTR IN
notice: ratelimit exceeded 8.in-addr.arpa. 2 query <IP_ADDRESS>.in-addr.arpa. IN PTR from <IP_ADDRESS>
info: <IP_ADDRESS> <IP_ADDRESS>.in-addr.arpa. PTR IN

Expected behavior
I would expect that the IP address of the client that is doing the request is logged. In this case:
notice: ratelimit exceeded 8.in-addr.arpa. 2 query <IP_ADDRESS>.in-addr.arpa. IN PTR from <IP_ADDRESS>

System:

Unbound version: unbound 1.20.0
OS: Debian sid
unbound -V output:

Version 1.20.0

Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --with-pythonmodule --with-pyunbound --enable-subnet --enable-dnstap --enable-systemd --enable-cachedb --with-libhiredis --with-libnghttp2 --with-chroot-dir= --with-dnstap-socket-path=/run/dnstap.sock --disable-rpath --with-pidfile=/run/unbound.pid --with-libevent --enable-tfo-client --with-rootkey-file=/usr/share/dns/root.key --enable-tfo-server
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 3.2.2 4 Jun 2024
Linked modules: dns64 python cachedb subnetcache respip validator iterator
TCP Fastopen feature available

BSD licensed, see LICENSE in source package for details.
Report bugs to<EMAIL_ADDRESS>or https://github.com/NLnetLabs/unbound/issues

Thanks!
It seems the wrong value was printed indeed. Now it will print the first client's address if any.
I say first because maybe more than one are waiting for an answer.


chore: refactor view engine

TODO

[x] Rework raw and escaped output
[x] decide on what {{ strtoupper($var) }} should do: should $var be escaped, should the whole strtoupper($var) be escaped?
[x] Fix line ending tests for Windows
[x] Performance testing
[x] Relative view paths don't seem to work anymore
[x] Include the compiled PHP file instead
[x] Properly disable view cache (broken)
[x] Make sure the view cache directory exists
[x] Add tests for ViewCachePool

TODO after merge
#565

Well, let's go!


The popup disappears too quickly

The user should have enough time to process and copy-paste the error

Even better would be:

Add a small dismiss/close button
Stop the timeout for hiding the toast if the mouse rolls over the toast.
Restart the timeout for hiding the toast if the mouse exits the area.

Should be fixed in e18191ad4c9f79ba3a841fbe46ad158beff00902 thanks!


Revision 1: Document Revisions

Documentation Revisions Due Thurs April 4th (Team 6 issues and TA feedback on Avenue):

SRS: @HamidHarris
Hazard Analysis: @FardeenAfsar
VnV Plan: @DangJustin
Detailed Design and Software Architecture: @Lazarus-XD
VnV Report: @fadymorcos21
Problem Statement and Development Plan @DangJustin
User's Guide


T-RGB 2.1 inch Half Circle: Trouble communicating with the screen

Hello,
I can't seem to communicate with the screen after flashing the default code on my T-RGB.
While monitoring I get:
I (1098) main: ------ Initialize I2C.
W (1098) i2c.master: Please check pull-up resistances whether be connected properly. Otherwise unexpected behavior would happen. For more detailed information, please read docs
I (1098) gpio: GPIO[8]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 0| Pulldown: 0| Intr:0
I (1098) gpio: GPIO[48]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 0| Pulldown: 0| Intr:0
I (1098) main: ------ Initialize PMU.
I (1098) main: ------ Initialize TOUCH.
I (1098) main: ------ Initialize DISPLAY.
I (1098) RGB: ============T-RGB==============
E (1098) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1098) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1118) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
I (1128) RGB: Extension BEGIN SPI SUCCESS !
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (1128) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized

The i2c.master: i2c_master_transmit_receive(1041): i2c handle not initializedseems to come from the initialization of the screen in the display_rgb.cpp:
  int i = 0;
  while (init_cmd[i].len != 0xff) {
      writeCommand(init_cmd[i].addr);
      writeData(init_cmd[i].param, init_cmd[i].len & 0x1F);
      if (init_cmd[i].len & 0x80) {
          delay(100);
      }
      i++;
  }

After a lot of repetitions of that error, the program seems to run, but the LCD stay black except for the backlight who light.
E (2828) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (2828) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
E (2828) i2c.master: i2c_master_transmit_receive(1041): i2c handle not initialized
I (2948) RGB: Turn on LCD backlight
I (2948) gpio: GPIO[46]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (2948) main: Initialize LVGL library
I (2948) main: Register display driver to LVGL
I (2958) main: Install LVGL tick timer
I (2958) main: Register touch driver to LVGL
I (2958) main: Display LVGL
I (3248) main: Create LVGL task
I (3248) main_task: Returned from app_main()
I (3248) main: Starting LVGL task

Did you managed to get the T-RGB configuration to work ?
I'm on the last version of the code e458330 with the idf version ESP-IDF v5.3-dev-2815-gbe06a6f5ff.
Thanks

The I2C error has been fixed. This is the touch screen going into sleep mode, I2C access error, but the screen not lighting up situation does not exist. My side is working normally.

Hello, the commit indeed fixed the issue. The screen is now working. Thanks


DCOS-8068 Add health check results table to task page

This adds the missing Health Check Results table to the task detail page as is available in Marathon UI.

Reviewer: @aldipower

LGTM 💯 ✨

retest this please

retest this please

retest this please

merge once super nit is fixed

relevant tests are passing


White screen on launch

When I launch the application I get stuck with the following white screen:

Release 1.1.0
Windows 11
logs attached:
error.log
info.log

known issue, will be fixed on next release

This has been fixed.


Allow ISUPPORT parameters to be negated

ISUPPORT allows negating parameters via -PARAMETER which allows servers to change functionality without disconnecting clients. As per https://modern.ircdocs.horse/#rplisupport-005:

Tokens of the form -PARAMETER are used to negate a previously specified parameter. If the client receives a token like this, the client MUST consider that parameter to be removed and revert to the behaviour that would occur if the parameter was not specified. The client MUST act as though the paramater is no longer advertised to it. These tokens are intended to allow servers to change their features without disconnecting clients. Tokens of this form MUST NOT contain a value field.

Docker on Travis choked on the name of your branch...


Regenerate APIs

The two pubsub files changed are not changes we want. Next week I'll fix the codegen so these aren't produced.
The asset changes are correct,

I've removed the PubSub commit.


Deprecate --compilers

This attempt is a bit rough; we might have to tweak tests to tell Node to suppress the deprecation warning, for instance.

Coverage remained the same at 89.177% when pulling 60bc6539f8e60da3d5a8913084a4bbd46c946deb on deprecate-compilers into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

this won't make it into v4.0.0

well, hmm... eh.  it'll dump to STDERR.  should be okay...I can live with the fallout.

I'm gonna tweak the text a bit.

Coverage remained the same at 89.436% when pulling 29460257df0f041d5cc52a74ce80774251111a4d on deprecate-compilers into c5d69e0d9cdb494198e1c65a85ef5d58c0687aa3 on master.


refactor(command): document everything, remove unused options

Coverage increased (+0.3%) to 33.662% when pulling fb448cc90bfcad92099dfa2d4bb61db8029398ad on refactor/updated-command into 43425c16e811adc15bd0afe1ab10c6d8dea2c3c6 on main.


migrate to >=py311 enum.StrEnum usage

🚀 Pull Request
Description

After adopting Scientific Python SPEC-0 and dropping support of py310, we're now free to adopt enum.StrEnum and enum.auto and thus purge some tech debt.

Are you sure about auto()? With explicit strings we still get the built-in validation and documentation of Enum, while allowing users to type strings in their own code, which I imagine would be easier.

Users can still type strings as before, so there's no difference in user experience or behaviour.
When auto() is used for a StrEnum it's giving us the lower case string of the enumeration name for free ... the only difference is in the rendered documentation where the value of an enumeration isn't shown i.e., this ...

vs this ...

TBH on reflection I prefer the former, so if you wanted to push a PR dropping the use of auto, that would be welcomed 😉

Ohhhh now I can't decide 😖

it's giving us the lower case string value of the enumeration name for free

That's good!

the rendered documentation where the value of an enumeration isn't shown

That's bad!

TBH on reflection I prefer the former

Let me know if you're just being nice. If you really want it I will write it!

#1152


Not working with esbuild

We have an older application and we are building it with esbuild. We want to integrate Svelte into it; we are using the esbuild-svelte plugin.
Repro
Steps to reproduce the problem:

When trying to import svelte-multiselect, I got the following error from esbuild:

✘ [ERROR] Could not resolve "svelte/internal/flags/legacy"

    admin_ui/node_modules/svelte-multiselect/dist/icons/Cross.svelte:2:7:
      2 │ import "svelte/internal/flags/legacy";
        ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./internal/flags/legacy" is not exported by package "svelte":

    admin_ui/node_modules/svelte-multiselect/node_modules/svelte/package.json:25:13:
      25 │   "exports": {
         ╵              ^

  You can mark the path "svelte/internal/flags/legacy" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
...
...
...
✘ [ERROR] Could not resolve "svelte/internal/client"

    admin_ui/node_modules/svelte-multiselect/dist/icons/Cross.svelte:3:19:
      3 │ import * as $ from "svelte/internal/client";
        ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./internal/client" is not exported by package "svelte":

    admin_ui/node_modules/svelte-multiselect/node_modules/svelte/package.json:25:13:
      25 │   "exports": {
         ╵              ^

  You can mark the path "svelte/internal/client" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.

Then I added the following to the esbuild config:

{
  ...
  external: ['svelte/internal/client', 'svelte/internal/flags/legacy'],
  ...
}

And it got compiled successfully but I got the following error in the browser terminal:
Uncaught Error: Dynamic require of "svelte/internal/client" is not supported

Expected behavior
It should build using esbuild.
Additional context
Versions:

esbuild: 0.24.0
esbuild-svelte: 0.9.0
svelte-preprocess: 6.0.3
svelte: 5.14.1
svelte-multiselect: 11.0.0-rc.1

esbuild config:
{
  entryPoints: [{ out: 'admin_ui', in: './admin_ui/src/main.ts' }],
  entryNames: '[ext]/[name]',
  assetNames: 'assets/[name]',
  target: 'es2020',
  bundle: true,
  color: true,
  outdir: path.resolve(
    path.dirname(fileURLToPath(import.meta.url)),
    '..',
    'priv',
    'static'
  ),
  mainFields: ['svelte', 'browser', 'module', 'main'],
  conditions: ['svelte', 'browser'],
  external: ['svelte/internal/client', 'svelte/internal/flags/legacy'],
  plugins: [
    esbuildSvelte({
      preprocess: sveltePreprocess({
        postcss: {
          configFilePath: 'admin_ui/postcss.config.js',
          plugins: [tailwindcss(tailwindConfig), autoprefixer]
        }
      })
    })
  ]
}

i'm a bit out of the loop with the latest in the Svelte ecosystem right now. might be "svelte/internal/flags/legacy" was only added in Svelte 5. which version are you using? either way, i'm confused since Cross.svelte doesn't import from svelte anyway so it's probably some kind of version mismatch

There is the versions I'm using:

Versions:

esbuild: 0.24.0
esbuild-svelte: 0.9.0
svelte-preprocess: 6.0.3
svelte: 5.14.1
svelte-multiselect: 11.0.0-rc.1

in that case maybe try the latest Svelte v4 release to see if the error changes or disappears

In Svelte v4.2.19 it gets compiled successfully but I got the following error in the browser console when the component needs to be rendered:
Component.js:130 Uncaught TypeError: Cannot read properties of undefined (reading '$$')
    at init2 (Component.js:130:44)
    at new MultiSelect (MultiSelect.svelte:410:43)
    at create_fragment7 (App.svelte:9:44)
    at init (Component.js:148:34)
    at new App (App.svelte:6:14)
    at main.ts:4:1
    at main.ts:4:61
init2 @ Component.js:130
MultiSelect @ MultiSelect.svelte:410
create_fragment7 @ App.svelte:9
init @ Component.js:148
App @ App.svelte:6
(anonymous) @ main.ts:4
(anonymous) @ main.ts:4

I have a main.ts file which is calling the App.svelte component.
main.ts:
import App from './App.svelte';
import './main.css';

new App({ target: document.getElementById('admin-ui-app')! });

App.svelte:
<script lang="ts">
	import MultiSelect from 'svelte-multiselect';

	const ui_libs = [`Svelte`, `React`, `Vue`, `Angular`, `...`]

	let selected: any = [];
</script>

<MultiSelect bind:selected options={ui_libs} />

that sounds like it might be a config issue on your end. can you retrieve the line on which it fails from Component.js:130:44 to see what object the $$ is being accessed on?

I don't have a Component.js file, it's from the Svelte source code: https://github.com/sveltejs/svelte/blob/6045028666ba6b19ab03571f123ea62fac95b642/packages/svelte/src/runtime/internal/Component.js#L130

i know, thanks for digging that up. i figured you could maybe command-click on the error message to get into your node_modules where the error originates.
in any case, sounds like the cause of TypeError: Cannot read properties of undefined (reading '$$') or maybe esbuild is that document.getElementById('admin-ui-app')! returns null

I found out what was the problem. 🙏
I had to add:
{
  ...
  alias: { svelte: 'svelte' },
  ...
}

to the esbuild config.
Thank you for your help.

glad you fixed it and thanks for reporting back! 👍 might help others who encounter the same issue


Indoor and outdoor flight

The parrot drone has different settings for outdoor and indoor flight. This seems to affect its PID system for sustaining stable flight. I have tried to find a way to set the drone to either indoor or outdoor flight using this library, but cannot find how to do this. Is there a way of doing this using ar-drone?

I think client.config('control:outdoor', true) will tell the drone it's flying outdoors.
From page 79 of the AR.Drone Developer Guide:
CONTROL:outdoor
Description:  This settings tells the control loop that the AR.Drone is flying outside.
Setting the indoor/outdoor flight will load the corresponding indoor/outdoor_control_yaw, indoor/outdoor_euler_angle_max and indoor/outdoor_control_vz_max.
Note: This settings enables the wind estimator of the AR.Drone 2.0 , and thus should always be enabled when flying outside. Note: This settings corresponds to the Outdoor flight setting of AR.FreeFlight.
AT command example : AT*CONFIG=605,"control:outdoor","TRUE"


lint/stylePropObject for React

This PR adds a rule for ensuring the style property value is an object. #341

Sweet, thanks! I think we'll want the react/jsx rules prefixed with react or jsx but we can sort out the consistency issues later.


Title text on breaking changes page needs to be updated

The page at https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/breaking-changes/compiler breaking changes - dotnet 7 indicates at the top "This document lists known breaking changes in Roslyn after .NET 6 all the way to .NET 7." but the file title says "C# compiler breaking changes since C# 10".  Also, the file is located under the C# 11 folder in the side navigation with the name "Breaking changes".  Finally, the URL says dotnet 7.
While fixing these inconsistencies, is it possible to keep the breaking changes from versions older than C#10?  Maybe list the breaks in reverse order (C#10 at the top, C# 6 at the bottom).  Another option would be to list breaking changes under each C# version, like how C#11 does.  These breaking changes need to be documented so transitions to the new .NET versions can be done correctly and completely.

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

ID: 55fec18d-f110-36a3-3c1c-8d9d80d4de57
Version Independent ID: 3c2bd421-7880-b8e8-f9f9-dc22175ac8db
Content: C# compiler breaking changes since C# 10
Content Source: [docs/compilers/CSharp/Compiler Breaking Changes - DotNet 7.md](https://github.com/dotnet/roslyn/blob/main/docs/compilers/CSharp/Compiler Breaking Changes - DotNet 7.md)
Product: dotnet-csharp
Technology: csharp-whats-new
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

Hi @Trisped
I'm going to close this as not planned.
This article is published from the dotnet/csharplang repo. As we've improved our processes, this page is maintained by the compiler developers. The information on older breaking changes is also published, but we didn't do the extra work to reformat the compiler dev docs and publish in a different format. The C# LDM puts a very high bar on breaking changes. This means there are relatively few breaking changes, and those are often constrained to edge cases in code.
The use of ".NET 6" / "C# 10" and ".NET 7 / C# 11" is by design. C# 10 shipped with .NET 6. C# 11 shipped with .NET 7. We want both terms in the title and header to improve SEO for searches.


Add delete buttons to GUI

Several things done in this PR as during the adding of the GUI several smaller bugs were found:

the to_dataframe function was enabling a race condition. Note that the functionality itself was correct because it followed the rule of "multiple reads - single write". However, if somebody else wrote the table in the middle the function crashed. The new implementation is not only thread safe but also at least 2X faster.
The prep template sample deletion was not safe. Having an artifact attached is enough to not allow sample deletion. Fixed and test added.
Connected the GUI with the backend to delete samples/columns from the templates. @antgonza noticed that it can be slow, so we offload it to the cluster. To simplify code, a single dispatchable function has been added that can be used for both template types and both functionalities, simplifying a lot of code duplication.
The HTML code that @antgonza added had a fair amount of code duplication due to the previous structure of the code - I've reorganize it to reduce the amount of code duplication.

Coverage decreased (-0.04%) to 83.852% when pulling 675a1ffcc95fd7b622d59aca570ceea50895a6ee on josenavas:add-delete-to-gui into 4b632dd2938a80d77bcfae82e39547c15b9f6fac on biocore:master.

Some comments

👍  will merge once tests pass, thanks!!!

@josenavas actual errors!

Coverage increased (+0.1%) to 84.038% when pulling 86cb6368b610192be4a6e628a162c72451debde5 on josenavas:add-delete-to-gui into 4b632dd2938a80d77bcfae82e39547c15b9f6fac on biocore:master.

Tests are passing!


Add datetime package for date/time format helpers

This replaces the date/time helpers that are generated per SDK. The Parse func is typically used for handling date/time values returned in respone headers. The date/time types are used in SerDe methods.
Part of the fix for https://github.com/Azure/azure-sdk-for-go/issues/21584

This replaces the time helpers that we generate, e.g. https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/resourcemanager/compute/armcompute/time_rfc3339.go
The various time_*.go files will go away.


Backslashes 941170

This PR moves rule 941170 to use \x5c backslash representation and adds two tests for it.
As a bonus, the two existing tests for rule 941170 get Accept headers added (so that they no longer trigger rule 920300, "Request Missing an Accept Header").

Meeting decision January: @emphazer will review this PR.

@emphazer Can you take a look at this one?

@fzipi sure i will do it this week

i tested it with 10gb data and the matches are exactly the same.
this PR is ready to be merged!

Awesome! Merging!


service: Failed at step EXEC spawning /bin/ash: Permission denied

rkt Version: 1.25.0
appc Version: 0.8.10
Go Version: go1.7.5
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.9.24-coreos x86_64
--
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1353.7.0
VERSION_ID=1353.7.0
BUILD_ID=2017-04-26-2154
PRETTY_NAME="Container Linux by CoreOS 1353.7.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
--
systemd 233
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN default-hierarchy=legacy

What did you do?
acbuild --debug begin
acbuild set-name hauscloud.de/alpine_source
rm -rf .acbuild/currentaci/rootfs
acbuild copy "$SOURCE/alpine" /
acbuild label add version $2
acbuild label add arch amd64
acbuild label add os linux
acbuild run --engine chroot -- apk update
acbuild run --engine chroot -- apk --no-cache add busybox-suid
# built aci from alpine minimum source and
acbuild run --engine chroot -- adduser -h /home/paul -s /bin/ash -g paul -D paul
acbuild set-user paul
acbuild set-group paul
acbuild set-exec -- ash
acbuild write --overwrite "alpine_source.aci"
acbuild --debug end

sudo rkt run --insecure-options=image --interactive alpine_source.aci --net=host --debug

What did you expect to see?
ash prompt
What did you see instead?
alpine-source.service: Failed at step EXEC spawning /bin/ash: Permission denied
Error: Unable to determine interpreter for "/lib/ld-musl-x86_64.so.1"
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Container rkt-64c68754-444f-47c8-8ea8-60d0b6ba3db7 failed with error code 203

I have tested the exact same build using the quay.io/coreos/alpine-sh dependency and that works fine.  It is however alpine verion 3.2 as opposed to the current 3.6 and I dont want to rely on this mysterious image. And i want to learn.

Error: Unable to determine interpreter for "/lib/ld-musl-x86_64.so.1"

Please make sure that such a loader exists at that location, that it has proper read+exec permission, and that is ABI matches the one for the OS you are currently running.

extracted from source by root.
ls -las /lib
8 drwxr-xr-x.  5 root root    4096 May 24 17:51 .
8 drwx------. 18 root root    4096 May 24 17:51 ..
...
556 -rwxr-xr-x.  1 root root  563688 May 23 22:27 ld-musl-x86_64.so.1   <- looks good
...
I dont know how to check an ABI but the root fs is alpines at https://nl.alpinelinux.org/alpine/v3.6/releases/x86_64/alpine-minirootfs-3.6.0-x86_64.tar.gz.  I expoect it to be in order.
Furthermore it should be noted that if i dont change the execute user, everything works fine.  This problem only appears when trying to execute application within container as non root.

Is .. 0700 on purpose?

DOH!
Fixed and now working.  Thankyou for your time :)
Great project. Keep up the good work.

Great to hear! I'm closing this as not-a-bug.


[Improvement] Open engine session and send credentials in the one

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

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

What would you like to be improved?
This is a follow up of #2059
In that pr, we send credentials when opening session.
But openEngineSession and sendCredentials are not in one rpc request.
We might meet corner case when hive delegation is expired.
For example:
If hive delegation token is expired, we will lose the shared metastore client.
And when opening engine session, it will create a sparkSession, which will recreate the shared metastore client.
But it will fail because the old hive delegation token is expired, but it has not received the new hive delegation token yet.
So, the openEngineSession operation will fail.
So, we need gather openEngineSession and sendCredentials in the one to fix the corner case.
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

cc @lightning-L would you like to take this one?

FYI:
You can getEncodedCredentials before openEngineSession.
Then put it into the configuration of TOpenSessionReq.
Then apply the credentials in  SparkTBinaryFrontendService::OpenSession.

cc @lightning-L would you like to take this one?

ok


Observer functions in dom-repeat are not correctly updated for non set operations

Template: :scroll:
<template is="dom-repeat" items="[[getFoo(foo.*)]]">
   <p>[[item]]</p>
</template>

Component: :large_orange_diamond:
this.push('foo', Math.random());

getFoo: function(f) {
  return f.base.concat(['wow']);
}

Expected: :cat2:
When I :pushpin: push elements into foo, they should show up in the DOM
IRL: :earth_asia:
nothing shows up :cry:
Hack Fix: :computer:
calling :ear: set and reassigning the entire foo entity correctly shows things

:fire: broken example - http://jsbin.com/gixedavoti/1/edit?html,output
:white_check_mark: working hacked example - http://jsbin.com/kibutanave/1/edit?html,output

:100: :ice_cream: :sun_with_face:

@kevinpschaaf this sounds familiar, can you dedupe?

This is still an issue with Polymer 2: http://jsbin.com/xumuyixege/edit?html,console,output


feat(pkg/command): add a options struct to store the values provided …

…by the user through the flags

Codecov Report

Merging #7 (0dcabf4) into main (6197d52) will decrease coverage by 3.62%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
- Coverage   86.95%   83.33%   -3.63%
==========================================
  Files           2        4       +2
  Lines          46       66      +20
==========================================
+ Hits           40       55      +15
- Misses          3        8       +5
  Partials        3        3

Impacted Files
Coverage Δ

pkg/client/client.go
0.00% <0.00%> (ø)

pkg/command/command.go
100.00% <100.00%> (ø)

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 6197d52...0dcabf4. Read the comment docs.


Proposal listener fix

This PR fixes the bug in which newly created proposals were not always added automatically to the proposals list.
This was done by checking if the proposal start block is in the future. If so, then the user vote power is set to undefined.
These changes also have the side effect of making the proposal states update automatically as new blocks are received, since currentBlockNumber is now a dependency of the useProposalsWithoutVotes hook.

Yes, thinking now maybe I should split useProposalWithoutVotes hook into two separate ones, one for static data that doesn't change, and one for dynamic data that could change with a new block.

The description of this PR is no longer correct right? The last paragraph

Yes, description updated.


Create 0000-01-02-Lekanac.md

Lekanas File

layout: slide
title: "Welcome to our second slide!"
Your text
Use the left arrow to go back!


Can not start keyd-application-mapper with GNOME 3.38 wayland

It worked in X11, but Wayland could not start keyd-application-mapper. The extension was not installed too.
pi@rpi:~ $ keyd-application-mapper
Gnome detected
Extension ?keyd? doesn't exist
Traceback (most recent call last):
  File "/usr/bin/keyd-application-mapper", line 379, in <module>
    mon.init()
  File "/usr/bin/keyd-application-mapper", line 274, in init
    if 'DISABLED' in run('gnome-extensions show keyd'):
  File "/usr/bin/keyd-application-mapper", line 36, in run
    return subprocess.check_output(['/bin/sh', '-c', cmd]).decode('utf8')
  File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/bin/sh', '-c', 'gnome-extensions show keyd']' returned non-zero exit status 2.

gnome 3.38
keyd 2.2.6-beta

Gnome's extension system is notoriously erratic and breaks compatibility across versions. Currently I don't plan to support anything older than 41, but patches are welcome :). If upgrading doesn't solve the problem feel free to open another issue.

The cause and timing are unknown, but keyd was added to gnome extensions. It also worked with gnome 3.38 wayland.

I have found that keyd-application-mapper may not work properly if autokey-gtk or its dependent packages are installed. I also found that the keyd extension wouldn't install unless I logged in to Gnome in Wayland.
Uninstall autokey-gtk
$ sudo apt remove autokey-gtk && sudo apt autoremove
Install keyd
$ sudo apt install python3-xlib && git clone https://github.com/rvaiya/keyd && cd keyd && make && sudo make install && cd && sudo rm -r ~/keyd && sudo adduser <USERNAME> keyd && touch ~/.config/keyd/app.conf
Reboot
$ sudo reboot
If you're using Xorg, switch to Wayland and login
Install keyd-application-mapper
$ keyd-application-mapper
Logout and Login with Xorg or Wayland
Open the Extensions app and enable keyd
gnome3.38
keyd 2.2.6-beta

I have found that keyd-application-mapper may not work properly if autokey-gtk or its dependent packages are installed.

I believe autokey is an evdev based remapper. In general it is ill advised to use multiple pieces of remapping software since they can interfere with each other. If possible, you should try and do everything in keyd.

I also found that the keyd extension wouldn't install unless I logged in to Gnome in Wayland.

Yes, this is by design. The user is expected to run keyd-application-mapped in the target environment. If you run it under the X version of gnome it will favour X based application tracking.

Open the Extensions app and enable keyd

It should enable itself using the gnome-extensions command, but it is possible this is broken on earlier versions. As I mentioned, anything older than 41 is unsupported.


Invalid Region detected (One or more regions have not been tagged)

I'm trying to tag some images and I cannot move to the second image because of this message. Attached  is a screenshot.

Any help is appreciated

i am also getting the same error, any help appriciated.
thank you


Add "nohttperror" URL parameter

Not sure about the name, but some sites (forums) that proxy images.
When we return steve/alex with 404, or the (potentially) outdated avatar with a 50x, these services will not proxy the image.
GitHub's usercontent proxy does the same:

Ugh..it's hard to decide what the right thing to do here is. Most people will immediately be confused as to why steves are showing, and think it's broken. Just setting a 200 http code could break apis that check for the status code. Maybe make the parameter show the actual code, rather than the opposite.

I'm not sure what you suggest.. So we should always return 200 unless that extra param is set?

I see two options here:

Send all images with 200 HTTP code
Send images with proper HTTP code (200, steve = 404, mojang issues = 503)

We need a URL parameter to toggle between those two. The first one seems is wrong, so using it as the default would be bad.

We're now using 200 for fallback images, so we're only left with the 503 problem.
Apparently Chrome(ium) doesn't render images with 4xx or 5xx status code.
Seems like chromium intends to render images regardless of the status code, so the bug has been confirmed:

That's surprising. We explicitly try to ensure that we show images regardless of status code error, but I guess that logic must have regressed somehow.

More details: chromium-464515. We're not alone:

This is a big problem for us as we have a user ID photo system that is designed to 404 and show a default image. Pages full of broken images aren't really acceptable. I'm now going to have to break best practices and make the 404 image return a 200 until this is fixed

tl;dr Browsers should do fine with the 503, I think having this parameter optional should work for image caching proxies (i.e. GitHub, etc).
How about calling it error=false?

Actually, I'm unsure about this whole thing. Image cache/proxies should forward 404 if the Content-Type is image/whatever – Other User-Agents (i.e. Browsers) do that as well.
I'll probably open an issue at atmos/camo. What do you think @Jake0oo0?

here it is: atmos/camo#75

Closing because it's not a bug on our side. People need to fix their image proxies.


nixos/hedgedoc: Set StateDirectory to workDir and uploadsPath

Description of changes
Currently, hedgedoc doesn't allow uploading images into documents.
The cause of the failing uploads is, that the "uploadsPath" is not included in the systemd StateDirectories of the service configuration.
Tested on a vanilla NixOS with and without this patch. Without, i cannot upload images, with the patch it works.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

This is wrong. StateDirectory only accepts paths relative to /var/lib


GHSA-p782-xgp4-8hr8 Vulnerability

https://github.com/advisories/GHSA-p782-xgp4-8hr8
This one is a bit stickier than the other issue I opened, seems like it must be a sub-dependency that is causing the problematic library to be included, because golang.org/x/sys has what seems to be an OK version specified in go.mod 😕

fixed


Python dev ctrl to use BLE implementation from src/platform/ instead of ChipCoreBluetoothMgr.py

Python dev ctrl to use BLE implementation from src/platform/ instead of ChipCoreBluetoothMgr.py

Closed by #4542


Updated syllabus: CSCI 150 - Discrete Structures

Updated the CSCI 150 syllabus for Spring 2023 to reflect the changes of his grading policies
cs150_schweitzer_syllabus_s23.pdf

Thank you so much! Finally merged this in and added you as a contributor in https://github.com/Hunter-Open-Source-Club/syllabi/commit/9bdb29790102690e276d2e8cf42cefee7e832046. I'm beyond late getting to this, sorry.
Do you have any other syllabi on hand you can share?


Support generation tasks and various improvements

I will add bertscore later. But also you don't have to merge this since this doesn't block me. Only if you think this is helpful.

bertscore added

Amazing, thank you for extending FormatSpread for generation tasks!!!