"Unknown error" in ResizeSensor.getElementSize()

Dear Marc,
first things first: Thank you so much for conceiving and maintaining this excellent library.
We just wanted to let you know that we are getting these traces from our Javascript telemetry subsystem which catches exceptions happening on the browser:
"stackframes": [
    "getElementSize()@webpack://..../node_modules/css-element-queries/src/ResizeSensor.js:70:0",
    "onScroll()@webpack://..../node_modules/css-element-queries/src/ResizeSensor.js:217:0"
]

As we are still running version 1.1.1, that would match this specific line in the source code:
https://github.com/marcj/css-element-queries/blob/1.1.1/src/ResizeSensor.js#L70
We will update to version 1.2.0 and see whether the problem is still persistent or if any upgrade on its way mitigated it already. Ah, presumable it only happens with Internet Explorer
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; wbx 1.0.0; rv:11.0) like Gecko

Thanks for listening and with kind regards,
Andreas.

Do you have the actual error message as well? Yeah, please let me know whether it happens on newest version as well. But it probably will since we still have this line of code there.

Do you have the actual error message as well?

It's really just literally "Unbekannter Fehler" as long as what our telemetry JSON is telling us about the error message. I am blaming Internet Explorer for that.

Interesting. Let me know when you got more information about that, then we can try to replicate/debug.

I would like to ramp up an Internet Explorer 11 somewhere and just execute element.getBoundingClientRect() for some actually valid element on the developer console - I believe IE11 will have such a thing these days? - and then see what happens.
However, I lost my VirtualBox setup recently, so I currently lack an Internet Explorer which is just a fingertip away and I don't see any in my nearest distance. Saying that, I will definitively get back to this at some time when the telemetry reports will keep nagging me or the next time when I will need a working Vagrant setup.

You get free VMs here for all platforms with whatever IE you want, directly from MS, without installing anything manually: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ Let me know what you find.

Now remembering that about the free VMs from MS, I'll try my best. Thanks! [1] says it's an Internet Explorer 11 on Windows 10 which has been triggering this error, according to the User Agent string. Currently, I am downloading IE11 for Win8.1, afterwards maybe MSEdge on Win10.
[1] https://developers.whatismybrowser.com/useragents/parse/


Improve documentation

Add a more detailed description of the project

I'll do it too

thank you man!


Step does not save log if not using xcpretty

The step apparently doesn't save a log file if you don't use xcpretty and because BITRISE_XCODE_TEST_FULL_RESULTS_TEXT was removed you can't post-process the log output anymore.
Secondly, the step still claims this is a valid environment variable so the text should be updated.
Lastly, it would be really nice if you could get both the raw log and the xcpretty output. Using tee or the go pipe stuff it should be fairly easy to do that.
Background: I'm working on a step to automatically comment on pull requests when a build fails and include the failing test lines from the log. I already have everything working locally, I just can't get the actual log output for processing.

v1.10.0 is now out and includes this: https://github.com/bitrise-io/steps-xcode-test/releases/tag/1.10.0
Thanks for the request! 😉


Token data used for authorization is included in enterprise audit log events - [GA]

Summary
For enterprise audit log events where a token - PAT (Classic), fine-grained PAT, OAuth, GitHub Apps - was used as the method of authentication, the audit log will contain a hashed rendering of the token used for authentication, as well as the token type and token scope. In doing so, customers will be able to query actions a token has been used to perform on enterprise assets.
Intended Outcome
Compromised tokens have the potential to provide threat actors with access to private data. After learning of a token compromise, we know that administrators and security professionals want to understand the actions taken using the corrupt token. To support Enterprise customers to complete these investigations, we will enhance the audit log data by logging identifiable and queryable token data in the audit log for events using tokens for authentication.
How will it work?
The audit log will display the authentication methods, as well as the last 8 chars of the token for authentication, for audit log events using any token for authentication. This data will be available in the GitHub enterprise account UI, the audit log API, streaming, and in the Site Admin dashboard for GHES customers.

🚢 this has shipped to dotcom! https://github.blog/changelog/2022-11-09-displaying-authentication-token-data-in-your-enterprise-audit-log-is-generally-available
Leaving open to track GHES release.

This is now available on GHES 3.8: https://github.blog/2023-03-07-github-enterprise-server-3-8-is-now-generally-available/


Line height should be a variable

--line-height should be a css variable and applied to the body

Line heights are handled with --typeset variables now


Add support for openEuler OS

Add support for openEuler OS
Signed-off-by: Dai zhiwei<EMAIL_ADDRESS>

Can one of the admins verify this patch?

okay to test.


Cleanup and update base.yaml jobs to CRC 2.30 (OCP 4.14)

Update from crc 2.19 to 2.30
Extract nodeset from inline to nodeset.yaml
Add ocps group (this may be used in the future)
Move to unified zuul node label

JIRA: OSPRH-4340
JIRA: OSPRH-2712
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve

recheck
Wait for OpenStack subscription creation timeout

recheck

/lgtm


Fix ssi_expander.py

Fixed ssi_expander.py
Tested on mac with different relative and absolute paths

Can you explain what this fixes?

sure.
Function InlineIncludes requires exactly 2 params, but ssi_expander.py call it using only one
The result:
$ ./ssi-server/ssi_expander.py ./template/ ./test/
Traceback (most recent call last):
  File "./ssi-server/ssi_expander.py", line 45, in <module>
    process(source, dest)
  File "./ssi-server/ssi_expander.py", line 27, in process
    file(dest_path, 'w').write(ssi.InlineIncludes(src_path))
TypeError: InlineIncludes() takes exactly 2 arguments (1 given)

