Potential generator improvements.

@petertseng found some things that could be improved while he was building a generator:
From: https://github.com/exercism/xruby/pull/484#issuecomment-259102521

you need to touch .version or the generator won't run (increment_version requires that such a file exists). And you need to have an example file too. I tried to generate my tests before working on my example, but increment_version_in_example requires that the example actually exist.

@bmulvihill and I are working on improving the generator process, so we'll take these into account.

Yeah I actually noticed this too, we could have a simple command to scaffold this stuff when creating a new generator.
ie
bin/generate new EXERCISE_NAME

We might even want a different executable to handle something like this to prevent confusion, something like bin/scaffold EXERCISE_NAME

Maybe, but look at adding the functionality to take an argument.  This seems so closely tied to generate that it does not make sense to have a new executable.

Another idea that could be considered if y'all really do not want a new command:
Make the two cases mentioned above tolerant of the files not existing.

In the case of the .version file: Create it and write 1 into it.
In the case of the example file: Either do nothing, or simply print a warning "example file doesn't exist" (since this case should only happen when writing the generator for the first time)

That said, something to scaffold the adding of a new exercise with generator seems useful - the lib file, the example.tt file, possibly appending it to config.json if possible (!). Back in the day it used to be more, you would have to add a bin/generate-#{slug}, thanks for getting rid of that step!

Prefer to create .version on first use.  That is a great thing... No example file warning is good, as well, a first contributor would be lead to do the needful.

Should now use the version number from canonical rather than the sha as is currently done in bin/generator/git_command.rb  Should add a warn('Deprecated - use canonical_version instead.') maybe?

@kotp and I are working on a generator, and have noticed some pain points.

The documentation says a generator requires workload, however the method is actually work_load.
It isn't at all clear how to construct work_load

I think it should be workload it's one word.

The documentation says a generator requires workload, however the method is actually work_load.

What made you think this? Was it some documentation? Another test file?
I'm trying to work out what we need to do to can clear up any confusion.

It isn't at all clear how to construct work_load

Yeah the documentation needs to be improved.
Thanks for the feedback @hilary

One of the causes of my confusion was the inconsistency between #test_name (in $PROBLEM_cases) and #name (in example.tt). I left a note in your PR as well, @Insti

Currently these ideas of @Insti are buried in a PR. I wanted to surface them here so they are easier to find...

Now some of the things from the grand design in my head:

Note: "problem" in all these examples is the variable exercise name.
Generator problem_cases.rb should live in exercises/problem/.meta/generator/
Templates should live in problem/.meta/generator/ be called test_file_template.erb (or similar). Once they are under .meta they don't need to contain the word example
There definitely should be a default test_file_template.erb - probably in /lib/generator
ExerciseCase should not be an OpenStruct and the canonical data should be kept separate from the methods of this class.
Remove requirement for a test case object to know its index.
canonical_data version should be added to the test file - probably immediately to the left of the abbreviated commit hash.
.version should be updated to be the canonical_data version (e.g. 2.1.0) plus an x-ruby version. (3) e.g.: <IP_ADDRESS>
Some of this will require changes to the bin/generator code.
By creating the new modern generators under .meta/generator it will be easy to track which exercises have been upgraded as the lib/problem_cases.rb are deleted with the end goal being all generators living under .meta/generator and lib being mostly empty.
Everything needed to create a generator for an exercise will be in exercises/problem/.meta/generator/

Todo
In checklist form so we can track our progress.

[ ] Generator problem_cases.rb should live in exercises/problem/.meta/generator/
[ ] Templates should live in problem/.meta/generator/ be called test_file_template.erb (or similar). Once they are under .meta they don't need to contain the word example
[ ] There definitely should be a default test_file_template.erb - probably in /lib/generator
ExerciseCase should not be an OpenStruct and the canonical data should be kept separate from the methods of this class.
[ ] Remove requirement for a test case object to know its index.
[ ] canonical_data version should be added to the test file - probably immediately to the left of the abbreviated commit hash.
[ ] .version should be updated to be the canonical_data version (e.g. 2.1.0) plus an x-ruby version. (3) e.g.: <IP_ADDRESS>
[ ] All generators should live under .meta/generator
[ ] Everything needed to create a generator for an exercise will be in exercises/problem/.meta/generator/

Question: ".version should be updated to be the canonical_data version (e.g. 2.1.0) plus an x-ruby version. (3) e.g.: <IP_ADDRESS>".
Why do we want the x-ruby version? I'm assuming that the canonical data version is following semantic versioning. Understanding the role of the xruby version should (hopefully) make it possible to include it within the semver model.