Line 22 - because dirpath always has a source as a prefix. e.g.:
$ python
Python 2.7.10 (default, Oct 23 2015, 19:19:21)
[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-7<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> for dirpath, dirnames, filenames in os.walk("./ssi-server"):
...   print dirpath, dirnames, filenames
...
./ssi-server ['.git'] ['about.html', 'index.html', 'LICENSE', 'README.md', 'ssi.py', 'ssi.pyc', 'ssi_expander.py', 'ssi_server.py']
./ssi-server/.git ['hooks', 'info', 'logs', 'objects', 'refs'] ['config', 'description', 'HEAD', 'index', 'packed-refs']
./ssi-server/.git/hooks [] ['applypatch-msg.sample', 'commit-msg.sample', 'post-update.sample', 'pre-applypatch.sample', 'pre-commit.sample', 'pre-push.sample', 'pre-rebase.sample', 'pre-receive.sample', 'prepare-commit-msg.sample', 'update.sample']
./ssi-server/.git/info [] ['exclude']
./ssi-server/.git/logs ['refs'] ['HEAD']

Looks good, thanks for the fix.
I don't really use this project much any more. Any interest in taking it over?

I'm going to use it for a while, so if you don't need I can take care about it.

Great. I've added you as a collaborator to the repo.
I stopped using this once I learned about static site generators.


Consider adding WS instead of Polling events (Teleporter)

Issue Type
[ ] bug report
[ X] feature request

Current Behavior
eth_subscribe for ws has been rolled out
TBD

open PR available, closing for now as there is no intention of merging it for now.


Replaced SQLDatabaseChain deprecated direct initialisation with from_llm method

Removed usage of deprecated methods
Replaced SQLDatabaseChain deprecated direct initialisation with from_llm method
Who can review?
@hwchase17
@agola11

thanks @imeckr!


UniFlagStorage is completely broken in master

We need to grab the implementation from #910, add guards, and conditionally include GL in the vanilla core, if no one has a better idea. Profiling #926 also needs a similar solution.

fixed by #953


Landing page

Added a landing page as a routed component for the root domain "/". The rest of the application is now under "/registries"

Sorry, we were working on a forked repo and by accident I submitted the pull request to the original repo

no problem!


Won't build on Windows 11

So I'm currently creating an game engine and i wanted to look at other smaller engines when I saw this and wanted to try it I cloned it and ran genWinProject.bat and build it using Visual Studio 2022. But i get these 2 errors:

My specs:

Asus Tuf Gaming A15 Laptop
AMD Ryzen 7 6800H
16 GB DDR5 4800 MHz
NVIDIA GeForce RTX 3070 Laptop GPU 8 GB VRAM
AMD Radeon Graphics 512 MB VRAM

I will create a pull request soon because you forgot to add a precompiled header


fix: datasets related objects, apply filter and openapi spec

SUMMARY
Applies filter on datasets related object and simplifies OpenApi spec using mashmallow schemas
TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #10252 into master will decrease coverage by 4.71%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #10252      +/-   ##
==========================================
- Coverage   70.16%   65.44%   -4.72%
==========================================
  Files         598      598
  Lines       31949    31965      +16
  Branches     3223     3223
==========================================
- Hits        22418    20921    -1497
- Misses       9424    10863    +1439
- Partials      107      181      +74

Flag
Coverage Δ

#cypress
?

#javascript
59.47% <ø> (ø)

#python
69.60% <100.00%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

superset/datasets/api.py
92.02% <100.00%> (+2.82%)
:arrow_up:

superset/datasets/schemas.py
94.20% <100.00%> (+2.04%)
:arrow_up:

superset-frontend/src/SqlLab/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/explore/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/SqlLab/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/explore/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/setup/setupColors.js
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/chart/ChartContainer.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 143 more

Continue to review full report at Codecov.

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


fix[security]: Disable nginx server signature by default

Motivation and context

Disable nginx server signature to not display nginx and OS version to the public, which will make vulnerability discovery by third-party actors slightly more difficult.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

Security Enhancements

Improved privacy by configuring the server to not disclose software version numbers in responses.
Enhanced security by disabling the nginx server signature to mitigate potential attacks.
Introduced a security enhancement by disabling the nginx server signature by default to make it harder for attackers to find known vulnerabilities.

@jackylamhk , thank you for the PR. Could you please add a comment with explanations why the change is necessary into the nginx config? Also, please add a line into changelog. Every PR which improves something, should have something like that. Have a great day!

@nmanovic Thanks for reviewing this. See comment above for explaination, and I believe CHANGELOG.md is auto-updated via GitHub Actions.

@jackylamhk , I read comments. I want to have the comment in the code to explain it explicitly. Also, CHANGELOG.md isn't updated automatically. See how other PRs do that and also read instructions inside CHANGELOG.md.

@nmanovic Sorry - I misunderstood your original request. I've added an in-line code comment to provide context and created the CHANGELOG fragment as requested. Kindly let me know if anything else needs to be done.

@nmanovic Sure - just pushed a new commit.


Grobid Vulnerabilities

Dear Grobid Team,
We are thrilled by the remarkable achievements of Grobid in processing literature PDFs and are eager to delve deeper into its capabilities. While exploring Grobid, we've encountered some inquiries regarding its dependencies and the vulnerabilities associated with them.
Upon installing Grobid as a standalone application, we have observed certain vulnerabilities within the JAR files located in the 'grobid-installation\grobid-service\lib' directory. We've listed a few of these vulnerabilities for your reference along with the link of National Vulnerability Database (NVD):
i.	hibernate-validator-5.4.3.Final [https://nvd.nist.gov/vuln/detail/CVE-2019-10219]
ii.	scala-library-2.10.3 [https://nvd.nist.gov/vuln/detail/CVE-2017-15288]
iii.	commons-text-1.8.jar [https://nvd.nist.gov/vuln/detail/CVE-2022-42889]
iv.	snakeyaml-1.24.jar [https://nvd.nist.gov/vuln/detail/CVE-2022-38750]**
v.	and others.
We attempted to update these JAR files to their latest versions manually, but this solution proved ineffective for all cases. Therefore, we would appreciate your insights into whether Grobid has any plans to address these vulnerability issues.
With regards,
Sandesh BS

Thank you very much @sandeshbssuresh-agi for reporting these vulnerabilities ! This is very appreciated, and we will do our best to fix them.
iii. and iv. should be already fixed in the current master thanks to upgrade of the dependencies.
i. is related to the version of Dropwizard we are using (web service framework). Upgrading will stop the compatibility with JDK 1.8 that we were trying to maintain, but it's probably time to move on to java 11 as minimum requirement. See PR #1031 for this.
ii. is more annoying because the related dependency ("stringmetric") has not been updated to a more recent scala version. It is used to compute string distances for the evaluation, so we could remove it from the core and service part.
In general, Grobid should be a service for internal ingestion/pipeline of PDF, not facing directly the web and users, so these vulnerabilities are not so problematic I think.

Your time and attention are valued; thank you.


🗎 Behaviour quirks link broken in FAQ

Steps to Reproduce
The FAQ says

For solutions to this issue, read the behavior quirks guide in the Standalone Python Builds documentation for solutions.

However, that link is giving me a 404 message.
Expected Result
I expected to be redirected to a working web page somewhere.
Actual Result
I got a 404 error.
Version Info
Not applicable.
Stacktrace
Not applicable.

Thanks!

For reference, it's at https://gregoryszorc.com/docs/python-build-standalone/main/quirks.html

@zanieb Thanks for the link! 🙏


Swapping between Ł/ł resets to Ł after force closing

@losh11 I can take a look if you want.

bugfix-Labelrefresh


Feature request: try playing local files first

OS:
OS X
Issue Descriptions:
It would be great to be able to point GPMDP to a local folder hierarchy, with the intention that if a mp3 matching the current play request is found there, it will be played locally as a first try.
This has (a) a certain logic to it given that Google Play Music can source (and match) tracks from local files, and (b) would be very helpful for those of us who live in slow/low-bandwidth parts of the world (ie. most of it as of mid 2016).

While I commend the thought I'm not sure this is something that will ever be implemented in this project. There have been many requests for similar things such as offline music, playlists etc and the general consensus is that it's not possible and/or out of scope.

That's a tad dismissive, especially given the only similar reference I've found has been to an issue that was closed without reason (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/932). No discussion or further questions re use cases or alternatives?

I apologize if it seemed that way, my reasoning was stated in that thread as well though. It will add a lot of overhead in the player as it causes us to heavily rely on not only the DOM of GPM but also the internals of their JS. In order to play local files in their player we would need to override 100% of the functionality of Google play music. Its not as simple as pointing a audio tag to a local file and everything will just work.

That expands usefully on "a lot of overhead" -- in effect a near-complete rewrite is a lot of overhead and I can see it would be unreasonable given the project's scope. Thanks.


[#152635692] Configure UAA to use our custom assets on login/accept webpages

🐝🐝🐝 Merge after #1105 🐝🐝🐝
What
Uses an app that #1105 deployed to serve a new custom stylesheet on the UAA webpages. This uses an asset_base_url that is marked as deprecated, but we have chosen to use it for now. Tests are added to guard against its removal or our custom CSS becoming out-of-date. See commit messages for details.
Deploying this will update UAA. Thanks to #1104 we expect the downtime to be momentary if at all.
How to review

Review #1105 and this PR.
Merge #1105.
Merge this PR.

Who can review
Not @46bit @stephenjoe1 @bleach

I've just noticed that this PR doesn't match the uaa-restyle-pr2-152635692 branch I had locally. It's functionally the same but missing some tidyup I'd done.

I've just noticed that this PR doesn't match the uaa-restyle-pr2-152635692 branch I had locally. It's functionally the same but missing some tidyup I'd done.

No problem. Leave a comment when you'd like me to re-review.

Dan had a good idea and we're now testing the checksum of the stylesheet, rather than keeping a copy of it saved. I deployed my pipeline with an incorrect checksum to see what would happen if the stylesheet changed:

@dcarley This is ready for review once more. 👍


Define encoding

resolved: #28
details:
Defined encoding.
This is used for making hexadecimal byte code.

[x] Test case

LGTM


[TwigComponent] Remove 3 futures deprecations (minor)

Q
A

Bug fix?
no

New feature?
no

License
MIT

Fix deprecations
Framework
1x: Since symfony/framework-bundle 6.4: Not setting the "framework.handle_all_throwables" config option is deprecated. It will default to "true" in 7.0.
1x in ComponentFactoryTest::testTwigComponentServiceTagWithoutKeyButCollissionCausesAnException from Symfony\UX\TwigComponent\Tests\Integration

1x: Since symfony/framework-bundle 6.4: Not setting the "framework.php_errors.log" config option is deprecated. It will default to "true" in 7.0.
1x in ComponentFactoryTest::testTwigComponentServiceTagWithoutKeyButCollissionCausesAnException from Symfony\UX\TwigComponent\Tests\Integration

PHPUnit
1) Symfony\UX\TwigComponent\Tests\Unit\TwigPreLexerTest::testPreLex
Data Provider method Symfony\UX\TwigComponent\Tests\Unit\TwigPreLexerTest::getLexTests() is not static

Fixed the previous fail (handle_all_throwable does not exist before Symfony 6.2)
The new one (phpcs) is fixed in https://github.com/symfony/ux/pull/1122

Thanks Simon!


unique translation IDs: missing some translations

Menu Categories:

Menu Feeds:

Menu Settings->Users

@stratmaster fixed in #240. Also I have just found that "No feed." also missing.

"No feed" bug also fixed.

@L11R Thank you very much! I've opened another pull request, cause some strings still have been faulty (IMO).

Thank you guys for your contributions. Let me know if you spot other mistakes.


fsc fails with StackOverflowException on a file with > 485 let bindings

Please provide a succinct description of the issue.
C:\Users\Eric>"C:\Program Files (x86)\Microsoft SDKs\F#\4.0\Framework\v4.0\fsc.exe" -o:obj\Debug\Test.dll -g --debug:full --noframework --define:DEBUG --define:TRACE --optimize- -r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp.NETFramework\v2.0\<IP_ADDRESS>\FSharp.Core.dll" -r:C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll -r:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll" -r:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll --target:library --nowarn:00052 --warn:5 --warnaserror:76 --vserrors --LCID:1033 --utf8output --fullpaths --flaterrors --highentropyva- --sqmsessionguid:d9b14b80-365b-425e-811d-066cf3c283cb Test.fs
Microsoft (R) F# Compiler version 14.0.23413.0
Copyright (c) Microsoft Corporation. All Rights Reserved.
Process is terminated due to StackOverflowException.
Related information
I generated a test case with the following function, but I will also attach the generated file
Test.zip
let testlet path i =
    let head =
        [|"module TestCase"
          "open System"
          ""|]
    let binds = [|0..i-1|] |> Array.map (fun i -> sprintf "let x%d = \"%d\"" i i)
    System.IO.File.Delete(path)
    System.IO.File.WriteAllLines(path, Array.append head binds)

Provide any related information

Operating system

Windows 10 build 14393.105

Note, this issue may be related to #851, I wasn't sure, and I had it boiled down to a simple example, so I filed a new bug. I apologize if I've created noise.

@estokes could you confirm that the issue doesn't happen if you compile in RELEASE mode instead of DEBUG?
In #851 according to last information there, it is related to the diasymreader component which I assume is outside of this repository, not sure if owner of this component could fix it for new release.

Confirmed. It does not happen when not compiling debug code.

it's happening in pdbCloseMethod in ilwritepdb.fs - will try to send your repro as unit test

see https://github.com/Microsoft/visualfsharp/pull/1537

AFAIK we have existing tests like this, I don't understand why CI isn't catching this problem.
So we both need to fix this and check our CI test coverage

@dsyme  see #1537 I tried to reprocude in the normal fsharpQA test suite, but seems I don't get that to go red. I also proposed a "fix"


Create a webhooks request form

Is your feature request related to a problem? Please describe.
Now we have webhooks requests on a daily or weekly basis. It's not optimal to send those request to @bonustrack in DM.
Describe the solution you'd like
A form we can link to from the docs and people can enter a domain and the events they want to subscribe to and then the role with that task assigned get's an email.

Should be fixed via the Webhook UI.


Add documentation about running cwltool from jupyter notebooks

Workflows can be run from jupyter notebooks using:
%%bash
cwltool /home/jvdzwaan/cwl-working-dir/add_multiply_example_workflow.cwl --num1 2 --num2 3

Or using a cwltool Factory? (needs to be tested)
https://github.com/common-workflow-language/cwltool#import-as-a-module


HHH-16606 - Class cast exception when retrieving only single property of array type using criteria query

Jira issue HHH-16606
When only single property of array type is selected using criteria query with explictely specified (array) result type, returned result is wrapped into object array. Thi is caused by wrongly determined result transformer as RowTransformerArrayImpl instead of RowTransformerSingularReturnImpl.

Not every array result type should be handled by RowTransformerArrayImpl.
If there is single selection of same type as result type, it should be handled by RowTransformerSingularReturnImpl.

Thanks for your great work. I simplified your fix a bit as I believe the RowTransformerArrayImpl should only be used if the result type is Object[].
Superseded by https://github.com/hibernate/hibernate-orm/pull/6729


Security issue

This package has security issues, which was privately reported to Snyk.
For repo owners: please contact me (or the Snyk team) for coordinated fix and disclosure. PGP key: https://apple502j.github.io/pubkey.txt
For users: please avoid using the package.

this was fixed in #3 and published in v2.0.1, thanks!


Add e2e tests for example projects

This PR adds e2e tests that do the following actions for each example project:

Start docker-compose located in examples/docker/docker-compose.yaml.
sbt run the example project.
Use Prometheus API to assert expectations on the metrics produced by example project.

TODO:

[x] e2e tests cannot be fully ran on GitHub Windows CI runners, because docker-compose we use does not support Windows containers.  Tests should still at least run the example projects.

Potential TODO:

[ ] e2e tests only check for existence of single metric out of a metric group - more metrics and assertions for their values could be added.
[x] e2e tests are located in IntegrationTest configuration of example projects, even though they do not need to be located under specific example project, because they do not depend on them during compile time - e2e tests could be moved to their own separate module to make examples more lightweight.
[x] docker-compose we use - examples/docker/docker-compose.yaml - needs some modifications so it can be ran with testcontainers. Instead of modifying it, we can create a temporary copy of it during a test run and apply modifications to that copy.

e2e tests are located in IntegrationTest configuration of example projects, even though they do not need to be located under specific example project, because they do not depend on them during compile time - e2e tests could be moved to their own separate module to make examples more lightweight.

A separate module for e2e sounds good to me even now. Other than clean separation and hunting down regressions, I see some future development in that module (or maybe in a similar one?) to be considered:

in this module, we could have baseline examples without the otel and collect the execution time
we could compare execution times of the same examples but with otel agent + extension to see how "heavy" mesmer is.

Note that even if our metrics and adding OTEL do not obstruct the performance much, it's great to have numbers for the users so that they can see for themselves. Also, one of the reasons for many premature optimizations was the lack of such a tool, I think.
I know it's a little offtopic but wdyt?

@lgajowy I do have two observations in regards to these topics:

Mixing example and test code introduces conflicting concerns. Ideally the examples should be bare minimum, simple applications, but tests often require additional code, harnesses and tricks to cover various scenarios. Trying to maintain these both concerns on same code can become a bit of a headache. But then again, ideally you do want your examples to be tested. I have not come up with the perfect solution for this in my OSS work, though I do have some ideas, mainly centered around tests  doing test code generation into example projects during test runtime.
Performance comparisons require very tightly controlled execution environments, so unless we want to provision a dedicated machine with specific configuration to do these comparisons, the results and value we get is rather questionable. Unless we just have these performance tests for user's/developer's local workstation use only.

I will put these new e2e tests into their own new module.

Recently added run-examples jobs need to be removed from main branch protection rules 😄

Very valid concerns

Mixing example and test code introduces conflicting concerns.

Yeah - that's what I'd avoid too. The examples we have should stay as they are. I meant the tests in e2e to be used in different ways (performance tests/regression tests). Having said that I didn't check the tools for collecting performance data so maybe the whole "performance measuring effort" should be done differently with a dedicated tool.

Performance comparisons require very tightly controlled execution environments

Oh yeah. I know that very well from the Beam project. :D For starters we should use our local machines and to generate the numbers for people we should indeed use something dedicated. Even on dedicated machines the results may vary slightly, but when you collect the historical results eg. daily, you have a general idea on how good/bad your performance is.

Hmm, I wonder how complicated it would be to setup an on-demand performance test runner machine to automate collection of performance data. I know that on the cloud such machine would not be too cheap, even if we run it only once a day. Maybe we have a spare machine in the office? It could be setup as a GitHub Action runner to run the tests on schedule - for example I am thinking about setting up a RPi4 as a GitHub Action runner at my home for ARM builds and private projects 😄

I know that on the cloud such machine would not be too cheap

We need exact numbers. Probably worth to investigate. Another mode would be to just test (pre) release to see if we have any regressions in comparison to previous release. For sure there are ways of optimizing this and finding a good middle ground. :) Heck, maybe even our private machines are ok?

Maybe we have a spare machine in the office?

I'd be sad if we'd need to poke anyone in the office to turn it on/off, restart etc. 😅

I guess we could setup a mock localhost OTEL collector that would just accept and store whatever requests come in from the example application and then assert for certain data being in those requests. It is somewhat effort intensive to setup and won't speed up the tests that much - example application startup takes way longer than starting docker-compose. But that would be a more lightweight solution long term.

are we sure that it's not enough to use AgentTestRunner/LibraryTestRunner for such tests?

That is a completely different setup then, I would argue is is not an E2E test then.

Overall it is nasty that we have to package and run the example projects as in production to be sure that Mesmer works. If general Java/Scala development would require that, nobody would work with both of these languages 😅 Maybe Muzzle can solve that, but E2E tests like these are the best assurance until then.


Example of failed OCR

Hey, nice project. This is really cool.
Here's a screenshot that trips up the OCR.

I think it's getting confused with the UI in the top right.

Clicking the OCR button gives this error.

Also, setting the window to 1440x900 as recommended, it fails to generate the grid when clicking Show Grid or Calculate. Here's the exported image.

.

Hmm yeah this is a pretty old project of mine, and the automatic OCR doesn't always work hat great.
After toying a bit around with your two pictures I get this (you can import them again via "Load from file"):
Picture1:
You can click "Calculate" to auto-determine the Grid and then open the "HexGrid Parameter" and adjust the "BarTopRight" parameter (330 x 300 should work). But unfortunaly it seems the actual OCR still fails due to a bad grid alignment, you could try manually adjusting the Grid Parameter, but thats rather tiresome...
It's also the reason why I recommend 1440x900, all the default parameter just works best in that resolution
Picture2:
If you press "Show Binary Pattern" you can see that HS recognizes too few cells to determine the grid (aka only 2).
Under "Binary Pattern Parameter" you can enable "Use Active Cells in Pattern" and "Use inactive Cells in pattern", then Hs has enough information to find the grid and OCR etc also works (I then managed to find a single black cell for the next Solve step)
Regards
~ Mike


[feature] chart selection events

Requirement
It would be great if when I clicked a attribute on a chart - that it would expose the ability for me to listen to that event and see the data associated.
For example:
<SandDanceReact
   onChartSelection={(event, data) => {
        // data = single or group point clicked
   }}
/>

Nevermind - found this in viewOptions -
<SandDanceReact
          data={data}
          viewerOptions={{
            onSelectionChanged: (selection: any) => {
              debugger;
            }
 />


Update free-programming-books-tr.md

r4ds cevirisi eklendi
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

good addition, but be sure to check the free-programming-books-lint output for linter errors. Alphabetical order and spacing are the most common problems.


Total-order planner

Submitting code for planner.

This looks really nice -- great work!

There are too many conflicts for me to resolve -- can you have a look?

One of the main issues is that the PlanningKB items are immutable (and therefore hashable and searchable) and the FOLKB items from logic.py aren't. I'll need some time to see if I can make these two object models work, and probably a decision from you as to which way to go with the implementation.

Hey @bcorfman, I know that Expr objects have a __hash__ method. I think that FOLKB should only be using these; do you know where they are not used?

Hi Dr. Norvig - I use the existing A* algorithm to solve the example planning problems. Recall that the set of explored items is maintained during the search to keep track of repeated states (line 270 in the current search.py). Any items in this set must be hashable and unique. I use my PlanningKB as the state variable in the search Node, and it's hashable because the PlanningKB only uses frozenset variables instead of regular mutable sets.  The FolKB database doesn't work inside the Node.state because it's designed (because of its tell and ask methods) to be mutable -- that means its clauses variable is a mutable list, and its state can't be hashed.

I got it. What about if you use tuple(kb.clauses) for the state? You could then put the clauses back into a KB when you need to.

Yep, a tuple should work for the FolKB clauses. (I remember using tuples with the Node setup for one of the Berkeley Pac-Man projects.) I guess my question is whether you want to a) just make the FolKB usable for the search algorithms, 2) combine the existing logic.py and my new planning.py code together, or 3) just pass the FolKB clause list into the PlanningKB init and then use the PlanningKB to conduct the search. I think #3 is the easiest -- although there'd be two KBs for different purposes, my PlanningKB and Action classes use frozenset methods to quickly perform goal and precondition checks. I can make changes based on what you think is the best long-term approach.

Closing for now. I'll open another pull request shortly once I get the remaining conflicts resolved.

I merged my planning code with the current version that's in the AIMA repo. It's not the cleanest  because it was hard for me to tell the state of the code at the moment -- there seems to be a lot of design ideas in progress, and I was hesitant to start melding too much without some evaluation on my own code first.
I built a basic PDDL parser with lots of tests/examples in the pddl_files subdirectory in order to give my total order planner a thorough shakedown before submitting it. The examples are run by executing the test_planning_solutions function inside the planning module.  Most of the tests are just translations of the ones that were already inside the existing planning code, but there are a couple additions too. The parser could be better about more specific error reporting when something goes wrong, but it does work solidly otherwise.
Dr. Norvig, I did try a few of your suggestions above to try merging the FolKB class and my PlanningKB class, but these ideas quickly got snarled because my PlanningKB, PlanningProblem and PlanningAction classes are very interdependent and rely on Python's set classes. Modifying the existing AIMA Problem, Node or Action code would have big changes that would affect other modules, so I didn't want to do that without feedback.
Please let me know if you want to proceed any further.

I added a couple of classmethods to my PlanningProblem and PlanningAction classes. These alternative constructors (PlanningProblem.from_PDDL_object and PlanningAction.from_action) take existing PDDL and Action objects as parameters. If you decide to use my PDDL parser too, I might rename the PDDL class to something more appropriate -- there's starting to be a lot of things named "PDDL" in the code, and it could create confusion.

I think this looks pretty good, but there's a lot here stretching over a long time. Can you, @bcorfman , check in with @ad71 and perhaps @samagra14 over in aima-java, who is also working on planning now, and together come to a consensus?

After I checked in, I found a bug that was exposed by one of my test cases, and I realized that the existing Action and PDDL classes were doing some things I should incorporate to fix it. I will make the changes over the next couple days so we're more in sync, and try to come to consensus on the remainder!

@bcorfman please also have a look at #927 and tell me if you want me to change something. My total order planner is a misnomer and I'll change it in the next commit but apart from that, the PR heavily relies on the current Action and PDDL classes. It might be a problem if those classes are changed. Do inform me if you really want to though, we can find a way around it. Thanks!

@ad71 I will take a look at #927 and get my bearings ... the basic issue for using any of the search algorithms (A*) for the current KBs is that they must be frozen types (i.e., tuples, frozensets, etc.) to be hashable when stored in the frontier. If we get away from a search representation for the planners (i.e., like you did with Graphplan, correct?), we can stay with the tell() and retract() methods that modify the KB. But otherwise, it seems like we'd be stuck with two different KB representations: frozen and searchable, or mutable and unsearchable. We could move between them, but I don't think we can combine the KB types together in my opinion (at least without an unfortunate breaking of the Python object model, e.g., utils.hashabledict). I always could be missing something though.

@bcorfman we faced similar problems trying to make NQueensProblem and EightPuzzle work with search algorithms, so we decided to let those problems return tuples as states, ie, they didn't use KBs. When we wanted to internally change the state, we converted it to a list, carried out the changes and converted it back. It seems like a lot of work and a lot of duplicated code, but this can be done for KBs as well, though the code would be far from elegant. As of now, I can't think of a better solution...

Sorry I'm so behind -- I fixed the bug I found with my TO planner. I will take a look at #927 over the next couple days and see if we can wrap this up ASAP.

@ad71  I implemented what Dr. @norvig suggested for PlanningAction and PlanningKB ... both of their init methods take strings or Exprs now for a cleaner API.
I agree with you on translating between representations ... your observation is a good reason why Python has both lists and tuples and sets and frozensets, and they can easily be moved between. Do you think we should try the classmethod approach for moving between the types, or use some other way like a standalone function?
Probably my PlanningProblem should be renamed PlanningSearchProblem or something else to distinguish it from the mutable (PDDL) representations. Same for PlanningAction, so it isn't confused with the existing Action class ... I suggest STRIPSAction because of its negative and positive preconditions and add and remove effects that are implemented with set operations. I'm open to improvements.
As I mentioned previously, strongly think we should rename the PDDL class though (since it has little to do with the PDDL language) ... could we rename that to PlanningProblem instead?

@bcorfman I agree that PDDL is a misleading name. I'll change this in the next update. PlanningSearchProblem and STRIPSAction are good names for your classes. I think you can go ahead with it.
As for translation between representations, I'm fine with anything that works, Dr. @norvig can give you a better suggestion.

OK, I'll change the code to reflect the new names. Should I add a draft writeup on the new code in the Jupyter notebook, our hold off for now?
On June 15, 2018 3:04:58 PM EDT, Aman Deep Singh<EMAIL_ADDRESS>wrote:

@bcorfman I agree that PDDL is a misleading name. I'll change this in
the next update. PlanningSearchProblem and STRIPSAction are good
names for your classes. I think you can go ahead with it.
As for translation between representations, I'm fine with anything that
works, Dr. @norvig can give you a better suggestion.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/aimacode/aima-python/pull/645#issuecomment-397714774

Editing notebooks will result in merge conflicts with the other PR. You can add the write-ups later.
If you think you won't have time later on, you can go ahead and add it now, I'll take care of merge conflicts when/if they arise.

No problem; I can wait.

During the interim, I'll work on some unit tests to add to test_planning.py as well.


Advanced Summary

[x] Summary by date
[ ] Tests for that
[x] Summary by month
[ ] Tests for that
[ ] Summary for categories
[ ] Tests for that
[ ] Link up with the computer time stamp
[ ] UI to display summary for this month by default

Parsertests:

[ ] SummaryByDateParser
[ ] SummaryByMonthParser
[ ] SummaryParser
[ ] MonthTest

Changing parserUtil tests

[ ] modify date related tests
[ ] modify money related tests
[ ] add month related tests

SummaryList tests

[ ] SummaryByMonthList
[ ] SummaryByDateList


Support manifest list

Hello,
First, thanks for your work on this crate, it is very helpful!
I'm interested in the manifest list feature. Currently, I work on a crate to provide the ability to pull OCI images for a school project. So I need to be able to pull for example alpine or ubuntu images from docker.io/library.
For example, when I use the pull_manifest_and_config method of your Client, I have this error :
unsupported media type: application/vnd.docker.distribution.manifest.list.v2+json
I checked your code and I see that the crates do not support the manifest list feature. Is this something under consideration? I see there is a TODO in your code, but no more information about future implementation. If not, did you know if there is a workaround to be able to pull those images?
Thank you!
Thomas

Yes, I've looked #26, but I'm not sure it resolves my use case.  #26 is focused on the ability to push manifest lists, and not on pulling. What I'm interested in is the ability to pull images such as docker.io/library/alpine or docker.io/library/ubuntu.
To give you an idea, currently, with this piece of code :
pub async fn pull_manifest(&mut self) -> Result<(OciManifest, String, String)> {
  self.client
      .pull_manifest_and_config(&self.reference, &self.auth)
      .await
      .map_err(|e| Error::PullManifest(e.to_string()))?
}

When my reference is parsed from docker.io/library/ubuntu, I have the following error :
unsupported media type: application/vnd.docker.distribution.manifest.list.v2+json
So that's ok, as I said in my first comment.
But it is strange, because if I use docker.io/amd64/ubuntu, it works great.
I'm not sure to understand the difference between those two OCI references, and how the process has to be different for each.


Finish compile time evaluation (without instantiations)

This will close #72. I have unary ops and binary ops working but I need to finish with

[x] error, match_kind members
[x] enum and serializable enum members
[x] universal sets "default", "_"
[x] hs.size for header stacks hs
[x] e.minSizeInBits() / e.minSizeInBytes() for headers
[x] bitslices x[hi:lo]

@jnfoster Can you take a look at what I did to the test issue1717.p4 here? It looks to me like p4c is doing overloading of member lookups based on whether something is a function or not. I just modified the test to avoid it.

When p4c resolves a member expression, it does something special for minSizeinBits, isValid, etc.
https://github.com/p4lang/p4c/blob/master/frontends/p4/typeChecking/typeChecker.cpp#L2625
So I guess we could do the same.

Fixed but pushed to the wrong branch. Oops


Downloading wintun dll for release sometimes fails

I was testing the release process for the Windows installer on a fork, since I noticed that the msi file is missing from the v0.5.4 release on this repo.
Something I noticed is that the download of the wintun zip file fails sometimes:

This happened twice during my testing. I wonder if the server for the wintun project isn't so reliable, or if there's something else going on.
Either way, maybe it's worth just checking the dll file into this repo so we can be sure the release process is reliable.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

I saw this a couple more times in my testing today. Thoughts @LeeSmet or @maximevanhees?

I saw this a couple more times in my testing today. Thoughts @LeeSmet or @maximevanhees?

I had the same experience today whilst testing on my fork. It seems to be unreliable but I have no idea why.

Another approach we could consider is adding some retry and timeout parameters to the curl invocation. Such as:
--connect-timeout 60
--retry 5

For five tries with a one minute timeout each.

While this is an annoying issue, I don't really think we should spend time trying to work around this on our end at the moment. A failed worfklow can be rerun later by manual intervention, which should be sufficient here since it's a very infrequent worklflow, and since it's an  external site/service we don't know what is actually happening over there.

That's fine by me.


add ios 9.1 Shortcut Icon

Awesome! I will update the docs and see how pre-iOS9.1 devices deal with these new icons.

Just released 1.2.0 which includes your changes :beers:


Confusion about the $ sign in the config file

https://github.com/microsoft/SoftTeacher/blob/bef9a256e5c920723280146fc66b82629b3ee9d4/configs/soft_teacher/soft_teacher_faster_rcnn_r50_caffe_fpn_coco_180k.py#L28
Is it the Config class that implements calling variables by using $ in .py, as in shell script?

see the vars.py...


chore: remove tsd

TSD has weird regressions with vue-next 3.0.9, maybe due to TS 4.2.
Instead of figthing it, let's adopt what the other Vue projects did and replace TSD with a plain tsc check.
See https://github.com/vuejs/vue-next/commit/97dedebd8097116a16209664a1ca38392b964da3 for example for a similar commit on vue-next

This should unblock #508


Warning alerts regarding missing libraries (redfish, paramiko) even though they're both installed

Hi everyone.
Trying to run and use the ilo-ansible-collection roles, in particular the ones related with ilo_snmp (create_snmp_alert_destinations, delete_snmp_alert_destinations, get_snmp_alert_destinations) in an execution environment prepared specifically at the Ansible Automation Platform with the respective requirements.yml (paramiko v.2.8.1, certifi v2024.2.2) and requirements.txt (python-ilo-rest-library v<IP_ADDRESS>) as well as hpe.ilo v1.0.35 and community.general  v8.4.0).
The warning alerts are raised at lines 135, 136 and 138,139 of "ilo_oem_utils.py".
Could you please pinpoint what needs to be checked on my side or if something needs to be updated at the code so that it recognises that the missing elements are part of the execution environment, which anyway I already confirmed by checking the content of the created pod using python -m pip list ?
Thanks

@MoSXaR , Please let us know if it is still issue.  Also, please escalate to HPE support if needed.


Spec316

got rid of ecmfeatures since they are not supported as of versino 1.0.0

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Resolves #43

We should include a sample file to lint, like bootstrap.js
https://github.com/twbs/bootstrap/blob/v3.3.6/dist/js/bootstrap.js

closing this in favor of #48 as new work was done there


no forum identified on https://github.com/ARMmbed/mbed-cli

There is no forum identified on main git hub page for newbies to ask questions unworthy of being "an issue."

Meaning the main git hub page for mbed-cli.

@jahess I believe the developer site (http://developer.mbed.org) would be what you're looking for, and that's listed at the top of the repo. But would you like to see this added to the README?

@jahess Bump

Closing from inactivity


Remove dot at the end of a PR title before adding the "(GH-#)." suffix

Some contributors write their PR titles with a dot at the end. It's fine, but since it's not done consistently, and it would be a bit overkill for us to edit all PR titles to remove trailing dots, I would suggest doing it as a post-processing step.

We can just remove the dot at the end before appending the "(GH-#)." suffix, unless it's "..." which we should likely keep as is.
Not sure about ".." which is something folks like reduz tend to use, we can assume this won't really happen and would be fixed by editing the PR itself.

I can't recall PRs ending with .. or ..., why would that be the case? Should probably strip that completely. If it's from a commit message that is too long, then we should probably edit it ahead of generating the log.

 but well :P
Realistically, no, it's unlikely to be a common occurrence and stripping all dots probably won't harm much if such dramatic ellipsis ever happens.


Improve German locale

I've added currently missing keys from the English locale into the German one as well as making some small changes to the existing translations.
Mainly:
Protokolldateien => Logdateien
(both are correct, but the second one is shorter)
Administrator => Admin
(both are correct, the second one is shorter so it's less likely to get cut off when it comes after a long group name)
Über => About
(To me, 'About-Sektion' seems like a normal thing to call it in German while just 'Über' feels kinda weird as a button label.)
Notes:
Records (as in Record ID or User Records) are translated as 'Aufzeichnungen' which I base on a single occurrence in the actual Neos translations. I am not sure how familiar German Neos users would be with the term but it should be fine.

Thanks


Assembly-Output name

When I mouse over the Output name box, it gives the wrong instructions, telling me to choose something to upload

Fixed in commit


BTS translate bugfixes + added translations

Translation: bugfix in following widgets:

OptionsRadio (BTS)
OptionsCheck (BTS)

Added item and title translations for german in schemaTestBts

merged


saveAs: check for extended mimetype

fixes #731

@muaz-khan I'd be grateful if you could review and release this in a new recordrtc version 😃


link/export to quarto schema

https://quarto.org/docs/journals/authors.html

Yes, now this is documented there is some work to do. Either exporting to Quarto schema, or for quarto to read JAMS spec maybe.
I can help with that.

Also time to see https://www.ncbi.nlm.nih.gov/books/NBK579698/


Fix shadow release

Description
This PR fixes a bug introduced with #161. As a result, after #161 master can not build releases any longer.
The problem was triggered by this line:
https://github.com/MeteoSwiss-APN/spack-mch/blob/4ae467939db6f9c15e75b72690728458dfad0527/packages/cosmo/package.py#L43
That is setting a dependency of the like
depends_on('cosmo-dycore@aversion', when='@aversion', type='build')

That goal was to fix within  spack what version of dycore can and should be build depending on the version of cosmo. This is a tight requirement, since in principle a version of the dycore can be compatible with multiple versions of cosmo, as far as there are no changes in the dycore and in particular in the API.
However, without it, any version of cosmo will be built against the latest of the dycore, which will lead users to error prone compilations unless always specify in the spec the version of the dycore required:
spack install<EMAIL_ADDRESS><EMAIL_ADDRESS>...

However the solution employing the depends_on is problematic...
If there are releases that as a string is a subset of another, spack fails to resolve the spec.
This happened when adding the new releases of c2sm, which included all the releases of cosmo-org.
For example: 5.08.mch1.0.p1 and 5.08 will clash, and even if there is no reason why it should not work, spack fails to concretize the spec.
Therefore the proposal if this PR is to remove that mechanism.
We set of the releases of mch apn and c2sm (avoiding clashes by filtering the apn ones with the substring 'mch') but we dont specify the version of the dycore cosmo will depend on.
Notice, this is a change of paradigm proposed here:

Spack set conflicts and dependencies, however it is not a release manager. It does not specify for each specific release the releases of the dependencies that should be used.
Like that, we will need a small external spec builder, which will build the spec of spack for each release of cosmo for the user, in order to avoid the error prone situation when the user needs to set by hand all versions of dependencies.

I am working on a solution in that direction, but to be discussed first, before we continue with this PR
@kosterried @jonasjucker @lxavier

I looked quite a bit into this and have some strong opinions. But I think it's best to discuss this in a spack meeting.

@BenWeber42 we decided to go one with part of the solution yaml + other feature from @cosunae PR (see meeting notes in the wiki). From discusison with Giacomo it seems your main concerns was related to the spack yaml format which we decided to use.
Maybe best is that you check with Carlos if he will implement anything before the next spack meeting otherwise we can call for short meeting before.

The thing is, I think auto discovery (#199 ) is a mistake altogether (at least for cosmo and cosmo-dycore, most likely also for the others).
In the spack packages we should have only official releases. Official releases almost never occur very frequently. It's mostly fine having to create a new PR in spack-mch if there's a new release.
The versions we get additionally with auto discovery can be seen mostly as develop versions in my opinion. E.g., for the mch releases we have 5.07.mch1.0.p0 - 5.07.mch1.0.p12. I don't see how they should be considered official releases. I think they're more develop releases for our operations.
Develop versions shouldn't exist in the spack package. Only official versions should exist there. If someone wants to build a develop version, the correct way is to git clone that tag and then spack dev-build (or devbuildcosmo in this case).
If the release procedure depends on these develop versions, then we should adjust the release procedure to use dev-build/cosmodevbuild.
If doing a git clone + spack dev-build is considered too cumbersome, we can add a custom spack git-dev-build <git ref spec> <spack spec> command which unifies both commands. So that we can keep develop versions outside of the spack packages.
Not only is this auto discovery completely against the way spack is meant to be used (imho), but it also slows down everything that requires the package (spack spec/install etc), since we're fetching all tags over the network each time.
Once we only have official releases in the cosmo and cosmo-dycore packages, we can easily enforce that the versions match up<EMAIL_ADDRESS><EMAIL_ADDRESS>etc. The list of official releases (+ supported by the spack package) isn't that big, so that we can easily maintain this. Then the users can easily spack install cosmo@<official release> and everything works out of the box. I believe this should cover a lot of users (probably also c2sm users? @jonasjucker ) already.
Whereas for develop versions, you just do it the spack way. Additionally, this is no different than with the old bash scripts.  Which with spack is simply git clone + spack <dev-build/cosmodevbuild>.
The way I see it, is that this would be strictly an improvement and we'd finally use spack the way it's meant to be, instead of trying to force spack to do things it was never meant to do.

I think most C2SM users will either build the master or clone it and use dev-build/cosmodevbuild.
One problem I see with your solution is, that for a change of dependencies you need to adapt in COSMO and Spack, otherwise you only need to adapt COSMO.
This additional step could be forgotten...
The problem is, correct me if I am wrong, we have 3 different repos in one Spack package, therefore we need to specify version for all 3 -> the package.py will look little bit crowded then with all the depend_on.

I dont think that spack should determine what's your software release cycle. In an agile methodology one could be releasing as often as every two weeks. And we (MeteoSwiss) have had in the past cases where we needed to deploy patches quite often for testing. We need the capability to deploy any release with our CI, irrespective if the release is deployed for production (I guess that is what you mean "official") or for a testbed of OSM. And we need that capability without the manual intervention of having to create and merge a PR adding a version.
Of course that we could use the dev-build mode for everything. But we would need to use that within our CI for all releases that we need to build for OSM, therefore we would not use spack versions at all. And devbuild is not a building spack mode, we created it. So I wonder why is a dev-build more the right way of using spack than using spack versions (that is a builtin functionality) for building any git tag?
Also it eliminates all the strong points of spack knowing about the version within spack. You can not any spack syntax that depends on the version, like define conflicts, patches... because spack does not know anything about what contains a dev-build.
Finally, spack itself has an autodiscovery of releases, just didnt work with private repos.
See spack.url
https://spack.readthedocs.io/en/latest/developer_guide.html
So I dont see why being able to build any git tag that is accessible is not the right way for spack.

In any case this PR was a test attempt and by now obsolete. We are solving this with giacomo's PR that is almost ready, so I will close this to avoid confusion. We can move the discussion there.


feature(plugins/okta): make api token and organization field optional

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area plugins

What this PR does / why we need it:
We are avoiding api_token and organization field from being required
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: SKosier
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @SKosier. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, SKosier
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4cfb13301d53f65636c3fb245998675488805e84


Revert #420 for aws

Because of reasons yet unknown to me, rclone recursive deletion code introduced with #420 is flaky:
https://github.com/iterative/terraform-provider-iterative/blob/d5c4d1e19a0348dd7e779ae020588109c5cca7c3/task/common/machine/storage.go#L126-L151
This pull request restores the old cloud–specific code that goes through all the objects and deletes them as part of the destroy operation.
Closes #452.

Merging this opens a follow–up technical debt issue to fix rclone flakiness for the common Delete() operation and revert this.

https://github.com/iterative/terraform-provider-iterative/issues/459

I've opened an I2 (irking issue) to investigate why rclone bucket emptying finishes way after the function has returned.


Vulnerability roundup 70: mupdf-1.14.0: 1 advisory

search, files

[ ] CVE-2019-7321 (nixos-unstable, nixos-19.03)

Scanned versions: nixos-unstable: a1dd419c1ff; nixos-19.03: 1601f559e89. May contain false positives.

See also #54807 and #57163.

Contacted mupdf upstream - there is a typo in the CVE. It affects version 1.15. We are not affected.
#mupdf @ irc.freenode.org
10:24:02 <@ator> marek: I suspec a typo on their part.

Commit https://github.com/ArtifexSoftware/mupdf/commit/7d52765c5b8a5c76e459d148cd94dbaf51e562ec which introduces this bug includes a 1.15 tag.

false positive


Writing dataset to GCS fails with OSError

Hello there,
I was trying the newly added GCS support, and I am encountering this error when trying to write a dataset via the python API:
[...]
File "YYY/lib/python3.9/site-packages/lance/dataset.py", line 654, in write_dataset
    _write_dataset(reader, uri, params)
OSError: LanceError(I/O): Generic GCS error: Error performing copy request 3d217d1b-1a94-436f-8726-0d955df92fba.lance/_versions/1.manifest: response error "{
  "error": {
    "code": 400,
    "message": "Rewriting objects created via Multipart Upload is not implemented yet. As a workaround, you can use compose to overwrite the object (by specifying XXX/3d217d1b-1a94-436f-8726-0d955df92fba.lance/_versions/1.manifest as both the source and output of compose) prior to rewrite.",
    "errors": [
      {
        "message": "Rewriting objects created via Multipart Upload is not implemented yet. As a workaround, you can use compose to overwrite the object (by specifying XXX/3d217d1b-1a94-436f-8726-0d955df92fba.lance/_versions/1.manifest as both the source and output of compose) prior to rewrite.",
        "domain": "global",
        "reason": "invalid"
      }
    ]
  }
}

Any idea of what is going on?

Thanks @gsilvestrin !
Let me know if you think it is an object_store related issue. I’ll be happy to fill a bug report there.

awesome @gsilvestrin , thanks so much! I'll take it for a spin and let you know how it goes!

Thank you @gsilvestrin , I can confirm this solved the problem!


Update xeus-python to 0.16

@DerThorsten are we safe with this one? Has all the pyjs -> pyjs_core imports been updated correctly?

@DerThorsten are we safe with this one? Has all the pyjs -> pyjs_core imports been updated correctly?

the pyjs unit test pass by importing pyjs, pyjs itself then imports pyjs_core.
So I believe we should be save...(famous last words)

Actually, I am very confident as I already have a deployment with the changes at https://emscripten-forge.github.io/pyjs/try_from_py/

Oups. I forgot to reset the build number. I guess this is not so harmful though?

no not a problem


Deny forward steps to be used inside backward block.

Deny using I expressions inside () without ~ operator.

Superseded by #627


sign GitHub commits using PGP #75

Having an issue with getting the key verified when commiting

need to debug a little further

https://platform.github.community/t/signing-app-commits/3420/17?u=dabutvin

The helpful @mastahyeti was able to trace the verification error to https://github.com/keybase/go-crypto/blob/8bab6ce2ea76875dcf28c287110f9cdf17fee30c/openpgp/packet/public_key.go#L650

it seems that there is some difference between how Go’s openpgp library is validating the signature and how GnuPG is.
A good next step might be to try to reproduce this in a more isolated way and open an issue with the openpgp library. Better yet would be to write a failing test for the library. It is worth noting that the github.com/keybase/go-crypto Go package is a fork of the golang.org/x/crypto/openpgp package, so it would be worth testing against the upstream version as well. This is the first time I’ve seen the BouncyCastle PGP library being used, so I’m not terribly surprised so see that it doesn’t play well with Go’s implementation.

Got it working!


Fix unwanted schema validation

Only insert schema validation if expected response is a JSON Content-Type, linked to #392

@nicklloyd How can I get past the Lint error of using  @ts-ignore in the unit tests?


[UI] Cluster Templates - Sharing issue

Version: master-head (7/23/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a cluster template, share it to a user, give them member access.
Log in as that user. Try to clone a revision.

 We are missing everything under "Cluster Options".

Closing as duplicate of https://github.com/rancher/rancher/issues/21717


[patch] Pull liftTimeout to http hook defaults

This resolves a TODO comment which says to pull the liftTimeout defaulting in the startServer() function to the hooks definition defaults.

@eashaw just checking if this PR needs any further work to be merged :)


Suggestion - changes as "object" instead of writing on images directly

It would be nice that the changes (Freetext, obfuscate, free drawing) be saved as an object, which is rendered on publish instead of directly.
This would allow to edit minor details (typo, font, additional information) after they have been placed at any point.

Would also be nice if these objects could span frames - so with a text box, I could say "render on frames 7-23"....

It's a great idea that I'd very much to see, but I do wonder if this would cause some kind of performance hit.

I started working on this. Basically, I'll have to rewrite the entire editor and the recorders to support this feature.
The screen recorders are already in shape for this change (the webcam recorder and board recorder are not ready).
I also started working on the new editor, I'm laying the foundation for all new features.
@lansalot Right now, you can select multiple frames when applying some changes, the same would happen with a new editor.

What is the progress on this? Has there been any work or design already done regarding this feature? I'm considering taking a stab at it.

Progress I would say is around 45%.
This was implemented in v3 (a complete rewrite of the project).
The renderer/previewer is already handling multiple layers, changes made to layers trigger rendering nicely as fast.


[bug] event.listen not allowed on window main, webview main, allowed windows: , allowed webviews: , referenced by ~

Describe the bug
There is a "main" window and I created an additional "google" webviewWindow. When the "google" window was loaded, the "emit_to" sent an event to the "main" window. However, the "main" window received the following error and did not receive the event.
What additional settings should I apply?
I recently upgraded from alpha version to beta, and I checked the document, but I'm not sure.

let _ = WebviewWindowBuilder::new(&_app_handle, "google", WebviewUrl::External(_url.parse().unwrap()))
            .parent(&m_webview).unwrap()
            .decorations(true)
            .resizable(true)
            .initialization_script(&_script)
            .on_page_load(move |window, payload| {
                match payload.event() {
                    PageLoadEvent::Started => {}
                    PageLoadEvent::Finished => {
                        window.get_webview_window("main").unwrap().emit_to(EventTarget::labeled("main"), "onready", payload.url()).unwrap();
                    }
                }
            })
            .build()
            .unwrap();

{
  "productName": "test",
  "version": "0.0.0",
  "identifier": "com.tauri.dev",
  "build": {
    "beforeDevCommand": "yarn dev",
    "devUrl": "http://localhost:1420",
    "beforeBuildCommand": "yarn build",
    "frontendDist": "../dist"
  },
  "app": {
    "withGlobalTauri": true,
    "windows": [
      {
        "title": "main",
        "label": "main",
        "width": 1200,
        "height": 800,
        "url": "http://localhost:3000"
      }
    ],
    "security": {
      "csp": null
    }
  },
  "bundle": {
    "active": true,
    "targets": "all",
    "icon": [
      "icons/32x32.png",
      "icons/128x128.png",
<EMAIL_ADDRESS>      "icons/icon.icns",
      "icons/icon.ico"
    ]
  }
}

{
  "$schema": "../schemas/desktop-schema.json",
  "identifier": "default",
  "description": "Capability for the main window",
  "windows": ["main"],
  "permissions": [
    "path:default",
    "event:default",
    "window:default",
    "app:default",
    "image:default",
    "resources:default",
    "menu:default",
    "tray:default",
    "shell:allow-open",
    "event:allow-listen",
    "event:allow-emit-to"
  ]
}

Reproduction
No response
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Mac OS 13.5.2 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.16.0
    - pnpm: 8.6.10
    - yarn: 1.22.21
    - npm: 9.5.1

[-] Packages
    - tauri [RUST]: 2.0.0-beta.12
    - tauri-build [RUST]: 2.0.0-beta.10
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - tauri-cli [RUST]: 2.0.0-alpha.18
    - @tauri-apps/api [NPM]: 2.0.0-beta.6
    - @tauri-apps/cli [NPM]: 2.0.0-beta.10

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

why did you close this issue? I have the same.

@wanghanzhen
I solved it by adding these settings.
in /src-tauri/capabilities/default.json
"remote": {
  "urls": ["https://**"]
}


can't see active checkbox in this extension

hello! Your
extension is pretty good!But I can't see active checkbox in "Dynamic Thresholding" in the latest version.Versions in April have no problem.

I opened a PR in that Extension, which will fix this Issue once it is merged~

Got it！Thanks


Cron Jobs Not Terminating

Currently, when running the cron jobs locally using pnpm sls:local-invoke in apps/server, the cron job does not terminate as it should.

Closed by #407


feat: 404 report for customers

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

v1.18.0
GitHub release

Your semantic-release bot :package::rocket:


Bump pipeline-tools version

Related issue: https://github.com/rancher/rancher/issues/17511
https://github.com/rancher/rancher/issues/17570

LGTM


Goal-based features have stopped working with YNAB update

Defective ToolKit Feature Name:
Expected Behavior
Goal indicator and blue-colored available amount should show on categories with goals
Actual Behavior
Indicators are missing and underfunded goal color is yellow.
Steps to Reproduce the Behavior

Activate features
Open YNAB

Export of Toolkit Settings (Bottom Left of Settings Page)
[{"key":"accountTransactionSearch","value":true},{"key":"accountsDisplayDensity","value":"2"},{"key":"accountsEmphasizedOutflows","value":false},{"key":"accountsSelectedTotal","value":true},{"key":"accountsStripedRows","value":false},{"key":"activityTransactionLink","value":true},{"key":"budgetBalanceToZero","value":true},{"key":"budgetProgressBars","value":"0"},{"key":"budgetRowsHeight","value":"2"},{"key":"categoryActivityPopupWidth","value":"1"},{"key":"changeEnterBehavior","value":false},{"key":"checkCreditBalances","value":false},{"key":"collapseExpandBudgetGroups","value":true},{"key":"collapseSideMenu","value":true},{"key":"colourBlindMode","value":false},{"key":"currentMonthIndicator","value":false},{"key":"daysOfBuffering","value":true},{"key":"daysOfBufferingHistoryLookup","value":"3"},{"key":"editButtonPosition","value":"0"},{"key":"enableRetroCalculator","value":true},{"key":"enlargeCategoriesDropdown","value":true},{"key":"goalIndicator","value":true},{"key":"goalIndicatorWarningColor","value":true},{"key":"googleFontsSelector","value":"0"},{"key":"hideAOM","value":false},{"key":"highlightNegativesNegative","value":false},{"key":"importNotification","value":true},{"key":"incomeFromLastMonth","value":"0"},{"key":"l10n","value":"0"},{"key":"largerClickableIcons","value":false},{"key":"monthlyNotesPopupWidth","value":"1"},{"key":"pacing","value":"0"},{"key":"printingImprovements","value":true},{"key":"privacyMode","value":"2"},{"key":"reconciledTextColor","value":"0"},{"key":"removePositiveHighlight","value":false},{"key":"removeZeroCategories","value":false},{"key":"reports","value":true},{"key":"resizeInspector","value":false},{"key":"rightClickToEdit","value":true},{"key":"runningBalance","value":true},{"key":"seamlessBudgetHeader","value":false},{"key":"splitKeyboardShortcut","value":false},{"key":"splitTransactionAutoAdjust","value":true},{"key":"squareNegativeMode","value":false},{"key":"swapClearedFlagged","value":false},{"key":"toBeBudgetedWarning","value":false},{"key":"toggleSplits","value":false},{"key":"toggleTransactionFilters","value":"2"},{"key":"warnOnQuickBudget","value":true}]
System Settings
ToolKit Version: 0.5.3
Operating System (Mac/Windows/Etc): Windows 7
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 52.0.2743.116 m
Other Extensions: None for YNAB

@pchristopherson Thanks for the report!
I've got a fix ready to go in and this will be resolved on our next release!

This is now released as part of v0.6.0. Does it work for you on the latest version?

Works great...thank you!
On Thu, Aug 18, 2016 at 8:21 AM, Kevin Brown<EMAIL_ADDRESS>wrote:

This is now released as part of v0.6.0. Does it work for you on the latest
version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/474#issuecomment-240706656,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATEdxsOBcvTqZd1gX2YsWVHJAaWcm8Cpks5qhE5FgaJpZM4JltvW
.

Brilliant, thanks! I'll go ahead and close this issue.


update tutorials list

Creating aws-singletier.adoc and aws-multitier.adoc, and updating aws.adoc

Trying to add/update aws-singletier.adoc and aws-multitier.adoc. The conflicting file aws-single-ami.doc should be deleted.

Trying to add/update aws-singletier.adoc and aws-multitier.adoc. The conflicting file aws-single-ami.doc should be deleted.


JSX transformation issue

I was playing around with Solid today, and ran into an issue with the given JSX:
import { render } from "solid-js/dom";

function Link({
  children,
  href,
  className,
}) {
  return (

      {children}

  );
}

function Component() {
  return (

      <Link>new</Link>
      {" | "}
      <Link>comments</Link>
      {" | "}
      <Link>show</Link>
      {" | "}
      <Link>ask</Link>
      {" | "}
      <Link>jobs</Link>
      {" | "}
      <Link>submit</Link>

  );
}

render(() => <Component />, root);

The error is Uncaught TypeError: Cannot read property 'nextSibling' of null.
I assume it's because your template doesn't take into consideration it needs holes to insert the dynamic components between. One possible solution might be to add comment nodes into the HTML so that you can correctly find the sibling and replace the comment with the new DOM node.

Thanks for reporting.
I do use the method you mentioned. I just got very aggressive at optimizing those cases out over the years. It's possible I over-optimized and missed a case. I will look into this.

Keeping this one open the logic is actually too simple as well. I will need to do a bit more work here.

Ok fixed this one more robustly now with Solid v0.18.7. Now it can detect multiple expressions between 2 strings properly. Don't hesitate to report any other issues you fine. Thanks.


Properly calculate CALayer's ContentsCenter by translating them to co…

…rresponding Xaml Image NineGrid values.

This change is

:shipit:


Module subgenerator

Great work! thanks for this. We could explore AST to automatically add the reducer later.


Fixes config singleton usage

When multiple Indexiatech addons are included in a single app, they check if Em.Config exists in the initializers and if not create it. However, if Em.Config does exist they continue to use the imported Config variable. This variable is the constructor for the config object, not the instance of it created and added to Ember. Errors are thrown by the 2nd, 3rd... etc plugin trying to initialize their configurations.
The solution is to use initialize if it doesn't exist Em.Config and use it exclusively for setting configs.

+1 ... does work... (thanks @pzuraq!)

So merge it please.

Sorry for the delay, This is fixed in the repo, I a bit changed it because Em.config is too risky regarding collisions, changed to Em.IdxConfig but it should work smoothly now.


Start guidelines for editors

Should include the following:

Tag versions of packages at publication for reproducibility purposes

We use the template issue available here
https://github.com/computorg/published-paper-tsne/issues/5


Add human-readable-time package

How is this any better than the existing dateformat?

It has currying support(call as constructor) and more flexible syntax

Thanks for the suggestion, but I'm gonna pass on this.


I have modified the head section for SEO

I have updated the title, and have filled the content attribute of meta tag where there was a  #  symbol. I have put comments along with the code.

i have the required changes . Please check

i have made the required changes . Please check

Looks better. But as I said, this won't make any noticeable difference. Please refer this to improve the state!

@kumarshobhit I was thinking about adding a robots.txt file to the root directory. Since this project is currently under staging condition. I'm approving it!
Good job! :rocket:

@all-contributors please add @kumarshobhit for code


[Webpack 3?] Duplicate declaration error

I've been trying to isolate this error, but I think that it has something to do with Webpack 3 and I can't pull anything of value from Babili and Webpack.
However, you can reproduce this issue by:
git clone https://github.com/ckeditor/ckeditor5-build-classic.git
git co babili-webpack-error
npm i
npm run build-ckeditor

This is the output I get:
(babili-webpack-error b720deb) p@m /workspace/test/ckeditor5-build-classic> npm run build-ckeditor

><EMAIL_ADDRESS>build-ckeditor /workspace/test/ckeditor5-build-classic
> ./bin/build-ckeditor.sh

Building 'build/ckeditor.js'...

Hash: 50fb7c52c064ebfdf790
Version: webpack 3.0.0
Time: 3798ms
          Asset    Size  Chunks                    Chunk Names
    ckeditor.js  405 kB       0  [emitted]  [big]  main
ckeditor.js.map  484 kB       0  [emitted]         main
  [37] ./ckeditor.js 191 bytes {0} [built]
  [58] (webpack)/buildin/harmony-module.js 596 bytes {0} [built]
  [59] (webpack)/buildin/global.js 509 bytes {0} [built]
    + 88 hidden modules

ERROR in unknown: Duplicate declaration "count"

Done.

This is the Webpack config: https://github.com/ckeditor/ckeditor5-build-classic/blob/babili-webpack-error/webpack.config.js
And the crucial file is this one: https://github.com/ckeditor/ckeditor5-typing/blob/958eeb26c6d862de3cdfbf53efd0a554e3c8e13e/src/typing.js
It imports:

https://github.com/ckeditor/ckeditor5-typing/blob/958eeb26c6d862de3cdfbf53efd0a554e3c8e13e/src/input.js
https://github.com/ckeditor/ckeditor5-typing/blob/958eeb26c6d862de3cdfbf53efd0a554e3c8e13e/src/delete.js

Which both depends on:

https://github.com/ckeditor/ckeditor5-typing/blob/958eeb26c6d862de3cdfbf53efd0a554e3c8e13e/src/changebuffer.js

Both of these modules import count function and I think that this is that duplicated count identifier.
If I disable Babili plugin in webpack.config.js everything works fine. I also checked that builds done without Babili run correctly so most likely the issue is not on Webpack's side.
Output without Babili:
(babili-webpack-error b720deb M3) p@m /workspace/test/ckeditor5-build-classic> npm run build-ckeditor

><EMAIL_ADDRESS>build-ckeditor /workspace/test/ckeditor5-build-classic
> ./bin/build-ckeditor.sh

Building 'build/ckeditor.js'...

Hash: 50fb7c52c064ebfdf790
Version: webpack 3.0.0
Time: 759ms
          Asset    Size  Chunks                    Chunk Names
    ckeditor.js  405 kB       0  [emitted]  [big]  main
ckeditor.js.map  484 kB       0  [emitted]         main
  [37] ./ckeditor.js 191 bytes {0} [built]
  [58] (webpack)/buildin/harmony-module.js 596 bytes {0} [built]
  [59] (webpack)/buildin/global.js 509 bytes {0} [built]
    + 88 hidden modules

Done.

I've checked the unminified output but I can't find anything there which would suspiscious.
I'm using webpack 3.0.0 and babili-webpack-plugin 0.1.2.

Actually, there are just two places where count identifier is used:
/* 36 */
/***/ (function(module, __webpack_exports__, __webpack_require__) {

"use strict";
/* harmony export (immutable) */ __webpack_exports__["a"] = count;
/**
 * @license Copyright (c) 2003-2017, CKSource - Frederico Knabben. All rights reserved.
 * For licensing, see LICENSE.md.
 */

/**
 * @module utils/count
 */

/**
 * Returns the number of items return by the iterator.
 *
 *		count( [ 1, 2, 3, 4, 5 ] ); // 5;
 *
 * @param {Iterable.<*>} iterator Any iterator.
 * @returns {Number} Number of items returned by that iterator.
 */
function count( iterator ) {
	let count = 0;

	for ( let _ of iterator ) { // jshint ignore:line
		count++;
	}

	return count;
}

/***/ })

And:
	insertChildren( index, nodes ) {
		this._fireChange( 'children', this );
		let count = 0;

		nodes = normalize( nodes );

		for ( let node of nodes ) {
			node.parent = this;

			this._children.splice( index, 0, node );
			index++;
			count++;
		}

		return count;
	}

The first is that imported count() function, so it's most likely it.

Thanks for the detailed writeup. Seems to a bug in DCE.

Duplicate of #226 . That got fixed. But looks like it has reappeared.
minimal repro:
function foo() {
  function count(it) {
    let count = 1;
    for(;it();) {
      count++;
    }
    return count;
  }
  return count;
}


Status Command

I was looking through Flare code and I thought it would be a cool idea to have a Status command, to be able to view the bot's status. I'm sure this will inevitably be shown on the Web panel, but I thought I'd make a suggestion for such a command here.
For reference, here's the Flare command: https://github.com/FlareBot/FlareBot/blob/master/src/main/java/stream/flarebot/flarebot/commands/informational/StatusCommand.java
What do y'all think?

I think this should be in the Beta, but that's my personal opinion, it looks like the perfect command to take a look at how the backend behaves instead of manually checking, highly recommended, we could extend this however. In my opinion a must have


Some minor changes to make local dev setup work

8u66+8u65arm java version is apparently not available, it fails to download. Upgraded the java version
removed the .vagrant folder from source control since local installation will generate those files (if present, it crib about uid 1000 not available for e.g.)

Sorry about java update problem, that was already updated in the roger-mesos. We should just have one repo.

Thanks a lot Venky, this is awesome !
On Sat, Apr 9, 2016 at 4:38 PM, Vinit Mahedia<EMAIL_ADDRESS>wrote:

Sorry about java update problem, that was already updated in the
roger-mesos https://github.com/seomoz/roger-mesos. We should just have
one repo.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207885367

Folks
I tried merging the latest from roger-mesos to ensemble. It's not trivial.
Given that roger-mesos is way ahead (including mesos/marathon/docker
versions + other changes across the repo) we could do 1 of the following -
Option 1 - Create PR against roger-mesos (and recreate ensemble as a fork
in mesosup and keep it updated.)
Option 2 - Create PR against a re-forked roger-mesos (name it ensemble as
is) under mesosup (and keep the fork link as this helps in keeping the repo
updated.)
Option 3 - Make the non-trivial merge to ensemble and continue to keep it
updated (this is a hassle actually)
We're currently on Option 3 which is a real pain to maintain.
Can we move to option 1 or 2?

Ankan.

On Sat, Apr 9, 2016 at 6:46 PM, Arunabha Ghosh<EMAIL_ADDRESS>wrote:

Thanks a lot Venky, this is awesome !
On Sat, Apr 9, 2016 at 4:38 PM, Vinit Mahedia<EMAIL_ADDRESS>wrote:

Sorry about java update problem, that was already updated in the
roger-mesos https://github.com/seomoz/roger-mesos. We should just have
one repo.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207885367

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207895645

Option 1 seems intuitive to understand, I vote for that.
Agree that current scheme (#3) is tedious

BTW, would there be any complications if I (legally an employee of Yahoo) make pull requests and contribute to seomoz org?

Yep, technically Moz has not released any IP claims to the project so if we
contribute to roger-mesos, we should not assume anything unless Moz adds an
indemnity clause.
How about we add stuff to ensemble and port changes back to roger-mesos ?
On Sat, Apr 9, 2016 at 7:22 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

BTW, would there be any complications if I (legally an employee of Yahoo)
make pull requests and contribute to seomoz org?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207898364

IANAL but -

There's an Apache 2.0 license in the code and it's public/open source.
And in both options 1 & 2 we'll keep the mesosup repo updated.
If there's a problem it is likely going to be at your employer's side for
the work you do. You should check with them on what the general policy is
for OS contribution.

In any case we could go with option 2 (Create PR against a re-forked
roger-mesos under mesosup). But keeping the fork link is needed else it's a
huge pain maintaining changes at both sides. For roger-mesos, the bulk of
the update (e.g. version upgrades etc) is going to happen in
seomoz/roger-mesos. And occasional changes on mesosup side. So, all we need
to do is always get the latest from seomoz before making any updates. Also,
if we do make updates at mesosup end, Vinit or I will merge the PR into
roger-mesos. With the github fork link in place all this is trivial.
For things that we completely develop under mesosup (like say junction - if
we ever get to that), we should just do that and seomoz could simply use
mesosup/junction like any other OS project (like mesos or marathon itself).
Does this make sense?
On Sat, Apr 9, 2016 at 8:20 PM, Arunabha Ghosh<EMAIL_ADDRESS>wrote:

Yep, technically Moz has not released any IP claims to the project so if we
contribute to roger-mesos, we should not assume anything unless Moz adds an
indemnity clause.
How about we add stuff to ensemble and port changes back to roger-mesos ?
On Sat, Apr 9, 2016 at 7:22 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

BTW, would there be any complications if I (legally an employee of Yahoo)
make pull requests and contribute to seomoz org?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207898364

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207906195

I just forked seomoz/roger-mesos into mesosup -
https://github.com/mesosup/roger-mesos.
So, we can go with either of the options 1 or 2 are possible (but let's
just do one!)
On Sun, Apr 10, 2016 at 7:40 AM, Ankan Mukherjee<EMAIL_ADDRESS>wrote:

IANAL but -

There's an Apache 2.0 license in the code and it's public/open source.
And in both options 1 & 2 we'll keep the mesosup repo updated.
If there's a problem it is likely going to be at your employer's side
for the work you do. You should check with them on what the general policy
is for OS contribution.

In any case we could go with option 2 (Create PR against a re-forked
roger-mesos under mesosup). But keeping the fork link is needed else it's a
huge pain maintaining changes at both sides. For roger-mesos, the bulk of
the update (e.g. version upgrades etc) is going to happen in
seomoz/roger-mesos. And occasional changes on mesosup side. So, all we need
to do is always get the latest from seomoz before making any updates. Also,
if we do make updates at mesosup end, Vinit or I will merge the PR into
roger-mesos. With the github fork link in place all this is trivial.
For things that we completely develop under mesosup (like say junction -
if we ever get to that), we should just do that and seomoz could simply use
mesosup/junction like any other OS project (like mesos or marathon itself).
Does this make sense?
On Sat, Apr 9, 2016 at 8:20 PM, Arunabha Ghosh<EMAIL_ADDRESS>wrote:

Yep, technically Moz has not released any IP claims to the project so if
we
contribute to roger-mesos, we should not assume anything unless Moz adds
an
indemnity clause.
How about we add stuff to ensemble and port changes back to roger-mesos ?
On Sat, Apr 9, 2016 at 7:22 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

BTW, would there be any complications if I (legally an employee of
Yahoo)
make pull requests and contribute to seomoz org?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207898364

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-207906195

Why not just have one repo? Nobody cares where you contribute stuff until you start making money off of it, significant amount that is. I believe forking and merging is technically the same thing as contributing directly, it's just a different method of doing exactly same thing.
@rvenkatesh25 you might need to talk to "the one who cannot be named and writes" I doubt you want to get involve in endless chain of emails eventually saying nothing of substance. @codingtwinky tried doing that, you might want to check with him.

On Sun, Apr 10, 2016 at 12:27 PM, Vinit Mahedia<EMAIL_ADDRESS>wrote:

Why not just have one repo? Nobody cares where you contribute stuff until
you start making money off of it, significant amount that is. I believe
forking and merging is technically the same thing as contributing directly,
it's just a different method of doing exactly same thing.

Well, you really should read your employment contract sometime :-).
One big issue is that roger-mesos is owned by the seomoz org in github, and
I imagine that Moz would prefer roger-mesos to stay closely aligned with
Moz's needs. Even today, we effectively have half the team at mesosup
outside of Moz, and in the future this could skew even further. However the
practical reality is that Ankan and Vineet are the only people doing
significant development right now.
Let's discuss this over a quick hangout. Is everyone free tonight ?

@rvenkatesh25 https://github.com/rvenkatesh25 you might need to talk to
"the one who cannot be named and writes" I doubt you want to get involve in
endless chain of emails eventually saying nothing of substance.
@codingtwinky https://github.com/codingtwinky tried doing that, you
might want to check with him.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208048352

I am free. It's just that I am really confused about which commit is on what repo and in future, it will create even more confusion when we have more commit.

For some reason, the java update failed for me, manual install worked. Might be something wrong at my end but putting it here if someone else runs into the same issue, there might be some problem.
stderr: E: Version '8u77+8u77arm-1~webupd8~1' for 'oracle-java8-installer' was not found

I'm available tonight.
On Apr 10, 2016 2:43 PM, "Vinit Mahedia"<EMAIL_ADDRESS>wrote:

I am free. It's just that I am really confused about which commit is on
what repo and in future, it will create even more confusion when we have
more commit.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208079220

Looks like Venky isn't free. Let's try to do this sometime this coming week.
On Sun, Apr 10, 2016 at 3:54 PM, ankan<EMAIL_ADDRESS>wrote:

I'm available tonight.
On Apr 10, 2016 2:43 PM, "Vinit Mahedia"<EMAIL_ADDRESS>wrote:

I am free. It's just that I am really confused about which commit is on
what repo and in future, it will create even more confusion when we have
more commit.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208079220

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208087265

Sorry, I was out during the day. We can talk tonight. What time works for everyone?

Or let's plan for tomorrow, Monday 8PM.
Btw, I am leaving for India on 15th (friday) and I will be there until may 9th.

Is everyone still around ? If so let's try to connect today. Reply back if
you see this and are ok for a chat at 8 pm PST
On Sun, Apr 10, 2016 at 7:28 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

Or let's plan for tomorrow, Monday 8PM.
Btw, I am leaving for India on 15th (friday) and I will be there until may
9th.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208123030

I'm in

Texting Vineet and Ankan.
On Sun, Apr 10, 2016 at 7:42 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

I'm in
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208130767

I'm in.
On Apr 10, 2016 7:55 PM, "Arunabha Ghosh"<EMAIL_ADDRESS>wrote:

Texting Vineet and Ankan.
On Sun, Apr 10, 2016 at 7:42 PM, Venkatesh Iyer<EMAIL_ADDRESS>wrote:

I'm in
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208130767

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208135494

https://plus.google.com/hangouts/_/grmwknyocrgzpaiitfz3irwnpme?authuser=0&hl=en
On Sun, Apr 10, 2016 at 7:57 PM, ankan<EMAIL_ADDRESS>wrote:

I'm in.
On Apr 10, 2016 7:55 PM, "Arunabha Ghosh"<EMAIL_ADDRESS>wrote:

Texting Vineet and Ankan.
On Sun, Apr 10, 2016 at 7:42 PM, Venkatesh Iyer <
<EMAIL_ADDRESS>wrote:

I'm in
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208130767

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208135494

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mesosup/ensemble/pull/2#issuecomment-208136386

Closing. Build against the forked roger-mesos repo now


profession not saved on production

The profession is saved locally and on staging but not on production. I can fill in the field, but is not shown in the views (both english and german)

now it works :) does anybody change something?

haha, no maybe some caching in your browser?

ja, maybe ... however, it's weird ... do we have any control about that from the script side? I wonder how this works for other profiles. @zaziemo could you please add a profession to your profile on production and check if it works, please? If yes, then we can close this issue.

@tyranja yes, I close it, maybe it's just me having problems with it


refactor: Make it so that sqrt lemmas don't turn equalities around

From LeanAPAP

maintainer merge

bors merge