We can't change the x-common version just because we do something.
If we were to add ruby-specific tests (there's a couple I would like to add things like input mutation checks to) we need to have a way of tracking those too.
If you want to use some other combination of symbols that is more semver compliant that is fine, just let me know what you want them to be.

I guess I'm asking why we don't just use the canonical data version?


LDAP identity provider

Whould be useful integrate LDAP as identity provider to avoid manual insert of users.

Hi @saiello.
I have been waiting for this to come up and now day has finally arrived. This should be rather straight forward. We can either allow to configure Castle Mock LDAP directly or we can allow Castle Mock to use the Tomcat Realm. Or maybe both solution could be good. I will look into how we could add support for this.
Best regards,
Karl Dahlgren

@karldahlgren currently castlemock is secured using spring security, so I think spring security support for ldap will be more convenient than of tomcat.

Hi, Its better Spring LDAP if you are using spring, I think this Feature is a Main Security concern.


TexerII APE support

TexerII source code is available
Get permission for integration under BSD from @unconed

Permission granted.

Development is ongoing in branch wip/texer2.

The source code provided is of a development version, so I have to extract the missing pieces by reversing the released .ape binary. This is going to take a while.

Almost done, only cosmetic features and edge cases left.

Help text in proper window
Fix loading of images with weird filenames

@unconed fyi.


SVG example generates svg holding lots of small black boxes -> the DOM looks weird.

Link to PDF file (or attach file here):
error_prone_file.pdf
It also happens in other pages of the pdf file, but I have only provided one page to reproduce the problem.
Configuration:

Chrome - 58.0.3029.110 (64-bit)
macOS Sierra - 10.12.5
PDF.js version: "betaVersion": "1.8.188"

Steps to reproduce the problem:

Just try the added pdf file with pdf.js's own provided svgviewer example

What is the expected behavior?
https://www.dropbox.com/s/c2gknbtlo6vchua/Screenshot 2017-06-07 14.34.57.png?dl=0
What went wrong?
https://www.dropbox.com/s/082uf4z73v19zrs/Screenshot 2017-06-07 14.35.26.png?dl=0
--
I the earlier versions of pdf.js this problem was occurring in many of my pdf's -> many have been fixed over time, but it still seems to occur sometimes.
--
kaarebs

With the current master version I also see grey boxes when I open the generated SVG file in Chrome and Firefox.
With PR 8542, the grey boxes disappear (the black boxes are still around though).
Before #8542:

After #8542:


chore: Use axios instead of the deprecated request module

mm, CI has an issue?

this looks like an issue somewhere inside web view handlers. Not related to my changes at all. Btw, xcuitest driver also fails some web view-related e2e tests. Feel free to jump in if you have time, because I never touched that part and, to be honest, have minimum passion to work with it.


404 error

Having problems getting it to open in power BI.  Any help would be appreciated.

I'm seeing same error (404) when single query returns many records. Reducing the result size would help. Then I used multiple queries and merged results with PowerBI, have to admit it's not a great workaround.


ERROR: Will not install to the user site because it will lack sys.path

I try the "Bare Metal Installation" like described in the documents.
After typing pip3 install -r requirements/base.txt get the following: ERROR: Will not install to the user site because it will lack sys.path precedence to setuptools in /opt/PapermergeDMS/.venv/lib/python3.8/site-packages
Info:

OS: Ubuntu Server 20.04.4
Browser Firefox
Database [SQLite, PostgreSQL 12.1]
Papermerge Version 2.0.1

That part of documentation is really outdated :(
"Bare Metal Installation" part is meant only for Python/Django developers.
I will move "Bare Metal Installation" into separate "Developer Manual" section to make it clearer that its target auditory are developers.
If you intend to install and play around with Papermerge instance from (advanced) user perspective you may have a look
at setup with portainer or setup with docker-compose


we should deprecate old libraries

Many examples still use old libraries. We should port the examples one by one, and clearly mark the libraries as deprecated, so no one uses them for new verification projects. Should we have a deprecated folder in the lib folder, mirroring the to_be_ported folder in the exercise folder?
Array.fst defines seq and seems to be replaced by Seq.fst and SeqProperties.fst and is used in the following examples:
algorithms/downgrade.fst
algorithms/qsort_arr.fst
bignum/eval_st.fst
bug-reports/bug151.fst
crypto/acls-cap.fst
crypto/cert.fst
crypto/cnt-format.fst
crypto/encrypt.fst
crypto/encrypt2.fst
crypto/encrypt3.fst
crypto/format.fst
crypto/hybrid.fst
crypto/hybrid2.fst
crypto/mac.fst
crypto/mac3.fst
crypto/padding.fst
crypto/rpc.fst
crypto/rpc2.fst
crypto/sig.fst
to_be_ported/misc/ringbuffer.fst
to_be_ported/monadic/sparseArray0-1.fst
to_be_ported/monadic/sparseArray0.fst
to_be_ported/sep/rbsep.fst
to_be_ported/sep/rbsep.fst
to_be_ported/sep/rbsep2.fst
to_be_ported/sep/rbsep2.fst
unit-tests/certsig.fst
unit-tests/mac2.fst

partialmap.fst defines modules Set, Map, Heap, Array and appears in
crypto/cnt-format.fst
crypto/format.fst
crypto/Makefile

I suggest maybe we could associate a status info to each file to know wether it is

Stable
InConstruction (or whatever...)
Deprecated

Then we can review the deprecated one, check that everything has been ported to the new one and cleanup when ready.

Sounds like a good idea. Should we agree on the syntax of this metadata, even if we don't have a java-doc like tool to process it?

 We don't care about backwards compatibility! Just delete the libraries you think are no longer needed.

Strongly agree with Catalin. Delete old ones. Partialmap.fst, especially.

in particular, FStar.JS.fst is no longer used, I think...

Nik suggested creating a new issue for F* Lib cleanup, but we should likely also revisit the status of this one.

For instance I am wondering whether we really need a TwoLevelHeap library? We could move it to examples/ if it has didactic value?

There are probably a few things that should be removed like FStar.Crypto.fst but I think ulib is currently in a much better shape than lib was when we created the issue. To me documentation should have higher priority as we can remove or relocate files when documenting...


Where's the api info to send a resolve

Hi There,
I'm looking for the how to send an acknowledge or resolved for an alert

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

ID: c8ca0e65-acf5-32c8-bfa1-8a614881e053
Version Independent ID: b19eea83-4834-6824-1363-2542888b4b1c
Content: Using Log Analytics Alert REST API
Content Source: articles/log-analytics/log-analytics-api-alerts.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

@cconrado Thanks for the feedback! We are currently investigating and will update you shortly.

@cconrado I believe this is it:
https://docs.microsoft.com/en-us/rest/api/monitor/alertsmanagement/alerts/changestate

@cconrado closing this issue for now but feel free to add comments as needed.

@jason-j-MSFT this is it just its not easy to find

@bwren could you take a look at this?  This function may be good to add to the document, and as @cconrado stated, its hard to find,

@rboucher Should be able to look at this.

@rboucher awesome thanks

unfortunately, it looks like this will be held up until I'm back for the holidays @cconrado . Just keeping you in the loop.

@rboucher aww bummer but makes sense thanks

@cconrado  Worked a little late to try and push it through. Take a look tomorrow.  I'm not sure if you have access to this PR, but the changes are at https://github.com/Azure/azure-docs-rest-apis/pull/2124

@rboucher I don't have access but I certainly appreciate the extra effort. Thanks 👍


Cannot establish connection with api.binance.com:443

I have tried to downgrade urlib3 but the error persists. I have tried curl https://api.binance.com/api/v3/time, the servertime is returned successfully.
2023-05-15 10:58:16,811: loading name: lvtu, exchange name: binance,  pair name: ETHBUSD
2023-05-15 10:58:16,811: loading name: lvtu, exchange name: binance,  pair name: ETHUSDT
2023-05-15 10:58:16,811: loading name: lvtu, exchange name: binance,  pair name: BTCUSDT
2023-05-15 10:58:16,811: name: lvtu, exchange: binance
/home/ic/Desktop/worldbreak-dev514
2023-05-15 10:58:16,811: GET https://api.binance.com/sapi/v1/capital/config/getall?timestamp=1684119496811&recvWindow=10000&signature=8002e37cb1ec87f06e5b5d59a4686421d2ae26dd6c0a086fc79934004bfb1d9f, Request: {'X-MBX-APIKEY': '', 'User-Agent': 'python-requests/2.29.0', 'Accept-Encoding': 'gzip, deflate', 'Accept': '/', 'Connection': 'keep-alive'} None
2023-05-15 10:58:16,812: Starting new HTTPS connection (1): api.binance.com:443
Traceback (most recent call last):
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connection.py", line 174, in _new_conn
conn = connection.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/util/connection.py", line 95, in create_connection
raise err
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/util/connection.py", line 85, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connectionpool.py", line 703, in urlopen
httplib_response = self._make_request(
^^^^^^^^^^^^^^^^^^^
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connectionpool.py", line 386, in _make_request
self._validate_conn(conn)
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
conn.connect()
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connection.py", line 363, in connect
self.sock = conn = self._new_conn()
^^^^^^^^^^^^^^^^
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connection.py", line 186, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7fdef6726f10>: Failed to establish a new connection: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/requests/adapters.py", line 487, in send
resp = conn.urlopen(
^^^^^^^^^^^^^
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/connectionpool.py", line 787, in urlopen
retries = retries.increment(
^^^^^^^^^^^^^^^^^^
File "/home/ic/anaconda3/envs/trading/lib/python3.11/site-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.binance.com', port=443): Max retries exceeded with url: /sapi/v1/capital/config/getall?timestamp=1684119496811&recvWindow=10000&signature=8002e37cb1ec87f06e5b5d59a4686421d2ae26dd6c0a086fc79934004bfb1d9f (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdef6726f10>: Failed to establish a new connection: [Errno 101] Network is unreachable'))
During handling of the above exception, another exception occurred:

The problem that is described here doesn't involve any usage of our library. Therefore we'd close this issue. Please consult either binance or the urlib3's author for your issue. Thank you.


Afghanistan data has double entries

This issue was raised by Barnali (barnali@ucsb.edu).
Currently I am exploring Afghanistan crop yield data and found that the unit AF2017A127 i.e.  Kandahar has different double entries for both winter and spring season. I have pulled the data on 28th August 2024.

@gnodnooh I can't help too much here because I never ran the AF code, and don't have the script set up to read from the AUX data. I can confirm that the duplicates in the final product are real and that they shouldn't exist. But beyond that I'm not sure how to help.
If it's a consideration for us, we are about to upload the aux data into the FDW and the duplicates don't exist in that dataset, so we could run the script and check to make sure we don't get duplicates there.


Remove base_style and base_template relationship

As previously discussed, this will remove the field base_style_id from the doku_template model and subsequently remove all references and relationships associated with base Templates and base Stylesheets.
Along the way, I introduced ESLint which should help us detect issues earlier and enforce some JavaScript coding style guides. Appropriate commands can be found in the package.json file:

npm run lint
npm run lint.fix to automatically fix issues (if possible). Always check the result before committing!

While enforcing the ESLint rules, I stumbled upon some issues that have been fixed right-away. E.g. this:
https://github.com/desklab/doku/blob/b892d82978d88b081fb661a35d0f9f4a1e8bc727/doku/static/src/sites/templates.vue#L60

Did you notice the failing tests, @jnsdrtlf ? Seems like collecting them fails due to name 'SQLAlchemySchema' is not defined (this effects all seven tests)

Oh no, I somehow missed that. Could you fix it for me please?

Fixed the failing tests in 2e614957db65e60f42d8cb1a2f6adc9e7f4d6e2b. I think we still have some problems with legacy-base-stylesheets:
Removing a stylesheet (which was created as a base-stylesheet for a template when they still existed), which is no longer used by any template (and the correct tag unused is shown as well), fails with:
psycopg2.errors.ForeignKeyViolation: update or delete on table "doku_stylesheet" violates foreign key constraint "doku_template_base_style_id_fkey" on table "doku_template"
DETAIL:  Key (id)=(1) is still referenced from table "doku_template".

I am quite certain that you forgot to run alembic upgrade head ;)
The constraint should have been dropped in this line:
https://github.com/desklab/doku/blob/2e614957db65e60f42d8cb1a2f6adc9e7f4d6e2b/alembic/versions/c2d7aa36d0e7_remove_base_style.py#L21

As we dicussed / i showed you before, i did run alembic upgrade head and still got the error with my local development setting used for some time before. However, this seems to be related with some local issues with the state of the db and alembic. Conesquently i created a new doku environment from bottom up and the issue was no longer present, therefore i think we should merge this one, thanks for the work (also regarding the code clean-up)!


raidboss/oopsy: add triggers for Gilded Araya

Tested in emulator and in game.
@JLGarber is handling the timeline.

Thanks to a nice looong testing run, it looks like Khadga does repeat in the loop.  It was pattern 1 again, but unknown if that's fixed or random, so I refactored the trigger to use combatant data to make sure the trigger is correct.  @JLGarber , I know you approved already, but tagging just in case you want to re-review.  If not, I'll merge late tonight.

I just did this trial for the first time finally, using these triggers. Seems like the image-related callouts are too delayed to react to properly. Is there some other factor that could be used to determine the callout sooner?

I just did this trial for the first time finally, using these triggers. Seems like the image-related callouts are too delayed to react to properly. Is there some other factor that could be used to determine the callout sooner?

@JLGarber and I were testing last night and talked about it, but the options are limited and not great.  For the initial three attacks where the Image is stationary, we could trigger off a fixed delay from the tether, which gives more flexibility in terms of timing; but that's arguably the easiest form of the mechanics since she is always north.
All of the subsequent Iconic Execution mechs involve a (we're pretty sure) random cardinal jump (8CB2), followed by the same 'mirror my last attack' Iconic Execution cast (8CB1) from the boss, which happens at exactly the same time as the Image starts casting the relevant Iconography attack.  We don't know what cardinals will be safe until the jump is complete -- I wasn't able to find any data like headings to telegraph where she will land.  And the image jumps and starts casting at almost exactly the same time.  I originally tested using combatantData after the jump, but given the need to add a small delay for safety, the call actually comes out later than just triggering from the Image's 20 line (which has the correct pos data).  I think the problem is that there just isn't a lot of time to react to the mechanic in the fight given the visual cues we get, and I didn't see anything else in the data that could give us more lead time.

Here's an example with full packet decode dump. If we had ActorSetPos available that would net an extra 1.2s.
But my main thought here is that maybe the previous mechanic should mention the followup mechanic, e.g. something like:

Under -> Under Image
Under -> Under Image after teleport

4096|2024-01-17T17:30:46.2600000-05:00|ActorControl|400105FB|SetModelState|00000004|00000000|00000000|00000000|00000000|835b2c6f984c5809
261|2024-01-17T17:30:45.9530000-05:00|Change|400105FB|WeaponId|4|352348899670b82b
21|2024-01-17T17:32:20.7880000-05:00|400105FB|Asura Image|8C80|Divine Awakening|400105FB|Asura Image|49|8000|1B|8C808000|0|0|0|0|0|0|0|0|0|0|0|0|69200|69200|10000|10000|||100.00|80.10|0.00|0.00|69200|69200|10000|10000|||100.00|80.10|0.00|0.00|00002BC8|0|1|dab8609c79deeb52
264|2024-01-17T17:32:20.7880000-05:00|400105FB|8C80|00002BC8|0|||||6a2ee8cf7a4d39d4
4096|2024-01-17T17:32:20.7880000-05:00|ActionEffect1|400105FB|400105FB|00000000|00008C80|00002BC8|2.6|E0000000|0|-9.58737992426961E-05|8C80|00|Spell|00|1|SetModelState|0|0|0|0|80|0|False|True|Unknown|Unknown|0|StartActionCombo|0|0|0|0|80|35968|False|True|Unknown|Unknown|35968|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|Nothing|0|0|0|0|0|0|False|False|Unknown|Unknown|0|400105FB|00000000|933dafe9a3c4cd1d
4096|2024-01-17T17:32:21.5920000-05:00|ActorControl|400105FB|SetModelState|00000000|00000000|00000000|00000000|00000000|c8838b3056c71747
261|2024-01-17T17:32:21.1230000-05:00|Change|400105FB|WeaponId|0|c6045e01fa4eb79b
38|2024-01-17T17:32:23.2870000-05:00|400105FB|Asura Image|005A5A00|69200|69200|10000|10000|0||100.00|80.10|0.00|0.00|0|0|0|026A09F8|0|E0000000|2dafe4c237da22c5
26|2024-01-17T17:32:23.2870000-05:00|9F8|Unknown_9F8|9999.00|E0000000||400105FB|Asura Image|26A|69200||aa6866fc05dbca6e
4096|2024-01-17T17:32:23.2870000-05:00|StatusEffectList|400105FB|00|5A|5A|00|69200|69200|10000|10000|0|0000|00|09F8|026A|0.0000|E0000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|0000|0000|0.0000|00000000|6b2bbe3c15abe9ce
4096|2024-01-17T17:32:23.2870000-05:00|ActorControl|400105FB|GainEffect|000009F8|0000026A|00000000|00000000|00000000|259fbf1f23170d0d
35|2024-01-17T17:32:25.3800000-05:00|400105FC|Asura|400105FB|Asura Image|0000|0000|00F3|400105FB|000F|0000|383b0e60b768279f
4096|2024-01-17T17:32:25.3800000-05:00|ActorControl|400105FC|Tether|00000000|000000F3|400105FB|0000000F|00000000|b25a10e8f77e20a3
4096|2024-01-17T17:32:37.4400000-05:00|ActorControl|400105FB|PlayActionTimeline|00001E39|00000000|00000000|00000000|00000000|d451c9ab8e6f6899
4096|2024-01-17T17:32:38.5050000-05:00|ActorSetPos|400105FB|1.5707|00|00|00000000|80.1000|100.0000|0.0000|00000000|9159d71b696c1e82
4096|2024-01-17T17:32:38.5510000-05:00|ActorControl|400105FB|PlayActionTimeline|00001E43|00000000|00000000|00000000|00000000|0dd6f9db909e4d10
261|2024-01-17T17:32:38.2340000-05:00|Change|400105FB|Heading|1.5708|PosX|80.1000|PosY|100.0000|PosZ|0.0000|a957a12a47ba9afc
261|2024-01-17T17:32:38.2340000-05:00|Change|400105FB|Heading|1.5708|PosX|80.1000|PosY|100.0000|PosZ|0.0000|186577a08c8ed288
20|2024-01-17T17:32:39.7080000-05:00|400105FB|Asura Image|8C84|Wheel of Deincarnation|400105FB|Asura Image|3.700|80.10|100.00|0.00|1.57|654839f269d8bceb

Here's an example with full packet decode dump. If we had ActorSetPos available that would net an extra 1.2s.
But my main thought here is that maybe the previous mechanic should mention the followup mechanic, e.g. something like:

Under -> Under Image
Under -> Under Image after teleport

Yeah, I think adding the followup to the callout makes sense.
I just went back to look at the raw log without the analysis filter.  Even without ActorSetPos, we do have a CombatantMemory line ~1.1s before the Image starts casting.  I vaguely remember some discussion somewhere about triggers using CombatantMemory lines but I don't recall the outcome.  Thoughts?

I vaguely remember some discussion somewhere about triggers using CombatantMemory lines but I don't recall the outcome. Thoughts?

https://github.com/OverlayPlugin/cactbot/blob/749239d373ccd5d43287045b37a34bb82ec5f460/ui/raidboss/data/04-sb/ultimate/ultima_weapon_ultimate.ts#L548-L553

I vaguely remember some discussion somewhere about triggers using CombatantMemory lines but I don't recall the outcome. Thoughts?

https://github.com/OverlayPlugin/cactbot/blob/749239d373ccd5d43287045b37a34bb82ec5f460/ui/raidboss/data/04-sb/ultimate/ultima_weapon_ultimate.ts#L548-L553

Thanks.  I'll do a little tinkering and see if it feels better.

Yeah, I concur with “include the image follow-up in the initial trigger output”. It just makes sense in terms of priming the player for “there is more after this”.

This feels much better in game with Iconic Execution.  LMK if other changes; otherwise, good to go on my end.

Okay, with this latest round of changes it looks good to me. Go ahead and push the button when you're ready. I'll get the timeline stuff in place and ready for review sho9rtly.


Bug: mux-player-react breaks in NextJS

Is there an existing issue for this?

[X] I have searched the existing issues

Which Mux Elements/Packages does this apply to? Select all that apply
mux-player
Which browsers are you using?
Chrome, Edge ("Edgeium")
Which operating systems are you using?
Other (add details below)
Description
Hey! I'm working on a project right now and we're using mux-player-react with NextJS. When I used the minimal styling of the component by importing from mux-player, it was throwing an error like this
SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:988:16)
    at Module._compile (internal/modules/cjs/loader.js:1036:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)

I already saw a PR that fixes this (but for a separate package), and I want to add that to the mux-player package.
Reduced test case
No response
Steps to reproduce

Setup any nextjs app version 12.3.0
Install mux-player-react, import it, use it, add in the custom minimal style by importing from @mux/mux-player/themes/minimal
Run the nextjs app

Current Behavior
NextJS app is throwing an error

Expected Behavior
App should run smoothly, the nextjs app should render the mux-player-react component with minimal style
Errors

What version of the package are you using?
v1.11.3

To add, I was able to fix this locally by modifying the package.json file in mux-player in my node_modules directory. I just added the key-value pair type: module just like in the previous PR I referenced


fix github actions rust caching

moves rust setup & caching to a composite action
only caches on main (we are using 80gb of github's 10gb evicting all our cache entries instantly)
will see if this is enough or if it has to be reduced further
cleans up some workflows

Current dependencies on/for this PR:

main

PR #3175   👈

This comment was auto-generated by Graphite.

only caches on main

Does this mean that PRs will use the cache on main to build, but not create their own cache?

(we are using 80gb of github's 10gb evicting all our cache entries instantly)
will see if this is enough or if it has to be reduced further

You mentioned cargo-sweep: if our cache is currently only additive, could we use cargo-sweep on it to make sure we don't cache outdated artifacts?

@alexkirsz
yes caches will be created on main and reused by PRs, but PRs don't save their cache
cargo-sweep would be nice to include as well

@alexkirsz
yes caches will be created on main and reused by PRs, but PRs don't save their cache
cargo-sweep would be nice to include as well, but might have to write a js action to get that to run before and after jobs


pythonPackages.lightgbm: fix build

Motivation for this change
#68361
fix build
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

thank you @jonringer

@Ma27 still needs backport for 19.09

Thanks for the heads up! Backported as e0ffa0fd398a655719d3775fc5e78b50cdbd7ceb.


Error when attempting to sign in to github pull requests

Click on "Allow" in "the extension github pull requests nightly build wants to access the github account":

See:

Oh no! An error occurred!
Please restart the sign in process from the editor.
Error code 801

Seem like it eventually worked. I wouldn't expect to need to go though external github auth flow given I was already signed in to preferences sync?

Yeah, the reason for the additional auth is that preferences sync and GHPR have different permissions, so a new, different token is needed.
Closing as a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/1221


Miscellaneous build improvements

Description
This patch does quite a bit of things, mainly:

Reuse the builder container instead of spinning a new container on each command.
Refactor CMakeLists files so they depend on less env variables.
Separate unit tests to their own cmake script.
Compile unit tests as separate binaries and run them via ctest.
Add unit tests running under ASAN and UBSAN in CI.

This is meant to be step one of a larger refactor, aiming to be able to build collector on any system and not just inside the builder. Next step is to turn all third party dependencies into cmake modules, giving the option to use system installed dependencies or compiling the dependencies alongside the collector build step.
Checklist

[x] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Testing Performed
CI should be enough.

Nice changes!

One thing that often bothers me is that currently the build process could not be interrupted with SIGINT. Would this be different with this PR?

Just tested it and SIGINT absolutely stops compilation on make image with this change.


Mario/deps update

Updated plutus-extra, plutus-apps`, and all that follows.

Is there a reason we're change to mlabs plutus-extra over Liqwid?

Is there a reason we're change to mlabs plutus-extra over Liqwid?

Yes, it's https://github.com/Liqwid-Labs/plutus-extra/pull/192
Once that PR is merged or plutus-extra updated wholesale we can switch back to Liqwid.

Gotcha, we can merge then but let's get a ticket up to revert to regular plutus-extra once we're able


SOMA Slice to AnnData bug [main-old branch]

Trying to slice a specific layer called X_norm from my SOMA Collection. Here's some pseudo code:
answer = soco.query(
    obs_ids=['example_1'],
    X_layer_names=["normalized_X"],
)
SOMASlice.concat(answer)

Throws the error:
KeyError: 'data'

Should this function have another variable for the X layer being queried?
https://github.com/single-cell-data/TileDB-SOMA/blob/a85213b595d7932aa9616aa0d2b53ec051f8479f/apis/python/src/tiledbsoma/soma_slice.py#L74

Hi @mdylan2 -- can I please get your tiledbsoma.__version__?

0.1.22

CLosing because this is based on old SOMA spec


Hamburger Menu Dysfunction in PymPay Repository

Problem:
The hamburger menu in the PymPay repository is not functioning as expected, impacting the navigation experience for users.
Expected Behavior:
The hamburger menu should toggle and display the navigation options seamlessly, providing an intuitive and user-friendly navigation experience.
Steps to Reproduce:

Open the PymPay repository.
Access the website or application.
Attempt to open the hamburger menu.

Current Behavior:
The hamburger menu does not respond or display the navigation options as intended, hindering users from accessing crucial features.
Screenshot:

Please @AdityaSeth777 assign me this issue. I want to work on it. Thank You

Sure. For the record, this is how an issue should be presented with. I'm assigning it to you. Start working. All the best.

@Soumojitshome2023 Submit the PR once you are done. Thank you for raising this issue though.


Crash: _terminal (and other members?) used after freed in TermControl

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable): master (672010a1)

Any other software?

Steps to reproduce

Open the terminal
Put your mouse cursor on the + button to open a new tab
Quickly click with the left mouse button and then click with the middle mouse button to open a tab and close it. If you do it right, you should get this error message (which might be a bug in and of itself?):
Don't click OK yet!
Focus the terminal window, behind that error message.
Repeat 3. Nothing will happen because the application is frozen while you click OK in the dialog.
Click OK in the dialog.
Now, the dialog closes and another dialog with the same error message opens. If it didn't open, you need to start again from 2. You'll need to train to click with the right timing.
Click OK in the new dialog.
Terminal crashes!

Expected behavior

No crash.
Actual behavior

Crash on this line: https://github.com/microsoft/terminal/blob/941a44a46491e1a018419eb24c9d92d3b2640e55/src/cascadia/TerminalControl/TermControl.cpp#L563 because even though we check that this is still alive with weakThis, _terminal is null. Also, it seems that there are other places where we do check this but don't check members that could be null now because Close was called. It's scary!

Triaged this one into v1.0 - it's stability and reliability, sp p1

The "c0000142" error is actually because powershell was started and its parent console object died before it had a chance. That one we just can't help here :smile:

Okay I tried to to this naively and bluescreened my laptop. I'm not touching this, but @DHowett-MSFT has an idea of how to go about this, so I'm going to let him have it


Update documentation with Setup notes

This is ready for review. PR here - https://github.com/endatix/docs-website/pull/3


Add info screen

Description
Create a secondary screen of information which users can select to review device status and performance
Requirements

Screen should be activated by pressing a button

Needs to be soldered to the board
Needs to be integrated into the 3D printed case (see #13)

Display network info

IP Address
Azure connection status

Temporarily implemented via the onboard button in #16. I'll implement a new physical button when I get around to breadboarding. Software-wise, that should only require changing the button reference from board.BUTTON to the new button's output pin.


How to fetch audioSessionId from MediaBrowser.

How to fetch audioSessionId from MediaBrowser or tell me some other way to get the audio session id.

The only way to get the audio session ID with a MediaController/MediaBrowser is registering a Listener and implement onAudioSessionIdChanged(int). This callback is currently not called for MediaController (see MediaControllerImpBase). I think we should call that callback because we promise this by the listener contract. I marked this as a bug.
However, I wonder a bit why you need the audio session ID on the controller side. You can register the same listener on the session/service side when you build your session/player in the service. Can you tell us about your use case of receiving the audio session ID on the controller side?

Drive-by note: Player.Listener.onAudioSessionIdChanged will only be invoked if ExoPlayer.setSessionId is called - it won't be called with the audio session ID that ExoPlayer generates when it's constructed (this is since ExoPlayer 2.13.0).
So although fixing MediaController to invoke Player.Listener.onAudioSessionIdChanged seems generally correct and worthwhile, I'm not sure if it will actually help to access the auto-generated session ID from the controller side?

The only way to get the audio session ID with a MediaController/MediaBrowser is registering a Listener and implement onAudioSessionIdChanged(int). This callback is currently not called for MediaController (see MediaControllerImpBase). I think we should call that callback because we promise this by the listener contract. I marked this as a bug.
However, I wonder a bit why you need the audio session ID on the controller side. You can register the same listener on the session/service side when you build your session/player in the service. Can you tell us about your use case of receiving the audio session ID on the controller side?

My requirement was to use it to create an equilizer intent.

Yeah. Sorry I'm  a noob, so you'd have to be a bit more verbose to make me understand.  :)
Generally, I would recommend to move this logic to the session, instead of having it at the controller end. Send a custom command from the controller to the service if you need to initiate this from the controller side. The session can create the equilizer intent. Without exactly knowing what this is, I'd say this belongs to the session/service side.
However, I mark as an enhancement. We will update this bug once there is a change regarding this. I don't think this is of high priority though.

Yeah. Sorry I'm a noob, so you'd have to be a bit more verbose to make me understand. :)
Generally, I would recommend to move this logic to the session, instead of having it at the controller end. Send a custom command from the controller to the service if you need to initiate this from the controller side. The session can create the equilizer intent. Without exactly knowing what this is, I'd say this belongs to the session/service side.
However, I mark as an enhancement. We will update this bug once there is a change regarding this. I don't think this is of high priority though.

Thanks for the suggestion. I was also thinking the same.
But suppose someone decides to built his own equilizer and want the setting to preview in real time, I guess he might need audioSessionId to do so. Am I right or are their any other solution.
Thanks


Forth extensions steal .FS registration from F# language

Can't seem to find a Forth plugin for VSCode that respects .FS[X] files as F# rather than Forth.

/causedByExtension
Please file for the Forth extensions you think are doing this. There might be an inherent conflict here, it seems both languages are using .fs.


🪗 Adds Accordion component

<Accordion />

I used the radix accordion as the base so I didn't have to reinvent the a11y details
~rather than exporting a single Accordion component that can be passed some array of {title: ..., content: ...} data, I opted to export the outer Accordion as well as AccordionItem, AccordionTrigger, and  AccordionPanel so each accordion can be composed as needed.~
The Accordion subcomponents, Item, Trigger, and Panel, are exports on the larger Accordion component and accessed via dot notation.
the usage ends up looking like:

<Accordion>
  <Accordion.Item>
    <Accordion.Trigger>
      Trigger content
    </Accordion.Trigger>
    <Accordion.Panel>
      Collapsible content
    </Accordion.Panel>
  </Accordion.Item>
</Accordion>

both Accordion.Trigger and Accordion.Panel can take a string, JSX, native elements, or whatever as children
Accordion.Trigger and Accordion.Panel don't need to be included in any particular order, so long as they're both children of Accordion.Item and connected via id, so content can be placed between them, the trigger can be placed beneath the panel, etc.
everything else should be fairly straightforward

📦 Published PR as canary version: 1.15.8--canary.72.6a2ec06.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Is there a way to keep the compound exports so you only have to import one component Accordion and use it like <Accordion.Item /> following what Radix does.
I think that would make this component way cleaner and easier to understand since you can’t use AccordionItem outside of the root.

Is there a way to keep the compound exports so you only have to import one component Accordion and use it like <Accordion.Item /> following what Radix does.

I agree, that's a nice pattern. I just pushed an update with that change. I'll update above with the new syntax as well.
Thanks, @cdedreuille! Now get back to vacationing! 🙂

@winkerVSbecks Thanks for the review! My most recent commits should address all of your comments.

Can you add mobile viewports to exercise Accordion on smaller viewports? Note that mobile is tricky because the accordion is displayed in the context of an FAQ so the viewport definition has to take that into account.


Some page style changes

Keep the home-link-logo top left.
Give build name more room on releases page.
Changes default to last 10 releases.
Adds github link/logo to footer.
Only show the video promo and text on localhost or github.
(maybe that should only be github?)
A few little spacing additions.

Can you rebase this one too? You shouldn't need the flask-mail head edit anymore.


[question]: MAUI - Error updating nuget from 4.3.3 to 5.0.2

How can we help?
When trying to update the nuget package in our MAUI app from 4.3.3 to 5.0.2 or any 5.X.X i get the following error:
Path not found:
C:\Users\DaveXXXXX.nuget\packages\onesignalsdk.dotnet\5.0.2\res\ios\OneSignalFramework.xcframework\ios-arm64_x86_64-maccatalyst\OneSignalFramework.framework\Versions\Current\Modules\OneSignalFramework.swiftmodule\x86_64-apple-ios-macabi.private.swiftinterface
The path is 260 characters long but i already enabled "LongPaths" in windows registry.
Is this really a path problem or did anyone have this problem?
Code of Conduct

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

Same problem with XCode 15.0.1 in distant Mac and .net Maui 8 with Visual Studio 2022 v 17.8.1 windows 11

Same problem.

Same problem here. Will you fix it?

I did the same as snoova except I used RegEdit to add long path support.  And I right-clicked My Computer, properties, advanced, environment variables to test Temp to be C:\Tmp.  I found LongPathEnabled turned off and needed to be reset periodically.

@DaveBrask do you create a short directory for the nugets?
important is to restore nuget packages from command line. After that, you can run your project in VS

I'm using 5.1.3.  I didn't need to restore from the command line.


Automatically load a subset of world plugins

Addresses #57

Just checking @mjcarroll, I remember we already discussed the use case in #537. Would exporting an empty IGN_GAZEBO_SERVER_CONFIG be enough to prevent the load of these plugins? Do you think that adding a test for this use case could be worth?

Just checking @mjcarroll, I remember we already discussed the use case in #537. Would exporting an empty IGN_GAZEBO_SERVER_CONFIG be enough to prevent the load of these plugins? Do you think that adding a test for this use case could be worth?

Empty may currently be an issue, due to an upstream ign-common bug I found while implementing this: https://github.com/ignitionrobotics/ign-common/issues/96
To work around this in the short-term, exporting any content that doesn't point to a valid file should be sufficient to trigger this behavior.  There are tests in ServerConfig_TEST.cc to cover this as well.

Can you fix conflicts?

Done.

Also, since this changes a lot the way ign-gazebo is used and adds functionality that's difficult to discover, what do you think of writing a tutorial?

Will do.

I'm removing this from the Dome beta release. We're already in feature freeze and code freeze is in 2 days. This is a backwards-compatible feature that can be merged into Citadel then merged forward to Dome after the release.

@osrf-jenkins run tests please

@mjcarroll , what's the status of this PR? You mentioned you were working on some more fixes. It would be nice to get this in soon.

I noticed that scenebroadcaster test seems to be failing over here as well: https://github.com/ignitionrobotics/ign-gazebo/pull/531, so I don't think it's related to my changes?

I noticed that scenebroadcaster test seems to be failing over here as well: https://github.com/ignitionrobotics/ign-gazebo/pull/531, so I don't think it's related to my changes?

Holding this until 3->4 forward ports are done

Holding this until 3->4 forward ports are done


⚠ Bofrost.lu has degraded performance

In 473be7a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1497 ms

Resolved: Bofrost.lu performance has improved in 846a0c5 after 6 minutes.


[WFCORE-2382] credential reference with {EXT} command ignores parameters

https://issues.jboss.org/browse/WFCORE-2382
https://issues.jboss.org/browse/JBEAP-8212

Core - Full Integration Build 4659 outcome was FAILURE using a merge of 8c240bd66468fd6cb8ff656f7bb6cc00c41b24cd
Summary: Exit code 1 (new) Build time: 00:00:55

Full integration - Windows Build 3086 outcome was FAILURE using a merge of 8c240bd66468fd6cb8ff656f7bb6cc00c41b24cd
Summary: Exit code 1 (new) Build time: 00:04:30


CDN is broken

I was looking through the documentation and wanted to play around with the latest release (2.1.1) but on the homepage the CDN showing is (2.1.0), when using (2.1.) (https://cdnjs.cloudflare.com/ajax/libs/numbro/2.1.0/numbro.min.js) it appears it is broken.
Can someone fix this?

Please see #446

done, thanks for reporting!


problem: doesn't run because of invalid path to vault binary

Codecov Report

Merging #1054 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1054   +/-   ##
=======================================
  Coverage   41.94%   41.94%
=======================================
  Files         342      342
  Lines        5436     5436
  Branches      764      764
=======================================
  Hits         2280     2280
  Misses       3017     3017
  Partials      139      139

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 c3e4d02...887e3be. Read the comment docs.


Data discrepancy between DB and GraphiQL interface

The decimal number data getting displayed in the GraphiQL interface is getting rounded off and hence is different from the data in the DB.
For eg:- If there is a column with value as<PHONE_NUMBER>517.1299 in the DB , the same column gets displayed in the GraphiQL interface as<PHONE_NUMBER>517.13.
Is there a way to maintain the data consistency between the DB and the GraphiQL Ui interface.

Looks like you might be using standard floats - PostgreSQL is rounding it:
select<PHONE_NUMBER>517.1299::float;

      float8
------------------
<PHONE_NUMBER>517.13

If you need higher precision than this you should use numeric:
select<PHONE_NUMBER>517.1299::numeric;

      numeric
--------------------
<PHONE_NUMBER>517.1299
(1 row)

If you're using numeric then you should find that PostGraphile outputs it as a string.
(You didn't mention which version you're using.)

The version of postgraphql being used is 3.5.0.
The datatype of the column in the Postgres Database is double precision.
The value of the column in the database is<PHONE_NUMBER>745.6797 and when we query the DB the values returned is<PHONE_NUMBER>745.6797. But after querying for the same data via the GraphiQL interface, the value is getting rounded off to<PHONE_NUMBER>745.68.
Please confirm if there is some rounding logic in the PostgraphQL API.
The version of PostgresQL DB is 9.5.

There is no rounding logic in the PostGraphile v4 API - we use the value direct from PostgreSQL (and if we don't support it, we use the string type instead). Both PostgreSQL and V8 use IEEE Standard 754 for Binary Floating-Point Arithmetic, so the values should be equivalent.
In PostGraphQL v3 it's possible that we are attempting to represent a numeric or decimal as a float which will result in loss of precision due to IEEE Standard 754. As you've opted to not share any SQL with me I can't tell what data types you're working with.
Here's some things that may help you figure it out:
select<PHONE_NUMBER>745.6797;
      ?column?
--------------------
<PHONE_NUMBER>745.6797
(1 row)

^ The above is a numeric (arbitrary precision number) which in v4 we represent with a string because Node.js and GraphQL both don't support arbitrary precision numbers. I'm not sure how v3 handles it - it's possible it casts to a float, and this is what the issue is.
select<PHONE_NUMBER>745.6797::float;
      float8
------------------
<PHONE_NUMBER>745.68
(1 row)

^ PostgreSQL rounds the number to what you say if you treat the number as a float.

There is no rounding logic in the PostGraphile v4 API - we use the value direct from PostgreSQL (and if we don't support it, we use the string type instead).

I suspect something more subtle is happening.  I've noticed similar "rounding" behavior with big integers, similar to the loss of precision I would expect with floating point, even when they are attempted to be handled as strings.
Here's an easily reproducible example using 4.0.0-alpha2.28:
create or replace function static_big_integer() returns setof int8 as $$
    select generate_series(30894622507013190,<PHONE_NUMBER>7014190);
$$ language sql stable security definer;
comment on function static_big_integer() is
E'generates 1000 integers between<PHONE_NUMBER>7013190 and<PHONE_NUMBER>7014190';

{
  staticBigInteger {
    edges {
      node
    }
  }
}

Result:
{
  "data": {
    "staticBigInteger": {
      "edges": [
        {
          "node": "30894622507013190"
        },
        {
          "node": "30894622507013190". <-- should end in 1, not 0
        },
        {
          "node": "30894622507013190". <-- should end in 2, not 0
        },
        {
          "node": "30894622507013190". <-- should end in 3, not 0
        },
        {
          "node": "30894622507013190". <-- should end in 4, not 0
        },
        {
          "node": "30894622507013196". <-- should end in 5, not 6
        },
        {
          "node": "30894622507013196"
        },
        {
          "node": "30894622507013196"
        },
        {
          "node": "30894622507013200"
        },
        {
          "node": "30894622507013200"
        },

Thanks for the reproducing test case! It turns out that PostgreSQL is generating valid JSON but that Node.js is incapable of parsing said JSON without loss of precision. I just had a read through the JSON specification and it seems JSON actually puts no limit on the size of numbers (I previously believed that they were limited to IEEE754, like JavaScript) - this is yet another way that JSON differs to JavaScript!
With this test case it should be quite easy to work around the issue; I'll get this fixed before v4 enters beta.

 Fix PostgreSQL producing JSON that Node.js cannot handle without loss of precision

Here's a JSON parser for JS that enables parsing these large numbers:
https://www.npmjs.com/package/json-bigint
However I think I'm just going to convert them to strings in Postgres and stick to the built in JSON.parse

However I think I'm just going to convert them to strings in Postgres and stick to the built in JSON.parse

Thanks for the quick replies, and +1 for asking the database to the work!


This means Lakota Family, in Native American. It's the tribe I've descended from. It's also the poorest county in the United States. I don't live there but all of my family does. It's extreme poverty on the Pine Ridge Reservation. So I want to creat a crypto currency that I can make profitable for them. The least I can do for them kids and the ones who managed to make it through blizzards, wars, and sicknesses. If anyone can assist me in creating this crypto it will be gratefully appreciated. I'm a rookie myself in the crypto world but I only get to live once!

This means Lakota Family, in Native American. It's the tribe I've descended from. It's also the poorest county in the United States. I don't live there but all of my family does. It's extreme poverty on the Pine Ridge Reservation. So I want to creat a crypto currency that I can make profitable for them. The least I can do for them kids and the ones who managed to make it through blizzards, wars, and sicknesses. If anyone can assist me in creating this crypto it will be gratefully appreciated. I'm a rookie myself in the crypto world but I only get to live once!
Originally posted by @Swhistler1 in https://github.com/Iktomi-ink/demo-repository/issues/1

@Swhistler1 just create a 10 line solidity code and deploy to the ethernum network and a token will be created and that's it😀


Gobblin as a Service

Gobblin as it exists today is a framework that can be used to build different integration applications like ingest, replication etc. Each of these applications are typically configured as a separate job and executed through a scheduler like Azkaban. This PR introduces an approach to evolve Gobblin from a framework to a service. Specifically, the goal of this PR is to enable self service so that different users or external services can programmatically provision and execute all supported Gobblin applications limiting the need for the development and manual deployment during the provisioning process across multiple Gobblin Deployments.
Gobblin as a Service (GAAS) overall Architecture

The figure above provides a high level architectural view of Gobblin as a Service.
In the diagram above, each of the solid lines represents a unique Gobblin Job. The dotted lines are control flow messages.
At a high level, Gobblin as a Service exposes an API (and in future an UI) for users to submit requests. These requests are then translated into well defined Gobblin jobs. The users would principally interact with Gobblin as a Service through the Orchestration Service. We discuss the details of this module below.
Service Cluster (Frontend / Backend)

GaaS itself runs in a cluster mode for high availability. This cluster consists of identical nodes backed by a VIP for load balancing. Each node in the cluster hosts a frontend server and a backend server.

FE servers (not in this PR): FE or Frontend servers exposes a User Interface to let users manage their requests. It interacts with the  Backend servers via the REST APIs.
BE servers: BE or Backend servers are the core of the system and have several sub modules. These servers are the actual orchestrators of the user desired data flow.  All nodes in the cluster are identical. However, only one of them performs monitoring to avoid duplication of work. This node is designated as the master node and its election is done using Helix/Zookeeper.  The BE servers communicates with different Gobblin Jobs using any communication paradigm supported by that particular Gobblin Job. At the very minimum, Kafka messages are supported.

The important sub-components of Backend server are discussed in “Service Core Architecture” design section.
Modes (Standalone single instance / cluster)
GaaS can be run and deployed in multiple modes. The dependencies for each are listed as follows:

Single instance mode: FE and BE deployed on same box, no requirement of Zookeeper
Cluster mode: FE and BE deployed on multiple boxes, Zookeeper required for master election for monitoring in BE server.

Service Core Architecture (modules running on each machine)

As described in the previous section, each node / machine in the cluster runs identical subcomponents. In this section, we will zoom into the modules that Backend server on each machine runs.
Before we discuss individual sub-components and their design, let us define a few terms for easier understanding of the design.
General terms:

Logical Data Flow: Representative of the required flow of dataset from source to specific destination(s) that can take the form: “Ingest Salesforce data to NoSQL and then load the data onto HDFS”
Gobblin Jobs: Representative of physical flow ie. job in that Gobblin understands of the form of Pair <Job Executor Instance, Job Specification <Job Config, Job Template>> that ingests, manipulates and moves data. For eg., a DistcpNg job executing on Grid-1 that copies data between Grid-1 and Grid-2 are an example of Gobblin jobs.

Logical Entities:

FlowSpec: Data model representation that describes a Logical Data Flow.
JobSpec: Data model representation that describes a physical Gobblin Job.
TopologySpec: Data model representation that describes a topology ie. a JobExecutorInstance and its capabilities tuple (JobExecutorInstance is described later)
GobblinMetricsEvents: Standard events that gobblin-metric emits to help track various execution events and metrics.
Job Templates: Pre-configured file with properties that can be overridden for various possible physical Gobblin Jobs.
Template Packs: Independently deployed template collection that contains Gobblin Job Templates.

Key components and their working:

JobExecutorInstance: A technology and location tuple representative of a data pipeline or system that can process physical Gobblin Jobs. Examples are:  <Azkaban-1, Grid-1>, <Gobblin SelfManaged Cluster, Grid-2>
JobExecutorInstance Capabilities: List of tuple of JobExecutorInstance and its Capability. Capability is the tuple of source and list of destination(s) that a JobExecutorInstance supports.
GobblinClusterJobExecutorInstance: A Gobblin SelfManaged Cluster’s JobExecutorInstance.
AzkabanJobExecutorInstance: An Azkaban JobExecutorInstance.
FlowManager:  A sub-component of Gobblin-as-a-Service that runs as a JVM Service in BE and hosts FlowCatalog and FlowCompiler.
FlowCatalog: A catalog of all the FlowSpecs that are currently known to Gobblin-as-a-Service.
FlowCatalogListener: A hook to listen to any FlowSpec changes such as addition, deletion or update of any FlowSpec.
FlowStore: A persistence layer where FlowSpecs are persisted for durability.
FlowCompiler: A logical module that takes in a FlowSpec and converts it into JobSpecs that are runnable on specific JobExecutorInstance.
TopologyManager: A sub-component of Gobblin-as-a-Service that runs as a JVM Service in BE and hosts TopologyCatalog.
TopologyCatalog: A catalog of all the TopologySpecs that are currently known to Gobblin-as-a-Service.
TopologyCatalogListener: A hook to listen to any TopologySpec changes such as addition, deletion or update of any TopologySpec.
OrchestratorModule: A sub-component of Gobblin-as-a-Service that runs as a JVM Service in BE and is a FlowCatalogListener and TopologyCatalogListener. If any FlowSpec is added, removed or updated or any TopologySpec is added, removed or updated then the OrchestratorModule invokes FlowCompiler to determine updated JobSpecs for a FlowSpec and provisions them on respective JobExecutorInstances.
JobCompiler: A logical module that takes in a JobSpec and creates customized jobs that can be understood by respective JobExecutorInstance such as GobblinClusterJobExecutorInstance and AzkabanJobExecutorInstance.
Monitoring Module: A sub-component of Gobblin-as-a-Service that runs as a JVM Service in BE and tracks completion of FlowSpec and related metrics and SLAs.
MetricsConsumers: A logical module used by Monitoring to consume metrics from various sources such as Kafka. (We generally emit GobblinMetricsEvents to Kafka from all JobExecutorInstance)
MetricAnalyzer: A logical module used by Monitoring to analyze consumed metrics and aggregate them by FlowSpec.
SLAMonitor: A logical module used by Monitoring to use the analysis performed by MetricAnalyzer to ensure against SLA violations.
MetricsStore: A persistence layer where metrics are persisted for durability.
CoreServices: A sub-component of Gobblin-as-a-Service that is the application entry point for BE and starts other sub-components as JVM Services.
Provisioner: A futuristic sub-component of Gobblin-as-a-Service that will run as a JVM Service and provision ie. launch and setup JobExecutorInstances if required.
JobMonitor: A component that is a part of JobExecutorInstance that listens for any new or updated JobSpec being shipped by the Orchestrator module in Gobblin-as-a-Service.
KafkaJobMonitor: A Kafka JobMonitor that listens to Kafka for any new or updated JobSpecs.

Address all the minor comments, will create separate Jiras / Issues for couple of bigger items:

When we restore all scheduled jobs from Kafka when ClusterMaster restarts, we might not be able to fully restore the state since some job events might be lost due to Kafka retention
Comprehensive testing of URIs for FlowSpecs

Thanks for the continued review!!


Update StringSubstitutor JavaDoc

Its just class name replacement, propably refactoring miss

Coverage remained the same at 97.833% when pulling 62d8ada45af760c8a5cb1a89f3e9ecee15f0bade on wrzosdev:patch-1 into b962c35db685f8a6f2642e03be56d09672012fd0 on apache:master.

Thanks! 👍


DELETE cdns/{name}/federations/{id} takes in CDN ID in the "name" parameter

I'm submitting a ...

bug report

Traffic Control components affected ...

Traffic Ops

Current behavior:

The DELETE cdns/{name}/federations/{id} expects the CDN name as a parameter, but actually takes in the CDN ID. This is misleading and confusing to anyone who uses that API endpoint.
Expected behavior:

The endpoint should take in the CDN "name" for the name parameter, as do all the other federation endpoints.
Minimal reproduction of the problem with instructions:

Run TO and TP locally
Open the network tab of the inspect console in TP so that you can see the requests
Create a federation for one of the CDNs and then try to DELETE it
Note how the DELETE endpoint takes in the CDN ID for the name parameter
Anything else:

Unclear without investigation whether this is a regression bug or just incorrect documentation

Turns out the issue was just in Traffic Portal, which was incorrectly using the CDN ID instead of the CDN Name. I'll fix it in my current PR, run some more tests and close this issue.

Fixed in https://github.com/apache/trafficcontrol/pull/6043


Helm: Add the possibility to overwrite Pod and Container SecurityContext

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Using multiple strategy types

@MRIIOT, can I use multiple strategy types in config.yml? Like strategy: l99.driver.fanuc.collectors.UseCase01, l99.driver.fanuc.collectors.ProgramAndPieceCount, fanuc? Or should I rather merge l99.driver.fanuc.collectors.UseCase01 with l99.driver.fanuc.collectors.ProgramAndPieceCount first and then use the merged strategy type?

Right now it is only one strategy type per machine.  Merging the strategies to give you the data you want would be ideal.

I see. Well, having multiple strategies is not that important then.


ui-04 g90 colour is wrong on site

The g90 theme colour for ui-04 is listed as 'Gray 60' with a hex code of #8d8d8d. As far as I can make out, 'Gray 60' is actually #6f6f6f.  (It appears to have been given the 'Gray 50' color, which is #8d8d8d.)
https://github.com/carbon-design-system/carbon-website/blob/acad8caae9654b468daa011a67e6c139ded17785/src/data/guidelines/color-tokens.js#L205-L216

Also ,'Blue 70' is sometimes shown as #054ada (as in $hover-primary-text) and sometimes as #0043ce (as in $support-04)


Update volume limits

WIP
Description
Updates volume limiting to support multiple asset denominations.
Previously, all volume limits were in dollars. This approximation worked for v1 pools where all assets were worth ~1 dollar, but will not work for v2.
Coingecko volumes are now returned in the base currency for each pair, and volume limits for trades in the opposite direction are computed using the current price at each tick in the volume limited arb pipeline.
Hygiene checklist

[ ] Changelog entry
[x] Everything public has a Numpy-style docstring
(modules, public functions, classes, and public methods)
[ ] Pylint score monotonically increased
[ ] Commit history is cleaned-up with minor changes squashed together
and descriptive commit messages following Tim Pope's style

Cute Animal Picture

These changes do not affect the simple pipeline, but do affect the volume limited arbitrage pipeline. There, the volume limits are altered slightly for v1 pools because the limits are no longer in USD, but in units of the actual currency being traded.
Testing with 3pool, the results are similar enough to be visually indistinguishable, but not numerically identical (as expected).
Old volume limiter:

New volume limiter:

Full plot html files in this zip:
3pool_volume_limiter_comparison.zip


Corrupted entries in firewall logs

Since update to 20.1.5 a entry with interface S appears randomly in the logs.

All other log entries are ok

It's probably greedy matching issue with  2fad6bf36d0eb. Can you confirm?
# opnsense-patch 2fad6bf36d0eb

I've applied the patch and at least in the first 5 minutes it seems to be ok.


OpenCL error when running binary

$ ./sia-gpu-miner
./sia-gpu-miner: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: no version information available (required by ./sia-gpu-miner)
Initializing...
Failed to get number of OpenCL platforms with error code -1001 (clGetPlatformIDs).
Ubuntu 14.04:
nvidia-opencl-icd-346
nvidia-libopencl1-346
opencl-headers (assume this is not required...)

Some other people on ubuntu were having the same problem. I think you are missing a library. If you figure out what you need to install, can you let us know and we'll add it to the readme.

This worked for me on Ubuntu 15.04 with the 346.96 nvidia driver (gtx 970)
http://askubuntu.com/questions/541114/how-to-make-opencl-work-on-14-10-nvidia-331-89-drivers


Build warning when building with java 11

command mvn clean install -Pits
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass (file:/home/papolishchuk/.m2/repository/org/codehaus/groovy/groovy-all/2.4.21/groovy-all-2.4.21.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

mvn -v
Apache Maven 3.8.3 (ff8e977a158738155dc465c6a97ffaf31982d739)
Maven home: /home/me/maven/3.8.3
Java version: 11.0.13, vendor: Amazon.com Inc., runtime: /home/me/java/corretto-<IP_ADDRESS>.1
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.13.0-27-generic", arch: "amd64", family: "unix"

not the case anymore


Modify default cli fields in fidesctl.toml on init

Relates to #512
Code Changes

[x] Default cli fields for indclude_values changed from  "cli": {"server_url", "analytics_id"} to "cli": {"server_protocol", "server_host", "server_port", "analytics_id"}

Steps to Confirm

[ ] Create an empty .fides directory
[ ] Run fidesctl init
[ ] Verify the generated .fides/fidesctl.toml file contains server_protocol, 'server_host, and analytics_id` as keys.

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[x] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
The server port is included in the values to includes, however since it does not have a default value it doesn't get added to the resulting file. I included it anyways in case a default value is ever added, that way the resulting file will include it. I am not sure if #512 can be closed with this or not. The issue of the protocol being doubled seems to be fixed even without this update so I think it can.

@sanders41 thanks for this fix! Good catch

tested locally, looks good!


Revisit filesystem, internal, external, and locale encodings

These encoding aliases are actually dynamic, and can be changed by user code. For example if you have test.rb:
Encoding.default_external = Encoding::Windows_1253
require_relative "test2"
p $foo.encoding

and test2.rb:
# encoding: external
$foo = "\xb5"

then the whole thing will print #<Encoding:Windows-1253>. Currently we alias a lot of these to UTF-8, and don't handle internal at all. This whole thing needs to be revisited to allow consumers to pass in their encodings.

Oh wow, is anyone using these encoding in the magic encoding comment? I have never seen it.

Fixed by https://github.com/ruby/ruby/pull/9490


xLaunch xTasks configs for separate Identity Server

I see that if the identity server is separated, it is not included in the xLaunch, and xTasks.    A fix for this would be much appreciated!

Hello Berin. Added in v0.0.417. Regards


Updating to 3.23.0 causes error with RDS cluster_identifier

When updating to the latest version (currently 3.23.0) from 3.12.2 of the AWS provider we are seeing the following error when running an update concerning the database cluster_identifier claiming it to be invalid for the aws.rds.Cluster resource. We are also using lateest version (2.17.0) of the CLI.
aws:rds:Cluster (databaseCluster):
    error: aws:rds/cluster:Cluster resource 'databaseCluster' has a problem: only lowercase alphanumeric characters and hyphens allowed in "cluster_identifier"

This is not a field that we are explicitly defining, it was being set by the provider. We think this could possibly be because this field was recently marked as auto-named. Currently the only workaround we have found for this is explicitly specifying the value by hard coding the same cluster_identifier value specified in the checkpoint file.

The TL;DR here is that we accidentally shipped a breaking change and reverting it is not an option because that would be a breaking change for anyone who created an RDS cluster after the change was introduced (v3.13.0). An explanation of the issue and suggested workarounds are described below.
This error arose because we marked clusterIdentifier as an auto-named property. There are two issues with this:

Auto-naming adds a random suffix to the resource name. If the resource name has a capitalized character (i.e. dbCluster), the autoname would be dbCluster-[random-characters-or-numbers]. But, the cluster identifier property can only have lower cased characters. This is fixed by #1300 which will lowercase all characters when creating the clusterIdentifer, so the result will be dbcluster-[random-characters-or-number]. So anyone creating a new cluster will not hit this issue again.
It was already being auto-named by the underlying tf provider. This means that anyone who created a cluster with pulumi-aws v3.12.2 or earlier and did not specify a clusterIdentifier in their program that upgrades to a new version of the provider will cause a forced replacement on update because the cluster identifier will have changed (from the tf autonamed to the pulumi autonamed).

Workarounds

You can specifically set the clusterIdentifier in your program to the existing auto-generated name which follows the pattern tf-[random-numbers-and-characters]. To check the value of the existing clusterIdentifier, you can export the stack with pulumi stack export and check the outputs for your cluster and the clusterIdentifier should be listed there.
If you have many stacks each with a different db cluster, workaround 1 might not be an option. In this case you will have to manually edit the exported stack json and re-import it.

Export your stack with pulumi stack export > stack.json
Open stack.json in a text editor, copy the "clusterIdentifier": [value] line from outputs and add it to inputs.
Update the "__defaults" list in inputs to include "clusterIdentifier".
Re-import your stack with pulumi stack import --file stack.json.

:pray: Apologies for any grief this may have caused you :pray:

The TL;DR here is that we accidentally shipped a breaking change and reverting it is not an option because that would be a breaking change for anyone who created an RDS cluster after the change was introduced (v3.13.0). An explanation of the issue and suggested workarounds are described below.
This error arose because we marked clusterIdentifier as an auto-named property. There are two issues with this:

Auto-naming adds a random suffix to the resource name. If the resource name has a capitalized character (i.e. dbCluster), the autoname would be dbCluster-[random-characters-or-numbers]. But, the cluster identifier property can only have lower cased characters. This is fixed by #1300 which will lowercase all characters when creating the clusterIdentifer, so the result will be dbcluster-[random-characters-or-number]. So anyone creating a new cluster will not hit this issue again.
It was already being auto-named by the underlying tf provider. This means that anyone who created a cluster with pulumi-aws v3.12.2 or earlier and did not specify a clusterIdentifier in their program that upgrades to a new version of the provider will cause a forced replacement on update because the cluster identifier will have changed (from the tf autonamed to the pulumi autonamed).

Workarounds

You can specifically set the clusterIdentifier in your program to the existing auto-generated name which follows the pattern tf-[random-numbers-and-characters]. To check the value of the existing clusterIdentifier, you can export the stack with pulumi stack export and check the outputs for your cluster and the clusterIdentifier should be listed there.
If you have many stacks each with a different db cluster, workaround 1 might not be an option. In this case you will have to manually edit the exported stack json and re-import it.

Export your stack with pulumi stack export > stack.json
Open stack.json in a text editor, copy the "clusterIdentifier": [value] line from outputs and add it to inputs.
Update the "__defaults" list in inputs to include "clusterIdentifier".
Re-import your stack with pulumi stack import --file stack.json.

:pray: Apologies for any grief this may have caused you :pray:

thank you @komalali!

thank you @komalali!

After thinking it through some more we realized that reverting is not a breaking change, so we will revert the auto-naming of RDS clusters.

After thinking it through some more we realized that reverting is not a breaking change, so we will revert the auto-naming of RDS clusters.


#164694232 Authors can tag their articles.

What does this PR do?

Allow authors of articles to tag their articles

Description of Task to be completed?

[x] update article model, add tags field to the article class

[x]  implement an endpoint that gets all tags

[ ] test feature functionality

How should this be manually tested?

Move into project directory on your local computer

Run server using python manage.py runserver command
Login using verified login_credentials
Create an article using endpoint  POST/ api/articles/
use the body below

request body
    {   "title":value,
        "description": value,
        "body":value,
        "tags":["value","value"]
     }

What are the relevant pivotal tracker stories?
#164694232

Coverage decreased (-1.006%) to 94.63% when pulling d0fb41895b1d4d527aa58e96c3cc2f7bc1fb88f1 on ft-tag-articles-164694232 into 70e436b8093e80cdf48cf8b049d1d0a902bc8e80 on develop.


Remove /reference_datasets from v03 reference datasets paths.

gs://seqr-reference-data/v03/GRCh38/reference_datasets/

it's unnecessary to put it in the path if it's in the bucket.

This is actually incorrect, we do want reference_datasets in the path.  Our path structure is now gs://seqr-reference-data/v03/GRCh38/{DatasetType}/{reference_datasets/cached_reference_dataset_queries} so we should keep it in the path.


let pub make examples from packages easily accessible.

This issue was originally filed by @butlermatt

What steps will reproduce the problem?

Pub install web_ui
Find the TodoMVC example buried deep in pub-cache
try running??

What is the expected output? What do you see instead?
It is really really difficult to run examples which are distributed with packages.
What version of the product are you using? On what operating system?
any
Please provide any additional information below.
Solutions involve manually downloading packages from pub (tar.gz format no .zip option for Windows users) or cloning a development repository (which can break due to changing dependencies, being a development branch, etc).
It would be great if there was a way pub could make these example folders easily accessible from the installed packages, perhaps copying them to a new destination to allow them to be loaded into the editor.
My personal preference would be to copy them rather than symlink them and make them visible, that way originals can always be left in-tact and developers can experiment with examples and trash them when done.

This issue has been moved to dart-lang/pub#549.


TypeError: Cannot read properties of undefined (reading 'elements')

TypeError: Cannot read properties of undefined (reading 'elements')
at StoryProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:201:101138)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at SnackbarProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:262:29113)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at HistoryProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:2690233)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at Media3pApiProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:238:9786)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at FileProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:246:68345)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at APIProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:213:3094)
at https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at ConfigProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:201:113084)
at _ (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:5:25443)
at Fe (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:1:32060)
at ce (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:1:29079)
at FlagsProvider (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:213:3908)
at StoryEditor (https://sindhifonts.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:5:46918)

@mangnejo As noted on your other issue, all support for the Web Stories plugin is provided on our WordPress.org support forum. If you create a new topic there, we'd be happy to take a look and help you troubleshoot. Thanks!


Plugin causes warning on Windows platform

When compiling the app with this command for WP8 devices, I get this warning:
**cordova build windows --appx=8.1-phone**
MakePRI : warning 0xdef00520: Invalid qualifier: MOBILE-EVENTS [D:\PhoneGap\Argim\platforms\windows
\CordovaApp.Phone.jsproj]

Is there any way to prevent this? Thanks.

@andreszs The plugin enhances the iOS platform only. The warning must come from somewhere else.


Cannot get attrs.Converter() with takes_self pass through mypy

I've been playing with the attrs.Converter() but I am unable to get it type-checked with mypy when using takes_self. Now I am not considering (the obvious) Unsupported converter, only named functions, types and lambdas are currently supported error. What I am struggling with is how to annotate the self. The following code:
def str2int(s: str|int, self_: "C") -> int:
    return int(s)

@attrs.define
class C:
    x: int = attrs.field(
        converter=attrs.Converter(str2int, takes_self=True)
    )

Leads to the following error:
error: No overload variant of "Converter" matches argument types "Callable[[str | int, C], int]", "bool"  [call-overload]
note: Possible overload variants:
note:     def [In, Out] Converter(self, converter: Callable[[In], Out]) -> Converter[In, Out]
note:     def [In, Out] Converter(self, converter: Callable[[In, AttrsInstance, Attribute[Any]], Out], *, takes_self: Literal[True], takes_field: Literal[True]) -> Converter[In, Out]
note:     def [In, Out] Converter(self, converter: Callable[[In, Attribute[Any]], Out], *, takes_field: Literal[True]) -> Converter[In, Out]
note:     def [In, Out] Converter(self, converter: Callable[[In, AttrsInstance], Out], *, takes_self: Literal[True]) -> Converter[In, Out]

Is this just my own ignorance or an issue with attrs or mypy?
I am using:

attrs 24.2.0
mypy 1.13.0

I just noticed that the check passes with mypy 1.12.1 which may suggest a regression in mypy.

I forgot to circle back here. After playing a bit more with converters and validators I figured that the solution is actually pretty simple and straightforward:
def str2int(s: str|int, self_: attrs.AttrsInstance) -> int:
    if not isinstance(self_, C):
        raise TypeError(f"Converter does not know how to work with {type(self_)}")
    # Now the type of `self_` is properly inferred as `C`
    return int(s)

@attrs.define
class C:
    x: int = attrs.field(
        converter=attrs.Converter(str2int, takes_self=True)
    )

I am closing the issue. If anyone things this is worth documenting I can prepare a pull request for that.

Also possible to use typing.cast here.


Cable routing improvement proposal solo12

We are building a solo 12 in pal-robotics and we have found the cable routing around the shoulder joint very complicated. We had some issue with the cables being torn by the consecutive 90º forlds.
The assembly would be much simpler and durable if the cable channel was 3 to 5 mm wider. Would it be possible to expand the "Body Structure Hip AA Support" such that it has more room for the cabling.

Thank you.

True - the internal wire passage is pretty tight.
I increased it by 3mm - from 4mm to 7mm.
You can find the updated STL file here.
Does this solve your issue?

Best. Felix

Great!
Thank you.


Commit Function

Adds a commit function callback for LPs.
This function is called for an event on an LP when there is a guarantee that the event will not be rolled back.

Coverage increased (+0.05%) to 55.64% when pulling c5139d160c169054f0ca4ce372d0b96f8884a462 on commit into 793ded44bcc65e6e804fac031ebad80600d79706 on master.

[Current coverage][cc-pull] is 74.67%

Merging [#90][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

@@           master        #90   diff @@
========================================
  Files          25         25
  Lines        2542       2546     +4
  Methods         0          0
  Branches        0          0
========================================
+ Hits         1897       1901     +4
  Misses        645        645
  Partials        0          0

Powered by Codecov. Last updated by [793ded4...c5139d1][cc-compare]
[cc-base-branch]: https://codecov.io/gh/carothersc/ROSS/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/carothersc/ROSS/compare/793ded44bcc65e6e804fac031ebad80600d79706...c5139d160c169054f0ca4ce372d0b96f8884a462
[cc-pull]: https://codecov.io/gh/carothersc/ROSS/pull/90?src=pr

I believe there is a guarantee that all processed events will be fossil collected (and therefore committed) before the lp finalize functions are called... but someone should check my reasoning.
The "End Simulation" message may appear during commit calls, but this is due to parallel nodes. To prevent this, we could move the "End Simulation" message to after the tw_net_barrier call after the scheduling loop.

Coverage increased (+0.05%) to 55.64% when pulling d45672e68c6da0de7a142c7e3dd9394f76b32369 on commit into 793ded44bcc65e6e804fac031ebad80600d79706 on master.

A corresponding pull request has been created for CODES. Once this ROSS branch is merged, the CODES documentation should be updated (with the new hash) and the CODES pull request can be merged.
The commit function callback has been documented here: http://carothersc.github.io/ROSS/model-dev/lp-type-callbacks.html


Upgrade network to <IP_ADDRESS>

In stack.yaml and stack-8.6.5.yaml to avoid issues building network-<IP_ADDRESS> in some windows envs
fixes #1393
I suppose this should wait to next scheduled stack.yaml change

It is almost october, so we ought to do a release very soon, although we skipped september.

It turns out that bump up network version didnt resolve the issue.


kh: exclude rancher events

The rancher changes look good to me. Let's keep the PR open for a bit longer just in case we have more rules changes to make.


Add openldap support

See OPENLDAP.md for usage

I tested it and it is working, only problem is that you cannot generate config for checking group membership because RequireGroup is hardcoded to false, but after you manually change configuration it is working like a charm.


feat(Dropdown): setActiveFromChild prop

See issue: #960

I'm not 100% sure this will work with the use-case in #960. Using react-router's Link with it's activeClassName means that the active prop will not get set, only the "active" class if and when it is active and even that is only evaluated afterwards.
Looking at how react-bootstrap created this feature, they are just matching routes directly in their code to determine if the route is active rather than using anything react-router would give them.
So while this would work, it would not be able to leverage react-router to determine if the link is active, leaving it up to the user to add that logic in the active prop.

Yes you are right :( it doesn't work when using react-router Link

Still a nice feature. The kinks for the Link integration can be worked out later. For now, people can manage the active state of the dropdown via the items's active props rather than having additional logic in their code.

There's zero documentation for setActiveFromChild. It would be nice to always update the documentation when new features are added.

I don't think the property name is enough documentation in this case. A simple usage example would be clarifying enough, though.

@apaatsio good idea. I have created a PR, let me know if it is okay :)


⚠ Bofrost.at has degraded performance

In 691865b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2211 ms

Resolved: Bofrost.at performance has improved in 355b4a1 after 310 days, 21 hours, 10 minutes.


per-site templates and css

aleph.env should contain a list of directories to look for template files, allowing any file to be overridden
custom style sheets can be specified from config

@danohuiginn your turn, let me know if this works for you :)

Assuming this is OK now.


Some Dapper issues

I've found that it's easy to break Dapper and I'm including a script to reproduce it here. Works fine with Sqlite.
Not sure about priority of this ... do we even care about Dapper at this point in time?.
#!/usr/bin/env -S dotnet fsi

#r "nuget: DuckDB.NET.Data, 0.4.0"

// or include path to DuckDB.NET.Data build and load the .dll directly
//#I "../org/DuckDB.NET/DuckDB.NET.Data/bin/Debug/netstandard2.0/"
//#r "DuckDB.NET.Data.dll"

// also put libduckdb.{dll|so} someplace (e.g. in current directory) and point to it here
#I "."

#r "nuget: Microsoft.Data.Sqlite, 6.0.6"
#r "nuget: Dapper, 2.0.123"

open DuckDB.NET.Data
open Microsoft.Data.Sqlite
open Dapper
open System.Data

// test with either DuckDb or Sqlite
let conn =
    //new SqliteConnection("Data Source=:memory:") :> IDbConnection
    new DuckDBConnection("Data Source=:memory:") :> IDbConnection

conn.Open()
conn.Execute("CREATE TABLE test (id INTEGER, name VARCHAR)") |> ignore

[<CLIMutable>] type Row = { id:int; name:string }

conn.Query<Row>("SELECT * FROM test")
|> Seq.length
|> printfn "initial rows: %d"

conn.Execute("INSERT INTO test (id,name) VALUES (123,'test')") |> ignore

for row in conn.Query<Row>("SELECT * FROM test") do
    printfn $"after insertion: {row.id} {row.name}"

This should be fixed in 8eddf5217a8b99dd8592d46a0bafc8e8be6de25f


Potential bug in RunInfo Streamer

While playing around with RunInfo, I noticed that in the streamer the build window is treated as an Int_t, even though it is a long int. I haven't tested whether this, but that might mean that reading the run info from file, we're limited to 2^31 (about 2e9 = 20s) as maximum value for our build window.
Now obviously this isn't going to be an issue for any normal sorting, but maybe we should put a warning in RunInfo class about this (if it turns out to be true).

Are we sticking with a warning or do we just want to make it a long?

I'm not sure what happens if we change this to be a long in the streamer and then try and read an older version. I think we'll need to increment the version of RunInfo and make the streamer read it as long if the version is new, and as int for old versions. That way all the already sorted data should still be fine, and all new data would have a much larger limit.

Yeah, an incremented version, with a warning in the old version seems like the way to go for me.

On Oct 14, 2015, at 1:16 PM, Vinzenz Bildstein<EMAIL_ADDRESS>wrote:
I'm not sure what happens if we change this to be a long in the streamer and then try and read an older version. I think we'll need to increment the version of RunInfo and make the streamer read it as long if the version is new, and as int for old versions. That way all the already sorted data should still be fine, and all new data would have a much larger limit.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/495#issuecomment-148123072.

Okay, I've incremented the version to 6 and changed the streamer. Testing this with a RunInfo file with BuildWindow =<PHONE_NUMBER>00000 works fine. The warning would just need to go into the documentation, I wouldn't want to have a printout every single time we try to read the RunInfo from an older file.


(MAINT) Update CHANGELOG for 1.0.0 release

@smcelmurry @jpartlow I couldn't have said it better, so I just copied the commit messages into the CHANGELOG.
:shipit:

:+1:


Kkaye/include paths

This is an initial implementation of issue https://github.com/dropbox/djinni/issues/244. Included is:

--idl-include-path argument which specified a path to resolve @import and @extern directives.

Can be specified multiple times to indicate multiple paths, both relative and absolute. Relative paths are in relation to the directory from which djinni is run. eg:

  --idl-include-path "vendor/idl"
  --idl-include-path "/an/absolute/path/to/externs"

Modified import and extern file resolution logic to support multiple paths.

Resolution order begins at current directory. If import is not found relative to current file, resolution proceeds to search each --idl-include-path in the order specified, until the import is found.
If no imports are found then a FileNotFoundException is thrown and the user is provided an error message.

I look forward to hearing thoughts and feedback.

Automated message from Dropbox CLA bot
@GreatCall-KayeK, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Thanks for the PR @GreatCall-KayeK.  I've added some suggestions in line notes.  You'll also need to sign the CLA before I can merge your code.

@artwyman My apologies for the long delay on this PR, the CLA got stuck in legal.
I've signed that as well as implemented your feedback. Please let me know if you would like me rebase prior to merging this feature.

No worries, you're not the one slowing things down.  I'm way behind on PRs, but hope to have some time to catch up before the holidays.  Rebase is optional, so long as you've resolved all conflicts.  There aren't any major changes in master that I recall, which would make this harder to review.

@artwyman Thank you for your feedback. I've implemented changes and resolved merge conflicts.